alerting on the dreaded "broadcast storm" scenario

as I am aware SevOne does not have a preferred way to alert on the  dreaded "broadcast storm" scenario.  This is how I have it configured within my deployment:

Currently I monitor on broadcast storms in the following manner:

-broadcast storm occurs on a single port o a Juniper ex3300 switch.

- the Juniper switch generated a SNMP trap which is then sent to SevOne (this is hard coded in the config)

- SevOne takes the incoming SNMPV3 trap and pass's it thru to the "Trap Event Editor"

- Within the  "Trap Event Editor" the unique OID is denoted for the switch fabric that set off the alert under general and the trigger is hard coding with the following items:

General: JUNIPER-CHASSIS-DEFINES-MIB::jnxProductNameEX3300

Trigger: JUNIPER-SYSLOG-MIB::jnxSyslogTrap

- from here an email is generated and sent to the network team.

That email consists of the following:

---------------------------------------------------------------------------------------------------------------------

Trap received from $dev: $oid -- Bindings: $var

The combined broadcast, multicast and unknown unicast frames received on this port has reached the pre-configured storm control threshold of 1 Mbps. If the user on this port is using IP Multicast to send a traffic stream to receivers then storm control needs to be temporarily disabled on this port for the remainder of the day.

Below are the relevant commands for storm control.

// show if port is error disable
show ethernet-switching interfaces

// re-enable port
clear ethernet-switching port-error interface ge-0/0/0

// show log message to see date/time of port shutdown show log messages | last

** Traffic Statistic Commands **

// clear statistics on port
clear interface statistics ge-0/0/0

// show bandwidth usage in bps
show interface ge-0/0/0

// show traffic statistics (number of broadcast and multicast frames) show interface ge-0/0/0 extensive

---------------------------------------------------------------------------------------------------------------------

Can this be done in an easier way for end users?

If this be added into the NMS as a default feature that is much easer to setup and monitor? It may be be useful to others.