Table of Contents
OpenConfig is a working group of technical contributors from different companies (mainly Google).
This working group defines vendor-neutral data models.
The OpenConfig defined YANG modules are published on this Github repository https://github.com/openconfig/public/tree/master/release/models
Here's the OpenConfig support on EOS
Certificate-based authentication is required for the devices to stream OpenConfig to CVP.
To enable certificate-based authentication between CVP and the devices, refer to this directory
To stream OpenConfig data to CVP, gNMI needs to be enabled on the EOS devices.
In the example below, default is the name of the management VRF. If you use another VRF for management change it accordingly.
configure
management api gnmi
transport grpc default
exit
The gNMI server should now be enabled and running on port 6030 in the default VRF.
show management api gnmi
The switch will use TerminAttr to publish the OpenConfig data to CVP when the cvgnmi flag is set.
configure
daemon TerminAttr
show active
Add the flag -cvgnmi at the end of the daemon TerminAttr configuration, then do a shutdown/no shutdown on the TerminAttr daemon otherwise the change will not be taken into account and then exit the daemon TerminAttr configuration.
shutdown
no shutdown
exit
The device should now stream OpenConfig data to CVP.
Use the telemetry browser on CVP GUI (Settings and Tools > Developper Tools > Telemetry Browser) to verify it.
Once we configured the devices to stream OpenConfig data to CVP, we can use gNMI or RESTCONF to access to these data on CVP.