CCNA lab 28 of 46
Syslog and SNMP: see what your network is saying
Send two routers' logs to a network management station, read each message's facility, severity and mnemonic, then poll the routers with SNMPv2c and SNMPv3 and catch their link traps.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 28 - Syslog and SNMP - see what your network is saying
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 4 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
Harbourside Leisure's two routers fail occasionally, and the first anyone hears of it is a phone call. You'll set up a network management station (NMS, an Ubuntu workstation already running a syslog and trap receiver) so the routers send their log messages and traps to it, and so it can poll them with SNMP.
| Device | Address | Notes |
|---|---|---|
| R1 | 10.28.0.1/24 | managed router |
| R2 | 10.28.0.2/24 | managed router |
| S1 | 10.28.0.3/24 | switch |
| NMS | 10.28.0.100/24 | syslog (UDP 514) and trap (UDP 162) receiver; net-snmp tools |
Lab values: SNMPv2c read-only community CLB-RO (polling) and CLB-TRAP (traps); SNMPv3 user nms in group NMS-GROUP, SHA password AuthPass1!, AES-128 password PrivPass1!.
What you’ll practise
- Interpret syslog messages: timestamp, facility, severity, mnemonic and text
- Configure buffered and remote logging with a severity threshold, facility and source interface
- Explain SNMP managers, agents, MIBs, OIDs and the message types
- Configure read-only SNMPv2c with an ACL and SNMPv3 with authentication and encryption
- Send SNMP traps and see them arrive at the NMS
The tasks
- Take a syslog message apart
- Keep logs on the router
- Send logs to the NMS
- Understand SNMP
- Enable SNMPv2c read-only polling
- Add SNMPv3 with authentication and encryption
- Send traps
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 S1Gi0/0 - R2
Gi0/0to S1Gi0/1 - NMS
eth0to S1Gi0/2
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| S1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 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
CCNA 200-301 guided labs.Open
28 - Syslog and SNMP - see what your network is sayingand 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 CCNA 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.