Configuring Dynamic Telemetry Subscription (IPv4 Collector)

Usage Scenario

If a collector functioning as a client initiates a connection to a device functioning as a server, the data sampled is dynamically subscribed to. In this case, you need to configure the source IP address and number for a port to be listened, and enable the gRPC service. The protocol used to send data is gRPC.

If the connection where dynamic telemetry subscription resides is interrupted, the device automatically cancels the subscription and stops data sampling and reporting. The configuration cannot be restored unless the collector sends a connection request again. For example, if a user wants to monitor an interface for a period of time, configure dynamic telemetry subscription. To stop monitoring, tear down the connection. The subscription is automatically canceled and cannot be restored. This avoids the long-term load on devices and simplifies the interaction between users and devices.

Pre-configuration Tasks

Before configuring dynamic telemetry subscription, complete the following tasks:

• Configure a static route or dynamic routing protocol to ensure that devices can communicate at the network layer.

• Create a local user, add the user to the administrator group, and configure the service type of the user.

• Create an ACL, if needed, for the gRPC service to control which clients can connect to the server. For details about how to create an ACL, see "ACL Configuration" in Configuration Guide > IP Services.

• Create an SSL policy, if needed, for the gRPC service so that the server and client can establish a secure SSL connection. For details about how to create an SSL policy, see "Configuring and Binding an SSL Policy" in Configuration Guide > Basic Configuration.