Traps Reference

Avaya Ethernet Routing Switch 8800/8600

7.1.3
NN46205-706, 04.01
January 2012
© 2012 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation,
to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on its Hardware and Software
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language,
as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the
Avaya Support Web site: http://support.avaya.com. Please note that if
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE ( “AVAYA”).
2 Traps Reference
Comments? infodev@avaya.com
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
the express written consent of Avaya can be a criminal, as well as a
civil offense under the applicable law.
Third-party components
Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (“Third
Party Components”), which may contain terms that expand or limit
rights to use certain portions of the Product (“Third Party Terms”).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the Avaya Support
Web site: http://support.avaya.com/Copyright.
Preventing Toll Fraud
“Toll fraud” is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of Toll Fraud associated with
your system and that, if Toll Fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Toll Fraud Intervention
If you suspect that you are being victimized by Toll Fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site: http://support.avaya.com. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation and Product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the Documentation and Product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support Web site: http://support.avaya.com.
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your Product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Web site: http://support.avaya.com.
January 2012
 Contents

Chapter 1: Purpose of this document............................................................................... 5

Chapter 2: New in this release........................................................................................... 7
Other changes........................................................................................................................................... 7
New traps......................................................................................................................................... 7
Chapter 3: Traps reference................................................................................................. 9
Proprietary traps........................................................................................................................................ 9
Standard traps........................................................................................................................................... 27
Chapter 4: Customer Service............................................................................................. 35
Getting technical documentation............................................................................................................... 35
Getting product training............................................................................................................................. 35
Getting help from a distributor or reseller.................................................................................................. 35
Getting technical support from the Avaya Web site.................................................................................. 35

Traps Reference January 2012 3

4 Traps Reference January 2012
Chapter 1: Purpose of this document

The document describes the proprietary and standard traps available for the Avaya Ethernet Routing
Switch 8800/8600.

Traps Reference January 2012 5

Purpose of this document

6 Traps Reference January 2012

Comments? infodev@avaya.com
Chapter 2: New in this release

The following section details what's new in Avaya Ethernet Routing Switch 8800/8600 Traps Reference,
NN46205-706 for Release 7.1.3:
• Other changes on page 7

Other changes
See the following sections for information about changes that are not feature-related:
• New traps on page 7

New traps
Trap messages for the following features are added for Release 7.1.3:
• VLACP flap detect and damping

Traps Reference January 2012 7

New in this release

8 Traps Reference January 2012

Comments? infodev@avaya.com
Chapter 3: Traps reference

This chapter provides information about traps. The Avaya Ethernet Routing Switch 8800/8600 generates
alarms, traps, and logs.
For more information about logs, see Avaya Ethernet Routing Switch 8800/8600 Logs Reference,
NN46205-701.

Proprietary traps
The following tables describe Avaya proprietary traps for the Ethernet Routing Switch
8800/8600. All these traps have a status of current.
Table 1: 1.3.6.1.4.1.2272.1.21.0.xx series

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnCardDown rcCardIndex A rcCardDown trap signifies
2.1.21.0.1 rcCardAdminStatus that the SNMPv2 entity,
rcCardOperStatus acting in an agent role, has
detected that the
rcCardOperStatus object for
one of its cards is about to
transition into the down
state.
1.3.6.1.4.1.227 rcnCardUp rcCardIndex A rcCardUp trap signifies
2.1.21.0.2 rcCardAdminStatus that the SNMPv2 entity,
rcCardOperStatus acting in an agent role, has
detected that the
rcCardOperStatus object for
one of its cards is about to
transition into the up state.
1.3.6.1.4.1.227 rcnErrorNotificatio rcErrorLevel A rcErrorNotification trap
2.1.21.0.3 n rcErrorCode signifies that the SNMPv2
rcErrorText entity, acting in an agent
role, has detected that an
error condition has
occurred.
1.3.6.1.4.1.227 rcnStpNewRoot rcStgId A rcStpNewRoot trap
2.1.21.0.4 signifies that the SNMPv2
entity, acting in an agent
role, has detected the

Traps Reference January 2012 9

Traps reference

OID Notification type Objects Description

Spanning Tree Protocol has
declared the device to be
the new root of the spanning
tree.
1.3.6.1.4.1.227 rcnStpTopologyC rcStgId rcPortIndex A rcStpTopologyChange
2.1.21.0.5 hange trap signifies that the
SNMPv2 entity, acting in an
agent role, has detected the
Spanning Tree Protocol has
gone due a topology change
event.
1.3.6.1.4.1.227 rcnChasPowerSu rcChasPowerSupplyId A
2.1.21.0.6 pplyDown rcChasPowerSupplyO rcChasPowerSupplyDown
perStatus trap signifies that the
SNMPv2 entity, acting in an
agent role, has detected that
the
rcChasPowerSupplyOperSt
atus object for one of its
power supply unit is about to
transition into the down
state.
1.3.6.1.4.1.227 rcnChasFanDown rcChasFanId A rcChasFanDown trap
2.1.21.0.7 rcChasFanOperStatus signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
rcChasFanOperStatus
object for one of its power
supply unit is about to
transition into the down
state.
1.3.6.1.4.1.227 rcnLinkOscillation rcPortIndex A rcLinkOscillation trap
2.1.21.0.8 signifies that the SNMPv2
entity, acting in an agent
role, has detected an
excessive number of link
state transitions on the
specified port.
1.3.6.1.4.1.227 rcnMacViolation rcErrorText A rcMacViolation trap
2.1.21.0.9 rcPortIndex signifies that the SNMPv2
entity, acting in an agent
role, has received a PDU
with an invalid source MAC
address.
1.3.6.1.4.1.227 rcnSonetTrap rcPortIndex A rcSonetTrap trap signifies
2.1.21.0.10 rcPosSonetTrapType that the SNMPv2 entity,

10 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

rcPosSonetTrapIndica acting in an agent role, has
tion detected a change of status
on a Sonet port.
1.3.6.1.4.1.227 rcn2kCardDown rc2kCardIndex A rcCardDown trap signifies
2.1.21.0.11 rc2kCardFrontAdminS that the SNMPv2 entity,
tatus acting in an agent role, has
rc2kCardFrontOperSt detected that the
atus rcCardOperStatus object for
one of its cards is about to
transition into the down
state.
1.3.6.1.4.1.227 rcn2kCardUp rc2kCardIndex A rcCardUp trap signifies
2.1.21.0.12 rc2kCardFrontAdminS that the SNMPv2 entity,
tatus acting in an agent role, has
rc2kCardFrontOperSt detected that the
atus rcCardOperStatus object for
one of its cards is about to
transition into the up state.
1.3.6.1.4.1.227 rcn2kTemperature rc2kChassisTemperat A rc2kTemperature trap
2.1.21.0.13 ure signifies that the SNMPv2
entity, acting in an agent
role, has detected the
chassis is overheating.
1.3.6.1.4.1.227 rcnChasPowerSu rcChasPowerSupplyId A rcChasPowerSupplyUp
2.1.21.0.14 pplyUp rcChasPowerSupplyO trap signifies that the
perStatus SNMPv2 entity, acting in an
agent role, has detected that
the
rcChasPowerSupplyOperSt
atus object for one of its
power supply unit is about to
transition into the up state.
1.3.6.1.4.1.227 rcn2kAtmPvcLink rc2kAtmPvcIfIndex A
2.1.21.0.15 StateChange rc2kAtmPvcVpi rc2kAtmPvcLinkStateChan
rc2kAtmPvcVci ge trap signifies that the
rc2kAtmPvcOamVcSt SNMPv2 entity, acting in an
atus agent role, has detected that
the
rc2kAtmPvcOamVcStatus
object for one of PVC is
about to transition into
different state, either from
up to down or from down to
up.
1.3.6.1.4.1.227 rcnStpTCN rcStgId rcPortIndex A rcStpTopologyChange
2.1.21.0.16 rcStgBridgeAddress trap signifies that the

Traps Reference January 2012 11

Traps reference

OID Notification type Objects Description

SNMPv2 entity, acting in an
agent role, has detected the
Spanning Tree Protocol has
gone due to a topology
change event.
1.3.6.1.4.1.227 rcnSmltIstLinkUp — A rcSmltIstLinkUp trap
2.1.21.0.17 signifies that the split MLT
link is from down to up.
1.3.6.1.4.1.227 rcnSmltIstLinkDo — A rcSmltIstLinkDown trap
2.1.21.0.18 wn signifies that the split MLT
link is from up to down.
1.3.6.1.4.1.227 rcnSmltLinkUp rcMltSmltId A rcMltSmltId trap signifies
2.1.21.0.19 that the split SMLT link is
up.
1.3.6.1.4.1.227 rcnSmltLinkDown rcMltSmltId A rcMltSmltId trap signifies
2.1.21.0.20 that the split SMLT link is
down.
1.3.6.1.4.1.227 rcnChasFanUp rcChasFanId A rcChasFanUp trap
2.1.21.0.21 rcChasFanOperStatus signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
rcChasFanOperStatus
object for one of its power
supply unit is about to
transition into the up state.
1.3.6.1.4.1.227 rcnPasswordCha rcCliPasswordChange A rcPasswordChange trap
2.1.21.0.22 nge rcCliPassChangeRes signifies that the SNMPv2
ult entity, acting in an agent
role, has detected that one
of the cli password is
changed.
1.3.6.1.4.1.227 rcnEmError rc2kCardIndex A rcEmError trap signifies
2.1.21.0.23 rcChasEmModeError that the SNMPv2 entity,
acting in an agent role, has
detected Em error.
1.3.6.1.4.1.227 rcnPcmciaCardRe — A rcPcmciaRemoved trap
2.1.21.0.25 moved signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
PCMCIA card is being
removed.
1.3.6.1.4.1.227 rcnSmartCpldTim rc2kCardIndex A rcSmartCpldTimerFired
2.1.21.0.26 erFired trap signifies that the cpld
timer fired.

12 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnCardCpldNotU rc2kCardIndex A rcCardCpldNotUpDate
2.1.21.0.27 pDate trap signifies that the cpld is
not up to date.
1.3.6.1.4.1.227 rcnIgapLogFileFul — A rcIgapLogFileFull trap
2.1.21.0.28 l signifies that the Igap
accounting time-out Log File
reach the maximum.
1.3.6.1.4.1.227 rcnCpLimitShutDo rcPortIndex A rcCpLimitShutDown trap
2.1.21.0.29 wn ifAdminStatus signifies that the cp limit for
ifOperStatus the port is shutting down.
rcPortCpLimitShutDo
wn
1.3.6.1.4.1.227 rcnSshServerEna rcSshGlobalPort A rcSshServerEnabled trap
2.1.21.0.30 bled signifies that the SSH server
is enabled.
1.3.6.1.4.1.227 rcnSshServerDisa rcSshGlobalPort A rcSshServerDisabled trap
2.1.21.0.31 bled signifies that the SSH server
is disabled.
1.3.6.1.4.1.227 rcnSshSessionLo rcSshGlobalHostIpAd A rcSshSessionLogin trap
2.1.21.0.32 gin dr signifies that there is a SSH
session login.
1.3.6.1.4.1.227 rcnSshSessionLo rcSshGlobalHostIpAd A rcSshSessionLogout trap
2.1.21.0.33 gout dr signifies that there is a SSH
session logout.
1.3.6.1.4.1.227 rcnSshUnauthoriz rcSshGlobalHostIpAd A
2.1.21.0.34 edAccess dr rcSshUnauthorizedAccess
trap signifies that an
unauthorized access has
occurred.
1.3.6.1.4.1.227 rcnHaCpuState rc2kCardIndex A rcHaCpuState trap
2.1.21.0.35 rcL2RedundancyHaC signifies the state of the HA-
puState CPU.
1.3.6.1.4.1.227 rcnInsufficientMe rc2kCardIndex A rcInsufficientMemory trap
2.1.21.0.36 mory indicates insufficient
memory on CPU blade for
proper operation.
Recommended memory =
256 MB available through
Avaya Inc. upgrade kit
1.3.6.1.4.1.227 rcnSaveConfigAct rcSysActionL1 A rcSaveConfigAction trap
2.1.21.0.37 ion indicates the switch run time
or boot configuration is
being saved.

Traps Reference January 2012 13

Traps reference

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnLoopDetectOn rcVlanId rcPortIndex A rcLoopDetectOnPort trap
2.1.21.0.38 Port indicates that a loop has
been detected on a port.
The vlan on that port will be
disabled.
1.3.6.1.4.1.227 rcnbgpEstablishe rcIpBgpPeerIpAddres The BGP Established event
2.1.21.0.39 d s is generated when the BGP
rcIpBgpPeerLastError FSM enters the
rcIpBgpPeerState ESTABLISHED state.
1.3.6.1.4.1.227 rcnbgpBackwardT rcIpBgpPeerIpAddres The
2.1.21.0.40 ransition s BGPBackwardTransition
rcIpBgpPeerLastError Event is generated when the
rcIpBgpPeerState BGP FSM moves from a
higher numbered state to a
lower numbered state.
1.3.6.1.4.1.227 rcnAggLinkUp rcMltId A rcAggLinkUp trap is
2.1.21.0.41 generated when the
operational state of the
aggregator changes from
down to up.
1.3.6.1.4.1.227 rcnAggLinkDown rcMltId A rcAggLinkDown trap is
2.1.21.0.42 generated when the
operational state of the
aggregator changes from up
to down.
1.3.6.1.4.1.227 rcnIgmpNewGrou rcIgmpGroupIfIndex An IgmpNewGroupMember
2.1.21.0.43 pMember rcIgmpGroupIpAddres trap signifies that a new
s rcIgmpGroupInPort member has come on an
rcIgmpGroupMember interface.
1.3.6.1.4.1.227 rcnIgmpLossGrou rcIgmpGroupMember An IgmpLossGroupMember
2.1.21.0.44 pMember s trap signifies that a group
rcIgmpGroupIpAddres member has been lost on an
s rcIgmpGroupInPort interface.
rcIgmpGroupIfIndex
1.3.6.1.4.1.227 rcnIgmpNewQueri igmpInterfaceIfIndex An igmpNewQuerier trap
2.1.21.0.45 er igmpInterfaceQuerier signifies that a new querier
has come up on an
interface.
1.3.6.1.4.1.227 rcnIgmpQuerierC igmpInterfaceIfIndex An rcIgmpQuerierChange
2.1.21.0.46 hange rcIgmpInterfaceExtnN trap signifies that the querier
ewQuerier has changed.
igmpInterfaceQuerier

14 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnDvmrpIfStateC dvmrpInterfaceIfIndex A rcDvmrpIfStateChange
2.1.21.0.47 hange dvmrpInterfaceOperSt trap signifies that there has
ate been a change in the state
of a DVMRP interface.
1.3.6.1.4.1.227 rcnDvmrpNewNbr dvmrpNeighborIfIndex A rcDvmrpNewNbrChange
2.1.21.0.48 Change dvmrpNeighborAddre trap signifies that a new
ss neighbor has come up on a
DVMRP interface.
1.3.6.1.4.1.227 rcnDvmrpNbrLoss dvmrpNeighborIfIndex A rcDvmrpNbrLossChange
2.1.21.0.49 Change dvmrpNeighborAddre trap signifies that a new
ss neighbor has gone down on
a DVMRP interface.
1.3.6.1.4.1.227 rcnFdbProtectViol rcPortIndex rcVlanId The rcFdbProtectViolation
2.1.21.0.59 ation trap signifies that the port
has violated the user
configured limit for total
number of fdb-entries
learned on that port.
1.3.6.1.4.1.227 rcnLogMsgContro rcSysMsgLogFrequen A rcMsgControl trap
2.1.21.0.60 l cy rcSysMsgLogText signifies whether the
number of times of repetition
of the particular Log
message has exceeded the
particular frequency/count
or not.
1.3.6.1.4.1.227 rcnSaveConfigFil rcSysActionL1 A rcSaveConfig trap
2.1.21.0.61 e rcSysConfigFileName signifies that either the
runtime config or the boot
config has been saved on
the switch.
1.3.6.1.4.1.227 rcnDNSRequestR rcSysDnsServerListIp A rcDnsRequestResponse
2.1.21.0.62 esponse Addr trap signifies that the switch
rcSysDnsRequestTyp had sent a query to the DNS
e server or it had received a
successful response from
the DNS Server.
1.3.6.1.4.1.227 rcnDuplicateIpAd ipNetToMediaNetAddr A rcDuplicateIpAddress trap
2.1.21.0.63 dress ess signifies that a duplicate IP
ipNetToMediaPhysAd address is detected on the
dress subnet.
1.3.6.1.4.1.227 rcnLoopDetectPor rcPortIndex A rcLoopDetectPortDown
2.1.21.0.64 tDown ifAdminStatus trap signifies that a loop has
ifOperStatus been detected on a port and

Traps Reference January 2012 15

Traps reference

OID Notification type Objects Description

the port is going to shut
down.
1.3.6.1.4.1.227 rcnLoopDetectMa rcPortIndex A rcLoopDetectMacDiscard
2.1.21.0.67 cDiscard rcSysMacFlapLimitTi trap signifies that a loop has
me been Detected on a port and
rcSysMacFlapLimitCo the mac address will be
unt discarded on all ports in that
vlan.
1.3.6.1.4.1.227 rcnAutoRecoverP rcPortIndex A rcnAutoRecoverPort trap
2.1.21.0.68 ort signifies that autorecovery
has reenabled a port
disabled by link flap or cp
limit.
1.3.6.1.4.1.227 rcnAutoRecoverL rcVlanNewLoopDetect A
2.1.21.0.69 oopDetectedPort edAction rcnAutoRecoverLoopDetect
edPort trap signifies that
autorecovery has cleared
the action taken on a port by
loop detect.
1.3.6.1.4.1.227 rcnExtCpLimitShu rcPortIndex A rcnExtCpLimitShutDown
2.1.21.0.70 tDown ifAdminStatus trap signifies that port is shut
down due to Extended CP-
Limit.
1.3.6.1.4.1.227 rcnExtCpLimitSop rcSysExtCplimitSysOc An
2.1.21.0.71 Congestion tapidCongested rcnExtCpLimitSopCongesti
rcSysExtCplimitPorts on signifies that system
Monitored octapid polling finds that
system octapid is congested
or not.
rcSysExtCplimitSysOctapid
Congested signifies
whether system octapid is
congested or not.
rcSysExtCplimitPortsMonito
red signifies whether ports
are selected for monitoring
the ingress traffic utilization.
1.3.6.1.4.1.227 trapTacacsAuthFa — This trap is generated when
2.1.21.0.74 ilure users log in to the chassis
with tacacs+ authentication
but tacacs+ authentication
failed.
1.3.6.1.4.1.227 trapTacacsNoSer — This trap is generated when
2.1.21.0.75 vers users log in to the chassis
with tacacs+ authentication

16 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

but no available tacacs+
server.
1.3.6.1.4.1.227 trapTacacsRxUns — This trap is generated when
2.1.21.0.76 upportedFrame users log in to the chassis
with tacacs+ authentication
but tacacs+ task receives
unsupported packet from
tacacs+ server.
1.3.6.1.4.1.227 trapTacacsExcee — This trap is generated when
2.1.21.0.77 dedMaxLogins users log in to the chassis
with tacacs+ authentication
but tacacs+ session has
exceeded max session
count of tacacs+
supporting.
1.3.6.1.4.1.227 trapTacacsClientF — This trap is generated when
2.1.21.0.78 ailure users log in to the chassis
with tacacs+ authentication
but tacacs+ task failed to
accept the authentication
request.
1.3.6.1.4.1.227 rcnBpduReceived rcPortBpduFilteringTi This event is generated
2.1.21.0.79 meout when a BPDU is received on
a port that has BPDU
filtering enabled.
1.3.6.1.4.1.227 rcnVlacpPortDow rcPortIndex A rcnVlacpPortDown trap
2.1.21.0.80 n signifies that Vlacp is down
on the port specified.
1.3.6.1.4.1.227 rcnVlacpPortUp rcPortIndex A rcnVlacpPortUp trap
2.1.21.0.81 signifies that Vlacp is Up on
the port specified.
1.3.6.1.4.1.227 rcnExtCpLimitShu — An
2.1.21.0.82 tDownNormal rcnExtCpLimitShutDownNo
rmal trap signifies that Ports
are shut down due to
Extended CP-Limit in
Normal mode.
1.3.6.1.4.1.227 rcnEapMacIntrusi rcSysIpAddr A rcnEapMacIntrusion trap
2.1.21.0.83 on rcRadiusPaePortNum signifies that an EAP MAC
ber intrusion has occurred on
rcRadiusEapLastAuth this Port.
Mac
rcRadiusEapLastRejM
ac

Traps Reference January 2012 17

Traps reference

OID Notification type Objects Description

1.3.6.1.4.1.227 rcPlugOptModTe rcPortIndex This is used to trap changes
2.1.21.0.89 mperatureStatusT rcPlugOptModTemper in the temperature status.
rap atureStatus
1.3.6.1.4.1.227 rcPlugOptModVolt rcPortIndex This is used to trap changes
2.1.21.0.90 ageStatusTrap rcPlugOptModVoltage in the voltage level.
Status
1.3.6.1.4.1.227 rcPlugOptModBia rcPortIndex This is used to trap changes
2.1.21.0.91 sStatusTrap rcPlugOptModBiasSta in the laser bias status.
tus
1.3.6.1.4.1.227 rcPlugOptModTx rcPortIndex This is used to trap changes
2.1.21.0.92 PowerStatusTrap rcPlugOptModTxPow in the transmit power
erStatus status.
1.3.6.1.4.1.227 rcPlugOptModRx rcPortIndex This is used to trap changes
2.1.21.0.93 PowerStatusTrap rcPlugOptModRxPow in the received power
erStatus status.
1.3.6.1.4.1.227 rcPlugOptModAux rcPortIndex This is used to trap changes
2.1.21.0.94 1StatusTrap rcPlugOptModAux1M in the Aux1 status.
onitoring
rcPlugOptModAux1St
atus
1.3.6.1.4.1.227 rcPlugOptModAux rcPortIndex This is used to trap changes
2.1.21.0.95 2StatusTrap rcPlugOptModAux2M in the Aux2 status.
onitoring
rcPlugOptModAux2St
atus
1.3.6.1.4.1.227 rcnMaxRouteWar rcVrfName A rcnMaxRouteWarnClear
2.1.21.0.110 nClear trap signifies that the
number of routes in the
routing table of the Virtual
Router has dropped below
its warning threshold.
1.3.6.1.4.1.227 rcnMaxRouteWar rcVrfName A rcnMaxRouteWarnSet
2.1.21.0.111 nSet trap signifies that the given
Virtual Router routing table
is reaching its maximum
size. Action should be taken
to prevent this.
1.3.6.1.4.1.227 rcnMaxRouteDrop rcVrfName A rcnMaxRouteDropClear
2.1.21.0.112 Clear trap signifies that the given
Virtual Router routing table
is no longer dropping new
routes as it is below its
maximum size.

18 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnMaxRouteDrop rcVrfName A rcnMaxRouteDropSet
2.1.21.0.113 Set trap signifies that the given
Virtual Router routing table
has reached its maximum
size, and is now dropping all
new nonstatic routes.
1.3.6.1.4.1.227 rcnMstpNewCistR rcStgBridgeAddress A rcMstpNewCistRoot trap
2.1.21.0.117 oot signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
Multiple Spanning Tree
Protocol has declared the
device to be the new root of
the common internal
spanning tree.
1.3.6.1.4.1.227 rcnMstpNewMstiR rcStgBridgeAddress A rcMstpNewMstiRoot trap
2.1.21.0.118 oot rcStgId signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
Multiple Spanning Tree
Protocol has declared the
device to be the new root of
the spanning tree instance.
1.3.6.1.4.1.227 rcnMstpNewCistR rcStgBridgeAddress A
2.1.21.0.119 egionalRoot rcMstpNewCistRegionalRo
ot trap signifies that the
SNMPv2 entity, acting in an
agent role, has detected that
the Multiple Spanning Tree
Protocol has declared the
device to be the new
regional root of the common
internal spanning tree.
1.3.6.1.4.1.227 rcnRstpNewRoot rcStgBridgeAddress A rcRstpNewRoot trap
2.1.21.0.120 signifies that the SNMPv2
entity, acting in an agent
role, has detected that the
Rapid Spanning Tree
Protocol has declared the
device to be the new root of
the spanning tree.
1.3.6.1.4.1.227 rcnRsmltEdgePee rcVlanId A
2.1.21.0.124 rModified rcnRsmltEdgePeerModified
trap signifies that the
RSMLT Peer address is
different from that of the

Traps Reference January 2012 19

Traps reference

OID Notification type Objects Description

stored address. A save
config is necessary if
EdgeSupport has to use this
info on next reboot.
1.3.6.1.4.1.227 rcnChasPowerSu — A
2.1.21.0.167 pplyNoRedundan rcnChasPowerSupplyNoRe
cy dundancy trap signifies that
the chassis is running on
power supply without
redundancy.
1.3.6.1.4.1.227 rcnChasPowerSu — A
2.1.21.0.168 pplyRedundancy rcnChasPowerSupplyRedu
ndancy trap signifies that the
chassis is running on power
supply with redundancy.
1.3.6.1.4.1.227 rcnLicenseTrialPe — A
2.1.21.0.171 riodExpired rcnLicenseTrialPeriodExpir
ed trap signifies that the Trial
Period License has
expired.
1.3.6.1.4.1.227 rcnLicenseTrialPe rcSysLicenseTrialDay A
2.1.21.0.172 riodExpiry sLeft rcnLicenseTrialPeriodExpir
y trap signifies the time
remaining before the
License Trial Period expires
in days.
1.3.6.1.4.1.227 rcnVrfUp rcVrfName This notification is
2.1.21.0.173 rcVrfOperStatus generated when the
specified VRF's operational
status is toggled from down
to up.
1.3.6.1.4.1.227 rcnVrfDown rcVrfName This notification is
2.1.21.0.174 rcVrfOperStatus generated when the
specified VRF's operational
status is toggled from up to
down.
1.3.6.1.4.1.227 rcnMrouteIngress rcIpResourceUsageGl This notification is
2.1.21.0.175 ThresholdExceed obalIngressRecInUse generated when the number
ed rcIpResourceUsageGl of mroute ingress records
obalIngressThreshold exceeds the ingress
threshold.
1.3.6.1.4.1.227 rcnMrouteEgress rcIpResourceUsageGl This notification is
2.1.21.0.176 ThresholdExceed obalEgressRecInUse generated when the number
ed of mroute egress records

20 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

rcIpResourceUsageGl exceeds the egress
obalEgressThreshold threshold.
1.3.6.1.4.1.227 rcnRemoteMirrori rcPortRemoteMirrorin A rcRemoteMirroringStatus
2.1.21.0.177 ngStatus gIndex trap signifies whether the
rcPortRemoteMirrorin remote mirroring is enabled
gEnable or disabled on a particular
rcPortRemoteMirrorin port.
gMode
1.3.6.1.4.1.227 rcnMaxMrouteWa — A rcnMaxMrouteWarnSet
2.1.21.0.178 rnSet trap signifies that the given
Virtual Routers multicast
routing table is reaching its
maximum size. Action
should be taken to prevent
this.
1.3.6.1.4.1.227 rcnMaxMrouteDro — A rcnMaxMrouteDropSet
2.1.21.0.179 pSet trap signifies that the given
Virtual Routers multicast
routing table has reached its
maximum size, and is now
dropping all new non static
routes.
1.3.6.1.4.1.227 rcnMaxMrouteWa — A rcnMaxMrouteWarnClear
2.1.21.0.180 rnClear trap signifies that the
number of routes in the
multicast routing table of the
Virtual Router has dropped
below its warning
threshold.
1.3.6.1.4.1.227 rcnMaxMrouteDro — A rcnMaxMrouteDropClear
2.1.21.0.181 pClear trap signifies that the given
Virtual Routers multicast
routing table is no longer
dropping new routes as it is
below its maximum size.
1.3.6.1.4.1.227 rcnAggLinkStateC — The trap is generated when
2.1.21.0.182 hange, the operational state of the
LAG changes; it identifies
three events: local down,
remote down, up.
1.3.6.1.4.1.227 rcnBfdSessExcee — A
2.1.21.0.183 dThreshold rcnBfdSessExceedThreshol
d signifies that the BFD
session have exceed
system limit and hence

Traps Reference January 2012 21

Traps reference

OID Notification type Objects Description

creation of new session
failed.
1.3.6.1.4.1.227 rcnBfdStatusChan — A rcnBfdSessChange
2.1.21.0.184 ge signifies that the status of
BFD session changed.
1.3.6.1.4.1.227 rcnChasPowerSu — A
2.1.21.0.185 pplyRunningLow rcnChasPowerSupplyRunni
ngLow trap signifies that the
chassis is running on low
power supply.
1.3.6.1.4.1.227 rcnIsisPlsbMetric rcIsisLocalLspId An SPBM IS-IS trap is
2.1.21.0.192 MismatchTrap rcIsisLocall1Metric generated when an LSP
rcIsisNgbLspId with a different value of l1–
rcIsisNgbl1Metric metric is received.
rcIsisPlsbTrapType
rcIsisTrapIndicator
1.3.6.1.4.1.227 rcnIsisPlsbDuplic rcIsisLocalSysId An SPBM IS-IS trap is
2.1.21.0.193 ateSysidTrap rcIsisLocalInterface generated when a Hello
rcIsisPlsbTrapType packet with a duplicate
rcIsisTrapIndicator system ID is received.
1.3.6.1.4.1.227 rcnIsisPlsbLsdbU rcIsisPlsbTrapType An SPBM IS-IS trap signifies
2.1.21.0.194 pdate that LSDB information has
changed.
1.3.6.1.4.1.227 rcnChasFanCooli rcChasFanOperStatus A rcnChasFanCoolingLow
2.1.21.0.196 ngLow rcChasFanType trap signifies that the
rcErrorLevel chassis is running on low fan
rcErrorText cooling.
1.3.6.1.4.1.227 rcnSmpFtpFail — A rcnSmpFtpFail trap
2.1.21.0.205 signifies that Ftp/Tftp has
failed in SMP(System
Messaging Platform). Ftp of
logfile happens when logfile
in PCMCIA becomes full or
PCMCIA has no space.
1.3.6.1.4.1.227 rcnSmpLogFileDe — A rcnSmpLogFileDeleted
2.1.21.0.206 leted trap signifies that Log File
has been deleted from
PCMCIA. Deletion of logfile
happens when either FTP of
logfile is successful or
PCMCIA has no space.
1.3.6.1.4.1.227 rcCardIndex rcnLegacyCardDetect Detects the legacy card on
2.1.21.0.265 ed the chassis.

22 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnIsisPlsbBvidMi rcIsisLocalSysId This event is generated
2.1.21.0.278 smatch rcIsisLocalPrimaryBvi when the Bvid TLV from the
d neighbor node does not
rcIsisLocalPrimaryTie match the local
BrkAlg configuration.
rcIsisLocalSecondary
Bvid
rcIsisLocalSecondary
TieBrkAlg
rcIsisNgbSysId
rcIsisNgbPrimaryBvid
rcIsisNgbPrimaryTieBr
kAlg
rcIsisNgbSeconaryBvi
d
rcIsisNgbSecondaryTi
eBrkAlg
rcIsisLocalBvidCounte
r
rcIsisNgbBvidCounter
rcIsisPlsbTrapType
rcIsisTrapIndicator
1.3.6.1.4.1.227 rcnIsisPlsbSmltVir rcIsisLocalVirtualBma An SPBM IS-IS trap signifies
2.1.21.0.279 tBmacMismatch c that the virtual BMAC
rcIsisPeerVirtualBmac configured in the switch is
rcIsisPlsbTrapType different from the virtual
rcIsisTrapIndicator BMAC configured in the IST
peer.
1.3.6.1.4.1.227 rcnIsisPlsbSmltPe rcIsisSysId An SPBM IS-IS trap signifies
2.1.21.0.280 erBmacMismatch rcIsisSmltPeerSysId that either the SMLT Peer
rcIsisPlsbTrapType BMAC configured in the IST
rcIsisTrapIndicactor peer is different from the IS-
IS system ID of the local
switch or the SMLT peer
BMAC configured in the
local switch is different from
the IS-IS system ID of the
IST peer.
1.3.6.1.4.1.227 rcnIsisPlsbAdjStat rcIsisNgbSysId This event is generated
2.1.21.0.281 e rcIsisLocalInterface when there is an IS-IS
rcIsisPlsbTrapType adjacency state change
rcIsisAdjState (down, init, up)
1.3.6.1.4.1.227 rcnIsisPlsbDuplic rcIsisNgbNickname An SPBM IS-IS trap is
2.1.21.0.282 ateNNameTrap rcIsisPlsbTrapType generated when an LSP
rcIsistrapIndicator with a duplicate nickname is
rcIsisNgbSysId received. This trap should

Traps Reference January 2012 23

Traps reference

OID Notification type Objects Description

rcIsisDuplicateNname be generated by all the
Counter switches in the network.
1.3.6.1.4.1.227 rcnIsisPlsbSmltSp rcIsisLocalSmltSplitBe An SPBM IS-IS trap signifies
2.1.21.0.283 litBebMismatch b that the SMLT split-Beb
rcIsisPeerSmltSplitBe configured in the local
b rcIsisPlsbTrapType switch and the IST peer are
rcIsisTrapIndicator the same. One IST switch
should be configured as
split-Beb primary and the
IST peer should be
configured as split-Beb
secondary.
1.3.6.1.4.1.227 rcnIsisPlsbMultiLi rcIsisNgbSysId This event is generated
2.1.21.0.284 nkAdjTrap rcIsisLocalInterface when IS-IS form more than
rcIsisPrevInterface one adjacency with the
rcIsisPlsbTrapType same IS-IS
rcIsisNgbHostName
rcIsisTrapIndicator
1.3.6.1.4.1.227 rcnVLacpFlapDet rcPortIndex A
2.1.21.0.289 ectShutDown rcVlacpFlapDetectShutDow
n trap signifies that the port
is shut down because
rcPortVLacpFlapFrequency
number of VLACP flaps
were detected within
rcPortVLacpFlapInterval
seconds on this port.The
port can be brought UP by
toggling the port admin state
manually.
1.3.6.1.4.1.227 rcnMsdpMaxSAC rcMsdpVrfId This event is generated
2.1.80.1.0.1 acheWarnSet rcMsdpSACacheType when the SA entries in the
cache database exceeds 85
% of maximum value (6K) in
local cache or in foreign
cache.
1.3.6.1.4.1.227 rcnMsdpMaxSAC rcMsdpVrfId This event is generated
2.1.80.1.0.2 acheWarnClear rcMsdpSACacheType when the Sa entries in the
cache database drops to 80
% of the maximum value
(6K).
1.3.6.1.4.1.227 rcnMsdpMaxSAC rcMsdpVrfId This event is generated
2.1.80.1.0.3 acheErrorSet rcMsdpSACacheType when the SA entries in the
cache database hits 100 %
of the maximum value (6K).

24 Traps Reference January 2012

Comments? infodev@avaya.com
 Proprietary traps

OID Notification type Objects Description

1.3.6.1.4.1.227 rcnMsdpMaxSAC rcMsdpVrfId This event is generated
2.1.80.1.0.4 acheErrorClear rcMsdpSACacheType when the SA entries in the
cache database drops to
95% of the maximum value.
1.3.6.1.4.1.227 rcnMsdpMaxPeer rcMsdpVrfId This event is generated
2.1.80.1.0.5 SACacheWarnSet rcMsdpPeerSALimit when the SA entries for this
peer exceeds 85 % of
maximum value configured
for this peer.
1.3.6.1.4.1.227 rcnMsdpMaxPeer rcMsdpVrfId This event is generated
2.1.80.1.1.2.1 SACacheWarnCle rcMsdpPeerSALimit when the SA entries for this
.11 ar peer drops to 80 % of the
maximum value configured
for this peer.
1.3.6.1.4.1.227 rcnMsdpMaxPeer rcMsdpVrfId This event is generated
2.1.80.1.0.7 SACacheErrorSet rcMsdpPeerSALimit when the SA entries for this
peer hits 100 % of the peer
SA limit.
1.3.6.1.4.1.227 rcnMsdpMaxPeer rcMsdpVrfId This event is generated
2.1.80.1.0.8 SACacheErrorCle rcMsdpPeerSALimit when the SA entries for this
ar peer drops to 95% of the
peer SA limit.
1.3.6.1.4.1.227 rcnMsdpEstablish rcMsdpVrfId The MSDP Established
2.1.80.1.0.9 ed MsdpPeerFsmEstabli event is generated when the
shedTransitions MSDP FSM enters the
ESTABLISHED state.
1.3.6.1.4.1.227 rcnMsdpBackwar rcMsdpVrfId The
2.1.80.1.0.10 dTransition MsdpPeerState MSDPBackwardTransition
Event is generated when the
MSDP FSM moves from a
higher-numbered state to a
lower-numbered state.

Table 2: 1.3.6.1.4.1.45.5.10.x.xx series

OID Notification Objects Description

type
1.3.6.1.4.1.45 nsnaClosedCo nsnaClosedConnec This notification is generated
.5.10.0.1 nnectionToSn tionReason whenever the device closes the
as connection to the NSNAS. The
reason why the connection is
closed is indicated in
nsnaClosedConnectionReason.

Traps Reference January 2012 25

Traps reference

OID Notification Objects Description

type
1.3.6.1.4.1.45 nsnaStatusQu — This notification is generated
.5.10.0.2 oIntervalExpir whenever the status-quo interval
ed expires after the connection to
theNSNAS has closed. Note that if
the configured status-quo interval
is 0 (indicating no status quo
interval), this notification will be
generated at the same time as the
corresponding
nsnaClosedConnectionToSnas
notification.
1.3.6.1.4.1.45 nsnaInvalidMe nsnaInvalidMessag This notification is generated
.5.10.0.3 ssageFromSn eHeader whenever the device receives an
as invalid message from the NSNAS.
This generally means that the
received message is corrupted. As
much of the message header as is
available will be included in
nsnaInvalidMessageHeader.

Table 3: 1.3.6.1.4.1.2272.1.50.x.xx series

OID Notification Objects Description

type
1.3.6.1.4.1.227 rcWisSonetTra sectionAlarm(1) Used to indicate a particular type
2.1.50.2.1 pType lineAlarm(2) of 10GE Sonet trap.
pathAlarm(3)
1.3.6.1.4.1.227 rcWisSonetTra noDefect(1) Used to indicate an indication for a
2.1.50.2.2 pIndication sectionLossOfSign 10GE Sonet trap.
al(2)
sectionLossOfFram
e(3)
lineAlarmIndication(
4)
lineRemoteDefectIn
dication(5)
pathLossOfPointer(
6)
pathAlarmIndicatio
n(7)
pathRemoteDefectI
ndication(8)
pathUnequipped(9)
pathSignalLabelMis
match(10)

26 Traps Reference January 2012

Comments? infodev@avaya.com
 Standard traps

OID Notification Objects Description

type
pathTraceMismatc
h(11)
1.3.6.1.4.1.227 rcnSlppPortDo rcSlppPortSlppEna A port down event that has
2.1.64.1.0.1 wnEvent ble occurred due to SLPP. The user is
rcSlppVlanSlppEna notified of the expected Vlan ID
ble along with the Vlan ID and source
rcSlppIncomingVla MAC address of the packet
nId coming in on the port identified.
rcSlppSrcMacAddr The first two objects can be used
ess to lookup instance info for port ID
and VLAN ID.

Standard traps
The following table describes standard traps that the Avaya Ethernet Routing Switch
8800/8600 can generate.
Table 4: Standard traps

OID Notification type Objects Description

1.3.6.1.2.1.10.1 mplsTunnelUp mplsTunnelAdmin This notification is generated
66.3.0.1 Status when a mplsTunnelOperStatus
mplsTunnelOper object for one of the configured
Status tunnels is about to leave the
down state and transition into
some other state (but not into
the notPresent state). This other
state is indicated by the included
value of
mplsTunnelOperStatus.
1.3.6.1.2.1.10.1 mplsTunnelDown mplsTunnelAdmin This notification is generated
66.3.0.2 Status when a mplsTunnelOperStatus
mplsTunnelOper object for one of the configured
Status tunnels is about to enter the
down state from some other
state (but not from the
notPresent state). This other
state is indicated by the included
value of
mplsTunnelOperStatus.
1.3.6.1.2.1.10.1 mplsTunnelRero mplsTunnelAdmin This notification is generated
66.3.0.3 uted Status when a tunnel is rerouted. If the

Traps Reference January 2012 27

Traps reference

OID Notification type Objects Description

mplsTunnelOper mplsTunnelARHopTable is
Status used, then this tunnel instance's
entry in the
mplsTunnelARHopTable may
contain the new path for this
tunnel some time after this trap
is issued by the agent.
1.3.6.1.2.1.10.1 mplsTunnelReopt mplsTunnelAdmin This notification is generated
66.3.0.4 imized Status when a tunnel is reoptimized. If
mplsTunnelOper the mplsTunnelARHopTable is
Status used, then this tunnel instance's
entry in the
mplsTunnelARHopTable may
contain the new path for this
tunnel some time after this trap
is issued by the agent.
1.3.6.1.2.1.10.1 mplsLdpInitSessi mplsLdpEntityInit This notification is generated
66.4.0.1 onThresholdExce SessionThreshol when the value of the
eded d mplsLdpEntityInitSessionThres
hold object is not zero, and the
number of Session Initialization
messages exceeds the value of
the
mplsLdpEntityInitSessionThres
hold object.
1.3.6.1.2.1.10.1 mplsLdpPathVect mplsLdpEntityPat This notification is sent when the
66.4.0.2 orLimitMismatch hVectorLimit mplsLdpEntityPathVectorLimit
mplsLdpPeerPath does not match the value of the
VectorLimit mplsLdpPeerPathVectorLimit
for a specific Entity. Reference
RFC3036, LDP Specification,
Section 3.5.3.
1.3.6.1.2.1.10.1 mplsLdpSession mplsLdpSession If this notification is sent when
66.4.0.3 Up State the value of
mplsLdpSession mplsLdpSessionState enters
DiscontinuityTime the operational(5) state.
mplsLdpSession
StatsUnknownMe
sTypeErrors
mplsLdpSession
StatsUnknownTlv
Errors
1.3.6.1.2.1.10.1 mplsLdpSession mplsLdpSession This notification is sent when the
66.4.0.4 Down State value of mplsLdpSessionState
mplsLdpSession leaves the operational(5) state.
DiscontinuityTime

28 Traps Reference January 2012

Comments? infodev@avaya.com
 Standard traps

OID Notification type Objects Description

mplsLdpSession
StatsUnknownMe
sTypeErrors
mplsLdpSession
StatsUnknownTlv
Errors
1.3.6.1.2.1.14.1 ospfVirtIfStateCh ospfRouterId An ospfIfStateChange trap
6.2.1 ange ospfVirtIfAreaId signifies that there has been a
ospfVirtIfNeighbor change in the state of an OSPF
ospfVirtIfState virtual interface. This trap
should be generated when the
interface state regresses (e.g.,
goes from Point-to-Point to
Down) or progresses to a
terminal state (i.e., Point-to-
Point).
1.3.6.1.2.1.14.1 ospfNbrStateCha ospfRouterId An ospfNbrStateChange trap
6.2.2 nge ospfNbrIpAddr signifies that there has been a
ospfNbrAddressL change in the state of a non-
essIndex virtual OSPF neighbor. This trap
ospfNbrRtrId should be generated when the
ospfNbrStat neighbor state regresses (e.g.,
goes from Attempt or Full to 1-
Way or Down) or progresses to
a terminal state (e.g., 2-Way or
Full). When a neighbor
transitions from or to Full on
non-broadcast multi-access and
broadcast networks, the trap
should be generated by the
designated router. A designated
router transitioning to Down will
be noted by ospfIfStateChange
1.3.6.1.2.1.14.1 ospfVirtNbrState ospfRouterId An ospfIfStateChange trap
6.2.3 Change ospfVirtNbrArea signifies that there has been a
ospfVirtNbrRtrId change in the state of an OSPF
ospfVirtNbrState virtual neighbor. This trap
should be generated when the
neighbor state regresses (e.g.,
goes from Attempt or Full to 1-
Way or Down) or progresses to
a terminal state (e.g., Full).
1.3.6.1.2.1.14.1 ospfIfConfigError ospfRouterId An ospfIfConfigError trap
6.2.4 ospfIfIpAddress signifies that a packet has been
ospfAddressLessI received on a non-virtual
f ospfPacketSrc interface from a router whose
ospfConfigErrorT configuration parameters

Traps Reference January 2012 29

Traps reference

OID Notification type Objects Description

ype conflict with this router's
ospfPacketType configuration parameters. Note
that the event optionMismatch
should cause a trap only if it
prevents an adjacency from
forming.
1.3.6.1.2.1.14.1 ospfVirtIfConfigEr ospfRouterId An ospfConfigError trap
6.2.5 ror ospfVirtIfAreaId signifies that a packet has been
ospfVirtIfNeighbor received on a virtual interface
ospfConfigErrorT from a router whose
ype configuration parameters
ospfPacketType conflict with this router's
configuration parameters. Note
that the event optionMismatch
should cause a trap only if it
prevents an adjacency from
forming.
1.3.6.1.2.1.14.1 ospfIfAuthFailure ospfRouterId An ospfIfAuthFailure trap
6.2.6 ospfIfIpAddress signifies that a packet has been
ospfAddressLessI received on a non-virtual
f ospfPacketSrc interface from a router whose
ospfConfigErrorT authentication key or
ype authentication type conflicts
authTypeMismatc with this router's authentication
h authFailure key or authentication type.
ospfPacketType
1.3.6.1.2.1.14.1 ospfVirtIfAuthFail ospfRouterId An ospfVirtIfAuthFailure trap
6.2.7 ure ospfVirtIfAreaId signifies that a packet has been
ospfVirtIfNeighbor received on a virtual interface
ospfConfigErrorT from a router whose
ype authentication key or
authTypeMismatc authentication type conflicts
h authFailure with this router's authentication
ospfPacketType key or authentication type.
1.3.6.1.2.1.14.1 ospfIfStateChang ospfRouterId An ospfIfStateChange trap
6.2.16 e ospfIfIpAddress signifies that there has been a
ospfAddressLessI change in the state of a non-
f ospfIfState virtual OSPF interface. This trap
should be generated when the
interface state regresses (e.g.,
goes from Dr to Down) or
progresses to a terminal state
(i.e., Point-to-Point, DR Other,
Dr, or Backup).
1.3.6.1.2.1.16.0 risingAlarm alarmIndex The SNMP trap that is
.1 alarmVariable generated when an alarm entry

30 Traps Reference January 2012

Comments? infodev@avaya.com
 Standard traps

OID Notification type Objects Description

alarmSampleTyp crosses its rising threshold and
e alarmValue generates an event that is
alarmRisingThres configured for sending SNMP
hold traps. TRAP TYPE
ENTERPRISE rmon
1.3.6.1.2.1.16.0 fallingAlarm alarmIndex The SNMP trap that is
.2 alarmVariable generated when an alarm entry
alarmSampleTyp crosses its falling threshold and
e alarmValue generates an event that is
alarmFallingThre configured for sending SNMP
shold traps. TRAP TYPE
ENTERPRISE rmon
1.3.6.1.2.1.46.1 vrrpTrapStateTra ifIndex A vrrpTrapStateTransition trap
.3.0.3 nsition vrrpTrapStateTra signifies a state transition has
nsitionType occurred on a particular vrrp
vrrpTrapStateTra interface. Implementation of this
nsitionCause trap is optional.
vrrpOperVrId 'vrrpOperIpAddr' contains the IP
vrrpOperIpAddr address of the vrrp interface
ipAdEntAddr while ipAdEntAddr' contains the
IP address assigned to physical
interface.
1.3.6.1.2.1.68.0 vrrpTrapNewMas vrrpOperMasterIp The newMaster trap indicates
.1 ter Addr that the sending agent has
transitioned to Master state.
1.3.6.1.2.1.68.0 vrrpTrapAuthFail vrrpTrapPacketSr A vrrpAuthFailure trap signifies
.2 ure c that a packet has been received
vrrpTrapAuthErro from a router whose
rType authentication key or
authentication type conflicts
with this router's authentication
key or authentication type.
1.3.6.1.2.1.80.0 pingProbeFailed pingCtlTargetAdd Generated when a probe failure
.1 ressType is detected when the
pingCtlTargetAdd corresponding
ress pingCtlTrapGeneration object is
pingResultsOper set to probeFailure(0) subject to
Status the value of
pingResultsIpTar pingCtlTrapProbeFailureFilter.
getAddressType The object
pingResultsIpTar pingCtlTrapProbeFailureFilter
getAddress can be used to specify the
pingResultsMinRt number of successive probe
t failures that are required before
pingResultsMaxR this notification can be
tt generated.

Traps Reference January 2012 31

Traps reference

OID Notification type Objects Description

pingResultsAvera
geRtt
pingResultsProbe
Response
pingResultsSentP
robes
pingResultsRttSu
mOfSquares
pingResultsLastG
oodProbe
1.3.6.1.2.1.80.0 pingTestFailed pingCtlTargetAdd Generated when a ping test is
.2 ressType determined to have failed when
pingCtlTargetAdd the corresponding
ress pingCtlTrapGeneration object is
pingResultsOper set to testFailure(1). In this
Status instance
pingResultsIpTar pingCtlTrapTestFailureFilter
getAddressType should specify the number of
pingResultsIpTar probes in a test required to have
getAddress failed in order to consider the
pingResultsMinRt test as failed.
t
pingResultsMaxR
tt
pingResultsAvera
geRtt
pingResultsProbe
Responses
pingResultsSentP
robes
pingResultsRttSu
mOfSquares
pingResultsLastG
oodProbe
1.3.6.1.2.1.80.0 pingTestComplet pingCtlTargetAdd Generated at the completion of
.3 ed ressType a ping test when the
pingCtlTargetAdd corresponding
ress pingCtlTrapGeneration object is
pingResultsOper set to testCompletion(4).
Status
pingResultsIpTar
getAddressType
pingResultsIpTar
getAddress
pingResultsMinRt
t
pingResultsMaxR
tt

32 Traps Reference January 2012

Comments? infodev@avaya.com
 Standard traps

OID Notification type Objects Description

pingResultsAvera
geRtt
pingResultsProbe
Responses
pingResultsSentP
robes
pingResultsRttSu
mOfSquares
pingResultsLastG
oodProbe
1.3.6.1.2.1.81.0 traceRoutePathC traceRouteCtlTar The path to a target has
.1 hange getAddressType changed.
traceRouteCtlTar
getAddress
traceRouteResult
sIpTgtAddrType
traceRouteResult
sIpTgtAddr
1.3.6.1.2.1.81.0 traceRouteTestF traceRouteCtlTar Could not determine the path to
.2 ailed getAddressType a target
traceRouteCtlTar (traceRouteNotifications 2).
getAddress
traceRouteResult
sIpTgtAddrType
traceRouteResult
sIpTgtAddr
1.3.6.1.2.1.81.0 traceRouteTestC traceRouteCtlTar The path to a target has just
.3 ompleted getAddressType been determined.
traceRouteCtlTar
getAddress
traceRouteResult
sIpTgtAddrType
traceRouteResult
sIpTgtAddr
1.3.6.1.4.1.2272 rcVrrpExtTrapSta ifIndex, Specifies a transition state that
.1.206.2.2.1 teTransition rcVrrpExtTrapStat occurs on a particular VRRP
eTransitionType, interface, for a given transition
rcVrrpExtTrapStat cause and type.
eTransitionCause
,
rcVrrpExtOperatio
nsVrId,
rcVrrpTmpOperati
onsPrimaryIpAdd
r,
rcVrrpTmpOperati
onsMasterIpAddr

Traps Reference January 2012 33

Traps reference

OID Notification type Objects Description

1.3.6.1.4.1.2272 rcVrrpExtTrapSta rcVrrpTmpOperati Indicates that the sending agent
.1.206.1.0.1 teTransitionCaus onsMasterIpAddr, is transitioned to Master state. It
e rcVrrpTmpNewM generates the IP address of the
asterReason Master indicating the transition
reason.
1.3.6.1.6.3.1.1.5 coldStart — A coldStart trap signifies that the
.1 SNMPv2 entity, acting in an
agent role, is reinitializing itself
and that its configuration may
have been altered.
1.3.6.1.6.3.1.1.5 warmStart — A warmStart trap signifies that
.2 the SNMPv2 entity, acting in an
agent role, is reinitializing itself
such that its configuration is
unaltered.
1.3.6.1.6.3.1.1.5 linkDown — A linkDown trap signifies that
.3 the sending protocol entity
recognizes a failure in one of the
communication links
represented in the agent's
configuration. TRAP-TYPE
ENTERPRISE snmp
1.3.6.1.6.3.1.1.5 linkUp — A linkUp trap signifies that the
.4 sending protocol entity
recognizes that one of the
communication links
represented in the agent's
configuration has come up.
TRAP-TYPE ENTERPRISE
snmp
1.3.6.1.6.3.1.1.5 authenticationFai — —
.5 lure

34 Traps Reference January 2012

Comments? infodev@avaya.com
Chapter 4: Customer Service

Visit the Avaya Web site to access the complete range of services and support that Avaya provides. Go
to www.avaya.com or go to one of the pages listed in the following sections.

Getting technical documentation

To download and print selected technical publications and release notes directly from the
Internet, go to www.avaya.com/support.

Getting product training

Ongoing product training is available. For more information or to register, you can access the
Web site at www.avaya.com/support. From this Web site, you can locate the Training contacts
link on the left-hand navigation pane.

Getting help from a distributor or reseller

If you purchased a service contract for your Avaya product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller for assistance.

Getting technical support from the Avaya Web site

The easiest and most effective way to get technical support for Avaya products is from the
Avaya Technical Support Web site at www.avaya.com/support.

Traps Reference January 2012 35

Customer Service

36 Traps Reference January 2012

Comments? infodev@avaya.com