Table Of Contents
Upgrading Cisco ONS 15454 SDH to Release 6.0
Contents
Before You Begin
Errorless Upgrades and Exceptions
XC-VXC-10G
XC-VXL-10G/XC-VXL-2.5G
Document Procedures
NTP-U122 Prepare for Upgrade to Release 6.0
DLP-U192 Verify CTC PC or UNIX Workstation Requirements
DLP-U193 Verify Common Control Cards
NTP-U123 Back Up the Software Database
NTP-U124 Upgrade to Release 6.0
DLP-U194 Download Release 6.0 Software
DLP-U195 Perform an MS-SPRing Lockout
DLP-U196 Activate the New Load
DLP-U112 Delete Cached JAR Files
DLP-U197 Remove the MS-SPRing Lockout
DLP-U79 Set the Date and Time
NTP-U110 Install Public-Key Security Certificate
NTP-U125 Revert to Previous Software Load and Database
DLP-U198 Revert to Protect Load
DLP-U177 Manually Restore the Database
NTP-U126 Upgrade to Release 6.0 Using TL1
Related Documentation
Release-Specific Documents
Platform-Specific Documents
Obtaining Documentation
Cisco.com
Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Upgrading Cisco ONS 15454 SDH to Release 6.0
This document explains how to upgrade Cisco ONS 15454 SDH Cisco Transport Controller (CTC) software from Release 4.x or 5.x to Release 6.0 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 BITS timing.
Contents
•Before You Begin
•U122 Prepare for Upgrade to Release 6.0
•U123 Back Up the Software Database
•U124 Upgrade to Release 6.0
•U110 Install Public-Key Security Certificate
•U125 Revert to Previous Software Load and Database
•U126 Upgrade to Release 6.0 Using TL1
•Related Documentation
•Obtaining Documentation
•Documentation Feedback
•Cisco Product Security Overview
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
Before You Begin
Before beginning, write down the following information about your site; the data will be useful during and after the upgrade: Date, Street Address, Site Phone Number, and Dial Up Number.
Caution Read all procedures before you begin the upgrade.
Caution This upgrade is supported only for Software Releases 4.0.x, 4.1.x, 4.5, 4.6.x, 4.7, and 5.x. If you wish to upgrade from an earlier software release, you must contact Cisco Technical Assistance Center (Cisco TAC). For more information, see the
"Obtaining Technical Assistance" section.
Note In releases prior to Release 4.6 you could independently set proxy server gateway settings; however, with Release 4.6 and later, this is no longer the case. To retain the integrity of existing network configurations, settings made in a previous release are not changed on an upgrade to Release 4.6 or later. Current settings are displayed in CTC (whether they were inherited from an upgrade, or they were set using the current GUI).
Errorless Upgrades and Exceptions
The following table defines where errorless upgrades are expected for Release 6.0, and where exceptions can occur. Please review the table.
Note Upgrades from releases prior to 4.6 are not expected to be errorless.
Note Upgrades for DWDM configurations are expected to be errorless.
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.
XC-VXC-10G
This table applies to nodes equipped with XC-VXC-10G cards.
Table 0-1 XC-VXC-10G
Card Type
|
Expected Traffic Effect
|
E1
|
Errorless
|
E3
|
Errorless
|
E1-42
|
Errorless
|
DS3I
|
Errorless
|
STMn
|
Errorless
|
MRC-12
|
Errorless
|
ML-series Ethernet
|
Traffic hits 3-8 minutes (approximately)
|
G-series Ethernet
|
Errorless
|
XC-VXL-10G/XC-VXL-2.5G
This table applies to nodes equipped with XC-VXL-10G or XC-VXL-2.5G cards.
Table 0-2 XC-VXL-10G/XC-VXL-2.5G
Card Type
|
Expected Traffic Effect
|
E1
|
Errorless
|
E3
|
Errorless
|
E1-42
|
Errorless
|
DS3I
|
Errorless
|
STMn
|
Errorless
|
ML-series Ethernet
|
Traffic hits 3-8 minutes (approximately)
|
G-series Ethernet
|
Errorless
|
Document Procedures
Procedures in this document are to be performed in consecutive order unless otherwise noted. In general, you are not done with a procedure until you have completed it for each node you are upgrading, and you are not done with the upgrade until you have completed each procedure that applies to your network. If you are new to upgrading the ONS 15454 SDH, you might wish to check off each procedure on your printed copy of this document as you complete it.
Each non-trouble procedure (NTP) is a list of steps designed to accomplish a specific procedure. Follow the steps until the procedure is complete. If you need more detailed instructions, refer to the detail-level procedure (DLP) specified in the procedure steps. Throughout this guide, NTPs are referred to as "procedures" and DLPs are termed "tasks." Every reference to a procedure includes its NTP number, and every reference to a task includes its DLP number.
The DLP (task) supplies additional task details to support the NTP. The DLP lists numbered steps that lead you through completion of a task. Some steps require that equipment indications be checked for verification. When the proper response is not obtained, a trouble clearing reference is provided. This section lists the document procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
1. U122 Prepare for Upgrade to Release 6.0—This section contains critical information and tasks that you must read and complete before beginning the upgrade process.
2. U123 Back Up the 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.
3. U124 Upgrade to Release 6.0—You must complete this entire procedure before the upgrade is finished.
4. U110 Install Public-Key Security Certificate—You must complete this procedure to be able to run ONS 15454 SDH Software R6.0.
5. U125 Revert to Previous Software Load and Database—Complete this procedure only if you need to return to the software load you were running before activating the Release 6.0 software.
6. U126 Upgrade to Release 6.0 Using TL1—Complete this procedure only if you want to upgrade to Software R6.0 using TL1.
NTP-U122 Prepare for Upgrade to Release 6.0
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 Release 6.0 software
|
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 6.0.
Step 2 Log into the node that you will upgrade. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 3 Complete the "DLP-U192 Verify CTC PC or UNIX Workstation Requirements" task.
Step 4 If you have multiple ONS 15454 SDH nodes configured in the same IP subnet, ensure that only one is connected to a router. Otherwise, the remaining nodes might be unreachable. Refer to the Cisco ONS 15454 SDH Reference Manual for LAN-connection suggestions.
Step 5 Complete the "DLP-U193 Verify Common Control Cards" task.
Step 6 When you have completed the tasks for this section, proceed with the "U123 Back Up the Software Database" procedure.
Stop. You have completed this procedure.
DLP-U192 Verify CTC PC or UNIX 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 R6.0.
|
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 either one of the following:
•IBM-compatible PC with a Pentium III/700 or faster processor, CD-ROM drive, a minimum of 384 MB RAM and 190 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)
•UNIX workstation with Solaris Versions 8 or 9, on an UltraSPARC or faster processor, with a minimum of 384 MB RAM and a minimum of 190 MB of available hard drive space
Step 2 Ensure that your web browser software is one of the following:
•Netscape Navigator 7.x or higher
•Internet Explorer 6.x or higher
Note Cisco recommends you use either Internet Explorer 6.x or Netscape 7.x for Windows workstations running Release 6.0. However, if you upgrade to Netscape 7 or JRE 1.4.2 and you still need to launch CTC directly from nodes running software prior to Release 4.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 13) in this case.
Step 3 Verify that the Java Version installed on your computer is:
–Java Runtime Environment (JRE) 1.4.2, and Java Plug-in 1.4.2
Tip You can check the JRE version in your browser window after entering the node IP address in the URL window under Java Version.
•The Java Policy file is installed on your computer.
Note For important information on CTC backward compatibility affected by your choice of JRE versions, see the Readme.txt or Readme.html file on the software CD.
Note To install JRE 1.4.2, the Java Policy file, or the Release 6.0 online help, refer to the installation instructions in the Cisco ONS 15454 SDH Procedure Guide, or Cisco ONS 15454 DWDM Installation and Operations Guide.
Step 4 Return to your originating procedure (NTP).
DLP-U193 Verify Common Control Cards
Purpose
|
This task verifies that two TCC2 or TCC2P cards and two XC-VXL-10G, XC-VXL-2.5G, or XC-VXC-10G cards (SONET/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 Dense wavelength division multiplexing (DWDM) nodes need only TCC2/TCC2P cards installed during the upgrade.
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, or XC-VXC-10G cards (as needed for SONET or SDH operation) are in Slots 8 and 10. Software R6.0 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-U123 Back Up the Software Database
Purpose
|
This procedure preserves all configuration data for your network before performing the upgrade.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U122 Prepare for Upgrade to Release 6.0
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Maintenance or higher
|
Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide. If you are already logged in, continue with Step 2.
Step 2 In the node (default) view, click the Maintenance > Database tabs.
Step 3 Click Backup.
Step 4 Save the database on the workstation's hard drive or on network storage. Use an appropriate file name with the file extension .db. (Cisco recommends that you use the IP address of the node and the date, for example 1010120192061103.db.)
Step 5 Click Save. A message appears indicating that the backup is complete.
Step 6 Click OK.
Step 7 Repeat Steps 1 through 6 for each node in the network.
Step 8 (Optional) Cisco recommends that you manually log critical information by either writing it down or printing screens where applicable. Use the following table to determine the information you should log; complete the table (or your own version) for every node in the network.
Note When upgrading from Release 4.0.x alarm and audit logs will be deleted due to changes in the alarm log structure.
Table 3 Manually Recorded Data
Item
|
Record Data Here (If Applicable)
|
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, or XC-VXC-10G (as needed for SONET or SDH configurations).
|
Slot 8 or Slot 10 (circle one)
|
Network information; do a print screen from the Provisioning tab in the network view.
|
|
Current configuration (MS-SPRing2 , 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-U124 Upgrade to Release 6.0
Purpose
|
This procedure upgrades your CTC software to Software R6.0.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U123 Back Up the Software Database
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Step 1 Insert the Release 6.0 software 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 Setup Wizard. You can use the setup wizard to install components or click Cancel to continue with the upgrade.
Caution Do not perform maintenance or provisioning activities during the activation task.
Step 2 Complete the "DLP-U194 Download Release 6.0 Software" task for all nodes (or groups of eight or less nodes) you are upgrading.
Step 3 Complete the "DLP-U195 Perform an MS-SPRing Lockout" task (MS-SPRing nodes only).
Step 4 Complete the "DLP-U196 Activate the New Load" task for all nodes you are upgrading.
Note You can only activate one node at a time; however, you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully.
Step 5 If necessary, complete the "DLP-U112 Delete Cached JAR Files" task.
Step 6 (Optional) If you wish to ensure that a software revert to the previous software release will no longer be possible, complete the "DLP-U194 Download Release 6.0 Software" task for all nodes, or groups of nodes you are upgrading a second time.
Step 7 Complete the "DLP-U197 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 Complete the "DLP-U79 Set the Date and Time" task (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 Release 6.0 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 R6.0, proceed with the "U125 Revert to Previous Software Load and Database" procedure.
Step 11 To back up the Release 6.0 database for the Working software load, see , see "U123 Back Up the Software Database" procedure in order to preserve the database for the Release 6.0 software
Stop. You have completed this procedure.
DLP-U194 Download Release 6.0 Software
Purpose
|
This task downloads Software R6.0 to the ONS 15454 SDH nodes prior to activation.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U123 Back Up the 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 "U126 Upgrade to Release 6.0 Using TL1" procedure.
Step 1 From the View menu, choose Go to Network View.
Step 2 Verify that the alarm filter is not on:
a. Click the Alarms tab.
b. Click the Filter tool at the lower-right side of the bottom toolbar. Alarm filtering is enabled if the tool is depressed (selected) and disabled if the tool is raised (not selected).
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 SWFTDWN alarm indicates that the software download is taking place. The alarm is normal and clears when the download is complete.
Step 4 Return to node view and click the Maintenance > Software tabs.
Step 5 Click Download. The Download Selection dialog box appears.
Step 6 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 7 Open the Cisco15454SDH folder.
Step 8 Select the file with the .pkg extension and click Open.
Step 9 In the list of compatible nodes, select the check boxes for all nodes you are downloading the software to.
Note Cisco advises that you limit concurrent software downloads on an SDCC 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 10 Click OK. The Download Status column monitors the progress of the download.
Note The software download process can take typically less than10 minutes per node.
Step 11 Return to your originating procedure (NTP).
DLP-U195 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
|
U123 Back Up the Software Database
|
Required/As Needed
|
Required for MS-SPRing only
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Note During activation, MS-SPRing spans are not protected. You must leave the MS-SPRing in the lockout state until you have finished activating all nodes in the ring, but then you must be sure to remove the lockout after you are finished activating.
Note To 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 > MS-SPRing tabs.
Step 2 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, MRC-12), perform the following steps:
a. Next to the trunk card row, click the East Switch column to show the pull-down menu.
b. From the menu options, choose Lockout Span.
c. Click Apply.
d. In the same row, click the West Switch column to show the pull-down menu.
e. From the menu options, choose Lockout Span.
f. Click Apply.
Note Ignore any Default K alarms that occur on the protect VC4 timeslots 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 3 Return to your originating procedure (NTP).
DLP-U196 Activate the New Load
Purpose
|
This task activates Software R6.0 in each node in the network.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U194 Download Release 6.0 Software
U195 Perform an MS-SPRing Lockout (if required)
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
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, Maintenance > Protection tab select each of the listed protection groups, then view the Active/Standby status of each card in the Selected Group area.
Note Cisco recommends you run the optional Cache Loader pre-caching utility in Step 13 or the activation task. If you do not plan to run the pre-caching utility, Cisco recommends that the first node you activate be a LAN-connected node. This ensures that the new CTC JAR files download to your workstation as quickly as possible.
Note ML cards undergo a cold restart during an upgrade. The following alarms might be raised in conjunction with the ML cold restart. These should clear once the upgrade is complete.
On the ML port:
•LOA
•TPTFAIL
•VCG DOWN
On the paths traversed by the ML circuits:
•SD-P
•SF-P
•PDI-P
Step 1 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 2 Verify that the alarm filter is not on:
a. Click the Alarms tab.
b. Click the Filter tool at the lower-right side of the bottom toolbar.
Alarm filtering is enabled if the tool is depressed (selected) and disabled if the tool is raised (not selected).
Step 3 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding alarms before proceeding.
Step 4 Click the Maintenance > Software tabs.
Step 5 Verify that the protect version is 6.0.
Step 6 Click Activate. The Activate dialog box appears with a warning message.
Step 7 Click Yes to proceed with the activation. The "Activation Successful" message appears when the software is successfully activated.
Note When you click Yes, CTC loses connection to the node and displays the network view.
Step 8 Click OK in the message box.
Step 9 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 comes back up, it signals to the active TCC2/TCC2P 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 originally active TCC2/TCC2P then comes back up as the standby TCC2/TCC2P.
•While the second TCC2/TCC2P is rebooting, the cross-connect card (SONET/SDH only) in Slot 8 reboots, and then the cross-connect card (SONET/SDH only) in Slot 10 reboots.
•Next, the E-series Ethernet cards reset simultaneously.
•Next, the traffic cards, G-series Ethernet cards, CE-series Ethernet cards, and ML-series Ethernet cards boot consecutively from left to right, first standby, then working, for each card pair.
•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 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 10 In CTC, choose File > Exit.
Step 11 In your browser window, click Delete CTC Cache.
Note You must ensure that CTC is closed before clicking the Delete CTC Cache button. CTC behavior is unreliable if the button is clicked while the software is still running.
Note It might also be necessary to delete cached files from your browser's directory or from the temp directory on your MS Windows workstation. If you have trouble reconnecting to CTC, complete the "DLP-U112 Delete Cached JAR Files" task.
Step 12 Close your browser and then reopen it.
Step 13 (Optional) Run the Cache Loader pre-caching utility, which can improve your speed logging back into CTC after an upgrade, and which is required to log into nodes running releases prior to Release 4.6. Perform the following steps to run the Cache Loader.
a. Load the Release 6.0 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 opens.
c. Click Next. The setup options dialog box opens.
d. Choose Custom, and click Next. The custom options dialog box opens.
e. Select Cisco Transport Controller, and CTC JAR files (deselect any other preselected options), then click Next. A confirmation box opens.
f. Click Next 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 14 Reconnect to CTC using the IP address from Step 1. The new CTC applet for Software R6.0 uploads. During this logon, type the user name CISCO15. A password is not required.
Note Steps 10 through 14 are only necessary after upgrading the first node in a network because cached files only need to be removed from your workstation once. For the remaining nodes, you will still be disconnected and removed to the network view during the node reboot, but after the reboot is complete, CTC will restore connectivity to the node.
Step 15 Return to your originating procedure (NTP).
DLP-U112 Delete Cached JAR Files
Purpose
|
This task deletes cached 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 > Advanced > Cache.
b. Click Clear Memory Cache.
c. Click OK.
d. Click Clear Disk Cache.
e. Click OK twice.
In Microsoft Internet Explorer:
a. Choose Tools > Internet Options > General.
b. Choose Delete Files.
c. Select the Delete all offline content check box.
d. 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 Delete cached files from your workstation (Windows systems only).
a. In your Windows start menu, choose Settings > Control Panel > System > Advanced.
b. Click Environment Variables. 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. Select 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-U197 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
|
U196 Activate the New Load
|
Required/As Needed
|
Required for MS-SPRing
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Step 1 In CTC node view, click the Maintenance > MS-SPRing tabs.
Step 2 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, MRC-12), perform the following steps:
a. Next to the trunk card row, click the West Switch column to show the pull-down 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 pull-down menu.
e. From the menu options, choose Clear.
f. Click Apply to activate the command.
Step 3 Repeat this task as many times as necessary to remove all MS-SPRing span lockouts on the upgrade nodes.
Step 4 Return to your originating procedure (NTP).
DLP-U79 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 Apply.
Step 3 Repeat Steps 1 and 2 for each remaining node.
Step 4 Return to your originating procedure (NTP).
NTP-U110 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 R6.0, proceed with the "U125 Revert to Previous Software Load and Database" procedure.
Stop. You have completed this procedure.
NTP-U125 Revert 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 R6.0, you should have backed up the existing database at all nodes in the network (this is part of the "U123 Back Up the 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 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 Releases prior to Release 5.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, continue with Step 2.
Step 2 Complete the "DLP-U195 Perform an MS-SPRing Lockout" task (MS-SPRing only).
Step 3 Complete the "DLP-U198 Revert to Protect Load" task.
Step 4 Complete the "DLP-U197 Remove the MS-SPRing Lockout" task (MS-SPRing only).
Step 5 If the software revert to your previous release failed, complete the "DLP-U177 Manually Restore the Database" task.
Stop. You have completed this procedure.
DLP-U198 Revert to Protect Load
Note To perform a supported (non-service-affecting) revert from Software R6.0, the release you want to revert to must have been working at the time you activated to Software R6.0 on that node. Also, a supported revert automatically restores the node configuration at the time of the previous activation. Thus, any configuration changes made after activation will be lost when you revert the software. The exception to this is when you have downloaded Release 6.0 a second time, to ensure that no actual revert to a previous load can take place. In this latter case, the revert will occur, but will not be traffic affecting and will not change you database.
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, Maintenance > Protection tab select each of the listed protection groups, then view the Active/Standby status of each card in the Selected Group area.
Step 1 From the node view, click the Maintenance > Software tabs.
Step 2 Verify that the protect software displays the release you upgraded from.
Step 3 Click Revert. Revert 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 revert and drops the connection to the node.
Step 5 Wait until the software revert finishes before continuing.
Note The system reboot might take up to 30 minutes to complete.
Step 6 Close your Netscape or Internet Explorer browser.
Step 7 Wait one minute before restoring another node.
Note After you upgrade to JRE 1.4.2, you cannot log into an ONS 15454, ONS 15454 SDH, or ONS 15327 node until you reconfigure the Java Plug-in to use JRE 1.3.1. If you are reverting to a release that uses JRE 1.3.1_02 and you retained JRE 1.3.1_02 during the upgrade, you do not need to do anything.
Step 8 Perform the "DLP-U112 Delete Cached JAR Files" task.
Step 9 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 10 Return to your originating procedure (NTP).
DLP-U177 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
|
U198 Revert to Protect Load
U197 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 the CTC node view, click the Maintenance > Database tabs.
Step 2 Click Restore. The Open dialog box appears.
Step 3 Select the previously saved file and choose Open.
The database id 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.
Step 6 Return to your originating procedure (NTP).
NTP-U126 Upgrade to Release 6.0 Using TL1
Note To perform a download using TL1 you must first have an FTP server running on you workstation in order to establish the required FTP session. For example, if your FTP server is set up with a login and password of FTPUSER1 and FTPUSERPASSWORD1, and if the FTP server has an IP address of 10.1.1.1 and is running on the standard FTP port, where the software package is called "15454-03xx-A04K-1405.pkg" the command will be:
COPY-RFILE::RFILE-PKG:100::TYPE=SWDL,
SRC="ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1/15454-03xx-A04K-1405.pkg";
Step 1 From the PC connected to the ONS 15454 SDH, start Netscape or Internet Explorer.
Step 2 Enter the ONS 15454 SDH IP address of the node you want to communicate with in the Netscape or Internet Explorer Web address (URL) field.
Step 3 In CTC, the IP address at the CTC window should match the IP address you entered in Step 2.
Step 4 In CTC, click Tools > Open TL1 Connection.
Step 5 Choose the node that you want to communicate with from the Select Node dialog box.
Step 6 Click OK.
A TL1 interface window appears. There are three subwindows in the TL1 interface window: Request history, Message log, and TL1 request. Type commands in the TL1 request window. You will see responses in the Message log window. The Request history window allows you to recall previous commands by clicking them.
Step 7 Verify that the Connect button is selected (grayed out).
Step 8 Type the Activate User command in the TL1 request window to open a TL1 session:
