ON THIS PAGE
junos:genstate-path
Usage
<rpc-reply>
<operational-response-tag junos:genstate-path="path">
<element junos:genstate-path="path">
<first-child-of-element junos:genstate-path="path">
<second-child-of-element junos:genstate-path="path">
<!-- additional children of element -->
</element>
</operational-response-tag>
</rpc-reply>Description
Define the genstate resource path associated with the container or
leaf statement in the operational response.
A gNMI telemetry collector can subscribe to resource paths published in the
genstate YANG modules to query for the corresponding state data
on a device. When a client application executes an operational RPC with the
format="xml-genstate-path" attribute, the server returns XML
output that includes the junos:genstate-path attribute for every
emitted tag that is available for subscription. The attribute value is the
genstate subscription path.
Usage Example
The following example executes the
<get-commit-revision-information> RPC and requests the
xml-genstate-path format.
<rpc><get-commit-revision-information format="xml-genstate-path"/></rpc>
The xml-genstate-path format returns the command output with the
genstate paths that a telemetry client can subscribe to for the
corresponding state data.
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/26.2R1.12-EVO/junos"> <commit-revision-information junos:genstate-path="genstate:/genstate/commit-revision-information"> <revision junos:genstate-path="genstate:/genstate/commit-revision-information/revision">re0-1778619027-1</revision> </commit-revision-information> </rpc-reply>
Release Information
junos:genstate-path attribute added in Junos OS Release 26.2R1 and
Junos OS Evolved Release 26.2R1.