User guide

Using SNMP
ExtremeWare 7.2e Installation and User Guide 51
already been using SNMPv1/v2c trap receivers, trap groups are very easy to incorporate into your
network. You cannot define your own trap groups. If you need to define more selectively which
notifications to receive, you will need to use the notification filter capabilities available in SNMPv3.
To configure trap groups, use the following command:
configure snmp add trapreceiver <ip address> {port <number>} community {hex}
<community string> {from <source ip address>} {mode [enhanced | standard]} trap-group
{auth-traps{,}} {extreme-traps{,}} {link-up-down-traps{,}} {ospf-traps{,}
{ping-traceroute-traps{,}} {rmon-traps{,}} {security-traps{,}} {smart-traps{,}}
{stp-traps{,}} {system-traps{,}} {vrrp-traps{,}}
For example, to send system and link up/link down traps to the receiver at 10.20.30.44 port 9347 with
the community string private, use the following command:
configure snmp add trapreceiver 10.20.30.44 port 9347 community private trap-group
link-up-down-traps , system-traps
Table 11 lists the currently defined SNMP trap groups. From time to time, new trap groups may be
added to this command.
Table 11: SNMP Trap Groups
Trap Group Notifications MIB Subtree
stp-traps newRoot
topologyChange
dot1dBridge, 1.3.6.1.2.1.17
ospf-traps ospfIfStateChange
ospfVirtIfStateChange
ospfNbrStateChange
ospfVirtNbrStateChange
ospfIfConfigError
ospfVirtIfConfigError
ospfIfAuthFailure
ospfVirtIfAuthFailure
ospfIfRxBadPacket
ospfVirtIfRxBadPacket
ospfTxRetransmit
ospfVirtIfTxRetransmit
ospfOriginateLsa
ospfMaxAgeLsa
ospfLsdbOverflow
ospfLsdbApproachingOverflow
ospfTraps, 1.3.6.1.2.1.14.16.2
ping-traceroute-traps pingTestFailed
pingTestCompleted
tracerouteTestFailed
tracerouteTestCompleted
pingNotifications, 1.3.6.1.2.1.80.0
traceRouteNotifications, 1.3.6.1.2.1.81.0
vrrp-traps vrrpTrapNewMaster
vrrpTrapAuthFailure
vrrpNotifications, 1.3.6.1.2.1.68.0