Caveats in Cisco IOS XE 3.12S Releases
Caveats describe unexpected behavior. Severity 1 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 this chapter.
This section describes caveats in Cisco IOS XE 3.10S releases. The following information is provided for each caveat:
- Symptom—A description of what is observed when the caveat occurs.
- Conditions—The conditions under which the caveat has been known to occur.
- Workaround—Solutions, if available, to counteract the caveat.
The Dictionary of Internetworking Terms and Acronyms contains definitions of acronyms that are not defined in this document:
http://docwiki.cisco.com/wiki/Category:Internetworking_Terms_and_Acronyms_(ITA)
Bug Search Tool
The Caveats section only includes the bug ID and a short description of the bug. For details on the symptoms, conditions, and workaround for a particular bug you must use the Bug Search Tool.
Use the following link to access the tool: https://tools.cisco.com/bugsearch/search.
You will be prompted to log into Cisco.com. After successful login, the Bug Search Tool page opens. Use the Help link in the Bug Search Tool to obtain detailed help.
Caveats
The following sections describe the open and resolved caveats in 3.12S Releases:
Open Caveats—Cisco IOS XE Release 3.12.4S
There are no open caveats in Cisco IOS XE Release 3.12.4S.
Resolved Caveats—Cisco IOS XE Release 3.12.4S
|
|
CSCut55741 |
Wrong extraneous fan entries in Entity MIB. |
Open Caveats—Cisco IOS XE Release 3.12.3S
There are no open caveats in Cisco IOS XE Release 3.12.3S.
Resolved Caveats—Cisco IOS XE Release 3.12.3S
|
|
CSCur77331 |
Led Indicator on ASR903 showing down after port flapping for XCONNECT |
Open Caveats—Cisco IOS XE Release 3.12.2S
This section documents the issues that have are open in Cisco IOS XE Release 3.12.2S.
Symptom: Memory leak observed on router causing router reload.
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
Symptom: Router crashed observed on unconfiguring the CEM interface without logging out of the CEM configuration mode.
Conditions: This issue occurs on adding and removing the CEM interface configuration.
Workaround: Exit from the sub-mode before issuing the no xconnect command.
Symptom: In Virtual Private Wire Service (VPWS) configuration, some circuits remain down in the Standby RP and after SSO is performed.
Conditions: This issue occurs after single MTU change operation to update MTU to a valid value is performed on a set of interfaces (in the range of 100’s).
Workaround: Retry MTU change either on a smaller set of interfaces or on those interfaces separately for which circuits are down.
Symptom: Error logs seen on removal of IPv6 address on the BDI interface.
Conditions: This issue occurs after removal of IPv6 address or IPv6 ISIS router on the BDI interface.
Workaround: There is no workaround.
Symptom: Memory leaks observed on router.
Conditions: This issue occurs when DMVPN crypto sessions are configured.
Workaround: There is no workaround.
Symptom: Configurations are not removed on standby RSP after unconfiguring 63 CEM channels on active RSP.
Conditions: This issue occurs after unconfiguring 63 CEM channels on active RSP on OC-3 controller.
Workaround: There is no workaround.
Symptom: Inter VRF ping fails in router memory leak.
Conditions: This issue occurs after pinging a VRF prefix in a different VRF.
Workaround: There is no workaround.
Symptom: The IOS OAM implementation displays incorrect values for dying gasp conditions for “Power Failure” and “Physical Down”.
Conditions: This issue occurs when a "Physical Down" or "Power Failure" dying gasp is sent when an IOS box is peering with an IOX box.
Workaround: Interpret a dying gasp reported as "Physical Down" as actually being "Power Failure" and vice versa.
Symptom: PID disappears after standby RSP reboot.
Conditions: This issue occurs on standby RSP reboot.
Workaround: There is no workaround.
Symptom: Local ping fails with host queue in stuck state.
Conditions: This issue occurs when a packet descriptor may get corrupted leading to host queue in stuck state.
Workaround: Reload the router.
Resolved Caveats—Cisco IOS XE Release 3.12.2S
This section documents the issues that have been resolved in Cisco IOS XE Release 3.12.2S.
Symptom: Router crash observed to an address error.
Conditions: This issue occurs due to a Kron policy configuration.
Workaround: Remove the Kron configurations from the system.
Symptom: H-QoS top level service-policy fails on the router after switching between RSP modules.
Conditions: This issue occurs after switching RSP modules.
Workaround: Reattach the policy-map.
Symptom: ACL QoS classification breaks with IPSec tunnel.
Conditions: This issue occurs with ACL classification in policy-map and is applied to a physical interface. QoS pre-classify is configured under IPSec tunnel.
Workaround: Apply a QoS to IPSec tunnel.
Symptom: Bandwidth percentage does not work on changing the port speed.
Conditions: This issue occurs on changing bandwidth percentage.
Workaround: There is no workaround.
Symptom: Multicast traffic stops flowing over pseudowire on changing the configuration.
Conditions: This issue occurs when BDI goes down and comes up.
Workaround: Reload the device.
Symptom: COS classification does not work after router reload.
Conditions: This issue occurs on a policy with class-map having cos match configuration and reload is performed.
Workaround: Remove and re-apply the policy-map.
Symptom: CMAND logs have invalid function call messages.
Conditions: This issue is observed on reload.
Workaround: There is no workaround.
Symptom: Small buffer and IDB leak seen with PIM registers on the router.
Conditions: This issue was observed with PIM registers egressing a BDI interface.
Workaround: Block PIM registers using boundaries.
Symptom: Memory leak observed in normal buffer output of router.
Conditions: This issue occurs under normal conditions.
Workaround: Remove the qos pre-classify command in the crypto map. Reload the device. Use the memory-size iomem command to assign more memory.
Symptom: MTU settings on POS interface do not work correctly.
Conditions: This issue occurs when POS is unconfigured.
Workaround: There is no workaround.
Symptom: Core interface ping fails when system has seven Layer3 port-channels.
Conditions: This issue occurs on the Ten Gigabit IM inserted in slot 1.
Workaround: There is no workaround.
Symptom: GETVPN GM stops decrytping traffic after TEK rekey.
Conditions: This issue occurs on crypto map.
Workaround: There is no workaround.
Symptom: Restarting the router may flush and later originate default type-5 LSA during NSF/NSR restart. The flush may cause traffic loss.
Conditions: This issue occurs on NSF or NSR restart.
Workaround: There is no workaround.
Symptom: RSP1A crashes when multicast VPN configuration is used but SDM profile remains default.
Conditions: This issue occurs when show platform hardware pp active nqatm 0 ipv4tunnel all command is executed.
Workaround: Use correct SDM profile.
Open Caveats—Cisco IOS XE Release 3.12.1S
There are no open caveats in Cisco IOS XE Release 3.12.1S.
Resolved Caveats—Cisco IOS XE Release 3.12.1S
This section documents the issues that have been resolved in Cisco IOS XE Release 3.12.1S.
Symptom: IPv4 labelled BGP traffic drops on the router.
Conditions: This issue occurs for prefixes after a reload of the router.
Workaround: There is no workaround.
Symptom: Multicast traffic is not sent over BDI interface with IGMP snooping enabled.
Conditions: This issue occurs on the router when IGMP snooping is enabled.
Workaround: Disable IGMP snooping.
Symptom: Continuous increase in output drop counters observed on the interface despite no traffic flow through the interface.
Conditions: This issue occurs on port-channel configurations with QOS applied on them.
Workaround: Remove the QoS configuration.
Symptom: AutoNegotiation configuration on the fiber ports is not retained after IM OIR or reload.
Conditions: This issue occurs on IM OIR/ or router reload.
Workaround: Do not disable the AutoNegotiation property on the fiber ports, else reconfigure the AutoNegotiation on the ports manually.
Symptom: Critical alarm goes out on FPGA of port.
Conditions: This issue occurs after performing an SSO on the router.
Workaround: There is no workaround.
Symptom: Class-map filter modification do not work for uninstalled policy-maps.
Conditions: This issue occurs when a policy-map with 2 classes exist on the router. Modify the class-map filter gets rejected.
Workaround: Remove the class from the policy-map and modify it.
Symptom: DHCP packets getting dropped on a transparent node between client and server.
Conditions: This issue occurs when global DHCP snooping is enabled on the transparent node.
Workaround: Disable the global DHCP snooping feature.
Symptom: Bulk sync failure seen on router when DAI is configures and ip arp inspection filter nag bridge-domain static command is executed.
Conditions: This issue occurs with DAI configuration.
Workaround: After switchover or router reload, configure the c ip arp inspection filter nag bridge-domain static command.
Symptom: Router crash observed after reload.
Conditions: This issue occurs in normal conditions. There is no specific trigger or condition under which this may occur.
Workaround: There is no workaround.
Symptom: Forwarding Manager (FMAN) FP logs filled with error messages.
Conditions: This issue is observed on image upgrade.
Workaround: There is no workaround.
Further Problem Description:
Symptom: P TV does not work with RSP1B video template.
Conditions: This issue occurs when BDI numbers lesser than 4000 is used.
Workaround: Use BDI numbers greater than 4000.
Open Caveats—Cisco IOS XE Release 3.12S
This section documents the unexpected behavior that might be seen with the Cisco ASR 900 router in Cisco IOS XE Release 3.12.S.
Symptom: Egress traffic drop was observed on an ACR ATM interface in PVP mode.
Conditions: This issue occurs on the ACR ATM interface after performing SSO.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS XE Release 3.12S
This section documents the issues that have been resolved in Cisco IOS XE Release 3.12S.
Symptom: Traffic drop observed on the router.
Conditions: This issue occurs after performing an IM OIR.
Workaround: There is no workaround.
Symptom: Multicast does not function in scaled mode with SM mode and BDI in core.
Conditions: This issue was seen in the scaled mode.
Workaround: Execute the no ip igmp snooping command on the router to forward multicast traffic.
Symptom: Multicast packets with TTL=0 are forwarded and not dropped.
Conditions: This issue occurs with multicast incoming traffic with TTL=0.
Workaround: There is no workaround.
Symptom: Layer 3 multicast traffic drop was observed on the trunk port.
Conditions: This issue occurs when multicast is converged, and a shutdown followed by a no shutdown command is executed on the multicast router interface (mrouter port).
Workaround: Execute command clear ip mroute command to clear IPv4 multicast routes and the command clear ipv6 pim topology to clear IPv6 multicast routes.
Symptom: Multicast receivers received duplicate traffic.
Conditions: This issue occurs in the following conditions:
– Executing a shutdown command or default shutdown command on the last EFP under a bridge-domain configured on the port-channel interface.
– Executing a shutdown or default shutdown command on the last TEFP under a bridge-domain configured on the port-channel interface.
– Executing a shutdown or default shutdown command on the port-channel and configuring an EFPor TEFP without waiting for at least 3 minutes.
– Deleting the last TEFP on a particular NILE (either 0 or 1 or both) and immediately configuring EFP under the same port and for the same bridge-domain.
Workaround: Clearing multicast routes for the multicast group receiving duplicate traffic may resolve the issue. Execute command clear ip mroute command to clear IPv4 multicast routes and the command clear ipv6 pim topology to clear IPv6 multicast routes.
Symptom: The router displays an OUT_OF_TCAM error message on the console.
Conditions: This issue occurs when a PIM-enabled interface is added or deleted.
Workaround: Reload the router.
Symptom: S/N entries are allocated for BDI in down state.
Conditions: This occurs when the BDI state is down.
Workaround: There is no workaround.
Symptom: Deletion of last EFP configured under port-channel fails to update ASIC in the router. The EFP is removed from the running configuration but the router continues to forward multicast traffic on the last EFP configured under the port-channel.
Conditions: This issue occurs under the following conditions:
– Defaulting port-channel interface.
– Executing the shut or no shut commands on the port-channel interface.
– Executing the shut or no shut commands on the last EFP of a bridge-domain under the port-channel.
Workaround: There is no workaround.
Symptom: Multicast traffic was flooded back on Source Tx port.
Conditions: This issue occurs when:
– The router is configured with PIM-SM.
– IIF is the Trunk EFP (BDI) and OIF is used as the Regular EFP.
– Both IIF and OIF are in the same bridge-domain (BD).
The Trunk EFP IIF configuration is removed with (either no service instance or port default) and a Normal EFP is configured on the same IIF Port belonging to the same BD.
Workaround: Execute the clear ip mroute command.
Symptom: EMPLSintd memory leak is observed on configuration and unconfiguration of remote LFA FRR tunnels.
Conditions: This issue occurs when memory leaks are seen on interface flap or after unconfiguring and configuring the remote LFA FRR.
Workaround: There is no workaround.
Symptom: Self ping fails when ICMP punt traffic congests the host queue.
Conditions: This issue occurs when the host queue is congested by ICMP punt traffic for a long time.
Workaround: There is no workaround.
Symptom: Remote MEPs are not learnt on cross-connect service with a POS interfaces the core link.
Conditions: This issue occurs when CFM up MEPs are configured for an cross-connect service configured on an access interface, with POS links in core.
Workaround: There is no workaround.
Symptom: Packet drop observed after resetting the multilink bundle more than 3 or 4 times.
Conditions: This issue occurs on an MLPPP interface over channelized STM.
Workaround: Configure the remote end to accept compressed packets.
Symptom: Ping failure observed on the interface connected with port 0/0/0 with ACR configuration.
Conditions: This issue occurs when ACR is configured on the router.
Workaround: Install the IM in the other bay or use a port other than 0/0/0 as the core.
Symptom: The r outer shuts down when the SNMP host is enabled by executing the snmp-server host command globally.
Conditions: This issue occurs when the snmp-server host command is executed.
Workaround: Use the management interface VRF for the SNMP host.
Symptom: Bulk synchronization fails for ATM layer 2 configuration on T1E1 IM is observed on the router.
Conditions: This issue occurs on TDM IM with ATM configuration.
Workaround: There is no workaround.
Symptom: No alarm is reported after executing the shutdown command on the controller, when high availability (HA) is setup.
Conditions: This issue occurs when a POS interface is created on an HA setup, and a shutdown command is executed on the interface after SSO.
Workaround: There is no workaround.
Symptom: Increased usage of MPLSintd observed after scale configuration and stress test. Interface flaps and BFD flaps are observed on the router.
Conditions: This issue occurs with increased usage in MPLSintd resource leading to router crash over a prolong period of time.
Workaround: There is no workaround.
Symptom: ONS-SC-155-EL optic is not recognized by the router when inserted in the OC-3 IM.
Conditions: This issue occurs when the ONS-SC-155-EL optic is inserted in the OC-3 IM on the router. An error message is displayed on the console indicating that the transceiver is not supported. The optic is not detected when the show inventory command is executed.
Workaround: There is no workaround.
Symptom: Ping fails when the ARP type is in UNKNOWN state
Conditions: This issue occurs when the Cisco ASR 903 router acts as a helper and resides between the DHCP sever and a Cisco ASR 901 router.
Workaround: Execute the shutdown command followed by the no shutdown command on the interface. Execute clear arp-cache command, to clear the cache.
Symptom: IGMP snooping is not supported with the IP services license, thereby breaking multicast routing.
Conditions: This issue occurs with IP service licenses.
Workaround: Disable IGMP snooping and cause flooding of multicast packets.