Cisco ONS 15600 SDH Troubleshooting Guide, Release 1.4
Chapter 2, Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

Alarm Index

Alarm Index by Alarm Type

Alarm Type/Object Definition

Trouble Notifications

Conditions

Severities

Safety Summary

Alarm Procedures

AIR-FLOW

AIS (BITS)

APSB

APSCDFLTK

APSC-IMP

APSCINCON

APSCM

APSCNMIS

AU-AIS

AU-LOP

AUD-LOG-LOSS

AUD-LOG-LOW

AUTORESET

AUTOSW-AIS-SNCP

AUTOSW-LOP-SNCP

AUTOSW-PDI-SNCP

.AUTOSW-SDBER-SNCP

AUTOSW-SFBER-SNCP

AUTOSW-UNEQ-SNCP

BKUPMEMP

BPV

CHANLOSS

CIDMISMATCH-0

CIDMISMATCH-1

CLKFAIL

CONTBUS-0

CONTBUS-1

CONTBUS-CLK-0

CONTBUS-CLK-1

CONTCOM

CTNEQPT-PB-0

CTNEQPT-PB-1

CXCHALT

DATAFLT

EOC

EQPT (CAP)

EQPT (CXC, Traffic Card, TSC)

EQPT-BOOT

EQPT-HITEMP

E-W-MISMATCH

EXERCISE-RING-FAIL

EXT

FAILTOSW

FAILTOSWR

FAN-DEGRADE

FAN-FAIL

FAN-FAIL-PARTIAL

FAN-PWR

FE-FRCDWKSWPR-SPAN

FEPRLF

FE-LOCKOUTOFPR-SPAN

FE-MANWKSWPR-RING

FORCED-REQ

FORCED-REQ-RING

FREQ-MISMATCH

FRNGSYNC

FSTSYNC

FULLPASSTHR-BI

HELLO

HLDOVRSYNC

HP--DEG

HP-EXC

HP-RDI

HP-TIM

HP-UNEQ

IMPROPRMVL (CAP)

IMPROPRMVL (CXC, Traffic Card, TSC)

IMPROPRMVL (FAN)

INTRUSION

INVMACADR

KB-PASSTHR

LASER-BIAS (STM-64)

LASER-OVER-TEMP (STM-64)

LKOUTPR-S

LOCKOUT-REQ

LOF (BITS)

LOF

LOS (BITS)

LOS

LPBKCRS

LPBKFACILITY (STM-16)

LPBKPAYLOAD (STM-64)

MANSWTOINT

MAN-REQ

MANUAL-REQ-RING

MANUAL-REQ-SPAN

MANRESET

MANSWTOPRI

MANSWTOSEC

MATECLK

MEA

MFGMEM (CAP)

MFGMEM (CXC, Traffic Card, TSC)

MFGMEM (FAN)

MS-AIS

MS-DEG

MS-EXC

MS-RDI

MSSP-OOSYNC

OPEN-SLOT

PDI-P

PRC-DUPID

PWR-A

PWR-B

PWR-FA

PWR-FAIL-A

PWR-FAIL-B

PWR-FAIL-RET-A

PWR-FAIL-RET-B

PWRRESTART

RING-MISMATCH

RING-SW-EAST

RING-SW-WEST

ROLL

ROLL-PEND

RS-TIM

SECUR-THRESHOLD

SFTWDOWN

SNTP-HOST

SQUELCH

SSM-DUS

SSM-FAIL

SSM-OFF

SSM-PRC

SSM-RES

SSM-SEC

SSM-SMC

SSM-SSUA

SSM-SSUB

SSM-STU

SSM-TNC

SWTOPRI

SWTOSEC

SWTOTHIRD

SWVER

SYNCCLK

SYNC-FREQ

SYNCPRI

SYNCSEC

SYSBOOT

T-OPR-High/Low

UNEQ-P

UNPROT-SYNCCLK

UNPROT-XCMTX

UPGRADE

WTR

XCMTX

Common Troubleshooting Procedures

Identify a Ring ID or Node ID Number

Change a Ring ID Number

Clear a Loopback

Change a Node ID Number

Delete a Circuit

Request a Cross-Connect Card Preferred Copy Switch

Soft-Reset the TSC Card Using CTC

Hard-Reset the TSC Using CTC

Physically Replace a Card

Reset the TSC Card with a Card Pull

Verify Node Visibility for Other Nodes

Verify or Create Node DCC Terminations

Lock Out an MS-SPRing Span

Clear an MS-SPRing Span Lockout

Remove and Replace a Card

Set the Optical Power Received Nominal Value

Alarm Troubleshooting


This chapter gives CiscoONS15600SDH alarm and condition default severities, descriptions, and when necessary, troubleshooting procedures. Table2-1 gives an alphabetical list of alarms and conditions that appear on the ONS15600SDH. Table2-2 gives a list of alarms and conditions organized by type. Both lists cross-reference the alarm and condition entries. The entries contain more detailed descriptions and troubleshooting information.

Alarm troubleshooting procedures apply to the Cisco Transport Controller (CTC) version of the alarm. If a troubleshooting procedure does not clear the alarm, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.

Active card alarms have these default severities as defined in ITU-T G.783:

Critical (CR)

Major (MJ)

Minor (MN)

Standby card alarms have a default severity of minor, Non-Service Affecting (MN, NSA) as defined in ITU-T G.783.

Conditions are commonly encountered while troubleshooting alarms. In this chapter, they have these default severity ratings:

Not alarmed, Non-Service Affecting (NA, NSA)

Not reported, Non-Service Affecting (NR, NSA)


Note For a comprehensive list of all conditions, refer to the CiscoONS15600SDHTL1Test Access .


2.1  Alarm Index

This table lists alarms by the name displayed in the CTC Alarms window Conditions column.

Table 2-1 Alarm Index  

AIR-FLOW

FEPRLF

PDI-P

AIS (BITS)

FORCED-REQ-RING

PRC-DUPID

APSB

FORCED-REQ

PWR-A

APSCDFLTK

FREQ-MISMATCH

PWR-B

APSC-IMP

FRNGSYNC

PWR-FA

APSCINCON

FSTSYNC

PWR-FAIL-A

APSCNMIS

FULLPASSTHR-BI

PWR-FAIL-B

AU-AIS

HELLO

PWR-FAIL-RET-A

AU-LOP

HLDOVRSYNC

PWR-FAIL-RET-B

AUD-LOG-LOSS

HP--DEG

PWRRESTART

AUD-LOG-LOW

HP-EXC

RING-MISMATCH

AUTORESET

HP-RDI

RING-SW-EAST

AUTOSW-AIS-SNCP

HP-TIM

RING-SW-WEST

AUTOSW-LOP-SNCP

HP-UNEQ

ROLL

AUTOSW-PDI-SNCP

IMPROPRMVL (CAP)

ROLL-PEND

.AUTOSW-SDBER-SNCP

IMPROPRMVL (CXC, Traffic Card, TSC)

RS-TIM

AUTOSW-SFBER-SNCP

IMPROPRMVL (FAN)

SECUR-THRESHOLD

AUTOSW-UNEQ-SNCP

INTRUSION

SFTWDOWN

BKUPMEMP

INVMACADR

SNTP-HOST

BPV

KB-PASSTHR

SQUELCH

CHANLOSS

LASER-BIAS (STM-64)

SSM-DUS

CIDMISMATCH-0

LASER-OVER-TEMP (STM-64)

SSM-FAIL

CIDMISMATCH-1

LKOUTPR-S

SSM-OFF

CLKFAIL

LOCKOUT-REQ

SSM-PRC

CONTBUS-0

LOF (BITS)

SSM-RES

CONTBUS-1

LOF

SSM-SEC

CONTBUS-CLK-0

AU-LOP

SSM-SMC

CONTBUS-CLK-1

LOS (BITS)

SSM-SSUA

CONTCOM

LOS

SSM-SSUB

CTNEQPT-PB-0

LPBKCRS

SSM-STU

CTNEQPT-PB-1

LPBKFACILITY (STM-16)

SSM-TNC

CXCHALT

LPBKPAYLOAD (STM-64)

SWTOPRI

DATAFLT

MANSWTOINT

SWTOSEC

EOC

MAN-REQ

SWTOTHIRD

EQPT (CAP)

MANUAL-REQ-RING

SWVER

EQPT (CXC, Traffic Card, TSC)

MANUAL-REQ-SPAN

SYNCCLK

EQPT-BOOT

MANRESET

SYNC-FREQ

EQPT-HITEMP

MANSWTOPRI

SYNCPRI

E-W-MISMATCH

MANSWTOSEC

SYNCSEC

EXERCISE-RING-FAIL

MATECLK

SYSBOOT

EXT

MEA

UNPROT-XCMTX

FAILTOSW

MFGMEM (CAP)

UPGRADE

FAILTOSWR

MFGMEM (CXC, Traffic Card, TSC)

WTR

FAN-DEGRADE

MFGMEM (FAN)

XCMTX

FAN-FAIL

MS-AIS

 

FAN-FAIL-PARTIAL

MS-DEG

 

FAN-PWR

MS-EXC

 

FE-FRCDWKSWPR-SPAN

MS-RDI

 

FE-LOCKOUTOFPR-SPAN

MSSP-OOSYNC

 

FE-MANWKSWPR-RING

OPEN-SLOT

 

2.2  Alarm Index by Alarm Type

This list of alarm types gives the name and page number of every alarm in the chapter and is organized by alarm type.

Table 2-2 Alarm Index by Alarm Type 

BITS:: AIS (BITS)

BITS:: FRNGSYNC

BITS:: HLDOVRSYNC

BITS:: LOF (BITS)

BITS:: LOS (BITS)

BITS:: MANSWTOINT

BITS:: MANSWTOPRI

BITS:: MANSWTOSEC

BITS:: SWTOPRI

BITS:: SWTOSEC

BITS:: SWTOTHIRD

BITS:: SYNC-FREQ

BITS:: SYNCPRI

BITS:: SYNCSEC

BP:: PWR-FA

EQPT:: AUTORESET

EQPT:: BKUPMEMP

EQPT:: CIDMISMATCH-0

EQPT:: CIDMISMATCH-1

EQPT:: CLKFAIL

EQPT:: CXCHALT

EQPT:: CONTBUS-0

EQPT:: CONTBUS-1

EQPT:: CONTBUS-CLK-0

EQPT:: CONTBUS-CLK-1

EQPT:: CONTCOM

EQPT:: CTNEQPT-PB-0

EQPT:: CTNEQPT-PB-1

EQPT:: EQPT (CAP)

EQPT:: EQPT (CXC, Traffic Card, TSC)

EQPT:: EQPT-BOOT

EQPT:: EQPT-HITEMP

EQPT:: FAN-DEGRADE

EQPT:: FAN-FAIL

EQPT:: FAN-FAIL-PARTIAL

EQPT:: FAN-PWR

EQPT:: FSTSYNC

EQPT:: IMPROPRMVL (CAP)

EQPT:: IMPROPRMVL (CXC, Traffic Card, TSC)

EQPT:: IMPROPRMVL (FAN)

EQPT:: LASER-BIAS (STM-64)

EQPT:: LASER-OVER-TEMP (STM-64)

EQPT:: MANRESET

EQPT:: MEA

EQPT:: MFGMEM (CAP)

EQPT:: MFGMEM (CXC, Traffic Card, TSC)

EQPT:: MFGMEM (FAN)

EQPT:: OPEN-SLOT

EQPT:: PWR-FAIL-A

EQPT:: PWR-FAIL-B

EQPT:: PWR-FAIL-RET-A

EQPT:: PWR-FAIL-RET-B

EQPT:: PWRRESTART

EQPT:: SFTWDOWN

EXT:: EXT

NE:: AIR-FLOW

NE:: AUD-LOG-LOSS

NE:: AUD-LOG-LOW

NE:: DATAFLT

NE:: INTRUSION

NE:: INVMACADR

NE:: PWR-A

NE:: PWR-B

NE:: SECUR-THRESHOLD

NE:: SYNCCLK

NE:: SYSBOOT

NE:: UNPROT-SYNCCLK

NE:: UNPROT-XCMTX

NE:: UPGRADE

NE:: XCMTX

STM-N:: MS-AIS

STM-N:: APSB

STM-N:: APSCDFLTK

STM-N:: APSC-IMP

STM-N:: APSCINCON

STM-N:: APSCM

STM-N:: APSCNMIS

STM-N:: MSSP-OOSYNC

STM-N:: CHANLOSS

STM-N:: EOC

STM-N:: E-W-MISMATCH

STM-N:: EXERCISE-RING-FAIL

STM-N:: FAILTOSWR

STM-N:: FE-LOCKOUTOFPR-SPAN

STM-N:: FE-MANWKSWPR-RING

STM-N:: FAILTOSWR

STM-N:: FEPRLF

STM-N:: FORCED-REQ-RING

STM-N:: LKOUTPR-S

STM-N:: LOCKOUT-REQ

STM-N:: LOF

STM-N:: LOS

STM-N:: LPBKFACILITY (STM-16)

STM-N:: LPBKPAYLOAD (STM-64)

STM-N:: MANUAL-REQ-RING

STM-N:: MANUAL-REQ-SPAN

STM-N:: PRC-DUPID

STM-N:: MS-RDI

STM-N:: RING-MISMATCH

STM-N:: RING-SW-EAST

STM-N:: RING-SW-WEST

STM-N:: MS-DEG

STM-N:: MS-EXC

STM-N:: SQUELCH

STM-N:: SSM-DUS

STM-N:: SSM-OFF

STM-N:: SSM-PRC

STM-N:: SSM-RES

STM-N:: SSM-SEC

STM-N:: SSM-SMC

STM-N:: SSM-SSUA

STM-N:: SSM-SSUB

STM-N:: SSM-STU

STM-N:: SSM-TNC

STM-N:: WTR

SHELF:: AIR-FLOW

SHELF:: XCMTX

VCMONHP:: AU-AIS

VCMONHP:: AUTOSW-AIS-SNCP

VCMONHP:: AUTOSW-LOP-SNCP

VCMONHP:: AUTOSW-PDI-SNCP

VCMONHP:: .AUTOSW-SDBER-SNCP

VCMONHP:: AUTOSW-SFBER-SNCP

VCMONHP:: AUTOSW-UNEQ-SNCP

VCMONHP:: FAILTOSW

VCMONHP:: FORCED-REQ

VCMONHP:: LOCKOUT-REQ

VCMONHP:: LPBKCRS

VCMONHP:: FORCED-REQ

VCMONHP:: MAN-REQ

VCMONHP:: PDI-P

VCMONHP:: HP-RDI

VCMONHP:: ROLL

VCMONHP:: ROLL-PEND

VCMONHP:: HP--DEG

VCMONHP:: HP-EXC

VCMONHP:: HP-TIM

VCMONHP:: UNEQ-P

VCRNGHP:: FULLPASSTHR-BI

VCRNGHP:: KB-PASSTHR


2.2.1  Alarm Type/Object Definition

This table lists the alarm types and their definitions. The CTC Alarms window lists an alarm type in the Object column for each alarm.

Table 2-3 Alarm Type/Object Definition

Alarm Type
Definitions
BITSEOC

Alarms for timing reference.

BP

Backplane alarm.

EXT

External alarm.

EQPT

A card in any of the 14 card slots. This object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, and Virtual Container (VC).

NE

The entire network element (SYSTEM).

STM-N

Alarm for an STM-N line on an STM-N card.

SHELF

Shelf alarm.

VC

Alarm for a VC.


2.3  Trouble Notifications

The ONS15600SDH uses standard ITU categories to characterize levels of trouble. The ONS15600SDH reports alarmed trouble notifications in the Alarms window and not alarmed (NA) trouble notifications in the Conditions window in CTC. Alarms signify a problem that the user needs to fix, such as a Loss of Signal ( LOS). Conditions notify the user of an event that does not require action, such as a Switch to a Secondary Timing Reference ( SWTOSEC) or a user-initiated Manual Reset ( MANRESET).

The ITU further divides alarms into Service Affecting (SA) and NSA status. An SA failure affects a provided service or the network's ability to provide service. For example, an LOS is characterized as an SA failure. LOS occurs when the incoming signal or outgoing signal ceases to be detected because of equipment failure or configuration problems. This affects a provided service, because traffic switches to the protect card. The Equipment High Temperature ( EQPT-HITEMP) alarm, which means the ONS15600SDH is hotter than 122 degrees Fahrenheit (50 degrees Celsius), is also an SA failure. Even if a particular port on the card might not be affected, the high temperature affects the network service.

2.3.1  Conditions

When an SA failure is detected, the ONS15600SDH also sends an Alarm Indication Signal (AIS) downstream. When it receives the AIS, the receiving node sends a Remote Defect Indication (RDI) upstream. AIS and RDI belong in the conditions category and show up in the Conditions window of the ONS15600SDH. However, unlike most conditions which are not alarmed, Telcordia classifies these conditions as not reported (NR).

Both CTC and TL1 report NR and NA events as conditions. NA events are also reported as autonomous events under TL1 and in the History window of CTC. For a comprehensive list of conditions, refer to the CiscoONS15600SDH TL1 Command Guide.

2.3.2  Severities

The ONS15600SDH uses ITU-standard severities:

Critical indicates a severe, service-affecting alarm that needs immediate correction. An example of a critical alarm is BKUPMEMP. This alarm must be resolved immediately to reinstate traffic.

Major is a serious alarm, but the failure has less of an impact on the network. An example of a major alarm is APSCM. This alarm affects traffic but does not completely shut it down. It has to be resolved quickly.

Minor alarms do not seriously affect service. An example of a minor alarm is Fast-Start Synchronization ( FSTSYNC). FSTSYNC lets you know that the ONS15600SDH is choosing a new timing reference because the old reference failed. The loss of the prior timing source is something a user needs to check, but it should not immediately disrupt service.

A user can customize ONS15600SDH alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the CiscoONS15600SDH Procedure Guide. This chapter lists the default alarm severity for the active reporting card or port, if applicable.

2.4  Safety Summary

This section covers safety considerations to ensure safe operation of the ONS15600SDH system. Personnel should not perform any procedures in this manual unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards. In these instances, users should pay close attention to the following caution:


Caution Hazardous voltage or energy might be present on the backplane when the system is operating. Use caution when removing or installing cards.


Some troubleshooting procedures require installation or removal of optical cards. In these instances, users should pay close attention to the following warnings:


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Warning Class 1 laser product.


2.5  Alarm Procedures

This section lists alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severities, descriptions, and troubleshooting procedures accompany the alarms and conditions.

2.5.1  AIR-FLOW

Minor (MN), Non-Service Affecting (NSA)

The shelf Air Flow Degrade alarm accompanies a degradation in air flow to a Core Cross Connect (CXC) card, Timing and Shelf Controller (TSC) card, or an optical (STM-N) card.

Clear the AIR-FLOW Condition


Step 1 Ensure that filler modules are installed in the ONS15600SDH empty slots. Filler modules help airflow.

Step 2 If the alarm does not clear, check the condition of the air filter to determine whether it needs replacement. Complete the "Replace the Air Filter" procedure on page3-10 as necessary.

Step 3 If the alarm does not clear and the filter is clean, remove and reinsert each fan tray (one at a time).

When you reinsert the fan trays, making sure the plugs connect to the backplane receptacles of the ONS 15600 SDH.


Note Fans should run immediately when correctly inserted.


Step 4 If a fan does not run or the alarm persists, complete the "Replace a Fan Tray" procedure on page3-11.

Step 5 If a replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service-affecting problem.


2.5.2  AIS (BITS)

Not Alarmed (NA), Non-Service Affecting (NSA)

The Alarm Indication Signal (AIS) BITS condition indicates a problem in the building integrated timing supply (BITS) electrical signal.

Clear the AIS Condition


Step 1 Check upstream BITS equipment for alarms, especially antenna outage, and clear those alarms.

Step 2 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.3  APSB

Minor (MN), Non-Service Affecting (NSA)

The Automatic Protection Switching (APS) Byte Failure alarm occurs for traffic (STM-N) cards when line-terminating equipment detects protection-switching byte failure in the incoming automatic protection switching signal. A failure occurs when an inconsistent APS byte or invalid code is detected. Some older non-Cisco SDH nodes send invalid APS codes when they are configured in a 1+1 group with newer SDH nodes such as the ONS15600SDH. These invalid codes raise an APSB on an ONS node. The alarm applies to 1+1 protection groups.


Note APS switches are hitless in the ONS15600SDH.


Clear the APSB Alarm


Step 1 Examine the incoming SDH overhead with an optical test to confirm inconsistent or invalid K bytes. Refer to the CiscoONS15600SDH Procedure Guide for instructions.

Step 2 If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS15600SDH. For ONS15600SDH protection switching to operate properly, the upstream equipment might need to be replaced.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.4  APSCDFLTK

Minor (MN), Non-Service Affecting (NSA)

The APS Default K Byte Received alarm occurs when a multiplex section-shared protection ring (MS-SPRing) is not properly configured, for example, when a four-node MS-SPRing has one node configured as a subnetwork connection protection (SNCP) ring. A node in an SNCP or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a node configured for MS-SPRing. One of the bytes sent is considered invalid by the MS-SPRing configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.

Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "MSSP-OOSYNC" alarm on page2-64.

Clear the APSCDFLTK Alarm


Step 1 Complete the "2.6.1Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.

Step2 Repeat Step 1 for all nodes in the ring.

Step 3 If two nodes have the same node ID number, complete the "2.6.4Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.

Step 4 If the alarm does not clear, verify that the east port and west port optical fibers are configured correctly. (See the "E-W-MISMATCH" alarm on page2-31.) West port fibers must connect to east port fibers, and vice versa. The CiscoONS15600SDH Procedure Guide provides a procedure for fibering MS-SPRings.

Step 5 If the alarm does not clear, complete the "2.6.11Verify Node Visibility for Other Nodes" procedure.

Step 6 If nodes are not visible, complete the "2.6.12Verify or Create Node DCC Terminations" procedure to ensure that SDH DCC terminations exist on each node.

Step 7 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.5  APSC-IMP

Minor (MN), Non-Service Affecting (NSA)

An Improper APS Code alarm indicates invalid K bytes. The APSC-IMP alarm occurs on STM-N cards in an MS-SPRing configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. APSCIMP occurs when these bits indicate a bad or invalid K byte. The alarm clears when the node receives valid K bytes.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into an ESD jack.


Clear the APSC-IMP Alarm


Step1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.

For specific procedures to use the test set equipment, consult the manufacturer.

If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15600 SDH. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15600 SDHs, consult the appropriate user documentation.

Step 2 If the K byte is valid, verify that each node has a ring ID that matches the other node ring IDs. Complete the "2.6.1Identify a Ring ID or Node ID Number" procedure.

Step 3 Repeat Step 2 for all nodes in the ring.

Step 4 If a node has a ring ID number that does not match the other nodes, make the ring ID number of that node identical to the other nodes using the "2.6.2Change a Ring ID Number" procedure.

Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.6  APSCINCON

Minor (MN), Non-Service Affecting (NSA)

An APS Inconsistent alarm accompanies an inconsistent APS byte. The SDH overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS15600SDH, to switch the SDH signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.

Clear the APSCINCON Alarm


Step1 Look for other alarms, especially the "LOS" alarm on page2-54, the "LOF" alarm on page2-52, or the "MS-AIS" condition on page2-62. Clearing these alarms clears the APSCINCON alarm.

Step 2 If an APSINCON alarm occurs without other alarms, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.7  APSCM

Major (MJ), Service Affecting (SA)

The APS-Channel Mismatch Failure alarm occurs on traffic (STM-N) cards when the received K2 channel ID does not match the transmitted K1 channel ID. In many cases, the working and protection channels are crossed, and the protect channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. The APSCM alarm only occurs on 1+1 protection groups.


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left side of the shelf assembly.



Note APS switches are hitless in the ONS15600SDH.


Clear the APSCM Alarm


Step 1 Verify that the working port fibers connect directly to the adjoining node's working port fibers.

Step 2 If the alarm does not clear, verify that the protection port fibers connect directly to the adjoining node's protection port fibers.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.8  APSCNMIS

Major (MJ), Service Affecting (SA)

The APS Node ID Mismatch alarm occurs when the source node ID contained in the K2 byte of the incoming APS channel is not present in the ring map. The APSCNMIS alarm can occur and clear when an MS-SPRing is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains, the alarm clears when a K byte with a valid source node ID is received.

Clear the APSCNMIS Alarm


Step 1 Complete the "2.6.1Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.

Step 2 If the Node ID column contains any two nodes with the same node ID:

a. Record the repeated node ID.

b. Click Close in the Ring Map dialog box.

c. Complete the "2.6.4  Change a Node ID Number" procedure  to change one node's ID number so that each node ID is unique.


Note If the node names shown in the network view do not correlate with the node IDs, log into each node and click the Provisioning > MS-SPRing tabs. The MS-SPRing window shows the node ID of the login node.


Step 3 If the alarm does not clear, use the "2.6.13Lock Out an MS-SPRing Span" procedure, then complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure to clear the lockout. Applying and removing a lockout on a span causes the ONS15600SDH to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.

Step 4 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.9  AU-AIS

Not Reported (NR), Non-Service Affecting (NSA)

An Administration Unit (AU) AIS condition applies to the administration unit, which consists of the VC capacity and pointer bytes (H1, H2, and H3) in the SDH frame.

Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

Clear the AU-AIS Condition


Step 1 Complete the "Clear the AIS Condition" procedure.

Step 2 If the condition does not clear, complete the "Clear the APSB Alarm" procedure.

Step 3 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.10  AU-LOP

Critical (CR), Service Affecting (SA)

An Administration Unit Loss of Pointer Path alarm indicates that the transmitted optical circuit size is different from the provisioned optical circuit size. AU-LOP occurs when valid H1/H2 pointer bytes are missing from the SDH overhead. Receiving equipment monitors the H1/H2 pointer bytes to locate the SDH payload. An AU-LOP alarm means that eight, nine, or ten consecutive frames do not have valid pointer values. The alarm clears when three consecutive valid pointers are received.

One of the conditions that can cause this alarm is a transmitted VC4-Nc circuit that is different from the provisioned VC4-Nc. This condition causes a mismatch of the path type on the concatenation facility. It occurs when there are eight to ten new data flags received, or eight to ten invalid pointers. For example, if a VC4-4c or VC4 is sent across a path provisioned for VC4-16c, a LOP alarm occurs.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the AU-LOP Alarm


Step 1 Complete the "Switch all SNCP Circuits on a Span" procedure on page3-4 or the "Initiate a Force Switch on a 1+1 Port" procedure on page3-4 as appropriate.

Step 2 Use a test set to verify that the incoming signal is valid; refer to the CiscoONS15600SDH Procedure Guide for instructions on testing optical circuits. If the upstream signal is not valid, troubleshoot upstream.

Step 3 If the incoming signal is valid, complete the "2.6.15Remove and Replace a Card" procedure for the reporting card.


Note If the traffic (STM-N) card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH Procedure Guide. Label the bad port, and place it out of service until the card can be replaced.


Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more informationor log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service affecting problem.


2.5.11  AUD-LOG-LOSS

Not Alarmed (NA), Non-Service Affecting (NSA)

The Audit Trail Log Loss condition occurs when the log is 100 percent full and the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries.

Clear the AUD-LOG-LOSS Condition


Step 1 In node view, click the Maintenance > Audit tabs.

Step 2 Click Retrieve and click Archive .

Step 3 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.

Step4 Enter a name in the File Name field.

You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.

Step 5 Click Save .

The 640 entries will be saved in this file. New entries will continue with the next number in the sequence, rather than starting over.


Note When you have archived a group of audit trail entries, they are no longer visible in CTC. The entries cannot be imported into CTC.


Step 6 If the alarm does not clear, log onto http://www.cisco.com/tac for more information log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.12  AUD-LOG-LOW

Not Reported (NR), Non-Service Affecting (NSA)

The Audit Trail Log Loss condition occurs when the audit trail log is 80 percent full. The log capacity is 640 entries.


Note AUD-LOG-LOW is an informational condition. It does not require troubleshooting.


2.5.13  AUTORESET

Minor (MN), Non-Service Affecting (NSA)

The Automatic System Reset alarm occurs when a TSC card, CXC card, or traffic (STM-N) card automatically reboots. The reboot is caused by changing an IP address or performing any other operation that causes the active TSC card to lose communication with the card (a "heartbeat" failure). The TSC card automatically resets the card it loses communication with. If communication is not reestablished, the card resets again.


Note If an optical card associated with an active port in a 1+1 protection group resets, all DCC traffic terminated or tunneled on the active port is lost while the card resets. No DCC traffic is lost during a reset of an optical card associated with a standby port.


If the lack of communication continues, the AUTORESET alarm is cleared and the EQPTBOOT alarm occurs. Consequently, AUTORESET does not need troubleshooting.

2.5.14  AUTOSW-AIS-SNCP

Not Reported (NR), Non-Service Affecting (NSA)

The Automatic Protection Switch AIS condition indicates that automatic SNCP path protection switching occurred because of the "AU-AIS" condition on page2-14 on the circuit path.

Troubleshoot with the "Clear the AU-AIS Condition" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.15  AUTOSW-LOP-SNCP

Not Alarmed (NA), Non-Service Affecting (NSA)

The Automatic Protection Switch Loss of Path (LOP) condition indicates that automatic SNCP path protection switching occurred because of the "AU-LOP" condition on page2-14 on the VC4 signal.

Troubleshooting using the "Clear the AU-LOP Alarm" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.16  AUTOSW-PDI-SNCP

Not Alarmed (NA), Non-Service Affecting (NSA)

The Automatic Protection Switch Path Defect Indication (PDI) condition indicates that automatic SNCP path protection switching occurred for the VC4 signal because of a "PDI-P" condition on page2-65.

Troubleshoot with the "Clear the PDI-P Condition" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.17  .AUTOSW-SDBER-SNCP

Not Alarmed (NA), Non-Service Affecting (NSA)

The Automatic Protection Switch Signal Degrade (SD) Bit Error Rate (BER) condition indicates that a VC4 signal degrade condition caused automatic SNCP path protection switching.

Troubleshoot with the "Clear the MS-DEG Condition" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.18  AUTOSW-SFBER-SNCP

Not Alarmed (NA), Non-Service Affecting (NSA)

The Automatic Protection Switch Signal Fail (SF) BER condition indicates that a signal fail condition caused automatic SNCP path protection switching on a VC4 signal.

Troubleshoot with the "Clear the MS-DEG Condition" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.19  AUTOSW-UNEQ-SNCP

Not Alarmed (NA), Non-Service Affecting (NSA)

The Automatic Protection Switch Unequipped Path condition indicates that the "UNEQ-P" alarm on page2-82 caused automatic SNCP path protection switching to occur on the VC4 signal.

Troubleshoot with the "Clear the UNEQ-P Alarm" procedure . If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.20  BKUPMEMP

Critical (CR), Non-Service Affecting (NSA)

The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TSC card flash memory. The alarm occurs when the TSC card is in use and has one of four problems: The flash manager does not format a flash partition, the flash manager does not write a file to a flash partition, there is a problem at the driver level, or the code volume fails cyclic redundancy checking (CRC). CRC is a method to check for errors in data transmitted to the TSC card.

Clear the BKUPMEMP Alarm


Step 1 Verify that both TSC cards are powered and enabled. Confirm that the green SRV LEDs are turned on and that the ACTSTBY LED is turned on the active TSC card.

Step 2 If the alarm does not clear, complete the "2.6.8Hard-Reset the TSC Using CTC" procedure.

Step 3 If the alarm does not clear, remove and reinsert (reseat) the reporting card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 4 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure.


Note When different versions of software are on the two TSC cards, it takes approximately 20 minutes for the active TSC card to transfer the software to the newly installed standby TSC card. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.



Note If the active and standby TSC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby TSC card.


Step 5 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

Step 6 If you want to make the reporting card the active card again, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.


2.5.21  BPV

The Bipolar Violation alarm is generated when bipolar violation does not satisfy the requirements described in ITU-T recommendations.

Clear the BPV alarm


Step 1 Check if the input signal is correct and that the externally synchronized node is correctly provisioned with the 64KHz signal

Step 2 If the type of signal is correct then check if all two wires are firmly connected to the BITS-IN pins.

Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.22  CHANLOSS

Not Alarmed (NA), Non-Service Affecting (NSA)

The SDH Regenerator Section Layer DCC Termination Failure condition occurs when the ONS15600SDH receives unrecognized data in the Regenerator section layer DCC bytes.


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the CHANLOSS Condition


Step 1 In the absence of other alarms, determine whether the alarmed port is connected to another vendor's equipment. If so, you can mask the alarm on this path using a custom alarm profile. For more information about custom profiles, see the CiscoONS15600SDH Procedure Guide.

Step 2 If alternate vendor equipment is not the cause of the alarm, complete the "2.6.15Remove and Replace a Card" procedure.

Step 3 If the alarm does not clear, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.

Step 4 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.23  CIDMISMATCH-0

Minor (MN), Non-Service Affecting (NSA)

A Connection ID Mismatch on CXC-0 (in Slot 6) alarm occurs when at least one internal connection ID mismatch is present at the VC4 level on the traffic (STM-N) card outbound data path. The alarm occurs when the head end of the connection between traffic cards is removed.


Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.


Clear the CIDMISMATCH-O Alarm


Step 1 Depending on how many CIDMISMATCH alarms are raised, take the following actions:

If two CIDMISMATCH alarms (CIDMISMATCH-0 and CIDMISMATCH-1) are present, continue with Step 6 .

One CIDMISMATCH-x alarm indicates trouble related to one CXC card. If an automatic switch to the alternate copy CXC card occurred, the alarmed CXC card can be serviced. If traffic has not switched, complete the "2.6.6  Request a Cross-Connect Card Preferred Copy Switch" procedure .

To determine which CXC card is the preferred copy and if it is currently being used, in node view open the Maintenance > Preferred Copy tabs. The Data Copy area Preferred field shows Copy A or Copy B. The Currently Used field shows the copy being used.


Note In CTC, CopyA refers to the CXC card in Slot 6. CopyB refers to the CXC card in Slot 8. Either copy can be chosen as the preferred copy CXC card. The other CXC card is called the alternate CXC card in this chapter.


Step 2 Perform a CTC soft reset on the alarmed CXC card:

a. In node view, position the cursor over the card.

b. Right-click and choose Soft-reset Card from the shortcut menu .

c. Click Yes in the Soft-reset Card dialog box.

Step 3 If the alarm does not clear, and if the port is part of a 1+1 protection group or part of an SNCP, ensure that an automatic protection switch has moved traffic to the protect port. If an APS switch occurred, continue with Step 4.

An SNCP APS is identified by an AUTOSW-type alarm or condition (such as AUTOSW-AIS, AUTOSW-LOP-SNCP, AUTOSW-PDI-SNCP, AUTOSW-SDBER-SNCP, AUTOSW-SFBER-SNCP, or AUTOSW-UNEQ-SNCP).

A 1+1 APS is identified on the node view Maintenance > Protection window. If you click the protection group, in the Selected Group list, the ports are designated as Working/Standby and Protect/Active.

If the reporting traffic card has 1+1 active ports and traffic has not switched to the protect ports, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page 3-4 . If the ports are part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page 3-4 .

Step 4 Remove and reinsert (reseat) the reporting traffic card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 5 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure for the traffic card.

Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.

Step 7 When the alarm clears, if an automatic switch to the alternate copy CXC card occurred, traffic is restored to the preferred copy.

If the reporting card is a traffic card, traffic reverts to the working port if an automatic switch occurred. If traffic was manually switched in a 1+1 protection group, revert traffic to the original port by completing the "Clear a Force Switch on a 1+1 Port" procedure on page 3-7 . If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page 3-7 .


2.5.24  CIDMISMATCH-1

Minor (MN), Non-Service Affecting (NSA)

A Connection ID Mismatch on CXC-1 (Slot 8) alarm occurs when at least one internal connection ID mismatch is present at the VC4 level on the STM-16 or STM-64 card outbound data path. The alarm occurs when the head end of the connection between traffic (STM-N) cards is removed. Troubleshoot with the "Clear the CIDMISMATCH-O Alarm" procedure.


Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.


2.5.25  CLKFAIL

Major (MJ), Non-Service Affecting (NSA)

The Clock Fail alarm occurs when an internal clock module fails. If this alarm occurs against the standby TSC card, the card must be replaced. If the alarm occurs against the active TSC card, the card automatically becomes standby because the traffic and CXC cards can only take timing from the active TSC card.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the CLKFAIL Alarm


Step 1 Complete the "2.6.15Remove and Replace a Card" procedure for the reporting TSC card.


Note When there are different versions of system software on the two TSC cards, it takes approximately 20 minutes for the active TSC card to transfer the system software to the newly installed standby TSC card. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.



Note If the active and standby TSC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby TSC card.


Step 2 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.26  CONTBUS-0

Major (MJ), Non-Service Affecting (NSA)

An Inbound Interconnection Control Bus 0 Failure alarm on the TSC card, CXC card, or traffic (STM-N) cards occurs when one or more cards experience a control bus communication problem with the TSC card in Slot 5.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.



Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.


Clear the CONTBUS-0 Alarm


Step 1 If a single traffic (STM-N) card is reporting the alarm and it is part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page3-4. If the traffic card is part of a 1+1 protection group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page3-4.

If the reporting card is a CXC card, traffic should have already switched from the errored copy of the card.

If the active TSC card is reporting the alarm, shelf control should already have switched off the card.

Step 2 Complete the "2.6.15Remove and Replace a Card" procedure for the reporting card.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.

Step 4 When the alarm clears, if an automatic switch to the alternate copy CXC card occurred, traffic is automatically restored to the preferred copy.

If a Force switch was applied in a 1+1 protection group, revert traffic to the original port by completing the "Clear a Force Switch on a 1+1 Port" procedure on page 3-7 . If a Force switch was applied in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page 3-7 .

Step 5 When the alarm has been cleared, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure as needed.


2.5.27  CONTBUS-1

Major (MJ), Non-Service Affecting (NSA)

An Inbound Interconnection Control Bus 1 Failure on the TSC card, CXC card, or traffic (STM-N) cards occurs when one or more cards in the shelf experiences a control bus communication problem with the TSC card in Slot 10.

Troubleshoot with the "Clear the CONTBUS-0 Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.

2.5.28  CONTBUS-CLK-0

Major (MJ), Non-Service Affecting (NSA)

An Inbound Interconnection Timing Control Bus 0 Failure alarm to the Slot 10 TSC card alarm occurs if the timing signal from the Slot 5 TSC card has an error. If the Slot 10 TSC card and all other cards on the shelf raise this alarm, the alarm processor on the Slot 5 TSC card clears the alarm on the other cards and raises this alarm against the Slot 5 TSC card only.

Troubleshoot with the "Clear the CONTBUS-0 Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.


2.5.29  CONTBUS-CLK-1

Major (MJ), Non-Service Affecting (NSA)

An Inbound Interconnection Timing Control Bus 1 Failure alarm on the Slot 5 TSC card alarm occurs if the timing signal from the Slot 10 TSC card has an error. If the Slot 5 TSC card and all other cards on the shelf raise the alarm, the processor on the Slot 10 TSC card clears the alarm on the other cards and raises this alarm against the Slot 10 TSC card only.

Troubleshoot with the "Clear the CONTBUS-0 Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.


2.5.30  CONTCOM

Major (MJ), Non-Service Affecting (NSA)

The Interconnection Control Communication Failure alarm occurs when the internal messaging processor on the reporting active TSC card fails.

A TSC card should boot and be in the ready state within approximately five minutes. If the CONTCOM clears within this time frame and the TSC card goes to standby or active mode as applicable, no action is necessary.

If the communication equipment on the backplane fails, a CONTBUS alarm occurs instead of a CONTCOM alarm.

Clear the CONTCOM Alarm


Step 1 Complete the "2.6.8Hard-Reset the TSC Using CTC" procedure.

Step 2 If the CTC reset does not clear the alarm, remove and reinsert (reseat) the reporting card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 3 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.

Step 5 When the alarm has been cleared, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure as needed.


2.5.31  CTNEQPT-PB-0

Critical (CR), Service Affecting (SA)

The CXC-0 Data Payload Bus Interconnect Failure alarm occurs when the data path interconnection between equipment from CXC-0 (Slot 6) to inbound or outbound traffic (STM-N) card slots experiences failure. The CXC card and the reporting card are no longer communicating through the backplane. The problem exists in the CXC card, the reporting traffic card, or the backplane. If more than one traffic card on the shelf raises this alarm, the TSC card clears this alarm on the traffic cards and raises it against CXC-0.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.



Note When an alarm includes a numeric designation, it indicates whether the alarm applies to the first or second card of a specific type on the shelf. A zero indicates that the alarm occurs against the first card of its type, from left to right, in the shelf. A one indicates that the alarm occurs against the second card of its type in the shelf.



Note If you insert a new TSC card that has the same version of software as the active and standby TSC card, it takes approximately three minutes for the standby TSC card to become available.



Note It takes approximately 20 minutes for the active TSC card to transfer the system software to the newly installed TSC card. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.


Clear the CTNEQPT-PB-0 Alarm


Step 1 If the alarm occurs against a single traffic (STM-N) card, continue with Step 2. If the alarm occurs against multiple traffic cards, it indicates a problem with the CXC card. Continue with Step 6.

Step 2 If the traffic card ports are part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page3-4. If the ports are part of a 1+1 group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page3-4.

Step 3 Perform a CTC hard reset on the traffic card:


Caution Use hard resets with caution. There can be up to 15 other sets of STM-16 bandwidth that could be affected by a hard reset.


a. Open node view.

b. Position the CTC cursor over the card reporting the alarm.

c. Right-click and choose Hard-reset Card from the shortcut menu .

d. Click Yes in the Hard-reset Card dialog box.

Step 4 If the CTC reset does not clear the alarm, remove and reinsert (reseat) the reporting card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 5 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure.


Note If the traffic card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH ProcedureGuide. Label the bad port and take it out of service until the card can be replaced.


Step 6 If you replace the traffic card and the alarm does not clear, a CXC card problem is indicated. If an automatic switch to the alternate copy CXC card occurred, the CXC card can be serviced. If traffic has not switched, request a preferred copy switch by completing the "2.6.6Request a Cross-Connect Card Preferred Copy Switch" procedure.

To determine which CXC card is the preferred copy and whether it is currently being used, in node view go to the Maintenance > Preferred Copy window. The Data Copy area Preferred field shows Copy A or Copy B. The Currently Used field shows the copy being used.


Note In CTC, CopyA refers to the CXC card in Slot 6. CopyB refers to the CXC card in Slot 8. Either copy can be chosen as the preferred copy CXC card. The other CXC card is called the alternate CXC card in this chapter.


Continue with Step 7 .

Step 7 Perform a CTC soft reset on the CXC card:

a. Open the node view.

b. Position the CTC cursor over the card.

c. Right-click and choose Soft-reset Card from the shortcut menu .

d. Click Yes in the Soft-reset Card dialog box.

Step 8 If the CTC reset does not clear the alarm, remove and reinsert (reseat) the card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 9 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure for the CXC card.

Step 10 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country to report a service-affecting problem.

Step 11 Depending on which card raised the alarm, perform the following actions:

If traffic was manually switched in a 1+1 protection group, revert traffic to the original port by completing the "Clear a Force Switch on a 1+1 Port" procedure on page 3-7 .

If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page 3-7 .


Note If an automatic switch to the alternate copy CXC card occurred, traffic is automatically restored to the preferred copy.



2.5.32  CTNEQPT-PB-1

Critical (CR), Service Affecting (SA)

The CXC-1 Data Payload Bus Interconnect Failure alarm occurs when the data path interconnection fails between equipment from CXC-1 (Slot 8) and traffic card slots. If more than one traffic card on the shelf raises this alarm, the TSC card clears the alarm on the traffic cards and raises the alarm against the CXC-1. Troubleshoot with the "Clear the CTNEQPT-PB-0 Alarm" procedure.

2.5.33  CXCHALT

Major (MJ), Service Affecting (SA)

A CXC Operation Suspended alarm indicates that operation on the alternate CXC card has halted because of problems in Fan Tray 2, which services control cards including the CXC cards.

The CXCHALT alarm occurs five minutes after a fan failure alarm such as the "FAN-DEGRADE" alarm on page2-36, the "FAN-FAIL" alarm on page2-36, the "IMPROPRMVL (FAN)" alarm on page2-48, or the "FAN-FAIL-PARTIAL" alarm on page2-37 to halt alternate CXC operation.


Caution If a CXCHALT occurs due to a fan failure you should move a working fan assembly from Tray 1 or 3 and install it in the Tray 2 position, because the remaining working CXC card can be damaged in as little as 15 minutes. If damage occurs to the remaining CXC card, it will restart and then fail. Traffic is dropped until a replacement is installed.


Troubleshoot the fan alarm by following the "Clear the FAN-FAIL Alarm" procedure, which includes fan replacement.

2.5.34  DATAFLT

Minor (MN), Non-Service Affecting (NSA)

The Software Data Integrity Fault alarm occurs when the network element (NE) or shelf TSC card exceeds its flash memory capacity.


Caution When the system reboots, configurations older than three minutes are saved.


Log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.

2.5.35  EOC

Minor (MN), Non-Service Affecting (NSA)

The Embedded Operations Channels alarm occurs for traffic (STM-N) card ports when the ONS15600SDH loses its DCC while establishing connections between nodes. If regenerator section DCC is not enabled at the far-end port, the near-end port reports EOC. If both ports have regenerator section DCC (SDCC) enabled and have working fiber connections, the EOC alarm clears.

The DCC is three bytes, D1 through D3, in the SDH section overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS15600SDH uses the DCC on the section DCC to communicate network management information.


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the EOC Alarm


Step 1 If the "LOS" alarm on page2-54 is also reported, complete the "Clear the LOF Alarm" procedure. If the "MS-EXC" condition on page2-64 is reported, complete the "Clear the MS-DEG Condition" procedure.

Step 2 Verify that the far-end traffic card port is cabled to the node traffic card port reporting the EOC alarm, and verify that the far-end transmitting card port is in service.

A traffic card that is ready for service and has at least one port enabled has green SRV and Laser On LEDs illuminated. If the SRV LED is amber, the card is not in service.

Step 3 If the alarm does not clear, verify that the far-end section DCC is enabled:

a. Under the node view, click the Provisioning > RS DCC tabs.

b. If the slot and port are listed in the SDCC Terminations list, the DCC is provisioned. If the slot and port are not listed in the SDCC Terminations list, click Create .

c. Click the traffic card and select the port that links to the adjacent node.

d. Click OK .

Step 4 If the alarm does not clear, perform a soft reset on the near-end and far-end traffic cards:

a. Open the node view.

b. Position the cursor over the card.

c. Right-click and choose Soft-reset Card from the shortcut menu.


Note If a traffic (STM-N) card with an active port in a 1+1 protection group is soft reset, all DCC traffic terminated or tunneled on the active port is lost while the card resets. No DCC traffic is lost during a soft reset of an optical card associated with a standby port.


d. Click Yes in the Soft-reset Card dialog box.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of TAC toll-free numbers for your country.


2.5.36  EQPT (CAP)

Major (MJ), Non-Service Affecting (NSA)

An Equipment Failure alarm for a CAP card indicates a card failure. Troubleshoot with the "Clear the EQPT Alarm" procedure

If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.37  EQPT (CXC, Traffic Card, TSC)

Critical (CR), Service Affecting (SA)

An Equipment Failure alarm for a CXC card, TSC card, or traffic (STM-N) card indicates a card failure.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the EQPT Alarm


Step 1 If the reporting card is an active traffic card in a 1+1 group or is part of an SNCP, it is likely that an APS traffic switch has occurred on this port.

An SNCP APS is identified by an AUTOSW-type alarm or condition (such as AUTOSW-AIS, AUTOSW-LOP-SNCP, AUTOSW-PDI-SNCP, AUTOSW-SDBER-SNCP, AUTOSW-SFBER-SNCP, or AUTOSW-UNEQ-SNCP).

A 1+1 APS is identified on the node view Maintenance > Protection window. If you click the protection group, in the Selected Group list, the ports are designated as Working/Standby and Protect/Active.

If the traffic has not switched to the protect port and it is part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page 3-4 . If the port is part of a 1+1 group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page 3-4 .

Step 2 The EQPT alarm can also indicate that another problem has occurred. Check for other alarms and follow the troubleshooting procedures as necessary. If you are still unable to complete this procedure, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

Step 3 If the reporting card is a CXC card and an automatic switch to the alternate copy CXC card occurred, the CXC card can be serviced. If traffic has not switched to the alternate CXC card, complete the "2.6.6Request a Cross-Connect Card Preferred Copy Switch" procedure.

Step 4 If the reporting card is a CXC card, traffic (STM-N) card, or TSC card, remove and reinsert (reseat) the card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card back into the slot along the guide rails.

d. Close the ejectors.

Step 5 If the physical reseat of the card does not clear the alarm, complete the "2.6.15Remove and Replace a Card" procedure.


Note If the traffic card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH Procedure Guide. Label the bad port, and place it out of service until the card can be replaced.


Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

Step 7 If the reporting card was the active TSC card and you want to switch it from standby back to active, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.

Step 8 If an automatic switch to the alternate copy CXC card occurred, traffic is automatically restored to the preferred copy.

If the reporting card is a traffic card, traffic reverts to the working port if an automatic switch occurred. If traffic was manually switched in a 1+1 protection group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page 3-4 . If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page 3-7 .


2.5.38  EQPT-BOOT

Critical (CR), Service Affecting (SA)

An Equipment Boot Failure alarm occurs when a TSC card, CXC card, or traffic (STM-N) card does not fully boot from the restart point after self-rebooting three times. Troubleshoot with the "Clear the EQPT Alarm" procedure.

2.5.39  EQPT-HITEMP

Minor (MN), Non-Service Affecting (NSA)

The Equipment Failure High Temperature alarm occurs when the TSC card, CXC card, or traffic (STM-N) card internal temperature exceeds 185 degrees Fahrenheit (85 degrees Celsius).


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the EQPT-HITEMP Alarm


Step 1 Ensure that the room temperature is not abnormally high.

Step 2 If the room temperature is not the cause of the alarm, ensure that filler modules are installed in the ONS15600SDH empty slots. Filler modules help airflow.

Step 3 If the "FAN-DEGRADE" alarm on page2-36 or the "FAN-FAIL" alarm on page2-36 accompanies the alarm, complete the "Clear the FAN-FAIL Alarm" procedure.

Step 4 If the alarm does not clear, check the condition of the air filter to see if it needs cleaning or replacement. Complete the "Replace the Air Filter" procedure on page3-10 as needed.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.40  E-W-MISMATCH

Major (MJ), Service-Affecting (SA)

A Procedural Error Misconnect East/West Direction alarm occurs when nodes in a ring have an east slot misconnected to another east slot or a west slot misconnected to another west slot. In most cases, the user did not connect the fibers correctly, or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but might change the traditional east-west node connection pattern of the ring.


Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its East-West slots configured correctly. If the alarm appears during the initial setup, the alarm clears itself shortly after the ring setup is complete.



Note The lower numbered slot at a node is traditionally labeled as the west slot and the higher numbered slot is labeled as the east slot. For example, Slot 2 is west and Slot 12 is east.



Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.


Clear the E-W-MISMATCH Alarm with a Physical Switch


Step 1 Diagram the ring setup, including nodes and spans, on a piece of paper or white board.

Step 2 In the node view, from the View menu choose GotoNetworkView .

Step 3 Label each of the nodes on the diagram with the same name that appears on the network map.

Step 4 Right-click each span to reveal the node name/slot/port for each end of the span.

Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1-
Node2/Slot2/Port1 (2F MS-SPRing STM16, Ring ID=0), label the end of the span that connects Node1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 2/Port 1.

Step 6 Repeat Steps 4 and 5 for each span on your diagram.

Step 7 Label the highest slot at each node "east" and the lowest slot at each node "west."

Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span.

Step 9 If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.


Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Step 10 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


Clear the E-W-MISMATCH Alarm in CTC


Step 1 Log into the misconnected node. A misconnected node has both ring fibers connecting it to its neighbor nodes misconnected.

Step 2 Click the Maintenance > MS-SPRing tabs.

Step 3 From the row of information for the fiber span, complete the "2.6.1Identify a Ring ID or Node ID Number" procedure to identify the node ID, ring ID, and the slot and port in the East Line list and West Line columns. Record the above information.

Step 4 From the View menu choose GotoNetworkView .

Step 5 Delete and recreate the MS-SPRing:

a. Click the Provisioning > MS-SPRing tabs.

b. Click the row from Step 3  to select it and click Delete .

c. Click Create MS-SPRing .

d. Fill in the ring ID and node ID from the information collected in Step 3 .

e. Click OK in the MS-SPRing Creation window.

Step 6 Open the node view and click the Maintenance > MS-SPRing tabs.

Step7 Change the West Line drop-down menu to the slot you recorded for the East Line in Step 3.

Step 8 Change the East Line drop-down menu to the slot you recorded for the West Line in Step 3.

Step 9 Click OK .

Step 10 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.41  EXERCISE-RING-FAIL

Not Alarmed (NA), Non-Service Affecting (NSA)

The Exercise-Ring command issues ring protection switching of the requested channel without completing the actual bridge and switch. The EXERCISE-RING-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.


Note If the exercise command gets rejected due to the existence of a higher priority condition in the ring, EXERCISE-RING-FAIL will not be reported.


Clear the EXERCISE-RING-FAIL Condition


Step 1 Look for and clear an MS-SPRing alarm or the "LOF" alarm on page2-52.

Step 2 Reissue the Exercise Ring command:

a. Click the Provisioning > MS-SPRing tabs.

b. Click the row of the affected ring in the West Switch column.

c. Select Exercise Ring in the drop-down menu .

Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.42  EXT

Minor (MN), Non-Service Affecting (NSA)

An External Facility alarm is detected external to the node because an environmental event, such as an open door or flooding, has occurred.

Follow your standard operating procedure to remedy environmental conditions that cause alarms. The alarm clears when the situation is remedied. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.43  FAILTOSW

Critical (CR), Service Affecting (SA)

The Failure to Switch alarm occurs when a working circuit does not switch to the protect circuit in an SNCP. Common causes of this alarm include a missing or defective protection port, a lockout of protection on the working or protect path, or path level defects/alarms that would cause an SNCP switch to fail including the "AU-AIS" condition on page2-14, the "AU-LOP" alarm on page2-14, the "UNEQ-P" alarm on page2-82, the "HP-EXC" condition on page2-43, and the "HP--DEG" condition on page2-43.

The "LOF" alarm on page2-52, the "LOS" alarm on page2-54, the "MS-DEG" condition on page2-62, or the "MS-EXC" condition on page2-64 can also occur on the failed path.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the FAILTOSW Alarm on an SNCP


Step 1 If the "AU-AIS" condition on page2-14, the "AU-LOP" alarm on page2-14, the "UNEQ-P" alarm on page2-82, the "HP-EXC" condition on page2-43, the "HP--DEG" condition on page2-43, the "LOF" alarm on page2-52, the "LOS" alarm on page2-54, the "MS-DEG" condition on page2-62, or the "MS-EXC" condition on page2-64 are also occurring on the reporting port, complete the applicable alarm clearing procedure.

If the alarm does not clear, physically check the fiber connections to the card and ports to ensure that they are securely fastened and intact. For more information about fiber connections and terminations, refer to the Cisco ONS 15600 SDH Procedure Guide.

Step 2 In node view, click the Circuits > Circuits tabs.

Step 3 Highlight the path where you tried to perform the switch. In the Switch State column, verify that the state is Clear. If it is not, select Clear from the list.

Step 4 Click Apply .

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.44  FAILTOSWR

Not Alarmed (NA), Non-Service Affecting (NSA)

The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems.

FAILTOSWR clears with one of the following events: a higher priority event, such as an external switch command occurs, the next ring switch succeeds, or the cause of the APS switch clears.


Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Clear the FAILTOSWR Condition in a Two-Fiber MS-SPRing Configuration


Step 1 Perform the EXERCISE RING command on the reporting card:

a. Click the Maintenance > MS-SPRing tabs.

b. Click the row of the affected ring in the West Switch column.

c. Select EXERCISE_RING in the drop-down menu.

Step 2 If the condition does not clear, in node view choose GotoNetworkView from the View menu.

Step 3 Look for alarms on STM-N cards that make up the ring or span and troubleshoot these alarms.

Step 4 If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node and click the Maintenance > MS-SPRing tabs.

Step 5 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-N cards are active and in service:

a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.

A green LED indicates an active card. An amber LED indicates a standby card.

b. To determine whether the STM-N port is in service, double-click the card in CTC to open the card view.

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS . Click Apply .

Step6 If the STM-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.

Step 7 If fiber continuity to the ports is OK, verify that the correct port is in service:

a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.

A green LED indicates an active card. An amber LED indicates a standby card.

b. To determine whether the STM-N port is in service, double-click the card in CTC to open the card view.

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS . Click Apply .

Step 8 If the correct port is in service, use an optical test set to verify that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.


Caution Using an optical test set disrupts service on the optical (traffic) card. It might be necessary to manually switch traffic carrying circuits over to a protection path.


Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, use the procedure in the CiscoONS15600SDH Procedure Guide.

Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the STM-N card's receiver specifications. The "Optical Traffic Card Transmit and Receive Levels" section on page1-32 lists these specifications.

Step 11 Repeat Steps 6 through 10 for any other ports on the card.

Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Replace an STM-16 Card or STM-64 Card" procedure on page3-2 for the protect standby STM-N card.

Step 13 If the condition does not clear after you replace the MS-SPRing cards on the node one at a time, follow
Steps 4 through 12 for each of the nodes in the ring.

Step 14 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.45  FAN-DEGRADE

Minor (MN), Non-Service Affecting (NSA)

The Partial Fan Failure Speed Control Degradation alarm occurs if the fan speed in Fan Tray 1, 2, or 3 falls below 500 RPM when read by a tachometry counter.

Troubleshoot with the "Clear the FAN-FAIL Alarm" procedure.

If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.46  FAN-FAIL

Critical (CR), Service Affecting (SA)

The Fan Failure alarm occurs when two or more fans (out of a total of six) have failed. There is no standby fan. All fans should be active. The FAN_FAIL alarm can be accompanied by the "MFGMEM (FAN)" alarm on page2-61.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the FAN-FAIL Alarm


Step 1 If the "MFGMEM (FAN)" alarm on page2-61 is also reported, complete the "Clear the MFGMEM (FAN) Alarm" procedure.

Step 2 If the alarm does not clear, check the condition of the air filter to see if it needs cleaning or replacement using the "Replace the Air Filter" procedure on page3-10.

Step 3 If the alarm does not clear and if the filter is clean, take the reporting fan trays out of the ONS15600SDH.

Step 4 Reinsert the fan trays, making sure you can hear the fans start operating.

Fans should run immediately when correctly inserted.

Step 5 If the alarm does not clear or if the fans do not run, replace the fan trays using the "Replace a Fan Tray" procedure on page3-11.

Step 6 If the alarm does not clear or if the replacement fan trays do not operate correctly, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.47  FAN-FAIL-PARTIAL

Major (MJ), Non-Service Affecting (NSA)

The Partial Fan Failure alarm occurs when one of the six fans in the shelf fails.

Troubleshoot with the "Clear the FAN-FAIL Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.48  FAN-PWR

Minor (MN), Non-Service Affecting (NSA)

The Fan Power Failure alarm occurs when a power feed (A or B) from the shelf to Fan Tray 1, 2, or 3 fails. Because fans are not able to differentiate the power feeds, there is only one alarm for A or B failure.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the FAN-PWR Alarm


Step 1 Remove the reporting fan trays from the ONS15600SDH.

Step 2 Reinsert the fan trays, making sure you hear the fans start to operate.

Fans should run immediately when correctly inserted.

Step 3 If the alarm does not clear or if the fans do not run, replace the fan trays using the "Replace a Fan Tray" procedure on page3-11.

Step 4 If the alarm cannot be cleared, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.49  FE-FRCDWKSWPR-SPAN

Minor (MN), Minor (MN)

The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a two-fiber MS-SPRing is forced from working to protect using the FORCE SPAN command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Clear the FE-FRCDWKSWPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE alarm/condition on a card in Slot 12 of Node 1 might link to the main alarm from a card in Slot 1 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 4 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.50  FEPRLF

Minor (MN), Non-Service Affecting (NSA)

The Far-End APS Channel Protection Line Failure alarm occurs on traffic (STM-N) cards when an APS-switching channel signal failure occurs on the protect card that transmits to the node.

Clear the FEPRLF Alarm


Step 1 Determine which node and port link directly to the card reporting the FEPRLF alarm. For example, an FE alarm/condition on a card in Slot 12 of Node 1 might link to the main alarm from a card in Slot 1 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE alarm.

Step 3 Look up and troubleshoot the main alarm.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.51  FE-LOCKOUTOFPR-SPAN

Not Alarmed (NA), Non-Service Affecting (NSA)

The Far-End Lock Out of Protection Span condition occurs when an MS-SPRing span is locked out of the protection system from a far-end node using the LOCKOUT SPAN command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-LOCKOUTOFPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Clear the FE-LOCKOUTOFPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE alarm/condition on a card in Slot 12 of Node 1 might link to the main alarm from a card in Slot 1 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Make sure there is no lockout set. See the "2.6.14Clear an MS-SPRing Span Lockout" procedure for instructions.

Step 4 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.52  FE-MANWKSWPR-RING

Not Alarmed (NA), Non-Service Affecting (NSA)

The Far End Ring Manual Switch of Working Facility to Protect condition occurs when an MS-SPRing working ring is switched from working to protect at a far-end node using the MANUAL RING command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-MANWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Clear the FE-MANWKSWPR-RING Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE alarm/condition on a card in Slot 12 of Node 1 might link to the main alarm from a card in Slot 1 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 4 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.53  FORCED-REQ

Not Alarmed (NA), Non-Service Affecting (NSA)

The Force Switch Request Path condition occurs when you enter the Force command on an SNCP circuit to switch traffic from a working circuit to a protect circuit or vice versa. You do not need to clear this condition if you want the Force switch to remain intact. If you want to clear this condition, complete the "Clear a Force Switch on a SNCP Span" procedure on page3-7.

2.5.54  FORCED-REQ-RING

Not Alarmed (NA), Non-Service Affecting (NSA)

The Force Switch Request Ring condition applies to optical trunk cards when the FORCE RING command is applied to two-fiber MS-SPRings to move traffic from working to protect.

Clear the FORCED-REQ-RING Condition


Step 1 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.55  FREQ-MISMATCH

Minor (MN), Non-Service Affecting (NSA)

The Frequency Mismatch alarm occurs when one of the two TSC cards has a timing module failure that causes an inconsistency between the TSC card timing frequencies. This alarm can be caused by the active or standby TSC card.

The ONS15600SDH checks timing frequency synchronization in 83-minute cycles. The FREQ-MISMATCH alarm occurs if two consecutive timing check cycles show frequency mismatches. The alarm is cleared if one cycle shows a timing frequency match between the TSC cards.

Clear the FREQ-MISMATCH Alarm


Step 1 Complete the "2.6.15Remove and Replace a Card" procedure for the standby TSC card.

Step 2 Wait for two intervals of 83 minutes (2 hours and 46 minutes) and check the node view Alarms window to see if the alarm is cleared.

During the initial 83-minute synchronization check cycle when the replacement standby TSC card is booting up, the replacement TSC card is attaining the timing from the BITS or internal source, so it is normal that the two TSC cards are not synchronized. The ONS 15600 SDH system disregards the result of this check cycle and begins keeping track of synchronization in the second 83-minute cycle. If the result of the cycle shows that the TSC cards are synchronized properly, the alarm is cleared.

Step 3 If the FREQ-MISMATCH alarm did not clear after two timing check cycles, it means that the second timing cycle resulted in a mismatch. Wait a third 83-minute cycle (1 hour and 23 minutes) and check the alarm again.

If the alarm has cleared, it means the third cycle showed that the TSC card timing modules were synchronized. If the alarm remains, it means that the ONS 15600 SDH system has had two frequency mismatch cycles, and indicates a problem with the other TSC card.

Step 4 If the FREQ-MISMATCH alarm remains after three 83-minute cycles, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure to make the TSC card standby.

Step 5 Complete the "2.6.15Remove and Replace a Card" procedure for the standby TSC card.

The card removal and reboot temporarily clears the alarm.

Step 6 Wait for three intervals of 83 minutes (4 hours and 9 minutes) and check CTC to see if the FREQ-MISMATCH alarm has recurred. If it has not recurred, the problem is solved.

Step 7 If the alarm has recurred after both TSC cards have been replaced, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.56  FRNGSYNC

Not Alarmed (NA), Non-Service Affecting (NSA)

The Free-Running Synchronization Mode condition occurs when the reporting node is in free-run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the ONS15600SDH has lost its designated BITS timing source.

Clear the FRNGSYNC Condition


Step 1 Check for additional alarms that relate to timing and troubleshoot as necessary.

Step 2 Reestablish a primary and secondary timing source according to local site practice. Refer to the CiscoONS15600SDH Procedure Guide for instructions.

Step 3 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.57  FSTSYNC

Not Alarmed (NA), Non-Service Affecting (NSA)

The Fast Synchronization condition occurs when the ONS15600SDH synchronizes its clock modules. Since the ONS15600SDH uses Stratum 3E timing, synchronization can take about 12 minutes. This condition occurs on the TSC card where the timing distribution is sourced. Whenever this condition is active, any timing or controller switching can affect the traffic. Errorless switching is not guaranteed. The "UNPROT-SYNCCLK" alarm on page2-83 can accompany this condition if there is no timing protection is available while the clock is synchronizing.

If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.58  FULLPASSTHR-BI

Not Alarmed (NA), Non-Service Affecting (NSA)

The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node in an MS-SPRing when the protect channels on the node are active and carrying traffic and a change is present in the receive K byte from No Request. (Both data and K bytes are in pass-through mode.)

Clear the FULLPASSTHR-BI Condition


Step 1 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.59  HELLO

Minor (MN), Non-Service Affecting (NSA)

The Open Shortest Path First (OSPF) Hello Fail alarm occurs when SDH DCC termination OSPF area IDs are mismatched between two DCC terminations for a span. On a span between two ONS15600SDHs, this alarm occurs at both nodes containing the mismatched DCC area IDs. On a span between an ONS15600SDH and an ONS 15600, this alarm is raised only on the ONS15600SDH node because the ONS 15600 does not currently support this alarm. Mismatched OSPF area IDs can cause CTC to lose management across the link.

Clear the HELLO Alarm


Step 1 Log into both end nodes with the DCC terminations.

Step 2 On the nodes where the alarm occurred, record the slot and port (from the Slot column and Port column in the Alarms window) that the Hello alarm occurs against. This information helps you determine which DCC termination is mismatched.


Tip You can log into another node by going to network view and double-clicking the node.


Step 3 On one node, in node view, click the Provisioning > Network > OSPF tabs.

Step 4 In the DCC/GCC OSPF Area ID Table area, locate the alarmed DCC termination by comparing slot and port numbers to the slot and port number indicated in the alarm on the node.

Step 5 Click the Area ID column cell for the mismatched DCC termination.

Step 6 Change the area ID in the cell to the same ID as its partner DCC termination. (ONS 15454 SDH, ONS 15600, and ONS15600SDH default to 0.0.0.0 format addresses.)

Step 7 Click Apply .

Step 8 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.60  HLDOVRSYNC

Not Alarmed (NA), Non-Service Affecting (NSA) condition

The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS15600SDH. It also usually occurs during the selection of a new node reference clock. This alarm indicates that the ONS15600SDH has gone into holdover and is using the ONS15600SDH G.813 internal reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips might begin to occur on an ONS15600SDH relying on an internal clock.

Troubleshoot with the "Clear the FRNGSYNC Condition" procedure . If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.61  HP--DEG

Not Alarmed (NA), Non-Service Affecting (NSA)

The High-Order Path Signal Degrade condition occurs when the B3 error count in the SDH overhead exceeds the limit. Troubleshoot with the "Clear the MS-DEG Condition" procedure.

2.5.62  HP-EXC

Not Alarmed (NA), Non-Service Affecting (NSA)

The High Order Path-Excessive BER condition occurs when the B3 error count in the SDH overhead exceeds the limit. Troubleshoot with the "Clear the MS-DEG Condition" procedure.

2.5.63  HP-RDI

Not Reported (NR), Non-Service Affecting (NSA)

A High Order Path-Remote Fault Indication condition occurs when the ONS15600SDH detects an RFI in the SDH overhead of the VC4 signal because of a fault in another node. Resolving the fault in the adjoining node clears the HP-RDI alarm in the reporting node.

HP-RDI occurs in the node that terminates a path. The path layer is the segment between the originating equipment and the terminating equipment. This segment can encompass several consecutive line segments. An HP-RDI error message on theONS15600SDH indicates that the node reporting the HP-RDI is the terminating node on that path segment.

Clear the HP-RDI Condition


Step 1 Verify that the ports are enabled and in-service on the reporting ONS15600SDH.

In the card-level view, traffic port state is indicated by the color of the port:

Gray—Out of service (OOS)

Green—In service (IS)

Red—Critical alarm

Yellow—Minor alarm

Orange—Major alarm

Step 2 If a port is OOS, click the Provisioning > MS tabs and choose In Service from the drop-down menu for that port. Click Apply .

Step 3 To find the path and node failure, verify the integrity of the SDH circuit path at each of the intermediate SDH nodes, checking for inconsistencies in path size or protection configuration.

Step 4 Identify and resolve alarms in reporting node. The "UNEQ-P" alarm on page2-82 frequently needs to be resolved. Complete the "Clear the UNEQ-P Alarm" procedure.

Step 5 If the condition does not clear, log on to http://www.cisco.com/tac for more information or clog into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.64  HP-TIM

Minor (MN), Non-Service Affecting (NSA)

The High Order Path Trace Identifier Mismatch alarm occurs when the current expected High Order Path path trace string does not match the current received path trace string. Path Trace Mode must be set to manual for this alarm to occur.

In manual mode in the High Order Path Trace area, the user can type a new expected string into the field. This string must match the string typed into the Current Received String field for the sending port. If these fields do not match, it is typically because of an upstream path terminating equipment (PTE) error.

Clear the HP-TIM Alarm


Step 1 Log into CTC at the circuit source and note which slot and port is reporting the alarm in the Alarms window.

Step 2 Click the Circuits > Circuits tabs.

Step 3 Select the circuit reporting the alarm by identifying it according to its Source or Destination column slots and ports. This circuit has probably switched to the protect port.

Step 4 Click Edit .

Step 5 Click Show Detailed Map at the bottom of the Edit Circuits window.

Step 6 On the detailed circuit map, right-click the drop/destination circuit port and choose Edit Path Trace from the shortcut menu.

Step 7 Compare the Current Received String and Current Expected String entries in the path trace dialog box.

Step 8 If the strings differ and the Current Received String is correct but the Current Expected String is not, correct the Transmit or Expected strings and click Apply .

Step 9 If the strings differ and the Current Expected String is correct but the Current Received String is not, there is a problem with the PTE upstream. Troubleshoot the problem in the PTE.

Step 10 Click Close .

Step 11 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.65  HP-UNEQ

Critical (CR), Service-Affecting (SA)

The High Order Path Unequipped alarm applies to the C2 path signal label byte in the high-order (VC-4) path overhead. HP-UNEQ occurs when no C2 byte is received in the SDH path overhead.

Clear the HP-UNEQ Alarm


Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the alarm to display the Select Affected Circuits dialog box.

Step 3 Click the Select Affected Circuits dialog box.

Step 4 When the affected circuits appear, look in the Type column for VC.

Step 5 If the Type column does not contain VC, there are no VCs. Go to Step 8.

Step 6 If the Type column does contain VC, attempt to delete these row(s):


Note Note The node does not allow you to delete a valid VC.


a. Click the VC row to highlight it. Complete the "2.6.5  Delete a Circuit" procedure 

b. If an error message dialog box appears, the VC is valid and not the cause of the alarm.

Step 7 If any other columns contain VC, repeat Step 6.

Step 8 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the State column of any circuits.

Step 9 If you find circuits listed as incomplete, verify these circuits are not working circuits that continue to pass traffic with an appropriate optical test set and site-specific procedures.

For specific procedures to use the test set equipment, consult the manufacturer.

Step 10 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "2.6.5  Delete a Circuit" procedure .

Step 11 Recreate the circuit with the correct circuit size. Refer to the CiscoONS15600SDH Procedure Guide for circuits procedures.

Step 12 Log back in and verify that all circuits terminating in the reporting card are active:

a. Click the Circuits tab.

b. Verify that the State column lists all circuits as active.

Step 13 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the CiscoONS15600SDH Procedure Guide.


Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).



Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Step 14 If the alarm does not clear, complete the "2.6.9Physically Replace a Card" procedure for the optical and/or electrical cards.


Note When you replace a card with an identical type of card, you do not need to make any changes to the database.


Step 15 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.66  IMPROPRMVL (CAP)

Major (MJ), Non-Service Affecting (NSA)

The Improper Removal CAP alarm occurs when a CAP is not correctly installed on the backplane or is missing altogether. The problem is not user serviceable. Log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.67  IMPROPRMVL (CXC, Traffic Card, TSC)

Critical (CR), Service Affecting (SA)

Minor (MN), Service Affecting (SA)

The Improper Removal (CXC, Traffic Card, or TSC) alarm occurs when a TSC card, CXC card, or traffic (STM-N) card is physically removed from its slot before being deleted from CTC. This alarm can occur if the card is recognized by CTC and the active TSC card but is not in service. For example, it could be inserted in the slot but not fully plugged into the backplane.

If the removed TSC card or CXC card is the last one on the shelf, the severity is Critical and traffic is affected. Otherwise, the alarm is minor.


Caution Do not remove and reinsert (reseat) a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.



Note After deleting a card in CTC, the software allows you approximately 15 seconds to physically remove the card before CTC begins a card reboot.


Clear the IMPROPRMVL Alarm


Step 1 Depending on the card reporting the alarm, take the following actions:

a. If the card is a CXC card or TSC card, continue with Step 6 .

b. If the reporting card is a traffic card and if the ports are in service, take the ports out of service:

Double-click the reporting card to open the CTC card view.

Click the Provisioning tab.

Click the Status column of any in-service ports.

Choose Out of Service to take the ports out of service.

Step 2 Check whether the port is paired in a 1+1 group; if so, delete the protection group:

a. At the node view, click the Provisioning > Protection tabs.

b. Under the Protection Groups list, click the protection group of the reporting port.

c. Click Delete .

Step 3 Check whether the card is provisioned as a DCC termination; if so, delete the DCC:

a. At the node view, click the Provisioning > DCC/GCC tabs.

b. Click the termination in the SDCC Terminations list.

c. Click Delete and click Yes in the dialog box that appears.

Step 4 Check whether the card is used as a timing reference; if so, change the timing reference:

a. At the node view, click the Provisioning > Timing tabs.

b. In the General Timing area, check whether the Timing Mode is Line. If so, the source is internal to the SNCP circuit and the reference must be moved.

c. Click the Ref-1 and/or Ref-2 drop-down menu.

d. Change the reference to Internal Clock or move the line timing selection to another card on the shelf.

e. Click Apply .

Step 5 Check whether the card is carrying circuits. If so, delete the circuits:


Caution Before deleting the circuit, ensure that it is not carrying live traffic.


a. At the node view, click the Circuits > Circuits tabs.

b. Click the applicable path that connects to the reporting card.

c. Click Delete .

Step 6 Right-click the card reporting the IMPROPRMVL and choose Delete .


Note CTC does not allow you to delete a card if any port on the card is in service, if it has circuits, if it is in a protection scheme, if DCCs are enabled, or if it is used as a timing reference.


Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.68  IMPROPRMVL (FAN)

Critical (CR), Service Affecting (SA)

The Improper Removal Fan alarm occurs when Fan Tray 1, 2, or 3 is physically removed from its slot.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the IMPROPRMVL (FAN) Alarm


Step 1 Complete the "Replace a Fan Tray" procedure on page3-11.

Step 2 If the fan tray does not run immediately, troubleshoot with the "Clear the FAN-FAIL Alarm" procedure.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.69  INTRUSION

Not Alarmed (NA), Non-Service Affecting (NSA)

The Invalid Login condition occurs when a user tries to log into a node with an invalid ID or password three times. The user can retry by restarting the session.

If for some reason the alarm does not clear after the site security has been established, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.70  INVMACADR

Major (MJ), Non-Service Affecting (NSA)

The Invalid MAC Address alarm occurs when the ONS15600SDH MAC address retrieval fails and the node does not have a valid MAC address to support the operating system (OS). Do not attempt to troubleshoot an INVMACADR alarm. To contact the CiscoTAC, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.71  KB-PASSTHR

Not Alarmed (NA), Non-Service Affecting (NSA)

The K Bytes Pass Through Active condition occurs on a nonswitching node in an MS-SPRing when the protect channels on the node are not active and the node is in K Byte Pass-Through state.

Clear the KB-PASSTHR Condition


Step 1 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.72  LASER-BIAS (STM-64)

Major (MJ), Service Affecting (SA)

The High Laser Bias Current alarm occurs when a port on an STM-64 card is transmitting a laser current outside of the acceptable preset range. The alarm occurs at the card level rather than at the port level. The alarm is typically accompanied by signal or bit errors on the downstream node.


Note The difference between this alarm and the laser bias current performance-monitoring parameter is that the alarm indicates a serious physical condition in the transmitter.


Clear the LASER-BIAS Alarm


Step 1 If the alarm is reported against the working STM-64 card and traffic has not automatically switched to protect, initiate a Force switch. If it is part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page3-4. If is part of a 1+1 group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page3-4.

Step 2 Complete the "2.6.15Remove and Replace a Card" procedure for the reporting card.

If the alarm does not clear after replacing the card, log on to http://www.cisco.com/tac f or more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or t o report a service-affecting problem.

Step 3 Traffic reverts to the working port if an automatic switch occurred. If the alarm cleared and traffic was switched in Step 1, revert traffic by completing the "Clear a Force Switch on a 1+1 Port" procedure on page3-7. If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page3-7.


2.5.73  LASER-OVER-TEMP (STM-64)

Critical (CR), Service Affecting (SA)

The Port-Level High Temperature STM-64 equipment alarm accompanies a fault in one of the four STM-64 ports. The fault causes output signal bit errors that are detected by the downstream node, which performs an APS.

If more than one card has this condition, troubleshoot with the "Clear the EQPT-HITEMP Alarm" procedure. Any time an STM-64 card or port reports an over-temperature condition, follow the "Clear the LASER-BIAS Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.

2.5.74  LKOUTPR-S

Not Alarmed (NA), Non-Service Affecting (NSA)

The Lockout of Protection Span condition occurs on a MS-SPRing node when traffic is locked out of a protect span using the LOCKOUT SPAN command.

Clear the LKOUTPR-S Condition


Step 1 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.75  LOCKOUT-REQ

Not Alarmed (NA), Non-Service Affecting (NSA)

The Lockout Request on Path Facility condition occurs on traffic (STM-N) cards when a user initiates a lockout switch request on an SNCP circuit. An SNCP circuit lockout prevents automatic protection switching from occurring. Clearing the lockout clears the condition.


Caution Leaving a lockout enabled after the condition that required it is resolved can result in later traffic loss.


Clear the Lockout Switch Request and the LOCKOUT-REQ Condition


Step 1 Complete the "Clear a Force Switch on a SNCP Span" procedure on page3-7.

Step 2 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.76  LOF (BITS)

Major (MJ), Service Affecting (SA)

Minor (MN), Non-Service Affecting (NSA)

The Loss of Frame (BITS) alarm is major if there is no backup TSC card BITS source and minor if one of the TSC cards BITS sources fails. If one of the pair fails, a timing APS is activated on the second source.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the LOF (BITS) Alarm


Step 1 Verify that the framing and coding match between the BITS input and the TSC card:

a. Find the coding and framing formats of the external BITS timing source. This should be in the user documentation for the external BITS timing source or on the external timing source itself.

b. Click the node view Provisioning > Timing tabs to open the General Timing window.

c. Verify that coding matches the coding of the BITS timing source.

d. If the coding does not match, click Coding to reveal a menu. Choose the appropriate coding.

e. Verify that Framing matches the framing of the BITS timing source.

f. If the framing does not match, click Framing to reveal the menu. Choose the appropriate framing.


Note In the Timing window, the B8ZS (binary 8-zero substitution) coding field is normally paired with ESF (Extended Superframe) in the Framing field, and the AMI (alternate mark inversion) coding field is normally paired with SF (Super Frame) (D4) in the Framing field.


Step 2 Ensure that the BITS clock is operating properly.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.77  LOF

Critical (CR), Service Affecting (SA)

Minor (MN), Non Service Affecting (NSA)

The Loss of Frame alarm occurs when a port on the reporting traffic (STM-N) card has an LOF. LOF indicates that the receiving ONS15600SDH has lost frame delineation in the incoming data. LOF occurs when the SDH overhead loses a valid framing pattern for three milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.

LOF on a traffic card is sometimes an indication that the port reporting the alarm expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver.

If the port is in 1+1 protection and successfully switches, the alarm severity is MN, NSA. If the port is unprotected or if protection switching is prevented, the severity is CR, SA.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the LOF Alarm


Step 1 Verify that the automatic protection switch to the protect port was successful.


Note APS switches are hitless in the ONS15600SDH.


An SNCP APS is identified by an AUTOSW-type alarm or condition (such as AUTOSW-AIS, AUTOSW-LOP-SNCP, AUTOSW-PDI-SNCP, AUTOSW-SDBER-SNCP, AUTOSW-SFBER-SNCP, or AUTOSW-UNEQ-SNCP).

A 1+1 APS is identified on the node view Maintenance > Protection window. If you click the protection group, in the Selected Group list, the ports are designated as Working/Standby and Protect/Active.

Step 2 Verify that the traffic (STM-N) card and port on the upstream node is in service.

On an in-service traffic card, the green SRV and Laser On LEDs are illuminated.

If the card ports are in service, in the card view Provisioning window, the Status column(s) for the port(s) show In Service. If the ports are not in service, click the port column and choose In Service , then click Apply .

Step 3 If the alarm does not clear, clean the optical fiber connectors:

a. Clean the fiber connectors according to local site practice.

b. If no local practice exists, use a Cletop Real-Type or equivalent fiber-optic cleaner and follow the instructions accompanying the product and/or consult the procedures in the Cisco ONS 15600 SDH Procedure Guide.

Step 4 If you continue to receive the LOF alarm, see the "Optical Traffic Card Transmit and Receive Levels" section on page1-32.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.78  LOS (BITS)

Major (MJ), Service Affecting (SA)

Minor (MN), Non-Service Affecting (NSA)

The Loss of Signal BITS alarm is major if there is no backup TSC card BITS source, and minor if one of the TSC card BITS sources fails. If one of the pair fails, a timing APS is activated on the second source.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the LOS (BITS) Alarm


Step 1 Check the wiring connection from the ONS15600SDH backplane BITS clock pin fields to the timing source. For more information about wiring connections, refer to the CiscoONS15600SDH Procedure Guide.

Step 2 Ensure that the BITS clock is operating properly.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service-affecting problem.


2.5.79  LOS

Critical (CR), Service Affecting (SA)

A Loss of Signal alarm for either an STM-16 or STM-64 port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the ports, or no signal exists on the line. Possible causes for a loss of signal include upstream equipment failure or a fiber cut.

Troubleshoot by following the "Clear the LOF Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


2.5.80  LPBKCRS

Not Alarmed (NA), Service Affecting (SA)

The Loopback Cross-Connect condition indicates a software cross-connect loopback is active between a traffic (STM-N) card and a cross-connect card.

Loopback is a commonly used troubleshooting technique. A signal is sent out on a link or section of the network and returned to the sending device. If the signal does not return or returns with errors, the test confirms that the problem is present in the tested link. By setting up loopbacks on various parts of the node and excluding other parts, you can logically isolate the source of the problem. For more information on loopbacks, see the "Identify Points of Failure on a Circuit Path" procedure on page1-2.

Three types of loopbacks are available: Cross-Connect, Facility, and Payload. Cross-connect loopbacks troubleshoot STM-16 signals on CXC cards. Facility loopbacks troubleshoot STM-16 ports only and are generally performed locally or at the near end. Payload loopbacks troubleshoot STM-64 ports only and are generally performed locally or at the near end.

Clear the LBKCRS Condition


Step 1 To remove the loopback cross-connect condition, double-click the traffic (STM-N) card in node view.

Step 2 Click the Provisioning > AU4 tabs.

Step 3 In the XC Loopback column, deselect the check box for the port.

Step 4 Click Apply .

Step 5 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country in order to report a service-affecting problem.


2.5.81  LPBKFACILITY (STM-16)

Not Alarmed (NA), Non-Service Affecting (NSA)

A Facility Loopback Active condition occurs on STM-16 cards when a software facility loopback is active for a port on the reporting card, and the facility entity is out of service.


Caution Before performing a facility loopback on an STM-16 card, make sure the card contains at least two SDCC paths to the node where the card is installed. A second SDCC path provides a nonlooped path to log into the node after the loopback is applied, enabling you to remove the facility loopback. Ensuring a second SDCC is not necessary if you are directly connected to the ONS15600SDH containing the loopback STM-N.


Clear the LBKFACILITY Condition


Step 1 To remove the loopback facility condition, double-click the reporting card in node view.

Step 2 Click the Maintenance > Loopback tabs.

Step 3 In the Loopback Type column, click the correct row for the port and choose None from the drop-down menu.

Step 4 Click Apply .

Step 5 Click the Provisioning > Line tabs.

Step 6 In the Status column, click the correct row for the port and choose In Service from the drop-down menu.

Step 7 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.82  LPBKPAYLOAD (STM-64)

Not Alarmed (NA), Non-Service Affecting (NSA)

A Payload Loopback Active condition occurs on STM-64 cards when a software payload loopback is active for a port on the STM-64 card, and the facility entity is out of service.

Clear the LPBKPAYLOAD Condition


Step 1 To remove the loopback payload condition, double-click the reporting card in node view.

Step 2 Click the Maintenance > Loopback tabs.

Step 3 In the Loopback Type column, click the correct row for the port and choose None from the drop-down menu.

Step 4 Click Apply .

Step 5 Click the Provisioning > MS tabs.

Step 6 In the Status column, click the correct row for the port and choose In Service from the drop-down menu.

Step 7 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.83  MANSWTOINT

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Synchronization Switch to Internal Clock condition occurs when the NE (node) timing source is manually switched to the internal timing source.

2.5.84  MAN-REQ

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Switch Request Path condition occurs when a user initiates a Manual switch request for an SNCP circuit port.

Clear the MANREQ Condition


Step 1 Complete the "Clear a Force Switch on a SNCP Span" procedure on page3-7. This procedure also clears the Manual switch request.

Step 2 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.85  MANUAL-REQ-RING

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on two-fiber MS-SPRing rings to switch from working to protect or protect to working.

Clear the MANUAL-REQ-RING Condition


Step 1 Complete the "2.6.14Clear an MS-SPRing Span Lockout" procedure. This procedure also clears the Manual switch request.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.86  MANUAL-REQ-SPAN

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Switch Request on Span condition occurs when a user initiates a MANUAL SPAN command to move 1+1 traffic from a working span to a protect span.

Clear the MANUAL-REQ-SPAN Condition


Step 1 Complete the "Clear a Force Switch on a 1+1 Port" procedure on page3-7. This procedure also clears the Manual switch request.

Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.87  MANRESET

Not Alarmed (NA), Non-Service Affecting (NSA)

A Manual System Reset condition occurs when you right-click a TSC card, CXC card, or traffic (STM-N) card in CTC and choose Hard-reset Card or Soft-reset Card. Resets performed during a software upgrade also prompt the alarm. This condition clears automatically when the card finishes resetting.

2.5.88  MANSWTOPRI

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Synchronization Switch to Primary Reference condition occurs when the NE (node) timing source is manually switched to the primary source.

2.5.89  MANSWTOSEC

Not Alarmed (NA), Non-Service Affecting (NSA)

The Manual Synchronization Switch to Second Reference condition occurs when the NE (node) timing source is manually switched to the second source.

2.5.90  MATECLK

Minor (MN), Non-Service Affecting (NSA)

The Mate Clock alarm occurs when the active TSC cannot detect the clock from the standby TSC.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the MATECLK Alarm


Step 1 In CTC, check for any alarms that indicate that there are faulty clock references, such as the "HLDOVRSYNC" alarm on page2-43 or the "FRNGSYNC" alarm on page2-41, and resolve these alarms.

Step 2 If the MATECLK persists, complete the "2.6.15Remove and Replace a Card" procedure for the standby TSC and wait 15 minutes.

Step 3 If the MATECLK still persists, complete the "2.6.15Remove and Replace a Card" procedure for the active TSC, using the standby TSC to replace the active TSC.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more informationor log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service-affecting problem.


2.5.91  MEA

Critical (CR), Service Affecting (SA)

The Mismatch Between Equipment Type and Provisioned Attributes alarm is reported against a card slot when the physical TSC card, CXC card, STM-16, or STM-64 card in a slot does not match the card type provisioned for that slot in CTC. Deleting the incompatible card in CTC or physically removing the card clears the alarm.

Clear the MEA Alarm


Step 1 Physically verify the type of card that sits in the slot reporting the MEA alarm.

Step 2 In CTC, click the node view Inventory tab to reveal the provisioned card type.

Step 3 If you prefer the card type depicted by CTC, complete the "2.6.15Remove and Replace a Card" procedure for the reporting card and replace it with the card type depicted by CTC (provisioned for that slot).


Note CTC does not allow you to delete a card if at least one port on the card is in service, has a path mapped to it, is paired in a working-protection scheme, has DCC enabled, or is used as a timing reference.


Step 4 If you want to leave the installed card in the slot but it is not in service, delete any circuits mapped to it by following the "Clear the IMPROPRMVL Alarm" procedure.

Step 5 Place the cursor over the provisioned card in CTC and right-click to choose Delete Card .

When the card is deleted in CTC, the card that physically occupies the slot automatically reboots and appears in CTC.

Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service-affecting problem.


2.5.92  MFGMEM (CAP)

Minor (MN), Non-Service Affecting (NSA)

The Manufacturing Data Memory Failure CAP alarm occurs if the ONS15600SDH cannot access the data in the EEPROM on the CAP. MFGMEM is caused by EEPROM failure on the CAP, fuse failure for the EEPROM, or TSC card inability to read the MAC address from the CAP.

The EEPROM stores manufacturing data, including the MAC address, that is needed for compatibility and inventory issues. If the TSC card cannot read a valid MAC address, this disrupts IP connectivity and turns the ONS15600SDH icon in the CTC network view gray. If the alarm is accompanied by the "PWR-FA" alarm on page2-68 , the 5-VDC fuse for the EEPROM might be tripped. If that is the case, use the procedure below to eliminate the TSC card as the cause of the alarm, but do not attempt to troubleshoot it further. Log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


Tip You can reestablish the node management capability by disconnecting the Ethernet cable from the CAP and connecting it to the active TSC card LAN port.


Clear the MFGMEM Alarm on the CAP by Resetting the TSC Card


Step 1 Complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.

Wait for the "FSTSYNC" condition on page 2-42  to clear.

Step 2 If the alarm does not clear, complete the "2.6.8Hard-Reset the TSC Using CTC" procedure.

If the alarm does not clear, log on to http://www.cisco.com/tac f or more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.  The standby TSC card might also need replacement. If the alarm continues after both TSC cards have been replaced, the problem lies in the EEPROM on the CAP, and this must be replaced.

Step 3 When the alarm is cleared, you can make the standby TSC card active again by completing the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.


2.5.93  MFGMEM (CXC, Traffic Card, TSC)

Minor (MN), Non-Service Affecting (NSA)

The Manufacturing Data Memory Failure (CXC, Traffic Card, TSC) alarm occurs if the ONS15600SDH EEPROM on a CXC, STM-N, or TSC card fails.

Clear the MFGMEM Alarm on the CXC, TSC, or Traffic Card


Step 1 If the alarm is reported against a TSC card, troubleshoot with the "Clear the MFGMEM Alarm on the CAP by Resetting the TSC Card" procedure.

Step 2 If the reporting card is an active traffic line port in a 1+1 group or an SNCP, ensure that an APS traffic switch has occurred to move traffic to the protect port.

An SNCP APS is identified by an AUTOSW-type alarm or condition (such as AUTOSW-AIS, AUTOSW-LOP-SNCP, AUTOSW-PDI-SNCP, AUTOSW-SDBER-SNCP, AUTOSW-SFBER-SNCP, or AUTOSW-UNEQ-SNCP).

A 1+1 APS is identified on the node view Maintenance > Protection window. If you click the protection group, in the Selected Group list, the ports are designated as Working/Standby and Protect/Active.

Step 3 If the reporting port is part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page3-4. If the port is part of a 1+1 group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page3-4.

Step 4 If the reporting card is a CXC card and an automatic switch to the preferred copy CXC card occurred, traffic automatically switches to the alternate copy.

Step 5 Perform a CTC hard reset on the reporting card (or a soft reset on the CXC card):


Caution Use hard resets with caution. There can be up to 15 other sets of bandwidth affected by a hard reset. A forced hard reset of a CXC card will cause a service disruption.


a. Open the node view.

b. Position the CTC cursor over the card reporting the alarm.

c. Right-click and choose Hard-reset Card (or Soft-reset Card ) from the shortcut menu.

d. Click Yes in the Hard-reset Card (or Soft-reset Card) dialog box.

Step 6 If the CTC reset does not clear the alarm, remove and reinsert (reseat) the card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card into the slot along the guide rails.

d. Close the ejectors.

Step 7 If the physical reseat of the card does not clear the alarm, complete the "2.6.15Remove and Replace a Card" procedure.


Note If the traffic (STM-N) card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH Procedure Guide. Label the bad port, and place it out of service until the card can be replaced.


Step 8 If the MFGMEM alarm continues to report after you replaced the card, the problem lies in the EEPROM. Log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.

Step 9 If the alarm clears and it was reported by a traffic card, traffic reverts to the working port if an automatic switch occurred. If traffic was manually switched in a 1+1 protection group, revert traffic to the original port by completing the "Clear a Force Switch on a 1+1 Port" procedure on page3-7. If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page3-7.

If an automatic switch to the alternate copy CXC card occurred, traffic is automatically restored to the preferred copy.

Step 10 If the reporting card is a TSC card and you want to make the standby TSC card active again, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.


2.5.94  MFGMEM (FAN)

Critical (CR), Service Affecting (SA)

The Manufacturing Data Memory Fan alarm occurs if the ONS15600SDH EEPROM on a fan tray fails. MFGMEM can be accompanied by the "FAN-FAIL" alarm on page2-36.

Clear the MFGMEM (FAN) Alarm


Step 1 Pull out the fan tray.

Step 2 Reinsert the fan tray, making sure you can hear the fans start operating. Fans should run immediately when correctly inserted.

Step 3 If a fan does not run or the alarm persists, complete the "Replace a Fan Tray" procedure on page3-11.

Step 4 If a replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information or to report a service-affecting problem.


2.5.95  MS-AIS

Not Reported (NR), Non-Service Affecting (NSA)

The Multiplex Section AIS condition indicates that there is a defect in the multiplexing section layer of the SDH overhead. The line layer refers to the segment between two SDH devices in the circuit and is also known as a maintenance span. The line layer deals with SDH payload transport, and its functions include multiplexing and synchronization.

Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.


Note DS-3 facility and terminal loopbacks do not transmit DS-3 MS-AIS in the direction away from the loopback. Instead of DS-3 MS-AIS, a continuance of the signal transmitted to the loopback is provided.


Clear the MS-AIS Condition


Step 1 Complete the "Clear the AIS Condition" procedure.

Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.96  MS-DEG

Not Alarmed (NA), Non-Service Affecting (NSA)

A Multiplex Section-Signal Degrade Line condition occurs for an optical port that detects a signal degrade condition. Signal degrade is defined by Telcordia as a "soft failure" condition. MS-DEG and the "MS-EXC" condition on page2-64 monitor the incoming bit error rate (BER) and are similar alarms. SD is triggered at a lower BER than SF. The BER threshold on the ONS15600SDH is user provisionable and has a range for SD from 10-9 to 10-5.

MS-DEG causes a switch from the working card to the protect card at the line (facility) level. A line- or facility-level SD alarm travels on the B2 byte of the SDH overhead. The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered the alarm. A BER increase is sometimes caused by a physical fiber problem, including a faulty or incorrectly plugged fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the MS-DEG Condition


Step 1 Verify that the user-provisionable BER threshold is set at the expected level:

a. From the node view, double-click the card reporting the alarm to open the card view.

b. Click the Provisioning > MS tabs.

c. Under the SD BER column on the Provisioning window, verify that the cell entry is consistent with what the system was originally provisioned for. The default setting is 1E-7.

d. If the entry is consistent with what the system was originally provisioned for, continue with Step 2 .

e. If the entry is not consistent the original provisioning, click the cell to reveal a drop-down menu of choices and choose the entry consistent with the original provisioning.

f. Click Apply .

Step 2 Ensure that the fiber connector for the card is completely plugged in. For more information about fiber connections and card insertion, refer to the CiscoONS15600SDH Procedure Guide.

Step 3 Use an optical test set to measure the power level of the line to ensure that it is within guidelines. Refer to the CiscoONS15600SDH Procedure Guide for circuit test procedures.

Step 4 Verify that optical receive levels are within the acceptable range.

Step 5 Clean the fiber connectors at both ends:

a. Clean the fiber connectors according to local site practice.

b. If no local practice exists, use a Cletop Real-Type, 3M OGI connector cleaner, or equivalent fiber-optic cleaner and follow the instructions accompanying the product and/or consult the procedures in the Cisco ONS 15600 SDH Procedure Guide.

Step 6 Clean the optical transmitter and receiver by following site practice.

Step 7 Verify that a single-mode laser is used at the far end.

Step 8 If the problem persists, complete the "2.6.15Remove and Replace a Card" procedure on the transmitter card at the other end of the optical line.


Note If the traffic card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH Procedure Guide. Label the bad port, and place it out of service until the card can be replaced.



2.5.97  MS-EXC

Not Alarmed (NA), Non-Service Affecting (NSA)

A Multiple Section-Signal Fail condition occurs when the quality of the signal on STM-16 and STM-64 cards causes the BER on the incoming optical line to exceed the SF threshold. Signal failure is defined by Telcordia as a "hard failure" condition. MS-DEG and MS-EXC both monitor the incoming BER error rate and are similar alarms, but SF is triggered at a higher BER than SD. The default value of NA is determined by TelcordiaGR-253-CORE. The BER threshold on the ONS15600SDH is user provisionable and has a range for SF from 10-5 to 10-3.

MS-EXC causes a switch from the working port to the protect port at the line (facility) level. A line or facility level SF alarm travels on the B2 byte of the SDH overhead. The SF alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice. Troubleshoot with the "Clear the MS-DEG Condition" procedure.

2.5.98  MS-RDI

Minor (MN), Minor (MN)

The Multiplex Section (MS) Remote Defect Indication (RDI) condition indicates that there is an RDI occurring at the SDH overhead multiplexing section level.

An RDI occurs when the ONS 15600 SDH detects an RDI in the SDH overhead because of a fault in another node. Resolving the fault in the adjoining node clears the MS-RDI condition in the reporting node.

Clear the MS-RDI Condition


Step 1 Log into the far-end node of the reporting ONS 15600 SDH.

Step 2 Verify whether there are other alarms, especially the "2.5.79LOS" procedure.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for the procedure.

Step 4 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.5.99  MSSP-OOSYNC

Major (MJ), Service-Affecting (SA)

The MS-SPRing Out Of Synchronization alarm occurs when a node on a working ring loses its DCC connection. CTC cannot generate the ring table and raises the MSSPR-OSYNC alarm.

Clear the MSSP-OOSYNC Alarm


Step 1 Verify cabling continuity to the node reporting the alarm.

When the DCC is established between the node and the MS-SPRing, it becomes visible to the MS-SPRing and should be able to function on the circuits.

Step 2 If alarms occur when you provisioned the DCCs, see the "EOC" alarm on page2-28.

Step 3 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.100  OPEN-SLOT

Major (MJ), Non-Service Affecting (NSA)

One of the input/output (I/O) slots (Slots 1 through 4 and 11 through 14) does not contain a traffic card or filler card.

Clear the OPEN-SLOT Alarm


Step 1 Insert a filler card or STM-N card into the empty slot.

Step 2 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.101  PDI-P

Not Alarmed (NA), Non-Service Affecting (NSA)

A Payload Defect Indication Path condition indicates a signal label mismatch failure (SLMF) in the VC4 signal. An invalid C2 byte in the SDH path overhead causes an SLMF. The C2 byte is the signal-label byte. This byte tells the equipment what the SDH payload envelope contains and how it is constructed. It enables a SDH device to transport multiple types of services.

The ONS15600SDH encounters an SLMF when the payload, such as an ATM, does not match what the signal label is reporting. The "AU-AIS" condition on page2-14 often accompanies the PDI-P alarm. If the PDI-P is the only alarm reported with the AIS-P, clear the PDI-P alarm to clear the AIS-P alarm. PDI-P can also occur during an upgrade, but usually clears itself and is not a valid alarm.


Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector.
Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the PDI-P Condition


Step 1 Check the incoming signal overhead with an optical test to verify that the C2 byte is correct; refer to the Cisco ONS15600SDH Procedure Guide for circuit test procedures.

Step 2 If the C2 byte is not correct, it indicates an upstream equipment problem (typically with path-terminating equipment). Troubleshoot the upstream equipment.

Step 3 If the condition does not clear, complete the "2.6.15Remove and Replace a Card" procedure for the reporting card.


Note If the traffic (STM-N) card is implicated and you are able to continue using the traffic card with one port out of service, perform a bridge and roll to move the port traffic to a free port using the "Bridge and Roll Traffic" procedure in the CiscoONS15600SDH Procedure Guide. Label the bad port, and place it out of service until the card can be replaced.


Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.102  PRC-DUPID

Major (MJ), Service-Affecting (SA) for Ring

Major (MJ), Non-Service Affecting (NSA) for NE

The Procedural Error Duplicate Node ID alarm indicates that two identical node IDs exist in the same ring. The ONS15600SDH requires each node in the ring to have a unique node ID.

Clear the PRC-DUPID Alarm


Step 1 Log into a node on the ring.

Step 2 Find the node ID by completing the "2.6.1Identify a Ring ID or Node ID Number" procedure.

Step3 Repeat Step 2 for all the nodes on the ring.

Step 4 If two nodes have an identical node ID number, complete the "2.6.4Change a Node ID Number" procedure so that each node ID is unique.

Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.103  PWR-A

Minor (MN), Non-Service Affecting (NSA)

The NE Power Failure at Input A alarm applies to the shelf. PWR-A occurs when no power is supplied to the main power distribution unit (PDU). This alarm can be raised if power is connected to the backup PDU but not to the main one because power must be available to both units.


Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment.


Clear the PWR-A Alarm


Step 1 Verify that both PDU A-side circuit breakers are turned on.

Step 2 Determine whether a power connection between the office power connector and the PDU is present.

Step 3 If the alarm cannot be cleared, verify the continuity of the power connection with a voltmeter using the procedures in the Cisco ONS 15600 SDH Procedure Guide..

Step 4 If the alarm does not clear and if cable continuity is present, remove and reattach (reseat) the cable ends between the office power connector and the PDU.

Step 5 If the alarm does not clear, physically replace the power cable.

Step 6 If the alarm cannot be cleared, physically replace the PDU using the "Remove a Power Distribution Unit" procedure on page3-14.

Step 7 If replacement does not clear the alarm, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country to report a service-affecting problem.


2.5.104  PWR-B

Minor (MN), Service Affecting (SA)

The NE Power Failure at Input B alarm applies to the NE (node) shelf. It occurs when no power is supplied to the second PDU. This alarm can be raised if power is connected to the main PDU but not to the backup, since power must be available to both units.

Troubleshoot with the "Clear the PWR-A Alarm" procedure . If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment.


2.5.105  PWR-FA

Minor (MN), Non-Service Affecting (NSA)

The Backplane Power Fuse Failure alarm indicates that the backplane EEPROM memory 5-VDC fuse fails, but the equipment is still in service. Service is not currently affected, but network management can be affected because the ONS15600SDH system uses a default NE (node) IP address instead of a programmed one in this case. This alarm might be accompanied by the "INVMACADR" alarm on page2-49, which appears in the alarm history when network management capability is restored.

Do not attempt to troubleshoot the alarm. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

2.5.106  PWR-FAIL-A

Major (MJ), Non-Service Affecting (NSA)

The Equipment Power Failure at Connector A alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the CAP, a CXC card, a traffic (STM-N) card, or a TSC card.


Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment.


Clear the PWR-FAIL-A Alarm


Step 1 If the "PWR-A" alarm on page2-67 or the "PWR-B" alarm on page2-67 also occurs, troubleshoot it by completing the "Clear the PWR-A Alarm" procedure.

If a PWR-A occurs in addition to PWR-FAIL-A, PWR-A usually clears the lower-hierarchy PWR-FAIL-A alarm. If you clear the PWR-A alarm and the PWR-FAIL-A alarm still remains, continue following this procedure.

Step 2 If a single card has reported the alarm, take the following actions depending what kind of card reported it:

If the reporting card has an active traffic line port in a 1+1 protection scheme or is part of an SNCP, ensure that an APS traffic switch has occurred to move traffic to the protect port.

An SNCP APS is identified by an AUTOSW-type alarm or condition (such as AUTOSW-AIS, AUTOSW-LOP-SNCP, AUTOSW-PDI-SNCP, AUTOSW-SDBER-SNCP, AUTOSW-SFBER-SNCP, or AUTOSW-UNEQ-SNCP).

A 1+1 APS is identified on the node view Maintenance > Protection window. If you click the protection group, in the Selected Group list, the ports are designated as Working/Standby and Protect/Active.

If the reporting port is part of an SNCP, complete the "Switch all SNCP Circuits on a Span" procedure on page 3-4 . If the port is part of a 1+1 group, complete the "Initiate a Force Switch on a 1+1 Port" procedure on page 3-4 . Continue with Step 4 .

If an automatic switch to the alternate copy CXC card occurred, the CXC card can be serviced. If the switch has not occurred, complete the "2.6.6  Request a Cross-Connect Card Preferred Copy Switch" procedure . Continue with Step 4 .

To determine which CXC card is the preferred copy and if it is currently being used, open the node view Maintenance > Preferred Copy window. The Data Copy area Preferred field shows Copy A or Copy B. The Currently Used field shows the copy being used.


Note In CTC, CopyA refers to the CXC card in Slot 6/7. CopyB refers to the CXC card in Slot8/9. Either copy can be chosen as the preferred copy CXC card. The other CXC card is called the alternate CXC card in this chapter.


Step 3 If the alarm is reported against a TSC card, complete the "2.6.8Hard-Reset the TSC Using CTC" procedure.

Step 4 If the alarm is reported against a traffic (STM-N) card or CXC card, perform a hard reset (or soft reset on the CXC card):


Caution Use hard resets with caution. There can be up to 15 other sets of bandwidth affected by a hard reset. A forced hard reset of a CXC card will cause a service disruption.

Note Whenever TSC cards are changed from active to standby, it takes approximately 12 minutes to completely synchronize to the timing source because the Stratum 3E timing module is being adopted.


a. Position the cursor over the active card.

b. Right-click and choose Hard-reset Card (or Soft-reset Card ) from the shortcut menu.

c. Click Yes in the Hard-reset Card (or Soft-reset Card) dialog box.

Step 5 If the alarm does not clear, remove and reinsert (reseat) the reporting card:

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Check the pins one the backplane connector, including the power pins on the edge of the card. Also inspect the pins on the backplane as well. A bent pin can cause power failure.


Caution If a backplane pin is bent, do not insert another card in the slot until the problem is remedied.

d. Slide the card into the slot along the guide rails.

e. Close the ejectors.

Step 6 If the alarm does not clear, complete the "2.6.15Remove and Replace a Card" procedure for the reporting card.

Step 7 If the single card reseat and replacement does not clear the alarm, or if multiple cards report the alarm, verify the office power; refer to the CiscoONS15600SDH Procedure Guide for instructions.

Step 8 If the alarm does not clear, reseat the power cable connection to the connector. For more information about ONS15600SDH power connections, refer to the CiscoONS15600SDH Procedure Guide.

Step 9 If the alarm does not clear, physically replace the power cable connection to the connector.

Step 10 If the alarm does not clear, a problem with the PDU is indicated. Complete the "Remove a Power Distribution Unit" procedure on page3-14.

Step 11 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.

Step 12 If the alarm clears and it was reported by a traffic (STM-N) card, traffic reverts to the working port if an automatic switch occurred. If traffic was manually switched to a 1+1 protection port, revert traffic by completing the "Clear a Force Switch on a 1+1 Port" procedure on page3-7. If traffic was manually switched in an SNCP, revert traffic to the original path by completing the "Clear a Force Switch on a SNCP Span" procedure on page3-7.

Step 13 If the alarm was reported by a CXC card and an automatic switch to the alternate copy CXC card occurred, traffic is automatically restored to the preferred copy.

Step 14 If the reporting card was reported by a TSC card and you want to make the standby card active, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.


2.5.107  PWR-FAIL-B

Major (MJ), Non-Service Affecting (NSA)

The Equipment Power Failure at Connector B alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the CAP, a CXC card, a traffic (STM-N) card, or a TSC card.

Troubleshoot this alarm with the "Clear the PWR-FAIL-A Alarm" procedure.

2.5.108  PWR-FAIL-RET-A

Minor (MN), Non-Service Affecting (NSA)

The Equipment Power Failure at Power Return A alarm occurs when the main power return path is not available. This alarm occurs on the CAP, a CXC card, a traffic (STM-N) card, or a TSC card. Troubleshoot using the "Clear the PWR-FAIL-A Alarm" procedure.

2.5.109  PWR-FAIL-RET-B

Minor (MN), Non-Service Affecting (NSA)

The Equipment Power Failure at Power Return B alarm occurs when the main power return path is not available. This alarm occurs on the CAP, a CXC card, a traffic (STM-N) card, or a TSC card. Troubleshoot using the "Clear the PWR-FAIL-A Alarm" procedure.

2.5.110  PWRRESTART

Not Alarmed (NA), Non-Service Affecting (NSA)

The Power-Up Restart condition occurs when the shelf is restarted while no CTC connection is present. The Slot 5 TSC card on the shelf does not report this condition because the card is inactive when the condition occurs. You can see this condition in the Alarm History window when the CTC connection resumes.

2.5.111  RING-MISMATCH

Major (MJ), Service Affecting (SA)

At least one node in the ring has an incorrect node ID. The RING-MISMATCH alarm clears when all nodes in the ring have the correct node IDs.

Clear the RING-MISMATCH Alarm


Step 1 Complete the "2.6.1Identify a Ring ID or Node ID Number" procedure to verify each node's ID number.

Step 2 Repeat Step 1 for all nodes in the ring.

Step 3 If one node has an incorrect node ID number, complete the "2.6.4Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.112  RING-SW-EAST

Not Alarmed (NA), Non-Service Affecting (NSA)

The Ring Switch Is Active East Side condition accompanies a ring switch at the east side of a two-fiber MS-SPRing. The condition clears when the switch is cleared.

2.5.113  RING-SW-WEST

Not Alarmed (NA), Non-Service Affecting (NSA)

The Ring Switch Is Active West Side condition occurs when a ring switch occurs at the west side of a two-fiber MS-SPRing. The condition clears when the switch is cleared.

2.5.114  ROLL

Not Alarmed (NA), Non-Service Affecting (NSA)

A Bridge and Roll Active condition occurs when a valid VC4 signal is detected after the bridge and roll command is issued. The ROLL condition clears when the bridge and roll command is complete or canceled.

2.5.115  ROLL-PEND

Not Alarmed (NA), Non-Service Affecting (NSA)

A Bridge and Roll Pending Completion condition occurs when the bridge and roll command is issued for a VC4 signal. This condition applies to the interval when bridge is set and waiting for the valid signal to be certified. The condition is cleared when the valid signal is detected for automatic and manual bridge and roll, or when the bridge and roll command is canceled for a manual bridge and roll. The command cannot be completed if this condition remains standing.


Note Roll and Roll-Pend alarms are not cleared when the port is in OOS.


2.5.116  RS-TIM

Critical (CR), Non-Service Affecting (NSA)

The Regeneration Section Trace Identifier Mismatch alarm occurs when the current expected section trace (J0) trace string does not match the current received section trace string. Section Trace Mode must be set to MANUAL/MANUAL_NO_AIS for this alarm to occur.

In the MANUAL/MANUAL_NO_AIS mode in the Section Trace area (TL1 command), the user can type a new expected string into the field. This string must match the string typed into the Current Received String field for the sending port. If these fields do not match, it is typically because of upstream path terminating equipment error.

Clear the RS-TIM Alarm


Step 1 Log into TL1 session with ACT-USER command.

Step 2 With RTRV-TRC-STM16/64 TL1 command, against the facility reporting the alarm, verify current string and its value is different from expected one.

Step 3 Be sure that two ports of the I/O boards connected by optical fiber are exactly what you want to connected.

Step 4 With ED-TRC-STM16/64 command set the port expected section trace with the correct string. Alternatively, you can set the sent section trace of the other facility with the expected one by running the above command against the facility.

Step 5 Verify RS-TIM alarm is cleared

Step 6 Log off from TL1 session.

Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.5.117  SECUR-THRESHOLD

Not Alarmed (NA), Non-Service Affecting (NSA)

The Invalid Login Attempt Threshold Exceeded condition occurs when a user attempts to log into the NE (node) with an invalid ID or password more times than the threshold allowed. The condition can be remedied by waiting approximately 15 seconds before logging in again, or by restarting the CTC or TL1 session.

2.5.118  SFTWDOWN

Not Alarmed (NA), Non-Service Affecting (NSA)

A Software Download in Progress condition occurs when a TSC card is downloading or transferring software. No action is necessary. Wait for the transfer or the software download to complete.


Note It takes approximately 20 minutes for the active TSC card to transfer the system software to the newly installed TSC card. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.



Note If the active and standby TSC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby TSC card.


2.5.119  SNTP-HOST

Minor (MN), Non-Service Affecting (NSA)

The Simple Network Timing Protocol (SNTP) Host Failure alarm indicates that an ONS node serving as an IP proxy for the other ONS nodes in the ring is not forwarding SNTP information to the other ONS nodes in the network. The forwarding failure can result from two causes, either the IP network attached to the ONS proxy node is experiencing problems, or the ONS proxy node itself is not functioning properly.

Clear the SNTP-HOST Alarm


Step 1 Ping the SNTP host from a workstation in the same subnet to ensure that communication is possible within the subnet.

Step 2 If the ping fails, contact the network administrator who manages the IP network that supplies the SNTP information to the proxy and determine whether the network is experiencing problems which might affect the SNTP server/router connecting to the proxy ONS15600SDH.

Step 3 If no network problems exist, ensure that the ONS15600SDH proxy is provisioned correctly:

a. In node view for the ONS node serving as the proxy, click the Provisioning > General tabs.

b. Ensure that the Use NTP/SNTP Server check box is checked.

c. If the Use NTP/SNTP Server check box is not checked, check it.

d. Ensure that the Use NTP/SNTP Server field contains a valid IP address for the server.

Step 4 If proxy is correctly provisioned, refer to the CiscoONS15600SDH Reference Manual for more information about SNTP hosts.

Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.120  SQUELCH

Not Alarmed (NA), Non-Service Affecting (NSA)

The Ring Squelching Traffic condition occurs in an MS-SPRing when a node that originates or terminates VC4 circuits fails or is isolated by multiple fiber cuts or maintenance FORCE RING commands. The isolation or failure of the node disables circuits that originate or terminate on the failed node. Squelch alarms appear on one or both of the nodes on either side of the isolated/failed node. The "AU-AIS" condition on page2-14 also appears on all nodes in the ring except the isolated node.


Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.



Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Clear the SQUELCH Condition


Step 1 Determine the isolated node:

a. In the node view, click View > Go to Network View .

b. The gray node with red spans is the isolated node.

Step 2 Verify fiber continuity to the ports on the isolated node.

Step 3 If fiber continuity is okay, verify that the proper ports are in service:

a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.

A green LED indicates an active card. An amber LED indicates a standby card.

b. To determine whether the STM-N port is in service, double-click the card in CTC to open the card view.

c. Click the Provisioning > MS tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS . Click Apply .

Step 4 If the correct ports are in service, use an optical test set to verify that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

Step 5 If the signal is valid, verify that the power level of the optical signal is within the optical (traffic) card's receiver specifications. Refer to the CiscoONS15600SDH Reference Manual for card specifications.

Step 6 If the receiver levels are okay, ensure that the optical transmit and receive fibers are connected properly.

Step 7 If the connectors are okay, complete the "2.6.15Remove and Replace a Card" procedure for the STM-N card.

Step 8 If the condition does not clear, log onto http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.121  SSM-DUS

Not Alarmed (NA), Non-Service Affecting (NSA)

The Synchronization Status Messaging (SSM) Changed to Do Not Use (DUS) condition occurs when the synchronization status message quality level changes to DUS.

The port that reports the condition is not at fault. The condition applies to the timing source. SSM-DUS prevents timing loops by providing a termination point for the signal usage.

2.5.122  SSM-FAIL

Major (MJ), Service Affecting (SA)

Minor (MN), Non-Service Affecting (NSA)

The SSM Failed to Receive Synchronization alarm occurs when SSM received by the ONS15600SDH fails. The problem is external to ONS15600SDH. If one of two sources fails, the alarm is minor. If there is no backup source, the alarm is major. The ONS15600SDH is set up to receive SSM, but the timing source is not delivering valid SSM messages.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

Clear the SSM-FAIL Alarm


Step 1 Verify that SSM is enabled on the external timing source.

Step 2 Use an optical test set to determine that the external timing source is delivering SSM; refer to the CiscoONS15600SDH Procedure Guide for circuit test procedures.


2.5.123  SSM-OFF

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Changed to Off condition occurs when SSM is disabled by a user.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops. Troubleshoot with the "Clear the SSM-FAIL Alarm" procedure if desired.

2.5.124  SSM-PRC

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to PRC (Primary Reference Clock) condition occurs when the SSM transmission level changes to Stratum 1 Traceable.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.125  SSM-RES

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to Reserved (RES) condition occurs when the synchronization message quality level changes to RES.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.126  SSM-SEC

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to PRC condition occurs when SSM transmission level changes to a timing quality generated by an SDH Equipment Clock (SEC) that is defined in Recommendation G.813, Option I.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.127  SSM-SMC

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to SDH Minimum Clock Traceable (SMC) condition occurs when the synchronization message quality level changes to SMC.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.128  SSM-SSUA

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to PRC condition occurs when SSM transmission level changes to a timing quality generated by Types V or I slave clock that is defined in Recommendation G.812.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.129  SSM-SSUB

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to PRC condition occurs when SSM transmission level changes to a timing quality generated by Types IV slave clock that is defined in Recommendation G.812.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.130  SSM-STU

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Synchronization Traceability Unknown condition occurs when the reporting node is timed to a reference that does not support SSM, but the ONS15600SDH has SSM support enabled. STU can also be raised if the timing source is sending out SSM messages but SSM is not enabled on the ONS15600SDH.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. SSM enables SDH devices to automatically choose the highest quality timing reference and to avoid timing loops.

Clear the SSM-STU Condition


Step 1 Click the node view Provisioning > Timing tabs.

Step 2 If the Sync Messaging check box is checked, click the box to deselect it.

Step 3 If the Sync Messaging check box is unchecked, click the box to select it.

Step 4 Click Apply .


2.5.131  SSM-TNC

Not Alarmed (NA), Non-Service Affecting (NSA)

The SSM Quality Level Changed to Transit Node Clock Traceable (TNC) condition occurs when the synchronization message quality level changes to TNC.

SSM communicates information about the quality of the timing source. SSM is carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

2.5.132  SWTOPRI

Not Alarmed (NA), Non-Service Affecting (NSA)

The Synchronization Switched to Primary Reference condition occurs when the ONS15600SDH switches to the primary timing source (reference 1). The ONS15600SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.

2.5.133  SWTOSEC

Not Alarmed (NA), Non-Service Affecting (NSA)

The Synchronization Switched to Second Reference condition occurs when the ONS15600SDH has switched to the second timing source (reference 2). The ONS15600SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. To clear the SWTOSEC condition, complete the "Clear the SYNCPRI Alarm" procedure.

2.5.134  SWTOTHIRD

Not Alarmed (NA), Non-Service Affecting (NSA)

The Synchronization Switched to Third Reference condition occurs when the ONS15600SDH has switched to the third timing source (reference 3). The ONS15600SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. To clear the SWTOTHIRD condition, complete the "Clear the SYNCPRI Alarm" procedure.

2.5.135  SWVER

Not Alarmed (NA), Non-Service Affecting (NSA)

The Software Version condition is reported when a new software version is activated on the ONS15600SDH. When a new version of software is uploaded, it results in the active TSC card running the new version and the standby TSC card running the old version. This situation raises the SW-VER condition. It remains until the user accepts the new version in the CTC. The acceptance causes the standby TSC card to reboot and upload the new version.

If the user does not accept the version, the active TSC card switches to the standby TSC card with the original version. After the switch, the new standby TSC card reverts to the previous version.

2.5.136  SYNCCLK

Critical (CR), Service Affecting (SA)

A Synchronization Clock Unavailable alarm occurs when both TSC cards lose their timing function.

Clear the SYNCCLK Alarm


Step 1 From the node view, click the Provisioning > Timing tabs.

Step 2 Check the current configuration for the Ref-1 of the NE Reference.

Step 3 If the primary reference is a BITS input, complete the "Clear the LOF Alarm" procedure.

Step 4 If the primary reference clock is an incoming port on the ONS15600SDH, complete the "Clear the LOF Alarm" procedure.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.137  SYNC-FREQ

Major (MJ), Service Affecting (SA)

The Synchronization Reference Frequency Out of Bounds alarm occurs when the synchronization frequency reference for the NE (node) is not within acceptable boundaries.

Clear the SYNC-FREQ Alarm


Step 1 Verify that the internal or BITS timing reference is stable. The timing reference is located on the active TSC card. Check for any alarms against this card and troubleshoot them.

Step 2 If the alarm does not clear, complete the "2.6.7Soft-Reset the TSC Card Using CTC" procedure.

Step 3 If the alarm clears, complete the "2.6.15Remove and Replace a Card" procedure to replace the TSC card with a new TSC card.


Note It takes approximately 20 minutes for the active TSC card to transfer the system software to the newly installed TSC card. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.



Note If the active and standby TSC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby TSC card.


Step 4 If the SYNC-FREQ alarm continues to report after replacing the TSC card, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.138  SYNCPRI

Minor (MN), Non-Service Affecting (NSA)

A Primary Synchronization Reference Failure alarm occurs at the NE (node) level when the ONS15600SDH loses the primary timing source (reference 1). The ONS15600SDH uses three ranking timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the ONS15600SDH should switch to its second timing source (reference 2). This switch also triggers the SWTOSEC alarm.

Clear the SYNCPRI Alarm


Step 1 From the node view, click the Provisioning > Timing tabs and identify the timing source in Ref-1 of the NE Reference.

Step 2 If the Ref-1 is Internal, this refers to the active TSC card. Look for any alarms related to the TSC card and troubleshoot them.

Step 3 If the Ref-1 is BITS, follow the "Clear the LOF (BITS) Alarm" procedure.

Step 4 If the primary reference clock is an incoming port on the ONS15600SDH, follow the "Clear the LOF Alarm" procedure.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.139  SYNCSEC

Minor (MN), Non-Service Affecting (NSA)

A Second Synchronization Reference Failure Alarm occurs at the NE (node) level when the ONS15600SDH loses the second timing source (reference 2). The ONS15600SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCSEC occurs, the ONS15600SDH should switch to the third timing source (reference 3) to obtain valid timing for the ONS15600SDH. This switch also triggers the "SWTOTHIRD" condition on page2-78.

Clear the SYNCSEC Alarm


Step 1 From the node view, click the Provisioning > Timing tabs.

Step 2 Check the current configuration of the REF-2 for the NE Reference.

Step 3 If the second reference is a BITS input, follow the "Clear the LOS (BITS) Alarm" procedure.

Step 4 If the second timing source is an incoming port on the ONS15600SDH, follow the "Clear the LOF Alarm" procedure.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of CiscoTAC toll-free numbers for your country.


2.5.140  SYSBOOT

Minor (MN), Non-Service Affecting (NSA)

The System Reboot alarm indicates that new software is booting on the node or shelf TSC card. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes approximately three minutes.

2.5.141  T-OPR-High/Low

Not Alarmed (NA), Non-Service Affecting (NSA)

T-OPR-High and T-OPR-Low are threshold crossings that occur when optical power received (OPR) falls below the OPR-Low value or above the OPR-High value that was determined when the OPR normalized level was last set.

Clear the T-OPR High/Low Threshold Crossing


Step 1 In CTC, open the card view for the card/port that is reporting T-OPR and click the Maintenance > Transceiver tabs.

Step 2 If the OPR value is within acceptable limits for the card (refer to the CiscoONS15600SDH Reference Manual for card receiver specifications), recalibrate the OPR value by completing the "2.6.16Set the Optical Power Received Nominal Value" procedure.

Step 3 If the OPR value is below the minimum receive power level, check the far end transmitter for failure and look for damaged or dirty fiber-optic cables. Repair as necessary and complete the "2.6.16Set the Optical Power Received Nominal Value" procedure.

Step 4 If the OPR value is above the maximum receive power level, new equipment might have been added and is transmitting at a higher power level. Attenuate as necessary and complete the "2.6.16Set the Optical Power Received Nominal Value" procedure.

Step 5 If the threshold crossing is not resolved, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.142  UNEQ-P

Critical (CR), Service Affecting (SA)

An Unequipped Path Signal Label Mismatch Failure alarm occurs when the path does not have a valid sender. The indicator is carried in the C2 signal path byte in the SDH overhead. The source of the problem is the node that is transmitting the signal into the node reporting the UNEQ-P.

UNEQ-P occurs in the node that terminates a path. The path layer is the segment between the originating equipment and the terminating equipment. This segment can encompass several consecutive line segments.

An UNEQ-P error message on the ONS15600SDH indicates that the node reporting the "HP-RDI" condition on page2-44 is the terminating node on that path segment.


Note If you have created a new path but it has no signal, an UNEQ-P alarm is reported on the traffic (STM-N) cards and an AIS-P alarm is reported on the terminating cards. These alarms clear when the path carries a signal.



Caution Always use the supplied ESD wristband when working with a powered ONS15600SDH. Plug the wristband cable into the ESD jack located on the lower-left outside edge of the shelf assembly.


Clear the UNEQ-P Alarm


Step 1 Open the node view and navigate to the Circuits > Circuits tabs.

Step 2 In the State column, check for any circuit that has the status INCOMPLETE. (A completed circuit has ACTIVE status.)


Note Circuits have an incomplete status while they are in the process of being routed on the system. If you have created a large number of circuits, this status can remain for several minutes before it changes to active.


Step 3 If the alarm remains for some time and the circuit does not clear the alarm, delete the circuit:

a. Click the incomplete circuit to highlight it.

b. Click Delete .

Step 4 Recreate the circuit as necessary; refer to the CiscoONS15600SDH Procedure Guide for instructions.

Step 5 If the alarm does not clear after re-creation, ensure that the circuit continues to pass traffic using an optical test set; refer to the CiscoONS15600SDH Procedure Guide for circuit test procedures.

Step 6 If the alarm does not clear, verify that the incoming signal is valid by testing with an optical test set.

Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.143  UNPROT-SYNCCLK

Minor (MN), Non-Service Affecting (NSA)

The Unprotected Synchronization or Clock Equipment alarm indicates that only one TSC card has acquired the primary timing reference. The alarm is reported if there is no standby TSC card, or if the standby TSC card has restarted and 700 seconds (in FSTSYNC mode) have not elapsed.

This condition is normal following a change to the system timing reference (BITS to Line, Line to BITS). Changing the clock reference causes both TSC cards to raise the "FSTSYNC" condition on page2-42 for 700 seconds. The UNPROT-SYNCCLK alarm occurs during this period. If both TSC cards are reset within 700 seconds of each other, this alarm occurs also and remains until both TSC cards attain the clock reference. If the alarm does not clear, follow the "Clear the UNPROT-SYNCCLK Alarm" procedure.

Clear the UNPROT-SYNCCLK Alarm


Step 1 Determine whether one or both TSC cards have the "FSTSYNC" condition on page2-42 raised. If either TSC card has a FSTSYNC condition, wait 700 seconds for the condition and the UNPROT-SYNCCLK alarm to clear.

Step 2 If FSTSYNC was reported and continues after 700 seconds, replace the standby TSC card. Continue with Step 7.

Step 3 If FSTSYNC is not reported, from the node view, click the Provisioning > Timing tabs.

Step 4 Verify the current configuration for the Ref-1 of the NE Reference.

If the primary reference clock is an incoming port on the ONS 15600 SDH, follow the "Clear the LOF Alarm" procedure .

Step 5 If no protect TSC card is installed, install one. Refer to the "Install the Common Control Cards" procedure in the CiscoONS15600SDH Procedure Guide.

Step 6 If the alarm persists, remove and reinsert (reseat) the standby TSC card and wait 700 seconds for the TSC card to acquire the reference.

a. Open the card ejectors.

b. Slide the card out of the slot.

c. Slide the card into the slot along the guide rails.

d. Close the ejectors.

Step 7 If the alarm reappears after you perform the switch, complete the "2.6.10Reset the TSC Card with a Card Pull" procedure on the standby TSC card and wait 700 seconds for the TSC card to acquire the reference.


Note It takes approximately 20 minutes for the active TSC card to transfer the system software to the newly installed TSC card. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the TSC card reboots and goes into standby mode after approximately three minutes.



Note If the active and standby TSC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby TSC card.



2.5.144  UNPROT-XCMTX

Minor (MN), Non-Service Affecting (NSA)

The Unprotected Cross-Connection Matrix Equipment alarm indicates that only one functional CXC card on the node supports the cross-connection. The alarm clears if the redundant CXC card is installed. This alarm could be accompanied by the "2.5.67IMPROPRMVL (CXC, Traffic Card, TSC)" procedure or the "EQPT (CXC, Traffic Card, TSC)" alarm on page2-29.

Clear the UNPROT-XCMTX Alarm


Step 1 If there is no protect CXC card installed, install one.

Allow the newly installed CXC card to boot.

Step 2 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.


2.5.145  UPGRADE

Not Alarmed (NA), Non-Service Affecting (NSA)

The System Upgrade in Progress condition indicates that a system upgrade is occurring on the TSC card.

When software is downloaded, it is loaded into the available code volume on the active TSC card. The software is copied to the available code volume on the standby TSC card next. The "SFTWDOWN" condition on page2-73 occurs at that time. When the user activates the load, the UPGRADE condition occurs.


Note Whenever TSC cards are changed from active to standby, it takes approximately 12 minutes to completely synchronize to the timing source because the Stratum 3E timing module is being adopted.


2.5.146  WTR

Not Alarmed (NA), Non-Service Af]fecting (NSA)

The Wait to Restore condition indicates that revertive switching is specified and that a switch to protection occurred. When the working path is viable, this condition occurs while the wait to restore timer has not expired. The condition clears when the timer expires and traffic switches back to the working path.

2.5.147  XCMTX

Critical (CR), Service Affecting (SA)

The Unavailable Cross-Connection Matrix Equipment alarm indicates no cross-connection matrix on the NE (node). If there was previously a single CXC card running in unprotected mode, that card fails. If there were two cards running in protected mode, the matrix has become unavailable on both. Troubleshoot with the "Clear the UNPROT-XCMTX Alarm" procedure.

2.6  Common Troubleshooting Procedures

This section contains procedures that are commonly used while troubleshooting alarms for the ONS15600SDH.

2.6.1  Identify a Ring ID or Node ID Number


Step 1 In the node view, click View>GotoNetworkView .

Step 2 Click the Provisioning > MS-SPRing tabs.

Step 3 From the Ring ID column, record the Ring ID, or in the nodes column, record the Node IDs in the MS-SPRing. The Node IDs are the numbers in parentheses next to the node name.


2.6.2  Change a Ring ID Number


Step 1 In the node view, click View>GotoNetworkView .

Step 2 Click the Provisioning > MS-SPRing tabs.

Step 3 Highlight the ring and click Edit.

Step 4 In the MS-SPRing window, enter the new ID in the Ring ID field.

Step 5 Click Apply.

Step 6 Click Yes in the Changing Ring ID dialog box.


2.6.3  Clear a Loopback


Step 1 Log into a node on the network if you have not done so already.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > Loopback tabs.

Step 4 In the Loopback Type column, determine whether any port row displays a state other than None.

Step 5 If a row contains a state other than None, click in the column cell to display the drop-down menu and select None.

Step 6 In the State column, determine whether any port row shows a state other than INS.

Step 7 If a row shows a state other than INS, click in the column cell to display the drop-down list and select INS.

Step 8 Click Apply.


2.6.4  Change a Node ID Number


Step 1 In the node view, click View>GotoNetworkView .

Step 2 Click the Provisioning > MS-SPRing tabs.

Step 3 Highlight the ring and click Edit.

Step 4 In the MS-SPRing window, right-click the node on the ring map.

Step 5 Select Set Node ID from the shortcut menu.

Step 6 Enter the new ID in the field.

Step 7 Click Apply.


2.6.5  Delete a Circuit


Step 1 Log into a node on the network if you have not done so already.

Step 2 In node view, click the Circuits tab.

Step 3 Click the circuit row to highlight it and click Delete.

Step 4 Click Yes in the Delete Circuits dialog box.


2.6.6  Request a Cross-Connect Card Preferred Copy Switch


Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.



Step 1 Determine which CXC card is the preferred copy and which is currently in use.

In the node view, click the Maintenance > Preferred Copy tabs.

Step 2 In the Set Preferred drop-down menu, select the alternate copy. (For example, if the Slot 8 CopyB is preferred and in use, select the Slot 6 CopyA.


Caution Do not select the copy that you want to replace.


Step 3 Click Apply .

Step 4 Click Yes in the confirmation dialog box.


Note If you attempt a preferred copy switch and the switch is unsuccessful, it indicates a problem on the alternate CXC card.


Step 5 Click Refresh until the tab shows that the alternate copy you selected is now the preferred copy. The Currently Used field dynamically changes to show the newly selected preferred copy.


2.6.7  Soft-Reset the TSC Card Using CTC

This procedure is used to force system control from the active TSC card to the standby TSC card. In this kind of reset, the card is rebooted but the flash memory is not cleared.


Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.



Note Whenever TSC cards are changed from active to standby, it takes approximately 12 minutes to completely synchronize to the timing source because the Stratum 3E timing module is being adopted.



Step 1 Determine which TSC card is active and which is standby.

Position the cursor over the active card. An active TSC card has a green ACT STBY LED illuminated.

Step 2 Right-click the active TSC card to reveal the shortcut menu.

Step 3 Click Soft-reset Card .

Step 4 Click Yes when the confirmation dialog box appears.

Step 5 Click OK when the "Lost connection to node, changing to Network View" dialog box appears.


Note The TSC card takes several minutes to reboot. Refer to the CiscoONS15600SDH Procedure Guide for more information about LED behavior during TSC card reboots.


Step 6 Confirm that the TSC card you reset is in standby mode after the reset.

A TSC card that is ready for service has a green SRV LED illuminated. An active TSC card has a green ACT STBY LED illuminated, but a standby card does not have this LED illuminated.


Tip If you run the cursor over the TSC card in CTC, a popup displays the card's status (whether active or standby).



2.6.8  Hard-Reset the TSC Using CTC

This procedure is used to force system control from the active TSC card to the standby TSC. This kind of reset reboots the card and clears the flash memory, making it appear like a newly inserted card.


Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard.



Caution Use hard resets with caution. There can be up to 15 other sets of bandwidth affected by a hard reset.



Note When a TSC card changes from active to standby, the node takes approximately 12 minutes to synchronize completely to the timing source because of the more accurate G.813 timing module being adopted.



Step 1 Determine which TSC card is the active card and which is the standby card.

Position the cursor over the active card. An active TSC card has a green ACT STBY LED illuminated.

Step 2 Right-click the active TSC card to reveal the shortcut menu.

Step 3 Click Hard-reset Card .

Step 4 Click Yes when the confirmation dialog box appears.

Step 5 Click OK when the "Lost connection to node, changing to Network View" dialog box appears.


Note The TSC card takes several minutes to reboot. Refer to the CiscoONS15600SDH Procedure Guide for more information about LED behavior during TSC card reboots.


Step 6 Confirm that the TSC card you reset is in standby mode after the reset.


Tip If you run the cursor over the TSC card in CTC, a popup displays the card's status (whether active or standby).



2.6.9  Physically Replace a Card


Step 1 Open the card ejectors.

Step 2 Slide the card out of the slot.

Step 3 Open the ejectors on the replacement card.

Step 4 Slide the replacement card into the slot along the guide rails.

Step 5 Close the ejectors.


2.6.10  Reset the TSC Card with a Card Pull


Note To determine whether you have an active or standby TSC card, position the cursor over the TSC card graphic to view the status.



Note Resetting a standby TSC card does not change its status to active.



Step 1 Ensure that the TSC card you want to reset is in standby mode.

A TSC card that is ready for service has a green SRV LED illuminated. An active TSC card has a green ACT STBY LED illuminated, but a standby card does not have this LED illuminated.


Tip If you run the cursor over the TSC card in CTC, a popup displays the card's status (whether active or standby).


Step 2 When the TSC card is in standby mode, unlatch the top and bottom ejector levers on the TSC card.

Step 3 Physically pull the card at least partly out of the slot until the lighted LEDs turn off.

Step 4 Wait 30 seconds. Reinsert the card and close the ejector levers.


Note The TSC card takes several minutes to reboot. Refer to the CiscoONS15600SDH Procedure Guide for more information about LED behavior during TSC card reboots.



Note When a standby TSC card is removed and reinserted (reseated), all three fan lights might momentarily illuminate, indicating that the fan controller cards have also reset.



2.6.11  Verify Node Visibility for Other Nodes


Step 1 In the node view, click the Provisioning > MS-SPRing tabs.

Step 2 Highlight an MS-SPRing.

Step 3 Click Ring Map .

Step 4 Verify that each node in the ring appears on the ring map with a node ID and IP address.

Step 5 Click Close.


2.6.12  Verify or Create Node DCC Terminations


Step 1 In the node view, click the Provisioning > DCC/GCC tabs.

Step 2 View the Port column entries to see where terminations are present for a node. If terminations are missing, proceed to Step 3.

Step 3 If necessary, create a DCC termination:

a. Click Create .

b. In the Create RS-DCC Terminations dialog box, click the ports where you want to create the DCC termination. To select more than one port, press the Shift key. To select particular ports, press the Control key.

c. In the Port State area, click the Set to IS radio button.

d. Verify that the Disable OSPF on Link check box is unchecked.

e. Click OK .


2.6.13  Lock Out an MS-SPRing Span


Step 1 In the node view, click the Maintenance > MS-SPRing tabs.

Step 2 Click the MS-SPRing row table cell under the West Switch column to reveal the drop-down menu.

Step 3 Choose LOCKOUT SPAN and click Apply .

Step 4 Click OK in the MS-SPRing Operations dialog box.


2.6.14  Clear an MS-SPRing Span Lockout


Step 1 In the node view, click the Maintenance > MS-SPRing tabs.

Step 2 Click the MS-SPRing row table cell under the West Switch column to reveal the drop-down menu.

Step 3 Choose CLEAR and click Apply .

Step 4 Click OK on the MS-SPRing Operations dialog box.


2.6.15  Remove and Replace a Card

This is a generic procedure. For more specific procedures, see the "Replace a CXC Card" procedure on page3-1, the "Replace an STM-16 Card or STM-64 Card" procedure on page3-2, or the "Replace a TSC Card" procedure on page3-9.


Note When you replace a card with an identical type of card, you do not need to make changes to the database.



Step 1 Open the card ejectors.

Step 2 Slide the card out of the slot.

Step 3 Open the ejectors on the replacement card.

Step 4 Slide the replacement card into the slot along the guide rails until it contacts the backplane.

Step 5 Close the ejectors.


2.6.16  Set the Optical Power Received Nominal Value


Step 1 In node view, double-click the STM-N card that you want to provision. The card view appears.

Step 2 Click the Provisioning > QOS Thresholds tabs.

Step 3 From the Types list, choose Physical and click Refresh.

Step 4 For the port you want to provision, click Set in the Set OPR column. In the confirmation dialog box, click OK .