Network automation lab 14 of 27

Model-driven telemetry on IOS XE: dial-in, dial-out and webhook alerts

Stream data out of an IOS XE router instead of polling it: a dial-in subscription over NETCONF, configured dial-out subscriptions created three ways (CLI, NETCONF and RESTCONF), a collector that sees the router connect, and a small pipeline that turns telemetry into webhook alerts.

Run this lab

It needs Lite: its 2 nodes are set to 2 vCPU and 5,120 MB in total. That fits the free demo too.

In your workspace: Shared, then Network Automation - CCNA and CCNP Automation guided labs, then 14 - Model-driven telemetry on IOS XE - dial-in dial-out and webhook alerts

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 80 minutes
Nodes need
2 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Kestrel Freight's NOC polls its routers with SNMP every five minutes and misses everything that happens in between. The team wants push: the router streams the data it's asked for, as structured YANG-modelled data, as often as needed. You'll prototype it on the Manchester router xe1: a live CPU stream to your workstation, permanent dial-out subscriptions defined three different ways (as the ENAUTO blueprint expects), and an alerting step that posts to the NOC's webhook when a threshold is crossed.

DeviceAddressRoles
xe110.10.20.21IOS XE 17.3, NETCONF 830 and RESTCONF 443 enabled
devbox10.10.20.10dial-in client (ncclient), stand-in collector on TCP 57500 (tcp_collector.py), NOC webhook on http://127.0.0.1:8000/alerts (alert_receiver.py)

~/lab/mdtlab.py has a NETCONF connect() and a subscribe() helper. Login netops / NetOps-Lab1.

What you’ll practise

  • Explain model-driven telemetry: subscriptions, streams, XPath filters, periodic and on-change updates, encodings, transports and collectors
  • Create a dynamic (dial-in) subscription over NETCONF and process its notifications
  • Configure dial-out subscriptions with the CLI, NETCONF and RESTCONF, and verify their state
  • Turn streamed data into webhook alerts

The tasks

  1. The telemetry model
  2. A dial-in subscription over NETCONF
  3. A dial-out subscription with the CLI
  4. The same with NETCONF
  5. The same with RESTCONF
  6. From telemetry to webhook alerts
  7. Save, and think about scale

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Model-driven telemetry on IOS XE - dial-in dial-out and webhook alerts2 nodes and 1 network, 2 links. Every link is listed as text below the diagram.devboxxe1Mgmteth0Gi1
2 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Model-driven telemetry on IOS XE: dial-in, dial-out and webhook alerts, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
devboxEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
xe1Cisco CSR 1000vcsr1000vng-universalk9.17.03.08a-serial1 vCPU, 4,096 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Network Automation - CCNA and CCNP Automation guided labs.

  3. Open 14 - Model-driven telemetry on IOS XE - dial-in dial-out and webhook alerts and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Network automation labs

All Network automation labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.