Cisco NCS 2000 Series Upgrade Guide, Release 10.1.x.x
This document explains how to upgrade the Cisco Transport Controller (CTC) software to the NCS fixed grid or NCS flex software using the control cards. For a complete list of compatible control cards, see Card Compatibility
Cisco NCS 2000 Series Upgrade Guide, Release 10.1.x.x
This document explains how to upgrade the Cisco Transport Controller (CTC) software to the NCS fixed grid or NCS flex software using the control cards. For a complete list of compatible control cards, see Card Compatibility
NCS Upgrade Paths
This table describes the NCS upgrade paths.
Source Release |
Upgrade Options |
---|---|
R9.6.0.7 (SONET or SDH) MSTP |
R10.1.x.x (NCS fixed grid) |
R9.8.1.1 (SONET or SDH) MSTP |
|
R10.0.1 (SONET or SDH) MSTP |
|
R10.0.2 (SONET or SDH) MSTP |
|
R10.0.1, 10.0.2 (NCS flex ) |
R10.1.x.x (NCS flex) |
R10.0.1, 10.0.2 (NCS fixed grid) |
R10.1.x.x (NCS fixed grid) |
Source Release |
Upgrade Options |
---|---|
R9.6.0.5 (SONET or SDH) MSTP |
R10.0.1.x, 10.0.2 (NCS fixed grid) |
R9.8.0 (SONET or SDH) MSTP |
|
R10.0 (SONET or SDH) MSTP |
|
R10.0.1 (SONET or SDH) MSTP |
|
R10.0, 10.0.1 (NCS flex ) |
R10.0.1.x, 10.0.2 (NCS flex) |
R10.0, 10.0.1 (NCS fixed grid) |
R10.0.1.x, 10.0.2 (NCS fixed grid) |
For upgrade path details, refer the NCS Software Matrix
Some of the key limitations to be considered before proceeding with the upgrade are:
-
When a node is upgraded from R9.80 (SONET or SDH), R10.0 (SONET or SDH) MSTP to NCS fixed grid, the database backup taken from the originating release cannot be restored after the upgrade.
-
When a node is upgraded from NCS fixed grid to NCS flex, the database back-up taken from the originating release cannot be restored after the upgrade.
-
When a node is upgraded from NCS fixed grid to NCS fixed grid or from NCS flex to NCS flex, the database is retained during the upgrade.
Caution |
Do not attempt to upgrade a configuration that contains Cisco ONS 15454 M12 nodes to Cisco NCS software. |
Errorless Upgrades and Exceptions
This section describes important information to be aware of before you begin the upgrade process:
-
When a node installed with GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE cards configured with REP or a channel group is upgraded from R9.2.0 or later releases, traffic loss occurs. The traffic loss is less than 60 seconds for each GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE card that undergoes a soft reset during the upgrade process.
- Before you upgrade the software on a
NCS 2006 shelf powered by a 15454-M6-DC20 or a 15454-M6-AC module to R9.6.x or a later release, you must verify that the total power
consumed by all the line cards in the shelf does not cross the maximum power limit.
Table 1. Maximum Power Limit Values for the ONS 15454 M6 Shelf Power Module
Maximum Power Limit
15454-M6-DC20
960 W
15454-M6-DC
1440 W
15454-M6-AC
900 W
15454-M6-AC2
1200 W
If the power consumption exceeds the limit after the upgrade, the line cards that caused it to exceed, do not boot. This results in traffic loss. To avoid this traffic loss, use the 15454-M6-AC2 module instead of the 15454-M6-AC module and the 15454-M6-DC module instead of the 15454-M6-DC20 module. For details about power calculation, see the table, Line Card Power Consumption Values .
- After you upgrade to R9.6.0 or later releases, use the Force FPGA Update button in the CTC card view > Provisioning > Card tab to update the SWAN FPGA image on OTU2_XP cards. This allows detection of the HI-BER alarm when OTU2_XP cards are configured in the 10G Ethernet LAN Phy to WAN Phy mode.
-
The MXP_MR_2.5 and MXPP_MR_2.5 cards automatically download a new field-programmable gate array (FPGA) image during an upgrade from a software release prior to R7.0 to R10.1.x.xR10.5.x.x. The upgrades for DWDM configurations are expected to be errorless with the following exceptions if nodes are running MXP_MR_2.5 and MXPP_MR_2.5 cards:
-
If Y-cable protection is not provisioned, the data path incurs a traffic hit of up to 10 seconds or less.
-
If Y-cable protection is provisioned on cards running Fiber Channel (FC) payloads, traffic switches away from the card downloading the new FPGA causing the FC link to be reinitialized.
-
If Y-cable protection is provisioned on cards running Gigabit Ethernet (GE) payloads, there is no traffic interruption.
-
-
If a R9.6.0 node is provisioned with the 15216-MD-48-CM interleaver module, delete the module in CTC before upgrading the software to R9.6.0.3, R9.6.0.4, R9.8, R10.x.x, or R10.1.x.x. The interleaver module can be provisioned again in CTC after the upgrade is complete.
Cisco NCS Software Packages
Caution |
Do not download and activate the Cisco NCS software package on a Cisco ONS 15454 M12 shelf. |
The Cisco NCS software is shipped in two packages:
-
NCS Flex: contains software that supports flex cards and configurations in NCS 2002 and NCS 2006 . WSON is supported in this package.
- NCS Fixed Grid: contains software that supports fixed grid cards and configurations in NCS 2002 and NCS 2006. WSON is supported in this package.
Note |
You can download the NCS fixed grid package on a NCS flex node and vice versa. The node database is deleted during the activation. After the activation, it is recommended to relaunch CTC to view the new package that is activated. The database is not lost during activation, for Optical Line Amplifier (OLA) nodes with these cards- OPT-AMP-C, OPT-EDFA-xx, OPT-RAMAN-CTP, OPT-RAMAN-COP. |
This table describes the node controller and shelf controller for NCS packages.
Package | Node Type | Node Controller | Shelf Controller |
---|---|---|---|
NCS Flex | Flex NCS Node | TNC / TNCE / TSC / TSCE / TNCS / TNCS-O / TNCS-2 / TNCS-2O | TNC / TNCE / TSC / TSCE / TNCS / TNCS-O / TNCS-2 / TNCS-2O |
NCS Fixed Grid | Fixed Grid Node | TNC / TNCE / TSC / TSCE / TNCS / TNCS-O / TNCS-2 / TNCS-2O | TNC / TNCE / TSC / TSCE / TNCS / TNCS-O / TNCS-2 / TNCS-2O |
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 software, make a printed copy of this document and use it as a checklist.
Each non-trouble procedure (NTP) is a list of steps designed to accomplish a specific procedure. Follow the steps until the procedure is complete. If you need more detailed instructions, refer to the detail-level procedure (DLP) specified in the procedure steps. Throughout this guide, NTPs are referred as “procedures” and DLPs as “tasks.” Every reference to a procedure includes its NTP number, and every reference to a task includes its DLP number.
The DLP (task) supplies additional task details to support the NTP. The DLP lists numbered steps that lead you through completion of a task. Some steps require that equipment indications be checked for verification. When a proper response is not obtained, a trouble clearing reference is provided.
This section lists the document procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
-
NTP-U487 Preparing to Upgrade to a New Release—This procedure contains critical information and tasks that you must read and complete before beginning the upgrade process.
-
NTP-U488 Back Up the Cisco NCS Software Database—Complete the database backup to ensure that you have preserved your node and network provisioning in the event that you need to restore them.
-
NTP-U489 Upgrade the Cisco NCS Software—Complete this procedure to complete the upgrade.
-
NTP-U490 Install Public-Key Security Certificate— Complete this procedure to be able to run the software.
-
NTP-U491 Restore the Previous Software Load and Database— Complete this procedure if you want to return to the previous software load you were running before activating the new release.
-
NTP-U493 Upgrade to the NCS Software Using TL1— Complete this procedure only if you want to upgrade to a new release using Transaction Language (TL1).
NTP-U487 Preparing to Upgrade to a New Release
Purpose |
This procedure provides critical information checks and tasks you must complete before beginning an upgrade to the latest release. R10.1.x.x |
Tools/Equipment |
Cisco NCS nodes |
Prerequisite Procedures |
"DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document. |
Required/As Needed |
Required |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Procedure
Step 1 |
Before you begin, make sure that information related to your site, for example, date, street address, site phone number, and dialup number are stored in a safe and accessible location. The data will be useful during and after the upgrade. |
||
Step 2 |
Read the release notes of the release you are upgrading to. Visit Release Notes to download the release notes.
|
||
Step 3 |
Ensure your workstation meets the minimum hardware and software requirements before starting the upgrade. For more information on the hardware and software requirements, read the release notes. |
||
Step 4 |
Refer to the Software Upgrade Matrix to verify if the upgrade path is supported. |
||
Step 5 |
Make sure that the control cards are installed in the appropriate slots on all the nodes in the network and on both the slots as indicated here. For a complete list of supported control cards, see Supported Control Cards:
|
||
Step 6 |
Repeat the above step for every node in the network. |
||
Step 7 |
Collect the node diagnostics logs from the node. This action is very useful incase the upgrade fails, as the diagnostics help in understanding if the node had issues before the upgrade. |
||
Step 8 |
Export the current alarms and conditions to your local storage. After the upgrade, if new alarms or conditions arise, then comparing the time stamp of the alarm to the previously saved time stamp helps in identifying new alarms or conditions. |
||
Step 9 |
Perform a backup of the node database. This is very useful incase the upgrade fails, then the database can be restored using the backup. The detailed procedure for backing up the database is discussed in the next section. Stop. You have completed this procedure. |
NTP-U488 Back Up the Cisco NCS Software Database
Purpose |
This procedure retains all configuration data for your network before performing the upgrade. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
|
Required/As Needed |
Required |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Procedure
Step 1 |
In the node view, click the Maintenance>Database tabs. |
||||||||||||||||||||||||||||
Step 2 |
In the database pane, click the Backup button. The Database Backup dialog box is displayed. |
||||||||||||||||||||||||||||
Step 3 |
Click Browse. Navigate to the local PC directory or network directory and type a database name using the IP address of the node to upgrade in the File Name field and click OK. To overwrite an existing file, click Yes. |
||||||||||||||||||||||||||||
Step 4 |
When the backup is complete, click OK. |
||||||||||||||||||||||||||||
Step 5 |
Repeat Steps 1 through 5 for each node in the network. |
||||||||||||||||||||||||||||
Step 6 |
(Optional) It is recommended that you manually log critical information by either writing it down, printing screens, or by exporting the data to an appropriate format, as applicable. Use the following table to determine the information that should be logged.
1 DCC=data communications channel
Stop. You have completed this procedure. |
NTP-U489 Upgrade the Cisco NCS Software
Purpose |
This procedure upgrades the CTC software to R10.1.x.x and must be performed on all nodes, or groups of nodes to be upgraded. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
|
Required/As Needed |
Required |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Caution |
Do not perform maintenance or provisioning activities during the activation task. |
Note |
When you upgrade from Release 9.21 to Release 9.3 and later releases, some OCHNC circuits do not automatically upgrade during the software activation process. These circuits must be reconfigured again using the Reconfigure Circuits option in CTC. |
Procedure
Step 1 |
Insert the software CD into the workstation CD-ROM drive (or otherwise acquire access to the software) to begin the upgrade process.
|
||
Step 2 |
Complete the DLP-U546 Download the NCS Software task for all nodes to be upgraded. |
||
Step 3 |
Complete the DLP-U548 Activate the New Cisco NCS Software task for all nodes to be upgraded.
|
||
Step 4 |
Complete the DLP-U549 Delete Cached JAR Files task, as necessary. |
||
Step 5 |
(Optional) If you want to prevent a software revert to an earlier software release, complete the DLP-U546 Download the NCS Software task on all nodes, or groups of nodes you are upgrading a second time.
|
||
Step 6 |
If you need to return to the software and database you had before activating Software R10.1.x.x, proceed with the NTP-U491 Restore the Previous Software Load and Database procedure. |
||
Step 7 |
To back up the Software R10.1.x.x database for the working software load, see NTP-U488 Back Up the Cisco NCS Software Database procedure in order to preserve the database for the current release. After the upgrade is complete, the date and time in CTC is reset. Stop. You have completed this procedure. |
What to do next
After upgrading the software to a different build, if there is a change in the FPGA, the FPGA is upgraded automatically. During the FPGA upgrade process, the card goes for a cold reboot. If Optical Supervisory Channel (OSC) is provisioned, then the transient PPM-IMPROPER-REMOVAL alarm is raised, which gets cleared in a short span of time. This happens because of the power glitches to the PPM while the card is coming up after the cold reboot.
DLP-U546 Download the NCS Software
Purpose |
This task downloads R10.1.x.x software to the NCS nodes before activation. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
|
Required/As Needed |
Required |
Onsite/Remote |
Onsite or remote |
Security Level |
Maintenance user or higher |
Note |
The control card contains flash memory with two partitions—Working and protect (backup). The software is downloaded to the protect (backup) partition of the flash memory on both the standby and active cards. This download is not traffic affecting because the active software continues to run in the primary RAM location. The software can therefore be downloaded at any time. |
Note |
To download and upgrade the software using TL1, see the NTP-U493 Upgrade to the NCS Software Using TL1 procedure. |
Note |
All the nodes in the network must run the DWDM package with WSON to make the WSON feature functional because WSON is a network level feature. |
Procedure
Step 1 |
From CTC View menu, choose Go to Network View. |
||
Step 2 |
Make sure that the alarm filter is turned off. To do so, complete the following: |
||
Step 3 |
Resolve any outstanding alarms. To view alarms for all the nodes in the network, click the Alarms tab.
|
||
Step 4 |
From the CTC View menu, choose Go to Home View to go to the node view. |
||
Step 5 |
Click the Maintenance> Software tabs. |
||
Step 6 |
Click the Download button. The Download Selection dialog box appears. |
||
Step 7 |
Locate the software files on the software CD or on your hard drive. |
||
Step 8 |
To open the folder, choose the file with the PKG extension and click Open. |
||
Step 9 |
From the list of compatible nodes, select the nodes where the software must be downloaded.
|
||
Step 10 |
Click OK. The Download Status column monitors the progress of the download. |
||
Step 11 |
Return to your originating procedure (NTP). |
DLP-U548 Activate the New Cisco NCS Software
Purpose |
This task activates the software on each node in the network. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
|
Required/As Needed |
Required |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Note |
It is recommended that the first node that is activated be connected via LAN. This ensures that the new CTC JAR files download to the workstation as quickly as possible. If a node is provisioned to have no LAN access, the value is overridden in the case of node isolation. Additionally, if the node is not reachable, the LAN access is turned on. It is recommended that you avoid node isolation. |
Note |
During the activation process, when the node is being upgraded to R11.0 (and later releases), the USB-MOUNT-FAIL alarm is raised. In MSM, the USB-MOUNT-FAIL alarm is raised on all subtended shelf controllers and the node controller. When all the subtended shelf controllers and the node controller complete the upgrade successfully, the USB-MOUNT-FAIL alarm is cleared. No manual intervention is required to clear the USB-MOUNT-FAIL alarm. After the USB-MOUNT-FAIL alarm is cleared, USB sync is triggered. After USB sync is successfully completed, the node is migrated to the latest software successfully. |
Procedure
Step 1 |
If CTC is not already started, start CTC. |
||
Step 2 |
Record the IP address of the node. The IP address can be obtained either on the LCD or on the upper left corner of the CTC window. |
||
Step 3 |
Make sure that the alarm filter is turned off. To do so, complete the following: |
||
Step 4 |
Make sure that all cards that are part of a 1+1 or Y-cable protection group must be active on the working card of the protection group and no protection switches are occurring. Also, ensure that traffic carrying protect cards are in a standby state. To do so, complete the following:
|
||
Step 5 |
In shelf view, click the Maintenance > Software tabs. |
||
Step 6 |
Verify that the version in the Protect Version column is R10.1.x.x. |
||
Step 7 |
Click the Activate button. The Activate dialog box displays a warning message. |
||
Step 8 |
Click Yes to proceed with the activation. During node activation, all the common control cards in the node reboot beginning with the standby card. As soon as the standby
card recovers from the reboot, it signals the active card to reset as a standby card and the standby card transitions to active.
An Activation Successful message indicates that the software is successfully activated.
|
||
Step 9 |
Click OK. The connection between CTC and the node is lost and CTC displays the Network view. The INCOMPATIBLE-SW alarm is raised in
CTC for the first node that is activated because CTC is unable to connect to the NE due to differing, incompatible versions
of the software between CTC and the NE. A CTC alert is displayed to update the CTC software. To clear the INCOMPATIBLE-SW
alarm, perform steps 10 through 12 only for the first node that is activated on the network.
During the activation process:
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 > Update CTC. The CTC software is updated. A CTC alert is displayed to restart CTC. |
||
Step 11 |
In CTC, choose File > Exit. |
||
Step 12 |
Start CTC again. |
||
Step 13 |
Click the Launch CTC button in the CTC launcher window. The new CTC applet loads. The login window is displayed. |
||
Step 14 |
Type the user name and password and click Login. |
||
Step 15 |
Return to your originating procedure (NTP). |
DLP-U549 Delete Cached JAR Files
Purpose |
This task deletes cached JAR files. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
None |
Required/As Needed |
You need to complete this task after you activate the first network node. |
Onsite/Remote |
Onsite or remote |
Security Level |
Maintenance user or higher |
Note |
Whenever the CTC software is upgraded or reverted, make sure that the browser and hard drive cache files are cleared. |
Procedure
Step 1 |
Delete cached files from your browser directory. In Netscape:
In Microsoft Internet Explorer:
|
||
Step 2 |
Close the browser.
|
||
Step 3 |
On Windows systems, delete cached files from your workstation in this location: C:\Documents and Settings\username\Application Data\Cisco\CTC
|
||
Step 4 |
Reopen the browser. You should now be able to connect to CTC. |
||
Step 5 |
Return to your originating procedure (NTP). |
DLP-U551 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 |
Security Level |
Superuser |
Note |
If you are using SNTP, this task is not applicable. |
Procedure
Step 1 |
In CTC node view, click the Provisioning > General tabs. |
Step 2 |
Set the correct date and time. Click Apply . |
Step 3 |
Repeat Steps 1 and 2 on all the remaining nodes. |
Step 4 |
Return to your originating procedure (NTP). |
NTP-U490 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 software R4.1 or later. |
Onsite/Remote |
Onsite or remote |
Security Level |
Provisioning or higher |
Procedure
Step 1 |
Log into CTC. |
Step 2 |
If the Java Plug-in Security Warning dialog box appears, choose one of the following options:
After the completion of the security certificate dialog boxes, the web browser displays information about the Java and system environments. If this is the first login, a CTC downloading message appears while CTC files are downloaded to the computer. The process can take several minutes, if it is the first time. After the download, the CTC Login dialog box appears. |
Step 3 |
Return to the software and database you had before activating the software, proceed with the NTP-U491 Restore the Previous Software Load and Database procedure. Stop. You have completed this procedure. |
NTP-U491 Restore the Previous Software Load and Database
Purpose |
This procedure returns to the software and database provisioning that was present before R10.1.x.x was activated. The software load and database cannot be restored to the previous version if the software on both the working and protect cards were upgraded to R10.1.x.x. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
"DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document. NTP-U487 Preparing to Upgrade to a New Release |
Required/As Needed |
As needed |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Note |
Tasks to revert to a previous load are not part of the upgrade, and are provided here as a convenience to those wishing to perform a revert after an upgrade. If you have successfully performed all necessary procedures up to this point, you have finished the software upgrade. |
Caution |
If a node is set to secure, dual-IP mode, the database information is overwritten with this configuration and cannot be reverted to single-IP repeater mode. |
Note |
The defaults database files (db files) used to restore the basic configuration on a single non-multishelf node are shipped along with the standard R10.1.x.x software release package. For a multishelf set-up, the multishelf configuration must be unprovisioned to restore the basic configuration using the defaults database file. Also, the database backup from a multishelf system can be used to restore the same multishelf system. |
Note |
All line cards of the subtended shelf controller may undergo a reboot during a software revert from Release 11.0 or earlier to a previous software release and is traffic impacting. |
Procedure
Step 1 |
Complete the DLP-U552 Revert to Protect Load task. |
Step 2 |
If the software revert to your previous release failed to restore the database, complete the DLP-U553 Manually Restore the Database task. Stop. You have completed this procedure. |
DLP-U552 Revert to Protect Load
Purpose |
This task reverts to the software you were running prior to the last activation. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
NTP-U487 Preparing to Upgrade to a New Release |
Required/As Needed |
Required for revert |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Note |
If the software is downloaded again after a version is activated, a revert to the previous version cannot be performed. |
Note |
To perform a supported (non-service-affecting) revert from R10.1.x.x, the release you want to revert to must have been working at the time you activated to the current software version on that node. Also, a supported revert automatically restores the node configuration at the time of the previous activation. The exception to this is when you have downloaded R10.1.x.x a second time, ensuring that no revert to a previous load can take place. In this case, the revert occurs, but is not traffic-affecting and does not change the database. |
Note |
Ensure that all cards that are part of a protection group (1+1 or Y-cable) are active on the working card of that protection group and that no protection switches are occurring. To ensure that traffic carrying protect cards are in a standby state, in the node view click the Maintenance tab, and view the Protect column for each of the listed protection groups. View the active/standby status of each card in the Maintenance tab. |
Procedure
Step 1 |
From the node view, click the Maintenance tab, then click the Software button. |
||
Step 2 |
Verify that the protect software displays the release you upgraded from. |
||
Step 3 |
Click the Revert button. Revert activates the protect software and restores the database from the previous load. A confirmation dialog box appears.
|
||
Step 4 |
Click OK. This begins the revert process and drops the connection to the node. |
||
Step 5 |
Wait until the software revert completes before continuing.
|
||
Step 6 |
Wait one minute before reverting another node. |
||
Step 7 |
After reverting all the nodes in the network, restart the browser and log back into the last node that was reverted. This uploads the appropriate CTC applet to your workstation. |
||
Step 8 |
Perform the DLP-U549 Delete Cached JAR Files task. |
||
Step 9 |
Return to your originating procedure (NTP). |
DLP-U553 Manually Restore the Database
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 |
|
Required/As Needed |
As needed |
Onsite/Remote |
Onsite or remote |
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. |
Procedure
Step 1 |
In CTC node view, click the Maintenance tab, then click the Database button. |
||
Step 2 |
Click the Restore button. The DB Restore dialog box appears. |
||
Step 3 |
Click Browse to locate the database file stored on the workstation hard drive or on network storage. |
||
Step 4 |
Click the database file to highlight it and click Open. The DB Restore dialog box appears. |
||
Step 5 |
If you need a complete database restore, check the Complete database (System and Provisioning) checkbox.
|
||
Step 6 |
Click Ok. The database is restored and the control cards reboot. |
||
Step 7 |
When the control cards have finished rebooting, log into CTC and verify that the database is restored. Wait one minute before restoring the next node. |
||
Step 8 |
Repeat Steps 1 to 7 for each node in the network. You have now completed the manual database restore.
|
||
Step 9 |
Return to your originating procedure (NTP). |
NTP-U493 Upgrade to the NCS Software Using TL1
Purpose |
This procedure upgrades the software to R10.1.x.x using TL1 rather than CTC. |
Tools/Equipment |
PC or UNIX workstation |
Prerequisite Procedures |
|
Required/As Needed |
Optional |
Onsite/Remote |
Onsite or remote |
Security Level |
Superuser |
Note |
To ensure that your syntax for each command is correct, see the TL1 syntax in the TL1 Command Guide for your particular release when issuing the following commands:
|
Note |
To download the software using TL1, an FTP server or a terminal emulation program like HyperTerminal must be running on the workstation. |
Note |
The download (COPY-RFILE) command is different when downloading software to a gateway network element (GNE) or an end network element (ENE) under the following conditions:
|
Note |
|
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/NCS2K-F-03xx-A04K-1405.pkg”,
FORCEENABLE=YES;
-
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/NCS2K-L-03xx-A04K-1405.pkg”,FORCEENABLE=YES;
The ":2361" after the FTP server IP address 10.111.11.1 denotes port 21 on the server.
The software PKG file in the preceding example is located in the home directory of the FTP server. If the software PKG file is not in the home directory on the FTP server, insert the directory path where the software PKG resides between the last IP address and the PKG file in the command line. An example is shown here.
COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL,
SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1:21@90.90.90.90/CISCO/SOFTWARE/NCS2K-F-03xx-A04K-1405.pkg”,,FORCEENABLE=YES;
Procedure
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 node. |
||
Step 2 |
Type the IP address for the node, using port 3083 or 2361. The terminal emulation interface displays a warning message and a command prompt (usually >). You can enter TL1 commands at this prompt. |
||
Step 3 |
Type the ACT-USER (Activate User) command in the TL1 request window to open a TL1 session: ACT-USER:[<TID>]:<uid>:<CTAG>::<pid>;
where:
|
||
Step 4 |
Repeat Step 2 for each node to be upgraded. |
||
Step 5 |
Type the COPY-RFILE command in the TL1 window or, if you are using HyperTerminal, click Transfer > Receive File, and use the associated dialog box to select a file to receive. The COPY-RFILE command downloads a new software package from the location specified by the FTP URL into the inactive flash partition residing on the controller card. COPY-RFILE:[<TID>]:<src>:<CTAG>::TYPE=<xfertype>,[SRC=<src1>],[DEST=<dest>],[OVWRT=<ovwrt>],[FTTD=<fttd>],[FORCEENABLE=<FORCEENABLE>];
where:
|
||
Step 6 |
Repeat Step 6 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:
where:
|
||
Step 8 |
Complete “NTP-U487 Preparing to Upgrade to a New Release” procedure on page 8 for each node to be upgraded. |
||
Step 9 |
Complete NTP-U488 Back Up the Cisco NCS Software Database for each node to be upgraded. |
||
Step 10 |
Verify that there are no outstanding alarms or conditions on each node using the following commands: RTRV-PROTNSW-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>[::::];
where:
RTRV-ALM-ALL:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],[<CONDITION>],[<SRVEFF>][,,,];
where:
Resolve all issues before proceeding.
|
||
Step 11 |
Starting at the node farthest from the GNE, type the APPLY command to activate the system software. APPLY:[<TID>]::<CTAG>[::<MEM_SW_TYPE>]:[FORCEENABLE=<FORCEENABLE>];
where:
If the command is successful, the appropriate flash is selected and the TNC/TNCE/TSC/TSCE card reboots. The following occurs:
After the common control cards finish resetting and all associated alarms clear, you can safely proceed to the next step. (If you are upgrading remotely and cannot see the nodes, wait for 5 minutes for the process to complete, then check to ensure that related alarms have cleared before proceeding.) Repeat this step for each node that will be upgraded, moving from the furthest node from the GNE toward the GNE itself, which should be activated last.
|
||
Step 12 |
After all nodes have been activated, log in using CTC or Telnet and verify there are no outstanding alarms. |
||
Step 13 |
To back up the database for the working software load, see NTP-U488 Back Up the Cisco NCS Software Database in order to preserve the database for the current software. Stop. You have completed this procedure. |
Related Documentation
Use this document in conjunction with the following publications:
-
Release notes:
http://www.cisco.com/en/US/products/ps13295/prod_release_notes_list.html
-
TL1 command guides:
http://www.cisco.com/en/US/products/ps13295/prod_command_reference_list.html
-
Configuration guides:
http://www.cisco.com/en/US/products/ps13295/products_installation_and_configuration_guides_list.html
-
Troubleshooting guides:
http://www.cisco.com/en/US/products/ps13295/prod_troubleshooting_guides_list.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. 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. (1721R)