Table of Contents
Alarm Troubleshooting
3.1 UCP Alarms
3.2 UCP Conditions
Alarm Troubleshooting
This chapter describes the alarms and conditions associated with the unified control plane (UCP). For procedures that clear UCP alarms, refer to Release 3.4 or later of the Cisco ONS 15454 Troubleshooting Guide or the Cisco ONS 15454 SDH Troubleshooting Guide.
3.1 UCP Alarms
Table 3-1 lists the UCP alarms.
Table 3-1 Alarm Descriptions
| Alarm |
Severity |
Description |
|
CKTDOWN
|
Critical
Service affecting
|
The UCP Circuit Down alarm applies to logical circuits created within the UCP between devices. It occurs when a signaling failure occurs across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 because the node serves as an edge device.
|
|
RSVP-HELLODOWN
|
Minor
Non-service affecting
|
The RSVP Hello Down alarm occurs when the hello protocol, which monitors UCP control channel status, is not available for reserving resources. The lack of availability can be caused by misconfiguration or loss of connectivity between the reporting node and its neighbor.
|
|
LMP-HELLODOWN
|
Minor
Non-service affecting
|
The LMP Hello Down alarm occurs when the hello protocol, which monitors UCP control channel status, is not available for link management. Unavailability can be caused by physical layer errors (such as cabling) or by control channel misconfiguration.
|
|
LMP-NDFAIL
|
Minor
Non-service affecting
|
The LMP Neighbor Detection Fail alarm occurs when neighbor detection within the UCP has failed. LMP-NDFAIL can be caused by physical failure (such as cabling) between the neighbors or by control channel misconfiguration.
|
3.2 UCP Conditions
Table 3-2 lists the UCP alarm conditions.
Table 3-2 Alarm Conditions
| Condition |
Raised When... |
Cleared When... |
|
UCP_CKT_DOWN
|
A provisioned circuit is temporarily or permanently down
|
The circuit becomes available.
|
|
UCP_NBR_DOWN
|
The Resource Reservation Protocol (RSVP) hello procedure indicates that a neighbor is down
|
The RSVP hello procedure declares that the neighbor is available.
|
|
UCP_CC_DOWN
|
The link management protocol (LMP) hello procedure indicates that the control channel is down
|
The LMP hello procedure indicates that the control channel is available.
|
|
UCP_ND_FAILED
|
The LMP neighbor discovery procedure fails
|
The control channel resets and the neighbor discovery procedure completes.
|
|
UCP_UNAUTH_CKTREQ
|
A node receives an unauthorized signaling request
|
This condition is not cleared (transient event).
|