Users Guide

Table Of Contents
Table 8. SNMP Trap List (continued)
56 TR_VRRPV3_GIVE
UP_MASTER
1.3.6.1.4.1.6027.3.2
6.1.5.1.45
dellNetSysAlarmVrr
pGiveupMaster
DELL-
NETWORKING-
CHASSIS-MIB.mib
The VRRP
generate this trap
when it is no longer
the master and
has entered non-
operational state
57 TR_VRRPV3_NEW
_MASTER
1.3.6.1.2.1.68.0.1 vrrpTrapNewMaste
r
draft-ietf-vrrp-
unified-mib-06.mib
The newMaster
trap indicates that
the sending agent
has transitioned to
'Master' state.
58 TR_VRRPV3_PRO
TOERR_REASON
1.3.6.1.2.1.68.0.3 vrrpTrapProtoError draft-ietf-vrrp-
unified-mib-06.mib
The error trap
indicates that the
sending agent has
encountered the
protocol error
indicated by
vrrpTrapProtoError
Reason.
59 TR_BGP4_ESTABL
ISHED
1.3.6.1.4.1.6027.20.1
.1.0.1
dellNetBgpM2Esta
blished
DELL-
NETWORKING-
BGP4-V2-MIB.mib
The BGP
Established event
is generated
when the BGP
FSM enters
the ESTABLISHED
state
60 TR_BGP4_BACKW
_XSITION
1.3.6.1.4.1.6027.20.1
.1.0.2
dellNetBgpM2Back
wardTransition
DELL-
NETWORKING-
BGP4-V2-MIB.mib
The
BGPBackwardTran
sition Event is
generated when
the BGP FSM
moves from a
higher numbered
state to a lower
numbered state.
61 TR_ECFM_FAULT
_ALARM
1.0.8802.1.1.3.0.1 dot1agCfmFaultAlar
m
stdecfm.mib A MEP has a
persistent defect
condition. A
notification (fault
alarm) is sent to
the management
entity with the OID
of the MEP that
has detected the
fault. Whenever a
MEP has a
persistent defect, it
may or may not
generate a Fault
Alarm to warn the
system
administrator of
the problem, as
controlled by the
MEP Fault
Notification
SNMP Traps 1551