New and Changed Programmability Features
Feature | Description | Changed in Release | Where Documented | ||
---|---|---|---|---|---|
Support to poll specific processes to stream telemetry data. |
Introduced
|
Release 7.1.2 |
Obtain this data model from Github repository. |
||
OCNI BGP advertised prefix |
OCNI BGP data model has global, neighbor and peer-group containers. Under the neighbor container are the Address Family Identifier (AFI) state-related leaves. Three leaves (sent, installed and advertised prefix count) are related to the prefixes received from and advertised to the neighbor specific to that AFI. The sent count is defined as how many prefixes are sent to the neighbor for a specific AFI. In the existing implementation, the cumulative count may not display accurate value owing to various conditions such as route-refresh out, policy changes, route-target changes, configuration changes like nexthop-self to name a few. In this release, BGP walks through the prefix table calculating exactly how many prefixes are advertised for each neighbor. The results are collected in an array, converted and sent to MDT. |
Release 7.1.2 |
Obtain this data model from Github repository. |
||
Generic Routing Encapsulation (GRE) Tunnel configuration support added to oc-interfaces data model |
|
Release 7.1.2 |
Drive Network Automation Using Programmable YANG Data Models chapter Obtain this data model from Github repository. |
||
Table connection support in openconfig- network instance (oc-ni) data model
|
The oc-ni data model is defined by OpenConfig community. This model defines the network instance concept to model Layer 3
and Layer 2 network instances applicable for services such as L3VPN, L2VPN, and EVPN.
The table-conection container in the oc-ni data model contains policies that dictate how routing information base (RIB) or forwarding information base (FIB) entries are propagated between routing tables. The leaf list consists of a list of connections between pairs of routing or forwarding tables, the leaking of entries between which is specified by the import policy. A connection connecting a source table to a destination table implies that routes that match the policy specified for the connection are available for the destination protocol to advertise, or match within its policies. It shows the configuration and state parameters that relate to the connection between tables.
|
Release 7.1.2 |
Obtain this data model from Github repository. |
||
Support for |
Support for oc-system data model to manage system-wide services and functions on network devices. Use this data model to configure and retrieve operational state data of the system.
|
Release 7.1.15 |
Obtain this data model from Github repository. |
||
Revision of oc-interfaces.yang model from version 1.0.2 to version 2.4.0 |
|
Release 7.1.1 |
Drive Network Automation Using Programmable YANG Data Models chapter Obtain this data model from Github repository. |
||
gRPC Network Operations Interface (gNOI) |
gNOI defines a set of gRPC-based microservices for executing operational commands on network devices. Extensible Manageability Services (EMS) gNOI is the Cisco IOS XR implementation of gNOI.
|
Release 7.1.1 |
Use gRPC Protocol to Define Network Operations with Data Models chapter |
||
Support for |
The OpenConfig -Bidirectional Forwarding Detection (oc-bfd) data model defines the BFD protocol in multi-vendor environment to configure and get operational state data for the BFD protocol.
|
Release 7.1.1 |
Drive Network Automation Using Programmable YANG Data Models chapter Obtain this data model from Github repository. |
||
Support for |
The native Multicast Label Distribution Protocol (mldp) model defines configuration and operational state data for the MLDP protocol. |
Release 7.1.1 |
Drive Network Automation Using Programmable YANG Data Models chapter Obtain this data model from Github repository. |
||
Revised |
The OpenConfig - Integrated Intermediate System-to-Intermediate System (oc-isis) model defined by the OC community. In this release, support is provided for additional paths in oc-isis data model. |
Release 7.1.1 |
Obtain this data model from Github repository. |
||
Revised |
The OpenConfig-Policy (oc-policy) data model defined by the OC community contains general data definitions for use in routing policy. It can be imported by modules that contain protocol-specific policy conditions and actions. In this release, support is extended for additional paths in the oc-policy data model with a revised version 2.0.1 to version 3.1.0. For information about limitations for this feature, see the Note section after this table. |
Release 7.1.1 |
Obtain this data model from Github repository. |
||
Power ON and Power OFF a line card using |
Enhancement to support the ability to power ON and power OFF a line card using oc-platform data model. |
Release 7.1.1 |
Obtain this data model from Github repository. The relevant model paths are:
|
||
Stream telemetry data using |
Streaming data related to the underlying characteristics of the device including the operational state or configuration of that device using openconfig-platform data model. |
Release 7.1.1 |
Obtain this data model from Github repository. |
||
Revised gNMI features |
Enhancement of gNMI specification to include updates from version 0.4.0 to version 0.6.0. Support is extended for the following gNMI features:
|
Release 7.1.1 |
Use gRPC Protocol to Define Network Operations with Data Models chapter gRPC Network Management Interface For more information about the enhanced features, see gRPC Network Management Interface (gNMI) in Github repository. |
![]() Note |
|