Avaya Installation Wizard (AIW) · Web viewA license filename has the format SVm-.lic, where is the system ID,

Avaya Installation Wizard (AIW)

Upgrade Tool

January 2005

Upgrade Tool

January 2005

Job Aid:Upgrade Tool And Worksheets

for Avaya S8300, S8500, and S8700 Series Media Servers, LSPs, and Avaya G350 and G700 Media Gateways

555-245-757, Issue 4

January 2005

This job aid describes the steps required to use the Communication Manager R2.2 Upgrade Tool to upgrade software and firmware on the following platforms:

Main Servers

S8300 Media Server

S8500 Media Server

S8700 Media Server

S8710 Media Server

Other Servers

S8300 Media Server configured as a Local Survivable Processor (LSP)

S8700/S8710 Standby Server

Media Gateways

G700 Media Gateway

G350 Media Gateway

CAUTION: If the media server’s current release of Communication Manager is R2.1, use the Upgrade Tool that already exists on the media server to upgrade the server, or any of its LSPs. to Communication Manager R2.2. If the media server’s current release of Communication Manager is R2.0, you can use the R2.0 upgrade tool to upgrade LSPs (if the LSP has the S8300B version), but you cannot use the R2.0 Upgrade Tool to upgrade the media server itself. See the following table:

Current Version

Target Version

Use the Upgrade Toolof Media Server

of Media Server

to Upgrade Media Server?-------------------

-------------------

----------------------------------- R2.0

R2.2

No R2.1

R2.2

Yes R2.2

R2.2.x

Yes

See also the Job Aid: Upgrade Tool and Worksheets document (Issue 2 for CM R2.0 or Issue 3 for CM R2.1), appropriate for the release.

The job aid also contains the Upgrade Tool Worksheets you need to run the Upgrade Tool. Worksheets appear at the end of this document and should be filled in with actual customer data by the project manager, software specialist, or another support person who configures Voice over IP systems, along with the customer administrator. The project manager should then send a printout of the worksheets to the person running the upgrade. Better yet, since this document is a Word file, the project manager can also type data directly into the file and email the file to the person running the upgrade.

Important: To complete the worksheets in Word, simply tab to the fields and type the data. Then, save the file by selecting File>Save As, and then enter a name for the file.

Note: For additional information on the Upgrade Tool, use the online help available on the Upgrade Tool itself.

Purpose

The Upgrade Tool allows you to automatically upgrade or update the following:

· Local Survivable Processors (LSPs) and remote or local G350 and G700 Media Gateways from the primary controller. The primary controller can be an S8300, S8500, S8700, or S8710 Media Server. You can also use the tool to apply updates (patches) to the LSPs.

· Most of the media modules that are resident in the G350 or G700 Media Gateways (MM312, MM710, MM711, MM712, MM714, MM717, MM720, MM722, and MM760)

· The primary controller on which the Upgrade Tool is running. This upgrade also includes software updates.

· The standby server if the primary controller is an S8700/S8710 Media Server.

With the Upgrade Tool, you connect to the LSPs and gateways over the network in order to run the upgrades. Additionally, you do not have to run the upgrades one by one. Simply type the needed information for all LSPs and gateways into the Upgrade Tool. Then run the Upgrade Tool, which automatically upgrades the software and firmware on all LSPs and G350 or G700 gateways, respectively.

Figure 1 on page 4 illustrates many of the configurations that the Upgrade Tool supports.

NOTE: You cannot run the Upgrade Tool from an LSP. You must run it from a primary controller.

You cannot use the Communication Manager R2.2 Upgrade Tool to do the following:

· Install a new primary controller or LSP or a new G350 or G700 Media Gateway.

For each new installation, you must be on site and use the Avaya Installation Wizard (for a primary controller or LSP), the Avaya Gateway Installation Wizard (for a media gateway), or perform a manual installation.

· Upgrade LSPs to Communication Manager Release 2.2.

For upgrades of LSPs from Communication Manager Release 2.0 or 2.1 to Release 2.2, use the Upgrade Tool for Communication Manager R2.0/2.1 that resides on the primary controller prior to its upgrade to R2.2.

CAUTION: If the system you are upgrading uses Communication Manager R1.3 or earlier, you cannot upgrade an LSP with any version of the Upgrade Tool. This restriction applies because the hard drive of the S8300 must be replaced as part of the upgrade.

Additionally, if the LSP is using R2.0 software but does not have the “B” version of S8300 Media Server, you cannot upgrade the LSP with any version of the Upgrade Tool. This restriction applies because the S8300 must be replaced with the S8300B as part of the LSP upgrade.

LSPs must be upgraded to newest release of Communication Manager before you upgrade the primary controller to the newest release. As a result, the R2.2 version of the Upgrade Tool is only available for use after all LSPs have already been upgraded to CM2.2 and the primary controller has been upgraded to R2.2.

· Use the Communication Manager Release 2.2 Upgrade Tool to upgrade a primary controller (S8300, S8500, S8700, or S8710 Media Server) to Communication Manager R2.2. Instead, if the existing media server has R2.1 software, use the Upgrade Tool on that earlier release of Communication Manager to perform the upgrade to R2.2.

· Upgrade an active LSP (one that has taken control of calls because of a problem with the primary controller).

· Upgrade P330 or C360 Expansion modules.

NOTE: This limitation does not apply to the P330 processor embedded in a G700 Media Gateway, nor to the P330 processors in a G700 stack.

· Upgrade G600, G650, CMC1, SCC1, or MCC1 Media Gateways

Sequence of Upgrades by the Upgrade Tool

To upgrade an LSP or gateway with the Upgrade Tool, the LSP or gateway must already be administered and registered with the primary controller. To check, use the Query Versions option on the Upgrade Tool navigation pane (on the left side of the Upgrade Tool screens). The Query Versions screen will show an IP address next to each registered LSP and gateway.

The Upgrade Tool upgrades components of a configuration in the following order:

· All LSPs you specify

· The media gateways and their media modules

· The primary controller

NOTE: For an S8700/S8710 Media Server, the active server is upgraded after the standby server.

Because the LSPs are upgraded before the media gateways, the Upgrade Tool can use the TFTP server capability of the LSPs to supply the upgrade firmware to the gateways. In these cases, the Upgrade Tool uses the firmware that was bundled in the upgrade software (the .tar file) and automatically copied to each LSP’s TFTPboot directory.

NOTE: You cannot copy individual firmware files for the gateways or media modules to the TFTPboot directory of an LSP or S8300 primary controller. Only those files in the .tar file can be copied to the TFTPboot directory. Therefore, make sure the firmware in the .tar file is the most recent firmware available before using an LSP’s TFTP server for gateway upgrades.

An S8300 primary controller can also serve as the TFTP server for the gateways that do not have LSPs. However, as with an LSP used as a TFTP server, make sure the firmware in the most recently installed .tar file on the primary controller is the most current. To use the S8300 TFTP server in this case, the S8300 must be running Communication Manager R2.1 or higher release of software.

If you cannot be sure the .tar file has the most current firmware, you can use any TFTP server (or for G350 Media Gateways, any FTP server) in the customer’s network to supply the upgrade firmware.

Figure 1: Configurations supported by the Upgrade Tool

Special Considerations for an S8700 or S8710 Media Server

If you run the Upgrade Tool from an S8700/S8710 Media Server, start each upgrade session from the active server. The upgrade of each target LSP or gateway begins and ends from the same physical media server. If, during an upgrade session, an interchange occurs such that the standby server (Server y) becomes the active server, the originally active server (Server x) will continue with any upgrades in the session that you started until they are complete. The status for LSP or gateway upgrades that you run on a particular server will be shown on that server only. The upgrade status on the two servers will therefore be different.

NOTE: This aspect of upgrade status is a difference from the Upgrade Tool on Communication Manager R2.0. For more information, see Job Aid: Upgrade Tool and Worksheets for Avaya S8300 (LSP) Media Server and Avaya G350 and G700 Media Gateways, November, 2003.

To view the current upgrade status if an interchange occurs, log in to the actual IP address or host name of the S8700/S8710 server that you used to do the upgrade, not the alias address or alias name for the active server. When scheduling further upgrade jobs, you must log in to the newly active server to run the tool.

When you upgrade an S8700/S8710 Media Server, you run the Upgrade Tool from the active server (Server x). The Upgrade Tool then upgrades the media gateways you selected and the standby server (Server y). When these upgrades are complete and the standby server (Server y) has rebooted, an interchange occurs automatically, so the standby server (Server y) becomes active and the active server (Server x) becomes standby. The Upgrade Tool then continues running on the server (Server x) it had been running on prior to the interchange and upgrades Server x.

The newly active server (Server y) remains active when the upgrades are complete. For the upgrades that you started before the interchange, there will be no status data on the server that is active after the interchange (Server y). The upgrade status data is available only on the server on which the upgrade was started (Server x).

CAUTION: After an interchange, do not start another upgrade on the newly-active server until the current upgrade has finished. To see when the upgrade has finished, access the Upgrade Tool from the server on which you started the upgrade and use the View Active and View Prior menu options. The View Active screen shows the status of devices while the upgrade is running. The View Prior display shows when the upgrade is complete.

Figure 2: Upgrade process of the S8700/S8710 Media Server

Software and Firmware You Can Upgrade with the Upgrade Tool

The Upgrade Tool allows you to upgrade the following software and firmware:

· The S8300 software contained in the .tar file (for the primary controller as well as LSPs)

· License files for the primary controller and LSPs

· Firmware for the media gateway processors and media modules

The .tar software and firmware file

The .tar file for upgrades contains the software for upgrading the media servers. It also contains media gateway and media module firmware that was up-to-date at the time the .tar file was made available. Though the Upgrade Tool can conveniently use firmware from the TFTP server of the upgraded LSP to upgrade media gateways, only firmware in the .tar file can be loaded on to the LSP’s TFTP server. This firmware may not be the most recent. Therefore, check the firmware versions contained in the .tar file to make sure they are the latest before you install firmware using the LSP’s TFTP server.

If the firmware versions contained in the .tar file are not the latest, then the latest firmware files must be uploaded to a TFTP server other than the LSP or the primary controller. Alternatively, for a G350 Media Gateway, the files can be uploaded to an FTP server.

NOTE: The /var/ftp/home/pub directory on the primary controller may be used as the FTP server for firmware upgrades of G350 Media Gateways and their respective media modules. In this case, the Upgrade Tool can install the firmware files from the primary controller onto every connected G350 Media Gateway you identify.

Licenses

Each LSP, as well as the primary controller, needs a new license file for the upgrade. The Upgrade Tool also allows you to install new license files on the primary controller and LSPs. License files must be copied to the /var/ftp/home/pub directory on the primary controller in order for the Upgrade Tool to be able to install them. In addition, each license file must have a System ID (SID) and Module ID (MID) that matches the SID and MID of an LSP or the primary controller.

Software and firmware filenames

For all upgrades, you need to enter the software and firmware filenames in the appropriate fields on the Upgrade Tool’s Schedule Upgrade screen. The correct filenames should first be entered on the Upgrade Tool Worksheets. The software/firmware filenames have a different format for each type of device. The following table shows example filenames for each type of device.

Table 1: Example Software and Firmware Filenames

Component

Filename Example

S8700 or S8710 Media Server (primary controller)

S8x00-02.2-26.0.411.0.tar

S8500 Media Server (primary controller)

S8x00-02.2-26.0.411.0.tar

S8300 Media Server (primary controller)

S8x00-02.2-26.0.411.0.tar

LSP Software

S8x00-02.0-00.0.411.0.tar

LSP or primary controller update file name

02.1.411.0-0001.tar.gz

G350 Processors

G350 Processor

g350_sw_21_11_0.bin

G350 Device Manager

g350_emweb_1_0_7.bin

MM312 DCP Media Module

mm312v6.fdl

MMANALOG Media Module (Integrated Analog)

mmanalogv3.fdl

G700 Processors

P330 Stack Processor

viisa3_12_1.exe

P330 Device Manager

p330Tweb.3.8.6.exe

G700 Media Gateway Processor (MGP)

mgp_21_11_0.bin

VoIP Media Module and Motherboard VoIP (MM760)

mm760v3.fdl

Media Modules (G350 and G700)

MM710 E1/T1 Media Module

mm710v3.fdl

MM711 Analog Port/Trunk Media Module (version 6 or earlier)

mm711v16.fdl

MM711 Analog Port/Trunk Media Module (version 7)

mm711h7v21.fdl

MM711 Analog Port/Trunk Media Module (version 20or later)

mm711h20v54.fdl


mm712v14.fdl

MM714 Analog Media Module

mm714v5.fdl


mm717v3.fdl

MM722 BRI Media Module

mm722v3.fdl

Prerequisite Tasks for Running the Upgrade Tool

NOTE: To upgrade LSPs or media gateways from R1.3 to Communication Manager R2.2, you must use the instructions in “Upgrading an Existing S8300A to R2.2” in Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, Issue 7, 555-234-100. For an upgrade from R2.0 or R2.1, you may use the Upgrade Tool built into the R2.0/R2.1 software to upgrade LSPs and G700 and G350 Media Gateways.

LSPs must always have Communication Manager software that is equivalent to or more recent than the issue of software on the primary controller. Otherwise, the LSPs will not be able to synchronize translations with the primary controller and calls on the LSP’s gateway cannot be processed. Though you, technically, can use the R2.2 Upgrade Tool to upgrade LSPs that are currently using R2.0 or later software, for proper call-handling operation, LSPs should already have Communication Manager Release 2.2 or higher software if the primary controller does. As a result, you normally use the Upgrade Tool on Communication Manager R2.2 only to upgrade a primary controller, LSPs, and G350 and G700 Media Gateways to higher software.

The tasks necessary to prepare for an upgrade of a primary controller, an LSP, and/or media gateway are the same, regardless of whether you are performing the upgrade manually or by using the Upgrade Tool. For a detailed description of these tasks, see:

· Installation and Upgrades for the Avaya G350 Media Gateway, 03-300395

· Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, Issue 7, 555-234-100

· Upgrading Software and Firmware ( Avaya S8500 Media Server, Issue 3, 555-245-111

· Upgrading Software and Firmware ( Avaya S8700 Series Media Server, Issue 3, 555-245-115

Table 2: Prerequisite Task List to Using the Upgrade Tool

Task

Description

Get Upgrade Tool Worksheet s or planning forms from the Project Manager

The Upgrade Tool Worksheets or planning forms specify the latest available versions of software and firmware. The Upgrade Tool Worksheets or planning forms list the target software and firmware versions. The worksheets also indicate what TFTP and FTP servers the tool must use, along with their IP addresses, logins and password, if any.

Note: You can use the Query Version feature of the Upgrade Tool to automatically check the version of software and firmware currently installed on each upgrade target (S8300, S8500, S8700, S8710, G350, or G700).

Get the system IDs (SID) and module IDs (MID) used to create license files

The SIDs and MIDs may already be included in the planning forms from the project manager.

To get new license files for a primary controller or LSP upgrade, you need the system ID of each server, primary controller or LSP, you are upgrading. You can determine the system ID by running the Query Versions option in the Upgrade Tool. You can also determine the system IDs by displaying the System Parameters Customer Options screen on each server’s system access terminal (SAT) command line interface. You access this screen with the SAT command display system-parameters customer-options.

For older systems, you may need the serial number of the gateway that houses an LSP. You can determine the serial number by going to the Maintenance Web Interface and clicking on Serial Numbers on the main menu. Alternatively, you can log in to the media gateway (mgp) with Telnet and enter the show system command.

Check the number of allocated ports (S8300 only)

Releases 2.0 and higher of Communication Manager support a maximum of 900 ports if the S8300 is a primary controller. If the existing system has more than 900 ports allocated, then there may be a problem with the upgrade and you need to escalate.

//is this being fixed?//

Ask the customer to check the system for the maximum number of ports. This can be done via the SAT command, display system-parameters customer options. Verify that the Maximum Ports: field is 900 or less.

Table 2: Prerequisite Task List to Using the Upgrade Tool (Continued)

Task

Description

Check that the customer has an FTP server for backing up data (S8300 only)

During the installation and upgrade procedures, you will need to back up the system data to an FTP server. Normally, you will use an FTP server on the customer’s LAN for backups. To do this, you will need information on how to get to the backup location — login ID and password, and the IP address and directory path on the FTP server. Check with your project manager or the customer for this information.

Complete the RFA process

For each LSP or primary controller you are upgrading, complete and download the license file to your laptop. A license filename has the format SVm-.lic, where is the system ID, is the version of the license, and is the module ID. For example, in the license file name S13870V3m22-030701-102344.lic, the system ID is 13870 and the module ID is 22.

NOTE: Your project manager may perform the RFA process and send you the license file(s).

For more information, see “Upgrading an Existing S8300B to R2.2” in Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, Issue 7, 555-234- 100, ”Downloading License and Avaya Authentication Files” in Upgrading Software and Firmware Avaya Series Media Server, Issue 3, 555-245-115, or ”Downloading License and Avaya Authentication Files” in Upgrading Software and Firmware Avaya S8500 Media Server, Issue 3, 555-245-111.

Get all necessary software.

The file containing the S8300/S8700/S8710/S8500 software and G700 and G350 firmware has a .tar extension. The .tar file is on a CD-ROM that you take to the site. You may also need the most recent versions of the software update (patch) files, G700/G350 firmware files, and media module firmware files. You obtain these files from the Avaya Support web site and download them to your laptop.

The .tar file (and Communication Manager update file, if necessary) must also be downloaded to each LSP prior to running the upgrade. Normally, these files are downloaded locally, at each LSP’s location, from a technician laptop. However, the .tar and update file can also be downloaded to an LSP from any computer that has a network connection to the LSP.

Note: For a download of the .tar file, the customer’s LAN must have sufficient bandwidth since the .tar file is over 200 MB.


Task

Description

Check the current software release

You can use the Query Version feature of the Upgrade Tool to automatically check the version of software and firmware currently installed on each upgrade target (S8300, S8500, S8700, S8710, G350, or G700).

(LSPs only) Connect your laptop to each LSP.

For each LSP, the tech laptop has a cross-connect cable connected to the Services port of the S8300, and the technician configures the laptop for the connection.

Note: You can also connect over a network if the LAN bandwidth is high enough.

Download the .tar file and update file from your laptop for each LSP.

At the location of each LSP you want to upgrade, you must copy the .tar file and update file to that LSP’s/var/home/ftp/pub directory

hard drive prior to running the Upgrade Tool. Use the Upload

Download Files to Server

(via browser) option on the Maintenance Web Pages main menu.

Download G700 and G350 firmware files to an FTP or TFTP directory (for media gateways without LSPs)

For any G700 or G350 Media Gateway that does not have access to an LSP, send the individual firmware files to the customer and ask the customer to copy the files to a directory on a customer TFTP (for G700 or G350) or FTP (for G350 only) server. The Upgrade Tool reads the new firmware files from this directory on the TFTP or FTP server.

The firmware may be contained in a tar.gz file or may be available as individual firmware files. If you are sending the tar.gz file, the customer will have to unzip it.

Note: If the customer does not have a TFTP directory, the customer can create one using the downloadable TFTP Server software that is accessible at http://avaya.com/support. See instructions in the Installation and Upgrades document for the G700 Media Gateway.

For G350 media firmware upgrades, you can use the Download Files Web page to copy the G350 firmware files to the primary controller’s var/home/ftp/pub directory. In this case, the Upgrade Tool can install the firmware files from the primary controller onto every connected G350 Media Gateway you identify.

Note: Each G350 Media Gateway you are upgrading must be able to communicate with the primary controller over the network, and the primary controller must be able communicate with each G350 Media Gateway.


Task

Description

Load update files, the .tar file, and license files to the primary controller FTP directory

Use the Download Files Web page to load the appropriate Communication Manager R2.2 update files, .tar file, and license files to the media server.

From the primary controller, the Upgrade Tool can install the license files on every connected LSP. However, the Upgrade Tool can only install the .tar file and update files to the primary controller on which it is running. The Upgrade Tool cannot install software on LSPs using the .tar file or update files that you downloaded to the primary controller. Instead, LSPs require you to follow the previous step in this checklist, “Download the .tar file and update file from your laptop for each LSP.” Then, the Upgrade Tool can remotely install the upgrade and update software.

NOTE: See “Upgrading an Existing S8300B to R2.2” in Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, Issue 7, 555-234-100, “Copy license and Avaya authentication files to the media server” in Upgrading Software and Firmware Avaya S8700 Series Media Server, Issue 3, 555-245-115, or ”Copy license and Avaya authentication files to the media server” in Upgrading Software and Firmware Avaya S8500 Media Server, Issue 3, 555-245-111.

If the primary controller is an S8700, S8710 or S8500 Media Server, insert the software CD-ROM in the CD-ROM drive.

The Upgrade Tool automatically uploads and installs the upgrade software from the CD-ROM on an S8500, S8700, or S8710 Media Server.

Prepare for the Upgrade on the primary controller

Clear alarms

Check link status (S8500, S8710, and S8700 primary controllers only)

Record all busyouts

Check clock synchronization (S8500, S8710, and S8700 primary controllers only)

Disable scheduled maintenance

Busyout MMI circuit packs - high or critical reliability only (S8710 and S8700 primary controllers only)

Check for translation corruption

Back up system

Run the Upgrade Tool

See Using the Upgrade Tool.

Using the Upgrade Tool

Run upgrades at a time when the volume of voice and network traffic is low.

NOTE: If your primary controller is a duplicated S8700 or S8710 Media Server, be sure to begin any upgrades from the active server (Server x). The Upgrade Tool automatically causes an interchange once the LSPs, media gateways, other modules, and the standby media server (Server y) are upgraded. This interchange allows the Upgrade Tool to upgrade the originally-active Server x.

However, if LSPs and media gateway upgrades are not yet complete and there is an interchange such that the duplicated server (Server y) becomes the newly-active server, any devices listed in the scheduled upgrade that started on the originally-active server (Server x) will continue to be upgraded from Server x, assuming the interchange was not due to a failure of Server x.

CAUTION: If you are upgrading, at the same time, the active (Server x) and standby (Server y) servers for an S8700 or S8710 Media Server, an interchange will occur after the original standby Server y has been upgraded. After this interchange, do not start another upgrade on the newly active Server y until the current upgrade has finished running on the formerly active Server x. You must use the Upgrade Tool’s View Prior menu option from Server x, on which you originally started the upgrade, to verify that the upgrade of Server x is complete.

Accessing the Upgrade Tool

You can access the Upgrade Tool on the S8300, S8500, S8700, or S8710 Media Server with the following steps:

Access the media server by connecting a crossover cable to the Services port or by connecting over the LAN. Be sure you have appropriately configured your laptop settings for this connection (see Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Upgrading Software and Firmware Avaya S8500 Media Server, 555-245-111, or Upgrading Software and Firmware Avaya S8700 Series Media Server, 555-245- 115).

Open a browser on your laptop and connect to the media server’s IP address. For a direct connection through the Services port, the IP address is 192.11.13.6. For a LAN connection, use the server’s IP address on the LAN.

1. Log in as craft. Or, if you are a customer, log in with a customer super user login

2. At the media server home page, click Launch Upgrade Tool.

The system displays the Upgrade Tool Home Page.

Figure 3: Upgrade Tool home screen

Running a query for installed versions of software and firmware

3. Click Query Versions to view the software and firmware versions for each LSP and gateway registered with the primary controller.

Figure 4: Query Versions select screen

4. Select Initiate New Query and click Submit to set up a new query.

This could take several minutes, depending on how many LSPs and gateways are in the configuration. The system automatically finds and lists each primary controller (including the active and standby S8700/S8710 Media Servers), LSP, G350 Media Gateway, and G700 Media Gateway registered with the primary controller. Additionally, for each media gateway, the Upgrade Tool lists each media module.

Since this screen can be very long, hot links are provided in each section to jump to the other sections.

Figure 5: Query Versions definition screen (S8300 version)

5. Enter data for the devices you want to query.

You can select all or some of these devices to be queried. You can enter a common Logon ID and Password that will be used to access all gateways for which you do not enter an override value. You can save your entries on the screen and return to the screen later to run a query. This capability allows you to stop and research necessary information without losing your entries.

6. When finished, press Query to start the query.

While the query is running, the system displays an “In-Progress” screen that is updated every 10 seconds.

If you wish to stop the query before it completes, click the Stop button.

When the query is finished, the system displays the complete Query Version Results screen and changes the Query Status from “In-Progress” to “Complete”.

Figure 6: View Prior Query results screen (S8700 version)

7. Note the versions of the devices in the network.

If you leave this screen, you can click Query Versions, select View Last Query Result, and click Submit to review the results again without rerunning a query.

Running the upgrade

8. To set up and schedule upgrades, click Schedule Upgrade. The system displays all server, LSP and gateway targets that are administered.

Figure 7: Schedule Upgrade screen

Figure 8: Schedule Upgrade screen, continued

Figure 9: Schedule Upgrade screen (continued - S8300 version)

Figure 10: Schedule Upgrade screen (continued)


9. Fill in all appropriate fields. Click the Help button for information about the fields on the screen.

NOTE: The file names must be entered in the format shown. Do not change the names of the firmware files in the process of loading them onto the TFTP or FTP servers.

Use the information from the planning forms or Upgrade Worksheets to complete the Software/Firmware fields.

Use the following guidelines for setting up the upgrade:

· If the customer uses a common Logon ID and Password for multiple gateways, complete the Common G350/G700 Logon Values fields.

· If the customer has a centralized TFTP server for use by multiple G700 or G350 Media Gateways or the customer has a centralized FTP server for use by multiple G350 Media Gateways, complete the Common TFTP/FTP Server Values fields.

· If you use the /var/home/ftp/pub directory for the FTP server for G350 firmware upgrades, the directory name is pub. Do not enter the entire directory pathname. The IP address of the primary controller connects automatically to /var/home/ftp.

Also, for an S8700 or S8710 Media Server, use the physical IP address of the server on which the firmware files are loaded, not the alias IP address of the active server.

· Use the Max Sessions field to specify how many gateways can be simultaneously connected to a TFTP or FTP server for upgrading. The number must be between 1 and 20 inclusive. If you do not specify a number, the Upgrade Tool defaults to 6, such that six gateways at a time are connected to the TFTP or FTP server.

· If any gateways require unique logon values or unique TFTP or FTP servers, complete the Override Common Values for G350 and G700 Targets fields. You can enter override values for the following:

· The logon and password of the unique FTP server

· The IP address of the unique TFTP or FTP server

· The directory on the TFTP or FTP server that contains the firmware files

· The logon information for the gateway

· If any override fields are left blank, the values entered in the Common fields are used.

· If you check Use FTP for any row of values, the Upgrade Tool assumes the IP address and directory apply to an FTP server. If you use the primary controller’s var/home/ftp/pub directory for FTP, the directory name you enter is pub.

· Some upgrades may time out due to traffic on the network and limitations on how long the Upgrade Tool will allow an upgrade to continue. The upgrade of a single LSP must be complete in one hour. The upgrade of a media gateway has a 30 minute limit.

Since the media gateway (MGP) firmware files, in particular, are fairly large, these may cause a timeout during an upgrade to a remote location.

What you enter in the TFTP Directory field depends on the type of TFTP server you are using.

· If the TFTP server is an S8300 or LSP, enter the path to the firmware files relative to the /tftpboot directory. For example, if the firmware files are in /tftpboot/cm2.0/218.0, enter cm2.0/218.0.

NOTE: If the files are in C:\tftpboot on the S8300 server/LSP and there is no subdirectory, leave the TFTP Directory field blank.

· If the TFTP server is an Avaya Windows server, enter the path to the firmware files relative to the C:\tftpboot directory. For example, if the firmware files are in C:\tftpboot\cm2.2\218.0, enter cm2.2\218.0.

NOTE: If the files are in C:\tftpboot on the Avaya server and there is no subdirectory, leave the TFTP Directory field blank.

· If the TFTP server is a customer server, ask the customer how their TFTP server is set up.

NOTE: A TFTP server must be accessible over the LAN from the gateway you are upgrading. The FTP server must be accessible over the LAN from the G350 Media Gateways you are upgrading.

10. Click Schedule to set up the upgrade schedule or Run Now to run the upgrades immediately.


The Start Date and Time fields are required, but the Stop Date and Time fields are not. Use the Stop Date and Time to ensure that no upgrades occur during peak traffic time. No new upgrades will be started after the stop time, but upgrades in progress at that time will continue to completion.

11. Click Submit to complete the upgrade schedule.

The upgrades will run according to the schedule you set. The Upgrade Tool automatically saves translations, reboots the media gateways and servers, and makes the upgrades permanent.

Checking the status of an upgrade

You can check the status of prior upgrades or the upgrade currently running.

View the status of a prior upgrade

To check the status of prior upgrades, do the following:

12. Click View Prior to view completed upgrades.

The View Prior screen enables you to view the status of the last four upgrades.

Figure 13: View Prior Query select screen

13. Select the upgrade that you wish to view and click View. The View Prior screen shows the upgrade status of each component for the upgrade selected.

This screen shows up to four selections, depending on how many upgrades have been started from this server. The screen does not show upgrades that you started from another server, such as the other server in an S8700/S8710 pair.

Normally, the Upgrade Tool on the S8700/S8710 server from which the upgrade was originally started will contain all upgrade data. The server that becomes active because of an interchange during the upgrade process will not contain data for the upgrade.

Figure 14: View Prior Query results screen

Figure 15: View Prior Query results screen, continued

Figure 16: View Prior Query results screen, continued

When an upgrade is complete, Completed appears in the Status column for each target component. If an upgrade fails, Error is reported in the Status column. For a description of other status messages, click the Help button to view the online help.

If the upgrade times out, check the status of the upgrade with the View Prior screen. Check to see what version of firmware the endpoints have to determine which devices still need to be upgraded.

View the status of the upgrade in progress

To review the status of an upgrade in progress, click View Active to view upgrades currently in progress.

NOTE: If you use the View Active screen while upgrading the server on which the Upgrade Tool itself is running, the screen displays an error while the server is rebooted. To view the successful status of the upgrade of the server on which the Upgrade Tool is running, you must use the View Prior screen after the upgrade is complete.

However, the upgrade is not complete until the following events occur:

· The server reboots

· Additional database updates occur after the reboot

· The upgrade is made permanent.

Making the upgrade permanent takes at least an additional five minutes beyond the reboot.

You can check to see when the upgrade is complete by checking the View Prior upgrade screen periodically or by doing the following:

1. Access the Maintenance Web pages on the server from which you started the upgrade.

2. Select Boot Partition from the menu on the left.

3. Check to see if a physical partition is identified as both the boot partition and the active partition, and that the physical partition contains the most recent software release.

Completing the Upgrade

Perform the following tasks to complete the upgrades.

Target

Description

Complete the Upgrade Process on the Primary Controller

Verify operation of the media server(s)

Record busyouts

Enable scheduled maintenance

Verify survivable remote port networks (S8700 and S8710 only)

Release MMI (S8700/S8710 high and critical reliability systems only)

Busyout trunks that were busied out before the upgrade

Check for translation corruption

Resolve alarms

Back up the system

Release alarm suppression on the active server (S8700/S8710 only)

Upgrade Tool Worksheets

Software and Firmware Upgrade File Names

Complete the following worksheet to record software and firmware upgrade file names. These names should also be available from the normal planning forms from your project manager. See Software and Firmware You Can Upgrade with the Upgrade Tool on page 6.

Table 3: Upgrade software and firmware file names

Items for Upgrading

New file name for target

.tar file for S8700 or S8710 Media Server (primary controller)

.tar file for S8500 Media Server (primary controller)

.tar file for S8300 Media Server (primary controller)

.tar file for LSP

Update file for LSP and primary controller

G350 Only

G350 Processor

G350 Device Manager

MM312 24-port DCP Media Module

MMANALOG (Integrated Analog)

G700 Only

Media Gateway Processor (MGP)

P330 Stack Processor

P330 Device Manager

MM760 VoIP Media Module and Motherboard VoIP

G350 and G700

MM710 E1/T1 Media Module

MM711 Analog Port/Trunk Media Module (version 6 or earlier)

MM711 Analog Port/Trunk Media Module (version 7)

MM711 Analog Port/Trunk Media Module (version 20 or later)


MM714 Global Analog Media Module

MM717 24-port DCP Media Module

M720 BRI Media Module

MM722 BRI Trunk Media Module

Upgrade Targets

Complete the following worksheets to record upgrade targets and the upgrade software they require.

LSPs to Upgrade

Complete the following table only if you are not upgrading every LSP administered on the primary controller. This table lists each LSP that should be upgraded. To obtain a list of possible LSPs, you can use the Query Version feature of the Upgrade Tool. (You could also use the display lsp SAT command in Communication Manager on the primary controller.)

Make additional copies of this table if necessary.

Table 4: LSP Upgrade Targets

LSP Node Name

LSP IP Address

Common G350/G700 Gateway Values

Multiple media gateways may have the same login and password values. In this case, enter the login information in the following table:

Table 5: Global Settings for G350/G700 Gateway

G350/G700 Root Login ID

G350/G700 Password

Common TFTP Server Values (for G700 Media Gateways)

Multiple G700 media gateways might receive firmware updates from the same TFTP server. In this case, enter the TFTP server information in the following table:

Table 6: Global Settings for TFTP Server

TFTP Server IP Address

TFTP Server Directory

Common FTP Server Values (for G350 Media Gateways)

Multiple G350 media gateways might receive firmware updates from the same FTP server. In this case, enter the FTP server information in the following table:

Table 7: Global Settings for TFTP Server

FTP Server IP Address

FTP Server Directory

FTP Server Login ID

FTP Server Password

G700 Media Gateways to Upgrade

Complete the following table only if you cannot use the global settings for the G700 Media Gateways. This table lists each gateway that should be upgraded and its TFTP server information. To obtain a list of possible gateways, you can use the Query Version feature of the Upgrade Tool. You can also use the list media-gateway SAT command in Communication Manager on the primary controller.


Table 8: G700 Media Gateways to Be Upgraded

G700 Media Gateway Node Name

G700 Media Gateway IP Address

TFTP Server IP Address (If not global)

TFTP Server Directory (If not global)

Upgrade This Gateway?

Gateway Root Login(If not global)

Gateway Password (If not global)

G350 Media Gateways to Upgrade

Complete the following table only if you cannot use the global settings for all G350 Media Gateways. This table lists each gateway that should be upgraded and its FTP server information. To obtain a list of possible gateways, you can use the Query Version feature of the Upgrade Tool. You can also use the list media-gateway SAT command in Communication Manager on the primary controller.


Table 9: G350 Media Gateways to Be Upgraded

G350 Media Gateway Node Name

G350 Media Gateway IP Address

FTP Server Login ID (If not global)

FTP Server Pass-word (If not global)

FTP Server IP Address (If not global)

FTP Server Directory (If not global)

Upgrade This Gateway?

Gate-way Root Login(If not global)

Gate-way Pass-word (If not global)

NOTES:

All trademarks identified by the ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.

Copyright ( 2004 Avaya Inc. All rights reserved.

8

9

_1089707343.doc

Documents

Avaya Installation Wizard (AIW) · Web viewA license filename has the format SVm-.lic, where is the system ID,