Release Notes for the Cisco ASR 903 Router - IOS XE Release 3.11 Restrictions and Caveats [Cisco ASR 900 Series Aggregation Services Routers]

Table Of Contents

Restrictions and Caveats in Cisco IOS XE 3.11 Releases

Caveats in Cisco IOS XE 3.11S Releases

Open Caveats—Cisco IOS XE Release 3.11S

Resolved Caveats—Cisco IOS XE Release 3.11S

Restrictions and Caveats in Cisco IOS XE 3.11 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.

Note If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.)

The Dictionary of Internetworking Terms and Acronyms contains definitions of acronyms that are not defined in this document:

http://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.11S

•Resolved Caveats—Cisco IOS XE Release 3.11S

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

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 gett 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 int erface 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: Thi issue occurs afer 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 occura 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 addresss.

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

	Release Notes for the Cisco ASR 903 Router
	IOS XE Release 3.11 Restrictions and Caveats
Release Notes for the Cisco ASR 903 Router Release Notes for the Cisco ASR 903 Router New Features in Cisco IOS XE 3.6S New Features in Cisco IOS XE 3.7S New Features in Cisco IOS XE 3.8S New Features in Cisco IOS XE 3.9 New Features in Cisco IOS XE 3.10S New Features in Cisco IOS XE 3.11S IOS XE Release 3.6 Restrictions and Caveats IOS XE Release 3.7 Restrictions and Caveats IOS XE Release 3.8 Restrictions and Caveats IOS XE Release 3.9 Restrictions and Caveats IOS XE Release 3.10 Restrictions and Caveats IOS XE Release 3.11 Restrictions and Caveats	Download this chapter IOS XE Release 3.11 Restrictions and Caveats Download the complete book Release Notes for the Cisco ASR 903 Router (PDF - 3 MB) Feedback Table Of Contents Restrictions and Caveats in Cisco IOS XE 3.11 Releases Caveats in Cisco IOS XE 3.11S Releases Open Caveats—Cisco IOS XE Release 3.11S Resolved Caveats—Cisco IOS XE Release 3.11S Restrictions and Caveats in Cisco IOS XE 3.11 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. Note If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.) The Dictionary of Internetworking Terms and Acronyms contains definitions of acronyms that are not defined in this document: http://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.11S •Resolved Caveats—Cisco IOS XE Release 3.11S 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 xconnects. 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 gett 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 int erface 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: Thi issue occurs afer 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 occura 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 addresss. 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 whiel 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.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks