Administrator Guide
58 TR_VRRPV3_PROT
OERR_REASON
1.3.6.1.2.1.68.0.3 vrrpTrapProtoError draft-ietf-vrrp-
unied-mib-06.mib
The error trap
indicates that the
sending agent has
encountered the
protocol error
indicated by
vrrpTrapProtoErrorR
eason.
59 TR_BGP4_ESTABLI
SHED
1.3.6.1.4.1.6027.20.1.1.0.
1
dellNetBgpM2Establi
shed
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
dellNetBgpM2Backw
ardTransition
DELL-
NETWORKING-
BGP4-V2-MIB.mib
The
BGPBackwardTransit
ion Event is
generated when the
BGP FSM moves
from a higher
numbered state to a
lower numbered
state.
61 TR_ECFM_FAULT_A
LARM
1.0.8802.1.1.3.0.1 dot1agCfmFaultAlar
m
stdecfm.mib A MEP has a
persistent defect
condition. A
notication (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
Notication
Generator State
Machine and
associated Managed
Objects. If a defect
with a higher priority
is raised after a Fault
Alarm has been
issued, another Fault
Alarm is issued. The
management entity
receiving the
notication can
identify the system
from the network
source address of
the notication, and
can identify the MEP
reporting the defect
by the indices in the
SNMP Traps
1543