05-26-2014 05:18 AM - edited 03-07-2019 07:32 PM
hello,
need some assistance or help. I have a Nexus 7009 with a FEX N2K-C2248PQ connected. If the N2K goes down (e.g. power down) a syslog event is generated but no snmp-trap from the N7K to the snmp server. Interface up/downs or power supply failures are traped. This is the syslog event:
2014 Feb 13 10:47:47.594 n7009 %FEX-2-NOHMS_ENV_FEX_OFFLINE: FEX-113 Off-line (Serial Number xxxxxxxxx)
is there anybody with an idea?
Solved! Go to Solution.
06-18-2014 11:50 PM
We've found no solution out-of-the-box, even after some intense research.
But we implemented a simple workaround: Embedded Event Manager Applet. (EEM)
event manager applet EM-CHECK-FEX
description "Checks FEX for availability because no trap would be send"
event syslog occurs 1 pattern "FEX-2-NOHMS_ENV_FEX_OFFLINE"
action 100 snmp-trap strdata "FEX changed to OFFLINE"
action 101 syslog priority notifications msg TRAP_SEND: FEX changed to OFFLINE
The EEM tracks the occurence of the specific syslog-pattern.
If the syslog-pattern in question appears, a snmp-trap will be send.
06-18-2014 11:50 PM
We've found no solution out-of-the-box, even after some intense research.
But we implemented a simple workaround: Embedded Event Manager Applet. (EEM)
event manager applet EM-CHECK-FEX
description "Checks FEX for availability because no trap would be send"
event syslog occurs 1 pattern "FEX-2-NOHMS_ENV_FEX_OFFLINE"
action 100 snmp-trap strdata "FEX changed to OFFLINE"
action 101 syslog priority notifications msg TRAP_SEND: FEX changed to OFFLINE
The EEM tracks the occurence of the specific syslog-pattern.
If the syslog-pattern in question appears, a snmp-trap will be send.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide