cc/td/doc/product/l3sw/4840g/ios_12/120_10
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring the SLB Processor

Configuring the SLB Processor

This chapter describes how to configure the Server Load Balancing (SLB) switch processor so it can be accessed by other devices. For further information about the commands used in this chapter, refer to the command reference publications in the Cisco IOS documentation set and to "Command Reference."

This chapter includes the following sections:


Note   You are at Step 2 in the suggested process for configuring your SLB switch. See the "Configuring Your SLB Switch" section. By now you have set up the hardware and are ready to proceed with configuring the SLB processor.

Starting Up the SLB Switch

Before starting up the SLB switch, you should verify the following:

  For instructions, refer to the Catalyst 4840G Chassis Installation Guide.

When you start up the SLB switch, the CLI prompts you whether to enter the initial configuration dialog. Answer no to this prompt:

Would you like to enter the initial dialog? [yes]: no

 

You see the following user EXEC prompt:

SLB-Switch> 
 

You can now begin configuring the SLB switch.

Using the Console Port or a Management Port

You can configure the SLB switch from a direct console connection to the console port or remotely through its management port.

  For interface configuration instructions, see the "Configuring the Management Port" section.

For further details on configuring ports and lines for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide .

Modem Support

You can connect a modem to the console port on the Catalyst 4840G SLB switch. The following settings on the modem are required:

You can configure your modem by setting the DIP switches on the modem or by connecting the modem to terminal equipment. Refer to the user manual provided with your modem for the correct configuration information.


Note   Because there are no hardware flow control signals available on the console port, the console port terminal characteristics should match the modem settings.

For further details on configuring ports and modems for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Dial Solutions Configuration Guide .

Using Passwords

You can configure both an enable password and an enable secret password. For maximum security, the enable password should be different from the enable secret password.

The Enable Password

The enable password is a nonencrypted password. It can contain any number of uppercase and lowercase alphanumeric characters. Give the enable password only to users permitted to make configuration changes to the SLB switch.

The Enable Secret Password

The enable secret password is a secure, encrypted password. By setting an encrypted password, you can prevent unauthorized configuration changes. On systems running Cisco IOS software, you must type in the enable secret password before you can access global configuration mode.You must type in the enable secret password to access boot ROM software.

An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters. The first character cannot be a number. Spaces are valid password characters. Leading spaces are ignored; trailing spaces are recognized.

You will configure passwords in the "Configuring the Management Port" section.

Configuring the Management Port

Command Purpose

Step 1 

SLB-Switch> enable 

SLB-Switch#

Enters privileged EXEC configuration mode. You can also abbreviate the command to ena.

The SLB-Switch# prompt indicates that you are in privileged EXEC configuration mode.

Step 2 

SLB-Switch# configure 
terminal

SLB-Switch(config)#

Enters global configuration mode. You can also abbreviate the command to config t.

The SLB-Switch(config)# prompt indicates that you are in global configuration mode.

Step 3 

SLB-Switch# enable 
password password

Sets the enable password.

See the "Using Passwords" section.

Step 4 

SLB-Switch(config)# 
enable secret password

Enters an enable secret password. Once set, a user must enter the enable secret password to gain access to global configuration mode.

Step 5 

SLB-Switch(config)# 
interface [fastethernet 
1-40 | gigabitethernet 41-42]

 
SLB-Switch(config-if)#

Enters interface configuration mode on the interface.

Step 6 

SLB-Switch(config-if)# ip 
address ip-address 
subnetmask

Enters the IP address and IP subnet mask for the interface.

Step 7 

SLB-Switch(config-if)# no 
shutdown

Enables the interface.

Step 8 

SLB-Switch(config-if)# 
exit

SLB-Switch(config)#

Returns to global configuration mode.

Step 9 

SLB-Switch(config)# line 
vty line-number

SLB-Switch(config-line)<ET
>#

Enters line configuration mode for virtual terminal connections. Commands entered in this mode control the operation of Telnet sessions to the Catalyst 4840G SLB switch.

Step 10 

SLB-Switch(config-line)<E
T># password password

Enters a password for Telnet sessions.

Step 11 

SLB-Switch(config-line)<E
T># end

SLB-Switch#

Returns to privileged EXEC mode.

Step 12 

SLB-Switch# copy 
running-config startup-config

Saves your configuration changes to NVRAM.


Note   Any Fast Ethernet interface, fastethernet 1 through 40 and any Gigabit Ethernet interface, gigabitethernet 41 or 42, on the Catalyst 4840G SLB switch can be configured as a management port. Once you have configured an interface as a management port, you cannot route or bridge traffic to the other Ethernet ports on the SLB switch from this management port.

The Catalyst 4840G SLB switch should now be operating correctly. You can now use Telnet to remotely assign and verify configurations.

Displaying the Operating Configuration

You can display the configuration file when you are in privileged EXEC (enable) mode.

    SLB-Switch# more system:running-config
     
    
    SLB-Switch# more nvram:startup-config
     
    

If you made changes to the configuration, but did not yet write the changes to NVRAM, the contents of the running-config file will differ from the contents of the startup-config file.

Configuring the Host Name

In addition to the system passwords and enable password, your initial configuration should include the host name to make it easier to configure and troubleshoot the SLB switch. To configure the host name, perform these steps:

Command Purpose

Step 1 

SLB-Switch# configure terminal

SLB-Switch(config)#

Enters global configuration mode.

Step 2 

SLB-Switch(config)# hostname name

Specifies a system name.

Step 3 

SLB-Switch(config)# end				

SLB-Switch#

Returns to privileged EXEC mode.

Step 4 

SLB-Switch# copy system:running-config 
nvram:startup-config

Saves your configuration changes to NVRAM.

Using Flash PC Cards

This section describes how to use a Flash PC Card to copy system images and make standard configurations. A Flash PC Card is not required for the operation of the SLB switch.


Note   A Flash PC Card must be ordered as a spare part. It is recommended that you use a 20 MB Flash PC Card to download and store a copy of the SLB switch software image. Doing so allows you to store two or more images at the same time.

Flash PC Cards store a copy of the software image. The following sections describe how to format, delete, configure, and copy files between the onboard Flash memory Single In-Line Memory Module (SIMM), network servers, and Flash PC Card.

Formatting a Flash PC Card

A Flash PC Card is blank and must be formatted before use. The formatting procedure erases all information on the Flash PC Card.

Following is the general procedure for formatting a Flash PC Card:


Step 1   Backup files that you have on an existing Flash PC Card by copying them to a TFTP server using the copy flash tftp: command.

Step 2   Insert the Flash PC Card you want to format into slot 0.

Step 3   Format the Flash PC Card using the format command.


The following example demonstrates formatting a Flash PC Card in slot 0 and naming it "NewPCcard":

SLB-Switch# format slot0:

Format operation may take a while. Continue? [confirm] y

Enter volume ID (up to 30 characters): NewPCcard

Formatting sector 1
Format device slot0 completed
 

This example uses a 16-MB Flash PC Card. At the line Formatting sector 1, the system counts the card's sectors backward from 128 to 1 as it formats them. For 20-MB Flash PC Cards, the system counts backward from 160 to 1.


Note   For more information on inserting a Flash PC Card, refer to the Catalyst 4840G Chassis Installation Guide.

Copying the Startup Configuration File to the Flash PC Card

Use the following command to copy the startup configuration file from NVRAM to a Flash PC Card once the Flash PC Card is formatted and ready to use:

Command
Purpose
SLB-Switch# copy nvram:startup-config 
flash-device

Copies the file startup-config to the Flash PC Card in the specified location.

The following example demonstrates copying the startup configuration file to the Flash PC Card in slot 0; the default filename is used:

SLB-Switch# copy nvram:startup-config slot0:
Destination filename [startup-config]? y
3790 bytes copied in 0.484 secs

SLB-Switch#    

Viewing the Contents of Flash Memory

This section describes commands you can use with the onboard Flash memory SIMM (bootflash) and Flash PC Cards.

Determining the Current File System Device

To determine which file system device you are accessing, use the pwd (print working directory) command, as shown in the following example:

SLB-Switch# pwd

bootflash

Moving Between Flash Memory Media

To move between Flash memory media, use the cd command, as shown in the following example:

SLB-Switch# cd slot0:

SLB-Switch# pwd

slot0
SLB-Switch#

Listing the Flash Memory Directory Contents

To list the directory contents of any Flash memory media, use the dir command, as shown in the following example:

SLB-Switch# dir

Directory of slot0:/
 
1   -rw-   3509000	   Jan 25 1999   19:46:25    cat4840G-in-mz.120-1.W5.6a.bin
3   -rw- 	  3509004   Feb 5 1999    19:46:25    cat4840G-in-mz.120-1a.W5.6b.bin
4   -rw- 	  2386	      Feb 19 1999   17:25:36    startup-config
 
16384000 bytes total (9360836 bytes free)
SLB-Switch# 

Deleting Files from Flash Memory

When you delete a file from Flash memory, the system marks the file as deleted, allowing you to later recover a deleted file using the undelete command. Erased files cannot be recovered. To permanently erase the configuration file, use the squeeze command.

The squeeze command permanently removes files marked for deletion, and pushes all the other undeleted files together to eliminate spaces between them. To prevent data loss due to sudden power loss, the "squeezed" data is temporarily saved to another location in Flash memory. The squeeze command keeps a log of the functions performed so that if a power failure occurs, the system continues the process when the power resumes.


Caution  When deleting files from memory, be careful not to delete all the system images. If you delete all existing system images, you can no longer download new images.

The following is an example of the delete and squeeze commands used together. Note that the delete command requires you to specify the filename, while the squeeze command requires that you specify the Flash memory media (for example, slot0:).

SLB-Switch# delete cat4840G-in-mz.X.bin

SLB-Switch# dir

Directory of slot0:/
 
4 -rw-	2386	May 11 1999 17:25:36  startup-config
 
16384000 bytes total (9360836 bytes free)
SLB-Switch# 
 

The image file is marked for deletion. Use the squeeze command to complete the operation.

SLB-Switch# squeeze slot0:

All deleted files will be removed, proceed? [confirm] y

Squeeze operation may take a while, proceed? [confirm] Y

ebESESESESESESESES
SLB-Switch# dir

4 -rw-	2386	May 11 1999 17:25:36  startup-config
 
12869836 bytes available (1825540 bytes used)
 

Table 3-1 lists and describes the output that could be generated from a squeeze command.


Table 3-1: Interpreting the Output from the squeeze Command
Output Letter Description

e

This special location was erased (which must be performed before any write operation).

b

The data about to be written to this special location was temporarily copied.

E

The sector temporarily occupied by the data was erased.

S

The data was written to its permanent location in Flash memory.

Z

This log was erased after the squeeze command was successfully completed.

Booting from a Flash PC Card

Future releases of Cisco IOS system images can be obtained from a network server, a floppy disk, or a Flash PC Card. This section describes how to configure the SLB switch so that it boots from an image on a Flash PC Card. To enable booting from a Flash PC Card, perform the following steps:

Command Purpose

Step 1 

SLB-Switch# configure terminal

SLB-Switch(config)#

Enters global configuration mode.

Step 2 

SLB-Switch(config)# no boot system

Disables booting from bootflash.

Step 3 

SLB-Switch(config)# boot system flash 
[flash-fs:] [partition-number:] 
[filename]

Enables booting from the image name file on the specified Flash file system device.

Step 4 

SLB-Switch(config)# config-reg 0x2102

Sets the configuration register for automatic booting.

Step 5 

SLB-Switch(config)# end

SLB-Switch#

Exits global configuration modes.

Step 6 

SLB-Switch# copy system:running-config 
nvram:startup-config

Saves the configuration to NVRAM.

Step 7 

SLB-Switch# reload

Reboots the system.

When you enter boot commands, be careful not to insert extra spaces because they influence the way the SLB switch interprets the command. For example, notice the difference in the following commands:

The following command correctly instructs the SLB switch to boot the image1 file.

SLB-Switch(config)# boot system flash slot0:image1

 

The following command incorrectly contains a space between "slot0:" and "image2." The SLB switch finds the filename field blank and so boots the first file on the Flash PC Card.

SLB-Switch(config)# boot system flash slot0: image2

Backing Up a System Image to a TFTP Server

To create a backup copy of your system image, or to verify that the copy in Flash memory is the same as the original file on disk, you can copy system images from Flash memory to a Trivial File Transfer Protocol (TFTP) server.

In some implementations of TFTP, you must create a dummy file on the TFTP server and give it read, write, and execute permissions before copying the file over it. Refer to your TFTP documentation for more information.

Before you copy software between the network server and Flash memory in the SLB switch, perform the following tasks:

To create a backup of the system software on a TFTP server, perform the following steps:

Command Description

Step 1 

SLB-Switch# cd filesystem:

Changes the Flash device to the slot that holds the Flash PC Card.

Step 2 

SLB-Switch# show flash all

Displays the contents of Flash memory, including the names of the images that currently reside there.

Note the name of the image file you want to copy.

Step 3 

SLB-Switch# copy flash tftp: 

Copies a file from Flash memory to a TFTP server. Be sure to include a colon at the end of the tftp keyword, as shown in this example.

The following example demonstrates copying a specified system image file from the current flash device to the default TFTP server:

SLB-Switch# copy flash tftp:

Source filename []? cat4840G-in-mz.X.bin

Address or name of remote host [172.8.1.129]? y

Destination filename [cat4840G-in-mz.X.bin]? y

Copying a System Image from a TFTP Server to a Flash PC Card

It is a good idea to have a copy of the current system image on a Flash PC Card in case the file in Flash memory becomes corrupted. You can then replace the system software by copying the backup image from the Flash PC Card to the onboard Flash memory. Perform the following steps to copy the system image from the TFTP server to a Flash PC Card:


Note   Be sure that you have a properly formatted Flash PC Card in the appropriate slot before beginning this procedure.

Command Description

Step 1 

SLB-Switch# cd filesystem:

Changes the Flash device to the slot that holds the Flash PC Card.

Step 2 

SLB-Switch# pwd

Verifies that you are in the right directory.

Step 3 

SLB-Switch# copy tftp flash:

Copies a file from a TFTP server to Flash memory.

The following example demonstrates copying a system image file from the default TFTP server to the current Flash PC Card:

SLB-Switch# copy tftp flash:

Source filename []? cat4840G-in-mz.X.bin

Address or name of remote host [172.8.1.129]? y

Destination filename [cat4840g-in-mz.X.bin]? y

5746016 bytes available on device slot0, proceed? [confirm] y

 

Now that you have configured the processor, see "Configuring Interfaces," for instructions on interface configurations for your SLB switch.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Sep 28 15:22:15 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.