Scribd
Upload
18 views3 pages

Untitled Document

The document discusses configuring NTP on routers R1 and R2 to synchronize their time with NTP server N1. It provides instructions to configure R1 and R2 as NTP clients to use N1 as their NTP server and verify that their clocks are correctly synchronized with N1.

Uploaded by

www.yuvan9580
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
18 views3 pages

Untitled Document

The document discusses configuring NTP on routers R1 and R2 to synchronize their time with NTP server N1. It provides instructions to configure R1 and R2 as NTP clients to use N1 as their NTP server and verify that their clocks are correctly synchronized with N1.

Uploaded by

www.yuvan9580
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Packet Tracer - Configure and Verify NTP

Addressing Table

Objectives
In this activity, you will configure NTP on R1 and R2 to allow time synchronization.

Background / Scenario
Network Time Protocol (NTP) synchronizes the time of day among a set of distributed time
servers and clients. While there are a number of applications that require synchronized time,
this lab will focus on correlating events that are listed in the system log and other time-specific
events from multiple network devices. NTP uses the User Datagram Protocol (UDP) as its
transport protocol. All NTP communications use Coordinated Universal Time (UTC).

An NTP server usually receives its time from an authoritative time source, such as an atomic
clock attached to a time server. The NTP server then distributes this time across the network.
NTP is extremely efficient. No more than one packet per minute is necessary to synchronize two
devices to within a millisecond of each other.

Instructions
Step 1: NTP Server
a. Server N1 is already configured as the NTP Server for this topology. Verify its configuration
under Services > NTP.

Open configuration window

b. From R1, ping N1 (209.165.200.225) to verify connectivity. The ping should be successful.

c. Repeat the ping to N1 from R2 to verify connectivity to N1.

Step 2: Configure the NTP Clients


Cisco devices can be configured to refer to an NTP server to use to synchronize their clocks. It
is important to keep time consistent among all devices. Configure R1 and R2 as NTP clients so
their clocks are synchronized. Both R1 and R2 will use N1 server as their NTP server.

a. Check the current NTP and clock settings as shown below:

R1# show ntp status


%NTP is not enabled.

R1# show clock detail

*0:1:53.745 UTC Mon Mar 1 1993

Time source is hardware calendar

b. Configure R1 and R2 as NTP Clients. Use the ntp server command to specify an NTP
server, as shown below:

R1# conf t

R1(config)# ntp server 209.165.200.225

c. Repeat this configuration on R2.

Step 3: Verify NTP settings


a. Check the clocks on R1 and R2 again to verify that they are synchronized:

R1# show clock detail

12:7:18.451 UTC Sat Oct 12 2019

Time source is NTP

Note: When working on physical routers, allow a few minutes before R1 and R2 clocks are
synchronized. With Packet Tracer you can use the Fast Forward Time button to speed up
synchronization.

Execute the same command on R2.

Are the clocks synchronized?


Yes. R1 and R2 have the same time as N1.

b. Check the NTP status and NTP associations by using the following commands to verify
NTP operation and configuration.

R1# show ntp status

Clock is synchronized, stratum 2, reference is 209.165.200.225

<Output omitted>
R1# show ntp associations

address ref clock st when poll reach delay offset disp

*~209.165.200.225127.127.1.1 1 11 32 377 9.00 4.00 0.24

* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy