|
|
Catalyst 8540 for Cisco IOS Release 12.1(19)E2
Text Part Number: OL-2550-11, A0
This document describes the features and caveats for Cisco IOS Release 12.1(19)E2 for the Catalyst 8540 multiservice ATM switch router (MSR), and the Catalyst 8540 campus switch router (CSR). For relevant features, some information on Cisco IOS Release 12.0 is provided.
 |
Note All information pertains to both the Catalyst 8540 MSR and Catalyst 8540 CSR platforms, unless differences between the platforms are noted in the text. |
This document includes the following sections:
The Catalyst 8540 is a 13-slot, modular chassis with optional dual, fault-tolerant, load-sharing AC or DC power supplies.
The Catalyst 8540 MSR switch router provides a 20-Gbps full-duplex nonblocking switch fabric with switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.
The Catalyst 8540 CSR switch router belongs to a class of high-performance Layer 3 switch routers and is optimized for the campus LAN or the intranet. The Catalyst 8540 CSR switch router provides both wirespeed Ethernet routing and switching services.
This section describes the system requirements for Cisco IOS Release 12.1(19)E2 and includes the following sections:
Table 1 lists the default Flash and DRAM memory for the Catalyst 8540, as well as memory upgrade options.
Table 1 Catalyst 8540 Default Memory and Upgrade Options
|
To check that your system has a 16-MB boot Flash SIMM, enter the show hardware EXEC command. The part numbers for Catalyst 8540 switch router route processors with a default 16-MB boot Flash SIMM follow:
If you have an 8-MB boot Flash SIMM, and have no additional memory installed, we recommend that you order a spare Flash PC card programmed with the latest version of the system image.
|
Note We recommend that you use a San Disk 48-MB PC Card to download and store a copy of the switch router software image. This allows you to store two or more images at the same time. |
A Flash PC Card must be ordered as a spare part. See Table 1 for part numbers. For information on upgrading a Flash PC Card, see the "Upgrading a PC Card" section. For more detailed information on Flash PC Cards, refer to the "Configuring the Route Processor " chapter of the Layer 3 Switching Software Feature and Configuration Guide.
Alternatively, you can use one of the following options to accommodate the larger image:
|
Note If you have a Smart Modular, Sharp, or Intel 2+ Flash PC card that was formatted using a Cisco IOS software release prior to 12.0(4a)W5(11a), reformat it with Cisco IOS Release 12.1(19)E2 prior to downloading the image (you might need to boot the image from a TFTP server to format the PC Flash card). Do not erase the system image on the boot Flash SIMM. If the procedure fails, you will need it to recover. (See caveat CSCdm47012 for more information.) |
|
Note The boot ROM on the Catalyst 8540 MSR can be field-upgraded via the reprogram command. For more information about upgrading the boot ROM, refer to the ATM and Layer 3 Switch Router Command Reference. |
For more information about downloading system images and changing the default boot image, refer to the "File Management" chapter of the Configuration Fundamentals Configuration Guide in the Cisco IOS software documentation set.
This section describes how to upgrade to a SanDisk 48-MB PC card. PC upgrade cards are available in 48-MB.
|
Note You need Cisco IOS Release version 12.1(5)EY or higher and rommon version 12.0(14)W5(20) or higher to upgrade to the SanDisk PC card. If you do not meet these minimum version requirements, the SanDisk PC card will not work. |
To upgrade the PC card, follow these steps:
Step 2 Once the switch is up and running, use the copy command to copy the rommon image to the boot Flash SIMM.
Step 3 Reprogram the rommon image using the reprogram command.
The following example shows the rommon being reprogrammed:
Step 4 Load the switch with the latest Cisco IOS release image again.
Step 5 Enter the format command to format the PC card. It is now ready for use.
The following example shows the format command being entered on slot 0:
Table 2 lists the hardware modules supported on the Catalyst 8540 MSR in Cisco IOS Release 12.1(19)E2.
|
Note Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8540 hardware. |
Table 2 Catalyst 8540 MSR Supported Hardware Modules and
Minimum Software Requirements
|
| 1 The T1/E1 IMA port adapters also require carrier module FPGA image version 1.8 or later, and IMA port adapter functional image version 3.2 or later. |
Table 3 lists the hardware modules supported on the Catalyst 8540 CSR in Cisco IOS Release 12.1(19)E2.
Table 3 Catalyst 8540 CSR Supported Hardware Modules and
Minimum Software Requirements
|
Note We strongly recommend that you use the latest available software release for all Catalyst 8540 hardware. |
To determine the version of Cisco IOS software currently running on a Catalyst 8540, log in to the switch router and enter the show version EXEC command. The following sample output is from the show version command. The version number is indicated on the second line as shown below:
Most of the interface modules supported on the Catalyst 8540 have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/l3sw/8540/rel_12_0/w5_6f/rel_note/fpga_rn/ind ex.htm
For more information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8540 MSR)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide .
The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Table 4 lists the software features available for the Catalyst 8540 MSR.
Table 4 Feature Sets Supported by the Catalyst 8540 MSR
|
|
1 LES = LAN Emulation Server 2 BUS = broadcast and unknown server 3 LECS = LAN Emulation Configuration Server 4 MCR = minimum cell rate 5 ABR = available bit rate 6 MIB = Management Information Base 7 UBR = unspecified bit rate 8 LER = label edge routing 9 LDP = Label Distribution Protocol 10 LSR = label switch router |
The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Table 5 lists the software features available for the Catalyst 8540 CSR.
Table 5 Feature Sets Supported by the Catalyst 8540 CSR
|
|
1 integrated routing and bridging 2 CPU redundancy for the Catalyst 8540 CSR 3 Inter-Switch Link 4 Constrained Multicast Flooding 5 Border Gateway Protocol 6 Routing Information Protocol 7 Interior Gateway Routing Protocol 8 Enhanced Interior Gateway Routing Protocol 9 Open Shortest Path First 10 Internet Packet Exchange 11 Protocol Independent Multicast 12 AppleTalk Update-based Routing Protocol 13 Classless Interdomain Routing 14 Bootstrap Protocol 15 Cisco Group Management Protocol 16 Cisco Discovery Protocol 17 Dynamic Host Configuration Protocol 18 Hot Standby Routing Protocol 19 Bridge-Group Virtual Interface 20 Internet Control Message Protocol 21 Network Time Protocol 22 Internet Group Management Protocol 23 Internet Packet Exchange Service Advertisement Protocol 24 Simple Network Management Protocol 25 User Datagram Protocol 26 Intermediate System-to-Intermediate System |
Table 6 lists the release names, versions, and part numbers used with the Catalyst 8540 MSR and Catalyst 8540 CSR switch routers.
Table 6 Release Name to Version to Part Number Matrix for Catalyst 8540 Switch Routers
|
Following are some issues which you should be aware of during upgrade or downgrade of the Cisco IOS software for the Catalyst 8540 MSR:
|
Note The procedure used to upgrade and downgrade a Catalyst 8540 MSR is available on the following: http://www.cisco.com/warp/public/121/8540redundancy.shtml. |
1. When a Frame Relay connection traffic table row (CTTR) index is created using the CLI a corresponding ATM CTTR is also created automatically by the switch and the MBS value (in the internally created ATM CTTR) is calculated using the Bc value configured on the Frame Relay side. However, the ATM CTTR can also be created using the CLI and then associated with a Frame Relay CTTR. If you create the Frame Relay CTTR and associated it with the manually created ATM CTTR, during an upgrade of Catalyst 8540 MSR from Cisco IOS release 12.1(12c)EY to the release 12.1(13)EB, manually created ATM CTTR association will not be in effect on the new primary Route Processor (after switchover). Instead, an ATM CTTR (with random index) corresponding to Frame Relay CTTR is recreated with an MBS value generated from the Bc value configured on the Frame Relay side. This means, after upgrade, if manual association of ATM CTTR to Frame Relay CTTR is required, it needs to be redone (by deleting the existing Frame Relay CTTR and then recreating it with manual association of an ATM CTTR).
2. When the Catalyst 8540 MSR is downgraded from release 12.1(13)EB to any lower version, ATM CTTRs having packet-discard enabled and ATM VCs associated with CTTRs having packet-discard enabled are lost. This is because, during an upgrade if release 12.1(13)EB is running on the primary Route Processor and some lower version is running on the secondary Route Processor, the ATM CTTR (having packet-discard enabled) information are not synced to the secondary Route Processor. And if Route Processor switchover is done to complete the downgrade the ATM CTTRs having packet-discard enabled are lost along with the ATM VCs associated with these ATM CTTRs.
3. When the Catalyst 8540 MSR is downgraded from release 12.1(13)EB to any lower version (in the 12.1 train), Frame Relay CTTRs having non-default frame size and Frame Relay VCs associated with Frame Relay CTTR having non-default frame size are lost. This is because, during an downgrade if release 12.1(13)EB is running on the primary Route Processor and some lower version is running on the secondary Route Processor, the Frame Relay CTTR (having non-default frame size) information are not synced to the secondary Route Processor. And if Route Processor switchover is done to complete the downgrade, Frame Relay CTTRs having non-default frame size are lost along with the Frame Relay VCs associated with these Frame Relay CTTRs. However, the Frame Relay VCs will not be removed from the firmware. But, traffic flow through those VCs STOPS at the ATM leg (including that of psuedo port) is NOT present in the hardware for all Frame Relay VCs after downgrade. To recover from this problem, use the hw-module slot/subslot reset command and recreate the lost Frame Relay CTTRs and Frame Relay VCs.
4. Frame Relay CTTR could be configured with Bc/Be less than Frame Size before release 12.1(13)EB. With release12.1(13)EB, Bc/Be can not be less than the Frame Relay frame size. Hence if the Catalyst 8540 MSR, Catalyst 8510 MSR, or a LightStream 1010 is running an image older than release 12.1(13)EB and if the startup configuration has the Bc/Be value less than 2000 bits (in older images default frame size = 250 bytes = 2000 bits) and is reloaded and rebooted with release 12.1(13)EB, then the following error messages might appear for the primary Route Processor:
Any Frame Relay CTTR having Bc/Be less than Frame Size might be lost after reboot.
Also, Frame Relay VCs associated with these CTTRs might cause the following message to appear when the primary Route Processor is coming up:
5. Upgrading from Cisco IOS Release 12.1(12c)E or 12.1(12c)EY, using the standard upgrade procedure, causes the switched connections (transiting or terminating) on the Catalyst 8540 to be torn down if ILMI keep-alives are enabled on the interface of the Catalyst 8540 and its peer through which the connections are transiting. The workaround is, before upgrading, disable ILMI keep-alive on both the ends of the NNI link between the Catalyst 8540 and its peer switch.
6. When the Catalyst 8540 MSR image is downgraded from Cisco IOS Release 12.1(14)EB to a software image that does not support 8192 (8k) VCs on the enhanced ATM Router Module, and the enhanced ATM Router Module has more than 2048 (2k) VCs configured at the time of downgrade, the internal Control VCs from the Route Processor to the enhanced ATM Router Module and the VCs between the enhanced ATM Router Module and other Layer 3 capable ports might not be set up. This affects the Layer3 and bridging functionality on the enhanced ATM Router Module. The workaround is to downgrade with less than 1500 VCs configured on the enhanced ATM Router Module and then configure the remaining VCs until the limit is reached. Refer to DDTS CSCin27040 for additional information.
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.1. The new features are sorted by release number.
There are no new features in Cisco IOS Release 12.1(19)E2.
There are no new features in Cisco IOS Release 12.1(14)EB1.
There are no new features in Cisco IOS Release 12.1(19)E.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(14)EB:
|
Note The VCI range has been increased from 4095 to 8191 with the introduction of 8k (8192) VC support on the enhanced ATM Router Module for Cisco IOS Release 12.1(14)EB and later. |
The following new feature is available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(14)E1:
There are no new features for the Catalyst 8540 CSR in Cisco IOS Release 12.1(14)E1.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(13)EB1:
There are no new features in Cisco IOS Release 12.1(13)E1.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(12c)EY:
There are no new features for the Catalyst 8540 CSR in Cisco IOS Release 12.1(12c)EY.
There are no new features in Cisco IOS Release 12.1(12c)E1.
The following new feature is available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(12c)E:
There are no new features for the Catalyst 8540 CSR in Cisco IOS Release 12.1(12c)E.
There are no new features in Cisco IOS Release 12.1(11b)E1.
There are no new features in Cisco IOS Release 12.1(11b)E.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(10)EY:
There are no new features for the Catalyst 8540 CSR in Cisco IOS Release 12.1(10)EY.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(10)E:
The following new feature is available for the Catalyst 8540 CSR in Cisco IOS Release 12.1(10)E:
There are no new features in Cisco IOS Release 12.1(7a)EY1.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(7a)EY:
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.1(7a)EY:
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(6)EY:
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.1(6)EY:
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(5)EY:
See the "Related Documentation" section for a list of documents that describe these features.
The following new feature is available for the Catalyst 8540 CSR in Cisco IOS Release 12.1(5)EY:
See the "Related Documentation" section for a list of documents that describe this feature.
This section lists caveats for the Catalyst 8540 MSR by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release. To find caveats for the Catalyst 8540 CSR see the "Caveats for the Catalyst 8540 CSR" section.
Table 7 lists caveats for the Catalyst 8540 MSR.
Table 7 Caveat Matrix for the Catalyst 8540 MSR
|
This section lists caveats for the Catalyst 8540 CSR by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release. For information on Catalyst 8540 MSR see "Caveats for the Catalyst 8540 MSR" section.
Table 8 lists caveats for the Catalyst 8540 CSR:
Table 8 Caveat Matrix for the Catalyst 8540 CSR
|
This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8540.
Symptom: The Frame Relay retry-interval is shown twice in the running configuration. This means the configured Frame Relay Soft VCs are not preserved after an image reload or a route processor switchover.
Symptom: PNNI routing fails from one access device to a complex-peer in some branches. For example, in the following network example, calls from the Ls1010 switch to an interface on the Catalyst 8540 switch are not set up.
But, calls from the Catalyst 8540 switch to the Ls1010 switch are set up correctly. If the Catalyst 8540.2 switch is configured as a simple single-level hierarchy the calls originated from either switch to the other switch are set up without any problems.
Workaround: Configure the complex node (Catalyst 8540.2 switch) as a simple hierarchy.
Symptom: The switch crashes when you run the no tag-switching mtu command.
Symptom: The following issues could be seen on the simultaneous execution of certain PNNI CLIs.
The following issues are also seen:
Symptom: On a Catalyst 8540 MSR, if an OC-3 interface is overbooked and configured with PVCs that consume more than 599 Mbps of bandwidth, during bootup these PVCs are lost from the running configuration.
The following error message appears during bootup for every PVC that is rejected.
Workaround: Configure the PVCs that were lost once the switch boots up.
Symptom: After a Route Processor switchover, no traffic flows through structured CES circuits (Hard PVCs, Soft PVCs and SVCs). This does not occur on unstructured CES circuits.
Workaround: Use the shutdown and no shutdown commands on the CES interface and traffic starts flowing again.
Symptom: The marking feature does not work on the Enhanced Gigabit Ethernet module if the outgoing interface is TC-ATM. It works if the outgoing VC is a normal 1483 PVC.
Symptom: Primary Route Processor crashes on copying a diag-image from TFTP to PCMCIA flashcard.
Workaround: Configured "no file verify auto" to avoid the automatic IOS image verification. This will prevent the crash.
Symptom: If a Frame Relay-Frame Relay PVC is deleted through SNMP Resource Management the information is incorrect in the show frame-relay interface resource serial card/subcard/port:chn_grp_# command display.
This allows for creation of more VCs than the physical bandwidth available.
Workaround: Delete and recreate the channel group.
Symptom: Upgrading from Cisco IOS Release 12.1(12c)E or 12.1(12c)EY, using the standard upgrade procedure, causes the switched connections (transiting or terminating) on the Catalyst 8540 to be torn down if ILMI keep-alives are enabled on the interface of the Catalyst 8540 and its peer through which the connections are transiting.
Workaround: Before upgrading, disable ILMI keep-alive on both the ends of the NNI link between the Catalyst 8540 and its peer switch.
Symptom: RMON packet size based counters are not working for 8-port Gigabit Ethernet interfaces. The problem is not found using image version cat8540m-wp-mz.120-22.W5.25.
Symptom: When you configure HSRP on a GEC subinterface to track a parallel link which already has a standby group, a memory leak occurs and HSRP starts changing status up and down continuously.
Symptom: When the last match clause of a class map that is being used in a service policy applied to an interface is deleted, the Catalyst 8540 MSR changes to ROMMON mode.
Workaround: Remove the service policy from the interface and then delete the match clause.
Symptom: When you boot the Catalyst 8540 MSR switch the following error messages pertaining to ONLINE diag failure appears.
This happens because an E1 RJ-45 interface module is installed in the chassis. This might cause the E1 RJ-45 interfaces to change state to Admin down.
Workaround: Use the no shutdown command on the interface that changed state to Admin down.
Symptom: The number of point-to-multipoint Soft-PVC connections on the destination switch displayed by the output of show atm state command might display conflicting results with the output of show atm vc conn-type soft cast p2mp command. The show atm vc conn-type soft cast p2mp command displays the correct status of the point-to-multipoint Soft-PVC connections on the switch.
Symptom: The "Number of soft vc re-try attempts:" value shown in the output of the show atm soft-vc p2mp interface atm card/subcard/port vpi vci command is always one greater than the actual number of re-try attempts made.This is because the counter is incremented on starting the party retry timer and not when the timeout happens and the signalling message is sent.
Symptom: The show diag power-on command displays incorrect slot number information for slots 9 through 12.
Symptom: If the BITS port in T1 mode is the primary clock and it changes to "unlockable", the clock switches to the next priority clock but does not revert back to the BITS port even when it is reconfigured correctly.
Workaround: Reconfigure the BITS clock source as in the following example:
Symptom: For Frame Relay Soft VCs that use frame size other than 250 (default), the CTTR should not be modified.
Workaround: Delete the Soft VC from the configuration and re-create with new a CTTR.
Symptom: The CBR interface module sends a "remote alarm" to the peer interface if the line flaps continuously. This causes the peer interface to change to "yellow alarm" state.
Workaround: Enter the shutdown and no shutdown commands on the CBR interface.
Symptom: When the Catalyst 8540 MSR image is migrated from either Release 12.1(11b)E5 or 12.1(12c)E to Release 12.1(12.1.020719.) using the Route Processor switchover method, the new Primary Route Processor reloads while taking over.
Symptom: When bursty traffic is sent to the ARM via a carrier module installed 1-port OC-12 interface module in a peer Catalyst 8540 MSR, the ARM interface displays underruns and drops packets.
|
Note If a 4-port OC-12 interface module is used instead of the carrier module installed 1-port OC-12 version, there are no displayed underruns or dropped packets. |
Symptom: A memory leak might occur during an "atmSoft_timerProcess". With every "soft-vc" retry the holding memory on "atmsig CC" and "atm soft CV timer" increases and the "free" memory decreases. The free memory might fall to as low as 700K at times.
Symptom: Packets received with a destination multicast MAC address and destination unicast IP address are forwarded to the Route Processor and then forwarded back out on the VLAN where the packets were received.
Symptom: An ATM interface might stick in the state "going down" if the PVC is created from the ATM Router Module with VCI "34" on the ATM side. For example, "atm pvc 2 35 pd on interface ATM0/0/0 7 34" causes the line to flap "up" and "down".
Workaround: Recreate the PVC using any VCI other than "34" on the ATM side.
Symptom: When you downgrade a Catalyst 8540 image from an image that supports 128K ITT entries per MSC module to an image that supports only 32K ITT entries per MSC module, and more than 32K of ITT space was used before the downgrade, the results are undefined. The values displayed for free and used ITT space are incorrect. This is caused by a mismatch in capabilities of the primary and secondary images. Such a downgrade is not recommended.
Symptom: After you configure a Point-to-Multi Point connection, if you try to remove the connection from the leaf side, the following message is displayed:
Workaround: Delete the PVC or PVP from the root end.
Symptom: When a VBR-RT PVC is configured with the UPC drop option, packets below traffic rate are also dropped.
Symptom: When an ATM Soft-VC or Soft-VCP is configured between two interfaces of a Catalyst 8540 MSR using a particular VPI, and a Soft-VC or Soft-VCP is configured with the same VPI, the following error appears:
The internal error message should not appear when the Soft-VC or Soft-VCP configuration fails.
Plus, the following expected message is seen more than once:
The internal error message is not seen when a PVC configuration on an interface is followed by a PVP configuration that uses the same VPI. Also, the internal error is not seen when the interface on which the configuration is being done does not have the resources required by the Soft-VC or Soft-VCP.
After the configuration is executed and then fails, this causes the allocation of the bandwidth requested by the CBR VC even though no VC actually exists. If, for example, N kbps is free on an interface, and a Soft-VC is configured from that interface with a VPI-VCI already in use and uses a CTTR of N kbps, the configuration fails, but all N kbps that were free on that interface are lost. This bandwidth loss is seen only with the CBR service-category.
|
Note Using the shutdown and no shutdown commands on the interface does not recover the lost bandwidth. |
Workaround: For the Catalyst 8540 MSR, if you switchover the route processor it recovers the lost bandwidth on the interface. No workaround exists on the Catalyst 8510 MSR.
No workaround exists for the following error message:
Symptom: If an IMA group exists between a Catalyst 8540 and Catalyst 8510 switches with CBR soft VCs configured between the switches and a link of the IMA group is shutdown or fails the IMA interfaces still display the pervious bandwidth value. This bandwidth value is greater than the actual resources available on the interface and the soft VCs still appear as "up" on both the Catalyst 8540 and Catalyst 8510 switches. This continues to happen as more links are shutdown or fail until the 2 CBR soft VCs that require the resources of 7 E1 links still appear as "up" with only 1 E1 link actually "up" between the IMA interfaces and the other 6 links shutdown.
Workaround: Use the shutdown and no shutdown commands on the IMA group and it will display the correct values of available and allocated bandwidth.
Symptom: If a VC is down when the switch is reloaded, the ARM subinterface stays UP even though the OAM-state is OAM-Down.
Workaround: Bring the VC UP at least once after a reload.
Symptom: If you configure OAM on a PVC while it is down, the OAM state of the VC is displayed as "not applicable" instead of "OAM-Down" and never changes. This means OAM cells are not sent even after the VC comes UP. This only occurs if AIS is not enabled for the VC.
Workaround: Configure OAM for a VC only when it is in UP state.
Symptom: When reloading the Catalyst 8540 MSR switch, the first channel group of the 4CE1 interface module comes up in failed state in the firmware.
Workaround: Enter the shutdown and no shutdown commands on the interface.
Symptom: The Catalyst 8540 MSR might experiences an unexpected reload when reset. This creates a few new entries in the snmpTargetAddrTable. This operation is caused by SNMPV3.
Symptom: If you have hard CES PVCs whose ATM legs belong to a shaped VP tunnel, and you perform a route processor switchover, one of the following two problems might occur:
1. The new primary route processor crashes after displaying the following message:
2. All CBR interfaces go down and they come up only after you perform no shutdown on the interfaces.
Workaround: None for problem 1. For problem 2, perform a no shutdown on all CBR interfaces.
Symptom: Subinterfaces of route processor and ATM router module ports are not registered with SNMP ifTable.
Symptom: If your switch is running Cisco IOS Release 12.1(7a)EY and you perform an OIR of a CES interface module, this might cause the route processor to crash.
Symptom: An unexpected reload on two Catalyst 8540 MSR switches was seen. After booting the switch, the problem is NOT seen again.
The traces pointed to "less stack space" and "mmc subsys init".
Symptom: The clear counters command used with an OC-48 ATM interface module installed does not reset the FEBE counters in the show controllers command display. See the following example:
Workaround: Reload the Cisco IOS image on the switch and do not OIR the OC-48 interface module.
Symptom: When connecting the IMA interface module from a Catalyst 8540 MSR to a Nortel Passport 15000, the IMA interface does not come up.
Symptom: A corrupted HW-CEF table on the Gigabit interface module causes punts (redirects) and CPU usage.
A Catalyst 8540 MSR switches running 12.1(14)E1 might experience high CPU usage due to IP input.
This is caused by corrupted CEF entries in the interface module HW forwarding table that cause the packets to be punted (redirected) to the main route processor CPU.
Workaround: None. For a temporary workaround, use the clear adjacency command to clear the HW -CEF table but, eventually the CPU returns to normal.
Symptom: The ATM router module might have a connectivity problem for bridged traffic. The connectivity is broken for five minutes when the soft VC between the ATM router modules are rerouted using another path.
Workaround: Run the clear bridge command on the Catalyst 8540 switch that is not switching traffic.
Symptom: Soft PVC does not come up.
If a Soft PVC originates from a Catalyst 8540 MSR switch directly connected to an Alcatel switch, the Soft PVC never comes up. If the call originated from the Alcatel side, the Soft PVC comes up with no problem.
The Alcatel switch is directly connected, ATM NNI and PNNI are up, and adjacency is up:
But, if the show atm pnni dtl node 40 ubr command is used:
When the call is initiated from the LightSteam 1010 switch, nothing comes to the Alcatel switch. At the same time, when the call is initiated from the Alcatel switch, the Soft PVC comes up:
Symptom: The loopback diagnostic does not work with a 4-port OC -12 interface module in the Catalyst 8540 MSR.
This occurs after running the shutdown and no shutdown commands on the interface.
Workaround: Remove and reapply loopback diagnostic.
Symptom: Whenever you attempt to update the Access Control List (ACL) attached to the management interface (Ethernet2/0/0) on the LightStream 1010 ATM switch the following error message appears:
ACL functionality on the interface is not affected.
Symptom: There is a connectivity problem over bridged PVCs on an enhanced ATM router module. This is a configuration issue.
TCAM Layer 2 switching region space on the enhanced ATM router module interface (set to default 1024 entries) becomes exhausted. This causes local learning to not occur on the enhanced ATM router module interface which, in turn, creates the connectivity problem.
Workaround: Increase the size of the Layer 2 switching region on the TCAM using the global configuration command sdm size l2-switching #_of_entries. Save the new configuration to NVRAM and reboot the switch (the configuration takes effect after reboot).
Symptom: The Catalyst 8540 CSR might display the following messages when running Cisco IOS Release 12.0(20)W5(26) software:
There is no noticeable impact to the operation of the switch.
Workaround: Downgrade to Cisco IOS Release 12.0(20)W5(24a) software or earlier.
Symptom: On the Catalyst 8540 CSR the Underruns counter on the egress interface increment. This occurs because the Catalyst 8540 CSR is a cut through switch and it starts forwarding once a predefined number of bytes are received by the ingress interface. However, if any input errors occur (for example, bad CRC, alignment errors, or giant packet errors) after the switch starts forwarding, the switch would have already started forwarding the frame and will register an underrun error on the egress port.
To determine the cause of underruns on a particular interface, the counters on all other Fast Ethernet or Gigabit Ethernet interfaces need to be checked for input errors and eliminated.
|
Note The input error counter on the EPIF based 2-Port Gigabit Ethernet module does not increment and bad frames are dropped by the GMUX on the module. |
Symptom: After upgrading to Cisco IOS Release 12.1(13)E1, the Catalyst 8540 MSR might displaying the following error message continuously:
This might cause connectivity problems.
Symptom: Under certain circumstances, when an OC-12 interface flaps up-and-down on a Catalyst 8540 MSR running Cisco IOS Release 12.1(12)E or EY software, the switch fabric might start dropping cells on VCs exiting this interface.
Workaround: Try reloading the switch image.
Symptom: On the Catalyst 8540 MSR, after powering off and turning the power back on, the PVC configuration disappeared from running configuration but still exits in startup config.
Workaround: Either reconfigure the PVC manually or copy startup configuration to running configuration.
Symptom: The Catalyst 8540 MSR might display following error messages:
Symptom: The Catalyst 8540 MSR might suddenly crash and display a traceback.
Symptom: Internal buffers (vbufs) are exhausted, ASSERTION FAILED, and some high-Priority IPC (Inter-process Communications) drops occur.
Symptom: PNNI adjacency between directly connected Catalyst 8500 MSR switches fails to come up using the following configuration: both switches running IOS Release 12.1(12c)EY and a Catalyst 8510 MSR connected to a Catalyst 8540 MSR over an OC-3 connection. The following conditions caused the problem to appear:
1. The Catalyst 8510 MSR was upgraded from IOS Release 12.0(7)W5(15c) to IOS Release 12.1(12c)EY
2. The PNNI adjacency did not come up after Catalyst 8510 MSR was reloaded and power cycled and the following message appeared in the console log:
3. When the physical port was changed from ATM 9/1/3 to ATM 9/1/1(on the same interface module of the Catalyst 8540 MSR) the previous error message disappeared, but PNNI did not come up as shown in the following example:
4. On the Catalyst 8540 MSR, one-way PNNI adjacency was established and the following message appeared:
Symptom: On a Catalyst 8540 MSR running 12.1(12c)EY, the switch might crash if a show tech command is entered while many VCs are being created and torn down.
Symptom: Ethernet interface modules fail the Online Access Test after upgrading from Cisco IOS Release 12.0.5.W5.13 to Cisco IOS Release 12.0.22.W5.25.
Workaround: This access test failure is caused by the incompatibility of hardware version (4.1) and firmware version (2.1) of the Ethernet interface modules installed in the switch. Upgrade to the latest firmware version (3.3) to resolve this problem.
Symptom: When issuing privilege interface level 10 atm .... commands and a further subset of these commands, the prompt does not return for an extended period of time and virtual exec CPU utilization goes very high.
Symptom: A Route Processor failover on Catalyst 8540 MSR might cause a DS3 interface with scrambling enabled to disrupt traffic passing through it. This might result in CRC errors being seen on the edge device.
Workaround: Enter the shutdown and no shutdown commands on the DS3 interface of the Catalyst 8540 MSR.
Symptom: When the Catalyst 8540 receives a gratitude ARP that updates the ARP table with a new MAC address the ingress port TCAM still points to an old adjacency. Once the IP address is pinged from the Route Processor, the ingress port TCAM adjacency is updated.
Workaround: Use the clear lane le-arp card/subcard/port command to update the ingress port TCAM adjacency.
Symptom: A Cisco 8540 running IOS Release 12.1(12c)E1 may have packets for the default route routed on the Route Processor instead of the interface modules if default-network is configured. This causes an increased CPU utilization in the IP Input process.
This is caused by a switching table in the interface module not being cleared when the ip default-network command is not configured. This leads to traffic being switched or dropped incorrectly.
Workaround: The ip route 0.0.0.0 0.0.0.0 next-hop can be used instead of the ip default-network command. The Catalyst 8540 must be reloaded with no ip default-network configuration to clear the redundant entries in the interface module switching table.
Symptom: On a Catalyst 8540 MSR switch, in the show switch fabric command display, the Rx Cells and Tx Cells counters remain at 0 under MSC3 even though traffic is flowing through the ports linked to that MSC.
Symptom: After a LAN emulation client (LEC) goes down, a router that has an enhanced ATM port adapter (PA-A3) may not be able to register a network service access point (NSAP) address with an Integrated Local Management Interface (ILMI). Several messages that are similar to the following may be logged in the log file:
This symptom is observed on a Cisco router that has a PA-A3 port adapter and that is running Cisco IOS Release 12.2(10a). This symptom is observed after the software is upgraded from Cisco IOS Release 12.2(8)T4.
Workaround: Reload the router.
Symptom: While pinging (sweep range) across a Soft PVC between two ARM (I) interface modules, cell drops occur at a rate of less than one percent.
Symptom: Cell drops are observed for OC12 interface modules with a Hierarchical VP tunnel.
The problem occurs if a Hierarchical VP tunnel is defined on interface in slot 0 and the primary Route Processor is in slot 8 and the secondary Route Processor has come up in slot 4.
The same problem can be seen if there is a Hierarchical VP tunnel defined on interface in slot 9 and the primary is Route Processor is in slot 4 and the secondary Route Processor has come up in slot 8
This occurs when the secondary Route Processor boots up and there is a Hierarchical VP tunnel on any of the interfaces that share the same MSC as the secondary RP. There are no issues if the Redundant Route Processor is never booted.
Workaround: For OC12 interface modules with Hierarchical VP tunnel use slot 2 or slot 11.
Symptom: Input errors on interface ATM0 increment one per minute. Only Input errors are incrementing and no other counters (For example, CRC and other errors).
The Catalyst 8540 switch running Cisco IOS Release 12.0(18)W5(22) might experience a memory leak in pool manager.
The system logs may indicate tracebacks similar to the following:
For further information on memory leaks, refer to the Troubleshooting Memory Problems publication at http://www.cisco.com/warp/public/63/mallocfail.shtml#subfour
Symptom: The K1 CPU on the 8-port Gigabit Ethernet interface module might reset itself, when the following message appears on the console:
CDP and other well-known multicast-MAC traffic received at rates greater than 700 Mbps by the 8-port Gigabit Ethernet interface module cause the K1 CPU to run out of memory. The K1 CPU might also malfunction by concatenating multiple packets causing getbuffer to fail in IOS.
Symptom: After upgrading the switch image, the LightStream 1010 switch might lose PNNI neighbors. When the "Auto-Config" function becomes stuck, it causes PNNI neighbor loss and prevents soft-PVCs from connecting.
Workaround: Use the shutdown and no shutdown commands on the interfaces or reboot the switch to recover.
Symptom: The IMA interface module does not generate a syslog message when the link goes down.
Symptom: A Route Processor crash occurs when address registration fails at the switch. Also, an error message is flashed to the console. This problem occurs when traffic is flowing over a Flexwan module and either a hw-module-reset or OIR has occurred.
Symptom: When using version UNI 4.0, during SVC call set ups, a Catalyst 8500 MSR switch in the "Call Received" state does not send a connect-ack upon reception of a connect. This causes the SVC to be released.
Workaround: Use version UNI 3.1
Symptom: On a Catalyst 8500 MSR or LightStream 1010 switch with a DS3 interface, the interface goes down after only 7ms of AIS and then comes back up. For example, the following message appears:
Then approximately three seconds later, the next message appears:
Symptom: When you try to upgrade the FPGA from 1.8 to A.1.9 on the carrier module C85MS-SCAM-2P with HW version 3.1, the following error message appears:
Workaround: Use carrier modules with HW version 3.0 or 4.0.
Symptom: The "ifindex persistent" feature support was addedbeginning with Cisco IOS Release 12.1(13)E.
The SNMP ifIndex persistence feature provides an interface index (ifIndex) value that is retained and used when the switch reboots. The ifIndex value is a unique identifying number associated with a physical or logical interface.
For additional information reference, Configuring SNMP IfIndex Persistence .
Symptom: Hosts connected to the Catalyst 8540 switch through an Eight Port Gigabit Ethernet module, that do not transmit data frequently are intermittently unreachable.
The connectivity to the hosts eventually recovers.
Symptom: A Catalyst 8500 MSR running Cisco IOS version 12.0(20)W5(24b) might crash with a bus error in the SNMP code.
Workaround: Disabling polling chassis MIBs might prevent the crash.
Symptom: If you disconnect the transmit cable from an E1 CBR interface on a Catalyst 8540, Catalyst 8510, or LightStream 1010 switch, the interface still appears up/up. No indication of error messages appear in the log files.
When the transmit cable is reconnected, it starts to transmit traffic again. However, if the transmit cable is disconnected multiple times, the link does not pass traffic even when the transmit cable is reconnected.
Workaround: Use the shutdown and no shutdown commands on the interface and it returns to normal, or disconnect the receive cable and reconnect it.
Symptom: On a Cisco 6400 Node Switch Processor (NSP) running Cisco IOS Release 12.2(2)B and its derivatives, using the atm ping command to test a valid and active VP might fail with the following message:
The failure occurs when running the ping towards specific destination ATM switches, and is dependent on the format of the loopback cell received from the destination ATM switches. The occurrence of this problem is difficult to predict and depends on the particular ATM switch implementation of the destination switch.
Symptom: A Cisco 6400 NSP, running Cisco IOS Release 12.1(5)DB or 12.2(2)B, displays the following error message when you use the atm ping interface atm slot/subslot/port VPI VCI end-loopback command and enter the wrong VP/VC combination:
Any future atm ping commands to any connections (both valid and invalid) always result in the same error message and the ping commands fails. It fails even if the connection is valid, and even if a VP ping is used (for example, no VC number is specified).
You can still use the IP ping command to diagnose the connectivity between the NRP2 (Node Route Processor 2) and NSP.
Symptom: Occasionally, after route processor switchover or reboot of the Catalyst 8540 MSR, there is very low usage in OC-12.The output rate of the show interface command is a 5-minute output rate 0 bits per sec, 0 packets per sec.
Workaround: Run the shutdown and no shutdown commands on the affected interface.
Symptom: If an OC-3 interface module receives AIS-P or AIS-L (and possibly other alarms) for more than 250 microseconds (two OC3-Frames) the interface changes state to "going down". This causes traffic to be interrupted for at least 4 seconds (the time after the interface comes "up" again.
|
Note This problem does not occur with OC-3 interface modules installed in LightStream 1010 switches. |
A Catalyst 8540 MSR switch with an OC-3 single mode interface module (installed in a carrier module) receiving an AIS-L or AIS-P for longer than 250 microseconds (2 SONET frames) cause the interface to change state to "going down". The interface comes up again after about 4 seconds displaying the follow messages:
Symptom: A Catalyst 8540 CSR configured for IRB/BVI does not perform MAC learning in the microcode based on the reception of ARP requests. This includes gratuitous ARPs. This might cause problems with redundancy and failover mechanisms that rely on advertising the new location of a virtual IP/MAC pair via gratuitous ARP. Gratuitous ARP updates the bridge and ARP tables of devices in the network when a failover occurs. The Cisco PIX firewall also uses this mechanism for failover.
Workaround: There is no workaround for this problem in an IRB configuration on this platform. In a bridging only configuration, this problem does not occur.
Clearing the bridge table removes the condition. After the aging period (5 minutes) the connection is also restored.
Symptom: On rare occasions, when a route processor switchover occurs the microcode download on the Enhanced Gigabit Ethernet card might fail.
Workaround: Manually reloading the interface module using epc portstuck-manual-reload interface gigabitEthernet interface-number might solve the problem.
Symptom: The Catalyst 8540 MSR might encounter a memory leak in ATMSIG processes and this might render the switch unusable after one month of operation.
Symptom: When a point-to-multipoint SVC connection is set up through a switch (root and leaf are active and cross-connected), and a request is received to add a leaf through another interface, and the allocation of this half-leg fails, the connection structures associated with this half-leg are not cleaned up. Therefore, when the connection is cleared, that failed connection cannot be released, which ties up bandwidth and VPI and VCI resources for the root half-leg of the connection.
|
Note These resources cannot be cleared using the shutdown and no shutdown commands on the interface. |
Symptom: Avaya PBX and Definity PBX interoperability testing.
The following caveats exist for signalled ATM point-to-multipoint (P2MP) connections and the debugging of issues related to them on the Catalyst 8500 ATM switches:
Symptom: The 64-bit ifHCInOctets and ifHCOutOctets counters, queried using UCD snmpget routine returns invalid values. The difference between the two values, retrieved in succession (10 seconds, 20 seconds, 30 seconds periods) is invalid for the speed of interface and known traffic on that interface. Often the difference is very close to the 32-bit maximum value, indicating a memory or network-byte ordering problem. These same symptoms have been noted on the show interface command output as well.
Symptom: A Catalyst 8540 MSR running Cisco IOS (tm) PNNI Software (cat8540m-WP-M), Release 12.0(20)W5(24a) RELEASE SOFTWARE, using the QUAD E3 interface module might experience a limitation to the number of Soft-VCs that can be established to it's interfaces.
Output seen on the remote configured switch indicates "NOT CONNECTED" when using the show atm vc command.
The following similar output might appear when using the debug atm sig-soft interfaces atm card/subcard/port:
Symptom: When setting up SVCs over an NNI link, one system becomes the master in terms of deciding which VPI/VCIs are assigned to SVCs. When the slave signals a Connection ID in SETUP, it may specify a VPI/VCI value. The Catalyst 8540 MSR signals the lowest VCI in the address range.
When signaled over a VP tunnel, the Connection Identifier IE formulated by the slave specifies that the VCI signalled is to be ignored.
However, when connection management allocates the half-leg for the ingress interface, if the connection ID specified in the ID matches an already-existing connection, and the connection signaled is point-to-multipoint link, the Connection Manager assumes the signaled SVC is the same as the one already allocated. This causes two SVCs point to the same VPI/VCI. This, subsequently, results in the deletion of the existing half-leg, the bandwidth allocated by the SVC lost, and the existing connection turned into a half-leg connection (dangling).
Workaround: None. The dangling half-leg can be recovered for SVCs by using the shutdown and no shutdown commands on the interface.
Symptom: You should not configure a structured CES circuit with more than 19 timeslots across a T1 ATM interface on a Catalyst 8540 MSR. While the circuit can be configured with more than 19 timeslots and will be built over the T1 ATM interface, the Catalyst 8540 MSR will discard cells on the configured VC causing errors on the emulated circuit.
With 20 timeslots configured you see cells queued and dropped (CLP0 Q full drop) on the PVC. This problem occurs with both hard and soft PVCs are configured over the T1 atm interface.
To detect the problem, use the show atm vc int atm card/subcard/port vpi vci command and confirm the Clp0 q full drops field is increasing.
Workaround: Configure the structured CES circuit to use only 19 or fewer time slots.
Symptom: The switch crashes when the IPX encapsulation is changed on Fast Ethernet or Portchannel interfaces.
This might occur after you change encapsulation and then perform a shutdown/no shutdown.
Symptom: On the LightStream 1010 switch, a PNNI PVC link on an NNI interface might flap after the link stabilizes and the ATM PNNI VC component does not come back up.
Workaround: "Bounce" the PNNI process using the no atm router pnni and atm router pnni configuration commands to disable and enable the PNNI processes.
Symptom: Many PHY parity errors occur on the traffic going through the OC-12 interface module. This causes PHY Parity Error interrupts due to high CPU utilization (increasing to approximately 90 percent) during route processor switchover.
This occurs because the PHY Parity Check bit in the SMR register is set to "1" (enabled) during route processor switchover. Then SMR register is set from 0x0 to 0xF during switchover, enabling the PHY Parity Check bit. The default value of this register should be 0x0 (PHY Parity Check disabled).
Symptom: EIGRP does not work on a BVI interface. The BVI interface cannot receive or generate EIGRP hello packets.
Symptom: A Soft VC or Soft PVC connecting two ATM interfaces in the same Catalyst 8540 MSR might become stuck for no reason.
Workaround: Remove and reapply the Soft VC configuration on the source ATM interface.
Symptom: The Catalyst 8540 MSR switch might crash if OAM enabled PVCs are configured between the Catalyst 8540 MSR switch and a Nortel switch.
|
Note Disabling OAM management on the Catalyst 8540 MSR side of the OAM PVC does not solve the problem. |
Workaround: Disable OAM management on the Nortel side of the PVC.
Symptom: The values of input and output bytes on an ATM interface do not increment on successive SNMP queries. Increments in the values appear after 5 or 6 successive queries (approximately 25 seconds).
Symptom: After OAM detects a failure on a PVC terminating on the ATM Router Module (ARM), it fails to remove the adjacency, the directly connected route, and any additional route pointing to the next hop reachable over the failed PVC. This condition might stop traffic.
Workaround: There is no work-around, other than to perform an admin shutdown of the ARM subinterface (if the PVC is the last or only PVC on that subinterface). Alternatively, you could remove the PVC until the problem has been rectified.
Symptom: When the Cisco ATM switch is running UNI 4.0 with a Fore or Marconi switch, it might releasing a call because of unsupported traffic parameters.
This occurs when the Cisco ATM switch is connected to the other vendor equipment and configured to operate with UNI 4.0 version across the link and as a non-negotiated link. If any traffic parameter values are modified the Cisco ATM switch treats this as fatal error and releases the call.
Workaround: Hardcode the UNI version to 3.1
Symptom: On Frame Relay soft VCs, all frames sent with DE (discard eligibility) bit set are dropped at the serial interface even when the UPC is configured as "tag-drop" for the softVC.
Symptom: On a Frame Relay to ATM Soft VC, all the frames sent with the DE bit set are dropped at the serial interface even when the UPC intent is configured as "tag-drop" for the Soft VC.
Symptom: When using ATM Frame Relay IWF on a Catalyst 8500 MSR running Release 12.0(18)W5(22) or later, the output queue of the pseudo-ATM interface might go to 40/40 and remain there even if no traffic is going through the switch on the ATM-FR circuits.
Symptom: Prefix entry pointing to invalid adjacency in EPIF Patricia tree.
Symptom: On an ATM router module (ARM) that is running Cisco IOS Release 12.0(13)W5(19c), the ARM port may become stuck when a backup server is moved to a different switch.
Workaround: Configure the epc port-reload global configuration command for autorecovery on the stuck ARM port.
Symptom: When a port on a Catalyst 8540 CSR is configured as a Snoop (monitor) interface, the traffic on the Snoop interface appears corrupted. Sniffing the same traffic on the attached Catalyst switch shows that the traffic itself is not corrupted. The issue is that the Snoop interface does not provide reliable information to the monitoring station attached to that interface.
Symptom: LightStream 1010 switches running 12.0(X)W5 Cisco IOS may not completely adhere to the ITU-T Q.2971 "B-ISDN DSS2 UNI Layer 3 Specification for Point-to-Multipoint Call/Connection Control". This could affect interoperability.
Workaround: Configure UNI Version 3.1 on the LightStream 1010 ATM interfaces if the point-to-multipoint interoperability issue is observed.
Symptom: You may see spurious memory access at atom_VCConn_nodecmp during a route processor switchover.
Symptom: Occasionally after a system crash or route processor switchover you may see a PVC connection that exists in the interface software configuration but not does appear configured in the interface hardware.
Workaround: Perform an OIR on the interface module with the failed connection or perform a route processor switchover to restore the connection on the interface hardware.
Symptom: ATM PVCs configured on the ATM0.X subinterfaces might appear under the ATM0 main interface. This leaves the subinterfaces with out ATM PVCs and no connectivity. This only occurs after a switch reload, power cycle or using the force-failover main-cpu command on Catalyst 8540 MSRs running Cisco IOS Release 12.1(7a)EY, 12.1(7a)EY1, or 12.1(10)E.
Workaround: Use the no sync dynamic-info command to disable sync dynamic-info.
Symptom: If configuring RFC1483 bridging on the ATM router module, when certain RFC 1483 bridging PVC cable connections are unplugged the Catalyst 8540MSR CPU utilization will become very high. This could last a few hours until you shutdown the corresponding bridge-group subinterface on the ATM router module. Only shutting down the physical ATM port will not help.
Workaround: Shutdown the corresponding bridging group subinterface on ATM router module.
Symptom: Multiple Cisco products contain vulnerabilities in the processing of Simple Network Management Protocol (SNMP) messages. The vulnerabilities can be repeatedly exploited to produce a denial of service. In most cases, workarounds are available that may mitigate the impact. These vulnerabilities are identified by various groups as VU#617947, VU#107186, OUSPG #0100, CAN-2002-0012, and CAN-2002-0013.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-malformed-snmp-msgs-pub.shtml.
Symptom: The Catalyst 8540 reboots if you try to add a point-to-multipoint leaf to the point-to-multipoint root from Ciscoview ADP fileset for Catalyst 8540 version 5.0.
Symptom: Excessive CLP0 discards on TSCAM for PD enabled VCs.
Symptom: Multicast packets of some specific lengths (121 bytes to 240 bytes) cause a portstuck condition on the ATM router module interfaces.
Symptom: SSH fails with CRC-check failed error message some times.
Symptom: The Peak Cell Rate sent in the ATM Traffic Descriptor Information Element in the ATM Signalling SETUP messages for CES IWF circuit Soft PVCs does not conform to the standard.
The PCR signalled is always greater than or equal to that needed.
This has no effect on the set up of connections to other Catalyst 8540, Catalyst 8510, and LightStream 1010 ATM switches. These same calls may not be accepted by systems from other vendors.
Workaround: Initiate the connection using the other vendor equipment.
Symptom: The IRB connection has no connectivity in a native VLAN across ISL/dot1q Gigabit Etherchannel in the same bridge-group. However, there is connectivity on other VLANs.
Workaround: Configure a dummy VLAN as native VLAN on the dot1q trunk.
Symptom: If you use the no negotiation auto command in interface config mode on a 2-port Enhanced Gigabit Ethernet interface module with GMAC-D2 (hw-version 6.0 onwards), any packets larger than 1518 bytes or less than 64 bytes are filtered by the GMAC (Gigabit Ethernet Media Access Controller).
Workaround: Reload the particular interface using the epc portstuck-manual-reload interface card/subcard/port command.
Symptom: The Catalyst 8540MSR and LightStream 1010 console hangs when using the hw-module {slot number | subslot subslot/subcard} reset command on the Frame Relay E1 interface nodule.
Workaround: Shutdown all controllers in the module before using the hw-module {slot number | subslot subslot/subcard} reset command.
Symptom: Load balancing between provider edge (PE) to provider (P) switches and provider edge to provider edge does not work. If MPLS is enabled on the switch router running Release 12.1 software, MPLS might not re-resolve all dependant routes for a path if you enter the shut/noshut or the clear ip route commands on the outgoing interface of the next hop router.
Symptom: Unusual delays in Frame Relay VC counters update on Frame Relay ATM interface modules.
Symptom: Frame relay PVC goes down and remains down after enabling the OAM feature and performing a shut / no shut on the serial interface. However, traffic flow is not affected through the PVC even though it appears down.
Workaround: Disable OAM and shut/no shut the serial interface to force the interface to appear back up.
Symptom: The show ip traffic command displays a constant incrementing counter for "Drop No Route," but, there is a default route learned via OSPF in our routing table. Also, the show cef drop command displays numerous drops for "no route," but the debug ip cef drop command does not display any output.
Symptom: When an IMA interface module is installed in the switch chassis, and if "loopback PIF" is configured on any OC-3 or OC-12 interface, loopback is NOT reflected when queried through SNMP. Loopback is NOT actually being set.
Symptom: Globally changing TDP to LDP or changing LDP to TDP sometimes causes a loss of neighbors.
Workaround: Following is a four-step work-around:
1. Configure no tag-switching ip on both sides.
2. Configure the desired protocol at each end.
4. Configure tag-switching ip at each end.
Symptom: If PNNI continuously receives a high rate of corrupted PTSP packets over a long period of time, it can cause a large number of internal node numbers to be generated for bogus Node IDs. If the number of internal node numbers reaches 1032, it can cause a crash.
Under normal conditions, PTSP packets should have a very low rate of being corrupted. But if PNNI interfaces are tunneled through a network where the connections are rate limited to a too low rate it can force cell drops which can corrupt packets.
Workaround: Troubleshoot and remove the cause of PTSP packet corruption.
Symptom: A point-to-multi point failure might occur if a physical hardware connection does not exist but a virtual software connection is configured. Due to the connection delink failure the following error message appears on the console:
Symptom: A Catalyst 8540 MSR with an IMA interface module connection with an IMA interface connection to a Catalyst 8510 MSR fails if the Catalyst 8510 MSR interface is reset. You see the following error on the Catalyst 8540 MSR:
For example, the show controller atm command for interface 2/0/0 also displays the following:
Workaround: OIR of the carrier module clears the failed state of the IMA interface module and restores service.
Symptom: There is a 1 percent loss in ping packets to adjacent node with bidirectional traffic.
Symptom: The ATM router module has only 147 Mbps of resources available on the ATM interfaces. The following display shows the available bit rate for an ATM router module ATM interface:
Symptom: You might see a Bus Error exception at get_slot_ptr while trying to do the continuous snmpwalk on the ciscoLS1010SubModuleGroup object of CISCO-RHINO-MIB and simultaneously toggling the redundant power-supply after at least one route processor switchover.
Symptom: Inverse ARP does not succeed for a Frame Relay PVC terminated on ATM router module.
Symptom: The enhanced ATM router module subinterface counters do not get updated.
Symptom: When reloading the switch the following error message appears after a varying number of SVCs are set up.
Symptom: A Simple Network Management Protocol version 3 (SNMPv3) user is created by using message digest 5 (MD5) authentication with the following commands:
An SNMP walk is performed, the configuration is saved, and the switch is reloaded.
It is working and a debug snmp header shows this:
A second SNMP walk is performed:
After the second SNMP walk is performed, the command does not return any output and the debug snmp headers show this:
Symptom: PNNI and SSCOP signaling does not come back up on the Catalyst 8540 MSR OC48 interfaces after a powerlessly.
Symptom: Ping fails when one of the two parallel soft VCs is missing.
Workaround: Use clear bridge command to reset bridge forwarding cache.
Symptom: LDP session does not go down when you shut the enhanced ATM router module interface. When tag-switching is configured on a Fast Ethernet interface and the controlling ATM router module is either not configured or shutdown, TDP will come up but the tag packets received on the Fast Ethernet interface will be dropped because there is no controlling ATM router module to process the packets.
Workaround: Make sure the Fast Ethernet interface is linked to an active controlling ATM router module.
Symptom: An ATM router module interface with a PVC configured might experience a port stuck condition.
Symptom: Once the route processor switches over the following error message is seen on new Primary if we have a Gigabit processor interface module:
Enter the show diag online access command to get more details about the failure.
Symptom: Configuring different encapsulations on 2-port Gigabit Ethernet subinterfaces clears the existing active configuration when multiple subinterfaces are present on a main interface.
Workaround: All subinterfaces have to be configured with the same encapsulation (either 802.1 Q or Inter-Switch Link [ISL]).
Symptom: The counter "Rx Frames with DE Tagged Locally" (counting DE bits tagged locally) should increment for all frames above the CIR (committed information rate). This conforms to the policy feature available on the Stratacom ATM switches.
Symptom: A tag switching traceback might appear when an interface is shut.
Symptom: A crash occurs while configuring BVI/eigrp, or while powering off the redundant power supply.
Symptom: Catalyst 8540 CSR eight port Gigabit Ethernet interface modules fails to run CLNS.
Workaround: Update to Cisco IOS release 12.1(11b)E.
Symptom: A Catalyst 8540 MSR locks up when configuring ATM port snooping. The switch lockup can occur if ATM port snooping is configured without an analyzer connected to the snoop port.
Workaround: 1.- Load the most recent version of Cisco IOS.
2.- Have the analyzer connected to the snoop port prior to configuring ATM port snooping. Keep the analyzer connected until the snoop configuration is removed.
Symptom: When a circuit emulation service (CES) circuit that is carrying traffic is removed, no warning message is shown.
Symptom: When running Cisco IOS Release 12.0(18)W5(22) on a Catalyst 8540 MSR, or on a LightStream 1010, interoperability problems occur when peers run an older Cisco IOS version, and tunnels and SVC/Soft VCs are used.
Workaround: Upgrade all switches to the most current Cisco IOS release.
Symptom: All MPLS VPN connectivity is broken on Cisco 7500, Cisco 7200, and all common platforms if there is a TCATM link between the two provider edges (PEs) that falls in the IGP path and LSP. The routers are disabled from initiating headend VC request over TCATM link.
Symptom: Point-to-multipoint PVCs that are configured by using SNMP are not preserved across route processor switchovers.
Workaround: Disable the dynamic synchronization feature.
Symptom: When a Catalyst 8540 MSR has a large number of inverse multiplexing over ATM (IMA) port adapter modules, a message similar to the following is generated:
Symptom: On the CES module interface, the status reads UP/UP and the status of the PVC to that interface is UP in even though there is no physical connection at that port.
Workaround: Perform shutdown and no shutdown on the interface to clear the erroneous status.
Symptom: When using a Packet Over SONET card, the Open Shortest Path First (OSPF) routes do not come up after a route processor switchover, even though they were up before the switchover.
Symptom: The switch might reload when VP tunnels are created and removed.
Symptom: Untagged packets are bridged between 8-port Gigabit Ethernet subinterfaces in the same card. This happens even when they are part of different bridge-groups.
Workaround: Configure a different native VLAN for each 8-port Gigabit Ethernet interface with subinterfaces in the same card.
Symptom: The Soft-VC permanent virtual connection (PVC) status is indicated as ACTIVE only when the Soft VC is established, and its connection state is UP. If the Soft VC is not connected, the source end of the Soft VC indicates the PVC status as INACTIVE instead of ACTIVE, and the destination end of the Soft VC does not exist, and therefore indicates the PVC status as DELETED.
Symptom: On a Catalyst 8540 MSR, an SNMP query on the table ciscoLS1010PortTable, or on the object ciscoLS1010PortIfIndex, might result in a crash.
Symptom: The Management Information Base (MIB) object "ifAdminStatus" shows "UP" for an ADMIN DOWN E1 Controller after a reload or a route processor switchover.
Workaround: Enter the no shutdown/shutdown command sequence on the controller.
Symptom: After disabling the synchronization of both the running configuration and the startup configuration, a switchover results in connection installation failure, and the failure of all Layer 3 and ATM router module card downloads.
Symptom: In a primary/secondary redundant router configuration, virtual-circuit cross-connections and virtual channel link (VCLs) that are in the primary router and are deleted by using the Simple Network Management Protocol (SNMP) are still present in the secondary router. Minutes after the configuration change, the deleted elements are still present in the secondary router. If SNMP is used to write the running configuration to the startup configuration, a message is generated that indicates the configuration was received on the secondary router. When the primary router is reloaded, the secondary takes over, but does not reflect the change in its running configuration, even though the startup configuration correctly indicates the cross-connects/VCLs are deleted.
Symptom: After a reload of the primary router in a primary/secondary redundant Catalyst 8540 configuration, the secondary router cannot fetch as many of the elements of the atmVcCrossConnectTable as are known to exist. The following message appears when a get is attempted, and fails, on the table:
Symptom: When Frame Relay/ATM Network Interworking (FRF.5) is configured on a Catalyst 8540, traffic above the peak information rate is dropped, and the INPUT ERROR counter is incremented, rather than the INPUT DROPS counter.
Symptom: With a Frame Relay-ATM Soft-VC set up in FRF5, UPC on the passive side is always set to PASS, regardless of the hard setting on the serial interface with the frame-relay upc-intent tag-drop command. The default is PASS. When this is changed to tag-drop, the configuration does not reflect the change and the show vc int serial command always shows the UPC intent as PASS.
Symptom: Cisco Discovery Protocol (CDP) does not work over Portchannel platforms.
Symptom: After switch processor switchover, interfaces that were up prior to the switchover become administratively down.
Workaround: After switch processor switchover, enter the no shutdown command to make the interface up.
Symptom: Use of the epc portstuck-manual-reload command on a port channel causes a Catalyst 8540 to crash.
Workaround: The epc portstuck-manual-reload command should be used only on physical ports; it should not be used on logical ports. If a port-channel member needs to be reloaded, individually reload each physical port in the port channel. Allow approximately 1 minute for the port to reload/recreate the VCs, before using this CLI on the next port.
Symptom: After the simultaneous rebooting of switches terminating the active and passive side of Soft-VC for FRF5, randomly Soft-VPC stays up but, traffic might be dropped on the Frame Relay interface module. This might occur either on the active side of Soft-PVC or on the passive side of the call.
The Frame Relay interface module starts forwarding traffic only after you use the shutdown and no shutdown commands on the serial interface.
You might see the following error message when you reset the Frame Relay interface module:
For additional details, refer to DDTS CSCdv17817.
Symptom: The Catalyst 8540 MSR needs MIN VPI configuration capability to connect to a PBX VSI. Otherwise, the Catalyst 8540 MSR cannot tear down on a Soft PVC due to VPI/VCIs.
Symptom: After the Tag Distribution Protocol (TDP) toggles from down to up ("flaps") on the Label Controlled ATM (LC-ATM) interface, it takes a long time for the interface to become TDP ready. Entering the show tag-switching tdp discovery command might indicate that TDP is not ready, and TVCs might still be allocated on the interface. This can occur under stressful conditions in which cross-connections fail to be de-allocated on the ATM switching fabric.
Symptom: Catalyst 8540 MSRs connected in a ring configuration (via OC-48 modules) experience problems recovering from a power outage. Symptoms include OC-48 interfaces on one side of the connection being DOWN/DOWN while the directly connected interface is UP/UP.
Workaround: This problem occurs only as a result of a bad clock configuration on the entire network. Power cycle the router, then restart it from the command line; after this has been done, enter the shutdown/no shutdown command sequence.
Symptom: Single bit errors have been observed on CES circuits originating on the same interface module if two other circuits always carry non-spec-conform AAL1 SNP for SN=0. Only this very high number of SNP errors in 1/8 of all AAL1 cells causes the issue. Multiple SNP corrections that could be seen in production networks are handled correctly without data-loss or corruption.
This is an interoperability issue with a Lucent PSAX 2300.
Symptom: The unframed mode is not preserved when transiting across route processor switchovers.
Workaround: Delete the serial interface, and use the CLI to recreate it.
Symptom: When the shutdown/no shutdown command sequence is entered for a port in a CES card, a burst of bit errors can be observed on the circuit on some other port of the same port adapter.
Symptom: Under stressful conditions such as large topology changes, TVC cross-connections might fail to be removed from the ATM switching fabric, causing the TC-ATM function to repeat attempts to remove the TVCs. This might lead to the TC-ATM state process entering a bad state, and to an error message being displayed.
Symptom: Not all of the contents of the atmVcCrossConnectTable can be seen after the removal and re-insertion of a module. The message:
is seen on the console during some Simple Network Management Protocol (SNMP) get operations.
Symptom: When an E1 IMA (inverse multiplexing over ATM) adapter is inserted into a chassis in which several other IMA adapters have already been added, the clock cannot be derived from the network.
Symptom: During the Interim Local Management Interface (ILMI) batch synchronization process, only the last LAN Emulation Configuration Server (LECS) address can be successfully synchronized from the active route processor to the standby route processor. This affects redundancy support for the service registry feature only when more than one LECS address has been configured on the active route processor.
Symptom: The Catalyst 8540 MSR switch may ignore certain commands from the NVRAM after a reboot. This appears most often on switches with dual route processors.
Workaround: Create a connection traffic index and use that number for the set up of the PVC.
Symptom: When RFC 1483 bridged frames are sent with PID 0x0001 to the controller of a Catalyst 8540 Enhanced ATM router module, the frame is corrupted. This might show up as "dispose ip.formaterr" from "debug ip error output".
Workaround: If the equipment that sends the frames can be configured so that it sends RFC 1483 bridged frames with PID 0x0007 only, make that change. In all other cases, there is no workaround.
Symptom: The system crashes when changing a Bridge Group Virtual Interface (BVI) to a non-BVI using the same IP address.
Symptom: On the Catalyst 8540 MSR with OC-48 interface module, the PIF3 corrupts the egress cell on the receiving resource management cell.
When receiving a resource management cell (PTI field = 6) the OC-48c interface module sets the payload bytes 1-4 and 44-46 to "FF".
Workaround: Removing any resource management traffic allows normal operation.
Symptom: What is present in the Patricia trie in the Ethernet processor interface is out of synchronization with what is present in IP Cisco Express Forwarding (CEF). This might cause connectivity problems. This problem only exists on Ethernet processor interfaces; entries in the Switching Database Manager (SDM) on Gigabit processor interface cards are not affected.
Workaround: Find the route (for example, the route network_x) that is not consistent with IP CEF; enter (in the case of this example) the clear ip route network_x command.
Symptom: Some point-to-multipoint crossconnnect entries are missing from the atmVcCrossConnectTable when the point-to-multipoint root if-index is higher than the if-index of the leaves.
Symptom: Interfaces with Tag enabled get stuck in the TDP not ready state.
Workaround: None. The only way to bring up the Tag on such interfaces is via system reload.
Symptom: During TagVC installation, if the switch driver returns an error, the Connection Manager leaves the TagVC in the wrong FSM state. This can lead to TVCs existing on an interface when there are no tag bindings.
Workaround: None; reload the switch to clear such unused TVCs.
Symptom: When running Cisco IOS Release 12.0(13)W05(19), a bus error causes the system to restart. This occurs when an 8-port Gigabit Ethernet card with control traffic is at or near its traffic capacity.
Symptom: If a large frame or packet (more than 6096 Bytes) is received on the tag control virtual circuit (0/32 of an interface enabled for tag switching), the frame is not purged from the switch fabric. Subsequent packets received on this virtual circuit are dropped, causing the Tag Distribution Protocol (TDP) and the routing session (OSPF) to time out.
Workaround: Disable, then re-enable, tag switching on the affected interface; subsequent occurrences can be avoided by increasing the queue depth, using the following entry:
Symptom: The SNMP TRAP object ccrCpuStatusChange returns an invalid value.
Symptom: The ATM router module portstuck recovery code does not always work.
Symptom: After reloading the core switch, all neighboring switches running 12.0(16)W6(21) or 12.0(16)W6(21a) crash, and a message similar to the following is generated:
Symptom: Channel stuck detection/recovery doesn't work sometimes for ATM router module interface.
Workaround: Enter the sh epc portstuck arm command to determine whether "stat_sent" or "stat_rcvd" counters are incrementing up on only one channel of any ATM router module port. If the counters are incrementing up on only one channel, this might indicate the problem is a stuck channel; enter the epc portstuck-manual-reload interface command to manually reload the port.
Symptom: Over an 8-port Gigabit Ethernet interface, a ping to a Bridge Group Virtual Interface (BVI) fails over a dot1q subinterface which has a VLAN ID of 1 that is native VLAN.
Workaround: Configure the dot1q VLAN ID to a value other than 1 for a native VLAN (for example, configure dot1q vlan id 3 as native VLAN).
Symptom: A port of a 4-port DS3 port adapter for LightStream 1010s and for Catalyst 8540s is in a yellow or red alarm state, and stops sending DS3 framing for a brief time when the alarm is cleared from the interface and the interface transitions to an UP/UP state. The loss of frame (LOF) can be seen when the Acterna tool TBERD is connected to the TX port of the DS3 port.
Symptom: When operating at 75 to 100% of wire speed with a packet-size range of 64 to 84 bytes, a simple marking-action in an IPQoS service policy causes a port-stuck condition in an Enhanced Gigabit Ethernet processor interface card.
Symptom: If the well known VC\Qs of a tunnel are deleted and configured manually and a route processor switchover occurs then these manually configured VC\Qs might not be recognized by the new primary route processor. Instead, they are replaced with the default well known VC.
Symptom: The switch might hang during a manual switch processor "switch over" that follows a route processor switchover.
Workaround: Allow two minutes between manual route processor switchovers and manual switch processor switchovers.
Symptom: In a network running cell-mode MPLS (tag switching) with a large number of IP routes (and consequently, with many TVCs being set up), a 16-port OC-3 interface module might fail to allocate a new TVC on a bind request and print out the below error message. This occurs even though the number of TVCs currently set up does not reach the limit of VCs supported on that interface or the cross-connect interface.
Workaround: Enter the shutdown command followed by the no shutdown command on the interface for which the error message appears.
Symptom: In Cisco IOS Release 12.1(6)EY and earlier, only two equal cost IP paths were supported on Ethernet processor interface based Fast Ethernet and Gigabit Ethernet interface modules.
Workaround: Upgrade to Cisco IOS Release 12.1(7a)EY. In this release, four path load balancing for IP is available through the epc epif-4-path-lbal command.
Symptom: The system image might crash while configuring VC bundling. This might be related to a memory cleanup process and configuring or unconfiguring VC bundles quickly might increase its likelihood.
Symptom: The EIGRP Summary Routes are not properly populated in the adjacency table when a default route also exists. This affects the Fast Ethernet and ATM router module interfaces, but does not impact the Gigabit Ethernet interfaces.
Symptom: A Cisco edge services router (ESR) that is running Cisco IOS Release 12.1(2)E1 experiences interoperability problems when an ATM traffic descriptor information element is included in the CONNECT message on a non-negotiated link. Under such conditions, a STATUS message is sent with cause "invalid information element contents (100)" and call will not succeed. This problem is observed when Cisco routers are connected to other vendor switches like FORE, and occurs only when UNI version is 4.0.
Symptom: After deleting a connection, an immediate request to re-install with the same VPI/VCI results in connection-creation failure messages.
Workaround: Increase the bit map size from 32 to 64, to avoid reuse of the same VPI/VCI immediately after a call is released.
Symptom: Signaling packets are dropped between the Catalyst 8540 and its neighboring devices during a route processor switchover. This is caused by automatic status inquiries, from both sides, that occur after a switchover.
Workaround: Perform one of the following to workaround this problem:
Symptom: On the ATM router module, the HyBridge Input P might cause high route processor utilization.
Workaround: For every bridge group on the ATM router module, add a map-group with a corresponding map-list. Under the map-list configuration add a "bridge atm-vc XXX broadcast," where XXX is the VCI value created on the ATM router module subinterface.
Symptom: The no negotiation auto configuration might not be preserved in the running configuration after an OIR of an 8-port Gigabit Ethernet interface module.
Workaround: Reconfigure no negotiation auto.
Symptom: You might not be able to change the spanning tree protocol of a bridge-group.
Workaround: Remove the current bridge-group configuration and then reconfigure it with the new spanning tree protocol.
Symptom: A soft-vp created with VBR-NRT SC will be seen as a VBR-NRT Tx and Rx SC on the source; however, on the destination it might appear as a UBR on both Tx and Rx.
Symptom: When SVCs go down and OSPF recalculates IP routes and updates the routing/cef/epc tables, if the switch does not have an arp entry, it will switch by using the route processor. This occurs when the network behind that "empty" arp entry is put into the epc-table, it finds no adjacency, and switches via the route processor.
Workaround: Configure 'arp timeout 0' under the ATM interfaces that are configured with SVCs.
Symptom: After a switch processor or route processor switchover, incorrect values appear in the show interface atm display counters for the OC-3 interface module.
Workaround: Reload the switch.
Symptom: The switch experiences high route processor utilization when IPX networks are added to BVI interfaces.
Workaround: This is load related; as more IPX networks are added, route processor utilization increases. If configuring bridging over ATM router module subinterfaces, then configure a map-list for the bridged VC with the keyword bridge.
Symptom: When entering the show atm ilmi-status command the switch shows the 0.0.0.0 as a peer IP address even though a loopback address is configured.
Symptom: Cell rejects and cell drops might occur because of the nature of UBR connections and inconsistent programming of scheduler on connections going out of OC48.
Symptom: A switch router with an eight-port Gigabit Ethernet interface module might forward duplicate broadcasts when bridging is configured on a trunk.
Symptom: When running cell-mode MPLS on a network of Catalyst 8500s with redundant paths, conversion for MPLS after a routing change might take up to 4 1/2 minutes. OSPF converges normally.
Ports on the Two-port Enhanced Gigabit Ethernet interface module might get stuck after an OIR.
Symptom: If a 256K Two-port Enhanced Gigabit Ethernet interface module is hot swapped with a 64K Enhanced Gigabit Ethernet interface module, the ports in 64K module might not come up.
Symptom: The no ip route-cache cef command might disappear from the running configuration on BVI interfaces after reloading the switch.
Symptom: ATM-SOFT-PVC-MIB atmSoftPVccRetryThreshold has an incorrect default value 0 instead of 1. This incorrect value turns on atmSoftPvcCallFailuresTrap by default and impacts the usability of the feature.
Symptom: There is a noise problem with the CES PAM hardware version one.
Symptom: Ping might fail through an 8-port Gigabit interface module with dot1q/vlan 1.
Workaround: Save the configuration and reload the switch.
Symptom: A ROMMON configuration might not work properly on a slot after performing an OIR on the interface module in that slot.
Workaround: Reload the switch router.
Symptom: The CMPM carrier module shows the same serial numbers for the carrier module and the interface modules in it; however, when the show hardware command is entered, different serial numbers from the carrier module are shown for both the carrier module and interface modules.
Symptom: When video traffic is sent through an eight-port Gigabit Ethernet interface module traffic might be bursty because of packets being delivered out of order occasionally.
Symptom: The Internetwork Packet Exchange (IPX) statistics sometimes fluctuate when no traffic is flowing through the interface. The only affected functionality is IPX statistics.
Symptom: After rebooting the switch router, Ethernet interfaces might have invalid MAC addresses, causing connectivity problems over that interface.
Workaround: Enter the shutdown command and then the no shutdown command on the affected Ethernet interfaces.
Symptom: Sending a crafted control NTP packet might cause a buffer overflow.
Workaround: Include the "ntp access-group serve-only" line in the configuration of the router.
Symptom: On an OC-48 interface module, the show controllers command might show the following:
This does not affect functionality.
Workaround: Enter the shutdown command and then the no shutdown command on the interface.
Symptom: Under a heavy load, the switch router mis-orders cells going out of single-port OC-12 port-adapter modules placed in a carrier module.
Workaround: Whenever a heavy load is expected on single-port OC-12 modules placed in a carrier module, reprogram the carrier module with Carrier Module FPGA Image 1.9, and upgrade the Cisco IOS image to the latest version.
Symptom: When the routing table exceeds 50 K routes and if 8-port gigabit ethernet interface modules are installed, a CAM full condition might occurs. This leads to a port-stuck situation.
Workaround: OIR the interface module. The 8-port gigabit ethernet interface module was not designed to handle more than 50 K routes.
Symptom: When a static route to a connected interface is added and deleted when another static route is present in the same network, the packets might be process-switched.
Symptom: The Online Diagnostic Snake test, which is enabled by default, might send ILMI traps when an interface changes state to UP. This can cause clients on other interfaces to reset ILMI.
Workaround: Disable the snake test by entering the no diag online snake command.
Symptom: The following error messages might occur on a reload:
Symptom: Spurious memory access might occur at lss_arm_atm_adjacency_mac(). This happens after the following warning message:
Symptom: This condition occurs when asymmetrical routing, bridge groups, and LANE clients are configured on ATM router module sub interfaces. The bridge groups allow bridging to ELANs on non ATM interfaces and sometimes packets destined to an outside ELAN or VLAN might be sent or received over the LANE broadcast bus for a particular LANE client. The packets should instead go over a data direct vc. This is caused by a sender's default gateway being the remote BVI instead of the local BVI.
Symptom: In Front Panel View, if one member is removed from the Cluster, a particular device will be removed successfully, but others will show ports with cyan color, not reflecting the actual status of the ports.
Workaround: Let the Front Panel View refresh automatically or manual by pressing the refresh button or refresh menu item or close and reopen the Front Panel View window. Have to refresh the Cluster LED also along with the Cluster Data.
Symptom: The ifTable indexes do not match the MIB-II table indexes.
Symptom: Two adjacent ATM devices (for example, ATM port at Catalyst 8540, ATM NIC, or Cisco 7200 router) had problems performing ILMI negotiation. The result of the ILMI negotiation is VPI/VCI range fails and the following error message appears:
Symptom: The physical status might show that it is down while the IMA shows that it is up. This happens when there is a loss of frame (LOF) on the link. IMA dictates the state of the Receive Fault or Tranceive Fault on the link looking at the alarms OOCD, OOF, LOS and AIS. However, it does not need to look at LOF as a persisting LOF results in OOCD.
The physical status blindly looks for all the alarms on links to be 0. This is a cosmetic problem which will not affect the traffic on the link.
Symptom: An ATM router module interface configured for transparent bridging and in blocking state might forward certain frames.
Workaround: Depending on topology, a work-around might be to ensure that a non-ATM router module interface is in blocking state. Where this is not feasible, power cycle the ATM router module interface that is in blocking state.
Symptom: A subinterface might be stuck in the waiting state after a CPU reload. The CPU reload is displayed with the show atm statistics command. This will cause the P2MP VC count to be less than what it was before CPU reload.
Workaround: To bring the subinterface up, enter the shutdown command and then the no shutdown command on the subinterface.
Symptom: IP addresses on shutdown interfaces might be programmed as invalid host addresses after entering the epc portstuck-manual-reload command. This does not impact functionality.
Symptom: ILMI might stay in the "waitdevtype" state after a redundancy failover. This is because on an OC3 port adapter, each of the 4 ports are served by one processor interface.
Workaround: The first port needs to be set for the other three ports to be able to receive. Sometimes this does not occur on a redundancy failover. Bring up port 0, if problem is seen on ports 1-3, port 4, if problem is seen on ports 5-7, port 8, if problem is seen on ports 9-11, and port 12, if problem is seen on ports 14-15. The ports can be brought up by connecting a loopback cable, or by simply using that port.
Symptom: Under stressful conditions, tag virtual-circuit cross-connections fail to be set up, even though the input and output legs have been allocated. This can cause the input and/or output legs to remain allocated, but be in the NOT CONNECTED state.
Symptom: If SVC is configured on the ATM router module or the Enhanced ATM router module and an OIR is performed on the module, the adjacency available across the SVC will remain 'Valid' on the Ethernet port interface or Gigabit Processor interface cam. This will cause packets destined to that adjacency to go into a disappear.
Workaround: Before performing an OIR on the ATM router module or the Enhanced ATM router module, remove any subinterfaces that have SVC configurations on them.
Symptom: When an IOS configuration for the boot loader is set to an image on a SanDisk PC Card, the subsequent reboot with a configuration register setting of 0x2102 fails with the following message:
Symptom: When access is made to PNNI tables, a memory leak might occur. This only happens when an Network Management System (NMS) is running SNMP on the switch router.
Workaround: Turn off NMS polling of PNNI tables and use the commands instead for determining any PNNI information.
Symptom: An IP address might not be learned by peer switch when using ILMI-status.
Symptom: The ATM router module might get channel stuck. This stops traffic from passing through MSR. This is often initially described as a "hung" condition.
Workaround: OIR the ATM router module.
Symptom: After performing a route processor switchover several times, and then reloading only the secondary route processor and booting up again, the primary route processor might display the following error messages:
This does not impact functionality.
Symptom: NCDP uses default address of the switch for uniquely identifying the root. The default address might get corrupted on a route processor switchover. If more than one redundant Catalyst 8540 is running NCDP then NCDP might not work as expected after a route processor switchover.
Symptom: ATM router module might set the CLP of all cells to 1 when bridging is configured over a 1483 PVC. This happens for cells being transmitted over the 1483 PVC only.
Symptom: The ATM router module interface shuts down after entering the epc portstuck-manual-reload command with IP traffic.
Symptom: Spurious memory access at lss_arm_atm_adjacency_mac might occur after entering the epc portstuck-manual-reload command simultaneously on two ATM router module interfaces of two connected switch routers. There is spurious memory access to both switch routers. This has no functionality impact.
Symptom: If an 8-port Gigabit Ethernet interface module is hot swapped after configuring PAgP port channel between two Catalyst 8540 CSRs, members on the hot swapped side of the port channel move out of it while the members on the side that was not hot swapped remain in the port channel. This happens only with the 8-port Gigabit Ethernet interface module.
Workaround: After some time, PAgP might add the hot swapped interface back to the port channel. If this does not happen, configure the ports manually.
Symptom: The port stuck message might not appear into system log.
Symptom: If a static ARP is configured for one interface and then the IP address for that interface is moved to a subinterface, the static ARP entry remains associated with the original interface instead of with the subinterface.
Workaround: When the IP address is reconfigured to a subinterface off of the original interface, delete and reconfigure the ARP address also.
Symptom: After the switch has been running for over two hours it might start to lose traffic on its LANE/1483/1577 interfaces on the ATM router module. Frame interfaces (like Fast Ethernet) or non-LANE interfaces on the ATM router module (with configured pvc's) traffic passes without any problems. It doesn't matter if the traffic is going to the route processor not, part of the traffic is lost.
Workaround: OIR the module or reload the switch. Shutting down the ATM router module interfaces does not help.
Symptom: After performing an online insertion and removal of an OC48 port adapter, entering the show command and the no show commands on the OC-48 might generate the following error messages:
Workaround: Perform one more online insertion and removal and ensure that at least two minutes elapse between any two online insertions and removals.
Symptom: Telnet responses between two switch routers might be very slow.
Workaround: Replace one switch router with another that can accept ISL-frame less than 94B (for instance, the Catalyst 5000).
Symptom: After configuring an ipx network between a Catalyst 8540 MSR and a Router 7500, the Catalyst 8540 MSR displays old buffers detected messages. This does not impact functionality.
Symptom: A LightStream 1010 stops switching some VCs, and log error messages similar to the following example are generated:
Workaround: Reload the switch.
Symptom: An active Fast Ethernet interface might become administratively down after the route processor automatically switches over following entry of the test crash command.
Symptom: The display might show that oversized packets are on an Enhanced ATM router module interface when the interface is a member of a BVI. This happens even when there is no traffic except BPDU and OSPF routing updates. These "large packets" are not the real traffic transiting through the ATM router module. They are CPU-bound traffic (i.e. routing updates). The following is the message that might occur on the console:
The system recovers from this.
Symptom: After switching over the route processor several times, the following message might display:
This happens when an IMA port adapter is present in the chassis. Once the switch router boots up no functionality impact is seen.
Symptom: The ATM router module interface might indicate outgoing packets when the interface is administratively down. This does not impact the functionality.
Symptom: When there is a lot of signaling svc set up and teardown on an nni tunnel interface, calls will fail with a vpi/vci collision.
Workaround: Use a non-tunnel interface.
Symptom: The switch router might lose traffic on its LANE or 1483 or 1577 interfaces on ATM router module. Frame interfaces or non-lane interfaces on ATM router module with configured pvc's should pass traffic without any problems. It doesn't matter if the traffic is going to RP or not, part of the traffic is lost.
Workaround: The switch router will recover from this state only after an OIR of the module or a reload.
Symptom: After loading the secondary route processor running a release earlier than Cisco IOS Release 12.1(7a)EY (with the primary route processor running Cisco IOS Release 12.1(7a)EY), bringing down the secondary route processor and then reloading it with Cisco IOS Release 12.1(7a)EY might cause the secondary route processor to crash.
The following error messages might appear at the time of the crash:
Workaround: Reload the secondary route processor.
Symptom: IP routing and IPX routing over BVI on an 8-port Gigabit Ethernet interface module might fail when the interface module is removed from the bridge group.
Symptom: Cell loss on PVC connections might occur if you remove the active route processor module without using the redundancy prepare-for-cpu-removal command prior to removing the module. Using the redundancy prepare-for-cpu-removal command prevents any cell loss outage from affecting the established PVCs during removal.
Symptom: After entering the shutdown command and the no shutdown command on an ATM router module interface with more than 32 CLIP clients the following error message might display on the console:
This does not impact functionality.
Workaround: After waiting a few minutes, enter the shutdown command and the no shutdown command.
Symptom: On a Catalyst 8500 MSR performing an ATM Frame Relay internetworking function, when the Local Management Interface (LMI) indicates a permanent virtual connection (PVC) is inactive, this information is not propagated by the ATM Frame Relay code.
Symptom: When entering the shut down command on the OC-48 interface, the following traceback might be displayed with spurious memory access at snmp_trap:
This does not affect functionality.
Symptom: Entering the shutdown command on the ATM router module interface might cause CPU hogs if a large number of PVCs are configured on that interface.
Symptom: A system running PNNI with Cisco IOS Release 12.0(7)W5(15c) will reject an ATM call set up if the set up includes the 5a information element coded with associated signaling, explicit VPCI, and any VCI.
If another ATM switch sends a set up that includes the 5a information element coded with associated signaling, explicit VPCI, and any VCI, the system will release the call with cause code 35: requested VPCI/VCI not available.
Call set ups that include the 5a information element coded with the associated signaling, explicit VPCI, and explicit VCI signaling, including those made by Cisco ATM switches, are not affected by this problem. This interoperability issue exists between Cisco ATM switches and other vendor switches that do not explicitly request the VCI value in the call set up.
Symptom: Spurious memory access at pim_igmp_new_dr_querier might be seen when running PIM-SM with multicast traffic on ATM router module interfaces. This happens when DR changes are seen. This does not impact functionality.
Symptom: While sending traffic with super CAM (for example, the OC48 combo super CAM or OC12 super CAM) and enabling the online diags, then performing an OIR of the super CAM. If you use shutdown and no shutdown commands on one of the interfaces you might see the following error message:
Symptom: When the show ip cef ip address command is entered, the output might report an invalid cached adjacency for ip addresses that are reachable through the LANE interface.
Symptom: When using the Internetwork Packet Exchange (IPX), the output of the traceroute command skips the middle hop when the middle router is a Catalyst 85xx MSR, Catalyst 85xx CSR, or LightStream 1010.
Symptom: ROMMON does not work on the Gigabit Ethernet interface module.
Symptom: When OAM management is configured on a PVC of an ATM router module in order to check the end-to-end connectivity, the subinterface might stay up/up even if the remote end is down.
Symptom: The switch router might not send ICMP unreachable messages when an inbound access list is configured and being accessed on an interface module that has an ACL daughter card.
Symptom: In a multi-vendor environment, if the non-Cisco IMA interface side does not support Test pattern, as specified in Inverse Multiplexing for ATM (IMA) Specification Version 1.1 by the ATM Forum, the Cisco IMA interface status might change from up to down continuously.
Symptom: When global switch ATM address prefixes are added or deleted via the atm address command, addresses registered for existing CES circuits are not changed. Therefore, the goal of changing the switch address might not be achieved (in that CES does not change its addressing, and therefore will not accept calls using the new prefix).
Workaround: This workaround is for the primary switch address only. When the address is changed, the existing circuits can be deleted and created again, and the circuits will register addresses using the new primary switch address.
Symptom: The ATM router module might not function correctly over 20 M. When this occurs, the ATM router module loses packets or port gets stuck. This occurs even when multicast is not configured.
Symptom: The show hardware detail command does not show the actual version of the FPGA for any of the daughter cards. This shows the version of the FPGA motherboard which is misleading.
Symptom: The atm arp-server nsap command is removed from the running configuration upon reloading the switch.
Workaround: The copy startup-config running-config command will restore the original configuration.
Symptom: If you save the running configuration, you may see the following error:
This happens when you enter a write mem command or a copy running-config startup-config command. Enter a show file command to show the 127 entries of private configuration.
Workaround: Save the running configuration in a file, reload the router, and then enter a write mem command or copy running-config startup-config command.
Symptom: Although packets are being sent out from an ATM OC-12 interface module, the 5-minute output rate shown using the show interface atm command indicates 0 bits per second output. This is not consistent with the output rate shown when the show atm traffic command is entered.
Symptom: When entering the show atm interface traffic command on an ATM subinterface, the total number of cells that has passed might show as zero. This rate is incorrect.
Symptom: The Xconnect set up fails for unidirectional TVC if there is another one with a different direction and the same vpi/vci on a particular interface of the Catalyst 8540 MSR. This can be seen only if VC merge is disabled.
Symptom: If you set the ARP timers on an interface and replace the module, the startup-configuration is not loaded into the card. All ARP timers are reset to default.
Symptom: When the MRP reset button is pushed, the switch router might not boot the main image. If this happens, the switch router will eventually go into ROMMON mode.
Symptom: Under certain conditions, the BVI output queue might get stuck when queuing outgoing packets but not dispatching them to hardware. This causes the output queue on the BVI interface to grow constantly.
Workaround: Create another BVI interface and move all the traffic over to the new BVI interface.
Symptom: The output errors counter is incorrect on Gigabit Ethernet show interface command. They have a high value 4xxxxxxxxx and a clear counter command does not change it back to 0. This value can increase or decrease over time.
Symptom: IP traffic is not sent over a PVC if aal5mux encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR. If the deb atm errors command is enabled, the following error messages will appear:
Symptom: The route processor redundancy might fail if you have both PVC and bridging configured on the subinterface of the ATM router module.
Symptom: The Catalyst 8540 MSR hangs after OIR of OC-3 multimode interface module.
Workaround: Reload the switch.
Symptom: A Catalyst 8540, which correctly boots as a fully redundant system, does not complete a route processor failover. The secondary route processor, as it resumes function as the primary after a failover, displays the following error:
Symptom: The ATM router module does not strip the Ethernet pad when switching data from Ethernet to ATM. This might occasionally lead to connectivity issues since some end systems do not expect to see the pad.
Symptom: When an enhanced Gigabit Ethernet interface module sends out ISL packets with packet sizes 1531 to 1548, the output error counter on the egress port increases.
Symptom: The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module. Slot 0 subslot 0 of the carrier module can either be empty or have another card in it, and hierarchical VP tunnel configuration will still fail. However, if the mixed mode port adapter is inserted in slot 0 subslot 0 of the carrier module, then the hierarchical VP tunnel can be configured.
Symptom: The ifSpeed is reported as 100MB even when the auto-negotiation results in 10MBit.
Symptom: When using SNMP to monitor the status of each interface module and submodule in the chassis, the output does not give all interface modules. However, when entering the show hardware command, all interface modules appear.
Symptom: An 8-port Gigabit Ethernet interface module port that is shut down might come up after an OIR.
Workaround: Enter the shutdown command on the affected port.
Symptom: When a Catalyst 5500 connected to a Catalyst 8540 CSR is powered down, the BVI interface does not receive EIGRP and ospf multicast hello packets.
Symptom: The ATM router module microcode for RFC1483 did not have the ability to understand CLNS topology updates, forcing the card to drop packets. This also affected the IS-IS routing updates.
Workaround: Upgrade to the Cisco IOS release 12.0(11)W5(19).
Symptom: There is no support for SONET MIB objects in ATM uplink module.
Symptom: The router reloads when handling internetworking packet exchange (IPX) access-logging-messages. This situation may still occur if access-logging is not enabled.
You may exceed the 200 IPX network limit when the hardware is activated after being removed. When the hardware is reactivated, the interfaces that were not counted while the hardware was removed cause the limit to be exceeded.
Symptom: When auto negotiation is disabled on an enhanced two-port Gigabit Ethernet port, it is up even if the GBIC is not present.
Symptom: The static bridging command disappears from the running configuration.
Symptom: When the module is removed from the switch, the interfaces continue to show as inserted and also the IDB's are not deleted. This is not seen when time is given between the act of insertion and removal of the modules.
Workaround: Wait two minutes after OIR before inserting a new interface module into the switch.
Symptom: In the Catalyst 8540 switch, the output of a show ethernet command has lost the carrier count following the collision counter. This is a counter error only and does not actually indicate a lost carrier and does not impact the operation of the Ethernet interface.
Symptom: When two Catalyst 8540 CSRs with 2-port Gigabit Ethernet interface modules are connected back-to-back, packets are lost. On one side the counters might show input and output increasing, but the other side shows only output packets increasing. The Address Resolution Protocol (ARP) from the other side is lost, and the ability to ping the other side is lost.
Workaround: Reset the Gigabit Ethernet interface module.
Symptom: On the ATM uplink any packet routed on a point-to-point interface will be routed by the route processor.
Workaround: Do not configure point-to-point subinterfaces on the ATM uplink.
Symptom: When reloading a new image into the enhanced two-port Gigabit Ethernet interface module the ATM uplink enhanced Gigabit interface appears to have been reset. The enhanced two-port Gigabit Ethernet interface module download shows no effect on the ATM uplink.
Symptom: There is no instance of ACL card in the MIB table.
Symptom: With an encapsulation change on a two-port Gigabit Ethernet interface module, the interface no longer sends packets. It seems that it is receiving packets and sending packets to the route processor when necessary, but the packets are not sent.
Symptom: When theCatalyst 8540 is powered-up or power cycled, the shutdown/no shutdown command has to be entered on the CBR ports to activate the CBR ports.
Symptom: When two 8540 CSR switch routers are directly connected by a two-port Gigabit Ethernet interface module, a reset of one switch router does not cause the remote switch router's interfaces to go down too. The problem is caused by the reset switch router's interfaces not going down, so remote interfaces do not go down.
Workaround: Physically remove the cable from the ports or enter the shutdown command.
Symptom: In some instances, an ATM interface on a Catalyst 8540 MSR might get stuck in a going down state.
Processor utilization stays high for a long period of time. For example, for an 8K VC, the route processor stays high for approximately 720 seconds, and for 4K VCs, approximately 300 seconds.
Symptom: The prompt on the secondary route processor does not reflect the hostname of the switch router after a sync.
Symptom: When configuring region sizes you are not considering the ACL region size when checking for the total size. Configuration allows regions sizes exceeding total Tcam size. No error message is printed at the time of configuration but upon next boot you get the following error messages:
Symptom: The ip cef command does not re-enable the CEF switching on the Catalyst 8540 when it was previously disabled due to lack of memory. The Catalyst 8540 requires CEF switching but this can become disabled if insufficient memory is available. When insufficient memory is available, the following message appears:
Symptom: HVPT: Incorrect scheduling values installed for low PCR. When a HVPT with a PCR of 2 kbps is configured on a OC-3 interface, this results in the cell starving of WKVC on the main interface.
Symptom: An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.
Symptom: The switch router might reload after a bus error in handle_new_collect.
Symptom: On rare occasions the switch fails SVC set ups even when physical connectivity is established.
Workaround: Reload the switch.
Symptom: The output from the show bridge command is incomplete.
Symptom: After reloading the switch, the route processor that was the primary route processor might become the secondary route processor and the route processor that was the secondary route processor might become the primary route processor.
Symptom: When you change the port speed from 10 to 100 on a Catalyst 8540 CSR running 12.0(5)W5(13), enter the shutdown and no shutdown commands for the new setting to take effect.
Symptom: Fast Ethernet interfaces that are in shutdown mode have packet output and bytes incrementing in the show interface command.
Workaround: Enter the clear counters command.
Symptom: The root cause of this is that the HSRP specific structures are not properly updated when an interface goes down or when a card is removed.
Workaround: Remove HSRP from the configuration before removing the card.
Symptom: The above message is sometimes received. This message is can be ignored.
Symptom: When you enter the show lane client command, part of the command output includes a statement such as "LEC up for 8 hours 41 minutes". The current MIBs, such as, interface mibs, ATM mibs, and the LAN-EMULATION-CLIENT-MIB do not display this information.
Symptom: When you reload a Catalyst 8540 MSR with a redundant route processor, the secondary route processor will become the primary route processor after the reload.
The uptime shown when you enter the show version command is the uptime of the boot image. This should be the uptime of the running IOS software.
Symptom: On the Catalyst 8540 MSR switch the following object MIBs do not work as expected:
CISCO-ATM-CONN-MIB, CISCO-RHINO-MIB, OLD-CISCO-SYS-MIB, CISCO-ATM-RM-MIB, CISCO-ATM-IF-PHYS-MIB, CISCO-OAM-MIB
Symptom: The above messages may appear on the console. They are not reproducible. The message appears on subinterface ATM11/0/0.14 on the ATM router module port.
Symptom: The command show atm resources displays the number of cells in the UBR queue in an MSC and it increases continuously. The increase happens very slowly.
This occurs when traffic is sent through a Catalyst 8540 MSR at line rate. Increasing the threshold group per VC queue size does not eliminate the problem.
Symptom: Under extreme low-memory conditions, if a switch is configured with many hierarchical tunnels and LANE components configured on the CPU port of the switch (or ATM interface of a router), removing many subinterfaces or removing a few subinterfaces many times can result in a crash. This removal without first cleaning up LANE configuration results in the loss of 6400 bytes of memory.
Workaround: Delete LANE configuration on a subinterface before deleting the subinterface itself.
Symptom: When you try to connect Racal-Datacomm CSUs together using ports on the same CES interface module, timing problems might prevent the CSUs from starting up.
This section describes the following Catalyst 8540 restrictions:
The following restrictions apply to the ACL daughter card supported on the Catalyst 8540:
We recommend that you evaluate the level of CPU utilization and performance in your switch router before turning on AppleTalk. Unlike IP and IPX, AppleTalk routing and processing in the Catalyst 8540 is accomplished by the switch processor, not the interface module. This means that routing AppleTalk packets consumes more processing time than routing other protocol packets. In a switch with a sustained high CPU utilization, turning on AppleTalk could result in longer convergence times for routing protocols like EIGRP. AppleTalk packet throughput is dependent on the amount of available CPU processing power.
The four adjacent ports (such as 0-3 or 4-7) on a 10/100 Fast Ethernet interface must all use the same VLAN encapsulation, that is, either 802.1Q and native, or ISL and native.
The Catalyst 8540 MSR ATM router module does not support the following features:
|
Note This section is applicable to the Catalyst 8540 MSR switch router only. |
When assigning Ethernet interfaces to an EtherChannel, all interfaces must be either Fast Ethernet or Gigabit Ethernet. You cannot mix Fast Ethernet and Gigabit Ethernet interfaces within a single EtherChannel.
Catalyst 8500 interface modules support a maximum of six paths based on the modules and configuration To improve EIGRP or OSPF convergence, set the maximum-paths for the router or switch router, using the following command:
The maximum-paths value can be configured for the following modules:
The following restrictions apply to policy-based routing (PBR) on the Catalyst 8540 MSR and the Catalyst 8540 CSR:
|
Note The IP packet length range supported in a route map is 0-1535. A maximum of three non-overlapping length ranges are allowed per interface, including subinterfaces. |
|
Note Due to platform limitations, the set interface null0 command does not generate an "unreachable" message. |
The 8-port Gigabit Ethernet interface module is supported on the Catalyst 8540 MSR and Catalyst 8540 CSR. This section describes limitations of the 8-port Gigabit Ethernet interface module.
The 8-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 128 ports per bridge group.
If your Catalyst 8540 MSR or Catalyst 8540 CSR has an 8-port Gigabit Ethernet interface module, you cannot create a port channel that has some members on that module and some on other modules. All port channel members must reside on the same Gigabit Ethernet interface module.
Also, if your switch router has an 8-port Gigabit Ethernet interface module, port channel IDs 57 to 64 are reserved, and cannot be assigned to other external interfaces. If you assign a port channel ID number greater than 56, the system will respond with the following message:
If you have already assigned port channel IDs 57 to 64, you must reassign them before installing an 8-port Gigabit Ethernet interface module.
If your switch router does not have an 8-port Gigabit Ethernet interface module, you can assign port channel ID numbers up to 64.
The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8540:
On an 8540, the reprogram command for upgrading the FPGA on the switch processor requires power cycling the box after completing the FPGA download.
The Catalyst 8540 switch routers support extra long haul (1000BASE-ZX) GBICs. It supports a maximum of 12 1000BASE-ZX GBICs per system to comply with FCC Class A emissions (CFR 47 Part 15), or 8 1000BASE-ZX GBICs per system to comply with EN55022 Class B emissions (CISPR22 Class B).
The Catalyst 8540 supports the use of redundant route processors and switch modules. The second route processor would be installed in slot 8, and an additional switch module would be installed in slot 6.
There are some precautions that need to be taken before removing a route processor module from a chassis that is powered-up. If a route processor module that is currently running IOS is removed from the chassis in a skewed manner such that the left side of the processor comes out before the right side does, the traffic flowing through the device might stop flowing.
To avoid this, make sure the route processor module that is being removed is currently at the ROM monitor prompt; it is then safe to remove it from the chassis. One way to get the system into ROM monitor from IOS is to enter the reload command. This will work if the system is not configured to auto-boot. If the system is configured to auto-boot, it starts booting IOS again.
Since you need to ensure that a route processor is in ROM monitor before removing it, the redundancy prepare-for-cpu-removal command has been added to take the system to the ROM monitor prompt. Execute this command on the route processor being removed before removing it. Once this command is issued, the route processor will go to the ROM monitor prompt and stay there even if the system is configured to auto-boot. At this point it is safe to remove the route processor from the system.
If a Catalyst 8540 has three switch modules, then by default the switch modules in slots 5 and 7 come up as active, and the one in slot 6 comes up as the standby. If you wish to change this default, there is a command that lets you select the "preferred" switch module slots. This command is a privileged exec level command with the following format:
redundancy preferred-switch-card-slot slot#1 slot#2
Two unique preferred slots must be specified. The range of the slot value is 5 to 7. If one of the preferred slots is not a currently active switch module, you are informed of this and asked if the system should change the active switch modules to the preferred switch modules. If such a switch-over occurs, all the active connections in the system will be reinitialized. If you wish to continue, then the preferred switch modules become active, and the other switch module becomes the standby. This configuration will remain in effect until either one of the active switch modules is removed.
The preferred switch module configuration is preserved across route processor switch-overs. However, the preferred switch modules setting will be lost if the system is power-cycled or if both route processors are reloaded to the ROM monitor.
The autonegotiation feature for speed and duplex on 10/100BASE-T Ethernet ports defaults to "on." This means that for each port, the Catalyst 8500 CSR automatically detects the port speed (10 Mbps or 100 Mbps) and duplex of the peer port, if that port also autonegotiates.
To override autonegotiation and set a port to 10 Mbps operation, enter the following command:
To set a port to 100 Mbps operation, issue the following command:
To set the duplex value for a port to full-duplex, issue the following command:
To set the duplex value for a port to half-duplex, issue the following command:
 |
Caution If you connect a Catalyst 8540 CSR switch router running Cisco IOS Release 12.0(5)W5(13) software to a router or switch running in forced full-duplex mode, you might encounter symptoms such as high collision rate or reduced throughput, as the Catalyst 8540 CSR unsuccessfully tries to autonegotiate with the other device. When autonegotiation fails, the Catalyst 8540 defaults to half-duplex operation, which causes a mismatch between it and the other device. Possible workarounds include forcing the Catalyst 8540 CSR to operate in full-duplex mode or removing the full-duplex command from the other device. |
You can use Catalyst 8540 CSR interface modules in a Catalyst 8540 MSR chassis with an MSR route processor and switch modules. Use only CSR (Ethernet) interface modules, and load the CSR software image on the MSR.
When you connect a Catalyst 8540 CSR to a Catalyst 5000 100BASE-FX MM Ethernet interface module using ISL, ensure that the hardware version on the Catalyst 5000 interface module is 1.3 or higher. You might experience connectivity problems between the Catalyst 8540 CSR and the Catalyst 5000 if the hardware version on the Catalyst 5000 Ethernet interface module is lower than 1.3.
The Catalyst 8540 MSR and 8540 CSR systems have been certified as Y2K Compliant. For more information, see the following URL: http://www.cisco.com/warp/public/752/2000/.
The following documents provide information related to Catalyst 8540 switch routers.
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have 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.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
http://www.cisco.com/en/US/partner/ordering/index.shtml
http://www.cisco.com/go/subscription
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top 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: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
To obtain customized information and service, you can self-register on Cisco.com at this URL:
The Cisco 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 website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
You can use the Cisco TAC website 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 website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
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.
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
http://www.cisco.com/go/packet
http://www.cisco.com/go/iqmagazine
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Wed Jul 30 11:22:17 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
