|
|
This appendix describes how to upgrade the LocalDirector software. Topics include:
 |
Caution Before upgrading to a new version of software or changing your network configuration, you should always make a backup copy of your configuration file by saving it to diskette with the write floppy command, or to a TFTP server. Although LocalDirector loads the existing configuration file from Flash memory when rebooting, keeping a backup copy is always recommended. |
If you purchased a SMARTnet agreement for LocalDirector, you can register on Cisco.com and download software upgrades for LocalDirector. The steps to upgrade LocalDirector using software obtained from Cisco.com are:
Follow this procedure to obtain a copy of LocalDirector software from Cisco.com:
Step 2 Click the link Software Center in the Service & Support section.
Step 3 Click the link Internet Software.
Step 4 Click the link Web Software.
Step 5 Click the link Cisco LocalDirector, under Internet Software Products.
Step 6 Click the link Download LocalDirector Software. A Web page with content similar to the following appears:
Select a File to Download
Filename Description Release Size 'Bytes' More Info
3_1lui_pdf.zip LUI 3.1 Docs 3.1 688911 ?
3_1pdfs.tar LocalDirector Manual 3.x 1802240 ?
3_1pdfs.zip LocalDirector Manual 3.x 1581829 ?
cvs32_fcs_nt40sp4.exe LocalDirector binary CVS_3.2.1 31779908 ?
This Web page contains all versions of LocalDirector software and the accompanying release notes. Descriptions of each download file, its release number, and file size (in bytes) are listed. You will also see a link under the column More Info (click the ?) with more information about the download file.
Table B-1 describes the types of files you can download. The xxx in the filename refers to the software release version.
ldxxx.exe | A self-extracting file for MS-DOS or Windows that includes the binary, readme, and rawrite files. |
ldxxx.bin | A binary file for LocalDirector software. |
ldxxx.txt | A readme file that includes directions for creating a LocalDirector bootable diskette. |
rawrite.exe | A utility for MS-DOS that is used to write the ldxxx.bin file for LocalDirector to diskette. |
Step 7 Click the filename link that you want to download. A web page containing instructions for downloading using FTP and HTTP appears.
Step 8 Click a link to choose a Cisco Cisco.com server containing the download source.
Step 9 Provide your Cisco.com password, if requested.
Step 10 Choose a location on your computer to save the download file.
Step 11 Continue with the instructions in "Creating a Boot Diskette."
To create a bootable LocalDirector diskette, use one of the following procedures, based on the operating system of your computer.
To create a bootable LocalDirector diskette if your computer is running the UNIX operating system, perform the following steps:
Step 2 Change to the directory where you saved the ldxxx.bin file.
Step 3 Insert a diskette into the workstation drive, and use the following command:
dd bs=18b if=./ldxxx.bin of=/dev/rfd0
Step 4 Follow the upgrade procedure that is appropriate for your type of LocalDirector configuration (see the section "Performing the Upgrade").
To create a bootable LocalDirector diskette if your computer is a PC, perform the following steps:
Step 2 Double-click ldxxx.exe to extract its contents.
Step 3 Use the rawrite command at a DOS command prompt. When prompted, enter ldxxx.bin as the filename, and your diskette drive as the destination drive. You will see prompts similar to the following:
C:\LDSoftware>rawrite
RaWrite 1.2 - Write disk file to raw floppy diskette
Enter source file name: ldxxx.bin
Enter destination drive: a:
Please insert a formatted diskette into drive A: and press -ENTER-:
Number of sectors per track for this disk is 18
Writing image to drive A:. Press ^C to abort.
Track: 22 Head: 1 Sector: 16
Done.
 |
Note The diskette you insert into drive A does not need to be formatted. Any data that already exists on the diskette will be completely overwritten when using the rawrite command. |
Step 4 Follow the upgrade procedure that is appropriate for your type of LocalDirector configuration (see the section "Performing the Upgrade").
This section contains the upgrade instructions for the following types of LocalDirector configurations:
|
Caution During the LocalDirector upgrade, all existing network connections will be lost. We recommend that you perform the upgrade procedure when the fewest users are affected. |
To upgrade a standalone LocalDirector, perform the following steps:
Step 2 Insert the floppy disk with the upgrade software in LocalDirector (see the section "Creating a Boot Diskette" if you do not have your boot diskette).
Step 3 Reboot LocalDirector or use the reload command.
As part of the boot sequence, LocalDirector compares the version of software on the diskette against the version residing in Flash RAM. If the version on the diskette is newer, it is copied to Flash RAM, overwriting the older version. The reboot process can take from 1 to 2 minutes.
After the reboot is complete, remove the floppy and store it in a safe place.
The new software version starts up, using your existing network configuration.
Step 4 Use the write mem command to update the version number in the configuration file.
Step 5 Check that your network configuration is running normally. Use the show interface command and ping the real servers.
|
Caution Unless your LocalDirector configuration uses stateful failover, all existing connections will be lost during the LocalDirector upgrade. If your site does not use stateful failover, we recommend that you perform the upgrade procedure when the fewest users are affected. To configure stateful failover, refer to the chapter that discusses stateful failover in the LocalDirector hardware installation guide that is shipped with your system. |
To upgrade LocalDirector configured for failover, perform the following steps:
Step 2 On the primary (active) LocalDirector, use the following commands to configure the syslog facility:
LocalDirector(config)primary# syslog output 20.7
LocalDirector(config)primary# syslog console
Step 3 On the secondary (standby) LocalDirector, insert the floppy disk with the upgrade software (see the section "Creating a Boot Diskette" if you do not have your boot diskette).
Step 4 Reboot the secondary LocalDirector or use the reload command.
As part of the boot sequence, LocalDirector compares the version of software on the diskette against the version residing in Flash RAM. If the version on the diskette is newer, it is copied to Flash RAM, overwriting the older version. The reboot process can take from 1 to 2 minutes.
Step 5 After the secondary LocalDirector successfully reboots, the primary LocalDirector automatically copies the network configuration to it.
|
Caution To ensure a successful upgrade, do not interrupt the configuration copy process. Be sure the copy is complete before proceeding with the upgrade procedure. |
Step 6 Check the progress of the copy process by viewing the syslog messages on the primary LocalDirector.
Messages similar to the following appear for a nonstateful failover configuration:
LocalDirector(config)primary# <162> Primary: Power failure other side.
<162> Primary: Cable OK.
<162> Primary: Monitoring on interface 3 waiting
<162> Primary: Monitoring on interface 0 waiting
<162> Primary: Begin Configuration Replication: Sending to mate
<162> Primary: End Configuration Replication
Messages similar to the following appear after the above messages when stateful failover is configured:
<165> Begin Stateful Connection Replication: Sending to mate
<162> Primary: Monitoring on interface 3 normal
<162> Primary: Monitoring on interface 0 normal
<165> End Stateful Connection Replication
Step 7 From the primary LocalDirector, use the show failover command to verify that the failover status
is normal.
Step 8 From the secondary LocalDirector, use the failover active command to make the secondary LocalDirector the active LocalDirector.
With the secondary LocalDirector active, you can upgrade the primary LocalDirector, which is now in standby mode.
Step 9 From the primary LocalDirector, insert the floppy disk with the upgrade software.
Step 10 Reboot the primary LocalDirector or use the reload command.
As part of the boot sequence, LocalDirector compares the version of software on the diskette against the version residing in Flash RAM. If the version on the diskette is newer, it is copied to Flash RAM, overwriting the older version. The reboot process can take from 1 to 2 minutes.
Step 11 After the primary LocalDirector successfully reboots, the active secondary LocalDirector automatically copies the network configuration to the standby primary LocalDirector.
|
Caution To ensure a successful upgrade, do not interrupt the configuration copy process. Be sure the copy is complete before proceeding with the upgrade procedure. |
Step 12 Check the progress of the copy process by viewing the syslog messages on the active LocalDirector.
Step 13 From the primary LocalDirector, use the show failover command to verify that the failover is operating normally and ping the real servers to test connectivity.
Step 14 On the primary LocalDirector, use the following commands to reset the syslog facility:
LocalDirector(config)primary# syslog output 20.3
LocalDirector(config)primary# no syslog console
Step 15 After the upgrade is complete, remove the upgrade floppy diskette and store it in a safe place.
To upgrade software using a boot image contained on a TFTP servers, see the tftp-server command reference page in "Command Reference,"to obtain your upgraded boot image.
Follow the procedure in the "Performing the Upgrade" section, but use the TFTP boot image instead of the image on the floppy diskette.
Posted: Wed Jan 3 13:25:59 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.