Install the Control Cards

Note The terms “Unidirectional Path Switched Ring” and “UPSR” may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as “Path Protected Mesh Network” and “PPMN”, refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.

3.1 Card Overview

The card overview section lists the cards described in this chapter.

Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. The cards are then installed into slots displaying the same symbols. For a list of slots and symbols, see the “Card Slot Requirements” section in the Cisco ONS 15454 Hardware Installation Guide.

3.1.1 Common Control Cards

The following common control cards are needed to support the functions of the DWDM, transponder, and muxponder cards on ONS 15454 shelf:

TCC2 or TCC2P or TCC3

AIC-I (optional)

MS-ISC-100T (multishelf configurations only)

The TNC, TNCE, TSC, and TSCE cards are used to support the functions of DWDM, transponder, and muxponder cards on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 shelves.

3.1.2 Card Compatibility

Table 3-1 lists the platform and software release compatibility for the control cards.

Table 3-1 Platform and Software Release Compatibility for Control Cards

1.The TCC3 card is backward compatible with software Release 9.1 and earlier releases. In the Release 9.1 and earlier releases, the TCC3 card boots up as the TCC2P card in the Cisco ONS 15454 DWDM systems.

2.From releases 9.2.3 and later, the TNC and TNCE cards can be interchanged on an ONS 15454 M6 shelf without any alarms. However, if you combine both the cards in a single chassis and configure the OC3 OSC, it raises an EOC alarm.

3.1.3 Front Mount Electrical Connections (ETSI only)

The following Front Mount Electrical Connections (FMECs) are needed to support the functions of the DWDM, transponder, and muxponder cards:

3.4 TCC2P Card

The Advanced Timing, Communications, and Control Plus (TCC2P) card is an enhanced version of the TCC2 card. The primary enhancements are Ethernet security features and 64K composite clock BITS timing.

The TCC2P card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET SOH DCC/GCC termination, and system fault detection for the ONS 15454. The TCC2P also ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing requirements. It monitors the supply voltage of the system.

The TCC2P card supports multi-shelf management. The TCC2P card acts as a shelf controller and node controller for the ONS 15454. The TCC2P card supports up to four subtended shelves through the MS-ISC card or external switch. In a multi-shelf configuration, the TCC2P card allows the ONS 15454 node to be a node controller and does not support subtending of ONS 15454 M6 shelves.

The TCC2P card is compliant to the following standards:

The LAN interface of the TCC2P card meets the standard Ethernet specifications by supporting a cable length of 328 ft. (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft. (10 m) maximum at temperatures from –40 to 32 degrees Fahrenheit (–40 to 0 degrees Celsius).

The TCC2P card is Restriction of Use of Hazardous Substances (RoHS) complaint. The RoHS regulations limit or ban the specific substances such as lead, cadmium, polybrominated biphenyl (PBB), mercury, hexavalent chromium, and polybrominated diphenyl ether (PBDE) flame retardants in a new electronic and electric equipment.

Install TCC2P cards in Slots 7 and 11 for redundancy. If the active TCC2P card fails, traffic switches to the protect TCC2P card. All TCC2P card protection switches conform to protection switching standards when the bit error rate (BER) counts are not in excess of 1 * 10 exp – 3 and completion time is less than 50 ms.

3.5 TCC3 Card

The Timing Communications Control Three (TCC3) card is an enhanced version of the TCC2P card. The primary enhancements include the increase in memory size and compact flash space. The TCC3 card boots up as TCC2P card in older releases and as TCC3 card from Release 9.2 onwards.

The TCC3 card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET SOH DCC/GCC termination, and system fault detection for the ONS 15454. The TCC3 also ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing requirements. It monitors the supply voltage of the system.

The TCC3 card supports multi-shelf management. The TCC3 card acts as a shelf controller and node controller for the ONS 15454. The TCC3 card supports up to 30 subtended shelves through the MSM-ISC card or external switch. In a multi-shelf configuration, the TCC3 card allows the ONS 15454 node to be a node controller if an M6 shelf is subtended to it. We recommend the use of TCC3 card as a node controller when the number of subtended shelves exceeds four.

The TCC3 card is compliant with the following standards:

The LAN interface of the TCC3 card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures ranging from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from –40 to 32 degrees Fahrenheit (–40 to 0 degrees Celsius).

The TCC3 card is Restriction of Use of Hazardous Substances (RoHS) compliant. The RoHS regulations limit or ban the specific substances such as lead, cadmium, polybrominated biphenyl (PBB), mercury, hexavalent chromium, and polybrominated diphenyl ether (PBDE) flame retardants in a new electronic and electric equipment.

The TNC and TNCE cards are provisioned as master and slave in the 15454-M6 shelf, and as a stand-alone card in the 15454-M2 shelf. The TNC and TNCE cards serve as the processor card for the node.

On the 15454-M6 shelf, install redundant TNC and TNCE cards in slots 1 and 8. If the active TNC or TNCE card fails, system traffic switches to the redundant TNC or TNCE card. The card supports line cards from slots 2 to 7.

On the 15454-M2 shelf, install the stand-alone TNC and TNCE cards in slot 1. The TNC and TNCE cards support line cards in slots 2 and 3.

The TNC and TNCE cards monitor both the supply voltage inputs on the 15454-M6 shelf. The TNC and TNCE cards raise an alarm if one of the supply voltage inputs has a voltage out of the specified range. The 15454-M2 shelf has dual power supply.

You can insert and remove the TNC and TNCE cards even when the system is online, without impacting the system traffic.

You can upgrade the TSC or TSCE card to a TNC or TNCE card. During the upgrade, the TNC and TNCE cards do not support OSC functions such as UDC, VoIP, DCC, and timing function. However, you can still provision the SFP ports on the TNC and TNCE cards during the upgrade. The TNC/TNCE and TSC/TSCE cards cannot be inserted in the same shelf.

The TNC and TNCE cards support all the alarms supported by the TCC2P and AIC-I cards. The card adjusts the fan speed according to the temperature and reports a fan failure alarm.

Note The LAN interface of the TNC and TNCE cards meet the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from -40 to 32 degrees Fahrenheit (-40 to 0 degrees Celsius).

3.6.1 Faceplate and Block Diagram

The faceplate design of the TNC and TNCE cards allow sufficient space to insert or remove cables while accessing the Ethernet and SFP ports.

The TNC and TNCE cards can be installed only in slots 1 or 8 of the ONS 15454 M6 shelf and in slot 1 of the ONS 15454 M2 shelf. The TNC and TNCE cards have an identifier on the faceplate that matches with an identifier in the shelf. A key is also provided on the backplane interface connectors as identifier in the shelf.

The TNC and TNCE cards support field-programmable gate array (FPGA) for the backplane interface. The TNC cards have two FPGA: TCCA, SYNTIDE and FRAMPOS

The TNCE cards have one FPGA: VEGA and FRAMPOS

Figure 3-4 illustrates the faceplate and block diagram for the TNC card.

Figure 3-4 TNC Faceplate and Block Diagram

Figure 3-5 illustrates the faceplate and block diagram for the TNCE card.

The TSC and TSCE cards are provisioned as master and slave in the ONS 15454 M6 shelf, and as a stand-alone card in the ONS 15454 M2 shelf. The TSC and TSCE cards serve as the processor card for the node.

On the ONS 15454 M6 shelf, install redundant TSC and TSCE cards in slots 1 and 8. If the active TSC or TSCE card fails, system traffic switches to the redundant TSC or TSCE card. The TSC and TSCE cards support line cards from slots 2 to 7.

On the ONS 15454 M2 shelf, install the stand-alone TSC and TSCE cards in slot 1. The TSC and TSCE cards support line cards in slots 2 and 3.

The TSC and TSCE cards monitor both the supply voltage inputs on the 15454-M6 shelf. The TSC and TSCE cards raise an alarm if one of the supply voltage inputs has a voltage out of the specified range. The 15454-M2 shelf has dual power supply.

You can insert and remove the TSC and TSCE cards even when the system is online, without impacting the system traffic.

The TSC and TSCE cards do not support optical service channel (OSC) and SFP ports.

You can upgrade the TSC or TSCE card to a TNC or TNCE card. During the upgrade, the TNC and TNCE cards do not support OSC functions such as UDC, VoIP, DCC, and timing function. However, you can still provision SFP ports on the TNC and TNCE cards during the upgrade. The TNC, TNCE, TSC, and TSCE cards cannot be inserted in the same shelf.

The TSC and TSCE cards support all the alarms supported by the TCC2P and AIC-I cards. The card adjusts the fan speed according to the temperature and reports a fan failure alarm.

Note The LAN interface of the TSC and TSCE cards meet the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from -40 to 32 degrees Fahrenheit (-40 to 0 degrees Celsius).

3.7.1 Faceplate and Block Diagram

The faceplate design of the TSC and TSCE cards allow sufficient space to insert or remove cables while accessing the Ethernet ports.

The TSC and TSCE cards can be installed only in slots 1 or 8 of the 15454-M6 shelf and in slot 1 of the 15454-M2 shelf. The TSC and TSCE cards have an identifier on the faceplate that matches with an identifier in the shelf. A key is also provided on the backplane interface connectors as identifier in the shelf.

The TSC and TSCE cards support field-programmable gate array (FPGA) for the backplane interface. The TSC cards have two FPGA: TCCA and SYNTIDE

The TSCE cards have one FPGA: VEGA

Figure 3-6 illustrates the faceplate and block diagram for the TSC card.

3.8 Digital Image Signing

(Cisco ONS 15454 M2 and ONS 15454 M6 only)

The DIS feature complies with the new U.S. Government Federal Information Processing Standard (FIPS) 140-3 to provide security for all software provided on the Cisco ONS 15454 M6 and ONS 15454 M2 platforms. This standard requires software to be digitally signed and verified for authenticity and integrity prior to load and execution.

New controller cards, such as TNC/TNCE/TSC/TSCE, provide services that authenticate the origin of the software running on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms. The signage and verification process is transparent until verification fails.

3.8.1 DIS Identification

Digitally signed software can be identified by the last three characters appended to the working version and protected version field in CTC. The DIS conventions can be viewed under the working version displayed in the Maintenance > Software tab in CTC. For example, 9.2.0 (09.20-X10C-29.09-SDA) and 9.2.0 (09.20-010C-18.18-SPA).

The significance of the three characters appended to the software version is explained in Table:

Table 3-2 DIS Conventions in the Software Version

Character

Meaning

S (first character)

Indicates that the package is signed.

P or D (second character)

Production (P) or Development (D) image. Production image—Software approved for general release. Development image—development software provided under special conditions for limited use.

A (third character)

This third character indicates the version of the key used for signature generation. The version changes when a key is revoked and a new key is used. The values of the version key varies from A to Z.

3.9 AIC-I Card

The optional Alarm Interface Controller–International (AIC-I) card provides customer-defined (environmental) alarms and controls and supports local and express orderwire. It provides 12 customer-defined input and 4 customer-defined input/output contacts. The physical connections are via the backplane wire-wrap pin terminals. If you use the additional alarm expansion panel (AEP), the AIC-I card can support up to 32 inputs and 16 outputs, which are connected on the AEP connectors. The AEP is compatible with ANSI shelves only. A power monitoring function monitors the supply voltage (–48 VDC).

3.9.1 Faceplate and Block Diagram

3.9.2 AIC-I Card-Level Indicators

3.9.3 External Alarms and Controls

The AIC-I card provides input/output alarm contact closures. You can define up to 12 external alarm inputs and 4 external alarm inputs/outputs (user configurable). The physical connections are made using the backplane wire-wrap pins or FMEC connections. For information about increasing the number of input/output contacts, see the “ONS 15454 ANSI Alarm Expansion Panel” section in the Cisco ONS 15454 Hardware Installation Guide.

LEDs on the front panel of the AIC-I indicate the status of the alarm lines, one LED representing all of the inputs and one LED representing all of the outputs. External alarms (input contacts) are typically used for external sensors such as open doors, temperature sensors, flood sensors, and other environmental conditions. External controls (output contacts) are typically used to drive visual or audible devices such as bells and lights, but they can control other devices such as generators, heaters, and fans.

You can program each of the twelve input alarm contacts separately. You can program each of the sixteen input alarm contacts separately. Choices include:

Alarm on Closure or Alarm on Open

Alarm severity of any level (Critical, Major, Minor, Not Alarmed, Not Reported)

Service Affecting or Non-Service Affecting alarm-service level

63-character alarm description for CTC display in the alarm log

You cannot assign the fan-tray abbreviation for the alarm; the abbreviation reflects the generic name of the input contacts. The alarm condition remains raised until the external input stops driving the contact or you provision the alarm input.

The output contacts can be provisioned to close on a trigger or to close manually. The trigger can be a local alarm severity threshold, a remote alarm severity, or a virtual wire:

Local NE alarm severity: A hierarchy of Not Reported, Not Alarmed, Minor, Major, or Critical alarm severities that you set to cause output closure. For example, if the trigger is set to Minor, a Minor alarm or above is the trigger.

Remote NE alarm severity: Same as the local NE alarm severity but applies to remote alarms only.

Virtual wire entities: You can provision any environmental alarm input to raise a signal on any virtual wire on external outputs 1 through 4 when the alarm input is an event. You can provision a signal on any virtual wire as a trigger for an external control output.

You can also program the output alarm contacts (external controls) separately. In addition to provisionable triggers, you can manually force each external output contact to open or close. Manual operation takes precedence over any provisioned triggers that might be present.

Note For ANSI shelves, the number of inputs and outputs can be increased using the AEP. The AEP is connected to the shelf backplane and requires an external wire-wrap panel.

3.9.4 Orderwire

Orderwire allows a crafts person to plug a phone set into an ONS 15454 and communicate with crafts people working at other ONS 15454s or other facility equipment. The orderwire is a pulse code modulation (PCM) encoded voice channel that uses E1 or E2 bytes in section/line overhead.

The AIC-I allows simultaneous use of both local (section overhead signal) and express (line overhead channel) orderwire channels on a SONET/SDH ring or particular optics facility. Express orderwire also allows communication via regeneration sites when the regenerator is not a Cisco device.

You can provision orderwire functions with CTC similar to the current provisioning model for DCC/GCC channels. In CTC, you provision the orderwire communications network during ring turn-up so that all NEs on the ring can reach one another. Orderwire terminations (that is, the optics facilities that receive and process the orderwire channels) are provisionable. Both express and local orderwire can be configured as on or off on a particular SONET/SDH facility. The ONS 15454 supports up to four orderwire channel terminations per shelf. This allows linear, single ring, dual ring, and small hub-and-spoke configurations. Orderwire is not protected in ring topologies such as bidirectional line switched ring (BLSR), multiplex section-shared protection ring (MS-SPRing), path protection, or subnetwork connection protection (SNCP) ring.

The ONS 15454 implementation of both local and express orderwire is broadcast in nature. The line acts as a party line. Anyone who picks up the orderwire channel can communicate with all other participants on the connected orderwire subnetwork. The local orderwire party line is separate from the express orderwire party line. Up to four OC-N/STM-N facilities for each local and express orderwire are provisionable as orderwire paths.

The AIC-I supports selective dual tone multi-frequency (DTMF) dialing for telephony connectivity, which causes one AIC-I card or all ONS 15454 AIC-I cards on the orderwire subnetwork to “ring.” The ringer/buzzer resides on the AIC-I. There is also a “ring” LED that mimics the AIC-I ringer. It flashes when a call is received on the orderwire subnetwork. A party line call is initiated by pressing *0000 on the DTMF pad. Individual dialing is initiated by pressing * and the individual four-digit number on the DTMF pad.

Table 3-3 shows the pins on the orderwire connector that correspond to the tip and ring orderwire assignments.

Table 3-3 Orderwire Pin Assignments

RJ-11 Pin Number

Description

1

Four-wire receive ring

2

Four-wire transmit tip

3

Two-wire ring

4

Two-wire tip

5

Four-wire transmit ring

6

Four-wire receive tip

When provisioning the orderwire subnetwork, make sure that an orderwire loop does not exist. Loops cause oscillation and an unusable orderwire channel.

3.9.5 Power Monitoring

The AIC-I card provides a power monitoring circuit that monitors the supply voltage of –48 VDC for presence, under voltage, and over voltage.

3.9.6 User Data Channel

The user data channel (UDC) features a dedicated data channel of 64 kbps (F1 byte) between two nodes in an ONS 15454 network. Each AIC-I card provides two user data channels, UDC-A and UDC-B, through separate RJ-11 connectors on the front of the AIC-I card. Each UDC can be routed to an individual optical interface in the ONS 15454.

3.9.7 Data Communications Channel

The DCC features a dedicated data channel of 576 kbps (D4 to D12 bytes) between two nodes in an ONS 15454 network. Each AIC-I card provides two data communications channels, DCC-A and DCC-B, through separate RJ-45 connectors on the front of the AIC-I card. Each DCC can be routed to an individual optical interface in the ONS 15454.

3.10 MS-ISC-100T Card

The Multishelf Internal Switch Card (MS-ISC-100T) is an Ethernet switch used to implement the multishelf LAN. It connects the node controller shelf to the network and to subtending shelves. The MS-ISC-100T must always be equipped on the node controller shelf; it cannot be provisioned on a subtending controller shelf.

The recommended configuration is to implement LAN redundancy using two MS-ISC-100T cards: one switch is connected to the Ethernet front panel port of the TCC2/TCC2P card in Slot 7, and the other switch is connected to the Ethernet front panel port of the TCC2/TCC2P card in Slot 11. The Ethernet configuration of the MS-ISC-100T card is part of the software package and is automatically loaded. The MS-ISC-100T card operates in Slots 1 to 6 and 12 to 17 on the node controller shelf; the recommended slots are Slot 6 and Slot 12.

3.11.1 MIC-A/P FMEC

The MIC-A/P FMEC provides connection for the BATTERY B input, one of the two possible redundant power supply inputs. It also provides connection for eight alarm outputs (coming from the TCC2/TCC2P card), sixteen alarm inputs, and four configurable alarm inputs/outputs. Its position is in Slot 23 i n the center of the subrack Electrical Facility Connection Assembly (EFCA) area.

The MIC-A/P FMEC has the following features:

Connection for one of the two possible redundan t p ower supply inputs

Connection for eight alarm outputs (coming from the TCC2/TCC2P card)

Connection for four configurable alarm inputs/outputs

Connection for sixteen alarm inputs

Storage of manufacturing and inventory data

For proper system operation, both the MIC-A/P and MIC-C/T/P FMECs must be installed in the ONS 15454 ETSI shelf.

3.11.3 MIC-C/T/P FMEC

The MIC-C/T/P FMEC provides connection for the BATTERY A input, one of the two possible redundant power supply inputs. It also provides connection for system management serial port, system management LAN port, modem port (for future use), and system timing inputs and outputs. Install the MIC-C/T/P in Slot 24.

The MIC-C/T/P FMEC has the following features:

Connection for one of the two possible redundan t p ower supply inputs

Connection for two serial ports for local craft/modem (for future use)

Connection for one LAN port

Connection for two system timing inputs

Connection for two system timing outputs

Storage of manufacturing and inventory data

For proper system operation, both the MIC-A/P and MIC-C/T/P FMECs must be installed in the shelf.

Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94

This task installs redundant TCC2/TCC2P/TCC3 cards. The first card you install in the ONS 15454 must be a TCC2/TCC2P/TCC3 card, and it must initialize before you install any cross-connect or traffic cards. Cross-connect cards are only required in hybrid nodes.

Tools/Equipment

Two TCC2/TCC2P/TCC3 cards

Prerequisite Procedures

None

Required/As Needed

Required

Onsite/Remote

Onsite

Security Level

None

Caution Do not remove a TCC2/TCC2P/TCC3 card during the software transfer process, which is indicated by alternate flashing FAIL and ACT/STBY LEDs. Removing a TCC2/TCC2P/TCC3 during the software transfer process will corrupt the system memory.

Note Allow each card to boot completely before installing the next card.

Step 1 Open the latches/ejectors of the first TCC2/TCC2P/TCC3 card that you will install.

Step 2 Use the latches/ejectors to firmly slide the card along the guide rails until the card plugs into the receptacle at the back of the slot (Slot 7 or 11).

Note In Step 4, you will be instructed to watch the LED activity (sequence) on the front of the TCC2/TCC2P/TCC3 card. This activity begins immediately after you close the latches in Step 3.

Step 3Verify that the card is inserted correctly and close the latches/ejectors on the card.

Note It is possible to close the latches/ejectors when the card is not completely plugged into the back panel of the shelf. Ensure that you cannot insert the card any farther.

If you insert a card into a slot provisioned for a different card, all LEDs turn off.

Step 4As needed, go to Step a to verify the LED activity on the TCC2 card. For the TCC2P go to Step b. For the TCC3 card go to Step c.

a.For the TCC2 card:

All LEDs turn on briefly. The red FAIL LED and the yellow ACT/STBY LED turn on for about 15 seconds. (For TCC3 card it takes around 20 to 25 seconds)

The red FAIL LED and the green ACT/STBY LED turn on for about 40 seconds.

The red FAIL LED blinks for about 15 seconds.

The red FAIL LED turns on for about 15 seconds. All LEDs turn on for about 3 seconds before turning off for about 3 seconds.

Both green PWR LEDs turn on for 10 seconds. The PWR LEDs then turn red for 2 to 3 minutes before going to steady green.

While the PWR LEDs are red for two to three minutes, the ACT/STBY turn on.

The boot-up process is complete when the PWR LEDs turn green and the ACT/STBY remains on. (The ACT/STBY LED will be green if this is the first TCC2 card installed, and amber if this is the second TCC2 card installed.)

Note It might take up to four minutes for the A and B power alarms to clear.

Note Alarm LEDs might be on; disregard alarm LEDs until you are logged into CTC and can view the Alarms tab.

Note If you are logged into CTC, the SFTWDOWN alarm might appear as many as two times while the TCC2 card initializes. The alarm should clear after the card completely boots.

Note If the FAIL LED is on continuously, see the tip in Step 8 about the TCC2 card automatic upload.

b.For the TCC2P card:

All LEDs turn on briefly. The red FAIL LED, the yellow ACT/STBY LED, the green SYNC LED, and the green ACO LED turn on for about 15 seconds.

The red FAIL LED and the green ACT/STBY LED turn on for about 30 seconds.

The red FAIL LED blinks for about 3 seconds.

The red FAIL LED turns on for about 15 seconds.

The red FAIL LED blinks for about 10 seconds and then becomes solid.

All LEDs (including the CRIT, MAJ, MIN, REM, SYNC, and ACO LEDs) blink once and turn off for about 5 seconds.

Both green PWR LEDs turn on for 10 seconds. The PWR LEDs then turn red for 2 to 3 minutes before going to steady green. During this time, the ACT/STBY, MJ, and MN LEDs might turn on, followed by the SNYC LED briefly.

The boot-up process is complete when the PWR LEDs turn green and the yellow ACT/STBY remains on. (The ACT/STBY LED will be green if this is the first TCC2P card installed, and yellow if this is the second TCC2P card installed.)

Note It might take up to three minutes for the A and B power alarms to clear.

Note Alarm LEDs might be on; disregard alarm LEDs until you are logged into CTC and can view the Alarms tab.

Note If you are logged into CTC, the SFTWDOWN alarm might appear as many as two times while the TCC2P card initializes. The alarm should clear after the card completely boots.

Note If the FAIL LED is on continuously, see the tip in Step 8 about the TCC2P card automatic upload.

c.For the TCC3 card:

All LEDs turn on briefly. The red FAIL LED, the yellow ACT/STBY LED, the green SYNC LED, and the green ACO LED turn on for about 25 seconds.

The red FAIL LED and the green ACT/STBY LED turn on for about 15 seconds.

The red FAIL LED blinks for about 3 seconds.

The red FAIL LED turns on for about 60 seconds.

The red FAIL LED blinks for about 15 seconds and then becomes solid (the LED is turned on for about 20 seconds).

All LEDs (including the CRIT, MAJ, MIN, REM, SYNC, and ACO LEDs) blink once and turn off for about 5 seconds.

Both green PWR LEDs turn on for 10 seconds. The PWR LEDs then turn red for 2 to 3 minutes before going to steady green. During this time, the ACT/STBY, MJ, and MN LEDs might turn on, followed by the SNYC LED briefly.

The boot-up process is complete when the PWR LEDs turn green and the yellow ACT/STBY remains on. (The ACT/STBY LED will be green if this is the first TCC3 card installed, and yellow if this is the second TCC3 card installed.)

Note It might take up to three minutes for the A and B power alarms to clear.

Note Alarm LEDs might be on; disregard alarm LEDs until you are logged into CTC and can view the Alarms tab.

Note If you are logged into CTC, the SFTWDOWN alarm might appear as many as two times while the TCC3 card initializes. The alarm should clear after the card completely boots.

Note If the FAIL LED is on continuously, see the tip in Step 8 about the TCC3 card automatic upload.

Step 5Verify that the ACT/STBY LED is green if this is the first powered-up TCC2/TCC2P/TCC3 card installed, or yellow for standby if this is the second powered-up TCC2/TCC2P/TCC3. The IP address, temperature of the node, and time of day appear on the LCD. The default time and date is 12:00 AM, January 1, 1970.

Step 6The LCD cycles through the IP address (the default is 192.1.0.2), node name, and software version. Verify that the correct software version is shown on the LCD. The software text string indicates the node type (SDH or SONET) and software release. (For example: SDH 09.20-05L-20.10 indicates it is an SDH software load, Release 9.2. The numbers following the release number do not have any significance.)

Step 7If the LCD shows the correct software version, continue with Step 8. If the LCD does not show the correct software version, refer to your next level of technical support, upgrade the software, or remove the TCC2/TCC2P/TCC3 card and install a replacement card.

Refer to the release-specific software upgrade document to replace the software. To replace the TCC2/TCC2P/TCC3 card, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide.

Step 8Repeat Steps 1 through 7 for the redundant TCC2/TCC2P/TCC3 card. If both TCC2/TCC2P/TCC3 cards are already installed, proceed to Step 9.

Tip If you install a standby TCC2/TCC2P/TCC3 card that has a different software version than the active TCC2/TCC2P/TCC3 card, the newly installed standby TCC2/TCC2P/TCC3 card automatically copies the software version from the active TCC2/TCC2P/TCC3 card. You do not need to do anything in this situation. However, the loading TCC2/TCC2P/TCC3 card does not boot up in the normal manner. When the standby card is first inserted, the LEDs follow most of the normal boot-up sequence. However, after the red FAIL LED turns on for about 5 seconds, the FAIL LED and the ACT/STBY LED begin to flash alternately for up to 30 minutes while the new software loads onto the active TCC2/TCC2P/TCC3 card. After loading the new software, the upgraded TCC2/TCC2P/TCC3 card’s LEDs repeat the appropriate bootup sequence, and the amber ACT/STBY LED turns on.

Note If you insert a card into a slot provisioned for a different card, all LEDs turn off.

Note Alarm LEDs might be on; disregard alarm LEDs until you are logged into CTC and can view the Alarms tab.

Note When installing cards, allow each card to boot completely before installing the next card.

Step 1Open the latches/ejectors on the card.

Step 2 Use the latches/ejectors to firmly slide the card along the guide rails in Slot 9 until the card plugs into the receptacle at the back of the slot.

Step 3 Verify that the card is inserted correctly and close the latches/ejectors on the card.

Note It is possible to close the latches/ejectors when the card is not completely plugged into the backplane. Ensure that you cannot insert the card any further.

Step 4Verify the following:

The red FAIL LED blinks for up to 10 seconds.

Note If the red FAIL LED does not turn on, check the power.

The PWR A and PWR B LEDs become red, the two INPUT/OUTPUT LEDs become amber, and the ACT LED turns green for approximately 5 seconds.

The PWR A and PWR B LEDs turn green, the INPUT/OUTPUT LEDs turn off, and the green ACT LED remains on.

Note It might take up to 3 minutes for the PWR A and PWR B LEDs to update.

Note If you insert a card into a slot provisioned for a different card, no LEDs turn on.

Note If the red FAIL LED is on continuously or the LEDs act erratically, the card is not installed properly. Remove the card and repeat Steps 1 to 4.

Step 5 Return to your originating procedure (NTP).

DLP-G309 Install the MS-ISC-100T Card

Purpose

This task installs redundant MS-ISC-100T cards. The MS-ISC-100T card is required for a multishelf node configuration. It provides LAN redundancy on the node controller shelf. An alternative to using the MS-ISC-100T card is the Cisco Catalyst 2950, although Cisco recommends using the MS-ISC-100T. For more information on the Catalyst 2950 installation, refer to the Catalyst 2950 product documentation.

Note When installing cards, allow each card to boot completely before installing the next card.

Note The MS-ISC-100T is not supported in a subtended shelf.

Step 1 Open the latches/ejectors on the card.

Step 2 Use the latches/ejectors to firmly slide the card along the guide rails into the appropriate slot in the node controller shelf until the card plugs into the receptacle at the back of the slot. The card can be installed in any slot from Slot 1 to 6 or 12 to 17. Cisco recommends that you install the MS-ISC-100T cards in Slot 6 and Slot 12.

Step 3 Verify that the card is inserted correctly and close the latches/ejectors on the card.

Note It is possible to close the latches/ejectors when the card is not completely plugged into the backplane. Ensure that you cannot insert the card any further.

Step 4Verify the LED activity:

The red FAIL LED blinks for 35 to 45 seconds.

The red FAIL LED turns on for 15 to 20 seconds.

The red FAIL LED blinks for approximately 3 minutes.

The red FAIL LED turns on for approximately 6 minutes.

The green ACT or ACT/STBY LED turns on. The SF LED can persist until all card ports connect to their far end counterparts and a signal is present.

Note If the red FAIL LED does not turn on, check the power.

Note If you insert a card into a slot provisioned for a different card, all LEDs turn off.

Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94

(ONS 15454 M2 and ONS 15454 M6 only) This task installs redundant TNC/TNCE/TSC/TSCE cards on the ONS 15454 M6 shelf and a stand-alone TNC/TNCE/TSC/TSCE card on the ONS 15454 M2 shelf. Install and initialize the TNC/TNCE/TSC/TSCE card before installing any other line cards into the shelf assemblies. On the ONS 15454 M6 shelf, install the TNC/TNCE/TSC/TSCE cards in slots 1 and 8 for redundancy. On the ONS 15454 M2 shelf, install the stand-alone TNC/TNCE/TSC/TSCE card in slot 1.

Tools/Equipment

Two TNC/TNCE/TSC/TSCE cards for the ONS 15454 M6 shelf and one TNC/TNCE/TSC/TSCE card for the ONS 15454 M2 shelf

Prerequisite Procedures

None

Required/As Needed

Required

Onsite/Remote

Onsite

Security Level

None

Note The ONS 15454 M2 shelf supports stand-alone control cards such as TNC, TSC, TNCE, or TSCE. During replacement or removal of the control card, ensure that the optical fibers are not disturbed. The fibers must be correctly routed in the retention feature mounted on the front side of the shelf.

Caution Do not remove the TNC/TNCE/TSC/TSCE cards during the software installation process, which is indicated by alternate flashing FAIL and ACT/STBY LEDs. Removing the TNC/TNCE/TSC/TSCE cards during the software installation process will corrupt the system memory.

Note On the ONS 15454 M6 shelf, install the TNC/TNCE/TSC/TSCE cards in slots 1 and 8 for redundancy. On the ONS 15454 M2 shelf, install the stand-alone TNC/TNCE/TSC/TSCE card in slot 1. For more information, see the “Card Slot Requirements” section in the Cisco ONS 15454 Hardware Installation Guide.

Note You cannot insert the TNC/TNCE/TSC/TSCE cards in other slots due to mechanical constraints. To identify the card slot, match the symbol placed on the lower side of the card front panel with the symbol in the shelf.

Caution To achieve redundancy, two TNC and TNCE cards or two TSC and TSCE cards must be installed in the ONS 15454 M6 shelf. Do not install one TNC or TNCE card and a redundant TSC or TSCE card in the same shelf.

Step 1Open the latches/ejectors of the first TNC/TNCE/TSC/TSCE card that you will install.

Step 2 Use the latches/ejectors to firmly slide the card horizontally along the guide rails until the card plugs into the receptacle at the back of the slot (slot 1 or 8 in the ONS 15454 M6 shelf and slot 1 in the ONS 15454 M2 shelf).

Step 3 Verify that the card is inserted correctly, and close the latches/ejectors on the card.

If you insert a card into a slot assigned for a different card, all LEDs turn off.

Step 4 As needed, verify the LED activity on the TNC/TNCE/TSC/TSCE card.

The red FAIL LED, PWR LED turn on briefly.

The red FAIL LED turns on for about 10 seconds.

The red FAIL LED and the amber ACT/STBY LED turn on for about 30 seconds.

The red FAIL LED blinks for about 10 seconds.

The red FAIL LED turns on for about 15 seconds.

All the LEDs including the CRIT, MAJ, MIN, REM, SYNC, and ACO LEDs blink once and turn off for about 10 seconds.

ACT/STBY LED blinks for about 1 second.

All the LEDs including the CRIT, MAJ, MIN, REM, SYNC, and ACO LEDs turn off for about 10 seconds.

The ACT/STBY, ACO, and PWR LEDs turn on.

The boot-up process is complete when the PWR LEDs turn green and the amber ACT/STBY remains on. The ACT/STBY LED turns green if this is the first TNC/TNCE/TSC/TSCE card installed, and amber if this is the second TNC/TNCE/TSC/TSCE card installed.

Note It might take up to four minutes for the power alarms to clear.

Note Alarm LEDs might be on. After completing the TNC/TNCE/TSC/TSCE card installation, log in to CTC and click the Alarms tab to display the alarms raised on the card. For procedure to clear the alarm, see the Cisco ONS DWDM Troubleshooting Guide.

Note During the TNC/TNCE/TSC/TSCE card initialization, the SFTWDOWN alarm appears twice. The alarm clears after the TNC/TNCE/TSC/TSCE card boots completely.

Note If the FAIL LED is on continuously, see the tip in Step 8 about the TNC/TNCE/TSC/TSCE card automatic upload.

Step 5 Verify that the ACT/STBY LED is green if this is the first powered-up TNC/TNCE/TSC/TSCE card installed or amber if this is the second powered-up TNC/TNCE/TSC/TSCE. The IP address, temperature of the node, and time of day appear on the LCD. The default time and date is 12:00 AM, January 1, 1970.

Step 6 The LCD cycles through the IP address (the default is 192.1.0.2), node name, and software version. Verify that the correct software version is shown on the LCD. The software text string indicates the node type (SDH or SONET) and software release. (For example: SDH 09.20-05L-20.10 indicates it is an SDH software load, Release 9.2. The numbers following the release number do not have any significance.)

Step 7If the LCD shows the correct software version, continue with Step 8. If the LCD does not show the correct software version, refer to your next level of technical support, upgrade the software, or remove the TNC/TNCE/TSC/TSCE card and install a replacement card. Refer to the release-specific software upgrade document to replace the software.

Tip If you install a standby TNC/TNCE/TSC/TSCE card that has a different software version than the active TNC/TNCE/TSC/TSCE card, the standby TNC/TNCE/TSC/TSCE card copies the software version from the active TNC/TNCE/TSC/TSCE card. When the standby card is first inserted, the LEDs follow the normal boot-up sequence. However, after the red FAIL LED turns on for about 5 seconds, the FAIL LED and the ACT/STBY LED begin to flash alternately for up to 30 minutes. After loading the new software, the upgraded TNC/TNCE/TSC/TSCE cards LEDs repeat the appropriate bootup sequence, and the amber ACT/STBY LED turns on.

Step 9 Return to your originating procedure (NTP).

DLP-G605 Provision PPM and Port for the TNC and TNCE Cards

Purpose

(ONS 15454 M2 and ONS 15454 M6 only) This task provisions a PPM and port on TNC and TNCE cards. PPMs are created to support the OSC function.

PPM Type—Displays the PPM associated with the chosen PPM in the above step.

Step 5 Click OK. The newly created PPM appears in the Pluggable Port Modules area. The row in the Pluggable Port Modules area becomes white when the PPM is inserted and the Actual Equipment Type column lists the name of PPM.

Note Each TNC and TNCE cards support UDC/VoIP configuration. You can configure UDC or VoIP on the two SFP ports present on the TNC and TNCE cards. The TNC and TNCE cards support the UDC/VoIP configuration only when OSC is provisioned on the SFP ports.

Note If two nodes are connected through the fiber and if the TNC and TNCE cards in one node has UDC configuration, the TNC and TNCE cards in the other node must also have UDC configuration. The same rule applies to VoIP configuration.

Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TNC and TNCE cards where you want to configure UDC and VoIP.

Step 2 Click the Provisioning > UDC / VOIP tabs.

Step 3 From the Service Type drop-drop list, choose UDC or VOIP.

Note You can configure UDC or VoIP on only one SFP port at a time per TNC or TNCE card. If you want to configure UDC or VoIP on the second SFP port, choose NONE from the Service Type drop-down list for the first port and then choose UDC or VoIP for the second port.

Step 1 Verify that the node you are upgrading has 9.4.x installed. The software version is displayed in the upper left corner of the window.

Step 2 Back up the database before beginning the upgrade.

Step 3 Physically replace the standby TSC card with a TNC card.

a. Check the LED on the faceplate. The ACT/STBY LED on the faceplate of the TNC/TSC card indicates whether the card is in active or standby mode. A green ACT/STBY LED indicates an active card and an amber light indicates a standby card.

b. Open the ejectors on the standby TSC card.

c. Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete.

d. Right-click the slot from which the TSC card was ejected out.

e. Click Delete Card to delete TSC from CTC.

Note If the TSC card is not deleted from the CTC shelf view before inserting the TNC card, the MEA (card mismatch) alarm appears on that slot.

Note It takes approximately 10 minutes for the active TSC card to copy the system software and database to the newly installed TNC card. During this operation, the LEDs on the TNC card flash Fail and then the active/standby LED flashes. When the transfer completes, the TNC card reboots and goes into standby mode after approximately three minutes. Do not remove the card from the shelf during a database transfer.

Caution If your active TSC card resets during the upgrade before the new TNC card is in full standby mode, remove the new TNC card immediately.