Get/Set RPC

Information is retrieved from the NE using GET RPC messages, which consists of ‟GetRequest” and ‟GetResponse” messages. The client asks for information by specifying following:

a set of paths

All rules to a path definition apply, as specified in the gNMI specification.
type

This refers to configuration, state, or operational data.
encoding

In accordance to server advertisement during capability discovery.
use_models

This message is ignored.

There is an upper limit on the size of the ‟GetResponse” message. This limit cannot exceed 100MB. If the limit is exceeded, the SR OS gRPC server responds with an error message.

To modify the information in an NE element, a SET gRPC message is used. This gRPC supports three types of transactions:

delete
replace
update

With a gNMI SET RPC, SR OS authorizes all configuration changes, that is, it checks the YANG tree and authorizes every changed element.

The deletion of a container results in the deletion of any children containers that are authorized for deletion as well as their contents. Children containers that are not authorized for deletion, as well as their contents, are retained. For example, upon deletion of configure system, configure system security is not deleted because the deletion of that child container is not authorized.

Note: Only changes to configuration values are checked for authorization. A configuration command that simply writes the same value to a leaf succeeds even if the user does not have access to that leaf (but there is no resulting change to the configuration).

For example, when a user is not authorized to change access li, but attempts to change it for another user who already has access li, SR OS allows that action because there is no change in value.