Network Time Server Configuration Guide

BRIDZA

Table of Contents

• Unboxing and Network Connection
• Web UI Configuration
• GNSS Antenna Installation
• PTP Profile Configuration
• NTP Client Configuration
• Troubleshooting

1. Unboxing and Network Connection

1.1 Package Contents

1.2 Front Panel Overview

+------------------------------------------------------------------+
| [STATUS] [ALARM] [NTP] [PTP] [GNSS] | LCD DISPLAY |
| ● ○ ● ○ ● | 192.168.1.100 |
| | NTP: Active |
| [FUNC] [ENTER] | PTP: Master Mode |
| [ESC] [◄] [▼] [►] [▲] | GNSS: 12 Sats Locked |
+------------------------------------------------------------------+

LED Indicators:

1.3 Rear Panel Connectors

+-----------------------------------------------------------+
| [DC IN 12V] [ETH1] [ETH2] [USB] [USB] [GPIO] [GNSS] |
| ⚡ ◉◉ ◉◉ ◉◉ ◉◉ D-SUB SMA |
+-----------------------------------------------------------+

1.4 Network Connection Steps

• Connect Power: Attach 12V DC adapter
• Connect Ethernet: Cable from ETH1 to network switch
• Connect GNSS: Attach antenna cable to GNSS SMA port
• Power On: Press power button
• Wait for Boot: Approximately 60 seconds
• Check LCD: Should show IP address and status

1.5 Default Network Settings

2. Web UI Configuration

2.1 Accessing the Web Interface

• Open web browser
• Enter IP address (default: http://192.168.1.100)
• Login with credentials:

- Username: admin

- Password: admin (change immediately)

2.2 Network Settings

Path: Configuration → Network → Interfaces

┌─────────────────────────────────────────────────────────┐
│ Network Interfaces │
├─────────────────────────────────────────────────────────┤
│ Interface: ETH1 (Primary) │
│ ─────────────────────────────────────────────────────── │
│ Connection Type: [Static ▼] │
│ IP Address: [192.168.1.100] │
│ Subnet Mask: [255.255.255.0 ] │
│ Gateway: [192.168.1.1 ] │
│ Primary DNS: [8.8.8.8 ] │
│ Secondary DNS: [8.8.4.4 ] │
│ │
│ [x] Enable NTP on this interface │
│ [x] Enable PTP on this interface │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

2.3 NTP Configuration

Path: Configuration → NTP → Server

┌─────────────────────────────────────────────────────────┐
│ NTP Server Configuration │
├─────────────────────────────────────────────────────────┤
│ Enable NTP Server: [✓] │
│ │
│ Stratum Level: [2 ▼] (1-15, lower = higher priority) │
│ │
│ NTP Mode: [Unicast ▼] │
│ │
│ Maximum Peers: [5 ▼] │
│ │
│ Authentication: [Disabled ▼] │
│ └─ Options: Disabled | MD5 | SHA1 | NTS │
│ │
│ Leap Second Handling: [Insert ▼] │
│ └─ Options: Insert | Delete | None │
│ │
│ Query Interval: [64 seconds ▼] │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

2.4 PTP Configuration

Path: Configuration → PTP → Profiles

See Section 4 for detailed PTP profile settings.

2.5 GNSS Configuration

Path: Configuration → GNSS

┌─────────────────────────────────────────────────────────┐
│ GNSS Configuration │
├─────────────────────────────────────────────────────────┤
│ Enable GNSS: [✓] │
│ │
│ Constellation: [Multi-Constellation ▼] │
│ └─ GPS | GLONASS | Galileo | BeiDou | Multi-GNSS │
│ │
│ Disciplined Oscillator: [Rubidium ▼] │
│ └─ Internal OCXO | Internal Rubidium | External │
│ │
│ Discipline Mode: [Normal ▼] │
│ └─ Normal | Fast Lock | Holdover Only │
│ │
│ Antenna Cable Delay: [0] ns (enter if >10m cable) │
│ │
│ Elevation Mask: [10] degrees │
│ CN0 Threshold: [35] dB-Hz │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

3. GNSS Antenna Installation

3.1 Antenna Specifications

3.2 Installation Location Requirements

Ideal Location:

• Clear sky view: 360° azimuth, >10° elevation
• Minimum 3m from transmitting antennas
• Minimum 1m from metallic surfaces
• Away from heating/cooling vents
• Protected from water/snow accumulation

Avoid:

• Near radar or communication transmitters
• Under or near satellite dishes
• In elevator shafts or basement areas
• Near rotating structures

3.3 Cable Installation

Note: For cables >15m, use low-loss cable (LMR-400) or add inline amplifier.

3.4 Ground Installation (Survey Pin Mount)

• Drill 12mm hole for ground pin
• Insert ground pin securely
• Attach antenna base to pin
• Connect coaxial cable
• Apply silicone sealant around base
• Route cable with drip loop
• Connect to time server

3.5 Roof/Mast Installation

• Install mast or tripod mount
• Ensure mast is grounded
• Mount antenna with orientation marker (magnetic or arrow)
• Connect and weatherproof cable connections
• Ground cable shield at entry point

4. PTP Profile Configuration

4.1 PTP Profiles Overview

4.2 Default Profile Configuration

Path: Configuration → PTP → Profiles → Default

┌─────────────────────────────────────────────────────────┐
│ PTP Default Profile Configuration │
├─────────────────────────────────────────────────────────┤
│ Enable PTP: [✓] │
│ │
│ Profile: [Default (IEEE 1588-2008) ▼] │
│ │
│ Domain: [0 ▼] (0-255) │
│ │
│ Transport: [IPv4 ▼] │
│ └─ IPv4 | IPv6 | Ethernet │
│ │
│ Sync Interval: [1 ▼] seconds │
│ └─ Options: 1/128, 1/64, 1/32, 1/16, 1/8, 1/4, 1/2, 1 │
│ │
│ Announce Interval: [2 ▼] seconds │
│ └─ Options: 1, 2, 4, 8 seconds │
│ │
│ Delay Request: [1 ▼] seconds │
│ └─ Same as sync interval typically │
│ │
│ Priority1: [128] (0-255, lower = preferred) │
│ Priority2: [128] (0-255, lower = preferred) │
│ │
│ Clock Quality: │
│ Clock Class: [248] │
│ Clock Accuracy:[254 ▼] │
│ Offset Scaled Log Variance: [65535] │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

4.3 Telecom Profile (G.8265.1)

For telecom synchronization applications requiring enhanced performance.

┌─────────────────────────────────────────────────────────┐
│ PTP Telecom Profile Configuration │
├─────────────────────────────────────────────────────────┤
│ Enable PTP: [✓] │
│ │
│ Profile: [Telecom (ITU-T G.8265.1) ▼] │
│ │
│ Domain: [0 ▼] (0-3 for Telecom) │
│ │
│ Transport: [IPv4 ▼] │
│ │
│ Sync Interval: [1/16 ▼] seconds │
│ └─ For telecom: 1/16 or 1/8 recommended │
│ │
│ Announce Interval: [1 ▼] seconds │
│ │
│ Delay Request: [1/16 ▼] seconds │
│ │
│ Priority1: [128] (typically 128-136 for telecom) │
│ Priority2: [128] (set by local policy) │
│ │
│ Grandmaster Selection: [Profile-based ▼] │
│ └─ BMCA uses clock class and accuracy │
│ │
│ Unicast Negotiation: [✓] Enable │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

4.4 PTP as Master Configuration

┌─────────────────────────────────────────────────────────┐
│ PTP Master Mode │
├─────────────────────────────────────────────────────────┤
│ PTP Mode: [Master ▼] │
│ └─ Master | Slave | Boundary Clock │
│ │
│ Note: As Master, this device provides timing to slaves │
│ │
│ VLAN Tagging: [Disabled ▼] │
│ └─ Disabled | 802.1Q | QinQ │
│ VLAN ID: [100] │
│ │
│ DSCP Marking: [46] (EF PHB for telecom) │
│ │
│ [Apply] [Cancel] │
└─────────────────────────────────────────────────────────┘

4.5 PTP Performance Expectations

5. NTP Client Configuration

5.1 Linux NTP Client Configuration

Install NTP (if not installed):

# Ubuntu/Debian
sudo apt-get install ntp

# RHEL/CentOS
sudo yum install ntp

Configure /etc/ntp.conf:

# BRIDZA Time Server Configuration
server 192.168.1.100 iburst prefer

# Fallback servers (optional)
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst

# Drift file
driftfile /var/lib/ntp/ntp.drift

# Log directory
logfile /var/log/ntp.log

# Restrictions
restrict default nomodify notrap nopeer noquery
restrict 192.168.1.100 nomodify notrap noquery

# Allow time queries from local network
restrict 127.0.0.1
restrict ::1

Restart NTP:

sudo systemctl restart ntp

Verify Synchronization:

# Check synchronization status
ntpq -p

# Expected output:
# remote refid st t when poll reach delay offset jitter
# ==============================================================================
# *192.168.1.100 GPS 2 u 64 377 0.123 0.021 0.015
# +time.example.co .GPS. 1 u 64 377 15.234 0.123 0.045

# Check detailed timing
ntpdate -q 192.168.1.100

# Monitor continuously
ntpdc -c monlist

5.2 Windows NTP Configuration

Option 1: Using Registry (Command Prompt as Admin)

:: Add BRIDZA as NTP server
reg add "HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters" /v NtpServer /t REG_SZ /d "192.168.1.100,0x9" /f

:: Set announcement interval
reg add "HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient" /v SpecialPollInterval /t REG_DWORD /d 900 /f

:: Set to NTP mode
reg add "HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters" /v Type /t REG_SZ /d NTP /f

:: Force sync
w32tm /config /update
w32tm /resync /force

Option 2: Using PowerShell

# Set NTP server
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Parameters" -Name "NtpServer" -Value "192.168.1.100,0x9"

# Configure settings
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Config" -Name "AnnounceFlags" -Value 5
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient" -Name "SpecialPollInterval" -Value 900

# Restart and sync
Restart-Service W32Time
Get-WmiObject -Class Win32_OperatingSystem | select LastBootUpTime
w32tm /resync

Verify Windows NTP:

w32tm /query /status
w32tm /query /peers
w32tm /query /source

5.3 chrony Configuration (Modern Linux)

For systems using chrony instead of ntpd:

Install chrony:

# Ubuntu/Debian
sudo apt-get install chrony

# RHEL/CentOS
sudo yum install chrony

Configure /etc/chrony/chrony.conf:

# BRIDZA Time Server
server 192.168.1.100 iburst prefer

# Other NTP servers
pool pool.ntp.org iburst

# Record rate at which system gains/losses time
driftfile /var/lib/chrony/drift

# Allow NTP client access from local network
cmdallow 192.168.1.0/24

# Enable kernel synchronization
rtcsync

# Log directory
logdir /var/log/chrony

Commands:

# Restart chrony
sudo systemctl restart chrony

# Check status
chronyc sources
chronyc tracking

6. Troubleshooting

6.1 NTP Not Synchronizing

Diagnostic Commands:

# Check NTP service
systemctl status ntp

# Check peers
ntpq -p

# Manual query
ntpdate -q 192.168.1.100

# Check firewall
sudo iptables -L -n | grep 123

6.2 PTP Sync Accuracy Poor

Diagnostic Commands:

# Check PTP status (requires ptp4l)
sudo ptp4l -i eth0 -m -l 6

# Monitor sync offset
sudo pmc -i eth0 get CURRENT_DATA_SET

6.3 GNSS Not Locking

Web UI Status: Configuration → Status → GNSS

6.4 Web UI Not Accessible

Technical Support

For additional assistance:

• Email: [email protected]
• Documentation: https://rf.bridza.com/downloads
• Knowledge Base: https://rf.bridza.com/support

Document Version: 1.0 | Last Updated: 2025