|
|
Catalyst 8510 and LightStream 1010 Switch Cisco IOS Release 12.1(10)E
Text Part Number: OL-1198-04 Rev. B0
This document describes the features and caveats for Cisco IOS Release 12.1(10)E software for the Catalyst 8510 and the LightStream 1010 switch.
 |
Note All information pertains to both the Catalyst 8510 and LightStream 1010 switch platforms, unless differences between the platforms are noted in the text. |
This document includes the following sections:
The Catalyst 8510 and LightStream 1010 switch provide 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.
|
Note The ATM switch processors (hardware version 4.0 or higher) and all port adapters can be installed in the Catalyst 5500 switch chassis. |
The Catalyst 8510 CSR belongs to a class of high-performance Layer 3 switch routers. It is optimized for the campus LAN or the intranet and provides both wirespeed Ethernet routing and switching services.
This section describes the system requirements for Cisco IOS Release 12.0 and includes the following sections:
The DRAM memory configuration is 64-MB DRAM (MEM-ASP64M), which is the default for both the Catalyst 8510 and the LightStream 1010 switch platforms.
Table 1 lists the default Flash and DRAM memory for the Catalyst 8510 CSR, as well as memory upgrade options.
Table 1 Catalyst 8510 CSR Default Memory and Upgrade Options
| Memory Type | Catalyst 8510 CSR Defaults | Upgrade Options |
|---|---|---|
To download and store a copy of the Catalyst 8510 CSR software image, we recommend using a minimum 20 MB Flash PC Card, which will allow you to have two or more images installed at the same time.
The Catalyst 8510 CSR boots from its onboard Flash memory by default. To change this default to boot from a Flash PC Card instead, you must change the configuration register setting to 0x2102. Refer to the Layer 3 Switching Software Feature and Configuration Guide for more information.
Table 2 lists the interfaces supported by both the Catalyst 8510 MSR and LightStream 1010 switch and Cisco IOS Release 12.1(10)E and their minimum software release requirements. All platform specific requirements are noted in the table. Table 3 lists this information for the Catalyst 8510 CSR.
|
Note Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8510 and LightStream 1010 hardware. |
Table 2 Catalyst 8510 MSR and LightStream 1010 Interface Modules and
Minimum Software Required
| Part Number | Description | Minimum Software Version Required |
|---|---|---|
4-port T1 (circuit emulation) with RJ-48 interface port adapters |
||
4-port E1 (circuit emulation) with RJ-48 interface port adapters |
||
4-port E1 (circuit emulation) with BNC interface port adapters |
||
ASP1 with FC-per-flow queuing (FC-PFQ3) |
||
Catalyst 8510 MSR: S851R2-12107EY LightStream 1010: SL10R2-12107EY |
| 1ASP = ATM switch processor.
2FC-PCQ = feature card per-class queuing. 3FC-PFQ = feature card per-flow queuing. 4IMA = inverse multiplexing over ATM. 5The LightStream 1010 switch requires the ASP-C with FC-PFQ to support the ATM router module. 6ACL = access control list. |
Table 3 Catalyst 8510 CSR Interface Modules and Minimum Software Required
| Part Number | Description | Minimum Software Version Required |
|---|---|---|
| Route Processors, Switch Cards, and Daughter Cards | ||
| Gigabit Ethernet Interface Modules | ||
| Fast Ethernet Interface Modules | ||
To determine the version of Cisco IOS software currently running on either the Catalyst 8510 or the LightStream 1010 switch, log in to the switch and enter the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
Some of the port adapters supported on the Catalyst 8510 and LightStream 1010 switch 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/atm/c8540/fpga_rel/index.htm
For information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8510 and LightStream 1010)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.
The Cisco IOS release 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 Cisco IOS software feature sets available for the Catalyst 8510 MSR and LightStream 1010 switch in Cisco IOS Release 12.1(10)E. Table 5 lists the software feature sets available for the Catalyst 8510 CSR.
Table 4 Feature Sets Supported by the Catalyst 8510 MSR and LightStream 1010 Switch
| 1SNMP = Simple Network Management Protocol.
2PPP = Point-to-Point Protocol. 3SLIP = Serial Line Internet Protocol. 4IP = Internet Protocol. 5NTP = Network Time Protocol. 6TACACS+ = Terminal Access Controller Access Control System Plus. 7VCCs = virtual channel connections. 8VPCs = virtual path connections. 9IISP = Interim-Interswitch Signaling Protocol. 10LANE = LAN emulation. 11LEC = LAN emulation client. 12LES = LAN emulation server. 13BUS = broadcast and unknown server. 14LECS = LAN emulation configuration server. 15ASP = ATM switch processor. 16ARP = Address Resolution Protocol. 17OAM = Operation, Administration, and Maintenance. 18RMON = Remote Monitoring. 19MCR = minimum cell rate. 20You can download the Catalyst 8510 software image on a LightStream 1010 switch to support L3-ATM (via the ATM router module). However, the LightStream 1010 switch software image does not include support for the ATM router module. |
Table 5 Feature Sets Supported by the Catalyst 8510 CSR
| 1redundancy |
Table 6 lists the release names, versions, and part numbers used with the Catalyst 8510 MSR and LightStream 1010 switch. Platform-specific information is noted in the table. Table 7 lists the release names, versions, and part numbers used with the Catalyst 8510 CSR.
Table 6 Release Name to Version and Part Number Matrix for Catalyst 8510 MSR and LightStream 1010
| Release Name | Release Version | Part Number |
|---|---|---|
Catalyst 8510 MSR: S851R2-12105EY |
||
Table 7 Release Name to Version and Part Number Matrix for Catalyst 8510 CSR Switch Routers
| Release Name | Release Version | Part Number |
|---|---|---|
This section includes new features that appear in this and previous releases of Cisco IOS release 12.1 software. The new features are sorted by release number.
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in
Cisco IOS Release 12.1(10)E:
There are no new features for the Catalyst 8510 CSR in Cisco IOS Release 12.1(10)E.
There are no new features in Cisco IOS Release 12.1(7a)EY1.
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in Cisco IOS Release 12.1(7a)EY:
The following new features are available for the Catalyst 8510 and LightStream 1010 switch routers in Cisco IOS Release 12.1(6)EY:
The following new features are available for the Catalyst 8510 and the LightStream 1010 switch in Cisco IOS Release 12.1(5)EY1.
This section lists the caveats and corrected caveats for each release. Use Table 8 to determine the status of a particular caveat for the Catalyst 8510 MSR or the LightStream 1010 and its relevancy to your software release. Use Table 9 to determine the status of a particular caveat for the Catalyst 8510 CSR and its relevancy to your software release. In Table 8 and Table 9, "C" indicates a fixed or closed caveat, and "O" indicates an open or unresolved caveat. Platform specific caveats are appropriately indicated.
Table 8 Caveat Matrix for Catalyst 8510 MSR and LightStream 1010
| DDTS # | 12.1(10)E | 12.1(7a)EY1 | 12.1(7a)EY | 12.1(6)EY | 12.1(5)EY1 |
|---|---|---|---|---|---|
CSCdv39328 |
|||||
CSCdv32093 |
|||||
CSCdv15238 |
|||||
CSCdu86398 |
|||||
CSCdu82922 |
|||||
CSCdu56774 |
|||||
CSCdu20618 |
|||||
CSCdt96927 |
|||||
CSCdt62215 |
|||||
CSCdt05674 |
|||||
CSCds78385 |
|||||
CSCdm04186 |
|||||
Table 9 Caveat Matrix for Catalyst 8510 CSR
| DDTS # | 12.1(10)E | 12.1(7a)EY1 | 12.1(7a)EY | 12.1(6)EY | 12.1(5)EY1 |
|---|---|---|---|---|---|
This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8510 switch and the LightStream 1010 switch.
|
Note The maximum number of ELAN LES/BUS pairs that the ATM switch processor interface supports is 10. On configuring a Frame Relay NIW/SIW PVC, a small number of discarded frames are occasionally seen due to CRC errors. These discards happen even without passing traffic. |
Symptom: Configuring different encapsulations on 2-port Gigabit Ethernet subinterfaces clears the existing active configuration when multiple sub-interfaces 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: 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 IOS version, and tunnels and SVC/Soft VCs are used.
Workaround: Upgrade all switches to the most current IOS release.
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: When both the primary and secondary route processors are up and running, on the secondary the output of the show atm interface resource atmx/y/z command for an inverse multiplexing over ATM (IMA) interface shows all the available cell rates as zero. This results in loss of all VCs (that pass through the IMA interface) requiring guaranteed service (such as CBR, VBR, ABR with MCR, UBR).
Workaround: None. Upon switchover, the new primary route processor recovers from the problem.
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: An LightStream 1010can reload when VP tunnels are created and removed.
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: 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: 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 setup 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 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: 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: After a reload, a permanent virtual connection (PVC) is not set up.
Workaround: PVCs should be created either 1) using connection traffic table (CTT) rows created through use of the Simple Network Management Protocol (SNMP) or through the command line interface (CLI), or 2) using the default CTT rows (1 - 6). One way to determine whether a CTT row has been created through the SNMP or CLI is to enter the show running-config command; only CTT rows that can be used to create PVCs are listed in the output.
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:
atm threshold 2 max-queue-limit 511
Symptom: The SNMP TRAP object ccrCpuStatusChange returns an invalid value.
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: 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: In a network running cell-mode MPLS (tag switching) with a large number of IP routes (and consequently, with many TVCs being setup), 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 Fast Ethenet and Gigabit Ethernet interface modules that were based on an Ethernet processor interface.
Workaround: Upgrade to Cisco IOS Release 12.1(7a)EY; in that release, four-path load balancing for IP is available through use of the epc epif-4-path-lbal command.
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: After performing consecutive OIRs of three traffic-shaping carrier modules (TSCAMs) in a chassis more than 20 times, memory allocation fails. Because the TSCAMs require 2 MB of contiguous memory, this failure might occur on a system with severely fragmented memory.
Workaround: Do not perform a large number of consecutive OIRs on the TSCAM and do not perform an OIR on a module that has a large number of VCs.
Symptom: After a reload, the switch router's memory might be corrupted. This occurs after the following error messages are displayed:
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: One side of a circuit emulation service (CES) E1 port of a LightStream LS1010 switch connection remains consistently in the YELLOW alarm or ALARM INTEGRATION state.
A ROMMON configuration might not work properly.
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 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.
There might be a buffer overflow.
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: In the ATM-MIB there is an atmVcCrossConnectTable that allows SNMP to create VC Cross-connects. It is not possible to create multipoint connections. At the time of creating the second entry corresponding to the multipoint connection, SNMP reports the following error:
Symptom: The snmp polling of the virtual path mibs atmVplLastChange and atmVplOperstatus results in unavailability of the virtual path. But the polling of the virtual circuit in this virtual path states that it is available.
Symptom: If an interface comes up after the system initialization, the scheduler for that interface might not be programmed correctly. Since IMA interfaces comes up after system initialization, IMA interfaces are usually affected by this.
Workaround: Enter the shutdown command on the IMA interface. Take the first link on the IMA interface out of IMA group. Bring that interface up. Shutdown that interface and then make it part of IMA group. Enter the no shutdown command to bring the IMA interface up.
Symptom: The ifTable indexes do not match the MIB-II table indexes.
Symptom: A LightStream 1010 switch router might automatically reload. When you enter the show version command, the switch reports the reason as "System was restarted by error - a Software forced crash". In addition, log error message might say:
Other messages indicating memory corruption might also occur.
Symptom: HSRP cannot be configured on Cisco IOS Release 12.1(5)EY1 image on the Catalyst 8510 MSR platform.
Symptom: After resetting a switch or router that is connected to a CES port on a LightStream 1010 or Catalyst 8510, there is connectivity about the physical layer.
Workaround: Enter the shutdown command and then the no shutdown command on the CBR interface of the LightStream 1010 or Catalyst 8510.
Symptom: An ATM router module port configured for transparent bridging and in blocking state may forward certain frames.
Workaround: Ensure that a non-ATM router module port is in blocking state. If this is not feasible, physically shutdown the ATM router module port that is in blocking state.
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. 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.
Workaround: 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: When the switch router is under stress because there are greater than 1000 TVCs on a given interface, some TVCs might not get setup successfully and the following error message occurs:
Workaround: Configure less than 1000 TVCs on interfaces.
Symptom: The transmit side of a tag-enabled ATM interface may go into the "not TDP ready" state Use the show tag tdp discovery command to verify that it is in the "not TDP ready" state. As a consequence, Tag is inactive on that interface.
Workaround: Enter the shutdown command followed by the no shutdown command. If this does not work, there is no workaround.
Symptom: The IP PAT tree becomes programmed incorrectly for 1483 SVC after removing the ARM card. If an SVC is configured on an ARM/ARM2 card and the card is OIRed, the adjacency available across the SVC will remain valid in the EPIF/XPIF cam. This results in packets destined to that adjacency to disappear.
Workaround: Before OIRing an ARM/ARM2 card, remove any sub-interfaces that have a SVC configurations, then proceed to do the OIR.
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 instead use the commands for determining any PNNI information.
A peer switch might not learn an IP address through ILMI-status.
Symptom: An IP address might not be learned by peer switch when using ILMI-status.
Symptom: The ARM sets 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 ARM1 interface shut downs when entering the epc portstuck-manual-reload command with IP traffic. This only occurs when running the epc portstuck-manual-reload command several times.
Symptom: Spurious memory access at lss_arm_atm_adjacency_mac is observed after there is a CLI epc portstuck-manual-reload command entered on two ARM1 interfaces, while two Catalyst 8540 MSRs are connected.
This has no functionality impact.
Symptom: Port stuck messages might not log into the system log.
Symptom: The outbound ACL fails to filter packets in the subinterface when the static ARP is configured and the ACL is used with it. If a static ARP is configured and the same address is moved from an interface to a subinterface of the same interface, the static ARP entry remains associated with the main interface itself.
Workaround: When the IP address is reconfigured to a subinterface of a main interface, you then need to delete and reconfigure the ARP address.
Symptom: The following operations will result in a CPU HOG and a CPU HOG error message:
This will not affect the future operation of the TSCAM.
Workaround: Though this CPU HOG should not have any adverse impact on the network, it is recommended that any online insertion or removal of TSCAMs or Port Adapter Modules in the subcard 0 position of the TSCAM are scheduled appropriately.
Symptom: Telnet responses between two switch routers might be very slow.
Workaround: Replace one switch router with another that can accept ISL-frames less than 94B in size (for instance, the Catalyst 5000).
Symptom: After configuring an ipx network between a Catalyst 8540 MSR and a Catalyst 8540 MSR, and a Catalyst 7500, old buffers detected messages being displayed on the Catalyst 8540 MSR. This occurs with an ATM interface and a Fast Ethernet interface. The Encap is 11 (Novell-Ether). This does not impact any 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: Oversized packets on the ARM2 interface are observed when it is a member of a BVI. This console output relates to the oversized packets on the ARM2 interface. The following message is displayed:
The system recovers from this. The cause of this may be temporary congestion in the switch fabric, leading to the loss of the last cell of the packet.
Symptom: The ARM (8540-ARM-64K) indicates outgoing packets when on an interface that is in an admin down state.
This was observed on Cisco Internetwork Operating System Software IOS (tm) PNNI Software (cat8540m-WP-M), Version 12.0(10)W5(18c). This does not impact the functionality.
Symptom: The switch router might loose traffic on its LANE or 1483 or 1577 interfaces on ARM. Frame interfaces or non-LANE interfaces on ARM with configured PVC's should pass traffic without any problems. It doesn't matter if the traffic is going to route processor 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: A switch with a lot of FC-PCQ connections or running a lot of LANE traffic, might display the following message when the interface carrying most of the traffic is shutdown:
Symptom: While executing a series of shutdown/no shutdown commands on the ARM interface with a large number of CLIP clients (more than 32), the following error message appears on the console:
This does not impact functionality. Enter the shutdown command, followed by the no shutdown command to recover.
Symptom: On Cisco IOS Release 12.0(10)W5(18b), when the module with c8510-ACL is in the Catalyst 5500 chassis, the show hardware command does not show the ACL daughter card.
Symptom: In the Cisco IOS release image ls1010-wp-mz.120-13.W5.19, the LS1010 power on diagnostic test causes the IOS not to boot while the ARM and Fast Ethernet modules are installed.
Workaround: Upgrade to Cisco IOS release image version ls1010-wp-mz.120-13.W5.19a.
Symptom: The IP CEF adjacencies are reported as invalid when using the ARM configured with LANE clients on the Catalyst 8540 MSR. The router reports an invalid cached adjacency for ip addresses that is not reachable through the LANE interface when running the show ip cef <ip address> command.
With an invalid cache adjacency, all the packets destined to this address will be sent to the route processor for processing.
The CEF adjacency will be invalid until a LANE data direct VC and valid LE-ARP entry are established on the adjacent device. As soon as the data direct VC and LE-ARP entry are established, the adjacency will be reported as valid.
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: If the HSRP has been configured on a Catalyst 8500 running an Cisco IOS Release 12.0(10)W5(18c), and the ARM is removed and then reinserted, the HSRP configuration is lost.
Symptom: When a ping command is entered from one member of a BVI to the outside, it causes some pings between members of the BVI to timeout.
Symptom: Under certain conditions, the Catalyst 8510 does not have a certain MAC address in the CAM table. This leads to flooding of L2 traffic for a short time, until the MAC addresses are learned.
Workaround: Issue a clear br gr command.
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: 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 sub-interfaces of an ARM (ARM1 or 2) may appear to receive the INARP packets even though the main interface is shut down. The upper layer finally discards the packet based on the state of the interface. There is no impact to any functionality.
Symptom: The output of the EXEC command show atm controllers atm 2/0/0 is incorrect. Interfaces with spurious card/subcard/port IDs are displayed, duplicating valid interface displays.
Symptom: The ARM always signals a fixed value for the PCR if LANE is configured on the ARM. The hidden CLI will give a way to signal the user-configured PCR. This will help with ATM traffic shaping/policing by the ATM nodes in between.
Symptom: The IP adjacencies are not being cleared from the gigabit ethernet card quickly. The sh epc ip-address command was issued on the adjacency, it was found that the entry for the host on vlan2 was still there and took some time to clear. As soon as it did clear, the ping command works again.
Symptom: Per-VC drop counters are not consistent. This applies only to non-packet discard connections. The inconsistencies are between the three per-VC statistics: total RX cell drops, RX UPC violations, and RX clp0 q full drops. The total of RX UPC violations and RX Clp0 q full drops exceeds the total RX cell drops count. However, the total RX cell drops is accurate.
Symptom: The atmVcCrossConnectAdminStatus entries might disappear.
Symptom: The switch router will crash and hang when ip http server is configured and a browser connects to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack. This information has been announced on public Internet mailing lists which are widely read by both security professionals and by security "crackers," and should be considered public information.
Workaround: Disable the IP http server with the following command: no ip http server
Alternatively, the administrator can block port 80 connections to the switch router via access lists or other firewall methods. For further information, refer to the security advisory available at http://www.cisco.com/warp/public/707/advisory.html.
Symptom: ifOutOctets wrapping at 3000000 on an ATM interface.
Symptom: CPU hog by OIR handler.
Symptom: Multicast stats shows an incorrect rate in kbps.
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: The output from the show bridge commands are incomplete.
Symptom: The ILMI status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) appear stuck in the Restarting state after a shutdown/no shutdown command sequence.
Symptom: A LightStream 1010 configured for MPLS might not correctly increment counters on outgoing TVCs, although the data is being correctly sent out of the TVC.
Symptom: OAM F5 loopback cells are not passing across 25-Mbps port adapter interfaces.
Workaround: Configure the global configuration command no atm oam intercept end-to-end on the switch.
Symptom: The switch might have spurious memory access tags after configuring and unconfiguring tag switching on different ATM interfaces. This is not known to impact tag switching functionality on the switch. The following message might appear on the console:
Symptom: IMA group fails to come up intermittently, especially after reload and on E1 IMA links.
Workaround: Go to one of the IMA interfaces and give the following command:
If the group still remains down, it indicates a persisting alarm on the line. The line configuration has to be checked to clear the problem.
Symptom: Performing a shutdown/no shutdown command sequence on an ARM interface, especially when it has configured a large number of LANE clients, might cause an error message like this to appear:
%LANE-3-LANE_ERROR: lecs finder: ILMI hung on interface ATM1/0/0
It indicates an internal timeout occurred. It should try to self-cover and not affect any normal operations.
Symptom: The show ncdp path root command might not display any information when you access the switch through the Ethernet port.
Workaround: Access the switch using the console port.
Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).
Symptom: The CES ABCD bits are not user configurable when a fault occurs.
Symptom: EIGRP routes stop might be advertised out of an interface when there doesn't appear to be any interface problems.
Workaround: Enter the shutdown command followed by the no shutdown command on the effected interface.
Symptom: Power-on diagnostics will display an NVRAM-Config failure following the second power-cycle after you use the write erase command if the write memory command has not been used between power-cycles.
This failure will occur only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.
|
Note Power-on diagnostics run only if the switch is powered on. Power-on diagnostics do not run when using the reload command. |
Workaround: After using the write erase command, use the write memory command before power cycling the switch.
Symptom: The following message appears on the neighbor ATM switch after using the reload command:
%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background
Symptom: Spurious memory access on show ip route command when SONICT interface is shutdown.
If you shutdown a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():
Symptom: On a switch router configured with 32 MB RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.
This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a system configured with 64MB of RAM.
Symptom: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation. While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very long period of time (for example, overnight) causes memory fragmentation in the TDP process.
Symptom: When loading a software image version 11.3 or later on a switch router with a software image version 11.2 or earlier, LEC and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch.
The ATM address of the switch along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with the 11.3 software version, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch ATM address with various selector byte values.
Workaround: If LANE components fail to come up because their ATM addresses conflict with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. It is recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which eliminates this problem.
Symptom: The show controller atm card/subcard/port command displays the incorrect interface type after hot swapping the port adapter.
Symptom: A non-zero generic flow control (GFC) field is not reset to zero when passing through the switch router.
When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).
Symptom: ILMI does not come up upon reload of VP-MUX (VUNI).
ILMI on the tunnel interface, which is connected to the far end peer device through a VP-MUX switch and virtual UNI, is occasionally unable to come up and stay in state of "WaitDevType" after reloading the VP-MUX switch. This situation can be cleared by shutting down the tunnel interface, disabling ILMI followed by a no shutdown command on the tunnel interface. After the interface settles down, ILMI on the tunnel can then be reenabled by shutting down the interface, entering the atm ilmi-enable command and also the atm auto-configuration command, if desired. Reenable the tunnel interface with a no shutdown command.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface oversubscribes and, potentially, affects the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmission to the scheduled rate. This can cause cells to be dropped in the WAN. It might be better to do any dropping prior to multiplexing onto the VP, so that a packet discard can be performed. Packet discard cannot be performed on the VP trunk.
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch that had the closed physical interface.
Symptom: While setting up a large number of calls, the system generates the following error message:
%SYS-3-CPUHOG: Task ran for 5852 msec (0/0), process = Exec, PC = 6008DBB4
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable IP routing and then save the configuration to NVRAM.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Symptom: If there are multiple parallel paths to the same destination on a switch router with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of 4 parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Symptom: On a switch router equipped with an FC-PFQ, the maximum number of cells available for use is 64,511. The number of cells in the switch fabric is 65,535.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Symptom: Cell loss might occur while hot swapping a power supply.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (via PortSelTable) is not possible until the interface's MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on PortSelectGroups representing the interface on which the call came in and the counters shown on the PortSelectGroups representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order to validate clients.
If different emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration:
This configuration of an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:
The clients are still allowed to join the ELAN. Disregard the warning messages.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Symptom: Remote defect identification (RDI) cells sent by an end point in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Starting with Cisco IOS Release 12.0(10)W5(18b) software release, hardware and software functionality interoperability exists between CSR interface modules and MSR interface modules by way of the ATM router module on the MSR chassis running an MSR image.
Catalyst 8510 and LightStream 1010 systems running Cisco IOS Release 12.0(0.6)W5(1) or later have been certified as Y2K Compliant. For more information, see the following URL:
http://www.cisco.com/warp/public/752/2000/.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasmania Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
Posted: Tue Mar 11 16:39:10 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.