Table Of Contents
Alarm Troubleshooting
1.1 Alarm Index
1.2 Alarm Index by Alarm Type
1.2.1 Alarm Type/Object Definition
1.3 Trouble Notifications
1.3.1 Conditions
1.3.2 Severities
1.4 Alarm Procedures
1.4.1 AIS
1.4.2 AIS-L
1.4.3 AIS-P
1.4.4 AIS-V
1.4.5 APSB
1.4.6 APSCDFLTK
1.4.7 APSC-IMP
1.4.8 APSCINCON
1.4.9 APSCM
1.4.10 APSCNMIS
1.4.11 APSMM
1.4.12 AUTOLSROFF
1.4.13 AUTORESET
1.4.14 AUTOSW-AIS
1.4.15 AUTOSW-LOP (STSMON)
1.4.16 AUTOSW-LOP (VT-MON)
1.4.17 AUTOSW-PDI
1.4.18 AUTOSW-SDBER
1.4.19 AUTOSW-SFBER
1.4.20 AUTOSW-UNEQ (STSMON)
1.4.21 AUTOSW-UNEQ (VT-MON)
1.4.22 BKUPMEMP
1.4.23 BLSROSYNC
1.4.24 CARLOSS (E-Series)
1.4.25 CARLOSS (EQPT)
1.4.26 CARLOSS (G1000-4)
1.4.27 CONCAT
1.4.28 CONTBUS-A
1.4.29 CONTBUS-A-18
1.4.30 CONTBUS-B
1.4.31 CONTBUS-B-18
1.4.32 CTNEQPT-PBSTBY
1.4.33 CTNEQPT-PBACT
1.4.34 DATAFLT
1.4.35 DS3-MISM
1.4.36 EOC
1.4.37 EQPT
1.4.38 EQPT-MISS
1.4.39 E-W-MISMATCH
1.4.40 EXCCOL
1.4.41 EXERCISE-RING-FAIL
1.4.42 EXERCISE-SPAN-FAIL
1.4.43 EXT
1.4.44 FAILTOSW
1.4.45 FAILTOSW-PATH
1.4.46 FAILTOSWR
1.4.47 FAILTOSWS
1.4.48 FAN
1.4.49 FE-AIS
1.4.50 FE-DS1-MULTLOS
1.4.51 FE-DS1-SNGLLOS
1.4.52 FE-DS3-SA
1.4.53 FE-EQPT-NSA
1.4.54 FE-IDLE
1.4.55 FE-LOCKOUT
1.4.56 FE-LOF
1.4.57 FE-LOS
1.4.58 FEPRLF
1.4.59 FORCED-REQ
1.4.60 FRNGSYNC
1.4.61 FSTSYNC
1.4.62 HITEMP
1.4.63 HLDOVERSYNC
1.4.64 IMPROPRMVL
1.4.65 INCOMPATIBLE-SW
1.4.66 INVMACADDR
1.4.67 LOCKOUT-REQ
1.4.68 LOF (BITS)
1.4.69 LOF (DS1)
1.4.70 LOF (DS3)
1.4.71 LOF (EC1-12)
1.4.72 LOF (OC-N)
1.4.73 LOGBUFR90
1.4.74 LOGBUFROVFL
1.4.75 LOP-P
1.4.76 LOP-V
1.4.77 LOS (BITS)
1.4.78 LOS (DS-N)
1.4.79 LOS (EC1-12)
1.4.80 LOS (OC-N)
1.4.81 LPBKDS1FEAC
1.4.82 LPBKDS3FEAC
1.4.83 LPBKFACILITY (DS-N or EC1-12)
1.4.84 LPBKFACILITY (OC-N)
1.4.85 LPBKTERMINAL (DS-N, EC1-12)
1.4.86 LPBKTERMINAL ( G1000-4)
1.4.87 LPBKTERMINAL (OC-N)
1.4.88 MAN-REQ
1.4.89 MANRESET
1.4.90 MEA (AIP)
1.4.91 MEA (EQPT)
1.4.92 MEA (FAN)
1.4.93 MEM-GONE
1.4.94 MEM-LOW
1.4.95 MFGMEM
1.4.96 NOT-AUTHENTICATED
1.4.97 PDI-P
1.4.98 PEER-NORESPONSE
1.4.99 PLM-P
1.4.100 PLM-V
1.4.101 PRC-DUPID
1.4.102 RAI
1.4.103 RCVR-MISS
1.4.104 RDI-P
1.4.105 RFI-L
1.4.106 RFI-P
1.4.107 RFI-V
1.4.108 RING-MISMATCH
1.4.109 SD-L
1.4.110 SD-P
1.4.111 SF-L
1.4.112 SF-P
1.4.113 SFTWDOWN
1.4.114 SFTWDOWN-FAIL
1.4.115 SQUELCH
1.4.116 SSM-FAIL
1.4.117 STU
1.4.118 SWMTXMOD
1.4.119 SWTOPRI
1.4.120 SWTOSEC
1.4.121 SWTOTHIRD
1.4.122 SYNCPRI
1.4.123 SYNCSEC
1.4.124 SYNCTHIRD
1.4.125 SYSBOOT
1.4.126 TIM-P
1.4.127 TPTFAIL
1.4.128 TRMT
1.4.129 TRMT-MISS
1.4.130 UNEQ-P
1.4.131 UNEQ-V
1.5 DS3-12E Line Alarms
Alarm Troubleshooting
This chapter gives a description, severity, and troubleshooting procedure for each Cisco ONS 15454 alarm. Table 1-1 gives an alphabetical list of alarms that appear on the ONS 15454. Table 1-2 gives a list of alarms organized by alarm type. Both lists cross-reference the alarm entry, which gives the severity, description and troubleshooting procedure for each particular alarm.
The troubleshooting procedure for an alarm applies to both the CTC and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
The default standby severity for all ONS 15454 alarms is Minor, Non-service affecting, as defined in Telcordia GR-474. All severities listed in the alarm entry are the default for the active card, if applicable.
This chapter provides a comprehensive list of alarms (conditions with a severity of Minor, Major or Critical.) It also includes some conditions with severities of non-alarmed (NA) or not reported (NR), which are commonly encountered while troubleshooting major alarms. The default standby severity for conditions with a severity of NA, Non-service affecting (NSA) is NA, NSA. The default standby severity for conditions with a severity of NR, NSA is NR, NSA. For a comprehensive list of all conditions, see the Cisco ONS 15454 TL1 Command Guide.
1.1 Alarm Index
The alarm index list alarms by the name displayed on the CTC alarm pane in the conditions column.
1.2 Alarm Index by Alarm Type
The alarm index by alarm type gives the name and page number of every alarm in the chapter organized by alarm type.
1.2.1 Alarm Type/Object Definition
Table 1-3 Alarm Type/Object Definition
AIP
|
Auxiliary interface protection module
|
BITS
|
Building integration timing supply (BITS) incoming references (BITS-1, BITS-2)
|
BPLANE
|
The backplane
|
DS1
|
A DS1 line on a DS1 or DS3XM card
|
DS3
|
A DS3 line on a DS3 or DS3XM card
|
E1000F
|
An Ethernet line on an E1000 card
|
E100T
|
An Ethernet line on an E100 card
|
EC1-12
|
An EC1 line on an EC1 card
|
ENVALRM
|
An environmental alarm port on an AIC card
|
EQPT
|
A card in any of the 17 card slots. This object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, STS and VT
|
EXT-SREF
|
BITS outgoing references (SYNC-BITS1, SYNC-BITS2)
|
FAN
|
Fan-tray assembly
|
G1000
|
An Ethernet line on a G1000
|
NE
|
The entire network element (SYSTEM)
|
NE-SREF
|
Represents the timing status of the NE
|
OCN
|
An OCN line on an OCN card
|
RING
|
BLSR ring number (STSRNG)
|
STSMON
|
STS alarm detection at the monitor point (upstream of cross-connect)
|
STSTRM
|
STS alarm detection at termination (downstream of cross-connect)
|
VT-MON
|
VT1 alarm detection at the monitor point (upstream of cross-connect)
|
VT-TERM
|
VT1 alarm detection at termination (downstream of cross-connect)
|
1.3 Trouble Notifications
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The ONS 15454 reports both alarmed trouble notifications, under the Alarms tab, and non-alarmed (NA) trouble notifications, under the Conditions tab 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 which does not require action, such as a switch to a secondary timing reference (SWTOSEC) or a user-initiated manual reset (MANRESET).
Telcordia further divides alarms into Service-Affecting (SA) and Non-Service-Affecting (NSA) status. An SA failure affects a provided service or the network's ability to provide service. For example, a missing transmitter (TRMT-MISS) alarm is characterized as an SA failure. TRMT-MISS occurs when the cable connector leading to a port on an active DS1-14 card is removed. This affects a provided service, because traffic switches to the protect card. The high temperature (HITEMP) alarm, which means the ONS 15454 is hotter than 122 degrees Fahrenheit (50 degrees Celsius), is also an SA failure. Although for example a particular DS1-14 port may not be affected, a high temperature affects the network's ability to provide service.
1.3.1 Conditions
When an SA failure is detected, the ONS 15454 also sends an alarm indication signal (AIS) downstream. When it receives the AIS, the receiving node sends a remote failure indication (RFI) upstream. AIS and RFI belong in the conditions category and show up on the Conditions screen of the ONS 15454. However, unlike most conditions which are non-alarmed, Telcordia classifies these conditions as not reported (NR).
Both CTC and TL1 report NRs and NAs as conditions when conditions are retrieved. NAs are also reported as autonomous events under TL1 and under the History tab of the CTC. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 TL1 Command Guide.
1.3.2 Severities
The ONS 15454 uses Tecordia-standard severities: Critical (CR), Major (MJ), and Minor (MN). Critical indicates a severe, service-affecting alarm that needs immediate correction. Major is still a serious alarm, but the failure has less of an impact on the network. For example, with a DS1-14 LOS, a Major alarm, 24 DS-0 circuits lose protection. But with a OC-192 LOS, a Critical alarm, over a hundred thousand DS-0 circuits lose protection.
Minor alarms, such as Fast Start Synchronization (FSTSYNC), do not have a serious affect on service. FSTSYNC lets you know that the ONS 15454 is choosing a new timing reference because the old reference failed. The loss of the prior timing source is something a user needs to look at, but it should not imediately disrupt service.
Telcordia standard severities are the default settings for the ONS 15454. A user may customize ONS 15454 alarm severities with the alarm profiles feature. For a description of alarm profiles, refer to the Cisco ONS 15454 Installation and Operations Guide.
This chapter lists the default alarm severity for the active reporting card, if applicable. The default severity for alarms reported by standby cards is always Minor, Non-Service-Affecting.
1.4 Alarm Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description and troubleshooting procedure accompany each alarm and condition.
1.4.1 AIS
•
Not Reported (NR)
The ONS 15454 detects an alarm indication signal (AIS) in the SONET overhead. This alarm is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AIS, for example, when the port on the reporting node is in-service but the OC-N port on a node upstream on the circuit is not in-service. The upstream node often reports a loss of service or has an out-of-service port. The AIS clears when you clear the primary alarm on the upstream node. However, the primary alarm node may not report any alarms that indicate it is at fault.
Procedure: Clear the AIS Condition
Step 1 Check upstream nodes and equipment for alarms, especially for LOS and out-of-service ports.
Step 2 Clear the upstream alarms.
1.4.2 AIS-L
•Not Reported (NR)
The ONS 15454 detects an alarm indication signal (AIS) in the SONET overhead. This alarm is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AIS, for example, when the port on the reporting node is in-service but a node upstream on the circuit does not have its OC-N port in-service. The upstream node often reports an LOS or has an out-of-service port. The AIS-L clears when you clear the primary alarm on the upstream node. However, the primary alarm node may not report any alarms that indicate it is at fault.
An AIS-L occurs at the line layer. The line layer refers to the segment between two SONET devices in the circuit and is also known as a maintenance span. The line layer deals with SONET payload transport, and its functions include multiplexing and synchronization.
Procedure: Clear the AIS-L Condition
Step 1 Check upstream nodes and equipment for alarms, especially for LOS and an out-of-service port.
Step 2 Clear the upstream alarms.
1.4.3 AIS-P
•Not Reported (NR) (Condition)
The ONS 15454 detects an alarm indication signal (AIS) in the SONET overhead. This alarm is secondary to another alarm occurring simultaneously in an upstream node. The AIS is caused by an incomplete circuit path, for example, when the port on the reporting node is in-service, but a node upstream on the circuit does not have its port in-service. The upstream node often reports a LOS or has an OC-N port out of service. The AIS-P clears when the primary alarm on the upstream node is cleared. However, the node with the primary alarm may not report any alarms to indicate it is at fault.
AIS-P occurs in each node on the incoming OC-N path. The path layer is the segment between the originating equipment and the terminating equipment. This path segment encompasses several consecutive line segments or segments between two SONET devices. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.
Procedure: Clear the AIS-P Condition
Step 1 Check upstream nodes and equipment for alarms, especially LOS and out-of-service ports.
Step 2 Clear the upstream alarms.
1.4.4 AIS-V
•Not Reported (NR)
The ONS 15454 detects an alarm indication signal (AIS) in the SONET overhead. This alarm is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AIS, for example, when the port on the reporting node is in-service but a node upstream on the circuit does not have its OC-N port in-service. The upstream node often reports a LOS or has an out-of-service port. The AIS-V clears when the primary alarm is cleared. The node with the out-of-service port may not report any alarms to indicate it is at fault.
An AIS-V indicates that an upstream failure occurred at the virtual tributary (VT) layer. The VT, or electrical layer, is created when the SONET signal is broken down into an electrical signal, for example when an optical signal comes into an ONS 15454 OC-N card. If this optical signal is demultiplexed by the ONS 15454, and one of the channels separated from the optical signal is then cross-connected into the DS1-14 ports in the same node, that ONS 15454 reports an AIS-V alarm.
An AIS-V error message on the electrical card is accompanied by an AIS-P error message on the cross-connected OC-N card.
Note See the "AIS-V on DS3XM-6 Unused VT Circuits" section on page 2-33 for AIS-Vs that occur on DS3XM-6 unused VT circuits.
Procedure: Clear the AIS-V Condition
Step 1 Check upstream nodes and equipment for alarms, especially LOS and out-of-service ports.
Step 2 Correct the upstream alarms.
1.4.5 APSB
•Minor, Non-service affecting
The channel byte failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming automatic protection switching (APS) signal. This happens when an inconsistent APS byte or invalid code is detected. Some older, non-Cisco SONET nodes send invalid APS codes if configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15454. These invalid codes will raise an APSB on an ONS node.
Procedure: Clear the APSB Alarm
Step 1 Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes.
Step 2 If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment may not interoperate effectively with the ONS 15454. For ONS 15454 protection switching to operate properly, the upstream equipment may need to be replaced.
1.4.6 APSCDFLTK
•Minor, Non-service affecting
The Default K Byte Received alarm occurs when a BLSR is not properly configured, for example, when a four-node BLSR has one node configured as UPSR. A node in a UPSR or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
The alarm can also be caused when a new node is added but a new ring map has not been accepted. Troubleshooting for APSCDFLTK is often similar to troubleshooting for BLSROSYNC.
Procedure: Clear the APSCDFLTK Alarm
Step 1 Prior to accepting a new mapping table, verify that each node has a unique node ID number.
a. Log into a node on the ring.
b. Click the Provisioning > Ring tabs.
c. Record the node ID number.
d. Repeat steps a - c for all nodes in the ring.
e. If two nodes have the same node ID number, change one node's ID number so that each node has a unique node ID.
f. Click Apply.
Step 2 Verify correct configuration of east port and west port optical fibers (see the "E-W-MISMATCH" section).
Step 3 If it is a four fiber BLSR system, make sure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if there is a working fiber incorrectly attached to a protection fiber.
Step 4 Click Yes to accept the Ring Map.
Step 5 If the alarm does not clear, check the ring map for each ONS 15454 in the network and verify that each node is visible to the other nodes.
a. At the node (default) view, click the Provisioning > Ring tabs.
b. Highlight a BLSR ring.
c. Click Ring Map.
d. Verify that each node that is part of the ring appears on the Ring Map with a Node ID and IP Address.
e. Click Close.
Step 6 If nodes are not visible, ensure that SDCC terminations exist on each node.
a. Click the Provisioning > SONET DCC tabs.
b. Click Create.
c. Click the OC-N card that links to the adjacent node.
d. Click OK.
Step 7 If the alarm still does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.7 APSC-IMP
•Minor, Non-service affecting
An Improper SONET Automatic Protect Switch code alarm indicates invalid K bytes. This alarm occurs on OC-N cards in a BLSR 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 electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the APSC-IMP Alarm
Step 1 To determine the validity of the K byte signal, examine the received signal. Use an optical test set capable of viewing SONET overhead.
Step 2 If the K byte is invalid, the problem lies in upstream equipment and not in the reporting ONS 15454. Troubleshoot the appropriate upstream equipment.
Step 3 If the K byte is valid, verify that each node has a ring ID that matches the other node ring IDs:
a. Using CTC, log into a node on the ring.
b. Click the Provisioning > Ring tabs.
c. Record the ring ID number.
d. Repeat steps a - c for all nodes in the ring.
Step 4 If a node has a ring ID number that does not match the other nodes, change the ring ID number of that node to match the other nodes in the ring.
Step 5 Click Apply.
1.4.8 APSCINCON
•Minor, Service affecting
An inconsistent automatic protection switching (APS) alarm is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the SONET 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.
Procedure: Clear the APSCINCON Alarm
Step 1 Look for other alarms, especially LOS, loss of frame (LOF) or AIS. Clearing these alarms clears the APSCINCON alarm.
Step 2 If an APSINCON alarm occurs with no other alarms, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.9 APSCM
•Major, Service affecting
The APS Channel Mismatch alarm occurs when the ONS 15454 expects a working channel but receives a protection channel. 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 will not occur. The APSCM alarm only occurs on the ONS 15454 when 1+1 bidirectional protection is used on OC-N cards in a 1+1 configuration.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the APSCM Alarm
Step 1 Verify that the working-card channel fibers connect directly to the adjoining node's working-card channel fibers.
Step 2 Verify that the protection-card channel fibers connect directly to the adjoining node's protection-card channel fibers.
1.4.10 APSCNMIS
•Major, Service affecting
The APS Node ID Mismatch alarm raises when the source node ID contained in the K2 byte of the APS channel being received is not present in the ring map. This alarm may occur and clear when a BLSR is being provisioned. If so the user can disregard the temporary occurrence. If an APSCNMIS raises and stays, the alarm clears when the receiving node receives or matches the expected K-byte. If the APSCNMIS is raised and stays, the alarm clears when a K byte with valid source node ID in K2 is received.
Procedure: Clear the APSCNMIS Alarm
Step 1 Verify that each node has a unique node ID number.
a. Click the Provisioning > Ring tabs.
b. Click the BLSR row to highlight.
c. Click Ring Map.
d. If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.
e. Click Close on the Ring Map dialog box.
Step 2 If two nodes have the same node ID number, change one node's ID number so that each node has a unique node ID:
a. Display the network view.
b. Log into one of the nodes that uses the repeated node ID recorded in Step 1.
Note If the node names shown on the network view do not correlate with the node IDs, log into each node and click the Provisioning > Ring tabs. This screen displays the node ID of the node you are logged into.
c. Click the Node ID table cell to reveal a pull-down menu.
d. Select a unique node ID from the pull-down menu and click Apply.
Note Locking out and clearing the lockout on a span causes the ONS 15454 to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.
Step 3 If the alarm does not clear, lockout a span on the ring and then clear the lockout:
a. Click the Ring > Maintenance tabs.
b. Click the table cell under the West Switch heading to reveal the pull-down menu.
c. Select LOCKOUT SPAN and click Apply.
d. Click OK on the BLSR Operations dialog box.
e. Click the same table cell under the West Switch heading to reveal the pull-down menu.
f. Select CLEAR and click Apply.
g. Click OK on the BLSR Operations dialog box.
1.4.11 APSMM
•Minor, Non-service affecting
An APS Mode Mismatch failure occurs when there is a mismatch of the protection switching schemes at the two ends of the span. If one node is provisioned for bidirectional switching, the node at the other end of the span must also be provisioned for bidirectional switching. If one end is provisioned for bidirectional and the other is provisioned for unidirectional, an APSMM alarm occurs in the ONS node that is provisioned for bidirectional. This alarm occurs in a 1+1 configuration.
Procedure: Clear the APSMM Alarm
Step 1 For the reporting ONS 15454, display the CTC node view and click the Provisioning > Protection tabs.
Step 2 Choose the 1+1 protection group configured for the OC-N cards.
This is the protection group optically connected (with DCC connectivity) to the far end.
Step 3 Record whether the bidirectional switching box is checked.
Step 4 Log into the far end node and verify that the OC-N 1+1 protection group is provisioned.
This is the protection group optically connected (with DCC connectivity) to the near end.
Step 5 Verify that the bidirectional switching box matches the checked or unchecked condition of the box recorded in Step 3. If not, change it to match.
Step 6 Click Apply.
1.4.12 AUTOLSROFF
•Critical, Service affecting
Warning On the OC-192 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 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 100 mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.
The auto laser off alarm raises when the OC-192 card temperature exceeds 90 degrees Centigrade. The internal equipment automatically shuts down the OC-192 laser when the card temperature rises to prevent the card from self-destructing.
Procedure: Clear the AUTOLSROFF Alarm
Step 1 Read the temperature displayed on the ONS 15454 LCD front panel.
Step 2 If the temperature of the ONS 15454 exceeds 90 degrees Centigrade, complete the "Clear the HITEMP Alarm" procedure.
Step 3 If the temperature of the ONS 15454 is below 90 degrees Centigrade, replace the OC-192 card.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 4 Call the Technical Assistance Center (TAC) at 1-800-553-2447 to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.
1.4.13 AUTORESET
•Minor, Non-service affecting
The AUTORESET alarm occurs when a card performs a warm reboot automatically. This happens when you change an IP address or perform any other operation that causes an automatic card-level reboot.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the AUTORESET Alarm
Step 1 Check for additional alarms that may have triggered an automatic reset.
Step 2 If the card automatically resets more than once a month with no apparent cause, replace it with a new card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.14 AUTOSW-AIS
•Not Reported (Condition)
AUTOSW-AIS indicates that automatic UPSR protection switching took place because of an AIS alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "AIS" section.
1.4.15 AUTOSW-LOP (STSMON)
•Not Alarmed (Condition)
AUTOSW-LOP indicates that automatic UPSR protection switching took place because of an LOP alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "LOP-P" section.
1.4.16 AUTOSW-LOP (VT-MON)
•Minor, Service affecting
AUTOSW-LOP indicates that automatic UPSR protection switching took place because of an LOP alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "LOP-P" section.
1.4.17 AUTOSW-PDI
•Not Alarmed (Condition)
AUTOSW-PDI indicates that automatic UPSR protection switching took place because of a PDI alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "PDI-P" section.
1.4.18 AUTOSW-SDBER
•Not Alarmed (NA) (Condition)
AUTOSW-SDBER indicates that automatic UPSR protection switching took place because of an SD alarm. The UPSR is configured for revertive switching and has switched back to the working path.
1.4.19 AUTOSW-SFBER
•Not Alarmed (NA) (Condition)
AUTOSW-SFBER indicates that automatic UPSR protection switching took place because of a SF alarm. The UPSR is configured for revertive switching and will switch back to the working path. Troubleshoot with the "SF-L" section.
1.4.20 AUTOSW-UNEQ (STSMON)
•Not Alarmed (Condition)
AUTOSW-UNEQ indicates that automatic UPSR protection switching took place because of an UNEQ alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "UNEQ-P" section.
1.4.21 AUTOSW-UNEQ (VT-MON)
•Minor, Service affecting
AUTOSW-UNEQ indicates that automatic UPSR protection switching took place because of an UNEQ alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears. Troubleshoot with the "UNEQ-P" section.
1.4.22 BKUPMEMP
•Critical, Non-service affecting
The BKUPMEMP alarm refers to a problem with the TCC+ card's flash memory. The alarm occurs when the TCC+ card is in use and has one of four problems: the flash manager fails to format a flash partition, the flash manager fails to 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 TCC+.
The BKUPMEMP alarm will also raise the EQPT alarm. In this instance, use the following procedure will clear the BKUPMEMP and the EQPT alarm.
Procedure: Clear the BKUPMEMP Alarm
Step 1 Verify that both TCC+ cards are powered and enabled by confirming lighted ACT/STBY LEDs on the TCC+ cards.
Step 2 Reset the active TCC+ card to make the standby TCC+ card active:
a. In CTC, display the node view.
b. Position the cursor over the active TCC+ card slot.
c. Right click and choose RESET CARD.
Step 3 If the alarm clears, reseat the old TCC+ and allow it to boot up completely.
Step 4 Do a second reset, this time on the newly-active TCC+ card to make the recently-reseated standby TCC+ card active.
a. In CTC, display the node view.
b. Position the cursor over the active TCC+ card slot.
c. Right click and choose RESET CARD.
Step 5 If the alarm reappears after you perform the switch, replace the TCC+ card.
a. Open the card ejectors.
b. Slide the card out of the slot.
c. Open the ejectors on the replacement card.
d. Slide the replacement card into the slot along the guide rails.
e. Close the ejectors.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
1.4.23 BLSROSYNC
•Major, Service affecting
The BLSR Out Of Sync alarm occurs when the mapping table needs updating. To clear the alarm, a new ring map must be created and accepted. Before you create a new ring map, complete Steps 1 - 4.
Procedure: Clear the BLSROSYNC Alarm
Step 1 Prior to accepting a new mapping table, verify that each node has a unique node ID number:
a. Log into a node on the ring.
b. Click the Provisioning > Ring tabs.
c. Record the Node ID number.
d. Repeat steps a - c for all nodes in the ring.
e. If two nodes have the same node ID number, change one node ID number, so the node ID number is unique within that ring.
f. Click Apply.
Step 2 Verify that each node has a ring ID that matches the other node ring IDs:
a. Log into the next node on the ring.
b. Click the Provisioning > Ring tabs.
c. Record the Ring ID number.
d. Repeat steps a - b for all nodes in the ring.
e. If a node has a ring ID number that does not match the other nodes, change the ring ID to match all the other nodes in the ring.
f. Click Apply.
Step 3 Verify correct configuration of the east port and west port optical fibers (see the "E-W-MISMATCH" section.)
Step 4 If it is a four-fiber BLSR system, amke sure that each protect fiber connects to another protect fiber, and each working fiber connects to another working fiber. The software does not report any alarm, if there is a working fiber misconnected to a protect fiber.
Step 5 If the east-to-west configuration changes, click Apply.
The BLSR Ring Map Change screen appears.
Step 6 Click Yes to accept the Ring Map.
Step 7 If the alarm does not clear, check the ring map for each ONS 15454 in the network and verify that each node is visible to the other nodes.
Step 8 If nodes are not visible, ensure that SDCC terminations exist on each node.
a. Click the Provisioning > SONET DCC tabs.
b. Click Create.
c. Click the OC-N card that links to the adjacent node.
d. Click OK.
Step 9 If alarms are raised when the DCCs are turned on, follow the troubleshooting procedure in the "EOC" section.
Step 10 If the alarm still does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.24 CARLOSS (E-Series)
•Major, Service affecting
A carrier loss on the LAN is the data equivalent of a SONET LOS alarm. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of this alarm are a disconnected cable, an OC-N fiber connected to the Ethernet GBIC or an improperly installed Ethernet card. Ethernet card ports must be enabled (put in service) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
This alarm also occurs after the restoration of a node's database. In this instance, the alarm will clear in approximately 30 seconds after spanning tree protection reestablishes. This applies to the E-series Ethernet cards but not the G1000-4 card, as this card does not use STP and is unaffected by STP reestablishment.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CARLOSS Alarm
Step 1 Verify that the Ethernet cable is properly connected and attached to the correct port.
Step 2 Verify that the Ethernet cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
Step 3 Check that the transmitting device is operational. If not, troubleshoot the device.
Step 4 Using a test set, determine that a valid signal is coming into the Ethernet port.
Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the Ethernet cable connecting the transmitting device to the Ethernet port.
Step 6 If a valid Ethernet signal is present, physically reseat the Ethernet card.
Step 7 If the alarm does not clear, replace the Ethernet card.
a. Open the card ejectors.
b. Slide the card out of the slot.
c. Open the ejectors on the replacement card.
d. Slide the replacement card into the slot along the guide rails.
e. Close the ejectors.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 8 If a CARLOSS alarm repeatedly appears and clears, examine the layout of your particular network to determine whether the Ethernet circuit is part of an Ethernet manual cross connect. If the reporting Ethernet circuit is part of an Ethernet manual cross connect, then the reappearing alarm may be a result of mismatched STS circuit sizes in the set up of the manual cross connect. If the Ethernet circuit is not part of a manual cross connect, these steps do not apply.
Note A Ethernet manual cross connect is used when another vendors' equipment sits between ONS 15454s, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Right-click or left-click the Select Affected Circuits dialog that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. From the examination of the layout of your particular network, determine the ONS 15454 and card that host the Ethernet circuit at the other end of the Ethernet manual cross connect.
e. Log into the ONS 15454 at the other end of the Ethernet manual cross connect.
f. Double-click the Ethernet card that is part of the Ethernet manual cross connect.
g. Click the Circuits tab.
h. Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross connect. This circuit will connect the Ethernet card to an OC-N card on the same node.
i. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross connect have the same circuit size from the circuit size information you recorded.
j. If one of the circuit sizes is incorrect, navigate to the incorrectly configured circuit.
k. Click the incorrectly configured circuit to highlight it and click Delete.
l. Click Yes at the Delete Circuit dialog box, and OK at the Confirmation dialog box.
m. Reconfigure the circuit with the correct circuit size. Refer to the Cisco Installation and Operations Guide for procedures to provision Ethernet manual cross connects.
1.4.25 CARLOSS (EQPT)
•Minor, Non-service affecting
This carrier loss alarm means the ONS 15454 and the workstation hosting CTC do not have a TCP/IP connection. It is a problem involves the LAN or data circuit used by the RJ-45 connector on the TCC+ card or the LAN backplane pin connection on the back of the ONS 15454. It does not involve an Ethernet circuit connected to a port on Ethernet card. The problem is in the connection (usually a LAN problem) and not the CTC or the ONS 15454.
Procedure: Clear the CARLOSS Alarm
Step 1 Verify connectivity by pinging the ONS 15454 that is reporting the alarm:
a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Command Prompt.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
c. For both the Sun and Microsoft operating systems, at the prompt type:
ping [ONS 15454 IP address]
For example, ping 192.1.0.2.
If the workstation has connectivity to the ONS 15454, it displays a "reply from [IP Address]" after the ping. If the workstation does not have connectivity, a "Request timed out" message displays.
Step 2 If the ping is successful, an active TCP/IP connection exists. Restart the CTC.
Step 3 If you are unable to establish connectivity, perform standard network/LAN diagnostics. For example, trace the IP route, check cables, and check any routers between the node and CTC.
1.4.26 CARLOSS (G1000-4)
•Major, Service affecting
A carrier loss on the LAN is the data equivalent of a SONET LOS alarm. The Ethernet card has lost its link and is not receiving a valid signal.
CARLOSS on the G1000-4 stems from two general areas:
a) The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. A common cause is an Ethernet cable not connected properly to the reporting Ethernet port, an OC-N card is connected to the port instead of an Ethernet device, or there is a problem with the signal from the Ethernet device attached to the G1000-4 port.
b) There is a problem in the end-to-end path (including possibly the remote end G1000-4 card), which is causing the reporting G1000-4 to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far end G1000-4 port turns the transmitter laser back on, and this clears the CARLOSS on the reporting card. In this case, the CARLOSS alarm will normally be accompanied by another alarm or condition on the end-to-end path, such as a TPTFAIL or an OC-N alarm or condition.
Refer to the Ethernet Operations Chapter of the Installation and Operations Guide for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TPTFAIL" section for more information on alarms that occur when a point-to-point circuit exists between two G1000-4 cards.
Ethernet card ports must be enabled (put in service) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CARLOSS Alarm
Step 1 Verify that the Ethernet cable is properly connected and attached to the correct port.
Step 2 Verify that the Ethernet cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
Step 3 Check that the transmitting attached Ethernet device is operational. If not, troubleshoot the device.
Step 4 Using an Ethernet test set, determine that a valid signal is coming into the Ethernet port.
Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the Ethernet cable connecting the transmitting device to the Ethernet port.
Step 6 If link auto negotiation is set to enabled on the G1000-4 port, but the auto negotiation process fails then the G1000-4 will turn off its transmitter laser and report a CARLOSS alarm. If link auto negotiation has been enabled on the port, check for conditions which could cause auto negotiation to fail:
•Confirm that the attached Ethernet device has auto negotiation enabled and is configured for compatibility with the asymmetric flow control on the G1000-4.
•Confirm that the attached Ethernet device configuration allows reception of flow control frames.
Step 7 If all above attempts fail, disable and re-enable the Ethernet port to attempt to remove the CARLOSS condition (this will restart the auto negotiation process).
Step 8 If the TPTFAIL alarm is also reported, see "TPTFAIL" section. If the TPTFAIL alarm is not reported, continue to the next step.
Note When both alarms are reported, the reason for the condition may be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 9 Check to see if terminal loopback has been provisioned on this port.
On the G1000-4 card, provisioning a terminal loopback causes the transmit laser to turnoff. If an attached Ethernet device detects this as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Shutting of the transmit laser could cause the CARLOSS alarm detected by the G1000-4 port in loopback.
a. Click the Conditions tab click Retrieve Conditions.
b. If LPBKTERMINAL appears in the condition field of the Conditions pane, a terminal loopback has been set on this port.
Click Maintenance > Loopback.
Under the Loopback Type column, select NONE for the port row reporting the alarm.
Click Apply.
c. If LPBKTERMINAL does not appear in the condition field of the Conditions pane, continue to Step 4.
Step 10 If a CARLOSS alarm repeatedly appears and clears, examine the layout of your particular network to determine whether the Ethernet circuit is part of an Ethernet manual cross connect. If the reporting Ethernet circuit is part of an Ethernet manual cross connect, then the reappearing alarm may be a result of mismatched STS circuit sizes in the set up of the manual cross connect. If the Ethernet circuit is not part of a manual cross connect, these steps do not apply.
Note A Ethernet manual cross connect is used when another vendors' equipment sits between ONS 15454s, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Right-click or left-click the Select Affected Circuits dialog that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. From the examination of the layout of your particular network, determine the ONS 15454 and card that host the Ethernet circuit at the other end of the Ethernet manual cross connect.
e. Log into the ONS 15454 at the other end of the Ethernet manual cross connect.
f. Double-click the Ethernet card that is part of the Ethernet manual cross connect.
g. Click the Circuits tab.
h. Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross connect. This circuit will connect the Ethernet card to an OC-N card on the same node.
i. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross connect have the same circuit size from the circuit size information you recorded.
j. If one of the circuit sizes is incorrect, navigate to the incorrectly configured circuit.
k. Click the incorrectly configured circuit to highlight it and click Delete.
l. Click Yes at the Delete Circuit dialog box, and OK at the Confirmation dialog box.
m. Reconfigure the circuit with the correct circuit size. Refer to the Cisco Installation and Operations Guide for procedures to provision Ethernet manual cross connects.
Step 11 If a valid Ethernet signal is present, physically reseat the Ethernet card.
Step 12 If the alarm does not clear, replace the Ethernet card.
a. Open the card ejectors.
b. Slide the card out of the slot.
c. Open the ejectors on the replacement card.
d. Slide the replacement card into the slot along the guide rails.
e. Close the ejectors.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
1.4.27 CONCAT
•Critical, Service affecting
The STS Concatenation error alarm occurs when the transmitted STSc circuit is smaller than the provisioned STSc, which causes a mismatch of the circuit type on the concatenation facility. For example, an STS3c or STS1 is sent across a circuit provisioned for STS12c.
Either an incorrect circuit size was provisioned on the reporting node, or the circuit source is delivering the wrong circuit size. If a recently-configured circuit reports this alarm, it is more likely that the provisioned circuit size is incorrect. If a previously configured circuit has been operating correctly for a period and then reports the alarm, it is more likely that a problem occurred with the circuit source.
Procedure: Clear the CONCAT Alarm
Step 1 Check that the provisioned circuit size is correct:
a. Click the Circuits tab.
b. Find the appropriate row using the Circuit Name and record the size listed in the size column.
c. Determine whether the size listed matches the original network design plan.
Step 2 If the circuit size listed does not match the original network design plan, delete the circuit:
a. Click the circuit row to highlight it and click Delete.
b. Click Yes at the Delete Circuits dialog box.
c. Recreate the circuit with the correct circuit size.
Step 3 Check that the size of the circuit source matches the correct circuit size:
a. Measuring the source signal with a test set to determine if the circuit size matches the provisioned circuit.
b. If the source circuit signal is a test set, check that the test set settings match the intended circuit size.
1.4.28 CONTBUS-A
•Major, Non-service affecting
The communication failure TCC A to shelf slot alarm means the TCC+ card in Slot 7 has lost communication with a line card. Cards require frequent communication with the TCC+ card because the TCC+ performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET Data Communications Channel (SDCC) termination, system fault detection, and other operations for the ONS 15454. The TCC+ card also ensures that the system maintains Telcordia timing requirements.
The CONTBUS-A alarm can appear briefly when the ONS 15454 switches to the standby TCC+ card. In this instance, the alarm clears after the cards establish communication with the new primary TCC+ card. In cases where the alarm persists, the problem lies in the physical path of communication from the TCC+ to the reporting card. The physical path of communication includes the TCC+ card, the card in Slot X and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CONTBUS-A Alarm
Step 1 Ensure the reporting card is physically present. Record the card type.
Step 2 Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, complete the "Clear the MEA Alarm" procedure.
Step 3 If only one card slot reporting the alarm, perform a software reset of the traffic card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 4 If the software reset does not clear the alarm, physically reseat the reporting card.
Step 5 If all traffic cards report this alarm, perform a software reset of the active TCC+ card.
a. Display the node view.
b. Position the cursor over the active TCC+ card slot.
c. Right-click and choose RESET CARD.
Step 6 If the software reset does not clear the alarm, physically reseat the TCC+ card.
Step 7 If the alarm still does not clear, replace the TCC+ card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.29 CONTBUS-A-18
•Major, Non-service affecting
The communication failure from TCC slot to TCC slot alarm means the main processor on the TCC+ card in Slot 7 has lost communication with the coprocessor on the second TCC+ card in Slot 11. The problem is with the physical path of communication from the TCC+ card to the reporting card. The physical path of communication includes the two TCC+ cards and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CONTBUS-A-18 Alarm
Step 1 Position the cursor over the TCC+ card in Slot 7.
Step 2 Right-click the mouse to reveal a menu.
Step 3 To clear the alarm, choose RESET CARD to make the standby TCC+ in Slot 11 the active TCC+ and clear the alarm.
Step 4 Wait approximately 2 minutes for the TCC+ in Slot 7 to reset as the standby TCC+. Verify that the Standby LED is lit before proceeding to the next step.
Step 5 Position the cursor over the TCC+ card in Slot 11.
Step 6 Right-click the mouse to reveal a menu.
Step 7 Choose RESET CARD to make the standby TCC+ in Slot 7 the active TCC+.
Step 8 If the alarm reappears when the TCC+ in Slot 7 reboots as the active TCC+, the TCC+ card in Slot 7 is defective and must be replaced.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.30 CONTBUS-B
•Major, Non-service affecting
The communication failure TCC A to shelf slot alarm means the TCC+ card in Slot 11 lost communication with a line card. Cards require frequent communication with the TCC+ card, because the TCC+ card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET DCC termination, and system fault detection among other operations for the ONS 15454. The TCC+ card also ensures that the system maintains Telcordia timing requirements.
This alarm may appear briefly when the ONS 15454 switches over to the protect TCC+ card. In this instance, the alarm clears after the other cards establish communication with the new primary TCC+ card. In cases where the alarm persists, the problem lies in the physical path of communication from the TCC+ card to the reporting card. The physical path of communication includes the TCC+ card, the card in Slot X, and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CONTBUS-B
Step 1 Ensure the reporting card is physically present and that it matches the type of card identified in that slot on CTC.
Step 2 If this slot is the only one reporting the alarm, perform a software reset of the traffic card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click the mouse and choose RESET CARD to do a software reset.
Step 3 If the software reset does not clear the alarm, physically reseat the reporting card.
Step 4 If all cards with the exception of the active TCC+ report this alarm, perform a software reset of the active TCC+:
a. Display the CTC node view.
b. Position the cursor over the active TCC+ card slot.
c. Choose RESET CARD.
Step 5 If the software reset does not clear the card, physically reseat the TCC+ card to perform a card pull.
Step 6 If the alarm still does not clear, replace the TCC+ card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.31 CONTBUS-B-18
•Major, Non-service affecting
The communication failure from TCC slot to TCC slot alarm means main processor on the TCC+ card in Slot 11 lost communication with the coprocessor on the TCC+ card in Slot 7. The problem is with the physical path of communication from the TCC+ card to the reporting TCC+ card. The physical path of communication includes the two TCC+ cards and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CONTBUS-B-18 Alarm
Step 1 Position the cursor over the TCC+ card in Slot 11.
Step 2 Right-click and choose RESET CARD to make the TCC+ in Slot 11 the active TCC+ card.
Step 3 Wait approximately 2 minutes for the TCC+ in Slot 7 to reset as the standby TCC+ card. Verify that the Standby LED is lit before proceeding to the next step.
Step 4 Position the cursor over the TCC+ card in Slot 7.
Step 5 Right-click and choose RESET CARD again to make the TCC+ in Slot 11 the active TCC+ card.
Step 6 If the alarm reappears when the TCC+ in Slot 11 reboots as the active TCC+, the TCC+ card in Slot 11 is defective and must be replaced.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.32 CTNEQPT-PBSTBY
•Critical, Service affecting
The interconnection equipment failure protect payload bus alarm indicates a failure of the main payload between the protect cross-connect (XC/XCVT/XC10G) card in Slot 10 and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in either the cross-connect card, the reporting traffic card, the TCC+ card or the backplane.
Note If all traffic cards show this alarm, physically reseat the standby TCC+ card. If this fails to clear the alarm, replace the standby TCC+ card. Do not physically reseat an active TCC+ card. This disrupts traffic.
Note If CTNEQPT-PBSTBY is raised against all traffic cards on the shelf and SWMTXMOD, SD-L, AIS-L and RFI-L are also present, this could indicate a failed cross-connect card oscillator. Refer to the "Operation: Cross-Connect Card Oscillator Fails" section on page 2-31.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CTNEQPT-PBSTBY Alarm
Step 1 Perform a software reset on the standby cross-connect (XC/XCVT/XC10G) card:
a. Display the node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 2 If the alarm persists, physically reseat the standby cross-connect card.
Step 3 If the alarm persists and the reporting traffic card is the active card in the protection group, do a force switch to move traffic away from the card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Force and OK.
Step 4 Perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click to choose RESET CARD.
Step 5 If the alarm persists, physically reseat the reporting card.
Step 6 Clear the force switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Step 7 If the reporting traffic card is protect, perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 8 If the alarm persists, physically reseat the reporting card.
Step 9 If the alarm persists, replace the standby cross-connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 10 If the alarm persists, replace the reporting traffic card.
1.4.33 CTNEQPT-PBACT
•Critical, Service affecting
The interconnection equipment failure protect payload bus alarm indicates a failure in the main payload bus between the active cross-connect (XC/XCVT/XC10G) card in Slot 8 and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, or the backplane.
Note If all traffic cards show this alarm, do a forced side switch on the active TCC+ card, as shown in Step 1, and physically reseat this TCC+ card. If this fails to clear the alarm, replace the TCC+ card. Do not physically reseat an active TCC+ card; this disrupts traffic.
Note If CTNEQPT-PBACT is raised against all traffic cards on the shelf and SWMTXMOD, SD-L, AIS-L and RFI-L are also present, this could indicate a failed cross-connect card oscillator. Refer to the "Operation: Cross-Connect Card Oscillator Fails" section on page 2-31
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the CTNEQPT-PBACT Alarm
Step 1 Do a side switch from the active cross-connect (XC/XCVT/XC10G) card to the protect cross-connect card:
a. Determine the active cross-connect card. The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is yellow.
Note You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.
b. In the node view, select the Maintenance > XC Cards tabs.
c. Click Switch.
d. Click Yes on the Confirm Switch dialog box.
Note After the active cross-connect goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
Step 2 Perform a software reset on the reporting card:
a. From the node view, position the cursor over the slot reporting the alarm.
b. Right-click to choose RESET CARD.
Step 3 If the alarm persists, perform a card pull on the standby cross-connect card.
Step 4 If the alarm persists and the reporting traffic card is the active card in the protection group, do a force switch to move traffic away from the card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Force and OK.
Step 5 Perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click to choose RESET CARD.
Step 6 If the alarm persists, physically reseat the reporting card.
Step 7 Clear the force switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
Step 8 Click Clear and click YES at the confirmation dialog box.
Step 9 If the reporting traffic card is protect, perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click to choose RESET CARD.
Step 10 If the alarm persists, physically reseat the reporting card.
Step 11 If the alarm persists, replace the cross-connect card. First, ensure the card has been side switched from active to standby (Step 1):
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 12 If the alarm persists, replace the reporting traffic card.
1.4.34 DATAFLT
•Minor, Non-service affecting
The software fault data integrity fault alarm means the database exceeded the capacity of the flash memory on the TCC+.
Caution When the system reboots, the last configuration entered is not saved.
Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.35 DS3-MISM
•Not Alarmed (NA) (Condition)
The DS3 frame format mismatch indicates a frame format mismatch on the DS3-12E card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C-BIT for a DS3-12E card, and the incoming signal's frame format is detected as M23 or UNFRAMED, then the ONS 15454 reports a DS3-MISM alarm. The alarm is not raised when the line type is set to AUTO PROVISION or UNFRAMED.
The alarm or condition clears when the line type is set to AUTO PROVISION or UNFRAMED, the port state is set to OOS, or the correct frame format is set. Setting the line type to AUTO PROVIS ION causes the ONS 15454 to detect the received frame format and provision the port to use the matching frame format, either Unframed, M23 or C-bit.
Procedure: Clear the DS3-MISM
Step 1 Go to the CTC card-level view for the reporting DS3-12E.
Step 2 Click Provisioning > Line tabs.
Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal.
Step 4 If the Line Type pull-down column does not to match the expected incoming signal, select the correct Line Type on the pull down menu.
Step 5 Click Apply.
Step 6 If the alarm does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use a test set to verify that the actual signal coming into the ONS 15454 matches the expected incoming signal.
1.4.36 EOC
•Major, Non-service affecting
The termination failure SDCC alarm means the ONS 15454 has lost its data communications channel (DCC). The DCC is three bytes, D1 through D3, in the SONET overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P.) The ONS 15454 uses the DCC on the SONET section layer (SDCC) to communicate network management information.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the EOC Alarm
Step 1 If an LOS alarm is also reported, first resolve the LOS alarm by following the troubleshooting procedure given for that alarm.
Step 2 On the node reporting the alarm, check the physical connections from the cards to the fiber- optic cables that are configured to carry DCC traffic.
Step 3 Verify that both ends of the fiber span have in-service ports by checking that the ACT LED on each OC-N card is illuminated.
Step 4 Verify that the DCC is provisioned for the ports at both ends of the fiber span.
a. Under the node view, click the Provisioning > SONET DCC tabs.
b. If the slot and port are listed under SDCC Terminations, the DCC is provisioned.
c. If the slot and port are not listed under the SDCC Terminations, click Create.
d. Click the OC-N card that links to the adjacent node.
e. Click OK.
f. Repeat steps (a) - (e) at the adjacent nodes.
Step 5 Verify that the OC-N port is active and in-service:
a. Confirm that the OC-N card shows a green LED by viewing the CTC or viewing the physical card.
A green LED indicates an Active card. A yellow LED indicates a Standby card.
b. To determine whether the OC-N port is in In Service, double-click the card in the CTC to display the card-level view.
c. Click the Provisioning > Line tabs.
d. Verify that the Status column lists the port as In Service.
e. If the Status column lists the port as Out of Service, click the column and select In Service. Click Apply.
Step 6 With a test set, check for signal failures on fiber terminations.
Caution Using a test set will disrupt service on the OC-N card. It may be necessary to manually switch traffic carrying circuits over to a protection path.
Step 7 Measure power levels to verify that the budget loss is within the parameters of the receiver. See the "Optical Card Transmit and Receive Levels" section on page 2-43.
Step 8 Ensure that fiber connectors are securely fastened and properly terminated.
Step 9 Reset the active TCC+ using the "Card Replacement" section on page 3-19.
Resetting the active TCC+ switches the traffic to the standby TCC+. If the alarm clears when the ONS 15454 switches to the standby TCC+, the user can assume that the original active TCC+ is the cause of the alarm.
Step 10 Replace the original active TCC+ with a new TCC+ card.
Caution Resetting the active TCC+ can result in loss of traffic.
Step 11 Delete and recreate the problematic SDCC termination:
a. Click the Provisioning > SONET DCC tabs.
b. Highlight the problematic SDCC termination.
c. Click Delete.
d. Click Yes at confirmation dialog box.
Step 12 Verify that both ends of the SDCC have been recreated at the optical ports.
Step 13 Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.37 EQPT
•Critical, Service affecting
An equipment failure (EQPT) alarm indicates that a hardware failure has occurred on the reporting card.
If the EQPT alarm occurs with a BKUPMEMP alarm, follow the procedure "Clear the BKUPMEMP Alarm" section. This procedure will also clear the EQPT alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the EQPT Alarm
Step 1 Perform a software reset on the reporting card.
a. Display the CTC node view.
b. Position the CTC cursor over the slot reporting the alarm.
c. Right click RESET CARD.
Step 2 If the software reset fails to clear the alarm, physically reseat the card.
Step 3 If the physical reseat of the card fails to clear the alarm, replace the card.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
1.4.38 EQPT-MISS
•Critical, Service affecting
The rplaceable equipment unit is missing alarm is reported against the fan tray assembly unit. It indicates the replaceable fan tray assembly unit is missing or not fully inserted.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the EQPT-MISS Alarm
Step 1 If the alarm is reported against the fan object, check that the fan tray assembly is present.
Step 2 If the fan tray assembly is present, use the retractable handles embedded in the front of the fan tray to pull the fan tray assembly forward several inches and the push the fan tray assembly firmly back into the ONS 15454 shelf assembly and close the retractable handles.
Step 3 If no fan try assembly is present, obtain a fan tray assembly and refer to the fan tray assembly installation information in the Cisco ONS 15454 Installation and Operations Guide.
1.4.39 E-W-MISMATCH
•Major, Service affecting
A Procedural Error Misconnect East/West Direction alarm occurs when nodes in a ring have an east slot/port misconnected to another east slot/port or a west slot/port misconnected to another west slot/port. In most cases, the user did not hook up the fibers correctly, or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slot/ports 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 will clear the alarm, but may 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 slot/ports configured correctly. In this instance, the alarm clears itself shortly after the ring setup is complete.
Note The lower numbered slot on a node is traditionally labelled as the west slot and the higher numbered slot is labelled as the east slot. For example, Slot 6 is west and Slot 12 is east.
Procedure: 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 Display the CTC network view and label each of the nodes on the diagram with the same name that appears on the screen's network map.
Step 3 Double-click each span to reveal the node name/slot/port for each end of the span.
Step 4 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1 - Node2/Slot6/Port1 (2F BLSR OC48, Ring ID=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.
Step 5 Repeat Steps 3 and 4 for each span on your diagram.
Step 6 Label the highest slot at each node east and the lowest slot at each node west.
Step 7 Look at the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span.
Step 8 If any span has an east-to-east or west-to-west connection, physically switch the fiber connectors from the card that does not fit the pattern to the card that will continue the pattern. This should clear the alarm.
Note The above physical switch procedure is the recommend method of clearing this alarm. This method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slot/ports as east and west. This is useful when the misconnected node is not geographically near the troubleshooter.
Procedure: Clear the E-W-MISMATCH Alarm with the CTC
Step 1 Log into the misconnected node. This is the node with both ring fibers misconnected; it is in the middle of the two nodes that have one of two ring fibers misconnected.
Step 2 Click the Provisioning > Ring tabs.
Step 3 From the row of information for the fiber span, write down the Node ID, Ring ID, and the Slot and Port in the east line list and west line list.
Step 4 Click the row from Step 3 to select it and click Delete.
Step 5 Click Create.
Step 6 Fill in the Ring ID and Node ID from the information collected in Step 3.
Step 7 Change the West line pull-down menu to the slot/port you recorded for the East line in Step 3.
Step 8 Change the East line pull-down menu to the slot/port you recorded for the West line in Step 3.
Step 9 Click OK.
Step 10 Click Yes at the Ring Map Change dialog box.
Step 11 Click Accept at the new Ring Map.
1.4.40 EXCCOL
•Minor, Non-service affecting
The Excess Collisions on the LAN alarm indicates that too many collisions are occurring between data packets on the network management LAN, and communications between the ONS 15454 unit and the CTC may be affected.The network management LAN is the data network connecting the workstation running the CTC software to the TCC+ card. This problem is external to the ONS 15454.
Procedure: Clear the EXCCOL Alarm
Troubleshoot the network management LAN connected to the TCC+ card for excess collisions. You may need to contact the system administrator of the network management LAN to accomplish the following steps:
Step 1 Verify that the network device port connected to the TCC+ card has a flow rate set to 10 Mb, half-duplex.
Step 2 Troubleshoot the network device connected to the TCC+ card and the network management LAN.
1.4.41 EXERCISE-RING-FAIL
•Not Alarmed (NA) (Condition)
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.
Procedure: Clear the EXERCISE-RING-FAIL Condition
Step 1 Check for any LOS, LOF or BLSR service affecting alarms.
Step 2 Lookup and troubleshoot any of these alarms, then reissue the Exercise-Ring command.
1.4.42 EXERCISE-SPAN-FAIL
•Not Alarmed (NA) (Condition)
The Exercise Span command issues span switching of the requested channel without completing the actual bridge and switch. The EXERCISE-SPAN-FAILED alarm 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 span, EXERCISE-SPAN-FAIL will not be reported.
Procedure: Clear the EXERCISE-SPAN-FAIL Condition
Step 1 Check for any LOS, LOF or BLSR service affecting alarms.
Step 2 Lookup and troubleshoot any of these alarms, then reissue the Exercise Span command.
1.4.43 EXT
•Minor, Service affecting
An external facility alarm is detected external to the node because an environmental alarm is present, for example, a door is open or flooding has occurred.
Procedure: Clear the EXT Alarm
Step 1 Open the AIC card maintenance screen to gather further information about this alarm.
Step 2 Perform your standard operating procedure for this environmental condition.
1.4.44 FAILTOSW
•Not Alarmed (NA) (Condition)
The FAILTOSW alarm is raised when a working DS-N card cannot switch to the protect card in a 1:N protection group, because another working DS-N card, with a higher-priority alarm, is switched over and monopolizing the lone protect card.
Procedure: Clear the FAILTOSW Alarm
Step 1 Lookup and troubleshoot the higher-priority alarm. Clearing this alarm will free up the 1:N card and clear the FAILTOSW.
Note A higher-priority alarm is an alarm raised on the working DS-N card using the 1:N card protection group. This working DS-N card is reporting an alarm, but not reporting a FAILTOSW alarm.
Step 2 Replace the working DS-N card that is reporting the higher-priority alarm. This card is the working DS-N card using the DS:N card protection and not reporting FAILTOSW.
Replacing the working DS-N card reporting the higher-priority alarm, will allow traffic to revert back to this slot. This frees up the 1:N card, which can then take over traffic from the card reporting the lower-priority alarm and the FAILTOSW alarm.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.45 FAILTOSW-PATH
•Not Alarmed (NA) (Condition)
The fail to switch path means the working path did not switch to the protection path on a UPSR. Common causes of this alarm include a missing or defective protection card or a lockout set on one of the UPSR nodes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the FAILTOSW-PATH on a UPSR Configuration
Step 1 Ensure that a lockout is not set on the UPSR:
a. Display the CTC network view.
b. Right-click the span (the line between the nodes).
c. Click Circuits.
d. Under Switch State, confirm that Clear appears.
e. If Clear does appear, perform Steps a - d at the next span.
f. If Clear still does not appear, click the Switch all UPSR- circuits away menu.
g. Choose Clear and click Apply.
h. Click Yes at the Confirm UPSR Switch Are You Sure? dialog box.
i. Click OK at the next dialog box.
Step 2 Check the fiber connections to ensure they are securely fastened and intact.
Step 3 Ensure the OC-N cards are active and in-service.
Step 4 Verify that the protect OC-N card paired with the active reporting OC-N card is the same type and in-service.
Step 5 If the alarm persists and the reporting traffic card is active, do a manual switch to move traffic away from the card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Manual and OK.
Step 6 Perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click to choose RESET CARD.
d. If the alarm persists, physically reseat the reporting card.
Step 7 If the traffic does not switch over, right-click on the protect card and click Reset.
Step 8 Attempt another manual switch after the protect cards have booted up completely.
Step 9 If you are still unable to perform a switch, reseat the protect card.
Step 10 Attempt another manual switch.
Step 11 Clear the manual switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Step 12 If the alarm persists, replace the protect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 13 Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.46 FAILTOSWR
•Not Alarmed (NA) (Condition)
This fail to switch ring signals an automatic protection switching (APS) ring switch failure. FAILTOSWR clears when one of the following actions occurs: a higher priority event, such as a user-switch command occurs, the next ring switch succeeds, or the cause of the APS switch (such as an SF or SD alarm) clears.
Warning On the OC-192 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 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 100 mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.
Procedure: Clear the FAILTOSWR on a Four-Fiber BLSR Configuration
Step 1 Check to see that every node expected to be part of the ring is listed in the ring map:
a. Click the Provisioning > Ring tabs.
b. Highlight the row of the affected ring.
c. Click Ring Map.
d. Verify that a Node ID appears in the Ring Map for every node expected to be part of the ring.
Step 2 Display the CTC network view.
Step 3 Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.
Step 4 Log into the near-end node and click the Ring > Provisioning tabs.
Step 5 Record the OC-N cards listed under West Line and East Line. Ensure these OC-N cards are active and in-service.
Step 6 Verify fiber continuity to the ports on the recorded cards.
Step 7 Verify that the correct port is in-service.
Caution Using a test set will disrupt service on the optical card. It may be necessary to manually switch traffic carrying circuits over to a protection path.
Step 8 Use an optical test set to verify that a valid signal exists on the line.
Test the line as close to the receiving card as possible.
Step 9 Clean the fiber:
a. Clean fiber 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.
Step 10 Verify that the power level of the optical signal is within the OC-N card's receiver specifications. The "Optical Card Transmit and Receive Levels" section on page 2-43 lists these specifications.
Step 11 Repeat Steps 1 - 5 for any other ports on the card.
Step 12 Replace the protect standby OC-N card.
Step 13 If the alarm does not clear after you replace the BLSR cards on this node one by one, follow Steps 4 - 14 for each of the nodes in the ring.
Step 14 Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.47 FAILTOSWS
•Not Alarmed (NA) (Condition)
This failure to switch to protection span signals an APS span switch failure. For four-fiber BLSR, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS alarm will not appear. If the ring switch does not occur, the FAILTOSWS alarm appears. FAILTOSWS clears when one of the following actions occur: a higher priority event, such as a user-switch command occurs, the next ring switch succeeds, or the cause of the APS switch (such as an SF or SD alarm) clears.
Follow the procedure for "Clear the FAILTOSWR on a Four-Fiber BLSR Configuration" section.
1.4.48 FAN
•Critical, Service affecting
The failure of the cooling fan tray alarm indicates a problem with the fan-tray assembly. When the fan is not fully functional, the temperature of the ONS 15454 can rise above its normal operating range. The fan tray contains six fans and needs a minimum of five working fans to properly cool the ONS 15454. However, even with five working fans, the fan tray can need replacement because a sixth working fan is required for extra protection against overheating.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the FAN Alarm
Step 1 Check the condition of the air filter to see if it needs replacement.
Step 2 If the filter is clean, take the fan-tray assembly out of the ONS 15454.
Step 3 Reinsert the fan tray making sure the back of the fan tray connects to the rear of the ONS 15454.
Note The fan should run immediately when correctly inserted.
Step 4 If the fan does not run or the alarm persists, replace the fan tray.
Step 5 If the replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.49 FE-AIS
•Not Alarmed (NA) (Condition)
The far end ais alarm means the far-end node's DS3XM-6 or DS3-12E card is reporting an alarm indication signal (AIS). The prefix FE in an alarm message means the main alarm is occurring at the far-end node and not at the node reporting this FE-AIS alarm. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. Both the alarms clear when the main alarm clears.
Procedure: Clear the FE-AIS Condition
Step 1 To troubleshoot an FE alarm, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS alarm from the DS3XM-6 card in Slot 12 of Node 1 may link to the main AIS alarm from an DS3XM-6 card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE alarm.
Step 3 Clear the main alarm.
1.4.50 FE-DS1-MULTLOS
•Not Alarmed (NA) (Condition)
The far end multiple DS1 LOS detected on DS3XM-6 condition means multiple inputs detect a loss on the far end. The prefix FE in an alarm/condition message means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-MULTOS alarm. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarm/conditons clear when the main alarm clears.
Procedure: Clear the FE-DS1-MULTLOS Condition
Step 1 To troubleshoot an FE condition/alarm, 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 may link to the main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition/alarm.
Step 3 Look up and troubleshoot the main alarm.
1.4.51 FE-DS1-SNGLLOS
•Not Alarmed (NA) (Condition)
The far end single DS1 LOS on the DS3XM-6 condition means one of the DS1-14 inputs on the far end detects an LOS. The prefix FE in an alarm/condition means the main alarm is occurring at the far-end node and not at the node reporting this FE-EQPT-FAILSA alarm. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.
Procedure: Clear the FE-DS1-SNGLLOS Condition
Step 1 To troubleshoot an FE alarm/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 may link to the main alarm from a card in Slot 6 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.
1.4.52 FE-DS3-SA
•Not Alarmed (NA) (Condition)
The far end DS3 equipment failure service affecting alarm means a far-end DS-3 equipment failure is occurring. The prefix FE in an alarm/condition means the main alarm is occurring at the far-end node and not at the node reporting the FE alarm. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. Both alarm/coditions clear when the main alarm clears.
Procedure: Clear the FE-DS3-SA Condition
Step 1 To troubleshoot an FE alarm/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 may link to the main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE alarm/condition.
Step 3 Clear the main alarm.
1.4.53 FE-EQPT-NSA
•Not Alarmed (NA) (Condition)
The far end common equipment failure non service affecting condition means a non-service affecting equipment failure is detected in the far-end DS-3. The prefix FE in an alarm/condition message means that the main alarm is occurring at the far-end node, not the node reporting this FE-EQPT-NSA alarm. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the FE-EQPT-NSA Condition
Step 1 To troubleshoot an FE alarm/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 may link to the main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE alarm/condition.
Step 3 Look up and troubleshoot the main alarm.
1.4.54 FE-IDLE
•Not Alarmed (NA) (Condition)
The far end idle condition means a far-end node detects an idle DS-3 signal. The prefix FE in an alarm/condition means that the main alarm is occurring at the far-end node, not the node reporting this FE-IDLE alarm. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarms clear when the main alarm clears.
Procedure: Clear the FE-IDLE Condition
Step 1 To troubleshoot the FE alarm/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 may link to the main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE alarm/condition.
Step 3 Clear the main alarm.
1.4.55 FE-LOCKOUT
•Not Alarmed (NA) (Condition)
The far end lockout condition raises whenever the Lockout Protection Span command is entered from any other node. This alarm indicates the prevention of any ring switch requests. The alarm clears when the lock out is removed.
Procedure: Clear the FE-LOCKOUT Condition on a BLSR
Step 1 Display CTC network view.
Step 2 Find the node reporting the LOCKOUT-REQ.
Step 3 Log into the node reporting the LOCKOUT-REQ.
Step 4 Follow the "Clear the Lockout Switch Request and the LOCKOUT-REQ Condition" procedure.
1.4.56 FE-LOF
•Not Alarmed (NA) (Condition)
The far end LOF condition means a far-end node reports a DS-3 loss of frame (LOF). The prefix FE in an alarm/condition means that the main alarm is occurring at the far-end node, not the node reporting this FE-LOF alarm. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.
Procedure: Clear the FE-LOF Condition
Step 1 To troubleshoot an FE alarm/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 may link to the main alarm from a card in Slot 6 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.
1.4.57 FE-LOS
•Not Alarmed (NA) (Condition)
The far end LOS condition means a far-end node reports a DS-3 loss of signal (LOS). The prefix FE in an alarm/condition message means that the main alarm is occurring at the far-end node, and not at the node reporting this FE-LOS alarm. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.
Procedure: Clear the FE-LOS Condition
Step 1 To troubleshoot the FE alarm/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 may link to the main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE alarm.
Step 3 Clear the main alarm.
1.4.58 FEPRLF
•Minor, Non-service affecting
The far end protection line failure alarm means that there was an APS switching channel failure of signal on the protect card coming into the node.
Note The FEPRLF alarm only occurs on the ONS 15454 when 1+1 bidirectional protection is used on optical cards in a 1+1 configuration.
Procedure: Clear the FEPRLF Alarm on a Four-Fiber BLSR
Step 1 To troubleshoot the FE alarm, 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 may link to the main alarm from a card in Slot 6 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.
1.4.59 FORCED-REQ
•Not Alarmed (NA) (Condition)
The force switch request on facility or equipment alarm means a user entered the force command on a span or card to force traffic from a working card or working span to a protection card or protection span or vice versa. You do not need to clear this alarm if you want the force switch to remain in place. To clear this alarm, clear the force command.
Procedure: Clear the FORCED-REQ
Step 1 Click the Maintenance tab.
Step 2 Click the Protection tab for a card or span switch.
Step 3 At Operation, click the drop-down arrow.
Step 4 Choose Clear and click Apply.
1.4.60 FRNGSYNC
•Major, Service affecting
The free running synchronization mode alarm means the reporting ONS 15454 is in free run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the ONS 15454 has lost its designated BITS timing source. After the 24-hour holdover period expires, timing slips may begin to occur on an ONS 15454 relying on an internal clock.
Procedure: Clear the FRNGSYNC Alarm
Step 1 If the ONS 15454 is configured to operate from its own internal clock, disregard this alarm.
Step 2 If the ONS 15454 is configured to operate off an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards.
Step 3 Find and troubleshoot alarms related to the failures of the primary and secondary reference sources, such as SYNCPRI and SYNCSEC.
1.4.61 FSTSYNC
•Minor, Non-service affecting
A Fast Start Synchronization mode alarm raises when the ONS 15454 is choosing a new timing reference. The previous timing reference has failed. This alarm disappears after approximately 30 seconds.
Note This is an informational alarm.
1.4.62 HITEMP
•Critical, Service affecting (NE)
•Minor, Non service affecting (EQPT)
The equipment failure high temperature alarm means the temperature of the ONS 15454 is above 50 degrees Celsius (122 degrees Fahrenheit).
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the HITEMP Alarm
Step 1 Check the temperature of the ONS 15454 on the front panel LCD.
Step 2 Check that the temperature of the room is not abnormally high.
Step 3 Ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454.
Step 4 Ensure that blank faceplates fill the ONS 15454 empty slots. Blank faceplates help airflow.
Step 5 Check the condition of the air filter to see if it needs replacement.
Step 6 If the filter is clean, take the fan-tray assembly out of the ONS 15454.
Step 7 Reinsert the fan tray, making sure the back of the fan tray connects to the rear of the ONS 15454.
Note The fan should run immediately when correctly inserted.
Step 8 If the fan does not run or the alarm persists, replace the fan tray.
Step 9 If the replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.63 HLDOVERSYNC
•Major, Service affecting
Loss of the primary/secondary timing reference raises the holdover synchronization mode alarm. Timing reference loss occurs when line coding on the timing input is different than the configuration on the ONS 15454. It also usually occurs during the selection of a new node reference clock. This alarm indicates that the ONS 15454 has gone into holdover and is using the ONS 15454 internal reference clock, which is a Stratum 3-level timing device. The alarm clears when primary or secondary timing is reestablished.
Procedure: Clear the HLDOVERSYNC Alarm
Step 1 Check for additional alarms that relate to timing.
Step 2 Reestablish a primary and secondary timing source according to local site practice.
1.4.64 IMPROPRMVL
•Critical, Service-affecting
The procedural error improper removal alarm means a card was physically removed from its slot before the card was deleted in CTC. The card does not need to be in-service to cause this alarm, it only needs to be recognized by CTC and the TCC+ card. This alarm does not appear if you delete the card from CTC before you physically remove the card from the node.
Note CTC gives the user approximately 15 seconds to physically remove the card before the CTC begins a card reboot.
Caution Do not pull 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 electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the IMPROPRMVL Alarm
Step 1 Right-click the card reporting the IMPROPRMVL.
Step 2 Choose Delete.
Note CTC will not allow you to delete this card if the card is in-service, has a circuit mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.
Step 3 If the card is in-service, take the facility out of service:
Caution Before taking the facility out of service, ensure that no live traffic is present on the facility.
a. In CTC, double-click the reporting card to display the card view.
b. Click the Provisioning tab.
c. Click the Status of any in-service ports.
d. Choose Out of Service to take the ports out of service.
Step 4 If a circuit has been mapped to the card, delete the circuit:
Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.
a. At the node view, click the Circuits tab.
b. Click the applicable circuit, i.e., the circuit that connects to the reporting card.
c. Click Delete.
Step 5 If the card is paired in a protection scheme, delete the protection group:
a. Click the Provisioning > Protection tabs.
b. Click the protection group of the reporting card.
c. Click Delete.
Step 6 If the card is provisioned for DCC, delete the DCC provisioning:
a. Click the SONET DCC > Provisioning tabs.
b. Click the slots and ports listed in SDCC Terminations.
c. Click Delete and click Yes in the dialog box that appears.
Step 7 If the card is used as a timing reference, change the timing reference:
a. Click the Provisioning > Timing tabs.
b. Click the Ref-1 menu.
c. Change Ref-1 from the listed OC-N card to Internal Clock.
d. Click Apply.
Step 8 Right-click the card reporting the IMPROPRMVL and choose Delete.
1.4.65 INCOMPATIBLE-SW
•Minor, Non-service affecting
The incompatible software alarm means the CTC software version loaded on the connecting workstation and the CTC software version loaded on the TCC+ card are incompatible. This occurs when the TCC+ software is upgraded but the PC has not yet upgraded the compatible CTC jar file. INCOMPATIBLE-SW also occurs when CTC logs into a node with compatible software but encounters another node in the network that has a newer version of CTC.
Procedure: Clear the INCOMPATIBLE-SW Alarm
Step 1 Exit the current CTC session and completely close the browser.
Step 2 Start the browser.
Step 3 Type the ONS 15454 IP address of the node that reported the alarm. This can be the original IP address you logged on with or an IP address other than the original.
Step 4 Log into CTC. The browser will download the jar file from CTC.
1.4.66 INVMACADDR
•Major, Non-service affecting
The equipment failure invalid MAC address alarm means the ONS 15454 Media Access Control layer address (MAC Address) is invalid. The MAC Address is permanently set into the ONS 15454 chassis when it is manufactured. Do not attempt to troubleshoot an INVMACADDR. Contact the Cisco Technical Assistance Center (TAC) at (1-800-553-2447).
Procedure: Clear the INVMACADDR Alarm
This is not a user-serviceable problem. Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.67 LOCKOUT-REQ
•Not Alarmed (NA) (Condition)
The Lockout Switch Request on Facility/Equipment alarm occurs when a user initiates a lockout switch request for an OC-N card or a lockout switch request on a UPSR at the path level. A lockout prevents protection switching from occurring. Clearing the lockout will again allow protection switching to take place. Clearing the lockout switch request clears the LOCKOUT-REQ alarm. This is an informational alarm.
Procedure: Clear the Lockout Switch Request and the LOCKOUT-REQ Condition
Step 1 Display the CTC network view.
Step 2 Click Circuits tab and highlight the circuit.
Step 3 Click Edit and click the UPSR tab.
Step 4 From the Switch State menu, highlight Clear.
Step 5 Click Apply and click Close.
1.4.68 LOF (BITS)
•Major, Service affecting
The loss of frame alarm means a port on the TCC+ BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data.
Note The procedure assumes that the BITS timing reference signal is functioning properly. It also assumes the alarm is not appearing during node turn-up.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOF Alarm
Step 1 Verify that the line framing and line coding match between the BITS input and the TCC+:
a. In CTC node view or card view, note the slot and port reporting the alarm.
b. 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 timing source itself.
c. Click the Provisioning > Timing tabs to display the General Timing screen.
d. Verify that Coding matches the coding of the BITS timing source (either B8ZS or AMI).
e. If the coding does not match, click Coding to reveal a menu. Choose the appropriate coding.
f. Verify that Framing matches the framing of the BITS timing source (either ESF or SF [D4]).
g. If the framing does not match, click Framing to reveal the menu. Choose the appropriate framing.
Note On the timing subtab, the B8ZS coding field is normally paired with ESF in the Framing field, and the AMI coding field is normally paired with SF (D4) in the Framing field.
Step 2 If the alarm does not clear when the line framing and line coding match between the BITS input and the TCC+, replace the TCC+ card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.69 LOF (DS1)
•Major, Service affecting
The loss of frame alarm indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. If the LOF appears on the DS1-14 card, the transmitting equipment may have its framing set to a format that differs from the receiving ONS 15454.
Procedure: Clear the LOF Alarm
Step 1 Verify that the line framing and line coding match between the DS1-14 port and the signal source.
a. In CTC, note the slot and port reporting the alarm.
b. Find the coding and framing formats of the signal source for the card reporting the alarm. You may need to contact your network administrator for this information.
c. Display the card-level view of the reporting card.
d. Click the Provisioning > Line tabs.
e. Verify that the line type of the reporting port matches the line type of the signal source.
f. If the signal source line type does not match the reporting port, click Line Type to reveal a menu. Choose the matching type.
g. Verify that the reporting Line Coding matches the signal source's Line Type.
h. If the signal source line coding does not match the reporting port, click Line Coding to reveal the menu. Choose the matching type and click Apply.
Note On the Line tab, the B8ZS coding field is normally paired with ESF in the Framing field. AMI coding is normally paired with SF (D4) in the Framing field.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.70 LOF (DS3)
•Critical, Service affecting
The loss of frame alarm indicates that the receiving ONS 15454 lost frame delineation in the incoming data. The framing of the transmitting equipment may be set to a format that differs from the receiving ONS 15454. On DS3-12E cards, the alarm occurs only on cards with the provisionable framing format set to C-bit or M23, not on cards with the provisionable framing format is set to unframed.
Procedure: Clear the LOF Alarm
Step 1 Change the line type of the non-ONS equipment attached to the reporting card to C-bit.
1.4.71 LOF (EC1-12)
•Critical, Service affecting
The loss of frame alarm means a port on the reporting EC1-12 card has a LOF condition. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.
LOF on an EC1-12 card is sometimes an indication that the EC1-12 card 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.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOF Alarm
Step 1 The LOF should trigger an automatic protection switch away from the working card that reported the alarm. If it did not, do a manual switch to move traffic away from the reporting card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Manual and OK.
Step 2 Clear the manual switch:
a. At the node view, click the Maintenance >Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Note If you do not have a protect card for the reporting card, create a new circuit on the reporting card to achieve the same effect.
Step 3 If you still receive the LOF alarm, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.72 LOF (OC-N)
•Critical, Service affecting
The loss of frame alarm means a port on the reporting OC-N card has an LOF condition. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.
LOF on an OC-N card is sometimes an indication that the OC-N card 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.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOF Alarm
Step 1 The LOF should trigger an automatic protection switch away from the working card that reported the alarm. If it did not, do a manual switch to move traffic away from the reporting card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Manual and OK.
Note If you do not have a protect card for the reporting card, create a new circuit on the reporting card to achieve the same effect.
Step 2 Clear the manual switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Step 3 Verify that the OC-N port on the upstream node is in-service.
Step 4 If you continue to receive the LOF alarm, see the "Faulty Fiber-Optic Connections" section on page 2-38.
1.4.73 LOGBUFR90
•Major, Service affecting
The log buffer 90% full alarm means that the memory buffer holding the alarms seen on the Alarms pane in CTC is 90% full. If the buffer continues to fill, a LOGBUFROVFL alarm is reported. The LOGBUFROVFL alarm means the memory buffer is full, and any new alarms occurring on the ONS 15454 will not display on the CTC alarms pane. The CTC receives alarms from all ONS nodes on the network, even if the CTC is set to the node or card level view.
Procedure: Clear the LOGBUFR90 Alarm
Step 1 Click the close button on the upper right corner of the CTC screen.
Step 2 Click the close button on the upper right corner of the browser screen.
Step 3 Log back into the ONS 15454. The LOGBUFR90 alarm should clear after an approximately one minute delay.
Exiting CTC and logging back into the ONS 15454 removes any cleared alarms from the log buffer and resynchronizes the alarm pane to show any alarms that were not displayed as a result of a full log buffer.
Note Checking the AutoDelete Cleared Alarms checkbox on the Alarms panel helps prevent log buffer overflow.
1.4.74 LOGBUFROVFL
•Major, Service affecting
The log buffer overflow alarm means the memory buffer is full, and any new alarms occurring on the ONS 15454 will not display on the CTC alarms pane. The CTC receives alarms from all ONS nodes on the network, even if the CTC is set to the node or card level view.
Procedure: Clear the LOGBUFROVFL Alarm
Step 1 Click the close button on the upper right corner of the CTC screen.
Step 2 Click the close button on the upper right corner of the browser screen.
Step 3 Log back into the ONS 15454. The LOGBUFROVFL alarm should clear after an approximately one minute delay.
Exiting CTC and logging back into the ONS 15454 removes any cleared alarms from the log buffer and resynchronizes the alarm pane to show any alarms not displayed as a result of a full log buffer.
Note Checking the AutoDelete Cleared Alarms checkbox on the Alarms panel helps prevent log buffer overflow.
1.4.75 LOP-P
•Critical, Service affecting
This loss of pointer path alarm indicates a loss of pointer (LOP) at the path level. LOP occurs when valid H1/H2 pointer bytes are missing from the SONET overhead. Receiving equipment monitors the H1/H2 pointer bytes to locate the SONET payload. A 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 STSc circuit that is smaller than the provisioned STSc. This condition causes a mismatch of the circuit type on the concatenation facility. For example, if an STS-3c or STS-1 is sent across a circuit provisioned for STS-12c, a LOP alarm occurs.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOP-P Alarm
Step 1 Verify the cabling and physical connections on the reporting card.
Step 2 Perform a soft reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click to choose RESET CARD.
Step 3 Do a manual switch (side switch) to move traffic away from the card.
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Manual and OK.
Note If you do not have a protect card for the reporting card, create a new circuit on the reporting card to achieve the same effect.
Step 4 Clear the manual switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Step 5 If the alarm persists, the problem is at the far-end node. Verify the stability of the cabling and physical connections that connect to the far-end card.
Step 6 Do a soft reset on the far-end card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 7 Perform a soft reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 8 Switch from the far-end working card to the far-end protect card.
Step 9 If the alarm persists, replace the far-end card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.76 LOP-V
•Major, Service affecting
The loss of pointer VT alarm indicates a loss of pointer at the VT level. The VT, or electrical, layer occurs when the SONET signal is broken down into an electrical signal, for example, when an optical signal comes into an ONS 15454. The ONS 15454 demultiplexes this optical signal. One of the channels separated from the optical signal cross connects into a ONS 15454 DS3XM-6 or DS1-14 port. The ONS 15454 reports the LOS-V alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOP-V Alarm
Step 1 Verify the stability of the cabling and physical connections on the reporting card.
Step 2 Perform a software reset on the reporting card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 3 Do a manual switch to move traffic away from the card:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Click the Protect/Standby card of the selected groups.
d. Click Manual and OK.
Note If you do not have a protect card for the reporting card, create a new circuit on the reporting card to achieve the same effect.
Step 4 Clear the manual switch:
a. At the node view, click the Maintenance > Protection tabs.
b. Double-click the protection group that contains the reporting card.
c. Highlight either selected group.
d. Click Clear and click YES at the confirmation dialog box.
Step 5 If the alarm persists, the problem is at the far-end node. Verify the cabling and physical connections that connect to the far-end card.
Step 6 Do a soft reset on the far-end card.
Step 7 Switch from the far-end working card to the far-end protect card.
1.4.77 LOS (BITS)
•Major, Service affecting
The TCC+ card has a loss of signal (LOS) from the BITS timing source. An LOS occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (BITS-N) means the BITS clock or the connection to the BITS clock failed.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOS Alarm
Step 1 Verify the wiring connection from the ONS 15454 backplane BITS clock pin fields to the timing source.
Step 2 Check that the BITS clock is operating properly.
1.4.78 LOS (DS-N)
•Critical, Service affecting
This alarm indicates a loss of signal (LOS) at the card for either a DS-3 port or a DS1-14 port. LOS occurs when the port on the card is in-service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure or a fiber cut.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOS Alarm
Step 1 Verify cabling continuity to the port.
Step 2 Verify that the correct port is in-service.
Step 3 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible.
Step 4 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.
Step 5 If there is a valid signal, replace the DS-N connector on the ONS 15454.
Step 6 Repeat Steps 1 - 5 for another port on the card.
Step 7 Look for another alarm that may identify the source of the problem.
Step 8 Replace the reporting card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.79 LOS (EC1-12)
•Critical, Service affecting
A port on the reporting EC1-12 card has a loss of signal (LOS) condition. An LOS occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS means the upstream transmitter has failed. If an EC1-12 LOS alarm is not accompanied by additional alarms, a fiber break or cabling problem is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOS Alarm
Step 1 Verify cabling continuity to the port.
Step 2 Verify that the correct port is in-service.
Step 3 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible.
Step 4 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.
Step 5 If there is a valid signal, replace the cable connector on the ONS 15454.
Step 6 Repeat Steps 1 - 5 for another port on the card.
Step 7 Look for another alarm that may identify the source of the problem.
Step 8 Replace the reporting card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.80 LOS (OC-N)
•Critical, Service affecting
A port on the reporting OC-N card has a loss of signal (LOS) condition. An LOS occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS means the upstream transmitter has failed. If an OC-N LOS alarm is not accompanied by additional alarms, a fiber break is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the LOS Alarm
Step 1 Verify fiber continuity to the port.
Step 2 Verify that the correct port is in-service.
Step 3 Use an optical test set to verify that a valid signal exists on the line.
Test the line as close to the receiving card as possible.
Step 4 Clean the fiber:
a. Clean fiber 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.
Step 5 Verify that the power level of the optical signal is within the OC-N card's receiver specifications. The "Optical Card Transmit and Receive Levels" section on page 2-43 lists these specifications for each card.
Step 6 If there is a valid signal, replace the connector on the backplane.
Step 7 Repeat Steps 1 - 5 for another port on the card.
Step 8 Replace the OC-N card.
1.4.81 LPBKDS1FEAC
•Not Alarmed (NA) (Condition)
A loopback due to FEAC command DS1 condition on the DS3XM-6 card means a DS-1 loopback signal is received from the far-end node due to a Far-End Alarm and Control (FEAC) command. An FEAC command is often used with loopbacks.
Loopback is a commonly used troubleshooting technique. A signal is sent out on a link or part 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 or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically narrow down the source of the problem. For more information about loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
Caution The CTC permits loopbacks on an in-service circuit. This operation is service affecting.
Note This is an informational alarm.
1.4.82 LPBKDS3FEAC
•Not Alarmed (NA) (Condition)
A loopback due to FEAC command DS3 condition means a DS-3 loopback signal is received from the far-end node because of a Far-End Alarm and Control (FEAC) command. An FEAC command is often used with loopbacks. This condition is only reported by DS3-12E or DS3XM-6 cards. A DS3XM-6 card both generates and reports FEAC alarm/conditions, but a DS3-12E card only reports FEAC alarms/conditions.
Loopback is a commonly used troubleshooting technique. A signal is sent out on a link or part 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 or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically narrow down the source of the problem. For more information about loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
Caution The CTC permits loopbacks on an in-service circuit. This operation is service affecting.
Note This is an informational alarm.
1.4.83 LPBKFACILITY (DS-N or EC1-12)
•Not Alarmed (NA) (Condition)
A loopback facility alarm means a software facility loopback is active for a port on the reporting card.
Loopback is a commonly used troubleshooting technique. A signal is sent out on a link or part 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 or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically narrow down the source of the problem. For more information on loopbacks, see "Network Troubleshooting Tests" section on page 2-1.
There are two types of loopbacks: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far-end equipment. You can provision loopbacks through CTC.
Caution The CTC permits loopbacks to be performed on an in-service circuit. This operation is service affecting.
Note DS3XM-6 cards only support facility loopbacks on DS-1 circuits.
Procedure: Clear the LBKFACILITY Condition
Step 1 Double-click the reporting card in CTC or right-click the reporting card in CTC and choose Open from the menu.
Step 2 Click the Maintenance tab.
a. If the condition is reported against a DS3XM-6 card, also click the DS1 tab.
b. If a Loopback Type column cell that displays Facility (Line) is not shown under the DS1 tab, then click the DS3 tab to reveal a Loopback Type column cell that displays Facility (Line).
Step 3 Click the Loopback Type column cell that displays Facility (Line).
Step 4 Click None, and click Apply.
1.4.84 LPBKFACILITY (OC-N)
•Not Alarmed (NA) (Condition)
A loopback facility alarm means a software facility loopback is active for a port on the reporting card.
Loopback is a commonly-used troubleshooting technique. A signal is sent out on a link or part 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 or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically isolate the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
Two types of loopbacks are available: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far end equipment. You provision loopbacks using CTC.
Caution Before performing a facility loopback on an OC-N card, make sure there is another SDCC path to the ONS 15454 containing the OC-N card being put in loopback. A second SDCC path is necessary so you have a non-looped back path to log into the ONS 15454 containing the OC-N card being put in loopback and remove the facility loopback. This is not necessary if you are directly connected to the ONS 15454 with the OC-N card in facility loopback.
Procedure: Clear the LBKFACILITY Condition
Step 1 To remove the loopback alarm, double-click or right-click on the reporting card in the CTC. Choose Open from the list of options.
Step 2 Click the Maintenance tab.
Step 3 Click the Loopback Type column and choose None from the menu.
Step 4 Click Apply.
1.4.85 LPBKTERMINAL (DS-N, EC1-12)
•Not Alarmed (NA) (Condition)
A loopback terminal alarm means a software facility loopback is active for a port on the reporting card.
Loopback is a commonly-used troubleshooting technique. A signal is sent out on a suspect link or part of the network, and a signal comes back to the sending device. If the signal does not come back or returns with errors, the test confirms that the problem is present in the tested link or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically isolate the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
Two types of loopbacks are available: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far end equipment. You provision loopbacks using CTC.
Note Terminal loopback is not supported at the DS1 level for the DS3XM-6 card.
Procedure: Clear the LBKTERMINAL Condition
Step 1 To remove the loopback alarm, double-click or right-click on the reporting card in the CTC. Choose Open from the list of options.
Step 2 Click the Maintenance tab.
Step 3 Click the Loopback Type column and choose None from the menu.
Step 4 Click Apply.
1.4.86 LPBKTERMINAL ( G1000-4)
•Not Alarmed (NA) (Condition)
A loopback terminal alarm means a software terminal loopback is active for a port on the reporting card.
Loopback is a commonly used troubleshooting technique. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter logically isolates the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
When a port is set in terminal loopback the outgoing signal being transmitted is fed back into the receive direction on the same port and the externally received signal is ignored. On the G1000-4 card the outgoing signal is not transmitted; it is only fed back to the receive direction. G1000-4 cards only support Terminal loopbacks. Terminal loopbacks test ports and spans and are often used for remote sites or far-end equipment. Loopbacks are provisioned using CTC. CTC permits loopbacks on an in-service circuit. This operation is service affecting.
Procedure: Clear the LPBKTERMINAL Condition
Step 1 To remove the loopback alarm, double-click the reporting card in CTC, or right-click the reporting card and choose Open from the list of options.
Step 2 Click the Maintenance tab.
Step 3 Choose the Loopback Type column and choose None from the menu.
Step 4 Click Apply.
1.4.87 LPBKTERMINAL (OC-N)
•Not Alarmed (NA) (Condition)
A loopback terminal alarm means a software facility loopback is active for a port on the reporting card.
Loopback is a commonly-used troubleshooting technique. A signal is sent out on a suspect link or part 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 or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically isolate the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.
Two types of loopbacks are available: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far end equipment. You provision loopbacks using CTC.
Procedure: Clear the LBKTERMINAL Condition
Step 1 To remove the loopback alarm, double-click or right-click on the reporting card in the CTC. Choose Open from the list of options.
Step 2 Click the Maintenance tab.
Step 3 Click the Loopback Type column and choose None from the menu.
Step 4 Click Apply.
1.4.88 MAN-REQ
•Not Alarmed (NA) (Condition)
The Manual Switch Request on a Facility/Equipment alarm occurs when a user initiates a manual switch request on an OC-N card or UPSR path. Clearing the manual switch clears the MANUAL-REQ alarm.
Procedure: Clear the Manual Switch and the MAN-REQ Condition
Step 1 From network view, click the Circuits tab.
Step 2 Highlight the circuit.
Step 3 Click Edit and click the UPSR tab.
Step 4 From the Switch State menu, highlight Clear.
Step 5 Click Apply and click Close.
1.4.89 MANRESET
•Not Alarmed (NA) (Condition)
A maual system reset condition means a user performed a manual system reset by right-clicking a card and chose Reset. Resets performed during a software upgrade also prompt the alarm. This condition clears automatically, when the card finishes resetting.
1.4.90 MEA (AIP)
•Critical, Service affecting
If the mismatch between entity/equipment type and provisioned attributes alarm is reported against the Alarm Interface Panel (AIP), the fuse in the AIP board blew or is missing. This alarm also occurs when an old AIP board with a 2 amp fuse is installed in a newer 10 Gbps compatible or ANSI shelf assembly (15454-SA-ANSI). In either case, replace the AIP.
Procedure: Clear the MEA Alarm
Follow the "Alarm Interface Panel Replacement" section on page 3-7.
1.4.91 MEA (EQPT)
•Critical, Service affecting
The mismatch between entity/equipment type and provisioned attributes alarm is reported against a card slot when the physical card inserted into a slot does not match the card type that is provisioned for that slot in CTC. The alarm also occurs when certain cards introduced in Release 3.1 or laterare inserted into an older, pre-ANSI (15454-SA-NEBS3E or older) shelf assembly or older Ethernet cards (E1000-2 and E100T-12) are used in a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI). Removing the incompatible cards to clear the alarm.
Procedure: Clear the MEA Alarm
Step 1 Determine whether the ONS 15454 shelf assembly is a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) or an earlier shelf assembly. At the CTC shelf view, click the Inventory tab.
Under the Hardware Part # column, if the part number is 800-19857-XX or 800-19856-XX, then you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly.
Under the Hardware Part # column, if the number is not 800-19856-XX or 800-19856-XX, then you are using an earlier shelf assembly.
Note On the 15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1 (P/N: 800-07149) shelves the AIP cover is clear plastic. On the 15454-SA-ANSI shelf (P/N: 800-19857), the AIP cover is metal.
Step 2 Physically verify the type of card that sits in the slot reported in the object column of the MEA row on the alarms screen by reading the name at the top of the card's faceplate.
a. If you have a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) and the card reporting the alarm is not an E1000-2 or E100T-12, proceed to Step 3.
b. If you have a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) and the card reporting the alarm is an E1000-2 or E100T-12, then that version of the Ethernet card is incompatible and must be removed.
Note The E1000-2-G and E100T-G cards are compatible with the newer ANSI 10 Gbps compatible shelf assembly and are the functional equivalent of the older, non-compatible E1000-2 and E100T-12 cards. E1000-2-G and E100T-G cards can be used as replacements for E1000-2 and E100T-12 cards in a ANSI 10 Gbps compatible shelf assembly.
c. If you have an older, pre-ANSI shelf assembly and the card reporting the alarm is not a card introduced in Release 3.1 or later, which includes the XC10G, OC-192, E1000-2-G, E100T-G or OC-48 any slot (AS), proceed to Step 3.
d. If you have an older, pre-ANSI shelf assembly and the card reporting the alarm is a card introduced in Release 3.1 or later, which includes the XC10G, OC-192, E1000-2-G, E100T-G or OC-48 any slot (AS), the reporting card is incompatible with the shelf assembly and must be removed.
Step 3 On CTC, click the Inventory tab to reveal the provisioned card type.
Step 4 If you prefer the card type depicted by CTC, replace the physical card reporting the mismatch with the card type depicted by CTC (provisioned for that slot).
Step 5 If you prefer the card that physically occupies the slot and the card is not in-service, has no circuits mapped to it and is not part of a protection group, then put the cursor over the provisioned card in CTC and right-click to choose Delete Card.
The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
Note If the card is in-service, has a circuit mapped to it, is paired in a working protection scheme, has DCC communications turned on, or is used as a timing reference, then CTC will not allow you to delete the card.
Step 6 If the card is in-service, take the facility out of service:
Caution Before taking the facility out of service, ensure that no live traffic exists on the facility.
a. Double-click the reporting card to display the card view.
b. Click the Provisioning tab.
c. Click the Status of any in-service ports.
d. Choose Out of Service to take the ports out of service.
Step 7 If a circuit has been mapped to the card, delete the circuit:
Caution Before deleting the circuit, ensure that no live traffic exists on the facility.
a. On the node view, click the Circuits tab.
b. Choose the applicable circuit (the one that connects to the reporting card).
c. Click Delete.
Step 8 If the card is paired in a protection scheme, delete the protection group:
a. Click the Provisioning > Protection tabs.
b. Choose the protection group of the reporting card.
c. Click Delete.
Step 9 Right-click the card reporting the alarm.
Step 10 Choose Delete.
The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
1.4.92 MEA (FAN)
•Critical, Service affecting
The mismatch between entity/equipment type and provisioned attributes alarm is reported against the fan tray when a newer fan-tray assembly (15454-FTA3) with a 5 amp fuse is used with an older shelf assembly or when an older fan tray with a 2 amp fuse is used with a newer 10 Gbps compatible or ANSI shelf assembly (15454-SA-ANSI) that contains cards introduced in Release 3.1 or later. If a newer ANSI shelf assembly contains only cards introduced before Release 3.1, then an older fan tray assembly (15454-FTA-2) can be used and will not report an MEA alarm.
Procedure: Clear the MEA Alarm
Step 1 Determine whether the ONS 15454 shelf assembly is a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) or an earlier shelf assembly. At the CTC shelf view, click the Inventory tab.
Under the Hardware Part # column, if the part number is 800-19857-XX or 800-19856-XX, then you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly.
Under the Hardware Part # column, if the number is not 800-19857-XX or 800-19856-XX, then you are using an earlier shelf assembly.
Step 2 If you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly, the alarm indicates that an older incompatible fan tray assembly is installed in the shelf assembly. See the "Fan-Tray Assembly Replacement" section on page 3-5.
Step 3 If you are using an earlier shelf assembly, the alarm indicates that you are using a newer fan tray assembly (15454-FTA3), which is incompatible with the earlier version of the shelf assembly. Obtain an earlier version of the fan tray assembly (15454-FTA2) and see the "Fan-Tray Assembly Replacement" section on page 3-5.
1.4.93 MEM-GONE
•Major, Non-service affecting
The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC+ card. CTC will not function properly until this alarm clears. The alarm clears when additional memory becomes available.
Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.94 MEM-LOW
•Minor, Non-service affecting
The free memory of card almost gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the TCC+ card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the TCC+ card is exceeded, CTC will cease to function.
Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.95 MFGMEM
•Critical, Service Affecting
The MFGMEM or Manufacturing Data Memory Failure alarm raises if the ONS 15454 cannot access the data in the erasable programmable read-only memory (EPROM). Either the memory module on the component failed or the TCC+ lost the ability to read that module. The EPROM stores manufacturing data that is needed for both compatibility and inventory issues. The EPROM on the alarm interface panel (AIP) also stores the MAC address. An inability to read a valid MAC address will disrupt IP connectivity and gray out the ONS 15454 icon on the CTC network view.
Procedure: Clear the MFGMEM Alarm on the AIP, Fan Tray, or Backplane.
Step 1 Do a software-initiated system reset on the TCC+ by referring to the "Perform a Software-Initiated Reset" procedure on page 3-14.
Step 2 If the alarm does not clear, do a card pull reset on the TCC+ by referring to the "Perform a Card Pull" procedure on page 3-14.
Step 3 If the alarm does not clear, physically replace the standby TCC+ card on the ONS 15454 with a new TCC+ card.
a. Open the TCC+ card ejectors.
b. Slide the card out of the slot. This raises the IMPROPRMVL alarm which will clear when the upgrade is complete.
c. Open the ejectors on the TCC+ card.
d. Slide the TCC+ card into the slot along the guide rails.
e. Close the ejectors.
Note It takes approximately 20 minutes for the active TCC+ to transfer the system software to the newly-installed TCC+. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the LEDs on the TCC+ flash Fail and then the Active/Standby LED flashes. When the transfer completes, the TCC+ reboots and goes into Standby mode after approximately three minutes.
Step 4 Right click the active TCC+ card to reveal a pull-down menu.
Step 5 Click Reset Card.
Wait for the TCC+ to reboot. The ONS 15454 switches the standby TCC+ card to active mode.
Step 6 Verify that the remaining TCC+ card is now in standby mode (the ACT/STBY LED changes to amber).
Step 7 Physically replace the remaining TCC+ card with the second TCC+ card.
a. Open the TCC+ card ejectors.
b. Slide the card out of the slot.
c. Open the ejectors on the TCC+ card.
d. Slide the TCC+ card into the slot along the guide rails.
e. Close the ejectors.
The ONS 15454 boots up the second TCC+ card. The second TCC+ must also copy the system software, which can take up to twenty minutes.
Step 8 If the MFGMEM alarm continues to report after replacing the TCC+ cards, the problem lies in the EPROM.
Step 9 If the MFGMEM is reported from the fan tray, replace the fan tray.
Step 10 If the MFGMEM is reported from the AIP, the backplane, or the alarm persists after the fan tray is replaced, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).
1.4.96 NOT-AUTHENTICATED
•Minor, Non-service affecting
This not authenticated alarm indicates that the username and password entered do not match the information stored in the TCC+. All ONS nodes must have the same username and password created to display every ONS node in the network. You can also be locked out of certain ONS nodes on a network if your username and password were not created on those specific ONS nodes.
Note For initial log on to the ONS 15454, type the user name CISCO15 and click Login (no password is required).
Procedure: Clear the NOT-AUTHENTICATED Alarm
Step 1 If you have an alternate username and a password available to access the system:
a. Use the alternate username and password to access the ONS node.
b. Click the Provisioning > Security tabs.
c. Look under the Users field to find the username that raised the alarm.
d. If the username that raised the alarm is listed, then highlight the username to reveal the associated password. Record the correct password.
e. If the username is not listed, then click Create.
f. Fill in the fields on the Create User dialog box with the username and password that raised the alarm then click OK.
Step 2 If you do not have an alternate username and password available, call the Cisco Technical Assistance Center at (1-800-553-2447). TAC can issue a new username and password.
1.4.97 PDI-P
•Not Alarmed (NA) (Condition)
A Payload Defect Indication Path alarm indicates a signal label mismatch failure (SLMF). An invalid C2 byte in the SONET path overhead causes an SLMF. The C2 byte is the signal label byte. This byte tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.
The ONS 15454 encounters an SLMF when the payload, such as an ATM, does not match what the signal label is reporting. An AIS alarm often accompanies the PDI-P alarm. If the PDI-P is the only alarm reported with the AIS, clear the PDI-P alarm to clear the AIS alarm. PDI-P can also occur during an upgrade, but usually clears itself and is not a valid alarm.
A PDI-P condition reported on the port of an OC-N card supporting a G1000-4 card circuit may result from the end-to-end Ethernet link integrity feature of the G1000-4. This will typically be accompanied by an alarm, such as TPTFAIL or CARLOSS, reported against one or both Ethernet ports terminating the circuit. In this instance troubleshooting the accompanying alarm will clear the PDI-P condition.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the PDI-P Condition
Step 1 Verify that all circuits terminating in the reporting card are in an active state:
a. Click the Circuits tab.
b. Verify that the State column lists the port as ACTIVE.
c. If the State column lists the port as INCOMPLETE, wait 10 minutes for the ONS 15454 to fully initialize. If INCOMPLETE does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
Step 2 After determining that the port is active, verify the signal source to the card reporting the alarm.
Step 3 If traffic is affected, delete and recreate the circuit.
Caution Deleting a circuit may affect traffic.
Step 4 Check the far-end OC-N card that provides STS payload to the reporting card.
Step 5 Confirm the cross-connect between the OC-N card and the reporting card.
Step 6 Clean the far-end optical fiber:
a. Clean the fiber 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.
Step 7 Replace the optical/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.
1.4.98 PEER-NORESPONSE
•Major, Non-service affecting
The switch agent raises a peer card not responding alarm if either traffic card in a protection group does not receive a response to the peer status request message. This is a software failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure between peer cards.
Procedure: Clear the PEER-NORESPONSE Alarm Reported
Step 1 Right click on the card reporting the alarm.
Step 2 Click Reset Card and OK on the confirmation dialog.
Step 3 Wait for the card to reset.
Step 4 At reset, the green Act LED on the card will be replaced on the CTC by a white Ldg LED. When the card finishes resetting, the green Act LED will reappear.
Step 5 Right click on the peer card of the card reporting the alarm.
Step 6 Click Reset Card and OK on the confirmation dialog.
1.4.99 PLM-P
•Critical, Service affecting
A Payload Label Mismatch Path indicates a Signal Label Mismatch Failure (SLMF). An invalid C2 byte in the SONET path overhead causes an SLMF. The C2 byte is the signal label byte. This byte tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.
The ONS 15454 encounters an SLMF when the payload, such as a DS-3 signal, does not match what the signal label is reporting. An AIS alarm often accompanies the PLM-P alarm. If the PLM-P is the only alarm reported with the AIS, clearing the PLM-P alarm clears the AIS alarm.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the PLM-P Alarm
Step 1 Verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the State column lists the port as ACTIVE.
c. If the State column lists the port as INCOMPLETE, wait 10 minutes for the ONS 15454 to fully initialize. If INCOMPLETE does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
Step 2 After determining the port is active, verify the signal source to the traffic card reporting the alarm.
Step 3 If traffic is being affected, delete and recreate the circuit.
Caution Deleting a circuit may affect traffic.
Step 4 Check the far-end OC-N card that provides STS payload to the DS-N card.
Step 5 Verify the cross-connect between the OC-N card and the DS-N card.
Step 6 Clean the far-end optical fiber:
a. Clean the fiber 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.
Step 7 Replace the OC-N/DS-N cards.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.100 PLM-V
•Minor, Service affecting
A VT Payload Label Mismatch alarm indicates that the content of the V5 byte in the SONET overhead is inconsistent or invalid. This alarm occurs when ONS nodes interoperate with equipment that performs bit-synchronous mapping for DS-1. ONS nodes use asynchronous mapping.
Procedure: Clear the PLM-V Alarm
Step 1 Verify that your signal source matches the signal allowed by the traffic card. For example, the traffic card does not allow VT6 or VT9 mapping.
Step 2 Verify that the SONET VT path originator is sending the correct VT label value. You can find the SONET VT path originator using circuit provisioning steps.
1.4.101 PRC-DUPID
•Major, Service affecting
The procedural error duplicate node ID alarm indicates that two identical node IDs exist in the same ring. The ONS 15454 requires each node in the ring to have a unique node ID.
Procedure: Clear the PRC-DUPID Alarm
Step 1 Find the nodes with identical node IDs.
a. Log into a node on the ring.
b. Click the Provisioning > Ring tabs.
c. Record the Node ID number.
d. Repeat steps a - c for all nodes in the ring.
Step 2 If two nodes have an identical node ID number, change the node ID number of one node.
a. Log into a node that has an identical node ID number.
b. Click the Provisioning > Ring tabs.
c. Change the number in the Node ID field to a unique number between 0 and 31.
d. Click Apply.
1.4.102 RAI
•Not Alarmed (NA) (Condition)
The remote alarm indication condition signifies an end-to-end failure. The error condition is sent from one end of the SONET path to the other.
RAI on the DS3XM-6 card indicates that far-end node is receiving a DS-3 AIS.
Procedure: Clear the RAI Condition
Use the AIS procedure to troubleshoot the far-end DS-3 node for RAI.
1.4.103 RCVR-MISS
•Major, Service affecting
A facility termination equipment receiver missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. This usually occurs when a missing receive cable on the DS1-14 port or a possible mismatch of backplane equipment, for example, an SMB connector or a BNC connector is connected to a DS1-14 card.
Note DS-1s are four-wire circuits and need a positive (tip) and negative (ring) connection for both transmit and receive.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the RCVR-MISS Alarm
Step 1 Ensure that the device attached to the DS1-14 port is operational.
Step 2 Verify that the cabling is securely connected.
Step 3 Verify that the pinouts are correct.
Step 4 Replace the receive cable if Steps 1 - 3 do not clear the alarm.
1.4.104 RDI-P
See the RFI-P.
1.4.105 RFI-L
•Not reported
A Remote Fault Indication alarm occurs when the ONS 15454 detects a remote fault indication (RFI) in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-L alarm in the reporting node.
RFI-L indicates that the alarm is occurring at the line level. The line layer is the segment between two SONET devices in the circuit and is also known as a maintenance span. The line layer deals with SONET payload transport. The line layer functions include multiplexing and synchronization.
Procedure: Clear the RFI-L Condition
Step 1 Log into the far-end node from the reporting ONS 15454.
Step 2 Check for alarms in the far-end node, especially LOS.
Step 3 Resolve alarms in the far-end node.
1.4.106 RFI-P
•Not reported
A Remote Failure Indication Path alarm occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-P alarm in the reporting node.
RFI-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 may encompass several consecutive line segments. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.
An RFI-P error message on the ONS 15454 indicates that the node reporting the RFI-P is the terminating node on that path segment.
Procedure: Clear the RFI-P Condition
Step 1 Verify that the ports are enabled and in-service on the reporting ONS 15454.
Step 2 To find the path and node failure, verify the integrity of the SONET STS circuit path at each of the intermediate SONET nodes.
Step 3 Check for alarms in the node with the failure, especially UNEQ-P or UNEQ-V.
Step 4 Resolve alarms in that node.
1.4.107 RFI-V
•Not reported
A Remote Fault Indication VT alarm occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-V alarm in the reporting node.
RFI-V indicates that an upstream failure has occurred at the VT layer. The VT (electrical) layer is created when the SONET signal is broken down into an electrical signal, for example when an optical signal comes into an ONS 15454. If this optical signal is demultiplexed and one of the channels separated from the optical signal is cross connected into the DS1-14 port in the ONS 15454, the ONS 15454 reports an RFI-V alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the RFI-V Condition
Step 1 Check connectors to ensure they are securely fastened and connected to the correct slot/port.
Step 2 Verify that the DS1-14 port is active and in-service.
Step 3 Check the signal source for errors.
Step 4 Log into the far-end node from the reporting ONS 15454.
Step 5 Check for alarms in the far-end node, especially UNEQ-P or UNEQ-V.
Step 6 Find and troubleshoot the far-end node alarms.
1.4.108 RING-MISMATCH
•Major, Service affecting
A procedural error mismatch ring alarm occurs when the Ring ID of the ONS 15454 that is reporting the alarm does not match the Ring ID of another ONS node in the BLSR. ONS nodes connected in a BLSR must have identical Ring IDs to function.
Procedure: Clear the RING-MISMATCH Alarm
Step 1 Click the Provisioning > Ring tabs.
Step 2 Note the number in the Ring ID field.
Step 3 Log into the next ONS node in the BLSR.
Step 4 Verify that the Ring ID number matches the Ring ID number of the reporting node.
a. If the Ring ID matches the Ring ID in the reporting ONS node, log into the next ONS node in the BLSR.
b. If the Ring ID does not match the Ring ID in the reporting ONS node, change the Ring ID to match the Ring ID of the reporting node and click Apply.
c. Click Yes on the Accept Ring Map Changes dialog box.
d. Verify that the ring map is correct.
e. Click Accept for the new BLSR Ring Map.
Step 5 Repeat Step 4 for all ONS nodes in the BLSR.
1.4.109 SD-L
•Not Alarmed (NA) (Condition)
A signal degrade alarm occurs when the quality of the signal is so poor that the bit error rate (BER) on the incoming optical line passed the signal degrade (SD) threshold. Signal degrade is defined by Telcordia as a "soft failure" condition. SD and signal fail (SF) both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF.
The BER threshold on the ONS 15454 is user provisionable and has a range for SD from 10-9 to 10-5.
SD-L 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 SONET overhead.
The SD alarm clears when the BER level falls to one-tent h 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.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the SD-L Condition
Step 1 Verify that the user-provisonable BER threshold is set at the expected level.
a. From the CTC node view, double-click the card reporting the alarm to bring up the card view.
b. Click the Provisioning > Line tabs.
c. Under the SD BER column on the Provisioning pane, check 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 to step 2.
e. If the entry is not consistent with what the system was originally provisioned for, click on the cell to reveal the range of choices and click the entry that is consistent with what the system was originally provisioned for.
f. Click Apply.
Step 2 With an optical test set, measure the power level of the line to ensure it is within guidelines.
Step 3 Verify that optical receive levels are within the acceptable range.
Step 4 Clean the fibers at both ends for a line signal degrade:
a. Clean the fiber 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.
Step 5 Verify that single-mode fiber is used.
Step 6 Verify that a single-mode laser is used at the far end.
Step 7 If the problem persists, the transmitter at the other end of the optical line may be failing and require replacement.
1.4.110 SD-P
•Not Alarmed (NA) (Condition)
A signal degrade alarm occurs when the quality of the signal is so poor that the bit error rate (BER) on the incoming optical line passed the signal degrade (SD) threshold. Signal degrade is defined by Telcordia as a "soft failure" condition. SD and signal fail (SF) both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF. SD causes the card to switch from working to protect.
The BER threshold on the ONS 15454 is user provisionable and has a range for SD from 10-9 to 10-5.
SD-P causes a switch from the working card to the protect card at the path (STS) level. A path or STS level SD alarm travels on the B3 byte of the SONET overhead. The ONS 15454 detects path SD on the STS level, not the VT level.
The SD alarm clears when the BER level falls to one-tent h 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.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the SD-P Condition
Step 1 Verify that the user-provisonable BER threshold is set at the expected level.
a. From the CTC node view, double-click the card reporting the alarm to bring up the card view.
b. Click the Provisioning > Line tabs.
c. Under the SD BER column on the Provisioning pane, check 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 to step 2.
e. If the entry is not consistent with what the system was originally provisioned for, click on the cell to reveal the range of choices and click the entry that is consistent with what the system was originally provisioned for.
f. Click Apply.
Step 2 With an optical test set, measure the power level of the line to ensure it is within guidelines.
Step 3 Verify that optical receive levels are within the acceptable range.
Step 4 Verify that single-mode fiber is being used.
Step 5 Verify that a single-mode laser is being used at the far end.
Step 6 If the problem persists, the transmitter at the other end of the optical line may be failing and require replacement.
1.4.111 SF-L
•Not Alarmed (NA) (Condition)
A signal failure alarm occurs when the quality of the signal is so poor that the BER on the incoming optical line passed the signal failure (SF) threshold. . Signal failure is defined by Telcordia as a "hard failure" condition. SD and SF both monitor the incoming BER error rate and are similar alarms, but SF is triggered at a higher BER than SD.
The BER threshold on the ONS 15454 is user provisionable and has a range for SF from 10-5 to 10-3.
SF-L causes a switch from the working card to the protect card at the line (facility) level. A line or facility level SF alarm travels on the B2 byte of the SONET overhead.
SF causes a card to switch from working to protect at either the path or line level. 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.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the SF-L Condition
Step 1 Verify that the user-provisonable BER threshold is set at the expected level.
a. From the CTC node view, double-click the card reporting the alarm to bring up the card view.
b. Click the Provisioning > Line tabs.
c. Under the SF BER column on the Provisioning pane, check that the cell entry is consistent with what the system was originally provisioned for. The default setting is 1E-4.
d. If the entry is consistent with what the system was originally provisioned for, continue to step 2.
e. If the entry is not consistent with what the system was originally provisioned for, click on the cell to reveal the range of choices and click the entry that is consistent with what the system was originally provisioned for.
f. Click Apply.
Step 2 Using an optical test set, measure the power level of the line and ensure it is within the guidelines.
Step 3 Verify that optical receive levels are within the acceptable range.
Step 4 Clean the fibers at both ends for a line signal fail:
a. Clean the fiber 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.
Step 5 Verify that single-mode fiber is being used.
Step 6 Verify that a single-mode laser is being used at the far-end node.
Step 7 If the problem persists, the transmitter at the other end of the optical line may be failing and need replacement.
1.4.112 SF-P
•Not Alarmed (NA) (Condition)
A signal failure alarm occurs when the quality of the signal is so poor that the BER on the incoming optical line passed the signal failure (SF) threshold. Signal failure is defined by Telcordia as a "hard failure" condition. SD and SF both monitor the incoming BER error rate and are similar alarms, but SF is triggered at a higher BER than SD.
The BER threshold on the ONS 15454 is user provisionable and has a range for SF from 10-5 to 10-3.
SF-P causes a switch from the working card to the protect card at the path (STS) level. A path or STS level SF alarm travels on the B3 byte of the SONET overhead. The ONS 15454 detects path SF on the STS level, not the VT level.
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.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the SF-P Condition
Step 1 Verify that the user-provisonable BER threshold is set at the expected level.
a. From the CTC node view, double-click the card reporting the alarm to bring up the card view.
b. Click the Provisioning > Line tabs.
c. Under the SF BER column on the Provisioning pane, check that the cell entry is consistent with what the system was originally provisioned for. The default setting is 1E-4.
d. If the entry is consistent with what the system was originally provisioned for, continue to step 2.
e. If the entry is not consistent with what the system was originally provisioned for, click on the cell to reveal the range of choices and click the entry that is consistent with what the system was originally provisioned for.
f. Click Apply.
Step 2 Using an optical test set, measure the power level of the line and ensure it is within the guidelines.
Step 3 Verify that optical receive levels are within the acceptable range.
Step 4 Verify that single-mode fiber is being used.
Step 5 Verify that a single-mode laser is being used at the far-end node.
Step 6 If the problem persists, the transmitter at the other end of the optical line may be failing and need replacement.
1.4.113 SFTWDOWN
•Minor, Non-service affecting
A software download in progress alarm occurs, when the TCC+ is downloading or transferring software. No action is necessary. Wait for the transfer or the software download to complete.
1.4.114 SFTWDOWN-FAIL
•Minor, Non-service affecting
The software download from the TCC+ card to the ONS 15454 failed. The problem lies in the TCC+ card.
Procedure: Clear the SFTWDOWN-FAIL Alarm
Step 1 Attempt the download again by clicking the Maintenance > Software tabs and the Download button.
Step 2 If the download fails, reset the standby TCC+ to ensure that the standby card is synchronized with the database on the active TCC+:
a. Identify the standby TCC+.
If you are looking at the physical ONS 15454, the ACT/STBY LED of standby TCC+ is amber .
If you are looking at the CTC node view of the ONS 15454, the standby TCC+ has a yellow LED depiction with the letters "Sby".
b. Right-click on the standby TCC+.
c. Select Reset Card from the pull-down menu.
d. Click Yes at the Are You Sure dialog that appears.
While the card resets, the FAIl LED will blink on the physical card and then no LED will be lit.
While the card resets, the white LED with the letters "LDG" appears on the card in CTC.
e. Verify that the reset is complete and error free.
No new alarms appear under the alarms tab on the CTC.
If you are looking at the physical ONS 15454, the ACT/STBY LED is lit.
If you are looking at the CTC node view of the ONS 15454, a yellow LED depiction with "Sby" has replaced the white "LDG" depiction on the card in CTC.
f. Wait ten minutes to verify that the Standby TCC+ does not reset itself.
g. If the TCC+ reset is not complete and error free or if the TCC resets itself, call the Cisco Technical Assistance Center (1-800-553-2447).
Step 3 Attempt the download again by clicking the Maintenance > Software tabs and the Download button.
Step 4 If the software download fails again, refer to and complete the Back Up and Restore the Database procedure in the ONS 15454 Procedure Guide, then proceed to the next step in this procedure.
Step 5 Reset the active TCC+:
a. Identify the active TCC+.
If you are looking at the physical ONS 15454, the ACT/STBY LED of the active TCC+ is green.
If you are looking at the CTC node view of the ONS 15454, the active TCC+ has a green LED depiction with "Act".
b. Right-click on the active TCC+.
c. Select Reset Card from the pull-down menu.
d. Click Yes at the Are You Sure dialog that appears.
e. Wait ten minutes to verify that the newly standby TCC+ does not reset itself.
f. Verify that the reset is complete and error free.
No new alarms appear under the alarms tab on the CTC.
If you are looking at the physical ONS 15454, the ACT/STBY LED has stopped blinking and is now amber.
If you are looking at the CTC node view of the ONS 15454, a yellow LED depiction with Sby has replaced the blue/white depiction on the card in CTC. (The formerly active TCC+ is now standby.)
g. If the TCC+ reset is not complete and error free or if the TCC resets itself, call the Cisco Technical Assistance Center (1-800-553-2447).
Step 6 Attempt the download again by clicking the Maintenance > Software tabs and the Download button.
Step 7 If the download fails again, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
1.4.115 SQUELCH
•Not Alarmed, Non-service affecting (Condition)
The ring is squelching traffic alarm occurs in a BLSR when a node that originates or terminates STS circuits fails or is isolated by multiple fiber cuts or maintenanceforce ring commands. The isolation or failure of the node will disable the 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 AIS-P alarm will also appear on all nodes in the ring, except the isolated node.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Warning On the OC-192 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 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 100 mm may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.
Procedure: Clear the SQUELCH Condition
Step 1 Determine the isolated node:
a. Display the CTC network view.
b. The grayed out node with red spans will be the isolated node.
Step 2 Verify fiber continuity to the ports on the isolated node.
Step 3 Verify that the proper ports are in service.
Step 4 Use an optical test set to verify that a valid signal exists on the line.
Test the line as close to the receiving card as possible.
Step 5 Verify that the power level of the optical signal is within the optical card's receiver specifications. Each individual card section in Chapter 4 lists the receiver specifications for that card.
Step 6 Ensure that the optical transmits and receives are connected properly.
Step 7 Replace the OC-N card.
1.4.116 SSM-FAIL
•Minor, Non-service affecting
The failed to receive synchronization status message alarm means the synchronization status messaging (SSM) received by the ONS 15454 failed. The problem is external to ONS 15454. The ONS 15454 is set up to receive SSM, but the timing source is not delivering valid SSM messages.
SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.
Procedure: Clear the SSM-FAIL Alarm
Step 1 Check that SSM is enabled on the external timing source.
Step 2 Use a test set to determine that the external timing source is delivering SSM.
1.4.117 STU
•Not Alarmed (NA) (Condition)
The synchronization traceability unknown alarm occurs when the reporting node is timed to a reference that does not support synchronization status messaging (SSM), but the ONS 15454 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 ONS 15454.
SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. SSM enables SONET devices to automatically choose the highest quality timing reference and to avoid timing loops.
Procedure: Clear the STU Condition
Step 1 Click the Provisioning > Timing tabs.
Step 2 If Sync Messaging is checked, uncheck the box.
Step 3 If Sync Messaging is unchecked, check the box.
Step 4 Click Apply.
1.4.118 SWMTXMOD
•Critical, Service affecting
The Switching Matrix Module Failure alarm occurs on the XCVT card or a traffic card. If the alarm reports against a traffic card, it means that the logic component on the cross-connect card is out of frame (OOF) with the logic component on the reporting traffic card. All traffic on the reporting traffic card is lost.
If the alarm reports against an XCVT card, it means that a logic component internal to the reporting XCVT card is out of frame with a second logic component on the same XCVT card. One or more traffic cards may lose traffic as a result of this failure.
Procedure: Clear the SWMTXMOD Alarm
Step 1 If the card reporting the alarm is the standby XCVT card, perform a CTC reset on the standby XCVT:
a. Display the node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
d. Click Yes at the Resetting Card confirmation dialog.
Wait for the card to reboot.
e. If the alarm persists, physically reseat the standby XCVT card.
Step 2 If the card reporting the alarm is the active XCVT card, perform a side switch from the active XCVT card to the standby XCVT card:
a. Determine the active XCVT card. The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is yellow.
Note You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.
b. In the node view, choose the Maintenance > XC Cards tabs.
c. Click Switch.
d. Click Yes on the Confirm Switch dialog box.
Note After the active cross-connect goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
e. Perform a CTC reset on the reporting card:
From the node view, position the cursor over the slot reporting the alarm.
Right-click to choose RESET CARD.
Click Yes at the Resetting Card confirmation dialog.
Wait for the card to reboot.
f. If the alarm persists, physically reseat the standby XCVT card.
Step 3 If the card reporting the alarm is an I/O card, perform a side switch from the active cross-connect (XC, XCVT, XC10G) card to the standby cross-connect card:
a. Determine the active cross-connect (XC, XCVT, XC10G) card. The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is yellow.
Note You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.
b. In the node view, choose the Maintenance > XC Cards tabs.
c. Click Switch.
d. Click Yes on the Confirm Switch dialog box. After the active card goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
e. If the alarm does not clear after the cross-connect (XC, XCVT, XC10G) side switch, perform a CTC reset on the reporting card:
f. Display the CTC node view.
g. Position the cursor over the slot reporting the alarm.
h. Right-click to choose RESET CARD.
i. Click Yes at the Resetting Card confirmation dialog.
Wait for the card to reboot.
j. If the alarm persists, physically reseat the reporting traffic/line card.
1.4.119 SWTOPRI
•Not Alarmed (NA) (Condition)
The synchronization switch to primary reference condition occurs when the ONS 15454 switches to the primary timing source (reference 1). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.
Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.
1.4.120 SWTOSEC
•Not Alarmed (NA) (Condition)
The synchronization switch to secondary reference condition occurs when the ONS 15454 has switched to the secondary timing source (reference 2). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.
Procedure: Clear the SWTOSEC Condition
Find and troubleshoot alarms related to failures of the primary source, such as the SYNCPRI alarm.
1.4.121 SWTOTHIRD
•Not Alarmed (NA) (Condition)
The synchronization switch to third reference condition occurs when the ONS 15454 has switched to the third timing source (reference 3). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.
Procedure: Clear the SWTOTHIRD Condition
Find and troubleshoot alarms related to failures of the primary and secondary reference source, such as the SYNCPRI and SYNCSEC alarms.
1.4.122 SYNCPRI
•Minor, Non-service affecting
A loss of timing on primary reference alarm occurs when the ONS 15454 loses the primary timing source (reference 1). The ONS 15454 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 ONS 15454 should switch to its secondary timing source (reference 2). This switch also triggers the SWTOSEC alarm.
Procedure: Clear the SYNCPRI Condition
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, follow the procedure in the "LOS (BITS)" section.
Step 4 If the primary reference clock is an incoming port on the ONS 15454, follow the procedure in the "LOS (OC-N)" section.
1.4.123 SYNCSEC
•Minor, Non-service affecting
A loss of timing on secondary reference alarm occurs when the ONS 15454 loses the secondary timing source (reference 2). The ONS 15454 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 ONS 15454 should switch to the third timing source (reference 3) to obtain valid timing for the ONS 15454. This switch also triggers the SWTOTHIRD alarm.
Procedure: 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 secondary reference is a BITS input, follow the procedure in the "LOS (BITS)" section.
Step 4 If the secondary timing source is an incoming port on the ONS 15454, follow the procedure in the "LOS (OC-N)" section.
1.4.124 SYNCTHIRD
•Minor, Non-service affecting
A loss of timing on third reference alarm occurs when the ONS 15454 loses the third timing source (reference 3). The ONS 15454 uses three ranking timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCTHIRD occurs and the ONS 15454 uses an internal reference for source three, then the TCC+ card may have failed. The ONS 15454 often reports either FRNGSYNC or HLDOVERSYNC alarms after a SYNCTHIRD alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the SYNCTHIRD Alarm
Step 1 From node view, click the Provisioning > Timing tabs.
Step 2 Check the current configuration of the REF-3 for the NE Reference.
Step 3 If the third timing source is a BITS input, follow the procedure in the "LOS (BITS)" section.
Step 4 If the third timing source is an incoming port on the ONS 15454, follow the procedure in the "LOS (OC-N)" section.
Step 5 If the third timing source uses the internal ONS 15454 timing, perform a software reset on the TCC+ card:
a. Display the CTC node view.
b. Position the cursor over the slot reporting the alarm.
c. Right-click and choose RESET CARD.
Step 6 If this fails to clear the alarm, physically reseat the TCC+ card.
Step 7 If the reset fails to clear the alarm, replace the TCC+ card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.4.125 SYSBOOT
•Major, Service affecting
The system reboot alarm indicates that new software is booting on the TCC+ card. This is an informational alarm. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 30 minutes.
1.4.126 TIM-P
•Minor, Service affecting
The STS Path Trace Identifier Mismatch Path alarm occurs when the expected path trace string does not match the received path trace string. Path Trace Mode must be set to manual or Auto for this alarm to occur.
In manual mode at the Path Trace screen, the user types the expected string into the New Expected String field for the receiving port. This string must match the string typed into the New Transmit String field for the sending port. If these fields do not match, the TIM-P alarm will occur. In Auto mode on the receiving port, the card sets the expected string to the value of the received string. If the alarm occurs on a port that has been operating with no alarms, this means the circuit path changed or someone typed and entered a new incorrect value into the New Transmit String field. Follow the procedure below to clear either instance.
This alarm also occurs on a port that has previously been operating without alarms if someone switches or removes the DS-3 cables or optical fibers that connect the ports. This TIM-P occurrence is usually accompanied by other alarms, such as LOS, UNEQ-P, or PLM-P. In this case, reattach or replace the original cables/fibers to clear the alarm.
Procedure: Clear the TIM-P Alarm
Step 1 Log into the circuit source node and select the Circuits tab.
Step 2 Select the circuit reporting the alarm, then click Edit.
Step 3 At the bottom of the Edit Circuit window, check the Show Detailed Map box.
Step 4 On the detailed circuit map, right-click the source circuit port and select Edit Path Trace from the shortcut menu.
Step 5 On the detailed circuit map, right click the drop/destination circuit port and select Edit Path Trace from the shortcut menu.
Step 6 Compare the New Transmit String and the New Expected String entries in the Path Trace Mode dialog box.
Step 7 If the strings differ, correct the Transmit or Expected strings and click Apply.
Step 8 Click Close.
1.4.127 TPTFAIL
•Major, Service affecting
The transport layer failure alarm indicates a break in the end-to-end Ethernet link integrity feature of the G1000-4 cards. This alarm indicates a far-end condition and not a problem with the port reporting TPTFAIL.
This alarm indicates a problem on either the SONET path or the remote Ethernet port, which prevents the complete end-to-end Ethernet path from working. If there is any SONET path alarm such as AIS-P, LOP-P, UNEQ-P, PDI-P, RDI-P on the SONET path used by the Ethernet port, the affected port raises a TPTFAIL alarm. Also if the far end G1000-4 Ethernet port is administratively disabled or it is seeing a CARLOSS condition it will set the C2 byte in the SONET path overhead to indicate a payload defect condition (PDI-P) which in turn will cause a TPTFAIL to be reported against this near-end port.
Another important point regarding a TPTFAIL condition is that the near-end port is automatically disabled (transmit laser turned off) when this condition occurs. In turn this can also cause the external Ethernet device attached at the near end to detect link down and turn off its transmitter and also cause a CARLOSS condition to occur on this port. In all cases the real problem is either in the SONET path being used by this G1000-4 port or the far end G1000-4 port to which it is mapped.
Procedure: Clear the TPTFAIL Alarm
Step 1 An occurrence of TPTFAIL on a G1000-4 port indicates either a problem with the SONET path that this port is using or with the far end G1000-4 port that is mapped to this port. Lookup and troubleshoot any alarms being reported by the OC-N card utilized by the Ethernet circuit of the G1000-4.
Step 2 If no alarms are reported by the OC-N card or a PDI-P condition is reported the problem may be on the far- end G1000-4 port that the port reporting TPTFAIL is mapped to. Lookup and troubleshoot any alarms, such as CARLOSS, reported against the far-end port or card.
1.4.128 TRMT
•Major, Service affecting
A facility termination equipment transmit failure alarm occurs when there is a transmit failure on the DS1-14 card because of an internal hardware failure. The card must be replaced.
Procedure: Clear the TRMT Alarm
Step 1 Replace the DS1-14 card reporting the failure.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 Call the Technical Assistance Center (TAC) at (1-800-553-2447) to discuss the failed card and possibly open a returned materials authorization (RMA).
1.4.129 TRMT-MISS
•Major, Service affecting
A facility termination equipment transmitter missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. This means transmit cable is missing on the DS1-14 port or the backplane does not match the inserted card; for example, an SMB connector or a BNC connector connects to a DS1-14 card instead of a DS-3 card.
Note DS-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.
Procedure: Clear the TRMT-MISS Alarm
Step 1 Check that the device attached to the DS1-14 port is operational.
Step 2 Verify that the cabling is securely connected.
Step 3 Verify that the pinouts are correct.
Step 4 If Steps 1 - 3 do not clear the alarm, replace the transmit cable,.
1.4.130 UNEQ-P
•Critical, Service affecting
An signal label mismatch failure unequipped path alarm occurs when the path does not have a valid sender. The UNEQ-P indicator is carried in the C2 signal path byte in the SONET 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. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.
A UNEQ-P error message on the ONS 15454 indicates that the node reporting the RFI-P is the terminating node on that path segment.
Note If you have created a new circuit but it has no signal, an UNEQ-P alarm is reported on the OC-N cards and an AIS-P alarm is reported on the terminating cards. These alarms clear when the circuit carries a signal.
Caution Deleting a circuit affects traffic.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the UNEQ-P Alarm
Step 1 Display the CTC network view and right-click the span reporting UNEQ-P.
Step 2 Select Circuits from the menu.
Step 3 If the specified circuit is a VT tunnel, check for VTs assigned to the VT tunnel.
Step 4 If the VT tunnel has no assigned VTs, delete the VT tunnel from the list of circuits.
Step 5 If you have complete visibility to all nodes, check for incomplete circuits such as stranded bandwidth from circuits that were not deleted completely.
Step 6 If you find incomplete circuits, verify whether they are working circuits and if they are still passing traffic.
Step 7 If the incomplete circuits are not needed or are not passing traffic, delete them and log out of CTC. Log back in and check for incomplete circuits again. Recreate any needed circuits.
Step 8 Verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the State column lists the port as ACTIVE.
c. If the State column lists the port as INCOMPLETE. If INCOMPLETE does not change after a full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
Step 9 After you determine that the port is active, verify the signal source received by the card reporting the alarm.
Step 10 Check the far-end OC-N card that provides STS payload to the card.
Step 11 Verify the far-end cross-connect between the OC-N card and the DS-N card.
Step 12 Clean the far-end optical fiber:
a. Clean the fiber 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.
1.4.131 UNEQ-V
•Major, Service affecting
An signal label mismatch failure unequipped path alarm indicates that the node is receiving SONET path overhead with bits 5, 6, and 7 of the V5 overhead byte all set to zeroes. The source of the problem is the node that is transmitting the VT-level signal into the node reporting the UNEQ-P. The problem node is the next node upstream that processes the signal at the VT level.
The V in UNEQ-V indicates that the failure has occurred at the VT layer. The VT (electrical) layer is created when the SONET signal is broken down into an electrical signal, for example, when an optical signal comes into an ONS 15454, the optical signal is demultiplexed and one of the channels separated from the optical signal is cross connected into an ONS 15454 cross-connect (XC/XCVT/XC10G) card and the corresponding DS-N card.
Warning Invisible laser radiation may be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Procedure: Clear the UNEQ-V Alarm
Step 1 Verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the State column lists the port as ACTIVE.
c. If the State column lists the port as INCOMPLETE. If INCOMPLETE does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service-affecting problem (1-800-553-2447).
Step 2 After you determine that the port is active, verify the signal source being received by the DS-N card reporting the alarm.
Step 3 If traffic is being affected, delete and recreate the circuit.
Caution Deleting a circuit can be service affecting.
Step 4 Check the far-end OC-N card that provides STS payload to the DS-N card.
Step 5 Verify the cross-connect between the OC-N card and the DS-N card.
Step 6 Clean the far-end optical fiber:
a. Clean the fiber 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.
Step 7 Replace OC-N/DS-N cards.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
1.5 DS3-12E Line Alarms
Unlike the standard DS-3 card, which uses the unframed format exclusively, the DS3-12E card provides three choices: unframed, M23, or C-bit. The choice of framing format affects which line alarms the DS3-12E card reports. The table below lists the line alarms reported under each format.
The choice of framing format does not affect the reporting of STS alarms. Regardless of format, the DS3-12E card reports the same STS alarms as the standard DS-3 card.
Table 1-4 DS3-12E Line Alarms
Alarm
|
UNFRAMED
|
M23
|
CBIT
|
LOS
|
u
|
u
|
u
|
AIS
|
u
|
u
|
u
|
LOF
|
m
|
u
|
u
|
IDLE
|
m
|
u
|
u
|
RAI
|
m
|
u
|
u
|
Terminal Lpbk
|
u
|
u
|
u
|
Facility Lpbk
|
u
|
u
|
u
|
FE Lpbk
|
m
|
m
|
u
|
FE Common Equipment Failure
|
m
|
m
|
u
|
FE Equipment Failure-SA
|
m
|
m
|
u
|
FE LOS
|
m
|
m
|
u
|
FE LOF
|
m
|
m
|
u
|
FE AIS
|
m
|
m
|
u
|
FE IDLE
|
m
|
m
|
u
|
FE Equipment Failure-NSA
|
m
|
m
|
u
|
