I’d like to preface this by saying on the nexus platform storm-control by default does not actually errdisable the port (I believe in catalyst it did). We can just have it syslog and generate an SNMP trap.
en conf t event manager environment _email_to [email protected] event manager environment _email_server x.x.x.x event manager environment _email_from [email protected] event manager applet STORM-EMAIL event storm-control action 1.0 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "$_event_pub_time: Storm control on device tripped"
sample config for nexus:
en conf t int e1/1 storm-control broadcast level 20 storm-control multicast level 20 storm-control unicast level 20 storm-control action trap
sources:
1 – cisco documentation
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_chapter_010000.pdf
2 – syslog message source
https://supportforums.cisco.com/t5/eem-scripting/nexus-storm-control-eem-help/td-p/3071003