|
|
This chapter describes some fundamental tasks you perform to maintain the configuration files, system images, and hardware functional images used by your ATM switch. The following sections are included:
Check the information in the first sections of the chapter to determine if it applies to your installation. Also, familiarize yourself with the Cisco IOS File System section, as this describes new features in this release. If you are an experienced IOS user, you can skip the third section. You should learning about maintaining functional images if you have a channelized Frame Relay port adapter.
If you are managing the ATM switch through an Ethernet interface or ATM subinterface on the processor, and your management station or Trivial File Transfer Protocol (TFTP) server is on a different subnet than the ATM switch, you must first configure a static IP route.
 | Caution Failure to configure a static IP route prior to installing the new image will result in a loss of remote administrative access to the ATM switch. If this happens, you can regain access from a direct console connection, although this requires physical access to the console port. |
To configure a static IP route, perform the following tasks, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | Configure a static IP route on the Ethernet interface or ATM subinterface of the processor. | |
| 2 | end | Return to privileged EXEC mode. |
| 3 | copy system:running-config nvram:startup-config | Save the configuration to NVRAM. |
| 1The IP route prefix of the remote network where the management station or TFTP server resides. 2The subnet mask of the remote network where the management station or TFTP server resides. |
The following example shows how to configure an IP address on the main Ethernet port, then save the configuration.
Switch(config)# interface ethernet0 Switch(config-if)# ip address 172.20.52.11 255.255.255.224 Switch(config-if)# end Switch# copy system:running-config nvram:startup-config
This release of the ATM switch system software uses the Cisco IFS (IOS File System). With IFS, you now access files on a storage device by specifying a filename and the file system containing the file. The following old command, for example, accesses the running-config and startup-config files:
Switch# copy running-config startup-config
With IFS, you additionally specify the system containing the files using the syntax filesystem:filename. For example:
Switch# copy system:running-config nvram:startup-config
The syntax filesystem:filename is called the file URL. In addition, remote file systems (such as TFTP, FTP, and rcp) allow you to specify additional options in the file URL, such as username, password, remote host, and so on. This way, you can enter all the required information at once without having to respond to prompts.
With IFS, some show commands have been replaced with more commands. For example:
Switch# show running-config
has been replaced with the following command:
Switch# more system:running-config
For complete information on using file URLs and the new IFS commands and syntax, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publication.
File systems on the ATM switch include read-only memory (RAM, or system), Flash memory (such as bootflash and the PCMCIA cards in slot0 and slot1), and remote file systems (such as TFTP or rcp servers).
You can use the show file systems privileged EXEC command to display the valid file systems on your ATM switch. For example:
Switch# show file systems
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - opaque rw null:
- - opaque rw system:
- - network rw tftp:
126968 122659 nvram rw nvram:
* - - flash rw slot0: flash:
- - flash rw slot1:
7602176 704008 flash rw bootflash:
- - network rw rcp:
- - network rw ftp:
131072 0 opaque ro atm-acct-ready:
131072 131072 opaque ro atm-acct-active:
Refer to the Configuration Fundamentals Configuration Guide for details on the following frequently performed tasks:
The following sections list common tasks you perform to maintain system images and configuration files on your ATM switch:
For detailed instructions on performing these tasks, refer to the Configuration Fundamentals Configuration Guide.
The following are frequently performed tasks to maintain configuration files:
The following are frequently performed tasks to maintain system image files:
The following commonly performed tasks are used to reboot the ATM switch and specify startup information:
You can load functional images used by certain hardware controllers in the ATM switch. The following sections describe the function and maintenance of functional images:
Functional images provide the low-level operating functionality for various hardware controllers. On hardware controllers with insystem programmable devices, such as Field Programmable Gate Arrays (FPGAs) and Erasable Programmable Logic Devices (EPLDs), the hardware functional images can be reprogrammed independently of loading the system image and without removing the devices from the controller.
All new hardware is shipped with functional images preloaded. Loading a different functional image is therefore required only when upgrading or downgrading functional image versions.
You load a functional image in two steps:
Step 1 Copy the image to a Flash memory device (bootflash, slot0, or slot1). For instructions on copying files to a Flash memory device, refer to the Configuration Fundamentals Configuration Guide.
Step 2 Load the image from the Flash memory device to the hardware controller.
To download a functional image from a Flash memory device to a hardware controller, use the following command in privileged EXEC mode:
| Command | Task |
|---|---|
reprogram device:filename slot [subcard] | Load the functional image with the specified filename to a device. |
The reprogram command checks the compatibility of the image for the selected card type before downloading the functional image.
| Caution Do not interrupt the download procedure. Wait until it has finished before attempting any commands on the switch. |
The following example demonstrates loading the functional image abr_tmp.exo from the PCMCIA card in slot 0 to the controller in slot 0, subcard 1.
Switch# reprogram slot0:abr_tmp.exo 0 1
To display the functional image version in a hardware controller, use the following command in privileged EXEC mode:
| Command | Task |
|---|---|
show functional-image-info {slot slot| subslot slot/subcard} | Display the functional image information. |
The following example shows the functional image information for the module in slot 0, subcard 1:
Switch# show functional-image-info subslot 0/1 #HardwareRequired : B8(3.2) #FunctionalVersion : 2.3 #Sections : 1 #Section1Format : BINARY , length = 308316 PUMA-4CE1 Firmware image Copyright (c) 1996-98 by cisco Systems, Inc. All rights reserved. generated by : rsankar on : Fri Oct 16 12:48:44 PDT 1998 Firmware Image : /tftpboot/puma4ce1fw/2.3/C85MS-4E1-FRRJ48.2.3 EPLD config file : C85MS-4E1-FRRJ48.jcf Chain description: Part type Bits Config file EPM7256S 10 /cougar/custom/puma/pld/testbench/PROG_FILES/4CE1/PLD/DB/7256.pof EPM7064S 10 /cougar/custom/puma/pld/testbench/PROG_FILES/4CE1/PLD/DB/7064.pof EPM7128S 10 /cougar/custom/puma/pld/testbench/PROG_FILES/4CE1/PLD/MB/7128S.pof Number devices = 3 Number of instruction bits = 30 FPGA config file information: date/time File 10/16/98 /tftpboot/puma4ce1fw/2.3/C85MS-4E1-FRRJ48.3.2.ttf
Posted: Fri Apr 9 10:08:43 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.