Receiving a Response Code When a subscription is successfully created, the device responds with a subscription result of notif-bis:ok and a subscription ID. The following is a sample response RPC message for a dynamic subscription: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101"> xmlns="urn:ietf:params:xml:ns:yang:ietf-event-notifications" xmlns:notif-bis="urn:ietf:params:xml:ns:yang:ietf-event-notifications">notif-bis:
ok xmlns="urn:ietf:params:xml:ns:yang:ietf-event-notifications">2147484201 Receiving Subscription Push Updates for NETCONF Dial-In Subscription updates pushed from the device are in the form of an XML RPC and are sent over the same NETCONF session on which these are created. The subscribed information element or tree is returned within the datastore-contents-xml tag. The following is a sample RPC message that provides the subscribed information:
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 2017-05-09T21:34:51.74Z xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push"> 2147483650 xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-process-cpu-oper"> 5 If the information element to which a subscription is made is empty, or if it is dynamic, for example, a named access list, and does not exist, the periodic update will be empty and will have a self-closing datastore-contents-xml tag. The following is a sample RPC message in which the periodic update is empty:
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> Model-Driven Telemetry Receiving a Response Code Command or Action Purpose Device(config-mdt-subs)# encoding encode-kvgpb Step 8 receiver ip address ip-address receiver-port protocol protocol profile name Example: Device(config-mdt-subs)# receiver ip address 10.22.22.45 45000 protocol grpc tls profile secure profile _ _ Configures the receiver IP address, protocol, and profile for notifications. Step 9 end Example: Device(config-mdt-subs)# end Exits telemetry-subscription configuration mode and returns to privileged EXEC mode. Model-Driven Telemetry 45