Snmp Traps Table - Alcatel-Lucent OmniSwitch AOS Release 6 Manual

SNMP Overview

SNMP Traps Table

The following table provides information on all SNMP traps supported by the switch. Each row includes
the trap name, its ID number, any objects (if applicable), its command family, and a description of the
condition the SNMP agent in the switch is reporting to the SNMP management station. You can generate a
list of SNMP traps that are supported on your switch by using the
No. Trap Name
0 coldStart
1 warmStart
2 linkDown
IfIndex—A unique value, greater than zero, for each interface. It is recommended that values are assigned con-
tiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-ini-
tialization of the entity's network management system to the next re-initialization.
ifAdminStatus—The desired state of the interface. The testing (3) state indicates that no operational packets
can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down (2) state.
As a result of either explicit management action or per configuration information retained by the managed sys-
tem, ifAdminStatus is then changed to either the up (1) or testing (3) states (or remains in the down (2) state).
ifOperStatus—The current operational state of the interface. The testing (3) state indicates that no operational
packets can be passed. If ifAdminStatus is down (2) then ifOperStatus should be down(2). If ifAdminStatus is
changed to up (1) then ifOperStatus should change to up (1) if the interface is ready to transmit and receive net-
work traffic; it should change to dormant (5) if the interface is waiting for external actions (such as a serial line
waiting for an incoming connection); it should remain in the down (2) state if and only if there is a fault that
prevents it from going to the up (1) state; it should remain in the notPresent (6) state if the interface has missing
(typically, hardware) components.
3 linkUp
IfIndex—A unique value, greater than zero, for each interface. It is recommended that values are assigned con-
tiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-ini-
tialization of the entity's network management system to the next re-initialization.
ifAdminStatus—The desired state of the interface. The testing (3) state indicates that no operational packets
can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down (2) state.
As a result of either explicit management action or per configuration information retained by the managed sys-
tem, ifAdminStatus is then changed to either the up (1) or testing (3) states (or remains in the down (2) state).
ifOperStatus—The current operational state of the interface. The testing(3) state indicates that no operational
packets can be passed. If ifAdminStatus is down (2) then ifOperStatus should be down (2). If ifAdminStatus is
changed to up (1), then ifOperStatus should change to up (1) if the interface is ready to transmit and receive net-
work traffic; it should change to dormant (5) if the interface is waiting for external actions (such as a serial line
waiting for an incoming connection); it should remain in the down (2) state if and only if there is a fault that
prevents it from going to the up (1) state; it should remain in the notPresent (6) state if the interface has missing
(typically, hardware) components.
4 authenticationFailure
page 3-10
show snmp trap config
Objects Family
none chassis
none chassis
IfIndex interface
ifAdminStatus
ifOperStatus
ifIndex interface
ifAdminStatus
ifOperStatus
none snmp
OmniSwitch AOS Release 6 Switch Management Guide
Using SNMP
command.
Description
The SNMP agent in the switch is
reinitiating and its configuration
may have been altered.
The SNMP agent in the switch is
reinitiating itself and its configu-
ration is unaltered.
The SNMP agent in the switch
recognizes a failure in one of the
communications links configured
for the switch.
The SNMP agent in the switch
recognizes that one of the com-
munications links configured for
the switch has come up.
The SNMP agent in the switch
has received a protocol message
that is not properly authenticated.
July 2010