Tag :: OpenConfig

AAA accounting records can be enabled for OpenConfig gNMI/gNOI RPCs. Accounting records can be logged to the TACACS+ server, RADIUS server, or to syslog.

When OpenConfig is enabled, the entire YANG tree is exposed to the client. This allows a client to have read and write access to all parts of the YANG tree. In some cases, it would be preferable to block portions of the YANG tree so that specific part of the tree cannot be modified or read by the client. 

Traditionally, the OpenConfig gNMI service is based on a dial in model. A client sends a request to the gNMI server and

gNOI (gRPC Network Operations Interface) defines a set of gRPC based microservices for executing operational

gNOI (gRPC Network Operations Interface) defines a set of gRPC based microservices for executing operational

gNOI (gRPC Network Operations Interface) defines a set of gRPC based microservices for executing operational

The candidate configuration feature implements support for a candidate data store as specified in RFC6241.

Octa is a process which combines OpenConfig and certain TerminAttr functionality, primarily with the intent of

4.21.3F release supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC

4.23.2F release supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC

4.22.0F release supports reading and streaming various OpenConfig configuration and state models over gNMI (gRPC

These are the release notes and configuration guide for the OpenConfig feature in the 4.21.0F release.

This feature adds support for streaming the output of the following show command in Octa:. The

This feature allows LFIB (Label Forwarding Information Base) & associated counters export through OpenConfig mpls AFT (Abstract Forwarding Tree) YANG model.