-
Notifications
You must be signed in to change notification settings - Fork 2
ntp
Thomas Mangin edited this page Apr 21, 2026
·
1 revision
Pre-Alpha. This page describes behavior that may change.
Ze includes an NTP client plugin for system clock synchronization. The plugin provides a clock readiness gate that other components (interface management, BFD) can check before making time-sensitive decisions.
NTP is configured as a plugin:
ntp {
enabled true;
server 0.pool.ntp.org;
server 1.pool.ntp.org;
}
The plugin synchronizes the system clock on startup and periodically thereafter.
The NTP plugin signals clock readiness via the event bus. Components that depend on accurate time (BFD timers, certificate validation) can wait for the clock to be synchronized before proceeding.
Unreviewed draft. This wiki was authored in bulk and has not been reviewed. File corrections on the issue tracker.
- Overview
- YANG Model
- Editor Workflow
- Archive and Rollback
- System
- Interfaces
- VRRP
- BFD
- FIB
- OSPF
- IS-IS
- MPLS / LDP / RSVP-TE
- RSVP-TE
- SRv6
- Static Routes
- Policy Routing
- Firewall
- Traffic Control
- Class of Service
- L2TP/PPP
- PPPoE
- VPP Data Plane
- RPKI
- IPsec VPN
- TACACS+ AAA
- RADIUS AAA
- AS112 DNS
- Authorization
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Flow Export
- DDoS Mitigation
- Anomaly Detection
- Health Checks
- Audit Trail
- Production Diagnostics
- Logging
- Operational Reports
- Healthcheck
- Self-Update
- Zero-Touch Provisioning
- MRT Analysis
- Upgrade and Restart
- Storage
- Policy
- Core
- Resilience
- Validation
- Capabilities
- Address Families
- Protocol
- Subsystems
- Infrastructure
- Route Server at an IXP
- Transit Edge with RPKI
- Public Looking Glass
- ExaBGP Migration Walkthrough
- FlowSpec Injection
- Chaos-Tested Peering
- AS Path Topology