BGP

Delay BGP Route Advertisements

You can now prevent traffic loss due to premature advertising of BGP routes and subsequent packet loss in a network. You can achieve this by setting the delay time of the BGP start-up in the router until the Routing Information Base (RIB) is synchronized with the Forward Information Base (FIB) in the routing table. This delays the BGP update generation and prevents traffic loss in a network.

You can configure a minimum delay of 1 second and a maximum delay of 600 seconds.

This feature introduces the update wait-install delay startup command.

Interface and Hardware Component

Decapsulating Multiple Tunneled Packets Using Tunnel Source Direct

With this new tunnel source direct option, a single tunnel interface can decapsulate multiple tunnel packets whose outer destination IP is any of the IPv4 or IPv6 address that is locally configured and operationally Up in the switch.

Now, you can choose the IP ECMP links when there are multiple IP links between the two switches for decapsulation.

ERSPAN Traffic to a Destination Tunnel in a Non-Default VRF

In the Cisco IOS XR Release 7.5.3, the tunnels are grouped under the VRFs and you can segregate the traffic towards a specific VRF domain.

Encapsulated Remote Switched Port Analyzer (ERSPAN) now transports mirrored traffic through GRE tunnels with multiple VRFs, helping you design your network with multiple Layer 3 partitions.

In earlier releases, ERSPAN transported mirrored traffic through GRE tunnels that belonged to only default VRF.

Outer-header hashing support for IPoGREoGUE and MPLSoGREoUDP flows.

This feature specifies the IP hashing profile only on outer IP (L3 and L4) headers for IPoGREoGUE and MPLSoGREoUDP flows.

IP Addresses and Services

Client ID change in DHCP IPv4 Server Profile

With this release, we’ve introduced the allow-client-id-change configuration under DHCP IPv4 mode. This option ensures that the client machines have only one binding with DHCP IPv4 server constantly.

In scenarios where a client with active binding and valid lease time sends a discover message with a new client id, and the DHCP server approves such requests assuming it as a new client due to different client IDs. This results in multiple bindings for the same client, making the older binding redundant. This feature avoids wastage of DHCP resources due to such multiple bindings.

MPLS

Self-Ping Probe for Reoptimized LSP

You can now prevent traffic drops on a reoptimized label switch path (LSP) by timely confirmation that it's ready to handle the traffic. This confirmation is made possible by enabling the label edge router (LER) to send self-ping probes over the reoptimized LSP to the ingress LER. As soon the probe reaches the LER, there's confirmation that the RSVP programming is complete along the path. Post this confirmation, the LER switches traffic to the reoptimized LSP with no drop in traffic.

This feature introduces the self-ping keyword in the named-tunnels tunnel-te command.

System Management

Advanced Secure Hash Algorithm (SHA) for SNMPv3 Authentication

We’ve added the following SHA algorithms in this release that can be used to authenticate to the SNMPv3 server:

• HMAC128SHA224

• HMAC192SHA256

• HMAC256SHA384

• HMAC384SHA512

You can configure the above SHA algorithm for SNMPv3 authentication using the snmp-server user command.

System Security

Automatic renewal of Public Key Infrastructure (PKI) certificate

You can now enable the router to renew the PKI certificate from the Certificate Authority (CA) by configuring the percentage of the certificate validity, after which the router requests a new certificate from the CA, and the CA authorizes it before certification expiration. This feature eliminates the previously needed manual efforts of certification renewal and avoids interruptions such as MACsec session flaps due to certificate expiry and so on.

This feature introduces the following commands:

• auto-enroll

• renewal-message-type

OpenSSH Certificate based Authentication for Router

You can now use OpenSSH certificates to authenticate to the remote routers from a client machine. This feature uses the ssh-keygen utility, a standard SSH component to generate and manage authentication keys, available in OpenSSH to create a CA (Certificate Authority) like infrastructure for logging into the router.

In this feature, the certificates that are used to authenticate router and client are both signed by the same CA. This automatically establishes trust between router and client, and eliminates the need to establish trust, while using the client for remote logging to router for the first time.

Programmability

Unified Data Model to Configure Encapsulated Ambiguous VLANs

Use the Cisco-IOS-XR-um-if-encap-ambiguous-cfg.yang unified data model to configure encapsulated ambiguous VLANs with IEEE802.1ad Provider Bridging (PB) encapsulation type on an access-interface.

Unified Data Model to map script file to the custom OID

Use the Cisco-IOS-XR-um-script-server-cfg.yang unified data model to map script file to the custom OID.

Cisco-IOS-XR-um-if-encap-ambiguous-cfg.yang

Use the unified data model to configure encapsulated ambiguous VLANs with IEEE802.1ad Provider Bridging (PB) encapsulation type on an access-interface.

openconfig-network-instance.yang

Version 0.15.0

The OpenConfig data model is revised from version 0.6.0 to 0.15.0 and supports the following sensor paths to configure and retrieve the Layer 3 forwarding constructs, Layer 2 instances, static routes, forwarding instances, Border Gateway Protocol (BGP) parameters and so on:

openconfig-network-instance/network-instances/network-instance[name]/

• config

• state

• tables

• protocols

You can stream Event-driven and Model-driven telemetry data for the operational state of the network instance.

openconfig-system.yang Version 0.7.0

The OpenConfig data model is revised from version 0.6.0 to 0.7.0. This version introduces support to view the statistics of CPU utilization of a component, create a customized banner that is displayed before the username and password login prompts and view the operational state of the system memory using the following sensor paths:

openconfig-system:system/

• cpus

• memory/state

• config/login-banner

Event-driven telemetry is not supported for openconfig-system:/system/cpus sensor path. For the other sensor paths, you can stream Event-driven and Model-driven telemetry data for the operational state of the system.

openconfig-system-terminal.yang Version 0.3.1

The OpenConfig data model is revised from version 0.3.0 to 0.3.1. This version introduces the following config sensor paths to configure the IPv4 or IPv6 telnet server and the number of telnet sessions that are active simultaneously, and state sensor paths to view that the configuration is enabled:

IPv4:openconfig-system/system/telnet-server/

oc-term-ext:ipv4/oc-term-ext:vrf[vrf-name]/

• oc-term-ext:state/oc-term-ext:enable

• oc-term-ext:config/oc-term-ext:session-limit

• oc-term-ext:state/oc-term-ext:session-limit

IPv6: openconfig-system/system/telnet-server/

oc-term-ext:ipv6/oc-term-ext:vrf[vrf-name]/

• oc-term-ext:state/oc-term-ext:enable

• oc-term-ext:config/oc-term-ext:session-limit

• oc-term-ext:state/oc-term-ext:session-limit

With this release, an extended model Cisco-IOS-XR-openconfig-system-terminal-ext.yang is introduced to manage the telnet server configuration.

You can stream Event-driven and Model-driven telemetry data for the operational state of the system.

openconfig-routing-policy.yang Version 3.2.2

The OpenConfig data model is revised from version 3.1.0 to 3.2.2. You can configure the set-tag operation for local and interior gateway protocol (IGP) tagged routes in a routing policy.

This data model is used along with related data models for routing protocols such as border gateway protocol (BGP), interior gateway routing protocol (IGRP) and so on. With this release, the openconfig-bgp-policy.yang OpenConfig model is also revised from version 4.0.1 to version 6.0.2. You can configure BGP routes exchanged between two BGP peers using the following sensor paths:

openconfig-routing-policy:routing-policy/

• policy-definitions/policy-definition

• defined-sets/tag-sets/tag-set

• defined-sets/prefix-sets/prefix-set

• defined-sets/openconfig-bgp-policy:bgpdefined-sets/community-sets/community-set

• defined-sets/openconfig-bgp-policy:bgpdefined-sets/ext-community-sets/ext-community-set

• defined-sets/openconfig-bgp-policy:bgpdefined-sets/as-path-sets/as-path-set

You can stream Event-driven and Model-driven telemetry data for the operational state of the routing policy.

openconfig-local-routing.yang Version 1.2.0

The OpenConfig data model, which is part of the openconfig-network-instance.yang data model is revised from version 1.0.1 to 1.2.0. This revision introduces support to configure and retrieve the operational state data for static routes using the following sensor paths:

openconfig-network-instance/network-instances/network-instance[name]/

• config/enabled

• protocols/[identifier-name]/static-routes/static/config/description

• protocols/[identifier-name]/static-routes/static/state/description

You can stream Event-driven and Model-driven telemetry data for the operational state of the static routes.

openconfig-lacp.yang Version 1.2.0

The OpenConfig data model is revised from version 1.1.0 to 1.2.0 and introduces the following sensor paths to monitor the Link Aggregation Control Protocol ( LACP) aggregate interface timeouts and the time since the last timeout:

lacp/interfaces/interface[name]/members/member[interface]/state/:

• last-change

• counters/lacp-timeout-transitions

You can stream Event-driven telemetry data for the time since the last change of a timeout, and Model-driven telemetry data for the number of times the state has transitioned with a timeout. The state change is monitored since the time the device restarted or the interface was brought up, whichever is most recent.

openconfig-interfaces.yang Version 2.5.0

The OpenConfig data model is revised from version 2.4.3 to 2.5.0. This version introduces support to configure the interface to connect the system to an out-of-band management network and enable the system CPU to handle traffic using the following sensor paths:

openconfig-interfaces/interfaces/interface[name]/state/

• state/management

• state/cpu

• subinterfaces/subinterface[index]/state/management

• subinterfaces/subinterface[index]/state/cpu

You can stream Event-driven and Model-driven telemetry data for the operational state of the interface.

openconfig-if-ethernet.yang Version 2.12.1

The OpenConfig data model is revised from version 2.8.1 to 2.12.1 to support the following sensor paths to manage the Forward Error Correction (FEC) configuration and state of Ethernet interfaces:

Configuration sensor path:

openconfig-interfaces:interfaces/interface[name="interface-name"]/

openconfig-if-ethernet:ethernet/config/fec-mode

State sensor paths supported on half-duplex interfaces:

openconfig-interfaces:interfaces/interface[name="interface-name"]/

openconfig-if-ethernet:ethernet/state/

• in-carrier-errors

• in-interrupted-tx

• in-late-collision

• in-single-collision

State sensor paths supported on half-duplex and full-duplex interfaces:

openconfig-interfaces:interfaces/interface[name="interface-name"]/

openconfig-if-ethernet:ethernet/state/

• in-mac-errors-rx

• in-symbol-error

• out-mac-errors-tx

• in-maxsize-exceeded

You can stream Model-driven telemetry data for the operational state of the Ethernet interfaces.

openconfig-alarms.yang Version 0.3.2

The openconfig-alarms.yang OpenConfig data model is part of the openconfig- system.yang data model. The model is revised from 0.3.0 to 0.3.2 to enhance the time at which the alarm was raised by the system. This value is expressed relative to the UNIX Epoch time.

Using this sensor path, you can stream Event-driven and Model-driven telemetry data.

openconfig-platform-cpu.yang Version 0.1.1

The OpenConfig data model is revised from version 0.1.0 to 0.1.1 and introduces the following sensor paths to view the CPU utilization statistics of the fan components:

• openconfig-platform:components/component/cpu/openconfig-platform-cpu:utilization/state

• openconfig-platform:components/component[name=<node-name>]/cpu/openconfig-platform-cpu:utilization/state

The node-name indicates the location of the RP/CPU node.

openconfig-bgp.yang Version 6.0.0

The OpenConfig data model is revised from version 3.0.1 to 6.0.0. This version introduces the following changes:

• Added new BGP mappings to the data model openconfig-network-instance.yang

• Normalized timestamp units to nanoseconds

• Removed obsolete model mappings

• Managed model mappings with the same semantics but with different names that are absent in the new openconfig-network-instance.yang data model. For example, the name of the leaf under shutdown-threshold-pct container is changed to prefix-limit -pct. warning-threshold

• Added new sensor paths for Event-based telemetry

openconfig-rib-bgp.yang Version 0.7.0

The OpenConfig data model is revised from version 0.2.0 to 0.7.0. This version introduces the following changes:

• Managed model mappings for BGP Routing Information Base (RIB) in the openconfig-network-instance.yang data model

• Updated changes related to importing segment-routing module

oc-if-aggregate.yang Version 2.4.3

The OpenConfig data model is revised from version 1.0.2 to 2.4.3. This version does not add or modify leaves. Use this data model to manage the link bundles where one or more ports are aggregated together and treated as a single interface to provide increased bandwidth.

openconfig-bfd.yang Version 0.2.3

The OpenConfig data model is revised from version 0.2.2 to 0.2.3, the current latest version from the OC community.

Event-driven telemetry and Model-driven telemetry is not supported for the sensor paths.

openconfig-telemetry.yang Version 0.5.1

The OpenConfig data model is revised from version 0.2.0 to 0.5.1, the latest published version from the OC community. Use this data model to configure telemetry sessions on the router.

openconfig-messages.yang Version 0.0.1

The data model introduces the following sensor path to retrieve the operational state of syslog messages:

openconfig-system:system/messages

The severity of syslog messages varies from the highest severity level 0 (for emergencies) to the lowest severity level 7 (for debugging). Depending upon a specified severity level, the router streams data to the telemetry server, starting from the chosen severity level and higher. This enables you to limit the streamed syslog to the most significant ones.

Before you subscribe to the sensor path, you must configure the severity level either through the CLI or YANG:

• CLI: Router(config)#logging yang severity-level

• YANG: openconfig-system/messages/config/severity

This release does not support the debug-entries container.

openconfig-lldp.yang Version 0.2.1

You can now override the system default values of some of the mandatory LLDP Type-Length-Values (TLVs) that are advertised by routers to their directly connected neighboring devices. While advertising their identity and capabilities, routers can assign user-defined meaningful names instead of autogenerated values. Using the NETCONF RPC or CLI you can specify these user-defined values. The following leaves support user-defined values for the LLDP TLVs:

• OC-lldp:lldp/config/system-name

• OC-lldp:lldp/config/system-description

• OC-lldp:lldp/config/chassis-id-type

• OC-lldp:lldp/config/chassis-id

The data model also supports the following sensor paths to retrieve the operational state of LLDP packets that are sent and received by a specified interface:

• OC-lldp:lldp/state/counters/last-clear

• OC-lldp:lldp/state/counters/tlv-accepted

• OC-lldp:lldp/interfaces/interface/state/counters

• OC-lldp:lldp/interfaces/interface/neighbors/neighbor/state/age

• OC-lldp:lldp/interfaces/interface/neighbors/neighbor/state/last-update

openconfig-isis Version 0.6.0

With the revised version of this model, you can now monitor the system performance by checking the packet counter statistics and bandwidth, time, length, and values (TLVs) of IS-IS database.

The revised model updates the leaf nodes in the following paths:

• Configuration

• Global Mode

• System-level

• Interface

openconfig-macsec.yang Version 0.2.0

The OpenConfig data model for MACsec now includes viewing error counter for Protocol Data unit (PDU) and Secure Association Key (SAK) in the MKA (MACSecKey Agreement) protocol in the mka/state/counter sensor path that was previously deviated.

Using this sensor path, you can stream Event-driven and Model-driven telemetry data.