This appendix describes the administrative and service states for Cisco ONS 15454 dense wavelength division multiplexing (DWDM) cards, optical payload ports, out-of-band optical supervision channel (OSC) ports, optical channel network connections (OCHNC), and transponder/muxponder cards and ports. Software Release 5.0 states are based on the generic state model defined in Telcordia GR-1093-Core, Issue 2 and ITU-T X.731.
C.1 Service States
Service states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or more Secondary States (SST). Table C-1 lists the ANSI and ETSI service state PSTs and PSTQs supported by the ONS 15454.
Table C-1 ONS 15454 Service State Primary States and Primary State Qualifiers
ANSI Primary State, Primary State Qualifier
ETSI Primary State, Primary State Qualifier
Definition
IS-NR (In-Service and Normal)
Unlocked-enabled
The entity is fully operational and will perform as provisioned.
OOS-AU (Out-of-Service and Autonomous)
Unlocked-disabled
The entity is not operational because of an autonomous event.
OOS-AUMA (Out-of-Service and Autonomous Management)
Locked-disabled
The entity is not operational because of an autonomous event and has also been manually removed from service.
OOS-MA (Out-of-Service and Management)
Locked-enabled
The entity has been manually removed from service.
Table C-2 defines the ANSI and ETSI SSTs supported by the ONS 15454.
Table C-2 ONS 15454 Secondary States
ANSI Secondary State
ETSI Secondary State
Definition
AINS
automaticInService
The entity is delayed before transitioning to the IS-NR (ANSI)/Unlocked-enabled (ETSI) service state. The transition to IS-NR/Unlocked-enabled depends on correction of conditions. 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.
DSBLD
disabled
The entity was manually removed from service and does not provide its provisioned functions. All services are disrupted; unable to carry traffic.
MEA
mismatchOfEquipment
An improper card is installed. For example, an installed card is not compatible with the card pre-provisioning or the slot. This SST applies only to cards.
MT
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.
SWDL
softwareDownload
The card is involved in a software and database download. This SST applies only to cards.
UAS
unassigned
The card is not provisioned in the database. This SST applies only to cards.
UEQ (Unequipped)
notInstalled
The card is not physically present (that is, an empty slot). This SST applies only to cards.
C.2 Administrative States
Administrative states are used to manage service states. Administrative states consist of a PST and an SST. Table C-3 lists the ANSI and ETSI administrative states supported by the ONS 15454. See Table C-2 for SST definitions.
Note A change in the administrative state of an entity does not change the service state of supporting or supported entities.
Table C-3 ONS 15454 Administrative States
ANSI Administrative State (PST,SST)
ETSI Administrative State (PST,SST)
Definition
IS
Unlocked
Puts the entity in-service.
IS,AINS
Unlocked,automaticInService
Puts the entity in automatic in-service.
OOS,DSBLD
Locked,disabled
Removes the entity from service and disables it.
OOS,MT
Locked,maintenance
Removes the entity from service for maintenance.
C.3 Service State Transitions
This section describes the transition from one service state to the next state for DWDM cards, optical payload ports, OSC ports, OCHNCs, and transponder/muxponder cards and ports. A service state transition is based on the action performed on the entity and any autonomous activity.
C.3.1 DWDM Card Service State Transitions
Table C-4 lists ANSI and ETSI service state transitions for AD-1B-xx.x, AD-4B-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, OSC-CSM, OSCM, OPT-BST, OPT-PRE, 4MD-xx.x, 32WSS, 32MUX-O, and 32DMX-O cards.
Table C-4 ONS 15454 Optical Unit Service State Transitions
1The transponder and muxponder cards have both client and trunk ports. To bring up service, it is not necessary that both the client side and trunk side have to be in the IS-NR (ANSI)/Unlocked-enabled (ETSI) service state.
2In a client-side facility loopback, the client port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the remaining client and trunk ports can be in any other service state. In a client-side terminal loopback on transponder cards, the client port is in the OOS-MA,LPBK & MT service state and the trunk ports are in IS-NR (ANSI)/Unlocked-enabled (ETSI). For client-side terminal loopbacks on muxponder cards, the client port is in the OOS-MA,LPBK & MT service state and remaining client and trunk ports can be in any service state.
3In a trunk-side facility loopback, the trunk port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the remaining client and trunk ports can be in any other service state. In a trunk-side terminal loopback, the trunk port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the client ports are in IS-NR (ANSI)/Unlocked-enabled (ETSI) for complete loopback functionality. This type of loopback affects all client ports because it is performed on the aggregate signal.
Feedback
A change in the administrative state of an entity does not change the service state of supporting or supported entities.
