- Preface
- Chapter 1, Shelf and Backplane Hardware
- Chapter 2, Common Control Cards
- Chapter 3, Electrical Cards
- Chapter 4, Optical Cards
- Chapter 5, Ethernet Cards
- Chapter 6, Storage Access Networking Cards
- Chapter 7, Card Protection
- Chapter 8, Cisco Transport Controller Operation
- Chapter 9, Security
- Chapter 10, Timing
- Chapter 11, Circuits and Tunnels
- Chapter 12, SONET Topologies and Upgrades
- Chapter 13, Management Network Connectivity
- Chapter 14, Alarm Monitoring and Management
- Chapter 15, Performance Monitoring
- Chapter 16, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
Administrative and Service States
This appendix describes administrative and service states for Cisco ONS 15454 cards, ports, and cross-connects. For circuit state information, refer to Chapter 11 "Circuits and Tunnels." 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.
This appendix contains the following sections:
B.1 Service States
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.
Table B-2 defines the SSTs supported by the ONS 15454.
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. See Table B-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.
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.
Note When an entity is put in the OOS,MT administrative state, the ONS 15454 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.ReportLoopbackConditionsOnOOS-MTPorts to TRUE on the NE Defaults tab.
B.3.1 Card Service State Transitions
Table B-4 lists card service state transitions.
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 OOS-AU,AINS service state cannot transition autonomously into the IS-NR service state until the parent port is in the IS-NR service state.
You cannot transition a port from the IS-NR service state to the OOS-MA,DSBLD service state. You must first put the port in the OOS-MA,MT service state. Once a port is in the OOS-MA,MT state, the NODE.general.ForceToOosDsbldStateChange default setting of TRUE allows you to put a port in OOS-MA,DSBLD 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 bidirectional line switched rings (BLSRs).
•Cross-connects are present on the port.
•Overhead connections or overhead terminations are in use (such as express orderwire, local orderwire, or user data channels [UDCs]).
To change this behavior so that you cannot put a port in OOS-MA,DSBLD if any of these conditions exist, set the NODE.general.ForceToOosDsbldStateChange default setting to FALSE. For the procedure to change node defaults, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 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 IS-NR; OOS-MA,DSBLD; and OOS-MA,MT service states; they do not support the OOS-AU,AINS 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.
Note The DS1 port service state on the DS3XM-12 card is based on the DS3 service state.
|
|
|
---|---|---|
IS-NR |
Put the port or cross-connect in the OOS,MT administrative state. |
OOS-MA,MT |
Put the port or cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS1 |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-MA,MT & OOG |
|
Alarm/condition is raised. |
OOS-AU,FLT OOS-AU,FLT & OOG for a VCAT cross-connect |
|
(Cross-connect only) Put the cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect |
|
OOS-AU,AINS |
Put the port or cross-connect in the IS administrative state. |
IS-NR |
Put the port or cross-connect in the OOS,MT administrative state. |
OOS-MA,MT |
|
Put the port or cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-MA,MT and OOG |
|
Alarm/condition is raised. |
OOS-AU,AINS & FLT OOS-AU,AINS & FLT & OOG for a VCAT cross-connect |
|
OOS-AU,AINS & FLT |
Alarm/condition is cleared. |
OOS-AU,AINS |
Put the port or cross-connect in the IS administrative state. |
OOS-AU,FLT |
|
Put the port or cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD |
|
Put the port or cross-connect in the OOS,MT administrative state. |
OOS-AUMA,FLT & MT |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-AUMA,FLT & MT & OOG |
|
OOS-AU,AINS & FLT & OOG |
Alarm/condition is cleared. |
OOS-AU,AINS or OOS-MA,MT •If an In Group member is IS-NR or OOS-AU,AINS, the member transitions to OOS-AU,AINS •If an In Group member is OOS-MA,MT, the member transitions to OOS-MA,MT |
Put the VCAT cross-connect in the IS administrative state. |
OOS-AU,FLT & OOG |
|
Put the VCAT cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD & OOG |
|
Put the VCAT cross-connect in the OOS,MT administrative state. |
OOS-AUMA,FLT & MT & OOG |
|
OOS-AU,FLT |
Alarm/condition is cleared. |
IS-NR |
Put the port or cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS & FLT |
|
Put the port or cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect |
|
Put the port or cross-connect in the OOS,MT administrative state |
OOS-AUMA,FLT & MT |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-AUMA,FLT & MT & OOG |
|
OOS-AU,FLT & OOG |
Alarm/condition is cleared. |
IS-NR or OOS-MA,MT •If an In Group member is IS-NR or OOS-AU,AINS, the member transitions to IS-NR. •If an In Group member is OOS-MA,MT, the member transitions to OOS-MA,MT |
Put the VCAT cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS & FLT & OOG |
|
Put the VCAT cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD & OOG |
|
Put the VCAT cross-connect in the OOS,MT administrative state. |
OOS-AUMA,FLT & MT & OOG |
|
OOS-AUMA,FLT & LPBK & MT |
Release the loopback. |
OOS-AUMA,FLT & MT |
Alarm/condition is cleared. |
OOS-MA,LPBK & MT |
|
OOS-AUMA,FLT & LPBK & MT & OOG |
Release the loopback. |
OOS-AUMA,FLT & MT & OOG |
Alarm/condition is cleared. |
OOS-MT,MT & OOG |
|
OOS-AUMA,FLT & MT |
Alarm/condition is cleared. |
OOS-MA,MT |
Put the port or cross-connect in the IS administrative state. |
OOS-AU,FLT |
|
Put the port or cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS & FLT |
|
Put the port or cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect |
|
Put the port or cross-connect in a loopback. |
OOS-AUMA,FLT & LPBK & MT |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-AUMA,FLT & MT & OOG |
|
OOS-AUMA,FLT & MT & OOG |
Alarm/condition is cleared. |
OOS-MA,MT & OOG |
Put the VCAT cross-connect in the IS administrative state. Note VCAT In Group members are in the OOS-AU,FLT or IS-NR service state. |
OOS-AU,FLT & OOG |
|
Put the VCAT cross-connect in the IS,AINS administrative state. Note VCAT In Group members are in the OOS-AU,AINS & FLT or IS-NR service state. |
OOS-AU,AINS & FLT & OOG |
|
Put the VCAT cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD & OOG |
|
Put the VCAT cross-connect in the OOS,MT administrative state. Note VCAT In Group members are in the OOS-MA,FLT & MT service state. |
OOS-MA,FLT & MT |
|
Operate a loopback. |
OOS-MA,FLT & LPBK & MT & OOG |
|
OOS-MA,DSBLD |
Put the port or cross-connect in the IS administrative state. |
IS-NR |
Put the port or cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS |
|
Put the port or cross-connect in the OOS,MT administrative state. |
OOS-MA,MT |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-MA,MT & OOG |
|
OOS-MA,LPBK & MT |
Release the loopback. Note While in OOS-MA,LPBK & MT, 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. |
OOS-MA,MT |
Alarm/condition is raised. |
OOS-AUMA,FLT & LPBK & MT OOS-AUMA,FLT & LPBK & MT & OOG for a VCAT cross-connect |
|
OOS-MA,LPBK & MT & OOG |
Alarm/condition is raised. |
OOS-AUMA,FLT & LPBK & MT & OOG |
OOS-MA,MT |
Put the port or cross-connect in the IS administrative state. |
IS-NR |
Put the port or cross-connect in the IS,AINS administrative state. |
OOS-AU,AINS |
|
Put the port or cross-connect in the OOS,DSBLD administrative state. |
OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect |
|
Put the port or cross-connect in a loopback. |
OOS-MA,LPBK & MT |
|
Put the VCAT cross-connect in the OOS,OOG administrative state. |
OOS-MA,MT & OOG |
|
Alarm/condition is raised. |
OOS-AUMA,FLT & MT OOS-AUMA,FLT & MT & OOG for a VCAT cross-connect |
|
OOG-MA,MT & OOG |
Alarm/condition is raised. |
OOS-AUMA,FLT & MT & OOG |
1 For a VCAT cross-connect, an IS-NR to OOS-AU,AINS 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.