SNMPv2 MIB

coldStart

Controller cold restart. Repeated spontaneous occurrence may indicate power or other hardware problems.

No action required. For information only.

warmStart

Controller warm restart.

authenticationFailure

SNMP request received with Community String or transport validation failure. Indicates possible provisioning error.

Entity MIB

entConfigChange

An internal object has been created.

No action required. For information only.

Ethernet Interface MIB

linkup

The port state transitioned to up due to an administrative action, a good incoming signal, and/or a good pluggable transmission module.

No action required. For information only.

linkdown

The port state transitioned to down due to an administrative action, incoming signal failure, and/or pluggable transmission module failure.

Check for disconnected cable or unequipped pluggable transmission module.

Refer to Procedure 5-3: Address VLNC40/42/42B, VLNC60/61/62, or VLNC64 circuit pack related failures.

FASTPATH PortMACLocking MIB

agentPortMACLockingViolation

A packet with a disallowed MAC address has been received on a locked port.

No action required. For information only.

FASTPATH Switching MIB

multipleUsersTrap

More than one CLI user is logged in with administrative access.

No action required. For information only. See the snmp-server enable traps multiuser parameter.

fanFailureTrap

The fan unit failed or is unequipped.

Refer to Procedure 5-19: Clear "fan shelf failed" or "hardware failure" alarm.

fanFailureClearTrap

The fan unit is installed and working properly.

No action required. For information only.

stpInstanceNewRootTrap

This machine is a new STP Root when there is more than one STP instance

No action required. For information only. See the snmp-server enable traps stpmode parameter.

stpInstanceTopologyChangeTrap

An STP topology change when there is more than one STP instance.

failedUserLoginTrap

A user terminal session login attempt failed (for example, wrong password, too many sessions).

No action required. For information only.

FASTPATH IF MIB

linkup

The port state transitioned to up due to an administrative action, a good incoming signal, and/or a good pluggable transmission module.

No action required. For information only.

linkdown

The port state transitioned to down due to an administrative action, incoming signal failure, and/or pluggable transmission module failure.

Check for disconnected cable or unequipped pluggable transmission module.

Refer to Procedure 5-3: Address VLNC40/42/42B, VLNC60/61/62, or VLNC64 circuit pack related failures.

Ethernet Ring Protection MIB

erpPort1Blocked

Ethernet ring protection on Port 1 is blocked.

No action required. For information only.

erpPort1Unblocked

Ethernet ring protection on Port 1 is unblocked.

erpPort2Blocked

Ethernet ring protection on Port 2 is blocked.

erpPort2Unblocked

Ethernet ring protection on Port 2 is unblocked.

erpMultipleRPLs

An ERP RPL Owner is receiving messages which are only generated by an RPL Owner, and there may only be one RPL Owner in the ring.

Identify which node(s) in the ring should not be set to be the RPL Owner, then change that node to not be the RPL Owner.

erpMultipleRPLsCleared

The multiple RPL condition cleared.

No action required. For information only.

erpWatchdogTimeout

An ERP node is not receiving periodic ERP R-APS PDUs. This may be caused by there being no RPL Owner in the ring or by misprovisioning of the ERP VLAN or md-level.

Determine which ERP node is misprovisioned and reprovision the required ERP node correctly.

erpWatchdogTimeoutClear

The Watchdog Timeout condition cleared.

No action required. For information only.

Ethernet OAM (802.1ag) MIB

dot1agCfmFaultAlarm

The Maintenance Association End Point (MEP) has detected an xconCCMdefect, errorCCMdefect, someRMEPCCMdefect, or someMACstatusDefect.

xconCCMdefect

If the CCMs are received from an incorrect MAID:

1. Verify that the receiving local MEP is configured correctly (MD name, MA name, and MD level).

2. Check dot1agCfmMepXconCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MAID.

3. Check network resources to find the remote MEP with that MAC address. Either it has been configured incorrectly (wrong MD name or MA name, which comprises the MAID; or wrong MD level) or the network connectivity is misconfigured to create an incorrect path to the local MEP.

4. If there is a concurrent someRMEPCCMdefect then also check for two remote MEP's with "swapped" configurations resulting in the intended one connected elsewhere, and the wrong one routed here.

If the CCMs are received from a lower level:

1. Verify that the local and remote MEPs have the same, correct, MD level configured.

2. Verify that there is no missing local MEP at a lower level, which should be receiving the CCMs.

dot1agCfmFaultAlarm (continued)

errorCCMdefect

If the received CCMs have an incorrect MEPID:

1. Verify correct local configuration of remote MEPs using the show ethoam remote-mepid command.

2. Check dot1agCfmMepErrorCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MEPID.

3. Check network resources to find the remote MEP with that MAC address, and correct its MEPID. If the MEPID is the same as the local MEP, then check the network for loops including misconfigured spanning trees or physical loopbacks.

If the received CCMs have the wrong period, then correct the configuration of each MEP so that the sending period is the same. Peer MEPs are expected to send CCMs with the same period.

dot1agCfmFaultAlarm (continued)

someRMEPCCMdefect

There is a loss of continuity with a remote MEP in the MA.

1. Check provisioning to ensure that all intended remote MEPs are configured locally, using the show ethoam remote-mepid command.

2. Check that each remote MEP is configured to enable CCM, using the show ethoam mep command, at the remote MEP's NE.

3. When the configuration is confirmed, look for faults in the network that would prevent traffic continuity. This can include further provisioning errors in network connectivity including VLAN configuration. There may be unprotected link faults or other hardware failures in the network.

someMACstatusDefect

A remote MEP is reporting its port is not up or that all remote MEPs have blocked ports.

Check the remote MEPs in the MA to find the problem (that is, why a port is not up or all have spanning tree blocks).

802.3 Link OAM MIB

LinkOAM Report cTCAEVT alarm

If the thresholds are non-zero, the link is degraded, causing symbol or frame errors locally or remotely.

Check the linkoam event log to determine which events are occurring, and where. Note that only non-zero threshold events are logged. Repair according to local procedures

LinkOAM Report cCLE alarm

There is a local or remote Link Failure, Dying Gasp, or Critical Event.

Check the linkoam event log to determine the type of event and where it is occurring. Refer to linkdown resolutions.

LinkOAM Report cSI alarm

The remote did not respond to a loopback request within 5 seconds.

No action required. Retry loopback. If it continues to be refused, check the remote node state.

LinkOAM Report cODNC alarm

Links are good, and link OAM is enabled, but the discovery state is not SEND_ANY for over 3 seconds.

May be caused by local and remote nodes both set to passive mode (at least one must be active), or by incompatible configuration. Check provisioning at local and remote node.

LinkOAM Report cExSER alarm

LinkOAM is enabled and the number of symbol errors in the last second exceeds or equals the configured threshold.

Check the linkoam event log to determine the type of event and where it is occurring. Refer to linkdown resolutions.

TSD-IM SNMP NE MIB

opticsimAlarmHldOverRaise

The system timing source is in holdover mode. This occurs when the system can not recover a clock signal from a reference source.

The reference source might have a signal failure or be of degraded quality. Fix reference source or select a working reference source. If there is a signal fail condition on the timing source perform appropriate corrective action. If SSM is supported on the timing source, check the SSM received on it. If it is not received or the received SSM is at/below quality level of DUS, perform any corrective action necessary in the adjacent nodes.

opticsimAlarmHldOverClear

The condition cleared.

No action required. For information only.

opticsIMAlarmUruRaise

The underlying resource is unavailable.

Verify that the SFP is inserted.

opticsIMAlarmUruClear

The condition cleared.

No action required. For information only.

opticsIMAlarmLossOfSignalRaise

The corresponding port has a loss of signal.

Verify the connection on the Ethernet port.

opticsIMAlarmLossOfSignalClear

The condition cleared.

No action required. For information only.

opticsimTLURaise

The system detected timing source unequipped condition

Equip the timing source. If the timing source has an SFP module, insert the corresponding SFP module. Otherwise, check the configuration to see if the correct port is being used for timing source.

opticsimTLUClear

The condition cleared.

No action required. For information only.

opticsimAlarmSynchronizationSignalFailRaise

The configured timing source has a signal fail condition.

Fix the source of timing or change it.

opticsimAlarmSynchronizationSignalFailClear

The condition cleared.

No action required. For information only.

opticsIMAlarmTCARaise

Network performance degraded below threshold levels.

Perform network analysis.

opticsimAlarmEthOAMLossOfContinuityRaise

The Maintenance Association End Point (MEP) has detected an someRMEPCCMdefect.

There is a loss of continuity with a remote MEP in the MA.

1. Check provisioning to ensure that all intended remote MEPs are configured locally, using the show ethoam remote-mepid command.

2. Check that each remote MEP is configured to enable CCM, using the show ethoam mep command, at the remote MEP's NE.

3. When the configuration is confirmed, look for faults in the network that would prevent traffic continuity. This can include further provisioning errors in network connectivity including VLAN configuration. There may be unprotected link faults or other hardware failures in the network.

opticsimAlarmEthOAMMisMergeConditionRaise

The Maintenance Association End Point (MEP) has detected an xconCCMdefect.

If the CCMs are received from an incorrect MAID:

1. Verify that the receiving local MEP is configured correctly (MD name, MA name, and MD level).

2. Check dot1agCfmMepXconCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MAID.

3. Check network resources to find the remote MEP with that MAC address. Either it has been configured incorrectly (wrong MD name or MA name, which comprises the MAID; or wrong MD level) or the network connectivity is misconfigured to create an incorrect path to the local MEP.

4. If there is a concurrent someRMEPCCMdefect then also check for two remote MEPs with "swapped" configurations resulting in the intended one connected elsewhere, and the wrong one routed here.

opticsimAlarmEthOAMUnexpectedMepIdRaise

The Maintenance Association End Point (MEP) has detected an errorCCMdefect.

If the received CCMs have an incorrect MEPID:

1. Verify correct local configuration of remote MEPs using the show ethoam remote-mepid command.

2. Check dot1agCfmMepErrorCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MEPID.

3. Check network resources to find the remote MEP with that MAC address, and correct its MEPID. If the MEPID is the same as the local MEP, then check the network for loops including misconfigured spanning trees or physical loopbacks.

opticsimAlarmEthOAMUnexpectedLevelRaise

The Maintenance Association End Point (MEP) has detected an xconCCMdefect.

If the CCMs are received from an incorrect MAID:

1. Verify that the receiving local MEP is configured correctly (MD name, MA name, and MD level).

2. Check dot1agCfmMepXconCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MAID.

3. Check network resources to find the remote MEP with that MAC address. Either it has been configured incorrectly (wrong MD name or MA name, which comprises the MAID; or wrong MD level) or the network connectivity is misconfigured to create an incorrect path to the local MEP.

4. If there is a concurrent someRMEPCCMdefect then also check for two remote MEP's with "swapped" configurations resulting in the intended one connected elsewhere, and the wrong one routed here.

If the CCMs are received from a lower level:

1. Verify that the local and remote MEPs have the same, correct, MD level configured.

2. Verify that there is no missing local MEP at a lower level, which should be receiving the CCMs.

opticsimAlarmEthOAMUnexpectedPeriodRaise

The Maintenance Association End Point (MEP) has detected an errorCCMdefect.

If the received CCMs have an incorrect MEPID:

1. Verify correct local configuration of remote MEPs using the show ethoam remote-mepid command.

2. Check dot1agCfmMepErrorCcmLastFailure to find the MAC address of the MEP which is the source of the problem, and its MEPID.

3. Check network resources to find the remote MEP with that MAC address, and correct its MEPID. If the MEPID is the same as the local MEP, then check the network for loops including misconfigured spanning trees or physical loopbacks.

If the received CCMs have the wrong period, then correct the configuration of each MEP so that the sending period is the same. Peer MEPs are expected to send CCMs with the same period.

opticsimAlarmEthOAMRDIRaise

Remote MEP reports a CCM alarm.

A possible unidirectional failure in network connectivity between the MEP and the remote MEP.

opticsimAlarmEthOAMUNPrRaise

The Maintenance Association End Point (MEP) has detected an incorrect priority.

If the received CCMs have an incorrect Priority.

1. Verify correct local configuration of remote MEPs using the show ethoam remote-mepid command.

2. If the received CCMs have the wrong priority, then correct the configuration of each MEP so that the sending priority is the same. Peer MEPs are expected to send CCMs with the same priority.

opticsimClientSignalFailRaise

An incoming Service OAM message (ETH-CSF) indicates that a Client Signal Failed (CSF) enabled Up-MEP on an UNI-N interface has detected a signal or equipment failure.

No action required. For information only.

opticsimClientSignalFailClear

The condition cleared.

No action required. For information only.

opticsimAlarmInputPowerDegradeRaise

The optical receive power measurement on pluggable transmission module is lower than the pre-set threshold.

Verify the connection on the pluggable transmission module.

opticsimAlarmInputPowerDegradeClear

The condition cleared.

No action required. For information only.

OPTICSIM-EQPT-MIB

opticsIMAlarmReplaceableUnitMissingRaise

The replaceable unit (SFP) is missing.

Verify if the SFP is inserted.

opticsIMAlarmReplaceableUnitMissingClear

The condition cleared.

No action required. For information only.

opticsIMAlarmReplaceableUnitProblemRaise

There is a problem in the replaceable unit.

Replace the SFP as the current one is unreadable.

opticsIMAlarmReplaceableUnitProblemClear

The condition cleared.

No action required. For information only.

OpticsIMAlarmReplaceableUnitTypeMismatchRaise

There is a mismatch in the replaceablt unit (SFP).

Verify if the SFP is of supported speed/type.

OpticsIMAlarmReplaceableUnitTypeMismatchClear

The condition cleared.

No action required. For information only.