The Precision Time Protocol (PTP), as defined in the IEEE 1588 standard, synchronizes with nanosecond accuracy the real-time clocks of the devices in a network. The clocks in are organized into a master-member hierarchy. PTP identifies the switch port that is connected to a device with the most precise clock. This clock is referred to as the master clock. All the other devices on the network synchronize their clocks with the master and are referred to as members. Constantly exchanged timing messages ensure continued synchronization.
NTP synchronizes the timekeeping among a set of distributed time servers and clients. This synchronization allows the events to be correlated when the system logs are created and the other time-specific events occur.
An NTP server must be accessible by the client switch. NTP runs over User Datagram Protocol (UDP), which runs over IP. NTP is documented in RFC 1305. All NTP communication uses Coordinated Universal Time (UTC), which is the same as Greenwich Mean Time. An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock that is attached to a time server. NTP distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two machines to within a millisecond of one another.
NTP uses a stratum to describe how many NTP hops away a machine is from an authoritative time source. A stratum 1 time server has a radio or atomic clock that is directly attached; a stratum 2 time server receives its time from a stratum 1 time server, and so on. A machine running NTP automatically chooses as its time source the machine with the lowest stratum number that it is configured to communicate with through NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
Hi,I've had below topology: So from RT1's perspective, if link RT1 - RT5 is the link to be protected, the P-space (RT1, Redlink) will be RT2? I can see the definition of P space of RT1 is the set of nodes that RT1 can reach as per pre-convergenc...
Cisco Champion Radio · S7|E30 Taming Your AI/ ML Workloads with Kubeflow
As organizations increasingly introduce machine learning (ML) capabilities to their existing products, their artificial intelligence (AI) projects and operations complexity g...
Cisco IOS-XE 17.3.1 – Catalyst Switching Updates
Table of Contents
Hardware Additions since IOS-XE 17.2.1
Key Summary Features
Platform and Infra Features
High Availability Features
Routing / MPLS / VPN Features