RPC deletes dynamic subscription, the same way as the clear telemetry ietf subscription command. A subscription is also deleted when the parent NETCONF session is torn down or disconnected. If the network connection is interrupted, it may take some time for the SSH or NETCONF session to timeout, and for subsequent subscriptions to be removed. The RPC is similar to the RPC. However, the RPC uses the identifier element that contains the ID of the subscription to be deleted, instead of the subscription-id element. The transport session used by the target subscription also differs from the one used by the RPC.
Deleting Subscriptions Using the CLI The following sample output shows all the available subscriptions: Device# show telemetry ietf subscription all Telemetry subscription brief ID Type State Filter type -------------------------------------------------------- 2147483648 Dynamic Valid xpath 2147483649 Dynamic Valid xpath The following example shows how to delete a dynamic subscription: Device# clear telemetry ietf subscription 2147483648 Deleting Subscriptions Using NETCONF RPC The following example shows how to delete a subscription using NETCONF:
message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:yang:ietf-event-notifications" xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0"> 2147483650 Deleting Subscriptions Using NETCONF RPC The following examples show how to delete subscriptions using the RPC: xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-oper"> * Enter a NETCONF operation, end with an empty line version="1.0" encoding="UTF-8"?> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="2"> Model-Driven Telemetry Deleting Dynamic Subscriptions Model-Driven Telemetry 14