The following is a sample NETCONF reply to retrieve the state of named receivers: xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-oper-v2"> version="1.0" encoding="UTF-8"?> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="2"> xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-oper-v2"> my-receiver tls-profile grpc-tls rcvr.test.com 45000 named-rcvr-state-valid 2020-…:00 Subscription Receiver Operation and Operational States Subscription receivers are the subscription-related objects that connects to the actual subscription receiver or collector.
While the mechanism needed to reach the collector is specific to the receiver type, a connection is the entity that is used to allow the subscription to reach its receiver or collector. Subscription receiver state is based on its ability to request and use the connection to the receiver and has a number of states that are associated with the control of other resources required to allow the subscription to send updates to the receiver or collector.
Subscription Receiver States The operational state of a subscription receiver consists of the configured name (that is the index of the connection), the state of the receiver, an explanation or note about the state, and the time of the last state change. The explanation string is not always used. The possible states of a subscription receiver are shown in the table below. Table 4: Subscription Receiver States Model-Driven Telemetry Subscription Receiver Operation and Operational States Subscription Receiver State Description CLI Value YANG Value The receiver is disconnected and no attempt is made to reconnect it. Disconnected rcvr-state-disconnected Model-Driven Telemetry 24