So in this hands-on lab, what I'd love you to do is I'd love you to use loop
back addresses on all of our devices.
So R1 is 1111. R2 is 222. I've got routing protocol set up to make all that
reachable.
So I'd like you to set up R1 and R2 as stratum level one NTP servers.
So once you've done that, I'd then like you to set up R3 as an NTP client that
is using R1 as an NTP server.
Set up R4 as an NTP client that's using R2 as an NTP server. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Set up R4 as an NTP client that's using R2 as an NTP server.
And then, although I didn't demonstrate this in the lab, I'd like you to take R
8 and set it up as an NTP client to server one NUG,
which is at this address 192.168.1.100.
And it is running a flavor of NTP as part of the Windows server operating
system.
And then once you set up those three clients, you can use commands such as show
NTP status, show NTP associations,
show NTP associations detail.
And then once you've verified we have synchronization, I'd then like you to go
ahead and set up peering. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ahead and set up peering.
Peering between R3 and R4.
And once again, I'd like you to peer to each other's loopback addresses,
which provides some fault tolerance in the event we have a single physical
interface fail.
So my friend, those are the lab tasks.
Have some fun with the hands-on practice with NTP.
And when you are ready, and after you've done this lab, join me in the next
video
and we'll do a walkthrough of these tasks.