Community and Support

            Traps wrongly processed

            There are scenarios in which two trap OIDs from the same vendor are almost similar. Example 

            .1.3.6.1.4.1.6431.1.1.1.1515

            .1.3.6.1.4.1.6431.1.1.1.15

            Though the user have created separate trap processors for each trap OID, an incoming trap with a trap OID .1.3.6.1.4.1.6431.1.1.1.1515 can be processed by a different trap processor meant for .1.3.6.1.4.1.6431.1.1.1.15. This is because trap processor's trap OID is present inside the in coming trap message.  

            In order to avoid this, the trap OIDs  should be wrapped by < and > symbols. ie Edit the Admin-->SNMP trap processor meant for .1.3.6.1.4.1.6431.1.1.1.1515 and wrap the trap OID like <.1.3.6.1.4.1.6431.1.1.1.1515>

            Save the trap processor. Traps will be processed by the correct processors.
            Updated: 27 Feb 2014 01:27 PM
            Helpful?  
            Help us to make this article better
            0 0