Wait until the system displays the message Unpacked Successfully.. and then click Continue

The system displays the Manage Updates screen.

4. If the update ID you want to activate shows unpacked in the Status column:

a. Select the update ID b. Click Activate

The screen shows the status of activating the update. If a reboot or restart of Communication Manager is required, the system automatically reboots or restarts Communication Manager.

5. Click Yes.

Wait until the system displays the Continue button.

6. Click Continue.

The system displays the status of the update.

Configuring the Processor Ethernet interface (on the ESS)

Perform this task if you are upgrading the server from Communication Manager Release 5.1.x or prior to Communication Manager 5.2 or later.

1. Under Installation, click Configure Server and follow the instructions on the wizard.

Alternatively, you can configure services individually. For more information, see the online help available with the SMI.

2. On the Set Identities page, verify that PE is assigned to the same NIC as the corporate LAN.

3. On the Configure Interfaces page, assign an IP-alias address for the PE interface of the duplex ESS. PE must be assigned to the same NIC as the corporate LAN. The IP-alias address is assigned in the Active server field.

4. Submit the change and exit from the Configure Server wizard.

Accessing the server command line interface with ssh protocol

Note:

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

Manager Release 3.0 and later.

your laptop for the network connection. In addition, a third-party ssh client must already be installed on your computer.

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

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

Note:

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

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

! _CAUTION:

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

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

To access the command line interface using PuTTY with ssh:

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

PuTTY.

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

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

4. Under Protocol, select SSH.

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

The Options controlling SSH connections dialog box opens.

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

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

Note:

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

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

docs.html.

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

The Options controlling the effects of keys dialog box opens.

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

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

10. Click Open.

Note:

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

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

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

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

12. Log in to the server.

XL configuration considerations

Note:

Note: If you are upgrading an S8720XL main server, proceed to Configuring the main

server for S8720 in XL configurationon page 175.

If you are upgrading an S8720 main server, proceed to Performing an integrity check on the second S8700-Series Serveron page 200.

If you are upgrading an S8720 ESS server, proceed to Configuring the ESS server for compatibility with XL configurationon page 198.

If you are upgrading an S8710 Server, proceed to Performing an integrity check on the second S8700-Series Serveron page 200.

Configuring the main server for S8720 in XL configuration

This section applies only to a main server configured for an XL. If you are not enabling the server as an XL configuration, skip this section and proceed to Performing an integrity check on the first S8700-Series Serveron page 172.

Note: If the main servers are configured as an XL configuration, ESSs and LSPs also must be configured to be compatible with the main server.

To configure the main server as an XL configuration:

1. At the server command line interface, type stop -acfn and press Enter to stop Communication Manager call processing.

2. On the Maintenance Web page, under Server Configuration, click Configure Server.

3. Click Continue until you get to the Specify how you want to use this wizard screen.

! _CAUTION:

CAUTION: For the next step, if you select and save as Extra Large you cannot revert to

Standard. If you try to go back to Standard, server translation corruption occurs.

4. Select Configure individual services and click Continue.

5. In the left column, click:

● Configure Memory (if a main server)

● Configure ESS (if an ESS server)

6. Select Extra Large and click Change.

7. Click Close Window.

8. At the server command line interface, type start -ac and press Enter to restart Communication Manager call processing.

9. At the server command line interface, type swversion and press Enter.

In the Memory Config field, verify that the setting is Extra Large.

Configuring the ESS server for compatibility with XL configuration

This section applies only to an ESS server where the main server is configured as an XL. If the main server is not configured as XL, skip this section and proceed to Performing an integrity check on the first S8700-Series Serveron page 172.

Note:

Note: If the main servers are configured as XL, the ESS servers and LSPs also must be

configured to be compatible with the XL configuration. An S8720 Server can be configured as standard or XL. An S8730 Server is always configured as XL.

To configure the ESS server for compatibility with the main server’s XL configuration:

1. At the server command line interface, type stop -acfn and press Enter to stop Communication Manager call processing.

2. On the Maintenance Web page, under Server Configuration, click Configure Server.

The system displays the Review Notices screen.

3. Click Continue until you get to the Specify how you want to use this wizard screen.

CAUTION: For the next step, if you select and save as Extra Large you cannot revert to Standard. If you try to go back to Standard, server translation corruption occurs.

4. Select Configure individual services and click Continue.

5. In the left column, click Configure ESS (if an ESS server)

6. Select Extra Large and click Change.

7. Click Close Window.

8. At the server command line interface, type start -ac and press Enter to restart Communication Manager call processing.

9. At the server command line interface, type swversion and press Enter.

In the Memory Config field, verify that the setting is Extra Large.

Performing an integrity check on the second S8700-Series Server

To perform an integrity check on the second (standby) S8700-Series Server:

1. On the System Management Interface (formerly known as Maintenance Web Interface), under Administration > Server (Maintenance) > Server, click Process Status.

2. Under Frequency, click Display Once and click View.

3. Verify all operations are Up.