ONS 15454 SDH Troubleshooting Guide R8.5.x -- Alarm Troubleshooting (M through W)

From DocWiki

Jump to: navigation, search

Contents

MAN-REQ

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EQPT, ML1000, MLM100T, MLFX, VCMON-HP, VCMON-LP

The Manual Switch Request condition occurs when a user initiates a Manual switch request on an STM-N port. Clearing the Manual switch clears the MAN-REQ condition. You do not need to clear the switch if you want the manual switch to remain.

MAN-REQ is raised for an IEEE 802.17b-based RPR span if the manual switch was requested in the Cisco IOS CLI with the "rpr-ieee protection request manual-switch {east | west}" command. It clears from the RPR-IEEE span when you remove the switch in the CLI. For the IEEE 802.17b-based RPR, MAN-REQ suppresses the "RPR-SD" alarm and the "WTR" alarm (for the ML object). This condition is suppressed by the following alarms:

Clear the MAN-REQ Condition

  1. Complete the Initiate a 1+1 Protection Port Manual Switch Command.
  2. If the condition is raised on an IEEE 802.17b-based span, enter the following CLI command in RPR-IEEE interface configuration mode:
    router(config-if)#no rpr-ieee protection request manual-switch {east | west}
  3. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MANRESET

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

A User-Initiated Manual Reset condition occurs when you right-click a card in CTC and choose Reset.

Note: MANRESET is an informational condition and does not require troubleshooting.

MANSWTOINT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: NE-SREF

The Manual Switch To Internal Clock condition occurs when the NE timing source is manually switched to an internal timing source.

Note: MANSWTOINT is an informational condition and does not require troubleshooting.

MANSWTOPRI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary timing source.

Note: MANSWTOPRI is an informational condition and does not require troubleshooting.

MANSWTOSEC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to a second timing source.

Note: MANSWTOSEC is an informational condition and does not require troubleshooting.

MANSWTOTHIRD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Manual Switch To Third Reference condition occurs when the NE timing source is manually switched to the tertiary timing source.

Note: MANSWTOTHIRD is an informational condition and does not require troubleshooting.

MANUAL-REQ-RING

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on MS-SPRing rings to switch from working to protect or protect to working. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the MANUAL RING command originated is marked with an "M" on the network view detailed circuit map.

Clear the MANUAL-REQ-RING Condition

  1. Complete the Clear an MS-SPRing External Switching Command.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MANUAL-REQ-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Manual Switch Request on Ring condition occurs on MS-SPRings when a user initiates a Manual Span command to move MS-SPRing traffic from a working span to a protect span. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the MANUAL SPAN command was applied is marked with an "M" on the network view detailed circuit map.

Clear the MANUAL-REQ-SPAN Condition

  1. Complete the Clear an MS-SPRing External Switching Command.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MAX-STATIONS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The Maximum IEEE 802.17b-based RPR Station Number Exceeded alarm can be raised by all ML card stations on a ring when the maximum quantity of RPR stations, 255, is exceeded. This excess causes the RPR-IEEE scheme-and traffic-to break down.

IEEE 802.17b-based RPR messaging uses time-to-live (TTL), an 8-bit value. The maximum value these 8 bits (one byte) can have is 255. As a message travels (or hops) from station to station, the TTL is decremented by each station. Thus one station cannot communicate with another station more than 255 hops away.

If you are creating a large ring (more than 127 nodes), the MAX-STATION alarm might be raised until the ring is closed and stable.

MAX-STATIONS does not suppress any other alarms. The alarm is suppressed by the "RPR-PASSTHR" alarm.

Clear the MAX-STATIONS Alarm

  1. Remove the extra stations from the ring to clear this alarm in all other stations and to restore traffic in the ring. For procedures to add or remove IEEE 802.17b-based RPR stations, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MEA (BIC)

The MEA alarm for the BIC object is not used in this platform in this release. It is reserved for development.

MEA (EQPT)

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Object: EQPT

The MEA alarm for equipment 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.

Note: When downgrading the CTC software from R7.2 to R6.0 and the XCVXC cross-connect card to the XCVXL for use in that release, the standby (Slot 8) XCVXL can raise the MEA alarm until the downgrade is complete.

Clear the MEA (EQPT) Alarm

  1. Physically verify the type of card that is installed in the slot reporting the MEA alarm. In node view, click the Inventory tab and compare it to the actual installed card.
  2. 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). Complete the Physically Replace a Traffic Card.
    Note: When you replace a card with the identical type of card, you do not need to make any changes to the database.
  3. If you prefer the card that physically occupies the slot and the card is not in service, has no circuits mapped, and is not part of a protection group, place 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, is paired in a working/protection scheme, has DCC communications enabled, or is used as a timing reference, CTC does not allow you to delete the card.
  4. If any ports on the card are in service, place them out of service (Locked, maintenance) by completing the following steps:
    Caution! Before placing ports out of service, ensure that no live traffic is present.
    1. Double-click the reporting card to display the card view.
    2. Click the Provisioning > Line tab.
    3. Click the Admin State column of any Unlocked ports.
    4. Choose Locked, maintenance to take the ports out of service.
  5. If a circuit has been mapped to the card, complete the Delete a Circuit.
    Caution! Before deleting the circuit, ensure that live traffic is not present.
  6. If the card is paired in a protection scheme, delete the protection group by completing the following steps:
    1. Click the Provisioning > Protection tabs.
    2. Choose the protection group of the reporting card.
    3. Click Delete.
    4. Click Yes in the Delete Protection Group dialog box.
  7. Right-click the card reporting the alarm.
  8. Choose Delete.
    The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
  9. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

MEA (FAN)

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Object: FAN

The Mismatch of Equipment Attributes alarm is reported against the fan-tray assembly when an older ONS 15454 SDH fan-tray assembly (FTA2) is used with certain cards that require the newer fan-tray assembly (15454E-FTA-48V). The 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) and fan-tray assembly (15454E-FTA-48V) are required with the ONS 15454 SDH OC192 LR/STM64 LH 1550, E1000-2-G, E100T-G, OC48 IR/STM16 SH AS 1310, or OC48 LR/STM16 AS 1550 cards.

Note: For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the MEA (FAN) Alarm

  1. Determine whether the ONS 15454 SDH shelf assembly is a newer ETSI 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) or an earlier shelf assembly by completing the following steps:
    1. In node view, click the Inventory tab.
    2. In the HW Part # column, if the number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454-SA-10G).
    3. In the HW Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.
  2. If you have a 10-Gbps-compatible shelf assembly (15454E-SA-ETSI), the alarm indicates that an older, incompatible fan-tray assembly is installed in the shelf assembly. Obtain a newer fan-tray assembly (15454-FTA3) with a 5 A fuse and complete the Replace the Fan-Tray Assembly.
  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 complete the Replace the Fan-Tray Assembly.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

MEA (PPM)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

MEA (SHELF)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

MEM-GONE

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: EQPT

The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC2/TCC2P card. CTC does not function properly until this alarm clears. The alarm clears when additional memory becomes available.

Note: The alarm does not require user intervention. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MEM-LOW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Free Memory of Card Almost Gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the TCC2/TCC2P card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the card is exceeded, CTC ceases to function.

Note: The alarm does not require user intervention. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MFGMEM (AICI-AEP, AICI-AIE, PPM)

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Objects: AICI-AEP, AICI-AIE
DWDM Logical Object: PPM

The Manufacturing Data Memory Failure (MFGMEM) alarm occurs if the ONS 15454 SDH cannot access the data in the electronically erasable programmable read-only memory (EEPROM). Either the memory module on the component failed or the TCC2/TCC2P card lost the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. Inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.

Clear the MFGMEM Alarm

  1. Complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card.
    Wait ten minutes to verify that the standby TCC2/TCC2P card does not reset itself. If the TCC2/TCC2P card reset is not complete and error-free or if the TCC2/TCC2P card reboots itself, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.
    Note: If CTC stops responding after performing a reset on the TCC2/TCC2P card, close the browser and start CTC again on the affected node.
  2. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card.
  3. If the alarm does not clear, physically replace the standby TCC2/TCC2P card on the ONS 15454 SDH with a new TCC2/TCC2P card. Complete the Physically Replace a Traffic Card.
    Note: The active TCC2/TCC2P card takes up to 30 minutes to transfer the system software to the newly installed TCC2/TCC2P card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2/TCC2P card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2/TCC2P card reboots and goes into standby mode after approximately three minutes.
  4. Reset the active TCC2/TCC2P card. Complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card.
    Wait ten minutes to verify that the standby TCC2/TCC2P card does not reset itself. If the TCC2/TCC2P card reset is not complete and error-free or if the TCC2/TCC2P card reboots itself, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.
  5. Physically replace the remaining TCC2/TCC2P card with the second TCC2/TCC2P card. Complete the Physically Replace a Traffic Card.
    The ONS 15454 SDH boots up the second TCC2/TCC2P card. The second TCC2/TCC2P card must also copy the system software, which can take up to twenty minutes.
  6. If the MFGMEM alarm continues to report after replacing the TCC2/TCC2P cards, the problem lies with the EEPROM.
  7. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MFGMEM (BPLANE, FAN)

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Objects: BPLANE, FAN

The Manufacturing Data Memory (EEPROM) failure alarm occurs if the ONS 15454 SDH cannot access the data in the EEPROM. Lack of access occurs when either the memory module on the component fails or the TCC2/TCC2P card loses the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. An inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.

Clear the MFGMEM (BPLANE, FAN) Alarm

  1. Complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card.
    Note: If CTC stops responding after performing a reset on the TCC2/TCC2P card, close the browser and start CTC again on the affected node.
  2. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card.
  3. Physically replace the remaining TCC2/TCC2P card with the second TCC2/TCC2P card. Complete the Physically Replace a Traffic Card.
    Note: The active TCC2/TCC2P card takes up to 30 minutes to transfer the system software to the newly installed TCC2/TCC2P card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2/TCC2P card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2/TCC2P card reboots and goes into standby mode after approximately three minutes.
  4. Perform a CTC reset on the TCC2/TCC2P card. Complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card.
  5. Verify that the remaining TCC2/TCC2P card is now in standby mode. (The ACT/STBY LED changes to amber.)
  6. Physically replace the remaining TCC2/TCC2P card with the second TCC2/TCC2P card. Do this by completing the Physically Replace a Traffic Card. (The procedure is similar.)
  7. If the MFGMEM alarm continues to report after replacing the TCC2/TCC2P cards, the problem lies with the EEPROM.
  8. If the MFGMEM is reported from the fan-tray assembly, replace the fan-tray assembly. Obtain a fan-tray assembly and complete the Replace the Fan-Tray Assembly.
  9. If the MFGMEM is reported from backplane, or if the alarm persists after the fan-tray assembly is replaced, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

MS-AIS

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Objects: STM1E, STMN

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

Generally, any AIS is a special SDH signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

Clear the MS-AIS Condition

  1. Complete the Clear the AIS Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MS-DEG

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STM1E

The Multiplex Section Signal Degrade condition is similar to the "SDBER-EXCEED-HO" alarm, but applies only to the multiplex section overhead of the STM1E object in Release 7.2.

Clear the MS-DEG Condition

  1. Complete the Clear the SDBER-EXCEED-HO Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MS-EOC

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The MS-DCC Termination Failure alarm occurs when the ONS 15454 SDH loses its data communications channel. The DCC is nine bytes, D4 through D 12, in the SDH overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the SDH section overhead to communicate network management information.

Clear the MS-EOC Alarm

  1. Complete the Clear the RS-EOC Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MS-EXC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STM1E

The Multiplex Section Signal Excessive BER condition is similar to the "SFBER-EXCEED-HO" alarm, but applies only to the multiplex section overhead of the STM1E object in Release 7.2.

Clear the MS-EXC Condition

  1. Complete the Clear the SDBER-EXCEED-LO Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MS-RFI

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Objects: STM1E, STMN

The MS Remote Fault Indication (RFI) condition indicates that there is an RFI occurring at the SDH overhead multiplexing section level.

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

Clear the MS-RFI Condition

  1. Log into the far-end node of the reporting ONS 15454 SDH.
  2. Determine whether there are other alarms, especially the "LOS (STM1E, STMN)" alarm.
  3. Clear the main alarm. See the appropriate alarm section in this chapter for the procedure.
  4. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

MSSP-OOSYNC

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: STMN

The Procedural Error MS-SPRing Out of Synchronization alarm occurs when you attempt to add or delete a circuit and a node on a working ring loses its DCC connection because all transmit and receive fiber has been removed. The CTC cannot generate a table of the nodes and causes the MSSP-OOSYNC alarm.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the MSSP-OOSYNC Alarm

  1. Reestablish cabling continuity to the node reporting the alarm. Refer to the "Install Cards and Fiber-Optic Cables" chapter in the Cisco ONS 15454 SDH Procedure Guide for cabling procedures to reestablish the DCC. To verify cable continuity, follow site practices.
    When the DCC is established between the node and the rest of the MS-SPRing, the DCC becomes visible to the MS-SPRing and should be able to function on the circuits.
  2. If alarms occur when you have provisioned the DCC, see the "RS-EOC" alarm.
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

MSSP-SW-VER-MISM

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: STMN

The MS-SPRing Software Version Mismatch alarm is by the TCC2/TCC2P card when it checks all software versions for all nodes in a ring and discovers a mismatch in versions.

Clear the MSSP-SW-VER-MISM Alarm

  1. Clear the alarm by loading the correct software version on the TCC2/TCC2P card with the incorrect load. To download software, refer to the release-specific software download document.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a Service-Affecting (SA) problem.

MS-SQUELCH-HP

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Multiplex Section Ring is Squelching High-Order Path Traffic condition is raised on an STM-N facility. If the node failure scenario includes the source node, the node that drops the signal will squelch traffic. The condition resolves when the node recovers.

This condition is raised with an NA severity by default. However, it indicates that traffic is squelched due to node failure (traffic outage). Traffic outages can be caused by different problems, such as multiple LOS alarms, MS-AIS, or node power outages. MS-SQUELCH-HP is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what is causing the node isolation.

Note: MS-SQUELCH-HP is an informational condition.

MS-SQUELCH-LP

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Multiplex Section Ring is Squelching Low-Order Path Traffic condition is raised on an STM-N facility. If the node failure scenario includes the source node, the node that drops the signal will squelch traffic. The condition resolves when the node recovers.

This condition is raised with an NA severity by default. However, it indicates that traffic is squelched due to node failure (traffic outage). Traffic outages can be caused by different problems, such as multiple LOS alarms, AIS, or node power outages. MS-SQUELCH-LP is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what is causing the node isolation.

Note: MS-SQUELCH-LP is an informational condition.

MT-OCHNC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

NO-CONFIG

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The No Startup Configuration alarm applies to ML-Series Ethernet (traffic) cards and occurs when you preprovision Slot 5 to 6 and Slot 12 to 13 for the card without inserting the card first, or when you insert a card without preprovisioning. (This is an exception to the usual rule in card provisioning.) Because this is normal operation, you should expect this condition during provisioning. When the startup configuration file is copied to the active TCC2/TCC2P card, the alarm clears.

Note: For more information about the ML-Series Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the NO-CONFIG Alarm

  1. Create a startup configuration for the card in the Cisco IOS CLI.
    Follow the card provisioning instructions in the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.
  2. Upload the configuration file to the TCC2/TCC2P card by completing the following steps:
    1. In node view, right-click the ML-Series card graphic.
    2. Choose IOS Startup Config from the shortcut menu.
    3. Click Local > TCC and navigate to the file location.
  3. Complete the Reset a Traffic Card in CTC.
  4. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

NON-CISCO-PPM

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Object: PPM

The Non-Cisco PPM Inserted condition occurs when a PPM that is plugged into a card's port fails the security code check. The check fails when the PPM used is not a Cisco PPM.

Clear the NON-CISCO-PPM Condition

  1. Obtain the correct Cisco PPM and replace the existing PPM with the new one.
  2. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

NOT-AUTHENTICATED

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: SYSTEM

The NOT-AUTHENTICATED alarm is raised by CTC (not by the NE) when it fails to log into a node. This alarm only displays in CTC where the login failure occurred. This alarm differs from the "INTRUSION-PSWD" alarm in that INTRUSION-PSWD occurs when a user exceeds the login failures threshold.

Note: NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.

OCHNC-INC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OCH-TERM-INC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-1-AIS-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-2-AIS-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-3-AIS-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-4-AIS-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-AIS-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-BDI-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-LCK-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-OCI-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-SD-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-SF-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ODUK-TIM-PM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OOU-TPT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCTRM-HP, VCTRM-LP

The Out of Use Transport Failure alarm is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) This condition is raised when a member circuit in a VCAT is unused, such as when it is removed by SW-LCAS. It occurs in conjunction with the "VCG-DEG" alarm.

Clear the OOT-TPT Condition

  1. Complete the Clear the VCG-DEG Condition. Clearing that condition clears this condition as well.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

OPTNTWMIS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: NE

The Optical Network Type Mismatch alarm is raised when DWDM nodes are not configured for the same type of network, either MetroCore and MetroAccess. All DWDM nodes on the same network must be configured for the same network type because APC and automatic node setup (ANS) behave differently on each of these network types.

When the OPTNTWMIS occurs, the "APC-DISABLED" alarm could also be raised.

Note: For more information about ANS and APC, refer to the Cisco ONS 15454 DWDM Procedure Guide.

Clear the OPTNTWMIS Alarm

  1. In node view of the alarmed node, click the Provisioning > WDM-ANS > Provisioning tabs.
  2. Choose the correct option from the Network Type list box, and click Apply.
  3. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

OPWR-HDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OPWR-HFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OPWR-LDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OPWR-LFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OSRION

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-AIS

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-BDI

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-IAE

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-LOF

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-SD

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-SF

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OTUK-TIM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

OUT-OF-SYNC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PARAM-MISM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PDI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: VCMON-HP

The Payload Defect Indication condition indicating a signal label mismatch failure (SLMF) in the ONS 15454 SDH VC overhead. The condition indicates to downstream equipment that there is a defect in one or more of the directly mapped payloads contained in that circuit.

An SLMF often occurs when the payload does not match what the signal label is reporting.

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

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Warning! Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Clear the PDI Condition

  1. Verify that all circuits terminating in the reporting card are DISCOVERED by completing the following steps:
    1. Click the Circuits tab.
    2. Verify that the Status column lists the circuit as active.
    3. If the Status column lists the circuit as PARTIAL, wait 10 minutes for the ONS 15454 SDH to initialize fully. If the PARTIAL status does not change after full initialization, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.
  2. After determining that the circuit is DISCOVERED, ensure that the signal source to the card reporting the alarm is working.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the on the middle-right outside edge of the shelf assembly.
  3. If traffic is affected, complete the Delete a Circuit.
    Caution! Deleting a circuit can affect existing traffic.
  4. Recreate the circuit with the correct circuit size. Refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide for detailed procedures to create circuits.
  5. If circuit deletion and re-creation does not clear the condition, verify that there is no problem stemming from the far-end STM-N card providing payload to the reporting card.
  6. If the condition does not clear, confirm the cross-connect between the STM-N card and the reporting card.
  7. If the condition does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
  8. If the condition does not clear, complete the Physically Replace a Traffic Card for the optical or electrical cards.
    Note: When you replace a card with the identical type of card, you do not need to make any changes to the database.
  9. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PEER-NORESPONSE

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: MLMR

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. PEER-NORESPONSE is a software failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure between peer cards.

However, for ML-MR-10 cards, a peer card not responding alarm is raised if a CPP card that is active does not receive any heartbeat response from its peer card. This happens under the following conditions:

  • Peer card is not present in the ONS 15454 chassis
  • Peer card is not configured for protection
  • Protection is disabled on the peer card
  • Peer card has reset.

Clear the PEER-NORESPONSE Alarm

  1. Complete the Reset a Traffic Card in CTC for the reporting card. For the LED behavior, see the Typical Traffic Card LED Activity During Reset.
  2. Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the LED appearance: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
  3. For ML-MR-10 card, ensure that the CPP peer card has not failed, the correct protection configuration is present on both CPP cards, and protection is not disabled on the CPP peer card.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PLM-P

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Objects: STSMON, STSTRM

A Payload Label Mismatch Path alarm indicates that signal does not match its label. The condition is indicated by a problematic C2 byte value in the SDH path overhead. The alarm is raised if all of the following conditions are met:

  • The received C2 byte is not 0x00 (unequipped).
  • The received C2 byte is not a PDI value.
  • The received C2 does not match the expected C2.
  • The expected C2 byte is not 0x01 (equipped, unspecified).
  • The received C2 byte is not 0x01 (equipped, unspecified).

For example, on nodes equipped with CTC Software R4.1 and earlier, this alarm could occur when you have a DS3XM-6 card connected to a DS-3 card instead of a DS-1 card. The DS3XM-6 card expects a C2 label byte value of 01. A DS-1 card transmits this value, but a DS-3 card transmits a value of 04. The mismatch between the sent and expected values causes the PLM-P alarm.

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

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Warning! Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Clear the PLM-P Alarm

  1. Complete the Clear the PDI Condition.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the on the middle-right outside edge of the shelf assembly.
  2. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.

PMI

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ADD-OPWR-HDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ADD-OPWR-LDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ADD-OPWR-HFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

ADD-OPWR-LFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PORT-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PORT-MISMATCH

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: CEMR, FCMR

The Pluggable Port Mismatch alarm applies to FC_MR-4, ML-MR-10 and CE-MR-10 Ethernet cards, and TXP card SFP connectors. The alarm indicates that the provisioned payload for the connector does not match the SFP configuration.

The error must be resolved in the Cisco IOS CLI configuration. PORT-MISMATCH cannot be resolved in CTC. For information about provisioning the ML-MR-10 and CE-MR-10 Ethernet cards from the Cisco IOS interface, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1 800 553-2447).

PRC-DUPID

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: STMN

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

Clear the PRC-DUPID Alarm

  1. Log into a node on the ring.
  2. Complete the Identify an MS-SPRing Ring Name or Node ID Number.
  3. Repeat Step 2 for all the nodes on the ring.
  4. If two nodes have an identical node ID number, complete the Change an MS-SPRing Node ID Number so that each node ID is unique.
  5. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

PROTNA

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Protection Unit Not Available alarm is caused by a locked protection card when a TCC2/TCC2P card or cross-connect card that is provisioned as part of a protection group is not available. Unavailable protection can occur when a card is reset, but the alarm clears as soon as the card is back in service. The alarm clears if the device or facility is brought back in service.

Clear the PROTNA Alarm

  1. If the PROTNA alarm occurs and does not clear, and if the alarm is raised against a common control card (TCC2/TCC2P card), ensure that there is a redundant control card installed and provisioned in the chassis.
  2. If the alarm is raised against a line card, determine whether the ports have been taken out of service by completing the following steps:
    1. In CTC, double-click the reporting card to display the card view (if the card is not a cross-connect card).
    2. Click the Provisioning > Line tabs.
    3. Click the Admin State column of any Unlocked ports. The port is out of service if the Admin State is Locked,maintenance or Locked,disabled.
  3. If any port is out of service, choose Unlocked to put the port in service.
    Note: If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.
  4. Complete the Reset a Traffic Card in CTC for the reporting card. For the LED behavior, see the Typical Traffic Card LED Activity During Reset.
  5. Verify that the reset is complete and error-free. For LED appearance, see the Traffic Card LED Activity.
  6. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card for the reporting card.
  7. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PROV-MISMATCH

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PTIM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

PWR-FAIL-A

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Equipment Power Failure at Connector A alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the electrical connections, cross-connect cards, STM-N cards, or TCC2/TCC2P card.

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

Clear the PWR-FAIL-A Alarm

  1. If a single card has reported the alarm, take the following actions depending on the reporting card:
  2. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card.
  3. If the alarm does not clear, complete the Physically Replace a Traffic Card for the reporting card.
  4. If the single card replacement does not clear the alarm, or if multiple cards report the alarm, verify the office power. Refer to the "Install the Shelf and FMECS" chapter in the Cisco ONS 15454 SDH Procedure Guide for procedures.
  5. If the alarm does not clear, reseat the power cable connection to the connector.
  6. If the alarm does not clear, physically replace the power cable connection to the connector.
  7. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PWR-FAIL-B

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Equipment Power Failure at Connector B alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the electrical connections, cross-connect cards, STM-N cards, or TCC2/TCC2P card.

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

Clear the PWR-FAIL-B Alarm

  1. Complete the Clear the PWR-FAIL-A Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PWR-FAIL-RET-A

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Equipment Power Failure at Connector A alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the electrical connections, cross-connect cards, STM-N cards, or TCC2/TCC2P card.

Clear the PWR-FAIL-RET-A Alarm

  1. Complete the Clear the PWR-FAIL-A Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

PWR-FAIL-RET-B

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Equipment Power Failure at Connector B alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the electrical assembly, cross-connect cards, STM-N cards, or TCC2/TCC2P card.

Clear the PWR-FAIL-RET-A Alarm

  1. Complete the Clear the PWR-FAIL-A Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RAI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, DS3, E1

The Remote Alarm Indication (RAI) condition signifies an end-to-end electrical failure. The error condition is sent from one end of the SDH path to the other. RAI on the DS3i-N-12 card indicates that the far-end node is receiving a DS-3 AIS.

Clear the RAI Condition

  1. Complete the Clear the AIS Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RCVR-MISS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: DS1, E1

A Facility Termination Equipment Receiver Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance usually occurs when a receive cable is missing from the E-1 port or a possible mismatch of backplane equipment occurs, for example, an SMB connector or a BNC connector is connected to an E-1 card.

Note: E-1s are four-wire circuits and need a positive (tip) and negative (ring) connection for both transmit and receive.

Clear the RCVR-MISS Alarm

  1. Ensure that the device attached to the E-1 port is operational.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
  2. If the attachment is good, verify that the cabling is securely connected.
  3. If the cabling is good, verify that the pinouts are correct.
  4. If the pinouts are correct, replace the receive cable.
  5. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

RSV-RT-EXCD-RINGLET0

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The Reserved Bandwidth Exceeds Link Rate on Ringlet Zero alarm is raised by an ML-1000 card if the sum the of reserved bandwidth configured on each station of ringlet 0 is greater then the link rate (circuit bandwidth). The alarm clears when the sum of the reserved bandwidth on each station falls below the link rate. In the case of SW-LCAS or LCAS circuits, the link rate is the working link rate, which will change when members are removed

RSV-RT-EXCD-RINGLET0 does not suppress any alarms, but it is suppressed by the "RPR-PASSTHR" alarm.

Clear the RSV-RT-EXCD-RINGLET0 Alarm

  1. At the CLI command prompt in privileged executive mode, enter the following command:
    router#show rpr-ieee topology detail
    This command's output shows the configured reserved bandwidth rate from each station.
  2. Reduce the reserved bandwidth on the alarmed station until the error clears. Enter the following CLI command in IEEE 802.17b-based RPR interface configuration mode:
    router (config-if)#rpr-ieee tx-traffic rate-limit reserved
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

RSV-RT-EXCD-RINGLET1

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The Reserved Bandwidth Exceeds Link Rate on Ringlet One alarm is raised by an ML-1000 card if the sum the of reserved bandwidth configured on each station of ringlet 1 is greater then the link rate (circuit bandwidth). The alarm clears when the sum of the reserved bandwidth on each station falls below the link rate. In the case of SW-LCAS or LCAS circuits, the link rate is the working link rate, which will change when members are removed

RSV-RT-EXCD-RINGLET1 does not suppress any alarms, but it is suppressed by the "RPR-PASSTHR" alarm.

Clear the RSV-RT-EXCD-RINGLET1 Alarm

  1. At the CLI command prompt in privileged executive mode, enter the following command:
    router#show rpr-ieee topology detail
    This command's output shows the configured reserved bandwidth rate from each station.
  2. Reduce the reserved bandwidth on the alarmed station until the error clears. Enter the following CLI command in IEEE 02.17b-based RPR interface configuration mode:
    router (config-if)#rpr-ieee tx-traffic rate-limit reserved
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

RFI

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

RFI-L

The RFI-L condition is not used in this platform in this release. It is reserved for development.

RFI-V

The RFI-V condition is not used in this platform in this release. It is reserved for development.

RING-ID-MIS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: STMN
DWDM Logical Object: OSC-RING

The Ring Name Mismatch condition refers to the ring OSC in APC. It occurs when a ring name does not match other detectable node ring names, and can cause problems with applications that require data exchange with APC. This alarm is somewhat similar to RING-MISMATCH, which applies to MS-SPRings, but instead of applying to ring protection, it applies to DWDM node discovery within the same network.

Note: For more information about APC, refer to the Cisco ONS 15454 DWDM Procedure Guide.

Clear the RING-ID-MIS Alarm

  1. Complete the Clear the RING-MISMATCH Alarm.
  2. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RING-MISMATCH

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: STMN

A Procedural Error Mismatched Ring alarm occurs when the ring name of the ONS 15454 SDH that is reporting the alarm does not match the ring name of another ONS node in the MS-SPRing. ONS nodes connected in an MS-SPRing must have identical ring names to function.

Note: This alarm can also be expected when upgrading to Release 7.2 when the ring identifier is updated.

Clear the RING-MISMATCH Alarm

  1. Log into the first node in the ring.
  2. Verify the ring name. Complete the Identify an MS-SPRing Ring Name or Node ID Number.
  3. Note the name in the Ring Name field.
  4. Log into the next ONS node in the MS-SPRing.
  5. Verify the ring name. Complete the Identify an MS-SPRing Ring Name or Node ID Number.
  6. If the ring name matches the ring name in the reporting ONS node, repeat Step 5 for the next ONS node in the MS-SPRing.
  7. Complete the Change an MS-SPRing Ring Name.
  8. Verify that the ring map is correct.
  9. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a Service-Affecting (SA) problem.

RING-SW-EAST

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Ring Switch Is Active East Side condition occurs when a ring switch occurs at the east side of a MS-SPRing using a Force Ring command. The condition clears when the switch is cleared. RING-SW-EAST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an "F" on the network view detailed circuit map.

Note: RING-SW-EAST is an informational condition. The condition does not require troubleshooting.

RING-SW-WEST

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Ring Switch Is Active West Side condition occurs when a ring switch occurs at the west side of a MS-SPRing using a Force Ring command. The condition clears when the switch is cleared. RING-SW-WEST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an "F" on the network view detailed circuit map.

Note: RING-SW-WEST is an informational condition. The condition does not require troubleshooting.

ROLL

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-HP, VCMON-LP, VCTRM-HP, VCTRM-LP

The ROLL condition indicates that circuits are being rolled. This is typically carried out to move traffic for a maintenance operation or to perform bandwidth grooming. The condition indicates that a good signal has been received on the roll destination leg, but the roll origination leg has not yet been dropped. The condition clears when the roll origination leg is dropped.

Note: ROLL is an informational condition and does not require troubleshooting.

ROLL-PEND

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-HP, VCMON-LP, VCTRM-HP, VCTRM-LP

ROLL-PEND indicates that a roll process has been started, but a good signal has not been received yet by the roll destination leg. This condition can be raised individually by each path in a bulk circuit roll.

The condition clears when a good signal has been received on the roll destination leg.

Note: ROLL-PEND is an informational condition and does not require troubleshooting.

ROUTE-OVERFLOW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Objects: NE
DWDM Logical Object: NE regardless of MSTP or MSPP

The ROUTE-OVERFLOW indicates the condition when the OSPF routing table exceeds 700 routes. The symptoms for this condition are loss of visibility to a node or network, inability to access a node using CTC, CTM, Telnet, Ping, and so on.

Clear the ROUTE-OVERFLOW Condition

  1. Reconfigure the OSPF network to less than 700 routes.

RPR-PASSTHR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: RPRIF

The IEEE 802.17b-based RPR Interface in Pass-Through Mode condition indicates that an ML card's RPR-IEEE interface is not participating in a ring. Instead, the card is behaving like a passive device that allows the signal to transit but does not manipulate it. Pass-through mode itself is hitless.

You can manually place an ML card into (or out of) pass-through mode using the Cisco IOS CLI command SHUTDOWN (SHUT) for such reasons as adding, removing, or servicing the node. To do so is hitless.

The ML-1000 automatically enters pass-through mode if either of the following conditions is true:

  • Redundant interconnect (RI) is configured and the ML card is in primary mode (that is, single traffic queue mode), standby state.
  • RI is configured and the RI interface goes down during the "WTR" alarm, while the ML card is in secondary mode (that is, dual traffic queue mode) on a Cisco proprietary RPR ring.

Note: For GFP and HDLC mode, the ML card shutdown (SHUT) command causes an "AU-AIS" alarm to be sent to the peer. But in IEEE 802.17b-based RPR mode the "AU-AIS" alarm is not inserted toward the peer.

The RPR-PASSTHR condition suppresses the following alarms:

If RPR-PASSTHR is raised-meaning that this RPR-IEEE interface is not available-one or more of its peer nodes might raise the "RPR-PEER-MISS" alarm. RPR-PASSTHR does not suppress the "RPR-PEER-MISS" alarm or the "RPR-RI-FAIL" alarm.

Clear the RPR-PASSTHR Condition

  1. If the ML card was manually configured shut down using the CLI command SHUTDOWN (SHUT), enter the following command at the command prompt:
    router#no shut
  2. If the card is in pass-through mode due to being in an RI primary mode standby state, either the IEEE 802.17b-based RPR interface is down or the interconnect interface is down. You must clear the root cause of either problem to clear the pass-through. To trace the root cause problem in the RPR-IEEE interface setup, enter the following CLI command in privileged executive mode:
    router#show interface rpr-ieee 0
  3. View the command output and locate the RI information line. It displays the name of the monitored interfaces as "monitoring ring interface," or "monitoring interconnect interface."
  4. Locate and clear any trouble on the monitored interface. Trouble might be indicated on that interface through previous alarms that occurred before RPR-PASSTHR was raised.
  5. If the card is in pass-through mode while in RI secondary mode when the interconnect fails, pass-through mode should clear automatically in 60 seconds.
  6. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-PEER-MISS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The IEEE 802.17b-based RPR Peer Node Is Missing condition is raised by an ML card when RI is configured on the card, but this station does not detect its peer station in the topology. The condition clears when the peers detect each other.

Clear the RPR-PEER-MISS Condition

  1. Determine whether the peer MAC address is properly configured by completing the following steps:
    1. Enter the following CLI command in privileged executive mode:
      router# show interface rpr-ieee 0
      This command's output will include information, similar to the following, about the RPR-IEEE interface raising the condition:
      Hardware is RPR-IEEE Channelized SDH, address is 000e.8312.bcf0 (bia 000e.87312.bfc0)
    2. Verify that the alarmed interface's configured peer MAC address is the correct MAC address for the peer card. A card in primary mode need to list the peer MAC address of the card operating in secondary mode; the secondary card needs to list the peer MAC address of the primary card. Peer MAC address information is contained in the same "show interface rpr-ieee 0" command output. In the following line example, the RPR-IEEE interface raising the alarm is primary; it is in active mode, and its configured peer, the secondary card, is MAC address 000e.8312.b870:
      RI: primary,active peer mac 000e.8312.b870
      Note: The primary and secondary cards do not have to be neighbors on the ring.
      Note: If RI is configured, then RI information is displayed in the "show interface rpr 0" output.
      To correct the MAC address configuration, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide for procedures.
  2. If the condition does not clear, enter the following command in privileged executive mode:
    router# show rpr-ieee protection
  3. The command output, similar to the following lines, shows whether any protection switches are active:
    West Span Failures: none
    East Span Failures: none
    A protection switch can cause an RPR-PEER-MISS condition. You may also see the "RPR-PROT-ACTIVE" alarm raised for a span. Clear any protection issues.
  4. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-PROT-ACTIVE

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: RPRIF

The IEEE 802.17b-based RPR Protection is Active condition, raised by the ML card, indicates that ring protection is active and that steering protection as defined in IEEE 802.17b is active.

IEEE 802.17b-based RPR provides hitless protection switching for all protected traffic on a ring. Its steering protection mechanism ensures that each station receives span change information (such as fail or restoration) in time to make protection switching decisions within the 50-millisecond time frame.

The condition clears when steering protection is no longer active.For more information about steering, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

This condition is suppressed by the "RPR-PASSTHR" alarm.

Clear the RPR-PROT-ACTIVE Condition

  1. Locate and clear any service-affecting SDH error that might have caused a protection switch, in turn triggering the RPR-PROT-ACTIVE condition. Clearing the SDH condition will clear RPR-PROT-ACTIVE.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-PROT-CONFIG-MISM

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The IEEE 802.17b-based RPR Protection Configuration Mismatched alarm is raised by an ML card when it detects that its steering protection scheme is mismatched with other vendors' equipment configured for wrapping protection. The ONS 15454 SDH does not support IEEE 802.17's optional wrapping scheme.

The alarm clears when the other vendor's equipment configuration is changed to utilize steering protection.

RPR-PROT-CONFIG-MISM is suppressed by the "RPR-PASSTHR" alarm.

Clear the RPR-PROT-CONFIG-MISM Alarm

  1. You cannot clear this alarm from the ONS 15454 SDH; rather, it is caused by incompatible vendor equipment configuration. See that equipment's support information to correct the configuration for steering instead of wrapping. This, in turn, will cause RPR-PROT-CONFIG-MISM to clear.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-RI-FAIL

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: RPRIF

The IEEE 802.17b-based RPR RI Fail condition is raised by an ML card in primary or secondary mode. If a card is in primary mode, a Gigabit Ethernet interface can cause an interconnect interface (IC) failure. (The IC includes the Gigabit Ethernet interface and possibly a port channel interface.) In primary mode, RPR-RI-FAIL can also be raised in response to a downed ring interface. In secondary mode, the only possible cause of this condition is IC failure.

The alarm clears when the RPR-IEEE interface returns to Init modes and faults, if present, are cleared. RPR-RI-FAIL is suppressed by the "RPR-PASSTHR" alarm.

Clear the RPR-RI-FAIL Condition

  1. If the card is in primary mode, enter the following command at the CLI in privileged executive mode:
    router# show interface rpr-ieee 0
  2. The RI information line displays the name of the monitored interfaces and says either "monitoring ring interface," or "monitoring interconnect interface."
  3. Determine why the monitored interface is down. It can occur because the ring interface has been shut down using the "shutdown" CLI command, or because both SDH circuits are down or Locked,disabled.
  4. If correcting the previous problem on a primary interface does not clear the condition, or if the condition is raised on a card is secondary mode, the IC failure root cause must be corrected. This can be due to a fiber pull, having link protocol down, or shut down interfaces.
    • Link state is indicated in the "show interface rpr-ieee 0" output on the following line:
    RPR-IEEE0 is up, line protocol is up
    • A shutdown is indicated if a node is in pass-through mode. The same command output indicates whether or not this is the case:
    MAC passthrough not set
  5. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-SD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: ML100T, ML1000, MLFX

The IEEE 802.17b-based RPR Signal Degrade condition indicates that a minor signal degradation has occurred on an RPR-IEEE ring that, if not overridden, can deactivate the link.The RPR-SD condition is reported if the SDH "SDBER-EXCEED-HO" alarm, is raised on the circuit which carries the span. The RPR-SD condition clears when the SDH signal degrade clears.

RPR-SD suppresses the "MAN-REQ" alarm (for the ML object) and the "WTR" alarm (for the ML object).

It is suppressed by the following alarms:

Clear the RPR-SD Condition

  1. Complete the Clear the SDBER-EXCEED-HO Condition to clear this secondary condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-SF

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: ML100T, ML1000, MLFX

The IEEE 802.17b-based RPR Signal Fail condition indicates a signal loss or major signal degradation that deactivates the RPR-IEEE link. The failure that raises RPR-SF can be attributable to any of the following alarms:

The RPR-SF condition can also occur if a SDH circuit's state is UNASSIGNED (not provisioned).

This condition clears when these primary cause alarms are cleared. RPR-SF is suppressed by the "RPR-PASSTHR" alarm or the "FORCED-REQ" alarm (for the ML object). RPR-SF itself suppresses the following alarms:

Clear the RPR-SF Condition

  1. Complete the trouble-clearing procedure in this chapter for any primary cause SDH failure condition as previously listed.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPR-SPAN-MISMATCH

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: ML100T, ML1000, MLFX

The IEEE 802.17b-based RPR-SPAN-MISMATCH alarm is caused by span misprovisioning, span forced switching, physical miscabling, or a circuit loopback.

If a traffic-affecting issue such as the "AU-AIS" alarm, the "GFP-LFD" alarm, the "AU-LOP" alarm, the "HP-RFI" alarm, or the "HP-UNEQ" alarm occurs, it suppresses RPR-SPAN-MISMATCH.

Miscabling problems between this node's east or west span and its neighboring span in the same direction can also cause this alarm, as will provisioning an XC loopback on a circuit that carries IEEE 802.17b-based RPR-IEEE traffic.

Note: Clearing a circuit XC loopback does not always cause the loopback to clear. If this is the case, a FORCE switch is used to clear the RPR-SPAN-MISMATCH alarm. The FORCE might cause a traffic hit.

RPR- SPAN-MISMATCH is suppressed by the "RPR-PASSTHR" alarm.

Clear the RPR-SPAN-MISMATCH Alarm

  1. Locate and clear any primary cause provisioning errors.
  2. If the alarm does not clear, locate and correct any span cabling errors.
  3. If the alarm does not clear, look for and clear XC loopbacks on the spans.
  4. If the alarm does not clear, configure a FORCE switch on the 802.17b-based RPR span and then clear the switch. To do this, enter the following CLI command in RPR-IEEE interface provisioning mode:
    router(config)#rpr-ieee protection request forced-switch {east | west}
    Clear the switch by entering the following command:
    router(config)#no rpr-ieee protection request forced-switch {east | west}
  5. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RPRW

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: ML100T, ML1000, MLFX

The Cisco proprietary RPR Wrapped condition applies to CE100T-8 and ML-Series cards and occurs when the RPR protocol initiates a ring wrap due to a fiber cut, node failure, node restoration, new node insertion, or other traffic problem. It can also be raised if the POS port is Admin down condition. (In this case, you will not see any SDH-level or TPTFAIL alarms.)

When the wrap occurs, traffic is redirected to the original destination by sending it in the opposite direction around the ring after a link state change or after receiving any SDH path-level alarms.

Clear the RPRW Condition

  1. Look for and clear any service-affecting SDH path-level alarms on the affected circuit, such as the "AU-LOP" alarm , "LOS (TRUNK)" alarm, or the "HP-TIM" alarm. Clearing this alarm can also clear RPRW.
  2. If the condition does not clear, look for and clear any service alarms for the ML-Series card itself, such as the "CARLOSS (CEMR, CE100T, CE1000)" alarm, "CARLOSS (ML100T, ML1000, MLFX)" alarm, "TPTFAIL (CEMR, CE100T, CE1000)" alarm, or the "TPTFAIL (ML100T, ML1000, MLFX)" alarm.
  3. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

RS-TIM

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Object: STMN

The Regenerator Section TIM alarm occurs when the expected J0 path trace string does not match the received string.

If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Follow the procedure below to clear either instance.

A TIM is usually accompanied by other alarms, such as the "LOS (STM1E, STMN)" alarm. If so, reattach or replace the original cables/fibers to clear the alarms.

Clear the RS-TIM Alarm

  1. Complete the Clear the TIM Alarm for the J0 byte.
  2. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

RUNCFG-SAVENEED

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

The Run Configuration Save Needed condition occurs when you change the running configuration file for ML-Series cards. RUNCFG-SAVENEED is a reminder that you must save the change to the startup configuration file permanently.

The condition clears after you save the running configuration to the startup configuration, such as by entering:

copy run start

at the privileged EXEC mode of the Cisco IOS CLI. If you do not save the change, the change is lost after the card reboots. If the command "copy run start" is executed in configuration mode and not privileged EXEC mode, the running configuration will be saved, but the alarm will not clear

Note: For more information about the ML-Series Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

SD (DS1, DS3, E1, E3, E4, STMN)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, DS3, E1, E3, E4, STMN

A Signal Degrade (SD) condition occurs on optical STM-N lines and the low-order path termination when the quality of the signal is so poor that the BER on the incoming optical line passed the signal degrade threshold. Signal degrade is defined by the ITU as a "soft failure" condition. SD and SF both monitor the incoming BER and are similar, but SD is triggered at a lower bit error rate than SF.

An SD condition occurs for STM-N cards and the low-order path termination when the BER on the incoming optical line has passed the signal failure threshold in the range of 1E-9 dBm to 1E-5 dBm. For unprotected circuits, the BER threshold value is not user-provisionable and the error rate is set to a Telcordia GR-253-CORE specification of 1E-6 dBm.

The SD condition travels on the B2 byte of the multiplexing section SDH overhead. The condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice. SD can also be caused by repeated cross-connect card switches that in turn can cause switching on the lines or paths.

Warning! On the OC192 LR/STM64 LH 1550 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). Statement 293

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Warning! Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Note: Some levels of BER errors (such as 1E-9 dBm) take a long period to raise or clear, about 9,000 seconds, or 150 minutes. If the SD threshold is provisioned at 1E-9 dBm rate, the SD alarm requires at least one and one-half hours to raise and then another period at least as long to clear.

Note: The recommended test set for use on all SDH ONS electrical cards (except E1 cards) is the Omniber 718. The FireBerd test set is recommended for testing E1 cards.

Clear the SD (DS3, E1, E3, E4, STMN) Condition

  1. Verify that the user-provisionable BER threshold is set at the expected level. Complete the Clear an STM-N Card Facility or Terminal Loopback Circuit or Clear a Non-STM Card Facility or Terminal Loopback Circuit, as required.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
  2. With an optical test set, measure the power level of the line to ensure that the power is within guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
  3. Verify that optical receive levels are within the acceptable range. These are listed in the Optical Card Transmit and Receive Levels.
  4. If the receive levels are out of range, clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
  5. Verify that single-mode fiber is used.
  6. Verify that a single-mode laser is used at the far-end node.
  7. If the problem persists, the transmitter at the other end of the optical line could be failing and require replacement.
  8. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SD (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SDBER-EXCEED-HO

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-HP, VCTRM-HP

The Signal Degrade Threshold Exceeded for High Order condition indicates that the signal degrade BER threshold has been exceeded for a high-order (VC-4) path on optical (traffic) cards. SDBER-EXCEED-HO occurs when the signal BER falls within the degrade threshold (typically 1E-7 dBm) set on the node.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the SDBER-EXCEED-HO Condition

  1. Determine the BER threshold. Complete the Clear an STM-N Card Facility or Terminal Loopback Circuit.
  2. If adjustment is acceptable in site practices, adjust the threshold.
    Using an optical test set, measure the input power level of the line and ensure that the level is within the guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
  3. Verify the input fiber cable connections to the reporting card.
  4. Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
    If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the condition applies to VCMON-HP, it is Service-Affecting (SA).

SDBER-EXCEED-LO

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-LP, VCTRM-LP

The Signal Degrade Threshold Exceeded for Low Order condition indicates that the signal degrade BER threshold has been exceeded for a low-order (VC-4) path on optical (traffic) cards. SDBER-EXCEED-LO occurs when the signal BER falls within the degrade threshold (typically 1E-7 dBm) set on the node.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the SDBER-EXCEED-LO Condition

  1. Determine the BER threshold. Complete the Clear an STM-N Card Facility or Terminal Loopback Circuit.
  2. If adjustment is acceptable in site practices, adjust the threshold.
    Using an optical test set, measure the input power level of the line and ensure that the level is within the guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
  3. Verify the input fiber cable connections to the reporting card.
  4. Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
    If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the condition applies to VCMON-HP, it is Service-Affecting (SA).

SD-L

The Signal Degrade Line alarm is not used in this platform for this release. It is reserved for development.

SF (DS1, DS3, E1, E3, E4, STMN)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, DS3, E1, E3, E4, STMN

A Signal Failure (SF) condition occurs on optical STM-N cards and the low-order path termination when the BER on the incoming optical line has passed the signal failure threshold in the range of 1E-5 dBm to 1E-3 dBm. The condition travels on the B2 byte of the multiplexing section SDH overhead; this condition causes a protection switch at the line (facility) level.

The SF condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. 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.

Signal failure is defined by the ITU as a "hard failure" condition. SD and SF both monitor the incoming BER error rate and are similar, but SF is triggered at a higher BER than SD.

Warning! On the OC192 LR/STM64 LH 1550 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). Statement 293

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Warning! Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Clear the SF (DS3, E1, E3, E4, STMN) Condition

  1. Verify that the user-provisionable BER threshold is set at the expected level. Complete the Clear an STM-N Card Facility or Terminal Loopback Circuit.
  2. Using an optical test set, measure the power level of the line and ensure that the level is within the guidelines. For specific procedures to use the test set equipment, consult the manufacturer.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
  3. Verify that the optical receive levels are within the acceptable range.
  4. Clean the fibers at both ends according to site practice for a line signal failure. If no site practice exists, complete the procedure for cleaning optical connectors in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
  5. Verify that single-mode fiber is being used.
  6. If the problem persists, the transmitter at the other end of the optical line could be failing and need replacement.
  7. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SF (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SFBER-EXCEED-HO

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-HP, VCTRM-HP

The Signal Failure Threshold Exceeded for High Order condition occurs when the signal fail BER threshold has been exceeded for a high-order (VC-4 or VC-3) path on optical (traffic) cards. SFBER-EXCEED-HO occurs when the signal BER falls past the fail threshold (typically 1E-4 dBm) set on the node.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the SFBER-EXCEED-HO Condition

  1. Determine the BER threshold by clicking the card reporting the condition, and clicking the Provisioning tab.
  2. If adjustment is acceptable in site practices, adjust the threshold.
  3. Verify the input power levels to the reporting card.
  4. Verify input fiber cable connections to the reporting card.
  5. Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
    If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the condition applies to the VCTRM-HP object, it is Service-Affecting (SA).

SFBER-EXCEED-LO

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-LP, VCTRM-LP

The Signal Failure Threshold Exceeded for High Order condition occurs when the signal fail BER threshold has been exceeded for a high-order (VC-4 or VC-3) path on optical (traffic) cards. SFBER-EXCEED-HO occurs when the signal BER falls past the fail threshold (typically 1E-4 dBm) set on the node.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the SFBER-EXCEED-HO Condition

  1. Determine the BER threshold by clicking the card reporting the condition, and clicking the Provisioning tab.
  2. If adjustment is acceptable in site practices, adjust the threshold.
  3. Verify the input power levels to the reporting card.
  4. Verify input fiber cable connections to the reporting card.
  5. Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.
    If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the condition applies to the VCTRM-HP object, it is Service-Affecting (SA).

SF-L

The Signal Fail Line alarm is not used in this platform for this release. It is reserved for development.

SFTWDOWN

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: EQPT

A Software Download in Progress alarm occurs when the TCC2/TCC2P card is downloading or transferring software.

No action is necessary. Wait for the transfer or the software download to complete. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

Caution! Updating software on a standby TCC2/TCC2P card can take up to 30 minutes. Wait the full time period before removing the card. Premature removal can cause flash corruption.

Note: When you upgrade a TCC2 to card to a TCC2P, the SFTWDOWN alarm can be raised and cleared more than once before the software download is complete. For example, when you remove the standby TCC2 card in Slot 11 and replace it with a TCC2P card, the SFTWDOWN alarm occurs within moments of this replacement. It can briefly clear and then raise again before it is finally cleared at the end of the upgrade process.

Note: SFTWDOWN is an informational alarm and does not require troubleshooting.

SHELF-COMM-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SH-IL-VAR-DEG-HIGH

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SH-IL-VAR-DEG-LOW

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SHUTTER-OPEN

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SIGLOSS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: FCMR
DWDM Logical Objects: ESCON, FC, GE, ISC, TRUNK

The Signal Loss on Data Interface alarm is raised on FC_MR-4 card receive client ports and MXP card FC and ISC client data ports when there is a loss of signal. (Loss of Gigabit Ethernet client signal results in a CARLOSS [GE], not SIGLOSS.) SIGLOSS can also be raised on the MXP trunk port.

If the SYNCLOSS alarm was previously raised on the port, the SIGLOSS alarm will demote it.

Clear the SIGLOSS Alarm

  1. Ensure that the data port connection at the near-end card's port of the SDH link is operational.
  2. Verify fiber continuity to the port. To verify fiber continuity, follow site practices.
  3. Check the physical port LED on the card. The port LED looks clear (that is, not lit green) if the link is not connected.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a Service-Affecting (SA) problem.

SNTP-HOST

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: NE

The Simple Network Time Protocol (SNTP) host failure alarm indicates that an ONS node serving as an IP proxy for the other ONS nodes in the ring is not forwarding SNTP information to the other ONS nodes in the network. The host failure can result from two causes: the IP network attached to the ONS proxy node is experiencing problems, or the ONS proxy node itself is not functioning properly.

Clear the SNTP-HOST Alarm

  1. Ping the SNTP host from a workstation in the same subnet to ensure that communication is possible within the subnet by completing the procedure in the Verify PC Connection to the ONS 15454 SDH (ping).
  2. If the ping fails, contact the network administrator that manages the IP network that supplies the SNTP information to the proxy and determine whether the network is experiencing problems which could affect the SNTP server/router connecting to the proxy ONS 15454 SDH.
  3. Ensure that the ONS 15454 SDH is provisioned correctly by completing the following steps:
    1. In node view of the ONS node serving as the proxy, click the Provisioning > General tabs.
    2. Ensure that the Use NTP/SNTP Server check box is checked.
    3. If the Use NTP/SNTP Server check box is not checked, check it.
    4. Ensure that the correct server name is entered in the NTP/SNTP Server field.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SPANLEN-OUT-OF-RANGE

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SPAN-SW-EAST

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Span Switch Is Active East Side condition occurs when a span switch occurs at the east side of a four-fiber MS-SPRing span using a Force Span command. The condition clears when the switch is cleared. SPAN-SW-EAST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Span was applied shows an "F" on the network view detailed circuit map.

Note: SPAN-SW-EAST is an informational condition. The condition does not require troubleshooting.

SPAN-SW-WEST

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Span Switch Is Active West Side condition occurs when a span switch occurs at the west side of a four-fiber MS-SPRing span using a Force Span command. The condition clears when the switch is cleared. SPAN-SW-WEST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Span was applied shows an "F" on the network view detailed circuit map.

Note: SPAN-SW-WEST is an informational condition. The condition does not require troubleshooting.

SQUELCH

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN

The Ring Squelching Traffic condition occurs in an MS-SPRing when a node that originates or terminates VC circuits fails or is isolated by multiple fiber cuts or maintenance FORCE RING commands. The isolation or failure of the node disables the circuits that originate or terminate on the failed node. Squelch conditions appear on one or both of the nodes on either side of the isolated/failed node. The AU-AIS condition also appears on all nodes in the ring, except the isolated node.

Warning! On the OC192 LR/STM64 LH 1550 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). Statement 293.

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Warning! Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Clear the SQUELCH Condition

  1. Determine the isolated node by completing the following steps:
    1. In node view, click View > Go to Network View.
    2. The grayed out node with red spans is the isolated node.
  2. Verify fiber continuity to the ports on the isolated node. To verify fiber continuity, follow site practices.
  3. If fiber continuity is good, verify that the proper ports are in service by completing the following steps:
    1. Confirm that the LED is correctly illuminated on the physical card.
      A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
    2. To determine whether the STM-N port is in service, double-click the card in CTC to display the card view.
    3. Click the Provisioning > Line tabs.
    4. Verify that the Admin State column lists the port as Unlocked.
    5. If the Admin State column lists the port as Locked,maintenance or Locked,disabled, click the column and choose Unlocked. Click Apply.
      Note: If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.
  4. If the correct ports are in service, use an optical test set to verify that a valid signal exists on the line.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
    For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
  5. If the signal is valid, verify that the power level of the optical signal is within the optical card receiver specifications. Refer to the Cisco ONS 15454 SDH Reference Manual for card specifications.
  6. If the receiver levels are acceptable, ensure that the optical transmit and receive fibers are connected properly.
  7. If the connectors are acceptable, complete the Physically Replace a Traffic Card for the STM-N card.
    Note: When you replace a card with the identical type of card, you do not need to make any changes to the database.
  8. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SQUELCHED

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: STMN
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Client Signal Squelched condition is raised by a TXP_MR_10G, TXP_MR_10E, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_2.5G, or MXPP_MR_2.5G card.

The condition can be raised in the following situations:

  • An MXP or TXP client facility detects that an upstream receive facility has experienced a loss of signal (such as an Ethernet CARLOSS, DWDM SIGLOSS, or optical LOS). In response, the facility's transmit is turned off (SQUELCHED). The upstream receive facilities are the trunk receive on the same card as the client, as well as the client receive on the card at the other end of the trunk span.
  • The client will squelch if the upstream trunk receive (on the same card) experiences a SIGLOSS, Ethernet CARLOSS, LOS, or LOS (TRUNK) alarm. In some transparent modes, the client is squelched if the trunk detects an AIS condition or a TIM alarm.
  • The client will squelch if the upstream client receive (on the card at the other end of the DWDM span) experiences CARLOSS, SIGLOSS, or LOS.

In an example situation, an upstream MXP_2.5G_10G client port receive experiences a "loss of light," and this port raises CARLOSS, SIGLOSS, or LOS (determined by the payload type) locally. The port also sends client signal fail (GFP-CSF) to its downstream card. The downstream card raises a GFP-CSF alarm, turns off the client transmit laser, and raises the SQUELCHED condition.

The local client raises SQUELCHED if it also raises one of the following alarms for the client, all of which are signalled by the upstream node:

On the MXP_MR_10G, the local client raises a SQUELCHED condition if the upstream client detects one of the following alarms. Note that no corresponding local alarm is raised to indicate which of these conditions is present upstream.

The local client raises a SQUELCHED condition if the local trunk raises one of the following alarms:

When troubleshooting the SQUELCHED condition locally, look for failures progressing upstream in the following order. (If you are troubleshooting this alarm remotely, reverse the order of progress.)

  • Local client alarms, as above
  • Local trunk alarms, as above
  • Remote (upstream) client receive alarms, as above

Note: If you see a SQUELCHED condition on the trunk, this can only be caused by a transponder (TXP) card.

Note: For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.

Clear the SQUELCHED Condition

  1. If the object is reported against any object besides ESCON, determine whether the remote node and local node reports and LOF or the LOS alarm (for the client trunk, as listed above). If it does, turn to the relevant section in this chapter and complete the troubleshooting procedure.
  2. If no LOF or LOS is reported, determine whether any other listed remote node or local node conditions as listed above has occurred. If so, turn to the relevant section of this chapter and complete the troubleshooting procedure.
  3. If none of these alarms is reported, determine whether the local port reporting the SQUELCHED condition is in loopback. (You will see LPBKFACILITY OR LPBKTERMINAL in the condition window for this port.) If it is in loopback, complete the following steps:
    1. Double-click the client card to open the card view.
    2. Click the Maintenance > Loopback > Port tabs.
    3. If the port Admin State column says locked,Maintenance or locked,Disabled, click the cell to highlight it and choose Unlocked from the drop-down list. Changing the state to Unlocked also clears any loopback provisioned on the port.
  4. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

SQM

Default Severity: Critical (CR), Service-Affecting (SA) for VCTRM-HP; Major (MJ), Service-Affecting (SA) for VCTRM-LP
SDH Logical Objects: VCTRM-HP, VCTRM-LP

The Sequence Mismatch alarm is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when the expected sequence numbers of VCAT members do not match the received sequence numbers.

Clear the SQM Alarm

  1. For the errored circuit, complete the Delete a Circuit.
  2. Recreate the circuit using the procedure in the "Create Circuits and VT Tunnels" chapter of the Cisco ONS 15454 SDH Procedure Guide.
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

SSM-DUS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, DS1, E1, STMN
DWDM Logical Object: TRUNK

The Synchronization Status Messaging (SSM) Quality level Changed to Do Not Use (DUS) occurs when the synchronization status message (SSM) quality level degrades to DUS or is manually changed to DUS.

The signal is often manually changed to DUS to prevent timing loops from occurring. Sending a DUS prevents the timing from being reused in a loop. SSM-DUS can also be sent for line maintenance testing.

Note: SSM-DUS is an informational condition alarm. The condition does not require troubleshooting.

SSM-FAIL

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, E1, STMN
DWDM Logical Object: TRUNK

The SSM Failed BITS or STM-N alarm occurs when the SSM byte (S1 byte) of the SDH overhead multiplexing section received by the ONS 15454 SDH has failed. The problem is external to the ONS 15454 SDH.This alarm indicates that although the ONS 15454 SDH is set up to receive SSM, the timing source is not delivering valid SSM messages.

Clear the SSM-FAIL Alarm

  1. Verify that SSM is enabled on the external timing source.
  2. Use an optical test set to determine that the external timing source is delivering the SSM (S1) byte. For specific procedures to use the test set equipment, consult the manufacturer.
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SSM-LNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, NE-SREF, STMN
DWDM Logical Object: TRUNK

The SSM Local Node Clock (LNC) Traceable condition occurs when the SSM (S1) byte of the SDH overhead multiplexing section has been changed to signify that the line or BITS timing source SSM quality level is G812L.

Note: SSM-LNC is an informational condition. The condition does not require troubleshooting.

SSM-OFF

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, DS1, E1, STMN
DWDM Logical Object: TRUNK

The SSM Off BITS or STM-N condition applies to references used for timing the node. SSM-OFF occurs when the SSM (S1) byte of the SDH overhead multiplexing section for this reference has been turned off. The ONS 15454 SDH is set up to receive SSM, but the timing source is not delivering SSM messages.

SSM is an SDH protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH multiplex section overhead. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

To clear the condition, complete the Clear the SSM-FAIL Alarm. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SSM-PRC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, NE-SREF, STMN
DWDM Logical Object: TRUNK

The SSM Primary Reference Clock (PRC) Traceable condition occurs when the SDH overhead multiplexing section S1 byte indicates that the line or BITS timing source SSM quality level is G811.

Note: SSM-PRC is an informational condition. The condition does not require troubleshooting.

SSM-PRS

The SSM Primary Reference Source (PRS) Traceable condition is not used in this platform in this release. It is reserved for development.

SSM-RES

The SSM Reserved (RES) For Network Synchronization Use condition is not used in this platform in this release. It is reserved for development.

SSM-SDH-TN

The SSM-SDH-TN condition is not used in this platform in this release. It is reserved for development.

SSM-SETS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, NE-SREF, STMN
DWDM Logical Object: TRUNK

The SSM Synchronous Equipment Timing Source (SETS) Traceable condition occurs when the SSM (S1) byte indicates that the line or BITS timing source has changed to SETS.

Note: SSM-SETS is an informational condition. The condition does not require troubleshooting.

SSM-SMC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

SSM-ST2

The SSM Stratum 2 (ST2) Traceable condition is not used in this platform in this release. It is reserved for development.

SSM-ST3

The SSM Stratum 3 (ST3) Traceable condition is not used in this platform in this release. It is reserved for development.

SSM-ST3E

The SSM Stratum 3E (ST3E) Traceable condition is not used in this platform in this release. It is reserved for development.

SSM-ST4

The SSM Stratum 4 (ST4) Traceable condition is not used in this platform in this release. It is reserved for development.

SSM-STU

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: BITS, E1, NE-SREF, STMN
DWDM Logical Object: TRUNK

The SSM Synchronization Traceability Unknown (STU) BITS or STM-N condition occurs when the reporting node is timed to a reference that does not report the SSM S1 byte, but the ONS 15454 SDH has SSM support enabled. STU also occurs if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15454 SDH.

Clear the SSM-STU Condition

  1. Click the Provisioning > Timing > BITS Facilities tabs.
  2. Complete one of the following depending upon the status of the Sync Messaging Enabled check box:
    • If the Sync. Messaging Enabled check box for the BITS source is checked, uncheck the box.
    • If the Sync. Messaging Enabled check box for the BITS source is not checked, check the box.
  3. Click Apply.
  4. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SSM-TNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: NE-SREF, STMN
DWDM Logical Objects: TRUNK

The SSM Transit Node Clock (TNC) Traceable BITS or STM-N condition occurs when the SSM quality level is changed to G812T.

Note: SSM-TNC is an informational condition. The condition does not require troubleshooting.

SW-MISMATCH

The SW-MISMATCH condition is not used in this platform in this release. It is reserved for development.

SWMTXMOD-PROT

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Object: EQPT

The Switching Matrix Module Failure on Protect Slot alarm is raised by the Slot 10 cross connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-PROT occurs when a logic component internal to the Slot 10 cross connect is out of frame (OOF) with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.

The XC-VXC cross-connect card can raise this alarm (in Slot 10) whether it is ACT or standby (SBY). The XCVXL card can raise SWMTXMOD-PROT against itself if the cross-connect card is OOF with a second logic component on the same cross connect card.

Clear the SWMTXMOD-PROT Alarm

  1. Complete the Reset a Traffic Card in CTC for the Slot 10 card. For the LED behavior, see the Typical Traffic Card LED Activity During Reset.
  2. Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
  3. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card for the Slot 10 cross-connect card.
  4. Complete the Side Switch the Active and Standby Cross-Connect Cards.
    Note: After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.
  5. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

SWMTXMOD-WORK

Default Severity: Critical (CR), Service-Affecting (SA)
SDH Logical Object: EQPT

The Switching Matrix Module Failure on Working Slot alarm is raised by the Slot 8 cross connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-WORK occurs when a logic component internal to the Slot 8 cross connect is OOF with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.

The XCVXC cross-connect card can raise this alarm (in Slot 8) whether it is ACT or standby (SBY). The XCVT card can raise SWMTXMOD-WORK against itself if the cross-connect card is OOF with a second logic component on the same cross connect card.

Clear the SWMTXMOD-WORK Alarm

  1. Complete the Reset a Traffic Card in CTC for the Slot 8 card. For the LED behavior, see the Typical Traffic Card LED Activity During Reset.
  2. Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
  3. If the alarm does not clear, complete the Remove and Reinsert (Reseat) Any Card for the Slot 8 cross-connect card.
  4. Complete the Side Switch the Active and Standby Cross-Connect Cards.
    Note: After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.
  5. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

SWTOPRI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Primary Reference condition occurs when the ONS 15454 SDH switches to the primary timing source (reference 1). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.

Note: SWTOPRI is an informational condition. The condition does not require troubleshooting.

SWTOSEC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Secondary Reference condition occurs when the ONS 15454 SDH has switched to a secondary timing source (reference 2).

To clear the condition, clear alarms related to failures of the primary source, such as the "SYNCPRI" alarm on page 2-244. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SWTOTHIRD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Third Reference condition occurs when the ONS 15454 SDH has switched to a third timing source (reference 3).

To clear the condition, clear alarms related to failures of the primary source, such as the "SYNCPRI" alarm on page 2-244 and the "SYSBOOT" alarm on page 2-245. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SYNC-FREQ

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, E1, STMN
DWDM Logical Object: TRUNK

The Synchronization Reference Frequency Out Of Bounds condition is reported against any reference that is out of the bounds for valid references. The NE fails this reference and chooses another reference or internal to run on.

Clear the SYNC-FREQ Condition

  1. Use an optical test set to verify the timing frequency of the line or BITS timing source and ensure that that timing falls within the proper frequency. For specific procedures to use the test set equipment, consult the manufacturer.
    For BITS, the proper timing frequency range is approximately -15 PPM to 15 PPM. For optical line timing, the proper frequency range is approximately -16 PPM to 16 PPM.
  2. If the reference source frequency is not out of bounds, replace the TCC2/TCC2P card. Complete the Physically Replace a Traffic Card.
  3. If the SYNC-FREQ condition continues to report after replacing the TCC2/TCC2P card, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SYNCLOSS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: FCMR
DWDM Logical Objects: FC, GE, ISC, TRUNK

The Loss of Synchronization on Data Interface alarm is raised on FC_MR-4 client ports and MXP cards client or trunk ports when there is a loss of signal synchronization on the port. This alarm is demoted by the SIGLOSS alarm.

Clear the SYNCLOSS Alarm

  1. Ensure that the data port connection at the near-end card's port of the SDH link is operational.
  2. Verify fiber continuity to the port. To do this follow site practices.
  3. View the physical port LED to determine whether the alarm has cleared:
    • If the LED is green, the alarm has cleared.
    • If the port LED is clear (that is, not illuminated green), the link is not connected and the alarm has not cleared.
    • If the LED is red, this indicates that the fiber is pulled.
  4. If the SYNCLOSS alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

SYNCPRI

Default Severity: Minor (MN), Non-Service-Affecting (NSA) for EXT-SREF; Major (MJ), Non-Service-Affecting (NSA) for NE-SREF
SDH Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Primary Reference alarm occurs when the ONS 15454 SDH loses the primary timing source (reference 1). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the ONS 15454 SDH should switch to its secondary timing source (reference 2). The timing switch also triggers the "SWTOSEC" condition.

Clear the SYNCPRI Alarm

  1. In node view, click the Provisioning > Timing > General tabs.
  2. Verify the current configuration for REF-1 of the NE reference.
  3. If the primary reference is a BITS input, verify the wiring connection from the ONS 15454 SDH backplane BITS clock pin fields to the timing source.
  4. Verify that the BITS clock is operating properly.
  5. If the primary reference clock is an incoming port on the ONS 15454 SDH, complete the LOF (TRUNK).
  6. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SYNCSEC

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Secondary Reference alarm occurs when the ONS 15454 SDH loses the secondary timing source (reference 2). If SYNCSEC occurs, the ONS 15454 SDH should switch to a third timing source (reference 3) to obtain valid timing for the ONS 15454 SDH. The timing switch also triggers the "SWTOTHIRD" condition.

Clear the SYNCSEC Alarm

  1. In node view, click the Provisioning > Timing > General tabs.
  2. Verify the current configuration of REF-2 for the NE Reference.
  3. If the secondary reference is a BITS input, verify the wiring connection from the ONS 15454 SDH backplane BITS clock pin fields to the timing source.
  4. Verify that the BITS clock is operating properly.
  5. If the secondary timing source is an incoming port on the ONS 15454 SDH, complete the Clear the LOS (BITS) Alarm.
  6. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SYNCTHIRD

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Third Reference alarm occurs when the ONS 15454 SDH loses the third timing source (reference 3). If SYNCTHIRD occurs and the ONS 15454 SDH uses an internal reference for source three, then the TCC2/TCC2P card could have failed. The ONS 15454 SDH often reports either the "FRNGSYNC" condition or the "HLDOVRSYNC" condition after a SYNCTHIRD alarm.

Clear the SYNCTHIRD Alarm

  1. In node view, click the Provisioning > Timing > General tabs.
  2. Verify that the current configuration of REF-3 for the NE Reference. For more information about timing references, refer to the "Timing" chapter in the Cisco ONS 15454 SDH Reference Manual.
  3. If the third timing source is a BITS input, complete the Clear the LOS (BITS) Alarm.
  4. If the third timing source is an incoming port on the ONS 15454 SDH, complete the Clear the LOS (STM1E, STMN) Alarm.
  5. If the third timing source uses the internal ONS system timing, complete the Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card.
    Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
  6. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

SYSBOOT

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: NE

The System Reboot alarm indicates that new software is booting on the TCC2/TCC2P card. SYSBOOT 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. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

Note: SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.

TEMP-MISM

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: NE

Temperature Reading Mismatch Between Control Cards is raised when the temperature reading on the two TCC2/TCC2P cards are out of range of each other by more than some predefined difference (such as 5 degrees C). A message containing power monitoring and temperature information is exchanged between the two TCC2/TCC2P cards, allowing the values to be compared. The temperature of each TCC2/TCC2P card is read from a system variable.

This condition can be caused by a clogged fan filter or by fan tray stoppage.

Clear the TEMP-MISM Condition

  1. Complete the Inspect, Clean, and Replace the Reusable Air Filter.
  2. If the condition does not clear, complete the Remove and Reinsert a Fan-Tray Assembly.
  3. If this alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TIM

Default Severity: Major (MJ), Service-Affecting (SA) for STM1E; Critical (CR), Service-Affecting (SA) for STMN, TRUNK
SDH Logical Objects: STM1E, STMN
DWDM Logical Object: TRUNK

The Section TIM alarm occurs when the expected J0 section trace string does not match the received section trace string. This occurs because the data being received is not correct, and the receiving port could not be connected to the correct transmitter port.

If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed due to a fibering misconnection, a TL1 routing change, or to someone entering an incorrect value in the Current Transmit String field.

TIM occurs on a port that has previously been operating without alarms if someone switches optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the "LOS (STM1E, STMN)" alarm or the "HP-UNEQ" alarm. If these alarms accompany a TIM alarm, reattach or replace the original cables/fibers to clear the alarms. If a Transmit or Expected String was changed, restore the original string.

Clear the TIM Alarm

  1. Ensure that the physical fibers are correctly configured and attached. To do this, consult site documents. For more information about cabling the ONS 15454 SDH, refer to the Cisco ONS 15454 DWDM Procedure Guide Chapter 1, "Install the Shelf and Common Control Cards."
  2. If the alarm does not clear, you can compare the J0 expected and transmitted strings and, if necessary, change them by completing the following steps:
    1. Log into the circuit source node and click the Circuits tab.
    2. Select the circuit reporting the condition, then click Edit.
    3. Check the Show Detailed Circuit Map check box and click Apply.
    4. On the detailed circuit map, right-click the source circuit port and choose Edit J0 Path Trace (port) from the shortcut menu.
    5. Compare the Current Transmit String and the Current Expected String entries in the Edit J0 Path Trace dialog box.
    6. If the strings differ, correct the Transmit or Expected strings and click Apply.
    7. Click Close.
  3. If the alarm does not clear, ensure that the signal has not been incorrectly routed. (Although the ONS 15454 SDH routes circuits automatically, the circuit route could have been changed using TL1.) If necessary, manually correct the routing using TL1. For procedures, consult the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Reference Guide and the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TIM-MON

Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SDH Logical Object: STMN
DWDM Logical Object: TRUNK

The TIM Section Monitor TIM alarm is similar to an HP-TIM alarm, but it applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, and TXP_MR_10E cards when they are configured in transparent mode. (In Transparent termination mode, all SDH overhead bytes are passed through from client ports to the trunk ports or from trunk ports to client ports.)

Note: For more information about MXP and TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.

Clear the TIM-MON Alarm

  1. Complete the Clear the HP-TIM Alarm.
  2. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TPTFAIL (CEMR, CE100T, CE1000)

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: CEMR, CE1000, CE100T

The Transport (TPT) Layer Failure alarm for the CE-Series card indicates a break in the end-to-end Ethernet link integrity feature of the ONS 15454 SDH CE-Series card. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.

Note: For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the TPTFAIL (CEMR, CE100T, CE1000) Alarm

  1. Complete the Clear the TPTFAIL (G1000) Alarm.
  2. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

TPTFAIL (FCMR)

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: FCMR

The Transport Fail alarm is raised against a local Fibre Channel (FC) port on an FC_MR-4 card when the port receives another SDH error such as the "MS-AIS" alarm, the "AU-LOP" alarm, the "HP-UNEQ" alarm, the "LP-PLM" alarm, the "HP-TIM" alarm, LOM (for VCAT only), or SQM (for VCAT only).

This TPTFAIL can be raised against Fibre Channel cards if the remote FC card port is down from SIGLOSS or SYNCLOSS. In that case, the remote FC card port sends a "PDI" alarm and signals the local FC port transmitter to turn off (thus causing the local FC port to raise the TPTFAIL alarm). A TPTFAIL can also be raised when a far-end receive fiber is pulled. This alarm can be demoted when a facility loopback is placed on the FC_MR-4 port.

Clear the TPTFAIL (FCMR) Alarm

  1. Find and clear any path alarms applying to the port. Refer to the correct section of this chapter for trouble clearing instructions. Clearing the path alarm also clears the TPTFAIL.
  2. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.

TPTFAIL (G1000)

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Object: G1000

The Transport (TPT) Layer Failure alarm indicates a break in the end-to-end Ethernet link integrity feature of the G-Series cards. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.

The TPTFAIL alarm indicates a problem on either the SDH path or the remote Ethernet port that prevents the complete end-to-end Ethernet path from working. If any SDH path conditions or alarms such as the "AU-AIS" condition, the "AU-LOF" alarm, or the "HP-UNEQ" alarm exist on the SDH path used by the Ethernet port, the affected port causes a TPTFAIL alarm. Also, if the far-end G-Series Ethernet port is administratively disabled or the port is reporting the "CARLOSS (G1000)" alarm, the C2 byte in the SDH path overhead causes a TPTFAIL to be reported against the near-end port.

When a TPTFAIL alarm occurs, the near-end port is automatically disabled (transmit laser turned off). In turn, the laser shutoff can also cause the external Ethernet device attached at the near end to detect a link down and turn off its transmitter. This also causes a CARLOSS condition to occur on the reporting port. In all cases, the source problem is either in the SDH path being used by the G-Series port or the far-end G-Series port to which it is mapped.

An occurrence of TPTFAIL on a G-Series port indicates either a problem with the SDH path that the port is using or with the far end G-Series port that is mapped to the port.

Note: For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the TPTFAIL (G1000) Alarm

  1. Clear any alarms being reported by the STM-N card on the G-Series card circuit.
  2. If no alarms are reported by the STM-N card, the problem could be on the far-end G-Series port. Clear any alarms, such as CARLOSS, reported against the far-end port or card.
  3. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

TPTFAIL (ML100T, ML1000, MLFX)

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: ML100T, ML1000, MLFX

The TPT Layer Failure alarm indicates a break in the end-to-end packet-over-SDH (ML) link integrity feature of the ML-Series cards. TPTFAIL indicates a far-end condition or misconfiguration of the ML POS port.

The TPTFAIL alarm indicates a problem on either the SDH path, the remote POS port, or a misconfiguration of the POS port that prevents the complete end-to-end POS path from working. If any SDH conditions or alarms such as the "AU-AIS" condition, the "AU-LOP" alarm, or the "HP-UNEQ" alarm exist on the circuit used by the POS port, the affected port could report a TPTFAIL alarm. If the far-end ML-Series POS port is administratively disabled, the port inserts the "AU-AIS" condition that is detected by the near-end port. The near-end port could report TPTFAIL in this event. If the POS port is misconfigured at the Cisco IOS CLI level, the misconfiguration causes the port to go down and report TPTFAIL.

Note: For more information about the ML-Series Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm

  1. If there are no SDH alarms reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide for configuration information.
  2. If the "LP-PLM" alarm is the only alarm reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide for configuration information.
  3. If present, clear the "AU-AIS" condition, the "AU-LOP" alarm, or the "HP-UNEQ" alarm.
  4. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

TRAIL-SIGNAL-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

TRMT

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: DS1, E1

A Facility Termination Equipment Failure alarm occurs when there is a transmit failure on the E1-N-14 card because of an internal hardware failure. The card must be replaced.

Clear the TRMT Alarm

  1. Replace the E1-N-14 card reporting the failure. Complete the Physically Replace a Traffic Card.
    Caution! Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
    Caution! Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for more information about protection switches.
    Note: When you replace a card with the identical type of card, you do not need to make any changes to the database.
  2. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

TRMT-MISS

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: DS1, E1

A Facility Termination Equipment Transmitter Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance is detected when a transmit cable is missing on the E-1 port or the backplane does not match the inserted card, for example, an SMB connector or a BNC connector is connected to an E-1 card.

Note: E-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.

Clear the TRMT-MISS Alarm

  1. Verify that the device attached to the E-1 port is operational.
  2. If the device is operational, verify that the cabling is securely connected.
  3. If the cabling is secure, verify that the pinouts are correct.
  4. If the pinouts are correct, replace the transmit cable.
  5. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

TU-AIS

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Objects: VCMON-LP, VCTRM-LP

A Tributary Unit (TU) AIS occurs when there is an AIS, indicating a secondary condition, in the low-order tributary overhead of the virtual circuit (VC).

Generally, any AIS is a special SDH signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

Clear the TU-AIS Condition

  1. Complete the Clear the AIS Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TU-LOP

Default Severity: Major (MJ), Service-Affecting (SA)
SDH Logical Objects: VCMON-LP, VCTRM-LP

A TU LOP alarm indicates that the SDH low order path overhead section of the administration unit has detected a loss of path. TU-LOP occurs when a mismatch between the expected and provisioned circuit size.

Warning! Class 1 laser product. Statement 1008

Warning! Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

Warning! Invisible laser radiation could 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 could pose an eye hazard. Statement 1056

Clear the TU-LOP Alarm

  1. Complete the Clear the AU-LOP Alarm.
  2. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

TX-AIS

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, DS3, E1, E3

The Transmit Direction AIS condition is raised by the ONS backplane when it receives a far-end LOS from a DS1i-N-14, DS3i-N-14, or E-N card.

Clear the TX-AIS Condition

  1. Determine whether there are alarms on the downstream nodes and equipment, especially the "LOS (STM1E, STMN)" alarm, or locked ports.
  2. Clear the downstream alarms using the applicable procedures in this chapter.
  3. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TX-LOF

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, E1

The Transmit Direction LOF condition is transmitted by the backplane when it receives a DS-1 TX-LOF.

This alarm is raised only at the transmit (egress) side.

Clear the TX-LOF Condition

  1. Complete the Clear the LOF (DS1, DS3, E1, E4, STM1E, STMN) Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

TX-RAI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: DS1, E1, E3

The Transmit Direction RAI condition is transmitted by the backplane when it receives a DS1i-N-14, DS3i-N-12, or E-N card TX-AIS. This alarm is raised only at the transmit side, but RAI is raised at both ends.

Clear the TX-RAI Condition

  1. Complete the Clear the TX-AIS Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

UNC-WORD

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

UNQUAL-PPM

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
SDH Logical Object: PPM

The Unqualified PPM Inserted condition occurs when a PPM with a nonqualified product ID is plugged into the card's port; that is, the PPM passes the security code check as a Cisco PPM but is not qualified for use on the particular card.

Clear the UNQUAL-PPM Condition

  1. Obtain the correct Cisco PPM and replace the existing PPM with the new one.
  2. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

UT-COMM-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

UT-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

VCG-DEG

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: VCG

The VCAT Group Degraded alarm is a VCAT group alarm. (VCATs are groups of independent circuits that are concatenated from different time slots into higher-rate signals.) The alarm occurs when one member circuit carried by the ML-Series Ethernet card is down. This alarm is accompanied by the "OOU-TPT" alarm. It only occurs when a Critical (CR) alarm, such as LOS, causes a signal loss.

Note: For more information about the ML-Series Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the VCG-DEG Condition

  1. Look for and clear any Critical (CR) alarms that apply to the errored card, such as the "LOS (OTS)" alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

VCG-DOWN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: VCG

The VCAT Group Down alarm is a VCAT group alarm. (VCATs are groups of independent circuits that are concatenated from different time slots into higher-rate signals.) The alarm occurs when both member circuits carried by the ML-Series Ethernet card are down. This alarm occurs in conjunction with another Critical (CR) alarm, such as the "LOS (2R)" alarm.

Note: For more information about the ML-Series Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Clear the VCG-DOWN Condition

  1. Complete the Clear the VCG-DEG Condition.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

VOA-HDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

VOA-HFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

VOA-LDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

VOA-LFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

VOLT-MISM

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Object: PWR

The Power Monitoring Mismatch Between Control Cards alarm is raised against the shelf when the power voltages of both TCC2/TCC2P cards are out of range of each other by more than 5Vdc.

Clear the VOLT-MISM Condition

  1. Check the incoming voltage level to the shelf using a voltmeter. Follow site practices or consult the "Install the Shelf and FMECs" chapter in the Cisco ONS 15454 SDH Procedure Guide for power installation procedures.
  2. Correct any incoming voltage issues.
  3. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

WKSWPR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EQPT, STMN, VCMON-HP, VCMON-LP
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC

The Working Switched To Protection condition occurs when a line raises the "LOS (STM1E, STMN)" alarm, the "SF (DS1, DS3, E1, E3, E4, STMN)" condition, or the "SD (DS1, DS3, E1, E3, E4, STMN)" condition.

Clear the WKSWPR Condition

  1. Complete the "Clear the LOS (STM1E, STMN) Alarm.
  2. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

WTR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SDH Logical Objects: EQPT, ML1000, ML100T, MLFX, STMN, VCMON-HP, VCMON-LP
DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Wait To Restore condition occurs when the "WKSWPR" condition is raised and the wait-to-restore time has not expired, meaning the active protect path cannot revert to the working path. The condition clears when the timer expires and traffic switches back to the working path.

If the condition is raised on an IEEE 802.17b-based RPR span, it indicates that the wait-to-restore timer is active after a span failure has cleared.

Caution! E-1 traffic loss can occur on an E-1 with 1:N protection if an E-1 card is reset with the protect card in the WTR state.

Note: WTR is an informational condition. It does not require troubleshooting.

WVL-MISMATCH

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

Traffic Card LED Activity

ONS 15454 SDH traffic card LED behavior patterns are listed in the following sections. These sections give behavior for card insertion, reset, and side-switch.

Typical Traffic Card LED Activity After Insertion

When a card is inserted, the following LED activities occur:

  1. The red FAIL LED turns on and remains illuminated for 20 to 30 seconds.
  2. The red FAIL LED blinks for 35 to 45 seconds.
  3. All LEDs blink once and turn off for 5 to 10 seconds.
  4. The ACT or ACT/SBY LED turns on. The SF LED can persist until all card ports connect to their far-end counterparts and a signal is present.

Typical Traffic Card LED Activity During Reset

While a card resets, the following LED activities occur:

  1. The FAIL LED on the physical card blinks and turns off.
  2. The white LED with the letters "LDG" appears on the reset card in CTC.
  3. The green ACT LED appears in CTC.

Typical Card LED State After Successful Reset

When a card successfully resets, the following LED states are present:

    • If you are looking at the physical ONS 15454 SDH, the ACT/SBY LED is illuminated.
    • If you are looking at node view of the ONS 15454 SDH, the current standby card has an amber LED depiction with the initials "SBY," and this has replaced the white "LDG" depiction on the card in CTC.
    • If you are looking at node view of the ONS 15454 SDH, the current active card has a green LED depiction with the initials "ACT," and this has replaced the white "LDG" depiction on the card in CTC.

Typical Cross-Connect LED Activity During Side Switch

While a cross-connect card is switched in CTC from active (ACT) to standby (SBY) or from SBY to ACT, the following LED activity occurs:

  1. The FAIL LED on the physical card blinks and turns off.
  2. The yellow SBY LED becomes a green ACT LED, indicating that it is now active.
  3. The green ACT LED becomes a yellow SBY LED, indicating that it is now standby.

Frequently Used Alarm Troubleshooting Procedures

This section gives common procedures that are frequently used when troubleshooting alarms. Most of these procedures are summarized versions of fuller procedures existing elsewhere in the ONS 15454 SDH documentation. They are included in this chapter for the user's convenience. For further information, please refer to the Cisco ONS 15454 SDH Procedure Guide.

Node and Ring Identification, Change, Visibility, and Termination

The following procedures relate how to identify or change MS-SPRing names and node IDs, and how to verify visibility from other nodes.

Identify an MS-SPRing Ring Name or Node ID Number

  1. Log into a node on the network. If you are already logged in, go to Step 2.
  2. In node view, click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
    From the Ring Name column, record the ring name, or in the Nodes column, record the Node IDs in the MS-SPRing. The Node IDs are the numbers in parentheses next to the node name.
    Note: For more information about ring or node traffic switching operations, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.

Change an MS-SPRing Ring Name

  1. Log into a node on the network. If you are already logged in, go to Step 2.
  2. In node view, click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
  4. Highlight the ring and click Edit.
  5. In the MS-SPRing window, enter the new name in the Ring Name field.
  6. Click Apply.
  7. Click Yes in the Changing Ring Name dialog box.

Change an MS-SPRing Node ID Number

  1. Log into a node on the network. If you are already logged in, go to Step 2.
  2. In node view, click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
  4. Highlight the ring and click Edit.
  5. In the MS-SPRing window, right-click the node on the ring map.
  6. Select Set Node ID from the shortcut menu.
  7. In the Edit Node ID dialog box, enter the new ID. The Node ID is the number in parentheses after the Node Name.
  8. Click OK.

Verify Node Visibility for Other Nodes

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. In node view, click the Provisioning > MS-SPRing tabs.
  3. Highlight a MS-SPRing.
  4. Click Ring Map.
  5. In the MS-SPRing Ring Map window, verify that each node in the ring appears on the ring map with a node ID and IP address.
  6. Click Close.

Protection Switching, Lock Initiation, and Clearing

The following sections give instructions for port, ring, and span switching and switch-clearing commands, as well as lock-ons and lockouts.

Initiate a 1+1 Protection Port Force Switch Command

This procedure switches 1+1 protection group traffic from one port in the group to the other using a Force switch.

Caution! The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.

Caution! Traffic is not protected during a Force protection switch.

Note: A Force command switches traffic on a working path even if the path has signal degrade (SD) or signal fail (SF) conditions. A force-switch does not switch traffic on a protect path. A Force switch preempts a Manual switch.

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups area, select the protection group with the port you want to switch.
  3. In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the protect/standby port, click this port.
  4. In the Switch Commands area, click Force.
  5. Click Yes in the Confirm Force Operation dialog box.
  6. If the switch is successful, the group now says "Force to working" in the Selected Groups area.

Initiate a 1+1 Protection Port Manual Switch Command

This procedure switches 1+1 protection group traffic from one port in the group to the other using a Manual switch.

Note: A Manual command switches traffic if the path has an error rate less than the signal degrade. A Manual switch is preempted by a Force switch.

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups area, select the protection group with the port you want to switch.
  3. In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the protect/standby port, click this port.
  4. In the Switch Commands area, click Manual.
  5. Click Yes in the Confirm Force Operation dialog box.
  6. If the switch is successful, the group now says "Manual to working" in the Selected Groups area.

Clear a 1+1 Protection Port Force or Manual Switch Command

Note: If the 1+1 protection group is configured as revertive, clearing a Force switch to protect (or working) moves traffic back to the working port. In revertive operation, the traffic always switches back to working. There is no revert to protect. If ports are not configured as revertive, clearing a Force switch to protect does not move traffic back.

Note: If the Force Switch was user-initiated, the reversion occurs immediately when the clear command is issued. The five-minute WTR period is not needed in this case. If the Force was system-initiated, allow the five-minute waiting period (during WTR) before the reversion occurs.

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups area, choose the protection group containing the port you want to clear.
  3. In the Selected Group area, choose the port you want to clear.
  4. In the Switching Commands area, click Clear.
  5. Click Yes in the Confirmation Dialog box.
    The Force switch is cleared. Traffic immediately reverts to the working port if the group was configured for revertive switching.

Initiate a Card or Port Lock On Command

Note: For 1:1 and 1:N electrical protection groups, working or protect cards can be placed in the Lock On state. For a 1+1 optical protection group, only the working port can be placed in the Lock On state.

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups list, click the protection group where you want to apply a lock-on.
  3. If you determine that the protect card is in standby mode and you want to apply the lock-on to the protect card, make the protect card active if necessary by completing the following steps:
    1. In the Selected Group list, click the protect card.
    2. In the Switch Commands area, click Force.
  4. In the Selected Group list, click the active card where you want to lock traffic.
  5. In the Inhibit Switching area, click Lock On.
  6. Click Yes in the confirmation dialog box.

Initiate a Card or Port Lock Out Command

Note: For 1:1 or 1:N electrical protection groups, working or protect cards can be placed in the Lock Out state. For a 1+1 optical protection group, only the protect port can be placed in the Lock Out state.

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups list, click the protection group that contains the card you want to lock out.
  3. In the Selected Group list, click the card you want to lock traffic out of.
  4. In the Inhibit Switching area, click Lock Out.
  5. Click Yes in the confirmation dialog box.
    The lockout has been applied and traffic is switched to the opposite card.

Clear a Card or Port Lock On or Lock Out Command

  1. In node view, click the Maintenance > Protection tabs.
  2. In the Protection Groups list, click the protection group that contains the card you want to clear.
  3. In the Selected Group list, click the card you want to clear.
  4. In the Inhibit Switching area, click Unlock.
  5. Click Yes in the confirmation dialog box.
    The lock-on or lockout is cleared.

Initiate a 1:1 Card Switch Command

Note: The Switch command only works on the active card, whether this card is working or protect. It does not work on the standby card.

  1. In node view, click the Maintenance > Protection tabs.
  2. Click the protection group that contains the card you want to switch.
  3. Under Selected Group, click the active card.
  4. Next to Switch Commands, click Switch.
    The working slot should change to Working/Active and the protect slot should change to Protect/Standby.

Initiate a Force Switch for All Circuits on an SNCP Span

This procedure forces all circuits in an SNCP from the working span to the protect. It is used to remove traffic from a card that originates or terminates SNCP circuits.

Caution! The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.

Caution! Traffic is not protected during a Force protection switch.

  1. Log into a node on the network. If you are already logged in, continue with Step 3.
  2. Click View > Go to Network View.
  3. Right-click a network span and choose Circuits.
    The Circuits on Span dialog box shows the SNCP circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
  4. Click the Perform SNCP span switching field.
  5. Choose FORCE SWITCH AWAY from the drop-down list.
  6. Click Apply.
  7. In the Confirm SNCP Switch dialog box, click Yes.
  8. In the Protection Switch Result dialog box, click OK.
    In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.

Initiate a Manual Switch for All Circuits on an SNCP Span

This procedure manually switches all circuits in an SNCP from the working span to the protect. It is used to remove traffic from a card that originates or terminates SNCP circuits.

Caution! The Manual command does not override normal protective switching mechanisms.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View. If you are already in network view, continue with Step 3.
  3. Right-click a network span and choose Circuits.
    The Circuits on Span dialog box shows the SNCP circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
  4. Click the Perform SNCP span switching field.
  5. Choose MANUAL from the drop-down list.
  6. Click Apply.
  7. In the Confirm SNCP Switch dialog box, click Yes.
  8. In the Protection Switch Result dialog box, click OK.
    In the Circuits on Span dialog box, the switch state for all circuits is MANUAL. Unprotected circuits do not switch.

Initiate a Lock-Out-of-Protect Switch for All Circuits on an SNCP Span

This procedure prevents all circuits in an SNCP working span from switching to the protect span. It is used to keep traffic off cards that originate or terminate SNCP circuits.

Caution! The Lock Out of Protect command overrides normal protective switching mechanisms.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View. If you are already in network view, continue with Step 3.
  3. Right-click a network span and choose Circuits.
    The Circuits on Span dialog box shows the SNCP circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
  4. Click the Perform SNCP span switching field.
  5. Choose LOCK OUT OF PROTECT from the drop-down list.
  6. Click Apply.
  7. In the Confirm SNCP Switch dialog box, click Yes.
  8. In the Protection Switch Result dialog box, click OK.
    In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.

Clear an SNCP Span External Switching Command

Note: If the ports terminating a span are configured as revertive, clearing a Force or Manual switch to protect moves traffic back to the working port. If ports are not configured as nonrevertive, clearing a Force switch to protect does not move traffic back.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View. If you are already in network view, continue with Step 3.
  3. Right-click a network span and choose Circuits.
    The Circuits on Span dialog box shows the SNCP circuits, including circuit names, locations, and a color code showing which circuits are active on the span.
  4. Initiate a Force switch for all circuits on the span by completing the following steps:
    1. Click the Perform SNCP span switching field.
    2. Choose CLEAR from the drop-down list.
    3. Click Apply.
    4. In the Confirm SNCP Switch dialog box, click Yes.
    5. In the Protection Switch Result dialog box, click OK.
      In the Circuits on Span dialog box, the switch state for all circuits is CLEAR. Unprotected circuits do not switch.

Initiate a Force Ring Switch on an MS-SPRing

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. From the View menu, choose Go to Network View.
  3. In network view, click the Provisioning > MS-SPRing tabs.
  4. Click the row of the MS-SPRing you are switching, then click Edit.
  5. Right-click a MS-SPRing node west port and choose Set West Protection Operation.
  6. In the Set West Protection Operation dialog box, choose FORCE RING from the drop-down list.
  7. Click OK.
  8. Click Yes in the two Confirm MS-SPRing Operation dialog boxes that appear.

Initiate a Force Span Switch on a Four-Fiber MS-SPRing

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. From the View menu, choose Go to Network View.
  3. In network view, click the Provisioning > MS-SPRing tabs.
  4. Click the row of the MS-SPRing you are switching, then click Edit.
  5. Right-click a MS-SPRing node west port and choose Set West Protection Operation.
  6. In the Set West Protection Operation dialog box, choose FORCE SPAN from the drop-down list.
  7. Click OK.
  8. Click Yes in the two Confirm MS-SPRing Operation dialog boxes that appear.

Initiate a Manual Ring Switch on an MS-SPRing

  1. From the View menu, choose Go to Network View.
  2. Click the Provisioning > MS-SPRing tabs.
  3. Choose the MS-SPRing and click Edit.
  4. Right-click the MS-SPRing node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
  5. In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose MANUAL RING from the drop-down list.
  6. Click OK.
  7. Click Yes in the two Confirm MS-SPRing Operation dialog boxes.

Initiate a Lockout on an MS-SPRing Protect Span

  1. From the View menu, choose Go to Network View.
  2. Click the Provisioning > MS-SPRing tabs.
  3. Choose the MS-SPRing and click Edit.
  4. Right-click the MS-SPRing node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
  5. In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose LOCKOUT PROTECT SPAN from the drop-down list.
  6. Click OK.
  7. Click Yes in the two Confirm MS-SPRing Operation dialog boxes.

Initiate an Exercise Ring Switch on an MS-SPRing

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
  4. Click the row of the MS-SPRing you are exercising, then click Edit.
  5. Right-click the west port of a node and choose Set West Protection Operation.
  6. In the Set West Protection Operation dialog box, choose EXERCISE RING from the drop-down list.
  7. Click OK.
  8. Click Yes in the Confirm MS-SPRing Operation dialog box.

Initiate an Exercise Ring Switch on a Four Fiber MS-SPRing

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
  4. Click the row of the MS-SPRing you are exercising, then click Edit.
  5. Right-click the west port of a node and choose Set West Protection Operation.
  6. In the Set West Protection Operation dialog box, choose EXERCISE SPAN from the drop-down list.
  7. Click OK.
  8. Click Yes in the Confirm MS-SPRing Operation dialog box.

Clear an MS-SPRing External Switching Command

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Click View > Go to Network View.
  3. Click the Provisioning > MS-SPRing tabs.
  4. Click the MS-SPRing you want to clear.
  5. Right-click the west port of the MS-SPRing node where you invoked the switch and choose Set West Protection Operation.
  6. In the Set West Protection Operation dialog box, choose CLEAR from the drop-down list.
  7. Click OK.
  8. Click Yes in the Confirm MS-SPRing Operation dialog box.

CTC Card Resetting and Switching

This section gives instructions for resetting traffic cards, TCC2/TCC2P card, and cross-connect cards.

Caution! For TXP and MXP cards placed in a Y-cable protection group, do not perform a software reset on both cards simultaneously. Doing so will cause a traffic hit of more than one minute. For more information about Y-cable protection groups, refer to the Cisco ONS 15454 DWDM Reference Manual.

Caution! Resetting the active card in a Y-cable group will cause a traffic outage if the standby card is down for any reason.

Note: When an AICI is reset from CTC, any subsequent user client operations (such as CTC or TL1 activity) is paused for approximately 5-10 seconds. The reset does not cause any conditions to be raised.

Reset a Traffic Card in CTC

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. In node view, position the cursor over the optical or electrical traffic card slot reporting the alarm.
  3. Right-click the card. Choose Reset Card from the shortcut menu.
  4. Click Yes in the Resetting Card dialog box.

Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card

Caution! Resetting an active TCC2/TCC2P card reset can be traffic-affecting.

Caution! In a node equipped with two TCCP cards (not TCC2s), resetting an active TCC2P causes the ALM-PWR and CRFT-TMG ports to transition into the Locked-disabled, NotInstalled&Unassigned state. The ports return to the Unlocked state approximately two minutes after the reset is completed.

Note: Before you reset the TCC2/TCC2P card, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Identify the active TCC2/TCC2P card:
    If you are looking at the physical ONS 15454 SDH shelf, the ACT/SBY LED of the active card is green. The ACT/STBLY LED of the standby card is amber.
  3. Right-click the active TCC2/TCC2P card in CTC.
  4. Choose Reset Card from the shortcut menu.
  5. Click Yes in the Confirmation Dialog box.
    The card resets, the FAIL LED blinks on the physical card, and connection to the node is lost. CTC switches to network view.
  6. Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the Traffic Card LED Activity.
    Double-click the node and ensure that the reset TCC2/TCC2P card is in standby mode and that the other TCC2/TCC2P card is active.
    • If you are looking at the physical ONS 15454 SDH shelf, the ACT/SBY LED of the active card is green. The ACT/STBLY LED of the standby card is amber.
    • No new alarms appear in the Alarms window in CTC.

Side Switch the Active and Standby Cross-Connect Cards

Caution! The cross-connect card side switch is usually traffic-affecting.

  1. Log into a node on the network. For instructions regarding how to log into a node, refer Cisco ONS 15454 Procedure Guide, Release 8.0. If you are already logged in, continue with Step 2.
  2. Display node view.
  3. Determine the active or standby cross-connect card.
    The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.
    Note: You can also position the cursor over the card graphic to display a popup identifying the card as active or standby.
  4. In node view, click the Maintenance > Cross-Connect > Cards tabs.
  5. Click Switch.
  6. Click Yes in the Confirm Switch dialog box. See the Typical Cross-Connect LED Activity During Side Switch for LED information.
    Note: During a maintenance side switch or soft reset of an active XC10G card, the 1+1 protection group might display a protection switch. To disallow the protection switch from being displayed, the protection group should be locked at the node where XC switch or soft reset of an active XC switch is in progress.

Caution! Active cross connect (XC10G/XCVT) cards should not be physically removed.

The following rules must be followed for removing an Active Cross Connect Card (XC10G/XCVT):

If the active cross connect has to be removed, perform an XCVT/XC10G side switch to change the status of the card from active to standby and then remove the cross connect card once it goes back to standby.

OR

Perform a lockout on all circuits that originate from the node whose active cross connect card has to be removed (performing a lockout on all spans will also accomplish the same goal).

Physical Card Reseating, Resetting, and Replacement

Caution! Do not physically replace a card without first making provisions to switch or move traffic to a different card or circuit. General procedures for this are located in the Protection Switching, Lock Initiation, and Clearing. In-depth traffic switching procedures and information can be found in the Cisco ONS 15454 SDH Procedure Guide.

Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card

Caution! Do not perform this action without the supervision and direction of Cisco. Log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.

Caution! The TCC2/TCC2P card reseat could be traffic-affecting.

Note: Before you reset the TCC2/TCC2P card, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.

Note: When a standby TCC2/TCC2P card is removed and reinserted (reseated), all three fan lights could momentarily illuminate, indicating that the fans have also reset.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
    Ensure that theTCC2/TCC2P card you want to reseat is in standby mode. A standby card has an amber ACT/SBY (Active/Standby) LED illuminated.
  2. When the TCC2/TCC2P card is in standby mode, unlatch both the top and bottom ejectors on the TCC2/TCC2P card.
  3. Physically pull the card at least partly out of the slot until the lighted LEDs turn off.
  4. Wait 30 seconds. Reinsert the card and close the ejectors.
    Note: The TCC2/TCC2P card requires several minutes to reboot and displays the amber standby LED after rebooting. Refer to the Cisco ONS 15454 SDH Reference Manual for more information about LED behavior during card rebooting.

Remove and Reinsert (Reseat) Any Card

  1. Open the card ejectors.
  2. Slide the card halfway out of the slot along the guide rails.
  3. Slide the card all the way back into the slot along the guide rails.
  4. Close the ejectors.

Physically Replace a Traffic Card

Caution! Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the Protection Switching, Lock Initiation, and Clearing for commonly used traffic-switching procedures.

  1. Open the card ejectors.
  2. Slide the card out of the slot.
  3. Open the ejectors on the replacement card.
  4. Slide the replacement card into the slot along the guide rails.
  5. Close the ejectors.

Physically Replace an In-Service Cross-Connect Card

Caution! The cross-connect reseat could be traffic-affecting. See the Protection Switching, Lock Initiation, and Clearing for traffic-switching procedures prior to completing this procedure.

Note: This procedure is placed in the chapter as a quick guide for the user's convenience. An in-depth procedure is located in the Cisco ONS 15454 SDH Procedure Guide.

  1. Determine the active cross-connect card (XC-VXL or XC-VXC-10G). The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is amber.
    Note: You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.
  2. Switch the active cross-connect card (XC-VXL) to standby by completing the following steps:
    1. In the node view, click the Maintenance > Cross-Connect tabs.
    2. Under Cross Connect Cards, choose Switch.
    3. Click Yes in the Confirm Switch dialog box.
    Note: After the active XC-VXL goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.
  3. Physically remove the new standby cross-connect card (XC-VXL) from the ONS 15454 SDH.
    Note: An improper removal (IMPROPRMVL) alarm is raised when a card reseat is performed, unless the card is first deleted in Cisco Transport Controller (CTC). The alarm clears after the card replacement is complete.
  4. Insert the replacement cross-connect card (XC-VXL) into the empty slot.
    The replacement card boots up and becomes ready for service after approximately one minute.

Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. In node view, double-click the card reporting the alarm to display the card view.
  3. Click the Provisioning > Line tabs.
  4. Under the SD BER (or SF BER) column on the Provisioning tab, verify that the cell entry is consistent with the originally provisioned threshold. The default setting is 1E-7.
  5. If the entry is consistent with the original provisioning, go back to your original procedure.
  6. If the entry is not consistent with what the system was originally provisioned for, click the cell to display the range of choices and click the original entry.
  7. Click Apply.

Delete a Circuit

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. In node view, click the Circuits tab.
  3. Click the circuit row to highlight it and click Delete.
  4. Click Yes in the Delete Circuits dialog box.

Verify or Create Node RS-DCC Terminations

Note: Portions of this procedure are different for ONS 15454 SDH DWDM nodes.

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. In node view, click the Provisioning > Comm Channels > RS-DCC tab.
  3. View the Port column entries to see where terminations are present for a node. If terminations are missing, proceed to Step 4.
  4. If necessary, create a DCC termination by completing the following steps:
    1. Click Create.
    2. In the Create RS-DCC Terminations dialog box, click the ports where you want to create the DCC termination. To select more than one port, press the Shift key.
    3. In the port state area, click the Set to Unlocked radio button.
    4. Verify that the Disable OSPF on Link check box is unchecked.
    5. Click OK.

Clear an STM-N Card Facility or Terminal Loopback Circuit

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Double-click the reporting card in CTC to display the card view.
  3. Click the Maintenance > Loopback > Port tabs.
  4. In the Loopback Type column, determine whether any port row shows a state other than None.
  5. If a row contains another state besides None, click in the column cell to display the drop-down list and select None.
  6. In the Admin State column, determine whether any port row shows a state other than Unlocked.
  7. If a row shows a state other than Unlocked, click the column cell to display the drop-down list and select Unlocked.
  8. Click Apply.
    Note: If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.

Clear an STM-N Card XC Loopback Circuit

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Double-click the reporting card in CTC to display the card view.
  3. Click the Maintenance > Loopback > VC4 tabs.
  4. Click Apply.

Clear a Non-STM Card Facility or Terminal Loopback Circuit

  1. Log into a node on the network. If you are already logged in, continue with Step 2.
  2. Double-click the reporting card in CTC to display the card view.
  3. Click the Maintenance > Loopback tabs.
  4. In the Loopback Type column, determine whether any port row shows a state other than None.
  5. If a row contains another state besides None, click in the column cell to display the drop-down list and select None.
  6. In the Admin State column, determine whether any port row shows a state other than Unlocked.
  7. If a row shows a state other than Unlocked click in the column cell to display the drop-down list and select Unlocked.
  8. Click Apply.
    Note: If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.

Air Filter and Fan Procedures

The following procedures are used for the air filter and fan tray.

Inspect, Clean, and Replace the Reusable Air Filter

You need a vacuum cleaner or detergent and water faucet, a spare filter, and a pinned hex key.

Warning! Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206

Although the filter works if it is installed with either side facing up, Cisco recommends that you install it with the metal bracing facing up to preserve the surface of the filter.

  1. Verify that you are replacing a reusable air filter. The reusable filter is made of a gray, open-cell, polyurethane foam that is specially coated to provide fire and fungi resistance. NEBS 3E and later versions of the ONS 15454 SDH use a reusable air filter.
  2. If the air filter is installed in the external filter brackets, slide the filter out of the brackets while being careful not to dislodge any dust that could have collected on the filter by completing the following steps. If the filter is installed beneath the fan tray and not in the external filter brackets:
    1. Open the front door of the shelf assembly by completing the following substeps. (If it is already open or if the shelf assembly does not have a front door, continue with Step 3.)
      • Open the front door lock.
      • Press the door button to release the latch.
      • Swing the door open.
    2. Remove the front door by completing the following substeps (optional):
      • Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.
      • Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.
      • Secure the dangling end of the ground strap to the door or chassis with tape.
  3. Push the outer side of the handles on the fan-tray assembly to expose the handles.
  4. Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.
  5. When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.
  6. Gently remove the air filter from the shelf assembly. Be careful not to dislodge any dust that could have collected on the filter.
  7. Visually inspect the air filter material for dirt and dust.
  8. If the reusable air filter has a concentration of dirt and dust, either vacuum or wash the air filter. Prior to washing the air filter, replace the dirty air filter with a clean air filter and also reinsert the fan-tray assembly. Wash the dirty air filter under a faucet with a light detergent.
    Spare ONS 15454 SDH filters should be kept in stock for this purpose.
    Note: Cleaning should take place outside the operating environment to avoid releasing dirt and dust near the equipment.
  9. If you washed the filter, allow it to completely air dry for at least eight hours.
    Caution! Do not put a damp filter back in the ONS 15454 SDH.
  10. If the air filter should be installed in the external filter brackets, slide the air filter all the way to the back of the brackets to complete the procedure.
  11. If the filter should be installed beneath the fan-tray assembly, remove the fan-tray assembly and slide the air filter into the recessed compartment at the bottom of the shelf assembly. Put the front edge of the air filter flush against the front edge of the recessed compartment. Push the fan tray back into the shelf assembly.
    Caution! If the fan tray does not slide all the way to the back of the shelf assembly, pull the fan tray out and re-adjust the position of the reusable filter until the fan tray fits correctly.
    Note: On a powered-up ONS 15454 SDH, the fans start immediately after the fan-tray assembly is correctly inserted.
  12. To verify that the tray is plugged into the backplane, ensure that the LCD on the front of the fan-tray assembly is activated and displays node information.
  13. Rotate the retractable handles back into their compartments.
  14. Replace the door and reattach the ground strap.

Remove and Reinsert a Fan-Tray Assembly

  1. Use the retractable handles embedded in the front of the fan-tray assembly to pull it forward several inches.
  2. Push the fan-tray assembly firmly back into the ONS 15454 SDH.
  3. Close the retractable handles.

Replace the Fan-Tray Assembly

Caution! The 15454-FTA3 fan-tray assembly can only be installed in ONS 15454 SDH R3.1 and later shelf assemblies (15454-SA-ANSI, P/N: 800-19857; 15454-SA-HD, P/N: 800-24848). It includes a pin that does not allow it to be installed in ONS 15454 shelf assemblies released before ONS 15454 SDH R3.1 (15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1, P/N: 800-07149). Equipment damage can result from attempting to install the 15454-FTA3 in a incompatible shelf assembly.

Caution! Do not force a fan-tray assembly into place. Doing so can damage the connectors on the fan tray and/or the connectors on the backplane.

Note: The 15454-SA-ANSI or 15454-SA-HD shelf assembly and 15454-FTA3 fan-tray assembly are required with the ONS 15454 STM-64, and STM-16 any slot (AS) cards.

To replace the fan-tray assembly (FTA), it is not necessary to move any of the cable management facilities.

  1. Open the front door of the shelf assembly by completing the following steps. If the shelf assembly does not have a front door, continue with Step 3.
    1. Open the front door lock.
    2. Press the door button to release the latch.
    3. Swing the door open.
  2. Remove the front door (optional) by completing the following steps:
    1. Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.
    2. Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.
    3. Secure the dangling end of the ground strap to the door or chassis with tape.
  3. Push the outer side of the handles on the fan-tray assembly to expose the handles.
  4. Fold out the retractable handles at the outside edges of the fan tray.
  5. Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.
  6. When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.
  7. If you are replacing the fan-tray air filter and it is installed beneath the fan-tray assembly, slide the existing air filter out of the shelf assembly and replace it before replacing the fan-tray assembly.
    If you are replacing the fan-tray air filter and it is installed in the external bottom bracket, you can slide the existing air filter out of the bracket and replace it at anytime. For more information on the fan-tray air filter, see the Inspect, Clean, and Replace the Reusable Air Filter.
  8. Slide the new fan tray into the shelf assembly until the electrical plug at the rear of the tray plugs into the corresponding receptacle on the backplane.
  9. To verify that the tray has plugged into the backplane, check that the LCD on the front of the fan tray is activated.
  10. If you replace the door, be sure to reattach the ground strap.

Rating: 5.0/5 (1 vote cast)

Personal tools