This appendix describes the administrative and service states for Cisco ONS 15454 SDH cards, ports, and cross-connects. For circuit state information, see Chapter 12, "Circuits and Tunnels." Administrative and service 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.
Service states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or more Secondary States (SST). Table B-1 lists the service state PSTs and PSTQs supported by the ONS 15454 SDH.
Table B-1 ONS 15454 SDH Service State Primary States and Primary State Qualifiers
Primary State, Primary State Qualifier
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.
Table B-2 defines the SSTs supported by the ONS 15454 SDH.
Table B-2 ONS 15454 SDH Secondary States
Secondary State
Definition
automaticInService
The entity is delayed before transitioning to the Unlocked-enabled service state. The transition to the Unlocked-enabled state depends on the 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 STM-N ports and connections in the disabled state continue to send an Multiplex Section - Alarm Indication Signal Line (MS-AIS).
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.
B.2 Administrative States
Administrative states are used to manage service states. Administrative states consist of a PST and an SST. Table B-3 lists the administrative states supported by the ONS 15454 SDH. See Table B-2 for SST definitions.
Note When an entity is put in the Locked,maintenance administrative state, the ONS 15454 SDH suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnUnlocked,MaintenancePorts to TRUE on the NE Defaults tab.
Note A change in the administrative state of an entity does not change the service state of supporting or supported entities.
Table B-3 ONS 15454 SDH Administrative States
Administrative State (PST,SST)
Definition
Unlocked
Puts the entity in service.
Unlocked,automaticInservice
Puts the entity in automatic in-service.
Locked,disabled
Removes the entity from service and disables it.
Locked,maintenance
Removes the entity from service for maintenance.
Locked,outOfGroup
(VCAT circuits only) Removes a VCAT member cross-connect from service and from the group of members.
B.3 Service State Transitions
This section describes the transition from one service state to the next for cards, ports, and cross-connects. A service state transition is based on the action performed on the entity.
B.3.2 Port and Cross-Connect Service State Transitions
Table B-5 lists the port and cross-connect service state transitions. Port states do not impact cross-connect states with one exception. A cross-connect in the Unlocked-disabled,automaticInService service state cannot transition autonomously into the Unlocked-enabled service state until the parent port is in the Unlocked-enabled service state.
You cannot transition a port from the Unlocked-enabled service state to the Locked-enabled,disabled state. You must first transition the port to the Locked-enabled,maintenance state. Once a port is in the Locked-enabled,maintenance state, the NODE.general.AllowServiceAffectingPortChangeToDisabled default setting of TRUE allows you to put a port in Locked-enabled,disabled even if the following conditions exist:
•The port is a timing source.
•The port is used for line, section, or tunneling DCC.
•The port supports 1+1 protection or multidirectional multiplex section-shared protection ring (MS-SPRing).
•Cross-connects are present on the port.
•Overhead connections or overhead terminations are in use (such as, express or local orderwire, or user data channels).
To change this behavior so that you cannot put a port in Locked-enabled,disabled if any of these conditions exist, set the NODE.general.AllowServiceAffectingPortChangeToDisabled default setting to FALSE. For the procedure to change node defaults, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.
The following ports do not support all of the service states listed in Table B-5:
•E-Series Ethernet ports do not support service states; these ports are either enabled or disabled.
•FC_MR-4 ports support the Unlocked-enabled; Locked-enabled,disabled; and Locked-enabled,maintenance service states; they do not support the Unlocked-disabled,automaticInService service state.
Note Deleting a port or cross-connect removes the entity from the system. The deleted entity does not transition to another service state.
Table B-5 ONS 15454 SDH Port and Cross-Connect Service State Transitions
Current Service State
Action
Next Service State
Unlocked-enabled
Put the port or cross-connect in the Locked,maintenance administrative state.
Locked-enabled,maintenance
Put the port or cross-connect in the Unlocked,automaticInService administrative state.
Put the port or cross-connect in the Unlocked administrative state.
Unlocked-enabled
Put the port or cross-connect in the Unlocked,automaticInService administrative state.
Unlocked-disabled,automaticInService
Put the port or cross-connect in Locked,maintenance.
Locked-enabled,maintenance
Put the VCAT cross-connect in the Locked,outOfGroup administrative state.
Locked-enabled,maintenance & outOfGroup
Put the VCAT member in the Locked,outOfGroup administrative state.
Locked-enabled,maintenance & outOfGroup
Locked-enabled,loopback & maintenance
Release the loopback.
Note While in Locked-enabled, loopback & maintenance service state, both Cisco Transport Controller (CTC) and Transaction Language One (TL1) allow a cross-connect to be deleted, which also removes the loopback. This applies only to the cross-connect, not the ports.
Locked-enabled,maintenance
Alarm/condition is raised.
Locked-disabled,failed & loopback & maintenance
Locked-disabled,failed & loopback & maintenance & outOfGroup for a VCAT member
Put the port or cross-connect in the Unlocked administrative state.
Unlocked-enabled
Put the port or cross-connect in the Unlocked,automaticInService administrative state.
Unlocked-disabled,automaticInService
Put the port or cross-connect in the Locked,disabled.
Locked-enabled,disabled
Locked-enabled,disabled & outOfGroup for a VCAT cross-connect
Put the port or cross-connect in a loopback.
Locked-enabled,loopback & maintenance
Put the VCAT cross-connect in the Locked,outOfGroup administrative state.
Locked-enabled,maintenance & outOfGroup
Alarm/condition is raised.
Locked-disabled,failed & maintenance
Locked-disabled,failed & maintenance & outOfGroup for a VCAT member
Locked-enabled,maintenance & outOfGroup
Alarm/condition is raised.
Locked-disabled,failed & maintenance & outOfGroup
1For a VCAT member, an Unlocked-enabled to Unlocked-disabled,automaticInService transition will not occur with a Loss of Multiframe (LOM) or Sequence Mismatch (SQM) condition on the member.
B.3.3 Pluggable Equipment Service State Transitions
The service state transitions for pluggable equipment are the same as for other equipment with the exceptions listed in Table B-6.
Note Pluggable equipment (pluggable interface modules [PIMs] and pluggable port modules [PPMs]) will transition out of the UAS state when inserted if the software can read the EEPROM and identify information on the pluggable equipment. If the software cannot read the pluggable equipment, the equipment is considered invalid and will not transition out of the UAS state.
Table B-6 ONS 15454 SDH Pluggable Equipment Service State Transitions
Current Service State
Action
Next Service State
Unlocked-enabled
Reset the pluggable equipment.
Unlocked-enabled
Provision an unsupported service rate.
Unlocked-disabled,mismatchOfEquipment
Pluggable equipment does not work with the board configuration.