States
Service states include an administrative state, operational state, and status attribute. Administrative states are used to manage service states. Administrative states use a status attribute to specify the change in service state. Entity states in Software Release 5.0 and later are based on the generic state model defined in Telcordia GR-1093-CORE, Issue 2 and ITU-T X.731.
The following table defines the administrative states and operational states supported by the Cisco ONS 15454 SDH.
 
Administrative State-Operational State
Definition
Unlocked-enabled
The entity is fully operational and will perform as provisioned.
Unlocked-disabled
The entity is not operational because of an autonomous event.
Locked-disabled
The entity is not operational because of an autonomous event and has also been manually removed from service.
Locked-enabled
The entity has been manually removed from service.
The following table defines the Secondary States (SSTs) supported by the ONS 15454 SDH.
 
Secondary State
Definition
automaticInService
The entity is delayed before transitioning to the Unlocked-enabled service state. The transition to Unlocked-enabled state depends on correction of conditions, or on a soak timer. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command.
disabled
The entity was manually removed from service and does not provide its provisioned functions. All services are disrupted; the entity is unable to carry traffic.
Note
CTC does not allow you to change an entity from the Unlocked-enabled service state to the Locked-enabled,disabled service state. You must first put the entity in the Locked-enabled,maintenance service state.
failed
The entity has a raised alarm or condition.
loopback
The entity is in loopback mode.
mismatchOfEquipment
An improper card is installed, a cross-connect card does not support an installed card, or an incompatible backplane is installed. For example, an installed card is not compatible with the card preprovisioning or the slot. This SST applies only to cards.
maintenance
The entity has been manually removed from service for a maintenance activity but still performs its provisioned functions. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command.
outOfGroup
The virtual concatenation (VCAT) member cross-connect is not used to carry VCAT group traffic. This state is used to put a member circuit out of the group and to stop sending traffic. Locked-enabled,outOfGroup only applies to the cross-connects on an end node where VCAT resides. The cross-connects on intermediate nodes are in the Locked-enabled,maintenance service state.
softwareDownload
The card is involved in a software download. This SST applies only to cards.
unassigned
The card is not provisioned in the database. This SST applies only to cards.
notInstalled
The card is not physically present (that is, an empty slot). This SST applies only to cards.
 

Copyright © 2002-2011, Cisco Systems, Inc. All rights reserved.