Document Procedures

Procedures in this document must be performed in consecutive order unless noted otherwise. Ensure that the procedure is completed for each node in a given network. If you are new to upgrading the ONS 15600, make a printed copy of this document and use it as a checklist.

Each non-trouble procedure (NTP) is a list of steps designed to accomplish a specific procedure. Follow the steps until the procedure is complete. If you need more detailed instructions, refer to the detail-level procedure (DLP) specified in the procedure steps. Throughout this guide, NTPs are referred as "procedures" and DLPs as "tasks." Every reference to a procedure includes its NTP number, and every reference to a task includes its DLP number.

The DLP (task) supplies additional task details to support the NTP. The DLP lists numbered steps that lead you through completion of a task. Some steps require that equipment indications be checked for verification. When a proper response is not obtained, a trouble clearing reference is provided.

Step 4 Disable all other Ethernet devices (such as a dial-up adapter) on the workstation that runs CTC. For instructions, contact the Cisco TAC.

Note If you have multiple IP addresses on your workstation, you should remove them; you cannot run ONS 15600 SDH Software R9.2.1.x if multiple IP addresses are configured.

Step 5 If you have multiple ONS 15600 SDH nodes configured in the same IP subnet, ensure that only one is connected to a router. Otherwise, the remaining nodes might be unreachable. Refer to the Cisco ONS 15600 Reference Manual for LAN-connection suggestions.

Step 6 Verify that TSC cards are installed in Slots 5 and 10, and that the TSC in Slot 10 is active.

Step 7 If the TSC in Slot 5 is active, select the slot, and right-click to display a shortcut menu. Click the Soft reset Card button. The reset takes a few minutes, and resets the TSC card in Slot 10 as the active TSC.

Note To successfully run the CTC on workstations running Windows Vista or Windows 7, upgrade the CTC Software to R9.0 or later. Releases prior to R9.0 are not supported on Windows Vista or Windows 7.

Note Use the latest patch or service pack released by the OS vendor. Check with the vendor for the latest patch or service pack.

•UNIX workstation with Solaris Version 9 or 10 on an UltraSPARC-III or faster processor, with a minimum of 1 GB RAM and a minimum of 250 MB of available hard drive space.

Step 2 Ensure that your web browser software is one of the following:

•Netscape Navigator 7.x or higher on Windows

•Internet Explorer 6.x or higher on Windows

•Mozilla 1.7 or higher on Solaris

Step 3 Verify that the Java Version installed on your computer is Java Runtime Environment (JRE) 1.5.0; higher versions of Java will not run CTC for the ONS 15600 SDH R8.0.

Note To check your JRE version, type the node IP address in the Address field of your browser and then look at the JRE version listed under the Java Environment label. If you need to install JRE 1.6.0, go to www.java.com and follow the instructions on the site to download and install the JRE 1.6.0 package.

Note Multiplex Section-Shared Protection Ring (MS-SPRing nodes only) The database must be backed up prior to locking the MS-SPRing. To restore a software database, a backup file of that database must be available.

Step 2 In CTC node view, click the Maintenance tab and then click the Software button.

Step 3 Verify that the correct working and protect versions of the software are installed.

Step 4 (Optional) Cisco recommends that you manually log critical information by either writing it down or printing screens where applicable. Use Table 1 to determine the information you should log. Complete the table (or your own version) for every node in the network.

Note The TSC card in Slot 10 must be the active TSC card for an upgrade.

Slot 5 or Slot 10 (circle one). If the TSC in Slot 5 shows active status, the slot and right-click to display a shortcut menu. Click Soft reset Card. The reset takes a few minutes, and resets the TSC card in Slot 10 as the active TSC.

SSXC preferred copy

Slot 6/7 or Slot 8/9 (circle one)

Network information; do a print screen from the Provisioning tab in network view.

Current configuration: SNCP, linear, etc. Do print screens as needed.

List all protection groups in the system; do a print screen from the Protection Group window.

List alarms; do a print screen from the Alarm window.

List circuits; do a print screen from the Circuit window.

Step 5 In CTC node view, click the Maintenance tab and then click the Database button.

Step 6 Click the Backup button.

Step 7 In the Database Backup dialog box, click the Browse button, then navigate to a local PC directory or network directory and type a database name (such as database 10101882010107.db) in the Select file for saving backupfield.

Step 8 In the Database Backup dialog box, click the OK button. If you are overwriting an existing file, clickYes in the confirmation dialog box.

Step 9 In the Database Backup dialog box, check the Alarm History and the Performance check boxes in order to choose these database items in addition to provisioning information.

Note The Provisioning selection in the Database Backup dialog box is a default component of the backup file, and this selection is dimmed.

Step 10 Save the database on the workstation's hard drive or on network storage. In the Database Backup dialog box, click OK.

Step 11 A message indicates the status of the backup. When the backup is complete, click the OK button to close the message dialog box.

Caution After you have accepted the Software
R9.2.1.x build and both releases are present in the working and protect fields on CTC, you cannot revert to Software R8.0 without downloading Software 8.0 or installing the Software R8.0 PKG file and restoring the Software R8.0 database.

Step 11 Repeat Steps 6 through 10 for all nodes in the network that need to be upgraded. Allow each node to finish. Wait until all alarms have been cleared for 10 minutes before activating the next node.

Step 13 (Optional) Use this step only if you wish to ensure that a software revert to the previous software release is no longer possible. Complete the "DLP-U575 Download the ONS 15600 SDH Software" task again for all nodes, or groups of nodes you are upgrading.

Step 15 As needed, upgrade any spare TSC cards by installing the spare in the standby slot.

Caution When you insert a spare TSC card in the standby slot, a software mismatch alarm is raised. The working software on the active TSC card is then copied to the standby TSC, causing the standby TSC card to reset. When the standby TSC card reset completes, the standby TSC is running the same software version as the active TSC card.

Note You can activate only one node at a time; however, you can begin activation of the next node as soon as the TSC cards for the current node have rebooted successfully (wait 5 minutes from the time the SYSBOOT alarm is raised).

(MS-SPRing nodes only) The database must be backed up prior to locking the ring.

Required/As Needed

Required for MS-SPRing only

Onsite/Remote

Onsite or remote (but in the presence of the workstation)

Security Level

Maintenance and above

Note During activation, MS-SPRing spans are not protected. You must leave the MS-SPRing in the lockout state until you have finished activating all nodes in the ring, but you must be sure to remove the lockout after you have finished activating.

Note To prevent ring or span switching, perform the lockout on both the east and west spans of each node.

Step 4 For each of the MS-SPRing trunk (span) cards (STM-16, STM-64), perform the following steps:

a. Next to the trunk card row, click the East Switch column to show the drop-down list.

b. From the menu options, choose Lockout Protect.

c. Click Apply.

d. In the same row, click the West Switch column to show the drop-down list.

e. From the menu options, choose Lockout Protect.

f. Click Apply.

Note Ignore any Default K alarms that occur on the protect STS time slots during this lockout period.

Note Certain Multiservice Switching Platform (MSSP) related alarms might be raised following activation of the first node in the ring. The following alarms, if raised, are normal and should not cause concern. They clear upon completion of the upgrade, after all nodes have been activated.

Note The download task does not affect traffic because the active software continues to run at the primary RAM location; therefore, you can download the software at any time.

Step 1 If CTC is not already running, start CTC.

Step 2 In node view, click the Alarms tab.

Step 3 Verify that the alarm filter is not on. Click the Filter tool at the lower-left of the window.

Step 4 The Alarm Filter dialog box appears. Click the check boxes to deselect any selections in the Show Severity section of the General tab.

Step 5 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding critical alarms before proceeding. If necessary, refer to the Cisco ONS 15600 SDH Troubleshooting Guide.

Step 6 If the TSC card in Slot 5 is the active TSC, you will need to perform a soft reset to make the TSC in Slot 10 the active TSC. Select Slot 5, then right-click to display a shortcut menu. Click the Soft reset Card button. The reset takes a few minutes, and resets the TSC card in Slot 10 as the active TSC.

Note The TSC card can take several minutes to reboot.

Step 7 If not in node view, open the View menu and choose Go to Home View to go to the node view.

1If you have downloaded the software into the protect side of the TSC card and want to activate (or revert) it at a later time, the Activate (or Revert) buttons may be grayed out. This occurs when the Cisco ONS 15600 node detects the software in the protect side of the TSC as invalid. In order to activate (or revert) the software, download the software to the TSC card once again.

Note Although the software activation task is not service affecting, Cisco recommends that you activate the new load during a maintenance window.

Caution Do not perform maintenance or provisioning activities during the activation task.

Note For MS-SPRing nodes only, a non-service affecting APS-CHAN-FAILURE alarm is raised on each of the nodes joined to an activating node in the ring during activation. After the activation completes for that node, the alarms will clear.

Note Cisco recommends that the first node you activate be a LAN-connected node. This ensures that the new CTC JAR files will download to your workstation as quickly as possible.

Step 1 If CTC is not already running, use the IP address of the ONS 15600 SDH node to start CTC.

Step 2 In node view, click the Maintenance tab and then click the Software button.

Step 3 Verify that the version in the Protect Version column is Software R9.2.1.x.

Step 4 Click the Activate button. The Activate dialog box appears with a warning message indicating that you should perform a database backup before proceeding.

Step 5 Make sure the TSC card in Slot 10 is active, if not, perform a soft reset on TSC card in Slot 5. Select Slot 5, then right-click to display a shortcut menu. Click the Soft reset Card button. The reset takes a few minutes, and resets the TSC card in Slot 10 as the active TSC.

–A Wait message, generated when the standby TSC card containing the upgrade software reboots. It signals to the active TSC card that it is ready to take over. When the active TSC receives this signal, it resets itself, and the standby TSC in Slot 5 takes over and transitions to the active software version. The pre-upgrade version of the TSC card is now the standby TSC.

Step 7 Click OK when the Rebooting dialog box appears indicating that the software is successfully activated. The node reboot could take up to four minutes.

Step 8 A Connection Lost dialog box appears, indicating that the connection between the node and CTC is not currently active. Click OK in the Connection Lost dialog box.

Note CTC loses connection to the node while the node reboots and displays the network view. The node might take several minutes to reboot. A Minor loss of connection between the node and CTC alarm appears in the History tab. Next, a CTC and node incompatible alarm is raised. Wait for node reactivation.

Step 9 In CTC, choose Exit from the File menu to exit, or proceed to Step 9 to delete the CTC cache.

Note You must ensure that CTC is closed before clicking the Delete CTC Cache button. CTC behavior is unreliable if the button is clicked while the software is still running.

Note It might also be necessary to delete cached files from your browser's directory, or from the temp directory on your MS Windows workstation. If you have trouble reconnecting to CTC, complete the "DLP-U577 Delete Cached JAR Files" task.

Step 11 Close your browser.

Step 12 Install JRE 5.0, in order to run CTC with ONS 15600 SDH Software R9.2.1.x and (optionally) run the Cache Loader pre-caching utility:

Note Cisco recommends you run the optional Cache Loader pre-caching utility during this step, prior to activating the node. This ensures that the new CTC JAR files download to your workstation as quickly as possible.

Step 2 If the Java Plug-in Security Warning dialog box appears, choose one of the following options:

•Grant This Session—Installs the public-key certificate to your PC only for the current session. After the session is ended, the certificate is deleted. This dialog box will display the next time you log into the ONS 15600 SDH.

•Deny—Denies permission to install the certificate. If you choose this option, you cannot log into the ONS 15600 SDH.

•Grant always—Installs the public-key certificate and does not delete it after the session is over. Cisco recommends this option.

•View Certificate—Allows you to view the public-key security certificate.

Step 2 In node view, click the Maintenance tab and then click the Software button.

Step 3 Click the Accept button. The acceptance process will take approximately 2 to 5 minutes.

Note You can reject the new software load by clicking the Cancel button.

Note If the Cancel button is not active, the standby TSC has not finished acquiring the active timing reference. The acquire process can take approximately 10 to 15 minutes. When the acquire process completes, the Cancel button becomes active.

Step 4 On the Maintenance tab, click the Software button and verify the version:

a. Click the Info button.

b. In the Current Software Info dialog box, verify that the TSC B Working field shows the correct version. The TSC B Protect field should show the previous version.

c. If the TSC B Working and TSC B Protectfields show none, click OK and click the Info button again after several minutes. Repeat until the TSC B software versions appear.

Step 3 For each of the MS-SPRing trunk (span) cards (STM-16 or STM-64), perform the following steps:

a. Next to the trunk card row, click the West Switch column to show the drop-down list.

b. Choose Clear from the list.

c. Click the Apply button to activate the command.

Note When removing a lockout, be sure to apply your changes each time you choose the Clear option. If you try to select Clear for more than one lockout at a time, you risk traffic loss on the first ring switch.

d. In the same row, click the East Switch column to show the drop-down list.

e. Choose Clear from the list.

f. Click Apply to activate the command.

Step 4 Repeat this task as many times as necessary to remove all MS-SPRing span lockouts on the upgrade nodes.

Step 5 Return to your originating procedure (NTP).

DLP-U581 Set the Date and Time

Purpose

This task resets the date and time at each node.

Tools/Equipment

PC or UNIX workstation

Prerequisite Procedures

None

Required/As Needed

As needed

Onsite/Remote

Onsite or remote (but in the presence of the workstation)

Security Level

Superuser

Note If you are not using Simple Network Time Protocol (SNTP), the upgrade procedure can cause the date and time setting to change. If you are using SNTP, you do not need to perform this task.

Step 1 Start CTC.

Step 2 In node view, click the Provisioning tab, and click the General button.

Note If the version in both the Working Version and the Protect Version fields in CTC is Software R9.2.1.x, as you cannot revert to a previous software version.

Note The tasks to downgrade to a previous load are not a part of the upgrade. They are provided here as a convenience to those wishing to restore an earlier software load after an upgrade. If you have performed all necessary procedures up to this point, you have finished the software upgrade.

Note A system-wide soft reset occurs after the Software 8.0 database is restored. All line (I/O) and matrix cards automatically soft reset. Existing traffic can be affected, depending on the circuit provisioning map.

Step 1 Start CTC using the IP address for an ONS 15600 SDH node that has been upgraded from Software R8.0 to Software R9.2.1.x, and access the node view. For detailed instructions, refer to the Cisco ONS 15600 SDH Procedure Guide.

Note To perform a downgrade from SoftwareR9.2.1.x, Software R8.0 must have been working at the time you activated to Software R9.2.1.x on that node. Also, a supported reversion restores the node configuration at the time of the previous activation. Thus, any configuration changes made after activation will be lost when you revert the software.

Note To restore the database for a reverted software version, select the database for the reverted version.

Step 7 In the Open dialog box, navigate to a local PC directory or network directory where the backup database file is stored and click the Open button, then click OK. The Database Restore dialog box appears.

Note If alarms and performance were backed up, click the Alarms and Performance check boxes in the Database Restore dialog box.

Step 8 Click Yes in the confirmation dialog box.

Step 9 Click the History tab to view the conditions:

1. Downloading (approximately 10 to 20 minutes)

2. System Upgrade in progress (approximately 3 to 5 minutes)

Step 10 Click the Maintenance tab and then click the Software button. The Download Status column shows the percentage of the completion of the upgrade progress.

When the Download Status column is empty, Software R8.0 has finished loading.

Step 11 Log out of CTC.

Step 12 Restart CTC with the Software R8.0 version, using the same IP address used in Step 1.

Note This procedure assumes you are upgrading using Release 6.x TL1 syntax. TL1 commands issued prior to software activation to Software R9.2.1.x will vary in syntax depending on the release you are actually upgrading from. To ensure that your syntax for each command is correct, use the TL1 syntax supplied in the Cisco ONS SDH TL1 Command Guide for your particular release when issuing the following commands:

•ACT-USER

•APPLY

•CANC

•COPY-RFILE

•REPT EVT FXFR

•OPR-PROTNSW-<STMN_TYPE>

•RTRV-COND-ALL

•RTRV-ALM-ALL

Note To perform an R9.2.1.x software download using TL1, you must first have an FTP server or a terminal emulation program like HyperTerminal running on your workstation. In the following conditions, the download (COPY-RFILE) command is different when downloading software to a gateway network element (GNE) or an end network element (ENE):

•- FTP is being used.

•- The server is set up with a login and password of FTPUSER1 and FTPUSERPASSWORD1.

The ":2361" after the FTP server IP address 10.111.11.1 denotes port 2361 on the server.

The software PKG file in the preceding example is located in the home directory of the FTP server. If the software PKG file is not in the home directory on the FTP server, insert the directory path where the software package resides between the last IP address and the PKG file in the command line. An example is shown here.

COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL,

SRC="ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1:2361@90.90.90.90/CISCO/SOFTWARE/15600-0xxx-x
xxx-xxxx.pkg";To use

Step 1 To use TL1 commands, set up an FTP session or use HyperTerminal or a similar terminal emulation package to establish a session with the ONS 15600 SDH node.

Step 2 Type the IP address for the node, using port 3083 or 2361.

The terminal emulation interface will display a Warning message and a command prompt (usually >). You issue TL1 commands at this prompt.

Step 3 Type the ACT-USER (Activate User) command in the TL1 request window to open a TL1 session:

ACT-USER:[<TID>]:<uid>:<CTAG>[::<pid>];

where:

•<TID> is the target identifier (optional).

•<UID> is the profile username (required).

•<CTAG> is the correlation tag that correlates command and response messages (optional).

•<PID> is the password identifier (required).

For example, in the TL1 command:

ACT-USER::CISCO99:100::PASSWORD;

ACT-USER is the activation command, CISCO99 is the user ID, 100 is the correlation tag (used to correlate commands to command responses), and PASSWORD is the password associated with the user ID.

A response message containing the CTAG that you specified indicates the completion status of the command.

Step 4 Select the IP address for the node, using port 3083 or 2361.

Step 5 Type the COPY-RFILE command in the TL1 window or, if using HyperTerminal, click Transfer > Receive File, and click in the associated dialog box to select a file to receive. The COPY-RFILEcommand downloads a new software package from the location specified by the FTP URL into the inactive Flash partition residing on either of the TSC cards.

Step 7 Look for the REPT EVT FXFR message in the TL1 window. REPT EVT FXFR is an autonomous message used to report the start, completion, and completed percentage status of the software download. REPT EVT FXFR also reports any failure during the software upgrade, including invalid package, invalid path, invalid user ID/password, and loss of network connection.

•<AID> identifies the facility in the node to which the switch request is directed.

•<CTAG> is the correlation tag that correlates command and response messages.

•<SC> is the switch command that is to be initiated on the paths.

•<SWITCHTYPE> is the MS-SPRing switch type.

•<DIRN> is the direction of transmission in which switching is to be made and is relative to the SONET line or path identified by the AID. The default value is RCV and should be changed to BTH.

Note Some nodes might have more than one MS-SPRing. If this is the case, all MS-SPRing spans on all nodes being upgraded need to be locked out. Nodes that are not being upgraded do not need to have the MS-SPRing spans locked out. You must be aware of each span that is part of a MS-SPRing to make sure all necessary spans are locked out.

Note MS-SPRing lockouts must remain in place until the upgrade is complete for all nodes.

Note Ignore any Default K alarms that occur on the protect STS time slots during the lockout.

Note Certain MS-SPRing-related alarms might be raised following activation of the first node in the ring. The alarms, if raised, are normal, and should not cause concern. They clear upon completion of the upgrade, after all nodes have been activated.

Step 11 Verify that all necessary MS-SPRing spans on each node being upgraded have been locked out using the following command:

RTRV-PROTNSW-<STMN_TYPE>:[<TID>]:<AID>:<CTAG>[::::];

<AID> must not be null.

Step 12 Verify that there are no outstanding alarms or conditions on each node using the following commands:

RTRV-COND-ALL:[<TID>]:[<AID>]:<CTAG>::[<TYPEREQ>][,,,];

where:

<TYPEREQ> is the type of condition to be retrieved. A null value is equivalent to ALL.

•<AID> identifies the facility in the node to which the switch request is directed.

•<CTAG> is the correlation tag that correlates command and response messages.

•<NTFCNCDE> is a notification code. A null value is equivalent to ALL.

•<CONDITION> is the type of alarm condition. A null value is equivalent to ALL.

•<SRVEFF> is the effect on service caused by the alarm condition. A null value is equivalent to ALL.

Resolve all issues before proceeding.

Note You can only activate only one node at a time; however, in a parallel upgrade you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully. If you wish to perform a parallel upgrade remotely, wait five minutes for the controller cards to complete the reboot.

Step 13 Starting at the node farthest from the GNE, type the APPLY command to activate the system software.

APPLY:[<TID>]::<CTAG>[::<MEM_SW_TYPE>];

where:

•<TID> is the target identifier.

•<CTAG> is the correlation tag that correlates command and response messages.

If the command is successful, the appropriate flash is selected and the TSC card reboots.

The following occurs:

•When the standby TSC card containing the upgrade software reboots (this can take up to 5 minutes).

•When the reboot is completed, the standby TSC is now running the Software R9.2.1.x upgrade. The active TSC in Slot 10 is running Software R8.0.

•The standby TSC acquires the active timing reference, which may take up to 15 minutes to accomplish. Then the active TSC in Slot 10 reboots, and the card in Slot 5 becomes active, using Software R9.2.1.x as the working copy. When the TSC card in Slot 10 resets, it is in standby mode, and is running the Software R8.0 version.

•All remaining cards in the shelf reset simultaneously, raising a SYSBOOT alarm while activation in progress. When all cards have reset, this alarm clears.

•When the common control cards have finished resetting and all alarms are cleared, you can proceed to the next step.

After the common control cards finish resetting and all associated alarms clear, you can safely proceed to the next step. (If you are upgrading remotely and cannot see the nodes, wait for 5 minutes for the process to complete, then check to ensure that related alarms have cleared before proceeding.)

Step 14 Perform Step 13 for each node that will be upgraded, moving from the furthest node from the GNE toward the GNE itself, which should be activated last.

Note You might have to log in ( and Step 3) to each node again to activate the software (Step 13).

Step 15 After all nodes have been activated, log in using CTC or Telnet ( and Step 3) and verify there are no outstanding alarms.

Step 16 Remove all MS-SPRing lockouts using the following TL1 command:

RLS-PROTNSW-<STMN_TYPE>:[<TID>]:<AID>::[::<DIRECTION>];

where:

•<AID> identifies the facility in the node to which the switch request is directed.

•<CTAG> is the correlation tag that correlates command and response messages (optional).

•<DIRN> is the direction of transmission (transmit or receive). The possible values are:

Where to Find Safety and Warning Information

For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.

Cisco Optical Networking Product Documentation CD-ROM

Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)