cisco Model-Driven Telemetry — Deleting Configured Subscriptions

> > elem: "power-supply"> elem: "state"> > mode: SAMPLE sample_interval: 10000000000 > mode: STREAM encoding: JSON_IETF >' Modifying Configured Subscriptions There are two ways to modify configured subscriptions: • Management protocol configuration operations, such as NETCONF RPC • CLI (same process as creating a subscription) Subscription receivers are identified by the address and port number. Receivers cannot be modified. To change the characteristics (protocol, profile, and so on) of a receiver, it must be deleted first and a new receiver created.

If a valid receiver configuration on a valid subscription is in the disconnected state, and the management wants to force a new attempt at setting up the connection to the receiver, it must rewrite the receiver with the exact same characteristics. Deleting Configured Subscriptions You can use the CLI or management operation to delete configured subscriptions. The no telemetry ietf subscription command removes the configured subscriptions. Note that configured subscriptions cannot be deleted using RPCs, only through the configuration interface.

Deleting Subscriptions Using the CLI Device# configure terminal Device(config)# no telemetry ietf subscription 101 Device(config)# end Deleting Subscriptions Using NETCONF The following sample RPC shows how to delete a configured subscription: operation="delete"> 102 xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-cfg"> Model-Driven Telemetry Modifying Configured Subscriptions Model-Driven Telemetry 20