While all the states discussed in this section are available to all types of connections, not all have to be used. Table 5: Telemetry Connection States Additional operational state associated with a connection includes the identity of the remote receiver (the peer, when available), and the time of the last state change. Telemetry Protocol Connections This section discusses protocol type connections and how these are used by subscription receivers that are assigned to named protocol receivers. Table 6: Parameters of a Protocol-Type Connection Some of these parameters are based on the configuration of the subscription receiver’s parent subscription.
When resolving the connection parameters from the configuration, the VRF is determined first, followed by the destination IP address, and finally the source IP address, if an order is not specified. If a given step in the resolution fails non-permanently, there are infinite retries at 5 second intervals. Model-Driven Telemetry Telemetry Protocol Connections Connection State Description CLI Value YANG Value The connection has been created, but not yet initiated. Pending con-state-pending Connecting con-state-connecting A request to set up the connection is in progress. Active con-state-active The connection is up and is available for use by subscription receivers.
Disconnecting con-state -disconnecting The connection has been torn down and is waiting to be released by subscription receivers. Parameter Origin Comments Destination IP address Named receiver host Because hosts use domain names, domain name resolution may be required. Destination port number Named receiver port Must be explicitly configured. Source VRF Subscription, if specified Default VRF is used, if not specified. Otherwise the VRF name is resolved to an internal identifier. Source IP address Subscription, if specified If not specified, the source IP address is determined based on the VRF and destination IP address. Model-Driven Telemetry 26