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
- 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.
| Device | Address | Roles |
|---|---|---|
| xe1 | 10.10.20.21 | IOS XE 17.3, NETCONF 830 and RESTCONF 443 enabled |
| devbox | 10.10.20.10 | dial-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
- The telemetry model
- A dial-in subscription over NETCONF
- A dial-out subscription with the CLI
- The same with NETCONF
- The same with RESTCONF
- From telemetry to webhook alerts
- 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.
Every link, as text
- devbox
eth0to Mgmt (network) - xe1
Gi1to Mgmt (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| devbox | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| xe1 | Cisco CSR 1000v | csr1000vng-universalk9.17.03.08a-serial | 1 vCPU, 4,096 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Network Automation - CCNA and CCNP Automation guided labs.Open
14 - Model-driven telemetry on IOS XE - dial-in dial-out and webhook alertsand 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
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.