Named Receivers With FQDN support, a new method of configuring receivers is introduced, called the named-receiver configuration. Named receivers are top-level configuration entities that can exist independent of subscriptions. Named receivers are identified by a name. The name is an arbitrary string, and is the index or key of the named receiver records in the system. The named receiver configuration contains all configurations associated with the receiver that is not subscription-dependent. The advantages of using named receivers are as follows: • Capable of supporting different types of receivers. • Better state and diagnostics information.
• Hostname can be used instead of an IP address to specify the host for protocol receivers. • Parameters of a receiver that is used by multiple subscriptions can be changed at a single place. Only protocol-type named receivers are supported, and these are: • cloud-native: Cloud native protocol • cntp-tcp: Civil Network Time Protocol (CNTP) TCP protocol • cntp-tls: CNTP TLS protocol • grpc-tcp: gRPC TCP protocol • grpc-tls: gRPC TLS protocol • native: Native protocol • tls-native: Native TLS protocol Named Protocol Receivers Named protocol receivers are used to specify telemetry transports that use protocols.
In addition to the name that identifies a receiver, named protocol receivers also use a host specification. The host specification takes a hostname or IP address, and a destination port number. Secure protocol transports also use a profile string. When a valid named protocol receiver is created, it is not automatically connected to the receiver. The named protocol receiver must be requested by at least one subscription to create a connection to the receiver. Note You can configure a named protocol receiver by using the CLI or YANG models. Configuring the Named Protocol Receiver Using YANG Models The YANG model, Cisco-IOS-XE-mdt-cfg, contains the named protocol receiver.
The container mdt-named-protocol-rcvrs inside the top level mdt-config-data container has a list of mdt-named-protocol-rcvr structures. This group has five members: • Name, which is the index in the list • Protocol • Profile Model-Driven Telemetry Named Receivers Model-Driven Telemetry 21