 Feedback
|
Contents
- Upgrading the Cisco ONS 15454 to Release 9.2.1
- Software Upgrade Compatibility
- Errorless Upgrades and Exceptions
- Document Procedures
- NTP-U487 Preparing to Upgrade to a New Release
- DLP-U544 Verify CTC Workstation Requirements
- DLP-U545 Verify Common Control Cards
- NTP-U488 Back Up the Cisco ONS 15454 Software Database
- NTP-U489 Upgrade the Cisco ONS 15454 Software
- DLP-U546 Download the ONS 15454 Software
- DLP-U547 Perform a BLSR Lockout
- DLP-U548 Activate the New Cisco ONS 15454 Software
- DLP-U549 Delete Cached JAR Files
- DLP-U550 Remove the BLSR Lockout
- DLP-U551 Set the Date and Time
- NTP-U490 Install Public-Key Security Certificate
- NTP-U491 Restore the Previous Software Load and Database
- DLP-U552 Revert to Protect Load
- DLP-U553 Manually Restore the Database
- NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Card
- NTP-U510 Upgrade the TSC Card to the TNC Card
- NTP-U493 Upgrade to the ONS 15454 Software Using TL1
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
Upgrading the Cisco ONS 15454 to Release 9.2.1
This document explains how to upgrade Cisco ONS 15454 Cisco Transport Controller (CTC) software using the Advanced Timing Communications and Control (TCC2), Advanced Timing Communications and Control Plus (TCC2P), Timing Communications Control Three (TCC3), Transport Node Controller (TNC), or Transport Shelf Controller (TSC) card.
To understand the supported upgrade paths, refer to the Software Upgrade Compatibility.
NoteThe Transport Node Controller and the Transport Shelf controller cards are the control cards installed on ONS 15454 M2 and ONS 15454 M6 shelves.
NoteThe OC-48 IR 1310 card is supported from R8.5 and later.
- Software Upgrade Compatibility
- Errorless Upgrades and Exceptions
- Document Procedures
- NTP-U487 Preparing to Upgrade to a New Release
- NTP-U488 Back Up the Cisco ONS 15454 Software Database
- NTP-U489 Upgrade the Cisco ONS 15454 Software
- NTP-U490 Install Public-Key Security Certificate
- NTP-U491 Restore the Previous Software Load and Database
- NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Card
- NTP-U510 Upgrade the TSC Card to the TNC Card
- NTP-U493 Upgrade to the ONS 15454 Software Using TL1
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
Software Upgrade Compatibility
This table describes the possible upgrade paths supported from Releases 4.1.x, 4.5.x, 4.6.x, 4.7.x, 5.0.x, 6.0.x, 6.2.x, 7.0.x, 7.2.x, 8.0.x, 8.5.x, 9.0.x, 9.1.x, and 9.2 to Release 9.2.1 in the Multiservice Provisioning Platform (MSPP).
Releases 7.2.3, 8.6.1, 8.5.x, 9.0.1, 9.1.0, 9.2.0, 9.2.0.3 can be upgraded to Release 9.2.1 in Cisco ONS 15454 MSPP
Table 1 Supported Software Upgrades for the Cisco ONS 15454 MSPP Release
Upgrade Options
4.1x1
4.5.x2, 4.6.x2, 4.7.x2, 5.0.x2, 6.0.x2, 6.2.x2, 7.0.x2, 7.2.x2, 8.0.x2, 8.5.x2, 9.1.x
4.5.x
4.6.x2, 4.7.x2, 5.0.x2, 6.0.x2, 6.2.x2, 7.0.x2, 7.2.x2
4.6.x
4.7.x2, 5.0.x2, 6.0.x2, 6.2.x2, 7.0.x2, 7.2.x2
4.7.x
5.0.x2, 6.0.x2, 6.2.x2, 7.0.x2, 7.2.x2
5.0.x
6.0.x2, 6.2.x2, 7.0.x2, 7.2.x2, 8.0.x2, 8.5.x2, 9.1.x
6.0.x
6.2.x2, 7.0.x2, 7.2.x2, 8.0.x2, 8.5.x2
6.2.x
7.2.x2, 8.0.x2, 8.5.x2
7.0.x
7.2.x2, 8.0.x2, 8.5.x2, 9.0.x, 9.1.x, 9.2
7.2.x
8.0.x2, 8.5.x2, 9.0.x, 9.2.1
8.0.x
8.5.x2, 9.0.x, 9.2
8.5.x3
9.0.x
9.0.x, 9.1.x, 9.2, 9.2.1
9.1.x
9.1.x, 9.2, 9.2.1
9.2.x
9.2.1
1 Before upgrading from R4.1.x or later, make sure that the TCC2P cards are installed.2 Support is limited because Cisco has either announced End-of-Life of the release, or the version you are upgrading to is a non-preferred release.3 R8.5.4 and R8.6.1 can be upgraded to R9.2.1.5.4 For DS1 payload, R8.5.4 to R9.0 / R9.1 upgrade is not supported. Also, during an upgrade from R8.5.4 to R9.0 / R9.1, the E1 traffic may be lost and can be recovered by applying and releasing terminal or facility loopback on the E1 ports that carries traffic.5 Upgrade is not supported for R8.5.1. All other 8.5.x releases are supported.This table describes the possible upgrade paths supported from Releases 4.1.x, 4.5.x, 4.6.x, 4.7.x, 5.0.x, 6.0.x, 6.2.x, 7.0.x, 7.2.x, 8.0.x, 8.5.x, 9.0.x, 9.1.x, and 9.2.x to Releases 9.2.1 in the Cisco ONS 15454 Multiservice Transport Platform (MSTP).
Releases 7.2.3, 8.6.1, 8.5.x, 9.0.0, 9.0.1, 9.1.0, 9.2.0, 9.2.0.2, and 9.2.0.3 can be upgraded to Release 9.2.1 in Cisco ONS 15454 MSTP.
Releases 9.2.0, 9.2.0.2, and 9.2.0.3 can be upgraded to Release 9.2.1 in Cisco ONS 15454 M2 and Cisco ONS 15454 M6 MSTP.
Table 2 Supported Software Upgrades—Cisco ONS 15454 MSTP Release
Upgrade Options
4.1x6
4.5.x7, 4.6.x7, 4.7.x7, 5.0.x7, 6.0.x7, 6.2.x7, 7.0.x7, 7.2.x7, 8.0.x7, 8.5.x7
4.5.x
4.6.x7, 4.7.x7, 5.0.x7, 6.0.x7, 6.2.x7, 7.0.x7, 7.2.x7
4.6.x8
4.7.x7, 5.0.x7, 6.0.x7, 6.2.x7, 7.0.x7, 7.2.x7
4.7.x
5.0.x7, 6.0.x7, 6.2.x7, 7.0.x7, 7.2.x7
5.0.x
6.0.x7, 6.2.x7, 7.0.x7, 7.2.x7, 8.0.x7, 8.5.x7, 9.1.x, 9.2
6.0.x
6.2.x7, 7.0.x7, 7.2.x7, 8.0.x7, 8.5.x7
6.2.x
7.2.x7, 8.0.x7, 8.5.x7
7.0.x
7.2.x
8.0.x7, 8.5.x7, 9.0.x, 9.2, 9.2.1
8.0.x
8.5.x7, 9.0.x, 9.1.x, 9.2
8.5.x
8.5.x7, 9.0.x, 9.1.x11, 9.211, 9.2.1
9.0.x
9.0.x, 9.1.x, 9.2, 9.2.1
9.1.x
9.1.x, 9.2, 9.2.1
9.2.x
9.2.1
6 Before upgrading from R4.1.x or later, make sure that the TCC2P cards are installed.7 Support is limited because Cisco has either announced End-of-Life of the release, or the version you are upgrading to is a non-preferred release.8 If a direct upgrade from R4.6.x to R8.0.0 or later is performed on ONS 15454 nodes containing TXP and MXP cards, CTC does not display the cards in card view. Therefore, when upgrading from R4.6.x to R8.0.0 and later, perform a step upgrade to R7.0.7 and then upgrade to R8.0.0 or later.9 To upgrade a multi-shelf node from R7.0.0 or R7.0.1 to R8.5.x, R9.0.x, R9.1.x, R9.2, or R9.2.1 perform a step upgrade to R8.0.0 before upgrading to the destination version. R7.0.2 through R7.0.5 can be upgraded directly to R8.5.x, R9.0.x, R9.1.x, R9.2, or R9.2.1.10 To upgrade a multi-shelf node from R7.0.6 to R9.2.1, perform a two step upgrade to R8.00 or R8.51 and then to R9.2.1.11 Upgrade is not supported for R8.5.1. All other 8.5.x releases are supported.Errorless Upgrades and Exceptions
This section describes important information to be aware of before you begin the upgrade process:
- When a node installed with GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE cards configured with REP or LACP is upgraded, traffic loss may occur. This traffic loss is due to reconvergence when the cards soft reset during the upgrade process.
- If Y-cable protection is not provisioned, the data path incurs a traffic hit of up to 10 seconds or less.
- If Y-cable protection is provisioned on cards running Fiber Channel (FC) payloads, traffic switches away from the card downloading the new FPGA causing the FC link to be reinitialized.
- If Y-cable protection is provisioned on cards running Gigabit Ethernet (GE) payloads, there is no traffic interruption.
- During R7.x and R8.x upgrades to later releases, user data channel (UDC) traffic passing through the OSC-CSM and OSCM cards incur a traffic hit for a few milliseconds.
- During an upgrade from R 8.5.x, R 9.0, or R 9.1 to R 9.2.x or later releases, a loss of Gigabit Ethernet traffic of up to one second is incurred. This traffic loss occurs when auto-negotiation is disabled on the far end of the ADM-10G card. If the node has a path protection circuit, a path protection switchover occurs. To avoid this switchover during an upgrade, perform the path protection lockout procedure before upgrading the software. Note, however, this procedure does not help avoid hits in the flow of traffic.
- During a revert procedure, if Gigabit Ethernet traffic is not flowing or GFP alarms are present on an ADM-10G card, hard-reset the ADM-10G card to ensure smooth traffic flow.
- In R9.2.1.x, the CE-1000-4 card incurs a traffic hit of 30 seconds during activation and FPGA card upgrade. The upgraded CE-1000-4 card also incurs a traffic hit of 110 seconds if the software is subsequently reverted, because the FPGA is downgraded during the revert.
NoteWhen upgrading from R5.0 to R6.0 or later in enhanced card mode on nodes running an FC_MR-4 card, a hitless software upgrade is not possible. This is because the FPGA must be upgraded to support differential delay in enhanced mode. However, the upgrade is hitless in the line rate mode.
The following tables are define where errorless upgrades or exceptions can occur.
The following table applies to nodes equipped with XC-VXC-10G cards
Table 3 XC-VXC-10G Card Type
Expected Traffic Effect
DS-1
Errorless
DS-3
Errorless
DS3E
Errorless
DS3XM
Errorless
EC-1
Errorless
OC-N
Errorless
E-Series Ethernet
Traffic hits up to 5 minutes (approximately)
ML-Series Ethernet
Traffic hits 3–8 minutes (approximately)
CE-Series Ethernet
Errorless
G-Series Ethernet
Errorless (except as noted)
The following table applies to nodes equipped with XC10G cards.
Table 4 XC10G Card Type
Expected Traffic Effect
DS-1
Errorless
DS-3
Errorless
DS3E
Errorless
DS3XM
Errorless
EC-1
Errorless
OC-N
Errorless
E-Series Ethernet
Traffic hits up to 5 minutes (approximately)
ML-Series Ethernet
Traffic hits 3–8 minutes (approximately)
CE-Series Ethernet
Errorless
G-Series Ethernet
Errorless (except as noted)
The following table applies to nodes equipped with XCVT cards. (Errorless upgrade is not guaranteed in this case.)
Table 5 XCVT Card Type
Expected Traffic Effect
DS-1
Traffic hits < 60 ms (hitless)
DS-3
Traffic hits < 60 ms (hitless)
DS3E
Traffic hits < 60 ms (hitless)
DS3XM
Traffic hits < 60 ms (hitless)
EC-1
Traffic hits < 60 ms (hitless)
OC-N
Traffic hits < 60 ms (hitless)
E-Series Ethernet
Traffic hits up to 5 minutes (approximately)
ML-Series Ethernet
Traffic hits 3–8 minutes (approximately)
CE-Series Ethernet
Traffic hits < 60 ms (hitless)
G-Series Ethernet
Hitless; traffic hits < 60 ms
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 15454 , 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.
This section lists the document procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
- NTP-U487 Preparing to Upgrade to a New Release—This procedure contains critical information and tasks that you must read and complete before beginning the upgrade process.
- NTP-U488 Back Up the Cisco ONS 15454 Software Database—Complete the database backup to ensure that you have preserved your node and network provisioning in the event that you need to restore them.
- NTP-U489 Upgrade the Cisco ONS 15454 Software—Complete this procedure to complete the upgrade.
- NTP-U490 Install Public-Key Security Certificate— Complete this procedure to be able to run the ONS 15454 Software.
- NTP-U491 Restore the Previous Software Load and Database— Complete this procedure if you want to return to the previous software load you were running before activating the new release.
- NTP-U493 Upgrade to the ONS 15454 Software Using TL1— Complete this procedure only if you want to upgrade to a new release using Transaction Language (TL1).
NTP-U487 Preparing to Upgrade to a New Release
Procedure
Purpose
This procedure provides critical information checks and tasks you must complete before beginning an upgrade to R9.2.1.x.
Tools/Equipment
Cisco ONS 15454 nodes
Prerequisite Procedures
"DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document.
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
Step 1 Before you begin, make sure that information related to your site, for example, date, street address, site phone number, and dialup number are stored in a safe and accessible location. The data will be useful during and after the upgrade. Step 2 Read the release notes of the release you are upgrading to. Visit http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html to download the release notes.
Note Disable APC before upgrading from R7.0.x to R8.0.x or later and enable it after the upgrade is complete.
Step 3 Complete the task, DLP-U544 Verify CTC Workstation Requirements. Step 4 Complete the task, DLP-U545 Verify Common Control Cards. Step 5 When you have completed the tasks for this section, proceed with the procedure, NTP-U488 Back Up the Cisco ONS 15454 Software Database. Stop. You have completed this procedure.
DLP-U544 Verify CTC Workstation Requirements
Procedure
Purpose
This task lists PC or UNIX workstation hardware and software requirements. Perform this task before upgrading the workstation to run the software.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
None
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
DLP-U545 Verify Common Control Cards
Procedure
Purpose
This task lists card-slot requirements of common control cards , and cross connect cards (XC-VXC-10G, XC10G, XCVXL, or XCVTcards ) in a node.
Tools/Equipment
PC or UNIX workstation with CTC installed
Prerequisite Procedures
Install the TCC2, TCC2P, TCC3, TNC, or TSC control cards.
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
NoteThe TCC2P card is an enhanced version of the TCC2 card and includes enhancements such as Ethernet security features and 64K composite clock BITS timing. The TCC3 card is an enhanced version of the TCC2P card and includes enhancements such as increased memory size and compact flash space.
NoteTCC2P or TCC3 cards act as TCC2 cards in releases prior to Software R6.0.
NoteThe TNC and TSC controller cards are installed on the ONS 15454 M2 and ONS 15454 M6 shelves.
CautionThe TCC2 card fails to boot when it is added as a standby card to a node containing an active TCC2P card configured in the secure mode.
NoteDense wavelength division multiplexing (DWDM) nodes need only control cards installed during the upgrade.
NTP-U488 Back Up the Cisco ONS 15454 Software Database
Procedure
Purpose
This procedure retains all configuration data for your network before performing the upgrade.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
- "DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document.
- NTP-U487 Preparing to Upgrade to a New Release
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
Note(BLSR nodes only) The database must be backed up prior to locking the bidirectional line switched ring.
Step 1 In the node view, click the Maintenance>Database tabs. Step 2 In the database pane, click the Backup button. The Database Backup dialog box is displayed.
Step 3 Click Browse. Navigate to the local PC directory or network directory and type a database name using the IP address of the node to upgrade (such as database15454SONET010107.db) in the File Name field and click OK. To overwrite an existing file, click Yes. Step 4 When the backup is complete, click OK. Step 5 Repeat Steps 1 through 5 for each node in the network. Step 6 (Optional) It is recommended that you manually log critical information by either writing it down, printing screens, or by exporting the data to an appropriate format, as applicable. Use the following table to determine the information that should be logged.
Information
Record Data Here
IP address of the node
Node name
Timing settings
DCC12 connections—list all optical ports with active DCCs
User IDs of all users, including at least one Superuser
Inventory—A print screen of the Inventory window
Active TCC2/TCC2P/TCC3 card
Slot 7 or Slot 11
Active XC-VXC-10G, XC10G, or XCVT card
Slot 8 or Slot 10
Active TNC/TSC (Cisco ONS 15454 M6) cards
Slot 1 and Slot 8
Active TNC/TSC (Cisco ONS 15454 M2) card
Slot 1
Network information—A print screen of the Provisioning tab in the network view
Current configuration (BLSR, linear, etc.)— A print screen, as needed
List all protection groups in the system—A print screen of the Protection group window
List alarms—A print screen of the Alarm window
List circuits—A print screen of the Circuit window
Stop. You have completed this procedure.
NTP-U489 Upgrade the Cisco ONS 15454 Software
Procedure
Purpose
This procedure upgrades the CTC software to R9.2.1.x and must be performed on all nodes, or groups of nodes to be upgraded.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
CautionDo not perform maintenance or provisioning activities during the activation task.
NoteDuring a parallel upgrade, when end-to-end circuits in an ML-Series resilient packet ring (RPR) are present across multiple nodes, traffic resumes only after all the nodes in these circuits complete activation
NoteIf you are upgrading multiple nodes from a release prior to Software R7.0 and have at least one optical channel network connection (OCHNC) circuit, you will see transient OCHTERM-INC conditions raised during the upgrade. This condition clears after all the nodes have been upgraded.
NoteSeveral alarms are raised during the upgrade due to software incompatibility. However. these alarms clear after the upgrade is complete.
NoteSeveral alarms are raised on the ML-Series cards since they undergo a hard reboot during the upgrade (cold restart is rarely used). These alarms clear after the upgrade is complete. On the ML-Series port the LOA, TPTFAIL, and VCG DOWN alarms are raised. On the paths traversed by the ML-Series circuits the SD-P, SF-P, and PDI-P alarms are raised.
NoteDuring the upgrade of R8.0 or R8.5.x to a later release, if path protection circuits of type UPSR_DRI or 2waydc was created on an ADM-10G card, any existing software provisioning on the card is lost. Therefore, make sure that these path protection circuit types are not present before you upgrade to a later release.
NoteThe ADM-10G card does not support adding drops to existing Synchronous Transport Signal (STS) circuits. Therefore, when upgrading from R8.0 to a later release, delete any STS circuits with multiple drops on the ADM-10G card.
Step 1 Insert the Cisco ONS 15454 Software CD into the workstation CD-ROM drive (or otherwise acquire access to the software) to begin the upgrade process.
Note Inserting the software CD activates the CTC Java Setup Wizard. Use the setup wizard to install the components or click Cancel to continue with the upgrade.
Step 2 (BLSR nodes only) The database must be backed up prior to locking the BLSR. See NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure for details. Step 3 (BLSR nodes only) Complete the DLP-U547 Perform a BLSR Lockout task. Step 4 Complete the DLP-U546 Download the ONS 15454 Software task for all nodes to be upgraded. Step 5 Complete the DLP-U548 Activate the New Cisco ONS 15454 Software task for all nodes to be upgraded.
Note Only one node can be activated at a time. During a parallel upgrade, activate another node as soon as the controller cards reboot successfully. To perform parallel upgrade remotely, wait five minutes for the controller cards to reboot completely.
Step 6 Complete the DLP-U549 Delete Cached JAR Files task, as necessary.
Caution If the Cisco ONS 15454 software is downloaded again after a version is activated, a revert to the previous version cannot be performed.
Step 7 (Optional) If you wish to ensure that a software revert to the previous software release is no longer possible, complete the DLP-U546 Download the ONS 15454 Software task or all nodes, or groups of nodes you are upgrading a second time. Step 8 Complete the DLP-U550 Remove the BLSR Lockout task for all BLSR nodes in the network.
Note Leave the BLSR in the lockout state until you have finished activating all nodes.
Step 9 Complete the DLP-U551 Set the Date and Time task for nodes that are not using Simple Network Time Protocol (SNTP). Step 10 If you need to return to the software and database you had before activating Software R9.2.1.x, proceed with the NTP-U491 Restore the Previous Software Load and Database procedure.
Note When you upgrade a TCC2 card to a TCC2P, the SFTWDOWN alarm can be raised and cleared more than once before the software download is complete. For example, when you remove the standby TCC2 card in Slot 11 and replace it with a TCC2P card, the SFTWDOWN alarm occurs within moments of this replacement. It can briefly clear and then occur again before the alarm is finally cleared at the end of the upgrade process.
Note When you upgrade a TCC2P card to a TCC3, the SFTWDOWN alarm can be raised and cleared more than once before the software download is complete. For example, when you remove the standby TCC2P card in Slot 11 and replace it with a TCC3 card, the SFTWDOWN alarm occurs within moments of this replacement. It can briefly clear and then occur again before the alarm is finally cleared at the end of the upgrade process
Step 11 To back up the Software R9.2.1.x database for the working software load, see NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure in order to preserve the database for the current release. After the upgrade is complete, the date and time in CTC is reset.
Stop. You have completed this procedure.
DLP-U546 Download the ONS 15454 Software
Procedure
Purpose
This task downloads R9.2.1.x software to the ONS 15454 nodes prior to activation.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Maintenance user or higher
NoteThe TCC2/TCC2P/TCC3/TNC/TSC card contains flash memory with two partitions—working and protect (backup). An upgrade downloads the software to the protect (backup) partition of the flash memory on both the standby and active TCC2/TCC2P/TCC3/TNC/TSC cards. This download is not traffic affecting because the active software continues to run in the primary RAM location. The software can therefore be downloaded at any time.
NoteTo download and upgrade the software using TL1, see the NTP-U493 Upgrade to the ONS 15454 Software Using TL1 procedure.
Step 1 From CTC View menu, choose Go to Network View. Step 2 Make sure that the alarm filter is turned off. To do so, complete the following:
Step 3 Resolve any outstanding alarms. To view alarms for all the nodes in the network, click the Alarms tab.
Note The SWFTDWN alarm is raised on the standby and active TCC2, TCC2P, TCC3, TNC, or TSC cards during software download. The alarms clears as soon as the download is complete.
Step 4 From the CTC View menu, choose Go to Home View to go to the node view. Step 5 Click the Maintenance> Software tabs. Step 6 Click the Download button. The Download Selection dialog box appears. Step 7 Locate the software files on the ONS 15454 software CD or on your hard drive. Step 8 To open the Cisco ONS 15454 folder, choose the file with the PKG extension and click Open. Step 9 From the list of compatible nodes, select the nodes where the software must be downloaded.
Note It is recommended that simultaneous software downloads on the section data communications channel (SDCC) be limited to eight nodes at a time, using the central node to complete the download. If more than eight concurrent software downloads are selected at a time, it is placed in a queue.
Step 10 Click OK. The Download Status column monitors the progress of the download. Step 11 Return to your originating procedure (NTP).
DLP-U547 Perform a BLSR Lockout
Procedure
Purpose
This task performs a BLSR lockout. If you have BLSR provisioned, you must perform this task before beginning the upgrade.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
Required/As Needed
Required for BLSR only
Onsite/Remote
Onsite or remote
Security Level
Maintenance user or higher
Note(BLSR nodes only) The database must be backed up prior to locking the BLSR. See NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure for details.
NoteDuring the activation, BLSR spans are not protected. You must leave the BLSR in the lockout state until you have finished activating all nodes in the ring. Ensure that the lockout is removed after activation.
NoteTo prevent ring or span switching, perform the lockout on both the east and west spans of each node.
Step 1 In node view, click the Maintenance tab, then click the BLSR button. Step 2 For each of the BLSR trunk (span) cards (OC-12, OC-48, OC-192, MRC-2.5-4, MRC-12,OC192-XFP), perform the following steps:
- Next to the trunk card row, click the East Switch column to show the shortcut menu.
- From the menu options, choose Lockout Protect.
- Click the Apply button.
- In the same row, click the West Switch column to show the shortcut menu.
- From the menu options, choose Lockout Protect.
- Click the Apply button.
Note Ignore any Default K alarms that occur on the protect synchronous transport signal (STS) time slots during this lockout period.
Note Step 3 Return to your originating procedure (NTP).
DLP-U548 Activate the New Cisco ONS 15454 Software
Procedure
Purpose
This task activates the software on each node in the network.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
DLP-U546 Download the ONS 15454 Software
DLP-U547 Perform a BLSR Lockout (if required)
Required/As Needed
Required
Onsite/Remote
Onsite or remote
Security Level
Superuser
NoteIt is recommended that the first node that is activated be connected via LAN. This ensures that the new CTC JAR files download to the workstation as quickly as possible.
If a node is provisioned to have no LAN access, the value is overridden in the case of node isolation. Additionally, if the node is not reachable, the LAN access is turned on. It is recommended that you avoid node isolation.
CautionG-Series cards (G1000-4 and G1K-4) purchased prior to R7.2 incur a traffic hit of 2 to 3 minutes per card during activation and FPGA card upgrade. When the software is reverted, the upgraded cards incur a traffic hit of 2 to 3 minutes since the FPGA is also downgraded.
NoteIf the Cisco IOS version has changed from the previous release to the new release, an ERROR-CONFIG alarm is raised on each ML-Series card after the reset. To clear this alarm, perform a copy running-config startup-config command (or a write mem command) on each ML-Series card. See the “Initial Configuration” chapter of the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.
Step 1 If CTC is not already started, start CTC. Step 2 Record the IP address of the node. The IP address can be obtained either on the LCD or on the upper left corner of the CTC window. Step 3 Make sure that the alarm filter is turned off. To do so, complete the following:
Make sure that all cards that are part of a 1+1 or Y-cable protection group must be active on the working card of the protection group and no protection switches are occurring.
Step 4 Ensure that traffic carrying protect cards are in a standby state. To do so, complete the following: Step 5 In shelf view, click the Maintenance > Software tabs. Step 6 Verify that the version in the Protect Version column is R9.2.1.x. Step 7 Click the Activate button. The Activate dialog box displays a warning message. Step 8 Click Yes to proceed with the activation. An Activation Successful message indicates that the software is successfully activated. Step 9 Click OK. The connection between CTC and the node is lost and CTC displays the Network view.
Step 10 After activating the node, the software upgrade reboot occurs as follows:
- All the common control cards (TCC2, TCC2P, TCC3, TNC, or TSC) in the node reboot beginning with the standby card. As soon as the standby card reboots, it signals the active card to reset as a standby card and the standby card transitions to active.
- While the second common control card reboots, the standby cross-connect card begins rebooting, followed by the active cross-connect card.
- The E-Series Ethernet cards reset simultaneously.
- Protect cards in the Y-cable protection group boot next, in the order that the protection group was created.
- 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.
- The SYSBOOT alarm is raised as soon as the common control cards and cross-connect card reset. This alarm clears when all the cards reset. The activation process can take up to 30 minutes, depending on the number of cards installed in the node.
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 the software upgrade, a reset alarm is raised on all the cards. When upgrading from Release 6.0, 6.1, 6.2, 6.2.x, 7.0, 7.0.x, 7.2, or 7.2.x to 8.0, a MANRESET alarm is raised on standby TCC cards and an AUTORESET alarm in all the other cards. However, from R8.0, the MANRESET alarm is not raised and the AUTORESET alarm is raised on all the cards.
Step 11 In CTC, choose File > Exit. Step 12 Start CTC again. Step 13 Click the Setting button in the CTC launcher window. The CTC launcher settings dialog box appears.
Step 14 Click the Delete Cache button in the Cache tab. A warning message is displayed.
Step 15 Click Yes to proceed with the cache deletion. Step 16 Click OK to close the CTC launcher settings dialog box. Step 17 (Optional) Run the Cache Loader pre-caching utility. This logs you into CTC at a faster pace after an upgrade. However, you must log into nodes running releases prior to Software R4.6.
Note If you do not plan to run the pre-caching utility, it is recommended 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.
Perform the following steps to run the Cache Loader.
- Load the Software CD into your CD-ROM drive. If the directory of the CD does not open automatically, open it.
- Double-click the setup.exe file to run the Installation Wizard. The CTC Installation Wizard dialog box appears.
- Click the Next button. The Setup Options dialog box appears.
- Choose Custom, and click the Next button. The Custom Options dialog box appears.
- Click to select Cisco Transport Controller, and CTC JAR files (deselect any other preselected options) and click the Next button. A confirmation dialog box appears.
- Click the Next button again. The CTC Cache Loader pre-caches the JAR files to your workstation, displaying a progress status box.
- When the utility finishes, click OK, and in the wizard, click Finish.
Step 18 Click the Launch CTC button. The new CTC applet loads. The login window is displayed.
Step 19 Type the user name and password and click Login.
Note Complete Steps 11 through 19 only after upgrading the first node in a network. This is because cached files must be removed from your workstation only once. For the remaining nodes, you will still be disconnected and moved to the network view during the node reboot. After the reboot is complete, CTC restores connectivity to the node.
Step 20 Return to your originating procedure (NTP).
DLP-U549 Delete Cached JAR Files
Procedure
Purpose
This task deletes cached JAR files.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
None
Required/As Needed
You need to complete this task after you activate the first network node.
Onsite/Remote
Onsite or remote
Security Level
Maintenance user or higher
NoteWhenever the CTC software is upgraded or reverted, make sure that the browser and hard drive cache files are cleared.
Step 1 Delete cached files from your browser directory. In Netscape:
- Select Edit > Preferences. Click the Advanced tab and click the Cache button.
- Click the Clear Memory Cache button, and click OK.
- Click the Clear Disk Cache button, and click OK twice.
In Microsoft Internet Explorer:
Step 2 Close the browser.
Note Cached JAR files cannot be deleted from the hard drive until the browser is closed. Other applications that use JAR files must also be closed. Step 3 On Windows systems, delete cached files from your workstation in this location: C:\Documents and Settings\username\Application Data\Cisco\CTC Step 4 Reopen the browser. You should now be able to connect to CTC. Step 5 Return to your originating procedure (NTP).
DLP-U550 Remove the BLSR Lockout
Procedure
Step 1 In CTC node view, click the Maintenance tab, then click the BLSR button. Step 2 For each of the BLSR trunk (span) cards (OC-12, OC-48, OC-192, MRC-2.5-4, MRC-12,OC192-XFP), perform the following steps:
Step 3 Repeat this task as many times as necessary to remove all BLSR span lockouts on the upgrade nodes. Step 4 Return to your originating procedure (NTP).
DLP-U551 Set the Date and Time
Procedure
Purpose
This task sets the date and time. If you are not using SNTP, the upgrade procedure can cause the Date/Time setting to change. Perform this task to reset 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
Security Level
Superuser
NoteIf you are using SNTP, this task is not applicable.
NTP-U490 Install Public-Key Security Certificate
Procedure
Purpose
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 15454 Software R4.1 or later.
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 on the PC only for the current session. After the session ends, the certificate is deleted. This dialog box appears at the next login into ONS 15454
- Deny—Denies permission to install the certificate. If this option is chosen, login into the ONS 15454 is denied.
- Grant always—Installs the public-key certificate and does not delete it after the session is over. It is recommended to use this option.
- View Certificate—The public-key security certificate is displayed.
After the completion of the security certificate dialog boxes, the web browser displays information about the Java and system environments. If this is the first login, a CTC downloading message appears while CTC files are downloaded to the computer. The process can take several minutes, if it is the first time. After the download, the CTC Login dialog box appears.
Step 3 Return to the software and database you had before activating the 9.2.1.x software, proceed with the NTP-U491 Restore the Previous Software Load and Database procedure. Stop. You have completed this procedure.
NTP-U491 Restore the Previous Software Load and Database
Procedure
Purpose
This procedure returns to the software and database provisioning that was present before 9.2.1.x was activated.
The software load and database cannot be restored to the previous version if the software on both the working and protect cards were upgraded to 9.2.1.x.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
"DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document.
NTP-U487 Preparing to Upgrade to a New Release
Required/As Needed
As needed
Onsite/Remote
Onsite or remote
Security Level
Superuser
NoteTasks to revert to a previous load are not part of the upgrade, and are provided here as a convenience to those wishing to perform a revert after an upgrade. If you have successfully performed all necessary procedures up to this point, you have finished the software upgrade.
CautionIf a node is set to secure, dual-IP mode, the database information is overwritten with this configuration and cannot be reverted to single-IP repeater mode.
NoteThe defaults database files (db files) used to restore the basic configuration on a single non-multishelf node are shipped along with the standard 9.2.1.x software release package. For a multishelf set-up, the multishelf configuration must be unprovisioned to restore the basic configuration using the defaults database file. Also, the database backup from a multishelf system can be used to restore the same multishelf system.
Step 1 (BLSR nodes only) The database must be backed up prior to locking the BLSR. See NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure for details. Step 2 (BLSR nodes only) Complete the DLP-U547 Perform a BLSR Lockout task. Step 3 Complete the DLP-U552 Revert to Protect Load task. Step 4 (BLSR nodes only) Complete the DLP-U550 Remove the BLSR Lockout task. Step 5 If the software revert to your previous release failed to restore the database, complete the DLP-U553 Manually Restore the Database task. Stop. You have completed this procedure.
DLP-U552 Revert to Protect Load
Procedure
Purpose
This task reverts to the software you were running prior to the last activation.
You cannot revert backwards to a previous version of the protect load if the software on both the working and protect sides is Software R9.2.1.x.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
NTP-U487 Preparing to Upgrade to a New Release
NTP-U488 Back Up the Cisco ONS 15454 Software Database
Required/As Needed
Required for revert
Onsite/Remote
Onsite or remote
Security Level
Superuser
NoteTo perform a supported (non-service-affecting) revert from 9.2.1.x, the release you want to revert to must have been working at the time you activated to the current software version on that node. Also, a supported revert automatically restores the node configuration at the time of the previous activation. The exception to this is when you have downloaded 9.2.1.x a second time, ensuring that no revert to a previous load can take place. In this case, the revert occurs, but is not traffic-affecting and does not change the database.
NoteEnsure that all cards that are part of a protection group (1+1 or Y-cable) are active on the working card of that protection group and that no protection switches are occurring. To ensure that traffic carrying protect cards are in a standby state, in the node view click the Maintenance tab, and view the Protect column for each of the listed protection groups. View the active/standby status of each card in the Maintenance tab.
Step 1 From the node view, click the Maintenance tab, then click the Software button. Step 2 Verify that the protect software displays the release you upgraded from. Step 3 Click the Revert button. Revert activates the protect software and restores the database from the previous load. A dialog box asks you to confirm the choice.
Note Any FPGA downgrades during the revert process may affect traffic. Configuration changes made after activation are lost when you revert.
Step 4 Click OK. This begins the revert process and drops the connection to the node. Step 5 Wait until the software revert completes before continuing.
Note The system reboot may take up to 30 minutes to complete.
Step 6 Wait one minute before reverting another node. Step 7 After reverting all the nodes in the network, restart the browser and log back into the last node that was reverted. This uploads the appropriate CTC applet to your workstation. Step 8 Perform the DLP-U549 Delete Cached JAR Files task. Step 9 Return to your originating procedure (NTP).
DLP-U553 Manually Restore the Database
Procedure
Purpose
This task manually restores the database. Use this task if you were unable to perform a revert successfully and need to restore the database.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
DLP-U552 Revert to Protect Load
DLP-U550 Remove the BLSR Lockout (if required)
Required/As Needed
As needed
Onsite/Remote
Onsite or remote
Security Level
Superuser
CautionDo not perform these steps unless the software revert failed.
CautionThis process is service affecting and should be performed during a maintenance window.
Step 1 In CTC node view, click the Maintenance tab, then click the Database button. Step 2 Click the Restore button. The Open dialog box appears. Step 3 Select the previously saved database file and click the Open button. The database is restored and the TCC2/TCC2P/TCC3/TNC/TSC cards reboot.
Step 4 When the TCC2/TCC2P/TCC3/TNC/TSC cards have finished rebooting, log into CTC and verify that the database is restored. Wait one minute before restoring the next node.
Step 5 Repeat Steps 1 to 4 for each node in the network. You have now completed the manual database restore.
Note When the complete database is restored, the node does not report an event regarding the IP change; the node reboots and configures the new IP from the database. If the IP address being restored is not in the CTC network IP addressing scheme, you might lose visibility of the node. To resolve this, you must launch CTC with the IP mentioned in the table against the database backup. Refer to the table, “Manually Recorded Data” in the NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure for more information.
Step 6 Return to your originating procedure (NTP).
NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Card
Procedure
Purpose
This procedure upgrades the TCC2/TCC2P card to the TCC3 card. The TCC3 card supports ONS 15454 R9.2.1.x. The TCC2/TCC2P card is compatible with ONS 15454 , as well as earlier software versions.
Tools/Equipment
Two TCC3 cards
Prerequisite Procedures
None
Required/As Needed
As needed
Onsite/Remote
Onsite
Security Level
Maintenance or higher
NoteDowngrade procedures from TCC3 cards to TCC2P/TCC2 cards are not supported. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).
Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15454 Procedure Guide. Step 2 Verify that the LAN wires on the backplane are installed properly. The TCC3 card does not autodetect miswired LAN connections. If a LAN connection is miswired, a LAN Connection Polarity Reversed condition appears. For information on installing LAN wires, refer to the Cisco ONS 15454 Procedure Guide. Step 3 Verify that the node you are upgrading has ONS 15454 R9.2.1.x installed. The software version is displayed in the upper left corner of the window. Step 4 Complete the NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure before beginning the upgrade. Step 5 Physically replace the standby TCC2/TCC2P card on the ONS 15454 with a TCC3 card.
Caution If your active TCC2/TCC2P card resets during the upgrade before the new TCC3 card is in full standby mode, remove the new TCC3 card immediately.
Step 6 When the newly installed TCC3 card is in standby, right-click the active TCC2/TCC2P card in CTC. Step 7 From the pull-down menu, click Reset Card. Wait for the TCC2/TCC2P card to reboot. The ONS 15454 switches the standby TCC3 card to active mode. The TCC2/TCC2P card verifies that it has the same database as the TCC3 card and then switches to standby.
Step 8 Verify that the remaining TCC2/TCC2P card is now in standby mode (the ACT/STBY LED changes to amber). Step 9 Physically replace the remaining TCC2/TCC2P card with the second TCC3 card.
- Open the TCC2/TCC2P card ejectors.
- Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete.
- Open the ejectors on the TCC3 card.
- Slide the TCC3 card into the slot along the guide rails.
- Close the ejectors.
Tip When a newly installed TCC3 card has a different version of the ONS 15454 software installed from the version running on the active TCC3 card, the newly installed TCC3 card automatically copies the software version running on the active TCC3 card. You do not need to do anything in this situation. However, loading the TCC3 card does not boot up in the normal manner. When the card is first inserted, the red FAIL LED stays on for a short period. The FAIL LED then blinks normally and all LEDs go dark. After loading the new software for approximately 10 minutes, the TCC3 card becomes the standby card and the amber LED is illuminated.
Step 10 If power-related alarms occur after the second TCC3 card is installed, check the voltage on the backplane. Refer to the Cisco ONS 15454 Troubleshooting Guide for information on clearing alarms. Stop. You have completed this procedure.
NTP-U510 Upgrade the TSC Card to the TNC Card
Procedure
Purpose
This procedure upgrades the TSC card to the TNC card on the Cisco ONS 15454 M6 shelf.
Tools/Equipment
Two TNC cards
Prerequisite Procedures
"DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document.
Required/As Needed
As needed
Onsite/Remote
Onsite
Security Level
Maintenance or higher
Step 1 Verify that the LAN wires on the RJ-45 LAN port are installed properly. The TNC card does not autodetect miswired LAN connections. If a LAN connection is miswired, a LAN Connection Polarity Reversed condition appears. For information on installing LAN wires, refer to the Cisco ONS 15454 Procedure Guide. Step 2 Verify that the node you are upgrading has ONS 15454 M6 Software installed. The software version is displayed in the upper left corner of the window. Step 3 Complete the NTP-U488 Back Up the Cisco ONS 15454 Software Database procedure before beginning the upgrade. Step 4 Physically replace the standby TSC card with a TNC card.
Note It takes approximately 10 minutes for the active TSC card to copy the system software and database to the newly installed TNC card. During this operation, the LEDs on the TNC card flash Fail and then the active/standby LED flashes. When the transfer completes, the TNC card reboots and goes into standby mode after approximately three minutes. Do not remove the card from the shelf during a database transfer.
Caution If your active TSC card resets during the upgrade before the new TNC card is in full standby mode, remove the new TNC card immediately.
Step 5 When the newly installed TNC card is in standby, right-click the active TSC card in CTC. Step 6 From the pull-down menu, click Reset Card. Wait for the TSC card to reboot. The standby TNC card is switched to active mode. The TSC card verifies that it has the same database as the TNC card and then switches to standby.
Step 7 Verify that the remaining TSC card is now in standby mode (the ACT/STBY LED changes to amber). Step 8 Physically replace the remaining TSC card with the second TNC card.
The second TNC card boots up. The second TNC card must also copy the database. Do not remove the card from the shelf during a database transfer.
Step 9 If power-related alarms occur after the second TNC card is installed, check the voltage on the RJ-45 LAN port. Refer to the Cisco ONS 15454 Troubleshooting Guide for information on clearing the alarms. Stop. You have completed this procedure.
NTP-U493 Upgrade to the ONS 15454 Software Using TL1
Procedure
Purpose
This procedure upgrades the ONS 15454 software to R9.2.1.x using TL1 rather than CTC.
Tools/Equipment
PC or UNIX workstation
Prerequisite Procedures
Required/As Needed
Optional
Onsite/Remote
Onsite or remote
Security Level
Superuser
NoteThis procedure assumes you are upgrading using TL1 Release 6.x and later. TL1 commands used prior to activation to Release 6.x vary in syntax depending on the ONS 15454 release that you are actually upgrading from. To ensure that your syntax for each command is correct, see the TL1 syntax in the Cisco ONS 15454 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
- RLS-PROTNSW-<OCN_TYPE>
NoteTo download the software using TL1, an FTP server or a terminal emulation program like HyperTerminal must be running on the workstation.
NoteThe download (COPY-RFILE) command is different when downloading software to a gateway network element (GNE) or an end network element (ENE) under the following conditions:
- FTP is being used.
- Server is set up with a login and password of FTPUSER1 and FTPUSERPASSWORD1.
- FTP server has an IP address of 10.1.1.1.
- FTP server is running on the standard FTP port.
- Software package is called “15454DWDMxxx-0930-xxxx-xxxx.pkg.”
NoteWhen upgrading from R8.0 and later, if the path protection circuits of type UPSR_DRI or 2waydc is created on the ADM-10G card, software provisioning is lost. Ensure that there are no path protection circuits of type UPSR_DRI or 2waydc created on the ADM-10G card before upgrading to the latest release.
The GNE and ENE commands are as follows:
- When downloading software to a GNE, use a command similar to: COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL, SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1/15454-03xx-A04K-1405.pkg”;
- When downloading software to an ENE, use a command similar to: COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL, SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.111.11.1:2361@90.90.90.90/15454-03xx-A04K-1405.pkg”;
The ":2361" 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 PKG 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:21@90.90.90.90/CISCO/SOFTWARE/15454-03xx-A04K-1405.pkg”;
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 15454 node. Step 2 Type the IP address for the node, using port 3083 or 2361. The terminal emulation interface displays a warning message and a command prompt (usually >). You can enter 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 Operation Support System (OSS) profile user ID (required).
- <CTAG> is the correlation tag that correlates command and response messages (required).
- <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 Repeat Step 2 for each node to be upgraded. Step 5 Select the IP address for the node, using port 3083 or 2361. Step 6 Type the COPY-RFILE command in the TL1 window or, if you are using HyperTerminal, click Transfer > Receive File, and use the associated dialog box to select a file to receive. The COPY-RFILE command downloads a new software package from the location specified by the FTP URL into the inactive flash partition residing on the controller card. COPY-RFILE:[<TID>]:<src>:<CTAG>::TYPE=<xfertype>,[SRC=<src1>],[DEST=<dest>],[OVWRT=<ovwrt>],[FTTD=<fttd>]; where:
- <TID> is the target identifier (optional).
- <src> is the source AID (required).
- <CTAG> is the correlation tag that correlates command and response messages (required).
- <xfertype> is the file transfer protocol (required).
- <src1> specifies the source of the file to be transferred (required).
- <dest> is the destination of the file to be transferred (required).
- <ovwrt> is overwrite. If <OVWRT> is yes, then files should be overwritten. If <OVWRT> is no, then file transfers will fail if the file already exists at the destination (required).
- <fttd> is the URL format (required).
Step 7 Repeat Step 6 for all nodes to be upgraded. Step 8 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. The format of the message is:
REPT EVT FXFR
SID DATE TIME
A ATAG REPT EVT FXFR
"<FILENAME>,<FXFR_STATUS>,[<FXFR_RSLT>],[<BYTES_XFRD>]"
;
where:
- <FILENAME> indicates the transferred file path name and is a string.
- <FXFR_STATUS> indicates the file transferred status: Start, IP (in progress), or COMPLD.
- <FXFR_RSLT> indicates the file transferred result: success or failure. FXFR_RSLT is optional (the FXFR_RSLT is only sent when the FXFR_STATUS is COMPLD).
- <BYTES_XFRD> indicates the percentage transfer complete and is optional (the BYTES_XFRD is only sent when the FXFR_STATUS is IP or COMPLD).
Step 9 Complete “NTP-U487 Preparing to Upgrade to a New Release” procedure on page 8 for each node to be upgraded. Step 10 Complete NTP-U488 Back Up the Cisco ONS 15454 Software Database for each node to be upgraded. Step 11 Lock each BLSR span on all the nodes being upgraded using the following command: OPR-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>::<SC>,[<SWITCHTYPE>][:<DIRN>]; where:
- <TID> is the target identifier (optional).
- <AID> is the Access IDentifier that indicates the facility in the node to which the switch request is directed.
- <CTAG> is the correlation tag that correlates command and response messages (optional).
- <SC> is the switch command that is to be initiated on the paths.
- <SWITCHTYPE> is the BLSR 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 BLSR. If this is the case, all BLSR spans on all nodes being upgraded must be locked. Nodes that are not being upgraded do not require BLSR spans lockouts. You must be aware of each span that is part of a BLSR to make sure all necessary spans are locked.
Note Ignore any Default K alarms that occur on the protect STS time slots during the lockout.
Note Some BLSR-related alarms may 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: BLSR-OOSYNC (MN); RING-MISMATCH (MJ); APSCDFLTK (MN); BLSR-RESYNC (NA).
Step 12 Verify that all necessary BLSR spans on each node being upgraded have been locked out using the following command: RTRV-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::::]; where:
Step 13 Verify that there are no outstanding alarms or conditions on each node using the following commands: RTRV-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::::]; where:
RTRV-ALM-ALL:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],[<CONDITION>],[<SRVEFF>][,,,];
- <TID> is the target identifier (optional)
- <AID> is the access identifier that indicates the facility in the node to which the switch request is directed (must not be null) (required).
- <TYPEREQ> is the type of condition to be retrieved. A null value is equivalent to ALL.
where:
- <TID> is the target identifier
- <AID> is the Access IDentifier that indicates the facility in the node to which the switch request is directed (must not be null).
- <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 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 14 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 (optional).
- <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. MEM_SW_TYPE is CANC to cancel the activation.
If the command is successful, the appropriate flash is selected and the TCC2/TCC2P/TCC3/TNC/TSC card reboots.
The following occurs:
- Each card in the node reboots, beginning with the standby TCC2/TCC2P/TCC3/TNC/TSC card. When the standby TCC2/TCC2P/TCC3/TNC/TSC card reboots, it signals to the active TCC2/TCC2P/TCC3/TNC/TSC card that it is ready to take over. When the active TCC2/TCC2P/TCC3/TNC/TSC receives this signal, it resets itself, and the standby TCC2/TCC2P/TCC3/TNC/TSC takes over and transitions to active. The pre-upgrade version of the TCC2/TCC2P/TCC3/TNC/TSC card is now the standby TCC2/TCC2P/TCC3/TNC/TSC.
- While the second TCC2/TCC2P/TCC3/TNC/TSC is rebooting, the stand by cross-connect card (SONET/SDH only) reboots, and then the active cross-connect card (SONET only) reboots.
- Next, the E-Series Ethernet cards reset simultaneously.
- 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, with the exception that E1-42 protect cards will always be reset before any of their peer working cards.
- A system reboot (SYSBOOT) alarm is raised while activation is in progress (following the TCC2/TCC2P/TCC3/TNC/TSC 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.) Repeat this step 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 to each node again to activate the software.
Step 15 After all nodes have been activated, log in using CTC or Telnet and verify there are no outstanding alarms. Step 16 Remove all BLSR lockouts using the following TL1 command: RLS-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::<DIRECTION>]; where:
- <TID> is the target identifier (optional)
- <AID> is the access identifier that indicates the facility in the node to which the switch request is directed (must not be null) (required).
- <CTAG> is the correlation tag that correlates command and response messages (optional).
- <DIRECTION> is the direction of transmission (transmit or receive). The possible values are:
For example:
RLS-PROTNSW-OC48:PETALUMA:FAC-6-1:209::BTH;Step 17 To back up the database for the working software load, see NTP-U488 Back Up the Cisco ONS 15454 Software Database in order to preserve the database for the current software. Stop. You have completed this procedure.
Related Documentation
Use this document in conjunction with the following publications:
- Release notes: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html
- TL1 command guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_command_reference_list.html
- Reference guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_technical_reference_list.html
- Procedure guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_installation_guides_list.html
- Configuration guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/products_installation_and_configuration_guides_list.html
- Troubleshooting guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_troubleshooting_guides_list.html
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: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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: http://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)
