gNMI Protocol The gNMI Protocol feature describes the model-driven configuration and retrieval of operational data using the gRPC Network Management Interface (gNMI) capabilities, and the Get, Set, and Subscribe remote procedure calls (RPCs). gNMI Version 0.4.0 is supported. Restrictions for gNMI Protocol, on page 1 Information About the gNMI Protocol, on page 2 How to Enable the gNMI Protocol, on page 14 Configuration Examples for the gNMI Protocol, on page 20 Additional References for the gNMI Protocol, on page 20 Feature Information for the gNMI Protocol, on page 21 Restrictions for gNMI Protocol The following restrictions apply to the gNMI Protocol feature:
• BYTES and ASCII encoding options are not supported. • JSON IETF keys must contain a YANG prefix where the namespace of the child elements differs from that of the parent. This means that the routed VLAN derived from augmentation in openconfig-vlan.yang must be entered as oc-vlan:routed-vlan because it is different from the namespace of the parent nodes (parent nodes have the prefix oc-if) PROTO encoding is supported from Cisco IOS XE Dublin 17.11.1. • GetRequest: • Operational data filtering is not supported. • Use models are not supported.
These are a set of model data messages indicating the schema definition modules that define the data elements that must be returned in response to a Get RPC call. • GetResponse: • Alias, which is a string that provides an alternate name for a prefix specified within the GetResponse notification message is not supported. • Delete, which is a set of paths that are to be removed from a data tree is not supported. gNMI Protocol 1