Needing OID for Nexus SLA trap

[steven.2.holmes]

Afternoon all,

I'm looking for a bit of advice regarding setting up our NMS to correctly handle IP SLA Timeout traps for the following from our Nexus 7K when SLA's timeout:

ip sla reaction-configuration 1 react timeout action-type trapOnly

I've been asked by our NMS team to provide the trap OID, for this and to this point struggling to locate it. A couple of forums mention 1.3.6.1.4.1.9.9.42.1.2.10.1.2.1, but I can't seem to confirm it.

Is anyone able to confirm or provide a way of obtaining this?

[Mark Malone]

hi
Check this post Joe Clarke has answered it with a different OID ,you could test it easy enough , it wont break nythig either work or wont

https://community.cisco.com/t5/network-management/snmp-oid-for-ipsla-shows-up-also-if-operation-failed/td-p/1545858

[steven.2.holmes]

Update:

So these are what were compiled and added into our EMS:

We have compiled the MIB file given and got the below trap definitions.

Trap OID	ClassName	InstanceName	EventName	Severity	EventText	Expiration	State
.1.3.6.1.4.1.9.9.42.1.2.1.1.3 6 4	SNMPTrap	$SYS$	rttMonCtrlAdminRttType	3	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.1.1.1 6 2	SNMPTrap	$SYS$	rttMonCtrlAdminOwner	3	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.1.1.5 6 6	SNMPTrap	$SYS$	rttMonCtrlAdminFrequency	3	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.9.1.9 6 10	SNMPTrap	$SYS$	rttMonCtrlOperState	5	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.2.1.17 6 18	SNMPTrap	$SYS$	rttMonEchoAdminNumPackets	3	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.1.1.6 6 7	SNMPTrap	$SYS$	rttMonCtrlAdminTimeout	3	The 0 Varibles are -	600	NOTIFY
.1.3.6.1.4.1.9.9.42.1.2.9.1.5 6 6	SNMPTrap	$SYS$	rttMonCtrlOperTimeoutOccurred	3	The 0 Varibles are -	600	NOTIFY

After adding these and testing, although SNMP traps were received, no trap notification was triggered within the EMS customer view:

The detail from the EMS team was that as the EMS considers the trap ID which first follows the device IP (10.1.1.1), this being |.1.3.6.1.4.1.9.9.42.2|6|5 , it will check for this OID in the config file, and as this wasn't compiled as part of the request, therefore no trap generated within the EMS.

ASL_MSG-*-ASLP-icoi-trapd/trap_mgr_parse.asl: April 15, 2019 11:51:11 AM GMT+01:00 trap_mgr_parse.asl[00]: Undefined Trap : Trap was Not Generated...: 3611068605|10.1.1.1|.1.3.6.1.4.1.9.9.42.2|6|5|.1.3.6.1.4.1.9.9.42.1.2.1.1.3.311||.1.3.6.1.4.1.9.9.42.1.4.1.1.5.311.1.1.1|02 |.1.3.6.1.4.1.9.9.42.1.2.19.1.2.311.1|7|.1.3.6.1.4.1.9.9.42.1.2.19.1.10.311.1|1|.1.3.6.1.4.1.9.9.42.1.2.19.1.9.311.1|1|.1.3.6.1.4.1.9.9.42.1.2.19.1.5.311.1|0|.1.3.6.1.4.1.9.9.42.1.2.19.1.6.311.1|0|.1.3.6.1.4.1.9.9.42.1.2.2.1.33.311||

This was fine, and therefore believed they just needed to recompile with .1.3.6.1.4.1.9.9.42.2 OID. This however they have comeback saying the OID ‘1.3.6.1.4.1.9.9.42.2’ is mapped to ‘rttMonNotifications’ in the OID file, and that they cannot get the trap definitions from that MIB file with this being a Enterprise OID rather than a Trap OID. I am now at a loss of where I can obtain the OID trap definitions from for 1.3.6.1.4.1.9.9.42.2’ if not from the main CISCO-RTTMON-MIB.OID file.

Does anyone have any recommendations?