Release Notes for the Cisco ASR 900 Series Routers
IOS XE Release 3.11 Restrictions and Caveats
Downloads: This chapterpdf (PDF - 238.0KB) The complete bookPDF (PDF - 2.66MB) | The complete bookePub (ePub - 298.0KB) | Feedback

Table of Contents

Restrictions and Caveats in CiscoIOSXE3.11S Releases

Caveats in CiscoIOSXE3.11S Releases

Bug Search Tool

Open Caveats—Cisco IOS XE Release 3.11.2S

Resolved Caveats—Cisco IOS XE Release 3.11.2S

Open Caveats—Cisco IOS XE Release 3.11.1S

Resolved Caveats—Cisco IOS XE Release 3.11.1S

Open Caveats—Cisco IOS XE Release 3.11S

Resolved Caveats—Cisco IOS XE Release 3.11S

Restrictions and Caveats in Cisco IOS XE 3.11S Releases

This chapter provides information about restrictions and caveats in Cisco IOS XE 3.11 releases.


Note We recommend that you view the field notices for the current release to determine whether your software or hardware platforms are affected. You can access field notices at http://www.cisco.com/en/US/support/tsd_products_field_notice_summary.html.


Caveats in Cisco IOS XE 3.11S 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.11S 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.

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.

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)

The following sections describe the open and resolved caveats in 3.11S Releases:

Open Caveats—Cisco IOS XE Release 3.11.2S

  • CSCuo11380

Symptom: AIS alarm observed on OC-3 controller.

Conditions: This issue occurs during a reload or after performing multiple IM OIR.

Workaround: Perform a soft OIR on the IM.

  • CSCuo40840

Symptom: Layer2 traffic on TEFP is punted to CPU.

Conditions: This issue occurs on loading and removing the configuration using config replace procedure.

Workaround: There is no workaround.

  • CSCuo85701

Symptom: Prec6 packets get incremented after interface flaps and reload is performed.

Conditions: This issue occurs after configuring policy-maps with classifying cos 6 and prec 6 packets on port channel

Workaround: There is no workaround.

  • CSCuo95061

Symptom: Ping fails when standby configured with Hot Standby Router Protocol (HSRP) takes over from the active RSP.

Conditions: This issue occurs when standby configured with HSRP takes over from the active RSP.

Workaround: There is no workaround.

  • CSCuo97889

Symptom: IPv6 traffic gets dropped while doing an SSO.

Conditions: This issue occurs during SSO.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS XE Release 3.11.2S

  • CSCul50165

Symptom: The Cisco ASR 903 fails to forward packets with the maximum configurable MTU on A900-IMA16D and A900-IMA4OS.

Conditions: This issue occurs when mtu max MTU interface command is executed.

Workaround: There is no workaround.

  • CSCum05115

Symptom: IPv4 labeled BGP traffic drops on the router.

Conditions: This issue occurs for prefixes after a reload of the router.

Workaround: There is no workaround.

  • CSCum45110

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.

  • CSCun07802

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.

  • CSCun47966

Symptom: Memory leak observed during ASP switchover.

Conditions: This issue occurs when APS switchover is performed.

Workaround: There is no workaround.

  • CSCun70703

Symptom: Interface Module Goes to out of service after ISSU.

Conditions: This issue occurs after performing ISSU when there is a IM FPGA change.

Workaround: Perform IM FPGA upgrade using the package file and proceed with ISSU.

  • CSCun75471

Symptom: Memory usage gradually increases over time, when storm control feature is enabled on the router.

Conditions: This issue is observed when storm control feature is enabled.

Workaround: There is no workaround.

  • CSCun79358

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.

  • CSCun83203

Symptom: Bandwidth percentage does not working on changing the port speed.

Conditions: This issue occurs after changing the port speed.

Workaround: There is no workaround.

  • CSCuo03508

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 ip arp inspection filter nag bridge-domain static command.

  • CSCuo05897

Symptom: Multicast traffic stops flowing over psuedowire on changing the configuration. The traffic does not resume till reloaded.

Conditions: This issue occurs on changing the configuration.

Workaround: Reload the device.

  • CSCuo06895

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.

Open Caveats—Cisco IOS XE Release 3.11.1S

This section documents the unexpected behavior that might be seen with the Cisco ASR 903 router in Cisco IOS XE Release 3.11.1S.

  • CCSCul58083

Symptom: After IP mtu is configured on an interface, any change in to the MTU are not reflected on the interface.

Conditions: This issue occurs when IP MTU is configured and the MTU is changed.

Workaround: Set the required interface MTU before executing the ip mtu command or unconfigure the IP MTU on the interface and then change the interface MTU.

  • CSCul58148

Symptom: After setting the MTU on an interface, the ip mtu is also set. However, when the interface is defaulted, the ip mtu setting is not unconfigured.

Conditions: This issue occurs when the IP address is set on the interface and MTU is configured. The issue occurs when the interface is defaulted

Workaround: Do not default the interface. Use no mtu command instead.

  • CSCum70550

Symptom: IPv4 and MPLS TTL does not get decremented when fragmentation is involved in the same router.

Conditions: This issue occurs when IP fragmentation is performed.

Workaround: There is no workaround.

  • CSCum81665

Symptom: Console errors and incremental leaks are observed on the Cisco ASR 903 router.

Conditions: This issue is observed on executing the clear ip mroute with pim-ssm configured for core replication.

Workaround: There is no workaround.

  • CSCum85248

Symptom: Stale entries do not get timed out or get removed, even after there is no multicast traffic for the corresponding group.

Conditions: This issue occurs when the supported limit of entries is exceeded.

Workaround: Reload the router to remove the entries.

Resolved Caveats—Cisco IOS XE Release 3.11.1S

This section documents the issues that have been resolved in Cisco IOS XE Release 3.11.1S.

  • CSCuj34652

Symptom: IPv6 traffic drops for the packets with next header options. Next header options include Hop-by-hop options, fragment header.

Conditions: This issue occurs when option packets are punted to CPU and generates the time exceeded message.

Workaround: There is no workaround.

  • CSCuj43795

Symptom: The port in error-disabled state & physical status shows as down but is UP on the other connected end device.

Conditions: This issue occurs when the port is configured with DHCP rate limiting values so that the port goes to error-disable state once it reaches the rate configured.

Workaround: Perform a shutdown followed by a no shutdown on the respective interface to move the port to UP state.

  • CSCuj60771

Symptom: Self-generated DHCP traffic generating out of the router is not getting marked (cos) with user specified value.

Conditions: This issue occurs when DHCP packets (CPU to client) are not getting marked.

Workaround: There is no workaround.

  • CSCuj83619

Symptom: DHCP binding does not happen with multiple clients over T-EFP.

Conditions: This issue occurs when TEFP with multiple vlans are configured.

Workaround: Configure EFPS instead of TEFP.

  • CSCul65485

Symptom: Wrong speed and bandwidth is displayed with DWDM XFP

Conditions: This issue occurs when the DWDM XFP is inserted and the show interface command is executed.

Workaround: There is no workaround.

CSCul65832

Symptom: Multicast VPN traffic is not received by the receivers.

Conditions: This issue occurs the multicast traffic is begins and joins the VRFs.

Workaround: Increase the MTU size of the core interface on the router that is not forwarding the mVPN traffic.

  • CSCul70905

Symptom: Warning messages are seen when an HSRP group is configured on the physical interface.

Conditions: This issue occurs when an HSRP group is configured on the physical interface.

Workaround: There is no workaround.

  • CSCum14431

Symptom: MVPN traffic is incorrectly received by the receivers due to core replication not working.

Conditions: This issue occurs when large scale is present or when data MDT is used with scale for MVPN.

Workaround: Use default MDT.

  • CSCum26178

Symptom: Bert does not go in sync with hard loop; The reports display that the BERT is running forever. The BERT cannot be stopped and a new BERT cannot be started.

Conditions: This issue occurs when hard loop is configured on OC-3 controller. The BERT is not in sync & BERT is running forever & new BERT cannot be started.

Workaround: There is no workaround.

  • CSCum65037

Symptom: The set ip next-hop peer-address command configured within a route-map does not appear in the running-configuration, causing a loss in configuration across a reload.

Conditions: This issue occurs in Unified MPLS for Mobile transport model with IGP-LDP Access, IGP routes (mainly CSG loopbacks) from Access ring would be redistributed into BGP in the pre-aggregation device (Cisco ASR 903 router). When this happens, IGP next hops that are directly connected to the pre-aggregation devices are treated as BGP next hops in the local BGP database of the pre-aggregation device. Hence when the corresponding link goes down, there might be unnecessary BGP next hop scan for AF IPv4 taking place.

Workaround: Reconfigure the set ip next-hop peer-address command within the route-map after reboot of the device to get the intended functionality.

  • CSCum69866

Symptom: ONS-SC-155-EL optic does not get recognized by the router when inserted in the OC-3 IM.

Conditions: This issue occurs on insertion of ONS-SC-155-EL optic in OC-3 IM in the router. An error message gets displayed on the console that the transceiver is not supported The optic does not get detected in show inventory command output.

Workaround: There is no workaround.

  • CSCum81574

Symptom: Ingress PE node with pim-ssm gets crashed on sending multicast traffic.

Conditions: This issue occurs when the ode gets crashed when core MDT routes reach around 1K with the video template.

Workaround: There is no workaround.

  • CSCum92427

Symptom: Ping fails when ARP type goes to UNKNOWN state.

Conditions: This issue occurs when the Cisco ASR 903 router resides between the DHCP sever and a Cisco ASR 901 router, which acts as a helper.

Workaround: Perform a shutdown followed by a no shutdown on the interface. Execute clear arp-cache to clear the cache.

Open Caveats—Cisco IOS XE Release 3.11S

This section documents the unexpected behavior that might be seen with the Cisco ASR 903 router in Cisco IOS XE Release 3.11S.

  • CSCuh86847

Symptom: When MR-APS CEM feature is configured on the router, the traffic stops flowing on deletion and recreation of CEM groups and cross connects.

Conditions: This issue occurs after deletion and recreation of CEM groups is performed and after a few iterations of performing an RSP SSO on a HA configured router.

Workaround: Perform an OIR of the OC-3 IM to resume the traffic.

  • CSCuj60116

Symptom: WANPHY:SYNC-E does not get synced in WAN mode.

Conditions: This issue occurs in WAN mode.

Workaround: There is no workaround.

  • CSCul15030

Symptom: Traffic drops for few seconds then resumes for 2-3 minutes.

Conditions: This issue may be observed with a specific topology.

Workaround: There is no workaround.

  • CSCul21349

Symptom: Crash is observed after seeing out of TCAM entries on the console.

Conditions: This issue occurs after seeing out of TCAM entries on the console.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS XE Release 3.11S

This section documents the issues that have been resolved in Cisco IOS XE Release 3.11S.

  • CSCuf35542

Symptom: Precise Frequency Monitor (PFM) fails for about 5 minutes after OIR is performed.

Conditions: This issue occurs after an OIR is trigger ed.

Workaround: Wait for 5-6 minutes after an OIR.

  • CSCug05491

Symptom: The router drops traffic on VPLS circuits.

Conditions: This issue occurs when REP is configured with VLAN load balancing and VPLS VFI is configured on the VLANs. This issue occurs after Stateful switchover (SSO) is performed.

Workaround: There is no workaround.

  • CSCug39899

Symptom: Traffic stops flowing go through QinQ BDI interface after ARP times out and the ARP is removed by shutting the BDI interface.

Conditions: This issue occurs when static routing is configured and no routing protocol is configured on the interface.

Workaround: Manually resolve ARP by pinging the next hops BDI interface.

  • CSCug44762

Symptom: POS interface stays down after a shutdown followed by a no shutdown on POS interface.

Conditions: This issue is seen when a shutdown followed by a no shutdown is performed on POS interface.

Workaround: Perform shutdown followed by a no shutdown on the controller.

  • CSCug50283

Symptom: Only 2-path are utilized for load sharing though 3-path is available.

Conditions: This issue occurs when ECMP is configured.

Workaround: There is no workaround.

  • CSCug61505

Symptom: The platform enable command is seen for ACR virtual controller when OC-3 IM is present in slot 0.

Conditions: This issue occurs after configuring aps group acr command on the OC-3 controller.

Workaround: Insert the IM in other bays instead of bay 0.

  • CSCug83434

Symptom: Lot of memory leak chunks are seen for FMANRP on the standby RSP.

Conditions: This issue occurs after memory leaks are verified on standby RSP.

Workaround: Perform a router reload.

  • CSCug84082

Symptom: ATM/IMA PVP links configured on either T1/E1 IM or OC-3IM exhibit traffic or ping failure.

Conditions: This issue occurs when ATM/IMA link flaps and is followed by SSO. Link flap can be IM OIR, etc.

Workaround: Performing an IM OIR may fix the issue, else perform a router reload.

  • CSCug84428

Symptom: Traffic drop are seen on the T1/E1 IM serial and MLPPP links.

Conditions: This issue occurs when traffic is sent via streams with jumbo packet sizes of 7000 bytes or larger. The interfaces toggle between the up/down state.

Workaround: Perform a IM OIR of the T1/E1 IM.

  • CSCug89348

Symptom: IOSXE_RP_SPA-3-IPCPORTFAIL tracebacks are seen on router with high availability configured.

Conditions: This issue occurs after SSO is performed.

Workaround: There is no workaround.

  • CSCug92536

Symptom: PLATFORM-3-NOMAC traceback is seen on standby console.

Conditions: This issue is seen when CEM-ACR is configured on a HA setup.

Workaround: There is no workaround.

  • CSCug96958

Symptom: IMA interfaces stay up when controller is shutdown.

Conditions: This issue occurs after performing an admin shutdown on OC-3 controller.

Workaround: Perform no shutdown on the controller.

  • CSCug97639

Symptom: IPv4 VRF ping fails when disabling IPv6 unicast-routing globally on the router.

Conditions: This issue occurs when IPv6 unicast-routing is disabled.

Workaround: Enable IPv6 unicast-routing

  • CSCuh06123

Symptom: Incorrect quality level (QL) mapping between the clock class and quality level on the PTP master.

Conditions: This issue is seen when QL value is configured before configuring the PTP master.

Workaround: Reconfigure the QL values or reload the router.

  • CSCuh18073

Symptom: In a domain with 2 BGP exit points acting in Active or Repair mode, the traffic exits the domain through Repair Path BGP PE instead of exiting through Active Path BGP PE.

Conditions: This issue exists when the environment has 2 BGP exit points.

Workaround: There is no workaround.

  • CSCuh22045

Symptom: Small MTU size is not fragmented on the OC-3 IM.

Conditions: This issue occurs after a reload and SSO is performed.

Workaround: Unconfigure and configure the IM.

  • CSCuh46103

Symptom: The BDI statistics do not get incremented on the router.

Conditions: This issue occurs when the ingress and egress statistics are displayed using the show interface bdi or show interface bdi stats command.

Workaround: Use show platform hardware pp active interface statistics bdi command.

  • CSCuh81658

Symptom: PTP packets are being treated as default packets even though QOS policy is configured

Conditions: This issue occurs after CPU generated PTP packets do not reach egress QoS with high priority label (15 or 126) and hence does not hit the corresponding default port entries or even the EFP policy’s control entries matching these labels.

Workaround: There is no workaround.

  • CSCuh93765

Symptom: The interface goes down reporting loss of frame alarm.

Conditions: This issue occurs on performing shutdown followed by a no shutdown on the PE and CE.

Workaround: Perform an OIR on CE side.

  • CSCui22637

Symptom: Crash observed on the router after unconfiguring 1000 psuedowires.

Conditions: This issue occurs after unconfiguring 1000 psuedowires at a stretch.

Workaround: There is no workaround.

  • CSCui30240

Symptom: SPA is not initialized messages are seen on bootup.

Conditions: This message is seen post bootup as well during shutdown command followed by a no shutdown command is issued on the controller. This issue occurs on remote PE reload.

Workaround: Disable console logging.

  • CSCui34041

Symptom: Traffic is not flowing for one of the prefix.

Conditions: This issue occurs when the MAX MPLS label of that template is assigned to that prefix.

Workaround: Disable and enable that prefix.

  • CSCui34989

Symptom: OC-3 IM IOMD crash is seen post SSO.

Conditions: This issue occurs after SSO is performed.

Workaround: There is no workaround.

  • CSCui47776

Symptom: Virtual circuit receive counters do not increment after SSO is performed.

Conditions: This issue occurs when 1000 VCs are configured and SSO is performed.

Workaround: There is no workaround.

  • CSCui52938

Symptom: Layer 3 interface adjacency is incomplete.

Conditions: This issue occurs after the RSP is removed from the router.

Workaround: There is no workaround.

  • CSCui55567

Symptom: Traffic convergence for OC-3 IM with TDM features such as serial, MLPPP or POS is high after RSP SSO.

Conditions: This issue occurs after SSO is performed.

Workaround: There is no workaround.

  • CSCui75901

Symptom: Sync packets are not sent at a regular interval by the router and inter-packet gap is not within the standard range.

Conditions: This issue occurs under normal conditions.

Workaround: There is no workaround.

  • CSCui97872

Symptom: The controller remains in disabled state after enabling the license.

Conditions: This issue occurs on performing IM OIR or framing.

Workaround: Disable the license and enable it.

  • CSCuj06140

Symptom: SPAN captured packet has wrong destination MAC address.

Conditions: This issue is seen when MPLS-TP BFD packet is captured.

Workaround: There is no workaround.

  • CSCuj07507

Symptom: High convergence for downstream traffic observed on the router.

Conditions: This issue occurs when VPLS VFI’s controlled by g.8032 open ring with a large scale of about 500VC’s and 10000 MAC address (40 per BD).

Workaround: Use a lower MAC address scale.

  • CSCuj46477

Symptom: Layer 2 multicast traffic stops on VPLS VCs and starts flowing back on the ingress EFP.

Conditions: This issue occurs when one of the VPLS VC goes down.

Workaround: Traffic resumes after the VC comes up.

  • CSCuj55599

Symptom: ARP request for HSRP VRRP MAC (VMAC) is not punted to CPU.

Conditions: This issue occurs while sending unicast ARP packets on the router.

Workaround: There is no workaround.

  • CSCuj76162

Symptom: The input error counter constantly increases in show platform infrastructure lsmpi command.

Conditions: This problem occurs when the synchronous mode is configured on the interface of router.

Workaround: There is no workaround.

  • CSCul14925

Symptom: The following message displays on the console:

%PMAN-3-PROCHOLDDOWN: SIP1: pman.sh: The process iomd has been helddown (rc 143)

Conditions: When you perform a hard interface module (IM) online insertion and removal (OIR), IM pull out, or soft IM OIR and IOMD is gracefully terminated from the kernel.

Workaround: There is no workaround. There is no service impact.