- About this Guide
- Chapter 1, Install Shelf and Common Control Cards
- Chapter 2, Connect the PC and Log Into the GUI
- Chapter 3, Turn Up a Node
- Chapter 4, Perform Acceptance Tests
- Chapter 5, Turn Up a Network
- Chapter 6, Provision Channels and Circuits
- Chapter 7, Manage Alarms
- Chapter 8, Monitor Performance
- Chapter 9, Manage Node Settings
- Chapter 10, Change Card Settings
- Chapter 11, Maintain the Node
- Chapter 12, Power Down the Node
- Chapter 13, Shelf Hardware Reference
- Chapter 14, Card Reference
- Chapter 15, Node Reference
- Chapter 16, Network Reference
- Chapter 17, CTC Operation Reference
- Chapter 18, Security and Timing Reference
- Chapter 19, Network Connectivity Reference
- Chapter 20, Alarm Management Reference
- Appendix A, CTC Information and Shortcuts
- Appendix B, Shelf Specifications
- Appendix C, DWDM Extended State Model
DWDM Enhanced State Model
This appendix describes the state model 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 4.7 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-2 defines the ANSI and ETSI SSTs supported by the ONS 15454.
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.
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, 32MUX-O, and 32DMX-O cards.
C.3.2 Optical Payload Port Service State Transitions
Table C-5 lists the ANSI and ETSI optical payload port service state transitions.
C.3.3 OSC Port Service State Transitions
Table C-6 lists the ANSI and ETSI OSC port service state transitions.
C.3.4 OCHNC Service State Transitions
Table C-7 lists the ANSI and ETSI OCHNC service state transitions.
C.3.5 Transponder/Muxponder Card Service State Transitions
Table C-4 lists ANSI and ETSI transponder and muxponder card service state transitions.
C.3.6 Transponder/Muxponder Port Service State Transitions
Table C-9 lists the ANSI and ETSI transponder and muxponder port service state transitions.
|
|
|
---|---|---|
IS-NR (ANSI) Unlocked-enabled (ETSI) |
Place the port in the OOS,MT administrative state. |
OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) |
Place the port in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) |
|
Place the port in the IS,AINS administrative state. |
OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) |
|
OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) |
Place the port in the IS administrative state. |
IS-NR1 (ANSI) Unlocked-enabled (ETSI) |
Place the port in the OOS,MT administrative state. |
OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) |
|
Place the port in the OOS,DSBLD. |
OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) |
|
OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) |
Place the port in the IS administrative state. |
IS-NR1 (ANSI) Unlocked-enabled (ETSI) |
Place the port in the IS,AINS administrative state. |
OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) |
|
Place the port in the OOS,MT. |
OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) |
|
OOS-MA,LPBK & MT (ANSI) Locked-enabled,loopback & maintenance (ETSI) |
Release the loopback. |
OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) |
OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) |
Place the port in the IS administrative state. |
IS-NR1 Unlocked-enabled (ETSI) |
Place the port in the IS,AINS administrative state. |
OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) |
|
Place the port in the OOS,DSBLD. |
OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) |
|
Place the port in loopback. |
Locked-enabled,loopback & maintenance (ETSI) |
1 The 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. 2 In 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. 3 In 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. |