Table Of Contents
Resolved Caveats—Cisco IOS Release 12.0(33)S2
Resolved Caveats—Cisco IOS Release 12.0(33)S1
Resolved Caveats—Cisco IOS Release 12.0(33)S
Open Caveats—Cisco IOS Release 12.0(33)S
Resolved Caveats—Cisco IOS Release 12.0(32)S11
Resolved Caveats—Cisco IOS Release 12.0(32)S10
Resolved Caveats—Cisco IOS Release 12.0(32)S9
Resolved Caveats—Cisco IOS Release 12.0(32)S8
Resolved Caveats—Cisco IOS Release 12.0(32)S7
Resolved Caveats—Cisco IOS Release 12.0(32)S6
Resolved Caveats—Cisco IOS Release 12.0(32)S5
Resolved Caveats—Cisco IOS Release 12.0(32)S4
Resolved Caveats—Cisco IOS Release 12.0(32)S3
Resolved Caveats—Cisco IOS Release 12.0(32)S2
Resolved Caveats—Cisco IOS Release 12.0(32)S1
Resolved Caveats—Cisco IOS Release 12.0(32)S
Resolved Caveats—Cisco IOS Release 12.0(31)S6
Resolved Caveats—Cisco IOS Release 12.0(31)S5
Resolved Caveats—Cisco IOS Release 12.0(31)S4
Resolved Caveats—Cisco IOS Release 12.0(31)S3
Resolved Caveats—Cisco IOS Release 12.0(31)S2
Resolved Caveats—Cisco IOS Release 12.0(31)S1
Resolved Caveats—Cisco IOS Release 12.0(31)S
Resolved Caveats—Cisco IOS Release 12.0(30)S5
Resolved Caveats—Cisco IOS Release 12.0(30)S4
Resolved Caveats—Cisco IOS Release 12.0(30)S3
Resolved Caveats—Cisco IOS Release 12.0(30)S2
Resolved Caveats—Cisco IOS Release 12.0(30)S1
Resolved Caveats—Cisco IOS Release 12.0(30)S
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
Because Cisco IOS Release 12.0S is based on Cisco IOS Release 12.0, many caveats that apply to Cisco IOS Release 12.0 will also apply to Cisco IOS Release 12.0S. For information on severity 1 and severity 2 caveats in Cisco IOS Release 12.0, see the Caveats for Cisco IOS Release 12.0 document located on Cisco.com.
Note
If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Technical Support: Tools & Resources: Bug Toolkit. (The Bug Toolkit is listed under Troubleshooting.) Another option is to go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.)
The Dictionary of Internetworking Terms and Acronyms contains definitions of acronyms that are not defined in this document:
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ita/index.htm
The caveats section consists of the following subsections:
Cross-Platform Release Notes for Cisco IOS Release 12.0S, Part 3:
Caveats for 12.0(33)S through 12.0(30)S•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cross-Platform Release Notes for Cisco IOS Release 12.0S, Part 4:
Caveats for 12.0(29)S1 through 12.0(27)S•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cross-Platform Release Notes for Cisco IOS Release 12.0S, Part 5:
Caveats for 12.0(26)S6 through 12.0(24)S•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cross-Platform Release Notes for Cisco IOS Release 12.0S, Part 6:
Caveats for 12.0(23)S6 through 12.0(6)S•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Resolved Caveats—Cisco IOS Release 12.0(33)S2
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(33)S2. This section describes only severity 1, severity 2, and select severity 3 caveats.
These caveats are documented in the following format:
•
•
•
Miscellaneous
•
Symptoms: A Data-link switching plus (DLSw+) circuit may not function when a TCP connection gets stuck. After about 90 seconds, the TCP connection is closed by DLSw+, and a new TCP connection is built for DLSw+. Once the new TCP connection is up, the DLSw+ circuit starts functioning again.
Conditions: This symptom is observed on a Cisco router that is configured with both a DLSw+ interface and an ATM interface.
Possible Workaround: If this is an option, remove the ATM interface from the router. When you configure the DLSw+ interface and the ATM interface on different routers, the symptom does not occur.
•
Symptoms: Under stress conditions, an L2TP multihop node may crash.
Conditions: This symptom is observed when a session is being disconnected.
Workaround: There is no workaround.
•
Symptoms: A static map configuration for an ATM PVC that uses the protocol ip ip-address command is rejected, giving an ambiguous command error.
Conditions: This symptom is observed when you configure a static map on an ATM PVC using the protocol ip ip- address command.
Workaround: Explicitly configure the [broadcast | no broadcast] option:
Router(config-if-atm-vc)# protocol ip 10.10.100.2 broadcastRouter(config-if-atm-vc)# protocol ip 10.10.100.2 ?broadcast Pseudo-broadcastno Prevent Pseudo-broadcast on this connection<cr>Router(config-if-atm-vc)# protocol ip 10.10.100.2 no broadcastRouter(config-if-atm-vc)#•
Symptoms: A PE that is part of a confederation and that has received a VPNv4 prefix from an internal and an external confederation peer, may assign a local label to the prefix despite the fact that the prefix is not local to this PE and that the PE is not changing the BGP next-hop.
Conditions: The symptoms are observed when receiving the prefix via two paths from confederation peers.
Workaround: There is no workaround.
Further Problem Description: Whether or not the PE will chose to allocate a local label depends on the order that the multiple paths for this VPNv4 prefix are learned. The immediate impact is that the local label allocated takes up memory in the router as the router will populate the LFIB with the labels.
•
Symptoms: The NetFlow cache runs out of space for new flow entry when customer uses heavy traffic.
Conditions: Large amount of traffic, which could exhaust the NetFlow cache.
Workaround: There is no workaround.
•
Symptoms: In Eng3 ATM, when a subinterface flaps, traffic to certain destinations is forwarded to the wrong subinterface.
Conditions: This symptom is observed in Cisco IOS Release 12.0(32)S05 and 12.0(32)S06. The symptom is not found in Cisco IOS Release 12.0(31)S2.
Workaround: There is no workaround; however, reloading the line card solves the problem.
•
Symptoms: A BGP neighbor may send a notification reporting that it received an invalid BGP message with a length of 4097 or 4098 bytes.
Conditions: The problem can be seen for pure IPv4 BGP sessions (no MP-BGP in use) when the router that is running the affected software generates a large number of withdraws in a short time period and fills an entire BGP update message (up to 4096 bytes normally) completely with withdraws. Because of a counting error, the router that is running the affected software can generate an update message that is 1 or 2 bytes too large when formatting withdraws close to the 4096 size boundary.
Workaround: The issue is not seen when multiple address families are being exchanged between BGP neighbors.
•
Symptoms: The interface output rate (214 Mb/s) is greater than the interface line rate (155 Mb/s).
Conditions: This symptom is observed with a Cisco 7600/7500/7200-NPE400 and below. That is, PA-POS-2OC3/1OC3 (PULL mode).
Workaround: There is no workaround.
Further Problem Description: From the Ixia, packets are transmitted at 320 Mb/s. On the UUT (Cisco 7600), the outgoing interface (POS-Enhanced Flexwan) shows the output rate as 200 Mb/s. But the interface bandwidth is 155 Mb/s.
•
Symptoms: The show ip mds stats linecard command shows MDFS reloads on all line cards.
Conditions: This symptom is observed when multicast distributed routing is added on a VRF through the configuration of the ip multicast-routing vrf vpn distributed command.
Further Problem Description: Note that while the MDFS reload is a real reload, it is without a preceding clear, so it will not generally cause traffic interruption because it merely causes the same information to be downloaded to the line cards again. However, in a highly scaled system that is running close to the limit, the additional load introduced by a full MDFS reload of every line card may cause additional failures owing to maxing out of the CPUs.
•
Symptoms: The shape average percent calculation is wrong.
Conditions: This symptom is observed on a Cisco 7500 router that is configured for dLFIoLL. The policy is attached to ATM and multilink interfaces.
Workaround: Use only absolute values in the shape policy.
•
Symptoms: OSPF routes are not populated in the Routing Information Base (RIB) with the next hop as traffic engineering (TE) tunnels.
Conditions: Occurs when multiple TE tunnels are configured and the tunnels come up or are shut/no shut simultaneously.
Workaround: Shut/no shut tunnels one at a time.
•
Symptoms:
–
–
Conditions: This symptom is observed when running RPR+.
Workaround: Reapply the original configuration.
Further Problem Description: Deletion of a multilink interface and subsequent creation using the same name may cause portions of the original configuration to return even if not explicitly configured. The hold-queue command is not being synchronized to the standby RP.
•
Symptoms: The v6-vrf-lite configuration does not synch properly with the standby; hence 100 percent of the traffic is lost after an SSO switchover.
Conditions: The conditions under which this symptom is observed are unknown.
Workaround: There is no workaround.
•
Symptoms: Router may crash @ipflow_fill_data_in_flowset when changing flow version.
Conditions: Occurs when NetFlow is running with data export occurring while manually changing the flow-export version configuration from version 9 to version 5 and back to version 9 again.
Workaround: Do not change the NetFlow flow version while the router is exporting data and routing traffic.
•
Symptoms: An E3 linecard may drop packets larger than a certain size because of a buffer carving problem when the mtu command is used for multilink interfaces.
Conditions: This symptom is observed with images based on Cisco IOS Release 12.0(32)S10.
Workaround: Changing the MTU or reloading the linecard may clear the problem.
•
Symptoms: After executing the following CLI commands (steps mentioned alphabetically) via a script (not reproducible manually), the router sometimes crashes:
Test10:
a. clear ip bgp 10.0.101.46 ipv4 multicast out
b. clear ip bgp 10.0.101.47 ipv4 multicast out
Test 1:
c. show ip bgp ipv4 multicast nei 10.0.101.2
d. show ip bgp ipv4 multicast [<prefix>]
e. config terminal
The crash does not happen for each of the following cases:
1. If the same CLI is cut and paste manually, there is no crash.
2. If the clear cli command is not executed, there is no crash.
3. If the config terminal command is not entered, there is no crash.
Conditions: The symptom occurs after executing the above CLI.
Workaround: There is no workaround.
•
Symptoms: A Cisco 7200 device crashes when a policy map is applied.
Conditions: This symptom is observed when the service policy map is applied on the channelized E3 interface of a Cisco 7200 VXR router and traffic is pumped.
Workaround: Remove the service policy map.
•
Symptoms: You may observe a problem which the OSPF neighbor is down after switch-over in spite of using OSPF Non-Stop Forwarding (NSF).
Conditions: This occurs with the following conditions:
–
–
–
Workaround: Change the OSPF config to "nsf ietf" and change the OSPF interface to "broadcast".
•
Symptoms: The command hold-queue length in cannot be configured for port-channel interface.
Conditions: The symptom is observed with a Cisco 7600 series router after upgrading to Cisco IOS Release 12.2(33)SRC.
Workaround: There is no workaround.
Further Problem Description: Queueing is not supported for port-channel with a Cisco 7600 series router. The hold-queue is a legacy queueing command and is not supported.
•
Symptoms: The "set metric" clause in the continue route-map sequence is not setting metric correctly in some particular conditions. This is also applicable in case where the nexthop setting is done via route-map with a continue clause.
Conditions: The symptom is observed on a Cisco 12000 series router that is running Cisco IOS Release 12.0(32)SY4. This is platform independent. This symptom occurs if the route-map has a continue clause and the match condition does not allow the continue clause to be executed. The following route-map sequence which has to be executed will not execute properly if the metric or nexthop of the prefix are to be modified via the route-map.
Workaround: Avoid using "continue" in a route-map and modifying metric or nexthop via the following route-map sequence.
•
Symptoms: An unexpected reboot occurs because of a software-forced crash.
Conditions: This symptom is observed when changes are made in the policy map.
Workaround: There is no workaround.
•
Symptoms: A router crashes with an unexpected exception to CPUvector 300.
Conditions: This symptom is observed when you configure MPLS trunks on an 4xT3E3 SPA with FR IETF encapsulation.
Workaround: There is no workaround.
•
Symptoms: A device may crash when the show clns interface command is issued on the wrong interface.
Conditions: The symptom is observed when there are a number (around 100 or more) CLNS interfaces on the device.
Workaround: There is no workaround.
•
Symptoms: Router crashes.
Conditions: Router may crash in some cases after removing interface Auto-template and unconfiguring auto-mesh with large number of active mesh auto-tunnels. Currently, this crash has only been observed occasionally with internal scale test scripts and has not occurred with manual configuration.
Workaround: Wait until all auto-tunnels are down after unconfiguring auto-tunnel mesh globally, and before removing interface Auto-template
•
Symptoms: BGP peers are stuck with table versions of 0. BGP peers do not announce any routes to neighbors.
Conditions: Whenever the interfaces flap with online insertion and removal (OIR) multiple times, all of the BGP peers using such interfaces for peering connections encounter this issue.
Workaround: Delete and reconfigure the neighbor.
•
Symptoms: Policy-map outputs are not seen in standby router. The policy is attached to the VC in the standby, but no output is seen.
Conditions: The symptom is observed when an ATM PVC is created and a service policy is attached to the PVC.
Workaround: There is no workaround.
•
Symptoms: A customer upgraded to Cisco IOS Release 12.0(32)Sy4, and now the customer is seeing a memory leak in the BGP process. The memory leak is happening with the BGP router process at the rcache chunk memory when the route map has a "continue" clause in the configuration.
Conditions: The leak is seen when a "continue" statement is configured in an outbound route map.
Workaround: There is no workaround.
•
Symptoms: High CPU utilization is seen on a Cisco 12000 series Internet router caused by the "IPC Seat Manager" process.
Conditions: This symptom may be observed when the router is enabled with multicast distributed routing and has high scaled multicast configurations.
Workaround: There is no workaround.
•
Symptoms: A SIP601 sometimes crashes or gets an alignment error.
SLOT 4:Mar 17 17:59:03.877 UTC: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x408C1E14 reading 0xF SLOT 4:Mar 17 17:59:03.877 UTC: %ALIGN-3- TRACE: -Traceback= 408C1E14 408C03D4 00000000 00000000 00000000 00000000 00000000 00000000
Conditions: The conditions under which this symptom occurs are unknown.
Workaround: There is no workaround.
•
Symptoms: The local PE is sending graft messages even after receiving data from the remote PE on an MVPN network.
Conditions: This symptom is observed when the graft-ack messages are lost in transit (could be due to misconfiguration/ACL, etc.).
Workaround: Fix the misconfiguration so that graft-ack messages are forwarded as expected.
•
Symptoms: Configuring a PBR at the E5 GE subinterface may cause buffer depletion. The buffer cannot be released except by reloading the linecard.
Conditions: This symptom is observed when a PBR is configured at the subinterface.
Workaround: There is no workaround.
•
Symptoms: A Catalyst 6500 or a Cisco 7600 may reload unexpectedly.
Conditions: Occurs when NetFlow is configured on one of the following:
–
–
Workaround: Disable NetFlow. This is done with the following commands:
no ip flow ingress
no ip flow egress
no ip route-cache flowEnter the appropriate command for each subinterface for which NetFlow is currently configured.
•
Symptoms: MFR bundles associated with E5 channelized based SPAs will stop forwarding traffic, an mismatch of the connection identifier (CI) of the channelized SPA is seen on CI value in the shim header of the l2 rewrite.
Conditions: This problem will occur for l2vpns only on E5 channelized based SPAs.
Workaround: Enter into interface configuration mode.
Alternate Workaround: Remove and re-add the xconnect.
•
Symptoms: When a router reloads, the line protocol on serial interfaces will go down.
Conditions: This symptom is observed when bringing up the SPA-1XCHSTM1/OC3 or SPA-2XCT3/DS0 with a scaled configuration that has serial interfaces on all the T1s.
Workaround: There is no workaround.
•
Symptoms: Spurious accesses are seen when SNMP queries are performed on the router.
Conditions: This symptom occurs if SNMP queries like "snmpwalk -v2c 7.42.19.43 public .1.3.6.1.4.1.9.3.6.13.1" are performed on the router. Spurious accesses are seen.
Workaround: There is no workaround.
•
Symptoms: The line card on a Cisco 10720 resets when an IP phone is connected. The "%TOASTER-2-FAULT: T1 Exception summary:" message appears.
Conditions: The line card to which the Cisco Call Manager is connected to a Cisco 10720 crashes when an IP phone is connected to the network.
Workaround: The recommended approach is to upgrade the Cisco IOS software.
•
Symptoms: New T1s cannot be provisioned on a CT3 SPA.
Conditions: When a customer tries to create a new T1 on one of the controllers of a CT3-SPA that is inserted into a SIP-401, the following errors are displayed:
Router(config-controller)# t1 15 channel-group 7 timeslots 1-24 %Failed to configure channel group Router(config-controller)# Apr 24 22:51:05.283 UTC: %GRPSPA-3-VC_PROV_ERROR: Provision T1 15 channel group 7 of T3 4/0/1 unsuccessful (error code 44) -Traceback= 20A640 20A748 954AA4 94DB80 94DC90 9582D0 4FF4E0 5006FC 240B7C 2563B0 13D7410 13C6F3C 2F517C SLOT 4:Apr 24 22:51:05.271 UTC: %SPA_CHOC_DSX-3-SPA_SW_ERR: SPA on Subslot 0: HDLC controller device driver failure: Failed to start operation Software error was encountered.-Traceback= 40031128 408B4020 408BCE40 408BD374 408BF114 408C004C 408C0ED8 408D24E0 408D25F8Workaround: There is no workaround.
•
Symptoms: Newer SDRAM devices on the 2- and 4-port OC48 POS/RPR SPA require an additional initialization sequence as recommended by the vendor.
Without this new initialization sequence, packets that go through the transit buffer in RPR/SRP mode or in subscription mode may get corrupted, or packet loss may occur.
Conditions: Card initialization after inserting the SPA or removing an unpowered shutdown.
Workaround: Perform an OIR on the SPA.
Customers are advised to upgrade to the newer image with this new initialization sequence. Serial numbers of impacted cards are available from manufacturing.
•
Symptoms: The MDFS state of the line card stays in a "disabled" state, which may lead to multicast traffic being punted to the RP.
Conditions: This symptom may be observed with the following sequence of operation:
1. The router is booted without configuring the ip multicast-routing distributed command.
2. The ip multicast-routing distributed command is configured.
The issue will not be seen if the ip multicast-routing distributed command is present in the startup configuration when the router is reloaded.
Workaround: Enter the clear ip mds linecard slot- number command.
•
Symptoms: A device crashes with ACL configurations.
Conditions: The RP will crash when the device is running low on memory or in a highly fragmented situation if an ACL/ACE is added/deleted.
Workaround: There is no workaround.
•
Symptoms: Ping packets of 8180 or larger cause sourcing POS linecard/SIP to reload and remain in a boot state waiting for IPC connection.
Conditions: This symptom is observed with ping packets that are sourced from PRP2 with part number 800-27058-03.
Workaround: Reload the router.
Further Problem Description: This symptom is observed only on PRP2 with part number 800-27058-03.
•
Symptoms: A crash occurs when BGP graceful restart is configured.
Conditions: In the following configuration:
ip vrf vfifteen
rd 15:15
import ipv4 unicast map rfifteen
route-target export 150:15
route-target import 150:15Delete the RD, and then the unicast map, and then the VRF.
Workaround: There is no feasible workaround. Try to avoid doing such an operation as explained above.
•
Symptoms: Low CPS may be observed.
Conditions: The symptoms are seen with PPPoA and PPPoE sessions.
Workaround: There is no workaround.
•
Symptoms: A copy tftp operation failed with a Socket error when the FPD of an SPA was updated or when the SPA was reloaded, OIRed.
Conditions: This symptom is related to the number of (nnets) non-virtual interfaces on the box. Depending on that, a number of SPA reloads must be done.
Workaround:
1. Reload the SPA or the router.
2. Configure one loopback interface.
•
Symptoms: A router can crash at l2tp_process_control_packet_cleanup.
Conditions: Conditions are unknown at this time.
Workaround: There is no workaround.
•
Symptoms: CPU hogs are seen in a 1-port E3 channelized OC48.
Conditions: This symptom is observed when any of the following is done:
–
–
–
–
Workaround: There is no workaround.
•
Symptoms: The following error messages appear:
SLOT 5:*May 9 21:43:48.547: %LC_SPA_DMLP-1-SPAHWBUNDLEERROR: Could not perform required operation in SPA H/w for bundle Multilink2 in bflc_cx3_dmlp_frag_on_off SLOT 5:*May 9 21:44:10.727: %SPA_CHOC_DSX-3-ERROR: Multilink2 (cmd 203) Serial5/0/1/8:0: response parsing failed. chnl 36, bid 1 -Traceback= 40031008 408924C0 4072B1BC 40899F64 4033DB90 4033E190 4033E5C0 4033E930 4033F448 4033F600 4015B53C 4015C020 SLOT 5:*May 9 21:44:10.735: %LC_SPA_DMLP-3-CFG_FAIL: bundle Multilink2 (id 1): bay 0 err 7 (del rx link)
Conditions: When we remove/add/remove all members from all the configured MLP bundles once or several times, these tracebacks are seen.
Workaround: There is no workaround.
Further Problem Description: spabrg EFC mapping goes to a mismatch state, and the following is seen:
SLOT 5:*May 9 21:59:26.771: %SPA_CHOC_DSX-3-HDLC_CTRL_ERR: SPA 5/0: 20 TX Chnl Queue Overflow events on HDLC Controller were encountered.
•
Symptoms: The hw-module slot x qos account layer2 encapsulation command does not take effect for an AToM connection.
Conditions: This symptom is observed when xconnect is configured under a VLAN.
Workaround: There is no workaround.
•
Symptoms: When configuring "is-type level-1" under "router isis", the following error message may be received:
% Ambiguous command: "is-type level-1"
Conditions: The symptom is observed when configuring "is-type level-1" under "router isis".
Workaround: There is no workaround.
•
Symptoms: A PA-POS-2OC3 experiences an output stuck condition.
Conditions: This issue is sporadic in nature and is sometimes seen with QoS configurations although QoS is not the cause of the issue. The issue is due to an extra interrupt, which is confusing the driver if it expires before the FIFO reaches the low point. For example, if the FIFO goes full but is filled with large packets, then it is possible that the no traffic timer will expire before the tx packets have emptied. It is a communication issue between the hardware and the driver code.
Workaround: There is no workaround.
•
Symptom: Serials that are part of MLPPP/MFR remain in a down state.
Conditions: This symptom is observed when T1 controllers remain down.
Workaround: There is no workaround.
•
Symptoms: MDFS may get disabled in a scaled mVPN environment that has many global mroutes. Once disabled, it may keep on changing between the "active" and "disabled" states. Linecard CPU utilization may also go high.
Conditions: This symptom is observed with a Cisco IOS Release 12.0(32)S10 image.
Workaround: There is no workaround.
•
Symptoms: Router crashed while running the show vpdn tunnel all command.
Conditions: When there are thousands of L2TP tunnels coming up, going down, running the show vpdn tunnel all command may result in a crash.
Workaround: There is no workaround.
•
Symptoms: After a router reloads, sometimes the configuration for the gigE and POS OC12 SPA is lost from the running configuration.
Conditions: This symptom is observed when the router is reloaded.
Workaround: There is no workaround.
•
Symptoms: If both L2 and L3 services co-exist on the same interface, you can no longer configure urpf on the L3 subinterface after the fix for CSCsl09772. After the router reloads, the urpf command will be erased from the L3 subinterface. You have to use the workaround to reapply the urpf command.
Conditions: This symptom is observed when both L2 and L3 services are configured on the same interface.
Workaround: Do the following:
1. Remove the L2 connection.
2. Add urpf on the L3 subinterface.
3. Re-add the L2 connection.
•
Symptoms: Intermediate System-to-Intermediate System (IS-IS) tries to access invalid memory address and may cause router to stop working.
Conditions: Occurs when a switch over happens and standby router becomes active.
Workaround: There is no workaround.
•
Symptoms: CPU Hog and related tracebacks are seen from the E3 Gig linecard.
Conditions: Attach a scaled policy/LC reload/router reload.
Workaround: There is no workaround.
•
Symptoms: The pos delay triggers line command is configurable at the interface level of E3 channelized POS interfaces.
Conditions: This symptom is observed on a Cisco 12416 Internet series router that is booted with the Cisco IOS Release 12.0(32)S nightly build of 05/19/08. The router contains an E3 CHOC48 linecard.
Workaround: There is no workaround.
•
Symptoms: FRF12 packets are dropped by a PE router.
Conditions: This symptom is observed on a Cisco 12000 series Internet router that has a SPA-1XCHSTM1/OC3, SPA-2XCT3/DS0, or SPA-8XCHT1/E1.
Workaround: There is no workaround.
•
Symptoms: EFC clock interrupts are causing a line card to crash.
Conditions: The conditions under which this symptom occurs are unknown.
Workaround: There is no workaround.
•
Symptoms: The RP crashes.
Conditions: With a map-class that has an egress policy with iphc action, dlci removal is done.
Workaround: Ensure that the map-class is removed and then dlci removal is done.
•
Symptoms: Slow-path multicast fragmentation is not happening correctly. One of the output interfaces is not receiving the packets in case of MVPN traffic.
Conditions: This symptom is observed with MVPN traffic with fragmentation on one of the interfaces on E5.
Workaround: There is no workaround.
•
Symptoms: A Cisco 12000 works as a PE, and an Eng5 SIP line card is used to face the CE. In the VRF, the default route 0.0.0.0 is learned from the remote PE. When the problem occurs, all traffic from the CE that is forwarded via the VRF default route is dropped.
Conditions: This symptom is observed on a Cisco 12000 Eng5 SIP line card that is running Cisco IOS Release 12.0(32)SY04, 12.0(32)SY05, or 12.0(32)SY06. When VRFs are created and deleted, new VRFs that are created will have a problem if they are allocated with a table ID allocated for older deleted VRFs.
Workaround:
1. Reload the ingress Eng5 line card that is facing the CE.
or
2. If the customer does not want to reload the line card, a second workaround can be attempted, but it is not a reliable workaround and may not always be successful. Create a new VRF without removing any VRFs, which gets a new table ID, and apply the VRF configuration completely wherever the old VRF configuration is applied.
Further Problem Description: This problem cannot be cleared by using the clear cef linecard x or clear ip route vrf xxx 0.0.0.0 commands.
•
Symptoms: A heartbeat failure causes SPAs to go out of service.
Conditions: This symptom can be observed under the following conditions:
1. Provision/unprovision the MFR with QoS attached to its subinterfaces with traffic.
2. Add/remove of QoS policy tried on MFR subinterfaces with queues having packets.
3. Link is swapped from MLPPP to MLFR.
Workaround: Reload the line card.
•
Symptoms: Removal of a subinterface may cause memory corruption or a crash. The symptoms are unpredictable.
Conditions: The symptoms are rare and will only be observed if a sub- interface is configured for mpls traffic-eng auto-tunnel primary use, and the sub-interface is later removed from the configuration.
Workaround: Do not remove sub-interfaces.
•
Symptoms: MVPN inner packet with IP option causes depletion of FrFab buffers of Cisco 12000-SIP-401.
Conditions: This symptom occurs on Cisco 12000 routers that are running the c12kprp-k4p-mz.120-32.SY2g image and with Cisco 12000-SIP-401. This is triggered by multicast traffic.
Workaround: Only a reload of the card solves the problem.
•
Symptoms: Trying to remove the MFR bundle crashes the router.
Conditions: After OIR, remove the VIP (those VIP interfaces are members of MFR bundle). Try to remove the MFR bundle.
Workaround: There is no workaround.
Further Problem Description: The MFR bundle has one Channelized PA interface as a member. OIR remove that PA seated VIP and next try to remove the bundle using the no int MFR command. The router crashes.
•
Symptoms: After a router reloads, the SPAs on a SIP601 may take twice as long to come up in OK mode. When this occurs, you also experience the problem that is documented in CSCsq55258.
Conditions: This symptom is observed after a router reloads.
Workaround: There is no workaround.
•
Symptoms: In rare situations, the show controller SONET port command might crash the RP.
Conditions: This symptom has been observed on a 4CHOC12/DS3-I-SCB= line card, but it can be seen on other similar channelized line cards. It may be reproducible by executing the show controller SONET port command on a nonexistent port like sonet 3/4 (that is, only sonet 0/0, 0/1, 0/2, and 0/3 are valid on a 4CHOC line card). When the problem can be seen, the CLI help indicates an incorrect unit number:
Router# show controller sonet 12/?<0-48> Controller unit numberIf the controller unit number is shown fine (for example, <0-3>), then the crash will not occur.
Workaround: There is no workaround.
•
Symptoms: The pos delay triggers line command is configurable on APS-enabled interfaces of E3 clear channel POS line cards. After the commit of CSCsq45452, the pos delay triggers path command is not configurable on APS-enabled interfaces of E3 channelized POS line cards.
Conditions: This symptom is observed on a Cisco 12000 series Internet router that is booted with Cisco IOS Release 12.0(32)S. The router contains ISE OC48 POS and ISE CHOC48 POS line cards.
Workaround: There is no workaround.
•
Symptoms: Memory chunk allocated for LDP-IGP Sync may leak.
Conditions: The symptom is observed on a router with a dual link to its neighbor. LDP and LDP Graceful Restart are enabled on both routers. When LDP is disabled and re-enabled globally on the neighbor router, a small memory leak occurs on this router.
To verify the memory leak, on Router 1, enable memory leak debug with the set memory debug incremental starting-time command. On Router 2, disable LDP globally with the no mpls ip. Wait for LDP session go down, then re-enable LDP. On Router 1, the memory chunk leak for LDP should be seen with the sh mem debug leaks chunks command.
Workaround: There is no workaround.
•
Symptoms: When the
Guest
