Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

NX-OS snmp-trap strdata does not return string sent from device to object server

NX-OS snmp-trap strdata does not return string sent from device to object server

Applet was created:

    event manage applet TEST_VPC
    description "%ETHPORT-5-IF_DOWN_ADMIN_DOWN"
    event syslog occurs 1 priority 4 pattern "%ETHPORT-5-IF_DOWN_ADMIN_DOWN"
    action 1.0 snmp-trap strdata "Loopback0 is admin down"

after event is generated (link admin down), trap is sent to snmp server, but string does not appear in received messages:

2014-03-17T04:29:26: Debug: D-P_M-105-000: 1 trap in queue
2014-03-17T04:29:26: Debug: D-P_M-105-000: V2/V3 trap/inform received
2014-03-17T04:29:26: Information: I-P_M-104-000: Number of items in the trap queue is 0
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReqId: 1427018637
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] community: xxxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] IPaddress: x.x.x.x
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] PeerIPaddress: x.x.x.x
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReceivedPort: 162
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReceivedTime: 1395044966
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Protocol: UDP
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] SNMP_Version: 2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] UpTime: 1166940388
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Uptime: 1:30:03.88
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.2.1.1.3.0: (1166940388) 135 days, 1:30:03.88
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] notify: .1.3.6.1.4.1.9.9.43.2.0.2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.6.3.1.1.4.1.0: .1.3.6.1.4.1.9.9.43.2.0.2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] OID1: .1.3.6.1.4.1.9.9.43.1.1.1.0
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_raw: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_text: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_hex: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.4.1.9.9.43.1.1.1.0: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] OID2: .1.3.6.1.4.1.9.9.43.1.1.6.1.6.36
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_raw: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_text: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_hex: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.4.1.9.9.43.1.1.6.1.6.36: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Node: xxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] PeerAddress: xxxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] EventCount: 360
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Processing alert {0 remaining}
 

please help figure this out

Everyone's tags (1)
1 REPLY
Cisco Employee

This is a CISCO-CONFIG-MAN

This is a CISCO-CONFIG-MAN-MIB trap, not an EEM trap.  I don't think your EEM applet is being triggered since you have that priority argument in there.  Try removing that and leave the syslog pattern alone.  You will see the string as a varbind in the trap.

58
Views
0
Helpful
1
Replies
CreatePlease login to create content