• Hostname • Port number The following is a sample NETCONF RPC that shows how to create a named protocol receiver: xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-cfg"> my-receiver grpc-tls tls-profile collector.cisco.com 57500 Subscription Configuration Using Named Receivers To use a named receiver with a subscription, both the receiver type and receiver name must be specified. No additional receiver configuration is required, since all receiver-specific configuration is part of the named receiver configuration.
However; named protocol receivers still use the source VRF and source address of the subscriptions as part of the connection resolution process. The only supported name receiver type is protocol . Subscriptions can use either named receivers or legacy receivers, but cannot use both. If the legacy receiver is configured, setting the subscription receiver type and a named-receiver name is blocked. Similarly, if a subscription receiver type or a named receiver is specified, you cannot configure legacy receivers. Note that subscriptions use only one receiver, even if more than one receiver is configured.
Subscriptions using legacy receivers and subscriptions using named receivers are permitted to use the same connection; however, it is not recommended. Configuring a Named-Receiver Subscription Configuration Using YANG Model The only value supported for rcvr-type is rcvr-type-protocol, when named receivers are used. When legacy receivers are used, the value is the default rcvr-type-unspecified. The following is a sample NETCONF RPC that shows how to create a subscription using a named protocol-receiver:
xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-cfg"> Model-Driven Telemetry Subscription Configuration Using Named Receivers Model-Driven Telemetry 22