|
|
ESP software is initially installed at the factory before delivery to the customer. As the software is refined and features added, you may need to load new software releases onto your ESP. This appendix provides procedures for upgrading your ESP software.
ESP Release 2.0 is compatible with BPX switch software release 8.4.x and is not compatible with switched software release 9.1.x. ESP Release 22 (or later) is compatible with BPX switch software release 9.1 and cannot run with BPX switch software release 8.4. Therefore when upgrading from ESP 2.0 to ESP 2.2 some special procedures need to be preformed. These procedures are described in the section Upgrading from ESP 2.0 to ESP 2.2 following the typical upgrade procedures.
Typically ESP software is upgraded in three steps:
1 ) Loading the New Software onto the StrataView Plus Workstation
2 ) Transferring the Software to the ESP
3 ) Loading the Software on the ESP
ESP software will have to be loaded onto the StrataView Plus Workstation from either a supplied tape or by FTPing it from a Cisco server. Typically new software upgrades are made available to customers through the Cisco Connection ONLINE (CCO) web page (http://www.cisco.com). Contact Cisco Customer Service to find out how to locate the appropriate software for your ESP.
When you transfer the file (a compressed tar file with a .Z extension), you must put it in the following directory on the StrataView Plus workstation:
/usr/users/svplus/images/esp
If the ESP directory (/esp) does not exist, you must create it.
To download an image to the ESP from StrataView Plus, follow these steps:
Step 1 Log into the StrataView Plus and start HP OpenView and a StrataView Plus Desktop.
Step 2 Double click on the StrataCom Network icon on the HP OpenView Topology Map. The StrataView Network Topology window will appear. This map should show all the BPXs (that is, WAN Service Nodes) in your network.
Step 3 Double click the BPX icon to show the attached shelves, including the ESP icons.
Step 4 Select the ESP you to which you wish to load software.
Step 5 Pull down the StrataCom option on the window's menu bar. Select Image Download. A list of available *.Z files will appear, including the files that you loaded there in the last section. The file will have the form ESP_BIN_rel_ver.Z.
Step 6 Select the appropriate *.Z file and the file will be transferred to the ESP. (The software has not been loaded at this time. You need to use the ApsUpgrade script as the root user to finish loading it.)
This process makes a backup of the existing software, stores it, then tries to load the new software into the operating directory. If it encounters a problem with the new software, such as a checksum error, it will restore the backup copy of the old software.
Before loading new software on the ESP, you must take it Out of Service.
To load the software, which has already been transferred from the StrataView Plus Workstation, follow these steps:
Step 1 Log into the ESP as apsuser. The ESP Configuration Interface will start.
Step 2 Select ESP Information from the main menu.
Step 3 Enter 5, Modify ESP Config, and change the Admin State to 1 Out of Service.
Step 4 Return to the ESP Configuration Interface Main Menu and select 0 to exit the ESP software and return to the UNIX prompt.
Step 5 Log in as root and run /opt/aps/scripts/ApsUpgrade:
(a) cd /opt/aps/scripts
(b) ApsUpgrade ESP_FILE
The ApsUpgrade script will display a sequence of messages as it runs. If it encounters an error, it will display it as a text message. If the upgrade is successful, the ApsUpgrade script will conclude with the message "APS Upgraded successfully from (software version) to (software version)."
The ESP will reboot as part of the software upgrade.
The ESP is in the Out of Service state after the software upgrade.
Step 6 After a successful software upgrade, bring the ESP back In Service:
(a) Log into the ESP as apsuser. The ESP Configuration Interface will start.
(b) Select ESP Information from the main menu.
(c) Enter 5, Modify ESP Config, and change the Admin State to 2 In Service.
Because ESP 2.2 is not compatible with BPX switched software release 8.4.x and ESP 2.0 is not compatible with BPX switched software release 9.1.x, you must carefully plan upgrades from ESP 2.0 to ESP 2.2 (and downgrades from ESP 2.2 to ESP 2.0).
Any upgrade will result in at least some momentary downtime on the WAN Service Node, during which the SVC service is temporarily lost and SPVCs are torn-down and later re-routed. The service interruption on a WAN Service Node with redundant ESPs is limited to the duration of the ESP switch-over. During an ESP switch-over, the initially-active ESP tears down SPVC (if ESP Release 2.2 is running) and SVC connections. Also, ports with ILMI enabled will need to re-register their addresses. The switch-over and re-establishment of SVC service and SVPC connections will take approximately from 1 to 8 minutes, depending on the number of ports, the number of SPVCs, etc.
For WAN Service Nodes without ESP redundancy, the node downtime is longer, since the single ESP must remain Out Of Service while it is being upgraded. Here the WAN Service Node downtime is estimated to be between 10 and 30 minutes, depending on the configuration.
Upgrades and downgrades are normally done on a node-by-node basis. During the network upgrade, the ESP software (2.0 and 2.2) and the BPX switch software (8.4 and 9.1) will become mixed. In networks which are running different ESP Releases (2.0 and/or 2.2) and BPX releases (8.4 and/or 9.1), SVC or SPVC service is available as follows:
The same basic procedure is used to upgrade (or downgrade) from any ESP release to any other ESP release. The only variation is that for some ESP upgrades (or downgrades), the BPX switch software (SWSW) will also have to be upgraded or downgraded for compatibility. (Since the procedure for upgrading an ESP to a newer release or downgrading to an older release are identical, we will refer to them both as an upgrade from this point forward.)
When there are redundant ESPs in the WAN Service Node, you bring the standby ESP Out Of Service while you load it with the new ESP software. (Note that the process of loading new ESP software also automatically upgrades the database and system files and reboots the ESP.) Next perform a graceful upgrade of the BPX switch software if necessary. Then switch-over to the upgraded ESP. The other, non-upgraded, ESP can be brought Out Of Service, upgraded, and finally brought back up as the standby ESP.
The following procedure limits the loss of SVC functionality to the duration of an ESP switch-over (approximately 1-8 minutes, depending on number of ports, etc.
Step 1 Load the new ESP software release onto the StrataView Plus Workstation
Step 2 Execute Image Download from StrataView Plus to download the new ESP software tar file to both ESPs.
Step 3 Bring the Standby ESP into Shutdown state using the ESP CLI.
Step 4 Return to the ESP Configuration Interface Main Menu and select 0 to exit the ESP software and return to the UNIX prompt.
Step 5 Log in as root and run /opt/aps/scripts/ApsUpgrade as described in the section, Loading the Software on the ESP
Step 6 Once the upgraded ESP has finished rebooting, modify the Admin State of the upgraded ESP to "In Service". Depending on the old and new versions, it may not yet be able to come into service due to a mismatch with the SWSW (Annex G polling will fail). If there is a SWSW mismatch, the ESP will keep trying to establish Annex G communication and will go in service once it is able to (i.e. once the SWSW has been upgraded).
Step 7 If a BPX switch software (SWSW) upgrade is required, perform a graceful upgrade of the SWSW. Note that this requires BCC redundancy. To upgrade BPX switch software, use the BPX switch CLI to perform the following commands:
(a) Execute loadrev command to copy new SWSW image into RAM on the standby BCC, and into flash memory on the active BCC.
(b) Once loadrev is complete (that is, standby BCC is in "upgraded" state), execute runrev command to switch-over the BCCs and begin running the new software image.
(c) Execute loadrev command again to upgrade the previously active BCC.
Once the new SWSW becomes active, the ESP will automatically switch-over, since the non-upgraded ESP will now fail, and the upgraded ESP, now being able to establish Annex G communication with the BPX 8620, will come into service. SVC service is lost during the switch-over.
Step 8 Shutdown the non-upgraded ESP.
Step 9 Upgrade the shutdown ESP's software as in step 4 above.
Step 10 Once the newly upgraded ESP has finished rebooting, bring it back in service using the ESP CLI. When it comes back in service it will adopt the Standby role. The upgrade is now complete.
Without ESP redundancy, SVC functionality is lost for the duration of the upgrade procedure, approximately 10-30 minutes. The SVC downtime is kept at a minimum if the user upgrades the ESP in parallel with the BPX switched software upgrade. Ideally, the SWSW upgrade should be started early enough so that it is complete by the time the ESP software upgrade is complete.
Step 1 Load the new ESP software release onto the StrataView Plus Workstation.
Step 2 Execute Image Download from SV+ to download the new ESP software tar file to the ESP.
Step 3 If a SWSW upgrade is required, perform a graceful upgrade of the SWSW, as described in Step 6 of the Step-by-Step Upgrade Procedure for Redundant ESPs.
Step 4 While the SWSW upgrade is in progress, begin the ESP software upgrade. The first step is to bring the ESP into Shutdown state using the ESP Configuration Interface. (SVC calls cannot be made once the ESP is shutdown.)
Step 5 Return to the ESP Configuration Interface Main Menu and select 0 to exit the ESP software and return to the UNIX prompt.
Step 6 Log in as root and run /opt/aps/scripts/ApsUpgrade as described in the section, Loading the Software on the ESP
Step 7 After the upgraded ESP has finished rebooting, modify the Admin State to "In Service". If the SWSW upgrade is finished, the ESP will come up in the StandAlone role. The upgrade is now complete, and SVC functionality is restored.
|
|