FILE DESCRIPTION     1/198 18-CRA 119 1170/1-V1 Uen A    

SNMP MIB Notifications

© Copyright Ericsson AB 2009. All rights reserved.

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner. 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

SmartEdge is a registered trademark of Telefonaktiebolaget L M Ericsson.
NetOp is a trademark of Telefonaktiebolaget L M Ericsson.

Contents

1SNMP MIB Notifications
1.1Setting up SNMP Alarm Models for Notifications
1.2Deleting SNMP Alarm Models for Notifications

2

AAA Notifications

3

Bridge Notifications

4

DHCP Notifications

5

Entity Notifications

6

Environmental Notifications
6.1Descriptions and Object Identifiers
6.2rbnFanStatusChange Example

7

IP Pool Notifications

8

L2TP Notifications

9

Link and Interface Notifications
9.1Descriptions and Object Identifiers
9.2rbnNElinkUp Examples
9.3rbnNElinkDown Example

10

RMON Notifications

11

Routing Notifications
11.1Descriptions and Object Identifiers
11.2ospfNbrStateChange Example
11.3vrrpTrapNewMaster Example
11.4Enable Notifications for VRRP-MIB Example
11.5vrrpTrapAuthFailure Example

12

System Management Notifications
12.1dot1agCfmFaultAlarm Example

13

System Resource Notifications


1   SNMP MIB Notifications

The SmartEdge router supports the notifications for IETF-standard Management Information Bases (MIBs) and enterprise MIBs described in the following sections.

Note:  
For a list of MIBs supported by the SmartEdge router, including enterprise MIBs, 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 your network, the examples may appear different from your system.

1.1   Setting up SNMP Alarm Models for Notifications

You can use ALARM-MIB to create alarm models to specify the types of alarms and alarm states to raise for existing notifications. To configure an alarm model:

  1. Use the snmp alarm command to enter the SNMP alarm model command mode.
  2. Use one of the following commands to set up the SNMP alarm model with additional parameters:
  3. Use the following show commands to display information about SNMP alarm models:
  4. Enable debugging for snmp alarm models by using the debug snmp mib alarm command.

1.2   Deleting SNMP Alarm Models for Notifications

2   AAA Notifications

Table 1 lists notifications generated by the router to indicate AAA notifications as defined in RBN-SUBSCRIBER-ACTIVE-MIB, RBN-TACACS-MIB, and RBN-RADIUS-MIB.

Table 1    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 raises this event when a RADIUS accounting server transitions to the down state. The system clears this event 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 raises this event when a RADIUS authorization server transitions to the down state. The system clears this event 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 raises this event when the subscriber session received one or more policy names from 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 raises this event when a TACACS+ authorization server transitions to the down state. The system clears this event 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.

Table 2    AAA Objects

Notification

Object

rbnRadiusAcctStateChange

RBN-RADIUS-MIB

rbnRadiusAcctSrvState:

  • 1. unknown—The state on initial creation.

  • 2. up—The server is responding.

  • 3. down—The server is not responding.

 

radiusAccServerAddress

IpAddress

 

radiusAccClientServerPortNumber

IpAddress

 

rbnRadiusClientPort

Unsigned32 (1024–65535)

 

rbnRadiusContext

SnmpAdminString (SIZE (1–63))

 

rbnRadiusReason:

  • 1. Responding—The server is responding.
    Valid for a transition to 'up'

  • 2. PacketTimeout—The server is not responding and a packet-level timeout has occurred.
    Valid for a transition to 'down'

  • 3. serverTimeout—The server is not responding and a server-level timeout has occurred.
    Valid for a transition to 'down'

  • 4. portDown—The physical port used to access the server has been shutdown.
    Valid for a transition to 'down'

 

rbnRadiusUsername

SnmpAdminString (SIZE (0–128))

rbnRadiusAuthStateChange

RBN-RADIUS-MIB

rbnRadiusAuthSrvState:

  • 1. unknown—The state on initial creation.

  • 2. up—The server is responding.

  • 3. down—The server is not responding.

 

radiusAuthServerAddress

IpAddress

 

radiusAuthClientServerPortNumber

IpAddress

 

rbnRadiusClientPort

Unsigned32 (1024–65535)

 

rbnRadiusContext

SnmpAdminString (SIZE (1–63))

 

rbnRadiusReason:

  • 1. Responding—The server is responding.
    Valid for a transition to 'up'

  • 2. PacketTimeout—The server is not responding and a packet-level timeout has occurred.
    Valid for a transition to 'down'

  • 3. serverTimeout—The server is not responding and a server-level timeout has occurred.
    Valid for a transition to 'down'

  • 4. portDown—The physical port used to access the server has been shutdown.
    Valid for a transition to 'down'

 

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:

  • 0—Unknown

  • 1—Ipv4

  • 2—Ipv6

  • 16—Dns

 

rbnTacacsServerAddress

Octet String (Size (0–255))

 

rbnTacacsServerPort

Unsigned32(0–65535)

 

rbnTacacsServerState:

  • 1. unknown—The state on initial creation.

  • 2. up—The server is responding.

  • 3. down—The server is not responding.

 

rbnTacacsServerReason:

  • 1. responding—The server is responding.
    Valid for a transition to 'up'

  • 2. packetTimeout—The server is not responding and a packet-level timeout has occurred.
    Valid for a transition to 'down'

  • 3. serverTimeout—The server is not responding and a server-level timeout has occurred.
    Valid for a transition to 'down'

  • 4. serverError—The server has an error resulting in a transition to down state.
    Valid for a transition to 'down'

 

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 RBN-BRIDGE-MIB.

Table 3    Bridge Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnBridgeCctStateEvent

1.3.6.1.4.1.2352.2.42.0.1

RBN-BRIDGE-MIB

The system raises this event when a loop has been detected (which locks the bridge circuit) and clears the event 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

RBN-BRIDGE-MIB

The system raises this event 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

RBN-BRIDGE-MIB

The system raises this event 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

(1)  The recommended severity level.

Table 4 describes the objects for bridge notifications.

Table 4    Bridge Objects

Notification

Objects and Values

rbnBridgeCctStateEvent

RBN-BRIDGE-MIB

rbnBridgeGroupName

SnmpAdminString (SIZE(1–32))

 

rbnBridgeCircuitDescriptor

SnmpAdminString (SIZE (1–255))

 

rbnBridgeCircuitStatus:

  • 1—blocked

  • 2—cleared

 

rbnBridgeGroupContextName

SnmpAdminString (SIZE(1–64))

 

rbnBridgeGroupName

SnmpAdminString (SIZE(1–32))

rbnBridgeNewRootEvent

RBN-BRIDGE-MIB

rbnBridgeGroupContextName

SnmpAdminString (SIZE(1–64))

 

rbnBridgeId

Integer32 (1–65535)

 

dot1dStpPortState:

  • 1—disabled

  • 2—blocking

  • l3—istening

  • l4—earning

  • 5—forwarding

  • 6—broken

 

rbnBridgePortPreviousState:

  • 1—deleted

  • 2—disabled

  • 3—blocked

  • 4—listening

  • 5—learning

  • 6—forwarding

rbnBridgeTopologyChangeEvent

RBN-BRIDGE-MIB

rbnBridgeGroupContextName

SnmpAdminString (SIZE(1–64))

 

rbnBridgeId

Integer32 (1–65535)

 

dot1dStpPortState:

  • 1—disabled

  • 2—blocking

  • l3—istening

  • l4—earning

  • 5—forwarding

  • 6—broken

 

rbnBridgePortPreviousState:

  • 1—deleted

  • 2—disabled

  • 3—blocked

  • 4—listening

  • 5—learning

  • 6—forwarding

 

dot1dStpPortState:

  • 1—disabled

  • 2—blocking

  • l3—istening

  • l4—earning

  • 5—forwarding

  • 6—broken

 

rbnBridgePortPreviousState:

  • 1—deleted

  • 2—disabled

  • 3—blocked

  • 4—listening

  • 5—learning

  • 6—forwarding

4   DHCP Notifications

Table 5 lists notifications generated by the router to indicate DHCP notifications as defined in RBN-DHCP-MIB.

Table 5    DHCP Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnDhcpIntfThresholdFallingThresholdMet

RBN-DHCP-MIB

A notification indicating that a per-interface falling threshold has been reached.

 

 

 

Event: None

Command: None

rbnDhcpIntfThresholdRisingThresholdMet

RBN-DHCP-MIB

A notification indicating that a per-interface rising threshold has been reached.

 

 

 

Event: None

Command: None

rbnDhcpCtxThresholdFallingThresholdMet

1.3.6.1.4.1.2352.2.30.0.3

RBN-DHCP-MIB

The system clears this event 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 (Context)

Major

Event: rbnDhcpCtxThresholdRisingThresholdMet

Command: None

rbnDhcpCtxThresholdRisingThresholdMet

1.3.6.1.4.1.2352.2.30.0.4

RBN-DHCP-MIB

The system raises this event 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 (Context)

Major

Event: rbnDhcpCtxThresholdFallingThresholdMet

Command: None

rbnDhcpRangeThresholdFallingThresholdMet

1.3.6.1.4.1.2352.2.30.0.5

RBN-DHCP-MIB

The system clears this event 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 (IP pool)

Major

Event: rbnDhcpRangeThresholdRisingThresholdMet

Command: None

rbnDhcpRangeThresholdRisingThresholdMet

1.3.6.1.4.1.2352.2.30.0.6

RBN-DHCP-MIB

The system raises this event 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 (IP pool)

Major

Event: rbnDhcpRangeThresholdFallingThresholdMet

Command: None

(1)  The recommended severity level.

Table 6 describes the objects for DHCP notifications.

Table 6    DHCP Objects

Notification

Objects and Values

rbnDhcpIntfThresholdFallingThresholdMet

RBN-DHCP-MIB

rbnDhcpIntfThresholdContextName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpIntfThresholdAvailable

Unsigned32

 

rbnDhcpIntfThresholdFallingThreshold

Unsigned32 (0–196608)

rbnDhcpIntfThresholdRisingThresholdMet

RBN-DHCP-MIB

rbnDhcpIntfThresholdContextName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpIntfThresholdAvailable

Unsigned32

 

rbnDhcpIntfThresholdRisingThreshold

Unsigned32 (0–196608)

rbnDhcpCtxThresholdFallingThresholdMet

RBN-DHCP-MIB

rbnDhcpCtxThresholdName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpCtxThresholdAvailable

Unsigned32

 

rbnDhcpCtxThresholdFallingThreshold

Unsigned32 (0–196608)

rbnDhcpCtxThresholdRisingThresholdMet

RBN-DHCP-MIB

rbnDhcpCtxThresholdName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpCtxThresholdAvailable

Unsigned32

 

rbnDhcpCtxThresholdRisingThreshold

Unsigned32 (0–196608)

rbnDhcpRangeThresholdFallingThresholdMet

RBN-DHCP-MIB

rbnDhcpRangeThresholdContextName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpRangeThresholdInterfaceName

SnmpAdminString (SIZE (1–80))

 

rbnDhcpRangeThresholdEndAddr

IpAddress

 

rbnDhcpRangeThresholdAvailable

Unsigned32

 

rbnDhcpRangeThresholdFallingThreshold

Unsigned32 (0–196608)

rbnDhcpRangeThresholdRisingThresholdMet

RBN-DHCP-MIB

rbnDhcpRangeThresholdContextName

SnmpAdminString (SIZE (0–63))

 

rbnDhcpRangeThresholdInterfaceName

SnmpAdminString (SIZE (1–80))

 

rbnDhcpRangeThresholdEndAddr

IpAddress

 

rbnDhcpRangeThresholdAvailable

Unsigned32

 

rbnDhcpRangeThresholdRisingThreshold

Unsigned32 (0–196608)

5   Entity Notifications

Table 7 lists notifications generated by the router to indicate entity notification as defined in RFC 2037, Entity MIB using SMIv2 and RBN-CARDMON-MIB and RBN-NOTIFY-ENHANCE-MIB.

Table 7    Entity Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

entConfigChange

1.3.6.1.2.1.47.2.0.1

ENTITY-MIB

The system generates this event when the entity configuration changes. It can be utilized by an 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:

  • coldStart

  • cardAlarm

Command: None

rbnNEentConfigChange

1.3.6.1.4.1.2352.2.36.0.1

RBN-NOTIFY-ENHANCE-MIB

The system generates this event 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:

  • coldStart

  • cardAlarm

Command: traps nemib {exclusive | non-exclusive}

rbnCardAlarm

1.3.6.1.4.1.2352.2.31.0.

RBN-CARDMON-MIB

The system raises or clears this event 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 raises or clears this event 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 raises or clears this notification when an SFP or XFP tranceiver changes status. The severity of this notification can be either “Major” or “Warning.” It will be cleared when the defective SFP or XFP tranceiver is replaced in the port.

 

Port

Major or Warning

Event: None

Command: system alarm tranceiver suppress

(1)  The recommended severity level.

Table 8 describes the objects for system management notifications.

Table 8    Entity Objects

Notification

Objects and Values

entConfigChange

ENTITY-MIB

See RFC 2037, Entity MIB using SMIv2

rbnNEentConfigChange

RBN-NOTIFY-ENHANCE-MIB

rbnNESlot

Unsigned32 (0–255)

 

rbnNECardName

DisplayString (SIZE (0–255))

 

rbnNECardOp:

  • 1—insert

  • 2—remove

  • 3—other

 

sysName

DisplayString (SIZE (0–255))

rbnCardAlarm

RBN-CARDMON-MIB

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

 

rbnCardAlarmId:

  • 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

 

rbnCardAlarmId:

  • 69—ethtransceiveraux1hi

  • 70—ethtransceiveraux1lo

  • 71—ethtransceiveraux2hi

  • 72—ethtransceiveraux2lo

  • 73—ethtransceiverlvcc5hi

  • 74—ethtransceiverlvcc5lo

  • 75—ethtransceiverlvcc3hi

  • 76—ethtransceiverlvcc3lo

  • 77—ethtransceiverlvcc2hi

  • 78—ethtransceiverlvcc2lo

 

rbnCardAlarmDateAndTime

Octet String (Size (8 | 11)

 

rbnCardAlarmDescription

SnmpAdminString (SIZE(0–64)

 

rbnCardAlarmProbableCause (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

 

The following are used with environmental alarm:

  • 70—RealTimeClockFailure

  • Values 83–100 are reserved for equipment alarm related probable causes

  • 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

  • Values 137–150 are reserved for environmental alarm related probable causes

  • 149—Customized

 

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

 

rbnCardAlarmSeverity:

  • 1—cleared

  • 2—critical

  • 3—major

  • 4—minor

  • 5—warning

rbnNECardAlarm

RBN-NOTIFY-ENHANCE-MIB

rbnCardAlarmServiceAffecting:

  • 1—yes

  • 2—no

 

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

 

rbnCardAlarmId:

  • 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

 

rbnCardAlarmType:

  • 1—other

  • 2—communicationsAlarm

  • 3—qualityOfServiceAlarm

  • 4—processingErrorAlarm

  • 5—equipmentAlarm

  • 6—environmentalAlarm

  • 7—integrityViolation

  • 8—operationalViolation

  • 9—physicalViolation

  • 10—securityServiceOrMechanismViolation

  • 11—timeDomainViolation

 

rbnCardAlarmDateAndTime

Date and time in the following format (with ranges):

  • year* 0–65536

  • month 1–12

  • day 1–31

  • hour 0–23

  • minutes 0–59

  • seconds 0–60 (use 60 for leap-second)

  • deci-seconds 0–9

  • direction from UTC '+' / '-'

  • hours from UTC* 0–13

  • minutes from UTC 0–59

Example output: 1992-5-26,13:30:15.0,-4:0

 

rbnCardAlarmDescription

SnmpAdminString (SIZE(0–64))

 

rbnCardAlarmProbableCause (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

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

 

The following are used with environmental alarm:

  • Values 83–100 are reserved for equipment alarm related probable causes

  • 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

  • Values 137–150 are reserved for environmental alarm related probable causes

  • 149—Customized

 

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

 

rbnCardAlarmSeverity:

  • 1—cleared

  • 2—critical

  • 3—major

  • 4—minor

  • 5—warning

 

rbnNECardName

DisplayString (SIZE (0–255))

 

sysName

DisplayString (SIZE (0–255))

rbnSfpAlarm

RBN-SFP-MIB

rbnSfpAlarmCardSlot

Unsigned32

 

rbnSfpAlarmPort

Unsigned32

 

AlarmId

Integer

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

 

rbnSfpAlarmSeverity

Integer

  • 1—cleared

  • 2—indeterminate

  • 3—critical

  • 4—major

  • 5—minor

  • 6—warning

 

rbnSfpAlarmType

Integer

5—equipmentAlarm

 

rbnSfpAlarmDateAndTime

OctetString

 

rbnSfpAlarmDescription

OctetString (0..64)

 

rbnSfpAlarmProbableCause (continued) 80—tranceiverFailure

Integer

6   Environmental Notifications

The following sections provide information about environmental notifications for the SmartEdge router.

6.1   Descriptions and Object Identifiers

Table 9 lists notifications generated by the router to indicate environmental notification as defined in RBN-ENVMON-MIB and RBN-SYS-RESOURCES-MIB.

Table 9    Environmental Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnFanStatusChange

1.3.6.1.4.1.2352.2.4.0.3

RBN-ENVMON-MIB

The system raises or clears 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:

  • normal—the fan or fans monitored by the test point are operational.

  • failed—the fan or fans monitored by the test point have failed.

  • absent—the fan or fans monitored by this test point is not present.

  • unknown—the test point are unable to monitor the fan or fans.

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 raises or clears this event when there is a change in power supply status.

Cause: The status of a power test point, with the following values:

  • normal—the power supply (or supplies) monitored by the test point is operational.

  • failed— then the power supply (or supplies) monitored by the test point has failed.

  • absent—then the power supply (or supplies) monitored by this test point is not present.

  • unknown— then the test point is unable to monitor the power supply (or supplies).

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 raises or clears 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

(1)  The recommended severity level.

Table 10 describes the objects for environmental notifications.

Table 10    Environmental Objects

Notification

Objects and Values

rbnFanStatusChange

RBN-ENVMON-MIB

rbnFanStatus:

  • 1—normal

  • 2—failed

  • 3—absent

  • 4—unknown

rbnPowerStatusChange

RBN-ENVMON-MIB

rbnPowerStatus:

  • 15—normal

  • 2—failed

  • 3—absent

  • 4—unknown

rbnSRPowerExceededEvent

RBN-SYS-RESOURCES-MIB

rbnSRPowerExceededStatus:

  • 1—normal

  • 2—failed

6.2   rbnFanStatusChange Example

If a fan fails in the system, an SNMP management station might display the following output:

*TRAP_v2c{AgIpAddr=155.53.0.21
SysUpTime=23128610
SnmpTrapOID=rbnFanStatusChange
MgrSvrErrStat=NO_ERROR
}VARLIST{rbnFanStatusTable{INDEX=1
rbnFanStatus{TYPE=enum
NAM=failed
NUM=2
}}}%

7   IP Pool Notifications

Table 11 lists notifications generated by the router to indicate IP pool; notifications are defined in RBN-IP-POOL-MIB.

Table 11    IP Pool Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnIpPoolThreshholdMet

1.3.6.1.4.1.2352.2.15.0.2

RBN-IPPOOL-MIB

The system raises this event 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

RBN-IPPOOL-MIB

The system raises this event 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

RBN-IPPOOL-MIB

The system raises this event 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

(1)  The recommended severity level.

Table 12 describes the objects for IP pool notifications.

Table 12    IP Pool Objects

Notification

Objects and Values

rbnIpPoolThreshholdMet

RBN-IPPOOL-MIB

rbnIpPoolContextName

SnmpAdminString (SIZE (0–63))

 

rbnIpPoolInterfaceName

SnmpAdminString (SIZE (0–127))

 

rbnIpPoolMask

IpAddress

 

rbnIpPoolAvailable

Unsigned32

 

rbnIpPoolThreshold

Unsigned32 (0–65535)

rbnIpPoolContextThreshholdMet

RBN-IPPOOL-MIB

rbnIpPoolContextName

SnmpAdminString (SIZE (0–63))

 

rbnIpPoolContextAvailable

Unsigned32

 

rbnIpPoolContextThreshold

Unsigned32

rbnIPPoolContextThreshholdPercentageMet

RBN-IPPOOL-MIB

rbnIpPoolContextName

SnmpAdminString (SIZE (0–63))

 

rbnIpPoolContextTotalSize

Unsigned32

 

rbnIpPoolContextAvailable

Unsigned32

 

rbnIpPoolContextThresholdPercentage

Integer32 (0–100)

8   L2TP Notifications

Table 13 lists notifications generated by the router to indicate L2TP notifications as defined in RBN-L2TP-MIB.

Table 13    L2TP Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnL2tpMibTunnelStateChange2

1.3.6.1.4.1.2352.2.28.0.2

RBN-L2TP-MIB

The system raises or clears this event 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

(1)  The recommended severity level.

Table 14 describes the objects for L2TP notifications.

Table 14    L2TP Objects

Notification

Objects and Values

rbnL2tpMibTunnelStateChange2

RBN-L2TP-MIB

rbnL2tpTCfgTunnelContext

SnmpAdminString (SIZE (0–80))

 

rbnL2tpMibTunnelState:

  • 0—Invalid

  • 1—Deleted

  • 2—Idle

  • 3—Created

  • 4—WaitAAA

  • 5—WaitCtlReply

  • 6—WaitCtlConn

  • 7—Established

 

rbnL2tpTCfgRemoteTunnelID

Unsigned32 (0–65535)

 

rbnL2tpMIBDisableTrap

TruthValue

9   Link and Interface Notifications

The following sections provide information about link and interface notifications for the SmartEdge router.

9.1   Descriptions and Object Identifiers

Table 15 lists notifications generated by the router to indicate link and interface notifications as described in RBN-NOTIFY-ENHANCE-MIB and RFC 2863, The Interfaces Group MIB, and RFC 2495, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types and RBN-ATM-PVC-OAM-MIB.

Table 15    Link and Interface Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

linkDown

1.3.6.1.6.3.1.1.5.3

IF-MIB

The system raises this notification when the link status of an interface is down.

Causes include:

  • A fiber is cut.

  • There is attenuation in the signal.

  • There is no frame structure in the signal transmitted by the upstream station.

  • The receiving end of the local station is faulty.

Check:

  • That the port is configured correctly.

  • That the no shutdown command is configured.

  • That the cables are plugged in properly.

  • If a link is down on the neighboring device.

  • If the port comes up when plugged into another working device.

  • System diagnostics for failed hardware.

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 raises 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:

  • A fiber is cut.

  • There is attenuation in the signal.

  • There is no frame structure in the signal transmitted by the upstream station.

  • The receiving end of the local station is faulty.

Check:

  • That the port is configured correctly.

  • That the no shutdown command is configured.

  • That the cables are plugged in properly.

  • If a link is down on the neighboring device.

  • If the port comes up when plugged into another working device.

  • System diagnostics for failed hardware.

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 clears this event when an interface link status is up.

Causes include:

  • The no shutdown command was configured on the port.

  • A cable was plugged in.

  • A port bounce occurred.

  • The system came back online.

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 clears this event 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:

  • The no shutdown command was configured on the port.

  • A cable was plugged in.

  • A port bounce occurred.

  • The system came back online.

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 raises or clears this event when the interface line status changes.

Causes include:

  • The configuration was added or modified for the circuit.

  • The circuit bounced.

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 raises or clears this event 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:

  • The configuration was added or modified for the circuit.

  • The circuit bounced.

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 raises or clears this event when the interface line status changes.

Causes include:

  • The configuration was added or modified for the circuit.

  • The circuit bounced.

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 raises or clears this event 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:

  • The configuration was added or modified for the circuit.

  • The circuit bounced.

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 raises or clears this event 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

(1)  The recommended severity level.

Table 16 describes the objects for link and interface notifications.

Table 16    Link and Interface Objects

Notification

Objects and Values

linkDown

IF-MIB

RFC 2863, The Interfaces Group MIB

ifIndex

Integer32 (1–2147483647)

 

ifAdminStatus:

  • 1—up—Ready to pass packets

  • 2—down

  • 3—testing—In test mode

 

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

rbnNElinkDown

RBN-NOTIFY-ENHANCE-MIB

ifIndex

Integer32 (1–2147483647)

 

ifAdminStatus:

  • 1—up—Ready to pass packets

  • 2—down

  • 3—testing—In test mode

 

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

 

ifSpeed

Gauge32

 

ifHighSpeed

Gauge32

 

rbnNECircuitId

DisplayString (SIZE (0–255))

 

sysName

DisplayString (SIZE (0–255))

linkUp

IF-MIB

See RFC 2863, The Interfaces Group MIB

ifIndex

Integer32 (1–2147483647)

 

ifAdminStatus:

  • 1—up—Ready to pass packets

  • 2—down

  • 3—testing—In test mode

 

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 state of lower-layer interfaces

rbnNElinkUp

RBN-NOTIFY-ENHANCE-MIB

ifIndex

Integer32 (1–2147483647)

 

ifAdminStatus:

  • 1—up—Ready to pass packets

  • 2—down

  • 3—testing—In test mode

 

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 state of lower-layer interfaces

 

ifSpeed

Gauge32

 

ifHighSpeed

Gauge32

 

rbnNECircuitId

DisplayString (SIZE (0–255))

 

sysName

DisplayString (SIZE (0–255))

dsx1LineStatusChange

DS1-MIB

RFC 2495, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

dsx1LineStatus—The various bit positions are:

  • 1—dsx1NoAlarm
    No alarm present

  • 2—dsx1RcvFarEndLOF
    Far-end LOF (Yellow Alarm)

  • 4—dsx1XmtFarEndLOF
    Near end sending LOF Indication

  • 8—dsx1RcvAIS
    Far end sending AIS

  • 16—dsx1XmtAIS
    Near end sending AIS

  • 32—dsx1LossOfFrame
    Near-end LOF (Red Alarm)

  • 64—dsx1LossOfSignal
    Near-end loss of signal

  • 128—dsx1LoopbackState
    Near end is looped

  • 256—dsx1T16AIS
    E1 TS16 AIS

  • 512—dsx1RcvFarEndLOMF
    Far end sending TS16 LOMF

  • 1024—dsx1XmtFarEndLOMF
    Near end sending TS16 LOMF

  • 2048—dsx1RcvTestCode
    Near end detects a test code

  • 4096—dsx1OtherFailure
    Any line status not defined here

  • 8192—dsx1UnavailSigState
    Near end in unavailable signal state

  • 16384—dsx1NetEquipOOS
    Carrier equipment out of service

  • 32768—dsx1RcvPayloadAIS
    DS2 payload AIS

  • 65536—dsx1Ds2PerfThreshold
    DS2 performance threshold exceeded

 

dsx1LineStatusLastChange

TimeStamp

rbnNEdsx1LineStatusChange

dsx1LineStatus—The various bit positions are:

RBN-NOTIFY-ENHANCE-MIB

  • 1—dsx1NoAlarm
    No alarm present

  • 2—dsx1RcvFarEndLOF
    Far-end LOF (Yellow Alarm)

  • 4—dsx1XmtFarEndLOF
    Near end sending LOF Indication

  • 8—dsx1RcvAIS
    Far end sending AIS

  • 16—dsx1XmtAIS
    Near end sending AIS

  • 32—dsx1LossOfFrame
    Near-end LOF (Red Alarm)

  • 64—dsx1LossOfSignal
    Near-end loss Of signal

  • 128—dsx1LoopbackState
    Near end is looped

  • 256—dsx1T16AIS
    E1 TS16 AIS

  • 512—dsx1RcvFarEndLOMF
    Far end sending TS16 LOMF

  • 1024—dsx1XmtFarEndLOMF
    Near end sending TS16 LOMF

  • 2048—dsx1RcvTestCode
    Near end detects a test code

  • 4096—dsx1OtherFailure
    any line status not defined here

  • 8192—dsx1UnavailSigState
    Near end in unavailable signal state

  • 16384—dsx1NetEquipOOS
    Carrier equipment out of service

  • 32768—dsx1RcvPayloadAIS
    DS2 payload AIS

  • 65536—dsx1Ds2PerfThreshold
    DS2 performance threshold exceeded

 

dsx1LineStatusLastChange

TimeStamp

 

rbnDsx1AlarmSeverity:

  • cleared

  • critical

  • major

  • minor

  • warning

 

rbnDsx1AlarmServiceAffecting:

  • yes

  • no

 

rbnNECircuitId

DisplayString (SIZE (0–255))

 

sysName

DisplayString (SIZE (0–255))

dsx3LineStatusChange

DS3-MIB

RFC 2496, Definitions of Managed Objects for the DS3/E3 Interface Type

dsx3LineStatus—The various bit positions are:

  • 1—dsx1NoAlarm
    No alarm present

  • 2—dsx1RcvFarEndLOF
    Receiving Yellow or Remote Alarm Indication

  • 4—dsx3XmitRAIAlarm
    Transmitting Yellow or Remote Alarm Indication

  • 8—dsx3RcvAIS
    Receiving AIS failure state

  • 16—dsx3XmitAIS
    Transmitting AIS

  • 32—dsx3LOF
    Receiving LOF failure state

  • 64—dsx3LOS
    Receiving LOS failure state

  • 128—dsx3LoopbackState
    Looping the received signal

  • 256—dsx3RcvTestCode
    Receiving a test pattern

  • 512—dsx3OtherFailure
    any line status not defined here

  • 1024—dsx3UnavailSigState
    Near end in unavailable signal state

  • 2048—dsx3NetEquipOOS
    Carrier equipment out of service

 

dsx3LineStatusLastChange

TimeStamp

rbnNEdsx3LineStatusChange

RBN-NOTIFY-ENHANCE-MIB

dsx3LineStatus—The various bit positions are:

  • 1—dsx3NoAlarm
    No alarm present

  • 2—dsx3RcvRAIFailure
    Receiving Yellow or Remote Alarm Indication

  • 4—dsx3XmitRAIAlarm
    Transmitting Yellow or Remote Alarm Indication

  • 8—dsx3RcvAIS
    Receiving AIS failure state

  • 16—dsx3XmitAIS
    Transmitting AIS

  • 32—dsx3LOF
    Receiving LOF failure state

  • 64—dsx3LOS
    Receiving LOS failure state

  • 128—dsx3LoopbackState
    Looping the received signal

  • 256—dsx3RcvTestCode
    Receiving a test pattern

  • 512—dsx3OtherFailure
    any line status not defined here

  • 1024—dsx3UnavailSigState
    Near End in unavailable signal state

  • 2048—dsx3NetEquipOOS
    Carrier equipment out of service

 

dsx3LineStatusLastChange

TimeStamp

 

rbnDsx3AlarmSeverity:

  • 1—cleared

  • 2—critical

  • 3—major

  • 4—minor

  • 5—warning

 

rbnDsx3AlarmServiceAffecting:

  • 1—yes

  • 2—no

 

rbnNECircuitId

DisplayString (SIZE (0–255))

 

sysName

DisplayString (SIZE (0–255))

rbnAtmPvcOamStatusStateChange

RBN-ATM-PVC-OAM-MIB

rbnAtmPvcOamStatusState:

  • 1—noOam

  • 2—oamUp—The ATM PVC OAM function is active, and no failure condition is detected on the circuit.

  • 3—oamDownLoopback—The ATM PVC OAM function is active, and F5 OAM loopback cell management has detected a fault on the circuit.

  • 4—oamDownAis—The ATM PVC OAM function is active, and the system received a VC-AIS cell, which indicates a fault on the circuit.

  • 5—oamDownRdi—The ATM PVC OAM function is active, and the system received a VC-RDI cell, which indicates a fault on the circuit.

9.2   rbnNElinkUp Examples

If Port 12/8 in SmartEdge-Lab1 system becomes operational, the CLI displays the following 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

9.3   rbnNElinkDown Example

If Port 5/2 in SmartEdge-Lab1 system becomes operational, the CLI might display the following 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

10   RMON Notifications

Table 17 lists notifications generated by the router to indicate RMON notifications as defined in RFC 2819, Remote Network Monitoring Management Information Base.

Table 17    RMON Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

fallingAlarm

1.3.6.1.2.1.16.0.2

RMON-MIB

The system clears 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

RMON-MIB

The system raises 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.

(1)  The recommended severity level.

Table 18 describes the objects for RMON notifications.

Table 18    RMON Objects

Notification

Objects and Values

fallingAlarm

RMON-MIB

See RFC 2819, Remote Network Monitoring Management Information Base

alarmIndex

 

alarmVariable

Object Identifier

 

alarmSampleType:

  • 1—absoluteValue

  • 2—deltaValue

 

alarmValue

Integer32

 

alarmRisingThreshold

Integer32

risingAlarm

RMON-MIB

See RFC 2819, Remote Network Monitoring Management Information Base

alarmIndex

Integer32

 

alarmVariable

Object Identifier

 

alarmSampleType:

  • 1—absoluteValue

  • 2—deltaValue

 

alarmValue

Integer32

 

alarmRisingThreshold

Integer32

11   Routing Notifications

The following sections provide information about routing notifications for the SmartEdge router.

11.1   Descriptions and Object Identifiers

Table 19 lists notifications generated by the router to indicate routing notifications as defined in RFC 4273, Definitions of Managed Objects for BGP-4 and RFC 4750, OSPF Version 2 MIB.

Table 19    Routing Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

bgpBackwardTransNotification

1.3.6.1.2.1.15.0.2

BGP4-MIB

The system raises this event when BGP FSM moves from a higher-numbered state to a lower-numbered state.

Possible causes:

  • Port flapping

  • Other problem establishing a BGP neighbor.

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 clears this event 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

ospfIfStateChange

1.3.6.1.2.1.14.16.2.1

OSPF-MIB

The system raises this trap when a change in the state of a nonvirtual OSPF interface occurs.

Cause: This trap should be generated when the interface state regresses (for example when it transitions DR to Down) or progresses to one of the following terminal states:

  • Point-to-Point

  • DR Other

  • DR

  • Backup

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-MIB

The system raises this event 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-MIB

The system raises 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-MIB

The system raises 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-MIB

The system raises this notification when a nonvirtual interface receives a packet from a router with configuration parameters that conflict with the receiving router's configuration parameters.(2)

Confirm that the configuration of the sending and receiving router are 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-MIB

The system raises this notification when a nonvirtual interface receives a packet from a router with configuration parameters that conflict with the receiving router's configuration parameters.(3)

Confirm that the configuration of the sending and receiving router are 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-MIB

The system raises 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-MIB

The system raises this notification when a 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-MIB

The system raises this event 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-MIB

The system raises this event 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-MIB

The system raises this event 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-MIB

The system raises this event 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-MIB

The system raises this trap 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-MIB

The system raises this event 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 recommended severity level.

(2)  the optionMismatch event causes a trap only if it prevents an adjacency from forming

(3)  the optionMismatch event causes a trap only if it prevents an adjacency from forming

Table 20 describes the objects for routing notifications.

Table 20    Routing Objects

Notification

Objects and Values

bgpBackwardTransNotification

BGP4-MIB

See RFC 4273, Definitions of Managed Objects for BGP-4

bgpPeerRemoteAddr

IpAddress

 

bgpPeerLastError

Error code and subcode seen by the peer

Octet String (Size (2))

 

bgpPeerState:

  • 1—idle

  • 2—connect

  • 3—active

  • 4—opensent

  • 5—openconfirm

  • 6—established

bgpEstablished Notification

BGP4-MIB

See RFC 4273, Definitions of Managed Objects for BGP-4

bgpPeerRemoteAddr

IpAddress

 

bgpPeerLastError

Error code and subcode seen by the peer

Octet String (Size (2))

 

bgpPeerState:

  • 1—idle

  • 2—connect

  • 3—active

  • 4—opensent

  • 5—openconfirm

  • 6—established

ospfIfStateChange

OSPF-MIB

See RFC 4750, OSPF Version 2 MIB

ospfRouterId—The originator of the trap

 

ospfIfIpAddress

IpAddress

 

ospfAddressLessIf

Integer32 (0–2147483647)

 

ospfIfState:

  • 1—down

  • 2—loopback

  • 3—waiting

  • 4—pointToPoint

  • 5—designatedRouter

  • 6—backupDesignatedRouter

  • 7—otherDesignatedRouter

ospfNbrStateChange

OSPF-MIB

See RFC 4750, OSPF Version 2 MIB

ospfRouterId

IpAddress

 

ospfNbrIpAddr

IpAddress

 

ospfNbrAddressLessIndex

Integer32 (0–2147483647)

 

ospfNbrRtrId

IpAddress

 

ospfNbrState:

  • 1—down

  • 2—attempt

  • 3—init

  • 4—twoWay

  • 5—exchangeStart

  • 6—exchange

  • 7—loading

  • 8—full

ospfVirtIfStateChange

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtIfAreaId

IpAddress

 

ospfVirtIfNeighbor

IpAddress

 

ospfVirtIfState:

  • 1—down

  • 4—pointToPoint

ospfVirtNbrStateChange

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtNbrArea

IpAddress

 

ospfVirtNbrRtrId

IpAddress

 

ospfVirtNbrState

INTEGER:

  • 1—down

  • 2—attempt

  • 3—init

  • 4—twoWay

  • 5—exchangeStart

  • 6—exchange

  • 7—loading

  • 8—full

ospfIfConfigError

OSPF-MIB

ospfRouterId

IpAddress

 

ospfIfIpAddress

IpAddress

 

ospfAddressLessIf

InterfaceIndexOrZero

 

ospfPacketSrc

IpAddress

 

ospfConfigErrorType

INTEGER:

  • 1—badVersion

  • 2—areaMismatch

  • 3—unknownNbmaNbr

  • 4—unknownVirtualNbr

  • 7—netMaskMismatch

  • 8—helloIntervalMismatch

  • 9—deadIntervalMismatch

  • 10—optionMismatch

  • 11—mtuMismatch

  • 12—duplicateRouterId

  • 13—noError

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfVirtIfConfigError

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtIfAreaId

IpAddress

 

ospfVirtIfNeighbor

IpAddress

 

ospfConfigErrorType

INTEGER:

  • 1—badVersion

  • 2—areaMismatch

  • 3—unknownNbmaNbr

  • 4—unknownVirtualNbr

  • 7—netMaskMismatch

  • 8—helloIntervalMismatch

  • 9—deadIntervalMismatch

  • 10—optionMismatch

  • 11—mtuMismatch

  • 12—duplicateRouterId

  • 13—noError

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfIfAuthFailure

OSPF-MIB

ospfRouterId

IpAddress

 

ospfAddressLessIf

InterfaceIndexOrZero

 

ospfPacketSrc

IpAddress

 

ospfConfigErrorType

INTEGER:

  • 5—authTypeMismatch

  • 6—authFailure

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfVirtIfAuthFailure

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtIfAreaId

IpAddress

 

ospfVirtIfNeighbor

IpAddress

 

ospfConfigErrorType

INTEGER:

  • 5—authTypeMismatch

  • 6—authFailure

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfIfRxBadPacket

OSPF-MIB

ospfRouterId

IpAddress

 

ospfIfIpAddress

IpAddress

 

ospfAddressLessIf

InterfaceIndexOrZero

 

ospfPacketSrc

IpAddress

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfVirtIfRxBadPacket

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtIfAreaId

IpAddress

 

ospfVirtIfNeighbor

IpAddress

 

ospfPacketType

INTEGER:

  • 1—hello

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

  • 5—lsAck

  • 6—nullPacket

ospfTxRetransmit

OSPF-MIB

ospfRouterId

IpAddress

 

ospfIfIpAddress

IpAddress

 

ospfAddressLessIf

InterfaceIndexOrZero

 

ospfNbrRtrId

IpAddress

 

ospfPacketType

INTEGER:

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

 

ospfLsdbType

INTEGER:

  • 1—routerLink

  • 2—networkLink

  • 3—summaryLink

  • 4—asSummaryLink

  • 5—asExternalLink

  • 6—multicastLink

  • 7—nssaExternalLink

  • 10—areaOpaqueLink

 

ospfLsdbLsid

IpAddress

 

ospfLsdbRouterId

IpAddress

ospfVirtIfTxRetransmit

OSPF-MIB

ospfRouterId

IpAddress

 

ospfVirtIfAreaId

IpAddress

 

ospfVirtIfNeighbor

IpAddress

 

ospfPacketType

INTEGER:

  • 2—dbDescript

  • 3—lsReq

  • 4—lsUpdate

 

ospfLsdbType

INTEGER:

  • 1—routerLink

  • 2—networkLink

  • 3—summaryLink

  • 4—asSummaryLink

  • 5—asExternalLink

  • 6—multicastLink

  • 7—nssaExternalLink

  • 10—areaOpaqueLink

 

ospfLsdbLsid

IpAddress

 

ospfLsdbRouterId

IpAddress

ospfOriginateLsa

OSPF-MIB

ospfRouterId

IpAddress

 

ospfLsdbAreaId

IpAddress

 

ospfLsdbType

INTEGER:

  • 1—routerLink

  • 2—networkLink

  • 3—summaryLink

  • 4—asSummaryLink

  • 5—asExternalLink

  • 6—multicastLink

  • 7—nssaExternalLink

  • 10—areaOpaqueLink

 

ospfLsdbLsid

IpAddress

 

ospfLsdbRouterId

IpAddress

ospfMaxAgeLsa

OSPF-MIB

ospfRouterId

IpAddress

 

ospfLsdbAreaId

IpAddress

 

ospfLsdbType

INTEGER:

  • 1—routerLink

  • 2—networkLink

  • 3—summaryLink

  • 4—asSummaryLink

  • 5—asExternalLink

  • 6—multicastLink

  • 7—nssaExternalLink

  • 10—areaOpaqueLink

 

ospfLsdbLsid

IpAddress

 

ospfLsdbRouterId

IpAddress

vrrpTrapNewMaster

VRRP-MIB

vrrpOperMasterIpAddr

IpAddress

vrrpTrapAuthFailure

VRRP-MIB

vrrpTrapPacketSrc

IpAddress

 

vrrpTrapAuthErrorType

INTEGER:

  • 1—invalidAuthType

  • 2—authTypeMismatch

  • 3—authFailure

11.2   ospfNbrStateChange Example

If the OSPF neighbor state changes to the initial state for neighbor router 2.2.2.2, the CLI 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)

11.3   vrrpTrapNewMaster Example

If the VRRP state transitions to Master for router 2.2.2.2, the CLI output displays:

From: 2.2.2.2
sysUpTime.0 = 01:34:47.59
snmpTrapOID.0 = vrrpTrapNewMaster
vrrpOperMasterIpAddr.67108865.3 = 10.1.1.1

11.4   Enable Notifications for VRRP-MIB Example

To enable notifications for VRRP-MIB by using the CLI, enter the following commands:

[local]jazz#config
[local]jazz(config)#snmp server
[local]jazz(config-snmp-server)#traps vrrpmib

To enable the VRRP-MIB notifications by using your SNMP management tool, set the vrrpNotificationCntl object to 1: enabled. To disable VRRP-MIB notifications by using the SNMP management tool, set the vrrpNotificationCntl object to 2: disabled.

11.5   vrrpTrapAuthFailure Example

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 CLI displays the following output:

From: 2.2.2.2
sysUpTime.0 = 01:15:37.98
snmpTrapOID.0 = vrrpTrapAuthFailure
vrrpTrapPacketSrc = 1.1.1.10
vrrpTrapAuthErrorType = authFailure(3)

12   System Management Notifications

Table 21 lists notifications generated by the router to indicate system management notification as defined in RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) and RBN-BULKSTATS-MIB.

Table 21    System Management Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

authenticationFailure

1.3.6.1.6.3.1.1.5.5

SNMPv2-MIB

The system raises this event 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 raises this event when the SNMP agent restarts.

Cause: One of the following can cause SNMP to restart:

  • Process restart

  • XCRP switchover

  • Chassis reload

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.

pingTestFailed

The system raises this event 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.

Use the show snmp ping result command to show information about what caused the failure.

Node

Informational

Event: none.

Command: show snmp ping, snmp ping.

pingTestCompleted

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.

dot1agCfmFaultAlarm

1.3.111.2.802.1.1.8.0.1

IEEE8021-CFM-MIB

Description: The system raises this alarm when a maintenance association endpoint (MEP) has a persistent defect condition. It sends the highest priority defect with the OID of the MEP that has caused the defect.

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 and the value of the dot1agCfmMepIdentifier object identifies the MEP reporting this defect.

Only 1 local MEP is allowed per maintenance association in a working condition, so the MEP ID always stays at zero.

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 raises this 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.

(1)  The recommended severity level.

Table 22 describes the objects for system management notifications.

Table 22    System Management Notification Objects

Notification

Objects and Values

authenticationFailure

SNMPv2-MIB

See RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

coldStart

SNMPv2-MIB

See RFC 3418, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

dot1agCfmFaultAlarm

IEEE8021-CFM-MIB

dot1agCfmMepHighestPrDefect:

  • 0—none

  • 1—defRDICCM

  • 2—defMACstatus

  • 3—defRemoteCCM

  • 4—defErrorCCM

  • 5—defXconCCM

pingTestFailed

PING-MIB

pingCtlTargetAddressType

InetAddressType:

  • 0—unknown

  • 1—ipv4

  • 16—dns

 

pingCtlTargetAddress

InetAddress

Octet String (Size (0..255))

 

pingResultsOperStatus:

3—completed

 

pingResultsIpTargetAddressType

InetAddressType:

  • 0—unknown

  • 1—ipv4

  • 16—dns

 

pingResultsIpTargetAddress

InetAddress

Octet String (Size (0..255))

 

pingResultsMinRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsMaxRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsAverageRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsProbeResponses

Gauge32

Implicit Integer (0..4294967295)

 

pingResultsSentProbes

Gauge32

Implicit Integer (0..4294967295)

 

pingResultsRttSumOfSquares

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsLastGoodProbe

DateAndTime

Octet String (SIZE (8 | 11))

pingTestCompleted

PING-MIB

pingCtlTargetAddressType

InetAddressType:

  • 0—unknown

  • 1—ipv4

  • 16—dns

 

pingCtlTargetAddress

InetAddress

Octet String (Size (0..255))

 

pingResultsOperStatus:

3—completed

 

pingResultsIpTargetAddressType

InetAddressType:

  • 0—unknown

  • 1—ipv4

  • 16—dns

 

pingResultsIpTargetAddress

InetAddress

Octet String (Size (0..255))

 

pingResultsMinRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsMaxRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsAverageRtt

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsProbeResponses

Gauge32

Implicit Integer (0..4294967295)

 

pingResultsSentProbes

Gauge32

Implicit Integer (0..4294967295)

 

pingResultsRttSumOfSquares

Unsigned32

Implicit Integer (0..4294967295)

 

pingResultsLastGoodProbe

DateAndTime

Octet String (SIZE (8 | 11))

rbnBulkStatsTrfrFail2

RBN-BULKSTATS-MIB

pingCtlTargetAddress

InetAddress

Octet String (Size (0..255))

 

pingResultsOperStatus:

  • 1—enabled

  • 2—disabled

  • 3—completed

 

pingResultsIpTargetAddressType

InetAddressType:

  • 0—unknown

  • 1—ipv4

  • 2—ipv6

  • 16—dns

12.1   dot1agCfmFaultAlarm Example

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. In this case, there is no persistent defect condition because dot1agCfmMepHighestPrDefect.1.1.0 is set to none(0), which means that no defect is present:

Community: public@local
From: 10.12.129.29
sysUpTime.0 = 04:17:04.81
snmpTrapOID.0 = dot1agCfmFaultAlarm
dot1agCfmMepHighestPrDefect.1.1.0 = none(0)

13   System Resource Notifications

Table 23 lists notifications generated by the router to indicate system resource notifications as defined in the RBN-CONFIG-MIB and RBN-SYS-RESOURCES-MIB.

Table 23    System Resource Notifications

Event and OID

Description and Cause

Recommended Action

Reporting Module

Severity(1)

Related Events and Commands

rbnSRProcessEvent

1.3.6.1.4.1.2352.2.24.0.1

RBN-SYS-RESOURCES-MIB

The system raises this event when a process stops and clears this event when it 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 raises this event when the value of the rbnSRStorageStatus object for a device changes to failed.

Possible causes:

  • Card exceeded the supported number of times it can read and write data

  • Other hardware failure

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 raises this event 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 raises this event when it completes a configuration job.

Cause: The configuration has completed loading.

None; this is for information only.

Controller

Minor

Event: None

Command: None

(1)  The recommended severity level.

Table 24 describes the objects for system resource notifications.

Table 24    System Resource Objects

Notification

Objects and Values

rbnSRProcessEvent

RBN-SYS-RESOURCES-MIB

rbnSRProcessNotifyPID

Unsigned32 (0–2147483647)

 

rbnSRProcessNotifyEventCause:

  • 1—firstStart

  • 2—hangup

  • 3—interrupt

  • 4—quit

  • 5—illegalInstruction

  • 6—traceTrap

  • 7—abort

  • 8—emt

  • 9—floatingPointException

  • 10—kill

  • 11—busError

  • 12—segmentFault

  • 13—systemCallError

  • 14—pipeError

  • 15—alarmClock

  • 16—softwareTermination

  • 17—urgentConditionOnIOChannel

  • 18—stopNotFromTty

  • 19—stopFromTty

  • 20—continueStopped

  • 21—childExit

  • 22—ttyInput

  • 23—ttyOutput

  • 24—inputOutput

  • 25—exceededCpuTime

  • 26—exceededFileSize

  • 27—virtualAlarm

  • 28—profilingAlarm

  • 29—windowResize

  • 30—infoRequest

  • 31—userDefined1

  • 32—userDefined2

  • 33—powerFailRestart

  • 34—unknown

 

rbnSRProcessNotifyEventType:

  • 1—death

  • 2—birth

 

rbnSRProcessNumOfSpawn

Unsigned32 (0–2147483647)

rbnSRStorageFailedEvent

RBN-SYS-RESOURCES-MIB

rbnSRStorageDescr

SnmpAdminString (SIZE (0–64))

 

rbnSRStorageMedia:

  • 1—other

  • 2—hardDisk

  • 3—flashMemory

 

rbnSRStorageSlot

Unsigned32 (0–255)

rbnSRSwitchoverEvent

RBN-SYS-RESOURCES-MIB

None

rcfJobCompleted

RBN-CONFIG-FILE-MIB

rcfJobResult:

  • 0—success

  • 1—other

  • 2—noMemory

  • 3—parse

  • 4—io

  • 5—access

 

rcfJobErrorMsgs

SnmpAdminString