Table of Contents

List of Terms
Feature Pack Contents
How to Use These Release Notes

Memory Defaults and Upgrade Options
Hardware Supported
Software Compatibility
Determining Your Software Release
Product Numbers Quick-Reference List
Feature Pack Overview Table
Feature Set Tables

Image Installation Tips and Troubleshooting When Using RSL

Image Installation Tips
Recovering from a Connection Error
Restoring the Startup Configuration

Alternatives to RSL

Installing the Router Software by Using a TFTP Server Application
Installation Procedure for Flash Images
Sample Session
Installation Procedure for RAM Images
Sample Session

Release-Specific Documents
Platform-Specific Documents

Platform Documents
Software Documents

Feature Modules
Cisco IOS Documentation Set

Documentation Modules
Release 12.0 Documentation Set

World Wide Web
Documentation CD-ROM
Ordering Documentation

Cisco Connection Online
Technical Assistance Center
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
Documentation Feedback

Release Notes for Cisco IOS Release 12.0(10)W5(18c) Feature Pack for the Cisco Catalyst 8540 MSR

November 13, 2000

These release notes describe the Cisco IOS Release 12.0(10)W5(18c) feature pack for the Catalyst 8540 MSR ATM switch router.

Note   You can find the most current Cisco IOS documentation on Cisco Connection Online (CCO ). These electronic documents may contain updates and modifications made after the hardcopy documents were printed. For more information about CCO, refer to "Cisco Connection Online" section.

Contents

These release notes describe the following topics:

Introduction

List of Terms

The following terms are used throughout this document:

Feature—Networking functionality that supports network technology and hardware. For example: Double Authentication, IP Multicast over Token Ring, Voice Over IP, PPP over ATM, and so forth.

Feature Set—A group of features. For example: IP, IP Plus, Enterprise Plus, IP IPSec 56, and so forth.

Image—Software code containing a Cisco IOS feature set. The image file nomenclature, such as c800-y6-mw, c1000-bnsy40-mz, and c2500-g-l, specifies a platform, feature set, and file compression method. For example, c4500-is56i-mz indicates:

Feature Pack—A small box containing hardcopy documentation and CDs that contain software images, applications and electronic documentation. Feature packs provide software upgrades for many of the Cisco hardware platforms.

Feature Pack Contents

Your feature pack contains:

---

Note    If you cannot use RSL to load images, you can follow the instructions in the "Alternatives to RSL" section.

---

How to Use These Release Notes

The tables in these release notes contain details about the Cisco feature packs. Use these tables to perform the following tasks before loading a software image onto a router:

1. Use Table 1, "Catalyst 8540 MSR Default Memory and Upgrade Options,"on for the feature set memory requirements, factory-default memory, and available memory upgrades for your Catalyst 8540 MSR.

2. Use Table 4, "Catalyst 8540 MSR Feature Packs," on to identify your feature pack and the memory required for your feature set, based on the image you load.

3. Use the tables in the "Feature Set Supported by the Catalyst 8540 MSR" section to identify which features are supported in a feature set image.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.0(10)W5(18c):

Memory Defaults and Upgrade Options

Hardware Supported

Cisco IOS Release 12.0(10)W5(18c) supports the Catalyst 8540 MSR switch router. The following table lists the supported ATM port adapters and modules:

Software Compatibility

The feature pack described in this release note contains Cisco IOS Release 12.0(10)W5(18c) software images, some images from previous software releases, and Router Software Loader (RSL) Version 7.10.

Determining Your Software Release

To determine the version of Cisco IOS software running on your Catalyst 8540 MSR, log in to the Catalyst 8540 MSR, and enter the show version user EXEC command.

Product Numbers Quick-Reference List

Feature Pack Overview Table

Feature Set Tables

The Cisco IOS software is packaged in feature sets consisting of software images—depending on the Catalyst 8540 MSR. Each feature set contains a specific set of Cisco IOS features.

For a summary of which feature sets are supported on each Catalyst 8540 MSR, see Table 4 in the "Feature Pack Overview Table" section.

Table 5 lists the features and feature sets supported by the Catalyst 8540 MSR in Cisco IOS Release 12.0(10)W5(18c).

Note   This feature set table contains only a selected list of features. This table is not a cumulative or complete list of all the features in each image.

Table 5   Feature Set Supported by the Catalyst 8540 MSR

Feature Set
Left-justified E.164 AFI support
SNMP1
Asynchronous support
PPP2 (SLIP3/PPP)
IP4
NTP5
TACACS+6
Telnet
Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI9 3.0)
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)
Multipoint-to-point UNI signaling
Soft VCCs and VPCs
VP tunneling
VPI/VCI range support in ILMI 4.0
PNNI hierarchy
ILMI10 version 4.0
IISP11
LANE12 client (LEC13) and LANE services (LES14/BUS15/LECS16) on Route Processor
ATM ARP17 server on Route Processor
ATM ARP client on Route Processor
ATM tag switch router (TSR)
Port snooping
OAM18 F4 and F5
E.164 address translation
E.164 autoconversion
Circuit emulation
ATM access lists
ATM accounting
ATM RMON19
Multiple, weighted, dynamic thresholds for selective packet marking and discard
Shaped VP tunnels for CBR20 traffic
Substitution of other service categories in shaped VP tunnels
Dual leaky bucket policing
Scheduler/Service Class/PVC configuration
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC)
Network clocking enhancements for smooth switchover
Per-VC or per-VP nondisruptive snooping
Support for non-zero MCR21 on ABR22 connections
Access lists on ILMI registration
CUGs
ATM soft restart
ATM accounting enhancements
CISCO-SYSLOG-MIB support
CISCO-CONFIG-COPY-MIB support
Signaling diagnostics and MIB23
Supplemental AToM MIB
E1 Frame Relay Port Adapter
Frame Relay to ATM Interworking Features on the Channelized E1 Port Adapter
Hierarchical VP tunnels
Remote logging for accounting
Tag switching VC-merge on non-UBR24 VP tunnels and hierarchical VP tunnels
PNNI complex node representation
Support for ATM-Fabric Integration Module in Catalyst 5500
PNNI explicit paths
PNNI alternate link selection
Tag switching CoS
Network Clock Distribution Protocol
Simple Gateway Control Protocol
Switch redundancy
CPU redundancy: PVP/PVC/VP tunnel preservation
12-bit VPI
ATM Router Module
ATM overbooking
Framing overhead
ATM End System Address (AESA) gateway
Online insertion and removal support for 8-port Gigabit Ethernet interface modules
Route processor switchover support for 8-port Gigabit Ethernet interface modules
Appletalk support for 8-port Gigabit Ethernet interface modules
RFC 1483 support on the ATM router modules
RFC 1577 support on the ATM router modules
Layer 2 Bridging Features
Layer 2 transparent bridging
Layer 2 MAC learning, aging, and switching by hardware
Spanning-Tree Protocol (IEEE 802.1d) support per bridge group
Support for a maximum of 64 active bridge groups
Integrated routing and bridging (IRB) mode support
Virtual LAN (VLAN) Features
Inter-Switch Link (ISL)-based VLAN trunking
802.1Q-based VLAN routing Note    Untagged packets arriving on a native VLAN are handled by the CPU, rather than the microcode.
Layer 3 Routing, Switching, and Forwarding Features
IP, IPX, and IP multicast routing and forwarding between Ethernet ports
AppleTalk 1 and 2 routing
CMF (constrained multicast flooding)
Up to 128 IP multicast groups
QoS-based forwarding based on IP precedence-based forwarding
Load balancing among equal-cost paths based on source and destination IP and IPX addresses
Supported Routing Protocols
RIP and RIP II (Routing Information Protocol)
IGRP (Interior Gateway Routing Protocol)
EIGRP (Enhanced Interior Gateway Routing Protocol)
OSPF (Open Shortest Path First)
IPX (Internet Packet Exchange) RIP and EIGRP
PIM (Protocol Independent Multicast) — sparse and dense modes
RTMP (AppleTalk Routing Table Maintenance Protocol)
AURP (AppleTalk Update-based Routing Protocol)
Secondary addressing
Static routes
Classless Interdomain Routing (CIDR)
Fast EtherChannel (FEC) Features
Bundling of up to four Fast Ethernet ports in a maximum of 64 FECs
Load sharing based on source and destination IP addresses of unicast packets
Load sharing for bridge traffic based on MAC address
ISL
802.1Q routing
Note    Up to 64 active FEC and GEC port channels in one system.
Gigabit EtherChannel (GEC) Features
Bundling of up to four Gigabit Ethernet ports
Load sharing based on source and destination IP addresses of unicast packets
Load sharing for bridge traffic based on MAC address
ISL
802.1Q routing
Up to 64 active FEC and GEC port channels in one system Note    Up to 64 active FEC and GEC port channels in one system.
Enhanced Gigabit Ethernet Features
Two 1-port enhanced Gigabit Ethernet port adapters with built-in ACL functionality and 16, 64, or 256 KB of memory available for routing tables
Access Control Lists (ACL)
Layer 2 filtering: MAC address filtering standard ACL
Layer 3 filtering using an ACL daughter card: Standard/extended IP access ACL lists (1-99; 1301-1999/100-199; 2000-2699) in hardware; both inbound and outbound TCP ACL based on TCP-precedence, TCP port number, TCP ToS, and TCP flags UDP ACL based on UDP port number ICMP ACL IPX standard ACL (800-899) without source node Required for each existing line card implementing data-plane ACLs The same part number Catalyst 8510 ACL is supported on the 8-port 10/100Base-TX, 8-port 100Base-FX, and 1-port Gigabit Ethernet interface modules All Cisco IOS ACLs for control-plane traffic Named access lists Note    The ACL daughter card is supported in the Fast Ethernet card 4.1 version and above, and the Gigabit Ethernet card 2.1 version and above.
Additional Protocols Supported
BOOTP (Bootstrap Protocol)
CGMP (Cisco Group Management Protocol) server support
CDP (Cisco Discovery Protocol) support on Ethernet ports
DHCP (Dynamic Host Configuration Protocol) Relay
HSRP (Hot Standby Routing Protocol) over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface)
ICMP (Internet Control Message Protocol)
IGMP (Internet Group Management Protocol)
IPX SAP (Internet Packet Exchange Service Advertisement Protocol) and SAP filtering
IRB (integrated routing and bridging) routing mode support
SNMP (Simple Network Management Protocol)
UDP (User Datagram Protocol) turbo flooding

1SNMP = Simple Network Management Protocol 2PPP = Point-to-Point Protocol 3SLIP = Serial Line Internet Protocol 4IP = Internet Protocol 5NTP = Network Time Protocol 6TACACS+ = Terminal Access Controller Access Control System Plus 7VCCs = virtual channel connections 8VPCs = virtual path connections 9UNI = User-Network Interface 10ILMI = Interim Local Management Interface 11IISP = Interim-Interswitch Signaling Protocol 12LANE = LAN Emulation 13LEC = LAN Emulation Client 14LES = LAN Emulation Server 15BUS = broadcast and unknown server 16LECS = LAN Emulation Configuration Server 17ARP = Address Resolution Protocol. 18OAM = Operation, Administration, and Maintenance 19RMON = Remote Monitoring 20CBR = constant bit rate 21MCR = minimum cell rate 22ABR = available bit rate 23MIB = Management Information Base 24UBR = unspecified bit rate

Installation Notes

This section describes the following topics:

Image Installation Tips and Troubleshooting When Using RSL

Image Installation Tips

The following information about RSL operations can help you with the installation process:

Recovering from a Connection Error

If any of the following elements apply to your installation, modify the Short Timeout value from the Options dialog box in RSL:

"Failed to configure the router to enable the Cisco IOS software image and configuration file upload and download operations. You may want to check the router to make sure that the selected interface exists."

If you are connecting to any other router or access server, increase the Short Timeout to a value over 25 seconds.

Note   If you change the timeout value, you must do so before connecting to the Catalyst 8540 MSR, or the new value will not be used. Also, increasing the Short Timeout value can increase the time it takes for RSL to connect to the target Catalyst 8540 MSR.

Restoring the Startup Configuration

In some cases, RSL is unable to restore the startup configuration. If this happens, follow these steps:

Step 2   Restart RSL and connect by using the Preconfigured router option.

Step 3   When asked if you want to overwrite the existing startup configuration file, choose no.

Step 4   When asked if you want to continue, choose yes.

Step 5   When the Catalyst 8540 MSR is connected, select Download Router Configuration in the Router Software Loader dialog box.

Step 6   Select the appropriate file and click the radio button beside Copy configuration to the router nonvolatile memory. The Catalyst 8540 MSR should now contain the startup configuration it had before the initial RSL connection.

Step 7   Exit RSL.

Note   In the steps above, the Catalyst 8540 MSR configuration register (config-register 0xnnnn) is not restored.

Note   If you press Ctrl-Alt-Delete to quit RSL, the router configuration and the configuration register are not restored. However, the configuration file is not deleted from the PC. To restore the configuration file, follow the steps above, beginning with Step 2.

Alternatives to RSL

RSL is designed to work with a PC running Microsoft Windows 95 and is the recommended method for downloading software to the Catalyst 8540 MSR; however, two alternatives are available for installing router software:

Installing the Router Software by Using a TFTP Server Application

This section explains how to install the Cisco IOS software onto Cisco Catalyst 8540 MSR using a Trivial File Transfer Protocol (TFTP) server or remote copy protocol (rcp) server application. Because TFTP and rcp require familiarity with the Cisco IOS command-line interface, we recommend using the Router Software Loader (RSL) application on your software feature pack CD-ROM whenever possible.

Note   You can use the TFTP application with Windows, Macintosh, or UNIX systems; however, you can use the TFTP server included on this software feature-pack CD-ROM only with a PC running Windows 95. For other operating systems, you can find a number of TFTP or rcp applications from independent software vendors or as shareware from public sources on the World Wide Web.

Note   For detailed troubleshooting information, refer to TFTP Upgrade Instructions on the Cisco Technical Assistance Center (TAC) web site.

Note   We recommend that you back up the router configuration before upgrading the router software.

Step 2   Start the TFTP server application by either clicking the Cisco TFTP Server icon on your desktop or choosing Programs from the Start menu and then selecting Cisco TFTP server.

Step 3   Set up the TFTP server root directory to be the location for the image files. From the menu bar, select View and then Options.

Step 4   In the TFTP server root directory field, click Browse to locate the directory that contains the files to copy to the Cisco Catalyst 8540 MSR. From the Browse for the TFTP Server Root Directory window, select a root directory and click OK.

Step 5   In the Options window, click OK.

Step 6   Complete the file transfer by using the Cisco IOS Planner to determine the image to load and the memory requirements for that image. Access the Cisco IOS Planner by going to the Cisco homepage (www.cisco.com) and logging in, then clicking Software Center under the Service & Support heading. You should arrive at the Technical Assistance Center (TAC). Click Cisco IOS Software, then scroll down to the bottom of the Cisco IOS Software page, and click the Upgrade Planner link. You should see Cisco IOS Planner at the top of the page.

Step 7   Select your Platform, Release, and Software Feature to load onto the Catalyst 8540 MSR. You should see the Minimum Recommended Memory to download the image below the table.

Installation Procedure for Flash Images

Note   If installing from RAM images, proceed to "Installation Procedure for RAM Images."

Note   For rcp applications, substitute rcp for every occurrence of TFTP. For example, use "copy rcp flash" instead of "copy tftp flash."

The following example shows the output from the command show version:

Step 2   If your TFTP server or the workstation where you start your Telnet session are not in the same network as the router, add the default gateway.

Knowing if the TFTP Server and the Router Are in the Same Network

Compare the IP address with the mask on the TFTP server and the mask on the Ethernet interface of the router. If you can ping the TFTP server's IP address from the router, they are in the same network.

In case 1, a default gateway is not required because the TFTP server and this interface of the router are in the same network. In case 2, it is necessary to configure a default gateway on the router, because the TFTP server and router are in different IP networks.

Adding the Default Gateway in the Configuration

Once you know the IP address of the default gateway, use the IP default-gateway command from global configuration mode:

Determining the IP Address and Mask on the Router

Look for the IP address command under the interface Ethernet in your configuration.

Determining the IP Address of the TFTP Server (for Windows 95)

Select Start from the toolbar, then select Run. Enter winipcfg and then click ok to display the IP configuration dialog box.

Determining the IP Address of the TFTP Server (for UNIX stations)

Enter the command netstat -in. The IP addresses of the interfaces on your station should appear. Select the one that goes into the router network.

Determining the Default Gateway for the Router

The default gateway is always the next hop that any packet crosses to reach the workstation where you have the TFTP server or the Telnet session source or both. The traceroute command will show the IP address of the default gateway in the first line of the output.

Configuring to Cross a Frame-Relay Link to Reach the TFTP Server

First, consider the remote end of the frame-relay link as the default gateway. Then, add a frame-relay map IP statement in the configuration with the IP address of that remote end and the dlci number needed to reach it.

Step 3   Verify that the selected Platform, Release, and Software Feature are correct by logging onto the Cisco homepage, then clicking Software Center under Service & Support. Next click Cisco IOS Software, then click the Upgrade Planner link.

Step 4   Establish a direct console session or virtual Telnet connection to the Catalyst 8540 MSR.

To prevent losing a Telnet connection during the reboot phase of this software installation (Step 11), use a direct console connection between the Catalyst 8540 MSR console port and the PC COM port.

Step 5   Launch the hyperterminal on the PC, using the following settings:

Step 6   To launch the Catalyst 8540 MSR into Rxboot mode, change the configuration register to the value 0x2101 as follows:

Note   If connected by Telnet and you lose the session following the reload, try again after a few minutes.

Step 7   Use the following sequence of commands to restore the previous configuration register value for the next reload. Replace the asterisks (****) with the configuration register value you recorded in Step 1 of this section:

Caution   Do not save anything while in boot mode. Avoid using the save commands (write mem or copy run start), and answer no to any question that suggests saving your current configuration. If you save data while in this mode, you can partially or completely erase your configuration.

The following example shows how to avoid using save commands:

Note   If you did not keep a copy of the configuration register in Step 4, use 0x2102 in the following step.

Step 8   Verify that the IP addresses of the TFTP server and the Catalyst 8540 MSR targeted for the TFTP software upgrade are in the same range. To do this, ping the TFTP server.

Step 9   Ping the Catalyst 8540 MSR from the TFTP server to verify that a network connection exists between them. See Step 2 in this section for detailed information on how to verify a network connection.

Caution   Cisco recommends that you keep a copy of the Catalyst 8540 MSR configuration before upgrading the Catalyst 8540 MSR software. At prompt, type copy startup tftp, then the host name or address of TFTP server.

Step 10   Copy the new software image from the TFTP server to the Catalyst 8540 MSR.

Step 11   Enter the IP address of the TFTP server as in the following example:

Step 12   Enter the filename of the Cisco IOS software image that you will install, as in the following example:

Source file name? c1600-y-l.112-18.P

Note   The image name varies depending on the file name of the image on the TFTP server.

Step 13   Specify the destination image filename.

This is the name that you call the new software image once loaded onto the Catalyst 8540 MSR. You can name the image anything. Common practice uses the UNIX image filename.

Step 14   Enter yes to erase the existing software image in the Catalyst 8540 MSR Flash memory before copying the new one. Or, enter no to keep the existing software image. Verify that you have enough memory to keep both.

The copying process takes several minutes; the time differs from network to network. During the transfer process, a list of the access files is displayed.

The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets were transferred successfully.

A checksum verification of the image occurs after the image is written to Flash memory. The Catalyst 8540 MSR reloads itself with the new image when the software upgrade is complete.

What to Check if I See "Text checksum verification failure" During the Copy

In both cases, a checksum failure indicates that the file has not been properly copied into the memory. Copy it again. Make sure that the file in the TFTP server is the same size as in the location where you got it.

Sometimes, you will see this behavior when the network is busy. Try again when the network is less busy, or try to establish a direct Ethernet connection between the TFTP server and the router to download the file.

What to Check if You Have the Error Message "error opening TFTP"

If you get the following problem, verify that the file is in the root directory of the TFTP server, and check again that you entered the correct filename. Be careful with I (capital i), l (small L), and 1(one) that could be mistaken. The example below shows the error message that you might see:

What to Check if You See a "Timeout" Error Message

Verify that the TFTP server is open on your PC. Make sure that the file is in the root directory by going to the menu bar and selecting View, then Options.

What to Check if You See the Error Message "can't open file"

Verify that the TFTP server is running on your computer. Make sure that you have copied the exact filename. Especially be careful with I (capital i), l (small L), and 1 (one) that could be mistaken.

Caution   Do not save anything while in boot mode. Avoid using the save commands (write mem or copy run start), and answer no to any question that suggests saving your current configuration. If you save data while in this mode, you can partially or completely erase your configuration. See Step 7 for an example.

Step 15   Before reloading, verify that the image is properly installed in Flash memory and that the Boot system commands point to the proper file to load. Then type the following commands:

Verify That You Stored the New Cisco IOS Image Properly

Use the command show flash to verify that you saved the file, that the size is correct, and that you don't have an invalid checksum. If the file does not appear, or if it appears followed by "[invalid checksum]", or if the size doesn't correspond to the file size on the TFTP server, you will need to start the procedure again. Go back to Step 1 in this section.

Tip Be aware that the router uses bytes and some TFTP servers use Kilobytes.

Verify That the Boot System Commands Are in the Right Order in the Configuration

The router stores and executes the boot system commands in the configuration file in the order that you enter them. If a boot system command entry in the list specifies an invalid device or filename, the router skips that entry.

Step 16   After the reload is complete, use the command show version to verify that the Catalyst 8540 MSR is now running with the desired Cisco IOS image. An example of the show version command follows:

Sample Session

Installation Procedure for RAM Images

Step 2   Ping the Catalyst 8540 MSR from the TFTP server to verify that a network connection exists between them. See Step 2 in the "Installation Procedure for Flash Images" section for detailed information on how to verify a network connection.

Step 3   Copy the new software image from the TFTP server to the Catalyst 8540 MSR:

Caution   Cisco recommends that you keep a copy of the Catalyst 8540 MSR configuration before upgrading the Catalyst 8540 MSR software. At prompt, type copy startup tftp, then the host name or address of the TFTP server.

Copying a System Image From One Device to Another

Here is a list of the possibilities (these may vary depending on your platform):

Below you can find the three most common system images and a detailed example:

Detailed example:

Step 4   Enter the IP address of the TFTP server as in the following example:

Step 5   Enter the filename of the Cisco IOS software image that you will install, as in the following example: Source file name? c2500-js-l_113-3.bin

Note   The image name varies depending on the filename of the image on the TFTP server.

Step 6   Specify the destination image filename.

This is the name that you call the new software image once it is loaded onto the Catalyst 8540 MSR. You can name the image anything. Common practice is to use the UNIX image filename.

Step 7   Enter yes to erase the existing software image in the Catalyst 8540 MSR Flash memory before copying the new one. Or, enter no to keep the existing software image. Verify that you have enough memory to keep both.

The copying process takes several minutes; the time differs from network to network. During the transfer process, a list of the access files is displayed.

The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets were transferred successfully.

A checksum verification of the image occurs after the image is written to Flash memory. The Catalyst 8540 MSR reloads itself with the new image when the software upgrade is complete.

What to Check if You See "Text checksum verification failure" During the Copy

In both cases, a checksum failure indicates that the file has not been properly copied into the memory. Copy it again. Make sure that the file in the TFTP server is the same size as in the location where you got it.

Sometimes, you will see this behavior when the network is busy. Try again when the network is less busy, or try to establish a direct ethernet connection between the TFTP server and the router to download the file.

What to Check if You Have the Error Message "error opening TFTP"

If you get the following error message, verify that the file is in the root directory of the TFTP server, and check again that you entered the correct filename. Be careful with I (capital i), l (small L), and 1(one) that could be mistaken. The example below shows the error message that you might see:

What to Check if You See a "Timeout" Error Message

Verify that the TFTP server is open on your PC. Make sure that the file is in the root directory by going to the menu bar and selecting View, then Options.

What to Check if You See the Error Message "can't open file"

After you complete the reload, the router should run the desired Cisco IOS image. Use the show version command to verify that the image is there. See Step 7 for detailed instructions on how to verify if the Cisco IOS image is stored properly and if the boot system commands are set correctly.

Caution   Do not save anything while in boot mode. Avoid using the save commands (write mem or copy run start), and answer no to any question that suggests saving your current configuration. If you save data while in this mode, you can partially or completely erase your configuration. See Step 7 for an example.

Step 8   Before reloading, verify that the image is properly installed in Flash memory and that the Boot system commands point to the proper file to load. Then type the following commands:

Verify That You Stored the New Cisco IOS Image Properly

Use the command show flash to verify that you saved the file, that the size is correct, and that you don't have an invalid checksum. If the file does not appear, or if it appears followed by "[invalid checksum]", or if the size doesn't correspond to the file size on the TFTP server, you will need to start the procedure again. Go back to Step 1 in this section.

Tip Be aware that the router uses bytes and some TFTP servers use Kilobytes.

Verify That the Boot System Commands Are in the Right Order in the Configuration

The router stores and executes the boot system commands in the configuration file in the order that you enter them. If a boot system command entry in the list specifies an invalid device or filename, the router skips that entry.

Step 9   After the reload is complete, use the command show version to verify that the <<router/access server>> is now running with the desired Cisco IOS image. An example of the show version command follows:

Configuration register is 0x2102

Sample Session

Related Documentation

The following sections describe the documentation available for the Catalyst 8540 MSR. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.

Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online on CCO and the Documentation CD-ROM only.

Use these release notes with the documents listed in the following sections:

Release-Specific Documents

The following documents are specific to Release12.0. They are located on CCO and the Documentation CD-ROM:

On CCO at:

Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Catalyst 8540 MSR Release Notes: Catalyst 8540 MSR Release 12.0 Documents: Catalyst 8540 MSR Release 12.0(10)W5(18) Documents: Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(10)W5(18c)

Platform-Specific Documents

These documents are available for the Catalyst 8540 MSR on CCO and the Documentation CD-ROM.

Platform Documents

Here is a list of the platform-specific documentation available for the Catalyst 8540 MSR:

Software Documents

Here is a list of the software documentation available for the Catalyst 8540 MSR:

You can access these documents on CCO at:

Cisco Product Documentation: ATM Adapters and Switches: Catalyst 8540 MSR Documents: Catalyst 8540 MSR Release W5 Documents: Catalyst 8540 MSR Release 12.0 Documents: Catalyst 8540 MSR Release 12.0(10)W5(18c) Documents

On the Documentation CD-ROM at:

ATM Adapters and Switches: Catalyst 8540 MSR Documents: Catalyst 8540 MSR Release 12.0 Documents: Catalyst 8540 MSR Release 12.0(10)W5(18c) Documents

Feature Modules

Feature modules describe new features supported by Release 12.0(10)W5(18c) and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the features modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.

You can access these documents on CCO at:

Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: New Feature Documentation

On the Documentation CD-ROM at:

Cisco IOS Software Configuration: Cisco IOS Release 12.0: New Feature Documentation

Cisco IOS Documentation Set

The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents, which are shipped with your order in electronic form on the Documentation CD-ROM—unless you specifically ordered the printed versions.

Documentation Modules

Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.

You can access these documents on CCO at:

Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS Release 12.0: Configuration Guides and Command References

You can access these documents on the Documentation CD-ROM at:

Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS Release 12.0: Configuration Guides and Command References

Release 12.0 Documentation Set

Table 5 describes the contents of the Cisco IOS Release 12.0 software documentation set, which is available in electronic form and also in printed form upon request.

Note   You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the paper documents were printed.

You can access the Cisco IOS documentation set on CCO at:

Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0

You can access the Cisco IOS documentation set on the Documentation CD-ROM at:

Cisco IOS Software Configuration: Cisco IOS Release 12.0

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtml  .

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO)  as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed documents, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO  in the following ways:

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Software Configuration Tips on the Cisco Technical Assistance Center Home Page

If you have a CCO log-in account, you can access the following URL, which contains links and tips on configuring your Cisco products:

http://www.cisco.com/kobayashi/technotes/serv_tips.shtml

This URL is subject to change without notice. If it changes, point your Web browser to CCO, press Login, and click on this path: Technical Assistance Center: Technical Tips.

The following sections are provided from the Technical Tips page:

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.

Posted: Fri Jan 17 16:27:06 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.