Guest

Cisco ONS 15454 Series Multiservice Provisioning Platforms

Upgrading Cisco ONS 15454 Release 2.2.x to 2.2.2 Using the TCC Card

 Feedback

Table Of Contents

Upgrading Cisco ONS 15454 Release 2.2.x to 2.2.2 Using the TCC Card

Introduction

Upgrade Requirements

CTC Workstation Requirements

DNS & WINS Setting

IP Address Caveat

LAN Caveat

Valid Craft Port

Memory Chip Verification

Telnet Session

Added Superuser

AIP Verification

Back Up the Database

Upgrade the Software

Upload

Before You Activate

Activate the New Load

BLSR Nodes

Date Setting

Spare TCC Units

XC to XCVT Upgrade

Restore the Previous Software and Database

Manually Restore the Software Load

Manually Restore the Database


Upgrading Cisco ONS 15454 Release 2.2.x to 2.2.2 Using the TCC Card


Introduction

This document explains how to upgrade Cisco ONS 15454's Cisco Transport Controller (CTC) software from Release 2.2.x to Release 2.2.2 using the Timing, Communications, and Control (TCC) card.

Before beginning, write down the following information about your site; the data will be useful during and after the upgrade: Date, Node Name, Node Location, Street Address, Site Phone Number, Node IP Address, Subnet Mask, Dial Up Number, and Node ID.


Caution Read each procedure before you begin the upgrade.

Upgrade Requirements

This section contains critical information that you must read before the upgrade process.

Read the Release Notes for Cisco ONS 15454 Release 2.2.2 before you begin this upgrade procedure.


Caution Use this document with the TCC card only. To upgrade using the TCC+ card, see Upgrading Cisco ONS 15454 Release 2.2.x to 2.2.2 Using the TCC+ Card.


Note Upgrading to a new CTC release can create limitations to your ability to use the Cisco Transport Manager (CTM). If you are using CTM, before you choose to upgrade to a new CTC release you should check the latest CTM Release Notes for any possible compatibility issues. The CTM Release Notes can be found at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/optnet/ctm/index.htm


CTC Workstation Requirements

Before upgrading the workstation to run CTC Release 2.2.2, verify all hardware and software requirements.

A Windows or Unix workstation:

IBM-compatible PC with a 486 or higher processor, CD ROM drive, and 128 MB RAM running Windows 95, Windows 98, Windows 2000, or Windows NT

UNIX workstation running Solaris

Direct connection to the ONS 15454 using 10baseT Ethernet Network Interface Card (NIC) and Ethernet Cable (use the CAT 5 10baseT Patch cable to connect to the TCC)

Browser software (select one):

Netscape Navigator 4.08 or higher (Netscape Navigator is included on the ONS 15454 software CD shipped with the node.)

Netscape Communicator 4.61 or higher

Internet Explorer 4.0 Service Pack 2 or higher

Java Policy File and Java Runtime Environment file (included on the ONS 15454 software CD)

DNS & WINS Setting

When setting up TCP/IP Network properties for a workstation that will run CTC Release 2.0, ensure that DNS and WINS resolution are disabled. WINS resolution is rarely used, but DNS is commonly used in corporate networks. When DNS is enabled it causes CTC to hang and requires a TCC side switch at every network node to correct the lockup.

IP Address Caveat

Disable all other Ethernet devices (such as a dial-up adapter) on the workstation that runs CTC.

If you have multiple IP addresses on your workstation, you must remove them; you cannot install CTC Release 2.2.2 if multiple IP addresses are running.

LAN Caveat

If you have multiple ONS 15454 nodes configured in the same IP subnet, only one can be connected to a router. Otherwise, the remaining nodes might be unreachable. Refer to the Cisco ONS 15454 User Documentation, Release 2.2.1 for LAN-connection suggestions.

Valid Craft Port

The front-panel Ethernet interface is changed in Release 2.0.

The permanent wire-wrap LAN connection on the backplane will communicate with the node if either TCC (A or B) is active or if the front-panel TCC connection is used.

When using Release 2.2.0 or greater you can connect through either of the TCC RJ-45 ports regardless of which one is active.


Memory Chip Verification

Hyundai DRAM chips could potentially cause failure of software downloads to the TCC. This failure is related to a specific DRAM chip that was introduced in manufacturing between 9/29/1999 and 11/1/1999. The affected TCC modules are exclusive to the serial number ranges of 31550 and 45500 and FAA04280001 through FAA0430A4BA. There are other cards within this range of serial numbers that do not contain the specified component and are not affected by this issue. Any TCCs in the specified serial number ranges should be inspected for the failing component using the following procedure.


Note Do not screen in-service nodes; this procedure is potentially traffic-affecting. For all in-service nodes, screen for Hyundai DRAM during a maintenance window.



Step 1 From the CTC node view, right-click the standby TCC card and choose Reset.

Step 2 While the standby TCC card reboots, physically remove it from the shelf.

Step 3 Turn the TCC card over.

Step 4 Look in the lower left-hand quarter of the card and locate the U30 and U35 memory chips. Look for HYxxxxxxxxx or NEC Japan.

Step 5 If you have the HY type chips, replace the TCC with a TCC that does not have the HYxxxxxxxxx chips. Allow the card to boot up and come back online.

Step 6 From the CTC node view, right-click the active TCC card and choose Reset.

Step 7 While the active TCC card reboots, physically remove the card from the shelf.

Step 8 Repeat Steps 3 through 5 for the active TCC.

Step 9 If you encounter any of these defective cards, call the Technical Assistance Center (TAC) at 1 877 323-7368 and obtain an RMA number for each.


Telnet Session

Make sure all active telnet sessions to any node in the network are closed.

Added Superuser

A new superuser, CISCO15, was added to Release 2.2.0.

You can currently use the cerent454 superuser name, but this username will be phased out in a future release.

AIP Verification

Verify that all AIP boards on each node are revision 003A, A0, or B0. All AIP boards with revision 005x must be swapped. Repeat for every node.

Back Up the Database

Before upgrading from Release 2.2.x to Release 2.2.2 software, you must back up the current database for all nodes in the network.


Step 1 Log into CTC.

Step 2 From the node view, click the Maintenance > Database tabs.

Step 3 Click Backup.

Step 4 Save the database on the workstation's hard drive or on network storage. Use an appropriate file name with the file extension .db (for example, myDatabase.db).

Step 5 Click Save. The File Received dialog box appears.

Step 6 Click OK.


Cisco recommends that you manually log critical information by either writing it down or printing screens where applicable. This step is optional after you have backed up the database. Use the following table to determine the information you should log; complete the table (or your own version) for every node in the network.

Item
Record data here (if applicable)

IP address of the node

 

Node name

 

Timing settings

 

DCC connections; list all optical ports that have DCCs activated

 

User IDs (List all, including at least one super user)

 

Inventory; do a print screen from the inventory window

 

Active TCC

Slot 7 or Slot 11 (circle one)

Active XC

Slot 8 or Slot 10 (circle one)

Network information; record all the information from the Provisioning tab in the network view.

 

Current configuration: BLSR, linear, etc.

 

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

 

Upgrade the Software

After backing up the database and logging all of the required information, insert the Release 2.2.2 software CD into the workstation and begin the upgrade process. You must upload and activate the software.


Caution Temporary traffic interruption is possible during the activation.


Caution Do not perform maintenance or provisioning activities during the upgrade process.

There are two flash RAMs on the TCC card. An upgrade uploads the software to the backup RAM on both the backup and active TCCs. This procedure does not affect traffic because the active software continues to run at the primary RAM location; therefore, you can upload the software at any time.

Upload


Step 1 Check all nodes in the ring for existing alarms. Resolve any outstanding alarms before proceeding.

Step 2 Ensure that no outstanding alarms are being declared against any synchronization facility. Clear any minor, major, or critical alarms on synchronization facilities before proceeding.


Note Information alarms are blue in color; you can disregard these.



Caution Because of bandwidth considerations, do not upload software to more than three nodes with one workstation at the same time.


Note During the software upgrade process, an alarm indicates that the software upgrade is taking place. This is normal and clears when the upgrade is complete.


Step 3 Using CTC Release 2.2.x, log into the node that is farthest from your workstation.

Step 4 From the CTC node view, click the Maintenance > Software tabs.

Step 5 Click Upgrade. The Software Upgrade dialog box opens.

Step 6 Click Open to locate the software files in the CD drive. The File Upload dialog box opens.

Step 7 From the CD drive directory, open the ONS 15454 folder.

Step 8 Select the file with the ".pkg" extension and click Open. The Software Upgrade dialog box opens.

Step 9 Click Upgrade.


Note CTC will display the node view and a pop-up status window so you can monitor the file transfer. A message indicating that your files transferred successfully will appear after the software has finished loading. The upgrade process can take 30 minutes or more.



Caution Do not close CTC during the upgrade. Closing CTC will abort the upgrade process.


Before You Activate

BLSR Nodes Only

If the node is in a bidirectional line switched ring (BLSR) configuration, you must complete the following steps before activating the new load.


Step 1 Perform a ring lockout to prevent switches from occurring during the upgrade.

a. Click the Maintenance > Ring tabs.

b. Right-click on one of the trunk cards (OC12 or OC48) and choose Ring Lockout from the pull-down menu.

c. Click Apply to activate the command. Leave the node in this state until the software is activated.


Note A Default K alarm or alarms on the protect STS timeslots can occur during this lockout period. Ignore these alarms if they occur.


Step 2 Repeat Step 1 at every node in the BLSR.

Step 3 Using CTC, reset each BLSR trunk card (OC12/OC48) one at a time.


Note If a card does not reset, do not continue with the activation process. Physically reseat the card if necessary. If you need to reseat the card or cards, make sure you first release all lockouts on protection switches. Once the card is rebooted and active, issue the lockouts again.


Step 4 Repeat Step 3 at every node in the BLSR.


All Nodes

Perform the following steps for all nodes in the network. Begin with the farthest node out and work in towards the node hosting CTC (your workstation).


Step 1 From the CTC node view, right-click the STBY TCC and choose Reset from the pop-up menu.

Step 2 Before activating the new load, wait for the standby TCC to come back up. If the card is visible, wait for the green SYNC LED on the standby TCC to light up. If the card is not visible, wait two or three minutes after the standby TCC's reset alarm clears before activating the new load.

Step 3 Make sure all cards that are part of a protection group (1:1 and 1:N) are active on the working card of that protection group and that no protection switches are occurring. In other words, make sure protect cards are in standby before proceeding.

Step 4 To ensure database synchronization, run the memAudit utility:

a. Close all active telnet connections to the ONS 15454.

b. Copy the memAudit.exe from the ONS 15454 software CD or the following Cisco.com web page to a folder on your hard drive:

http://www.cisco.com/pcgi-bin/tablebuild.pl/ons15454

c. In a command window, change the prompt to the folder where the memAudit.exe is located.

d. At the prompt, type the following command:

memAudit <nodename or IP address>


Note Optional parameters exist for the memAudit command. For more information about the memAudit utility, view the memAudit_readme.htm file on the CD or Cisco.com web page.



Activate the New Load

Log in and activate each node beginning with the farthest node in the network and ending with your workstation node.


Step 1 Log into the node farthest from the node you are connected to.

Step 2 Verify that the node has no active alarms.

Step 3 From the CTC node view, click the Maintenance > Software tabs.

Step 4 Verify that the protect software displays 2.2.2.

Step 5 Click Activate. The Activate dialog box appears with a warning message.

Step 6 Click Yes to proceed with the activation.

Step 7 After activating the node, wait until the software upgrade finishes at that node before continuing.

Activation proceeds from the node through each card installed, beginning with the standby TCC. Once the standby TCC is fully activated and fully rebooted, it becomes the active TCC and the other TCC reboots. Then the XC or XCVT and AIC reboot; next, the line cards boot from left to right one by one. The whole process takes approximately 30 minutes. This process is traffic affecting, so Cisco recommends that you activate the new load during a maintenance window. TDM traffic will endure a 50 ms or greater hit, and Ethernet traffic will take about a 3 to 4 minute hit due to STP recalculation. After all cards have booted, the active XCVT boots again to ensure that all circuits are updated correctly. Once the active XCVT finishes this final reboot and all alarms clear you can safely proceed to the next step.

Step 8 Shut down and restart your Netscape or Internet Explorer browser.

Step 9 Reconnect to CTC using the IP address from Step 2. The new CTC applet for Release 2.2.2 uploads. This applet gives you network visibility while you are upgrading.


Note Only activate one node at a time.


Step 10 Log into each of the remaining nodes and activate them one at a time. Make sure each node is finished and clear of alarms for ten minutes before activating the next node.

Step 11 After each node is finished, you must log out of your CTC session in Netscape to download the new Java plug-ins from the ONS 15454 node.

Step 12 After activating the last node (the node connected to your workstation) wait for the system to reboot.



Note Be patient. The system might take several minutes to reboot.


BLSR Nodes

Release the span lockouts on all BLSR nodes after the new software load is activated on all nodes.


Step 1 In CTC node view, click the Maintenance > Ring tabs.

Step 2 Select the direction where the lockout is active.

Step 3 Select Clear.

Step 4 Click Apply to activate the command.

Step 5 You might need to invoke the ring map table and accept it to clear Default K byte or Node ID mismatch alarms. Go to the Ring tab and click the Ring Map button. Accept the ring map.


Date Setting

The upgrade procedure can cause the Date setting to change.


Step 1 In CTC node view, click the Provisioning > General tabs.

Step 2 Set the correct date and click Apply.

Step 3 Repeat Steps 1 and 2 for each remaining node.


Spare TCC Units

All spare TCC units should be upgraded to CTC Release 2.2.2 software.


Step 1 Determine the standby TCC; the yellow STBY LED is illuminated.

Step 2 Physically remove the standby TCC.

Step 3 Insert the spare TCC in the unoccupied TCC slot and allow it to boot up.

The TCC automatically upgrades to the software version on the active TCC. This automatic upgrade can take about 30 minutes and LEDs flash during this process. The TCC that you removed can be used as the spare.


XC to XCVT Upgrade

This procedure explains how to replace dual XC cards with dual XCVT cards without affecting traffic.

The procedure requires that the ONS 15454 is running CTC Release 2.2.0 or later. The node also needs two XC cards installed and two XCVT cards available.


Step 1 Determine the standby XC card. The ACT/STBY LED of the standby XC card is yellow and the ACT/STBY LED of the active card is green.

You can also put the mouse cursor over the card graphic in CTC to reveal a tooltip displaying Active/Standby status.

Step 2 Unlatch the top and bottom ejector levers of the STANDBY XC card. Remove the card from the slot and put it away.

Step 3 Insert the first XCVT into the empty slot and latch the ejectors.

The red FAIL LED on the card illuminates, blinks for several seconds, then turns off. The ACT/STBY LED turns yellow and stays on.

Step 4 In CTC node view click the Maintenance > XC Cards tabs.

Step 5 Choose Manual from the menu for the Slot X on the active XC card.

Step 6 Click Apply.

A minor alarm appears on the manually-switched slot.

Step 7 On the same slot, choose Clear from the pull-down menu to remove the manual operation.

Step 8 Click Apply.

The XCVT should now be active as indicated by the green ACT/STBY LED.

Step 9 Remove the second XC card after verifying that it is the standby card.

Step 10 Replace the second XC card with the second XCVT card and allow it to boot up.


Restore the Previous Software and Database

Unexpected catastrophic events during the upgrade might require you to terminate the upgrade process and return to the previous software load and database. The TCC requires two procedures to restore the previous software and database. You should have saved a copy of the database in the "Back Up the Database" section.


Caution This process is traffic affecting and should be performed during a service window.

Manually Restore the Software Load


Step 1 Record the IP address of the node you connected to CTC on.

Step 2 From the node view, right-click the standby TCC and choose Reset. An "Are You Sure" dialog box appears asking you to confirm the choice.

Step 3 Click Yes. The standby TCC reboots.

Step 4 Wait for the TCC to finish rebooting (this will take approximately 4 minutes).

Step 5 From the node view, click the Maintenance > Software tabs.

Step 6 Verify that the protect software displays 2.2.x (the release you were upgrading from).

Step 7 Click Revert. A dialog box asks you to confirm that you wish to revert.


Note On the TCC+, revert activates the protect software and restores the database from the previous load; however, on the TCC, revert only activates the protect software. This is why you must also manually restore the database when restoring with TCC cards.


Step 8 Click OK. This begins the revert and drops the connection to the node.

Step 9 After restoring the software, wait until the downgrade finishes at that node before continuing.


Note Be patient. The system reboot might take up to 30 minutes to complete.


Step 10 Shut down your Netscape or Internet Explorer browser.

Step 11 Wait one minute before restoring another node.

Step 12 After reverting all of the nodes in the network, restart the browser and log back into the last node that was reverted with the IP address that you recorded in Step 1. This uploads the appropriate CTC applet for Release 2.2.x to your workstation.


Manually Restore the Database


Step 1 From the CTC node view, click the Maintenance > Database tabs.

Step 2 Click Backup. The "Open..." dialog box opens.

Step 3 Select the previously-saved file and choose Open.

The database will be restored and the TCCs will reboot.

Step 4 Once the TCCs have rebooted, log back into CTC and verify that the database is restored.

Wait one minute before restoring the next node.