Avaya S8 Series User manual

Upgrading Avaya Aura™

Communication Manager on Avaya

S8xxx Servers

03-602885

Issue 1

May 2009

Notice

While reasonable efforts were made to ensure that the information in this

document was complete and accurate at the time of printing, Avaya Inc. can

assume no liability for any errors. Changes and corrections to the information

in this document may be incorporated in future releases.

For full support information, please see the complete document,

Avaya Support Notices for Hardware Documentation, document number

03-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 disclaimer

Avaya Inc. is not responsible for any modifications, additions, or deletions to

the original published version of this documentation unless such modifications,

additions, or deletions were performed by Avaya. Customer and/or End User

agree to indemnify and hold harmless Avaya, Avaya's agents, servants and

employees against all claims, lawsuits, demands and judgments arising out of,

or in connection with, subsequent modifications, additions or deletions to this

documentation to the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked Web

sites referenced elsewhere within this documentation, and Avaya does not

necessarily endorse the products, services, or information described or offered

within them. We cannot guarantee that these links will work all of the time and

we have no control over the availability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales

agreement to establish the terms of the limited warranty. In addition, Avaya’s

standard warranty language, as well as information regarding support for this

product, while under warranty, is available through the following Web site:

http://www.avaya.com/support

.

Copyright

Except where expressly stated otherwise, the Product is protected by copyright

and other laws respecting proprietary rights. Unauthorized reproduction,

transfer, and or use can be a criminal, as well as a civil, offense under the

applicable law.

Avaya support

Avaya provides a telephone number for you to use to report problems or to ask

questions about your product. The support telephone number

is 1-800-242-2121 in the United States. For additional support telephone

numbers, see the Avaya Web site: http://www.avaya.com/support

.

Contents

Issue 1 May 2009 3

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Firmware upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Upgrading to Communication Manager Release 5.2 . . . . . . . . . . . . . . . . . . . 18

Upgrade tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

The Avaya Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Manage Software Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Avaya Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Communication Manager Servers managed by Software Update Manager . . . . . 20

Error resistant download via https . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Upgrade procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Upgrading to Communication Manager Release 5.2 . . . . . . . . . . . . . . . . . 23

Upgrade sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Avaya one-X portal dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Duplicated Enterprise Survivable Server (ESS) upgrade . . . . . . . . . . . . . . . . . 26

Upgrade procedures for Duplicated ESS Servers. . . . . . . . . . . . . . . . . . . 27

Duplex ESS upgrade workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

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

Chapter 2: Upgrading Software on Servers . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Common prerequisites for all upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Checklist of tasks to perform before you go on site . . . . . . . . . . . . . . . . . 36

RFA license and authentication files. . . . . . . . . . . . . . . . . . . . . . . . . . 38

Generating and retrieving license and authentication files. . . . . . . . . . . . . . 39

Logins and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Platform/PNC license settings for the S8700-Series Server . . . . . . . . . . . . . 39

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

Preserving connections while upgrading an S8700-Series Server. . . . . . . . . . . . 40

Connections not preserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Tools to preserve connections during an upgrade . . . . . . . . . . . . . . . . . . 42

Manual 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Pre-upgrade service pack requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 49

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

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Pre-upgrade service pack requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Tasks 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

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

Manage Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

The need to restore IP telephone files . . . . . . . . . . . . . . . . . . . . . . . . . 76

TN8412AP SIPI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . . . 76

Upgrading LSPs and media gateways, if any . . . . . . . . . . . . . . . . . . . . . 77

Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Upgrading the MPC firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 78

Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 79

Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 79

Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

Accessing the server’s web interface . . . . . . . . . . . . . . . . . . . . . . . . . 80

Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Ensuring a super-user login exists. . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Suppressing alarming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Connecting the CD/DVD-ROM drive to the server . . . . . . . . . . . . . . . . . . . 84

Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 86

Removing the CD-ROM from the CD-ROM drive. . . . . . . . . . . . . . . . . . . . 87

Installing Communication Manager on the server. . . . . . . . . . . . . . . . . . . 88

Contents

Issue 1 May 2009 5

Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Verifying reboot progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Installing security and Communication Manager

service pack updates, if any . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing the RFA license file and authentication file . . . . . . . . . . . . . . . . 95

Copying IP telephone firmware to the server, if necessary. . . . . . . . . . . . . . 95

Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 96

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Accessing the server command line interface with ssh protocol . . . . . . . . . . 97

Enabling scheduled maintenance with SAT (main only) . . . . . . . . . . . . . . . 98

Busying out previously busied-out trunks. . . . . . . . . . . . . . . . . . . . . . . 99

Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 100

Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 101

Registering 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

The need to restore IP telephone firmware files . . . . . . . . . . . . . . . . . . . 104

TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . 105

Upgrading LSPs and media gateways, if any . . . . . . . . . . . . . . . . . . . . . 105

Upgrading firmware on media gateways and media modules . . . . . . . . . . . . 107

Upgrade of Communication Manager on the ESS servers . . . . . . . . . . . . . . 107

Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Upgrading the SAMP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Stopping call processing on the LSPs or ESS servers

if being used (main server only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 109

Recording all busyouts (main server only) . . . . . . . . . . . . . . . . . . . . . . 110

Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 110

Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 110

Checking for translation corruption with the SAT. . . . . . . . . . . . . . . . . . . 111

Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 111

Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Contents

Issue 1 May 2009 6

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Ensuring a super-user login exists. . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Installing a DIMM in an S8500B Server. . . . . . . . . . . . . . . . . . . . . . . . . 114

Suppressing alarming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

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

Checking software release, only if starting from R2.x . . . . . . . . . . . . . . . . 118

Activating the preupgrade service pack, only if starting from R2.x . . . . . . . . . 119

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Inserting the Communication Manager CD into the server . . . . . . . . . . . . . . 120

Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 121

Installing Communication Manager on the server. . . . . . . . . . . . . . . . . . . 122

Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Verifying reboot progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 127

Installing security and Communication Manager

service pack updates, if any . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Accessing the server command line interface with ssh protocol . . . . . . . . . . 129

Configuring the ESS or LSP for compatibility with an XL configuration. . . . . . . 130

Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Creating a customer login (if necessary) . . . . . . . . . . . . . . . . . . . . . . . 132

Installing the RFA license file and authentication file . . . . . . . . . . . . . . . . 133

Stopping and starting ESS servers. . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Setting the Processor Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Copying IP telephone firmware to the server, if necessary

(main servers only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Enabling scheduled maintenance with SAT (main only) . . . . . . . . . . . . . . . 135

Busying out previously busied-out trunks. . . . . . . . . . . . . . . . . . . . . . . 136

Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 137

Starting call processing on the LSPs and ESSs, if any

(main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 138

Registering 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

The need to restore IP telephone firmware files . . . . . . . . . . . . . . . . . . . 141

TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . . . . . . . . . . . 142

Upgrading media gateways, LSPs and ESS servers, if being used . . . . . . . . . 142

Upgrading firmware on media gateways and media modules . . . . . . . . . . . . 144

Upgrade of Communication Manager on the ESS servers . . . . . . . . . . . . . . 144

Duplex ESS upgrade workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Verifying the status of ESS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Stopping call processing on the LSPs or ESS servers

if being used (main server only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

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

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

Connecting to the active server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 149

Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Checking link status with SAT (main server only). . . . . . . . . . . . . . . . . . . 150

Recording all busyouts (main server only) . . . . . . . . . . . . . . . . . . . . . . 150

Checking synchronization with the SAT (main server only) . . . . . . . . . . . . . 151

Disabling scheduled maintenance with the SAT (main server only) . . . . . . . . . 151

Busying out MMI circuit packs with SAT for a duplicated control

network only (main server only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . 152

Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Ensuring a super-user login exists. . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Backing up recovery system files on the active server . . . . . . . . . . . . . . . . 154

Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Suppressing alarming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 155

Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Clearing the ARP cache on the laptop computer . . . . . . . . . . . . . . . . . . . 156

Clearing the Web browser cache on the laptop . . . . . . . . . . . . . . . . . . . . . . 157

Backing up files on the standby server . . . . . . . . . . . . . . . . . . . . . . . . 157

Verifying the backup on the standby server . . . . . . . . . . . . . . . . . . . . . . 158

Suppressing alarming on the standby server . . . . . . . . . . . . . . . . . . . . . 158

Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 159

Contents

Issue 1 May 2009 8

Removing a DAL1 or installing a DAL2 card. . . . . . . . . . . . . . . . . . . . . . 159

Placing or Replacing the server in the rack . . . . . . . . . . . . . . . . . . . . . . 160

Restoring power to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Verify that the DAL2 card is installed correctly . . . . . . . . . . . . . . . . . . . . 161

Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 161

Connecting to the active server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Accessing the active server’s web interface. . . . . . . . . . . . . . . . . . . . . . 162

Selecting the Preupgrade Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 163

Upgrade tasks for the first server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Clearing the ARP cache on the laptop . . . . . . . . . . . . . . . . . . . . . . . . . 164

Checking the software release on the standby server . . . . . . . . . . . . . . . . 165

Activating the preupgrade service pack on the standby server

(R2.x only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Inserting the Communication Manager CD-ROM into the standby

server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 167

Upgrading Communication Manager on the server . . . . . . . . . . . . . . . . . . 168

Rebooting the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Verifying reboot progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Suppressing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 172

Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 172

Installing security and service pack updates, if any . . . . . . . . . . . . . . . . . 172

Configuring the Processor Ethernet interface (on the ESS) . . . . . . . . . . . . . 173

Accessing the server command line interface with ssh protocol . . . . . . . . . . 173

XL configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 179

Releasing the standby server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Interchanging the servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Performing an integrity check on the first S8700-Series Server . . . . . . . . . . . 180

Creating a super-user login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Installing the new license and Avaya authentication files on newly

active server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Stopping and starting the ESS servers . . . . . . . . . . . . . . . . . . . . . . . . 182

Disconnecting from the newly active server. . . . . . . . . . . . . . . . . . . . . . 182

Upgrade tasks for the new standby server (second server) . . . . . . . . . . . . . . . 183

Removing a DAL1 or installing a DAL2 card. . . . . . . . . . . . . . . . . . . . . . 183

Placing or Replacing the server in the rack . . . . . . . . . . . . . . . . . . . . . . 184

Contents

Issue 1 May 2009 9

Restoring power to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Verify that the DAL2 card is installed correctly . . . . . . . . . . . . . . . . . . . . 185

Disconnecting from the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Accessing the standby server’s maintenance interface . . . . . . . . . . . . . . . 186

Checking the software release on the standby server . . . . . . . . . . . . . . . . 186

Activating the preupgrade service pack on the server (R2.x only). . . . . . . . . . 186

Inserting the Communication Manager CD into the server . . . . . . . . . . . . . . 187

Copying Communication Manager to the server . . . . . . . . . . . . . . . . . . . 187

Upgrading Communication Manager on the server . . . . . . . . . . . . . . . . . . 189

Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Verifying reboot progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Suppressing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Performing an integrity check on the second S8700-Series Server . . . . . . . . . 193

Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . . . . 193

Installing security and service pack updates, if any . . . . . . . . . . . . . . . . . 193

Configuring the Processor Ethernet interface (on the ESS) . . . . . . . . . . . . . 194

Accessing the server command line interface with ssh protocol . . . . . . . . . . 194

XL configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Performing an integrity check on the second S8700-Series Server . . . . . . . . . 200

Verifying the operation of the servers . . . . . . . . . . . . . . . . . . . . . . . . . 200

Setting Server A/Server 1 active for ESS, if necessary . . . . . . . . . . . . . . . . 200

Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Copying IP telephone firmware to the server, if necessary

(main servers only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Disconnecting from the standby server . . . . . . . . . . . . . . . . . . . . . . . . 202

Administering 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) . . . . . . . . . . . 204

Releasing MMI circuit packs in duplicated control network using SAT, (main server only)

204

Busying out previously busied-out trunks (main server only) . . . . . . . . . . . . 204

Checking for translation corruption with SAT (main server only) . . . . . . . . . . 204

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Backing up files on the active server. . . . . . . . . . . . . . . . . . . . . . . . . . 205

Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 206

Logging off all administration applications on the active server. . . . . . . . . . . 206

Disconnecting from the active server . . . . . . . . . . . . . . . . . . . . . . . . . 206

Connecting to the standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Contents

Issue 1 May 2009 10

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Backing up files on the standby server . . . . . . . . . . . . . . . . . . . . . . . . 207

Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . 207

Starting call processing on the LSPs and ESSs, if any . . . . . . . . . . . . . . . . 208

Logging off all administration applications . . . . . . . . . . . . . . . . . . . . . . 208

Registering Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 3: Upgrading Firmware on TN circuit packs

and Ethernet switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

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

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

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Access the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Determining current IPSI firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Pre-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Interchanging the IPSIs (duplicated control network only) . . . . . . . . . . . . . . 221

Post-upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

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

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

Appendix A: Accessing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Connecting to the server directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Computer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Connecting to the server remotely over the network . . . . . . . . . . . . . . . . . . . 233

Connecting to the server remotely over a modem . . . . . . . . . . . . . . . . . . . . 233

Setting up a dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Dialing up to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Finding the IP address of the active server (duplicated servers) . . . . . . . . . . 234

Disabling the boot timeout of the SAMP board . . . . . . . . . . . . . . . . . . . . 234

Accessing the System Management Interface (SMI) . . . . . . . . . . . . . . . . . . . 235

Using the command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

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

Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Contents

Issue 1 May 2009 11

Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Browser settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Connecting directly to the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Connecting remotely through the network . . . . . . . . . . . . . . . . . . . . . . 240

Appendix B: DAL: Removing or Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Verifying which DAL is installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Removing power from the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Removing the server from the rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Removing the cover from the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Removing the PCI riser cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Removing the DAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Installing the DAL2 in the S8710 or S8720 . . . . . . . . . . . . . . . . . . . . . . . . . 247

Replacing the PCI riser cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

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

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 upgrades

Several pieces of equipment require periodic firmware upgrades. This equipment includes:

● The IP Server Interface circuit pack (TN2312AP/BP)

● Programable circuit packs (TN799DP, TN2302AP, TN2602AP)

● Avaya Ethernet switches (C-363T, C-364T), if being used.

Introduction

18 Upgrading Avaya Aura™ Communication Manager on Avaya S8xxx Servers

!

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

To upgrade Communication Manager to Release 5.2, you need to follow the same upgrade

process as done for previous Communication Manager releases, if those upgrade processes

included using Manage Software or Software Update Manager. Upgrade Tool and Avaya

Installation Wizard cannot be used to upgrade to Communication Manager Release 5.2 or later.

The applicable changes for Release 5.2 are:

● You can no longer use the Upgrade Tool for the upgrade.

● You can no longer use Avaya Installation Wizard (AIW) for the upgrade.

● Changed upgrade procedure, if you are upgrading a system that includes S8700-Series

Server.

Upgrade tool

You cannot use the Upgrade Tool to upgrade Communication Manager to Release 5.2 or later.

After Communication Manager 5.2 is running on the server, the System Management Interface

contains a reference to the Upgrade Tool (from menu, Upgrade > Upgrade Tool).

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 page

Manage Software Web page is used to load any new release of the Communication Manager

software for the main server. The Manage Software can also be run remotely, if you can access

the System Management Interface (SMI). The Manage Software can be directed to copy the

release software from a TFTP server to the disk of the media server. The Manage Software can

also be directed to copy the release software from a URL (an HTTP Web server) to the disk of

the server.

For Release 5.2 of Communication Manager the Manage Software Web page provides

additional secure method for copying files to the server. The change in the field for Release 5.2

is:

● IA770 Intuity Audix term replaced with Communication Manager Messaging (CMM)

Introduction

20 Upgrading Avaya Aura™ Communication Manager on Avaya S8xxx Servers

Avaya Software Update Manager

Avaya Software Update Manager (SUM) is an application that downloads software to managed

Avaya devices. Avaya Software Update Manager also checks the software versions currently in

use against the latest versions available from Avaya, and recommends updates when a newer

version is available. For more information on SUM Tool see Avaya Integrated Management 5.2

Software Update Manager User Guide available at 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 https

After Communication Manager 5.2 is running on the server, subsequent use of Manage

Software for upgrades will provide enhancements when compared to previous releases.

Release 5.2 of Communication Manager has implemented upgrade improvements to provide a

more robust and remotely successful distributed Communication Manager System upgrade

experience. These upgrade improvements in Release 5.2 of Communication Manager enable

you to:

● Reduce copy size from files size (which currently can approach 100MB) to something

more granular (for example: block size) such that when remote upgrades are being

performed over a bouncing network as much of the copying is done without re-transmittal.

● Support SCP and HTTPS protocol, which is added to allow secure file transfers.

Page is loading ...

Avaya S8 Series User manual

Avaya S8 Series User manual

Related papers

Other documents