When the reboot is complete, click Continue

The system displays the Update Tripwire Database Web page. If your planning documents instruct you to enable Tripwire, follow the instructions to reset the signature database.

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

5. Click Continue.

The system displays the Install License Files Web page.

6. Click Continue.

The system installs the license file and authentication file if you selected this action in step 5 on Installing Communication Manager on the serveron page 122.

The system displays the Installation Complete screen.

7. Click Close.

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

Note:

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

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

8. Close the Web browser.

9. Reopen the Web browser and log in.

Verifying reboot 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 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.

Verifying software operation

To verify the software version.

1. Under Server, click Software Version.

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

Checking system 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 server

! _CAUTION:

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

the server, the server might come up running the previous version of software.

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

To make the upgrade permanent.

1. Under Server Upgrades, click Make Upgrade Permanent.

2. Click Submit to make the partition with the new software version the permanent partition.

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

Installing security and Communication Manager service pack updates, if any

1. Under Server Upgrades, select Manage Updates.

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

The window shows the status of the update.

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

The system displays the Manage Updates screen.

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

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

5. Click Yes.

Wait until the system displays the Continue button.

6. Click Continue.

Accessing the server command line interface with ssh protocol

Note:

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

Manager Release 3.0 and later.

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

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

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

Note:

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

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

! _CAUTION:

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

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

To access the command line interface using PuTTY with ssh:

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

PuTTY.

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

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