November 2013 AOS Release 6.4.6.R01 Release Notes
SNMP Traps
The following table provides a list of AOS Release 6.4.4.R01 SNMP traps managed by the switch.
The SNMP agent in the switch is reinitiating
and itsk configuration may have been altered.
The SNMP agent in the switch is reinitiating
itself and its configuration 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 communications links configured for
The SNMP agent in the switch has received a
protocol message that is not properly
An entConfigChange notification is generated
when a conceptual row is created, modified, or
deleted in one of the entity tables.
The status of the Alcatel-Lucent Mapping
Adjacency Protocol (AMAP) port changed.
This trap is not supported.
The switch notifies the NMS when a significant
event happens that involves the policy manager.
A software trouble report (STR) was sent by an
application encountering a problem during its
A notification that some change has occurred in
the chassis.
An NI status change was detected.
A MAC range overlap was found in the
backplane eeprom.
The SNMP agent has transferred from the
backup state to the master state.
This trap is not supported.
Indicates a device-level threshold was crossed.
Indicates a module-level threshold was crossed.
Indicates a port-level threshold was crossed.
The BGP routing protocol has entered the
established state.
This trap is generated when the BGP router port
has moved from a more active to a less active
This trap is sent when the Ethernet code drops
the link because of excessive errors.
Signifies the loss of adjacency with a neighbor
device. This trap is generated when the neighbor
time expires and the switch has no other
neighbors on the same interface with a lower IP
Page 20 of 80 OmniSwitch 6850E/6855/9000E—Release 6.4.6.R01