CCNP ENARSI lab 32 of 35
IP SLA and NetFlow v5, v9 and Flexible NetFlow
Measure voice quality across a WAN with IP SLA UDP jitter and a responder, alert on slow round trips, and see who is using the network with traditional NetFlow v5 and Flexible NetFlow v9, decoded live by a collector.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 32 - IP SLA and NetFlow v5 v9 and Flexible NetFlow
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 4 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
Nighthawk Media's branch office (R1) complains that video calls to head office (R3) break up in the afternoons, and nobody knows what else is using the WAN. You'll add measurement (IP SLA, which generates synthetic traffic and measures it) and visibility (NetFlow, which records real traffic) and send the flow records to a collector that decodes them live.
| Device | Interface | Address | Notes |
|---|---|---|---|
| R1 | Lo0 / Lo1 / Gi0/0 | 10.255.0.1/32 / 10.32.1.1/24 / 10.32.12.1/24 | branch |
| R2 | Lo0 / Gi0/0 / Gi0/1 | 10.255.0.2/32 / 10.32.12.2/24 / 10.32.23.2/24 | WAN router: traditional NetFlow |
| R3 | Lo0 / Lo1 / Gi0/0 / Gi0/1 | 10.255.0.3/32 / 10.32.3.1/24 / 10.32.23.3/24 / 10.32.100.1/24 | head office: IP SLA responder, Flexible NetFlow |
| COLLECTOR | eth0 | 10.32.100.100/24 | NetFlow collector, UDP 2055 |
OSPF already connects everything.
What you’ll practise
- Configure an IP SLA UDP jitter operation with a codec and an IP SLA responder
- Configure an ICMP echo operation with thresholds and a reaction
- Read jitter, latency, packet loss and MOS from IP SLA statistics
- Configure traditional NetFlow with v5 export and read the cache
- Configure Flexible NetFlow records, exporters and monitors with v9 export
The tasks
- Measure voice quality with UDP jitter
- Alert on slow round trips
- Traditional NetFlow v5 on R2
- Flexible NetFlow v9 on R3
- Where assurance fits
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
- R1
Gi0/0to R2Gi0/0 - R2
Gi0/1to R3Gi0/0 - R3
Gi0/1to COLLECTOReth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| COLLECTOR | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENARSI 300-410 guided labs.Open
32 - IP SLA and NetFlow v5 v9 and Flexible NetFlowand 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 CCNP ENARSI 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.