Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

Transcription

1 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers Issue 1 May 2009

2 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full support information, please see the complete document, Avaya Support Notices for Hardware Documentation, document number To locate this document on our Web site, simply go to and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site:

3 Contents Chapter 1: Introduction Firmware upgrades Additional documentation Upgrading to Communication Manager Release Upgrade tool The Avaya Installation Wizard Manage Software Web page Avaya Software Update Manager Communication Manager Servers managed by Software Update Manager Error resistant download via https Upgrade procedures Upgrading to Communication Manager Release Upgrade sequence Avaya one-x portal dependency Duplicated Enterprise Survivable Server (ESS) upgrade Upgrade procedures for Duplicated ESS Servers Duplex ESS upgrade workflow Resources How this book is designed and organized Chapter 2: Upgrading Software on Servers Common prerequisites for all upgrades Checklist of tasks to perform before you go on site RFA license and authentication files Generating and retrieving license and authentication files Logins and passwords Platform/PNC license settings for the S8700-Series Server Checking for an FTP/SCP/SFTP Server or Compact Flash for Backing up Preserving connections while upgrading an S8700-Series Server Connections not preserved Tools to preserve connections during an upgrade Manual steps to preserve connections during an upgrade Upgrade modules Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/ C/D Server (Migration from S8300A to S8300C/D) Introduction Pre-requisites Pre-upgrade service pack requirements Tasks checklist Issue 1 May

4 Contents Upgrading Communication Manager from 2.x, 3.x or 4.x to 5.x and replacing S8300B Server with an S8300C/D Server (Migration from S8300B to S8300C/D) Introduction Pre-requisites Pre-upgrade service pack requirements Tasks checklist Upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP 67 Introduction Prerequisites Tasks Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage Software Prerequisites The need to restore IP telephone files TN8412AP SIPI circuit pack upgrades Upgrading LSPs and media gateways, if any Preupgrade tasks Upgrading the MPC firmware Connecting to the server Starting a SAT session Checking link status with SAT (main server only) Recording all busyouts Checking synchronization with the SAT (main server only) Disabling scheduled maintenance with the SAT (main server only) Checking for translation corruption Saving a copy of the 4600-series telephone configuration file, if any Accessing the server s web interface Copying files to the server Resolving alarms Ensuring a super-user login exists Backing up recovery system files Verifying the backup Suppressing alarming Upgrade tasks Connecting the CD/DVD-ROM drive to the server Copying Communication Manager to the server Removing the CD-ROM from the CD-ROM drive Installing Communication Manager on the server Issue 1 May

5 Contents Rebooting the server Verifying reboot progress Verifying software operation Checking system status Installing security and Communication Manager service pack updates, if any Installing the RFA license file and authentication file Copying IP telephone firmware to the server, if necessary Making the upgrade permanent on the server Post-Upgrade tasks Accessing the server command line interface with ssh protocol Enabling scheduled maintenance with SAT (main only) Busying out previously busied-out trunks Checking for translation corruption Resolving alarms Backing up recovery system files Releasing alarm suppression (optional) Logging off all administration applications Registering Communication Manager Upgrading Communication Manager on Avaya S8500-Series Server MAIN/ESS/LSP from R2.x/ R3.x/R4.x/R5.x to Release 5.2 using Manage Software Prerequisites The need to restore IP telephone firmware files TN2312AP/BP IPSI circuit pack upgrades Upgrading LSPs and media gateways, if any Upgrading firmware on media gateways and media modules Upgrade of Communication Manager on the ESS servers Preupgrade tasks Connecting to the server Upgrading the SAMP firmware Stopping call processing on the LSPs or ESS servers if being used (main server only) Starting a SAT session Checking link status with SAT (main server only) Recording all busyouts (main server only) Checking synchronization with the SAT (main server only) Disabling scheduled maintenance with the SAT (main server only) Checking for translation corruption with the SAT Accessing the System Management Interface (SMI) Copying files to the server Issue 1 May

6 Contents Resolving alarms Ensuring a super-user login exists Backing up recovery system files Verifying the backup Installing a DIMM in an S8500B Server Suppressing alarming Saving a copy of the 4600-series telephone configuration file, if any Checking software release, only if starting from R2.x Activating the preupgrade service pack, only if starting from R2.x Upgrade tasks Inserting the Communication Manager CD into the server Copying Communication Manager to the server Installing Communication Manager on the server Rebooting the server Verifying reboot progress Verifying software operation Checking system status Making the upgrade permanent on the server Installing security and Communication Manager service pack updates, if any Accessing the server command line interface with ssh protocol Configuring the ESS or LSP for compatibility with an XL configuration Checking system status Creating a customer login (if necessary) Installing the RFA license file and authentication file Stopping and starting ESS servers Setting the Processor Ethernet Post-Upgrade tasks Copying IP telephone firmware to the server, if necessary (main servers only) Enabling scheduled maintenance with SAT (main only) Busying out previously busied-out trunks Checking for translation corruption Resolving alarms Backing up recovery system files Releasing alarm suppression (optional) Starting call processing on the LSPs and ESSs, if any (main server only) Logging off all administration applications Registering Communication Manager Issue 1 May

7 Contents Upgrading Communication Manager on the S8700-Series main or ESS servers from R2.x/R3.x/ R4.x/R5.x to 5.2 using Manage Software Prerequisites The need to restore IP telephone firmware files TN2312AP/BP IPSI circuit pack upgrades Upgrading media gateways, LSPs and ESS servers, if being used Upgrading firmware on media gateways and media modules Upgrade of Communication Manager on the ESS servers Duplex ESS upgrade workflow Verifying the status of ESS servers Preupgrade tasks Stopping call processing on the LSPs or ESS servers if being used (main server only) Clearing the ARP cache on the laptop Clearing the Web browser cache on the laptop Connecting to the active server Accessing the System Management Interface (SMI) Starting a SAT session Checking link status with SAT (main server only) Recording all busyouts (main server only) Checking synchronization with the SAT (main server only) Disabling scheduled maintenance with the SAT (main server only) Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) Checking for translation corruption Accessing the System Management Interface (SMI) Copying files to the server Resolving alarms Ensuring a super-user login exists Backing up recovery system files on the active server Verifying the backup Suppressing alarming Disconnecting from the active server Connecting to the standby server Resolving alarms Clearing the ARP cache on the laptop computer Clearing the Web browser cache on the laptop Backing up files on the standby server Verifying the backup on the standby server Suppressing alarming on the standby server Disconnecting from the standby server Issue 1 May

8 Contents Removing a DAL1 or installing a DAL2 card Placing or Replacing the server in the rack Restoring power to the server Verify that the DAL2 card is installed correctly Disconnecting from the standby server Connecting to the active server Accessing the active server s web interface Selecting the Preupgrade Step Disconnecting from the active server Upgrade tasks for the first server Connecting to the standby server Clearing the ARP cache on the laptop Checking the software release on the standby server Activating the preupgrade service pack on the standby server (R2.x only) Inserting the Communication Manager CD-ROM into the standby server Copying Communication Manager to the server Upgrading Communication Manager on the server Rebooting the standby server Verifying reboot progress Suppressing alarms Verifying software operation Performing an integrity check on the first S8700-Series Server Making the upgrade permanent on the server Installing security and service pack updates, if any Configuring the Processor Ethernet interface (on the ESS) Accessing the server command line interface with ssh protocol XL configuration considerations Performing an integrity check on the first S8700-Series Server Releasing the standby server Interchanging the servers Performing an integrity check on the first S8700-Series Server Creating a super-user login Installing the new license and Avaya authentication files on newly active server Stopping and starting the ESS servers Disconnecting from the newly active server Upgrade tasks for the new standby server (second server) Removing a DAL1 or installing a DAL2 card Placing or Replacing the server in the rack Issue 1 May

9 Contents Restoring power to the server Verify that the DAL2 card is installed correctly Disconnecting from the server Connecting to the standby server Resolving alarms Accessing the standby server s maintenance interface Checking the software release on the standby server Activating the preupgrade service pack on the server (R2.x only) Inserting the Communication Manager CD into the server Copying Communication Manager to the server Upgrading Communication Manager on the server Rebooting the server Verifying reboot progress Suppressing alarms Verifying software operation Performing an integrity check on the second S8700-Series Server Making the upgrade permanent on the server Installing security and service pack updates, if any Configuring the Processor Ethernet interface (on the ESS) Accessing the server command line interface with ssh protocol XL configuration considerations Performing an integrity check on the second S8700-Series Server Verifying the operation of the servers Setting Server A/Server 1 active for ESS, if necessary Post-Upgrade tasks Copying IP telephone firmware to the server, if necessary (main servers only) Disconnecting from the standby server Administering the node name for the IP-alias address for the duplicated ESS servers (after ESS upgrade and pre-upgrade Main) Enabling scheduled maintenance with SAT (main server only) Releasing MMI circuit packs in duplicated control network using SAT, (main server only) 204 Busying out previously busied-out trunks (main server only) Checking for translation corruption with SAT (main server only) Resolving alarms Backing up files on the active server Releasing alarm suppression (optional) Logging off all administration applications on the active server Disconnecting from the active server Connecting to the standby server Issue 1 May

10 Contents Resolving alarms Backing up files on the standby server Releasing alarm suppression (optional) Starting call processing on the LSPs and ESSs, if any Logging off all administration applications Registering Communication Manager Chapter 3: Upgrading Firmware on TN circuit packs and Ethernet switches Prerequisites Upgrade modules Upgrading firmware on the IPSIs and SIPIs Prerequisites Access the Web Interface Determining current IPSI firmware Upgrade Tasks Pre-Upgrade tasks Copying files to the server Upgrade tasks Interchanging the IPSIs (duplicated control network only) Post-upgrade tasks Upgrading firmware on TN circuit packs Upgrading firmware on the Avaya Ethernet Switch Appendix A: Accessing the server Connecting to the server directly Computer specifications Network configuration Connecting to the server remotely over the network Connecting to the server remotely over a modem Setting up a dial-up connection Dialing up to the server Finding the IP address of the active server (duplicated servers) Disabling the boot timeout of the SAMP board Accessing the System Management Interface (SMI) Using the command line interface Accessing the server command line interface with ssh protocol Logins Issue 1 May

11 Contents Network configuration Browser settings Connecting directly to the server Connecting remotely through the network Appendix B: DAL: Removing or Installing Verifying which DAL is installed Removing power from the server Removing the server from the rack Removing the cover from the server Removing the PCI riser cage Removing the DAL Installing the DAL2 in the S8710 or S Replacing the PCI riser cage Replacing the cover on the server Installing the DAL2 in the S8730 Server Index Issue 1 May

12 Contents Issue 1 May

13 Contents Issue 1 May

14 Contents Issue 1 May

15 Chapter 1: Introduction This document describes procedures for upgrades of Avaya telecommunication products that use Communication Manager. An upgrade is an installation of a newer release of software on an existing server or a newer version of firmware on a hardware component. Hardware components include: Media gateways Media modules Ethernet switches Programmable circuit packs The information in this book describes upgrades to Linux-based servers only. For more information about upgrades of Communication Manager on the DEFINITY Server CSI, see Installation, Upgrades, and Additions for Avaya CMC1 Media Gateways, The most common type of upgrade is an update of Communication Manager on a server. Upgrades can be either major or minor. A minor upgrade is a dot release. Some upgrade paths require a change in hardware, for example, DAL1 cards will need to be replaced with DAL2 cards. On occasion it is necessary to install a service pack in between releases of Communication Manager. A service pack is also known as a software update or patch. This process updates a portion of Communication Manager without changing the release. On occasion, an upgrade may require a pre-upgrade or post-upgrade service pack or both. CAUTION:! CAUTION: Read this caution if you are upgrading a main server with one or more LSPs from Communication Manager Release to Release 5.x. As part of the standard upgrade process, an LSP must upgrade before the main server. However, if the LSP upgrades from Release to Release 5.x, it will not get a filesync from the main server until the main server upgrades from Release to Release 5.x. In the timeframe after the LSP upgrade and before the main sever upgrade, the LSP continues to use the last translations it received before the upgrade. In some customer environments, an LSP running out-of-date translations might be undesirable. For example, if the main server remains on Release for an extended period of time after the upgrade of an LSP to Release 5.x, the risk is higher that the translations on the LSP may become seriously out-of-date. In this example, the customer may choose to upgrade to Release 4.x instead of Release 5.x. Issue 1 May

16 Introduction Important:! Important: S8700-Series Servers cannot be upgraded to Communication Manager 5.0 or later releases. For Communication Manager 5.0 and later releases, the S8700 Server must migrate to an S8710, an S8720, or an S8730 Server. For more information on how to migrate the S8700-Series Servers, see Migrating Avaya Servers and Media Gateways, Important:! Important: Upgrading a S8710 Server or an S8720 Server with hardware duplication to Communication Manager 5.x and later releases requires a DAL2 card. For information on how to replace a DAL1 with a DAL2 or on how to install a DAL2, see DAL: Removing or Installing on page 241. Important:! Important: S8500A Servers cannot be upgraded to Communication Manager 5.0 or later releases. For Communication Manager 5.0 or later releases, an S8500A Server must migrate to an S8500C Server, S8510 Server, an S8710 Server, an S8720 Server, or an S8730 Server. For information on how to migrate an S8500A Server, see Migrating Avaya Servers and Media Gateways, CAUTION:! CAUTION: When you are upgrading the server as a primary controller, you must check Latest Communication Manager Software & Firmware Compatibility Matrix for the supported upgrade paths. If you attempt to upgrade the server to a release that is not supported as an upgrade path, you might corrupt the translations. Also, you must check Latest Communication Manager Software & Firmware Compatibility Matrix for compatibility of software loads between the primary controller and any LSPs or ESS servers. If the software loads of the primary controller and the LSPs/ESS servers are incompatible, then file synchronization between the primary controller and the LSPs/ESS servers can cause translation corruption on the LSPs/ESS servers. To check the Latest Communication Manager Software & Firmware Compatibility Matrix from any computer, access Select Downloads > Latest TN Circuit Pack, Media Server, and Media Gateway Firmware and Software Updates > Latest Communication Manager Software & Firmware Compatibility Matrix. 16 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

17 Firmware upgrades Another type of upgrade is firmware on various hardware components. These components include Branch media gateways, such as the G150, the G350, and the G700 Media modules on the branch media gateways Programmable TN circuit packs Ethernet switches, such as the C-363T or C-364T This section does not cover an upgrade of a DEFINITY switch to a Linux-based server. This process is called a migration. For more information, see Migrating Avaya Servers and Media Gateways, Important:! Important: You cannot use Upgrade Tool or Avaya Installation Wizard (AIW) for the upgrade procedures to Communication Manager Release 5.2 or later. For Release 5.2 of Communication Manager, Internet Explorer 6 and 7 are supported for use with the System Management Interface (SMI) and with Avaya Installation Wizard (AIW). For Pre-Release 5.2 use the Maintenance Web Interface, and for Release 5.2 use the System Management Interface (SMI). The term IA770 INTUITY AUDIX messaging application refers to Pre-Release 5.2 and the term Communication Manager Messaging (CMM) refers to Release 5.2 or later. For information on Migrations, see Migrating Avaya Servers and Media Gateways, For information on Conversions, see Converting Avaya Servers and Media Gateways, Firmware upgrades Several pieces of equipment require periodic firmware upgrades. This equipment includes: The IP Server Interface circuit pack (TN2312AP/BP) Programable circuit packs (TN799DP, TN2302AP, TN2602AP) Avaya Ethernet switches (C-363T, C-364T), if being used. Issue 1 May

18 Introduction! Important: Important: The most current version of firmware must be installed on the programmable circuit packs, particularly the TN2312AP/BP IP Server Interface. You cannot activate many features of Release 5.2 of Communication Manager unless these circuit packs are on the most current version. Firmware for these products are available from the Avaya Support Web site, support. Additional documentation Avaya recommends that you also have the documents that are listed in Resources on page 28 for the upgrade. These documents are also included on the CD, Documentation for Communication Manager Release 5.2, Media Gateways and Servers, The content of the documentation CD is available at for viewing or downloading. Upgrading to Communication Manager Release 5.2 To upgrade Communication Manager to Release 5.2, you need to follow the same upgrade process as done for previous Communication Manager releases, if those upgrade processes included using Manage Software or Software Update Manager. Upgrade Tool and Avaya Installation Wizard cannot be used to upgrade to Communication Manager Release 5.2 or later. The applicable changes for Release 5.2 are: You can no longer use the Upgrade Tool for the upgrade. You can no longer use Avaya Installation Wizard (AIW) for the upgrade. Changed upgrade procedure, if you are upgrading a system that includes S8700-Series Server. Upgrade tool You cannot use the Upgrade Tool to upgrade Communication Manager to Release 5.2 or later. After Communication Manager 5.2 is running on the server, the System Management Interface contains a reference to the Upgrade Tool (from menu, Upgrade > Upgrade Tool). 18 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

19 Upgrading to Communication Manager Release 5.2 The reference to Upgrade Tool is for information only, and if you access the Upgrade Tool link, the system displays the following message: The "Upgrade Tool" (UT) is no longer available. Please use one of the following upgrade tools: Software Update Manager (SUM). Manage Software option in the Upgrade category within the System Management Interface (SMI). The Avaya Installation Wizard The Avaya Installation Wizard (AIW) cannot be used to upgrade Communication Manager to Release 5.2 or later. The Avaya Installation Wizard (AIW) is a tool to be used in installations (not upgrades) of Communication Manager in certain system configurations. The Installation Wizard helps you to reduce complexity, time-to-install, and the cost of installation. Avaya Installation Wizard (AIW) does not allow upgrades to Communication Manager 5.2 or later releases. AIW verifies the target release and blocks it, if it is for release 5.2 or above. AIW allows upgrades to lower level releases. The Avaya Installation Wizard is a universally-available part of Communication Manager software and is accessible from the Web pages interface. The most recent version of Avaya Installation Wizard, as well as its documentation, can be accessed online at: Manage Software Web page Manage Software Web page is used to load any new release of the Communication Manager software for the main server. The Manage Software can also be run remotely, if you can access the System Management Interface (SMI). The Manage Software can be directed to copy the release software from a TFTP server to the disk of the media server. The Manage Software can also be directed to copy the release software from a URL (an HTTP Web server) to the disk of the server. For Release 5.2 of Communication Manager the Manage Software Web page provides additional secure method for copying files to the server. The change in the field for Release 5.2 is: IA770 Intuity Audix term replaced with Communication Manager Messaging (CMM) Issue 1 May

20 Introduction Avaya Software Update Manager Avaya Software Update Manager (SUM) is an application that downloads software to managed Avaya devices. Avaya Software Update Manager also checks the software versions currently in use against the latest versions available from Avaya, and recommends updates when a newer version is available. For more information on SUM Tool see Avaya Integrated Management 5.2 Software Update Manager User Guide available at Communication Manager Servers managed by Software Update Manager The Avaya Software Update Manager allows you to automatically upgrade Communication Manager software, service packs, security updates, licenses, and authentication files on Communication Manager Servers used in the customer s network, including: The S8300 Server, S8400 Server, S8500 Server, S8510 Server, S8700 Server, S8710 Server, S8720 Server, or S8730 Server as primary controllers. The S8400 ESS as possible ESS Server, S8500 Server, S8510 Server, S8700 Server, S8710 Server, S8720 Server, or S8730 Server as ESSs. The S8300, S8500 and S8510 Servers as LSPs. In addition, Software Update Manager can upgrade software for the following: The SAMP on an S8500-Series Servers. The MPC on an S8400 Server. Error resistant download via https After Communication Manager 5.2 is running on the server, subsequent use of Manage Software for upgrades will provide enhancements when compared to previous releases. Release 5.2 of Communication Manager has implemented upgrade improvements to provide a more robust and remotely successful distributed Communication Manager System upgrade experience. These upgrade improvements in Release 5.2 of Communication Manager enable you to: Reduce copy size from files size (which currently can approach 100MB) to something more granular (for example: block size) such that when remote upgrades are being performed over a bouncing network as much of the copying is done without re-transmittal. Support SCP and HTTPS protocol, which is added to allow secure file transfers. 20 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

21 Upgrading to Communication Manager Release 5.2 Also added are foundational elements that informs you the upgrade file transfers and processes are continuing, specifically that the process is progressing and not hung. The progress is displayed in text only format, as shown in Figure 1, Figure 2, Figure 3, and Figure 4: Figure 1: Method selection for file transfer Figure 2: Detection of available release Issue 1 May

22 Introduction Figure 3: Copy in progress Figure 4: Copy complete 22 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

23 Upgrade procedures Upgrade procedures Upgrading to Communication Manager Release 5.2 You can upgrade to Release 5.2 of Communication Manager software from all previously launched releases of Communication Manager, provided the upgrade is a software upgrade that does not involve a migration. Release 5.2 of Communication Manager is supported on the following server platforms: S8710 (with DAL2 card), S8720 (with DAL2 card if hardware duplication), S8730 (with DAL2 card if hardware duplication) S8500 (B/C), S8510 S8300 (B/C) but SES only on S8300C S8400 A/B If you have releases prior to Communication Manager 5.2 you can upgrade directly to Release 5.2 without any intermediate steps. The supported Communication Manager upgrade paths for Release 5.2 are: For CM 1.x to CM 5.2 (Not a supported upgrade path) - S S8300A - S8700 For CM 2.0.x to CM S8300A, S8300B - S8500A - S8700 For CM 2.1.x to CM S8300B - S8500A - S8700 For CM 2.2.x to CM S8300B - S8500A, S8500B - S8700, S8710 Issue 1 May

24 Introduction For CM 3.0.x to CM S8300B - S8500A, S8500B, S8500B EMMC - S8700, S8710 For CM 3.1.x to CM S8300B - S8400A - S8500A, S8500B, S8500C, S8500B EMMC - S8700, S8710, S8720, S8720XL For CM 4.0.x to CM S8300B, S8300C - S8400A - S8500A, S8500B, S8500C, S8500B EMMC - S8700, S8710, S8720, S8720XL For CM 5.0.x to CM S8300B, S8300C - S8400A, S8400B - S8500B, S8500C, S8510, S8500B EMMC - S8710, S8720, S8720XL, S8730 For CM 5.1.x to CM S8300B, S8300C - S8400A, S8400B - S8500B, S8500C, S8510, S8500B EMMC - S8710, S8720, S8720XL, S8730 For CM 5.2 to CM 5.2.x - S8300B, S8300C - S8400A, S8400B - S8500B, S8500C, S8500B EMMC, S S8710, S8720, S8720XL, S8730 S8100, S8300A, S8500A and S8700-Series Servers cannot be upgraded to Communication Manager R5.2. These servers require migrations: - S8300A requires a migration to S8300C 24 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

25 Upgrade procedures - S8500A requires a migration to S S8700 requires a migration to S8730 For S8710 Server to upgrade from Communication Manager R2.2 to R5.1, you need to replace the DAL1 card with the DAL2 card prior to upgrading. Same process applies for S8720 Server that has the DAL1 card in standard mode. Upgrading Release 5.2 of Communication Manager on these servers is no different than upgrading them to Release 5.0. Any servers not mentioned above cannot be upgraded to Release 5.2 of Communication Manager. Those servers must be replaced with a server currently being sold. See the Migrations section for the migration paths supported. Backup and Restore Support: You can backup any release of Communication Manager software and restore it to Release 5.2. One exception is a full backup on S8500A, which cannot be restored on S8500C or S8510. Upgrade sequence When you are upgrading multiple components in a distributed server/gateway configuration, then its necessary to adhere to a systematic order of events while conducting the upgrades. 1. LSPs 2. Supported Media Gateway media modules or supported Media Gateway. Since a Media Gateway running software that supports 1.3, 2.0, 3.0, 4.0 or 5.2 supports media modules that also support 1.3, 2.0, 3.0, 4.0 or 5.2, the order in which the media module software and Media Gateway software is upgraded is not an issue. 3. Update TN packs (if not, complete as part of pre-upgrade process) 4. ESSs 5. Primary Servers 6. Standalone SES servers (update or re-master, as appropriate) This means that if a LSP is upgraded to the Release 5.2 of Communication Manager, all H.248 Media Gateways that are supported by that LSP must be running a version of gateway software that supports 5.2. This also means that before a primary server is upgraded to 5.2, all Media Gateways, Media Gateway media modules, and LSPs in the configuration must be upgraded to 5.2 before an upgrade of the primary server is attempted. The MM716, MM316, and MM314 media modules require the latest gateway software. Issue 1 May

26 Introduction Avaya one-x portal dependency Avaya one-x Portal has a dependency on the release level of the Communication Manager systems to which it connects. When the Communication Manager release changes, administrative changes must be made in one-x Portal in order to ensure continued interoperability between the two applications. If you are using the S8400 Server for UP telephone firmware downloads, the IP telephone firmware files must be reinstalled to the server after the upgrade. The firmware and 4600-series telephone configuration file are overwritten during the upgrade. The 4600 firmware is contained within a 4600.tar file in a name format similar to the filename 4600H323_cm2_2_wi1_15_ipt2_2_ tar. This file must be retrieved from the Avaya Downloads Web site and downloaded to the server after the upgrade. The upgrade to Release 5.x preserves the /tftpboot/4600settings.txt file through the upgrade. If the S8400 Server is used for IP telephone firmware downloads, the IP telephone firmware files must be reinstalled to the S8400 Server after the upgrade. You can save a copy of the 4600 configuration file before the upgrade, and copy the file back to the tfpboot directory after the upgrade. Duplicated Enterprise Survivable Server (ESS) upgrade For Release 5.2 of Communication Manager the Processor Ethernet (PE) is supported for Duplex Servers. PE on Duplex Server is only supported on the S8720 and S8730 Servers. If you have a duplicated ESS and want to upgrade from Communication Manager 5.1 or earlier to Communication Manager 5.2 or later then you need to follow the procedure at Upgrading Communication Manager on the S8700-Series main or ESS servers from R2.x/R3.x/R4.x/R5.x to 5.2 using Manage Software on page 139. Duplex ESS upgrade workflow on page 27 and repeated on page 145 lists the tasks to upgrade a Communication Manager system that included duplicated ESS. The detailed instructions required upgrading duplicated ESS are included in Upgrading Communication Manager on the S8700-Series main or ESS servers from R2.x/R3.x/R4.x/R5.x to 5.2 using Manage Software on page 139. Customers with releases prior to Communication Manager 5.2 can upgrade to Communication Manager 5.2 Processor Ethernet on Duplex Servers (S8720 or S8730) on the hardware platforms outlined here: S8720 (software upgrade or can opt to upgrade server to S8730 as well) S8730 (software upgrade) S8500 or S8510 (must upgrade server to S8730 in conjunction with software upgrade) S8700 or S8710 (must upgrade server to S8730 in conjunction with software upgrade) Addressing customers who need to expand capacity beyond 2,400 users 26 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

27 Duplicated Enterprise Survivable Server (ESS) upgrade Unless the resulting configuration is mixed PE and IP Connect, the above upgrades require the replacement of Port Networks (G650 Media Gateways) with H.248 Media Gateways. Upgrade procedures for Duplicated ESS Servers Important:! Important: When you upgrade a duplex ESS from an earlier release of Communication Manager to Release 5.2, the ESS uses the PE Active Server IP address (IP-alias). The ESS servers are upgraded before the main server. In a situation when the ESS is upgraded and the main server is not, the main server has no concept that an ESS has a PE Active Server IP Address. The upgraded ESS uses the PE Active Server IP Address that is shared by the duplicated pair. Duplex ESS upgrade workflow On each duplex ESS server, complete the following tasks: 1. Upgrade the ESS. 2. Access the System Management Interface (formerly known as Maintenance Web Interface). 3. Configure the PE interface. Ensure that PE is assigned an IP-alias address and ensure that PE is assigned to the same NIC as the corporate LAN. 4. Verify that the Server A of the duplex ESS is active. After you upgrade each duplex ESS pair of servers, complete the following tasks on the main server: 1. Change the node name of server A for the duplicated pair to the node name configured for the PE interface. If the node name does not exist, define a new node name with the IP address that you configured for the PE interface of the duplex ESS. 2. Save translations. After you have upgraded all the ESS and LSP servers in the system, complete the following tasks on the main server: 1. Upgrade the main server(s). 2. If the system has any duplicated ESS servers, administer the Server A node name of each duplicated ESS pair on its respective survivable-processor SAT screen. Issue 1 May

28 Introduction Resources To help with the procedures in this book, you might need to refer to the following books. These documents are also included on the CD, Documentation for Communication Manager Release 5.2, Media Gateways and Servers, The content of the documentation CD is available at for viewing or downloading. Document Migrating Avaya Servers and Media Gateways, ( ). Converting Avaya Servers and Media Gateways, ( ). Installing and Upgrading the Avaya S8300 Server, Installing and Upgrading the Avaya G700 Media Gateway Avaya IA 770 INTUITY AUDIX Messaging Application Release 3.1 Administering the S8300 and S8400 Media Servers to Work with IA 770, ( ) Quick Start for Hardware Installation: Avaya S8400 Server in an Avaya G650 Media Gateway ( ) Description A migration is a change in hardware. The types of migration include a non-linux-based system to a Linux-based server, Linux-based server to a different Linux-based server, and media gateway to a different media gateway. Procedures on change in function or mode, reliability, or connectivity of various hardware components. Components include servers and media gateways. A conversion may be preceded by a migration and may include an upgrade. Procedures to install, upgrade, or migrate an Avaya S8300 Server. Procedure describes the various ways of connecting to and logging into the Avaya G700 Media Gateway. Procedures to administer the Communication Manager Messaging (CMM) - formerly known as IA770 INTUITY AUDIX messaging application. Procedure to install the server and connect components. 1 of 3 28 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers

29 Resources Document Quick Start for Hardware Migration: Avaya S8400 Server in an Avaya CMC1 or G600 Media Gateway ( ) Installing and Configuring the Avaya S8400 Server ( ) Quick Start for Hardware Installation: Avaya S8500-Series Server ( ) Installing and Configuring the Avaya S8500-Series Server ( ) Quick Start for Hardware Installation: Avaya S8700-Series Server ( ) Installing and Configuring an Avaya S8700-Series Server ( ) Installing Center Stage Switch ( ) Installing the MDF and Telephones ( ) Description Procedure to install the server and connect components. Procedures to install Communication Manager and configure the server and the TN8412AP System Internet Protocol Interface circuit pack. Procedures to install the server in a rack and connect components. Procedures to install Communication Manager and configure the server and the TN2312BP IP Server Interface circuit packs Procedures to install the server in a rack and connect components Procedures to install Communication Manager and configure the server and TN2312BP IP Server Interface (IPSI) circuit packs Procedures to install an MCC1 Media Gateway as a port network and Center Stage Switch. Procedures to install the main distribution frame and telephones Installing the Avaya G650 Media Gateway ( ) Avaya Aura Communication Manager Hardware Description and Reference ( ) Using the Avaya Enterprise Survivable Servers (ESS) ( ) Procedures to install a G650 Media Gateway, backplane, and endpoints Descriptions of all products, components, and connectivity Information on installing and configuring ESSs and migrating a main server to an ESS. 2 of 3 Issue 1 May

30 Introduction Document Administering Avaya Aura Communication Manager ( ) Administering Network Connectivity on Avaya Aura Communication Manager ( ) Avaya Application Solutions: IP Telephony Deployment Guide ( ) Job Aid: Approved Grounds ( ) Job Aid: Connector and Cable Diagrams (Pinout Charts) ( ) Job Aid: Option Switch Settings ( ) Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers ( ) Maintenance Alarms for Avaya Aura Communication Manager, Media Gateways and Servers ( ) Maintenance Procedures for Avaya Aura Communication Manager, Media Gateways and Servers ( ) Description End-user information on administering trunks and telephones. Information on implementing converged data and voice communications networks. Guidelines for planning converged data and voice communications networks. Description of all approved grounds. Diagrams for various components. Settings for various components. How to use command interfaces, command syntax, and output from maintenance-related commands. How to use alarms, error codes, and tests to diagnose and repair problems. How to troubleshoot and replace various components. 3 of 3 30 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers