Table Of Contents
Upgrading the Cisco ONS 15454 SDH to Release 9.1
Contents
Before You Begin
Errorless Upgrades and Exceptions
Document Procedures
NTP-U446 Preparation for Upgrading to Release 9.1
DLP-U480 Verify CTC Workstation Requirements
DLP-U481 Verify Common Control Cards
NTP-U447 Back Up the ONS 15454 SDH Software Database
NTP-U448 Upgrade to ONS 15454 SDH Software R9.1
DLP-U482 Download ONS 15454 SDH Software R9.1
DLP-U483 Perform an MS-SPRing Lockout
DLP-U484 Activate the New ONS 15454 SDH Software R9.1
DLP-U485 Delete Cached JAR Files
DLP-U486 Remove the MS-SPRing Lockout
DLP-U487 Set the Date and Time
NTP-U449 Install Public-Key Security Certificate
NTP-U450 Restore to Previous Software Load and Database
DLP-U488 Revert to Protect Load
DLP-U489 Manually Restore the Database
NTP-U451 Upgrade to ONS 15454 SDH Software R9.1 Using TL1
Related Documentation
Obtaining Optical Networking Information
Where to Find Safety and Warning Information
Cisco Optical Networking Product Documentation CD-ROM
Obtaining Documentation and Submitting a Service Request
Upgrading the Cisco ONS 15454 SDH to Release 9.1
This document explains how to upgrade Cisco ONS 15454 SDH Cisco Transport Controller (CTC) software from Releases 6.0, 6.1, 6.1.x, 7.0, 7.2, 7.2.x, 8.0, 8.5, 8.5.x, 9.0 to Release 9.1, using the Advanced Timing, Communications, and Control (TCC2) or Advanced Timing, Communications, and Control Plus (TCC2P) card.
Note 
The TCC2P card is an enhanced version of the TCC2 card. The primary enhancements are Ethernet security features and 64K composite clock building integrated timing supply (BITS) timing.
Contents
This document contains the following information:
•Before You Begin
•Errorless Upgrades and Exceptions
•Document Procedures
•U446 Preparation for Upgrading to Release 9.1
•U447 Back Up the ONS 15454 SDH Software Database
•U448 Upgrade to ONS 15454 SDH Software R9.1
•U449 Install Public-Key Security Certificate
•U450 Restore to Previous Software Load and Database
•U451 Upgrade to ONS 15454 SDH Software R9.1 Using TL1
•Related Documentation
•Obtaining Optical Networking Information
•Obtaining Documentation and Submitting a Service Request
Before You Begin
Before beginning, write down the following information about your site: date, street address, site phone number, and dialup number. This data will be useful during and after the upgrade.
Caution Read all procedures before you begin the upgrade.
Caution This upgrade is supported only for Release 6.0, 6.1, 6.1.x, 7.0, 7.2, 7.2.x, 8.0, 8.5, 8.5.x, and 9.0 upgrading to Software Release 9.1. If you wish to upgrade from an earlier software release, you must contact the Cisco Technical Assistance Center (Cisco TAC). For more information, see the
"Obtaining Documentation and Submitting a Service Request" section.
Note Software R9.1 supports parallel upgrades for multiple nodes in a network. In a parallel upgrade, you can still activate only 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.
Errorless Upgrades and Exceptions
The following tables define where errorless upgrades are expected for Software R9.1, and where exceptions can occur. Please review Table 1, Table 2, or Table 3 for your particular cross-connect card type.
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 resumes.
Caution G-Series cards (G1000-4 and G1000) purchased prior to Software R7.2 incur a traffic hit of 2 to 3 minutes per card during activation, while a field-programmable gate array (FPGA) upgrade to the card takes place. Cards thus upgraded also incur the same traffic hit if the software is subsequently reverted, since the FPGA is downgraded in the case of such a revert.
Note Upgrades for dense wavelength division multiplexing (DWDM) configurations are expected to be errorless with the following exception:
The MXP_MR_2.5 and MXPP_MR_2.5 cards automatically download a new FPGA image during a software upgrade from Software R8.5 or earlier to Software R9.1. For cards with no Y-cable protection, the data path incurs a traffic hit of up to 10 seconds (typically less). Y-cable-protected cards with Fibre Channel (FC) payloads incur an FC link reinitialization as traffic switches away from the card downloading the new FPGA image. Y-cable-protected cards with Gigabit Ethernet (GE) payloads will not incur a traffic hit.
Note For FC_MR-4 card, hitless software upgrades are not possible with an activation from Software R5.0 to Software R6.0 or higher in enhanced card mode. This is because the FPGA must be upgraded to support differential delay in enhanced mode. Upgrades are still hitless with the line rate mode.
Table 1 applies to nodes equipped with XC-VXC-10G cards.
Table 1 XC-VXC-10G
Card Type
|
Expected Traffic Effect
|
E1
|
Errorless
|
E3
|
Errorless
|
E1-42
|
Errorless
|
DS3I
|
Errorless
|
STMn (including STM64-XFP and STM1E)
|
Errorless
|
MRC-12
|
Errorless
|
ML-Series Ethernet
|
Traffic hits 3 to 8 minutes (approximately)
|
G-Series Ethernet
|
Errorless (except as noted)
|
E-Series and CE-Series Ethernet
|
Errorless
|
Table 2 applies to nodes equipped with XC-VXL-10G or XC-VXL-2.5G cards.
Table 2 XC-VXL-10G/XC-VXL-2.5G
Card Type
|
Expected Traffic Effect
|
E1
|
Errorless
|
E3
|
Errorless
|
E1-42
|
Errorless
|
DS3I
|
Errorless
|
STMn (including STM64-XFP and STM1E)
|
Errorless
|
MRC-12
|
Errorless
|
ML-Series Ethernet
|
Traffic hits 3 to 8 minutes (approximately)
|
G-Series Ethernet
|
Errorless (except as noted)
|
E-Series and CE-Series Ethernet
|
Errorless
|
Table 3 applies to nodes equipped with XC10G cards.
Table 3 XC10G
Card Type
|
Expected Traffic Effect
|
E-1
|
Errorless
|
E-3
|
Errorless
|
STM1E
|
Errorless
|
FMEC-DS1/E1
|
Errorless
|
FMEC-E1
|
Errorless
|
STM-N (including MRC-12 and STM64-XFP)
|
Errorless
|
E-Series Ethernet
|
Traffic hits up to 5 minutes (approximately)
|
ML-Series Ethernet
|
Traffic hits 3 to 8 minutes (approximately)
|
G-Series Ethernet
|
Errorless (except as noted)
|
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 SDH, 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).
1. U446 Preparation for Upgrading to Release 9.1—This section contains critical information and tasks that you must read and complete before beginning the upgrade process.
2. U447 Back Up the ONS 15454 SDH 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.
Caution You must back up the database when using a multiplex section-shared protection ring
(MS-SPRing) configuration.
3. U448 Upgrade to ONS 15454 SDH Software R9.1—You must complete this entire procedure to complete the upgrade.
4. U449 Install Public-Key Security Certificate—You must complete this procedure to be able to run ONS 15454 SDH Software R9.1.
5. U450 Restore to Previous Software Load and Database—Complete this procedure only if you need to return to the software load you were running before activating Software R9.1.
6. U451 Upgrade to ONS 15454 SDH Software R9.1 Using TL1—Complete this procedure only if you want to upgrade to Software R9.1 using Transaction Language (TL1).
NTP-U446 Preparation for Upgrading to Release 9.1
Purpose
|
This procedure provides the critical information checks and tasks you must complete before beginning an upgrade.
|
Tools/Equipment
|
ONS 15454 SDH nodes to upgrade
PC or UNIX workstation
Cisco ONS 15454 SDH Software R9.1
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Superuser
|
Step 1 Read the Release Notes for Cisco ONS 15454 SDH Release 9.1.
Step 2 Log into the node that you want to upgrade. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 3 Complete the "DLP-U480 Verify CTC Workstation Requirements" task.
Step 4 Complete the "DLP-U481 Verify Common Control Cards" task.
Step 5 When you have completed the tasks for this section, proceed with the "U447 Back Up the ONS 15454 SDH Software Database" procedure.
Stop. You have completed this procedure.
DLP-U480 Verify CTC Workstation Requirements
Purpose
|
This task verifies all PC or UNIX workstation hardware and software requirements. Use this task before upgrading the workstation to run CTC Software R9.1.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Step 1 Ensure that your workstation is one of the following:
•IBM-compatible PC with a Pentium IV or faster processor, CD-ROM drive, a minimum of 1 GB RAM and 250 MB of available hard drive space, running Windows 98, Windows NT 4.0 (with Service Pack 6a), Windows 2000 Professional (with Service Pack 3), or Windows XP Professional (with Service Pack 1 and 2).
Note To successfully run the CTC on workstations running Windows Vista, upgrade the CTC Software to R8.5.x or later. Releases prior to R8.5.x are not supported on Windows Vista.
•UNIX workstation with Solaris Version 9 or 10 on an UltraSPARC-III or faster processor, with a minimum of 1 GB RAM and a minimum of 250 MB of available hard drive space.
Step 2 Ensure that your web browser software is one of the following:
•Netscape Navigator 7.x or later on Windows
•Internet Explorer 6.x or later on Windows
•Mozilla 1.7 or later on Solaris
Note Cisco recommends you use either Internet Explorer 6.x or Netscape 7.x for Windows workstations running Software R9.1. However, if you upgrade to Netscape 7 or JRE 5.0 and you still need to launch CTC directly from nodes running software prior to R4.6, you must first run the pre-caching utility supplied in the setup program on the software CD. Run the pre-caching utility during the activation (Step 14" on page 16) in this case.
Step 3 Verify that the following are installed on your computer:
•Java Runtime Environment (JRE) 5.0
•Java Plug-in 5.0
Tip Check the JRE version in your browser window under Java Version after entering the node IP address in the URL window.
Note For important information about CTC backward compatibility affected by your choice of JRE version, see the Readme.txt or Readme.html file on the software CD.
Note To install JRE 5.0, the Java Policy file, or the SoftwareR9.1 online help, refer to the installation instructions in the Cisco ONS 15454 SDH Procedure Guide.
Step 4 Return to your originating procedure (NTP).
DLP-U481 Verify Common Control Cards
Purpose
|
This task verifies that two TCC2 or TCC2P cards and two XC-VXL-10G, XC-VXL-2.5G, XC-VXC-10G, or XC10G cards (SDH only) are installed at each node, as appropriate for your network configuration.
|
Tools/Equipment
|
PC or UNIX workstation with CTC installed
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Note The TCC2P card is an enhanced version of the TCC2 card. The primary enhancements are Ethernet security features and 64K composite clock BITS timing.
Note DWDM nodes need only TCC2/TCC2P cards installed during the upgrade.
Note When TCC is rebooted after running the VxWorks command to delete database, perform the following steps:
1. I/O cards need to be plugged out after running the VxWorks command to delete database and before rebooting TCC.
2. I/O cards need to be plugged in after TCC comes to ACTIVE.
The above steps are applicable even in the power cycle of the NODE after running the VxWorks command to delete database on the TCC.
Reasons:
•Running the VxWorks command to delete database and TCC reboot operation effectively erases the XC provisioning.
•The provisioning of some of the I/O cards (DS3/EC1,OC3-8, OC12-4, OC48-AS (in low-speed slots), OC192, and MRC-12) are dependent on XC provisioning and when this fails, the card is rebooted.
After the XC provisioning is restored (which typically takes a few seconds after the TCC reboot), the I/O cards can be successfully provisioned.
Step 1 Ensure that the cards are installed. The TCC2 or TCC2P cards are in Slots 7 and 11 and the XC-VXL-10G, XC-VXL-2.5G, XC-VXC-10G, or XC10G cards (as needed for SDH operation) are in Slots 8 and 10. Software R9.1 does not support simplex operation.
Step 2 Repeat Step 1 at every node in the network.
Step 3 Return to your originating procedure (NTP).
NTP-U447 Back Up the ONS 15454 SDH Software Database
Purpose
|
This procedure preserves all configuration data for your network before performing the upgrade.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U446 Preparation for Upgrading to Release 9.1
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Maintenance or higher; Superuser, if performing optional Step 9
|
Caution You must back up the database when using an MS-SPRing configuration.
Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide. After you log 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.
Step 4 In the Database Backup dialog box, click the Browse button, then navigate to a local PC directory or network directory and type a database name (such as database15454SDH010107.db) in the File Name field.
Step 5 In the Database Backup dialog box, click the OK button. If you are overwriting an existing file, click Yes in the confirmation dialog box.
Step 6 Click the Save button to save the database on the workstation's hard drive or on a network storage location.
Step 7 When the backup is complete, click OK.
Step 8 Repeat Steps 1 through 7 for each node in the network.
Step 9 (Optional) Cisco recommends that you manually log critical information by either writing it down, printing screens, or exporting the data to appropriate format where applicable. Use Table 4 to determine the information you should log; complete the table (or your own version) for every node in the network.
Table 4 Manually Recorded Data
Item
|
Record Data Here
|
IP address of the node.
|
|
Node name.
|
|
Timing settings.
|
|
DCC1 connections; list all optical ports that have DCCs activated.
|
|
User IDs; list all, including at least one Superuser.
|
|
Inventory; do a print screen from the Inventory window.
|
|
Active TCC2/TCC2P.
|
Slot 7 or Slot 11 (circle one)
|
Active XC-VXL-10G, XC-VXL-2.5G, XC10G, or XC-VXC-10G.
|
Slot 8 or Slot 10 (circle one)
|
Network information; do a print screen from the Provisioning tab in the network view.
|
|
Current configuration (MS-SPRing, linear, etc.); do print screens as needed.
|
|
List all Protection groups in the system; do a print screen from the Protection Group window.
|
|
List alarms; do a print screen from the Alarm window.
|
|
List circuits; do a print screen from the Circuit window.
|
|
Stop. You have completed this procedure.
NTP-U448 Upgrade to ONS 15454 SDH Software R9.1
Purpose
|
This procedure upgrades the node software to Software R9.1.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U447 Back Up the ONS 15454 SDH Software Database
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Caution Do not perform maintenance or provisioning activities during the activation task.
Caution When managing end-to-end circuits participating in an ML-Series RPR ring 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 resumes.
Note Software provisioning will be lost when upgrading from R8.0 or R8.5.x to R9.1 if path protection circuit of type UPSR_DRI or with type=2waydc is created on ADM-10G card. Ensure that there are no path protection circuit of type UPSR_DRI or with type=2waydc created on ADM-10G card before upgrading to R9.1.
Note CTC allows you to add new drops to an existing STS circuit by editing the circuit and creating new drops in the Drops tab. This feature, however, is not supported by the ADM-10G card. In R8.0 and R8.5.x, although ADM-10G card did not support this feature, if you attempted to add new drops by editing the existing STS circuit, CTC did not report any error or warning. This behavior has been corrected in R9.1. In R9.1, CTC reports an error if you try to add new drops to existing STS circuits. Hence, when upgrading from R8.0 or R8.5.x to R9.1, it is strongly recommended that you delete all STS circuits with multiple drops on the ADM-10G card. If this is not followed, upgrade to R9.1 may be successful but you may encounter unexpected behavior later.
Note After upgrading from R4.x, R5.x, R6.x, R7.0.x, R8.0.x to R9.1, the date and time in CTC is reset.
Note When upgrading to R9.1, the TCC2P cards go through hard reboot instead of soft reboot due to a change (enhancement) in the boot code. The new standby TCC2P displays the "NP" state for a small duration as the card hard reboots. This behavior does not impact any functionality.
Step 1 Insert the Software R9.1 CD into the workstation CD-ROM (or otherwise acquire access to the software) to begin the upgrade process.
Note Inserting the software CD activates the CTC Java Setup Wizard. You can use the setup wizard to install components or click the Cancel button to continue with the upgrade.
Step 2 Complete the "DLP-U482 Download ONS 15454 SDH Software R9.1" task for all nodes (or groups of eight or less nodes) you are upgrading.
Caution You must back up the database when using an MS-SPRing configuration.
Step 3 For MS-SPRing nodes only, complete the "DLP-U483 Perform an MS-SPRing Lockout" task.
Step 4 Complete the "DLP-U484 Activate the New ONS 15454 SDH Software R9.1" task for all nodes you are upgrading.
Note You can activate only 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 5 minutes from the time the SYSBOOT alarm is raised).
Step 5 If necessary, complete the "DLP-U485 Delete Cached JAR Files" task for all nodes, or groups of nodes you are upgrading a second time.
Caution If you download Software R9.1 a second time following activation you can not revert to the previous software version.
Step 6 (Optional) If you wish to ensure that a software revert to the previous software release is no longer be possible, complete the "DLP-U482 Download ONS 15454 SDH Software R9.1" task a second time.
Step 7 Complete the "DLP-U486 Remove the MS-SPRing Lockout" task for all MS-SPRing nodes in the network.
Note Leave the MS-SPRing in the lockout state until you have finished activating all nodes.
Step 8 For MS-SPRing nodes only, complete the "DLP-U487 Set the Date and Time" task for any nodes not using Simple Network Time Protocol (SNTP).
Step 9 As needed, upgrade any spare TCC2 or TCC2P cards by installing the spare in the standby slot of a Software R9.1 node.
Note The standby TCC2 or TCC2P card copies one or both software releases from the active TCC2 or TCC2P card, as needed. Each software copy takes about 5 minutes, and the TCC2 or TCC2P card resets after each copy. Thus, for a TCC2 or TCC2P card that has no matching software with the active TCC2 or TCC2P card, you should expect to see two TCC2 or TCC2P card resets and software copying lasting about 10 minutes total.
Step 10 If you need to return to the software and database you had before activating Software R9.1, proceed with the "U450 Restore to 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
Step 11 To back up the Software R9.1 database for the working software load, see "U447 Back Up the ONS 15454 SDH Software Database" procedure.
Stop. You have completed this procedure.
DLP-U482 Download ONS 15454 SDH Software R9.1
Purpose
|
This task downloads Software R9.1 to the ONS 15454 SDH nodes prior to activation.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U447 Back Up the ONS 15454 SDH Software Database
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser or Maintenance
|
Note The TCC2/TCC2P card has two flash RAMs. An upgrade, downloads the software to the backup RAM on both the standby and active TCC2/TCC2P cards. 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.
Note To download and upgrade the software using TL1, see the "U451 Upgrade to ONS 15454 SDH Software R9.1 Using TL1" procedure.
Step 1 From the CTC View menu, choose Go to Network View.
Step 2 Verify that the alarm filter is not on.
a. Click the Filter tool at the lower-left of the window.
The Alarm Filter dialog box appears.
b. Click to select any check box that is not selected in the Show Severity section of the General tab.
Step 3 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding alarms before proceeding.
Note During the software download process, the SFTWDOWN alarm is raised twice, once on standby and again on active, to indicate that the software download is taking place. The alarm is normal and clears when the download is complete.
Step 4 From the CTC View menu, choose Go to Home View to go to the node view.
Step 5 For nodes in single-shelf architecture mode, proceed to Step 7. For nodes in multishelf mode (implemented using either MS-ISC cards or external Catalyst switches) running software R7.00 or earlier, do the following:
a. Provision the active TCC/TCC2 cards in the node controller shelf and subtended shelf in slots 7 and before starting the upgrade process.
b. Make sure that all active TCC/TCC2 cards in the node controller and subtended shelf are in the same slot 11 (slot 7 is recommended). It they are, go to Step 7.
Step 6 Provision the node controller and subtended shelf in the same slot a switch-over of the active TCC/TCC2 card must be performed. Do the following:
a. Right-click the currently active TCC/TCC2 card (Slot 11) and choose Soft-reset Card.
b. Click Yes in the confirmation dialog box.
c. Click OK in the Connection Lost dialog box.
It might take a few minutes for CTC to establish connectivity
d. Verify if the standby TCC/TCC2 (slot 7) is active.
e. Repeat steps a to d as necessary.
Step 7 Return to node view and click the Maintenance tab, and then click the Software button.
Step 8 Click the Download button. The Download Selection dialog box appears.
Step 9 Browse to locate the software files on the ONS 15454 SDH software CD or on your hard drive, if you are working from a local copy.
Step 10 To open the Cisco15454SDH folder, select the file with the PKG extension and click the Open button.
Step 11 In the list of compatible nodes, click the check boxes for all nodes for software download.
Note Cisco advises that you limit concurrent software downloads to eight nodes at once, using the central node to complete the download.
Note If you attempt more than eight concurrent software downloads at once, the downloads in excess of eight will be placed in a queue.
Step 12 Click the OK button. The Download Status column monitors the progress of the download.
Note The software download process can take typically less than 10 minutes per node.
Step 13 Return to your originating procedure (NTP).
DLP-U483 Perform an MS-SPRing Lockout
Purpose
|
This task performs an MS-SPRing lockout. If you have an MS-SPRing provisioned, you must use this task before beginning the upgrade.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U447 Back Up the ONS 15454 SDH Software Database
|
Required/As Needed
|
Required for MS-SPRing only
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Maintenance
|
Note During activation, MS-SPRing spans are not protected. You must leave the MS-SPRing in the lockout state until all nodes in the ring are activated, and you must be sure to remove the lockout after activation.
Caution You must back up the database when using an MS-SPRing configuration.
Note To prevent ring or span switching, perform the lockout on both the east and west spans of each node.
Step 1 If CTC is not yet running, start CTC.
Step 2 In node view, click the Maintenance tab, then click the MS-SPRing button.
Step 3 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, MRC-2.5G-12, MRC-12, STM64-XFP), perform the following steps:
a. Next to the trunk card row, click the East Switch column to show the shortcut menu.
b. From the menu options, choose Lockout Protect.
c. Click Apply.
d. In the same row, click the West Switch column to show the shortcut menu.
e. From the menu options, choose Lockout Protect.
f. Click Apply.
Note Ignore any Default K alarms that occur on the protect VC4 time slots during this lockout period.
Note Certain MS-SPRing-related alarms might be raised following activation of the first node in the ring. The following alarms, if raised, are normal, and should not cause concern. They will clear upon completion of the upgrade, after all nodes have been activated.
•MSSP-OOSYNC (MN)
•RING-MISMATCH (MJ)
•APSCDFLTK (MN)
•MSSP-RESYNC (NA)
Step 4 Return to your originating procedure (NTP).
DLP-U484 Activate the New ONS 15454 SDH Software R9.1
Caution G-Series cards (G1000-4 and G1000) purchased prior to Software R7.2 incur a traffic hit of 2 to 3 minutes per card during activation, while an FPGA upgrade to the card takes place, and incurs the same traffic hit if the software is subsequently reverted, since the FPGA will be downgraded in the case of such a revert.
Note Ensure that all cards that are part of a protection group (1+1, 1:1, 1:N, 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, then click the Protection button. Select each of the listed protection groups, then view the active/standby status of each card in the Selected Group area.
Note Cisco recommends that you run the optional Cache Loader pre-caching utility in Step 14 of this 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.
Note ML-Series cards undergo a cold restart during an upgrade. The following alarms might be raised in conjunction with the ML-Series cold restart. These should clear when the upgrade is complete.
On the ML-Series port:
•LOA
•TPTFAIL
•VCG DOWN
On the paths traversed by the ML-Series circuits:
•SD-P
•SF-P
•PDI-P
Step 1 If CTC is not yet running, 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 In CTC node view, verify that the alarm filter is not on.
a. Click the Filter tool at the lower-left of the window.
The Alarm Filter dialog box appears.
b. Click to deselect any selections in the Show Severity section of the General tab.
Step 4 Click the Maintenance tab, and then click the Software button.
Step 5 Verify that the version in the Protect Version column is Software R9.1.
Step 6 Click the Activate button. The Activate dialog box displays a warning message.
Step 7 Click Yes to proceed with the activation.
Step 8 An Activation Successful message indicates that the software is successfully activated.
Step 9 Click OK in the message box.
Note When you click OK, CTC loses connection to the node and displays the network view.
Step 10 After activating the node, the software upgrade reboot occurs as follows:
•Each card in the node reboots, beginning with the standby TCC2 or TCC2P card. When the standby TCC2/TCC2P card reboots, it signals to the active TCC2/TCC2P card that it is ready to take over. When the active TCC2/TCC2P receives this signal, it resets itself, and the standby TCC2/TCC2P takes over and transitions to active. The pre-upgrade version of the TCC2/TCC2P card is now the standby TCC2/TCC2P.
•While the second TCC2/TCC2P is rebooting, the stand by cross-connect card (SONET/SDH only) reboots, and then the active cross-connect card (SONET/SDH 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, 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 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.)
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.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 11 In CTC, choose File > Exit.
Step 12 In your browser window, click the Delete CTC Cache button.
Note You must ensure that CTC is closed before clicking the Delete CTC Cache button. CTC behavior is unreliable if the button is clicked while the software is still running.
Note It might also be necessary to delete cached files from your browser's directory or from the TEMP directory on your MS Windows workstation. If you have trouble reconnecting to CTC, complete the "DLP-U485 Delete Cached JAR Files" task.
Step 13 Close your browser and then reopen it.
Step 14 (Optional) Run the Cache Loader pre-caching utility, which can improve your speed logging back into CTC after an upgrade, and which is required to log into nodes running releases prior to Software R4.6. Perform the following steps to run the Cache Loader.
a. Load the Software R9.1 CD into your CD-ROM drive. If the directory of the CD does not open automatically, open it.
b. Double-click the setup.exe file to run the Installation Wizard. The CTC Installation Wizard dialog box appears.
c. Click Next. The Setup Options dialog box appears.
d. Choose Custom, and click Next. The Custom Options dialog box appears.
e. Click to select Cisco Transport Controller, and CTC JAR files (deselect any other preselected options), then click the Next button. A confirmation dialog box appears.
f. Click the Next button again. The CTC Cache Loader pre-caches the JAR files to your workstation, displaying a progress status box.
g. When the utility finishes, click OK, and then in the wizard, click Finish.
Step 15 Reconnect to CTC using the IP address from Step 2. The new CTC applet for Software R9.1 uploads. During login, enter the user name and password.
Note Steps 11 through 15 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. After the reboot is complete, CTC restores connectivity to the node.
Step 16 Return to your originating procedure (NTP).
Note If a node is provisioned to have no LAN access, the value is overridden if there is a possibility of node isolation. Additionally, if the node is not reachable, the LAN access is turned on.
Cisco recommends that you avoid node isolation.
DLP-U485 Delete Cached JAR Files
Purpose
|
This task deletes cached Java JAR files. 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.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed.
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Maintenance or higher
|
Step 1 Delete cache files from your browser directory.
In Netscape:
a. Choose Edit > Preferences, click the Advanced tab, then click the Cache button.
b. Click the Clear Memory Cache button, and click OK.
c. Click the Clear Disk Cache button, and click OK twice.
In Microsoft Internet Explorer:
a. Choose Tools > Internet Options. The Internet Options dialog box appears.
b. Click the General tab.
c. Click Delete Files.
d. Select the Delete all offline content check box.
e. Click OK twice.
Step 2 Close your browser.
Note You cannot delete cached JAR files from your hard drive until you have closed your browser. If you have other applications open that use JAR files, you must also close them.
Step 3 On Windows systems only, delete cached files from your workstation ().
a. In your Windows start menu, choose Control Panel > System and click the Advanced tab.
b. Click the Environment Variables button. This shows you a list of user variables and a list of system variables.
c. In the list of user variables, look for the TEMP variable. The value associated with this variable is the path to your temporary directory where JAR files are stored.
d. Open the TEMP directory located in the path you just looked up.
e. click View > Details.
f. Select and delete all files with "jar" in the Name or Type field.
Step 4 Reopen your browser. You should now be able to connect to CTC.
Step 5 Return to your originating procedure (NTP).
DLP-U486 Remove the MS-SPRing Lockout
Purpose
|
This task releases the span lockouts on all MS-SPRing nodes after the new software load is activated on all nodes.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U484 Activate the New ONS 15454 SDH Software R9.1
|
Required/As Needed
|
Required for MS-SPRing
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser or Maintenance
|
Step 1 If CTC is not yet running, start CTC.
Step 2 In CTC node view, click the Maintenance tab, then click the MS-SPRing button.
Step 3 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, MRC-2.5G-12, MRC-12, STM64-XFP), perform the following steps:
a. Next to the trunk card row, click the West Switch column to show the shortcut menu.
b. From the menu options, choose Clear.
c. Click Apply to activate the command.
Note When removing a lockout, be sure to apply your changes each time you choose the Clear option. If you try to select Clear for more than one lockout at a time, you risk traffic loss on the first ring switch.
d. In the same row, click the East Switch column to show the shortcut menu.
e. From the menu options, choose Clear.
f. Click Apply to activate the command.
Step 4 Repeat this task as many times as necessary to remove all MS-SPRing span lockouts on the upgrade nodes.
Step 5 Return to your originating procedure (NTP).
DLP-U487 Set the Date and Time
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 (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Note If you are using SNTP, you do not need this task.
Step 1 In CTC node view, click the Provisioning > General tabs.
Step 2 Set the correct date and time, then click the Apply button.
Step 3 Repeat Steps 1 and 2 for each remaining node.
Step 4 Return to your originating procedure (NTP).
NTP-U449 Install Public-Key Security Certificate
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 SDH 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 to your PC only for the current session. After the session is ended, the certificate is deleted. This dialog box will appear the next time you log into the ONS 15454 SDH.
•Deny—Denies permission to install the certificate. If you choose this option, you cannot log into the ONS 15454 SDH.
•Grant always—Installs the public-key certificate and does not delete it after the session is over. Cisco recommends this option.
•View Certificate—Allows you to view the public-key security certificate.
Step 3 If you need to return to the software and database you had before activating Software R9.1, proceed with the "U450 Restore to Previous Software Load and Database" procedure.
Stop. You have completed this procedure.
NTP-U450 Restore to Previous Software Load and Database
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 R9.1, you should have backed up the existing database at all nodes in the network (this is part of the "U447 Back Up the ONS 15454 SDH 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.
Caution G-Series cards (G1000-4 and G1000) purchased prior to Software R7.2 will incur a traffic hit of 2 to 3 minutes per card during activation, while FPGA upgrade to the card takes place. Upgraded cards will also incur the same traffic hit if the software is subsequently reverted, as the FPGA will be downgraded in the case of such a revert.
Caution If you have converted a node to secure, dual-IP mode, the database information is overwritten with this configuration and you cannot revert it to single-IP repeater mode.
Note TCC2P cards act as TCC2 cards in software releases prior to R5.0.
Step 1 Log into the node. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide. If you are already logged in and this is not an MS-SPRing, continue with Step 4.
Step 2 (For MS-SPRing nodes only) The database must be backed up prior to locking the MS-SPRing nodes. See "U447 Back Up the ONS 15454 SDH Software Database" procedure for details.
Step 3 (For MS-SPRing nodes only) Complete the "DLP-U483 Perform an MS-SPRing Lockout" task.
Step 4 Complete the "DLP-U488 Revert to Protect Load" task.
Step 5 (For MS-SPRing nodes only) Complete the "DLP-U486 Remove the MS-SPRing Lockout" task.
Step 6 If the software revert to your previous release failed to restore the database, complete the
"DLP-U489 Manually Restore the Database" task.
Stop. You have completed this procedure.
DLP-U488 Revert to Protect Load
Note To perform a supported (non-service-affecting) revert from Software R9.1, the release you want to revert to must have been working at the time you activated to Software R9.1 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 exception to this is when you have downloaded Software R9.1 a second time, ensuring that no revert to a previous load can take place. In this case, the revert will occur, but will not be traffic affecting and will not change you database.
Note Ensure that all cards that are part of a protection group (1+1, 1:1, 1:N, 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, then view the active/standby status of each card in the Maintenance tab.
Step 1 From the node view, click the Maintenance tab, and then click the Software button.
Step 2 Verify that the protect software displays the release you upgraded from.
Step 3 Click the Revert button. This action activates the protect software and restores the database from the previous load. A dialog box asks you to confirm the choice.
Step 4 Click OK. This begins the reversion and drops the connection to the node.
Step 5 Wait until the software reversion finishes before continuing.
Note The system reboot might take up to 30 minutes to complete.
Step 6 Wait one minute before reverting another node.
Step 7 After reverting all of 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-U485 Delete Cached JAR Files" task.
Step 9 Return to your originating procedure (NTP).
DLP-U489 Manually Restore the Database
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
|
U488 Revert to Protect Load
U486 Remove the MS-SPRing Lockout (if required)
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Caution Do not perform these steps unless the software revert failed.
Caution This process is service affecting and should be performed during a maintenance window.
Step 1 In CTC node view, click the Maintenance tab, and 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 choose Open.
The database is restored and the TCC2/TCC2P cards reboot.
Step 4 When the TCC2/TCC2P cards have rebooted, log back 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 Table 4 "Manually Recorded Data" in the "U447 Back Up the ONS 15454 SDH Software Database" procedure for more information.
Step 6 Return to your originating procedure (NTP).
NTP-U451 Upgrade to ONS 15454 SDH Software R9.1 Using TL1
Note This procedure assumes you are upgrading using Release 6.x TL1 syntax. TL1 commands issued prior to software activation to Software R9.1 will vary in syntax depending on the release you are actually upgrading from. To ensure that your syntax for each command is correct, use the TL1 syntax supplied in the Cisco ONS SDH TL1 Command Guide for your particular release when issuing the following commands:
•ACT-USER
•COPY-RFILE
•REPT EVT FXFR
•OPR-PROTNSW-<OCN_TYPE>
•RTRV-COND-ALL
•RTRV-ALM-ALL
Note To perform an R9.1 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 FTP server has an IP address of 10.1.1.1.
•- The FTP server is running on the standard FTP port.
•- The software package is called "15454SDH-0xxx-xxxx-xxxx.pkg".
Note Software provisioning will be lost when upgrading from R8.0 or R8.5.x to R9.1 if path protection circuit of type UPSR_DRI or with type=2waydc is created on ADM-10G card. Ensure that there are no path protection circuit of type UPSR_DRI or with type=2waydc created on ADM-10G card before upgrading to R9.1.
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 2361 on the server.
The software PKG file in the preceding example is located in the home directory of the FTP server. If the software PKG file is not in the home directory on the FTP server, insert the directory path where the software package file 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 SDH node. Select the IP address for the node, using port 3083 or 2361.
Step 2 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 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).
Step 4 Select 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 5 Type the COPY-RFILE command 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-RFILE command 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.
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 (optional).
•<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 6 Repeat Step 5 for all nodes to be upgraded.
Step 7 Look for the REPT EVT FXFR message in the TL1 window. REPT EVT FXFR is an autonomous message used to report the start, completion, and completed percentage status of the software download. REPT EVT FXFR also reports any failure during the software upgrade, including invalid package, invalid path, invalid user ID/password, and loss of network connection. The format of the message is:
"<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 8 Complete "U446 Preparation for Upgrading to Release 9.1" procedure for each node to be upgraded.
Step 9 Complete "U447 Back Up the ONS 15454 SDH Software Database" procedure for each node to be upgraded.
Step 10 (MS-SPRing nodes only) The database must be backed up prior to locking the BLSR. See "U447 Back Up the ONS 15454 SDH Software Database" procedure for details.
Step 11 Lock out each MS-SPRing span on each node being upgraded using the following command.
OPR-PROTNSW-<STMN_TYPE>:[<TID>]:<AID>:<CTAG>::<SC>,[<SWITCHTYPE>][:<DIRN>];
where:
•<TID> is the target identifier (optional).
•<AID> identifies the facility in the node to which the switch request is directed.
•<CTAG> is the correlation tag that correlates command and response messages
•<SC> is the switch command that is to be initiated on the paths.
•<SWITCHTYPE> is the MS-SPRing switch type.
•<DIRN> is the direction of transmission in which switching is to be made and is relative to the SDH line or path identified by the AID. The default value is RCV and should be changed to BTH.
Note Some nodes might have more than one MS-SPRing. If this is the case, all MS-SPRing spans on all nodes being upgraded need to be backed up and then locked out. Nodes that are not being upgraded do not need to have the MS-SPRing spans locked out. You must be aware of each span that is part of an MS-SPRing to make sure all necessary spans are locked out.
Note MS-SPRing lockouts must remain in place until the upgrade is complete for all nodes.
Note Ignore any Default K alarms that occur on the protect STS time slots during the lockout.
Note Certain Multiservice Switching Platform (MSSP) related alarms might be raised following activation of the first node in the ring. The following alarms, if raised, are normal, and should not cause concern. They clear upon completion of the upgrade, after all nodes have been activated: MSSP-OOSYNC (MN); RING-MISMATCH (MJ); APSCDFLTK (MN); MSSP-RESYNC (NA).
Step 12 Verify that all necessary MS-SPRing spans on each node being upgraded have been locked out using the following command:
RTRV-PROTNSW-<STMN_TYPE>:[<TID>]:<AID>:<CTAG>[::::];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node. <AID> must not be null.
•<CTAG> is the correlation tag that correlates command and response messages (optional).
Step 13 Verify that there are no outstanding alarms or conditions on each node using the following commands:
RTRV-COND-ALL:[<TID>]:[<AID>]:<CTAG>::[<TYPEREQ>][,,,];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node. <AID> must not be null.
•<CTAG> is the correlation tag that correlates command and response messages (optional).
•<TYPEREQ> is the type of condition to be retrieved. A null value is equivalent to ALL.
RTRV-ALM-ALL:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],[<CONDITION>],[<SRVEFF>][,,,];
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node. <AID> 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, you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully.
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.
•<CTAG> is the correlation tag that correlates command and response messages.
•<MEM_SW_TYPE> indicates a memory switch action during the software upgrade, either:
–MEM_SW_TYPE is ACT to activate.
–MEM_SW_TYPE is CANC to cancel the activation.
If the command is successful, the appropriate flash is selected and the TCC2/TCC2P card reboots.
The following occurs:
•Each card in the node reboots, beginning with the standby TCC2 or TCC2P card. When the standby TCC2/TCC2P card reboots, it signals to the active TCC2/TCC2P card that it is ready to take over. When the active TCC2/TCC2P receives this signal, it resets itself, and the standby TCC2/TCC2P takes over and transitions to active. The pre-upgrade version of the TCC2/TCC2P card is now the standby TCC2/TCC2P.
•While the second TCC2/TCC2P is rebooting, the stand by cross-connect card (SONET/SDH only) reboots, and then the active cross-connect card (SONET/SDH only) reboots. Next, the E-Series Ethernet cards reset simultaneously.
•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 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 15 Perform Step 14 for each node that will be upgraded.
Note You might have to log into each node again to activate the software.
Step 16 After all nodes have been activated, log in using CTC or Telnet and verify there are no outstanding alarms.
Step 17 Remove all MS-SPRing lockouts using the following TL1 command:
RLS-PROTNSW-<STMN_TYPE>:[<TID>]:<AID>:<CTAG>[::<DIRECTION>];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node. <AID> must not be null.
•<CTAG> is the correlation tag that correlates command and response messages (optional).
•<DIRN> is the direction of transmission (transmit or receive). The possible values are RCV—Receive direction only (default).
–TRMT—Transmit direction only.
–BTH—Both transmit and receive directions.
For example:
RLS-PROTNSW-STM16:PETALUMA:FAC-6-1:209::BTH;
Step 18 To back up the database for the Working software load, see the "U447 Back Up the ONS 15454 SDH Software Database" procedure.
Stop. You have completed this procedure.
Related Documentation
•Release Notes for the Cisco ONS 15454 SDH Release 9.1
•Cisco ONS 15454 SDH Procedure Guide
Provides installation, turn-up, test, and maintenance procedures for SDH networks
•Cisco ONS 15454 SDH Reference Manual
Provides technical reference information for ONS 15454 SDH cards, nodes, and networks
•Cisco ONS 15454 DWDM Procedure Guide
Provides installation, turn-up, test, and maintenance procedures for DWDM networks
•Cisco ONS 15454 DWDM Reference Manual
Provides technical reference information for DWDM cards, nodes, and networks
•Cisco ONS 15454 SDH Troubleshooting Guide
Provides a list of ONS 15454 SDH alarms, errors, and transient conditions, as well as alarm and general troubleshooting procedures
•Cisco ONS 15454 DWDM Troubleshooting Guide
Provides a list of DWDM alarms, errors, and transient conditions, as well as alarm and general troubleshooting procedures
•Cisco ONS SDH TL1 Command Guide
Provides a full TL1 command and autonomous message set including parameters, access identifiers (AIDs), conditions, and modifiers for the Cisco ONS 15454 SDH
•Cisco ONS SDH TL1 Reference Guide
Provides general information, procedures, and errors for TL1 in the Cisco ONS 15454 SDH
•Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide
Provides software features for all Ethernet cards and configuration information for Cisco IOS on ML-Series cards.
Obtaining Optical Networking Information
This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section.
Where to Find Safety and Warning Information
For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.
Cisco Optical Networking Product Documentation CD-ROM
Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
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.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0910R)
© 2009 Cisco Systems, Inc. All rights reserved.
