Before You Begin

Before beginning, write down the following information about your site; the data will be useful during and after the upgrade: date, street address, site phone number, and dialup number.

Caution Read all procedures before you begin the upgrade.

Caution This upgrade is supported only for Software R7.x upgrading to Software R8.0.

Note Software R8.0 supports parallel upgrades for multiple nodes in a network. In a parallel upgrade you can still only activate one node at a time; however, you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully (wait five minutes from the time the SYSBOOT alarm is raised).

Caution When managing end-to-end circuits participating in an ML-series resilient packet ring (RPR) across multiple nodes involved in a parallel upgrade, all nodes participating in these circuits must have completed the activation before the end-to-end traffic will resume.

Document Procedures

Procedures in this document are to be performed in consecutive order unless otherwise noted. In general, you are not done with a procedure until you have completed it for each node you are upgrading, and you are not done with the upgrade until you have completed each procedure that applies to your network. If you are new to upgrading the ONS 15310-MA, you might want to check off as you complete each procedure on your printed copy of this document.

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 to as "procedures" and DLPs are termed "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 the proper response is not obtained, a trouble clearing reference is provided.

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

Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15310-MA Procedure Guide. When you are logged in, continue with Step 2.

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

Step 3 Click the Backup button. A Database Backup dialog box appears.

Step 4 In the Database Backup dialog box, click the Browse button, then navigate to a local PC directory or network directory and type or select a database name using the IP address of the node to upgrade (such as 10101882010107.db).

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

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

Step 7 Repeat Steps 1 through 6 for each node in the network.

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

Note A traffic interruption of less than 50 ms on each circuit is possible during the activation task, with Ethernet traffic disruption possibly lasting up to several minutes on each circuit. Do not perform maintenance or provisioning activities during the activation task.

Caution When managing end-to-end circuits participating in an ML-Series resilient packet ring (RPR) across multiple nodes involved in a parallel upgrade, all nodes participating in these circuits must have completed the activation before the end-to-end traffic will resume.

Note Activate one node at a time. You can begin activation of the next node as soon as the controller cards for the current node have rebooted (wait five minutes from the time the SYSBOOT alarm is raised).

Note The CTX2500 card has two flash RAMs. An upgrade downloads the software to the backup RAM on the CTX2500 card. 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, using the IP address of the ONS 15310-MA node.

Step 2 In CTC node view, click the Alarms tab.

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

Step 4 The Alarm Filter dialog box appears. Click 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 Troubleshooting Guide.

Note During the software download process, the SWFTDWN alarm indicates that the software download is incomplete.

Caution Activation can be service affecting, so Cisco recommends that you activate the new load during a maintenance window. ML-Series Ethernet traffic can remain down from the time the CTX2500 cards switch to the time all Ethernet cards have finished resetting (3 to 8 minutes). Time-division multiplexing (TDM) traffic and CE-Series Ethernet traffic should remain errorless.

Note Cisco recommends you run the optional Cache Loader pre-caching utility in Step 13 of the activation task. If you do not plan to run the pre-caching utility, Cisco recommends that the first node you activate be a LAN-connected node. This ensures that the new CTC JAR files download to your workstation as quickly as possible.

Step 1 If CTC is not already running, start CTC, using the IP address of the ONS 15310-MA node.

Step 2 Record the IP address of the node. The IP address is on the upper left corner of the CTC window.

Step 3 Verify that the alarm filter is not on. Click to deselect any selections in the Show Severity section of the General tab.

Step 4 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding critical alarms before proceeding.

Step 5 Click the Maintenance tab and then clickthe Software button.

Step 6 Verify that the version in theProtect Version column is Software R8.0.

Step 7 Click the Activate button. Click Yes to proceed with the activation.

Step 8 Click Yes to proceed with the activation. An Activation Successful message indicates that the software is successfully activated. Click OK in the message dialog box.

When you click Yes the activation begins, and the software upgrade reboot occurs as follows:

•Each card in the node resets, beginning with the standby CTX2500 card. When the standby CTX2500 finishes rebooting, the two CTX2500 cards switch and CTC temporarily loses connection to the node. (The connection is restored after the switch is established, within 4 minutes of the connection loss.)

•Next, the now standby (previously active) CTX2500 reboots, along with the electrical and Ethernet cards, which reboot from left to right.

•The whole process can take up to 10 minutes. This process is errorless for TDM and CE-series traffic. ML-Series cards are expected to incur a traffic hit of 3 to 8 minutes.

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

Note During a software upgrade, a reset alarm is raised on all the cards. When upgrading from release 6.0.x, 6.1.x, 6.2.x, 7.0, 7.2, 7.2.x to 8.x, a MANRESET alarm is raised on Standby TCC cards and an AUTORESET alarm in all the other cards. However, from release 8.0, the MANRESET alarm is not raised and the AUTORESET alarm is raised on all the cards.

Step 9 In CTC, choose File > Exit.

Note Steps 10 through 14 are only necessary after upgrading the first node in a network because cached files only need to be removed from your workstation once. For the remaining nodes, you will still be disconnected and removed to the network view during the node reboot, but after the reboot is complete, CTC will restore connectivity to the node.

Note You must ensure that CTC is closed before clicking the Delete CTC Cache button. CTC behavior will be 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 Microsoft Windows workstation. If you have trouble reconnecting to CTC, complete the "DLP-U347 Delete Cached JAR Files" task.

Step 12 Close your browser and then reopen it.

Step 13 (Optional) Run the Cache Loader pre-caching utility, which can improve your speed logging back into CTC after an upgrade. Perform the following steps to run the Cache Loader.

a. Load the Software R8.0 CD into your CD-ROM drive. If the directory of the CD does not open automatically, open it.

g. When the utility finishes, click OK, and then in the wizard, click Finish.

Step 14 Reconnect to CTC using the IP address from Step 2. The new CTC applet for Software R8.0 uploads. During this logon, enter your Superuser user ID and password.

Step 15 Return to your originating procedure (NTP).

Note When you revert the software to an earlier version, a reset alarm is raised on all the cards. When you revert from release 8.x or later to 6.0.x, 6.1.x, 6.2.x, 7.0, 7.2, or to 7.2.x, an AUTORESET alarm is raised on the Standby TCC cards and a MANRESET alarm in all other cards. However, in releases earlier to 8.0, the AUTORESET alarm is not raised and the MANRESET alarm is raised on all the cards.

DLP-U347 Delete Cached JAR Files

Purpose

This task manually deletes cached Java JAR files from your browser and hard drive. When you upgrade or revert to a different CTC software load, you must reload CTC to your browser. Before you can reload CTC, you must ensure that previously cached files are cleared from your browser and hard drive.

NTP-U233 Install Public-Key Security Certificate

This procedure installs the ITU Recommendation X.509 public-key security certificate. The public-key certificate is required to run Software R4.1 or later.

Tools/Equipment

None

Prerequisite Procedures

This procedure is performed when logging into CTC. You cannot perform it at any other time.

Required/As Needed

This procedure is required to run ONS 15310-MA software.

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Step 1 Log into CTC.

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 15310-MA.

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

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

After you complete the security certificate dialog boxes, the web browser displays information about your Java and system environments. If this is the first login, a CTC downloading message displays while CTC files are downloaded to your computer. The first time you connect to an ONS 15310-MA, this process can take several minutes. After the download, the CTC Login dialog box displays.

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

Note Before you upgraded to Software R8.0, you should have backed up the existing database at all nodes in the network (this is part of the "NTP-U231 Back Up the ONS 15310-MA Software Database" procedure). Cisco recommends that you record or export all critical information to your hard drive. If you need to revert to the backup database, use the following tasks, in order.

Step 1 Log into the node. For detailed instructions, refer to the Cisco ONS 15310-MA Procedure Guide. If you are already logged in, continue with Step 2.

Note To perform a supported (non-service-affecting) revert from Software R8.0, the release you want to revert to must have been working at the time you activated to Software R8.0 on that node. Also, 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. The exception to this is when you have downloaded Software R8.0 a second time, to ensure that no actual revert to a previous load can take place. In this latter case, the revert will occur, but will not be traffic affecting and will not change you database.

Step 1 If CTC is not already running, start CTC, using the IP address of the ONS 15310-MA node.

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

Step 3 Verify that the protect software is the release you upgraded from.

Step 4 Click the Revert button to activate the protect software and restores the database from the previous load. A dialog box asks you to confirm the choice.

Step 5 Click Yes. This begins the revert. CTC drops the connection to the node and takes you to the network view, displaying a confirmation dialog box.

Step 6 Click OK and wait until the software revert finishes before continuing.

Note The system reboot might take up to 10 minutes to complete.

Step 7 Wait one minute before reverting another node.

Step 8 After reverting all of the nodes in the network, close and restart your Netscape or Internet Explorer browser and log back into the last node that was reverted. This uploads the appropriate CTC applet to your workstation.

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

Step 9 Return to your originating procedure (NTP).

DLP-U350 Manually Restore the Database

Purpose

This task manually restores the database. If you were unable to perform a revert successfully and need to restore the database, perform this task.

Note This procedure assumes you are upgrading using Release 6.x TL1 syntax. TL1 commands issued prior to software activation to Software R8.0.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 SONET TL1 Command Guide for your particular release when issuing the following commands:

•ACT-USER

•COPY-RFILE

•REPT EVT FXFR

•OPR-PROTNSW-<OCN_TYPE>

•RTRV-COND-ALL

•RTRV-ALM-ALL

Note To perform an R8.0 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 ":21" after the FTP server IP address 10.111.11.1 denotes port 21 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:

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 15310-MA 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 will 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 optical support system Operations Support System (OSS) profile user ID (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-RFILEcommand in the TL1 window or, if using HyperTerminal, Select Transfer > Receive File, and use 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 TCC2/TCC2P 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 userid/password, and loss of network connection.

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

•<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 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 11 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.

•<MEM_SW_TYPE> indicates a memory switch action during the software upgrade. MEM_SW_TYPE is ACT for activate.

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

•Any cards in Y-cable protection groups boot next, one at a time (protect card first), in order of first creation (refer to the CTC protection group list for order of first creation).

•Next, the traffic cards, G-Series Ethernet cards, CE-Series Ethernet cards, and ML-Series Ethernet cards boot consecutively, in ascending order of slot number, first standby, then working, for each card pair.

•A system reboot (SYSBOOT) alarm is raised while activation is in progress (following the CTX2500 and cross connect card resets). When all cards have reset, this alarm clears. The complete activation process can take up to 30 minutes, depending on how many cards are installed.

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 12 Perform Step 11 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 Note You might have to log in (Step 1 and Step 3) to each node again to activate the software (Step 11).

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

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 Documentationas 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)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.