ATM and Layer 3 Quick Software Configuration Guide, 12.1(5)EY1
Getting Started
Download this chapter
Getting StartedGetting Started
Download the complete book
ATM and Layer 3 Quick Software Configuration GuideATM and Layer 3 Quick Software Configuration Guide (PDF - 6 MB)
give_us_feedback

Table Of Contents

Getting Started

Naming the Switch Router

Assigning a Password

Setting Up Remote Administrative Access

Updating the System Image

Downloading System Images from Cisco.com

Copying the System Image to the Switch Router

Reloading the Switch Router

Updating Images on Redundant Route Processors (Catalyst 8540)

Getting Started

This chapter describes basic software configuration of the switch router, and includes the following sections:

• Naming the Switch Router

• Assigning a Password

• Setting Up Remote Administrative Access

• Updating the System Image

Note For more software configuration information, refer to the ATM Switch Router Software Configuration Guide and Layer 3 Software Configuration Guide.

Naming the Switch Router

You can name the switch router to distinguish it from other Cisco devices in your network. This feature is especially useful when you have multiple console windows open and you need to distinguish one Cisco device from another. Naming the switch changes the default prompt to match the host name; for example, Nevada_Switch>.

Perform these steps:

 
Command
Purpose

Step 1

Switch> enable

Enters privileged EXEC mode.

Step 2

Switch# configure terminal

Switch(config)#

Enters global configuration mode.

Step 3

Switch(config)# hostname Name

Name(config)#

Specifies the host name for the switch. Note that the prompt changes to match the host name.

Note The pound sign (#) that follows the host name indicates the current mode of operation and is added automatically.

 

Step 4

Name(config)# end

Name#

Returns to privileged EXEC mode.

Example 

Switch> enable

Switch# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# hostname Nevada_Switch

Nevada_Switch(config)# end

Nevada_Switch#

Verify 

Switch# more system:running-config

!

version xx.x

no service pad

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname Nevada_Switch

!

<Information deleted>

Assigning a Password

Configure an administrative password on the switch router to prevent unauthorized configuration changes.

Perform these steps:

 
Command
Purpose

Step 1

Switch> enable

Enters privileged EXEC mode.

Step 2

Switch# configure terminal

Switch(config)#

Enters global configuration mode.

Step 3

Switch(config)# enable password password

Specifies the enable password.

Step 4

Switch(config)# exit

Switch#

Returns to privileged EXEC mode.

Example 

Switch> enable

Switch# configure terminal

Switch(config)# enable password guessme

Switch(config)# exit

Switch#

Verify 

Switch# exit

Switch con0 is now available 

Press RETURN to get started. 

Switch> enable 

Password: guessme 

Switch#

Setting Up Remote Administrative Access

You can configure the Ethernet interface on the router processor (processor card) so that you can Telnet to the switch router and configure it remotely. This section describes how to configure the Ethernet port for remote administrative access.

Note For local administrative access, connect a PC or workstation to the console port on the route processor. This requires physical access to the switch router.

Perform these steps:

 
Command
Purpose

Step 1

Switch> enable

Enters privileged EXEC mode.

Step 2

Switch# configure terminal

Switch(config)#

Enters global configuration mode.

Step 3

Switch(config)# ip route prefix mask ethernet 0[.subinterface]

Configures a static route on the Ethernet interface. If your management station or TFTP1 server is on a different subnet than the switch, you must configure a static IP route.2

Step 4

Switch(config)# interface ethernet 0

Switch(config-if)#

Enters interface configuration mode on the Ethernet interface.

Step 5

Switch(config-if)# ip address ip-address subnet-mask

Specifies an IP address on the Ethernet interface.

Step 6

Switch(config)# end

Switch#

Returns to privileged EXEC mode.

Step 7

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

Saves your configuration changes to NVRAM.

1 TFTP = Trivial File Transfer Protocol.

2 If you fail to configure a static IP route before installing a new image, you might lose remote administrative access to the switch. If this happens, you can regain access from a direct console connection, although this requires physical access to the console port on the route processor.

Example 

Switch> enable

Switch# configure terminal

Switch(config)# ip route 209.165.201.0 255.255.255.224 ethernet 0

Switch(config)# interface ethernet 0

Switch(config-if)# ip address 209.165.201.20 255.255.255.224

Switch(config-if)# end

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

Verify 

Switch# show interface ethernet 0

Ethernet0 is up, line protocol is up

  Hardware is SonicT, address is 00e0.4fac.b400 (bia 00e0.4fac.b400)

  Internet address is 209.165.201.20/27

  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 
1/255

  Encapsulation ARPA, loopback not set, keepalive set (10 sec)

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Queueing strategy: fifo

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 1000 bits/sec, 2 packets/sec

  5 minute output rate 0 bits/sec, 1 packets/sec

     897 packets input, 55088 bytes, 0 no buffer

     Received 337 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     0 input packets with dribble condition detected

     20731 packets output, 2024862 bytes, 0 underruns

     0 output errors, 0 collisions, 1 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Switch#

Updating the System Image

This section provides basic instructions for updating the system image on your switch router. This procedure assumes that you are manually booting the switch router from a system image on a Flash PC Card. You can also configure the switch router to boot automatically from a system image specified in the BOOT environment variable. For additional information on booting options and maintaining system images, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.

The following steps give the general procedure for updating the system software:

Step 1 Download the system image from Cisco.com.

Step 2 Copy the system image to the switch router.

Step 3 Reload the switch router with the new image.

Downloading System Images from Cisco.com

Cisco IOS system images, along with other software, are available from the Software Center listed under "Services and Support" on Cisco.com at http://www.cisco.com. You can download system images from Cisco.com using your browser's FTP capability, using conventional FTP, or using the Cisco.com asynchronous dial-up interface.

For instructions on accessing and downloading software from Cisco.com, refer to the "Using the Software Center" information available in the Software Center on Cisco.com.

Copying the System Image to the Switch Router

You can copy the system image to the switch router using TFTP, FTP, or RCP. If the system you used to download the image from Cisco.com does not function as a TFTP, FTP, or RCP server, you must first copy the file to an intermediate server that provides those services to your switch router.

Note Before copying the system image from the server to the switch router, check the size of the file to make sure you will have enough room for it on the Flash memory device. On UNIX file systems, use the ls -la command from the directory where the file is stored to display the file size.

To copy the system image from a TFTP server to the Flash PC Card, initiate a Telnet session or console connection to the switch.

Perform these steps:

 
Command
Purpose

Step 1

enable

Enters privileged EXEC mode.

Step 2

209.165.201dir filesystem:

Displays the contents and available space on the Flash device.

Note If there is not enough free space to copy the new system image, perform Steps 2 and 3. Otherwise, proceed to Step 4.

Step 3

Switch> delete filesystem:filename

Deletes files as needed to free space for the new system image. If you have older system images stored on the file system, it is recommended that you delete the oldest one and leave a newer one in case you need to revert.

Step 4

Switch# squeezeSwitch# filesystem:

Permanently deletes files so that the space can be reused.

Step 5

Switch# copy tftp: filesystem:

Initiates a TFTP session to copy the system image from the TFTP server. The system prompts you for a TFTP server name and filename.

Step 6

Switch# dir filesystem:

Displays the contents of the file system. This step confirms that the file was copied as expected.

Example 

Switch# dir slot0:

Directory of slot0:/

1  -rw-     7158424   Nov 30 1999 15:46:33  cat8540c-in-mz.120-6.5.W5.15.0.8

2  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3


20578304 bytes total (6222180 bytes free)

Switch# delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8

Delete filename [cat8540c-in-mz.120-6.5.W5.15.0.8]?

Delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8? [confirm]

Switch# squeeze slot0:

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

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

Erasomg squeeze log . . . . . . . . . . . . . . . 

Switch# copy tftp: slot0:

Address or name of remote host [] ? 209.165.201.25

Source filename [] ? joe/cat8540c-in-mz.120-6.5.W5.16.0.8

Destination filename [cat8540c-in-mz.120-6.5.W5.16.0.8] ?

Verify 

Switch# dir slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

Note Be sure that the size of the downloaded file on the switch router is the same as the file on the server. If the file size on the switch router is different, delete the file and download it again from the server.

Reloading the Switch Router

When the configuration register is set for manual booting, issuing the reload command causes the system to enter ROM monitor mode, where you enter the boot command and the name of the system image to use. To reload the switch router, connect to the console port to access the switch router in ROM monitor mode. For automatic booting, enter the reload command from an Ethernet connection to the route processor.

Note This procedure assumes that you need to change the boot field in the configuration register from its default value so that the system reverts to ROM monitor mode when the reload command is entered.

Perform these steps:

 
Command
Purpose

Step 1

Switch# enable

Enters privileged EXEC mode.

Step 2

configure terminal

Switch>

Enters global configuration mode.

Step 3

Switch#config-register 0x0

Sets the configuration register for manual booting from ROM monitor mode.1

Step 4

Switch(config)#end

Switch(config)#

Returns to privileged EXEC mode.

Step 5

Switch(config)# copy system:running-config nvram:startup-config

Saves your configuration changes to NVRAM.

Step 6

Switch#reload

Initiates a reload of the system software.

Step 7

Switch# dirSwitch# filesystem:

Displays the contents of the file system. Perform this optional step to display and copy the name of the system image to the clipboard for use in the next step.

Step 8

rommon 1> boot filesystem:filename

Reboots the switch router with the new system image.

Step 9

rommon 1> show version

Displays the system software version information. Use this step to confirm that the system is loaded with the expected software version.

1 For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.

Example 

Switch(config)# config-register 0x0

Switch(config)# end

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

Destination filename [startup-config]?

Building configuration...

[OK]

Switch# reload

System configuration has been modified. Save? [yes/no]: yes

Warning: Attempting to overwrite an NVRAM configuration previously written

by a different version of the system image.

Overwrite the previous NVRAM configuration?[confirm]

Building configuration...

[OK]

Proceed with reload? [confirm]

rommon 1> dir slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

rommon 2> boot slot0:cat8540c-in-mz.120-6.5.W5.15.0.8


<The system boots.>

Verify 

Switch> show version

Cisco Internetwork Operating System Software

IOS (tm) L3 Switch/Router Software (C8540CSR-IN-M), Version 12.0(6.5)W5(16.0.8)

Copyright (c) 1986-2000 by cisco Systems, Inc.

Compiled Fri 07-Jan-2000 15:25 by

Image text-base: 0x60010930, data-base: 0x60882000

Updating Images on Redundant Route Processors (Catalyst 8540)

When updating the system image on a switch router with redundant route processors, you must update both route processors.

Perform these steps:

 
Command
Purpose

Step 1

enable

Enters privileged EXEC mode on the primary route processor Ethernet interface.

Step 2

Switch> dir slotn:

dir sec-slotn:

Displays the contents and available space on the Flash PC Card. If there is not enough free space to copy the new system image, perform Steps 3 and 4. Otherwise, proceed to Step 5.

Step 3

Switch> delete slotn:filename

Switch# delete sec-slotn:filename

Deletes files as needed to free space for the new system image.

Step 4

Switch# squeezeSwitch# slotn:

Switch# squeezeSwitch# sec-slotn:

Permanently deletes files so that the space can be reused.

Step 5

copy tftp:Switch# slotn:

copy tftp:Switch# sec-slotn:

Copies the system image from the TFTP server.

Step 6

dirSwitch# slotn:

dirSwitch# sec-slotn:

Displays the Flash PC Card contents.

Step 7

configure terminal

Switch#

Enters global configuration mode.

Step 8

config-register 0x0

Sets the configuration register for manual booting from ROM monitor mode.1

Step 9

Switch#end

Switch(config)#

Returns to privileged EXEC mode.

Step 10

Switch(config)# copy system:running-config nvram:startup-config

Saves your configuration changes to NVRAM.

Step 11

Switch(config)# reload

Initiates a reload of the system software.

Note The secondary route processor becomes the primary at this point.

 

Step 12

Switch#dirSwitch# slotn:

Displays the contents of the file system.

Step 13

Switch# bootrommon 1> slotn:filename

Reboots the route processor with the new system image.

Note This route processor becomes the secondary.

 

Step 14

enable

On the new primary route processor console interface, enters privileged EXEC mode.

Step 15

rommon 2> reload

Initiates a reload of the primary route processor.

Note The secondary route processor becomes the primary at this point.

 

Step 16

dirSwitch> slotn:

Displays the Flash PC Card contents.

Step 17

Switch# bootrommon 1> slotn:filename

Reboots the route processor with the new system image.

Note This route processor becomes the secondary.

 

Step 18

enable

On the new primary route processor, enters privileged EXEC mode.

Step 19

rommon 1> show redundancy

Displays the system redundancy information.

1 For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.

Example 

Switch> enable

Switch# dir slot0:

Directory of slot0:/

1  -rw-     7158424   Nov 30 1999 15:46:33  cat8540c-in-mz.120-6.5.W5.15.0.8

2  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3


20578304 bytes total (6222180 bytes free)

Switch# dir sec-slot0:

Directory of sec-slot0:/

1  -rw-     7158424   Nov 30 1999 15:46:33  cat8540c-in-mz.120-6.5.W5.15.0.8

2  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3


20578304 bytes total (6222180 bytes free)

Switch# delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8

Delete filename [cat8540c-in-mz.120-6.5.W5.15.0.8]?

Delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8? [confirm]

Switch# delete sec-slot0:cat8540c-in-mz.120-6.5.W5.15.0.8

Delete filename [cat8540c-in-mz.120-6.5.W5.15.0.8]?

Delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8? [confirm]

Switch# squeeze slot0:

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

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

Erasomg squeeze log . . . . . . . . . . . . . . . 

Switch# squeeze sec-slot0:

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

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

Erasomg squeeze log . . . . . . . . . . . . . . . 

Switch# copy tftp: slot0:

Address or name of remote host [] ? 209.165.201.25

Source filename [] ? joe/cat8540c-in-mz.120-6.5.W5.16.0.8

Destination filename [cat8540c-in-mz.120-6.5.W5.16.0.8] ?

Switch# copy tftp: sec-slot0:

Address or name of remote host [] ? 209.165.201.25

Source filename [] ? joe/cat8540c-in-mz.120-6.5.W5.16.0.8

Destination filename [cat8540c-in-mz.120-6.5.W5.16.0.8] ?

Switch# dir slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

Switch# dir sec-slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

Switch(config)# config-register 0x0

Switch(config)# end

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

Destination filename [startup-config]?

Building configuration...

[OK]

Switch# reload

System configuration has been modified. Save? [yes/no]: yes

Building configuration...

[OK]

Proceed with reload? [confirm]


<The secondary route processor becomes the primary.>


rommon 1> dir slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

rommon 2> boot slot0:cat8540c-in-mz.120-6.5.W5.15.0.8


<This route processor boots as the secondary.>


<Connect to the console for the new primary route processor.>


Switch> enable

Switch# reload

System configuration has been modified. Save? [yes/no]: yes

Building configuration...

[OK]

Proceed with reload? [confirm]


<The secondary route processor becomes the primary.>

rommon 1> dir slot0:

Directory of slot0:/

1  -rw-     7197444   Jan 02 2000 00:35:33  cat8540c-in-mz.120-6.5.W5.16.0.3

2  -rw-     7110320   Jan 07 2000 15:25:40  cat8540c-in-mz.120-6.5.W5.16.0.8


20530200 bytes total (6270284 bytes free)

rommon 2> boot slot0:cat8540c-in-mz.120-6.5.W5.15.0.8


<This route processor boots as the secondary.>

Verify 

Switch# show redundancy


This CPU is the PRIMARY

Primary

-------

Slot:                          4  

Uptime:                        3 weeks, 3 days, 6 hours, 40 minutes

Image:                         PNNI Software (cat8540m-WP-M), Version 12.1(2.3)W6(1.33), 
CISCO DEVELOPMENT TEST VERSION


Time Since :                  

  Last Running Config. Sync:   2 hours, 55 minutes

  Last Startup Config. Sync:   1 day, 41 minutes

Last Restart Reason:           Normal boot


Secondary

---------

State:                         UP

Slot:                          8  

Uptime:                        16 hours, 54 minutes

Image:                         PNNI Software (cat8540m-WP-M), Version 12.1(2.3)W6(1.33), 
CISCO DEVELOPMENT TEST VERSION