Copyright |
© Ericsson AB 2009–2011. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. | ||||||
Disclaimer |
The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. | ||||||
Trademark List |
|

1 SNMP MIB Notifications
The SmartEdgerouter supports the notifications for Internet Engineering Task Force (IETF) standard Management Information Bases (MIBs) and enterprise MIBs.
For a list of Standard SNMP MIBs supported by the SmartEdge router, see Standard SNMP MIBs.
- Note:
- Simple Network Management Protocol (SNMP) examples in this document utilize the open source tool Net-SNMP. Depending on the product you use to monitor the network, the examples may appear different from your system.
This document applies to both the Ericsson SmartEdge® and SM family routers. However, the software that applies to the SM family of systems is a subset of the SmartEdge OS; some of the functionality described in this document may not apply to SM family routers.
For information specific to the SM family chassis, including line cards, refer to the SM family chassis documentation.
For specific information about the differences between the SmartEdge and SM family routers, refer to the Technical Product Description SM Family of Systems (part number 5/221 02-CRA 119 1170/1) in the Product Overview folder of this Customer Product Information library.
1.1 Setting up SNMP Alarm Models for Notifications
ALARM-MIB is used to create alarm models that specify the alarm types and states to raise for existing notifications.
To configure an SNMP alarm model, do the following:
- Use the snmp alarm model command to enter the SNMP alarm model command mode.
The SNMP alarm model includes the following attributes:
- Review the output of the following show commands, which
display information about SNMP alarm models:
- show snmp alarm model : Displays information about each alarm model.
- show snmp alarm active : Displays information about active alarm models.
- show snmp alarm cleared: Displays information about cleared alarm models.
- show snmp alarm stats: Displays general statistics about all alarm models, including how many have been configured.
- Enable debugging for SNMP alarm models using the debug snmp mib alarm CLI command.
2 AAA Notifications
Table 1 lists notifications generated by the router to indicate Authentication, Authorization and Accounting (AAA) notifications.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity(1) |
Related Events and Commands |
---|---|---|---|---|---|
rbnRadiusAcctStateChange 1.3.6.1.4.1.2352.2.32.0.2 RBN-RADIUS-MIB |
The system sends out this notification when a RADIUS accounting server transitions to the down state or when a RADIUS server transitions to the up state(2) Cause: The connection to the RADIUS server is established (cleared) or lost (raised). |
Ensure that the correct RADIUS configuration appears and that IP and link connectivity is available and free of errors between the SER and the RADIUS server. |
Context |
Warning |
Event: None Command: None |
rbnRadiusAuthStateChange 1.3.6.1.4.1.2352.2.32.0.1 RBN-RADIUS-MIB |
The system sends out this notification when a RADIUS authorization server transitions to the down state or when a RADIUS server transitions to the up state(3) Cause: The connection to the RADIUS server is established (cleared) or lost (raised). |
Ensure that the correct RADIUS configuration appears and that IP and link connectivity is available and free of errors between the SER and the RADIUS server. |
Context |
Warning |
Event: None Command: None |
rbnSubsConfigErrorEvent 1.3.6.1.4.1.2352.2.27.3.0.1 RBN-SUBSCRIBER-ACTIVE-MIB |
The system sends out this notification when the subscriber session receives one or more policy names from the AAA server. The policy is not defined in the node configuration, and the subscriber session is allowed to come up. Cause: A subscriber AAA record is referring to an undefined policy on the node. |
Define the policy on the node or change the policy in AAA server for the subscriber. |
Context |
Warning |
Event: None Command: None |
rbnTacacsStateChange 1.3.6.1.4.1.2352.2.33.0.1 RBN-TACACS-MIB |
The system sends out this notification when a TACACS+ authorization server transitions to the down state or when a RADIUS server transitions to the up state.(4) Cause: The connection to the TACACS+ server is established (cleared) or lost (raised). |
Ensure that the correct TACACS+ configuration appears and that IP and link connectivity is available and free of errors between the SER and the TACACS+ server. |
Context |
Warning |
Event: None Command: None |
(1) The recommended severity level.
(2) If the value of the rbnRadiusAcctSrvState object
is down and the value of the rbnRadiusReason object is packetTimeout, then the value of the rbnRadiusUsername object
is a username. Otherwise, the value of the rbnRadiusUsername
object is a zero-length string.
(3) If the value of the rbnRadiusAuthSrvState object
is down and the value of the rbnRadiusReason object is packetTimeout, the value of the rbnRadiusUsername object is
a username. Otherwise, the value of the rbnRadiusUsername
object is a zero-length string.
(4) If the value of the rbnTacacsState object is down and the value of the rbnTacacsReason object is packetTimeout, the value of the rbnTacacsUserName object is
a username. Otherwise, the value of the rbnTacacsUserName
object is a zero-length string. If value of the rbnTacacsServerReason
object is serverError, the rbnTacacsServerMsg object
may contain a string from the server; otherwise, the value is a zero-length
string.
Table 2 describes the objects for AAA notifications.
Notification |
Object |
---|---|
rbnRadiusAcctStateChange RBN-RADIUS-MIB |
rbnRadiusAcctSrvState:
|
radiusAccServerAddress IpAddress | |
radiusAccClientServerPortNumber IpAddress | |
rbnRadiusClientPort Unsigned32 (1024..65535) | |
rbnRadiusContext SnmpAdminString (SIZE (1..63)) | |
rbnRadiusReason Integer
| |
rbnRadiusUsername SnmpAdminString (SIZE (0..128)) | |
rbnRadiusAuthStateChange RBN-RADIUS-MIB |
rbnRadiusAuthSrvState Integer
|
radiusAuthServerAddress IpAddress | |
radiusAuthClientServerPortNumber IpAddress | |
rbnRadiusClientPort Unsigned32 (1024..65535) | |
rbnRadiusContext SnmpAdminString (SIZE (1..63)) | |
rbnRadiusReason Integer
| |
rbnRadiusUsername SnmpAdminString (SIZE (0..128)) | |
rbnSubsConfigErrorEvent RBN-SUBSCRIBER-ACTIVE-MIB |
rbnSubsActiveCircuitHandle Octet String (SIZE (8)) |
rbnSubsConfigErrorMsgs SnmpAdminString | |
rbnTacacsStateChange RBN-TACACS-MIB |
rbnTacacsContext SnmpAdminString (SIZE (1..63)) |
rbnTacacsServerIndex Unsigned32 (1..4294967295) | |
rbnTacacsServerAddressType InetAddressType
| |
rbnTacacsServerAddress Octet String (SIZE (0..255)) | |
rbnTacacsServerPort Unsigned32 (0..65535) | |
rbnTacacsServerState RbnTacacsState Integer
| |
rbnTacacsServerReason RbnTacacsReason Integer
| |
rbnTacacsUserName SnmpAdminString (SIZE (0..128)) | |
rbnTacacsServerMsg SnmpAdminString (SIZE (0..256)) |
3 Bridge Notifications
Table 3 lists notifications generated by the router to indicate bridge notifications as defined in the RBN-BRIDGE-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnBridgeCctStateEvent 1.3.6.1.4.1.2352.2.42.0.1 |
The system sends out this notification when a loop has been detected (which locks the bridge circuit) and when the loop is cleared. Data traffic may be dropped during inconsistent state. Cause: A loop among bridge circuits has been detected. One or more circuits are in inconsistent forwarding state. |
If this trap raises regularly, check the bridge configuration and network connection for inconsistency. |
Bridge |
Warning |
Event: None Command: None |
rbnBridgeNewRootEvent 1.3.6.1.4.1.2352.2.42.0.2 |
The system sends out this notification when the sending agent has become the new root of the spanning tree. Cause: The trap is sent by a bridge after its election as the new root. |
None |
Bridge |
Informational |
Event: None Command: None |
rbnBridgeTopologyChangeEvent 1.3.6.1.4.1.2352.2.42.0.3 |
The system sends out this notification when configured ports on a bridge transition from the learning state to the forwarding state, or from the forwarding state to the blocking state. Cause: The port transitions from the learning state to the forwarding state, or from the forwarding state to the blocking state |
None. This is for information only. |
Bridge |
Informational |
Event: None Command: None |
Table 4 describes the objects for bridge notifications.
Notification |
Objects and Values |
---|---|
rbnBridgeCctStateEvent |
rbnBridgeGroupName SnmpAdminString (SIZE(1..32)) |
rbnBridgeCircuitDescriptor SnmpAdminString (SIZE (1..255)) | |
rbnBridgeCircuitStatus Integer:
| |
rbnBridgeGroupContextName SnmpAdminString (SIZE(1..64)) | |
rbnBridgeNewRootEvent |
rbnBridgeId Integer32 (1..65535) |
dot1dStpPortState Integer:
| |
rbnBridgeTopologyChangeEvent |
rbnBridgeId Integer32 (1..65535) |
dot1dStpPortState Integer:
| |
rbnBridgePortPreviousState Integer:
|
4 DHCP Notifications
Table 5 lists notifications generated by the router to indicate Dynamic Host Configuration Protocol (DHCP) notifications as defined in the RBN-DHCP-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnDhcpIntfThresholdFallingThresholdMet 1.3.6.1.4.1.2352.2.30.0.1 |
A notification indicating that a per-interface falling threshold has been reached. |
Falling threshold events are enabled if either or both of rbnDhcpIntfThresholdFallingSendTrap and rbnDhcpIntfThresholdFallingLogMessage are true. |
Node |
Major |
Event: None Command: None |
rbnDhcpIntfThresholdRisingThresholdMet 1.3.6.1.4.1.2352.2.30.0.2 |
A notification indicating that a per-interface rising threshold has been reached. |
Rising threshold events are enabled if either or both of rbnDhcpIntfThresholdRisingSendTrap and rbnDhcpIntfThresholdRisingLogMessage are true. |
Node |
Major |
Event: None Command: None |
rbnDhcpCtxThresholdFallingThresholdMet 1.3.6.1.4.1.2352.2.30.0.3 |
The system sends out this notification when it reaches the threshold of a context falling. Cause: The leases for each context are below the defined threshold. |
Check if there are any connectivity problems that might prevent leases from succeeding. |
Node |
Major |
Event: rbnDhcpCtxThresholdRisingThresholdMet Command: None |
rbnDhcpCtxThresholdRisingThresholdMet 1.3.6.1.4.1.2352.2.30.0.4 |
The system sends out this notification when it reaches the threshold of a context falling. Cause: The leases for each context are below the defined threshold. |
Configure more DHCP ranges if subnets become exhausted. Ensure that you configure the lease-time commands (default-lease-time, offer-lease-time, and max-lease-time) and dhcp max-addrs commands to prevent over-utilization of available addresses. |
Node |
Major |
Event: rbnDhcpCtxThresholdFallingThresholdMet Command: None |
rbnDhcpRangeThresholdFallingThresholdMet 1.3.6.1.4.1.2352.2.30.0.5 |
The system sends out this notification when it reaches the per-subnet falling threshold. Cause: The leases for each subnet are lower than the defined threshold. |
Check any connectivity problems that can prevent leases from succeeding. |
Node |
Major |
Event: rbnDhcpRangeThresholdRisingThresholdMet Command: None |
rbnDhcpRangeThresholdRisingThresholdMet 1.3.6.1.4.1.2352.2.30.0.6 |
The system sends out this notification when it reaches the per-subnet falling threshold. Cause: The leases for each subnet are lower than the defined threshold. |
One subnet may be nearing exhaustion of available IP addresses. Other subnets are available for DHCP unless you receive the context threshold alarm. |
Node |
Major |
Event: rbnDhcpRangeThresholdFallingThresholdMet Command: None |
Table 6 describes the objects for DHCP notifications.
Notification |
Objects and Values |
---|---|
rbnDhcpIntfThresholdFallingThresholdMet |
rbnDhcpIntfThresholdContextName SnmpAdminString (SIZE (0..63)) |
rbnDhcpIntfThresholdAvailable Unsigned32 | |
rbnDhcpIntfThresholdFallingThreshold Unsigned32 (0..196608) | |
rbnDhcpIntfThresholdRisingThresholdMet |
rbnDhcpIntfThresholdContextName SnmpAdminString (SIZE (0..63)) |
rbnDhcpIntfThresholdAvailable Unsigned32 | |
rbnDhcpIntfThresholdRisingThreshold Unsigned32 (0..196608) | |
rbnDhcpCtxThresholdFallingThresholdMet |
rbnDhcpCtxThresholdName SnmpAdminString (SIZE (0..63)) |
rbnDhcpCtxThresholdAvailable Unsigned32 | |
rbnDhcpCtxThresholdFallingThreshold Unsigned32 (0..196608) | |
rbnDhcpCtxThresholdRisingThresholdMet |
rbnDhcpCtxThresholdName SnmpAdminString (SIZE (0..63)) |
rbnDhcpCtxThresholdAvailable Unsigned32 | |
rbnDhcpCtxThresholdRisingThreshold Unsigned32 (0..196608) | |
rbnDhcpRangeThresholdFallingThresholdMet |
rbnDhcpRangeThresholdContextName SnmpAdminString (SIZE (0..63)) |
rbnDhcpRangeThresholdInterfaceName SnmpAdminString (SIZE (1..80)) | |
rbnDhcpRangeThresholdEndAddr IpAddress | |
rbnDhcpRangeThresholdAvailable Unsigned32 | |
rbnDhcpRangeThresholdFallingThreshold Unsigned32 (0..196608) | |
rbnDhcpRangeThresholdRisingThresholdMet |
rbnDhcpRangeThresholdContextName SnmpAdminString (SIZE (0..63)) |
rbnDhcpRangeThresholdInterfaceName SnmpAdminString (SIZE (1..80)) | |
rbnDhcpRangeThresholdEndAddr IpAddress | |
rbnDhcpRangeThresholdAvailable Unsigned32 | |
rbnDhcpRangeThresholdRisingThreshold Unsigned32 (0..196608) |
5 Entity Notifications
Table 7 lists router generated notifications that are entity specific.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
entConfigChange 1.3.6.1.2.1.47.2.0.1 ENTITY-MIB |
The system sends out this notification when the entity configuration changes. It can be utilized by a Network Management System (NMS) to trigger logical and physical entity table maintenance polls. This notification signifies that a physical entity of a chassis changed in the last 5 seconds (for example, card addition or removal), and the SNMP manager can reread the entity and act on the change. Cause: Hardware has been inserted or removed, or a card has failed. |
Use the show hardware, show diag, and show log commands to identify any failed or missing hardware. |
Node |
Minor |
Events:
Command: None |
rbnNEentConfigChange 1.3.6.1.4.1.2352.2.36.0.1 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when the entity configuration changes. It can be utilized by an NMS to trigger logical and physical entity table maintenance polls. This is an enhanced version of entConfigChange trap defined in ENTITY-MIB. Use the traps nemib {exclusive | non-exclusive} command to enable this notification. Cause: Hardware has been inserted or removed, or a card has failed. |
Use the show hardware, show diag, and show log commands to identify any failed or missing hardware. |
Card on the Node |
Minor |
Events:
Command: traps nemib {exclusive | non-exclusive} |
rbnCardAlarm 1.3.6.1.4.1.2352.2.31.0. RBN-CARDMON-MIB |
The system sends out this notification when an event occurs on a controller or traffic card. Cause: An alarm has been raised or cleared on a controller, system, or I/O card. |
Dependent upon which notification raised and installed hardware. See individual traps for troubleshooting steps. |
Device |
Warning |
Event: None Command: None |
rbnNECardAlarm 1.3.6.1.4.1.2352.2.36.0.2 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when an event occurs on a controller or traffic card. This is an enhanced version rbnCardAlarm trap defined in the RBN-CARDMON-MIB Cause: An alarm has been raised or cleared on a controller, system, or I/O card. |
Dependent upon which notification raised and installed hardware. See individual traps for troubleshooting steps. |
Card |
Warning |
Event: None Command: traps nemib {exclusive | non-exclusive} |
rbnSfpAlarm 1.3.6.1.4.1.2352.2.49.0.1 RBN-SFP-MIB |
The system sends out this notification when an SFP or XFP tranceiver changes status. |
This notification is cleared when the defective SFP or XFP tranceiver is replaced in the port. |
Port |
Major or Warning |
Event: None Command: system alarm tranceiver suppress |
Table 8 describes the objects for system management notifications.
| |||||||||||||||||||||||||||||||||||||||
|
6 Environmental Notifications
The following sections provide information about environmental notifications for the SmartEdge router.
Table 9 lists notifications generated by the router to indicate environmental notifications as defined in the RBN-ENVMON-MIB and the RBN-SYS-RESOURCES-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnFanStatusChange 1.3.6.1.4.1.2352.2.4.0.3 RBN-ENVMON-MIB |
The system sends out this notification when the fan status changes. This notification is enabled by default. Cause: The status of a fan test point, with the following values:
|
If a fan has failed, replace the fan tray. |
Node |
Minor |
Event: None Command: None |
rbnPowerStatusChange 1.3.6.1.4.1.2352.2.4.0.4 RBN-ENVMON-MIB |
The system sends out this notification when there is a change in power supply status. Cause: The status of a power test point, with the following values:
|
Ensure that the power is correctly connected, clean, and within specifications. |
Node |
Major |
Event: None Command: None |
rbnSRPowerExceededEvent 1.3.6.1.4.1.2352.2.24.0.4 RBN-SYS-RESOURCES-MIB |
The system sends out this notification when a controller card is inserted and more power is drawn than recommended. The circuits over the administratively down traffic card are impacted. Cause: Power consumption on a SmartEdge router is over the recommended value when a controller card is inserted. |
Remove a controller card or traffic card to clear the power exceed condition. Network design should avoid this scenario on a SmartEdge router |
Node |
Major |
Event: None Command: None |
Table 10 describes the objects for environmental notifications.
Notification |
Objects and Values |
---|---|
rbnFanStatusChange RBN-ENVMON-MIB |
rbnFanStatus Integer
|
rbnPowerStatusChange RBN-ENVMON-MIB |
rbnPowerStatus Integer
|
rbnSRPowerExceededEvent RBN-SYS-RESOURCES-MIB |
rbnSRPowerExceededStatus Integer
|
6.1 Output Example for rbnFanStatusChange
If a fan fails in the system, an SNMP management station might display the following output:
RFC1213-MIB::sysUpTime.0 = Timeticks: (29899) 0:04:58.99 SNMPv2-MIB::snmpTrapOID.0 = OID: RBN-ENVMON-MIB::rbnFanStatusChange RBN-ENVMON-MIB::rbnFanStatus.1 = INTEGER: failed(2)
7 IP Pool Notifications
Table 11 lists notifications generated by the router to indicate IP pool. The notifications are defined in RBN-IP-POOL-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnIpPoolThreshholdMet 1.3.6.1.4.1.2352.2.15.0.2 |
The system sends out this notification when the falling threshold of each pool in a context is reached. Cause: The number of available IP addresses for the pool has decreased to the defined threshold. |
This is an informative message; there are still more available IP addresses available unless you receive the rbnIpPoolContextThresholdMet alarm. If this is a named IP pool, verify that subscribers that use that named pool can still obtain IP addresses. |
Context IP pool |
Critical |
Event: None Command: None |
rbnIpPoolContextThreshholdMet 1.3.6.1.4.1.2352.2.15.0.3 |
The system sends out this notification when the falling threshold of the per-context IP pool is reached. Cause: The number of available IP addresses for the context has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context |
Critical |
Event: None Command: None |
rbnIPPoolContextThreshholdPercentageMet 1.3.6.1.4.1.2352.2.15.0.1 |
The system sends out this notification when the falling threshold of the per-context percentage is reached. The percent (%) of available addresses for the context has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context |
Major |
Event: None Command: None |
rbnInetIpPoolHiFallingThrshMet 1.3.6.1.4.1.2352.2.15.0.4 |
The system sends out this notification when the falling threshold high watermark of per-pool address usage is reached. The number or percent of available prefixes for the pool has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context IP pool |
Major |
Event: None Command: show ipv6 pool |
rbnInetIpPoolLoFallingThrshMet 1.3.6.1.4.1.2352.2.15.0.5 |
The system sends out this notification when the falling threshold low-water mark of per-pool address usage is reached. The number or percent of available prefixes for the pool has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context IP pool |
Critical |
Event: None Command: show ipv6 pool |
rbnInetIpPoolCtxHiFallingThrshMet 1.3.6.1.4.1.2352.2.15.0.6 |
The system sends out this notification when the falling threshold high watermark of per-context address usage is reached. The number or percent of available prefixes for the pool has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context |
Major |
Event: None Command: show ipv6 pool |
rbnInetIpPoolCtxLoFallingThrshMet 1.3.6.1.4.1.2352.2.15.0.7 |
The system sends out this notification when the falling threshold low-water mark of per-pool address usage is reached. The number or percent of available prefixes for the pool has decreased to the defined threshold. |
Check for any connectivity issues that can prevent user authentication on the system. |
Context |
Critical |
Event: None Command: show ipv6 pool |
Table 12 describes the objects for IP pool notifications.
Notification |
Objects and Values |
---|---|
rbnIpPoolThreshholdMet |
rbnIpPoolContextName SnmpAdminString (SIZE (0..63)) |
rbnIpPoolInterfaceName SnmpAdminString (SIZE (0..127)) | |
rbnIpPoolMask IpAddress | |
rbnIpPoolAvailable Unsigned32 | |
rbnIpPoolThreshold Unsigned32 (0..65535) | |
rbnIpPoolContextThreshholdMet |
rbnIpPoolContextName SnmpAdminString (SIZE (0..63)) |
rbnIpPoolContextAvailable Unsigned32 | |
rbnIpPoolContextThreshold Unsigned32 | |
rbnIPPoolContextThreshholdPercentageMet |
rbnIpPoolContextName SnmpAdminString (SIZE (0..63)) |
rbnIpPoolContextTotalSize Unsigned32 | |
rbnIpPoolContextAvailable Unsigned32 | |
rbnIpPoolContextThresholdPercentage Integer32 (0..100) | |
rbnInetIpPoolHiFallingThrshMet |
rbnInetIpPoolEndPrefixType InetAddressType (2—IPv6) |
rbnInetIpPoolEndPrefix InetAddress (16 bytes) | |
rbnInetIpPoolEndPrefixLen InetAddressLength SIZE(1..128) | |
rbnInetIpPoolInterfaceName SnmpAdminString | |
rbnInetIpPoolName SnmpAdminString | |
rbnInetIpPoolSize Unsigned32 | |
rbnInetIpPoolAvailable Unsigned32 | |
rbnInetIpPoolThrshType RbnInetIpPoolThresholdType Integer
| |
rbnInetIpPoolHiFallingThrsh RbnInetIpPoolThreshold (0 to IP pool size) | |
rbnInetIpPoolLoFallingThrshMet |
rbnInetIpPoolEndPrefixType InetAddressType (2—IPv6) |
rbnInetIpPoolEndPrefix InetAddress (16 bytes) | |
rbnInetIpPoolEndPrefixLen InetAddressLength SIZE(1..128) | |
rbnInetIpPoolInterfaceName SnmpAdminString | |
rbnInetIpPoolName SnmpAdminString | |
rbnInetIpPoolSize Unsigned32 | |
rbnInetIpPoolAvailable Unsigned32 | |
rbnInetIpPoolThrshType RbnInetIpPoolThresholdType Integer
| |
rbnInetIpPoolLoFallingThrsh RbnInetIpPoolThreshold (0 to IP pool size) | |
rbnInetIpPoolCtxHiFallingThrshMet |
rbnInetIpPoolCtxName SnmpAdminString |
rbnInetIpPoolCtxPoolSize Unsigned32 | |
rbnInetIpPoolCtxAvailable Unsigned32 | |
rbnInetIpPoolCtxThrshType RbnInetIpPoolThresholdType Integer
| |
rbnInetIpPoolCtxHiFallingThrsh Unsigned32 (0 to IP pool size) | |
rbnInetIpPoolCtxLoFallingThrshMet |
rbnInetIpPoolCtxName SnmpAdminString |
rbnInetIpPoolCtxPoolSize Unsigned32 | |
rbnInetIpPoolCtxAvailable Unsigned32 | |
rbnInetIpPoolCtxThrshType RbnInetIpPoolThresholdType Integer
| |
rbnInetIpPoolCtxLoFallingThrsh Unsigned32 (0 to IP pool size) |
8 IP Security Notifications
Table 13 lists notifications generated by the router to indicate IPSec notifications as defined in the RBN-IP-SECURITY-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnIpSecTunnelStatusChangeAlarm 1.3.6.1.4.1.2352.2.55.0.1 |
This notification signifies a change in the IpSecTunnelState. When IPSecTunnelState has the value down, rbnIpSecEventSeverity has the value major. When IPSecTunnelState has the value up or is obsoleted due to configuration change rbnIpSecEventSeverity has the value clear. |
None. |
Context IPSec Tunnel |
N/A |
N/A |
rbnIpSecNoValidRSASelfCertificateAlarm 1.3.6.1.4.1.2352.2.55.0.2 |
This alarm is set when there is no valid RSA self-certificate for a context. As long as any valid RSA self- certificate exists from any CA, this alarm will not be set. |
It is cleared when a valid self-certificate is configured or when system time is change to make the existing certificate valid. |
Context IPSec Tunnel |
Major |
N/A |
rbnIpSecNoValidRSATrustedCertificateAlarm 1.3.6.1.4.1.2352.2.55.0.3 |
This alarm is raised when there is no valid RSA trusted-certificate for a context. As long as any valid RSA trusted-certificate exists for any CA, this alarm will not be raised. |
It is cleared, when a valid trusted-certificate is configured or when system time is change to make the existing certificate valid. |
Context IPSec Tunnel |
Major |
N/A |
rbnIpSecRSASelfCertificateNearingExpiryAlarm 1.3.6.1.4.1.2352.2.55.0.4 |
This alarm notifies the operator that the RSA self certificate expiration is near. It is raised at the user- specified time before the expiration. |
It is cleared when a new certificate with the self subject name is added, the certificate is deleted, or the system time is pulled up. |
Context IPSec Tunnel |
Warning |
N/A |
rbnIpSecRSATrustedCertificateNearingExpiryAlarm 1.3.6.1.4.1.2352.2.55.0.5 |
This alarm notifies the operator that the RSA self certificate expiration is near. It is raised at the user-specified time before the expiration. |
It is cleared when a new certificate with the self subject name is added, the certificate is deleted, or the system time is pulled up. |
Context IPSec Tunnel |
Warning |
N/A |
Table 14 describes the objects for IPSec notifications.
Notification |
Objects and Values |
---|---|
rbnIpSecTunnelStatusChangeAlarm |
rbnIpSecEventDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnIpSecEventSeverity ItuPerceivedSeverity Integer See Section 19.12 ItuPerceivedSeverity for the values. | |
rbnIpSecEventType IANAItuEventType Integer See Section 19.11 IANAItuEventType for the values. | |
rbnIpSecEventProbableCause IANAItuProbableCause Integer See Section 19.10 IANAItuProbableCause for the values. | |
rbnIpSecTunnelIdentifier SnmpAdminString (SIZE(0..270)) | |
rbnIpSecTunnelName SnmpAdminString (SIZE(0..50)) | |
rbnIpSecTunnelType Integer
| |
rbnIpSecTunnelDownCause Integer
| |
rbnIpSecRemoteIdType Integer
-- Values 4, 6-8, 12-200 and 201-255 are reserved for IANA.
| |
rbnIpSecRemoteId SnmpAdminString (SIZE(0..256)) | |
rbnIpSecLocalAddrContextName SnmpAdminString (SIZE(0..32)) | |
rbnIpSecLocalAddressType InetAddressType | |
rbnIpSecLocalAddress InetAddress | |
rbnIpSecRemoteAddressType InetAddressType | |
rbnIpSecRemoteAddress InetAddress | |
rbnIpSecTunnelState Integer
| |
rbnIpSecNoValidRSASelfCertificateAlarm |
rbnIpSecEventDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnIpSecEventSeverity ItuPerceivedSeverity Integer See Section 19.12 ItuPerceivedSeverity for the values. | |
rbnIpSecEventType IANAItuEventType Integer See Section 19.11 IANAItuEventType for the values. | |
rbnIpSecEventProbableCause IANAItuProbableCause Integer See Section 19.10 IANAItuProbableCause for the values. | |
rbnIpSecNoValidRSATrustedCertificateAlarm |
rbnIpSecEventDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnIpSecEventSeverity ItuPerceivedSeverity Integer | |
rbnIpSecEventType IANAItuEventType Integer | |
rbnIpSecEventProbableCause IANAItuProbableCause Integer | |
rbnIpSecRSASelfCertificateNearingExpiryAlarm |
rbnIpSecEventDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnIpSecEventSeverity ItuPerceivedSeverity Integer See Section 19.12 ItuPerceivedSeverity for the values. | |
rbnIpSecEventType IANAItuEventType Integer See Section 19.11 IANAItuEventType for the values. | |
rbnIpSecEventProbableCause IANAItuProbableCause Integer See Section 19.10 IANAItuProbableCause for the values. | |
rbnIpSecCertificateSubjectName SnmpAdminString (SIZE(0..256)) | |
rbnIpSecCertificateHandle Unsigned32 | |
rbnIpSecExpiryDateAndTime DateAndTime Octet String (SIZE (8)) | |
rbnIpSecRSATrustedCertificateNearingExpiryAlarm |
rbnIpSecEventDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnIpSecEventSeverity ItuPerceivedSeverity Integer See Section 19.12 ItuPerceivedSeverity for the values. | |
rbnIpSecEventType IANAItuEventType Integer See Section 19.11 IANAItuEventType for the values. | |
rbnIpSecEventProbableCause IANAItuProbableCause Integer See Section 19.10 IANAItuProbableCause for the values. | |
rbnIpSecCertificateSubjectName SnmpAdminString (SIZE(0..256)) | |
rbnIpSecCertificateHandle Unsigned32 | |
rbnIpSecExpiryDateAndTime DateAndTime Octet String (SIZE (8)) |
9 L2TP Notifications
Table 15 lists notifications generated by the router to indicate L2TP notifications as defined in the RBN-L2TP-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnL2tpMibTunnelStateChange2 1.3.6.1.4.1.2352.2.28.0.2 |
The system sends out this notification when the SNMP entity detects that the operational state of a tunnel has entered or moved from the established state. The value of the rbnL2tpMibTunnelState object determines the current tunnel state. Cause: The tunnel may have been created (raised) or torn down (cleared). |
Ensure that the correct tunnel configuration appears and that IP and link connectivity is available and free of errors between the two peers. |
Context L2TP Tunnel |
Minor |
Event: None Command: None |
Table 16 describes the objects for L2TP notifications.
Notification |
Objects and Values |
---|---|
rbnL2tpMibTunnelStateChange2 |
rbnL2tpTCfgTunnelContext SnmpAdminString (SIZE (0..80)) |
rbnL2tpMibTunnelState Integer
| |
rbnL2tpTCfgRemoteTunnelID Unsigned32 (0..65535) | |
rbnL2tpMIBDisableTrap TruthValue Integer |
10 L2VPN Cross-Connection (XC) Notifications
Table 17 lists notifications generated by the router to indicate L2VPN cross-connection (XC) notifications as defined in the RBN-L2VPN-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnMplsL2VpnLdpPwStateChange 1.3.6.1.4.1.2352.2.39.0.1 |
This notification is generated when the XC state transitions operationally to up, down, or standby. |
None |
Context |
Informational |
Event: None Command: show xc l2vpn detail |
Table 18 describes the objects for L2VPN XC notifications.
Notification |
Objects and Values |
---|---|
rbnMplsL2VpnLdpPwStateChange |
rbnMplsL2VpnLdpPwStateChange Integer
|
11 Link and Interface Notifications
Table 19 lists notifications generated by the router to Indicate Link and Interface Notifications.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
linkDown 1.3.6.1.6.3.1.1.5.3 IF-MIB |
The system sends out this notification when the link status of an interface is down. Causes include:
|
Check:
|
Port, Circuit, or Interface |
Critical |
Event: linkUp Command: None |
rbnNElinkDown 1.3.6.1.4.1.2352.2.36.0.3 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when the link status of an interface is down. This is an enhanced version of the linkDown trap defined in the IF-MIB. Use the traps nemib {exclusive | non-exclusive} and snmp server commands to enable this notification. Causes include:
|
Check:
|
Port, Circuit, or Interface |
Major |
Event: rbnNElinkUp Command: traps nemib {exclusive | non-exclusive} |
linkUp 1.3.6.1.6.3.1.1.5.4 IF-MIB |
The system sends out this notification when an interface link status is up. Causes include:
|
None; this is an informative message. |
Port, Circuit, or Interface |
Minor |
Event: LinkDown Command: None |
rbnNElinkUp 1.3.6.1.4.1.2352.2.36.0.4 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when an interface link status is up. This is an enhanced version of the linkUp trap defined in the IF-MIB. Use the traps nemib {exclusive | non-exclusive} or the snmp server commands to enable this notification. Causes include:
|
None; this is an informative message. |
Port, Circuit, or Interface |
Minor |
Event: rbnNElinkDown Command: traps nemib {exclusive | non-exclusive} |
dsx1LineStatusChange 1.3.6.1.2.1.10.18.15.0.1 DS1-MIB |
The system sends out this notification when the interface line status changes. Causes include:
|
Check the circuit and port counters for increased errors that can explain the cause of the bounce. |
Node |
Minor |
Event: None Command: None |
rbnNEdsx1LineStatusChange 1.3.6.1.4.1.2352.2.36.0.5 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when the interface line status changes. This is an enhanced version of the dsx1LineStatusChange trap defined in the DS1-MIB. Use the traps nemib {exclusive | non-exclusive} command to enable this notification. Causes include:
|
Check the circuit and port counters for increased errors that can explain the cause of the bounce. |
Port |
Minor |
Event: None Command: traps nemib {exclusive | non-exclusive} |
dsx3LineStatusChange 1.3.6.1.2.1.10.30.15.0.1 DS3-MIB |
The system sends out this notification when the interface line status changes. Causes include:
|
Check the circuit and port counters for any increased errors that might explain the cause of the bounce. |
Node |
Minor |
Event: None Command: None |
rbnNEdsx3LineStatusChange 1.3.6.1.4.1.2352.2.36.0.6 RBN-NOTIFY-ENHANCE-MIB |
The system sends out this notification when the interface line status changes. This is an enhanced version of the dsx3LineStatusChange trap defined in the DS3-MIB. Use the traps nemib {exclusive | non-exclusive} command to enable this notification. Causes include:
|
Check the circuit and port counters for any increased errors that might explain the cause of the bounce. |
Port |
Minor |
Event: None Command: traps nemib {exclusive | non-exclusive} |
rbnAtmPvcOamStatusStateChange 1.3.6.1.4.1.2352.2.19.0.1 RBN-ATM-PVC-OAM-MIB |
The system sends out this notification when the value changes. The notification raises when the rbnAtmPvcOamStatusState object transitions from oamUp to oamDown and clears when it transitions from any of the oamDown to oamUp. Cause: The status of an ATM PVC changed due to an ATM PVC OAM function. |
Check circuit counters for errors on PVCs. If errors increase, identify the source of the errors and check the configuration and hardware diagnostics for correct operation. |
Node |
Major |
Events: None Command: None |
Table 20 describes the objects for link and interface notifications.
Notification |
Objects and Values |
---|---|
linkDown IF-MIB |
ifIndex Integer32 (1..2147483647) |
ifAdminStatus Integer
| |
ifOperStatus Integer See Section 19.7 for the values. | |
rbnNElinkDown RBN-NOTIFY-ENHANCE-MIB |
ifIndex Integer32 (1..2147483647) |
ifAdminStatus Integer
| |
ifOperStatus Integer See Section 19.7 for the values. | |
ifSpeed Gauge32 | |
ifHighSpeed Gauge32 | |
rbnNECircuitId DisplayString (SIZE (0..255)) | |
sysName DisplayString (SIZE (0–255)) | |
linkUp IF-MIB |
ifIndex Integer32 (1..2147483647) |
ifAdminStatus Integer
| |
ifOperStatus Integer See Section 19.7 for the values. | |
rbnNElinkUp RBN-NOTIFY-ENHANCE-MIB |
ifIndex Integer32 (1..2147483647) |
ifAdminStatus Integer
| |
ifOperStatus Integer See Section 19.7 for the values. | |
ifSpeed Gauge32 | |
ifHighSpeed Gauge32 | |
rbnNECircuitId DisplayString (SIZE (0..255)) | |
sysName DisplayString (SIZE (0..255)) | |
dsx1LineStatusChange DS1-MIB |
dsx1LineStatus Integer
|
dsx1LineStatusLastChange TimeStamp | |
rbnNEdsx1LineStatusChange RBN-NOTIFY-ENHANCE-MIB |
dsx1LineStatus Integer
|
dsx1LineStatusLastChange TimeStamp | |
rbnDsx1AlarmSeverity Integer
| |
rbnDsx1AlarmServiceAffecting Integer
| |
rbnNECircuitId DisplayString (SIZE (0..255)) | |
sysName DisplayString (SIZE (0..255)) | |
dsx3LineStatusChange DS3-MIB |
dsx3LineStatus Integer
|
dsx3LineStatusLastChange TimeStamp | |
rbnNEdsx3LineStatusChange RBN-NOTIFY-ENHANCE-MIB |
dsx3LineStatus Integer
|
dsx3LineStatusLastChange TimeStamp | |
rbnDsx3AlarmSeverity Integer
| |
rbnDsx3AlarmServiceAffecting Integer
| |
rbnNECircuitId DisplayString (SIZE (0..255)) | |
sysName DisplayString (SIZE (0..255)) | |
rbnAtmPvcOamStatusStateChange RBN-ATM-PVC-OAM-MIB |
rbnAtmPvcOamStatusState Integer
|
11.1 Output Example for rbnNElinkUp
If Port 12/8 in SmartEdge-Lab1 system becomes operational, the following is output:
2008-05-06 16:06:14 SE-Lab1 [10.192.16.214]: SNMPv2-MIB::sysUpTime.0 = Timeticks: (285745234) 33 days, 1:44:12.34 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.2352.2.36.0.4 IF-MIB::ifIndex.13 = INTEGER: 13 IF-MIB::ifAdminStatus.13 = INTEGER: up(1) IF-MIB::ifOperStatus.13 = INTEGER: up(1) IF-MIB::ifSpeed.13 = Gauge32: 100000000 IF-MIB::ifHighSpeed.13 = Gauge32: 100 SNMPv2-SMI::enterprises.2352.2.36.1.1.4.0 = STRING: "12-8" SNMPv2-MIB::sysName.0 = STRING: SE-Lab1
11.2 Output Example for rbnNElinkDown
If Port 5/2 in SmartEdge-Lab1 system becomes operational, the following is output:
2008-05-06 16:05:53 SE-Lab1 [10.192.16.214]: SNMPv2-MIB::sysUpTime.0 = Timeticks: (285743090) 33 days, 1:43:50.90 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.2352.2.36.0.3 IF-MIB::ifIndex.13 = INTEGER: 13 IF-MIB::ifAdminStatus.13 = INTEGER: up(1) IF-MIB::ifOperStatus.13 = INTEGER: up(1) IF-MIB::ifSpeed.13 = Gauge32: 10000000 IF-MIB::ifHighSpeed.13 = Gauge32: 10 SNMPv2-SMI::enterprises.2352.2.36.1.1.4.0 = STRING: "12-8" SNMPv2-MIB::sysName.0 = STRING: SE-Lab1
12 Media Gateway Notifications
Table 21 lists notifications generated by the router to monitor Media Gateway status as described in RBN-MEDIA-GATEWAY-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
rbnH248LinkStatusAlarm 1.3.6.1.4.1.2352.2.52.0.1 |
The H.248 link for a Media Gateway Controller (MGC) Group was down for more than the configured timeout with major severity (rbnMGEventSeverity). The notification is sent with a rbnMGEventSeverity value of clear when the link state is restored to the Up state or is obsoleted due to a configuration change. |
See rbnMGEventProbableCause |
Node |
See rbnMGEventSeverity |
Configure the timeout value with the alarms h248-link-status command in global configuration mode; the default is 30 seconds. |
Table 24 describes the objects for Media Gateway notifications.
Notification |
Objects and Values |
---|---|
rbnH248LinkStatusAlarm |
rbnMGEventDateAndTime DateAndTime |
rbnMGEventSeverity ItuPerceivedSeverity Integer See Section 19.12 ItuPerceivedSeverity for the values. | |
rbnMGEventSender SnmpAdminString (SIZE(1..64)) | |
rbnMGEventType IANAItuEventType Integer See Section 19.11 IANAItuEventType for the values. | |
rbnMGEventProbableCause IANAItuProbableCause Integer See Section 19.10 IANAItuProbableCause for the values. | |
rbnMGEventInformation SnmpAdminString (SIZE(0..256)) |
13 RMON Notifications
Table 23 lists notifications generated by the router to indicate RMON notifications as defined in RMON-MIB
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
fallingAlarm 1.3.6.1.2.1.16.0.2 |
The system sends out this notification when remote monitoring (RMON) falls. Cause: The value of a MIB object decreases. For example, you can monitor whether the temperature of the router decreases. |
Dependent upon which MIB object you set up for this notification to monitor. |
Node |
Warning |
Events: risingAlarm Commands: None. |
risingAlarm 1.3.6.1.2.1.16.0.1 |
The system sends out this notification when remote monitoring (RMON) rises. Cause: The value of a MIB object increases. For example, you can monitor an error counter to determine if errors increase. |
Dependent upon which MIB object you set up for this notification to monitor. |
Node |
Warning |
Events: fallingAlarm Commands: None. |
Table 24 describes the objects for RMON notifications.
Notification |
Objects and Values |
---|---|
fallingAlarm |
alarmIndex Integer32 (1..65535) |
alarmVariable Object Identifier | |
alarmSampleType Integer
| |
alarmValue Integer32 | |
alarmRisingThreshold Integer32 | |
risingAlarm |
alarmIndex Integer32 (1..65535) |
alarmVariable Object Identifier | |
alarmSampleType Integer
| |
alarmValue Integer32 | |
alarmRisingThreshold Integer32 |
14 Routing Notifications
Table 25 lists notifications generated by the router to indicate routing notifications.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
bgpBackwardTransNotification 1.3.6.1.2.1.15.0.2 BGP4-MIB |
The system sends out this notification when BGP FSM moves from a higher-numbered state to a lower-numbered state. Possible causes:
|
Ensure that BGP is correctly configured and that there are no errors in IP and link connectivity between neighboring devices. |
BGP |
Minor |
Event: bgpEstablishedNotification Command: None |
bgpEstablished Notification 1.3.6.1.2.1.15.0.1 BGP4-MIB |
The system sends out this notification when BGP FSM enters the established state. Cause: Neighbor relationship between BGP peers is established. |
None; this is for information only. |
BGP |
Minor |
Event: bgpBackwardTransNotification Command: None |
mplsL3VpnVrfUp 1.3.6.1.2.1.10.166.11.0 .1 MPLS-L3VPN-STD-MIB |
The system sends out this notification when:
|
Ensure that the correct number of interfaces are associated with the VRF and that the operational status is correct. |
Node |
Informational |
Event: linkUp, linkDown, mplsL3vpnvrfUp, mplsL3VpnVrfDown Commands: show ip interface; show bindings |
mplsL3VpnVrfDown 1.3.6.1.2.1.10.166.11.0.2 MPLS-L3VPN-STD-MIB |
The system sends out this notification when:
|
Ensure that the correct number of interfaces are associated with the VRF and that the operational status is correct. |
Node |
Informational |
Event: linkUp, linkDown, mplsL3vpnvrfUp, mplsL3VpnVrfDown Commands: show ip interface; show bindings |
mplsL3VpnVrfRouteMidThreshExceeded 1.3.6.1.2.1.10.166.11.0.3 MPLS-L3VPN-STD-MIB |
This notification is generated when the number of routes contained by the specified VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold. |
A single notification MUST be generated when this threshold is exceeded, and no other notifications of this type should be issued until the value f mplsL3VpnVrfPerfCurrNumRoutes has fallen below that of mplsL3VpnVrfConfMidRteThresh. |
Node |
Informational |
Event: None. Commands: snmp server traps mplsl3vpn; ip | ipv6 maximum-routes vpn. |
mplsL3VpnVrfNumVrfRouteMaxThreshExceeded 1.3.6.1.2.1.10.166.11.0.4 MPLS-L3VPN-STD-MIB |
This notification is generated when the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsL3VpnVrfMaxRouteThreshold. In cases where mplsL3VpnVrfConfHighRteThresh is set to the same value as mplsL3VpnVrfConfMaxRoutes, mplsL3VpnVrfConfHighRteThresh need not be exceeded; rather, just reached for this notification to be issued. The default value is 0 minutes. |
If this value is set to 0, the agent should only issue a single notification at the time that the maximum threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value. |
Node |
Informational |
Event: None. Commands: snmp server traps mplsl3vpn; ip | ipv6 maximum-routes vpn. |
mplsL3VpnNumVrfRouteMaxThreshCleared 1.3.6.1.2.1.10.166.11.0.6 MPLS-L3VPN-STD-MIB |
This notification is generated only after the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold, and then falls below this value. The emission of this notification informs the operator that the error condition has been cleared without the operator having to query the device. |
A single notification will be issued to indicate the first instance of the error condition as well as the first time the error condition is cleared. |
Node |
Informational |
Event: None. Commands: snmp server traps mplsl3vpn; ip | ipv6 maximum-routes vpn. |
ospfIfStateChange 1.3.6.1.2.1.14.16.2.1 OSPF-TRAP-MIB |
The system sends out this notification when a change in the state of a nonvirtual OSPF interface occurs. Cause: This trap is generated when the interface state regresses (for example when it transitions DR to Down) or progresses to one of the following terminal states:
|
If the transition is to a lower state, for example the down state, determine whether the state transition was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf interface |
ospfVirtIfStateChange 1.3.6.1.2.1.14.16.2.1 OSPF-TRAP-MIB |
The system sends out this notification when the state of an OSPF virtual interface changes. Cause: The interface state changes from Point-to-Point to Down or to a terminal state (for example, Point-to-Point state). |
If the transition is to a lower state, for example the down state, determine whether the state transition was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf interface |
ospfNbrStateChange 1.3.6.1.2.1.14.16.2.2 OSPF-TRAP-MIB |
The system sends out this notification when there has been a change in the state of a nonvirtual OSPF neighbor. Cause: The neighbor state regresses (for example, changes from the attempt state or full state to one way or down state) or progresses to a terminal state (for example to a two-way state or full state). When a neighbor transitions from or to the full state 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. |
If the transition is to a lower state, for example the down state, determine whether the state transition was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf neighbor |
ospfVirtNbrStateChange 1.3.6.1.2.1.14.16.2.3 OSPF-TRAP-MIB |
The system sends out this notification when the state of an OSPF virtual neighbor changes. Cause: The system generates this notification when the neighbor state regresses (for example, from the attempt or full state to the one-way or down state) or progresses to a terminal state (for example, the full state). |
If the transition is to a lower state, for example the down state, determine whether the state transition was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf neighbor |
ospfIfConfigError 1.3.6.1.2.1.14.16.2.4 OSPF-TRAP-MIB |
The system sends out this notification when a nonvirtual interface receives a packet from a router with configuration parameters that conflict with the receiving router's configuration parameters.(1) |
Confirm that the configuration of the sending and receiving router is correct. |
OSPF |
Informational |
Event: None Command: show ospf interface detail; show ospf malform |
ospfVirtIfConfigError 1.3.6.1.2.1.14.16.2.5 OSPF-TRAP-MIB |
The system sends out this notification when a virtual interface receives a packet from a router with configuration parameters that conflict with the receiving router's configuration parameters. |
Confirm that the configuration of the sending and receiving router is correct. |
OSPF |
Informational |
Event: None Command: show ospf interface detail; show ospf malform |
ospfIfAuthFailure 1.3.6.1.2.1.14.16.2.6 OSPF-TRAP-MIB |
The system sends out this notification when a nonvirtual interface receives a packet from a router with a authentication key or authentication type that conflicts with the authentication key or authentication type of the receiving router. |
Confirm that the authentication key and authentication type of the sending and receiving router are correct. |
OSPF |
Informational |
Event: None Command: show ospf interface detail; show ospf malform |
ospfVirtIfAuthFailure 1.3.6.1.2.1.14.16.2.7 OSPF-TRAP-MIB |
The system sends out this notification when a non virtual interface receives a packet from a router with a authentication key or authentication type that conflicts with the authentication key or authentication type of the receiving router. |
Confirm that the authentication key and authentication type of the sending and receiving router are correct. |
OSPF |
Informational |
Event: None Command: show ospf interface detail; show ospf malform |
ospfIfRxBadPacket 1.3.6.1.2.1.14.16.2.8 OSPF-TRAP-MIB |
The system sends out this notification when a virtual interface receives an OSPF packet that cannot be parsed. |
Determine whether the packet received in error is expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf malform |
ospfVirtIfRxBadPacket 1.3.6.1.2.1.14.16.2.9 OSPF-TRAP-MIB |
The system sends out this notification when a nonvirtual interface receives an OSPF packet that cannot be parsed. |
Determine whether the packet received in error is expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf malform |
ospfTxRetransmit 1.3.6.1.2.1.14.16.2.10 OSPF-TRAP-MIB |
The system sends out this notification when a nonvirtual interface retransmits an OSPF packet. All packets that may be retransmitted are associated with an LSDB entry. |
Use the LS type, LS ID, and router ID to identify the LSDB entry. |
OSPF |
Informational |
Event: None Command: show ospf database |
ospfVirtIfTxRetransmit 1.3.6.1.2.1.14.16.2.11 OSPF-TRAP-MIB |
The system sends out this notification when a virtual interface retransmits an OSPF packet. All packets that may be retransmitted are associated with an LSDB entry. |
Use the LS type, LS ID, and Router ID to identify the LSDB entry. |
OSPF |
Informational |
Event: None Command: show ospf database |
ospfOriginateLsa 1.3.6.1.2.1.14.16.2.12 OSPF-TRAP-MIB |
The system sends out this notification when the router originates a new LSA. Cause: An LSA is originated or resent due to a topology change. |
Determine whether the change to Link State Advertisement (LSA) was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf database |
ospfMaxAgeLsa 1.3.6.1.2.1.14.16.2.13 OSPF-TRAP-MIB |
The system sends out this notification when one of the LSAs in the router’s link database has aged to the maximum age (3,600 seconds) as identified in the object MaxAge. |
Determine whether the Link State Advertisement (LSA) withdrawal was expected or represents a problem in your OSPF network. |
OSPF |
Informational |
Event: None Command: show ospf database |
vrrpTrapNewMaster 1.3.6.1.2.1.68.0.1 VRRP-MIB |
The sending agent has transitioned to the Master state. This trap is disabled by default. Enable this trap in the CLI by using the snmp server traps vrrpmib command or setting the vrrpNotificationCntl SNMP object. |
N/A |
SNMP |
Informational |
Event: vNone Command: show vrrp statistics |
vrrpTrapAuthFailure 1.3.6.1.2.1.68.0.2 VRRP-MIB |
The authentication key or authentication type of an incoming packet conflicts with the authentication key or authentication type of the specified VRRP router. This trap is disabled by default and has to be enabled in CLI or through MIB by using the snmp server traps vrrpmib command or setting the vrrpNotificationCntl SNMP object. |
Determine whether the backup VRRP router uses the same authentication type and key as the Master VRRP. Correct the authentication type and key if needed. |
SNMP |
Informational |
Event: vrrpTrapNewMaster Command: show vrrp statistics |
(1) the optionMismatch event causes a trap only if it prevents an adjacency
from forming.
(2) the optionMismatch event causes a trap only if it prevents
an adjacency from forming.
Table 26 describes the objects for routing notifications.
Notification |
Objects and Values |
---|---|
bgpBackwardTransNotification BGP4-MIB |
bgpPeerRemoteAddr IpAddress |
bgpPeerLastError Error code and subcode seen by the peer Octet String (SIZE (2)) | |
bgpPeerState Integer
| |
bgpEstablished Notification BGP4-MIB |
bgpPeerRemoteAddr IpAddress |
bgpPeerLastError Error code and subcode seen by the peer Octet String (SIZE (2)) | |
bgpPeerState Integer
| |
mplsL3VpnVrfUp MPLS-L3VPN-STD-MIB |
mplsL3VpnIfConfRowStatus Integer
|
mplsL3VpnVrfOperStatus Integer
| |
mplsL3VpnVrfDown MPLS-L3VPN-STD-MIB |
mplsL3VpnIfConfRowStatus Integer
|
mplsL3VpnVrfOperStatus Integer
| |
mplsL3VpnVrfRouteMidThreshExceeded MPLS-L3VPN-STD-MIB |
mplsL3VpnVrfPerfCurrNumRoutes Gauge32 Integer (0..4294967295) |
mplsL3VpnVrfConfMidRteThresh Unsigned32 Integer (0..4294967295) | |
mplsL3VpnVrfNumVrfRouteMaxThreshExceeded MPLS-L3VPN-STD-MIB |
mplsL3VpnVrfPerfCurrNumRoutes Gauge32 Integer (0..4294967295) |
mplsL3VpnVrfConfHighRteThresh Unsigned32 Integer (0..4294967295) | |
mplsL3VpnNumVrfRouteMaxThreshCleared MPLS-L3VPN-STD-MIB |
mplsL3VpnVrfPerfCurrNumRoutes Gauge32 Integer (0..4294967295) |
mplsL3VpnVrfConfHighRteThresh Unsigned32 Integer (0..4294967295) | |
ospfIfStateChange OSPF-TRAP-MIB |
ospfRouterId—The originator of the trap |
ospfIfIpAddress IpAddress | |
ospfAddressLessIf Integer32 (0..2147483647) | |
ospfIfState Integer
| |
ospfNbrStateChange OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfNbrIpAddr IpAddress | |
ospfNbrAddressLessIndex Integer32 (0..2147483647) | |
ospfNbrRtrId IpAddress | |
ospfNbrState Integer
| |
ospfVirtIfStateChange OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtIfAreaId IpAddress | |
ospfVirtIfNeighbor IpAddress | |
ospfVirtIfState Integer
| |
ospfVirtNbrStateChange OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtNbrArea IpAddress | |
ospfVirtNbrRtrId IpAddress | |
ospfVirtNbrState Integer
| |
ospfIfConfigError OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfIfIpAddress IpAddress | |
ospfAddressLessIf InterfaceIndexOrZero | |
ospfPacketSrc IpAddress | |
ospfConfigErrorType Integer
| |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfVirtIfConfigError OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtIfAreaId IpAddress | |
ospfVirtIfNeighbor IpAddress | |
ospfConfigErrorType Integer
| |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfIfAuthFailure OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfAddressLessIf InterfaceIndexOrZero | |
ospfPacketSrc IpAddress | |
ospfConfigErrorType Integer
| |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfVirtIfAuthFailure OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtIfAreaId IpAddress | |
ospfVirtIfNeighbor IpAddress | |
ospfConfigErrorType Integer
| |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfIfRxBadPacket OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfIfIpAddress IpAddress | |
ospfAddressLessIf InterfaceIndexOrZero | |
ospfPacketSrc IpAddress | |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfVirtIfRxBadPacket OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtIfAreaId IpAddress | |
ospfVirtIfNeighbor IpAddress | |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfTxRetransmit OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfIfIpAddress IpAddress | |
ospfAddressLessIf InterfaceIndexOrZero | |
ospfNbrRtrId IpAddress | |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfLsdbType Integer See Section 19.9 for the values. | |
ospfLsdbLsid IpAddress | |
ospfLsdbRouterId IpAddress | |
ospfVirtIfTxRetransmit OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfVirtIfAreaId IpAddress | |
ospfVirtIfNeighbor IpAddress | |
ospfPacketType Integer See Section 19.8 for the values. | |
ospfLsdbType Integer See Section 19.9 for the values. | |
ospfLsdbLsid IpAddress | |
ospfLsdbRouterId IpAddress | |
ospfOriginateLsa OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfLsdbAreaId IpAddress | |
ospfLsdbType Integer See Section 19.9 for the values. | |
ospfLsdbLsid IpAddress | |
ospfLsdbRouterId IpAddress | |
ospfMaxAgeLsa OSPF-TRAP-MIB |
ospfRouterId IpAddress |
ospfLsdbAreaId IpAddress | |
ospfLsdbType Integer See Section 19.9 for the values. | |
ospfLsdbLsid IpAddress | |
ospfLsdbRouterId IpAddress | |
vrrpTrapNewMaster VRRP-MIB |
vrrpOperMasterIpAddr IpAddress |
vrrpTrapAuthFailure VRRP-MIB |
vrrpTrapPacketSrc IpAddress |
vrrpTrapAuthErrorType Integer
|
14.1 Output Example for ospfNbrStateChange
If the OSPF neighbor state changes to the initial state for neighbor router 2.2.2.2, the output displays:
From: 10.12.129.18 sysUpTime.0 = 00:15:58.54 snmpTrapOID.0 = ospfNbrStateChange ospfRouterId.2.2.2.2.0 = 22.22.22.22 ospfNbrIpAddr.2.2.2.2.0 = 2.2.2.2 ospfNbrAddressLessIndex.2.2.2.2.0 = 0 ospfNbrRtrId.2.2.2.2.0 = 11.11.11.11 ospfNbrState.2.2.2.2.0 = exchangeStart(5)
14.2 Output Example for vrrpTrapNewMaster
If the VRRP state transitions to Master for router 2.2.2.2, the output displays:
From: 2.2.2.2 sysUpTime.0 = 01:34:47.59 snmpTrapOID.0 = vrrpTrapNewMaster vrrpOperMasterIpAddr.67108865.3 = 10.1.1.1
14.3 CLI Example for VRRP-MIB Notifications
To enable notifications for VRRP-MIB issue the following CLI commands:
[local]Redback#config [local]Redback(config)#snmp server [local]Redback(config-snmp-server)#traps vrrpmib
To enable the VRRP-MIB notifications with an SNMP management tool, set the vrrpNotificationCntl object to 1: enabled.
To disable VRRP-MIB notifications with the SNMP management tool, set the vrrpNotificationCntl object to 2: disabled.
14.4 Output Example for vrrpTrapAuthFailure
If the authentication key or authentication type of an inbound VRRP packet from VRRP router 1.1.1.10 conflicts with the authentication key or authentication type of VRRP router 2.2.2.2, the following is output:
From: 2.2.2.2 sysUpTime.0 = 01:15:37.98 snmpTrapOID.0 = vrrpTrapAuthFailure vrrpTrapPacketSrc = 1.1.1.10 vrrpTrapAuthErrorType = authFailure(3)
15 System Management Notifications
Table 27 lists notifications generated by the router to indicate system management notifications.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
authenticationFailure 1.3.6.1.6.3.1.1.5.5 SNMPv2-MIB |
The system sends out this notification when it could not authenticate the address of a protocol message. Cause: A device attempted to connect by using the incorrect community string. |
Use access lists to only allow SNMP connections from trusted sources. Verify that the SNMP community string uses the correct configuration. |
SNMP agent |
Warning |
Event: none. Command: none. |
coldStart 1.3.6.1.6.3.1.1.5.1 SNMPv2-MIB |
The system sends out this notification when the SNMP agent restarts. Cause: One of the following can cause SNMP to restart:
|
Determine whether the SNMP process restarted or if the XCRP performed a switchover. Send the output from the show tech and show crashfiles commands to customer support. |
SNMP agent |
Critical |
Event: none. Command: none. |
pingProbeFailed 1.3.6.1.2.1.80.0.1 PING-MIB |
Generated when a probe failure is detected, when the corresponding pingCtlTrapGeneration object is set to probeFailure(0), subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of consecutive probe failures that are required before this notification can be generated. |
Walk pingProbeHistoryTable to get details. |
Node |
Informational |
Event: none Command: none. |
pingTestFailed 1.3.6.1.2.1.80.0.2 PING-MIB |
The system sends out this notification when a ping test fails. Cause: The corresponding pingCtlTrapGeneration object is set to testFailure(1). The pingCtlTrapTestFailureFilter object specifies the number of probes in a test that must fail in order to consider the test failed. |
Walk pingProbeHistoryTable to get details. |
Node |
Informational |
Event: none Command: none. |
pingTestCompleted 1.3.6.1.2.1.80.0.3 PING-MIB |
Generated when a ping test completes. Cause: The corresponding pingCtlTrapGeneration object is set to testCompletion(2). |
None. |
Node |
Informational |
Event: none. Command: show snmp ping, snmp ping. |
traceRoutePathChange 1.3.6.1.2.1.81.0.1 TRACEROUTE-MIB |
Generated when the path to a target has changed. |
None. |
Node |
Informational |
Event: none. Command: show snmp traceroute, snmp traceroute. |
traceRouteTestFailed 1.3.6.1.2.1.81.0.2 TRACEROUTE-MIB |
Generated when the path to a target could not be determined. |
None. |
Node |
Informational |
Event: none. Command: show snmp traceroute, snmp traceroute. |
traceRouteTestCompleted 1.3.6.1.2.1.81.0.3 TRACEROUTE-MIB |
Generated when the path to a target is determined. |
None. |
Node |
Informational |
Event: none. Command: show snmp traceroute, snmp traceroute. |
dot1agCfmFaultAlarm 1.3.111.2.802.1.1.8.0.1 IEEE8021-CFM-MIB |
The system sends out this notification when a maintenance association endpoint (MEP) has a persistent defect condition. Cause: The MEP has a persistent defect condition. |
After you receive the notification, identify the system from the network source address of the notification. Identify the MEP reporting the defect from the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification. The dot1agCfmMdIndex in the OID identifies the maintenance domain in which in the MEP exists. The value of the dot1agCfmMaIndex object identifies the MEP's maintenance association The value of the dot1agCfmMepIdentifier object identifies the CFM database MEPID of the MEP reporting this defect. Only 1 local MEP is allowed per maintenance association in a working condition. A defect to A raised trap is caused by a remote MEP. The local MEP reporting the defect is present in the identifier along with the highest defect for the MEP. The remote MEP id is not in the trap content and the remote MEP causing the error can be found only from the show logs. The defect condition is the value of the dot1agCfmMepHighestPrDefect variable and is raised by the MEP whenever it loses or restores contact with one or more other MEPs. |
CFM |
Warning |
Event: none Command: none |
rbnBulkStatsTrfrFail2 1.3.6.1.4.1.2352.2.21.0.2 RBN-BULKSTATS-MIB |
The system sends out this notification when bulkstats data does not transfer to the receiver. Cause: The SmartEdge router could not reach the server for the bulkstats transfer. |
Verify that IP and link connectivity are up for the SmartEdge router and server. Verify that the protocol in use (for example, FTP) is not being blocked and that those services are correctly configured on the SmartEdge router and server. |
Node |
Major |
Event: none Command: none. |
Table 28 describes the objects for system management notifications.
Notification |
Objects and Values |
---|---|
authenticationFailure SNMPv2-MIB |
N/A |
coldStart SNMPv2-MIB |
N/A |
dot1agCfmFaultAlarm IEEE8021-CFM-MIB |
dot1agCfmMepHighestPrDefect Dot1agCfmHighestDefectPri Integer
|
pingProbeFailed PING-MIB |
pingCtlTargetAddressType InetAddressType Integer Default is 0.
|
pingCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsOperStatus Integer
| |
pingResultsIpTargetAddressType InetAddressType Integer Default is 0.
| |
pingResultsIpTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsMinRtt Unsigned32 Integer (0..4294967295) | |
pingResultsMaxRtt Unsigned32 Integer (0..4294967295) | |
pingResultsAverageRtt Unsigned32 Integer (0..4294967295) | |
pingResultsProbeResponses Gauge32 Integer (0..4294967295) | |
pingResultsSentProbes Gauge32 Integer (0..4294967295) | |
pingResultsRttSumOfSquares Unsigned32 Integer (0..4294967295) | |
pingResultsLastGoodProbe DateAndTime Octet String (SIZE (8)) | |
pingTestFailed PING-MIB |
pingCtlTargetAddressType InetAddressType Integer Default is 0.
|
pingCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsOperStatus: 3—completed | |
pingResultsIpTargetAddressType InetAddressType Integer Default is 0.
| |
pingResultsIpTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsMinRtt Unsigned32 | |
pingResultsMaxRtt Unsigned32 | |
pingResultsAverageRtt Unsigned32 | |
pingResultsProbeResponses Gauge32 | |
pingResultsSentProbes Gauge32 | |
pingResultsRttSumOfSquares Unsigned32 | |
pingResultsLastGoodProbe DateAndTime Octet String (SIZE (8)) | |
pingTestCompleted PING-MIB |
pingCtlTargetAddressType InetAddressType Integer Default is 0.
|
pingCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsOperStatus 3—completed | |
pingResultsIpTargetAddressType InetAddressType Integer Default is 0.
| |
pingResultsIpTargetAddress InetAddress Octet String (SIZE (0..255)) | |
pingResultsMinRtt Unsigned32 | |
pingResultsMaxRtt Unsigned32 | |
pingResultsAverageRtt Unsigned32 | |
pingResultsProbeResponses Gauge32 | |
pingResultsSentProbes Gauge32 | |
pingResultsRttSumOfSquares Unsigned32 | |
pingResultsLastGoodProbe DateAndTime Octet String (SIZE (8)) | |
traceRoutePathChange TRACEROUTE-MIB |
traceRouteCtlTargetAddressType InetAddressType Integer
|
traceRouteCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
traceRouteResultsIpTgtAddrType InetAddressType Integer
| |
traceRouteResultsIpTgtAddr InetAddress Octet String (SIZE (0..255)) | |
traceRouteTestFailed TRACEROUTE-MIB |
traceRouteCtlTargetAddressType InetAddressType Integer
|
traceRouteCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
traceRouteResultsIpTgtAddrType InetAddressType Integer
| |
traceRouteResultsIpTgtAddr InetAddress Octet String (SIZE (0..255)) | |
traceRouteTestCompleted TRACEROUTE-MIB |
traceRouteCtlTargetAddressType InetAddressType Integer
|
traceRouteCtlTargetAddress InetAddress Octet String (SIZE (0..255)) | |
traceRouteResultsIpTgtAddrType InetAddressType Integer
| |
traceRouteResultsIpTgtAddr InetAddress Octet String (SIZE (0..255)) | |
rbnBulkStatsTrfrFail2 RBN-BULKSTATS-MIB |
rbnBulkStatsLastTrfrIpAddrType2 InetAddressType Integer
|
rbnBulkStatsLastTrfrIpAddr2 InetAddress Octet String (SIZE (0..255)) | |
rbnBulkStatsLastTrfrStatus2 Integer
|
15.1 Output Example for dot1agCfmFaultAlarm
If you want to determine whether a maintenance association endpoint (MEP) has a persistent defect condition, an SNMP management station might display the following output for the dot1agCfmFaultAlarm notification.
Redback% getmany -v2c test.lab public dot1agCfmMepHighestPrDefect Community: public@local From: 10.12.129.29 sysUpTime.0 = 04:17:04.81 snmpTrapOID.0 = dot1agCfmFaultAlarm dot1agCfmMepHighestPrDefect.1.1.31 = defMACstatus(2)
16 System Resource Notifications
Table 29 lists notifications generated by the router to indicate system resource notifications.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnSRProcessEvent 1.3.6.1.4.1.2352.2.24.0.1 RBN-SYS-RESOURCES-MIB |
The system sends out this notification when a process stops or begins. A process may have terminated and impact the associated services unless the process is restarted. Cause: A process restarted. |
Use the show crashfiles command to check the crash files. Use the show tech command to show the crash files to customer support for investigation. A process may have terminated unexpectedly. Debug the system if the process does not restart automatically. |
Controller |
Major |
Event: None Command: None |
rbnSRStorageFailedEvent 1.3.6.1.4.1.2352.2.24.0.3 RBN-SYS-RESOURCES-MIB |
The system sends out this notification when the value of the rbnSRStorageStatus object for a device changes to failed. Possible causes:
|
Replace the flash card. |
Controller |
Warning |
Event: None Command: None |
rbnSRSwitchoverEvent 1.3.6.1.4.1.2352.2.24.0.2 RBN-SYS-RESOURCES-MIB |
The system sends out this notification when an XCRP switchover occurs. Cause: The XCRP was manually switched over, or automatically switched over, to recover from an error. |
Use the show crashfiles command to check the crash files. Use the show tech command to show the crash files to customer support for investigation. |
Controller |
Informational |
Event: None Command: None |
rcfJobCompleted 1.3.6.1.4.1.2352.2.13.0.1 RBN-CONFIG-FILE-MIB |
The system sends out this notification when it completes a configuration job. Cause: The configuration has completed loading. |
None; this is for information only. |
Controller |
Minor |
Event: None Command: None |
Table 30 describes the objects for system resource notifications.
Notification |
Objects and Values | |
---|---|---|
rbnSRProcessEvent RBN-SYS-RESOURCES-MIB |
rbnSRProcessNotifyPID Unsigned32 (0..2147483647) | |
rbnSRProcessNotifyEventCause Integer:
|
| |
rbnSRProcessNotifyEventType Integer
| ||
rbnSRProcessNumOfSpawn Unsigned32 (0..2147483647) | ||
rbnSRStorageFailedEvent RBN-SYS-RESOURCES-MIB |
rbnSRStorageDescr SnmpAdminString (SIZE (0..64)) | |
rbnSRStorageMedia Integer
| ||
rbnSRStorageSlot Unsigned32 (0..255) | ||
rcfJobCompleted RBN-CONFIG-FILE-MIB |
rcfJobResult Integer
| |
rcfJobErrorMsgs SnmpAdminString Octet String (SIZE (0..255)) |
17 System Security Notifications
Table 31 lists notifications generated by the router to monitor system security as described in RBN-SYS-SECURITY-MIB. The router samples data at the start and end of the interval configured using the interval command in malicious-traffic configuration mode. The difference between the start and end of the interval is called the delta value.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
rbnMaliciousPktThresholdHiExceeded 1.3.6.1.4.1.2352.5.54.0.1 |
This notification signifies that one of the delta values is equal to or greater than the corresponding high threshold value. The specific delta value is the last object in the notification varbind list. |
None. |
Node |
Warning |
Event: None. Command: Set the high threshold with the threshold high low command in malicious-traffic configuration mode. |
rbnMaliciousPktThresholdLowExceeded 1.3.6.1.4.1.2352.5.54.0.2 |
This notification signifies that one of the delta values is less than or equal to the corresponding low threshold value. The specific delta value is the last object in the notification varbind list. |
None. |
Node |
Warning |
Event: None. Command: Set the low threshold with the threshold high low command in malicious-traffic configuration mode. |
Table 32 describes the objects for system resource notifications.
Notification |
Objects and Values |
---|---|
rbnMaliciousPktThresholdLowExceeded |
rbnThresholdNotifyTime DateAndTime Octet String (SIZE (8)) |
18 System Services Engine (SSE) Notifications
Table 33 lists notifications generated by the router to indicate system resource events as defined in the RBN-SSE-MIB.
Event and OID |
Description and Cause |
Recommended Action |
Reporting Module |
Severity |
Related Events and Commands |
---|---|---|---|---|---|
rbnSseFsgSwitchManual 1.3.6.1.4.1.2352.2.48.0.1 |
The system sends out this notification when the file server group manual switch is in progress. Probable Cause: Operation Notification |
Determine whether the manual switch was intentional. |
Node |
Major |
Event: None Command: None |
rbnSseFsgSwitchAuto 1.3.6.1.4.1.2352.2.48.0.2 |
The system sends out this notification when the file server group automatic switch is in progress. Probable Cause: Operation Notification |
Determine whether the automatic switch was the result of an intended process. |
Node |
Warning |
Event: None Command: None |
rbnSseFsgSwitchCompleted 1.3.6.1.4.1.2352.2.48.0.3 |
The system sends out this notification when the file server group switch completed. Probable Cause: Operation Notification |
None. Informational only. |
Node |
Warning |
Event: None Command: None |
rbnSseFsgSwitchFail 1.3.6.1.4.1.2352.2.48.0.4 |
The system sends out this notification when the file server group switch failed. Probable Cause: Operation Notification |
Determine the cause of the failure. |
Node |
Major |
Event: None Command: None |
rbnSseFsgSwitchWtr 1.3.6.1.4.1.2352.2.48.0.5 |
The system sends out this notification when the file server group automatic switch is waiting to be restored. Probable Cause: Configuration or customization error |
Determine if the automatic switch is waiting as a result of a stalled system or process. |
Node |
Warning |
Event: None Command: None |
rbnSseFsgNotOperational 1.3.6.1.4.1.2352.2.48.0.6 |
The system sends out this notification when the file server group is not operational. Probable Cause: Database Inconsistency |
Determine if the file server group should be operational and, if so, what is causing the file server group to not be operational. |
Node |
Major |
Event: None Command: None |
rbnSseFsgBlockDeviceFail 1.3.6.1.4.1.2352.2.48.0.7 |
The system sends out this notification when the file server group block device failed. Probable Cause: Operation Failure |
Determine the reason for the failure. |
Node |
Major |
Event: None Command: None |
rbnSseFsgPartitionNotOperational 1.3.6.1.4.1.2352.2.48.0.8 |
The system sends out this notification when the file server group partition is not operational. Probable Cause: Database inconsistency |
Determine why the partition is not operational. |
Node |
Major |
Event: None Command: None |
rbnSseFsgParitionDataSyncing 1.3.6.1.4.1.2352.2.48.0.9 |
The system sends out this notification when the file server group partition data sync is in progress. Probable Cause: Configuration or customization error. |
Determine whether the data sync is intentional. |
Node |
Warning |
Event: None Command: None |
rbnSseFsgParitionDataSyncFail 1.3.6.1.4.1.2352.2.48.0.10 |
The system sends out this notification when the file server group partition data sync failed. Probable Cause: Operation Failure |
Determine why the partition data sync failed. |
Node |
Major |
Event: None Command: None |
rbnSseFsgPartitionFull 1.3.6.1.4.1.2352.2.48.0.11 |
The system sends out this notification when the file server group partition is full Probable Cause: Operation Notification |
Determine why the partition is full and clean out entries or add more space to the partition. |
Node |
Major |
Event: None Command: None |
rbnSseFsgPartitionLow 1.3.6.1.4.1.2352.2.48.0.12 |
The system sends out this notification when the file server group partition is low in space. Probable Cause: Operation Notification |
Determine why the partition is low in space and clean out entries or add more space to the partition. |
Node |
Warning |
Event: None Command: None |
rbnSseFsgPartitionNotOperStandby 1.3.6.1.4.1.2352.2.48.0.13 |
The system sends out this notification when the file server group partition is not ready at standby Probable Cause: Database Inconsistency |
Determine why the partition is not ready at standby. |
Node |
Major |
Event: None Command: None |
Table 34 describes the objects for system resource notifications.
Notification |
Objects and Values |
---|---|
rbnSseFsgSwitchManual |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgSwitchAuto |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgSwitchCompleted |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgSwitchFail |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgSwitchWtr |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgNotOperational |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgBlockDeviceFail |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgPartitionNotOperational |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgParitionDataSyncing |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgParitionDataSyncFail |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgPartitionFull |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgPartitionLow |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. | |
rbnSseFsgPartitionNotOperStandby |
rbnSseAlarmDateAndTime DateAndTime Octet String (SIZE (8)) |
rbnSseAlarmSeverity Integer See Section 19.3 for the values. | |
rbnSseAlarmProbableCause Integer See Section 19.4 for the values. | |
rbnSseEventType Integer See Section 19.5 for the values. | |
rbnSseAlarmDescription SnmpAdminString SIZE(0..64) | |
rbnFSGroupState Integer See Section 19.6 for the values. |
19 Object Appendix
19.1 RbnAlarmId and rbnCardAlarmId
1—unknown
2—cpFail: Circuit pack failure
3—cpBackplaneFail: Circuit pack backplane failure
4—diagFail: Diagnostic failure
5—voltageFail: Voltage failure
6—controllerSwitchFail: Controller switch failure
7—controllerTempCritical: Controller temp critical
8—controllerFail: Controller failure
9—controllerDiagFail: Controller diag test failure
10—cpPowerOnDiagFail: Circuit pack power-on—diagnostic failure
11—controllerPowerOnDiagFail: Controller power-on—diagnostic failure
12—cpOverheat: Circuit pack overheat
13—controllerOverheat
14—backplaneclkfail
15—btciferror
16—btcnotready
17—cpbackplanedegrade
18—cpcardcodemismatch
19—cpmismatch
20—cpmissing
21—cpresetcomplete
22—downloadcompleted
23—downloadfailed
24—syncfail
25—backupfail
26—controllercardcodemismatch
27—controllercardtypemismatch
28—controllermissing
29—controlleroverheat
30—controllerswitchauto
31—controllerswitchcompleted
32—controllerswitchexfailed
33—controllerswitchforced
34—controllerswitchmanual
35—localfantrayinventfail
36—localinventfail
37—localbackplaneinventfail
38—lostm2m
39—nonvolatilememfail
40—peerhwincompatible
41—peerinventfail
42—peermodeincompatible
43—peersharedformatmismatch
44—rtclockfail
45—mic1missing
46—mic2missing
47—mic1mismatch
48—mic2mismatch
49—mic1voltagefailure
50—mic2voltagefailure
51—mic1overheat
52—mic2overheat
53—mic1failure
54—mic2failure
55—mic1podfail
56—mic2podfail
57—mic1diagnosticfail
58—mic2diagnosticfail
59—ethtransceiverrxpowerhi
60—ethtransceiverrxpowerlo
61—ethtransceivertemphi
62—ethtransceivertemplo
63—ethtranceivervoltagehi
64—ethtranceivervoltagelo
65—ethtransceiverbiashi
66—ethtransceiverbiaslo
67—ethtransceivertxpowerhi
68—ethtransceivertxpowerlo
69—ethtransceiveraux1hi
70—ethtransceiveraux1lo
71—ethtransceiveraux2hi
72—ethtransceiveraux2lo
73—ethtransceiverlvcc5hi
74—ethtransceiverlvcc5lo
75—ethtransceiverlvcc3hi
76—ethtransceiverlvcc3lo
77—ethtransceiverlvcc2hi
78—ethtransceiverlvcc2lo
82—aseAsp1Down
83—aseAsp2Down
84—controllerSwNotSupported
19.2 rbnCardAlarmProbableCause
For more details, refer to RBN-ALARM-TC.my.
1—aIS
3—DegradedSignal
4—FarEndReceiverFailure
5—FramingError
6—LossOfFrame
7—LossOfPointer
8—LossOfSignal
9—PayloadTypeMismatch
10—TransmissionError
12—ExcessiveBER
13—PathTraceMismatch
14—Unavailable
15—SignalLableMismatch
17—ReceiveFailure
18—TransmitFailure
19—ModulationFailure
20—DemodulationFailure
21—LinkFailure
22—ConfigurationMismatch
23—ConcatenationMismatch
Values 27–50 are reserved for communications alarm related probable causes.
The following are used with equipment alarm:
51—BackplaneFailure
53—EquipmentIdDuplication
54—ExternalIFDeviceProblem
55—LineCardProblem
56—MultiplexerProblem
57—NEIdentifierDuplication
58—PowerProblem
59—ProcessorProblem
60—ProtectionPathFailure
61—ReceiverFailure
62—ReplaceableUnitMissing
63—ReplaceableUnitTypeMismatch
64—SyncSourceMismatch
65—TerminalProblem
66—TimingProblem
67—TransmitterFailure
68—TrunkCardProblem
69—ReplaceableUnitProblem
70—RealTimeClockFailure
Values 83–100 are reserved for equipment alarm related probable causes.
The following are used with environmental alarm:
101—AirCompressorFailure
102—AirConditioningFailure
103—AirDryerFailure
104—BatteryDischarging
105—BatteryFailure
106—CommercialPowerFailure
107—CoolingFanFailure
108—EngineFailure
109—FireDetectorFailure
110—FuseFailure
111—GeneratorFailure
112—LowBatteryThreshold
113—PumpFailure
114—RectifierFailure
115—RectifierHighVoltage
116—RectifierLowVoltage
117—VentilationsSystemFailure
118—EnclosureDoorOpen
119—ExplosiveGas
120—Fire
121—Flood
122—HighHumidity
123—HighTemperature
124—HighWind
125—IceBuildUp
126—IntrusionDetection
127—LowFuel
128—LowHumidity
129—LowCablePressure
130—LowTemperature
131—LowWater
132—Smoke
133—ToxicGas
149—Customized
Values 137–150 are reserved for environmental alarm related probable causes.
The following are used with processing error alarm:
151—StorageCapacityProblem
152—MemoryMismatch
153—CorruptData
154—OutOfCPUCycles
155—SfwrEnvironmentProblem
156—SfwrDownloadFailure
157—LossOfRealTime
158—Reinitialized
159—OperationNotification
160—OperationFailure
Values 168–200 are reserved for processing error alarm related probable causes.
1001—LossOfTimingSource
1002—ApsChannelProcessingFailure
1003—ApsByteFailure
1004—ApsChannelMatchFailure
1005—ApsModeMismatch
1007—LossOfTUMultiframeIndicator
1010—PathSelectorFailure
1011—BlsrDefaultKBytes
1012—BlsrInconsistentAPSCodes
1013—BlsrNodeIdMismatch
1014—BlsrImproperAPSCodes
1015—BlsrSquelching
1016—BlsrInvalidNeighbour
1017—BlsrInvalidRingMap
1018—BlsrInvalidRingId
1019—BlsrIncompleteRingConfig
1020—BlsrIncompleteETConfig
1021—BlsrNodeIncorrectOrientation
19.3 rbnSseAlarmSeverity
1—cleared
2—indeterminate
3—critical
4—major
5—minor
6—warning
19.4 rbnSseAlarmProbableCause
1—aIS
2—callSetUpFailure
3—degradedSignal
4—farEndReceiverFailure
5—framingError
6—lossOfFrame
7—lossOfPointer
8—lossOfSignal
9—payloadTypeMismatch
10—transmissionError
11—remoteAlarmInterface
12—excessiveBER
13—pathTraceMismatch
14—unavailable
15—signalLabelMismatch
16—lossOfMultiFrame
17—receiveFailure
18—transmitFailure
19—modulationFailure
20—demodulationFailure
21—broadcastChannelFailure
22—connectionEstablishmentError
23—invalidMessageReceived
24—localNodeTransmissionError
25—remoteNodeTransmissionError
26—routingFailure
51—backplaneFailure
52—dataSetProblem
53—equipmentIdentifierDuplication
54—externalIFDeviceProblem
55—lineCardProblem
56—multiplexerProblem
57—nEIdentifierDuplication
58—powerProblem
59—processorProblem
60—protectionPathFailure
61—receiverFailure
62—replaceableUnitMissing
63—replaceableUnitTypeMismatch
64—synchronizationSourceMismatch
65—terminalProblem
66—timingProblem
67—transmitterFailure
68—trunkCardProblem
69—replaceableUnitProblem
70—realTimeClockFailure
71—antennaFailure
72—batteryChargingFailure
73—diskFailure
74—frequencyHoppingFailure
75—iODeviceError
76—lossOfSynchronisation
77—lossOfRedundancy
78—powerSupplyFailure
79—signalQualityEvaluationFailure
80—tranceiverFailure
81—protectionMechanismFailure
82—protectingResourceFailure
101—airCompressorFailure
102—airConditioningFailure
103—airDryerFailure
104—batteryDischarging
105—batteryFailure
106—commercialPowerFailure
107—coolingFanFailure
108—engineFailure
109—fireDetectorFailure
110—fuseFailure
111—generatorFailure
112—lowBatteryThreshold
113—pumpFailure
114—rectifierFailure
115—rectifierHighVoltage
116—rectifierLowFVoltage
117—ventilationsSystemFailure
118—enclosureDoorOpen
119—explosiveGas
120—fire
121—flood
122—highHumidity
123—highTemperature
124—highWind
125—iceBuildUp
126—intrusionDetection
127—lowFuel
128—lowHumidity
129—lowCablePressure
130—lowTemperatue
131—lowWater
132—smoke
133—toxicGas
134—coolingSystemFailure
135—externalEquipmentFailure
136—externalPointFailure
151—storageCapacityProblem
152—memoryMismatch
153—corruptData
154—outOfCPUCycles
155—sfwrEnvironmentProblem
156—sfwrDownloadFailure
157—lossOfRealTimel
158—applicationSubsystemFailure
159—configurationOrCustomisationError
160—databaseInconsistency
161—fileError
162—outOfMemory
163—softwareError
164—timeoutExpired
165—underlayingResourceUnavailable
166—versionMismatch
201—bandwidthReduced
202—congestion
203—excessiveErrorRate
204—excessiveResponseTime
205—excessiveRetransmissionRate
206—reducedLoggingCapability
207—systemResourcesOverload
500—adapterError
501—applicationSubsystemFailture
502—bandwidthReducedX733
503—callEstablishmentError
504—communicationsProtocolError
505—communicationsSubsystemFailure
506—configurationOrCustomizationError
507—congestionX733
508—coruptData
509—cpuCyclesLimitExceeded
510—dataSetOrModemError
511—degradedSignalX733
512—dteDceInterfaceError
513—enclosureDoorOpenX733
514—equipmentMalfunction
515—excessiveVibration
516—fileErrorX733
517—fireDetected
518—framingErrorX733
519—heatingVentCoolingSystemProblem
520—humidityUnacceptable
521—inputOutputDeviceError
522—inputDeviceError
523—lanError
524—leakDetected
525—localNodeTransmissionErrorX733
526—lossOfFrameX733
527—lossOfSignalX733
528—materialSupplyExhausted
529—multiplexerProblemX733
530—outOfMemoryX733
531—ouputDeviceError
532—performanceDegraded
533—powerProblems
534—pressureUnacceptable
535—processorProblems
536—pumpFailureX733
537—queueSizeExceeded
538—receiveFailureX733
539—receiverFailureX733
540—remoteNodeTransmissionErrorX733
541—resourceAtOrNearingCapacity
542—responseTimeExecessive
543—retransmissionRateExcessive
544—softwareErrorX733
545—softwareProgramAbnormallyTerminated
546—softwareProgramError
547—storageCapacityProblemX733
548—temperatureUnacceptable
549—thresholdCrossed
550—timingProblemX733
551—toxicLeakDetected
552—transmitFailureX733
553—transmiterFailure
554—underlyingResourceUnavailable
555—versionMismatchX733
600—authenticationFailure
601—breachOfConfidentiality
602—cableTamper
603—delayedInformation
604—denialOfService
605—duplicateInformation
606—informationMissing
607—informationModificationDetectede
608—informationOutOfSequence
609—keyExpired
610—nonRepudiationFailure
611—outOfHoursActivity
612—outOfServic
613—proceduralError
614—unauthorizedAccessAttempt
615—unexpectedInformation
1024—other
19.5 rbnSseEventType
1—other
2—communicationsAlarm
3—qualityOfServiceAlarm
4—processingErrorAlarm
5—equipmentAlarm
6—environmentalAlarm
7—integrityViolation
8—operationalViolation
9—physicalViolation
10—securityServiceOrMechanismViolation
11—timeDomainViolation
19.6 rbnFSGroupState
0—unknown
1—up
2—down
3—partial
4—stale
5— noCard
6—unassigned
19.7 ifOperStatus
1—up—Ready to pass packets
2—down
3—testing—In test mode
4—unknown—Status can not be determined
5—dormant
6—notPresent—Component is missing
7—lowerLayerDown—Down due to lower-layer interface state
19.8 ospfPacketType
1—hello
2—dbDescript
3—lsReq
4—lsUpdate
5—lsAck
6—nullPacket
19.9 ospfLsdbType
1—routerLink
2—networkLink
3—summaryLink
4—asSummaryLink
5—asExternalLink
6—multicastLink
7—nssaExternalLink
10—areaOpaqueLink
19.10 IANAItuProbableCause
1—aIS
2—callSetUpFailure
3—degradedSignal
4—farEndReceiverFailure
5—framingError
6—lossOfFrame
7—lossOfPointer
8—lossOfSignal
9—payloadTypeMismatch
10—transmissionError
11—remoteAlarmInterface
12—excessiveBER
13—pathTraceMismatch
14—unavailable
15—signalLabelMismatch
16—lossOfMultiFrame
17—receiveFailure
18—transmitFailure
19—modulationFailure
20—demodulationFailure
21—broadcastChannelFailure
22—connectionEstablishmentError
23—invalidMessageReceived
24—localNodeTransmissionError
25—remoteNodeTransmissionError
26—routingFailure
51—backplaneFailure
52—dataSetProblem
53—equipmentIdentifierDuplication
54—externalIFDeviceProblem
55—lineCardProblem
56—multiplexerProblem
57—nEIdentifierDuplication
58—powerProblem
59—processorProblem
60—protectionPathFailure
61—receiverFailure
62—replaceableUnitMissing
63—replaceableUnitTypeMismatch
64—synchronizationSourceMismatch
65—terminalProblem
66—timingProblem
67—transmitterFailure
68—trunkCardProblem
69—replaceableUnitProblem
70—realTimeClockFailure
71—antennaFailure
72—batteryChargingFailure
73—diskFailure
74—frequencyHoppingFailure
75—iODeviceError
76—lossOfSynchronisation
77—lossOfRedundancy
78—powerSupplyFailure
79—signalQualityEvaluationFailure
80—tranceiverFailure
81—protectionMechanismFailure
82—protectingResourceFailure
101—airCompressorFailure
102—airConditioningFailure
103—airDryerFailure
104—batteryDischarging
105—batteryFailure
106—commercialPowerFailure
107—coolingFanFailure
108—engineFailure
109—fireDetectorFailure
110—fuseFailure
111—generatorFailure
112—lowBatteryThreshold
113—pumpFailure
114—rectifierFailure
115—rectifierHighVoltage
116—rectifierLowFVoltage
117—ventilationsSystemFailure
118—enclosureDoorOpen
119—explosiveGas120—fire
121—flood
122—highHumidity
123—highTemperature
124—highWind
125—iceBuildUp
126—intrusionDetection
127—lowFuel
128—lowHumidity
129—lowCablePressure
130—lowTemperatue
131—lowWater
132—smoke
133—toxicGas
134—coolingSystemFailure
135—externalEquipmentFailure
136—externalPointFailure
151—storageCapacityProblem
152—memoryMismatch
153—corruptData
154—outOfCPUCycles
155—sfwrEnvironmentProblem
156—sfwrDownloadFailure
157—lossOfRealTimel
158—applicationSubsystemFailure
159—configurationOrCustomisationError
160—databaseInconsistency
161—fileError
162—outOfMemory
163—softwareError
164—timeoutExpired
165—underlayingResourceUnavailable
166—versionMismatch
201—bandwidthReduced
202—congestion
203—excessiveErrorRate
204—excessiveResponseTime
205—excessiveRetransmissionRate
206—reducedLoggingCapability
207—systemResourcesOverload
500—adapterError
501—applicationSubsystemFailture
502—bandwidthReducedX733
503—callEstablishmentError
504—communicationsProtocolError
505—communicationsSubsystemFailure
506—configurationOrCustomizationError
507—congestionX733
508—coruptData
509—cpuCyclesLimitExceeded
510—dataSetOrModemError
511—degradedSignalX733
512—dteDceInterfaceError
513—enclosureDoorOpenX733
514—equipmentMalfunction
515—excessiveVibration
516—fileErrorX733
517—fireDetected
518—framingErrorX733
519—heatingVentCoolingSystemProblem
520—humidityUnacceptable
521—inputOutputDeviceError
522—inputDeviceError
523—lanError
524—leakDetected
525—localNodeTransmissionErrorX733
526—lossOfFrameX733
527—lossOfSignalX733
528—materialSupplyExhausted
529—multiplexerProblemX733
530—outOfMemoryX733
531—ouputDeviceError
532—performanceDegraded
533—powerProblems
534—pressureUnacceptable
535—processorProblems
536—pumpFailureX733
537—queueSizeExceeded
538—receiveFailureX733
539—receiverFailureX733
540—remoteNodeTransmissionErrorX733
541—resourceAtOrNearingCapacity
542—responseTimeExecessive
543—retransmissionRateExcessive
544—softwareErrorX733
545—softwareProgramAbnormallyTerminated
546—softwareProgramError
547—storageCapacityProblemX733
548—temperatureUnacceptable
549—thresholdCrossed
550—timingProblemX733
551—toxicLeakDetected
552—transmitFailureX733
553—transmiterFailure
554—underlyingResourceUnavailable
555—versionMismatchX733
600—authenticationFailure
601—breachOfConfidentiality
602—cableTamper
603—delayedInformation
604—denialOfService
605—duplicateInformation
606—informationMissing
607—informationModificationDetectede
608—informationOutOfSequence
609—keyExpired
610—nonRepudiationFailure
611—outOfHoursActivity
612—outOfServic
613—proceduralError
614—unauthorizedAccessAttempt
615—unexpectedInformation
1024—other
19.11 IANAItuEventType
1—other
2—communicationsAlarm
3—qualityOfServiceAlarm
4—processingErrorAlarm
5—equipmentAlarm
6—environmentalAlarm
7—integrityViolation
8—operationalViolation
9—physicalViolation
10—securityServiceOrMechanismViolation
11—timeDomainViolation
19.12 ItuPerceivedSeverity
1—cleared
2—indeterminate
3—critical
4—major
5—minor
6—warning