Upgrading, Migrating, and Converting Media Servers and Gateways

Upgrading, Migrating, and Converting Media Servers and Gateways
Release 3.1
03-300412 Issue 2.1 June 2006
2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full support information, please see the complete document, Avaya Support Notices for Hardware Documentation, document number 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, Avayas 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
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . .
Port network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reliability and availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this book is designed and organized . . . . . . . . . . . . . . . . . . . .
51
51 52 54 56
Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firmware upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
64 64
Chapter 2: Upgrading Software on Media Servers . . . . . . . . . . .

Upgrades that can affect service . . . . . . . . . . . . . . . . . . . . . . . . . Common prerequisites for all upgrades . . . . . . . . . . . . . . . . Checklist of tasks to perform before you go on site . . . . . . . . License and Avaya authentication files . . . . . . . . . . . . . . . Generating and retrieving license and authentication files . . . . Logins and passwords . . . . . . . . . . . . . . . . . . . . . . . . Caution about platform/PNC license settings for the S8700-series Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
66 67 68 70 70 71 71 73
. . . . .
Upgrade modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading Communication Manager from 1.x to 3.1 on an S8300 Media Server . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-upgrade service pack requirements . . . . . . . . . . . . . . . . . . . . . Tasks checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
75 76 77 78
Upgrading Communication Manager from 2.x to 3.1 on an S8300 Media Server . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
83 84 85
Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The need to restore IP telephone files . . . . . . . . . . . . . . . . . . . .
89
90 90
Issue 2.1 June 2006
Contents
TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . Preupgrade service pack for upgrades starting from R2.x only . Upgrading LSPs, ESSs, and H.248 media gateways, if any . . . Upgrading firmware on media gateways and media modules . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
90 91 91 93 94 94 96 97 97 97 97 98 98 99 99 100 100 100 101 101 101 102 102 103 103 104 105 105 106 107 110 111 112 112 112 113 113 114
SAMP card boot timeout if upgrading with remastering program . . . . . . . Upgrade tasks (S8500 Main Server as main server) . . . . . . . . . . . . . . . Upgrade tasks (S8500 Main Server as ESS) . . . . . . . . . . . . . . . . . . . Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the SAMP firmware (S8500B only). . . . . . . . . . . . . Connecting to the media server . . . . . . . . . . . . . . . . . . . . Stopping call processing on the LSPs or ESSs if being used (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Checking link status with SAT (main server only) . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . Checking synchronization with the SAT (main server only) . . . . . Disabling scheduled maintenance with the SAT (main server only) Checking for translation corruption with the SAT . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . Saving a copy of the 4600-series telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . Checking software release, only if starting from R2.x . . . . . . . . Activating the preupgrade service pack, only if starting from R2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting the Communication Manager CD-ROM into the media server. Copying Communication Manager to the media server . . . . . . . . . Installing Communication Manager on the media server . . . . . . . . Rebooting the media server . . . . . . . . . . . . . . . . . . . . . . . . Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . . . Making the upgrade permanent on the media server . . . . . . . . . . Installing postupgrade service pack, if any, on media server . . . . . . Setting the Processor Ethernet . . . . . . . . . . . . . . . . . . . . . . Copying IP telephone firmware to the media server, if necessary (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. .
4 Upgrading, Migrating, and Converting Media Servers and Gateways
Contents
Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the 4600-series IP Telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . Starting call processing on the LSPs and ESSs, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . . Registering Avaya Communication Manager . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115 115 115 115 116 116 116 117 117 118 118
. . . . . . . . . . . . . . .
Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Upgrade Tool . . . . . . . . . . . . . . . . . . . .
About use of the Upgrade Tool . . . . . . . . . . . . . . . . . . . . . . . . . . Which devices the Upgrade Tool can upgrade . . . . . . . . . . . . . . . . SAMP card boot timeout if upgrading with remastering program . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . Preupgrade service pack for upgrades starting from R2.x only . Overview of the upgrade process . . . . . . . . . . . . . . . . . The need to restore IP Phone files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
120 121 121 121 122 122 122 124 124 126 126 126 126 127 127 127 128 128 128 129 129 130
Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the SAMP firmware (S8500B only). . . . . . . . . . . . . . . . . Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking link status with SAT (main server only) . . . . . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking synchronization with the SAT (main server only) . . . . . . . . . Disabling scheduled maintenance with the SAT (main server only) . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . . Saving a copy of the 4600-series telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . . . Copying the service pack files to the media server, only if starting from R2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the preupgrade software service pack only if starting from R2.x
Issue 2.1 June 2006
Contents
Copying files to the media server . . . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting the Communication Manager CD-ROM into the media server. Copying Communication Manager to the media server . . . . . . . . . Removing the CD-ROM from the CD-ROM drive . . . . . . . . . . . . . Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Upgrade Tool . . . . . . . . . . . . . . . . . . . . . . Installing Avaya authentication files (if required) . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . Setting the Processor Ethernet . . . . . . . . . . . . . . . . . . . Copying IP telephone firmware to the media server, if necessary (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the 4600-series IP Telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . . Registering Avaya Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
131 131 132 132 132 133 134 135 135 136 137 137 138 138 139 139 139 140 140 140 140 141 141 141 142 142 142
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Postrequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the G150 Media Gateways, if used . . . . . . . . . . . . . . . .
Upgrading Communication Manager on Avaya S8700 Media Server from R1.x to R3.1 . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . Preupgrade service pack . . . . . . . . . . . . . . . . . . . . . Upgrade of LSPs and media gateways, if being used . . . . . Upgrading firmware on media gateways and media modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
144 144 144 145 147 147 151
Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Stopping call processing on the LSPs or ESSs if being used (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Checking link status with SAT (main server only) . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . Checking synchronization with the SAT (main server only) . . . . . Disabling scheduled maintenance with the SAT (main server only) Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Backing up files on the standby media server . . . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . Copying preupgrade service pack(s) to the standby media server . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
151 151 152 152 153 153 153
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154 154 154 155 155 156 156 156 157 157 157 158 158 158 159 159 159 160 160 161 161 163 164 164 165 165 166 167 168 168 169
Upgrade tasks (first media server) . . . . . . . . . . . . . . . . . . . . . . Busying out the standby media server . . . . . . . . . . . . . . . . . . Checking the software release on the standby media server . . . . . . Installing the preupgrade service pack . . . . . . . . . . . . . . . . . . Verifying connectivity to customer network server. . . . . . . . . . . . Backing up the system files with Linux MigrationBackup . . . . . . Setting Telnet parameters . . . . . . . . . . . . . . . . . . . . . . . . . Erasing the MBR on the media server . . . . . . . . . . . . . . . . . . . Inserting the Communication Manager CD-ROM into the media server. Rebooting the standby media server . . . . . . . . . . . . . . . . . . . Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . Installing Communication Manager . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . . . Selecting media server type . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
Contents
Configuring the network parameters (optional). . . . . . . . . . . . Verifying connectivity to the network server (optional) . . . . . . . Installing postupgrade service pack, if any, on media server . . . . Verifying installation of the service pack . . . . . . . . . . . . . . . Restoring the Linux migration backup files . . . . . . . . . . . . . Verifying date and time . . . . . . . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . Releasing the standby media server. . . . . . . . . . . . . . . . . . Interchanging the media servers. . . . . . . . . . . . . . . . . . . . Installing the new license and Avaya authentication files on newly active media server . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
169 171 171 172 173 174 175 175 175 175 176 177 177 177 177 177 178 178 179 179 181 182 182 182 183 184 185 185 185 186 188 188 188 189 190 191 191 192 192 192
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrade tasks (second media server) . . . . . . . . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . Copying preupgrade service pack(s) to the standby media server . . . Busying out the standby media server . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . Installing the preupgrade service pack . . . . . . . . . . . . . . . . . . Verifying connectivity to customer network server (optional) . . . . . . Backing up the system files using Linux MigrationBackup . . . . . . Erasing the MBR on the standby media server . . . . . . . . . . . . . . Inserting the Communication Manager CD-ROM into the media server. Rebooting the standby media server . . . . . . . . . . . . . . . . . . . Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . Installing Communication Manager . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . . . Selecting media server type . . . . . . . . . . . . . . . . . . . . . . . . Configuring the network parameters (optional). . . . . . . . . . . . . . Verifying connectivity from the network server. . . . . . . . . . . . . . Verifying connectivity to the network server (optional) . . . . . . . . . Installing postupgrade service pack, if any, on media server . . . . . . Verifying service pack installation . . . . . . . . . . . . . . . . . . . . . Restoring the Linux migration backup files . . . . . . . . . . . . . . . Verifying date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing the standby media server. . . . . . . . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . . . . . . .
Contents
Connecting to the active media server . . . . . . . . . . . . . . . . . . . . Verifying the operation of the media servers . . . . . . . . . . . . . . . . . Postupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . . . . . Releasing MMI circuit packs with SAT (duplicated control network only) Busying out previously busied out trunks . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . Logging off all administration applications on the active media server . Disconnecting from the active media server . . . . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . . Backing up files on the standby media server . . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . Starting call processing on the LSPs and ESSs, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging off all administration applications on the standby media server Registering Avaya Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
192 193 193 193 193 194 194 194 194 195 195 195 196 196 196 197 197 198
Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . . Preupgrade service pack for upgrades starting from R2.x only . . Upgrade of H.248 media gateways, LSPs and ESSs, if being used The need to restore IP telephone files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
200 200 201 201 203 204 207 209 209 210 210 210 211 211 211 212
Upgrade tasks for the S8700-series Media Server as main server . . . . . . . Upgrade tasks (S8700-series Media Server as ESS) . . . . . . . . . . . . . . Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping call processing on the LSPs or ESSs if being used (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Checking link status with SAT (main server only) . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . Checking synchronization with the SAT (main server only) . . . . . Disabling scheduled maintenance with the SAT (main server only) Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
Issue 2.1 June 2006
Contents
Checking for translation corruption . . . . . . . . . . . . . . . . Saving a copy of the 4600-series telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . Copying files to the media server . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . Accessing the media server maintenance web interface. . . . . Copying files to the media server . . . . . . . . . . . . . . . . . Backing up files on the standby media server . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . Tasks to preserve connections when starting from R3.0.1 only (main server only): . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . Connecting to the active media server . . . . . . . . . . . . Accessing the media server maintenance web interface. . . Selecting the Preupgrade Step to preserve calls . . . . . . . Disconnecting from the active media server . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212 213 213 214 214 214 215 215 216 216 216 217 217 218 218 218 219 219 219 219 220 221 221 221 221 221 222 223 223 225 227 228 229 229 229 230 230 231
Upgrade tasks for the first media server . . . . . . . . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . . Busying out the standby media server . . . . . . . . . . . . . . . . . . . Checking the software release on the media server, if starting from R2.x only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the preupgrade service pack on the media server (R2.x only). Inserting the Communication Manager CD-ROM into the media server. . Copying Communication Manager to the media server . . . . . . . . . . Installing Communication Manager on the media server . . . . . . . . . Rebooting the media server . . . . . . . . . . . . . . . . . . . . . . . . . Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . . . . Making the upgrade permanent on the media server . . . . . . . . . . . Installing postupgrade service pack, if any, on media server . . . . . . . Releasing the standby media server. . . . . . . . . . . . . . . . . . . . . Interchanging the media servers. . . . . . . . . . . . . . . . . . . . . . .
Contents
Installing the new license and Avaya authentication files on newly active media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the newly active media server. . . . . . . . . . . . . . Upgrade tasks for the new standby media server (second server) . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . . Busying out the standby media server . . . . . . . . . . . . . . . . . . . Checking the software release on the media server (R2.x only) . . . . . . Activating the preupgrade service pack on the media server (R2.x only). Inserting the Communication Manager CD-ROM into the media server. . Copying Communication Manager to the media server . . . . . . . . . . Installing Communication Manager on the media server . . . . . . . . . Rebooting the media server . . . . . . . . . . . . . . . . . . . . . . . . . Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . . . . Making the upgrade permanent on the media server . . . . . . . . . . . Installing postupgrade service pack, if any, on media server . . . . . . . Releasing the standby media server. . . . . . . . . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . . . . Verifying the operation of the media servers . . . . . . . . . . . . . . . . Copying IP telephone firmware to the media server, if necessary (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the 4600-series IP Telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . . . . Releasing MMI circuit packs in duplicated control network using SAT, (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . Logging off all administration applications on the active media server Disconnecting from the active media server . . . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . Backing up files on the standby media server . . . . . . . . . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
232 232 233 233 233 233 234 234 235 235 236 239 240 241 241 241 242 242 243 243 243 243 244 244 245 245 245 245 246 246 247 247 247 247 248 248
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
11
Contents
Starting call processing on the LSPs and ESSs, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . . . . . . . Registering Avaya Communication Manager . . . . . . . . . . . . . . . . .
248 249 249
Using the Upgrade Tool to upgrade Communication Manager on Avaya S8700-Series Media Server . . . . . . . . . . . . . . . . . .
About use of the Upgrade Tool . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade using the Upgrade Tool . . . . . . . . . . . . . . . . . . . . . . . The need to restore IP telephone files . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TN2312AP/BP IPSI circuit pack upgrades . . . . . . . . . . . . . Preupgrade service pack for upgrades starting from R2.x only . Overview of the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
252 253 255 255 255 255 256 257 259 259 259 260 260 260 261 261 262 262 263 263 263 264 264 265 265 265 265 266 266 266 267 267
Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Current configuration tasks: . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Checking link status with SAT (main server only) . . . . . . . . . . Recording all busyouts using SAT. . . . . . . . . . . . . . . . . . . Checking synchronization with the SAT (main server only) . . . . . Disabling scheduled maintenance with the SAT (main server only) Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) . . . . . . . . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . . Saving a copy of the 4600-series telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Backing up files on the standby media server . . . . . . . . . . . . Verifying the backup . . . . . . . . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Copying the service pack files to the media server, only if starting from R2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the preupgrade software service pack (starting from R2.x only) . Copying files to the media server . . . . . . . . . . . . . . . . . . . . . . . Inserting the Communication Manager CD-ROM into the media server. . . Copying Communication Manager to the media server . . . . . . . . . . . Removing CD-ROM from the CD-ROM drive . . . . . . . . . . . . . . . . . Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Upgrade Tool . . . . . . . . . . . . . . . . . . . . . . . . Installing Avaya authentication files on the active server, if required. Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . . . . Copying IP telephone firmware to the media server, if necessary (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267 268 268 269 270 271 272 272 273 274 274 274 275 275 275 275 276 276 276 276 277 277 277 278 278 278 278 279 279 279
. . .
Post-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the 4600-series IP Telephone configuration file, if any (main server only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . . . . . . Releasing MMI using SAT . . . . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . . . . . . Releasing alarm suppression on the media server (optional) . . . . . . . . Logging off all administration applications . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . . . . . . . Backing up files on the standby media server . . . . . . . . . . . . . . . . Releasing alarm suppression on the media server . . . . . . . . . . . . . Logging off the administration applications on the standby media server . Registering Avaya Communication Manager . . . . . . . . . . . . . . . . . Post-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the G150 Media Gateways, if being used . . . . . . . . . . . . .
Chapter 3: Upgrading Firmware on TN circuit packs and Ethernet switches . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
281
281 281
Issue 2.1 June 2006
13
Contents
Upgrading firmware on the IPSIs and SIPIs . . . . . . . . . . . . . .

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access the Maintenance Web Interface . . . . . . . . . . . . . . . . . . . . Determining current IPSI firmware . . . . . . . . . . . . . . . . . . . . . . . Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . Interchanging the IPSIs (duplicated control network only) Post-upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
284 284 285 285 286 286 288 291 292
Upgrading firmware on programmable TN circuit packs. . . . . . . Upgrading firmware on the Avaya Ethernet Switch . . . . . . . . .
293 295
Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
S8400 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC . . . . . . . . . . . Avaya IP600 in a G600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S8500 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths for S8500 Media Servers . . . . . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server SI in an MCC . . . . . . . . . . . . . . . DEFINITY Server SI in an SCC . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC Avaya IP600/S8100 in a G600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 298 298 299 299 300 301 301 301 301 302 302 303 303 303 304 304 304 305 305 305 306
S8700 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths for S8700-Series Media Servers . . . . . . . . . . . . . . . . Transferring translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . From a magneto optical disk . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server SI in an MCC . . . . . . . . . . . . . . . DEFINITY Server SI in an SCC . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC Avaya IP600/S8100 in a G600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common prerequisites to all migrations . . . . . . . . . . . . . . . . . . . . .
Contents
License and Avaya authentication files . . . . . . . . . . . . . . . . Generating and retrieving license and authentication files . . . . Logins and passwords . . . . . . . . . . . . . . . . . . . . . . . . Caution about platform/PNC license settings for the S8700-series Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
313 313 313 314 315
Migration chapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4: Migrating to an Avaya S8400 Media Server . . . . . . . . .

Migration paths for S8400 Media Servers . . . . . . . . . . . . . . . . Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash Migrating from a DEFINITY Server CSI in a CMC using Xmodem . . Migrating from an S8100 using ftp . . . . . . . . . . . . . . . . . . . Migrating all other systems. . . . . . . . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC . Avaya IP600 in a G600 . . . . . . . . . . . . . . . . . . . Prerequisites for migrating to an S8400 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
317
317 317 318 318 318 318 319 319 319 319 320
Migrating from existing DEFINITY and Linux platforms. . . . . . . . . . . . .
Migration modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server that uses a Card Reader . . . . . . . . . 321
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . Installing the linear card reader software Prerequisites . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 321 322 325 325 331 333 333 335 336 337 337 337 338 338 338 339 339
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Accessing Remote Feature Activation. . . Connecting to the processor . . . . . . . . Removing netcon data modules . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . Verifying hardware . . . . . . . . Turning off power to all cabinets. Removing circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
15
Contents
Inserting circuit packs . . . . . . . . . . . Connecting cables . . . . . . . . . . . . . Replacing the TN799C C-LAN circuit pack Installing TN771 Maintenance/Test . . . .
. . . .
. . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
339 340 340 341 341 341 342 343 344 345 345 346 346 347 348 349 350 350 351 351 351 352 352 352 353 353 353 354 354
Migrating translations . . . . . . . . . . . . . . . Installing the software load. . . . . . . . . . . Configuring the media server . . . . . . . . . Installing the license and authentication file . Copying translation files to the media server .
Post-migration administration . . . . . . . . . . . . Assigning IP addresses to the SIPI circuit packs Using static addressing. . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . Logging in to the SIPI . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . Resetting the SIPI . . . . . . . . . . . . . . . . . . Enabling control of the SIPI . . . . . . . . . . . . Verifying SIPI translations . . . . . . . . . . . . . Verifying SIPI connectivity . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . Troubleshooting the migration . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . .
Migrating from a DEFINITY Server CSI in a CMC with an ATA Flash to an S8400 Media Server . . . . . . . . . . . . . . . . . . . . . . .
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the processor . . . . . . . . . . . . . . . . . . . . . . . . . . Removing netcon data modules . . . . . . . . . . . . . . . . . . . . . . . .
355
355 356 356 357 363 365 365 366
Contents
Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . .
. . . .
. . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
367 367 367 368 368 369 369 369 370 370 371 371 371 372 372 373 374 374 375 375 376 376 378 379 379 380 380 380 381 381 381 382 382 382 382
Migration tasks. . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . Turning off the power to the control cabinet Removing circuit packs. . . . . . . . . . . . Inserting circuit packs . . . . . . . . . . . . Connecting cables . . . . . . . . . . . . . . Replacing the TN799C C-LAN circuit pack . Installing TN771 Maintenance/Test . . . . .
Migrating translations . . . . . . . . . . . . . . . Installing the software load. . . . . . . . . . . Configuring the media server . . . . . . . . . Copying translation files to the media server .
Post-migration administration . . . . . . . . . . . . Assigning IP addresses to the SIPI circuit packs Using static addressing. . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . Logging in to the SIPI . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . Resetting the SIPI . . . . . . . . . . . . . . . . . . Enabling control of the SIPI . . . . . . . . . . . . Verifying SIPI translations . . . . . . . . . . . . . Verifying SIPI connectivity . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . Troubleshooting the migration . . . . . . . . . . .
Migrating from a DEFINITY Server CSI in a CMC to an S8400 Media Server using Xmodem . . . . . . . . . . . . . . . . .
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
383
383 383
Issue 2.1 June 2006
17
Contents
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Removing netcon data modules . . . . . . Saving translations . . . . . . . . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Migration tasks. . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . Connecting to the SAT . . . . . . . . . . . Copying translation files . . . . . . . . . . Turning off power to all cabinets. . . . . . Removing circuit packs. . . . . . . . . . . Inserting circuit packs . . . . . . . . . . . Connecting cables . . . . . . . . . . . . . Replacing the TN799C C-LAN circuit pack Installing TN771 Maintenance/Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
384 384 390 392 392 393 394 394 394 395 395 395 396 396 396 397 397 397 398 398 399 399 399 401 401 402 403 403 403 403 404 405 406 407 408 408 409 409 409 410
Migrating translations . . . . . . . . . . . . . . . Installing the software load. . . . . . . . . . . Configuring the media server . . . . . . . . . Installing the license and authentication file . Copying translation files to the media server . Copying translation files to the media server . Closing all sessions. . . . . . . . . . . . . . .
Post-migration administration . . . . . . . . . . . . Assigning IP addresses to the SIPI circuit packs Using static addressing. . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . Logging in to the SIPI . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . Resetting the SIPI . . . . . . . . . . . . . . . . . . Enabling control of the SIPI . . . . . . . . . . . . Verifying SIPI translations . . . . . . . . . . . . . Verifying SIPI connectivity . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . .
Contents
Verifying the IP addresses . . . . . . . . . Checking the link status . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
410 410 411 411 411 412 412
Migrating from an IP600 or S8100 to an S8400 Media Server using ftp 413
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacement of INTUITY AUDIX Messaging with IA770 INTUITY AUDIX Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of IA770 INTUITY AUDIX Messaging software . . . . . . . . . . INTUITY AUDIX data that can be reused in IA770 INTUITY AUDIX Messaging and data that must be reinput. . . . . . . . . . . . . . . . . . . . . . . . . Removing unused INTUITY AUDIX ports or hunt groups . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Saving translations . . . . . . . . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Migration tasks. . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . Opening a SAT session . . . . . . . . . . . Copying translation files . . . . . . . . . . Opening an ftp session . . . . . . . . . . . Moving the translation files. . . . . . . . . Turning off power to all cabinets. . . . . . Removing circuit packs. . . . . . . . . . . Inserting circuit packs . . . . . . . . . . . Connecting cables . . . . . . . . . . . . . Replacing the TN799C C-LAN circuit pack Installing TN771 Maintenance/Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 413 414 414 415 415 416 416 421 423 424 424 424 425 425 425 426 426 426 427 427 427 428 428 428 429 429 430 430
Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting telnet parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
19
Contents
Installing the software load. . . . . . . . . . . Configuring the media server . . . . . . . . . Installing the license and authentication file . Copying translation files to the media server .
. . . .
. . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
430 431 432 432 433 434 434 435 435 436 437 438 438 439 439 439 440 440 440 441 441 441 442 442 442
Post-migration administration . . . . . . . . . . . . Assigning IP addresses to the SIPI circuit packs Using static addressing. . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . Logging in to the SIPI . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . Resetting the SIPI . . . . . . . . . . . . . . . . . . Enabling control of the SIPI . . . . . . . . . . . . Verifying SIPI translations . . . . . . . . . . . . . Verifying SIPI connectivity . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . Administering IA 770 INTUITY AUDIX Messaging. Testing the installation . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . Troubleshooting the migration . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . .
Chapter 5: Migrating to an Avaya S8500 Media Server . . . . . . . . .

Migrating from existing DEFINITY and Linux platforms. . . . . . . . . . . . . Migration paths for S8500 Media Servers . . . . . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server SI in an MCC . . . . . . . . . . . . . . . DEFINITY Server SI in an SCC . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC Avaya IP600/S8100 in a G600 . . . . . . . . . . . . . . . Prerequisites for migrating to an S8500 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
443
443 444 444 445 445 445 446 446 446
Migration modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating a DEFINITY Server CSI in a CMC to an S8500 Media Server 447

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 448
Contents
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
448 449 455 457 457 457 458 458 458 459 459 459 459 460 461 461 461 462 462 462 463 463 464 464 465 465 465 467 467 468 468 469 470 470 471 472 472 472 473 473
Migrating translations . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Copying translation files to media server . . . . . . . . . Restoring translation files . . . . . . . . . . . . . . . . . Administering the IPSIs . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . Setting the alarm activation level . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . Changing the control cabinet to a port network Turning off the power to the control cabinet . . Replacing the processor circuit pack . . . . . . Replacing the TN799C C-LAN circuit pack . . . Installing TN771 Maintenance/Test circuit pack Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Postmigration administration . . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
21
Contents
Verifying the IP addresses . . . . . . . . . Checking the link status . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
473 474 474 475 475 475 475
Migrating a DEFINITY Server SI Direct-Connect in an SCC to a Direct-Connect . . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
477
477 478 478 479 484 486 487 487 487 488 488 489 489 489 489 490 490 491 491 492 492 492 493 493 494 494 497 501 502 502
Migrating translations . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Verifying the license file . . . . . . . . . . . . . . . . . . Copying translation files to media server . . . . . . . . . Restoring translation files . . . . . . . . . . . . . . . . . Administering the IPSIs . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . Setting the alarm activation level . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . Removing the processor port network control cabinet Installing the expansion control carrier . . . . . . . . . Stacking the port media gateways . . . . . . . . . . . . Installing IPSI and maintenance circuit packs . . . . . Connecting the CAT5 cables to the IPSI circuit packs . Installing Expansion Interface circuit packs . . . . . . Turning on the media gateway . . . . . . . . . . . . . . . . . . . . . . .
Post-migration administration . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
502 504 504 505 506 506 508 508 509 510 510 510 511 511 511 512 512 513 513 513 513
Migrating a DEFINITY Server SI Direct-Connect in an MCC to a Direct-Connect . . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
515
515 516 516 517 523 525 526 526 526 527 527 527 528 528 528 529
Migrating translations . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Verifying the license file . . . . . . . . . . . . . . . . . . Copying translation files to media server . . . . . . . . . Restoring translation files . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
23
Contents
Administering the IPSIs . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager Setting the alarm activation level . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . Removing the processor port network control carrier Installing the expansion control carrier . . . . . . . . Installing IPSI and maintenance circuit packs . . . . Connecting the CAT5 cables to the IPSI circuit packs Installing Expansion Interface circuit packs . . . . . Turning on the media gateway . . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
529 530 530 531 531 531 531 532 533 535 535 536 536 536 537 538 538 539 539 541 541 542 543 543 543 544 544 544 545 545 546 546 546 546
Postmigration administration . . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . .
Migrating a DEFINITY ONE/S8100 to an S8500 Media Server . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
547
547 548 548 549
Contents
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . Recording IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
555 557 557 558 558 558 559 559 560 560 560 561 561 562 562 562 563 563 564 564 565 565 565 566 566 567 567 568 569 569 571 571 572 573 573 573 574 574 574 575
Migrating translations . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Verifying the license file . . . . . . . . . . . . . . . . . . Copying translation files to media server . . . . . . . . . Restoring translation files . . . . . . . . . . . . . . . . . Administering the IPSIs . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . Setting the alarm activation level . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . Changing the control cabinet to a port network Turning off the power to the control cabinet . . Replacing the processor circuit pack . . . . . . Replacing the TN799C C-LAN circuit pack . . . Installing TN771 Maintenance/Test circuit pack Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
25
Contents
Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
575 575 576 576
Migrating an Avaya IP600/S8100 to an S8500 Media Server . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . Recording IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
577
577 578 578 579 586 588 588 589 589 589 590 590 590 591 591 592 592 592 593 593 593 594 595 597 598 598 598 599 599 600 600 601 602 602
Migrating translations . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Verifying the license file . . . . . . . . . . . . . . . . . . Copying translation files to media server . . . . . . . . . Administering the IPSIs . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . Setting the alarm activation level . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . Changing the IP600 control chassis to a port network . Turning off the control chassis . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . Replacing the processor circuit pack . . . . . . . . . . Replacing the TN799C C-LAN circuit pack . . . . . . . Installing TN771 Maintenance/Test circuit pack . . . . Connecting to the media server . . . . . . . . . . . . . . . . . . . . . .
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . .
Contents
Setting the VLAN and diffserv parameters Resetting the IPSI . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . Enabling control of the IPSI . . . . . . . . Verifying the customer data . . . . . . . . Verifying circuit pack locations . . . . . . Verifying circuit pack insertion. . . . . . . Verifying the IP addresses . . . . . . . . . Checking the link status . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
604 604 605 606 606 606 607 607 607 607 608 609 609 609 609
Chapter 6: Migrating to an Avaya S8700-Series Media Server . . . . .

Migrating from existing DEFINITY and Linux platforms. . . . . . . . . . . . . Migration paths for S8700-Series Media Servers . . . . . . . . . . . . . . . . Migrating hardware . . . . . . . . . . . . . . . . . . . . . . DEFINITY Server R or SI in an MCC . . . . . . . . . . . . DEFINITY Server SI in an SCC . . . . . . . . . . . . . . . DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC Avaya IP600/S8100 in a G600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
611
611 612 612 612 613 614 614 614 615
Prerequisites for migrating to an S8700-Series Media Server . . . . . . . . . Migration modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating a DEFINITY Server CSI in a CMC to an S8700-Series Media Server with IP-PNC . . . . . . . . . . . . . . .
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the media server . . . . . . Verifying system status. . . . . . . . . . . Recording all busyouts . . . . . . . . . . . Recording node names and IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
617
617 618 618 619 628 630 630 631 631 631
Issue 2.1 June 2006
27
Contents
Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server . . . . . . . . . . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration (S8710 only). . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . Changing the IP600 control chassis to a port network Turning off the power to the control cabinet . . . . . . Replacing the processor circuit pack . . . . . . . . . . Replacing the TN799C C-LAN circuit pack . . . . . . . Installing TN771 Maintenance/Test circuit pack . . . . Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
632 632 632 633 633 633 635 636 636 637 637 637 638 638 638 639 639 640 640 640 640 642 642 643 643 644 645 645 646 647 647 647 648 648 648 649 649 650 650 650 650
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . .
Contents
Migrating from a DEFINITY Server SI in an SCC to an S8700-Series Media Server with Fiber-PNC . . . . . . . . . . . . .
Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . . . . Connecting to the processor . . . . . . . . . . . . . . . . . . . . Verifying system status. . . . . . . . . . . . . . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . Recording node names and IP addresses. . . . . . . . . . . . . Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading and administering the existing hardware . . . . . . Connecting the media server cables and the IPSI cables to the Ethernet switch . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the hardware in each port network . . . . . . . . . . Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs . . . . . . . . . . . . Determining IPSI placement in port networks . . . . . . . . . . Duplex-reliability configuration . . . . . . . . . . . . . . . . . . Setting up a high-reliability or critical-reliability configuration . Connecting the CAT5 cables to the IPSI circuit packs . . . . . . Installing Expansion Interface circuit packs . . . . . . . . . . . Completing circuit pack replacement . . . . . . . . . . . . . . . Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration (S8710 only). . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . Removing the processor port network control cabinet Installing the expansion control media gateway . . . . Stacking the port media gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
651
651 652 652 653 660 663 663 663 664 664 664 665 665 666 666 666 667 670 678 683 683 683 683 684 684 684 686 687 688 688 689 689 689 689 690 691
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
29
Contents
Installing IPSI and maintenance circuit packs . . . . . . . . . . . . . . . . Installing Expansion Interface circuit packs . . . . . . . . . . . . . . . . . Turning on the media gateway . . . . . . . . . . . . . . . . . . . . . . . . . Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using DHCP addressing . . . . . . . . . . . . . . . . . . . . . . . Administering the location assignment . . . . . . . . . . . . . . . Setting the switch ID . . . . . . . . . . . . . . . . . . . . . . . . . Setting the cabinet number. . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
691 691 692 692 692 694 694 694 695 696 696 697 697 698 698 698 698 699 699 700 700 700 700 700
Changing port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . .
Migrating a DEFINITY Server SI in an MCC to an S8700-Series Media Server with Fiber-PNC . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . Connecting to the processor . . . . . . . . . . . . . . Verifying system status. . . . . . . . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . Recording node names and IP addresses. . . . . . . Saving translations . . . . . . . . . . . . . . . . . . . Upgrading and administering the existing hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
701
701 702 702 703 710 712 712 713 713 713 714 714
Contents
Connecting the media server cables and the IPSI cables to the Ethernet switch . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the hardware in each port network . . . . . . . . . . Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs . . . . . . . . . . . . Determining IPSI placement in port networks . . . . . . . . . . Duplex reliability configuration . . . . . . . . . . . . . . . . . . High-reliability or critical-reliability configuration . . . . . . . . Connecting the CAT5 cables to the IPSI circuit packs . . . . . . Installing Expansion Interface circuit packs . . . . . . . . . . . Completing circuit pack replacement . . . . . . . . . . . . . . . Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration . . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . . . . Removing the processor port network control carrier . . . . Installing the expansion control carrier and the port carrier. Installing IPSI and maintenance circuit packs . . . . . . . . Connecting the CAT5 cables to the IPSI circuit packs . . . . Installing Expansion Interface circuit packs . . . . . . . . . Turning on the media gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
715 715 716 716 717 720 722 723 723 723 724 724 724 725 727 727 727 728 728 729 729 729 730 731 731 731 732 732 732 734 734 734 735 736 736 737 737 738 738
Post-migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using DHCP addressing . . . . . . . . . . . . . . . . . . . . . . . Administering the location assignment . . . . . . . . . . . . . . . Setting the switch ID . . . . . . . . . . . . . . . . . . . . . . . . . Setting the cabinet number. . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
31
Contents
Verifying circuit pack insertion. . . . . . . Verifying the IP addresses . . . . . . . . . Checking the link status . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
738 738 739 739 740 740 740 740 740
Changing port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . .
Migrating a DEFINITY Server R to an S8700-Series Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . From a magneto optical disk . . . . . . . . . . . . . . . . . . . . . . . . . Ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-level overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPSI placement decisions . . . . . . . . . . . . . . . . . . . . . . . . Installing and configuring the S8700-Series Media Server complex . Transferring existing translations . . . . . . . . . . . . . . . . . . . . Replacing expansion interface and maintenance circuit packs, if necessary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the tone clocks with TN2312BP IPSI circuit packs in the expansion port networks and the processor port network (optional) Converting the processor port network to a port network . . . . . . Cutting over to S8700-Series Media Server control . . . . . . . . . . Completing the migration . . . . . . . . . . . . . . . . . . . . . . . . Testing the S8700-Series configuration . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . Connecting to the processor . . . . . . . . . Verifying administration and system status. Recording all busyouts . . . . . . . . . . . . Recording node names and IP addresses. . Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
741
741 742 742 743 743 743 744 754 757 758 758 759 759 760 760 761 761 762 762 762 763 763 764 764 765 765
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . . .
Contents
Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Transferring translations . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . Copying translation files from the MO disk to the active S8700-Series Media Server . . . . . . . . . . . . . . . . . . . . Disconnecting from the active media server . . . . . . . . . . . Connecting to the standby media server . . . . . . . . . . . . . Disconnecting from the standby media server . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . Installing the translations. . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration . . . . . . . . . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . Upgrading and administering the existing hardware . . . . . . Connecting the media server cables and the IPSI cables to the Ethernet switch . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the hardware in each port network . . . . . . . . . . Duplex reliability configuration . . . . . . . . . . . . . . . . . . High-reliability or critical-reliability configuration . . . . . . . . Connecting the CAT5 cables to the IPSI circuit packs . . . . . . Installing Expansion Interface circuit packs . . . . . . . . . . . Completing circuit pack replacement . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . . . . Removing the processor port network control carrier(s) . . Installing the expansion control carrier and the port carrier. Installing IPSI and maintenance circuit packs . . . . . . . . Connecting the CAT5 cables to the IPSI circuit packs . . . . Installing Expansion Interface circuit packs . . . . . . . . . Turning on the media gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
765 765 766 766 766 766 767 767 769 770 770 770 770 771 773 774 775 775 776 776 777 777 779 782 785 785 785 785 786 786 787 788 788 788 789 789 789 791 791
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using DHCP addressing . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
33
Contents
Administering the location assignment . . Setting the switch ID . . . . . . . . . . . . Setting the cabinet number. . . . . . . . . Verifying IPSI translations . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . Enabling control of the IPSI . . . . . . . . Verifying the customer data . . . . . . . . Verifying circuit pack locations . . . . . . Verifying circuit pack insertion. . . . . . . Verifying the IP addresses . . . . . . . . . Checking the link status . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . Testing the installation . . . . . . . . . . . Busying out previously busied out trunks Troubleshooting the migration . . . . . . . Returning replaced equipment . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
791 792 793 793 794 794 795 795 795 795 796 796 797 797 797 797
Migrating a DEFINITY ONE/S8100 to an S8700-Series Media Server with IP-PNC . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . Connecting to the processor . . . . . . . . Recording node names and IP addresses. Saving translations . . . . . . . . . . . . . Recording IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
799
799 799 800 801 810 812 812 812 813 813 814 814 814 814 815 817 817 818 818 818 819
Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration (S8710 only). . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . .
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Verifying hardware . . . . . . . . . . . . . . . . Changing the control cabinet to a port network Turning off the power to the control cabinet . . Replacing the processor circuit pack . . . . . . Replacing the TN799C C-LAN circuit pack . . . Installing TN771 Maintenance/Test circuit pack Connecting to the media server . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
819 819 820 820 821 821 822 822 822 823 824 824 825 826 827 827 828 829 829 829 830 830 830 831 831 832 832 832 832
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . Busying out previously busied out trunks . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . .
Migrating an Avaya IP600/S8100 to an S8700-Series Media Server with IP-PNC . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the processor . . . . . . . . . . . . . . . . . . . . . . . . . . Recording node names and IP addresses. . . . . . . . . . . . . . . . . . .
833
833 833 834 835 844 846 847 847
Issue 2.1 June 2006
35
Contents
Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recording IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . Checking system status . . . . . . . . . . . . . . . . . . . . . . Verifying the license file . . . . . . . . . . . . . . . . . . . . . . Restoring data for a migration (S8710 only). . . . . . . . . . . . Adding IPSI translations to Communication Manager . . . . . . Adding IPSI information . . . . . . . . . . . . . . . . . . . . . . Setting IPSI duplication (high-reliability critical-reliability only) Setting the alarm activation level . . . . . . . . . . . . . . . . . Backing up translations . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . Changing the IP600 control chassis to a port network Turning off the control chassis . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . Replacing the processor circuit pack . . . . . . . . . . Replacing the TN799C C-LAN circuit pack . . . . . . . Installing TN771 Maintenance/Test circuit pack . . . . Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
848 848 849 849 849 849 850 852 852 853 853 853 854 854 854 855 855 858 858 859 859 859 859 861 861 862 862 863 864 864 865 866 866 866 867 867 867 868 868 869
Post-migration administration . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Assigning IP addresses to the IPSI circuit packs . . . . . . . . . Using static addressing. . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Logging in to the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . Setting the control interface . . . . . . . . . . . . . . . . . . . . . Setting the VLAN and diffserv parameters . . . . . . . . . . . . . Resetting the IPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . Enabling control of the IPSI . . . . . . . . . . . . . . . . . . . . . Verifying the customer data . . . . . . . . . . . . . . . . . . . . . Verifying circuit pack locations . . . . . . . . . . . . . . . . . . . Verifying circuit pack insertion. . . . . . . . . . . . . . . . . . . . Verifying the IP addresses . . . . . . . . . . . . . . . . . . . . . . Checking the link status . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . Testing the installation . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Busying out previously busied out trunks . . . . . . . . . . . . . . . . . . Troubleshooting the migration . . . . . . . . . . . . . . . . . . . . . . . . . Returning replaced equipment . . . . . . . . . . . . . . . . . . . . . . . . .
869 869 869
Migrating an S8500 Media Server to an S8710 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . . . Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used) . . . . . . . . . . . Upgrading firmware . . . . . . . . . . . . . . . . . . . . . Upgrading software on the local survivable processors . On the S8500 Media Server . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . Connecting to the media server . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . Saving translations . . . . . . . . . . . . . . . . . Backing up the translation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
871
871 871 873 874 874 874 875 875 876 876 876 877 877 877 877 878 878 878 878 879 880 882 883 883 884 884 884 885 886 886 886 886
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
On active S8710 Media Server . . . . . . . . . . . . . . . . . . . . . Turning on both media servers . . . . . . . . . . . . . . . . . . . Accessing the media server . . . . . . . . . . . . . . . . . . . . . Setting up a Telnet session. . . . . . . . . . . . . . . . . . . . . . Installing Communication Manager . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. Accessing the media server . . . . . . . . . . . . . . . . . . . . . Configuring both media servers using AIW . . . . . . . . . . . . . On the S8710 Media Servers . . . . . Connecting customer LAN cables . Restoring the translations . . . . . Pretesting the system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
On the S8500 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting the S8500 Media Server from the customer network . . . . On the S8710 Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting the S8710 Media Servers to the control network . . . . . . . .
Issue 2.1 June 2006
37
Contents
On the S8500 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting down the S8500 Media Server . . . . . . . . . . . . . . . . . . . . Disconnecting the cables. . . . . . . . . . . . . . . . . . . . . . . . . . . .
887 887 888
Migrating from an S8700 Media Server to an S8710 Media Server .

Basic Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . . . Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used) . . . . . . . . . . . . . Upgrading software on the local survivable processors . . . Upgrading firmware on media gateways and media modules . Verifying hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
889
889 890 891 898 900 900 901 902 902 902 902 902 903 904 904 904 905 905 905 906 906 906 907 908 909 909 909 910 910 910 911 911 912
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On the active S8700 Media Server . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Clearing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . . Checking clock synchronization . . . . . . . . . . . . . . . . . . . . Disabling scheduled maintenance . . . . . . . . . . . . . . . . . . . Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) . . . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . . Checking the software release . . . . . . . . . . . . . . . . . . . . . Backing up the Linux migration upgrade set to the network . . . . Backing up the Linux migration upgrade set to the services laptop Recording the Product ID. . . . . . . . . . . . . . . . . . . . . . . .
On the standby S8700 Media Server . . . . . . . . . . . . . . . . . . . . . . . Accessing the standby S8700 Media Server . . . . . . . . . . . . . . . . . Shutting down the S8700 Media Server . . . . . . . . . . . . . . . . . . . . On the first S8710 Media Server . . . . . . . . . . . . . . Turning on the media server . . . . . . . . . . . . . . . Accessing the media server . . . . . . . . . . . . . . . Configuring Telnet for Windows 2000 or Windows XP . Installing Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Accessing the server command line interface with SSH protocol. . . Using PuTTY to reaccess the media server . . . . . . . . . . . . . . . Checking the software version . . . . . . . . . . . . . . . . . . . . . . Changing the date and the time . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . . Configuring the network parameters . . . . . . . . . . . . . . . . . . Verifying connectivity to the network server . . . . . . . . . . . . . . Installing the new license file and the Avaya authentication file . . . Restoring the Linux migration upgrade set from the network . . . . . Downloading the license file and the Avaya authentication file . . . . Selecting the media server type . . . . . . . . . . . . . . . . . . . . . Restoring the Linux migration upgrade set from the services laptop . Installing software update . . . . . . . . . . . . . . . . . . . . . . . . Verifying the software update installation. . . . . . . . . . . . . . . . Verifying the media server configuration . . . . . . . . . . . . . . . . On the second S8710 Media Server . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. . . Installing Communication Manager and restoring files . . . . . . . . Installing the new license file and the Avaya authentication file . . . Restoring the Linux migration upgrade set from the network . . . . . Restoring the Linux migration upgrade set from the services laptop . Installing software updates, if any . . . . . . . . . . . . . . . . . . . . Verifying media server configuration . . . . . . . . . . . . . . . . . . Transferring system control to the S8710 Media Servers . . . Moving Ethernet cables. . . . . . . . . . . . . . . . . . . . Moving cables to the S8710 Media Server (media server 1) Releasing the media server. . . . . . . . . . . . . . . . . . Moving cables to the S8710 Media Server (media server 2) Completing the cable migration . . . . . . . . . . . . . . . On the standby S8710 Media Server . . . . . . . . Accessing the standby media server . . . . . . Pinging all the connections to the media server Backing up files on the media server . . . . . . Releasing alarm suppression (optional). . . . . Setting the Product ID . . . . . . . . . . . . . . Logging off all administration applications . . . Disconnecting from the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
913 915 915 915 915 916 917 918 918 919 920 921 922 923 923 923 924 925 925 926 927 927 927 927 927 928 928 928 929 929 929 929 930 930 930 930 931 931 931 931
On the active S8710 Media Server . . . . . . . . . . . . . . . . . . . . . . . . Accessing the active media server . . . . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
39
Contents
Backing up files on the media server . . . . . . . . Releasing alarm suppression (optional). . . . . . . Setting the Product ID . . . . . . . . . . . . . . . . Logging off all administration applications . . . . . Disconnecting from the media server . . . . . . . . Registering the system . . . . . . . . . . . . . . . . Removing customer files from the services laptop.
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
932 932 932 932 932 933 933
Migrating from an S8700 or S8710 Media Server to an S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks checklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Premigration administration . . . . . . . . . . . . . . . . . . . . . . . Upgrading H.248 media gateways, LSPs, and ESSs (if being used) Upgrading software on the local survivable processors . . . . . . Upgrading firmware on media gateways and media modules . . . . Verifying hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Enterprise Survivable Servers . . . . . . . . . . . . . . . . . Using local survivable processors. . . . . . . . . . . . . . . . . . . On the active S8700 or S8710 Media Server . . . . . . . . . . . . . . Configuring Telnet for Windows 2000 or WindowsXP . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . Checking the software release . . . . . . . . . . . . . . . . . . . . Clearing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . Recording all busyouts . . . . . . . . . . . . . . . . . . . . . . . . Checking clock synchronization . . . . . . . . . . . . . . . . . . . Disabling scheduled maintenance . . . . . . . . . . . . . . . . . . Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) . . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . Saving translations . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the CNC status . . . . . . . . . . . . . . . . . . . . . . . Recording the server connection type. . . . . . . . . . . . . . . . Backing up the active S8700 or S8710 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
935
935 937 937 942 947 947 947 948 948 948 948 948 949 949 949 950 953 953 953 954 954 954 955 955 956 956 957 957 958
Migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Obtaining the Product ID on the active S8700 or S8710 Media Server . . . Looking up server configuration information on the active S8700 or S8710 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnecting from the active S8700 or S8710 Media Server . . . . . . . . On the standby S8700 or S8710 Media Server . . . . . . . . . . . . . . . . Checking the software release . . . . . . . . . . . . . . . . . . . . . . . Clearing the ARP cache on the laptop computer . . . . . . . . . . . . . Connecting to the standby S8700 or S8710 Media Server . . . . . . . . Accessing the standby S8700 or S8710 Media Server . . . . . . . . . . Checking the CNC status . . . . . . . . . . . . . . . . . . . . . . . . . . Recording the server connection type. . . . . . . . . . . . . . . . . . . Backing up the standby S8700 or S8710 Media Server. . . . . . . . . . Obtaining the Product ID on the standby S8700 or S8710 Media Server Looking up server configuration information on the standby S8700 or S8710 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . Busying out the standby S8700 or S8710 Media Server . . . . . . . . . Shutting down the standby S8700 or S8710 Media Server . . . . . . . . Removing the duplication cables . . . . . . . . . . . . . . . . . . . . . Removing the standby S8700 or S8710 Media Server from the rack . . Removing the DAL1 card, if necessary . . . . . . . . . . . . . . . . . . On first S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . Installing the DAL1 card in the S8720 Media Server, if necessary. . Installing the first S8720 Media Server in the rack . . . . . . . . . . Inserting the Communication Manager software distribution CD . . Connecting the cables to the first S8720 Media Server . . . . . . . Accessing the first S8720 Media Server . . . . . . . . . . . . . . . . Installing Communication Manager . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. . Accessing the media server maintenance web interface. . . . . . . Checking the software version . . . . . . . . . . . . . . . . . . . . . Verifying date and time . . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server (if any) . . . . . . . . . . . . . . . Activating the software update (if any) . . . . . . . . . . . . . . . . Stopping Communication Manager on the first S8720 Media Server Configuring to allow restoring configuration data and translations from the ftp server on the network . . . . . . . . . . . . . . . . . . Configuring to allow restoring configuration data and translations from flash card or Services laptop . . . . . . . . . . . . . . . . . . Verifying connectivity from the first S8720 Media Server to the network server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring configuration data and translations to the first S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
965 965 966 966 966 967 967 967 968 968 968 976 976 977 977 978 978 978 980 980 982 982 983 986 986 987 989 989 989 990 990 991 991 992 993 993
. . . . . . . . . . . . . . . .
Issue 2.1 June 2006
41
Contents
Verifying the first S8720 Media Server configuration. . . . . . Rebooting the first S8720 Media Server . . . . . . . . . . . . . Accessing the first S8720 Media Server . . . . . . . . . . . . . Confirming the product ID on the first S8720 Media Server . . Enabling CNC, if necessary . . . . . . . . . . . . . . . . . . . Initializing Communication Manager. . . . . . . . . . . . . . . Performing an integrity check on the first S8720 Media Server
. . . . . . .
. . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
996 998 998 998 999 999 999 1000 1000 1001 1001 1002 1002 1002 1003 1003 1003 1005 1005 1007 1007 1007 1010 1011 1012 1013 1013 1013 1014 1014 1015 1016 1017 1017 1020 1021 1022
Making the first S8720 Media Server active . . . . . . . . . . . . . . Shutting down the active S8700 or S8710 Media Server . . . . . . Accessing the first S8720 Media Server . . . . . . . . . . . . . . . Releasing the first S8720 Media Server . . . . . . . . . . . . . . . Verifying the first S8720 Media Server is active. . . . . . . . . . . Installing the license and authentication files. . . . . . . . . . . . Verifying connectivity between the first S8720 Media Server and port networks, LSPs, and ESSs. . . . . . . . . . . . . . . . . . .
. . . . .
Removing the remaining S8700 or S8710 Media Server . . . . . . . . . . . . Removing the S8700 or S8710 Media Server from the rack . . . . . . . . . Removing the DAL1 card, if necessary . . . . . . . . . . . . . . . . . . . . On the second S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . Installing the DAL1 card in the S8720 Media Server, if necessary. . . . . Installing the second S8720 Media Server in the rack . . . . . . . . . . . Inserting the Communication Manager software distribution CD . . . . . Connecting the cables to the second S8720 Media Servers . . . . . . . . Accessing the media server . . . . . . . . . . . . . . . . . . . . . . . . . Installing Communication Manager . . . . . . . . . . . . . . . . . . . . . Accessing the second S8720 Media Server . . . . . . . . . . . . . . . . . Checking the software version . . . . . . . . . . . . . . . . . . . . . . . . Verifying date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the second S8720 Media Server (if any). . . . . . . . . . Activating the software update (if any) . . . . . . . . . . . . . . . . . . . Stopping Communication Manager on the second S8720 Media Server . Configuring to allow restoring configuration data and translations from the ftp server on the network . . . . . . . . . . . . . . . . . . . . . Configuring to allow restoring configuration data and translations from flash card or Services laptop . . . . . . . . . . . . . . . . . . . . . . . . Verifying connectivity to the network server . . . . . . . . . . . . . . . . Restoring configuration data and translations to the second S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the second S8720 Media Server configuration . . . . . . . . . . Rebooting the second S8720 Media Server . . . . . . . . . . . . . . . . . Accessing the second S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Confirming the product ID on the first S8720 Media Server . . . . Enabling CNC, if necessary . . . . . . . . . . . . . . . . . . . . . Initializing Communication Manager. . . . . . . . . . . . . . . . . Performing an integrity check on the second S8720 Media Server Connecting the duplication cables. . . . . . . . . . . . . . . . . . Releasing the second S8720 Media Server . . . . . . . . . . . . . Verifying the second S8720 Media Server is in standby state . . . Releasing alarm suppression (optional). . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . . Disconnecting from the second S8720 Media Server. . . . . . . . On the active (first) S8720 Media Server . . . . . . . . Accessing the active media server . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . Enabling scheduled maintenance . . . . . . . . . . Saving translations . . . . . . . . . . . . . . . . . . Backing up files on the active S8720 Media Server. Releasing alarm suppression (optional). . . . . . . Logging off all administration applications . . . . . Disconnecting from the active S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
1022 1022 1022 1023 1024 1026 1027 1027 1027 1027 1028 1028 1028 1028 1029 1029 1029 1029 1029 1030 1030 1030 1030 1031 1031 1031 1031 1031 1031 1032 1032 1032 1033 1033 1034
On the standby S8720 Media Server . . . . . . . . . . . Accessing the standby media server . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . Backing up files on the standby S8720 Media Server Releasing alarm suppression (optional). . . . . . . . Logging off all administration applications . . . . . . Disconnecting from the standby media server . . . .
Completing the migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing customer files from the Services laptop . . . . . . . . . . . . . Interchanging media servers (optional) . . . . . . . . . . . . . . . . . Accessing the standby media server . . . . . . . . . . . . . . . . . Interchanging media servers (optional) . . . . . . . . . . . . . . . . Performing an integrity check on the active S8720 Media Server . . Upgrading H.248 media gateways, LSPs, and ESSs (if being used) Upgrading software on the local survivable processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is covered in the Conversions Section . . . . . . . . . . . . . . . . . What is not covered in the Conversions Section . . . . . . . . . . . . . . . 1035 1036 1036
Issue 2.1 June 2006
43
Contents
Common conversion prerequisites . . . . . . . . . . . . . . Presite checklist. . . . . . . . . . . . . . . . . . . . . . . . License and authentication files . . . . . . . . . . . . . . . Generating and retrieving license and authentication files Logins and passwords . . . . . . . . . . . . . . . . . . . . Additional documentation . . . . . . . . . . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
1037 1037 1039 1040 1040 1040
Chapter 7: Converting PNs to IP-PNC . . . . . . . . . . . . . . . . . . 1041

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating IP-PNC PNs with fiber-PNC configurations Media gateway combinations . . . . . . . . . . . . . . Reliability levels . . . . . . . . . . . . . . . . . . . . . Dedicated and nondedicated control networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041 1042 1043 1044 1046
Converting some or all direct-connect port networks to IP-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

Introduction . . . . . . . . . . . The starting configuration . . The converted configuration . Configuration diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047 1047 1048 1048 1049 1049 1049 1049 1050 1050 1050 1051 1051 1051 1052 1052 1053 1053 1055 1062 1063 1063 1065 1066
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . Before you go on site . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Starting a SAT session . . . . . . . . . . . . . . . . . . .
Preconversion tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling scheduled maintenance with the SAT (main server only) Backing up recovery system files . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . Conversion Tasks . . . . . . . . . . . . . . . . . . . . . . . Conversion tasks checklist. . . . . . . . . . . . . . . . . Changing direct-connect synchronization, if necessary Adding new circuit packs. . . . . . . . . . . . . . . . . . Setting the VLAN parameters and diffserv parameters. . Verifying IPSI translations . . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . Upgrading firmware on the new circuit packs . . . . . . Disabling PNC duplication, if necessary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Removing fiber-related administration . . . . . . Enabling PNC duplication, if necessary . . . . . . Removing fiber-related hardware . . . . . . . . . Administering PN synchronization, if necessary .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
1066 1066 1067 1067 1069 1069 1069 1069 1069 1070 1070 1070 1071 1075 1075
Postconversion tasks . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . .
Configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Converting some or all CSS port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079

Introduction . . . . . . . . . . . The starting configuration . . The converted configuration . Configuration Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079 1079 1080 1080 1081 1081 1081 1081 1082 1082 1082 1083 1083 1084 1084 1085 1085 1086 1088 1095 1096 1096
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . Presite assumptions . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. Starting a SAT session . . . . . . . . . . . . . . . . . . . Preconversion tasks . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . Backing up recovery system files . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . Conversion Tasks . . . . . . . . . . . . . . . . . . . . . . Conversion tasks checklist. . . . . . . . . . . . . . . . Changing CSS synchronization, if necessary . . . . . Adding new circuit packs. . . . . . . . . . . . . . . . . Setting the VLAN parameters and diffserv parameters. Verifying IPSI translations . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . . . . . . . .
Issue 2.1 June 2006
45
Contents
Upgrading firmware on the new circuit packs . . . . . . Disabling PNC duplication, if necessary . . . . . . . . . Removing fiber-related administration . . . . . . . . . . Enabling PNC duplication, if necessary . . . . . . . . . . Removing fiber-related hardware . . . . . . . . . . . . . Refreshing the switch-node clock memory, if necessary Administering PN synchronization, if necessary . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
1098 1098 1099 1099 1099 1100 1101 1103 1103 1103 1103 1104 1104 1104 1105 1105 1112 1112
Post-conversion tasks. . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . .
Configuration Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Converting some or all ATM port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115

Introduction . . . . . . . . . . . The starting configuration . . The converted configuration . Configuration Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115 1115 1116 1116 1116 1117 1117 1117 1118 1118 1118 1119 1119 1119 1120 1120 1121 1121 1121
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presite assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . Preconversion tasks . . . . . . . . . . . . . . . . . . . . . . . . . . Copying files to the media server . . . . . . . . . . . . . . . . . . . Verifying software operation . . . . . . . . . . . . . . . . . . . . . . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for translation corruption . . . . . . . . . . . . . . . . . . Disabling scheduled maintenance with the SAT (main server only) Backing up recovery system files . . . . . . . . . . . . . . . . . . . Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . .
Conversion Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conversion tasks checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . Changing ATM synchronization, if necessary . . . . . . . . . . . . . . . .
Contents
Adding new circuit packs. . . . . . . . . . . . . . . . . Setting the VLAN parameters and diffserv parameters. Verifying IPSI translations . . . . . . . . . . . . . . . . Verifying IPSI connectivity . . . . . . . . . . . . . . . . Upgrading firmware on the new circuit packs . . . . . Disabling PNC duplication, if necessary . . . . . . . . Removing fiber-related administration . . . . . . . . . Enabling PNC duplication, if necessary . . . . . . . . . Removing fiber-related hardware . . . . . . . . . . . . Administering PN synchronization, if necessary . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
1123 1130 1131 1131 1133 1133 1134 1134 1134 1135 1136 1136 1136 1137 1137 1137 1138 1138 1138 1143 1143
Post-conversion tasks. . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . . . . . . Enabling scheduled maintenance with SAT. . . . . . . . . . . . . Checking for translation corruption with SAT (main server only) . Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up recovery system files on the active server . . . . . . Releasing alarm suppression (optional) . . . . . . . . . . . . . . Logging off all administration applications . . . . . . . . . . . . .
Configuration Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8: Converting the Media Server Mode . . . . . . . . . . . . . 1147 Converting S8300 LSP mode to ICC mode . . . . . . . . . . . . . . 1149
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before going to the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the customer site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149 1150 1151
Converting S8300 ICC mode to LSP mode . . . . . . . . . . . . . . 1157

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before going to the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the customer site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157 1158 1159
Installing or converting to an S8500 LSP . . . . . . . . . . . . . . . 1165

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the hardware (new installation only) . . . . . . Clearing the ARP cache on the laptop computer . . . . . Connecting the laptop and turning on the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 1166 1167 1167 1167
Issue 2.1 June 2006
47
Contents
Configuring the SNMP modules in the UPS . . . . . . . . . . . . . . . . Configuring the SNMP subagent in the Avaya Ethernet switch . . . . . Disabling the boot timeout of the SAMP board (S8500B upgrade only). Installing Avaya Communication Manager . . . . . . . . . . . . . . . . Configuring the S8500 LSP . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the RMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SAMP software update, if necessary . . . . . . . . . . . . . . Configuring the modem. . . . . . . . . . . . . . . . . . . . . . . . . . . Administering the new primary controller. . . . . . . . . . . . . . . . . Enable license server capability on a media gateway, if necessary . . . Install and verify the license on the new LSP . . . . . . . . . . . . . . . Opening the TCP ports on the S8500 LSP. . . . . . . . . . . . . . . . . Connect the new S8500 LSP to the LAN/WAN . . . . . . . . . . . . . . Reset the S8500 LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify that the primary controller identifies the new LSP and has sent the translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Readminister the desired media gateways to point to the LSP . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
1168 1168 1168 1169 1171 1172 1173 1174 1174 1176 1176 1177 1179 1179 1179 1180
. . . .
Converting IP-PNC port networks with simplex control to duplicated control . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preconversion assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and cabling a second Ethernet switch, if necessary . . . . . Configuring the SNMP subagent in the Avaya Ethernet switch (if used) Enabling firewall settings, if necessary . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . Configuring Control Network B . . . . . . . . . . . . . . . . . . . . . . Designating the slot for the duplicated IPSI circuit pack. . . . . . . . . Installing the duplicated IPSI circuit pack . . . . . . . . . . . . . . . . . Adding control network cabling for the new circuit pack . . . . . . . . Verifying the IPSI circuit packs are inserted properly . . . . . . . . . . Programming the duplicated IPSI circuit pack . . . . . . . . . . . . . . Starting a SAT session . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering the duplicated IPSI circuit pack on the media server . . Verifying IPSI translations . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading IPSI firmware, if necessary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181 1181 1182 1182 1183 1185 1186 1186 1188 1189 1197 1197 1197 1199 1199 1200 1200
Contents
Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only) . . . . . . . 1201
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicated control network. . . . . . . . . . . . . . . . . . . Overflow with coresident TN2302AP circuit packs . . . . . . Reduced channels with duplicated TN2602AP circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201 1201 1202 1202 1202 1204 1205 1205 1206 1206 1207 1208 1208 1209 1209 1210 1211 1211 1211 1213 1213 1214 1217 1217 1219 1219
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checklist for converting a port network to duplicated TN2602AP IP Media Resource 320 circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . Instructions for converting a port network to duplicated TN2602AP IP Media Resource 320 circuit packs . . . . . . . . . . . . . . Checking your shipment, if not reusing existing TN2602AP circuit packs . Accessing the media server maintenance web interface. . . . . . . . . . . Accessing the server command line interface with SSH protocol. . . . . . Checking software release . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the existence and location of TN2302 and TN2602AP circuit packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading firmware on the existing TN2602AP circuit packs, if necessary Disabling an existing TN2602AP circuit pack or TN2302 circuit packs . . . Removing the TN2302 circuit pack hardware . . . . . . . . . . . . . . . . . Connecting the cables to any new TN2602AP circuit packs . . . . . . . . . Installing the TN2602AP circuit packs, if new . . . . . . . . . . . . . . . . . Installing the TN771DP Maintenance Test circuit pack . . . . . . . . . . . . Verifying installation and voice channels . . . . . . . . . . . . . . . . . . . Upgrading firmware on the new TN2602AP circuit packs, if necessary. . . Administering the node name for the TN2602AP circuit pack, if necessary Administering the IP interface for the TN2602AP circuit packs . . . . . . . Testing the external connection to the LAN . . . . . . . . . . . . . . . . . Verifying active call status . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing I/O cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Converting software duplication link to a DAL1 link on an S8720 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
Before you start . . . . . . . . . . . . . . Removing power from the server(s) . . . Removing the server from the rack . . . Removing the top cover from the server Removing the riser assembly . . . . . . Inserting the DAL1 circuit pack . . . . . Replacing the riser assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223 1224 1225 1226 1226 1227 1228
Issue 2.1 June 2006
49
Contents
Replacing the cover on the server . . . . . . . . . . . . . Replacing the server in the rack . . . . . . . . . . . . . . Restoring power to the server(s). . . . . . . . . . . . . . Connecting to the active media server . . . . . . . . . . Accessing the media server maintenance web interface. Reconnecting the duplication cables . . . . . . . . . . . Reconfiguring the Ethernet interface . . . . . . . . . . . Checking system status . . . . . . . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
1230 1230 1231 1232 1232 1233 1234 1235
Appendix A: Accessing the media server . . . . . . . . . . . . . . . . 1237

Connecting to the media server directly . . . . . . . . . . . . . . . . . . . . 1237 1241 1242 1242 1243 1243 1244 1244 1245 1245 1246 1246 1248 1249 1250 1250 1250 Connecting the G700 Media Gateway directly . . . . . . . . . . . . . . . . . . Computer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the media server remotely over the network . . . . . . . . . . Connecting to the media server remotely over a modem . . . . . . . . . Setting up a dial-up connection . . . . . . . . . . . . . . . . . . . . . . Dialing up to the media server . . . . . . . . . . . . . . . . . . . . . . . Finding the IP address of the active media server (duplicated servers) . . . . . . . .
Accessing the Maintenance Web Interface . . . . . . . . . . . . . . . . . . . Using the command line interface . . . . . . . . . . . . . . . . . . . . . . . . Accessing the server command line interface with SSH protocol. . . . . . Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browser settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting directly to the media server. . . . . . . . . . . . . . . . . . . . Connecting remotely through the network . . . . . . . . . . . . . . . . . .
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
Port network connectivity
Chapter 1: Introduction
This document describes procedures for upgrades, migrations, and conversions of Avaya telecommunications products that use the Avaya Communications Manager software application.
An upgrade is an installation of a newer release of software on a media server or a newer version of firmware on a hardware component. Components include media gateways, media modules, Ethernet switches, and programmable circuit packs. For more information on upgrades and upgrade paths, see Upgrades on page 63.
A migration is a change in hardware. The types of migration include migrating a non-Linux-based switch to a Linux-based media server, migrating a Linux-based media server to a different Linux-based media server; and migrating a media gateway to a different media gateway. A migration is usually accompanied by an upgrade. For more information on migrations and migration paths, see Migrations on page 297.
A conversion is a change in function or mode, reliability, or connectivity of various hardware components. Components include media servers and media gateways. A conversion may be preceded by a migration and may include an upgrade. For more information on conversions, see Conversions on page 1035
Port network connectivity

Port networks are connected to each other either by an IP connection or a fiber connection. IP connections use CAT-5 (category 5) or better Ethernet cables to connect port networks to an IP network for the transmission of bearer (voice) traffic. Both the control traffic and the bearer traffic are provided over the IP network. Fiber connections are sometimes called multiconnect connections. These connections use fiber-optic cables to connect port networks for the transmission of bearer traffic. The three types of fiber connections are direct connect, center stage switch (CSS), and asynchronous transfer mode (ATM). Direct connect is a special case of fiber connection in which fiber-optic cables connect two or three port networks without the use of a CSS or an ATM switch. A configuration can include Internet Protocol port network connectivity (IP-PNC) and fiber port network connectivity (fiber-PNC) port networks. Migrations and conversions can often result in this combination of port network connectivity.
Issue 2.1 June 2006
51
Introduction
Reliability and availability

The reliability of a telecommunications system is defined by the extent of duplication of certain components. The traditional standard, high, and critical reliability levels apply to the pre-Linux-based switches. For Linux-based media servers, the standard reliability level is expanded to include simplex for S8500 media servers and duplex for S8700-Series media servers. The availability of a telecommunications system is the time the system is ready and able to process calls as a percentage of the scheduled time. Availability depends on reliability. Release 3.1 introduced the ability to combine types of port network connectivity (PNC) and to apply reliability designations separately to the IP-PNC portion and the fiber-PNC portion of the system. The reliability level is defined per port network for the IP-PNC portion and collectively for the fiber-PNC portion. Therefore, combined PNC systems can have combined reliabilities. For pure IP-PNC configurations, the reliability designation is also per port network. Release 3.1 introduced the ability to add, to an IP-PNC port network, duplicated bearer reliability, in addition to duplicated control reliability, which together constitute critical reliability. Note: Duplicated bearer can be implemented without duplicated control for both the S8500 and S8700-series Media Servers. Unlike previous releases, duplicated control is not a prerequisite for duplicated bearer.
Note:
Table 1 and Table 2 summarize reliability levels for systems with Linux-based media servers. Reliability definitions for pre-Linux-based CSI switch are unchanged.
Reliability and availability
Note:
Note: The terms control and bearer mean control network and bearer network, respectively. More detailed definitions of reliability levels, including the circuit packs involved, are given in the Hardware Description and Reference for Avaya Communication Manager, 555-245-207.
Table 1: Reliability levels (per system) for Linux-based systems SImplex S8500
(pre-3.0 releases)

Duplex
High
Critical
one server single control single bearer

NA
NA
NA
S87xx
fiber-PNC (all releases) NA
two servers single control single bearer two servers single control single bearer
two servers duplicated cc control single bearer two servers duplicated c control single bearer
two servers duplicated control duplicated bearer NA
S87xx
IP-PNC (pre-3.1 releases) NA
Table 2: Reliability levels (per PN) for Release 3.1 Linux-based systems Duplex
S87xx IP-PNC (Release 3.1 and later)

High

Critical two servers duplicated control single bearer

two servers single control single bearer
two servers duplicated control duplicated bearer
For more information on conversions, see Conversions on page 1035.
Issue 2.1 June 2006
53
Introduction
Resources
To help with the procedures in this book, you might need to refer to the following books. Here is a list of books contained on the Documentation for Avaya Communication Manager 3.1, Media Gateways and Servers CD-ROM, 03-300151.
Document Installing and Upgrading the the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100)
Administering the S8300 and S8400 Media Servers to work with IA 770, 07-600788
Description Procedures to install a G700 Media Gateway, an S8300 Media Server, and media modules and upgrading Communication Manager Procedures to administer the IA770 INTUITY AUDIX messaging application Procedures to install the media server in a rack and connect components. Procedures to install Communication Manager and configure the media server and the TN2312BP IP Server Interface circuit packs Procedures to install the media server in a rack and connect components
Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703) Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Installing Center Stage Switch (03-300707) Installing the MDF and Telephones (03-300686) Installing the Avaya G650 Media Gateway (03-300685) Hardware Description and Reference for Avaya Communication Manager (555-245-207)
Procedures to install Communication Manager and configure the media server and TN2312BP IP Server Interface (IPSI) circuit packs Procedures to install an MCC1 Media Gateway as a port network and Center Stage Switch. Procedures to install the main distribution frame and telephones Procedures to install a G650 Media Gateway, backplane, and endpoints Descriptions of all products, components, and connectivity
1 of 2
Resources
Document Using the Avaya Enterprise Survivable Servers (ESS) (03-300428) Administrator Guide for Avaya Communication Manager (03-300509) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600) Job Aid: Approved Grounds (555-245-772) Job Aid: Connector and Cable Diagrams (Pinout Charts) (555-245-773) Job Aid: Option Switch Settings (555-245-774) Maintenance Commands for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300431) Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300430) Maintenance Procedures for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300432)
Description Information on installing and configuring ESSs and migrating a main media server to an ESS. End-user information on administering trunks and telephones. Information on implementing converged data and voice communications networks.
Guidelines for planning converged data and voice communications networks.
Description of all approved grounds. Diagrams for various components.
Settings for various components. How to use command interfaces, command syntax, and output from maintenance-related commands.
How to use alarms, error codes, and tests to diagnose and repair problems.
How to troubleshoot and replace various components.
2 of 2
Issue 2.1 June 2006
55
Introduction
How this book is designed and organized

To use this book, you can print:
A section, such as "Migrations," that includes all the chapters and modules within that section 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 Upgrades on page 63 Chapter 2: Upgrading Software on Media Servers on page 65 Introduces the modules associated with upgrading software on the S8300, the S8500, and the S8700-Series media servers Presents the tasks required to upgrade the software on an S8300 Media Server from Release 1.x to Release 2.x. Presents the tasks required to upgrade the software on an S8300 Media Server from Release 2.x or later to Release 3.1. Presents the tasks required to upgrade the software on an S8500 Media Server from Release 2.x to Release 3.1 using the Maintenance Web Interface. Presents the tasks required to upgrade the software on an S8500 Media Server from Release 2.1 or later to Release 3.1 using the Upgrade Tool. 1 of 6 Description
Upgrading Communication Manager from 1.x to 3.1 on an S8300 Media Server on page 75
Upgrading Communication Manager from 2.x to 3.1 on an S8300 Media Server on page 83
Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface on page 89
Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Upgrade Tool on page 119
Section, chapter, or module Upgrading Communication Manager on Avaya S8700 Media Server from R1.x to R3.1 on page 143
Description Presents the tasks required to upgrade the software on an S8700-Series Media Server from Release 1.x to Release 3.1 using the Maintenance Web Interface. Presents the tasks required to upgrade the software on an S8700-Series Media Server from Release 2.x or later to Release 3.1 using the Maintenance Web Interface. Presents the tasks required to upgrade the software on an S8700-Series Media Server from Release 2.1 or later to Release 3.1 using the Upgrade Tool. Introduces the modules associated with upgrading firmware on circuit packs and Ethernet switches Presents the tasks required to upgrade the firmware on the TN2312 IPSI circuit pack It points to the procedures on the Avaya Support Web site. It points to the procedures on the Avaya Support Web site.
Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface on page 199
Using the Upgrade Tool to upgrade Communication Manager on Avaya S8700-Series Media Server on page 251
Chapter 3: Upgrading Firmware on TN circuit packs and Ethernet switches on page 281 Upgrading firmware on the IPSIs and SIPIs on page 283 Upgrading firmware on programmable TN circuit packs on page 293 Upgrading firmware on the Avaya Ethernet Switch on page 295 Migrations on page 297 Migrating to an Avaya S8400 Media Server on page 317 Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server that uses a Card Reader on page 321
Introduces the modules associated with migrating to the S8400 Media Server. Presents the tasks required to migrate a DEFINITY Server CSI in a CMC or G600 Media Gateway with a linear flash to an S8400 Media Server that uses a card reader. Presents the tasks required to migrate a DEFINITY Server CSI in a CMC or G600 Media Gateway with an ATA flash to an S8400 Media Server. 2 of 6
Migrating from a DEFINITY Server CSI in a CMC with an ATA Flash to an S8400 Media Server on page 355
Issue 2.1 June 2006
57
Introduction
Section, chapter, or module Migrating from a DEFINITY Server CSI in a CMC to an S8400 Media Server using Xmodem on page 383
Description Presents the tasks required to migrate a DEFINITY Server CSI in a CMC to an S8400 Media Server that uses Xmodem. Presents the tasks required to migrate an S8100 to an S8400 Media Server using ftp. Introduces the modules associated with migrating to the S8500 Media Server. Presents the tasks required to migrate a DEFINITY Server CSI to an S8500 Media Server. Presents the tasks required to migrate a DEFINITY Server SI direct connect in an SCC to an IP-PNC configuration. It includes both the S8500 and the S8700-Series Media Servers. Presents the tasks required to migrate a DEFINITY Server SI direct connect in an MCC to an IP-PNC configuration. It includes both the S8500 and the S8700-Series Media Servers. Presents the tasks required to migrate a DEFINITY ONE/S8100 in a CMC to an S8500 Media Server. Presents the tasks required to migrate an IP600/S8100 in a G600 to an S8500 Media Server. Introduces the modules associated with migrating to the S8700-Series Media Server. Presents the tasks required to migrate a DEFINITY Server CSI in a CMC to an S8700-Series Media Server in an IP-PNC configuration. 3 of 6
Migrating from an IP600 or S8100 to an S8400 Media Server using ftp on page 413 Chapter 5: Migrating to an Avaya S8500 Media Server on page 443 Migrating a DEFINITY Server CSI in a CMC to an S8500 Media Server on page 447 Migrating a DEFINITY Server SI Direct-Connect in an SCC to a Direct-Connect on page 477
Migrating a DEFINITY Server SI Direct-Connect in an MCC to a Direct-Connect on page 515
Migrating a DEFINITY ONE/S8100 to an S8500 Media Server on page 547 Migrating an Avaya IP600/S8100 to an S8500 Media Server on page 577 Chapter 6: Migrating to an Avaya S8700-Series Media Server on page 611 Migrating a DEFINITY Server CSI in a CMC to an S8700-Series Media Server with IP-PNC on page 617
Section, chapter, or module Migrating from a DEFINITY Server SI in an SCC to an S8700-Series Media Server with Fiber-PNC on page 651 Migrating a DEFINITY Server SI in an MCC to an S8700-Series Media Server with Fiber-PNC on page 701 Migrating a DEFINITY Server R to an S8700-Series Media Server on page 741
Description Presents the tasks required to migrate a DEFINITY Server SI in an SCC to an S8700-Series Media Server. Presents the tasks required to migrate a DEFINITY Server SI in an MCC to an S8700-Series Media Server. Presents the tasks required to migrate a DEFINITY ECS R in an MCC to an S8700-Series Media Server. Presents the tasks required to migrate a DEFINITY ONE/S8100 in a CMC to an S8700-Series Media Server in an IP-PNC configuration. Presents the tasks required to migrate an IP600/S8100 in a G600 to an S8700-Series Media Server in an IP-PNC configuration. Presents the tasks required to migrate an S8500 Media Server to an S8710 Media Server in an IP-PNC configuration. Presents the tasks required to migrate an S8700 Media Server to an S8710 Media Server in either an IP-PNC or multi-connect configuration. Presents the tasks required to migrate an S8710 or S8710 Media Server to an S8720 Media Server in either an IP-PNC or multi-connect configuration.
Migrating a DEFINITY ONE/S8100 to an S8700-Series Media Server with IP-PNC on page 799
Migrating an Avaya IP600/S8100 to an S8700-Series Media Server with IP-PNC on page 833
Migrating an S8500 Media Server to an S8710 Media Server on page 871
Migrating from an S8700 Media Server to an S8710 Media Server on page 889
Migrating from an S8700 or S8710 Media Server to an S8720 Media Server on page 935
Conversions on page 1035 Chapter 7: Converting PNs to IP-PNC on page 1041 Introduces the modules associated with converting to an IP-PNC configuration. 4 of 6
Issue 2.1 June 2006
59
Introduction
Section, chapter, or module Converting some or all direct-connect port networks to IP-connect on page 1047
Description Presents the tasks required to convert an S8500 or S8700-Series media server from a direct connect configuration to an IP-PNC configuration. Presents the tasks required to convert an S8700-Series media server from a CSS (multi-connect configuration) to an IP-PNC configuration. Presents the tasks required to convert an S8700-Series media server from an ATM (multi-connect configuration) to an IP-PNC configuration. Introduces the modules associated with converting to a different mode (new function). Presents the tasks required to convert an S8300 Media Server configured in the ICC mode to an S8300 Media Server configured in the LSP mode. Presents the tasks required to convert an S8300 Media Server configured in the LSP mode to an S8300 Media Server configured in the ICC mode. Presents the tasks required to convert a port network from simplex control to duplicated control. Presents the tasks required to convert a port network from simplex bearer to duplicated bearer. 5 of 6
Converting some or all CSS port networks to IP-PNC on page 1079
Converting some or all ATM port networks to IP-PNC on page 1115
Chapter 8: Converting the Media Server Mode on page 1147 Converting S8300 ICC mode to LSP mode on page 1157
Converting S8300 LSP mode to ICC mode on page 1149
Converting IP-PNC port networks with simplex control to duplicated control on page 1181 Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only) on page 1201
Section, chapter, or module Installing or converting to an S8500 LSP on page 1165
Description Presents the tasks required to convert an S8500 main server to an S8500 LSP. Describes the various ways to access the media servers for administration, including physical connection methods (laptop, modem, LAN), login methods (Web Interface, telnet, P330 Device Manager for G700), Avaya Site Administration and network and browser settings 6 of 6
Appendix A: Accessing the media server on page 1237
Issue 2.1 June 2006
61
Introduction
Upgrades
An upgrade is an installation of a newer release of software on an existing media server or a newer version of firmware on a hardware component. Hardware components include:

Media gateways Media modules Ethernet switches Programmable circuit packs Note: The information in this book describes upgrades to Linux-based media servers only. For more information about upgrades of Avaya Communication Manager on the DEFINITY Server CSI, see Installation, Upgrades, and Additions for Avaya CMC1 Media Gateways, 555-233-118.
Note:
The most common type of upgrade is an update of Communication Manager on a media server. Upgrades can be either major or minor. A minor upgrade is a dot release. On occasion an upgrade requires a change in hardware, such as the hard disk drive. On occasion it is necessary to install a service pack in between releases of Avaya 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:
When you are upgrading the media server as a primary controller, you must check Product Support Notice #739U for the supported upgrade paths. If you attempt to upgrade the media server to a release that is not supported as an upgrade path, you might corrupt the translations. Also, you must check PSN #739U 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 PSN #739U, from any computer, access http://support.avaya.com. Select Product Support Notices > View All Documents > PSN #739U.
Issue 2.1 June 2006
63
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 media server. This process is called a migration. For more information, see Migrations on page 297.
Firmware upgrades
Several pieces of equipment require periodic firmware upgrades. This equipment includes:

The IP Server Interface (TN2312AP/BP) Programable circuit packs (TN799DP, TN2302AP, TN2602AP) Avaya Ethernet switches (C-363T, C-364T), if being used.
!
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 3.1 of Avaya 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 Chapter 1: Introduction for the upgrade. These documents are included on the documentation CD-ROM: Documentation for Avaya Communication Manager, Media Gateways and Servers (03-300151).
Chapter 2: Upgrading Software on Media Servers

The software upgrades in this section cover upgrades of Avaya Communication Manager on S8300, S8500, and S8700 Series Media Servers. Two different tools might be available to upgrade an existing, registered media server:

The Maintenance Web Interface, which is available for all releases The Upgrade Tool, which is available for upgrades from release 2.1 (R2.1)
In either case, ensure that you have the CD-ROM with the latest release of Communication Manager ready to install.
! CAUTION:
CAUTION:
For an S8300 Media Server, three upgrade paths exist:
From Release 1.x to 3.1. This upgrade requires: - An updated license file and Avaya authentication file - An interim upgrade to Release 2.0 or R2.1 to replace the S8300 with an S8300B Media Server
From Release 2.x to Release 3.1. This upgrade requires: - An updated license file - A preupgrade service pack
From Release 3.0.x to Release 3.1. This upgrade has no special requirements.
Issue 2.1 June 2006
65
Upgrading Software on Media Servers
For an S8500 Media Server, two upgrade paths exist:
From Release 3.0.x to Release 3.1. This upgrade has no special requirements, but is covered within the instructions of the R2.x to R3.1 upgrade.
For an S8700-Series Media Server, three upgrade paths exist:
From Release 1.x to 3.0. This upgrade requires: - An updated license file and Avaya authentication file - A preupgrade service pack (software update) - An interim upgrade to Release 1.3.x for some paths
From Release 3.0.x to Release 3.1. This upgrade has no special requirements, but is covered within the instructions of the R2.x to R3.1 upgrade
Upgrades that can affect service

Some upgrades of Communication Manager affect service. During such upgrades, existing calls are dropped and new calls cannot be established. Other upgrades preserve either connections or calls. If an upgrade preserves connections, stable calls, in which the talk path is established, are maintained during the upgrade. However, new calls or call transfers from stable calls are not processed. If an upgrade preserves calls, stable calls are maintained during the upgrade and new calls or call transfers are processed. See Table 3: Connection and call preserving upgrades for information on which upgrades preserve connections or calls.
Common prerequisites for all upgrades
Table 3: Connection and call preserving upgrades Hardware S8300 pre-R3.0 S8300 R3.0 and later S8500 S8700 series pre-R3.0 S8700 series R3.0 or later Preserves connections no yes no no yes Preserves calls no yes no no no

Before you go onsite, you must:

Complete the tasks in the Checklist of tasks to perform before you go on site on page 68. Get a new license file. For more information, see License and Avaya authentication files on page 70.
Issue 2.1 June 2006
67
Checklist of tasks to perform before you go on site

Task Verify that your Services laptop has the appropriate hardware. Description 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 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. For example, obtain logins and passwords for the following components: Media server Media gateway Auxiliary equipment Communication Manager These logins and passwords include those initially needed by the customer. You must have a serial number to obtain an update for an existing license file.
Verify that your Services laptop has the appropriate software.
Obtain the appropriate logins and passwords for all equipment and software.
Obtain the server ID (SID) for the media servers.
If you have a media gateway, you need the serial number from the media gateway. If you have a media server, you need the serial number from the reference IPSI. 1 of 3
Task Verify that you have the Communication Manager software distribution CD-ROM with the current software and firmware. Verify that you have the current preupgrade and postupgrade (if required) service packs on your laptop computer. Verify that you have the most current firmware.
Description Use this CD-ROM to install the software on the media server and upgrade the firmware. The most recent versions of the service packs are also on this CD-ROM. Check which service packs you need and download the files from the Avaya Support Web site, http:// avaya.com/support.
The following firmware is on the software CD:

IPSIs C-LAN MedPro VAL circuit packs
Firmware is upgraded often. To enusre 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. Obtain the static craft password. 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. If the media 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: The static craft password is for use by Avaya technicians only who are using a direct connection from a laptop computer to the media server. 2 of 3
Note:
Issue 2.1 June 2006
69
Task Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary. Verify that you copied all the necessary files to your computer.
Description Perform this step only if the configuration of the customers INADS alarming modem has changed.
These files can include: Service packs License file Authentication file Firmware for programmable circuit packs 3 of 3
License and Avaya authentication files

Use Remote Feature Activation (RFA) to obtain the Communication Manager license files and the Avaya authentication files. RFA is a Web-based application that is available to Avaya employees and authorized BusinessPartners. 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. Note: To access the RFA application, you must complete the RFA online training and received access authorization.
Note:
Generating and retrieving license and authentication files

To 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 media server Internet access to the RFA Web page with Internet Explorer 5.0 or higher
Before you arrive on site, download the license file and the Avaya authentication file to the Services laptop. You install these files as part of the installation process.
Logins and passwords

Once you install the Avaya authentication files, a challenge/response system called Access Security Gateway (ASG) protects Avaya services logins to the media 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 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 media 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.
Caution about platform/PNC license settings for the S8700-series Media Server
The license settings for port network connectivity (PNC) IP-PNC or fiber- PNC (previously referred to as "multiconnect" [MC]) can be complex and can cause problems if not set correctly. When creating a license for an S8700-series Media Server, use the following summary (Table 4) and guidelines:
Table 4: Summary for license settings for the S8700-series platform and PNC License file attribute Platform Type Internet Protocol (IP) PNC (FEAT_IP_PNC) feature Platform Number in Customer Options screen Result in Communication Manager Internet Protocol (IP) PNC feature in Customer Options screen no Allowed configuration
8700 Media Server MC1
OFF2
61
IP-PNC and fiber-connect PNs simultaneously SCC1 or MCC1 are allowed in configuration using IP-PNC.
8700 Media Server IP3
OFF2
83
no
Same as above.
Issue 2.1 June 2006
71
1. Use for all new installations and migrations. Required for upgrades of an S8700-series Media Server that was a fiber-PNC or MC (platform 6) configuration before the upgrade. 2. This attribute, before release 3.0, restricted the ability to configure a network with both IP-PNC and fiber-PNC port networks and to configure SCC1 and MCC1 PNs using IP-PNC only. For all upgrades, migrations, and installations to release 3.0 and later, these restrictions have been lifted for both platforms. Thus, this field is no longer applicable and should be set as OFF. 3. Required, and used only, for upgrades of an S8700-series Media Server that was an IPC (platform 8) configuration before the upgrade.
Guidelines
For a new installation or migration, the licensed platform type should always be 8700 Media Server MC (platform 6). For an upgrade, the licensed platform type of the server must remain the same. If the platform type is 8700 Media Server IP (platform 8) before the upgrade, the platform type must be 8700 Media Server IP (platform 8) after the upgrade. If the platform type is 8700 Media Server MC (platform 6) before the upgrade, the type must be 8700 Media Server MC (platform 6) after the upgrade. Effective with CM 3.0, Internet Protocol (IP) PNC (FEAT_IP_PNC in the RFA license file) is always to set to OFF. After you install, migrate to, or upgrade the server, then this attribute should appear as n (no) in the display-only Internet Protocol (IP) PNC field on page 4 of the Communication Manager Customer Options screen. Note: The Internet Protocol (IP) PNC (FEAT_IP_PNC license attribute, before release 3.0, restricted port network connectivity (PNC) for each of the platforms. The OFF setting previously restricted MC (platform 6) platforms from using IP-PNC. The ON setting previously restricted IP (platform 8) platforms from using MC-PNC configurations. With release 3.0, both of these restrictions were lifted.
Note:
Upgrade modules
Upgrade modules
The following modules are contained in this chapter:
Upgrading Communication Manager from 1.x to 3.1 on an S8300 Media Server on page 75 Upgrading Communication Manager from 2.x to 3.1 on an S8300 Media Server on page 83 Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface on page 89 Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Upgrade Tool on page 119 Upgrading Communication Manager on Avaya S8700 Media Server from R1.x to R3.1 on page 143 Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface on page 199 Using the Upgrade Tool to upgrade Communication Manager on Avaya S8700-Series Media Server on page 251
Issue 2.1 June 2006
73
Introduction
Upgrading Communication Manager from 1.x to 3.1 on an S8300 Media Server
Introduction
This module provides a high-level list of tasks that you must complete to upgrade Avaya Communication Manager from a pre-2.1 release to a 3.1 release on an S8300 Media Server in either primary controller or local survivable processor (LSP) mode. Note: An upgrade to Communication Manager 2.1 or later requires an S8300B Media Server. Replace the S8300A Media Server if it is in use.
Note:
To complete these tasks, you will need the following additional documents:
Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. To obtain this document, go to http:// support.avaya.com. Click S8300 > Installations, Migrations, Upgrades & Configurations and then select the document. Administrator Guide for Avaya 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 pre-R2.1 release is replaced by an S8300B with a blank hard drive. For detailed procedures for most of the tasks in this upgrade scenario, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006.
Issue 2.1 June 2006
75
Pre-requisites
Perform the tasks in this section before going to the customer site. Task 1. Obtain pre-upgrade service pack, if necessary. Steps/Comments If you are upgrading software from certain releases of Communication Manager, you may need to obtain a pre-upgrade service pack (see Table 5: R3.1 Upgrade requirements depending on pre-upgrade release on page 77 If you are upgrading an S8300A to software release 3.1, you must replace the S8300A with an S8300B Media Server. If the S8300 is in LSP mode, and the primary controller that will support the LSP is being migrated to Communication Manager 3.1, 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 3.1, load 628.) Download it and take it to the site.
2. Obtain a replacement S8300B Media Server, if needed. 3. Create/update license and authentication files on the RFA web site.
4. Obtain post-upgrade service pack file.
5. Obtain the Communication Manager 3.1 software CD, and a USB CD-ROM drive, if necessary.
If you have a TFTP server configured on your services laptop, you can read the Server CD and transfer the software to the S8300B Media Server from your laptop. Alternatively, the Communication Manager software can be read from an external USB CD-ROM drive.
Pre-upgrade service pack requirements
Pre-upgrade service pack requirements

The upgrade may require a pre-upgrade service pack, depending on the release of Avaya Communication Manager from which you are upgrading. Table 5: R3.1 Upgrade requirements depending on pre-upgrade release describes when a service pack is required. Table 5: R3.1 Upgrade requirements depending on pre-upgrade release Software Release Before Upgrade to Release 3.1 Release 1.1.x and all other 1.x.x releases not listed below R011x.01.xxx.x Release 1.2.x, 1.3.0. R011x.02.110.4 R011x.03.526.6 Upgrade Requirement
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 media server as if it were a new installation using the Avaya Installation Wizard. 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. 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. 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.
Release 1.3.1.x R011x.03.1.531.0 R011x.03.1.5xx.x
Release 2.x R012x.00.0.000.0 R012x.01.x.xxx.x
1. The LMBR backup contains backup sets for the translations, OS and system files. 2. The Data backup contains backup sets for the translations, OS and system files, security files, and AUDIX data, if any
Issue 2.1 June 2006
77
Tasks checklist
Perform the tasks in this section at the customer site. Task Steps/Comments
Go to the standard documentation

Use Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. To upgrade the S8300, you complete selected tasks from Chapter 11. You need to complete only some of the tasks in these chapters. The specific tasks are identified by page number 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 IA770 is in use (ICC mode), get IA770 data and stop IA770. See "Getting IA770 (AUDIX) Data and Stopping IA770 (if IA770 is being used)" in Chapter 11. 2. Perform data backup See "Back up system files" in Chapter 11. Backup according to the release from which you are upgrading. See Table 5: R3.1 Upgrade requirements depending on pre-upgrade release on page 77 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. 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. 1 of 5
3. Record configuration information See "Recording configuration information" in Chapter 11.
Tasks checklist
Task 4. Install pre-upgrade service pack, if necessary. See "Installing the pre-upgrade software service pack, if necessary" in Chapter 11. 5. Perform the Linux migration backup See "Linux migration backup (if current release is 1.2.0 through 1.3.x)" in Chapter 11. 6. Replace the S8300A with the S8300B See "Replacing the S8300A with the S8300B Media Server" in Chapter 11.
Steps/Comments This service pack allows you to back up data so that it can be restored to a different Linux operating system.
This backup allows you to restore translations and system files after the hard drive has been replaced.
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 S8300B (together with the LED panel for a G700) into the gateway. Set Telnet parameters Remaster hard drive and install upgrade software ICC Mode: If using IA770, select yes on Install AUDIX screen LSP Mode: Select No on Install AUDIX screen. Verify software version Copy files to the S8300 (license file, authentication file, service pack file)
7. Upgrade the S8300B. See "Upgrading the S8300B Media Server" in Chapter 11.
8. Install post-upgrade service pack file. See "Installing post-upgrade Communication Manager service pack file from your laptop" in Chapter 11. 2 of 5
Issue 2.1 June 2006
79
Task 9. Disable RAM disk and reboot. See "Disabling RAM disk on the media server" and "Reboot the media server" in Chapter 11. 10. Restore data See "Restoring data" in Chapter 11.
Steps/Comments ICC Mode only: RAM disk must be disabled in order to successfully restore translations.
Select the restore procedure according to the release from which you upgraded.
ICC Mode: Restore Translations and AUDIX files, if used. LSP Mode: No data restore required.
11. Enable RAM disk and reboot. See "Enabling RAM disk on the media server" and "Reboot the media server" in Chapter 11. 12. Set time, date, and time zone. See "Verifying the time, date, and time zone" in Chapter 11.
ICC Mode only: RAM disk must be manually enabled after you restore translations.
ICC Mode: The time zone of the new ICC must be set, and all LSPs under the ICCs control must be set to the new ICCs 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.
13. Install license file. See "Installing the new license file" in Chapter 11. 14. Install authentication file. See "Installing the new authentication file, if any" in Chapter 11. 15. Verify that the media gateway has registered with either the primary controller (LSP mode) or the S8300B (ICC mode).
Open a SAT session with either the primary controller (LSP mode) or the S8300B (ICC mode) and enter list media-gateway. Verify that the Registered field (Reg?) is set to y.
Place a test call. 3 of 5
Tasks checklist
Task
Steps/Comments ICC mode: On LSPs of the S8300B (if any)
16. Reboot LSPs (if any) 17. Verify LSP translations date and time (if any).
At the LSPs SAT prompt, enter reset system 4. To view the LSPs translations date and time, enter list configuration software.
ICC mode: On the S8300B 18. Verify LSP status (if any)
At the ICCs 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 ICCs translations date and time, enter list configuration software. On the ICC, enter the Linux command filesync -a trans. Ensure that the translation synchronization completed successfully. Wait several minutes, then check the timestamp of the LSPs translation files using the SAT command list survivable-processor on the ICC.
19. If the LSPs (if any) translations have not synchronized with the ICC, invoke translation synchronization.
LSP mode: On the S8300Bs primary controller 20. Verify S8300B LSP status (if any)
At the primary controllers SAT prompt, enter list survivable-processor. The S8300B 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 controllers translations date and time, enter list configuration software. 4 of 5
Issue 2.1 June 2006
81
Task 21. If the S8300B LSPs translations have not synchronized with the primary controller, invoke translation synchronization.
Steps/Comments On the primary controller, enter the Linux command filesync -a trans. Ensure that the translation synchronization completed successfully. Wait several minutes, then check the timestamp of the LSPs translation files using the SAT command list survivable-processor on the primary controller.
22. Upgrade G700 Media Gateway firmware See "Upgrade the firmware on the G700 Media Gateway" in Chapter 11. 23. Set Rapid Spanning Tree See "Setting rapid spanning tree on the network" in Chapter 11.
Using the Avaya Installation Wizard:

Upgrade G700 firmware Upgrade media module firmware
Post-upgrade tasks 24. Implement any additional design changes to voice and/ or voice messaging networks. 25. Re-register the S8300B (LSP mode only) with the Avaya servicing center. 5 of 5
Introduction
Introduction
This module provides a high-level list of tasks for upgrading Communication Manager from 2.x to 3.1 on an S8300B Media Server. The media server can be in either ICC or LSP mode.
! CAUTION:
CAUTION:
When you are upgrading the media server as a primary controller, you must check Product Support Notice #739U for the supported upgrade paths. If you attempt to upgrade the media server to a release that is not supported as an upgrade path, you might corrupt the translations. Also, you must check PSN #739U 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 PSN #739U, from any computer, access http://support.avaya.com. Select Product Support Notices > View All Documents > PSN #739U. Note: The following procedures are for an S8300B Media Server running Communication Manager release 2.1 or higher.
Note:
To complete these tasks, you will need the following additional documents:
Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. To obtain this document, go to http:// support.avaya.com and navigate to S8300 > Installations, Migrations, Upgrades & Configurations. Select the appropriate document. Administrator Guide for Avaya Communication Manager, 03-300509.
Follow the detailed procedures in Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006, for most of the tasks in this upgrade scenario.
Issue 2.1 June 2006
83
Prerequisites
Perform the tasks in this section before going to the customer site. Task 1. Create/update license and authentication files on the RFA web site. Steps/Comments You must create a new license file for the primary controller if both of the following situations are true:

the S8300B is in LSP mode the primary controller that will support the LSP is being migrated to Communication Manager 3.1.
2. Obtain post-upgrade service pack file.
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. For example, release 3.1, load 336. Download the service pack and take it to the site.
3. Obtain the Communication Manager 3.1 software CD, and a USB CD-ROM drive, if necessary.
If you have a TFTP server configured on your services laptop, you can read the Server CD and transfer the software to the S8300B Media Server from your laptop. Alternatively, the Communication Manager software can be read from an external USB CD-ROM drive.
Tasks
Tasks

Use Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. 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. On the S8300 (ICC or LSP) 1. If IA770 is in use (ICC mode), get IA770 data and stop IA770. See "Getting IA770 (AUDIX) Data and Stopping IA770 (if IA770 is being used)" in Chapter 12. 2. Backup all system files translations, OS, and security backup sets. See "Backing up S8300 recovery system files" in Chapter 12. 3. Install preupgrade service pack (R2.x only) See "Copying and installing the service pack files to the media server (starting from R2.x only)" in Chapter 12. ICC mode: Do not restore these backup sets on the S8300B. However, back up these sets in case it is necessary to revert to the original configuration. LSP mode: Backup only OS and security sets. These backup sets will not be restored on the S8300B. Back up the sets in case it is necessary to revert to the original configuration. You must install this service pack to enable the S8300B Web Interface to upload and install the CM 3.1 software.
1 of 4
Issue 2.1 June 2006
85
Task 4. Upgrade the S8300B, using the Web Interface, Manage Software screens. See "Copying the software and firmware files to the server" and "Installing new software" in Chapter 12.

Steps/Comments Copy files from the Server CD. Install files on the S8300B. Make upgrade permanent.
! CAUTION:
CAUTION:
When you are upgrading the media server as a primary controller, you must check Product Support Notice #739U for the supported upgrade paths. If you attempt to upgrade the media server to a release that is not supported as an upgrade path, you might corrupt the translations. Also, you must check PSN #739U 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 PSN #739U, from any computer, access http:// support.avaya.com. Select Product Support Notices > View All Documents > PSN #739U.
5. Install post-upgrade service pack file. See "Installing post-upgrade Communication Manager service pack file from your laptop, if any" in Chapter 12. 2 of 4
Tasks
Task 6. Install the updated license and authentication files 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 (ICC mode).
Steps/Comments
Open a SAT session with either the primary controller (LSP mode) or the S8300B (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 S8300B (if any) 9. Reboot LSPs (if any) 10. Verify LSP translations date and time (if any). At the LSPs 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 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 must match the translations date and time on the ICC. To view the date and time of the ICC translations, enter list configuration software. On the ICC, enter the Linux command filesync -a trans. 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 ICC. 3 of 4
Issue 2.1 June 2006
87
Task
Steps/Comments LSP mode: On the primary controller of the S8300B
13. Verify S8300B LSP status (if any)
At the SAT prompt, enter list survivable-processor. The LSP name and IP address should be listed. The Translations Updated date and time should match the translations date and time on the primary controller. To view the primary controllers translations dates and times, enter list configuration software-version. On the primary controller, enter the Linux command filesync -a 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.
14. If the S8300B LSPs translations have not synchronized with the primary controller, invoke translation synchronization.
15. Upgrade G700 Media Gateway firmware See "Manually upgrading G700 firmware" in Chapter 12. 16. Set Rapid Spanning Tree See "Setting rapid spanning tree on the network" in Chapter 12.
Using the Avaya Installation Wizard:

Upgrade G700 firmware Upgrade media module firmware
Post-upgrade tasks 17. Implement any additional design changes to either or both voice networks and voice messaging networks. 18. Reregister the S8300B in LSP mode with the Avaya servicing center. 4 of 4
Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface
Use this procedure to upgrade an existing S8500 Media Server or Enterprise Survivable Server (ESS) from release 2.x or 3.0 of Avaya Communication Manager to release 3.1. This procedure uses the new Manage Software link on the Maintenance Web Interface. If the media server is running Release 2.1 or later, you can use the Upgrade Tool. For more information, see Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Upgrade Tool.
! CAUTION:
CAUTION:
!
Important:
Important: An upgrade from Release 2.x to Release 3.1 or later requires that you install a preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 3.1. For more information on which service pack to use, see Upgrading LSPs, ESSs, and H.248 media gateways, if any on page 91.
An upgrade from Release 2.x to Release 3.1 requires an updated license file. For more information on generating a license file, see License and Avaya authentication files on page 70.
!
Important:
Important: You cannot upgrade manual backup servers (MBS). If you have one or more MBSs, you can migrate the servers to Enterprise Survivable Servers (ESSs). For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).
Issue 2.1 June 2006
89
Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web
Prerequisites
Before you go onsite, you must complete the tasks in the Checklist of tasks to perform before you go on site on page 68.
The need to restore IP telephone files

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. 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. 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. See the following tasks:
Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 103 Copying IP telephone firmware to the media server, if necessary (main server only) on page 114 Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 115
TN2312AP/BP IPSI circuit pack upgrades

The TN2312AP/BP IP Server Interface (IPSI) circuit packs must have the most recent release of the firmware before you upgrade Communication Manager on the media server. Upgrade the IPSI firmware first. For firmware upgrade procedures, see Upgrading firmware on the IPSIs and SIPIs on page 283.
Prerequisites
Preupgrade service pack for upgrades starting from R2.x only

An upgrade from R2.x of Communication Manager requires a preupgrade service pack, depending on which software load the media server is on. For more information about the software load that is associated with each release, see Software release and load on page 91.
! CAUTION:
CAUTION:
If the server has a Release 2.x field load other than those listed in the table, do not use this section to upgrade the server. You must escalate. Table 6: Software release and load Software release of the existing media server 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 Associated software load R012x.00.0.219.0 R012x.00.1.221.1 R012x.01.0.411.7 R012x.01.1.414.1 R012x.02.0.111.4 R012x.02.1.118.1 Service pack file name 00.0.219.0-xxxx.tar.gz 00.1.221.1-xxxx.tar.gz 01.0.411.7-xxxx.tar.gz 01.1.414.1-xxxx.tar.gz 02.0.111.4-xxxx.tar.gz 02.1.118.1-xxxx.tar.gz
Upgrading LSPs, ESSs, and H.248 media gateways, if any

Note:
Note: Do not perform these tasks and go to Accessing the media server maintenance web interface on page 100 if the customer has none of the following network elements: - H.248 media gateways - Enterprise Survivable Servers (ESSs) - Local survivable processors (LSPs)
You must upgrade Communication Manager on the S8300 and S8500 LSPs before you upgrade Communication Manager on the primary controller. If the configuration uses G250, G350, or G700 Media Gateways, you must upgrade them to the latest firmware. If the media server supports ESSs, you must upgrade the ESSs before you upgrade the primary controller.
Issue 2.1 June 2006
91
The correct order is: 1. If the system includes one or more LSPs, upgrade Communication Manager on the S8300 or S8500 LSP to the latest version. 2. Upgrade the firmware on the media gateway and the media modules to the latest version. 3. If using ESSs, upgrade Communication Manager on the S8500 or S8700-series ESS to the latest version. 4. Upgrade Communication Manager on the S8500 or S8700-series primary controller to the latest version.
Upgrade of Communication Manager on the S8300 LSPs and ESSs, if any

For more information on S8300 LSP upgrades, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100). 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,
Note:
You might use the Upgrade Tool, available on the Web pages of the primary controller, to upgrade Communication Manager on all the LSPs and ESSs. However, to use the tool, the following files must be resident on each LSP and ESS:

Communication Manager Authentication file
For more information about using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheets, 555-245-757.
Stopping and starting LSPs

Before you upgrade the S8500 Media Server, 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.
Prerequisites
Upgrading the LSPs

For more information on LSP upgrades, see one of the following chapters in Installation and Upgrades for Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100:
Chapter 11: "Upgrade of an existing S8300A to R3.1 with manual upgrade of G700 firmware" Chapter 12: "Upgrade of an existing S8300B to R3.1 with manual upgrade of G700 firmware"
Upgrading firmware on media gateways and media modules

You can use the Upgrade Tool to upgrade the firmware on all the media gateways and media modules. However, to use the tool, the firmware files must be installed on the S8300 or other TFTP server that is accessible to the media gateways. For more information on the firmware upgrade process, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100).
Upgrade of Communication Manager on the ESSs

The upgrade of an S8500 or S8700-series ESS is very similar to the upgrade of an S8500 or S8700-series main server. Use the instruction in this document, Upgrading, Migrating, and Converting Media Servers and Gateways, 03-300412. Note: An ESS does not accept translations if they are running a version of Avaya Communication Manager that is older than that of the primary controller. However, an ESS remains registered with the primary controller even with an older version of Communication Manager.
Note:
You might use the Upgrade Tool, available on the Web pages of the main server, to upgrade Communication Manager on all the ESSs. However, to use the tool, the following files must be first downloaded to the ESS:

Communication Manager Authentication file, if necessary
Issue 2.1 June 2006
93
Stopping and starting ESSs

As with LSPs, you have the same option of stopping and starting ESSs to prevent IP telephone registrations with the ESSs during a server upgrade. For more information, see Stopping and starting LSPs on page 92.
SAMP card boot timeout if upgrading with remastering program

! CAUTION:
CAUTION:
If you follow the upgrade procedures as described in this document, the SAMP card boot timeout in the S8500B does not usually timeout during an upgrade. As a result, you do not have to disable the SAMP boot timeout prior to an upgrade. However, if you do not follow the upgrade procedures in this document, but instead, upgrade the software using a telnet session and the remastering program, you must disable the SAMP boot timeout first. See Disabling the boot timeout of the SAMP board (S8500B upgrade only) on page 1168 or "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.
Upgrade tasks (S8500 Main Server as main server)

Preupgrade tasks:

Upgrading the SAMP firmware (S8500B only) on page 97 Connecting to the media server on page 97 Stopping call processing on the LSPs or ESSs if being used (main server only) on page 97 Starting a SAT session on page 98 Checking link status with SAT (main server only) on page 98 Recording all busyouts on page 99 Checking synchronization with the SAT (main server only) on page 99 Disabling scheduled maintenance with the SAT (main server only) on page 100 Checking for translation corruption with the SAT on page 100
Upgrade tasks (S8500 Main Server as main server)
Accessing the media server maintenance web interface on page 100 Copying files to the media server on page 101 Resolving alarms on page 101 Backing up recovery system files on page 101 Verifying the backup on page 102 Suppressing alarming on page 102 Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 103 Checking software release, only if starting from R2.x on page 103 Activating the preupgrade service pack, only if starting from R2.x on page 104
Upgrade tasks:

Inserting the Communication Manager CD-ROM into the media server on page 105 Copying Communication Manager to the media server on page 106 Installing Communication Manager on the media server on page 107 Rebooting the media server on page 110 Verifying reboot progress on page 111 Verifying software operation on page 112 Checking system status on page 112 Making the upgrade permanent on the media server on page 112 Installing postupgrade service pack, if any, on media server on page 113 Setting the Processor Ethernet on page 113 Copying IP telephone firmware to the media server, if necessary (main server only) on page 114
Postupgrade tasks:
Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 115 Enabling scheduled maintenance with SAT on page 115 Busying out previously busied out trunks on page 115 Checking for translation corruption on page 116 Resolving alarms on page 116 Backing up recovery system files on page 116 Releasing alarm suppression (optional) on page 117 Starting call processing on the LSPs and ESSs, if any (main server only) on page 117
Issue 2.1 June 2006
95
Logging off all administration applications on page 118 Registering Avaya Communication Manager on page 118
Upgrade tasks (S8500 Main Server as ESS)

Preupgrade tasks:

Upgrading the SAMP firmware (S8500B only) on page 97 Connecting to the media server on page 97 Starting a SAT session on page 98 Checking for translation corruption with the SAT on page 100 Accessing the media server maintenance web interface on page 100 Copying files to the media server on page 101 Resolving alarms on page 101 Backing up recovery system files on page 101 Verifying the backup on page 102 Suppressing alarming on page 102 Checking software release, only if starting from R2.x on page 103 Activating the preupgrade service pack, only if starting from R2.x on page 104
Upgrade tasks:

Inserting the Communication Manager CD-ROM into the media server on page 105 Copying Communication Manager to the media server on page 106 Installing Communication Manager on the media server on page 107 Rebooting the media server on page 110 Verifying reboot progress on page 111 Verifying software operation on page 112 Checking system status on page 112 Making the upgrade permanent on the media server on page 112 Installing postupgrade service pack, if any, on media server on page 113 Setting the Processor Ethernet on page 113
Post-Upgrade tasks:
Enabling scheduled maintenance with SAT on page 115
Preupgrade tasks
Checking for translation corruption on page 116 Backing up recovery system files on page 116 Logging off all administration applications on page 118 Registering Avaya Communication Manager on page 118
Preupgrade tasks
Upgrading the SAMP firmware (S8500B only)
Before you upgrade the S8500B Media Server to Communication Manager R3.1, upgrade the firmware on the Avaya Server Availability Management Processor (SAMP) card. Check the Downloads section at http://support.avaya.com for the most recent firmware available for the S8500 Media Server and SAMP. For more information, see Using the Avaya Server Availability Management Processor (SAMP), 03-300322.
Connecting to the media server

Perform one of the following options:

If you are on site, connect to the services port on the back of the media server. If you are off site, use the IP address of the media server to log on to the media server.
Stopping call processing on the LSPs or ESSs if being used (main server only)
This procedure is optional. To stop Communication Manager on an LSP or ESS: 1. Connect to the services port (2) on the back of the main media server (primary controller). 2. Access the command line interface of the server using telnet and an IP address of 192.11.13.6.
Issue 2.1 June 2006
97
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. The login prompt for the LSP or ESS appears. 4. Log in to the LSP or ESS as craft. 5. Type stop -afcn and press Enter to stop potential call processing on the LSP or ESS. The LSP or ESS shuts down Communication Manager. 6. Repeat steps 1 through 5 for each LSP or ESS.
! 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 The save translations process on the LSP or ESS automatically causes the endpoints of the media gateways to reregister with the primary controller.
For more information on the S8300 LSP, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100).
Starting a SAT session

To 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: You must use SAT commands for tasks in Checking link status with SAT (main server only) on page 98 through Checking for translation corruption with the SAT on page 100.
Note:
Checking link status with SAT (main server only)

To use the SAT to check the status of various links: 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.
Preupgrade tasks
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 busyouts

To record busyouts: 1. Type display errors. 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.
Checking synchronization with the SAT (main server only)

To check the clock synchronization with the SAT: 1. Type status sync and press Enter to verify that the clock synchronization is correct. 2. Make a note of any outages.
Issue 2.1 June 2006
99
Disabling scheduled maintenance with the SAT (main server only)

To prevent scheduled daily maintenance from interfering with the upgrade: 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 corruption with the SAT

To check for translation corruption: 1. 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 you continue the upgrade.
Accessing the media server maintenance web interface

To access the media server: 1. Start the Web browser. 2. In the Address field, type 192.11.13.6. Press Enter to open the login Web page. 3. Log in as craft or dadmin. 4. Select yes to suppress alarms The system displays the Integrated Management Standard Management Solutions Maintenance Web page. 5. Click Launch Maintenance Web Interface to go to the main menu.
Preupgrade tasks
Copying files to the media server

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

License and Avaya Authentication files Preupgrade and postupgrade service pack files Programmable circuit pack firmware
To copy files to the media server: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im 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 media server. 4. Click Download to copy the files to the media server. The system copies the files automatically to the default file location.
Resolving alarms
To clear alarms: 1. 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.
Backing up recovery system files

To 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.
Issue 2.1 June 2006
101
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. 4. Click Start Backup to start the back up process.
Verifying the backup

To verify that the backup was successful: 1. Under Data Backup/Restore, select 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 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.
Preupgrade tasks
Saving a copy of the 4600-series telephone configuration file, if any (main server only)
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. 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, perform the following steps: 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 . 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.x

Check the version of Communication Manager to ensure that you install the correct preupgrade service pack. For more information, see Upgrading LSPs, ESSs, and H.248 media gateways, if any on page 91. Under Server, click Software Version to see what software release is on the media server.
Issue 2.1 June 2006
103
Activating the preupgrade service pack, only if starting from R2.x

To activate the service pack: 1. Access the command line interface of the server with telnet and an IP address of 192.11.13.6. 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 media 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 media server displays a message that the service pack was applied. 7. Type update_show again and press Enter to list Communication Manager files to verify the service pack file was activated. 8. Enter y in response to the question, Commit this software?
Upgrade tasks
Upgrade tasks
! CAUTION:
CAUTION:
! CAUTION:
CAUTION:
If you follow the upgrade procedures in this document, the SAMP card boot timeout in the S8500B does not usually timeout during an upgrade. As a result, you do not have to disable the SAMP boot timeout prior to an upgrade. However, if you do not follow the upgrade procedures in this section, but instead, upgrade the software using a telnet session and the remastering program, you must disable the SAMP boot timeout first. 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.
Inserting the Communication Manager CD-ROM into the media server

Insert the CD-ROM that contains Communication Manager into the CD-ROM drive on the media server. Close the tray. Note: You can copy Communication Manager software from an http or tftp server onto the media server. In this case, skip this step.
Note:
Issue 2.1 June 2006
105
Copying Communication Manager to the media server

To copy Communication Manager to the media server: 1. On the browser toolbar, click Refresh to reload the current page. 2. 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.
3. 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 Complete c. Click Continue to return to the initial Manage Software page.
Upgrade tasks
If fewer than 3 releases resides on the hard disk a. Select Copy a release to the local hard drive, but do not install it. Click Continue to view the options for copying the software to the hard disk. b. Select Copy from this servers 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. When complete, the system displays the following message: Success g. Click Continue to return to the initial Manage Software page.
Installing Communication Manager on the media server

! CAUTION:
CAUTION:
If you are upgrading existing software, did you check Product Support Notice #739U to make sure the upgrade path to the new load is supported?
To install Communication Manager on the media server: 1. On the browser toolbar, click Refresh to reload the current page.
Issue 2.1 June 2006
107
2. Under Server Upgrades, click Manage Software.
3. Select Install one of the following releases currently resident on the local hard drive: and click Continue. The Choose Software Web page appears. 4. Select the software release you want, and click Continue. The Choose License Source Web page appears.
Upgrade tasks
Choose License Source screen
5. If you have copied the license and authentication files to the server, select the following options: - I will supply the license/authentication files myself when prompted later in this process. - Update authentication information as well as license information. 6. Click Continue. The Review Notices Web page appears. 7. 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. 8. Click Continue. The Begin Installation Web page appears. The page summarizes the request you have made.
Issue 2.1 June 2006
109
9. Click Continue. The Install in Progress Web page appears. The installation takes 10 to 20 minutes. The Install in Progress screen refreshes every 10 seconds or on demand by clicking the Refresh button. When complete, the Reboot Server Web page appears.
Rebooting the media server

Note:
Note: When you reboot the media 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 media server. 1. Click Reboot. The Reboot in Progress Web page appears. 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: The reboot can take 20 minutes or longer. The system does not automatically tell you when the reboot is complete. 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 111. 3. Wait 5 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.
Note:
Note:
Upgrade tasks
! CAUTION:
CAUTION:
DO NOT CLICK CANCEL past this point. Be patient. If the installation fails, a message appears on the Reboot in Progress screen. 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 screen. 6. Unless instructed in your planning documents to update the tripwire database, select Do not update the tripwire data base now and click Continue. The system displays the Installation Complete screen. 7. Click Close. You are returned to the main menu. 8. Go to Verifying software operation on page 112
Verifying reboot progress

To 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 media 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.
Issue 2.1 June 2006
111
Verifying software operation

To verify the software version. 1. Under Server, click Software Version. 2. Look in the Reports as field to verify that the new software is present.
Checking system status

To 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.
Making the upgrade permanent on the media server

! CAUTION:
CAUTION:
You must make the upgrade permanent. Otherwise, the next time that you reboot the media 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.
Upgrade tasks
Installing postupgrade service pack, if any, on media server

Note:
Note: Do not perform this procedure if you are not installing a service pack for Communication Manager. This service pack might not preserve calls.
To install a post-upgrade service pack. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Log in as craft. 3. Type update_unpack and press Enter. 4. Select the update by number and press Enter. 5. Type update_show and press Enter to list Communication Manager files to verify that the new software update file was unpacked. 6. Type update_activate update, where update is the update ID number produced by update_show. An example can be 00.0.628.x-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot with an automatic reset system 4 command. If the system reboots, it might also display the 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 media server displays a message that the service pack was applied. 7. Type update_show again and press Enter to list Communication Manager files to verify that the new service pack file is activated.
Setting the Processor Ethernet

To verify the Ethernet port settings on the server and to set the processor Ethernet port. 1. Under Server Configuration, click Configure Server. The Review Notices Web page appears. 2. Click Continue until the Specify how you want to use this wizard Web page appears.
Issue 2.1 June 2006
113
3. Select Configure individual services, and click Continue. The Configure Individual IP Services menu appears on the left pane of the Web page. 4. Click the Set Identities menu option. The Set Identities Web page appears. 5. Under Assign the Processor Ethernet to an Interface, select Corporate LAN. 6. Click Continue. The Configure Interfaces Web page appears. 7. Click Change and close the window.
Copying IP telephone firmware to the media server, if necessary (main server 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. 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 media server. Note: The IP telephone firmware that was originally downloaded is overwritten.
Note:
To copy files to the media server: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im 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 media server. 4. Click Install this file on the local server. 5. Click Download to copy the file(s) to the media server. The files are copied automatically to the /tftpboot directory. The 46xx IP Telephone Web page is reinstated at the next reboot.
Post-Upgrade tasks
Post-Upgrade tasks
Note:
Note: Tasks Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 115 through Checking for translation corruption on page 116 use SAT commands on the active media server.
Restoring the 4600-series IP Telephone configuration file, if any (main server only)
If you copied a 4600-series Telephone configuration file to the /var/home/ftp/pub directory prior to the upgrade, you must restore it after the upgrade. However, before you restore the file, ensure that you have downloaded the appropriate IP telephone firmware. 1. At the Linux command line, type cd ~ftp/pub, and press Enter. 2. At the prompt, type cp 46xxsettings.txt /tftpboot, and press Enter. The 4600-series IP Telephone settings file is now restored to the /tftpboot directory.
Enabling scheduled maintenance with SAT

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 need to ensure that they also are busied out after the conversion.
Issue 2.1 June 2006
115
Checking for translation corruption

To check for translation corruption: 1. Type newterm. 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.
Resolving alarms

To 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. 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. 4. Click Start Backup to start the back up process.
Note:
Post-Upgrade tasks
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. 2. Log in as craft or dadmin. 3. Type almsuppress -n and press Enter to release alarm suppression. 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 media server is the primary controller for a G350 or G700 Media Gateway equipped with an LSP. You shut down the media 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 (media server) with SSH. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Type telnet IPaddress, where IPaddress is the IP address of the S8300 or S8500 LSP, or the S8500 or S8700-series ESS. 3. Log in as craft or dadmin. 4. At the prompt type start -afcn and press Enter to restart call processing on the LSP or ESS.
Issue 2.1 June 2006
117
5. Repeat for each LSP or ESS. For more information, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, or Using the Avaya Enterprise Survivable Server (ESS), 03-300428.
Logging off all administration applications

When you complete all the administration, log off all the applications that you used.
Registering Avaya Communication Manager

Follow standard procedures to register the new software.
Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Upgrade Tool
Use this procedure to upgrade an existing S8500 Media Server from release 2.x or 3.0 of Avaya Communication Manager to release 3.1. This method uses the Upgrade Tool available with Release 2.1 and later. If you prefer to upgrade Communication Manager with the Maintenance Web Interface, see Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface.
! CAUTION:
CAUTION:
!
Important:
Important: An upgrade from Release 2.x to Release 3.1 or later requires that you install a preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 3.1. For more information about which service pack to use, see Preupgrade service pack for upgrades starting from R2.x only on page 122.
An upgrade from Release 2.x to Release 3.1 requires an updated license file. For more information about generating a license file, see License and Avaya authentication files on page 70 in Chapter 2: Upgrading Software on Media Servers.
!
Important:
Important: You cannot upgrade manual backup servers (MBS). If you have one or more MBSs, you can migrate the servers to Enterprise Survivable Servers (ESSs). For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).
Issue 2.1 June 2006
119
Upgrading Communication Manager on Avaya S8500 Media Server from R2.x/R3.0 to R3.1 or from R3.1 to
!
Important:
Important: You cannot use the Upgrade Tool to upgrade the G150 Media Gateway or G250 Media Gateways. You must upgrade the G150 and G250 separately. For more information, see Installation and Configuration for the Avaya G150 Media Gateway (03-300395). Also, if you are upgrading an ESS by itself locally, you cannot use the Upgrade Tool. Instead, you must follow the procedures in Upgrading Communication Manager on Avaya S8500 Media Server or S8500 ESS Using Maintenance Web Interface on page 89.
About use of the Upgrade Tool

Note:
Note: For information on using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheet (555-245-757) and the online Help.
With the Upgrade Tool, you can automatically and remotely upgrade the following software from the primary controller:
Communication Manager on the Local Survivable Processors (LSPs) and Enterprise Survivable Servers (ESSs). You can also use the tool to apply preupgrade and postupgrade service packs and licenses to the LSPs and ESSs. Firmware on the G350 or the G700 Media Gateways and most of the media modules that are resident in the media gateways. Communication Manager and preupgrade and postupgrade service packs and a license on the primary controller, if the primary controller is already running R2.1 or later.
With the Upgrade Tool, you do not have to physically be at the ESS, LSP, and media gateway locations to perform the upgrades. Additionally, you do not have to run the upgrades one by one. You can enter the needed information for all ESSs, LSPs and gateways into the Upgrade Tool, then run the Upgrade Tool. The tool automatically upgrades Communication Manager and firmware on all LSPs, ESSs, and G350/G700 Media Gateways. Note: ESSs and LSPs must be upgraded to the latest release of Communication Manager before you upgrade the primary controller to the latest release. To use the Upgrade Tool, the LSPs and the primary controller must be running Release 2.1 or later of Avaya Communication Manager.
Note:
Which devices the Upgrade Tool can upgrade

Before you upgrade an ESS, LSP, or gateway, administer and register the ESS, LSP or media gateway with the primary controller. To check if a device is registered, use the Query Versions option on the Upgrade Tool navigation pane on the left side of the Upgrade Tool screens. The Query Versions screen shows an IP address next to each registered ESS, LSP, and gateway. The Upgrade Tool upgrades the components of a configuration in the following order:

All LSPs that you specify All ESSs that you specify The media gateways and the media modules The primary controller

! CAUTION:
CAUTION:
If you follow the upgrade procedures in this document, the SAMP card boot timeout in the S8500B does not usually timeout during an upgrade. As a result, you do not have to disable the SAMP boot timeout prior to an upgrade. However, if you do not follow the upgrade procedures in this document, but instead, upgrade the software using a telnet session and the remastering program, you must disable the SAMP boot timeout first. See Disabling the boot timeout of the SAMP board (S8500B upgrade only) on page 1168 or "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.
Prerequisites
Issue 2.1 June 2006
121


! CAUTION:
CAUTION:
Overview of the upgrade process

Because you cannot use the Upgrade Tool to upgrade the G150 and G250 Media Gateways, you must upgrade them separately.
Prerequisites
The upgrade process consists of the following high level steps: 1. Obtain the updated license files and preupgrade and postupgrade service packs for LSPs and the primary controller. Also, obtain firmware files for all G350 and G700 Media Gateways. 2. If LSPs or ESSs are used, prepare the LSPs and ESS for the upgrade:
Distribute Communication Manager software to the site of each LSP and ESS. You can distribute software with either of the following methods: - CD-ROMs that someone mails - Software someone copies to a TFTP or HTTP server, from which the LSP/ESS can download the software over the customer LAN.
Use the Maintenance Web Interface pages to copy the preupgrade service packs (R2.x only) to the primary controller (main server). Use the Upgrade Tool to install and activate the preupgrade service pack on any LSPs, ESSs, and the primary controller (R2.x only). Copy the new Communication Manager software to all the LSPs and ESSs with the Manage Software Web page. You can log in remotely to each LSP/ESS to copy software if one of the following tasks is done first: - Someone at each location inserts the software CD-ROM for you. - You loaded the software on a TFTP or HTTP server in the customer LAN.
3. Use the Maintenance Web Interface pages to copy the postupgrade service packs and license files of the LSPs, ESSs, and primary controller from one of the following devices: - Your laptop - An FTP server - Another means of transport onto the primary controller. 4. Copy the new Communication Manager software to the primary controller with the Manage Software Web page. 5. Start the Upgrade Tool to upgrade

Communication Manager, postupgrade service packs, and license files on the LSPs. The firmware on the G350 and G700 media gateways and media modules. Communication Manager, post-upgrade service packs, and license files on the ESSs. Communication Manager and post-upgrade service pack on the primary controller.
6. If installed, upgrade the G150 and G250 Media Gateways manually. You cannot use the Upgrade Tool to upgrade the G150 and G250 Media Gateways.
Issue 2.1 June 2006
123
The need to restore IP Phone files

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. 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. 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. See the following tasks:
Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 128 Copying IP telephone firmware to the media server, if necessary (main server only) on page 139 Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 139
Upgrade tasks
Preupgrade tasks:

Upgrading the SAMP firmware (S8500B only) on page 126 Connecting to the media server on page 126
Current configuration tasks:

Starting a SAT session on page 126 Checking link status with SAT (main server only) on page 127 Recording all busyouts on page 127 Checking synchronization with the SAT (main server only) on page 127 Disabling scheduled maintenance with the SAT (main server only) on page 128 Checking for translation corruption on page 128 Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 128 Accessing the media server maintenance web interface on page 129 Copying the service pack files to the media server, only if starting from R2.x on page 129
Upgrade tasks
Installing the preupgrade software service pack only if starting from R2.x on page 130 Copying files to the media server on page 131 Resolving alarms on page 131 Backing up recovery system files on page 132 Verifying the backup on page 132 Suppressing alarming on page 132 Inserting the Communication Manager CD-ROM into the media server on page 133 Copying Communication Manager to the media server on page 134 Removing the CD-ROM from the CD-ROM drive on page 135
Upgrade tasks:

Starting the Upgrade Tool on page 136 Installing Avaya authentication files (if required) on page 137 Verifying software operation on page 137 Checking system status on page 138 Setting the Processor Ethernet on page 138 Copying IP telephone firmware to the media server, if necessary (main server only) on page 139
PostUpgrade tasks:
Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 139 Enabling scheduled maintenance with SAT on page 140 Busying out previously busied out trunks on page 140 Checking for translation corruption on page 140 Resolving alarms on page 140 Backing up recovery system files on page 141 Releasing alarm suppression (optional) on page 141 Logging off all administration applications on page 141 Registering Avaya Communication Manager on page 142 Upgrading the G150 Media Gateways, if used on page 142
Issue 2.1 June 2006
125
Preupgrade tasks
Upgrading the SAMP firmware (S8500B only)
Before you upgrade the S8500B Media Server to Communication Manager R3.1, upgrade the firmware on the Avaya Server Availability Management Processor (SAMP) card. Check the Downloads section at http://support.avaya.com for the most recent firmware available for the S8500 Media Server and SAMP. For more information, see Using the Avaya Server Availability Management Processor (SAMP), 03-300322.

Perform one of the following options:

If you are on site, connect to the services port on the back of the media server. If you are off site, use the IP address of the media server to log on to the media server.

To start a SAT session: 1. Start a terminal emulation application, such as Native Configuration Manager or Microsoft HyperTerminal or use a telnet session. 2. Type telnet 192.11.13.6 5023. Press Enter. 3. Log on as craft or dadmin. 4. Suppress alarm origination.
Preupgrade tasks

To use the SAT to check the status of various links: 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:



Issue 2.1 June 2006
127


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. 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.
Preupgrade tasks
To copy the 4600-series configuration file to a safe location, perform the following steps: 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 . 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.

Copying the service pack files to the media server, only if starting from R2.x
Note:
Note: If you are upgrading an R3.x system, skip to Copying files to the media server on page 131.
Issue 2.1 June 2006
129
To copy the service pack files to the media server: Note: Do not perform this task if you are upgrading an R3.0 release to R3.1. 1. On the Maintenance Web Interface, under Miscellaneous, click Download Files. 2. Select the download method, Files to download from the machine Im using to connect to the server. Note: Do not select the check box, Install this file on the local server. 3. Browse to the directory on the laptop that contains the preupgrade and post-upgrade service pack files. 4. Select the service pack files and click Download.
Note:
Note:
Installing the preupgrade software service pack only if starting from R2.x
Note:
Note: Do not perform this task if you are upgrading an R3.0 release to R3.1.
You must install a preupgrade service pack to modify the server upgrade tools, including the web Interface and upgrade scripts. This service pack then enables the upgrade to Communication Manager 3.1 to complete successfully. LSPs with R2.x software also require the preupgrade service pack. 1. On the Welcome page of the Communication Manager Web pages, double-check Launch Upgrade Tool. The Upgrade Tool Welcome page appears. 2. Select Schedule Upgrade from the menu on the left pane. The Schedule Upgrade page appears. 3. Enter the file name of the preupgrade software service pack in the Update File Name field for the Main Server(s). 4. Enter the file name of the preupgrade software service pack in the Update File Name field for LSP. 5. Scroll down to the Main Server Targets field and select the Update box for the primary controller. 6. Scroll down to the LSP Targets field and select the Update box for the LSPs you are upgrading.
Preupgrade tasks
7. Click Run Now. The Upgrade Tool updates the primary controller and any LSPs you selected. 8. Check the status of the updates by selecting the View Current option from the left pane menu. The word Completed appears in the status field for the primary controller and each LSP you are updating.


Resolving alarms
Issue 2.1 June 2006
131

Note:

! CAUTION:
CAUTION:
To suppress alarming: 1. Access the command line interface of the server with telnet and an IP address of 192.11.13.6.
Preupgrade tasks
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.

Note:
! CAUTION:
CAUTION:
Issue 2.1 June 2006
133

!
Important:
Upgrade tasks
Removing the CD-ROM from the CD-ROM drive

To 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 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.
Upgrade tasks
! CAUTION:
CAUTION:
If you follow the upgrade procedures in this document, the SAMP card boot timeout in the S8500B does not usually timeout during an upgrade. As a result, you do not have to disable the SAMP boot timeout prior to an upgrade. However, if you do not follow the upgrade procedures in this section, but instead, upgrade the software using a telnet session and the remastering program, you must disable the SAMP boot timeout first. 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.
Issue 2.1 June 2006
135
Starting the Upgrade Tool

!
Important:
Important: The Communication Manager software must be copied directly to each LSP by logging into the LSP and using the Manage Software Web page. In addition, the authentication file, if needed, must be downloaded to each LSP also by logging into the LSP and using the Download Software Web page. Then, you can run the Upgrade Tool from the primary controller to upgrade the LSPs and install new licenses and postupgrade service packs, if necessary.
Use the Upgrade Tool to upgrade LSPs, media gateways and modules, and the S8500 Media Server as primary controller. Note: For more information on using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheets, Issue 3 (555-245-757) and the online Help.
Note:
The following steps start the Upgrade Tool. 1. On the Home page, click Launch Upgrade Tool.
Upgrade tasks
The system displays the Upgrade Tool Home Page.
2. Follow the procedures in the Job Aid: Upgrade Tool and Worksheets.
Installing Avaya authentication files (if required)

New authentication files are required when you upgrade the software to a release with a new whole number, such as from R2.2 to R3.0. To install the security file: 1. On the Maintenance Web Interface, under Security, select Authentication File. 2. Select Install the Authentication file I previously downloaded and click Install to install the Avaya authentication file. The system tells you that the authentication file is installed successfully.

Issue 2.1 June 2006
137

To 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.
Setting the Processor Ethernet

To verify the Ethernet port settings on the server and to set the processor Ethernet port. 1. Under Server Configuration, click Configure Server. The Review Notices Web page appears. 2. Click Continue until the Specify how you want to use this wizard Web page appears. 3. Select Configure individual services, and click Continue. The Configure Individual IP Services menu appears on the left pane of the Web page. 4. Click the Set Identities menu option. The Set Identities Web page appears. 5. Under Assign the Processor Ethernet to an Interface, select Corporate LAN. 6. Click Continue. The Configure Interfaces Web page appears. 7. Click Change and close the window.
Post-Upgrade tasks
Note:
Post-Upgrade tasks
Issue 2.1 June 2006
139



Resolving alarms
Post-Upgrade tasks

Note:


Issue 2.1 June 2006
141

Postrequisites
Upgrading the G150 Media Gateways, if used
Note:
Note: If the configuration does not include G150 Media Gateways, do not perform this task.
You must upgrade the G150 Media Gateways and their WAN Expansion Interfaces first if both of the following conditions are true:

The configuration includes both G150 Media Gateways and WAN Expansion Interfaces. Newer software exists for the G150 Media Gateways.
For more information, see Installing and Configuring the Avaya G150 Media Gateway (03-300395).
Upgrading Communication Manager on Avaya S8700 Media Server from R1.x to R3.1
This procedure is for upgrading Avaya Communication Manager on an existing, registered S8700-series Media Server running Release 1.x of Avaya Communication Manager. This upgrade requires that you remaster the hard disk with a software distribution CD-ROM. The CD-ROM contains an updated operating system and Release 3.1 of Avaya Communication Manager. This method uses the Manage Software link on the Maintenance Web Interface.
!
Important:
Important: You cannot upgrade Release 1.0 or 1.1 directly to Release 3.1. You must first upgrade to Release 1.3.x. Important: When you upgrade from Release 1.x to Release 3.1 or later, you must install either one or two preupgrade service packs before you can upgrade Communication Manager. These service packs support the upgrade to Release 3.1. For more information on which service packs to use, see Preupgrade service pack on page 144. Important: Upgrading from Release 1.x to Release 3.1 requires an updated license file. For more information on generating a license file, see License and Avaya authentication files on page 70.
!
Important:
!
Important:
! CAUTION:
CAUTION:
The licensing of the platform and port network connectivity attributes for the S8700-series Media Server can be complex. For more information, see Caution about platform/PNC license settings for the S8700-series Media Server on page 71.
!
Important:
Important: You cannot upgrade Survivable Remote EPNs or manual backup servers (MBS). If you have one or more MBSs or SREPNs, you can migrate the servers to Enterprise Survivable Servers (ESSs). For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).
Although you always upgrade Communication Manager on a busied-out standby media server, you can access SAT commands on the active media server only. You perform some preupgrade tasks on the active media server, then you move to the standby media server for the actual software upgrade. You must also perform some postupgrade tasks on the active media server.
Issue 2.1 June 2006
143
! CAUTION:
CAUTION:
When you reboot an active media server, you cause a service interruption. Ensure that you are on a busied out, standby media server when you upgrade the software.
Prerequisites

Preupgrade service pack

An upgrade from R2.x of Communication Manager requires either one or two preupgrade service packs, depending on which software load the media server is on. For more information about the software load that is associated with each release, see Software release and load.
Prerequisites
! CAUTION:
CAUTION:
If the server has a Release 1.x field load other than those listed in the table, do not use this section to upgrade the server. You must escalate.
Table 8: Software release and load Software release of existing media server 1.2 1.3 1.3.1 1.3.2 Associated software load R011x.02.110.4 R011x.03.526.5 R011x.03.1.531.0 R011x.03.2.536.1 Service pack file name 02.0.110.4-1003.tar.gz 02.0.110.4-1004.tar.gz 03.0.526.5-1003.tar.gz 03.0.526.5-1004.tar.gz 01.0.531.0-1004.tar.gz 03.2.536.1-1004.tar.gz
Upgrade of LSPs and media gateways, if being used

Note:
Note: If the customer has no H.248 media gateways or no local survivable processors (LSPs), skip these tasks and go to Connecting to the active media server on page 151.
You must upgrade Communication Manager on the S8300 and S8500 LSPs before you upgrade Communication Manager on the primary controller. If the configuration uses G250, G350, or G700 Media Gateways, you must upgrade them to the latest firmware. If the media server supports ESSs, you must upgrade the ESSs before you upgrade the primary controller. The correct order is: 1. If the system includes one or more LSPs, upgrade Communication Manager on the S8300 or S8500 LSP to the latest version. 2. Upgrade the firmware on the media gateway and the media modules to the latest version. 3. If using ESSs, upgrade Communication Manager on the S8500 or S8700-series ESS to the latest version. 4. Upgrade Communication Manager on the S8500 or S8700-series primary controller to the latest version.
Issue 2.1 June 2006
145

Note:


Before you upgrade the S8700-series Media 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 media 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.
Upgrade tasks
Upgrading the LSPs

For more information on LSP upgrades, see one of the following chapters in Installation and Upgrades for Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100:
Chapter 11: "Upgrade of an existing S8300A to R3.1 with manual upgrade of G700 firmware" Chapter 12: "Upgrade of an existing S8300B to R3.1 with manual upgrade of G700 firmware"

Upgrade tasks
Preupgrade tasks:
Stopping call processing on the LSPs or ESSs if being used (main server only) on page 151 Connecting to the active media server on page 151

Starting a SAT session on page 152 Checking link status with SAT (main server only) on page 152 Recording all busyouts on page 153 Checking synchronization with the SAT (main server only) on page 153 Disabling scheduled maintenance with the SAT (main server only) on page 153 Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 154
Issue 2.1 June 2006
147
Checking for translation corruption on page 154 Accessing the media server maintenance web interface on page 154 Resolving alarms on page 155 Backing up recovery system files on the active server on page 155 Verifying the backup on page 156 Suppressing alarming on page 156 Disconnecting from the active media server on page 156 Connecting to the standby media server on page 157 Clearing the ARP cache on the laptop computer on page 157 Accessing the media server maintenance web interface on page 157 Backing up files on the standby media server on page 158 Verifying the backup on page 158 Copying preupgrade service pack(s) to the standby media server on page 158 Suppressing alarming on page 159
Upgrade tasks (first media server)

Busying out the standby media server on page 159 Checking the software release on the standby media server on page 160 Installing the preupgrade service pack on page 160 Verifying connectivity to customer network server on page 161 Backing up the system files with Linux MigrationBackup on page 161 Setting Telnet parameters on page 163 Erasing the MBR on the media server on page 164 Inserting the Communication Manager CD-ROM into the media server on page 164 Rebooting the standby media server on page 165 Verifying reboot progress on page 165 Installing Communication Manager on page 166 Accessing the media server maintenance web interface on page 167 Verifying software operation on page 168 Copying files to the media server on page 168 Selecting media server type on page 169 Configuring the network parameters (optional) on page 169 Verifying connectivity to the network server (optional) on page 171
Upgrade tasks
Installing postupgrade service pack, if any, on media server on page 171 Verifying installation of the service pack on page 172 Restoring the Linux migration backup files on page 173 Verifying date and time on page 174 Verifying software operation on page 175 Checking system status on page 175 Releasing the standby media server on page 175 Interchanging the media servers on page 175 Installing the new license and Avaya authentication files on newly active media server on page 176 Disconnecting from the active media server on page 177
Upgrade tasks (second media server):

Connecting to the standby media server on page 177 Copying preupgrade service pack(s) to the standby media server on page 177 Busying out the standby media server on page 177 Verifying software operation on page 178 Installing the preupgrade service pack on page 178 Verifying connectivity to customer network server (optional) on page 179 Backing up the system files using Linux MigrationBackup on page 179 Erasing the MBR on the standby media server on page 181 Inserting the Communication Manager CD-ROM into the media server on page 182 Rebooting the standby media server on page 182 Verifying reboot progress on page 182 Installing Communication Manager on page 183 Accessing the media server maintenance web interface on page 184 Verifying software operation on page 185 Copying files to the media server on page 185 Selecting media server type on page 185 Configuring the network parameters (optional) on page 186 Verifying connectivity from the network server on page 188 Verifying connectivity to the network server (optional) on page 188 Installing postupgrade service pack, if any, on media server on page 188
Issue 2.1 June 2006
149
Verifying service pack installation on page 189 Restoring the Linux migration backup files on page 190 Verifying date and time on page 191 Verifying software operation on page 191 Checking system status on page 192 Releasing the standby media server on page 192 Disconnecting from the standby media server on page 192 Connecting to the active media server on page 192
PostUpgrade tasks:

Enabling scheduled maintenance with SAT on page 193 Releasing MMI circuit packs with SAT (duplicated control network only) on page 193 Busying out previously busied out trunks on page 194 Checking for translation corruption on page 194 Resolving alarms on page 194 Backing up recovery system files on page 194 Releasing alarm suppression (optional) on page 195 Logging off all administration applications on the active media server on page 195 Disconnecting from the active media server on page 195 Connecting to the standby media server on page 196 Backing up files on the standby media server on page 196 Releasing alarm suppression (optional) on page 196 Starting call processing on the LSPs and ESSs, if any (main server only) on page 197 Logging off all administration applications on the standby media server on page 197 Registering Avaya Communication Manager on page 198
Preupgrade tasks
Preupgrade tasks
This procedure is optional. To stop Communication Manager on an LSP or ESS: 1. Connect to the services port (2) on the back of the main media 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. The login prompt for the LSP or ESS appears. 4. Log in to the LSP or ESS as craft. 5. Type stop -afcn and press Enter to stop potential call processing on the LSP or ESS. The LSP or ESS shuts down Communication Manager. 6. Repeat steps 1 through 5 for each LSP or ESS.
! CAUTION:
CAUTION:
Connecting to the active media server

If you are on site, connect to the services port on the back of the active media server. If you are off site, log on to the active media server with the actual IP address of the media server.
Issue 2.1 June 2006
151

To start a SAT session: 1. Start a terminal emulation application, such as Native Configuration Manager or Microsoft HyperTerminal or use a telnet session. 2. Type telnet 192.11.13.6 5023. Press Enter. 3. Log on as craft or dadmin. 4. Suppress alarm origination. Note: Tasks Checking link status with SAT (main server only) on page 152 through Checking for translation corruption on page 154 use SAT commands. You can perform these tasks on the active media server only.
Note:


Preupgrade tasks



Issue 2.1 June 2006
153
Busying out MMI circuit packs with SAT for a duplicated control network 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. 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.


To access the media server: 1. Start the Web browser. 2. In the Address field, type 192.11.13.6. Press Enter to open the login Web page.
Preupgrade tasks
3. Log in as craft or dadmin. 4. Select yes to suppress alarms The system displays the Integrated Management Standard Management Solutions Maintenance Web page. 5. Click Launch Maintenance Web Interface to go to the main menu.
Resolving alarms
Backing up recovery system files on the active server

Note:
Note: You can only save translations on the active media server.
To back up system configuration files: 1. Under Data Backup/Restore, click Backup Now. 2. Select the data sets. For the main server only, select Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. An ESS gets translations from the main server, so there is no reason to backup the translations on an ESS. Do not select Full Backup because this option does not save translations. 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. 4. Click Start Backup to start the back up process.
Note:
Issue 2.1 June 2006
155

! CAUTION:
CAUTION:
Disconnecting from the active media server

If you are on site, unplug the laptop computer from the services port on the back of the active media server.
Preupgrade tasks
Connecting to the standby media server

If you are on site, connect to the services port on the back of the standby media server. If you are off site, log on to the standby media server with the actual IP address of the media server.
Clearing the ARP cache on the laptop computer

You 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: 1. Click Start > Run to open the Run dialog box. 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.
4. To access the media server, type ping -t 192.11.13.6. Press Enter. 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. To stop the ping, type ctrl c. Press Enter. 6. Close the MS-DOS window.

To access the media server: 1. Start the Web browser. 2. In the Address field, type 192.11.13.6. Press Enter to open the login Web page. 3. Log in as craft or dadmin.
Issue 2.1 June 2006
157
4. Select yes to suppress alarms The system displays the Integrated Management Standard Management Solutions Maintenance Web page. 5. Click Launch Maintenance Web Interface to go to the main menu.
Backing up files on the standby media server

To back up the system configuration files on the standby media server: 1. Under Data Backup/Restore, select Backup Now. 2. Select the data sets, including Avaya Call Processing (ACP) translations, and the backup method.
!
Important:
Important: Do not select Full Backup or Save ACP translations prior to backup because you cannot save translations on a standby media server.
3. Click Start Backup to start the back up process. Wait until the backup is complete.

Copying preupgrade service pack(s) to the standby media server

Copy the preupgrade service pack(s) from the computer to the media server. To copy files to the media server, complete the following steps: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im 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 media server. 4. Click Download to copy the file(s) to the media server. The system copies files automatically to the default file location.
! CAUTION:
CAUTION:

Busying out the standby media server
To busy out the media server: 1. On the Maintenance Web page, under Server, select Busy-Out Server. Then click Busy Out to busy out the standby server. 2. Click Status Summary to verify that the standby server is busied out.
Issue 2.1 June 2006
159
Checking the software release on the standby media server

Check the version of Communication Manager to ensure you install the correct preupgrade service pack. For more information, see Preupgrade service pack on page 144 Under Server, click Software Version to see what software release is on the media server.
Installing the preupgrade service pack

You must install the preupgrade service packs that are applicable to Release 1.2 or 1.3 of Communication Manager before you back up the system files. To install a Communication Manager service pack: 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. To access the ftp directory, type cd /var/home/ftp and press Enter 4. To list files in the ftp directory, type ls -ltr at the prompt, and press Enter. The media server displays a list of the files in the ftp directory. 5. Verify that the directory contains the *.tar.gz files that you have uploaded. 6. Type sudo patch_install patch.tar.gz, where patch is the release number or the issue number of the service pack file, such as, 03.0.526.5-xxxx.tar.gz. Press Enter. 7. Repeat step 6 for second service pack if required. 8. Type patch_show and press Enter to list the service pack files that are installed on the media server. Verify that the new files are installed. 9. Type sudo patch_apply patch, where patch is the release or issue number of the service pack that you just installed, such as, 03.0.526.5-xxxx. Do not use the *.tar.gz extension at the end of the file name. Press Enter. The media server goes through a software reset system 4. 10. Type statapp -c and press Enter. You can view the processes as they refresh and progress. Verify that every process says Up and Standby before you type additional commands. To stop the continual refresh, press ctrl c. 11. To list Communication Manager files, type patch_show again and press Enter. Verify the new service packs are applied.
Verifying connectivity to customer network server

Avaya does not recommend that you back up the files to a server on the customer network. However if you do so, you must verify that you can access that server by pinging it. If ping is disabled on the network, you cannot ping the server nor back up files to the network server. In this case, you must work with the customer network administrator to determine the best way to back up files. Note: The recommended method for a backup uses a PCMCIA flashcard. 1. Under Diagnostics, click Execute Ping. 2. Type the IP address of the server where the system files are to be stored and click Execute Ping. If you can successfully ping the server, back up the files.
Note:
Backing up the system files with Linux MigrationBackup

After you install the preupgrade service pack, you must back up the files so that you can restore the files later.
! CAUTION:
CAUTION:
When you remaster the hard disk, the NIC port (previously assigned as Eth4 for Multiconnect and Eth0 for IP-connect) for the customer network does not work. Therefore, before you can restore the backed up files from the customer network, you must reconfigure the Ethernet port. The preferred option for backing up files is to use the PCMCIA flashcard.
! CAUTION:
CAUTION:
Use the new menu item under Server Configuration and Upgrades titled Linux MigrationBackup. Note: Restart your browser before you do the next steps.
Note:
To back up the system files onto the PCMCIA flashcard: 1. Place the PCMCIA flashcard into the bottom slot of the PCMCIA drive in the media server.
Issue 2.1 June 2006
161
2. Under Server Configuration and Upgrades, click Linux MigrationBackup.
3. Select Initiate new backup and click Submit.
4. Select Local PC card and type 1 or a higher number in the Retain data sets at destination field. If you must back up to a server on the customer network, select FTP. Complete the User Name, Password, Host Name for host IP address, and the Directory fields for where you want to back up the files.
5. Click Submit.
6. Click Status to view the Backup History. Note: The backup status function for the Linux Migration is not enabled for Release 1.3.1. To check the backup status when you upgrade from Release1.3.1, under Data Backup/Restore, select Backup Status. Then select the backup set and click Check Status. 7. Select the box next to the file that is being backed up and click Check Status. When the backup is complete, the system displays the following message: Backup is finished
Note:
!
Important:
Important: Check the text to verify that no error messages exist.
Setting Telnet parameters

Note:
Note: Use a telnet session to access the information on the CD-ROM.
You can set the Microsoft Telnet application to send a carriage return (CR) and a line feed (LF) whenever you press Enter. The installation program sees this single key press as two key presses. If you are running Windows 2000 or Windows XP, you must undo this setting before you copy the Remaster Program to the hard disk drive. To configuring telnet for Windows 2000/XP, perform the following steps: 1. Click Start > Run to open the Run dialog box. 2. Type telnet and press Enter to open a Microsoft Telnet session. 3. Type display and press Enter to see the current settings.
Issue 2.1 June 2006
163

If the message says Sending only CR, close the dialog box. If the message says Sending both CR & LF, continue with step 5.
5. Type unset crlf and press Enter. 6. Type display and press Enter to verify that the settings changed. The system displays the following message: Sending only CR 7. Close the dialog box. Note:
Note:
Erasing the MBR on the media server

To erase the master boot record (MBR): 1. Click Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6 and press Enter. 3. Log in as craft or dadmin. 4. Type sudo erase_mbr and press Enter to erase the MBR. 5. When the system displays the message, WARNING: Are you sure you want to erase the master boot record? (y/n) [n], type y for yes. 6. Type quit to end the telnet session.

Note:
Rebooting the standby media server

!
Important:
Important: When you shut down the media server, you lose access to the Maintenance Web Interface.
The following steps reboots the media server. 1. On the Web Interface under Server, click Shutdown Server. 2. Select Immediate Shutdown now and Restart server after shutdown. 3. Click Shutdown Server.


Issue 2.1 June 2006
165
Installing Communication Manager

Use a telnet session to install Communication Manager. To install Communication Manager: 1. From the laptop Start menu, click Start > Run. 2. In the Run dialog box, type telnet 192.11.13.6. Press Enter to view the first screen.
Note:
Note: To navigate on these screens, use the arrow keys to move to an option, and then press the spacebar to select the option. Press Enter to submit the screen. 3. Select Install, ensure that OK is highlighted. Press Enter.
4. On the Select Release Version window, ensure that the Build line and OK are highlighted. Press Enter to partition the hard disk and reformat the partitions. Once the drive is configured correctly, the program starts the installation process and reports the progress.
These processes can take up to 20 minutes. When the media server is ready to reboot, the CD-ROM drive drawer opens. Remove the CD-ROM from the drive at this time. The reboot can take up to 3 minutes. The Telnet session ends automatically.

Issue 2.1 June 2006
167



Selecting media server type

You must select the media server type. 1. Under Server Configuration click Configure Server to open the Select server type page of the Configure Server process. If you selected the server type earlier, you do not see this screen.
2. Select the appropriate server type and click Continue.
Configuring the network parameters (optional)

Note:
Note: If you backed up the system files to the flashcard, do not perform this procedure. Continue with Installing postupgrade service pack, if any, on media server on page 171. If you backed the system files up to the customer network, you must readminister the Ethernet port that connects to the customer network. You must have the following information for the two media servers and the active server: - Host name - IP address - Subnet mask - Default gateway In addition, you need the IP address for the Ethernet port connecting to the customer network.
Issue 2.1 June 2006
169
Because the software upgrade destroyed the configuration data, you must configure the network parameters before restoring the backup files. 1. Under Server Configuration click Configure Server to open the first page. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page.
3. Select Configure individual services and click Continue. 4. Select Configure Interfaces from the menu on the left. 5. Fill in the following data for the Ethernet port, which can be Eth 0 for IP-PNC and Eth 4 for fiber-PNC:

The IP address The Gateway The Subnet mask (or use the default addresses)
6. Select AUTOSENSE for the speed. Click Change to update and reboot the media server. When the screen displays Successfully configured the ethernet interfaces. the Ethernet ports are configured. 7. Click Close Window to close the Configure Server wizard.
Verifying connectivity to the network server (optional)

Note:
Note: If you backed up the system files to the flashcard, do not perform this procedure. Continue with Installing postupgrade service pack, if any, on media server on page 171.
You must verify that the Ethernet port is working. From the media server, ping the network server on which the backup files are stored. Note: You might need to restart your browser before you perform this procedure. 1. Under Diagnostics click Ping. 2. Type the IP address of the server where the system files are stored and click Execute Ping. If you can successfully ping the server, restore the backed up Linux migration files.
Note:

Note:
To install a post-upgrade service pack. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Log in as craft. 3. Type update_unpack and press Enter. 4. Select the update by number and press Enter. 5. Type update_show and press Enter to list Communication Manager files to verify that the new software update file was unpacked. 6. Type update_activate update, where update is the update ID number produced by update_show. An example can be 00.0.628.x-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot with an automatic reset system 4 command. If the system reboots, it might also display the message /opt/ecs/sbin/drestart 2 4 command failed.
Issue 2.1 June 2006
171
Ignore this message. You must wait until the restart or the reset is complete before you enter additional commands. The media server displays a message that the service pack was applied. 7. Type update_show again and press Enter to list Communication Manager files to verify that the new service pack file is activated.
Verifying installation of the service pack

To show the latest service pack: 1. Under Server click Software Version. 2. Verify that the new service pack is listed. Note: You usually select the Make Upgrade Permanent function on the Maintenance Web Interface at this point. However, this is not necessary for this upgrade because there is no previous software version in the alternate partition.
Note:
Restoring the Linux migration backup files

! CAUTION:
CAUTION:
You must run the restore only once. If you run restore more than once, you might corrupt the system data. If a restore appears to be incomplete, check the Backup History Log and the Backup Log on the Maintenance Web Interface. Also check the system log in the bash command line interface. If all sources indicate that a restore has not completed, you can safely rerun the restore.
To restore backed up system files: 1. Under Data Backup/Restore, click View/Restore Data.

If you backed up to a PCMCIA flashcard, select Local PC Card. If you backed up to a server on the customer network, select FTP. Then complete the User Name, Password, Host Name, and the Directory fields for the location of the backup files. The Host Name field must use the host IP address.
3. Select the backup file to restore. The file name starts with /upgrade-2.0_. Select Force restore if server name mismatch and Force restore if backup version mismatch. 4. Click Restore to restore all the system files. 5. Click Restore Status.
Issue 2.1 June 2006
173
6. Select the first file. Then scroll down and click Review Status to see the results of the restore. When restore finishes, the screen displays Restore is finished. 7. Type drestart 1 4 and press Enter to load the restored translations.
!
Important:
Important: If the restore process fails, the system displays a message that states the reason for the failure and the translation file is not restored. You must resolve the reason for the failure and restart the process.
Verifying date and time

To verify the time and date. 1. Under Server, click Server Date/Time.
2. Verify that the date, the time, and the time zone are correct. Make changes as necessary. 3. If you make changes, click Submit.


To check the system status: 1. Under Server, click Status Summary. 2. Verify the following information:

Standby Refreshed is set to Yes Standby Shadowing is set to On Duplication Link is set to Up
Releasing the standby media server

To release the media server from busyout mode: 1. Under Server, click Release Server. 2. To verify that the standby server is no longer busied out, click Status Summary.
Interchanging the media servers

To interchange the active and standby media servers: Note: For Communication Manager Release 3.0 and earlier, interchanging the media servers does not preserver calls. The Communication Manager reset is equivalent to a reset system 4. However, if you are upgrading a Release 3.0.1 system and you performed the Pre Upgrade Step, most stable calls are preserved. Unstable calls and DCS or SIP calls are dropped.
Note:
Issue 2.1 June 2006
175
1. Select Status Summary, and check that the Standby Refreshed field says yes. 2. Under Server, click Interchange Servers. 3. To preserve connections during the upgrade, do no select Force interchange regardless of server status. However, if you must proceed regardless of connections being dropped, you can select this field. 4. To make the newly upgraded standby server the new active server, click Interchange. 5. To verify that the media server you are connected to is the active server, click Status Summary. Note: At this point, the media servers are on different software loads. Therefore, for servers upgrading from Communication Manager release 3.0 and earlier, Standby Refreshed is no and Standby Shadowing is off. For release 3.0.1 servers, these fields show yes and on respectively.
Note:
Installing the new license and Avaya authentication files on newly active media server
Note:
Note: You must install the license file on an active media server and before you install the Avaya authentication file. If the license is installed on the standby media server, 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 media server: Note: The media 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. The system displays a message that tells you the license is installed successfully. 3. Under Security, click Authentication File. 4. Click Install the Authentication file I previously downloaded and click Install. The system displays a message that tells you the authentication file is installed successfully.
Note:
Upgrade tasks (second media server)


Copying preupgrade service pack(s) to the standby media server

Copy the preupgrade service pack(s) from the computer to the media server. To copy files to the media server, complete the following steps: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im 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 media server. 4. Click Download to copy the file(s) to the media server. The system copies files automatically to the default file location.

To busy out the media server. 1. Under Server, select Busy-Out Server. Then click Busy Out to busy out the standby server. 2. Click Status Summary to verify that the standby server is busied out.
Issue 2.1 June 2006
177

Installing the preupgrade service pack

You must install the preupgrade service packs that are applicable to Release 1.2 or 1.3 of Communication Manager before you back up the system files. To install a Communication Manager service pack: 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. To access the ftp directory, type cd /var/home/ftp and press Enter 4. To list files in the ftp directory, type ls -ltr at the prompt, and press Enter. The media server displays a list of the files in the ftp directory. 5. Verify that the directory contains the *.tar.gz files that you have uploaded. 6. Type sudo patch_install patch.tar.gz, where patch is the release number or the issue number of the service pack file, such as, 03.0.526.5-xxxx.tar.gz. Press Enter. 7. Repeat step 6 for second service pack if required. 8. Type patch_show and press Enter to list the service pack files that are installed on the media server. Verify that the new files are installed. 9. Type sudo patch_apply patch, where patch is the release or issue number of the service pack that you just installed, such as, 03.0.526.5-xxxx. Do not use the *.tar.gz extension at the end of the file name. Press Enter. The media server goes through a software reset system 4. 10. Type statapp -c and press Enter. You can view the processes as they refresh and progress. Verify that every process says Up and Standby before you type additional commands. To stop the continual refresh, press ctrl c. 11. To list Communication Manager files, type patch_show again and press Enter. Verify the new service packs are applied.
Verifying connectivity to customer network server (optional)

Avaya does not recommend that you back up the files to a server on the customer network. However if you do so, you must verify that you can access that server by pinging it. If ping is disabled on the network, you cannot ping the server nor back up files to the network server. In this case, you must work with the customer network administrator to determine the best way to back up files. Note: The recommended method for a backup uses a PCMCIA flashcard. 1. Under Diagnostics, click Execute Ping. 2. Type the IP address of the server where the system files are to be stored and click Execute Ping. If you can successfully ping the server, back up the files.
Note:
Backing up the system files using Linux MigrationBackup

After you install the preupgrade service pack, you must back up the files so that you can restore the files later.
! CAUTION:
CAUTION:
When you remaster the hard disk, the NIC port (previously assigned as Eth4 for Multiconnect and Eth0 for IP-connect) for the customer network does not work. Therefore, before you can restore the backed up files from the customer network, you must reconfigure the Ethernet port. The preferred option for backing up files is to use the PCMCIA flashcard.
! CAUTION:
CAUTION:
Use the new menu item under Server Configuration and Upgrades titled Linux MigrationBackup. Note: Restart your browser before you do the next steps.
Note:
To back up the system files onto the PCMCIA flashcard: 1. Place the PCMCIA flashcard into the bottom slot of the PCMCIA drive in the media server.
Issue 2.1 June 2006
179
2. Under Server Configuration and Upgrades, click Linux MigrationBackup.
3. Select Initiate new backup and click Submit.
4. Select Local PC card and type 1 or a higher number in the Retain data sets at destination field. If you must back up to a server on the customer network, select FTP. Complete the User Name, Password, Host Name for host IP address, and the Directory fields for where you want to back up the files.
5. Click Submit.
6. Click Status to view the Backup History. Note: The backup status function for the Linux Migration is not enabled for Release 1.3.1. To check the backup status when you upgrade from Release1.3.1, under Data Backup/Restore, select Backup Status. Then select the backup set and click Check Status. 7. Select the box next to the file that is being backed up and click Check Status. When the backup is complete, the system displays the following message: Backup is finished
Note:
!
Important:
Important: Check the text to verify that no error messages exist.
Erasing the MBR on the standby media server

To erase the master boot record (MBR): 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 or dadmin. 3. To erase the MBR, type sudo erase_mbr and press Enter. 4. When the system displays the message WARNING: Are you sure you want to erase the master boot record? (y/n) [n] , type y for yes. 5. Type quit to end the telnet session.
Issue 2.1 June 2006
181

Note:
Rebooting the standby media server

!
Important:
Important: When you shut down the media server, you lose access to the Maintenance Web Interface.
The following steps reboots the media server. 1. On the Web Interface under Server, click Shutdown Server. 2. Select Immediate Shutdown now and Restart server after shutdown. 3. Click Shutdown Server.



Note:
Issue 2.1 June 2006
183
These processes can take up to 20 minutes. When the media server is ready to reboot, the CD-ROM drive drawer opens. Remove the CD-ROM from the drive at this time. The reboot can take up to 3 minutes. The Telnet session ends automatically.




Selecting media server type

Note:
Note: If you did not perform the previous task, you must select the media server type before you install the postupgrade patch.
Issue 2.1 June 2006
185
To determine the media server type: 1. Under Server Configuration, click Configure Server to open the Select server type page of the Configure Server process. If you selected the server type earlier, you do not see this screen.
2. Select the appropriate server type and click Continue.
Configuring the network parameters (optional)

Note:
Note: If you backed up the system files to the flashcard, do not perform this procedure. Continue with Installing postupgrade service pack, if any, on media server on page 171. If you backed the system files up to the customer network, you must readminister the Ethernet port that connects to the customer network. You must have the following information for the two media servers and the active server: - Host name - IP address - Subnet mask - Default gateway In addition, you need the IP address for the Ethernet port connecting to the customer network.
Because the software upgrade destroyed the configuration data, you must configure the network parameters before restoring the backup files. 1. Under Server Configuration click Configure Server to open the first page. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page.
3. Select Configure individual services and click Continue. 4. Select Configure Interfaces from the menu on the left. 5. Fill in the following data for the Ethernet port, which can be Eth 0 for IP-PNC and Eth 4 for fiber-PNC:

The IP address The Gateway The Subnet mask (or use the default addresses)
6. Select AUTOSENSE for the speed. Click Change to update and reboot the media server. When the screen displays Successfully configured the ethernet interfaces. the Ethernet ports are configured. 7. Click Close Window to close the Configure Server wizard.
Issue 2.1 June 2006
187
Verifying connectivity from the network server

After you configure the S8700 Media Server, the virtual or shared IP address of the server pair might not be immediately available to the customer network. 1. Obtain the virtual IP address from the Configure Server: Configure Interfaces Web page. Record the IP address in the IP address for active server field. 2. From the gateway server for the S8700 Media Server, ping the virtual IP address.
Verifying connectivity to the network server (optional)

Note:
Note: If you backed up the system files to the flashcard, do not perform this procedure. Continue with Installing postupgrade service pack, if any, on media server on page 171.
You must verify that the Ethernet port is working. From the media server, ping the network server on which the backup files are stored. Note: You might need to restart your browser before you perform this procedure. 1. Under Diagnostics click Ping. 2. Type the IP address of the server where the system files are stored and click Execute Ping. If you can successfully ping the server, restore the backed up Linux migration files.
Note:

Note:
To install a post-upgrade service pack. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Log in as craft. 3. Type update_unpack and press Enter.
4. Select the update by number and press Enter. 5. Type update_show and press Enter to list Communication Manager files to verify that the new software update file was unpacked. 6. Type update_activate update, where update is the update ID number produced by update_show. An example can be 00.0.628.x-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot with an automatic reset system 4 command. If the system reboots, it might also display the 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 media server displays a message that the service pack was applied. 7. Type update_show again and press Enter to list Communication Manager files to verify that the new service pack file is activated.
Verifying service pack installation

To show the latest service pack: 1. Under Server click Software Version. 2. Verify that the new service pack is listed. Note: You usually select the Make Upgrade Permanent function on the Maintenance Web Interface at this point. However, this is not necessary for this upgrade because there is no previous software version in the alternate partition.
Note:
Issue 2.1 June 2006
189
Restoring the Linux migration backup files

! CAUTION:
CAUTION:
You must run the restore only once. If you run restore more than once, you might corrupt the system data. If a restore appears to be incomplete, check the Backup History Log and the Backup Log on the Maintenance Web Interface. Also check the system log in the bash command line interface. If all sources indicate that a restore has not completed, you can safely rerun the restore.
To restore backed up system files: 1. Under Data Backup/Restore, click View/Restore Data.

If you backed up to a PCMCIA flashcard, select Local PC Card. If you backed up to a server on the customer network, select FTP. Then complete the User Name, Password, Host Name, and the Directory fields for the location of the backup files. The Host Name field must use the host IP address.
3. Select the backup file to restore. The file name starts with /upgrade-2.0_. Select Force restore if server name mismatch and Force restore if backup version mismatch. 4. Click Restore to restore all the system files. 5. Click Restore Status.
6. Select the first file. Then scroll down and click Review Status to see the results of the restore. When restore finishes, the screen displays Restore is finished. 7. Type drestart 1 4 and press Enter to load the restored translations.
!
Important:
Important: If the restore process fails, the system displays a message that states the reason for the failure and the translation file is not restored. You must resolve the reason for the failure and restart the process.

To verify the time and date. 1. Under Server, click Server Date/Time.
2. Verify that the date, the time, and the time zone are correct. Make changes as necessary. 3. If you make changes, click Submit.

Issue 2.1 June 2006
191



Disconnecting from the standby media server

Disconnect the laptop from the services port on the back of the standby media server.

Postupgrade tasks
Verifying the operation of the media servers

To verify the operation of the media servers: 1. Click View Summary Status and verify that the following fields show the values as indicated:

Duplicated? yes Standby Busied? no Standby Refreshed? yes Standby Shadowing: on Duplication Link: up
Postupgrade tasks
Note:
Note: Tasks Enabling scheduled maintenance with SAT on page 193 through on page 194 use SAT commands on the active media server.

Releasing MMI circuit packs with SAT (duplicated control network only)
Type release board UUCSS and press Enter to release the circuit packs that you busied out in the on page 153 section.
Issue 2.1 June 2006
193


Resolving alarms

Postupgrade tasks
Note:

Logging off all administration applications on the active media server

When you have completed all the administration, log off all the applications used.

Issue 2.1 June 2006
195


!
Important:

Postupgrade tasks
!
Important:
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 (media server) with SSH. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Type telnet IPaddress, where IPaddress is the IP address of the S8300 or S8500 LSP, or the S8500 or S8700-series ESS. 3. Log in as craft or dadmin. 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 Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, or Using the Avaya Enterprise Survivable Server (ESS), 03-300428.
Logging off all administration applications on the standby media server

Issue 2.1 June 2006
197

Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface
Use this procedure to upgrade Avaya Communication Manager on an S8700-series Media Server running Release 2.x, 3.0, or 3.1 of Avaya Communication Manager. The procedures, except as noted later in this module, apply to either a main server or an Enterprise Survivable Server (ESS). If the media server is running Release 2.1 or later, you might use the Upgrade Tool. For more information, see Using the Upgrade Tool to upgrade Communication Manager on Avaya S8700-Series Media Server.
! CAUTION:
CAUTION:
!
Important:
Important: An upgrade from Release 2.x to Release 3.1 or later requires that you install a preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 3.1. For more information, see Preupgrade service pack for upgrades starting from R2.x only on page 201.
An upgrade from Release 2.x to Release 3.1 requires an updated license file. Upgrading from Release 3.0 does not require an updated license, unless certain new features are also being purchased. For more information, see License and Avaya authentication files on page 70.
Issue 2.1 June 2006
199
Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/
! CAUTION:
CAUTION:
!
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 3.1. However, you can migrate the MBSs to Enterprise Survivable Servers (ESSs). For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428).
Although you always upgrade Communication Manager on a busied-out standby media server, you can access SAT commands only on the active media server. Some preupgrade steps are done on the active media server first, then you move to the standby media server for the actual software upgrade. Some post-upgrade steps are done on the active media server, also.
! CAUTION:
CAUTION:
Rebooting an active media server causes a service interruption. Ensure that you are on a busied out, standby media server when upgrading the software.
Prerequisites
You 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 68.

Prerequisites

! CAUTION:
CAUTION:
Upgrade of H.248 media gateways, LSPs and ESSs, if being used

Note:
Note: Do not perform these tasks and go to Connecting to the active media server on page 210 if the customer has none of the following network elements: - H.248 media gateways - Enterprise Survivable Servers (ESSs) - Local survivable processors (LSPs)
You must upgrade Communication Manager on the S8300 and S8500 LSPs before you upgrade Communication Manager on the primary controller. If the configuration uses G250, G350, or G700 Media Gateways, you must upgrade them to the latest firmware. If the media server supports ESSs, you must upgrade the ESSs before you upgrade the primary controller.
Issue 2.1 June 2006
201
The correct order is: 1. If the system includes one or more LSPs, upgrade Communication Manager on the S8300 or S8500 LSP to the latest version. 2. Upgrade the firmware on the media gateway and the media modules to the latest version. 3. If using ESSs, upgrade Communication Manager on the S8500 or S8700-series ESS to the latest version. 4. Upgrade Communication Manager on the S8500 or S8700-series primary controller to the latest version.

Note:


Before you upgrade the S8700-series Media 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 media 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.
Prerequisites
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.
Upgrade firmware on media gateways and media modules

You can use the Upgrade Tool to upgrade the firmware on all the media gateways and media modules. However, to use the tool, the firmware files must be resident on the S8300. For more information on the firmware upgrade process, see Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100).

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. 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. 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.
Issue 2.1 June 2006
203
Upgrade tasks for the S8700-series Media Server as main server

Preupgrade tasks:
Stopping call processing on the LSPs or ESSs if being used (main server only) on page 209 Connecting to the active media server on page 210 Starting a SAT session on page 210 Checking link status with SAT (main server only) on page 210 Recording all busyouts on page 211 Checking synchronization with the SAT (main server only) on page 211 Disabling scheduled maintenance with the SAT (main server only) on page 211 Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 212 Checking for translation corruption on page 212 Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 213 Accessing the media server maintenance web interface on page 213 Copying files to the media server on page 214 Resolving alarms on page 214 Backing up recovery system files on page 214 Verifying the backup on page 215 Suppressing alarming on page 215 Disconnecting from the active media server on page 216 Connecting to the standby media server on page 216 Clearing the ARP cache on the laptop computer on page 216 Accessing the media server maintenance web interface on page 217 Copying files to the media server on page 217 Backing up files on the standby media server on page 218 Verifying the backup on page 218 Suppressing alarming on page 218
Upgrade tasks for the S8700-series Media Server as main server
Tasks to preserve connections when starting from R3.0.1 only (main server only):

Disconnecting from the standby media server on page 219 Connecting to the active media server on page 219 Accessing the media server maintenance web interface on page 219 Selecting the Preupgrade Step to preserve calls on page 220 Disconnecting from the active media server on page 221 Connecting to the standby media server on page 221
Upgrade tasks for the first media server:

Busying out the standby media server on page 221 Checking the software release on the media server, if starting from R2.x only on page 221 Activating the preupgrade service pack on the media server (R2.x only) on page 222 Inserting the Communication Manager CD-ROM into the media server on page 223 Copying Communication Manager to the media server on page 223 Installing Communication Manager on the media server on page 225 Rebooting the media server on page 227 Verifying reboot progress on page 228 Verifying software operation on page 229 Checking system status on page 229 Making the upgrade permanent on the media server on page 229 Installing postupgrade service pack, if any, on media server on page 230 Releasing the standby media server on page 230 Interchanging the media servers on page 231 Installing the new license and Avaya authentication files on newly active media server on page 232 Disconnecting from the newly active media server on page 232
Upgrade tasks for the second media server:

Connecting to the standby media server on page 233 Accessing the media server maintenance web interface on page 233 Busying out the standby media server on page 233 Checking the software release on the media server (R2.x only) on page 234 Activating the preupgrade service pack on the media server (R2.x only) on page 234 Inserting the Communication Manager CD-ROM into the media server on page 235
Issue 2.1 June 2006
205
Copying Communication Manager to the media server on page 235 Installing Communication Manager on the media server on page 236 Rebooting the media server on page 239 Verifying reboot progress on page 240 Verifying software operation on page 241 Checking system status on page 241 Making the upgrade permanent on the media server on page 241 Installing postupgrade service pack, if any, on media server on page 242 Releasing the standby media server on page 242 Disconnecting from the standby media server on page 243 Connecting to the active media server on page 243 Verifying the operation of the media servers on page 243 Copying IP telephone firmware to the media server, if necessary (main server only) on page 243
Post-Upgrade tasks:
Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 244 Enabling scheduled maintenance with SAT on page 245 Releasing MMI circuit packs in duplicated control network using SAT, (main server only) on page 245 Busying out previously busied out trunks on page 245 Checking for translation corruption with SAT (main server only) on page 245 Resolving alarms on page 246 Backing up translations on page 246 Releasing alarm suppression (optional) on page 247 Logging off all administration applications on the active media server on page 247 Disconnecting from the active media server on page 247 Connecting to the standby media server on page 247 Backing up files on the standby media server on page 248 Releasing alarm suppression (optional) on page 248 Starting call processing on the LSPs and ESSs, if any (main server only) on page 248 Logging off all administration applications on page 249 Registering Avaya Communication Manager on page 249
Upgrade tasks (S8700-series Media Server as ESS)
Upgrade tasks (S8700-series Media Server as ESS)

Preupgrade tasks:

Connecting to the active media server on page 210 Starting a SAT session on page 210 Accessing the media server maintenance web interface on page 213 Copying files to the media server on page 214 Resolving alarms on page 214 Backing up recovery system files on page 214 Verifying the backup on page 215 Suppressing alarming on page 215 Disconnecting from the active media server on page 216 Connecting to the standby media server on page 216 Clearing the ARP cache on the laptop computer on page 216 Accessing the media server maintenance web interface on page 217 Copying files to the media server on page 217 Backing up files on the standby media server on page 218 Verifying the backup on page 218 Suppressing alarming on page 218
Upgrade tasks for the first media server:

Busying out the standby media server on page 221 Checking the software release on the media server, if starting from R2.x only on page 221 Activating the preupgrade service pack on the media server (R2.x only) on page 222 Inserting the Communication Manager CD-ROM into the media server on page 223 Copying Communication Manager to the media server on page 223 Installing Communication Manager on the media server on page 225 Rebooting the media server on page 227 Verifying reboot progress on page 228 Verifying software operation on page 229 Checking system status on page 229 Making the upgrade permanent on the media server on page 229
Issue 2.1 June 2006
207
Installing postupgrade service pack, if any, on media server on page 230 Releasing the standby media server on page 230 Interchanging the media servers on page 231 Installing the new license and Avaya authentication files on newly active media server on page 232 Disconnecting from the newly active media server on page 232
Upgrade tasks for the second media server:

Connecting to the standby media server on page 233 Accessing the media server maintenance web interface on page 233 Busying out the standby media server on page 233 Checking the software release on the media server (R2.x only) on page 234 Activating the preupgrade service pack on the media server (R2.x only) on page 234 Inserting the Communication Manager CD-ROM into the media server on page 235 Copying Communication Manager to the media server on page 235 Installing Communication Manager on the media server on page 236 Rebooting the media server on page 239 Verifying reboot progress on page 240 Verifying software operation on page 241 Checking system status on page 241 Making the upgrade permanent on the media server on page 241 Installing postupgrade service pack, if any, on media server on page 242 Releasing the standby media server on page 242 Disconnecting from the standby media server on page 243 Connecting to the active media server on page 243 Verifying the operation of the media servers on page 243
Post-Upgrade tasks:

Resolving alarms on page 246 Backing up translations on page 246 Releasing alarm suppression (optional) on page 247 Logging off all administration applications on the active media server on page 247 Disconnecting from the active media server on page 247 Connecting to the standby media server on page 247
Preupgrade tasks
Backing up files on the standby media server on page 248 Releasing alarm suppression (optional) on page 248 Logging off all administration applications on page 249 Registering Avaya Communication Manager on page 249
Preupgrade tasks
This procedure is optional. To stop Communication Manager on an LSP or ESS: 1. Connect to the services port (2) on the back of the main media 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. The login prompt for the LSP or ESS appears. 4. Log in to the LSP or ESS as craft. 5. Type stop -afcn and press Enter to stop potential call processing on the LSP or ESS. The LSP or ESS shuts down Communication Manager. 6. Repeat steps 1 through 5 for each LSP or ESS.
! CAUTION:
CAUTION:
Issue 2.1 June 2006
209


To 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: You must use SAT commands on the active server to complete the tasks Checking link status with SAT (main server only) on page 210 through Checking for translation corruption on page 212.
Note:


Preupgrade tasks



Issue 2.1 June 2006
211
! CAUTION:
CAUTION:

Preupgrade tasks

Issue 2.1 June 2006
213


Resolving alarms

Preupgrade tasks
Note:

! CAUTION:
CAUTION:
Issue 2.1 June 2006
215




Preupgrade tasks



Issue 2.1 June 2006
217

!
Important:

! CAUTION:
CAUTION:
To suppress alarming: 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. 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.
If you are on site, unplug the laptop from the services port on the back of the standby media server.


Issue 2.1 June 2006
219
Selecting the Preupgrade Step to preserve calls

To preserve calls during the interchange step in the upgrades: 1. Under Server Upgrade, click Pre Upgrade Step. The system displays the Pre Upgrade Step window.
2. On the Pre Upgrade Step window, 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.
Upgrade tasks for the first media server



Checking the software release on the media server, if starting from R2.x only
Check the version of Communication Manager to ensure that you install the correct preupgrade service pack. For more information, see Preupgrade service pack for upgrades starting from R2.x only on page 201. Under Server, click Software Version to see what software release is on the media server.
Issue 2.1 June 2006
221
Activating the preupgrade service pack on the media server (R2.x only)

Note:
! CAUTION:
CAUTION:

To copy Communication Manager to the media server: 1. On the browser toolbar, click Refresh to reload the current page.
Issue 2.1 June 2006
223
2. Under Server Upgrades, select Manage Software.
!
Important:
If fewer than 3 releases resides on the hard disk a. Select Copy a release to the local hard drive, but do not install it. Click Continue to view the options for copying the software to the hard disk. b. Select Copy from this servers 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. When complete, the system displays the following message: Success g. Click Continue to return to the initial Manage Software page.

! CAUTION:
CAUTION:
To install Communication Manager on the media server: 1. On the browser toolbar, click Refresh to reload the current page. 2. Under Server Upgrades, click Manage Software.
Issue 2.1 June 2006
225
3. Select Install one of the following releases currently resident on the local hard drive: and click Continue. The Choose Software Web page appears. 4. Select the software release you want, and click Continue. The Choose License Source Web page appears. Choose License Source screen
5. If you have copied the license and authentication files to the server, select the following options: - I will supply the license/authentication files myself when prompted later in this process. - Update authentication information as well as license information. 6. Click Continue. The Review Notices Web page appears. 7. 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.
8. Click Continue. The Begin Installation Web page appears. The page summarizes the request you have made. 9. Click Continue. The Install in Progress Web page appears. The installation takes 10 to 20 minutes. The Install in Progress screen refreshes every 10 seconds or on demand by clicking the Refresh button. When complete, the Reboot Server Web page appears.

Note:
! CAUTION:
CAUTION:
Note:
Note:
Issue 2.1 June 2006
227
! CAUTION:
CAUTION:
DO NOT CLICK CANCEL past this point. Be patient. If the installation fails, a message appears on the Reboot in Progress screen. 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 screen. 6. Unless instructed in your planning documents to update the tripwire database, select Do not update the tripwire data base now and click Continue. The system displays the Installation Complete screen. 7. Click Close. You are returned to the main menu. 8. Go to Verifying software operation on page 229.






! CAUTION:
CAUTION:
Issue 2.1 June 2006
229

Note:

Interchanging the media servers

To interchange the active and standby media servers: Note: For Communication Manager Release 3.0 and earlier, interchanging the media servers does not preserver calls. The Communication Manager reset is equivalent to a reset system 4. However, if you are upgrading a Release 3.0.1 system and you performed the Pre Upgrade Step, most stable calls are preserved. Unstable calls and DCS or SIP calls are dropped. 1. Select Status Summary, and check that the Standby Refreshed field says yes. 2. Under Server, click Interchange Servers. 3. To preserve connections during the upgrade, do no select Force interchange regardless of server status. However, if you must proceed regardless of connections being dropped, you can select this field. 4. To make the newly upgraded standby server the new active server, click Interchange. 5. To verify that the media server you are connected to is the active server, click Status Summary. Note: At this point, the media servers are on different software loads. Therefore, for servers upgrading from Communication Manager release 3.0 and earlier, Standby Refreshed is no and Standby Shadowing is off. For release 3.0.1 servers, these fields show yes and on respectively.
Note:
Note:
Issue 2.1 June 2006
231
Installing the new license and Avaya authentication files on newly active media server
Note:
Note: You must install the license file on an active media server and before you install the Avaya authentication file. If the license is installed on the standby media server, 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 media server: Note: The media 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. The system displays a message that tells you the license is installed successfully. 3. Under Security, click Authentication File. 4. Click Install the Authentication file I previously downloaded and click Install. The system displays a message that tells you the authentication file is installed successfully.
Note:
Disconnecting from the newly active media server

If you are on site, unplug the laptop computer from the services port on the back of the newly active media server.
Upgrade tasks for the new standby media server (second server)



Issue 2.1 June 2006
233
Checking the software release on the media server (R2.x only)

Check the version of Communication Manager to ensure that you install the correct preupgrade service pack. See Preupgrade service pack for upgrades starting from R2.x only on page 201. Under Server click Software Version to see what software release is on the media server.
Activating the preupgrade service pack on the media server (R2.x only)

Note:

!
Important:
Issue 2.1 June 2006
235

! CAUTION:
CAUTION:
To install Communication Manager on the media server: 1. On the browser toolbar, click Refresh to reload the current page.
2. Under Server Upgrades, click Manage Software.
3. Select Install one of the following releases currently resident on the local hard drive: and click Continue. The Choose Software Web page appears. 4. Select the software release you want, and click Continue. The Choose License Source Web page appears.
Issue 2.1 June 2006
237
Choose License Source screen
5. If you have copied the license and authentication files to the server, select the following options: - I will supply the license/authentication files myself when prompted later in this process. - Update authentication information as well as license information. 6. Click Continue. The Review Notices Web page appears. 7. 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. 8. Click Continue. The Begin Installation Web page appears. The page summarizes the request you have made.
9. Click Continue. The Install in Progress Web page appears. The installation takes 10 to 20 minutes. The Install in Progress screen refreshes every 10 seconds or on demand by clicking the Refresh button. When complete, the Reboot Server Web page appears.

Note:
! CAUTION:
CAUTION:
Note:
Note:
Issue 2.1 June 2006
239
! CAUTION:
CAUTION:
DO NOT CLICK CANCEL past this point. Be patient. If the installation fails, a message appears on the Reboot in Progress screen. 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 screen. 6. Unless instructed in your planning documents to update the tripwire database, select Do not update the tripwire data base now and click Continue. The system displays the Installation Complete screen. 7. Click Close. You are returned to the main menu. 8. Go to Verifying software operation on page 241.






! CAUTION:
CAUTION:
Issue 2.1 June 2006
241

Note:



Verifying the operation of the media servers

To verify the operation of the media servers: 1. Click View Summary Status and verify that the following fields show the values as indicated:

Duplicated? yes Standby Busied? no Standby Refreshed? yes Standby Shadowing: on Duplication Link: up
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. 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 media server.
Issue 2.1 June 2006
243
Note:
Note: The IP telephone firmware that was originally downloaded is overwritten.
Post-Upgrade tasks
Note:
Note: You must use SAT commands on the active media server for the tasks Enabling scheduled maintenance with SAT on page 245 through on page 245.
Post-Upgrade tasks

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 212 section.

Checking for translation corruption with SAT (main server only)

To check for translation corruption: 1. 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 you continue the upgrade.
Issue 2.1 June 2006
245
Resolving alarms
Backing up translations
To back up translations: 1. S8710: Place a formatted flash card in the compact flash drive attached to a USB port. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Data Backup/Restore, click Backup Now. 6. Select the data sets and the backup method. If you select Save ACP translations prior to backup, the media server automatically saves the translations to the hard disk before the media server saves the translations to the backup media. 7. Click Start Backup to start the backup process.
Post-Upgrade tasks

Logging off all administration applications on the active media server



Issue 2.1 June 2006
247

!
Important:

Post-Upgrade tasks
!
Important:
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 (media server) with SSH. 1. Access the command line interface of the server with an SSH client like PuTTY and an IP address of 192.11.13.6. 2. Type telnet IPaddress, where IPaddress is the IP address of the S8300 or S8500 LSP, or the S8500 or S8700-series ESS. 3. Log in as craft or dadmin. 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 Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, or Using the Avaya Enterprise Survivable Server (ESS), 03-300428.


Issue 2.1 June 2006
249
Using the Upgrade Tool to upgrade Communication Manager on Avaya S8700-Series Media Server
Use this procedure to upgrade an existing S8700, S8710, or 8720 Media Server running Release 2.x, 3.0, or 3.1 of Avaya Communication Manager. This method uses the Upgrade Tool, available with Release 2.1 and later, and can include remote upgrades of any LSPs, ESSs, and H.248 media gateways. For more information about upgrading with the Maintenance Web Interface, see Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface.
! CAUTION:
CAUTION:
!
Important:
Important: An upgrade from Release 2.x to Release 3.1 or later requires that you install a preupgrade service pack before you upgrade Communication Manager. This service pack supports the upgrade to Release 3.1. For more information about which service pack to use, see Preupgrade service pack for upgrades starting from R2.x only on page 255.
An upgrade from Release 2.x to Release 3.1 requires an updated license file. Upgrading from Release 3.0 does not require an updated license, unless certain new features are also being purchased. For more information, see License and Avaya authentication files on page 70.
Issue 2.1 June 2006
251
! CAUTION:
CAUTION:
!
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 3.1. However, you can migrate the MBSs to Enterprise Survivable Servers (ESSs). For more information, see Avaya Enterprise Survivable Servers (ESS) User Guide (03-300428). Important: You cannot use the Upgrade Tool to upgrade the G150 Media Gateway or G250 Media Gateways. You must upgrade the G150 and G250 separately. For more information, see Installation and Configuration for the Avaya G150 Media Gateway (03-300395). Also, if you are upgrading an ESS by itself locally, you cannot use the Upgrade Tool. Instead, you must follow the procedures in Upgrading Communication Manager on Avaya S8700-series Media Servers or S8700-series ESS from R2.x/ R3.0 to R3.1 or from R3.1 to R3.1.x Using the Maintenance Web Interface on page 199.
!
Important:

Note:
Note: For information on using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheet (555-245-757) and the online Help.
With the Upgrade Tool, you can automatically and remotely upgrade the following software from the primary controller:
Communication Manager on the Local Survivable Processors (LSPs) and Enterprise Survivable Servers (ESSs). You can also use the tool to apply preupgrade and postupgrade service packs and licenses to the LSPs and ESSs. Firmware on the G350 or the G700 Media Gateways and most of the media modules that are resident in the media gateways. Communication Manager and preupgrade and postupgrade service packs and a license on the primary controller, if the primary controller is already running R2.1 or later.
With the Upgrade Tool, you do not have to physically be at the ESS, LSP, and media gateway locations to perform the upgrades. Additionally, you do not have to run the upgrades one by one. You can enter the needed information for all ESSs, LSPs and gateways into the Upgrade Tool, then run the Upgrade Tool. The tool automatically upgrades Communication Manager and firmware on all LSPs, ESSs, and G350/G700 Media Gateways. Note: ESSs and LSPs must be upgraded to the latest release of Communication Manager before you upgrade the primary controller to the latest release. To use the Upgrade Tool, the LSPs and the primary controller must be running Release 2.1 or later of Avaya Communication Manager.
Note:
Upgrade using the Upgrade Tool

Before you upgrade an ESS, LSP, or gateway, administer and register the ESS, LSP or media gateway with the primary controller. To check if a device is registered, use the Query Versions option on the Upgrade Tool navigation pane on the left side of the Upgrade Tool screens. The Query Versions screen shows an IP address next to each registered ESS, LSP, and gateway. The Upgrade Tool upgrades the components of a configuration in the following order:

All LSPs that you specify All ESSs that you specify The media gateways and the media modules The primary controller - Standby media server from the active media server - Newly standby media server, after interchange, from the newly active media server. For more information, see Process to upgrade the active and the standby media servers on page 254.
Issue 2.1 June 2006
253
Figure 1: Process to upgrade the active and the standby media servers
1 S8700 Server X (Active Server) Software on CD-ROM S8700 Server Y (Standby Server)
Software loaded from CD-ROM S8700 Server X (Active Server) Software on CD-ROM S8700 Server Y (Standby Server)
Software installed from active server
Interchange occurs
S8700 Server X (Standby Server) Software installed on standby server
Software on CD-ROM
S8700 Server Y (Active Server)
cydclspd LAO 031105
Run the Upgrade Tool from the active media server. The Upgrade Tool then upgrades each target LSP, the media gateways that you selected, and the standby media server. When these upgrades are complete and the standby media server reboots, an interchange occurs automatically. The standby media server then becomes active, and the active media server becomes the standby. The Upgrade Tool continues to run on the same media server as before the interchange and upgrades itself. The newly active media server remains active when the upgrades are complete. For the upgrades that you started before the interchange, no status data is available on the media server that is active after the interchange. The upgrade status data is available only on the media server on which the upgrade was started, which is now the standby media server. To view the current upgrade status after an interchange, log in to the physical IP address or the host name of the media server that you used to do the upgrade. Do not log in to the alias address or the alias name for the active media server. When you schedule further upgrade jobs, you must log in to the newly active media server to run the Upgrade Tool.
! CAUTION:
CAUTION:
After an interchange, do not start another upgrade on the newly active server until the current upgrade finishes. To see when the upgrade is complete, use the View Prior option of the Upgrade Tool from the server on which you started the upgrade.
Preserving connections during the upgrade

The Upgrade Tool automatically preserves connections that are preservable. You do not need to execute the Pre Upgrade Step in the Maintenance Web pages to preserve connections.
Prerequisites

During an upgrade, any data in the /tftpboot directory is overwritten with new software and firmware. 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. 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.
Prerequisites


! CAUTION:
CAUTION:
If the server has a Release 2.x field load other than those listed in the table, do not use this section to upgrade the server. You must escalate.
Issue 2.1 June 2006
255
Table 10: Software release and load Software release of the existing media server 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 Associated software load R012x.00.0.219.0 R012x.00.1.221.1 R012x.01.0.411.7 R012x.01.1.414.1 R012x.02.0.111.4 R012x.02.1.118.1 Service pack file name 00.0.219.0-xxxx.tar.gz 00.1.221.1-xxxx.tar.gz 01.0.411.7-xxxx.tar.gz 01.1.414.1-xxxx.tar.gz 02.0.111.4-xxxx.tar.gz 02.1.118.1-xxxx.tar.gz
Overview of the upgrade process

Because you cannot use the Upgrade Tool to upgrade the G150 and G250 Media Gateways, you must upgrade them separately. The upgrade process consists of the following high level steps: 1. Obtain the updated license files and preupgrade and postupgrade service packs for LSPs and the primary controller. Also, obtain firmware files for all G350 and G700 Media Gateways. 2. If LSPs or ESSs are used, prepare the LSPs and ESS for the upgrade:
Distribute Communication Manager software to the site of each LSP and ESS. You can distribute software with either of the following methods: - CD-ROMs that someone mails - Software someone copies to a TFTP or HTTP server, from which the LSP/ESS can download the software over the customer LAN.
Use the Maintenance Web Interface pages to copy the preupgrade service packs (R2.x only) to the primary controller (main server). Use the Upgrade Tool to install and activate the preupgrade service pack on any LSPs, ESSs, and the primary controller (R2.x only).
Upgrade tasks
Copy the new Communication Manager software to all the LSPs and ESSs with the Manage Software Web page. You can log in remotely to each LSP/ESS to copy software if one of the following tasks is done first: - Someone at each location inserts the software CD-ROM for you. - You loaded the software on a TFTP or HTTP server in the customer LAN.
3. Use the Maintenance Web Interface pages to copy the postupgrade service packs and license files of the LSPs, ESSs, and primary controller from one of the following devices: - Your laptop - An FTP server - Another means of transport onto the primary controller. 4. Copy the new Communication Manager software to the primary controller with the Manage Software Web page. 5. Start the Upgrade Tool to upgrade

Communication Manager, postupgrade service packs, and license files on the LSPs. The firmware on the G350 and G700 media gateways and media modules. Communication Manager, post-upgrade service packs, and license files on the ESSs. Communication Manager and post-upgrade service pack on the primary controller.
6. If installed, upgrade the G150 and G250 Media Gateways manually. You cannot use the Upgrade Tool to upgrade the G150 and G250 Media Gateways.
Upgrade tasks
Preupgrade tasks:

Connecting to the active media server on page 259 Starting a SAT session on page 259 Checking link status with SAT (main server only) on page 260 Recording all busyouts using SAT on page 260 Checking synchronization with the SAT (main server only) on page 260 Disabling scheduled maintenance with the SAT (main server only) on page 261 Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 261 Checking for translation corruption with SAT (main server only) on page 262
Issue 2.1 June 2006
257
Saving a copy of the 4600-series telephone configuration file, if any (main server only) on page 262 Accessing the media server maintenance web interface on page 263 Resolving alarms on page 263 Backing up recovery system files on the active server on page 263 Verifying the backup on page 264 Suppressing alarming on page 264 Disconnecting from the active media server on page 265 Connecting to the standby media server on page 265 Accessing the media server maintenance web interface on page 265 Backing up files on the standby media server on page 265 Verifying the backup on page 266 Suppressing alarming on page 266 Disconnecting from the standby media server on page 266 Connecting to the active media server on page 267 Accessing the media server maintenance web interface on page 267 Copying the service pack files to the media server, only if starting from R2.x on page 267 Installing the preupgrade software service pack (starting from R2.x only) on page 268 Copying files to the media server on page 268 Inserting the Communication Manager CD-ROM into the media server on page 269 Copying Communication Manager to the media server on page 270 Removing CD-ROM from the CD-ROM drive on page 271
Upgrade tasks:

Starting the Upgrade Tool on page 272 Installing Avaya authentication files on the active server, if required on page 273 Verifying software operation on page 274 Checking system status on page 274 Copying IP telephone firmware to the media server, if necessary (main server only) on page 274
Postupgrade tasks:
Restoring the 4600-series IP Telephone configuration file, if any (main server only) on page 275 Enabling scheduled maintenance with SAT on page 275
Releasing MMI using SAT on page 275 Busying out previously busied out trunks on page 276 Checking for translation corruption with SAT (main server only) on page 276 Resolving alarms on page 276 Backing up recovery system files on the active server on page 276 Releasing alarm suppression on the media server (optional) on page 277 Logging off all administration applications on page 277 Disconnecting from the active media server on page 277 Connecting to the standby media server on page 278 Backing up files on the standby media server on page 278 Releasing alarm suppression on the media server on page 278 Logging off the administration applications on the standby media server on page 278 Registering Avaya Communication Manager on page 279


To 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.
Issue 2.1 June 2006
259


Recording all busyouts using SAT

Type display errors and press Enter. Look for type 18 errors and record any trunks that are busied out, so you can return them to their busyout state after the upgrade.


! CAUTION:
CAUTION:
Issue 2.1 June 2006
261


Resolving alarms

Note:
To back up system configuration files: 1. Under Data Backup/Restore, click Backup Now. 2. Select the data sets. For the main server only, select Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. An ESS gets translations from the main server, so there is no reason to backup the translations on an ESS. Do not select Full Backup because this option does not save translations.
Issue 2.1 June 2006
263
Note:

! CAUTION:
CAUTION:




!
Important:
Issue 2.1 June 2006
265

! CAUTION:
CAUTION:



Copying the service pack files to the media server, only if starting from R2.x
To copy the service pack files to the media server, perform the following steps: Note: Do not perform this task if you are upgrading an R3.0 release to R3.1. 1. On the Maintenance Web Interface, under Miscellaneous, click Download Files. 2. Select the download method, Files to download from the machine Im using to connect to the server. Note: Do not select the check box, Install this file on the local server. 3. Browse to the directory on the laptop that contains the preupgrade service pack files. 4. Select the service pack files and click Download.
Note:
Note:
Issue 2.1 June 2006
267
Installing the preupgrade software service pack (starting from R2.x only)
Note:
Note: Do not perform this task if you are upgrading an R3.0 release to R3.1.
The preupgrade service pack modifies the server upgrade tools, including the Web Interface and upgrade scripts. These modifications enable the upgrade to Communication Manager 3.1 to complete successfully. LSPs with R2.x software also require the preupgrade service pack. 1. On the Welcome page of the Communication Manager Web pages, double-check Launch Upgrade Tool. The Upgrade Tool Welcome page appears. 2. Select Schedule Upgrade from the menu on the left pane. The Schedule Upgrade page appears. 3. Enter the file name of the preupgrade software service pack in the Update File Name field for the Main Server(s). 4. Enter the file name of the preupgrade software service pack in the Update File Name field for LSP. 5. Scroll down to the Main Server Targets field and select the Update box for the primary controller. 6. Scroll down to the LSP Targets field and select the Update box for the LSPs you are upgrading. 7. Click Run Now. The Upgrade Tool updates the primary controller and any LSPs you selected.


To copy files to the media server: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im 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 media server. 4. Click Download to copy the files to the media server. The system copies the files automatically to the default file location.
! CAUTION:
CAUTION:
Do not transfer files across the duplication link to the other media server. You must connect to the media server that you are uploading the files to.

Note:
! CAUTION:
CAUTION:
Issue 2.1 June 2006
269

!
Important:
Removing CD-ROM from the CD-ROM drive

To 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 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.
Issue 2.1 June 2006
271
Upgrade tasks
Starting the Upgrade Tool
!
Important:
Important: The Communication Manager software must be copied directly to each LSP by logging into the LSP and using the Manage Software Web page. In addition, the authentication file, if needed, must be downloaded to each LSP also by logging into the LSP and using the Download Software Web page. Then, you can run the Upgrade Tool from the primary controller to upgrade the LSPs and install new licenses and postupgrade service packs, if necessary.
Use the Upgrade Tool to upgrade LSPs, media gateways and modules, and the S8500 Media Server as primary controller. Note: For more information on using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheets, Issue 3 (555-245-757) and the online Help.
Note:
The following steps start the Upgrade Tool. 1. On the Home page, click Launch Upgrade Tool.
Upgrade tasks
The system displays the Upgrade Tool Home Page.
2. Follow the procedures in the Job Aid: Upgrade Tool and Worksheets. Note: An interchange occurs during the upgrade. Thus, when the upgrade is complete, the active server from which you ran the Upgrade Tool is be the standby server.
Note:
Installing Avaya authentication files on the active server, if required

New authentication files are required when you upgrade the software to a release with a new whole number, such as from R2.2 to R3.0. To install the security file: 1. On the Maintenance Web Interface, under Security, select Authentication File. 2. Select Install the Authentication file I previously downloaded and click Install to install the Avaya authentication file. The system tells you that the authentication file is installed successfully. Note: You must install authentication files on each LSP and ESS individually using this procedure. You can download the authentication files to the LSPs and ESS remotely, then perform the installations remotely if the LSPs and ESSs are available for remote access.
Note:
Issue 2.1 June 2006
273



Note:
Post-Upgrade tasks
Post-Upgrade tasks
Note:
Note: You must use SAT commands on the active media server for the tasks Enabling scheduled maintenance with SAT on page 275 through Busying out previously busied out trunks on page 276.

Releasing MMI using SAT

To release MMI with the SAT, perform the following step: 1. Type release board UUCSS where UU is the cabinet location, C is the carrier, and SS is the slot. 2. Press Enter to release the circuit packs that you busied out in the Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 261 section.
Issue 2.1 June 2006
275


Resolving alarms

Note:
To back up system configuration files: 1. Under Data Backup/Restore, click Backup Now.
Post-Upgrade tasks
2. Select the data sets. For the main server only, select Avaya Call Processing (ACP) translations and Save ACP translations prior to backup. An ESS gets translations from the main server, so there is no reason to backup the translations on an ESS. Do not select Full Backup because this option does not save translations. 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. 4. Click Start Backup to start the back up process.
Note:
Releasing alarm suppression on the media server (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. 1. Access the command line interface of the server with PuTTY with SSH and an IP address of 192.11.13.6. 2. Log in as craft or dadmin. 3. Type almsuppress -n and press Enter to release alarm suppression. 4. Log off.


Issue 2.1 June 2006
277


!
Important:
Releasing alarm suppression on the media server

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. 1. Access the command line interface of the server with PuTTY, with SSH and an IP address of 192.11.13.6. 2. Log in as craft. 3. Type almsuppress -n and press Enter to release alarm suppression. 4. Log off.
Logging off the administration applications on the standby media server

Post-requisites

Follow standard procedures for registering the new software.
Post-requisites
Upgrading the G150 Media Gateways, if being used
Note:
Note: If the configuration does not include G150 Media Gateways, do not perform this task.
You must upgrade the G150 Media Gateways and their WAN Expansion Interfaces first if both of the following conditions are true:

The configuration includes both G150 Media Gateways and WAN Expansion Interfaces. Newer software exists for the G150 Media Gateways.
For more information, see Installing and Configuring the Avaya G150 Media Gateway (03-300395).
Issue 2.1 June 2006
279
Prerequisites
Chapter 3: Upgrading Firmware on TN circuit packs and 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 Avaya 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.
Prerequisites
You 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 68 in Chapter 2: Upgrading Software on Media Servers on page 65.
Upgrade modules
The following modules are contained in this chapter:

Upgrading firmware on the IPSIs and SIPIs on page 283 Upgrading firmware on programmable TN circuit packs on page 293 Upgrading firmware on the Avaya Ethernet Switch on page 295
Issue 2.1 June 2006
281
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 media 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 media server. The process only requires IP connectivity to the IPSIs, which both media 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.
! CAUTION:
CAUTION:
Issue 2.1 June 2006
283
Prerequisites
Before 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 media 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, S8700, S8710, or S8720 Media Server. To find out the firmware that is currently on the IPSIs, see Determining current IPSI firmware on page 285
Access the Maintenance Web Interface

Access the Maintenance Web Interface with the following steps. 1. If on site, connect to the services port on the back of the media server. If off site log in to the media server using the IP address of the media server. 2. Start the Web browser. 3. If connected directly to the media 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 media server. 4. Log in as craft or dadmin. 5. When asked whether to suppress alarms, click yes. 6. Click Launch Maintenance Web Interface to get to the Main Menu.
Upgrade Tasks
Determining current IPSI firmware

The 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: IP address 135.9.77.28 IPSI Name ipsi-A01e IPSI Board TN2312 HW# 32 FW# 7
The last column shows the firmware version. 2. Print the page. 3. Determine which IPSIs need new firmware.
Upgrade Tasks
Preupgrade tasks:

Access the Maintenance Web Interface on page 286 Determining active IPSIs (duplicated control network only) on page 287 Busying out standby IPSIs (duplicated control network only) on page 287
Issue 2.1 June 2006
285
Upgrade tasks:

Downloading firmware to IPSI on page 288 Activating the new firmware on page 290 Releasing standby IPSIs (duplicated control network only) on page 291 Verifying the health of the IPSIs on page 291
Post-upgrade tasks:
Verifying IPSI firmware version on page 292
Pre-Upgrade tasks
Access the Maintenance Web Interface
Access the Maintenance Web Interface with the following steps. Note: If duplicated media servers, you must connect to the active media server. 1. If on site, connect to the services port, default 2 [Eth1], on the back of the media server. If off site log in to the media server using the IP address of the media server. 2. Start the Web browser. 3. If connected directly to the media 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 media server. 4. Log in as craft or dadmin. 5. When asked whether to suppress alarms, click yes. 6. Click Launch Maintenance Web Interface to get to the Main Menu.
Note:


Upgrade Tasks
Determining active IPSIs (duplicated control network only)

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.
Note:
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.
Issue 2.1 June 2006
287
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. 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 media 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.
Upgrade Tasks
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.
Issue 2.1 June 2006
289
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
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 Avaya Communication Manager or from other events such as board removal or power loss. Canceling the resets means some IPSIs have newer firmware than others.
Upgrade Tasks
Releasing standby IPSIs (duplicated control network only)

Note: The following steps are done using SAT commands.
Note:
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: The following steps are done using SAT commands.
Note:
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 287 through Verifying the health of the IPSIs on page 291 for each new standby IPSI.
Issue 2.1 June 2006
291
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 programmable 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 CLAN 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
! CAUTION:
CAUTION:
Issue 2.1 June 2006
293
Upgrading firmware on programmable 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.
! CAUTION:
CAUTION:
Information on how to upgrade the firmware is in the following documents available on the Avaya Support Web site: C-360 series Installation and Configuration for the Avaya C360 Converged Stackable Switches, Software Version 4.5, "Updating the Firmware" Avaya P333T User Guide for Version 4.0, "Upgrading the Software" Avaya P3334T User Guide for Version 4.0, "Upgrading the Software" Avaya P332MF User Guide for Version 4.0, "Upgrading the Software" Avaya P333R User Guide for Version 4.0, "Upgrading the Software" Avaya P333R-LB Version 3.11 User Guide, "Upgrading the Software" Avaya P332G-ML User Guide for version 4.5, "Upgrading the Software" Avaya P332GT-ML User Guide for version 4.5, "Upgrading the Software" Avaya P334T-ML User Guide for version 4.5, "Upgrading the Software"
P333T P3334T P3332MF P333R P333R-LB P332G-ML P332GT-M P334T-ML
You must be connected directly to the Avaya Ethernet switch to upgrade the firmware. You cannot upgrade the firmware through the media server.
Issue 2.1 June 2006
295
Upgrading firmware on the Avaya Ethernet Switch
Migrations
A migration is a change in hardware. The types of migration include a:

non-Linux-based system to a Linux-based media server Linux-based media server to a different Linux-based media server media gateway to a different media gateway
An upgrade usually accompanies a migration
The most common migrations are from non-Linux-based systems to Linux-based media servers. Non-Linux-based systems include systems such as the DEFINITY ONE/S8100. Less common migrations include migrations from one Linux-based media server to another. Not all non-Linux-based systems can migrate to a Linux-based media server. Whether you can migrate a system depends on the supported migration path. A migration path refers to the platform and the software release from which you can migrate to the new platform.
To migrate a system, you need a new license file. You cannot migrate a license file as part of a hardware migration. You must use Remote Feature Activation (RFA) to generate a brand new license. This section describes the migrations from existing DEFINITY systems to the Avaya S8400, S8500, or S8700-Series Media Servers. This section includes:

Migration paths Migration hardware Prerequisites
If you are migrating to an S8400 Media Server, see S8400 Media Server on page 298. If you are migrating to an S8500 Media Server, see S8500 Media Server on page 299. If you are migrating to an S8700-Series Media Server, see S8700.
Issue 2.1 June 2006
297
S8400 Media Server

Use these procedures to migrate from existing DEFINITY systems to the Avaya S8400 Media Server with limited out-of-service time. The existing systems must be standard reliability. In all instances, the cabinets can be reused a port network (PN). You do not need a G650 Media Gateway. You can migrate the following existing systems:

DEFINITY Server CSI in a Compact Modular Cabinet (CMC) DEFINITY ONE in a CMC Avaya IP600/S8100 in a G600
Migrating hardware
The information in this section is based on the assumption that the media server complex is installed, configured, and operational.
DEFINITY Server CSI or DEFINITY ONE/S8100 in a CMC

When migrating an existing DEFINITY Server CSI or DEFINITY ONE in a CMC, you use the TN8400AP S8400 Media Server circuit pack to control the PN. You replace the processor circuit pack with the TN8400AP Media Server and TN8412AP S8400 IP Interface (SIPI) circuit packs in the cabinet in the A position. Install the TN8400AP Media Server circuit pack in slot 1 and the TN8412AP SIPI circuit pack in slot 2. This migration affects service because you must turn off the CSI or DEFINITY ONE chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
S8500 Media Server
Avaya IP600 in a G600

When migrating an existing Avaya IP600, you use the TN8400AP S8400 Media Server circuit pack to control the PN. You replace the processor circuit pack with the TN8400AP Media Server and TN8412AP SIPI circuit packs in the cabinet in the A position. Install the TN8400AP Media Server circuit pack in slot 1 and the TN8412AP SIPI circuit pack in slot 2. This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
S8500 Media Server

Use these procedures to migrate from existing DEFINITY systems to the Avaya S8500 Media Server with limited out-of-service time. The existing systems must be standard reliability and direct connect. You cannot migrate systems that use a center stage switch (CSS) or asynchronous transfer mode (ATM). In all instances, the cabinets can be reused as port networks (PNs). You do not need a G650 Media Gateway. However, you can add a G650 Media Gateway PN if the existing system has only one or two port networks. You can migrate the following existing systems:
DEFINITY Server SI in a single carrier cabinet (SCC) or multicarrier cabinet (MCC). You can migrate only the Direct-Connect configurations DEFINITY Server CSI in a compact modular cabinet (CMC). You can migrate only the IP-PNC configurations DEFINITY ONE in a CMC. You can migrate only the IP-PNC configurations. Avaya IP600/S8100 in a G600. You can migrate only the IP-PNC configurations.
Issue 2.1 June 2006
299
Migration paths for S8500 Media Servers

When you migrate to an S8500, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files by e-mail to the project manager before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418.
These migration paths require that the media server is running Communication Manager Release 1.2.x, 1.3.x, 2.0.x, or 2.1.x software before the migration. Upgrades from a release of Communication Manager that is earlier than Communication Manager Release 1.3.1 require that you install the preupgrade service pack before the upgrade to Communication Manager Release 3.0. An S8500 Media Server that is running Communication Manager Release 1.3.x or 2.x software can support a configuration that has one or more local survivable processors (LSPs) that are running Communication Manager Release 3.0. An S8500 Media Server that is running Communication Manager Release 3.0 software can support a configuration that has one or more LSPs or Enterprise Survivable Servers (ESSs). The LSPs and ESSs must be running Communication Manager Release 3.0. For more information see Upgrades on page 63.
Migrating hardware
Migrating hardware
DEFINITY Server SI in an MCC

When you migrate an existing DEFINITY Server SI in a multicarrier cabinet (MCC), you use one TN2312BP IPSI circuit pack to control from one to three port networks (PNs). Avaya recommends that you install the IPSI in the A carrier in the existing processor port network (PPN) instead of in one of the expansion port networks (EPNs). But before you install the IPSI, you must convert the PPN to a PN. This process requires that you:

Replace the processor control carrier with an expansion control carrier. Remove all the control circuit packs.
This migration affects service because you must be turn off the carrier. Before you turn off the cabinet, you must perform some premigration administration.
DEFINITY Server SI in an SCC

When you migrate an existing DEFINITY Server SI in a single carrier cabinet (SCC), you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the cabinet in the A position in the existing PPN instead of in one of the EPNs. But before installing the IPSI, you must convert the PPN to a PN. This process requires that you:

Replace the processor control cabinet with an expansion control cabinet. Remove all the control circuit packs.
This migration affects service because you must turn off the PPN stack to replace the cabinet. Before turning off the cabinets, you must perform some premigration administration.

When you migrate an existing DEFINITY Server CSI or DEFINITY ONE in a compact modular cabinet (CMC), you use one TN2312BP IPSI circuit pack to control the PN. If a CSI, you replace the TN2182 Tone Clock circuit pack with the IPSI which you install in the A position of the cabinet. You also must remove the processor circuit pack. If a DEFINITY ONE, you replace the processor circuit pack with the IPSI.
Issue 2.1 June 2006
301
This migration affects service because you must turn off the CMCs to replace the processor and the tone clock circuit packs. Before you turn off the cabinets, you must perform some premigration administration.
Avaya IP600/S8100 in a G600

When you migrate an existing Avaya IP600, you use one TN2312BP IPSI circuit pack to control the PN. You also must replace the processor circuit pack with the IPSI which you can install in the A position of the cabinet. This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
S8700 Media Server

Use these procedures to migrate from existing DEFINITY and Linux platforms to the Avaya S8700-Series Media Server configuration with limited time out-of-service. The S8710 or S8720 Media Server can be either a fiber-port network connectivity (PNC) configuration or an IP-PNC configuration or both. Note: Once you complete the migration to fiber-PNC, you can convert to IP-PNC. See Converting PNs to IP-PNC on page 1041.
Note:
You can migrate the following existing systems to an S8700-Series Media Serve. r:

DEFINITY Server R in a multicarrier cabinet (MCC) DEFINITY Server SI in a single carrier cabinet (SCC) or a multicarrier cabinet (MCC) Avaya IP600 (S8100) in a G600 Media Gateway DEFINITY ONE (S8100) in a compact modular cabinet (CMC) DEFINITY Server CSI in a CMC
You can migrate the following existing Linux systems to an S8700-Series Media Server:

S8500 S8700
Migration paths for S8700-Series Media Servers

When you migrate to an S8700-Series Media Server with a fiber-PNC configuration, you can use the existing translations. For a DEFINITY Server R with a magneto optical drive, use the Magneto Optical to S87x0 Translations (MOST) tool to copy the translations to the S8710 Media Server. For a DEFINITY Server R without an optical drive or a DEFINITY Server SI, you must: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation files on a PCMCIA flash card or compact flash card and translation reports before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418. When you migrate from an S8100, the only supported method of moving translations is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files through e-mail to the project manager before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418.
Transferring translations
This section provides information on transferring translations to the S8700-Series Media Servers.
From a magneto optical disk

Use the Magneto Optical to S87x0 Translations (MOST) tool to transfer translation files from a magneto optical disk to an Avaya S8700-Series Media Server. Use the MOST tool only when you migrate call processing translations on a DEFINITY Server R to an Avaya S8700-Series Media Server in a fiber-connect configuration.l The MOST tool is not shipped with each system but might be available locally. The MOST tool that you use with the S8700 Media Server consists of:

an external magneto optical drive a SCSI PC card an external SCSI cable
Issue 2.1 June 2006
303
The MOST tool that you use with the S8710 Media Server consists of:

an external magneto optical drive a USB cable
Ordering information
Comcode 700226269 700355415 Description Magneto Optical Server to S8700 Translations (not orderable) Magneto Optical Server to S8710 Translations with USB cable
! CAUTION:
CAUTION:
When you create the optical disk to move translations from the source system to the S8700-Series Media Server, you must follow specific steps. For more information, see Presite migration checklist on page 311.
Migrating hardware

When you migrate an existing DEFINITY Server SI in a multicarrier cabinet (MCC), you use one TN2312BP IPSI circuit pack to control from one to three port networks (PNs). Avaya recommends that you install the IPSI in the A carrier in the existing processor port network (PPN) instead of in one of the expansion port networks (EPNs). But before installing the IPSI, you must convert the PPN to a PN. This process requires that you:

This migration affects service because you must turn off the PPN to replace the carrier. Before you turn off the cabinet, you must perform some premigration administration.
Migrating hardware

When you migrate an existing DEFINITY Server SI in an single carrier cabinet (SCC), you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the cabinet in the A position in the existing PPN instead of in one of the EPNs. But before installing the IPSI, you must convert the PPN to a PN. This process requires that you:

This migration affects service becuase you must turn off the PPN stack to replace the cabinet. Before you turn off the cabinets, you must perform some premigration administration.

You can only migrate a DEFINITY Server CSI or a DEFINITY ONE/S8100 in a compact modular cabinet (CMC) to an Avaya S8710 or an S8720 with an IP-PNC configuration. When you migrate an existing DEFINITY Server CSI or a DEFINITY ONE in a CMC, you use one TN2312BP IPSI circuit pack to control the PN. If a CSI, you replace the TN2182 Tone Clock circuit pack with the IPSI which you install in the A position of the cabinet. You also must remove the processor circuit pack. If a DEFINITY ONE, you replace the processor circuit pack with the IPSI. This migration affects service because, if a CSI, you must turn off the CMCs to replace the processor and tone clock circuit packs. Before you turn off the cabinets, you must perform some premigration administration.

You can only migrate an Avaya IP600 to an Avaya S8710 or an S8720 with an IP-PNC configuration. When you migrate an existing Avaya IP600, you use one TN2312BP IPSI circuit pack to control the PN. You replace the processor circuit pack with the IPSI in the cabinet in the A position. This migration affects service becuase you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
Issue 2.1 June 2006
305
Common prerequisites to all migrations

The following list of migration prerequisites are common to all migration modules. Prerequisites that are unique to a specific module are contained in the module. Before you go on site, perform the following tasks:
:
Task Verify that the correct hardware is installed on your Services laptop.
Description Correct hardware includes: 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 Correct software includes: Windows 2000 or Windows XP operating system Terminal emulation program: HyperTerminal or another TCP/IP networking software bundled with the Windows OS Internet Explorer 5.0 or later For example, obtain logins and passwords for the following components: Media Server Media Gateway SIPI or IPSI circuit pack auxillary equipment Communication Manager These logins and passwords include the logins and the passwords that you might need for the equipment of the customer. You need a new license file and authentication file. You need the serial number from the reference SIPI or IPSI and the SAP order number to generate a new license file. 1 of 3
Verify that the correct software is installed your Services laptop.
Obtain the serial number for the Media Servers, if necessary.
Task Verify that you have the Communication Manager software distribution CD-ROM with the current software and firmware. Verify that you have the current preupgrade or premigration service packs, if required, on your laptop. Verify that you have the current post-upgrade or post-migration service packs, if required, on your laptop. Verify that you have the current firmware available.
Description Use this CD-ROM to install the software on the media server and upgrade the firmware. The most recent versions of the service packs are also on this CD-ROM. Check which service packs you need and download files from the Avaya Support Web site (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site (http:// avaya.com/support).
The following firmware is on the software CD-ROM:

IPSIs CLAN MedPro VAL circuit packs
Important: Firmware is upgraded often. To ensure that you have the latest version, go to the Avaya Support Web site (http://avaya.com/support). Click Downloads and select the product. Download license and authentication files to your Services laptop. Avaya technical support representatives only: Obtain the static craft password. New license and authentication files are necessary. Obtain information and download files from the Remote Feature Activation (RFA) web site at http:// rfa.avaya.com. Call the ASG Conversant number 800-248-1234 or 1-720-444-5557 and follow the prompts to get the password. You need the Product ID, the FL, or IL number of the customer. 2 of 3
Issue 2.1 June 2006
307
Task Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary.
Description This step is necessary if the configuration of the customer INADS alarming modem has changed or if any changes were made to the system alarming configuration. ART is available only to Avaya associates. BusinessPartners can call 800-295-0099. These files can include: Service packs License file Authentication file Firmware for programmable circuit packs 3 of 3
Verify that you copied the necessary files to your computer.
Premigration setup
When you migrate from a DEFINITY system, complete the following additional tasks before you start the migration: Task About 2 weeks before the migration, freeze the translations. Collect the translations locally by a spare flash card. If the existing system does not have a magneto optical drive or if the MOST tool is not used, send the translation media to the STS. For more information, see From a magneto optical disk on page 303. About 2 business days before, contact the STARS team by creating a trouble ticket. Description For more information on where and how send the translations, contact the STS scheduling desk at 720-444-9418. STS then updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. Verify that a copy of the existing translations exists so that you can reenter the translations later.
Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new Communication Manager license and Avaya authentication file is requested, ASG access (remote and on-site) is impacted. The Service Tools and Application Remote Support (STARS) team provides assistance to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// stars.avaya.com/ticket/requests/request.asp.
Mark the ticket status as CRITICAL.
Indicate text in the ticket to notify the STARS team that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. 1 of 2
Issue 2.1 June 2006
309
Task Ensure that the technical support representative has access to the ASG Site Manager tool.
Description If an engineer who works on the Avaya WAN is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote and on-site) is affected when you upgrade an S8x00 media server from 1.x.x to 2.x.x and request a new Communication Manager license and Avaya authentication file.
The STARS team provides the escalation path to report ASG troubles during the upgrade. Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
This event happens at least 1 days before the migration.
When you finish installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the customer media server. You can use the password the next time that you log in as craft, if you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access still requires an ASG challenge/response. This unique craft password remains valid until the password is changed by installing a new authentication file.
Save the translation file to a directory on the Services laptop.
File size usually is in the range of 1-4 megabytes.
2 of 2
Presite migration checklist

Before you go on site, complete the following tasks: Task Verify that the voice network, dial plan, and E911 for remote locations were redesigned. Verify that all existing circuit packs work with the new system. Replace any TN799B/C C-LAN circuit packs. Replace the 259A adapter and the CAT3 cable. Replace TN570 EI circuit packs. Description Perform this task only if applicable.
Check the Minimum Vintage Table. Go to the Hardware and Software Compatibility Matrix at ftp// ftp.avaya.com/incoming/Up1cku9/tsoweb/media/ minhardwarevintages.pdf. Replace with the TN799DP circuit pack. Replace with the cable extender adapter with Comcode 848525887 and the CAT5 or better cable. Replace with TN570B vintage 7 or later circuit packs.
Issue 2.1 June 2006
311
On site migration checklist

When you are on site, complete the following tasks before you start the migration: Task Verify that the EIA 310D 19-inch (48-cm) open equipment rack is grounded. For S8710 only: Verify that the open, customer-supplied, EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack is properly installed and solidly secured. Verify that you have the correct cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. Verify that you have all necessary equipment onsite. Description See the job aid titled Approved Grounds (555-245-772). Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on installing the rail, see the rail kit documentation.
The cables must be labeled and run from the control hardware rack to the port networks. Appropriate connectivity must be provided.
For the list of required hardware, see:
Installing and Configuring the Avaya S8500 Media Server (03-300143) Installing and Configuring the Avaya S8700-Series Media Server (03-300145)

Note:



Issue 2.1 June 2006
313
Caution about platform/PNC license settings for the S8700-series Media Server
The license settings for port network connectivity (PNC) IP-PNC or fiber- PNC (previously referred to as "multiconnect" [MC]) can be complex and can cause problems if not set correctly. When creating a license for an S8700-series Media Server, use the following summary (Table 11) and guidelines:
Table 11: Summary for license settings for the S8700-series platform and PNC License file attribute Platform Type Internet Protocol (IP) PNC (FEAT_IP_PNC) feature Platform Number in Customer Options screen Result in Communication Manager Internet Protocol (IP) PNC feature in Customer Options screen no Allowed configuration
8700 Media Server MC1
OFF2
61
IP-PNC and fiber-connect PNs simultaneously SCC1 or MCC1 are allowed in configuration using IP-PNC.
8700 Media Server IP3
OFF2
83
no
Same as above.
1. Use for all new installations and migrations. Required for upgrades of an S8700-series Media Server that was a fiber-PNC or MC (platform 6) configuration before the upgrade. 2. This attribute, before release 3.0, restricted the ability to configure a network with both IP-PNC and fiber-PNC port networks and to configure SCC1 and MCC1 PNs using IP-PNC only. For all upgrades, migrations, and installations to release 3.0 and later, these restrictions have been lifted for both platforms. Thus, this field is no longer applicable and should be set as OFF. 3. Required, and used only, for upgrades of an S8700-series Media Server that was an IPC (platform 8) configuration before the upgrade.
Guidelines
For a new installation or migration, the licensed platform type should always be 8700 Media Server MC (platform 6). For an upgrade, the licensed platform type of the server must remain the same. If the platform type is 8700 Media Server IP (platform 8) before the upgrade, the platform type must be 8700 Media Server IP (platform 8) after the upgrade. If the platform type is 8700
Migration chapters
Media Server MC (platform 6) before the upgrade, the type must be 8700 Media Server MC (platform 6) after the upgrade.
Effective with CM 3.0, Internet Protocol (IP) PNC (FEAT_IP_PNC in the RFA license file) is always to set to OFF. After you install, migrate to, or upgrade the server, then this attribute should appear as n (no) in the display-only Internet Protocol (IP) PNC field on page 4 of the Communication Manager Customer Options screen. Note: The Internet Protocol (IP) PNC (FEAT_IP_PNC license attribute, before release 3.0, restricted port network connectivity (PNC) for each of the platforms. The OFF setting previously restricted MC (platform 6) platforms from using IP-PNC. The ON setting previously restricted IP (platform 8) platforms from using MC-PNC configurations. With release 3.0, both of these restrictions were lifted.
Note:
Migration chapters

Migrating to an Avaya S8400 Media Server on page 317 Migrating to an Avaya S8500 Media Server on page 443 Migrating to an Avaya S8700-Series Media Server on page 611
Issue 2.1 June 2006
315
Chapter 4: Migrating to an Avaya S8400 Media Server

This chapter describes how to migrate from existing DEFINITY systems to the Avaya S8400 Media Server. The most common migrations are from non-Linux-based systems to Linux-based media servers. Non-Linux-based systems include systems such as the DEFINITY ONE/S8100. Less common migrations include migrations from one Linux-based media server to another. Not all non-Linux-based systems can migrate to a Linux-based media server. Whether you can migrate a system depends on the supported migration path. A migration path refers to the platform and the software release from which you can migrate to the new platform.

An S8400 Media Server that is running Communication Manager Release 3.1 software can support a configuration that has one or more LSPs. The LSPs must be running Communication Manager Release 3.1. For more information, see Upgrades on page 63.
Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash

When you migrate from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server with a flash card reader: 1. Copy the translations to the linear flash card in the PCMCIA slot on the TN798B Processor circuit pack. 2. Plug the PCMCIA flash card with the translations into the flash card reader attached to the Services laptop. 3. Copy the translations to the S8400 Media Server.
Issue 2.1 June 2006
317
Migrating to an Avaya S8400 Media Server
Migrating from a DEFINITY Server CSI in a CMC using Xmodem

When you migrate from a DEFINITY Server CSI in a CMC to an S8400 Media Server using Xmodem: 1. Copy the translations to the Compact Flash card in the PCMCIA slot on the TN798B Processor circuit pack. 2. Copy the translations onto the Services laptop. 3. Copy the translations to the S8400 Media Server.
Migrating from an S8100 using ftp

When you migrate from an S8100 to an S8400 Media Server using ftp: 1. On the SAT, copy the translation files. 2. Move the translations onto the Services laptop. 3. Copy the translations to the S8400 Media Server.
Migrating all other systems

When you migrate to an S8400, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Copy the translations to the Compact Flash. 2. Copy the translation files from the Compact Flash to the S8400 Media Server.
Migrating from existing DEFINITY and Linux platforms

Use these procedures to migrate from existing DEFINITY systems to the Avaya S8400 Media Server with limited out-of-service time. The existing systems must be standard reliability. In all instances, the cabinets can be reused as a port network (PN). You do not need a G650 Media Gateway. You can migrate the following existing systems:

DEFINITY Server CSI in a Compact Modular Cabinet (CMC) DEFINITY ONE in a CMC Avaya IP600/S8100 in a G600
Migrating hardware
Migrating hardware

When migrating an existing DEFINITY Server CSI or DEFINITY ONE in a CMC, you use the TN8400AP S8400 Media Server circuit pack to control the PN. You replace the processor circuit pack with the TN8400AP Media Server and TN8412AP S8400 IP Interface (SIPI) circuit packs in the cabinet in the A position. Install the TN8400AP Media Server circuit pack in slot 1 and the TN8412AP SIPI circuit pack in slot 2. This migration affects service because you must turn off the CSI or DEFINITY ONE chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
Avaya IP600 in a G600

When migrating an existing Avaya IP600, you use the TN8400AP S8400 Media Server circuit pack to control the PN. You replace the processor circuit pack with the TN8400AP Media Server and TN8412AP SIPI circuit packs in the cabinet in the A position. Install the TN8400AP Media Server circuit pack in slot 1 and the TN8412AP SIPI circuit pack in slot 2. This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
Prerequisites for migrating to an S8400 Media Server

This section describes the following tasks that you must complete before you start the migration.

Tasks that you must perform before you go on site Tasks that you must perform on site before you start the migration from an existing DEFINITY system Tasks that you must perform on site before you start the migration Documents that Avaya recommends that you have before you start the migration
Issue 2.1 June 2006
319
Migration modules
This chapter describes the following types of migrations:
Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server that uses a Card Reader on page 321 Migrating from a DEFINITY Server CSI in a CMC with an ATA Flash to an S8400 Media Server on page 355 Migrating from a DEFINITY Server CSI in a CMC to an S8400 Media Server using Xmodem on page 383 Migrating from an IP600 or S8100 to an S8400 Media Server using ftp on page 413
Basic migration steps
Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server that uses a Card Reader
Use these procedures to migrate from an existing DEFINITY Server CSI in a Compact Modular Cabinet (CMC) system or G600 Media Gateway with a linear flash to an Avaya S8400 Media Server that uses a card reader. To migrate an existing DEFINITY Server CSI in a CMC, you use one TN8412AP S8400 IP Interface (SIPI) circuit pack to control the one port network. You must replace the TN2182 Tone Clock circuit pack with a SIPI circuit pack that you install in the A position in the cabinet. You also must remove the processor circuit pack. This migration affects service.

Remove the netcon data modules Replace the tone clock circuit pack with the TN8412AP S8400 IP Interface (SIPI) circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Replace the processor circuit pack with the TN8400AP Media Server circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Enable control of the SIPI and switch control to the media server Complete the postmigration administration
Migration paths
Avaya supports the following migrations of a DEFINITY Server CSI in a CMC or a G600 Media Gateway to the S8400 Media Server configuration:
DEFINITY Release 6 through Release 8
Issue 2.1 June 2006
321
Migrating from a DEFINITY Server CSI in a CMC with a Linear Flash to an S8400 Media Server that uses a
To migrate, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Copy the translations to the linear flash card in the PCMCIA slot on the TN798B Processor circuit pack. 2. Plug the PCMCIA flash card with the translations into the flash card reader attached to the Services laptop. 3. Copy the translations to the S8400 Media Server.
Installing the linear card reader software

You need to install the software for the linear card reader so that you can copy the translations to the Services laptop. This installation is a one-time installation. To install the linear card reader: 1. Insert the CD-ROM into the Services laptop. The system displays the Omni Drive home page window.
Migration paths
2. Under Professional Line, click USB Professional. The system displays the OmniDrive USB Professional window.
3. In the PC Card Manager area, click PCM Setup. Do not select Setup at the bottom.
4. Select the setup language, for example, English and click OK.
Issue 2.1 June 2006
323
5. Accept the license and follow the prompts.
6. When you finish, click Finish. Access to PC Card Manager is by either: a. The shortcut created on your desktop b. Through Start > Programs > PCM.
7. Click Exit and remove the CD-ROM.
Migration paths
Prerequisites
You must complete the following tasks before you start the migration:

Presite Checklist on page 325 - Perform these tasks before you go on site. Additional tasks on page 327 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 329 - Perform these tasks before you go on site. On site migration checklist on page 329 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 331 - Have these documents ready to use while you perform the migration.
Tasks checklists
Presite Checklist
Before you go on site, perform the following tasks
:
Task Verify that your Services laptop has the appropriate hardware.
Description Correct hardware components include: 40 MB available disk space direct Ethernet cable serial cable and adapter RS-232 port connector Network interface card (NIC) with a 10/100 BaseT Ethernet interface 10/100 BaseT Ethernet, category 5, or better, crossconnect cable with an RJ45 connector on each end, MDI to MDI-X CD-ROM drive Correct software components include: Windows 2000/XP operating system Terminal emulation program: HyperTerminal or other TCP/IP networking software: bundled with Windows OS Web browser: Internet Explorer 5.0 or later 1 of 3
Issue 2.1 June 2006
325
Task Obtain appropriate logins and passwords for all equipment and software.
Description For example, obtain logins and passwords for the following components: Media Server Media Gateway SIPI or IPSi circuit pack auxillary equipment Communication Manager These logins and passwords include the equipment of the customer. You need a new license file and authentication file. You need the serial number from the reference SIPI or IPSI and the SAP order number to generate a new license file. You use this CD to install the software on the media server and upgrade the firmware.
Obtain the serial number of the Media Servers, if necessary.
Verify that you have the Communication Manager software distribution CD with the current software and firmware. Verify that you have the current preupgrade or premigration service packs, if required, on your laptop. Verify that you have the current post-upgrade or post-migration service packs, if required, on your laptop. Verify that you have the current firmware available.
Check which service packs you need and download files from the Avaya Support Web site at (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site at (http:// avaya.com/support).
The following firmware are on the software CD:

IPSIs or SIPIs C-LAN MedPro VAL circuit packs
For the most current versions, go to the Avaya Support web site at (http://avaya.com/support). Click Downloads and select the product. Download license and authentication files to your Services laptop. New license and authentication files are necessary. Obtain information and download files from the Remote Feature Activation (RFA) web site at http:// rfa.avaya.com. 2 of 3
Migration paths
Task Avaya technical support representatives only: Obtain the static craft password. Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary.
Description Call the ASG Conversant number, 800-248-1234 or 1-720-444-5557 and follow the prompts to get the password. You need the Product ID, the FL, or IL number of the customer. This step is necessary if the configuration of the customer INADS alarming modem has changed as well as any changes to the system alarming configuration. ART is available only to Avaya associates. Business Partners can call 800-295-0099. These files can include: service packs license file authentication file firmware for programmable circuit packs 3 of 3
Verify that you have copied all necessary files to your computer
Additional tasks
Before you go on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task Verify that you have the required, customer-provided network information. Obtain a completed Electronic Preinstallation Worksheet (EPW) Description The EPW is an Excel spreadsheet that provides the information about the network. You need this information to configure the control network components with the Avaya Installation Wizard. Get the EPW from the Avaya project manager, Avaya software technician, or customer network administrator. A blank EPW is available at the Avaya Installation Wizard web site (http://support.avaya.com/ avayaiw/).
Premigration setup
The premigration team must complete the following tasks. If these tasks are not completed, do not continue with the migration. For more information, see Migration paths on page 321.
Issue 2.1 June 2006
327
To migrate from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task Ensure that the technical support representative has access to the ASG Site Manager tool. Description If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. Remote or on-site ASG access is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. The STARS team provides the escalation path to report ASG troubles during the upgrade. Verify that you have the appropriate logins and passwords to access the media servers and server complex components. This event happens at least one day prior to the migration.
When you finish installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, if you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access requires an ASG challenge and response. This unique craft password remains valid until the password is changed by installing a new authentication file.
Migration paths


When you are on site, complete the following tasks before you start the migration: Task Verify that you have the correct cables for the TN8412AP S8400 Internet Protocol Interface (SIPI) circuit packs. Verify that you have all necessary equipment onsite. Description The cables must be labeled and run from the control hardware rack to the port networks. Appropriate connectivity must be provided.
For the list of required hardware, see Installing and Configuring the Avaya S8400 Media Server (03-300678).
Issue 2.1 June 2006
329
When you are migrating from a DEFINITY system, complete the following additional tasks before you start the migration: Task Ensure that the technical support representative has access to the ASG Site Manager tool. Description If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. The STARS team provides the escalation path to report ASG troubles during the upgrade. Verify that you have the appropriate logins and passwords to access the media servers and server complex components. This event happens at least one day prior to the migration.
Migration tasks
Documentation checklist for migrations

For a list of documents that are needed to perform the migration, see Resources on page 54. Document Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706) Installing and Configuring the Avaya S8400 Media Server (03-300678) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide that provides physical installation and connection information.
Provides installation instructions for the S8400 Media Server. Provides information on network connectivity.
Migration tasks
! CAUTION:
CAUTION:
This migration affects service. When the PPN is turned off, the system drops all calls. Service returns when the media server takes control of the IPSIs.
The general migration procedures are as follows:

Turn off the processor gracefully - pre-conversion administration Replace the processor circuit pack or tone clock circuit pack with a TN8412AP S8400 IP Interface (SIPI) circuit pack Connect the SIPI circuit pack to the Ethernet switch on the customer network Assign an IP address to the SIPI circuit pack
Issue 2.1 June 2006
331
You can reuse the translations from the existing system when you migrate to an S8400 Media Server. Note: You must install the new Communication Manager license file on the media server before you make the change. The SIPI serial number can be used for licensing purposes.
Note:
Perform the following tasks to convert a processor port network to a port network (CMC). Premigration administration:

Accessing Remote Feature Activation on page 333 Connecting to the processor on page 335 Removing netcon data modules on page 336 Verifying system status on page 337 Recording all busyouts on page 337 Recording node names and IP addresses on page 337 Saving translations on page 338
Migration tasks:

Verifying hardware on page 338 Turning off power to all cabinets on page 339 Removing circuit packs on page 339 Inserting circuit packs on page 339 Connecting cables on page 340 Replacing the TN799C C-LAN circuit pack on page 340 Installing TN771 Maintenance/Test on page 341 Installing the software load on page 341 Configuring the media server on page 342 Installing the license and authentication file on page 343 Copying translation files to the media server on page 344
Postmigration administration:

Using static addressing on page 346 Clearing the ARP cache on the laptop computer on page 346 Logging in to the SIPI on page 347 Setting the control interface on page 348
Premigration administration
Resetting the SIPI on page 349 Enabling control of the SIPI on page 350 Verifying SIPI translations on page 350 Verifying SIPI connectivity on page 351 Verifying the customer data on page 351 Verifying circuit pack locations on page 351 Verifying circuit pack insertion on page 352 Verifying the IP addresses on page 352 Checking the link status on page 352 Upgrading firmware on page 353 Testing the installation on page 353 Busying out previously busied out trunks on page 353 Troubleshooting the migration on page 354 Returning replaced equipment on page 354
This migration is a service-affecting event. The CMCs must be turned off to replace the processor and tone clock circuit packs. Before you turn off the cabinets, you must perform the following premigration administration.
Accessing Remote Feature Activation

Use this section for information on how to access Remote Feature Activation (RFA). You can access the RFA information page for these items (if not already installed on your PC): Note: For Release 10 and later, do not use the FET because the license contains the existing switch configuration information. For Releases G3v4 and earlier, do not use the FET because the ASD tool and process captures the existing switch configuration information.
Note:
Issue 2.1 June 2006
333
Feature Extraction Tool (FET) application. Use FET only for G3v4 through Release 9csi releases that upgrade to Avaya Communication Manager. Integrated FET also is available within the RFA application. License Installation Tool (LIT) application. Use LIT to install a Communication Manager license on any Release 10 or later DEFINITY Server CSI.
Computer requirements
Before you attempt to access RFA, verify that your computer has:

Internet Explorer 5.0 or later 128-bit encryption Internal access to the RFA web site at http://rfa.avaya.com A supported monitor resolution of 800 x 600
User requirements
An RFA user must meet the following requirements:
Be either an: - An Avaya associate or contractor with a valid Avaya Human Resources Identification (HR ID) number. - An approved BusinessPartner with a valid BusinessPartner number. - An Avaya contractor who works with Avaya.
Be a registered and authenticated RFA user. - To be registered in RFA means you have a Single Sign-On (SSO) login and you have registered for each product family in which you want to create a license file. If you do not already have an SSO login, see Avaya Remote Feature Activation (RFA) User Guide, 03-300149. If you are an Avaya employee, you do not have to register. You can use your Windows NT login name and password to log on. - To be authenticated in RFA means you have successfully registered, and your Avaya coach or Group Authorization Identification (GAI) manager approved your access to RFA.
For more information, see Avaya Remote Feature Activation (RFA) User Guide, 03-300149.
Going to the Remote Feature Activation web site

The RFA web site automates some of the upgrade procedures, including generating a license file. 1. At the Services laptop/PC browser, type http://rfa.avaya.com 2. Using your SSO, log in to the RFA web site. 3. Follow the links to the RFA information page. 4. Complete the information necessary to create a license file. If you have a direct connection to the switch: 1. Using your RFA Job Aids, run the Features Extraction Tool (FET) from the RFA web site to create a Switch Configuration file. 2. When prompted, type in the transaction ID number. 3. The FET creates and uploads automatically the Switch Configuration file. 4. Do not deliver the license file at this time. You deliver and install the license later in this upgrade procedure. If you do not have a direct connection to the switch: 1. Run the Features Extraction Tool (FET) from the Services laptop/PC to create a Switch Configuration file. 2. When prompted, type in the transaction ID number. 3. Use the FET instructions to create a new switch connection profile. 4. Create the Switch Configuration file. 5. Upload the Switch Configuration File to the RFA web site. Deliver the license file to the Services laptop/PC for installation late in this procedure.
Connecting to the processor

To connect to the processor: 1. Connect the computer that you use to access the cabinet. 2. Start a SAT session using Native Configuration Manager or Avaya Site Administration. 3. Log in as craft.
Issue 2.1 June 2006
335
Removing netcon data modules

To remove Netcon data module information: 1. Type list data module. Press Enter. The system displays the Data Module window. 2. Notice if the system contains any Netcon circuit packs. If there are Netcon data modules, continue to step 3. If there are no Netcon data modules, continue to Verifying system status on page 394. 3. Type list user ext x. Press Enter where x shows who is using the associated Netcon data module.
list usage extension 2501 LIST USAGE REPORT Used By Hunt Group
Group Number
99
Member 1
Command successfully completed
For example, the screen in step 3 shows the extension 2501 is being used on Hunt Group 99. 4. Type change hunt-group xx. Press Enter where xx is the hunt group number. The system displays the Hunt Group window. 5. In the Hunt Group screen, press the space bar to highlight the information. Press Return to remove the information. 6. Repeat for each extension. 7. When you finish, press Submit. 8. Repeat for each listing. 9. Type remove data-module xxxx. Press Submit where xxxx is the extension to be removed. 10. Repeat for all items listed on the list data module command.
Verifying system status

Check which groups are in- or out-of-service before the migration. After the migration, compare the after the migration list with the before the migration list to ensure that the lists are the same. To verify system status: 1. To determine whether the system has administration, run the following commands: a. list configuration all b. list trunk-group c. list hunt-group If any command does not complete successfully, escalate the problem immediately. After the migration, check the same administration to ensure that the translations are intact.

Recording node names and IP addresses

To record node names and IP addresses: 1. Note the node names and the IP addresses that are assigned to the TN2302AP IP Media Processor and the TN799C/DP C-LAN circuit packs. Ensure that these names and addresses are the same after the migration. Note: If the existing system has TN799C C-LAN circuit packs, you must replace these circuit packs with TN799DP circuit packs. 2. To get the node names for the TN2302AP IP Media Processor and TN799C/DP C-LAN circuit packs, type display ip-interfaces. Press Enter. 3. To get the IP addresses that match the node names, type list node-names. Press Enter. 4. Record the information for use after the migration.
Note:
Issue 2.1 June 2006
337
Saving translations
This step is important in case you need to back out of the migration. To save translations from the CSI: Note: Save translations to a flash card. 1. Plug the Linear Flash card in the PCMCIA slot on the TN798B Processor circuit pack. 2. Type save translation and press Enter to save translations to the PCMCIA. 3. The system displays a Command successfully completed message or an error message.
Note:
Migration tasks
You can reuse the translations from the current system when you migrate to an S8400 Media Server. Note: You must install the new Communication Manager license file on the media server before you make the change. The SIPI serial number can be used for licensing purposes.
Note:
Perform these tasks to convert a processor port network to a port network (CMC).
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: The TN8400AP Media Server circuit pack that contains the IA770 feature replaces the TN798 or TN2402 Processor circuit pack that does not have that feature. You must return the current processor circuit pack to Avaya.
Note:
Migration tasks
Turning off power to all cabinets

! CAUTION:
CAUTION:
Ensure that you have done the premigration administration. For more information, see Premigration administration.
To turn off power to all cabinets:
Turn off the power to each cabinet.
Removing circuit packs

To remove circuit packs from the CMC: 1. Remove the TN798B or TN2402 Processor circuit pack from slot A01. 2. Remove the TN2182 Tone Clock circuit pack from slot A02. 3. Remove the TN767 DS1 Interface circuit pack, if installed. 4. Remove the TN2207 DS1 Interface circuit pack, if installed. 5. Remove the TN2313 DS1 Interface circuit pack, if installed.
Inserting circuit packs

To install circuit packs into the CMC: 1. Install the TN8412AP S8400 IP Interface (SIPI) circuit pack into slot A02. 2. Install the TN8400AP Media Server circuit pack into slot A01. 3. If the system had a TN767, TN2207, or TN2313 DS1 Interface circuit pack, install the TN464HP DSD1 Interface circuit pack in any open slot.
Issue 2.1 June 2006
339
Connecting cables
To connect cables: 1. On the rear of the carrier, connect the media server cable adapter into port 1 on the rear of the TN8400AP Media Server circuit pack. 2. Connect the amphenol connector into slot A02 on the rear of the TN8412AP SIPI circuit pack. 3. Connect the customer LAN cable into the port labeled ETH-B on the adapter in slot A01. 4. Connect the IPSI cable into the port labeled ETH-A on the adapter in slot A01. 5. Connect the other end of the IPSI cable to the amphenol connector in slot A02. 6. Connect the power plug on the DVD drive to a wall outlet. 7. Connect the USB DVD drive to the USB port on the faceplate of the TN8400AP Media Server circuit pack. 8. On the DVD drive, ensure that the on/off/ext switch is in the EXT position. 9. Insert the Communication Manager CD into the USB DVD drive. 10. Connect the Services laptop to the Services port on the front of the TN8400AP Media Server circuit pack. 11. Turn on the power to all cabinets.
Replacing the TN799C C-LAN circuit pack

If you need to replace the TN799C C-LAN circuit pack: 1. Remove the TN799C Control-LAN (C-LAN) circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. You might need to reinstall this circuit pack if you must stop the migration. 3. Insert the new TN799DP C-LAN circuit pack into the same slot. 4. Replace the 259A adapter and CAT3 cable on the connector panel. 5. Use the Amphenol adapter that you used for the TN799 circuit pack and a CAT5 cable.
Migrating translations
Installing TN771 Maintenance/Test

You can install a TN771 Maintenance/Test circuit pack in any slot other than slots A01 and A02. Avaya recommends one TN771 Maintenance/Test circuit pack per location for the following conditions:
There are three or more G650, G600, or CMC1 cabinets in the S8400 system. Do not include G150 and H.248 gateways in this count, and There are IP endpoints or ISDN endpoints. These endpoints consist of: - BRI trunks - PRI trunks - BRI stations
The TN8412AP S8400 IP Interface (SIPI) circuit pack provides all maintenance functions that were present on the TN798 or TN2402 Processor circuit pack. This carrier does not have a TN775 Maintenance (EPN) dedicated slot.
This section describes how to migrate the translation files from the current system to the S8400 Media Server.
Installing the software load

To install the software load: 1. From the Services laptop, click Start > Run to open the Run window. 2. Type ping -t 192.11.13.6. Press Enter to indicate when the Services port is responding. 3. Click Start > Run to open the Run window. 4. Type telnet 192.11.13.6. Press Enter to telnet in to the Services port on the front of the S8400 Media Server.
Issue 2.1 June 2006
341
5. When the prompt displays with menu options, select Install or Upgrade Software. Use the arrow keys to navigate and the space bar to select. When the system finishes, the media server reboots. 6. Open a Web browser. 7. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 8. Log in as craft or dadmin.
Configuring the media server

To configure the media server: 1. Open a Web browser. 2. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 3. Log in as craft or dadmin. 4. Under Maintenance, click Launch Maintenance Web Interface. 5. Under Server, click Server Date/Time. 6. In the Server Date/Time window, verify the data and time are correct. If the date and time are incorrect:: a. Enter the date b. Enter the time c. Select the time zone d. Click Submit: 7. Under Server Configuration, click Configure Server. The system starts the Configure Server Wizard. 8. In the Review Notices window, click Continue. 9. In the Back Up Data window, click Continue. 10. In the Specify how you want to use this wizard page, select Configure all servers using the wizard and click Continue. Note: You can set up media servers to various configurations. The following steps provide a general outline of required steps to complete the configuration.
Note:
11. In the Set Server Identifies window, perform the following steps:

In the Host Name field, enter a unique name for the server. In the ID field, enter as required or accept the default. In the CNA field, enter as required or accept the default. In the Enterprise LAN field, enter as required or accept the default. In the Assign the Processor Ethernet to an Interface area, select one as required.
12. Click Continue. 13. In the Configure Ethernet Interfaces window, set up as required. Click Continue. 14. In the Ethernet Adjuncts window, set up as required. Click Continue. 15. In the External DNS Server Configuration window, set up as required. Click Continue. 16. In the Static Network Routes (Optional) window, set up as required. Click Continue. 17. In the Configure Time Server window, set up as required. Click Continue. 18. In the Set Modem Interface window, set up as required. Click Continue. 19. In the Configure Maintenance Processor Complex (MPC) window, set up as required and click Continue to configure the server.
Installing the license and authentication file

To install the Communication Manager license file and the Avaya authentication file: 1. Open a Web browser. 2. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 3. Log in as craft or dadmin. 4. Click Miscellaneous > Download Files. 5. Click Browse and select the file saved on the Services laptop. 6. Click Download to place the file on the media server.
Issue 2.1 June 2006
343
Copying translation files to the media server

To copy translation files to the media server: 1. Plug the PCMCIA flash card with the translations into the Flash Card Reader attached to the Services laptop. 2. On the desktop, double-click the PC Card Manager icon > Actions > Copy > Card to File(s). When the system finishes, the system opens the Copy: Card to File window. 3. Highlight any old job and click Delete to remove them. 4. In the Copy Jobs area, click New. When the system finishes, system opens the Define Copy Job window. 5. In the Size field, type the flash card size, for example, 128 MByte. 6. Enter a file name to copy the translation file to and click OK. An example of a file name might be Csixln. When the system finishes, the system returns to the Copy: Card to File window. 7. Highlight the desired file. Click Copy. When the system finishes, the file is placed in the C:\Program Files\PCM directory. Click Cancel to exit. 8. Open a Web browser. 9. Click Launch Maintenance Web Interface. 10. Under Miscellaneous, click Download Files. 11. Select Files to download from the machine Im using to connect to the server. 12. Click Browse and select the translation file saved on the Services laptop and click Download. A translation file example might be C:\Program Files\PCM\Csixln. The file is placed in the /var/home/ftp/pub directory of the S8400 Media Server. 13. Click Start > Run to open the Run window. 14. Type telnet 192.11.13.6. Click OK to telnet in to the Services port on the front of the TN8400AP Media Server circuit pack. 15. Log in as craft or dadmin. 16. From the /var/home/ftp/pub directory, run a bash program. 17. Type read_csi_file -f filename. Press Enter where filename in this example is CsiXln. The system renames the translation files as xln1 and xln2.
Post-migration administration
18. Type cd /etc/opt/defty. Press Enter. 19. Type ls -ltr. Press Enter. Verify that the xln1 and xln2 files are not zero length. 20. Open a SAT session. 21. Type reset system 4. Press Enter to load the restored translations into memory. If the restore process fails, you get an error message with the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process.
This section describes the post-migration administration to complete the migration to the S8400 Media Server.
!
Important:
Important: When you format the compact flash card for use in the S8400 Media Server, all data is erased from the compact flash card.
Note:
Note: Do not use the compact flash card (Comcode 700381841) in an S8100 Windows system. The operation system does not recognize the compact flash card.
After the migration, you can format the compact flash card (Comcode 700381841) for the S8400 Media Server and use the compact flash card as the backup compact flash card.
Assigning IP addresses to the SIPI circuit packs

When you use static IP addressing, you must assign IP addresses to the SIPI circuit packs.
Issue 2.1 June 2006
345
Using static addressing

You can administer static IP addresses for the SIPI circuit packs. You administer the addresses directly through the Ethernet port connection on the SIPI faceplate (top port). For more information, see Figure 2: Connecting directly to the SIPI. Figure 2: Connecting directly to the SIPI
CLK
S E R V I C E N E T W O R K
2 3
cadlipsi KLC 031502
Figure notes: 1. Services laptop 2. PCMCIA Network Interface Card (NIC) 3. NIC adapter cable (if necessary) 4. CAT5 crossover cable to SIPI
Note:
Note: Ensure that you have the password before proceeding.

You 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: 1. Click Start > Run to open the Run dialog box. 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:

Logging in to the SIPI

To log in to the SIPI: 1. Type telnet 192.11.13.6. Press Enter to open the Telnet window and connect to the SIPI Prompt = [IPSI]: Note: While connected to the SIPI, type help or ? to obtain online help. Most commands have two or three letter abbreviations. 2. Type ipsilogin. Press Enter. The abbreviated command is il. Note: The craft login used on the SIPI has a different password than the craft login used on the media servers. 3. Log in as craft. Prompt = [IPADMIN]:
Note:
Note:
Issue 2.1 June 2006
347
Setting the control interface

To set the control interface: 1. Type show control interface. Press Enter. 2. Type show port 1. Press Enter to see the current settings. 3. Type set control interface ipaddr netmask, where ipaddr is the customer-provided IP address and netmask is the customer provided subnet mask. Press Enter.
4. Enter quit to save the changes and exit the SIPI session. 5. Telnet to 192.11.13.6 and login. 6. Enter show control interface. The system displays the IP address, subnet mask, and default gateway information. Verify that the proper information was entered. 7. If a default gateway is used, enter the gateway IP address with set control gateway gatewayaddr, where gatewayaddr is the customer-provided IP address for their gateway. 8. Enter quit to save the changes and exit the SIPI or IPSI session. 9. Telnet to 192.11.13.6 and login. 10. Use show control interface to verify the administration. 11. Type exit. Press Enter to see the changes.
Resetting the SIPI

To reset the SIPI: 1. Type reset. Press Enter Answer Y to the warning. Note: Resetting the SIPI terminates the administration session. If further administration is required, start a new telnet session to the SIPI. Note: Control network settings become effective when you exit the IPADMIN session. Control settings include the IP address, the subnet mask, and the gateway. 2. Disconnect the Services laptop from the faceplate. 3. Check the LCD. Verify that it has an I P with a filled-in V that shows at the bottom. For more information, see Figure 3: LED display that shows that the SIPI has a static IP address. Figure 3: LED display that shows that the SIPI has a static IP address
Note:
Note:
CLK
ETR
S E R V
Note:
Note: Clear the ARP cache on the laptop before connecting to another SIPI. If the cache is not cleared, the laptop appears to stop and does not connect to the next IPSI. For more information, see Clearing the ARP cache on the laptop computer on page 346. 4. Close the window.
fpdlled2 LAO 112905
Issue 2.1 June 2006
349
Enabling control of the SIPI

To enable control of the SIPI: Note: Ensure that the TN8412P SIPI has the current firmware.
Note:
! CAUTION:
CAUTION:
This procedure allows the media server to take control of the SIPI-controlled port network(s). Failure to complete the procedure correctly can result in no connection to the network. 1. Type add cabinet 1. Press Enter. 2. Administer the appropriate cabinet type and carriers. 3. Type add ipserver-interface 1 where 1 means port network. Press Enter. 4. In the Host field, type in the IP address that was programmed into the SIPI. Press Enter. 5. Type save translation. Press Enter. 6. Type change system ipserver-interface. Press Enter. 7. In the IPSI Control of Port Networks field, type enabled. Press Enter. 8. Type save translation. Press Enter. 9. Verify the translation migration was successful. Place test calls, verify trunk status (if applicable), and so forth. The media server now controls all the port networks.
Verifying SIPI translations

To verify SIPI translations: 1. Type list ipserver-interface. Press Enter. 2. Verify that the SIPI circuit pack(s) is translated.
Verifying SIPI connectivity

To verify SIPI connectivity: 1. Start a Web browser. 2. Under Diagnostics, click Ping. 3. Under Endpoints to Ping, select IPSIs with cab number (199) ___ carrier number ___. 4. Type the correct cabinet and carrier numbers in the text boxes. 5. Click Execute Ping. 6. Verify that the endpoints respond correctly.
Verifying the customer data

The new translations must include all the media gateway and circuit pack administration. This data includes the:

Media gateway Circuit pack administration of the changed cabinets
Verify that the data is correct.
Verifying circuit pack locations

To verify circuit pack locations: 1. Type list cabinet. Press Enter to view all the cabinets. Verify that the screen shows the cabinet number that is assigned to the changed cabinets. 2. Type display cabinet number, where number is the cabinet number of the changed cabinet. Press Enter. Under Carrier Description, Carrier Type verify that the number of carriers there are in use matches one of the following numbers:

For a single carrier cabinet (SCC), the number of media gateways in the stack For a G600 or G650 Media gateway, the number of media gateways in the rack
Issue 2.1 June 2006
351
Verifying circuit pack insertion

To verify circuit pack insertion: 1. To see the list of all the slot locations, type list configuration all. Press Enter. 2. Verify that the circuit pack code and vintage number appears in the Code and Vintage fields. If No board appears in either field, a circuit pack was not installed in that slot.
Verifying the IP addresses

Ensure that the node names and IP addresses assigned to the TN2302AP IP Media Processor circuit pack and the TN799DP C-LAN circuit pack are the same as before the migration. To verify the IP addresses: 1. To get the node names for the TN2302AP IP Media Processor circuit pack and TN799DP C-LAN circuit pack in the slots of interest, type display ip-interfaces. Press Enter. 2. To verify that the node names exist and that the IP addresses match the node names, type list node-names. Press Enter.
Checking the link status

Compare the list that you made before the migration. Ensure that the in-service or the out-of-service links match the status of the links before the migration. To check the link status: 1. Type display communication-interface links. Press Enter. 2. Record all the enabled links. 3. Type status link number where number is a number 1-99. Press Enter. 4. Compare which links are in service with the premigration list. 5. Repeat steps 3 and 4 for all link numbers.
Upgrading firmware
Each TN8412AP S8400 IP Interface (SIPI) circuit pack must be on the most current and same firmware load. You might need to upgrade the firmware on the SIPI. The most current firmware load is on the installation CD. To obtain the firmware, you also can go to Avaya Support Web page at (http://avaya.com/support and click Downloads. First, verify the version of firmware that is currently on the SIPI circuit pack. 1. Under Installation and Upgrades, click View IPSI Version. Select Query All and click View IPSI Version. 2. Verify the firmware release for the TN8412AP SIPI circuit pack. If necessary, upgrade the firmware on the just installed SIPI circuit pack that you just installed. For more information, see Upgrading firmware on the IPSIs and SIPIs on page 283. You also must upgrade the firmware on the following circuit packs, if necessary.

UDS1 (TN464GP, TN2464BP, and TN2313AP) Maintenance/Test (TN771DP) Control LAN (C-LAN) (TN799DP) IP Media Processor (TN2302AP)
For more information, see Upgrading firmware on the IPSIs and SIPIs on page 283.
Testing the installation

Test the complete installation. For more information, see Testing the Complete Configuration on the Documentation for Avaya Communication Manager Release 3.0, Media Gateways and Servers CD-ROM.

Issue 2.1 June 2006
353
Troubleshooting the migration

For more information, see Troubleshooting an Installation on the Documentation for Avaya Communication Manager Release 3.0, Media Gateways and Servers CD-ROM.
Returning replaced equipment

Once you determine that the port network functions, return the old processors and any other replaced equipment to Avaya. Use established procedures.
Migrating from a DEFINITY Server CSI in a CMC with an ATA Flash to an S8400 Media Server
Use these procedures to migrate from an existing DEFINITY Server CSI in a Compact Modular Cabinet (CMC) or G600 Media Gateway to an Avaya S8400 Media Server. Use the ATA flash card on the TN2402 ProLogix Processor circuit pack for whichever loads that circuit pack supports. To migrate an existing DEFINITY Server CSI in a CMC, you use one TN8412AP S8400 IP Interface (SIPI) circuit pack to control the one port network. You must replace the TN2182 Tone Clock circuit pack with a SIPI circuit pack that you install in the A position in the cabinet. You also must remove the processor circuit pack. This migration affects service.
Replace the tone clock circuit pack with the TN8412AP S8400 IP Interface (SIPI) circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Replace the processor circuit pack with the TN8400AP Media Server circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Enable control of the SIPI and switch control to the media server Complete the postmigration administration
Issue 2.1 June 2006
355
Migration paths
Avaya supports the following migrations of a DEFINITY Server CSI in a CMC or a G600 Media Gateway to the S8400 Media Server configuration:
DEFINITY Release 9 and later
To migrate, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Copy the translations to the compact flash. 2. Plug the Compact Flash card from the PCMCIA/Compact Flash adapter into the Compact Flash slot on the TN8400AP Media Server circuit pack. 3. Copy the translation files from the compact flash to the S8400 Media Server.
Prerequisites

Presite checklist on page 357 - Perform these tasks before you go on site. Additional tasks on page 359 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 361 - Perform these tasks before you go on site. On site migration checklist on page 361 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 363 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite checklist
:
Description Correct hardware components include: 40 MB available disk space direct Ethernet cable serial cable and adapter RS-232 port connector Network interface card (NIC) with a 10/100 BaseT Ethernet interface 10/100 BaseT Ethernet, category 5, or better, crossconnect cable with an RJ45 connector on each end, MDI to MDI-X CD-ROM drive Correct software components include: Windows 2000/XP operating system Terminal emulation program: HyperTerminal or other TCP/IP networking software: bundled with Windows OS Web browser: Internet Explorer 5.0 or later For example, obtain logins and passwords for the following components: Media Server Media Gateway auxiliary equipment Communication Manager These logins and passwords include the equipment of the customer. You need a new license file and authentication file. You need the serial number from the reference IPSI and the SAP order number to generate a new license file. 1 of 3
Obtain appropriate logins and passwords for all equipment and software.
Issue 2.1 June 2006
357
Task Verify that you have the Communication Manager software distribution CD with the current software and firmware. Verify that you have the current preupgrade or premigration service packs, if required, on your laptop. Verify that you have the current post-upgrade or post-migration service packs, if required, on your laptop. Verify that you have the current firmware available.
Description You use this CD to install the software on the media server and upgrade the firmware.
Check which service packs you need and download files from the Avaya Support Web site (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site (http:// avaya.com/support).

For the most current versions, go to the Avaya Support web site (http://avaya.com/support). Click Downloads and select the product. Download license and authentication files to your Services laptop. Avaya technical support representatives only: Obtain the static craft password. New license and authentication files are necessary. Obtain information and download files from the Remote Feature Activation (RFA) web site at http:// rfa.avaya.com. Call the ASG Conversant number, 800-248-1234 or 1-720-444-5557 and follow the prompts to get the password. You need the Product ID, the FL, or IL number of the customer. 2 of 3
Migration paths
Description This step is necessary if the configuration of the customer INADS alarming modem has changed as well as any changes to the system alarming configuration. ART is available only to Avaya associates. Business Partners can call 800-295-0099. These files can include: service packs license file authentication file firmware for programmable circuit packs 3 of 3
Additional tasks
Issue 2.1 June 2006
359
Premigration setup
The premigration team must complete the following tasks. If these tasks are not completed, do not continue with the migration. For more information, see Migration paths on page 356. To migrate from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task Ensure that the technical support representative has access to the ASG Site Manager tool. Description If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. The STARS team provides the escalation path to report ASG troubles during the upgrade. Verify that you have the appropriate logins and passwords to access the media servers and server complex components. This event happens at least one day prior to the migration.
Migration paths

Before you go on site, complete the following tasks: Task Verify that the voice network, dial plan, and E911 for remote locations were redesigned. Verify that all existing circuit packs work with the new system. Replace any TN799B/C C-LAN circuit packs. Replace the 259A adapter and CAT3 cable. Replace TN570 EI circuit packs. Description Perform this task only if applicable.
Check the Minimum Vintage Table. Go to the Hardware and Software Compatibility Matrix (ftp// ftp.avaya.com/incoming/Up1cku9/tsoweb/media/ minhardwarevintages.pdf). Replace with the TN799DP circuit pack. Replace with the cable extender adapter (Comcode 848525887) and the CAT5 or better cable. Replace with TN570B vintage 7 or later circuit packs.

Issue 2.1 June 2006
361
Migration tasks

Migration tasks
! CAUTION:
CAUTION:
This migration affects service because when you turn off the processor port network (PPN), the system drops all calls. Service returns when the media server takes control of the IPSIs.

Turn off the processor gracefully - preconversion administration Replace the processor circuit pack or tone clock circuit pack with an IP Server Interface (IPSI) circuit pack Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the SIPI circuit pack
You can reuse the translations from the existing system when you migrate to an S8400 Media Server.
Issue 2.1 June 2006
363
Note:
Note: You must install the new Communication Manager license file on the media server before you make the change or the system will not run.
Perform these tasks to convert a processor port network to a port network (CMC). Premigration administration:

Connecting to the processor on page 365 Removing netcon data modules on page 366 Verifying system status on page 367 Recording all busyouts on page 367 Recording node names and IP addresses on page 367 Saving translations on page 368
Migration tasks:

Verifying hardware on page 369 Turning off the power to the control cabinet on page 369 Removing circuit packs on page 369 Inserting circuit packs on page 370 Connecting cables on page 370 Replacing the TN799C C-LAN circuit pack on page 371 Installing TN771 Maintenance/Test on page 371 Installing the software load on page 372 Configuring the media server on page 372 Copying translation files to the media server on page 373
Post-migration administration:

Using static addressing on page 375 Clearing the ARP cache on the laptop computer on page 375 Logging in to the SIPI on page 376 Setting the control interface on page 376 Resetting the SIPI on page 378 Enabling control of the SIPI on page 379
Verifying SIPI translations on page 379 Verifying SIPI connectivity on page 380 Verifying the customer data on page 380 Verifying circuit pack locations on page 380 Verifying circuit pack insertion on page 381 Verifying the IP addresses on page 381 Checking the link status on page 381 Upgrading firmware on page 382 Testing the installation on page 382 Busying out previously busied out trunks on page 382 Troubleshooting the migration on page 382
This migration affects service because you must turn off the CMCs to replace the processor and tone clock circuit packs. Before you turn off the cabinets, you must perform the following premigration administration.

Issue 2.1 June 2006
365

Group Number
99
Member 1



To record node names and IP addresses: 1. Note the node names and the IP addresses that are assigned to the TN2302AP IP Media Processor and the TN799C/DP C-LAN circuit packs. Ensure that these names and addresses are the same after the migration. Note: If the existing system has TN799C C-LAN circuit packs, you must replace these circuit packs with TN799DP circuit packs. 2. To get the node names for the TN2302AP IP Media Processor and TN799C/DP C-LAN circuit packs, type display ip-interfaces. Press Enter.
Note:
Issue 2.1 June 2006
367
3. To get the IP addresses that match the node names, type list node-names. Press Enter. 4. Record the information for use after the migration.
Saving translations
This step is important in case you need to back out of the migration. To save translations: Note: Save translations to a flash card. 1. Plug the PCMCIA/Compact Flash adapter in the PCMCIA slot on the TN2402 ProLogix Processor circuit pack. 2. Type save translation. Press Enter to save translations to the system disk. 3. The system displays a Command successfully completed message or an error message.
Note:
Migration tasks
You can reuse the translations from the current system when you migrate to an S8400 Media Server.
Note:
Note: You must install the new Communication Manager license file on the media server before you make the change. The SIPI serial number can be used for licensing purposes.
Migration tasks
Verifying hardware
Note:
Turning off the power to the control cabinet

! CAUTION:
CAUTION:
Ensure that you have completed the premigration administration. If you do not perform the premigration administration, the system will not function. For more information, see Migrating translations on page 814.
To turn off power to the control cabinet: 1. On the faceplate of the processor, press and hold the shutdown button until the shutdown process starts. When you see the green light the system is shut down.
! DANGER:
DANGER:
The latch on the power supply acts as the DC power switch and removes only DC power from the backplane. To remove the AC power from the cabinet, pull the AC power cord from the back of the cabinet. 2. Unplug the power cord from the back of the cabinet to turn off the cabinet.

Issue 2.1 June 2006
369

Connecting cables
To connect cables: 1. On the rear of the carrier, connect the media server cable adapter into port 1 on the rear of the TN8400AP Media Server circuit pack. 2. Connect the amphenol connector into slot A02 on the rear of the TN8412AP SIPI circuit pack. 3. Connect the customer LAN cable into the port labeled ETH-B on the adapter in slot A01. 4. Connect the IPSI cable into the port labeled ETH-A on the adapter in slot A01. 5. Connect the other end of the IPSI cable to the amphenol connector in slot A02. 6. Connect the power plug on the DVD drive to a wall outlet. 7. Connect the USB DVD drive to the USB port on the faceplate of the TN8400AP Media Server circuit pack. 8. On the DVD drive, ensure that the on/off/ext switch is in the EXT position. 9. Insert the Communication Manager CD into the USB DVD drive. 10. Connect the Services laptop to the Services port on the front of the TN8400AP Media Server circuit pack. 11. Turn on the power to all cabinets.


Issue 2.1 June 2006
371

To install the software load: 1. From the Services laptop, click Start > Run to open the Run window. 2. Type ping -t 192.11.13.6. Press Enter to indicate when the Services port is responding. 3. Click Start > Run to open the Run window. 4. Type telnet 192.11.13.6. Press Enter to telnet in to the Services port on the front of the S8400 Media Server. 5. When the prompt displays with menu options, select Install or Upgrade Software. Use the arrow keys to navigate and the space bar to select. When the system finishes, the media server reboots. 6. Open a Web browser. 7. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 8. Log in as craft or dadmin.

To configure the media server: 1. Open a Web browser. 2. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 3. Log in as craft or dadmin. 4. Under Maintenance, click Launch Maintenance Web Interface. 5. Under Server, click Server Date/Time. 6. In the Server Date/Time window, verify the data and time are correct. If the date and time are incorrect:: a. Enter the date b. Enter the time c. Select the time zone d. Click Submit:
7. Under Server Configuration, click Configure Server. The system starts the Configure Server Wizard. 8. In the Review Notices window, click Continue. 9. In the Back Up Data window, click Continue. 10. In the Specify how you want to use this wizard page, select Configure all servers using the wizard and click Continue. Note: You can set up media servers to various configurations. The following steps provide a general outline of required steps to complete the configuration. 11. In the Set Server Identifies window, perform the following steps:

Note:

To copy translation files to the media server: 1. Plug the Compact Flash card with the translations from the PCMCIA/Compact Flash adapter into the Compact Flash slot on the TN8400AP Media Server circuit pack. 2. From the Services laptop, open a bash session.
Issue 2.1 June 2006
373
3. Type read_csi_xln and press Enter to bring the CSI translations from the Compact Flash to the /etc/opt/defty directory. The system renames the translation files as xln1 and xln2. 4. Type cd /etc/opt/defty and press Enter. 5. Type ls -ltr and press Enter. Verify that the xln1 and xln2 files are not zero length. 6. Open a SAT session. 7. Type reset system 4 and press Enter to load the restored translations into memory. If the restore process fails, you get an error message with the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process.
!
Important:
Note:


CLK
2 3
cadlipsi KLC 031502
Note:

Issue 2.1 June 2006
375


Note:
Note:

To set the control interface: 1. Type show control interface. Press Enter. 2. Type show port 1. Press Enter to see the current settings.
3. Type set control interface ipaddr netmask, where ipaddr is the customer-provided IP address and netmask is the customer provided subnet mask. Press Enter.
Issue 2.1 June 2006
377
Resetting the SIPI

Note:
Note:
CLK
ETR
S E R V
Note:
fpdlled2 LAO 112905

Note:
! CAUTION:
CAUTION:

Issue 2.1 June 2006
379








Issue 2.1 June 2006
381
Upgrading firmware




Migrating from a DEFINITY Server CSI in a CMC to an S8400 Media Server using Xmodem
Use these procedures to migrate from an existing DEFINITY Server CSI in a Compact Modular Cabinet (CMC) with a linear flash to an Avaya S8400 Media Server that uses Xmodem. When you migrate an existing DEFINITY Server CSI in a CMC, you use one TN8412AP S8400 IP Interface (SIPI) circuit pack to control the one port network (PN). You must replace the TN2182 Tone Clock circuit pack with the SIPI circuit pack. You also must replace the TN798B Processor circuit pack. This migration affects service.
Replace the tone clock circuit pack with the TN8412AP S8400 IP Interface (SIPI) circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Replace the processor circuit pack with the TN8400AP Media Server circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Enable control of the SIPI and switch control to the media server Complete the postmigration administration
Migration paths
Avaya supports the following migrations of a DEFINITY Server CSI in a CMC to the S8400 Media Server configuration:
DEFINITY Release 8 and later
To migrate, you can use the existing translations. One supported method to move translations from legacy systems is to: 1. Copy the translations using Xmodem. 2. Copy the translation files to the S8400 Media Server.
Issue 2.1 June 2006
383
Prerequisites
You must complete the following tasks before you start the migration

Presite Checklist on page 384 - Perform these tasks before you go on site. Additional tasks on page 386 - Perform these tasks before you start the migration from an existing DEFINITY system. Premigration setup on page 387 - Perform these tasks before you go on site. On site migration checklist on page 388 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 390 - Have these documents ready to use while you perform the migration.
Tasks checklists
Presite Checklist
:
Migration paths

Issue 2.1 June 2006
385
Additional tasks
Migration paths
Premigration setup
Issue 2.1 June 2006
387


Migration paths
Issue 2.1 June 2006
389

Migration tasks
! CAUTION:
CAUTION:
This migration affects service because you must turn off the CMC to replace the processor and tone clock circuit packs. Before you turn off the cabinets, you must perform the following premigration administration.

Migration tasks
Note:
Note: You must install the new Communication Manager license file on the media server before you make the change. The SIPI serial number can be used for licensing purposes.

Connecting to the processor on page 392 Removing netcon data modules on page 393 Saving translations on page 394 Verifying system status on page 394 Recording all busyouts on page 394 Recording node names and IP addresses on page 395
Migration tasks:

Verifying hardware on page 395 Connecting to the SAT on page 396 Copying translation files on page 396 Turning off power to all cabinets on page 396 Removing circuit packs on page 397 Inserting circuit packs on page 397 Connecting cables on page 397 Replacing the TN799C C-LAN circuit pack on page 398 Installing TN771 Maintenance/Test on page 398 Installing the software load on page 399 Configuring the media server on page 399 Installing the license and authentication file on page 401 Copying translation files to the media server on page 401 Copying translation files to the media server on page 402 Closing all sessions on page 403

Using static addressing on page 403 Clearing the ARP cache on the laptop computer on page 404 Logging in to the SIPI on page 405 Setting the control interface on page 406
Issue 2.1 June 2006
391
Resetting the SIPI on page 407 Enabling control of the SIPI on page 408 Verifying SIPI translations on page 408 Verifying SIPI connectivity on page 409 Verifying the customer data on page 409 Verifying circuit pack locations on page 409 Verifying circuit pack insertion on page 410 Verifying the IP addresses on page 410 Checking the link status on page 410 Upgrading firmware on page 411 Testing the installation on page 411 Busying out previously busied out trunks on page 411 Troubleshooting the migration on page 412 Returning replaced equipment on page 412


Group Number
99
Member 1
Issue 2.1 June 2006
393
Saving translations
This step is important in case you need to back out of the migration. To save translations: Note: Save translations to a flash card. 1. Plug the PCMCIA/Compact Flash adapter in the PCMCIA slot on the TN798B or TN2402 Processor circuit pack. 2. Type save translation. Press Enter to save the translations to the PCMCIA. The system displays a Command successfully completed message or an error message.
Note:


Migration tasks

Note:
Migration tasks
Note:
Verifying hardware
Note:
Issue 2.1 June 2006
395
Connecting to the SAT

To do connect to the System Administration Terminal (SAT): 1. Connect the Services laptop modem to an analog line. 2. On the Services laptop, click Start > Programs > Accessories > Communications > HyperTerminal. 3. In the Connect To window, fill in the appropriate data. Click OK. 4. In the Connect window, verify the information. Click Dial. 5. At the login prompt, type craft and the password. Press Enter. 6. For the Terminal Type, type VT220. Press Enter. You now are logged in to the SAT.
Copying translation files

To do copy the translation files: 1. On the SAT, type upload trans. Press Enter. 2. Click Transfer > Receive File. 3. In the Place received file in the following folder field, enter the location where the translation files are to be placed. 4. In the Use receiving protocol field, select Xmodem. Click Receive. 5. In the Receive Filename window, in the file name field, type in a file name. Click OK. 6. In Xmodem file to receive window, in the Error checking field, CRC is shown and attempts to upload the files three times and fails. CRC then changes to Checksum and Xmodem starts the upload. When the system finishes, the file is located in the directory designated in step 3.

! CAUTION:
CAUTION:
To turn off power to all cabinets:
Turn off the power to each cabinet.
Migration tasks


Connecting cables
To connect cables: 1. On the rear of the carrier, connect the media server cable adapter into port 1 on the rear of the TN8400AP Media Server circuit pack. 2. Connect the amphenol connector into slot A02 on the rear of the TN8412AP SIPI circuit pack. 3. Connect the customer LAN cable into the port labeled ETH-B on the adapter in slot A01. 4. Connect the IPSI cable into the port labeled ETH-A on the adapter in slot A01. 5. Connect the other end of the IPSI cable to the amphenol connector in slot A02. 6. Connect the power plug on the DVD drive to a wall outlet. 7. Connect the USB DVD drive to the USB port on the faceplate of the TN8400AP Media Server circuit pack. 8. On the DVD drive, ensure that the on/off/ext switch is in the EXT position. 9. Insert the Communication Manager CD into the USB DVD drive.
Issue 2.1 June 2006
397
10. Connect the Services laptop to the Services port on the front of the TN8400AP Media Server circuit pack. 11. Turn on the power to all cabinets.



To install the software load: 1. From the Services laptop, click Start > Run to open the Run window. 2. Type ping -t 192.11.13.6. Press Enter to indicate when the Services port is responding. 3. Click Start > Run to open the Run window. 4. Type telnet 192.11.13.6. Press Enter to telnet in to the Services port on the front of the S8400 Media Server. 5. When the prompt displays with menu options, select Install or Upgrade Software. Use the arrow keys to navigate and the space bar to select. When the system finishes, the media server reboots. 6. Open a Web browser. 7. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 8. Log in as craft or dadmin.

To configure the media server: 1. Open a Web browser. 2. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 3. Log in as craft or dadmin. 4. Under Maintenance, click Launch Maintenance Web Interface.
Issue 2.1 June 2006
399
5. Under Server, click Server Date/Time. 6. In the Server Date/Time window, verify the data and time are correct. If the date and time are incorrect:: a. Enter the date b. Enter the time c. Select the time zone d. Click Submit: 7. Under Server Configuration, click Configure Server. The system starts the Configure Server Wizard. 8. In the Review Notices window, click Continue. 9. In the Back Up Data window, click Continue. 10. In the Specify how you want to use this wizard page, select Configure all servers using the wizard and click Continue. Note: You can set up media servers to various configurations. The following steps provide a general outline of required steps to complete the configuration. 11. In the Set Server Identifies window, perform the following steps:

Note:


To copy translation files to the S8400 Media Server: 1. Open a Web browser. 2. Click Launch Maintenance Web Interface. 3. Under Miscellaneous, click Download Files. 4. Select Files to download from the machine Im using to connect to the server. 5. Click Browse and select the translation file saved on the Services laptop and click Download. A translation file example might be C:\Program Files\PCCsixln. The file is placed in the /var/home/ftp/pub directory of the S8400 Media Server. 6. Click Start > Run to open the Run window. 7. Type telnet 192.11.13.6. Click OK to telnet in to the Services port on the TN8412AP SIPI circuit pack. 8. Log in as craft or dadmin. 9. From the /var/home/ftp/pub directory, type read_csi_xmod -f filename. Press Enter where filename in this example is CsiXln. The system renames the translation files as xln1 and xln2. If the restore process fails, you get an error message with the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process. 10. Type cd /etc/opt/defty. Press Enter.
Issue 2.1 June 2006
401
11. Type ls -ltr. Press Enter. Verify that the xln1 and xln2 files are not zero length. 12. Open a SAT session. 13. Type reset system 4. Press Enter to load the restored translations into memory.

To copy translation files to the S8400 Media Server: 1. Open a Web browser. 2. Click Launch Maintenance Web Interface. 3. Under Miscellaneous, click Download Files. 4. Select Files to download from the machine Im using to connect to the server. 5. Click Browse and select the translation file saved on the Services laptop and click Download. A translation file example might be C:\Program Files\PCCsixln. The file is placed in the /var/home/ftp/pub directory of the S8400 Media Server. 6. Click Start > Run to open the Run window. 7. Type telnet 192.11.13.6. Click OK to telnet in to the Services port on the TN8412AP SIPI circuit pack. 8. Log in as craft or dadmin. 9. From the /var/home/ftp/pub directory, type read_csi_xmod -f filename. Press Enter where filename in this example is CsiXln. The system renames the translation files as xln1 and xln2. If the restore process fails, you get an error message with the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process. 10. Type cd /etc/opt/defty. Press Enter. 11. Type ls -ltr. Press Enter. Verify that the xln1 and xln2 files are not zero length. 12. Open a SAT session. 13. Type reset system 4. Press Enter to load the restored translations into memory.
Closing all sessions

To close all sessions: 1. From the HyperTerminal window, when the upload finishes The system displays a Command successfully completed message or an error message. 2. Type logoff. Press Enter.
!
Important:
Note:


You can administer static IP addresses for the SIPI circuit packs. You administer the addresses directly through the Ethernet port connection on the SIPI faceplate (top port). For more information, see Figure 6: Connecting directly to the SIPI.
Issue 2.1 June 2006
403
Figure 6: Connecting directly to the SIPI
CLK
2 3
cadlipsi KLC 031502
Note:



Note:
Note:
Issue 2.1 June 2006
405

Resetting the SIPI

Note:
Note:
CLK
ETR
S E R V
Note:
fpdlled2 LAO 112905
Issue 2.1 June 2006
407

Note:
! CAUTION:
CAUTION:






Issue 2.1 June 2006
409



Upgrading firmware



Issue 2.1 June 2006
411


Migrating from an IP600 or S8100 to an S8400 Media Server using ftp

Use these procedures to migrate from an existing IP600 system in a Compact Modular Babinet (CMC) or an S8100 switch in a Compact Modular Cabinet (CMC) to an Avaya S8400 Media Server using file transfer protocol (ftp). The existing systems supported for migrations must be standard reliability and direct connect. In all instances, the cabinets can be reused as port networks (PNs). However you can add a G650 Media Gateway PN if the existing system has one PN. When migrating an existing S8100 in a CMC, you use one TN8412AP S8400 IP Interface (SIPI) circuit pack to control the PN. You also must replace the processor circuit pack. This migration affects service.
Install the TN8412AP S8400 IP Interface (SIPI) circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Replace the processor circuit pack with the TN8400AP Media Server circuit pack. For more information, see Quick Start for Hardware Migration: Avaya S8400 Media Server in an Avaya CMC1 or G600 Media Gateway (03-300706). Enable control of the SIPI and switch control to the media server Complete the postmigration administration
Replacement of INTUITY AUDIX Messaging with IA770 INTUITY AUDIX Messaging

The S8100 Media Server offers an embedded version of the INTUITY AUDIX Messaging application. This application is not supported on the S8400 Media Server. Instead, the customer may choose to install the embedded IA770 INTUITY AUDIX Messaging application, INTUITY AUDIX Messaging R5.1, or INTUITY AUDIX Messaging LX.
Issue 2.1 June 2006
413
Installation of IA770 INTUITY AUDIX Messaging software

If you install the IA770 INTUITY AUDIX application as a part of this migration, you install the software as part of the Communication Manager software. If you install an external version of INTUITY AUDIX Messaging or Modular Messaging, all installation is done on the external messaging server.
INTUITY AUDIX data that can be reused in IA770 INTUITY AUDIX Messaging and data that must be reinput
Though you restore the S8100 switch translations in the S8400 Communication Manager as a part of this migration, you cannot use Communication Manager Web pages to restore INTUITY AUDIX administration data to the installed IA770 INTUITY AUDIX application. This restriction includes all administration data previously defined in the INTUITY AUDIX itself through the INTUITY AUDIX windows or the AUDIX command line interface. This restriction also includes messages, greetings, and names. Note: The customer administrator should advise subscribers well in advance that their messages, greetings, and names will be deleted during the upgrade and will not be restored. Additionally, the administrator should advise subscribers to use Message Manager to save critical messages on their P.C.s. These messages will remain available only on the P.C. to which the messages were saved. The messages cannot be reimported into IA770 INTUITY AUDIX Messaging.
Note:
To save some time, you can export INTUITY AUDIX mailbox data prior to the upgrade and import the mailbox data after the upgrade using Avaya Site Administration, ProVision, or another tool. However, you must manually reinput all other administration data using the IA770 INTUITY AUDIX interface, Avaya Site Administration, or ProVision. However, some key switch translations within Communication Manager that support INTUITY AUDIX Messaging are restored as part of the switch translation restore and can be reused. These translations include:

The AUDIX coverage path The assignment of the AUDIX coverage path for each telephone extension
However, the following switch translations must be modified for the IA770 INTUITY AUDIX application:

The node name for AUDIX The AUDIX hunt group
Migration paths
Note:
Note: The IA770 INTUITY AUDIX hunt group does not require assigned AUDIX ports. Note the extensions of the ports previously assigned to the hunt group, and remove them from the hunt group.
Additional switch elements like a signaling group and trunk group must also be administered to support IA770 INTUITY AUDIX Messaging. For information on how to administer these and all switch integration elements, see Avaya IA770 INTUITY AUDIX Messaging Application Release 3.1 Administering the S8300 and S8400 Media Servers to Work with IA770, 07-600788.
Removing unused INTUITY AUDIX ports or hunt groups

The previously administered INTUITY AUDIX analog ports from the S8100 translations are part of the overall station usage of the switch and count against the maximum station capacity available on the S8400 Media Server. The hunt group for the IA770 INTUITY AUDIX applications does not use analog ports. Therefore, after you modify the AUDIX hunt group for IA770 INTUITY AUDIX Messaging, the hunt groupss previously assigned AUDIX ports are available for use by telephones or other devices. Use the remove station command to remove these ports from the switch so that they can be added later for future use. If you do not replace the S8100 embedded INTUITY AUDIX application as part of the migration to the S8400 Media Server, you should remove the hunt group from switch administration, and then remove the analog ports. In this case, you also must modify the administration of each subscriber telephone to remove the AUDIX coverage path. For information on how to administer these elements, see Avaya IA770 INTUITY AUDIX Messaging Application Release 3.1 Administering the S8300 and S8400 Media Servers to Work with IA770, 07-600788.
Migration paths
The IP600 or S8100 and their releases that can be migrated to S8400 Media Server configuration include:
Communication Manager Release 9 and later
To migrate, you can use the existing translations. The only supported method to move translations from legacy systems is to use ftp. When you migrate from an IP600 or an S8100 to an S8400 Media Server using ftp: 1. On the SAT, copy the translation files. 2. Move the translations onto the Services laptop. 3. Copy the translations to the S8400 Media Server.
Issue 2.1 June 2006
415
Prerequisites

Presite checklist on page 416 - Perform these tasks before you go on site. Additional tasks on page 418 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 420 - Perform these tasks before you go on site. Presite migration checklist on page 420 - Perform these tasks on site before you start the migration. On site migration checklist on page 420 - Have these documents ready to use while you perform the migration.
Tasks checklists
Presite checklist
:
Migration paths

Issue 2.1 June 2006
417
Additional tasks
Migration paths
Premigration setup
Issue 2.1 June 2006
419


Migration tasks
Migration tasks
! CAUTION:
CAUTION:
Issue 2.1 June 2006
421

You can reuse the translations from the existing system when you migrate to an S8400 Media Server. Note: You must install the new Communication Manager license file on the media server before you make the change. The SIPI serial number can be used for licensing purposes.
Note:

Connecting to the processor on page 424 Saving translations on page 424 Verifying system status on page 424 Recording all busyouts on page 425 Recording node names and IP addresses on page 425
Migration tasks:

Verifying hardware on page 426 Opening a SAT session on page 426 Copying translation files on page 426 Opening an ftp session on page 427 Moving the translation files on page 427 Turning off power to all cabinets on page 427 Removing circuit packs on page 428 Inserting circuit packs on page 428 Connecting cables on page 428 Replacing the TN799C C-LAN circuit pack on page 429 Installing TN771 Maintenance/Test on page 429 Setting telnet parameters on page 430 Installing the software load on page 430
Configuring the media server on page 431 Installing the license and authentication file on page 432 Copying translation files to the media server on page 432

Using static addressing on page 434 Clearing the ARP cache on the laptop computer on page 435 Logging in to the SIPI on page 435 Setting the control interface on page 436 Resetting the SIPI on page 437 Verifying SIPI translations on page 438 Verifying SIPI connectivity on page 439 Verifying the customer data on page 439 Verifying circuit pack locations on page 439 Verifying circuit pack insertion on page 440 Verifying the IP addresses on page 440 Checking the link status on page 440 Upgrading firmware on page 441 Administering IA 770 INTUITY AUDIX Messaging on page 441 Testing the installation on page 441 Busying out previously busied out trunks on page 442 Troubleshooting the migration on page 442 Returning replaced equipment on page 442
Issue 2.1 June 2006
423

Saving translations
This step is important in case you need to back out of the migration. These translations are not used in the migration. To save translations: Note: Save translations to a flash card. 1. Plug the PCMCIA/Compact Flash adapter in the PCMCIA slot on the TN2314 Processor circuit pack. 2. In DEFINITY, type save translation. Press Enter to save the translations.
Note:

Migration tasks


Note:
Migration tasks
Note:
Perform these tasks to change a processor port network to a port network (CMC).
Issue 2.1 June 2006
425
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: The TN8400AP Media Server circuit pack that contains the IA770 feature replaces the TN795 or TN2314 Processor circuit pack that does not have that feature. The current processor circuit pack must be returned to Avaya.
Note:
Opening a SAT session

To open a SAT session: 1. Using a crossover cable, connect the Services laptop to the Services port on the TN2314 or TN795 Processor circuit pack. 2. Click Start > Run to open the Run window 3. Type telnet 192.11.13.6. Press Enter. 4. Log in as lucent3. 5. At the LAC prompt, type definity or multivantage. Press Enter. 6. For the terminal type, select NTT.
Copying translation files

To copy translation files: 1. On the SAT, type save translations. Press Enter. 2. Type logoff and press Enter. 3. At the LAC prompt, type bash. Press Enter. 4. Type ftpserv. Press Enter. 5. At the prompt, type cd d:/LucentData/Definity. Press Enter. 6. Type cp xltn1_data.xln d:/LucentPub/ftproot/. Press Enter. 7. Type cp xltn2_data.xln d:/LucentPub/ftproot/. Press Enter. 8. Type ftpserv to turn on the ftp services. Press Enter.
Migration tasks
Opening an ftp session

To open an ftp session on the Services laptop: 1. On the Services laptop, click Start > Run to open the Run window. 2. Create a customer directory or create a directory at \temp for this migration. 3. Type cmd. Press Enter. 4. Type cd \temp or the directory location. Press Enter. 5. Type ftp 192.11.13.6. Press Enter. 6. Log in as anonymous. Press Enter. 7. For the password, press Enter. 8. At the ftp prompt, type bin. Press Enter. 9. Type get xltn1_data.xln. Press Enter. 10. Type get xltn2_data.xln. Press Enter. 11. Type bye. Press Enter to close the ftp session.
Moving the translation files

To move the translation files on the Services laptop
Move the xln files to the c:/temp directory.

! CAUTION:
CAUTION:
To turn off power to all cabinets: 1. From the bash prompt on the Services laptop, type shutdown system and press Enter to perform a graceful shutdown. 2. Wait until the Shutdown Complete LED on the lower portion of the faceplate of the processor is solid green 3. Turn off the power to all cabinets.
Issue 2.1 June 2006
427

To remove circuit packs from the CMC: 1. Remove the TN795 or TN2314 Processor circuit pack from slot A01. 2. Remove the TN744 Call Classifier-Detector circuit pack. 3. Remove the TN767 DS1 Interface circuit pack, if installed. 4. Remove the TN2207 DS1 Interface circuit pack, if installed. 5. Remove the TN2313 DS1 Interface circuit pack, if installed.

Connecting cables
To connect cables: 1. On the rear of the carrier, connect the media server cable adapter into port 1 on the rear of the TN8400AP Media Server circuit pack. 2. Connect the amphenol connector into slot A02 on the rear of the TN8412AP SIPI circuit pack. 3. Connect the customer LAN cable into the port labeled ETH-B on the adapter in slot A01. 4. Connect the IPSI cable into the port labeled ETH-A on the adapter in slot A01. 5. Connect the other end of the IPSI cable to the amphenol connector in slot A02. 6. Connect the power plug on the DVD drive to a wall outlet. 7. Connect the USB DVD drive to the USB port on the faceplate of the TN8400AP Media Server circuit pack.
Migration tasks
8. On the DVD drive, ensure that the on/off/ext switch is in the EXT position. 9. Insert the Communication Manager CD into the USB DVD drive. 10. Connect the Services laptop to the Services port on the front of the TN8400AP Media Server circuit pack. 11. Turn on the power to all cabinets.


Issue 2.1 June 2006
429
This section provides information to migrate translation files from the current media server to the S8400 Media Server.
Setting telnet parameters

The Microsoft telnet application can be set to send a carriage return (CR) and line feed (LF) whenever you press Enter. The installation program interprets this as two key presses. You need to correct this before you telnet to the server. Note that this procedure is done entirely on your laptop, not on the S8400 Media Server. To set the telnet parameters: 1. Click Start > Run to open the Run dialog box. 2. Type telnet. Press Enter to open a Microsoft Telnet session. 3. Type unset crlf. Press Enter. 4. Type display. Press Enter to confirm that Sending only CR is set. 5. Close the window by clicking the X in the upper-right corner. This procedure resets your Microsoft telnet defaults and does not need to be done each time you use Telnet.

To install the software load: 1. From the Services laptop, click Start > Run to open the Run window. 2. Type ping -t 192.11.13.6. Press Enter to indicate when the Services port is responding. 3. Click Start > Run to open the Run window. 4. Type telnet 192.11.13.6. Press Enter to telnet in to the Services port on the front of the S8400 Media Server.
5. When the prompt displays with menu options, select Install or Upgrade Software. Use the arrow keys to navigate and the space bar to select. When the system finishes, the media server reboots. 6. Open a Web browser. 7. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 8. Log in as craft or dadmin.

To configure the media server: 1. From the Services laptop, open a Web browser. 2. In the Address field, type http://192.11.13.6. Press Enter to access the login Web page. 3. Log in as craft or dadmin. 4. Under Server, click Server Date/Time. 5. On the Server Date/Time window, set the date, time, and time zone for the server. 6. Click Submit to put the changes into effect. 7. Under Maintenance, click Launch Maintenance Web Interface > Configure Server. 8. In the Review Notices window, click Continue. 9. In the Back Up Data window, click Continue. 10. In the Specify how you want to use this wizard page, select Configure all services using the wizard. Click Continue. Note: You can set up media servers to various configurations. The following steps provide a general outline of required steps to complete the configuration. 11. In the Set Server Identifies window:

Note:
Issue 2.1 June 2006
431
12. Click Continue. 13. In the Configure Interfaces window, set up as required. Click Continue. If you are installing the IA770 messaging application, in the Integrated Messaging area, enter the IP address in the IP address server1 field. Click Continue. 14. In the Ethernet Adjuncts window, set up as required. Click Continue. 15. In the External DNS Server Configuration window, set up as required. Click Continue. 16. In the Static Network Routes (Optional) window, set up as required. Click Continue. 17. In the Network Time Server window, set up as required. Click Continue. 18. In the Set Modem Interface window, set up as required. Click Continue. 19. In the Configure Maintenance Processor Complex (MPC) window, set up as required. Click Continue to configure the server. 20. When completed, under Miscellaneous, click Messaging Software. 21. Verify the messaging software is enabled. If messaging software is disabled, click Enable.


To copy translation files to the media server: 1. From the Services laptop, open a Web browser. 2. Click Launch Maintenance Web Interface. 3. Under Miscellaneous, click Download Files.
4. Select Files to download from the machine Im using to connect to the server. 5. Click Browse and select the translation file saved on the Services laptop and click Download. A translation file example might be C:\Program Files\PCM\xltn1_data.xln and xl.tn2_data.xln The file is placed in the /var/home/ftp/pub directory of the S8400 Media Server. 6. On the Services laptop, click Start > Run to open the Run window 7. Type telnet 192.11.13.6 and click OK to telnet in to the Services port on the TN8400AP S8400 circuit pack. 8. Log in as craft or dadmin. 9. Type cd /var/home/ftp/pub directory. Press Enter. 10. From the /var/home/ftp/pub directory, type read_s8100_file. Press Enter. The system renames the translation files as xln1 and xln2. If the restore process fails, you get an error message with the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process. 11. Type cd /etc/opt/defty. Press Enter. 12. Type ls -ltr. Press Enter. Verify that the xln1 and xln2 files are not zero length. 13. Open a SAT session. 14. Type reset system 4. Press Enter to load the restored translations into memory.
!
Important:
Note:
Note: Do not use the compact flash card (Comcode 700381841) in an S8100 Windows system. The operating system does not recognize the compact flash card.
After the migration, you can format the compact flash card with Comcode 700381841 for the S8400 Media Server and use the compact flash card as the backup compact flash card.
Issue 2.1 June 2006
433


CLK
2 3
cadlipsi KLC 031502
Note:



Note:
Note:
Issue 2.1 June 2006
435

Resetting the SIPI

Note:
Note:
CLK
ETR
S E R V
Note:
fpdlled2 LAO 112905
Issue 2.1 June 2006
437

Note:
! CAUTION:
CAUTION:






Issue 2.1 June 2006
439



Upgrading firmware

Administering IA 770 INTUITY AUDIX Messaging

Administer the IA 770 INTUITY AUDIX Messaging as required. For more information, see Avaya IA 770 INTUITY AUDIX Messaging Application, Administering the S8300 and S8400 Media Servers to work with IA 770.

Issue 2.1 June 2006
441



Chapter 5: Migrating to an Avaya S8500 Media Server

This chapter describes how to migrate from existing DEFINITY systems to the Avaya S8500 Media Server. The most common migrations are from non-Linux-based systems to Linux-based media servers. Non-Linux-based systems include systems such as the DEFINITY ONE/S8100. Less common migrations include migrations from one Linux-based media server to another. Not all non-Linux-based systems can migrate to a Linux-based media server. Whether you can migrate a system depends on the supported migration path. A migration path refers to the platform and the software release from which you can migrate to the new platform.

Use these procedures to migrate from existing DEFINITY systems to the Avaya S8500 Media Server with limited out-of-service time. The existing systems must be standard reliability and direct connect. You cannot migrate systems that use a center stage switch (CSS) or asynchronous transfer mode (ATM). In all instances, the cabinets can be reused as port networks (PNs). You do not need a G650 Media Gateway. However, you can add a G650 Media Gateway PN if the existing system has only one or two port networks. You can migrate the following existing systems:
DEFINITY Server SI in a single carrier cabinet (SCC) or multicarrier cabinet (MCC). You can migrate only the Direct-Connect configurations DEFINITY Server CSI in a compact modular cabinet (CMC). You can migrate only the IP-PNC configurations DEFINITY ONE in a CMC. You can migrate only the IP-PNC configurations. Avaya IP600/S8100 in a G600. You can migrate only the IP-PNC configurations.
Issue 2.1 June 2006
443

When you migrate to an S8500, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files by e-mail to the project manager before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418. These migration paths require that the media server is running Communication Manager Release 1.2.x, 1.3.x, 2.0.x, or 2.1.x software before the migration. Upgrades from a release that is earlier than Release 1.3.1 require that you install the preupgrade service pack before the upgrade to Communication Manager Release 3.1. An S8500 Media Server that is running Communication Manager Release 1.3.x or 2.x software can support a configuration that has one or more local survivable processors (LSPs) that are running Communication Manager Release 3.1 software. An S8500 Media Server running Communication Manager Release 3.1 software can support a configuration that has one or more Enterprise Survivable Servers (ESSs) running Communication Manager Release 3.x software. An S8500 Media Server that is running Communication Manager Release 3.1 software can support a configuration that consists of LSPs and ESSs. The LSPs and ESSs must be running Communication Manager Release 3.1 or later software. For more information, see the Upgrades chapter.
Migrating hardware
This information in this section is based on the assumption that the media server complex is installed, configured, and operational.
Migrating hardware

When you migrate an existing DEFINITY Server SI in a multicarrier cabinet (MCC), you use one TN2312BP IPSI circuit pack to control from one to three port networks (PNs). Avaya recommends that you install the IPSI in the A carrier in the existing processor port network (PPN) instead of in one of the expansion port networks (EPNs). But before you install the IPSI, you must convert the PPN to a PN. This process requires that you:

This migration affects service because you must be turn off the carrier. Before you turn off the cabinet, you must perform some premigration administration.

When you migrate an existing DEFINITY Server SI in a single carrier cabinet (SCC), you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the cabinet in the A position in the existing PPN instead of in one of the EPNs. But before installing the IPSI, you must convert the PPN to a PN. This process requires that you:

This migration affects service because you must turn off the PPN stack to replace the cabinet. Before turning off the cabinets, you must perform some premigration administration.

When you migrate an existing DEFINITY Server CSI or DEFINITY ONE in a compact modular cabinet (CMC), you use one TN2312BP IPSI circuit pack to control the PN. If a CSI, you replace the TN2182 Tone Clock circuit pack with the IPSI which you install in the A position of the cabinet. You also must remove the processor circuit pack. If a DEFINITY ONE, you replace the processor circuit pack with the IPSI. This migration affects service because you must turn off the CMCs to replace the processor and the tone clock circuit packs. Before you turn off the cabinets, you must perform some premigration administration.
Issue 2.1 June 2006
445

When you migrate an existing Avaya IP600, you use one TN2312BP IPSI circuit pack to control the PN. You also must replace the processor circuit pack with the IPSI which you can install in the A position of the cabinet. This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
Prerequisites for migrating to an S8500 Media Server


Migration modules

Migrating a DEFINITY Server CSI in a CMC to an S8500 Media Server on page 447 Migrating a DEFINITY Server SI Direct-Connect in an SCC to a Direct-Connect on page 477 Migrating a DEFINITY Server SI Direct-Connect in an MCC to a Direct-Connect on page 515 Migrating a DEFINITY ONE/S8100 to an S8500 Media Server on page 547 Migrating an Avaya IP600/S8100 to an S8500 Media Server on page 577
Migrating a DEFINITY Server CSI in a CMC to an S8500 Media Server

Use these procedures to migrate from an existing DEFINITY Server CSI in a compact modular cabinet (CMC) system to the Avaya S8500 Media Server with an IP-port network connectivity (PNC) configuration. The existing systems must be standard reliability. In all instances, the cabinets can be reused as port networks. However, you can add a G650 Media Gateway port network if the existing system has a port network. To migrate an existing DEFINITY Server CSI in a CMC, you use one TN2312BP IPSI circuit pack to control the one port network (PN). You must remove the TN2182 Tone Clock circuit pack and install an IPSI circuit pack in the A position. You also must remove the processor circuit pack. This migration affects service.

To migrate from DEFINITY platforms, you must:
Install the media server. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8500 Media Servers (555-245-701). Replace the tone clock circuit pack with the IPSI circuit pack Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media server Complete the postmigration administration
Issue 2.1 June 2006
447
Migration paths
Avaya supports the following migrations of a DEFINITY Server CSI in a CMC to the S8500 Media Server IP-PNC configuration:

DEFINITY Release 5 through Release 10 MultiVantage Release 11 and 1.x Communication Manager Release 2.0 through Release 3.1
To migrate, you can use the existing translations. The only supported method to move translations from legacy systems is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files through e-mail to the project manager before the migration. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
Prerequisites

Presite Checklist on page 449 - Perform these tasks before you go on site. Additional tasks on page 451 - Perform these tasks before you start the migration from an existing DEFINITY system. Premigration setup on page 451 - Perform these tasks before you go on site. On site migration checklist on page 454 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 454 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite Checklist
Before you go on site, perform the following tasks:
:
Issue 2.1 June 2006
449

Migration paths
Additional tasks
Premigration setup
The premigration team must complete the following tasks. If these tasks are not completed, do not continue with the migration. Some tasks need to be completed on site up to two weeks before starting the actual migration.

Freeze the translations. Send the translations to STS. Get the translations back from STS by e-mail.
Issue 2.1 June 2006
451
For more information, see Migration paths on page 448. When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally. Description For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. About 2 business days before the migration, create a trouble ticket to contact the STARS team. Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new authentication file is requested, ASG access (remote and on-site) is impacted. You need assistance from the Service Tools and Application Remote Support (STARS) team to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// gsomissrv2.global.avaya.com/request_system/ request.asp?tools_team=1 Mark the ticket status as CRITICAL. Indicate text in the ticket to notify the STARS team that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. Ensure that the technical support representative has access to the ASG Site Manager tool. If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. 1 of 2
Migration paths
Task The STARS team provides the escalation path to report ASG troubles during the upgrade. Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
Description This event happens at least one day prior to the migration.
Copy the translation file from STS to a directory on the Services laptop.
File size is usually in the range of 1-4 megabytes.
2 of 2

Issue 2.1 June 2006
453

When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task The customer supplies an open EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly. Verify that you have the license file that the file includes the licensed features. Verify that you have the Avaya authentication file. Description Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the documentation that comes with the rail kit.
Use the License File link on the Maintenance Web Interface to verify.

For a list of documents that Avaya recommends you have on hand for the migration, see Resources on page 54. You also need the following Additional documentation: Document Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide that provides physical installation and connection information.
Provides installation instructions for the S8500 Media Server.
Provides information on network connectivity.
Migration tasks
Migration tasks
! CAUTION:
CAUTION:
The following list describes the general migration procedures:

Turn off the processor gracefully - pre-conversion administration Replace the processor circuit pack or tone clock circuit pack with an IP Server Interface (IPSI) circuit pack Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the IPSI circuit pack
You can reuse the translations from the existing system when you migrate to an S8500 Media Server. Note: You must install the new Communication Manager license file on the media server before you make the change or the system will not run.
Note:

Connecting to the processor on page 457 Verifying system status on page 457 Recording all busyouts on page 458 Recording node names and IP addresses on page 458 Saving translations on page 458
Migration tasks:

Accessing the media server maintenance web interface on page 459 Copying translation files to media server on page 459 Restoring translation files on page 459 Administering the IPSIs on page 460 Adding IPSI translations to Communication Manager on page 461 Setting the alarm activation level on page 461 Backing up translations on page 461
Issue 2.1 June 2006
455
Verifying hardware on page 462 Changing the control cabinet to a port network on page 462 Turning off the power to the control cabinet on page 463 Replacing the processor circuit pack on page 463 Replacing the TN799C C-LAN circuit pack on page 464 Installing TN771 Maintenance/Test circuit pack on page 464 Connecting to the media server on page 465

Accessing the server command line interface with SSH protocol on page 465 Using static addressing on page 467 Clearing the ARP cache on the laptop computer on page 468 Logging in to the IPSI on page 468 Setting the control interface on page 469 Setting the VLAN and diffserv parameters on page 470 Resetting the IPSI on page 470 Verifying IPSI translations on page 471 Verifying IPSI connectivity on page 472 Enabling control of the IPSI on page 472 Verifying the customer data on page 472 Verifying circuit pack locations on page 473 Verifying circuit pack insertion on page 473 Verifying the IP addresses on page 473 Checking the link status on page 474 Upgrading firmware on page 474 Testing the installation on page 475 Busying out previously busied out trunks on page 475 Troubleshooting the migration on page 475 Returning replaced equipment on page 475


Issue 2.1 June 2006
457


Note:
Saving translations
Although the migrated translations are already copied to the media server, you must save the translations in case you need to back out of the migration. Note: Save translations to a flash card.
Note:
To save translations: 1. To save translations to the system disk, type save translation. Press Enter. Either a Command successfully completed The message displays or all error messages are logged.
Copying translation files to media server

To copy translation files to the media server: 1. Under Miscellaneous, click Download Files. 2. Click Files(s) to download from the machine Im using to connect to the server. 3. Click Browse and select the file saved on the services laptop. 4. Click Download to place the file on the media server.
Restoring translation files

To restore translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file might be at the top of the list. 4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files.
Issue 2.1 June 2006
459
6. Click Restore Status. 7. Select the first file and then scroll down and click Review Status to see the results of the restore. When the restore process completes, the screen displays Restore is finished. 8. Use Native Configuration Manager or Avaya Site Administration to start a SAT session. 9. Type reset system 4. Press Enter to load the restored translations. If the restore process fails, the system displays an error message that states the reason for the failure. The translation file is not restored. You must resolve the reason for the failure and restart the process.
Administering the IPSIs

To administer the IPSIs: 1. Type change system-parameters ipserver-interface. Press Enter 2. Verify that the Primary Control Subnet Address field is correct. The subnet address must match the most significant three octets (the first three groups of digits in the subnet address) of the server IP address that is listed on the control network entry from the completed Electronic Preinstallation Worksheet (EPW). An asterisk (*) to the right of the Subnet Address field means that although a subnet address displays, this address is incorrect. Avaya Communication Manager does not have the subnet information. After you verify the information shown on the screen, submit this form with or without changes to update the Communication Manager with the correct subnet information.
! CAUTION:
CAUTION:
If the information in the Primary Control Subnet Address field is incorrect, you must change the information on the media server. Use the Maintenance Web Interface. Under Server Configuration and Upgrades, click Configure Server to change the media server configuration. Then continue with step 3 of this procedure. 3. Verify that the Switch Identifier field is set correctly for this installation. You must enter the correct switch identifier here before you administer the TN2312 IPSI circuit packs. 4. Verify that the IPSI Control of Port Networks field is set to disabled. 5. Press Enter.
Adding IPSI translations to Communication Manager

To add IPSI translations to Communication Manager: 1. Type add ipserver-interface 1. Press Enter to add the IPSI circuit pack information. 2. If you use static addressing, in the Host field, type the IP address for the IPSI that is in the port network listed in the Location field. 3. Verify that the IP Control? field is set to y. 4. Verify that all the other fields are populated. 5. Press Enter to put the changes into effect. 6. Repeat Steps 1 through 5 for each IPSI.
Setting the alarm activation level

To set the alarm activation level: 1. Type change system-parameters maintenance. Press Enter. 2. In the CPE Alarm Activation Level field, select warning, minor, or major, depending on the level that the customer wants. The default is none.
To back up translations: 1. Under Data Backup/Restore, click Backup Now. 2. Select the data sets and the backup method. If you select Save ACP translations prior to backup, the media server automatically saves the translations to the hard drive before the media server saves the translations to the backup media. 3. Click Start Backup to begin the backup process.
Issue 2.1 June 2006
461
Migration tasks
Note:
Verifying hardware
Ensure that you have the conversion specific hardware on hand.
Note:
Note: The TN798 circuit pack or the TN2402 Processor circuit pack that contains the Audix feature is replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not have the Audix feature. You must return the existing processor circuit pack to Avaya.
Note:
Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Changing the control cabinet to a port network

To change the control cabinet to a port network (PN): 1. Remove the TN798 or the TN2402 Processor circuit pack. Replace the TN2182 Tone Clock circuit pack with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack. 2. Connect a CAT5 straight-through cable from the IPSI to the media server through the customer network.
Migration tasks
Note:
Note: If you replace a TN795 Processor circuit pack, you might not need the TN744D/E Call Classifier-Detector circuit pack. The TN2312BP IPSI circuit pack has call classifier functionality. However, increased voice and data traffic can require the TN744D/E Call Classifier-Detector circuit pack. Note: If you have a TN799C or earlier C-LAN circuit pack, you must replace the circuit pack with a TN799DP C-LAN circuit pack.
Note:

! CAUTION:
CAUTION:
! DANGER:
DANGER:
Replacing the processor circuit pack

To replace the processor circuit pack: 1. Remove the entire processor circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. You might need to reinstall this circuit pack if you must stop the migration. 3. Remove the TN2182 Tone Clock circuit pack.
Issue 2.1 June 2006
463
4. Remove the octopus cable from the connector that is associated with slot 2 on the connector panel. 5. Install the IPSI adapter to the connector that is associated with slot 2 on the connector panel. 6. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 7. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 8. Attach the new label above the circuit pack slots.
Note:

Installing TN771 Maintenance/Test circuit pack

You must replace the TN798 or the TN2402 circuit pack with a TN771 Maintenance/Test circuit pack. Each location must have one TN771 Maintenance/Test circuit pack. To install the TN771 Maintenance/Test circuit pack:
Install the TN771 circuit pack in slot 1. This carrier does not have a dedicated slot for the TN775 Maintenance (EPN) circuit pack.
Postmigration administration

To connect to the media server: 1. Connect one end of the green CAT5 straight-through cable to the Ethernet switch on the customer network. 2. Connect the other end of the cable to the IPSI adapter on the back of the media gateway.
Perform the following tasks to complete postmigration administration.
Accessing the server command line interface with SSH protocol

Note:
Note: Using the SSH protocol to access the server is applicable to CM Release 3.0 and forward.
To use this procedure with a laptop cable connection to the services port, you must configure your laptop for the network connection. See Network configuration on page 1242. In addition, a third-party SSH client must already be installed on your computer. 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: 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.
Note:
! 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.
Issue 2.1 June 2006
465
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:
Note:
Assigning IP addresses to the IPSI circuit packs

When you use static IP addressing, you must assign IP addresses to the IP server interface circuit packs.

You can administer static IP addresses for the IPSI circuit packs. You administer the addresses directly through the Ethernet port connection on the IPSI faceplate switch which is the top port (Figure 10: Connecting directly to the IPSI on page 467). Figure 10: Connecting directly to the IPSI
CLK
2 3
cadlipsi KLC 031502
Figure notes: 1. Services laptop 2. PCMCIA Network Interface Card (NIC) 3. NIC adapter cable (if necessary) 4. CAT5 cross-over cable to IPSI
Note:
Note: Ensure that you have the IPSI password before you continue.
Issue 2.1 June 2006
467


Logging in to the IPSI

To log in to the IPSI: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. Note: Most commands have abbreviations. For more help while you are connected to the IPSI, you can type help or ?. 2. Type ipsilogin. Press Enter. The abbreviated command is il. Note: The craft login that you use on the IPSI has a different password than the craft login used on the media servers. 3. Log in as craft. Prompt = [IPADMIN]:
Note:
Note:

To set the control interface: 1. Type show control interface. Press Enter. 2. To see the current settings, type show port 1. Press Enter. 3. Type set control interface ipaddr netmask, where ipaddr is the customer-provided IP address and netmask is the customer provided subnetmask. Press Enter.
4. To save the changes and exit the IPSI session, type quit. Press Enter. 5. SSH to 192.11.13.6 and log in. 6. Type show control interface. Press Enter. The system displays the IP address, the subnetmask, and the default gateway information. 7. Verify that the correct information was entered. 8. If a default gateway is used, enter the gateway IP address. Type set control gateway gatewayaddr, where gatewayaddr is the customer-provided IP address for their gateway. Press Enter. 9. To save the changes and exit the IPSI session, type quit. Press Enter. 10. SSH to 192.11.13.6 and log in. 11. To verify the administration, type show control interface. Press Enter. 12. To see the changes, type exit. Press Enter.
Issue 2.1 June 2006
469
Setting the VLAN and diffserv parameters

To set the VLAN parameters and the diffserver parameters: 1. Log back in as craft. 2. To display the quality of service values, type show qos. Press Enter. 3. If necessary, use the following commands to set the VLAN and diffserv parameters to the recommended values shown. Note: Use Help to obtain syntax guidelines for these commands.

Note:
Type set vlan priority 6 Type set diffserv 46 Type set vlan tag on Type set port negotiation 1 disable Type set port duplex 1 full Type set port speed 1 100
4. To check the administered values, type show qos. Press Enter. 5. To exit, type quit. Press Enter.
!
Important:
Important: Ensure that the port settings on the Ethernet switches are set to the same values as shown in the set port commands in step 3.
Resetting the IPSI

To reset the IPSI: 1. Type reset. Press Enter Answer Y to the warning. Note: Resetting the IPSI terminates the administration session. If further administration is required, start a new SSH session to the IPSI. Note: The IP address, subnet mask, and gateway control network settings become effective when you exit the IPADMIN session. 2. Disconnect the laptop computer from the faceplate.
Note:
Note:
3. Check the LCD. Verify that the display shows the letters I and P and a filled-in V that shows at the bottom (Figure 11: LED display that shows that the IPSI has a static IP address). Figure 11: LED display that shows that the IPSI has a static IP address
CLK
S E R V
Note:
Note: Clear the ARP cache on the laptop before you connect to another IPSI. If you do not clear the cache, the laptop appears to stop and does not connect to the next IPSI. For more information, see Clearing the ARP cache on the laptop computer on page 468. 4. Repeat steps 1 through 3 for each IPSI circuit pack.
Verifying IPSI translations

To verify IPSI translations: 1. Type list ipserver-interface. Press Enter. 2. Verify that the ISPI circuit pack(s) are translated. The State of Health - C P E G column shows 0.0.0.0 for each healthy IPSI. If a "1" shows in any position, you must troubleshoot the problem. Tip:
Tip:
The pattern 0.1.1.0 usually means that a cabinet type is administered incorrectly or a connectivity problem exists, such as an incorrectly terminated cable.
fpdlled1 LJK 022502
Issue 2.1 June 2006
471
Verifying IPSI connectivity

To verify IPSI connectivity: 1. Under Diagnostics, click Ping. 2. Under Endpoints to Ping, select IPSIs with cab number (199) ___ carrier number ___. 3. Type the correct cabinet and carrier numbers in the text boxes. 4. Click Execute Ping. 5. Verify that the endpoints respond correctly.
Enabling control of the IPSI

To enable control of the IPSI: Note: Ensure that the IPSI has the same, current firmware.
Note:
! CAUTION:
CAUTION:
This procedure allows the media server to take control of the IPSI-controlled port network(s). Failure to complete the steps correctly can result in no connection to the network. 1. Type change system-parameters ipserver-interface. Press Enter. The system displays IP Server Interface (IPSI) System Parameters window. 2. Set the IPSI Control of Port Networks: field to enabled 3. Press Enter to effect the change. 4. Type save translation. Press Enter.
The media server now controls all the port networks.






Issue 2.1 June 2006
473

Upgrading firmware
Each IPSI must be on the most current and same firmware load. You might need to upgrade the firmware on the IPSI. The most current firmware load is on the installation CD. To obtain the firmware, you also can go to Avaya Support Web page(http://avaya.com/support and click Downloads. First, verify the version of firmware that is currently on the IPSI circuit pack. 1. Under Installation and Upgrades, click View IPSI Version. Select Query All and click View IPSI Version. 2. Verify the firmware release for the TN2312BP IPSI. If necessary, upgrade the firmware on the just installed TN2313BP IP Server Interface circuit pack that you just installed. For more information, see Upgrading firmware on the IPSIs and SIPIs on page 283. You also must upgrade the firmware on the following circuit packs, if necessary.

UDS1 (TN464GP, TN2464BP, and TN2313AP) Maintenance/Test (TN771DP) Control LAN (CLAN) (TN799DP) IP Media Processor (TN2302AP)




Issue 2.1 June 2006
475
Migrating a DEFINITY Server SI Direct-Connect in an SCC to a Direct-Connect

Note: Once you complete the migration to fiber-PNC, you can convert to IP-PNC. See Converting PNs to IP-PNC on page 1041.
Note:
Use these procedures to migrate from an existing DEFINITY Server SI direct-connect in an single carrier cabinet (SCC) system to the Avaya S8500 or S8700-Series Media Server with a direct-connect configuration. These procedures are for migrating direct-connect to direct-connect configurations. If you want to change one or more port networks (PNs) to a fiber-port network connectivity (PNC) configuration, see Conversions on page 1035. The existing system uses expansion interface (EI) circuit packs to provide port network connectivity (PNC) for one, two, or three PNs. The existing system must be standard reliability. In all instances you can reuse the cabinets as PNs. However, you can add an EI-connected G650 Media Gateway PN if the existing system has only one or two PNs. To migrate an existing DEFINITY Server SI in an SCC, you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the cabinet in the A position in the existing processor port network (PPN) instead of in one of the expansion port networks (EPNs). But before you install the IPSI, you must change the PPN to a PN:

Replace the processor control cabinet with an expansion control cabinet Remove all the control circuit packs
This migration affects service.

Install the media server. If Avaya supplies the Ethernet switch(es), and uninterruptible power supplies (UPSs), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8500 Media Servers (555-245-701) or Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). Change the existing processor control cabinet/carrier to an expansion control cabinet/ carrier Replace tone clock circuit pack with IPSI circuit packs
Issue 2.1 June 2006
477
Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media server Complete the post-migration administration
Migration paths
Avaya supports the following migrations of a DEFINITY Server SI direct-connect in an SCC to the S8500 or S8700-Series Media Server direct-connect configuration include:

DEFINITY Release G3V4 DEFINITY Release G3/si (with Intel 386) DEFINITY Release 5 through Release 10 MultiVantage Release 11 and Release 1.x Communication Manager Release 2.0 through Release 2.2
Prerequisites
You must complete the following tasks before you start the migration. The pre-requisites are defined as follows:

Presite Checklist on page 479 - Perform these tasks before you go on site. Additional tasks on page 481 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 483 - Perform these tasks before you go on site. Documentation checklist for migrations on page 484 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite Checklist
:
Issue 2.1 June 2006
479

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
481
For more information, see Migration paths on page 478. When you migrate from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally. Description For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. About 2 business days prior to the migration, contact the STARS team by creating a trouble ticket. Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new RFA authentication file is requested, ASG access (remote and on-site) is impacted. You need assistance from the Service Tools and Application Remote Support (STARS) team to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// gsomissrv2.global.avaya.com/request_system/ request.asp?tools_team=1 Mark the ticket status as CRITICAL. Indicate text in the ticket to let the STARS team know that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. Ensure that the technical support representative has access to the ASG Site Manager tool. If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new RFA authentication file. 1 of 2
Migration paths
2 of 2

Issue 2.1 June 2006
483

For a list of documents that Avaya recommends you have on hand for the migration, see Resources on page 54. Additional documentation needed. Document Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Installing and Configuring the Avaya S8700-Series Media Server (03-300145) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide providing physical installation and connection information.
Provides installation instructions for the S8700-Series Media Server.
Migration tasks
! CAUTION:
CAUTION:
Migration tasks
The following list describes general procedures:

Turn off the power to the processor gracefully - pre-conversion administration Replace the processor control carrier/cabinet with an expansion control carrier or cabinet Replace the tone clock circuit pack and Maintenance circuit pack with an IP Server Interface (IPSI) circuit pack and new maintenance circuit pack, respectively Replace old expansion interface circuit packs with new expansion circuit packs, if necessary Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the IPSI circuit pack
Perform the following tasks to convert a processor port network to a port network (SCC). Premigration administration:

Migration tasks:

Accessing the media server maintenance web interface on page 489 Verifying the license file on page 489 Copying translation files to media server on page 489 Restoring translation files on page 490 Administering the IPSIs on page 490 Adding IPSI translations to Communication Manager on page 491 Setting the alarm activation level on page 491 Backing up translations on page 492 Verifying hardware on page 492 Removing the processor port network control cabinet on page 493 Installing the expansion control carrier on page 493 Stacking the port media gateways on page 494 Installing IPSI and maintenance circuit packs on page 494 Connecting the CAT5 cables to the IPSI circuit packs on page 497 Installing Expansion Interface circuit packs on page 501
Issue 2.1 June 2006
485
Turning on the media gateway on page 502

This migration affects service because you must turn off the PPN stack to replace the cabinet. Before you turn off the cabinets, you must perform the following premigration administration.
! CAUTION:
CAUTION:
The licensing of the platform and port network connectivity attributes for the S8700-Series Media Server can be complex. See Caution about platform/PNC license settings for the S8700-series Media Server on page 314 and License and Avaya authentication files on page 313.



Issue 2.1 June 2006
487

Note:
Saving translations
Note:
This section provides information for migrating translation files from the existing system to the S8500 or S8700-Series Media Server.

Verifying the license file

To verify the Communication Manager license file: 1. Under Security, click License File. 2. Verify that the Communication Mgr License Mode field is set to Normal.

To copy translation files to the media server: 1. Under Miscellaneous, click Download Files. 2. Click Files(s) to download from the machine Im using to connect to the server. 3. Click Browse and select the file that you saved on the Services laptop. 4. Click Download to place a copy of the file on the media server.
Issue 2.1 June 2006
489

To restore translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file might be at the top of the list. 4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file and then scroll down and click Review Status to see the results of the restore. When the restore process completes, the screen displays Restore is finished. 8. Use Native Configuration Manager or Avaya Site Administration to start a SAT session. 9. Type reset system 4. Press Enter to load the restored translations. If the restore process fails, the system displays an error message that states the reason for the failure. The translation file is not restored. You must resolve the reason for the failure and restart the process.

! CAUTION:
CAUTION:


Issue 2.1 June 2006
491
Migration tasks
You may reuse the translations from the existing system when migrating to an S8500 Media Server.
Note:
Perform these tasks to change a processor port network to a port network (SCC).
Verifying hardware
Migration tasks
Removing the processor port network control cabinet

To remove the processor port network control cabinet: 1. Label both ends of all the cables that you will remove from the cabinets. You will reuse these cables.
! CAUTION:
CAUTION:
All active calls that are processed through this PN are dropped when the cabinet stack is turned off. All trunks and lines within this cabinet stack are out of service until the cabinet stack is turned on and the media server controls the PN. Note: If the system is equipped with power failure transfer (PFT) units that use ground start trunks, you must install a temporary ground wire to the PFT units. This ground wire allows units to operate correctly when the cabinet is turned off. The AUX cable that usually supplies the ground is disconnected. 2. Connect a 10 AWG (#25) (2.6 mm2) wire to pin 49 of the connecting block or to pin 49 of the cable access panel (CAP) on the power failure transfer panel. 3. Route the opposite end of the wire to an approved ground and connect. 4. Turn off the cabinets in the SCC1 stack. 5. Remove all circuit packs from the cabinets. 6. Place the circuit packs in an antistatic carriers or bags. 7. Disconnect the cables on the front of the cabinets. 8. Disconnect the following cables on the back of the cabinets:

Note:
CURL. You must replace this cable. TDM/LAN. You can reuse this cable. ICC-A and ICC-B. You can reuse this cable.
9. Remove all cabinet grounds. 10. Remove the top cabinet. 11. Remove the subsequent cabinets, including control cabinet A.
Installing the expansion control carrier

To install the expansion control media gateway: 1. Install the J58890N expansion control media gateway. 2. Connect the media gateway grounds and power.
Issue 2.1 June 2006
493
Stacking the port media gateways

To stack the port media gateways: 1. If needed, stack a port media gateway (J58890H) on top of the expansion control media gateway. 2. If needed, stack a third and a fourth port media gateway on top of the first port media gateway. 3. Install the new CFY1B CURL unit on the back of control cabinet A. 4. Connect the following cables to the back of all the media gateways:

TDM/LAN ICC-A and ICC-B
Installing IPSI and maintenance circuit packs

To install the IPSI and maintenance card circuit packs: 1. Remove the TN2182 Tone Clock circuit pack from the control carrier. Place the circuit pack in an antistatic carrier or bag. Note: Do not remove the TN771 Maintenance/Test circuit pack if this circuit pack is present. 2. Remove the TN775B/C Maintenance (EPN) circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier or bag. 3. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot. 4. With the red line on the bottom, attach one end of the short ribbon cable to the connector on the component side of the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack (Ribbon cable connector on page 495).
Note:
Migration tasks
Figure 12: Ribbon cable connector
caxxinst LJK 022002
5. Push the tabs on the ends of the connector inward to lock the connector in place. 6. Thread the ribbon through the slot on the front panel (Simplex reliability ribbon cable connection on page 496). 7. Insert the TN775D Maintenance (EPN) circuit pack part way into the MAINTENANCE slot. 8. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D Maintenance (EPN) circuit pack with the red line on the bottom (Simplex reliability ribbon cable connection on page 496).
Issue 2.1 June 2006
495
Figure 13: Simplex reliability ribbon cable connection
B
MS AR AL J MA MIN RN W K AC TR ER EM ON
TO F AU OF
CLK
cadsdupx KLC 072502
9. Push the tabs on the ends of the connector inward to lock the connector in place. 10. Thread the ribbon through the slot on the front panel. 11. Fully insert the circuit packs. 12. In the rest of the empty slots, insert Z100C apparatus blanks. 13. Assign the switch ID and the cabinet ID to the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that you just inserted. For more information, see Assigning IP addresses to the IPSI circuit packs on page 537. Note: For consistency, use the ribbon in the front for connectivity. Do not use ICCC.
Note:
Migration tasks
Connecting the CAT5 cables to the IPSI circuit packs

Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) or Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703).
To connect the CAT5 cables to the IPSI circuit packs: 1. Connect the green CAT5 cable to the IPSI in the A carrier or the cabinet in the A position. 2. Remove the upper, rear, and the lower rear covers from the media gateway (Removal of the upper, rear, and the lower rear covers on page 497). Figure 14: Removal of the upper, rear, and the lower rear covers
KL
SM RA LA JA M NI M NR W KC A RT R NO EM E
FF OT UA
AU X 17
1 2
10 9
TE
RM
cadscatb LAO 091103
Figure notes: 1. Media gateway B 2. Upper rear cover 3. Lower rear cover
Issue 2.1 June 2006
497
3. Use a cable pass-thru kit to run the 25-m or 50-m green CAT5 cable from the Ethernet switch or customer network through the media gateway (CAT5 cable in pass-thru kit on page 498). Figure 15: CAT5 cable in pass-thru kit
CLK
MS AR AL J MA MIN N WR K AC TR ER EM ON
O AUT OFF
cadscat2 KLC 032602
Migration tasks
4. Install the clamp on ferrite on the CAT5 Ethernet cable (CAT5 cable run through the clamp-on ferrite on page 499). Figure 16: CAT5 cable run through the clamp-on ferrite
KL
FF OT UA
2 2
cadscata LAO 091103
Figure notes: 1. Media gateway A 2. Clamp on Ferrite
Issue 2.1 June 2006
499
!
WARNING:
WARNING: Locate the ferrite as close to the exit of the media gateway as possible. If the ferrite is not located as close to the exit as possible, the cable can pick up electromagnetic interference (EMI) from inside the cabinet.
5. Connect the green CAT5 cable to the bottom connector on the front of the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack in media gateway A (CAT5 cable connected to the IPSI on page 500). Figure 17: CAT5 cable connected to the IPSI
CLK
O AUT OFF
cadscat3 KLC 032602
Migration tasks
6. Replace the rear covers and the ground plate. Dress the CAT5 Ethernet cable to exit from either the left or the right side of the media gateway (Replacement of the upper and lower rear covers on page 501). Figure 18: Replacement of the upper and lower rear covers
KL
FF OT UA
AU X 17
1 2
10 9
TE
RM
cadscatc LAO 091103
Figure notes: 1. Media gateway B 2. Upper rear cover 3. Lower rear cover
Installing Expansion Interface circuit packs

You must replace any expansion interface circuit packs in the PPN.
If the existing PPN has TN776 or TN570 Expansion Interface circuit packs, you must replace them with a TN570B Expansion Interface vintage 7 or later circuit pack. If this system includes an Enterprise Survivable Server (ESS), replace the circuit packs with a TN570D or later Expansion Interface circuit pack.
Issue 2.1 June 2006
501
To install the Expansion Interface circuit packs: 1. Remove the existing circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. 3. Insert the TN570B Expansion Interface vintage 7 or later circuit pack into the EXPN INTFC slots (A01, A02). 4. Repeat Steps 1 and 2 for each PN that does not contain TN570B Expansion Interface vintage 7 or later circuit packs.
Turning on the media gateway

To turn on the media gateway: 1. Turn on the media gateways. 2. Remove the emergency ground wire if used.

Note:
To use this procedure with a laptop cable connection to the services port, you must configure your laptop for the network connection. See Network configuration on page 1242. In addition, a third-party SSH client must already be installed on your computer. 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:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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.
Note:
Note:
Issue 2.1 June 2006
503
9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.


You can administer static IP addresses for the IPSI circuit packs. You administer the addresses directly through the Ethernet port connection on the IPSI faceplate switch which is the top port (Figure 19: Connecting directly to the IPSI on page 505).
Figure 19: Connecting directly to the IPSI
CLK
2 3
cadlipsi KLC 031502
Note:


Issue 2.1 June 2006
505

Note:
Note:

To set the control interface: 1. Type show control interface. Press Enter. 2. To see the current settings, type show port 1. Press Enter.
3. Type set control interface ipaddr netmask, where ipaddr is the customer-provided IP address and netmask is the customer provided subnetmask. Press Enter.
Issue 2.1 June 2006
507


Note:
!
Important:
Resetting the IPSI

To reset the IPSI: 1. Type reset. Press Enter Answer Y to the warning. Note: Resetting the IPSI terminates the administration session. If further administration is required, start a new SSH session to the IPSI. Note: The IP address, subnet mask, and gateway control network settings become effective when you exit the IPADMIN session.
Note:
Note:
2. Disconnect the laptop computer from the faceplate. 3. Check the LCD. Verify that the display shows the letters I and P and a filled-in V that shows at the bottom (Figure 20: LED display that shows that the IPSI has a static IP address). Figure 20: LED display that shows that the IPSI has a static IP address
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502
Issue 2.1 June 2006
509


Note:
! CAUTION:
CAUTION:






Issue 2.1 June 2006
511

Upgrading firmware





Issue 2.1 June 2006
513
Migrating a DEFINITY Server SI Direct-Connect in an MCC to a Direct-Connect

Note:
Use these procedures to migrate from an existing DEFINITY Server SI direct-connect in a multicarrier cabinet (MCC) system to the Avaya S8500 or S8700-Series Media Server with a direct-connect configuration. The existing system uses expansion interface (EI) circuit packs to provide port network connectivity (PNC) for one, two, or three PNs. The existing system must be standard reliability. In all instances you can reuse the cabinets as PNs. However, you can add an EI-connected G650 Media Gateway PN if the existing system has only one or two PNs. To migrate an existing DEFINITY Server SI in an MCC, you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the A carrier in the existing processor port network (PPN) instead of in one of the expansion port networks (EPNs). But before you install the IPSI, you must change the PPN to a PN:

Replace the processor control carrier with an expansion control carrier Remove all the control circuit packs

Install the media server. If Avaya supplies the Ethernet switch(es), and uninterruptible power supplies (UPSs), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8500 Media Servers (555-245-701) or Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). Change the existing processor control cabinet/carrier to an expansion control cabinet/ carrier Replace tone clock circuit pack with IPSI circuit packs Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media server Complete the post-migration administration
Issue 2.1 June 2006
515
Migration paths
DEFINITY Server SI Direct-Connect in an MCC and their releases that can be migrated to the S8500 or S8700-Series Media Server direct-connect configuration include:

DEFINITY Release G3V4 DEFINITY Release G3s/si (with Intel 386) DEFINITY Release 5 through Release 10 MultiVantage Release 11 and Release 1.x Communication Manager Release 2.0 through Release 2.2
Prerequisites

Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
517

Migration paths
Additional tasks
Premigration setup

For more information, see Migration paths on page 516.
Issue 2.1 June 2006
519
To migrate from a DEFINITY system, complete the following additional tasks before you start the migration: Task About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally. Description For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. About 2 business days prior to the migration, contact the STARS team by creating a trouble ticket. Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new authentication file is requested, ASG access (remote and on-site) is impacted. You need assistance from the Service Tools and Application Remote Support (STARS) team to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// gsomissrv2.global.avaya.com/request_system/ request.asp?tools_team=1 Mark the ticket status as CRITICAL. Indicate text in the ticket to notify the STARS team that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. Ensure that the technical support representative has access to the ASG Site Manager tool. If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. 1 of 2
Migration paths
Replace the 982LS current limiter (CURL) Copy the translation file from STS to a directory on the Services laptop.
Replace with CFY1B CURL. File size is usually in the range of 1-4 megabytes.
2 of 2

Issue 2.1 June 2006
521


For a list of documents that Avaya recommends you have on hand for the migration, see Resources on page 54.
Migration tasks
Additional documentation needed. Document Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Installing and Configuring the Avaya S8700-Series Media Server (03-300145) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide providing physical installation and connection information.
Provides installation instructions for the S8700-Series Media Server.
Migration tasks
! CAUTION:
CAUTION:

Turn off the power to the processor gracefully - pre-conversion administration Replace the processor control carrier/cabinet with an expansion control carrier or cabinet
Issue 2.1 June 2006
523
Replace the tone clock circuit pack and Maintenance circuit pack with an IP Server Interface (IPSI) circuit pack and new maintenance circuit pack, respectively Replace old expansion interface circuit packs with new expansion circuit packs, if necessary Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the IPSI circuit pack
You can reuse the translations from the existing system when you migrate to an S8500 or S8700-Series Media Server. Perform the following tasks to convert a processor port network to a port network (MCC). Premigration administration:

Migration tasks:

Accessing the media server maintenance web interface on page 528 Verifying the license file on page 528 Copying translation files to media server on page 528 Restoring translation files on page 529 Administering the IPSIs on page 529 Adding IPSI translations to Communication Manager on page 530 Setting the alarm activation level on page 530 Backing up translations on page 531 Verifying hardware on page 531 Removing the processor port network control carrier on page 531 Installing the expansion control carrier on page 532 Installing IPSI and maintenance circuit packs on page 533 Connecting the CAT5 cables to the IPSI circuit packs on page 535 Installing Expansion Interface circuit packs on page 535 Turning on the media gateway on page 536

This migration affects service because you must turn of the PPN to replace the carrier. Before you turn off the cabinet, you must perform the following premigration administration.
! CAUTION:
CAUTION:
Issue 2.1 June 2006
525




Note:
Saving translations
Note:
This section provides information for migrating translation files from the existing system to the S8500 or the S8700-Series Media Server.
Issue 2.1 June 2006
527





Issue 2.1 June 2006
529
! CAUTION:
CAUTION:


Migration tasks
Migration tasks
Perform these tasks to convert a processor port network to a port network (MCC).
Verifying hardware
Removing the processor port network control carrier

To remove the processor port network control carrier: 1. Label both ends of all the cables being removed from the control carriers. They can be reused.
! CAUTION:
CAUTION:
The system drops all active calls that are processed through this PN when the cabinet is turned off. The trunks and the lines within this cabinet do not operate until the cabinet is turned on and the media server controls the port network.
! CAUTION:
CAUTION:
Do not turn off the survivable remote expansion port networks. If the EPNs are turned off, the system cannot process calls.
Issue 2.1 June 2006
531
Note:
Note: If the system has a power failure transfer (PFT) unit that uses ground start trunks, you must install a temporary ground wire to the PFT units. This action allows the units to operate correctly when the cabinet is turned off. The AUX cable, that usually supplies the ground, will be disconnected. 2. Connect a 10 AWG (#25) (2.6 mm2) wire to pin 49 of the connecting block that is associated with the PFT panel. 3. Route the opposite end of the wire to an approved ground and connect the wire to the ground. 4. Disconnect the power cable on the front of carrier A. 5. Remove all circuit packs from carrier A. 6. Place the circuit packs in antistatic carriers or bags. 7. Remove the power supplies from carrier A. 8. Remove the faceplate from carrier A. 9. Disconnect the cables on the back of carrier A:

TDM/LAN. You can reuse this cable. ICC-A, -B. You must replace this cable. AUX cable. You can reuse this cable. 9-pin D subminiature plug on the right side of cabinet from the P1 connector on the carrier. You can reuse this plug,
10. Remove the current limiter (CURL) from the back of the carrier. You can reuse the CURL. 11. Remove all carrier grounds. 12. Remove carrier A from the cabinet.
Installing the expansion control carrier

To install the expansion control carrier: 1. Install the J58890-AF-2 L13 PN expansion control carrier in position A. 2. Connect the carrier grounds. 3. Install the CFY1B current limiter (CURL) on the back of control carrier A. 4. Connect the following cables to the back of the carriers:
TDM/LAN - Carrier A to D (if equipped) - Carrier A to B - Carrier B to C (if equipped)
Migration tasks
ICC cables from carrier A to B (if required) - No ICC cables are required for systems with simplex reliability
AUX cable to carrier A 9-pin D subminiature plug to the P1 connector on each carrier
5. Install the faceplates on carrier A. 6. Install the power supplies in carrier A.

To install the IPSI and maintenance card circuit packs: 1. Remove the TN2182 Tone Clock circuit pack from the control carrier. Place the circuit pack in an antistatic carrier or bag. Note: Do not remove the TN771 Maintenance/Test circuit pack if this circuit pack is present. 2. Remove the TN775B/C Maintenance (EPN) circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier or bag. 3. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot. 4. With the red line on the bottom, attach one end of the short ribbon cable to the connector on the component side of the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack (Ribbon cable connector on page 533). Figure 21: Ribbon cable connector
Note:
caxxinst LJK 022002
5. Push the tabs on the ends of the connector inward to lock the connector in place.
Issue 2.1 June 2006
533
6. Thread the ribbon through the slot on the front panel (Simplex reliability ribbon cable connection on page 534). 7. Insert the TN775D Maintenance (EPN) circuit pack part way into the MAINTENANCE slot. 8. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D Maintenance (EPN) circuit pack with the red line on the bottom (Simplex reliability ribbon cable connection on page 534). Figure 22: Simplex reliability ribbon cable connection
B
MS AR AL J MA MIN RN W K AC TR ER EM ON
TO F AU OF
CLK
cadsdupx KLC 072502
9. Push the tabs on the ends of the connector inward to lock the connector in place. 10. Thread the ribbon through the slot on the front panel. 11. Fully insert the circuit packs. 12. In the rest of the empty slots, insert Z100C apparatus blanks.
Migration tasks
13. Assign the switch ID and the cabinet ID to the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that you just inserted. For more information, see Assigning IP addresses to the IPSI circuit packs on page 537. Note: For consistency, use the ribbon in the front for connectivity. Do not use ICCC.
Note:

Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) or Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703) and Job Aid, Cabling Guide - MCC1 and SCC1 Media Gateway (555-245-771).
To connect the CAT 5 cables to the IPSI circuit packs:
Connect the green CAT5 cable to the IPSI in the A carrier.

Issue 2.1 June 2006
535

Perform the following tasks to complete postmigration administration.

Note:
Note:
! CAUTION:
CAUTION:
Note:
Note:

Issue 2.1 June 2006
537

CLK
2 3
cadlipsi KLC 031502
Note:



Note:
Note:

Issue 2.1 June 2006
539


Note:
!
Important:
Resetting the IPSI

Note:
Note:
Issue 2.1 June 2006
541
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502


Note:
! CAUTION:
CAUTION:


Issue 2.1 June 2006
543





Upgrading firmware

Issue 2.1 June 2006
545




Migrating a DEFINITY ONE/S8100 to an S8500 Media Server

Use these procedures to migrate from an existing DEFINITY ONE/S8100 in a compact modular cabinet (CMC) system to the Avaya S8500 Media Server with a IP-port network connectivity (PNC) configuration. The existing systems must be standard reliability and direct connect. In all instances, the cabinets can be reused as port networks (PNs). However, you can add a G650 Media Gateway PN if the existing system has one PN. When you migrate an existing DEFINITY ONE/S8100 in a CMC, you use one TN2312BP IPSI circuit pack to control the PN. You also replace the processor circuit pack with the IPSI. This migration affects service.

Install the media server. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8500 Media Servers (555-245-701). Change the existing processor control cabinet/carrier to a port network Replace the tone clock circuit pack with the IPSI circuit pack Connect the media servers to the media gateways Enable control of the IPSIs and control to the media server Complete the post-migration administration
Issue 2.1 June 2006
547
Migration paths
DEFINITY ONE/S8100 and their releases that can be migrated to the S8500 Media Server IP-PNC configuration include:

DEFINITY Release 6 through Release 10 MultiVantage Release 11 and Release 1.x Communication Manager Release 1.0 through Release 1.3
Prerequisites
You must complete the following tasks before you start the migration.

Presite checklist on page 549 - Perform these tasks before you go on site. Premigration setup on page 551 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 553 - Perform these tasks before you go on site. On site migration checklist on page 554 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 554 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
549

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
551
For more information, see Migration paths on page 548. When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally. Description For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. About 2 business days before the migration, create a trouble ticket to contact the STARS team. Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new authentication file is requested, ASG access (remote and on-site) is impacted. You need assistance from the Service Tools and Application Remote Support (STARS) team to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// gsomissrv2.global.avaya.com/request_system/ request.asp?tools_team=1 Mark the ticket status as CRITICAL. Indicate text in the ticket to notify the STARS team that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. Ensure that the technical support representative has access to the ASG Site Manager tool. If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. 1 of 2
Migration paths
2 of 2

Issue 2.1 June 2006
553


Migration tasks
You also need the following Additional documentation: Document Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide that provides physical installation and connection information.
Migration tasks
! CAUTION:
CAUTION:

You can reuse the translations from the existing system when you migrate to an S8500 Media Server. You can reuse the translations from the existing system when you migrate to an S8500 Media Server.
Issue 2.1 June 2006
555
Note:

Connecting to the processor on page 557 Recording node names and IP addresses on page 558 Saving translations on page 558 Recording IP settings on page 558
Migration tasks:

Accessing the media server maintenance web interface on page 559 Verifying the license file on page 560 Copying translation files to media server on page 560 Restoring translation files on page 560 Administering the IPSIs on page 561 Setting the alarm activation level on page 562 Backing up translations on page 562 Verifying hardware on page 563 Changing the control cabinet to a port network on page 563 Turning off the power to the control cabinet on page 564 Replacing the processor circuit pack on page 564 Replacing the TN799C C-LAN circuit pack on page 565 Installing TN771 Maintenance/Test circuit pack on page 565 Connecting to the media server on page 565

Accessing the server command line interface with SSH protocol on page 566 Using static addressing on page 567 Clearing the ARP cache on the laptop computer on page 568 Logging in to the IPSI on page 569 Setting the control interface on page 569 Setting the VLAN and diffserv parameters on page 571 Resetting the IPSI on page 571 Verifying IPSI translations on page 572
Verifying IPSI connectivity on page 573 Verifying the customer data on page 573 Verifying circuit pack locations on page 573 Verifying circuit pack insertion on page 574 Verifying the IP addresses on page 574 Checking the link status on page 574 Upgrading firmware on page 575 Testing the installation on page 575 Busying out previously busied out trunks on page 575 Troubleshooting the migration on page 576 Returning replaced equipment on page 576

To connect to the processor: Note: You need a cross-over cable to connect your Services laptop directly to the processor. 1. Perform one of the following actions to connect the Services laptop directly into the Avaya IP600 processor circuit pack:

Note:
If the processor circuit pack is a TN795, place the NIC card into the slot on the faceplate. If the processor circuit pack is a TN2314, plug the RJ45 connector directly into the RJ45 jack on the faceplate.
2. Start a terminal emulation application or Avaya Site Administration. 3. Log in as lucent3.
Issue 2.1 June 2006
557

Note:
Saving translations
Note:
Recording IP settings
You must view and record the IP settings that are assigned to the processor, and use these same settings for the Avaya S8500 Media Server. You can verify the IP settings against the filled-out Electronic Preinstallation Worksheet. To view these settings, perform the following administration on the Services laptop that is connected to the processor circuit pack by way of telnet. To record the IP settings: 1. Select Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6. Press Enter to access the media server.
3. Log in as lucent3 to get to the LAC prompt. 4. Type bash. Press Enter to start a BASH session. 5. Type setip. Press Enter to display the current list of IP settings. You will see the following information:

cust: IPaddress, subnet mask, gateway dns: server name, domain name, 2 DNS server IP addresses wins: two WINS server IP addresses ras: one remote access server IP address
6. Record this information exactly as displayed.
!
Important:
Important: Include any periods, commas, or other punctuation marks. Record this information in lowercase or uppercase as the information appears.
This section describes how to migrate translation files from the existing system to the S8500 Media Server.

Issue 2.1 June 2006
559




! CAUTION:
CAUTION:

Issue 2.1 June 2006
561

Migration tasks
Note:
Perform the following tasks to convert a processor port network to a port network (CMC).
Migration tasks
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: Customers who currently use the Audix feature on the S8100 must purchase a separate Audix system. The TN795 or the TN2314 Processor circuit pack that contains the Audix feature is replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not contain the Audix feature. You must return the existing processor circuit pack to Avaya. Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Note:
Note:

To change the control cabinet to a port network, you must:
Replace the TN795 or TN2314 Processor circuit pack with a TN2312BP Internal Protocol Server Interface (IPSI) circuit pack. Connect a CAT5 straight-through cable from the IPSI to the media server through the network of the customer. Note: If you replace a TN795 Processor circuit pack, you might not need the TN744D/E Call Classifier-Detector circuit pack. The TN2312BP IPSI circuit pack has call classifier functionality. However, increased voice and data traffic can require the TN744D/E Call Classifier-Detector circuit pack. Note: If you have a TN799C or earlier CLAN circuit pack, you must replace the TN799 circuit pack with a TN799DP CLAN circuit pack.
Note:
Note:
Issue 2.1 June 2006
563

! CAUTION:
CAUTION:
! DANGER:
DANGER:

To replace the processor circuit pack: 1. Remove the entire processor circuit pack and place it in an antistatic carrier or bag. You might need to reinstall this circuit pack if you must stop the migration. 2. Remove the octopus cable from the connector that is associated with slot 2 on the connector panel. 3. Install the IPSI adapter to the connector that is associated with slot 2 on the connector panel. 4. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 5. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 6. Attach the new label above the circuit pack slots.
Note:
Migration tasks



Issue 2.1 June 2006
565
Note:
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:
Note:


Issue 2.1 June 2006
567
CLK
2 3
cadlipsi KLC 031502
Note:



Note:
Note:

Issue 2.1 June 2006
569


Note:
!
Important:
Resetting the IPSI

Note:
Note:
Issue 2.1 June 2006
571
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502





Issue 2.1 June 2006
573



Upgrading firmware



Issue 2.1 June 2006
575


Migrating an Avaya IP600/S8100 to an S8500 Media Server

Use these procedures to migrate from an existing DEFINITY IP600/S8100 switch to the Avaya S8500 Media Server with a IP-port network connectivity (PNC) configuration. The existing switches must be standard reliability and direct connect. In all instances, you can reuse the cabinets as port networks (PNs). However, you can add a G650 Media Gateway port network only if the existing switch has one or two PNs. To migrate an existing Avaya IP600/S8100, you use one TN2312BP IPSI circuit pack to control the PN. You replace the processor circuit pack in the A position in the cabinet with the IPSI. This migration affects service.

Install the media server. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8500 Media Servers (555-245-701). Change the existing processor control cabinet/carrier to a port network Replace the tone clock circuit pack with the IPSI circuit pack Connect the media servers to the media gateways Enable control of the IPSIs and control to the media server Complete the post-migration administration
Issue 2.1 June 2006
577
Migration paths
DEFINITY IP600/S8100 and their releases that can be migrated to the S8500 Media Server IP-PNC configuration include:

DEFINITY Release 9 through Release 10 MultiVantage Release 11 and Release 1.x Communication Manager Release 1.0 through Release 1.3
Prerequisites

Presite checklist on page 579 - Perform these tasks before you go on site. For additional information, see Migration paths on page 578. on page 581 - Perform these tasks before you start the migration from an existing DEFINITY system. Presite migration checklist on page 583 - Perform these tasks before you go on site. On site migration checklist on page 584 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 585 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
579

Migration paths
Additional tasks
Premigration setup

For additional information, see Migration paths on page 578.
Issue 2.1 June 2006
581
When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally. Description For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. About 2 business days before the migration, create a trouble ticket to contact the STARS team. Whenever an S8x00 media server is upgraded from 1.x.x to 2.x.x and a new authentication file is requested, ASG access (remote and on-site) is impacted. You need assistance from the Service Tools and Application Remote Support (STARS) team to ensure successful ASG access before and after the upgrade. To contact the STARS team, use http:// gsomissrv2.global.avaya.com/request_system/ request.asp?tools_team=1 Mark the ticket status as CRITICAL. Indicate text in the ticket to notify the STARS team that you are upgrading an S8x00 media server. Include the date of the upgrade and the FL and product or alarm ID of the system. The STARS team contacts you on how to access your product before and after the upgrade. A temporary ASG product ID is created for you and your team to use for access during the time of the upgrade. Ensure that the technical support representative has access to the ASG Site Manager tool. If an engineer who works on the Avaya WAN, is supporting the technical support representative during the upgrade, ensure that the engineer has access to the ASG Mobile tool prior to the upgrade. ASG access (remote or on site) is affected when you upgrade an S8xxx media server from 1.x.x to 2.x.x and request a new authentication file. 1 of 2
Migration paths
Description This happens at least one day prior to the migration.
2 of 2

Issue 2.1 June 2006
583

When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task The customer supplies an open EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly. Verify that you have the license file that the file includes the licensed features. Verify that you have the Avaya authentication file. Description Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the documentation that comes with the rail kit.
Migration paths
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task Verify the customer supplies an EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly and solidly secured. Verify that you have the license file that the license file includes:
Description Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For information on how to install the rail, see the rail kit documentation.
the right to use (RTU) feature the applicable hardware parts in the existing system any hardware that is being added as part of the migration Use the License File link on the Maintenance Web Interface to verify. Replace with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not have the Audix feature. You also must return the existing Processor circuit pack to Avaya.
Verify that you have the Avaya authentication file. Replace the TN795 or the TN2314 Processor circuit pack that contains the Audix feature.

Issue 2.1 June 2006
585
You also need the following Additional documentation: Document Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) Installing and Configuring the Avaya S8500 Media Server (03-300143) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide that provides physical installation and connection information.
Migration tasks
! CAUTION:
CAUTION:

Note:
Migration tasks
Perform the following tasks to convert a processor port network to a port network (IP600). Premigration administration:

Connecting to the processor on page 588 Recording node names and IP addresses on page 589 Saving translations on page 589 Saving translations on page 589
Migration tasks:

Accessing the media server maintenance web interface on page 590 Verifying the license file on page 590 Copying translation files to media server on page 591 Administering the IPSIs on page 591 Adding IPSI translations to Communication Manager on page 592 Setting the alarm activation level on page 592 Backing up translations on page 592 Verifying hardware on page 593 Changing the IP600 control chassis to a port network on page 593 Turning off the control chassis on page 594 Replacing I/O cables on page 595 Replacing the processor circuit pack on page 597 Replacing the TN799C C-LAN circuit pack on page 598 Installing TN771 Maintenance/Test circuit pack on page 598 Connecting to the media server on page 598

Accessing the server command line interface with SSH protocol on page 599 Using static addressing on page 600 Clearing the ARP cache on the laptop computer on page 601 Logging in to the IPSI on page 602 Setting the control interface on page 602 Setting the VLAN and diffserv parameters on page 604 Resetting the IPSI on page 604 Verifying IPSI translations on page 605 Verifying IPSI connectivity on page 606
Issue 2.1 June 2006
587
Enabling control of the IPSI on page 606 Verifying the customer data on page 606 Verifying circuit pack locations on page 607 Verifying circuit pack insertion on page 607 Verifying the IP addresses on page 607 Checking the link status on page 607 Upgrading firmware on page 608 Testing the installation on page 609 Busying out previously busied out trunks on page 609 Troubleshooting the migration on page 609 Returning replaced equipment on page 609
This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform the following premigration administration.


Note:

Note:
Saving translations
You must save the translations in case you need to stop out of the migration. You might want to print out the translations for reference. To save translations: 1. Type save translation. Press Enter to save translations to the system disk. Either a Command successfully completed message displays or all error messages are logged.
You must view and record the IP settings that are assigned to the processor, and use these same settings for the Avaya S8500 Media Server. You can verify the IP settings against the filled-out Electronic Preinstallation Worksheet. To view these settings, perform the following administration on the Services laptop that is connected to the processor circuit pack by way of telnet. To record the IP settings: 1. Select Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6. Press Enter to access the media server. 3. Log in as lucent3 to get to the LAC prompt. 4. Type bash. Press Enter to start a BASH session.
Issue 2.1 June 2006
589
5. Type setip. Press Enter to display the current list of IP settings. You will see the following information:

6. Record this information exactly as displayed.
!
Important:
Important: Include any periods, commas, or other punctuation marks. Record this information in lowercase or uppercase as the information appears.
This section describes how to migrate translation files from the existing switch to the S8500 Media Server.




! CAUTION:
CAUTION:
Issue 2.1 June 2006
591


Migration tasks
Migration tasks
Perform the following tasks to convert a processor port network to a port network (IP600).
Verifying hardware
Note:
Note: Customers who currently use the Audix feature on the S8100 must purchase a separate Audix system. The TN795 or the TN2314 Processor circuit pack that contains the Audix feature is replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not contain the Audix feature. You must return the existing processor circuit pack to Avaya.
Note:
Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Changing the IP600 control chassis to a port network

To change the Avaya IP600 control chassis to a port network, you must:

Replace the existing straight-wire WP cables, if present, with new twisted pair I/O cables. Replace the processor circuit pack with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack. Connect a CAT5 straight-through cable from the IPSI to the media server through the network of the customer.
Issue 2.1 June 2006
593
Note:
Note: If you replace a TN795 Processor circuit pack, you might not need the TN744D/E Call Classifier-Detector circuit pack. The TN2312BP IPSI circuit pack has call classifier functionality. However, increased voice and data traffic can require the TN744D/E Call Classifier-Detector circuit pack.
Note:
Note: If you have a TN799C or earlier CLAN circuit pack, you must replace the TN799 circuit pack with a TN799DP CLAN circuit pack.
Note:
Turning off the control chassis

To turn off the control chassis:
! CAUTION:
CAUTION:
Ensure that you have completed the premigration administration. For more information, see Premigration administration on page 846. 1. Press and hold the shutdown button on the on the faceplate of the processor until the shutdown process starts. Ensure that you see the green light. This light indicates that the system is shut down.
! DANGER:
DANGER:
The latch on the power supply acts as the DC power switch and removes only DC power from the backplane. To remove the AC power from the chassis, pull the AC power cord from the back of the chassis. 2. To turn off the chassis, unplug the power cord from the back of the chassis.
Migration tasks
Replacing I/O cables

On older MCC, SCC, and G600 cabinets you must replace the existing I/O cables (WP-90753, LI), which connect the backplane to the rear connector panel, with twisted pair I/O cables. The existing I/O cables have straight, not twisted, wires. They may be mostly white with two red, or multi-colored. If the cables have multi-colored, tightly twisted wires, no replacement is necessary. To order the DEFINITY kit with twisted pair I/O cables, use comcode 700234032.
! CAUTION:
CAUTION:
Turn off power to the carrier or media gateway being serviced. Failure to turn off the power can result in electric shock.
! CAUTION:
CAUTION:
When adding or replacing any hardware and associated cables and adapters, be sure to ground yourself against electrostatic discharge (ESD) by wearing a grounded wrist strap. Failure to follow ESD procedures can result in system damage or service disruption.
To replace the existing I/O cables: 1. For the G600 Media Gateway, you must remove the fan assembly to access the cables. Loosen the thumb screws on the fan assembly and pull it straight out as shown in G600 Media Gateway fan assembly removal on page 596. Leave the fan assembly off until all the wires are installed. 2. Note the orientation of the existing 10 cables. The existing I/O cables may be white and red or multicolored. They are not twisted. 3. Remove the nontwisted pair of existing I/O cables from the backplane and the connector panel slots. 4. In their place install the 10 tight-twisted pair I/O cables onto the backplane, according to the proper orientation shown in Proper orientation for the twisted pair I/O cables on page 597. Observe the white outline printed on the backplane for the location of each connector. 5. When viewed from the "wiring" side of the twin connectors (that is, while plugging them into the backplane) and with the connectors oriented properly for plug-in, they should look like Proper orientation for the twisted pair I/O cables on page 597. The circled pin locations are No-Connects; that is, they have no wires in them. At the top there is an orange-black pair on the right and a violet-brown pair on the left. The 50-position metal shell D connectors should be installed into the connector panel with the longer side of the D (pins 125) toward the right when viewed from the rear of the media gateway.
Issue 2.1 June 2006
595
6. For the G600 Media Gateway, replace the fan unit if no other media gateways are to be installed. If you are adding more media gateways to the rack, leave the fan units off until all of the TDM cables are installed. Figure 27: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
Migration tasks
Figure 28: Proper orientation for the twisted pair I/O cables
2 1
iodspair KLC 072602
Figure notes: 1. Top 2. No connects; no wires 3. Violet-brown 4. Orange-black 5. Bottom

To replace the processor circuit pack: 1. Remove the entire processor circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. You want the circuit pack intact if you need to back out of the migration. 3. Remove the octopus cable from the connector that is associated with slot 2 on the backplane. 4. Install the IPSI adapter to the connector that is associated with slot 2 on the backplane. 5. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 6. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 7. Attach the new label above the circuit pack slots.
Note:
Issue 2.1 June 2006
597



Note:
Note:
! CAUTION:
CAUTION:
Issue 2.1 June 2006
599
Note:
Note:


CLK
2 3
cadlipsi KLC 031502
Note:


Issue 2.1 June 2006
601

Note:
Note:

Issue 2.1 June 2006
603


Note:
!
Important:
Resetting the IPSI

Note:
Note:
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502
Issue 2.1 June 2006
605


Note:
! CAUTION:
CAUTION:







Compare the list that you made before the migration. Ensure that the in-service or the out-of-service links match the status of the links before the migration.
Issue 2.1 June 2006
607
To check the link status: 1. Type display communication-interface links. Press Enter. 2. Record all the enabled links. 3. Type status link number where number is a number 1-99. Press Enter. 4. Compare which links are in service with the premigration list. 5. Repeat steps 3 and 4 for all link numbers.
Upgrading firmware





Issue 2.1 June 2006
609
Chapter 6: Migrating to an Avaya S8700-Series Media Server

This chapter describes how to migrate from an existing DEFINITY and Linux system to the Avaya S8700-Series Media Server. The most common migrations are from non-Linux-based systems to Linux-based media servers. Non-Linux-based systems include systems such as the DEFINITY ONE/S8100. Less common migrations include migrations from one Linux-based media server to another. Not all non-Linux-based systems can migrate to a Linux-based media server. Whether you can migrate a system depends on the supported migration path. A migration path refers to the platform and the software release from which you can migrate to the new platform.

Use these procedures to migrate from existing DEFINITY and Linux platforms to the Avaya S8700-Series Media Server configuration with limited time out-of-service. The S8710 or S8720 Media Server can be either a fiber-port network connectivity (PNC) configuration or an IP-PNC configuration or both. Note: Once you complete the migration to fiber-PNC, you can convert to IP-PNC. See Converting PNs to IP-PNC on page 1041.
Note:
You can migrate the following existing systems to an S8700-Series Media Serve. r:

DEFINITY Server R in a multicarrier cabinet (MCC) DEFINITY Server SI in a single carrier cabinet (SCC) or a multicarrier cabinet (MCC) Avaya IP600 (S8100) in a G600 Media Gateway DEFINITY ONE (S8100) in a compact modular cabinet (CMC) DEFINITY Server CSI in a CMC
You can migrate the following existing Linux systems to an S8700-Series Media Server:

S8500 S8700
Issue 2.1 June 2006
611
Migrating to an Avaya S8700-Series Media Server

When you migrate to an S8700-Series Media Server with a fiber-PNC configuration, you can use the existing translations. For a DEFINITY Server R with a magneto optical drive, use the Magneto Optical to S87x0 Translations (MOST) tool to copy the translations to the S8710 Media Server. For a DEFINITY Server R without an optical drive or a DEFINITY Server SI, you must: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation files on a PCMCIA flash card or compact flash card and translation reports before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418. When you migrate from an S8100, the only supported method of moving translations is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files through e-mail to the project manager before the migration. For forms and more information, contact the STS scheduling desk at 720-444-9418.
Migrating hardware
DEFINITY Server R or SI in an MCC

The migration process depends on whether the migration is to an S8700-Series with a CSS/ ATM or direct-connect configuration. S8700 MC: If all the port networks (PNs) are connected through a CSS or ATM, Avaya recommends that you first replace the following components before you start the migration:

Tone clocks with TN2312BP IPSI circuit packs in the processor port network (PPN) Expansion port networks (EPNs)
Migrating hardware
The IPSIs are hot swappable. If all the PNs are direct-connect, Avaya recommends that you install one IPSI in the existing PPN rather than in one of the EPNs. But before you install the IPSI, you must convert the PPN to an EPN. This process requires that you:

Replace the processor control carrier with an EPN. Remove all the control circuit packs.
This migration affects service because you must turn off the PPN to replace the carrier. Before you turn off the cabinet, you must perform some premigration administration.
S8700 IP: When you migrate an existing DEFINITY Server SI direct-connect in an MCC to the S8710 with a direct-connect configuration, you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the A carrier in the existing PPN rather than in one of the EPNs. But before you install the IPSI, you must take the following steps to convert the PPN to a PN. This process requires that you:

This migration affects service because you must turn off the PPN to replace the carrier.

S8700 IP When you migrate an existing DEFINITY Server SI Direct-Connect in an SCC, you use one TN2312BP IPSI circuit pack to control from one to three PNs. Avaya recommends that you install the IPSI in the cabinet in the A position in the existing PPN rather than in one of the EPNs. But before you installing the IPSI, you must convert the PPN to a PN. This process requires that you:

This migration affects service because you must turn off the PPN stack to replace the cabinet.
Issue 2.1 June 2006
613

You can only migrate a DEFINITY Server CSI or a DEFINITY ONE/S8100 in a compact modular cabinet (CMC) to an Avaya S8710 or an S8720 with an IP-PNC configuration. When you migrate an existing DEFINITY Server CSI or a DEFINITY ONE in a CMC, you use one TN2312BP IPSI circuit pack to control the PN. If a CSI, you replace the TN2182 Tone Clock circuit pack with the IPSI which you install in the A position of the cabinet. You also must remove the processor circuit pack. If a DEFINITY ONE, you replace the processor circuit pack with the IPSI. This migration affects service because, if a CSI, you must turn off the CMCs to replace the processor and tone clock circuit packs. Before you turn off the cabinets, you must perform some premigration administration.

You can only migrate an Avaya IP600 to an Avaya S8710 or an S8720 with an IP-PNC configuration. When you migrate an existing Avaya IP600, you use one TN2312BP IPSI circuit pack to control the PN. You replace the processor circuit pack with the IPSI in the cabinet in the A position. This migration affects service becuase you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform some premigration administration.
Prerequisites for migrating to an S8700-Series Media Server


Migration modules
Before you start the software migration and the media server configuration, you must verify that:
The customer has a local area network (LAN) that is set up and running and a network administrator who is available to assist you on the date of the migration. You have the IP addresses and the unique names for the media servers. You have a new license file and a password file. You have the current translations available for download by ProVision. You have the current firmware available. Firmware for the IPSI, the C-LAN, MedPro, and the VAL circuit packs are part of the software CD-ROM. For the latest software and firmware, see the Avaya Support Web site (http://support.avaya.com), click Find Documentation and Downloads by Product Name.
Migration modules
Migrating a DEFINITY Server CSI in a CMC to an S8700-Series Media Server with IP-PNC on page 617 Migrating from a DEFINITY Server SI in an SCC to an S8700-Series Media Server with Fiber-PNC on page 651 Migrating a DEFINITY Server SI in an MCC to an S8700-Series Media Server with Fiber-PNC on page 701 Migrating a DEFINITY Server R to an S8700-Series Media Server on page 741 Migrating a DEFINITY ONE/S8100 to an S8700-Series Media Server with IP-PNC on page 799 Migrating an Avaya IP600/S8100 to an S8700-Series Media Server with IP-PNC on page 833 Migrating an S8500 Media Server to an S8710 Media Server on page 871 Migrating from an S8700 Media Server to an S8710 Media Server on page 889 Migrating from an S8700 or S8710 Media Server to an S8720 Media Server on page 935
Issue 2.1 June 2006
615
Migrating a DEFINITY Server CSI in a CMC to an S8700-Series Media Server with IP-PNC
Note:
Use these procedures to migrate from an existing DEFINITY Server CSI in a Compact Modular Cabinet (CMC) system to the Avaya S8700-Series Media Server with IP-port network connectivity (PNC). You can only migrate a CSI in a CMC to an Avaya S8700-Series IP-PNC configuration. To migrate an existing DEFINITY Server CSI in a CMC, you use one TN2312BP IPSI circuit pack to control the one port network (PN). You must remove the TN2182 Tone Clock circuit pack and install an IPSI circuit pack in the A position. You also must remove the processor circuit pack. This migration affects service.

Install the media servers. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the in the 4-post, 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). Replace the tone clock circuit pack with the IPSI circuit pack Connect the media servers to the media gateways Enable control of the IPSIs and control to the media server Complete the postmigration administration
Issue 2.1 June 2006
617
Migration paths
DEFINITY Server CSI in a CMC and their releases that can be migrated to the S8700-Series Media Server IP-PNC configurations include:

DEFINITY Release 5 through Release 10 MultiVantage Release1.1 Communication Manager Release 2-0 through Release 3.1
To migrate, in most cases, you must reenter all the translations.
Prerequisites

Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
619

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
621
For more information, see Migration paths on page 618. When you migrate from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task Determine which adapters and cables you can reuse. Description You cannot reuse the following items:
The C-LAN 259A adapter. You must use the adapter to the IP Media Processor for 100-Mbps speed. The CAT3 cable that is used with C-LAN. You must use a CAT5 or better cable for 100-Mbps speed.
CAUTION: You must complete the following eight tasks before you freeze translations or save translations to an MO disk that is used to read translations directly into a media server. Be sure to do this step before freezing translations. Verify that existing logins do not start with a number or an asterisk (*). Be sure to do this step before freezing translations. Verify that the functions of the TN577 Packet Gateway and the TN726B Data Line circuit packs (BX.25 links and mode two data modules) were changed to work through the C-LAN circuit packs. Linux does not support logins that start with a number or an asterisk (*). Use Avaya Terminal Emulator or Avaya Site Administration to perform a list logins command.
Note that you cannot reuse the TN577 circuit pack. Use Avaya Terminal Emulator or Avaya Site Administration to perform a list node-names command.
1 of 4
Migration paths
Task Be sure to do this step before freezing translations. Verify that the CMS and INTUITY peripherals and Distributed Communication Service (DCS) links are assigned node names and an Ethernet address. Be sure to do this step before freezing translations. Remove all Mode II Data Modules before you change the S8700-Series Media Server.
Description
The S8700 and the S8710 do not support the following data modules:

System Ports PDMs (7400/8400 Data Modules) PktGateway Pkt Data Dataline Modem Pool System CDR PDMs System Features Printer PDMs
Be sure to do this step before you freeze translations. The TN750 Announcement circuit packs are not supported in the S8700-Series Media Servers.
The announcements translations migrate to the S8700 Series Media Server. However, you must change the circuit pack locations to the TN2501AP Voice Announcement over LAN (VAL) circuit pack. NOTE: All announcement names must be unique on a TN2501AP VAL circuit pack. The announcement names cannot contain any spaces, blanks, or the following characters:

forward slash (/) colon (:) asterisk (*) question mark (?) backward slash (\) angle brackets (<>)
Type change announcements to change any names and port locations. 2 of 4
Issue 2.1 June 2006
623
Task Be sure to do this step before you freeze translations. On the IP Services screen in the Service Type field, remove Alarm1 and Alarm2. Be sure to do this step before you freeze translations. On the Trunk Group screen, change the Measured field from measured to none. Be sure to do this step before you freeze translations. Check the Dial Plan screen (or Dial Plan Analysis Table screen depending on the release) for 0 assigned as attd. Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations. Use a flash card to collect the translations locally.
Description You first might need to change the System Parameters Maintenance screen before you can make any changes to the IP Services screen.
This action indicates that trunk group measurement reports are not required. Remember to remeasure trunk groups. Type list trunk-group to get a list of the trunk groups that are "measured" and need to be changed.
If none, check the Attendant Console screens for any buttons with attd-qcalls or attd-qtime btns. Remove these if 0 is not assigned as attd.
Replace the TN775/B/C circuit packs with TN775D circuit packs in any EPN that controls an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. 3 of 4
Migration paths
Task Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
Description When you finish installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, if you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access requires an ASG challenge and response. This unique craft password remains valid until the password is changed by installing a new authentication file.
4 of 4

Issue 2.1 June 2006
625

Migration paths
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task The customer supplies an open EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly and solidly secured. Verify that cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are labeled and that appropriate connectivity is provided. Verify that you have the license file and that these files include the licensed features. Verify that you have the Avaya authentication file. Description Ensure that you have the screws that come with the rack for installing in square holes or with adapters. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the rail kit documentation.
The cables for TN2312BP Internet Protocol Server Interface (IPSI) circuit packs run from the control hardware rack to the port networks.

For a list of documents that Avaya recommends you have on hand for the migration, see Resources on page 54. Document Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Description A quick reference guide that provides physical installation and connection information.
Issue 2.1 June 2006
627
Document Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Job Aid: Server and CSS Separation - Avaya S8700-Series Media Server (555-245-766)
Description Provides installation instructions for the S8710 and S8720 Media Servers. Provides information on and connectivity diagrams when the S8710 or S8720 Media Servers are in separate locations.
Migration tasks
! CAUTION:
CAUTION:


Connecting to the media server on page 630 Verifying system status on page 631 Recording all busyouts on page 631 Recording node names and IP addresses on page 631 Saving translations on page 632
Migration tasks
Migration tasks:

Accessing the media server on page 632 Checking system status on page 633 Verifying the license file on page 633 Restoring data for a migration (S8710 only) on page 633 Adding IPSI translations to Communication Manager on page 635 Adding IPSI information on page 636 Setting IPSI duplication (high-reliability critical-reliability only) on page 636 Setting the alarm activation level on page 637 Backing up translations on page 637 Verifying hardware on page 638 Changing the IP600 control chassis to a port network on page 638 Turning off the power to the control cabinet on page 638 Replacing the processor circuit pack on page 639 Replacing the TN799C C-LAN circuit pack on page 639 Installing TN771 Maintenance/Test circuit pack on page 640 Connecting to the media server on page 640

Accessing the server command line interface with SSH protocol on page 640 Using static addressing on page 642 Clearing the ARP cache on the laptop computer on page 643 Logging in to the IPSI on page 643 Setting the control interface on page 644 Setting the VLAN and diffserv parameters on page 645 Resetting the IPSI on page 645 Verifying IPSI translations on page 646 Verifying IPSI connectivity on page 647 Enabling control of the IPSI on page 647 Verifying the customer data on page 647 Verifying circuit pack locations on page 648 Verifying circuit pack insertion on page 648 Verifying the IP addresses on page 648
Issue 2.1 June 2006
629
Checking the link status on page 649 Upgrading firmware on page 649 Testing the installation on page 650 Busying out previously busied out trunks on page 650 Troubleshooting the migration on page 650 Returning replaced equipment on page 650
! CAUTION:
CAUTION:




Note:
Issue 2.1 June 2006
631
Saving translations
Note:
This section describes how to migrate translation files from the existing system to the S8700-Series Media Server.
Accessing the media server

To access the media server: 1. Start the Web browser. 2. In the Address field, type 192.11.13.6. Press Enter to open the login Web page. 3. Log in as craft or dadmin. 4. Select yes to suppress alarms. The system displays the Integrated Management Standard Management Solutions Maintenance web page. 5. Click Launch Maintenance Web Interface to go to the Main Menu.



Restoring data for a migration (S8710 only)

You cannot perform this task unless you have:

Received the customer conversion files from the Avaya STS team. Saved the files on your Services laptop computer.
Accessing the media server from your laptop

To access the media server from your laptop: 1. Connect a crossover cable to the Services port on the back of the media server. 2. Start the Web browser. 3. In the Address field, type 192.11.13.6. Press Enter to display the logon Web page. 4. Log in as craft or dadmin. 5. Select yes to suppress alarms. 6. Click Launch Maintenance Web Interface to go to the main menu.
Issue 2.1 June 2006
633

To verify the license file: 1. Under Security, click License File. 2. Verify that the MultiVantage License Mode field is Normal.
Copying the translation files to the media server

To copy translation files to the media server: 1. Under Miscellaneous, click Download Files. 2. Click Browse and select the file that you saved on the Services laptop. 3. Click Download to place the file on the media server.
Restoring the translation files

To restore the translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file might be at the top of the list. 4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file, scroll down and click Review Status to see the results of the restore. When done, the screen shows the message Restore is finished. If the restore process fails, the system displays an error message that states the reason for the failure and the translation file is not restored. Resolve the reason for the failure and restart the process.

To connect to the standby media server: 1. Start a Web browser. 2. Log in as craft or dadmin. 3. Click Launch Maintenance Web Pages. 4. Under Server, click Release Server. 5. Click Release.

To connect to the active media server: 1. Start a Web browser. 2. Log in as craft or dadmin. 3. Click Launch Maintenance Web Interface. 4. Under Server, click Status Summary to verify that the standby media server was refreshed. Do not continue until the standby media server is refreshed. 5. Start a SAT session with Native Configuration Manager or Avaya Site Administration. 6. Login as craft or dadmin.
Installing the translations

To install the translations: 1. Type reset system 4. Press Enter. 2. Return the STS-supplied PCMCIA flash card to Avaya. To add the IPSI translations before you save translations, continue with Backing up translations on page 637.

To add IPSI translations to Communication Manager: 1. Type change system-parameters ipserver-interface. Press Enter. 2. Verify that the Primary Control Subnet Address and Secondary Control Subnet Address (was equipped) fields are correct. The subnet work addresses must match the most significant three octets (the first three groups of digits in the subnet work address) of the Server IP address that appears on the control network entry from the completed Electronic Preinstallation Worksheet (EPW). An asterisk (*) to the right of the Subnet Address field means that although a subnet work address appears, this address is incorrect. Avaya Communication Manager call processing software does not have the subnet information. After you verify the information on the screen, submit this form with or without changes to update Communication Manager with the correct subnet work information.
Issue 2.1 June 2006
635
! CAUTION:
CAUTION:
If the information in either the Primary Control Subnet Address fields, the Secondary Control Subnet Address field, or both, is incorrect, you must change the information on the media servers. Use the Maintenance Web Interface. Under Server Configuration and Upgrades, click Configure Server to change the media server configuration. Then return here to perform Step 3. 3. Verify that the Switch Identifier field is set correctly for this installation. The correct Switch Identifier must be entered here before you administer the TN2312 IPSI circuit packs. 4. Verify that the IPSI Control of Port Networks field is set to disabled. 5. Press Enter to submit the screen. Note: The information that you provide depends on whether the IPSIs get static addresses or the addresses are assigned automatically through DHCP.
Note:
Adding IPSI information

To add IPSI information: 1. Type add ipserver-interface PNnumber where PNnumber is the port network number. Press Enter. 2. When you use static addressing, in the Host field, type in the IP address for the IPSI in the port network that is listed in the Location field. 3. Verify that all the other fields are populated. 4. Press Enter to put the changes into effect. 5. Repeat Steps 1 through 5 for each port network.
Setting IPSI duplication (high-reliability critical-reliability only)

To set IPSI duplication: 1. Type change system-parameters duplication. Press Enter. 2. Set the Enable Operation of IPSI Duplication field to y. 3. Press Enter to put the changes into effect.
Migration tasks

Migration tasks
Perform the following tasks to convert a processor port network to a port network (CMC). Note: If you want to make the system high reliability, you cannot reuse the Compact Modular Cabinets (CMCs). You must install Avaya G650 Media Gateways and move all the circuit packs to the G650s. Note: You must install the new Communication Manager license file on the media server before you make the change or the system will not run.
Note:
Note:
Issue 2.1 June 2006
637
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: The TN798 circuit pack or the TN2402 Processor circuit pack that contains the Audix feature is replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not have the Audix feature. You must return the existing processor circuit pack to Avaya. Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Note:
Note:


Replace the existing straight-wire WP cables, if present, with new twisted-pair I/O cables. Replace the processor circuit pack with a TN2312BP IP Server Interface (IPSI) circuit pack. Connect a CAT5 straight-through cable from the IPSI to the media server through the network of the customer.

! CAUTION:
CAUTION:
Migration tasks
! DANGER:
DANGER:

To replace the processor circuit pack: 1. Remove the entire processor circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. You might need to reinstall this circuit pack if you must stop the migration. 3. Remove the TN2182 Tone Clock circuit pack. 4. Remove the octopus cable from the connector that is associated with slot 2 on the connector panel. 5. Install the IPSI adapter to the connector that is associated with slot 2 on the connector panel. 6. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 7. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 8. Attach the new label above the circuit pack slots.
Note:

Issue 2.1 June 2006
639

If the cabinet does not have a TN2302AP IP Media Processor (CSI did not require it), you must install one in slot 10. For more information, see the Adding New Hardware book, Install and Administer IP Connectivity Hardware section.

Note:
Note:
! CAUTION:
CAUTION:
Note:
Note:
Issue 2.1 June 2006
641


CLK
2 3
cadlipsi KLC 031502
Note:



Note:
Note:
Issue 2.1 June 2006
643



Note:
!
Important:
Resetting the IPSI

Note:
Note:
Issue 2.1 June 2006
645
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502


Note:
! CAUTION:
CAUTION:


Issue 2.1 June 2006
647





Upgrading firmware

Issue 2.1 June 2006
649




Migrating from a DEFINITY Server SI in an SCC to an S8700-Series Media Server with Fiber-PNC
Note:
Use these procedures to migrate from an existing DEFINITY Server SI in an single carrier cabinet (SCC) to the Avaya S8710 or S8720 Media Server with a fiber-port network connectivity (PNC) configuration. But before you install the TN2312BP IPSI circuit pack, you must convert the processor port network (PPN) to an expansion port network (EPN). This process requires that you:

Replace the processor control carrier with an expansion control carrier Remove all the control circuit packs

Install the media server. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the 4-post, 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703). Replace the tone clock circuit pack with the IPSI circuit pack If this system is a high-reliability or a critical-reliability system, replace the second control carrier or cabinet with a port carrier or cabinet if you reuse SCCs Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media server Install the new Communication Manager license file and the authentication file Complete the postmigration administration
Issue 2.1 June 2006
651
Migration paths
Avaya supports the following migrations of a DEFINITY Server SI in an SCC to the S8710 or S8720 Media Server fiber-PNC configurations include:

DEFINITY Release G3V4 DEFINITY Release G3s/si (with Intel 386) DEFINITY Release 5 through Release 10 MultiVantage Release 1.1 and 1.2 Communication Manager Release 1.3 through Release 2.2
When migrating, you can use the existing translations. You must: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation files by e-mail. Included are translation reports and documentation on how to save the them to the Services laptop and restore them to the S8700 Series. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
Prerequisites
This section provides those tasks that must be completed prior to starting the migration. The prerequisites are defined as follows:

Migration paths
Tasks checklists
Presite checklist
:
Description Correct hardware includes: 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 Correct software includes: Windows 2000 or Windows XP operating system Terminal emulation program: HyperTerminal or another TCP/IP networking software bundled with the Windows OS Internet Explorer 5.0 or later For example, obtain logins and passwords for the following components: Media Server Media Gateway SIPI or IPSI circuit pack auxillary equipment Communication Manager These logins and passwords include the logins and the passwords that you might need for the equipment of the customer. 1 of 3
Issue 2.1 June 2006
653
Task Obtain the serial number for the Media Servers, if necessary.
Description You need a new license file and authentication file. You need the serial number from the reference SIPI or IPSI and the SAP order number to generate a new license file. Use this CD-ROM to install the software on the media server and upgrade the firmware. The most recent versions of the service packs are also on this CD-ROM. Check which service packs you need and download files from the Avaya Support Web site (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site (http:// avaya.com/support).
Verify that you have the Communication Manager software distribution CD-ROM with the current software and firmware. Verify that you have the current preupgrade or premigration service packs, if required, on your laptop. Verify that you have the current post-upgrade or post-migration service packs, if required, on your laptop. Verify that you have the current firmware available.

Migration paths
Additional tasks
Issue 2.1 June 2006
655
Premigration setup

For more information, see Migration paths on page 652. When you are migrating from a DEFINITY system, complete the following additional task before you start the migration: Task Determine which adapters and cables you can reuse. Description You cannot reuse the following items:
The 982LS Current Limiter (CURL) for an SI. You must replace with the larger CFY1B CURL. The C-LAN 259A adapter. You must use the adapter for IP Media Processor for 100-Mbps speed. The CAT3 cable that is used with C-LAN. You must use a CAT5 or better cable for 100-Mbps speed.
Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations. Use a spare flash card to collect the translations locally.
Replace the TN775/B/C circuit packs with TN775D circuit packs in any EPN that contains an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. For forms and more information, contact the STS scheduling desk at 720-444-9418. 1 of 2
Migration paths
Description When you finish installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, if you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access requires an ASG challenge and response. This unique craft password remains valid until the password is changed by installing a new authentication file.
2 of 2

Issue 2.1 June 2006
657

Migration paths
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task The customer supplies an open EIA 310D (or equivalent) standard, 4-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly and solidly secured. Verify that the cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are labeled and that appropriate connectivity is provided. Verify that you have the license file from RFA and that the files include the licensed features. Verify that you have the Avaya authentication file from RFA. Verify that you have the required tools on site. For the Magneto Optical Server Tool, see Migrating translations on page 683. Description Ensure that you have the screws that come with the rack (for installing in square holes or with adapters). Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the rail kit documentation.
The cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs run from the control hardware rack to the port networks.
Issue 2.1 June 2006
659

For a list of documents that Avaya recommends you have on hand for the migration, see Resources on page 54. Document Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Job Aid: Server and CSS Separation - Avaya S8700-Series Media Server (555-245-766) Description A quick reference guide that provides physical installation and connection information.
Provides installation instructions for the S8710 and S8720 Media Servers. Provides information on and connectivity diagrams when the S8710 or S8720 Media Servers are in separate locations.
Migration tasks
The information in this section is based on the assumption that the media server complex is installed, configured, and operational. This section describes how to change an existing processor port network (PPN) to a port network (PN) for each type of cabinet.
! CAUTION:
CAUTION:
Migration tasks

Turn off the power to the processor gracefully - pre-conversion administration Replace the processor control carrier/cabinet with an expansion control carrier or cabinet Replace the tone clock circuit pack and Maintenance circuit pack with an IP Server Interface (IPSI) circuit pack and new maintenance circuit pack, respectively Replace old expansion interface circuit packs with new expansion circuit packs, if necessary Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the IPSI circuit pack
Note:
Perform these tasks to convert a processor port network to a port network (SCC). Premigration administration:

Connecting to the processor on page 663 Verifying system status on page 663 Recording all busyouts on page 664 Recording node names and IP addresses on page 664 Saving translations on page 664 Upgrading and administering the existing hardware on page 665 Connecting the media server cables and the IPSI cables to the Ethernet switch on page 665 Upgrading the hardware in each port network on page 666 Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs on page 666 Determining IPSI placement in port networks on page 666 Duplex-reliability configuration on page 667 Setting up a high-reliability or critical-reliability configuration on page 670 Connecting the CAT5 cables to the IPSI circuit packs on page 678 Installing Expansion Interface circuit packs on page 683 Completing circuit pack replacement on page 683
Issue 2.1 June 2006
661
Migration tasks:

Accessing the media server maintenance web interface on page 683 Checking system status on page 684 Verifying the license file on page 684 Restoring data for a migration (S8710 only) on page 684 Adding IPSI translations to Communication Manager on page 686 Setting IPSI duplication (high-reliability critical-reliability only) on page 687 Adding IPSI information on page 688 Setting the alarm activation level on page 688 Backing up translations on page 689 Verifying hardware on page 689 Removing the processor port network control cabinet on page 689 Installing the expansion control media gateway on page 690 Stacking the port media gateways on page 691 Installing IPSI and maintenance circuit packs on page 691 Installing Expansion Interface circuit packs on page 691 Turning on the media gateway on page 692

Accessing the server command line interface with SSH protocol on page 692 Using DHCP addressing on page 694 Administering the location assignment on page 694 Setting the switch ID on page 695 Setting the cabinet number on page 696 Verifying IPSI translations on page 696 Verifying IPSI connectivity on page 697 Enabling control of the IPSI on page 697 Verifying the customer data on page 698 Verifying circuit pack locations on page 698 Verifying circuit pack insertion on page 698 Verifying the IP addresses on page 698 Checking the link status on page 699 Upgrading firmware on page 699
Testing the installation on page 700 Busying out previously busied out trunks on page 700 Troubleshooting the migration on page 700 Returning replaced equipment on page 700
This migration affects service because you must turn off the cabinets to replace the Processor and tone clock circuit packs. Before you turn off the cabinets, you must perform the following premigration administration.
! CAUTION:
CAUTION:


Issue 2.1 June 2006
663


Note:
Saving translations
Note:
Upgrading and administering the existing hardware

This section describes how to upgrade and administer existing PNs to prepare for a migration to the S8710 or S8720 fiber-PNC configuration for single carrier cabinets (SCCs). This process consists of:

Placing the CAT5 cables between the Ethernet switches and the PNs. Changing out expansion interface circuit packs (if necessary). Changing out tone clock and maintenance circuit packs for IP Server Interfaces (IPSI) and new Maintenance circuit packs. Connecting the IPSI circuit packs to the Ethernet switches. Assigning IDs or static IP addresses to the IPSI circuit packs.
You can perform these tasks while the existing system is in service. However, duplex-reliability configurations encounter short service interruptions when the tone clock circuit pack is changed out in IPSI-controlled PNs. Note: If you install IPSIs in the existing PPN, you must move all the new circuit packs to the new carrier or cabinet during the PPN conversion.
Note:
The information in this section is based on the assumption that the S8700-Series Media Servers have the latest software release, and that the media server complex is installed, configured, and operational. This section describes the following tasks:
Connecting the media server cables and the IPSI cables to the Ethernet switch on page 665 Upgrading the hardware in each port network on page 666 Installing Expansion Interface circuit packs on page 683 Post-migration administration on page 692
Connecting the media server cables and the IPSI cables to the Ethernet switch
Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703).
Each TN2312BP IP Server Interface (IPSI) circuit pack must have a CAT5 Ethernet cable that connects back to the Ethernet switch. Cables for IPSIs that are located in PN carrier A are green. Cables for IPSIs that are located in PN carrier B (high or critical reliability) are red.
Issue 2.1 June 2006
665
In duplex configurations, each media server is connected to the Ethernet switch or switches that comprise control network A (CNA) (green cable). In high-reliability and critical-reliability configurations, each media server is connected to the Ethernet switch or switches that comprise control network B (CNB) (red cable).
Upgrading the hardware in each port network

In IPSI-controlled PNs, you must replace the existing tone clock and the maintenance circuit packs with a TN2312BP IPSI circuit pack and TN775D or later Maintenance circuit pack, respectively. You also must replace the TN570 (R) Expansion Interface circuit packs with TN570B, vintage 7, or later circuit packs. This section contains the following information:
Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs on page 666 Assigning IP addresses to the IPSI circuit packs on page 694 Migrating translations on page 683
Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs
Note:
Note: Before you start, read this procedure and Assigning IP addresses to the IPSI circuit packs on page 694. If you use a DHCP server, you can set the switch ID and the cabinet number on the IPSI circuit pack. However, you must complete certain sequences before to a predetermined timeout interval. If you do not set the switch ID and the cabinet number when you first install the circuit pack, it can be done later but it requires that the circuit pack be reseated. This might result in an additional service interruption in a duplex reliability configurations.
Determining IPSI placement in port networks

Use this information to determine in which PNs you must install the IPSI circuit packs. Not all PNs require IPSI circuit packs. PNs that do not contain an IPSI have an Expansion Interface (EI) circuit pack that controls the PN. These EI-controlled PNs are assigned automatically to an IPSI when the system is initialized. The system automatically balances the EI-controlled PNs among the available IPSIs.
Also, with Communication Manager Release 2.0 or later, you can put an IPSI in a DS1-C-remoted PN. To place the IPSI circuit packs correctly, follow these rules:
When you place an IPSI in a DS1-C-remoted port network, make sure that you administer the nonremoted IPSI first and that you set the IP Control field to y. You do not have to set the IPSI in the DS1-C-remoted PN to no. However, if you set to y, customers must run Ethernet from the IPSI and there is limited control (1:2 versus 1:5). Place the reference IPSI in the PN with the shortest Ethernet connection to the media servers. The reference IPSI is the one whose serial number is used in the license file. This placement minimizes the amount of data network that could fail between the IPSI and the media servers and cause the system to switch to No License mode. Use the following formulas to determine the minimum number of PNs that require an IPSI: - Duplex (direct connect): One IPSI controls up to three PNs. If you use one or two PNs and you add a G650 media gateway PN, it may have an IPSI. If you use two IPSIs, the IP control for one IPSI is yes and the other is no. - Duplex (CSS or ATM): Divide the total number of PNs by 5 (if the result is not an integer, round up), and add one. - High- or critical-reliability: Divide the total number of PNs by 5 (if the result is not an integer, round up). For each IPSI-connected PN, you need two IPSIs.
On large configurations that contain multiple switch node carriers, you must place the IPSIs as evenly as possible among the switch nodes. Use the list fiber all command to determine which port networks are connected to which switch node.
Duplex-reliability configuration
!
WARNING:
WARNING: The following procedure affects service when you are switching the circuit packs. Coordinate this activity with the customer to minimize disruption of customer activities.
Note:
Note: You can replace the Maintenance circuit pack with the TN775D Maintenance (EPN) (if necessary) and the TN2182 Tone Clock circuit packs with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs and program these new circuit packs prior to installation. All the circuit packs being replaced are hot-swappable. Therefore, you do not need to turn off the PNs or the carrier.
Issue 2.1 June 2006
667
To set up a duplex configuration: 1. Type status system all and press Enter to determine:

Which PNs contain TN2182 Tone Clock circuit packs Which cabinets contain the Tone Clock circuit packs Which Tone Clock is active Which Tone Clock is standby
2. In cabinets receiving an IPSI circuit pack, remove the TN2182 Tone Clock circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier or bag. Note: If present, do not remove the TN771 Maintenance/Test circuit pack. 3. Remove the TN775B/C Maintenance (EPN) circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier or bag. 4. Insert the TN2312BP IPSI circuit pack part way into the TONE-CLOCK slot. 5. With the red line on the bottom (pin 1), attach one end of the short ribbon cable to the connector on the component side of the TN 2312BP circuit pack (Ribbon cable connector on page 668). Figure 33: Ribbon cable connector
Note:
caxxinst LJK 022002
6. Push the tabs on the ends of the connector inward to lock the connector in place. 7. Thread the ribbon through the slot on the front panel (Duplex-reliability ribbon cable connection on page 669). Standard reliability is referred to as duplex reliability in the S8700 or S8710 configuration because of the two media servers. 8. Insert the TN775D maintenance circuit pack part way into the MAINTENANCE slot. 9. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D circuit pack with the red line on the bottom (Duplex-reliability ribbon cable connection on page 669).
Figure 34: Duplex-reliability ribbon cable connection
B
MS
AR AL J MA MIN RN W K AC EM
TR ER N O
CL
TO F AU OF
cadsdupx KLC 072502
10. Push the tabs on the ends of the connector inward to lock the connector in place. 11. Thread the ribbon through the slot on the front panel. 12. Fully insert the circuit packs. 13. Program the TN2312BP that you just inserted. For more information, see Assigning IP addresses to the IPSI circuit packs on page 694.
Issue 2.1 June 2006
669
Setting up a high-reliability or critical-reliability configuration

Note:
Note: You can replace the tone clocks with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs and administer the IPSI circuit packs ahead of time. The circuit packs are hot-swappable. Therefore, you do not need to turn off the PNs or the carriers.
To set up a high- or critical-reliability configuration: 1. Determine in which PNs you must install the IPSI circuit packs. For more information, see Determining IPSI placement in port networks on page 666. Note: Not every port network requires an IPSI circuit pack. 2. Type status system all. Press Enter to determine:

Note:
Which port networks contain TN2182 Tone Clock circuit packs Which media gateway contain tone clock circuit packs Which is active Which is standby
3. If needed, type set tone-clock cabinet carrier. Press Enter to make the tone clock in the B carrier active. 4. Remove the ground plate and the upper and the lower rear covers from the media gateway. For more information, see Removing ground plate and upper and lower rear covers on page 671.
Figure 35: Removing ground plate and upper and lower rear covers
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
cadscat1 KLC 032602
Figure notes: 1. Media gateway B 2. Media gateway A 3. Upper rear cover 4. Ground plate 5. Lower rear cover
5. If the IPSI circuit packs and the TN775D Maintenance (EPN) circuit packs are not already present, insert these circuit packs part way into their respective slots. The slots are labeled Tone/Clock and Maintenance. If these circuit packs are already present, unseat them and pull them part way out. 6. With the red line on the bottom (pin 1), attach one end of the short ribbon cable to the connector on the component side of the IPSI circuit pack. 7. Push the tabs on the ends of the connector inward to lock the connector in place (Ribbon cable connector on page 672).
Issue 2.1 June 2006
671

cadsinst LJK 030102
8. Thread the ribbon through the slot on the front panel. 9. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D Maintenance (EPN) circuit pack. Make sure the red line is on the bottom. See Figure 37: Duplex ribbon cable connection on page 673.
Figure 37: Duplex ribbon cable connection
B
MS
TR ER N O
CL
TO F AU OF
cadsdupx KLC 072502
10. Push the tabs on the ends of the connector inward to lock the connector in place. 11. Thread the ribbon through the lower slot on the faceplate of the TN775D Maintenance (EPN) circuit pack. 12. For high-reliability or critical-reliability configurations, use the pass-through tool to feed the long ribbon cable through media gateway A (Figure 38: Ribbon cable placement with the pass-through tool on page 674).
Issue 2.1 June 2006
673
Figure 38: Ribbon cable placement with the pass-through tool
CLK
O AUT OFF
cadsrib2 KLC 032602 602
13. Plug the long ribbon cable into the bottom connector on the component side of the TN775D Maintenance (EPN) circuit pack. The red line is on bottom (Figure 39: High-reliability and critical-reliability ribbon cable connection on page 675). 14. Push the tabs on the ends of the connector inward to lock the connector in place. 15. Thread the ribbon cable through the remaining slot on the faceplate of the TN775D Maintenance (EPN) circuit pack. 16. Route the cable through the TDM slot in the back of the SCC1 media gateway A and up to SCC1 media gateway B (Cable routing through the TDM slot on page 676).
Figure 39: High-reliability and critical-reliability ribbon cable connection
B
CLK
A
S RM ALA J MA MIN RN W K AC TR ER EM ON
TO AU OFF
CLK
O AUT OFF
CLK
O AUT OFF
cadsrib3 KLC 072502
Issue 2.1 June 2006
675
Figure 40: Cable routing through the TDM slot
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
3
cadsrib4 KLC 032602
Figure notes: 1. Media gateway B 2. Media gateway A 3. TDM cable slot
17. Use the pass-through tool to feed the long ribbon cable through media gateway B. 18. If not already present, insert an IPSI circuit pack part way into the tone clock slot of media gateway B. 19. Connect the long ribbon cable to the connector on the component side of the IPSI circuit pack in media gateway A. The red line is on bottom (Figure 39: High-reliability and critical-reliability ribbon cable connection on page 675). 20. Fully insert the TN775D Maintenance (EPN) and the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. 21. If you installed both ribbon and CAT5 cables, replace the rear covers and the ground plates (Figure 41: Replacing the rear covers and the ground plates on page 677).
If you must install CAT5 cables, leave the rear covers and the ground plates off. Continue with Connecting the CAT5 cables to the IPSI circuit packs on page 678. Figure 41: Replacing the rear covers and the ground plates
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
cadsrib5 KLC 032602
Figure notes: 1. Media gateway B 2. Media gateway A 3. Ground plate that covers the TDM cable opening. Note: All cables that run between or from exiting media gateways use the opening that is provided for the TDM cables.
Comcode 700219413 Description Cable Pass Through Kit
Issue 2.1 June 2006
677

Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703).
To connect the CAT5 cables to the IPSI circuit packs: 1. If the ground plate is present, remove the ground plate. Remove the upper and the lower rear covers from the media gateway (Figure 42: Removing the ground plate on page 678). Figure 42: Removing the ground plate
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
cadscat1 KLC 032602
Figure notes: 1. Media gateway B 2. Media gateway A 3. Upper rear cover 4. Ground plate 5. Lower rear cover
2. Using a cable pass-through kit, run the 25- or 50-m green CAT5 cable from the Ethernet switch through the media gateway (Figure 43: CAT5 cable in the pass-through kit on page 679). Figure 43: CAT5 cable in the pass-through kit
CLK
O AUT OFF
cadscat2 KLC 032602
!
WARNING:
WARNING: Locate the ferrite as close to the exit of the media gateway as possible.
3. Install the clamp on ferrite on the CAT5 Ethernet cable (Figure 44: CAT5 cable run through the clamp-on ferrite on page 680).
Issue 2.1 June 2006
679
Figure 44: CAT5 cable run through the clamp-on ferrite
KL
FF OT UA
18
11 10
KL
FF OT UA
cadscat4 KLC 032602
Figure notes: 1. Media gateway B 2. Media gateway A 3. Clamp on Ferrite.
!
WARNING:
WARNING: Locate the ferrite as close to the exit of the media gateway as possible.
4. Connect the green CAT5 cable to the bottom connector on the front of the TN2312 IPSI circuit pack in media gateway A (Figure 45: CAT5 cable connected to the IPSI).
Figure 45: CAT5 cable connected to the IPSI
CLK
O AUT OFF
5. Replace the rear covers and the ground plate. Dress the CAT5 Ethernet cable to exit from either the left side or the right side of the media gateway (Figure 46: Replacement of the rear covers and the ground plate on page 682).
Issue 2.1 June 2006
cadscat3 KLC 032602
681
Figure 46: Replacement of the rear covers and the ground plate
KL
FF OT UA
18
1
11 10
KL
FF OT UA
cadscat5 KLC 032602
Figure notes: 1. Ground plate
6. For high-reliability or critical-reliability, repeat Steps 1 through 5 for the IPSI circuit pack in media gateway B. Use a red CAT5 Ethernet cable.

Completing circuit pack replacement

For standard (duplex) reliability configurations, repeat Duplex reliability configuration on page 717 for each port network that receives a TN2312BP. For high-reliability and critical-reliability configurations, repeat High-reliability or critical-reliability configuration on page 720 and Connecting the CAT5 cables to the IPSI circuit packs on page 722 for each port network that receives a TN2312BP.
This section describes how to migrate translation files from the existing system to the new S8700 Series Media Server.

Issue 2.1 June 2006
683




You cannot perform this procedure unless you have:

Received the customer conversion files from the Avaya STS team. Saved the conversion files on your Services laptop computer.

To access the media server from your laptop: 1. Connect a crossover cable to the Services port on the back of the media server. 2. Start the Web browser. 3. In the Address field, type 192.11.13.6. Press Enter to display the logon Web page. 4. Log in as craft or dadmin.
5. Select yes to suppress alarms. 6. Click Launch Maintenance Web Interface to go to the main menu.

Copying the translation files to media server


To restore translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically displays the default directory. 3. Select the first file. The latest file should be at the top of the list. 4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file, then scroll down and click Review Status to see the results of the restore. When done, the screen displays the message Restore is finished. If the restore process fails, the system displays an error message that states the reason for the failure and the translation file is not restored. Resolve the reason for the failure and restart the process.
Issue 2.1 June 2006
685


To connect to the active media server, perform the following steps: 1. Start a Web browser. 2. Log in as craft or dadmin. 3. Click Launch Maintenance Web Interface. 4. Under Server, click Status Summary to verify that the standby media server was refreshed. Do not continue until the standby media server is refreshed. 5. Open a SAT session with Native Configuration Manager or Avaya Site Administration. 6. Login as craft or dadmin.

To install the translations: 1. Type reset system 4. Press Enter. 2. Return the STS-supplied PCMCIA flash card to Avaya. To add the IPSI translations before you save the translations, continue with Adding IPSI translations to Communication Manager on page 686.

To add IPSI translations to Communication Manager: 1. Type change system-parameters ipserver-interface. Press Enter.
2. Verify that the Primary Control Subnet Address and Secondary Control Subnet Address (was equipped) fields are correct. The subnet work addresses must match the most significant three octets (the first three groups of digits in the subnet work address) of the Server IP address that appears on the control network entry from the completed Electronic Preinstallation Worksheet (EPW). An asterisk (*) to the right of the Subnet Address field means that although a subnet work address appears, this address is incorrect. Avaya Communication Manager call processing software does not have the subnet information. After you verify the information on the screen, submit this form with or without changes to update Communication Manager with the correct subnet work information.
! CAUTION:
CAUTION:
Note:

Issue 2.1 June 2006
687

To add IPSI information: 1. Type add ipserver-interface PNnumber where PNnumber is the port network number. Press Enter. 2. When you use a DHCP server, verify that the fields that are associated with the primary IPSI and secondary IPSI (if equipped) are populated with default data. The DHCP server sets the Host and the DHCP ID fields. 3. Verify the correct setting for the IP Control field:

If IPSIs are in IP-connected PNs, set the IP Control field to y. If IPSIs are in fiber-connected PNs (CSS or ATM), set the IP Control field to y. If IPSIs are in fiber-connected PNs (direct-connect), set the IP Control field to y unless more than one IPSI is present. If more than one IPSI is present, set the IP Control field for the second IPSI to n. If an IPSI is in a DS1-Cremoted PN, set the IP Control field to n to maintain the 5:1 ratio of IPSIs to PNs. If the field is set to y, the system decreases the ratio to 2:1.
4. Verify that all the other fields are populated. 5. Press Enter to put the changes into effect. 6. Repeat Steps 1 through 5 for each port network.

Migration tasks
Migration tasks
Perform the following tasks to convert a processor port network to a port network (SCC).
Verifying hardware
Removing the processor port network control cabinet

To remove the processor port network control cabinet: 1. Label both ends of all the cables that you will remove from all the cabinets. You will reuse these cables.
Issue 2.1 June 2006
689
! CAUTION:
CAUTION:
All active calls that are processed through this PN are dropped when the cabinet stack is turned off. All trunks and lines within this cabinet stack are out of service until the cabinet stack is turned on and the media server controls the PN. Note: If the system is equipped with power failure transfer (PFT) units that use ground start trunks, you must install a temporary ground wire to the PFT units. This ground wire allows units to operate correctly when the cabinet is turned off. The AUX cable that usually supplies the ground is disconnected. 2. Connect a 10 AWG (#25) (2.6 mm2) wire to pin 49 of the connecting block or to pin 49 of the cable access panel (CAP) on the power-failure transfer panel. 3. Route the opposite end of the wire to an approved ground and connect. Note: You can cut over and have the media server control the other PNs at this time. Only cutover at this time if you are not installing IPSI(s) in the PPN or the customer wants to minimize out-of-service time. To cutover, go to Enabling control of the IPSI on page 697. 4. Turn off the cabinets in the SCC1 stack. 5. Remove all circuit packs from the cabinets and place the circuit packs in an antistatic carrier or bag. 6. Disconnect the cables on the front of the cabinets. 7. Disconnect the following cables on the back of the cabinets.

Note:
Note:
CURL - you cannot reuse this cable. TDM/LAN - you can reuse this cable. ICC-A, ICC-B - you can reuse this cable.
8. Remove all cabinet grounds. 9. Remove the top cabinet. 10. Remove the subsequent cabinets, including control cabinet A and control cabinet B if this system is a high-reliability or critical-reliability system.
Installing the expansion control media gateway

To install the expansion control media gateway: 1. Install the J58890N expansion control media gateway. 2. Connect the media gateway grounds and power.
Migration tasks
Stacking the port media gateways

To stack the port media gateways: 1. If needed, stack a port media gateway (J58890H) on top of the expansion control media gateway. 2. If needed, stack a third and a fourth port media gateway on top of the first port media gateway. 3. Install the new CFY1B CURL unit on the back of control cabinet A. 4. Connect the following cables to the back of all the media gateways:

TDM/LAN ICC-A, ICC-B

If this PN does not contain an IPSI, install the tone clock and the maintenance circuit packs, as required. Then continue with Installing Expansion Interface circuit packs on page 785. If this PN contains one or two IPSIs, reinstall the IPSIs and the ribbon cables as you did before. For the procedures, see Duplex reliability configuration on page 779 and High-reliability or critical-reliability configuration on page 782.

Note:
Note: If the existing PPN has a TN776 or TN570 Expansion Interface circuit pack(s), you must replace them with a TN570B Expansion Interface, vintage 7, or higher circuit pack. If this system is to be used with an Enterprise Survivable Server (ESS), replace the TN776 or TN570 Expansion Interface circuit packs with a TN570D Expansion Interface or later circuit pack.
To install the Expansion Interface circuit packs: 1. Remove the existing circuit pack and place in an antistatic carrier or bag. 2. Insert the TN570C or higher EI circuit packs into the EXPN INTFC slots (A01, B02).
Issue 2.1 June 2006
691
If you want to reuse the EI circuit pack in a G650 Media Gateway: a. Move the EI/ATM Interface circuit pack from location C02 to location A01. b. If this system is a critical-reliability system, move EI/ATM Interface circuit pack from location D02 to location B02.
If you do not want to reuse the EI circuit pack in a CSS, continue with Step 4.
4. If you are using ATM EIs: a. Use a cable pass-through kit to run the fiber optic cables for the expansion interface circuit packs through the media gateway. b. Connect the fiber optic cables to the connector on the front of the expansion interface circuit packs. The LED lights when the cables are connected correctly.

Note:
To use this procedure with a laptop cable connection to the services port, you must configure your laptop for the network connection. See Network configuration on page 1242. In addition, a third-party SSH client must already be installed on your computer.
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: 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.
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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
Note:
Note:
Issue 2.1 June 2006
693
will have a different key. You get a prompt in this case because it appears that the host key has changed. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.

The IP server interface circuit packs receives IP addresses when you use the dynamic host configuration protocol (DHCP).
Using DHCP addressing

So that the TN2312BP IPSI circuit packs can receive IP addresses dynamically, you must assign the switch ID and the cabinet number to each IPSI circuit pack. The switch ID is A through J. The cabinet number is 01 through 64. For G650 Media Gateways, a cabinet is defined as one or more media gateways connected by TDM cable. This cabinet configuration is called a G650 rack mount stack.
Administering the location assignment

To administer the location assignment: 1. Fully insert the TN2312BP IPSI circuit pack. If necessary, reseat the circuit pack to start the programming sequence. Note: You must start the following steps within 5 seconds after you insert the circuit pack. Note: For the following step, do not use a graphite pencil.
Note:
Note:
2. Insert the point of a ballpoint pen, golf tee, or a similar object into the recessed push button switch.
CLK
S E R V
Note:
Note: If you pass up the letter or the number that you want, you can either (1) cycle through all the letters or numbers to get to the one you want, or (2) reinsert, or eseat, the circuit pack and start again.
Setting the switch ID

If you have only one system, the default switch ID is A. The second system is B, and so on. The switch ID is not the letter that designates the media gateway or the carrier. To set the switch ID: 1. While the display characters are flashing, press the button until the switch ID, A through J, shows on the top character of the LED display. When the correct letter shows, stop. The letter flashes a few times and then stops. The next character down starts to flash.
fpdlled3 LJK 022502
Issue 2.1 June 2006
695
Setting the cabinet number

Make sure that you program the cabinet number and not the port network number. If you have more than one IPSI in a cabinet, all IPSIs have the same cabinet number. To set the cabinet numbers: 1. While the first digit of the number is flashing, press the button until the correct tens digit, 0 through 6, shows on the display. When the correct digit shows, stop. The digit flashes a few times and then stops. The second digit starts to flash. 2. While the second digit is flashing, press the button until the correct units digit, 0 through 9, shows on the display. When the correct digit shows, stop. The digit flashes a few times and then stops. 3. All segments of the display go dark for one second. Then the Switch ID and media gateway stack number are shown in the top three characters of the LED display. The letter "V" is shown in the fourth or bottom character. When the DHCP server assigns an address to the IPSI, the center of the "V" fills in. The filled-in "V" looks like the bottom half of a diamond.
CLK
fpdlled2 LAO 112905
S E R V
For a duplicated control network, repeat these Steps 1 through 3 for the second IPSI in the cabinet.

To verify IPSI translations: 1. Type list ipserver-interface. Press Enter.
fpdlled1 LJK 022502
2. Verify that the ISPI circuit pack(s) are translated. The State of Health - C P E G column shows 0.0.0.0 for each healthy IPSI. If a "1" shows in any position, you must troubleshoot the problem. Tip:
Tip:


Note:
! CAUTION:
CAUTION:
Issue 2.1 June 2006
697



To verify circuit pack locations: 1. To view all the cabinets, type list cabinet. Press Enter. Verify that the screen shows the cabinet number that is a assigned to the converted cabinets. 2. Type display cabinet number, where number is the cabinet number of the converted cabinet. Press Enter. Under Carrier Description, Carrier Type verify that the number of carriers that are in use matches the number of media gateways in the stack (SCC).



Upgrading firmware

Issue 2.1 June 2006
699




Changing port networks to IP-PNC

Use these procedures to migrate fiber-PNC to fiber-PNC. To change one or more port networks to IP-PNC, see Conversions.
Migrating a DEFINITY Server SI in an MCC to an S8700-Series Media Server with Fiber-PNC

Note:
Use these procedures to migrate from an existing DEFINITY Server SI in an MCC to the Avaya S8700-Series Media Server with a fiber-port network connectivity (PNC) configuration. Before you install the TN2312BP IPSI circuit pack, you must convert the processor port network (PPN) to an expansion port network (EPN). This process requires that you:


Note:
Note: When this migration is complete, the terms EPN and port network (PN) can be used synonymously.
When migrating from DEFINITY platforms:
Install the media servers and, if Avaya supplied, the Ethernet switch(es) and uninterruptible power supply (UPSs) in the 4-post, 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Replace the tone clock circuit pack with the IPSI circuit pack If high or critical reliability, replace the second control carrier/cabinet with a port carrier/ cabinet when reusing MCCs Connect the media servers to the media gateways Enable control of the IPSIs, switching control to the media servers Install the new Communication Manager license file and the Avaya authentication file Complete the post-migration administration
Issue 2.1 June 2006
701
Migration paths
DEFINITY Server SI in an MCC and their releases that can be migrated to the S8700-Series Media Server fiber-PNC configurations include:

DEFINITY Release G3V4 DEFINITY Release G3s/si (w/Intel 386) DEFINITY Release 5 through Release 10 MultiVantage Release 1.1 and 1.2 Communication Manager Release 1.3 through Release 2.2
When migrating, you can use the existing translations. You must: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation files by e-mail. Included are translation reports and documentation on how to save the them to the Services laptop and restore them to the S8700 Series. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
Prerequisites
This section provides those tasks that must be completed prior to starting the migration. The prerequisites are defined as follows:

Prerequisites on page 702 - these are tasks that must be performed before going on site. Additional tasks on page 705 - these are tasks that must be performed on site before starting the migration from an existing DEFINITY system. Presite migration checklist on page 707 - these are tasks that must be completed before going on site. On site migration checklist on page 708 - these are tasks that must be performed on site before starting the migration. Migration tasks on page 710 - these are the documents Avaya recommends that you have on hand for the migration.
Migration paths
Tasks checklists
:
Issue 2.1 June 2006
703

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
705
For more information, see Migration paths on page 702. When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task Find out which adapters and cables are reusable. Description The following items are not reusable:
982LS Current Limiter (CURL) for an SI. You must replace with larger CFY1B CURL. C-LAN 259A adapter. You must use adapter for IP Media Processor for 100 Mbps speed. CAT3 cable used with C-LAN. You must use CAT5 or better for 100 Mbps speed.
Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations.
Replace with TN775D circuit packs in any EPNs that have an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS then updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. Verify that a copy of the existing translations exists so they can be reentered later.
Collect the translations locally by a spare flash card.
Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
When you have finished installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, provided you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access still requires an ASG challenge/response. This unique craft password remains valid until it is changed by installing a new authentication file.
Files usually are in the 1-4 megabytes range.
Migration paths

Before you go on site, complete the following tasks: Task Verify the voice network, dial plan, and E911 for remote locations were redesigned. Verify that all existing circuit packs work with the new system. Replace any TN799B/C C-LAN circuit packs. Replace 259A adapter and CAT3 cable. Replace the TN776 and TN570 EI circuit packs. Description (if applicable)
Check the Minimum Vintage Table. Go to the Hardware and Software Compatibility Matrix (ftp// ftp.avaya.com/incoming/Up1cku9/tsoweb/media/ minhardwarevintages.pdf). Replace with the TN799DP circuit pack. Replace with the cable extender adapter (Comcode 848525887) and CAT5 or better cable. Replace with TN570B, vintage 7 or later circuit packs.
Before you go on site, complete the following additional tasks: Task Replace the TN570 EI circuit packs. Description If coincidentally installing an ESS server, replace with TN570D or later circuit pack.
Issue 2.1 June 2006
707

When you are on site for a migration from a DEFINITY system, complete the following additional tasks before starting the migration:
Migration paths
Task Verify that the open, customer-supplied, EIA 310D (or equivalent) standard, 19-inch (48-centimeter), equipment rack is properly installed and solidly secured. Verify that cable for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs is labeled and that appropriate connectivity is provided. Verify that you have the license file that it includes the licensed features. Verify that you have the Avaya authentication file.
Description Ensure that the screws that come with the rack are there (for installing in square holes or with adapters). Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on installing the rail, see the documentation that comes with the rail kit. The TN2312BP Internet Protocol Server Interface (IPSI) circuit packs runs from the control hardware rack to the port networks.
Issue 2.1 June 2006
709

Migration tasks
Perform these tasks to convert a processor port network to a port network. Premigration administration:

Connecting to the processor on page 712 Verifying system status on page 713 Recording all busyouts on page 713 Recording node names and IP addresses on page 713 Saving translations on page 714 Upgrading and administering the existing hardware on page 714 Connecting the media server cables and the IPSI cables to the Ethernet switch on page 715
Migration tasks
Upgrading the hardware in each port network on page 715 Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs on page 716 Determining IPSI placement in port networks on page 716 Duplex reliability configuration on page 717 High-reliability or critical-reliability configuration on page 720 Connecting the CAT5 cables to the IPSI circuit packs on page 722 Installing Expansion Interface circuit packs on page 723 Completing circuit pack replacement on page 723
Migration tasks:

Accessing the media server maintenance web interface on page 724 Checking system status on page 724 Verifying the license file on page 724 Restoring data for a migration on page 725 Adding IPSI translations to Communication Manager on page 727 Setting IPSI duplication (high-reliability critical-reliability only) on page 727 Adding IPSI information on page 727 Setting the alarm activation level on page 728 Backing up translations on page 728 Verifying hardware on page 729 Removing the processor port network control carrier on page 729 Installing the expansion control carrier and the port carrier on page 730 Installing IPSI and maintenance circuit packs on page 731 Connecting the CAT5 cables to the IPSI circuit packs on page 731 Installing Expansion Interface circuit packs on page 731 Turning on the media gateway on page 732

Accessing the server command line interface with SSH protocol on page 732 Using DHCP addressing on page 734 Administering the location assignment on page 734 Setting the switch ID on page 735 Setting the cabinet number on page 736
Issue 2.1 June 2006
711
Verifying IPSI translations on page 736 Verifying IPSI connectivity on page 737 Enabling control of the IPSI on page 737 Verifying the customer data on page 738 Verifying circuit pack locations on page 738 Verifying circuit pack insertion on page 738 Verifying the IP addresses on page 738 Checking the link status on page 739 Upgrading firmware on page 739 Testing the installation on page 740 Busying out previously busied out trunks on page 740 Troubleshooting the migration on page 740 Returning replaced equipment on page 740
This migration affects service because you must turn off the PPN to replace the carrier. Before you turn off the cabinet, you must perform the following premigration administration.
! CAUTION:
CAUTION:

To connect to the processor, perform the following steps: 1. Use the computer used to access the cabinet. 2. Start a SAT session with Avaya Site Administration. 3. Log in as craft.



Note:
Issue 2.1 June 2006
713
Saving translations
Note:

This section describes how to upgrade and administer existing PNs to prepare for a migration to the S8710 or S8720 fiber-PNC configuration for multi carrier cabinets (MCCs). This process consists of:

Placing the CAT5 cables between the Ethernet switches and the PNs Changing out expansion interface circuit packs (if necessary) Changing out tone clock and maintenance circuit packs for IP Server Interfaces (IPSI) and new maintenance circuit packs Connecting the IPSI circuit packs to the Ethernet switches. Assigning IDs or static IP addresses to the IPSI circuit packs.
Note:
The information in this section is based on the assumption that the S8700-Series Media Servers have the latest software release, and that the media server complex is installed, configured, and operational. This section covers the following tasks:

Upgrading the hardware in each port network on page 715 Completing circuit pack replacement on page 723 Post-migration tasks on page 732
Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703).
Each TN2312BP IP Server Interface (IPSI) circuit pack must have a CAT5 Ethernet cable that connects back to the Ethernet switch. Cables for IPSIs that are located in PN carrier A are green. Cables for IPSIs that are located in PN carrier B (high or critical reliability) are red. In duplex configurations, each media server is connected to the Ethernet switch or switches that comprise control network A (CNA) (green cable). In high-reliability and critical-reliability configurations, each media server is connected to the Ethernet switch or switches that comprise control network B (CNB) (red cable).

In IPSI-controlled PNs, you must replace the existing tone clock and the maintenance circuit packs with a TN2312BP IPSI circuit pack and TN775D or later Maintenance circuit pack, respectively. You also must replace the TN570 (R) Expansion Interface circuit packs with TN570B vintage 7 or later circuit packs.

Duplex reliability configuration on page 717 Using DHCP addressing on page 734 Completing circuit pack replacement on page 723
Issue 2.1 June 2006
715
Replacing tone clocks with IPSI circuit packs and replacing maintenance circuit packs
Note:
Note: Before you start, read this procedure and Assigning IP addresses to the IPSI circuit packs on page 734. If you use a DHCP server, you can set the switch ID and the cabinet number on the IPSI circuit pack. However, you must complete certain sequences before to a predetermined timeout interval. If you do not set the switch ID and the cabinet number when you first install the circuit pack it can be done later but it requires that the circuit pack be reseated. This might result in an additional service interruption in a duplex reliability configurations.

Use this information to determine in which PNs you must install the IPSI circuit packs. Not all PNs require IPSI circuit packs. PNs that do not contain an IPSI have an Expansion Interface (EI) circuit pack that controls the PN. These EI-controlled PNs are assigned automatically to an IPSI when the system is initialized. The system automatically balances the EI-controlled PNs among the available IPSIs. Also, with Communication Manager Release 2.0 or later, you can put an IPSI in a DS1-C-remoted PN. To place the IPSI circuit packs correctly, follow these rules:
When you place an IPSI in a DS1-C-remoted port network, make sure that you administer the nonremoted IPSI first and that you set the IP Control field to y. You do not have to set the IPSI in the DS1-C-remoted PN to no. However, if set to y, customers must run Ethernet from the IPSI and there is limited control (1:2 versus 1:5). Place the reference IPSI in the PN with the shortest Ethernet connection to the media servers. The reference IPSI is the one whose serial number is used in the license file. This placement minimizes the amount of data network that could fail between the IPSI and the media servers and cause the system to switch to No License mode. Use the following formulas to determine the minimum number of PNs that require an IPSI: - Duplex (direct connect): One IPSI controls up to three PNs. If you use one or two PNs and you add a G650 media gateway PN, it may have an IPSI. If you use two IPSIs, the IP control for one IPSI is yes and the other is no. - Duplex (CSS or ATM): Divide the total number of PNs by 5 (if the result is not an integer, round up), and add one.
- High- or critical-reliability: Divide the total number of PNs by 5 (if the result is not an integer, round up). For each IPSI-connected PN, you need two IPSIs.
Duplex reliability configuration

To set up a duplex configuration:
!
WARNING:
WARNING: The following procedure affects service when the circuit packs are being switched out. Coordinate this activity with the customer to minimize disruption of customer activities.
Note:
Note: You can replace the maintenance circuit pack with the TN775D Maintenance (EPN) (if necessary) and the TN2182 Tone Clock circuit packs with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs and program them ahead of time. All the circuit packs being replaced are hot-swappable. Hot-swappable means you do not need to turn off the PNs or the carrier. 1. Type status system all and press Enter to determine:

Which PNs have TN2182 Tone Clock circuit packs Which cabinets they are in Which is active Which is standby
2. In cabinets receiving an IPSI circuit pack, remove the TN2182 Tone Clock circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier. Note: If present, do not remove the TN771 Maintenance/Test circuit pack. 3. Remove the TN775B/C Maintenance (EPN) circuit pack from the expansion control carrier. Place the circuit pack in an antistatic carrier. 4. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot. 5. With the red line on the bottom (pin 1), attach one end of the short ribbon cable to the connector on the component side of the TN 2312BP circuit pack. See Ribbon cable connector on page 718.
Note:
Issue 2.1 June 2006
717
caxxinst LJK 022002
6. Push the tabs on the ends of the connector inward to lock the connector in place. 7. Thread the ribbon through the slot on the front panel. See Duplex reliability ribbon cable connection on page 719. (Duplex reliability in the S8700 Series configuration consists of the two media servers.) 8. Insert the TN775D Maintenance circuit pack part way into the MAINTENANCE slot. 9. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D circuit pack. The red line is on the bottom. See Duplex reliability ribbon cable connection on page 719.
Figure 48: Duplex reliability ribbon cable connection
B
MS
TR ER N O
CL
TO F AU OF
cadsdupx KLC 072502
10. Push the tabs on the ends of the connector inward to lock the connector in place. 11. Thread the ribbon through the slot on the front panel. 12. Fully insert the circuit packs. 13. Program the TN2312BP just inserted. See Assigning IP addresses to the IPSI circuit packs on page 734.
Issue 2.1 June 2006
719
High-reliability or critical-reliability configuration

To set up a high- or critical-reliability configuration: Note: You can replace the maintenance circuit pack with the TN775D Maintenance (EPN) (if necessary) and the TN2182 Tone Clock circuit packs. Replace these circuit packs with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs and program them ahead of time. All the circuit packs being replaced are hot-swappable. Hot-swappable means you do not need to turn off the PNs or the carrier.
Note:
These procedures assume that the tone clock and maintenance circuit packs are in the A and B carriers. If one of them is in the E or D rather than B carrier, the ribbon cable is not necessary. 1. Determine which PNs get the IPSI circuit packs. For more information, see Duplex reliability configuration on page 717. Note: Not all port networks require an IPSI circuit pack. 2. Type status system all and press Enter to determine:

Note:
Which PNs have TN2182 Tone Clock circuit packs Which media gateway they are in Which is active Which is standby
3. If needed, type set tone-clock cabinet carrier and press Enter where cabinet is 1-64 and carrier is A-E to make the tone clock in the B carrier active. 4. Remove the TN2182 Tone Clock circuit pack from the standby carrier (A). Place the circuit pack in an antistatic carrier or bag. Note: If present, do not remove the TN771 Maintenance/Test circuit pack. 5. Remove the TN775B/C Maintenance/Test circuit pack from standby carrier (A). Place the circuit pack in an antistatic carrier. 6. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot on the standby carrier (A). 7. Attach one end of the short ribbon cable to the connector on the component side of the circuit pack. The red line must be on the bottom (pin 1). 8. Push the tabs on the ends of the connector inward to lock the connector in place. See Ribbon cable connector on page 718. 9. Thread the ribbon through the slot on the front panel.
Note:
10. Insert the TN775D Maintenance (EPN) circuit pack part way into the MAINTENANCE slot in carrier A. 11. Attach the other end of the short ribbon cable to the top connector on the component side of the circuit pack. The red line is on the bottom. See Duplex reliability ribbon cable connection on page 719. 12. Push the tabs on the ends of the connector inward to lock the connector in place. 13. Thread the ribbon through the slot on the front panel. 14. Fully insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack only. 15. Assign the Switch and Cabinet ID to the TN2312BP Internet Protocol Server Interface (IPSI) just inserted. For more information, see Assigning IP addresses to the IPSI circuit packs on page 734. 16. Type set tone-clock cabinet carrier. Press Enter to force a tone clock interchange. 17. Type status port-network number. where number is the number of the port network. Press Enter to verify the service state of the tone clock. Verify that the yellow LED on the IPSI circuit pack is flashing. 18. Remove the TN2182 Tone Clock circuit pack from the new standby carrier (B). Place the circuit pack in an antistatic carrier. 19. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot on the standby carrier (B). 20. Attach one end of the long ribbon cable to the connector on the component side of the circuit pack. The red line must be on the bottom (pin 1). 21. Push the tabs on the ends of the connector inward to lock the connector in place. See Ribbon cable connector on page 718. 22. Thread the ribbon through the slot on the front panel. 23. Attach the other end of the long ribbon cable to the bottom connector on the component side of the TN775D Maintenance (EPN) circuit pack (red line on the bottom). See High-reliability and critical reliability ribbon cable connection on page 722. 24. Fully insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack. 25. Program the TN2312BP Internet Protocol Server Interface (IPSI) that you just inserted. For more information, see Assigning IP addresses to the IPSI circuit packs on page 734. 26. Fully insert the TN775D Maintenance (EPN) circuit pack after you program both IPSIs are programmed.
Issue 2.1 June 2006
721
Figure 49: High-reliability and critical reliability ribbon cable connection
CL
B
MS
TR ER N O
CL
TO F AU OF
cadshic KLC 072502

Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Servers (555-245-703).
To connect the CAT 5 cables to the IPSI circuit packs: 1. Connect the green CAT5 cable to the IPSI in the A carrier or cabinet in the A position. 2. If high-reliability or critical-reliability, connect the red CAT5 cables to the IPSIs in the B carrier or cabinet in the B position.


For standard (duplex) reliability configurations, repeat Duplex reliability configuration on page 717 for each port network that receives a TN2312BP. For high-reliability and critical-reliability configurations, repeat High-reliability or critical-reliability configuration on page 720 and Connecting the CAT5 cables to the IPSI circuit packs on page 722 for each port network that receives a TN2312BP.
This section provides information for migrating translation files from the existing system to the new S8700 Series Media Server.
Issue 2.1 June 2006
723




Restoring data for a migration

The following procedure assumes the technician has already saved the customers conversion files of the customer on the laptop of the technical support representative. These conversion files were sent from the Avaya STS team.

To access the media server from your laptop: 1. Connect a crossover cable to the Services port on the back of the media server. 2. Start the Web browser. 3. In the Address field, type 192.11.13.6. Press Enter to bring up the logon Web page. 4. Log in as craft or dadmin. 5. When asked Do you want to suppress alarms?, select yes. 6. Click Launch Maintenance Web Interface to get to the Main Menu.
Verifying license file

To verify the license file: 1. Under Security, click License File. 2. Verify that the MultiVantage License Mode: field shows Normal.

To copy translations files to the media server: 1. Under Miscellaneous, click Download Files. 2. Click Browse and select the translation file saved on the Services laptop. 3. Click Download to place the file on the media server.

To restore the translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file should be at the top of the list.
Issue 2.1 June 2006
725
4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file, then scroll down and click Review Status to see the results of the restore. When done, the screen shows Restore is finished. If the restore process fails, you get an error message that states the reason for the failure. If that happens, the translation file is not restored. Resolve the reason for the failure and restart the process.

To connect to the standby media server: 1. Connect to the Services port on the back of the standby media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Release Server. 6. Click Release.

To connect to the active media server: 1. Connect to the Services port on the back of the active media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Interface. 5. Under Server, click Status Summary to verify that the standby media server was refreshed. Do not continue until the standby media server is refreshed. 6. Start a SAT session with Native Configuration Manager or Avaya Site Administration. 7. Login as craft or dadmin.

To install the translations: 1. Type reset system 4. Press Enter. 2. Return the STS-supplied PCMCIA flash card to Avaya. To add the IPSI translations before saving translations, go to Adding IPSI translations to Communication Manager on page 727.



To add IPSI information: 1. Type add ipserver-interface PNnumber where PNnumber is the port network number. Press Enter. 2. When you use static addressing, in the Host field, type in the IP address for the IPSI in the port network that is listed in the Location field. 3. Verify that all the other fields are populated.
Issue 2.1 June 2006
727
4. Press Enter to put the changes into effect. 5. Repeat Steps 1 through 5 for each port network.

To back up translations: 1. Format an unformatted CompactFlash card. Note: For the following step, if you are not sure the card is formatted, format the card. 2. S8700 MC: Insert the PCMCIA memory card (Local PC card) in the bottom PCMCIA slot of the active media server. S8710: Insert a formatted CompactFlash card in the compact flash drive attached to a USB port. 3. Start a Web browser. 4. Log in as craft or dadmin. 5. Click Launch Maintenance Web Pages. 6. Under Data Backup/Restore, click Backup Now. 7. Select the data sets and the backup method. If you select Save ACP translations prior to backup, the media server automatically saves the translations to its hard disk before saving it to the backup media. 8. Click Start Backup to start the back up process.
Note:
Migration tasks
Migration tasks
Perform the following tasks to change a processor port network to a port network (MCC).
Verifying hardware
Removing the processor port network control carrier

To remove the processor port network control carrier(s): 1. Label both ends of all the cables being removed from the control carriers. They can be reused.
! CAUTION:
CAUTION:
All active calls processed through this PN are dropped when the cabinet is turned off. All trunks and lines within this cabinet are not operating until the cabinet is turned on and the media server controls the PN. Note: If the system is equipped with Power Failure Transfer (PFT) units using ground start trunks, you must install a temporary ground wire to the PFT units to allow them to operate properly when the cabinet is turned off. The AUX cable that normally supplies the ground is disconnected. 2. Connect a 10 AWG (#25) (2.6 mm2) wire to pin 49 of the connecting block associated with the power failure transfer panel. 3. Route the opposite end of the wire to an approved ground and connect. Note: You can cut over to having the media server control the other PNs at this time. Only cutover at this time if you are not installing IPSI(s) in the PPN or the customer wants to minimize out-of-service time. To cut over, go to Enabling control of the IPSI on page 737. 4. Turn off the cabinet. 5. Disconnect the following cables on the front of carrier A.

Note:
Note:
Power ATM Fiber (optional)
Issue 2.1 June 2006
729
6. Remove all circuit packs from carrier A and place the circuit pack in an antistatic carrier or bag. 7. Remove the power supplies from carrier A. 8. Remove the faceplate from carrier A 9. Disconnect the following cables on the back of carrier A.

TDM/LAN - can be reused ICC-A, -B - must be replaced AUX Cable - can be reused 9-pin D subminiature plug on the right side of cabinet from the P1 connector on the carrier - can be reused
10. Remove the current limiter (CURL) unit from the back of the carrier. You can reuse the CURL. 11. Remove all carrier grounds. 12. Remove carrier A from the cabinet. 13. Repeat for carrier B (high-reliability and critical-reliability only).
Installing the expansion control carrier and the port carrier

To install the expansion control carrier and port carrier: 1. Install the J58890-AF-2 L13 PN expansion control carrier in position A. 2. Install a J58890BB -4 L14 Port carrier in position B. 3. Connect the carrier grounds. 4. Install the CFY1B current limiter (CURL) unit on the back of control carrier A. You can reuse the CURL. 5. Connect the cables to the back of the carriers.
TDM/LAN

Carrier A to D (if equipped) Carrier A to B Carrier B to C (if equipped)
ICC cables from carrier A to B (if required).

Duplex reliability: No ICC cables required High reliability: ICCC and ICCD Critical reliability: ICCA, ICCB, ICCC, and ICCD
Migration tasks
AUX cable to carrier A. 9-pin D subminiature plug to P1 connector on each carrier.
6. Install the faceplates on carrier A. 7. Install the faceplates on carrier B. 8. Install the power supplies in carrier A. 9. Install the power supplies in carrier B.

If this PN does not contain an IPSI, install the tone clock and the maintenance circuit packs, as required. Then continue with Installing Expansion Interface circuit packs on page 785. If this PN contains one or two IPSIs, reinstall the IPSIs and the ribbon cables as you did before. For the procedures, see Duplex reliability configuration on page 779 and High-reliability or critical-reliability configuration on page 782. Although you can use ICCs for connectivity (ICCC and ICCD) for consistency, just use the ribbons on the front.

Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Servers (555-245-703).
To connect the CAT 5 cables to the IPSI circuit packs:
Connect the green CAT5 cable to the IPSI in the A carrier.

Note:
Note: If the existing PPN has a TN776 or TN570 Expansion Interface circuit packs, you must replace them with a TN570B, vintage 7, or higher circuit pack. If you are also installing an Enterprise Survivable Server (ESS), you must replace the TN776 or TN570 Expansion Interface circuit packs with a TN570D Expansion Interface or later circuit pack.
Issue 2.1 June 2006
731
To install the Expansion Interface circuit packs: 1. Remove the existing circuit pack and place the circuit pack in an antistatic container or bag. 2. Insert the TN570C or later EI circuit packs into the EXPN INTFC slots (A01, B02).

Post-migration tasks
Note:
Note:
! CAUTION:
CAUTION:
Note:
Note:
Issue 2.1 June 2006
733



Note:
Note:
CLK
S E R V
Note:

fpdlled3 LJK 022502
Issue 2.1 June 2006
735

CLK
fpdlled2 LAO 112905
S E R V

To verify IPSI translations: 1. Type list ipserver-interface. Press Enter. 2. Verify that the ISPI circuit pack(s) are translated. The State of Health - C P E G column shows 0.0.0.0 for each healthy IPSI. If a "1" shows in any position, you must troubleshoot the problem.
fpdlled1 LJK 022502
Tip:
Tip:


Note:
! CAUTION:
CAUTION:
Issue 2.1 June 2006
737



To verify circuit pack locations: 1. Type list cabinet. Press Enter to view all the "cabinets." Verify that the cabinet number assigned to the converted cabinets shows. 2. Type display cabinet number, where number is the cabinet number of the converted cabinet. Press Enter. Under Carrier Description, Carrier Type verify that the number of "carriers" in use matches the number of media gateways in the rack (G600 or G650).



Upgrading firmware

Issue 2.1 June 2006
739




Changing port networks to IP-PNC

Use these procedures to migrate fiber-PNC to fiber-PNC. To change one or more port networks to IP-PNC, see Conversions.
Migrating a DEFINITY Server R to an S8700-Series Media Server

Note:
Use these procedures to migrate from an existing DEFINITY Server R system to an Avaya S8700-Series Media Server configuration. As of Communication Manager release 3.1, migrations to the S8700 and S8720 Media Servers are supported. If all the port networks (PNs) are connected through a center stage switch (CSS) or asynchronous transfer mode (ATM), Avaya recommends that you first replace the:

Tone-Clocks with TN2312BP IPSI circuit packs in the processor port network (PPN) Expansion port networks (EPNs)
The IPSIs are hot swappable. If all the PNs are direct connect, Avaya recommends that you install one IPSI in the existing PPN rather than in one of the EPNs. But before you install the IPSI, you must convert the PPN to an EPN. This process requires that you:

Replace the processor control carrier with an expansion control carrier Remove all the control circuit pack
This migration affects service. You must be turn off the PPN to replace the carrier. Before you turn off the cabinet, you must perform some premigration administration.

Note:
Note: When you complete this migration, the terms EPN and port network (PN) can be used synonymously.
When migrating from DEFINITY platforms:
Install the media servers. If Avaya supplies an Ethernet switch(es) and uninterruptible power supplies (UPSs), you also must install the switch and the UPS in the 4-post (S8710), 19-inch rack. For more information, see Quick Start for Hardware: Avaya S8700-Series Media Server (555-245-703). Replace the tone clock circuit pack with the IPSI circuit pack
Issue 2.1 June 2006
741
Connect the media servers to the media gateway Enable control of the IPSIs and switch control to the media servers Install new RFA license file and authentication file Complete the post-migration administration
Migration paths
Avaya supports the following migrations of a DEFINITY Server R to the S8700-Series Media Server configurations:

DEFINITY Release G3V4 DEFINITY Release 5 through 10 MultiVantage Release 1.1 through 1.2 Communication Manager Release 1.3
To migrate, you can use the existing translations. For a DEFINITY Server R with a magneto optical drive, you can use the Magneto Optical to S87x0 Translations (MOST) Tool to copy the translations to the S8700-Series Media Server. For a DEFINITY Server R without an optical drive, you must: 1. Freeze the translations 2. Send the translations to the Avaya Software Technical Support (STS) group STS then returns the translation files and translation reports by e-mail along with documentation on how to save them to the Services laptop and restore them to the S8700-Series Media Server. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
This section provides information on transferring translations to the S8700 Series Media Servers.
Prerequisites
From a magneto optical disk

Use the Magneto Optical to S87x0 Translations (MOST) Tool to transfer translation files from a magneto optical disk to an Avaya S8700-Series Media Server. Use this tool only when you migrate call processing translations on a DEFINITY Server R to an Avaya S8700-Series Media Server. The MOST tool is not shipped with each system but might be available locally. The MOST tool that you use with the S8710 or S8720 Media Server consists of:

An external Magneto Optical drive A USB cable
Comcode 700355415 Description Magneto Optical Server to S8710 Translations (with USB cable)
! CAUTION:
CAUTION:
When creating the optical disk that is used to move translations from the source system to the S8700-Series Media Server, there are specific steps that must be followed. For more information, see Presite migration checklist on page 751.
Prerequisites
This section provides those tasks that must be completed prior to starting the migration. This section covers the following tasks:
Presite checklist on page 744 - these are tasks that must be performed before going on site. Additional tasks on page 746 - these are tasks that must be performed on site before starting the migration from an existing DEFINITY system. Presite migration checklist on page 751 - these are tasks that must be completed before going on site.
Issue 2.1 June 2006
743
On site migration checklist on page 752 - these are tasks that must be performed on site before starting the migration. Documentation checklist for migrations on page 754 - these are the documents Avaya recommends that you have on hand for the migration.
Tasks checklists
Presite checklist
:
Description Correct hardware includes: 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 Correct software includes: Windows 2000 or Windows XP operating system Terminal emulation program: HyperTerminal or another TCP/IP networking software bundled with the Windows OS Internet Explorer 5.0 or later 1 of 3
Prerequisites
Task Obtain the appropriate logins and passwords for all equipment and software.
Description For example, obtain logins and passwords for the following components: Media Server Media Gateway SIPI or IPSI circuit pack auxillary equipment Communication Manager These logins and passwords include the logins and the passwords that you might need for the equipment of the customer. You need a new license file and authentication file. You need the serial number from the reference SIPI or IPSI and the SAP order number to generate a new license file. Use this CD-ROM to install the software on the media server and upgrade the firmware. The most recent versions of the service packs are also on this CD-ROM. Check which service packs you need and download files from the Avaya Support Web site (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site (http:// avaya.com/support).
Verify that you have the Communication Manager software distribution CD-ROM with the current software and firmware. Verify that you have the current preupgrade or premigration service packs, if required, on your laptop. Verify that you have the current post-upgrade or post-migration service packs, if required, on your laptop. Verify that you have the current firmware available.

Important: Firmware is upgraded often. To ensure that you have the latest version, go to the Avaya Support Web site (http://avaya.com/support). Click Downloads and select the product. 2 of 3
Issue 2.1 June 2006
745
Task Download license and authentication files to your Services laptop. Avaya technical support representatives only: Obtain the static craft password. Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary.
Description New license and authentication files are necessary. Obtain information and download files from the Remote Feature Activation (RFA) web site at http:// rfa.avaya.com. Call the ASG Conversant number 800-248-1234 or 1-720-444-5557 and follow the prompts to get the password. You need the Product ID, the FL, or IL number of the customer. This step is necessary if the configuration of the customer INADS alarming modem has changed or if any changes were made to the system alarming configuration. ART is available only to Avaya associates. BusinessPartners can call 800-295-0099. These files can include: Service packs License file Authentication file Firmware for programmable circuit packs 3 of 3
Additional tasks
Prerequisites
Premigration setup

For more information, see Migration paths on page 742. When migrated from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task Determine which adapters and cables you can reuse. Description You cannot reuse the following items:
The 982LS Current Limiter (CURL) for an SI. You must replace with larger CFY1B CURL. The C-LAN 259A adapter. You must use adapter for IP Media Processor for 100-Mbps speed. The CAT3 cable that is used with C-LAN. You must use a CAT5 or better cable for 100-Mbps speed.
CAUTION: If you are going to use the MOST Tool, you must complete the following eight tasks before you freeze translations or save translations to an MO disk that is used to read translations directly into an S8710 or S8720 Media Server. If you want to use STS for translation conversion, go to Replace any TN775/B/C maintenance circuit packs. on page 750. CAUTION: Be sure to perform this step before freezing translations. Verify that existing logins do not start with a number or an asterisk (*). 1 of 4 Linux does not support logins that start with a number or an asterisk (*). Use the SAT command list logins to verify existing logins do not start with a number or an asterisk (*).
Issue 2.1 June 2006
747
Task CAUTION: Be sure to do this step before freezing translations. Verify that the functions of the TN577 Packet Gateway and the TN726B Data Line circuit packs (BX.25 links and mode 2 data modules) were converted to work through the C-LAN circuit packs. CAUTION: Be sure to do this step before you freeze translations. Verify that the peripheral links were assigned node names and have an Ethernet address assigned. CAUTION: Be sure to do this step before freezing translations. Remove all Mode II Data Modules before you change the S8700-Series Media Server.
Description Note that you cannot reuse the TN577 circuit pack. Use Avaya Terminal Emulator or Avaya Site Administration to perform a list node-names command.
The peripherals include:

CMS INTUITY Distributed Communication Service (DCS)
The S8700-Series Media Servers do not support the following data modules:

System Ports PDMs (7400/8400 Data Modules) PktGateway Pkt Data Dataline Modem Pool System CDR PDMs System Printer PDMs 2 of 4
Prerequisites
Task CAUTION: Be sure to do this step before freezing translations. Change the circuit pack locations from the TN750 Announcement circuit packs to the TN2501AP VAL circuit pack.
Description The TN750 Announcement circuit packs are not supported in the S8700-Series Media Servers. The announcements translations come over to the S8700-Series Media Server. However, the circuit pack locations need to be changed to the TN2501AP Voice Announcement over LAN (VAL) circuit pack. NOTE: All announcement names must be unique on a TN2501AP Voice Announcement over LAN (VAL) circuit pack. The announcement names cannot contain any spaces, blanks, or the following characters:

period (.) forward slash (/) colon (:) asterisk (*) question mark (?) backward slash (\) angle brackets (<>)
Type change announcements to change any names and port locations. CAUTION: Be sure to do this step before freezing translations. On the IP Services screen in the Service Type field, remove Alarm1 and Alarm2. CAUTION: Be sure to do this step before freezing translations. On the Trunk Group screen, change the Measured field from measured to none. This action indicates that trunk group measurement reports are not required. Remember to remeasure trunk groups. Type list trunk-group to get a list of trunk groups that are "measured" and need to be changed. You first might need to change the System Parameters Maintenance screen before you can make any changes to the IP Services screen.
3 of 4
Issue 2.1 June 2006
749
Task CAUTION: Be sure to do this step before freezing translations. Check the Dial Plan screen (or Dial Plan Analysis Table screen depending on the release) for 0 assigned as attd. Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations.
Description If none, check the Attendant Console screens for any buttons with attd-qcalls or attd-qtime btns. Remove these if 0 is not assigned as attd.
Replace the TN775/B/C maintenance circuit pack with TN775D circuit packs in any EPN that contains an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS then updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. Verify that a copy of the existing translations exists so that you can reenter the translations later.
Collect the translations by tape or Magneto Optical cartridge.
If the existing system does not have a magneto optical drive or if the MOST (From a magneto optical disk on page 743) will not be used, send the translation media to the STS. Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
When you finish installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time that you log in as craft, if you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access still requires an ASG challenge/response. This unique craft password remains valid until the password is changed by installing a new authentication file.
4 of 4
Prerequisites

Before you go on site, complete the following additional tasks: Task Replace the TN570 EI circuit packs. Description If you also are installing an ESS server, replace with TN570D or later circuit pack.
Issue 2.1 June 2006
751

Prerequisites
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before starting the migration: Task The customer supplies an EIA 310D (or equivalent) standard, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly. Verify that cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are labeled and that appropriate connectivity is provided. Verify that you have the license file from RFA and that the file includes the licensed features. Verify that you have the Avaya authentication file from RFA. Verify that you have the required tools on site. For instructions on how to transfer translations using the Magneto Optical Server Tool, see Transferring translations on page 766. The TN2312BP Internet Protocol Server Interface (IPSI) circuit packs runs from the control hardware rack to the port networks. Description Ensure that you have the screws that come with the rack for installing in square holes or with adapters. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the documentation that comes with the rail kit.
Issue 2.1 June 2006
753

Migration tasks
! CAUTION:
CAUTION:
The following list describes the general procedures:

Turn off the processor gracefully - preconversion administration Connect the IPSI circuit pack to the Ethernet switch on the customer network Assign an IP address to the IPSI circuit pack
Migration tasks
Note:
Perform the following tasks to convert a processor port network to a port network (MCC). Premigration administration:

Connecting to the processor on page 762 Verifying administration and system status on page 763 Recording all busyouts on page 763 Recording node names and IP addresses on page 764 Saving translations on page 764
Migration tasks:

Accessing the media server maintenance web interface on page 765 Checking system status on page 765 Verifying the license file on page 765 Transferring translations on page 766 Disconnecting from the active media server on page 766 Connecting to the standby media server on page 766 Disconnecting from the standby media server on page 766 Connecting to the active media server on page 767 Copying translation files from the MO disk to the active S8700-Series Media Server on page 767 Disconnecting from the active media server on page 769 Connecting to the standby media server on page 770 Disconnecting from the standby media server on page 770 Connecting to the active media server on page 770 Installing the translations on page 770 Restoring data for a migration on page 771 Adding IPSI translations to Communication Manager on page 773 Setting IPSI duplication (high-reliability critical-reliability only) on page 774 Adding IPSI information on page 775 Setting the alarm activation level on page 775 Backing up translations on page 776
Issue 2.1 June 2006
755
Upgrading and administering the existing hardware on page 776 Connecting the media server cables and the IPSI cables to the Ethernet switch on page 777 Upgrading the hardware in each port network on page 777 Duplex reliability configuration on page 779 High-reliability or critical-reliability configuration on page 782 Connecting the CAT5 cables to the IPSI circuit packs on page 785 Installing Expansion Interface circuit packs on page 785 Completing circuit pack replacement on page 785 Verifying hardware on page 786 Removing the processor port network control carrier(s) on page 786 Installing the expansion control carrier and the port carrier on page 787 Installing IPSI and maintenance circuit packs on page 788 Connecting the CAT5 cables to the IPSI circuit packs on page 788 Installing Expansion Interface circuit packs on page 788 Turning on the media gateway on page 789

Accessing the server command line interface with SSH protocol on page 789 Using DHCP addressing on page 791 Administering the location assignment on page 791 Setting the switch ID on page 792 Setting the cabinet number on page 793 Verifying IPSI translations on page 793 Verifying IPSI connectivity on page 794 Enabling control of the IPSI on page 794 Verifying the customer data on page 795 Verifying circuit pack locations on page 795 Verifying circuit pack insertion on page 795 Verifying the IP addresses on page 795 Checking the link status on page 796 Upgrading firmware on page 796 Testing the installation on page 797
High-level overview
Busying out previously busied out trunks on page 797 Troubleshooting the migration on page 797 Returning replaced equipment on page 797
High-level overview
Note:
Note: This section applies to migrations of non-Linux-based servers to the S8700-Series fiber-port network connectivity (PNC) configuration only.
The migration from a DEFINITY Server R to the Avaya S8700-Series Media Server fiber-PNC configuration can be done in stages. The order in which you complete these stages, in most cases, depends on the available:

resources personnel, and the amount of out-of-service time that is acceptable to the customer
The recommended process is based on several assumptions:
The TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are installed ahead of time in the EPNs and the optional PPN. Most PNs that are converted from a PPN contain an IPSI, particularly for direct-connect systems. The general process is the same regardless of the degree of reliability.
The high-level stages are:

Install and configure the S8700-Series Media Server complex. Transfer the existing DEFINTY translations to Avaya Communication Manager that resides on the S8700-Series Media Servers. Add new translations for the IPSI circuit packs. Replace the expansion interface and the maintenance circuit packs in all the existing DEFINITY server PNs with TN570B, vintage 7 or later or TN775D circuit packs. (Optional) Replace tone clock circuit packs with TN2312BP IPSI circuit packs in the designated EPNs and PPN. Convert the PPN to a PN. Cut over to S8700-Series Media Server control. Complete the remaining migration steps, such as enabling alarm reporting and registering the system. Test the S8700-Series Media Server configuration.
Issue 2.1 June 2006
757
The order in which these high-level stages are listed represents a recommended sequence to follow. Some of the stages can occur in a different sequence without negative consequences. Local practice and resource management dictates the actual sequence.
IPSI placement decisions

In a direct-connect system Avaya installs the IPSIs in the PPN rather than an EPN because of the fiber connections and administration between the PNs. If you install the IPSIs in an EPN in a three-cabinet system, you might have to reconnect and readminister the optical fiber that connects the EI circuit packs. In a two-cabinet system, this would not be a problem. Even in a CSS system, Avaya recommends that you install the IPSIs in the PPN to speed up the system startup. You then install the rest of the IPSIs in as many cabinets as you can. Avaya does not recommend that you install IPSIs in both halves of a dual PN cabinet. If the cabinet fails, two IPSI PNs are lost. However, if in a 10-EPN system, 7 of the EPNs are DS1-C remoted and the other 3 PNs are one PPN cabinet and one dual PN cabinet. Putting IPSIs in both halves of the dual PN and the converted PPN eliminates running remote IPSI connections. If you install the IPSIs in the PNs and the PPN, prior to the migration, you save out-of-service time because you then can install, connect, and program the IPSIs and test the connectivity to the media server. To save more out-of-service time, you also can upgrade the firmware on the IPSIs if needed before the actual cutover. If you install the IPSIs in the PPN and then reinstall the IPSIs in the new carriers, you can ensure that the IPSIs work correctly before the cutover.
Installing and configuring the S8700-Series Media Server complex

In this stage you install the S8700-Series Media Servers, uninterruptible power supplies (UPSs), Ethernet systems, and connecting cables. After you complete the installation, you then:

Configure the components Install the license file and Avaya authentication file Upgrade and patch the software
For more information on how to install the media server complex and configure the media servers, see Installing and Configuring an Avaya S8700 Series Media Server (03-300145). You can complete this stage any time before you transfer the existing translations. These tasks do not affect service to the existing DEFINITY server system.
High-level overview
Transferring existing translations

For existing systems that have a magneto optical (MO) disk drive, you can connect the MO drive to the S8700-Series Media Server. You then can use the drive to transfer the translations. For systems that do not have a MO disk drive, you must: 1. Freeze the translations. 2. Send the translations to the STS. 3. Receive updated translation files by e-mail. Perform this stage after you install and configure the server complex and before you convert the PPN to a PN. Once you copy and save the translations, you can add the new IPSI translations, ensuring that the IPSIs are set to disabled. These tasks do not affect service. However, Avaya recommends that you complete this stage just before you convert the PPN. If you complete this stage early in the installation process, you increase the chance that the new translations are added to the existing DEFINITY system. This means that the translations might be out of sync. Unless these translations are concurrently entered into Avaya Communication Manager, they can be lost when you cutover the system.
Replacing expansion interface and maintenance circuit packs, if necessary

In PNs that have IPSIs, you must replace the maintenance circuit pack with a TN775D Maintenance (EPN) circuit pack. You also might need to replace the expansion interface (EI) circuit packs. Only TN570B vintage 7 or later circuit packs work in an S8700-Series fiber-PNC configuration. You can complete this stage at any time before the cutover. The maintenance and the EI circuit packs are hot swappable. Hot swappable means that you can replace the circuit packs in the existing DEFINITY system without the need to turn off the carrier or the cabinet. This stage affects service for duplex-reliability configurations. The PNs are out of service while you replace the circuit packs. To save out-of-service time in high-reliability and critical-reliability configurations, you can replace the circuit packs in only the standby carriers or cabinets.
Issue 2.1 June 2006
759
Replacing the tone clocks with TN2312BP IPSI circuit packs in the expansion port networks and the processor port network (optional)
Some PNs receive IPSI circuit packs. The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes the place of the existing TN2182 Tone Clock circuit pack and terminates control communication with the S8700-Series Media Servers. In existing PNs that receive IPSIs, flat ribbon cables run between the IPSIs and the maintenance circuit pack. These ribbon cables provide connectivity that is unavailable by the backplane of older carriers. Once the IPSI circuit packs are installed, you must either:

Program the faceplate so a DHCP server can assign IP addresses to the IPSIs Program static IP addresses into the IPSI, depending on whether the control network is dedicated (private) or nondedicated. Nondedicated means through the customer network.
You can complete this stage at any time before the cutover. The tone clock and the IPSI circuit packs are hot swappable, and you replace the circuit packs in the existing DEFINITY system without the need to turn off the power. The IPSI circuit pack provides the same functionality as the tone clock circuit pack. The IPSIs can be connected by CAT5 cable to the media server complex by the Ethernet switch before the cutover. You can do this while the IPSIs are working as tone clocks in the existing system. With this connection, you can test connectivity between the media servers and the IPSIs before the cutover. Even though you are converting the PPN to a PN, Avaya recommends that you install the IPSIs in the PPN and test connectivity prior to the migration. You then reinstall the IPSIs in the new carriers after you install the carriers. This stage affects service in duplex-reliability configurations. The PNs are out of service while you replace the circuit packs. To save out-of-service time in high-reliability and critical-reliability configurations, you can replace the circuit packs in only the standby MCC carriers or SCC cabinets.
Converting the processor port network to a port network

This stage consists of replacing the processor carrier A in the PPN with a new expansion control carrier (J58890AF-2 L13). If the PPN has duplicated control carriers or cabinets you also must replace carrier B with a new port carrier or cabinet. If you replaced the EIs and maintenance circuit packs and replaced the tone clock with an IPSI circuit pack in the old control carrier, you must reinsert these circuit packs into the new control carrier. You do not need to reprogram the IPSI. If the system is critical-reliability and you have a CSS or an ATM, you must move the EI circuit packs to positions A01 and B02. You must install and configure the media servers, transfer the translations, and upgrade the existing PNs before you complete this stage.
High-level overview
If you want to cut over and have the S8700-Series Media Server control the existing PNs while you convert the PPN, you must: 1. Turn off the PPN. 2. Enable the IPSIs from the S8700-Series Media Server. Do this only if the customer wants to minimize out-of-service time. If the PPN also contains the switch node carrier, you take the CSS out of service when you turn off the PPN. This stage affects service to the PPN and thus to the existing DEFINITY server system. The DEFINITY system is out of service while you replace the circuit packs. This should take no more than 30 minutes.
Cutting over to S8700-Series Media Server control

Once you convert the PPN and you turn on the power, you want to cut over to the S8700-Series Media Server. To cut over to the media server, you must enable the IPSIs on the IP Server Interface (IPSI) System Parameters screen. This stage affects service momentarily while the CSS comes back up and the calls are load balanced across the IPSIs throughout the port networks.
Completing the migration

This stage includes verifying the data of the customer and upgrading IPSI firmware, if necessary. The system generates alarms if the IPSIs do not have the most current firmware or do not all have the same firmware. For more information on other post migration tasks, such as:

Clearing alarms Backing up the media servers Enabling alarm reporting Registering the system
see the Completing the installation administration section in Installing and Configuring an Avaya S8700-Series Media Server (03-300145). This stage includes:

Clearing alarms Upgrading IPSI firmware, if necessary Backing up the media servers Enabling alarm reporting Registering the system
Issue 2.1 June 2006
761
You must complete this stage after the cutover. However, you also can complete some parts of this stage before the cutover such as upgrading firmware and registering the system. None of the tasks in this stage affect service. However, you might interrupt service if you must replace any hardware to clear the alarms.
Testing the S8700-Series configuration

In this stage you test the complete system and verify proper operation. Functional call processing is tested, such as station-to-station calls, outgoing calls, incoming calls, and so on. Various hardware-related testing procedures are provided. These might not be performed, depending on whether a given piece of hardware is configured. Perform the testing procedures after the cutover is complete and while finishing the migration. These procedures do not affect service. However, you might interrupt service if you have to replace any hardware to solve a problem. Note: You now are ready to start the migration.
Note:
! CAUTION:
CAUTION:

Verifying administration and system status

You want to check which groups are administered before the migration and compare the list after the migration to ensure that they are the same. To verify administration and system status: 1. Execute the following commands to determine whether the system has administration and system status: a. list config all b. list trunk c. list sig d. list station e. list dial analysis f. list vector g. list vdn h. list node-names i. list ip-interfaces j. display alias station k. disp sync l. status health m. status spe n. status pnc o. status sync If any command does not complete successfully, escalate the problem immediately. After the migration, check the same administration to ensure that the translations are intact.

Issue 2.1 June 2006
763

Note:
Saving translations
Although the migrated translations are already copied to the S8700-Series Media Server, this step is important in case you need to back out of the migration. Note: Save translations to disk, optical diskette, or tape.
Note:
To save translations, perform the following step: 1. Perform one of the following actions:
To save translations to the hard disk on the DEFINITY Server R: - For a single DEFINITY Server R, type save translation and press Enter. - For a duplicated DEFINITY Server R, type save translation both and press Enter.
To save the translations to a magneto optical (MO) disk drive, type save translation both removable and press Enter. To save the translations to a tape, type save translation tape and press Enter.
The system displays a Command successfully completed message or logs any error messages.
This section provides information for migrating translation files from the existing system to the new S8700-Series Media Server.




Issue 2.1 June 2006
765
Note:
Note: If you sent the translations to the STS group on a tape, STS returns the translations by e-mail with instructions.
For how to transfer translations if the existing system has an optional drive, see From a magneto optical disk on page 743. Once you copy the translations to the hard disk, you must administer the TN2312BP IP Server Interface circuit packs.

To disconnect from the active media server:
Unplug the laptop from the Services port (2) on the back of the active media server.

To connect to the standby media server: 1. Connect to the Services port (2) on the back of the standby media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Busy-out Server. 6. Click Busy Out.

To disconnect from the standby media server:
Unplug the laptop from the Services port (2) on the back of the standby media server.

Note:
Note: If the PCMCIA memory card currently is plugged in to the bottom slot on the active media server, remove the card. You need the bottom slot to plug in the MOST tool.
To connect to the active media server: 1. Click Start > Run > Command to open a DOS Command window. 2. Perform one of the following actions:
If you are connected to the Services port (2): a. Type telnet 192.11.13.6 and press Enter. b. At the login prompt, log in as craft or dadmin.
If you are connected through the customer network: a. Type telnet ipaddress, where ipaddress is the active media server IP address and press Enter. b. At the login prompt, log in as craft or dadmin.
Copying translation files from the MO disk to the active S8700-Series Media Server
To copy translation files from the MO disk to the active media server: 1. Type stop -acf. Press Enter to stop Communication Manager call processing. 2. Type sudo readmo -e. Press Enter to enable MO read. 3. Turn on the MO drive. Use the power switch on the back of the drive. For the media servers, see Magneto optical drive connection to media servers on page 769. 4. S8710: Insert the MOST Tool USB cable into a USB port on the back of the media server. 5. Insert the optical disk into the external MO drive. 6. Type sudo mo -1. Press Enter to list the contents of the MO disk. Note the file sizes of Translation and TranslationA. Note: The next step copies the translation files from the MO disk to /etc/opt/defty on the media server hard disk.
Note:
Issue 2.1 June 2006
767
7. Type sudo readmo. Press Enter to copy the translations from the MO disk to the media server. Reading the translation files takes from 40 seconds to one minute during which time the light on the front of the MO drive flashes rapidly. 8. Type cd /etc/opt/defty. Press Enter to change to the translations directory. 9. Type ls -l. Press Enter to verify that files xln1 and xln2 are the same size as files Translation and TranslationA from Step 6. 10. If the file sizes are different repeat Steps 6 through 9. If the file sizes are still different, escalate the problem through the appropriate channels. 11. S8700 MC: Eject the flash adapter from the media server. Unplug the MOST tool from the USB port. 12. Type sudo readmo -d. Press Enter to disable MO read. 13. Type start -ac. Press Enter to restart Communication Manager call processing. 14. Remove the cartridge from the MOST Tool. 15. Turn off the power to the MOST Tool.
Figure 50: Magneto optical drive connection to media servers
cadloptu LAO 040705
Figure notes: 1. Back of the media server 2. USB port on the S8700-Series Media Server 3. USB connector to the media server 4. USB connector to the MOST Tool 5. Bottom connector on the Magneto Optical drive 6. Magneto Optical Server to S8700-Series Translations (MOST) Tool

To disconnect from the active media server:
Unplug the laptop from the Services port (2) on the back of the active media server.
Issue 2.1 June 2006
769

To connect to the standby media server: 1. Connect to the Services port (2) on the back of the standby media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Release Server. 6. Click Release.

To disconnect from the standby media server:
Unplug the laptop from the Services port (2) on the back of the standby media server.

To connect to the active media server: 1. Connect to the Services port (2) on the back of the active media server. 2. Start a SAT session with Native Configuration Manager or Avaya Site Administration. 3. Log in as craft or dadmin.

To install the translations:
Type reset system 4. Press Enter.
To add the IPSI translations before you save translations, see Upgrading and administering the existing hardware on page 776.
Restoring data for a migration

You cannot perform this procedure unless you first have received the conversion files from the STS group and installed the files on the Services laptop.

To busy out the standby media server: 1. Connect to the Services port (2) on the back of the standby media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Busy-out Server. 6. Click Busy Out.
Accessing the active media server from your laptop

To access the active media server: 1. Connect a cross-over cable to the Services port (2) on the back of the active media server. 2. Start the Web browser. 3. Type 192.11.13.6 in the Address field. Press Enter to bring up the logon Web page. 4. Log in as craft or dadmin. 5. Select yes to suppress alarms. 6. Click Launch Maintenance Web Interface to go to the Main Menu.
Busying out the active media server

To busy out the active media server: 1. Connect to the Services port (2) on the back of the active media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Busy-out Server. 6. Click Busy Out.
Issue 2.1 June 2006
771

To verify the license file: 1. Under Security, click License File. 2. Verify that the CommunicaMgr License Mode field is set to Normal.

To copy translation files to the media server: 1. Under Miscellaneous, click Download Files. 2. Click Browse and select the file that you saved on the Services laptop. 3. Click Download to place a copy of the file on the media server.

To restore the translations files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically displays the default directory. 3. Select the first file. The latest file should be at the top of the list. 4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file and then scroll down and click Review Status to see the results of the restore. When the restore process is complete, the screen displays Restore is finished. If the restore process fails, the system displays an error message that states the reason for the failure. The translation file is not restored. You must resolve the reason for the failure and restart the process.

To connect to the active media server: 1. Connect to the Services port (2) on the back of the active media server. 2. Start a Web browser. 3. Log in as craft or dadmin.
4. Click Launch Maintenance Web Interface. 5. Under Server, click Status Summary to verify that the standby media server is refreshed. Do not continue until the standby media server is refreshed. 6. Start a SAT session with Native Configuration Manager or Avaya Site Administration. 7. Log in as craft or dadmin.

To install the translations: 1. Type reset system 4. Press Enter. 2. Log in to a SAT session. 3. Type list station. Press Enter. Verify that you have the current translations. To add the IPSI translations before you save the translations, see Upgrading and administering the existing hardware on page 776.

To connect to the standby media server: 1. Connect to the Services port (2) on the back of the standby media server. 2. Start a Web browser. 3. Log in as craft or dadmin. 4. Click Launch Maintenance Web Pages. 5. Under Server, click Release Server. 6. Click Release.

To add IPSI translations to Communication Manager: 1. Type change system-parameters ipserver-interface. Press Enter.
Issue 2.1 June 2006
773
2. Verify that the Primary Control Subnet Address and Secondary Control Subnet Address (was equipped) fields are correct. The subnet work addresses must match the most significant three octets (the first three groups of digits in the subnet work address) of the Server IP address that appears on the control network entry from the completed Electronic Preinstallation Worksheet (EPW). An asterisk (*) to the right of the Subnet Address field means that although a subnet work address appears, this address is incorrect. Avaya Communication Manager call processing software does not have the subnet information. After you verify the information on the screen, submit this form with or without changes to update Communication Manager with the correct subnet work information.
! CAUTION:
CAUTION:
Note:


To add IPSI information: 1. Type add ipserver-interface PNnumber, where PNnumber is the port network number. Press Enter. 2. When you use a DHCP server, verify that the fields associated with the Primary IPSI and Secondary IPSI (if equipped) are populated with default data. The Host and DHCP ID fields are set by the DHCP server. 3. Verify the correct setting for the IP Control? field

If there is only one IPSI, set the IP Control? field to y. If IPSIs are in fiber-connected PNs (CSS or ATM), set the IP Control? field to y. If IPSIs are in fiber-connected PNs (direct-connect), set the IP Control? field to y if there is more than 1 IPSI. Set the IP Control? field to n for the second IPSI. If an IPSI is in a DS1-C-remoted PN, set the IP Control? field to n for the first IPSI to maintain the 5:1 ratio of IPSIs to PNs. If the field is set to y, the system decreases the ratio to 2:1.
4. If this system is high-reliability or critical-reliability, set the Administer secondary ip server interface board field to y. 5. Verify that all the other fields are populated. 6. Press Enter to put the changes into effect. 7. Repeat Steps 1 through 5 for each port network.

Issue 2.1 June 2006
775

This section describes how to upgrade and administer existing PNs to prepare for a migration to the S8710 or S8720 fiber-PNC configuration for both multi-carrier cabinets (MCCs) and single carrier cabinets (SCCs). This process consists of:

Placing the CAT5 cables between the Ethernet switches and the PNs Changing out expansion interface circuit packs (if necessary) Changing out tone clock and maintenance circuit packs for IP Server Interfaces (IPSI) and new maintenance circuit packs Connecting the IPSI circuit packs to the Ethernet switches. Assigning IDs or static IP addresses to the IPSI circuit packs.
Note:
The information in this section is based on the assumption that the S8700 Series Media Servers have the latest software release, and that the media server complex is installed, configured, and operational. This section covers the following tasks:
Connecting the media server cables and the IPSI cables to the Ethernet switch on page 777 Upgrading the hardware in each port network on page 777 Installing Expansion Interface circuit packs on page 785 Post-migration administration on page 789
Note:
Note: For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703).
Each TN2312BP IP Server Interface (IPSI) circuit pack must have a CAT5 Ethernet cable that connects back to the Ethernet switch. Cables for IPSIs that are located in PN carrier A are GREEN. Cables for IPSIs that are located in PN carrier B (high or critical reliability) are RED. In duplex configurations, each media server is connected to the Ethernet switch or switches that comprise control network A (CNA) (GREEN cable). In high-reliability and critical-reliability configurations, each media server is connected to the Ethernet switch or switches that comprise control network B (CNB) (RED cable).

In IPSI-controlled PNs, you must replace the existing tone clock and the maintenance circuit packs with a TN2312BP IPSI circuit pack and TN775D or later maintenance circuit pack, respectively. You also must replace the TN570 (R) Expansion Interface circuit packs with TN570B, vintage 7 or later, circuit packs. This section contains the following information:
Replacing tone-clocks with IPSI circuit packs and replacing maintenance circuit packs on page 778 Using DHCP addressing on page 791 Completing circuit pack replacement on page 785
Issue 2.1 June 2006
777
Replacing tone-clocks with IPSI circuit packs and replacing maintenance circuit packs
Note: Before you start, read this procedure and Using DHCP addressing on page 791. If you use a DHCP server, you can set the switch ID and the cabinet number on the IPSI circuit pack at initial installation. However, you must complete certain sequences before to a predetermined timeout interval. If you do not set the switch ID and the cabinet number when you first install the circuit pack it can be done later but it requires that the circuit pack be reseated. This might result in an additional service interruption in a duplex reliability configuration.
Note:

Use this information to determine in which PNs you must install the IPSI circuit packs. Not all PNs require IPSI circuit packs. PNs that do not contain an IPSI have an Expansion Interface (EI) circuit pack that controls the PN. These EI-controlled PNs are assigned automatically to an IPSI when the system is initialized. The system automatically balances the EI-controlled PNs among the available IPSIs. Also, with Communication Manager Release 2.0 or later, you can put an IPSI in a DS1-C-remoted PN. To place the IPSI circuit packs correctly, follow these rules:
When you place an IPSI in a DS1-C-remoted port network, make sure that you administer the nonremoted IPSI first and that you set the IP Control field to y. You do not have to set the IPSI in the DS1-C-remoted PN to no. However, if set to y, customers must run Ethernet from the IPSI and there is limited control (1:2 versus 1:5). Place the reference IPSI in the PN with the shortest Ethernet connection to the media servers. The reference IPSI is the one whose serial number is used in the license file. This placement minimizes the amount of data network that could fail between the IPSI and the media servers and cause the system to switch to No License mode.
!
Important:
Important: If you are using an Enterprise Survivable Server (ESS) and want a given PN to failover, that PN must have an installed PN. For more information, see the Avaya Enterprise Survivable Servers User Guide (03-300428).
Use the following formulas to determine the minimum number of PNs that require an IPSI: - Duplex (direct connect) reliability: One IPSI controls up to three PNs. If you use one or two PNs and you add a G650 media gateway PN, it may have an IPSI. If you use two IPSIs, the IP control for one IPSI is yes and the other is no. - Duplex (CSS or ATM) reliability: Divide the total number of PNs by 5 (if the result is not an integer, round up), and add one.
- High- or critical-reliability: Divide the total number of PNs by 5 (if the result is not an integer, round up). For each IPSI-connected PN, you need two IPSIs.
Duplex reliability configuration

To set up a duplex configuration:
!
WARNING:
WARNING: The following procedure affects service when you are switching the circuit packs. Coordinate this activity with the customer to minimize disruption of customer activities.
Note:
Note: You can replace the maintenance circuit pack with the TN775D Maintenance (EPN) (if necessary) and the TN2182 Tone Clock circuit packs with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. You can program these new circuit packs ahead of time. All the circuit packs being replaced are hot-swappable, so you do not need to turn off the PNs or the carrier. 1. Type list configuration control. Press Enter to determine which PNs contain TN2182 Tone Clock circuit packs and which cabinets contain the circuit packs. 2. In cabinets receiving an IPSI circuit pack, remove the TN2182 Tone Clock circuit pack from the expansion control carrier. Place the circuit pack in an antistatic bag. Note: If present, do not remove the TN771 Maintenance/Test circuit pack. 3. Remove the TN775B/C Maintenance (EPN) circuit pack from the expansion control carrier. Place the circuit pack in an antistatic bag. 4. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot. 5. Attach one end of the short ribbon cable to the connector on the component side of the TN2312BP circuit pack. The red line must be on the bottom (pin 1). See Figure 51: Ribbon cable connector on page 780.
Note:
Issue 2.1 June 2006
779
caxxinst LJK 022002
6. Push the tabs on the ends of the connector inward to lock the connector in place. 7. Thread the ribbon through the slot on the front panel. See Duplex reliability ribbon cable connection on page 781. Duplex reliability in the S8700-Series configuration consists of the two media servers. 8. Insert the TN775D Maintenance circuit pack part way into the MAINTENANCE slot. 9. Attach the other end of the short ribbon cable to the top connector on the component side of the TN775D circuit pack. The red line must be on the bottom. See Duplex reliability ribbon cable connection on page 781.
Figure 52: Duplex reliability ribbon cable connection
B
MS
TR ER N O
CL
TO F AU OF
cadsdupx KLC 072502
10. Push the tabs on the ends of the connector inward to lock the connector in place. 11. Thread the ribbon through the slot on the front panel. 12. Fully insert the circuit packs. 13. Program the TN2312BP that you just inserted. For more information, see Using DHCP addressing on page 791.
Issue 2.1 June 2006
781
High-reliability or critical-reliability configuration

To set up a high-reliability or critical-reliability configuration: Note: You can replace the maintenance circuit pack with the TN775D Maintenance (EPN) (if necessary) and the TN2182 Tone Clock circuit packs with the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. You can program these circuit packs ahead of time. All the circuit packs being replaced are hot-swappable, so you do not need to turn off the PNs or the carrier.
Note:
These procedures assume that the tone clock and maintenance circuit packs are in the A and B carriers. If one of them is in the E or D rather than B carrier, the ribbon cable is not necessary. 1. Determine which PNs get the IPSI circuit packs. See Determining IPSI placement in port networks on page 778. Note: Not all PNs require an IPSI circuit pack. 2. Type list configuration control. Press Enter to determine which port networks contain TN2182 Tone Clock circuit packs and which media gateway contain the circuit packs. 3. Type status port-network number where number is the number of the port network. Press Enter to determine the active tone clock. 4. If needed, type set tone-clock cabinet carrier where cabinet is 1-64 and carrier is A-E. Press Enter to make the Tone Clock in the B carrier active. 5. Remove the TN2182 Tone Clock circuit pack from the standby carrier (A). Place the circuit pack in an antistatic carrier. Note: If present, do not remove the TN771 Maintenance/Test circuit pack. 6. Remove the TN775B/C Maintenance/Test circuit pack from standby carrier (A). Place the circuit pack in an antistatic carrier. 7. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot on the standby carrier (A). 8. Attach one end of the short ribbon cable to the connector on the component side of the circuit pack. The red line must be on the bottom (pin 1). 9. Push the tabs on the ends of the connector inward to lock the connector in place. See Ribbon cable connector on page 780. 10. Thread the ribbon through the slot on the front panel. 11. Insert the TN775D Maintenance (EPN) circuit pack part way into the MAINTENANCE slot in carrier A.
Note:
Note:
12. Attach the other end of the short ribbon cable to the top connector on the component side of the circuit pack. The red line must be on the bottom) See Duplex reliability ribbon cable connection on page 781. 13. Push the tabs on the ends of the connector inward to lock the connector in place. 14. Thread the ribbon through the slot on the front panel. 15. Fully insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack only. 16. Assign the Switch and Cabinet ID to the TN2312BP Internet Protocol Server Interface (IPSI) just inserted. See Using DHCP addressing on page 791. 17. Type set tone-clock cabinet carrier. Press Enter to force a tone clock interchange. 18. Type status port-network number. Press Enter where number is the number of the port network to verify the service state of the tone clock. Verify that the yellow LED on the IPSI circuit pack is flashing. 19. Remove the TN2182 Tone Clock circuit pack from the new standby carrier (B). Place the circuit pack in an antistatic carrier. 20. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack part way into the TONE-CLOCK slot on the standby carrier (B). 21. Attach one end of the long ribbon cable to the connector on the component side of the circuit pack. The red line must be on the bottom (pin 1). 22. Push the tabs on the ends of the connector inward to lock the connector in place. See Ribbon cable connector on page 780. 23. Thread the ribbon through the slot on the front panel. 24. Attach the other end of the long ribbon cable to the bottom connector on the component side of the TN775D Maintenance (EPN) circuit pack. The red line must be on the bottom. See High-reliability or critical reliability ribbon cable connection on page 784. 25. Fully insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack. 26. Program the TN2312BP Internet Protocol Server Interface (IPSI) just inserted. See Using DHCP addressing on page 791. 27. Fully insert the TN775D Maintenance (EPN) circuit pack after both IPSIs have been programmed.
Issue 2.1 June 2006
783
Figure 53: High-reliability or critical reliability ribbon cable connection
CL
B
MS
TR ER N O
CL
TO F AU OF
cadshic KLC 072502
Migration tasks

For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Servers (555-245-703). To connect the CAT 5 cables to the IPSI circuit packs: 1. Connect the green CAT5 cable to the IPSI in the A carrier or cabinet in the A position. 2. If high or critical reliability, connect the red CAT5 cables to the IPSIs in the B carrier or cabinet in the B position.

Note:
Note: If the existing PPN has TN570 Expansion Interface circuit packs, you must replace them with a TN570B Expansion Interface vintage 7 or later circuit pack. If this system is to be used with an Enterprise Survivable Server (ESS), replace the TN570 Expansion Interface circuit packs with a TN570D Expansion Interface or later circuit pack.
To install the Expansion Interface circuit packs: 1. Remove the existing circuit pack and place in an antistatic container. 2. Insert the TN570B Expansion Interface vintage 7 or later circuit pack into the EXPN INTFC slots (01, 02). 3. Repeat steps 1 and 2 for each PN that does not have TN570B Expansion Interface vintage 7 or later circuit packs.

For duplex reliability configurations, repeat Duplex reliability configuration on page 779 for each PN that receives a TN2312BP.
Migration tasks
Perform the following tasks to convert a processor port network to a port network (MCC).
Issue 2.1 June 2006
785
Verifying hardware
Removing the processor port network control carrier(s)

To remove the processor port network control carrier(s): 1. Label both ends of all the cables being removed from the control carriers. They can be reused.
! CAUTION:
CAUTION:
All active calls processed through this PN are dropped when the cabinet is turned off. All trunks and lines within this cabinet are not operating until the cabinet is turned on and the media server controls the PN. Note: If the system is equipped with Power Failure Transfer (PFT) units using ground start trunks, you must install a temporary ground wire to the PFT units to allow them to operate properly when the cabinet is turned off. The AUX cable that usually supplies the ground is disconnected. 2. Connect a 10 AWG (#25) (2.6 mm2) wire to pin 49 of the connecting block associated with the power failure transfer panel. 3. Route the opposite end of the wire to an approved ground and connect. Note: You can cut over and have the media server control the other PNs at this time. Only cutover at this time if you are not installing IPSI(s) in the PPN or the customer wants to minimize out-of-service time. To cutover, go to Enabling control of the IPSI on page 794. 4. Turn off the cabinet. 5. Disconnect the cables on the front of carrier A.

Note:
Note:
Power ATM Fiber (optional)
6. Remove all circuit packs from carrier A and place in an antistatic carrier. 7. Remove power supplies from carrier A. 8. Remove faceplate from carrier A
Migration tasks
9. Disconnect the cables on the back of carrier A.

TDM/LAN - reused ICC-A, -B - Replaced AUX Cable - reused 9-pin D subminiature plug on right side of cabinet from the P1 connector on carrier reused
10. Remove the Current Limiter (CURL) unit from the back of the carrier. The CURL can be reused. 11. Remove all carrier grounds. 12. Remove carrier A from the cabinet. 13. Repeat for carrier B (H/C only).
Installing the expansion control carrier and the port carrier

To install the expansion control carrier and port carrier: 1. Install the J58890-AF-2 L13 PN expansion control carrier in position A. 2. Install a J58890BB -4 L14 Port carrier in position B. 3. Connect the carrier grounds. 4. Install the CFY1B current limiter (CURL) unit on the back of control carrier A. You can reuse the CURL. 5. Connect the cables to the back of the carriers.
TDM/LAN

Carrier A to D (if equipped) Carrier A to B Carrier B to C (if equipped)
ICC cables from carrier A to B (if required).

Duplex reliability: No ICC cables required High reliability: ICCC and ICCD Critical reliability: ICCA, ICCB, ICCC, and ICCD
AUX cable to carrier A. 9-pin D subminiature plug to P1 connector on each carrier.
6. Install the faceplates on carrier A. 7. Install the faceplates on carrier B.
Issue 2.1 June 2006
787
8. Install the power supplies in carrier A. 9. Install the power supplies in carrier B.

If this PN does not contain an IPSI, install the tone clock and the maintenance circuit packs, as required. Then continue with Installing Expansion Interface circuit packs on page 785. If this PN contains one or two IPSIs, reinstall the IPSIs and the ribbon cables as you did before. For the procedures, see Duplex reliability configuration on page 779 and High-reliability or critical-reliability configuration on page 782. Although you can use ICCs for connectivity (ICCC and ICCD) for consistency, just use the ribbons on the front.

For a connectivity guide, see Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703) and the job aid titled Cabling Guide MCC1 and SCC1 Media Gateway (555-245-771). To connect the CAT 5 cables to the IPSI circuit packs:
Connect the Green CAT5 cable to the IPSI in the A carrier.

Note:
Note: If the existing PPN has a TN570 Expansion Interface circuit packs, you must replace them with a TN570B, vintage 7, or higher circuit pack. If this system is to be used with an Enterprise Survivable Server (ESS), replace the TN570 Expansion Interface circuit packs with a TN570D or later Expansion Interface circuit pack.
To install the Expansion Interface circuit packs: 1. Remove the existing circuit pack and place in an antistatic container. 2. Insert the TN570B, vintage 7, or higher EI circuit packs into the EXPN INTFC slots (A01, B02).
If reusing the EI circuit pack in a CSS: 3. Move the EI/ATM Interface circuit pack from location C02 to location A01. 4. If critical reliability, move the EI/ATM Interface circuit pack from location D02 to location B02. If using ATM EIs: 5. Run the fiber optic cables for the expansion interface circuit packs through the media gateway, using a cable pass-thru kit. 6. Connect the fiber optic cables to the connector on the front of the expansion interface circuit packs. The LED lights up when properly connected.

Note:
Note:
Issue 2.1 June 2006
789
! CAUTION:
CAUTION:
Note:
Note:



Note:
Note:
Issue 2.1 June 2006
791
CLK
S E R V
Note:

fpdlled3 LJK 022502

CLK
fpdlled2 LAO 112905
S E R V

To verify IPSI translations: 1. Type list ipserver-interface. Press Enter. 2. Verify that the ISPI circuit pack(s) are translated. The State of Health - C P E G column shows 0.0.0.0 for each healthy IPSI. If a "1" shows in any position, you must troubleshoot the problem.
fpdlled1 LJK 022502
Issue 2.1 June 2006
793
Tip:
Tip:


Note:
! CAUTION:
CAUTION:






Issue 2.1 June 2006
795

Upgrading firmware





Issue 2.1 June 2006
797
Migrating a DEFINITY ONE/S8100 to an S8700-Series Media Server with IP-PNC

Use these procedures to migrate from an existing DEFINITY ONE/S8100 system to the Avaya S8700-Series Media Servers with an IP-port network connectivity (PNC) configuration. You can migrate only a DEFINITY ONE/S8100 to an Avaya S8710 or S8720 Media Server IP-PNC configuration. To migrate an existing DEFINITY ONE/S8100, you use one TN2312BP IPSI circuit pack to control the port network (PN). You also must replace the processor circuit pack with the IPSI. This migration affects service.

To migrate from DEFINITY platforms:
Install the media servers. If Avaya supplies an Ethernet switch(es) and an uninterruptible power supplies (UPSs), you also must install the switch and the UPS in the 4-post, 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). Replace the tone clock circuit pack with the IPSI circuit pack Move circuit packs to the G650 Media Gateway Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media servers Complete the postmigration administration
Migration paths
Avaya supports the following migrations of a DEFINITY ONE/S8100 to the S8710 or S8720 Media Server IP-PNC configurations include:

DEFINITY Release 6 through 10 MultiVantage Release 1.1 and 1.2 Communication Manager Release 1.0 through Release 1.3
Issue 2.1 June 2006
799
To migrate, in most cases, all the translations must be reentered. However, when migrating from an S8100, the only supported method to move translations is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files through e-mail to the project manager before the migration. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
Prerequisites
You must be complete the following tasks before you start the migration:

Presite checklist on page 801 - Perform these tasks before you go on site. Premigration setup on page 803 - Perform these tasks on site before you start the migration from an existing DEFINITY system. Presite migration checklist on page 807 - Perform these tasks before you go on site. On site migration checklist on page 807 - Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 809 - Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
801

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
803
For more information, see Migration paths on page 799. When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task Determine which adapters and cables you can reuse. Description You cannot reuse the following items:
The C-LAN 259A adapter. You must use adapter for IP Media Processor for 100-Mbps speed. The CAT3 cable that is used with C-LAN. You must use a CAT5 or better for 100-Mbps speed.
CAUTION: You must complete the following seven tasks before you freeze translations or save translations to an MO disk that is used to read translations directly into a media server. Failure to complete the tasks correctly can result in a system that does not function. CAUTION: Be sure to do this step before freezing translations. Verify that the functions of the TN577 Packet Gateway and the TN726B Data Line circuit packs (BX.25 links and mode 2 data modules) were converted to work through the C-LAN circuit packs. Be sure to do this step before freezing translations. Verify that the CMS and INTUITY peripherals and Distributed Communication Service (DCS) links are assigned node names and an Ethernet address. 1 of 3 Note that you cannot reuse the TN577 circuit pack. Use Avaya Terminal Emulator or Avaya Site Administration to perform a list node-names command.
Migration paths
Task CAUTION: Be sure to do this step before freezing translations. Remove all Mode II Data Modules before you change to the S8700-Series Media Server.
Description The S8700-Series Media Server does not support the following data modules:

Be sure to do this step before you freeze translations. The TN750 Announcement circuit packs are not supported in the S8700-Series Media Servers.
The announcements translations migrate to the S8700 Series Media Server. However, you must change the circuit pack locations to the TN2501AP Voice Announcement over LAN (VAL) circuit pack. NOTE: All announcement names must be unique on a TN2501AP VAL circuit pack. The announcement names cannot contain any spaces, blanks, or the following characters:

Type change announcements to change any names and port locations. CAUTION: Be sure to do this step before freezing translations. On the IP Services screen in the Service Type field, remove Alarm1 and Alarm2. 2 of 3 You first might need to change the System Parameters Maintenance screen before you can make any changes to the IP Services screen.
Issue 2.1 June 2006
805
Task CAUTION: Be sure to do this step before freezing translations. On the Trunk Group screen, change the Measured field from measured to none. Be sure to do this step before you freeze translations. Check the Dial Plan screen (or Dial Plan Analysis Table screen depending on the release) for 0 assigned as attd. Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations.
Description This action indicates that trunk group measurement reports are not required. Remember to remeasure trunk groups. Type list trunk-group to get a list of the trunk groups that are "measured" and need to be changed.
If none, check the Attendant Console screens for any buttons with attd-qcalls or attd-qtime btns. Remove these if 0 is not assigned as attd.
Replace the TN775/B/C circuit packs with TN775D circuit packs in any EPN that controls an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS then updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the technical support representative. When you have finished installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, provided you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access still requires an ASG challenge/response. This unique craft password remains valid until a new authentication file is installed.
Verify that you have the appropriate logins and passwords to access the media servers and server complex components.
Copy the translation file to a directory on the Services laptop.
3 of 3
Migration paths


When you are on site, complete the following tasks before you start the migration: Task Verify that the EIA 310D 19-inch (48-cm) open equipment rack is grounded. For S8710 only: Verify that the open, customer-supplied, EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack is properly installed and solidly secured. Description See the job aid titled Approved Grounds (555-245-772). Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on installing the rail, see the rail kit documentation.
1 of 2
Issue 2.1 June 2006
807
Task Verify that you have the correct cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. Verify that you have all necessary equipment onsite.
Description The cables must be labeled and run from the control hardware rack to the port networks. Appropriate connectivity must be provided.
Installing and Configuring the Avaya S8500 Media Server (03-300143) Installing and Configuring the Avaya S8700-Series Media Server (03-300145) 2 of 2
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task S8710: The customer supplies an open, EIA 310D (or equivalent) standard four-post, 19-inch (48-centimeter), equipment rack. Verify that this rack is installed correctly. You might need to move the UPSs and Ethernet switches from the two-post rack. Ensure that you have:

Description Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the documentation that comes with the rail kit.
A Phillips screwdriver Rail kits for a four-post rack for the UPSs Cage nuts to attach the screws to the rack, if necessary At least 2 people to lift the equipment
Migration paths
Task Verify that the cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are labeled and that appropriate connectivity is provided. Verify that you have the license file and that the file includes:
Description The cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs run from the control hardware rack to the port networks.
the Right-To-Use (RTU) feature Applicable hardware parts in the existing system Any hardware that you add as part of the migration
Verify that you have the Avaya authentication file.

For a list of documents that you need to perform the migration, see Resources on page 54. Additional documentation needed. Document Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Description A quick-reference guide that provides physical installation and connection information.
Provides installation instructions for the S8700 and the S8710 Media Servers.
Issue 2.1 June 2006
809
Migration tasks
The information in this is based on the assumption that the media server complex is installed, configured, and operational. This section describes how to change an existing processor port network (PPN) to a port network (PN).
! CAUTION:
CAUTION:

Note:

Migration tasks:

Accessing the media server maintenance web interface on page 814 Checking system status on page 814 Verifying the license file on page 814 Restoring data for a migration (S8710 only) on page 815 Adding IPSI translations to Communication Manager on page 817 Adding IPSI information on page 817
Migration tasks
Setting IPSI duplication (high-reliability critical-reliability only) on page 818 Setting the alarm activation level on page 818 Backing up translations on page 818 Verifying hardware on page 819 Changing the control cabinet to a port network on page 819 Turning off the power to the control cabinet on page 820 Replacing the processor circuit pack on page 820 Replacing the TN799C C-LAN circuit pack on page 821 Installing TN771 Maintenance/Test circuit pack on page 821 Connecting to the media server on page 822

Issue 2.1 June 2006
811
! CAUTION:
CAUTION:


Note:

To record node names and IP addresses: 1. Note the node names and the IP addresses that are assigned to the TN2302AP IP Media Processor and the TN799C/DP C-LAN circuit packs. Ensure that these names and addresses are the same after the migration. Note: If the existing system has TN799C C-LAN circuit packs, you must replace these circuit packs with TN799DP circuit packs.
Note:
2. To get the node names for the TN2302AP IP Media Processor and TN799C/DP C-LAN circuit packs, type display ip-interfaces. Press Enter. 3. To get the IP addresses that match the node names, type list node-names. Press Enter. 4. Record the information for use after the migration.
Saving translations
Record the IP settings assigned to the processor as they can be used for the media server. Verify against the filled-out Electronic Preinstallation Worksheet. The following administration is done on the Services laptop connected to the processor circuit pack using telnet. To record the IP settings: 1. Select Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6. Press Enter to access the media server. 3. Log in as lucent3 to get to the LAC prompt. 4. Type bash. Press Enter to start a BASH session. 5. Type setip. Press Enter to show the current list of IP settings. You might see the following information:

cust: IPaddress, subnet mask, gateway dns: server name, domain name, 2 DNS server IP addresses wins: 2 WINS server IP addresses ras: 1 remote access server IP address
6. Write down this information, exactly as it displays. You must record this information exactly as it appears here. You cannot miss any periods, commas, or other punctuation marks. Record information in lowercase or uppercase as displayed.
Issue 2.1 June 2006
813
This section describes how to migrate translation files from the existing system to the S8700-Series Media Server.










To restore the translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file might be at the top of the list.
Issue 2.1 June 2006
815
4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file, scroll down and click Review Status to see the results of the restore. When done, the screen shows the message Restore is finished. If the restore process fails, the system displays an error message that states the reason for the failure and the translation file is not restored. Resolve the reason for the failure and restart the process.




! CAUTION:
CAUTION:
Note:

To add IPSI information: 1. Type add ipserver-interface PNnumber where PNnumber is the port network number. Press Enter. 2. When you use static addressing, in the Host field, type in the IP address for the IPSI in the port network that is listed in the Location field.
Issue 2.1 June 2006
817
3. Verify that all the other fields are populated. 4. Press Enter to put the changes into effect. 5. Repeat Steps 1 through 5 for each port network.


Migration tasks
Migration tasks
Perform the following tasks to convert a processor port network to a port network (CMC). Note: If you want to make the system high reliability, you cannot reuse the Compact Modular Cabinets (CMCs). You must install Avaya G650 Media Gateways and move all the circuit packs to the G650s. Note: You must install the new Communication Manager license file on the media server before you make the change or the system will not run.
Note:
Note:
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: Customers who currently use the Audix feature on the S8100 must purchase a separate Audix system. The TN795 or the TN2314 Processor circuit pack that contains the Audix feature is replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not contain the Audix feature. You must return the existing processor circuit pack to Avaya. Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Note:
Note:

To change the control cabinet to a port network, you must:
Replace the TN795 or TN2314 Processor circuit pack with a TN2312BP Internal Protocol Server Interface (IPSI) circuit pack. Connect a CAT5 straight-through cable from the IPSI to the media server through the network of the customer.
Issue 2.1 June 2006
819
Note:
Note: If replacing a TN795 Processor circuit pack, you might not need the TN744D/E Call Classifier-Detector circuit pack. The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack has call classifier functionality. However, increased voice and data traffic might require the TN744D/E Call Classifier-Detector circuit pack. Note: If you have a TN799C or earlier CLAN circuit pack, you must replace the TN799 circuit pack with a TN799DP CLAN circuit pack.
Note:

! CAUTION:
CAUTION:
! DANGER:
DANGER:

To replace the processor circuit pack: 1. Remove the entire processor circuit pack and place it in an antistatic carrier or bag. You might need to reinstall this circuit pack if you must stop the migration. 2. Remove the octopus cable from the connector that is associated with slot 2 on the connector panel. 3. Install the IPSI adapter to the connector that is associated with slot 2 on the connector panel.
Migration tasks
4. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 5. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 6. Attach the new label above the circuit pack slots.
Note:


If the cabinet does not have a TN2302AP IP Media Processor, you must install one in slot 10. For more information, see the Adding New Hardware book, Install and Administer IP Connectivity Hardware section.
Issue 2.1 June 2006
821

Note:
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open.
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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:
Note:

Issue 2.1 June 2006
823

CLK
2 3
cadlipsi KLC 031502
Note:

You 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: 1. Click Start > Run to open the Run dialog box. 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:


Note:
Note:
Issue 2.1 June 2006
825



Note:
!
Important:
Resetting the IPSI

Note:
Note:
Issue 2.1 June 2006
827
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502


Note:
! CAUTION:
CAUTION:


Issue 2.1 June 2006
829





Upgrading firmware

Issue 2.1 June 2006
831




Migrating an Avaya IP600/S8100 to an S8700-Series Media Server with IP-PNC

Use these procedures to migrate from an existing Avaya IP600/S8100 IP-port network connectivity (PNC) system to the Avaya S8700-Series Media Servers with an IP-PNC configuration. You can migrate an IP600/S8100 only to an Avaya S8710 or S8720 IP-PNC configuration. When you migrate an existing Avaya IP600/S8100, you use one TN2312BP IPSI circuit pack to control the port network (PN). You also replace the processor circuit pack with the IPSI in the cabinet in the A position. This migration affects service.

To migrate from DEFINITY platforms you must:
Install the media server. If Avaya supplies an Ethernet switch and an uninterruptible power supply (UPS), you also must install the switch and the UPS in the 19-inch rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703). Replace the tone clock circuit pack with the IPSI circuit pack Connect the media servers to the media gateways Enable control of the IPSIs and switch control to the media servers Complete the postmigration administration
Migration paths
DEFINITY IP600/S8100 and their releases that can be migrated to the S8710 or S8720 Media Server IP-PNC configurations include:

DEFINITY Release 9 through 10 MultiVantage Release 1.1 and 1.2 Communication Manager Release 1.0 through Release 1.3
Issue 2.1 June 2006
833
To migrate, in most cases, you must reenter all the translations. However, when you migrate from an S8100, the only supported method to move translations is to: 1. Freeze the translations. 2. Send the translations to the Avaya Software Technical Support (STS) group. STS then returns the translation reports and translation files through e-mail to the project manager before the migration. For the forms and more information, contact the STS scheduling desk at 720-444-9418.
Prerequisites
You must be complete the following tasks before you start the migration:

Presite checklist on page 835. Perform these tasks before you go on site. Presite migration checklist on page 841. Perform these tasks before you go on site. On site migration checklist on page 841. Perform these tasks on site before you start the migration. Documentation checklist for migrations on page 843. Have these documents ready to use while you perform the migration.
Migration paths
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
835

Migration paths
Additional tasks
Premigration setup

Issue 2.1 June 2006
837
For more information, see Migration paths on page 833. When you migrate from a DEFINITY system, you must complete the following additional tasks before you start the migration: Task Determine which adapters and cables you can reuse. Description You cannot reuse the following items:
The C-LAN 259A adapter. You must use adapter for IP Media Processor for 100-Mbps speed. The CAT3 cable that is used with C-LAN. You must use a CAT5 or better cable for 100-Mbps speed.
CAUTION: If you are going to use the MOST Tool, the following 8 tasks must be done before freezing translations or saving translations to an MO disk that will be used to read translations directly into a media server. If you want to use STS for translation conversion, see Replace any TN775/B/C maintenance circuit packs. on page 840. CAUTION: Be sure to do this step before freezing translations. Remove all Mode II Data Modules before you change to the S8700-Series Media Server. The S8700-Series Media Server do not support the following data modules:

System Ports PDMs (7400/8400 Data Modules) PktGateway Pkt Data Dataline Modem Pool System CDR PDMs System Features Printer PDMs 1 of 3
Migration paths
Task Be sure to do this step before you freeze translations. The TN750 Announcement circuit packs are not supported in the S8700-Series Media Servers.
Description The announcements translations migrate to the S8700 Series Media Server. However, you must change the circuit pack locations to the TN2501AP Voice Announcement over LAN (VAL) circuit pack. NOTE: All announcement names must be unique on a TN2501AP VAL circuit pack. The announcement names cannot contain any spaces, blanks, or the following characters:

Type change announcements to change any names and port locations. CAUTION: Be sure to do this step before freezing translations. On the IP Services screen in the Service Type field, remove Alarm1 and Alarm2. CAUTION: Be sure to do this step before freezing translations. On the Trunk Group screen, change the Measured field from measured to none. This action indicates that trunk group measurement reports are not required. Remember to re-measure trunk groups. To get a list of the trunk groups that are "measured" and need to be changed, type list trunk-group. You first might need to change the System Parameters Maintenance screen before you can make any changes to the IP Services screen.
2 of 3
Issue 2.1 June 2006
839
Task CAUTION: Be sure to do this step before freezing translations. Check the Dial Plan screen (or the Dial Plan Analysis Table screen depending on the release) for 0 assigned as attd. Replace any TN775/B/C maintenance circuit packs. About 2 weeks before the migration, freeze the translations.
Description If there are none, check the Attendant Console screens for any buttons with attd-qcalls or attd-qtime btns. Remove these if 0 is not assigned as attd.
Replace the TN775/B/C circuit packs with TN775D circuit packs in any EPN that contains an IPSI. For more information on where and how to send the translations, contact the STS scheduling desk at 720-444-9418. STS then updates the translations to the latest version. This process can take 2 weeks. STS returns the translation reports and translation files to the project manager by e-mail who sends them to the field technician. When you have finished installing the authentication file, Communication Manager has a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, provided you access the media server through the Services port. You do not need an ASG challenge/response to log in this way, even though every other means of craft access still requires an ASG challenge/response. This unique craft password remains valid a new authentication file is installed.
Verify that you have the appropriate logins and the passwords to access the media servers and the server complex components.
Copy the translation file to a directory on the Services laptop.
3 of 3
Migration paths


When you are on site, complete the following tasks before you start the migration: Task Verify that the EIA 310D 19-inch (48-cm) open equipment rack is grounded. For S8710 only: Verify that the open, customer-supplied, EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack is installed correctly and solidly secured. Description See the job aid titled Approved Grounds (555-245-772). Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on installing the rail, see the rail kit documentation.
1 of 2
Issue 2.1 June 2006
841
Task Verify the correct cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. Verify that you have all necessary equipment onsite.
Description The cables must be labeled and run from the control hardware rack to the port networks. Appropriate connectivity must be provided. For the list of required hardware, see Installing and Configuring the Avaya S8700-Series Media Server (03-300145). 2 of 2
When you are on site for a migration from a DEFINITY system, complete the following additional tasks before you start the migration: Task The customer supplies an EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack is installed correctly and solidly secured. Verify that cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs are labeled and that appropriate connectivity is provided. Verify that you have the license file and that the file includes the licensed features. Verify that you have the Avaya authentication file. Description Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on how to install the rail, see the documentation that comes with the rail kit. The TN2312BP Internet Protocol Server Interface (IPSI) circuit packs runs from the control hardware rack to the port networks.
Migration paths

Issue 2.1 June 2006
843

Migration tasks
! CAUTION:
CAUTION:
This procedure affects service. When the processor port network (PPN) is turned off, the system stops all calls. Service returns when the media server takes control of the IPSIs.

Turn off the processor gracefully - preconversion administration Replace the processor circuit pack or tone clock circuit pack with an IPSI circuit pack Replace the WP cables with twisted pair cables
Migration tasks
Connect the IPSI circuit pack to the Ethernet switch on the network of the customer Assign an IP address to the IPSI circuit pack Note: You must install the new Communication Manager license file on the media server before you make the change or the system will not run.
Note:
Perform the following tasks to convert a processor port network to a port network (IP600). Premigration administration:

Migration tasks:

Accessing the media server maintenance web interface on page 849 Checking system status on page 849 Verifying the license file on page 849 Restoring data for a migration (S8710 only) on page 850 Adding IPSI translations to Communication Manager on page 852 Adding IPSI information on page 852 Setting IPSI duplication (high-reliability critical-reliability only) on page 853 Setting the alarm activation level on page 853 Backing up translations on page 853 Verifying hardware on page 854 Changing the IP600 control chassis to a port network on page 854 Turning off the control chassis on page 855 Replacing I/O cables on page 855 Replacing the processor circuit pack on page 858 Replacing the TN799C C-LAN circuit pack on page 858 Installing TN771 Maintenance/Test circuit pack on page 859 Connecting to the media server on page 859
Accessing the server command line interface with SSH protocol on page 859
Issue 2.1 June 2006
845
Using static addressing on page 861 Clearing the ARP cache on the laptop computer on page 862 Logging in to the IPSI on page 862 Setting the control interface on page 863 Setting the VLAN and diffserv parameters on page 864 Resetting the IPSI on page 864 Verifying IPSI translations on page 865 Verifying IPSI connectivity on page 866 Enabling control of the IPSI on page 866 Verifying the customer data on page 866 Verifying circuit pack locations on page 867 Verifying circuit pack insertion on page 867 Verifying the IP addresses on page 867 Checking the link status on page 868 Upgrading firmware on page 868 Testing the installation on page 869 Busying out previously busied out trunks on page 869 Troubleshooting the migration on page 869 Returning replaced equipment on page 869
This migration affects service because you must turn off the IP600 chassis to replace the processor. Before you turn off the chassis, you must perform the following premigration administration.
! CAUTION:
CAUTION:


Note:

Note:
Issue 2.1 June 2006
847
Saving translations
You must view and record the IP settings that are assigned to the processor and use these same settings for the media server. Verify against the filled-out Electronic Preinstallation Worksheet. To view these settings, perform the following administration on the Services laptop that is connected to the processor circuit pack by way of telnet. To record the IP settings: 1. Select Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6 and press Enter. 3. Log in as lucent3 to get to the LAC prompt. 4. Type bash and press Enter to start a BASH session. 5. Type setip and press Enter to show the current list of IP settings. You should see the following information:

6. Record this information exactly as it displays.
!
Important:
Important: Include any periods, commas, or other punctuation marks. Record this information in lowercase or uppercase as the information displays.
This section describes how to migrate translation files from the existing system to the S8710 or S8720 Media Server.




Issue 2.1 June 2006
849






To restore the translation files: 1. Under Data Backup/Restore, click View/Restore Data. 2. Select Local Directory and click View. The field automatically shows the default directory. 3. Select the first file. The latest file might be at the top of the list.
4. Select Force restore if server name mismatch and Force restore if backup version mismatch. 5. Click Restore to restore the translation files. 6. Click Restore Status. 7. Select the first file, scroll down and click Review Status to see the results of the restore. When done, the screen shows the message Restore is finished. If the restore process fails, the system displays an error message that states the reason for the failure and the translation file is not restored. Resolve the reason for the failure and restart the process.



Issue 2.1 June 2006
851

! CAUTION:
CAUTION:
Note:

To add IPSI information: 1. Type add ipserver-interface PNnumber where PNnumber is the port network number. Press Enter. 2. When you use static addressing, in the Host field, type in the IP address for the IPSI in the port network that is listed in the Location field. 3. Verify that all the other fields are populated.
4. Press Enter to put the changes into effect. 5. Repeat Steps 1 through 5 for each port network.


Issue 2.1 June 2006
853
Migration tasks
Perform the following tasks to change a processor port network to a port network (IP600).
Verifying hardware
Ensure that you have the conversion specific hardware on hand. Note: If customers currently are using the Audix feature on the S8100 Media Server, they need to purchase a separate Audix system. The TN795 or TN2314 Processor circuit pack containing the Audix feature is being replaced with a TN2312BP Internet Protocol Server Interface (IPSI) circuit pack that does not have that feature. The existing processor circuit pack must be returned to Avaya. Note: Customers also must add an ED-1E568-70G1 DEFINITY Audix Slim board and a TN2501AP Voice Announcement over LAN (VAL) circuit pack for announcements.
Note:
Note:


Replace the existing straight-wire WP cables, if present, with new twisted-pair I/O cables. Replace the processor circuit pack with a TN2312BP IP Server Interface (IPSI) circuit pack. Connect a CAT5 straight-through cable from the IPSI to the media server through the network of the customer. Note: If you replace a TN795 Processor circuit pack, you might not need the TN744D/E Call Classifier-Detector circuit pack. The TN2312BP IPSI circuit pack has call classifier functionality. However, increased voice and data traffic can require the TN744D/E Call Classifier-Detector circuit pack. Note: If you have a TN799C or earlier CLAN circuit pack, you must replace the TN799 circuit pack with a TN799DP CLAN circuit pack.
Note:
Note:
Migration tasks
Note:
Turning off the control chassis

To turn off the control chassis:
! CAUTION:
CAUTION:
Ensure that you have completed the premigration administration. For more information, see Premigration administration on page 846. 1. Press and hold the shutdown button on the on the faceplate of the processor until the shutdown process starts. Ensure that you see the green light. This light indicates that the system is shut down.
! DANGER:
DANGER:
The latch on the power supply acts as the DC power switch and removes only DC power from the backplane. To remove the AC power from the chassis, pull the AC power cord from the back of the chassis. 2. To turn off the chassis, unplug the power cord from the back of the chassis.

On older MCC, SCC, and G600 cabinets you must replace the existing I/O cables (WP-90753, LI), which connect the backplane to the rear connector panel, with twisted pair I/O cables. The existing I/O cables have straight, not twisted, wires. They may be mostly white with two red, or multi-colored. If the cables have multi-colored, tightly twisted wires, no replacement is necessary. To order the DEFINITY kit with twisted pair I/O cables, use comcode 700234032.
! CAUTION:
CAUTION:
Turn off power to the carrier or media gateway being serviced. Failure to turn off the power can result in electric shock.
Issue 2.1 June 2006
855
! CAUTION:
CAUTION:
When adding or replacing any hardware and associated cables and adapters, be sure to ground yourself against electrostatic discharge (ESD) by wearing a grounded wrist strap. Failure to follow ESD procedures can result in system damage or service disruption.
To replace the existing I/O cables: 1. For the G600 Media Gateway, you must remove the fan assembly to access the cables. Loosen the thumb screws on the fan assembly and pull it straight out as shown in G600 Media Gateway fan assembly removal on page 857. Leave the fan assembly off until all the wires are installed. 2. Note the orientation of the existing 10 cables. The existing I/O cables may be white and red or multicolored. They are not twisted. 3. Remove the nontwisted pair of existing I/O cables from the backplane and the connector panel slots. 4. In their place install the 10 tight-twisted pair I/O cables onto the backplane, according to the proper orientation shown in Proper orientation for the twisted pair I/O cables on page 857. Observe the white outline printed on the backplane for the location of each connector. 5. When viewed from the "wiring" side of the twin connectors (that is, while plugging them into the backplane) and with the connectors oriented properly for plug-in, they should look like Proper orientation for the twisted pair I/O cables on page 857. The circled pin locations are No-Connects; that is, they have no wires in them. At the top there is an orange-black pair on the right and a violet-brown pair on the left. The 50-position metal shell D connectors should be installed into the connector panel with the longer side of the D (pins 125) toward the right when viewed from the rear of the media gateway. 6. For the G600 Media Gateway, replace the fan unit if no other media gateways are to be installed. If you are adding more media gateways to the rack, leave the fan units off until all of the TDM cables are installed.
Migration tasks
Figure 56: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
2 1
iodspair KLC 072602
Figure notes: 1. Top 2. No connects; no wires 3. Violet-brown 4. Orange-black 5. Bottom
Issue 2.1 June 2006
857

To replace the processor circuit pack: 1. Remove the entire processor circuit pack. 2. Place the circuit pack in an antistatic carrier or bag. You want the circuit pack intact if you need to back out of the migration. 3. Remove the octopus cable from the connector that is associated with slot 2 on the backplane. 4. Install the IPSI adapter to the connector that is associated with slot 2 on the backplane. 5. Install the maintenance cable onto the 9-pin D-sub connector on the adapter. This cable is for emergency transfer and "auxsig" signal. Note: The TN2312BP Internet Protocol Server Interface (IPSI) circuit pack takes only one slot. 6. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit pack into slot 2. 7. Attach the new label above the circuit pack slots.
Note:



Note:
Issue 2.1 June 2006
859
Note:
! CAUTION:
CAUTION:
Note:
Note:


CLK
2 3
cadlipsi KLC 031502
Note:
Issue 2.1 June 2006
861



Note:
Note:

Issue 2.1 June 2006
863


Note:
!
Important:
Resetting the IPSI

Note:
Note:
CLK
S E R V
Note:

Tip:
fpdlled1 LJK 022502
Issue 2.1 June 2006
865


Note:
! CAUTION:
CAUTION:



To verify circuit pack locations: 1. Type list cabinet. Press Enter to view all the "cabinets." Verify that the cabinet number assigned to the converted cabinets shows. 2. Type display cabinet number, where number is the cabinet number of the converted cabinet. Press Enter. Under Carrier Description, Carrier Type verify that the number of "carriers" in use matches the number of media gateways in the rack (G600 or G650).


Issue 2.1 June 2006
867

Upgrading firmware





Issue 2.1 June 2006
869
Migrating an S8500 Media Server to an S8710 Media Server

Use these procedures to migrate an existing S8500 Media Server to an S8710 Media Server configuration. In this migration, you can configure the S8710 Media Servers but reuse the translations from the S8500 Media Server. This migration requires a new Communication Manager license file. With this migration, you also upgrade to Communication Manager Release 3.0. If the configuration includes local survivable processors (LSPs), you must upgrade the LSPs before the S8710 Media Server takes control. This migration affects service.

Install the media servers in a 19-inch, 4-post rack. For more information, see Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). You also must install a second uninterruptible power supply (UPS). Connect the duplication cables.
Prerequisites
Before you start the software migration and the media server configuration, you must verify that:
The customer has a local area network (LAN) that is set up and running and a network administrator who is available to assist you on the date of the migration. You have the IP addresses and the unique names for the media servers. You have a new license file and a password file. The Services laptop has the correct hardware and software. - Windows 2000 or Windows XP operating system - 32-MB of RAM - 40-MB of available disk space
Issue 2.1 June 2006
871
- An RS-232 port connector - A network interface card (NIC) with a 10/100BaseT Ethernet interface - A 10/100 BaseT Ethernet, category 5 (or better), cross-connect cable with an RJ45 connector on each end (MDI to MDI-X) - A CD-ROM drive

You have the current translations available for download by ProVision. You have a filled-out Electronic Pre-Installation Worksheet (EPW). For the blank form, see the Avaya Installation Wizard Web site (http://support.avaya.com/avayaiw). The EPW provides: - An IP addresses - A product ID - An Avaya Services telephone number for remote access over modem - An Avaya Services IP address for alarms through the network
You have the current firmware available. Firmware for the IPSI, the C-LAN, the MedPro, and the VAL circuit packs are part of the software CD-ROM. For the latest software and firmware, see the Avaya Support Web site http://support.avaya.com. Click Find Documentation and Downloads by Product Name. You have the login IDs and the passwords to access the S8500 and the S8710 Media Servers and the server complex components. The password includes the unique service password for that equipment of the customer. To obtain the password for a specific media server, call ASG Conversant at 9-800-248-1234 or 1-720-444-5557. You must have the IL, FL, or product ID to get the password. To log in through the Services port as craft after you install the Avaya authentication file, use this password. This password does not require an ASG challenge or response.
Migration tasks
Migration tasks
Perform these tasks to migrate an S8500 Media Server to an S8710 Media Server. Premigration administration:

Verifying hardware on page 874 Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used) on page 874 Upgrading firmware on page 875 Upgrading software on the local survivable processors on page 875
On the S8500 Media Server:

Clearing the ARP cache on the laptop computer on page 876 Connecting to the media server on page 877 Starting a SAT session on page 877 Checking for translation corruption on page 877 Saving translations on page 877 Backing up the translation files on page 878
On the active S8710 Media Server:

Turning on both media servers on page 878 Accessing the media server on page 878 Setting up a Telnet session on page 879 Installing Communication Manager on page 880 Accessing the server command line interface with SSH protocol on page 882 Accessing the media server on page 883 Configuring both media servers using AIW on page 883
On the S8710 Media Servers:

Connecting customer LAN cables on page 884 Restoring the translations on page 884 Pretesting the system on page 885
Disconnecting the S8500 Media Server from the customer network on page 886
On the S8710 Media Servers:
Connecting the S8710 Media Servers to the control network on page 886
Issue 2.1 June 2006
873

Shutting down the S8500 Media Server on page 887 Disconnecting the cables on page 888
! CAUTION:
CAUTION:
The licensing of the platform and port network connectivity attributes for the S8700-series Media Server can be complex. See Caution about platform/PNC license settings for the S8700-series Media Server on page 314 and License and Avaya authentication files on page 313.
Verifying hardware
Ensure that you have the conversion specific hardware on hand. You can reuse some of the equipment and cables when you migrate from an S8500 Media Server to an S8710 or S8720 Media Server. However, you need new equipment to complete the migration.
Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used)
Note:
Note: If the customer has no G150, G350 or G700 Media Gateways or no local survivable processors (LSPs), skip these tasks and go to On the active S8700 Media Server on page 902.
If the configuration is using G150, G350, or G700 Media Gateways and media modules and newer firmware exists for them, you must upgrade the firmware on them first. If the media server is the primary controller for a G700 Media Gateway equipped with an LSP, you must upgrade the software on the LSPs before you transfer control to the S8710 Media Servers. The correct order is: 1. Upgrade media gateway firmware to latest version 2. Upgrade media modules firmware to latest version 3. Upgrade the media server software to latest version if using LSPs 4. Transfer control to the S8710 Media Server.
Upgrading firmware

Upgrading software on the local survivable processors

For more information on the software upgrade process, see Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100). Note: Although the LSPs remain registered with the primary controller, the LSPs do not accept translations if LSPs are running an older version of the software than the software that is on the primary controller.
Note:
You can use the Upgrade Tool to upgrade the firmware on the G700 Media Gateway. For more information on how to use the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheets (555-245-757). You might be able to use the Upgrade Tool to upgrade the software on the S8300 Media Server, depending on the version of the media server. For more information, see Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100).
Issue 2.1 June 2006
875
! CAUTION:
CAUTION:
You must stop call processing on the LSPs during the migration process. You can stop call processing on the active media server. If you do not stop call processing on the LSPs, all calls to the LSPs will be dropped.
Migration tasks
On the S8500 Media Server



To connect to the media server: 1. Use a cross-connect CAT5 cable to connect the laptop to the Services port (2) on the back of the media server.


Saving translations
To save translations: 1. Perform one of the following actions:

If the system includes LSPs, type save translation lsp. Press Enter. If the system does not include LSPs, type save translation. Press Enter.
Issue 2.1 June 2006
877
Backing up the translation files

To back up the translation files from the Web interface: 1. Connect the cord of the compact flash disk into one of the USB ports on the front of the media server. 2. Insert a formatted 128-MB compact flash disk into the bottom slot of the drive. 3. On the menu, click Backup/Restore > Backup Now. 4. Select Avaya Call Processing (ACP) Translations and Local PC and select the number of data sets to retain as the backup method. The LocalPC is the compact flash. 5. Click Start Backup to start the backup process. 6. Click Backup History to view the progress of the backup process. 7. When you finish, disconnect the Services laptop from the media server.
On active S8710 Media Server

Turning on both media servers
To turn on the media servers: 1. Connect the AC power cord to both media servers and to both UPSs. 2. Push the power button on the media server. 3. Place the CD-ROM with Communication Manager in the CD-ROM drive on the media server. The CD must be installed and the media server must boot from the CD. After pressing the power button on the media server, wait 10 seconds and press the eject button on the CD tray. The tray opens, insert the CD, and close the tray. Allow the media server to finish booting.

To access the media server: 1. Clear the ARP cache from the laptop if necessary. For more information, Clearing the ARP cache on the laptop computer on page 876 and return here.)
2. Use a cross-connect cable to connect the laptop to the Services port (2) on the back of the media server. 3. Wait at least 3 minutes after you turn on the media server before you start a Telnet session to access the information on the CD-ROM.
Setting up a Telnet session

To set up a Telnet session: Note: You might need a Telnet session to perform some of the tasks in this migration. Note: Use a telnet session to access the information on the CD-ROM.
Note:
Note:
You can set the Microsoft Telnet application to send a carriage return (CR) and a line feed (LF) whenever you press Enter. The installation program sees this as two key presses. If you are running Windows 2000 or Windows XP, you must correct this before you copy the Remaster Program to the hard disk. 1. Click Start > Run to open the Run dialog box. 2. Type telnet. Press Enter to open a Microsoft Telnet session. 3. Type display. Press Enter to see the current settings. 4. Perform one of the following actions: If the system displays the message Sending only CR, close the dialog box. If the system displays the message Sending both CR & LF, continue with step 5. 5. Type unset crlf. Press Enter. 6. Type display. Press Enter to verify that the settings changed. The system displays the message Sending only CR. 7. Close the dialog box.
Issue 2.1 June 2006
879

Note:
These processes can take up to 20 minutes. When the media server is ready to reboot, the CD-ROM drive drawer opens. Remove the CD-ROM from the drive at this time. The reboot can take up to 3 minutes. The Telnet session ends automatically. 5. Disconnect from the active media server and connect to the other media server. 6. Repeat Turning on both media servers on page 878 through Installing Communication Manager on page 880.
Issue 2.1 June 2006
881

Note:
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html.
Note:
8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:

To access the media server: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft or dadmin. 3. Log on to the Maintenance Web Interface. For more information, see Accessing the media server on page 878 and return here.
Configuring both media servers using AIW

Use the Avaya Installation Wizard (AIW) on each media server to:

Configure the media server Install the new license file and the software updates
Use one of the following methods to enter the date from the filled-out Electronic Preinstallation Worksheet (EPW):

Import the data from the EPW. Type the information manually.
Issue 2.1 June 2006
883
To access the Installation Wizard: 1. Open the browser with the Home page. 2. Click Launch Avaya Installation Wizard. 3. Follow the prompts to configure this server as "active." For more information, click Help on any page. Configure this server as "active."
On the S8710 Media Servers

Connecting customer LAN cables
To connect the LAN cables for the customer: 1. Connect the CAT5 cables from both S8710 Media Servers (Ethernet 4) to the customer LAN.
Restoring the translations

To restore the translations to the active media server: 1. Connect the compact flash reader cord to either USB port on the back of the media server. 2. Insert the compact flash card with the translations into the bottom slot of the drive. This card is the card that you use in Backing up the translation files on page 878. 3. Under Data Backup/Restore, click View/Restore Data. 4. Select Local PC Card. Note: If the laptop is connected to the standby media server, SSH across the duplication link to the active media server. The SSH address for server 1 is 192.11.13.13. The SSH address for server 2 is 192.11.13.14. Ensure that you copy the translations to the active media server. 5. Click View. Note: For the next step, the correction translation file is the most recent file. 6. Select the correct translation file and both Force options.
Note:
Note:
7. Click Restore. 8. Click Restore History and select the desired file that you want to restore. 9. Click Status to view the Restore status. When the restoration is complete, the system displays the following message: Backup: 0: Restore of <filepath/filename> is completed successfully.
Pretesting the system

To pretest the system: Note: Do not connect to the control network yet. 1. Install the license file and the authorization file. 2. Type reset system 4. Press Enter. 3. Type list station. Press Enter. Verify that the stations on this server are the same as the stations that were on the S8500 Media Server. 4. Type save translation. Press Enter. 5. Perform the necessary administration. For example, use the add duplication administration command. 6. When you finish, type save translation. Press Enter. 7. If the browser is not running, open the browser with the Home page. Note: Before you perform the next step, wait until the Status Summary informs you that the standby server memory is refreshed. 8. Select Server > Status Summary. The system displays the Status Summary window. 9. Verify the following settings:

Note:
Note:
The Duplicated field is set to yes The Standby Busied field is set to no The Standby Refreshed field is set to yes The Standby Shadowing field is set to on The Duplication Link field is up
Issue 2.1 June 2006
885
10. Log in to both media servers from anywhere on the customer LAN. This action verifies that connectivity exists and that the customer can log in to perform administration or other tasks. 11. Use the Web browser to select Server > Interchange Servers to interchange the media servers. Note: Ensure that you are connected to the active media server before you continue. The system is ready to take over call processing. 12. Connect both IPSI control network B cables from both media servers to the Ethernet switch for the standby IPSIs. These cables are the green CAT5 cables.
Note:

Disconnecting the S8500 Media Server from the customer network
Note:
Note: This procedure stops call processing.
To disconnect the S8500 Media Server from the customer network:
Remove the control network A cable from the S8500 Media Server.

Connecting the S8710 Media Servers to the control network
To connect the S8710 Media Servers to the control network: 1. Connect both S8710 Media Server IPSI control network A cables to the Ethernet switches. These cables are the green CAT5 cables.
Note:
Note: The IPSIs and the port networks reset automatically. The approximate out-of-service time is 5 minutes and then call processing might be on the S8710 Media Servers. 2. After approximately 30 minutes, verify that the system is functioning satisfactorily. Check and clear alarms. If everything is satisfactory, continue with Shutting down the S8500 Media Server on page 887.

Shutting down the S8500 Media Server
To shut down the S8500 Media Server:
! CAUTION:
CAUTION:
Do not unplug a functioning server unless you first stop all processes. If you unplug a functioning server but do not stop all processes first, you can corrupt the hard disk drive. 1. Under Server, click Shutdown Server. a. Clear Restart Server after Shutdown. b. Select Delayed shutdown 2. Click Shutdown.
! CAUTION:
CAUTION:
Do not hold down the power button for more than a second. If you hold the button down too long, the media server to reboots. 3. Press and release the power-control button on the front of the server. The internal fan shuts off. 4. Disconnect any remaining cables from the media server.
Issue 2.1 June 2006
887
Disconnecting the cables

To disconnect the cables: 1. Disconnect the laptop from the Services port. 2. Disconnect the power cord from the UPS. 3. Disconnect the power cord from the RSA. 4. Disconnect the modem from the RS-232 port on the SAMP or RSA card. 5. Disconnect the LAN connection (if used) from the Ethernet port on the SAMP or RSA card. 6. Disconnect the cable from the Ethernet port on the dual network interface card (NIC) (if used).
Basic Migration Steps
Migrating from an S8700 Media Server to an S8710 Media Server

Use these procedures to migrate an existing S8700 Media Server on Avaya Communication Manager Release 1.x through 2.x to an S8710 Media Server on Communication Manager Release 3.0. If the media server is on Communication Manager Release 1.x, you must upgrade the media server to Communication Manager Release 1.3.2 before the migration. This migration requires a new Communication Manager license file and an Avaya authentication file. In this migration, you reuse the system files and the translation files from the S8700 Media Servers. These migrations include the following configurations:

fiber-port network connectivity (PNC) to fiber-PNC IP-PNC to IP-PNC
With this migration, you also upgrade to Communication Manager Release 3.0 local survivable processors (LSPs). You must upgrade the LSPs before the S8710 Media Server takes control.

Note:
Note: Whenever you connect to a media server, perform Clearing the ARP cache on the laptop computer on page 902 to avoid temporary internet files that could cause confusion.

Upgrade the G350 or the G700 Media Gateways and the LSPs if LSPs are used. If Communication Manager Release 1.2 or 1.3 is installed, install the preupgrade update (patch). If Communication Manager Release 1.0 or 1.1 is installed, upgrade to Communication Manager Release 1.3. Back up the Linux migration upgrade set. This file set is the only file set that you will need. Install the Avaya S8710 Media Servers in either: - A 19-inch, 4-post rack as described in the Quick Start for Hardware Installation: Avaya S8700-Series Media Server (555-245-703). - A pull-out shelf that is attached to the existing 2-post rack.
Install the current software on the S8710 Media Servers.
Issue 2.1 June 2006
889
Restore the Linux migration upgrade set from the customer network to both S8710 Media Servers when you use the Linux Migration (Backup/Restore) link. Note: If you move Ethernet switches and UPSs to the four-post rack, move this equipment before the cutover.
Note:
Connect the control network Ethernet cables to the new S8710 Media Servers. Connect the standby media server first. Connect the duplication cables after restoring the files to the second media server. Complete the postmigration administration.
Prerequisites

Presite checklist on page 891. Perform these tasks before you go on site. Additional tasks on page 893. Perform these tasks on site before you start the migration from an existing DEFINITY system. Presite migration checklist on page 895. Perform these tasks before you go on site. On site migration checklist on page 896. Perform these are tasks on site before you start the migration. Documentation checklist for migrations on page 897. Have these documents ready to use while you perform the migration.
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
891

Additional tasks
Issue 2.1 June 2006
893
Premigration setup
Note: The premigration team must have completed the following tasks. If these tasks were not completed, do not continue with the migration.
Note:
When you are migrating from a DEFINITY system, complete the following additional tasks before starting the migration: Task Remove all Mode II Data Modules before you change the S8710 Media Server. Description The S8710 does not support the following data modules:

On the IP Services screen in the Service Type field, remove Alarm1 and Alarm2. On the Trunk Group screen, change the Measured field from measured to none.
You first might need to change the System Parameters Maintenance screen before you can make any changes to the IP Services screen. This action indicates that trunk group measurement reports are not required. Remember to remeasure trunk groups. To get a list of trunk groups that are "measured" and need to be changed, type list trunk-group.
Check the Dial Plan screen (or Dial Plan Analysis Table screen depending on the release) for 0 assigned as attd.
If there are none, check the Attendant Console screens for any buttons with attd-qcalls or attd-qtime btns. Remove these if 0 is not assigned as attd.
1 of 2
Description When you have finished installing the authentication file, Communication Manager will have a password for all Avaya logins, including craft. This password is unique to the media server of the customer. You can use the password the next time you log in as craft, provided you access the media server through the Services port. You do not need an ASG challenge/ response to log in this way, even though every other means of craft access still requires an ASG challenge/ response. This unique craft password remains valid until a new authentication file is installed.
2 of 2

Issue 2.1 June 2006
895
Before you go on site for a migration from a DEFINITY system, complete the following additional tasks before starting the migration: Task You might need to move the UPSs and the Ethernet switch(es) from the 2-post rack to the 4-post rack. Description Ensure that you have:

A Philips screwdriver Rail kits (700230741) for a 4-post rack for the UPSs Cage nuts to attach the screws to the rack, if necessary At least 2 people to lift the equipment

When you are on site, complete the following tasks before you start the migration: Task Verify that the EIA 310D 19-inch (48-cm) open equipment rack is grounded. For S8710 only: Verify that the open, customer-supplied, EIA 310D (or equivalent) standard 4-post, 19-inch (48-centimeter), equipment rack is properly installed and solidly secured. Description See the job aid titled Approved Grounds (555-245-772). Ensure that you have the screws that come with the rack. Ensure that the rail kit for the Avaya-supplied UPS is installed on the rack or available for installation. For more information on installing the rail, see the rail kit documentation.
1 of 2
Task Verify that you have the correct cables for the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs. Verify that you have all necessary equipment onsite.
Description The cables must be labeled and run from the control hardware rack to the port networks. Appropriate connectivity must be provided.
Installing and Configuring the Avaya S8500 Media Server (03-300143) Installing and Configuring the Avaya S8700-Series Media Server (03-300145) 2 of 2

For a list of documents that you need to perform the migration, see Resources on page 54. Additional documentation needed. Document Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Description A quick-reference guide that provides physical installation and connection information.
Issue 2.1 June 2006
897
Migration tasks
Perform the following tasks to migrate an S8700 Media Server to an S8710 Media Server. Premigration administration:
Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used) on page 900 Upgrading software on the local survivable processors on page 901 Upgrading firmware on media gateways and media modules on page 902 Verifying hardware on page 902

Clearing the ARP cache on the laptop computer on page 902 Connecting to the active media server on page 903 Accessing the media server maintenance web interface on page 904 Clearing alarms on page 904 Starting a SAT session on page 904 Recording all busyouts on page 905 Checking clock synchronization on page 905 Disabling scheduled maintenance on page 905 Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 906 Checking for translation corruption on page 906 Checking the software release on page 906 Backing up the Linux migration upgrade set to the network on page 907 Backing up the Linux migration upgrade set to the services laptop on page 908 Recording the Product ID on page 909
On the standby S8700 Media Server:

Accessing the standby S8700 Media Server on page 909 Shutting down the S8700 Media Server on page 910
On the first S8710 Media Server:

Turning on the media server on page 910 Accessing the media server on page 911 Configuring Telnet for Windows 2000 or Windows XP on page 911
Migration tasks
Installing Communication Manager on page 912 Accessing the server command line interface with SSH protocol on page 913 Using PuTTY to reaccess the media server on page 915 Checking the software version on page 915 Changing the date and the time on page 915 Copying files to the media server on page 915 Configuring the network parameters on page 916 Verifying connectivity to the network server on page 917 Installing the new license file and the Avaya authentication file on page 918 Restoring the Linux migration upgrade set from the network on page 918 Downloading the license file and the Avaya authentication file on page 919 Selecting the media server type on page 920 Restoring the Linux migration upgrade set from the services laptop on page 921 Installing software update on page 922 Verifying the software update installation on page 923 Verifying the media server configuration on page 923
On the second S8710 Media Server:

Installing Communication Manager and restoring files on page 925 Installing the new license file and the Avaya authentication file on page 925 Restoring the Linux migration upgrade set from the network on page 926 Restoring the Linux migration upgrade set from the services laptop on page 927 Installing software updates, if any on page 927 Verifying media server configuration on page 927
Transferring control to the S8710 Media Servers

Moving Ethernet cables on page 927 Moving cables to the S8710 Media Server (media server 1) on page 928 Releasing the media server on page 928 Moving cables to the S8710 Media Server (media server 2) on page 928 Completing the cable migration on page 929
On the standby S8710 Media Server:

Accessing the standby media server on page 929 Pinging all the connections to the media server on page 929
Issue 2.1 June 2006
899
Backing up files on the media server on page 930 Releasing alarm suppression (optional) on page 930 Setting the Product ID on page 930 Logging off all administration applications on page 930 Disconnecting from the media server on page 931

Accessing the active media server on page 931 Resolving alarms on page 931 Backing up files on the media server on page 932 Releasing alarm suppression (optional) on page 932 Setting the Product ID on page 932 Logging off all administration applications on page 932 Disconnecting from the media server on page 932 Registering the system on page 933 Removing customer files from the services laptop on page 933
! CAUTION:
CAUTION:
The licensing of the platform and port network connectivity attributes for the S8700-series Media Server can be complex. See Caution about platform/PNC license settings for the S8700-series Media Server on page 314 and License and Avaya authentication files on page 313.
Upgrading G150, G350 or G700 Media Gateways and local survivable processors (if being used)
Note:
Note: If the customer has no G150, G350 or G700 Media Gateways or no local survivable processors (LSPs), skip these tasks and go to On the active S8700 Media Server on page 902.
If the configuration is using G150, G350, or G700 Media Gateways and media modules and newer firmware exists for them, you must upgrade the firmware on them first. If the media server is the primary controller for a G700 Media Gateway equipped with an LSP, you must upgrade the software on the LSPs before you transfer control to the S8710 Media Servers. The correct order is: 1. Upgrade media gateway firmware to latest version 2. Upgrade media modules firmware to latest version 3. Upgrade the media server software to latest version if using LSPs 4. Transfer control to the S8710 Media Server.

Note:
! CAUTION:
CAUTION:
You must stop call processing on the LSPs during the migration process. You can stop call processing on the active media server. If you do not stop call processing on the LSPs, all calls to the LSPs will be dropped.
Issue 2.1 June 2006
901

For more detailed information on the firmware upgrade process, see Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server (555-234-100).
Verifying hardware
Ensure that you have the conversion specific hardware on hand. You can reuse some of the equipment and cables when migrating a S8700 Media Server to S8710 or S8720 Media Servers. But you need new equipment to complete the migration.
Migration tasks
Perform the following tasks to migrate an S8700 Media Server to an S8710 Media Server.
On the active S8700 Media Server



To connect to the active media server: 1. Connect the laptop to the Services port (2) on the back of the active media server with a cross-connect CAT5 cable (Figure 60: Services laptop computer connected directly to the S8700 Media Server). Figure 60: Services laptop computer connected directly to the S8700 Media Server
2 3
AVAYA
DAI - 1 DUP MEMORY
LINE
RECEIVE
TRANS
LINK STAT
cadlsrvr KLC 030402
Issue 2.1 June 2006
903

Clearing alarms
To clear alarms: 1. Perform one of the following actions:
If Communication Manager Release 1.x, under Alarms and Notification, click View Current Alarms. If Communication Manager Release 2.x, under Alarms, click Current Alarms.
2. Select the server alarms that you want to clear and click Clear. 3. Use SAT commands and a terminal emulation application, such as Native Configuration Manager or MS HyperTerminal, to resolve any major alarms. Note: The following tasks Starting a SAT session on page 904 through Checking the software release on page 906 are SAT commands. You can perform these tasks on the active media server only.
Note:


Checking clock synchronization

To check clock synchronization: 1. Type status sync. Press Enter to verify that the clock synchronization is good. 2. Ensure that the Switching Capabilities field is set to enabled. Note: Because of a change in Communication Manager Release 1.3, you do not need to disable Terminal Translation Initialization (TTI) before an upgrade or a migration or enable TTI afterwards.
Note:
Disabling scheduled maintenance

To prevent scheduled daily maintenance from interfering with the upgrade: 1. Type change system-parameters maintenance. Press Enter. 2. If scheduled maintenance is in progress, set the Stop Time field to 1 minute after the current time. or 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 90 minutes, set the Start Time field to 21:30.
Issue 2.1 June 2006
905
! CAUTION:
CAUTION:

Checking the software release

To check the software release: 1. Under Server Upgrades, click Software Version to see what software release is on the media server. 2. Perform one of the following actions:
If Communication Manager Release 1.0 or 1.1 software, upgrade the software to Communication Manager Release 1.3.2. If Communication Manager Release 1.2 or 1.3 software, apply the upgrade patch.
Backing up the Linux migration upgrade set to the network

Note:
Note: Because the S8710 Media Server does not have a PCMCIA flash drive, you must back up the files to either the customer network or the Services laptop. You then must restore the files to the S8710 Media Server later in the process. If you backed up the files to the Services laptop or if the FTP server of the customer is unavailable, do not perform this procedure. Continue with Backing up the Linux migration upgrade set to the services laptop on page 908. Note: During this backup, the system backs up the necessary Avaya Call Processing (ACP) translations and other files and labels these files as upgrade.
Note:
!
Important:
Important: Do not back up or restore any sets or files other than the Linux migration upgrade set.
To back up the Linux migration set to the network: 1. Perform one of the following actions:
For Communication Manager Release 1.x, under Server Configuration and Upgrades, click Linux Migration (Backup). For Communication Manager Release 2.x, under Server Upgrades, click Linux Migration (Backup/Restore)

For Communication Manager Release 1.x, select Initiate new backup and click Submit. For Communication Manager Release 2.x, select Initiate new backup or restore and click Submit.
3. Under Backup Method, select FTP. Complete the User Name, the Password, the Host Name, and the Directory fields for where you want to back up the files. The Host Name field must use the host IP address. 4. Click Submit. 5. Click Status to view the Backup History. 6. Select the box that is next to the file that is being backed up and click Check Status. When the backup is complete, the system displays the following message: Backup is finished
Issue 2.1 June 2006
907
! CAUTION:
CAUTION:
Check the text to verify that there are no error messages. Any error message means that the backup has failed. 7. Continue with Recording the Product ID on page 909.
Backing up the Linux migration upgrade set to the services laptop

To back up the Linux migration upgrade set from the S8700 Media Server to the Services laptop: 1. On the Services laptop, access the media server. For more information, see Accessing the media server maintenance web interface on page 904 and return here. 2. Under Security, click FTP. The system displays the FTP window. 3. Click Start Server. 4. Under Server Upgrades, click Linux Migration (Backup / Restore). The system displays the Linux Migration - Backup / Restore window. 5. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 6. In the Backup Method area, select FTP. 7. In the:

User Name field, type anonymous Password field, type your e-mail ID Host Name field, type the exact server hostname for the server you are on Directory field, type /pub
8. Click Submit. 9. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 10. Select Display status 11. Click Submit to review the status of the restore process. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. Ignore these error messages and continue with the backup.
On the standby S8700 Media Server
12. On the services laptop, type ftp 192.11.13.6. Press Enter to start an FTP session from the laptop to the S8700 Media Server. 13. For the login, type anonymous. Press Enter. 14. For the password, type your e-mail ID. Press Enter. 15. Type cd pub. Press Enter. 16. Type bin. Press Enter to make the transfer in a binary format. 17. Type get name, where name is the name of the Linux migration upgrade set. Press Enter. 18. Log off the system.
Recording the Product ID

To record the Product ID: 1. Click Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6. Press Enter. 3. Log in as craft or dadmin. 4. At the prompt, type productid. Press Enter. Record the Product ID for future use.

Accessing the standby S8700 Media Server
To access the standby S8700 Media Server: 1. Clear the ARP cache on the laptop, if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 902 and return here. 2. Disconnect the laptop from the active media server. 3. Connect the laptop to the Services port (2) on the standby media server. 4. Log in. For more information, see Accessing the media server maintenance web interface on page 904 and return here.
Issue 2.1 June 2006
909
5. Repeat one of the following procedures:
Backing up the Linux migration upgrade set to the network on page 907 and return here, or Backing up the Linux migration upgrade set to the services laptop on page 908 and return here
6. Continue with Shutting down the S8700 Media Server on page 910.
Shutting down the S8700 Media Server

! CAUTION:
CAUTION:
Ensure that you are connected to the standby S8700 Media Server. If you are on the active S8700 Media Server, you will cause an interchange.
To shut down the standby S8700 Media Server: 1. Under Server, click Shutdown Server. 2. In the Shutdown This Server window:

Select Immediate Shutdown Clear Restart Server after Shutdown Select Shut down even if this is the active server
3. Click Shutdown. 4. Disconnect the laptop from the Services port. 5. Disconnect the power cord from the UPS.
On the first S8710 Media Server

Note:
Note: The first S8710 Media Server becomes media server 1.
Turning on the media server

To turn on the media server: Note: You must place the CD-ROM in the drive before you turn on the media server.
Note:
1. Use a paperclip to open the CD-ROM drive on the media server. 2. Place the CD-ROM with Communication Manager in the CD-ROM drive. 3. Connect the AC power cord to media server 1 and to UPS 1 to turn on the media server.
! CAUTION:
CAUTION:
Do not push the UID button that is located above the power button. If you push the UID button, you reset the UID on the media server. 4. Push the power button.

To access the media server: 1. Clear the ARP cache from the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 902 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect cable. 3. Wait at least 3 minutes after you turn on the media server. Then start an SSH session to access the information on the CD-ROM.
Configuring Telnet for Windows 2000 or Windows XP

You can set the Microsoft Telnet application to send a carriage return (CR) and a line feed (LF) whenever you press Enter. The installation program sees this as two key presses. If you are running Windows 2000 or Windows XP, you must correct this before you copy the Remaster Program to the hard disk. 1. Click Start > Run to open the Run dialog box. 2. Type telnet. Press Enter to open a Microsoft Telnet session. 3. Type display. Press Enter to see the current settings. 4. Perform one of the following actions: If the system displays the message Sending only CR, close the dialog box. If the system displays the message Sending both CR & LF, continue with step 5. 5. Type unset crlf. Press Enter. 6. Type display. Press Enter to verify that the settings changed. The system displays the message Sending only CR. 7. Close the dialog box.
Issue 2.1 June 2006
911

Note:
Note: To navigate on these screens, use the arrow keys to move to an option, then press the space bar to select the option. Press Enter to submit the screen. 3. Select Install, ensure that OK is highlighted. Press Enter.
4. On the Select Release Version window, ensure that the Build line and <OK> are highlighted. Press Enter to partition the hard disk and reformat the partitions. Once the drive is properly configured, the program starts the installation process and reports the progress.
These processes can take up to 20 minutes. When the media server is ready to reboot, the CD-ROM drive drawer opens. You must remove the CD from the drive at this time. The reboot can take up to 3 minutes. The telnet session drops automatically.

Note:
To use this procedure with a laptop cable connection to the services port, you must configure your laptop for the network connection. See Network configuration on page 1242. In addition, a third-party SSH client must already be installed on your computer.
Issue 2.1 June 2006
913
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: 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.
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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
Note:
Note:
will have a different key. You get a prompt in this case because it appears that the host key has changed. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Using PuTTY to reaccess the media server

Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. For more information, see Accessing the media server on page 1237.
Checking the software version

To check the software version: 1. Under Server, click Software Version. 2. Verify the software version.
Changing the date and the time

To change the date and the time: 1. Under Server, click Server Date/Time. 2. Change the date, the time, and the time zone as needed. 3. Click Submit to put the changes into effect.

You must copy any required files from the services laptop to the media server. This includes the software update file and the firmware for programmable circuit packs. Note: Do not use this method to copy the Linux migration upgrade set. Note: The latest firmware for the programmable circuit packs and media modules might be on the CD-ROM.
Note:
Note:
Issue 2.1 June 2006
915
Configuring the network parameters

!
Important:
Important: If you backed up files to the services laptop, do not perform this procedure. Continue with Selecting the media server type on page 920.
Note:
Note: If you backed up to the network of the customer, you must readminister the Ethernet port that connects to the network. You must have the host name, the IP address, the subnet mask, and the default gateway for the two media servers and the active server. You also need the IP address for the Ethernet port that connects to the customer network.
To configure the network parameters: 1. Under Server Configuration, click Configure Server to open the first page and select the server type of the Configure Server process. The system displays the Configure Server window. 2. Select the appropriate server type and click Continue. 3. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 4. Select Configure individual services and click Continue. 5. Click Set Identities from the main menu. 6. On the Set Server Identities window: a. Populate the Host Name fields. b. In the This is server field, select 1. c. Assign the Ethernet ports and click Continue. 7. In the Configure Ethernet Interfaces window, type the correct IP addresses, the gateway, and the subnet mask or use the default addresses for the Ethernet port that is connected to the customer LAN. Select AUTOSENSE for the speed.

S8710 IP-PNC: Eth 0 S8710 Fiber-PNC: Eth 4
Click Change to update and reboot the media server. When the system shows the message Successfully configured ethernet interfaces, the Ethernet ports are configured. 8. Click Close Window to close the Configure Server wizard.
Verifying connectivity to the network server

To verify that the Ethernet port is working, ping the network server where the backup files are stored from the media server. Note: You might need to restart your browser before you perform this procedure. 1. Move the Ethernet cable that is connected to the network of the customer from the shut down standby S8700 Media Server to the S8710 Media Server (IP: Eth0; MC: Eth4). For more information, see Port connections on the back of the S8710 Media Server on page 917. Figure 61: Port connections on the back of the S8710 Media Server
2 1
Note:
3
100 MGz
RECEIVE MODE LINC ACTIVE DAL1 DUP MEMORY TRANS MODE
LINC SYNC
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadsnet2 KLC 043004
3 4
6 5 2
Figure notes: 1. Ethernet 0 to control network A (CNA) if this is a dedicated control network or to the customer network if this is a nondedicated control network (straight-through CAT5 cable) 2. Ethernet 1 to Services laptop (cross-connect CAT5 cable) 3. Ethernet 2 to duplicated media server (cross-connect CAT5 cable) 4. Ethernet 3 to control network B (CNB) if this is a duplicated control network 5. Ethernet 4 to network of the customer if this is a dedicated control network (straight-through CAT5 cable) 6. Not used
2. Under Diagnostics, click Ping.
Issue 2.1 June 2006
917
3. Select Host Name or IP Address and type the IP address of the server where the system files are stored. 4. Click Execute Ping. If you can successfully ping the server, you can proceed to restore the backed up sets of files.
Installing the new license file and the Avaya authentication file
To load a new license file and an Avaya authentication file. 1. Under Security, click License File, select Install the license previously downloaded, and then click Submit to install the license file. The system tells you that the license is installed successfully. 2. Under Security, click Avaya Authentication, and then click Install. The system tells you that the authentication is installed successfully.
Restoring the Linux migration upgrade set from the network

!
Important:
Important: If you backed up files to the services laptop, do not perform this procedure. Continue with Restoring the Linux migration upgrade set from the services laptop on page 921.
! CAUTION:
CAUTION:
You must restore the S8700 Media Server 1 files to the S8710 Media Server 1 and the S8700 Media Server 2 files to the S8710 Media Server 2. On media server 1, restore the backup set from the standby S8700 Media Server, that is, restore the backup set from media server 1.
! CAUTION:
CAUTION:
Run restore only once. If you run restore more than once, you can corrupt the system data. If a restore appears to be incomplete, check the Backup History and the Backup Logs on the Maintenance Web Interface. Check the system log through the Linux command line interface. If all these sources indicate that a restore did not complete, you can safely rerun the restore.
! CAUTION:
CAUTION:
When you receive a network transfer protocol (NTP) failure notice, ignore the notice. This notice occurs because media server 1 does not have a physical connection and thus cannot read the NTP.
To restore the Linux migration upgrade files: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). 2. Select Initiate new backup or restore and click Submit 3. Under Restore Method, select FTP. Complete the User Name, the Password, the Host Name, and the Directory fields for the location of the backup files. 4. Click Submit. 5. Select the upgrade set to restore and both Force options. Click Restore. If the upgrade version is a mismatch, click Force Restore. 6. Click Status to view the restore progress. 7. Select the upgrade set and click Check Status to view the restore progress. The restoration is complete when the system displays the following message: Backup: 0: Restore of <filepath/filename> is completed successfully.
Downloading the license file and the Avaya authentication file

This procedure assumes that the license file and the authentication file are on the services laptop. To download the files to the media server: 1. Under Miscellaneous, click Download Files. The system displays the Download Files window.
Issue 2.1 June 2006
919
2. In the Download Files window, click Browse next to the top field to open the File Upload window on your laptop. Find the license file that you need to upload to the media server. 3. Repeat Step 2 for the second field to find the Avaya authentication file. 4. When all the files that you want to upload show in the fields, click Download to upload all the files to the media server. Once you download the license file and the Avaya authentication file to the media server, you must install the files. For more information, see Installing the new license file and the Avaya authentication file on page 918.
Selecting the media server type

Note:
Note: If you did not perform Downloading the license file and the Avaya authentication file on page 919, you must select the media server type before you install the postupgrade patch.
To determine the media server type: 1. Under Server Configuration, click Configure Server to open the first page. 2. Select the server type of the Configure Server process. Note: If you performed this step earlier, the system does not display this screen. The system displays the Configure Server window. 3. Select the appropriate server type and click Continue. The system displays the Set Identities window. 4. Click Cancel.
Note:
Restoring the Linux migration upgrade set from the services laptop
! CAUTION:
CAUTION:
! CAUTION:
CAUTION:
! CAUTION:
CAUTION:
When you receive a network transfer protocol (NTP) failure notice, ignore the notice. This notice occurs because media server 1 does not have a physical connection and thus cannot read the NTP. Note: If you performed Restoring the Linux migration upgrade set from the network on page 918, do not perform this procedure.
Note:
To restore the Linux migration upgrade set from the services laptop to the S8710 Media Server: 1. Access the media server. For more information, see Accessing the media server maintenance web interface on page 904 and return here. 2. Under Server Upgrades, click Linux Migration (Backup / Restore). The system displays the Linux Migration - Backup / Restore window. 3. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 4. In the Restore Method area, select Local Directory. 5. Type /var/home/ftp/pub as the destination location of the Linux migration upgrade set and press Enter. 6. Click Submit. 7. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 8. Select Display status.
Issue 2.1 June 2006
921
9. Click Submit to view the status of the restore process. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. Ignore these error messages and continue with restoring the Linux migration upgrade set.
Installing software update

Note:
Note: Do not perform this procedure if you do not have a Communication Manager software update file to install.
To use a Telnet session to install the software update file. 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft. 3. Type cd /var/home/ftp/pub. Press Enter to access the pub directory. 4. At the prompt, type ls -ltr. Press Enter to list files in the pub directory. The media server displays a list of files in the FTP directory. Verify that the directory contains the Communication Manager .tar.gz file you uploaded, if any. 5. Type update_unpack update.tar.gz, where update is the release or the issue number of the latest software update file. An example can be 00.0.411.7-xxxx.tar.gz. Press Enter. 6. Type update_show. Press Enter to list Communication Manager files to verify that the new software update file was unpacked. 7. Type update_activate update, where update is the release number or the issue number of the latest software update file, such as 00.0.411.7-xxxx. For example, do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot (reset system 4). If the media server reboots, the server also might display the message /opt/ecs/sbin/drestart 2 4 command failed. Ignore this message. You must wait until the restart/reset completes before you enter additional commands. The media server displays a message that the software update (patch) was applied. 8. Type update_show again. Press Enter to list Communication Manager files. Review the list to verify that the new software update file was activated.
On the second S8710 Media Server
Verifying the software update installation

To verify the software update installation: 1. Under Server, click Software Version. 2. Verify that the new software update is listed.
Verifying the media server configuration

To verify the media server configuration: 1. Under Server Configuration, click Configure Server to start the configure server process. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 3. Select Configure all services using the wizard. 4. Click Continue to continue through all the screens, checking each screen for new screens and new fields on existing screens as mentioned in the Software Release Letter. Note: You must click through all the screens whether any changes exist. Note: You might need to reset the port speeds for the Ethernet interfaces. The Ethernet speeds must be set to AUTO-SENSE. 5. When you complete all the new fields, as necessary, click Continue on the Update System screen. The Update System screen shows each configuration task as it completes. When done, the screen shows the message All configuration information was entered. 6. Click Close Window to close the Configure Server wizard. 7. Disconnect from the media server.
Note:
Note:

Note:
Note: The second S8710 Media Server becomes media server 2.
Issue 2.1 June 2006
923

Note:
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open. 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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html.
Note:
8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:
Installing Communication Manager and restoring files

To install Communication Manager and restore files: 1. Repeat the procedures Turning on the media server on page 910 through Configuring the network parameters on page 916 and return here.
! CAUTION:
CAUTION:
Ensure you restore the files from media server 2. If you restore the files on media server 1, you can rename that media server as media server 2.
Installing the new license file and the Avaya authentication file
For a migration, you must load a new license file and an Avaya authentication file. 1. Under Security, click License File. Click Install the license previously downloaded, and then click Submit to install the license file. The system tells you that the license is installed successfully. 2. Under Security, click Avaya Authentication, and then click Install. The system tells you that the authentication is installed successfully.
Issue 2.1 June 2006
925
Restoring the Linux migration upgrade set from the network

!
Important:
Important: If you backed up files to the services laptop, do not perform this procedure. Continue with Restoring the Linux migration upgrade set from the services laptop on page 921.
! CAUTION:
CAUTION:
! CAUTION:
CAUTION:
! CAUTION:
CAUTION:
When you receive a network transfer protocol (NTP) failure notice, ignore the notice. This notice occurs because media server 1 does not have a physical connection and thus cannot read the NTP.
To restore the Linux migration upgrade set: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). 2. Select Initiate new backup or restore and click Submit 3. Under Restore Method, select FTP. Complete the User Name, the Password, the Host Name, and the Directory fields for the location of the backup files. 4. Click Submit. 5. Select the Linux migration upgrade set to restore and both Force options and click Restore. If the Linux migration upgrade set is a mismatch, click Force Restore. 6. Click Status to view the restore progress. 7. Select the upgrade set and click Check Status to view the restore progress. The restoration is complete when the system displays the following message: Backup: 0: Restore of <filepath/filename> is completed successfully.
Transferring system control to the S8710 Media Servers
Restoring the Linux migration upgrade set from the services laptop
To restore the Linux migration upgrade set from the Services laptop to the S8710 Media Server: 1. Repeat Restoring the Linux migration upgrade set from the services laptop on page 921 for media server 2 and return here.
Installing software updates, if any

To install any software updates: 1. Repeat the procedures Installing software update on page 922 through Verifying the software update installation on page 923 for media server 2 and return here.
Verifying media server configuration

To verify the media server configuration: 1. Repeat Verifying the media server configuration on page 923 on the active server and return here.
Transferring system control to the S8710 Media Servers

! CAUTION:
CAUTION:
If you move the Ethernet switch(es) and UPSs, there might be an interruption of service up to 30 minutes.
Moving Ethernet cables

To transfer control to the S8710 Media Servers, move the CAT5 cables from the S8700 Media Servers to the S8710 Media Servers.
Issue 2.1 June 2006
927
Moving cables to the S8710 Media Server (media server 1)

To move the cables: 1. Disconnect the blue CAT5 duplication cable from the stopped S8700 Media Server. Do not connect the cable to the S8710 Media Server at this time. 2. Disconnect the following CAT5 cables from the stopped S8700 Media Server and connect the cables to the busied out S8710 Media Server. That is, connect the cables to media server 1.

Customer network (black or blue) CNA (green) CNB (red)
3. Connect the Services laptop to the active S8700 Media Server. 4. Shut down the active S8700 Media Server. For more information, see Shutting down the S8700 Media Server on page 910 and return here. 5. Connect the services laptop to the S8710 Media Server. That is, connect the laptop to media server 1.
Releasing the media server

To release the S8710 Media Server that is media server 1: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft. 3. Type server -r. Press Enter.
Moving cables to the S8710 Media Server (media server 2)

To move the cables: 1. Disconnect the cables from the previously active S8700 Media Server. 2. Connect the cables to the busied out S8710 Media Server. That is, connect the cables to media server 2.
Completing the cable migration

To complete the cable migration: 1. Connect the CAT5 duplication cable to both media servers. 2. Connect the new yellow LC fiber-optic cable to both media servers. 3. Connect the Services laptop to the S8710 Media Server,.That is, connect the laptop to media server 2. 4. Release the S8710 Media Server. That is, release media server 2. For more information, see Releasing the media server on page 928 and return here. 5. Move the modem connections from the S8700 Media Servers to the S8710 Media Server.

Note:
Note: This section applies to media server 2.
Accessing the standby media server

To access the standby media server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 902 and return here. 2. If you are not already connected to the standby media server, connect to the standby media server. 3. Log in. For more information, see Accessing the media server maintenance web interface on page 904 and return here.
Pinging all the connections to the media server

To ping all connections to the media server: 1. Under Diagnostics, click Ping. 2. Select Other server(s), All IPSIs, UPS(s), Ethernet switches. Click Execute Ping.
Issue 2.1 June 2006
929
Backing up files on the media server

To back up files on the media server: 1. Under Data Backup/Restore, click Backup Now. 2. Select the data sets and the backup method. Select Save ACP translations prior to backup to save the translations to the hard disk before saving it to the backup media or network of the customer. 3. Click Start Backup to start the back up process.

If you complete the migration well before the time set when you suppressed alarming, you might want to release alarm suppression manually rather than wait. 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft or dadmin. 3. Type almsuppress -n. Press Enter to release alarm suppression. 4. Log off.
Setting the Product ID

Note:
Note: The Product ID is different from the Product ID on the S8700 Media Server.
To set the Product ID: 1. Click Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6. Press Enter. 3. Log in as craft or dadmin. 4. At the prompt type productid -p number where product_id is the Product ID that you received from the customer or the ART tool. Press Enter.

Disconnecting from the media server

Disconnect the laptop from the media server.

Note:
Note: This section applies to media server 1.
Accessing the active media server

To access the active media server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 902 and return here. 2. Connect to the active media server. 3. Log in. For more information, see Accessing the media server maintenance web interface on page 904.
Resolving alarms
To resolve alarms: 1. Under Alarms and Notification, click Current Alarms. 2. Select the server alarms that you want to clear and click Clear. 3. To resolve new alarms since the migration, use SAT commands and the following documentation:
Maintenance Commands for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300431) Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300430)
Issue 2.1 June 2006
931
Backing up files on the media server

To back up files on the media server: 1. Under Data Backup/Restore, click Backup Now. 2. Select the data sets and the backup method. Select Save ACP translations prior to backup to save the translations to the hard disk before saving it to the backup media or customers network. 3. Click Start Backup to start the back up process.

To release alarm suppression: 1. Repeat Releasing alarm suppression (optional) on page 930 on the active media server and return here.
Setting the Product ID

To set the Product ID: 1. Repeat Setting the Product ID on page 932 on the active media server and return here.

Disconnecting from the media server

Disconnect the laptop from the media server.
Registering the system

Follow the existing process and procedures to register the Avaya S8710 Media Server.
Removing customer files from the services laptop

Remove the customer Linux migration upgrade set from the services laptop.
Issue 2.1 June 2006
933
Migrating from an S8700 or S8710 Media Server to an S8720 Media Server

Use these procedures to migrate an existing S8700 or S8710 Media Server on Avaya Communication Manager Release 1.x, 2.x, and 3.x to an S8720 Media Server on Communication Manager Release 3.1. If the media servers are on Communication Manager 1.x, you must upgrade them to Communication Manager 1.3.2 before the migration. This migration requires a new Communication Manager license file and an Avaya authentication file. In this migration, you reuse the system and translation files from the S8700 or S8710 Media Servers. With this migration you are upgrading to Communication Manager 3.1. You must upgrade local survivable processors (LSPs), Enterprise Survivable Servers (ESSs), and H.248 media gateways before the migration.

Note:
Note: Whenever you connect to a media server, perform Clearing the ARP cache on the laptop computer on page 949 to avoid temporary internet files that might cause confusion.
If being used, upgrade: - G150 Media Gateways - G250 Media Gateways - G350 Media Gateways - G700 Media Gateways - LSPs - ESSs
If Communication Manager Release 1.2 or 1.3, install the preupgrade update (patch). If Communication Manager Release 1.0 or 1.1, upgrade to Communication Manager Release 1.3.2.
Issue 2.1 June 2006
935
Install the Avaya S8720 Media Servers either: - in a 19-inch, 4-post rack as described in the Quick Start for Hardware Installation: Avaya S8700 Series Media Server (555-245-703). - on a pullout shelf attached to the existing 2-post rack.
Install the current software on the S8720 Media Servers. Note: If moving Ethernet switch(es) and UPSs to the 4-post rack, do it here before the cutover.
Note:
Perform a save translation. On the active and standby S8700 or S8710, perform a full backup. On the standby S8700 or S8710, shut down and remove from the rack. On the first S8720: - Mount in the rack - Install Communication Manager software - Restore the backup data
Remove the control cables from the active S8700 or S8710. Shutdown the active S8700 or S8710. Release the first S8720 and install the license file. Remove the S8700 or S8710 from the rack. On the second S8720: - Mount in the rack - Install Communication Manager software - Restore the backup data - Perform a full backup
On the active S8720, save the translations and perform a full backup. Complete the post-migration administration.
Prerequisites

Presite checklist on page 937. Perform these tasks before you go on site. Additional tasks on page 939. Perform these tasks on site before you start the migration from an existing DEFINITY system. Presite migration checklist on page 940. Perform these tasks before you go on site. On site migration checklist on page 941. Perform these are tasks on site before you start the migration. Documentation checklist for migrations on page 941. Have these documents ready to use while you perform the migration.
Tasks checklists
Presite checklist
:
Issue 2.1 June 2006
937
Description For example, obtain logins and passwords for the following components: Media Server Media Gateway SIPI or IPSI circuit pack auxillary equipment Communication Manager These logins and passwords include the equipment of the customer. You need a new license file and authentication file. You need the serial number from the reference SIPI or IPSI and the SAP order number to generate a new license file. You use this CD to install the software on the media server and upgrade the firmware. The most recent versions of the service packs are also on this CD.
Obtain the serial number for the media servers, if necessary.
Check which service packs you need and download files from the Avaya Support Web site (http:// avaya.com/support). Check which service packs you need and download files from the Avaya Support web site (http:// avaya.com/support).

IPSIs C-LAN MedPro VAL circuit packs
For the most current versions, go to the Avaya Support web site (http://avaya.com/support). Click Downloads and select the product. Download license and authentication files to your Services laptop. New license and authentication files are necessary. Obtain information and download files from the Remote Feature Activation (RFA) web site at http:// rfa.avaya.com. 2 of 3
Additional tasks
Do this task only if you are not performing a full backup and restore to transfer the configuration data from the S8700 or S8710 to the S8720. Task Verify that you have the required, customer-provided network information. Obtain a filled out Electronic Preinstallation Worksheet (EPW) Description The EPW is an Excel spreadsheet providing the customers network information needed to use the Avaya Installation Wizard to configure the control network components. Get the EPW from the Avaya project manager, Avaya software technician, or customer network administrator. A blank EPW is available at the Avaya Installation Wizard web site (http://support.avaya.com/avayaiw/).
Issue 2.1 June 2006
939

Before you go on site for a migration from a system, complete the following additional tasks before starting the migration: Task You might need to move the UPSs and the Ethernet switch(es) from the 2-post rack to the 4-post rack. Description Ensure that you have:

A Philips screwdriver Rail kits (700230741) for a 4-post rack for the UPSs Cage nuts to attach the screws to the rack, if necessary At least 2 people to lift the equipment


For a list of documents that you need to perform the migration, see Resources on page 54.
Issue 2.1 June 2006
941
Additional documentation needed. Document Quick Start for Hardware Installation: Avaya S8700-Series Media Servers (555-245-703) Administration for Network Connectivity for Avaya Communication Manager (555-233-504) Installing and Configuring an Avaya S8700-Series Media Server (03-300145) Description A quick-reference guide that provides physical installation and connection information.
Migration tasks
Perform the following tasks to migrate an S8700 or S8710 Media Server to an S8720 Media Server. Note: The term first S8720 or second S8720 does not imply the actual media server number. Rather this references the sequence of events in the migration.
Note:
Premigration administration:

Upgrading H.248 media gateways, LSPs, and ESSs (if being used) on page 947 Upgrading software on the local survivable processors on page 947 Upgrading firmware on media gateways and media modules on page 948 Verifying hardware on page 948 Using Enterprise Survivable Servers on page 948 Using local survivable processors on page 948
On the active S8700 or S8710 Media Server: 1. Configuring Telnet for Windows 2000 or WindowsXP on page 949 2. Clearing the ARP cache on the laptop computer on page 949 3. Connecting to the active media server on page 950
Migration tasks
4. Accessing the media server maintenance web interface on page 953 5. Checking the software release on page 953 6. Clearing alarms on page 953 7. Starting a SAT session on page 954 8. Recording all busyouts on page 954 9. Checking clock synchronization on page 954 10. Disabling scheduled maintenance on page 955 11. Busying out MMI circuit packs with SAT for a duplicated control network only (main server only) on page 955 12. Checking for translation corruption on page 956 13. Saving translations on page 956 14. Checking the CNC status on page 957 15. Recording the server connection type on page 957 16. Backing up the active S8700 or S8710 Media Server on page 958 17. Obtaining the Product ID on the active S8700 or S8710 Media Server on page 965 18. Looking up server configuration information on the active S8700 or S8710 Media Server on page 965 19. Disconnecting from the active S8700 or S8710 Media Server on page 966 On the standby S8700 or S8710 Media Server: 1. Checking the software release on page 966 2. Clearing the ARP cache on the laptop computer on page 967 3. Connecting to the standby S8700 or S8710 Media Server on page 967 4. Accessing the standby S8700 or S8710 Media Server on page 967 5. Checking the CNC status on page 968 6. Recording the server connection type on page 968 7. Backing up the standby S8700 or S8710 Media Server on page 968 8. Obtaining the Product ID on the standby S8700 or S8710 Media Server on page 976 9. Looking up server configuration information on the standby S8700 or S8710 Media Server on page 976 10. Busying out the standby S8700 or S8710 Media Server on page 977 11. Shutting down the standby S8700 or S8710 Media Server on page 977 12. Removing the duplication cables on page 978
Issue 2.1 June 2006
943
13. Removing the standby S8700 or S8710 Media Server from the rack on page 978 14. Removing the DAL1 card, if necessary on page 978 On the first S8720 Media Server: 1. Installing the DAL1 card in the S8720 Media Server, if necessary on page 980 2. Installing the first S8720 Media Server in the rack on page 982 3. Inserting the Communication Manager software distribution CD on page 982 4. Connecting the cables to the first S8720 Media Server on page 983 5. Accessing the first S8720 Media Server on page 986 6. Installing Communication Manager on page 986 7. Accessing the media server maintenance web interface on page 989 8. Checking the software version on page 989 9. Verifying date and time on page 989 10. Copying files to the media server (if any) on page 990 11. Activating the software update (if any) on page 990 12. Stopping Communication Manager on the first S8720 Media Server on page 991 13. Configuring to allow restoring configuration data and translations from the ftp server on the network on page 991 14. Configuring to allow restoring configuration data and translations from flash card or Services laptop on page 992 15. Verifying connectivity from the first S8720 Media Server to the network server on page 993 16. Restoring configuration data and translations to the first S8720 Media Server on page 993 17. Verifying the first S8720 Media Server configuration on page 996 18. Rebooting the first S8720 Media Server on page 998 19. Accessing the first S8720 Media Server on page 998 20. Confirming the product ID on the first S8720 Media Server on page 998 21. Enabling CNC, if necessary on page 999 22. Initializing Communication Manager on page 999 23. Performing an integrity check on the first S8720 Media Server on page 999 Making the first S8720 Media Server active 1. Shutting down the active S8700 or S8710 Media Server on page 1000 2. Accessing the first S8720 Media Server on page 1001 3. Releasing the first S8720 Media Server on page 1001 4. Verifying the first S8720 Media Server is active on page 1002
Migration tasks
5. Installing the license and authentication files on page 1002 6. Verifying connectivity between the first S8720 Media Server and port networks, LSPs, and ESSs on page 1002 Removing the remaining S8700 or S8710 Media Server 1. Removing the S8700 or S8710 Media Server from the rack on page 1003 2. Removing the DAL1 card, if necessary on page 1003 On the second S8720 Media Server: 1. Installing the DAL1 card in the S8720 Media Server, if necessary on page 1005 2. Installing the second S8720 Media Server in the rack on page 1007 3. Inserting the Communication Manager software distribution CD on page 1007 4. Connecting the cables to the second S8720 Media Servers on page 1007 5. Accessing the media server on page 1010 6. Installing Communication Manager on page 1011 7. Accessing the second S8720 Media Server on page 1012 8. Checking the software version on page 1013 9. Verifying date and time on page 1013 10. Copying files to the second S8720 Media Server (if any) on page 1013 11. Activating the software update (if any) on page 1014 12. Stopping Communication Manager on the second S8720 Media Server on page 1014 13. Configuring to allow restoring configuration data and translations from the ftp server on the network on page 1015 14. Configuring to allow restoring configuration data and translations from flash card or Services laptop on page 1016 15. Verifying connectivity to the network server on page 1017 16. Restoring configuration data and translations to the second S8720 Media Server on page 1017 17. Verifying the second S8720 Media Server configuration on page 1020 18. Rebooting the second S8720 Media Server on page 1021 19. Accessing the second S8720 Media Server on page 1022 20. Confirming the product ID on the first S8720 Media Server on page 1022 21. Enabling CNC, if necessary on page 1022 22. Initializing Communication Manager on page 1022 23. Performing an integrity check on the second S8720 Media Server on page 1023
Issue 2.1 June 2006
945
24. Connecting the duplication cables on page 1024 25. Releasing the second S8720 Media Server on page 1026 26. Verifying the second S8720 Media Server is in standby state on page 1027 27. Releasing alarm suppression (optional) on page 1027 28. Logging off all administration applications on page 1027 29. Disconnecting from the second S8720 Media Server on page 1027 On the active (first) S8720 Media Server: 1. Accessing the active media server on page 1028 2. Resolving alarms on page 1028 3. Enabling scheduled maintenance on page 1028 4. Saving translations on page 1029 5. Backing up files on the active S8720 Media Server on page 1029 6. Releasing alarm suppression (optional) on page 1029 7. Logging off all administration applications on page 1029 8. Disconnecting from the active S8720 Media Server on page 1029 On the standby (second) S8720 Media Server 1. Accessing the standby media server on page 1030 2. Resolving alarms on page 1030 3. Backing up files on the standby S8720 Media Server on page 1030 4. Releasing alarm suppression (optional) on page 1031 5. Logging off all administration applications on page 1031 6. Disconnecting from the standby media server on page 1031 Completing the migration: 1. Registering the system on page 1031 2. Removing customer files from the Services laptop on page 1031 Interchanging media servers (optional): 1. Accessing the standby media server on page 1032 2. Interchanging media servers (optional) on page 1032 3. Performing an integrity check on the active S8720 Media Server on page 1033
This section describes the premigration administration you must perform.
! CAUTION:
CAUTION:
The licensing of the platform and port network connectivity attributes for the S8700-series Media Server can be complex. Failure to license the S8720 properly can result in loss of connectivity to the port networks (PNs). For more information, see Caution about platform/PNC license settings for the S8700-series Media Server on page 314 and License and Avaya authentication files on page 313.
Upgrading H.248 media gateways, LSPs, and ESSs (if being used)
If newer firmware exists for a configuration using H.248 media gateways, LSPs, or ESSs, and media modules, you must upgrade the firmware on them first. If the media server is the primary controller for a G700 Media Gateway equipped with an LSP or ESS, you must upgrade the software on the LSPs or ESSs before the migration. The correct order is: 1. Upgrade media gateway firmware to latest version 2. Upgrade media modules firmware to latest version 3. Upgrade media server software to latest version if using LSPs 4. Migrate to the S8720 Media Server.

Note:
Issue 2.1 June 2006
947

Verifying hardware
Ensure that you have the conversion specific hardware on hand. You can reuse some of the equipment and cables when migrating an S8700 or S8710 Media Server to S8720 Media Server.
Using Enterprise Survivable Servers

To ensure that the ESSs do not take over during the migration, you can reset the Network Service Timer on the ESS to 15 minutes.
Using local survivable processors

If using local survivable processors (LSPs), and if no "recovery rule" on the gateway screen is set, either:

Shutdown LSPs before the migration, or Reset the LSPs after the migration
Migration tasks
This section provides the information to migrate from the current media server to the S8720 Media Server.
On the active S8700 or S8710 Media Server

This section describes the procedures you must perform on the active S8700 or S8710 Media Server.
Configuring Telnet for Windows 2000 or WindowsXP

You can set the Microsoft Telnet application to send a carriage return (CR) and a line feed (LF) whenever you press Enter. The installation program sees this as two key presses. 1. On your laptop computer, click Start > Run to open the Run dialog box. 2. Type telnet. Press Enter to open a Microsoft Telnet session. 3. Type display. Press Enter to see the current settings. 4. Perform one of the following actions: If the system displays the message Sending only CR, close the dialog box. If the system displays the message Sending both CR & LF, continue with step 5. 5. Type unset crlf. Press Enter. 6. Type display. Press Enter to verify that the settings changed. The system displays the message Sending only CR. 7. Close the dialog box.


Issue 2.1 June 2006
949

To connect to the active media server: 1. Connect the laptop to the Services port (2) on the back of the active media server with a cross-connect CAT5 cable. For S8700 Media Server connections, see Figure 62: Services laptop computer connected directly to the S8700 Media Server.
Figure 62: Services laptop computer connected directly to the S8700 Media Server
2 3
AVAYA
DAI - 1 DUP MEMORY
LINE
RECEIVE
TRANS
LINK STAT
cadlsrvr KLC 030402
Figure notes: 1. Services laptop 2. Network interface card (NIC) (not necessary if the laptop has the NIC installed) 3. NIC adapter cable (if necessary) (not necessary if the laptop has the NIC installed) 4. CAT5 crossconnect cable
For S8700 or S8710 Media Server connections, see Services laptop computer connected directly to the S8710 Media Server on page 952.
Issue 2.1 June 2006
951
Figure 63: Services laptop computer connected directly to the S8710 Media Server
2 3
4
3
3
100 MGz
RECEIVE MODE LINC ACTIVE
DAL1 DUP MEMORY
TRANS MODE
LINC SYNC
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadlsrv2 KLC 042804
Figure notes: 1. Services laptop 2. Network interface card (NIC) (not necessary if the laptop has the NIC installed) 3. NIC adapter cable (if necessary) (not necessary if the laptop has the NIC installed) 4. CAT5 crossconnect cable
Note:
Note: If the system currently is running Release pre-3.0, use Accessing the media server maintenance web interface on page 953. If the system currently is running Release post-3.0, use secure shell (SSH).


To check the software release: 1. On the Maintenance Web Interface, click Software Version to see what software release is on the media server. 2. If Communication Manager Release 1.0 or 1.1, upgrade to Communication Manager Release 1.3.2. If Communication Manager Release 1.2 or 1.3, apply the upgrade patch. If Communication Manager Release 2.x or higher, proceed to Clearing the ARP cache on the laptop computer on page 949.
Clearing alarms
To clear alarms: 1. If Communication Manager Release 1.x, under Alarms and Notification, click View Current Alarms. If Communication Manager Release 2.x or higher, under Alarms, click Current Alarms. 2. Select the server alarms to be cleared and click Clear. 3. Resolve any major alarms with SAT commands and a terminal emulation application, such as Native Configuration Manager or MS HyperTerminal.
Issue 2.1 June 2006
953
Note:
Note: Tasks Starting a SAT session on page 954 through Checking for translation corruption on page 956 are SAT commands and can only be done on the active media server.


Checking clock synchronization

To check clock synchronization: 1. Type status synchronization. Press Enter to verify that the clock synchronization is good. 2. Ensure that the Switching Capabilities field shows enabled.

To prevent scheduled daily maintenance from interfering with the upgrade: 1. Type change system-parameters maintenance. Press Enter. 2. Record the settings for the Stop Time and Start Time fields. 3. If scheduled maintenance is in progress, set the Stop Time field to 1 minute after the current time. or 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 90 minutes, set the Start Time field to 21:30.
! CAUTION:
CAUTION:
Issue 2.1 June 2006
955

To check for translation corruption: 1. Type newterm. 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.
Saving translations
The save translation command is release dependent. Release 1.2 1.3 1.3.1 1.3.2 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 3.0 3.0.1 3.1 Load 110.4 526.5 531.1 536.1 219.0 221.1 411.7 414.1 111.4 118.0 340.3 346.0 Command save translation save translation save translation lsp save translation lsp save translation lsp save translation lsp save translation all save translation all save translation all save translation all save translation all save translation all save translation all If LSP present If LSP present If LSP present If LSP present If LSP present If LSP present If LSP present If LSP present If LSP or ESS present If LSP or ESS present If LSP or ESS present Condition
Additional information:
Type save translation and HELP. If [all or lsp] or [all or ess or lsp] displays, type save translation all. Press Enter. Type save translation and HELP. If [lsp or [ip address]] displays, type save translation lsp. Press Enter. Otherwise, type save translation. Press Enter.
To save translations, perform the following step:
Type save translation. Press Enter. If this operation is unsuccessful, follow the normal escalation procedures before continuing.
Checking the CNC status

Note:
Note: You can perform this step only if you have Communication Manager Release 3.0 or later.
If the system is using Control Network C (CNC), you need to check the CNC status. To check the CNC status: 1. Access the server command line interface. 2. Log in as craft or dadmin. 3. Type cnc status. Press Enter. The system displays one of the following messages: Control Network C has not been configured. Control Network C has been configured. 4. Record the CNC setting.
Recording the server connection type

To note the server connection type: 1. In a bash session, type grep -i offertype /etc/opt/ecs/ecs.conf. Press Enter. 2. Make a note of the server connection type. sray = fiber-port network connectivity (PNC) (formerly multi-connect) seagull = IP-PNC (formerly IP-connect)
Issue 2.1 June 2006
957
Backing up the active S8700 or S8710 Media Server

You must do a backup for the active S8700 or S8710 Media Servers. For more information, see Backup destinations for migrations on page 958. You can back up to: Note: Do not use the PCMCIA flash card (for S8700). The PCMCIA flash card is not a valid option for the migration 1. An ftp server on the network (release dependent) 2. The USB-connected Compact Flash (for the S8710 only) 3. The Services laptop Table 12: Backup destinations for migrations Backup destination PCMCIA flash card USB flash FTP server Services laptop
1. Preferred for S8710 2. Preferred for S8700
Note:
S8700 x2 x
S8710 x1 x x
The backup procedures in Migration to S8720, Release 3.1 or later, backup, release specific on page 958 are different depending on the software release currently running on your media server. Table 13: Migration to S8720, Release 3.1 or later, backup, release specific S8700 or S8710 Release 1.2 1.3 1.3.1 Load 02.0.110.4 03.0.526.5 03.1.531.0 Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore N/A1 N/A N/A Web Interface for Backup Data Set File Name of Backup upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. 1 of 2
Table 13: Migration to S8720, Release 3.1 or later, backup, release specific (continued) S8700 or S8710 Release 1.3.2 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 3.0 3.0.1 Load 03.2.536.1 00.0.219.0 00.1.221.1 01.0.411.7 01.1.414.1 02.0.111.4 02.0.118.1 00.0.340.3 00.1.346.0 Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Backup Now Backup Now N/A N/A N/A N/A N/A N/A N/A Full Full Web Interface for Backup Data Set File Name of Backup upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. full..tar.gz. full..tar.gz. 2 of 2
1. Data Set is not selectable by the user.
Backing up the configuration data and translations to the USB-connected Compact Flash card
Note: This procedure is only for the S8710 Media Server with Communication Manager Release 3.0 and later.
Note:
To back up the configuration data and translations to the USB-connected Compact Flash card: 1. On the Maintenance Web Interface, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup (release dependent). 3. Under Backup Method, click Local PC card. 4. In the Retain field, type 3.
Issue 2.1 June 2006
959
5. Click Start Backup. 6. Click Status to view the backup history. 7. Check the box next to the file being backed up and click Check Status. When the backup is complete, the system displays the following message. Backup successful
Backing up the configuration data and translations to an ftp server on the network
This procedure assumes that you are backing up from Communication Manager Release 3.0 and later. To back up the configuration data and translations to the network: 1. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup (release dependent). 3. Under Backup Method, select a ftp or select from the choices provided. 4. Fill in the following fields for where you are backing up the files:

User Name Password Host Name - enter the host IP address Directory
! CAUTION:
CAUTION:
Check the text to verify that there are no error messages. Ignoring the error message can result in no backup.
Backing up the configuration data and translations to the Services laptop

This procedure assumes that you are backing up from Communication Manager Release 3.0 and later. The backup destination is the IP address of the server being backed up. The backup is followed by a transfer of the backup file to the laptop. This backup is a manual process.
To back up the configuration data and translations to the Services laptop: 1. On the services laptop, access the media server. For more information, see Accessing the media server maintenance web interface on page 953 and return here. 2. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 3. In the Backup Method section, select FTP. 4. Under Backup Method, fill in the fields for where you are backing up the files.

User Name field is anonymous Password field is @ Host Name field is the IP address of the server being backup up The Host Name field must use the host IP address.
Directory field is pub (Communication Manager Release 2.0 and later)
5. Click Start Backup. 6. Start > Run to open a command prompt session. The system displays the Run window. 7. Type cmd. Press Enter. 8. Type ftp 192.11.13.6. Press Enter. 9. At the user prompt, type anonymous. Press Enter. 10. At the password prompt, type @. Press Enter. 11. At the ftp prompt, type bin. Press Enter. 12. Type cd pub (for Communication Manager Release 2.0 and later). Press Enter. 13. Type ls *.tar.gz. Press Enter. The file will be listed as full......tar.gz. Note: For the following step, if the mget command is unavailable, use get. 14. Type mget filename.tar.gz where filename is the name of the backed up file. Press Enter. 15. Type y. Press Enter. 16. Type bye. Press Enter. 17. At the prompt, type dir *.tar.gz. Press Enter to confirm the file is there.
Note:
Issue 2.1 June 2006
961
Backing up the configuration data and translations using Linux Migration Backup to the USB-connected Compact Flash card
Note: This procedure is only for the S8710 Media Server with Communication Manager Release pre3.x.
Note:
To back up the configuration data and translations using the Linux Migration Backup/Restore to the USB-connected Compact Flash card: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select Local PC Card. 4. In the Retain field, type 3. 5. Click Submit. 6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup.
Backing up the configuration data and translations using Linux Migration Backup to an ftp server on the network
This procedure assumes that you are backing up from Communication Manager release pre2.x. To back up the configuration data and translations using the Linux Migration Backup/Restore from the S8700 or S8710 Media Server to an ftp server on the network: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select FTP.
4. Fill in the following fields for where you are backing up the files:

5. Click Submit. 6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup.
Backing up the configuration data and translations using Linux Migration Backup to the Services laptop
This procedure assumes that you are backing up from Communication Manager release pre2.x. The backup destination is the IP address of the server being backed up. The backup is followed by a transfer of the backup file to the laptop. This backup is a manual process. To back up the configuration data and translations using the Linux Migration Backup/Restore from the S8700 or S8710 Media Server to the Services laptop: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select FTP. 4. In the following fields:

User Name field: type anonymous Password field: enter any password with a @ Host Name field: enter the IP address of the server being backup up The Host Name field must use the host IP address.
Issue 2.1 June 2006
963
Note:
Note: If Communication Manager Release 1.2 or 1.3, enter a slash (/) in the Directory field.
Directory field: type /pub
5. Click Submit. 6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup. 9. On the services laptop, type ftp 192.11.13.6. Press Enter to start an FTP session from the laptop to the S8700 or S8710 Media Server. 10. For the login, type anonymous. Press Enter. 11. For the password, type @. Press Enter. 12. At the ftp prompt, type bin. Press Enter to make the transfer in a binary format. 13. Type cd pub. Press Enter. cd pub is for Communication Manager Release 2.0 and later. 14. Type ls *.tar.gz. Press Enter. The file will be listed as upgrade......tar.gz. Note: For the following step, if the mget command is unavailable, use get. 15. Type mget filename.tar.gz where filename is the name of the backed up file. Press Enter. 16. Type y. Press Enter. 17. Type bye. Press Enter. 18. At the prompt, type dir *.tar.gz. Press Enter to confirm the file is there.
Note:
Obtaining the Product ID on the active S8700 or S8710 Media Server

To obtain the Product ID: 1. Access the server command line interface. 2. Log in as craft or dadmin. 3. At the prompt, type productid. Press Enter. The productid is the product ID you received from the customer or the ART too.
Looking up server configuration information on the active S8700 or S8710 Media Server
Perform this task if you are backing up to the customer network. To look up and record server configuration information: 1. Under Server Configuration, click Configure Server to open the first page (Select server type) of the Configure Server process. The system displays the Configure Server window. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 3. Select Configure individual services and click Continue. 4. Click Set Identities from the main menu. 5. In the Set Identities area, record the following information for later use:

The host names in the Host Name fields. Server number (from the This is server number field) Ethernet assignments (in the Select NIC Usage area)
6. Record the Ethernet port assignment and usage for each of the five possible interfaces. For example, see Control Network A in Network Interface Card usage on page 977. Notice that CNA is assigned Ethernet 0. Note: If these values are different from the defaults, physical connections to the Ethernet ports must match these settings.
Note:
Issue 2.1 June 2006
965
Table 14: Network Interface Card usage
7. Click Continue. 8. In the Corporate LAN Interface section, record the following information for later use:

IP addresses (under the Corporate LAN Interface area) Subnet mask (under the Corporate LAN Interface area) Default gateway (under the Corporate LAN Interface area)
Disconnecting from the active S8700 or S8710 Media Server

Disconnect the Services laptop from the active media server.
On the standby S8700 or S8710 Media Server

This section describes the procedures you must perform on the standby S8700 or S8710 Media Server.

To check the software release: 1. On the Maintenance Web Interface, click Software Version to see what software release is on the media server. 2. If Communication Manager Release 1.0 or 1.1, upgrade to Communication Manager Release 1.3.2. If Communication Manager Release 1.2 or 1.3, apply the upgrade patch. If Communication Manager Release 2.x or higher, go to Clearing the ARP cache on the laptop computer on page 967.


Connecting to the standby S8700 or S8710 Media Server

To connect to the standby S8700 or S8710 Media Server:
Connect the laptop to the Services port (2) on the back of the standby media server with a cross-connect CAT5 cable.
Accessing the standby S8700 or S8710 Media Server

To access the standby S8700 or S8710 Media Server: 1. Connect the laptop to the Services port (2) on the standby media server. 2. Log in. For more information, see Accessing the media server maintenance web interface on page 953 and return here.
Issue 2.1 June 2006
967
Checking the CNC status

Note:
Note: You can perform this step only if you have Communication Manager Release 3.0 or later.
If the system is using Control Network C (CNC), you need to check the CNC status. To check the CNC status: 1. Access the server command line interface. 2. Log in as craft or dadmin. 3. Type cnc status. Press Enter. The system displays one of the following messages: Control Network C has not been configured. Control Network C has been configured. 4. Record the CNC setting. The settings for this media server must be the same as for the active media server.
Recording the server connection type

To note the server connection type: 1. In a bash session, type grep -i offertype /etc/opt/ecs/ecs.conf. Press Enter. 2. Make a note of the server connection type. The connection type for this media server must be the same as for the active media server. sray = fiber-port network connectivity (PNC) (formerly multi-connect) seagull = IP-PNC (formerly IP-connect)
Backing up the standby S8700 or S8710 Media Server

You must do a backup for the standby S8700 or S8710 Media Servers. For more information, see Backup destinations for migrations on page 958. You can back up to: Note: Do not use the PCMCIA flash card (for S8700). The PCMCIA flash card is not a valid option for the migration 1. An ftp server on the network (release dependent)
Note:
2. The USB-connected Compact Flash (for the S8710 only) 3. The Services laptop Table 15: Backup destinations for migrations Backup destination PCMCIA flash card USB flash FTP server Services laptop
1. Preferred for S8710 2. Preferred for S8700
S8700 x2 x
S8710 x1 x x
The backup procedures in Migration to S8720, Release 3.1 or later, backup, release specific on page 958 are different depending on the software release currently running on your media server. Table 16: Migration to S8720, Release 3.1 or later, backup, release specific S8700 or S8710 Release 1.2 1.3 1.3.1 1.3.2 2.0 2.0.1 2.1 Load 02.0.110.4 03.0.526.5 03.1.531.0 03.2.536.1 00.0.219.0 00.1.221.1 01.0.411.7 Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore N/A1 N/A N/A N/A N/A N/A N/A Web Interface for Backup Data Set File Name of Backup upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. 1 of 2
Issue 2.1 June 2006
969
Table 16: Migration to S8720, Release 3.1 or later, backup, release specific (continued) S8700 or S8710 Release 2.1.1 2.2 2.2.1 3.0 3.0.1 Load 01.1.414.1 02.0.111.4 02.0.118.1 00.0.340.3 00.1.346.0 Linux Migration Backup/Restore Linux Migration Backup/Restore Linux Migration Backup/Restore Backup Now Backup Now N/A N/A N/A Full Full Web Interface for Backup Data Set File Name of Backup upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. full..tar.gz. full..tar.gz. 2 of 2
1. Data Set is not selectable by the user.
Backing up the configuration data and translations to the USB-connected Compact Flash card
Note: This procedure is only for the S8710 Media Server with Communication Manager Release 3.0 and later.
Note:
To back up the configuration data and translations to the USB-connected Compact Flash card: 1. North Maintenance Web Interface, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup (release dependent). 3. Under Backup Method, click Local PC card. 4. In the Retain field, type 3. 5. Click Start Backup. 6. Click Status to view the backup history. 7. Check the box next to the file being backed up and click Check Status. When the backup is complete, the system displays the following message. Backup successful
Backing up the configuration data and translations to an ftp server on the network
This procedure assumes that you are backing up from Communication Manager Release 3.0 and later. To back up the configuration data and translations to the network: 1. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup (release dependent). 3. Under Backup Method, select a ftp or select from the options provided. 4. Fill in the following fields for where you are backing up the files:

! CAUTION:
CAUTION:
Check the text to verify that there are no error messages. Ignoring the error message can result in no backup.
Backing up the configuration data and translations to the Services laptop

This procedure assumes that you are backing up from Communication Manager Release 3.0 and later. The backup destination is the IP address of the server being backed up. The backup is followed by a transfer of the backup file to the laptop. This backup is a manual process. To back up the configuration data and translations to the Services laptop: 1. On the services laptop, access the media server. For more information, see Accessing the media server maintenance web interface on page 953 and return here. 2. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 3. In the Backup Method section, select FTP.
Issue 2.1 June 2006
971
4. Under Backup Method, fill in the fields for where you are backing up the files.

User Name field is anonymous Password field is @ Host Name field is the IP address of the server being backup up The Host Name field must use the host IP address.
Directory field is pub (Release 2.0 and later)
5. Click Start Backup. 6. Start > Run to open a command prompt session. The system displays the Run window. 7. Type cmd. Press Enter. 8. Type ftp 192.11.13.6. Press Enter. 9. At the user prompt, type anonymous. Press Enter. 10. At the password prompt, type @. Press Enter. 11. At the ftp prompt, type bin. Press Enter. 12. Type cd pub (for Communication Manager Release 2.0 and later). Press Enter. 13. Type ls *.tar.gz. Press Enter. The file will be listed as full......tar.gz. Note: For the following step, if the mget command is unavailable, use get. 14. Type mget filename.tar.gz where filename is the name of the backed up file. Press Enter. 15. Type y. Press Enter. 16. Type bye. Press Enter. 17. At the prompt, type dir *.tar.gz. Press Enter to confirm the file is there.
Note:
Backing up the configuration data and translations using Linux Migration Backup to the USB-connected Compact Flash card
Note: This procedure is only for the S8710 Media Server with Communication Manager release pre3.x.
Note:
To back up the configuration data and translations using the Linux Migration Backup/Restore to the USB-connected Compact Flash card: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select Local PC Card. 4. In the Retain field, type 3. 5. Click Submit. 6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup.
Backing up the configuration data and translations using Linux Migration Backup to an ftp server on the network
This procedure assumes that you are backing up from Communication Manager release pre2.x. To back up the configuration data and translations using the Linux Migration Backup/Restore from the S8700 or S8710 Media Server to an ftp server on the network: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select FTP. 4. Fill in the following fields for where you are backing up the files:

Issue 2.1 June 2006
973
5. Click Submit. 6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup.
Backing up the configuration data and translations using Linux Migration Backup to the Services laptop
This procedure assumes that you are backing up from Communication Manager release pre2.x. The backup destination is the IP address of the server being backed up. The backup is followed by a transfer of the backup file to the laptop. This backup is a manual process. To back up the configuration data and translations using the Linux Migration Backup/Restore from the S8700 or S8710 Media Server to the Services laptop: 1. Under Server Upgrades, click Linux Migration (Backup/Restore). The system displays the Linux Migration - Backup / Restore window. 2. Select Initiate new backup or restore and click Submit. The system displays the Linux Migration - Backup / Restore Initiate window. 3. In the Backup Method section, select FTP. 4. In the following fields:

User Name field: type anonymous Password field: enter any password with a @ Host Name field: enter the IP address of the server being backup up The Host Name field must use the host IP address.
Note:
Note: If Communication Manager Release 1.2 or 1.3, enter a slash (/) in the Directory field.
Directory field: type /pub
5. Click Submit.
6. Under Server Upgrades, click Linux Migration (Backup / Restore) to review the status of the backup. The system displays the Linux Migration - Backup / Restore Status window. 7. Select Display status 8. Click Submit. The system displays the Linux Migration - Backup / Restore Status window. This window might display a BACKUP COMPLETE message with possible series 200 error messages. You can ignore these series 200 error messages and proceed with the backup. 9. On the services laptop, type ftp 192.11.13.6. Press Enter to start an FTP session from the laptop to the S8700 or S8710 Media Server. 10. For the login, type anonymous. Press Enter. 11. For the password, type @. Press Enter. 12. At the ftp prompt, type bin. Press Enter to make the transfer in a binary format. 13. Type cd pub. Press Enter. cd pub is for Communication Manager Release 2.0 and later. 14. Type ls *.tar.gz. Press Enter. The file will be listed as upgrade......tar.gz. Note: For the following step, if the mget command is unavailable, use get. 15. Type mget filename.tar.gz where filename is the name of the backed up file. Press Enter. 16. Type y. Press Enter. 17. Type bye. Press Enter.
Note:
Issue 2.1 June 2006
975
Obtaining the Product ID on the standby S8700 or S8710 Media Server

Note:
Note: You might see different values for the product ID between the active and standby media servers.
To obtain the Product ID: 1. Access the server command line interface. 2. Log in as craft or dadmin. 3. At the prompt, type productid. Press Enter. The productid is the product ID you received from the customer or the ART too.
Looking up server configuration information on the standby S8700 or S8710 Media Server
Perform this task if you are backing up to the customer network. To look up and record server configuration information: 1. Under Server Configuration, click Configure Server to open the first page (Select server type) of the Configure Server process. The system displays the Configure Server window. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 3. Select Configure individual services and click Continue. 4. Click Set Identities from the main menu. 5. In the Set Identities area, record the following information for later use:

Server number (from the This is server number field) Ethernet assignments (in the Select NIC Usage area)
6. Record the Ethernet port assignment and usage for each of the five possible interfaces. For example, see Control Network A in Network Interface Card usage on page 977. Notice that CNA is assigned Ethernet 0. Note: If these values are different from the defaults, physical connections to the Ethernet ports must match these settings.
Note:
Table 17: Network Interface Card usage
7. Click Continue. 8. In the Corporate LAN Interface section, record the following information for later use:

IP addresses (under the Corporate LAN Interface area) Subnet mask (under the Corporate LAN Interface area) Default gateway (under the Corporate LAN Interface area)
9. Click Close Window to exit the Configure Server window.
Busying out the standby S8700 or S8710 Media Server

To busyout the S8700 or S8710 Media Server: 1. On the Maintenance Web Interface, click Busy Out Server. The system displays the Busy Out Server window. 2. On the Busy-Out Server window, click Busy Out. The system displays the Busy Out Server Results window.
Shutting down the standby S8700 or S8710 Media Server

! CAUTION:
CAUTION:
Ensure that you are connected to the standby S8700 or S8710 Media Server. Proceeding with the following steps and being connected to the incorrect media server can result in service disruption.
To shut down the standby S8700 or S8710 Media Server: 1. Under Server, click Shutdown Server. The system displays the Shutdown This Server window.
Issue 2.1 June 2006
977
2. Make the following selections:

Select Immediate Shutdown Click Restart Server after Shutdown
3. Click Shutdown.
Removing the duplication cables

To remove the duplication cables: 1. Label and disconnect the duplication fiber cable from both S8700s or S8710s. 2. Label and disconnect the duplication interface IP cable from both S8700s or S8710s.
Removing the standby S8700 or S8710 Media Server from the rack
To remove the standby S8700 or S8710 Media Server from the rack: 1. Label and disconnect all remaining cables. 2. Disconnect the laptop from the Services port. 3. Disconnect the power cord from the UPS. 4. Remove the standby S87xx media server from the rack, if necessary. 5. Remove the rails from the rack.
Removing the DAL1 card, if necessary

Perform this procedure only if:

Migrating from an S8710, and S8720 uses hardware-assist memory duplication, and Reusing the DAL1 from the S8710
To remove the DAL1 card: 1. Turn off the media server. 2. Extend the media server from the rack. 3. Lift up on the hood latch handle and remove the access panel. Note: Always wear an antistatic wrist strap when working inside the media server.
Note:
4. Disconnect any internal or external cables connected to any existing circuit packs. 5. Lift the PCI riser cage thumbscrews (1, Removing the PCI riser cage on page 979) and turn them counter-clockwise. 6. Remove the PCI riser cage (2). Figure 64: Removing the PCI riser cage
1 2
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
0M 10
3 z G
0M 10
2 z G
3M 13
1 z G
VD
CI
h3df87cr LAO 102505
7. Push in the locking tab (1, Removing the DAL1 card on page 980). 8. Release the locking lever (2). Note: Do not use any tools when performing the next step. 9. Using a rocking motion, carefully pull the DAL1 card straight out from the PCI riser cage (3).
Note:
Issue 2.1 June 2006
979
Figure 65: Removing the DAL1 card
2 1
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
h3dsdalr LAO 102505
On first S8720 Media Server

This section describes the procedures you must perform on the first S8720 Media Server.
Installing the DAL1 card in the S8720 Media Server, if necessary

Note:
Note: If the S8720s are using hardware duplication, install the DAL1 card. If S8720s are using software duplication, go to Installing the first S8720 Media Server in the rack on page 982.
To install the DAL1 card in the S8720 Media Server: 1. Lift up on the hood latch handle and remove the access panel. Note: Always wear an antistatic wrist strap when working inside the media server. 2. Lift the PCI riser cage thumbscrews and turn them counterclockwise to loosen them. 3. Remove the PCI riser cage. 4. Remove the blank expansion slot cover from the PCI riser cage (3, Installing the DAL1 card on page 981). Figure 66: Installing the DAL1 card
Note:
1 2
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
3
h3df87di LAO 110205
5. Unlock the PCI retaining clip (1). 6. Carefully insert the DAL1 card into the middle slot of the PCI riser cage (4). 7. Lock the PCI retaining clip (2). 8. Align the PCI riser cage with the guides on the chassis and slide the riser cage into place.
RECEIVE MODE
Issue 2.1 June 2006
981
9. Lift and turn the thumbscrew knobs clockwise while pressing down, until tightened. 10. Turn the thumbscrews counterclockwise to lower the thumbscrew knobs. 11. Install the access cover on the media server. 12. Press down on the hood latch handle to lock the access panel in place.
Installing the first S8720 Media Server in the rack

To install the first S8720 Media Server in the rack: 1. Snap the rails on to the media server. 2. Attach the extension rails to the rack. 3. Install the S8720 Media Server in the rack. For more information, see Quick Start for Hardware Installation: S8700 Series Media Servers (03-300145).
Inserting the Communication Manager software distribution CD

To insert the Communication Manager software distribution CD in the S8720 Media Server: Note: You must place the CD in the CD/DVD drive before turning on the media server. 1. Use a paperclip to open the CD-ROM drive on the media server. 2. Insert the CM software distribution CD in the CD/DVD drive and close the drive door.
Note:
Connecting the cables to the first S8720 Media Server

To connect the cables to the media server: Note: Do not connect the fiber duplication connection cable or the duplication interface IP cable at this time to either S8720 Media Server 1. The network connections depend on the type of memory duplication and the type of control network being used. Connect the network cables as described in the following table. Control Network Dedicated Software Memory Duplication
Note:
Hardware Memory Duplication
LAN to Eth4 (3rd from left on quad NIC) CNA to Eth2 (1st on left on quad NIC) CNB (if used) to Eth3 (2nd from left on quad NIC) LAN/CNA to Eth2 (1st from left on quad NIC) CNB (if used) to Eth3 (2nd from left on quad NIC)
LAN to Eth4 (3rd from left on quad NIC) CNA to Eth0 (on server, labeled 1) CNB (if used) to Eth3 (2nd from left on quad NIC) LAN/CNA to Eth0 (on server, labeled 1) CNB (if used) to Eth3 (2nd from left on quad NIC)
Nondedicated
Issue 2.1 June 2006
983
Figure 67: Duplication and control network cables for hardware duplication
3
100 MGz
LINC SYNC
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadsnetc LAO 110805
3 4
6 5 2
Figure notes: 1. CNA (also LAN for nondedicated control network) Eth0 2. Services port Eth1 3. Duplication cable (crossover) Eth2 4. CNB (if used) Eth3 5. LAN (if dedicated control network) Eth4 6. CNC (if used) Eth5 7. Fiber duplication cable
Figure 68: Duplication and control network cables for software duplication
3
100 MGz
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadsnetb LAO 092305
3 4
6 5 2
Figure notes: 1. Duplication cable (Crossover) Eth0 2. Services port Eth1 3. CNA (also LAN for nondedicated control network) Eth2 4. CNB (if used) Eth3 5. LAN (if dedicated control network) Eth4 6. CNC (if used) Eth5
2. Connect the modem to one of the USB ports. 3. Connect the USB flash drive to one of the USB ports. 4. Connect the power cord to the rear of the media server to turn on the server.
Issue 2.1 June 2006
985
Accessing the first S8720 Media Server

To access the media server: 1. Clear the ARP cache from the laptop if necessary. For more information, see Connecting to the active media server on page 950 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect CAT5 cable. 3. On your laptop computer, click Start > Run to open the Run dialog box, 4. Type ping -t 192.11.13.6. Press Enter to check connectivity between the Services laptop and the media server. 5. Wait at least 3 minutes after turning on the media server before starting a Telnet session to access the information on the CD.

Note:

Note:
Issue 2.1 June 2006
987
Note:
! CAUTION:
CAUTION:
Note:
Note:


To check the software release:
On the Maintenance Web Interface, click Software Version to see what software release is running on the media server.

To change the date and time: 1. On the Maintenance Web Interface, under Server, click Server Date/Time. 2. Change the date, time, and time zone as needed. 3. Click Submit to effect the changes.
Issue 2.1 June 2006
989
Copying files to the media server (if any)

If a software update (service pack) is required, you must copy the update file from the services laptop to the media server. Be sure to copy the Communication Manager license and the Avaya authentication files. Firmware updates for programmable circuit packs and media modules might also be required. These files might be on the software CD. Note: Do not copy the Linux migration upgrade set using this method.
Note:
To copy files to the media server: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im using to connect to the server. 3. Click Browse next to the top field to open the Choose File window on your computer. 4. Find the files that you need to copy to the media server. 5. Click Download to copy the file(s) to the media server. The system automatically copies the files to the default location on the media server.
Activating the software update (if any)

Note:
Note: Skip this procedure if there is no Communication Manager software update file to install.
To use an SSH session to unpack and activate the software update file: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft. 3. Type update_unpack. Press Enter. 4. Select the update by number. Press Enter. 5. Type update_show. Press Enter to list Communication Manager files to verify the new software update file was unpacked. 6. Type update_activate update, where update is the update ID number produced by update_show. An example can be 00.0.411.7-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot (reset system 4). If it reboots, it also might display the message
/opt/ecs/sbin/drestart 2 4 command failed. Ignore this message. You must wait until the restart/reset completes before entering additional commands. The media server displays a message that the software update (patch) was applied. 7. Type update_show again. Press Enter to list Communication Manager files to verify the new software update file was activated.
Stopping Communication Manager on the first S8720 Media Server

To stop Communication Manager:
Type stop -acf. Press Enter to stop Communication Manager.
Configuring to allow restoring configuration data and translations from the ftp server on the network
!
Important:
Important: If you backed up files to the services laptop or the USB-connected Compact Flash, do not perform this procedure. Go to Configuring to allow restoring configuration data and translations from flash card or Services laptop on page 992.
If you backed up to the network of the customer, you must readminister the Ethernet port connecting to the network. You must have the host name, IP address, subnet mask and default gateway for the two media servers and the active server and the IP address for the Ethernet port connecting to the customer network. To configure the network parameters: 1. Under Server Configuration, click Configure Server to open the first page of the Configure Server process. The system displays the Select Server type window. 2. Select the appropriate server type (IP-PNC or fiber-PNC). Click Continue. If you are unsure of the server type, see Recording the server connection type on page 957. 3. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 4. Select Configure individual services. Click Continue.
Issue 2.1 June 2006
991
5. Click Set Identities from the main menu. 6. On the Set Server Identities window:

In the Host Name fields, fill out the host names for each server. In the This is server number field, select the appropriate number. For example, if you are on server 1, select 1. Assign the Ethernet ports. Click Continue.
7. In the Configure Ethernet Interfaces window, fill in the correct IP addresses, Gateway, and Subnet mask (or use the default addresses) for the Ethernet port connected only to the customer LAN and select AUTOSENSE for the speed. This is because CNA, CNB, and duplication values will be populated by the restore function. Click Change to update the media server. When the screen shows Successfully configured ethernet interfaces. The Ethernet ports are configured. 8. Click Close Window to close the Configure Server wizard. Go to Verifying connectivity from the first S8720 Media Server to the network server on page 993.
Configuring to allow restoring configuration data and translations from flash card or Services laptop
If you backed up to the USB-flash card or the Services laptop, you must configure the server type, name, and the number to prepare for the restore procedure. To configure to allow restoring configuration data and translations from the flash card or the Services laptop: 1. Under Server Configuration, click Configure Server to open the first page of the Configure Server process. The system displays the Select Server type window. 2. Select the appropriate server type (IP-PNC or fiber-PNC). Click Continue. If you are unsure of the server type, see Recording the server connection type on page 957. 3. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 4. Select Configure individual services. Click Continue. 5. Click Set Identities from the main menu.
6. On the Set Server Identities window:

7. In the Configure Ethernet Interfaces window, select AUTOSENSE for the speed. Click Change to update the media server. When the screen shows Successfully configured ethernet interfaces. 8. Click Close Window to close the Configure Server wizard. Go to Restoring configuration data and translations to the first S8720 Media Server on page 993.
Verifying connectivity from the first S8720 Media Server to the network server
To verify that the Ethernet port is working, ping from the media server the network server where the backup files are stored. Note: You might need to restart your browser before doing the next steps. 1. Under Diagnostics, click Ping. 2. Select Host Name or IP Address and type the IP address of the server where the system files are stored 3. Click Execute Ping. If you can successfully ping the server, you can proceed to restore the backed up sets of files.
Note:
Restoring configuration data and translations to the first S8720 Media Server
Note:
Note: The physical connections to the Ethernet ports must match the server configuration assignments that were backed up in Looking up server configuration information on the standby S8700 or S8710 Media Server on page 976. The connections to the Ethernet ports that do not match the configuration can prevent access to the server.
Issue 2.1 June 2006
993
The restore method depends on how you backed up the data. Currently there are three ways to restore backed up data.
Restoring data based up to the Compact Flash card (applicable only if migrating from an S8710 Media Server) Restoring data backed up to the customer network (applicable only if migrating an S8700 or S8710 Media Server) Restoring data backed up to the Services laptop (applicable only if migrating from an S8700 or S8710 Media Server)
In Migration to S8720, Release 3.1 or later, using Web interface, View/Restore on page 994, the restore procedure is dependent on what backup method was used. Table 18: Migration to S8720, Release 3.1 or later, using Web interface, View/Restore S8700 or S8710 Release 1.2 1.3 1.3.1 1.3.2 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 3.0 3.0.1 Load 02.0.110.4 03.0.526.5 03.1.531.0 03.2.536.1 00.0.219.0 00.1.221.1 01.0.411.7 01.1.414.1 02.0.111.4 02.0.118.0 00.0.340.3 00.1.346.0 upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. full..tar.gz. full..tar.gz. File Name of Backup
Restoring data backed up to the Compact Flash card

Note:
Note: This procedure is applicable only if migrating from an S8710 Media Server.
To restore data based up to the Compact Flash card: 1. On the Maintenance Web Interface, click View/Restore Data. The system displays the View/Restore Data window. 2. Under the View current backup contents in section, click Local PC Card. 3. Click View. 4. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file might be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 5. Click Restore. 6. Click Check Status view the restore progress.
Restoring data backed up to the customer network

To restore data backed up to the customer network from S8700 or S8710 Media Servers: 1. On the Maintenance Web Interface, click View/Restore Data. The system displays the View/Restore Data window. 2. Under the View current backup contents in section, click FTP. 3. Fill in the following fields for where you are backing up the files:

4. In the Method section, select FTP. 5. Click View. 6. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file might be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 7. Click Restore. 8. Click Check Status view the restore progress.
Issue 2.1 June 2006
995
Restoring data backed up to the Services laptop

To restore data backed up to the Services laptop from S8700 or S8710 Media Servers: 1. On the Maintenance Web Interface, under Miscellaneous, click Download Files. The system displays the Download Files window. 2. Click Files to download from the machine Im using to connect to the server. 3. Click Browse to the location where the backup file is located. 4. Click Open. 5. Click Download. 6. On the Download Files Results window, watch for the following message: The following files have been successfully downloaded to the server. The files are now on the /var/home/ftp/pub directory. 7. Click View/Restore Data. The system displays the View/Restore Data window. 8. Under the View current backup contents in section, click Local Directory and accept the local default value. 9. Click View. 10. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file might be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 11. Click Restore. Wait at least 15 seconds before the next step. 12. Click Check Status view the restore progress. The backup procedures are different depending on the software release currently running on your media server.
Verifying the first S8720 Media Server configuration

To verify the first S8720 Media Server configuration: 1. Under Server Configuration, click Configure Server to start the configure server process. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page.
3. Select Configure all services using the wizard. Click Continue. 4. On the Set Identities page, under the Select Server Duplication area, select either:

This is a duplicated server using duplication hardware This is a duplicated server using software-based duplication This is a duplicated server using encrypted software-based duplication
Note:
Note: The physical connections to the Ethernet ports are different for hardware duplication and software duplication. For more information, see Connecting the cables to the first S8720 Media Server on page 983. 5. Click Continue. Note: The following step applies only if you are using software duplication. 6. On the Configure Interface page, set the speed for Ethernet 0: Server Duplication Link to either:

Note:
AUTO SENSE 1 Gigabit full duplex
7. Click Continue through all the screens, checking for new screens and new fields on existing screens as mentioned in the Software Release Letter. Note: You must click through all the screens whether there are changes or not. 8. On the Configure ESS window:
Note:
If the server is a primary control main, click This is NOT an enterprise survivable server If the server is an ESS server, click This is an enterprise survivable server (ESS)
9. Click Continue. 10. When you complete all the new fields, as necessary, click Continue on the Update System screen. The Update System screen shows each configuration task as the task completes. When done, the screen shows the line All configuration information was entered. 11. Click Close Window to close the Configure Server wizard. 12. Disconnect from the media server.
Issue 2.1 June 2006
997
Rebooting the first S8720 Media Server

Reboot is necessary to initialize server settings that are restored but not yet activated. To reboot the first S8720 Media Server: 1. On the Maintenance Web Interface, under Server, click Shutdown Server. The system displays the Shutdown Server window. 2. Make the following selections:

Select Immediate Shutdown Select Restart Server after Shutdown
3. Click Shutdown.

To access the first S8720 Media Server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Connecting to the active media server on page 950 and return here. 2. Open a browser and connect to the media server. 3. Log in. For more information, see Accessing the media server maintenance web interface on page 953. 4. Suppress all alarms.
Confirming the product ID on the first S8720 Media Server

To confirm the Product ID: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft or dadmin. 3. At the prompt, type productid. Press Enter. The productid must match the value record in Obtaining the Product ID on the standby S8700 or S8710 Media Server on page 976. If value does not match, escalate the problem immediately.
Enabling CNC, if necessary

If the CNC status in Checking the CNC status on page 957 is Control Network C was configured, do this procedure. Otherwise, go to Initializing Communication Manager on page 999. If using Control Network C (CNC): 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft or dadmin. 3. Type cnc on. Press Enter.
Initializing Communication Manager

To initialize Communication Manager: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. Note: For the following step, the logons are release-dependent. 2. Log in as craft or dadmin. 3. Type stop -acf. Press Enter to stop Communication Manager. Communication Manager might already be stopped in Stopping Communication Manager on the first S8720 Media Server on page 991. 4. Type server -b. Press Enter to queue a busy out of the Communication Manager software. The system responds with the following message ACP not yet running, queueing busyout request. 5. Type start -ac. Press Enter to start Communication Manager and load the translations.
Note:
Performing an integrity check on the first S8720 Media Server

To perform an integrity check on the first S8720 Media Server: 1. On the Maintenance Web Interface, under Diagnostics, click Ping. The system displays the Ping window.
Issue 2.1 June 2006
999
2. Under Endpoints to Ping, click Other server(s), All IPSIs, UPS(s), Ethernet switches and click Execute Ping. If this ping fails, see Maintenance Procedures for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300432). 3. Click Server > Status Summary. The system displays the Status Summary window. 4. Verify the following: Mode: BUSY OUT Server Hardware: okay Processes: okay 5. Select Server > Process Status. The system displays the Process Status window. 6. Under Frequency, click Display Once. 7. Click View. 8. Verify all operations are Up except ENV can be off. 9. Telnet to a device outside the media server and ping the media server. 10. Under IPSI Firmware Upgrades, click IPSI Version. The system displays the IPSI Version window. 11. Under Query Type, click Query All and click View to verify connectivity to all IPSIs.
Making the first S8720 Media Server active

This section describes the procedures you must perform to make the first S8720 Media Server active.
Shutting down the active S8700 or S8710 Media Server

Note:
Note: Shutting down the active media server is the beginning of the service disruption.
To connect the Services laptop to the active S8700 or S8710 Media Server: Note: For this task, ensure that you are on the S8700 or S8710 Media Server.
Note:
Making the first S8720 Media Server active
1. Connect the laptop to the Services port (2) on the back of the active media server with a cross-connect CAT5 cable. 2. On the Maintenance Web Interface, under Server, click Shutdown Server. The system displays the Shutdown Server window. 3. Make the following selections:

Select Immediate Shutdown Clear Restart Server after Shutdown Select Shut down even if this is the active server
4. Click Shutdown. 5. On your laptop computer, click Start > Run to open the Run dialog box. 6. Type ping 192.11.13.6. Press Enter. 7. When the ping command does not respond, disconnect the media server from the Services laptop. The LEDs might still be lit.

To access the first S8720 Media Server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Connecting to the active media server on page 950 and return here. 2. Open a browser and connect to the media server. 3. Log in. For more information, see Accessing the media server maintenance web interface on page 953. 4. Suppress all alarms.
Releasing the first S8720 Media Server

To release the first S8720 Media Server: Note: Be prepared for the Access Security Gateway (ASG) challenge and response. 1. On the Maintenance Web Interface, click Server > Release Server. The system displays the Release Server window. 2. Click Release.
Note:
Issue 2.1 June 2006
1001
Verifying the first S8720 Media Server is active

To verify the first S8720 Media Server is active: 1. On the Maintenance Web Interface, click Server > Status Summary. The system displays the Status Summary window. 2. Verify the Mode field is Active. 3. To verify the process status, click Server > Process Status. The system displays the Process Status window. 4. Under Frequency, click Display Once. 5. Click View. 6. Verify all operations are Up except ENV that can be off.
Installing the license and authentication files

Note:
Note: If the migration originated from Communication Manager Release 2.x or earlier, perform this procedure.
To install the Communication Manager license file and the Avaya authentication files on the active S8720 Media Server: 1. To install the license file, click Security > License File. The system displays the License File window. 2. Click Submit. 3. To install the authentication file, click Security > Authentication File. The system displays the Authentication File window. 4. Click Submit.
Verifying connectivity between the first S8720 Media Server and port networks, LSPs, and ESSs
To verify connectivity between the first S8720 and port networks, LSPs, and ESSs: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Type list sys-link. Press Enter.
Removing the remaining S8700 or S8710 Media Server
3. Type list survivable. Press Enter. 4. Type status ess clusters. Press Enter. If ESS clusters are not registered, follow the normal escalation procedures. 5. Type status ess port-networks. Press Enter. If any port networks controlled by an ESS are down, type get forced-takeover ipserver-interfac all. Press Enter. 6. Repeat step 6. If the port networks are still down, follow the normal escalation procedures.
Removing the remaining S8700 or S8710 Media Server

This section describes the procedures you must perform to remove the remaining S8700 or S8710 Media Server.
Removing the S8700 or S8710 Media Server from the rack

To remove the S8700 or S8710 Media Server from the rack: 1. Label and disconnect cables. 2. Disconnect the Services laptop. 3. Remove the S8700 or S8710 Media Server from the rack.
Removing the DAL1 card, if necessary

Perform this procedure only if:

Migrating from an S8710, and S8720 uses hardware-assist memory duplication, and Reusing the DAL1 from the S8710
To remove the DAL1 card: 1. Turn off the media server. 2. Extend the media server from the rack. 3. Lift up on the hood latch handle and remove the access panel.
Issue 2.1 June 2006
1003
Note:
Note: Always wear an antistatic wrist strap when working inside the media server. 4. Disconnect any internal or external cables connected to any existing circuit packs. 5. Lift the PCI riser cage thumbscrews (1, Removing the PCI riser cage on page 979) and turn them counter-clockwise. 6. Remove the PCI riser cage (2).
Figure 69: Removing the PCI riser cage

1 2
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
0M 10
3 z G
0M 10
2 z G
3M 13
1 z G
VD
CI
h3df87cr LAO 102505
7. Push in the locking tab (1, Removing the DAL1 card on page 980). 8. Release the locking lever (2). Note: Do not use any tools when performing the next step. 9. Using a rocking motion, carefully pull the DAL1 card straight out from the PCI riser cage (3).
Note:
Figure 70: Removing the DAL1 card
2 1
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
h3dsdalr LAO 102505

This section describes the procedures you must perform on the second S8720 Media Server.
Installing the DAL1 card in the S8720 Media Server, if necessary

If the S8720s are using hardware duplication, install the DAL1 card. To install the DAL1 card in the S8720 Media Server: 1. Lift up on the hood latch handle and remove the access panel. Note: Always wear an antistatic wrist strap when working inside the media server.
Note:
Issue 2.1 June 2006
1005
2. Lift the PCI riser cage thumbscrews and turn them counterclockwise to loosen them. 3. Remove the PCI riser cage. 4. Remove the blank expansion slot cover from the PCI riser cage (3, Installing the DAL1 card on page 981). Figure 71: Installing the DAL1 card
1 2
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
3
h3df87di LAO 110205
5. Unlock the PCI retaining clip (1). 6. Carefully insert the DAL1 card into the middle slot of the PCI riser cage (4). 7. Lock the PCI retaining clip (2). 8. Align the PCI riser cage with the guides on the chassis and slide the riser cage into place. 9. Lift and turn the thumbscrew knobs clockwise while pressing down, until tightened. 10. Turn the thumbscrews counterclockwise to lower the thumbscrew knobs. 11. Install the access cover on the media server. 12. Press down on the hood latch handle to lock the access panel in place.
RECEIVE MODE
Installing the second S8720 Media Server in the rack

To install the second S8720 Media Server in the rack: 1. Install the slide on the media server. 2. Install the rails in the rack. 3. Install the S8720 Media Server in the rack. For more information, see Quick Start for Hardware Installation: S8700 Series Media Servers (03-300145).
Inserting the Communication Manager software distribution CD

To insert the Communication Manager software distribution CD in the S8720 Media Server: Note: You must place the CD in the CD/DVD drive before turning on the media server. 1. Use a paperclip to open the CD-ROM drive on the media server. 2. Insert the CM software distribution CD in the CD/DVD drive and close the drive door.
Note:
Connecting the cables to the second S8720 Media Servers

To connect the cables to the second media server: Note: Do not connect the fiber duplication connection cable or the duplication interface IP cable at this time to either S8720 Media Server
Note:
Issue 2.1 June 2006
1007
1. The network connections depend on the type of memory duplication and the type of control network being used. Connect the network cables as described in the following table. Control Network Dedicated Software Memory Duplication
Hardware Memory Duplication
CNA to Eth2 (1st on left on quad NIC) CNB (if used) to Eth3 (2nd from left on quad NIC) LAN to Eth4 (3rd from left on quad NIC) LAN/CNA to Eth2 (1st from left on quad NIC) CNB (if used) to Eth3 (2nd from left on quad NIC)
CNA to Eth0 (on server, labeled 1) CNB (if used) to Eth3 (2nd from left on quad NIC) LAN to Eth4 (3rd from left on quad NIC) LAN/CNA to Eth0 (on server, labeled 1) CNB (if used) to Eth3 (2nd from left on quad NIC)
Nondedicated
Figure 72: Duplication and control network cables for hardware duplication
3
100 MGz
LINC SYNC
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadsnetc LAO 110805
3 4
6 5 2
Figure notes: 1. CNA (also LAN for nondedicated control network) Eth0 2. Services port Eth1 3. Duplication cable (crossover) Eth2 4. CNB (if used) Eth3 5. LAN (if dedicated control network) Eth4 6. CNC (if used) Eth5 7. Fiber duplication cable
Issue 2.1 June 2006
1009
Figure 73: Duplication and control network cables for software duplication
3
100 MGz
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadsnetb LAO 092305
3 4
6 5 2
Figure notes: 1. Duplication cable (Crossover) Eth0 2. Services port Eth1 3. CNA (also LAN for nondedicated control network) Eth2 4. CNB (if used) Eth3 5. LAN (if dedicated control network) Eth4 6. CNC (if used) Eth5

To access the media server: 1. Clear the ARP cache from the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 967 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect CAT5 cable. 3. On your laptop computer, click Start > Run to open the Run dialog box, 4. Type ping 192.11.13.6. Press Enter to check connectivity between the Services laptop and the media server. 5. Wait at least 3 minutes after turning on the media server before starting a Telnet session to access the information on the CD.

Note:
Issue 2.1 June 2006
1011
Accessing the second S8720 Media Server

To access the second S8720 Media Server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 967 and return here. 2. Open a browser and connect to the media server. 3. Log in. For more information, see Accessing the media server maintenance web interface on page 953. 4. Suppress all alarms.

To check the software release:
On the Maintenance Web Interface, click Software Version to see what software release is running on the media server.

To change the date and time: 1. On the Maintenance Web Interface, under Server, click Server Date/Time. 2. Change the date, time, and time zone as needed. 3. Click Submit to effect the changes.
Copying files to the second S8720 Media Server (if any)

If a software update (service pack) is required, you must copy the update file from the services laptop to the media server. Note: You do not need to download a license file to this media server. The license will shadow over from the other media server.
Note:
Firmware updates for programmable circuit packs and media modules might also be required. These files might be on the software CD. Note: Do not copy the Linux migration upgrade set using this method.
Note:
To copy files to the media server: 1. On the Maintenance Web Interface, under Miscellaneous, select Download Files. 2. Select File(s) to download from the machine Im using to connect to the server. 3. Click Browse next to the top field to open the Choose File window on your computer. 4. Find the files that you need to copy to the media server. 5. Click Download to copy the file(s) to the media server. The system automatically copies the files to the default location on the media server.
Issue 2.1 June 2006
1013
Activating the software update (if any)

Note:
Note: Skip this procedure if there is no Communication Manager software update file to install. Note: On the second media server, you do not need to install the license and authentication files. These files will shadow in from the active media server.
Note:
To use an SSH session to unpack and install the software update file. 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft. 3. Type update_unpack. Press Enter. 4. Select the update by number. Press Enter. 5. Type update_show. Press Enter to list Communication Manager files to verify the new software update file was unpacked. 6. Type update_activate update, where update is the update ID number produced by update_show. An example can be 00.0.411.7-xxxx. Do not use the .tar.gz extension at the end of the file name. Press Enter. The media server might reboot (reset system 4). If it reboots, it also might display the message /opt/ecs/sbin/drestart 2 4 command failed. Ignore this message. You must wait until the restart/reset completes before entering additional commands. The media server displays a message that the software update (patch) was applied. 7. Type update_show again. Press Enter to list Communication Manager files to verify the new software update file was activated.
Stopping Communication Manager on the second S8720 Media Server

To stop Communication Manager:
Type stop -acf. Press Enter to stop Communication Manager.
Configuring to allow restoring configuration data and translations from the ftp server on the network
!
Important:
Important: If you backed up files to the services laptop or the USB-connected Compact Flash, do not perform this procedure. Go to Configuring to allow restoring configuration data and translations from flash card or Services laptop on page 992.
If you backed up to the customer network, you must readminister the Ethernet port connecting to the network. You must have the host name, IP address, subnet mask and default gateway for the two media servers and the active server and the IP address for the Ethernet port connecting to the customers network. To configure the network parameters: 1. Under Server Configuration, click Configure Server to open the first page of the Configure Server process. The system displays the Select Server type window. 2. Select the appropriate server type (IP-PNC or fiber-PNC). Click Continue. If you are unsure of the server type, see Recording the server connection type on page 957. 3. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 4. Select Configure individual services. Click Continue. 5. Click Set Identities from the main menu. 6. On the Set Server Identities window:

7. In the Configure Ethernet Interfaces window, fill in the correct IP addresses, Gateway, and Subnet mask (or use the default addresses) for the Ethernet port connected only to the customer LAN and select AUTOSENSE for the speed. This is because CNA, CNB, and duplication values will be populated by the restore function. Click Change to update the media server. When the screen shows Successfully configured ethernet interfaces. The Ethernet ports are configured. 8. Click Close Window to close the Configure Server wizard. Go to Verifying connectivity from the first S8720 Media Server to the network server on page 993.
Issue 2.1 June 2006
1015
Configuring to allow restoring configuration data and translations from flash card or Services laptop
If you backed up to the USB-flash card or the Services laptop, you must configure the server type, name, and the number to prepare for the restore procedure. To configure to allow restoring configuration data and translations from the flash card or the Services laptop: 1. Under Server Configuration, click Configure Server to open the first page of the Configure Server process. The system displays the Select Server type window. 2. Select the appropriate server type (IP-PNC or fiber-PNC). Click Continue. If you are unsure of the server type, see Recording the server connection type on page 957. 3. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 4. Select Configure individual services. Click Continue. 5. Click Set Identities from the main menu. 6. On the Set Server Identities window:

7. In the Configure Ethernet Interfaces window, select AUTOSENSE for the speed. Click Change to update the media server. When the screen shows Successfully configured ethernet interfaces. 8. Click Close Window to close the Configure Server wizard. Go to Restoring configuration data and translations to the first S8720 Media Server on page 993.
Verifying connectivity to the network server

To verify that the Ethernet port is working, ping from the media server the network server where the backup files are stored. Note: You might need to restart your browser before doing the next steps. 1. Under Diagnostics, click Ping. 2. Select Host Name or IP Address and type the IP address of the server where the system files are stored 3. Click Execute Ping. If you can successfully ping the server, you can proceed to restore the backed up sets of files.
Note:
Restoring configuration data and translations to the second S8720 Media Server
Note:
Note: The physical connections to the Ethernet ports must match the server configuration assignments that were backed up in Backing up the active S8700 or S8710 Media Server on page 958. The connections to the Ethernet ports that do not match the configuration can prevent access to the server.
The restore method depends on how you backed up the data. Currently there are three ways to restore backed up data.
Restoring data based up to the Compact Flash card (applicable only if migrating from an S8710 Media Server) Restoring data backed up to the customer network (applicable only if migrating an S8700 or S8710 Media Server) Restoring data backed up to the Services laptop (applicable only if migrating from an S8700 or S8710 Media Server)
Issue 2.1 June 2006
1017
In Migration to S8720, Release 3.1 or later, using Web interface, View/Restore on page 1018, the restore procedure is dependent on what backup method was used. Table 19: Migration to S8720, Release 3.1 or later, using Web interface, View/Restore S8700 or S8710 Release 1.2 1.3 1.3.1 1.3.2 2.0 2.0.1 2.1 2.1.1 2.2 2.2.1 3.0 3.0.1 Load 02.0.110.4 03.0.526.5 03.1.531.0 03.2.536.1 00.0.219.0 00.1.221.1 01.0.411.7 01.1.414.1 02.0.111.4 02.0.118.0 00.0.340.3 00.1.346.0 upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. upgrade..tar.gz. full..tar.gz. full..tar.gz. File Name of Backup
Restoring data backed up to the Compact Flash card

Note: This procedure is applicable only if migrating from an S8710 Media Server.
Note:
To restore data based up to the Compact Flash card: 1. On the Maintenance Web Interface, click View/Restore Data. The system displays the View/Restore Data window. 2. Under the View current backup contents in section, click Local PC Card. 3. Click View.
4. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file might be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 5. Click Restore. 6. Click Check Status view the restore progress.
Restoring data backed up to the customer network

To restore data backed up to the customer network from S8700 or S8710 Media Servers: 1. On the Maintenance Web Interface, click View/Restore Data. The system displays the View/Restore Data window. 2. Under the View current backup contents in section, click FTP. 3. Fill in the following fields for where you are backing up the files:

4. In the Method section, select FTP. 5. Click View. 6. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file could be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 7. Click Restore. 8. Click Check Status view the restore progress.
Restoring data backed up to the Services laptop

To restore data backed up to the Services laptop from S8700 or S8710 Media Servers: 1. On the Maintenance Web Interface, under Miscellaneous, click Download Files. The system displays the Download Files window. 2. Click Files to download from the machine Im using to connect to the server. 3. Click Browse to the location where the backup file is located.
Issue 2.1 June 2006
1019
4. Click Open. 5. Click Download. 6. On the Download Files Results window, watch for the following message: The following files have been successfully downloaded to the server. The files are now on the /var/home/ftp/pub directory. 7. Click View/Restore Data. The system displays the View/Restore Data window. 8. Under the View current backup contents in section, click Local Directory and accept the local default value. 9. Click View. 10. In the View/Restore Data Results window, select the file name to restore and select both force options. For example, the file might be called full_custservname_timestamp_datestamp.tar.gz where custservname is the customer server name from which Communication Manager is backed up. 11. Click Restore. 12. Click Check Status view the restore progress. The backup procedures are different depending on the software release currently running on your media server.
Verifying the second S8720 Media Server configuration

To verify the media server configuration: 1. Under Server Configuration, click Configure Server to start the configure server process. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 3. Select Configure all services using the wizard. Click Continue. 4. On the Set Identities page, under the Select Server Duplication area, select either:

This is a duplicated server using duplication hardware This is a duplicated server using software-based duplication This is a duplicated server using encrypted software-based duplication
Note:
Note: The physical connections to the Ethernet ports are different for hardware duplication and software duplication. For more information, see Connecting the cables to the first S8720 Media Server on page 983.
5. Click Continue. Note: The following step applies only if you are using software duplication. 6. On the Configure Interface page, set the speed for Ethernet 0: Server Duplication Link to either:

Note:
AUTO SENSE 1 Gigabit full duplex
7. Click Continue through all the screens, checking for new screens and new fields on existing screens as mentioned in the Software Release Letter. Note: You must click through all the screens whether there are changes or not. 8. On the Configure ESS window:
Note:
If the server is a primary control main, click This is NOT an enterprise survivable server If the server is an ESS server, click This is an enterprise survivable server (ESS)
9. Click Continue. 10. When you complete all the new fields, as necessary, click Continue on the Update System screen. The Update System screen shows each configuration task as the task completes. When done, the screen shows the line All configuration information was entered. 11. Click Close Window to close the Configure Server wizard. 12. Disconnect from the media server.
Rebooting the second S8720 Media Server

Reboot is necessary to initialize server settings that are restored but not yet activated. To reboot the second S8720 Media Server: 1. On the Maintenance Web Interface, under Server, click Shutdown Server. The system displays the Shutdown Server window. 2. Make the following selections:

Select Immediate Shutdown Select Restart Server after Shutdown
3. Click Shutdown.
Issue 2.1 June 2006
1021
Accessing the second S8720 Media Server

To access the second S8720 Media Server: 1. Open a browser and connect to the media server. 2. Log in. For more information, see Accessing the media server maintenance web interface on page 953. 3. Suppress all alarms.
Confirming the product ID on the first S8720 Media Server

To confirm the Product ID: 1. Use the PuTTY application to reaccess the server using the secure shell (SSH) protocol. 2. Log in as craft or dadmin. 3. At the prompt, type productid. Press Enter. The productid should match the value record in Obtaining the Product ID on the active S8700 or S8710 Media Server on page 965. If value does not match, escalate the problem immediately.
Enabling CNC, if necessary

If the CNC status in Checking the CNC status on page 957 is Control Network C has been configured, do this procedure. Otherwise, go to Initializing Communication Manager on page 1022. If using Control Network C (CNC):
Type cnc on. Press Enter.
Initializing Communication Manager

To initialize Communication Manager: 1. Type stop -acf. Press Enter to stop Communication Manager. 2. Type start -ac. Press Enter to start Communication Manager and load the translations.
Performing an integrity check on the second S8720 Media Server

To perform an integrity check on the second S8720 Media Server: 1. On the Maintenance Web Interface, under Diagnostics, click Ping. The system displays the Ping window. 2. Under Endpoints to Ping, click Other server(s), All IPSIs, UPS(s), Ethernet switches and click Execute Ping. If this ping fails, see Maintenance Procedures for Avaya Communication Manager 3.1, Media Gateways and Servers (03-300432). 3. Click Server > Status Summary. The system displays the Status Summary window. 4. Verify the following: Mode: BUSY OUT Server Hardware: okay Processes: okay 5. Select Server > Process Status. The system displays the Process Status window. 6. Under Frequency, click Display Once. 7. Click View. 8. Verify all operations are Up except ENV can be off. 9. Telnet to a device outside the media server and ping the media server. 10. Under IPSI Firmware Upgrades, click IPSI Version. The system displays the IPSI Version window. 11. Under Query Type, click Query All and click View to verify connectivity to all IPSIs.
Issue 2.1 June 2006
1023
Connecting the duplication cables

To connect the duplication cables:
Connect the duplication cables as described in the following table. Software Memory Duplication (see S8720 duplication and control network cables for software duplication on page 1026)
Control Network
Hardware Memory Duplication (see S8720 duplication and control network cables for hardware duplication on page 1025)
Dedicated
Duplication to Eth0 (on server, labeled 1)
Duplication to Eth2 (1st from left on quad NIC) Fiber to DAL1 card
Figure 74: S8720 duplication and control network cables for hardware duplication
3
100 MGz
LINC SYNC
2
100 MGz
iLO
2
2 1
UID
6
VDCI
133 MGz
2
3
3
100 MGz
LINC SYNC
2
100 MGz
iLO
1
2 1
UID
1
133 MGz
VDCI
3 1 5
Figure notes: 1. CNA (also LAN for nondedicated control network) Eth0 2. Duplication cable (Crossover) Eth2 3. CNB (if used) Eth3 4. LAN (if dedicated control network) Eth4 5. CNC (if used) Eth5 6. Fiber duplication cable
h3df87hd LAO 103105
Issue 2.1 June 2006
1025
Figure 75: S8720 duplication and control network cables for software duplication
3
100 MGz
2
100 MGz
iLO
2
2 1
UID
1
133 MGz
VDCI
1
3
3
100 MGz
2
100 MGz
iLO
1
2 1
UID
1
133 MGz
VDCI
2 3
5
h3df87sd LAO 103105
Figure notes: 1. Duplication cable (Crossover) Eth0 2. CNA (also LAN for non-dedicated control network) Eth2 3. CNB (if used) Eth3 4. LAN (if dedicated control network) Eth4 5. CNC (if used) Eth5
Releasing the second S8720 Media Server

To release the second S8720 Media Server: 1. On the Maintenance Web Interface, click Server > Release Server. The system displays the Release Server window. 2. Click Release.
Verifying the second S8720 Media Server is in standby state

To verify the second S8720 Media Server is in a standby state: 1. On the Maintenance Web Interface, click Server > Status Summary. The system displays the Status Summary window. 2. Verify the Mode field is Standby. 3. Check the following:

Standby Busied is no Standby Refreshed is yes Standby Shadowing is on
4. To verify the process status, click Server > Process Status. The system displays the Process Status window. 5. Under Frequency, click Display Once. 6. Click View. 7. Verify all operations are Standby except ENV that can be off.


Disconnecting from the second S8720 Media Server

Disconnect the Services laptop from the second S8720 Media Server.
Issue 2.1 June 2006
1027
On the active (first) S8720 Media Server

This section describes the procedures you must perform on the active (first) S8720 Media Server.
Accessing the active media server

To access the active media server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Connecting to the active media server on page 950 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect CAT5 cable. 3. Open a browser and connect to the active media server. 4. Log in. For more information, see Accessing the media server maintenance web interface on page 953.
Resolving alarms
To resolve alarms: 1. Under Alarms and Notification, click Current Alarms. The system displays the Current Alarms window. 2. Select the server alarms to be cleared. Click Clear. 3. Resolve new alarms since the migration with SAT commands. For more information, see:
Maintenance Commands for Avaya Communication Manager 2.1, Media Gateways and Servers Maintenance Alarms for Avaya Communication Manager 2.1, Media Gateways and Servers
Enabling scheduled maintenance

To schedule daily maintenance:
Reset the settings that were recorded in Disabling scheduled maintenance on page 955.
On the active (first) S8720 Media Server
Saving translations
To save translations:
Type save translation all. Press Enter. If this operation is unsuccessful, follow the normal escalation procedures before continuing.
Backing up files on the active S8720 Media Server

To back up files on the active media server: 1. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup. 3. Under Backup Method, select the backup method. 4. Click Start Backup to start the back up process.


Disconnecting from the active S8720 Media Server

Disconnect the Services laptop from the active media server.
Issue 2.1 June 2006
1029

This section describes the procedures you must perform on the standby S8720 Media Server.

To access the standby media server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 967 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect CAT5 cable. 3. Open a browser and connect to the active media server. 4. Log in. For more information, see Accessing the media server maintenance web interface on page 953.
Resolving alarms
To resolve alarms: 1. Under Alarms and Notification, click Current Alarms. The system displays the Current Alarms window. 2. Select the server alarms to be cleared. Click Clear.
Backing up files on the standby S8720 Media Server

To back up files on the standby media server: 1. Under Data Backup/Restore, click Backup Now. The system displays the Backup Now window. 2. Under Data Sets, click Full Backup. 3. Under Backup Method, select the backup method. 4. Click Start Backup to start the back up process.



Disconnect the Services laptop from the standby media server.

This section describes the procedures you must perform to complete the migration.
Registering the system

Follow the existing process and procedures to register the Avaya S8720 Media Server.
Removing customer files from the Services laptop

Remove the customer Linux migration upgrade set from the services laptop.
Issue 2.1 June 2006
1031
Interchanging media servers (optional)

This section describes the procedures you must perform to interchange the media servers.

To access the standby media server: 1. Clear the ARP cache on the laptop if necessary. For more information, see Clearing the ARP cache on the laptop computer on page 967 and return here. 2. Connect the laptop to the Services port (2) on the back of the media server with a cross-connect CAT5 cable. 3. Open a browser and connect to the active media server. 4. Log in. For more information, see Accessing the media server maintenance web interface on page 953.

To interchange the media servers to check capability of the standby media server to become the active media server: 1. Under Server, click Interchange Servers. The system displays the Interchange Servers window. 2. Verify the settings in the following fields:

Standby Busied: no Standby Refreshed: yes Standby Shadowing: on Duplication Link: up
3. Click Interchange. The system displays a confirmation message that the interchange has taken place. This media server is now the active media server.
Performing an integrity check on the active S8720 Media Server

To perform an integrity check on the active S8720 Media Server: 1. On the Maintenance Web Interface, under Diagnostics, click Server > Status Summary. The system displays the Status Summary window. 2. Verify the following: Mode: Active Server Hardware: okay Processes: okay 3. Select Server > Process Status. The system displays the Process Status window. 4. Under Frequency, click Display Once. 5. Click View. 6. Verify all operations are Up except ENV can be off.
Upgrading H.248 media gateways, LSPs, and ESSs (if being used)
If newer firmware exists for a configuration using H.248 media gateways, LSPs, or ESSs, and media modules, you must upgrade the firmware on them first. If the media server is the primary controller for a G700 Media Gateway equipped with an LSP or ESS, you must upgrade the software on the LSPs or ESSs before the migration. The correct order is: 1. Upgrade media gateway firmware to latest version 2. Upgrade media modules firmware to latest version 3. Upgrade media server software to latest version if using LSPs 4. Migrate to the S8720 Media Server.
Issue 2.1 June 2006
1033

Note:
Overview
Conversions
Overview
This section contains modules that describe conversion procedures for Linux-based systems. This section covers the following conversion paths:
Chapter 7: Converting PNs to IP-PNC on page 1041 - Converting some or all direct-connect port networks to IP-connect on page 1047 - Converting some or all CSS port networks to IP-PNC on page 1079 - Converting some or all ATM port networks to IP-PNC on page 1115
Chapter 8: Converting the Media Server Mode on page 1147 - Converting S8300 ICC mode to LSP mode on page 1157 - Converting S8300 LSP mode to ICC mode on page 1149 - Installing or converting to an S8500 LSP on page 1165 - Converting IP-PNC port networks with simplex control to duplicated control on page 1181 - Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only) on page 1201 - Converting software duplication link to a DAL1 link on an S8720 Media Server on page 1223 Note: For information on the following mode conversions, see the Avaya Enterprise Survivable Server (ESS) User Guide (03-300428) - S8500 Main to ESS - S8500 MBS to ESS - S8700 MBS to ESS - S8700 Main to ESS - S8700 ESS to Main
Note:
Issue 2.1 June 2006
1035
What is covered in the Conversions Section

Table 20 summarizes the conversion procedures this section covers. Table 20: Possible conversion paths To
All IP-PNC IP-PNC Mixed Fiber-PNC and IP-PNC S8300 mode S8500/S87xx mode
ICC
LSP
LSP
From
Dup. cont rol
Dup. bearer
DAL1 dup.
Configuration Conversions S8500 and S87xx Fiber-PNC1 S8500 and S87xx mixed fiber and IP-PNC
Mode Conversions S8300 LSP S8300 ICC S8500 Main S87xx simplex control S87xx simplex bearer S87xx software duplication
1. Fiber-PNC configurations for the S8700-series Media Server include direct connect, CSS, and ATM. Fiber-PNC configurations for the S8500 Media Server include only direct connect.
What is not covered in the Conversions Section

This section does not cover changes from a DEFINITY communications system to an IP-PNC or a fiber-PNC Linux-based system. For example, changes from a ProLogix, DEFINITY One, or an IP600 system to an IP-PNC or fiber-PNC Linux-based system are not covered in this section. These procedures are considered to be migrations and are covered in the Migrations section. In some cases, however, you might need to use the procedures from both sections.
Common conversion prerequisites

The following list of conversion prerequisites are common to all conversion modules covered in this section. Additional prerequisites that are unique to a specific module are contained in that module.
Presite checklist
The following checklist itemizes the information and materials you must collect, and the tasks you must perform, before you can go to the customer site.
Task Verify that your Services laptop has the appropriate hardware. Description Correct hardware components include: 32 MB RAM 40 MB of available disk space Cross-over Ethernet cables Direct Ethernet cable Serial cable and adapter RS-232 port connector Network interface card (NIC) with a 10/100 BaseT Ethernet interface 10/100 BaseT Ethernet, category 5 or better cross-connect cable with an RJ45 connector on each end, MDI to MDI-X CD-ROM drive Correct software components include: Windows 2000/XP operating system HyperTerminal or other terminal emulation program TCP/IP networking software, which is bundled with Windows OS Web browser: Internet Explorer 5.0 or later You must configure a network connection between your Services laptop and the server. For more information, see Accessing the media server. You might need to change your Services laptop browser settings to access the server remotely or directly. For more information, see Accessing the media server.
Verify that your Services laptop has the correct software.
Verify that your networking settings are correct. Verify that your web browser settings are correct
1 of 3
Issue 2.1 June 2006
1037
Task Obtain the appropriate logins and passwords for all equipment and software.
Description For example, obtain logins and passwords for the following components: Media server Media Gateway IPSI auxiliary equipment Communication Manager These logins and passwords include those logins and passwords for the customer equipment. Linux does not support logins that start with a number or asterisk. Use Avaya Terminal Emulator or Avaya Site Administration to perform a list logins command. You need the serial numbers if you are using a new license file or if you are updating an existing license file. The EPW is an Excel spreadsheet. The EPW provides the customer network information that you need to use the Avaya Installation Wizard to configure the control network components. Obtain the EPW from the Avaya project manager, Avaya software technician, or customer network administrator. A blank EPW is available at http://support.avaya.com/avayaiw/. The software CD-ROM contains firmware for the following circuit packs:

Verify that existing logins do not start with a number or an asterisk (*). Obtain the serial numbers of the media gateways and the media servers, if necessary. Verify that the EPW contains the required, customer-provided network information. Obtain a completed copy of the Electronic Preinstallation Worksheet (EPW) Verify that you have the current firmware files.
IPSIs MedPro CLAN VAL
For the most current versions, see Software & Firmware Downloads at http://avaya.com/support. Verify whether you need new license and authentication files. For more information on how to obtain license and authentication files, see License and authentication files on page 1039. You must install a new or an updated license file if you: Are changing the mode of the media server, including: - S8300 LSP to ICC or ICC to LSP
- S8500 or S8700 Main to ESS or ESS to Main - S8500 or S8700 MBS to ESS
Are installing TN2602AP Media Resource 320 circuit packs. The license file specifies the maximum number of available voice channels. Also need to install a new license file and a new authentication file because you are adding new purchased features.
2 of 3
Task Verify that you copied all necessary files to your Services laptop.
Description These files include: Converted translations files, if any Service pack files A new or updated license file A new authentication file The latest firmware for programmable circuit packs Call the ASG Conversant number, 800-248-1234 or 720-444-5557 and follow the prompts to obtain the password. You need the customer product ID for the FL or IL number.
For Avaya technicians directly connected with their laptop computers, obtain the static craft password that you need to login to the media server. Run the Automatic Registration Tool (ART) for the INADS IP address, if necessary. Verify that you have the correct cables to connect any new hardware. Verify that all existing circuit packs work with the new system. Verify that you have any new circuit packs that you need to replace older circuit packs.
Perform this step only if the configuration of the customer INADS alarming modem has changed. New connections might include: TN2312BP (IPSI) connection to the Ethernet switches
TN2302 or TN2306 connection to the LAN
See the Hardware and Software Compatibility Matrix (ftp// ftp.avaya.com/incoming/Up1cku9/tsoweb/media/ minhardwarevintages.pdf) and check the Minimum Vintage Table. Replace any TN799B/C CLAN circuit packs with the TN799DP.
3 of 3
License and authentication files

Note:
Issue 2.1 June 2006
1039



Additional documentation
Avaya recommends that you have the documents that are listed in Chapter 1: Introduction on page 51 on hand for the conversion. These documents are included on the documentation CD-ROM Documentation for Avaya Communication Manager, Media Gateways and Servers (03-300151).
Overview
Chapter 7: Converting PNs to IP-PNC

This chapter contains modules that describe how to convert some or all port networks (PNs) in an Avaya communications system from fiber-PNC to IP-PNC. These procedures assume that an S8500 or S8700-series media server running release 3.0 or later of Communication Manager controls the communications system. This chapter includes the following conversion modules:

Converting some or all direct-connect port networks to IP-connect on page 1047 Converting some or all CSS port networks to IP-PNC on page 1079 Converting some or all ATM port networks to IP-PNC on page 1115
!
Important:
Important: Avaya recommends that you perform a traffic analysis when changes from a fiber-PNC configuration to a mixed configuration that includes both fiber-PNC and IP-PNC PNs. A traffic analysis helps you understand Inter-PN bearer traffic and determine the correct number of media processor resources, other network parameters such as the use of network regions, codec sets, and VLANs. For more information, see Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600) and Administration for Network Connectivity (555-233-504).
Overview
The modules in this chapter provide procedures to convert fiber-PNC port networks (PNs) to IP-PNC PNs in an S8500 or an S8700-series communications system. Fiber-PNC PNs use the circuit-switched (TDM) protocol to transport bearer traffic (voice, fax, video) between PNs over fiber-optic cables. IP-PNC PNs use the packet-switched Internet Protocol (IP) to transport bearer traffic over Ethernet cables. Note: The term fiber-PNC (fiber port network connectivity) is used in this document with almost the same meaning as the term multiconnect. Multiconnect implies a dedicated control network and fiber-PNC PNs that carry the bearer traffic. The term fiber-PNC applies to configurations with either a dedicated or a nondedicated control network.
Note:
Issue 2.1 June 2006
1041
Converting PNs to IP-PNC
This chapter includes modules that describe how to convert the following three fiber-PNC configurations to full or partial IP-PNC configurations:
Direct connect In this configuration, one PN, the "control PN," is IPSI-connected to the control network, and one or two additional PNs are fiber-connected to the control PN. The call controller can be an S8500 Media Server or an S8700-series Media Server. The fiber connections are between the expansion interface (EI) circuit packs (TN570) in the PNs.
Center Stage Switch (CSS) In this configuration, all PNs are fiber-connected through the CSS and one or more PNs are IPSI-connected to the control network. The call controller is an S8700- series media server. The fiber connections are between the switch node interface (SNI) circuit packs (TN573) and the expansion interface (EI) circuit packs (TN570). The SNI circuit packs reside in a switch node carrier. The EI circuit packs reside in a PN. The fiber can also connect SNIs in two switch-node carriers.
Asynchronous Transmission Mode (ATM) In this configuration, all PNs are fiber-connected through the ATM switch, and one or more PNs are IPSI-connected to the control network. The call controller is an S8700 series media server. The fiber connections are between the ATM switch and the TN2305B or TN2306B ATM expansion interface circuit packs in the PNs.
The conversion procedures in this chapter apply to individual PNs in a communications system that is composed of one or more PNs. In the final converted system, the PNs can be either 100% IP-PNC or a mixture of fiber-PNC and IP-PNC.
Integrating IP-PNC PNs with fiber-PNC configurations

Starting with Communication Manager release 3.0, the system allows configurations that mix IP-PNC port networks (PNs) with existing fiber-connected CSSs, ATM networks, and direct-connected PNs. Both fiber-PNC and IP-PNC PNs can have either single or duplicated control networks. Only the fiber-PNC PNs can have duplicated bearer networks. A Communication Manager configuration can contain one of the following port network connectivity (PNC) combinations:

IP-PNC and direct-connect IP-PNC and CSS IP-PNC and ATM
Overview
Regardless of the combination of PNC methods, the maximum number of PNs allowed is 64. However, since a server can support IP-PNC and fiber-PNC PNs simultaneously, the following capacity rules apply to a configuration with both IP-PNC and fiber-PNC PNs:

With CSS, a configuration can include 2 to 44 CSS PNs, with an additional 20 IP-PNC PNs With ATM, a configuration can include 64 ATM and IP-PNC PNs in any combination With direct-connect, a configuration can include 2 or 3 direct-connect PNs, with 61 or 62 IP-PNC PNs Note: When you convert a system to IP-PNC, the Internet Protocol (IP) PNC? field on the Customer Options form the license file must be set to n. If this field is set to y, you cannot mix fiber-PNC and IP-PNC PNs or use SCC1 or MCC1 cabinets in the final configuration. If the final system is 100% IP-PNC and the configuration does not include SCC1 or MCC1 cabinets, this field can be set to either y or n. Avaya recommends n.
Note:
Media gateway combinations

The following table lists, by server, the media gateways and connection methods that you can configure within a mixed IP-PNC and fiber-PNC configuration. Table 21: Gateways supported in IP-PNC and fiber-PNC configurations Server Supported Central Gateways CMC1 G600 G650 SCC1 MCC1 IP-PNC Directconnect No No Yes Yes Yes CSS/ATMconnect No No No No No Reliabilities supported
S8500
Yes Yes Yes Yes Yes
Single control network and single bearer network Same as CMC1 with S8500 Same as CMC1 Same as CMC1 Same as CMC1 1 of 2
Issue 2.1 June 2006
1043
Table 21: Gateways supported in IP-PNC and fiber-PNC configurations (continued) Server Supported Central Gateways CMC1 G600 G650 IP-PNC Directconnect No No Yes CSS/ATMconnect No No Yes requires an MCC1 for CSS Yes requires an MCC1 for CSS Yes Reliabilities supported
S8700/ S8710/ S8720
Yes Yes Yes
Single control network and single bearer network Same as CMC1 with S8700-series - Single control and bearer - duplicated control - duplicated control and bearer Same as G650 with S8700-series
SCC1
Yes
Yes
MCC1
Yes
Yes
Same as G650 with S8700-series 2 of 2
Note:
Note: The TN2602 Media Resource 320 circuit pack is unavailable for installation in the CMC1 or the G600 media gateways.
Reliability levels
Avaya communications systems that are controlled by the S8500 media server have no duplication. This configuration is sometimes referred to as simplex reliability. Communications systems that are controlled by S8700-series media servers can have one or a combination of the following three duplication or reliability levels:
Duplex S8700-series media servers that are duplicated, which is the standard configuration
High Duplicated media servers and control network.
Critical Duplicated media servers, control network, and bearer network.
Overview
In a fiber-PNC configuration, the reliability level is an attribute of the communications system as a whole. For IP-PNC port networks, the reliability level is an attribute of the individual PNs. The converted communications system can include a mixture of fiber-PNC PNs and IP-PNC PNs. In a mixed system, the fiber-PNC PNs have a single reliability level, and each IP-PNC PN has its own reliability level. Therefore, no single reliability level can be attributed to a mixed fiber-PNC and IP-PNC configuration. Table 22 shows reliability options for the S8700 Series Media Server compared to reliability options for a DEFINITY R system.
:
Table 22: Reliability options for DEFINITY R and S8700 Series Reliability option Standard Duplex N/A

DEFINITY Server R One common control carrier per system, and single port network connectivity.

S8700 Series Media Server
N/A Two media servers Single control network One IPSI in each IPSI-connected PN Two online uninterruptible power supplies (UPSs) Single bearer connectivity Two media servers Duplicated control Network Two IPSIs in each IPSI-connected PN Two online UPS Single bearer connectivity Two media servers Duplicated control network Two IPSIs in each IPSI-connected PN Two online UPS Duplicated bearer connectivity
High
Two common control carriers, and single port network connectivity.
Critical
Two common control carriers, and duplicated port network connectivity.
Issue 2.1 June 2006
1045
Dedicated and nondedicated control networks

Control networks A and B can be separately configured for dedicated and nondedicated control networks. You can also use control network C for a nondedicated control network, while you use control networks A and B for dedicated control networks. Control network C uses the customer LAN exclusively for the control signaling. Control networks A and B can use either dedicated Ethernet switch connections or the customer LAN for control signaling. For more information about control networks and control network C, see Administration for Network Connectivity (555-233-204).
Introduction
Converting some or all direct-connect port networks to IP-connect
Introduction
This module describes how to convert port networks (PNs) with fiber port network connectivity (fiber-PNC) in a direct-connect configuration to Internet Protocol port network connectivity (IP-PNC). An S8500 Media Server or an S8700-series Media Server controls the PNs. This conversion changes the transmission of inter-PN bearer traffic from circuit-switched protocol over fiber connections to packet-switched IP over Ethernet connections.
!
Important:
Important: The S8700-series Media Servers must be running release 3.0 or later of Communication Manager before you start the conversion procedure. To upgrade the media servers, see the appropriate upgrade module in this book.
These procedures do not change the cabinet hardware as part of the conversion. All MCC1, SCC1, and G650 cabinets in the starting fiber-PNC configuration are present in the converted IP-connect configuration.
The starting configuration

The starting configuration consists of two or three fiber-PNC PNs. All PNs are fiber-connected, and one or more PNs are IPSI-connected to the control network. For Communication Manager release 3.0 and later, the starting configuration can include some IP-connect components in addition to the fiber-PNC components. Each PN can be implemented in an MCC1, an SCC1 stack, or a G650 stack. The overall system can be any combination of MCC1, SCC1, or G650 gateways. The reliability level of the starting configuration can be: Simplex: No duplication, the standard reliability for S8500 media servers Duplex: Duplicated media servers, the standard reliability for S8700-series Media Servers High: Duplicated media servers and control network, available for S8700-series Media Servers only Critical: Duplicated media servers, control network, and bearer network, available for S8700-series Media Servers only
Issue 2.1 June 2006
1047
The converted configuration

The final converted configuration can be all IP-connect or a mixture of IP-connect and fiber-PNC. For systems that are controlled by the S8500 media server, only simplex reliability, no duplication, is available. For systems that are controlled by the S8700-series Media Server, the IP-connect components can have high reliability, duplicated control networks and a critical reliability duplicated bearer network. The reliability level for the fiber-PNC portion of the converted system can also be duplex, high, or critical. The reliability level of the IP-PNC portion of the converted system is per PN and can be either duplex, high, or critical. That is, some IP-connect PNs can have duplicated control networks and/or duplicated bearer networks, while other IP-connect PNs have nonduplicated control networks. If synchronization is required for any of the IP-PNC PNs, the synchronization source must be administered separately for each IP-PNC PN.
!
Important:
Important: Avaya recommends that you perform a traffic analysis when changes from a fiber-PNC configuration to a mixed configuration that includes both fiber-PNC and IP-connect PNs. A traffic analysis helps you understand Inter-PN bearer traffic and determine the correct number of media processor resources, other network parameters such as the use of network regions, codec sets, and VLANs. For more information, see Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600) and Administration for Network Connectivity (555-233-504).
Configuration diagrams
Configuration diagrams on page 1071 provides sample before-and-after diagrams for the conversion of a direct connect configuration from fiber-PNC to IP-connect. Figure 76 and Figure 77 show typical starting and converted configurations for the direct-connect conversion scenario. For the starting configuration shown in Figure 76, the control network is duplicated and the bearer network is fiber-connected. For the converted configuration in Figure 77, the PNs are all IP-PNC with a duplicated control network. Note that the second Ethernet switch that is connected to PN <11> in Figure 77 is necessary only if the PN is remote from the media servers. Variations on these configurations include mixed-PNC and mixed-reliability starting and converted configurations.
Prerequisites
Prerequisites
This section lists the information and materials that you must have, and the tasks that you must perform before you can start the conversion.
Before you go on site

Before you go on site, you must:

Complete the Presite checklist on page 1037. Ensure that the Communication Manager software on the S8700-series Media Server is Release 3.0 or later.


Issue 2.1 June 2006
1049
Preconversion tasks
You must complete the following tasks before you start the conversion procedure. For more information on how to connect your services laptop to the media server, see Accessing the media server on page 1237.



Preconversion tasks
Resolving alarms


Note:
Issue 2.1 June 2006
1051
! CAUTION:
CAUTION:
Conversion Tasks
Before you start the conversion tasks, you must ensure that the S8700-series Media Servers are running Communication Manager release 3.1 or later. You must complete the following tasks to convert from a direct-connect configuration to an IP-PNC configuration.
!
Important:
Important: For more information on how to install the IPSI, the media processor, and the CLAN circuit packs, see Adding New Hardware Avaya S8500 and S8700 Series Media Servers (555-245-212).
Conversion Tasks
Conversion tasks checklist

The following checklist identifies the major tasks in the conversion procedure:

Changing direct-connect synchronization Adding new circuit packs Upgrading firmware on new circuit packs. Disabling PNC duplication. Removing fiber administration. Enabling PNC duplication. Removing fiber-related hardware. Administering PN synchronization. Completing post-conversion tasks
Changing direct-connect synchronization, if necessary

If you are not converting the PN that contains the direct-connect synchronization source, do not perform this procedure. Continue to Adding new circuit packs on page 1055. Note: The administration of synchronization for a direct-connect configuration is the same as for a CSS synchronization. For a direct-connect configuration, the synchronization commands and screens use CSS.
Note:
!
Important:
Important: Synchronization for a direct connect configuration is derived from a fiber-PNC PN. If you are converting only one PN to IP-connect, Avaya recommends that you do not convert the PN that contains the synchronization source. If you are converting the PN that contains the synchronization source, convert this PN last.
Issue 2.1 June 2006
1053
If you are converting the PN that contains the synchronization source, complete the following procedure to remove or change the synchronization source. 1. At the SAT, enter change synchronization css.
2. Perform one of the following actions to remove or change the synchronization source:
If you are converting all PNs to IP-connect, type blanks in the Primary and Secondary fields. If you are converting only one of the direct connect PNs to IP-PNC, and if two PNs remain fiber-connected, enter new circuit pack locations in the Primary and, optionally, the Secondary fields. Obtain these locations from the list of Circuit Packs Available for Synchronization below the Primary and Secondary fields. If you enter both primary and secondary synchronization sources, both locations must be from the same PN. Ensure that you select working sync sources from a PN that is not being converted to IP-PNC.
3. Click Submit. 4. Verify that the synchronization sources are updated correctly: 5. Perform one of the following actions:
If you are converting all PNs to IP-PNC and have blanked out the Primary and Secondary fields, enter list synchronization. Verify that the Primary and Secondary fields for CSS are blank. Then continue with Adding new circuit packs on page 1055. If some PNs remain fiber-connected, complete the following steps: a. Enter list synchronization.
Conversion Tasks
b. On the Synchronization Plan screen, note the Primary and the Secondary locations. c. Enter status synchronization.
d. On the Synchronization Status screen, the Source Physical Location field for CSS must show the same location that is listed as Primary on the Synchronization Plan screen. In this example, the location is 02B07. If the screen shows that the CSS uses the secondary synchronization source or the tone-board as the synchronization source, follow the troubleshooting guide for synchronization sources.
Adding new circuit packs

This section describes the following procedures:

Installing the new circuit packs on page 1058 Adding cables for the new circuit packs on page 1059 Administering the new circuit packs on page 1060 Note: For more information about how to install circuit packs, see Adding New Hardware Avaya S8500 and S8700 Series Media Servers (555-245-212).
Note:
Issue 2.1 June 2006
1055
Each IP-PNC port network must have a TN2312BP (IPSI) circuit pack and at least one media processor circuit pack. You must add these circuit packs to each PN that does not already have them. The media processor circuit packs can be either the TN2602AP IP Media Resource 320 or the TN2302AP IP Media Processor. The TN2602AP circuit pack provides higher capacities and allows for future duplication of the bearer PNC. You can install additional media processors to increase capacity. However, you can install no more than two TN2602 circuit packs in a PN. The need for additional media processor circuit pack depends on system configuration parameters such as the number of IP endpoints. Note: No other media processor circuit packs can be used for PNC duplication in Communication Manager release 3.1.
Note:
Depending on the system configuration, additional CLAN circuit packs (TN799DP) might also be needed. CLAN circuit packs (TN799DP) are required if the system supports IP endpoints, H.248 gateways, or other IP adjuncts. The number of CLAN circuit packs that you need depends on system parameters such as the number of IP endpoints and the desired level of availability.
!
Important:
Important: If the final configuration mixes fiber-PNC PNs and IP-connect PNs, at least one PN in the fiber-PNC portion of the system must have both of the following circuit packs: - A TN570 EI circuit pack - Either a TN2302 or a TN2602AP media processor circuit pack This PN acts as the "gateway port network."
Designating the slots for the new circuit packs

Note: In older MCC1, SCC1, and G600 gateways, you might need to replace the backplane I/O cables with the newer 100-mbps cable. This cable is provided in the I/O cable kit. The comcode for this kit is 700234032. For more information on how to replace the backplane cables, see Replacing the I/O cables on page 1075.
Note:
Designate the slot in which each new IPSI, media processor, and CLAN circuit pack is to be installed. Each of these circuit packs requires an I/O adapter. The I/O adapter is installed on the backplane connector that is associated with the slot in which the circuit pack is installed.
!
Important:
Important: The adapters for the three types of circuit packs are different and not necessarily interchangeable. Also, the adapters for the TN2302AP and TN2602AP media processor circuit packs are different. Ensure that you use the adapter that corresponds to each type of circuit pack.
Conversion Tasks
You can install the media processor and the CLAN circuit packs in any universal port slots. However, for SCC1 and MCC1 carriers, you must place the media processors in the slots that the EI circuit packs formerly occupied. You must place the IPSI circuit packs in the slots that are specified in the following table. IPSI slot locations
Slot Number Carrier or Gateway Primary Secondary, if duplicated control, for S8700 series only B01 B01 Tone Clock slot (A00) Tone Clock slot (A00) E02 Tone Clock slot (A00) B02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 E02 B01 B01 D01 Control duplication is not supported with three PNs. D01 (duplicated control)
G650 stack SCC1 EPN MCC1 EPN containing one PN MCC1 EPN containing two PNs
A01 A00
MCC1 EPN containing three PNs
MCC1 EPN containing four PNs
Control duplication is not supported with four PNs
D01 (duplicated control)
MCC1 EPN containing five PNs
Control duplication is not supported with five PNs
Issue 2.1 June 2006
1057
Installing the new circuit packs

!
Important:
Important: In some cases, you might need to remove an existing circuit pack from a slot before you install the new circuit pack. Remove these existing circuit packs last, after you install, cable, and administer all the new circuit packs that go into empty slots. To remove existing circuit packs, follow the procedures in Disabling PNC duplication, if necessary on page 1066 and Removing fiber-related administration on page 1066. Tip:
Tip:
The TN2312BP, TN2602AP, and TN799D circuit packs all support hot-plug-in. That is, they can be inserted into a live system without disrupting call processing.
Installing the IPSI circuit packs

Add the IPSI TN2312BP circuit packs to the slots that you designated for the IPSIs. To install an IPSI circuit pack: 1. Complete the following steps to replace the TN2182 tone clock circuit pack with an IPSI:
! CAUTION:
CAUTION:
The TN2312 IPSI must replace the TN2182 tone clock. Do not install the IPSI in addition to the tone-clock. Major system disruptions can occur if a PN contains both circuit packs.
!
Important:
Important: If the control network for this PN is duplicated, replace the standby tone clock first.
a. If the PN has duplicated control networks, and you replaced the standby tone-clock with an IPSI at location UUC, enter set tone-clock UUC,where UUC is the standby tone clock location. This command interchanges the active and standby tone clocks. b. Enter the SAT command busyout tone-clock UUC, where UUC is the standby tone clock location. c. Remove the standby TN2182 tone clock. 2. Insert the IPSI circuit pack into the slot that the tone clock previously occupied by. 3. Push firmly on the faceplate until the circuit pack is properly seated, then close the latch. 4. After about 1 minute, to open the SAT Circuit Packs screen, enter display circuit-pack cabinetnumber. Verify that the TN2312B circuit packs are shown in the appropriate slots. 5. If the IPSI replaced a tone clock, enter the SAT command enable tone-clock UUC, where UUC is the IPSI circuit pack location.
Conversion Tasks
For the S8700-series Media Servers only, you can include an additional IPSI in the PN for control duplication.
Installing the media processor circuit packs

Add the media processor circuit packs to the slots that you designated for media processors. To install a media processor circuit pack: 1. Insert the TN2602AP circuit pack into the slot that you previously prepared for the media processor. 2. Push firmly on the faceplate until the circuit pack is properly seated, then close the latch. 3. After about 1 minute, to open the SAT Circuit Packs screen, enter display circuit-pack cabinetnumber. Verify that the TN2312B circuit packs are shown in the appropriate slots.
Installing the CLAN circuit packs

Add the CLAN circuit packs to the slots that you designated for CLANs. To install a CLAN circuit pack: 1. Insert the TN799DP circuit pack into the slot that you previously prepared for the CLAN. 2. Push firmly on the faceplate until the circuit pack is seated, then close the latch. 3. On the SAT, open the Circuit Packs screen using display circuit-pack cabinetnumber and verify that the TN799DP circuit packs are shown in the appropriate slots.
Adding cables for the new circuit packs

IPSI circuit packs are connected to an Ethernet switch in the control network. Media processor and CLAN circuit packs are connected to the customer LAN.
!
Important:
Important: Each of the three types of circuit packs requires an I/O adapter that is connected to the backplane amphenol connector. The adapters for the three types of circuit packs are different and not necessarily interchangeable. Also, the adapters for the TN2302AP and TN2602AP media processor circuit packs are different. Ensure that you use the correct adapter that corresponds to each type of circuit pack.
Connecting IPSI cables

To connect an IPSI slot to the control network: 1. Connect the TN2312BP I/O adapter to the backplane amphenol connector that corresponds to the slot in which the TN2312BP is installed. 2. Connect a CAT5 or better Ethernet cable to the RJ45 connector on the IPSI adapter.
Issue 2.1 June 2006
1059
3. Connect the other end of the CAT5 cable to the Ethernet switch. 4. For the G650 gateway only, if the maintenance function is used, connect one end of the serial maintenance cable to the DB9 connector on the IPSI adapter. Connect the other end to the Emergency Transfer panel to provide 1 alarm output and 2 alarm inputs.
Connecting the media processor cables !

Important:
Important: If you are replacing a TN2302 with a TN2602, ensure that you replace the TN2302 I/O adapter with a TN2602 adapter.
To connect a media processor slot to the LAN: 1. Connect the medial processor I/O adapter to the backplane amphenol connector that corresponds to the slot in which the media processor circuit pack is installed. 2. Connect a CAT5 or better Ethernet cable to the top RJ45 jack on the media processor I/O adapter. This jack is labeled Port 1. 3. Connect the other end of the CAT5 cable to an RJ45 jack on the customer LAN.
Connecting CLAN cables

You can install the CLAN circuit packs in any universal port slot. To connect a CLAN slot to the LAN: 1. Connect the TN799DP I/O adapter to the backplane amphenol connector that corresponds to the slot in which the TN799DP is installed. 2. Connect a CAT5 or better Ethernet cable to the RJ45 jack on the TN799DP I/O adapter. 3. Connect the other end of the CAT5 cable to an RJ45 jack on the customer LAN.
Administering the new circuit packs

!
Important:
Important: In addition to the administration procedures described in this section, you might also need to adjust the administration of the network regions. Your planning documents might provide information about changes to network regions. For more information on how to administer network regions, see Administration for Network Connectivity, 555-233-504. Tip:
Tip:
To avoid the loss of new translations, save translations frequently during the administration process.
Conversion Tasks
Administering the IPSI circuit packs

To administer the TN2312BP circuit packs: Note: You must complete steps 1 and 2 just once for all IPSIs. Repeat the remaining steps for each IPSI. 1. If any of the IPSIs in the configuration are duplicated, enter change system-parameters duplication to set Enable Operation of IPSI Duplication to y. 2. Enter change system-parameters ipserver-interface to set the Switch Identifier for the IPSIs on this system. This identifier is usually A. If the identifier is not A, enter the correct value as a letter B to J in the Switch Identifier field and press Submit. Note: Repeat steps 3 and 4 for each new IPSI. 3. To add a new IPSI, enter add ipserver-interface n, where n is the PN number. 4. Perform one of the following actions, depending on whether you want to use DHCP addressing or static addressing. Use DHCP addressing usually with dedicated control networks. Use static addressing usually with nondedicated control networks.
Note:
Note:
For DHCP addressing:
Note:
Note: After you reseat the circuit pack, you must start the configuration operation within 5 seconds. a. Reseat the IPSI circuit pack to enable the recessed configuration button on the IPSI faceplate. b. To set the Switch ID and cabinet number, press the recessed button on the IPSI faceplate. When finished, continue with the next task, Setting the VLAN parameters and diffserv parameters on page 1062. Note: For more information about these settings, see Adding New Hardware Avaya S8500 and S8700 Series Media Servers (555-245-212).
Note:
For static addressing: a. Connect the services laptop to the Services port on the IPSI faceplate. b. Type telnet 192.11.13.6 to access the IPSI. c. At the IPSI prompt, enter ipsilogin to log in to the IPSI IP Administration Utility. d. Log in as craft and use the IPSI password e. Type set control interface ipaddr netmask to enter the static IP address and the netmask. f. Enter quit to save the changes and end the IPSI session.
Issue 2.1 June 2006
1061
g. Type 192.11.13.6 to access the IPSI, and log in again. h. Enter show control interface. The system displays the IP address, the subnet mask, and the default gateway information. Verify that the proper information was entered. i. If a default gateway is used, type set control gateway gatewayaddr where gatewayaddr is the customer-provided IP address for the network gateway. j. Enter quit to save the changes and end the IPSI session. k. Type 192.11.13.6 to access the IPSI, and log in again. l. Enter show control interface to verify the administration. m. Enter quit to end the IPSI session.
Setting the VLAN parameters and diffserv parameters

To set the VLAN parameters and diffserv parameters on the IPSI, if required: 1. Type telnet 192.11.13.6 to access the IPSI. 2. Enter show qos to display the quality of service values. 3. If necessary, use the following commands to set the VLAN parameters and the diffserv parameters to the recommended values: Note: Use Help to obtain syntax guidelines for these commands.

Note:
Enter set vlan priority 6 Enter set diffserv 46 Enter set vlan tag on Enter set port negotiation 1 disable Enter set port duplex 1 full Enter set port speed 1 100
4. Enter show qos to check the administered values. 5. Enter quit to end the IPSI session.
!
Important:
Important: Ensure that the port settings on the Ethernet switches are set to the same values as the values that appear in the set port commands.
Conversion Tasks
6. Use the following steps to reset the IPSI and exit the IPSI IP Admin Utility. a. Type telnet 192.11.13.6 to access the IPSI. b. Enter reset. c. Enter y in response to the warning. d. Disconnect the laptop from the IPSI. e. Verify that the LED display on the IPSI faceplate contains the letters I P and a filled-in V at the bottom. Repeat steps a through e for each of the other new IPSIs. Note: Clear the ARP cache on the laptop before you connect to another IPSI. To clear the cache, enter arp -d 192.11.13.6 at the Windows command prompt.
Note:

Tip:

Issue 2.1 June 2006
1063
Administering the media processor circuit pack

To administer the TN2602AP IP Media Resource 320: 1. From the active media server, log on to a SAT session. 2. To verify that the TN2602AP is correctly registered in the installed location, enter list configuration board UUCSS. 3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support Web site, you must upgrade the TN2602AP firmware. 4. To check the Maximum TN2602AP VoIP Channels field, enter display system-parameters customer-options, and go to page 2. 5. Verify the number of TN2602 circuit packs with 80 VoIP channels and the number of TN2602 circuit packs with 320 VoIP channels. 6. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN2602APs. 7. For each new TN2602AP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN2602AP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank. 8. To test connectivity to the IP endpoints through each TN2602AP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN2602AP. UUCSS is the cabinet, carrier, and slot location of the TN2602AP. 9. Repeat step 8 for another IP endpoint on a different subnet. 10. Make an external trunk call to a telephone on the port network and leave the call active. 11. To verify call processing, enter status media-processor board UUCSS. The Media Processor Status screen appears. 12. Look at the LINKS and DSP CHANNEL STATUS categories to determine whether the call is being processed.
Note:
Administering the CLAN circuit pack

To administer the TN799DP circuit pack: 1. From the active media server, log on to a SAT session. 2. To verify that the TN799DP is correctly registered in the installed location, enter list configuration board UUCSS.
Conversion Tasks
3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support web site, you must upgrade the TN799DP firmware. 4. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN799DPs. 5. For each new TN799DP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN799DP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank. 6. To display the Data Module screen, enter add data-module next. Enter ethernet in the Type field and complete the rest of the fields on the screen. 7. To test connectivity to the IP endpoints through each TN799DP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN799DP. UUCSS is the cabinet, carrier, and slot location of the TN799DP. 8. Repeat step 8 for another IP endpoint on a different subnet.
Note:
Upgrading firmware on the new circuit packs

The IPSI, the media processor, and the CLAN circuit packs that you added must have the latest available firmware installed. Check the firmware version that is installed on each circuit pack and compare with the latest version that is available on the Avaya Support Web site. If the circuit pack does not have the latest version installed, you must upgrade the firmware on that circuit pack. As part of the presite tasks, you copied the latest firmware to your laptop. If you did not copy the firmware, you must download the latest firmware files from the Avaya Support Web site at http://support.avaya.com.
Upgrading IPSI firmware, if necessary

For more information about how to upgrade the IPSI firmware, see Upgrading firmware on the IPSIs and SIPIs on page 283.
Upgrading media processor and CLAN firmware, if necessary

For more information about how to upgrade firmware on the TN2602AP or the TN799DP circuit packs, follow the instructions in Upgrading firmware on programmable TN circuit packs on page 293.
Issue 2.1 June 2006
1065
Disabling PNC duplication, if necessary

If the bearer network is duplicated, you must remove the duplication before you remove the fiber-optic connections. If the system does not have PNC duplication, continue with Removing fiber-related administration on page 1066. To remove PNC duplication, log in to the SAT and complete these steps: 1. Enter status pnc to check which of the duplicated PNCs is active. 2. If the B-PNC is active, enter reset pnc interchange to make the A-PNC active. 3. Enter busyout pnc-standby to busyout the standby PNC. 4. Enter change system-parameters duplication to open the duplication screen. 5. In the Enable Operation of PNC Duplication? field, enter n and press Submit.
Removing fiber-related administration

Before you can use the IP connections, you must remove the fiber administration for each PN that you are converting to IP-PNC. Complete the following steps at the SAT to busyout and remove the fiber links for each PN that you are converting to IP-PNC: Tip:
Tip:
To view the fiber link numbers and the endpoints, enter list fiber-link. 1. Enter busyout fiber-link n, where n is the link number for the fiber connection. 2. Enter remove fiber-link n. 3. Repeat steps 1 and 2 for each IP-PNC PN.
Enabling PNC duplication, if necessary

If the final configuration is a mixture of fiber-PNC and IP-PNC PNs and if the fiber- connect portion is duplicated, you must enable PNC duplication. To enable PNC duplication at the SAT: 1. Enter change system duplication to open the PNC Duplication screen. 2. Enter y in the Enable Operation of PNC Duplication? field and press Submit.
Conversion Tasks
Removing fiber-related hardware

Complete these steps for each PN that you are converting to IP-connect: 1. Remove the fiber cables that connect the EI circuit packs in the PNs. 2. Remove the TN570 expansion interface (EI) circuit packs from the port network carriers or gateways. 3. At the SAT, enter change circuit-pack. a. Enter blanks in the TN570 EI fields that correspond to the PNs that you converted to IP-connect. b. Press Submit.
Administering PN synchronization, if necessary

Perform this procedure if the PN that you just converted to IP-connect requires a synchronization source. To administer synchronization: 1. After the conversion, enter the SAT commands list synchronization and status synchronization to show the synchronization information for the IP-PNC PNs. The Primary and the Secondary fields on the Synchronization Plan screen and the Source Physical Location field on the Synchronization Status screen must be empty. 2. Enter change synchronization port-network n, where n is the PN number of the converted port network that requires synchronization.
Issue 2.1 June 2006
1067
Tip:
Tip:
Enter list cabinet to see a list of all the cabinets and the PNs that the cabinets contain.
3. In the Primary field, enter a synchronization-source circuit pack location. Obtain this location from the Circuit Packs Available for Synchronization list. Ensure that you choose a working synchronization source. In the example, location 03B03 is the primary synchronization source for PN 3. 4. Optionally, add another synchronization-source circuit pack location in the Secondary field. Obtain the location from the Circuit Packs Available for Synchronization list. 5. Press Submit. 6. Wait about 5 minutes for Communications Manager to update the synchronization plan. Then to check the changes, enter list synchronization and the status synchronization commands. 7. If the Switching Capability field for this PN is disabled on the Synchronization Status screen, enter enable synchronization-switch all. 8. To check for errors, enter test synchronization port-network n long. All listed ports must show PASS in the Results field. If the Results field does not show PASS, you must troubleshoot the synchronization error.
Postconversion tasks
Postconversion tasks
You must complete the following tasks after you complete the conversion tasks.



Resolving alarms
Issue 2.1 June 2006
1069

Note:
Note:


Figure 76: S8700-series direct-connect configuration with duplicated control network on page 1072 and Figure 77: S8700-series IP-connect configuration with mixed reliability on page 1074 show before and after diagrams for the conversion of a direct connect system from a fiber-PNC configuration to a mixed fiber-PNC and IP-connect configuration.
Issue 2.1 June 2006
1071
Figure 76: S8700-series direct-connect configuration with duplicated control network

1
Duplex ch 1 ch 2
1
disc
COMPACT
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1 2 UID
Simplex
Simplex
13
12 2
LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 18 20 22 24 LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 ROUT SYS PWR ROUT SYS PWR S1 S2 1 3 5 7 9 11 13 15 17 19 21 23 S1 S2 1 3 5 7 9 11 13 15 17
2
18 20 22 24 19 21 23
10 8 3 6
11
11
11 6
4 9
7 9 9
cycm3006 LAO 030505
Figure notes: S8700-series direct-connect configuration with duplicated control network

1. 2. 3. 4. S8700/S8710 Media Server. Ethernet switch. Direct-connect PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack), that consists of at least two media gateways or carriers. The figure show the G650 stack. PN control gateway or carrier in the A position. The gateway contains:
A TN2312AP/BP IPSI circuit pack for IP connection to the server.
NOTE: For the G650 Media Gateway, the BP version of the TN2312 is required in order to provide environmental maintenance.
Two TN570 EI circuit packs for bearer and control network connections to the other two PNs (if any).
5.
Duplicated expansion control gateway or carrier in the B position. The gateway contains a TN2312AP/BP IPSI circuit pack for IP connection to control network
1 of 2
Figure notes: S8700-series direct-connect configuration with duplicated control network

6. 7. PN (G650 Media Gateway stack, MCC1 Media Gateway, SCC1 Media Gateway stack), that consists of at least two media gateways or carriers. The figure shows a G650 stack and an SCC1 stack PN control gateway or carrier that contains two TN570 EI circuit packs for bearer and control network connections to the other two PNs. NOTE: One TN2182 tone clock circuit pack must also be present per PN if the PN consists of SCC1 or MCC1 Media Gateways. One maintenance-only TN2312BP IPSI circuit pack must be present per PN if the PNs consists of G650 Media Gateways. The control gateway or carrier is always in the A position in the MCC1 or gateway stack. 8. 9. 10. 11. IPSI-to-server control network connection through the Ethernet switch. TN 570/570 fiber connections between PNs. Customer LAN LAN connections of an optional TN2302AP IP Media Interface or a TN2602AP IP Media Resource 320 for IP-TDM voice processing, if any, and an optional TN799DP CLAN for control of IP endpoints NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs are optional for PNs in a direct-connect network and can be inserted into a port carrier as shown in the figure, the PN control carrier or the duplicated control carrier. However, the CLAN circuit pack is required for downloads of firmware updates. 12. 13. LAN connections of media servers for remote administration. Duplicated server links, including the link for translations transfer and the link for control data sharing.
2 of 2
Issue 2.1 June 2006
1073
Figure 77: S8700-series IP-connect configuration with mixed reliability

1
5 3 5 3 4 2 4 2
disc
COMPACT
Duplex ch 1 ch 2
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1
5
1 2 UID
10
2
2
18 20 22 24 19 21 23
Simplex
Simplex
3
LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 18 20 22 24 ROUT SYS PWR S1 S2 1 3 5 7 9 11 13 15 17 19 21 23
11
cycm3023 LAO 031405
This all IP-connect configuration was converted from a direct-connect configuration. PN <11> is located remotely from the S8700-series media servers. Control networks are duplicated for PNs <3>, but not for PN <11>.
Figure notes: S8700-series IP-connect configuration with mixed reliability
1. 2. 3. S8700, S8710, or S8720 Media Server Ethernet switch. IP-connect PN with a duplicated control network (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack), that consists of at least two media gateways or carriers. The figure shows the G650 stack.
1 of 2
Replacing the I/O cables
Figure notes: S8700-series IP-connect configuration with mixed reliability (continued)

4. PN control gateway or carrier in the A position that contains a TN2312AP/BP IPSI circuit pack for IP connection to the server. NOTE: For the G650 Media Gateway, the BP version of the TN2312 is required in order to provide environmental maintenance. 5. 6. 7. Duplicated expansion control gateway or carrier in the B position that contains a TN2312AP/BP IPSI circuit pack for IP connection to the control network IPSI-to-server control network connection by means of an Ethernet switch. LAN connections of a TN2302AP IP Media Interface or a TN2602AP IP Media Resource 320 for voice processing, and optional TN799DP CLAN for control of IP endpoints. NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs are optional for PNs in a direct-connect network and can be inserted into a port carrier, as shown in the figure, or in the PN control carrier or the duplicated control carrier. However, the CLAN circuit pack is required for downloads of firmware updates. 8. 9. 10. 11. Customer LAN. LAN connections of the media servers for remote administration. Duplicated server links, including the link for translations transfer and the link for control data sharing. Remote PN with nonduplicated control (G650 Media Gateway stack, MCC1 Media Gateway, SCC1 Media Gateway stack), that consists of at least two media gateways or carriers.The figure show the G650 stack.
2 of 2

On older MCC1, SCC1, and G600 media gateways or cabinets, you must replace the existing I/ O cables (WP-90753, LI) with twisted pair I/O cables. These I/O cables connect the backplane to the rear connector panel. The existing I/O cables have straight, not twisted, wires. These cables can be mostly white with two red or multicolored. If the cables have multicolored, tightly twisted wires, no replacement is necessary. To order the DEFINITY kit with twisted pair I/O cables, use comcode 700234032.
! CAUTION:
CAUTION:
Turn off power to the carrier or the media gateway before you replace the cables.
! CAUTION:
CAUTION:
When you add or replace any hardware and associated cables and adapters, ground yourself against electrostatic discharge (ESD). Always wear a grounded wrist strap.
Issue 2.1 June 2006
1075
To replace the existing I/O cables: 1. Perform one of the following actions:

If the configuration includes an MCC1 or an SCC1 Media Gateway, continue with step 2. If the configuration includes a G600 Media Gateway, you must remove the fan assembly to access the cables. Loosen the thumb screws on the fan assembly and pull it straight out (G600 Media Gateway fan assembly removal on page 1077). Leave the fan assembly off until you install all the wires.
2. Note the orientation of the existing 10 cables. The existing I/O cables can be white and red or multicolored. These cables are not twisted. 3. Remove the I/O cables that you want to replace from the backplane and the connector panel slots. 4. Install the twisted pair I/O cables onto the backplane in the place of the cables you just removed. Use the correct orientation (Proper orientation for the twisted pair I/O cables on page 1078). Observe the white outline that is printed on the backplane for the location of each connector. 5. View the cables from the "wiring" side of the twin connectors. That is, view the cables while you plug the cables into the backplane. Connectors oriented correctly for plug-in look like the cables in Proper orientation for the twisted pair I/O cables on page 1078. The circled pin locations are No-Connects." At the top there is an orange-black pair on the right and a violet-brown pair on the left. Do not install wires in these locations. If you are replacing I/O cables for all slot positions, plug all cables into the backplane. Then, match the "D" connector on each cable to the carrier frame. You must install the 50-position metal shell "D" connectors into the carrier frame. Also, from the rear of the media gateway, look at the pins. Ensure that the longer side of the "D" connector (pins 1 to 25) is toward the right . 6. Apply the 10/100 mbps label to the front of the carrier slot. Apply the label over the slot label that corresponds to the slot where you installed the twisted pair I/O cable. 7. For the G600 Media Gateway, replace the fan unit if you are not adding any media gateways. If you are adding more media gateways to the rack, leave the fan units off until you install all the TDM cables.
Figure 78: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
Issue 2.1 June 2006
1077
2 1
iodspair KLC 072602
Figure notes: 1. Top 2. No connects, no wires 3. Violet-brown 4. Orange-black 5. Bottom
Introduction
Converting some or all CSS port networks to IP-PNC
Introduction
This module describes how to convert one or more port networks (PNs) with fiber port network connectivity (fiber-PNC) using a center stage switch (CSS) to Internet Protocol port network connectivity (IP-PNC). An S8700-series Media Server controls the PNs. This conversion changes the transmission of inter-PN bearer traffic from circuit-switched protocol over fiber connections to packet-switched IP over Ethernet connections.
!
Important:
These procedures do not change the cabinet hardware as part of the conversion. All MCC1, SCC1, and G650 cabinets in the starting multiconnect configuration are present in the converted IP-PNC configuration. Note that for CSS starting configurations, the switch node carrier cannot be used in the converted configuration unless the carrier remains fiber-connected.

The starting configuration consists of Fiber-PNC PNs that use a CSS. All PNs are Fiber-PNC through the CSS and one or more PNs are IPSI-connected to the control network. For Communication Manager release 3.0 and later, the starting configuration can include some IP-PNC components in addition to the fiber-PNC components. Each PN can be implemented in an MCC1, an SCC1 stack, or a G650 stack. The overall system can be any combination of MCC1, SCC1, or G650 gateways. The reliability level of the starting configuration can be: Duplex: Duplicated media servers, the standard reliability for S8700-series Media Servers High: Duplicated media servers and control network, available for S8700-series Media Servers only Critical: Duplicated media servers, control network, and bearer network, available for S8700-series Media Servers only
Issue 2.1 June 2006
1079

The final converted configuration can be all IP-PNC or mixture of IP-PNC and fiber-PNC. The reliability level for the fiber-PNC portion of the converted system can be Duplex, High, or Critical. The reliability level of the IP-PNC portion of the converted system is per PN and can also be Duplex, High, or Critical. That is, some IP-PNC PNs can have duplicated control networks while other IP-PNC PNs have nonduplicated control networks. Still other can have duplicated bearer. See Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only) on page 1201. If synchronization is required for any of the IP-PNC PNs, the synchronization source must be administered separately for each IP-PNC PN.
!
Important:
Important: Avaya recommends that you perform a traffic analysis when changes from a fiber-PNC configuration to a mixed configuration that includes both fiber-PNC and IP-PNC PNs. A traffic analysis helps you understand Inter-PN bearer traffic and determine the correct number of media processor resources, other network parameters such as the use of network regions, codec sets, and VLANs. For more information, see Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600) and Administration for Network Connectivity (555-233-504).
Configuration Diagrams
on page 1105 provides sample before-and-after diagrams for the conversion of a CSS configuration from fiber-PNC to IP-PNC. For the starting configuration that is shown in Figure 80: A fiber-PNC configuration for an S8700-series CSS with duplicated control networks on page 1106, the control network is duplicated and the bearer network is fiber-connected through a CSS. The converted configuration that is shown in Figure 81: Mixed fiber-PNC and IP-PNC configuration for S8700-series with mixed reliability converted from CSS configuration on page 1108 is a mixture of fiber-PNC and IP-PNC PNs. Two of the PNs were converted to IP-PNC and the remaining PNs are fiber-connected through the CSS. All PNs after conversion, except PN 19, have duplicated control networks. Figure 82: Example of MCC1 Media Gateway with IP-PNC and mixed reliability on page 1110 shows an MCC1 that is converted to an IP-PNC configuration. The MCC1 contains three PNs:(1) carrier A, (2) carriers B and C, and (3) carriers D and E. PNs (2) and (3) have duplicated IPSIs and control networks and are thus at the high-reliability level. PN (1) has a single control network and is at the Duplex reliability level. Variations on these configurations include mixed PNC and mixed reliability starting and converted configurations.
Prerequisites
Prerequisites
Presite assumptions


T

Issue 2.1 June 2006
1081
Preconversion tasks



Prerequisites
Resolving alarms


The following steps prevent scheduled daily maintenance from interfering with the conversion. 1. On the SAT, enter change system-parameters maintenance. 2. If scheduled maintenance is in progress, set the Stop Time field to 1 minute after the current time. or If scheduled maintenance is not in progress, set the Start Time field to a time after the conversion will be completed. For example, if you start the conversion at 8:00 P.M. and it takes 4 hours, set the Start Time field to 23:59.
Issue 2.1 June 2006
1083

Note:
! CAUTION:
CAUTION:
Conversion Tasks
Conversion Tasks
Before you start the conversion tasks, you must ensure that the S8700-series Media Servers are running Communication Manager release 3.1 or later. You must complete the following tasks to convert from a CSS configuration to an IP-PNC configuration.
!
Important:
Important: For more information on how to install the IPSI, the media processor, and the CLAN circuit packs, see Adding New Hardware Avaya S8500 and S8700-series Media Servers (555-245-212).

The following checklist identifies the major task in the conversion procedure:

Changing CSS synchronization Adding new circuit packs Upgrading firmware on new circuit packs. Disabling PNC duplication. Removing fiber administration. Enabling PNC duplication. Removing fiber-related hardware. Refreshing the switch-node clock memory. Administering PN synchronization. Post-conversion tasks
Issue 2.1 June 2006
1085
Changing CSS synchronization, if necessary

If you are not converting the PN that contains the CSS synchronization source, skip to Adding new circuit packs on page 1088.
!
Important:
Important: Synchronization for a CSS configuration is derived from a connection through a PN connected to one of the SNI circuit packs in the switch node carrier. If you are converting only one PN to IP-PNC, Avaya recommends that you do not convert the PN that contains the CSS synchronization source. If you are converting the PN that contains the CSS synchronization source, convert this PN last.
If you are converting the PN that contains the synchronization source for the CSS, complete the following steps. 1. At the SAT, enter change synchronization css.
If you are converting all PNs to IP-PNC, type blanks in the Primary and Secondary fields. If you are converting only one of the CSS PNs to IP-PNC, and if some PNs remain fiber-connected, enter new circuit pack locations in the Primary and, optionally, the Secondary fields. Obtain these locations from the list of Circuit Packs Available for Synchronization below the Primary and Secondary fields. If you enter both primary and secondary synchronization sources, both locations must be from the same PN. Ensure that you select working sync sources from a PN that is not being converted to IP-PNC.
3. Click Submit.
Conversion Tasks
4. Verify that the synchronization sources are updated correctly: 5. Perform one of the following actions:
If you are converting all PNs to IP-PNC and have blanked out the Primary and Secondary fields, enter list synchronization. Verify that the Primary and Secondary fields for CSS are blank. Then skip to Adding new circuit packs on page 1088. If some PNs remain fiber-connected, complete the following steps: a. Enter list synchronization.
b. On the Synchronization Plan screen, note the Primary and the Secondary locations for CSS. c. Enter status synchronization.
d. On the Synchronization Status screen, the Source Physical Location field for CSS must show the same location that is listed as Primary on the Synchronization Plan screen. In this example, the location is 02B07. If the screen shows that the CSS uses the secondary synchronization source or the tone-board as the synchronization source, follow the troubleshooting guide for synchronization sources.
Issue 2.1 June 2006
1087


Installing the new circuit packs on page 1090 Adding cables for the new circuit packs on page 1092 Administering the new circuit packs on page 1093 Note: For more information about how to install circuit packs, see Adding New Hardware Avaya S8500 and S8700-series Media Servers (555-245-212).
Note:
Note:
!
Important:
Important: If the final configuration mixes fiber-PNC PNs and IP-PNC PNs, at least one PN in the fiber-PNC portion of the system must have both of the following circuit packs: - A TN570 EI circuit pack - Either a TN2302 or a TN2602AP media processor circuit pack This PN acts as the "gateway port network."
Conversion Tasks

Note:
!
Important:
Slot Number Carrier or Gateway Primary Secondary, if duplicated control, for S8700 series only B01 B01 Tone Clock slot (A00) Tone Clock slot (A00) E02 B01 B01 D01
A01 A00
1 of 2
Issue 2.1 June 2006
1089
IPSI slot locations (continued)

Slot Number Carrier or Gateway Primary Secondary, if duplicated control, for S8700 series only Control duplication not supported with 3 PNs. D01 (duplicated control)
Tone Clock slot (A00) B02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 E02
Control duplication not supported with 4 PNs
2 of 2

!
Important:
Tip:
The TN2312BP, the TN2602AP, and the TN799D circuit packs all support hot-plug-in. That is, you can be insert them into a live system without disrupting call processing.
Conversion Tasks

! CAUTION:
CAUTION:
!
Important:
a. If the PN has duplicated control networks, and you replaced the standby tone-clock with an IPSI at location UUC, enter set tone-clock UUC,where UUC is the standby tone clock location. This command interchanges the active and standby tone clocks. b. Enter the SAT command busyout tone-clock UUC, where UUC is the standby tone clock location. c. Remove the standby TN2182 tone clock. 2. Insert the IPSI circuit pack into the slot that the tone clock previously occupied by. 3. Push firmly on the faceplate until the circuit pack is properly seated, then close the latch. 4. After about 1 minute, to open the SAT Circuit Packs screen, enter display circuit-pack cabinetnumber. Verify that the TN2312B circuit packs are shown in the appropriate slots. 5. If the IPSI replaced a tone clock, enter the SAT command enable tone-clock UUC, where UUC is the IPSI circuit pack location. For the S8700-series Media Servers only, you can include an additional IPSI in the PN for control duplication.

Issue 2.1 June 2006
1091


!
Important:

To connect an IPSI slot to the control network: 1. Connect the TN2312BP I/O adapter to the backplane amphenol connector that corresponds to the slot in which the TN2312BP is installed. 2. Connect a CAT5 or better Ethernet cable to the RJ45 connector on the IPSI adapter. 3. Connect the other end of the CAT5 cable to the Ethernet switch. 4. For the G650 gateway only, if the maintenance function is used, connect one end of the serial maintenance cable to the DB9 connector on the IPSI adapter. Connect the other end to the Emergency Transfer panel to provide 1 alarm output and 2 alarm inputs.

Important:
To connect a media processor slot to the LAN: 1. Connect the medial processor I/O adapter to the backplane amphenol connector that corresponds to the slot in which the media processor circuit pack is installed.
Conversion Tasks
2. Connect a CAT5 or better Ethernet cable to the top RJ45 jack on the media processor I/O adapter. This jack is labeled Port 1. 3. Connect the other end of the CAT5 cable to an RJ45 jack on the customer LAN.


!
Important:
Tip:

To administer the TN2312BP circuit packs: Note: You must complete steps 1 and 2 just once for all IPSIs. Repeat the remaining steps for each IPSI. 1. If any of the IPSIs in the configuration are duplicated, enter change system-parameters duplication to set Enable Operation of IPSI Duplication to y. 2. Enter change system-parameters ipserver-interface to set the Switch Identifier for the IPSIs on this system. This identifier is usually A. If the identifier is not A, enter the correct value as a letter B to J in the Switch Identifier field and press Submit. Note: Repeat steps 3 and 4 for each new IPSI. 3. To add a new IPSI, enter add ipserver-interface n, where n is the PN number.
Note:
Note:
Issue 2.1 June 2006
1093
4. Perform one of the following actions, depending on whether you want to use DHCP addressing or static addressing. Use DHCP addressing usually with dedicated control networks. Use static addressing usually with nondedicated control networks.
Note:
Note:
For static addressing: a. Connect the services laptop to the Services port on the IPSI faceplate. b. Type telnet 192.11.13.6 to access the IPSI. c. At the IPSI prompt, enter ipsilogin to log in to the IPSI IP Administration Utility. d. Log in as craft and use the IPSI password e. Type set control interface ipaddr netmask to enter the static IP address and the netmask. f. Enter quit to save the changes and end the IPSI session. g. Type 192.11.13.6 to access the IPSI, and log in again. h. Enter show control interface. The system displays the IP address, the subnet mask, and the default gateway information. Verify that the proper information was entered. i. If a default gateway is used, type set control gateway gatewayaddr where gatewayaddr is the customer-provided IP address for the network gateway. j. Enter quit to save the changes and end the IPSI session. k. Type 192.11.13.6 to access the IPSI, and log in again. l. Enter show control interface to verify the administration. m. Enter quit to end the IPSI session.
Conversion Tasks


Note:
!
Important:
Note:
Issue 2.1 June 2006
1095

Tip:


To administer the TN2602AP IP Media Resource 320: 1. From the active media server, log on to a SAT session. 2. To verify that the TN2602AP is correctly registered in the installed location, enter list configuration board UUCSS. 3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support Web site, you must upgrade the TN2602AP firmware. 4. To check the Maximum TN2602AP VoIP Channels field, enter display system-parameters customer-options, and go to page 2.
Conversion Tasks
5. Verify the number of TN2602 circuit packs with 80 VoIP channels and the number of TN2602 circuit packs with 320 VoIP channels. 6. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN2602APs. 7. For each new TN2602AP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN2602AP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank. 8. To test connectivity to the IP endpoints through each TN2602AP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN2602AP. UUCSS is the cabinet, carrier, and slot location of the TN2602AP. 9. Repeat step 8 for another IP endpoint on a different subnet. 10. Make an external trunk call to a telephone on the port network and leave the call active. 11. To verify call processing, enter status media-processor board UUCSS. The Media Processor Status screen appears. 12. Look at the LINKS and DSP CHANNEL STATUS categories to determine whether the call is being processed.
Note:

To administer the TN799DP circuit pack: 1. From the active media server, log on to a SAT session. 2. To verify that the TN799DP is correctly registered in the installed location, enter list configuration board UUCSS. 3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support web site, you must upgrade the TN799DP firmware. 4. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN799DPs. 5. For each new TN799DP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN799DP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank.
Note:
Issue 2.1 June 2006
1097
6. To display the Data Module screen, enter add data-module next. Enter ethernet in the Type field and complete the rest of the fields on the screen. 7. To test connectivity to the IP endpoints through each TN799DP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN799DP. UUCSS is the cabinet, carrier, and slot location of the TN799DP. 8. Repeat step 8 for another IP endpoint on a different subnet.




If the bearer network is duplicated, you must remove the duplication before you remove the fiber-optic connections. If the system does not have PNC duplication, continue with Removing fiber-related administration on page 1099. To remove PNC duplication, log in to the SAT and complete these steps: 1. Enter status pnc to check which of the duplicated PNCs is active. 2. If the B-PNC is active, enter reset pnc interchange to make the A-PNC active. 3. Enter busyout pnc-standby to busyout the standby PNC.
Conversion Tasks
4. Enter change system-parameters duplication to open the duplication screen. 5. In the Enable Operation of PNC Duplication? field, enter n and press Submit.

Before you can use the IP connections, you must remove the fiber administration for each PN that you are converting to IP-PNC. Complete the following steps at the SAT to busyout and remove the fiber links for each PN that you are converting to IP-PNC: Tip:
Tip:
To view the fiber link numbers and the endpoints, enter list fiber-link. 1. Enter busyout fiber-link n, where n is the link number for the fiber connection. 2. Enter remove fiber-link n. 3. Repeat steps 1 and 2 for each IP-PNC PN.


Complete these steps for each PN that you are converting to IP-PNC: 1. Remove the fiber cables that connect the EI circuit packs in the PNs. 2. Remove the TN570 expansion interface (EI) circuit packs from the port network carriers or gateways. 3. At the SAT, enter change circuit-pack. a. Enter blanks in the TN570 EI fields that correspond to the PNs that you converted to IP-PNC. b. Press Submit.
Issue 2.1 June 2006
1099
Refreshing the switch-node clock memory, if necessary

Perform this procedure only if some PNs in the CSS remain fiber-connected and alarms were generated for the removed SNI (TN573) circuit packs. If you are converting all the PNs in a CSS to IP-PNC or if no alarms are present for the removed SNI circuit packs, continue with Post-conversion tasks on page 1103. If you do not convert all PNs in a CSS to IP-PNC, the switch-node clock might retain memory of the switch-node interface circuit packs. In this case, a major alarm SNI-PEER is generated.
Adding and removing the TN573

To clear the SN clock memory and prevent the alarms, use the change circuit-packs command to add, and then remove, the TN573 circuit pack. To add the TN573: 1. At the SAT, enter change circuit-pack n, where n is the cabinet number of the removed SNI circuit pack. 2. On the Circuit Packs screen, go to the carrier and the slot of the removed SNI circuit pack and enter TN573. 3. Press Submit. To remove the TN573 that you just added: 1. Enter change circuit-pack n 2. On the Circuit Packs screen, go to the carrier and the slot of the TN573 that you just added and type blanks in the field. 3. Press Submit.
Reseating the switch-node clock if alarms persist

Perform this task only if the SNI-PEER alarms continue after you complete the previous task, Adding and removing the TN573 on page 1100. If the alarms were cleared and have not returned, continue with Administering PN synchronization, if necessary on page 1101. If some PNs in the CSS remain fiber-connected, perform one of the following actions: Tip:
Tip:
To view the switch-node status, enter status switch-node.
If the configuration includes one CSS with one SN clock: 1. Enter busyout board UUCSS, where UUCSS is the location of the switch-node clock.
Conversion Tasks
2. Reseat the switch-node clock circuit pack (TN572). 3. Enter release board.
For one CSS with duplicated SN clocks: 1. Enter busyout board UUCSS, where UUCSS is the location of the standby switch-node clock. 2. Reseat the standby switch-node clock circuit pack (TN572). 3. Enter release board. 4. Enter set switch-node clock UUCSS, where UUCSS is the location of the currently-active standby switch-node clock. The active and the standby switch-node clocks are now interchanged. 5. Enter busyout board UUCSS, where UUCSS is the location of the standby switch-node clock. 6. Reseat the standby switch-node clock circuit pack. 7. Enter release board.
For more than one CSS: 1. Enter busyout pnc-standby. 2. Enter busyout board UUCSS, where UUCSS is the location of the switch-node clock in the standby CSS. 3. Reseat the standby switch-node clock circuit pack (TN572). 4. Enter release board 5. Enter release pnc-standby. 6. Enter reset pnc interchange. 7. Repeat steps 1 through 6 for each additional CSS.

Perform this procedure if the PN that you just converted to IP-PNC requires a synchronization source. To administer synchronization: 1. After the conversion, enter the SAT commands list synchronization and status synchronization to show the synchronization information for the IP-PNC PNs. The Primary and the Secondary fields on the Synchronization Plan screen and the Source Physical Location field on the Synchronization Status screen must be empty. 2. Enter change synchronization port-network n, where n is the PN number of the converted port network that requires synchronization.
Issue 2.1 June 2006
1101
Tip:
Tip:
Post-conversion tasks
You must complete the following task after you complete the conversion tasks.



Issue 2.1 June 2006
1103
Resolving alarms

Note:
Note:

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. 2. Log in as craft or dadmin. 3. Type almsuppress -n and press Enter to release alarm suppression. 4. Log off.

Figure 80: A fiber-PNC configuration for an S8700-series CSS with duplicated control networks on page 1106 and Figure 81: Mixed fiber-PNC and IP-PNC configuration for S8700-series with mixed reliability converted from CSS configuration on page 1108 show diagrams for the conversion of a CSS system from a fiber-PNC configuration to a mixed fiber-PNC and IP-PNC configuration. In this configuration, PNs <8> and <19> are converted from fiber-PNC to IP-PNC. The other PNs remain fiber-connected through the CSS.
Figure 82: Example of MCC1 Media Gateway with IP-PNC and mixed reliability on page 1110 shows a typical MCC1 gateway that is converted to IP-PNC with three IP-PNC PNs.This diagram is an example of an MCC1 with three IP-PNC PNs, one of which has a duplicated control network. The MCC1 is remote from the media servers and, thus, requires a second set of Ethernet switches.
Issue 2.1 June 2006
1105
Figure 80: A fiber-PNC configuration for an S8700-series CSS with duplicated control networks
Duplex ch 1 ch 2
disc
COMPACT
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1
5 3 5 3 4 2 4 2
1
5
1 2 UID
18
Simplex
17 2
2
18 20 22 24 19 21 23
15 7 8 16 3 7
5 16 4 14
10 16 9 6
13
11 13
11 13 13
Simplex
11
12
12
12
cycm3009 LAO 031405
Figure notes: An S8700-series CSS configuration with duplicated control networks

1. 2. 3. 4. S8700 or S8710 Media Server. Ethernet switch. MCC1 Media Gateway (CSS and PN). PN control carrier in the A position that contains:
A TN2312AP/BP IPSI circuit pack for IP connection to server. A TN570 EI circuit pack for bearer and control network connections to the switch node carrier (SNC).
5. 6. 7. 8. 9.
Duplicated control carrier in the B position that contains aTN2312AP/BP IPSI circuit pack for IP connection to a duplicated control network. SNC in the E position that contains multiple TN573B SNI circuit packs for EI connections to PNs. Dedicated IPSI-to-server control network connection through the Ethernet switch. IPSI-connected PN (G650 Media Gateway stack,MCC1 Media Gateway, or SCC1 Media Gateway stack that consists of at least two media gateways or carriers). The figure shows a G650 stack. PN control gateway or carrier in the A position that contains:
A TN2312AP/BP IPSI circuit pack for IP connection to server.
A TN570 EI circuit pack for bearer and control network connections to the SNC.
10. 11. 12.
Duplicated control gateway in the B position that contains a TN2312AP/BP IPSI circuit pack for IP connection to the server. Fiber-PNC PN (G650 Media Gateway stack, MCC1 Media Gateway, SCC1 Media Gateway stack) that consists of at least two media gateways or carriers. The figure shows a G650 and an SCC1 stack. PN control gateway or carrier in the A position that contains a TN570 EI circuit pack for bearer and control network connections to the SNI. NOTE: One TN2182 Tone Clock circuit pack must also be present per PN if the PNs consist of SCC1 or MCC1 Media Gateways. One maintenance-only TN2312BP IPSI circuit pack must be present per PN if the PN(s) consist of G650 Media Gateways.
13. 14. 15. 16.
TN 570/573B fiber connections between the PNs and the SNC TN 573B/570 fiber connections between the SNC and the A carrier of the MCC1, if the MCC1 is a PN. Customer LAN LAN connections of the following optional components:
TN2302AP IP Media Processor or TN2602AP IP Media Resource 320 for IP-TDM voice processing, if any TN799DP CLAN for control of IP endpoints, if any
NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs are optional for PNs in a CSS-connected network and can be inserted into a port carrier, as shown in the figure, the PN control carrier, or the duplicated control carrier. However, the CLAN circuit pack is required for downloads of firmware updates. 17. 18. LAN connections of media servers for remote administration. Duplicated server links, including the link for translations transfer and the link for control data sharing.
Issue 2.1 June 2006
1107
Figure 81: Mixed fiber-PNC and IP-PNC configuration for S8700-series with mixed reliability converted from CSS configuration
disc
COMPACT
Duplex ch 1 ch 2
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1
5 3 5 3 4 2 4 2
1
5
1 2 UID
18
17 2
2
18 20 22 24 19 21 23
15 7 7 8 16 7 7 7 16 4 3
Simplex
Simplex
14 10 16 9 6
19
11 13
11
12
12
cycm3024 LAO 031405
Figure notes: Mixed fiber-PNC and IP-PNC configuration for S8700-series with mixed reliability (converted from CSS configuration)
1. 2. 3. 4. S8700 or S8710 Media Server Ethernet Switch. MCC1 Media Gateway (CSS and PN) PN control carrier, in the A position that contains:
A TN2312AP/BP IPSI circuit pack for IP connection to server. A TN570 EI circuit pack for bearer and control network connections to the switch node carrier (SNC).
5. 6. 7. 8. 9.
Duplicated control carrier in the B position that contains a TN2312AP/BP IPSI circuit pack for IP connection to duplicated control network. SNC in the E position that contains multiple TN573B SNI circuit packs for EI connections to PNs. Dedicated IPSI-to-server control network connection through the Ethernet switch. IP-PNC PN with duplicated control networks (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack, consisting of at least two media gateways or carriers). The figure shows a G650 stack. PN control gateway or carrier in the A position that contains a TN2312AP/BP IPSI circuit pack for IP connection to server. NOTE: For the G650 Media Gateway, the BP version of the TN2312 is required in order to provide environmental maintenance.
10. 11. 12.
Duplicated control gateway, in the B position that contains a TN2312AP/BP IPSI circuit pack for IP connection to server. Fiber-PNC PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack), consisting of at least two media gateways or carriers. The figure shows a G650 stack and an SCC1 stack. PN control gateway or carrier in the A position that contains a TN570 EI circuit pack for bearer and control network connections to the SNI. NOTE: One TN2182 Tone Clock circuit pack must also be present per PN if the PNs consist of SCC1 or MCC1 Media Gateways. One maintenance-only TN2312BP IPSI circuit pack must be present per PN if the PNs consist of G650 Media Gateways.
13. 14. 15. 16.
TN 570/573 fiber connections between the PNs and the SNC TN 573B/570 fiber connections between the SNC and the A carrier of the MCC1, if the MCC1 is a PN Customer LAN LAN connections of TN2302AP IP Media Processor or a TN2602AP IP Media Resource 320 for voice processing, and optional TN799DP C-LAN for control of IP endpoints. The TN2302AP and/or TN2602AP media processor circuit packs are required for the IP-PNC PNs and optional for the fiber-PNC PNs. NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs can be inserted into a port carrier, as shown in figure, the PN control carrier, or the duplicated control carrier. However, the CLAN circuit pack is required for downloads of firmware updates.
17. 18. 19.
LAN connections of media servers for remote administration. Duplicated server links, including the link for translations transfer and the link for control data sharing. IP-PNC PN with a single control network (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack, that consists of at least two media gateways or carriers). The figure shows a G650 stack.
Issue 2.1 June 2006
1109
Figure 82: Example of MCC1 Media Gateway with IP-PNC and mixed reliability
disc
COMPACT
Duplex ch 1 ch 2
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1
5 3 5 3 4 2 4 2
1
5
1 2 UID
11
10
2
2
18 20 22 24 19 21 23
Simplex
Simplex
10
2
2
18 20 22 24 19 21 23
cycm3022 LAO 030505
Figure notes: Example of an MCC1 Media Gateway with IP-PNC and mixed reliability
1. 2. 3. 4. S8700 or S8710 Media Server. Ethernet switch. MCC1 Media Gateway. IP-PNC PN, with one expansion port carrier in the A position that contains:
A TN2312AP/BP IPSI circuit pack for IP connection to the server. A TN2302AP IP Media Processor or TN2602AP IP Media Resource 320 for IP-TDM voice processing An optional TN799DP CLAN for control of IP endpoints
1 of 2
Figure notes: Example of an MCC1 Media Gateway with IP-PNC and mixed reliability (continued)
5. IP-PNC PN, with two carriers, that contains:
An E-position control carrier with a TN2312AP/BP IPSI circuit pack for IP connection to server. A D-position duplicated control carrier with:
- A TN2312AP/BP IPSI circuit pack for IP connection to the server. - A TN2302AP IP Media Processor or the TN2602AP IP Media Resource 320 for IP-TDM voice processing - An optional TN799DP CLAN for control of IP endpoints 6. IP-PNC PN, with two carriers, that contains:
A C-position port carrie with:r
- A TN2302AP IP Media Processor or a TN2602AP IP Media Resource 320 for IP-TDM voice processing - An optional TN799DP CLAN for control of IP endpoints
B-position port carrier a TN2312AP/BP IPSI circuit pack for IP connection to the server.
7. 8.
IPSI-to-server control network connection through the Ethernet switch. LAN connections of a TN2302AP IP Media Processor or a TN2602 IP Media Resource 320 for IP-TDM voice processing and an optional TN799DP CLAN for control of IP endpoints NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, port networks, and adjunct systems. These circuit packs can be inserted into a port carrier, as shown in the figure, or the PN control carrier.
9. 10. 11.
Customer LAN LAN connections of media servers for remote administration Duplicated server links, including the fiber link for translations transfer and the DAL1 link for control data sharing.
2 of 2
Issue 2.1 June 2006
1111

! CAUTION:
CAUTION:
! CAUTION:
CAUTION:

2. Note the orientation of the existing 10 cables. The existing I/O cables can be white and red or multicolored. These cables are not twisted. 3. Remove the I/O cables that you want to replace from the backplane and the connector panel slots. 4. Install the twisted pair I/O cables onto the backplane in the place of the cables you just removed. Use the correct orientation (Proper orientation for the twisted pair I/O cables on page 1114). Observe the white outline that is printed on the backplane for the location of each connector. 5. View the cables from the "wiring" side of the twin connectors. That is, view the cables while you plug the cables into the backplane. Connectors oriented correctly for plug-in look like the cables in Proper orientation for the twisted pair I/O cables on page 1114.
The circled pin locations are No-Connects." At the top there is an orange-black pair on the right and a violet-brown pair on the left. Do not install wires in these locations. If you are replacing I/O cables for all slot positions, plug all cables into the backplane. Then, match the "D" connector on each cable to the carrier frame. You must install the 50-position metal shell "D" connectors into the carrier frame. Also, from the rear of the media gateway, look at the pins. Ensure that the longer side of the "D" connector (pins 1 to 25) is toward the right . 6. Apply the 10/100 mbps label to the front of the carrier slot. Apply the label over the slot label that corresponds to the slot where you installed the twisted pair I/O cable. 7. For the G600 Media Gateway, replace the fan unit if you are not adding any media gateways. If you are adding more media gateways to the rack, leave the fan units off until you install all the TDM cables. Figure 83: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
Issue 2.1 June 2006
1113
2 1
iodspair KLC 072602
Introduction
Converting some or all ATM port networks to IP-PNC
Introduction
This module describes how to convert one or more port networks (PNs) with fiber port network connectivity (fiber-PNC) using asynchronous transfer mode (ATM) to Internet Protocol port network connectivity (IP-PNC). The S8700-series Media Server controls the PNs. This conversion changes the transmission of inter-PN bearer traffic from circuit-switched protocol over fiber connections to packet-switched IP over Ethernet connections.
!
Important:
These procedures do not change the cabinet hardware as part of the conversion. All MCC1, SCC1, and G650 cabinets in the starting fiber-PNC configuration are present in the converted IP-PNC configuration.

The starting configuration consists of fiber-PNC PNs that use an ATM switch. All PNs are fiber-PNC through the ATM switch and one or more PNs are IPSI-connected to the control network. For Communication Manager release 3.0 and later, the starting configuration can include some IP-PNC components in addition to the fiber connect components. Each PN can be implemented in an MCC1, an SCC1 stack, or a G650 stack. The overall system can be any combination of MCC1, SCC1, or G650 gateways. The reliability level of the starting configuration can be: Duplex: Duplicated media servers, the standard reliability for S8700-series Media Servers High: Duplicated media servers and control network, available for S8700-series Media Servers only Critical: Duplicated media servers, control network, and bearer network, available for S8700-series Media Servers only
Issue 2.1 June 2006
1115

The final converted configuration can be all IP-PNC or mixture of IP-PNC and fiber connect. The IP-PNC components can have high reliability, duplicated control networks and a critical reliability duplicated bearer network. The reliability level for the fiber-PNC portion of the converted system can also be duplex, high, or critical. The reliability level of the IP-PNC portion of the converted system is per PN and can be either duplex, high, or critical. That is, some IP-PNC PNs can have duplicated control networks and/or duplicated bearer networks, while other IP-PNC PNs have nonduplicated control networks. If synchronization is required for any of the IP-PNC PNs, the synchronization source must be administered separately for each IP-PNC PN.
!
Important:
Important: Avaya recommends that you perform a traffic analysis when changes from a fiber-PNC configuration to a mixed configuration that includes both fiber-connect and IP-PNC PNs. A traffic analysis helps you understand Inter-PN bearer traffic and determine the correct number of media processor resources, other network parameters such as the use of network regions, codec sets, and VLANs. For more information, see Avaya Application Solutions: IP Telephony Deployment Guide (555-245-600) and Administration for Network Connectivity (555-233-504).
Configuration Diagrams on page 1138 provides sample before-and-after diagrams for the conversion from fiber-PNC to IP-PNC. For the starting configuration shown in Figure 85: An S8700-series ATM fiber-PNC configuration with duplicated control networks on page 1139, the control network is duplicated and the bearer network is fiber-connected through an ATM. In the converted configuration shown in Figure 86: An IP-PNC configuration with a duplicated control network that was converted from ATM on page 1141, the PNs are all IP-PNC with duplicated control networks. Variations on these configurations include mixed PNC and mixed reliability starting and converted configurations.
Prerequisites
Prerequisites
Presite assumptions


T

Issue 2.1 June 2006
1117
Preconversion tasks



Prerequisites
Resolving alarms


Issue 2.1 June 2006
1119

Note:
! CAUTION:
CAUTION:
Conversion Tasks
Conversion Tasks
Before you start the conversion tasks, you must ensure that the S8700-series Media Servers are running Communication Manager release 3.1 or later. You must complete the following tasks to convert from an ATM configuration to an IP-PNC configuration.
!
Important:
Important: For more information on how to install the IPSI, the media processor, and the CLAN circuit packs, see Adding New Hardware Avaya S8500 and S8700 Series Media Servers (555-245-212).

The following checklist identifies the major task in the conversion procedure:

Changing ATM synchronization Adding new circuit packs Upgrading firmware on new circuit packs. Disabling PNC duplication. Removing fiber administration. Enabling PNC duplication. Removing fiber-related hardware. Administering PN synchronization. Completing Post-conversion tasks
Changing ATM synchronization, if necessary

If you are not converting the PN that contains the ATM synchronization source, do not perform this procedure. Continue to Adding new circuit packs on page 1123.
!
Important:
Important: Synchronization for the ATM is derived from a connection through an ATM-connected PN. If you are not converting all ATM port networks to IP-PNC, Avaya recommends that you do not convert the PN that contains the ATM synchronization source. If you are converting the PN that contains the ATM synchronization source, convert this PN last.
Issue 2.1 June 2006
1121
If you are converting the PN that contains the synchronization source, complete the following steps to remove or change the synchronization source. 1. At the SAT, enter change synchronization atm.
If you are converting all PNs to IP-PNC, type blanks in the Primary and Secondary fields. If you are converting only one of the ATM PNs to IP-PNC, and if some PNs remain connected the ATM, enter new circuit pack locations in the Primary and, optionally, the Secondary fields. Obtain these locations from the list of Circuit Packs Available for Synchronization below the Primary and Secondary fields. If you enter both primary and secondary synchronization sources, both locations must be from the same PN. Ensure that you select working sync sources from a PN that is not being converted to IP-PNC.
3. Click Submit. 4. Verify that the synchronization sources are updated correctly: 5. Perform one of the following actions: a. If you are converting all PNs to IP-PNC and have blanked out the Primary and Secondary fields, enter list synchronization. Verify that the Primary and Secondary fields for ATM are blank. Then continue with Adding new circuit packs on page 1123.
If some PNs remain fiber-connected, complete the following steps: a. Enter list synchronization. b. On the Synchronization Plan screen, note the Primary and the Secondary locations. c. Enter status synchronization.
Conversion Tasks
- On the Synchronization Status screen, the Source Physical Location field for ATM must show the same location that is listed as Primary on the Synchronization Plan screen.


Installing the new circuit packs on page 1125 Adding cables for the new circuit packs on page 1127 Administering the new circuit packs on page 1128 Note: For more information about how to install circuit packs, see Adding New Hardware Avaya S8500 and S8700-Series Media Servers (555-245-212).
Note:
Note:
!
Important:
Important: If the final configuration mixes fiber-PNC PNs and IP-PNC PNs, at least one PN in the fiber connect portion of the system must have both of the following circuit packs: - A TN570 EI circuit pack - Either a TN2302 or a TN2602AP media processor circuit pack This PN acts as the "gateway port network."
Issue 2.1 June 2006
1123

Note:
!
Important:
Slot Number Carrier or Gateway Primary Secondary, if duplicated control, for S8700 series only B01 B01 Tone Clock slot (A00) Tone Clock slot (A00) E02 B01 B01 D01
A01 A00
1 of 2
Conversion Tasks
IPSI slot locations (continued)

Slot Number Carrier or Gateway Primary Secondary, if duplicated control, for S8700 series only Control duplication is not supported with three PNs. D01 (duplicated control)
Tone Clock slot (A00) B02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 (single control) E02 (duplicated control) Tone Clock slot (A00) B02 C02 D02 E02
Control duplication is not supported with four PNs
Control duplication is not supported with five PNs
2 of 2

!
Important:
Tip:
The TN2312BP, TN2602AP, and TN799D circuit packs all support hot-plug-in. That is, they can be inserted into a live system without disrupting call processing.
Issue 2.1 June 2006
1125

! CAUTION:
CAUTION:
!
Important:
a. If the PN has duplicated control networks, and you replaced the standby tone-clock with an IPSI at location UUC, enter set tone-clock UUC,where UUC is the standby tone clock location. This command interchanges the active and standby tone clocks. b. Enter the SAT command busyout tone-clock UUC, where UUC is the standby tone clock location. c. Remove the standby TN2182 tone clock. 2. Insert the IPSI circuit pack into the slot that the tone clock previously occupied by. 3. Push firmly on the faceplate until the circuit pack is properly seated, then close the latch. 4. After about 1 minute, to open the SAT Circuit Packs screen, enter display circuit-pack cabinetnumber. Verify that the TN2312B circuit packs are shown in the appropriate slots. 5. If the IPSI replaced a tone clock, enter the SAT command enable tone-clock UUC, where UUC is the IPSI circuit pack location. For the S8700-series Media Servers only, you can include an additional IPSI in the PN for control duplication.

Conversion Tasks


!
Important:

To connect an IPSI slot to the control network: 1. Connect the TN2312BP I/O adapter to the backplane amphenol connector that corresponds to the slot in which the TN2312BP is installed. 2. Connect a CAT5 or better Ethernet cable to the RJ45 connector on the IPSI adapter. 3. Connect the other end of the CAT5 cable to the Ethernet switch. 4. For the G650 gateway only, if the maintenance function is used, connect one end of the serial maintenance cable to the DB9 connector on the IPSI adapter. Connect the other end to the Emergency Transfer panel to provide 1 alarm output and 2 alarm inputs.

Important:
To connect a media processor slot to the LAN: 1. Connect the medial processor I/O adapter to the backplane amphenol connector that corresponds to the slot in which the media processor circuit pack is installed.
Issue 2.1 June 2006
1127
2. Connect a CAT5 or better Ethernet cable to the top RJ45 jack on the media processor I/O adapter. This jack is labeled Port 1. 3. Connect the other end of the CAT5 cable to an RJ45 jack on the customer LAN.


!
Important:
Tip:

To administer the TN2312BP circuit packs: Note: You must complete steps 1 and 2 just once for all IPSIs. Repeat the remaining steps for each IPSI. 1. If any of the IPSIs in the configuration are duplicated, enter change system-parameters duplication to set Enable Operation of IPSI Duplication to y. 2. Enter change system-parameters ipserver-interface to set the Switch Identifier for the IPSIs on this system. This identifier is usually A. If the identifier is not A, enter the correct value as a letter B to J in the Switch Identifier field and press Submit. Note: Repeat steps 3 and 4 for each new IPSI. 3. To add a new IPSI, enter add ipserver-interface n, where n is the PN number.
Note:
Note:
Conversion Tasks
4. Perform one of the following actions, depending on whether you want to use DHCP addressing or static addressing. Use DHCP addressing usually with dedicated control networks. Use static addressing usually with nondedicated control networks.
Note:
Note:
For static addressing: a. Connect the services laptop to the Services port on the IPSI faceplate. b. Type telnet 192.11.13.6 to access the IPSI. c. At the IPSI prompt, enter ipsilogin to log in to the IPSI IP Administration Utility. d. Log in as craft and use the IPSI password e. Type set control interface ipaddr netmask to enter the static IP address and the netmask. f. Enter quit to save the changes and end the IPSI session. g. Type 192.11.13.6 to access the IPSI, and log in again. h. Enter show control interface. The system displays the IP address, the subnet mask, and the default gateway information. Verify that the proper information was entered. i. If a default gateway is used, type set control gateway gatewayaddr where gatewayaddr is the customer-provided IP address for the network gateway. j. Enter quit to save the changes and end the IPSI session. k. Type 192.11.13.6 to access the IPSI, and log in again. l. Enter show control interface to verify the administration. m. Enter quit to end the IPSI session.
Issue 2.1 June 2006
1129


Note:
!
Important:
Note:
Conversion Tasks

Tip:


To administer the TN2602AP IP Media Resource 320: 1. From the active media server, log on to a SAT session. 2. To verify that the TN2602AP is correctly registered in the installed location, enter list configuration board UUCSS. 3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support Web site, you must upgrade the TN2602AP firmware. 4. To check the Maximum TN2602AP VoIP Channels field, enter display system-parameters customer-options, and go to page 2.
Issue 2.1 June 2006
1131
5. Verify the number of TN2602 circuit packs with 80 VoIP channels and the number of TN2602 circuit packs with 320 VoIP channels. 6. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN2602APs. 7. For each new TN2602AP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN2602AP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank. 8. To test connectivity to the IP endpoints through each TN2602AP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN2602AP. UUCSS is the cabinet, carrier, and slot location of the TN2602AP. 9. Repeat step 7 for another IP endpoint on a different subnet. 10. Make an external trunk call to a telephone on the port network and leave the call active. 11. To verify call processing, enter status media-processor board UUCSS. The Media Processor Status screen appears. 12. Look at the LINKS and DSP CHANNEL STATUS categories to determine whether the call is being processed.
Note:

To administer the TN799DP circuit pack: 1. From the active media server, log on to a SAT session. 2. To verify that the TN799DP is correctly registered in the installed location, enter list configuration board UUCSS. 3. Check the firmware version in the Vintage column. If the version is earlier than the latest version that is available on the Avaya Support web site, you must upgrade the TN799DP firmware. 4. To open the IP Node Names screen, enter change node-names ip and then enter the node names and the IP addresses for the TN799DPs. 5. For each new TN799DP circuit pack, enter add ip-interface UUCSS to open the IP Interfaces screen. Complete each field with the information for this TN799DP. Note: If you do not have a gateway IP address, leave the Gateway Address field blank.
Note:
Conversion Tasks
6. To display the Data Module screen, enter add data-module next. Enter ethernet in the Type field and complete the rest of the fields on the screen. 7. To test connectivity to the IP endpoints through each TN799DP, enter ping ip-address ipadress board UUCSS, where ipaddress is the IP address of an IP endpoint that is on the same subnetwork as the TN799DP. UUCSS is the cabinet, carrier, and slot location of the TN799DP. 8. Repeat step 8 for another IP endpoint on a different subnet.




If the bearer network is duplicated, you must remove the duplication before you remove the fiber-optic connections. If the system does not have PNC duplication, continue with Removing fiber-related administration on page 1134. To remove PNC duplication, open a SAT session and complete these steps: 1. Enter status pnc to check which of the duplicated PNCs is active. 2. If the B-PNC is active, enter reset pnc interchange to make the A-PNC active. 3. Enter busyout pnc-standby to busyout the standby PNC.
Issue 2.1 June 2006
1133
4. Enter change system-parameters duplication to open the duplication screen. 5. In the Enable Operation of PNC Duplication? field, enter n and press Submit.

Before the IP connections can be used, you must remove the fiber administration for each PN that is being converted to IP-PNC. Complete the following steps at the SAT to busyout and remove the fiber links for each PN being converted to IP-PNC: Tip:
Tip:
To view the fiber link numbers and their endpoints, enter list fiber-link. 1. Enter busyout fiber-link n, where n is the link number for the fiber connection. 2. Enter remove fiber-link n 3. Repeat steps 1 and 2 for each IP-PNC PN.


Complete these steps for each PN that you are converting to IP-PNC: 1. Remove the fiber cables that connect the EI circuit packs, TN570, and the ATM-EI circuit packs, TN2305B or TN2306B, in the PNs. 2. Remove the DS1 cable connecting the ATM switch to the sync splitter, if present. 3. Remove the TN2305B or TN2306B ATM-EI circuit packs from the PN cabinets, carriers, or gateways. 4. Remove the tone-clock circuit packs, TN2182, from the PN cabinets, carriers, or gateways.
Conversion Tasks
5. At the SAT, enter change circuit-pack. a. Type blanks in the EI fields (TN570) for the PNs that you are converting to IP-PNC. b. Type blanks the ATM-EI fields (TN2305/6) for the PNs that you are converting to IP-PNC. c. Type blanks the corresponding Tone Clock (TN2182) fields. d. Press Submit. 6. If converting all PNs to IP-PNC, remove the ATM switch.

Perform this procedure if the PN that you just converted to IP-PNC requires a synchronization source. To administer synchronization: 1. After the conversion, enter the SAT commands list synchronization and status synchronization to show the synchronization information for the IP-PNC PNs. The Primary and the Secondary fields on the Synchronization Plan screen and the Source Physical Location field on the Synchronization Status screen must be empty. 2. Enter change synchronization port-network n, where n is the PN number of the converted port network that requires synchronization. Tip:
Tip:
Issue 2.1 June 2006
1135
You must complete the following tasks after you complete the conversion tasks.



Resolving alarms

Note:
Note:
Issue 2.1 June 2006
1137


Figure 85: An S8700-series ATM fiber-PNC configuration with duplicated control networks on page 1139 and Figure 86: An IP-PNC configuration with a duplicated control network that was converted from ATM on page 1141 show before and after diagrams for the conversion of a ATM system from a fiber-PNC configuration to a mixed fiber-PNC and IP-PNC configuration. The IP-PNC configuration in Figure 85 was converted from an ATM configuration. Control network duplication was retained for all port networks.
Figure 85: An S8700-series ATM fiber-PNC configuration with duplicated control networks
Duplex ch 1 ch 2
disc
COMPACT
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
1
5 3 5 3 4 2 4 2
1
5
1 2 UID
23
Simplex
21
LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 ROUT SYS PWR S1 S2 1 3 5 7 9 11 13 15 17
2
18 20 22 24 LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 ROUT SYS PWR 19 21 23 S1 S2 1 3 5 7 9 11 13 15 17
2
18 20 22 24 19 21 23
19
20 9 3 20 15 6 5 4 8
22
Simplex
16
17
7 20 11
10
14
18 18 12 18 12 18 18
12
13
13
13
cycm3012 LAO 030505
Issue 2.1 June 2006
1139
Figure notes:An S8700-series ATM fiber-PNC configuration with duplicated control networks
1. 2. 3. 4. S8700 or S8710 Media Server. Ethernet switch IPSI-connected PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack), consisting of at least two media gateways or carriers. The figure shows an MCC1 Media Gateway. PN control gateway or carrier in the A position that contains:
A TN2312AP/BP IPSI circuit pack for IP connection to server.
A TN2305B or TN2306B ATM-CES circuit pack for bearer and control network connections to the ATM switch.
5. 6. 7. 8. 9. 10.
Duplicated control carrier in the B position that contains a TN2312AP/BP IPSI circuit pack for an IP connection to duplicated control network TN464GP DS-1 circuit pack, for clock synchronization with a network resource. ATM switch. IPSI-to-server control network connection through the Ethernet switch IPSI-connected PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack). The figure shows a G650 stack. PN control gateway or carrier in the A position that contains:
A TN2312AP/BP IPSI circuit pack for an IP connection to the server. A TN2305B or TN2306B ATM-CES circuit pack for bearer and control network connections to the ATM switch.
11. 12. 13.
Duplicated control gateway in the B position, that contains a TN2312AP/BP IPSI circuit pack for IP connection to the server. Fiber-PNC PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack). The figure shows a G650 stack and an SCC1 stack. PN control gateway or carrier in the A position that contains a TN2305B or TN2306B ATM-CES circuit pack for bearer and control network connections to the ATM switch. NOTE: One TN2182 Tone Clock circuit pack must also be present per PN if the PNs consist of SCC1 or MCC1 Media Gateways. One maintenance-only TN2312BP IPSI circuit pack must be present per PN if the PNs consist of G650 Media Gateways.
14. 15. 16. 17. 18. 19. 20.
OC-3 connections to the ATM switch. 401A/B sync splitter, attached to the back of the TN464GP DS1 circuit pack Public network (PSTN). Timing signal to ATM switch from sync splitter. Fiber connections from the TN2305B or the TN2306B to the ATM switch. Customer LAN. LAN connections of the TN2302AP IP Media Processor or the TN2602AP IP Media Resource 320 for voice processing, and an optional TN799DP C-LAN for control of IP endpoints. These circuit packs are optional for PNs in an ATM-connected network. However, the CLAN circuit pack is required for downloads of firmware updates. LAN connections of media servers for remote administration. DS1 connection from sync splitter. Duplicated server links, including the link for translations transfer and the link for control data sharing.
21. 22. 23.
Figure 86: An IP-PNC configuration with a duplicated control network that was converted from ATM
1
5 3 5 3 4 2 4 2
disc
COMPACT
1 2 UID
disc
COMPACT
Duplex ch 1 ch 2
Duplex ch 1 ch 2
1
5
1 2 UID
23
Simplex
21
LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 ROUT SYS PWR S1 S2 1 3 5 7 9 11 13 15 17
2
18 20 22 24 LNK COL Tx Rx FDX Hspd LAG PoE 2 4 6 8 10 12 14 16 ROUT SYS PWR 19 21 23 S1 S2 1 3 5 7 9 11 13 15 17
2
18 20 22 24 19 21 23
8 19 20 9 3 20 6 5 4 8
20 11
10
Simplex
To CNB To CNA
To CNB To CNA
To CNB To CNA 11
11
11
10
10
10
cycm3025 LAO 031405
Issue 2.1 June 2006
1141
Figure notes:An IP-PNC configuration with duplicated control networks that was converted from ATM
1. 2. 3. 4. S8700 or S8710 Media Server. Ethernet switch. IPSI-connected PN (G650 Media Gateway stack, MCC1 Media Gateway, or SCC1 Media Gateway stack), consisting of at least two media gateways or carriers. The figure shows an MCC1 Media Gateway. PN control gateway or carrier in the A position that contains a TN2312AP/BP IPSI circuit pack for an IP connection to the server. NOTE: For the G650 Media Gateway, the BP version of the TN2312 is required in order to provide environmental maintenance. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. Duplicated control carrier in the B position that contains a TN2312AP/BP IPSI circuit pack for an IP connection to the duplicated control network. Port carrier with a TN2302AP IP Media Interface or a TN2602AP IP Media Resource 320. N/A IPSI-to-server control network connection through the Ethernet switch IP-PNC PN (G650 Media Gateway stack,MCC1 Media Gateway, or SCC1 Media Gateway stack). The figure shows a G650 stack and an SCC1 stack. PN control gateway or carrier in the A position that contains a TN2312AP/BP IPSI circuit pack for an IP connection to the server. Duplicated control gateway in the B position that contains a TN2312AP/BP IPSI circuit pack for an IP connection to the server. N/A N/A N/A N/A N/A N/A N/A Customer LAN. LAN connections of the TN2302AP IP Media Interface or the TN2602AP IP Media Resource 320 for voice processing, and an optional TN799DP CLAN for control of IP endpoints. The CLAN circuit pack is required for downloads of firmware updates. LAN connections of the media servers for remote administration. N/A Duplicated server links, including the link for translations transfer and the link for control data sharing.
21. 22. 23.

! CAUTION:
CAUTION:
! CAUTION:
CAUTION:

2. Note the orientation of the existing 10 cables. The existing I/O cables can be white and red or multicolored. These cables are not twisted. 3. Remove the I/O cables that you want to replace from the backplane and the connector panel slots. 4. Install the twisted pair I/O cables onto the backplane in the place of the cables you just removed. Use the correct orientation (Proper orientation for the twisted pair I/O cables on page 1145). Observe the white outline that is printed on the backplane for the location of each connector. 5. View the cables from the "wiring" side of the twin connectors. That is, view the cables while you plug the cables into the backplane. Connectors oriented correctly for plug-in look like the cables in Proper orientation for the twisted pair I/O cables on page 1145.
Issue 2.1 June 2006
1143
The circled pin locations are No-Connects." At the top there is an orange-black pair on the right and a violet-brown pair on the left. Do not install wires in these locations. If you are replacing I/O cables for all slot positions, plug all cables into the backplane. Then, match the "D" connector on each cable to the carrier frame. You must install the 50-position metal shell "D" connectors into the carrier frame. Also, from the rear of the media gateway, look at the pins. Ensure that the longer side of the "D" connector (pins 1 to 25) is toward the right . 6. Apply the 10/100 mbps label to the front of the carrier slot. Apply the label over the slot label that corresponds to the slot where you installed the twisted pair I/O cable. 7. For the G600 Media Gateway, replace the fan unit if you are not adding any media gateways. If you are adding more media gateways to the rack, leave the fan units off until you install all the TDM cables. Figure 87: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
2 1
iodspair KLC 072602
Issue 2.1 June 2006
1145
Chapter 8: Converting the Media Server Mode

This chapter contains the following two modules describing procedures to change the mode of a media server. Converting S8300 ICC mode to LSP mode on page 1157 Converting S8300 LSP mode to ICC mode on page 1149 Note: These modules provide high-level checklists for the conversion tasks. Detailed task descriptions are given in - Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100. - Administrator Guide for Avaya Communication Manager, 03-300509. This chapter also contains the following modules: Installing or converting to an S8500 LSP on page 1165 Converting IP-PNC port networks with simplex control to duplicated control on page 1181 Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only) on page 1201 Converting software duplication link to a DAL1 link on an S8720 Media Server on page 1223 The following mode conversions are described in Avaya Enterprise Survivable Server (ESS) User Guide (03-300428)

Note:
S8500 Main to ESS S8500 MBS to ESS S8700 Main to ESS S8700 ESS to Main S8700 MBS to ESS
Issue 2.1 June 2006
1147
Converting the Media Server Mode
Introduction
Converting S8300 LSP mode to ICC mode
Introduction
This module provides a high-level list of tasks for converting an S8300B in LSP mode to primary controller (ICC) without performing an upgrade. To complete these tasks, you will need the following additional documents:
Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100. To obtain this document, go to http://support.avaya.com and navigate to Installations, Migrations, Upgrades & Configurations; then select the appropriate document. Administrator Guide for Avaya Communication Manager, 03-300509.
In this scenario, an S8300B, configured as an LSP, is converted to an S8300B standalone ICC primary controller. In both modes, the S8300B is running Communication Manager release 2.1 or later and no software/firmware upgrade is performed. The tasks include: 1. Removing the LSP from the current primary controller. 2. Updating the DHCP server alternate controller list. 3. Updating the gateway MGC list. 4. Installing IA770 messaging, if using it. 5. Setting date, time, and time zone. 6. Installing CM service pack, license, and authentication files, as needed. 7. Configuring the S8300B as an ICC. 8. Administering the new ICC and its media gateway. 9. Moving the endpoints supported by the current primary controller to the ICC. Follow the detailed procedures in Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006, for most of the tasks in this conversion scenario.
Issue 2.1 June 2006
1149
Before going to the site

Perform the tasks in this section before going to the customer site. Task 1. Redesign networks. Steps/Comments Assess the impact of the LSP to ICC conversion on all voice and voice messaging network nodes. Plan for any necessary changes to network elements. In particular, collect the server configuration information for the new ICC; that is, host name and IP address, primary controller IP address, DNS/DHCP IP addresses (if used), UPS IP addresses (if used), static routes data (if used), time server data, modem return route data (if supported by Avaya Services). 2. Create/update license and authentication files on the RFA web site. Go to http://rfa.avaya.com and follow the steps in Converting between an LSP and ICC (or a similar region-specific document if the system is outside the U.S.) to create new license and authentication files for the ICC. Go to http://support.avaya.com and click Downloads to see if there is a service pack file available for the Communication Manager release you are currently running, for example, release 3.1, load 628.0 If there is a service pack file available, download it and take it to the site.
3. Obtain post-conversion service pack file, if any.
Introduction
At the customer site


Use Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. To convert the LSP to an ICC, you complete selected tasks from Chapters 3 and 5. You need to complete only some of the tasks in these chapters. The specific tasks are identified by page number 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 or gateway on the LSP/ICC S8300, on the primary controller for the LSP, on a DHCP server, or on the gateway processor (MGP). The headings below indicate on which of these devices the task is performed. On the LSPs primary controller 1. Administer the primary controller to which the LSP was formerly assigned. See "Administer Communication Manager" in Chapter 9, and remove, instead of add, the LSP.
Remove LSP node name using the change node-names ip command. Dis-associate LSP from network regions using the change ip-network-region <number> command. Remove LSP from the LSP screen using the remove survivable-processor <node-name> command. Repeat for every LSP to be controlled by the new ICC. Remove media gateway using the remove media-gateway <number> command. Repeat for each gateway to be controlled by the converted LSP.
2. Administer the media gateway. See "Administering the Media Gateway" in Chapter 9.
Issue 2.1 June 2006
1151
Task
Steps/Comments On the DHCP server
3. Update the alternate controller list on the DHCP server. See "Considerations for IP Phones Supported by a Local Survivable Processor" in Chapter 9. On the gateways MGP 4. Telnet to the MGP and change the gateways controller list. See "Setting up the controller list for the G700" in Chapter 9.

Clear the gateways controller list. Enter the IP addresses of the new ICC and up to three alternate controllers. If the media gateway is a G350, enter: copy running-config startup-config
Reset MGP.
On the LSP to be converted 5. Backup all system files translations, OS, and security backup sets. See "Backing up S8300 system recovery files" in Chapter 12. 6. Record configuration information. See "Recording configuration information" in Chapter 11. 7. Restore default server configuration settings If you have not already done so, in the Record Configuration Information task, record all of the configuration information, regardless of the fact that you are not upgrading Communication Manager. You will re-enter some of this information after the conversion. On the Maintenance Web Interface, click Restore Defaults under Server Configuration. These backup sets will not be restored on the S8300B. They should be backed up in case it is necessary to revert to the original configuration.
Introduction
Task 8.
Steps/Comments Install IA770 and administer CWY1 integration according to Avaya IA770 INTUITY AUDIX Messaging Application, Release 3.0, Installation, Upgrades, and Troubleshooting (11-300532)
9.
Avaya IA770 INTUITY AUDIX Messaging Application, Release 3.0, Installation, Upgrades, and Troubleshooting (11-300532) Set the time zone of the new ICC, and all LSPs under the ICCs control must be set to the new ICCs time zone.
10. Set time, date, and time zone. See "Verifying Time, Date, and Timezone" in Chapter 12. 11. Install post-conversion service pack file, if any. See "Installing post-upgrade Communication Manager service pack file from your laptop, if any" in Chapter 12. 12. Install the new ICC license file. See "Installing the updated license file" in Chapter 12. 13. Install the new authentication file. See "Installing the updated license file" in Chapter 12. 14. Configure server. See "Configuring the S8300" in Chapter 9.
Fill in each Configure Server screen with data for the ICC. Some of the configuration data will be the same as that for the LSP. On the Configure Local Survivable Processor screen (page 123), select the radio button that indicates this is NOT a local survivable processor.
Issue 2.1 June 2006
1153
Task 15. Administer the new ICC. See "Administering an S8300 primary controller" in Chapter 9.

Steps/Comments Assign node names. Administer network regions. Associate other LSPs (if any) with a network region. Add IP interfaces Identifying LSPs to the primary controller Add media gateway. Repeat for each gateway to be controlled by the new ICC.
16. Administer the media gateway. See "Administering the Media Gateway" in Chapter 9.
For this scenario, the gateway will not automatically register with the ICC at this point. Skip the subtasks, Verify Changes and Save Translations in this section. When the gateway finally registers, the media modules will automatically populate, unless you are doing administration without hardware (AWOH). In this case, you will have to enter the media module types for each slot.
17. Reassign endpoints from the current primary controller to the standalone ICC. For information on updating translations, see the Administrator Guide for Avaya Communication Manager, 03-300509.
Update translations add stations and trunks - Using the Avaya Installation Wizard and the Electronic Pre-Installation Worksheet (EPW) is recommended. - Alternatively, use SAT commands.
Place test calls to verify. Reassign messaging system users of the current primary controller to the messaging system used by the new ICC. Enter test messages to verify.
18. Reboot the ICC.
Open a SAT session and enter reset system 4. After the reboot, any LSPs should be registered with the ICC, and in a few minutes translations should be synchronized.
Introduction
Task
Steps/Comments On the LSPs primary controller
19. Remove endpoints that will be controlled by the new ICC from the current primary controller.
Remove users/endpoints from the current primary controller.
On the new ICC 20. Verify that the media gateway has registered with the ICC.
Open a SAT session and enter list media-gateway. Verify that the Registered field (Reg?) is set to y. Place a test call.
On LSPs of the new ICC (if any) 21. Reboot LSPs (if any) 22. Verify LSP translations date and time (if any). At the LSPs SAT prompt, enter reset system 4. To view the LSPs translations date and time, enter list configuration software. On the ICC 23. Verify LSP status (if any)
At the SAT prompt, enter list survivable-processor(for CM R3.1) or list lsp (for CM R2.x). The LSP name and IP address should be listed. The Translations Updated date and time should match the translations date and time on the primary controller. To view the primary controllers translations dates and times, enter list configuration software-version. On the ICC, enter the Linux command filesync -a trans. Ensure that the translation synchronization completed successfully. Wait several minutes, then check the timestamp of the LSPs translation files using the SAT command list survivable-processor or list lsp on the ICC.
Issue 2.1 June 2006
1155
Task
Steps/Comments Post-conversion tasks
25. Implement any additional design changes to voice and/ or voice messaging networks.
Introduction
Converting S8300 ICC mode to LSP mode
Introduction
This module provides a high-level list of tasks for converting an S8300B primary controller to LSP mode without performing an upgrade. To complete these tasks, you will need the following additional documents:
Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100. To obtain this document, go to http://support.avaya.com and navigate to Installations, Migrations, Upgrades & Configurations; then select the appropriate document. Administrator Guide for Avaya Communication Manager, 03-300509.
In this scenario, an S8300B, configured as an ICC, is converted to an S8300B in LSP mode. In both modes, the media server is running Communication Manager release 2.1 or later and no software/firmware upgrade is performed. The tasks include: 1. Administering the primary controller for the new LSP. 2. Moving the endpoints supported by the ICC to the new primary controller. 3. Updating the DHCP server alternate controller list. 4. Updating the gateway MGC list. 5. Configuring the S8300B as an LSP. Follow the detailed procedures in Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006, for most of the tasks in this conversion scenario.
Issue 2.1 June 2006
1157
Before going to the site

Perform the tasks in this section before going to the customer site. Task 1. Redesign networks. Steps/Comments Assess the impact of the ICC to LSP conversion on all voice and voice messaging network nodes. Plan for any necessary changes to network elements. In particular, collect the primary server configuration information for the new LSP; that is, host name and IP address, primary controller IP address(es), DNS/DHCP IP addresses (if used), UPS IP addresses (if used), static routes data (if used), time server data, modem return route data (if supported by Avaya Services). 2. Create/update license and authentication files on the RFA web site.
Go to http://rfa.avaya.com and follow the steps in Converting between an ICC and LSP (or a similar region-specific document if the system is outside the U.S.) to create new license and authentication files for the LSP. If the new primary controller that will support the LSP is being migrated to Communication Manager 2.1 or later, you need to create a new license file for the primary controller.
Introduction
At the customer site


Use Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100, Issue 9, February 2006. To convert the ICC to an LSP, you complete selected tasks from Chapters 9 and 12. You need to complete only some of the tasks in these chapters. The specific tasks are identified by section in the left-hand column. The subtasks to perform 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 or gateway on the ICC/LSP S8300, on the primary controller for the LSP, on a DHCP server, or on the gateway processor (MGP). The headings in the table indicate on which of these devices the task is performed. On the new LSPs primary controller 1. Administer the primary controller that the LSP (after conversion) will use. See "Administer Communication Manager" in Chapter 9.

Assign node names Administer network regions Associate LSP with a network region Administer IP interfaces Identify LSPs to the primary controller
Administration of the S8400, S8500, or S8700-series primary controllers are the same. Administration of an S8300 primary controller is somewhat different. 2. Administer the media gateway. See "Administering the Media Gateway" in Chapter 9.

Add media gateway Repeat for each gateway controlled by the current ICC.
For this scenario, the gateway will not automatically register with the primary controller at this point. Skip the subtasks Verify Changes and Save Translations in this section. When the gateway finally registers, the media modules will automatically populate, unless you are doing administration without hardware (AWOH). In this case, you will have to enter the media module types for each slot. 1 of 5
Issue 2.1 June 2006
1159
Task 3. Reassign endpoints from the ICC to this primary controller. For information on updating translations, see the Administrator Guide for Avaya Communication Manager, 03-300509.
Steps/Comments Update translations add stations and trunks. - If the primary controller is a new installation, using the Avaya Installation Wizard and the Electronic Pre-Installation Worksheet (EPW) is recommended - Alternatively, use SAT commands.

Place test calls to verify. Reassign IA770 users to the messaging system used by this primary controller. Enter test messages to verify.
On the DHCP server 4. Update the alternate controller list on the DHCP server. See "Considerations for IP Phones Supported by a Local Survivable Processor" in Chapter 9. On the gateways MGP 5. Telnet to the MGP and change gateways controller list. See "Setting up the controller list for the G700" in Chapter 9.

Clear the gateways controller list. Enter the IP addresses of the primary controller and up to three alternate controllers. Set the LSP transition points. If the media gateway is a G350, enter: copy running-config startup-config
Reset MGP 2 of 5
Introduction
Task
6. Verify that the media gateway has registered with the primary controller. See the "To verify changes" subsection under "Administering the Media Gateway" in Chapter 9.
Open a SAT session and enter list media-gateway. Verify that the Registered field (Reg?) is set to y. Place a test call.
On the ICC/LSP 7. If IA770 is installed, get IA770 data and stop IA770. See "Getting IA770 (AUDIX) data and stopping IA770 (if IA770 is being used)" in Chapter 12. 8. Record configuration information. See "Recording configuration information" in Chapter 11. 9. Restore default server configuration settings 10. Set time, date, and time zone. See "Verifying Time, Date, and Timezone" in Chapter 12. If you have not already done so, in the Record Configuration Information task, record all of the configuration information, regardless of the fact that you are not upgrading Communication Manager. You will re-enter some of this information after the conversion. On the Maintenance Web Interface, click Restore Defaults under Server Configuration. 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.
3 of 5
Issue 2.1 June 2006
1161
Task 11. Install post-conversion service pack file, if any. See "Installing post-upgrade Communication Manager service pack file from your laptop, if any" in Chapter 12. 12. Install the LSP license file. See "Installing the updated license file" in Chapter 12. 13. Install the authentication file. See "Installing the updated license file" in Chapter 12. 14. Configure server. See "Configuring the S8300" in Chapter 9.

Steps/Comments
Fill in each Configure Server screen with data for the LSP. Some of the configuration data will be the same as that for the ICC. On the Configure Local Survivable Processor screen, select the LSP choice and the IP address to which the LSP should register. Open a SAT session and enter reset system 4. After the reboot, the LSP should be registered with the primary controller and in a few minutes translations should be synchronized. 4 of 5
15. Reboot the LSP.
Introduction
Task
16. Verify LSP status.
At the SAT prompt, enter list survivable-processor (for CM R3.1) or list lsp (for CM R2.x). The LSP name and IP address should be listed. The Translations Updated date and time should match the translations date and time on the primary controller. To view the primary controllers translations dates and times, enter list configuration software-version. On the primary controller, enter the Linux command filesync -a 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 or list lsp on the primary controller.
17. If the LSPs translations have not synchronized with the primary controller, invoke translation synchronization.
Post-conversion tasks 18. Implement any additional design changes to voice and/or voice messaging networks. 19. Re-register the S8300 as an LSP with the Avaya remote servicing center. 5 of 5
Issue 2.1 June 2006
1163
Installing or converting to an S8500 LSP
Introduction
This module provides a procedure for one of the following tasks:

Installing a new Avaya S8500 Media Server Converting the role an installed S8500 from a primary call controller to a local survivable processor (LSP).
To complete these tasks, you need the following additional documents:

Quick Start for Hardware Installation: Avaya S8500 Media Server, 555-245-701 Installing and Configuring the Avaya S8500 Media Server, 03-300143. Administrator Guide for Avaya Communication Manager, 03-300509.
These documents are available at http://support.avaya.com. For a new installation, you install the S8500 Media Server as an LSP, with an S8500 or S8700-series Media Server as the primary controller. For a conversion, you convert an S8500 Media Server from primary controller mode to LSP mode. An example of this scenario is an existing S8500 Media Server that is migrating to an S8700-series Media Server pair. You can subsequently convert the S8500 Media Server to an LSP and use it in the migrated network.
! CAUTION:
CAUTION:
If this is a conversion scenario, you cannot follow the standard upgrade procedure for the S8500 Media Server. Existing translations and configurations can interfere with proper operation after you designate the server as an LSP. Note: The installation and conversion procedures in this module use the Maintenance Web Interface. Some of the tasks can be automated by using the Avaya Installation Wizard with the Electronic Pre-installation Worksheet (EPW).
Note:
Issue 2.1 June 2006
1165
Checklist
Note:
Note: For the conversion scenario, this procedure assumes that service provided by the S8500 Media Server has been migrated to an S8700-series Media Server. The S8500 is therefore placed out of service and reinstalled as an LSP. For more information, see Migrating an S8500 Media Server to an S8710 Media Server on page 871.
To install a new S8500 LSP or convert an existing S8500 primary controller to an LSP server, perform the following tasks: 1. Installing the hardware (new installation only) on page 1167 2. on page 1167 3. Connecting the laptop and turning on the media server on page 1167 4. Configuring the SNMP modules in the UPS on page 1168 5. Configuring the SNMP subagent in the Avaya Ethernet switch on page 1168 6. Disabling the boot timeout of the SAMP board (S8500B upgrade only) on page 1168 7. Installing Avaya Communication Manager on page 1169 8. Configuring the S8500 LSP on page 1171 9. Configuring the RMB on page 1172 10. Installing SAMP software update, if necessary on page 1173 11. Configuring the modem on page 1174 12. Administering the new primary controller on page 1174 13. Enable license server capability on a media gateway, if necessary on page 1176 14. Install and verify the license on the new LSP on page 1176 15. Opening the TCP ports on the S8500 LSP on page 1177 16. Connect the new S8500 LSP to the LAN/WAN on page 1179 17. Reset the S8500 LSP on page 1179 18. Verify that the primary controller identifies the new LSP and has sent the translations on page 1179 19. Readminister the desired media gateways to point to the LSP on page 1180
Checklist
Installing the hardware (new installation only)

Use the instructions in Quick Start for Hardware Installation: Avaya S8500 Media Server (555-245-701) to install the S8500 Media Server in the data rack.


Connecting the laptop and turning on the media server

1. With a crossconnect cable, connect the laptop to the services port on the back of the media server. The services port is labeled port 2 on the server, but is called Ethernet 1 in the software. Note: You must place the software CD in the media server CD drive immediately after turning on the media server.
Note:
Issue 2.1 June 2006
1167
2. Connect the AC power cord to the media server and to the UPS or a nonswitched outlet to turn on the server. If it does not turn on, press the white power control button on the front of the media server. 3. Place the CD that contains the Avaya Communication Manager software in the CD-ROM drive on the media server. 4. Wait at least 3 minutes after turning on the server before starting a Telnet session to access the information on the CD.
Configuring the SNMP modules in the UPS

Follow the instructions in Installing and Configuring the Avaya S8500 Media Server, 03-300143 to configure SNMP modules, if any, for an uninterruptible power supply (UPS).
Configuring the SNMP subagent in the Avaya Ethernet switch

Follow the instructions in Installing and Configuring the Avaya S8500 Media Server, 03-300143 to configure a new Avaya-supplied Ethernet switch with an SNMP subagent.
Disabling the boot timeout of the SAMP board (S8500B upgrade only)
If you are using the remastering program to upgrade Communication Manager, for which you boot from the CD-ROM, you must disable the boot timeout of the SAMP board prior to the upgrade. To disable the boot timeout: Note: You can also disable the boot timeout of the SAMP board by connecting to the SAMP services port and using the SAMPs 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. 1. At the command line on the S8500 Media Server, type sampcmd, and press Enter. The Welcome banner appears, followed by the SAMP command line. 2. At the SAMP command line, type serverctrl boot timer disable, and press Enter. The system responds with OK.
Note:
Checklist
3. At the SAMP command line, type serverctrl, and press Enter. The system responds with the following output:
Power On Server Operational Reset Deasserted Boot Time Disabled
4. Type Exit and press Enter 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.
Installing Avaya Communication Manager

Install Avaya Communication Manager on the media server with the following steps. 1. From the laptop Start menu, click Start > Run to open the Run dialog box. 2. Type telnet 192.11.13.6 and press Enter to view the first screen.
Note:
Note: To navigate on these screens, use the arrow keys to move to an option, then press the space bar to select the option. Press Enter to submit the screen. 3. Select Install, ensure that <OK> is highlighted, and press Enter.
Issue 2.1 June 2006
1169
Note:
Note: If the hard drive on the S8500 has a version of Communication Manager installed, you see the following screen:
If this screen appears, select Yes on the screen. You want to repartition the hard disk and remove the existing software and translations. Then continue as with a normal new installation. 4. The Select Release Version screen is displayed. Ensure that the Build line and <OK> is highlighted. 5. Press Enter to partition the hard disk drive and reformat the partitions. Once the drive is properly configured, the program starts the installation process and reports on progress made.
Checklist
Configuring the S8500 LSP

To configure the new S8500 LSP, perform the following steps: Note: Do not install the license and authentication files until after you have administered the primary controller. For more information, see Administering the new primary controller on page 1174. Note: If the S8500 Media Server has a NIC card, it can be removed. As an LSP, the S8500 Media Server does not use it. 1. On the Maintenance Web Page, click Server Date and Time a. Choose - Set Date and Time Zone: The time of the LSP must be set to the same time zone as its primary controller. The time must be set even if the LSP is physically located in a different time zone. 2. Run the Configure Server command. Select the Configure Individual Services method. a. Choose - Set Identities:

Note:
Note:
Enter the host name for the LSP. Check the Server ID (SVID) value in the ID field. The primary controller is set to SVID 1. If the primary controller is a duplicated S8700-series Media Server, the server IDs are SVID 1 and SVID2. The ID for an LSP must be greater than 2 and less than or equal to 256. Gaps in the numbering are allowed. For example, SVIDs can be 10, 20, 30, . . .. However, the SVID must be incrementally higher than the highest ID of other existing LSPs or ESSes. Select the default Ethernet 0 in the Control Network A field. Select the default Ethernet 1 in the Services Port field. Select the default Ethernet 0 in the Corporate LAN field. Select the default unused in the Control Network B field. Select the Corporate LAN in the Assign a Processor Ethernet interface
b. Click Continue. c. Enter the following IP Addresses on the Configure Interfaces Web page.

The IP address for the LSP in the IP address servr1 field. The IP address for the LAN gateway in the Gateway field. The subnet mask for the LSP in the Subnet mask field. AUTO SENSE in the Speed field.
d. Click Change.
Issue 2.1 June 2006
1171
e. Choose - Configure LSP or ESS from the list in the left margin.

Select This is a local survivable processor (LSP) For the Registration address field, enter the IP address of a CLAN that the primary controller controls. If the primary controller is an S8500 Media Server, this address can be a processor ethernet IP address on the new primary controller. For the File Synchronization address at the main cluster field, enter the physical IP address or addresses of the primary controller media servers. These addresses must be connected to the corporate LAN. The IP address cannot be the address of a port assigned to a control network if the control network is dedicated to the IPSI connection. If the control network or the control networks are dedicated, the IP address you enter is the port assigned to the corporate LAN. Do not complete the File Synchronization address at the alternate main cluster field.
f. Click Change to save your changes on the Configure Interfaces Web page.
Configuring the RMB

The Remote Maintenance Board (RMB) page is under Configure Server in the Maintenance Web Interface and is under Optional Services in the Wizard configuration process. Manually complete all fields or verify that the IP information for the remote maintenance board was correctly retrieved from the Electronic Preinstallation Worksheet (EPW). Maintenance Web Interface screen for RMB
Checklist
Wizard Screen for RMB
For services laptop access:
IP Address field - 192.11.13.6 Mask field - 255.255.255.252
Subnet
The preceding information configures the remote maintenance board for the crossconnect cable. For customer LAN access (optional), the 3 fields must match customer LAN The SAMP is automatically configured within the Avaya Installation Wizard.
Installing SAMP software update, if necessary

For more information on updating SAMP software, see Using the Avaya Server Availability Management Processor (SAMP). The SAMP software might need to be updated, depending on the currently installed version. Ensure that the versions that require updates are included in your project planning information. To update the SAMP software version, if necessary: 1. Check the SAMP software version. - Telnet to the S8500 and login. - Enter sampcmd samp-update status. - Check the SAMP software version displayed. - If this software version does not need to be updated, skip this procedure and continue with the next procedure, Configuring the modem on page 1174.
Issue 2.1 June 2006
1173
2. Copy the SAMP software update file to the S8500 with the Download Files option from the Maintenance Web Interface. 3. Telnet to the S8500 and login. 4. Enter sampupdate <filename> to start the update process. The update process takes approximately 5 minutes. 5. Enter y in response to the question, Commit this software?
Configuring the modem

If the LSP uses a modem for remote access, follow instructions in Installing and Configuring the Avaya S8500 Media Server, 03-300143, to configure the modem.
Administering the new primary controller

You must administer the new primary controller so that it can identify and communicate with the S8500 LSP. To do this, complete the following SAT screens (on the primary controllers SAT): 1. At the SAT command line, type change node-names ip <name>, where <name> is the name of the LSP. The Node Names screen appears.
Checklist
Figure 89: IP Node Names screen

change node-names ip IP NODE NAMES Name 1. ______________ 2. ______________ 3. ______________ 4. ______________ 5. ______________ 6. ______________ 7. ______________ 8. ______________ 9. ______________ 10. ______________ 11. ______________ 12. ______________ 13. ______________ 14. ______________ 15. ______________ 16. ______________ IP Address ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Name ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ ______________ IP Address ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Page 1 of X
17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32.
2. In the Name column, type the name of the LSP. 3. In the IP Address column, type the IP address of the LSP. 4. At the SAT command line, type add survivable-processor <name>, where <name> is the LSP name from the Node Names screen. The Survivable Processor screen appears. Figure 90: Add Local Survivable Processor screen
add survivable-processor sv-mg2-lsp SURVIVABLE PROCESSOR - PROCESSOR ETHERNET Node Name: sv-mg2-lsp IP Address: 128.256.173.101 Type: LSP Network Region: 1 Page 1 of xx
5. The type field is automatically populated with LSP. LSP appears in the field if the node name is not associated with ESS.
Issue 2.1 June 2006
1175
6. Enter a network region for the LSP. The default is 1. However, there might be a different network region better suited for the LSP to provide media gateway and IP telephone support. 7. On pages 2 and 3 of the screen, add any adjuncts that the LSP might support if a failover from the primary controller occurs. For more information, see Installing and Configuring the Avaya S8500 Media Server, 03-300143, or Installing and Configuring the Avaya S8700 Series Media Server Release 3.1, 03-300145.
Enable license server capability on a media gateway, if necessary

If a G700 Media Gateway is providing the serial number for the license, skip this step. If a G250 or G350 Media Gateway is providing the serial number, access the administration level command line on the media gateway and run the command ip license-server. Note: For the license server role, select a gateway that is physically located near the LSP.
Note:
Install and verify the license on the new LSP

On the S8500 your are converting to an LSP, install a new license file with the appropriate settings for an LSP server. The new license file has the following attributes:

Local Survivable Processor (FEAT_LSP) set to Y. A Module ID (MID) greater than 1: The license file sets this value. Therefore, you cannot administer the MID in Communication Manager. A System ID (SID): The SID is unique to the system configuration. The primary controller and all LSPs must have the same SID. The serial number of an H.248 media gateway to serve as the license serial number host. The license serial number host can, therefore, be a G250, G250, or G700 Media Gateway. When you reset the system later in this procedure, the LSP sends this serial number to the primary controller. The primary controller then matches the serial number to that of an existing media gateway. The primary controller sends back to the LSP the IP address of the media gateway. The LSP can then verify its license by contacting that media gateway and requesting its serial number. The LSP compares the serial number received from the media gateway with the serial number from the license of the LSP.
Checklist
Note:
Note: You can use the serial number in a media gateway to support the license for only one server. This licensing limit is true regardless of the role (primary controller, LSP, ESS) that the server might have. As a result, the number of media gateways in the configuration cannot be less than the number of servers. That is, there must be at least as many H.248 media gateways as there are LSPs.
To install the license and authentication files, perform the following steps: 1. Under Security, click License File. 2. Select Install the license I previously downloaded and click Submit to install the license file. The system gives you a warning that the license requires a restart. Do not restart the server at this time. 3. Under Security, click Authentication File. 4. Click Install the Authentication file I previously downloaded and click Install. The system tells you the authentication is installed successfully. 5. Verify that the S8500 Media Server you are converting is licensed as an LSP. To verify the license, perform the following step: Note: When you access the SAT screen prior to doing a reset, the screen might indicate "License mode not available." This temporary state is normal and is resolved after you perform the reset later.
Note:
Open a SAT session on the LSP and enter display system-parameters customer-options. On page four of the system-parameters customer-options form, ensure that the Local Survivable Processor field is set to y. On page five of the form, ensure that the Processor Ethernet field is set to y.
Opening the TCP ports on the S8500 LSP

So that the processor ethernet connections work for the LSP, various TCP ports for processor ethernet must be open on the firewall.
Issue 2.1 June 2006
1177
To verify that the ports are open, perform the following steps: 1. click Firewall under the Security heading in the maintenance web interface. The Firewall Web page appears.
Note:
Note: The ftp, telnet, and tftp services are not required. 2. In the Input to Server column, ensure that the check box for snmp is selected. 3. Click the Advanced Setting button. The advanced firewall settings Web page appears. 4. Verify that the following defaults are set:

Output to server is selected for gateway compatibility, ports 1024:65535 Input to server is selected for ip-signaling-1, ports 5000:5021/tcp Input to server is selected for ip-signaling-2, ports 5024:9999/tcp Input to server is selected for h248message, port 2945/tcp
Checklist
Input to server and Output to server is selected for filesync, port 21874/tcp Input to server and Output to server is selected for h323gatestat, port 1719/udp Input to server and Output to server is selected for h323hostcall, port 1720/tcp
If any of the defaults are not set correctly, contact your sales representative. 5. Click the Standard Service button to return to the first Firewall page, then click Submit.
Connect the new S8500 LSP to the LAN/WAN

Cable the appropriate Ethernet port on the LSP to the customer LAN. Verify connectivity of the LSP to the customer LAN.
Reset the S8500 LSP

Use the following commands to notify all processes of the new parameters: Note: When you access the SAT screen prior to doing a reset, the screen might indicate a license mismatch. This temporary mismatch is normal and is resolved after the reset. 1. From the SAT command line, enter reset system 4. The system resets. In addition, the system registers with the new primary controller and receives the translations from the primary controller.
Note:
Verify that the primary controller identifies the new LSP and has sent the translations
To verify that the S8500 LSP has registered with the primary controller and has received the translations, perform the following steps: 1. Wait several minutes for the reset to finish. 2. On the new primary controller, use the SAT command list survivable-processor to verify that the LSP server registers and translations are updated. If the LSP has registered, the Service State? field shows in-service and the Translations Updated field shows the time and date.
Issue 2.1 June 2006
1179
Figure 91: List Local Survivable Processor screen

list survivable-processor Page 1 of xx
Name LSPNYC LSPCHI
Type LSP LSP
ID 04 05
SURVIVABLE PROCESSORS IP Address Service Translations State? Updated 128.256.173.101 in-service/idle 03:21 02/19/03 128.256.113.213 out-of-service 04:32 02/20/03
Readminister the desired media gateways to point to the LSP

Change the controller list for each G700, G350, or G250 media gateway for which the LSP is an alternate controller. This change enables the media gateway to seek service from the LSP if the connection to the primary controller fails. For instructions on changing the controller list of the media gateway, see one of the following documents:
Installing and Upgrading the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100 Installing and Upgrading the Avaya G250 Media Gateways, 03-300434 Installing and Upgrading the Avaya G350 Media Gateway, 03-300394
Introduction
Converting IP-PNC port networks with simplex control to duplicated control
Introduction
This module describes the procedures to convert one or more IP-PNC port networks with a simplex control configuration to a duplicated control configuration. The PNs are controlled by a pair of S8700 series Media Servers. Note: Duplicated control networks are not supported on the S8500 Media Server.
Note:
This conversion adds a second TN2312BP IPSI circuit pack to an IP-PNC port network and a second Ethernet switch, if necessary, for connections between the servers and the IPSIs. If the port network consists of SCC1 or MCC1 Media Gateways, cabling of the IPSI circuit pack to a TN775 Maintenance circuit pack is required. If the port network consists of G650 Media Gateways, the TN775 Maintenance circuit pack is not used, and, therefore, there is no cabling to a TN775 circuit pack.
Preconversion assumptions
The conversion procedures in this chapter assume that:
You have completed the pre-site checklist, Presite checklist on page 1037, before going to the customer site. The system has been upgraded to Communication Manager release 3.0 or higher. With release 3.0 or higher, you can add duplicated control for individual IP-PNC port networks. For earlier releases, all port networks had to have the same reliability level, which meant that you had to add duplicated control to all IP-PNC port networks.
Issue 2.1 June 2006
1181
Procedure
To convert an IP-PNC port network from a simplex control network to a duplicated control network, perform the following tasks:

Installing and cabling a second Ethernet switch, if necessary on page 1182 Configuring the SNMP subagent in the Avaya Ethernet switch (if used) on page 1183 Enabling firewall settings, if necessary on page 1185 Accessing the media server maintenance web interface on page 1186 Configuring Control Network B on page 1186 Designating the slot for the duplicated IPSI circuit pack on page 1188 Installing the duplicated IPSI circuit pack on page 1189 Adding control network cabling for the new circuit pack on page 1197 Verifying the IPSI circuit packs are inserted properly on page 1197 Programming the duplicated IPSI circuit pack on page 1197 Starting a SAT session on page 1199 Administering the duplicated IPSI circuit pack on the media server on page 1199 Verifying IPSI translations on page 1200 Upgrading IPSI firmware, if necessary on page 1200
Installing and cabling a second Ethernet switch, if necessary

If necessary, install and cable to the S8700 series Media Servers a second Ethernet switch. This switch provides IP connections between the duplex servers and the duplicated IPSI (TN2312BP) circuit packs. A second or alternate Ethernet switch may already be available if the customer has designated it. However, if the control networks are dedicated (that is, not using the customer LAN for the server-to-IPSI connection), then a second Ethernet switch, from either Avaya or a third party, is required. For information on installing and cabling Avaya Ethernet switches in the S8700-series configurations, see Quick Start for Hardware Installation: Avaya S8700 Series Media Server, 555-245-703.
Procedure
Configuring the SNMP subagent in the Avaya Ethernet switch (if used)
Note:
Note: These instruction apply only if using a new, Avaya-supplied Avaya Ethernet switch. Do not use these procedures to set traps on a non-Avaya-provided Ethernet switch. Note: The specific Avaya Ethernet switch model and firmware load shipped with a communication system may change over time. Therefore, this document is not specific on how to configure the SNMP subagent. Refer to the documentation that comes with the switch. Note: If the control network is non-dedicated (going over the customer's network), you must make sure that the 162/udp port for input to server is enabled (the default is disabled). Otherwise, the traps from the UPS(s) cannot be received. See Enabling firewall settings, if necessary on page 1185.
Note:
Note:
The simple network management protocol (SNMP) subagent in the Avaya Ethernet switch must be administered so it can report alarms to the media server when the hardware experiences problems. Each Avaya Ethernet switch requires a unique IP address, which can be a customer-provided one or the Avaya-provided default one. At a minimum, the following items need to be configured:

IP address (1 for each Ethernet switch) Subnet mask Trap receiver IP address Community string (get, set, trap) - Spanning tree version - Ethernet port speed (if applicable) Note: For the Ethernet switch to properly report alarms, the IP address(es) for the Ethernet switch(es) must also be configured in the media servers.
Note:
See the Basic Configuration section of the Quick Start Guide and the documentation CD that comes with the Ethernet switch for the default user ID, password, and configuration commands.
Issue 2.1 June 2006
1183
To administer the Ethernet switch(es): 1. Plug the Ethernet switch power cord into the back of the switch and the back of a UPS.
For a single control networkconnect Ethernet switch 1 for Control Network A (CNA) into UPS 1. For a duplicated control networkconnect Ethernet switch 1 for CNA into UPS 1 and connect Ethernet switch 2 for Control Network B (CNB) into UPS 2.
2. Connect the services laptop computer (RS-232 serial port) to the port labeled Console on the front of Ethernet switch 1 (CNA) using the flat cable supplied with the Avaya Ethernet switch. 3. On the services laptop open a VT-100 terminal emulation session. 4. Administer the terminal emulation port settings:

9600 baud No parity 8 data bits 1 stop bit
5. Follow the instructions in the Quick Start Guide. 6. Set the following parameters:
IP address and subnet mask of the Ethernet switch(es) - For Ethernet switch for CNA, the defaults are 198.152.254.240, 255.255.0.0. - For Ethernet switch for CNB, the defaults are 198.152.255.240, 255.255.0.0.
IP address of the trap receiver. (Do not use the Active Server IP address.) - For Ethernet switch for CNA, this is the IP address of media server 1. (default is 198.152.254.200) - For Ethernet switch for CNB, this is the IP address of media server 2. (default is 198.152.255.200)
SNMP community string for Get, Set, and Trap. (See the section on SNMP commands on the documentation CD that comes with the Avaya Ethernet switch.)
Procedure
!
SECURITY ALERT:
SECURITY ALERT: The Get and Set, community name strings are generally configured with default values of Public and Private, respectively. These community name strings function as passwords for their respective SNMP operation. It is always a good idea to change these community name strings to something other than the default values. If a Network Management Station (NMS) is in operation on the network, whatever these strings are changed to must be communicated to the NMS administrator. If the defaults are left administered this could create a serious security issue. For example, the default Set community name string, with its widely known value of Private, could be used to reconfigure the Ethernet switch via SNMP message.
7. Verify that spanning tree is enabled (the default setting). Use the command set spantree enabled. 8. Set spanning tree version to rapid-spanning-tree (not the default). This command is available on Avaya P363 Ethernet switches having firmware version 4.0 or later. You must update the firmware to this version to use the command. Use the command set spantree version rapid-spanning-tree. Note: For more information on the Spanning Tree CLI commands, see Installation and Configuration Guide, Avaya C360 and Reference Guide, Avaya C360, available at the Avaya Support Web site (http://www.avaya.com/support). 9. If IP-PNC, make sure all appropriate ports on the Ethernet switch are locked to 100 speed using full duplex. 10. When completed, disconnect the services laptop computer from the Ethernet switch. 11. If two Ethernet switches are present for CNA, repeat steps 1 through 7 for the second switch. 12. If a duplicated control network, repeat steps 1 through 9 for the remaining Ethernet switch(es).
Note:
Enabling firewall settings, if necessary

For the media server to receive SNMP traps from the UPS and Avaya Ethernet switch, you must enable the snmp trap, 162/udp port. The default is disabled. 1. Under Security, click Firewall. 2. Click Advanced Settings . . . to view the second page. 3. Scroll down until you see snmp trap, port 162/udp. 4. Select the box in the Input to Server column (far left) next to it.
Issue 2.1 June 2006
1185

Configuring Control Network B

Control network A will already be assigned on the S8700-series Media Server pair. With the addition of a duplicated IPSI, you must also assign Control network B. Control network B is essentially the Ethernet port on the S8700 series Media Server, its connection to an alternate Ethernet switch, the connection from the Ethernet switch to the duplicated IPSI. Use the following steps to configure control network B on the server pair: 1. On the Maintenance Web page, select Configure Server. 2. Click Continue until the Copy Settings page appears. The heading Specify how you want to use this wizard appears at the top of the page. 3. Select Configure individual services and click Continue. The Configure individual services menu appears to the left. 4. Select Set Identities. The Configure Server - Set Identities Web page appears. 5. On the Configure server - set identities page, select the interface that will be used for Control Network B.
Procedure
Figure 92: Configure server - set identities
6. Click Continue and verify the IP Addresses on the Configure Interfaces Web page. Then click Change.
Issue 2.1 June 2006
1187
Designating the slot for the duplicated IPSI circuit pack

Designate the slot in which each new IPSI is to be installed. Each of these circuit packs requires an I/O adapter that is installed on the backplane connector associated with the slot in which the circuit pack is installed. The IPSI circuit packs must be placed in the slots specified in the Secondary, if duplicated control S8700 series only column in the following table. IPSI slot locations
Slot Number Carrier/Gateway Primary Secondary, if duplicated control S8700 series only B01 B01 B01 B01 D01 Control duplication not supported with 3 PNs. D01 (duplicated control) Control duplication not supported with 4 PNs
G650 stack SCC1 EPN MCC1 EPN -- 1 PN MCC1 EPN -- 2 PNs MCC1 EPN -- 3 PNs
A01 A00 - Tone Clock slot (A00) - Tone Clock slot (A00) - E02 - Tone Clock slot (A00) - B02 - D02 (single control) - E02 (duplicated control)
MCC1 EPN -- 4 PNs
- Tone Clock slot (A00) - B02 - C02 - D02 (single control) - E02 duplicated control)
MCC1 EPN -- 5 PNs
- Tone Clock slot (A00) - B02 - C02 - D02 - E02
Procedure
Installing the duplicated IPSI circuit pack

Install the IPSI in the appropriate slot number identified in the Secondary column on the right of ISPI Slot Locations table. Note: For this task with SCC1 Media Gateways, you need a long ribbon cable and the Cable PassThrough Kit (comcode 700219413). For this task with MCC1 Media Gateways, you need a short ribbon cable (comcode 700168727).
Note:
To install the duplicated TN2312BP IPSI circuit pack, perform the following steps, depending on which type of media gateway you are working with:

For the G650 Media Gateway: on page 1189 For the MCC1 Media Gateway: on page 1189 For the SCC1 Media Gateway: on page 1191 Note: You can insert the IPSI circuit pack and administer it ahead of time. The circuit pack is hot-swappable. Therefore, you do not need to turn off the PNs or the carriers.
Note:
For the G650 Media Gateway:

1. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs into the B01 slot in media gateway B.
For the MCC1 Media Gateway:

1. Insert the TN2312BP IPSI circuit pack part way into the TONE-CLOCK slot on the standby carrier (B). 2. Attach one end of the long ribbon cable to the connector on the component side of the circuit pack. The red line must be on the bottom (pin 1). 3. Push the tabs on the ends of the connector inward to lock the connector in place. See Figure 93: Ribbon Cable Connector on page 1190.
Issue 2.1 June 2006
1189
Figure 93: Ribbon Cable Connector
caxxinst LJK 022002
4. Thread the ribbon through the slot on the front panel. 5. Attach the other end of the long ribbon cable to the bottom connector (labeled B) on the component side of the TN775D Maintenance (EPN) circuit pack. The red line must be on the bottom. See High/Critical Reliability Ribbon Cable Connection on page 1191. 6. Fully insert the IPSI circuit pack. 7. Program the IPSI just inserted. See Programming the duplicated IPSI circuit pack on page 1197. 8. Fully insert the TN775D Maintenance (EPN) circuit pack after the IPSI has been programmed.
Procedure
Figure 94: High/Critical Reliability Ribbon Cable Connection
CL
B
MS
TR ER N O
TO F AU OF
cadshc2 LAO 121605
For the SCC1 Media Gateway:

1. Remove the ground plate, upper and lower rear covers from the media gateway(s). See Removing ground plate and upper and lower rear covers (SCC1 shown) on page 1192.
Issue 2.1 June 2006
1191
Figure 95: Removing ground plate and upper and lower rear covers (SCC1 shown)
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
cadscat1 KLC 032602
Figure notes: 1. Media Gateway B 2. Media Gateway A 3. Upper rear cover 4. Ground plate 5. Lower rear cover
2. Remove the TN2182 Tone Clock circuit pack from the new standby carrier (B). Place the circuit pack in an antistatic carrier. 3. Use the pass through tool to feed the long ribbon cable through media gateway A. See Figure 96: Ribbon cable placement using the pass through tool on page 1193.
Procedure
Figure 96: Ribbon cable placement using the pass through tool
CLK
O AUT OFF
cadsrib2 KLC 032602 602
4. Plug the long ribbon cable into the bottom connector (labeled B) on the component side of the TN775D Maintenance (EPN) circuit pack. The red line is on bottom. See Figure 97: High/Critical Ribbon Cable Connection on page 1194. 5. Thread the ribbon cable through the remaining slot on the faceplate of the TN775D Maintenance (EPN) circuit pack. 6. Route the cable through the TDM slot in the back of the SCC1 media gateway A and up to SCC1 media gateway B. See Cable routing through the TDM slot on page 1195.
Issue 2.1 June 2006
1193
Figure 97: High/Critical Ribbon Cable Connection
B
CLK
A
S RM ALA J MA MIN RN W K AC TR ER EM ON
TO AU OFF
CLK
O AUT OFF
CLK
O AUT OFF
cadsrib3 KLC 072502
Procedure
Figure 98: Cable routing through the TDM slot
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
3
cadsrib4 KLC 032602
Figure notes: 1. Media Gateway B 2. Media Gateway A 3. TDM cable slot
7. Use the pass through tool to feed the long ribbon cable through media gateway B. 8. Insert the TN2312BP Internet Protocol Server Interface (IPSI) circuit packs part way into its designated slot in media gateway B. 9. Connect the long ribbon cable to the connector on the component side of the TN2312BP Internet Protocol Server Interface (IPSI) in media gateway A (red line on bottom). See Figure 97: High/Critical Ribbon Cable Connection on page 1194. 10. Fully insert the TN775D Maintenance (EPN) and TN2312BP Internet Protocol Server Interface (IPSI) circuit packs.
Issue 2.1 June 2006
1195
11. If both ribbon and CAT5 cables were installed, replace rear covers and ground plates. See Figure 99: Replace rear covers and ground plates (SCC1 shown) on page 1196. If CAT5 cables need to be installed, leave the rear covers and ground plates off and go to Adding control network cabling for the new circuit pack on page 1197. Figure 99: Replace rear covers and ground plates (SCC1 shown)
KL
FF OT UA
18
11 10
KL
FF OT UA
AU X 17
10 9
TE
RM
cadsrib5 KLC 032602
Figure notes: 1. Media Gateway B 2. Media Gateway A 3. Ground plate covering TDM cable opening. Note: All cables running between or exiting media gateways use the opening provided for TDM cables.
Procedure
Adding control network cabling for the new circuit pack

To connect the duplicated IPSI slot to the control network: 1. Connect the TN2312BP I/O Adapter to the backplane amphenol connector that corresponds to the slot in which the TN2312BP is installed. 2. Connect a CAT5 or better Ethernet cable to the RJ45 connector on the IPSI adapter. 3. Connect the other end of the CAT5 cable to the new, or alternate, Ethernet switch.
Verifying the IPSI circuit packs are inserted properly

To check that the IPSI circuit packs are inserted properly, perform the following steps: 1. After about 1 minute, open the SAT Circuit Packs screen using display circuit-pack cabinetnumber. Verify that the TN2312B circuit packs are shown in the appropriate slots.
Programming the duplicated IPSI circuit pack

Complete one of the following two steps for either DHCP addressing or static addressing. Use DHCP addressing usually with dedicated control networks. Use static addressing usually with non-dedicated control networks. Note: Clear the ARP cache on the laptop before connecting to another IPSI by entering arp -d 192.11.13.6 at the Windows command prompt. 1. For DHCP addressing, complete these steps: Note: After you reseat the circuit pack, you must start the configuration operation within 5 seconds. a. Reseat the IPSI circuit pack. The display flashes. b. Set the Switch ID and cabinet number by pressing the recessed button on the IPSI faceplate.
Note:
Note:
! CAUTION:
CAUTION:
The display on the secondary IPSI must be exactly the same as that of the existing IPSI. For example, if the IPSI in cabinet/carrier A reads A01, then the IPSI in cabinet/carrier B must also read A01.
Issue 2.1 June 2006
1197
c. When finished, skip to the next task, Setting VLAN and diffserv parameters on page 1198. Tip:
Tip:
For more information about these settings, see Adding New Hardware Avaya S8500 and S8700 Series Media Servers (555-245-212). 2. For static addressing instead of DHCP, complete these steps: a. Connect the services laptop to the Services port on the IPSI faceplate. b. Type telnet 192.11.13.6 to telnet to the IPSI. c. At the IPSI prompt, enter ipsilogin to log in to the IPSI IP Admin Utility. d. Log in using craft and the IPSI password e. Type set control interface ipaddr netmask to enter the static IP address and netmask. f. Enter quit to save the changes and exit the IPSI session. g. Telnet to 192.11.13.6 and login. h. Enter show control interface. The system displays the IP address, subnet mask, and default gateway information. Verify that the proper information was entered. i. If a default gateway is used, type set control gateway gatewayaddr where gatewayaddr is the customer-provided IP address for their gateway. j. Enter quit to save the changes and exit the IPSI session. k. Telnet to 192.11.13.6 and login. l. Use show control interface to verify the administration. m. Enter quit. Then enter reset and answer y (yes).
Setting VLAN and diffserv parameters

If required, complete the following steps to set the VLAN and diffserv parameters: 1. Log back in to the new IPSI. 2. Enter show qos to display the quality of service values. 3. If necessary, use the following commands to set the VLAN and diffserv parameters to the recommended values shown: Note: Use Help to obtain syntax guidelines for these commands.

Note:
Enter set vlan priority 6 Enter set diffserv 46
Procedure
Enter set vlan tag on Enter set port negotiation 1 disable Enter set port duplex 1 full Enter set port speed 1 100
4. Enter show qos to check the administered values. 5. Enter quit to exit.
!
Important:
Important: Ensure that the port settings on the Ethernet switches are set to the same values as in the set port commands.
6. Telnet to the IPSI and log in. 7. Enter reset. Enter y in response to the warning. 8. Disconnect the laptop from the IPSI. 9. Verify that the LED display on the IPSI faceplate contains I P and a filled-in V at the bottom.

Administering the duplicated IPSI circuit pack on the media server

To administer the TN2312BP circuit pack on the media server: Note: Steps 1 needs to be completed just once for all IPSIs. Step 2 must be repeated for each duplicated IPSI you are adding. 1. On the SAT command line interface, enter change system-parameters duplication and set Enable Operation of IPSI Duplication to y. 2. Enter add ipserver-interface n, where n is the PN number, to add the new IPSI.
Note:
Issue 2.1 June 2006
1199

Tip:

Note:
Note: For information about upgrading the IPSI firmware, see Upgrading firmware on the IPSIs in the Upgrades section of this book.
To upgrade firmware on the IPSIs: 1. Open the Maintenance Web Interface. 2. Copy IPSI firmware to the media processor hard drive. Use Download Files under Miscellaneous. 3. Determine which IPSIs you need to upgrade, using IPSI Version under IPSI Firmware Upgrades. 4. Download the new firmware to the IPSIs. Use Download IPSI Firmware. 5. Use Activate IPSI Upgrade to activate the new firmware. 6. When the IPSIs are recovered, use IPSI Version to verify the firmware versions.
Introduction
Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers only)
Introduction
This module describes the procedures to convert an Internet Protocol port network connectivity (IP-PNC) configuration from simplex bearer reliability to duplicated bearer reliability. The PNs are controlled by a pair of S8700 series media server. All voice and data transmission between the PN you are converting and other PNs in the network occurs over the customers LAN/WAN. If the active media processor, or connections to it, fail, active connections failover to the standby media processor and remain active. This duplication prevents calls from being dropped in case of failure. Note: Only two TN2602AP circuit packs are allowed per port network.
Note:
! CAUTION:
CAUTION:
The 4606, 4612, and 4624 telephones do not support the bearer duplication feature of the TN2602AP circuit pack. If these telephones are used while an interchange from active to standby media processor is in process, calls may be dropped.
!
Important:
Important: These conversion procedures assume that the S8700 series media servers are running release 3.1 or later of Communication Manager. If not, the media servers must be upgraded to release 3.1 before starting the conversion procedure. To upgrade the media servers, see the appropriate upgrade module in this book.
Duplicated control network

These procedures apply whether or not there is also an existing duplicated control network. Avaya strongly recommends a duplicated control network be configured prior to or along with the conversion to duplicated bearer. Though existing connections may continue during most failures to the port network, no new connections can be made if the control network is part of the failure.
Issue 2.1 June 2006
1201
Converting simplex bearer to duplicated bearer on IP-PNC port networks (with S8700-series Media Servers
Overflow with coresident TN2302AP circuit packs

If you anticipate that at peak traffic periods, traffic on the port network will exceed the maximum administered VoIP channels, 80 or 320, of the TN2602AP circuit pack, a TN2302 may be coresident. Communication Manager will pass excess traffic over the TN2302 at peak traffic periods, but these calls will not be supported by the duplicated reliability.
Reduced channels with duplicated TN2602AP circuit packs

If a pair of TN2602AP circuit packs previously used for load balancing are re-administered to be used for bearer duplication, only the voice channels of whichever circuit pack is active can be used. For example,
If you have two TN2602 AP circuit packs in a load balancing configuration, each with 80 voice channels, and you re-administer the circuit packs to be in bearer duplication mode, you will have 80 (not 160) channels available. If you have two TN2602 AP circuit packs in a load balancing configuration, each with 320 voice channels, and you re-administer the circuit packs to be in bearer duplication mode, you will have 320 (not 484 see the note that follows) channels available. Note: When two TN2602AP circuit packs, each with 320 voice channels, are used for load balancing within a port network, the total number of voice channels available is 484, not 640, because 484 is the maximum number of time slots available for connections within a port network.
Note:
Prerequisites
This section itemizes the information and materials you must have, and the tasks you must perform, before you can start the conversion procedure. The conversion procedure in this chapter assumes that:
The port network is an IP-PNC configuration, which means that there are no fiber links to other port networks. If not, you must first convert the port network from fiber-PNC to IP-PNC. If necessary, see one of the following: - Converting some or all direct-connect port networks to IP-connect on page 1047 - Converting some or all CSS port networks to IP-PNC on page 1079 - Converting some or all ATM port networks to IP-PNC on page 1115
Prerequisites
You have the most recent firmware for duplicated TN2602AP circuit packs. You may need to upgrade the firmware on the circuit packs if you find that they dont have the most recent and appropriate firmware. Note: Non-duplicated TN2602AP firmware is different from duplicated TN2602AP firmware. Be sure the firmware you have is for duplicated TN2602AP circuit packs.
Note:
In each IP-PNC PN that has both duplicated control and duplicated bearer, a TN771DP maintenance test circuit pack must be installed. You have completed the pre-site checklist, Presite checklist on page 1037, before going to the customer site. Unless one of the following conditions exists, you will need IP addresses, node names, and slots for the TN2602AP IP Media Resource 320 circuit packs: - You are replacing TN2302 circuit packs with the TN2602AP circuit packs and therefore are not reusing the TN2302 IP addresses, node names, and slots. - You are reusing load-balanced TN2602AP circuit packs that are already installed in the port network. You may also need the subnet mask and the default gateway IP address. Note: Get this information from the project manager or the customers network administrator.
Note:
The Communication Manager software on S8700-series Media Servers must be upgraded to release 3.1 or later. The Communication Manager license file must have at least two entries, either VALUE_2602_80VC or VALUE_2602_320VC, with the same number of VoIP channels either both 80 or both 320. (Optional) You may need to install a second Ethernet switch, if necessary, for connections to the network for the duplicated TN2602AP circuit packs. Adding a second Ethernet switch adds reliability to the duplicated bearer network. That is, if the failure is at the Ethernet switch or its connection to the TN2602AP circuit pack, the standby TN2602AP circuit pack can handle traffic through the alternate Ethernet switch. If there are already two Ethernet switches for duplicated control and the Ethernet switches are also connected to the customer LAN, you do not need a second Ethernet switch.
(Optional) If you install a second Ethernet switch, you may need to install a second UPS to support the second Ethernet switch, if necessary.
Issue 2.1 June 2006
1203
! CAUTION:
CAUTION:
If, in the unlikely event that a failure occurs on an active TN2602AP circuit pack during the setup and administration of duplication, active calls being carried on the circuit pack are dropped. In addition, TN2602AP call processing and interchange activity is tracked through the MEDPRO-C maintenance object. See Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers, 03-300430, for more information.
Checklist for converting a port network to duplicated TN2602AP IP Media Resource 320 circuit packs
The following sections describe the installation process:

Checking your shipment, if not reusing existing TN2602AP circuit packs on page 1205 Accessing the media server maintenance web interface on page 1206 Accessing the server command line interface with SSH protocol on page 1206 Checking software release on page 1207 Determining the existence and location of TN2302 and TN2602AP circuit packs on page 1208 Upgrading firmware on the existing TN2602AP circuit packs, if necessary on page 1208 Disabling an existing TN2602AP circuit pack or TN2302 circuit packs on page 1209 Removing the TN2302 circuit pack hardware on page 1209 Connecting the cables to any new TN2602AP circuit packs on page 1210 Installing the TN771DP Maintenance Test circuit pack on page 1211 Verifying installation and voice channels on page 1211 Upgrading firmware on the new TN2602AP circuit packs, if necessary on page 1213 Administering the node name for the TN2602AP circuit pack, if necessary on page 1213 Administering the IP interface for the TN2602AP circuit packs on page 1214 Testing the external connection to the LAN on page 1217 Verifying active call status on page 1217
Instructions for converting a port network to duplicated TN2602AP IP Media Resource 320 circuit packs Checking your shipment, if not reusing existing TN2602AP circuit packs
When the order arrives at your site, check the contents (see Table 23: Required Hardware on page 1205). 1. Inspect the shipping carton for damage before opening it. If the box is damaged, do not open it. Inform the shipping company, and ask for instructions on filing a claim. 2. If the box is undamaged, check the contents against the packing slip. Check the condition of each component, and note any damage or shortages on the packing slip. The carton should contain the items in Table 23: Required Hardware on page 1205 for each TN2602AP IP Media Resource 320 circuit pack ordered. 3. Read and follow any directions inserted into the package by the factory. Table 23: Required Hardware Comcode/ Code 108566381 700283690 700234032 700207111 700181118
1The
Description TN2602AP IP Media Resource 320 (MedPro) Media Resource 320 Adapter1 with retainer clip Migration kit (PEC code 63275):2 Upper circuit pack slot label Twisted pair I/O cables
Quantity 1 or 2/PN 1/MedRes
103
adapter has an amphenol connector on one side, an RJ45 connector and 2 Ethernet ports on the other for connecting to the network. See Media Resource 320 Adapter on page 1210. if installing in old carriers or cabinets with WP cables.
2Only 3
Only one cable is needed for each circuit pack.
Note:
Note: The customer must provide one CAT5 or better cable for each TN2602AP.
In addition, a TN771DP maintenance test circuit pack is required in an IP-PNC PN that has both duplicated control and duplicated bearer.
Issue 2.1 June 2006
1205


Note:
Note:
! CAUTION:
CAUTION:
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. The system displays the PuTTY Configuration window, with the Session dialog box open.
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. Press Enter. 3. In the Port field, type 22. 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: You can also customize the PuTTY tool with other settings, such as for color. For documentation on PuTTY, see http://www.putty.nl/docs.html. 8. Click Open. 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. 9. If necessary, click Yes to accept the servers host key. The system displays the PuTTY window. 10. Log in as craft.
Note:
Note:
Checking software release

To verify the software version, perform the following steps. 1. Under Server click Software Version. 2. Look in the Reports as: field to verify that the new software is running correctly. If it is, see the next step.
Issue 2.1 June 2006
1207
Determining the existence and location of TN2302 and TN2602AP circuit packs
To determine the location of existing TN2302 IP Media Processor circuit packs, perform the following steps: 1. Type display circuit-packs <port network #>, where <port network #> is the port network in which you are adding duplicated TN2602AP circuit packs. A list of circuit packs appears. 2. Locate, and record the location of, the TN2602AP circuit packs, if any. If there is only one or no TN2602AP circuit packs, locate one or two TN2302 circuit packs for replacement with TN2602AP circuit packs. Avaya recommends, when possible, that you install duplicated TN2602AP circuit packs in different carriers or cabinets. Doing so adds reliability in the event of carrier or cabinet failure. 3. Type display ip-interface UUCSS for each of the TN2302 circuit packs you are replacing or the currently installed TN2602AP circuit packs, if any. Record the existing administrative data. You can use the same node names and IP addresses as those formerly used by the TN2302 circuit packs.
Upgrading firmware on the existing TN2602AP circuit packs, if necessary

If you determined that you must upgrade the firmware on existing TN2602AP circuit packs, do so now. 1. Type campon-busyout media-processor UUCSS, where UUCSS is the location of a TN2602AP circuit pack you are converting, and press Enter. 2. Wait until all calls the circuit pack is carrying have ended. 3. Upgrade the firmware. (See Upgrading, Migrating, and Converting Media Servers and Gateways (03-300412), "Chapter 4: Upgrading Firmware on TN Circuit Packs and Media Modules.") 4. When the firmware has been installed, type release board UUCSS, and press Enter. 5. Repeat steps 1 through 4 for the other TN2602AP circuit pack, if it exists.
Disabling an existing TN2602AP circuit pack or TN2302 circuit packs

To remove any TN2302 circuit packs so you can reuse their slots, you must first disable them. To convert an existing TN2602AP circuit pack from a load-balancing circuit pack to a standby duplicated bearer circuit pack, you must first disable it. Note: Disabling the TN2302 circuit packs is optional. However, all bearer traffic is handled by the active TN2602AP circuit pack unless all channels are busy. Any overflow traffic is then handled by any remaining TN2302 circuit packs.
Note:
To disable the TN2302 or TN2602AP circuit packs, if any, perform the following steps: 1. Type campon-busyout media-processor UUCSS, where UUCSS is the location of a TN2302 circuit pack you are replacing or the TN2602AP you are converting, and press Enter. 2. Wait until all calls the circuit pack is carrying have ended. 3. Type change ip-interface UUCSS, where UUCSS is the location of a TN2302 circuit pack you are replacing or the TN2602AP circuit pack you are converting, and press Enter. 4. Type n in the Enable Ethernet Port field, and press Enter. 5. Type remove ip-interface UUCSS to remove the TN2302 or TN2602AP circuit pack from Communication Manager software. 6. Repeat steps 1 through 5 for the additional TN2302 circuit packs you are removing.
Removing the TN2302 circuit pack hardware

To remove the TN2302 circuit pack hardware, if any, perform the following steps: 1. Unseat the TN2302 circuit pack from its slot. 2. Disconnect the network cable(s) to the ETHERNET connector on the TN2302AP backplane adapter(s). 3. Disconnect the amphenol connector on the adapter from the amphenol connector corresponding to each TN2302AP slot. 4. Repeat steps 1 through 3 for the next TN2302 circuit pack.
Issue 2.1 June 2006
1209
Connecting the cables to any new TN2602AP circuit packs

You need to cable any new TN2602AP circuit packs you are installing in the port network. To install the cable for an IP Media Resource 320 circuit pack, perform the following steps: Note: If installing the TN2602AP into an old carrier or cabinet, you must replace the WP cables, which connect the backplane to the rear connector panel, with Twisted Pair I/O cables to handle the 100 Mbps speed. See Replacing the I/O cables on page 1219 for information on replacing the wires. 1. From the rear of the media gateway, connect the amphenol connector on the adapter to the amphenol connector corresponding to each TN2602AP slot. See Figure 100: Media Resource 320 Adapter. Figure 100: Media Resource 320 Adapter
2
Note:
PO
RT
4 1
PO 2 RT
addf2602 LAO 112105
Figure notes: 1. Amphenol connector to backplane connector corresponding to TN2602AP slot 2. RS-232 connector for services 3. Port 1: RJ45 LAN cable connection for 100 Mbps CAT5 cable 4. Port 2: RJ45 LAN connection for future use (do not use)
!
Important:
Important: Plug the CAT5 cable into the top port labeled Port 1. Do not plug it into the second port.
2. Connect the network cable(s) to the Port 1 ETHERNET connector on the Media Resource 320 adapter(s) on the backplane. 3. Snap the retainer clip(s) over the adapter(s) to hold them in place.
Installing the TN2602AP circuit packs, if new

! CAUTION:
CAUTION:
When adding or replacing any hardware, be sure to ground yourself against electrostatic discharge (ESD) by wearing a grounded wrist strap. Note: The TN2602AP circuit packs are hot-swappable, so you do not need to power down the media gateway to install them. Note: To properly seat the circuit pack, push firmly on the front of the faceplate until the latch reaches the bottom rail of the carrier. Then close the latch until it is fully engaged.
Note:
Note:
The following step installs the circuit pack. 1. Insert the TN2602AP circuit pack into the port slot you reserved for it and seat it properly. When you plug in the TN2602AP circuit pack, it starts to boot. The RED LED stays on until the onboard firmware is operational.
Installing the TN771DP Maintenance Test circuit pack

If the port network will have both duplicated control and duplicated bearer, install a TN771DP circuit pack. For more information, see Adding New Hardware Avaya S8500 and S8700-series Media Servers, 555-245-112.
Verifying installation and voice channels

Note:
Note: If you are reusing two existing TN2602AP circuit packs, you can skip this task.
To verify the installation: 1. Type list configuration board UUCSS and press Enter, where UUCSS is the cabinet, carrier, and slot location of the TN2602AP. 2. Verify that TN2602AP shows in the slot location. 3. Look under the Vintage column and note the firmware version. If the firmware version is not the most recent available from the Avaya Downloads Web site, you must upgrade the firmware on the circuit pack.
Issue 2.1 June 2006
1211
4. Type display system-parameters customer-options and press Enter. The Optional Features screen appears. 5. Go to page 2 of the Option Features screen. Figure 101: System Parameters Customer-Options screen
display system-parameters customer-options OPTIONAL FEATURES IP PORT CAPACITIES Maximum Administered H.323 Trunks: Maximum Administered IP Trunks: Maximum Concurrently Registered IP Stations: Maximum Administered Remote Office Trunks: Maximum Concurrently Registered Remote Office Stations: Maximum Concurrently Registered IP eCons: Maximum Video Capable H.323 Stations: Maximum Video Capable IP Softphones: Maximum Administered SIP Trunks: Maximum Number of DS1 Boards with Echo Cancellation: Maximum TN2501 VAL Boards: Maximum G250/G350/G700 VAL Sources: Maximum TN2602 Boards with 80 VoIP Channels: Maximum TN2602 Boards with 320 VoIP Channels: 100 10 0 0 0 0 0 USED 96 10 0 0 0 0 0 page 2 of x
0 1 0 20 4
0 0 0 12 3 0
Maximum Number of Expanded Meet-me Conference Ports: 0
(NOTE: You must logoff & login to effect the permission changes.)
6. Find the appropriate field, either the Maximum TN2602 Boards with 320 VoIP Channels or Maximum TN2602 Boards with 80 VoIP Channels field. Subtract the number in the Used column with the maximum number listed to the left of the Used column. If you are installing two new TN2602AP circuit packs, there must be two boards of the same number of channels available. If not, a new license must be installed. If you are installing one new TN2602AP because the port network already has one available, then there must be one board of the same number of channels available.
Upgrading firmware on the new TN2602AP circuit packs, if necessary

If you determined that you must upgrade the firmware on newly-installed TN2602AP circuit packs, if any, do so now. See Upgrading, Migrating, and Converting Media Servers and Gateways (03-300412), "Chapter 4: Upgrading Firmware on TN Circuit Packs and Media Modules."
Administering the node name for the TN2602AP circuit pack, if necessary
Note:
Note: If you are replacing one or two TN2302 circuit packs, you can reuse the node name and IP address for those circuit packs. Therefore, you may be able to skip this task for one or both TN2602AP circuit packs.
To administer the node names for the circuit packs, perform the following steps: 1. Type change node-names ip and press Enter. 2. Type in the node names and IP addresses for the TN2602AP.
change node-names ip Name cognac default medres03a01 medpro02b04 medpro02b05 clan03a04 clan03a05 clan04b04 IP NODE NAMES Name Page 1 of 1
IP Address IP Address 172.16 .19 .2 . . . 0 .0 .0 .0 . . . 192.168.1 .82 . . . 192.168.1 .83 . . . 172.16 .19 .222 . . . 192.168.1 .80 . . . 172.16 .19 .220 . . . 172.16 .19 .118 . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 12 of 12 administered node-names were displayed ) Use 'list node-names' command to see all the administered node-names
3. Type display circuit-packs and press Enter. Verify that the TN2602AP shows up in the Code column. 4. Repeat steps 1 through 3 for the second circuit pack, if necessary.
Issue 2.1 June 2006
1213
Administering the IP interface for the TN2602AP circuit packs

To administer the IP interface for the circuit packs, perform the following steps on the circuit pack you want to be the active circuit pack: Note: Any calls active when you start this procedure continue to use the TN2602AP circuit packs physical IP address for the connection, not the virtual IP address you are setting in this procedure. Therefore, any of these calls, if they continue after you complete this procedure, will drop in the event of an interchange. 1. Type one of the following commands:
Note:
For a previously-existing TN2602AP circuit pack that is still administered, type change ip-interface UUCSS and press Enter, where UUCSS is the cabinet, carrier, and slot location. For a newly-installed TN2602AP circuit pack that you are administering as the active circuit pack, type add ip-interface UUCSS, and press Enter
The IP Interfaces screen appears.

add ip-interface 1a03 IP INTERFACES Critical Reliable Bearer? n MEDPRO 01A03 TN2602 medres03a01 192.168.1.82 255.255.255.0 . . . y 1 n Page 1 of 1
Type: Slot: Code/Suffix: Node Name: IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? Network Region: VLAN:
ETHERNET OPTIONS Auto? n Speed: 100 Mbps Duplex: Full
2. In the Critical Reliable Bearer? field, type y, and press Enter. A second column of data for a standby TN2602AP appears on the right of the screen.
add ip-interface 1a03 IP INTERFACES Critical Reliable Bearer? y MEDPRO 01A03 Slot: TN2602 Code/Suffix: medpro03a01 Node Name: 192.168.1.82 IP Address: 255.255.255.0 . . . y Enable Ethernet Port? 1 n VLAN: xxx 255.255.255.255 Virtual MAC Address: ETHERNET OPTIONS Auto? n Auto? Speed: 100 Mbps Speed: Duplex: Full Duplex: Page 1 of 1
Type: Slot: Code/Suffix: Node Name: IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? Network Region: VLAN: VOIP Channels: Shared Virtual Address: Virtual MAC Table:
y n
n 100 Mbps Full
3. Complete the following fields.
The Type, Slot, IP Address, and Code/Suffix fields for the active circuit pack are populated automatically. In the Node Name field, type the same node name entered on the Node Name screen. In the Subnet Mask field, enter the subnet mask determined by the LAN administrator. This setting also applies to the second TN2602AP circuit pack when Critical Reliable Bearer is y. In the Gateway Address field, use the address determined by the LAN administrator. This setting also applies to the second TN2602AP circuit pack when Critical Reliable Bearer is y. Set the Enable Ethernet Port field to y. Set the Net Region field to 1 or another number determined by the LAN administrator. This setting also applies to the second TN2602AP circuit pack when Critical Reliable Bearer is y. Set VLAN to n. Set the VOIP Channel field to 80 or 320, depending on the number of circuit packs that are licensed for each, and the capacity the customer needs for this port network. This setting also applies to the second TN2602AP circuit pack when Critical Reliable Bearer is y.
Issue 2.1 June 2006
1215
Set the Shared Virtual Address field to the virtual IP address shared by the two TN2602AP circuit packs. Set the Virtual MAC Table field to a number from 1 to 4. Normally, you can enter 1. However, you might choose a different table number if all of the following conditions exist: - A port network under the control of a different Communication Manager main server has duplicated TN2602AP circuit packs. - That port network controlled by a different main server has the same number as the port network in which you are administering the TN2602AP circuit packs. - The port network or its main server connects to the same Ethernet switch as the port network in which you are administering the TN2602AP circuit packs. Selecting a different Virtual MAC Table from that chosen for a port network that has the previously-listed conditions helps prevent the possibility that two TN2602AP circuit packs within the customers network will have the same virtual MAC address.
The Virtual MAC Address field is populated automatically with a MAC address from the Virtual MAC Table you select.
4. Complete the following fields for the standby TN2602AP circuit pack:

In the Slot field, type the slot number of TN2602AP circuit pack. In the Node name field, type the name of the TN2602AP circuit pack. Set the Enable Ethernet Port field to y. Set VLAN to n. Set Ethernet Options to match the customers network for both circuit packs. The recommended settings are - Auto: y (default) If you enter n, also complete the following fields. The recommended values are displayed. - Speed: 100 Mbps - Duplex: Full
5. Press Enter to save the information and effect the new settings.
Testing the external connection to the LAN

To test the external IP connections, ping a computer on the same subnet, the gateway, and a computer beyond the gateway. If everything is configured correctly, the Result column on the Ping Results screen reads pass. If it reads abort, verify the IP-address information and check the connectivity, including the cabling. 1. Type ping ip-address ipaddress board UUCSS and press Enter, where ipaddress is the IP address of the TN2602AP IP Media Resource 320 and UUCSS is the cabinet, carrier, and slot location of a C-LAN circuit pack or another media processor circuit pack within the subnet.
ping ip-address 192.168.10.38 board 02B05 PING RESULTS End-pt IP 192.168.10.21 Port 01A13 Port Type MEDRES Result PASS Time(ms) 10 Error Code
2. If step 1 passes, type ping ip-address ipaddress board UUCSS and press Enter, where ipaddress is the IP address of an endpoint on the customers gateway and UUCSS is the cabinet, carrier, and slot location of the TN2602AP circuit pack you are testing. 3. If step 2 passes, type ping ip-address ipaddress board UUCSS and press Enter, where ipaddress is the IP address of an endpoint beyond the gateway and UUCSS is the cabinet, carrier, and slot location of the TN2602AP circuit pack you are testing. The TN2602AP IP Media Resource 320 circuit pack is now installed in the media gateway and connected to the IP network.
Verifying active call status

To verify that calls are being processed: 1. Make an external trunk call to a telephone on the port network and leave the call active. 2. Type status media-processor board UUCSS, where UUCSS is the location of the active circuit pack. The Media Processor Status screen appears.
Issue 2.1 June 2006
1217
status media-processor board 1c03 MEDIA-PROCESSOR STATUS Duplication State: Board Location: Source IP Address: Node Name: Subnet Mask: Gateway Address: MAC Address: Ethernet Enabled? active 1c03 192.168.22.11 medpro1 255.255.255.0 192.168.22.255 00:00:04:0d:05:03 yes Duplication State: Board Locations: Source IP Address: Node Name: Subnet Mask: Gateway Address: MAC Address: Ethernet Enabled?
Page 1 of 1
standby 1c07 192.168.22.51 medpro2 255.255.255.0 192.168.22.255 00:00:04:0d:05:07 yes
COMMON DUPLICATED VALUES Links mpcl: up eth: up peer: up Alarms mj: 0 mn: 0 wn: 0 Standby Refreshed: Network Region: Shared IP Address: Shared Virt-MAC: yes Locked? no 1 135.9.72.52 02:00:04:0d:05:18 Links mpcl: up eth: up peer: up Alarms mj: 0 mn: 0 wn: 0
DSP CHANNEL STATUS DSP DSP DSP DSP 1: 2: 3: 4: in-service/active, in-service/active, in-service/active, in-service/active, 60 50 57 47 calls calls calls calls DSP DSP DSP DSP 1: 2: 3: 4: in-service/standby in-service/standby in-service/standby in-service/standby
3. Look at the LINKS and DSP CHANNEL STATUS categories to determine whether the call is being processed. 4. Type set media-processor UUCSS, where UUCSS is the location of the standby TN2602AP circuit pack. The standby TN2602AP circuit pack becomes active. 5. Type status media processor board UUCSS, where UUCSS is the location of the newly-active circuit pack. The Media Processor Status screen appears. Under DSP CHANNEL STATUS, the test call has moved to the column for the newly-active TN2602AP circuit pack. Note: TN2602AP call processing and interchange activity is tracked through the MEDPRO-C maintenance object. See Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers, 03-300430, for more information.
Note:

Note:
Note: You only need to replace the I/O cables for the TN2602AP circuit packs you are installing.

! CAUTION:
CAUTION:
! CAUTION:
CAUTION:

2. Note the orientation of the existing 10 cables. The existing I/O cables can be white and red or multicolored. These cables are not twisted. 3. Remove the I/O cables that you want to replace from the backplane and the connector panel slots. 4. Install the twisted pair I/O cables onto the backplane in the place of the cables you just removed. Use the correct orientation (Proper orientation for the twisted pair I/O cables on page 1221). Observe the white outline that is printed on the backplane for the location of each connector.
Issue 2.1 June 2006
1219
5. View the cables from the "wiring" side of the twin connectors. That is, view the cables while you plug the cables into the backplane. Connectors oriented correctly for plug-in look like the cables in Proper orientation for the twisted pair I/O cables on page 1221. The circled pin locations are No-Connects." At the top there is an orange-black pair on the right and a violet-brown pair on the left. Do not install wires in these locations. If you are replacing I/O cables for all slot positions, plug all cables into the backplane. Then, match the "D" connector on each cable to the carrier frame. You must install the 50-position metal shell "D" connectors into the carrier frame. Also, from the rear of the media gateway, look at the pins. Ensure that the longer side of the "D" connector (pins 1 to 25) is toward the right . 6. Apply the 10/100 mbps label to the front of the carrier slot. Apply the label over the slot label that corresponds to the slot where you installed the twisted pair I/O cable. 7. For the G600 Media Gateway, replace the fan unit if you are not adding any media gateways. If you are adding more media gateways to the rack, leave the fan units off until you install all the TDM cables. Figure 102: G600 Media Gateway fan assembly removal
fndpremv LJK 102600
2 1
iodspair KLC 072602
Issue 2.1 June 2006
1221
Converting software duplication link to a DAL1 link on an S8720 Media Server

!
Important:
Important: Always check the Avaya Support Web site for Product Support Notices at http:// support.avaya.com and select Communication Manager > Product Support Notices.
This module describes the steps required to replace a software duplication link on an S8720 Media Server with the DAL1 duplication circuit pack (Material code 700262306):

Before you start on page 1223 Removing power from the server(s) on page 1224 Removing the server from the rack on page 1225 Removing the top cover from the server on page 1226 Removing the riser assembly on page 1226 Inserting the DAL1 circuit pack on page 1227 Replacing the riser assembly on page 1228 Replacing the cover on the server on page 1230 Replacing the server in the rack on page 1230 Restoring power to the server(s) on page 1231 Connecting to the active media server on page 1232 Accessing the media server maintenance web interface on page 1232 Reconnecting the duplication cables on page 1233 Reconfiguring the Ethernet interface on page 1234 Checking system status on page 1235
Before you start

Verify that you have the following on site:

DEF CP DAL1 (Material code 700262306) replacement duplication circuit pack Electrostatic wrist ground strap and mat
Issue 2.1 June 2006
1223
Removing power from the server(s)

To shut down a S8710 or S8720 server pair: 1. At the Web interface main menu for the standby server select Backup Now and backup the data to flashcard. 2. At the Web interface main menu for the standby server, select Shutdown Server. The Shutdown This Server page appears.
3. Select Immediate Shutdown and clear the Restart server after shutdown option. 4. Press the Shutdown button and wait until the server has turned off. 5. At the main menu for the active server, select Backup Now and backup the data to flashcard. 6. Select Shutdown Server with these options:

Choose the Immediate option Select Even If Server is Active Do not select Restart server after shutdown.
7. Click the Shutdown button and wait until the server has turned off. 8. When both servers are turned off, remove power from the servers.
Removing the server from the rack

! DANGER:
DANGER:
The Avaya S8720 Media Server weighs between 20-27kg (47-60 pounds). Do not remove the server from the rack by yourself.
To remove the server from the rack: 1. Remove and label all cables from the front and back panels of the server. 2. Release the two locking clips (Note 1 in Figure 104) on each side of the server. Figure 104: Remove the server from the rack
di
COMPAC
sc
T
Duplex ch 1 ch 2
1 2 UID
Simplex
h3df87rk LAO 101905
Figure notes: 1.
Release both latches
2.
Slide the server out of the rails
3. Pull the server straight out of the rails until it is completely free and set it on the antistatic mat.
Issue 2.1 June 2006
1225
Removing the top cover from the server

To remove the top cover from the server: 1. Lift the locking tab on the top cover of the server as shown in Figure 105 Figure 105: Remove the cover from the server
2 1
di
COMP ACT
sc
Duplex ch 1 ch 2
1 2 UID
Simplex
h3df8cvr LAO 101905
Figure notes: 1.
Locking tab
2.
Cover slides back for removal.
Lifting the tab slides the locking tabs of the cover free of the front panel. 2. Lift the cover straight up and set it aside.
Removing the riser assembly

To remove the riser assembly: 1. Release the two thumbscrews (Note 1 in Figure 106).
Figure 106: Remove the riser assembly

1 2
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
3 z G 0M 10
2 z G 0M 10
1 z G 3M 13
3
VD
CI
h3df87cr LAO 102505
Figure notes: 1.
Loosen both thumbscrews.
2.
Lift riser assembly straight up.
2. Lift the riser assembly straight up and set it on the antistatic mat.
Inserting the DAL1 circuit pack

To insert the DAL1 circuit pack: 1. Remove the DAL1 circuit pack from its protective packaging and set the circuit pack on the antistatic mat beside the riser assembly. 2. Align the circuit pack with the riser assembly and push the circuit pack into the slot above the quad-NIC circuit pack (see Figure 107).
Issue 2.1 June 2006
1227
Figure 107: Insert the DAL1 circuit pack
2 1
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
h3dsdali LAO 102505
Figure notes: 1.
Slide the DAL1 board into the slot above the quad-NIC circuit pack. Secure the board in the slot by tightening the thumb screw.
3.
Close the locking lever.
2.
Replacing the riser assembly

To replace the riser assembly: 1. Align the three tabs of the riser assembly with the guides on the server chassis as shown in Figure 108.
Figure 108: Replace the riser assembly

2
RECEIVE MODE
TRANS MODE
LINC SYNC
LINC ACTIVE
DAL1 DUP MEMORY
0M 10
3 z G
0M 10
2 z G
3M 13
1 z G
VD
CI
h3df87ci LAO 102505
Figure notes: 1.
Align tabs and insert carrier into connector.
2.
Tighten both thumb screws.
2. Slide the riser assembly in the slots until it rests on the base of the chassis and is aligned with the two thumbscrew holes. 3. Tighten the two thumbscrews to secure the riser assembly in place. 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.
Issue 2.1 June 2006
1229
Replacing the cover on the server

To replace the cover on the server: 1. Place the top cover on the media server so that the front alignment tabs are in place (refer to Figure 105: Remove the cover from the server on page 1226. 2. Push the locking lever down. The cover slides forward and locks into place.
Replacing the server in the rack

! DANGER:
DANGER:
The Avaya S8720 Media Server weighs 20-27kg (47-60 pounds). Do not replace the server in the rack by yourself.
To replace the server in the rack: 1. Ensure that the rails are extended and locked into place as shown in Figure 109.
Figure 109: Replace the server in the rack
di
COMPAC
sc
T
Duplex ch 1 ch 2
1 2 UID
Simplex
h3df87ri LAO 101905
Figure notes: 1.
Place server on rails, slide into place.
2.
Lock both tabs securely.
2. Align the server on the rails and push the server into the rack until the server is flush with the rack. 3. Push the two locking levers down to secure the server in the rack (Note 2 in Figure 109). 4. Replace all cable connections to the front and back panels of the server.
Restoring power to the server(s)

To restore power to the S8720 server: 1. Apply power to the servers by plugging the power cable into the socket on the back of the server. 2. Push the power button on the front panel of the servers.
Issue 2.1 June 2006
1231


Reconnecting the duplication cables

Connect the duplication cables as shown in S8720 duplication and control network cables for hardware duplication on page 1233 Figure 110: S8720 duplication and control network cables for hardware duplication
3
100 MGz
LINC SYNC
2
100 MGz
iLO
2
2 1
UID
6
VDCI
133 MGz
2
3
3
100 MGz
LINC SYNC
2
100 MGz
iLO
1
2 1
UID
1
133 MGz
VDCI
3 1 5
Figure notes: 1. CNA (also LAN for nondedicated control network) Eth0 2. Duplication cable (Crossover) Eth2 3. CNB (if used) Eth3 4. LAN (if dedicated control network) Eth4 5. CNC (if used) Eth5 6. Fiber duplication cable
h3df87hd LAO 103105
Issue 2.1 June 2006
1233
Reconfiguring the Ethernet interface

To reconfigure the Ethernet interface so that the duplication link uses the DAL1 board, perform the following steps: 1. Under Server Configuration, click Configure Server to open the first page of the Configure Server process. 2. Click Continue through the Review Notices to get to the Specify how you want to use this wizard page. 3. Select Configure individual services and click Continue. 4. Click Set Identities from the main menu. 5. On the Set Server Identities window:

Select This is a duplicated server using duplication hardware. Under Select NIC Usage, assign the Ethernet ports according to the following table, and click Continue. Control Network Dedicated Hardware Memory Duplication
LAN to Eth4 which is the 3rd port from the left on the quad NIC CNA to Eth0 which is the port labeled "1" on the server CNB (if used) to Eth3 which is the 2nd port from the left on the quad NIC LAN or CNA to Eth0 which is the port labeled "1" on the server CNB (if used) to Eth3 which is the 2nd port from the left on the quad NIC
Nondedicated
6. In the Configure Interfaces window, do the following steps:

Enter the IP addresses of the duplication link port (Eth 2) on each server. Select AUTOSENSE for the speed.
Click Change to update the media server. When the screen shows Successfully configured ethernet interfaces. 7. Click Close Window to close the Configure Server wizard.


Issue 2.1 June 2006
1235
Appendix A: Accessing the media server

You must have access to the media server for administration. The following computers and software are the supported access points for accessing the media 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 media 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. This appendix contains the following sections:

Connecting to the media server directly on page 1237 Connecting to the media server remotely over the network on page 1243 Connecting to the media server remotely over a modem on page 1243 Logins on page 1248 Network configuration on page 1249
Connecting to the media server directly

To access the media server directly, plug a laptop computer into the services port on the media server.
On the S8300 Media Server plug the CAT5 cable into the services port on the front as shown in Figure 111. On the S8500 Media Server, as shown in Figure 112, and the S8700-series Media Server, as shown in Figure 113, plug one end of a crossconnect CAT5 cable into the services port. This port defaults to port 2 (Eth1), On the back of the media server, plug the other end into the NIC on your computer. You might need a NIC adapter.
For more information about connectivity for your media server, see
A services laptop computer that is connected directly to the S8300 Media Server on page 1238 A services laptop computer that is connected directly to the S8500 Media Server on page 1239
Issue 2.1 June 2006
1237
A services laptop computer that is connected directly to the S8700 Media Server on page 1240 A services laptop computer that is connected directly to the S8710 Media Server or S8720 Media Server (S8710 Media Server shown) on page 1241.
Figure 111: A services laptop computer that is connected directly to the S8300 Media Server
2 3
2 3
51 ALM PWR CPU MSTR LNK COL Tx Rx FDX FC Hspd LAG
52
53
54
55
56
57
58
EXT 1 EXT 2
V2
59
60
61
62
63
64
65
66
ALM TST ACT SIG
SO
EI
SM EM
SI
EO
E1/T1
EIA 530A DCE
V1
ALM TST ACT OK TO REMOVE
V3
SHUT DOWN SERVICES USB 1 USB 2
ALM TST ACT
V4 EXT 1 EXT 2
ALM TST ACT
CONSOLE
1 2 3 4 5 6 7 8
51 COL Tx Rx FDX FC Hspd LAG
52
53
54
59
60
61
62
SERVICES
CONSOLE
cadllap2 LAO 032405
Figure notes: 1. Services laptop 2. Network interface card (NIC) 3. NIC adapter cable (if necessary) 4. Black CAT5 cross-connect cable
Connecting to the media server directly
2 3
cadlsrv3 KLC 093004
Figure notes: 1. Services laptop 2. Network interface card (NIC) 3. NIC adapter cable (if necessary) 4. Black CAT5 cross-connect cable
Issue 2.1 June 2006
1239
2 3
AVAYA
DAI - 1 DUP MEMORY
LINE
RECEIVE
TRANS
LINK STAT
cadlsrvr KLC 030402
Figure notes: 1. Services laptop 2. Network Interface Card (NIC) 3. NIC adapter cable (if necessary) 4. Black CAT5 crossconnect cable
Connecting the G700 Media Gateway directly
Figure 114: A services laptop computer that is connected directly to the S8710 Media Server or S8720 Media Server (S8710 Media Server shown)
2 3
4
3
3
100 MGz
RECEIVE MODE LINC ACTIVE
DAL1 DUP MEMORY
TRANS MODE
LINC SYNC
2
100 MGz
iLO
1
133 MGz
VDCI
UID
cadlsrv2 KLC 042804
Figure notes: 1. Services laptop 2. Network Interface Card (NIC) 3. NIC adapter cable (if necessary) 4. Black CAT5 crossconnect cable
Connecting the G700 Media Gateway directly

To access the G700 Media Gateway directly, you plug a laptop computer into the Console port on the media gateway. Plug one end of the CAT5 cable into the services port on the front of the media gateway. Plug the other end into the NIC on your computer. For more information about connectivity for your media server, see Figure 111.
Issue 2.1 June 2006
1241
Computer specifications
The computer that you use to access the media server must have the following minimum specifications:

Windows 2000 or Windows XP operating system 32-MB of RAM 40-MB of available disk space An RS-232 port connector 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 configuration
You also must configure your network connection. For more information, see Network configuration on page 1249. 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 media server through these interfaces:

The Maintenance Web Interface for server-specific administration. A command line interface in a Telnet or terminal emulation application for Linux and SAT commands, respectively. For duplicated media servers, you can use the SAT commands on the active media server only.
For more information, see Accessing the Maintenance Web Interface on page 1245.
Connecting to the media server remotely over the network
Connecting to the media server remotely over the network

You can access the media server from any computer that is connected through the LAN. However, the LAN security settings must allow remote access. To access the media 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 media server you want to access. For duplicated media servers, you can use the active (alias) media server address to connect automatically to the media server that is active.
Connecting to the media server remotely over a modem

This section describes the following tasks:

Setting up a dial-up connection on page 1244 Dialing up to the media server on page 1244 Finding the IP address of the active media server (duplicated servers) on page 1245 Accessing the Maintenance Web Interface on page 1245 Using the command line interface on page 1246 Note: Remote access over a modem is for Avaya services support access only and not for routine administration. Because the media server uses the same line to report alarms, the media server cannot report new alarms while the line is in use.
Note:
You can access the media server through an analog modem. The remote connection requires a data speed of at least 33.5 kilobits per second. On the S8500 Media Server, you access the media server through the remote maintenance board that is installed in the media server. For more information about how to access the SAMP, see the Avaya Server Availability Management Processor User Guide (03-300322).
Issue 2.1 June 2006
1243
Setting up a dial-up connection

To 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 media 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 media server

To 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 media server. 3. To open an SSH session, see Using the command line interface on page 1246.
Accessing the Maintenance Web Interface
Finding the IP address of the active media server (duplicated servers)

To find the IP address of the active media 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 media server to which you are connected.
Accessing the Maintenance Web Interface

To access the Maintenance Web Interface. You can either connect:
Directly to the services port on the media server. For more information, see Connecting to the media server directly on page 1237. 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 media server, you must disable all proxy servers. For more information and instructions, see Browser settings on page 1250. To access the Maintenance Web interface: 1. Open the MS Internet Explorer Web browser. 2. Perform one of the following actions:

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 media server.
3. When prompted, log in.
Issue 2.1 June 2006
1245
Using the command line interface

Note:
Note:
! CAUTION:
CAUTION:
Using the command line interface
Note:
Note:
Accessing the command line interface with terminal emulation

To use a command line interface in a terminal emulation window: 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:

Note:
115200 baud No parity 8 data bits 1 stop bit No flow control
3. Establish a network connection to the media server with either the IP address or the DNS host name. Use port 5023 for this connection. 4. When prompted, log in.
Issue 2.1 June 2006
1247
Logins
Initial 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 media 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 media servers. For more information, see the Administrator Guide for Avaya 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.
!
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.
To configure a new network connection: 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:

Note:
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.
Issue 2.1 June 2006
1249
Browser settings
Connecting directly to the media server
To set the browser for a direct connection to the media server: 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.6 5. Click OK> OK>OK again to close all the dialog boxes.
Note:
Connecting remotely through the network

When you connect through a proxy server, a connection session to a media server can time out. To avoid a media server time out during a session, add the host names or the IP addresses of the media servers to the list of host names and IP addresses. To add the host names or the IP addresses of the media servers to the list of host names and IP addresses: 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 media 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.
Note:
Index
Index
backing up, (continued) recovery system files . 101, 116, 132, 141, 194, 214, 1051, 1084, 1120 S8500 translations. . . . . . 461, 492, 531, 562, 592 S8700-Series translations246, 637, 689, 776, 818, 853 system files, Linux migration for S8500 to S8710 878 system files, using Linux migration . . . . . 161, 179 translations for DEFINITY SI in an MCC to S 8700-Series (Multi-Connect) . . . . . . . . . 728 backplane I/O cables, replacing . 1075, 1112, 1143, 1219 backup verifying . . 102, 132, 156, 158, 215, 218, 264, 266 bearer duplication enabling . . . . . . . . . . . . . . . . . . . 1066 boot timeout for SAMP . . . . . . . . . . 94, 121, 1168 busying out IPSI . . . . . . . . . . . . . . . . . . . . . 287 media server . . . . . . . . . . . . . . . . . 177 previously busied out trunks 115, 140, 194, 245, 276, 353, 382, 411, 442, 475, 513, 546, 575, 609, 650, 700, 740, 797, 832, 869 SIPI . . . . . . . . . . . . . . . . . . . . . 287 busying out MMI circuit packs . . 154, 212, 261, 906, 955 releasing . . . . . . . . . . . . . . . . . . . 245 busyout fiber-link command . . . . . . . . . . . . 1066 busyouts, recording99, 127, 153, 211, 337, 367, 394, 425, 458, 487, 526, 631, 664, 713, 763, 905, 954
Numerical
4600-series telephones restoring configuration files . . . .115, 139, 244, 275 46xx IP Phone configuration file . . . . . . . . . . . . . 203, 255 firmware . . . . . . . . . . . . . . . . . 203, 255
A
adapter for TN2602AP . . . . . . . . . . . . . . 1210 add data-module next command . . . . . . . . . 1065 administering existing hardware . . . . . . . . . . . 665, 714, 776 IPSI on CSI in a CMC to S8500460, 490, 529, 561, 591 location assignment . . . . . . . . . . 694, 734, 791 TN2602AP . . . . . . . . . . . . . . . . . . 1213 alarm suppression releasing . . . . . . . . . . . . . . . . . 277, 278 alarm suppression, releasing117, 141, 195, 196, 247, 248, 1070, 1104, 1138 alarms resolving101, 116, 131, 140, 155, 194, 214, 246, 263, 276, 1051, 1069, 1083, 1104, 1119, 1137 suppressing 102, 132, 156, 159, 215, 218, 264, 266, 1052, 1084, 1120 ARP cache, clearing on the laptop157, 216, 346, 375, 404, 435, 468, 505, 538, 568, 601, 643, 824, 862, 876, 902, 949, 967, 1167 ATM converting to IP-PNC . . . . . . . . . . . . . 1115 converting to IP-PNC, example . . . . . . . . 1141 example configuration . . . . . . . . . . . . . 1139 synchronization . . . . . . . . . . . . . . . . 1121 Audix on S8100 . . . . . . . . . . . . . . 563, 593, 819 slim board . . . . . . 462, 563, 593, 638, 819, 854 authentication file copying to media server . . . 100, 114, 139, 243, 274 installing . . . . . . . . . . . . . . . . . 137, 273 Authentication File Web page . . . . . . . . . . . . 273
C
C363T or C364T Ethernet switch configuring . . . . . . . . . . . . . . . . . . 1183 security alert . . . . . . . . . . . . . . . . . 1183 cabinets setting number . . . . . . . . . . . . 696, 736, 793 turning off . . . . . . . . . . . . . . . . . 339, 396 turning off S8100 . . . . . . . . . . . . . . . 427 cables connecting Ethernet cables . . . . . . . . . . 665 connecting IPSI cables . . . . . . . . . . . . 665 connecting to TN2602AP . . . . . . . . . . . 1210 replacing I/O cables . . . . . . . . . . . . 595, 855 cables, connecting . . . . . . . . . . . . . . . . 1059 cables, duplication . . . . . . . . . . . . . . . . 1233 cables, for IPSI . . . . . . . . . . . . . . . 1189, 1192 cabling connecting IPSI cables to Ethernet switches 715, 777 connecting media server to Ethernet switches715, 777 IPSI and media server cables to Ethernet switches 715 call processing, stopping LSP or ESS . . . 97, 151, 209
B
backing up Linux migration upgrade set to the network for S8700 to S8710 . . . . . . . . . . . . . . . . 907 Linux migration upgrade set to the services laptop for S8700 to S8710 . . . . . . . . . . . 908
Issue 2.1 June 2006
1251
Index
campon-busyout media-processor command 1208, 1209 change circuit pack command . . . . . . . . . . 1067 change ip-interface command . . . . . . . . . . 1214 change node-names command . . . . . . . . . . 1213 change synchronization css command . . . . . . 1054 change system duplication command . . . . . . . 1066 channels verifying voice channels . . . . . . . . . 1211, 1212 channels, reduced with TN2602AP . . . . . . . . 1202 circuit pack connecting cables . . . . . . . . . . . . . . 1059 circuit pack firmware copying to media server 101, 131, 168, 185, 214, 217, 268, 286, 1050, 1082, 1118 circuit pack replacement, completing . . . . . 683, 723 circuit packs completing replacement . . . . . . . . . . . . . 785 designating slots . . . . . . . . . . . . . . . 1056 inserting . . . . . . . . . . . . 339, 370, 397, 428 removing for S8400 . . . . . . . . . . 339, 369, 397 removing from IP600 for S8400 . . . . . . . . . 428 TN570 . . . . . . . . . . . . . . . . . . . . 1067 verifying insertion . 352, 381, 410, 440, 473, 511, 544, 574, 607, 648, 698, 738, 795, 830, 867 verifying locations . 351, 380, 409, 439, 473, 511, 544, 573, 607, 648, 795, 830 verifying locations, S8700-Series . . . . . 738, 867 verifying locations, SCC . . . . . . . . . . . . . 698 CLAN administering . . . . . . . . . . . . . . . . . 1064 connecting cables . . . . . . . . . . . . . . 1060 installing . . . . . . . . . . . . . . . . . . . 1059 clearing alarms, See Resolving alarms clock synchronization verifying . . . . . . . . . . . 99, 127, 153, 211, 260 command line interface . . . . . . . . . . . . . . 1246 accessing with SSH . . . . . . . . . . . . . . 1246 commands . . . . . . . . . . . . . . . . . . . 1208 add data-module next . . . . . . . . . . . . . 1065 busyout . . . . . . . . . . . . . . . . . . . . 287 busyout fiber-link . . . . . . . . . . . . . . . 1066 campon-busyout media-processor . . . . 1208, 1209 change circuit pack . . . . . . . . . . . . . . 1067 change ip-interface . . . . . . . . . . . . . . 1214 change node-names . . . . . . . . . . . . . 1213 change synchronization css . . . . . . . . . . 1054 change synchronization port-network . . . . . 1067 change system duplication . . . . . . . . . . 1066 display circuit-pack . . . . . . . . . . . 1058, 1059 display system-parameters customer-options . . 1212 enable synchronization-switch all . . . . . . . 1068 enable tone-clock . . . . . . . . . . . . . . . 1058 ip license-server . . . . . . . . . . . . . . . 1176 list configuration . . . . . . . . . . . . 1064, 1211 list fiber-link . . . . . . . . . . . . . . . . . 1066 list ipserver-interface . . . . . . . . . . . . . . 291
commands, (continued) list synchronization . . . . . . . . . . . 1054, 1067 ping ip-address . . . . . . . . . . . . . . . . 1217 release board . . . . . . . . . . . . . . . . . 1208 remove fiber-link . . . . . . . . . . . . . . . 1066 set ipserver-interface . . . . . . . . . . . . . 291 set tone-clock . . . . . . . . . . . . . . . . . 1058 status media-processor . . . . . . . . . . . . 1217 status synchronization . . . . . . . . . . . . . 1055 test synchronization port-network . . . . . . . . 1068 Communication Manager copying . . . . . . . . . . . 106, 134, 223, 235, 270 installing . . . . 166, 183, 880, 912, 986, 1011, 1169 registering . . . . . . . . . . . 118, 142, 198, 249 upgrading S8500 . . . . . . . . . . . . . . . . 89 upgrading S8700 from R1.x . . . . . . . . . . 143 configuration file, IP telephones restoring . . . . . . . . . . . . 115, 139, 244, 275 Configure Individual Services Web page . . . . . . 1186 Configure Interfaces Web page . . . . . . . . . . 1171 Configure LSP or ESS Web page . . . . . . . . . 1172 Configure Server Web pages . . . . . . . . . . . 1234 Configure server Web pages . . . . . . . . . . . 186 connecting cables . . . . . . . . . . . . . 340, 370, 397, 428 CAT5 cables to IPSI circuit packs 497, 535, 678, 722, 731, 785, 788 to IP600 processor . . . . . . . 557, 588, 812, 847 to media servers . 465, 565, 598, 630, 640, 822, 859 to processor335, 365, 392, 424, 457, 487, 526, 663, 762 to SI processor . . . . . . . . . . . . . . . . 712 to standby media server157, 177, 196, 216, 221, 233, 247, 265, 278 connection preservation during upgrades . . . . . . 66 connection-preserving upgrade . . . . . . . . . . 219 connections preserving connections during upgrade . . . . . 254 control cabinet, turning off . . . . . . 369, 463, 564, 638, 820 configuring duplicated control . . . . . . . . . 1186 interface, setting. . . . . . . . . 348, 376, 406, 436 networks . . . . . . . . . . . . . . . . . . . 1046 control cabinet, changing for CSI in a CMC to PN for S8500 . . . . . . . 462 for DEFINITY ONE/S8100 to PN for S8700-Series 819 for IP600/S8100 to PN for S8500 . . . . . . . . 593 for IP600/S8100 to PN for S8700-Series . . 638, 854 control chassis, turning off . . . . . . . . . . 594, 855 control interface, setting469, 506, 539, 569, 602, 644, 826, 863 control network, duplicated . . . . . . . . . . . . 1181 conversions from DEFINITY One, See Migrations . . . . . . 1036 from DEFINITY R, See Migrations . . . . . . . 1036 from DEFINITY SI, See Migrations . . . . . . . 1036
Issue 2.1 June 2006
1252
Index
conversions, (continued) from IP 600, See Migrations . . . . . . . . . . 1036 from ProLogix, See Migrations . . . . . . . . . 1036 converting between Main and ESS modes . . . . . . . . 1147 from ATM to IP-PNC . . . . . . . . . . . . . 1115 from CSS to IP-PNC . . . . . . . . . . . . . 1079 from direct-connect to IP-PNC . . . . . . . . . 1047 from ICC mode to LSP mode . . . . . . . . . 1157 from LSP mode to ICC mode . . . . . . . . . 1149 from S8500 main to LSP . . . . . . . . . . . 1165 media server mode . . . . . . . . . . . . . . 1147 software duplication to DAL1 duplication . . . . 1223 to IP-PNC . . . . . . . . . . . . . . . . . . 1041 converting media servers conversion paths . . . . . . . . . . . . . . . 1036 prerequisites . . . . . . . . . . . . . . . . . 1037 converting PNC slots for new circuit packs . . . . . . . . . . . 1056 Copy settings Web page . . . . . . . . . . . . . 1186 copying license and authentication files . . . . . . . . . 919 translation files . . . . . . . . . . . . . . . . . 459 translations for S8400 . . . . . . . . . . . . . . 344 translations for S8400 using Xmodem . . . 401, 402 translations on CSI in a CMC to S8500 . 489, 528, 560, 591 copying translations to S8700 or S8710 . . . . . . . . . . 683, 723, 765 using blowback . . . . . . . . . . . . 683, 723, 765 using MOST tool . . . . . . . . 683, 723, 743, 765 corruption of translations checking for . . . . . . . . . . . . . . . . . . 100 cover of S8700-series Media Server . . . . 1226, 1230 CSS converted to mixed fiber-PNC and IP-PNC, example . . . . . . . . . . . . . . . . . . 1108 converting to IP-PNC . . . . . . . . . . . . . 1079 example configuration . . . . . . . . . . . . . 1106 synchronization . . . . . . . . . . . . . . . . 1086 customer data, verifying351, 380, 409, 439, 472, 510, 543, 573, 606, 647, 698, 738, 795, 829, 866
D
DAL1 circuit pack conversion to . . . . . . . . . . . . . . . . . 1223 inserting . . . . . . . . . . . . . . . . . . . 1227 data for a migration restoring for CSI on a CMC to S8710 . 633, 815, 850 restoring for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . . . 771 restoring for DEFINITY SI in an MCC to S8700-Series (Multi-Connect) . . . . . . . . . 725 restoring for IP600/S8100 to S8710 . . . . . . . 684
data module add data-module next command . . . . . . . . 1065 date and time setting . . . . . . . . . . . . . . . . . .174, 1171 verifying . . . . . . . . . . . . . . . . . . . 191 DEFINITY R completing migration to S8700-Series . . . . . 761 converting the PPN to a PN . . . . . . . . . . 760 cutover to S8700 or S8710 control . . . . . . . 761 installing and configuring S8700-Series complex 758 IPSI placement . . . . . . . . . . . . . . . . 758 replacing tone clock circuit packs . . . . . . . . 760 transferring existing translations . . . . . . . . 759 upgrading and replacing interface and maintenance circuit packs . . . . . . . . . . 759 diffserv parameters for the IPSI . . . . . . . . . . 1198 direct connection to media server . . . . . . . . . 1237 direct-connect converting to IP-PNC . . . . . . . . . . . . . 1047 example configuration . . . . . . . . . . . . . 1072 synchronization . . . . . . . . . . . . . . . . 1053 direct-connect PNC converted to IP-PNC, example . . . . . . . . . 1074 display circuit packs . . . . . . . . . . . . . . . 1208 display circuit-pack command . . . . . . . . 1058, 1059 display system-parameters customer-options command . . . . . . . . . . . . . . . . . . . . 1212 documentation needed . . . . . . . . . . . . . . 1040 Download Files Web page . . . . . . . . . . 158, 177 Download IPSI Firmware Web page . . . . . . . . 289 downloading Communication Manager software, see Communication Manager, copying duplicated Ethernet switches . . . . . . . . . . . . . . . 1182 duplicated bearer converting to . . . . . . . . . . . . . . . . . 1201 removing fiber duplications . . . . . . . . . . . 1066 duplicated bearer and control TN771DP circuit pack requirement . . . . . . . 1203 duplicated control converting from simplex control. . . . . . . . . 1181 duplicated control and bearer TN771DP circuit pack requirement . . . . . . . 1203 duplicated IPSIs . . . . . . . . . . . . . . . . . 1181 duplicated TN2602AP . . . . . . . . . . . . . . . 1201 duplicated UPS . . . . . . . . . . . . . . . . . . 1203 duplication cables reconnecting . . . . . . . . . . . . . . . . . 1233 duplication link assigning ports . . . . . . . . . . . . . . . . 1234 converting to DAL1 link . . . . . . . . . . . . 1223
E
EI circuit packs removing . . . . . . . . . . . . . . . . . . . 1067
Issue 2.1 June 2006
1253
Index
enable synchronization-switch all command . . . . 1068 enable tone-clock command . . . . . . . . . . . 1058 ESS converting to . . . . . . . . . . . . . . . . . 1147 stopping call processing . . . . . . . . 97, 151, 209 stopping during upgrade . . . . . . . . . . . . 94 upgrading . . . . . . . . . . . . . . . . . 93, 201 upgrading Communication Manager software . . . . . . . . . . . . . . 92, 146, 202 Ethernet cables connecting to IPSIs . . . . . . . . . . . . . . . 665 connecting to media servers . . . . . . . . . . . 665 Ethernet Interface reconfiguring . . . . . . . . . . . . . . . . . 1234 Ethernet switch duplicated . . . . . . . . . . . . . . . . . . 1182 expansion interface circuit packs installing . . . 501, 535, 683, 691, 723, 731, 785, 788
I
I/O cables for TN2602AP . . . . . . . . . . . . . . . . . 1205 I/O cables, replacing . 595, 855, 1075, 1112, 1143, 1219 IA770 INTUITY AUDIX Messaging . . . . . . . . . 413 ICC converting to . . . . . . . . . . . . . . . . . 1149 converting to LSP . . . . . . . . . . . . . . . 1157 input/output cables, see I/O cables installing authentication file . . . . . . . . . . . . . 137, 273 CLAN . . . . . . . . . . . . . . . . . . . . . 1059 Communication Manager . . . . . . 912, 986, 1011 Communication Manager software166, 183, 880, 1169 expansion control carrier and port carrier . . 730, 787 expansion interface circuit packs . 501, 535, 683, 723 IPSI . . . . . . . . . . . . . . . . . . . . . 1058 license and authentication files . . . . . 343, 401, 432 linear card reader software . . . . . . . . . . . 322 media processor . . . . . . . . . . . . . . . 1059 pre-upgrade service pack . . . . . . . 104, 222, 234 SAMP software . . . . . . . . . . . . . . . . 1173 software load on S8400 . . . . . 341, 372, 399, 430 TN771 . . . . . . . . 464, 565, 598, 640, 821, 859 TN771 for S8400 . . . . . . . . 341, 371, 398, 429 TN771DP Maintenance Test circuit pack . . . . 1211 interchanging S8700-series Media Servers . . . 175, 231 IP addresses, verifying352, 381, 410, 440, 473, 511, 544, 574, 607, 648, 698, 738, 795, 830, 867 IP interface adding TN2602AP . . . . . . . . . . . . . . . 1214 IP Media Resource administering . . . . . . . . . . . . . . 1213, 1214 testing external connection to LAN . . . . . . . 1217 verifying active call status . . . . . . . . . . . 1217 IP phone configuration file . . . . . . . . . . . . . . 203, 255 IP settings recording . . . . . . . . . . . . . . . . . 558, 589 recording for S8700-Series . . . . . . . . . . . 813 IP telephone files restoring after upgrade. . . . . . . . . . . . 90, 124 IP telephones firmware . . . . . . . . . . . . . . . . . 203, 255 restoring configuration file . . . . 115, 139, 244, 275 IP-PNC converted from CSS, example . . . . . . . . . 1108 converted from direct connect PNC, example . . 1074 converting from ATM, example . . . . . . . . . 1141 converting to . . . . . . . . . . . . . . . . . 1041 media gateways supported . . . . . . . . . . . 1043 mixed with fiber-PNC . . . . . . . . . . . . . 1042
F
fiber links removing . . . . . . . . . . . . . . . . . . . 1066 fiber-PNC media gateways supported . . . . . . . . . . 1043 mixed with IP-PNC PNs . . . . . . . . . . . . 1042 firewall LSP . . . . . . . . . . . . . . . . . . . . . 1179 settings . . . . . . . . . . . . . . . . . . . 1185 Firewall Web page . . . . . . . . . . . . . . . . 1185 firmware downloading to IPSI. . . . . . . . . . . . . . . 288 for IP telephones . . . . . . . . . . . . . . 90, 124 upgrading Ethernet switch . . . . . . . . . 293, 295 upgrading SAMP . . . . . . . . . . . . . . 97, 126 firmware download IPSI . . . . . . . . . . . . . . . . . . . . . . 288 SIPI . . . . . . . . . . . . . . . . . . . . . . 288 firmware upgrade IPSI . . . . . . . . . . . . . . . . . . . . . 1200 TN2602AP . . . . . . . . . . . . . . . . . . 1208 firmware, circuit pack copying to media server 101, 131, 168, 185, 214, 217, 268, 286, 1050, 1082, 1118
G
G150 upgrading firmware on . . . . . . . . . . 142, 279
H
h.248 media gateways upgrading . . . . . . . . . . . . . . 91, 145, 201
Issue 2.1 June 2006
1254
Index
IPSI activating firmware . . . . . . . . . . . . 289, 290 adding IPSI information for CSI in a CMC to S8700-Series . . . . . . . . . 636, 727, 817, 852 adding IPSI information for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . 775 adding IPSI information for DEFINITY SI in an SCC to S8700-Series (Multi-Connect) . . . . . 688 administering . . . . . . . . . . . . . . . . . 1061 administering and enabling on CSI in a CMC to S8500 . . . . . . . . . . 460, 490, 529, 561, 591 assigning IP addresses 467, 504, 537, 567, 600, 642, 694, 734, 791, 823, 861 busying out . . . . . . . . . . . . . . . . . . . 287 connecting cables . . . . . . . . . . . . . . 1059 connecting the cable . . . . . . . . . . . . . 1197 connecting the cables on MCC1 . . . . . . . . 1189 connecting the cables on SCC1 . . . . . . . . 1191 designating slots for duplication . . . . . . . . 1188 determining placement . . . . . . . . 666, 716, 778 DHCP addressing . . . . . . . . . . . . . . 1197 downloading firmware . . . . . . . . . . . . . . 288 duplicated ISPIs . . . . . . . . . . . . . . . 1181 enabling control472, 510, 543, 606, 647, 697, 737, 794, 829, 866 firmware download . . . . . . . . . . . . . . . 288 installing . . . . . . . . . . . . . . . . . . . 1058 installing duplicated . . . . . . . . . . . . . . 1189 installing in CSI in a CMC . . . . . . . . . 463, 639 installing in DEFINITY ONE/S8100 to S8500 564, 820 installing in IP600/S8100 to S8500 . . . . . 597, 858 installing in MCC . . . . . . . . . . . . . 494, 533 installing in SCC . . . . . . . . . . . 691, 731, 788 interchanging duplicated . . . . . . . . . . . . 291 listing . . . . . . . . . . . . . . . . . . . . . 287 logging in to . 468, 506, 539, 569, 602, 643, 825, 862 placement, DEFINITY R . . . . . . . . . . . . . 758 programming the duplicated IPSI . . . . . . . 1197 releasing standby . . . . . . . . . . . . . . . . 291 resetting . . . 470, 508, 541, 571, 604, 645, 827, 864 setting alarm activation level . 461, 491, 530, 562, 592, 637, 688, 728, 775, 818, 853 setting IPSI duplication (high/critical reliability) for CSI in a CMC to S8700-Series 636, 687, 727, 774, 818, 853 setting static IP address for CSI in a CMC to S8700-Series . . . . . . . . . . . . . . . . . 642 setting static IP address for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . 791 setting static IP address for DEFINITY SI (Direct-Connect) in an SCC to an IP-Connect . . 504 setting VLAN and diffser parameters . . . . . . 1198 static addressing . . . . . . . . . . . . . . . 1198 upgrading firmware . . . . . . . . . . . . 283, 1200 verify firmware version . . . . . . . . . . . . . 292 verifying circuit pack version . 474, 512, 545, 575, 608, 649, 699, 739, 796, 831, 868, 875
IPSI, (continued) verifying connectivity472, 510, 543, 573, 606, 647, 697, 737, 794, 829, 866, 1063, 1096, 1131 verifying health . . . . . . . . . . . . . . . . 291 verifying proper seating . . . . . . . . . . . . 1197 verifying translations471, 509, 542, 572, 605, 646, 696, 736, 793, 828, 865, 1063, 1096, 1131, 1200 IPSI cables connecting . . . . . . . . . . . . . . . . . . 665 IPSI circuit packs . . . . . . . . . . . . . 666, 716, 778 connecting CAT5 cables497, 535, 678, 722, 731, 785, 788 duplex reliability . . . . . . . . . . . . 667, 717, 779 high-critical reliability . . . . . . . . . 670, 720, 782 IPSI connectivity, verifying 472, 510, 543, 573, 606, 647, 697, 737, 794, 829, 866, 1063, 1096, 1131 IPSI translations adding for CSI in a CMC to S8500 461, 491, 530, 561, 592, 727 adding for CSI in a CMC to S8700-Series635, 686, 773, 817, 852
L
laptop connection to media server . . . . . . . . . 1237 license TN2602AP . . . . . . . . . . . . . . . . . . 1203 verifying on LSP . . . . . . . . . . . . . . . . 1176 license and authentication files copying . . . . . . . . . . . . . . . . . . . . 919 copying to media server 100, 101, 114, 131, 139, 168, 185, 214, 217, 243, 268, 274, 286, 1050, 1082, 1118 generating and retrieving. . . . . . . . 70, 313, 1040 installing on media server . . 176, 232, 343, 401, 432 license file installing new 364, 455, 462, 492, 556, 562, 586, 594, 637, 661, 755, 810, 819, 845, 855 installing new on S8400 332, 338, 368, 391, 395, 422, 425 RFA process . . . . . . . . . . . . . 70, 313, 1039 verifying 489, 528, 560, 590, 633, 684, 724, 765, 814, 849 license-server command . . . . . . . . . . . . . 1176 linear card reader, installing software . . . . . . . 322 link status, checking 352, 381, 410, 440, 474, 512, 545, 574, 607, 649, 699, 739, 796, 831, 868 Linux migration backing up system files . . . . . . . . . . 161, 179 backing up system files for S8500 to S8710 . . . 878 backing up the upgrade set to the network for S8700 to S8710 . . . . . . . . . . . . . . . 907 backing up the upgrade set to the services laptop for S8700 to S8710 . . . . . . . . . . 908 restoring system files . . . . . . . . . . . 173, 190 Linux Migration Backup Web page . . . . . . . . . 179 list configuration command . . . . . . . . . 1064, 1211 list fiber-link command . . . . . . . . . . . . . . 1066
Issue 2.1 June 2006
1255
Index
list synchronization command . . . . . . . . . . . 1054 local survivable processor, see LSP location assignment, administering . . . . 694, 734, 791 login obtaining password for . . . . . . . . 71, 313, 1040 LSP administering the gateway controller list . . . . 1180 administering the primary controller . . . . . . 1174 configuring the LSP . . . . . . . . . . . . . . 1172 configuring the modem . . . . . . . . . . . . 1174 converting to . . . . . . . . . . . . . . . . . 1157 converting to ICC . . . . . . . . . . . . . . . 1149 firewall settings . . . . . . . . . . . . . . . . 1179 installing or converting . . . . . . . . . . . . 1165 resetting . . . . . . . . . . . . . . . . . . . 1179 setting the date and time . . . . . . . . . . . 1171 start call processing . . . . . . . . . . 117, 197, 248 stopping call processing . . . . . . . . 97, 151, 209 upgrading 91, 92, 145, 146, 201, 202, 875, 901, 947, 1034 verifying the translations . . . . . . . . . . . 1179
M
magneto optical drive copying translations . . . . . . . 683, 723, 743, 765 maintenance circuit packs . . . . . . . . 666, 716, 778 installing in MCC . . . . . . . . . . . . . 494, 533 installing in SCC . . . . . . . . . . . 691, 731, 788 replacing . . . . . . . . . . . . . . . . . . . . 759 maintenance test circuit pack installing . . . . . . . . . . . . . . . . . . . 1211 Maintenance Web Interface starting . . . . . . . . . . . . . . . . . . 284, 1245 maintenance, sceduled disabling . . . . 100, 128, 153, 211, 261, 1051, 1119 Make Upgrade Permanent Web page . . . 112, 229, 241 manual backup server . . . . . . . . . . 89, 143, 200 master boot record erasing . . . . . . . . . . . . . . . . . . . . . 181 MBS, converting to ESS . . . . . . . . . . . . . 1147 media gateway turning on . . . . . . . . . 502, 536, 692, 732, 789 media processor administering . . . . . . . . . . . . . . . . . 1064 checking location . . . . . . . . . . . . . . . 1208 connecting cables . . . . . . . . . . . . . . 1060 disabling . . . . . . . . . . . . . . . . . . . 1209 installing . . . . . . . . . . . . . . . . . . . 1059 removing . . . . . . . . . . . . . . . . . . . 1209 media server command line interface . . . . . . . . . . . . 1246 media servers . . . . . . . . . . . . . . . . . . 1230 access remotely over modem . . . . . . . . . 1243 access remotely over network . . . . . . . . . 1243
media servers, (continued) busying out . . . . . . . . . . . . . . . . . . 177 configuring network parameters . . . . . . . . 186 configuring S8400 . . . . . . . . . . . 342, 372, 399 connecting Ethernet cables . . . . . . . . . . 665 connecting to 192, 219, 243, 267, 465, 565, 598, 630, 640, 822, 859, 1069, 1103, 1136, 1232 copying service packs . . . . . . . . . . . . . 267 direct connection . . . . . . . . . . . . . . . 1237 inserting the DAL1 circuit pack . . . . . . . . . 1227 interchanging servers . . . . . . . . . . . 175, 231 license and authentication files . . . . . . . 176, 232 making the upgrade permanent . . . . 112, 229, 241 mode conversions . . . . . . . . . . . . . . . 1147 opening the cover . . . . . . . . . . . . . . . 1226 registering . . . . . . . . . . . . . . . . . . 279 removing from rack . . . . . . . . . . . 1225, 1230 removing the cover . . . . . . . . . . . 1226, 1230 removing the riser assembly . . . . . . . . . . 1226 replacing the riser assembly . . . . . . . . . . 1228 selecting server type . . . . . . . . . . . . 169, 185 setting date and time . . . . . . . . . . . . . 174 starting . . . . . . . . . . . . . . . . . . . . 1167 starting Maintenance Web pages . 100, 129, 154, 157, 167, 184, 213, 217, 219, 233, 263, 265, 267, 459, 489, 528, 559, 590, 683, 724, 765, 814, 849, 904, 953, 989, 1049, 1081, 1117, 1186, 1206, 1232 turning off . . . . . . . . . . . . . . . . . . . 1224 turning on . . . . . . . . . . . . . . . . . . . 1231 upgrade documentation . . . . . . . . . . . . . 64 verifying date and time . . . . . . . . . . . . . 191 verifying network connection . . . . . . . . . . 188 verifying operation of . . . . . . . . . . . 193, 243 migrating DEFINITY CSI in a CMC to S8400 . . . . . 298, 319 DEFINITY CSI in a CMC to S8500 . . . 301, 445, 447 DEFINITY CSI in a CMC to S8700 Series . . . . 617 DEFINITY CSI in a CMC to S8700-Series . . 305, 614 DEFINITY ONE/S8100 in a CMC to S8400 . 298, 319 DEFINITY ONE/S8100 in a CMC to S8500 . 301, 445 DEFINITY ONE/S8100 in a CMC to S8700-Series . . . . . . . . . . . . . . 305, 614 DEFINITY ONE/S8100 to S8500 IP-Connect . . 547 DEFINITY ONE/S8100 to S8700 Series IP-PNC . 799 DEFINITY R in an MCC to S8700-Series . . . . 612 DEFINITY R in an MCC to S8700-Series fiber-PNC741 DEFINITY SI (Direct-Connect) in an MCC to a Direct-Connect. . . . . . . . . . . . . . . . 515 DEFINITY SI (Direct-Connect) in an SCC to a Direct-Connect. . . . . . . . . . . . . . . . 477 DEFINITY SI in an MCC to S8500 . . . . . 301, 445 DEFINITY SI in an MCC to S8700-Series . . 304, 612 DEFINITY SI in an MCC to S8700-Series (fiber-PNC) . . . . . . . . . . . . . . . . . 701 DEFINITY SI in an SCC to S8500 . . . . . 301, 445 DEFINITY SI in an SCC to S8700-Series . . 305, 613
Issue 2.1 June 2006
1256
Index
migrating, (continued) DEFINITY SI in an SCC to S8700-Series (fiber-PNC) . . . . . . . . . . . . . . . . . . 651 from existing DEFINITY and Linux platforms 318, 443 from existing DEFINITY and Linux platforms to S8400 . . . . . . . . . . . . . . . . . . . 318 from existing DEFINITY and Linux platforms to S8500 . . . . . . . . . . . . . . . . . . . 443 from existing DEFINITY and Linux platforms to S8700 Series . . . . . . . . . . . . . . . . 611 IP600 to S8700-Series IP-PNC . . . . . . . . . 833 IP600/S8100 in a G600 to S8400 . . . . . 299, 319 IP600/S8100 in a G600 to S8500 . . . . . 302, 446 IP600/S8100 in a G600 to S8700-Series . . 305, 614 IP600/S8100 to S8500 IP-Connect . . . . . . . . 577 pre-requisites to S8400 . . . . . . . . . . . . . 319 pre-requisites to S8500 . . . . . . . . . . . . . 446 pre-requisites to S8700 Series . . . . . . . . . . 614 S8100 to an S8400 using ftp . . . . . . . . . . 413 S8500 to S8710 . . . . . . . . . . . . . . . . 871 S8700 to S8710 . . . . . . . . . . . . . . . . 889 S8700 to S8720 . . . . . . . . . . . . . . . . 935 to an S8400 . . . . . . . . . . . . . . . . . . 317 to an S8500 . . . . . . . . . . . . . . . 317, 443 to an S8700 Series . . . . . . . . . . . . . . . 611 migration completing DEFINITY R to S8700-Series . . . . . 761 path, definition . . . . . . . . . .297, 317, 443, 611 paths to S8400 . . . . . . . . . . . . . . . . . 317 to S8400 . . . . . . . . . . . . . . . . . 317, 320 to S8500 . . . . . . . . . . . . . . . 300, 444, 446 to S8700-Series . . . . . . . . . . . 303, 612, 615 migration steps, basic DEFINITY CSI in a CMC to S8700-Series . . . . 617 DEFINITY CSI to S8400 using ATA flash . . . . . 355 DEFINITY CSI to S8400 using linear flash . . . . 321 DEFINITY CSI to S8400 using Xmodem . . . . . 383 DEFINITY CSI to S8500 . . . . . . . . . 447, 651 DEFINITY ONE/S8100 to S8700-Series IP-Connect . . . . . . . . . . . . . . . . . . 799 DEFINITY R to an S8700-Series (Multi-Connect) . 741 DEFINITY SI (Direct-Connect) in an SCC to IP-Connect . . . . . . . . . . . . . . . 477, 515 DEFINITY SI in an MCC to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . . . 701 IP600/S8100 to S8500 IP-Connect . . . . . 547, 577 IP600/S8100 to S8700-Series IP-Connect . . . . 833 S8100 to S8400 using ftp . . . . . . . . . . . . 413 S8500 to S8710 . . . . . . . . . . . . . . . . 871 S8700 to S8710 . . . . . . . . . . . . . . . . 889 S8700, S8710 to S8720 . . . . . . . . . . . . . 935 mixed fiber and IP connect configurations . . . . . . . . . . . . . 1080, 1116 mixed fiber-PNC and IP-PNC . . . . . . . . . . . 1042 MMI circuit packs busying out . . . . . . . . . 154, 212, 261, 906, 955 releasing . . . . . . . . . . . . . . . . . . . . 245
mode conversion . . . . . . . . . . . . . . . . . 1147 modem access to media server . . . . . . . . . . . . 1243 MOST tool copying translations . . . . . . . 683, 723, 743, 765
N
netcon data modules removing for S8400 . . . . . . . . . . 336, 366, 393 network parameters configuring . . . . . . . . . . . . . . . . . . 186 node name and IP addresses, recording337, 367, 395, 425, 458, 488, 527, 558, 589, 631, 664, 713, 764, 812, 847 node names adding TN2602AP node name . . . . . . . . . 1213
O
opening the cover . . . . . . . . . . . . . . . . 1230
P
password after installation . . . . . . . . . . . . 71, 313, 1040 ping ip-address command . . . . . . . . . . . . . 1217 Ping Web page . . . . . . . . . . . . . . . . . . 188 PNC converting from direct-connect to IP-PNC . . . . 1047 converting from simplex bearer to duplicated bearer . . . . . . . . . . . . . . . . . . . . 1201 enabling bearer duplication . . . . . . . . . . 1066 mixed fiber and IP connect configurations . . . . 1048 mixing fiber-PNC and IP-PNC . . . . . . . . . 1042 example . . . . . . . . . . . . . . . . . . 1108 removing fiber-related administration . . . . . . 1066 supported IP-PNC and fiber-PNC combinations . 1043 PNC fiber duplication disabling . . . . . . . . . . . . . . . . . . . 1066 port network converting to an MCC . . . . . . . . . . . . . 729 synchronization . . . . . . . . . . 1067, 1101, 1135 powering up, see starting PPN converting to an MCC . . . . . . . . . . . . . 729 installing expansion control . . . . . . . . 493, 532 installing expansion control and port carrier . 730, 787 installing expansion control media gateway . . . 690 removing control carriers . . . . . . . . . . 729, 786 removing SCC control cabinet . . . . . . . . . 689 Pre Upgrade step Web page . . . . . . . . . . . 220 premigration administration 333, 392, 423, 457, 557, 630, 812
Issue 2.1 June 2006
1257
Index
premigration setup downloading authentication file451, 481, 519, 551, 581, 621, 656, 705, 747, 803, 837 downloading license file 451, 481, 519, 551, 581, 621, 656, 705, 747, 803, 837 freezing translations451, 481, 519, 551, 581, 621, 656, 705, 747, 803, 837 preserving connections Preupgrade step . . . . . . . . . . . . . . . . 220 preserving connections during upgrade . . . . . . . 219 pre-upgrade service pack activating . . . . . . . . . . . . . . . 104, 222, 234 installing . . . . . . . . . . . . . . . 104, 222, 234 preupgrade service pack copying to media server 101, 131, 158, 168, 177, 185, 214, 217, 268, 286, 1050, 1082, 1118 list by R1 release . . . . . . . . . . . . . . . . 144 list by R2 release . . . . . . . . . 91, 122, 201, 255 Preupgrade step for preserving connections . . . . . 220 processor connecting to 335, 365, 392, 424, 457, 487, 526, 663, 762 connecting to IP600 . . . . . . . 557, 588, 812, 847 connecting to SI . . . . . . . . . . . . . . . . 712 processor ethernet setting the port . . . . . . . . . . . . . . 113, 138 processor port network in MCC converting to port network . . . . . . . . . . . . 729 processor port network, converting to a PN . . . . . 760
R
rack . . . . . . . . . . . . . . . . . . . . 1225, 1230 rebooting the media server, software upgrade110, 227, 239 recording IP settings . . . . . . . . . . . . . . . . 558, 589 IP settings for S8700-Series . . . . . . . . . . . 813 node names and IP addresses337, 367, 395, 425, 458, 488, 527, 558, 589, 631, 664, 713, 764, 812, 847 registering Communication Manager .118, 142, 198, 249 registering media server . . . . . . . . . . . . . . 279 release alarm suppression 117, 141, 195, 196, 247, 248, 1070, 1104, 1138 release board command . . . . . . . . . . . . . 1208 reliability levels in IP connect and fiber connect configurations . 1044 reliability, mixed reliability example . . . . . . . . 1074 remote access to media server over modem . . . . . . . . . . . . . . . . . 1243 over network . . . . . . . . . . . . . . . . . 1243 Remote Feature Activation going to the website. . . . . . . . . . . . . . . 335 starting . . . . . . . . . . . . . . . . . . . . . 333 Remote Maintenance Board. See RMB remove fiber-link command . . . . . . . . . . . . 1066
removing circuit packs IP600 to S8400 . . . . . . . . . . 428 circuit packs S8400 . . . . . . . . . . 339, 369, 397 control cabinet for DEFINITY SI (Direct-Connect) in an MCC to an IP-Connect . 531 control cabinet for DEFINITY SI (Direct-Connect) in an SCC to an IP-Connect . 493 media server . . . . . . . . . . . . . . 1225, 1230 netcon data modules S8400 . . . . . . 336, 366, 393 replacing TN2182 with a TN2312BP in CSI . . . . . . 463, 639 TN2182 with a TN2312BP in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 TN2402 with a TN2312BP for CSI in a CMC 463, 639 TN744 . . . . . . . . . . . . . . . . . . . . 820 TN795 . . . . . . . . . . . . . . . . 563, 594, 854 TN795 with a TN2312BP for CSI in a CMC . 463, 639 TN795 with a TN2312BP in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 TN795 with a TN2312BP in IP600/S8100 t o S8500 . . . . . . . . . . . . . . . . . 597, 858 TN799 . . . . . . . . . . . . . 563, 594, 820, 854 TN799C with a TN799DP340, 371, 398, 429, 464, 565, 598, 639, 821, 858 resolving alarms101, 116, 131, 140, 155, 194, 214, 246, 263, 276, 1051, 1069, 1083, 1104, 1119, 1137 restoring data for a migration for CSI on a CMC to S8710 . . . . . 633, 815, 850 for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . 771 for DEFINITY SI in an MCC to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . 725 for IP600/S8100 to S8710 . . . . . . . . . 684 Linux migration upgrade files from the services laptop for S8700 to S8710 . . . . . . . . . . 927 Linux migration upgrade set from the network for S8700 to S8710 . . . . . . . . . . . 918, 926 system files, with Linux migration . . . . . . . . 173 translations . . . . . . . . . . . . . . . . . . 685 translations for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . . 772 restoring system files, using Linux migration . . . . 190 restoring translations for CSI in a CMC to S8700-Series . . . 634, 815, 850 for DEFINITY SI in an MCC to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . . 725 RFA process . . . . . . . . . . . . . . . 70, 313, 1039 riser assembly of S8700-series Media Server. 1226, 1228 RMB configuring . . . . . . . . . . . . . . . . . . 1172 SAMP . . . . . . . . . . . . . . . . . . . . 1172
Issue 2.1 June 2006
1258
Index
S
S8300 converting from ICC to LSP mode . . . . . . . 1157 converting LSP to ICC mode . . . . . . . . . 1149 S8500 as LSP . . . . . . . . . . . . . . . . . . . . 1165 disconnecting cables . . . . . . . . . . . . . . 888 installing hardware . . . . . . . . . . . . . . 1167 upgrading from R2.x/R3.0 with Web pages . . . . 89 S8700-series Media Server configuring duplicated control . . . . . . . . . 1186 inserting the DAL1 circuit pack . . . . . . . . . 1227 interchanging servers . . . . . . . . . . . 175, 231 preserving connections during upgrade . . . . . 219 removing from rack . . . . . . . . . . . 1225, 1230 removing the riser assembly . . . . . . . . . . 1226 removing top cover . . . . . . . . . . . 1226, 1230 replacing the riser assembly . . . . . . . . . . 1228 upgrading from R1.x . . . . . . . . . . . . . . 143 upgrading from R2.x/3.0 using Web pages . . . . 199 SAMP boot timeout during upgrade . . . . . . . . . 94, 121 configuring the SAMP disabling the boot timeout . . . . . . . . . . . 1168 updating SAMP software . . . . . . . . . . . 1173 upgrading firmware . . . . . . . . . . . . . 97, 126 SAT session, starting126, 152, 877, 904, 954, 1049, 1081, 1117, 1199 saving translations . . . . 458, 488, 527, 558, 632, 664, 714 translations IP600 . . . . . . . 589, 813, 847, 848 translations with PCMCIA . . . . . . . . . . . . 368 translations with PCMCIA and Xmodem . . . . . 394 SCC1 Media Gateway removing ground plate and covers . . . . . . . 1191 scheduled maintenance disabling . . . . 100, 128, 153, 211, 261, 1051, 1119 Select server type Web page . . . . . . . . . 169, 185 Server date/time Web page . . . . . . . . . . . . . 174 service affected by upgrades . . . . . . . . . . . . 66 service pack activating . . . . . . . . . . . . . . . 104, 222, 234 copying to server . . . . . . . . . . . . . . . . 267 preupgrade . . . . . . . . . . . . 91, 122, 201, 255 verifying installation . . . . . . . . . . . . . . . 172 service pack, preupgrade . . . . . . . . . 144, 158, 222 copying to media server . . . . . . . . . . . . . 177 Set identities Web page . . 113, 138, 1171, 1186, 1187 Set server identities Web page . . . . . . . . . . 1234 set tone-clock command . . . . . . . . . . . . . 1058 setting alarm activation level on TN2312BP461, 491, 530, 562, 592, 637, 688, 728, 775, 818, 853 cabinet number . . . . . . . . . . . . 696, 736, 793
setting, (continued) control interface348, 376, 406, 436, 469, 506, 539, 569, 602, 644, 826, 863 switch id . . . . . . . . . . . . . . . 695, 735, 792 telnet parameters . . . . . . . . . . . . . . . 430 VLAN and diffserv parameters470, 508, 541, 571, 604, 645, 827, 864 Shutdown this server Web page . . . . . . . . . . 1224 SIPI activating firmware . . . . . . . . . . . . 289, 290 assigning IP addresses for CSI in a CMC345, 374, 403, 434 busying out . . . . . . . . . . . . . . . . . . 287 enabling control . . . . . . . . . 350, 379, 408, 438 firmware download . . . . . . . . . . . . . . 288 listing . . . . . . . . . . . . . . . . . . . . . 287 logging in to . . . . . . . . . . . 347, 376, 405, 435 resetting . . . . . . . . . . . . 349, 378, 407, 437 static addressing . . . . . . . . 346, 375, 403, 434 upgrading firmware . . . . . . . . . . . . . . 283 verifying circuit pack version . . . 353, 382, 411, 441 verifying connectivity . . . . . . 351, 380, 409, 439 verifying firmware version . . . . . . . . . . . 292 verifying health . . . . . . . . . . . . . . . . 291 verifying translations . . . . . . . 350, 379, 408, 438 SNMP configuring SNMP modules . . . . . . . . . . 1168 configuring SNMP subagent . . . . . . . . . . 1168 software installing on S8400 . . . . . . . 341, 372, 399, 430 software upgrade rebooting the media server . . . . . . . . . . . . 110 verify software operation after112, 137, 168, 175, 178, 185, 191, 229, 241, 274, 1050, 1082, 1118 verifying software operation after . . . . . . . . . 113 software version verifying . . . . . . . . . . . . . . . . . . . 1207 Software version Web page . . . . . . . . . 172, 1207 spanning tree enabling . . . . . . . . . . . . . . . . . . . 1185 setting version . . . . . . . . . . . . . . . . 1185 SREPN . . . . . . . . . . . . . . . . . . . . . 200 standby media server connecting to 157, 177, 196, 216, 221, 233, 247, 265, 278 starting media server . . . . . . . . . . . . . . . . . 1167 Remote Feature Activation . . . . . . . . . . . 333 SAT session126, 152, 877, 904, 954, 1049, 1081, 1117, 1199 static addressing for CSI in a CMC to S8700-Series, setting . . . 642 for DEFINITY R to S8700-Series (Multi-Connect), setting . . . . . . . . . . . . 791 for DEFINITY SI (Direct-Connect) in an SCC to an IP-Connect, setting . . . . . . . . . . . 504 SIPI . . . . . . . . . . . . . . 346, 375, 403, 434
Issue 2.1 June 2006
1259
Index
status media-processor command . . . . . . . . 1217 status synchronization command . . . . . . . . . 1055 Survivable Remote EPN . . . . . . . . . . . . . . 200 switch id setting . . . . . . . . . . . . . . . . 695, 735, 792 synchronization ATM . . . . . . . . . . . . . . . . . . . . . 1121 CSS . . . . . . . . . . . . . . . . . . . . . 1086 direct-connect . . . . . . . . . . . . . . . . 1053 PN . . . . . . . . . . . . . . . . 1067, 1101, 1135 synchronization of clock . . . . . 99, 127, 153, 211, 260 system files backing up 101, 116, 132, 141, 194, 214, 1051, 1084, 1120 system status verifying 175, 192, 229, 241, 274, 337, 367, 394, 424, 457, 487, 526, 631, 633, 663, 684, 713, 724, 765, 814, 849, 1235
T
telnet parameters setting . . . . . . . . . . . . . . . . . . 163, 430 terminal emulation . . . . . . . . . . . . . . . . 1246 test synchronization port-network command . . . . 1068 time and date setting . . . . . . . . . . . . . . . . . . . . 1171 verifying . . . . . . . . . . . . . . . . . . . . 191 time and date, setting . . . . . . . . . . . . . . . 174 TN2182 circuit pack replacing with a TN2312BP in CSI . . . . . 463, 639 replacing with a TN2312BP in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 replacing with IPSI . . . . . . . . . . . . . . 1058 TN2302 circuit pack checking location . . . . . . . . . . . . . . . 1208 connecting cables . . . . . . . . . . . . . . 1060 disabling . . . . . . . . . . . . . . . . . . . 1209 overflow for TN2602AP . . . . . . . . . . . . 1202 removing . . . . . . . . . . . . . . . . . . . 1209 TN2312BP circuit pack replacing a TN2182 in CSI . . . . . . . . 463, 639 replacing a TN2182 in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 replacing a TN2402 in CSI . . . . . . . . 463, 639 replacing a TN795 in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 replacing a TN795 in IP600/S8100 for S8500 . . . . . . . . . . . . . . . . 597, 858 replacing a TN798 in CSI . . . . . . . . . 463, 639 setting alarm activation level . 461, 491, 530, 562, 592, 637, 688, 728, 775, 818, 853 TN2402 circuit pack replacing with a TN2312BP in CSI . . . . . 463, 639
TN2602AP circuit pack adapter for cables . . . . . . . . . . . . . . . 1210 administering . . . . . . . . . . . . . . 1064, 1213 channel reduction . . . . . . . . . . . . . . . 1202 checking location . . . . . . . . . . . . . . . 1208 connecting cables . . . . . . . . . . . . 1060, 1210 disabling . . . . . . . . . . . . . . . . . . . 1209 duplicated bearer . . . . . . . . . . . . . . . 1201 I/O cables . . . . . . . . . . . . . . . . . . . 1205 inserting into media gateway . . . . . . . . . . 1211 installing . . . . . . . . . . . . . . . . . . . 1059 license . . . . . . . . . . . . . . . . . . . . 1203 overflow with TN2302 . . . . . . . . . . . . . 1202 testing external connection . . . . . . . . . . . 1217 verifying active call status . . . . . . . . . . . 1217 TN570 circuit packs removing . . . . . . . . . . . . . . . . . . . 1067 TN744 circuit pack replacing . . . . . . . . . . . . . . . . . . . 820 TN771 circuit pack installing . . . . . . . 464, 565, 598, 640, 821, 859 installing for S8400 . . . . . . . 341, 371, 398, 429 TN771DP circuit pack installing . . . . . . . . . . . . . . . . . . . 1211 TN795 circuit pack replacing . . . . . . . . . . . . . . . 563, 594, 854 replacing with a TN2312BP in DEFINITY ONE/S8100 to S8500 . . . . . 564, 820 replacing with a TN2312BP in IP600/S8100 to S8500 . . . . . . . . . . 597, 858 TN798 circuit pack replacing with a TN2312BP in CSI . . . . . 463, 639 TN799 circuit pack replacing . . . . . . . . . . . . 563, 594, 820, 854 TN799C circuit pack replacing with a TN799DP340, 371, 398, 429, 464, 565, 598, 639, 821, 858 TN799DP circuit pack connecting cables . . . . . . . . . . . . . . . 1060 installing . . . . . . . . . . . . . . . . . . . 1059 replacing a TN799C340, 371, 398, 429, 464, 565, 598, 639, 821, 858 TN8412 firmware upgrade . . . . . . . . . . . . 283 tone clock circuit packs replacing . . . . . . . . . . . . . . . . . . . 760 replacing with IPSI. . . . . . . . . . . 666, 716, 778 tone clock, setting . . . . . . . . . . . . . . . . 1058 translation corruption checking for . 100, 116, 128, 140, 154, 194, 212, 877, 906, 1083, 1119 translations backing up for DEFINITY SI in an MCC to S8700-Series (Multi-Connect). . . . . . . . . 728 backing up S8500 . . . . . . 461, 492, 531, 562, 592 backing up S8700-Series246, 637, 689, 776, 818, 853 copying files. . . . . . . . . . . . . . . . . . 459
Index
translations, (continued) copying files on CSI in a CMC to S8500489, 528, 560, 591 copying files to media server . . . . . 685, 725, 772 copying files to S8710 . . . . . . . . . 634, 815, 850 copying for S8400 . . . . . . . . . . . . . . . 344 copying for S8400 using Xmodem . . . . . 401, 402 copying to S8700 or S8710 . . . . . . 683, 723, 765 restoring . . . . . . . . . . 459, 490, 529, 560, 685 restoring for CSI in a CMC to S8700-Series 634, 815, 850 restoring for DEFINITY R to S8700-Series (Multi-Connect) . . . . . . . . . . . . . . . . 772 restoring for DEFINITY SI in an MCC to S8700-Series (Multi-Connect) . . . . . . . . . 725 saving . . . . . . 458, 488, 527, 558, 632, 664, 714 saving IP600 . . . . . . . . . . 589, 813, 847, 848 saving with PCMCIA . . . . . . . . . . . . . . 368 saving with PCMCIA and Xmodem . . . . . . . . 394 verifying IPSI 471, 509, 542, 572, 605, 646, 696, 736, 793, 828, 865, 1063, 1096, 1131, 1200 turning off cabinets . . . . . . . . . . . . . . . . . 339, 396 control cabinet . . . . . . . 369, 463, 564, 638, 820 control chassis . . . . . . . . . . . . . . 594, 855 S8100 cabinets . . . . . . . . . . . . . . . . . 427 S8500 . . . . . . . . . . . . . . . . . . . . . 887 turning on media gateway . . . . . . . 502, 536, 692, 732, 789 turning on, see starting
U
upgrade firmware Ethernet switch . . . . . . . . . . . . . . . . . 295 G150 Media Gateway . . . . . . . . . . . . . . 279 LSPs. . . . . . . . . . . . . . . . . . . . . . 253 upgrade sequence R2.1 to R2.x . . . . . . . . . . . . . . . 122, 256 upgrade software R2.1 to R3.0 . . . . . . . . . . . . . . . . . . 251 R2.x to R3.0 . . . . . . . . . . . . . . . . . . 251 using Upgrade Tool . . . . . . . . . . . . 121, 251 Upgrade Tool . . . . . . . . . . . . . . . . . . . 119 interchange during upgrade . . . . . . . . . . . 254 preserving connections during upgrade . . . . . 254 sequence of devices upgraded . . . . . . . . . 253 starting . . . . . . . . . . . . . . . . . . 136, 272 upgrading devices with Upgrade Tool . . . . . . 253 using. . . . . . . . . 120, 252, 875, 901, 947, 1034 upgrades service-affecting list . . . . . . . . . . . . . . . 66
upgrading ESSs . . . . . . . . . . . . . . . . . . . . . 201 existing hardware . . . . . . . . . . . 665, 714, 776 G150 Media Gateway firmware . 874, 900, 947, 1033 G350 Media Gateway firmware . 874, 900, 947, 1033 G700 Media Gateway firmware . 874, 900, 947, 1033 hardware in each PN . . . . . . . . . 666, 715, 777 LSPs . . . . . . . . . . . . . . . . . . . . . . 91 making the upgrade permanent . . . . 112, 229, 241 media servers documentation needed . . . . . . . . . . . . 64 reboot the media server . . . . . . . . . . . . 239 S8500 Media Server . . . . . . . . . . . . . . . 119 S8700-series with Upgrade Tool . . . . . . . . 253 SAMP firmware . . . . . . . . . . . . . . . 97, 126 software on LSP. . . . . . . . 875, 901, 947, 1034 TN2602AP firmware . . . . . . . . . . . . . . 1208 upgrading Communication Manager from R2.x to R3.0 . . . . . . . . . . . . . . . 199 on ESS . . . . . . . . . . . . . . 92, 93, 146, 202 on LSP . . . . . . . . . . . . . . . . 92, 146, 202 R1.X to R3.1 on S8700 . . . . . . . . . . . . 143 R2.1 to R3.1 . . . . . . . . . . . . . . . . . . 119 R2.x to R3.1 . . . . . . . . . . . . . . . . . . 119 R2.x to R3.1 on S8500. . . . . . . . . . . . . . 89 rebooting the media server . . . . . . . . . . . 227 using Upgrade Tool . . . . . . . . . . 119, 252, 253 upgrading firmware Ethernet switch . . . . . . . . . . . . . . . . 293 G150 Media Gateway . . . . . . . . . . . . . 142 G250 Media Gateway . . . . . . . . . . . . . . 91 G350 Media Gateway . . . . . . . . . 91, 145, 201 G700 Media Gateway . . . . . . . . . 91, 145, 201 H.248 media gateways . . . . . . . . . . 252, 253 h.248 media gateways . . . . . . . . . . . . . 201 IPSI . . . . . . . . . . . . . . . . . . . . . 283 LSPs . . . . . . . . . . . . . . . . . . . 121, 252 S8300 . . . . . . . . . . . . . . . . . . . . 121 SIPI . . . . . . . . . . . . . . . . . . . . . 283 using Upgrade Tool . . . . . . . . . . 121, 252, 253 upgrading LSPs . . . . . . . . . . . . . . . . . 145 upgrading software using Maintenance Web Interface . . . . . . . . 89 using the Maintenance Web Interface . . . . . . 199 UPS duplicated. . . . . . . . . . . . . . . . . . . 1203
V
VLAN and diffserv parameters, setting470, 508, 541, 571, 604, 645, 827, 864 VLAN parameters for the IPSI . . . . . . . . . . . 1198
Issue 2.1 June 2006
1261
Index
W
Web pages Activate IPSI Upgrade . . . . Authentication File . . . . . . Configure Individual Services . Configure Interfaces . . . . . Configure LSP or ESS . . . . Configure Server . . . . . . . Configure server . . . . . . . Copy settings . . . . . . . . . Download Files . . . . . . . . Download IPSI Firmware . . . Firewall . . . . . . . . . . . IPSI Version . . . . . . . . . Linux Migration Backup . . . . Make Upgrade Permanent . . Ping . . . . . . . . . . . . . Pre Upgrade step . . . . . . . Select server type . . . . . . Server date/time . . . . . . . Set identities . . . . . . 113, Set server identities . . . . . . Shutdown this server . . . . . Software version . . . . . . . Web pages, starting . . . . . . .
1186 1171 1172 1234 . 186 1186 158, 177, 267 . . . . . 289 . . . . 1185 . . . . . 292 . . . . . 179 112, 229, 241 . . . . . 188 . . . . . 220 . . 169, 185 174, 191, 1171 138, 1171, 1186, 1187 . . . . . . . . 1234 . . . . . . . . 1224 . . . . . . 172, 1207 . . . . . . . . 1245
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. 290 . 273

Upgrading, Migrating, and Converting Media Servers and Gateways

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Upgrading, Migrating, and Converting Media Servers and Gateways

Enviado por

Direitos autorais:

Formatos disponíveis

Upgrading, Migrating, and Converting Media Servers and Gateways

03-300412 Issue 2.1 June 2006

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

Upgrading Communication Manager from 1.x to 3.1 on an S8300 Media Server . . . . . . . . . . . . . . . . . . . . . . .

Upgrading Communication Manager from 2.x to 3.1 on an S8300 Media Server . . . . . . . . . . . . . . . . . . . . . . .

Issue 2.1 June 2006

4 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

Postrequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the G150 Media Gateways, if used . . . . . . . . . . . . . . . .

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preupgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Upgrading, Migrating, and Converting Media Servers and Gateways

151 151 152 152 153 153 153

Issue 2.1 June 2006

8 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

10 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

248 249 249

12 Upgrading, Migrating, and Converting Media Servers and Gateways

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

Issue 2.1 June 2006

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

Common prerequisites to all migrations . . . . . . . . . . . . . . . . . . . . .

14 Upgrading, Migrating, and Converting Media Servers and Gateways

313 313 313 314 315

Chapter 4: Migrating to an Avaya S8400 Media Server . . . . . . . . .

Migrating from existing DEFINITY and Linux platforms. . . . . . . . . . . . .

Issue 2.1 June 2006

16 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

18 Upgrading, Migrating, and Converting Media Servers and Gateways

410 410 411 411 411 412 412

Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting telnet parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Issue 2.1 June 2006

Chapter 5: Migrating to an Avaya S8500 Media Server . . . . . . . . .

Migrating a DEFINITY Server CSI in a CMC to an S8500 Media Server 447

20 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

473 474 474 475 475 475 475

Migrating a DEFINITY Server SI Direct-Connect in an SCC to a Direct-Connect . . . . . . . . . . . . . . . . . . . . . . .

22 Upgrading, Migrating, and Converting Media Servers and Gateways

Migrating a DEFINITY Server SI Direct-Connect in an MCC to a Direct-Connect . . . . . . . . . . . . . . . . . . . . . . .

Issue 2.1 June 2006

Migrating a DEFINITY ONE/S8100 to an S8500 Media Server . . . .

24 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

575 575 576 576

Migrating an Avaya IP600/S8100 to an S8500 Media Server . . . . .

26 Upgrading, Migrating, and Converting Media Servers and Gateways

Chapter 6: Migrating to an Avaya S8700-Series Media Server . . . . .

Prerequisites for migrating to an S8700-Series Media Server . . . . . . . . . Migration modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Issue 2.1 June 2006

28 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

Changing port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . .

Migrating a DEFINITY Server SI in an MCC to an S8700-Series Media Server with Fiber-PNC . . . . . . . . . . . . .

30 Upgrading, Migrating, and Converting Media Servers and Gateways

Issue 2.1 June 2006

738 738 739 739 740 740 740 740 740

Changing port networks to IP-PNC . . . . . . . . . . . . . . . . . . . . . . . .

Migrating a DEFINITY Server R to an S8700-Series Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Migrating translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the media server maintenance web interface. . . . . . . . . . .