Chapter 18, CTC Operation Reference

Note Unless otherwise specified, "ONS 15454" refers to both ANSI and ETSI shelf assemblies.

18.1 CTC Software Delivery Methods

ONS 15454 provisioning and administration is performed using the CTC software. CTC is a Java application that is installed in two locations: it is stored on the TCC2 or TCC2P card and it is downloaded to your workstation the first time you log into the ONS 15454 with a new software release.

18.1.1 CTC Software Installed on the TCC2/TCC2P Card

CTC software is preloaded on the ONS 15454 TCC2/TCC2P cards; therefore, you do not need to install software on the TCC2/TCC2P cards. When a new CTC software version is released, use the release-specific software upgrade document to upgrade the ONS 15454 software on the TCC2/TCC2P card.

When you upgrade CTC software, the TCC2/TCC2P cards store the new CTC version as the protect CTC version. When you activate the new CTC software, the TCC2/TCC2P cards store the older CTC version as the protect CTC version, and the newer CTC release becomes the working version. You can view the software versions that are installed on an ONS 15454 by selecting the Maintenance > Software tabs in node view ( Figure 18-1).

Select the Maintenance > Software tabs in network view to display the software versions installed on all the network nodes ( Figure 18-2).

18.1.2 CTC Software Installed on the PC or UNIX Workstation

CTC software is downloaded from the TCC2/TCC2P cards and installed on your computer automatically after you connect to the ONS 15454 with a new software release for the first time. Downloading the CTC software files automatically ensures that your computer is running the same CTC software version as the TCC2/TCC2P cards you are accessing. The CTC files are stored in the temporary directory designated by your computer operating system. You can use the Delete CTC Cache button to remove files stored in the temporary directory. If the files are deleted, they download the next time you connect to an ONS 15454. Downloading the Java archive (JAR) files for CTC takes several minutes depending on the bandwidth of the connection between your workstation and the ONS 15454. For example, JAR files downloaded from a modem or a data communications channel (DCC) network link require more time than JAR files downloaded over a LAN connection.

18.2 CTC Installation Overview

To connect to an ONS 15454 using CTC, you enter the ONS 15454 IP address in the URL field of Netscape Navigator or Microsoft Internet Explorer. After connecting to an ONS 15454, the following occurs automatically:

A CTC launcher applet is downloaded from the TCC2/TCC2P card to your computer.

The launcher determines whether your computer has a CTC release matching the release on the ONS 15454 TCC2/TCC2P card.

If the computer does not have CTC installed, or if the installed release is older than the TCC2/TCC2P card's version, the launcher downloads the CTC program files from the TCC2/TCC2P card.

The launcher starts CTC. The CTC session is separate from the web browser session, so the web browser is no longer needed. Always log into nodes having the latest software release. If you log into an ONS 15454 that is connected to ONS 15454s with older versions of CTC, or to Cisco ONS 15327s or Cisco ONS 15600s, CTC files are downloaded automatically to enable you to interact with those nodes. The CTC file download occurs only when necessary, such as during your first login. You cannot interact with nodes on the network that have a software version later than the node that you used to launch CTC.

Each ONS 15454 can handle up to five concurrent CTC sessions. CTC performance can vary, depending upon the volume of activity in each session, network bandwidth, and TCC2/TCC2P card load.

Note You can also use TL1 commands to communicate with the Cisco ONS 15454 through VT100 terminals and VT100 emulation software, or you can telnet to an ONS 15454 using TL1 port 3083. Refer to the Cisco ONS SONET TL1 Command Guide or Cisco ONS 15454 SDH TL1 Command Guide for a comprehensive list of TL1 commands.

18.3 PC and UNIX Workstation Requirements

To use CTC for the ONS 15454, your computer must have a web browser with the correct Java Runtime Environment (JRE) installed. The correct JRE for each CTC software release is included on the Cisco ONS 15454 software CD and the ONS 15454 documentation CD. If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible with the different software releases.

When you change the JRE version on the JRE tab, you must exit and restart CTC for the new JRE version to take effect. Table 18-1 shows JRE compatibility with ONS 15454 software releases.

Table 18-1 JRE Compatibility
ONS Software Release	JRE 1.2.2 Compatible	JRE 1.3 Compatible	JRE 1.4 Compatible
ONS 15454 Release 4.1	No	Yes	No
ONS 15454 Release 4.5	No	Yes	No
ONS 15454 Release 4.6	No	Yes	Yes
ONS 15454 Release 4.7	No	No	Yes
ONS 15454 Release 5.0	No	No	Yes

Table 18-2 lists the requirements for PCs and UNIX workstations. In addition to the JRE, the Java plug-in and modified java.policy file are also included on the ONS 15454 software CD and the ONS 15454 documentation CD.

Table 18-2 Computer Requirements for CTC
Area	Requirements	Notes
Processor	Pentium III 700 MHz, UltraSPARC, or equivalent	700 MHz is the recommended processor speed. You can use computers with a lower processor speed; however, you might experience longer response times and slower performance.
RAM	384 MB RAM recommended, 512 MG RAM optimum	—
Hard drive	20 GB hard drive with 50 MB of space available	—
Operating System	•PC: Windows 98 (1st and 2nd editions), Windows ME, Windows NT 4.0 (with Service Pack 6a), Windows 2000 (with Service Pack 3), or Windows XP Home •Workstation: Solaris versions 8 or 9	—
Java Runtime Environment	JRE 1.4.2	JRE 1.4.2 is installed by the CTC Installation Wizard included on the Cisco ONS 15454 software and documentation CDs. JRE 1.4.2 provides enhancements to CTC performance, especially for large networks with numerous circuits. If CTC must be launched directly from nodes running software earlier than R4.6, uninstall JRE 1.4.2 and reinstall JRE 1.3.1_02, then, to run R5.0, uninstall JRE 1.3.1_02 and reinstall JRE 1.4.2.
Web browser	Netscape 7.x or Internet Explorer 6.x	Netscape 7.x is available at the following site: http://channels.netscape.com/ns/browsers/default.jsp Internet Explorer 6.x is available at the following site: http://www.microsoft.com
Cable	User-supplied CAT-5 straight-through cable with RJ-45 connectors on each end to connect the computer to the ONS 15454 directly or through a LAN	—

18.4 ONS 15454 Connections

You can connect to the ONS 15454 in multiple ways. You can connect your PC directly to the ONS 15454 (local craft connection) using the RJ-45 port on the TCC2/TCC2P card or, for the ANSI shelf, the LAN pins on the backplane (the ETSI shelf provides a LAN connection via the RJ-45 jack on the MIC-T/C/P FMEC). Alternatively, you can connect your PC to a hub or switch that is connected to the ONS 15454, connect to the ONS 15454 through a LAN or modem, or establish TL1 connections from a PC or TL1 terminal. Table 18-3 lists the ONS 15454 connection methods and requirements.

Table 18-3 ONS 15454 Connection Methods
Method	Description	Requirements
Local craft	Refers to onsite network connections between the CTC computer and the ONS 15454 using one of the following: •The RJ-45 (LAN) port on the TCC2/TCC2P card •The LAN pins on the ONS 15454 backplane (ANSI) •The RJ-45 jack on the MIC-T/C/P FMEC (ETSI) •A hub or switch to which the ONS 15454 is connected	If you do not use Dynamic Host Configuration Protocol (DHCP), you must change the computer IP address, subnet mask, and default router, or use automatic host detection.
Corporate LAN	Refers to a connection to the ONS 15454 through a corporate or network operations center (NOC) LAN.	•The ONS 15454 must be provisioned for LAN connectivity, including IP address, subnet mask, and default gateway. •The ONS 15454 must be physically connected to the corporate LAN. •The CTC computer must be connected to the corporate LAN that has connectivity to the ONS 15454.
TL1	Refers to a connection to the ONS 15454 using TL1 rather than CTC. TL1 sessions can be started from CTC, or you can use a TL1 terminal. The physical connection can be a craft connection, corporate LAN, or a TL1 terminal.	Refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.
Remote	Refers to a connection made to the ONS 15454 using a modem.	•A modem must be connected to the ONS 15454. •The modem must be provisioned for the ONS 15454. To run CTC, the modem must be provisioned for Ethernet access.

18.5 CTC Window

The CTC window appears after you log into an ONS 15454 ( Figure 18-3). The window includes a menu bar, a toolbar, and a top and bottom pane. The top pane provides status information about the selected objects and a graphic of the current view. The bottom pane provides tabs and subtab to view ONS 15454 information and perform ONS 15454 provisioning and maintenance. From this window, you can display three ONS 15454 views: network, node, and card.

18.5.1 Node View

Node view, shown in Figure 18-3, is the first view that appears after you log into an ONS 15454. The login node is the first node shown, and it is the "home view" for the session. Node view allows you to manage one ONS 15454 node. The status area shows the node name; IP address; session boot date and time; number of Critical (CR), Major (MJ), and Minor (MN) alarms; name and security level of the current logged-in user; software version; and network element default setup.

18.5.1.1 CTC Card Colors

The graphic area of the CTC window depicts the ONS 15454 shelf assembly. The colors of the cards in the graphic reflect the real-time status of the physical card and slot ( Table 18-4).

Table 18-4 Node View Card Colors
Card Color	Status
Gray	Slot is not provisioned; no card is installed.
Violet	Slot is provisioned; no card is installed.
White	Slot is provisioned; a functioning card is installed.
Yellow	Slot is provisioned; a Minor alarm condition exists.
Orange	Slot is provisioned; a Major alarm condition exists.
Red	Slot is provisioned; a Critical alarm exists.

On the ONS 15454 ETSI, the colors of the Front Mount Electrical Connection (FMEC) cards reflect the real-time status of the physical FMEC cards. Table 18-5 lists the FMEC card colors. The FMEC ports shown in CTC do not change color.

Table 18-5 Node View FMEC Color
Upper Shelf FMEC Color	Status
White	Functioning card is installed.
Yellow	Minor alarm condition exists.
Orange (Amber)	Major alarm condition exists.
Red	Critical alarm exists.

The wording on a card in node view shows the status of a card (Active, Standby, Loading, or Not Provisioned). Table 18-6 lists the card statuses.

Table 18-6 Node View Card Statuses
Card Status	Description
Sty	Card is in standby mode.
Act	Card is active.
NP	Card is not present.
Ldg	Card is resetting.

Table 18-7 Node View Card Port Colors and Service States
Port Color	Service State	Description
Cyan (blue)	Out-of-Service and Management, Loopback (OOS-MA,LPBK [ANSI]) Locked-enabled,loopback (ETSI)	Port is in a loopback state. On the card in node view, a line between ports indicates that the port is in terminal or facility loopback (see Figure 18-4 and Figure 18-5). Traffic is carried and alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command.
Cyan (blue)	Out-of-Service and Management, Maintenance (OOS-MA,MT [ANSI]) Locked-enabled,maintenance (ETSI)	Port is out-of-service for maintenance. Traffic is carried and loopbacks are allowed. Alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Use this service state for testing or to suppress alarms temporarily. Change the state to IS-NR/Unlocked-enabled; OOS-MA,DSBLD/Locked-enabled,disabled; or OOS-AU,AINS/Unlocked-disabled,automaticInService when testing is complete.
Gray	Out-of-Service and Management, Disabled (OOS-MA,DSBLD [ANSI]) Locked-enabled,disabled (ETSI)	The port is out-of-service and unable to carry traffic. Loopbacks are not allowed in this service state.
Green	In-Service and Normal (IS-NR [ANSI]) Unlocked-enabled (ETSI)	The port is fully operational and performing as provisioned. The port transmits a signal and displays alarms; loopbacks are not allowed.
Violet	Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS [ANSI]) Unlocked-disabled,automaticInService (ETSI)	The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in this service state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR/Unlocked-enabled. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. The AINS port will automatically transition to IS-NR/Unlocked-enabled when a signal is received for the length of time provisioned in the soak field.

18.5.1.2 Node View Card Shortcuts

If you move your mouse over cards in the graphic, popups display additional information about the card including the card type; the card status (active or standby); the type of alarm, such as Critical, Major, or Minor (if any); the alarm profile used by the card; and for transponder (TXP) or muxponder (MXP) cards, the wavelength of the dense wavelength division multiplexing (DWDM) port. Right-click a card to reveal a shortcut menu, which you can use to open, reset, delete, or change a card. Right-click a slot to preprovision a card (that is, provision a slot before installing the card).

18.5.1.3 Node View Tabs

Table 18-8 Node View Tabs and Subtabs
Tab	Description	Subtabs
Alarms	Lists current alarms (CR, MJ, MN) for the node and updates them in real time.	—
Conditions	Displays a list of standing conditions on the node.	—
History	Provides a history of node alarms including date, type, and severity of each alarm. The Session subtab displays alarms and events for the current session. The Node subtab displays alarms and events retrieved from a fixed-size log on the node.	Session, Node
Circuits	Creates, deletes, edits, and maps circuits.	—
Provisioning	Provisions the ONS 15454 node.	General, Ether Bridge, Network, Protection, BLSR, Security, SNMP, Comm Channels, Timing, Alarm Profiles, Defaults, UCP, WDM-ANS
Inventory	Provides inventory information (part number, serial number, Common Language Equipment Identification [CLEI] codes) for cards installed in the node. Allows you to delete and reset cards and change the card service state.	—
Maintenance	Performs maintenance tasks for the node.	Database, Ether Bridge, Protection, BLSR (ANSI), MS-SPRing (ETSI), Software, Cross-Connect, Overhead XConnect, Diagnostic, Timing, Audit, Routing Table, RIP Routing Table, Test Access, DWDM

18.5.2 Network View

Network view allows you to view and manage ONS 15454s that have DCC connections to the node that you logged into and any login node groups you have selected ( Figure 18-6).

Note Nodes with DCC connections to the login node do not appear if you checked the Disable Network Discovery check box in the Login dialog box.

The graphic area displays a background image with colored ONS 15454 icons. A Superuser can set up the logical network view feature, which enables each user to see the same network view.

The lines show DCC connections between the nodes ( Table 18-9). DCC connections can be green (active) or gray (fail). The lines can also be solid (circuits can be routed through this link) or dashed (circuits cannot be routed through this link). Circuit provisioning uses active/routable links. Selecting a node or span in the graphic area displays information about the node and span in the status area.

Table 18-9 DCC Colors Indicating State in Network View
Color and Line Style	State
Green and solid	Active/Routable
Green and dashed	Active/Nonroutable
Gray and solid	Failed/Routable
Gray and dashed	Failed/Nonroutable

The color of a node in network view, shown in Table 18-10, indicates the node alarm status.

Table 18-10 Node Status Shown in Network View
Color	Alarm Status
Green	No alarms
Yellow	Minor alarms
Orange	Major alarms
Red	Critical alarms
Gray with Unknown#	Node initializing for the first time (CTC displays Unknown# because CTC has not discovered the name of the node yet)

Table 18-11 Network View Tabs and Subtabs
Tab	Description	Subtabs
Alarms	Lists current alarms (CR, MJ, MN) for the network and updates them in real time.	—
Conditions	Displays a list of standing conditions on the network.	—
History	Provides a history of network alarms including date, type, and severity of each alarm.	—
Circuits	Creates, deletes, edits, filters, and searches for network circuits.	—
Provisioning	Provisions security, alarm profiles, bidirectional line switched rings (BLSRs) (ANSI), multiplex section-shared protection rings (MS-SPRing) (ETSI), and overhead circuits.	Security, Alarm Profiles, BLSR (ANSI), MS-SPRing (ETSI), Overhead Circuits, Provisionable Patchcords
Maintenance	Displays the type of equipment and the status of each node in the network; displays working and protect software versions; and allows software to be downloaded.	Software

18.5.3 Card View

The card view provides information about individual ONS 15454 cards. Use this window to perform card-specific maintenance and provisioning ( Figure 18-7). A graphic showing the ports on the card is shown in the graphic area. The status area displays the node name, slot, number of alarms, card type, equipment type, card status (active or standby), card service state if the card is present, and port service state (described in Table 18-7). The information that appears and the actions you can perform depend on the card. For more information about card service states, refer to Appendix C, "DWDM Administrative and Service States."

Note CTC provides a card view for all ONS 15454 cards except the TCC2/TCC2P card.

Use the card view tabs and subtabs shown in Table 18-12 to provision and manage the ONS 15454. The subtabs, fields, and information shown under each tab depend on the card type selected. The Performance tab is not available for the Alarm Interface Controller (AIC) or Alarm Interface Controller-International (AIC-I) cards.

Table 18-12 Card View Tabs and Subtabs
Tab	Description	Subtabs
Alarms	Lists current alarms (CR, MJ, MN) for the card and updates them in real time.	—
Conditions	Displays a list of standing conditions on the card.	—
History	Provides a history of card alarms including date, object, port, and severity of each alarm.	Session (displays alarms and events for the current session), Card (displays alarms and events retrieved from a fixed-size log on the card)
Circuits	Creates, deletes, edits, and search circuits.	—
Provisioning	Provisions an ONS 15454 card.	DS-N and OC-N cards: Line, Line Thresholds (different threshold options are available for DS-N and OC-N cards), Elect Path Thresholds, SONET Thresholds, SONET STS, and Alarm Profiles TXP and MXP cards: Card, Line, Line Thresholds, Optics Thresholds, OTN, and Alarm Profiles DWDM cards (subtabs depend on card type): Optical Line, Optical Chn, Optical Amplifier, Parameters, Optics Thresholds, and Alarm Profiles
Maintenance	Performs maintenance tasks for the card.	Loopback, Info, Protection, J1 Path Trace, AINS Soak (options depend on the card type), Automatic Laser Shutdown
Performance	Performs performance monitoring for the card.	DS-N and OC-N cards: no subtabs TXP and MXP cards: Optics PM, Payload PM, OTN PM DWDM cards (subtabs depend on card type): Optical Line, Optical Chn, Optical Amplifier Line, OC3 Line, Parameters, Optics Thresholds
Inventory	Displays an Inventory screen of the ports (TXP and MXP cards only).	—

18.6 TCC2/TCC2P Card Reset

You can reset the ONS 15454 TCC2/TCC2P card by using CTC (a soft reset) or by physically reseating a TCC2/TCC2P card (a hard reset). A soft reset reboots the TCC2/TCC2P card and reloads the operating system and the application software. Additionally, a hard reset temporarily removes power from the TCC2/TCC2P card and clears all buffer memory.

You can apply a soft reset from CTC to either an active or standby TCC2/TCC2P card without affecting traffic. If you need to perform a hard reset on an active TCC2/TCC2P card, put the TCC2/TCC2P card into standby mode first by performing a soft reset.

Note When a CTC reset is performed on an active TCC2/TCC2P card, the AIC and AIC-I cards go through an initialization process and also reset because the AIC and AIC-I cards are controlled by the active TCC2/TCC2P.

18.7 TCC2/TCC2P Card Database

When dual TCC2/TCC2P cards are installed in the ONS 15454, each TCC2/TCC2P card hosts a separate database; therefore, the protect card database is available if the database on the working TCC2/TCC2P fails. You can also store a backup version of the database on the workstation running CTC. This operation should be part of a regular ONS 15454 maintenance program at approximately weekly intervals, and should also be completed when preparing an ONS 15454 for a pending natural disaster, such as a flood or fire.

Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up database with a different node name, the circuits map to the new node name. Cisco recommends keeping a record of the old and new node names.

18.8 Software Revert

When you click the Activate button after a software upgrade, the TCC2/TCC2P card copies the current working database and saves it in a reserved location in the TCC2/TCC2P card flash memory. If later during the upgrade you need to revert to the original working software load from the protect software load, the saved database installs automatically. You do not need to restore the database manually or recreate circuits.

The revert feature is useful if the maintenance window in which you were performing an upgrade closes while you are still upgrading CTC software. You can revert to the protect software load without losing traffic. During the next maintenance window, you can complete the upgrade and activate the new software load.

Circuits created or provisioning done after you activate a new software load (upgrade to a higher release) will be lost with a revert. The database configuration at the time of activation is reinstated after a revert. (This does not apply to maintenance reverts, such as R5.0.1 to 5.0.2, because maintenance releases retain the database during activation.)

To perform a supported (non-service-affecting) revert from a software release you have just activated, the release you revert to must have been working at the time you first activated the new software on that node. Because a supported revert automatically restores the node configuration at the time of the previous activation, any configuration changes made after activation will be lost when you revert the software. Downloading the software release you are upgrading to a second time after you have activated the new load ensures that no actual revert to a previous load can take place (the TCC2/TCC2P will reset, but will not be traffic affecting and will not change your database).

Note To perform a supported software upgrade or revert you must consult the specific upgrade document and release notes for the release you are upgrading to (or reverting from).

Table Of Contents

CTC Operation Reference