Difference between revisions of "Sweetcomb/gNMIServer"
From fd.io
m (→Testing gNMI server functionalities) |
m (→Testing gNMI server functionalities) |
||
| Line 11: | Line 11: | ||
There are multiple gNMI clients available: | There are multiple gNMI clients available: | ||
| + | * [https://github.com/openconfig/gnmi gnmi_cli] | ||
* [https://github.com/google/gnxi/tree/master/gnmi_capabilities gnmi_capabilities] | * [https://github.com/google/gnxi/tree/master/gnmi_capabilities gnmi_capabilities] | ||
* [https://github.com/google/gnxi/tree/master/gnmi_get gnmi_get] : It will try to send a message with a default JSON IETF encoding. | * [https://github.com/google/gnxi/tree/master/gnmi_get gnmi_get] : It will try to send a message with a default JSON IETF encoding. | ||
Revision as of 14:16, 3 April 2019
gNMI Server
gNMI stands for gRPC Network Management Interface, it works like a client server protocol offering a set of 4 RPCs:
- Capabilities
- Get
- Set
- Subscribe
Testing gNMI server functionalities
There are multiple gNMI clients available:
- gnmi_cli
- gnmi_capabilities
- gnmi_get : It will try to send a message with a default JSON IETF encoding.
- gnmi_set
gnmi_capabilities -notls -target_addr localhost:50051
gnmi_get -notls -target_addr localhost:50051 -xpath "/ietf-interfaces/interface-state"
NB: Please note that gnmi client don't work with ":" separator in xpath. They only use "/".
