Table of Contents

Contents
System Requirements

Memory Requirements
Supported Hardware
Unsupported Hardware
Supported Features
Unsupported Features

New and Changed Information

New Hardware Features in Release 12.1(11b)EW
New Software Features in Release 12.1(11b)EW
New Hardware Features in Release 12.1(8a)EW
New Software Features in Release 12.1(8a)EW

Upgrading the System Software

Upgrading the Supervisor Engine III ROMMON and the Cisco IOS Software
Upgrading the Supervisor Engine III ROMMON
Upgrading the Cisco IOS Software

Limitations and Restrictions
Caveats

Open Caveats in Software Release 12.1(11b)EW1
Resolved Caveats in Software Release 12.1(11b)EW1
Open Caveats in Software Release 12.1(11b)EW
Resolved Caveats in Software Release 12.1(11b)EW
Open Caveats in Software Release 12.1(8a)EW1
Resolved Caveats in Software Release 12.1(8a)EW1
Open Caveats in Software Release 12.1(8a)EW
Resolved Caveats in Software Release 12.1(8a)EW

Troubleshooting

Recovering from Loss of the Boot Loader Image
Troubleshooting at the System Level
Troubleshooting Modules
Troubleshooting VLANs
Troubleshooting Spanning Tree
Troubleshooting MIBs

Documentation Updates for Release 12.1(8a)EW

Changes
Omissions

Related Documentation

Release-Specific Publications
Platform-Specific Publications
Cisco IOS Software Documentation Set

Documentation Modules
Release 12.1 Documentation Set

Obtaining Documentation

World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback

Obtaining Technical Assistance

Cisco.com
Technical Assistance Center

Cisco TAC Web Site
Cisco TAC Escalation Center

Release Notes for the Catalyst 4006 Switch with Supervisor Engine III, Cisco IOS Release 12.1(11b)EW1

Product Numbers:

• S4KL3-12111EW1—Cisco IOS for the Catalyst 4000, Release 12.1(11b)EW1

• S4KL3E-12111EW1—Cisco IOS for the Catalyst 4000, enhanced Layer 3 software image including OSPF, IGRP and EIGRP, Release 12.1(11b)EW1

• S4KL3-12108EW1—Cisco IOS for the Catalyst 4000, Release 12.1(8a)EW1

• S4KL3E-12108EW1—Cisco IOS for the Catalyst 4000, enhanced Layer 3 software image including OSPF, IGRP and EIGRP, Release 12.1(8a)EW1

Current Release
12.1(11b)EW1—July 23, 2002

Previous Releases
12.1(8a)EW1

Deferred Releases
12.1(11b)EW, 12.1(8a)EW

These release notes describe the features, modifications, and caveats for the Cisco IOS software on the Catalyst 4006 switch with Supervisor Engine III. The most current software release is version 12.1(11b)EW1.

The most current release notes for 12.1(11b)EW1 are available on Cisco.com at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_1_11/OL_2170.htm

Contents

This publication consists of these sections:

• System Requirements

• New and Changed Information

• Upgrading the System Software

• Limitations and Restrictions

• Caveats

• Troubleshooting

• Documentation Updates for Release 12.1(8a)EW

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

System Requirements

This section describes the system requirements:

• Memory Requirements

• Supported Hardware

• Unsupported Hardware

• Supported Features

• Unsupported Features

Memory Requirements

These are the required memory configurations for Cisco IOS on the Catalyst 4006 with Supervisor Engine III:

• 256-MB SDRAM DIMM

• 64-MB Flash SIMM

Supported Hardware

Unsupported Hardware

Cisco IOS for the Catalyst 4000 family runs only on the Catalyst 4006 with Supervisor Engine III. You cannot load Cisco IOS for the Catalyst 4000 family on any other Catalyst 4000 family switch or supervisor engine.

The following hardware is not supported:

• WS-X4232-L3—Catalyst 4000 Layer 3 Services module

If detected, the module remains powered down and has no effect on system behavior.

• WS-X4604-GWY—Catalyst 4000 Access Gateway module

If detected, the module remains powered down and has no effect on system behavior.

• The Fast Ethernet port on the supervisor module is inoperable in Cisco IOS release 12.1(11b)EW.

An Ethernet cable plugged into the Fast Ethernet port is active only in ROMMON mode.

Supported Features

Table 1 lists the software features for the Catalyst 4006 with Supervisor Engine III running Cisco IOS.

Unsupported Features

The following features are not supported in Cisco IOS Release 12.1(11b)EW for the Catalyst 4006 with Supervisor Engine III:

• Secure access via secure shell (SSH)

• Access control using authorization and accounting

• Kerberos support for access control

• HTTP server

• Community VLANs and two-way community VLANs in private VLANs

• MAC-layer Cisco IOS access control lists (ACLs)

• VLAN ACLs (VACLs; wire-rate ACLs are supported)

• VLAN Management Policy Server (VMPS) client or server

• Remote SPAN (RSPAN)

• Port security

• The following ACL types are not supported:

  • Standard XNS access list

  • Extended XNS access list

  • DECnet access list

  • Extended MAC address access list

  • Protocol type-code access list

  • Standard IPX access list

  • Extended IPX access list

Many of the above features will be supported in future Cisco IOS versions.

New and Changed Information

These sections describe the new and changed information for the Catalyst 4006 with Supervisor Engine III running Cisco IOS:

• New Hardware Features in Release 12.1(11b)EW

• New Software Features in Release 12.1(11b)EW

• New Hardware Features in Release 12.1(8a)EW

• New Software Features in Release 12.1(8a)EW

New Hardware Features in Release 12.1(11b)EW

Release 12.1(11b)EW provides initial support of the Cisco IOS software for the Catalyst 4006 switch with Supervisor Engine III and the following modules:

• WS-X4148-RJ45V—48-port inline power 10/100BASE-TX switching module with inline power support

• WS-X4095-PEM—Catalyst 4000 DC Power Entry Module

• WS-P4603-2PSU—Catalyst 4000 Auxiliary Power Shelf (3-slot) including two WS-X4608 power supplies

• WS-X4608—Catalyst 4603 Power Supply Unit for WS-P4603

New Software Features in Release 12.1(11b)EW

Release 12.1(11b)EW provides initial support of the Cisco IOS for the Catalyst 4006 switch with Supervisor Engine III.

• For more information on the following features, refer to these publications:

  • Software Configuration Guide for the Catalyst 4006 Switch with Supervisor Engine III at the following URL:

  http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_1_11/config/index.htm
  

  • Command Reference for the Catalyst 4006 Switch with Supervisor Engine III at the following URL:

  http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_1_11/command/index.htm
  

Release 12.1(11b)EW provides these features:

• Multiple VLAN access port

• Inline power management for Cisco IP phones and Aironet 350 Wireless Access Points on the WS-X4148-RJ45V module.

• Power redundancy

• Multicast flooding suppression for STP changes

• IGMP filtering

New Hardware Features in Release 12.1(8a)EW

Release 12.1(8a)EW provides initial support of the Cisco IOS software for the Catalyst 4006 switch with Supervisor Engine III and the following modules:

• WS-X4124-FX-MT—24-port 100BASE-FX Fast Ethernet switching module

• WS-X4148-FX-MT—48-port 100BASE-FX Fast Ethernet switching module

• WS-X4148-RJ—48-port 10/100 Fast Ethernet RJ-45 switching module

• WS-X4148-RJ21—48-port 10/100-Mbps Fast Ethernet RJ-21 (telco connector) switching module

• WS-X4148-RJ45V—48-port inline power 10/100BASE-TX switching module: data traffic only (inline power not supported in Cisco IOS software release 12.1(8a)EW)

• WS-X4232-GB-RJ—32-port 10/100 Fast Ethernet RJ-45, plus 2-port 1000BASE-X (GBIC) Gigabit Ethernet switching module

• WS-X4232-RJ-XX—32-port 10/100 Fast Ethernet RJ-45 modular uplink switching module

• WS-X4306-GB—6-port 1000BASE-X (GBIC) Gigabit Ethernet switching module

• WS-X4418-GB—18-port 1000BASE-X (GBIC) Gigabit Ethernet switching module

• WS-X4412-2GB-T—12-port 1000BASE-T Gigabit Ethernet and 2-GBIC ports switching module

• WS-X4424-GB-RJ45—24-port 10/100/1000BASE-T Gigabit Ethernet switching module

• WS-X4448-GB-LX—48-port 1000BASE-LX Gigabit Ethernet Fiber Optic interface switching module

• WS-X4448-GB-RJ45—48-port 10/100/1000BASE-T Gigabit Ethernet switching module

New Software Features in Release 12.1(8a)EW

Release 12.1(8a)EW provides initial support of the Cisco IOS for the Catalyst 4006 switch with Supervisor Engine III.

• For more information on the following features, refer to these publications:

  • Software Configuration Guide for the Catalyst 4006 Switch with Supervisor Engine III at the following URL:

  http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_18a/config/index.htm
  

  • Command Reference for the Catalyst 4006 Switch with Supervisor Engine III at the following URL:

  http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_18a/command/index.htm
  

Release 12.1(8a)EW provides these features:

• The Layer 2 features are as follows:

  ---

  Note   The following chapter references are for the Software Configuration Guide for the Catalyst 4006 Switch with Supervisor Engine III.

  ---

  • Layer 2 switch ports and VLAN trunks with the Dynamic Trunking Protocol (DTP) (refer to the "Configuring Layer 2 Ethernet Interfaces" chapter)

  • VLANs (refer to the "Understanding and Configuring VLANs" chapter)

  • Private VLANs (refer to the "Understanding and Configuring Private VLANs" chapter)

  • VLAN Trunk Protocol (VTP) and VTP domains (refer to the "Understanding and Configuring VTP" chapter)

  • Spanning Tree Protocol (refer to the "Understanding and Configuring STP" chapter)

  • Spanning tree PortFast, UplinkFast, and BackboneFast (refer to the "Configuring STP Features" chapter)

  • IGMP snooping (refer to the "Understanding and Configuring IGMP Snooping" chapter)

• Cisco Express Forwarding for IP unicast traffic (refer to the "Configuring CEF" chapter)

• Standard Domain Naming System (DNS) support (refer to the Cisco IOS Network Protocols Configuration Guide, Part 1, and the Cisco IOS Network Protocols Command Reference, Part 1)

• Dynamic Host Configuration Protocol (DHCP); (refer to Cisco IOS IP and IP Routing Configuration Guide, Release 12.1, "Configuring DHCP")

• Bootstrap Protocol (BOOTP) relay (refer to the Cisco IOS Network Protocols Configuration Guide, Part 1, and the Cisco IOS Network Protocols Command Reference, Part 1)

• Cisco Discovery Protocol (CDP); (refer to the "Understanding and Configuring CDP" chapter)

• Standard IP access control lists (ACLs) at wire rate (refer to the "Configuring Network Security" chapter)

• The Layer 3 features are as follows:

  • Layer 3 routing protocols (refer to the Cisco IOS Network Protocols Configuration Guides, Parts 1 and 2, and the Cisco IOS Network Protocols Command Reference, Parts 1 and 2):

  Static IP routing
  IP routing protocols
  IP multicast routing protocols
  

  • Layer-3 related protocols (refer to the Cisco IOS Release 12.1 Network Protocols Configuration Guides, Parts 1 and 2, and the Cisco IOS Release 12.1 Network Protocols Command Reference, Parts 1 and 2):

  Internet Group Management Protocol (IGMP) v1 and v2
  Cisco Group Multicast Protocol (CGMP) server support
  Full Internet Control Message Protocol (ICMP) support
  ICMP Router Discovery Protocol (IRDP)
  Multicast Source Discovery Protocol (MSDP)
  Multicast Border Gateway Protocol (MBGP)
  

• Multiple-Hot Standby Routing Protocol (M-HSRP; refer to "Hot Standby Router Protocol" in the Cisco IOS Network Protocols Configuration Guide, Part 1, and the Cisco IOS Network Protocols Command Reference, Part 1)

• Access control using several supported authentication methods (refer to the "Configuring the Switch for the First Time" chapter)

• Switched Port Analyzer (SPAN); (refer to the "Understanding and Configuring SPAN" chapter)

• Quality of Service (QoS); (refer to the "Understanding and Configuring QoS" chapter)

Upgrading the System Software

If you have a Catalyst 4006 switch with Supervisor Engine III running Cisco IOS 12.1(8a)EW1 or earlier, and you want to upgrade your switch to Cisco IOS 12.1(11b)EW, you must upgrade the Supervisor Engine III ROMMON version to at least 12.1(11br)EW in addition to upgrading the Cisco IOS software.

• Upgrading the Supervisor Engine III ROMMON and the Cisco IOS Software

• Upgrading the Supervisor Engine III ROMMON

• Upgrading the Cisco IOS Software

Upgrading the Supervisor Engine III ROMMON and the Cisco IOS Software

This section describes how to upload the ROMMON software and the Cisco IOS software on your switch in a single procedure. If this process fails, upgrade your ROMMON software as described in "Upgrading the Supervisor Engine III ROMMON" section and then upgrade your Cisco IOS software as described in "Upgrading the Cisco IOS Software" section.

Caution   To avoid actions that might make your system unbootable, please read this entire section before starting the upgrade.

To upgrade the ROMMON software and Cisco IOS software on you switch follow this procedure:

The cat4000-sup3-promupgrade-121_11br_EW programs are available at the same location on Cisco.com where you download Catalyst 4000 system images.

Step 2   Download the Cisco IOS software version 12.1(11b)EW image from Cisco.com and place it on a TFTP server in a directory that is accessible from the supervisor to be upgraded.

Step 3   Use the dir bootflash: command to ensure that there is sufficient space in Flash to store the promupgrade image and the Cisco IOS software image. If there is insufficient space, delete one or more images and then enter the squeeze bootflash: command to reclaim the space.

If you're using a Compact Flash card, use slot0: instead of bootflash:.

Step 4   Download the cat4000-sup3-promupgrade-121_11br_EW program into Flash memory using the copy tftp command.

The following example shows how to download the promupgrade image cat4000-sup3-promupgrade-121_11br_EW from the remote host 172.20.58.78 to bootflash:

Step 5   Download the software image into Flash memory using the copy tftp command.

The following example shows how to download the Cisco IOS software image cat4000-is-mz.121-11b.EW from the remote host 172.20.58.78 to bootflash:

Step 6   Use the show bootvar command to display the files specified in the BOOT variable.

The following example shows how to display the contents of the BOOT variable.

Switch# show bootvar

Switch#

Step 7   Enter the no boot system flash bootflash:file_name command to clear the BOOT variable.

The following example shows how to clear the cat4000-is-mz.121-8a.EW file and save the BOOT variable.

Step 8   Use the show bootvar command to verify that BOOT variable is empty.

The following example shows an empty the BOOT variable.

Switch# show bootvar

Step 9   Use the boot system flash command to add the cat4000-sup3-promupgrade-121_11br_EW program and the Cisco IOS software image to the BOOT variable.

The following example shows how to add the cat4000-sup3-promupgrade-121_11br_EW program and the cat4000-is-mz.121-11b.EW image to the BOOT variable.

Step 10   Use the show bootvar command to verify that the BOOT variable contains the promupgrade image and Cisco IOS image, and that the configuration register is set to 0x2102. If the configuration register is not set to 0x2102, proceed to step 11. If the configuration register is set to 0x2102, proceed to step 12.

The following example shows that the cat4000-sup3-promupgrade-121_11br_EW program and the cat4000-is-mz.121-11b.EW image are in the BOOT variable and that the configuration register is set to 0x21020.

Switch#

Step 11   Use the configure-register command to set the configuration register to 0x2102.

The following example show how to set the second least significant bit in the configuration register.

Step 12   Enter the reload command to reboot and upgrade the switch. The switch upgrades the ROMMON and boots the new Cisco IOS image.

Caution   The upgrade and reboot may require up to 15 minutes to complete. Do not disturb your switch during this process. If the process fails during the reboot, you must upgrade the ROMMON (as described in the "Upgrading the Supervisor Engine III ROMMON" section) and then upgrade the Cisco IOS software (as described in "Upgrading the Cisco IOS Software" section).

The following example shows the output from the upgrade and reboot.

Switch#

Step 13   After the switch has booted, use the show version command to confirm the ROMMON and Cisco IOS versions. If the ROMMON or Cisco IOS versions are incorrect, you must upgrade the ROMMON (as described in the "Upgrading the Supervisor Engine III ROMMON" section), and then upgrade the Cisco IOS software (as described in "Upgrading the Cisco IOS Software" section).

In the following example, the ROMMON level is 12.1(11br)EW, and the Cisco IOS version 12.1(11b)EW.

Step 14   Use the delete command to delete the promupgrade program from bootflash: and the squeeze bootflash: command to reclaim unused space.

The following example shows how to delete the cat4000-sup3-promupgrade-121_11br_EW image from bootflash: and reclaim unused space.

Step 15   Use the no boot system flash command to delete the cat4000-sup3-promupgrade-121_11br_EW image from the BOOT variable.

The following example shows how to delete the cat4000-sup3-promupgrade-121_11br_EW image from the BOOT variable.

Step 16   Use the show bootvar command to verify that the BOOT variable contains only the Cisco IOS software image.

The following example shows that the BOOT variable contains only the Cisco IOS image cat4000-is-mz.121-11b.EW.

Upgrading the Supervisor Engine III ROMMON

Caution   To avoid actions that might make your system unbootable, please read this entire section before starting the upgrade.

If you have a Catalyst 4006 switch with Supervisor Engine III running Cisco IOS 12.1(8a)EW1 or earlier, and you want to upgrade your switch to Cisco IOS 12.1(11b)EW, you must upgrade the Supervisor Engine III ROMMON version to at least 12.1(11br)EW. When you upgrade and boot the Cisco IOS software to 12.1(11b)EW, the FPGA is automatically upgraded.

Note   This version of ROMMON has an important limitation: Only one image should be specified in the BOOT variable.

Follow this procedure to upgrade your Supervisor Engine III ROMMON to 12.1(11br)EW:

Note   This section assumes that the console baud rate is set to 9600 (default). If you want to use a different baud rate, change the configuration register value for your switch.

Step 2   Download the cat4000-sup3-promupgrade-121_11br_EW program from Cisco.com and place it on a TFTP server in a directory that is accessible from the switch to be upgraded.

The cat4000-sup3-promupgrade-121_11br_EW programs are available at the same location on Cisco.com where you download Catalyst 4000 system images.

Step 3   Use the dir bootflash: command to ensure that there is sufficient space in Flash to store the promupgrade image. If there is insufficient space, delete one or more images and then enter the squeeze bootflash: command to reclaim the space.

If you're using a Compact Flash card, use slot0: instead of bootflash:.

Step 4   Download the cat4000-sup3-promupgrade-121_11br_EW program into Flash memory using the copy tftp command.

The following example shows how to download the promupgrade image cat4000-sup3-promupgrade-121_11br_EW from the remote host 172.20.58.78 to bootflash:

Step 5   Enter the reload command to reset the switch and press Ctrl-C to stop the boot process and re-enter ROMMON.

The following example shows the output after a reset into ROMMON.

Step 6   Run the prompupgrade program by entering the boot bootflash:cat4000-sup3-promupgrade-121_11br_EW command.

Caution   No intervention is necessary to complete the upgrade. To ensure a successful upgrade, do not interrupt the upgrade process. Do not perform a reset, power cycle, OIR of the supervisor, etc., for at least five minutes.

The following example shows the output from a successful upgrade followed by a system reset.

Step 7   Enter the show version command to verify that the ROMMON upgraded to 12.1(11r)EW.

Step 8   Use the delete command to delete the promupgrade program from bootflash and the squeeze command to reclaim unused space.

The following example shows how to delete the cat4000-sup3-promupgrade-121_11br_EW image from bootflash and reclaim unused space.

The ROMMON is now upgraded.

See the "Upgrading the Cisco IOS Software" section for instructions on upgrading the Cisco IOS software on your switch.

Upgrading the Cisco IOS Software

You can upgrade the Cisco IOS software on your Catalyst 4006 switch with Supervisor Engine III using the following procedure.

If you have Cisco IOS software release 12.1(8a)EW loaded on your switch, you must upgrade the ROMMON before upgrading your switch software. For more information, see the "Upgrading the Supervisor Engine III ROMMON" section.

Caution   To avoid actions that might make your system unbootable, please read this entire section before starting the upgrade.

Step 2   Use the dir bootflash: command to ensure that there is sufficient space in Flash memory to store the promupgrade image. If there is insufficient space, delete one or more images and then enter the squeeze bootflash: command to reclaim the space.

If you're using a Compact Flash card, use slot0: instead of bootflash:.

Step 3   Download the software image into Flash memory using the copy tftp command.

The following example shows how to download the Cisco IOS software image cat4000-is-mz.121-11b.EW from the remote host 172.20.58.78 to bootflash:

Step 4   Use the no boot system flash command to clear the BOOT variable.

Step 5   Use the boot system flash command to add the Cisco IOS software image to the BOOT variable.

The following example shows how to add the cat4000-is-mz.121-11b.EW image to the BOOT variable.

Switch# configure terminal Switch(config)# boot system flash bootflash:cat4000-is-mz.121-11b.EW Switch(config)# exit Switch# write Building configuration... Compressed configuration from 3641 to 1244 bytes [OK] Switch#

Step 6   Use the configure-register command to set the configuration register to 0x2102.

The following example show how to set the second least significant bit in the configuration register.

Switch# configure terminal Switch(config)# configure-register 0x2102 Switch(config)# exit Switch# write Building configuration... Compressed configuration from 3723 to 1312 bytes [OK] Switch#

Step 7   Enter the reload command to reset the switch and load the software.

---

Caution   No intervention is necessary to complete the upgrade. To ensure a successful upgrade, do not interrupt the upgrade process by performing a reset, power cycle, OIR of the supervisor, etc., for at least five minutes!

---

The following example shows the output from a successful upgrade followed by a system reset.

Switch#reset Rommon reg: 0x2B004180 Upgrading FPGA... Decompressing the image ############## [OK] ********************************************************** * * * Yoda FPGA Upgrade Utility For WS-X4014 Machines * * * * Copyright (c) 2002 by Cisco Systems, Inc. * * All rights reserved. * * * ********************************************************** Image size = 483.944 KBytes Maximum allowed size = 1023.75 KBytes Upgrading your FPGA image... DO NOT RESET the system unless instructed or upgrade of FPGA will fail !!! Beginning erase of 0x100000 bytes at offset 0x3d00000... Done! Beginning write of fpga image (0x78fb0 bytes at offset 0x3d00000)... This could take as little as 30 seconds or up to 2 minutes. Please DO NOT RESET! Success! FPGA image has been upgraded successfully. System will reset itself and reboot in about 15 seconds. 0 ********************************************************** * * * Welcome to Rom Monitor for WS-X4014 System. * * Copyright (c) 2002 by Cisco Systems, Inc. * * All rights reserved. * * * ********************************************************** Rom Monitor Program Version 12.1(11br)EW Board type 1, Board revision 5 Swamp FPGA revision 16, Dagobah FPGA revision 47 MAC Address : 00-30-85-XX-XX-XX IP Address : 10.10.10.91 Netmask : 255.255.255.0 Gateway : 10.10.10.1 TftpServer : Not set. Main Memory : 256 MBytes ***** The system will autoboot in 5 seconds ***** Type control-C to prevent autobooting. Switch#

Step 8   Use the show version command to verify that the new Cisco IOS software version is running on the switch.

---

Limitations and Restrictions

These sections list limitations and restrictions for the Cisco IOS for the Catalyst 4006 switch with Supervisor Engine III:

• Only ports 1 and 2 on the WS-X4418-GB and only ports 13 and 14 on the WS-X4412-2GB-T module can be set as ISL trunks.

• The Fast Ethernet port (10/100) on the supervisor module is inoperative in Cisco IOS releases 12.1(8a)EW and 12.1(11b)EW.

An Ethernet cable plugged into the Fast Ethernet port is active only in ROMMON mode.

• If an original packet is dropped due to transmit queue shaping and/or sharing configurations, a SPAN packet copy can still be transmitted on the SPAN port.

• Cisco recommends that you do not use over 100,000 routes with Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW.

• Cisco recommends that you configure no ip unreachables to all interfaces with ACLs configured for performance reasons.

• Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW support VLAN identifier space from 1 to 1000.

• Cisco IOS software releases 12.1(8a)EWand 12.1(11b)EW support a maximum of 16,000 IGMP snooping group entries.

• The Catalyst 4006 with Supervisor Engine III does not support per-port configuration to trust IP precedence values. Instead, a service-policy can be attached to the port in order to map IP precedence values to internal DSCP values.

• BGP Policy accounting is not supported in Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW. (CSCdv20786)

• BGP Conditional Advertisement are not supported in Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW. (CSCdv20786)

• Layer 3 path load balancing metrics are not supported in Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW. (CSCdv10578)

• The CLI contains some commands that are not supported in Cisco IOS software releases 12.1(8a)EW and 12.1(11b)EW. (CSCdw44274)

Caveats

Caveats describe unexpected behavior in Cisco IOS software releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.

Note   All caveats in Release 12.1 also apply to the corresponding 12.1 E releases. Refer to the Caveats for Cisco IOS Release 12.1 publication at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/121cavs/121mcavs.htm

Open Caveats in Software Release 12.1(11b)EW1

• A Catalyst 4006 switch with Supervisor Engine III using 12.1(11b)EW may crash when you enter the following command while the port channel set to channel-no is in a shutdown state:

show platform software etherchannel port-channel channel-no

This command was introduced in software release 12.1(11b)EW. Software release 12.1(8b)EW is not affected by this caveat.

Workaround: Don't use the above command for a port channel in a shutdown state. (CSCdx47694)

• On a Catalyst 4006 switch with Supervisor Engine III, the output rate in show interface command might display a value greater than the bandwidth that the interface can handle. There is no workaround. (CSCdx30670)

• When you use a large number of ACLs with more than 1000 entries, the switch can take more than five minutes to boot up.

Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)

• Under some conditions, the CEF database may get corrupted and the following error message will appear:

3d03h: %FIB-4-FIBIDB: Missing cef idb for GigabitEthernet2/6 during address ch

When this happens, traffic to or from that interface will not be received or forwarded correctly.

Workaround: Functionality might be restored by bringing the interface administratively down and up, or by disabling and re-enabling IP routing. (CSCdx37609)

• If an ACL is applied to more than one interface, and any Access Control Entry (ACE) in the ACL is subsequently modified, then the Ternary Content Addressable Memory (TCAM) usage of that ACL is multiplied by the number of interfaces to which the ACL is applied.

Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)

• A Cisco router configured for Multicast Source Discovery Protocol (MSDP) can experience frequent MSDP session resets with the MSDP peers of the router. This situation is often caused by excessive Source, Group (S, G) information that should be contained in a domain being passed to the outside, resulting in additional entries in the Source-Active (SA) cache.

Workarounds: Determine whether the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txt

Determine whether the router is running a Cisco IOS image that has the correction for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).

Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)

Resolved Caveats in Software Release 12.1(11b)EW1

• Under some conditions, the Supervisor Engine III (WS-X4014) might stop switching traffic on all connected ports. Should this occur, all incoming data traffic will be dropped.

When the switch enters this state, the NoPacketBuffAvailOrCdmFifoOverruns counter will increment on all ports that have received incoming data traffic. You can display the contents of the NoPacketBuffAvailOrCdmFifoOverruns counter by entering the show platform software interface statistics command.

Workaround: This condition is temporary and can be resolved by resetting the switch. (CSCdx66345)

• When burst CPU traffic conditions (low CPU traffic combined with intermittent bursts of routing updates) occur, packets sent to the CPU can be lost. This traffic interruption can occur for less than one second or for a few minutes. No intervention is required, the switch recovers automatically. (CSCdy06162)

Open Caveats in Software Release 12.1(11b)EW

• A Catalyst 4006 switch with Supervisor Engine III using 12.1(11b)EW may crash when you enter the following command while the port channel set to channel-no is in a shutdown state:

show platform software etherchannel port-channel channel-no

This command was introduced in software release 12.1(11b)EW. Software release 12.1(8b)EW is not affected by this caveat.

Workaround: Don't use the above command for a port channel in a shutdown state. (CSCdx47694)

• On a Catalyst 4006 switch with Supervisor Engine III, the output rate in show interface command might display a value greater than the bandwidth that the interface can handle. There is no workaround. (CSCdx30670)

• When you use a large number of ACLs with more than 1000 entries, the switch can take more than five minutes to boot up.

Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)

• Under some conditions, the CEF database may get corrupted and the following error message will appear:

3d03h: %FIB-4-FIBIDB: Missing cef idb for GigabitEthernet2/6 during address ch

When this happens, traffic to or from that interface will not be received or forwarded correctly.

Workaround: Functionality might be restored by bringing the interface administratively down and up, or by disabling and re-enabling IP routing. (CSCdx37609)

• A Cisco router configured for Multicast Source Discovery Protocol (MSDP) can experience frequent MSDP session resets with the MSDP peers of the router. This situation is often caused by excessive Source, Group (S, G) information that should be contained in a domain being passed to the outside, resulting in additional entries in the Source-Active (SA) cache.

Workarounds: Determine whether the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txt

Determine whether the router is running a Cisco IOS image that has the correction for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).

Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)

• If an ACL is applied to more than one interface, and any Access Control Entry (ACE) in the ACL is subsequently modified, then the Ternary Content Addressable Memory (TCAM) usage of that ACL is multiplied by the number of interfaces to which the ACL is applied.

Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)

Resolved Caveats in Software Release 12.1(11b)EW

• In the show power and show environment commands, the status of the Power Entry Module (PEM) is reported incorrectly. If the status of the PEM is listed as bad, it is actually good, and if the status is listed as good, it is actually bad. This has no affect on system operation. n software release 12.1(8a)EW1, the PEM is supported only in the show commands. (CSCdx05522)

• When a large number of ports (such as 240) have joined a large number of multicast groups, entering the clear ip igmp group command to delete IGMP group cache entries can sometimes reboot a Catalyst 4006 switch with Supervisor Engine III running Cisco IOS software release 12.1(8a)EW.

Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)

• Ocasssionally, a switch may have errors when reading register status. When this occurs, the switch logs the message instead of recovering from the error by attempting to read the register status again. The hardware is not actually bad.There is no workaround. (CSCdx52952)

• Typing Ctrl-/ when attached to the console port will cause the switch to reboot. There is no workaround (CSCdw06454).

• If you create Switched Virtual Interfaces (SVI) for both a primary VLAN and secondary VLAN and then delete them, a subsequent association between the VLANs the switch could reboot your switch.

Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)

• Packets that are software-generated or software-forwarded are not transmitted in a SPAN session. This includes Layer 2 control packets, such as CDP or Spanning Tree BPDUs, and packets forwarded by software such as FIB, or adjacency overload scenarios. There is no workaround. (CSCdv34494)

• In an ACL, the fragment keyword is ignored when the protocol is ip. For all other protocols the keyword is applied to traffic as expected.

Workaround: Replace the permit ip any any fragment command with the following commands:

permit 1 any any fragment permit 2 any any fragment permit 255 any any fragment

(CSCdw39872)

• The show platform hardware monitor command may corrupt the stack if it is invoked when a VSPAN session or a PSPAN session with many source interfaces is configured on the switch. There is no workaround; to be safe, do not use this command on switches running Cisco IOS software release 12.1(8a)EW. (CSCdw59733)

Open Caveats in Software Release 12.1(8a)EW1

• In the show power and show environment commands, the status of the Power Entry Module (PEM) is reported incorrectly. If the status of the PEM is listed as bad, it is actually good, and if the status is listed as good, it is actually bad. This has no affect on system operation. n software release 12.1(8a)EW1, the PEM is supported only in the show commands. (CSCdx05522)

• When a large number of ports (such as 240) have joined a large number of multicast groups, entering the clear ip igmp group command to delete IGMP group cache entries can sometimes reboot a Catalyst 4006 switch with Supervisor Engine III running Cisco IOS software release 12.1(8a)EW.

Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)

• When you use a large number of ACLs with more than 1000 entries, the switch can take more than five minutes to boot up.

Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)

• A Cisco router configured for Multicast Source Discovery Protocol (MSDP) can experience frequent MSDP session resets with the MSDP peers of the router. This situation is often caused by excessive source, group (S, G) information that should be contained in a domain being passed to the outside, resulting in additional entries in the Source-Active (SA) cache.

Workarounds: Determine if the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txt

Determine if the router is running a Cisco IOS image that has the fix for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).

Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)

• Typing Ctrl-/ when attached to the console port will cause the switch to reboot. There is no workaround (CSCdw06454).

• If you create Switched Virtual Interfaces (SVI) for both a primary VLAN and secondary VLAN and then delete them, a subsequent association between the VLANs the switch could reboot your switch.

Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)

• In an ACL, the fragment keyword is ignored when the protocol is ip. For all other protocols the keyword is applied to traffic as expected.

Workaround: Replace the permit ip any any fragment command with the following commands:

permit 1 any any fragment permit 2 any any fragment permit 255 any any fragment

(CSCdw39872)

• Packets that are software-generated or software-forwarded are not transmitted in a SPAN session. This includes Layer 2 control packets, such as CDP or Spanning Tree BPDUs, and packets forwarded by software such as FIB, or adjacency overload scenarios. There is no workaround. (CSCdv34494)

• If an ACL is applied to more than one interface, and any ACE in the ACL is subsequently modified, then the TCAM usage of that ACL is multiplied by the number of interfaces to which the ACL is applied.

Workaround: detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)

• The show platform hardware monitor command may corrupt the stack if it is invoked when a VSPAN session or a PSPAN session with many source interfaces is configured on the switch. There is no workaround; to be safe, do not use this command on switches running Cisco IOS software release 12.1(8a)EW. (CSCdw59733)

Resolved Caveats in Software Release 12.1(8a)EW1

• An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

(CSCdw65903)

Open Caveats in Software Release 12.1(8a)EW

• Under some conditions, the Supervisor Engine III (WS-X4014) might stop switching traffic on all connected ports. Should this occur, all incoming data traffic will be dropped.

When the switch enters this state, the NoPacketBuffAvailOrCdmFifoOverruns counter will increment on all ports that have received incoming data traffic. You can display the contents of the NoPacketBuffAvailOrCdmFifoOverruns counter by entering the show platform software interface statistics command.

Workaround: This condition is temporary and can be resolved by resetting the switch. (CSCdx66345)

• In the show power and show environment commands, the status of the Power Entry Module (PEM) is reported incorrectly. If the status of the PEM is listed as bad, it is actually good, and if the status is listed as good, it is actually bad. This has no affect on system operation. n software release 12.1(8a)EW1, the PEM is supported only in the show commands. (CSCdx05522)

• Typing Ctrl-/ when attached to the console port will cause the switch to reboot. There is no workaround (CSCdw06454).

• When a large number of ports (such as 240) have joined a large number of multicast groups, entering the clear ip igmp group command to delete IGMP group cache entries can sometimes reboot a Catalyst 4006 switch with Supervisor Engine III running Cisco IOS software release 12.1(8a)EW.

Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)

• When you use a large number of ACLs with more than 1000 entries, the switch can take more than five minutes to boot up.

Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)

• A Cisco router configured for Multicast Source Discovery Protocol (MSDP) can experience frequent MSDP session resets with the MSDP peers of the router. This situation is often caused by excessive source, group (S, G) information that should be contained in a domain being passed to the outside, resulting in additional entries in the Source-Active (SA) cache.

Workarounds: Determine if the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txt

Determine if the router is running a Cisco IOS image that has the fix for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).

Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)

• If you create Switched Virtual Interfaces (SVI) for both a primary VLAN and secondary VLAN and then delete them, a subsequent association between the VLANs the switch could reboot your switch.

Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)

• If an ACL is applied to more than one interface, and any ACE in the ACL is subsequently modified, then the TCAM usage of that ACL is multiplied by the number of interfaces to which the ACL is applied.

Workaround: detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)

• In an ACL, the fragment keyword is ignored when the protocol is ip. For all other protocols the keyword is applied to traffic as expected.

Workaround: Replace the permit ip any any fragment command with the following commands:

permit 1 any any fragment permit 2 any any fragment permit 255 any any fragment

(CSCdw39872)

• Packets that are software-generated or software-forwarded are not transmitted in a SPAN session. This includes Layer 2 control packets, such as CDP or Spanning Tree BPDUs, and packets forwarded by software such as FIB, or adjacency overload scenarios. There is no workaround. (CSCdv34494)

• The show platform hardware monitor command may corrupt the stack if it is invoked when a VSPAN session or a PSPAN session with many source interfaces is configured on the switch. There is no workaround; to be safe, do not use this command on switches running Cisco IOS software release 12.1(8a)EW. (CSCdw59733)

Resolved Caveats in Software Release 12.1(8a)EW

There are no resolved caveats in software release 12.1(8a)EW.

Troubleshooting

These sections provide troubleshooting guidelines for the Catalyst 4006 with Supervisor Engine III:

• Recovering from Loss of the Boot Loader Image

• Troubleshooting at the System Level

• Troubleshooting Modules

• Troubleshooting VLANs

• Troubleshooting Spanning Tree

• Troubleshooting MIBs

Recovering from Loss of the Boot Loader Image

If you lose the boot loader image, you can recover by using one of the following methods:

1. Boot from a CompactFlash card by entering the following command:

rommon 1> boot slot0:<bootable_image>

2. Use ROMMON TFTP boot.

The ROMMON TFTP boot is very similar to the BOOTLDR TFTP boot, except that:

• the BOOTLDR variable should not be set

• the TFTP server must be accessible from the 10/100 port on the supervisor engine.

To boot from ROMMON, perform the following tasks while in ROMMON mode:

   a. Ensure that the 10/100 port on the supervisor engine is physically connected to the network.

   b. Verify that bootloader environment is not set by entering the unset bootldr command.

   c. Set IP address of the 10/100 port on the supervisor engine by entering the following command: set interface fa1 <ip_address> <ip_mask>

For example, to set the supervisor Ethernet port with an IP address 172.16.1.5 and IP mask 255.255.255.0.0, enter the following command:


rommon 2> set interface fa1 172.16.1.5 255.255.0.0

   d. Set default gateway for the 10/100 port on the supervisor engine by entering the following command: set ip route default <gateway_ip_address>. The default gateway should be directly connected to the supervisor engine 10/100 port subnet.

   e. Ping the TFTP server to ensure that there is connectivity to the server from the 10/100 port on the supervisor engine by entering the following command: ping <tftp_server_ip_address>.

   f. Once the ping is successful, boot the image from the TFTP server by entering the following command: boot tftp://<tftp_server_ip_address>/<image_path_and_file_name>

For example, to boot the image name cat4000-is-mz.160 located on the TFTP server 172.16.1.8, enter the following command:


rommon 3> boot tftp://172.16.1.8/tftpboot/cat4000-is-mz

Troubleshooting at the System Level

This section contains troubleshooting guidelines for system-level problems:

• When the system is booting and running power-on diagnostics, do not reset the switch.

• Ensure that you do not mix the serial and ethernet cables plugged into the supervisor engine. The Fast Ethernet port (10/100 MGT) on the supervisor engine is inoperative in Cisco IOS releases 12.1(8a)EW and 12.1(11b)EW. An Ethernet cable plugged into the Fast Ethernet port is active only in ROMMON mode.

Troubleshooting Modules

This section contains troubleshooting guidelines for modules:

• When you hot insert a module into a chassis, always use the ejector levers on the front of the module to seat the backplane pins properly. Inserting a module without using the ejector levers might cause the supervisor engine to display incorrect messages about the module. For module installation instructions, refer to the Catalyst 4000 Family Module Installation Guide.

• Whenever you connect an interface that has duplex set to autonegotiate to an end station or another networking device, ensure that the other device is configured for autonegotiation as well. If the other device is not set to autonegotiate, the port set to autonegotiate will remain in half-duplex mode, which can cause a duplex mismatch resulting in packet loss, late collisions, and line errors on the link.

Troubleshooting VLANs

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:

• For interfaces connected to devices that do not support DTP, in which trunking is not currently being used, configure interfaces with the switchport mode access command, which puts the interface into access mode and causes it to stop sending DTP frames.

• When manually enabling trunking on a link to devices that do not support DTP, use the switchport nonegotiate and switchport mode trunk commands, which puts the interface into trunking mode without sending DTP frames.

Troubleshooting Spanning Tree

The Spanning Tree Protocol (STP) blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, switches periodically receive spanning tree bridge protocol data units (BPDUs) from neighboring switches. You can configure the frequency with which BPDUs are received by entering the spanning-tree VLAN vlan_ID hello-time command. By default, the 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 because convergence times might be unacceptably long.

Use these guidelines to debug STP problems:

• Ensure that the sum of the logical interfaces across all instances of spanning tree for different VLANs does not exceed 2000. The sum of all logical interfaces equals the number of trunks on the switch multiplied by the number of active VLANs on the trunks, plus the number of non-trunking interfaces on the switch. Note the following:

  • 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 maintain the number of supported logical spanning tree interfaces, keep switched traffic off the management VLAN.

The show spanning-tree summary totals command displays the number of logical interfaces in the STP Active column.

• Keep track of all blocked spanning tree interfaces in each switch in your network. For each of the blocked spanning tree ports, keep track of the output of the show interface command. Check to see if the interface has registered a lot of alignment, FCS, or any other type of line errors. If these errors are incrementing continuously, the interface might drop input BPDUs. If the input queue counter is incrementing continuously, the interface is losing input packets because of a lack of receive buffers. This problem can also cause the interface to drop incoming BPDUs.

• On a blocked spanning tree interface, check the duplex configuration to ensure that the interface duplex is set to the same mode as the interface of its neighboring device.

• On trunks, ensure that the trunk configuration is set properly on both sides of the link.

• On trunks, if the neighboring device supports it, set duplex to full on both sides of the link to prevent any collisions during times of heavy traffic.

Troubleshooting MIBs

For general information on MIBs, RMON groups, and traps, refer to the Cisco public MIB directory (http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml). For information on the specific MIBs supported by the Catalyst 4000 family switches, refer to the Catalyst 4000 MIB Support List located at ftp://ftp.cisco.com/pub/mibs/supportlists/cat4000/cat4000-supportlist.html.

Documentation Updates for Release 12.1(8a)EW

This section describes updates to the Cisco IOS for the Catalyst 4006 with Supervisor Engine III documentation. These changes will be included in the next update of the documentation.

Changes

The following system message has changed.

Error Message   C4K_IOSSYSMAN-3-OUTOFPRIVATEPOOLPACKETS:Cannot allocate Gsg packet buffer (probably packet leak)

Explanation   The system cannot allocate a platform packet buffer.

Recommended Action   Contact your technical support representatives.

If the Explanation above does not sufficiently explain the problem you are encountering, write down the error message exactly as it appears on the console or in the system log. Then, enter the show tech-support command to gather additional data about the error. If the error message text and the output from the show tech-support command do not help you solve the problem, contact your technical support representative and provide the representative with the information you have gathered.

Omissions

The following system messages were not included in the System Message Guide.

• C4K_CHASSIS-4-SEEPROMREADFAILED

Error Message   C4K_CHASSIS-4-SEEPROMREADFAILED:Failed to read module's serial eeprom, try reinserting module

Explanation   Reading the supervisor module's serial EEPROM failed. The read could fail because the module isn't seated correctly in the slot in the chassis.

Recommended Action   Remove and reinsert the module. If that doesn't resolve the problem you are encountering, power cycle the switch. If the read still fails, return the module to Cisco by contacting your technical support representative.

See the message explanation to determine whether the explanation addresses the problem you are encountering. If it does not, write down the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that can provide information about the error. If you cannot determine the type of error from the error message text or from the show tech-support output, contact your technical support representative and provide the representative with the gathered information.

• C4K_HWACLMAN-4-ACLHWPROGERR

Error Message   C4K_HWACLMAN-4-ACLHWPROGERR:[char] [char] - hardware TCAM limit, [char]

Explanation   Some ACL-based feature(s) could not be fully programmed into hardware. Packets that traverse these feature(s) will complete their processing in software. (If the feature is a policy map, then QoS will be completely disabled instead (on the specific interface)).

This message lists the impacted features; further message(s) will list the specific failure that occurred.

Recommended Action   See the message explanation to determine whether the explanation addresses the problem you are encountering. if it does not, write down the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information about the error. If you cannot determine the type of error from the error message text or from the show tech-support output, contact your technical support representative and provide the representative with the gathered information.

• C4K_HWACLMAN-4-ACLHWPROGERRREASON

Error Message   C4K_HWACLMAN-4-ACLHWPROGERRREASON:[char] [char] - [char]

Explanation   This message lists the specific failure that prevented an ACL-based feature([s) from being fully programmed into hardware. Only six Layer 4 operations are allowed per ACL.

Recommended Action   See the message explanation to determine whether the explanation addresses the problem you are encountering. if it does not, write down the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information about the error. If you cannot determine the type of error from the error message text or from the show tech-support output, contact your technical support representative and provide the representative with the gathered information.

• C4K_IPROUTEMAN-4-CANTALLOCATEFIBENTRY

Error Message   C4K_IPROUTEMAN-4-CANTALLOCATEFIBENTRY:FIB:No memory available to allocate FIB Entry for [ip-addr]

Explanation   Insufficient memory exists to allocate space for the route associated with this network.

Recommended Action   You might need to install additional memory. If this does not solve the problem, do the following:

Write down the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information about the error. If you cannot determine the type of error from the error message text or from the show tech-support output, contact your technical support representative and provide the representative with the gathered information.

• C4K_PKTPROCESSING-5-ADJLOOKUPFAILED

Error Message   C4K_PKTPROCESSING-5-ADJLOOKUPFAILED:[dec] packets dropped:Draining the backed up packets in CPU queue when we cleaned up FIB adjacencies. Source address [ip-addr] and destination address [ip-addr]

Explanation   This could happen when the software processes the routed packets and the router port is shut down. The adjacencies have been cleaned up, but the queued packet are still being processed.

Recommended Action   This message is informational only. No action is required.

• C4K_PKTPROCESSING-7-ADJLOOKUPFAILED

Error Message   C4K_PKTPROCESSING-7-ADJLOOKUPFAILED:[dec] packets dropped:Draining the backed up packets in CPU queue when we cleaned up FIB adjacencies. Last drained packet's source address [ip-addr] and destination address [ip-addr]

Explanation   This could happen when processing Layer 3 packets in software and a shut down is issued on a router port. The software cleans up the adjacencies, but there might still be packets that are backed up in the CPU queue that need to be processed.

Recommended Action   This is an informational message. No action is required.

Related Documentation

These sections describe the documentation available for the Cisco IOS for the Catalyst 4006 with Supervisor Engine III. These publications consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other publications. Documentation is available electronically or in printed form.

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

• Release-Specific Publications

• Platform-Specific Publications

• Cisco IOS Software Documentation Set

Release-Specific Publications

These publications are specific to Release 12.1 and are located on Cisco.com and the Documentation CD-ROM:

• Cross-Platform Release Notes for Cisco IOS Release 12.1

On Cisco.com at
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/xprn121/index.htm

On the Documentation CD-ROM at
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes

• Product bulletins, field notices, and other release-specific publications on Cisco.com at
  Technical Documents

• Caveats for Cisco IOS Release 12.1

As a supplement to the caveats listed in the "Caveats" section, see the Caveats for Cisco IOS Release 12.1 publication.

On Cisco.com at
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats

On the Documentation CD-ROM at
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats

---

Note   If you have an account on Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to Cisco.com and click 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.

---

Platform-Specific Publications

These publications are available for the Catalyst 4006 switch with Supervisor Engine III running the Cisco IOS at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/12_18a/index.htm

• Catalyst 4000 Family Installation Guide

• Catalyst 4000 Family Module Installation Guide

• Catalyst 4000 Family Supervisor Engine III Installation and Configuration Note

• Software Configuration Guide for the Catalyst 4006 with Supervisor Engine III

• Command Reference for the Catalyst 4006 with Supervisor Engine III

• System Message Guide for the Catalyst 4006 with Supervisor Engine III

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 publications 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 Cisco.com and the Documentation CD-ROM, two master hot-linked publications provide information for the Cisco IOS software documentation set.

On Cisco.com 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

Release 12.1 Documentation Set

The following table describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and orderable in printed form.

Note   You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM. These electronic publications may contain updates and modifications that were made after the hard-copy publications were printed.

On Cisco.com 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

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com

Translated documentation is available at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

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

Ordering Documentation

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

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

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

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

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

• Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

• Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://www.cisco.com/register/

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Copyright © 2002, Cisco Systems, Inc.
All rights reserved.

Posted: Tue Aug 6 14:37:01 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.