Configuring a Destination Collector

When you configure static telemetry subscription to the data sampled or a customized event, you need to create a destination group and specify a destination collector to which the data is sent.

Context

When static subscription is configured, a device functions as a client and a collector functions as a server. To statically subscribe to the data sampled or a customized event, you need to configure the IP address and port number of a destination collector, and the protocol and encryption mode for data sending.

Procedure

Run system-view
The system view is displayed.
Run telemetry
The telemetry view is displayed.
Run destination-group destination-group-name
A destination group to which the data sampled is sent is created, and the Destination-group view is displayed.
Run ipv4-address ip-address-ipv4 port port [ vpn-instance vpn-instance ] [ protocol { grpc [ no-tls ] | udp } ]
An IP address and a port number are configured for the destination collector, and a protocol and an encryption mode are configured for data sending.
This command can be run for no more than five times for each destination group.
Both this command and the protocol command in the Subscription view can be run to configure a protocol and encryption mode for the target collector. If the target collector is associated with the subscription, command configurations take effect based on the following rules:
- If the protocol command has been run in the subscription view, the protocol and encryption mode configured in the subscription view take effect.
- If the protocol command is not run in the Subscription view, the protocol and encryption mode configured in the Destination-group view take effect.
Run commit
The configuration is committed.