Skip to main content

CCNA Recap: NTP (Network Time Protocol)

This is a new series where I revisit CCNA topics for remembrance and explanation. A mix of old and new notes.

There are thousands of NTP servers around the world with access to atomic and GPS clocks (Very precise clocks), synchronised with Coordinated Universal Time.


NTP clients initiate a request with a server, and the client updates about once every 10 minutes on port 123.

NTP synchronize the clock times on computers and devices within a network. Why is this important? From updates to security (though NTP has its flaws), Timing matters.

It's possible to have Time of Day restrictions to network resources.

If you receive an alert that someone is on the network after hours, but your time isn't synchronized correctly, how do you know if someone is simply working past clock-out time after being logged in all day, or has truly logged in at 11 PM?






Older notes:

ntp server enables network time protocol function.

clock timezone [TMZ [In Relation to UTC]]
———————————
clock [season-time][TMZ] [recurring]
———————————
Use the ‘?’ to figure this one out

clock set HH:MM:SS D MONTH YEAR

NTP Server: Here’s the time. Adjust it yourself
NTP Clients: Ok, adjusting….adjusting….
NTP Client/Servers: Here’s the time you over here, meanwhile I’ll get my time as a client from this server over here. In a completely different direction

To be A NTP Clent
    * ntp server [xxx.xxx.xxx.xxx | hostname]
                * this IP / ho represents the server’s IP or hostname

Trusted clock source in a Cisco-only network, you tell a ntp router that “Hey, you are a trusted and valuable source,” by giving it the ntp master command.

show commands
* show ntp status
    * clock is synchronized
    * reference is X.X.X.X
    * Time and date
* show ntp associations
    * shows an ip address
    * * = the router has peered with said ip w/ NTP as an association





source: Old notes, SearchNetworking

EMPLOYERS: This is me reviewing things I have been tested on in the past.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory