1 rcvr-type-protocol receiver1 Named Receiver Operation and Operational State Named receiver objects and subscription receiver objects (that refer to the named receiver) have two different operational states. The operational states are valid or invalid. The most common reason for a named receiver to be invalid is incomplete configuration, however; it could also be due to other reasons. The operational state view of a named receiver has a field that provides a text explanation on why the receiver is invalid. When the receiver state is valid, this field is empty.
Displaying Named Receiver State Using the CLI To view the state of named receivers of all types, use the show telemetry receiver command. The all keyword displays information about all named receivers in a brief format, and the name keyword displays detailed information about the specified named receiver. The following is sample output from the show telemetry receiver all command: Device# show telemetry receiver all Telemetry receivers Name Type Profile State Explanation ----------- --------------------------------------------------------------------- receiver1 protocol tls-trustpoint Valid The following is sample output from the show telemetry receiver name command:
Device# show telemetry receiver name my-receiver Name: my-receiver Profile: tls-profile State: Valid State Description: Last State Change: 09/18/24 15:50:54 Type: protocol Protocol: grpc-tls Host: collector.cisco.com Port: 45000 (edited) Named Receiver State Using YANG Models The state of the named receivers can be retrieved using the Cisco-IOS-XE-mdt-oper-v2 YANG model. The mdt-oper-v2-data container contains an mdt-named-receivers list that contains the operational state of all named receivers. Model-Driven Telemetry Named Receiver Operation and Operational State Model-Driven Telemetry 23