Table Of Contents
Upgrading the Cisco ONS 15310-CL to Release 8.0
Contents
Before You Begin
Document Procedures
NTP-U224 Prepare for Upgrade to Release 8.0
DLP-U337 Verify CTC Workstation Requirements
NTP-U225 Back Up the ONS 15310-CL Software Database
NTP-U226 Upgrade to the ONS 15310-CL Software R8.0
DLP-U338 Download the ONS 15310-CL Release 8.0 Software
DLP-U339 Activate the New ONS 15310-CL Software Load
DLP-U340 Delete Cached JAR Files
DLP-U341 Set the Date and Time
NTP-U227 Install Public-Key Security Certificate
NTP-U228 Revert to Previous Software Load and Database
DLP-U342 Revert to Protect Load
DLP-U343 Manually Restore the Database
NTP-U229 Upgrade to ONS 15310 Release 8.0 Using TL1
Related Documentation
Obtaining Documentation and Submitting a Service Request
Upgrading the Cisco ONS 15310-CL to Release 8.0
This document explains how to upgrade Cisco ONS 15310-CL Cisco Transport Controller (CTC) software from Software Release 7.2 to Software Release 8.0.
Contents
This document contains the following information:
•
Before You Begin
•Document Procedures
•U224 Prepare for Upgrade to Release 8.0
•U225 Back Up the ONS 15310-CL Software Database
•U226 Upgrade to the ONS 15310-CL Software R8.0
•U227 Install Public-Key Security Certificate
•U228 Revert to Previous Software Load and Database
•U229 Upgrade to ONS 15310 Release 8.0 Using TL1
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Before You Begin
Before beginning, write down the following information about your site; the data will be useful during and after the upgrade: date, street address, site phone number, and dialup number.
Caution Read all procedures before you begin the upgrade.
Caution This upgrade is supported only for Software R7.2 upgrading to Software R8.0.
Note Software R8.0 supports parallel upgrades for multiple nodes in a network. In a parallel upgrade you can still only activate one node at a time; however, you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully (wait five minutes from the time the SYSBOOT alarm is raised).
Caution When managing end-to-end circuits participating in an ML-series resilient packet ring RPR across multiple nodes involved in a parallel upgrade, all nodes participating in these circuits must have completed the activation before the end-to-end traffic will resume.
Document Procedures
Procedures in this document are to be performed in consecutive order unless otherwise noted. In general, you are not done with a procedure until you have completed it for each node you are upgrading, and you are not done with the upgrade until you have completed each procedure that applies to your network. If you are new to upgrading the ONS 15310-CL, you might want 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. U224 Prepare for Upgrade to Release 8.0—This section contains critical information and tasks that you must read and complete before beginning the upgrade process.
2. U225 Back Up the ONS 15310-CL 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. U226 Upgrade to the ONS 15310-CL Software R8.0—You must complete this entire procedure before the upgrade is finished.
4. U227 Install Public-Key Security Certificate—You must complete this procedure to be able to run ONS 15310-CL Software R8.0.
5. U228 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 Software R8.0.
6. U229 Upgrade to ONS 15310 Release 8.0 Using TL1—Complete this procedure only if you want to install Software R8.0 using Transaction Language 1 (TL1).
NTP-U224 Prepare for Upgrade to Release 8.0
Purpose
|
This procedure provides the critical information checks and tasks you must complete before beginning an upgrade.
|
Tools/Equipment
|
ONS 15310-CL nodes to upgrade
PC or UNIX workstation
Cisco ONS 15310-CL Software R8.0
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Superuser
|
Step 1 Read the Release Notes for Cisco ONS 15310-CL Release 8.0.
Step 2 Log into the node that you will upgrade. For detailed instructions, refer to the Cisco ONS 15300-CL and Cisco ONS 15310-MA Procedure Guide.
Step 3 Complete the "DLP-U337 Verify CTC Workstation Requirements" task.
Step 4 When you have completed the tasks for this section, proceed with the "NTP-U225 Back Up the ONS 15310-CL Software Database" procedure.
Stop. You have completed this procedure.
DLP-U337 Verify CTC Workstation Requirements
Purpose
|
This task verifies all PC or UNIX workstation hardware and software requirements. Before upgrading the workstation to run CTC Software R8.0, complete this task.
|
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 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 on Windows
•Internet Explorer 6.x or higher on Windows
•Mozilla 1.7 or higher on Solaris
Step 3 Verify that the following are installed on your computer:
–- Java Runtime Environment (JRE) 5.0
–- Java Plug-in 5.0
–- Java Policy file
Tip You can check the JRE version in your browser window after entering the node IP address in the URL window under Java Version.
Note For important information on CTC backward compatibility affected by your choice of JRE versions, see the online help, and refer to the installation instructions in the Cisco ONS 15300-CL and Cisco ONS 15310-MA Procedure Guide.
Step 4 Return to your originating procedure (NTP).
NTP-U225 Back Up the ONS 15310-CL Software Database
Purpose
|
This procedure preserves all configuration data for your network before performing the upgrade.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U224 Prepare for Upgrade to Release 8.0
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Maintenance or higher; or Superuser, if performing optional Step 2
|
Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15300-CL and Cisco ONS 15310-MA Procedure Guide. If you are already logged in, continue with Step 2.
Step 2 (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.
Table 1 Manually Recorded Data
Item
|
Record Applicable Data Here
|
IP address of the node.
|
|
Node name.
|
|
Timing settings.
|
|
Data communications channel (DCC) 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.
|
|
Do a print screen from the Provisioning tab in the network view.
|
|
Current configuration (linear, etc.); do print screens as needed.
|
|
Protection groups; 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.
|
|
Step 3 In CTC node view, click the Maintenance tab and then click the Database button.
Step 4 Click the Backup button. A Database Backup dialog box appears.
Step 5 In the Database Backup dialog box, click the Browse button, then navigate to a directory and type or select a database name using the IP address of the node to upgrade (such as 10101882010107.db).
Step 6 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 7 A message indicates the status of the backup. When the backup is complete, click the OK button to close the message dialog box.
Step 8 Repeat Steps 1 through 7 for each node in the network.
Stop. You have completed this procedure.
NTP-U226 Upgrade to the ONS 15310-CL Software R8.0
Purpose
|
This procedure upgrades your CTC software to Software R8.0.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U225 Back Up the ONS 15310-CL 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 Software R8.0 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 the Cancel button to continue with the upgrade.
Caution A traffic interruption of less than 50 ms on each circuit is possible during the activation task, with Ethernet traffic disruption possibly lasting up to several minutes on each circuit. Do not perform maintenance or provisioning activities during the activation task.
Caution When managing end-to-end circuits participating in a CL-series resilient packet ring (RPR) across multiple nodes involved in a parallel upgrade, all nodes participating in these circuits must have completed the activation before the end-to-end traffic will resume.
Step 2 Complete the "DLP-U338 Download the ONS 15310-CL Release 8.0 Software" task for all nodes (or groups of eight or less nodes) you are upgrading.
Step 3 Complete the "DLP-U339 Activate the New ONS 15310-CL Software 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 (wait five minutes from the time the SYSBOOT alarm is raised).
Step 4 (Optional) If you wish to ensure that a software revert to the previous software release will no longer be possible, complete the "DLP-U338 Download the ONS 15310-CL Release 8.0 Software" task for all nodes, or groups of nodes you are upgrading a second time.
Caution Downloading Software R8.0 a second time following activation prevents reversion to the previous software version.
Step 5 Complete the "DLP-U341 Set the Date and Time" task (any nodes not using SNTP).
Step 6 If you need to return to the software and database you had before activating Software R8.0, proceed with the "NTP-U228 Revert to Previous Software Load and Database" procedure.
Step 7 To back up the Software R8.0 database for the working software load, see "NTP-U225 Back Up the ONS 15310-CL Software Database" procedure to preserve the database for Software R8.0.
Stop. You have completed this procedure.
DLP-U338 Download the ONS 15310-CL Release 8.0 Software
Purpose
|
This task downloads Software R8.0 to ONS 15310-CL nodes prior to activation.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U225 Back Up the ONS 15310-CL 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 15310-CTX-CL card has two flash RAMs. An upgrade downloads the software to the backup RAM on the 15310-CTX-CL card. The download task does not affect traffic because the active software continues to run at the primary RAM location; therefore, you can download the software at any time.
Step 1 If CTC is not already running, start CTC, using the IP address of the ONS 15310-CL node.
Step 2 In CTC node view, click the Alarms tab.
Step 3 Verify that the alarm filter is not on. Click the Filter button at the lower-left of the window.
Step 4 The Alarm Filter dialog box opens. Click to deselect any selections in the Show Severity section of the General tab.
Step 5 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding critical alarms before proceeding. If necessary, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide.
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 6 Return to node view and click the Maintenance tab and then click the Software button.
Step 7 Click the Download button.
The Download Selection dialog box opens.
Step 8 Click the Browse button to locate the software upgrade PKG package files.
Step 9 Open the Cisco 15310-CL folder.
Step 10 Choose 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 on a Section data communications channel (SDCC) to eight nodes at once, using the central node to complete the download. 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 OK. The Download Status column monitors the progress of the download.
Note The software download process can take up to 30 minutes per node, though typically under ten minutes.
Step 13 Return to your originating procedure (NTP).
DLP-U339 Activate the New ONS 15310-CL Software Load
Purpose
|
This task activates Software R8.0 in each node in the network.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U338 Download the ONS 15310-CL Release 8.0 Software
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote (but in the presence of the workstation)
|
Security Level
|
Superuser
|
Note Cisco recommends you run the optional Cache Loader pre-caching utility in Step 16 of the activation task. If you do not plan to run the pre-caching utility, Cisco recommends that the first node you activate be a LAN-connected node. This ensures that the new CTC JAR files download to your workstation as quickly as possible.
Step 1 If CTC is not already running, start CTC, using the IP address of the ONS 15310-CL node.
Step 2 Record the IP address of the node. The IP address is on the upper left corner of the CTC window.
Step 3 In node view, click the Alarms tab.
Step 4 Verify that the alarm filter is not on. Click the Filter button at the lower-left of the window.
Step 5 The Alarm Filter dialog box appears. Click to deselect any selections in the Show Severity section of the General tab.
Step 6 On the Alarms tab, check all nodes for existing alarms. Resolve any outstanding critical alarms before proceeding. If necessary, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide.
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 7 Click the Maintenance tab and then click the Software button.
Step 8 Verify that the software version in the Protect Version column is Software R8.0 (the release you are upgrading to).
Step 9 Click the Activate button. The Activate dialog box appears with a warning message.
Step 10 Click Yes to proceed with the activation. The Activation Successful message appears when the software is successfully activated. Click OK in the message dialog box.
Note When you click Yes, CTC will lose connection to the node and will display the network view.
Step 11 After activating the node, the software upgrade reboot occurs as follows:
•Each card in the node resets, beginning with the expansion card. The 15310-CTX-CL card will then reset and come back up.
•When the 15310-CTX-CL is finished, the Ethernet card comes back up, followed by reset of the electrical and optical ports.
•The process can take up to 8 minutes, This process is service affecting, so Cisco recommends that you activate the new load during a maintenance window. TDM traffic can endure a hit of up to 50 ms. Expect Ethernet traffic to remain down from the time the expansion card resets, until all cards have finished resetting and come back up (this will take 3 to 8 minutes).
After the common control cards finish resetting and all associated alarms clear, you can safely proceed to the next step. (If you are upgrading remotely and cannot see the nodes, wait for 5 minutes for the process to complete, then check to ensure that related alarms have cleared before proceeding.)
Note During the software upgrade, a reset alarm is raised on all the cards. When upgrading from release 6.0.x, 6.1.x, 6.2.x, 7.0, 7.2, 7.2.x to 8.x, a MANRESET alarm is raised on Standby TCC cards and an AUTORESET alarm in all the other cards. However, from release 8.0, the MANRESET alarm is not raised and the AUTORESET alarm is raised on all the cards.
Caution The upgrade process is service affecting, so Cisco recommends that you activate the new load during a maintenance window. TDM traffic can endure a hit of up to 50 ms. Ethernet traffic might remain down from the time the 15310-CTX-CL cards switch to the time all Ethernet cards have finished resetting.
Step 12 In CTC, choose File > Exit.
Step 13 In your browser window, click the Delete CTC Cache button. A confirmation dialog box appears.
Step 14 Click the Yes button to confirm.
Note You must ensure that CTC is closed before clicking the Delete CTC Cache button. CTC behavior will be unreliable if the button is clicked while the software is still running. It might also be necessary to delete cached files from your browser's directory, or from the TEMP directory on your Microsoft Windows workstation. If you have trouble reconnecting to CTC, complete the "DLP-U340 Delete Cached JAR Files" task.
Step 15 Close your browser and then reopen it.
Note Step 16 is necessary only 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 16 (Optional) Run the Cache Loader pre-caching utility, which can improve your speed logging back into CTC after an upgrade. Perform the following steps to run the Cache Loader.
a. Load the Software R8.0 CD into your CD-ROM drive. If the directory of the CD does not open automatically, open it.
b. Double-click the setup.exe file to run the Installation Wizard. The CTC Installation Wizard dialog box opens.
c. Click the Next button. The setup options dialog box opens.
d. Choose Custom, and click the Next button. The Custom Options dialog box opens.
e. Select Cisco Transport Controller, and CTC JAR Files (deselect any other preselected options), then click the Next button. A confirmation dialog box opens.
f. Click the Next button again. The CTC Cache Loader pre-caches the JAR files to your workstation, displaying a progress status dialog box.
g. When the utility finishes, click OK, and then, in the wizard, click the Finish button.
Step 17 Reconnect to CTC using the IP address from Step 2. The new CTC applet for Software R8.0 uploads. During this login, enter your Superuser user ID and password.
Step 18 Return to your originating procedure (NTP).
Note When you revert the software to an earlier version, a reset alarm is raised on all the cards. When you revert from release 8.x or later to 6.0.x, 6.1.x, 6.2.x, 7.0, 7.2, or to 7.2.x, an AUTORESET alarm is raised on the Standby TCC cards and a MANRESET alarm in all other cards. However, in releases earlier to 8.0, the AUTORESET alarm is not raised and the MANRESET alarm is raised on all the cards.
DLP-U340 Delete Cached JAR Files
Purpose
|
This task manually deletes cached JAR files from your browser and hard drive. When you upgrade or revert to a different CTC software load, you must reload CTC to your browser. Before you can reload CTC, you must ensure that previously cached files are cleared from your browser and hard drive.
|
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, and then click the Cache button.
b. Click the Clear Memory Cache button, and click OK.
c. Click Clear Disk Cache, and click OK twice.
In Microsoft Internet Explorer:
a. Choose Tools > Internet Options. The Internet Options dialog box appears.
b. Click the General tab, and then click the Delete Files button.
c. Click the Delete all offline content check box.
d. Click OK twice.
Step 2 Close your browser.
Note You will not be able to 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 (Windows systems only) Delete cached files from your workstation.
a. In your Windows Start menu, choose Control Panel > System and then click the Advanced tab.
b. Click the Environment Variables button. The resulting display will show 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 discovered path.
e. Select View > Details.
f. Click to 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-U341 Set the Date and Time
Purpose
|
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 tab and then click the General button.
Step 2 Set the correct date and time, then click the Apply button. Repeat Steps 1 and 2 for each remaining node.
Step 3 Return to your originating procedure (NTP).
NTP-U227 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 15310-CL software.
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Log into CTC.
Step 2 If the Java Plug-in Security Warning dialog box appears, choose one of the following options:
•Grant This Session—Installs the public-key certificate to your PC only for the current session. After the session is ended, the certificate is deleted. This dialog box will appear the next time you log into the ONS 15310-CL.
•Deny—Denies permission to install the certificate. If you choose this option, you cannot log into the ONS 15310-CL.
•Grant always—Installs the public-key certificate and does not delete it after the session is over. Cisco recommends this option.
•View Certificate—Allows you to view the public-key security certificate.
After you complete the security certificate dialog boxes, the web browser displays information about your Java and system environments. If this is the first login, a CTC downloading message appears while CTC files are downloaded to your computer. The first time you connect to an ONS 15310-CL, this process can take several minutes. After the download, the CTC Login dialog box appears.
Step 3 If you need to return to the software and database you had before activating Software R8.0, proceed with the "NTP-U228 Revert to Previous Software Load and Database" procedure.
Stop. You have completed this procedure.
NTP-U228 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 R8.0, you should have backed up the existing database at all nodes in the network (this is part of the "NTP-U225 Back Up the ONS 15310-CL Software Database" procedure). Cisco recommends that you record or export all critical information to your hard drive. If you need to revert to the backup database, use the following tasks, in order.
Step 1 Log into the node. For detailed instructions, refer to the Cisco ONS 15300-CL and Cisco ONS 15310-MA Procedure Guide. If you are already logged in, continue with Step 2.
Step 2 Complete the "DLP-U342 Revert to Protect Load" task.
Note Do not perform "DLP-U343 Manually Restore the Database" task unless the software revert failed.
Step 3 If the software reversion to your previous release failed to restore the database, complete the "DLP-U343 Manually Restore the Database" task.
Stop. You have completed this procedure.
DLP-U342 Revert to Protect Load
Note To perform a supported (non-service-affecting) reversion from Software R8.0, the release you want to revert to must have been working at the time you activated to Software R8.0 on that node. Also, a supported reversion 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 Software R8.0 a second time, to ensure that no actual reversion to a previous load can take place. In this latter case, the reversion will occur, but will not be traffic affecting and will not change you database.
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. Reversion activates the protect software and restores the database from the previous load. A dialog box asks you to confirm the choice.
Step 4 Click Yes. This begins the reversion. CTC drops the connection to the node and takes you to the network view, displaying a confirmation dialog box.
Step 5 Click OK and wait until the software reversion finishes before continuing.
Note The system reboot might take up to 4 minutes to complete.
Step 6 Wait one minute before reverting another node.
Step 7 After reverting all of the nodes in the network, close and restart your Netscape or Internet Explorer browser and log back into the last node that was reverted. This uploads the appropriate CTC applet to your workstation.
Note It might also be necessary to delete cached files from your browser's directory or from the TEMP directory on your MS Windows workstation. If you have trouble reconnecting to CTC, see the "DLP-U340 Delete Cached JAR Files" task.
Step 8 Return to your originating procedure (NTP).
DLP-U343 Manually Restore the Database
Purpose
|
This task manually restores the database. If you were unable to perform a revert successfully and need to restore the database, perform this task.
|
Tools/Equipment
|
PC or UNIX workstation
|
Prerequisite Procedures
|
U342 Revert to Protect Load
|
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 reversion failed.
Caution This process is service affecting and should be performed during a maintenance window.
Step 1 In 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 will be restored and the 15310-CTX-CL card will reboot.
Step 4 When the 15310-CTX-CL card has rebooted, log back into CTC and verify that the database is restored.
Wait one minute before restoring the next node.
Step 5 You have now completed the manual database restore.
Step 6 Return to your originating procedure (NTP).
NTP-U229 Upgrade to ONS 15310 Release 8.0 Using TL1
Note This procedure assumes you are upgrading using Release 6.x TL1 syntax. TL1 commands issued prior to software activation to Software R8.0.x will vary in syntax depending on the release that you are upgrading from. To ensure that your syntax for each command is correct, use the TL1 syntax supplied in the Cisco ONS SONET TL1 Command Guide for your particular release when issuing the following commands:
•ACT-USER
•COPY-RFILE
•REPT EVT FXFR
•OPR-PROTNSW-<OCN_TYPE>
•RTRV-COND-ALL
•RTRV-ALM-ALL
Note To perform an R8.0 software download using TL1, you must first have an FTP server or a terminal emulation program like HyperTerminal running on your workstation.
Note 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 "15310-03xx-A04K-1405.pkg
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/15310-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:21@90.90.90.90/15310-03xx-A04K-1405.p
kg";
The ":21" after the FTP server IP address 10.111.11.1 denotes port 21 on the server.
The software PKG file in the preceding example is located in the home directory of the FTP server. If the software PKG file is not in the home directory on the FTP server, insert the directory path where the software package resides between the last IP address and the PKG file in the command line. An example is shown here.
COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL,
SRC="ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1:21@90.90.90.90/CISCO/SOFTWARE/15310-03xx-A04
K-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 15310 node.
Step 2 Type the IP address for the node, using port 3083 or 2361.
The terminal emulation interface will appear 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 OSS profile user ID (required).
•<CTAG> is the correlation tag that correlates command and response messages (optional).
•<PID> is the password identifier (required).
For example, in the TL1 command:
ACT-USER:CISCO99:100:PASSWORD;
ACT-USER is the activation command, CISCO99 is the userid, 100 is the correlation tag (used to correlate commands to command responses), and PASSWORD is the password associated with the userid.
A response message containing the CTAG that you specified indicates the completion status of the command.
Step 4 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>]:<AID>:<CTAG>:TYPE=<xfertype>,[SRC=<src1>],[DEST=<dest>],[OVWRT=<ovwrt>]
,[FTTD=<fttd>];
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 (optional).
•<TYPE> 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 5 Repeat Step 4 for all nodes to be upgraded.
Step 6 Look for the REPT EVT FXFR message in the TL1 window. REPT EVT FXFR is an autonomous message used to report the start, completion, and completed percentage status of the software download. REPT EVT FXFR also reports any failure during the software upgrade, including invalid package, invalid path, invalid userid/password, and loss of network connection.
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 7 Complete U224 Prepare for Upgrade to Release 8.0 for each node to be upgraded.
Step 8 Complete U225 Back Up the ONS 15310-CL Software Database for each node to be upgraded.
Step 9 Lock out each BLSR span on each node being upgraded using the following command.
OPR-PROTNSW-<OCN_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 (optional).
•<SC> is the switch command that is to be initiated on the paths.
•<SWITCHTYPE> BLSR switch type.
•<DIRN> is the direction of transmission in which switching is to be made and is relative to the SONET line or path identified by the AID. The default value is RCV and should be changed to BTH.
Note Some nodes might have more than one BLSR. If this is the case, all BLSR spans on all nodes being upgraded need to be locked out. Nodes that are not being upgraded do not need to have the BLSR spans locked out. You must be aware of each span that is part of a BLSR to make sure all necessary spans are locked out.
Note BLSR 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 BLSR-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: BLSR-OOSYNC (MN); RING-MISMATCH (MJ); APSCDFLTK (MN); BLSR-RESYNC (NA).
Step 10 Verify that all necessary BLSR spans on each node being upgraded have been locked out using the following command:
RTRV-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::::];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node and must not be null.
•<CTAG> is the correlation tag that correlates command and response messages (optional).
Step 11 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 and 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>][,,,];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node and 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 only activate one node at a time; however, in a parallel upgrade you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully. If you wish to perform a parallel upgrade remotely, wait five minutes for the controller cards to complete the reboot.
Step 12 Starting at the node farthest from the GNE, type the APPLY command to activate the system software.
APPLY:[<TID>]::<CTAG>[::<MEM_SW_TYPE>];
where:
•<TID> is the target identifier.
•<CTAG> is the correlation tag that correlates command and response messages.
•<MEM_SW_TYPE> indicates a memory switch action during the software upgrade; MEM_SW_TYPE is ACT for activate.
If the command is successful, the appropriate flash is selected and the 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 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.
•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 13 Perform Step 12 for each node that will be upgraded, moving from the furthest node from the GNE toward the GNE itself, which should be activated last.
Note Note You might have to log in (Step 1 and Step 3) to each node again to activate the software (Step 12).
Step 14 After all nodes have been activated, log in using CTC or Telnet (Step 1and Step 3) and verify there are no outstanding alarms.
Step 15 Remove all BLSR lockouts using the following TL1 command:
RLS-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::<DIRECTION>];
where:
•<TID> is the target identifier (optional).
•<AID> indicates the entity in the node and 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, or BTH—both transmit and receive directions.
For example: RLS-PROTNSW-OC48:PETALUMA:FAC-6-1:209::BTH;
Stop. You have completed this procedure.
Related Documentation
•Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide, Release 8.0
•Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, Release 8.0
•Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 8.0
•Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide, Release 8.0
•Cisco ONS SONET TL1 Command Guide, Release 8.0 and Cisco ONS SONET TL1 Reference Guide, Release 8.0
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
©2007 Cisco Systems, Inc. All rights reserved.
Feedback
