cisco Model-Driven Telemetry — RPC Support in Telemetry

The following table describes the supported streams and encodings along with the combinations that are supported. While streams-as-inputs is intended to be independent of the protocols-as-outputs, not all combinations are supported. Table 3: Supported Combination of Protocols RPC Support in Telemetry You can send and receive YANG XML remote procedure calls (RPCs) in established NETCONF sessions. The and RPCs are supported for telemetry. When an RPC is sent, the RPC reply from a publisher contains an message with a element containing a result string. The following table displays the response and reason for the response in an message:

Model-Driven Telemetry RPC Support in Telemetry Transport Protocol NETCONF gRPC gNMI Dial-In Dial-Out Dial-In Dial-Out Dial-In Dial-Out Stream yang-push Yes No No Yes Yes No yang-notif-native Yes No No Yes No No Encodings XML No No Key-value Google Protocol Buffers (kvGPB) • JSONIETF _ • PROTO PROTO encoding is supported in Cisco IOS XE Dublin 17.11.1 and later releases. No Result String RPC Cause ok Success error-no-such-subscription The specified subscription does not exist. error-no-such-option The requested subscription is not supported. error-insufficient-resources A subscription cannot be created because of the following reasons: Model-Driven Telemetry 8