Restrictions and Limitations


Note

The error message "PLATFORM-1-NOSPACE: SD bootflash : no space alarm assert" may occur in the following scenarios:

  • Any sector of SD Card gets corrupted

  • Improper shut down of router

  • power outage.

This issue is observed on platforms which use EXT2 file systems.

We recommend performing a reload of the router. As a result, above alarm will not be seen during the next reload due to FSCK(file systems check) execution.

However, If the error persists after a router reload, we recommend to format the bootflash or FSCK manually from IOS.

  • Embedded Packet Capture (EPC) is not supported on ASR 900 routers.

  • From the Cisco IOS XE 16.6.1 releases, In-Service Software Upgrade (ISSU) is not supported on the router to the latest releases. For more information on the compatible release versions, see ISSU Support Matrix.

  • ISSU is not supported between a Cisco IOS XE 3S release and the Cisco IOS XE Bengaluru 17.6.x release.

  • The port restriction on 1-port OC-192 or 8-port low rate CEM interface module is on port pair groups. If you have OC48 configured on a port, the possible port pair groups are 0–1, 2–3, 4–5, 6–7. If one of the ports within this port group is configured with OC48 rate, the other port cannot be used.

  • RS422 pinout works only on ports 0–7.

  • The ip cef accounting command is not supported on the router.

  • Configuration sync does not happen on the Standby RSP when the active RSP has Cisco Software Licensing configured, and the standby RSP has Smart Licensing configured on the router. If the active RSP has Smart Licensing configured, the state of the standby RSP is undetermined. The state could be pending or authorized as the sync between the RSP modules is not performed.

  • Evaluation mode feature licenses may not be available to use after disabling, and enabling the smart licensing on the RSP2 module. A reload of the router is required.

  • Ingress counters are not incremented for packets of the below format on the RSP3 module for the 10-Gigabit Ethernet interfaces, 100-Gigabit Ethernet interfaces, and 40-Gigabit Ethernet interfaces:

    Packet Format

    MAC header---->VLAN header---->Length/Type

    When these packets are received on the RSP3 module, the packets are not dropped, but the counters are not incremented.

  • T1 SAToP, T3 SAToP, and CT3 are supported on an UPSR ring only with local connect mode. Cross-connect configuration of T1, T3, and CT3 circuits to UPSR are not supported.

  • PTP is not supported when 8-port 10-Gigabit Ethernet interface module is in oversubscribed mode.

  • Port channel 61–64 is not supported in the 16.11.1a release. The range of configurable port channel interfaces has been limited to 60.

  • Effective with Cisco IOS XE Everest 16.6.1, the VPLS over Port-channel (PoCH) scale is reduced from 48 to 24 for Cisco ASR 903 RSP3 module.


    Note

    The PoCH scale for Cisco ASR 907 routers is 48.

  • The frame drops may occur for packets with packet size of less than 100 bytes, when there is a line rate of traffic over all 1G or 10G interfaces available in the system. This restriction is applicable only on RSP2 module, and is not applicable for RSP3 module.

  • One Ternary Content-Addressable Memory (TCAM) entry is utilized for Segment Routing Performance Measurement. This is required for the hardware timestamping to function.

  • While performing an auto upgrade of ROMMON, only primary partition is upgraded. Use the upgrade rom-mon filename command to upgrade the secondary partition of the ROMMON during the auto upgrade. However, the router can be reloaded during the next planned reload to complete the secondary ROMMON upgrade. This is applicable to ASR 903 and ASR 907 routers.

  • In the Cisco IOS XE 17.1.1 release, the EVPN EVI type is VLAN-based by default, and while configuring for the EVPN EVI type, it is recommended to configure the EVPN EVI type as VLAN-based, VLAN bundle and VLAN aware model.

  • For Cisco IOS XE Gibraltar Release 16.9.5, Cisco IOS XE Gibraltar Release 16.12.3, and Cisco IOS XE Amsterdam 17.1.x, a minimum disk space of 2 MB is required in the boot flash memory file system for a successful ROMMON auto upgrade process. For a disk space lesser than 2 MB, ROMMON auto upgrade fails and the router reboots. This is applicable to Cisco ASR 903 and Cisco ASR 907 routers.

  • In the Cisco IOS XE 16.12.1, 17.1.1, and 17.2.1 releases, IPsec is not supported on the Cisco RSP3 module.

  • CEM circuit provisioning issues may occur during downgrade from Cisco IOS XE Amsterdam 17.3.1 to any lower versions or during upgrade to Cisco IOS XE Amsterdam 17.3.1 from any lower versions, if the CEM scale values are greater than 10500 APS/UPSR in protected CEM circuits. So, ensure that the CEM scale values are not greater than 10500, during ISSU to or from 17.3.1.

  • Some router models are not fully compliant with all IETF guidelines as exemplified by running the pyang tool with the lint flag. The errors and warnings that are exhibited by running the pyang tool with the lint flag are currently noncritical as they do not impact the semantic of the models or prevent the models from being used as part of the toolchains. A script has been provided, "check-models.sh", that runs pyang with lint validation enabled, but ignoring certain errors. This allows the developer to determine what issues may be present.

    As part of model validation for the Cisco IOS XE Amsterdam 17.3.1 release, "LEAFREF_IDENTIFIER_NOT_FOUND" and "STRICT_XPATH_FUNCTIONS" error types are ignored.

  • Test Access Port (TAP) is not supported when the iMSG VLAN handoff feature is enabled on the same node.

  • Data Communication Channel (DCC) is not supported in the A900-IMA1Z8S-CXMS interface module for the Cisco IOS XE Cupertino 17.8.1 release.

  • SF and SD alarms are not supported on T1 and T3 ports for the following interface modules:

    • A900-IMA3G-IMSG

    • A900-IMA48D-C

    • A900-IMA48T-C

  • In RSP2 and RSP3 modules, during In-Service Software Upgrade (ISSU), interface modules undergo FPGA upgrade.

    The following table details the IM Cisco IOS XE versions during ISSU with respect to FPGA upgrade and the impact of traffic flow for these IMs:

Table 1. Impact on IM during ISSU and FPGA Upgrade

IM

IM Version During ISSU

Pre-ISSU FPGA Upgrade

Post-ISSU Impact on IM

FPGA Version post ISSU

Phase 1

Cisco IOS XE 17.3.x or earlier version to Cisco IOS XE 17.4.x

FPGA upgrade completes and IM starts after the reload process.

FPGA version (phase -1) - 0.47

Traffic is impacted during upgrade.

0.75

Phases 1 and 2

Version earlier to Cisco IOS XE 17.8.x

FPGA upgrade completes and IM starts after the reload process.

  • FPGA version (Phase 1)— 0.47

  • FPGA version (Phase 2)

    • A900-IMA8Z—69.22

    • Combo IM: 69.24

Traffic is impacted during upgrade.

  • FPGA version (Phase 1)—0.75

  • FPGA version (Phase 2)

    • A900-IMA8Z—69.24

    • Combo IM: 69.32

Phase 1

Cisco IOS XE 17.4.1 or later versions to Cisco IOS XE 17.8.1

IM FPGA already upgraded with the latest version and reload is not required.

Traffic is not impacted.

0.75

For more information on the FPGA versions, see Supported FPGA, HoFPGA, and ROMMON Versions.

Refer the following table for supported IMs:

Table 2. ASR 900 Supported Ethernet Interface Module

Phase 1 IM

Phase 2 IM

Phase 3 IM

A900-IMA8S

A900-IMA8S1Z

A900-IMA8Z

A900 -IMA8T

A900-IMA8T1Z

A900-IMA2F

A900-IMA1X

A900-IMA2Z

A900-IMA2C