Configuration Notes

This appendix provides additional details for some of the configuration processes referenced in this installation guide. The appendix contains the following sections:

Password protection on two levels can be implemented to restrict access to the web-based GUI interface. "USER1" is allowed both read and write access. "USER2" is allowed only read access. When the web interface is accessed for the first time, a dialog box appears requesting a user name and password.

Definition of this password protection and changing user names and passwords are accomplished using the connect.exe program to register, change, or delete users and passwords. By default, no user is registered to the system.

To implement this feature, follow these steps.

Step 1 Initiate connect.exe.

Step 2 From the Main menu, select C: Environmental Parameters and FLASH Partitions.

Step 3 Select B: Environment Configuration.

Step 4 Select C: Add Environment Parameter.

Step 5 Add the following lines:

USER1=username1

PWD1=password1

USER2=username2

PWD2=password2

Step 6 Press ESCAPE until you return to main menu, then enter "q" to quit the program.

Note If a password is not defined, no password is required. If USER2 is not defined, all users are allowed to view the contents of the web interface. If USER1 is not defined, all users are allowed to change configurations.

Using Bootp and TFTP

The Cisco 6920 can acquire its IP address, network mask, gateway address, and SNMP manager IP addresses through a Bootp server. It can also be booted dynamically from a TFTP server on the network.

To implement this feature, follow these steps.

Step 1 Install a copy of the TFTP and Bootp/DHCP server on the host.

Step 2 Configure the TFTP server to point to the \tftp directory and configure the Bootp/DHCP server to add a static entry for each Cisco 6920 system to be booted.

Note Make sure that the network mask and gateway are properly specified.

Step 3 Copy the entire directory of the desired software release (Release 2.4 or later) to the \tftp directory.

Step 4 Use a text editor to create the file C:\tftp\bootp.ini with one of the following lines:

SWRelease=010112 2.3.2/240;!

SWRelease= 010112 2.3.2/240;

SWRelease=*/;

The format is yymmdd rr/bbb:! where yymmdd is the date when the release was created, rrr is the release number, and bbb is the build number. The build number can be found in any *.fls file under the release subdirectory.

The "!" at the end of a line forces the Cisco 6920 software to load the new bootloader and software. If the "!" is missing from the end of the line, the Cisco 6920 checks the software located in Flash memory. If it is the same software specified in the bootp.ini file, no software is loaded.

If you want to load specifically the software located in Flash memory, use the SWRelease=*/; line in the bootp.ini file.

Configure up to three SNMP manager IP addresses in the bootfile by adding the following line:
SnmpMgr=IPaddress,IPaddress,IPaddress;

Step 5 Use the connect.exe program to add the environment variable USEBOOT=TRUE.

Note If your current bootloader is not Release 2.4 or later, download a new bootloader before proceeding.

Step 6 Reset the Cisco 6920 and observe the output from the Bootp/DHCP and TFTP servers, and the HyperTerminal. Confirm the following events:

1. The Bootp/DHCP server received a request from the Cisco 6920.

2. The TFTP server indicates the transfer of the bootp.ini file to the Cisco 6920.

3. The HyperTerminal prints the Ethernet address and IP address of the Cisco 6920.

4. The TFTP server indicates the transfer of the binstallxxx.fls file to the Cisco 6920.

5. The HyperTerminal indicates that the Cisco 6920 is resetting.

6. The TFTP server and HyperTerminal indicate the transfer of the software for the PowerPC, DSP, and I/O cards to the Cisco 6920.

7. The HyperTerminal indicates:

: "INFO: Application verified"
: "INFO: Ver: xxx"

Note Actions 4, 5, and 6 occur depending on the contents of the bootp.ini file.

Table of Contents