Cisco ios xe show cpu software#
Subsequent releases of that software release train also support that feature. Only the software release that introduced support for a given feature in a given software release train. The following table provides release information about the feature or features described in this module. Technical Services Newsletter, and Really Simple SyndicationĪccess to most tools on the Cisco Support website requires aįeature Information for Model-Driven Telemetry Product Alert Tool (accessed from Field Notices), the Cisco Products, you can subscribe to various services, such as the To receive security and technical information about your Resolving technical issues with Cisco products and technologies. Including documentation and tools for troubleshooting and The Cisco Support website provides extensive online resources, Subscribing to YANG Datastore Push Updates XPath: /mdt-oper:mdt-oper-data/mdt-subscriptionsĭraft-ietf-netconf-netconf-event-notifications-01 The following is sample output from the show telemetry ietf subscription subscription-ID detail command:ĭevice# show telemetry ietf subscription 2147483667 detail The following is sample output from the show telemetry ietf subscription dynamic brief command:ĭevice# show telemetry ietf subscription dynamic brief Use the show telemetry ietf subscription command to display the list of current subscriptions.ġ00 /ios:native/router/ios-rip:rip/ios-rip:version You can retrieve the list of current subscriptions by sending a RPC to the Cisco-IOS-XE-mdt-oper model.
Cisco ios xe show cpu update#
The following is as sample RPC message in which the periodic update is empty: If the information element to which a subscription is made is empty, or if it is dynamic (for example, a named access list)Īnd 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 that provides the subscribed information: The subscribed information element or tree is returned within the datastore-contents-xml tag. Subscription updates pushed from the device are in the form of an XML RPC and are sent over the same NETCONF session on which
Cisco ios xe show cpu full#
Periodic updates contain a full copy of the subscribed data element or table. When subscribing for emptyĭata, empty update notifications are sent at the requested period. Subscriptions for data that does not currently exist are permitted and run as normal subscriptions. This value must be explicitly set in the RPC. The minimum period interval is 100, or one second. Updates to the subscribed information every 10 seconds. Period is time, in centiseconds (1/100 of a second), between periodic push updates. Updates are then sent at the expiry of the configured periodic timer.įor example, if the period is configured as 10 minutes, the first update is sent immediately after the subscription is created If the device is busy or due to network congestion. With periodic subscriptions, the first push-update with the subscribed information is sent immediately but it can be delayed Configured subscriptions cause the publisher to initiate connections to receivers, and as a result, they are considered Two types of subscriptions are used in telemetry on Cisco IOS XE systems: dynamic and configured subscriptions.īecause dynamic subscriptions are created by clients (the subscriber) that connect into the publisher, they are consideredĭial-in. NETCONF and other northbound programmable interfaces (such as RESTCONF or gNMI) are supported to configure subscriptions. Is the default minimum) and on-change triggered subscriptions are supported. Periodic triggered subscriptions (100 centiseconds Will cause one of the inactive but valid configured subscriptions to be attempted. If too many subscriptionsĪre operating at the same time to allow all the valid configured subscriptions to be active, the removal of an active subscription The subscriptions can be either configured or dynamic, and use any combination of transport protocols. Is required, how the data is to be formatted, and, when not implicit, who (which receivers) should receive the data.Įven though the maximum number of supported subscriptions is platform-dependent, currently 100 subscriptions are supported. Specifically, a subscription is used to define the set of data that is requested as part of the telemetry data when the data Subscriptions are items that create associations between telemetry roles, and define the data that is sent between them.