CABLETRON-TRAPS: View SNMP OID List / Download MIB

This trap is sent each time a transport connection becomes enabled on this DLSw.

This trap is sent each time a transport connection becomes disabled on this DLSw.

When a port goes from operational to segmented, a trap will be generated. For these purposes, the port state will be sampled every XXX seconds, thus it will be statistically possible to miss oscillating circuits.

When it is detected that a previously segmented port has gone operational, a trap will be generated. This is also sampled, thus a trap may not be generated for each transition.

This trap will be generated when it is determined that a MAU has been attached to the MMAC. This is only appropriate for MIMs that support the concept of a link state.

This trap will be generated when a previously attached MAU is removed or powered down. Again, this is only appropriate for MIM's that support link state.

This trap will be generated when the MMAC detects the existence of a new source address on one of it's ports.

This trap will indicate that the MMAC has not detected a packet generated by this source address within a certain timeout.

This trap will be generated when the MMAC detects that a MIM has been removed.

This trap will generated when the MMAC determines that a new board has been inserted.

This trap will be generated when the active port in a redundant circuit has failed polling. This will indicate the activation of redundancy.

This trap indicates that a new port has been activated in a redundant circuit. This does NOT indicate that this port is usable, but is being tested. If the port fails, a failure trap (above) will be generated.

This trap will be generated when the MMAC executes it's periodic redundancy diagnostics and finds one of the ports in a redundant circuit has failed. This message will not indicate that redundancy has been activated, just that the port has failed and should be fixed before it is needed.

This trap will be generated when the traffic (good packets per time interval) has been exceeded for a particular MIM.

This trap will be generated when packets of the selected error type exceeds a threshold percentage of the good packets for a particular interval for a particular MIM.

This trap will be generated when collisions exceed a threshold percentage of the good packets for a particular interval for a particular MIM.

This trap will be generated when the traffic (good packets per time interval) has been exceeded for a particular port.

This trap will be generated when packets of the selected error type exceeds a threshold percentage of the good packets for a particular interval for a particular port.

This trap will be generated when collisions exceed a threshold percentage of the good packets for a particular interval for a particular port.

This trap indicates that a port has changed from a station port to a trunk port or vice versa.

This trap is generated when a source address other than those locked to a port is seen.

This trap is generated when management intervention has reset a port after a violation has occurred.

This trap is generated when the device detects that the temperature within a MIM has reached a WARM condition.

This trap is generated when the device detects that the temperature within a MIM has reached a HOT condition.

This trap is generated when a power supply's voltage is LOW.

This trap is generated when the device detects that the temperature within a MIM has returned to a NORMAL state.

This trap is generated when all power supplies' voltage have returned to a NORMAL state.

This trap is generated when the device detects that the system fans have failed.

This trap is generated when the device detects that the system fans have returned to normal.

This trap is generated when the broadcast packets (per time interval) have exceeded the threshold for the given board.

This trap is generated when the broadcast packets (per time interval) have exceeded the threshold for the given port.

This trap is generated when the device detects that the power to the EMME is low.

This trap is generated when the device detects that the power to the EMME has returned to normal.

This trap is generated when it is detected that an EPIM has been removed.

This trap is generated when it is detected that an EPIM has been inserted.

This trap will be generated when the traffic (good packets per time interval) has been exceeded for a network.

This trap will be generated when packets of the selected error type exceeds a threshold percentage of the good packets for a particular interval for an entire network.

This trap will be generated when collisions exceed a threshold percentage of the good packets for a particular interval for an entire network.

This trap is generated when the status of the address lock changes for a certain network.

This trap is generated when the broadcast packets (per time interval) have exceeded the threshold for the given repeater.

This trap is generated when a change to the source address locking is detected at the port level.

This trap will generated when the MMAC determines that a new board has been inserted.

This trap is generated when the status of the secure state changes for a specific port.

This trap is generated when network learning is reset. When learning is reset, all secure addresses on each port, within the network, will be deleted and ports will learn source addresses, again.

This trap is generated when port group learning is reset. When learning is reset, all secure addresses on each port, within the port group, will be deleted and ports will learn source addresses, again.

This trap is generated when learning on a port is reset. When learning is reset, all secure addresses on the port will be deleted and the port will learn source addresses, again.

This trap is generated when network learn mode is changed between one-time learn mode and continuous learn mode.

This trap is generated when the port group learn mode is changed between one-time learn mode and continuous learn mode.

This trap is generated when the port learn mode is changed between one-time learn mode and continuous learn mode.

This trap is generated when a port is activated in redundancy due to another port failing.

This trap will be generated when it is detected that an interface port has been inserted.

This trap will be generated when it is detected that an interface port has been removed.

This trap will be generated when it is determined that a port on a strictly bridging interface (not a 'repeater') has been connected to a LAN. This is only appropriate for ports that support the concept of a link state.

This trap will be generated when a previously attached bridging port has been disconnected from a LAN. This is only appropriate for ports that support the concept of a link state.

This trap is sent when a stations port's link state turns on while the management state of the port is Enabled.

This trap is sent when a stations port's link state turns off while the management state of the port is Enabled.

This trap is sent when a board enters the ring speed fault state due to a station or ring port attaching to the board as a different speed than the board is configured for.

This trap is sent when a board leaves the ring speed fault state.

This trap is sent when a ring port wraps when its management state is Active, without regard for the selected type of the ring port.

This trap is sent when a ring port unwraps when its management state is Active, without regard for the selected type of the ring port.

This trap occurs when a Beacon is detected on the ring while the ring is in the Operational state, or when the Beacon contains different information than the last Beacon received.

This trap occurs when a ring returns to the Operational state.

This trap is sent when a new station address is added to the security allowed list

This trap is sent when a station is rejected from the ring with a REMOVE MAC command sent by the ring security.

This trap is sent when the TRMM has built a new station map.

This trap is sent after a fault recovery condition has been corrected, and reports that a port was removed in the process of correcting the condition.

This trap is sent after a fault recovery condition has been corrected, and reports that a board was bypassed in the process of correcting the condition.

This trap is sent when a port link state turns on and the port's management state is Disabled.

This trap is sent when a port link state turns off and the port's management state is Disabled.

This trap is sent when the ring has oscillated several times within a short amount of time. The ring is considered oscillating if it has failed a short time after recovering.

This trap is sent when ring purge errors have exceeded the specified threshold value.

This trap is sent when Active Monitor errors have exceeded the specified threshold value.

This trap is sent when Token errors have exceeded the specified threshold value.

This trap is sent when claim tokens have exceeded the specified threshold value.

This trap is sent when the Lost Frame count has exceeded the specified threshold value.

This trap is sent when the Beacon State count has exceeded the specified threshold value.

This trap is sent when the frame count has exceeded the specified threshold value.

This trap is sent when the line errors have exceeded the specified threshold value for the station.

This trap is sent when the Lost internal errors have exceeded the specified threshold value for the station.

This trap is sent when the Lost burst errors have exceeded the specified threshold value for the station.

This trap is sent when address/copied errors have exceeded the specified threshold value for the station.

This trap is sent when receiver congestion errors have exceeded the specified threshold value for the station.

This trap is sent when a station breaks through security and cannot be removed from the ring.

This trap is generated when a port enters the ring speed fault state due to a station or ring port attaching to the port at a different speed than the port is configured for.

This trap is generated when a port leaves the ring speed fault state.

This trap is sent when a stations port's link state turns on while the management state of the port is Enabled.

This trap is sent when a stations port's link state turns off while the management state of the port is Enabled.

This trap is sent when a 'active NON-93 series' board enters the ring speed fault state due to a station or ring port attaching to the board as a different speed than the board is configured for.

This trap is sent when a board leaves the ring speed fault state.

This trap is sent when a ring port wraps when its management state is Active, without regard for the selected type of the ring port.

This trap is sent when a ring port unwraps when its management state is Active, without regard for the selected type of the ring port.

This trap occurs, if beacon recovery is enabled, when Beaconing, Ring Purging or Claim Tokens are detected on the ring while the ring is in the Operational state, or when the Beacon contains different information than the last Beacon received.

This trap occurs when a ring returns to the Operational state.

This trap is sent when a new station is added to the security allowed list.

This trap is sent when a station is rejected from the ring with a REMOVE MAC command sent by the ring security.

This trap is sent when a station breaks through security and cannot be removed from the ring.

This trap is sent when a ring security break has been corrected, and reports that a port was removed (disabled) in the process of correcting the condition.

This trap is sent after a fault recovery condition has been corrected, and reports that a port was removed in the process of correcting the condition.

This trap is sent after a fault recovery condition has been corrected, and reports that a port group was bypassed in the process of correcting the condition.

This trap is sent after a fault recovery condition has been corrected, and reports that a board was bypassed in the process of correcting the condition.

This trap is sent when a port link state turns on and the port's management state is Disabled.

This trap is sent when a port link state turns off and the port's management state is Disabled.

This trap is sent when ring purge errors have exceeded the specified threshold value.

This trap is sent when Active Monitor errors have exceeded the specified threshold value.

This trap is sent when Token errors have exceeded the specified threshold value.

This trap is sent when claim tokens have exceeded the specified threshold value.

This trap is sent when the Lost Frame count has exceeded the specified threshold value.

This trap is sent when the frame count has exceeded the specified threshold value.

This trap is sent when the line errors have exceeded the specified threshold value for the station.

This trap is sent when the Lost internal errors have exceeded the specified threshold value for the station.

This trap is sent when the Lost burst errors have exceeded the specified threshold value for the station.

This trap is sent when address/copied errors have exceeded the specified threshold value for the station.

This trap is sent when receiver congestion errors have exceeded the specified threshold value for the station.

This trap is generated when a port enters the ring speed fault state due to a station or ring port attaching to the port at a different speed than the port is configured for.

This trap is generated when a port leaves the ring speed fault state.

This trap is generated when a TPIM is installed.

This trap is generated when a TPIM is removed.

This trap is sent each time the neighbor notification (ring poll) does not complete.

This trap is sent when the ring has oscillated (in and out of beaconing) when beacon recovery is enabled. The ring is considered oscillating if it has failed 21 secs after recovering from the previous.

This trap is sent after the management module successfully recovered the Ring Poll Failure condition.

This trap is sent after the management module has failed to recover the Ring Poll Failure condition. The interesting information includes the interface number and the MAC address of the last successful ring poll station.

This trap indicates that a SPVP was rerouted. The variables indicates the address of a rerouted spvp, the time stamp of when rerouting occurred, and the cause of rerouting. The cause codes are as follows: Unallocated (unassigned) number = 1 No route to specified transit network = 2 No route to destination = 3 Normal call clearing = 16 User busy = 17 No user responding = 18 Call rejected = 21 Number changed = 22 User rejects all calls with calling line identification restriction (CLIR) = 23 Destination out of order = 27 Invalid number format (address incomplete) = 28 Response to STATUS ENQUIRY = 30 Normal, unspecified = 31 Requested VPCI/VCI not available = 35 VPCI/VCI assignment failure = 36 User cell rate not available = 37 Network out of order = 38 Temporary failure = 41 Access information discarded = 43 No VPCI/VCI available = 45 Resource unavailable, unspecified = 47 Quality of Service unavailable = 49 Bearer capability not authorized = 57 Bearer capability not presently available = 58 Service or option not available, unspecified = 63 Bearer capability not implemented = 65 Unsupported combination of traffic parameters = 73 AAL parameters cannot be supported = 78 Invalid call reference value = 81 Identified channel does not exist = 82 Incompatible destination = 88 Invalid endpoint reference = 89 Invalid transit network selection = 91 Too many pending add party requests = 92 Mandatory information element missing = 96 Message type non-existent or not implemented = 97 Information element non existent or not implemented = 99 Invalid information element contents = 100 Message not compatible with call state = 101 Recovery on timer expiry = 102 Incorrect message length = 104 Protocol error, unspecified = 111

This trap indicates that a SPVC was rerouted. The variables indicates the address of a rerouted spvc, the time stamp of when rerouting occurred, and the cause of rerouting. The cause codes are as follows: Unallocated (unassigned) number = 1 No route to specified transit network = 2 No route to destination = 3 Normal call clearing = 16 User busy = 17 No user responding = 18 Call rejected = 21 Number changed = 22 User rejects all calls with calling line identification restriction (CLIR) = 23 Destination out of order = 27 Invalid number format (address incomplete) = 28 Response to STATUS ENQUIRY = 30 Normal, unspecified = 31 Requested VPCI/VCI not available = 35 VPCI/VCI assignment failure = 36 User cell rate not available = 37 Network out of order = 38 Temporary failure = 41 Access information discarded = 43 No VPCI/VCI available = 45 Resource unavailable, unspecified = 47 Quality of Service unavailable = 49 Bearer capability not authorized = 57 Bearer capability not presently available = 58 Service or option not available, unspecified = 63 Bearer capability not implemented = 65 Unsupported combination of traffic parameters = 73 AAL parameters cannot be supported = 78 Invalid call reference value = 81 Identified channel does not exist = 82 Incompatible destination = 88 Invalid endpoint reference = 89 Invalid transit network selection = 91 Too many pending add party requests = 92 Mandatory information element missing = 96 Message type non-existent or not implemented = 97 Information element non existent or not implemented = 99 Invalid information element contents = 100 Message not compatible with call state = 101 Recovery on timer expiry = 102 Incorrect message length = 104 Protocol error, unspecified = 111

This trap is generated for diagnostic purposes.

This trap is generated when the status of the bridge changes.

This trap is generated when the acquired portion of the bridge's filtering database is full.

This Trap is generated when Front Panel Redundancy changes the active port.

This trap is generated when night vision turns off or on. If power to the device is lost, this trap is sent with a value of 0, indicating that power has been lost but the device is running on 'night vision'. If power is not restored within 10 minutes, the device shuts down completely. If power is restored in that time frame, the trap is sent with a value of 1 indicating as such.

A LostContact signifies that a the Cabletron hub has lost contact with the destination IP address host/device. This trap is only sent at the 'trap-wait' intervals. Note that this trap indicates a poll failure, not a threshold failure. Threshold alarms are generated independently. The snmpPollDestination indicates the lost device.

This trap signifies that an OID value/threshold comparison has failed. The snmpOIDObject specifies which Object Identifier and instance (destination IP address, owner IP address, and sequence number) was used to trigger the alarm condition. The snmpOIDDestination indicates the node address that failed the OID poll.

A ReestabContact signifies that a the Cabletron hub has reestablished contact with the destination IP address host/device. This trap is sent immediately after contact has been reestablished.

This trap is generated when the configured broadcast threshold on a port is reached and will include the slot number and port number the threshold was reached on.

This trap is generated when the operational state of the LAN Emulation Client has changed.

This trap is generated for FDDI port connection state changes. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated whenever there is an increase in the number of SMT master ports.

This trap is generated anytime there is a decrease in the number of SMT master ports.

This trap is generated for every action against a FDDI port. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when the long term link error rate, fddimibPORTLerEstimate, crosses the fddimibPORTLerAlarm threshold. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when a FDDI module is bypassed on the FNB.

This trap is generated when a FDDI module is inserted on the FNB.

This trap is generated when there is a change in the FDDI ring state. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when there is a change in the insertion of the MAC to the FDDI ring. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when there is a change in the attachment configuration for the station or concentrator. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when there is a change in the attachment configuration for the station or concentrator. It provides information additional to fddiSMTCFState, twisted ring conditions in particular. The variables are found in the Cabletron SMT MIB.

This trap is generated when the frame error ratio exceeds the frame error threshold, fddimibMACFrameErrorThreshold. The variables are found in IETF FDDI MIB RFC-1512.

This trap is generated when the SMT detects a duplicate MAC address on the ring.

This trap is generated when any change occurs in the contLogicalEntryTable group of the container MIB.

This trap is generated when any change occurs to contPhysicalEntryTable group of the container MIB.

This trap is generated for changes to IP event log.

This trap is generated whenever an entry is made to the router IPX event log for where nwIpEventSeverity has a value of highest(1).

This trap is generated whenever an entry is made to the router Dec Net IV event log.

This trap is generated whenever an entry is made to the router Apple Talk event log.

This trap is generated whenever an entry is made to the router APPN event log.

When a link station becomes active, a trap is generated. nwAppnFwdLsName identifies the link station name.

When a link station is deactivated, a trap is generated. nwAppnFwdLsName identifies the link station name, nwAppnFwdLsAdjCpName identifies the fully qualified CP name of the adjacent node and nwAppnFwdLsAdjCpType is the type of that node.

This trap is generated when a new user enters the SFPS fabric.

This trap is generated when one of 6 violation types have occurred. 1 UserLock 2 RestrictedPort 3 IPNotLearned 4 IPInvalid 5 RestrictedMobility 6 UserLockSamePort

This trap is generated when a user (source MAC address) has surpassed the Source Blocker thresholds and is being blocked from sending traffic on the network.

A destination address has been unresolvable past the thresholds and is now being flood suppressed (only 1 per X seconds will pass).

This trap is generated when a port has entered standby. There are different standby states: 9 STAND_BY (manually set) 14 STAND_BY_FCL (one way neighbor) 15 STAND_BY_LOOPED (self originated Hello seen on port) 16 STAND_BY_RTA (redundant access port is standby/backup

This trap is generated when a port that was in standby is now not in standby. Most common is that either a one-way neighbor situation is gone or a standby RA port is now primary.

This trap is generated when the SOS Gateway agent detects that a third party NMS has added a new map to its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has deleted a map from its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has changed an attribute of a map in its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has opened a map.

This trap is generated when the SOS Gateway agent detects that a third party NMS has closed a map.

This trap is generated when the SOS Gateway agent detects that a third party NMS has added a new element to its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has deleted an element from its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has changed an attribute of an element in its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has added a new symbol to its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has deleted a symbol from its database.

This trap is generated when the SOS Gateway agent detects that a third party NMS has changed an attribute of a symbol in its database.

This trap is generated when the device detects that the power supply has been installed.

This trap is generated when the device detects that the power supply has been removed.

This trap is generated when the device detects that the power supply has returned to normal.

This trap is generated when the device detects that the power supply has failed.

This trap is generated when the device detects that the power supply is in the redundant state.

This trap is generated when the device detects that the power supply is not in the redundant state.

This trap is generated when a module is inserted.

This trap is generated when a module is removed.

This trap is generated in the event of an AC utility line failure

This trap is generated when the UPS switches back to line, and only if the aPCLineFail trap was issued first

This trap is generated in the event that the UPS' battery is found to be low

This trap is generated when the UPS' battery has charged above the low-battery point, and only if the aPCLowBattery trap was issued first

This trap is generated in the event that the UPS has entered an abnormal condition, such as an overload or trip on low battery. This trap is also sent, when the UPS is first turned on.

This trap is generated when the UPS has recovered from an abnormal condition, and only if the aPCAbnormalCondition trap was issued first

This trap is generated in the event that the UPS has been ordered to shut itself, or the load, off over the serial line.

This trap is generated when the term power bus is over voltage.

This trap is generated when the term power bus is under voltage.

This trap is generated when the term power bus is at an acceptable voltage. It will only be sent out after a trap was sent to say that the term voltage was under or over.

This trap is generated because the chassis is hot.

This trap is generated because the chassis is warm.

This trap is generated because the chassis is cool.

This trap is generated because the chassis is cold.

This trap is generated because the chassis has returned to normal after being warm, hot, cool or cold.

This trap is generated when the chassis's temperature sensor is broken.

This trap is generated when the chassis determines there is a humidity static risk.

This trap is generated when the chassis determines the humidity has returned to normal after being moist or static risk.

This trap is generated when the chassis determines there is a humidity moist risk.

This trap is generated when the chassis determines the humidity sensor is broken.

This trap is generated when the INV termination has been installed for module 1.

This trap is generated when the INV termination is faulty for module 1.

This trap is generated when the INV termination has been removed for module 1.

This trap is generated when the INV termination (module 1) has returned to normal after already sending a trap to say it was faulty.

This trap is generated when the INV termination has been installed for module 2.

This trap is generated when the INV termination is faulty for module 2.

This trap is generated when the INV termination has been removed for module 2.

This trap is generated when the INV termination (module 2) has returned to normal after already sending a trap to say it was faulty.

This trap is generated when the chassis detects a fan failure.

This trap is generated because a board is hot and the board has shut itself down.

This trap is generated because a board is warm.

This trap is generated because a board is cool.

This trap is generated because a board is cold.

This trap is generated because a board has returned to normal after being warm or hot.

This trap is generated when the board's temperature sensor is broken.

This trap is generated because a board is hot.

This trap is generated because a board's relative temp is warm.

This trap is generated because a board's relative temp has returned to normal after being warm or hot.

This trap is generated because a board's relative temp is hot but it cannot shutdown. It will need to be turned off remotely.

This trap is generated when the board's relative temperature is hot and is being powered off.

This trap is generated because a board's relative temp is warm. The fans are on MAX.

This trap is generated because a board's relative temp has returned to normal after being warm or hot. The fans are on MAX.

This trap is generated because a board's relative temp is hot but it cannot shutdown. It will need to be turned off remotely. The fans are on MAX.

This trap is generated when the board's relative temperature is hot and is being powered off. The fans are on MAX.

This trap is generated because a boards input voltage is over max.

This trap is generated because a boards input voltage is under minimum.

This trap is generated because a board input voltage has returned to normal after being over or under.

This trap is generated because a board output voltage is over MAX.

This trap is generated because a board output voltage is under MIN.

This trap is generated because a board output voltage has returned to normal after being over or under.

This trap is generated because a boards auxiliary voltage is over MAX.

This trap is generated because a board auxiliary voltage is under MIN.

This trap is generated because a board auxiliary voltage has returned to normal after being over or under.

This trap is generated because a board input current is over MAX. The power supply has therefore been shutdown.

This trap is generated because a boards output current is over MAX. The power supply has therefore been shutdown.

This trap is generated because a board input current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because a board output current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because the board is being powered off due to outside intervention.

This trap is generated because the board is being powered on due to outside intervention.

This trap is generated because the board is being reset due to outside intervention.

This trap is generated because the board power has been powered on.

This trap is generated because the board power has been powered off.

This trap is generated because the board has been reset.

This trap is generated because the board has been shutdown remotely due to being over current.

This trap is generated because the board has been shutdown remotely due to power conservation.

This trap is generated because the board has been shutdown remotely due to it's temperature.

This trap is generated because the board has had an unauthorized front panel disable.

This trap is generated because the board has been disabled through the front panel.

This trap is generated because the board has had an unauthorized front panel enable.

This trap is generated because the board has been enabled through the front panel.

This trap is generated because the board has had an unauthorized front panel reset.

This trap is generated because the board has been reset through the front panel.

This trap is generated because the board's A/D converter is broken.

This trap is generated because of a board PIC failure.

This trap is generated because the board PIC is now OK. This trap will only be sent AFTER a PIC failure trap has been generated.

This trap is generated when the board LLAP address already exists in this chassis.

This trap is generated because of a board mailbox failure.

This trap is generated because the board mailbox is now OK.

This trap is generated because an AC power supply is hot and the power supply has shut itself down.

This trap is generated because an AC power supply is warm.

This trap is generated because an AC power supply has returned to normal after being warm or hot.

This trap is generated because an AC power supply has returned to normal after being shutdown remotely. It will need to be powerOn remotely.

This trap is generated when the AC power supply's temperature sensor is broken.

This trap is generated because an AC power supply is hot.

This trap is generated because an AC power supply input voltage is over max.

This trap is generated because an AC power supply input voltage is under minimum.

This trap is generated because an AC power supply input voltage has returned to normal after being over or under.

This trap is generated because an AC power supply system voltage is over MAX.

This trap is generated because an AC power supply system voltage is under MIN.

This trap is generated because an AC power supply system voltage has returned to normal after being over or under.

This trap is generated because an AC power supply logic voltage is over MAX.

This trap is generated because an AC power supply logic voltage is under MIN.

This trap is generated because an AC power supply logic voltage has returned to normal after being over or under.

This trap is generated because an AC power supply term voltage is over MAX.

This trap is generated because an AC power supply term voltage is under MIN.

This trap is generated because an AC power supply term voltage has returned to normal after being over or under.

This trap is generated because an AC power supply logic current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an AC power supply term current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an AC power supply input current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply system current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply logic current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply term current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply logic sense current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply term sense current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an AC power supply input current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an AC power supply system current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an AC power supply logic current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an AC power supply term current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because the AC power supply is being powered off due to outside intervention.

This trap is generated because the AC power supply system power has been powered on.

This trap is generated because the AC power supply system power has been powered off.

This trap is generated because the AC power supply logic power has been powered on.

This trap is generated because the AC power supply logic power has been powered off.

This trap is generated because the AC power supply term power has been powered on.

This trap is generated because the AC power supply term power has been powered off.

This trap is generated because the AC power supply has been shutdown remotely due to being over current.

This trap is generated because the AC power supply has been shutdown remotely due to power conservation.

This trap is generated because the AC power supply A/D converter is broken.

This trap is generated because of an AC power supply PIC failure.

This trap is generated because the AC power supply PIC is now OK. This trap will only be sent AFTER a PIC failure trap has been generated.

This trap is generated when the AC power supply LLAP address already exists in this chassis.

This trap is generated because of an AC power supply fan failure.

This trap is generated because the AC power supply fan is now OK. This trap will only be sent AFTER a fan failure trap has been generated.

This trap is generated because an DC power supply is hot and the power supply has shut itself down.

This trap is generated because an DC power supply is warm.

This trap is generated because an DC power supply has returned to normal after being warm or hot.

This trap is generated because an DC power supply has returned to normal after being shutdown remotely. It will need to be powerOn remotely.

This trap is generated when the DC power supply's temperature sensor is broken.

This trap is generated because an DC power supply is hot.

This trap is generated because an DC power supply input voltage is over max.

This trap is generated because an DC power supply input voltage is under minimum.

This trap is generated because an DC power supply input voltage has returned to normal after being over or under.

This trap is generated because an DC power supply system voltage is over MAX.

This trap is generated because an DC power supply system voltage is under MIN.

This trap is generated because an DC power supply system voltage has returned to normal after being over or under.

This trap is generated because an DC power supply logic voltage is over MAX.

This trap is generated because an DC power supply logic voltage is under MIN.

This trap is generated because an DC power supply logic voltage has returned to normal after being over or under.

This trap is generated because an DC power supply term voltage is over MAX.

This trap is generated because an DC power supply term voltage is under MIN.

This trap is generated because an DC power supply term voltage has returned to normal after being over or under.

This trap is generated because an DC power supply logic current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an DC power supply term current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an DC power supply input current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply system current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply logic current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply term current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply logic sense current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply term sense current is over MAX. The power supply has therefore been shutdown.

This trap is generated because an DC power supply input current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an DC power supply system current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an DC power supply logic current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because an DC power supply term current is over MAX. The ability of the power supply to turn itself off has been disabled therefore outside intervention is needed.

This trap is generated because the DC power supply is being powered off due to outside intervention.

This trap is generated because the DC power supply system power has been powered on.

This trap is generated because the DC power supply system power has been powered off.

This trap is generated because the DC power supply logic power has been powered on.

This trap is generated because the DC power supply logic power has been powered off.

This trap is generated because the DC power supply term power has been powered on.

This trap is generated because the DC power supply term power has been powered off.

This trap is generated because the DC power supply has been shutdown remotely due to being over current.

This trap is generated because the DC power supply has been shutdown remotely due to power conservation.

This trap is generated because the DC power supply A/D converter is broken.

This trap is generated because of an DC power supply PIC failure.

This trap is generated because the DC power supply PIC is now OK. This trap will only be sent AFTER a PIC failure trap has been generated.

This trap is generated when the DC power supply LLAP address already exists in this chassis.

This trap is generated because of an DC power supply fan failure.

This trap is generated because the DC power supply fan is now OK. This trap will only be sent AFTER a fan failure trap has been generated.

This trap is generated because the power supply A/D converter is broken.

This trap is generated because of a power supply PIC failure.

This trap is generated because the power supply PIC is now OK. This trap will only be sent AFTER a PIC failure trap has been generated.

This trap is generated when the power supply LLAP address already exists in this chassis.

This trap is generated for each and every time the chassis ambient temperature crosses over a threshold value of either one of the chassis set thresholds chEnvAmbientHot, chEnvAmbientWarm, chEnvAmbientCool, or chEnvAmbientCold to another. This trap is also sent when the chassis temperature sensor is detected to be broken or not supported.

This trap is generated for each and every time the chassis humidity crosses a threshold value of either chEnvHumidityMoist, or chEnvHumidityDry, or when the humidity sensor is detected to be broken or not supported.

This trap is generated for each and every time the board temperature crosses over a threshold value of either one of the board set thresholds boardEnvTempHot, boardEnvTempWarm, boardEnvTempCool, or boardEnvTempCold to another. This trap is also sent when the board temperature sensor is detected to be broken or not supported.

This trap is generated for each and every time the board temperature relative to the chassis ambient temperature crosses a threshold value of either boardEnvTempRelHot, or boardEnvTempRelWarm. This trap is also sent when either temperature sensor located on the board or on the chassis is detected to be broken or not supported.

This trap is generated for each and every time the board temperature relative to the chassis ambient temperature crosses a threshold value of either boardEnvTempMaxFanRelHot, or boardEnvTempMaxFanRelWarm when all fans in the chassis are operating at there maximum speed. This trap is also sent when either temperature sensor located on the board or on the chassis is detected to be broken or not supported.

This trap is generated for each and every time the chassis main voltage rail deviates and causes the chPowerMainVoltageStatus to switch state from powerOK(1), overCurrent(2), overVoltage(3), or underVoltage(4) to another.

This trap is generated for each and every time the chassis diag voltage deviates and causes the chPowerDiagVoltageStatus to switch state from powerOK(1), overCurrent(2), overVoltage(3), or underVoltage(4) to another.

This trap is generated for each and every time the module's termination unit changes state and causes the termPowerStatus to switch from any states to either powerOK(1), overVoltage(3), or underVolatge(4) state.

This trap is generated for each and every time the module's power line voltage deviates and causes the boardPowerStatus to switch from any states to either powerOK(1), overVoltage(4), or underVoltage(5) state.

This trap is generated for each and every time the module's front panel button changes state and causes the termPowerModule1Status to switch state from either one of normal(1), iNBaFault(2), iNBbFault(3), fault(4), termModuleNotInstalled(5) to another.

This trap is generated for each and every time the module's front panel button changes state and causes the termPowerModule2Status to switch state from either one of normal(1), iNBaFault(2), iNBbFault(3), fault(4), termModuleNotInstalled(5) to another.

This trap is generated for each and every time the chassis fan changes over its status from either one value unknown(1), normal(2), testing(3), slow(4), inoperative(5), or off(6) to another.

This trap is generated for each and every time the module's power line current deviates and causes the boardPowerStatus to switch from any states to powerOK(1), or overCurrent(3) state.

This trap is generated for each and every time the module's front panel button state changes, it is caused when the boardPowerLocalStatus switching state from either one of resetRequest(1), powerDownRequest(2), powerOnRequest(3), or normal(4) to another.

This trap is generated for each and every time the module's DC-DC converter power supply voltage deviates and causes the boardPowerOperationalStatus to switch state from powerOn(1), powerOff(2), reset(3), overVoltage(4), underVoltage(5), overCurrent(6), overCurrentShutdown(7), temperatureShutdown(8), remotePowerOff(9), powerConservationShutdown(10), or frontPanelPowerOff(11) to another.

This trap is generated for each and every time the power supply temperature crosses over a threshold value of either one of the power supply set thresholds psEnvTempHot, psEnvTempWarm, psEnvTempCool, or psEnvTempCold to another. This trap is also sent when the power supply temperature sensor is detected to be broken or not supported.

This trap is generated for each and every time the power supply fan changes over its status from either one value unknown(1), normal(2), testing(3), slow(4), inoperative(5), or off(6) to another.

This trap is generated for each and every time the module's power line voltage deviates and causes the psPowerStatus to switch from any states to either powerOK(1), overVoltage(4), or underVoltage(5) state.

This trap is generated for each and every time the module's power line current deviates and causes the psPowerStatus to switch from any states to powerOK(1), or overCurrent(3) state.

This trap is generated for each and every time the power supply power line changes state from one operational mode to another switching between powerOn(1) and powerOff(2).

This trap is generated for each and every time the module's DC-DC converter power supply voltage deviates and causes the psPowerOperationalStatus to switch state from either one of powerOn(1), powerOff(2), reset(3), overVoltage(4), underVoltage(5), overCurrent(6), overCurrentShutdown(7), temperatureShutdown(8), or remotePowerOff(9) to another.

This trap is generated when an MMACplus card is inserted in the chassis.

This trap is generated when an MMACplus card is removed from the chassis.

This trap is generated when an MMACplus power supply is inserted in the chassis.

This trap is generated when an MMACplus power supply is removed from the chassis.

This trap is generated when an MMACplus power supply has a redundant power supply

This trap is generated when an MMACplus power supply has no redundant power supply

This trap is generated when an MMACplus board is transitioning to a normal state from a fault state

This trap is generated when an MMACplus power supply is not operational

This trap is generated in the event of an AC utility line failure.

This trap is generated when the UPS switches back to line, and only if the upsLineFail trap was issued first.

This trap is generated in the event that the UPS's battery is found to be low.

This trap is generated when the UPS's battery has charged above the low-battery point, and only if the upsLowBattery trap was issued first.

This trap is generated in the event that the UPS has entered an abnormal condition, such as an overload or trip on low battery. This trap is also sent when the UPS is first turned on.

This trap is generated when the UPS has recovered from an abnormal condition, and only if the upsAbnormalCondition trap was issued first.

This trap is generated in the event that the UPS has been ordered to shut itself, or the load, off over the serial line.

This trap is generated when the UPS's battery test has determined that a UPS battery is unable to retain adequate charge. This trap will be generated every five hours until a new battery test is run or the UPS is turned off.

This trap is generated when the External Measurement Unit has detected that an ambient temperature or humidity limit extreme has been exceeded, or that one of the contact closure inputs has changed from the selected `normal' state. In the case of multiple alarms, a trap is generated for every alarm condition detected. In addition, the trap is sent every two minutes whenever an alarm condition exists. It is discontinued when all alarm conditions are reset. This trap is sent only for alarm states that have been enabled.

This trap is generated when a new NVMP trap is sent that does not have an SNMP counterpart.

This trap will be generated when the active port, on a physical ATM interface that has redundancy enabled, has failed (become quiet).

This trap indicates that a new port has been activated on a physical ATM interface that has redundancy enabled. This does not indicate that this port is usable, but that it is being tested as a possible replacement.

This trap will be generated when the phyRedundIfTestTOD or the phyRedundIfPerformTest has tested a port and determined that it is not usable. The port should be fixed prior to it being needed.

This trap will be generated when redundancy finds that the primary port as designated be PhyRedundIfPrimaryPort is usable but cannot be used because PhyRedundIfPrimaryRevert is set to manual (2). This trap is generated only when redundancy is enabled (PhyRedundIfStatus is enable (1)) and the active port fails.

This trap signifies that the agent has detected the CTM operational. Connection set maps are allowed through the switch

This trap signifies that the agent has detected the CTM unoperational. A list of Cross Connect Ids will be sent indicating connections that need to be removed.

This trap signifies that the agent has detected a change in the operational status to down. A list of VC cross connections will be sent to be remapped.

This trap signifies that the agent has detected a change in the operational status to down. A list of VP cross connections will be sent to be remapped.

This trap signifies that the agent has detected a neighbor switch on a port.

This trap signifies that the agent has detected a lost neighbor switch on a port.

SPVC Call Failures.

Allocated bandwidth for this port has exceeded the allocBwThresholdHiFwd.

Allocated bandwidth for this port has exceeded the allocBwThresholdHiRev.

Allocated bandwidth for this port is below the allocBwThresholdLoFwd.

Allocated bandwidth for this port is below the allocBwThresholdLoRev.

The total of all the aggregate peak cell rates for the VCs using this port exceeds the physical bandwidth of the port in the forward direction.

The total of all the aggregate peak cell rates for the VCs using this port exceeds the physical bandwidth of the port in the reverse direction.

The peak allocated bandwidth has exceeded the peakBwTholdFwd value.

The peak allocated bandwidth has exceeded the peakBwTholdRev value.

Count of currently active constant bit rate connections exceeding the CBRConnectionCountTholdHiFwd threshold.

Count of currently active CBR connections exceeding the CBRConnectionCountTholdHiRev threshold.

Count of currently active CBR connections exceeding the CBRConnectionCountTholdLoFwd threshold.

Count of currently active CBR connections exceeding the CBRConnectionCountTholdLoRev threshold.

Bandwidth currently allocated which CBR exceeds the CBRAllocatedBwTholdHiFwd threshold.

Bandwidth currently allocated which CBR exceeds the CBRAllocatedBwTholdHiRev threshold.

Bandwidth currently allocated which CBR exceeds the CBRAllocatedBwTholdLoFwd threshold.

Bandwidth currently allocated which CBR exceeds the CBRAllocatedBwTholdLoRev threshold.

Count of currently active variable bit rate connections exceeding the VBRConnectionCountTholdHiFwd threshold.

Count of currently active VBR connections exceeding the VBRConnectionCountTholdHiRev threshold.

Count of currently active VBR connections exceeding the VBRConnectionCountTholdLoFwd threshold.

Count of currently active VBR connections exceeding the VBRConnectionCountTholdLoRev threshold.

Bandwidth currently allocated which VBR exceeds the VBRAllocatedBwTholdHiFwd threshold.

Bandwidth currently allocated which VBR exceeds the VBRAllocatedBwTholdHiRev threshold.

Bandwidth currently allocated which VBR exceeds the VBRAllocatedBwTholdLoFwd threshold.

Bandwidth currently allocated which VBR exceeds the VBRAllocatedBwTholdLoRev threshold.

Count of currently active available bit rate connections exceeding the ABRConnectionCountTholdHiFwd threshold.

Count of currently active ABR connections exceeding the ABRConnectionCountTholdHiRev threshold.

Count of currently active ABR connections exceeding the ABRConnectionCountTholdLoFwd threshold.

Count of currently active ABR connections exceeding the ABRConnectionCountTholdLoRev threshold.

Bandwidth currently allocated which ABR exceeds the ABRAllocatedBwTholdHiFwd threshold.

Bandwidth currently allocated which ABR exceeds the ABRAllocatedBwTholdHiRev threshold.

Bandwidth currently allocated which ABR exceeds the ABRAllocatedBwTholdLoFwd threshold.

Bandwidth currently allocated which ABR exceeds the ABRAllocatedBwTholdLoRev threshold.

Count of currently active unavailable bit rate connections exceeding the UBRConnectionCountTholdHiFwd threshold.

Count of currently active UBR connections exceeding the UBRConnectionCountTholdHiRev threshold.

Count of currently active UBR connections exceeding the UBRConnectionCountTholdLoFwd threshold.

Count of currently active UBR connections exceeding the UBRConnectionCountTholdLoRev threshold.

Bandwidth currently allocated which UBR exceeds the UBRAllocatedBwTholdHiFwd threshold.

This trap is generated when the operational state of the LAN Emulation Client has changed.

Bandwidth currently allocated which UBR exceeds the UBRAllocatedBwTholdLoFwd threshold.

Bandwidth currently allocated which UBR exceeds the UBRAllocatedBwTholdLoRev threshold.

Bandwidth currently allocated which UBR exceeds the UBRAllocatedBwTholdHiRev threshold.

This trap will be generated when an entity detects that a module has become operational.

This trap will be generated when an entity detects that a module is no longer operational.