|
|
June 26, 2000
 |
Caution Use this publication if you have the Cisco IOS for the Catalyst 6000 Family Switches product, which runs Cisco IOS Release 12.1(2)E on both the supervisor engine and the MSFC. If you are running Catalyst software on the supervisor engine and Cisco IOS only on the MSFC, refer to the Release Notes for MSFC publication: http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm |
|
Caution The Cisco IOS for the Catalyst 6000 Family Switches product supports redundant supervisor engine configurations where the MSFC routers are identical: both MSFC1 or both MSFC2. If they are not identical, one will boot first and become active and hold the other supervisor engine and MSFC in a reset condition. |
This publication consists of these sections:
Cisco IOS Release 12.1(2)E supports the Cisco IOS for the Catalyst 6000 Family of Switches product on the Catalyst 6000 family switches. Release 12.1(2)E is an early deployment (ED) release based on Release 12.1(1). All functionality in Release 12.1(1) is also in Release 12.1(2)E. Release 12.1 E will eventually be merged into 12.1 T. All features and functionality in Release 12.0 XE and Release 12.1(1)E are in Release 12.1(2)E.
For information on Release 12.0(7)XE1, refer to the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE on CCO:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/78_10404.htm
or the Documentation CD-ROM.
For information on Release 12.1, refer to the Cross-Platform Release Notes for Cisco IOS Release 12.1 on CCO:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/xprn121/index.htm
and the Documentation CD-ROM.
For more information about the Cisco IOS software release process, refer to the Cisco IOS Software Releases: Product Bulletin #537 located on CCO:
http://www.cisco.com/warp/public/cc/cisco/mkt/ios/rel/prodlit/537_pp.htm
and on the Documentation CD-ROM.
This publication does not describe features that are available in Release 12.1, Release 12.1 T, or other Release 12.1 Early Deployment (ED) releases.
All caveats in Release 12.1(1), 12.0 XE, and 12.1(1)E are also in Release 12.1(2)E. For a list of the software caveats that apply to Release 12.1(2)E, see the "Caveats" section, the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE on CCO (URL shown above) and the Caveats for Cisco IOS Release 12.1 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/121cavs/121mcavs.htm
that accompany these release notes.
For general product information about the Catalyst 6000 family switches, refer to the Catalyst 4000, 5000, and 6000 Family Software Product Bulletin. For general information about the Catalyst 6000 12.1(2)E IOS Release, refer to the Product Bulletin at:
http://www.cisco.com/warp/public/cc/pd/si/casi/ca6000/prodlit/
This section describes the system requirements for Release 12.1(2)ES:
Release 12.1(2)E requires the following memory configurations:
Table 1 lists the supported hardware and minimum and recommended software versions.
| Product Number
(append with "=" for spares) | Product Description | Minimum Software Version | Recommended Software Version |
|---|---|---|---|
| Supervisor Engine 1 with MSFC1/MSFC2 | |||
WS-X6K-S1A-MSFC2 | Supervisor Engine 1 with ROMMON version 5.2(1) or later, | 12.1(2)E | 12.1(2)E |
WS-X6K-SUP1A-MSFC | Supervisor Engine 1with ROMMON release 5.2(1) or later, | 12.0(7)XE1 | 12.1(1)E |
| Ethernet, Fast Ethernet, and Gigabit Ethernet | |||
WS-X6416-GBIC | 16-Port Gigabit Ethernet GBIC1 | 12.1(2)E | 12.1(2)E |
WS-X6316-GE-TX | 16-port Gigabit Ethernet RJ-45 | 12.1(2)E | 12.1(2)E |
WS-X6416-GE-MT | 16-Port Gigabit Ethernet MT-RJ | 12.0(7)XE1 | 12.1(1)E |
WS-X6408A-GBIC | 8-Port Gigabit Ethernet GBIC | 12.0(7)XE1 | 12.1(1)E |
WS-X6408-GBIC | 8-Port Gigabit Ethernet GBIC | 12.0(7)XE1 | 12.1(1)E |
WS-X6324-100FX-MM | 24-port 100FX Ethernet Multimode MT-RJ | 12.1(2)E | 12.1(2)E |
WS-X6324-100FX-SM | 24-port 100FX Ethernet Multimode MT-RJ | 12.1(2)E | 12.1(2)E |
WS-X6224-100FX-MT | 24-Port 100FX Ethernet Multimode MT-RJ | 12.0(7)XE1 | 12.1(1)E |
WS-X6348-RJ-45 | 48-port 10/100TX RJ-45 Ethernet switching module | 12.1(2)E | 12.1(2)E |
WS-X6248-RJ-45 | 48-Port 10/100TX RJ-45 | 12.0(7)XE1 | 12.1(1)E |
WS-X6248A-TEL | 48-Port 10/100TX RJ-21 | 12.1(2)E | 12.1(2)E |
WS-X6248-TEL | 48-Port 10/100TX RJ-21 | 12.0(7)XE1 | 12.1(1)E |
WS-X6024-10FL-MT | 24-Port 10BASEFL MT-RJ | 12.0(7)XE1 | 12.1(1)E |
| Modular Chassis | |||
WS-C6509-NEB | Catalyst 6509-NEB chassis (9 vertically-oriented slots) | 12.1(2)E | 12.1(2)E |
WS-C6009 | Catalyst 6009 chassis (9 slots) | 12.0(7)XE1 | 12.1(1)E |
WS-C6509 | Catalyst 6509 chassis (9 slots) | 12.0(7)XE1 | 12.1(1)E |
WS-C6006 | Catalyst 6006 chassis (6 slots) | 12.0(7)XE1 | 12.1(1)E |
WS-C6506 | Catalyst 6506 chassis (6 slots) | 12.0(7)XE1 | 12.1(1)E |
| 1GBIC = Gigabit Interface Converter |
 |
Note The ATM modules (WS-X6101-OC12-MMF or WS-X6101-OC12-SMF), the Multilayer Switch Module (WS-X6302-MSM), and the FlexWAN module (WS-X6182-2PA) are not supported. These modules will remain powered down if detected in the system. They will not affect system behavior. |
Table 2 lists the feature sets supported in 12.1(2)E.
|
Note EGP, BGP4 and IS-IS routing protocols require the additional purchase of the InterDomain Routing Feature License (FR-IRC6). |
|
Note The image names reflect the supervisor engine and MSFC versions. For example, the c6sup11-js-mz.121-2.E image is for Supervisor Engine 1 with MSFC1 and the c6sup12-js-mz.121-2.E image is for Supervisor Engine 1 with MSFC2. |
| Feature Set | Image Filename | Orderable Product Number (Installed on System; |
|---|---|---|
IOS Release 12.1(2)E Enterprise:
| Supervisor engine 1/MSFC2: | SC6IOS12A-12.1.2E |
Supervisor engine 1/MSFC1: | SC6IOS11A-12.1.2E | |
IOS Release 12.1(2)E Desktop:
| Supervisor engine 1/MSFC2: | SC6IOS12B-12.1.2E |
Supervisor engine 1/MSFC1: | SC6IOS11B-11.1.2E | |
IOS Release 12.1(2)E IP:
| Supervisor engine 1/MSFC2: | SC6IOSC-12.1.2E |
Supervisor engine 1/MSFC1: | SC6IOSC-11.1.2E | |
IOS Release 12.1(2)E IP/IPX:
| Supervisor engine 1/MSFC2: | SC6IOS12D-12.1.2E |
Supervisor engine 1/MSFC1: | SC6IOS11D-12.1.2E | |
MSFC2 boot loader | c6msfc-boot2-mz.121-2.E.bin | N/A |
MSFC1 boot loader (available, but not required to support 12.1(2)E) | c6msfc-boot-mz.121-2.E.bin | N/A |
This section describes the new and changed information for the Cisco IOS for the Catalyst 6000 Family of Switches product:
Initial support for:
None.
None.
None.
Initial support of the Cisco IOS for the Catalyst 6000 Family of Switches product, which runs Cisco IOS on both the supervisor engine and the MSFC1.
Software release 12.1(2)E supports the following new features:
The Local Proxy ARP feature allows the MSFC to respond to ARP requests for IP addresses within a subnet where normally no routing is required. With the local proxy ARP feature enabled, the MSFC responds to all ARP requests for IP addresses within the subnet and forwards all traffic between hosts in the subnet. Use this feature only on subnets where hosts are intentionally prevented from communicating directly by the configuration on the switch to which they are connected.
The local proxy ARP feature is disabled by default. Use the ip local-proxy-arp interface configuration command to enable the local proxy ARP feature on an interface. Use the no ip local-proxy-arp interface configuration command to disable the feature. ICMP redirects are disabled on interfaces where the local proxy ARP feature is enabled.
The WCCP Layer 2 PFC Redirection feature allows directly connected Cisco Cache Engines to use Layer 2 redirection, which is more efficient than Layer 3 redirection via GRE encapsulation. A directly connected Cache Engine can be configured to negotiate use of the WCCP Layer 2 PFC Redirection feature. The WCCP Layer 2 PFC Redirection feature requires no configuration on the MSFC. The show ip wccp web-cache detail command displays which redirection method is in use for each cache. Observe the following guidelines:
Configure the Cisco IOS Web Cache Communication Protocol (WCCP) as described in the Cisco IOS Configuration Fundamentals Configuration Guide, under "Configuring Web Cache Services Using WCCP", at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/fun_c/fcprt3/fcd305.htm
These section describe the IOS Server Load Balancing enhancements:
|
Note The CISCO-SLB-MIB supports the SLB feature. |
If multiple load balancing devices are used, replacing the client IP address with an IP address associated with the load balancer results in proper routing of outbound traffic to the correct load balancer. Client Network Address Translation (NAT) also requires that you modify the ephemeral client port since many clients can use the same ephemeral port. This modification is important so that server NAT can be performed on the packet and important protocol events (such as TCP SYN, FIN, or RST) are seen by the load balancer connection finite state machine. Even in cases where multiple load balancers are not used, client NAT can ensure that packets from load-balanced connections are not routed around the load balancer.
|
Note The same connection supports server NAT and client NAT. |
The Hypertext Transfer Protocol (HTTP) probe allows you to monitor the applications being load balanced. Frequent probes can verify the operation of the application, not just connectivity to the application. The basic function of the HTTP probe is to determine the real server status by issuing an HTTP get or HTTP post against each real server in a server farm.
Since multiple virtual servers can use a single server farm, all virtual servers tied to that server farm are probe; if a real server failed for one virtual server, it must be failed for all virtual servers using that real server. If multiple probes detect the failure of a real server, all virtual servers must agree that the real server is recovered before that real server is restored to inservice.
Currently only one probe per server farm is allowed.
An IOS SLB could represent a point of failure and the servers could lose their connections to the backbone if power fails, or if a link from a switch to the distribution-layer switch is disconnected. IOS SLB supports two redundancy options you can use to reduce that risk: Hot Standby Router Protocol (HSRP) and stateful backup. Stateful backup enables SLB to incrementally back up its load balancing decisions, or "keep state," between primary and backup Layer 3 switches.
None.
None.
|
Note The spanning-tree portfast command bpdu-guard keyword has been replaced with the bpduguard keyword. The spanning-tree portfast command still accepts the bpdu-guard keyword. |
With the exception of the following list, all features currently supported by the Catalyst 5.x software are also supported in IOS Release 12.1(2)E:
Many of the above features will be supported in future IOS versions.
This section lists limitations and restrictions for the Cisco IOS for the Catalyst 6000 Family of Switches product.
|
Note When numerous protocol features (such as VTP pruning, EtherChannel, and RMON) are enabled concurrently, the number of supported logical spanning tree interfaces is reduced. To achieve these numbers, keep switched traffic off the management VLAN. |
This section describes troubleshooting guidelines for the Catalyst 6000 family switch configuration and is divided into the following subsections:
If you lose the boot loader image, please refer to the following link for boot loader image recovery procedures:
http://www.cisco.com/warp/customer/473/14.html
This section contains troubleshooting guidelines for system-level problems:
This section contains troubleshooting guidelines for module problems:
|
Note Catalyst 6000 family switches do not support ISL-encapsulated Token Ring frames. To support trunked Token Ring traffic in your network, make trunk connections directly between switches that support ISL-encapsulated Token Ring frames. When a Catalyst 6000 family switch is configured as a VTP server, you can configure Token Ring VLANs from the switch. |
Although DTP is a point-to-point protocol, some internetworking devices might forward DTP frames. To avoid connectivity problems that might be caused by a switch acting on these forwarded DTP frames, do the following:
The Spanning Tree Protocol (STP) blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, switches receive spanning tree bridge protocol data units (BPDUs) periodically from neighboring switches. You can configure the frequency with which BPDUs are received by entering the spanning-tree vlan vlan_ID hello-time command (the default frequency is set to 2 seconds). If a switch does not receive a BPDU in the time period defined by the spanning-tree vlan vlan_ID max-age command (20 seconds by default), the blocked port transitions to the listening state, the learning state, and to the forwarding state. As it transitions, the switch waits for the time period specified by the spanning-tree vlan vlan_ID forward-time command (15 seconds by default) in each of these intermediate states. Therefore, a blocked spanning tree interface moves into the forwarding state if it does not receive BPDUs from its neighbor within approximately 50 seconds.
|
Note We do not recommend using the UplinkFast feature on switches with more than 20 active VLANs. The convergence time might be unacceptably long with more than 20 active VLANs. |
Use the following guidelines to debug STP problems:
These sections describe conversion from Catalyst software to the Cisco IOS for the Catalyst 6000 Family Switches product:
|
Note The system configuration is lost during the conversion to IOS. Reconfigure the switch after the conversion. We strongly recommend that you back up your supervisor engine Catalyst OS and your MSFC IOS configurations (for example to a TFTP server) before you begin the conversion. The MSFC IOS configuration can be used as a basis for configuring the newly converted system. |
|
Caution Please note that you must follow this sequence exactly to successfully convert your system. Failure to follow these instructions exactly may result in an unusable system. See the "Feature Sets in Release 12.1(2)E" section for information about supported software images. Do not attempt these procedures with other software images. |
Perform these steps while the switch is running Catalyst software on the supervisor engine and IOS on the MSFC2:
Step 2 Copy the system configuration.
|
Note Do not store the copy in the bootflash: device, because you will format the supervisor engine bootflash: device in Step 14. |
Step 3 Copy the IOS system software image (for example, c6sup12-js-mz.121-2.E.bin or later) to a Flash PC card in slot0.
Step 4 Use the dir slot0: command to confirm that the Flash PC card in slot0: contains the IOS system software image you just copied.
Step 5 Set the configuration register to boot into ROMMON:
Console> (enable) set boot config-register 0x0 Configuration register is 0x0 ignore-config: disabled console baud: 9600 boot: the ROM monitor
Step 6 Session to the MSFC2:
Console> (enable) session 15
Step 7 Copy the MSFC2 configuration.
|
Note With the Cisco IOS for the Catalyst 6000 Family Switches product, an MSFC2 does not require a boot loader image in the MSFC2 bootflash: device to boot successfully. Catalyst software does require a boot loader image in the MSFC2 bootflash: device to boot successfully. To maintain compatibility with Catalyst software, keep the boot loader image in the MSFC2 bootflash: device. |
Step 8 Set the configuration register of the MSFC2 to autoboot:
Router# configure terminal Router(config)# config-register 0x2 Router(config)# end Router# 00:08:02: %SYS-5-CONFIG_I: Configured from console by console Router#
Step 9 Save the configuration:
Router# copy running-config startup-config Router#
Step 10 Return to the supervisor engine:
Router# exit
Step 11 Reset the switch:
Console> (enable) reset This command will reset the system.
|
Note Perform these steps while the supervisor engine is in ROMMON. |
Step 12 Verify that the switch has booted into supervisor engine ROMMON. Look for "System Bootstrap, Version 5.2(1)CSX" or later.
Step 13 At the supervisor engine ROMMON prompt, enter these commands:
rommon 1 > CONFIG_FILE= rommon 2 > sync rommon 3 > boot slot0:c6sup12-js-mz.121-2.E.bin
|
Note Perform these steps while the switch is running IOS on both the supervisor engine and the MSFC2. |
|
Note The show config command works reliably only after the first reload. |
Step 14 Format the supervisor engine bootflash: device:
Router# format sup-bootflash:
|
Note The sup-bootflash: device is not reliably usable until it has been formatted. |
Step 15 To autoboot an image stored in the supervisor engine bootflash: device, copy the system software image from slot0:
Router# copy slot0:c6sup12-js-mz.121-2.E.bin sup-bootflash:
Step 16 Configure the switch to autoboot the image:
|
Note To avoid boot failure, include the device name (slot0: or sup-bootflash:) in the following commands. |
Router(config)# boot system flash slot0:c6sup12-js-mz.121-2.E.bin
or:
Router(config)# boot system flash sup-bootflash:c6sup12-js-mz.121-2.E.bin
Step 17 Set the configuration register parameter to autoboot:
Router(config)# config-register 0x102
Step 18 Copy the running configuration to the startup configuration in NVRAM:
Router# copy running-config startup-config
Step 19 Reload the switch:
Router# reload
Step 20 When prompted, save the configuration.
Step 21 Configure the switch as described in the Catalyst 6000 Family IOS Software Configuration Guide.
|
Caution Please note that you must follow this sequence exactly to successfully convert your system. Failure to follow these instructions exactly may result in an unusable system. See the "Feature Sets in Release 12.1(2)E" section for information about supported software images. Do not attempt these procedures with other software images. |
Perform these steps while the switch is running Catalyst software on the supervisor engine and IOS on the MSFC1:
Step 2 Copy the system configuration.
|
Note Do not store the copy in the bootflash: device, because you will format the supervisor engine bootflash: device in Step 20. |
Step 3 Copy the IOS system software image (for example, c6sup11-js-mz.121-2.E.bin or later) to a Flash PC card in slot0.
Step 4 Use the dir slot0: command to confirm that the Flash PC card in slot0: contains the IOS system software image you just copied.
Step 5 Set the configuration register to boot into ROMMON:
Console> (enable) set boot config-register 0x0 Configuration register is 0x0 ignore-config: disabled console baud: 9600 boot: the ROM monitor
Step 6 Session to the MSFC1:
Console> (enable) session 15
Step 7 Copy the MSFC1 configuration.
Step 8 If the boot loader in the MSFC1 bootflash: device is earlier than 12.0(7)XE, copy the boot loader image (c6msfc-boot-mz.121-2.E.bin or later) to the MSFC1 bootflash: device.
Router# copy device:boot_loader_image bootflash:
Step 9 Use the dir bootflash: command to confirm that the MSFC1 bootflash: contains the IOS boot loader image.
|
Caution You must have a boot loader image in the MSFC1 bootflash: device to boot successfully. Do not reset the switch unless there is a boot loader image in the MSFC1 bootflash: device. If there is no boot loader image in the MSFC1 bootflash: device and the state of the switch does not support the copy command, see the "Recovering From Loss of the Boot Loader Image" section. |
Step 10 Set the configuration register of the MSFC1 to boot into ROMMON:
Router# configure terminal Router(config)# config-register 0x0 Router(config)# end Router# 00:08:02: %SYS-5-CONFIG_I: Configured from console by console Router#
Step 11 Return to the supervisor engine:
Router# exit
Step 12 Reset the switch:
Console> (enable) reset This command will reset the system.
|
Note Perform these steps while the switch is in ROMMON. |
Step 13 Verify that the switch has booted into supervisor engine ROMMON. Look for "System Bootstrap, Version 5.2(1)CSX" or later.
Step 14 At the supervisor engine ROMMON prompt, enter these commands:
rommon 1 > CONFIG_FILE= rommon 2 > sync rommon 3 > boot slot0:c6sup11-js-mz.121-2.E.bin
Step 15 Verify that the switch has booted into MSFC1 ROMMON. Look for "System Bootstrap, Version 12.0(3)XE."
Step 16 Use the BOOTLDR command to set the BOOTLDR environment variable to use the IOS boot loader image in the MSFC1 bootflash: device. For example:
rommon 1 > BOOTLDR=bootflash:c6msfc-boot-mz.121-2.E.bin
|
Note IOS boot loader versions earlier than 12.0(7)XE do not support the Cisco IOS for the Catalyst 6000 Family Switch product. |
Step 17 Use the sync command to save the environment variables you just configured to NVRAM so they are read on the next reset:
rommon 2 > sync
Step 18 Enter a reset command:
rommon 3 > reset
Step 19 Boot the MSFC1 with the same command used for the supervisor engine:
rommon 1 > boot slot0:c6sup11-js-mz.121-2.E.bin
|
Note The MSFC1 ROMMON dir command will not display the contents of slot0. |
|
Note Perform these steps while the switch is running IOS on both the supervisor engine and the MSFC1. |
|
Note The show config command works reliably only after the first reload. |
Step 20 Format the supervisor engine bootflash: device:
Router# format sup-bootflash:
|
Note The sup-bootflash: device is not reliably usable until it has been formatted. |
Step 21 Configure the MSFC1 to use the boot loader image:
Router(config)# boot bootldr bootflash:c6msfc-boot-mz.121-2.E.bin
Step 22 To autoboot an image stored in the supervisor engine bootflash: device, copy the system software image from slot0:
Router# copy slot0:c6sup11-js-mz.121-2.E.bin sup-bootflash:
Step 23 Configure the switch to autoboot the image:
|
Note To avoid boot failure, include the device name (slot0: or sup-bootflash:) in the following commands. |
Router(config)# boot system flash slot0:c6sup11-js-mz.121-2.E.bin
or:
Router(config)# boot system flash sup-bootflash:c6sup11-js-mz.121-2.E.bin
Step 24 Set the configuration register parameter to autoboot:
Router(config)# config-register 0x102
Step 25 Copy the running configuration to the startup configuration in NVRAM:
Router# copy running-config startup-config
Step 26 Reload the switch:
Router# reload
Step 27 When prompted, save the configuration.
Step 28 Configure the switch as described in the Catalyst 6000 Family IOS Software Configuration Guide.
This section describes updates to the Cisco IOS for the Catalyst 6000 Family of Switches product documentation. These changes will be included in the next update to the documentation.
Router# copy source_device:source_filename slaveslot0:target_filename
Router# copy source_device:source_filename slavesup-bootflash:target_filename
Router# copy source_device:source_filename slavebootflash:target_filename
These sections describe changes to the documentation:
See the online version of the Catalyst 6000 Family IOS Command Reference publication:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/cmdref/index.htm
for revised information about these commands:
To optimize server-to-server performance, you can configure the MTU size on Gigabit Ethernet interfaces to support jumbo frames.
The jumbo frame feature supports only a single larger-than-default MTU size on the switch. Configuring a Gigabit Ethernet interface with an MTU size greater than the default automatically configures all other interfaces and EtherChannels with MTU sizes greater than the default to the newly configured size. Interfaces that have not been changed from the default are not affected.
Observe the following guidelines when configuring the jumbo frame feature:
To configure the MTU value, perform this task:
| Step | Command | Purpose |
|---|---|---|
1. | Router(config)# interface gigabitethernet slot/interface | Access Gigabit Ethernet interface configuration mode. |
2. | Router(config-if)# mtu mtu_size | Set the MTU size. Valid values are from 1500 to 10240 bytes. |
3. | Router# show interface gigabitethernet 1/2 | Verify the configuration. |
This example shows how to set the MTU size on a Gigabit Ethernet interface and verify the configuration:
Router(config)# interface gigabitethernet 1/2 Router(config-if)# mtu 10240 Router(config-if)# end Router# show interface gigabitethernet 1/2 GigabitEthernet1/2 is administratively down, line protocol is down Hardware is C6k 1000Mb 802.3, address is 0030.9629.9f88 (bia 0030.9629.9f88) MTU 10240 bytes, BW 1000000 Kbit, DLY 10 usec, <...Output Truncated...> Router#
|
Note Currently 10240 is the supported maximum MTU size, but this maximum size may change in future releases. |
The following sections describe the documentation available for the Cisco IOS for the Catalyst 6000 Family of Switches product. 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.
Use these release notes with these documents:
The following documents are specific to Release 12.1 and are located on CCO and the Documentation CD-ROM:
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to CCO and press Login. Then go to Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools. |
The following documents are available for the Catalyst 6000 family switches running the Cisco IOS for the Catalyst 6000 Family of Switches product:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/index.htm
Feature modules describe new features supported by Release 12.1(1) 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.1: New Feature Documentation
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1
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.
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.1: Configuration Guides and Command References
On the Documentation CD-ROM:
Cisco Products Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
The following table describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form ordered.
|
Note 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 hard-copy documents were printed. |
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
| Books | Major Topics |
|---|---|
| Cisco IOS User Interfaces |
| Using Cisco IOS Software |
| Preparing for Dial Access |
| Interface Configuration Overview |
| IP Addressing and Services |
| AppleTalk and Novell IPX Overview |
| Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Overview |
| Multiservice Applications Overview |
| Quality of Service Overview |
| Security Overview |
| Cisco IOS Switching Services Overview |
| Wide-Area Networking Overview |
|
|
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.
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.
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).
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 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.
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 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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.
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: Thu Sep 21 12:00:41 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.