cc/td/doc/product/lan/cat5000/c5krn
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for
Catalyst 5000 Family RSM/VIP2 Cisco IOS 12.0 Software Releases

Release Notes for
Catalyst 5000 Family RSM/VIP2 Cisco IOS 12.0 Software Releases

September 11, 2000

Current Release:
12.0(13)

Previous Releases:
12.0(12), 12.0(11), 12.0(10), 12.0(9), 12.0(8), 12.0(7), 12.0(6), 12.0(5), 12.0(4), 12.0(3), 12.0(2), 12.0(1)

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.

These release notes for the Catalyst 5000 family Route Switch Module (RSM) and the optional Versatile Interface Processor 2 (VIP2) support Cisco IOS Release 12.0. These release notes are updated to describe new memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.

For a list of the software caveats that apply to Release 12.0(13), see Caveats for Cisco IOS Release 12.0 that accompanies these release notes. This caveats document is updated for every maintenance release and is located on Cisco Connection Online (CCO) and the Documentation CD-ROM.

Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.0 on CCO and the Documentation CD-ROM.

Note   The RSM ships with Cisco IOS software installed. However, before this module can run in your Catalyst 5000 family switch, be sure that the Catalyst 5000 family supervisor engine module is running supervisor engine software release 3.2(1) or later. A copy of release 3.2(1) or later is provided in the enclosed DOS floppy disk. Software images are also available with File Transfer Protocol (FTP) as described later in these notes.

Contents

This document consists of these sections:

System Requirements

This section describes the system requirements for Release 12.0:

Memory Recommendations

Table 1 describes the memory requirements of the Cisco IOS feature sets for Release 12.0.


Table 1: Memory Requirements for Catalyst 5000 Family RSM and VIP2
Image Name Software Name Required Flash Memory Required DRAM Memory Runs From

IP

c5rsm-isv-mz

16 MB

32 MB

RAM

IP IPSEC 40

c5rsm-isv40-mz

16 MB

32 MB

RAM

IP IPSEC 56

c5rsm-isv56i-mz

16 MB

32 MB

RAM

DESKTOP/IBM

c5rsm-dsv-mz

16 MB

32 MB

RAM

DESKTOP/IBM IPSEC 56

c5rsm-dsv56i-mz

16 MB

32 MB

RAM

DESKTOP/IBM IPSEC 40

c5rsm-dsv40-mz

16 MB

32 MB

RAM

ENTERPRISE/APPN

c5rsm-ajsv-mz

16 MB

32 MB

RAM

ENTERPRISE/APPN/IPSEC 40

c5rsm-ajsv40-mz

16 MB

32 MB

RAM

ENTERPRISE/APPN/IPSEC 56

c5rsm-ajsv56i-mz

16 MB

32 MB

RAM

ENTERPRISE/IBM/VIP

c5rsm-jsv-mz

16 MB

32 MB

RAM

ENTERPRISE IPSEC 40

c5rsm-jsv40-mz

16 MB

32 MB

RAM

ENTERPRISE IPSEC 56

c5rsm-jsv56i-mz

16 MB

32 MB

RAM

Hardware Supported

The following switches are supported in Release 12.0:

For detailed descriptions of the new hardware features for Release 12.0, see the Cross-Platform Release Notes for Cisco IOS Release 12.0.

Determining the Software Version

To determine the version of Cisco IOS software running on your Catalyst 5000 family RSM and VIP2, log in to the RSM and VIP2 and enter the show version EXEC command:

router> show version
Cisco Internetwork Operating System Software
IOS (tm) 5000 Software (c5rsm), Version 12.0(10), RELEASE SOFTWARE

Upgrading to a New Release

For general information about upgrading to a new software release, see the product bulletin "Cisco IOS Upgrade Ordering Instructions" on CCO located at:

http://www.cisco.com/warp/public/cc/cisco/mkt/ios/prodlit/957_pp.htm

New and Changed Information

These sections contain new and changed information for Release 12.0. For a list of software features that apply to previous releases, refer to the product documentation for the Cisco IOS Software Release for 12.0, which is available on CCO and on the Documentation CD-ROM.

New Features for the RSM/VIP2 in Release 12.0(13)

No new features were introduced for the RSM/VIP2 in Release 12.0(13).

Caveats

Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are the least serious.

For information on caveats in Cisco IOS Release 12.1, see "Caveats for Cisco IOS Release 12.1," which lists severity 1 and 2 caveats for Release 12.1 on CCO and the Documentation CD-ROM.

Open Caveats in Release 12.0(13) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(13).

Resolved Caveats in Release 12.0(13) for the RSM/VIP2

There following caveat is resolved caveats for the RSM/VIP2 in Release 12.0(13):

  VLAN0 on a Route Switch Module participates in Open Shortest Path First (OSPF) election. This problem is resolved in software release 12.0(13).

Open Caveats in Release 12.0(12) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(12).

Resolved Caveats in Release 12.0(12) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(12).

Open Caveats in Release 12.0(11) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(11).

Resolved Caveats in Release 12.0(11) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(11).

Open Caveats in Release 12.0(10) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(10).

Resolved Caveats in Release 12.0(10) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(10).

Open Caveats in Release 12.0(9) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(9).

Resolved Caveats in Release 12.0(9) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(9).

Open Caveats in Release 12.0(8) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(8).

Resolved Caveats in Release 12.0(8) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(8).

Open Caveats in Release 12.0(7) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(7).

Resolved Caveats in Release 12.0(7) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(7).

Open Caveats in Release 12.0(6) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(6).

Resolved Caveats in Release 12.0(6) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(6).

Open Caveats in Release 12.0(5) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(5).

Resolved Caveats in Release 12.0(5) for the RSM/VIP2

There are no resolved caveats for the RSM/VIP2 in Release 12.0(5).

Open Caveats in Release 12.0(4) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(4).

Resolved Caveats in Release 12.0(4) for the RSM/VIP2

The following caveats are resolved in Release 12.0(4):

  When tunneling IPX over an IP tunnel, and when using an extended inbound access list for IP on the tunnel interface, the IPX traffic gets blocked by the access list.
  Workaround. Add a "permit gre" statement in the extended access list.
  A group of related software bugs that create an undesired interaction between network address translation (NAT) and the input access list processing in certain Cisco routers running 12.0-based versions of Cisco IOS software has been resolved. Refer to the following URL for complete information:
  http://www.cisco.com/warp/public/770/iosnatacl-pub.shtml
  Packet errors can occur in the MAC address fields of packets that are input from any interface sharing the same MEMD packet-free pools with an Ethernet interface that is using any form of RSP turbo switching (optimum/flow/cef).
  Workaround. Use one of the following workarounds:

Open Caveats in Release 12.0(3) for the RSM/VIP2

There are no open caveats for the RSM/VIP2 in Release 12.0(3).

Resolved Caveats in Release 12.0(3) for the RSM/VIP2

This caveat is resolved in Release 12.0(3):

  If a User Datagram Protocol (UDP) packet with an invalid length is sent to port 514 (the syslog port) on an IOS device, the device will probably reload. In this situation, a stack trace might not be saved. These packets are sent by the popular nmap port-scanning program.
  Workaround. You can work around this situation by preventing any affected Cisco IOS device from receiving or processing UDP datagrams addressed to its port 514 by using packet filtering on surrounding devices or by using input access list filtering on the affected IOS device.
  If you use an input access list, that list should be applied to all interfaces to which attackers might be able to send datagrams. These interfaces include not only physical LAN and WAN interfaces, but virtual subinterfaces of those physical interfaces, and virtual interfaces or interface templates corresponding to GRE, L2TP, L2F, and other tunneling protocols. The input access list must block traffic destined for any of the Cisco IOS device's own IP addresses, as well as for any broadcast or multicast addresses on which the Cisco IOS device might be listening. You must remember to block older all-zeroes broadcasts as well as newer all-ones broadcasts. There is no single input access list that works in all configurations. You must understand the affect of your access list in your specific configuration before you activate the list. The following example shows a possible access list for a three-interface router, along with the configuration commands needed to apply that access list. (The example assumes no need for input filtering other than as a workaround for this situation.)
  ! Deny all multicasts, and all unspecified-net broadcasts, to port 514
  access-list 101 deny udp any 224.0.0.0 31.255.255.255 eq 514
  ! Deny old-style unspecified-net broadcasts
  access-list 101 deny udp any host 0.0.0.0 eq 514
  ! Deny network-specific broadcasts. This example assumes that all of
  ! the local interfaces are on the class B network 172.16.0.0, subnetted
  ! everywhere with mask 255.255.255.0. This will differ from network
  ! to network. Note that we block both new-style and old-style broadcasts.
  access-list 101 deny udp any 172.16.0.255 0.0.255.0 eq 514
  access-list 101 deny udp any 172.16.0.0 0.0.255.0 eq 514
  ! Deny packets sent to the addresses of our own network interfaces.
  access-list 101 deny udp any host 172.16.1.1 eq 514
  access-list 101 deny udp any host 172.16.2.1 eq 514
  access-list 101 deny udp any host 172.16.3.3 eq 514
  ! Permit all other traffic (default would be to deny)
  access-list 101 permit ip any any
  
  ! Apply the access list to the input side of each interface
  interface ethernet 0
  ip address 172.16.1.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 2
  ip address 172.16.2.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 3
  ip address 172.16.3.3 255.255.255.0
  ip access-group 101 in
  
  You might have difficulties listing all possible addresses, particularly all possible broadcast addresses, to which attack packets might be sent. If you do not expect to receive any legitimate syslog traffic on an interface, you might want to block all syslog traffic arriving on that interface. This procedure affects traffic routed through the Cisco IOS device as well as traffic destined to the device. Input access lists have an impact on system performance and should be installed with caution, especially on systems that are running close to their capacity limits.

Open Caveats in Release 12.0(2) for the RSM/VIP2

  This section describes the caveat and unexpected behavior for the RSM/VIP2 in Release 12.0(2).

CSCdk77426

  If a User Datagram Protocol (UDP) packet with an invalid length is sent to port 514 (the syslog port) on an IOS device, the device will probably reload. In this situation, a stack trace might not be saved. These packets are sent by the popular nmap port-scanning program.
  Workaround. You can work around this situation by preventing any affected Cisco IOS device from receiving or processing UDP datagrams addressed to its port 514 by using packet filtering on surrounding devices or by using input access list filtering on the affected IOS device.
  If you use an input access list, that list should be applied to all interfaces to which attackers might be able to send datagrams. These interfaces include not only physical LAN and WAN interfaces, but virtual subinterfaces of those physical interfaces, and virtual interfaces or interface templates corresponding to GRE, L2TP, L2F, and other tunneling protocols. The input access list must block traffic destined for any of the Cisco IOS device's own IP addresses, as well as for any broadcast or multicast addresses on which the Cisco IOS device might be listening. You must remember to block older all-zeroes broadcasts as well as newer all-ones broadcasts. There is no single input access list that works in all configurations. You must understand the effect of your access list in your specific configuration before you activate the list. The following example shows a possible access list for a three-interface router, along with the configuration commands needed to apply that access list. (The example assumes no need for input filtering other than as a workaround for this situation.)
  ! Deny all multicasts, and all unspecified-net broadcasts, to port 514
  access-list 101 deny udp any 224.0.0.0 31.255.255.255 eq 514
  ! Deny old-style unspecified-net broadcasts
  access-list 101 deny udp any host 0.0.0.0 eq 514
  ! Deny network-specific broadcasts. This example assumes that all of
  ! the local interfaces are on the class B network 172.16.0.0, subnetted
  ! everywhere with mask 255.255.255.0. This will differ from network
  ! to network. Note that we block both new-style and old-style broadcasts.
  access-list 101 deny udp any 172.16.0.255 0.0.255.0 eq 514
  access-list 101 deny udp any 172.16.0.0 0.0.255.0 eq 514
  ! Deny packets sent to the addresses of our own network interfaces.
  access-list 101 deny udp any host 172.16.1.1 eq 514
  access-list 101 deny udp any host 172.16.2.1 eq 514
  access-list 101 deny udp any host 172.16.3.3 eq 514
  ! Permit all other traffic (default would be to deny)
  access-list 101 permit ip any any
  
  ! Apply the access list to the input side of each interface
  interface ethernet 0
  ip address 172.16.1.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 2
  ip address 172.16.2.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 3
  ip address 172.16.3.3 255.255.255.0
  ip access-group 101 in
  
  You might have difficulties listing all possible addresses, particularly all possible broadcast addresses, to which attack packets might be sent. If you do not expect to receive any legitimate syslog traffic on an interface, you might want to block all syslog traffic arriving on that interface. This procedure affects traffic routed through the Cisco IOS device as well as traffic destined to the device. Input access lists have an impact on system performance and should be installed with caution, especially on systems that are running clost to their capacity limits.

Resolved Caveats in Release 12.0(2) for the RSM/VIP2

No caveats were resolved for the RSM/VIP2 in Release 12.0(2).

Open Caveats in Release 12.0(1a) for the RSM/VIP2

This section describes the caveat and unexpected behavior for the RSM/VIP2 in Release 12.0(1a).

  If a User Datagram Protocol (UDP) packet with an invalid length is sent to port 514 (the syslog port) on an IOS device, the device will probably reload. In this situation, a stack trace might not be saved. These packets are sent by the popular nmap port-scanning program.
  Workaround. You can work around this situation by preventing any affected Cisco IOS device from receiving or processing UDP datagrams addressed to its port 514 by using packet filtering on surrounding devices or by using input access list filtering on the affected IOS device.
  If you use an input access list, that list should be applied to all interfaces to which attackers might be able to send datagrams. These interfaces include not only physical LAN and WAN interfaces, but virtual subinterfaces of those physical interfaces, and virtual interfaces or interface templates corresponding to GRE, L2TP, L2F, and other tunneling protocols. The input access list must block traffic destined for any of the Cisco IOS device's own IP addresses, as well as for any broadcast or multicast addresses on which the Cisco IOS device might be listening. You must remember to block older all-zeroes broadcasts as well as newer all-ones broadcasts. There is no single input access list that works in all configurations. You must understand the effect of your access list in your specific configuration before you activate the list. The following example shows a possible access list for a three-interface router, along with the configuration commands needed to apply that access list. (The example assumes no need for input filtering other than as a workaround for this situation.)
  ! Deny all multicasts, and all unspecified-net broadcasts, to port 514
  access-list 101 deny udp any 224.0.0.0 31.255.255.255 eq 514
  ! Deny old-style unspecified-net broadcasts
  access-list 101 deny udp any host 0.0.0.0 eq 514
  ! Deny network-specific broadcasts. This example assumes that all of
  ! the local interfaces are on the class B network 172.16.0.0, subnetted
  ! everywhere with mask 255.255.255.0. This will differ from network
  ! to network. Note that we block both new-style and old-style broadcasts.
  access-list 101 deny udp any 172.16.0.255 0.0.255.0 eq 514
  access-list 101 deny udp any 172.16.0.0 0.0.255.0 eq 514
  ! Deny packets sent to the addresses of our own network interfaces.
  access-list 101 deny udp any host 172.16.1.1 eq 514
  access-list 101 deny udp any host 172.16.2.1 eq 514
  access-list 101 deny udp any host 172.16.3.3 eq 514
  ! Permit all other traffic (default would be to deny)
  access-list 101 permit ip any any
  
  ! Apply the access list to the input side of each interface
  interface ethernet 0
  ip address 172.16.1.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 2
  ip address 172.16.2.1 255.255.255.0
  ip access-group 101 in
  
  interface ethernet 3
  ip address 172.16.3.3 255.255.255.0
  ip access-group 101 in
  
  You might have difficulties listing all possible addresses, particularly all possible broadcast addresses, to which attack packets might be sent. If you do not expect to receive any legitimate syslog traffic on an interface, you might want to block all syslog traffic arriving on that interface. This procedure affects traffic routed through the Cisco IOS device as well as traffic destined to the device. Input access lists have an impact on system performance and should be installed with caution, especially on systems that are running close to their capacity limits.

Resolved Caveats in Release 12.0(1a) for the RSM/VIP2

No caveats were resolved for the RSM/VIP2 in Release 12.0(1a).

Supported Port Adapters

Table 2 lists the port adapters supported in Release 12.0.


Table 2: Supported Port Adapters on the RSM
Part Number Description

PA-4T+

4-Port Serial Port Adapter, Enhanced

PA-8T-V35

8-Port Serial, V.35 Port Adapter

PA-8T-232

8-Port Serial, 232 Port Adapter

PA-8T-X21

8-Port Serial, X.21 Port Adapter

PA-4R

4-Port Token Ring 4/16-Mbps Port Adapter

PA-4R-FDX

4-Port Token Ring 4/16-Mbps, Full-Duplex Port Adapter

PA-4T+

4-Port Serial, Enhanced

PA-F-MM

1-Port FDDI Multimode Port Adapter

PA-F-SM

1-Port FDDI Single-Mode Port Adapter

PA-F/FD-MM

1-Port FDDI Full Duplex Multimode Port Adapter

PA-F/FD-SM

1-Port FDDI Full Duplex Single-Mode Port Adapter

PA-A1-OC3SMI

1 Port ATM OC3 Single Mode Intermediate Reach Port Adapter

PA-A1-OC3MM

1-Port ATM OC3 Multimode Port Adapter

PA-2CT1/PRI

2-Port Channelized T1/PRI Port Adapter

PA-2CE1/PRI-75

2-Port Channelized E1/PRI Port Adapter, 75 Ohm

PA-2CE1/PRI-120

2-Port Channelized E1/PRI Port Adapter, 120 Ohm

SA-COMP/1

Service Adapter; Compression (64 VCs Stac)

SA-COMP/4

Service Adapter; Compression (256 VCs Stac)

PA-4E

4-Port Ethernet 10baseT Port Adapter

PA-8E

8-Port Ethernet 10baseT Port Adapter

PA-H, PA-2H

HSSI Port Adapter; can be used only in Catalyst 5500 chassis, two maximum

SA-ENCRYPT

Encryption Service Adapter

PA-FE-TX

Fast Ethernet Port Adapter

PA-FE-FX

Fast Ethernet Port Adapter

PA-A3-E3

1-Port ATM Enhanced E3 Port Adapter

PA-A3-T3

1-Port ATM Enhanced T3 Port Adapter

PA-A3-OC3MM

1-Port ATM Enhanced OC3c/STM1 Multimode Port Adapter

PA-A3-OC3SMI

1-Port ATM Enhanced OC3c/STM1 Single-Mode (IR) Port Adapter

PA-A3-OC3SML

1-Port ATM Enhanced OC3c/STM1 Single-Mode (LR) Port Adapter

PA-E3

1-Port E3 Serial Port Adapter with E3 DSU; can be used only in Catalyst 5500 chassis, two maximum

PA-2E3

2-Port E3 Serial Port Adapter with E3 DSU; can be used only in Catalyst 5500 chassis, two maximum

PA-T3

1-Port T3 Serial Port Adapter with T3 DSU; can be used only in Catalyst 5500 chassis, two maximum

PA- 2T3

2-Port T3 Serial Port Adapter with T3 DSU; can be used only in Catalyst 5500 chassis, two maximum

PA-5EFL

5-Port Ethernet 10baseFL Port Adapter

PA-POS-OC3MM

1-Port Packet/SONET OC3c/STM1 Multimode Port Adapter1

PA-POS-OC3SMI

1-Port Packet/SONET OC3c/STM1 Single-Mode (IR) Port Adapter1

PA-POS-OC3SML

1-Port Packet/SONET OC3c/STM1 Single-Mode (LR) Port Adapter1

1Supported as of Release 12.0(2)

Port Adapter Caveats

The following caveats apply to port adapters used in the Catalyst VIP2 module:

Related Documentation

The following sections describe the documentation available for Cisco 5000 family switches. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, and other documents. Documentation is available as printed manuals or electronic documents.

Use these release notes with these documents:

Release-Specific Documents

The following documents are specific to Release 12.0(12) and are located on CCO and the Documentation CD-ROM:

  On CCO at:
  Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0:
  On the Documentation CD-ROM at:
  Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Cross-Platform Release Notes for Cisco IOS Release 12.0
  Technical Documents
  Contains caveats applicable to all platforms for all maintenance releases of 12.0.
  On CCO at:
  Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Caveats: Caveats for Cisco IOS Release 12.0
  On the Documentation CD-ROM at:
  Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS 12.0: Caveats: Caveats for Cisco IOS Release 12.0
Note   If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on CCO at: Software Center: Cisco IOS Software: Cisco Bug Toolkit: Cisco Bugtool Navigator II or at http://www.cisco.com/support/bugtools.

Platform-Specific Documents

The following documents are available for the Catalyst 5000 family RSM/VIP2:

Feature Modules

Feature modules describe new features supported by Release 12.0(12) and are an update 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 feature modules are available online on CCO or the documentation CD-ROM. The feature module information is incorporated in the next printing of the Cisco IOS documentation set.

On CCO:

Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: New Feature Documentation

On the Documentation CD-ROM:

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

Cisco IOS Software Documentation Set

The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that 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, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. You can use each configuration guide in conjunction with its corresponding command reference.

On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.

On CCO at:

Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Configuration Guides and Command References

On the Documentation CD-ROM:

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

Release 12.0 Documentation Set

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

On CCO at:

Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0

On the Documentation CD-ROM:

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

The following documents provide current IOS information:

Documents Chapter Topics

  • Configuration Fundamentals Configuration Guide

  • Configuration Fundamentals Command Reference

Configuration Fundamentals Overview
Cisco IOS User Interfaces
File Management
System Management

  • Bridging and IBM Networking Configuration Guide

  • Bridging and IBM Networking Command Reference

Transparent Bridging
Source-Route Bridging
Token Ring Inter-Switch Link
Remote Source-Route Bridging
DLSw+
STUN and BSTUN
LLC2 and SDLC
IBM Network Media Translation
DSPU and SNA Service Point
SNA Frame Relay Access Support
APPN
Cisco Database Connection
NCIA Client/Server Topologies
Cisco Mainframe Channel Connection
Airline Product Set

  • Dial Solutions Configuration Guide

  • Dial Solutions Command Reference

X.25 over ISDN
Appletalk Remote Access
Asynchronous Callback, DDR, PPP, SLIP
Bandwidth Allocation Control Protocol
ISDN Basic Rate Service
ISDN Caller ID Callback
PPP Callback for DDR
Channelized E1 & T1
Dial Backup for Dialer Profiles
Dial Backup Using Dialer Watch
Dial Backup for Serial Lines
Peer-to-Peer DDR with Dialer Profiles
DialOut
Dial-In Terminal Services
Dial-on-Demand Routing (DDR)
Dial Backup
Dial-Out Modem Pooling
Large-Scale Dial Solutions
Cost-Control Solutions
Virtual Private Dialup Networks
Dial Business Solutions and Examples

  • Cisco IOS Interface Configuration Guide

  • Cisco IOS Interface Command Reference

Interface Configuration Overview
LAN Interfaces
Logical Interfaces
Serial Interfaces

  • Network Protocols Configuration Guide, Part 1

  • Network Protocols Command Reference, Part 1

IP Overview
IP Addressing and Services
IP Routing Protocols

  • Network Protocols Configuration Guide, Part 2

  • Network Protocols Command Reference, Part 2

AppleTalk
Novell IPX

  • Network Protocols Configuration Guide, Part 3

  • Network Protocols Command Reference, Part 3

Network Protocols Overview
Apollo Domain
Banyan VINES
DECnet
ISO CLNS
XNS

  • Security Configuration Guide

  • Security Command Reference

AAA Security Services
Security Server Protocols
Traffic Filtering and Firewalls
IP Security and Encryption
Passwords and Privileges
Neighbor Router Authentication
IP Security Options

  • Cisco IOS Switching Services Configuration Guide

  • Cisco IOS Switching Services Command Reference

Switching Services
Switching Paths for IP Networks
Virtual LAN (VLAN) Switching and Routing

  • Wide-Area Networking Configuration Guide

  • Wide-Area Networking Command Reference

Wide-Area Network Overview
ATM
Frame Relay
SMDS
X.25 and LAPB

  • Voice, Video, and Home Applications Configuration Guide

  • Voice, Video, and Home Applications Command Reference

Voice over IP
Voice over Frame Relay
Voice over ATM
Voice over HDLC
Frame Relay-ATM Internetworking
Synchronized Clocks
Video Support
Universal Broadband Features

  • Quality of Service Solutions Configuration Guide

  • Quality of Service Solutions Command Reference

Policy-Based Routing
QoS Policy Propagation via BGP
Committed Access Rate
Weighted Fair Queueing
Custom Queueing
Priority Queueing
Weighted Random
Early Detection
Scheduling
Signaling
RSVP
Packet Drop
Frame Relay Traffic Shaping
Link Fragmentation
RTP Header Compression

  • Cisco IOS Software Command Summary

  • Dial Solutions Quick Configuration Guide

  • System Error Messages

  • Debug Command Reference

 

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

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 docs, 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:

Language

E-mail Address

 English


 tac@cisco.com


 Hanzi (Chinese)


 chinese-tac@cisco.com


 Kanji (Japanese)


 japan-tac@cisco.com


 Hangul (Korean)


 korea-tac@cisco.com


 Spanish


 tac@cisco.com


 Thai


 thai-tac@cisco.com

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





hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Sep 11 10:34:52 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.