Cisco ONS 15454 DWDM Configuration Guide, Release 9.4

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.

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:

• MIC-A/P
• MIC-C/T/P

3.3.1 Faceplate and Block Diagram

Figure 3-1 shows the faceplate and block diagram for the TCC2 card.

Figure 3-1 TCC2 Faceplate and Block Diagram

3.3.2 TCC2 Card Functions

The functions of the TCC2 card are:

• Communication and Control for Controller Cards
• Timing Synchronization
• Interface Ports
• Redundant Controller Card Installation
• Card level indicators—Table G-1
• Network level indicators—Table G-13

3.3.3 Related Procedures for TCC2 Card

The following is the list of procedures and tasks related to the configuration of the TCC2 card:

• G15 Install the Common Control Cards
• NTP-G18 Set Up CTC Computer for Local Craft Connection to the ONS 15454
• NTP-G17 Set Up Computer for CTC
• G22 Verify Common Card Installation
• G144 Provision a Multishelf Node
• G25 Set Battery Power Monitor Thresholds
• G26 Set Up CTC Network Access
• G143 Import the Cisco Transport Planner NE Update Configuration File
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• G51 Verify DWDM Node Turn Up
• NTP-G81 Change CTC Network Access
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• G105 Restore the Node to Factory Configuration

3.4.1 Faceplate and Block Diagram

Figure 3-2 shows the faceplate and block diagram for the TCC2P card.

Figure 3-2 TCC2P Faceplate and Block Diagram

3.4.2 TCC2P Card Functions

The functions of the TCC2P card are:

• Communication and Control for Controller Cards
• Timing Synchronization
• Interface Ports
• Database Storage
• Redundant Controller Card Installation
• Card level indicators—Table G-1 l
• Network level indicators—Table G-13
• Power level indicators—Table G-11

3.4.3 Related Procedures for TCC2P Card

The following is the list of procedures and tasks related to the configuration of the TCC2P card:

• G15 Install the Common Control Cards
• NTP-G18 Set Up CTC Computer for Local Craft Connection to the ONS 15454
• NTP-G17 Set Up Computer for CTC
• DLP-G43 Disable or Bypass Proxy Service Using Internet Explorer (Windows)
• DLP-G44 Disable or Bypass Proxy Service Using Mozilla (Solaris)
• DLP-G48 Create Login Node Groups
• DLP-G49 Add a Node to the Current Session or Login Group
• G22 Verify Common Card Installation
• G144 Provision a Multishelf Node
• G25 Set Battery Power Monitor Thresholds
• G26 Set Up CTC Network Access
• G143 Import the Cisco Transport Planner NE Update Configuration File
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• G51 Verify DWDM Node Turn Up
• NTP-G81 Change CTC Network Access
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• G105 Restore the Node to Factory Configuration

3.5.1 Faceplate and Block Diagram

Figure 3-3 shows the faceplate and block diagram for the TCC3 card.

Figure 3-3 TCC3 Faceplate and Block Diagram

3.5.2 TCC3 Card Functions

The functions of the TCC3 card are:

• Communication and Control for Controller Cards
• Timing Synchronization
• Interface Ports
• Database Storage
• Redundant Controller Card Installation
• Card level indicators—Table G-1
• Network level indicators—Table G-13
• Power level indicators—Table G-12

3.5.3 Related Procedures for TCC3 Card

The following is the list of procedures and tasks related to the configuration of the TCC3 card:

• G15 Install the Common Control Cards
• NTP-G18 Set Up CTC Computer for Local Craft Connection to the ONS 15454
• NTP-G17 Set Up Computer for CTC
• DLP-G43 Disable or Bypass Proxy Service Using Internet Explorer (Windows)
• DLP-G44 Disable or Bypass Proxy Service Using Mozilla (Solaris)
• DLP-G48 Create Login Node Groups
• DLP-G49 Add a Node to the Current Session or Login Group
• G22 Verify Common Card Installation
• G144 Provision a Multishelf Node
• G25 Set Battery Power Monitor Thresholds
• G26 Set Up CTC Network Access
• G143 Import the Cisco Transport Planner NE Update Configuration File
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• G51 Verify DWDM Node Turn Up
• NTP-G81 Change CTC Network Access
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• G105 Restore the Node to Factory Configuration

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.

Figure 3-5 TNCE Faceplate and Block Diagram

3.6.2 TNC and TNCE Card Functions

The functions of the TNC and TNCE cards are:

• Communication and Control for Controller Cards
• Optical Service Channel
• Timing Synchronization
• MultiShelf Management
• Database Storage
• Interface Ports
• External Alarms and Controls
• Lamp Test
• Redundant Controller Card Installation
• Card level indicators—Table G-1
• Network level indicators—Table G-13
• Power level indicators—Table G-12
• Port level indicators—Table G-14
• TNC and TNCE SFP indicators—Table G-15
• Protection Schemes
• Cards Supported by TNC/TNCE/TSC/TSCE

3.6.3 Related Procedures for TNC and TNCE Cards

The following is the list of procedures and tasks related to the configuration of the TNC and TNCE cards:

• G313 Install and Configure the TNC, TNCE, TSC, or TSCE Card
• NTP-G17 Set Up Computer for CTC
• DLP-G43 Disable or Bypass Proxy Service Using Internet Explorer (Windows)
• DLP-G44 Disable or Bypass Proxy Service Using Mozilla (Solaris)
• DLP-G48 Create Login Node Groups
• DLP-G49 Add a Node to the Current Session or Login Group
• DLP-G41 Set Up a Windows PC for Craft Connection to an ONS 15454 Using Automatic Host Detection
• NTP-G19 Set Up a CTC Computer for a Corporate LAN Connection to the ONS 15454
• G22 Verify Common Card Installation
• G250 Verify Digital Image Signing (DIS) Information
• NTP-G279 Monitor TNC and TNCE Card Performance
• G144 Provision a Multishelf Node
• G25 Set Battery Power Monitor Thresholds
• G26 Set Up CTC Network Access
• G143 Import the Cisco Transport Planner NE Update Configuration File
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• G51 Verify DWDM Node Turn Up
• NTP-G81 Change CTC Network Access
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• NTP-G277 Provision Alarms and Controls on the TNC, TNCE, TSC, or TSCE Card
• G105 Restore the Node to Factory Configuration

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.

Figure 3-6 TSC Faceplate and Block Diagram

Figure 3-7 illustrates the faceplate for the TSCE card.

Figure 3-7 TSCE Faceplate

3.7.2 TSC and TSCE Card Functions

The functions of the TSC and TSCE cards are:

• Communication and Control for Controller Cards
• Timing Synchronization
• MultiShelf Management
• Database Storage
• Interface Ports
• External Alarms and Controls
• Lamp Test
• Redundant Controller Card Installation
• Card level indicators—Table G-1
• Network level indicators—Table G-13
• Power level indicators—Table G-12
• Port level indicators—Table G-14
• Protection Schemes
• Cards Supported by TNC/TNCE/TSC/TSCE

3.7.3 Related Procedures for TSC and TSCE Cards

The following is the list of procedures and tasks related to the configuration of the TSC and TSCE cards:

• G313 Install and Configure the TNC, TNCE, TSC, or TSCE Card
• NTP-G17 Set Up Computer for CTC
• DLP-G43 Disable or Bypass Proxy Service Using Internet Explorer (Windows)
• DLP-G44 Disable or Bypass Proxy Service Using Mozilla (Solaris)
• DLP-G48 Create Login Node Groups
• DLP-G49 Add a Node to the Current Session or Login Group
• DLP-G41 Set Up a Windows PC for Craft Connection to an ONS 15454 Using Automatic Host Detection
• NTP-G19 Set Up a CTC Computer for a Corporate LAN Connection to the ONS 15454
• G22 Verify Common Card Installation
• G250 Verify Digital Image Signing (DIS) Information
• G144 Provision a Multishelf Node
• G25 Set Battery Power Monitor Thresholds
• G26 Set Up CTC Network Access
• G143 Import the Cisco Transport Planner NE Update Configuration File
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• G51 Verify DWDM Node Turn Up
• NTP-G81 Change CTC Network Access
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• G103 Back Up the Database
• G104 Restore the Database
• G106 Reset Cards Using CTC
• NTP-G277 Provision Alarms and Controls on the TNC, TNCE, TSC, or TSCE Card
• G280 Modify Threshold Settings for the TNC and TNCE Cards
• NTP-G278 Upgrade the TSC Card to the TNC Card
• G105 Restore the Node to Factory Configuration

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:

3.8.2 Related Procedures for DIS

To verify DIS, see G250 Verify Digital Image Signing (DIS) Information.

3.9.1 Faceplate and Block Diagram

Figure 3-8 shows the AIC-I faceplate and a block diagram of the card.

Figure 3-8 AIC-I Faceplate and Block Diagram

3.9.2 AIC-I Card-Level Indicators

Table G-2 lists the card-level LEDs on the card.

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.

Caution Do not configure orderwire loops. Orderwire loops cause feedback that disables the orderwire channel.

---

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.

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

Figure 3-9 shows the standard RJ-11 connectors used for orderwire ports.

Figure 3-9 RJ-11 Connector

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.

The UDC ports are standard RJ-11 receptacles. Table 3-4 lists the UDC pin assignments.

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.

The DCC ports are synchronous serial interfaces. The DCC ports are standard RJ-45 receptacles. Table 3-5 lists the DCC pin assignments.

3.9.8 Related Procedures for AIC-I Card

The following is the list of procedures and tasks related to the configuration of the AIC-I card:

• G15 Install the Common Control Cards
• G22 Verify Common Card Installation
• G60 Create and Delete Overhead Circuits
• NTP-G72 Provision External Alarms and Controls on the Alarm Interface Controller-International Card
• G101 Modify Alarm Interface Controller–International Settings

3.10.1 Faceplate Diagram

Figure 3-10 shows the card faceplate.

Figure 3-10 MS-ISC-100T Faceplate

3.10.2 MS-ISC-100T Card-Level Indicators

Table G-3 lists the card-level LEDs on the card.

3.10.3 Related Procedures for MS-ISC-100T Card

The following is the list of procedures and tasks related to the configuration of the MS-ISC-100T card:

• G15 Install the Common Control Cards
• G22 Verify Common Card Installation
• G144 Provision a Multishelf Node
• G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode
• NTP-G146 Add a Rack, Passive Unit, or Shelf to a Multishelf Node
• NTP-G147 Delete a Passive Unit, Shelf, or Rack from a Multishelf Node

3.11.1 MIC-A/P FMEC

Note For hardware specifications, see the “MIC-A/P FMEC Specifications (ETSI only)” section in the Hardware Specifications document.

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.2 Faceplate and Block Diagram

MIC-A/P Faceplate shows the MIC-A/P faceplate.

Figure 3-11 MIC-A/P Faceplate

Figure 3-12 shows a block diagram of the MIC-A/P.

Figure 3-12 MIC-A/P Block Diagram

Table 3-7 shows the alarm interface pinouts on the MIC-A/P DB-62 connector.

3.11.3 MIC-C/T/P FMEC

Note For hardware specifications, see the “MIC-C/T/P FMEC Specifications (ETSI only)” section in the Hardware Specifications document.

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.

3.11.4 Faceplate and Block Diagram

Figure 3-13 show s the MIC-C/T/P FMEC faceplate.

Figure 3-13 MIC-C/T/P Faceplate

Figure 3-14 shows a block diagram of the MIC-C/T/P.

Figure 3-14 MIC-C/T/P Block Diagram

The MIC-C/T/P FMEC has one pair of LEDs located on the RJ45 LAN connector. The green LED is on when a link is present, and the amber LED is on when data is being transferred.

3.12.1 Before You Begin

Before performing any of the following procedures, investigate all alarms and clear any trouble conditions. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide as necessary.

This section lists the chapter procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).

• G15 Install the Common Control Cards—Complete this procedure to install the control cards needed for the ONS 15454 platform.
• G313 Install and Configure the TNC, TNCE, TSC, or TSCE Card—Complete this procedure to install the control cards needed for the ONS 15454 M2 and ONS 15454 M6 platforms.

NTP-G15 Install the Common Control Cards

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

Caution Always use the supplied ESD wristband when working with a powered ONS 15454. For detailed instructions on how to wear the ESD wristband, refer to the Electrostatic Discharge and Grounding Guide for Cisco CPT and Cisco ONS Platforms.

---

Note If protective clips are installed on the backplane connectors of the cards, remove the clips before installing the cards.

Note If you install a card incorrectly, the FAIL LED flashes continuously.

Step 1 (ONS 15454 only) Complete the G33 Install the TCC2, TCC2P, or TCC3 Card.

Note If you install the wrong card in a slot, see the NTP-G107 Remove Permanently or Remove and Replace DWDM Cards.

Step 2 (ONS 15454 only) Complete the G34 Install the AIC-I Card, if necessary.

Step 3 (ONS 15454 only) Complete the G309 Install the MS-ISC-100T Card, if necessary.

Stop. You have completed this procedure.

DLP-G33 Install the TCC2, TCC2P, or TCC3 Card

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 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 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 4 As 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 5 Verify 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 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 7 If 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 8 Repeat 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.

Step 9 Return to your originating procedure (NTP).

DLP-G34 Install the AIC-I Card

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

Step 1 Open 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 4 Verify 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

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 4 Verify 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.

Step 5 Repeat Steps 1 through 4 for the redundant MS-ISC-100T card.

Step 6 Return to your originating procedure (NTP).

NTP-G313 Install and Configure the TNC, TNCE, TSC, or TSCE Card

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

Caution Always use the supplied ESD wristband when working with a powered ONS 15454 M2 and ONS 15454 M6 shelf assemblies. For detailed instructions on how to wear the ESD wristband, refer to the Electrostatic Discharge and Grounding Guide for Cisco CPT and Cisco ONS Platforms.

---

Note If you install a card incorrectly, the FAIL LED flashes continuously.

Step 1 Complete the G604 Install the TNC, TNCE, TSC, or TSCE Card.

Note If you install the wrong card in a slot, see the NTP-G107 Remove Permanently or Remove and Replace DWDM Cards.

Step 2 Complete the G605 Provision PPM and Port for the TNC and TNCE Cards.

Step 3 Complete the G606 Configure UDC and VoIP for the TNC and TNCE Cards.

Step 4 Complete the G774 Change the Frame Type on the OSC.

Stop. You have completed this procedure.

DLP-G604 Install the TNC, TNCE, TSC, or TSCE Card

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 Allow each TNC/TNCE/TSC/TSCE card to boot completely before installing the redundant TNC/TNCE/TSC/TSCE card.

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 1 Open 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.

Figure 3-15 illustrates the installation of TNC and TNCE cards on ONS 15454 M6 shelf.

Figure 3-15 Installing TNC and TNCE Cards on ONS 15454 M6 Shelf

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 7 If 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.

Step 8 (ONS 15454 M6 shelf only) Repeat Steps 1 through 7 for the redundant TNC/TNCE/TSC/TSCE card.

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

Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TNC and TNCE cards where you want to provision PPM and port settings.

Step 2 Click the Provisioning > Pluggable Port Modules tabs.

Step 3 In the Pluggable Port Modules area, click Create. The Create PPM dialog box appears.

Step 4 In the Create PPM dialog box, complete the following:

• PPM—Choose 1 or 2 from the PPM drop-down list.
• 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.

Step 6 In the Pluggable Ports area, click Create. The Create Port dialog box appears.

Step 7 In the Create Ports dialog box, complete the following:

• Port—Choose the port you want to configure from the Port drop-down list.
• Port Type—Choose the port type, such as OC-3, FE, or ONE-GE from the Port Type drop-down list.

Note OC-3 can be configured only on PPM port 1. FE and ONE-GE can be configured on both the ports. If the port type is FE, then disable ALS before provisioning OSC on that port.

Step 8 Click OK. The newly created port appears in the Pluggable Ports area. The port type you provisioned is listed in the Rate column.

Step 9 Repeat Steps 3 through 8 to provision another PPM and port on the TNC and TNCE cards.

Step 10 Return to your originating procedure (NTP).

DLP-G606 Configure UDC and VoIP for the TNC and TNCE Cards

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 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-G774 Change the Frame Type on the OSC

Step 1 Delete the OC-3, STM1, FE, or ONE_GE OSC communication channel. See DLP-G186 Delete an OSC Termination.

Step 2 Click the Provisioning > WDM-ANS > Internal Patchcords tabs.

Step 3 Choose the internal patchcord that is associated with OSC and click Delete.

Step 4 Delete the OSC payload on the TNC/TNCE card.

a. In node view (single-shelf mode) or shelf view (multishelf view), double-click the TNC/TNCE card where you want to delete the OSC payload.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. In the Pluggable Ports area, choose the OSC payload that you want to delete and click Delete.

Step 5 Provision the OSC payload on the TNC/TNCE card. See G605 Provision PPM and Port for the TNC and TNCE Cards.

Note OC-3/STM1 can be configured only on port 1. FE and ONE-GE can be configured on both the ports.

Step 6 Provision the internal patchcord from the OSC on the TNC card to the corresponding line card. See Virtual Patchcords.

Step 7 Provision the OSC communication channel. See NTP-G38 Provision OSC Terminations.

Step 8 Repeat the above steps for the other node.

Step 9 Return to your originating procedure (NTP).