What's New in Hardware for Cisco IOS XE Bengaluru 17.4.2
There are no new hardware features in this release.
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.
This chapter describes the new hardware and software features supported on the Cisco ASR 920 Series routers in Cisco IOS XE Bengaluru 17.4.x.
For information on features supported for each release, see Feature Compatibility Matrix.
There are no new hardware features in this release.
There are no new software features in this release.
There are no new hardware features in this release.
Feature | Description |
---|---|
1 port OC-48/STM-16 or 4 port OC-12/OC-3 / STM-1/STM-4 + 12 port T1/E1 + 4 port T3/E3 CEM Interface Module |
|
|
|
Carrier Ethernet |
|
This feature allows you to configure the platform bdi enable-state up global command. |
|
IP Multicast: PIM |
|
Display of aggregated egress multicast stats for BDI interfaces on Head node, which is part of the MLDP core is supported. |
|
IP Routing: BFD |
|
Scale numbers for BFD and hardware offload are enhanced for the Cisco ASR 900 RSP2 module. |
|
IP SLAs |
|
This feature allows you to configure user-defined and Enterprise traffic (EMIX) packet sizes.
|
|
SAT based support for configurable EMIX traffic pattern in FPGA |
The support for EMIX packet size is enhanced. For EMIX traffic, packet sizes of 64, 128, 256, 512, 1024, 1280, 1518, Maximum Transmission Unit (MTU) and user-defined patterns are supported. These packet sizes are forwarded in ratio of 1:1:1:1:1. |
This feature enables SAT based support for configurable EMIX traffic pattern in FPGA-based SAT. |
|
Layer 2 |
|
The Ethernet data plane loopback feature is enhanced to avoid control packets getting dropped. The enhancement supports internal shaper configuration, when terminal ELB session is activated or deactivated to rate the limit the ELB session traffic. The enhancement is applicable only on internal loopback. |
|
MPLS Basic |
|
Re-optimization with Tunnel Bandwidth Modification on Flex-LSP Protect Path |
This feature supports Make Before Break (MBB) functionality and thus ensures there is no traffic loss when a MPLS Flex LSP tunnel runs on protect LSP (if working LSP goes down) and the tunnel bandwidth is modified. When the working LSP comes up, use the following command to manually switch from the working to protect LSP: mpls traffic-eng switch tunnel tunnel-ID |
Segment Routing |
|
This feature allows you to configure an SR policy as the preferred path for a VPWS or VPLS pseudowire. VPWS or VPLS pseudowires between same PEs can be routed over different SR policies based on the requirements. Prior to this release, you could only steer the traffic using the SR policy for routing IPv4 traffic to a destination pseudowire (over IGP or BGP-LU). |
|
This feature enables a steering mechanism in which IGPs automatically use the policy for destination's downstream of the policy end point. |
|
This feature allows you to compute Loop Free Alternate (LFA) paths, TI-LFA backup paths, and Microloop Avoidance paths for a particular Flexible Algorithm using the same constraints as the calculation of the primary paths for such Flexible Algorithms, for IS-IS. See Calculation of Flexible Algorithm Path. Inter-area leaking of Flexible Algorithm SIDs and prefixes and selectively filtering the paths that are installed to the MFI are also supported. See Flexible Algorithm Prefix-SID Advertisement and Installation of Forwarding Entries for Flexible Algorithm Paths. |
|
Telemetry (Model-Based Telemetry and Event-Based Telemetry) Support for Performance Measurement |
This feature enables Model-Based Telemetry (MDT) and Event-Based Telemetry (EDT) that allow the data to be directed to a configured receiver. This data can be used for analysis and troubleshooting purposes to maintain the health of the network. The sr_5_label_push_enable SDM template is mandatory for this feature to function. |
Upgrading the Software on the Cisco ASR 920 Series Routers |
|
The features uses the following command to provide enhanced security to the routers: platform secure-cfg When you enable the command, the router does not boot if the SD card is replaced, swapped, or modified externally. Thus, you cannot format the SD card externally and this prevents the misuse of the router. |
GRPC telemetry is now supported on Cisco ASR 920 routers, for non-default VRF.
Complete YANG Model for Ethernet EVC Configuration – An Ethernet Virtual Connection (EVC) is defined by the Metro-Ethernet Forum (MEF) as an association between two or more user network interfaces that identifies a point-to-point or multipoint-to-multipoint path within the service provider network. An EVC is a conceptual service pipe within the service provider network.
YANG Data Models—For the list of Cisco IOS XE YANG models available with this release, navigate to https://github.com/YangModels/yang/tree/master/vendor/cisco/xe/1741.
Revision statements embedded in the YANG files indicate if there has been a model revision. The README.md file in the same GitHub location highlights changes that have been made in the release.
Complete YANG Model for CFM Configuration – Ethernet Connectivity Fault Management (CFM) is an end-to-end per-service-instance Ethernet layer operations, administration, and maintenance (OAM) protocol. It includes proactive connectivity monitoring, fault verification, and fault isolation for large Ethernet metropolitan-area networks (MANs) and WANs.
YANG Data Models—For the list of Cisco IOS XE YANG models available with this release, navigate to https://github.com/YangModels/yang/tree/master/vendor/cisco/xe/1741.
Revision statements embedded in the YANG files indicate if there has been a model revision. The README.md file in the same GitHub location highlights changes that have been made in the release.