The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Table of Contents
Release Notes for for Cisco IOS Release
Determining the Software Version
New Hardware Features in Release
N ew Software Features in Release
M odified Software Features in Release
Release Notes for Cisco ASR 901 Series Aggregation Services Router for Cisco IOS Release 15.3(3)S2
This release notes is for the Cisco ASR 901 Series Aggregation Services Router for Cisco IOS Release 15.3(3)S2 and contains the following sections:
The Cisco ASR 901 Series Aggregation Services Router is a cell-site access platform specifically designed to aggregate and transport mixed-generation radio access network (RAN) traffic. The router is used at the cell site edge as a part of a 2G, 3G, or 4G RAN.
The Cisco ASR 901 router helps enable a variety of RAN solutions by extending IP connectivity to devices using Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Node Bs using High Speed Packet Access (HSPA) or Long Term Evolution (LTE), base transceiver stations (BTSs) using Enhanced Data Rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), CDMA-2000, EVDO, or WiMAX, and other cell-site equipment.
It transparently and efficiently transports cell-site voice, data, and signaling traffic over IP using traditional T1 and E1 circuits, as well as alternative backhaul networks such as Carrier Ethernet and DSL, Ethernet in the First Mile (EFM), and WiMAX. It also supports standards-based Internet Engineering Task Force (IETF) Internet protocols over the RAN transport network, including those standardized at the Third-Generation Partnership Project (3GPP) for IP RAN transport. Custom designed for the cell site, the Cisco ASR 901 router features a small form factor, extended operating temperature, and cell-site DC input voltages.
Table 1 lists the Cisco ASR 901 router model versions.
Note Some of the Cisco ASR 901 models have port based licensing. For more details, see the Licensing chapter in Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide.
Table 2 lists the supported system configurations for the Cisco ASR 901 router:
Table 2 lists the memory available for Cisco ASR 901 router.
Cisco ASR 901 Series Aggregation Services Router TDM version
Cisco ASR 901 Series Aggregation Services Router, Ethernet version
Determining the Software Version
To determine the image and version of Cisco IOS software running on your Cisco ASR 901 router, log in to the router and enter the show version command in the EXEC mode:
New and Changed Information
- New Hardware Features in Release 15.3(3)S2
- New Software Features in Release 15.3(3)S2
- Modified Software Features in Release 15.3(3)S2
New Hardware Features in Release 15.3(3)S2
There are no new hardware features in Cisco IOS Release 15.3(3)S2.
New Software Features in Release 15.3(3)S2
There are no new software features in Cisco IOS Release 15.3(3)S2.
Modified Software Features in Release 15.3(3)S2
There are no modified features in Cisco IOS Release 15.3(3)S2.
Table 3 and Table 4 shows the SFP modules supported on the Cisco ASR 901 routers:
Table 3 SFPs Supported on the Cisco ASR 901 1G and 10G Routers for 1G Mode
4.These SFPs (GLC-BX-U and GLC-BX-D) should be connected back to back to bring the interface link up.
Table 4 SFPs Supported on the Cisco ASR 901 10G Router for 10G Mode
Note For information on how to configure SFPs, see the Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide.
The Cisco ASR 901 router supports the following MIBs:
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious of these three severity levels. Only select severity 3 caveats are listed.
This section contains the following topics:
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.
This section provides information about the open caveats for the Cisco ASR 901 router running Cisco IOS Release 15.3(3)S2.
Service policy classification based on inner Virtual LAN p-bits is not working.
The show ethernet service instance statistics command is not displaying any statistics.
A command restriction is required for Dual Rate Three Color (2R3C) on parent class in Hierarchical Quality of Service (HQoS).
Some ports are not getting bundled with the port channel because of attribute mismatch, such as flow-control.
The Multiprotocol Label Switching (MPLS) traffic fails when port channel encapsulation is not equal to the bridge domain on the core.
High CPU utilization is observed while performing save or copy operation.
Ingress VLAN translation failure occurs when entries exceed 3000.
The circuit emulation (CEM) interface displays wrong configuration in the show running-configuration command output, when pw-class is configured.
Traceback occurs after executing rep preempt segment segid command.
Weighted Random Early Detection (WRED) counters are not working for discard class 0.
The interface drops all ingress packets when you reload the router with write, erase, and copy the saved configuration to the running configuration.
Maximum bandwidth guarantee for Multilink Point-to-Point Protocol (MLPPP) interface is not working for 64-byte size frames in Low Latency Queuing (LLQ).
The servo is accepting more than 64PPS Sync in static unicast.
SyncE is not supported for the Copper SFPs: GLC-T and SFP-GE-T
High CPU utilization and traceback is observed while doing copy and paste of 16 E1 controllers unconfigurations.
Input errors are increasing when serial interface flaps. This issue is observed on a serial interface that is part of a multilink interface, when keepalive is disabled.
Traffic fails and continuous traceback is observed, when xconnect is configured on an untagged EVC.
The Two-Way Active Measurement Protocol (TWAMP) session-reflector packet truncation fails.
The write operation triggers the flaps for Hot Standby Router Protocol (HSRP). We recommend the use of minimum 1 sec (or above) hello timer for HSRP and Virtual Redundancy Router Protocol (VRRP). With this configuration, we support a maximum of 50 sessions.
IPv6 traffic is not getting dropped with link-local as source address.
The Layer 2 ATM/IMA interface and its permanent virtual circuits (PVCs) are not coming up when operations, administration and maintenance (OAM) is configured.
The OSPFv3 keeps old router-id even after changing the loopback address.
Manual tunnel having MPLS configuration with dynamic option in the following sequence does not set up targeted ldp session resulting in tunnel staying down. shut/no shut of the tunnel brings back the targeted Label Distribution Protocol (LDP) session up.
The issue is not observed when tunnel mode is configured ahead of tunnel destination,
The commands related to MPLS and MPLS-TE/FRR are applicable only to SVI interfaces though they can be enabled globally.
Thus configuring the MPLS commands on the GigabitEthernet interface or port-channel is not supported.
The OSPFv3 bidirectional forwarding detection (BFD) flaps after an interface is shut in a port-channel bundle.
The following error message is displayed for /128 prefix: “Reached Maximum Number of IPv6 Hosts”.
Load balancing is not working with different streams having symmetrical addresses.
The verify command is not supported for the USB flash in the Cisco ASR 901 10G router.
The IPv6 BFD packets should be mapped to Queue 6 on egress interface.
MAC address table (MAC learning) failures can be seen with more than 31000 MAC Addresses in certain conditions. So it is safe to assume the platform supports 31000 MAC addresses.
The “pura_cef_ipv6_route_create_update:Reached Maximum Number of Prefixes supported by platform.Additional Prefixes will not be programmed” message is displayed when the primary path is shut/unshut in a redundant convergent setup.
Alarm Indication Signal (AIS) is visible momentarily at T1 controller of CE1 while reverting back to primary.
Connectivity Fault Management (CFM) is not supported with 100 ms interval.
The router fails to recognize USB when its removed immediately after insertion.
The UBR transmits at a lower rate when all five class of service (CoS) Private Virtual Circuits (PVCs) are configured.
IPv6 traffic drop occurs globally when IPv4 VRF is configured on the same SVI with ip vrf definition.
The untagged Ethernet Virtual Circuit (EVC) port is not supported for spanning tree.
Traffic is receiving two VLAN tags, instead of three for QinQ with pop 2.
In Zero Touch Provisioning, the Cisco ASR 901 series router is not able to connect to the CE server using option-43 template, when source interface is passed as a parameter.
In traffic generator, the receiver (Rx) counter is incrementing even after the EVC mismatch.
Border Gateway Protocol (BGP) flap is observed between PEs when traffic from CE side is oversubscribed towards PE.
High convergence time is observed when “shut” operation is performed on fast re-route (FRR) configured with port channels. This issue can be resolved with BFD.
The Ethernet Over MPLS (EoMPLS) pseudowire redundancy fails when backup pseudowire is active in TE-FRR backup path.
In Zero Touch Provisioning, the Cisco ASR 901 10G router is using wrong Unique Device Identifier (UDI) event-id to make connection to the CE.
CPU hog is observed when primary path is “shut” in an LFA FRR set up with 1000 prefixes.
The show version command is not giving the image name when the boot system variable is set as: boot system flash image-name.
Error occurs when any label entry is crossing the 3500 range.
In Zero Touch Provisioning, the VLAN discovery is not supported for encapsulation dot1ad.
The mac-address flap control is putting all ports into “err-disabled” state, in some cases.
The show rom-monitor command is not showing upgraded ROMMON version in IOS mode.
The show inventory command is displaying the PID of SFP-SX-MM as GLC-SX-MM.
The router displays “soc_counter_sync: counter thread not responding” error, under heavy CPU usage.
The incremental-SPF configuration is causing micro loops during convergence, in IGP IS-IS.
The VRF routes are leaked from the adjacent VRF with a particular IP:nn pattern.
CPU hog and traceback is observed when scale configuration is pushed from CE server to the router.
Traffic outage and pstorm errors are observed when port channel is configured and unconfigured multiple times.
Peering is not working for untagged EVC when service instance is configured with default encapsulation.
The port channel interface flaps when lacp max-bundle is configured and unconfigured.
High reconvergence is observed for global traffic in Remote Loop Free Alternate (RLFA).
Configuration of backup peer on primary xconnect, after bringing up remote peer backup results in flap.
Auto-select is not working on the Gigabit Ethernet (0/4) port.
For combo ports, shutdown or no shutdown on the interface is mandatory while changing the media type from RJ45 to auto-select and auto-select to RJ45 respectively.
Strom control filter for the port channel does not show the discarded counters.
Console hangs when verify command is executed on two telnet sessions.
ASR 901 strom control filter does not support current counters value in show storm output.
Cisco ASR 901 series router crashes while defaulting the interface.
On Layer 3, multicast traffic are punted to CPU even when storm control drops all the packets.
100M SFP support is not available for auto-select medium feature.
After reload, incorrect error message is displayed for unsupported SFPs.
REP flaps with low LSL timers with the scale of MAC address, scale of bridge-domain, repeated/multiple REP topology changes, or CPU intensive activities.
IPV4 ACL does not block OSPF multicast packets that are punted to CPU.
Layer 3 traffic drops after preempting the REP sessions with VLB configuration.
This section provides information about the resolved caveats for the Cisco ASR 901 router running Cisco IOS Release 15.3(3)S2.
The CPU process for IP SLA continues to run even after stopping the traffic generator.
Error disable recovery state does not persist for the second time on fiber port even after the error recovery interval.
When more than four ports are connected to a peer where the ports are administratively up, the interface which detects a link up event takes the license first. Hence, the behavior of ports is non predictable. The first port which detects the link up will take the license and the other port may not get a valid license.
When the router boots up, the Gigabit Ethernet port flaps multiple times.
Double drop counter rate is observed for hierarchical QoS (HQoS) egress policy-map.
Stale drop entries are observed on application of policy-map on port without any traffic.
Strom control on port channel does not display blocking or forwarding state for both the member links.
IP connectivity fails on combo ports with copper link, after reload.
Re-routing in the core affects Connectivity Fault Management (CFM) sessions on the peer device.
IPv4/IPv6 ping is not 100 percent successful on enabling layer 2 cache.
Router crashes when CEM PW head-end loses connectivity to both remote PEs on core isolation and recovery.
GLC-LH-SMD port goes down when CWDM or avago type fibers are inserted adjacent to it.
FRR link and AC port flaps due to incorrect egress object in pseudowire redundancy DVP.
Output drops are found in the alternate port (the port in blocked state) with REP configuration.
On reload, GigabitEthernet 0/11 port on Cisco ASR 901 router flaps multiple times when GigabitEthernet 0/11 port with untagged service instance configuration is connected to GigabitEthernet port on a 7600 device.
Autoinstall gets into a loop when a tagged layer 2 packet is received before the display of setup dialogue.
IMA pseudowire traffic may fail with many Winpath WP_INVALID_IW_EMC_FLOW_EXISTS_IN_HASH errors and tracebacks.
ToP interface is not selected as network-clock when PTP reaches Normal/phase_aligned state
License boot level Advanced message is displayed thrice on using the show running-configuration command.
FP entries are exhausted after using set mpls exp imposition command in policy-map.
SyncE fails in Cisco ASR 901 router when 10G port operates as 1G mode.
Configuring set discard-class 2 command under ingress policy of an ingress interface breaks Layer 3 VPN connection.
Router crashes while unconfiguring and configuring port level MEPs.
QoS Class Drop counters rollback to zero when polling from SNMP server.
MTU behavior differs from other IOS platforms.
When using Cisco ASR901 router with TenGig interface and bridge-domain, although the L3 MTU of the SVI is set to 1500 bytes, the effective non-fragmented MTU size is 1486 bytes (the L2 MTU). This differs from other platforms in which the L3 MTU is the actual L3 MTU configured on the interface.
Memory leak occurs after applying and removing a policy-map on the output of the interface.
Broken Counters (counters that are not operational) are displayed in the output of show interface Vlan command.
When enabling VLAN counters in one VLAN, other VLAN counters are updated without enabling the vlan-counter command.
The following sections describe troubleshooting commands you can use with the Cisco ASR 901 Series Aggregation Services Router.
Collecting Data for Router Issues
To collect data for reporting router issues, issue the following command:
Collecting Data for ROMMON Issues
To collect data for ROMMON issues, issue the following command while in the EXEC mode:
Note If you contact Cisco support for assistance, we recommend that you provide any crashinfo files stored in flash memory. For more information about crashinfo files, see http://www.cisco.com/en/US/products/hw/routers/ps167/products_tech_note09186a00800a6743.shtml.
Documents related to the Cisco ASR 901 Series Aggregation Services Router include the following:
- Cisco ASR 901 Series Aggregation Services Router Hardware Installation Guide
- Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
- Regulatory Compliance and Safety Information for Cisco ASR 901 Series Aggregation Services Routers
- Cisco ASR 901 Series Aggregation Services Router Series MIB Specifications Guide
To access the related documentation on Cisco.com, go to:
Services and Support
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Release Notes for Cisco ASR 901 Aggregation Series Router for Cisco IOS Release 15.3(3)S2