CCNP ENARSI lab 31 of 35
SNMPv2c and SNMPv3, syslog, timestamps and conditional debugging
Wire two routers into a real monitoring server: accurate timestamps, local and remote syslog, SNMPv2c with an ACL, SNMPv3 with authentication and encryption, traps of both versions, and debugging that shows only what you ask for.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 2,048 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 31 - SNMPv2c and SNMPv3 syslog timestamps and conditional debugging
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 3 vCPU, 2,048 MB
- Smallest plan
- Lite
The scenario
Owl Analytics has bought a monitoring platform, and the operations team wants every router to feed it. The server NMS (a Linux host) collects syslog and SNMP traps and polls with the standard snmpget/snmpwalk tools. Routers R1 and R2 send nothing today, their log timestamps show uptime instead of the time, and last week an engineer's debug ip packet nearly froze a router.
| Device | Interface | Address | Notes |
|---|---|---|---|
| R1 | Gi0/0 / Gi0/1 / Lo0 | 10.0.12.1 / 10.31.100.1 /24 / 10.255.0.1/32 | core router |
| R2 | Gi0/0 / Lo0 | 10.0.12.2/24 / 10.255.0.2/32 | edge router |
| NMS | eth0 | 10.31.100.100/24 | syslog (UDP 514), traps (UDP 162), SNMP manager |
Monitoring standard: timestamps with milliseconds and time zone; local buffer 64 KB at informational; syslog to NMS at informational (R2: notifications) from Loopback0; SNMPv2c read-only community Owl-RO only for NMS; SNMPv3 user nms in group NMS-GROUP (authPriv, SHA Auth-Pass-26, AES-128 Priv-Pass-26); R1 sends SNMPv3 traps as nms, R2 sends SNMPv2c traps with community Owl-Trap; configuration-change traps on both.
What you’ll practise
- Configure timestamps, sequence numbers and the local logging buffer with the right severity
- Send syslog to a server from a stable source interface and read the severity levels
- Configure SNMPv2c read access restricted by an ACL, and poll it from a Linux manager
- Configure SNMPv3 views, groups and users with SHA and AES, and poll with authPriv
- Send SNMPv2c and SNMPv3 traps and recognise them at the receiver
- Limit debug output with conditional debugging
The tasks
- Timestamps and the local buffer
- Send syslog to the NMS
- SNMPv2c, restricted by an ACL
- SNMPv3 with authentication and encryption
- Traps of both versions
- Debug only what you need
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
- R2
Gi0/0to R1Gi0/0 - R1
Gi0/1to NMSeth0
| 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 |
| NMS | 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
31 - SNMPv2c and SNMPv3 syslog timestamps and conditional debuggingand 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.