Lab R17: Monitoring
Nothing is down this morning, and that is the trouble: the tools that would say so are the things that were changed. The office router R1 has a probe that decides which of two paths its traffic takes, a second probe that measures the primary path, a log, an SNMP agent for the management station and a flow monitor. Six changes were made in the night, and the first one made R1 stop writing the others down. Each ticket is somebody noticing that a tool is telling them less than it should. Put each one back to the design on the diagram.
What you will do
- Ticket 1: on the backup with nothing wrong
- Ticket 2: no jitter figures
- Ticket 3: a log with nothing in it
- Ticket 4: the management station is refused, and somebody else is not
- Ticket 5: half of every conversation
- Save it
New in this lab: SNMPv2c, SNMPv3, syslog, IP SLA, tracking, NetFlow.
How it is checked
Each of the 6 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 6 pass.
The lessons it follows
It opens after these, and uses what they teach:
Open the lab benchIt needs a computer: phones and tablets are not supported.
