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

Table of Contents

Restrictions and Caveats in CiscoIOSXE3.10S Releases

Limitations and Restrictions

Caveats in CiscoIOSXE3.10S Releases

Bug Search Tool

Caveats

Open Caveats—Cisco IOS XE Release 3.10.4S

Resolved Caveats—Cisco IOS XE Release 3.10.4S

Open Caveats—Cisco IOS XE Release 3.10.3S

Resolved Caveats—Cisco IOS XE Release 3.10.3S

Resolved Caveats—Cisco IOS XE Release 3.10.(2)aS

Open Caveats—Cisco IOS XE Release 3.10.2S

Resolved Caveats—Cisco IOS XE Release 3.10.2S

Open Caveats—Cisco IOS XE Release 3.10.1S

Resolved Caveats—Cisco IOS XE Release 3.10.1S

Open Caveats—Cisco IOS XE Release 3.10S

Resolved Caveats—Cisco IOS XE Release 3.10S

Restrictions and Caveats in Cisco IOS XE 3.10S Releases

This chapter provides information about restrictions and caveats in Cisco IOS XE 3.10 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.


This chapter contains the following sections:

Limitations and Restrictions

The following limitations apply to the Cisco ASR 903 Router in IOS XE Release 3.10(0)S:

TDM Limitation

  • The configure replace command is not supported for TDM interfaces.

IPv6 Limitations

The following limitation applies when using IPv6 on the Cisco ASR 903 Router:

  • IPv6 Neighbor Discovery (ND) cache timer expiry is 4 hours. To prevent the neighbor adjacency from being deleted after the timer expires:

configure hardware based BFD sessions with the neighbors, or

configure static IPv6 neighbors, or

configure the ipv6 nd cache expire timer refresh command.

OC-3 IM Limitations

  • The configure replace command is not supported on the OC-3 IMs.

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

Open Caveats—Cisco IOS XE Release 3.10.4S

  • CSCuq38761

UMMT: BFD triggered FRR does not work as expected over BDI interface.

  • CSCuq60722

RSPPID has disappeared from show platform diag command after reloading standby RSP.

  • CSCuq87125

DPS fix for MLPPP buffer leak issue.

  • CSCuq92777

Port-channel not getting removed-FMAN manager on deleting from IOS.

Resolved Caveats—Cisco IOS XE Release 3.10.4S

  • CSCun07843

Critical Alarm reporting link down on FPGA port 0/5/0 after SSO.

  • CSCuo09866

RSP1:FMAN-FP logs are flooded with error messages creating many trace log files.

  • CSCuo15916

QoS classification does not work after reload.

  • CSCuo21766

SNMP IF-MIB "ifHCOutUcastPkts" and "ifInUcastPkts" fetches wrong value.

  • CSCuo26304

CMAND logs are filled with "func call cman_cc_invalid" every minute.

  • CSCuo76490

PIM register causes small buffer and IDB leak over BDI interface.

  • CSCup03938

Enable 9K Jumbo packet length on Cisco ASR 903.

  • CSCup06402

Cisco ASR 903: BGP session flaps with shaped egress policy.

  • CSCup20634

Core interface ping fails when router has seven L3 Port-channels.

  • CSCuq12880

Cisco ASR 903 crashes on running show platform hard pp active nqatm 0 ipv4tunnel all command.

Open Caveats—Cisco IOS XE Release 3.10.3S

  • 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.

  • 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.10.3S

  • 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.

  • CSCum54906

Symptom: Crash observed on the router after executing the show interfaces pseudowire counters command.

Conditions: This issue occurs after executing the show interfaces pseudowire counters command.

Workaround: There is no workaround.

  • 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.

Resolved Caveats—Cisco IOS XE Release 3.10.(2)aS

This section documents the issues that have been resolved in Cisco IOS XE Release 3.10.(2)aS.

  • CSCul06921

Symptom: Port-channel member-links flaps are observed on the router.

Conditions: This issue is seen on router switchover.

Workaround: There is no workaround.

Open Caveats—Cisco IOS XE Release 3.10.2S

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

  • CSCuf15863

Symptom: Traffic loss of few milliseconds seen on the router.

Conditions: This issue occurs when remote LFA is configured on the core, and on shutting a primary path, the site which is not on primary path gets some milliseconds loss.

Workaround: There is no workaround.

  • CSCuf35464

Symptom: The active bits port does not send out the QL properly which is received from the remote bits.

Conditions: This issue occurs when the remote bits are configured as input and active bits as output.

Workaround: There is no workaround.

  • CSCui74718

Symptom: %EVENTLIB-3-RUNHOG tracebacks are reported on the console.

Conditions: This issue occurs when the router is configured in PTP slave mode. The clock is in phase aligned state and PTP configurations are removed using the no ptp clock ordinary domain command.

Workaround: There is no workaround.

  • CSCul07048

Symptom: IPv6 nd cache expire after reload or IM OIR is performed.

Conditions: This issue occurs when ISIS with BFD is enabled on the BDI interface.

Workaround: Reload or replace the configuration.

  • CSCul50165

Symptom: The router fails to forward packets with the maximum configured MTU.

Conditions: This issue was observed on MLPPP, T1, POS interfaces when the mtu max MTU interface command was executed on the router.

Workaround: There is no workaround.

  • CSCul58083

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.

  • CSCum40613

Symptom: The TOD port on the router does not function when configured as slave.

Conditions: This issue occurs after configuring TOD on the router.

Workaround: There is no workaround.

  • CSCum47925

Symptom: SSO convergence time of ~0.9 sec is observed with 100m SFP.

Conditions: This issue occurs when VPLS VC and EVC BD exists on the access.

Workaround: There is no workaround.

  • CSCum79011

Symptom: Pending objects take a long time (approx 30 min) to clear on the router.

Conditions: This issue occurs when QoS-policy is applied on member-link and services like psuedowire, HSRP on BDI are configured on the port-channel.

Workaround: There is no workaround.

  • CSCun70703

Symptom: Interface module goes to out of service during ISSU and when FPGA is changed.

Conditions: This issue occurs on performing ISSU when there is a IM FPGA change between the releases.

Workaround: Perform the following:

Perform IM FPGA upgrade using the package file.

Proceed with ISSU.

Resolved Caveats—Cisco IOS XE Release 3.10.2S

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

  • CSCuf35542

Symptom: PFM fails for about 5minutes after OIR on the master.

Conditions: This issue occurs after OIR is triggered two times on the master

Workaround: Wait for 5-6 minutes

  • CSCuh06123

Symptom: QL-mapping displays incorrectly on master.

Conditions: This issue occurs when QL value is configured first and then PTP master is configured

Workaround: Reconfigure QL values or reload the router.

  • CSCuh49073

Symptom: OSPF does not come up when PIM is enabled on the VPLS core interface.

Conditions: This issue occurs when PIM is enabled on the VPLS core interface.

Workaround: There is no workaround.

  • CSCuh54159

Symptom: Packet drops are seen under QOS policy map attached on the multilink bundle for traffic rate less than bundle capacity

Conditions: This issue occurs when unexpected packet drops are seen for QOS for traffic rates less than bundle bandwidth. After reloading the router with QOS policy attached on bundle, packet prioritization into different queues with differing bandwidth profiles occurs.

Workaround: Remove and reattach the policy map on the bundle

  • CSCui41169

Symptom: Active card reloads when standby comes active after switchover with scaled configuration

Conditions: This issue occurs when 4000K EVCs with 1-level ingress policy, and 2-level egress policy is configured on the router. Ingress policy should have 1-level policer, egress policy should have one parent and child policer. The issue occurs after a reload of the card with this configuration.

Workaround: There is no workaround.

  • CSCui44409

Symptom: No console message are seen on insertion or removal of USB

Conditions: This issue is observed standby RSP.

Workaround: More Info:

  • CSCui45075

Symptom: When an IM is removed from the router, the MST states are not reflected in the standby RSP. If a switchover happens at this state, it could cause total traffic drop.

Conditions: This issue is seen when HA is configured on the router.

Workaround: There is no workaround.

  • CSCui98883

Symptom: System crashes on configuring TOD.

Conditions: This issue occurs on dual RSP setup and PTP is configured.

Workaround: There is no workaround.

  • CSCui99309

Symptom: IPv6 BFD with static client does not display when VRF is configured.

Conditions: This issue occurs when VRF is configured on the router.

Workaround: There is no workaround.

  • CSCuj30644

Symptom: Multicast does not function in scaled mode and when BDI is configured on the core.

Conditions: This issue was seen in the scaled mode.

Workaround: Execute the no ip igmp snooping command on the router to forward the multicast traffic.

  • 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.

  • CSCuj38988, CSCum45935

Symptom: QL does not move to QL-FAILED state when the Gigabit ethernet interface is shutdown.

Conditions: This issue occurs when the Gigabit ethernet interface is shutdown.

Workaround: There is no workaround.

  • CSCuj42208

Symptom: Layer3 multicast traffic drop is seen on Trunk port.

Conditions: This issue occurs when multicast is converged. Performing a shutdown followed by a no shutdown on the multicast router interface fails to transmit multicast traffic to TEFP’s.

Workaround: Clear IP multicast routes using clear ip mroute command for IPv4 traffic and clear ipv6 pim topo command for IPv6 traffic.

  • CSCuj43453

Symptom: IOSd crash was seen on the router on bootup of PTP process.

Conditions: This issue occurs during bootup when multiple reloads of the router is performed.

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.

  • CSCuj60116

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

Conditions: This issue occurs in WAN mode.

Workaround: There is no workaround.

  • 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.

  • CSCuj96689

Symptom: Queue-limit command is not programmed for priority queue.

Conditions: This issue occurs when the policy map has both BRP and Priority queue with queue-limit configured for priority queue.

Workaround: Perform the following;

Attach the policy with all BRP configuration.

Dynamically add the queue-limit command to the priority class.

  • CSCul10279

Symptom: Crash observed on the router with multicast VPN configuration.

Conditions: This issue occurs when the router is configured with multicast VPN IPv4 configuration, Scaled ACL and IGMP Static Join configuration.

Workaround: There is no workaround.

  • CSCul11877

Symptom: HSRP standby router cannot ping the virtual IP.

Conditions: This issue occurs when the BDI interfaces are configured along with a range of bridge domains.

Workaround: There is no workaround.

  • CSCul21294

Symptom: PTSF alarms do not get posted when the egress interface is shutdown.

Conditions: This issue occurs when a PTP slave has one or more masters.

Workaround: There is no workaround.

  • CSCul21429

Symptom: The router console freezes and the OSPF or BFD sessions flap.

Conditions: This issue occurs when TOD type is changed dynamically on a PTP master from NTP to Cisco or vice-versa.

Workaround: Unconfigure TOD and reconfigure a new TOD type.

  • CSCul21447

Symptom: The ANNOUNCE message does not get updated.

Conditions: This issue occurs in the PTP slave.

Workaround: There is no workaround.

  • CSCul40676

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 change the port other than 0/0/0 as the core.

  • CSCul46353

Symptom: Traffic drop observed on priority queues.

Conditions: This issue occurs on QoS policy with 2-level priority queues (priority level classes) that do not guarantee the bandwidth on 1-level priority against 2-level traffic.

Workaround: There is no workaround.

  • CSCul46643

Symptom: Convergence with SSO for REP with multicast is greater than 3 seconds.

Conditions: This issue occurs on performing an SSO on the Receiver

Workaround: There is no workaround.

  • CSCul49147

Symptom: Time exceed message is generated when IPv6 packets are received on the router.

Conditions: This issue occurs when IPv6 packets have option headers.

Workaround: If the IPv6 options have fragment header then increase the MTU size.

  • CSCul50181

Symptom: A Cisco router may see unicast traffic not being forwarded out of the Gigabit ethernet interface while multicast traffic is being processed by the router correctly.

Conditions: This issue occurs when the router has BDI configured to the Gigabit ethernet interface.

Workaround: Reload the router.

  • CSCul51784

Symptom: IPv6 packets fails to get forwarded out of the router.

Conditions: This issue occurs when unicast RPF enabled for IPv4 traffic and IPv6 traffic is received on the interface.

Workaround: Remove unicast RPF checks on the interface where dual stack is configured.

  • CSCul52778

Symptom: STM -1 port keeps on increasing on changing the card type command multiple times.

Conditions: This issue occurs after executing the card type command many times.

Workaround: There is no workaround.

  • 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.

  • CSCul65977

Symptom: Enabling DAI on one interface leads to ARP packets being dropped on another interface in the same BD or cross-connect.

Conditions: This issue occurs after enabling DAI on one interface.

Workaround: There is no workaround.

  • CSCul80289

Symptom: Crash observed on the router.

Conditions: This issue occurs after unconfiguring the BDI interface and TEFP is learnt as mrouter.

Workaround: There is no workaround.

  • CSCum02924

Symptom: PTP session gets stuck in unknown state.

Conditions: This issue occurs when OSPF, clock domain & clock source are unconfigured and reconfigured.

Workaround: There is no workaround.

  • CSCum42701

Symptom: Tx and Rx power does not display the right values for OC-3 SFP.

Conditions: This issue is seen when the controller is disabled and the SFP is inserted.

Workaround: Perform a hard OIR of the OC-3 SFP.

Open Caveats—Cisco IOS XE Release 3.10.1S

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

  • CSCue42139

Symptom: The ptp state is stuck in acquiring state all the time

Conditions: This issue occurs when the active RSP is removed; the T3 timestamping is stuck and the ptp state stays in acquiring state all the time.

Workaround: Unconfigure and configure the ptp.

  • CSCuf78234

Symptom: The queue-limit command displays packets as default.

Conditions: This issue occurs when queue-limit command is configured on the router.

Workaround: Configure queue-limit is microseconds (us) or bytes.

  • CSCug97269

Symptom: The serial interface flaps when the neighbor controller is shut.

Conditions: This issue occurs on performing shutdown on peer OC-3 controller with ATM or IMA channels.

Workaround: There is no workaround.

  • CSCuh83433

Symptom: The path level controllers status on OC-3 IM sonet controller is not displayed after a second SSO is triggered manually after removing the RSP.

Conditions: This issue is seen on hard RSP reset of RSP1.

Workaround: Perform a controller shutdown followed by a no shut down.

  • CSCui08697

Symptom: The interface LED glows green after SSO.

Conditions: This issue occurs after an SSO is performed and shut down of the ports on the router.

Workaround: There is no workaround.

  • CSCui34041

Symptom: Traffic does not flow on one of the prefix of the MPLS template.

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

Workaround: Disable and enable that prefix.

  • CSCui41169

Symptom: The active card reloads when standby become active after switchover with scaled configurations.

Conditions: This issue occurs with 4000 EVCs with first and second level ingress policy. The Ingress policy has one policer and the egress policy has one parent and child policer. This issue occurs with reloading the card with this configuration.

Workaround: There is no workaround.

  • CSCui53268

Symptom: Adding a child policy map with Vlan class to parent PHB class dynamically, does not trigger the error message.

Conditions: This issue occurs when a PHB level policy is attached to an interface and any policy is being dynamically added as a child to one of the existing PHB classes.

Workaround: Detaching the policy and performing a modification and trying to reattach displays the error.

  • CSCui62568

Symptom: No error reported when invalid policer is dynamically modified to remove the PIR configuration with violate-action.

Conditions: This issue occurs when a policy-map with CIR and PIR value attached to an EFP is dynamically modified to just CIR which make the policer have exceed action without PIR.

Workaround: Remove the violate-action first and then remove PIR configuration.

  • CSCui74718

Symptom: “%EVENTLIB-3-RUNHOG” tracebacks reported on the console.

Conditions: This issue occurs on the router in ptp slave mode. The clock is in phase aligned state and the ptp configurations are removed using the no ptp clock ordinary domain command.

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

  • CSCui92961

Symptom: 100% traffic loss is observed on few pseudowires.

Conditions: This issue occurs when the router experiences couple of link flaps.

Workaround: Issue shutdown command followed by no shutdown command on the EFP; this can be tedious if impacted pseudowire count is more.

  • CSCuj04299

Symptom: FMAN FP core traceback observed on the router.

Conditions: This issue occurs after adding several new EFPs or BDIs to running configuration and updating the QoS configuration on the physical interface

Workaround: There is no workaround.

  • CSCuj09392

Symptom: Dynamically modifying the user-defined to class-default triggers error.

Conditions: This issue was seen when modifying the user-defined to class-default.

Workaround: There is no workaround.

  • CSCuj32391

Symptom: Dynamic modify of parent with class default policer to child policer does not take effect.

Conditions: This issue occurs on dynamic modify DM of parent having class-default policer value greater than child policer value.

Workaround: Reattach the policy-map

  • CSCuj38988

Symptom: Queue-limit does not go to queue-limit failed state when we the gigabit ethernet interface is shutdown.

Conditions: This issue occurs while shutting down he gigabit ethernet interface.

Workaround: There is no workaround.

  • CSCuj51830

Symptom: Traffic drops if policy is attached on port-channel interface.

Conditions: This issue occurs when the policy is attached on port-channel interface

Workaround: Use port-channel IDs less than 10.

  • CSCuj56164

Symptom: TCAM utilization shows incorrect current usage percentage.

Conditions: This issue occurs when EQoS application is enabled.

Workaround: There is no workaround.

  • CSCun70703

Symptom: Interface module goes to out of service during ISSU and when FPGA is changed.

Conditions: This issue occurs on performing ISSU when there is a IM FPGA change between the releases.

Workaround: Perform the following:

Perform IM FPGA upgrade using the package file.

Proceed with ISSU.

Resolved Caveats—Cisco IOS XE Release 3.10.1S

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

  • CSCue60699

Symptom: Router auto negotiates full duplex with 1000M half/full duplex configuration.

Conditions: This issue occurs when a router with Copper SFP with auto-negotiating is enabled and the peer router with Cu SFP configured with 1000M half-duplex mode exists.

Workaround: There is no workaround.

  • CSCug31550

Symptom: Incorrect TCAM entries with scale configuration are displayed after reapplying the policy map.

Conditions: This issue occurs after removing the policy map and reapplying it to service instances.

Workaround: There is no workaround.

  • CSCug36190

Symptom: Object Download failures are seen when configuring cross connect on the main interface and configure cross connect under the service instance.

Conditions: This issue occurs when cross connect is configured on the main interface.

Workaround: Remove the cross connect configuration from the main interface.

  • CSCug50280

Symptom: QoS does not work on the router.

Conditions: This issue occurs while adding user class to a port level policer dynamically when the policer already has class-default configured.

Workaround: Reload the router.

  • CSCug68820

Symptom: The show inventory command does not display PSU and fan tray information.

Conditions: This issue occurs after the PSU or fan tray is inserted after bootup and SSO is performed.

Workaround: Reload after PSU or the fan tray after it is inserted.

  • CSCug70182

Symptom: The ASR903-IMA8S port remains up without the fiber.

Conditions: This issue occurs when the GLC-FE-100FX optic is used.

Workaround: There is no workaround.

  • CSCug96284

Symptom: Memory leaks seen on boot up of the router.

Conditions: This issue occurs on booting the system.

Workaround: There is no workaround.

  • CSCuh00108

Symptom: CMAND crash seen on the router.

Conditions: This issue occurs during midplane idprom read at bootup.

Workaround: Reload the router.

  • CSCuh03023

Symptom: IP connectivity over BDI fails after a link flap network event.

Conditions: This issue occurs intermittently with BDI enabled for IP/MPLS forwarding and running VPN services over it. Adjacency failures are seen after couple of link flap events, which impacts Layer3 forwarding over BDI.

Workaround: There is no workaround.

  • CSCuh13883

Symptom: Standby IOMD crashes continuously at system bootup.

Conditions: This issue occurs at system bootup and when the system waits for a user input at the initial dialog box during configuration.

Workaround: There is no workaround.

  • CSCuh16707

Symptom: The interface module (IM) status LED glows green before the PHY Init state is complete.

Conditions: This issue occurs after an IM OIR is performed.

Workaround: Use the show platform command output to check if the IM reaches the OK state.

  • CSCuh42926

Symptom: High CPU utilization is seen when Trunk EFP is configured on port channel and MAC address table limit is configured on the bridge domain.

Conditions: This issue occurs when Trunk EFP is configured on port channel and MAC address table limit is configured on the bridge domain.

Workaround: Do not use port channel.

  • CSCuh46103

Symptom: BDI statistics not getting incremented on the router.

Conditions: This issue occurs when the ingress and egress statistics displayed using show interface bdi or the show int bdi statistics command does not get incremented even if the traffic is flowing through the BDI interface.

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

  • CSCuh51651

Symptom: CPP download failures and CFM remote MEPS not learnt.

Conditions: This issue occurs during configuring CFM offload scaled configurations using TFTP.

Workaround: There is no workaround.

  • CSCuh51702

Symptom: The system shuts down after 5mins irrespective of ambient temperature after removing the fan tray.

Conditions: This issue occurs after removing the fan tray.

Workaround: There is no workaround.

  • CSCuh81135

Symptom: Port speed configuration is changed automatically on changing the SFP module.

Conditions: This issue occurs on changing the SFP module.

Workaround: There is no workaround.

  • CSCuh85990

Symptom: Some CFM MEPs are not learnt when configuring large number (about 1K) on the router.

Conditions: This issue is seen only if large number of MEPs are configured.

Workaround: Remove and re-apply the configuration.

  • CSCuh92939

Symptom: Traffic drop occurs after replacing a Cu SFP with a fiber FP

Conditions: This issue occurs after replacing Cu SFP with fiber SFP after an SSO is performed.

Workaround: Perform an IM OIR.

  • CSCuh99117

Symptom: Packet drops for some of the prefixes in MPLS network are observed.

Conditions: This issue occurs when MPLS Layer3 VPN is configured on the router with MVPN template.

Workaround: There is no workaround.

  • CSCui16418

Symptom: After a switchover is performed, the ten gigabit ethernet interface might flap and traffic drops.

Conditions: This issue occurs after SSO is performed.

Workaround: There is no workaround.

  • CSCui32127

Symptom: CFM download error-objects are observed when CFM peers are reloaded or IM OIR is done on a scaled VPLS and CFM setup.

Conditions: This issue occurs on the router with 250 or more CFM MEP sessions and more than 1250 Layer2 virtual circuit sessions.

Workaround: There is no workaround.

  • CSCui34041

Symptom: Traffic does not flow to one of the prefix on MPLS template.

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

Workaround: Disable and enable the prefix.

  • CSCui40994

Symptom: Ethernet CFM ping fails because remote MEPs are not learnt.

Conditions: This issue occurs when MIP is configured on the same Vlan as MEP on the CFM domain.

Workaround: Remove MIP configuration.

  • CSCui50577

Symptom: Traffic drops are observed on router.

Conditions: This issue occurs after performing an IM OIR.

Workaround: There is no workaround.

  • CSCui58365

Symptom: Router reboots while modifying a policy-map with class-map "match vlan 100".

Conditions: This issue occurs while attaching the "match vlan 100" egress policy-map. This issue occurs after adding an ingress policy with no-match class and then adding an egress policy with match on Vlan or dynamically adding match vlan class on egress policy.

Workaround: There is no workaround.

  • CSCui68159

Symptom: Traffic drops when two EFPs are configured on with default encapsulation and rewrite push do1q on same BD.

Conditions: This issue occurs when two EFPs are configured on with default encapsulation and rewrite push do1q on the same BD.

Workaround: There is no workaround.

  • CSCui87339

Symptom: Transceiver init_failure observed after transceiver OIR is performed.

Conditions: This issue is seen after the OIR of transceiver is performed.

Workaround: A slow OIR of transceiver might recover the port.

  • CSCui93830

Symptom: HQoS top level service-policy fails on the router when switching between the RSPs.

Conditions: This issue occurs when switching between the RSPs.

Workaround: Reattach the policy-map.

  • CSCuj07507

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

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

Workaround: Use small MAC scales for traffic.

  • CSCuj42080

Symptom: The FGPA gets stuck while pumping high volume of CFM packets.

Conditions: This issue occurs while pumping high volume of CFM packets on the router.

Workaround: There is no workaround.

  • CSCuj50260

Symptom: CFM ping fail to MPIDS on the router.

Conditions: This issue occurs when MEPS are configured over port channel.

Workaround: There is no workaround.

Open Caveats—Cisco IOS XE Release 3.10S

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

  • CSCue36365

Symptom: During initial bootup of the serial interface module, the first character of the first packet received might be missing.

Conditions: Problem occurs during a cold boot of the serial interface module.

Workaround: There is no workaround. Problem is a transient condition and traffic resumes after receipt of the first message on the module.

  • CSCue42144

Symptom: PHY stops timestamping and the session stays at acquiring state.

Conditions: This issue is observed when you insert the Cu-SFP on the slave.

Workaround: There is no workaround.

  • CSCue49537

Symptom: The Cisco ASR 903 router crashes when you perform an OC3 IM OIR.

Conditions: This issue is observed when you have about 700 CEM circuits and perform an OC3 IM OIR.

Workaround: There is no workaround.

  • CSCue87629

Symptom: The following error message is displayed:

INFRA-6-PROCPATH_CLIENT_HOG: IOS shim client ‘iosd-nile’
 

Conditions: This issue is observed when you use the shutdown and no shutdown commands on the G8032 ring interface of peer or local device.

Workaround: There is no workaround.

  • CSCuf16426

Symptom: FMAN_FP download fails and the following error message is displayed:

%CHUNK-2-BADREFCOUNT errors.
 

Conditions: Have an MPLS TE in the core and flap the tunnels intermittently.

Workaround: Do not flap the core TE tunnels often.

  • CSCug15175

Symptom: The Cisco ASR 903 router falsely displays the following error message saying that a BFD node is down:

%OSPF-5-ADJCHG: Process 232, Nbr 192.0.2.33 on BDI632 from FULL to DOWN, Neighbor Down: BFD node down
 

Conditions: This issue is observed when you configure a BFD software session.

Workaround: There is no workaround.

  • CSCug36590

Symptom: The Cisco ASR 903 router displays the following error message:

%IDBINDEX_SYNC-4-RESERVE: Failed to lookup existing ifindex for an interface on the Standby, allocating a new ifindex from the Active (ifindex=126, idbtype=SWIDB)
 

Conditions: This issue is observed when you create an ATM channel, create a POS link, or create DS3 links.

Workaround: There is no workaround.

  • CSCug43550

Symptom: The receiver node crashes when the number of traffic sources increases beyond 400 with 196 OIFs at the receiver end.

Conditions: This issue is observed when 196 IGMP packets are sent to a node per second.

Workaround: Reduce the number of IGMP packets to four per second.

  • CSCug84082

Symptom: Ping fails and traffic drops on ATM/IMA PVP links configured on either T1E1 IM or OC3 IM.

Conditions: This issue is observed when you perform an SSO and flap the ATM/IMA link.

Workaround: Perform an IM OIR or reload the router.

  • CSCug96003

Symptom: When operating with a large number of TCP Raw Socket connections (greater than 512) and with traffic on all of them we saw some TCP retransmissions.

Conditions: The issue occurred in a stress test within a lab setup.

Workaround: None required.

  • CSCuh06123

Symptom: QL mapping is incorrect on the PTP master.

Conditions: This issue is observed when you first reboot the router or configure and unconfigure the router multiple times.

Workaround: Reconfigure the Ql values.

  • CSCuh33291

Symptom: The Cisco ASR 903 router generates linkDown traps when an interface changes from administratively down state to down state.

Conditions: This issue is observed when an interface changes from administratively down state to down state.

Workaround: There is no workaround.

  • CSCuh33314

Symptom: When you perform an ISSU or terminate the IOMd process, IOMd crashes on the standby RSP.

Conditions: This issue is observed when you terminate the IOMd process on the active RSP or when you perform an ISSU.

Workaround: There is no workaround.

  • CSCuh81658

Symptom: Although a QoS policy is configured, PTP packets are treated as default packets.

Conditions: This issue is observed when the CPU-generated PTP packets do not reach egress QoS with high a priority label (15 or 126).

Workaround: There is no workaround.

  • CSCuh85041

Symptom: SNMP returns the wrong card type for the serial interface module.

Conditions: Issue occurs during SNMP walk of ASR903.

Workaround: There is no workaround. This issue is not service affecting.

  • CSCuh85990

Symptom: When you use the show ethernet cfm maintenance-points remote command, only 992 remote maintenance endpoints are displayed.

Conditions: This issue is observed when you configure CFM MEP domains on an EVC.

Workaround: There is no workaround.

  • CSCuh88500

Symptom: Standby router reloads due to SPA bulk synchronization failure.

Conditions: This issue is observed when you perform an SSO.

Workaround: There is no workaround.

  • CSCui06748

Symptom: ICMP packets are punted to the CPU even after using the no ip redirect command on the Cisco ASR 903 router.

Conditions: This issue is observed when ICMP packets are punted initially.

Workaround: There is no workaround.

  • CSCui14481

Symptom: Traffic does not flow for HSPW sessions as the tunnel ID is incorrect.

Conditions: This issue is observed when you perform an IM OIR.

Workaround: Perform an SSO and flap the access interface.

  • CSCui19632

Symptom: BFD sessions flap randomly.

Conditions: This issue is observed in FPGA version 30020.

Workaround: There is no workaround.

  • CSCui19700

Symptom: When you apply a QoS policy on the core interface, QoS counters do not increment.

Conditions: This issue is observed when you apply a policy on the access interface with 500 EFPs and apply another policy on the core interface.

Workaround: There is no workaround.

  • CSCui22637

Symptom: The Cisco ASR 903 router crashes.

Conditions: This issue is observed when you unconfigure 1000 Ethernet service instances.

Workaround: There is no workaround.

Resolved Caveats—Cisco IOS XE Release 3.10S

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

  • CSCtx70302

Symptom: Traceback and log messages are seen while performing a multilink bundle shutdown on the Cisco ASR 903 router.

Conditions: This issue is observed when traffic flows over the multilink bundle.

Workaround: There is no workaround. This issue does not impact the operation of the router.

  • CSCua61934

Symptom: When a policy map with priority in class-default is attached to an interface, it is not rejected.

Conditions: This issue is observed when you configure policy-map having priority in class-default and attach the policy to an interface.

Workaround: There is no workaround.

  • CSCua90879

Symptom: QoS policies with a police statement on the class-default class do not take effect.

Conditions: This issue is observed when you apply a police statement to the class-default class within a QoS policy on an ingress EVC interface.

Workaround: Apply the police statement to a static class, such as class cos0.

  • CSCuc59386

Symptom: IOMD crashes continuously on OC-3 IM. The interfaces on OC-3 IM are not configurable and the following error message is displayed:

stand-by does not support this command
 

Conditions: This issue is observed on a Cisco ASR 903 router high availability setup with OC-3 IM.

Workaround: Reload the standby RSP.

  • CSCuc60148

Symptom: The router does not shut down when the temperature sensor reaches the shutdown threshold.

Conditions: Temperature sensor reaches shutdown threshold.

Workaround: Use the facility-alarm critical exceed-action shutdown commands to enable system shutdown.

  • CSCuc83088

Symptom: The router drops traffic while performing a Stateful Switchover (SSO).

Conditions: This issue is observed when the router is running HSRP or VRRP. It occurs when the destination MAC address is a virtual MAC (vMAC) address.

Workaround: Change the traffic priority and detour traffic before performing an SSO.

  • CSCud09100

Symptom: The router accepts a policy with marking at two levels. It should not accept a policy with marking at two levels.

Conditions: This issue is observed when you apply a policy with marking at two levels.

Workaround: There is no workaround.

  • CSCud09813

Symptom: Timestamping does not work in CFM over cross-connected MEP with port channel.

Conditions: This issue is observed when you configure CFM over cross-connected MEP with port channel from a Cisco ASR 903 router to a Cisco ME 3600 switch.

Workaround: There is no workaround.

  • CSCud12624

Symptom: Traceback is displayed when you configure the ACR group.

Conditions: This issue is observed when you configure an ACR group.

Workaround: There is no workaround.

  • CSCud29491

Symptom: A two-level policy with match EFP in parent and PHB-based policy in child can be applied.

Conditions: This issue is observed when you apply a policy on a physical interface having EFPs on that physical interface.

Workaround: There is no workaround. This configuration is not supported.

  • CSCud34630

Symptom: The following error message is displayed on the standby machine while using the shutdown and no shutdown commands on the ACR controller:

NETWORK_RF_API-3-FAILDECODEDATADESC
 

Conditions: This issue is observed on the standby machine when you configure ACR interface.

Workaround: There is no workaround.

  • CSCud35689

Symptoms: The router accepts a queue-limit configuration at the parent level of a policy or at the vlan class or port level.

Conditions: This issue is observed when you add a queue-limit configuration on a policy at the parent level or at the vlan class or at port level.

Workaround: There is no workaround. This configuration is not supported.

  • CSCud35732

Symptom: The router does not apply egress CFM MIP filtering.

Conditions: This issue is observed when you overwrite a MIP configuration using the ethernet CFM MIP level command.

Workaround: Instead of overwriting the MIP level configuration, remove and reapply the configuration.

  • CSCud38038

Symptom: The router records incorrect delay measurements after a reload.

Conditions: This issue is observed under the following conditions:

You configure Delay Measurement Message (DMM) on a port-channel interface.

The port-channel member links are on different interface modules (IMs).

You reload the router.

Workaround: Remove the ethernet cfm global command and reapply it after the port-channel member links to bundle. Alternatively, configure PTP clock synchronization.

  • CSCud38833

Symptom: When you configure the ACR CEM interfaces, tracebacks are displayed and the serial interface remains down.

Conditions: This issue is observed when you create a second CEM circuit under the same controller and delete the CEM circuit immediately.

Workaround: There is no workaround.

  • CSCud41297

Symptom: Multicast snooping traffic drops after removing and reconfiguring the querier EFP on 1000 groups.

Conditions: This issue is observed when you remove and reconfigure querier EFP with more than 500 multicast routs.

Workaround: There is no workaround.

  • CSCud43718

Symptom: After performing an SSO, multicast traffic is dropped for a few groups.

Conditions: This issue is observed in a scaled configuration with IGMP snooping enabled in a bridge-domain.

Workaround: There is no workaround.

  • CSCud55695

Symptom: When you apply a QoS policy with a port level class-default configuration containing a shaper value to a serial interface, the router applies the shaper value to the channel-level PIR for all serial interfaces on the IM.

Conditions: This issue is observed when you apply a QoS policy with a port level class-default configuration containing a shaper value to a serial interface.

Workaround: Add a dummy class-default level at the top of the policy and apply the shaper as a child policy.

  • CSCud55799

Symptom: Multiple priority commands are accepted per policy.

Conditions: This issue is observed when you have a policy map with priority configured in one of its classes. Add another class with policer first and with priority.

Workaround: There is no work around.

  • CSCud56364

Symptom: Convergence time for POS links for RSP SSO is about four to seven seconds.

Conditions: This issue is observed when all four POS links are created on OC-3 IM. This issue is not observed on port 0 of OC-3 IM.

Workaround: There is no work around.

  • CSCud61551

Symptom: The serial number of the RSP in slot 1 is sometimes not displayed in the show inventory command output.

Conditions: This issue is sometimes observed in the show inventory command output.

Workaround: Reload the router.

  • CSCud64129

Symptom: The router displays command options to configure control-plane policing, which is not supported.

Router(config)# control-plane
Router(config-cp)# service-policy ?
input Assign policy-map to the input of an interface
output Assign policy-map to the output of an interface
 

Conditions: This issue is observed when you attempt to configure control plane policing to restrict traffic by the CPU.

Workaround: There is no workaround. This feature is not supported.

  • CSCud71286

Symptom: Configuration synchronization failure is noticed on the interfaces.

Conditions: This issue is observed when you disable autonegotiation and configure the interface speed as 100 or 1000.

Workaround: There is no workaround. There is no impact on functionality.

  • CSCud90457

Symptoms: The serial interface on the CE end connected to the CEM interfaces on PE remain down on router reload with scaled configuration.

Conditions: This symptom is observed when you have CESoP and SAToP scaled circuits and reload the router.

Workaround: Perform an IM OIR to resolve the issue.

  • CSCud93007

Symptom: If you use the command channel-group 1 mode active on a interface, the router does not reject the command.

Conditions: This issue is observed after you configure a trunk EFP MEP using the ethernet cfm mep domain v7 mpid 1537 service v7137 command on an interface.

Workaround: There is no workaround.

  • CSCud96866

Symptom: The router displays the following symptoms:

Object download failures.

OSPF traffic flaps.

High CPU utilization.

Bundling and unbundling of port-channel member links.

Slow console updates.

Remote MEP learning failures.

Conditions: This issue is observed when you configure CFM offloaded MEPs on a port-channel interface at a high scale and use the shutdown and no shutdown command on the port-channel interface.

Workaround: There is no workaround.

  • CSCue00045

Symptom: Data traffic drops for a few groups when you use the shutdown and no shutdown commands on the interface.

Conditions: This issue is observed if join request is sent to the router within three minutes.

Workaround: There is no workaround.

  • CSCue01419

Symptom: EIGRP neighborship is lost on OC3IM and OC12 IM interfaces configured on port 0.

Conditions: This issue is observed only on interfaces that are configured on port 0 of OC3IM or OC12 IM. It is not seen on ports 1,2, or 3.

Workaround: Use the shutdown and no shutdown commands on the interfaces configured on port 0. Alternatively, remove and reconfigure EIGRP.

  • CSCue03418

Symptoms: Intermittently OSPF protocol flaps are noticed when you use the redundancy force-switchover or the switchover command. It can cause about 20 to 30 seconds of traffic loss.

Conditions: This symptom is observed while performing an SSO or when using the redundancy force-switchover command and on a HA system with 6 seconds as OSPF dead interval.

Workaround: Increase the dead interval value.

  • CSCue07040

Symptom: The router continuously displays ESDHC and MMCBLK0 errors.

Conditions: This issue is observed when the SD flash memory is being accessed.

Workaround: There is no workaround. Replace or format the bootflash.

  • CSCue14054

Symptom: When a port joins more number of multicast groups at a time, traffic drops for a few groups.

Conditions: This issue is observed when a port joins more than 900 multicast groups.

Workaround: Use the shutdown and no shutdown commands on that interface.

  • CSCue17123

Symptom: ATM and IMA pings fail from the second interface after performing an SSO.

Conditions: This issue is observed when you have multiple ATM interfaces and perform a switchover.

Workaround: There is no workaround.

  • CSCue18997

Symptom: In unicast mode, the PTP slave stream does not lock to the PTP master.

Conditions: This issue id observed after the PTP master configuration is removed and reconfigured.

Workaround: There is no workaround.

  • CSCue25146

Symptom: When the controller in active machine flaps, the standby machine is reloaded.

Conditions: This issue is observed when you configure ATM and the controller, use shutdown and no shutdown commands on the controller in the active machine.

Workaround: There is no workaround

  • CSCue27652

Symptoms: The ATM interfaces are deleted while performing an SSO.

Conditions: This issue is observed when the ATM interfaces are deleted on the standby machine after performing an IM OIR.

Workaround: There is no workaround.

  • CSCue30481

Symptom: The router does not lock to the syncE clock source after a reload. It is in Ql-failed state.

Conditions: This issue is observed when you reload the router with a saved syncE configuration.

Workaround: Delete and reconfigure the clock source.

  • CSCue35295

Symptom: Traffic drops when you remove the BFD template.

Conditions: This issue is observed when you remove the BFD template from the global configuration.

Workaround: There is no workaround.

  • CSCue36239

Symptom: Match EFP policy on a port channel stops working after one of the policies on the member links is removed.

Conditions: This issue is observed when you attach a policy to all the member links on the port channel, remove it from one of the member links from which traffic flows.

Workaround: Remove policies from all the member links and reattach the policies.

  • CSCue39978

Symptom: Traffic stops in ATM PVP after performing an IM OIR followed by SSO.

Conditions: This issue is observed after performing an IM OIR followed by SSO when ATM PVP is configured.

Workaround: Reload the router.

  • CSCue43250

Symptom: IMA configuration is not parsed correctly after a router reload when the A903-IM40S module is inserted in Bay4 or Bay5 of the Cisco ASR 903 router.

Conditions: This issue is observed when the IMA and ATM interfaces are adjacent. It happens only if the IM is inserted on Bay 4 or above.

Workaround: Insert the IM in bay 0 or bay 3 if you want the IMA and ATM parsing to work. Alternatively, reconfigure the ATM and IMA interfaces.

  • CSCue45274

Symptom: Traffic drop is seen on a port for more than 8 minutes when a BDI, which is not part of this new port is shut down.

Conditions: This issue is observed when a BDI is shut down and another port which is not a part of the shut down BDI port join the multicast group.

Workaround: There is no workaround.

  • CSCue45306

Symptom: The CEM circuits that are configured over TDM IM go down after performing an SSO.

Conditions: This issue is observed when you perform an SSO, the CEM circuits that are configured over TDM IM go down.

Workaround: Reload the router.

  • CSCue47834

Symptom: IOMd crashes and IM goes out of service during SSO.

Conditions: This issue is observed when you have ATM and IMA configured and perform an SSO. IOMd crashes and the IM goes out of service.

Workaround: There is no workaround.

  • CSCue54997

Symptom: The system accepts two input clock sources from the same OC3 IM although the system supports only one input clock source per OC3 IM. This results in clock failures.

Conditions: This issue is observed when two input clock sources are accepted from the same OC3 IM although the framer on the IM can support only one clock source.

Workaround: Do not configure the second input clock source from the same OC3 IM. Alternatively, remove both OC3 clock sources and configure the desired OC3 controller.

  • CSCue57671

Symptom: Router crashes while running the REP configuration.

Conditions: This issue is observed while removing the REP configuration from the interface.

Workaround: There is no workaround.

  • CSCue66019

Symptom: The router displays MLPPP interface errors.

Conditions: This issue is observed when there is more than 90% line rate traffic with mix MTU patterns.

Workaround: There is no workaround.

  • CSCue67835

Symptom: OSPF flaps when you set the dead interval timer as 6 seconds and hello interval as 2 seconds.

Conditions: This issue is observed when you perform an SSO.

Workaround: Use the default OSPF hello timers.

  • CSCue72481

Symptom: The same interface accepts an IP address and a MEP.

Conditions: This issue is observed when you configure an IP address and a MEP to the same interface.

Workaround: There is no workaround.

  • CSCue83621

Symptom: Policy map stops working after you dynamically remove class default class.

Conditions: This issue is observed when the policy map is attached to the target and the class default of the top level is deleted dynamically, the policy stops working.

Workaround: Detach and reattach the policy map on the target.

  • CSCue89503

Symptom: The power supply status reports critical after you remove and insert the power supply.

Conditions: This issue is observed after performing multiple OIRs.

Workaround: There is no workaround.

  • CSCuf01120

Symptom: IOMD crash is seen while performing an SSO when card type is not configured for T1E1 IM.

Conditions: This issue is observed when the TDM card type is not configured before performing an SSO.

Workaround: Configure the card type for T1E1 IM before preforming an SSO.

  • CSCuf20151

Symptom: The following error message is displayed when you apply a policy map:

QoS: Configuration failed. Can NOT match ACL in an output policy-map
 

Conditions: This issue is observed when you apply a policy map, reload, or reconfigure of the policy map.

Workaround: There is no workaround.

  • CSCuf43275

Symptom: The router does not detect traffic through GLC-FE-100EX and GLC-FE-100ZX transceivers.

Conditions: The router does not support traffic through GLC-FE-100EX and GLC-FE-100ZX transceivers.

Workaround: There is no workaround.

  • CSCuf43992

Symptom: The router crashes if you configure local span.

Conditions: This issue is observed when you configure local span on the router.

Workaround: There is no workaround.

  • CSCuf44077

Symptom: The show interface command output shows incorrect speed values after performing an SSO.

Conditions: This issue is observed when you use a 100M SFP.

Workaround: There is no impact on functionality. Reset the hardware module to resolve this issue.

  • CSCuf57632

Symptoms: When you reload the router, the device may not be able to load the startup configuration from NVRAM.

Conditions: This issue is sometimes observed when you reload the router.

Workaround: Reload the router again.

  • CSCuf65012

Symptom: When you perform an IM OIR on slot 4, the router may display syslog messages from the GigabitEthernet 0/5/0 port.

Conditions: This issue is observed when you perform an IM OIR on slot 4 and Slot 5.

Workaround: There is no workaround.

  • CSCuf79364

Symptom: When you try configure speed on the interface on the standby machine, it does not accept the command.

Conditions: This issue is observed after you insert a new IM and GE-T connector when router is running.

Workaround: Reload the router before configuring the speed.

  • CSCuf79504

Symptom: When you use the shutdown and no shutdown commands multiple times on the controller, ATM VC creation on the standby RSP fails.

Conditions: This issue is observed when you use the shutdown and no shutdown commands multiple times on the controller on active RSP.

Workaround: There is no workaround.

  • CSCuf81085

Symptom: After you use the shutdown and no shutdown commands on the controller of PE, IMA VCs go down.

Conditions: This issue is observed after using the shutdown and no shutdown commands on the OC3 controller on PE routers.

Workaround: Use the shutdown and no shutdown commands on the controller.

  • CSCuf85460

Symptom: When you delete the POS interface and try to create an ATM interface, the following error message is displayed:

%OC3.STS1 0/2/0.1:Port type not supported
Insufficient resources to create channel group
 

Conditions: This issue is observed when you reload the OC3-IM having POS interface and try to create an ATM interface.

Workaround: Create the POS interface, delete it, and the create an ATM interface.

  • CSCuf89665

Symptom: Flow control identifiers of active and protect interfaces are not created on to the standby. Due to which, the interface goes down when you perform an SSO.

Conditions: This issue is observed when you set up ACR on the standby machine.

Workaround: There is no workaround.

  • CSCuf89844

Symptom: The router crashes when you delete a BDI interface running BFD.

Conditions: This issue is observed when you assign a static MAC address on a neighbor router or on one of the BDI interfaces on the Cisco ASR 903 router, and delete the BDI interface running BFD on the Cisco ASR 903 router.

Workaround: There is no workaround. Do not change the MAC address on the BDI interface.

  • CSCug16135

Symptom: Critical alarm LED does not illuminate. The show facility-alarm status command shows a critical alarm.

Condition: This issue occurs when both active and standby RSP are in UP state.

Workaround: Use the show facility-alarm status command to view the alarm status.

  • CSCug17844

Symptom: Traffic does not match the configured class map of the applied policy.

Conditions: This issue is observed at egress, if a policy map which contains 8 user-defined class-maps is applied. As it exceeds the allowed number of class maps, traffic hits the class default.

Workaround: Remove the 8th user-defined class map and reapply the policy.

  • CSCug18630

Symptom: When you perform an OIR on the standby and active RSPs, CMAND crashes.

Conditions: This issue is observed after performing multiple standby OIRs and bringing the standby machine up.

Workaround: There is no workaround.

  • CSCug31212

Symptom: When you apply a policy map, the console shows an error message.

Conditions: This issue is observed when you apply a policy map with numbered ACLs.

Workaround: There is no workaround.

  • CSCug31645

Symptom: If you change the template on the router and change it again within two minutes, the standby RSP is unable to synchronize with the new template and the router reloads twice.

Conditions: This issue is observed when you change the template, and change it again within two minutes before reloading the router.

Workaround: Do not change the template and change it again within two minutes.

  • CSCug44762

Symptom: The POS interface stays down after using the shutdown and no shutdown commands.

Conditions: This is issue is observed when you use the shutdown and no shutdown commands on the POS interface.

Workaround: Use the shutdown and no shutdown commands on the controller.

  • CSCug48534

Symptom: Multicast traffic is forwarded on untagged EFPs when snooping is enabled.

Conditions: This issue is observed when untagged EFPs are shutdown at least once after it comes up.

Workaround: Reload the router or toggle IGMP snooping.

  • CSCug55586

Symptom: If you dynamically remove the egress markings, ingress marking does not work.

Conditions: This issue is observed if a marking is present at the logical level in the egress direction, DM does not work.

Workaround: Use the egress set at leaf or PHB level.

  • CSCug58606

Symptom: When you use the no shutdown command, the LED of 1G and 10G IM turns off.

Conditions: This issue is observed when you use the no shutdown command on 1G and 10G interfaces.

Workaround: There is no workaround.

  • CSCug61357

Symptom: ISIS adjacency and BFD stay down after using the shutdown and no shutdown commands.

Conditions: This issue is observed in R-LFA configurations.

Workaround: Use the shutdown and no shutdown commands again.

  • CSCug83426

Symptom: Interface reports loss of frame alarm and goes down.

Conditions: This issue is observed when you use the shutdown and no shutdown commands on the controllers of PE and CE.

Workaround: Perform an OIR on CE side.

  • CSCug83846

Symptom: The MTU value does not take effect on an interface.

Conditions: This issue is observed when you try to configure more than eight unique MTU values on the router.

Workaround: There is no workaround.

  • CSCug94540

Symptom: The total drop counters on an interface is not displayed when HQoS policy map is applied.

Conditions: This issue is observed when you apply a two-level policy on a port.

Workaround: Use the show policy-map interface gigabitethernet 0/0/0 command or show hqf interface gigabitethernet 0/0/0 command.

  • CSCug96958

Symptom: IMA interfaces stay up even when you use the shutdown command to shut down the controller.

Conditions: This issue is observed when you use the shutdown command on the OC3 controller.

Workaround: Use the no shutdown command bring up the controller and interfaces.

  • CSCug99750

Symptom: The Cisco ASR 903 router crashes when it accesses unpopulated data structures.

Conditions: This issue is observed when you perform an IM OIR and use the shutdown and no shutdown commands.

Workaround: There is no workaround.

  • CSCuh00009

Symptom: RSP crashes due to keepalive failure.

Conditions: This issue is observed when the router is being polled from different SNMP servers at different intervals.

Workaround: Increase the SNMP polling interval.

  • CSCuh06740

Symptom: Router gets reloaded after performing a soft OIR.

Conditions: This issue is observed after you perform a soft OIR or subsequent SSOs.

Workaround: There is no workaround.

  • CSCuh16011

Symptom: FMAN-FP crashes when you perform ab IM OIR.

Conditions: This issue is observed when you perform multiple IM OIRs with around 65 BFD sessions.

Workaround: Reload the router.

  • CSCuh18503

Symptom: BFD IPv6 sessions may not come up between Cisco ASR 9000 and Cisco ASR 903 routers.

Conditions: This issue is observed when the packets sent from Cisco ASR 903 router have invalid UDP checksums.

Workaround: There is no workaround.

  • CSCuh21696

Symptom: When you disable IGMP snooping, the IGMP control packets are not flooded on all ports.

Conditions: This issue is observed with TEFP over 10Gig, normal EFP, EFP over PC, and TEFP with IGMPSN.

Workaround: There is no workaround.

  • CSCuh27117

Symptom: Traffic loss of about six to eight seconds is observed when you perform an SSO.

Conditions: This issue is observed when you perform the switchover before IM OIR or the interface flaps.

Workaround: There is no workaround.

  • CSCuh48988

Symptom: When you create a policy map the following error message appears:

"Max class-maps in an Egress policy-map (port-channel_egress) cannot exceed 8"
 

Conditions: This issue is observed when a policy map with more than 8 class maps is configured.

Workaround: There is no workaround.

  • CSCuh77762

Symptom: On Cisco ASR 903 routers, the TenGigabitEthernet port operates at one gigabit speeds in WAN-PHY mode. This leads to a huge amount of output drop.

Conditions: This issue is observed if a QoS policy is configured on the TenGigabitEthernet interface.

Workaround: There is no workaround.

  • CSCuh79730

Symptom: The transmitting frequency is incorrectly displayed in the output of the show hw-module subslot 0 transceiver idprom command.

Conditions: This issue is observed if you use DWDM-XFP-C modules.

Workaround: There is no workaround.

  • CSCuh86102

Symptom: The interface stops forwarding traffic

Conditions: This issue is observed when the TenGigabitEthernet interface is in WAN-PHY mode and R0 is active.

Workaround: Use R1.