What's New in Hardware for Cisco IOS XE Dublin 17.10.x
There are no new hardware features for 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 Dublin 17.10.x.
For information on features supported for each release, see Feature Compatibility Matrix.
There are no new hardware features for this release.
Feature | Description | ||
---|---|---|---|
Carrier Ethernet |
|||
Tagged Packet Support Using Link Layer Discovery Protocol (LLDP) |
LLDP now supports tagged packet transmission over a service instance with dot1q encapsulation. LLDP advertises information about themselves to their network neighbors, and store the information they discover from other devices. Though both these transmitted frames go through the same physical interface, they can be uniquely identified by the information advertised in the Port ID Type-Length-Value (TLV). You can use the lldp enable command to enable LLDP over a particular service instance. Use the show lldp neighbors and show lldp entry command outputs for neighboring device details. |
||
CEM |
|||
You can configure frame relay on the iMSG serial interface for the following interface modules:
|
|||
IP |
|||
Improved IPv6 Forwarding Failure Notification |
Improvements have been made to the Cisco IOS XE platforms to maintain compliance with IETF standards as specified for the Internet Protocol, Version 6 (IPv6) in RFC 8200. The enhancements fix some common causes of IPv6 forwarding faults and notify the sender about undelivered packets to a specified target. Notifications are received as log messages that can be accessed by enabling the following debugging command: debug ipv6 Using the notifications, you can effectively troubleshoot IPv6 forwarding issues. |
||
IP SLAs |
|||
You can perform Service Activation and Deactivation (SADT) over Virtual Circuit (VC) even when access interface is down. |
|||
Programmability |
|||
Telemetry for Monitoring Optical Transceivers |
The Cisco-IOS-XE-transceiver-oper data model contains a collection of YANG definitions for monitoring optical transceivers. Maintaining certain parameters such as the voltage, temperature, or current at a desired level ensures optimal performance of optical modules. You can now subscribe to receive telemetry data, periodically, for debugging issues related to these parameters. Based on the telemetry data, you can mitigate problems such as elevated temperatures, which can have a significant effect on the performance of optical modules. |
||
System Logging |
|||
Support for Disabling GARP |
|||
Support for Disabling GARP |
You can now disable Gratuitous ARPs (GARP) on your router. A Gratuitous ARP (GARP) is an ARP request that is normally unneeded according to the ARP specification (RFC 826), however is useful in specific cases such as:
GARP is disabled by default, and is enabled using the ip arp gratuitous arp local command. You can choose to ignore the GARPs using the ip arp gratuitous ignore command. For more information, see Cisco IOS IP Addressing Services Command Reference. |
||
YANG Support |
|||
YANG Model Support for L2VPN Operations |
The Cisco-IOS-XE-l2vpn-oper native model is a collection of YANG definitions for L2VPN services operational data. The leaves and lists present in the following sensor paths are now supported:
With this model, you can get the L2VPN service name, service type, interface name, peer address, status, encapsulation type, and virtual circuit ID by using a NETCONF RPC. In earlier releases, you could perform this action by using the following CLIs:
|