Upgrading Avaya Aura™ Communication Manager …support.avaya.com/elmodocs2/comm_mgr/R5_2/CM5_2_htmlpages/CM5_2...Pre-upgrade service pack requirements ... TN2312AP/BP IPSI circuit

Upgrading Avaya Aura™ Communication Manager on Avaya S8xxx Servers

03-602885Issue 1

May 2009

© 2009 Avaya Inc.All Rights Reserved.

NoticeWhile 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 number03-600759.To locate this document on our Web site, simply go to http://www.avaya.com/support and search for the document number in the search box.

Documentation disclaimerAvaya 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 disclaimerAvaya 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.

WarrantyAvaya 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:http://www.avaya.com/support.

CopyrightExcept 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 supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support.

http://www.avaya.com/support


http://www.avaya.com/support/

Contents

Issue 1 May 2009 3

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Firmware upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Upgrading to Communication Manager Release 5.2 . . . . . . . . . . . . . . . . . . . 18

Upgrade tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18The Avaya Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Manage Software Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Avaya Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Communication Manager Servers managed by Software Update Manager . . . . . 20Error resistant download via https . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Upgrade procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Upgrading to Communication Manager Release 5.2 . . . . . . . . . . . . . . . . . 23Upgrade sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Avaya one-X portal dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Duplicated Enterprise Survivable Server (ESS) upgrade . . . . . . . . . . . . . . . . . 26Upgrade procedures for Duplicated ESS Servers . . . . . . . . . . . . . . . . . . . 27Duplex ESS upgrade workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28How this book is designed and organized . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 2: Upgrading Software on Servers . . . . . . . . . . . . . . . . . . . . . . . . . . 33Common prerequisites for all upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Checklist of tasks to perform before you go on site . . . . . . . . . . . . . . . . . 36RFA license and authentication files . . . . . . . . . . . . . . . . . . . . . . . . . . 38Generating and retrieving license and authentication files. . . . . . . . . . . . . . 39Logins and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Platform/PNC license settings for the S8700-Series Server . . . . . . . . . . . . . 39Checking for an FTP/SCP/SFTP Server or Compact Flash for Backing up . . . . . 40

Preserving connections while upgrading an S8700-Series Server. . . . . . . . . . . . 40Connections not preserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Tools to preserve connections during an upgrade . . . . . . . . . . . . . . . . . . 42Manual steps to preserve connections during an upgrade . . . . . . . . . . . . . . 42

Upgrade modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/C/D Server (Migration from S8300A to S8300C/D). . . . . . . . . . . . . . . . . . . . . . . 47

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Pre-upgrade service pack requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 49Tasks checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Contents

Issue 1 May 2009 4

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) . . . . . . . . . . . . . . . . . 57

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Pre-upgrade service pack requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 59Tasks checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP 67

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76The need to restore IP telephone files . . . . . . . . . . . . . . . . . . . . . . . . . 76TN8412AP SIPI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . . . 76Upgrading LSPs and media gateways, if any . . . . . . . . . . . . . . . . . . . . . 77

Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Upgrading the MPC firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 78Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 79Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 79Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 79Saving a copy of the 4600-series telephone configuration file, if any . . . . . . . . 80Accessing the server’s web interface . . . . . . . . . . . . . . . . . . . . . . . . . 80Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Ensuring a super-user login exists . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Connecting the CD/DVD-ROM drive to the server . . . . . . . . . . . . . . . . . . . 84Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 86Removing the CD-ROM from the CD-ROM drive. . . . . . . . . . . . . . . . . . . . 87Installing Communication Manager on the server. . . . . . . . . . . . . . . . . . . 88

Contents

Issue 1 May 2009 5

Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Installing security and Communication Managerservice pack updates, if any . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing the RFA license file and authentication file . . . . . . . . . . . . . . . . 95Copying IP telephone firmware to the server, if necessary. . . . . . . . . . . . . . 95Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 96

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Accessing the server command line interface with ssh protocol . . . . . . . . . . 97Enabling scheduled maintenance with SAT (main only) . . . . . . . . . . . . . . . 98Busying out previously busied-out trunks. . . . . . . . . . . . . . . . . . . . . . . 99Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 99Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 100Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 101Registering Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . 101

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 . . . . . . . . . . . . . . . . . . . . 103

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104The need to restore IP telephone firmware files . . . . . . . . . . . . . . . . . . . 104TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . 105Upgrading LSPs and media gateways, if any . . . . . . . . . . . . . . . . . . . . . 105Upgrading firmware on media gateways and media modules . . . . . . . . . . . . 107Upgrade of Communication Manager on the ESS servers . . . . . . . . . . . . . . 107

Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Upgrading the SAMP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Stopping call processing on the LSPs or ESS serversif being used (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 109Recording all busyouts (main server only) . . . . . . . . . . . . . . . . . . . . . . 110Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 110Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 110Checking for translation corruption with the SAT. . . . . . . . . . . . . . . . . . . 111Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 111Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Contents

Issue 1 May 2009 6

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Ensuring a super-user login exists . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Installing a DIMM in an S8500B Server . . . . . . . . . . . . . . . . . . . . . . . . . 114Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Saving a copy of the 4600-series telephone configuration file, if any . . . . . . . . 118Checking software release, only if starting from R2.x . . . . . . . . . . . . . . . . 118Activating the preupgrade service pack, only if starting from R2.x . . . . . . . . . 119

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Inserting the Communication Manager CD into the server . . . . . . . . . . . . . . 120Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 121Installing Communication Manager on the server. . . . . . . . . . . . . . . . . . . 122Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 127Installing security and Communication Managerservice pack updates, if any . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Accessing the server command line interface with ssh protocol . . . . . . . . . . 129Configuring the ESS or LSP for compatibility with an XL configuration. . . . . . . 130Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Creating a customer login (if necessary) . . . . . . . . . . . . . . . . . . . . . . . 132Installing the RFA license file and authentication file . . . . . . . . . . . . . . . . 133Stopping and starting ESS servers. . . . . . . . . . . . . . . . . . . . . . . . . . . 134Setting the Processor Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Copying IP telephone firmware to the server, if necessary(main servers only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Enabling scheduled maintenance with SAT (main only) . . . . . . . . . . . . . . . 135Busying out previously busied-out trunks. . . . . . . . . . . . . . . . . . . . . . . 136Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 136Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 137Starting call processing on the LSPs and ESSs, if any(main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 138Registering Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . 138

Contents

Issue 1 May 2009 7

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141The need to restore IP telephone firmware files . . . . . . . . . . . . . . . . . . . 141TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . 142Upgrading media gateways, LSPs and ESS servers, if being used . . . . . . . . . 142Upgrading firmware on media gateways and media modules . . . . . . . . . . . . 144Upgrade of Communication Manager on the ESS servers . . . . . . . . . . . . . . 144Duplex ESS upgrade workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Verifying the status of ESS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Stopping call processing on the LSPs or ESS serversif being used (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Clearing the ARP cache on the laptop . . . . . . . . . . . . . . . . . . . . . . . . . 148Clearing the Web browser cache on the laptop . . . . . . . . . . . . . . . . . . . . . . 148

Connecting to the active server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 149Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 150Recording all busyouts (main server only) . . . . . . . . . . . . . . . . . . . . . . 150Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 151Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 151Busying out MMI circuit packs with SAT for a duplicated controlnetwork only (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 152Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 152Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Ensuring a super-user login exists . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Backing up recovery system files on the active server . . . . . . . . . . . . . . . . 154Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 155Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Clearing the ARP cache on the laptop computer . . . . . . . . . . . . . . . . . . . 156

Clearing the Web browser cache on the laptop . . . . . . . . . . . . . . . . . . . . . . 157Backing up files on the standby server . . . . . . . . . . . . . . . . . . . . . . . . 157Verifying the backup on the standby server . . . . . . . . . . . . . . . . . . . . . . 158Suppressing alarming on the standby server . . . . . . . . . . . . . . . . . . . . . 158Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 159

Contents

Issue 1 May 2009 8

Removing a DAL1 or installing a DAL2 card. . . . . . . . . . . . . . . . . . . . . . 159Placing or Replacing the server in the rack . . . . . . . . . . . . . . . . . . . . . . 160Restoring power to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Verify that the DAL2 card is installed correctly . . . . . . . . . . . . . . . . . . . . 161Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 161Connecting to the active server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Accessing the active server’s web interface. . . . . . . . . . . . . . . . . . . . . . 162Selecting the Preupgrade Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 163

Upgrade tasks for the first server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Clearing the ARP cache on the laptop . . . . . . . . . . . . . . . . . . . . . . . . . 164Checking the software release on the standby server . . . . . . . . . . . . . . . . 165Activating the preupgrade service pack on the standby server(R2.x only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Inserting the Communication Manager CD-ROM into the standbyserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 167Upgrading Communication Manager on the server . . . . . . . . . . . . . . . . . . 168 Rebooting the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Suppressing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 172Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 172Installing security and service pack updates, if any . . . . . . . . . . . . . . . . . 172Configuring the Processor Ethernet interface (on the ESS) . . . . . . . . . . . . . 173Accessing the server command line interface with ssh protocol . . . . . . . . . . 173XL configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 179Releasing the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Interchanging the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 180Creating a super-user login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Installing the new license and Avaya authentication files on newlyactive server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Stopping and starting the ESS servers . . . . . . . . . . . . . . . . . . . . . . . . 182Disconnecting from the newly active server. . . . . . . . . . . . . . . . . . . . . . 182

Upgrade tasks for the new standby server (second server) . . . . . . . . . . . . . . . 183Removing a DAL1 or installing a DAL2 card. . . . . . . . . . . . . . . . . . . . . . 183Placing or Replacing the server in the rack . . . . . . . . . . . . . . . . . . . . . . 184

Contents

Issue 1 May 2009 9

Restoring power to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Verify that the DAL2 card is installed correctly . . . . . . . . . . . . . . . . . . . . 185Disconnecting from the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Accessing the standby server’s maintenance interface . . . . . . . . . . . . . . . 186Checking the software release on the standby server . . . . . . . . . . . . . . . . 186Activating the preupgrade service pack on the server (R2.x only) . . . . . . . . . . 186Inserting the Communication Manager CD into the server . . . . . . . . . . . . . . 187Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 187Upgrading Communication Manager on the server . . . . . . . . . . . . . . . . . . 189 Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Suppressing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Performing an integrity check on the second S8700-Series Server . . . . . . . . . 193Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 193Installing security and service pack updates, if any . . . . . . . . . . . . . . . . . 193Configuring the Processor Ethernet interface (on the ESS) . . . . . . . . . . . . . 194Accessing the server command line interface with ssh protocol . . . . . . . . . . 194XL configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Performing an integrity check on the second S8700-Series Server . . . . . . . . . 200Verifying the operation of the servers . . . . . . . . . . . . . . . . . . . . . . . . . 200Setting Server A/Server 1 active for ESS, if necessary . . . . . . . . . . . . . . . . 200

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Copying IP telephone firmware to the server, if necessary(main servers only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 202Administering the node name for the IP-alias address for the duplicated ESS servers (after ESS upgrade and pre-upgrade Main) . . . . . . . . . . . . . . . . . . . . . . . . . 202

Enabling scheduled maintenance with SAT (main server only) . . . . . . . . . . . 204Releasing MMI circuit packs in duplicated control network using SAT, (main server only)204

Busying out previously busied-out trunks (main server only) . . . . . . . . . . . . 204Checking for translation corruption with SAT (main server only) . . . . . . . . . . 204Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Backing up files on the active server. . . . . . . . . . . . . . . . . . . . . . . . . . 205Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 206Logging off all administration applications on the active server. . . . . . . . . . . 206Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 206Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Contents

Issue 1 May 2009 10

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Backing up files on the standby server . . . . . . . . . . . . . . . . . . . . . . . . 207Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 207Starting call processing on the LSPs and ESSs, if any . . . . . . . . . . . . . . . . 208Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 208Registering Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 3: Upgrading Firmware on TN circuit packsand Ethernet switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Upgrade modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Upgrading firmware on the IPSIs and SIPIs . . . . . . . . . . . . . . . . . . . . . . . . . . 213Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Access the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Determining current IPSI firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Pre-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Interchanging the IPSIs (duplicated control network only) . . . . . . . . . . . . . . 221Post-upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Upgrading firmware on TN circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Upgrading firmware on the Avaya Ethernet Switch . . . . . . . . . . . . . . . . . . . . . 225

Appendix A: Accessing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Connecting to the server directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Computer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Connecting to the server remotely over the network . . . . . . . . . . . . . . . . . . . 233Connecting to the server remotely over a modem . . . . . . . . . . . . . . . . . . . . 233

Setting up a dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Dialing up to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Finding the IP address of the active server (duplicated servers) . . . . . . . . . . 234Disabling the boot timeout of the SAMP board . . . . . . . . . . . . . . . . . . . . 234

Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . . . 235Using the command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Accessing the server command line interface with ssh protocol . . . . . . . . . . 236Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Contents

Issue 1 May 2009 11

Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Browser settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Connecting directly to the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Connecting remotely through the network . . . . . . . . . . . . . . . . . . . . . . 240

Appendix B: DAL: Removing or Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Verifying which DAL is installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Removing power from the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Removing the server from the rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Removing the cover from the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Removing the PCI riser cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Removing the DAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Installing the DAL2 in the S8710 or S8720 . . . . . . . . . . . . . . . . . . . . . . . . . 247

Replacing the PCI riser cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Replacing the cover on the server . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Installing the DAL2 in the S8730 Server . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Contents

Issue 1 May 2009 12

Contents

Issue 1 May 2009 13

Contents

Issue 1 May 2009 14

Issue 1 May 2009 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

Note:Note: 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, 555-233-118.

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 1.3.2 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 1.3.2 to Release 5.x, it will not get a filesync from the main server until the main server upgrades from Release 1.3.2 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 1.3.2 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.

Introduction

16 Upgrading Avaya Aura™ Communication Manager on Avaya S8xxx Servers

! 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, 03-300412.

! 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, 03-300412.

! 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 http://support.avaya.com. Select Downloads > Latest TN Circuit Pack, Media Server, and Media Gateway Firmware and Software Updates > Latest Communication Manager Software & Firmware Compatibility Matrix.

http://support.avaya.com

Firmware upgrades

Issue 1 May 2009 17

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, 03-300412.

! Important:Important: You cannot use Upgrade Tool or Avaya Installation Wizard (AIW) for the upgrade

procedures to Communication Manager Release 5.2 or later.

Note:Note: 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, 03-300412.

● For information on Conversions, see Converting Avaya Servers and Media Gateways, 03-602884.

Firmware upgradesSeveral 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.

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, http://avaya.com/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, 03-300151. The content of the documentation CD is available at http://avaya.com/support for viewing or downloading.

Upgrading to Communication Manager Release 5.2To 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 toolYou 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).

http://avaya.com/support



Upgrading to Communication Manager Release 5.2

Issue 1 May 2009 19

Note:Note: 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.

Note:Note: 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: http://support.avaya.com/avayaiw.

Manage Software Web pageManage 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)

Introduction


Avaya Software Update ManagerAvaya 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 http://support.avaya.com.

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 httpsAfter 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.

Upgrading to Communication Manager Release 5.2

Issue 1 May 2009 21

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

Introduction


Figure 3: Copy in progress

Figure 4: Copy complete

Upgrade procedures

Issue 1 May 2009 23

Upgrade procedures

Upgrading to Communication Manager Release 5.2You 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)

- S8100

- S8300A

- S8700

● For CM 2.0.x to CM 5.2

- S8300A, S8300B

- S8500A

- S8700


- S8300B

- S8500A

- S8700


- S8300B

- S8500A, S8500B

- S8700, S8710

Introduction



- S8300B

- S8500A, S8500B, S8500B EMMC

- S8700, S8710


- S8300B

- S8400A

- S8500A, S8500B, S8500C, S8500B EMMC

- S8700, S8710, S8720, S8720XL


- S8300B, S8300C

- S8400A

- S8500A, S8500B, S8500C, S8500B EMMC

- S8700, S8710, S8720, S8720XL


- S8300B, S8300C

- S8400A, S8400B

- S8500B, S8500C, S8510, S8500B EMMC

- S8710, S8720, S8720XL, S8730


- 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, S8510

- S8710, S8720, S8720XL, S8730

Note:Note: 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

Upgrade procedures

Issue 1 May 2009 25

- S8500A requires a migration to S8510

- 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 sequenceWhen 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)

Note:Note: 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.

Introduction


Avaya one-X portal dependencyAvaya 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_111405.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) upgradeFor 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

Duplicated Enterprise Survivable Server (ESS) upgrade

Issue 1 May 2009 27

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 workflowOn 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.

Introduction


ResourcesTo 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, 03-300151. The content of the documentation CD is available at http://support.avaya.com for viewing or downloading.

✓ Document Description

Migrating Avaya Serversand Media Gateways,(03-300412).

A migration is a change in hardware. The types ofmigration include a non-Linux-based system to aLinux-based server, Linux-based server to a differentLinux-based server, and media gateway to a differentmedia gateway.

Converting Avaya Serversand Media Gateways,(03-602884).

Procedures on change in function or mode, reliability,or connectivity of various hardware components.Components include servers and media gateways. Aconversion may be preceded by a migration and mayinclude an upgrade.

Installing and Upgrading theAvaya S8300 Server,555-234-100.

Procedures to install, upgrade, or migrate an AvayaS8300 Server.

Installing and Upgrading theAvaya G700 MediaGateway 03-603333.

Procedure describes the various ways of connecting toand logging into the Avaya G700 Media Gateway.

Avaya IA 770 INTUITYAUDIX MessagingApplication Release 3.1Administering the S8300and S8400 Media Serversto Work with IA 770, (07-600788)

Procedures to administer the Communication Manager Messaging (CMM) - formerly known as IA770 INTUITY AUDIX messaging application.

Quick Start for Hardware Installation: Avaya S8400 Server in an Avaya G650 Media Gateway (03-300705)

Procedure to install the server and connect components.

1 of 3

Resources

Issue 1 May 2009 29

Quick Start for Hardware Migration: Avaya S8400 Server in an Avaya CMC1 or G600 Media Gateway (03-300706)

Procedure to install the server and connect components.

Installing and Configuring the Avaya S8400 Server (03-300678)

Procedures to install Communication Manager and configure the server and the TN8412AP System Internet Protocol Interface circuit pack.

Quick Start for HardwareInstallation: AvayaS8500-Series Server (555-245-701)

Procedures to install the server in a rack and connect components.

Installing and Configuringthe Avaya S8500-SeriesServer (03-300143)

Procedures to install Communication Manager and configure the server and the TN2312BP IP Server Interface circuit packs

Quick Start for Hardware Installation: Avaya S8700-Series Server (555-245-703)

Procedures to install the server in a rack and connect components

Installing and Configuring an Avaya S8700-Series Server (03-300145)

Procedures to install Communication Manager and configure the server and TN2312BP IP Server Interface (IPSI) circuit packs

Installing Center Stage Switch (03-300707)

Procedures to install an MCC1 Media Gateway as a port network and Center Stage Switch.

Installing the MDF and Telephones (03-300686)

Procedures to install the main distribution frame and telephones

Installing the Avaya G650 Media Gateway (03-300685)

Procedures to install a G650 Media Gateway, backplane, and endpoints

Avaya Aura™ Communication Manager Hardware Description and Reference (555-245-207)

Descriptions of all products, components, and connectivity

Using the Avaya Enterprise Survivable Servers (ESS) (03-300428)

Information on installing and configuring ESSs and migrating a main server to an ESS.


2 of 3

Introduction


Administering Avaya Aura™ Communication Manager (03-300509)

End-user information on administering trunks and telephones.

Administering Network Connectivity on Avaya Aura™ Communication Manager (555-233-504)

Information on implementing converged data and voice communications networks.

Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600)

Guidelines for planning converged data and voice communications networks.

Job Aid: Approved Grounds (555-245-772)

Description of all approved grounds.

Job Aid: Connector and Cable Diagrams (Pinout Charts) (555-245-773)

Diagrams for various components.

Job Aid: Option Switch Settings (555-245-774)

Settings for various components.

Maintenance Commands for Avaya Aura™ Communication Manager, Media Gateways and Servers (03-300431)

How to use command interfaces, command syntax, and output from maintenance-related commands.

Maintenance Alarms for Avaya Aura™ Communication Manager, Media Gateways and Servers (03-300430)

How to use alarms, error codes, and tests to diagnose and repair problems.

Maintenance Procedures for Avaya Aura™ Communication Manager, Media Gateways and Servers (03-300432)

How to troubleshoot and replace various components.


3 of 3

How this book is designed and organized

Issue 1 May 2009 31

How this book is designed and organizedTo use this book, you can print:

● A chapter that includes all the modules contained in that chapter

● A module, which is designed to stand alone

Many modules have tasks that you must complete before you go on site. These prerequisite steps are listed in the chapter that precedes the module or in the module itself. Some modules might have tasks that you need to do after you complete the tasks in that module. These postrequisites might point to another module or other documentation.

The following table provides links to the sections, the chapters, and the modules that this book contains:

Section, chapter, or module Description

Introduction on page 15

Chapter 2: Upgrading Software on Servers on page 33 Introduces the modules associated with upgrading software on the S8300, the S8500-Series Servers, and the S8700-Series Servers

Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/C/D Server (Migration from S8300A to S8300C/D) on page 47

Presents the tasks required to upgrade the software from Release 1.x to Release 5.x and replace the S8300A Server with an S8300B Server.

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) on page 57

Presents the tasks required to upgrade the software from Release 1.x to Release 5.x and replace the S8300B Server with an S8300C Server.

Upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP on page 67

Presents the tasks required to upgrade the software on an S8300 Server from Release 2.x or later to Release 5.x.

Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage Software on page 75

Presents the tasks required to upgrade the software on an S8400 Server from Release 3.1/3.1.x or later to Release 5.x.

1 of 2

Introduction


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 on page 103

Presents the tasks required to upgrade the software on an S8500-Series Servers from Release 2.x/3.x/4.x to Release 5.x using the System Management Interface (formerly known as Maintenance Web Interface).

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

Presents the tasks required to upgrade the software on an S8700-Series Server from Release 2.x/3.x/4.x to Release 5.x using the System Management Interface (formerly known as Maintenance Web Interface).

Chapter 3: Upgrading Firmware on TN circuit packs and Ethernet switches on page 211

Introduces the modules associated with upgrading firmware on circuit packs and Ethernet switches

Upgrading firmware on the IPSIs and SIPIs on page 213

Presents the tasks required to upgrade the firmware on the TN2312 IPSI circuit pack

Upgrading firmware on TN circuit packs on page 223 It points to the procedures on the Avaya Support Web site.

Upgrading firmware on the Avaya Ethernet Switch on page 225

It points to the procedures on the Avaya Support Web site.

Section, chapter, or module Description

2 of 2

Issue 1 May 2009 33

Chapter 2: Upgrading Software on Servers

The software upgrades in this section cover upgrades of Communication Manager on S8300, S8400, S8500-Series Servers, and S8700-Series Servers. The tool available to upgrade an existing, registered server:

● The System Management Interface is available for Release 5.2

Note:Note: For Pre-Release 5.2 use the Maintenance Web Interface.

In either case, ensure that you have the CD-ROM with the latest release of Communication Manager ready to install.

Note:Note: You cannot use Upgrade Tool or Avaya Installation Wizard (AIW) for the upgrade







Upgrading Software on Servers


For an S8300 Server, two upgrade paths exist:

! Important:Important: S8300A Servers cannot upgrade to Communication Manager 2.1 or later

releases. For Communication Manager 5.2 and later releases, an S8300A Server must migrate to an S8300C or S8300D Server. For more information on how to migrate the S8300A see: Migrating Avaya Servers and Media Gateways, 03-300412.

● From Release 2.x to 5.x

● From Release 3.x/4.x/5.x to 5.x

● From Release 2.x to Release 5.x. This upgrade requires:

- An updated RFA license and authentication file

- A preupgrade service pack

● From Release 3.x to Release 5.x. This upgrade has no special requirements.

For an S8400 Server, one upgrade path exists:

● From Release 3.1.x / 4.x / 5.x to Release 5.x. This upgrade requires:

- An updated RFA license and authentication file (if required)

For an S8500-Series Server, one upgrade path exists:

! Important:Important: An S8500B Server must have 1G byte of memory for Communication Manager

release 4.0 or later.

! Important:Important: Communication Manager 5.0 or later is not supported on an S8500A Server.

! Important:Important: S8500A cannot be upgraded to Communication Manager 5.0 or later releases.

For Communication Manager 5.2 and later releases, an S8500A must migrate to either S8500C or S8510. For more information on how to migrate the S8500A Server, see: Migrating Avaya Servers and Media Gateways, 03-300412.

● For an S8500B and S8500C server: You can upgrade from Release 2.x to Release 5.x. This upgrade requires:

- An updated RFA license and authentication file

- A preupgrade service pack

- S8500B Server memory upgrade

● For an S8500B and S8500C Server: You can upgrade from Release 3.x to Release 5.x. This upgrade has special requirements, but is covered within the instructions of the R2.x to R5.x upgrade. This includes S8500B Server memory upgrade.

Common prerequisites for all upgrades

Issue 1 May 2009 35

For an S8700-Series Server, two upgrade paths exist:

! Important:Important: An S8710 must have a DAL2 card installed to run Communication Manager 5.x.

! Important:Important: From Release 1.x to 5.x:

S8700-Series Servers cannot upgrade to Communication Manager 5.0 or later releases. For Communication Manager 5.0 and later releases, an S8700 Server must migrate to an S8710, S8720, or S8730 Server. For more information on how to migrate the S8700-Series Servers see Migrating Avaya Servers and Media Gateways, 03-300412.

● From Release 2.x to Release 5.x. This upgrade requires:

- - An updated RFA license and authentication file (if required)

- - A preupgrade service pack

- - DAL2 card installation in the S8720 Server (if hardware duplication)

- - DAL2 card installation in the S8710 Server

● From Release 3.x/4.x/5.x to Release 5.x. This upgrade requires:

- - An updated RFA license and authentication file (if required)

- - DAL2 card installation in the S8720 Server (if hardware duplication)

- - DAL2 card installation in the S8710 Server

Common prerequisites for all upgradesBefore you go onsite, you must:

● Complete the tasks in the Checklist of tasks to perform before you go on site on page 36.

● Get an updated RFA license file. For more information, see RFA license and authentication files on page 38.



Checklist of tasks to perform before you go on site

Task Description

Verify that your Services laptop has the appropriate hardware.

Correct hardware includes:● 32 MB RAM● 40 MB of available disk space● A direct Ethernet cable● A serial cable and an adapter● An RS-232 port connector● A Network interface card (NIC) with a 10/100

BaseT Ethernet interface● A 10/100 BaseT Ethernet, category 5, or better,

crossconnect cable with an RJ45 connector on each end, MDI to MDI-X

● A CD-ROM drive

Verify that your Services laptop has the appropriate software.

Correct software includes:● Windows 2000 or Windows XP operating

system● HyperTerminal or another terminal emulation

program● TCP/IP networking software, which is bundled

with the Windows OS● Internet Explorer 5.0 or later● PuTTY software tool for SSH logins, available

from http://www.putty.nl/download.html.

Obtain the information related to the server used for backups.

Obtain the following attributes for using the backup server on the network to back up the Communication Manager and Communication Manager Messaging Servers:

● method of backup (SCP/SFTP/FTP, or local flashcard connected to the server)

● login

● password

● IP address

● Directory for backups

1 of 3

http://www.putty.nl/download.html


Issue 1 May 2009 37

Obtain the appropriate logins and passwords for all equipment and software.

For example, obtain logins and passwords for the following components:

● Server● Media gateway● Auxiliary equipment● Communication Manager

These logins and passwords include those initially needed by the customer.

Obtain the server ID (SID) for the servers.

You must have a serial number to obtain an update for an existing license file.

● If you have a media gateway, you need the serial number from the media gateway.

● If you have a server, you need the serial number from the reference IPSI.

Verify that you have the Communication Manager software distribution CD-ROM with the current software and firmware.

Use this CD-ROM to install the software on the server and upgrade the firmware. The most recent versions of the service packs are also on this CD-ROM.

Verify that you have the current preupgrade and postupgrade (if required) service packs on your laptop computer.

Check which service packs you need and download the files from the Avaya Support Web site, http://avaya.com/support.

Verify that you have the most current firmware.

The following firmware is on the software CD:● IPSIs

● C-LAN

● MedPro

● VAL circuit packs

Firmware is upgraded often. To ensure that you have the most current versions, go to the Avaya Support web site, http://avaya.com/support. Click Downloads and select the product.

Verify that you have the updated license and authentication files.

Updated license and authentication files are necessary for this major upgrade. Obtain information and download files from the Remote Feature Activation (RFA) web site, http://rfa.avaya.com.

Task Description

2 of 3




http://rfa.avaya.com



RFA license and authentication filesUse Remote Feature Activation (RFA) to obtain the Communication Manager license and authentication file. RFA is a Web-based application that is available to Avaya employees and authorized Business Partners. WIth RFA, you can create and deploy license files for all Communication Manager product platforms. For more information about RFA and how to generate license and Avaya authentication files, see the RFA Information page at

http://rfa.avaya.com.

Obtain the static craft password.

If the server of the customer does not have a static craft password, call the ASG Interactive Voice Response number, 800-248-1234 or 720-444-5557 and follow the prompts to get the password. You need the Product ID for the FL or IL number.

Note:Note: The static craft password is for use by

Avaya technicians only who are using a direct connection from a laptop computer to the server.

Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary.

Perform this step only if the configuration of the customer’s INADS alarming modem has changed.

Verify that you copied all the necessary files to your computer.

These files can include:● Service packs● License file● Authentication file● Firmware for programmable circuit packs

Check for an FTP/SCP/SFTP Server or Compact Flash for Backing upData

For more information see: Checking for an FTP/SCP/SFTP Server or Compact Flash for Backing up on page 40

Task Description

3 of 3

http://rfa.avaya.com


Issue 1 May 2009 39

Generating and retrieving license and authentication filesTo generate a license file, you need the following information:

● Your personal single sign-on (SSO) for the RFA Web site authentication login

● The SAP order number

● Required customer information

● For a new license, the serial number of the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that is designated as the reference IPSI

● For an updated license, the RFA system ID (SID) for the existing server

● Internet access to the RFA Web page with Internet Explorer 5.0 or higher

Before you arrive on site, download the license and the authentication file to the Services laptop. You install these files as part of the installation process.

Logins and passwordsOnce you install the authentication file, a challenge/response system called Access Security Gateway (ASG) protects Avaya services logins to the server. The ASG challenge/response protocol confirms the validity of each user, and this reduces the opportunity for unauthorized access.

When you finish installing the authentication file, Communication Manager has a password for the craft login. This password is unique to the server of the customer. You can use the password the next time that you log in as craft, if you access the server through the Services port. Every other means of craft access still requires an ASG challenge/response. RFA records the revised password. ASG Interactive Response provides this password at 1-800-248-1234 or 1-720-444-5557.

Platform/PNC license settings for the S8700-Series ServerFor Communication Manager Release 5.x, the two major types of port network connectivity, IP-PNC and fiber-PNC (also called multiconnect), are both enabled automatically in all licenses for S8700-Series Servers. As a result, unlike the license settings in previous releases, platform 8 for IP-PNC and the Internet Protocol (IP) PNC feature attribute are no longer needed and are not available as license options. For Release 5.x, with a platform 6 license, all connectivity for that server continues to function properly.

For an upgrade of an S8700-Series Server that previously was licensed for platform 8 and IP-PNC, the Release 5.x license requires a change of the platform number to platform 6



(multiconnect). However, all IP-PNC connectivity for that server continues to function properly. In fact, more IP-PNC port networks can be added to the configuration. For an upgrade of an S8700-Series Server that is enabled for platform 6 (multiconnect), the platform 6 designation of the Release 5.x license maintains the functionality of all fiber-PNC connectivity, but also permits the addition of IP-PNC port networks into the configuration.

Checking for an FTP/SCP/SFTP Server or Compact Flash for Backing up

During the installation and upgrade procedures, you must back up the system data to an FTP, or to the USB Compact Flash drive. You use a server on the customer’s LAN for backups.

Note:Note: Only specific releases of Communication Manager allow back up on a SFTP, or a

SCP Server.

● Check with your project manager or the customer for the following information about the FTP Server ((Back up on a SFTP, or SCP Server is limited to a few releases).

- Login ID and password

- IP address

- Directory path on the FTP Server

! Important:Important: Before going to the customer site, make sure that you can use either a customer

server for backups or a compact flash card.

Preserving connections while upgrading an S8700-Series Server

Note:Note: Upgrades to Communication Manager Release 5.x are not connection

preserving.

When upgrading within the same release (for example, R5.0 to R5.x), you can preserve the audio portion of many stable telephone calls throughout the course of the upgrade. You also can preserve the data transmission between many stable fax, data, or multimedia endpoints.


Issue 1 May 2009 41

Note:Note: A "connection" is the transmission of voice or data between two endpoints over

the bearer network. A connection does not include the control signaling portion of calls, such as that used for dialing, ringing, connecting, and disconnecting. A "connection" also does not include signaling for the use of telephone features such as conference, hold, or forwarding. A "stable" call generally is one in which the connection has been established and control signals are no longer being used.

When a connection is preserved, it is not dropped when the upgrade interchange begins. Instead, the voice or data transmission of the call continues until one or both of the callers end the call. Callers can end the call while the upgrade is still in progress or after the upgrade is complete. During the course of the upgrade, Communication Manager does not allow the use of additional calling features on preserved connections.

Note:Note: Every IP telephone reregisters after an upgrade is compete. An IP telephone

whose call is preserved during an upgrade also reregisters when the upgrade is complete, but only after the call also is complete.

Connections not preservedAs with previous releases of Communication Manager, the following connections are not preserved during an upgrade:

● H.323 IP trunks

● SIP trunks (for example, trunks established for SIP endpoints that use Communication Manager and SES for SIP connections)

● ISDN-BRI trunks or stations

● Unstable calls (Examples of unstable calls include those that are in the ringing or dialing stage, calls that are on hold, or calls in any state that require control signaling. Unstable calls are dropped, regardless of whether they are carrying voice or data transmissions.)

● SAT sessions

● Adjunct links (Examples of adjunct links include those to a CMS, ASAI, or CDR adjunct, a link to a system printer, or any other links configured using the IP Services screen.)

Also, connections are not preserved during an upgrade that includes a migration of server hardware. Therefore, connections are not preserved in a migration from an S8700 Server to an S8710/S8720/S8730 Server, or from an S8710 Server to an S8730 Server.



Tools to preserve connections during an upgrade

Pre Upgrade Step Web page

You can use the Pre Upgrade Step Web page (see Figure 5: Pre Upgrade Step window on page 43) to manually preserve connections during a Communication Manager software upgrade (see Manual steps to preserve connections during an upgrade on page 42). When you select Continue on the Pre Upgrade Step Web page, you lock the translations on the active server. This allows the standby server to precisely synchronize translations and preserve connections during the interchange. When the upgrade is complete, the translations are unlocked and the normal synchronization process resumes.

Should you decide to discontinue the upgrade after running the pre-upgrade step, click Undo on the Pre Upgrade Step Web page on the active server. This unlocks translations and resets the state of health.

Manual steps to preserve connections during an upgradeYou perform manual steps to preserve connections immediately after you perform all standard preupgrade tasks. To preserve connections during an upgrade, perform the following steps.

Connecting to the active server

If on site, connect to the Services port on the back of the active server.

If off site, log on to the active server using the actual IP address of the server.

Accessing the server

To access the server:

1. Start the Web browser.

2. In the Address field, type 192.11.13.6 and press Enter to bring up the login Web page.

3. Log in as craft or dadmin.

4. When asked Do you want to suppress alarms?, select yes.

Activating connection preservation during an upgrade

To activate connection preservation:

1. Under Server Upgrade, click Pre Upgrade Step.


Issue 1 May 2009 43

Figure 5: Pre Upgrade Step window



2. On the Pre Upgrade Step window, click Continue to start the pre-upgrade step.

The system shows the status of the pre-upgrade step operations.

When completed, your translations are synchronized. Communication Manager now can preserve connections during the upgrade.

Logging off the active server

Log off of the active server and continue with the standard upgrade process.

! CAUTION:CAUTION: If you decide not to proceed with the upgrade or you stop the upgrade process,

return to the Pre Upgrade Step window and click Undo (see Deactivating connection preservation on the active server (if necessary) on page 44). If you do not undo the Pre Upgrade Step, the standby server will not be synchronized for subsequent translation changes.

Deactivating connection preservation on the active server (if necessary)

Should you decide not to do the upgrade after running the Pre Upgrade Step, click Undo on the active server Pre Upgrade Step window.

Upgrade modules

Issue 1 May 2009 45

The system unlocks translations and resets the state of health. The system shows the status of undoing the pre-upgrade step after you click Undo.

Note:Note: If you complete the upgrade, Communication Manager deactivates the

connection preservation setup automatically. You do not need to deactivate connection preservation manually.

Upgrade modulesThe following modules are contained in this chapter:

● Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/C/D Server (Migration from S8300A to S8300C/D) on page 47

● 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) on page 57

● Upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP on page 67

● Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage Software on page 75

● 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 on page 103

● 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



Introduction

Issue 1 May 2009 47

Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/C/D Server (Migration from S8300A to S8300C/D)

IntroductionThis module provides a high-level list of tasks that you must complete to upgrade Communication Manager from a pre-2.1 release to a 5.x release on an S8300 Server in either primary controller or local survivable processor (LSP) mode.

Note:Note: S8300A Servers cannot upgrade to Communication Manager Release 2.1 and

later. You must migrate the S8300A to an S8300C/S8300D Server to run Communication Manager Release 5.x.

To complete these tasks, you will need the following additional documents:

● Installing and Upgrading the Avaya S8300 Server, 555-234-100.

● Installing and Upgrading the Avaya G700 Media Gateway, 03-603333.

● To obtain this document, go to http://support.avaya.com. Click S8300 > Installations, Migrations, Upgrades & Configurations and then select the document. This document contains detailed procedures for most of the tasks in this upgrade scenario.

● Administering Avaya Aura™ Communication Manager, 03-300509.

In this scenario, an S8300A that is configured as either a primary controller or an LSP and is running Communication Manager Release 1.x, 2.0, 2.0.1 is replaced by an S8300C or S8300D running Communication Manager Release 5.2.

For more information, see Server Migration Paths in Chapter 1 of the book Migrating Avaya Servers and Media Gateways, 03-300412.

! CAUTION:CAUTION: Read this caution if you are upgrading a main server with one or more LSPs from

Communication Manager Release 1.3.2 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 1.3.2 to Release 5.x, it will not get a filesync from the main server until the main server upgrades from Release 1.3.2 to


Upgrading Communication Manager from 1.x, 2.x and replacing S8300A Server with an S8300B/C/D Server


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 1.3.2 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.

Pre-requisitesPerform the tasks in this section before going to the customer site.

Task Steps/Comments

1. Obtain pre-upgrade service pack, if necessary.

If you are upgrading software from certain releases of Communication Manager, you may need to obtain a pre-upgrade service pack (see Table 1: R5.x Upgrade requirements depending on pre-upgrade release on page 49

2. Obtain a replacement S8300C/S8300D Server, if needed.

If you are upgrading an S8300A to software release 5.x, you must replace the S8300A with an S8300C/S8300D Server.

3. Create/update license and authentication files on the RFA web site.

If the S8300 is in LSP mode, and the primary controller that will support the LSP is being migrated to Communication Manager 5.x, you need to create an updated license file for the primary controller.

4. Obtain post-upgrade service pack file.

Go to http://support.avaya.com and click Downloads to obtain the service pack file available for the Communication Manager release to which you are upgrading. (For example, release 5.x.) Download it and take it to the site.

5. Obtain the Communication Manager 5.x software CD and a USB DVD/CD-ROM drive.

After you remaster the drive, the remastering program looks for the Communication Manager software files on the DVD/CD-ROM drive.

http://support.avaya.com/japple/css/japple?PAGE=avaya.css.CSSIndex

Pre-upgrade service pack requirements

Issue 1 May 2009 49

Pre-upgrade service pack requirementsThe upgrade may require a pre-upgrade service pack, depending on the release of Communication Manager from which you are upgrading. Table 1 describes when a service pack is required.

Table 1: R5.x Upgrade requirements depending on pre-upgrade release

Software Release Before Upgrade to Release 5.x

Upgrade Requirement

Release 1.1.x and all other 1.x.x releases not listed belowR011x.01.xxx.x

No pre-upgrade service pack required. You need to back up only translation files. Once the hard drive is remastered and the new software is installed on the S8300B, you must reconfigure the server as if it were a new installation using the Avaya Installation Wizard.

Release 1.2.x, 1.3.0.R011x.02.0.110.4R011x.03.526.6

You must apply a pre-upgrade service pack to the system files before backing up the system and translations files using Linux Migration Backup/Restore (LMBR). Once the hard drive is remastered and the new software is installed on the S8300B, you can restore all the files using View/Restore Data1.

1. The LMBR backup contains backup sets for the translations, OS and system files.

Release 1.3.1.xR011x.03.1.531.0R011x.03.1.5xx.xR011x.03.2.536.1

No pre-upgrade service pack required. Back up the system and translations files using Linux Migration Backup/Restore (LMBR). Once the hard drive is remastered and the new software is installed on the S8300B, you can restore all the files using View/Restore Data.

Release 2.xR012x.00.0.219.0R012x.01.x.xxx.x

No pre-upgrade service pack is required for the Linux backup. However, a different pre-upgrade service pack for a 2.x to 3.1 upgrade is required. Back up the system and translations files using Backup Now2. Once the hard drive is remastered and the new software is installed on the S8300B, you can restore the files using View/Restore Data.

2. The Data backup contains backup sets for the translations, OS and system files, security files, and AUDIX data, if any



Tasks checklistPerform the tasks in this section at the customer site.

Task Steps/Comments

Go to the standard documentation

Use: - Installing and Upgrading the Avaya S8300 Server, 555-234-100.

- Installing and Upgrading the Avaya G700 Media Gateway, 03-603333.

To upgrade the S8300, you complete selected tasks from Chapter 10. You need to complete only some of the tasks in these chapters. The specific tasks are identified by chapter in the left-hand column. The subtasks to perform or skip are listed in the right-hand column.It is important to note where the task is performed. Most of the tasks are done on a server — on the S8300, or on the primary controller for the S8300 (if the S8300 is configured as an LSP). The headings below indicate on which of these devices the task is performed.

On the S8300 (ICC or LSP)

1. If Communication Manager Messaging (CMM) is in use (ICC mode), get CMM data and stop CMM.

See Getting IA770 (AUDIX) Data and Stopping IA770(if IA770 is being used) in Chapter 10.

Note:Note: Communication

Manager Messaging (CMM) - formerly known as IA770 INTUITY AUDIX messaging application.

1 of 6

Tasks checklist

Issue 1 May 2009 51

2. Perform data backup.

See Backing up system files in Chapter 10.

Backup according to the release from which you are upgrading. See Table 1. For the first backup, you will not restore these data sets. It is important to have them in case it is necessary to revert to the original configuration.

3. Record configuration information.

See Recording configuration information in Chapter 10.

If you have not already done so, in the Record Configuration Information task, record all of the configuration information, regardless of the release from which you are upgrading. You will re-enter some of this information after the upgrade.

4. Install pre-upgrade service pack, if necessary.

See Installing the pre-upgrade software service pack, if necessary in Chapter 10.

This service pack allows you to back up data so that it can be restored to a different Linux operating system.

5. Perform the Linux migration backup

See Linux migration backup (if current release is 1.2.0 through 1.3.x) in Chapter 10.

This backup allows you to restore translations and system files after the hard drive has been replaced.

6. Replace the S8300A with the S8300C/S8300D.

See Replacing the S8300A with the S8300B or S8300C Server in Chapter 10.

● Shut down the S8300A.

● Remove the S8300A from the gateway. (If the gateway is a G700, the LED panel must be removed together with the S8300A.)

● Re-insert the S8300C/S8300D (together with the LED panel for a G700) into the gateway.

Task Steps/Comments

2 of 6



7. Upgrade the S8300C/S8300D.

See Upgrading the S8300B or S8300C Server in Chapter 10.

● Set Telnet parameters

● Remaster hard drive and install upgrade software

● ICC Mode: To use CMM (formerly known as IA770), select yes on Run AUDIX Installation screen

● LSP Mode: Select No on Run AUDIX Installation screen.

● Verify software version

● Copy files to the S8300 (license file, authentication file, service pack file)

8. Install post-upgrade service pack file.

See Installing security and Communication Manager service pack updates, if any in Chapter 10.

9. Set time, date, and time zone.

See Setting the time, date, and time zone in Chapter 10.

ICC Mode: The time zone of the new ICC must be set, and all LSPs under the ICC’s control must be set to the new ICC’s time zone.LSP Mode: The time of the LSP must be set to the same time zone as its primary controller, even if the LSP is physically located in a different time zone.

! Important:Important: If you change the time zone, you

must reboot the server.

10. Restore data backup.

See Restoring data backup in Chapter 10.

Select the restore procedure according to the release from which you upgraded.

● ICC Mode: Restore Translations and AUDIX files, if used.

● LSP Mode: Restore operating system and security files.

11. Reboot the server

See Rebooting the Server in Chapter 7.

A server reboot (Shutdown with/restart)should be done. Use the Shutdown Server link on the System Management Interface (SMI).

Task Steps/Comments

3 of 6

Tasks checklist

Issue 1 May 2009 53

12. Install license file and authentication file.

See Installing updated license and authentication files in Chapter 10.

13. Create a super-user login, if necessary.

See Creating a super-user login, if necessary, for R5.0 or higher in Chapter 10.

14. Verify that the media gateway has registered with either the primary controller (LSP mode) or the S8300C/S8300D (ICC mode).

● Open a SAT session with either the primary controller (LSP mode) or the S8300C/S8300D (ICC mode) and enter list media-gateway.

Verify that the Registered field (Reg?) is set to y.

● Place a test call.

ICC mode: On LSPs of the S8300C/S8300D (if any)

15. Reboot LSPs (if any). At the LSP’s SAT prompt, enter reset system 4.

16. Verify LSP translations date and time (if any).

To view the LSP’s translations date and time, enter list configuration software.

ICC mode: On the S8300C/S8300D

17. Verify LSP status (if any). ● At the ICC’s SAT prompt, enter list survivable-processor.

The LSP name and IP address should be listed.

● The Translations Updated should match the translations date and time on the ICC. To view the ICC’s translations date and time, enter list configuration software.

Task Steps/Comments

4 of 6



18. If the LSPs (if any) translations have not synchronized with the ICC, invoke translation synchronization.

● On the ICC’s SAT, enter the command save translation lsp.

● Ensure that the translation synchronization completed successfully.

Wait several minutes, then check the timestamp of the LSP’s translation files with the SAT command list survivable-processor on the ICC.

LSP mode: On the S8300C/S8300D’s primary controller

19. Verify S8300C/S8300D LSP status (if any).

● At the primary controller’s SAT prompt, enter list survivable-processor.

The S8300C/S8300D LSP name and IP address should be listed.

● The Translations Updated should match the translations date and time on the primary controller. To view the primary controller’s translations date and time, enter list configuration software.

20. If the S8300C/S8300D LSP’s translations have not synchronized with the primary controller, invoke translation synchronization.

● On the primary controller’s SAT, enter the command, save translation lsp.


Wait several minutes, then check the timestamp of the LSP’s translation files with the SAT command list survivable-processor on the primary controller.

21. Upgrade G700 Media Gateway firmware

See Installing new firmware on the G700 Media Gateway Processor in Chapter 10.

Using the Avaya Installation Wizard:● Upgrade G700 firmware

● Upgrade media module firmware

Task Steps/Comments

5 of 6

Tasks checklist

Issue 1 May 2009 55

22. Set Rapid Spanning Tree

See Setting rapid spanning tree on the network in Chapter 10.

Post-upgrade tasks

23. Implement any additional design changes to voice and/or voice messaging networks.

24. Re-register the S8300C/S8300D (LSP mode only) with the Avaya servicing center.

Task Steps/Comments

6 of 6



Introduction

Issue 1 May 2009 57

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)

IntroductionThis module provides a high-level list of tasks that you must complete to upgrade an S8300B Server running Communication Manager from a pre-2.1 release to a 5.x release on an S8300C/S8300D Server in either primary controller or local survivable processor (LSP) mode.




● To obtain this document, go to http://support.avaya.com. Click S8300 > Installations, Migrations, Upgrades & Configurations and then select the document. This document contains detailed procedures for most of the tasks in this upgrade scenario.


In this scenario, an S8300B that is configured as either a primary controller or an LSP and is running Communication Manager 2.0 or later release is replaced by an S8300C or S8300D running Communication Manager Release 5.2.

For more information, see Server Migration Paths in Chapter 1 of the book Migrating Avaya Servers and Media Gateways, 03-300412.


Upgrading Communication Manager from 2.x, 3.x or 4.x to 5.x and replacing S8300B Server with an S8300C/


Pre-requisitesPerform the tasks in this section before going to the customer site.

Task Steps/Comments

1. Obtain pre-upgrade service pack, if necessary.

If you are upgrading software from certain releases of Communication Manager, you may need to obtain a pre-upgrade service pack (see Table 2: R5.x Upgrade requirements depending on pre-upgrade release on page 59

2. Obtain a replacement S8300C/S8300D Server, if needed.

If you are upgrading an S8300B to software release 5.x, you can replace the S8300B with an S8300C/S8300D Server.

3. Create/update license and authentication files on the RFA web site.

If the S8300 is in LSP mode, and the primary controller that will support the LSP is being migrated to Communication Manager 5.x, you need to create an updated license file for the primary controller.


Go to http://support.avaya.com and click Downloads to obtain the service pack file available for the Communication Manager release to which you are upgrading. (For example, release 5.x.) Download it and take it to the site.




Pre-upgrade service pack requirements

Issue 1 May 2009 59

Pre-upgrade service pack requirementsThe upgrade may require a pre-upgrade service pack, depending on the release of Communication Manager from which you are upgrading. Table 2 describes when a service pack is required.

Table 2: R5.x Upgrade requirements depending on pre-upgrade release

Software Release Before Upgrade to Release 5.x

Upgrade Requirement

Release 1.1.x and all other 1.x.x releases not listed belowR011x.01.xxx.x

No pre-upgrade service pack required. You need to back up only translation files. Once the hard drive is remastered and the new software is installed on the S8300B, you must reconfigure the server as if it were a new installation using the Avaya Installation Wizard.

Release 1.2.x, 1.3.0.R011x.02.0.110.4R011x.03.526.6

You must apply a pre-upgrade service pack to the system files before backing up the system and translations files using Linux Migration Backup/Restore (LMBR). Once the hard drive is remastered and the new software is installed on the S8300B, you can restore all the files using View/Restore Data1.

1. The LMBR backup contains backup sets for the translations, OS and system files.

Release 1.3.1.xR011x.03.1.531.0R011x.03.1.5xx.xR011x.03.2.536.1

No pre-upgrade service pack required. Back up the system and translations files using Linux Migration Backup/Restore (LMBR). Once the hard drive is remastered and the new software is installed on the S8300B, you can restore all the files using View/Restore Data.

Release 2.xR012x.00.0.219.0R012x.01.x.xxx.x

No pre-upgrade service pack is required for the Linux backup. However, a different pre-upgrade service pack for a 2.x to 3.1 upgrade is required. Back up the system and translations files using Backup Now2. Once the hard drive is remastered and the new software is installed on the S8300B, you can restore the files using View/Restore Data.

2. The Data backup contains backup sets for the translations, OS and system files, security files, and AUDIX data, if any



Tasks checklistPerform the tasks in this section at the customer site.

Task Steps/Comments


Use:- Installing and Upgrading the Avaya S8300 Server, 555-234-100.


To upgrade the S8300, you complete selected tasks from Chapter 12. You need to complete only some of the tasks in these chapters. The specific tasks are identified by chapter in the left-hand column. The subtasks to perform or skip are listed in the right-hand column.It is important to note where the task is performed. Most of the tasks are done on a server — on the S8300, or on the primary controller for the S8300 (if the S8300 is configured as an LSP). The headings below indicate on which of these devices the task is performed.


1. Create a super-user login.

See Creating a super-user login, if one does not exist (releases earlier than Release 5.x) in Chapter 12.

1 of 6

Tasks checklist

Issue 1 May 2009 61

2. If CMM (formerly known as IA770) is in use (ICC mode), get CMM data and stop CMM.




3. Perform data backup.

See Backing up S8300 recovery system files in Chapter 12.

Backup according to the release from which you are upgrading. See Table 2. For the first backup, you will not restore these data sets. It is important to have them in case it is necessary to revert to the original configuration.

4. Record configuration information.

See Recording configuration information in Chapter 12.


5. Replace the S8300B with the S8300C/S8300D.

See Replacing the S8300B with the S8300C Server in Chapter 12.

● Shut down the S8300B.

● Remove the S8300B from the gateway. (If the gateway is a G700, the LED panel must be removed together with the S8300B.)

● Reinsert the LED panel.

● Install the S8300C/S8300D.

Task Steps/Comments

2 of 6



6. Remaster the hard drive and install the software.

See Remastering the hard drive and installing the software in Chapter 12.

● Set Telnet parameters

● Remaster hard drive and install upgrade software

● ICC Mode: To use CMM (formerly known as IA770), select yes on Run AUDIX Installation screen

● LSP Mode: Select No on Run AUDIX Installation screen.

● Verify software version


See Installing security and Communication Manager service pack updates, if any in Chapter 12.

8. Set time, date, and time zone.

See Setting the time, date, and time zone in Chapter 12.

ICC Mode: The time zone of the new ICC must be set, and all LSPs under the ICC’s control must be set to the new ICC’s time zone.LSP Mode: The time of the LSP must be set to the same time zone as its primary controller, even if the LSP is physically located in a different time zone.

9. Restore all data to the server.

See Restoring all data in Chapter 12.


10. Restore data backup.

See Restoring data backup in Chapter 12.

Select the restore procedure according to the release from which you upgraded.

● ICC Mode: Restore Translations and AUDIX files, if used.

● LSP Mode: Restore operating system and security files.

11. Reboot the server

See Rebooting the Server in Chapter 7.

A server reboot (Shutdown with/restart)should be done. Use the Shutdown Server link on the System Management Interface (SMI).

Task Steps/Comments

3 of 6

Tasks checklist

Issue 1 May 2009 63

12. Install license file and authentication file.

See Installing updated license and authentication files in Chapter 12.

13. Create a super-user login, if necessary.

See Creating a super-user login, if necessary, for R5.0 or higher in Chapter 12.

14. Verify that the media gateway has registered with either the primary controller (LSP mode) or the S8300C/S8300D (ICC mode).

● Open a SAT session with either the primary controller (LSP mode) or the S8300C/S8300D (ICC mode) and enter list media-gateway.

Verify that the Registered field (Reg?) is set to y.


ICC mode: On LSPs of the S8300B (if any)

15. Reboot LSPs (if any). At the LSP’s SAT prompt, enter reset system 4.


To view the LSP’s translations date and time, enter list configuration software.

ICC mode: On the S8300B

17. Verify LSP status (if any). ● At the ICC’s SAT prompt, enter list survivable-processor.

The LSP name and IP address should be listed.

● The Translations Updated should match the translations date and time on the ICC. To view the ICC’s translations date and time, enter list configuration software.

Task Steps/Comments

4 of 6






Wait several minutes, then check the timestamp of the LSP’s translation files with the SAT command list survivable-processor on the ICC.

LSP mode: On the S8300B’s primary controller

19. Verify S8300C/S8300D LSP status (if any).

● At the primary controller’s SAT prompt, enter list survivable-processor.

The S8300C/S8300D LSP name and IP address should be listed.

● The Translations Updated should match the translations date and time on the primary controller. To view the primary controller’s translations date and time, enter list configuration software.

20. If the S8300C/S8300D LSP’s translations have not synchronized with the primary controller, invoke translation synchronization.

● On the primary controller’s SAT, enter the command, save translation lsp.


Wait several minutes, then check the timestamp of the LSP’s translation files with the SAT command list survivable-processor on the primary controller.

21. Install G700 Media Gateway firmware.

See Installing new firmware on the G700 Media Gateway Processor in Chapter 12.

Using the Avaya Installation Wizard:● Upgrade G700 firmware


Task Steps/Comments

5 of 6

Tasks checklist

Issue 1 May 2009 65



23. Install firmware on other G700 Media Gateways.

See Installing new firmware on other G700 media gateways in Chapter 12.

Post-upgrade tasks

24. Implement any additional design changes to voice and/or voice messaging networks.

25. Re-register the S8300C/S8300D (LSP mode only) with the Avaya servicing center.

Task Steps/Comments

6 of 6



Introduction

Issue 1 May 2009 67

Upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP

IntroductionThis module provides a high-level list of tasks for upgrading Communication Manager from 2.x, 3.x, or 4.x to 5.x on an S8300 Server or S8300 LSP.





Note:Note: The following procedures are for:

- an S8300B/S8300C/S8300D Server running Communication Manager Release 2.1 or higher.

- an S8300C Server running Communication Manager Release 4.0 or higher.

Note:Note: Upgrades of S8300 to Release 5.x are not connection or call preserving.







● To obtain this document, go to http://support.avaya.com and navigate to S8300 > Installations, Migrations, Upgrades & Configurations. Select the appropriate document. This document contains detailed procedures for most of the tasks in this upgrade scenario.


PrerequisitesPerform the tasks in this section before going to the customer site.

Task Steps/Comments

1. Create/update a license and authentication file on the RFA web site.

You must create a new license file for the primary controller if both of the following situations are true:

● the S8300B/S8300C/S8300D is in LSP mode

● the primary controller that will support the LSP is being migrated to Communication Manager 5.x.


To download the service pack file available for the Communication Manager release to which you are upgrading go to http://support.avaya.com and click Downloads. Download the service pack and take it to the site.





Tasks

Issue 1 May 2009 69

TasksPerform the tasks in this section at the customer site.

Task Steps/Comments


Use:- Installing and Upgrading the Avaya S8300 Server, 555-234-100.


To upgrade the S8300, you complete selected tasks from Chapter 12. You need to complete only some of the tasks in these chapters. The page number associated with specific tasks are located in the left column. The subtasks to perform or skip are listed in the right column.Note where the task is performed. Most of the tasks are done on a server. The server is either the S8300 or the primary controller for the S8300 when the S8300 is configured as an LSP. The following headings indicate on which of these devices the task is performed.


1. If CMM (formerly known as IA770) is in use (ICC mode), get CMM data and stop CMM.




1 of 6



2. Backup all system files — translations, OS, and security backup sets.

See Backing up S8300 recovery system files in Chapter 12.

Note:Note: The following backup sets are not

restored on the S8300B/S8300C/S8300D. Back up the sets in case it is necessary to revert to the original configuration.

ICC: Translations, server and system files, and security files.LSP: Server and system files, and security files.

3. Install preupgrade service pack (R2.x only)

See Copying and installing the service pack files to the server (starting from R2.x only) in Chapter 12.

You must install this service pack to enable the S8300B/S8300C/S8300D Web Interface to upload and install the CM 5.x software.

Task Steps/Comments

2 of 6

Tasks

Issue 1 May 2009 71

4. Upgrade the S8300B/S8300C/S8300D, using the Web Interface, Manage Software screens.

See Copying the software and firmware files to the server and Installing new software in Chapter 12.

● Copy files from the Communication Manager Software Distribution CD.

● Install files on the S8300B/S8300C/S8300D.

● Make the upgrade permanent.

! 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 the Latest Communication Manager Software & Firmware Compatibility Matrix for compatibility of software loads between the primary controller and any LSPs or ESSs. If the software loads of the primary controller and the LSPs/ESSs are incompatible, then file synchronization between the primary controller and the LSPs/ESSs can cause translation corruption on the LSPs/ESSs.

To check the Latest Communication Manager Software & Firmware Compatibility Matrix from any computer, access http://support.avaya.com. Select Downloads > Latest TN Circuit Pack, Server, and Media Gateway Firmware and Software Updates > Latest Communication Manager Software & Firmware Compatibility Matrix.

Task Steps/Comments

3 of 6






See Installing post-upgrade Communication Manager service pack file from your laptop, if any in Chapter 12.

6. Install the updated license and authentication file

See Install updated license and authentication files in Chapter 12.

7. Save Translations

See Saving translations in Chapter 12.

8. Verify that the media gateway has registered with either the primary controller (LSP mode) or the S8300B/S8300C/S8300D (ICC mode).

● Open a SAT session with either the primary controller (LSP mode) or the S8300B/S8300C/S8300D (ICC mode) and enter list media-gateway.

Verify that the Registered field (Reg?) is y.


ICC mode: On LSPs of the S8300B/S8300C/S8300D (if any)

9. Reboot LSPs (if any) At the LSP’s SAT prompt, enter reset system 4.


To view the date and time of the LSP translations, enter list configuration software.

ICC mode: On the S8300B/S8300C/S8300D (primary controller)

11. Verify LSP status (if any) ● At the SAT prompt, enter list survivable-processor. The LSP name and IP address should be listed.

● The Translations Updated field shows the time and date of the translation most recently copied to the survivable server.

Task Steps/Comments

4 of 6

Tasks

Issue 1 May 2009 73




Wait several minutes. Then check the timestamp of the LSP translation files using the SAT command list survivable-processor on the ICC.

LSP mode: On the primary controller of the S8300B/S8300C/S8300D

13. Verify S8300B/S8300C/S8300D LSP status (if any)

● At the SAT prompt, enter list survivable-processor. The LSP name and IP address should be listed.

● The Translations Updated field shows the time and date of the translation most recently copied to the survivable server.

14. If the S8300B/S8300C/S8300D LSP’s translations have not synchronized with the primary controller, invoke translation synchronization.

● On the primary controller’s SAT, enter the command, save translation lsp ipaddress where ipaddress is the IP address of the LSP.

● Ensure that the translation synchronization completed successfully. Wait several minutes, then check the timestamp of the LSP translation files using the SAT command list survivable-processor on the primary controller.

15. Upgrade media gateway firmware

See Manually upgrading G700 firmware in Chapter 12.

Using the Avaya Installation Wizard:● Upgrade media gateway firmware




Task Steps/Comments

5 of 6



Post-upgrade tasks

17. Implement any additional design changes to either or both voice networks and voice messaging networks.

18. Reregister the S8300B/S8300C/S8300D in LSP mode with the Avaya servicing center.

Task Steps/Comments

6 of 6

Issue 1 May 2009 75

Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage Software

Use this procedure to upgrade Communication Manager on an S8400 Server from Communication Manager Release 3.1, 3.1.x, 4.x, 5.x to Communication Manager Release 5.2. This procedure uses the Manage Software link on the System Management Interface (formerly known as Maintenance Web Interface).

Note:Note: For Pre-Release 5.2 use the Maintenance Web Interface, and for Release 5.2

use the System Management Interface (SMI). You cannot use Upgrade Tool or Avaya Installation Wizard (AIW) for the upgrade procedures to Communication Manager Release 5.2 or later.

! Important:Important: If the S8400 has voice mail, the CMM (formerly known as IA770) requires the

TN2302 to have a minimum hardware version of 10 and a minimum firmware version of 80. The TN2302ap HV3 is not supported.






Upgrading Communication Manager on Avaya S8400 Server from R3.x/R4.x/R5.x to R5.2 using Manage


Note:Note: S8400 upgrades are not connection or call preserving.

An upgrade from Release 3.x to Release 5.x requires an updated RFA license file. For more information on generating a license file, see RFA license and authentication files on page 38.

PrerequisitesBefore you go onsite, you must complete the tasks in the Checklist of tasks to perform before you go on site on page 36.

The need to restore IP telephone files If this S8400 server is used for IP telephone firmware downloads, the IP telephone firmware files must be reinstalled to the server after the upgrade. The system might use files in the /tftpboot directory for the http or tftp capability for 4600-series IP telephone firmware downloads and configuration updates. If so, the firmware and 4600-series telephone configuration file are overwritten during the upgrade.

The 46xx firmware is contained within a 46xx .tar file, in a name format similar to the filename 46xxH323_cm2_2_wi1_15_ipt2_2_111405.tar. You must retrieve the firmware file from the Avaya Downloads Web site and download the 46xx firmware file to the server after the upgrade. The upgrade to Release 5.x preserves the /tftpboot/46xxsettings.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. However, you can save a copy of the 46xx configuration file before the upgrade and copy the file back into the /tftpboot directory after the upgrade.

For more information on copying and installing the IP telephone firmware files to the server, see the following tasks:

● Saving a copy of the 4600-series telephone configuration file, if any on page 80

● Copying IP telephone firmware to the server, if necessary on page 95

TN8412AP SIPI circuit pack upgradesThe TN8412AP S8400 IP Interface (SIPI) circuit packs must have the most recent release of the firmware before you upgrade Communication Manager on the server. Upgrade the SIPI firmware first. For firmware upgrade procedures, see Upgrading firmware on the IPSIs and SIPIs on page 213.

Preupgrade tasks

Issue 1 May 2009 77

Upgrading LSPs and media gateways, if any

Note:Note: If the customer has none of the following network elements, do not perform these

tasks and go to Accessing the server’s web interface on page 80:

- H.248 media gateways

- Local survivable processors (LSPs)

You must upgrade Communication Manager on the LSPs before you upgrade Communication Manager on the primary controller. If the configuration uses media gateways, you must upgrade them to the latest firmware.

The correct order is:

1. If the system includes one or more LSPs, upgrade Communication Manager on the LSP to the latest version.

2. Upgrade the firmware on the media gateway and the media modules to the latest version.

3. Upgrade Communication Manager on the primary controller to the latest version.

Preupgrade tasks

Upgrading the MPC firmwareBefore you upgrade the S8400 Server to Communication Manager R5.x, upgrade the firmware on the Avaya Maintenance Processor Complex (MPC) card. Check the Downloads section at http://support.avaya.com for the most recent firmware available for the S8400 Server and MCP.

Connecting to the serverPerform one of the following options:

● If you are on site, connect to the services port.

● If you are off site, use the IP address of the server to log on to the server.




Starting a SAT sessionTo start a SAT session:

1. Open a terminal emulation application, such as MS HyperTerminal.

2. Type 192.11.13.6 5023 and press Enter.3. Log on as craft or dadmin.

Note:Note: You must use SAT commands for tasks in Checking link status with SAT (main

server only) on page 78 through Checking for translation corruption on page 79.

Checking link status with SAT (main server only)

1. Type display communication-interface links and press Enter.2. Note all administered links.

3. Type status link number and press Enter for each administered link.

4. Check the following fields for the values listed:

● Link Status = connected● Service State = in service

5. Type list signaling group and press Enter.6. Note the signaling groups that are listed by number.

7. For each of the signaling groups listed, type status signaling group number and press Enter.

8. Make a note of any links that are not operating. Also, note any links that might be not operating because the customer does not use the links.

Recording all busyouts1. Type display errors and press Enter.

Preupgrade tasks

Issue 1 May 2009 79

2. Look for type 18 errors and record any trunks that are busied out. You can return these trunks to the busyout state after the migration/upgrade.

Checking synchronization with the SAT (main server only)1. Type status sync and press Enter to verify that the clock synchronization is

correct.

2. Make a note of any outages.

Disabling scheduled maintenance with the SAT (main server only)

1. Type change system-parameters maintenance and press Enter.2. Perform one of the following actions:

● If scheduled maintenance is in progress, set the Stop Time field to 1 minute after the current time.

● If scheduled maintenance is not in progress, set the Start Time field to a time after the upgrade is completed.

For example, if you start the upgrade at 8:00 p.m. and the upgrade takes 4 hours, set the Start Time field to 23:59.

Checking for translation corruptionTo check for translation corruption:

1. Type newterm and press Enter. 2. If you see the following message

Warning: Translation corruption detectedthen follow the normal escalation procedure for translation corruption before you continue the upgrade.



Saving a copy of the 4600-series telephone configuration file, if any

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. If the system uses the http or tftp server capability, the 4600-series IP Telephone firmware and configuration file in the /tftpboot directory are overwritten.

The 46xx firmware is contained within a 46xx .tar file, in a name format similar to the filename 46xxH323_cm2_2_wi1_15_ipt2_2_111405.tar. You must retrieve the firmware file from the Avaya Downloads Web site and download the 46xx firmware file to the server after the upgrade. However, you can save a copy of the 46xx configuration file before the upgrade and copy the file back into the /tftpboot directory after the upgrade.

You must redownload the 46xx firmware file after the upgrade. However, you can save a copy of the 46xx configuration file before the upgrade and copy the file back into the /tftpboot directory after the upgrade.

To copy the 4600-series configuration file to a safe location:

1. Access the command line interface of the server with telnet and an IP address of 192.11.13.6.

2. Log in as craft.

3. At the Linux command line, type cd /tftpboot, and press Enter.4. At the prompt, type ls 46*, and press Enter.

A named 46xxsettings.txt file appears in the list, or the prompt reappears with no files listed. If the file name does not appear, there is no file to copy. You are finished with this procedure.

5. If the file name 46xxsettings.txt appears, at the Linux command line, type cp 46xxsettings.txt ~ftp/pub.

6. The 4600-series IP Telephone settings file is now in a protected directory, /var/home/ftp/pub, and cannot be overwritten during the upgrade. Copy this file back to the /tftpboot directory after the upgrade.

Accessing the server’s web interface

1. Connect to the Services port on the faceplate of the server.


Preupgrade tasks

Issue 1 May 2009 81

3. In the Address field, type 192.11.13.6. Press Enter to open the login Web page.


5. Click yes to suppress alarms

The system displays the System Management Interface (formerly known as Maintenance Web Interface).

Copying files to the server To copy files to the server:

Copy the following files, as appropriate, from the computer to the server:

● License file and Avaya Authentication file

Note:Note: A preupgrade service pack is required for an upgrade from Release 2.x.;

● Preupgrade service pack files, if necessary

● Postupgrade service pack files if necessary

● Security update files (used post-upgrade, if necessary)

● Programmable circuit pack firmware

To copy files to the server:

1. Use the System Management Interface (formerly known as Maintenance Web Interface).. Under Miscellaneous, click Download Files.

2. Select File(s) to download from the machine I’m using to connect to the server.

Note:Note: Do not select the check box, “Install this file on the local server.”

3. Click Browse next to the top field to open the Choose File window on your computer. Find the files that you need to copy to the server.

4. Click Download to copy the files to the server.

The system copies the files automatically to the default file location.

5. Repeat steps 1 through 4 for each survivable server that will be upgraded.



Resolving alarmsTo clear alarms:

1. Use the System Management Interface (SMI) (formerly known as Maintenance Web Interface). Under Alarms, click Current Alarms to examine the alarm log.

2. Select the server alarms that you want to clear and click Clear, or click Clear All.3. Resolve or clear Communication Manager alarms with SAT commands and the

Maintenance Commands Reference and Alarms Maintenance books.

Ensuring a super-user login existsTo ensure that a super-user login exists in Communication Manager:

1. Ask the customer to access the Login Administration SAT screen with a super-user login to verify that a super-user login exists.

Alternatively, a Business Partner may need to verify that a super-user account exists and can be used to access the server and the SAT.

2. If a super-user account does not exist, you can create one after you have upgraded the software.

For more information, see Creating a customer login (if necessary) on page 132.

Backing up recovery system filesTo back up the system configuration files:

1. Under Data Backup/Restore, click Backup Now.

2. Select the data sets, including Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. Do not select Full Backup because this option does not save translations.

If the AUDIX options are available, select AUDIX and select AUDIX Translations, Names, and Messages. Do not select Full Backup because this option does not back up AUDIX files.

Preupgrade tasks

Issue 1 May 2009 83

Note:Note: If you back up to a flashcard, Avaya recommends that you use a different

flashcard from the one with the prior release translations. You might need these translations if you need to back out of the upgrade, migration, or conversion procedure.

3. Select the backup method (Network Device, Local CompactFlash card).

4. Click Start Backup to start the back up process.

5. Repeat steps 1 through 4 and select AUDIX Announcements.

Verifying the backupTo verify that the backup was successful:

1. Under Data Backup/Restore, click Backup History.

2. Select the backup that you want to verify, and click Check Status.

The system displays the status of the backup.

3. Verify that Backup Successful appears for each data set in the backup.

Suppressing alarming

! CAUTION:CAUTION: Ensure that you suppress alarming during the upgrade. If you do not, the system

can generate alarms, resulting in unnecessary trouble tickets.

To suppress alarming:

1. Access the command line interface of the server with telnet or an SSH client like PuTTY and an IP address of 192.11.13.6.

2. Log in as craft.

3. Type almsuppress -t time, where time is the length of time that the alarms are suppressed up to 120 minutes (2 hours). Press Enter to suppress both dial-out and SNMP alarms.

The system displays the following message:

Alarm is suppressed. 120 minutes left.



4. Log off and close the dialog box.

Upgrade tasks





Connecting the CD/DVD-ROM drive to the serverThere are three external USB CD/DVD-ROM drives that support the S8400 Servers:

● Panasonic Digistor 73082:

- The switch must be turned to the ON position.- Instead of AC power, the Panasonic uses Lithium ION battery for additional power.The

ION battery draws more power than the S8400 Server supplies. If the ION battery is depleted a red LED displays and a failed to mount cdrom message appears. You can charge the ION battery by plugging the CD-ROM drive in a USB port for approximately 30 minutes. The ION battery charges faster if the ON/OFF switch is set to OFF.TEAC (no longer available): CD reader only


Upgrade tasks

Issue 1 May 2009 85

● Addonics (not available through Avaya):

- Requires AC power to operate. - You must have the switch set to EXTernal.

● TEAC (no longer available): CD reader only

Note:Note: You can copy the Communication Manager software from an http or tftp server

onto the server. In this case, skip this step.

Note:Note: The CD/DVD-ROM drive must be placed on a surface within 5 degrees of level.

To connect the CD/DVD-ROM drive to the S8400 Server:

1. If this is an Addonics drive, plug one end of the CD/DVD-ROM power cord into the drive and plug the other end of the cord into an electrical outlet.

2. Set the power switch to "EXT" (Addonics) or to ON (Panasonic).

3. Connect the USB cable to the USB port on the faceplate of the server and the other end of the USB cable to the CD/DVD-ROM drive (all 3 readers).

4. Place the Communication Manager CD-ROM into the external CD/DVD-ROM. Turn on the S8400 Server.



Copying Communication Manager to the server To copy Communication Manager to the server:

1. Under Server Upgrades, select Manage Software.

! Important:Important: If three releases already reside on the hard disk, you must delete one release to

make room for the new release.

2. Perform one of the following actions:

● If three releases already reside on the hard disk

a. Select Delete one of the above releases from the local hard drive. Click Continue to view the releases available.

b. Select the software release that you want to delete and click Delete.

When complete, the system displays the following message:

Deletion Completec. Click Continue to return to the initial Manage Software page.

● If fewer than 3 releases resides on the hard disk

a. Select one of the following:

Upgrade tasks

Issue 1 May 2009 87

- Copy a release to the local hard drive, but do not install it- Copy from TFTP server at this IP address- Copy from URLand click Continue to view the options for copying the software to the hard disk.

b. Select Copy from this server’s CD-ROM drive: and click Continue.

c. The Choose Software screen appears, which you use to copy files from the source you selected.

d. Select the release to be copied and click Continue.

e. The system displays the Copy in Progress screen.

f. View the progress screen as the software is copied to the hard disk.


Successg. Click Continue to return to the initial Manage Software page.

h. Click Cancel to close the page.

Removing the CD-ROM from the CD-ROM driveTo release the CD tray and remove the CD:

1. Push the button on the CD-ROM drive to release the CD-ROM tray.

If the tray is not released, go to the System Management Interface (formerly known as Maintenance Web Interface) main menu. Under Server Configuration, click Eject CD-ROM.

2. Remove the Communication Manager CD-ROM from the tray and close the tray.

Note:Note: Skip this step if you intend to immediately continue with the software upgrade.

The CD will eject automatically during the procedure of Rebooting the server on page 90.



Installing Communication Manager on the server

! CAUTION:CAUTION: If you are upgrading existing software, did you check Latest Communication

Manager Software & Firmware Compatibility Matrix to make sure the upgrade path to the new load is supported?

To install Communication Manager on the server:

1. Select Install one of the following releases currently resident on the local hard drive and click Continue.

2. Select:

a. the software release you want.

! CAUTION:CAUTION: For the next step, if you select No, the Communication Manager Messaging

(CMM) - formerly known as IA770 INTUITY AUDIX messaging application - will not be available after the upgrade.

b. If the system supports CMM (formerly known as IA770) voice messaging system, select Yes.

Upgrade tasks

Issue 1 May 2009 89

c. Click Continue.

3. If you have copied the license and authentication files to the server, select the following options:

- If a super-user login already existed prior to the upgrade, select:

● I will supply the license files myself when prompted later in this process. ● Update authentication information as well as license information.

- If a super-user login did not exist prior to the upgrade, select:

● I will supply the license files myself when prompted later in this process. ● Do not update authentication information.

4. Click Continue.

5. For a new installation, or if you previously ran a backup, you do not need to run a backup at this time.

If your planning documents instruct you to enable Tripwire, follow the instructions to reset the signature database.

6. Click Continue.

The system displays the Begin Installation window. The page summarizes the request you have made.



7. Click Continue.

The installation takes 10 to 20 minutes.

The Install in Progress window refreshes every 10 seconds or on demand by clicking Refresh. When complete, the system displays the Reboot Server window.

Rebooting the server

Note:Note: When you reboot the server, it can no longer communicate with the Web

interface. The Reboot in Progress Web page remains on your screen until the reboot is complete. Although the Continue button is visible, do not click Continue yet.

To reboot the server.

1. Click Reboot. The system displays the Reboot in Progress screen. The tray of the CD-ROM drive opens automatically.

2. Remove the CD-ROM from the CD-ROM drive.

! CAUTION:CAUTION: If you do not remove the CD-ROM and the tray of the CD-ROM drive closes

again, the system might try to reboot from the software on the CD-ROM.

Note:Note: The reboot can take 5 minutes or longer. The system does not automatically tell

you when the reboot is complete.

Note:Note: The Web page does not show progress of the reboot process, so you do not

know when the reboot is complete. To check the progress, see Verifying reboot progress on page 91.

3. Wait 3 minutes and then click Continue. If you click Continue before the reboot is finished, the screen displays Expired Page. If you see the Expired Page message, refresh the browser. If the Session Timeout screen appears, close the screen, logoff, and log on again. Select Manage Software, select the option Join this upgrade session in progress and monitor its activity. Click the Pickup button.

Upgrade tasks

Issue 1 May 2009 91

! CAUTION:CAUTION: DO NOT CLICK CANCEL past this point. Be patient. If the installation fails, a

message appears on the Reboot in Progress screen.

Note:Note: This Web session will be interrupted by the reboot which occurs during the

upgrade of the primary server. After the reboot, you can continue to use the Manage Software window without logging in.

4. When the reboot is complete, click Continue to display the Update Tripwire Database screen. If you selected the install license files option earlier in the process, you are prompted to install the updated license and Avaya authentication files.

Click Continue to install the license and Avaya authentication files.

5. Clicking Continue again displays the Update Tripwire Database window.

6. Unless instructed in your planning documents to update the tripwire database, select Do not update the tripwire data base now and click Continue.

7. Click Close.

The Manage Software window closes and returns you to the main menu.

Note:Note: This Web session will be interrupted by the reboot that occurs during the primary

server upgrade. After the reboot, the links in the main menu of the Web interface will not function. Therefore, you must close and reopen the Web browser to continue with the upgrade procedure.

8. Close the Web browser.

9. Reopen the Web browser and log in.

Verifying reboot progressTo check the reboot process.

1. Click Start > Run to open the Run dialog box.

2. Type command and press Enter to open an MS-DOS window.

3. Type arp -d 192.11.13.6 and press Enter to clear the ARP cache in the laptop. This command responds with one of the following responses:

● The command line prompt when the cache is cleared.

● The following message is when the specified IP address does not currently contain an entry in the ARP cache:



The specified entry was not found.4. Type ping -t 192.11.13.6 to access the server. The -t causes the ping to repeat until

you get a response. When you get a response, in about 3 minutes, wait an additional 30 seconds before you go back to the Web interface.

5. Type ctrl c to stop the ping.

6. Close the MS-DOS window.

Note:Note: The upgrade is now finished.

Verifying software operation To verify the software version.

1. Under Server, click Software Version.

2. Look in the Communication Manager reports as field to verify that the new software is present.

Checking system statusTo check the system status:

1. Under Server, click Status Summary to verify that the server mode is active.

2. Click Process Status.

3. Select Summary and Display once. Click View to access the View Process Status Results screen.

4. Verify that all the processes are UP.

Upgrade tasks

Issue 1 May 2009 93

Installing security and Communication Managerservice pack updates, if any

1. Under Server Upgrades, select Manage Updates.

2. If an update file you want to activate shows packed in the Status column, select update ID and click Unpack.

The window shows the status of the update.

3. Wait until the system displays the message Finished unpacking...and click Continue.

The system displays the Manage Updates screen.

4. If the update ID you want to activate shows unpacked in the Status column, select the update ID and click Activate.

The window shows the status of activating the update. If a reboot is required, the system automatically reboots.

5. Click Yes.

Wait until the system displays the Continue button.

6. Click Continue.

Creating a customer login, if necessary



If an SUSER (super-user) login did not exist prior to the upgrade, you must create a customer login before you install the authentication file.

Note:Note: Make sure the customer can change this login, its password, or its permissions

later.

Note:Note: A craft level login can create the super-user login in Release 4.0 or later.

1. Ask a customer representative for a login name and password that the customer would like for the superuser login. If you are a business partner, you can also repeat this procedure to add the dadmin login.

2. In the Communication Manager System Management Interface, under Administration > Server (Maintenance) > Security, select Administrator Accounts.

3. Select Add Login.

4. Select Privileged Administrator and click Submit.The Administrator Accounts -- Add Login: Privileged Administrator screen appears.

5. In the Login name field: Type a login name for the account.

6. In the Primary group field: susers appears.

7. In the Additional groups (profile) field: prof18 appears (prof18 is the code for the customer superuser).

8. In the Linux shell field: /bin/bash appears

9. In the Home directory field: /var/home/login name appears (login name is the name you choose in step 4.

10. Skip the Lock this account and Date on which account is disabled-blank to ignore fields.

11. In the Select type of authentication section: Choose Password.

Note:Note: Do not lock the account or set the password to be disabled.

12. In the Enter key or password field and the Re-enter key or password field: Enter the password.

13. In the Force password/key change on next login section: Leave the radio button set to the no default.

14. Click Submit.

Upgrade tasks

Issue 1 May 2009 95

Installing the RFA license file and authentication file

Note:Note: You must install the RFA license file on the server before you install the

authentication file.

To install the RFA license file and authentication file on the server:

Note:Note: The servers are currently on different releases of Communication Manager.

Therefore, the system reports an error when you install the license file.

1. Under Security, click License File.

2. Select Install the license I previously downloaded and click Submit to install the license file.

3. Under Security, click Authentication File.

4. Click Install the Authentication file I previously downloaded and click Install.

Copying IP telephone firmware to the server, if necessaryIf, before the upgrade, the server served as an http server for IP telephone firmware, download the most recent IP telephone firmware bundle from the Avaya Firmware Download Web site. The firmware bundle reinstates the 46xx IP Telephone Web page in Communication Manager and also makes the 46xx IP Telephone firmware for the tftp or http server capability of the server.

Note:Note: The IP telephone firmware that was originally downloaded is overwritten.

1. On the System Management Interface (formerly known as Maintenance Web Interface), under Miscellaneous, select Download Files.

2. Select File(s) to download from the machine I’m using to connect to the server.3. Click Browse next to the top field to open the Choose File window on your computer. Find

the files that you need to copy to the server.

4. Click Install this file on the local server.



5. Click Download to copy the file(s) to the server.

The files are copied automatically to the /tftpboot directory. The 46xx IP Telephone Web page is reinstated at the next reboot.

Making the upgrade permanent on the server

! CAUTION:CAUTION: You must make the upgrade permanent. Otherwise, the next time that you reboot

the server, the server might come up running the previous version of software. You might lose any new translations you might have made, and you must install the new software again. If you do not make the upgrade permanent within 2 hours of the upgrade, an alarm is raised.

To make the upgrade permanent.

1. Under Server Upgrades, click Make Upgrade Permanent.2. Click Submit to make the partition with the new software version the permanent partition.

3. Under Server Upgrades, click Boot Partition to confirm that the new software release is selected for the boot partition and the active partition.

Post-Upgrade tasks

Issue 1 May 2009 97

Post-Upgrade tasksNote:

Note: Use the SAT commands on the active server for Checking for translation corruption on page 79.

Accessing the server command line interface with ssh protocol

Note:Note: Using the ssh protocol to access the server is applicable to Communication

Manager Release 3.0 and later.

To use this procedure with a laptop cable connection to the services port, you must configure your laptop for the network connection. In addition, a third-party ssh client must already be installed on your computer.

For more information on Network Configuration, see Converting Avaya Servers and Media Gateways, 03-602884.

PuTTY is one such client available for download from http://www.putty.nl/download.html. The following procedure describes, as an example of ssh access, how to log into the server command line with PuTTY.

Note:Note: A version of PuTTY that is defaulted for ssh server access is available for Avaya

services personnel only. In this version, some values below have already been pre-selected.

! CAUTION:CAUTION: While a variety of Avaya products support access using ssh, Avaya does not

provide support for third-party clients used for ssh access. Any problems with an ssh client, including PuTTY, are the responsibility of the user or the ssh client vendor.

To access the command line interface using PuTTY with ssh:

1. On your computer, click on the PuTTY desktop link or select Start > Programs > PuTTY > PuTTY.

2. In the Host Name (or IP address) field, type 192.11.13.6 if connecting to the services port. Otherwise, for access over the LAN/WAN, type the IP address or the host name of the server.

3. In the Port field, type 22 (the SAT is 5022).

4. Under Protocol, select SSH.




5. In the PuTTY menu on the left, click Connection > SSH.

The Options controlling SSH connections dialog box opens.

6. In the Preferred SSH protocol version field, select 2.

7. In the Encryption options window, use the up and down arrows to set AES (SSH-2) as the top option and 3DES as the second option.

Note:Note: You can save the PuTTY settings and customize the PuTTY tool with other

settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html.

8. In the PuTTY menu on the left, click Terminal > Keyboard.

The Options controlling the effects of keys dialog box opens.

9. In the Backspace key area, select Control-H.

This activates the backspace key while you are using the SAT.

10. Click Open.

Note:Note: If you have not connected to this particular server before, ssh prompts you to

accept the server host key. If you save this key when prompted, you will not be prompted if you connect again later. If you do not save the key, PuTTY prompts you the next time you connect to this server.

When connecting through the Services laptop interface on the server, if you save the host key, the host will be identified as 192.11.13.6. If you later connect to a different server through its laptop interface, this new host also appears as 192.11.13.6, but it will have a different key. You get a prompt in this case because it appears that the host key has changed.

11. If necessary, click Yes to accept the server’s host key.

12. Log in to the server.

Enabling scheduled maintenance with SAT (main only)To enable scheduled maintenance.

1. Type change system-parameters maintenance and press Enter.

http://www.putty.nl/docs.html


Post-Upgrade tasks

Issue 1 May 2009 99

2. Ensure that the administration for the Start Time and Stop Time fields is the same as before the upgrade.

Busying out previously busied-out trunks● If you recorded any busyouts earlier on the main server only, you must ensure that they

also are busied out after the migration.


1. On the SAT, type newterm and press Enter. 2. If you see the following message:

Warning: Translation corruption detected . . .then follow the normal escalation procedure for translation corruption before continuing the upgrade.









2. Select the data sets, including Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. An ESS server or an LSP gets translatiaons from the main server, so there is no reason to back up the translations on an ESS server or an LSP. Do not select Full Backup because this option does not save translations.



3. Select the backup method.


Releasing alarm suppression (optional) If you complete the upgrade well before the time set when you suppressed alarming, you might want to release alarm suppression manually rather than wait for the system to release alarm suppression.

To release alarm suppression:

1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6.


3. Type almsuppress -s n and press Enter to release alarm suppression.

4. Log off.

Post-Upgrade tasks

Issue 1 May 2009 101

Logging off all administration applicationsWhen you complete all the administration, log off all the applications that you used.

Registering Communication ManagerFollow standard procedures to register the new software.




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

Use these procedures to upgrade Communication Manager on an S8500B, S8500C, or S8510 Server running Communication Manager Release 2.x, 3.x, 4.x, 5.x to Communication Manager Release 5.2. This procedure, except as noted later in this module, apply to an S8500-Series main server, an S8500-Series Enterprise Survivable Server (ESS), or an S8500-Series Local Survivable Processor (LSP). This procedure uses the Manage Software link on the System Management Interface (formerly known as Maintenance Web Interface). For more information, see 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.








Upgrading Communication Manager on Avaya S8500-Series Server MAIN/ESS/LSP from R2.x/R3.x/R4.x/


! Important:Important: S8500A servers cannot upgrade to Communication Manager 5.x or later

releases. You must migrate from the S8500A Server to an S8500C server to run Communication Manager 5.x.

Note:Note: Upgrades of S8500-Series Servers to Release 5.x are not connection or call

preserving.

! Important:Important: An upgrade from Release 2.x to Release 5.x or later requires that you install a

preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 5.x. For more information on which service pack to use, see Upgrading LSPs and media gateways, if any on page 105.

Note:Note: An upgrade to Release 5.x requires an updated RFA license file. For more

information on generating a license file, see RFA license and authentication files on page 38.

! Important:Important: You cannot upgrade manual backup servers (MBS). If you have one or more

MBSs, you can migrate the servers to an ESS server. For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).

PrerequisitesBefore you go onsite, you must complete the tasks in the Checklist of tasks to perform before you go on site on page 36.

The need to restore IP telephone firmware files If S8500-Series Server is used for IP telephone firmware downloads, the IP telephone firmware files must be reinstalled to the server after the upgrade. The system might use files in the /tftpboot directory for the http or tftp capability for 4600-series IP telephone firmware downloads and configuration updates. If so, the firmware and 4600-series telephone configuration file are overwritten during the upgrade.

The 46xx firmware is contained within a 46xx .tar file, in a name format similar to the filename 46xxH323_cm2_2_wi1_15_ipt2_2_111405.tar. You must retrieve the firmware file from the

Prerequisites


Avaya Downloads Web site and download the 46xx firmware file to the server after the upgrade. The upgrade to R5.x preserves the /tftpboot/46xxsettings.txt file through the upgrade.

For more information on copying and installing the IP telephone firmware files to the server, see Copying IP telephone firmware to the server, if necessary (main servers only) on page 135.

TN2312AP/BP IPSI circuit pack upgradesThe TN2312AP/BP IP Server Interface (IPSI) circuit packs must have the most recent release of the firmware before you upgrade Communication Manager on the server. Upgrade the IPSI firmware first. For firmware upgrade procedures, see Upgrading firmware on the IPSIs and SIPIs on page 213.

Upgrading LSPs and media gateways, if any


tasks and go to Accessing the active server’s web interface on page 162:








Upgrade Communication Manager on the LSPs and ESS servers, if any

For more information on S8300 LSP upgrades, see

- Installing and Upgrading the Avaya S8300 Server, 555-234-100.




For more information on the ESS server upgrade, see 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 on page 103.

Note:Note: An LSP does not accept translations if it is running a version of Communication

Manager that is older than that of the primary controller. However, the LSP remains registered with the primary controller.



Stopping and starting LSPs

Before you upgrade the S8500-Series Servers, you might want to stop call processing on the LSPs. With call processing stopped, the media gateway and the IP telephones can quickly reregister with the primary controller after the upgrade.

If you stop call processing on the LSPs, you must restart call processing on the LSPs when the primary controller upgrade is complete. In addition, if the upgrade has problems so that service from the server is lost, all telephones go out of service. This loss of service includes telephones assigned to backup service on the LSPs.

If you do not stop call processing on the LSPs, all telephones have service during the time that the LSPs are controlling calls. Service continues even a problem exists with the upgrade of the primary controller. If you do not stop call processing on the LSPs, the IP telephones usually register to the appropriate LSP during the server upgrade. When the LSP passes control back to the primary controller, IP telephones subsequently reregister with the primary controller.

Upgrading the LSPs

For more information on S8300 LSP upgrades, see Installing and Upgrading the Avaya S8300 Server, 555-234-100.

● Chapter 4: Upgrading Communication Manager on an existing S8300B or S8300C

● Chapter 6: Manual upgrade of an existing S8300B or S8300C to R5.2

● Chapter 7: Migrating an S8300 Server

Note:Note: You cannot use Upgrade Tool or Avaya Installation Wizard for the upgrade


Prerequisites


Upgrading firmware on media gateways and media modulesFor more information on the firmware upgrade process, see:





Upgrade of Communication Manager on the ESS servers The upgrade of an S8700-Series ESS is very similar to the upgrade of an S8700-Series main server. Use the instruction in this document at, Upgrading media gateways, LSPs and ESS servers, if being used on page 142.

Note:Note: An ESS server does not accept translations if it is running a version of

Communication Manager that is older than that of the primary controller. However, an ESS server remains registered with the primary controller even with an older version of Communication Manager.



Stopping and starting ESS server

As with LSPs, you have the same option of stopping and starting ESS servers to prevent IP telephone registrations with the ESS server during a server upgrade. For more information, see Stopping call processing on the LSPs or ESS servers if being used (main server only) on

page 108.



Preupgrade tasksTo install a DIMM in an S8500B Server, go to Installing a DIMM in an S8500B Server on page 114.

Connecting to the serverPerform one of the following options:

● If you are on site, connect to the services port.

● If you are off site, use the IP address of the server to log on to the server.

Upgrading the SAMP firmwareBefore you upgrade the S8500B, S8500C, or S510 Server, upgrade the firmware on the Avaya Server Availability Management Processor (SAMP) card. Check the Downloads section athttp://support.avaya.com for the most recent firmware available for the S8500-Series Servers and SAMP.

For more information, see Using the Avaya Server Availability Management Processor (SAMP), 03-300322.

Stopping call processing on the LSPs or ESS serversif being used (main server only)

To stop Communication Manager on an LSP or an ESS server:

1. Connect to the services port on the back of the main server (primary controller).

2. Access the command line interface of the server using telnet and an IP address of 192.11.13.6.

3. Within this telnet session, type telnet IPaddress and press Enter, where IPaddress is the IP address of the S8300/S8500 LSP or S8500/S8700-series ESS server.

Note:Note: Use ssh if telnet service is not available.

The login prompt for the LSP or ESS server appears.

4. Log in to the LSP or ESS server as craft.


Preupgrade tasks


5. Type stop -afcn and press Enter to stop potential call processing on the LSP or ESS server.

The LSP or ESS server shuts down Communication Manager.

6. Repeat steps 1 through 5 for each LSP or ESS server.

! CAUTION:CAUTION: After you complete the upgrade of the primary controller, run save

translations on the primary controller before you restart Communication Manager on the LSP/ESS server. The save translations process on the LSP or ESS server automatically causes the endpoints of the media gateways to reregister with the primary controller.

For more information on the S8300 LSP, see:






Note:Note: You must use SAT commands for tasks in Checking link status with SAT (main

server only) on page 109 through Checking for translation corruption with the SAT on page 111.





● Link Status = connected



● Service State = in service5. Type list signaling group and press Enter.6. Note the signaling groups that are listed by number.



Recording all busyouts (main server only)

1. Type display errors and press Enter. 2. Look for type 18 errors and record any trunks that are busied out. You can return these

trunks to the busyout state after the migration/upgrade.


correct.





Preupgrade tasks




Checking for translation corruption with the SATTo check for translation corruption:

1. Type newterm and press Enter. 2. If you see the following message


Accessing the System Management Interface (SMI)To access the server:


2. In the Address field, type 192.11.13.6 and press Enter to open the login Web page.



The system displays the Communication Manager System Management Interface (SMI).

Note:Note: For Release 5.2 use the System Management Interface (formerly known as

Maintenance Web Interface).

Note:Note: If you experience trouble connecting to the Web page, go to Clearing the Web

browser cache on the laptop on page 259.





















2. Select the server alarms that you want to clear and click Clear, or click Clear All.

Preupgrade tasks


3. Resolve or clear Communication Manager alarms with SAT commands and the Maintenance Commands Reference and Alarms Maintenance books.


1. Ask the customer to access the Login Administration SAT screen with a super-user login to verify that a super-user account exists.

Alternatively, a Business Partner may need to verify that a super-user password exists and can be used to access the server and SAT.

2. If a super-user account does not exist, you can create one after you have upgraded the software. For more information, see Creating a customer login (if necessary) on page 132.



2. Select the data sets, including Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. An ESS server or an LSP gets translatiaons from the main server, so there is no reason to back up the translations on an ESS server or an LSP. Do not select Full Backup because this option does not save translations.












Installing a DIMM in an S8500B ServerThis section describes how to install a dual inline memory module (DIMM) in the S8500B Server. You will need 1 GB of memory in order to run Communication Manager Release 4.0 or later on this server. However, before you begin, review the following:

● This server comes with one 512 MB DIMM installed in DIMM connector 1. If your server has one DIMM installed, you must install an additional 512 MB DIMM in DIMM connector 3 to increase the DRAM memory size to 1 GB.

● The installing and removing of DIMMs changes the configuration information in the server.

To install a DIMM in an S8500B Server:

! CAUTION:CAUTION: When you handle static-sensitive devices, take precautions to avoid damage

from static electricity. Use an ESD strap connected to the chassis of the S8500B frame or to an ESD mat that the server is placed on.

1. Use a PuTTY session and log in to the server.

2. From the command line, run grep MemTotal /proc/meminfo.

The system responds with the amount of memory currently residing in the server.

In the above example, the amount of memory is approximately 512 MB. The MemTotal may vary slightly from server to server.

If the total is approximately 1 GB, then this server already has sufficient memory to run Communication Manager Release 5.x.

Preupgrade tasks


3. Log off the server.

4. Use the System Management Interface (SMI) to shut down the server and peripheral devices.

! Important:Important: Avaya recommends taking a backup before the memory.

5. Disconnect the power cord and all external cables.

6. Remove the cover.

On the inside of the cover is information showing the DIMM slot locations.

! CAUTION:CAUTION: To avoid breaking the retaining clips or damaging the DIMM connectors, open

and close the clips gently.

7. Open the retaining clip on each end of the DIMM connector.

8. Touch the static-protective package containing the DIMM to any unpainted metal surface on the server.

9. Remove the DIMM from the package.

10. Align the DIMM with the connector.

! Important:Important: Because you are installing only one DIMM in the next step, this DIMM must go

into the slot 3 connector.

11. Insert the DIMM into the slot 3 connector by aligning the DIMM edges with the slots at each end of the DIMM connector.

12. Firmly press the DIMM straight down into the connector by applying pressure on both ends of the DIMM simultaneously. See Figure 6: Inserting the DIMM on page 116.



Figure 6: Inserting the DIMM

Be sure that the retaining clips snap into the locked position when the DIMM is firmly seated in the connector.

If a gap exists between the DIMM and the retaining clips, the DIMM has not been correctly installed. If this happens, open the retaining clips and remove the DIMM; then, reinsert the DIMM.

Note:Note: Before sliding the cover forward, make sure that the cover will engage the ledge

at the front of the server properly.

13. Install the cover by placing it into position and sliding it forward.

14. Tighten the captive screws.

15. Connect all external cables and the power cord to the server.

Note:Note: Do not start the upgrade procedure at this time. The remainder of this procedure

is performed using the current software on the server.

16. Plug the power cord into properly grounded electrical outlets.

17. When the server is up and running, use a PuTTY session and log in to the server.

dimmin LAO 123005

1

2

Preupgrade tasks


18. From the command line, run grep MemTotal /proc/meminfo.

The system responds with the amount of memory now residing in the server.

In the above example, the amount of memory is approximately 1 GB. The MemTotal may vary slightly from server to server. This server has sufficient memory to run Communication Manager Release 5.x.

19. Log off the server.






2. Log in as craft.



Alarm is suppressed. 120 minutes left.4. Log off and close the dialog box.



Saving a copy of the 4600-series telephone configuration file, if any

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. If the system uses the http or tftp server capability, the 4600-series IP Telephone firmware and configuration file in the /tftpboot directory are overwritten.

The 46xx firmware is contained within a 46xx .tar file, in a name format similar to the filename 46xxH323_cm2_2_wi1_15_ipt2_2_111405.tar. You must retrieve the firmware file from the Avaya Downloads Web site and download the 46xx firmware file to the server after the upgrade. However, you can save a copy of the 46xx configuration file before the upgrade and copy the file back into the /tftpboot directory after the upgrade.

You must redownload the 46xx firmware file after the upgrade. However, you can save a copy of the 46xx configuration file before the upgrade and copy the file back into the /tftpboot directory after the upgrade.

To copy the 4600-series configuration file to a safe location:


2. Log in as craft.

3. At the Linux command line, type cd /tftpboot, and press Enter.4. At the prompt, type ls 46*, and press Enter.

A named 46xxsettings.txt file appears in the list, or the prompt reappears with no files listed. If the file name does not appear, there is no file to copy. You are finished with this procedure.

5. If the file name 46xxsettings.txt appears, at the Linux command line, type cp 46xxsettings.txt ~ftp/pub.

6. The 4600-series IP Telephone settings file is now in a protected directory, /var/home/ftp/pub, and cannot be overwritten during the upgrade. Copy this file back to the /tftpboot directory after the upgrade.

Checking software release, only if starting from R2.xCheck the version of Communication Manager to ensure that you install the correct preupgrade service pack. For more information, see Upgrading LSPs and media gateways, if any on page 105.

Preupgrade tasks


Under Server, click Software Version to see what software release is on the server.

If the Reports as field is R012 (for example, R012x.00.1.221.1), you need a pre-upgrade service pack.

Activating the preupgrade service pack, only if starting from R2.x

To activate the service pack:


2. Log in as either craft or dadmin.

3. Type update_unpack and press Enter.4. Select the number that corresponds to the service pack file, such as 00.0.339.4-xxxx.tar.gz. Press Enter.

5. Type update_show and press Enter to list Communication Manager files to verify that the new service pack file was unpacked.

6. Type update_activate update, where update is the release or the issue number of the latest service pack file, such as 00.0.339.4-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter.The server might reboot. If the system reboots, the system might also display the following message:

/opt/ecs/sbin/drestart 2 4 command failed.

Ignore this message. You must wait until the restart or the reset is complete before you enter additional commands.

The server displays a message that the service pack was applied.

7. If the system displays the question, Commit this software?, enter y.

8. Type update_show again and press Enter to list Communication Manager files to verify the service pack file was activated.

9. Click on the Refresh button of the web browser to see the Manage Software link on the System Management Interface (SMI).



Upgrade tasks





Inserting the Communication Manager CD into the serverInsert the CD that contains Communication Manager into the CD-ROM drive on the server. Close the tray.

Note:Note: You can copy Communication Manager software from an http or tftp server onto

the server. In this case, skip this step.


Upgrade tasks



1. Under Server Upgrades, select Manage Software.





a. Select Delete one of the above releases from the local hard drive. Click Continue to view the releases available.





a. Select one of the following:



- Copy a release to the local hard drive, but do not install it- Copy from TFTP server at this IP address- Copy from URLand click Continue to view the options for copying the software to the hard disk.

b. Select Copy from this server’s CD-ROM drive: and click Continue.

c. The Choose Software screen appears, which you use to copy files from the source you selected.

d. Select the release to be copied and click Continue.

e. The system displays the Copy in Progress screen.

f. View the progress screen as the software is copied to the hard disk.


Successg. Click Continue to return to the initial Manage Software page.

h. Click Cancel to close the page.

Installing Communication Manager on the server






Upgrade tasks


To install Communication Manager on the server:

1. On the browser toolbar, click Refresh to reload the current page.

2. Under Server Upgrades, click Manage Software.


4. Select the software release you want, and click Continue.



5. If you have copied the license and authentication files to the server, select the following options:

- If a super-user login already existed prior to the upgrade, select:

● I will supply the license files myself when prompted later in this process.

● Update authentication information as well as license information.

- If a super-user login did not exist prior to the upgrade, select:

● I will supply the license files myself when prompted later in this process.

● Do not update authentication information.

6. Click Continue.

7. For a new installation, or if you previously ran a backup, you do not need to run a backup at this time.


8. Click Continue.

The system displays the Begin Installation window. The page summarizes the request you have made.

9. Click Continue.


The system refreshes the Install in Progress window every 10 seconds or on demand by clicking Refresh. When complete, the system displays the Reboot Server window.

Rebooting the server To reboot the server.


interface. The Reboot in Progress Web page displays during the reboot. Although the Continue button is visible, do not click Continue yet.

1. Click Reboot. The system displays the Reboot in Progress window. The tray of the CD-ROM drive opens automatically.


Upgrade tasks



again, the system might try to reboot from the software on the CD-ROM.

Note:Note: The reboot takes approximately 3 minutes. The system does not automatically

report when the reboot is complete.

Note:Note: To check the progress, see Verifying reboot progress on page 126.

3. Wait 3 minutes and then click Continue.

If you click Continue before the reboot is finished, the browser displays Expired Page. If you see the Expired Page message, refresh the browser. If the system displays Page cannot be displayed, use the browser Back button to return to the Reboot in progress screen. If the Session Timeout screen appears, close the screen, logoff, and log on again. Select Manage Software, select the option Join this upgrade session in progress and monitor its activity. Click Pickup.


message displays on the Reboot in Progress window.


upgrade of the server. After the reboot, you can continue to use the Manage Software window without logging in.

4. When the reboot is complete, click Continue.

The system displays the Update Tripwire Database Web page. If your planning documents instruct you to enable Tripwire, follow the instructions to reset the signature database.


5. Click Continue.

The system displays the Install License Files Web page.

6. Click Continue.

The system installs the license file and authentication file if you selected this action in step 5 on Installing Communication Manager on the server on page 122.

The system displays the Installation Complete screen.

7. Click Close.




Note:Note: This Web session will be interrupted by the reboot that occurs during the server

upgrade. After the reboot, the links in the main menu of the Web interface will not function. Therefore, you must close and reopen the Web browser to continue with the upgrade procedure.
















Upgrade tasks










To make the upgrade permanent.


3. Under Server Upgrades, click Boot Partition to confirm that the new software release is selected for the boot partition and the active partition.



Installing security and Communication Managerservice pack updates, if any


2. If an update file you want to activate shows packed in the Status column, select update ID and click Unpack.

The window shows the status of the update.

3. Wait until the system displays the message Finished unpacking...and click Continue.


4. If the update ID you want to activate shows unpacked in the Status column, select the update ID and click Activate.

The window shows the status of activating the update. If a reboot is required, the system automatically reboots.

5. Click Yes.


6. Click Continue.

Upgrade tasks






























10. Click Open.






Configuring the ESS or LSP for compatibility with an XL configuration

This section applies only to an ESS or an LSP. If the main server is not or will not be an S8720 in XL configuration or an S8730, proceed to Checking system status on page 127. If the memory configuration of the ESS or LSP already matches the memory configuration of the MAIN, proceed to Checking system status on page 127. An upgrade of Communication Manager software does not change the memory configuration.

If the main servers are configured as S8720 in XL configuration or if the main server is an S8730, all ESS servers (except for an S8730 ESS server) and LSPs must be configured as XL. An S8730 ESS is automatically set as XL at the time of server installation and does not have to be re-configured.

If the main server is an S8720 XL or an S8730 Server, the ESS servers must either be an S8500-Series Server, an S8720 Server, or an S8730 Server.



Upgrade tasks


To configure the ESS server for an XL configuration:

1. At the ESS server command line interface, type stop -acfn and press Enter to stop Communication Manager call processing.

2. On the Maintenance Web page, under Server Configuration, click Configure Server.The system displays the Review Notices screen.

3. Click Continue until you get to the Specify how you want to use this wizard screen.

! CAUTION:CAUTION: For the next step, if you select and save as Extra Large you cannot revert to

Standard. If you try to go back to Standard, server translation corruption occurs.

4. Select Configure individual services and click Continue.

5. In the left column, click:

● Configure Memory (if a main server)

● Configure ESS/Configure LSP

6. Select Extra Large and click Change.

7. Click Close Window.

8. At the server command line interface, type start -ac and press Enter to restart Communication Manager call processing.



9. At the server command line interface, type swversion and press Enter.In the Memory Config field, verify that the setting is Extra Large.






Creating a customer login (if necessary)


Make sure you have a login name and password that the customer would like for the superuser login. If you are a business partner, you can also repeat this procedure to add the dadmin login.

Use the Communication Manager System Management Interface to create a super-user login.

To create a login:


later.

1. In the Communication Manager System Management Interface, under Administration > Server (Maintenance) > Security, select Administrator Accounts.




Upgrade tasks










12. In the Force password/key change on next login section: Do not check the box.

13. Click Submit.The system tells the login is added successfully.

Installing the RFA license file and authentication file

Note:Note: You must install the RFA license file on the server before you install the

authentication file.

To install the RFA license file and authentication file on the server:









Stopping and starting ESS serversIf this an ESS server, you need to stop it and then restart it.

1. On a server command line interface, run the stop -caf command.

The system provides a display of the stop operation. This allows you to determine when the process completes.

2. On a server command line interface, run the start -ca command.

The system provides a continuous display of the start operation. This allows you to determine when the process completes.

Setting the Processor EthernetTo verify the Ethernet port settings on the server and to set the processor Ethernet port.

1. Under Server Configuration, click Configure Server. 2. Click Continue until the system displays the Specify how you want to use this wizard

Web page.3. Select Configure individual services, and click Continue.

The system displays the Review Notices screen and the Configure Individual IP Services menu on the left pane of the Web page.

4. Click the Set Identities menu option.

If the Processor Ethernet is already assigned to an interface, you are done. Click Close Window and proceed to the next task.

5. Under Assign the Processor Corporate to an Interface, select Enterprise LAN and click Continue. The system displays the Configure Interfaces Web page.

6. Click Change.

7. When the system displays Successfully configured ethernet interfaces, close the window.

Post-Upgrade tasks



Note: Use the commands on the active server for Checking for translation corruption with the SAT on page 111.

Copying IP telephone firmware to the server, if necessary(main servers only)

If, before the upgrade, the server served as an http server for IP telephone firmware, download the most recent IP telephone firmware bundle from the Avaya Firmware Download Web site. Installing the IP Telephone firmware bundle reinstates the 46xx IP Telephone Web page in Communication Manager and also makes the 46xx IP Telephone firmware for the tftp or http server capability of the server.



1. On the System Management Interface (formerly known as Maintenance Web Interface), under Miscellaneous, click Download Files.

2. Select File(s) to download from the machine I’m using to connect to the server.3. Click Browse next to the top field to open the Choose File window on your computer. Find

the files that you need to copy to the server.

4. Click Install this file on the local server.5. Click Download to copy the file(s) to the server.


Enabling scheduled maintenance with SAT (main only)To enable scheduled maintenance.

1. Type change system-parameters maintenance and press Enter.



2. Ensure that the administration for the Start Time and Stop Time fields is the same as before the upgrade.

Busying out previously busied-out trunks● If you recorded any busyouts earlier on the main server only, you must ensure that they

also are busied out after the migration.








Post-Upgrade tasks


Backing up recovery system files


2. Select the data sets, including:

● Avaya Call Processing (ACP) translations● Save ACP translations prior to backupDo not select Full Backup because this option does not save translations.


4. Click Start Backup to start the backup process.

5. Click Check Status to observe the status of the backup.






4. Log off.

Starting call processing on the LSPs and ESSs, if any(main server only)

You must restart call processing on a local survivable processor (LSP) if both of the following conditions are true:

● The server is the primary controller for an H.248 Media Gateway equipped with an LSP.



● You shut down the server before you upgraded the software.

! Important:Important: You must be connected to the LSP on which you are upgrading the software.

You must also restart call processing on any Enterprise Survivable Server (ESS) on which you stopped call processing before you upgraded software.

Perform the following administration when you connect your laptop to the primary controller (server) with SSH.


2. Type ssh IPaddress, where IPaddress is the IP address of the S8300 or S8500 LSP, or the S8500 or S8700-series ESS.


4. At the prompt type start -afcn and press Enter to restart call processing on the LSP or ESS.

5. Repeat for each LSP or ESS.

For more information, see:



- Using the Avaya Enterprise Survivable Server (ESS), 03-300428.




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

Use this procedure to upgrade Communication Manager on an S8710, S8720, or S8730 Server running Communication Manager Release 2.x, 3.x, 4.x, 5.x to Communication Manager Release 5.2. This procedure, except as noted later in this module, apply to either a S8700-Series main server or an S8700-Series Enterprise Survivable Server (ESS). This procedure uses the Manage Software link on the on the System Management Interface (formerly known as Maintenance Web Interface).

You can use this procedure to enable S8720 in XL configuration at the time of the upgrade.



This upgrade affects service.

! Important:Important: S8700 Server cannot be upgraded to Communication Manager 5.0 or later

releases. For Communication Manager 5.0 and later releases, an S8700 Server must migrate to an S8710, S8720, or S8730 Server. For more information on how to migrate the S8700-Series Servers see Migrating Avaya Servers and Media Gateways, 03-300412.

Upgrading Communication Manager on the S8700-Series main or ESS servers from R2.x/R3.x/R4.x/R5.x to






! Important:Important: An upgrade from Release 2.x to Release 5.x or later requires that you install a

preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 5.x.

! Important:Important: An upgrade from Release 2.x, 3.x, or 4.x, to Release 5.x requires an updated

RFA license file. For more information, see RFA license and authentication files on page 38.

! Important:Important: If you have a Survivable Remote EPN or Manual Backup Servers (MBS), you can

no longer use them. They cannot be upgraded to Release 5.x. However, you can migrate the MBSs to ESS servers. For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).

! 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. An S8720 running 3.1 with hardware duplication may require that you remove the DAL1 and install a DAL2 card for 5.x. For information on how to replace a DAL1 with a DAL2 card or on how to install a DAL2 card, see DAL: Removing or Installing on page 241.


Prerequisites


! Important:Important: When you upgrade a duplex ESS from an earlier release of Communication

Manager to Release 5.2 or later, the duplex ESS uses the PE Active Server IP address (IP-alias). The upgraded duplex ESS uses the PE Active Server IP address that is shared by the duplex ESS pair.

In a situation when the duplex ESS is upgraded and is running Release 5.2 or later and the main server pair is not yet upgraded and is still running release 5.1.x or prior, the main server has no concept that the duplex ESS has a PE Active Server IP Address. In this interim state, special consideration must be given to the administration for the duplex ESS.

! CAUTION:CAUTION: The licensing of the platform and port network connectivity attributes for the

S8700-Series Server can be complex. For more information, see Platform/PNC license settings for the S8700-Series Server on page 39.

PrerequisitesYou must complete several tasks before going on site and starting the upgrade. You must complete the tasks in the Checklist of tasks to perform before you go on site on page 36.

The need to restore IP telephone firmware files If S8700-Series Server is used for IP telephone firmware downloads, the IP firmware files must be reinstalled to the server after the upgrade. The system might use files in the /tftpboot directory for the http or tftp capability for 4600-series IP telephone firmware downloads and configuration updates. If so, the firmware and 4600-series telephone configuration file are overwritten during the upgrade.

The 46xx firmware is contained within a 46xx .tar file, in a name format similar to the filename 46xxH323_cm2_2_wi1_15_ipt2_2_111405.tar. You must retrieve the firmware file from the Avaya Downloads Web site and download the 46xx firmware file to the server after the upgrade. The upgrade to R5.x preserves the /tftpboot/46xxsettings.txt file through the upgrade.

For more information on copying the IP telephone firmware files to the server, see Copying IP telephone firmware to the server, if necessary (main servers only) on page 201.



TN2312AP/BP IPSI circuit pack upgradesThe TN2312AP/BP IP Server Interface (IPSI) circuit packs must have the most recent release of the firmware before you upgrade Communication Manager on the server. Upgrade the IPSI firmware first. For firmware upgrade procedures, see Upgrading firmware on the IPSIs and SIPIs on page 213.

Upgrading media gateways, LSPs and ESS servers, if being used


tasks and go to Connecting to the active server on page 149:


- ESS server







Communication Manager upgrades on the LSPs and ESS servers, if any

For more information on S8300 LSP upgrades, see:



For more information on S8500 LSP or S8500 ESS upgrades, see 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 on page 103.

Prerequisites


Note:Note: An LSP does not accept translations if it is running a version of Communication

Manager that is older than that of the primary controller. However, the LSP remains registered with the primary controller,



Stopping and starting LSPs

Before you upgrade the S8700-Series Server, you might want to stop call processing on the LSPs. This stoppage allows the media gateway and IP telephones to quickly reregister with the primary controller after the upgrade.

If you stop call processing on the LSPs, you must restart them when the primary controller upgrade is complete. In addition, the stoppage of call processing on the LSPs has the following consequences:

● During the interchange between the active and standby servers, analog and digital telephone calls are dropped.

● New calls to or from IP telephones cannot be made during the interchange.

● If the upgrade has problems so that service from both servers is lost, all telephones go out of service. This outage includes telephones assigned to backup service on the LSPs.

If you do not stop call processing on the LSPs, all telephones have service during the time the LSPs are controlling calls. This service continues if there is a problem with the upgrade of the primary controller. In addition, not stopping call processing on the LSPs has the following consequences:

● IP telephones are likely to register to the appropriate LSP during the server upgrade.

● You must reset the LSPs when the primary controller upgrade is complete to reregister the IP telephones to the primary controller.

Upgrading the LSPs

For more information on S8300 LSP upgrades, see Installing and Upgrading the Avaya S8300 Server, 555-234-100.

● Chapter 4: Upgrading Communication Manager on an existing S8300B or S8300C

● Chapter 6: Manual upgrade of an existing S8300B or S8300C to R5.2

● Chapter 7: Migrating an S8300 Server



Note:Note: You cannot use Upgrade Tool or Avaya Installation Wizard for the upgrade


Upgrading firmware on media gateways and media modulesFor more information on the firmware upgrade process, see:



For more information on the G250 Media Gateway, see Installing and Upgrading the Avaya G250 Media Gateway for CM 3.1 (03-300434).

For more information on the IG550 Integrated Gateway, see Installing and Configuring the Avaya IG550 Integrated Gateway, 03-601554.



Upgrade of Communication Manager on the ESS servers The upgrade of an S8700-Series ESS is very similar to the upgrade of an S8700-Series main server. Use the instruction in this document at, Upgrading media gateways, LSPs and ESS servers, if being used on page 142.

Note:Note: An ESS server does not accept translations if it is running a version of

Communication Manager that is older than that of the primary controller. However, an ESS server remains registered with the primary controller even with an older version of Communication Manager.



Verifying the status of ESS servers


Duplex ESS upgrade workflow

! CAUTION:CAUTION: Do not attempt to use this abbreviated workflow as the procedure. To perform the

upgrade on the duplicated ESS, use the procedures from Verifying the status of ESS servers on page 145 through Registering Communication Manager on page 209.

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.


After you upgrade ALL the ESS and LSP servers in the system, upgrade the main server(s):

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.


Verifying the status of ESS serversAn ESS server could assume control of one or more port networks at any time. Therefore, it is important that you verify the status of an ESS server before you start the upgrade.



1. On the SAT of the ESS server that you are going to upgrade, run the status ess port-network command.

The system displays the status ess port-network page showing the state of all the port networks known to the server on which the command is run as shown in the following example.

Figure 7: status ess port-networks

If the ESS server is not in control of a port network, the Port Ntwk Ste (port network state) column displays down. If an up displays in the Port Ntwk Ste column, stop the upgrade and identify why the ESS server is controlling that port network. Do not start the upgrade until the Port Netwk Ste column displays down for all port networks.

For more information on the status ess port-network page, see Maintenance Commands for Avaya Aura™ Communication Manager, Media Gateways and Servers (03-300431).

Preupgrade tasks


Preupgrade tasksThis section describes the preupgrade tasks required to upgrade an S8700-Series Server running Communication Manager Release 1.x, 2.x, 3.x, or 4.x of Communication Manager.

Stopping call processing on the LSPs or ESS serversif being used (main server only)

To stop Communication Manager on an LSP or an ESS server:

1. Connect to the services port on the back of the main server (primary controller).

2. Access the command line interface of the server using telnet and an IP address of 192.11.13.6.

3. Within this telnet session, type telnet IPaddress and press Enter, where IPaddress is the IP address of the S8300/S8500 LSP or S8500/S8700-series ESS server.

Note:Note: Use ssh if telnet service is not available.

The login prompt for the LSP or ESS server appears.

4. Log in to the LSP or ESS server as craft.5. Type stop -afcn and press Enter to stop potential call processing on the LSP or ESS

server.

The LSP or ESS server shuts down Communication Manager.

6. Repeat steps 1 through 5 for each LSP or ESS server.

! CAUTION:CAUTION: After you complete the upgrade of the primary controller, run save

translations on the primary controller before you restart Communication Manager on the LSP/ESS server. The save translations process on the LSP or ESS server automatically causes the endpoints of the media gateways to reregister with the primary controller.

For more information on the S8300 LSP, see:





Clearing the ARP cache on the laptopTo clear the ARP cache:

Note:Note: Depending on the operating system on your laptop computer (that usually is

Windows 2000XP), you might need to clear the Address Resolution Protocol (ARP) cache before entering a new IP address. If you enter an IP address, and your computer cannot connect, you might need to clear the cache.

1. On your laptop computer, click Start > Run to open the Run dialog box.

2. Type command. Press Enter to open a MS-DOS Command Line window.

3. Type arp -d 192.11.13.6. Press Enter to clear the Address Resolution Protocol (ARP) cache in the laptop. This command responds with one of the following:


● The phrase: The specified entry was not found.

This phrase is returned when the specified IP address does not currently appear in the ARP cache.

Clearing the Web browser cache on the laptopDue to underlying changes on Communication Manager Web pages, you might experience problems with accessing some of the pages. For example, you might see some strange behavior when using the same laptop/PC to switch in-between Communication Manager loads or releases, especially when accessing the Communication Manager server(s) through the Services port (http://192.11.13.6). This is due to how your web browser is caching information and it does not always know what is new and what is old.

For example, for Communication Manager Release 3.1 and earlier, you log into https://192.11.13.6 and it takes you to https://192.11.13.6/log-in.

But if you are in Communication Manager Release 5.x and you log into https://192.11.13.6, it takes you to https://192.11.13.6/log-in/web-page (or something similar).

The problem is that the laptop gets confused after it has been at Release 5.x and then you want to go to another site in pre Release 5.x. The system cannot find the old login page.

This happens only if you are switching between releases and/or loads - especially if you go backwards in releases (for example, from Release 5.x on Server 1 to Release 3.0 on Server 2). There does not seem to be a problem going forward in releases.

Clearing the Web browser cache on the laptop


If you are experiencing problems logging in to Web pages:

1. On the Internet Explorer page, select Tools > Internet Options.

2. In the Temporary Internet files section, click Delete Cookies.

3. Click OK.

4. In the Temporary Internet files section, click Delete files.

5. Click OK.

6. In the History section, click History.

7. Click OK.

Connecting to the active serverIf you are on site, connect to the services port on the back of the active server.














Note:Note: You must use SAT commands on the active server to complete these tasks.





● Link Status = connected● Service State = in service

5. Type list signaling group and press Enter.6. Note the signaling groups that are listed by number.



Recording all busyouts (main server only)

1. Type display errors and press Enter.



2. Look for type 18 errors and record any trunks that are busied out. You can return these trunks to the busyout state after the migration/upgrade.


correct.







Busying out MMI circuit packs with SAT for a duplicated controlnetwork only (main server only)

! CAUTION:CAUTION: Multimedia-to-voice station calls are not preserved on an upgrade. If you do not

busyout the TN787 Multimedia Interface (MMI) circuit packs, the TN787 and TN787 Multimedia Voice Conditioner ports cannot be used.

To locate all the MMI circuit packs that need to be busied out:

1. Type display system-parameters customer-options and press Enter.



2. Under the Multimedia Call Handling (MMCH) options, select Basic and Enhanced fields.

3. If either the Basic or Enhanced field is set to y, type list configuration all. Press Enter to locate all MMI (TN787) circuit packs.

4. If MMI circuit packs exist, type busyout board UUCSS where UU is the cabinet, C is the carrier, and SS is the slot.

5. Press Enter for each MMI circuit pack.
































2. Select the server alarms that you want to clear and click Clear, or click Clear All.



3. Resolve or clear Communication Manager alarms with SAT commands and the Maintenance Commands Reference and Alarms Maintenance books.


1. Ask the customer to access the Login Administration SAT screen with a super-user login to verify that a super-user login exists.

Alternatively, a Business Partner may need to verify that a super-user account exists and can be used to access the server and the SAT.

2. If a super-user account does not exist, you can create one after you have upgraded the software.

See Creating a super-user login on page 180.

Backing up recovery system files on the active serverTo back up the system configuration files on the active server:


2. Select the data sets, including:

● Avaya Call Processing (ACP) translations, select Save ACP translations prior to backup

● Server and System Files● Security FilesDo not select Full Backup because this option does not save translations.















2. Log in as craft.




Disconnecting from the active serverTo disconnect from the active server:

● Unplug the laptop computer from the services port on the back of the active server.



Connecting to the standby server If you are on site, connect to the services port on the back of the standby server.

If you are off site, log on to the standby server with the actual IP address of the standby server.





Clearing the ARP cache on the laptop computerYou might need to clear the Address Resolution Protocol (ARP) cache before you enter a new IP address. This need depends on the operating system on your laptop computer. If you enter an IP address and your computer cannot connect, you might need to clear the cache.

To clear the ARP cache on the laptop:


2. To open an MS-DOS command line window, type command. Press Enter.3. Type arp -d 192.11.13.6. Press Enter. This command produces one of the following

responses:

● The command line prompt displays when the cache is cleared.

● The message The specified entry was not found appears when the specified IP address does not currently appear in the ARP cache.



Clearing the Web browser cache on the laptopDue to underlying changes on Communication Manager Web pages, you might experience problems with accessing some of the pages. For example, you might see some strange behavior when using the same laptop/PC to switch in-between Communication Manager loads or releases, especially when accessing the Communication Manager server(s) through the Services port (http://192.11.13.6). This is due to how your web browser is caching information and it does not always know what is new and what is old.

For example, for Communication Manager Release 3.1 and earlier, you log into https://192.11.13.6 and it takes you to https://192.11.13.6/log-in.

But if you are in Communication Manager Release 5.x and you log into https://192.11.13.6, it takes you to https://192.11.13.6/log-in/web-page (or something similar).

The problem is that the laptop gets confused after it has been at Release 5.x and then you want to go to another site in pre Release 5.x. The system cannot find the old login page.

This happens only if you are switching between releases and/or loads - especially if you go backwards in releases (for example, from Release 5.x on Server 1 to Release 3.0 on Server 2). There does not seem to be a problem going forward in releases.

If you are experiencing problems logging in to Web pages:

1. On the Internet Explorer page, select Tools > Internet Options.

2. In the Temporary Internet files section, click Delete Cookies.

3. Click OK.

4. In the Temporary Internet files section, click Delete files.

5. Click OK.

6. In the History section, click History.

7. Click OK.

Backing up files on the standby serverTo back up the system configuration files on the standby server:


2. Select the data sets, including Avaya Call Processing (ACP) translations.




! Important:Important: Do not select Full Backup or Save ACP translations prior to backup because

you cannot save translations on a standby server.

4. Click Start Backup to start the back up process. Wait until the backup is complete.

Verifying the backup on the standby serverTo verify that the backup was successful on the standby server:





Suppressing alarming on the standby server



To suppress alarming on the standby server:


2. Log in as craft.






Disconnecting from the standby serverDisconnect the laptop from the services port on the back of the standby server.

Removing a DAL1 or installing a DAL2 cardA DAL2 card is required in the following scenarios:

● S8710: Anytime an S8710 Server is running Communication Manager Release 5.x or later.

● S8720: For all S8720 Servers using hardware duplication.

● S8730: For all S8730 Servers using hardware duplication.

You can physically verify the type of DAL card that is installed in the server by looking at the label printed on the DAL card.

You can also verify the DAL card type using the following command:

1. From the command line, run cat /proc/mdd.

If the system responds with The card memory is 256 MB, you currently have a DAL1 card installed in the server.


Note:Note: The system responds with ’This DAL-1 card STANDBY’ as an output of the cat

/proc/mdd command on a pre-5.0 Communication Manager release. This output should be ignored if a DAL2 card has been installed in preparation for the Release 5.0 upgrade. In Release 5.0 and later, the output of the cat /proc/mdd command reports the DAL2 when the DAL2 card is installed.

If you currently have a DAL2 card installed or if you do not need a DAL2 card to complete the upgrade, proceed with Connecting to the active server on page 161.

If you must replace a DAL1 with a DAL2 card, or install a DAL2, see DAL: Removing or Installing on page 241. Once you have replaced or installed the DAL card, return to Placing or Replacing the server in the rack on page 160 to continue the upgrade.



Placing or Replacing the server in the rack

! DANGER:DANGER: The Avaya server weighs 47-60 pounds (20-27 kg). Do not replace the server in

the rack by yourself.

To replace the server in the rack:

1. Be sure that the rails are extended and locked into place as shown in the following figure.

Figure 8: Replacing the server in the rack

2. Align the server on the rails and push the server into the rack until it is flush with the rack (Note 1).

3. Push the two locking levers down to secure the server in the rack (Note 2).

Figure notes:

1. Place server on rails, slide into place 2. Lock both tabs securely

h3df87ri LAO 101905

UID

2

1

01

10

disc

COMPACT

54

54

Sim

ple

xD

up

lex

ch

ch

21

32

32

1

2



4. Replace all cable connections to the front and back panels of the server.

Restoring power to the serverTo restore power to the server:

1. Apply power to the server by plugging the power cable into the socket on the back of the server.

Verify that the DAL2 card is installed correctly1. Connect to the server.


The system responds with

The card memory is 512 MB if it sees the DAL2 card installed in the server.

! CAUTION:CAUTION: If the cat /proc/mdd command is performed on a pre 5.0 Communication

Manager release, the command displays "This DAL-1 card STANDBY". The output should be ignored if a DAL-2 card has been installed in preparation for the 5.0 upgrade. In release 5.0 and later, the output of cat /proc/mdd reports the DAL-2 card.

Disconnecting from the standby serverDisconnect the laptop from the services port on the back of the server.

Connecting to the active serverTo connect to the active server:

1. Connect to the service’s port on the back of the active server.



Accessing the active server’s web interfaceTo access the active server:





The system displays the Communication Manager System Management Interface (SMI) Web page.

Note:Note: If you experience problems connecting to the Web page, go to Clearing the Web

browser cache on the laptop on page 148 and return here.

Selecting the Preupgrade Step

Note:Note: If you are upgrading from a pre-Release 4.x to Release 5.x, calls are not

preserved during the interchange.



1. Under Server Upgrade, click Pre Upgrade Step.

The system displays the Pre Upgrade Step screen.

2. On the Pre Upgrade Step screen, to start the preupgrade step, click Continue.

The system shows the status of the preupgrade step operations and synchronizes translations between servers.

If you need to stop the upgrade process, click Undo.

Disconnecting from the active serverTo disconnect from the active server:

● Unplug the laptop computer from the services port on the back of the active server.



Upgrade tasks for the first serverPerform the tasks in this section to upgrade the first server.

Connecting to the standby server To connect to the standby server:

● Connect to the services port on the back of the standby server.

Clearing the ARP cache on the laptopTo clear the ARP cache:

Note:Note: Depending on the operating system on your laptop computer (that usually is

Windows 2000XP), you might need to clear the Address Resolution Protocol (ARP) cache before entering a new IP address. If you enter an IP address, and your computer cannot connect, you might need to clear the cache.

1. On your laptop computer, click Start > Run to open the Run dialog box.

2. Type command. Press Enter to open a MS-DOS Command Line window.

3. Type arp -d 192.11.13.6. Press Enter to clear the Address Resolution Protocol (ARP) cache in the laptop. This command responds with one of the following:


● The phrase: The specified entry was not found.

This phrase is returned when the specified IP address does not currently appear in the ARP cache.

Upgrade tasks for the first server


Checking the software release on the standby serverCheck the version of Communication Manager to determine if you need a pre-upgrade service pack.



Activating the preupgrade service pack on the standby server(R2.x only)

To activate the service pack:













9. If your Web browsers are open, refresh the screen.

Inserting the Communication Manager CD-ROM into the standbyserver

To insert the CD-ROM into the standby server:

1. Insert the CD-ROM that contains Communication Manager into the CD-ROM drive on the standby server.

2. Close the tray.

















a. Select Delete one of the above releases from the local hard drive.





a. Select Copy a release to the local hard drive, but do not install it and click Continue.

b. Select Copy from this server’s CD-ROM drive and click Continue.



c. Select the release to be copied and click Continue.

When complete, the system displays the Copy Complete screen.

d. Click Continue to return to the Choose Task screen.

Upgrading Communication Manager on the server





To upgrade Communication Manager on the standby server:



3. Select the software release.

4. Check Force continue, if necessary, and click Continue.

5. Select the following options:

Note:Note: Make these selections even though a license file and authentication file will be

installed after the server is upgraded and after this server becomes the active server.

- I want to reuse the license files from the currently active partition on this server.




- Do not update authentication information.6. Click Continue.

7. Click Continue.

The system displays the Begin Installation screen. The page summarizes the request you have made.

8. Click Continue.


The Install in Progress screen refreshes every 10 seconds or on demand by clicking Refresh. When complete, the system displays the Reboot Server screen.

Rebooting the standby server To reboot the standby server.

Note:Note: When you reboot the standby server, it can no longer communicate with the Web

interface. The Reboot in Progress Web page displays during the reboot. Although the Continue button is visible, do not click Continue yet.

1. Click Reboot. The system displays the Reboot in Progress screen. The tray of the CD-ROM drive opens automatically.

2. Remove the CD from the CD-ROM drive.

! CAUTION:CAUTION: If you do not remove the CD and the tray of the CD-ROM drive closes again, the

system might reboot from the software on the CD.

Note:Note: The reboot can take approximately 3 minutes. The system does not automatically


To check the reboot progress, see Verifying reboot progress on page 170.


If you click Continue before the reboot is finished, the browser displays Expired Page. If you see the Expired Page message, refresh the browser. If the system displays Page cannot be displayed, use the browser Back button to return to the Reboot in Progress screen. If the Session Timeout screen appears, close the screen, logoff, and log on again. Select Manage Software, select the option Join this upgrade session in progress and monitor its activity. Click Pickup.




message appears on the Reboot in Progress screen.




The system displays the Update Tripwire Database Web page. If your planning documents instruct you to enable Tripwire, follow the instructions to reset the signature database.



6. Click Close.






9. Go to Suppressing alarms on page 171.













Suppressing alarmsTo suppress alarms:

1. Close all Web browser windows related to the current server.



4. Log in as craft.5. Select yes to suppress alarms.




2. Look in the Reports as field to verify that the new software is present.



Performing an integrity check on the first S8700-Series ServerTo perform an integrity check on the first S8700-Series Server:

1. On the System Management Interface (formerly known as Maintenance Web Interface), under Administration > Server (Maintenance) > Server, click Process Status.

2. Under Frequency, click Display Once and click View.

3. Verify all operations are UP STANDBY.





3. Under Server Upgrades, click Boot Partition to confirm that the new software release is Yes for Boot Partition and Yes for Active Partition.

Installing security and service pack updates, if anyUse this procedure to unpack and active the files that you copied in the previous step.


2. If an update file you want to activate shows packed in the Status column:

a. Select update IDb. Click Unpack



3. Wait until the system displays the message Unpacked Successfully.. and then click Continue.


4. If the update ID you want to activate shows unpacked in the Status column:

a. Select the update IDb. Click Activate

The screen shows the status of activating the update. If a reboot or restart of Communication Manager is required, the system automatically reboots or restarts Communication Manager.

5. Click Yes.


6. Click Continue.

The system displays the status of the update.

Configuring the Processor Ethernet interface (on the ESS)Perform this task if you are upgrading the server from Communication Manager Release 5.1.x or prior to Communication Manager 5.2 or later.

1. Under Installation, click Configure Server and follow the instructions on the wizard. Alternatively, you can configure services individually. For more information, see the online help available with the SMI.

2. On the Set Identities page, verify that PE is assigned to the same NIC as the corporate LAN.

3. On the Configure Interfaces page, assign an IP-alias address for the PE interface of the duplex ESS. PE must be assigned to the same NIC as the corporate LAN. The IP-alias address is assigned in the Active server field.

4. Submit the change and exit from the Configure Server wizard.

































10. Click Open.






XL configuration considerations

Note:Note: If you are upgrading an S8720 main server, proceed to Configuring the main

server for S8720 in XL configuration on page 175.

If you are upgrading an S8720 ESS server, proceed to Configuring the main server for S8720 in XL configuration on page 175.

Skip this section in the system, if any of the following is true:

- The system including MAIN (primary controllers) is already configured as XL

- The primary controllers are S8720 and will not be configured as XL

Configuring the main server for S8720 in XL configuration

This section applies only to a main server configured for an XL. If you are not enabling the server as an XL configuration, skip this section and proceed to Performing an integrity check on the first S8700-Series Server on page 172.

Note:Note: If the main servers are configured as an XL configuration, ESSs and LSPs also

must be configured to be compatible with the main server.



To configure the main server as an XL configuration:

1. At the server command line interface, type stop -acfn and press Enter to stop Communication Manager call processing.

2. On the Maintenance Web page, under Server Configuration, click Configure Server.3. Click Continue until you get to the Specify how you want to use this wizard screen.








● Configure ESS (if an ESS server)





Configuring the ESS server for compatibility with XL configuration

This section applies only to an ESS server where the main server is configured as an XL. If the main server is not configured as XL, skip this section and proceed to Performing an integrity check on the first S8700-Series Server on page 172.

Note:Note: If the main servers are configured as XL, the ESS servers and LSPs also must be

configured to be compatible with the XL configuration. An S8720 Server can be configured as standard or XL. An S8730 Server is always configured as XL.

To configure the ESS server for compatibility with the main server’s XL configuration:









5. In the left column, click Configure ESS (if an ESS server)







Performing an integrity check on the first S8700-Series ServerTo perform an integrity check on the first S8700-Series Server:



3. Verify all operations are Up.

Releasing the standby serverTo release the server from busyout mode, if necessary:

1. Under Server, click Release Server.2. On the Release Server window, click Release.

3. To verify that the standby server is not busied out, click Status Summary.

Interchanging the serversTo interchange the active and standby servers:

Note:Note: Interchanging the servers does not preserve calls. The Communication Manager

reset is equivalent to a reset system 4.x.

1. Select Status Summary, and check that the Server Hardware and Processes fields say okay.

Note:Note: At this point, the servers are on different software loads. Therefore, for servers

upgrading from Communication Manager prerelease 4.0 and earlier, Standby Refreshed is no and Standby Shadowing is off.

2. Under Server, click Interchange Servers.

3. Check Force interchange regardless of server status and click Interchange.



4. To verify that the server you are connected to is the active server, click Status Summary.

Performing an integrity check on the first S8700-Series ServerTo perform an integrity check on the first (active) S8700-Series Server:




Creating a super-user login


Make sure you have a login name and password that the customer would like for the superuser login. If you are a business partner, you can also repeat this procedure to add the dadmin login.

Use the Communication Manager System Management Interface (SMI) to create a super-user login.

To create a login:


later.

1. In the Communication Manager System Management Interface (SMI), under Security, select Administrator Accounts.














12. In the Force password/key change on next login section: Do not check the box.

13. Click Submit.The system tells the login is added successfully.

Installing the new license and Avaya authentication files on newlyactive server

Note:Note: You must install the license file on an active server and before you install the

Avaya authentication file. If the license is installed on the active server while the standby server is on the previous release or older software, the error message Filesync of new license to standby server failed, rc=0, result=10 appears.

To install the new license and authentication files on the newly active server:









Stopping and starting the ESS serversIf this an ESS server, you must stop the Communication Manager process and then restart it after installing the license file. Doing this ensures that the new RFA license takes full effect.

1. On a server command line interface, run the stop -caf command.

The system provides a continuos display of the stop operation. This allows you to determine when the process completes.

2. On a server command line interface, run the start -ca command.

The system provides a continuous display of the start operation. This allows you to determine when the process completes.

Disconnecting from the newly active serverIf you are on site, unplug the laptop computer from the services port on the back of the newly active server.

Upgrade tasks for the new standby server (second server)



Removing a DAL1 or installing a DAL2 cardA DAL2 card is required in the following scenarios:

● S8710: Anytime an S8710 Server is running Communication Manager Release 5.x or later.

● S8720: For hardware duplication in an Extra Large (XL) configuration prior to Communication Manager 5.0 and for all S8720 Server with hardware duplication running 5.0 and later releases.

● S8730: The DAL2 card is required for S8730 Servers using hardware duplication.

To verify which DAL card is currently installed in the server:






If you currently have a DAL2 card installed or if you do not need a DAL2 card to complete the upgrade, proceed with Connecting to the standby server on page 156.

If you must replace a DAL1 with a DAL2 card, or install a DAL2 card, see DAL: Removing or Installing on page 241. Once you have replaced or installed the DAL card, return to Placing or Replacing the server in the rack on page 184 to continue this upgrade.



Placing or Replacing the server in the rack

! DANGER:DANGER: The Avaya server weighs 47-60 pounds (20-27 kg). Do not replace the server in

the rack by yourself.

To replace the server in the rack:

1. Be sure that the rails are extended and locked into place as shown in the following figure.

Figure 9: Replacing the server in the rack

2. Align the server on the rails and push the server into the rack until it is flush with the rack (Note 1).

3. Push the two locking levers down to secure the server in the rack (Note 2).

Figure notes:

1. Place server on rails, slide into place 2. Lock both tabs securely

h3df87ri LAO 101905

UID

2

1

01

10

disc

COMPACT

54

54

Sim

ple

xD

up

lex

ch

ch

21

32

32

1

2



4. Replace all cable connections to the front and back panels of the server.

Restoring power to the serverTo restore power to the server:

1. Apply power to the server by plugging the power cable into the socket on the back of the server.

Verify that the DAL2 card is installed correctly1. Connect to the server.


The system responds with

The card memory is 512 MB if it sees the DAL2 card installed in the server.

! CAUTION:CAUTION: If the cat /proc/mdd command is performed on a pre 5.0 Communication

Manager release, the command displays "This DAL-1 card STANDBY". The output should be ignored if a DAL-2 card has been installed in preparation for the 5.0 upgrade. In release 5.0 and later, the output of cat /proc/mdd reports the DAL-2 card.

Disconnecting from the serverDisconnect the laptop from the services port on the back of the server.









Accessing the standby server’s maintenance interfaceTo access the standby server:


2. In the address field, type 192.11.13.6 and press Enter.3. Log in as craft or dadmin.

4. Click yes to suppress alarms.


Checking the software release on the standby serverCheck the version of Communication Manager to determine if you need a pre-upgrade service pack.



Activating the preupgrade service pack on the server (R2.x only)To activate the service pack:













9. If your Web browsers are open, refresh the screen.

Inserting the Communication Manager CD into the serverInsert the CD that contains Communication Manager into the CD-ROM drive on the server. Close the tray.












a. Select Delete one of the above releases from the local hard drive.





a. Select Copy a release to the local hard drive, but do not install it and click Continue.

b. Select Copy from this server’s CD-ROM drive and click Continue.

c. Select the release to be copied and click Continue.

When complete, the system displays the Copy Complete screen.

d. Click Continue to return to the Choose Task screen.



Upgrading Communication Manager on the server





To upgrade Communication Manager on the standby server:



3. Select the software release.

4. Check Force continue, if necessary, and click Continue.

5. Select the following options:

Note:Note: Make these selections even though a license file and authentication file will be

installed after the server is upgraded and after this server becomes the active server.

- I want to reuse the license files from the currently active partition on this server. - Do not update authentication information.

6. Click Continue.

7. Click Continue.

The system displays the Begin Installation screen. The page summarizes the request you have made.




8. Click Continue.


The Install in Progress screen refreshes every 10 seconds or on demand by clicking Refresh. When complete, the system displays the Reboot Server screen.

Rebooting the server


interface. The Reboot in Progress window remains on your screen until the reboot is complete. Although the Continue button is visible, do not click Continue yet.

To reboot the server.

1. Click Reboot. The system displays the Reboot in Progress Web page. The tray of the CD-ROM drive opens automatically.



again, the system might reboot from the software on the CD-ROM.

Note:Note: The reboot can take approximately 3 minutes. The system does not automatically


To check the reboot progress, see Verifying reboot progress on page 170.


If you click Continue before the reboot is finished, the browser displays Expired Page. If you see the Expired Page message, refresh the browser. If the system displays Page cannot be displayed, use the browser Back button to return to the Reboot in Progress screen. If the Session Timeout screen appears, close the screen, logoff, and log on again. Select Manage Software, select the option Join this upgrade session in progress and monitor its activity. Click Pickup.




message displays on the Reboot in Progress window.




The system displays the Update Tripwire Database screen. If your planning documents instruct you to enable Tripwire, follow the instructions to reset the signature database.



6. Click Close.












The specified entry was not found.



4. Type ping -t 192.11.13.6 to access the server. The -t causes the ping to repeat until you get a response. When you get a response, in about 3 minutes, wait an additional 30 seconds before you go back to the Web interface.



Suppressing alarmsTo suppress alarms:

1. Close all Web browser windows related to the current server.



4. Log in as craft.5. Select yes to suppress alarms.







Performing an integrity check on the second S8700-Series ServerTo perform an integrity check on the second S8700-Series Server:



3. Verify all operations are UP.





3. Under Server Upgrades, click Boot Partition to confirm that the new software release is Yes for Boot Partition and Yes for Active Partition.

Installing security and service pack updates, if anyUse this procedure to unpack and active the files that you copied in the previous step.


2. If an update file you want to activate shows packed in the Status column:

a. Select update IDb. Click Unpack



3. Wait until the system displays the message Unpacked Successfully.. and then click Continue.


4. If the update ID you want to activate shows unpacked in the Status column:

a. Select the update IDb. Click Activate

The screen shows the status of activating the update. If a reboot or restart of Communication Manager is required, the system automatically reboots or restarts Communication Manager.

5. Click Yes.


6. Click Continue.

The system displays the status of the update.

Configuring the Processor Ethernet interface (on the ESS)Perform this task if you are upgrading the server from Communication Manager Release 5.1.x or prior to Communication Manager 5.2 or later.

1. Under Installation, click Configure Server and follow the instructions on the wizard. Alternatively, you can configure services individually. For more information, see the online help available with the SMI.

2. On the Set Identities page, verify that PE is assigned to the same NIC as the corporate LAN.

3. On the Configure Interfaces page, assign an IP-alias address for the PE interface of the duplex ESS. PE must be assigned to the same NIC as the corporate LAN. The IP-alias address is assigned in the Active server field.

4. Submit the change and exit from the Configure Server wizard.

































10. Click Open.






XL configuration considerations

Note:Note: If you are upgrading an S8720XL main server, proceed to Configuring the main

server for S8720 in XL configuration on page 175.

If you are upgrading an S8720 main server, proceed to Performing an integrity check on the second S8700-Series Server on page 200.

If you are upgrading an S8720 ESS server, proceed to Configuring the ESS server for compatibility with XL configuration on page 198.

If you are upgrading an S8710 Server, proceed to Performing an integrity check on the second S8700-Series Server on page 200.

Configuring the main server for S8720 in XL configuration

This section applies only to a main server configured for an XL. If you are not enabling the server as an XL configuration, skip this section and proceed to Performing an integrity check on the first S8700-Series Server on page 172.



Note:Note: If the main servers are configured as an XL configuration, ESSs and LSPs also

must be configured to be compatible with the main server.

To configure the main server as an XL configuration:


2. On the Maintenance Web page, under Server Configuration, click Configure Server.3. Click Continue until you get to the Specify how you want to use this wizard screen.








● Configure ESS (if an ESS server)





Configuring the ESS server for compatibility with XL configuration

This section applies only to an ESS server where the main server is configured as an XL. If the main server is not configured as XL, skip this section and proceed to Performing an integrity check on the first S8700-Series Server on page 172.

Note:Note: If the main servers are configured as XL, the ESS servers and LSPs also must be

configured to be compatible with the XL configuration. An S8720 Server can be configured as standard or XL. An S8730 Server is always configured as XL.

To configure the ESS server for compatibility with the main server’s XL configuration:









5. In the left column, click Configure ESS (if an ESS server)







Performing an integrity check on the second S8700-Series ServerTo perform an integrity check on the second (standby) S8700-Series Server:




Verifying the operation of the serversTo verify the operation of the servers:

● Click View Summary Status and verify that the following fields show the values as indicated:

- Duplicated? hw or sw (depending on the configuration)

- Standby Busied? no- Standby Refreshed? yes- Standby Shadowing: on- Duplication Link: up

Setting Server A/Server 1 active for ESS, if necessarySkip this task if the servers you are upgrading are S8700-Series Servers configured as main servers.

Note:Note: Perform this task after you have upgraded a duplicated ESS server from

Communication Manager Release 5.1.x or prior to Communication Manager Release 5.2 or later; and before you upgrade the MAIN Servers from Communication Manager Release 5.1.x to Communication Manager Release 5.2 or later.

Post-Upgrade tasks


Note:Note: The term Server A refers to one of the two servers in a duplicated ESS. An ESS

that is running on Communication Manager Release 5.2 or later will register and filesync to the main server running Communication Manager Release 5.1.x or prior, only if the Server A of the ESS is active. Typically, Server A will be the Server 1 as identified in the ID field in the output of the CLI command server, or in the ID field in the output of the Server --> Status Summary screen in the SMI.

To interchange the servers, if necessary:

1. Access the System Management Interface (SMI) of the standby ESS.

2. Under Server, click Interchange Servers.3. Click Interchange

The system displays a confirmation message that the interchange has taken place. This server is now the active server.


Note: You must use SAT commands on the active server for the tasks Enabling scheduled maintenance with SAT (main server only) on page 204 through Checking for translation corruption with SAT (main server only) on page 204.

Copying IP telephone firmware to the server, if necessary(main servers only)

If, before the upgrade, the server served as an http server for IP telephone firmware, download the most recent IP telephone firmware bundle from the Avaya Firmware Download Web site. Installing the IP Telephone firmware bundle reinstates the 46xx IP Telephone Web page in Communication Manager and also makes the 46xx IP Telephone firmware for the tftp or http server capability of the server.



1. On the System Management Interface (formerly known as Maintenance Web Interface), under Administration > Server (Maintenance) > Miscellaneous, click Download Files.





4. Click Install this file on the local server.5. Click Download to copy the file(s) to the server.


6. Repeat these steps for the other server, if applicable.

Disconnecting from the standby serverDisconnect the laptop from the services port on the back of the standby server.

Administering the node name for the IP-alias address for the duplicated ESS servers (after ESS upgrade and pre-upgrade Main)

Skip this task if the servers you are upgrading are S8700-Series Servers configured as main servers.

Note:Note: Perform this task after you have upgraded a duplicated ESS server from

Communication Manager Release 5.1.x or prior to Communication Manager Release 5.2 or later, and before you upgrade the MAIN Servers from Communication Manager Release 5.1.x to Communication Manager Release 5.2 or later.

At the SAT of the MAIN Server:

1. Type change node-names ip xxx and press Enter, where xxx is the node name of the Active Server IP Address (IP-alias) of the duplicated ESS servers.

If the node name already exists, confirm that the IP Address is correctly matching the PE Active Server IP Address (IP-alias) of the duplex ESS; press Cancel to exit the node-names screen, skip to step 5.

If the node name xxx does not exist, add a new node name, using steps 2-4.

Post-Upgrade tasks


! CAUTION:CAUTION: Choose this node name carefully. If you need to change it after the upgrade, you

must delete the ESS and readminister it. Do not delete or re-use the node name for server A because you will need this node name later, when you upgrade the main server.

2. (for new node name only) In the Name field, enter the node name.

3. (for new node name only) In the IP Address field, enter the PE Active Server IP Address of the duplex ESS.

4. (for new node name only) submit your changes to the node-names screen.

5. Type change system-parameters ess and press Enter.6. Administer the node name of Server A by the node name that you defined for the PE

interface of the duplex ESS for the ESS server that you are changing.Type save translation all and press Enter.

The ESS server registers with the main server and receives filesyncs.7. Administering the node name for Server A (main server only)

Skip this task if the servers you are upgrading are S8700-Series ESS.

Note:Note: Perform this task after you upgrade the S8700-Series main servers from

Communication Manager Release 5.1.x or prior to Communication Manager Release 5.2 or later; and if the main has administered Survivable Servers of Type “ESS D” as observed on the list survivable-processor screen.

Note:Note: The system-parameters ess screen is no longer available after the upgrade to

Communication Manager Release 5.2 or later. The translation data that was held in system-parameters ess screen is now located in the survivable-proccessor screen.

The Server A node name in the System Parameters ESS SAT screen of the pre-upgrade main is transferred to the ACTIVE SERVER IP Address field in the Survivable Processor SAT screen of the upgraded main. The SERVER A Node Name is set to blank in the Survivable Processor screen. Because the node name for Server A is blank on the Survivable Processor Screen, an alarm (ESS alarm 799) is generated on the main server.

At the SAT of the MAIN Server:

Tip:Tip: Run the list survivable-processor command and search for ESS D to

locate the servers that need administering.



1. Type change survivable-processor New-node-name and press Enter.Where New-node-name is the node name assigned to the ESS. The node name can be determined from the list survivable-processor screen.

2. Administer the node name of the ESS server A.

The alarm clears after the Server A node name is administered for the duplex ESS.

Enabling scheduled maintenance with SAT (main server only)To enable scheduled maintenance.

1. Type change system-parameters maintenance and press Enter.2. Ensure that the administration for the Start Time and Stop Time fields is the same as

before the upgrade.

Releasing MMI circuit packs in duplicated control network using SAT, (main server only)

Type release board UUCSS and press Enter to release the circuit packs that you busied out earlier. For more information, see Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 151 section.

Busying out previously busied-out trunks (main server only)● If you recorded any busyouts prior to the conversion you must ensure that they are

busied-out after the conversion.

Checking for translation corruption with SAT (main server only)To check for translation corruption:

1. Type newterm and press Enter.

Post-Upgrade tasks


2. If you see the following message:






Backing up files on the active serverTo back up the translations and system configuration files on the active server:

1. Under Data Backup/Restore, click Backup Now2. Select the data sets, including:

- Avaya Call Processing (ACP) translations, select Save ACP translations prior to backup

- Sever and System Files

- Security Files

! Important:Important: If this server is an ESS, select Do NOT save ACP translations prior to backup. If

this server is a main server, select Save ACP translations prior to backup. You may select Full Backup if a save translations was performed just prior to this backup.

3. Select the backup method









4. Log off.

Logging off all administration applications on the active server● When you have completed all the administration, log off all the applications used.

Disconnecting from the active serverIf you are on site, unplug the laptop computer from the services port on the back of the active server.




Post-Upgrade tasks





Backing up files on the standby serverTo back up the system configuration files on the standby server:


2. Select the data sets, including Avaya Call Processing (ACP) translations.


! Important:Important: Do not select Full Backup or Save ACP translations prior to backup because

you cannot save translations on a standby server.







4. Log off.



Starting call processing on the LSPs and ESSs, if anyYou must restart call processing on a local survivable processor (LSP) if both of the following conditions are true:

● The server is the primary controller for a G350 or G700 Media Gateway equipped with an LSP.

● You shut down the server before you upgraded the software.

! Important:Important: You must be connected to the LSP on which you are upgrading the software.

You must also restart call processing on any Enterprise Survivable Server (ESS) on which you stopped call processing before you upgraded software.

Perform the following administration when you connect your laptop to the primary controller (server) with SSH.


2. Type telnet IPaddress, where IPaddress is the IP address of the S8300 or S8500 LSP, or the S8500 or S8700-series ESS.


4. At the prompt type start -afcn and press Enter to restart call processing on the LSP or ESS.

5. Repeat for each LSP or ESS.

For more information, see:



- Using the Avaya Enterprise Survivable Server (ESS), 03-300428.


Post-Upgrade tasks





Prerequisites


Chapter 3: Upgrading Firmware on TN circuit packsand Ethernet switches

Several pieces of equipment require firmware upgrades periodically. This equipment includes the TN2312AP/BP IP Server Interface (IPSI) and TN8412AP S8400 IP Interface (SIPI) programable circuit packs, the TN799DP, TN2302AP, and TN2602AP circuit packs, and the Avaya Ethernet switches C-363T and C-364T.

The programmable circuit packs must be on the most current version, particularly the TN2312AP/BP and TN8412AP circuit packs. Many features available with Communication Manager Release 3.1 cannot be activated unless the circuit packs are on the most current version.

Firmware for these products are available from the Avaya Support Web site (http://avaya.com/support).

! CAUTION:CAUTION: If you are a customer administrator, you might be required to access the

Download Center Web site in order to download firmware. For instructions on setting up access to the Download Center, access http://support.avaya.com and click on the appropriate links.

PrerequisitesYou must complete several tasks before going on site and starting the upgrade. For presite tasks, see Checklist of tasks to perform before you go on site on page 36 in Chapter 2: Upgrading Software on Servers on page 33.

Upgrade modulesThe following modules are contained in this chapter:

● Upgrading firmware on the IPSIs and SIPIs on page 213

● Upgrading firmware on TN circuit packs on page 223

● Upgrading firmware on the Avaya Ethernet Switch on page 225




Upgrading Firmware on TN circuit packs and Ethernet switches



Upgrading firmware on the IPSIs and SIPIs

On occasion new firmware becomes available for the Internet Protocol Server Interface (IPSI) circuit packs (TN2312AP/BP) and S8400 IP Interface (SIPI) circuit packs (TN8412AP). Both types of circuit pack must have the most current firmware before the upgrading the software on the Avaya server.

! Important:Important: All information that follows applies to the TN8412AP as well as the TN2312AP/

BP circuit packs.

Note:Note: You can download firmware for a TN2312BP to a TN2312AP IPSI circuit pack,

though environmental maintenance is unavailable on the TN2312AP.

You can download firmware to one or more TN2312BP IPSI circuit pack from either the active or the standby server. The process only requires IP connectivity to the IPSIs, which both servers have.

After the firmware download completes and the IPSI resets, the IPSI automatically activates the new firmware. This activation occurs regardless of how the IPSI reset was started. The IPSI can be initiated as a scheduled event, by demand, or spontaneously by system software. You can schedule the firmware activation with the Activate IPSI Upgrade screen. However, the new firmware might activate earlier if the IPSI is reset for other reasons.

! CAUTION:CAUTION: Ensure that you want to upgrade the IPSI firmware before you start the

download. Once you have successfully downloaded the new firmware into an IPSI, you cannot cancel the upgrade.






PrerequisitesBefore starting the upgrade procedure, you need several items.

Ensure that you have the following prerequisites:

● Superuser or services login and password

● A computer with the following items:

- IP connectivity to the server

- IP connectivity to the World-Wide Web

- MS Internet Explorer 5.5 or 6.0

● The latest IPSI firmware, which is available at the Avaya Support Web site (http://avaya.com/support). Click Downloads and select your product. The product can include the S8500-Series Servers, S8700, S8710, or S8720 Server.

To find out the firmware that is currently on the IPSIs, see Determining current IPSI firmware on page 215.

Access the Web InterfaceAccess the System Management Interface (formerly known as Maintenance Web Interface) with the following steps.

1. If on site, connect to the services port on the back of the server.

If off site log in to the server using the IP address of the server.


3. If connected directly to the server, type 192.11.13.6 in the Address field to bring up the logon Web page.

If connected through the network, type in the host name or IP address of the server.


5. When asked whether to suppress alarms, click yes.



Prerequisites


Determining current IPSI firmwareThe following steps determine the firmware version on each IPSI.

1. Under IPSI Firmware Upgrades click IPSI Version and select Query All to see the firmware version of each IPSI circuit pack.

The output looks something like this:

The last column shows the firmware version.

2. Print the page.

3. Determine which IPSIs need new firmware.

IP address IPSI Name IPSI Board HW# FW#

135.9.77.28 ipsi-A01e TN2312 32 7



Upgrade Tasks

Pre-Upgrade tasks

Access the Web Interface

Access the System Management Interface (formerly known as Maintenance Web Interface) with the following steps.

Note:Note: If duplicated servers, you must connect to the active server.

1. If on site, connect to the services port, default 2 [Eth1], on the back of the server.

If off site log in to the server using the IP address of the server.


3. If connected directly to the server, type 192.11.13.6 in the Address field to bring up the logon Web page.

If connected through the network, type in the host name or IP address of the server.


5. When asked whether to suppress alarms, click yes.









Upgrade Tasks










Determining active IPSIs (duplicated control network only)

Note:Note: With a duplicated control network, you must download new firmware to an active

IPSI. However, whenever possible, activate the new firmware to a standby IPSI.

The following step displays all the IPSIs.

1. Type list ipserver-interface and press Enter to determine which IPSIs in port networks are active.

2. Print the page, which shows the board locations (Bd Loc) and which IPSIs are active or standby (Control State) or write down the information.

Busying out standby IPSIs (duplicated control network only)

The following steps busyout the standby IPSIs.

1. Type busyout ipserver-interface standbyIPSI, where standbyIPSI is an IPSI in standby mode and press Enter to busy the standby IPSI out.

2. Repeat for each IPSI circuit pack in standby mode.



Upgrade tasks

Downloading firmware to IPSI

! CAUTION:CAUTION: These steps do not disrupt call service unless a reset, such as power failure, of

the active IPSI occurs. A reset activates the new firmware image and might disrupt call service. To avoid that possibility, perform these steps during a low traffic period. Or, if duplicated IPSIs, perform these steps on the standby IPSIs only, interchange the IPSIs. Then perform the same steps on the remainder of the IPSIs.

The following steps download the firmware to each or all IPSIs.

1. Under IPSI Firmware Upgrades, click Download IPSI Firmware.

Upgrade Tasks


2. Select the time when you want the firmware download to start. You can do it immediately or schedule a time.

! CAUTION:CAUTION: Select All IPSIs only if the server is shut down during an upgrade or on a new

installation. Never select All IPSIs if duplicated IPSIs.

3. Select either an individual IPSI or All IPSIs by providing its cabinet number and carrier location.

4. Select the file to download.

5. Click Download Firmware to download the firmware to all IPSIs or an individual one.

6. If you have more than one IPSI to upgrade, repeat for each IPSI.



! Important:Important: The firmware download is first stored in RAM on the IPSI. After the entire

download file is successfully sent to the IPSI, the IPSI burns the firmware image into ROM. The firmware download is not permanent until the image is completely burned into ROM. If for any reason the download process is interrupted, you must start the download again. Examples of download interruptions include a break in the network connection, a failure of the IPSI, or power loss to the IPSI.

7. Click Download Status to view

● Scheduled firmware downloads

● History and status of previous downloads.

8. If necessary, cancel scheduled downloads from this screen. If you cancel, you cancel all the scheduled downloads, not just an individual one, unless you are only downloading to one IPSI.

Activating the new firmware

! CAUTION:CAUTION: Firmware activation causes a brief service interruption in a single control network

configuration in which the IPSIs are not duplicated. Schedule the activation for off hours.

! CAUTION:CAUTION: If a duplicated control network, schedule the activation for the IPSIs in a

busied-out, standby mode only.

Once the firmware is downloaded to the IPSI, you must activate it. The new firmware might activate earlier if the IPSIs are reset for other reasons. When you manually reset the IPSIs, the command resets the IPSIs one at a time. When the activation time for a particular IPSI arrives, it is reset even if it is busy handling calls.

1. Click Activate IPSI Upgrade.

2. Select either All IPSIs, if non-duplicated control network, or an individual IPSI by providing its cabinet number and carrier location.

3. Select the time when you want to start activating the firmware. You can do it immediately or schedule a time.

4. Select the time when you want to stop the activation. If the activations have not completed by the stop time, they will stop, and you must activate them at another time.

5. Click Activate IPSI Upgrade to start the activation or the clock for the activation schedule.

6. Click Activation Status to view

● Scheduled firmware resets

● History and status of the resets

Upgrade Tasks


7. If necessary, cancel the resets from this screen.

Cancellation affects only the IPSIs that have not yet been reset. The information on this screen applies only to resets started from this screen. This screen does not include the status for resets started through the Communication Manager or from other events such as board removal or power loss. Canceling the resets means some IPSIs have newer firmware than others.

Releasing standby IPSIs (duplicated control network only)

Note:Note: The following steps are done with SAT commands.

The following steps release the IPSIs from busyout mode.

1. Type release ipserver-interface busyIPSI, where busyIPSI is a busied-out IPSI and press Enter to release the IPSI.

2. Repeat for each busied-out IPSI circuit pack.

Verifying the health of the IPSIs

Note:Note: The following steps are done with SAT commands.

The following steps verify the health of the standby IPSIs.

1. Type list ipserver-interface and press Enter. Ensure that each standby IPSI has a State of Health of 0.0.0.

If any have something other than 0.0.0, view the active alarms.

2. Type display alarms and press Enter to resolve them before proceeding.

! CAUTION:CAUTION: If an IPSI has health problems, you should not interchange to that IPSI.

Interchanging to an unhealthy IPSI can bring down all the calls on that port network.

Interchanging the IPSIs (duplicated control network only)

The following steps interchange the IPSIs.

1. Type set ipserver-interface location, where location is the location of the standby IPSI to set the standby IPSI as the new active IPSI. This command forces an interchange from the active to the standby IPSI.



2. Type list ipserver-interface again to ensure that the new active IPSI is still healthy. The State of Health field must still be 0.0.0.

All the IPSIs must now be interchanged so that the newly active IPSIs are running the new version of firmware. The newly standby IPSIs are still running the old version.

3. Repeat the steps from Busying out standby IPSIs (duplicated control network only) on page 217 through Verifying the health of the IPSIs on page 221 for each new standby IPSI.

Post-upgrade tasks

Verifying IPSI firmware version

The following steps list all the IPSIs and their firmware version.

1. Under IPSI Firmware Upgrades click IPSI Version and select Query All to verify that the IPSI circuit packs have the required firmware version.


Upgrading firmware on TN circuit packs

TN circuit packs require firmware upgrades periodically. You can download new firmware to specific, programmable circuit packs. Programmable circuit packs have a “P” in their suffix. For example TN799DP is programmable, but TN799C is not. This programmable capability reduces the need to physically remove circuit packs and return them to Avaya for firmware updates.

In addition, with Communication Manager R3.1 and higher, you can use a central firmware despository on an SCP-enabled file server to update one or all of your non-self-downloadable circuit packs and the following versions of self-downloadable circuit packs:

● TN799DP Control-LAN (C-LAN) circuit pack, firmware version 17 or higher

● TN2602AP IP Media Resource 320, firmware version 20 or higher

● TN2501 VAL circuit pack, firmware version 10 or higher

Finally, with Communication Manager R3.1 and higher, you can use the Software Update Manager to download firmware to TN circuit packs.

To access the procedures for upgrading the firmware on these circuit packs, go to

ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/firmware/TNpackFirmwareDownloadInstructions.pdf



ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/firmware/TNpackFirmwareDownloadInstructions.pdf


Upgrading firmware on TN circuit packs



Upgrading firmware on the Avaya Ethernet Switch

On occasion you might need to upgrade the firmware on the Avaya Ethernet switch. New firmware is available at Avaya Support (http://avaya.com/support). Click Downloads, select the name of the Ethernet switch that you have, then select the firmware for your particular model.



Information on how to upgrade the firmware is in the following documents available on the Avaya Support Web site:

You must be connected directly to the Avaya Ethernet switch to upgrade the firmware. You cannot upgrade the firmware through the server.

C-360 series Installation and Configuration for the Avaya C360 Converged Stackable Switches, Software Version 4.5, "Updating the Firmware"

P333T Avaya P333T User Guide for Version 4.0, "Upgrading the Software"

P3334T Avaya P3334T User Guide for Version 4.0, "Upgrading the Software"

P3332MF Avaya P332MF User Guide for Version 4.0, "Upgrading the Software"

P333R Avaya P333R User Guide for Version 4.0, "Upgrading the Software"

P333R-LB Avaya P333R-LB Version 3.11 User Guide, "Upgrading the Software"

P332G-ML Avaya P332G-ML User Guide for version 4.5, "Upgrading the Software"

P332GT-M Avaya P332GT-ML User Guide for version 4.5, "Upgrading the Software"

P334T-ML Avaya P334T-ML User Guide for version 4.5, "Upgrading the Software"



Upgrading firmware on the Avaya Ethernet Switch



Appendix A: Accessing the server

You must have access to the server for administration. The following computers and software are the supported access points for accessing the server for initial configuration, aftermarket additions, and continuing maintenance:

● Personal computers.

● Services laptop computers equipped with a network interface card (NIC).

● Terminal emulation program.

● Web browser.

You can access the server either directly or remotely over the customer network or over a modem. Connecting directly and remotely over the customer network are the preferred methods. Remote access over a modem is for Avaya maintenance access only.

Connecting to the server directly To access the server directly, plug a laptop computer into the services port on the server.

● On the S8300 Server plug the CAT5 cable into the services port on the front as shown in Figure 10: A services laptop computer that is connected directly to the S8300 Server on page 228.

● On the S8500-Series Servers, as shown in Figure 11: A services laptop computer that is connected directly to S8500-Series Servers on page 229, for S8500B Server

● The S8700-Series Server, plug one end of a crossconnect CAT5 cable into the services port. This port defaults to port 2 (Eth1), On the back of the server, plug the other end into the NIC on your computer. You might need a NIC adapter.

For more information about connectivity for your server, see

● Figure 10: A services laptop computer that is connected directly to the S8300 Server on page 228

● Figure 11: A services laptop computer that is connected directly to S8500-Series Servers on page 229

● Figure 12: A services laptop computer that is connected directly to the S8710 Server or S8720 Server (S8710 Server shown) on page 230.

● Figure 13: A services laptop computer that is connected directly to the S8730 Server on page 231



Figure 10: A services laptop computer that is connected directly to the S8300 Server

Figure notes:

1. Services laptop2. Network interface card (NIC)

3. NIC adapter cable (if necessary)4. Black CAT5 cross-connect cable

Connecting to the server directly


Figure 11: A services laptop computer that is connected directly to S8500-Series Servers

Figure notes:

1. Services laptop2. Network interface card (NIC)

3. NIC adapter cable (if necessary)4. Black CAT5 cross-connect cable

2

1

cadlsrv3 KLC 093004

1

2

3

4

2



Figure 12: A services laptop computer that is connected directly to the S8710 Server or S8720 Server (S8710 Server shown)

Figure notes:

1. Services laptop2. Network Interface Card (NIC)

3. NIC adapter cable (if necessary)4. Black CAT5 crossconnect cable

2

3

iLO

VDCI

1

2

3

133 MGz

100 MGz

100 MGz

UID

2 1

DA

L1D

UP

ME

MO

RY

RE

CE

IVE

MO

DE

LIN

CS

YN

C

TR

AN

SM

OD

E

LIN

CA

CT

IVE

cadlsrv2 KLC 042804

1

2

3

4

2 1

Computer specifications


Figure 13: A services laptop computer that is connected directly to the S8730 Server

Computer specificationsThe computer that you use to access the server must have the following minimum specifications:

● Windows 2000 or Windows XP operating system

● 32-MB of RAM

Figure notes:

1. Services laptop2. Network Interface Card (NIC)

3. NIC adapter cable (if necessary)4. Black CAT5 crossconnect cable

DA

L1D

UP

ME

MO

RY

RE

CE

IVE

MO

DE

LIN

CS

YN

C

TR

AN

SM

OD

E

LIN

CA

CT

IVE

1

2

UIDILO 2PCIe 1PCIe 2

3

4

5

ca873srv LAO 081507

1

2

3

1

2

4



● 40-MB of available disk space

● A Network interface card (NIC) with a 10/100BaseT Ethernet interface

● A 10/100 BaseT Ethernet, CAT5 or better, cross-connect cable with an RJ45 connector on each end (MDI to MDI-X)

● CD-ROM drive

Network configurationYou also must configure your network connection. For more information, see Network configuration on page 238.

The network connection for the computer has the following TCP/IP properties:

● IP address: 192.11.13.5

● Subnet mask: 255.255.255.252

After you connect the computer to the network, you can administer the server through these interfaces:

● The System Management Interface (SMI) for server-specific administration.

● A command line interface in a Telnet or terminal emulation application for Linux and SAT commands, respectively. For duplicated servers, you can use the SAT commands on the active server only.

For more information, see Accessing the System Management Interface (SMI) on page 235.


use the System Management Interface (SMI).

Connecting to the server remotely over the network


Connecting to the server remotely over the network You can access the server from any computer that is connected through the LAN. However, the LAN security settings must allow remote access.

To access the server, open a Web browser or a terminal emulation application. In the address field, type the IP address or the DNS host name that is assigned to the server you want to access.

For duplicated servers, you can use the active (alias) server address to connect automatically to the server that is active.

Connecting to the server remotely over a modem Note:

Note: Remote access over a modem is for Avaya services support access only and not for routine administration. Because the server uses the same line to report alarms, the server cannot report new alarms while the line is in use.

You can access the server through an analog modem. The remote connection requires a data speed of at least 33.5 kilobits per second.

On the S8500-Series Server, you access the server through the analog modem that is connected to the remote maintenance board that is installed in the server. For more information about how to access the SAMP, see the Using the Avaya Server Availability Management Processor (SAMP) (03-300322).

Setting up a dial-up connectionTo use a computer modem, you first must set up your dial-up connection.

1. Start the dial-up connection program, which varies depending on your operating system. Usually, you can access a dial-up connection program from the My Computer or the Control Panel folders. For more information, see the Help system on your computer.

2. To open the New Connection wizard, double-click Make New Connection.

3. Within the wizard, and depending on your operating system, you might be asked to:

● Assign a name to the connection.

● Select dial-up to the network for the network connection type.

● Select the modem that you use for a dial-up connection.



● Type the appropriate telephone number to access the active server. For more information about the customer-supplied telephone numbers, see the completed Electronic Preinstallation Worksheet.

● Under Advanced, select PPP and log on manually. You might have to type a user name and a password. This entry depends on whether the server you are dialing into has a non-null CHAP secret key. If you must type a user name and a password, use craft as the user name and ignore the Password field.

Dialing up to the serverTo dial up, click the connection name or the icon, if you created an icon when you set up the connection. Once you are connected:

1. When prompted, enter your remote access login name and password.

2. When you see the Start PPP now! message, click Done. When you see the Connection Complete dialog box, your computer is connected to the server.

3. To open an SSH session, see Using the command line interface on page 236.

Finding the IP address of the active server (duplicated servers)To find the IP address of the active server in a configuration with duplicated servers:

1. Go to the task bar at the bottom right of your PC screen.

2. Right-click the Network Status icon. Click Status, and then click the Details tab.

3. Scroll down until you see the Server IP address. This IP address is for the server to which you are connected.

Disabling the boot timeout of the SAMP board

Note:Note: You can also disable the boot timeout of the SAMP board by connecting to the

SAMP services port and using the SAMP’s Web pages. For more information, see "Disabling the boot timeout on Release 3.1 using the SAMP Web page" in the Using the Avaya Server Availability Management Processor (SAMP), 03-300322.

Accessing the System Management Interface (SMI)


To disable the boot timeout of the SAMP:

1. At the command line on the S8500-Series Servers, enter sampcmd.

The Welcome banner appears, followed by the SAMP command line.

2. At the SAMP command line, enter serverctrl boot timer disable.

The system responds with OK.

3. At the SAMP command line, enter serverctrl.The system responds with the following output:

4. Enter Exit to return to the server command line.

When you have completed the upgrade and the server reboots, the SAMP boot timeout is automatically enabled again.

Accessing the System Management Interface (SMI) To access the System Management Interface. You can either connect:

● Directly to the services port on the server. For more information, see Connecting to the server directly on page 227.

● Over the customer network.

MS Internet Explorer 5.5 or 6.0 is the only browser that is supported.

When you connect directly to the server, you must disable all proxy servers. For more information and instructions, see Browser settings on page 240.

To access the System Management Interface (SMI):

1. Open the MS Internet Explorer Web browser.


● If you want to connect directly, in the Address field, type 192.11.13.6.

● If you want to connect remotely, in the Address field, type the IP address or the DNS host name of the server.

3. When prompted, log in.

Power OnServer OperationalReset DeassertedBoot Time Disabled




use the System Management Interface (SMI).

Using the command line interface















Using the command line interface














10. Click Open.






Accessing the command line interface with terminal emulation

To use a command line interface in a terminal emulation window:

Note:Note: Avaya Native Configuration Manager, Avaya Terminal Emulation, and

HyperTerminal are the only supported terminal emulation programs.

1. Open your terminal emulation application.





2. Ensure that the port settings of the terminal emulation program are configured as follows:

● 115200 baud

● No parity

● 8 data bits

● 1 stop bit

● No flow control

3. Establish a network connection to the server with either the IP address or the DNS host name. Use port 5023 for this connection.

4. When prompted, log in.

LoginsInitial configuration and upgrades by an Avaya technical support representative or an Avaya Business Partner requires a services login, such as craft or dadmin. Avaya technical support representatives can also use a unique password that is assigned to that customer system.

When you finish installing the Avaya authentication file, Communication Manager has a password for the craft login. This password is unique to the server of the customer. You can use the password the next time that you log in as craft, if you access the server through the Services port. Every other means of craft access still requires an ASG challenge/response. RFA records the revised password. ASG Interactive Response provides this password at 1-800-248-1234 or 1-720-444-5557.

Customers can set up their own logins to access Avaya servers. For more information, see the Administering Avaya Aura™ Communication Manager (03-300509). You must have superuser permission to create or change logins and passwords.

! Important:Important: When you assign login IDs, do not start the logins with a number.

Network configuration! Important:

Important: Record any IP addresses, DNS servers, or WINS entries that you change when you configure your services computer. You must restore these entries to connect to other networks.

Network configuration


To configure a new network connection:

Note:Note: These instructions are for Windows 2000 and Windows XP only.

1. On your computer desktop, right-click My Network Places and left-click Properties to display the Network Connections window.

Windows 2000 and Windows XP automatically detects the Ethernet card in your system and creates a LAN connection for you. More than one connection might occur.

2. Right-click the correct Local Area Connection and left-click Properties to display the Local Area Connection Properties dialog box.

3. Select Internet Protocol (TCP/IP).4. Click Properties to display the Internet Protocol (TCP/IP) Properties dialog box.

5. On the General tab, select Use the following IP address. Enter the following addresses:

● IP address: 192.11.13.5

● Subnet mask: 255.255.255.252

6. Record any IP addresses or other entries that you must clear. You might need to restore these later to connect to another network.

7. Select Use the following DNS server addresses. Leave the entries for Preferred DNS server and Alternate DNS server blank.

8. At the bottom of the dialog box, click Advanced to display the Advanced TCP/IP Settings dialog box.

9. Click the DNS tab. Ensure that no DNS server is administered. The address field is blank.

10. Click OK > OK > Close to close all the windows.

11. Reboot the system if directed to do so.

After you make these changes to the network configuration for your computer, the Network and Dial-up Connections window shows the status of the Local Area Connection. The system displays:

- Enabled when the Ethernet cable from the laptop is connected to the server.

- Disabled or unplugged when the NIC is not connected to any other equipment.



Browser settings

Connecting directly to the serverTo set the browser for a direct connection to the server:

Note:Note: Instructions are for Internet Explorer 6.0 only.

1. Click Tools > Internet Options.

2. Click the Connection tab.

3. In the LAN Settings box in the lower righthand of the page, click Advanced.

4. In the Exceptions box after the last entry, type 192.11.13.65. Click OK > OK > OK again to close all the dialog boxes.

Connecting remotely through the networkWhen you connect through a proxy server, a connection session to a server can time out. To avoid a server time out during a session, add the host names or the IP addresses of the servers to the list of host names and IP addresses.

To add the host names or the IP addresses of the servers to the list of host names and IP addresses:

Note:Note: The following instructions are for Internet Explorer 6.0 only.

1. Click Tools > Internet Options.

2. Click the Connection tab.

3. Click LAN settings > Advanced.

4. In the Do not use proxy server for addresses beginning with field, type the IP address for each server that you want to access remotely. If the first or the first and second octets are the same, you can shorten the address to xxx.xxx.* For example, if you have the IP addresses 135.9.42.75 and 135.9.113.113, then you can type 135.9.*).

5. Click OK > OK > OK again to close all the dialog boxes.

Verifying which DAL is installed


Appendix B: DAL: Removing or Installing

Use these procedures to remove or install a DAL:

● Verifying which DAL is installed on page 241

● Removing power from the server on page 242

● Removing the server from the rack on page 242

● Removing the cover from the server on page 244

● Removing the DAL on page 245

● Installing the DAL2 in the S8710 or S8720 on page 247

● Installing the DAL2 in the S8730 Server on page 250

If this is a new server (power not on and not mounted in a rack) proceed to, Removing the cover from the server on page 244.

Verifying which DAL is installedIf the server is not powered up, you can verify which DAL card is installed in the server by physically looking at the label on the board. You can also verify the board type in software using the following steps:

1. Connect to the server.






DAL: Removing or Installing


Removing power from the serverIf the server is not powered up and installed in the rack, skip this procedure and go to Removing the cover from the server on page 244.

! CAUTION:CAUTION: Ensure that you are connected to the standby server. Proceeding with the

following steps and being connected to the incorrect server can result in service disruption.

To shut down the server:

1. Under Server, click Shutdown Server.2. Make the following selections:

● Select Delayed Shutdown● Deselect Restart Server after Shutdown

3. Click Shutdown. Wait until the server has powered down.

4. When the server is powered down, disconnect the power cord from the server.

Removing the server from the rackSkip this procedure if the server is not installed in a rack and go to Removing the cover from the server on page 244.

! DANGER:DANGER: The server weighs between 47-60 pounds (20-27 kg). Do not remove the server

from the rack by yourself.

To remove the server from the rack:

1. Label and remove all cables from the front and back panels of the server.

2. Release the two (2) locking clips on each side of the server (Note 1 in Removing the server from the rack).

Removing the server from the rack


Figure 14: Removing the server from the rack

3. Pull the server straight out of the rails.

Figure notes:

1. Release both locking clips 2. Pull server straight out to remove

h3df87rk LAO 101905

UID

2

1

01

10

disc

COMPACT

54

54

Sim

ple

xD

up

lex

ch

ch

21

32

32

1

2



Removing the cover from the serverTo remove the cover from the server:

1. Lift the latch handle on the cover of the server as shown in Figure 15.

Figure 15: Removing the cover from the server

Lifting the latch handle moves the cover locking tabs free of the front panel.

2. Lift the cover straight up and set it aside.

3. Lower the hinged access panel.

Removing the PCI riser cageTo remove the riser cage:

1. Release the two (2) thumbscrews (Note 1 in Figure 16).

Figure notes:

1. Latch handle 2. Cover slides back for removal

h3df8cvr LAO 101905

UID

2

1

01

10

disc

COMPACT

54

54

Si m

ple

xD

up

l ex

ch

ch

21

32

32

1

2

Removing the DAL


Figure 16: Removing the PCI riser cage

2. Lift the riser cage straight up and set it on the antistatic mat.

Removing the DALIf you do not have to remove the DAL circuit pack, skip to Installing the DAL2 in the S8710 or S8720 on page 247 or Installing the DAL2 in the S8730 Server on page 250.

To remove the DAL circuit pack:

Note:Note: Always wear an antistatic wrist strap when working inside the server.

1. While holding the riser assembly steady push the locking tab in (Note 1 in Figure 17) and pull the lever (Note 2) out to release the DAL circuit pack.

Figure notes:

1. Loosen both thumbscrews 2. Lift riser cage straight up

2

3

VDCI

1

2

3

133 MGz

100 MGz

100 MGz

h3df87cr LAO 102505

DAL

1D

UP

MEM

OR

Y

REC

EIVE

MO

DE

LIN

CSY

NC

TRAN

SM

OD

E

LIN

CAC

TIVE

21

1



Note:Note: Do not use any tools when performing the next step.ou

2. Using a rocking motion, carefully pull the DAL card straight out from the PCI riser cage (3).

Figure 17: Removing the DAL circuit pack

Figure notes:

1. Push the locking tab in2. Release the locking lever

3. Pull the DAL circuit pack straight out

h3dsdalr LAO 102505

DAL

1D

UP

MEM

OR

Y

REC

EIVE

MO

DE

LIN

CSY

NC

TRAN

SM

OD

E

LIN

CAC

TIVE

2

1

3

Installing the DAL2 in the S8710 or S8720


Installing the DAL2 in the S8710 or S8720To install the DAL2 cards:

1. Remove the DAL2 card from its protective packaging and set it on the antistatic mat beside the riser assembly.

2. Lock the PCI retaining clip (Note 2 in Figure 18).

3. Align the circuit pack with the connector in the PCI riser cage and push the circuit pack into the same slot as the old circuit pack (Note 3 in Figure 18).

4. Lift and turn the thumbscrew knobs clockwise while pressing down, until tightened.

5. Turn the thumbscrews counterclockwise to lower the thumbscrew knobs.



Figure 18: Installing the DAL2 card

Replacing the PCI riser cageTo replace the riser cage:

1. Align the three tabs of the riser cage with the guides on the server chassis as shown in Figure 19.

Figure notes:

1. Slide the DAL2 card into the slot in the carrier

2. Secure the card in the slot by tightening the thumbscrew

3. Close the locking lever

h3df87di LAO 110205

DA

L1D

UP

ME

MO

RY

RE

CE

IVE

MO

DE

LIN

CS

YN

C

TRA

NS

MO

DE

LIN

CAC

TIV

E

1

2

3

4

Installing the DAL2 in the S8710 or S8720


Figure 19: Replacing the PCI riser cage

2. Slide the riser cage in the slots until it rests on the base of the chassis and is aligned with the two thumbscrew holes (Note 1).

3. Tighten the two thumbscrews to secure the riser cage in place (Note 2).

Tip:Tip: To start the thumbscrew, use one hand to push the spring-loaded screw down

into the threaded hole, then turn the screw with the other hand.

4. Lift the hinged access panel up and lock it in place.

Figure notes:

1. Align tabs and insert carrier into connector

2. Tighten both thumbscrews

2

3

VDCI

1

2

3

133 MGz

100 MGz

100 MGz

h3df87ci LAO 102505

DA

L1D

UP

ME

MO

RY

RE

CE

IVE

MO

DE

LIN

CS

YN

C

TRA

NS

MO

DE

LIN

CAC

TIV

E

2

1 2



Replacing the cover on the serverTo replace the cover on the server:

1. Place the cover on the server so that the front alignment tabs are in place.

2. Push the latch handle down.

The cover slides forward and locks into place.

Installing the DAL2 in the S8730 ServerTo install the DAL2 card in the S8730 Server:

1. Lift up on the hood latch handle and remove the access panel.

Note:Note: Always wear an antistatic wrist strap when working inside the server.

2. Remove the Trox wrench from the holder (see 1 in Figure 20).

3. Insert the Trox wrench in the riser cage thumbscrews and turn them counterclockwise to loosen them (see 2 in Figure 20).

4. Remove the PCI riser cage (see 3 in Figure 20).

! Important:Important: Do not disconnect the disk drive controller cables. Leave them connected while

installing the DAL2 card.

Installing the DAL2 in the S8730 Server


Figure 20: Removing the PCI riser cage on the S8730

5. Remove the blank expansion slot cover from the PCI riser cage.

6. Remove the PCI retaining clip.

hw873ccr LAO 072407

2

1

2

PCIe 1

PCIe 23

4

5

DAL

1D

UP

MEM

OR

Y

REC

EIVE

MO

DE

LIN

CSY

NC

TRAN

SM

OD

E

LIN

CAC

TIVE

3

2

1



Figure 21: Installing the DAL2 card in an S8730

7. Carefully insert the DAL2 card into the middle slot of the PCI riser cage (1 on Figure 21).

8. Insert the PCI retaining clip back into the slot (2 on Figure 21).

9. Lock the PCI retaining clip (3 on Figure 21).

10. Align the PCI riser cage with the guides on the chassis and slide the riser cage into place.

11. While pressing down, lift and turn the thumbscrew knobs clockwise until they are tight or use the Trox wrench to tighten.

12. Turn the thumbscrews counterclockwise to lower the thumbscrew knobs.

13. Return the Trox wrench to the Trox wrench holder (1 on Figure 20).

14. Install the access cover on the server.

15. Press down on the hood latch handle to lock the access panel in place.

DAL

1D

UP

MEM

OR

Y

REC

EIVE

MO

DE

LIN

CSY

NC

TRAN

SM

OD

E

LIN

CAC

TIVE

hw873dai LAO 081507

2

1

3


Index

Index

Aalarm suppression, releasing . . . . 100, 137, 206, 207alarms

resolving . . . . . . . . . 82, 99, 112, 136, 153, 205suppressing . . . . . . 83, 117, 155, 158, 171, 192

ARP cache, clearing . . . . . . . . . . . . . 148, 164ARP cache, clearing on the laptop . . . . . . . . . 156authentication file

copying to server . . . . . . . 81, 95, 111, 135, 201

Bbacking up

recovery system files . . . . . 82, 100, 113, 137, 154backup

verifying . . . . . . . . . . . . . 83, 114, 155, 158boot timeout for SAMP . . . . . . . . . . . . . . . 234busying out

IPSI . . . . . . . . . . . . . . . . . . . . . . 217SIPI . . . . . . . . . . . . . . . . . . . . . . 217

busying out MMI circuit packs. . . . . . . . . . . . 151releasing . . . . . . . . . . . . . . . . . . . . 204

busying-outpreviously busied-out trunks . . . . . . 99, 136, 204

busyouts, recording . . . . . . . . . . . .78, 110, 150

Ccall processing, stopping LSP or ESS . . . . . 108, 147CD/DVD-ROM drive

connecting to the media server . . . . . . . . . 84clearing

Web browser cache on laptop . . . . . . . 148, 157clearing alarms, See Resolving alarmsclock synchronization

verifying . . . . . . . . . . . . . . . .79, 110, 151command line interface. . . . . . . . . . . . . . . 236

accessing with SSH. . . . . . . . . . . . . . . 236commands

busyout . . . . . . . . . . . . . . . . . . . . 217list ipserver-interface . . . . . . . . . . . . . . 221set ipserver-interface . . . . . . . . . . . . . . 221

Communication Managercopying . . . . . . . . . . . . . 86, 121, 167, 187registering . . . . . . . . . . . . . . 101, 138, 209upgrading S8400 . . . . . . . . . . . . . . . . 75

connectingto standby server . . . . . . . . 156, 164, 185, 206

corruption of translationschecking for . . . . . . . . . . . . . . . . . 79, 111

DDAL2

adding . . . . . . . . . . . . . . . . . . . . 241Adding DAL2 or replacing DAL1 with DAL2 . . . 241installing in the S8730 . . . . . . . . . . . . . 250

DIMMinstalling in S8500B . . . . . . . . . . . . . . .114

direct connection to server . . . . . . . . . . . . 227Download IPSI Firmware Web page . . . . . . . . 219downloading Communication Manager software, see

Communication Manager, copying

EESS

stopping call processing . . . . . . . . . . 108, 147stopping during upgrade . . . . . . . . . . . . 107upgrading . . . . . . . . . . . . . . .107, 142, 144upgrading Communication Manager software 105, 142

ESS serverconfigure for S8720 in XL configuration .130, 177, 198

ESS serversverifying the status . . . . . . . . . . . . . . 145

ESSsstarting and stopping . . . . . . . . . . . . . 134stopping and starting . . . . . . . . . . . . . 182

extra large (XL) configurationconfiguring ESS or LSP media server. .130, 177, 198configuring LSP . . . . . . . . . . . .130, 177, 198

Ffiber-PNC

license . . . . . . . . . . . . . . . . . . . . . 39firmware

downloading to IPSI . . . . . . . . . . . . . . 218for IP telephones . . . . . . . . . . . 76, 104, 141upgrading Ethernet switch . . . . . . . . . 223, 225upgrading MPC on S8400 . . . . . . . . . . . . 77upgrading SAMP . . . . . . . . . . . . . . . 108

firmware downloadIPSI . . . . . . . . . . . . . . . . . . . . . 218


Index

SIPI . . . . . . . . . . . . . . . . . . . . . . 218

Hh.248 gateways

upgrading . . . . . . . . . . . . . . . . . 77, 105h.248 media gateways

upgrading . . . . . . . . . . . . . . . . . . . 142

Iinstalling

pre-upgrade service pack . . . . . . . 119, 165, 186interchanging S8700-series Servers. . . . . . . . . 179IP telephone files

restoring after upgrade . . . . . . . . 76, 104, 141IPSI

activating firmware . . . . . . . . . . . . 219, 220busying out. . . . . . . . . . . . . . . . . . . 217downloading firmware. . . . . . . . . . . . . . 218firmware download . . . . . . . . . . . . . . . 218interchanging duplicated . . . . . . . . . . . . 221listing . . . . . . . . . . . . . . . . . . . . . 217releasing standby . . . . . . . . . . . . . . . . 221upgrading firmware . . . . . . . . . . . . . . . 213verify firmware version . . . . . . . . . . . . . 222verifying health . . . . . . . . . . . . . . . . . 221

Llaptop connection to server . . . . . . . . . . . . . 227license and authentication files

copying to server . . . . . . . 81, 95, 111, 135, 201generating and retrieving . . . . . . . . . . . . 39installing on server . . . . . . . . . . 95, 133, 181

license filePNC settings . . . . . . . . . . . . . . . . . . 39RFA process . . . . . . . . . . . . . . . . . . 38

loginobtaining password for . . . . . . . . . . . . . 39

login, super-user . . . . . . . . . . . . . . . 132, 180LSP

start call processing. . . . . . . . . . . . 137, 208stopping call processing. . . . . . . . . . 108, 147upgrading . . . . . . . . . . . . . . 77, 105, 142

LSP media serverconfigure for extra large (XL) configuration130, 177, 198

LSPsstarting and stopping . . . . . . . . . . . . . . 134stopping and starting . . . . . . . . . . . . . . 182

Mmain server

configure for S8720 in extra large (XL) configuration175, 196

Maintenance Web Interfacestarting . . . . . . . . . . . . . . . . . . . . 235

maintenance, sceduleddisabling . . . . . . . . . . . . . . . 79, 110, 151

Make Upgrade Permanent Web page . 96, 127, 172, 193manual backup server . . . . . . . . . . . . 104, 140media servers

making the upgrade permanent . . . . . . .96, 127MMI circuit packs

busying out . . . . . . . . . . . . . . . . . . 151releasing . . . . . . . . . . . . . . . . . . . 204

modemaccess to server. . . . . . . . . . . . . . . . 233

MPCupgrading firmware on S8400 . . . . . . . . . . 77

Ppassword

after installation . . . . . . . . . . . . . . . . . 39PNC

license . . . . . . . . . . . . . . . . . . . . . 39PNC settings

IP-PNClicense . . . . . . . . . . . . . . . . . . . 39

powerremoving . . . . . . . . . . . . . . . . . . . 242

pre-upgrade service packactivating . . . . . . . . . . . . . . .119, 165, 186installing . . . . . . . . . . . . . . .119, 165, 186

processor ethernetsetting the port . . . . . . . . . . . . . . . . 134

Rrebooting the server, software upgrade 90, 124, 169, 190registering Communication Manager . . . .101, 138, 209release alarm suppression . . . . . 100, 137, 206, 207remote access to server

over modem . . . . . . . . . . . . . . . . . 233over network . . . . . . . . . . . . . . . . . 233

removingpower . . . . . . . . . . . . . . . . . . . . 242

resolvingalarms . . . . . . . . . 82, 99, 112, 136, 153, 205

RFA process . . . . . . . . . . . . . . . . . . . . 38

SS8400

upgrading from R3.1/R3.1.x to R5.x with Web pages75S8500B

installing a DIMM . . . . . . . . . . . . . . . .114


Index

S8700-series Serverinterchanging servers . . . . . . . . . . . . . . 179

S8720 in extra large (XL) configurationconfiguring main server . . . . . . . . . . 175, 196

S8730installing DAL2 . . . . . . . . . . . . . . . . . 250

SAMPdisabling the boot timeout . . . . . . . . . . . . 234upgrading firmware . . . . . . . . . . . . . . . 108

scheduled maintenancedisabling . . . . . . . . . . . . . . . .79, 110, 151

servercommand line interface . . . . . . . . . . . . . 236

serversaccess remotely over modem . . . . . . . . . . 233access remotely over network . . . . . . . . . . 233direct connection . . . . . . . . . . . . . . . . 227interchanging servers . . . . . . . . . . . . . . 179license and authentication files . . . . 95, 133, 181making the upgrade permanent . . . . . . 172, 193starting Maintenance Web pages80, 111, 149, 152, 162upgrade documentation . . . . . . . . . . . . . 18verifying operation of . . . . . . . . . . . . . . 200

service packactivating. . . . . . . . . . . . . . . 119, 165, 186

service pack, preupgrade. . . . . . . . . . . . . . 165Set identities Web page . . . . . . . . . . . . . . 134SIPI

activating firmware . . . . . . . . . . . . 219, 220busying out. . . . . . . . . . . . . . . . . . . 217firmware download . . . . . . . . . . . . . . . 218listing . . . . . . . . . . . . . . . . . . . . . 217upgrading firmware . . . . . . . . . . . . . . . 213verifying firmware version . . . . . . . . . . . . 222verifying health . . . . . . . . . . . . . . . . . 221

software upgraderebooting the server. . . . . . . . . . . . . 90, 124verify software operation after . . . 92, 126, 171, 192

SREPN . . . . . . . . . . . . . . . . . . . . . . 140standby server

connecting to . . . . . . . . . . 156, 164, 185, 206stopping and starting ESSs and LSPs . . . . . . . . 182super-user login . . . . . . . . . . . . . . . 132, 180suppressing

alarms . . . . . . . . . . . . . . . . . . 171, 192Survivable Remote EPN . . . . . . . . . . . . . . 140synchronization of clock . . . . . . . . . .79, 110, 151system files

backing up . . . . . . . . . .82, 100, 113, 137, 154

Tterminal emulation . . . . . . . . . . . . . . . . . 236TN8412 firmware upgrade . . . . . . . . . . . . . 213translation corruption

checking for . . . . . . . . . . 79, 99, 111, 136, 152

Uupgrade firmware

Ethernet switch . . . . . . . . . . . . . . . . 225upgrading

ESSs . . . . . . . . . . . . . . . . . . . . . 142LSPs . . . . . . . . . . . . . . . . . . . .77, 105making the upgrade permanent . . 96, 127, 172, 193MPC firmware on S8400 . . . . . . . . . . . . . 77reboot the server . . . . . . . . . . . . . . . 190SAMP firmware . . . . . . . . . . . . . . . . 108servers

documentation needed . . . . . . . . . . . . 18upgrading Communication Manager

on ESS . . . . . . . . . . . . . 105, 107, 142, 144on LSP . . . . . . . . . . . . . . . . . . 105, 142R3.1/R3.1.x to R5.x on S8400 . . . . . . . . . . 75rebooting the server . . . . . . . . . . . . . . 169

upgrading firmwareEthernet switch . . . . . . . . . . . . . . . . 223G250 Gateway . . . . . . . . . . . . . . .77, 105G350 Gateway . . . . . . . . . . . . . . .77, 105G350 Media Gateway . . . . . . . . . . . . . 142G700 Gateway . . . . . . . . . . . . . . .77, 105G700 Media Gateway . . . . . . . . . . . . . 142h.248 media gateways . . . . . . . . . . . . . 142IPSI . . . . . . . . . . . . . . . . . . . . . 213SIPI . . . . . . . . . . . . . . . . . . . . . 213

upgrading softwareusing Maintenance Web Interface . . . . . . . . 75

WWeb browser cache

clearing on laptop . . . . . . . . . . . . . 148, 157Web pages

Activate IPSI Upgrade . . . . . . . . . . . . . 220Download IPSI Firmware. . . . . . . . . . . . 219IPSI Version . . . . . . . . . . . . . . . . . 222Make Upgrade Permanent . . . . . 96, 127, 172, 193Set identities . . . . . . . . . . . . . . . . . 134starting . . . . . . . . . . . . . . . . . . . . 235

XXL configuration considerations . . . . . . . . 175, 196


Index

Documents

Upgrading Avaya Aura™ Communication Manager …support.avaya.com/elmodocs2/comm_mgr/R5_2/CM5_2_htmlpages/CM5_2...Pre-upgrade service pack requirements ... TN2312AP/BP IPSI circuit