zNetLaB › Guided labs › Enterprise
NTP, syslog and SNMP for the management plane
Enterprise Beginner 5 devices 4 checked tasks 100 points Free lab
HQ is the network’s time source. Make the branch router synchronise to it, send its log messages to the syslog server, and answer SNMP reads on a read-only community — then prove the NMS can read its name. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This is a free lab: it stays open on the free plan. It needs an account, which keeps your progress.
The scenario
HQ is the network’s time source. Make the branch router synchronise to it, send its log messages to the syslog server, and answer SNMP reads on a read-only community — then prove the NMS can read its name.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 4 goals show as passed (100 points).
Network status
Devices: 2 routers, 1 switch, 1 server, 1 PC, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. HQ starts with addresses (G0/1 10.0.12.1/30) and static routes already configured. Branch starts with addresses (G0/1 10.0.12.2/30, G0/0 10.9.0.1/24). Syslog is a host with 10.9.0.50/24, gateway 10.9.0.1. NMS is a host with 10.9.0.60/24, gateway 10.9.0.1. SW-Mgmt starts with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
HQ is an NTP master at stratum 3 (20 pts) Branch synchronises to HQ (stratum 4) (30 pts) Branch logs to the syslog server (25 pts) Branch answers SNMP on the read-only community NetRO (25 pts) The activity, in order
HQ is an NTP master at stratum 3 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Branch synchronises to HQ (stratum 4) Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Branch logs to the syslog server Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Branch answers SNMP on the read-only community NetRO Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
HQ is the network’s time source. Make the branch router synchronise to it, send its log messages to the syslog server, and answer SNMP reads on a read-only community — then prove the NMS can read its name.
What you will be able to do
HQ is an NTP master at stratum 3
Branch synchronises to HQ (stratum 4)
Branch logs to the syslog server
Branch answers SNMP on the read-only community NetRO
The network
ISR 2911, Catalyst 2960-24TT, Server, PC — 5 devices in all, already cabled.
Gi0/1 10.0.12.1/30 Gi0/1 10.0.12.2/30 Gi0/0 10.9.0.1/24 Gi0/1 Fa0/1 Fa0 Fa0/2 Fa0 HQ Branch SW-Mgmt Syslog 10.9.0.50/24 · gw 10.9.0.1 NMS 10.9.0.60/24 · gw 10.9.0.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
HQ ISR 2911 configure it Branch ISR 2911 configure it SW-Mgmt Catalyst 2960-24TT configure it Syslog Server 10.9.0.50 / 255.255.255.0 gw 10.9.0.1 NMS PC 10.9.0.60 / 255.255.255.0 gw 10.9.0.1
Cabling
HQ Gi0/1 ↔ Branch Gi0/1 Branch Gi0/0 ↔ SW-Mgmt Gi0/1 SW-Mgmt Fa0/1 ↔ Syslog Fa0 SW-Mgmt Fa0/2 ↔ NMS Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
HQ interface g0/1
ip address 10.0.12.1 255.255.255.252
no shutdown
exit
ip route 10.9.0.0 255.255.255.0 10.0.12.2 Branch interface g0/1
ip address 10.0.12.2 255.255.255.252
no shutdown
exit
interface g0/0
ip address 10.9.0.1 255.255.255.0
no shutdown
exit Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 HQ is an NTP master at stratum 3 20 On HQ: show ntp status says synchronized. 2 Branch synchronises to HQ (stratum 4) 30 On Branch: show ntp status says synchronized. 3 Branch logs to the syslog server 25 Checked automatically against the device’s live state (loggingHost). 4 Branch answers SNMP on the read-only community NetRO 25 Checked automatically against the device’s live state (snmpComm).
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
HQ ntp master 3 Branch ntp server 10.0.12.1
logging host 10.9.0.50
logging trap informational
snmp-server community NetRO RO
snmp-server location Branch-Rack-1
snmp-server contact noc@lab.local NMS snmpget -v 2c -c NetRO 10.9.0.1 1.3.6.1.2.1.1.5.0 Where this is examined
This lab practises these topics in the zNetLaB certification courses:
DHCP, DNS, NTP, SNMP, Syslog — CCNA · IP Services Debugs, ping/traceroute, SNMP, syslog, NetFlow, SPAN, IP SLA — CCNP Enterprise · ENCOR · Network Assurance OSI model, ports and protocols — CompTIA Network+ · Networking Concepts Monitoring, logging, SNMP and traffic capture — CompTIA Network+ · Network Operations Monitoring, logging, SIEM and traffic analysis — CompTIA Security+ · Security Operations Network visibility: NetFlow, SPAN, syslog, NTP — CCNP Security Core · Secure Network Access, Visibility and Enforcement Host and port discovery, banner grabbing — Ethical Hacking (network level) · Reconnaissance, Scanning and Enumeration Service enumeration: SNMP, CDP/LLDP, NTP — Ethical Hacking (network level) · Reconnaissance, Scanning and Enumeration Detection: logging, NetFlow, SPAN and IDS placement — Ethical Hacking (network level) · Perimeter, Evasion and Secure Design
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.