SyncServer-S2xx User Guide

..........
SyncServer S200, S250, S250i
..................User Guide
..................Rev. G2, May 2015
..................Part Number: 997-01520-01
..................CD Number: 998-01520-01
.....
Page 2
Microsemi Customer Assistance

To find the Microsemi representative closest to your location, please visit Microsemi Sales
http://www.microsemi.com/sales-contacts/0 online.
To reach a Microsemi Customer Assistance Center, call one of the following numbers:
n
n
n
Worldwide Main Number: 1-408-428-7907

US Toll-free Number: 1-888-367-7966
Europe, Middle East & Africa: 49 700 32886435
Notices
Copyright
Copyright 2015 Microsemi, Inc.
All rights reserved.
Due to continued product development this information may change without notice. If you
find any errors in the documentation, please report them to us in writing. Microsemi, Inc.
does not warrant that this document is error-free.
Limited Product Warranty

Hardware and embedded software Depending on the product, for a period of one, or two
years from date of shipment by Microsemi, Microsemi warrants that all Products shall be free
from defects in design, material, and workmanship; shall conform to and perform in accordance with Microsemi's published specifications, if any; shall be free and clear of any liens and
encumbrances; and shall have good and valid title. This warranty will survive inspection,
acceptance, and payment by Buyer. Microsemi does not warrant that the operation of such
Products will be uninterrupted or error free. This warranty does not cover failures caused by
acts of God, electrical or environmental conditions; abuse, negligence, accident, loss or damage in transit; or improper site preparation.
This warranty shall be null and void in the event (i) Buyer or any third party attempts repair of
the goods without Microsemis advance written authorization, or (ii) defects are the result of
improper or inadequate maintenance by Buyer or third party; (iii) of damage to said goods by
Buyer or third party-supplied software, interfacing or supplies; (iv) of improper use (including
termination of non-certified third party equipment on Microsemis proprietary interfaces and
operation outside of the product's specifications) by Buyer or third party; or (v) the goods are
shipped to any country other than that originally specified in the Buyer's purchase order.
Goods not meeting the foregoing warranty will be repaired or replaced, at Microsemis
option, upon return to Microsemis factory freight prepaid; provided, however that Buyer has
first obtained a return materials authorization number ("RMA Number") from Microsemi
authorizing such return. The RMA Number shall be placed on the exterior packaging of all
returns. Microsemi will pay shipping costs to return repaired or replacement goods to Buyer.
Microsemi reserves the right to disallow a warranty claim following an inspection of returned
product. When a warranty claim is questioned or disallowed, Microsemi will contact Buyer by
telephone or in writing to resolve the problem.
Limitation of Liability
The remedies provided herein are the Buyers sole and exclusive remedies. In no event or circumstances will Microsemi be liable to Buyer for indirect, special, incidental or consequential
damages, including without limitation, loss of revenues or profits, business interruption costs,
loss of data or software restoration, or damages relating to Buyers procurement of substitute products or services. Except for liability for personal injury or property damage arising
from Microsemis negligence or willful misconduct, in no event will Microsemis total cumulative liability in connection with any order hereunder or Microsemis Goods, from all causes
of action of any kind, including tort, contract, negligence, strict liability and breach of warranty, exceed the total amount paid by Buyer hereunder. SOME JURISDICTIONS DO NOT
ALLOW CERTAIN LIMITATIONS OR EXCLUSIONS OF LIABILITY, SO THE ABOVE
LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO ALL BUYERS.
Contact Information
Microsemi, Inc.
3870 N.1st Street
San Jose, CA 95134
For Sales, Technical Support, and Return Materials Authorization, please see Microsemi
Customer Assistance (on page 3).
Table of Contents
Microsemi Customer Assistance
Notices
Quick Start Guide
13
Configuring the SyncServer

Status LEDs
Halting the SyncServer
13
14
15
Product Overview
17
Key Features and Benefits

Software Features
SyncServer Signal Feature Comparison
Web Interface
17
18
18
19
Login
Properties of User Names and Passwords
STATUS Tab
STATUS - General
STATUS - Network
STATUS - Timing
STATUS - GPS
STATUS - NTP
STATUS - Alarms
NETWORK Tab
NETWORK - Ethernet
Port Bonding
NETWORK - SNMP
NETWORK - SNMP Traps
NETWORK - Ping
NTP Tab
NTP - Sysinfo
RESTART button
NTP - Assoc
NTP - Config
RESTART button
NTP - MD5 Keys
NTP - Prefs
TIMING Tab
20
20
22
22
22
23
23
25
25
27
27
30
31
32
33
34
34
34
35
36
39
39
40
42
TIMING - Time Zone

TIMING - HW Clock
Steering with a Frequency Reference
Frequency Reference - Power-Down / Reboot
TIMING - Holdover
TIMING - Sysplex
REFERENCES Tab
REFERENCES - GPS
REFERENCES - IRIG-B
SYSTEM Tab
SYSTEM - General
SYSTEM - Upgrade
SYSTEM - Factory Reset
ADMIN Tab
ADMIN - Web
ADMIN - Users
ADMIN - Alarms
Alarm Descriptions
ADMIN - Logs Config
SERVICES Tab
SERVICES - Startup
SERVICES - HTTP
SERVICES - SSH
SERVICES - Email
LOGS Tab
WIZARDS Tab
WIZARDS - 1st Setup
WIZARDS - NTP
WIZARDS - SNMP
WIZARDS - Backup
WIZARDS - Restore
WIZARDS - Upgrade
HELP Tab
HELP - Contacts
HELP - Docs
Keypad/Display Interface
42
42
44
45
45
47
50
50
51
52
52
53
53
55
55
56
57
59
61
64
64
65
66
67
68
70
70
70
70
70
71
71
72
72
72
73
TIME Button
STATUS Button
MENU Button
73
74
76
Command Line Interface
79
Specifications
83
Status LEDs
84
Keypad/Display
USB Ports
VAC Power Supply
VDC Power Supply
Timing Holdover
Accuracy & Stability
GPS Receiver
Safety Standards
EMC Standards
VCCI Compliance Information
Environmental
Maintainability
CAUTION: Lithium Battery
Failure Detection and Reporting
CE/WEEE/RoHS Conformance
Shock and Vibration
Console RS-232 Port
1PPS Out
1PPS In
10MHz Out
10MHz In
IRIG-B Out
IRIG-B In
Sysplex Out
Network Ports
Network Protocols
Web Interface Browser Compatibility
84
85
85
85
85
86
86
87
87
88
88
88
89
89
89
90
91
91
92
92
92
93
93
94
95
95
96
Tasks
97
Installation Guide
Unpacking
Rack Mounting
Grounding the SyncServer
WARNING: Grounding
Connecting VAC Power
CAUTION: VAC Power
Connecting VDC Power
WARNING: VDC Power
Using GPS
Safety Considerations
Selecting a Site for the Antenna
Installing the GPS Antenna
Operating in "Window Mode"
Verifying the GPS Installation
Distance Between Antenna and Receiver
Configuring GPS for Various Conditions
97
97
98
98
98
98
99
99
99
100
100
100
102
102
104
105
106
Upgrading System Software

Adding NTP Servers to the NTP Associations List
Recovering a Password
Configuring LAN1
CAUTION: DHCP Not Available
Logging in to the Web Interface
Using the 1st Setup Wizard
Configuring the Network Ports
Adding Server Associations
Using the Other Input References
107
109
110
111
111
112
112
112
112
113
115
Troubleshooting
Passwords
Web Interface Troubleshooting
Alarms and Notification
Factory Default Settings for Alarms
NTP Clients
Backing Up/Restoring Configurations
Creating a Backup File
Restoring from a Backup File
Restoring the Factory Default Configuration
Configuring SNMP
Transferring Configurations
Removing the Top Cover
Replacing the Battery
Software
115
115
116
116
116
117
118
118
119
119
120
122
122
122
123
125
Apache Software License

NTP Software License
GNU General Public License
Net-SNMP Software License
125
134
137
143
Listing of Memory Devices
145
ETX Module
86-611xPCB
MC9S12DG256 (U2)
145
145
146
Determining Latitude and Longitude
147
United States
Canada
International
147
162
164
10
Factory Default Settings
171
Login - default settings

Network Ports - default settings
SNMP
NTP
MD5 Keys
NTP Override Behaviour
TIMING
Time Zone
Hardware Clock Configuration
Holdover
Sysplex
REFERENCES
GPS
IRIG-B
SYSTEM
ADMIN
Login Webpage Configuration
Users
Alarms
Logs Config
SERVICES
Startup
HTTP
SSH
Email
171
171
171
171
172
172
172
172
172
172
173
173
173
173
173
173
173
174
174
175
176
176
176
177
177
Glossary
179
Hardware Clock
Introduction to GPS
Leap Indicator
NTP Daemon
Software Clock
Stratum
Timing Engine
Timing Source
UTC
179
179
180
180
180
181
181
181
181
Index
183
Appendix A: SNMP MIB
189
11
Quick Start Guide

This topic guides the user on how to:
n
n
n
Configure a SyncServer (see "Configuring the SyncServer" on page 13) that still has
its original factory configuration.
Read the status LEDs on the front panel.
Shut the SyncServer down correctly.
This topic is included in the main User Guide. For more information about the features and
tasks described here, consult the following sections in the main User Guide:
n
n
n
n
Web Interface (on page 19)

Keypad/Display Interface (on page 73)
Specifications (on page 83)
Tasks (on page 97)

Recommended Tasks
GPS antennas not rated for 12 VDC power may be damaged if connected to the SyncServer.
1. Mount the standard L1 GPS antenna (supplied) in a location that offers good visibility of
GPS satellites, such as a rooftop or outdoor antenna mast with wide open views of the
sky and horizon. Avoid obstructions and sources of Radio Frequency Interference.
Observe building codes and regulations. Also see Using GPS (on page 100) and
WARNING: GPS Antenna (see "Safety Considerations" on page 100).
2. On the rear panel:
n Connect the GPS antenna cable (supplied) to the GPS Ant connector.
n Connect LAN1 and any of the other network ports to the network.
n Consult Warnings and Cautions for safety information regarding grounding and
power.
n Connect the power and turn the power switch on.
3. Using the front panel keypad:
n Configure LAN1 with a static IP address using the MENU button and 1) LAN1.
n View the LAN1 IP address by pressing the STATUS button repeatedly until the
LAN1 STATUS screen is shown.
4. Go to the SyncServer Login page by entering the LAN1 IP address as the URL in Internet
Explorer.
5. Log in. The user name is "admin". The password is "symmetricom".
6. Configure the SyncServer using WIZARDS - 1st Setup. Select the following options:
997-01520-02 Rev. G2.......................................................................... Page 13
Quick Start Guide

"Configure Password Recovery" (Ask the IT department for the IP address of the
SMTP server).
n "Send test mail when finished"
n "Set Local Time Zone"
7. Configure the remaining network ports using NETWORK - Ethernet.
n Assign static IP addresses.
n Protect LAN1 and the other ports from unauthorized IP addresses or address
ranges using the Allowed Access feature.
8. Configure the NTP clients on your network with the IP address(es) of the SyncServer's
network ports.
n
The SyncServer is providing synchronized time to the network when the SYNC LED (front
panel) is orange or green.
Optional Tasks
In the web interface:
n
n
n
n
n
Connect any other Input References to the rear panel and configure them using the
pages under the REFERENCES section.
Use the NTP Config page to synchronize the SyncServer with any other NTP servers.
Use WIZARDS - SNMP to set up alarm notification by SNMP.
Use SERVICES - Email to set up alarm notification by email.
When the SyncServer is completely configured, use WIZARDS - Backup to save a backup
file of the configuration to a safe location. Write the location of the backup file on this printed document and store it in a location that is easy to find.
Status LEDs
The four tricolor LEDs provide the following status information:
Red
Sync
Orange
SyncServer is not
SyncServer is synsynchronized to a ref- chronized to a remote
erence.
NTP server.
NTP Stratum 16.
NTP Stratum 2-15.
Network Link failure on the

NTP
Alarm
Link failure on the

LAN1.
LAN2, or LAN3.
>3200 NTP packets > 2000 packets per
per second.
second.
Major Alarm.
Minor Alarm.
Green
Dark
SyncServer is synchronized to an Input

Reference.
NTP Stratum 1.
Power off.
All configured ports

Power off.
operational.
NTP activity within the No NTP activlast second.
ity in the last
second.
No Current/Enabled
Power off.
Alarms.
See the Troubleshooting (on page 115) topics to resolve problems with Red and Orange
LEDs.
Page 14..........................................................................997-01520-02 Rev. G2

Also see Stratum (on page 181).

Microsemi recommends shutting the operating system down before removing the power.
Using the keypad/display interface:
1.
2.
3.
4.
5.
Press the MENU button.

Select 3) Shutdown.
Select 1) Yes.
Press the ENTER button.
When the display shows "System Stopped - OK to Turn Power Off Now!" turn the power
off.
Or, using the web interface:

1. Go to the SERVICES - Startup page.
2. Select Halt and click the APPLY button.
3. Wait approximately 30 seconds before removing power.
997-01520-02 Rev. G2.......................................................................... Page 15
Product Overview
The SyncServer Network Time Server offers the following protocols for synchronizing equipment over a network:
n
n
n
n
n
NTP
SNTP
Time (TCP and UDP versions)
Daytime (TCP and UDP versions)
Sysplex Output (dedicated port)
These protocols are capable of synchronizing computers, servers, and networking equipment on an enterprise-scale network to within milliseconds of official UTC time. This degree
of synchronization is desirable for precise time-stamping of events and data correlation.
See also: SyncServer signal feature comparison (on page 18)
In This Chapter
Software Features

Key Features
n
n
n
n
n
n
n
n
n
n
n
n
Ultra High-Bandwidth NTP Time Server

Stratum 1 Operation via GPS Satellites
Three (3) 10Base-T/100Base-TX Ports
Independent Time References: GPS, IRIG-B, 1PPS, 10MHz (S250)
Versatile Timing Outputs: IRIG-B, IRIG-B (Legacy Truetime), IRIG-B with IEEE 1344
Extension, 1PPS, 10MHz, Sysplex (S250)
Stratum 2 Operation via NTP Servers
MD5 Authentication
Secure Web-Based Management
SSH, SSL, SNMP, Custom MIB, HTTPS, Telnet, and More
IPv6 and IPv4 Compatible
Nanosecond Time Accuracy to UTC
Rubidium & OCXO Oscillator Upgrades
Key Benefits
n
n
Synchronize Hundreds of Thousands of Client, Server & Workstation Clocks

Very Reliable and Secure Source of Time for Your Network
997-01520-02 Rev. G2.......................................................................... Page 17
17
18
18
Product Overview
n
n
n
n
n
Multiple NTP Ports for Easy Network Configuration and Adaptation

Extremely Accurate Time Source for Network Synchronization
Enhanced Network & Security Features
Automatic Reference Selection between, GPS, IRIG-B, 1PPS and 10MHz
Intuitive Web Interface for Easy Control & Maintenance
Software Features
Manageability
n
n
n
n
Copy a SyncServer configuration to multiple units.

Web-based user interface.
Simple, intuitive, Keypad/Display and Command Line Interface.
Easy set up and configuration.
Security
n
n
n
Encrypted username password.

Lock down the LAN1 network port.
Lock down HTTPD.

Use the following table to compare signal features between different models of SyncServer.
GPS
1PPS
10 MHz
IRIG-B
S200
X
S250
X
X
X
X
S250i
X
X
X
Page 18..........................................................................997-01520-02 Rev. G2
Web Interface
This section provides a topic for each page in the web interface, with an explanation of each
field, notes, and links to related topics.
Login
STATUS Tab
NETWORK Tab
NTP Tab
TIMING Tab
REFERENCES Tab
SYSTEM Tab
ADMIN Tab
SERVICES Tab
LOGS Tab
WIZARDS Tab
HELP Tab
997-01520-02 Rev. G2.......................................................................... Page 19
20
22
27
34
42
50
52
55
64
68
70
72
Web Interface
Login
Use the Login page to:
n
n
n
Log in to the SyncServer's web interface.

Recover lost passwords.
View and configure the system status. Use the ADMIN - Web (on page 55) page to configure the status information on the Login page.
The Login page includes the following elements:

n
n
n
Username: Enter the username here. (Factory default: "admin")

Password: Enter the corresponding password here. (Factory default: "symmetricom")
Secure: Opens an encrypted web session (HTTPS, port 443). For this feature to be available, the user must enable it by using the SERVICES - HTTP page.
Recover Password: Prompts the user to answer a password recovery question. If the user
answers correctly, the SyncServer resets the password to a random string and emails it
to the user's email address. For this feature to be available, the user must enable it using
the ADMIN - Users or WIZARDS - 1st Setup pages. Enabling this feature requires:
n Selecting and giving an answer to a recovery question.
n Providing an email address
n Providing SMTP Gateway configuration settings.
Also see Recovering a Password (on page 110)
PropertiesofUserNamesandPasswords
Usernames
Quantity & Length
There is an upper limit of 32 individual users, each username has a maximum of 32 characters in length.
Character set (Charset)
Each username is limited to the following printable ASCII characters:
n
n
n
n
n
n
n
Upper case letters {A-Z}

Lower case letters {a-z}
Numbers {0-9}
Period {.}
Dash {-}
Underscore {_}
Plus {+}
Usernames may NOT contain any of the following:
Page 20..........................................................................997-01520-02 Rev. G2
Login
n
n
n
n
n
n
Standard ASCII keyboard characters not described above, i.e. ! @ # $% ^ & * () = {} [] |

\;:'"<>?,/
Grave accent {`}
Tilde {~}
Whitespace characters (space, tab, linefeed, carriage-return, formfeed, vertical-tab etc.)
Non-ASCII characters
Non-printable characters
Passwords
Length
The password can have a maximum of 64 characters in length.
Character set (Charset)
Passwords must contain, at minimum, either a mix of upper and lowercase letters, or a mix of
letters and numbers.
Passwords are limited to the following printable ASCII characters:
n
n
n
n
n
Upper case letters {A-Z}

Lower case letters {a-z}
Numbers {0-9}
Tilde {~}
Most standard ASCII keyboard symbols, i.e. ! @ # $% ^ & * () _ - = {} [] | : ; " < > , . ? /
Passwords may NOT be all-lowercase, all-uppercase, all-numeric, or match the username.

They additionally may NOT contain any of the following:
n
n
n
n
n
n
n
Single-quote / apostrophe {'}

Grave accent {`}
Plus {+}
Backslash {\}
Whitespace characters (space, tab, linefeed, carriage-return, formfeed, vertical-tab etc.)
Non-ASCII characters
Non-printable characters
997-01520-02 Rev. G2.......................................................................... Page 21
Web Interface
STATUS Tab
Select a topic from below to learn more about the STATUS features of the Web Interface:
STATUS- General
Overall System Information
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
Hostname: The network hostname of the SyncServer, which can be configured on the
SYSTEM - General web page.
Model: The model number of the SyncServer.
Serial Number: The unique serial number of the SyncServer.
Local Time: The local time, determined by the time zone setting on the TIMING - Time Zone
web page.
Release Version: The system release version.
Software Version: The software version.
Hardware Clock Version: The version of the software on the Hardware Clock.
Up Time: The time elapsed since the operating system started.
Load Average: A figure of merit for the operating system load for the previous 1, 5, and
15 minutes (left to right).
Memory Used (Mbyte): The amount of memory occupied by the system.
Memory Free (Mbyte): The amount of free memory remaining.
Flash: The type of compact flash card installed.
CPU Vendor: The CPU vendor/manufacturer.
Model: The CPU model.
Number: The CPU number.
STATUS- Network
Network Status for each of the SyncServer's network ports:
n
n
The name of the Port.

The following Address information for each network port:
n mac: The MAC Address.
n v4: The IPv4 Address, if used.
n v6 link: The IPv6 Address, if used.
The State of the physical network port device (not of the connection). An "Up Arrow"
means it is "running". A "Down Arrow" means it is "not running".
Management Port DNS Servers: Both user-entered and DHCP-assigned DNS Server
addresses that are available from the LAN1 port.
The SyncServer requires at least one valid DNS server to resolve domain names, which
may be used in NTP associations, and SMTP gateways (email). Without a DNS server, any
function that uses a DNS name instead of an IP address may be affected. These can include
NTP, password recovery, and email notification of alarms.
Page 22..........................................................................997-01520-02 Rev. G2
STATUS Tab
See Network Port default settings (see "Network Ports - default settings" on page 171)
STATUS- Timing
Hardware Clock Status
Current Sync Source: The Input Reference currently used by the Hardware Clock. Consult the
TIMING - HW Clock topic for more information.
Hardware Clock Time: The time according to the Hardware Clock.
Hardware Clock Status: "Locked" means the Hardware Clock is synchronized to one of its references, or to the internal oscillator in "Holdover". "Unlocked" means the Hardware Clock
doesn't have an Input Reference and the Holdover period has expired. Also see TIMING HW Clock and TIMING - Holdover (on page 45).
Oscillator Type: The type of the oscillator installed in the Hardware Clock for operation and holdover.
For each of the following Input Status lines, "Locked" means that the reference is valid and
can be selected by the Hardware Clock. "Unlocked" means the reference is not valid, and is
therefore not available for use by the Hardware Clock. Also see TIMING - HW Clock to
arrange the priority of the Input References.
Some of these references are options or are only available in specific SyncServer models.
(Consult Product Overview (on page 17) for more information about features and models):
n
n
n
n
n
GPS Input Status

IRIG-B Input Status
1PPS Input Status (see note below)
10MHz Input Status (see note below)
Leap Warning: The state of the Leap Indicator (on page 180) as reported by the current
input reference.
Also see
n
SyncServer signal feature comparison (on page 18) to see the available source signals for each model of SyncServer.
Hardware Clock Configuration (on page 172) default settings
STATUS- GPS
GPS Receiver Operation
This page displays the status of the GPS Receiver.
See SyncServer signal feature comparison (on page 18) to see the available source signals for each model of SyncServer.
997-01520-02 Rev. G2.......................................................................... Page 23
Web Interface
Receiver Description: "GPS" indicates the presence of a 12-channel GPS receiver.
Receiver Status:
n
n
n
n
n
n
Receiver Down: The Hardware Clock can't communicate with the receiver.
Unknown Mode: An undefined mode of the GPS receiver.
Acquiring Signal: The receiver is attempting to track a GPS signal.
Bad Geometry: The geometry of the tracked satellites is unsatisfactory for a position solution.
Propagate Mode: A position estimation mode used in highly dynamic environments.
2d Solution: The receiver is able to perform position fixes for latitude and longitude but
does not have enough satellites for altitude.
3d Solution: The receiver is now able to perform position fixes for latitude, longitude and
altitude.
Position Hold: Position fixes are no longer attempted, and the surveyed or user-entered
position is used.
Time Valid: The receiver has valid timing information from GPS satellites (including GPSUTC Offset and Leap Indicator). If the GPS receiver and antenna are set up correctly, the
receiver status should eventually reach and remain in this state.
Mode:
Survey: The receiver is surveying and averaging its position. When it has finished surveying, the receiver switches to Position Hold mode. Survey mode and Position Hold
mode are appropriate for static applications, such as a typical server room environment.
This is the default mode when the SyncServer starts.
n Dynamic: The GPS receiver surveys continuously to determine its position and doesn't
switch to another mode. This mode must be initiated by a user, and is appropriate for
mobile applications such as ships, land vehicles, and aircraft. The degree of accuracy this
mode offers is fine for NTP time over networks, but is less than optimal for the timing outputs available on some SyncServer models.
n Position Hold: The GPS receiver has completed Survey mode and switched to this
mode, or the user has manually entered a position and "forced" it into this mode. The
accuracy and stability of the SyncServer's timing outputs are optimal when the receiver
has its exact position and is in this mode.
Antenna Cable Delay (nS):
n
The user-configured value (on the REFERENCES - GPS page) to compensate for GPS signal
propagation from the antenna along the length of the cable to the receiver.
Antenna Status:
The GPS receiver supplies power to the GPS antenna through the antenna cable. It also
monitors the current to that circuit to detect open or short circuits.
n
n
Good: The current to the GPS antenna and cable is normal.

Open:The current is too low. The GPS antenna or cable is probably disconnected or
broken. Some splitters may cause this condition as well.
Short: The current is too high. The GPS antenna or cable probably has a short circuit.
Page 24..........................................................................997-01520-02 Rev. G2
STATUS Tab
Position: The latitude and longitude of the GPS antenna in degrees, minutes, and fractional
seconds. Referenced to WGS-84.
Altitude: The altitude of the antenna in meters. Referenced to WGS-84.
Satellites: The list of GPS satellites visible to the receiver:
n
n
n
Sat Number: The GPS satellite's Satellite Vehicle (SV) number, a unique identification
number
Signal: The relative strength of the GPS signal (dBW = decibels relative to 1 Watt).
Status: "Current" means that the receiver is using the GPS signal in its timing solution.
"Tracked" means the receiver is tracking the signal, but isn't using it in the timing solution.
See GPS (on page 173) default settings
STATUS- NTP
This page displays the status of the NTP Server.
Values are displayed for:
n
n
n
n
n
n
n
n
n
n
n
n
n
n
system peer
system peer mode
leap indicator
stratum
precision
root distance
root dispersion
reference ID
reference time
system flags
jitter
stability
broadcast delay
authdelay
See default settings:

n
n
NTP (on page 171)

NTP Override Behaviour (on page 172)
STATUS- Alarms
Current Major or Minor Alarms
Alarms with Severity set to:
n
n
n
Major are displayed in red text.

Minor are displayed in orange text.
Notify are not displayed.
997-01520-02 Rev. G2.......................................................................... Page 25
Web Interface
Alarms can be configured using the ADMIN - Alarms page.
For each listing:
Time: The local date and time at which the alarm was raised.
Severity: The severity of the alarm event (Major/Minor).
Name: The name of the alarm, from the list of alarms on the ADMIN - Alarms page.
See Alarms (on page 174) default settings
Page 26..........................................................................997-01520-02 Rev. G2
NETWORK Tab
NETWORK Tab
Select a topic from below to learn more about the NETWORK features of the Web Interface:
NETWORK-Ethernet
Use this page to get status and configure Ethernet LAN port network settings, including DNS
servers.
Ethernet Port Configuration

Edit the network port configuration and view network port status.
EDIT: Clicking this button opens a dialog box for configuring the network port.
Pending Changes: A check mark indicates that settings have changed, reminding the user
to click the APPLY button.
Port: The name of the network port.
IP Address: The port's MAC, IPv4, and/or IPv6 network addresses.
Usage: These icons summarize information about the port:
n
n
n
n
n
(Checkmark): The user has changed the configuration, but hasn't clicked the APPLY
button at the bottom of the page yet.
(Management Port): This network port is configured as the management port (web
interface, SNMP, email, DNS).
(Up Arrow): The physical network port is enabled and functioning (does not indicate a
valid physical connection or configuration).
(DHCP): The network configuration is automatic via DHCP
(Question Mark): Status unknown - usually when there are pending changes.
(Number "6"): Uses IPv6
(Letter "B"): Configured for bonding with another port in a redundant pair.
DNS Servers
The DNS Server fields display the IP addresses of Domain Name Service (DNS) servers.
The SyncServer requires a valid DNS server address to resolve domain names. If a DNS
server isn't provided, NTP associations (NTP - Config) and the SMTP Gateway
(SERVICES - Email) must be specified using an IP address. DNS messages are only communicated through LAN1 port. The specified DNS servers must be reachable from the LAN1
port.
n
Management Port User DNS Servers: Manually enter one or more DNS Server IP
addresses here, if not supplied by DHCP.
Management Port DHCP DNS Servers (Read Only): If LAN1 has DHCP enabled,
and DHCP is configured to supply DNS server addresses, displays the DNS server IP
addresses supplied by DHCP. These values are not user-editable.
997-01520-02 Rev. G2.......................................................................... Page 27
Web Interface
Note: If the SMTP Gateway (which supports Password Recovery and Email Notification of
Alarms) and NTP associations are addressed using domain names, a valid DNS server
address must be supplied to the SyncServer.
Network Port Configuration

To edit the settings for a network port, click the corresponding EDIT button on the
NETWORK - Ethernet page. This opens a dialog box titled with the name of the port followed by "Configuration".
To apply configuration changes, click APPLY buttons on both this configuration window and
later on the NETWORK - Ethernet page.
Connection Mode:
n
n
Static: A user must configure the network port manually.

DHCP: A DHCP server will automatically configure the network port when changes are
applied. Not available for IPv6.
Disabled: This disables the network port.
Note: If the Connection Mode is DHCP and the lease expires or the SyncServer reboots, a
DHCP server could assign a new IP address to the SyncServers network port. If this occurs
with the LAN1 port, use the STATUS button on the front panel to obtain the new IP address.
Furthermore, if it occurs to a network port servicing NTP requests, NTP clients will no longer
be able to get a response from that port. In that case, the NTP clients would have to use an
alternate NTP source or become unsynchronized. For this reason, Microsemi recommends
using static IP addresses, only using DHCP for convenience during temporary installations.
IP Version:
n IPv4: The port uses IPv4 exclusively. (Static or DHCP)
n IPv6: The port uses IPv6 exclusively. The user must enter a static IPv6 address.
IP Address: The port's IPv4 address (e.g., "192.168.0.100") or IPv6 address(es) with
scope (e.g., fe80::2a0:6dff:fe00:10).
Mask: The port's IPv4 subnet mask (e.g., "255.255.255.0"). With IPv6, the mask is the
length of the prefix.defined in CIDR format (Classless Inter Domain Routing). Typically, the
IPv6 mask is 64.
Note: The SyncServer does not support masks on IPv6 gateway entry. While the user interface will accept/display a user entered mask, such as /64 for the IPv6 gateway, the underlying software checks for the entered mask and removes it, before sending the unmasked
IPv6 gateway address down to the lower level Linux system components to configure the network interface.
Gateway: The port's IPv4 or IPv6 gateway (e.g., "192.168.0.1"). This is an optional configuration parameter.
Redundant: Bonds LAN3 to LAN2 as virtual device with a single network address.
n
n
Active: The Active port handles network traffic. LAN2 is "Active" by default.
Backup: The Backup port handles network traffic if the connection to the Active port fails.
LAN3 is the "Backup" port by default.
Page 28..........................................................................997-01520-02 Rev. G2
NETWORK Tab
Scenario #1
If the connection to LAN2 fails, LAN2 becomes backup and LAN3 becomes active. After
repairing the connection, the user can manually reconfigure LAN2 as the Active port. While
LAN3 is working, LAN2 will remain as backup. It is only if and when LAN3 fails, LAN2 will
become Active. LAN2 does not automatically replace LAN3 while LAN3 is working correctly.
Reconfigure LAN2 as the Active port:
1. In the "LAN2 Configuration" window, select the "Redundant" checkbox, select "Active",
and then click the APPLY button.
2. On the NETWORK - Ethernet page, click the APPLY button.
To release a redundant bond, deselect the "Redundant" checkbox and apply the changes. If
the bond doesn't release, reboot the SyncServer.
Scenario #2
Following scenario #1, the backup LAN2 is repaired and available again to be the Active
port. If LAN3 now fails, LAN2 will takeover as the Active port.
Scenario #3
Following scenario #1, the backup LAN2 is not repaired, and now LAN3 fails. Connections
are not available.
For more information see Port Bonding (on page 30)
Allowed Access: Restricts the LAN port to access by specified IP addresses or address
ranges. If the user leaves this field blank, the LAN port accepts connections from any IP
address. Allowed Access applies to all forms of network traffic, including NTP and HTTP connections. Reconfiguring the IP address of the LAN port erases the Allowed Access list.
The user can specify address ranges by setting the IP address followed by the mask prefix
length, as described RFC 1518 and RFC 1519 for Classless Interdomain Routing. The
mask prefix length specifies the number of masked bits starting from the left-most position. For example, to allow access from the network represented by 192.168.0.0,
255.255.0.0, the user would enter 192.168.0.0/16. In other words, the first 16 bits of the
address, 192.168, are masked bits representing the network address The remaining bits are
host address which is set to 0.
Note: When configuring Allowed Access, take care to avoid blocking DNS, HTTP, NTP,
SMTP, SNMP, and SSH traffic.
Side Effects
Applying changes to the Ethernet port configuration restarts the NTP and xinetd daemons
(services). During that time:
n
n
The NTP daemon, NTP stratum, web interface are temporarily unavailable.
The Status LEDs, NTP stratum, and Alarms change states.
997-01520-02 Rev. G2.......................................................................... Page 29
Web Interface
Cables need to be attached to IPv6 configured ports

The NTP daemon rescans all interface ports every five minutes. If a cable is not attached to
an IPv6 configured port when the network settings are applied, the NTP daemon will not be
able to bind to that IPv6 port. If a cable is attached later to the IPv6 configured port, up to five
minutes can pass before the next rescan. At the time of the next rescan, the NTP daemon
would then be able to bind the port, and respond to NTP packets.
The solution to this behavior is to have the cable connected to the SyncServer IPv6 configured
port before applying the network settings.
Port Bonding
Setting-up Port Bonding (LAN2 and LAN3 not previously configured):
1. On the NETWORK->Ethernet page, edit LAN2 and configure as desired. Select the
"Redundant" checkbox, and choose "Active". Click Apply.
2. When the LAN2 edit window closes, click Apply on the NETWORK->Ethernet page.
LAN3 is now activated for Port Bonding, and shares the network configuration information you entered for LAN2.
Setting-up Port Bonding (LAN2 and LAN3 must be previously configured):

1. On the NETWORK->Ethernet page, edit either LAN2 or LAN3. Select the "Redundant"
checkbox, and choose "Active" or "Backup". Click Apply.
2. When the LAN Configuration edit window closes, click Apply on the NETWORK->Ethernet page. Port Bonding is now active.
NOTE: Selecting "Backup" automatically sets the opposite interface (LAN2 or LAN3) to "Active". Any previously assigned network settings for the Backup port are erased (because that
interface is now sharing settings with the "Active" port).
To Release Port Bonding:

1. On the NETWORK->Ethernet page, edit LAN2 (or LAN3), and deselect the "Redundant" checkbox. Make any other necessary changes (IP Address, etc.), then click Apply.
2. On the NETWORK->Ethernet page, edit LAN3 (or LAN2) to make any desired configuration changes, if any, then click Apply.
3. Reboot the SyncServer.
NOTE: When releasing Port Bonding, you will need to reassign the network settings of the
interface that was previously the "Backup" port.
Page 30..........................................................................997-01520-02 Rev. G2
NETWORK Tab
NETWORK-SNMP
This page provides configuration of basic SNMP settings and the creation of SNMPv3 users.
Basic Configuration
Establish the identity and community membership of the device.
sysLocation: Identify the location of the SyncServer (e.g. Server Room A, Company Division B, etc). Used by network management consoles.
sysName: Provide the SyncServer with a unique name. (This is distinct and separate from
"hostname" on the SYSTEM - General and STATUS - General pages.) Used by network
management consoles.
sysContact: The name of the individual responsible for the SyncServer. Used by network
management consoles.
Read Community: The SNMP read community string. The string must be provided for
SNMP v1/v2c GETS/WALKS to gain access.
Write Community: The SNMP write community string.
Note: At this time, the SyncServer does not support any writable SNMP variables.
V3 Users
SNMP user names are separate and distinct from the access control list usernames used to
log in to the SyncServer's user interfaces. SNMP user names are used by the network management software.
This is the list of SNMP v3 users. To delete a user, select the checkbox for a user name and
click the DELETE button. When prompted, enter the passphrase specified when the user
was created. The SNMP admin user cannot be deleted.
(Using SNMP v3 requires an SNMP v3 user on the recipient systems' SNMP v3-capable
agent/client)
User Name: Name of v3 User.
Mode: Currently only rouser (read-only user) mode is supported.
Level: Shows the Min Priv level of the user (see Min Priv, below):
n
n
n
n
auth: Authentication
noauth: No Authentication
priv: Auth and Privacy
blank: default level for admin
Add v3 User
To create an SNMPv3 user, complete the form and click the SAVE button.
Name: Alphanumeric user name, with no spaces or special characters.
Auth Phrase: Create a unique authentication passphrase for the user. It must be at least
eight characters long.
997-01520-02 Rev. G2.......................................................................... Page 31
Web Interface
Auth Crypt: The authentication type, MD5 or SHA1. It uses the Auth Phrase as its key
when calculating the message hash.
Priv Phrase: Creates a unique encryption passphrase for messages exchanged between
the network management software and the SyncServer. It must be at least eight characters
long.
Min Priv: Establishes the minimum authentication level required for the user. One of the following must be selected:
n
n
Authentication (Auth): Auth Phrase is always required

Auth and Privacy (Priv): Auth and Priv Phrase are always required
NETWORK-SNMPTraps
Use this page to configure, add, or delete SNMP trap recipients. The page is divided into two
sections. The first section displays the current recipients. The second section provides a form
for adding recipients or modifying existing recipients. The first section only displays basic
information for each recipient.
For information on configuring the SyncServer for SNMP queries and sending SNMP traps,
see Configuring SNMP (on page 120)
Trap Recipients
Destination: The IP address to which traps are to be sent.
Ver: The SNMP version (v1, v2c or v3).
(Send as Inform): If trap is to be sent as inform, inform is written, otherwise is blank.
User/Community: For SNMPv1/v2c traps, an optional community. For SNMPv3 traps, a
required SNMP v3 user on the recipient system. (Using SNMP v3 requires an SNMP v3
user on the recipient systems' SNMP v3-capable agent/client)
Add/Edit Trap Recipient

IP Address: The IP address to which traps are to be sent.
The SNMP version: v1, v2c, or v3.
User/Community: For SNMPv1/v2c traps, an optional community. For SNMPv3 traps, a
required SNMP v3 user on the recipient system.
Send as Inform: Sends an INFORM-PDU, otherwise a TRAP-PDU or TRAP2-PDU is sent.
Auth Phrase: For SNMPv3 traps, an optional Auth Phrase.
The hash algorithm used for the Auth Phrase: MD5 or SHA1.
Priv Phrase: For SNMPv3 traps, an optional Priv Phrase.
To edit a trap recipient, select the checkbox of a specific recipient and click the EDIT button.
Edit the values displayed in Add/Edit Trap Recipient and click the SAVE button. Similarly, use
the DELETE button to remove trap recipients from the list.
Page 32..........................................................................997-01520-02 Rev. G2
NETWORK Tab
NETWORK-Ping
Network Ping Test
Use this page to PING a network node from one of the SyncServer's network ports. This feature can be used to test and troubleshoot network connectivity issues. The network ping test
is supported on LAN1, LAN2, and LAN3.
To use PING:
1. Select the network port from which to send the PING packets. See "Ping 6 Command"
on page 33
2. For IPv6 networks, select Ping 6.
3. Enter the IP address of the host and click the APPLY button. Ping Output displays the results
five seconds after clicking apply.
Note: The approximate command line equivalent is "ping -c 5 -w 5", where "-c 5" means
"send five request packets to the requested destination" and "-w 5" means "timeout after 5
seconds if no responses". The network port that sends the ping request also receives the
responses.
Ping 6 Command
The SyncServer software executes the following command when pinging an IPv6 address.
ping6 -c 5 -w 5 -I <eth dev> ipv6address
-c 5 sends 5 ping requests.
-w 5 times out after 5 seconds regardless of the target is reachable or not.
ipv6address is the target address (Customer inputs this address in the SyncServer entry
box)
-I <eth dev> specifies the interface which corresponds to the drop down choice:
LAN1 -I eth0
LAN2 -I eth1
LAN3 -I eth2
LANG -I eth3
The drop down choice of the interface, suggests that it corresponds to where the ping6
packet will be sent out from. This is not entirely correct.
For example, the -I eth0 only means to set the source IP address in the ping packet to that
of the eth0, it does not specify which interface it actually will always use to send out the packets.
The interface the ping6 uses to send out the packets is entirely determined by the Linux
kernel routing table.
If the target Ipv6address is a link-local IPv6 address, the -I <eth dev> must also be a linklocal
address as specified in the way that SyncServer port was configured.
For example:
997-01520-02 Rev. G2.......................................................................... Page 33
Web Interface
ping6 -c 5 -w 5 -I <LAN1> ipv6address
If the ipv6address is a link-local address, then the LAN1 specified from the SyncServer
drop down menu on the ping page must also be configured with a link-local address. If it is
configured that way then the ping packet will be sent out that LAN1 port.
If the ipv6address address is a global address, then the -I <eth dev> information is ignored
and the Linux kernel routing table decides which port to send the ping packet out of. This is
how it is possible to specify a global address to send a ping6 to, but not have the packet exit
the specified LAN port. It is because either the LAN port did not have a global address specified, or if it did, the Linux kernel chose not to send the packet out that port, but rather
another LAN port that had a global address assigned.
NTP Tab
Select a topic from below to learn more about the NTP features of the Web Interface:
NTP- Sysinfo
This page shows the NTP Daemon Status and Control values:
Values are displayed for:
n
n
n
n
n
n
n
n
n
n
n
n
n
n
system peer
system peer mode
leap indicator
stratum
precision
root distance
root dispersion
reference ID
reference time
system flags
jitter
stability
broadcastdelay
authdelay
See also: RESTART button (on page 34)
RESTART button
After changing the NTP configuration, click the RESTART button to put the new configuration
into effect. While the NTP daemon restarts, its services are temporarily unavailable, and it
Page 34..........................................................................997-01520-02 Rev. G2
NTP Tab
generates the following alarm events: NTP Stratum Change, NTP System Peer Change,
NTP Leap Change.
NTP- Assoc
Use this page to view the status of NTP associations listed on the NTP - Config page.
Also see NTP Associations in the Glossary.
NTP Associations
Remote: The domain name or IP address of the remote end of the NTP association. Hardware Clock is the SyncServer's Hardware Clock. In the case of a remote NTP connection,
this will be the IP address of the remote end.
The character in the left margin indicates the mode in which this peer entry is operating:
n
n
n
n
n
* (asterisk) the association with which the NTP daemon is synchronizing (the system
peer on NTP - Sysinfo), marked "synchronizing".
+ (plus) indicates the SyncServer is symmetric active mode.
- (minus) indicates the SyncServer is symmetric passive mode.
= (equal) means the SyncServer is in client mode, marked "being polled".
^ (caret) indicates that the SyncServer is broadcasting to the remote node, marked
"broadcasting to".
~ (tilde) denotes that the remote node is broadcasting to the SyncServer.
Local: The IP address of the SyncServer network port at the local end of the NTP association. For the Hardware Clock it is "127.0.0.1", the IP address of the loopback port.
St: The stratum level of the remote clock in the NTP hierarchy. Lower values are given more
emphasis. For the local Hardware Clock, stratum 0 is a special value that indicates the Hardware Clock it is synchronized by a "timing root" reference such as GPS. Values in the range
of 1 through 15 indicate the number of steps the remote NTP connection is from its timing
root. Stratum 16 is a special value that indicates that the remote connection is not synchronized. The stratum reported by the SyncServer is incremented by one from its synchronizing peer. For example, while synchronized to the Hardware Clock (Stratum 0), the
stratum of the SyncServer is one (Stratum 1).
Poll: The length of the interval (in seconds) with which the SyncServer polls the remote
server, usually starting at 64 seconds and gradually increasing to 1024 seconds. Valid values
range from 16 to 65535, increasing by powers of 2. The polling interval for the Hardware
Clock is fixed at 16 seconds. The user-configured Minimum and Maximum Poll Interval settings on the NTP - Config page limit this interval.
Reach: This is an 8-bit shift register that keeps track of the last 8 attempts to reach the remote
end of the association. New bits are added to the rightmost end of the register (1 for reached
or 0 for unreached) and old bits "fall off" the left hand side. The shift register is represented in
octal. For example, by converting "377" from octal to binary, one gets "11111111", indicating
8 successful polls. For a sequence of eight successful polling attempts on a new association,
the octal value of Reach increases as follows: 1, 3, 7, 17, 37, 77, 177, 377. If the value isn't
one of those just shown, there may be a problem polling the remote end of the association. If
997-01520-02 Rev. G2.......................................................................... Page 35
Web Interface
the value remains at 0, or decreases to 0, the association is becoming unreachable. The
reach value stays 0 if the SyncServer is a broadcast or multicast server.
Delay: The total delay, in seconds, of the round trip to the remote end of the NTP association.
For example, a value of "0.07817" equals approximately 78 milliseconds. The Delay for the
Hardware Clock is "0". For most NTP associations, typical values range from tens to hundreds of milliseconds. The NTP daemon's clock selection algorithm gives preference to
lower Delay values.
Offset: The time offset between the SyncServer and the remote server, in seconds, of the last
poll. The NTP daemon's clock selection algorithm gives preference to lower Offset values.
The Offset for the Hardware Clock is usually in the microsecond range. For external NTP
associations, the offset is affected by the time base of the remote node and the characteristics of the network path, with values typically in the 1 - 10 millisecond range.
Disp: Dispersion represents the maximum error of the SyncServer relative to the NTP association. There are two components in dispersion, those determined by the peer relative to the
primary reference source of standard time and those measured by the SyncServer relative
to the peer. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the SyncServer can determine not only the time, but the
quality of the time as well.
NTP- Config
Use this page to create, edit, or delete NTP associations.
Also see Configuring NTP (see "Adding NTP Servers to the NTP Associations List" on
page 109) for more information.
Current NTP Associations

To edit or delete an association, select it using the checkbox and then click the EDIT or
DELETE button below. If the user selects EDIT, the details for that association are displayed
under Add/Edit NTP Association for the user to edit. Use the SAVE button to save the
changes and the RESTART button to make any changes take effect.
The list of Current NTP Associations always includes the Hardware Clock, which:
n
n
Cannot be deleted or edited.

Is configured as a preferred server ("server 127.127.45.0 prefer # pseudoaddress for the
timing engine" in ntp.conf).
Is displayed at the top of the list.
Additionally, the factory default configuration includes three Stratum 1 NTP servers operated
by Microsemi on the Internet.
The user should consider adding NTP servers available on the local network to the list of Current NTP Associations.
Add/Edit NTP Association

Use Add/Edit NTP Association to edit existing associations or to add new ones. The SyncServer can have multiple associations, each with a different Role.
Page 36..........................................................................997-01520-02 Rev. G2
NTP Tab
In the following explanations, the term "SyncServer" means "the local NTP daemon on the
SyncServer".
Role
n Server:
n
n
Addressing: Use with IPv4 class A, B and C addresses.

Description: Creates a persistent association between the SyncServer (client)
and an NTP node (server). The client synchronizes with the server if the client's
clock selection algorithm selects this server as the best clock. Typical server associations include: the hardware clock, the factory default NTP servers, and servers
added by the user. Also see system peer mode: client under NTP Daemon
Status.
Typical Usage: The user creates a Server association to designate an NTP node
that has an NTP Stratum better or equal to that of the SyncServer (client). Often,
the NTP server is another Stratum 1 server with a GPS reference that is outside
the user's administrative jurisdiction. The NTP servers operated by Microsemi
that are part of the factory default configuration are an example of this.
Peer:
Addressing: Use with IPv4 class A, B and C addresses.
n Description: Creates a persistent symmetric-active association between the SyncServer (peer1) with an NTP node (peer2). For the NTP node running in symmetric passive mode, there is nothing needs to be done on the NTP node.
However, the NTP node can be configured in symmetric active mode too. When
configured, the two nodes can synchronize with each other in a variety of failure
scenarios, such as loss of GPS and Internet connectivity. See system peer mode:
symmetric-active under NTP Daemon Status.
n Typical Usage: The user configures NTP associations on two NTP nodes that
point to the each other. The two nodes are usually of equal stratum and have independent references, such as two separate GPS installations or two separate network paths to NTP servers on the Internet. In the event of a reference failure, the
peers can synchronize to the node that has the best remaining reference.
Broadcast:
n Addressing: Use an IPv4 broadcast address of the local subnet. To broadcast
NTP messages on a subnet, if the local interface IP address were 192.168.61.58
and the mask were 255.255.255.0, the broadcast address could be
192.168.61.255.
n Description: Creates a broadcast server association. When configured with a
broadcast address (e.g., 192.168.61.255), the association broadcasts NTP messages from the network interface with the matching IP address (e.g.,
192.168.61.58). Broadcast messages go out to all nodes on the subnet, and are
usually blocked by routers from reaching adjacent subnets. Consult with the network administrator to select a correctly-scoped address and Time to live value.
n This type of association requires authentication on both the server and the clients.
See Using NTP Authentication.
n
997-01520-02 Rev. G2.......................................................................... Page 37
Web Interface
Typical Usage: Broadcast associations to reduce network traffic with a large number of NTP clients.
Broadcast Client:
n Addressing: The user does not specify an address with this setting.
n Description: Creates an association that listens for NTP broadcast messages on
all of the network interfaces. Upon receiving the first broadcast message, the
broadcast client association initiates a brief exchange with the server to calibrate
the propagation delay. Afterwards, the broadcast client association listens to and
gets the time from the broadcast server messages. This type of association
requires authentication on both the server and the clients. See Using NTP
Authentication.
n Typical Usage: Broadcast client associations can get authenticated time on networks that have a broadcast server.
Multicast Server: Create a Broadcast association with members of a multicast group.
The multicast address is a class D address starting from 224.0.0.1. (The IANA assigned
224.0.1.1 to be the NTP multicast address.) However, user can choose any class D
address that is not used on the local network by other protocols. Routers can be configured to transmit multicast messages to adjacent subnets.
Multicast Client:
n Addressing: Use the same IPv4 class D multicast address as the Multicast Server
(potentially 224.0.1.1).
n Description: Creates an association that listens for NTP multicast messages on all
of the network interfaces. Upon receiving the first message, the multicast client
association initiates a brief exchange with the server to calibrate the propagation
delay. Afterwards, the multicast client association listens to and gets the time from
the server messages. This type of association requires authentication on both the
server and the clients. See Using NTP Authentication.
n Typical Usage: Multicast client associations can get authenticated time on networks that have a multicast server.
n
Note: When authentication is configured, the same authentication scheme is available for all
NTP associations and over all network interfaces.
Address: The IP address or DNS name of the NTP association.
Burst
n Burst: When the server is reachable, send a burst of eight packets instead of the usual
one. The packet spacing is about two seconds. This is designed to improve timekeeping
quality for server associations. This setting should only be used in agreement with the
administrator of the remote NTP device as the traffic load may be onerous.
n iBurst: When the server is unreachable, send a burst of eight packets instead of the usual
one. As long as the server is unreachable, the packet spacing is about 16s. Once the
server is reachable, the packet spacing is about two seconds. This is designed to speed
the initial synchronization acquisition with the server command.
Version: Specifies the version number to be used for outgoing NTP packets. Versions 1-4 are
the choices, with version 4 the default.
Page 38..........................................................................997-01520-02 Rev. G2
NTP Tab
Minimum / Maximum Poll Interval: These options specify the minimum and maximum poll intervals for NTP messages, in seconds to the power of two. The maximum poll interval defaults
to 10 (1,024 s), but can be increased to an upper limit of 17 (36.4 h). The minimum poll interval defaults to 6 (64 s), but can be decreased to a lower limit of 4 (16 s).
MD5 Key: Use this field to authenticate NTP messages to and from the SyncServer for this
specific association. When enabled, the NTP packet header includes authentication fields
encrypted using either the MD5 key number (1 to 16).
Time to Live: This option is used only with broadcast association. It specifies the time-to-live
on broadcast server. Consult with the network administrator to specify a correct value. If this
field is left blank, the value of TTL defaults to 127.
RESTART button
After changing the NTP configuration, click the RESTART button to put the new configuration
into effect. While the NTP daemon restarts, its services are temporarily unavailable, and it
generates the following alarm events: NTP Stratum Change, NTP System Peer Change,
NTP Leap Change.
NTP- MD5Keys
Use this page to generate or manipulate keys generated using the RSA Message Digest 5
(MD5) algorithm authentication method. MD5 Keys are used to authenticate (not encrypt)
NTP messages sent or received by the SyncServer, using a cryptochecksum.
Also see Using MD5 Keys on a SyncServer.
NTP MD5 Security Keys

Use this page to manage MD5 keys as follows:
n
n
n
View and copy the current keys.

Upload a file containing keys from a local PC drive to the SyncServer.
Download the SyncServer's current key file to a local PC drive.
Generate: This button generates new random MD5 keys, immediately replacing any previous
MD5 keys.
Current Keys: This window displays the current list of keys.
The first line gives the SyncServer's hostname and the NTP time stamp of when the keys
were created. The second line shows the local time and date the keys were generated.
Each row of key information provides the following information:
n
n
n
The key number, 1 through 16

The key type, "MD5".
The key, an ASCII string containing only displayable characters. As an example, the random key generator may produce "\jdh.u$r;x"y:upH"
A comment that identifies the key type. For example: "# MD5 key"
997-01520-02 Rev. G2.......................................................................... Page 39
Web Interface
Upload Keys: Use this text field, with the BROWSE button, to enter the file path of the keys file.
Then click the UPLOAD button to load the keys to the SyncServer.
Download Keys: Press the Save As button to save the Current Keys to your PC as a file.
After keys are generated, the user can select Key and a key number in the MD5 key field on
the NTP - Config page.
Note: Disregard the "Unable to Open Key File" message while the Current Keys field is
empty.
NTP- Prefs
The settings on this page determine whether the NTP daemon, once synchronized, can
report an unsynchronized state.
Out of the three following stages of operation, the NTP - Prefs settings only apply during the
Loss of All References stage:
1. Startup: Upon starting, before synchronizing with any NTP associations, the NTP daemon reports to potential NTP clients that it is unsynchronized by setting leap indicator to
11 and stratum to 16.
2. Typical Operation: After synchronizing to an NTP association the NTP daemon uses leap
indicator and stratum normally. Leap indicator reports whether a leap event is pending
(usually 00 - no alarm). Stratum reports the stratum of the NTP daemon relative to the
system peer (system peer number + 1).
3. Loss of All References: If the NTP daemon cannot get the time from any association:
n With Standard NTP Rules (Factory Default) The stratum and leap indicator remain
the same as they were in the Typical Operation stage. The system peer remains
the unchanged, but the reference time stamp isn't updated and the reach statistic
gradually decreases to zero.
n With Override Behavior, if the estimated time error exceeds the Time Error Limit on
the TIMING - Holdover page, stratum reports 16 and leap indicator reports 11, as
they did during in the Startup stage.
After Loss of All References, if the NTP daemon synchronizes with an NTP association
again, it resumes Typical Operation.
Comments:
n
Given a pool of NTP associations from which to choose, an NTP client typically synchronizes with the best one, and does not require Override Behavior to declare an unsynchronized state.
Given a lack of NTP associations from which to choose, an NTP client may reject a SyncServer with better timing accuracy and stability than itself, if Override Behavior is
enabled.
The SyncServer's NTP daemon can get time from a server, peer, broadcastclient, and
multicastclient associations.
Page 40..........................................................................997-01520-02 Rev. G2
NTP Tab
n
Also see NTP Daemon Status, TIMING - HW Clock, TIMING - Holdover (on page 45),
Leap Indicator (on page 180), and Stratum (on page 181).
997-01520-02 Rev. G2.......................................................................... Page 41
Web Interface
TIMING Tab
Select a topic from below to learn more about the TIMING features of the Web Interface:
TIMING- TimeZone
Local Time Zone
This setting affects:
n
The time shown on the SyncServer front panel display when the user presses the TIME
button. Also see TIME Button (on page 73).
The time output by the IRIG out connector (if available), when the Output Type is set to
Local on the REFERENCES - IRIG-B page.
To determine the timecodes associated with each model of SyncServer, see SyncServer
feature comparison (see "SyncServer Signal Feature Comparison" on page 18).
The Time Zone setting does not affect NTP or any of the other timing outputs.
To set the time zone, select a profile from the list of Time Zones and click the APPLY button.
Each profile contains the offset from UTC to the time zone, plus any rules for daylight saving
time or summer time adjustments.
The Time Zones are alphabetically organized as follows:
n
n
n
n
Most Time Zones are sorted by continent and city name.

Some Time Zones are sorted by country and city name.
Some Time Zones are sorted by acronym (e.g., UTC, EST).
Some islands are sorted by ocean (e.g., Atlantic, Pacific, Indian) or national affiliation.
Current shows the time zone in effect and the local time at the moment the page was generated.
TIMING- HWClock
Use this page to configure the HW Clock.
See also: Steering with a Frequency Reference (on page 44), and Frequency Reference - Power-Down / Reboot (on page 45)
The Hardware Clock (HW Clock) provides accurate time to the SyncServer from one of its
timing references, allowing it to operate as a Stratum 1 Network Time Protocol server.
The SyncServer automatically detects and synchronizes the Hardware Clock to the highest
available reference in the following order:
n
n
n
n
GPS
IRIG
1 PPS
10 MHz
Page 42..........................................................................997-01520-02 Rev. G2
TIMING Tab
Any available source for a SyncServer can be enabled or disabled via a checkbox associated
with the source.
Note 1: At least one clock reference must be enabled.
Note 2: See SyncServer feature comparison (see "SyncServer Signal Feature Comparison" on page 18) to see which sources are available for each model of SyncServer.
If the reference becomes unavailable, the HW Clock uses the next highest available reference in the list.
If no other references are available, the HW Clock provides holdover by "flywheeling" on its
oscillator until a reference becomes available again. During this time, "REF" on the front
panel TIME screen (press the TIME button) is "None", while the "NTP Stratum" remains "1".
REF on the front panel NTP Status screen (press the STATUS button) changes to FLY.
If no references become available, the NTP daemon gets its time from other available NTP
references. At this time, "REF" on the TIME screen becomes "NTP" and "NTP Stratum"
degrades from "1" to the stratum of the NTP reference plus one. For example, with an NTP
Stratum 1 reference as its primary reference, the SyncServer's "NTP Stratum" becomes
"2". REF on the STATUS screen changes to the IP address of the synchronizing peer.
If references that set the time (GPS, IRIG, and NTP references) are not available, but a timing reference (1 PPS, 10 MHz) is, the user can set the time manually. See the "Setting the
Time Manually" section below.
NOTE 3: When providing a backup reference source for the GPS or IRIG Input references,
Microsemi recommends using the 10 MHz Input. An unsynchronized 1 PPS Input may cause
the NTP daemon to disqualify the HW Clock and rely on a lower-stratum NTP reference
instead, if one is available.
Oscillator Type: The type of oscillator in use. Three different oscillator types are offered in the
SyncServer.
n
n
TCXO This is the standard temperature compensated oscillator.

OCXO This optional oven oscillator is more stable and offers better holdover performance than the TCXO.
Rubidium This optional oscillator is more stable and has better holdover performance
than the OCXO.
Forced Timing Source: Forces the Hardware Clock to synchronize to a specific timing source.
n
Auto: The SyncServer automatically detects and synchronizes the Hardware Clock to the
timing reference(s) in the following order: GPS, IRIG-B, 1 PPS, 10 MHz. This is the factory default setting.
Free Run: Forces the Hardware Clock to ignore all references. This puts the SyncServer
oscillator into free running mode. If needed, the user can manually set the SyncServer's
UTC time while using this mode. The SyncServer takes submission of this page using the
APPLY button as the on-time mark.
UTC Time: Enter the UTC time here to set the Hardware Clock. Available when "Forced Timing Source" is set to Auto or Free Run.
997-01520-02 Rev. G2.......................................................................... Page 43
Web Interface
NOTE 4: When a timing source or user sets the Hardware Clock time, the SyncServer synchronizes its Software Clock (a.k.a, the "ntpd" or "NTP daemon") and its battery-backed
Real Time Clock (RTC) to the new time. The SyncServer also RESTARTS the NTP daemon after any clock change.
Setting the Time Manually

When Forced Timing Source is set to Auto or Free Run, the user can set the time manually
from the web interface or the command line interface. An adjust time command is also available from the command line interface.
NOTE 5: IMPORTANT: If the user is preparing to switch from Free Run to Auto and the time
is more than 1000 seconds off UTC time, manually set it within 1000 seconds of UTC time
before switching to Auto.
Using the Web Interface: Enter the UTC Time on the TIMING - HW Clock page and click the
APPLY button. The SyncServer applies the UTC Time at the next internal PPS rising edge
after receiving the web page.
Using the Command Line: Open a command line session to the Console RS-232 port or the
<LAN*> network port and log in as "admin" followed by the password. Enter the
SETTIMEOFYEAR command followed by the time in one of the following formats:
x.y
mm/dd/yyyy hh:mm:ss.x
yyyy ddd hh:mm:ss.x
MON dd yyyy hh:mm:ss.x
hh:mm:ss.x
In "x.y" format:
n
n
x = UTC seconds
y = fractions of a second
In the remaining formats:

n
n
n
n
n
n
n
n
n
mm = month 01 through 12
dd = day 01 through 31
ddd = day of year 001 through 366
yyyy = four-digit year
MON = first three letters of the month (e.g., "JAN")
hh = hours 00 through 23
mm = minutes 00 through 59
ss = seconds 00 through 59
x = fractions of a second
Steering with a Frequency Reference

To steer the clock using a frequency reference (1PPS, 10MHz), that frequency reference
must first be "qualified" by a valid timing source (see note below). To do this, connect the SyncServer to a valid timing source (GPS, IRIG-B, NTP Peer) then wait for the Sync Server to
lock to it. Once the SyncServer hardware clock locks to a valid timing source, all connected
frequency reference(s) will become "qualified" for Time-of-Day (TOD).
Page 44..........................................................................997-01520-02 Rev. G2
TIMING Tab
Frequency sources qualified by a hardware TOD source (GPS, IRIG-B) will be stratum-1,
and will continue to serve stratum-1 time even after the original timing reference is disconnected.
Frequency sources qualified by an NTP Peer will reflect the same stratum number and Reference Id / IP Address as the source that qualified them, and will continue to serve time (at that
same stratum) if the Peer is lost.
Frequency sources not qualified by any valid timing source are stratum-16.
Note: If you do not have access to a GPS, IRIG-B or NTP Peer timing reference, then an
alternate but not recommended -- option is to force-set the TOD through the serial interface. This forces the hardware clock to stratum-1, qualifying any attached frequency references also at stratum-1.
Once a frequency source has been locked and is actively steering the hardware clock, that
frequency source can then be used to qualify additional frequency sources.
Example:
1.
2.
3.
4.
Lock to GPS;
Connect 1PPS to "qualify" it.
Disconnect GPS; 1PPS remains qualified and steers the clock.
Connect 10MHz; the 10Mhz reference is now also qualified with the same stratum and
Reference Id as the 1PPS.
Frequency Reference - Power-Down / Reboot

Power Down
Upon power down, the frequency source essentially becomes "unqualified" due to the real
time clock's (RTC) "time away" (no matter how long) from monitoring that frequency input.
The SyncServer now comes back up as stratum-16 and will stay there until it is re-qualified
with a valid time source.
Reboot
When the system starts up, it is forced to stratum-16. It can only ever claim stratum-1 once it
has been connected and locked to a valid TOD reference (GPS, IRIG-B, NTP Peer). Once
this happens, any connected frequency reference is then "qualified" to serve stratum-1 time.
See Steering with a Frequency Reference (on page 44).
TIMING- Holdover
Overview
997-01520-02 Rev. G2.......................................................................... Page 45
Web Interface
The SyncServer uses holdover to continue operating as a stratum 1 NTP server/peer for a
period of time if the Input References become unavailable.
For example: A SyncServer in a downtown office building gets time from GPS. Surrounding
skyscrapers occasionally block signals from the GPS satellites as they move across the sky,
causing "gaps" that last several hours. The SyncServer uses holdover to continue operating
as a stratum 1 NTP server during these gaps.
The factory default settings are appropriate for most situations. However, the user should
consider extending holdover to cover the longest anticipated "gap" if more than one of the following conditions is true:
n
n
n
n
The SyncServer is the only NTP server available to the NTP clients.
The SyncServer only has one Hardware Clock Input Reference (e.g., GPS, Timecode).
The Hardware Clock is the only NTP association listed on the NTP - Assoc page.
Restoring an Input Reference would take longer than the holdover period in days.
Please note the Holdover settings on this page also affect NTP if Override Behavior is selected on the NTP - Prefs page.
The Settings
The user can simply set the number of days Holdover lasts, or specify a Time Error Limit. Setting either field generates an equivalent value in the other field.
About Time Error: When no Input References are available, the oscillator drifts away from
the correct time, accumulating time error. The type of oscillator affects how quickly time error
grows. The SyncServer keeps an ongoing estimate of the time error. Holdover ends when
the estimated time error is equal to or greater than the user-configured Time Error Limit.
The Oscillator Type affects the rate at which the oscillator accumulates time error when no
Input References are available.
n
n
TCXO The standard temperature-compensated oscillator.

OCXO The optional oven-compensated oscillator is more stable and offers better holdover performance than the TCXO.
Rubidium The optional rubidium oscillator has the best stability and holdover performance.
Several methods are available for the user to adjust Holdover or Time Error Limit:
n
n
n
Entering a value for Holdover Limit or Time Error Limit and click the SET button.
Sliding the green vertical bar on the Holdover graph left or right.
Sliding one of the black spheres under Holdover Limit or Time Error Limit left or right.
In Depth
Before entering holdover:
n
The Hardware Clock is synchronized to one of the Input References and reports Stratum
0 to the NTP daemon.
Page 46..........................................................................997-01520-02 Rev. G2
TIMING Tab
n
The NTP daemon is synchronized to the Hardware Clock "reference clock" and reports
Stratum 1 to the network.
The Hardware Clock enters holdover when the Input Reference becomes unavailable and
no other Input References are available.
While in holdover:
n
n
The Hardware Clock uses the internal oscillator to keep time (flywheeling).
The NTP daemon (Stratum 1) remains synchronized to the Hardware Clock (Stratum 0,
Reference = the name of the last Input Reference).
The SyncServer estimates the time error (difference) between the oscillator-based Hardware Clock time and UTC.
If two or more synchronizing NTP associations are available and the Hardware Clock
accumulates too much time error, the NTP daemon "drops" the Hardware Clock and synchronizes with the best association, with a corresponding adjustment to its Stratum.
The Hardware Clock leaves holdover when one of the following occurs:
n
An Input Reference becomes available again. (As a result, the NTP daemon returns to
Stratum 1 operation.)
The estimated time error exceeds the user-configurable Time Error Limit.
If the estimated time error exceeds the user-configurable Time Error Limit:
n
If one or more synchronizing NTP associations are available, the NTP daemon synchronizes with the best one, with a corresponding change to its stratum.
If no synchronizing NTP associations are available, the NTP daemon's behavior is
determined by the settings on the NTP - Prefs page. See NTP - Prefs (on page 40).
The Hardware Clock synchronizes to the NTP daemon.
TIMING- Sysplex
The Sysplex Timer port outputs serial time strings for IBM mainframe Sysplex systems. The
Sysplex Timer provides a common time reference across all the members of an IBM Sysplex. The Sysplex Timer is a key component when systems on multiple CPCs share access
to the same data.
See Sysplex Out (on page 94) for specifications and more information on the format of the
Sysplex output string.
Sysplex Output Configuration

The Sysplex Out port located on the rear panel outputs the time of day once per second.
Autostart:
n
Yes: The Sysplex Out connector automatically outputs the time of day after system startup. The user cannot stop or restart the output by entering the "C" or "R" commands.
No: The user starts or stops the Sysplex output by sending the following characters to the
Sysplex Out connector:
n "C" or "c" to start the output.
n "R" or "r" to stop the output.
997-01520-02 Rev. G2.......................................................................... Page 47
Web Interface
Parity: (Odd, None, Even) The parity setting of the Sysplex Out port (should match that of the
receiving device).
Flywheel Quality Character:
The user can set the Flywheel Quality Character to:
n
n
n
" " (space)

"X"
"F" (for Flywheel Quality Character)
About Sysplex and the Hardware Clock

To achieve the highest levels of precision and accuracy, the Sysplex Timer port gets its time
directly from the Hardware Clock. The Hardware Clock synchronizes with the highest priority Input Reference (e.g. GPS, IRIG-B).
If an Input Reference becomes unavailable, and Holdover expires, the Hardware Clock synchronizes to the time the NTP daemon gets from other synchronizing NTP associations (if
any are present). The default configuration includes three NTP servers on the Internet. If no
synchronizing NTP associations are present, the Hardware Clock is unsynchronized and
uses the internal oscillator to keep time.
The time quality character at the end of the Sysplex output string reflects the synchronization
state of the Hardware Clock. The user can select the time quality character used after holdover expires and the hardware clock is:
n
n
Synchronized to the NTP daemon, or

Using the internal oscillator to keep time.
This setting is called the Flywheel Quality Character.
About the Flywheel Quality Character

The time quality character at the end of the Sysplex output string has three states:
n
The first state is "X", time is invalid. The Hardware Clock has not yet synchronized to an
Input Reference.
The second state is " " (space), time is valid. Hardware Clock has synchronized to an
Input Reference, or is in Holdover.
The third state is "F", the Flywheel Quality Character. The Hardware Clock has no Input
References and Holdover has expired.
The time quality character can progress through a number of states:
1. After the user starts the SyncServer, the Sysplex port starts outputting a time string. Initially, the time quality character is "X" (time invalid).
2. When the Hardware Clock locks to an Input Reference, the time quality character
becomes " " (time valid).
3. If the Hardware Clock loses all Input References and enters Holdover, the time quality
character remains " " (time valid).
4. If Holdover expires, the time quality character becomes the Flywheel Quality Character,
determined by the user.
Page 48..........................................................................997-01520-02 Rev. G2
TIMING Tab
5. If an Input Reference becomes available again, the Hardware Clock synchronizes with it
and the time quality character becomes " " (time valid) again.
Usually there is a short delay between the Hardware Clock changing state and the time quality character changing.
Here are some potential guidelines for configuring the Flywheel Quality Character (FQC):
n
The user sets the FQC to " " if one or more of the following are true:
n The SyncServer is configured with two or more synchronizing NTP associations
and the user is satisfied with using time from other NTP associations.
n The SyncServer oscillator type has superior time keeping properties compared to
the receiving equipment. This is usually the case since most computer equipment
uses uncompensated quartz oscillators.
The user sets the FQC to "F" if the receiving equipment can handle "F" as a time quality
character in some way that is useful and distinct from the " " or "X" time quality characters.
The user sets the FQC to "X" so that the receiving equipment to handles time from NTP
or the Hardware Clock internal oscillator as "X" (time invalid).
Troubleshooting: If the time quality character remains "X" (time invalid) even though Input
References are connected to the SyncServer.
n
Verify that the physical connection to the input connector is valid and that there are no
cable breaks or short circuits.
On the TIMING - HW Clock page, verify that the Input Reference is Enabled and that Forced
Timing Source is set to Auto.
For IRIG-B, on the REFERENCES - IRIG-B page, check that the Timecode Input setting
matches the input signal type.
For GPS, wait for the GPS receiver to complete the GPS acquisition process and
achieve "locked" status. Also see Operating in "Window Mode" (on page 102).
Also see TIMING - Holdover (on page 45) and TIMING - HW Clock.
Note: If the user sets Forced Timing Source on the TIMING - HW Clock page to Free Run, the
Flywheel Quality Character in effect at that moment remains in effect thereafter.
997-01520-02 Rev. G2.......................................................................... Page 49
Web Interface
REFERENCES Tab
Select a topic from below to learn more about the REFERENCES features of the Web Interface:
REFERENCES-GPS
Note: This option is not available for the S250i model
GPS Position and Operating Mode

This page can be used to view or set the GPS receiver's Position and Mode, as well as the
GPS Antenna Cable Delay.
Status: Indicates whether the GPS receiver is a valid reference (locked) or not (unlocked).
Current Position: The GPS antenna position in Latitude and Longitude by degrees, minutes,
and seconds, and the cardinal points of the compass followed by the altitude in Meters.
These values can be permanently set when the GPS Mode is set to Position Hold.
Mode:
n
Survey: In this mode, the receiver surveys and averages its position before switching to
Position Hold mode. Use this setting for stationary applications, such as server rooms.
This is the default setting.
Dynamic: In this mode, the receiver continuously updates its position. Use this setting if
the position of the SyncServer could change occasionally or continuously, such as
vehicles, aircraft, and ships. This setting provides lower timing precision and accuracy
than the Survey and Position Hold modes.
Position Hold: In this mode, the receiver calculates the time based on a fixed position that
has been provided by Survey Mode or entered by the user. Use this setting if GPS visibility is poor and the receiver has difficulty establishing its position using Survey mode
after one day. The accuracy of the user-entered position affects the accuracy of the timing solution from the GPS reference. Also see Operating in "Window Mode" (on page
102).
Position Entry: Allows values of latitude, longitude, and altitude to be manually entered. Once
the values have been entered, click the APPLY button.
Antenna Cable Delay:
Use this setting to achieve the highest timing precision and accuracy on the timing outputs
such as IRIG Out or 1PPS Out. This setting has a negligible effect on NTP synchronization
because the scale of the adjustment (nanoseconds) is not significant compared to millisecond latencies on typical networks.
The Antenna Cable Delay advances the Hardware Clock slightly to cancel out the signal
delay caused by the length of the GPS antenna cable.
To calculate the adjustment, select the signal propagation rate for the appropriate cable type
from the table below and multiply it by the length of the cable.
Page 50..........................................................................997-01520-02 Rev. G2
REFERENCES Tab
Type
Rate per foot
Rate per meter
RG-58
RG-59
1.4 nS/foot
1.24 nS/foot
4.59 nS/meter
4.06 nS/meter
For example, the standard 50 foot RG-59 antenna cable x 1.24 nS/foot = 62 nS of Antenna
Cable Delay.
Or, using meters, the standard 15.24 meter RG-59 antenna cable x 4.06 nS/meter = 62 nS
of Antenna Cable Delay.
Note: The Antenna Cable Delay option is used to compensate for the signal delay caused by
the GPS antenna cable. Do not use this setting to compensate for the length of the Timecode
Output cable, use REFERENCES, IRIG-B instead.
REFERENCES-IRIG-B
Note: This option is not available for the S200 model.
Use this page to configure the IRIG In and IRIG Out connectors on the rear panel.
Locked: (Yes, No) Indicates the presence of a valid IRIG input.
Input Mode (IRIG In connector) and Output Mode (IRIG Out connector):
n
n
IRIG-B: Standard IRIG-B 123 time code.

IRIG-B (Legacy TrueTime): Standard IRIG-B with four time-quality bits and a lock indicator
encoded in the control bits.
IRIG-B with IEEE 1344 extension: Standard IRIG-B with information encoded in the control
bits per the IEEE 1344 standard. These include year, daylight saving time, leap second,
time quality, and parity information.
Auto: (Input Mode only) Automatically selects one of the modes above, based on the
incoming signal.
NOTE: IRIG-1344 only provides a leap warning during the last minute of the day of the
event. In this case, while the SyncServer will propagate that information via NTP, most NTP
clients will not query the SyncServer in time to be warned of the leap event.
Output Type: Set the type of time encoded in the IRIG-B time code output.
n
n
UTC: Standard IRIG encodes UTC. This is the factory default setting.
Local: Non-standard IRIG encoded with the local time offset instead of UTC. See the
TIMING - Time Zone page for information on setting the local time.
Cable Delay (nS): Compensate for the time delay in the output cable. This adjustment is used
to put the end of the output cable on-time. Select the signal propagation rate from the table
below and multiply it by the length of the cable to arrive at the cable delay.
RG-58 1.4 nS/foot 4.59 nS/meter
RG-59 1.24 nS/foot 4.06 nS/meter
See IRIG-B (S250i and S250) (see "IRIG-B" on page 173) default settings
997-01520-02 Rev. G2.......................................................................... Page 51
Web Interface
SYSTEM Tab
Select a topic from below to learn more about the SYSTEM features of the Web Interface:
SYSTEM- General
Use this page to manage:
n
n
The network Hostname for the SyncServer.

Automatically check for software upgrades.
Hostname: (Default: "SyncServer") The hostname identifies the SyncServer on the network
and is also an important element of NTP autokey authentication. When operating multiple
SyncServers on a network domain, or when using NTP autokey, replace the hostname with
a unique descriptive string composed of alphanumeric characters with no spaces or special
characters. The field has been programmed to reject invalid characters.
Software Update Availability Check: (Default: Enabled) When enabled, the SyncServer checks
a file on the Microsemi web site for software upgrades shortly after noon, local time, Monday
through Friday, as determined by the Local Time Zone setting on the TIMING - Time Zone
page. If the software Release and Revision on upgrade.txt (for S2XX models) is more recent
than that of the software on the SyncServer, the SyncServer displays a notice on the STATUS
- General page, and generates a System Upgrade Alarm on the ADMIN - Alarms page.
In order for the Software Update Availability Check to function, LAN1 must have:
n
n
Firewall access to the Internet (port 80)

A valid DNS server
To manually check if an upgrade is available, or if network conditions prevent Software

Update Availability Check from checking automatically, compare the STATUS - General page
with:
n
http://update.symmetricom.com/upgrade.txt for S200, S250, and S250i
Note: S2XX models have versions 1.XX

For example, compare "Version=1.10" and "Last Checkpoint: 1.103" on upgrade.txt with
"Release Version 1.10 Build 1.103" on the STATUS - General page. Since the values are the
same, no upgrade is available.
If an upgrade is available, go to Upgrading System Software (on page 107) to find out
how to upgrade the system software.
Note: The default configuration of the System Upgrade Alarm on the ADMIN - Alarms page is
"Severity = Minor", "Send SNMP trap", "Write to log", and "Send email notification" when
upgrades become available. SNMP and alarm email must be configured correctly to function.
The user can also contact Microsemi Customer Assistance (on page 3) for information
about upgrades.
Page 52..........................................................................997-01520-02 Rev. G2
SYSTEM Tab
SYSTEM- Upgrade
Use this page to upgrade the SyncServer's software. This can be done using the web interface to upload the new software from workstation, or using the keypad/display interface to
upload the new software from a USB flash memory device connected to one of the SyncServer's USB ports. Please consult Upgrading System Software (on page 107) before
upgrading the software.
Note: Please avoid decompressing the *.tar upgrade file prior to upgrading the SyncServer.
The SyncServer will not install software from an upgrade file that has been modified or
decompressed and recompressed. If needed, please download a new software file from
Microsemi.
Upload Upgrade Package to SyncServer

BROWSE button: Choose an upgrade file that's accessible from your workstation, such as a
network drive or Desktop.
UPLOAD button: Upload the upgrade file to the SyncServer.
Manage Files in SyncServer

Current Files: This window displays upgrade files and an upgrade history file.
Optional Parameters: This field can be used to supply optional installation parameters, if
required. This field is not required for normal operation.
INSTALL button: To install the upgrade file, select the file and click the INSTALL button.
VIEW button: To see the upgrade history, select the upgradehist.txt file and click the VIEW button.
DELETE button: To delete a file, select the file and click the DELETE button. It may be necessary to upload a file before the upgradehist.txt file can be selected and deleted.
SYSTEM- FactoryReset
Use this page to reset the SyncServer to its original factory default configuration.
Before resetting the factory defaults, the user may want to back up the current configuration
if they intend to use it again in the future.
To reset the factory defaults, select Reset to Factory Defaults and click the APPLY button. This
clears *ALL* of the current settings on the SyncServer, restores the original factory default
configuration, and reboots the SyncServer.
After restarting, the user may need to configure LAN1 before reconnecting to the web interface. The default username and password (admin, symmetricom).
See Factory Default Settings (on page 171)
A partial list of the defaults restored by this operation:
n
n
Network port settings

NTP Associations
997-01520-02 Rev. G2.......................................................................... Page 53
Web Interface
n
n
n
n
Hostname
All settings defined on the ADMIN pages (Web, Users, Alarms, Logs Config), including the
username and password settings.
All services are reset to their default modes of operation.
Hardware Clock settings, including forced mode, Time Zone, Position and Time Error
Limit, IRIG Input and Output, etc.
All cryptographic materials (NTP keys, sshd keys, SNMP users and communities)
deleted.
Logs are erased.
Also see Backing Up/Restoring Configurations (on page 118), Configuring LAN1 (on
page 111), and Logging in to the Web Interface (on page 112).
Page 54..........................................................................997-01520-02 Rev. G2
ADMIN Tab
ADMIN Tab
Select a topic from below to learn more about the ADMIN features of the Web Interface:
ADMIN-Web
Use this page to:
n
n
Configure the appearance and information displayed on the login page.

Modify the behavior of the web interface.
Login Page Configuration

The settings in this section configure the Login page to:
n
Display status information. This is convenient for monitoring status without logging in, particularly if LAN1 is on a private administrative network.
Remove status and information that identifies the SyncServer from the login page. This
makes it more difficult for unauthorized users to recognize the SyncServer via its web
interface.
The login page choices are:

n
n
Plain: Login page does not contain any identifying text or graphics.
Graphic: Login page contains identifying text, graphics, and user-selected status information.
The configurable system information includes the following choices:

n
n
n
n
n
n
Title: A user-determined text string at the top of the login page.

Time, Hostname and LEDs: The local time, the hostname, and the status LEDs.
NTP Status: The NTP Stratum and Reference ID.
Hardware Clock Status: The current Sync Source and whether the Hardware Clock is
locked.
GPS Receiver Status and the Satellite Count: GPS receiver is providing timing information
and the number of satellites visible.
Highest Severity Alarm: The name of the most recent and most severe pending alarm.
Version Information and Uptime: The model number, software version, and uptime since the
unit was started.
IP Addresses for all Configured LAN Ports: The MAC, IPv4, and IPv6 addresses of the LAN
ports.
Save Configuration Settings

Beyond the login page, the user can determine the behavior of the web pages.
Warn when Navigating without saving Changes: (Enabled by default)
n
When this feature is enabled, the SyncServer sends warnings messages if the user
makes settings changes and navigates away from the page without clicking the APPLY
button. This reduces the possibility of accidentally losing unsaved changes.
When this feature is disabled, the SyncServer suppresses these warning messages.
997-01520-02 Rev. G2.......................................................................... Page 55
Web Interface
Updating the Configuration Backup File: (Enabled by default)
n
When this feature is enabled, the SyncServer updates the configuration backup file in
non-volatile memory when the user applies or saves changes to the configuration. This
may slow the web interface's response time, but ensures that the current configuration is
backed up and will be restored if the SyncServer is rebooted.
When this feature is disabled, the SyncServer does not update the backup file when the
user applies or saves changes to the configuration. This may improve the web interface's
response time to applied changes but leaves the backup file unchanged. This option can
be useful for keeping a "known good configuration" available while trying out experimental configurations. If the experimental configurations aren't satisfactory, use the
WIZARDS - Restore page to restore the known good configuration. Once the desired configuration is reached, manually save the configuration backup file to non-volatile memory
using the WIZARDS - Backup page.
Send Browser hint to not Auto-complete login page username / password: (Disabled by default)
n
Enabling this setting enhances security. It prompts browsers to suppress the "auto-complete" and "remember password" features. This makes it more difficult for unauthorized
users to gain access to the SyncServer from an authorized user's workstation or by
exploiting stored browser settings.
Web Session Timeout

Select one of the following, and then press Apply:
n
n
n
n
n
5 Min
10 Min (default)
15 Min
30 Min
60 Min
ADMIN-Users
User Creation, Deletion and Password Maintenance
Use this page to:
n
n
n
n
n
Add new users

Delete existing users
Set a new password
Enable and configure password recovery
Send a test email for password recovery
User
Select either New User or admin:
Page 56..........................................................................997-01520-02 Rev. G2
ADMIN Tab
n
New User, allows new Username and password information to be entered. If Password
Recovery checkbox is selected, recovery information can be entered, and a test email can
be generated.
admin, allows usernames and passwords for existing users to be maintained.
Note: The Delete Selected User checkbox when checked, deletes information in the Recovery
Question fields. If the Apply button is clicked, the user information will be deleted.
Passwords
Passwords must contain six or more characters, including lower and upper case letters, or
letters and at least one number.
With password recovery enabled, the user can reset the password to a random string from
the Login page by correctly answering the password recovery question. The SyncServer
then sends an email message containing the new password to the email address supplied on
the ADMIN - Users page.
The SyncServer must have a valid SMTP Gateway addresses for password recovery to
work. If a DNS server is not available to <LAN*>, the SMTP gateway must be entered as an
IP address, not as a DNS name. If needed, contact the system administrator to obtain this
information.
See also: Changes to Passwords and User Names (see "Properties of User Names and
Passwords" on page 20)
Changing the Password and Enabling Password Recovery

1.
2.
3.
4.
5.
Enter the Old Password.

Enter the New Password and Retype New Password.
Select the Password Recovery checkbox.
Select a Recovery Question and enter the Answer.
Enter an Email Address and the SMTP Gateway's IP address or DNS name (if DNS is configured for <LAN*>).
6. (Optional) Select the Send Test Email checkbox.
7. Click the APPLY button.
NOTE: Once applied, test question, answer, and email address data will not remain visible
on the page. The SMTP Gateway entered here is also used for email notification of alarms.
However, email addresses for alarm notification are entered on the SERVICES - Email page.
Email notification of alarms is configured on the ADMIN - Alarms page.
ADMIN-Alarms
Alarm Configuration and Notification
Use this page to view alarm status and to perform the following tasks:
n
n
Configuring Alarm Severity (ALARM LED color).

Manually clearing alarms.
997-01520-02 Rev. G2.......................................................................... Page 57
Web Interface
n
n
n
Configuring Alarms to clear automatically after 15 minutes.

Configuring notification by SNMP traps and email messages.
Logging of alarms, notification events.
The Alarm LED at the top left corner of the web interface and on the front panel indicates the
highest severity alarm on the ADMIN - Alarms page:
n
n
n
Red: Alarm with severity = Major.

Orange: Alarm with severity = Minor.
Green: Alarm with severity = Notification, or no alarms.
Alarm Configuration and Notification

Name: Describes the system event that causes the alarm. Also see Alarm Descriptions (on
page 59), and Alarms and Notification (on page 116).
State: A graphic LED indicating the alarm state and severity at the time the page was generated:
n
n
n
n
Grey LED: Severity is set to Notify.

Green LED: Severity is Major or Minor, and there is no alarm.
Orange LED: Severity is set to Minor, and there is an alarm.
Red LED: Severity is set to Major, and the alarm there is an alarm.
Note: To check the current state, click the refresh icon (rotating arrows) at the lower right
corner of the page.
Clear Now: This checkbox is only available during an alarm. To clear the alarm, select the
Clear Now checkbox and click the APPLY button. Doing so returns the alarm to a "No
Alarm" state.
Auto Clear: Automatically clears the alarm after 15 minutes, regardless of the condition that
caused it.
Severity: Determines the Alarm LED response to an alarm and sets the "Level:" in the SNMP
trap, email message, and log entry.
n
n
n
Notify: Does not raise an alarm (No change to Alarm LED color).
Minor: Raises a minor system alarm (Alarm LED = Orange).
Major: Raises a major system alarm (Alarm LED = Red).
Note: If enabled, Send Trap, Write Log, and Send Email operate in response to alarms,
regardless of Severity.
Send Trap: Sends an SNMP trap when the alarm occurs and ends. SNMP must be configured correctly on the NETWORK - SNMP and NETWORK SNMP Traps pages for this to work.
Write Log: Generates a log entry in syslog when the alarm occurs and ends. The log can be
viewed from the LOGS - syslog page.
Send Email: Generates a descriptive entry in an email message when the alarm occurs and
ends. The SyncServer compiles the entries over a 5-minute period and sends email messages at five-minute intervals, so an email alert may contain more than 1 alarm. For Send
Email to work, the SERVICES - Email page must be configured with a valid SMTP Gateway
Page 58..........................................................................997-01520-02 Rev. G2
ADMIN Tab
and email address. If the SMTP gateway is a DNS name, LAN1 on NETWORK - Ethernet must
be configured with a valid DNS server address.
Note: When Clear Now and Auto Clear are used to clear an alarm, Send Trap, Write Log,
and Send Email do not generate notification messages or log entries.
Alarm Descriptions
Note: Alarm indicators for optional features or equipment appear when the related option is
present and enabled.
NTP System Peer Change Alarm: The SyncServer's current NTP synchronization peer has
changed.
NTP Stratum Change Alarm: The NTP Stratum level has degraded. For example, the NTP
Stratum has gone from 1 to 2.
NTP Leap Change Alarm: The SyncServer raises this alarm when the leap indicator changes
state. See STATUS - NTP (on page 25).
This change of state has two potential causes: The first is that the SyncServer was reconfigured, causing the NTP daemon to be restarted. More rarely, this can occur when the SyncServer is within 24 hours of a leap second adjustment.
System Network Alarm: Alarms if a configured port has no connection (network link). Clears if
all configured ports have connections.
System Upgrade Alarm: The SyncServer checks for software upgrades and raises this alarm if
a software upgrade is available. Microsemi recommends leaving this alarm enabled.
Microsemi recommends enabling Send Trap and/or Send Email for this alarm on the ADMIN Alarms page.
Note: In order to detect upgrades, the SyncServer must be correctly configured with a DNS
server and must have http access to the Internet through port 80. This feature is enabled by
default, but can be disabled on the SYSTEM - General page.
System Config Change Alarm: Generates an alarm if the system configuration has been
changed. If the Auto Clear is not selected, this alarm will remain pending until cleared by the
administrator.
System Health Alarm: The web interface has been unable to automatically save user configuration changes to the backup file. The user might need to perform a manual backup using
the WIZARDS - Backup page.
System Up/Down Alarm: The Syncserver has been restarted.
System Authentication Alarm: The SyncServer detected a failed login attempt on the web interface.
Timing No Source Alarm: The Hardware Clock does not have a valid timing reference.
Timing GPS Source Alarm: (Displayed on GPS-equipped SyncServers only) The GPS time reference is not providing valid timing information. This may be caused by:
n
An insufficient number of visible GPS satellites.
997-01520-02 Rev. G2.......................................................................... Page 59
Web Interface
n
The GPS satellite signals may be blocked from reaching the antenna, or are too weak to
be detected by the receiver.
The GPS antenna cable may be disconnected, broken, shorted, or too long.
Timing Timecode Source Alarm: The Hardware Clock is not detecting a valid input signal on the
IRIG In connector.
Timing PPS Source Alarm: The Hardware Clock is not detecting a valid input signal on the
1PPS In connector.
Timing 10MHz Source Alarm: The Hardware Clock is not detecting a valid input signal on the
10MHz In connector.
Timing GPS Antenna Short Alarm: (Displayed on GPS-equipped SyncServers only) The GPS
receiver detects an overcurrent condition on the GPS antenna cable. The likely cause is a
short circuit.
Timing GPS Antenna Open Alarm: (Displayed on GPS-equipped SyncServers only) The GPS
receiver detects too little current in the power supplied to the GPS antenna. The likely cause
is a disconnected or broken GPS antenna cable. A GPS splitter may also cause this condition.
Timing Oscillator DAC Range Alarm: The SyncServer is applying the maximum or minimum
DAC value to steer the oscillator. If this recurs frequently or over a sustained period of time,
there may be a problem with the oscillator.
Timing Rubidium Lock Alarm: The optional Rubidium oscillator, if installed, has not stabilized its
frequency output. After power up, this alarm may be raised for up to several minutes until the
Rubidium warms up and stabilizes its frequency output.
Timing Oscillator Unlock Alarm: The Hardware Clock's oscillator frequency is not locked to the
reference source.
Timing Source Change: The Hardware Clock has switched timing references.
Timing Source Change Lower Accuracy Input: The Hardware Clock has switched to a lower-priority timing source.
Timing PLL Unlock Alarm: The Hardware Clock oscillator's PLL unlocked.
Timing Time Quality 1e-6 Alarm: The Hardware Clock's estimated time error has exceeded 1e6 seconds (1 microsecond).
Timing Time Quality 1e-5 Alarm: The Hardware Clock's estimated time error has exceeded 1e5 seconds (10 microseconds).
Timing Time Quality 1e-4 Alarm: The Hardware Clock's estimated time error has exceeded 1e4 seconds (100 microseconds).
Timing Time Quality 1e-3 Alarm: The Hardware Clock's estimated time error has exceeded 1e3 seconds (1 millisecond).
Timing Leap Event Alarm: The leap indicator from the Hardware Clock's GPS or IRIG 1344 timing references, indicates that a leap event is pending. The pending event can be a Leap
Second Insertion, Leap Second Deletion, or Clear Alarm, which indicates that the alarm has
passed. See STATUS - Timing for more information.
Page 60..........................................................................997-01520-02 Rev. G2
ADMIN Tab
Note: IRIG-1344 only provides a Leap Indicator warning during the last minute of the day of
the event. In this case, while the SyncServer will propagate that information via NTP, NTP clients may not query the SyncServer in time to be warned of the leap second adjustment.
LAN1 Link Alarm: A network connection is not available on LAN1. Note that if LAN1 is down,
SNMP and Email notification do not work and the web interface is not available.
Note: The Network LED indicates the status of the "LAN* Link Alarms". Please consult
Status LEDs.
LAN2 Link Alarm: LAN2 has lost its network connection.
LAN3 Link Alarm: LAN3 has lost its network connection.
Timing NTP Daemon Alarm: The NTP Daemon is no longer a valid source of timing to the Hardware Clock.
System Reset Default Config Alarm: Typically, during a reboot, the SyncServer applies the current configuration. This alarm is raised when the system failed to initialize itself to the current
configuration and it automatically restored itself to the default configuration. The circumstances are usually caused by missing or corrupted current configuration.
ADMIN-LogsConfig
System Log Configuration
Use this page to configure the SyncServers logging subsystem. The SyncServer uses klogd
and syslogd, the standard logging facilities. What is logged and where it is logged is based on
the options selected in this page. A default set of options is preconfigured that should provide
a level of detail sufficient for the majority of applications. Each entry is broken down into facility and priority, where facility is the part of the system such as the kernel or the application
daemons and priority indicates the severity of the message. The priority ranges from
"Emerg", which represents only very significant events like kernel panics to "Debug", where
even debug messages are logged. Messages are generally logged to different files to allow
easier parsing. The messages file is unique however in that its default configuration captures
all messages flowing through the logging daemons. But, due to the high volume of traffic, it is
cleared at each power cycle or reboot.
Note: Most users should leave the logs configured in the default manner unless directed to
make changes by Microsemi technical support.
Log Types
syslog: syslog holds messages about system level events. Examples of system events are
privilege changes (e.g., sudo) and messages about regularly schedules events such as cron.
auth.log: The authentication log contains entries regarding authentication events from login or
PAM (Pluggable Authentication Module).
kern.log: The kernel log contains entries submitted by the kernel. Examples of kernel events
are network errors or hardware changes.
997-01520-02 Rev. G2.......................................................................... Page 61
Web Interface
daemon.log: The daemon log contains entries submitted by the daemon processes that
provide the services in the SyncServer. Examples of daemon log entries are NTP changes,
SNMP events, and xinetd events.
messages: The messages file is something of a catchall file. By selecting various priorities, it
is possible to capture large amounts of data regarding system operation. However, the
volume of data becomes impractical to manage quickly. As such, this file is cleared at each
power cycle or reboot.
events: The events log is not configurable. This log is maintained outside syslogd and contains configuration and event data related to operations performed in the web interface.
Log Priorities
In the case of kernel, syslog, auth and daemon logs, the priority specified will cause all messages less than or equal to the selected priority to be logged. The priorities are defined in descending order.
In the case of the messages log, only the selected priorities are logged. As such, up to four
priority levels are supported.
Debug: This priority level captures debug output from applications designed to produce this
type of output. This level generates a large volume of traffic and is not recommended unless
it is done under the direction of technical support personnel. An example may be a signal
handler called.
Info: This level captures informational output. This level typically provides information regarding successful operations. An example may be a successful file save or a normal application
startup.
Notice: This level captures transactional information. An example of this could be a network
connection or login.
Warning: This level captures information that is not expected by the application or system.
This could be something the system is not configured to handle. An example might be a malformed network packet or a drive change caused by inserting a thumb drive into a USB slot.
Err (deprecated): The use of this level is deprecated.
Crit: This level captures critical information. This data can often be used to debug the failure
of a system or application under abnormal conditions. An example of this may be a memory
error.
Alert: This level captures information about which the administrator should be made aware.
An example of this could be a failed login attempt.
Emerg: This level captures messages of the highest priority. These are typically last resort
messages before an abnormal exit of the calling application or the system itself. An example
of this would be a hardware error or memory exhausted message.
Remote Log System

It is possible to send a copy of all messages to up to 8 (eight) remote system running syslogd.
This allows centralized management of alarm messages. As the system logs are written to a
RAM based volume, messages may be lost if the system is rebooted or power cycled or
Page 62..........................................................................997-01520-02 Rev. G2
ADMIN Tab
experiences an unexpected failure. They may also be overwritten if memory is low.
Microsemi recommends rotating log files, if needed. Specifying the DNS name or IP address
of a remote server will configure the SyncServer to send a copy of each message received
by the syslog and kernel log daemons to the remote address, if it is reachable. The remote
server can then be configured to filter the messages using its configuration file.
A complete definition of how Syslog is configured may be obtained by consulting the standard syslog.conf man pages that are widely available on the Internet.
See Admin Logs Config (see "Logs Config" on page 175) default settings
997-01520-02 Rev. G2.......................................................................... Page 63
Web Interface
SERVICES Tab
Select a topic from below to learn more about the SERVICES features of the Web Interface:
SERVICES-Startup
Daemon Current State and Startup
The SyncServer uses a number services that operate continuously to support its functions.
Use this page to:
n
n
n
View the current state of the services and to turn them on or off.
Enable or disable services from starting automatically when the SyncServer is started.
Run, Reboot, or Halt the SyncServer's operating services and operating system.
Daemon
A list of the user controllable daemons supported by the SyncServer:
Web Server (HTTPD): Provides the SyncServer's web interface. If Auto Startup is deselected
and the SyncServer reboots, the web interface will not be available.
To start the web server after it has been stopped, open a command line session through the
Console RS-232 port located on the front panel or, if available, through a Telnet session with
LAN1 port. Once logged in, restart the web server by typing "HTTP on".
NTP: Network Time Protocol daemon. Supports all NTP functions.
SNMP: Simple Network Management Protocol daemon. Responds to SNMP requests and
sends SNMP traps.
SSH: Secure Shell daemon. Provides an encrypted channel for command line sessions with
the SyncServer through the LAN1 port.
Sysplex: Sysplex timing information on the Sysplex Timer-Out connector.
Time: Time Protocol requests per RFC 868 over TCP.
Time - UDP: Time Protocol requests per RFC 868 over UDP.
Daytime: Daytime Protocol per RFC 867 over TCP.
Daytime - UDP: Daytime Protocol per RFC 867 over UDP.
Telnet: Telnet protocol service for remote access to the command line interface on LAN1.
Current State/Startup
Shows the current state of the service. To change the state, select the desired state and click
the APPLY button.
On: The service is running.
Off: The service is stopped.
Auto: When selected, the service starts automatically when the SyncServer reboots.
Page 64..........................................................................997-01520-02 Rev. G2
SERVICES Tab
Note: Services that cannot be directly turned off display grayed out On and Off radio buttons.
These services can only be controlled by selecting or deselecting Auto Startup. Applying the
change will then stop or start the service as appropriate.
System Control
Run: The SyncServer continues to operate normally. This is the default setting.
Reboot: Reboots the SyncServer. During this process, the browser displays "This browser
will attempt to reconnect..." When the SyncServer finishes rebooting, the browser displays
the login screen (provided DHCP hasn't changed the IP address).
Halt: Halts the operating system after about 15 seconds, typically. While the SyncServer is
halting, the web interface displays "Halting System - This browser session cannot continue..." and the front panel display states "Shutting down. Please wait...". Wait at least 15
seconds, and shut the power switch off.
See Services Startup (see "Startup" on page 176) default settings
SERVICES-HTTP
Web Server Configuration
The SyncServer's web interface allows both standard and secure (encrypted) network
access. Standard access is provided by default. To use encrypted access, a secure certificate must be created. The SyncServer can only use self-signed certificates.
Creating a new certificate overrides previously created certificates. The certificate values
used are not significant to the SyncServer. They are provided to any user using the certificate. All of the fields must contain values.
When a certificate has been created, the Secure log in option appears on the login page. The
entire session uses the selected communication method.
Security
Standard (Port 80) Only: The web interface is available using a standard non-encrypted http
connection. This is the factory default configuration.
Secure (Port 443) and Standard (Port 80): The web interface is available using either type of connection.
Secure (Port 443) Only: The web interface is available using an SSL-encrypted connection.
Note1: To connect to Port 443, the URL in the browser must begin with "https".
Protocols
If the secure port 443 has been selected, the following the security protocol selections can be
checked:
n
n
n
TLS 1.0
SSL 3.0
SSL 2.0 (appears only if previously used)
997-01520-02 Rev. G2.......................................................................... Page 65
Web Interface
Note2: the default is to have both TLS 1.0 and SSL 3.0 selections checked.
Note3: SSL 2.0 exists only for the purposes of backwards compatibility on systems previously enabling this protocol. SSL 2.0 is a deprecated security protocol, and this option will
no longer appear on the SERVICES - HTTP page if at any time Port 443 or SSL 2.0 is disabled, or the system is restored to factory defaults.
Note4: At least one protocol needs to be selected. In addition, if at any time the protocol
being used is changed, the certificate will need to be regenerated. See the following.
Certificate Info:
Common Name: SyncServer's hostname, as entered on the SYSTEM - General page. The
default factory configuration is "SyncServer".
Bits: Number of RSA Key Bits, 1024 or 2056 bits. The default factory configuration is "1024".
Days to Expiration: The number of days before the certificate expires.
ISO Country Code: The Two-Character International Country Code.
State: The state where the SyncServer is located.
Locality: The locality where the SyncServer is located.
Organization: The organization or company the SyncServer belongs to.
Organizational Unit: The organizational unit or division that uses or is responsible for the SyncServer.
Email Address: The email address of the administrator responsible for the SyncServer.
See Services HTTP (see "HTTP" on page 176) default settings
SERVICES-SSH
SSH Security Configuration
After setting the other options on this page, select Regenerate SSH Secure Keys and click the
APPLY button to generate a new set of SSH secure keys. This step is required before the
user can log in to LAN1 using SSH.
Protocol: Sets the protocol to one of the following:
n
n
n
SSH-1 & SSH-2

SSH-1 Only
SSH-2 Only (default)
Allowed Users: List user names that are allowed SSH access.
Denied Users: List user names to exclude from SSH access.
Note: Use a space character between user names. This list supports the ? wild card as a substitute for an individual character, and the * wild card as a substitute for the rest of a word.
For example, Allowed Users = Bird* would let Bird1 and Birddog log in. Allowed Users =
Bird? would let Bird1 log in, but not Birddog.
Page 66..........................................................................997-01520-02 Rev. G2
SERVICES Tab
Log Level: The level of verbosity for logging ssh messages.
Can be set to one of the following:
n
n
n
n
n
n
QUIET
FATAL
ERROR
INFO (default)
VERBOSE
DEBUG
Server Key Bits: The number of bits to use when generating the keys.
Can be set to one of the following:
n
n
n
n
512
768 (default)
1024
2048
Key Regeneration: The interval, in seconds, with which to regenerate keys (default 3600
seconds).
See Services SSH (see "SSH" on page 177) default settings
SERVICES-Email
SMTP Gateway and Alarm Email Recipients
This page establishes the SMTP gateway and email addresses used by the SyncServer for
email notification of alarms and password recovery emails. This page must be configured correctly for "Send Email" notification on the ADMIN - Alarms page to work.
SMTP Gateway: Enter the DNS name or IP address of a SMTP server that's reachable from
LAN1.
User 1-10: Enter the email address of the individuals who should receive email notifications of
alarms.
997-01520-02 Rev. G2.......................................................................... Page 67
Web Interface
LOGS Tab
System Event Log
The Logs page provides access to system activity and messages that are generated by the
various subsystems in the SyncServer. The logs are separated by function. The logging
behavior can be configured using the ADMIN - Logs Config page. Each of the logs records a
series of time-stamped events.
In the case of the system, auth, daemon, kern and messages logs, the entries take the standard form defined by the syslog daemon. These entries are:
date time system facility message: Here "system" is the hostname that generated the message. The "facility" is a component of the system generating the message. This could be anything like the kernel itself, system daemons and even applications. Finally, there is the text of
the message itself. Here are two messages on the system SyncServer. One is from daemon.log and the other from the kernel:
Sep 19 19:20:26 SyncServer ntpd[3577]: ntpd [email protected] Tue Aug 9
01:05:42 UTC 2005 (7)
Sep 10 00:06:18 SyncServer kernel: Jida-Driver installed
In the case of the event log, the entries take the form of:
Date time user source description
Here "user" is the user logged into the web interface, "source" is the IP address of the remote
system using the web interface and "description" provides information regarding the nature
of the event. Here is a message showing a successful remote login along with the user id and
IP address of the contact.
10/01/2005 22:36:28 admin 192.168.7.16 Successful login
Events: The events log is not configurable. This log is maintained outside syslogd and contains configuration and event data related to operations performed in the web interface.
syslog: syslog holds messages about system level events. Examples of system events are
privilege changes (e.g., sudo) and messages about regularly schedules events such as cron.
auth.log: The authentication log contains entries regarding authentication events from login or
PAM (Pluggable Authentication Module).
daemon.log: The daemon log contains entries submitted by the daemon processes that
provide the services in the SyncServer. Examples of daemon log entries are NTP changes,
SNMP events, and xinetd events.
kern.log: The kernel log contains entries submitted by the kernel. Examples of kernel events
are network errors or hardware changes.
messages: The messages file is something of a catchall file. By selecting various priorities, it
is possible to capture large amounts of data regarding system operation. However, the
volume of data becomes impractical to manage quickly. As such, this file is cleared at each
power cycle or reboot.
Page 68..........................................................................997-01520-02 Rev. G2
LOGS Tab
Every 20 minutes, if no new messages were logged, the Syslog daemon logs a -- MARK -message to indicate that it is alive and well.
997-01520-02 Rev. G2.......................................................................... Page 69
Web Interface
WIZARDS Tab
Select a topic from below to learn more about the WIZARDS features of the Web Interface:
WIZARDS-1stSetup
Microsemi strongly recommends using the 1st Setup to perform the initial configuration of the
SyncServer.
1st Setup guides the operator through the following procedures:
n
n
n
n
Setting a new password

Enabling Password Recovery (optional)
Configuring the IP address, hostname, and DNS for <LAN*>.
Setting the local time zone (optional)
WIZARDS-NTP
Microsemi recommends using this wizard to perform an initial NTP configuration of up to 5
server associations.
To modify an existing NTP configuration, use the NTP - Config page instead.
Note: This Wizard deletes all NTP associations that are not server associations.
Also see: NTP - Config and NTP - MD5 Keys.
WIZARDS-SNMP
Use the SNMP wizard to add or change the following SNMP v1/v2c settings:
n
n
n
Set SysLocation, SysContact and SysName

Set the Read and Write Community Strings
Add up to four v1/v2c Trap Destinations
Advanced SNMP configuration (e.g., SNMP v3) is performed on the NETWORK - SNMP and
NETWORK - Traps pages. Upon completing the Wizard, the new SNMP settings replace the
previous ones and the SNMP daemon restarts.
See also NETWORK - SNMP (on page 31) and NETWORK - SNMP Traps (on page 32).
WIZARDS-Backup
The Backup wizard guides the operator through saving the SyncServers current configuration to nonvolatile memory in the SyncServer, and optionally transfers the backup configuration to a remote location. The backup file can be used to:
n
n
'Clone' the configuration to other SyncServers with the same Software Version.
Restore the SyncServer's configuration if it is lost or becomes unusable.
Page 70..........................................................................997-01520-02 Rev. G2
WIZARDS Tab
WIZARDS-Restore
Use the WIZARDS - Restore page to restore a saved configuration from a backup file, or to
restore the factory default configuration.
Reset to Factory Defaults: Returns the SyncServer to its original factory configuration, removing ALL user-entered and operational information including password, IP addressing, GPS
position, and time zone. See SYSTEM - Factory Reset (on page 53).
Restore Last Backup from SyncServer: Restores the configuration as it was when the user created the most recent backup configuration file. The backup file is located in the SyncServers
nonvolatile memory.
Restore From USB flash drive: Restores the configuration from a backup file located on a USB
drive attached either of the USB ports on the front panel.
Restore backup from workstation hard-drive or network directory: Restores the configuration
from any backup file located on local or network drive accessible to the browser.
Note: Resetting or restoring the configuration reboots the SyncServer. If LAN1 is configured
to use DHCP, the DHCP server may assign a new IP address to LAN1. If needed, use the
front panel STATUS button to view the new IP address on the LAN1 STATUS screen.
WIZARDS-Upgrade
Use WIZARDS - Upgrade to update the SyncServer software.
SyncServer upgrade packages are available at http://www.microsemi.com/ftdsupport
and then following the links from the Support menu
Users are required to register in order to download software. Some export restrictions may
apply.
To upgrade the software, download the upgrade package file to:
n
n
A file area that is accessible to the web browser.

To a USB flash drive, or to an area where it can be copied to a USB flash drive.
Then use WIZARDS - Upgrade to copy the upgrade file to the SyncServer and perform the
upgrade.
Note: The SyncServer automatically decompresses the software upgrade ".tar" file. Please
do not decompress the ".tar" file prior to upgrading the SyncServer.
997-01520-02 Rev. G2.......................................................................... Page 71
Web Interface
HELP Tab
Select a topic from below to learn more about the HELP features of the Web Interface:
HELP-Contacts
Customer Assistance Centers are:
Worldwide (Main Number) 1-408-428-7907
USA toll-free 1-888-367-7966
Europe, Middle East & Africa 49 700 32886425
Technical Support personnel are available by phone 24 hours a day, 7 days a week, through
the Main Customer Assistance number above and from 8 a.m to 5 p.m Central European
Time, weekdays, at the Europe, Middle East and Africa number.
Customers who have purchased Technical Support Contacts may e-mail support to:
n
n
Americas, Asia, Pacific [email protected]

Europe, Middle East & Africa [email protected]
Text box
Save local support contact information here such as Microsemi representative or company
IT contact.
Note: Any information entered in the text box will be deleted when a Reset to Factory
defaults is executed.
HELP-Docs
On-Line Manual
SyncServer Manual
To view the SyncServer Manual, click the View Manual link.
To download SNMP mib to local filesystem, click the Save As... button, navigate to a folder on
your hard drive, and save the SNMP mib file
Further help can be found at the Microsemi Web Site www.microsemi.com/ftdsupport
Page 72..........................................................................997-01520-02 Rev. G2
TIME Button
The keypad/display interface displays the time, system status, and provides the following
functions:
n
n
n
n
n
n
n
Configuring and enabling/disabling the LAN1 network port.

Setting the time and entering freerun mode.
Adjusting the brightness.
Locking the keypad.
Shutting down the SyncServer.
Backing up and restoring the configuration from the USB port.
Upgrading the software from the USB port.
Overview
When the SyncServer starts, the display shows the Microsemi logo followed by booting messages. After a minute or so, the SyncServer displays the default time screen.
The following buttons are user-input devices for the keypad/display interface.
n
n
n
ENTER: Use with MENU - Applies a menu selection or function setting.

CLR: Use with MENU - Returns to the previous screen without saving changes.
Left/Right Arrow Buttons: In functions, moves the cursor left or right. In status, scrolls a
screen horizontally when "<previous:next>" is displayed.
Up/Down Arrow Buttons: In functions, increments/decrements the value the cursor is on. In
status, displays the previous/next screen.
Number Buttons: Enters a number, or selects a numbered menu item.
The following three buttons change the function of the display.

n
n
n
TIME: Changes the format and contents of the time display.

STATUS: Displays status the network ports and aspects of the SyncServer.
MENU: Displays a menu of functions.
In This Chapter
TIME Button
STATUS Button
MENU Button
73
74
76
TIME Button
Pressing the TIME button repeatedly changes the format and contents of the time display:
n
n
Large numeric time display on full screen. Hours:Minutes:Seconds

Medium numeric time display on the left, current reference and NTP Stratum on the right
997-01520-02 Rev. G2.......................................................................... Page 73
n
Small date and time, reference, and NTP stratum.
The time display also indicates a time scale:

n
If the time zone setting on TIMING - Time Zone page is set to UTC, the time display shows
"UTC" as the time scale.
If the time zone setting on TIMING - Time Zone page is set to a non-UTC (local) time zone,
the time adds AM/PM.
If the Ignore UTC Corrections from GPS Reference setting on the TIMING - HW Clock page
is enabled (selected), the time display shows "GPS" as the time scale.
Note: The TIMING - Time Zone page configures the display for UTC or local time. The TIMING HW Clock can be used to display GPS time (not recommended). Also see TIMING - Time
Zone (on page 42) and TIMING - HW Clock.
STATUS Button
Pressing the STATUS button repeatedly displays a series of status screens for:
n
n
n
n
n
n
NTP
Alarms
Network Ports
Hardware Clock
GPS Receiver
SyncServer model, serial number, software version, and software upgrade availability.
The upper right corner of each screen displays the user-configured UTC, local, or GPS time.
See TIME Button (on page 73).
NTP Status Screen

Network Time Protocol (NTP) daemon status.
Stratum: The Stratum number of the SyncServer. Stratum 1 means it is locked to a Hardware
Clock Input Reference. Stratum 2-15 means the SyncServer is locked to another NTP time
source. Stratum 16 means that the SyncServer is unsynchronized.
REF: This field identifies the "system peer". While stratum is 16, this field shows the progression of the NTP clock PLL. The field starts with a value of "INIT". Once a peer has been
selected, the clock may be stepped, in which case the reference ID field changes to "STEP".
Once the PLL is locked, the stratum is updated and the reference ID provides information
about the selected peer. When the SyncServer is operating at stratum 1, the reference ID displays the name of the Hardware Clock reference input. If the selected peer is another NTP
server, the reference ID displays the address of the server.
NTP Packet I/O: The number of NTP packets the SyncServer has replied to and initiated. The
SyncServer replies to clients that send NTP requests. The SyncServer also sends NTP
requests when the NTP daemon isn't synchronized (i.e., Sync LED is RED) and when it is
configured to synchronize to an NTP association (e.g., a Server type association).
Also see STATUS - NTP (on page 25).
Page 74..........................................................................997-01520-02 Rev. G2
STATUS Button
Alarm Status Screen

Current alarm status.
Current: The total number of active alarms. Use the left/right arrows for search through the
list of alarms.
Major: List of current major alarms
Minor: List of current minor alarms
Also see ADMIN - Alarms (on page 57).
LAN Status Screens

Multiple screens, one for each network port.
State: Shows Up if the port is enabled and Down if the port is disabled.
IPv4 Addr: Shows the address of the port.
SM: Shows the subnet mask (IPv4) or scope (IPv6).
GW: Gateway address.
IPv6 Addr: The IPv6 Link local address for this port.
Also see NETWORK - Ethernet (on page 27).
Hardware Clock Status Screen

Hardware Clock and Input Reference status.
Source: (2 fields) The first field is the name of the current reference. The second field indicates "Locked" when the Hardware Clock is synchronized to that reference.
HH:MM:SS H/W: The UTC or GPS time from the Hardware Clock, depending on the
"Ignore..." setting on the TIMING - HW Clock page.
GPS In: Indicates "Locked" if the GPS receiver is a valid source of time.
1PPS In: Indicates "Locked" if 1PPS In is a valid source of phase.
IRIG-B In: Indicates "Locked" if IRIG In connector has a valid source of time.
10MHz In: Indicates "Locked" if 10MHz In is a valid source of frequency.
Also see TIMING - HW Clock.
GPS Receiver Status Screen

GPS receiver status.
Status: Indicates "Locked" when the receiver has a valid timing solution.
Satellites: The number of satellites the receiver is using.
Antenna: The electrical state of the GPS Antenna. "Good" for a normal antenna load current.
"Open" for an open electrical circuit in the antenna. "Short" for an electrical short circuit.
997-01520-02 Rev. G2.......................................................................... Page 75
Note: If you use a GPS antenna splitter, the status can become Open while the GPS receiver
is still able to operate normally.
Lat: The latitude of the SyncServer.
Mode: The acquisition mode of the receiver: Survey (GPS receiver is determining its position), Dynamic (a user-configured mode for mobile applications) or Hold (the GPS receiver
has determined its precise location, or the user has manually entered the location).
Lon: The longitude of the SyncServer.
Also see REFERENCES - GPS.
SyncServer Status Screen

Hardware and software identification. Software upgrade availability.
Model: The model number.
S.N.: The serial number.
Version: The software "Release Version" number.
Upgrade Available: Shows "Yes" if the SyncServer detects that more recent version of software is available at www.microsemi.com.
Also see SYSTEM - General (on page 52) and SYSTEM - Upgrade (on page 53).
MENU Button
Pressing the MENU button presents a tree-structured menu of functions:
1) LAN1
1) Config
1) IPv4
1) Static Addr (Apply a static IP address)
2) DHCP (Automatically get a dynamic IP address)
2) IPv6 (Automatically configure LAN1 with an IPv6
link local address. IPv6-only mode.)
2) On/Off
1) On (Enable the LAN1 network port)
2) Off (Disable the LAN1 network port - all traffic
types)
2) Brightness (Adjust the brightness of the front panel
display)
1) Low (Extends display life)
2) Medium
3) High
3) Shutdown (Press 1 to halt the SyncServer)
1) Yes
2) No
4) USB (Backs up or restores the configuration to/from a USB
flash drive)
Page 76..........................................................................997-01520-02 Rev. G2
MENU Button
1) Backup Cfg (Backs up the current configuration of the
SyncServer to the USB drive.)
2) Restore Cfg (Applies the SyncServer configuration on
the USB drive to the SyncServer.)
Notes:
n
Using 1) LAN1, 1) Config clears all other network port settings.
997-01520-02 Rev. G2.......................................................................... Page 77

The Command Line Interface (CLI) is available on LAN1 and the Console RS-232 port.
The user can connect to LAN1 using SSH or TELNET. By default, SSH is on and TELNET
is off. Use the SERVICES - Startup web page to change these settings.
The username and login are the same as for the web interface.
Note: Physical access to the console port on the SyncServer should be controlled. The interactive bootloader could allow a malicious user to override boot parameters and gain restricted access to the device. If more information is required, contact Microsemi Customer
Assistance (on page 3).
The CLI command structure has two levels: a top-level command set of system commands
and an intrinsic help command set. Commands are entered as ASCII strings typed at the
command prompt. The specific commands available at the particular tree level can be displayed by entering a "?" ("?" followed by "Enter" on the keyboard).
The CLI interface interprets the input on a character-by-character basis. As a result, only
enough characters to uniquely identify the command need to be entered for the CLI to recognize which command you want to invoke. The CLI also accepts multiple commands on a
single line when they are separated by spaces, so you don't have to press Enter after each
command.
It is suggested that commands marked "Use all caps" be entered in all caps. This helps prevent accidental entry of those commands.
The following Top-level, and Intrinsic Help commands are available from the CLI.
Top-level Commands
GPSSTRENGTH: (Status only) Displays the GPS satellite tracking information in the following
format:
N,X1,Y1,Z1,...,XN,YN,ZN
Defined as follows:
n
n
n
n
N = Number of satellites. If one or more satellites are available, Xi,Yi,Zi follows N.

X1 = Satellite vehicle number.
Y1 = Satellite signal strength in dBW where less than -200 dBW means no signal.
Z1 = Z1 can be either T or C:
n T(racking) means the SyncServer receives the information from the satellite but
the information is not used in its timing solution.
n C(urrent) means the SyncServer currently uses satellite information in its timing
solution.
For example, no satellites:

0
997-01520-02 Rev. G2.......................................................................... Page 79

For example, one satellite with vehicle number 16:
1,16,C,-158
For six satellites:

6,12,C,-156,14,C,-155,8,T,-162,24,C,-158,18,C,161,6,C,-160
HALT: Halts the operating system. After entering the command, it prompts "Enter 'Y' to confirm". Halt the SyncServer before turning the power off. Action only command.
REBOOT: Halts and reboots the operating system. After entering the command, it prompts
"Enter Y to confirm". Action only command.
DEFAULTS: Replaces the current configuration of the SyncServer with the factory default configuration. After entering the command, it prompts Enter Y to confirm. The command also
halts and reboots the SyncServer. Action only command.
IPV4ADDRESS <aaa.bbb.ccc.ddd>: Displays or sets the LAN1 IPv4 address. Without input, the
command displays the current IPv4 address. With input, the command sets the new IPv4
address. Query and action command.
IPV4MASK <aaa.bbb.ccc.ddd>: Displays or sets the LAN1 IPv4 subnet mask. Without input, the
command displays the current IPv4 subnet mask. With input, the command sets the new
IPv4 subnet mask. Query and action command.
IPV4GATEWAY <aaa.bbb.ccc.ddd>: Displays or sets the LAN1 IPv4 gateway. Without input, the
command displays the current IPv4 gateway. With input, the command sets the new IPv4
gateway. Query and action command.
IPV4DHCP: Enables DHCP for LAN1. Action only command.
IPV6AUTO: Enables the automatically generated IPv6 link local address for LAN1. Action only
command.
HTTP <on|off>: Without input, the command returns the current status of the SyncServer http
daemon (running or stopped). Use input on or off to start or stop the SyncServer http daemon. Query and action command.
DISP <time>: Resets the display immediately. Use in rare instances when display and keypad
freeze to avoid waiting (<24 hours) for it to clear on its own. After command is entered, it
prompts Do you wish to reset the front panel display? <Y/N>:
SETTIMEOFYEAR <time>: Sets the current time in UTC. The <time> input format can be any
one of the following
mm/dd/yyyy hh:mm:ss.x
yyyy ddd hh:mm:ss.x
mm dd yyyy hh:mm:ss.x
hh:mm:ss.x
Enter the command without any input, it displays the allowable input time format. Action only
command.
ADJUSTTIMEOFYEAR <seconds>: Adjust the current time by a user determined number of
seconds. The input can be a positive or a negative integer. If the input is negative, the time is
adjusted backward. Action only command.
INTRINSIC HELP: Traverse to the intrinsic command tree.
Page 80..........................................................................997-01520-02 Rev. G2
Intrinsic Help Commands

Intrinsic help commands are commands that can be used in any tree level as a basic shell
command tool. Below is the list of available intrinsic commands.
pop: Moves the command shell to the previous level. When issued from the main shell directory (i.e., the root) this disconnects the session.
root: Moves the command shell to point to the main shell directory. This is a convenience command for navigating the command shell. The command root pop <Enter> disconnects the
session.
exit: Exits the Telnet client session while it is active. This command has no effect if it is
executed from a serial session.
trace: Displays the current contents of the trace buffers. Most of the commands currently do
not use the trace buffer facility. It is normal that the trace buffers are empty.
clear: Clears the trace buffers.
stamp: Queries the time stamp of the internal operating system clock, which is set to zero
when the SyncServer is powered on. The time stamp of the internal operating system clock
is in milliseconds.
history: Displays the last fifteen commands that have been executed.
pause <milliseconds>: Waits for user specified number of milliseconds and then executes the
next command if it is provided in the same command line following the number. For example,
the pause 5000 history command would wait for five seconds and then execute the history
command. Input any integer number as the number of milliseconds to pause.
repeat <count>: This commands repeats execution user specified number of times of a command specified before it. For example, the GPSSTRENGTH repeat 5 executes
GPSSTRENGTH five times.
# : (pound sign followed by a space) Creates a comment from the space to the end-of-line
character. This is useful for adding a comment to a command being recorded in a logfile. For
example, GPSSTRENGTH pause 1000 repeat 1000 # monitor GPS sats <enter>. Also,
the command could be used to simply have the system ignore the remaining part of a long
string of commands. For example, ipv4address 192.168.2.2 ipv4mask 255.255.255.0 #
gateway 192.168.2.1 <enter> will set the IP address and subnet mask but not the gateway.
?: (question mark) Displays commands available at the current tree level.
Command Examples
Below are a few select examples of commands.
DEFAULTS example
Entering DEFAULTS replaces the current configuration of the SyncServer with the factory configuration. Enter "Y" to confirm. For example:
1 ? DEFAULTS
Restore SyncServer default factory configuration? Enter "Y" to confirm:
Y
REBOOT example
997-01520-02 Rev. G2.......................................................................... Page 81

Entering REBOOT halts and reboots the SyncServer's operating system. Enter "Y" to confirm.
For example:
1 ? REBOOT
Reboot SyncServer operating system? Enter "Y" to confirm: Y
HALT example
Entering HALT halts the operating system. Do this before turning the power switch off. Enter
"Y" to confirm. Enter "Y" to confirm. For example:
> HALT
Halt SyncServer operating system? Enter "Y" to confirm: Y
IPV4ADDRESS example
Entering IPV4ADDRESS displays/sets the IPv4 address. For example:
1 ? IPV4ADDRESS
192.168.47.150
2 ? IPV4ADDRESS 192.168.46.144
IPV4MASK example
Entering IPV4MASK displays/sets the IPv4 subnet mask. For example:
3 ? IPV4MASK
255.255.255.0
4 ? IPV4MASK 255.255.0.0
IPV4GATEWAY example
Entering IPV4GATEWAY displays/sets the IPv4 gateway address. For example:
5 ? IPV4GATEWAY
192.168.47.1
6 ? IPV4GATEWAY 192.168.46.1
Page 82..........................................................................997-01520-02 Rev. G2
Specifications
In This Chapter
Status LEDs
Keypad/Display
USB Ports
VAC Power Supply
VDC Power Supply
Timing Holdover
GPS Receiver
Safety Standards
EMC Standards
Environmental
Maintainability
Shock and Vibration
Console RS-232 Port
1PPS Out
1PPS In
10MHz Out
10MHz In
IRIG-B Out
IRIG-B In
Sysplex Out
Network Ports
Network Protocols
997-01520-02 Rev. G2.......................................................................... Page 83
84
84
85
85
85
85
86
86
87
87
88
88
88
89
89
89
90
91
91
92
92
92
93
93
94
95
95
96
Specifications
Status LEDs
The four tricolor LEDs provide the following status information:
Red
Sync
Orange
SyncServer is not
SyncServer is synsynchronized to a ref- chronized to a remote
erence.
NTP server.
NTP Stratum 16.
NTP Stratum 2-15.
Network Link failure on the

NTP
Alarm
Link failure on the

LAN1.
LAN2, or LAN3.
>3200 NTP packets > 2000 packets per
per second.
second.
Major Alarm.
Minor Alarm.
Green
Dark
SyncServer is synchronized to an Input

Reference.
NTP Stratum 1.
Power off.
All configured ports

Power off.
operational.
NTP activity within the No NTP activlast second.
ity in the last
second.
No Current/Enabled
Power off.
Alarms.
See the Troubleshooting (on page 115) topics to resolve problems with Red and Orange
LEDs.
Keypad/Display
The keypad/display displays the time, status information, and provides functions described
by Keypad/Display Interface (on page 73).
Keypad
Description:19-button firm silicone rubber keypad
Functionality:User input device
Arrow keys: Left, Right, Up, Down
Numeric keys: 0 through 9
Command keys:ENTER, CLR, TIME, STATUS, MENU
Display
Description:256 x 32 pixel vacuum fluorescent display (VFD)
Functionality:Displays time, status, and functions. User-configurable brightness levels.
Page 84..........................................................................997-01520-02 Rev. G2
USB Ports
USB Ports
Description:Two USB 2.0 ports (USB 1, 2).
Functionality:Connects with a USB flash drive device, which can be used for loading software
upgrades to the SyncServer, as well as for backing up and restoring the SyncServer configuration.
Connection:Requires a compatible USB memory device, such as a SanDisk cruzer micro USB
device (recommended). Not all USB flash drives are compatible with the SyncServer's USB
ports.
Also see:Keypad/Display Interface (on page 73), SYSTEM - Upgrade (on page 53),
WIZARDS - Upgrade (on page 71), WIZARDS - Backup (on page 70), WIZARDS - Restore
(on page 71).
VAC Power Supply

Description:Universal type VAC Power supply
Connector:IEC 320
Input Voltage Range:90-264 VAC
Input Frequency Range:47-63 Hz
Max. Power:
Initial Power On Continuous
With Rubidium Osc
45 watts
35 watts
Without Rubidium Osc 25 watts
21 watts
VDC Power Supply

This topic applies to the 48 VDC Operation Model only.
Description:VDC Power Supply
Connector:Two three-position screw terminal blocks
Input Voltage Range:40-60 VDC, 50 watts maximum, 1.5 amps
Isolation, Ground:Input is fully floating. Either input polarity may be strapped to chassis ground
at the input terminal block.
Isolation:Input to output 1,000 VAC minimum
Timing Holdover
Temperature Compensated Crystal Oscillator (TCXO)
997-01520-02 Rev. G2.......................................................................... Page 85
Specifications
Feature:Standard
Drift rate:21 milliseconds/day typical after having been locked to a stable reference for at least
30 minutes. (Assumes less than 5C temperature change over this time period).
Oven Controlled Crystal Oscillator (OCXO)

Feature:Option
Drift Rate:1 millisecond/day typical after having been locked to a stable reference for at least 1
hour. (Assumes less than 5C temperature change over this time period).
Rubidium Oscillator
Feature:Option
Drift Rate:6 microseconds/day typical for a Model S250 and 25 microseconds/day typical for a
Model S200 after having been locked to a stable reference for at least 1 hour. (Assumes less
than 5C temperature change over this time period).

Synchronization
Source
Timing Accuracy
to Reference
GPS, 4 or more satellites

tracked
GPS, 1 satellite tracked,
position known within 200m
NTP Client Mode, Local
server
IRIG-B
1PPS
50 nS RMS, 150 nS
peak
1 uS peak
Comments
2 mS peak
Position from satellite fix or entered by the

user.
Local server on same subnet.
10 uS peak
100 nS peak
Relative to input signal.

Relative to input signal.
The stability of the 1PPS, 10MHz, and IRIG-B outputs depend on the optional oscillator
installed.
GPS Receiver
Description:The internal GPS Receiver is the preferred reference for the SyncServer's Hardware Clock. The GPS receiver must be connected to a 12-VDC capable antenna using the GPS
Ant connector.
Note: The GPS receiver is only available in the S200 and S250 models.
Connector:
GPS Ant, BNC female, 12 VDC antenna power feed, detects Open and
Short circuits.
Page 86..........................................................................997-01520-02 Rev. G2
Safety Standards
Frequency:
Code:
Tracking:
Position Accuracy:
1PPS Accuracy:
Time standard:
Signal strength:
n
Cabling options:
n
n
1575.42 MHz (L1 signal)

Coarse Acquisition (C/A) code
Up to 12 satellites. All 32 PRN's.
Typically <10m w. four satellites. Available from web interface.
50 nS RMS, 150 nS Peak to UTC-USNO
UTC
1 sat -166 dBW to acquire, and -171 dBW to track.
150 ft. of Belden 9104 (RG-59 type)
300 ft. with inline amplifier
Compatible with down/up converter
Also see:
n
n
GPS Antenna
GPS Cable Configurations/Options (see "Distance Between Antenna and Receiver"
on page 105)
Safety Standards
Meets the following safety standards:
n
n
n
n
n
n
n
73/23 EEC CE Low Voltage Safety Directive

EN 60950-1:2001
UL 60950-1:2003
CSA 22.2 60950-1:2003
IEC 60950-1:2001
AS/NZ 60950-1:2003
PSE Japan
EMC Standards
Meets the following EMC standards:
n
n
n
n
n
n
n
n
n
FCC Part 15 Subpart B

2004/108/ECCE EMC Directive
EN55022 (1998) EMC Emissions for ITE, Class A
EN55024 (1998) EMC Immunity for ITE
EN61000-3-2 (2000)Harmonic Current Emissions
EN61000-3-3 (1995)Voltage Fluctuations and Flicker Emissions
VCCI: April 2000Japan EMC Standard
ICES-003Canada EMC Standard
AS/NZS CISPR 22:2002Australia/New Zealand EMC Standard
997-01520-02 Rev. G2.......................................................................... Page 87
Specifications
Note: In some cases, for FCC and CE EMC Radiated Emission Compliance, a ferrite EMI
suppressor (Fair Rite P/N 0444164951 or equivalent) may need to be placed on the unit end
of cables connected to the BNC Connectors. Please contact Microsemi Customer Assistance (on page 3) for additional information.

This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a
domestic environment, radio interference may occur, in which case the user may be required
to take corrective actions.
Environmental
Operating Temp:0 to +50 C (+32 F to +122 F)
Storage Temp:-10 to +70 C ( 14 F to +158 F)
Humidity:0 - 95%, non-condensing
Altitude:0 - 4000 meters AMSL
WARNING: Install the SyncServer to allow adequate airflow through and around the unit.
Microsemi recommends leaving 1.4 in. (3.6 cm) above and below the SyncServer or
enough space to allow 5 CFM.
AVERTISSEMENT : Installez le SyncServer pour permettre un flux d'air autour et a travers l'unit. Microsemi recommande de laisser 1.4 in. (3.6 cm) au-dessus et au-dessous du
SyncServer ou assez d'espace pour permettre 5 CFM.
Maintainability
This unit contains no user-serviceable parts. Please return to Microsemi for servicing.
The SyncServer functions without user adjustments throughout its life span.
Page 88..........................................................................997-01520-02 Rev. G2

The SyncServer contains a Lithium Battery that maintains the system's Real Time Clock
(RTC) when the SyncServer's power is off. Replace the Lithium Battery only with the same
or equivalent type. Do not dispose of the Lithium Battery in a fire or incinerator, or the battery
may explode. Follow disposal regulations in your area for Lithium Battery disposal.
ATTENTION : Le SyncServer contient une batterie de lithium pour maintenir l'horloge en
temps rel pendent que le courant est debranch. Remplacez la batterie de lithium seulement avec une batterie de type quivalent. Ne vous dbarrassez pas de la batterie de lithium
dans un feu ou un incinrateur, car la batterie pourrait exploser. Dbarrassez-vous de la batterie usage de lithium selon les instructions du fabricant.

The SyncServer is self-monitoring during normal operation. To the extent possible, any failures in the unit are isolated, to differentiate them from input signal failures, and reported. The
SyncServer provides debug and troubleshooting variables of the current status of the unit at
the request of an administrator.
Declaration of Conformity
In accordance with ISO/IEC GUIDE 22 and EN 45014:
Microsemi, Inc.
3750 Westwind Blvd.
Santa Rosa, Ca 95403 USA
Declares under our sole legal responsibility that the SyncServer Network 1520R-SXXX Network Time Server (Both AC and DC Models):
n
n
n
n
MODEL 1520R-S200, MODEL 1520R-S200-DC

MODEL 1520R-S250i, MODEL 1520R-S250i-DC
MODEL 1520R-S250, MODEL 1520R-S250-DC
MODEL 1520R-S300, MODEL 1520R-S300-DC, MODEL 1520R-S300-RB, MODEL
1520R-S300-RB-DC
MODEL 1520R-S350, MODEL 1520R-S350-DC, MODEL 1520R-S350-RB, MODEL
1520R-S350-RB-DC
CONFORMS TO THE FOLLOWING EUROPEAN UNION DIRECTIVES:

Safety
2006/95/EC Low Voltage Directive
n
73/23/EEC Low Voltage Safety as amended by 93/68/EEC
997-01520-02 Rev. G2.......................................................................... Page 89
Specifications
IEC 60950-1:2001 (1st Edition)
n EN 60950-1:2001
Electromagnetic Compatibility
n
2004/108/EC Electromagnetic Compatibility

EN55022 (1998) EMC Emissions for ITE, Class A
EN55024 (1998) EMC Immunity for ITE
n EN61000-3-2 (2000) Harmonic Current Emissions
n EN61000-3-3 (1995) Voltage Fluctuation and Flicker Emissions
WEEE
n
n
Waste Electrical and Electronic Equipment Directive (WEEE) 2002/95/EC

The SyncServer Model 1520R_SXXX is considered WEEE Category 3 (IT and Telecommunication Equipment) as defined by the WEEE Directive and therefore falls within the
scope of the WEEE Directive.
For more information about Microsemi's WEEE compliance and recycle program, please
visit Microsemi's website at http://www.mircrosemi.com
RoHS
Restriction of the Use of Certain Hazardous Substances Directive 2002/95/EC
The SyncServer Model 1520R_SXXX is considered WEEE Category 3 (IT and Telecommunications Equipment) as defined by the WEEE Directive and therefore falls within the
scope of the RoHS Directive.
These units are RoHS Compliant except that they will be manufactured using the RoHS Directive exemption allowing the use of lead in "solders for servers, storage and storage array
systems, network infrastructure equipment for switching, signaling, transmission as well as
network management for telecommunications". Reference RoHS Directive Annex Point 7
as amended by 2005/747/EC.
Note: This certification applies to all standard options and accessories supplied with the SyncServer System
Signature
First Date of Marketing with CE Mark: 31 August 2005
I declare that the equipment specified above conforms to the above Directives and Standards.
Signed: Robert Mengelberg, Compliance Engineer
Date: 12 August 2008
Shock and Vibration

The SyncServer has been designed and tested to withstand the following shock and vibration per Telcordia GR-63 Specifications:
Page 90..........................................................................997-01520-02 Rev. G2
Console RS-232 Port

Packaged Equipment Shock (Drop):Packaged for shipment. Drop from 29.5 in. - Surface, edge
and corner drops
Unpackaged Equipment Shock (Drop):Unpackaged. Drop from 3.9 in. - Surface, edge and corner
drops
Office Vibration Environment:Locked to 0.1 g - In equipment rack
Transportation Vibration:To 1.5 g - Packaged for shipment
Console RS-232 Port

Description:A bi-directional EIA standard RS-232C serial port (Console RS-232) located on the
front panel.
Functionality:Provides access to a the command line interface for limited status and configuration of the SyncServer.
Connection:DCE (Data Communications Equipment). (Use a "straight through" serial cable, not
a "null modem" crossover cable.)
Data Rates:9600 baud
Parity:None
Data Bits:8
Stop Bits:1
Connector:Female 9-pin D subminiature
Also see:Command Line Interface (on page 79)
Pin Assignment (Pinout):
n 1N/C
n 2Tx
n 3Rx
n 4N/C
n 5GND
n 6N/C
n 7CTS
n 8RTS
n 9N/C
1PPS Out
Description:1PPS Out, a female BNC connector mounted on the rear chassis, provides a once
per second pulse that is synchronous with the SyncServer's Hardware Clock.
Note: This feature is not available on the S200 model.
Connector:BNC female (1PPS Out)
Amplitude:TTL Levels into 50 Ohms
Duty Cycle:50% nominal
On Time Edge:Rising
997-01520-02 Rev. G2.......................................................................... Page 91
Specifications
1PPS In
Description:1PPS In, a female BNC connector mounted on the rear chassis, accepts a once per
second pulse from an external reference into the SyncServer's Hardware Clock. For the SyncServer to maintain lock to this signal, the stability of the 1PPS input must be better than the
pull-range of the system oscillator.
Connector:BNC female (1PPS In)
Amplitude:TTL Levels
Pulse Width100 nS minimum
On Time Edge:Rising
Impedance:270 Ohms
Typical system oscillator pull-ranges:
n TCXO 1E-6 (1 ppm)
n OCXO 5E-7 (0.5 ppm)
n Rubidium 1E-9 (1 ppb)
Note: If the 1PPS In signal is too noisy, the Hardware Clock may not be able to lock to it.
10MHz Out
Description:10MHz Out, a female BNC connector mounted on the rear chassis, provides a
10MHz signal from the SyncServer's Hardware Clock.
Connector:BNC female (10MHz Out)
Amplitude:> 3 Vpp and < 7 Vpp into 50 Ohms
Frequency:10MHz
Wave Shape:Sine Wave
10MHz In
Description:10MHz In, a female BNC connector mounted on the rear chassis, accepts a 10MHz
signal from an external frequency reference into the SyncServer's Hardware Clock. For the SyncServer to maintain lock to this signal, the stability of the 10MHz input must be better than the
pull-range of the system oscillator.
Connector:BNC female (10MHz In)
Amplitude:1 Vpp to 8 Vpp
Frequency:10MHz
Page 92..........................................................................997-01520-02 Rev. G2
IRIG-B Out
Wave Shape:Sine Wave or Square Wave
Impedance:> 50 k Ohms
n TCXO 1E-6 (1 ppm)
Note: If the 10MHz In signal is too noisy, the Hardware Clock may not be able to lock to it.
IRIG-B Out
Description:IRIG Out, provides a selected time code from the SyncServer's Hardware Clock. The
time code format is selected via the Web interface. Amplitude Modulated (AM) outputs are supported from the IRIG Out BNC. Also see REFERENCES - IRIG-B (on page 51).
Connector:IRIG Out, BNC female
DCLS Amplitude: TTL into 50 ohms
AM Amplitude:3.5 0.5 Vpp into 50 Ohms
AM Ratio:3:1 10%
Selectable Time Code Output Formats:
n
n
n
IRIG-B
IRIG-B (Legacy TrueTime)
IRIG-B with IEEE 1344 extension
IRIG-B In
Description:IRIG In accepts a time code for input from an external timing reference into the SyncServer's Hardware Clock. The time code format is selected via the Web interface. Supports
only amplitude modulated (AM) IRIG-B inputs. For the SyncServer to maintain lock to this signal, the stability of the time code input must be better than the pull-range of the system oscillator. Also see REFERENCES - IRIG-B (on page 51)
Connector:IRIG In, BNC female
DCLS Amplitude:<1.5 V for logic 0, >2.0 V for logic 1
AM Amplitude:1 to 8 Vpp
AM Ratio:2:1 to 4:1
Impedance:>5k Ohms
997-01520-02 Rev. G2.......................................................................... Page 93
Specifications
n TCXO 1E-6 (1 ppm)
Note: If the inbound signal is too noisy, the Hardware Clock may not lock to it.
Selectable Time Code Input Formats:
n IRIG B AM
n IRIG-B
n IRIG-B (Legacy TrueTime)
n IRIG-B with IEEE 1344 extensions
n Auto
Sysplex Out
Summary:The Sysplex Timer port outputs serial time strings for IBM mainframe Sysplex systems. The Sysplex Timer provides a common time reference across all the members of an IBM
Sysplex. The Sysplex Timer is a key component when systems on multiple CPCs share access to
the same data. Also see TIMING - Sysplex (on page 47).
Description:Sysplex Out is a male 9-pin D connector mounted on the rear chassis that transmits
Time of Day (TOD) with carriage return on time to an attached Sysplex-compatible device. Configured as DTE (Data Terminal Equipment). Configurable via the Web interface. Sysplex typically uses a "null-modem" serial cable (not supplied) for interconnection with other Sysplex
equipment.
Connector:male 9-pin (Sysplex Out)
Data Rates:9600 bps
Parity:Even, Odd, or None
Data Bits:8
Stop Bits:1
Pin Assignment:
n 1N/C
n 2Rx
n 3Tx
n 4N/C
n 5GND
n 6N/C
n 7RTS
n 8CTS
n 9N/C
Format:IBM 9037 Sysplex Timer (First Protocol)
Level:RS-232
Accuracy:<10 mS RMS
Page 94..........................................................................997-01520-02 Rev. G2
Network Ports
Phasing:Carriage return on-time marker
Control:Manual or Automatic start/stop, parity setting, flywheel quality character
String:<SOH>DDD:HH:MM:SSQ<CR><LF>
Where:
n
n
n
n
n
n
n
n
n
<SOH>Start of Header
DDDDay
:Colon separator
HHHours
MMMinutes
SSSeconds
QTime Quality
<CR>Carriage Return (On-time marker)
<LF>Line Feed
Network Ports
Description:Three 10/100 Mbps Ethernet ports (LAN1, LAN2, LAN3).
Connector:Three standard RJ-45 8-pin connectors
Frame Format for LAN1, LAN2, LAN3:
n IEEE 802.3 (10Base-T at 10 Mbps)
n IEEE 802.3u (Fast Ethernet at 100 Mbps)
Roles:
n
LAN1:
Web interface (HTTP), command line interface (TELNET)

n The default port for most NTP functions.
n DNS, SMTP, SNMP
All ports respond to NTP (port 123), TIME (port 37), and DAYTIME (port 13) requests.
n
Factory default static IPv4 addresses:

n
n
n
LAN1192.168.0.100
LAN2192.168.0.101
LAN3192.168.0.102
Note: The SyncServer's network ports require Category 5 (or better) network cable.
Network Protocols
The SyncServer supports the following protocols:
n
n
n
n
NTP (v2 - RFC1119, v3 - RFC1305, v4 - No RFC) (Port 123)

NTP Unicast, Multicast
SNTP v4 for IPv4, IPv6 and OSI (RFC 4330)
TIME (RFC868) (Port 37)
997-01520-02 Rev. G2.......................................................................... Page 95
Specifications
n
n
n
n
n
n
n
n
n
n
DAYTIME (RFC867) (Port 13)

HTTP/SSL/HTTPS (RFC2616)
DHCP (RFC2131)
SSH/SCP (Internet Draft)
SNMP v1/v2/v3 (RFC3584)
MIB II (RFC1213)
Telnet (RFC854)
MD5 Authentication (RFC1321)
SMTP Forwarding
IPv4 and v6

The SyncServer web interface is compatible with:
n
n
n
Internet Explorer 6.0 and 7.0 on Windows XP

Internet Explorer 7.0 on Windows Vista
Firefox 2.0/3.0 on Windows and Linux
Page 96..........................................................................997-01520-02 Rev. G2
Installation Guide
Tasks
In this section
Installation Guide
Unpacking
Rack Mounting
Grounding the SyncServer
WARNING: Grounding
Connecting VAC Power
CAUTION: VAC Power
Connecting VDC Power
WARNING: VDC Power
Using GPS
Upgrading System Software
Adding NTP Servers to the NTP Associations List
Recovering a Password
Configuring LAN1
Logging in to the Web Interface
Using the 1st Setup Wizard
Configuring the Network Ports
Adding Server Associations
Installation Guide
To install the SyncServer in a production environment, or some other of long-term installation, follow the steps in this Installation Guide. To get the SyncServer up and running
quickly in order learn about its features, consult the Quick Start Guide (on page 13).
Unpacking
Open the SyncServer packaging carefully to avoid damaging its contents.
Verify that the box contains the following standard items:
n
n
n
n
Printed Quick Start Guide

SyncServer Network Time Server
VAC Power cord (unless 48VDC option is ordered)
GPS antenna kit
n 12V GPS antenna
n PVC antenna-mounting tube
n 50 ft. Belden 9104 coaxial cable
997-01520-02 Rev. G2.......................................................................... Page 97
97
97
98
98
98
98
99
99
99
100
107
109
110
111
111
112
112
112
113
Tasks
2 pipe clamps
Product CD (contains the User Guide and other supporting documentation)
Standard serial cable
Standard 6 ft. network cable
n
n
n
n
Please also verify that the box also contains any options purchased with the SyncServer.
If the box is missing any items, please contact Microsemi Customer Assistance (on page
3).
RackMounting
The SyncServer is designed for mounting in a standard 19-inch (48.26 cm) rack. Follow the
rack manufacturer's instructions for mounting the SyncServer.
Avoid the following conditions:
n
Elevated Operating Temperatures: If the SyncServer is installed in a closed or multi-unit rack

assembly, the ambient temperature of the rack environment may be greater than the SyncServer's Maximum Operating Temperature of 50C/122F. Install the SyncServer in an
environment that is compatible with the SyncServer's operating temperature range,
which is 0 C to 50 C, or 32 F to 122 F
Reduced Air Flow: Position the SyncServer with enough space above, below, and adjacent to the chassis to allow an adequate flow of air so that it may operate safely.
Microsemi recommends leaving 1.4 in. (3.6 cm) above and below the SyncServer or
enough space to allow 5 CFM air flow.
Uneven Mechanical Loading: Mount the equipment so as to avoid uneven mechanical loading that could cause hazardous conditions.
Circuit Overloading: Observe the power ratings on the SyncServer's nameplate and the
additional load the SyncServer may place on the supply circuit.
Proper Grounding: Maintain reliable grounding (earthing) of rack-mounted equipment.
Groundingthe SyncServer
n
n
n
For VAC power, verify that a properly grounded three-prong outlet is available for the
standard power cord.
Connect the Chassis Grounding Screw on the rear panel to a reliable earth ground.
Verify that the equipment rack and other equipment are grounded correctly.
WARNING:Grounding
Microsemi recommends that the user connect the chassis grounding screw to a reliable
earth ground.
AVERTISSEMENT : Microsemi recommande que le chssis soit reli une terre fiable.
ConnectingVACPower
For units equipped with the standard VAC power supply:
n
Verify that the power switch, located on the rear panel, is off. (Press "O".)
Page 98..........................................................................997-01520-02 Rev. G2
Installation Guide
n
Connect the VAC Input connector on the rear panel to a grounded three-prong outlet
using the standard power cord supplied.
CAUTION:VACPower
n
The VAC Power Supply specification reflects the overall Power Supply ratings. For UL
and CE compliance the Power Supply must only be operated at 100 240 VAC, 50-60
Hz.
The SyncServer should only be plugged into a grounded receptacle.
ATTENTION :
n
Les spcifications d'approvisionnement de courant alternatif ci-dessus refltent les estimations globales d'alimentation d'nergie. Pour la conformit d'UL et de CE l'alimentation
d'nergie doit tre seulement opre 100 - 240 VCA, 50-60 hertz.
Relier le SyncServer une prise de courant avec contact adquat de mise la terre.
ConnectingVDCPower
For units equipped with the optional 48 VDC power supply:
n
Use a 14 amp DC circuit breaker in series with the DC power source. Do not connect the
unit directly to a DC power source without the breaker.
Provide a circuit disconnect in series with the VDC Power input. The SyncServer DC
option does not include a power switch
The minimum recommended wire size is 14 AWG (1.5mm2) for DC power source hook
up. Dont forget to tighten the terminal screws on the input power block.
The VDC Power supply in the SyncServer is DC isolated. The VDC Power inputs are
polarity protected so reversed DC connections will not power the unit but will also not
harm the unit.
Connect VDC Power to the PRI or optionally the SEC set of terminals observing correct
polarity (+, -). The SEC set of terminals has been provided for connections to a secondary power source. Note that the PRI and SEC power connections are simply diode
ORed, so the highest voltage source will be powering the unit.
The PRI and SEC ground terminals on the VDC Power input block are connected to the
chassis. These terminals are normally used to connect to the VDC Power return line.
Note: The 48 VDC Operation Model is supplied with two 48 VDC inputs to accommodate
input from an alternate VDC Power Source. Because of diode switching, the polarity can be
plus-plus, plus-minus, minus-plus, or minus-minus.
WARNING:VDCPower
For the 48 VDC model of the SyncServer:
n
n
n
Use a disconnect device, such as a switch, with the appropriate voltage/current rating
when connecting a VDC Power source.
Only use the unit in an restricted area.
The screw torque on the Power Terminal Block is 4.5 to 5.3 inch pounds.
997-01520-02 Rev. G2.......................................................................... Page 99
Tasks
n
The unit chassis must be grounded for proper safety.
AVERTISSEMENT :
Sur le 48 VDC modle du SyncServer:
n
n
n
n
Utilisez un dispositif de dbranchement, tel qu'un commutateur, avec le classement de

tension/courant appropri en connectant une source de pouvoir de DC.
Employez seulement l'unit dans un secteur avec l'accs limit.
Le couple de vis sur le TB de puissance est livres de 4.5 5.3 pouces.
Le chssis d'unit doit tre fondu pour la sret approprie
UsingGPS
This section guides the user through the process of selecting a good site for the GPS
antenna, installing the antenna, and how to use GPS when a good site isn't available.
Safety Considerations
n
n
n
n
n
Avoid electrocution and RF safety hazards such as power lines and high-energy radio
transmission antennas.
Where potential hazards exist, have a qualified technician perform the installation.
Observe local codes and regulations.
Use a lightning arrestor when needed.
Antennas not rated for 12 VDC may be damaged when connected to the SyncServer.
The GPS antenna supplied with the Receiver is rated for 12 VDC.
Safe Antenna and Cable Connection: An outside antenna or cable system must be properly
grounded to provide some protection against built up static charges and voltage. Section
810 of the National Electrical Code, ANSI/NFPA 70 (In Canada, part 1 of the Canadian
Electrical Code) provides information regarding proper grounding of the mast and supporting structure, grounding of the lead-in wire to an antenna discharge unit, size of
grounding conductors, location of antenna discharge unit, connection to grounding electrodes, and requirements for the grounding electrode.
Keep Antenna Clear of High Voltage Power Lines or Circuits: Locate an outside antenna system well away from power lines and electric light or power circuits so it will never touch
these power sources should it ever fail. When installing an antenna, absolutely never
touch power lines, circuits, or other power sources, as this could be fatal.
Selecting a Site for the Antenna

Roof Antenna Placement: When selecting a site for the roof antenna, find an outdoor location
that provides the best visibility of the sky and horizon. In most cases, this means locating the
antenna in a high location, such as a roof top. Avoid obstructions that could block GPS satellite signals and delay acquisition.
A short mounting mast and hose clamps are provided with the roof antenna to mount the
antenna to a pole or the peak of a building. The antenna mounting mast and clamps are well
Page 100..........................................................................997-01520-02 Rev. G2
Installation Guide
suited to attach the antenna to a vent pipe or mast affixed to the roof. The pipe must be rigid
and able to withstand high winds without flexing.
A typical roof antenna mounting.

GPS Receivers can be susceptible to reflected GPS signals called multipath signals. Multipath interference is caused by reflected signals that arrive at the antenna out of phase with
the direct signal. This interference is most pronounced at low elevation angles from 10 to 20
degrees above the horizon. The height of the mast/antenna may be extended upward to
lessen multipath interference. The antenna should also be at least three to six feet (1-2 m)
from a reflecting surface.
Use the criteria below to select a good outdoor site for the GPS antenna.
The best locations provide:
n
n
n
n
n
Unobstructed views of the sky and horizon.

Low electro-magnetic interference (EMI) and radio frequency interference (RFI) - away
from high-power lines, transmitting antennas, and powerful electrical equipment.
Convenient access for installation and maintenance.
Reasonable access for the antenna cable to reach the SyncServer.
Safety from hazards to people and equipment.
Avoid:
n
n
n
n
Overhanging foliage
Blocked views
Strong EMI RFI interference
Multipath interference (caused by adjacent structures that reflect GPS signals)
Mounting structures:
n
GPS antenna masts, vent pipes, or railings are usually satisfactory.
997-01520-02 Rev. G2.......................................................................... Page 101
Tasks
n
Radio towers may require the services of a specialist, and may be subject to signal interference.
Must be able to withstand very high winds.
If a good site is not available, consult Operating in "Window Mode" (on page 102).
Installing the GPS Antenna

1. Observe all relevant safety precautions and building code regulations. Avoid:
n Electrocution, RF, lightning, and falling hazards.
n RFI and EMI sources such as transmitting antennas.
n Crimping or making sharp bends in the cable.
2. Mount the standard L1 GPS antenna at the selected site:
n Position the GPS antenna vertically, with its top pointing toward the sky, and the
PVC mounting mast and connector pointing down.
n Secure the PVC mounting mast to the structure using the pipe clamps provided
with the antenna kit.
3. Run the antenna cable or cables to the SyncServer. Use a lightning arrestor and grounding, as required to meet building and safety codes.
4. Connect the antenna cable to the GPS Ant connector on the rear panel.
Note: Microsemi recommends posting a "Do not paint" notice to prevent the GPS antenna
from being painted accidentally.
Tips:
n
The user can access the connector underneath the GPS antenna by removing the four
recessed screws in the lower half of the GPS antenna with a Phillips-head screwdriver. It
is a relatively easy task and does not violate the weatherproofing design of the antenna.
Typically, users do this to attach an optional in-line amplifier inside the PVC mounting
mast or to replace the standard cable with a longer one. (Avoid unscrewing the PVC
mounting mast from the base of the GPS antenna as this may require a vice and lots of
torque.)
When extending the length of the cable, observe the recommended configurations in
GPS Cable Configurations/Options (see "Distance Between Antenna and Receiver"
on page 105). Avoid exceeding the recommended lengths by combining the standard 50
foot (15.24 m) cable with the extended-length cable.
Operating in "Window Mode"

The SyncServer Network Time Servers can provide can provide excellent synchronization to
UTC if the GPS receiver has an accurate fix on its position and one current GPS satellite
most of the time. This capability is known as Window Mode.
When a good antenna site isn't available, the user may be able to use sites with limited visibility of GPS satellites and reduced signal strength, such as:
n
n
Indoors, in a window or skylight.

Outdoors, on a balcony railing, building corner, or surrounded by tall structures (limited
view)
Page 102..........................................................................997-01520-02 Rev. G2
Installation Guide
Window Antenna Placement

For window mounted antenna installations, use the window with the best view of the sky. For
windows with equivalent views, orientations that face the equator are preferred. Generally
more satellites will be in view toward the equator than away from it. East or west facing windows will also work. Polar facing windows will also work but in general are not preferred. Windows that have the best view of the sky are always preferred regardless of orientation.
A typical window mounting with the antenna is shown in the preferred window.
Guidelines
For best results with window mode:
n
n
n
n
Position the antenna near the lower windowsill. This improves upward visibility of the sky.
If multiple sites are available, choose the one with the widest view of the sky and tilt the
antenna toward the "opening".
On the side of a building, the corners offer better visibility (270 degrees) than flat walls
(180 degrees).
A SyncServer equipped with the high-stability Rubidium oscillator option can provide precise time for extended periods while GPS is unavailable.
Secure the antenna so it won't fall or get knocked out of position.
To improve signal strength, test different window locations, shorten the antenna cable
length, avoid unnecessary connectors, and use an in-line amplifier option. (Signal
strength is visible on the STATUS - GPS page.)
Avoid windows with metallic film coatings, window blinds, overhead obstructions, and
foliage, all of which can block GPS signals.
Verify that the NTP - Associations page is configured with valid NTP servers or peers that
the SyncServer can rely on if GPS is unavailable.
Configuring Window Mode

After setting up the antenna:
997-01520-02 Rev. G2.......................................................................... Page 103
Tasks
1. On the TIMING - Holdover page, set the Time Error Limit (milliseconds) to the highest
acceptable value for absolute timing error (to UTC). Microsemi recommends a value
greater than or equal to 4 milliseconds.
2. On the STATUS - GPS page, if the GPS receiver has a valid position (latitude, longitude, altitude), the user can skip to step 3. Otherwise:
n Determine the approximate latitude, longitude, and altitude of the GPS antenna.
This can be done using a handheld GPS device, an online reference such as
Google Earth, or by looking up the Latitude and Longitude information provided
on the SyncServer Product Information CD-ROM.
n On the REFERENCES - GPS page, enter the approximate latitude, longitude, and altitude.
3. Set the Mode to Position Hold and click the APPLY button.
Other Considerations
The accuracy of the user-entered position affects the timing accuracy of the GPS reference.
When GPS status is locked:
Position Accuracy
Timing Accuracy
< 50 m (< 164 feet)

< 1 km (< 0.62 mile)
< 10 km (< 6.2 miles)
< 0.005 ms
< 0.1 ms
< 1.0 ms
During window mode operation, if the GPS receiver is not locked to any satellites and no
other Input References are available, the GPS receiver enters holdover mode and is subject
to oscillator drift. Also see Oscillators (see "Timing Holdover" on page 85).
Verifying the GPS Installation

Verify the GPS antenna installation:
1.
2.
3.
4.
Press the STATUS button on the front panel.

Press the up arrow button to display the GPS STATUS screen.
When the number of Satellites is equal or greater than "4", Status should be Locked.
With GPS locked, the SYNC LED on the front panel should be green within approximately
15 minutes.
This can also be accomplished in the web interface using the STATUS - GPS page.
Verify synchronization over a 24-hour period to ensure that the GPS antenna installation
meets requirements. This can be accomplished by:
n
n
Observing the SYNC LED or STATUS - GPS page.

Configuring alarm notification (email, SNMP) to receive notification of the Timing GPS
Source Alarm on the ADMIN - Alarm page.
Using FIND on the LOGS - messages page to search for "Timing GPS Source Alarm".
If the GPS installation does not meet requirements:
Page 104..........................................................................997-01520-02 Rev. G2
Installation Guide
n
n
n
Review the GPS topics in this user guide

Troubleshoot for issues with the GPS antenna and cable.
Contact Microsemi Customer Assistance (on page 3).
Distance Between Antenna and Receiver

GPS satellites signals operate in the L1 band (1575.42 MHz). Practically speaking the
antenna must have an unobstructed view of the sky and thus be mounted on a roof, or in
some cases in a window. GPS provides continuous operation day and night.
Since the GPS signal is very weak, the antenna amplifies the signal to drive it through the
cable to the receiver. Antenna cable however offers some resistance and the GPS signal
strength will attenuate as it travels down the cable. GPS receiver sensitivity is finite so if the
cable length is too long the signal will be too weak for the receiver to detect it. Consequently it
is very important to know the distance in advance between the antenna and the receiver so
that the proper cable solution can be installed.
Antenna cabling solutions typically vary depending on how far the antenna is installed from
the GPS receiver. Antenna cable runs are supported from the standard 50 ft (15m) to over
1500 ft. (457 m). 150 feet (45 m) is the unaided cable length limit for many GPS timing receivers from Microsemi.
Adding a GPS inline amplifier extends the cable length an additional 150 feet (45 m) up to a
total of up to 300 ft. (90 m). The inline amplifier installs in-line with the antenna cable, using
the existing antenna power. No extra wiring is required.
The GPS Down/Up converter makes cable runs of 250 to 1500 feet (75 m to 457 m) possible
using a special GPS antenna that converts the signal to a lower frequency less susceptible to
attenuation, and transmitting it the length of the cable, powered by an external power supply.
An external power supply is provided with the GPS Down/Up converter.
The following diagram gives a summary of the cabling solutions for different distances
between the antenna and receiver. For more specific cabling information see Cabling
between the receiver and antenna:
Cable lengths and antenna solutions
997-01520-02 Rev. G2.......................................................................... Page 105
Tasks
For more information about any of the options described above, please contact Microsemi
Customer Assistance (on page 3).
Configuring GPS for Various Conditions

This topic guides the user on how to configure the GPS receiver to operate under a variety of
conditions, including reduced GPS satellite availability and mobile applications.
In all cases, Microsemi recommends configuring the SyncServer with multiple references
and/or NTP server associations to provide synchronization if a single reference such as GPS
becomes unavailable.
To configure the mode and enter the position of the GPS receiver/antenna, use the
REFERENCES - GPS page.
To determine the number of "current" GPS satellites, use the STATUS - GPS page.
Stationary Applications
If the GPS antenna is in a location that provides 4 or more "current" GPS satellites on a continuous basis, Microsemi recommends letting the SyncServer operate in its factory configuration. In that configuration, when the SyncServer starts, the GPS receiver comes up in
Survey mode. Upon locking to four or more GPS satellites the receiver determines and averages its position. After averaging the position it shifts to Position Hold mode. The user can
expect this type of operation when the GPS antenna is mounted outdoors in a high location
that provides good clear unobstructed views of the sky and horizon in all directions.
The lack of 4 "current" GPS satellites for sufficient durations may delay or prevent the GPS
receiver from determining its position and entering Position Hold. If the GPS antenna is in a
location that continuously provides 1 or more "current" GPS satellites, the SyncServer can
provide excellent synchronization to UTC once it has an accurate position and is in Position
Hold mode. Therefore, Microsemi recommends that the user perform the following actions
(in order of priority):
n
Move the GPS antenna to a location that provides better visibility of GPS satellites and
improves the strength/quality of GPS signals reaching the GPS antenna input connector.
Consult the Selecting a Site for the Antenna (on page 100) topics.
Determine and enter SyncServer's position, then put the GPS receiver in Position Hold
mode. Consult the Latitude and Longitude (see "Determining Latitude and Longitude"
on page 147) topic.
Let the SyncServer operate for 24 hours to see if it can determine its position and transition into Position Hold unaided.
If the number of "current" GPS satellites drops to zero, and every effort has been made to
remedy this situation, the user may consider the following actions:
n
Using a SyncServer equipped with a higher-stability oscillator, such as the OCXO or

Rubidium.
Page 106..........................................................................997-01520-02 Rev. G2
Installation Guide
n
Setting the Time Error Limit to the highest value that meets the requirements of the application for which the SyncServer is being used. In this case, Microsemi recommends 4 milliseconds as an acceptable value for NTP synchronization.
Mobile Applications
If the SyncServer might be transported while operating, put the GPS receiver in Dynamic
mode. In this mode, the GPS receiver continuously updates its position. This provides:
n
n
Much greater timing accuracy than Position Hold for mobile operation
Less timing accuracy than Position Hold for stationary operation. If the SyncServer is
being used primarily for NTP synchronization, this decrease is negligible compared to the
timing latency on most networks. If the SyncServer's other timing outputs are being used,
the user should perform field tests to ensure that accuracy meets the requirements of the
application.
Note: Avoid using Position Hold while operating the SyncServer from a location that is different from the one that the GPS receiver has. Doing so introduces timing errors that
increase with the size of the difference of the latitude, longitude and altitude readings
between the SyncServer and the GPS receiver.
UpgradingSystem Software
Overview of the Software Upgrade Process
In its factory default configuration, the SyncServer automatically checks for software
upgrades every weekday shortly after noon local time. If an upgrade is available, the SyncServer generates a System Upgrade Alarm.
The user responding to the alarm logs into the web interface. The status bar at the top of the
window may show that an alarm has been triggered, and on the STATUS - General page,
"Release Version" states that an upgrade is available.
Before upgrading, as a precaution, the user should back up the configuration of the SyncServer (WIZARDS - Backup). Normally, the SyncServer transfers its settings from one version of the software to the next. However, if the upgrade process is interrupted (e.g., loss of
power), the settings may be lost. Having the backup makes it possible to restore the previous
settings if that happens.
The user downloads the software upgrade file from the Microsemi web site to their workstation and then follows the steps given below for upgrading the software on the SyncServer.
Note: Please avoid decompressing the *.tar upgrade file prior to upgrading the SyncServer.
For security, the SyncServer will reject any file that has been modified or decompressed and
recompressed. If needed, download a new software file from Microsemi.
Prerequisites for the System Upgrade Alarm to Work

The SyncServer notifies the user when a software upgrade is available, provided all of the following items are true:
997-01520-02 Rev. G2.......................................................................... Page 107
Tasks
n
The Check for software upgrades setting is enabled on the SYSTEM - General page (factory default = enabled).
The LAN1 port is configured correctly and has a DNS server on the NETWORK - Ethernet
page (typically configured during installation).
The LAN1 port can reach Microsemi.com on the Internet using port 80. Most proxy servers and firewall devices allow this type of traffic, but some may be configured to block it.
Consult your network administrator for more information.
The System Upgrade Alarm and its notification settings are enabled on the ADMIN Alarms page (factory defaults = enabled).
The user is reachable by one or more of the Alarm notification methods: email, Alarm
LED, SNMP (typically configured during installation).
See also:
n
n
n
WIZARDS - Backup (on page 70)

SYSTEM - Upgrade (on page 53)
ADMIN - Alarms (on page 57)
Checking if an Upgrade is Available

n
Check the System Upgrade Alarm on the ADMIN - Alarms page to see if a software
upgrade is available.
Or, manually check for an upgrade by comparing the Release Version on the STATUS General page with the Version at:
http://update.symmetricom.com/upgrade.txt
Downloading the Upgrade

1. Unless instructed to use another URL, download the software from Microsemi's online
portal at www.microsemi.com.
2. Save the software to your workstation or to the USB flash drive.
3. (Optional) Back up the SyncServer configuration to your workstation or USB flash drive.
Also see Creating a Backup File (on page 118).
Upgrading the Software

The user can upgrade the software using any one of the three methods given below.
Note: Please wait approximately 5 - 10 minutes while the SyncServer upgrades, shuts
down, and reboots. Avoid disconnecting or switching the power off during the upgrade process.
Method 1: Using the 4) USB function on the keypad/display interface:
1.
2.
3.
4.
Insert the USB flash drive in either USB port on the front panel.
Select 4) USB.
Select 3) Upgrade Software.
Page 108..........................................................................997-01520-02 Rev. G2
Installation Guide
5. Select 1) Yes.
Method 2: Using the WIZARDS - Upgrade page:
1.
2.
3.
4.
Click the BROWSE button (STEP 1: Transfer Upgrade File to SyncServer).

In the Choose file window, locate and double-click the upgrade file.
Click the NEXT button (STEP 1: Transfer Upgrade File to SyncServer).
Click the FINISH button. (STEP 2: Perform Upgrade).
Method 3: Using the SYSTEM - Upgrade page:

1. On the SYSTEM - Upgrade page, click the BROWSE button.
2. In the Choose file window, locate and double-click the upgrade file.
3. On the SYSTEM - Upgrade page, click the UPLOAD button.
The SyncServer reports "Downloading Upgrade File!"
4. Select the upgrade file in the Current Files window and click the INSTALL button.
(Optional) After the upgrade:

When the SyncServer is finished rebooting, the browser shows the login page, while the
Front Panel Display shows the model, time and date.
n
Log in to the web interface and check the Release Version on the STATUS - General page
to ensure that it matches the desired version
Check the overall configuration to verify that the settings are still correct.
AddingNTPServerstothe NTPAssociationsList
About NTP Associations
The SyncServer's factory configuration includes three NTP associations:
n
The Hardware Clock makes a timing reference source (e.g., GPS, Timecode) available to
the NTP daemon as an NTP association. The Hardware Clock NTP association is
always preferred and cannot be edited or deleted. See TIMING - HW Clock (on page
42) for more information.
Having multiple associations is important for obtaining the best reliability and accuracy from
the SyncServer's NTP daemon. The SyncServer uses the NTP associations to qualify one
another; synchronizing with the best one and rejecting any that provide the incorrect time. If
the Hardware Clock runs without an Input Reference for a sustained period of time, the SyncServer synchronizes with one of the NTP servers instead.
Configuring NTP Associations

If the following conditions are true, the user does not need to reconfigure NTP:
n
n
n
n
LAN1 is connected to the network and has Internet access through firewall port 123.
GPS is set up correctly and operating as a reference source.
No NTP servers are available on the local or wide area network.
The list of NTP association contains valid NTP server addresses.
997-01520-02 Rev. G2.......................................................................... Page 109
Tasks
Otherwise:
n
n
Correct any problems with the GPS installation.

Make arrangements with your IT department to open firewall port 123 so that NTP messages can travel between LAN1 and NTP servers on the Internet
Add any NTP servers on the local or wide area network, (LAN or WAN) as NTP associations.
Add public NTP servers to the SyncServer's NTP Associations, as described below.
Adding NTP Servers to the NTP Associations

1. Search the Internet for "NTP servers".
2. Review the lists of NTP servers on the various sites. (Stratum 1 recommended.)
3. Identify several NTP servers operated by trustworthy organizations, including one or two
nearby.
4. Verify that your usage complies with the access policies of the NTP servers.
5. Using the SyncServer's NTP - Config page, under Add/Edit NTP Association:
n Role: Select "Server".
n Address: Enter the URL or IP address of the NTP server.
n Leave the other settings at their default values unless there's a reason to change
them.
6. Click the RESTART button to restart the NTP daemon.
Note: When using a URL as the NTP server address, a valid DNS server must be available
for LAN1 on the NETWORK - Ethernet page.
RecoveringaPassword
Enable Recover Password when setting up the SyncServer so it is available when needed.
This can be done using the ADMIN - Users or WIZARD-1st Setup pages
To recover a lost or forgotten password:
1. Enter the username, select the Recover Password checkbox, and click the LOGIN button.
2. Answer the Recovery Question and click the RESET button. The SyncServer sends a message to the email address of the username.
3. When the email arrives, log into the SyncServer using the new password provided in the
email message.
4. Change the password using the ADMIN - Users page.
If Recover Password wasn't enabled:
n
If the SyncServer has multiple user accounts, you may be able to have another user log
in and change the password for you.
If there is no other way to log into the SyncServer, use the hardware jumper to restore
the factory configuration. See Restoring the Factory Default Configuration (on page
119).
Page 110..........................................................................997-01520-02 Rev. G2
Installation Guide
Haltingthe SyncServer
Microsemi recommends shutting the operating system down before removing the power.
Using the keypad/display interface:
1.
2.
3.
4.
5.

Select 3) Shutdown.
Select 1) Yes.
Press the ENTER button.
When the display shows "System Stopped - OK to Turn Power Off Now!" turn the power
off.
Or, using the web interface:

1. Go to the SERVICES - Startup page.
2. Select Halt and click the APPLY button.
3. Wait approximately 30 seconds before removing power.
ConfiguringLAN1
During installation, the user configures LAN1 to gain access to the web interface. After logging in to the web interface, the user can configure the remaining ports on the NETWORK - Ethernet page.
The factory default settings for the LAN1 network port are as follows:
n
n
n
IP Address:192.168.0.100
Mask: 255.255.255.0
Gateway: 0.0.0.0
Configure new network settings using the keypad on the front panel:
1. Press the MENU button on the front panel.
2. Using the number buttons, select 1) LAN1, then 1) Config, and configure the port as
needed.
3. Check the new LAN1 settings by pressing the STATUS button repeatedly until "LAN1
STATUS" is shown.
Note: Using the keypad/display interface to configure LAN1, erases the previous settings for
all of the network ports.
Also see MENU Button.
997-01520-02 Rev. G2.......................................................................... Page 111
Tasks
CAUTION: DHCP Not Available

If the user selects DHCP, the SyncServer tries to reach a DHCP server for approximately 90
seconds before stopping. Please do not disconnect the power during this time.
ATTENTION : Si l'utilisateur choisit DHCP, le SyncServer essaye d'atteindre un serveur de
DHCP pendant approximativement 90 secondes avant de s'arrter. Veuillez ne pas enlever
le courrant pendant ce temps.
LoggingintotheWebInterface
1. Get the LAN1 IP address by pressing the STATUS button repeatedly until the LAN1
STATUS screen is visible on the display.
2. Using Internet Explorer, enter the IP address as a URL. This displays the Login page.
3. At the SyncServer Login page, log in. The username is admin and password is symmetricom.
Note: When entering the IP address as a URL, leave off any leading zeroes in the IP
address. For example, instead of 192.168.047.025, enter 192.168.47.25.
Usingthe1stSetupWizard
Select the WIZARDS button and complete the 1st Setup wizard.
1. Configure the SyncServer using WIZARDS - 1st Setup. Select the following options:
n "Configure Password Recovery" (Ask the IT department for the IP address of the
SMTP server).
n "Send test mail when finished"
n "Set Local Time Zone"
Note: Reconfiguring LAN1 in the 1st Setup wizard erases the previous network settings for all
Ethernet ports.
Also see WIZARDS - 1st Setup.
Configuringthe Network Ports

Configure the remaining network ports using NETWORK - Ethernet.
Microsemi Recommends:
n
n
Using static IP addresses. (See explanation below.)

Using Allowed Access to protect the network ports from unauthorized IP addresses or
address ranges.
Explanation: NTP associations and authentication may rely on static network addresses. If a
DHCP server assigns a new address to a network port that has DHCP enabled, the associations and authentication may stop working.
Also see NETWORK - Ethernet (on page 27).
Page 112..........................................................................997-01520-02 Rev. G2
Installation Guide
AddingServerAssociations
NTP server and peer associations provide an important backup source of time if the SyncServer's Input References are unavailable. Having two or more server or peer associations
is important for reliability and redundancy.
(Optional) The user can add associations for NTP servers that reside on the company network:
n
For NTP servers that the user cannot configure, add server associations, as described
below.
For NTP servers that the user can configure, add peer associations as described in
Adding Peer Associations.
Note: Avoid creating server associations on two NTP servers that point to each other. Use
peer associations instead.
(Optional) If the SyncServer is located outside the United States, the user can also add at
least one server association that points to a local NTP server. This provides a shorter network path, which improves timing precision and accuracy. Often, public NTP servers are
operated by national timekeeping authorities, telecommunications companies, and universities. To find a local NTP server, search the Internet for "Public NTP servers". Include
the name of your country at the end of the search string. When available, select NTP servers
that are stratum 1 over those that are stratum 2.
To add a server association:
1.
2.
3.
4.
Go to NTP - Config in the web interface.

Under Add/Edit Association, for Role, select Server.
For Address, enter an IP address (recommended) or domain name.
(Optional) Configure the other settings under Add/Edit Association. For more information, see NTP - Config.
5. Click SAVE.
6. Click RESTART.
After restarting, the NTP daemon sends regular requests to the server and uses the replies
to compare the NTP server with other servers and peers. The NTP daemon selects the best
server or peer and synchronizes with it.
Also see Configuring NTP Clients.
997-01520-02 Rev. G2.......................................................................... Page 113
Troubleshooting

(Optional) Connect any additional Input References to the back panel and configure them, if
needed:
n
n
For IRIG In, see REFERENCES - Timecode.

1PPS In, 10MHz In don't require any configuration.
See SyncServer signal feature comparison (on page 18) to see the available signals for
each model of SyncServer.
In This section
Troubleshooting
Creating a Backup File
Restoring from a Backup File
Restoring the Factory Default Configuration
Configuring SNMP
115
118
118
119
119
120
122
122
122
123
Troubleshooting
The following troubleshooting scenarios provide high-level guidance on how to solve a range
of potential problems with the SyncServer.
n
A bullet is a proposed solution. The user should try each solution in turn until the problem
is solved.
A numbered step is a procedure. The user should complete the procedure to solve the
problem.
For additional help, contact Microsemi Customer Assistance (on page 3).
Passwords
You've tried logging in and the password doesn't work.
n
n
n
Passwords are case sensitive. Check that that Caps Lock isn't on.
Use the Recover Password feature, if it is available and configured.
Have another user log in and change your password settings.
997-01520-02 Rev. G2.......................................................................... Page 115

n
If all else fails, restore the factory default configuration using the hardware jumper. See
Restoring the Factory Default Configuration (on page 119).
Web Interface Troubleshooting

You can't reach the web interface.
n
n
n
Check that LAN1 is physically connected to the network.

Ping the IP Address of LAN1.
Check that the LAN1 IP Address, Mask, and Gateway are valid using the STATUS button
to display LAN1 STATUS.
LAN1 may be disabled. If needed, turn it on using the Keypad/Display as follows:
1. Press MENU.
2. Select 1) LAN1.
3. Select 2) On/Off.
4. Select 1) On.
The Web Server may be turned off.
n Cycle the power off and on again. Depending on the configuration of the SERVICES
- Startup page, the web server may be available when the SyncServer finishes
rebooting. See Halting the SyncServer.
Otherwise, log into the command line interface and turn the web server on using
the HTTP on command. See Command Line Interface (on page 79).
n After logging in to the web interface, select Auto for Web Server on the SERVICES Startup page.
The SERVICES - HTTP page may be configured for Secure (Port 443) Only. If so, edit the
URL in the browser so that it begins with "https" instead of "http".
n
Alarms and Notification

You're not receiving alarm notifications by email or snmp.
n
n
n
Check that the alarm notification settings are enabled, as shown in the Factory Default
Settings for Alarms topic that follows.
To receive SNMP traps, verify that the NETWORK - SNMP and NETWORK - SNMP Traps
pages are configured correctly.
To receive email notification, verify that the SERVICES - Email page is configured correctly.
Verify that LAN1 is configured with a valid DNS server address.
Factory Default Settings for Alarms

Name
NTP System Peer Change
Auto Clear Severity Send Trap Write Log Send Email

Notify
Page 116..........................................................................997-01520-02 Rev. G2
Troubleshooting
NTP Stratum Change
NTP Leap Change
System Network
System Upgrade
System Config Change
System Health
X
X
X
Major
System Up/Down
Notify
System Authentication
Timing No Source
X
X
Notify
Timing GPS Source

Timing IRIG-B Source
Timing PPS Source
Timing 10MHz Source
Timing GPS Antenna Short
X
X
X
X
X
Major
X
X
X
X
X
X
X
X
Notify
Notify
Minor
Notify
Timing GPS Antenna Open

X
Timing Oscillator DAC Range
Timing Rubidium Lock
Timing Oscillator Unlock
Timing Source Change
Timing Source Lower Accuracy Input
Timing PLL Unlock
X
Major
Major
X
X
X
X
X
X
X
Notify
Notify
Notify
Notify
Notify
Notify
X
X
X
X
X
X
X
Notify
Notify
Notify
Major
Major
X
X
Timing Quality 1e-6
Notify
Timing Quality 1e-5

Timing Quality 1e-4
Timing Quality 1e-3
Timing Leap Event
LAN1 Link
LAN2 Link
LAN3 Link
Timing NTP Daemon
System Reset Default Config
X
X
X
X
X
X
X
Notify
Notify
Notify
Notify
X
X
X
X
X
X
X
Major
Notify
Notify
Notify
Notify
NTP Clients
The NTP clients can't reach or synchronize with the SyncServer. On the SyncServer:
n
The Network LED on the front panel should be green. Otherwise, check the physical network port connections. Also see Status LEDs.
Check the configuration of the network ports on the NETWORK - Ethernet page, described
in Configuring the Network Ports (on page 112).
If the Sync LED on the front panel is red, the SyncServer is unsynchronized and NTP clients won't synchronize to it. Configure the SyncServer with a valid reference input and/or
997-01520-02 Rev. G2.......................................................................... Page 117

NTP server/peer associations. Also see Using GPS (on page 100), Using the Other
Input References, and Adding Server Associations (on page 113).

SyncServer's configuration settings can be saved to a "backup" file, which is useful in the following scenarios:
n
The user is testing multiple SyncServer configurations. The user saves the "original" configuration before testing, and then saves some of the more promising test configurations.
When the testing is complete, the user selects the best configuration and applies it to the
SyncServer.
The user needs to configure several SyncServers. The user configures a single SyncServer, creates a backup file, and then uses the backup file to transfer the configuration
to the remaining SyncServers.
The user needs a "known good configuration" in case the SyncServer's configuration is
inadvertently changed or lost.
The SyncServer's backup and restore features are available from two locations:
n
n
From the web interface, using the WIZARDS - Backup and the WIZARDS - Restore pages.
From the front panel keypad, using the MENU button and the 4) USB menu item.
The backup/restore features can use a variety of media:

n
n
A USB flash drive plugged into either of the USB ports on the front panel.
Any directory that is accessible to a browser.
Note 1 - Not all USB flash drives are compatible with the SyncServer's USB ports.
Microsemi recommends using SanDisk cruzer micro USB devices.
Note 2 - The backup file includes the configuration of the NETWORK - Ethernet page. If restoring a single configuration to multiple units, if the network ports have static IP addresses,
avoid IP address conflicts by changing these addresses.
Note 3 - Transferring configurations between a SyncServers with different hardware or software might not work. The user may want to back up the configuration of the "destination"
SyncServer before applying the configuration of the "originating" SyncServer. One can also
restore the Factory Defaults if the transfer doesn't work. See the Restoring the Factory
Default Configuration (on page 119) topic.
CreatingaBackupFile
From the front panel keypad
1.
2.
3.
4.
Plug a compatible USB flash drive into either USB port.

Wait 10 seconds.
Select 4) USB.
Page 118..........................................................................997-01520-02 Rev. G2

5. Select 1) Backup Cfg.
6. When the SyncServer finishes "Saving to USB Drive", remove the USB flash drive.
From the web interface

1. On the WIZARDS - Backup web page, click the BACKUP button to create a backup file on
the SyncServer.
2. Then use the SAVE AS or COPY button to download the backup file to a your workstation
or a USB device.
Restoringfrom aBackupFile
From the front panel keypad
1.
2.
3.
4.
5.
Plug the USB flash drive into the 'target' SyncServer.

Wait 10 seconds.
Press the MENU button, select 4) USB, and select 1) Restore Cfg.
The SyncServer reports "Restoring from USB Drive" and "Shutting down, please wait..."
When the SyncServer finishes rebooting, remove the USB flash drive.
From the web interface

On the WIZARDS - Restore web page, select one of the following options:
n
n
n
n
Reset to Factory Defaults. See Restoring the Factory Default Configuration (on
page 119).
Restore last backup from SyncServer.
Restore backup from USB flash drive.
Restore backup from a workstation hard-drive or network directory.
Restoringthe FactoryDefault Configuration

The user may wish to restore the factory default configuration in a variety of circumstances:
n
n
n
When the password is lost and the Recover Password feature is disabled (Use the Hardware Jumper method).
To erase the previous configuration prior to reconfiguring the SyncServer.
To erase site-specific information such as the IP addresses and the GPS position, prior to
sending the SyncServer off-site.
In some cases, the user may back up the current configuration of the SyncServer prior to
restoring the factory default configuration. See Creating a Backup File (on page 118).
Restoring the default factory configuration removes the current network settings. Afterwards, the user may need to configure the LAN1 port in order to use the web interface.
Using the Web Interface

To restore the factory configuration use the one of the following pages:
n
n
SYSTEM - Factory Reset

WIZARDS - Restore (select Reset to Factory Defaults).
997-01520-02 Rev. G2.......................................................................... Page 119

To clear site-specific information from the SyncServer, disconnect all input network cables
and GPS antenna cables from the rear of the SyncServer shortly after clicking the APPLY button, before the SyncServer has had time to restart.
Using the Hardware Jumper

This procedure requires:
n
n
n
A jumper.
Size 0 philips-head screwdriver
Tweezers or needle-nosed pliers for handling the jumper.
Note: Observe static protection measures while working inside the SyncServer.
To restore the factory configuration:
1. Halt the SyncServer as described in Halting the SyncServer.
2. VERY IMPORTANT: Remove the top cover as described in Removing the Top Cover (on
page 122).
3. Position a jumper (not supplied) across the jumper pins marked JP4, next to the circular
battery.
4. (Optional) To clear site-specific information, disconnect all network and GPS antenna
cables from the rear of the SyncServer and do not reconnect them.
5. Connect the power cable and turn the power switch on. The SyncServer restores the factory configuration.
6. After 100 seconds, turn the power switch off and disconnect the power cable.
7. Remove the jumper from the JP4 jumper pins.
8. Secure the top cover to the SyncServer using the screws.
9. Reconnect the power cable and turn the SyncServer's power on. The default factory configuration has been restored.
Configuring SNMP
On the SyncServer, SNMP:
n
n
n
Responds to requests for configuration and operational information.

Sends traps in response to events, as configured on the ADMIN - Alarms page.
Cannot be used to change the SyncServers configuration (is read only).
SNMP-related pages on the SyncServer:

n
n
n
n
n
WIZARDS - SNMP: Configure SNMP quickly (SNMP v1 and v2c only).

NETWORK - SNMP: Configure SNMP and add v3 users.
NETWORK - SNMP Traps: Configure trap recipients.
ADMIN - Alarms: Select which events generate SNMP traps.
SERVICES - Startup: Stop or start the SNMP daemon, and enable/disable it from starting
automatically when the SyncServer reboots.
Configuring the SyncServer for SNMP queries
Page 120..........................................................................997-01520-02 Rev. G2
Configuring SNMP
For SNMP v1/v2c queries, specify a Read Community string on the NETWORK - SNMP page.
For SNMP v3 queries, create v3 Users on the NETWORK - SNMP page.
Additional standard SNMP values, such as sysLocation and sysContact are also specified
on the NETWORK - SNMP page.
The SyncServer Product CD includes a copy of the SyncServer custom MIB file that can be
loaded into SNMP management stations.
Configuring the SyncServer to send SNMP Traps

To configure SNMP to send v1 or v2c traps:
1. Go to the NETWORK -> SNMP Traps page.
2. In the "Add/Edit Trap Recipient" section of the page, do the following:
n Enter the IP Address of the destination management console.
n Select whether it is a v1 or v2c trap.
n Enter the Community string that will be included in the trap PDU.
n For v2c, mark Send As Inform if you want to send an INFORM-PDU. (Otherwise a
TRAP-PDU or TRAP2-PDU is sent.)
n Click Save.
n Go to the ADMIN -> Alarms page, and specify which events should generate SNMP traps.
To configure SNMP to send v3 traps:
NOTE! To configure SNMP to send v3 traps, you must first create a v3 user which corresponds to a user on the destination management console. (This is done through the
NETWORK -> SNMP page.)
1. Go to the NETWORK -> SNMP Traps page.

2. In the "Add/Edit Trap Recipient" section of the page, do the following:
n Enter the IP Address of the destination management console.
n Select v3 as the trap type.
n Enter the name of the v3 User you created on the NETWORK -> SNMP page.
n Mark Send As Inform if you want to send an INFORM-PDU. (Otherwise a TRAP-PDU or
TRAP2-PDU is sent.)
n Enter the 8-character Auth phrase for the user, and indicate if it is M5D or SHA1.
n Specify an optional Priv phrase.
n Click Save.
n Go to the ADMIN -> Alarms page, and specify which events should generate SNMP
traps.
Use SNMP get from the destination management console (as this v3 user), to query the SyncServer for its EngineID. You may then configure any desired SNMP v3 trap receivers on
your remote management console.
997-01520-02 Rev. G2.......................................................................... Page 121
NOTE: The SyncServer gets a new EngineID on every upgrade (even if "upgrading" to the
same system software version you are already running). You MUST re-query the SyncServer via SNMP get and reconfigure your v3 trap receivers to use this new EngineID.
The user can transfer a configuration across multiple SyncServers to save time and effort,
provided they are running the same Software Version (displayed on the STATUS - General
page.
If you have physical access to the SyncServer, the easiest method for transferring the configuration is to use a USB flash drive and the front panel keypad.
1. Create a backup file on a configured SyncServer, as described in Creating a Backup
File (on page 118).
2. Restore that backup file to another SyncServer as described in Restoring from a
Backup File (on page 119).
3. IMPORTANT: When the SyncServer reboots, immediately change the IP address of LAN1
using the front panel MENU button as described in Configuring LAN1 (on page 111).
This step resets all of the network port addresses and prevents network address collisions with the previous SyncServer.
4. Log in and use the NETWORK - Ethernet page to configure the network ports.
5. On the SYSTEM - General page, update the Hostname.

After halting the SyncServer as described in Halting the SyncServer:
1. If needed, remove the SyncServer from the equipment rack.
2. Disconnect the power from the SyncServer.
3. Remove the top cover (lid):
n Remove the six retaining screws from the top cover.
n Lift the rear edge of the top cover from the chassis.
n SLOWLY and firmly separate the top cover from the adhesive heatsink pad.

To replace the battery:
1. To safeguard delicate instrument electronics, remove power to the SyncServer.
Page 122..........................................................................997-01520-02 Rev. G2

2. VERY IMPORTANT: Remove the SyncServer's top cover as described in Removing the
Top Cover (on page 122).
3. Locate the circular silver-colored disc-shaped lithium battery, located on the front right
corner of the motherboard.
4. Please do not lift or bend the metal clip. Doing so may damage or break the battery holder,
requiring repair.
5. Locate the sloping black plastic latch, opposite from the metal clip.
6. Depress the latch and slide the battery out of the holder
7. Dispose of the battery in accordance with local regulations.
8. Use the new battery to press the latch down while sliding the battery into the holder.
9. Re-apply power to the SyncServer.
CAUTION:LithiumBattery
The SyncServer contains a Lithium Battery that maintains the system's Real Time Clock
(RTC) when the SyncServer's power is off. Replace the Lithium Battery only with the same
or equivalent type. Do not dispose of the Lithium Battery in a fire or incinerator, or the battery
may explode. Follow disposal regulations in your area for Lithium Battery disposal.
ATTENTION : Le SyncServer contient une batterie de lithium pour maintenir l'horloge en
temps rel pendent que le courant est debranch. Remplacez la batterie de lithium seulement avec une batterie de type quivalent. Ne vous dbarrassez pas de la batterie de lithium
dans un feu ou un incinrateur, car la batterie pourrait exploser. Dbarrassez-vous de la batterie usage de lithium selon les instructions du fabricant.
997-01520-02 Rev. G2.......................................................................... Page 123
Software
Upgrades
Microsemi (formerly Symmetricom) makes software updates available as downloads on the
Internet.
Users are required to register in order to download software. Some export restrictions may
apply.
Licenses
This product contains licensed third party software, including software available under the
GPL licensing scheme. The text of each license is available in the "License" folder located on
the Product Information CD-ROM that is supplied with the SyncServer. Additionally, these
licenses and the source code for the related public software can be obtained by contacting
Microsemi Customer Assistance (on page 3).
These licenses include, but are not limited to the following:
n
n
n
n

By using the SyncServer, the user agrees to the terms of these licenses.
In This section

/* ====================================================================
* The Apache Software License, Version 1.1
*
* Copyright (c) 2000-2003 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
997-01520-02 Rev. G2.......................................................................... Page 125
125
134
137
143
Software
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The end-user documentation included with the redistribution,
* if any, must include the following acknowledgment:
* "This product includes software developed by the
* Apache Software Foundation (http://www.apache.org/)."
* Alternately, this acknowledgment may appear in the software itself,
* if and wherever such third-party acknowledgments normally appear.
*
* 4. The names "Apache" and "Apache Software Foundation" must
* not be used to endorse or promote products derived from this
* software without prior written permission. For written
* permission, please contact [email protected].
*
* 5. Products derived from this software may not be called "Apache",
* nor may "Apache" appear in their name, without prior written
* permission of the Apache Software Foundation.
*
* THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
* ====================================================================
*
* This software consists of voluntary contributions made by many
* individuals on behalf of the Apache Software Foundation. For more
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
*
* Portions of this software are based upon public domain software
* originally written at the National Center for Supercomputing Applications,
* University of Illinois, Urbana-Champaign.
*/
APACHE HTTP SERVER SUBCOMPONENTS:

The Apache HTTP Server includes a number of subcomponents with
separate copyright notices and license terms. Your use of the source
code for these subcomponents is subject to the terms and
conditions of the following licenses.
For the mod_mime_magic component:
/*
* mod_mime_magic: MIME type lookup via file magic numbers
* Copyright (c) 1996-1997 Cisco Systems, Inc.
*
* This software was submitted by Cisco Systems to the Apache Group in July
* 1997. Future revisions and derivatives of this source code must
* acknowledge Cisco Systems as the original contributor of this module.
Page 126..........................................................................997-01520-02 Rev. G2

* All other licensing and usage conditions are those of the Apache Group.
*
* Some of this code is derived from the free version of the file command
* originally posted to comp.sources.unix. Copyright info for that program
* is included below as required.
* ------------------------------------------------------------------* - Copyright (c) Ian F. Darwin, 1987. Written by Ian F. Darwin.
*
* This software is not subject to any license of the American Telephone and
* Telegraph Company or of the Regents of the University of California.
*
* Permission is granted to anyone to use this software for any purpose on any
* computer system, and to alter it and redistribute it freely, subject to
* the following restrictions:
*
* 1. The author is not responsible for the consequences of use of this
* software, no matter how awful, even if they arise from flaws in it.
*
* 2. The origin of this software must not be misrepresented, either by
* explicit claim or by omission. Since few users ever read sources, credits
* must appear in the documentation.
*
* 3. Altered versions must be plainly marked as such, and must not be
* misrepresented as being the original software. Since few users ever read
* sources, credits must appear in the documentation.
*
* 4. This notice may not be removed or altered.
* ------------------------------------------------------------------*
*/
For the modules\mappers\mod_imap.c component:

"macmartinized" polygon code copyright 1992 by Eric Haines, [email protected]
For the server\util_md5.c component:
/************************************************************************
* NCSA HTTPd Server
* Software Development Group
* National Center for Supercomputing Applications
* University of Illinois at Urbana-Champaign
* 605 E. Springfield, Champaign, IL 61820
* [email protected]
*
* Copyright (C) 1995, Board of Trustees of the University of Illinois
*
************************************************************************
*
* md5.c: NCSA HTTPd code which uses the md5c.c RSA Code
*
* Original Code Copyright (C) 1994, Jeff Hostetler, Spyglass, Inc.
* Portions of Content-MD5 code Copyright (C) 1993, 1994 by Carnegie Mellon
* University (see Copyright below).
* Portions of Content-MD5 code Copyright (C) 1991 Bell Communications
* Research, Inc. (Bellcore) (see Copyright below).
* Portions extracted from mpack, John G. Myers - [email protected]
* Content-MD5 Code contributed by Martin Hamilton ([email protected])
*
*/
997-01520-02 Rev. G2.......................................................................... Page 127
Software
/* these portions extracted from mpack, John G. Myers - [email protected] */

/* (C) Copyright 1993,1994 by Carnegie Mellon University
* All Rights Reserved.
*
* Permission to use, copy, modify, distribute, and sell this software
* and its documentation for any purpose is hereby granted without
* fee, provided that the above copyright notice appear in all copies
* and that both that copyright notice and this permission notice
* appear in supporting documentation, and that the name of Carnegie
* Mellon University not be used in advertising or publicity
* pertaining to distribution of the software without specific,
* written prior permission. Carnegie Mellon University makes no
* representations about the suitability of this software for any
* purpose. It is provided "as is" without express or implied
* warranty.
*
* CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
* THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
* AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
* FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
* AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
* OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
* SOFTWARE.
*/
/*
* Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
*
* Permission to use, copy, modify, and distribute this material
* for any purpose and without fee is hereby granted, provided
* that the above copyright notice and this permission notice
* appear in all copies, and that the name of Bellcore not be
* used in advertising or publicity pertaining to this
* material without the specific, prior written permission
* of an authorized representative of Bellcore. BELLCORE
* MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
* OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS",
* WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
*/
For the srclib\apr\include\apr_md5.h component:
/*
* This is work is derived from material Copyright RSA Data Security, Inc.
*
* The RSA copyright statement and Licence for that original material is
* included below. This is followed by the Apache copyright statement and
* licence for the modifications made to that material.
*/
/* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
rights reserved.
License to copy and use this software is granted provided that it
is identified as the "RSA Data Security, Inc. MD5 Message-Digest
Algorithm" in all material mentioning or referencing this software
or this function.
License is also granted to make and use derivative works provided
Page 128..........................................................................997-01520-02 Rev. G2

that such works are identified as "derived from the RSA Data
Security, Inc. MD5 Message-Digest Algorithm" in all material
mentioning or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either
the merchantability of this software or the suitability of this
software for any particular purpose. It is provided "as is"
without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
*/
For the srclib\apr\passwd\apr_md5.c component:
/*
* This is work is derived from material Copyright RSA Data Security, Inc.
*
* The RSA copyright statement and Licence for that original material is
* included below. This is followed by the Apache copyright statement and
* licence for the modifications made to that material.
*/
/* MD5C.C - RSA Data Security, Inc., MD5 message-digest algorithm
*/
/* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
rights reserved.
License to copy and use this software is granted provided that it
is identified as the "RSA Data Security, Inc. MD5 Message-Digest
Algorithm" in all material mentioning or referencing this software
or this function.
License is also granted to make and use derivative works provided
that such works are identified as "derived from the RSA Data
Security, Inc. MD5 Message-Digest Algorithm" in all material
mentioning or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either
the merchantability of this software or the suitability of this
software for any particular purpose. It is provided "as is"
without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this
documentation and/or software.
*/
/*
* The apr_md5_encode() routine uses much code obtained from the FreeBSD 3.0
* MD5 crypt() function, which is licenced as follows:
* ------------------------------------------------------------------* "THE BEER-WARE LICENSE" (Revision 42):
* <[email protected]> wrote this file. As long as you retain this notice you
* can do whatever you want with this stuff. If we meet some day, and you think
* this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
* ------------------------------------------------------------------*/
For the srclib\apr-util\crypto\apr_md4.c component:
* This is derived from material copyright RSA Data Security, Inc.
997-01520-02 Rev. G2.......................................................................... Page 129
Software
* Their notice is reproduced below in its entirety.
*
* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
* rights reserved.
*
* License to copy and use this software is granted provided that it
* is identified as the "RSA Data Security, Inc. MD4 Message-Digest
* Algorithm" in all material mentioning or referencing this software
* or this function.
*
* License is also granted to make and use derivative works provided
* that such works are identified as "derived from the RSA Data
* Security, Inc. MD4 Message-Digest Algorithm" in all material
* mentioning or referencing the derived work.
*
* RSA Data Security, Inc. makes no representations concerning either
* the merchantability of this software or the suitability of this
* software for any particular purpose. It is provided "as is"
* without express or implied warranty of any kind.
*
* These notices must be retained in any copies of any part of this
* documentation and/or software.
*/
For the srclib\apr-util\include\apr_md4.h component:
*
*
* rights reserved.
*
* License to copy and use this software is granted provided that it
* is identified as the "RSA Data Security, Inc. MD4 Message-Digest
* Algorithm" in all material mentioning or referencing this software
* or this function.
*
* License is also granted to make and use derivative works provided
* that such works are identified as "derived from the RSA Data
* Security, Inc. MD4 Message-Digest Algorithm" in all material
* mentioning or referencing the derived work.
*
*
*/
For the srclib\apr-util\test\testdbm.c component:

/* ====================================================================
* The Apache Software License, Version 1.1
*
* Copyright (c) 2000-2002 The Apache Software Foundation. All rights
* reserved.
*
Page 130..........................................................................997-01520-02 Rev. G2

* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The end-user documentation included with the redistribution,
* if any, must include the following acknowledgment:
* "This product includes software developed by the
* Apache Software Foundation (http://www.apache.org/)."
* Alternately, this acknowledgment may appear in the software itself,
* if and wherever such third-party acknowledgments normally appear.
*
* 4. The names "Apache" and "Apache Software Foundation" must
* not be used to endorse or promote products derived from this
* software without prior written permission. For written
* permission, please contact [email protected].
*
* 5. Products derived from this software may not be called "Apache",
* nor may "Apache" appear in their name, without prior written
* permission of the Apache Software Foundation.
*
* THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
* ====================================================================
*
* This software consists of voluntary contributions made by many
* individuals on behalf of the Apache Software Foundation. For more
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
*
* This file came from the SDBM package (written by [email protected]).
* That package was under public domain. This file has been ported to
* APR, updated to ANSI C and other, newer idioms, and added to the Apache
* codebase under the above copyright and license.
*/
For the srclib\apr-util\test\testmd4.c component:

*
*
997-01520-02 Rev. G2.......................................................................... Page 131
Software
* rights reserved.
*
*
*/
For the srclib\apr-util\xml\expat\conftools\install-sh component:
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
install - install a program, script, or datafile

This comes from X11R5 (mit/util/scripts/install.sh).
Copyright 1991 by the Massachusetts Institute of Technology
Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.
For the srclib\pcre\install-sh component:

#
#
#
#
#
#
#
#
#
#
#
#
Copyright 1991 by the Massachusetts Institute of Technology

Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.
For the pcre component:

PCRE LICENCE
-----------PCRE is a library of functions to support regular expressions whose syntax
and semantics are as close as possible to those of the Perl 5 language.
Written by: Philip Hazel <[email protected]>
University of Cambridge Computing Service,
Cambridge, England. Phone: +44 1223 334714.
Copyright (c) 1997-2001 University of Cambridge
Permission is granted to anyone to use this software for any purpose on any
Page 132..........................................................................997-01520-02 Rev. G2

computer system, and to redistribute it freely, subject to the following
restrictions:
1. This software is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
2. The origin of this software must not be misrepresented, either by
explicit claim or by omission. In practice, this means that if you use
PCRE in software which you distribute to others, commercially or
otherwise, you must put a sentence like this
Regular expression support is provided by the PCRE library package,
which is open source software, written by Philip Hazel, and copyright
by the University of Cambridge, England.
somewhere reasonably visible in your documentation and in any relevant
files or online help data or similar. A reference to the ftp site for
the source, that is, to
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/
should also be given in the documentation.
3. Altered versions must be plainly marked as such, and must not be
misrepresented as being the original software.
4. If PCRE is embedded in any software that is released under the GNU
General Purpose Licence (GPL), or Lesser General Purpose Licence (LGPL),
then the terms of that licence shall supersede any condition above with
which it is incompatible.
The documentation for PCRE, supplied in the "doc" directory, is distributed
under the same terms as the software itself.
End PCRE LICENCE
For the test\zb.c component:

/* Zeusbench V1.01
===============
This program is Copyright (C) Zeus Technology Limited 1996.
This program may be used and copied freely providing this copyright notice
is not removed.
This software is provided "as is" and any express or implied waranties,
including but not limited to, the implied warranties of merchantability and
fitness for a particular purpose are disclaimed. In no event shall
Zeus Technology Ltd. be liable for any direct, indirect, incidental, special,
exemplary, or consequential damaged (including, but not limited to,
procurement of substitute good or services; loss of use, data, or profits;
or business interruption) however caused and on theory of liability. Whether
in contract, strict liability or tort (including negligence or otherwise)
arising in any way out of the use of this software, even if advised of the
possibility of such damage.
Written by Adam Twiss ([email protected]). March 1996
997-01520-02 Rev. G2.......................................................................... Page 133
Software
Thanks to the following people for their input:
Mike Belshe ([email protected])
Michael Campanella ([email protected])
*/
For the expat xml parser component:
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
and Clark Cooper
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
====================================================================

This file is automatically generated from html/copyright.htm
Copyright Notice
[sheepb.jpg] "Clone me," says Dolly sheepishly
________________________________________________________________
The following copyright notice applies to all files collectively
called the Network Time Protocol Version 4 Distribution. Unless
specifically declared otherwise in an individual file, this notice
applies as if the text was explicitly included in the file.
***********************************************************************
* *
* Copyright (c) David L. Mills 1992-2001 *
* *
* Permission to use, copy, modify, and distribute this software and *
* its documentation for any purpose and without fee is hereby *
* granted, provided that the above copyright notice appears in all *
* copies and that both the copyright notice and this permission *
* notice appear in supporting documentation, and that the name *
* University of Delaware not be used in advertising or publicity *
* pertaining to distribution of the software without specific, *
* written prior permission. The University of Delaware makes no *
* representations about the suitability this software for any *
* purpose. It is provided "as is" without express or implied *
* warranty. *
Page 134..........................................................................997-01520-02 Rev. G2

* *
***********************************************************************
The following individuals contributed in part to the Network Time
Protocol Distribution Version 4 and are acknowledged as authors of
this work.
1. [1]Mark Andrews <[email protected]> Leitch atomic clock
controller
2. [2]Bernd Altmeier <[email protected]> hopf Elektronik serial
line and PCI-bus devices
3. [3]Viraj Bais <[email protected]> and [4]Clayton Kirkwood
<[email protected]> port to WindowsNT 3.5
4. [5]Michael Barone <michael,[email protected]> GPSVME fixes
5. [6]Karl Berry <[email protected]> syslog to file option
6. [7]Greg Brackley <[email protected]> Major rework of WINNT
port. Clean up recvbuf and iosignal code into separate modules.
7. [8]Marc Brett <[email protected]> Magnavox GPS clock driver
8. [9]Piete Brooks <[email protected]> MSF clock driver,
Trimble PARSE support
9. [10]Reg Clemens <[email protected]> Oncore driver (Current maintainer)
10. [11]Steve Clift <[email protected]> OMEGA clock driver
11. [12]Casey Crellin <[email protected]> vxWorks (Tornado) port and
help with target configuration
12. [13]Sven Dietrich <[email protected]> Palisade reference
clock driver, NT adj. residuals, integrated Greg's Winnt port.
13. [14]John A. Dundas III <[email protected]> Apple A/UX port
14. [15]Torsten Duwe <[email protected]> Linux
port
15. [16]Dennis Ferguson <[email protected]> foundation code for
NTP Version 2 as specified in RFC-1119
16. [17]Glenn Hollinger <[email protected]> GOES clock driver
17. [18]Mike Iglesias <[email protected]> DEC Alpha port
18. [19]Jim Jagielski <[email protected]> A/UX port
19. [20]Jeff Johnson <[email protected]> massive prototyping
overhaul
20. [21]Hans Lambermont <[email protected]> or
[22]<[email protected]> ntpsweep
21. [23]Poul-Henning Kamp <[email protected]> Oncore driver (Original
author)
22. [24]Frank Kardel [25]<[email protected]>
PARSE <GENERIC> driver (14 reference clocks), STREAMS modules for
PARSE, support scripts, syslog cleanup
23. [26]William L. Jones <[email protected]> RS/6000 AIX
modifications, HPUX modifications
24. [27]Dave Katz <[email protected]> RS/6000 AIX port
25. [28]Craig Leres <[email protected]> 4.4BSD port, ppsclock, Magnavox
GPS clock driver
26. [29]George Lindholm <[email protected]> SunOS 5.1 port
27. [30]Louis A. Mamakos <[email protected]> MD5-based authentication
28. [31]Lars H. Mathiesen <[email protected]> adaptation of foundation
code for Version 3 as specified in RFC-1305
29. [32]David L. Mills <[email protected]> Version 4 foundation: clock
discipline, authentication, precision kernel; clock drivers:
Spectracom, Austron, Arbiter, Heath, ATOM, ACTS, KSI/Odetics;
audio clock drivers: CHU, WWV/H, IRIG
30. [33]Wolfgang Moeller <[email protected]> VMS port
31. [34]Jeffrey Mogul <[email protected]> ntptrace utility
32. [35]Tom Moore <[email protected]> i386 svr4 port
33. [36]Kamal A Mostafa <[email protected]> SCO OpenServer port
34. [37]Derek Mulcahy <[email protected]> and [38]Damon
Hart-Davis <[email protected]> ARCRON MSF clock driver
997-01520-02 Rev. G2.......................................................................... Page 135
Software
35. [39]Rainer Pruy <[email protected]>
monitoring/trap scripts, statistics file handling
36. [40]Dirce Richards <[email protected]> Digital UNIX V4.0 port
37. [41]Wilfredo Snchez <[email protected]> added support for
NetInfo
38. [42]Nick Sayer <[email protected]> SunOS streams modules
39. [43]Jack Sasportas <[email protected]> Saved a Lot of
space on the stuff in the html/pic/ subdirectory
40. [44]Ray Schnitzler <[email protected]> Unixware1 port
41. [45]Michael Shields <[email protected]> USNO clock driver
42. [46]Jeff Steinman <[email protected]> Datum PTS clock
driver
43. [47]Harlan Stenn <[email protected]> GNU automake/autoconfigure
makeover, various other bits (see the ChangeLog)
44. [48]Kenneth Stone <[email protected]> HP-UX port
45. [49]Ajit Thyagarajan <[email protected]>IP multicast/anycast
support
46. [50]Tomoaki TSURUOKA <[email protected]>TRAK clock
driver
47. [51]Paul A Vixie <[email protected]> TrueTime GPS driver, generic
TrueTime clock driver
48. [52]Ulrich Windl <[email protected]> corrected and
validated HTML documents according to the HTML DTD
________________________________________________________________
[53]gif
[54]David L. Mills <[email protected]>

References
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
mailto:[email protected]
mailto:jagubox.gsfc.nasa.gov
http://www4.informatik.uni-erlangen.de/~kardel
Page 136..........................................................................997-01520-02 Rev. G2

30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
mailto:pebbles.jpl.nasa.gov
file://localhost/backroom/ntp-stable/html/index.htm

Note! This copyright does *not* cover user programs that use kernel services by
normal system calls - this is merely considered normal use of the kernel, and does
*not* fall under the heading of "derived work".
Also note that the GPL below is copyrighted by the Free Software
Foundation, but the instance of code that it refers to (the Linux
kernel) is copyrighted by me and others who actually wrote it.
Also note that the only valid version of the GPL as far as the kernel
is concerned is _this_ particular version of the license (ie v2, not
v2.2 or v3.x or whatever), unless explicitly otherwise stated.
Linus Torvalds
---------------------------------------GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
997-01520-02 Rev. G2.......................................................................... Page 137
Software
License is intended to guarantee your freedom to share and change free software-to make sure the software is free for all its users. This General Public License
applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it.
(Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this service if you
wish), that you receive source code or can get it if you want it, that you can
change the software or use pieces of it in new free programs; and that you know
you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer
you this license which gives you legal permission to copy, distribute and/or
modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software
is modified by someone else and passed on, we want its recipients to know that
what they have is not the original, so that any problems introduced by others will
not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be
licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below, refers to
any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing
the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program is covered
only if its contents constitute a work based on the
Page 138..........................................................................997-01520-02 Rev. G2

Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty; and give
any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that
whole or in part contains or is
part thereof, to be licensed as
parties under the terms of this
you distribute or publish, that in

derived from the Program or any
a whole at no charge to all third
License.
c) If the modified program normally reads commands interactively

when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the
Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
997-01520-02 Rev. G2.......................................................................... Page 139
Software
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a special
exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to these terms
and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
Page 140..........................................................................997-01520-02 Rev. G2

otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this License and
any other pertinent obligations, then as a consequence you may not distribute the
Program at all. For example, if a patent license would not permit royalty-free
redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License
would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to apply and
the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that
choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the
General Public License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address new problems or
concerns.
Each version is given a distinguishing version number. If the Program specifies a
version number of this License which applies to it and "any later version", you
have the option of following the terms and conditions either of that version or of
any later version published by the Free Software Foundation. If the Program does
not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author to ask
for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for
this. Our decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing and reuse of
software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED
997-01520-02 Rev. G2.......................................................................... Page 141
Software
IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE
PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach
them to the start of each source file to most effectively convey the exclusion of
warranty; and each file should have at least the "copyright" line and a pointer to
where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it
starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts
of the General Public License. Of course, the commands you use may be called some-
Page 142..........................................................................997-01520-02 Rev. G2

thing other than `show w' and `show c'; they could even be mouse-clicks or menu
items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if
any, to sign a "copyright disclaimer" for the program, if necessary. Here is a
sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it
more useful to permit linking proprietary applications with the library. If this
is what you want to do, use the GNU Library General Public License instead of this
License.

Various copyrights apply to this package, listed in 3 separate parts
below. Please make sure that you all the parts. Up until 2001, the
project was based at UC Davis, and the first part covers all code
written during this time. From 2001 onwards, the project has been
based at SourceForge, and Networks Associates Technology, Inc hold the
copyright on behalf of the wider Net-SNMP community, covering all
derivative work done since then. An additional copyright section has
been added as Part 3 below also under a BSD license for the work
contributed by Cambridge Broadband Ltd. to the project since 2001.
Code has been contributed to this project by many people over
the years it has been in development, and a full list of contributors
can be found in the README file under the THANKS section.
---- Part 1: CMU/UCD copyright notice: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appears in all copies and
that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of CMU and The Regents of
the University of California not be used in advertising or publicity
pertaining to distribution of the software without specific written
permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR
997-01520-02 Rev. G2.......................................................................... Page 143
Software
THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE,
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) ----Copyright (c) 2001-2002, Networks Associates Technology, Inc
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the Networks Associates Technology, Inc nor the
names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS
IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) ----Portions of this code are copyright (c) 2001-2002, Cambridge Broadband Ltd.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* The name of Cambridge Broadband Ltd. may not be used to endorse or
promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER `ÀS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
Page 144..........................................................................997-01520-02 Rev. G2
ETX Module

The following devices contain either volatile or non-volatile memory:
In This section
ETX Module
86-611xPCB
MC9S12DG256 (U2)
145
145
146
ETX Module
n
256MB SDRAM. The 256MB Synchronous Dynamic RAM is installed on the ETX Module in a DIMM socket. This part is used as system RAM memory for the ETX Module's
x86 processor. The content in this device is volatile and is lost when the SyncServer is
powered down. This part is socketed (ETX).
BIOS. 512KB FLASH memory used on the ETX module for system BIOS. This part is
soldered to the ETX module. This part is not reprogrammed in normal operation. The content in this device is non-volatile and there is no procedure to clear this memory.
86-611xPCB
n
512MB Compact Flash Primary (J3). The 512MB Compact Flash device is installed on
the 86-610x PCB. This part is used as a virtual Hard Drive by the ETX Modules x86 processor. There is no procedure to clear this memory. This part is socketed (J3).
U41 is a Xilinx XC2S200 FPGA that is re-programmed each time the board is powered
up. The program for this part is contained in J3s Compact Flash memory and is downloaded into U41 by U39. The content of this device is volatile and is lost when the board is
powered down. This part is soldered to the PCB.
M93C46 1Kb Serial Microwire EEPROM for Intel 82551ER Fast Ethernet Controller configuration (U34). This non-volatile part is used at power-on to initialize registers in the
Intel Fast Ethernet Controller. This part is not reprogrammed in normal operation. This
part is a DIP that is mounted in an 8-pin socket.
M93C46 1Kb Serial Microwire EEPROM for system configuration (U40), controlled by
PCI9030. This non-volatile part is used to store unit specific data. This part is a DIP that is
mounted in an 8-pin socket.
997-01520-02 Rev. G2.......................................................................... Page 145
MC9S12DG256 (U2)
n
(U2) 256KB Flash program memory. This Flash memory is used for microprocessor program storage. This part is not reprogrammed in normal operation. The content in this
device is non-volatile and there is no procedure to clear this memory. This part is
soldered to the PCB.
(U2) 12KB RAM. This RAM is embedded in U2 and is used as operating memory. The
content in this device is volatile and is lost when the SyncServer is powered down. This
part is soldered to the PCB.
(U2) 4KB EEPROM. This EEPROM is embedded in U2 and is used to store non-volatile
configuration data. This part is soldered to the PCB.
Page 146..........................................................................997-01520-02 Rev. G2
United States

To determine the position of the GPS antenna, use one of the following methods or
resources (sorted by degree of accuracy).
n
n
n
Use a handheld GPS unit outdoors or temporarily run the SyncServer with its GPS
antenna outdoors.
http://jan.ucc.nau.edu/~cvm/latlon_find_location.html
http://geonames.usgs.gov/pls/gnispublic
The following reference topics also provide the approximate latitude and longitude for many
locations around the world:
n
n
n
United States (on page 147)

Canada (on page 162)
International (on page 164)
United States
ALABAMA
Alexander City
Anniston AP
Auburn
Birmingham AP
Decatur
Dothan AP
Florence AP
Gadsden
Huntsville AP
Mobile AP
Mobile Co
Montgomery AP
Selma-Craig AFB
Talladega
Tuscaloosa AP
32
33
32
33
34
31
34
34
34
30
30
32
32
33
33
57' N
35' N
36' N
34' N
37' N
19' N
48' N
1' N
42' N
41' N
40' N
23' N
20' N
27' N
13' N
85
85
85
86
86
85
87
86
86
88
88
86
87
86
87
57' W
51' W
30' W
45' W
59' W
27' W
40' W
0' W
35' W
15' W
15' W
22' W
59' W
6' W
37' W
Anchorage AP
Barrow (S)
Fairbanks AP (S)
Juneau AP
Kodiak
Nome AP
ARIZONA
Douglas AP
Flagstaff AP
Fort Huachuca AP (S)
Kingman AP
Nogales
61
71
64
58
57
64
10'
18'
49'
22'
45'
30'
N
N
N
N
N
N
150
156
147
134
152
165
1' W
47' W
52' W
35' W
29' W
26' W
31
35
31
35
31
27' N
8' N
35' N
12' N
21' N
109
111
110
114
110
36' W
40' W
20' W
1' W
55' W
ALASKA
997-01520-02 Rev. G2.......................................................................... Page 147

Phoenix AP (S)
Prescott AP
Tucson AP (S)
Winslow AP
Yuma AP
ARKANSAS
Blytheville AFB
Camden
El Dorado AP
Fayetteville AP
Fort Smith AP
Hot Springs
Jonesboro
Little Rock AP (S)
Pine Bluff AP
Texarkana AP
CALIFORNIA
Bakersfield AP
Barstow AP
Blythe AP
Burbank AP
Chico
Concord
Covina
Crescent City AP
Downey
El Cajon
El Cerrito AP (S)
Escondido
Eureka/Arcata AP
Fairfield-Trafis AFB
Fresno AP (S)
Hamilton AFB
Laguna Beach
Livermore
Lompoc, Vandenberg AFB
Long Beach AP
Los Angeles AP (S)
Los Angeles CO (S)
Merced-Castle AFB
Modesto
Monterey
Napa
Needles AP
Oakland AP
Oceanside
Ontario
Oxnard
Palmdale AP
Palm Springs
Pasadena
Petaluma
Pomona Co
Redding AP
33
34
32
35
32
26' N
39' N
7' N
1' N
39' N
35
33
33
36
35
34
35
34
34
33
57' N
36' N
13' N
0' N
20' N
29' N
50' N
44' N
18' N
27' N
35
34
33
34
39
37
34
41
33
32
32
33
40
38
36
38
33
37
34
33
33
34
37
37
36
38
34
37
33
34
34
34
33
34
38
34
40
25' N
51' N
37' N
12' N
48' N
58' N
5' N
46' N
56' N
49' N
49' N
7' N
59' N
16' N
46' N
4' N
33' N
42' N
43' N
49' N
56' N
3' N
23' N
39' N
36' N
13' N
36' N
49' N
14' N
3' N
12' N
38' N
49' N
9' N
14' N
3' N
31' N
112
112
110
110
114
1' W
26' W
56' W
44' W
37' W
89
92
92
94
94
93
90
92
92
93
57' W
49' W
49' W
10' W
22' W
6' W
42' W
14' W
5' W
59' W
119
116
114
118
121
121
117
124
118
116
115
117
124
121
119
122
117
121
120
118
118
118
120
121
121
122
114
122
117
117
119
118
116
118
122
117
122
3' W
47' W
43' W
21' W
51' W
59' W
52' W
12' W
8' W
58' W
40' W
5' W
6' W
56' W
43' W
30' W
47' W
57' W
34' W
9' W
24' W
14' W
34' W
0' W
54' W
17' W
37' W
19' W
25' W
36' W
11' W
6' W
32' W
9' W
38' W
45' W
18' W
Page 148..........................................................................997-01520-02 Rev. G2
United States
Redlands
Richmond
Riverside-March AFB (S)
Sacramento AP
Salinas AP
San Bernadino, Norton AFB
San Diego AP
San Fernando
San Francisco AP
San Francisco Co
San Jose AP
San Louis Obispo
Santa Ana AP
Santa Barbara MAP
Santa Cruz
Santa Maria AP (S)
Santa Monica CIC
Santa Paula
Santa Rosa
Stockton AP
Ukiah
Visalia
Yreka
Yuba City
COLORADO
Alamosa AP
Boulder
Colorado Springs AP
Denver AP
Durango
Fort Collins
Grand Junction AP (S)
Greeley
Lajunta AP
Leadville
Pueblo AP
Sterling
Trinidad
CONNECTICUT
Bridgeport AP
Hartford, Brainard Field
New Haven AP
New London
Norwalk
Norwick
Waterbury
Widsor Locks, Bradley Fld
DELAWARE
Dover AFB
Wilmington AP
DISTRICT OF COLUMBIA
Andrews AFB
Washington, National AP
FLORIDA
34
37
33
38
36
34
32
34
37
37
37
35
33
34
36
34
34
34
38
37
39
36
41
39
3' N
56' N
54' N
31' N
40' N
8' N
44' N
17' N
37' N
46' N
22' N
20' N
45' N
26' N
59' N
54' N
1' N
21' N
31' N
54' N
9' N
20' N
43' N
8' N
117
122
117
121
121
117
117
118
122
122
121
120
117
119
122
120
118
119
122
121
123
119
122
121
11' W
21' W
15' W
30' W
36' W
16' W
10' W
28' W
23' W
26' W
56' W
43' W
52' W
50' W
1' W
27' W
29' W
5' W
49' W
15' W
12' W
18' W
38' W
36' W
37
40
38
39
37
40
39
40
38
39
38
40
37
27' N
0' N
49' N
45' N
17' N
45' N
7' N
26' N
3' N
15' N
18' N
37' N
15' N
105
105
104
104
107
105
108
104
103
106
104
103
104
52' W
16' W
43' W
52' W
53' W
5' W
32' W
38' W
30' W
18' W
29' W
12' W
20' W
41
41
41
41
41
41
41
41
11' N
44' N
19' N
21' N
7' N
32' N
35' N
56' N
73
72
73
72
73
72
73
72
11' W
39' W
55' W
6' W
25' W
4' W
4' W
41' W
39 8' N 75 28' W
39 40' N 75 36' W
38 5' N 76 5' W
38 51' N 77 2' W
997-01520-02 Rev. G2.......................................................................... Page 149

Belle Glade
Cape Kennedy AP
Daytona Beach AP
E Fort Lauderdale
Fort Myers AP
Fort Pierce
Gainsville AP (S)
Jacksonville AP
Key West AP
Lakeland Co (S)
Miami AP (S)
Miami Beach Co
Ocala
Orlando AP
Panama City, Tyndall AFB
Pensacola Co
St. Augustine
St. Petersburg
Stanford
Sarasota
Tallahassee AP (S)
Tampa AP (S)
West Palm Beach AP
GEORGIA
Albany, Turner AFB
Americus
Athens
Atlanta AP (S)
Augusta AP
Brunswick
Columbus, Lawson AFB
Dalton
Dublin
Gainsville
Griffin
LaGrange
Macon AP
Marietta, Dobbins AFB
Savannah
Valdosta-Moody AFB
Waycross
HAWAII
Hilo AP (S)
Honolulu AP
Kaneohe Bay MCAS
Wahiawa
IDAHO
Boise AP (S)
Burley
Coeur D'Alene AP
Idaho Falls AP
Lewiston AP
Moscow
Mountain Home AFB
26
28
29
26
26
27
29
30
24
28
25
25
29
28
30
30
29
27
28
27
30
27
26
39' N
29' N
11' N
4' N
35' N
28' N
41' N
30' N
33' N
2' N
48' N
47' N
11' N
33' N
4' N
25' N
58' N
46' N
46' N
23' N
23' N
58' N
41' N
80
80
81
80
81
80
82
81
81
81
80
80
82
81
85
87
81
82
81
82
84
82
80
39' W
34' W
3' W
9' W
52' W
21' W
16' W
42' W
45' W
57' W
16' W
17' W
8' W
23' W
35' W
13' W
20' W
80' W
17' W
33' W
22' W
32' W
6' W
31
32
33
33
33
31
32
34
32
34
33
33
32
33
32
30
31
36' N
3' N
57' N
39' N
22' N
15' N
31' N
34' N
20' N
11' N
13' N
1' N
42' N
55' N
8' N
58' N
15' N
84
84
83
84
81
81
84
84
82
83
84
85
83
84
81
83
82
5' W
14' W
19' W
26' W
58' W
29' W
56' W
57' W
54' W
41' W
16' W
4' W
39' W
31' W
12' W
12' W
24' W
19
21
21
21
43' N
20' N
27' N
3' N
155
157
157
158
5' W
55' W
46' W
2' W
43
42
47
43
46
46
43
34' N
32' N
46' N
31' N
23' N
44' N
2' N
116
113
116
112
117
116
115
13' W
46' W
49' W
4' W
1' W
58' W
54' W
Page 150..........................................................................997-01520-02 Rev. G2
United States
Pocatello AP
Twin Falls AP (S)
ILLINOIS
Aurora
Belleville, Scott AFB
Bloomington
Carbondale
Champaign/Urbana
Chicago, Midway AP
Chicago, O'Hare AP
Chicago Co
Danville
Decatur
Dixon
Elgin
Freeport
Galesburg
Greenville
Joliet
Kankakee
La Salle/Peru
Macomb
Moline AP
Mt Vernon
Peoria AP
Quincy AP
Rantoul, Chanute AFB
Rockford
Springfield AP
Waukegan
INDIANA
Anderson
Bedford
Bloomington
Columbus, Bakalar AFB
Crawfordsville
Evansville AP
Fort Wayne AP
Goshen AP
Hobart
Huntington
Indianapolis AP
Jeffersonville
Kokomo
Lafayette
La Porte
Marion
Muncie
Peru, Grissom AFB
Richmond AP
Shelbyville
South Bend AP
Terre Haute AP
Valparaiso
42 55' N 112 36' W

42 29' N 114 29' W
41
38
40
37
40
41
41
41
40
39
41
42
42
40
38
41
41
41
40
41
38
40
39
40
42
39
42
45' N
33' N
29' N
47' N
2' N
47' N
59' N
53' N
12' N
50' N
50' N
2' N
18' N
56' N
53' N
31' N
5' N
19' N
28' N
27' N
19' N
40' N
57' N
18' N
21' N
50' N
21' N
88
89
88
89
88
87
87
87
87
88
89
88
89
90
89
88
87
89
90
90
88
89
91
88
89
89
87
20' W
51' W
57' W
15' W
17' W
45' W
54' W
38' W
36' W
52' W
29' W
16' W
37' W
26' W
24' W
10' W
55' W
6' W
40' W
31' W
52' W
41' W
12' W
8' W
3' W
40' W
53' W
40
38
39
39
40
38
41
41
41
40
39
38
40
40
41
40
40
40
39
39
41
39
41
6' N
51' N
8' N
16' N
3' N
3' N
0' N
32' N
32' N
53' N
44' N
17' N
25' N
2' N
36' N
29' N
11' N
39' N
46' N
31' N
42' N
27' N
31' N
85
86
86
85
86
87
85
85
87
85
86
85
86
86
86
85
85
86
84
85
86
87
87
37' W
30' W
37' W
54' W
54' W
32' W
12' W
48' W
15' W
30' W
17' W
45' W
3' W
5' W
43' W
41' W
21' W
9' W
50' W
47' W
19' W
18' W
2' W
997-01520-02 Rev. G2.......................................................................... Page 151

Vincennes
IOWA
Ames (S)
Burlington AP
Cedar Rapids AP
Clinton
Council Bluffs
Des Moines AP
Dubuque
Fort Dodge
Iowa City
Keokuk
Marshalltown
Mason City AP
Newton
Ottumwa AP
Sioux City AP
Waterloo
KANSAS
Atchison
Chanute AP
Dodge City AP (S)
El Dorado
Emporia
Garden City AP
Goodland AP
Great Bend
Hutchinson AP
Liberal
Manhattan, Ft Riley (S)
Parsons
Russell AP
Salina
Topeka AP
Wichita AP
KENTUCKY
Ashland
Bowling Green AP
Corbin AP
Covington AP
Hopkinsville, Ft Campbell
Lexington AP (S)
Louisville AP
Madisonville
Owensboro
Paducah AP
LOUISIANA
Alexandria AP
Baton Rouge AP
Bogalusa
Houma
Lafayette AP
Lake Charles AP (S)
Minden
38 41' N 87 32' W
42
40
41
41
41
41
42
42
41
40
42
43
41
41
42
42
2' N
47' N
53' N
50' N
20' N
32' N
24' N
33' N
38' N
24' N
4' N
9' N
41' N
6' N
24' N
33' N
93
91
91
90
95
93
90
94
91
91
92
93
93
92
96
92
48' W
7' W
42' W
13' W
49' W
39' W
42' W
11' W
33' W
24' W
56' W
20' W
2' W
27' W
23' W
24' W
39
37
37
37
38
37
39
38
38
37
39
37
38
38
39
37
34' N 95
40' N 95
46' N 99
49' N 96
20' N 96
56' N 100
22' N 101
21' N 98
4' N 97
3' N 100
3' N 96
20' N 95
52' N 98
48' N 97
4' N 95
39' N 97
7' W
29' W
58' W
50' W
12' W
44' W
42' W
52' W
52' W
58' W
46' W
31' W
49' W
39' W
38' W
25' W
38
35
36
39
36
38
38
37
37
37
33' N
58' N
57' N
3' N
40' N
2' N
11' N
19' N
45' N
4' N
82
86
84
84
87
84
85
87
87
88
44' W
28' W
6' W
40' W
29' W
36' W
44' W
29' W
10' W
46' W
31
30
30
29
30
30
32
24' N
32' N
47' N
31' N
12' N
7' N
36' N
92
91
89
90
92
93
93
18' W
9' W
52' W
40' W
0' W
13' W
18' W
Page 152..........................................................................997-01520-02 Rev. G2
United States
Monroe AP
Natchitoches
New Orleans AP
Shreveport AP (S)
MAINE
Augusta AP
Bangor, Dow AFB
Caribou AP (S)
Lewiston
Millinocket AP
Portland (S)
Waterville
MARYLAND
Baltimore AP
Baltimore Co
Cumberland
Frederick AP
Hagerstown
Salisbury (S)
MASSACHUSETTS
Boston AP
Clinton
Fall River
Framingham
Gloucester
Greenfield
Lawrence
Lowell
New Bedford
Pittsfield AP
Springfield, Westover AFB
Taunton
Worcester AP
MICHIGAN
Adrian
Alpena AP
Battle Creek AP
Benton Harbor AP
Detroit
Escanaba
Flint AP
Grand Rapids AP
Holland
Jackson AP
Kalamazoo
Lansing AP
Marquette Co
Mt Pleasant
Muskegon AP
Pontiac
Port Huron
Saginaw AP
Sault Ste. Marie AP (S)
Traverse City AP
32
31
29
32
31'
46'
59'
28'
N
N
N
N
92
93
90
93
2' W
5' W
15' W
49' W
44
44
46
44
45
43
44
19' N
48' N
52' N
2' N
39' N
39' N
32' N
69
68
68
70
68
70
69
48' W
50' W
1' W
15' W
42' W
19' W
40' W
39
39
39
39
39
38
11'
20'
37'
27'
42'
20'
N
N
N
N
N
N
76
76
78
77
77
75
40'
25'
46'
25'
44'
30'
42
42
41
42
42
42
42
42
41
42
42
41
42
22' N
24' N
43' N
17' N
35' N
3' N
42' N
39' N
41' N
26' N
12' N
54' N
16' N
71
71
71
71
70
72
71
71
70
73
72
71
71
2' W
41' W
8' W
25' W
41' W
4' W
10' W
19' W
58' W
18' W
32' W
4' W
52' W
41
45
42
42
42
45
42
42
42
42
42
42
46
43
43
42
42
43
46
44
55' N
4' N
19' N
8' N
25' N
44' N
58' N
53' N
42' N
16' N
17' N
47' N
34' N
35' N
10' N
40' N
59' N
32' N
28' N
45' N
84
83
85
86
83
87
83
85
86
84
85
84
87
84
86
83
82
84
84
85
1' W
26' W
15' W
26' W
1' W
5' W
44' W
31' W
6' W
28' W
36' W
36' W
24' W
46' W
14' W
25' W
25' W
5' W
22' W
35' W
W
W
W
W
W
W
997-01520-02 Rev. G2.......................................................................... Page 153

Ypsilanti
MINNESOTA
Albert Lea
Alexandria AP
Bemidji AP
Brainerd
Duluth AP
Fairbault
Fergus Falls
International Falls AP
Mankato
Minneapolis/St. Paul AP
Rochester AP
St. Cloud AP (S)
Virginia
Willmar
Winona
MISSISSIPPI
Biloxi--Keesler AFB
Clarksdale
Columbus AFB
Greenville AFB
Greenwood
Hattiesburg
Jackson AP
Laurel
Mccomb AP
Meridian AP
Natchez
Tupelo
Vicksburg Co
MISSOURI
Cape Girardeau
Columbia AP (S)
Farmington AP
Hannibal
Jefferson City
Joplin AP
Kansas City AP
Kirksville AP
Mexico
Moberly
Poplar Bluff
Rolla
St. Joseph AP
St. Louis AP
St. Louis CO
Sikeston
Sedalia--Whiteman AFB
Sikeston
Springfield AP
MONTANA
Billings AP
Bozeman
42 14' N 83 32' W
43
45
47
46
46
44
46
48
44
44
43
45
47
45
44
39' N
52' N
31' N
24' N
50' N
18' N
16' N
34' N
9' N
53' N
55' N
35' N
30' N
7' N
3' N
93
95
94
94
92
93
96
93
93
93
92
94
92
95
91
21' W
23' W
56' W
8' W
11' W
16' W
4' W
23' W
59' W
13' W
30' W
11' W
33' W
5' W
38' W
30
34
33
33
33
31
32
31
31
32
31
34
32
25'
12'
39'
29'
30'
16'
19'
40'
15'
20'
33'
16'
24'
N
N
N
N
N
N
N
N
N
N
N
N
N
88
90
88
90
90
89
90
89
90
88
91
88
90
55' W
34' W
27' W
59' W
5' W
15' W
5' W
10' W
28' W
45' W
23' W
46' W
47' W
37
38
37
39
38
37
39
40
39
39
36
37
39
38
38
36
38
36
37
14' N
58' N
46' N
42' N
34' N
9' N
7' N
6' N
11' N
24' N
46' N
59' N
46' N
45' N
39' N
53' N
43' N
53' N
14' N
89
92
90
91
92
94
94
92
91
92
90
91
94
90
90
89
93
89
93
35'
22'
24'
21'
11'
30'
35'
33'
54'
26'
25'
43'
55'
23'
38'
36'
33'
36'
23'
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
45 48' N 108 32' W

45 47' N 111 9' W
Page 154..........................................................................997-01520-02 Rev. G2
United States
Butte AP
Cut Bank AP
Glasgow AP (S)
Glendive
Great Falls AP (S)
Havre
Helena AP
Kalispell AP
Lewiston AP
Livingstown AP
Miles City AP
Missoula AP
NEBRASKA
Beatrice
Chadron AP
Columbus
Fremont
Grand Island AP
Hastings
Kearney
Lincoln Co (S)
McCook
Norfolk
North Platte AP (S)
Omaha AP
Scottsbluff AP
Sidney AP
NEVADA
Carson City
Elko AP
Ely AP (S)
Las Vegas AP (S)
Lovelock AP
Reno AP (S)
Reno Co
Tonopah AP
Winnemucca AP
NEW HAMPSHIRE
Berlin
Claremont
Concord AP
Keene
Laconia
Manchester, Grenier AFB
Portsmouth, Pease AFB
NEW JERSEY
Atlantic City CO
Long Branch
Newark AP
New Brunswick
Paterson
Phillipsburg
Trenton Co
Vineland
45
48
48
47
47
48
46
48
47
45
46
46
57' N
37' N
25' N
8' N
29' N
34' N
36' N
18' N
4' N
42' N
26' N
55' N
112
112
106
104
111
109
112
114
109
110
105
114
30' W
22' W
32' W
48' W
22' W
40' W
0' W
16' W
27' W
26' W
52' W
5' W
40
42
41
41
40
40
40
40
40
41
41
41
41
41
16' N 96
50' N 103
28' N 97
26' N 96
59' N 98
36' N 98
44' N 99
51' N 96
12' N 100
59' N 97
8' N 100
18' N 95
52' N 103
13' N 103
45' W
5' W
20' W
29' W
19' W
26' W
1' W
45' W
38' W
26' W
41' W
54' W
36' W
6' W
39
40
39
36
40
39
39
38
40
10' N
50' N
17' N
5' N
4' N
30' N
30' N
4' N
54' N
119
115
114
115
118
119
119
117
117
46' W
47' W
51' W
10' W
33' W
47' W
47' W
5' W
48' W
44
43
43
42
43
42
43
3' N
2' N
12' N
55' N
3' N
56' N
4' N
71
72
71
72
71
71
70
1' W
2' W
30' W
17' W
3' W
26' W
49' W
39
40
40
40
40
40
40
39
23'
19'
42'
29'
54'
41'
13'
29'
74
74
74
74
74
75
74
75
26' W
1' W
10' W
26' W
9' W
11' W
46' W
0' W
N
N
N
N
N
N
N
N
997-01520-02 Rev. G2.......................................................................... Page 155

NEW MEXICO
Alamagordo
Holloman AFB
Albuquerque AP (S)
Artesia
Carlsbad AP
Clovis AP
Farmington AP
Gallup
Grants
Hobbs AP
Las Cruces
Los Alamos
Raton AP
Roswell, Walker AFB
Santa Fe CO
Silver City AP
Socorro AP
Tucumcari AP
NEW YORK
Albany AP (S)
Albany Co
Auburn
Batavia
Binghamton AP
Buffalo AP
Cortland
Dunkirk
Elmira AP
Geneva (S)
Glens Falls
Gloversville
Hornell
Ithaca (S)
Jamestown
Kingston
Lockport
Massena AP
Newburgh, Stewart AFB
NYC-Central Park (S)
NYC-Kennedy AP
NYC-La Guardia AP
Niagara Falls AP
Olean
Oneonta
Oswego Co
Plattsburg AFB
Poughkeepsie
Rochester AP
Rome, Griffiss AFB
Schenectady (S)
Suffolk County AFB
Syracuse AP
Utica
32
35
32
32
34
36
35
35
32
32
35
36
33
35
32
34
35
51' N
3' N
46' N
20' N
23' N
44' N
31' N
10' N
45' N
18' N
52' N
45' N
18' N
37' N
38' N
3' N
11' N
42
42
42
43
42
42
42
42
42
42
43
43
42
42
42
41
43
44
41
40
40
40
43
42
42
43
44
41
43
43
42
40
43
43
45' N
39' N
54' N
0' N
13' N
56' N
36' N
29' N
10' N
45' N
20' N
2' N
21' N
27' N
7' N
56' N
9' N
56' N
30' N
47' N
39' N
46' N
6' N
14' N
31' N
28' N
39' N
38' N
7' N
14' N
51' N
51' N
7' N
9' N
106
106
104
104
103
108
108
107
103
106
106
104
104
106
108
106
103
6' W
37' W
23' W
16' W
19' W
14' W
47' W
54' W
13' W
55' W
19' W
30' W
32' W
5' W
10' W
53' W
36' W
73
73
76
78
75
78
76
79
76
76
73
74
77
76
79
74
79
74
74
73
73
73
79
78
75
76
73
73
77
75
73
72
76
75
48' W
45' W
32' W
11' W
59' W
44' W
11' W
16' W
54' W
54' W
37' W
21' W
42' W
29' W
14' W
0' W
15' W
51' W
6' W
58' W
47' W
54' W
57' W
22' W
4' W
33' W
28' W
55' W
40' W
25' W
57' W
38' W
7' W
23' W
Page 156..........................................................................997-01520-02 Rev. G2
United States
Watertown
NORTH CAROLINA
Asheville AP
Charlotte AP
Durham
Elizabeth City AP
Fayetteville, Pope AFB
Goldsboro,Seymour-Johnson
Greensboro AP (S)
Greenville
Henderson
Hickory
Jacksonville
Lumberton
New Bern AP
Raleigh/Durham AP (S)
Rocky Mount
Wilmington AP
Winston-Salem AP
NORTH DAKOTA
Bismarck AP (S)
Devils Lake
Dickinson AP
Fargo AP
Grand Forks AP
Jamestown AP
Minot AP
Williston
OHIO
Akron-Canton AP
Ashtabula
Athens
Bowling Green
Cambridge
Chillicothe
Cincinnati Co
Cleveland AP (S)
Columbus AP (S)
Dayton AP
Defiance
Findlay AP
Fremont
Hamilton
Lancaster
Lima
Mansfield AP
Marion
Middletown
Newark
Norwalk
Portsmouth
Sandusky Co
Springfield
Steubenville
43 59' N 76 1' W
35
35
35
36
35
35
36
35
36
35
34
34
35
35
35
34
36
26' N
13' N
52' N
16' N
10' N
20' N
5' N
37' N
22' N
45' N
50' N
37' N
5' N
52' N
58' N
16' N
8' N
82
80
78
76
79
77
79
77
78
81
77
79
77
78
77
77
80
46
48
46
46
47
46
48
48
46' N 100
7' N 98
48' N 102
54' N 96
57' N 97
55' N 98
25' N 101
9' N 103
45'
54'
48'
48'
24'
41'
21'
35'
40
41
39
41
40
39
39
41
40
39
41
41
41
39
39
40
40
40
39
40
41
38
41
39
40
55' N
51' N
20' N
23' N
4' N
21' N
9' N
24' N
0' N
54' N
17' N
1' N
20' N
24' N
44' N
42' N
49' N
36' N
31' N
1' N
16' N
45' N
27' N
50' N
23' N
26' W
48' W
6' W
38' W
35' W
0' W
31' W
51' W
53' W
13' W
23' W
40' W
7' W
35' W
38' W
2' W
31' W
10' W
25' W
28' W
37' W
55' W
43' W
50' W
38' W
81
80
82
83
81
83
84
81
82
84
84
83
83
84
82
84
82
83
84
82
82
82
82
83
80
32' W
56' W
47' W
11' W
1' W
58' W
57' W
25' W
25' W
23' W
37' W
4' W
3' W
47' W
48' W
55' W
13' W
W
W
W
W
W
W
W
W
997-01520-02 Rev. G2.......................................................................... Page 157

Toledo AP
Warren
Wooster
Youngstown AP
Zanesville AP
OKLAHOMA
Ada
Altus AFB
Ardmore
Bartlesville
Chickasha
Enid, Vance AFB
Lawton AP
McAlester
Muskogee AP
Norman
Oklahoma City AP (S)
Ponca City
Seminole
Stillwater (S)
Tulsa AP
Woodward
OREGON
Albany
Astoria AP (S)
Baker AP
Bend
Corvallis (S)
Eugene AP
Grants Pass
Klamath Falls AP
Medford AP (S)
Pendleton AP
Portland AP
Portland Co
Roseburg AP
Salem AP
The Dalles
PENNSYLVANIA
Allentown AP
Altoona Co
Butler
Chambersburg
Erie AP
Harrisburg AP
Johnstown
Lancaster
Meadville
New Castle
Philadelphia AP
Pittsburgh AP
Pittsburgh Co
Reading Co
Scranton/Wilkes-Barre
41
41
40
41
39
36'
20'
47'
16'
57'
N
N
N
N
N
83
80
81
80
81
48'
51'
55'
40'
54'
W
W
W
W
W
34
34
34
36
35
36
34
34
35
35
35
36
35
36
36
36
47' N
39' N
18' N
45' N
3' N
21' N
34' N
50' N
40' N
15' N
24' N
44' N
14' N
10' N
12' N
36' N
96
99
97
96
97
97
98
95
95
97
97
97
96
97
95
99
41' W
16' W
1' W
0' W
55' W
55' W
25' W
55' W
22' W
29' W
36' W
6' W
40' W
5' W
54' W
31' W
44
46
44
44
44
44
42
42
42
45
45
45
43
44
45
38' N
9' N
50' N
4' N
30' N
7' N
26' N
9' N
22' N
41' N
36' N
32' N
14' N
55' N
36' N
123
123
117
121
123
123
123
121
122
118
122
122
123
123
121
7' W
53' W
49' W
19' W
17' W
13' W
19' W
44' W
52' W
51' W
36' W
40' W
22' W
1' W
12' W
40
40
40
39
42
40
40
40
41
41
39
40
40
40
41
39' N
18' N
52' N
56' N
5' N
12' N
19' N
7' N
38' N
1' N
53' N
30' N
27' N
20' N
20' N
75
78
79
77
80
76
78
76
80
80
75
80
80
75
75
26' W
19' W
54' W
38' W
11' W
46' W
50' W
18' W
10' W
22' W
15' W
13' W
0' W
38' W
44' W
Page 158..........................................................................997-01520-02 Rev. G2
United States
State College (S)
Sunbury
Uniontown
Warren
West Chester
Williamsport AP
York
RHODE ISLAND
Newport (S)
Providence AP
SOUTH CAROLINA
Anderson
Charleston AFB (S)
Charleston Co
Columbia AP
Florence AP
Georgetown
Greenville AP
Greenwood
Orangeburg
Rock Hill
Spartanburg AP
Sumter, Shaw AFB
SOUTH DAKOTA
Aberdeen AP
Brookings
Huron AP
Mitchell
Pierre AP
Rapid City AP (S)
Sioux Falls AP
Watertown AP
Yankton
TENNESSEE
Athens
Bristol-Tri City AP
Chattanooga AP
Clarksville
Columbia
Dyersburg
Greenville
Jackson AP
Knoxville AP
Memphis AP
Murfreesboro
Nashville AP (S)
Tullahoma
TEXAS
Abilene AP
Alice AP
Amarillo AP
Austin AP
Bay City
Beaumont
40
40
39
41
39
41
39
48'
53'
55'
51'
58'
15'
55'
N
N
N
N
N
N
N
77
76
79
79
75
76
76
52' W
46' W
43' W
8' W
38' W
55' W
45' W
41 30' N 71 20' W
41 44' N 71 26' W
34
32
32
33
34
33
34
34
33
34
34
33
30'
54'
54'
57'
11'
23'
54'
10'
30'
59'
58'
54'
N
N
N
N
N
N
N
N
N
N
N
N
82
80
79
81
79
79
82
82
80
80
82
80
43' W
2' W
58' W
7' W
43' W
17' W
13' W
7' W
52' W
58' W
0' W
22' W
45
44
44
43
44
44
43
44
42
27' N 98
18' N 96
23' N 98
41' N 98
23' N 100
3' N 103
34' N 96
55' N 97
55' N 97
26' W
48' W
13' W
1' W
17' W
4' W
44' W
9' W
23' W
35
36
35
36
35
36
36
35
35
35
34
36
35
26' N
29' N
2' N
33' N
38' N
1' N
4' N
36' N
49' N
3' N
55' N
7' N
23' N
84
82
85
87
87
89
82
88
83
90
86
86
86
35' W
24' W
12' W
22' W
2' W
24' W
50' W
55' W
59' W
0' W
28' W
41' W
5' W
32
27
35
30
29
29
25' N 99
44' N 98
14' N 100
18' N 97
0' N 95
57' N 94
41' W
2' W
42' W
42' W
58' W
1' W
997-01520-02 Rev. G2.......................................................................... Page 159

Beeville
Big Spring AP (S)
Brownsville AP (S)
Brownwood
Bryan AP
Corpus Christi AP
Corsicana
Dallas AP
Del Rio, Laughlin AFB
Denton
Eagle Pass
El Paso AP (S)
Fort Worth AP (S)
Galveston AP
Greenville
Harlingen
Houston AP
Houston Co
Huntsville
Killeen, Robert Gray AAF
Lamesa
Laredo AFB
Longview
Lubbock AP
Lufkin AP
Mcallen
Midland AP (S)
Mineral Wells AP
Palestine Co
Pampa
Pecos
Plainview
Port Arthur AP
San Angelo
Goodfellow AFB
San Antonio AP (S)
Sherman, Perrin AFB
Snyder
Temple
Tyler AP
Vernon
Victoria AP
Waco AP
Wichita Falls AP
UTAH
Cedar City AP
Logan
Moab
Ogden AP
Price
Provo
Richfield
St George Co
Salt Lake City AP (S)
28
32
25
31
30
27
32
32
29
33
28
31
32
29
33
26
29
29
30
31
32
27
32
33
31
26
31
32
31
35
31
34
29
22' N 97
18' N 101
54' N 97
48' N 98
40' N 96
46' N 97
5' N 96
51' N 96
22' N 100
12' N 97
52' N 100
48' N 106
50' N 97
18' N 94
4' N 96
14' N 97
58' N 95
59' N 95
43' N 95
5' N 97
42' N 101
32' N 99
28' N 94
39' N 101
25' N 94
12' N 98
57' N 102
47' N 98
47' N 95
32' N 100
25' N 103
11' N 101
57' N 94
40' W
27' W
26' W
57' W
33' W
30' W
28' W
51' W
47' W
6' W
32' W
24' W
3' W
48' W
3' W
39' W
21' W
22' W
33' W
41' W
56' W
27' W
44' W
49' W
48' W
13' W
11' W
4' W
38' W
59' W
30' W
42' W
1' W
31
29
33
32
31
32
34
28
31
33
26' N 100
32' N 98
43' N 96
43' N 100
6' N 97
21' N 95
10' N 99
51' N 96
37' N 97
58' N 98
24'
28'
40'
55'
21'
16'
18'
55'
13'
29'
37
41
38
41
39
40
38
37
40
42' N
45' N
36' N
12' N
37' N
13' N
46' N
2' N
46' N
6' W
49' W
36' W
1' W
50' W
43' W
5' W
31' W
58' W
113
111
109
112
110
111
112
113
111
W
W
W
W
W
W
W
W
W
W
Page 160..........................................................................997-01520-02 Rev. G2
United States
Vernal AP
VERMONT
Barre
Burlington AP (S)
Rutland
VIRGINIA
Charlottesville
Danville AP
Fredericksburg
Harrisonburg
Lynchburg AP
Norfolk AP
Petersburg
Richmond AP
Roanoke AP
Staunton
Winchester
WASHINGTON
Aberdeen
Bellingham AP
Bremerton
Ellensburg AP
Everett, Paine AFB
Kennewick
Longview
Moses Lake, Larson AFB
Olympia AP
Port Angeles
Seattle-Boeing Field
Seattle Co (S)
Seattle-Tacoma AP (S)
Spokane AP (S)
Tacoma, McChord AFB
Walla Walla AP
Wenatchee
Yakima AP
WEST VIRGINIA
Beckley
Bluefield AP
Charleston AP
Clarksburg
Elkins AP
Huntington Co
Martinsburg AP
Morgantown AP
Parkersburg Co
Wheeling
WISCONSIN
Appleton
Ashland
Beloit
Eau Claire AP
Fond Du Lac
Green Bay AP
40 27' N 109 31' W

44 12' N 72 31' W
44 28' N 73 9' W
43 36' N 72 58' W
38
36
38
38
37
36
37
37
37
38
39
2' N
34' N
18' N
27' N
20' N
54' N
11' N
30' N
19' N
16' N
12' N
46
48
47
47
47
46
46
47
46
48
47
47
47
47
47
46
47
46
59' N
48' N
34' N
2' N
55' N
13' N
10' N
12' N
58' N
7' N
32' N
39' N
27' N
38' N
15' N
6' N
25' N
34' N
37
37
38
39
38
38
39
39
39
40
44
46
42
44
43
44
78
79
77
78
79
76
77
77
79
78
78
31'
20'
28'
54'
12'
12'
31'
20'
58'
54'
10'
W
W
W
W
W
W
W
W
W
W
W
123
122
122
120
122
119
122
119
122
123
122
122
122
117
122
118
120
120
49' W
32' W
40' W
31' W
17' W
8' W
56' W
19' W
54' W
26' W
18' W
18' W
18' W
31' W
30' W
17' W
19' W
32' W
47' N
18' N
22' N
16' N
53' N
25' N
24' N
39' N
16' N
7' N
81
81
81
80
79
82
77
79
81
80
7' W
13' W
36' W
21' W
51' W
30' W
59' W
55' W
34' W
42' W
15'
34'
30'
52'
48'
29'
88
90
89
91
88
88
23' W
58' W
2' W
29' W
27' W
8' W
N
N
N
N
N
N
997-01520-02 Rev. G2.......................................................................... Page 161

La Crosse AP
Madison AP (S)
Manitowoc
Marinette
Milwaukee AP
Racine
Sheboygan
Stevens Point
Waukesha
Wausau AP
WYOMING
Casper AP
Cheyenne
Cody AP
Evanston
Lander AP (S)
Laramie AP (S)
Newcastle
Rawlins
Rock Springs AP
Sheridan AP
Torrington
43
43
44
45
42
42
43
44
43
44
52' N
8' N
6' N
6' N
57' N
43' N
45' N
30' N
1' N
55' N
91
89
87
87
87
87
87
89
88
89
15'
20'
41'
38'
54'
51'
43'
34'
14'
37'
W
W
W
W
W
W
W
W
W
W
42
41
44
41
42
41
43
41
41
44
42
55' N
9' N
33' N
16' N
49' N
19' N
51' N
48' N
36' N
46' N
5' N
106
104
109
110
108
105
104
107
109
106
104
28' W
49' W
4' W
57' W
44' W
41' W
13' W
12' W
0' W
58' W
13' W
51
53
55
52
49
56
50
52
6' N
34' N
11' N
53' N
38' N
39' N
1' N
11' N
114
113
118
118
112
111
110
113
1' W
31' W
53' W
4' W
48' W
13' W
43' W
54' W
55
58
50
49
49
49
53
54
49
49
48
44' N
50' N
43' N
11' N
13' N
28' N
53' N
17' N
8' N
11' N
25' N
120
122
120
123
122
119
122
130
117
123
123
11'
35'
25'
58'
54'
36'
41'
23'
44'
10'
19'
49
58
51
54
49
52' N 99
45' N 94
6' N 100
46' N 101
54' N 98
Canada
ALBERTA
Calgary AP
Edmonton AP
Grande Prairie AP
Jasper
Lethbridge AP (S)
McMurray AP
Medicine Hat AP
Red Deer AP
BRITISH COLUMBIA
Dawson Creek
Fort Nelson AP (S)
Kamloops Co
Nanaimo (S)
New Westminster
Penticton AP
Prince George AP (S)
Prince Rupert Co
Trail
Vancouver AP (S)
Victoria Co
MANITOBA
Brandon
Churchill AP (S)
Dauphin AP
Flin Flon
Portage La Prairie AP
W
W
W
W
W
W
W
W
W
W
W
59' W
4' W
3' W
51' W
16' W
Page 162..........................................................................997-01520-02 Rev. G2
Canada
The Pas AP (S)
Winnipeg AP (S)
NEW BRUNSWICK
Campbellton Co
Chatham AP
Edmundston Co
Fredericton AP (S)
Moncton AP (S)
Saint John AP
NEWFOUNDLAND
Corner Brook
Gander AP
Goose Bay AP (S)
St John's AP (S)
Stephenville AP
NORTHWEST TERRITORIES
Fort Smith AP(S)
Frobisher AP (S)
Inuvik (S)
Resolute AP (S)
Yellowknife AP
NOVA SCOTIA
Amherst
Halifax AP (S)
Kentville (S)
New Glasgow
Sydney AP
Truro Co
Yarmouth AP
ONTARIO
Belleville
Chatham
Cornwall
Hamilton
Kapuskasing AP (S)
Kenora AP
Kingston
Kitchener
London AP
North Bay AP
Oshawa
Ottawa AP (S)
Owen Sound
Peterborough
St Catharines
Sarnia
Sault Ste Marie AP
Sudbury AP
Thunder Bay AP
Timmins AP
Toronto AP (S)
Windsor AP
PRINCE EDWARD ISLAND
Charlottetown AP (S)
53 58' N 101 6' W

49 54' N 97 14' W
48
47
47
45
46
45
0' N
1' N
22' N
52' N
7' N
19' N
66
65
68
66
64
65
40'
27'
20'
32'
41'
53'
W
W
W
W
W
W
48
48
53
47
48
58'
57'
19'
37'
32'
57
54
60
52
58
57'
34'
25'
45'
33'
W
W
W
W
W
60
63
68
74
62
1' N 111
45' N 68
18' N 133
43' N 94
28' N 114
58'
33'
29'
59'
27'
W
W
W
W
W
45
44
45
45
46
45
43
49' N
39' N
3' N
37' N
10' N
22' N
50' N
64
63
64
62
60
63
66
13' W
34' W
36' W
37' W
3' W
16' W
5' W
44
42
45
43
49
49
44
43
43
46
43
45
44
44
43
42
46
46
48
48
43
42
9' N
24' N
1' N
16' N
25' N
48' N
16' N
26' N
2' N
22' N
54' N
19' N
34' N
17' N
11' N
58' N
32' N
37' N
22' N
34' N
41' N
16' N
77
82
74
79
82
94
76
80
81
79
78
75
80
78
79
82
84
80
89
81
79
82
24' W
12' W
45' W
54' W
28' W
22' W
30' W
30' W
9' W
25' W
52' W
40' W
55' W
19' W
14' W
22' W
30' W
48' W
19' W
22' W
38' W
58' W
N
N
N
N
N
46 17' N 63 8' W
997-01520-02 Rev. G2.......................................................................... Page 163

Summerside AP
QUEBEC
Bagotville AP
Chicoutimi
Drummondville
Granby
Hull
Megantic AP
Montreal AP (S)
Quebec AP
Rimouski
St Jean
St Jerome
Sept. Iles AP (S)
Shawinigan
Sherbrooke Co
Thetford Mines
Trois Rivieres
Val D'or AP
Valleyfield
SASKATCHEWAN
Estevan AP
Moose Jaw AP
North Battleford AP
Prince Albert AP
Regina AP
Saskatoon AP (S)
Swift Current AP (S)
Yorkton AP
YUKON TERRITORY
Whitehorse AP (S)
46 26' N 63 50' W
48
48
45
45
45
45
45
46
48
45
45
50
46
45
46
46
48
45
20' N
25' N
53' N
23' N
26' N
35' N
28' N
48' N
27' N
18' N
48' N
13' N
34' N
24' N
4' N
21' N
3' N
16' N
49
50
52
53
50
52
50
51
4' N
20' N
46' N
13' N
26' N
10' N
17' N
16' N
71
71
72
72
75
70
73
71
68
73
74
66
72
71
71
72
77
74
0' W
5' W
29' W
42' W
44' W
52' W
45' W
23' W
32' W
16' W
1' W
16' W
43' W
54' W
19' W
35' W
47' W
6' W
103
105
108
105
104
106
107
102
0' W
33' W
15' W
41' W
40' W
41' W
41' W
28' W
60 43' N 135 4' W
International
AFGHANISTAN
Kabul
ALGERIA
Algiers
ARGENTINA
Buenos Aires
Cordoba
Tucuman
AUSTRALIA
Adelaide
Alice Springs
Brisbane
Darwin
Melbourne
Perth
Sydney
AUSTRIA
Vienna
34 35' N 69 12' E
36 46' N 30 3' E
34 35' S 58 29' W
31 22' S 64 15' W
26 50' S 65 10' W
34
23
27
12
37
31
33
56'
48'
28'
28'
49'
57'
52'
S
S
S
S
S
S
S
138
133
153
130
144
115
151
35' E
53' E
2' E
51' E
58' E
51' E
12' E
48 15' N 16 22' E
Page 164..........................................................................997-01520-02 Rev. G2
International
AZORES
Lajes (Terceira)
38
BAHAMAS
Nassau 25
BANGLADESH
Chittagong 22
BELGIUM
Brussels 50
BERMUDA
Kindley AFB 33
BOLIVIA
La Paz 16
BRAZIL
Belem 1
Belo Horizonte 19
Brasilia 15
Curitiba 25
Fortaleza 3
Porto Alegre 30
Recife 8
Rio De Janeiro 22
Salvador 13
Sao Paulo 23
BELIZE
Belize 17
BULGARIA
Sofia 42
BURMA
Mandalay 21
Rangoon 16
CAMBODIA
Phnom Penh 11
CHILE
Punta Arenas 53
Santiago 33
Valparaiso 33
CHINA
Chongquing 29
Shanghai 31
COLOMBIA
Baranquilla 10
Bogota 4
Cali 3
Medellin 6
CONGO
Brazzaville 4
CUBA
Guantanamo Bay 19
Havana 23
CZECHOSLOVAKIA
Prague 50
DENMARK
Copenhagen 55
DOMINICAN REPUBLIC
45' N 27 5' W
5' N 77 21' W
21' N 91 50' E
48' N 4 21' E
22' N 64 41' W
30' S 68 9' W
27' S
56' S
52' S
25' S
46' S
2' S
4' S
55' S
0' S
33' S
48
43
47
49
38
51
34
43
38
46
29'
57'
55'
17'
33'
13'
53'
12'
30'
38'
W
W
W
W
W
W
W
W
W
W
31' N 88 11' W
42' N 23 20' E
59' N 96 6' E
47' N 96 9' E
33' N 104 51' E
10' S 70 54' W
27' S 70 42' W
1' S 71 38' W
33' N 106 33' E
12' N 121 26' E
59'
36'
25'
13'
N
N
N
N
74
74
76
75
48' W
5' W
30' W
36' W
15' S 15 15' E
54' N 75 9' W
8' N 82 21' W
5' N 14 25' E
41' N 12 33' E
997-01520-02 Rev. G2.......................................................................... Page 165

Santo Domingo 18
EQUADOR
Guayaquil 2
Quito 0
EGYPT
Cairo 29
EL SALVADOR
San Salvador 13
ETHIOPIA
Addis Ababa 90
Asmara 15
FINLAND
Helsinki 60
FRANCE
Lyon 45
Marseilles 43
Nantes 47
Nice 43
Paris 48
Strasbourg 48
FRENCH GUIANA
Cayenne 4
GERMANY
Berlin (West)
52
Hamburg 53
Hannover 52
Mannheim 49
Munich 48
GHANA
Accra 5
GIBRALTAR
Gibraltar 36
GREECE
Athens 37
Thessaloniki 40
GREENLAND
Narsarssuaq 61
GUATEMALA
Guatemala City 14
GUYANA
Georgetown 6
HAITI
Port Au Prince 18
HONDURAS
Tegucigalpa 14
HONG KONG
Hong Kong 22
HUNGARY
Budapest 47
ICELAND
Reykjavik 64
INDIA
Ahmenabad 23
Bangalore 12
29' N 69 54' W
0' S 79 53' W
13' S 78 32' W
52' N 31 20' E
42' N 89 13' W
2' N 38 45' E
17' N 38 55' E
10' N 24 57' E
42'
18'
15'
42'
49'
35'
N
N
N
N
N
N
4
5
1
7
2
7
47'
23'
34'
16'
29'
46'
E
E
W
E
E
E
56' N 52 27' W
27' N 13
33' N 9
24' N 9
34' N 8
9' N 11
18'
58'
40'
28'
34'
E
E
E
E
E
33' N 0 12' W
9' N 5 22' W
58' N 23 43' E
37' N 22 57' E
11' N 45 25' W
37' N 90 31' W
50' N 58 12' W
33' N 72 20' W
6' N 87 13' W
18' N 114 10' E
31' N 19 2' E
8' N 21 56' E
2' N 72 35' E
57' N 77 37' E
Page 166..........................................................................997-01520-02 Rev. G2
International
Bombay 18
Calcutta 22
Madras 13
Nagpur 21
New Delhi 28
INDONESIA
Djakarta 6
Kupang 10
Makassar 5
Medan 3
Palembang 3
Surabaya 7
IRAN
Abadan 30
Meshed 36
Tehran 35
IRAQ
Baghdad 33
Mosul 36
IRELAND
Dublin 53
Shannon 52
IRIAN BARAT
Manokwari 0
ISRAEL
Jerusalem 31
Tel Aviv 32
ITALY
Milan 45
Naples 40
Rome 41
IVORY COAST
Abidjan 5
JAPAN
Fukuoka 33
Sapporo 43
Tokyo 35
JORDAN
Amman 31
KENYA
Nairobi 1
KOREA
Pyongyang 39
Seoul 37
LEBANON
Beirut 33
LIBERIA
Monrovia 6
LIBYA
Benghazi 32
MADAGASCAR
Tananarive 18
MALAYSIA
Kuala Lumpur 3
54' N
32' N
4' N
9' N
35' N
72
88
80
79
77
11' S 106
10' S 123
8' S 119
35' N 98
0' S 104
13' S 112
49' E
20' E
15' E
7' E
12' E
50'
34'
28'
41'
46'
43'
E
E
E
E
E
E
21' N 48 16' E
17' N 59 36' E
41' N 51 25' E
20' N 44 24' E
19' N 43 9' E
22' N 6 21' W
41' N 8 55' W
52' S 134 5' E
47' N 35 13' E
6' N 34 47' E
27' N 9 17' E
53' N 14 18' E
48' N 12 36' E
19' N 4 1' W
35' N 130 27' E
4' N 141 21' E
41' N 139 46' E
57' N 35 57' E
16' S 36 48' E
2' N 125 41' E
34' N 126 58' E
54' N 35 28' E
18' N 10 48' W
6' N 20 4' E
55' S 47 33' E
7' N 101 42' E
997-01520-02 Rev. G2.......................................................................... Page 167

Penang 5
MARTINIQUE
Fort De France 14
MEXICO
Guadalajara 20
Merida 20
Mexico City 19
Monterrey 25
Vera Cruz 19
MOROCCO
Casablanca 33
NEPAL
Katmandu 27
NETHERLANDS
Amsterdam 52
NEW ZEALAND
Auckland 36
Christchurch 43
Wellington 41
NICARAGUA
Managua 12
NIGERIA
Lagos 6
NORWAY
Bergen 60
Oslo 59
PAKISTAN
Karachi 24
Lahore 31
Peshwar 34
PANAMA
Panama City 8
PAPUA NEW GUINEA
Port Moresby 9
PARAGUAY
Ascuncion 25
PERU
Lima 12
PHILIPPINES
Manila 14
POLAND
Krakow 50
Warsaw 52
PORTUGAL
Lisbon 38
PUERTO RICO
San Juan 18
RUMANIA
Bucharest 44
RUSSIA
Alma Ata 43
Archangel 64
Kaliningrad 54
Krasnoyarsk 56
25' N 100 19' E

37' N 61 5' W
41'
58'
24'
40'
12'
N 103
N 89
N 99
N 100
N 96
20' W
38' W
12' W
18' W
8' W
35' N 7 39' W
42' N 85 12' E
23' N 4 55' E
51' S 174 46' E
32' S 172 37' E
17' S 174 46' E
10' N 86 15' W
27' N 3 24' E
24' N 5 19' E
56' N 10 44' E
48' N 66 59' E
35' N 74 20' E
1' N 71 35' E
58' N 79 33' W
29' S 147 9' E
17' S 57 30' W
5' S 77 3' W
35' N 120 59' E
4' N 19 57' E
13' N 21 2' E
43' N 9 8' W
29' N 66 7' W
25' N 26 6' E
14' N
33' N
43' N
1' N
76
40
20
92
53'
32'
30'
57'
E
E
E
E
Page 168..........................................................................997-01520-02 Rev. G2
International
Kiev 50
Kharkov 50
Kuibyshev 53
Leningrad 59
Minsk 53
Moscow 55
Odessa 46
Petropavlovsk 52
Rostov on Don 47
Sverdlovsk 56
Tashkent 41
Tbilisi 41
Vladivostok 43
Volgograd 48
SAUDI ARABIA
Dhahran 26
Jedda 21
Riyadh 24
SENEGAL
Dakar 14
SINGAPORE
Singapore 1
SOMALIA
Mogadiscio 2
SOUTH AFRICA
Cape Town 33
Johannesburg 26
Pretoria 25
SOUTH YEMEN
Aden 12
SPAIN
Barcelona 41
Madrid 40
Valencia 39
SRI LANKA
Colombo 6
SUDAN
Khartoum 15
SURINAM
Paramaribo 5
SWEDEN
Stockholm 59
SWITZERLAND
Zurich 47
SYRIA
Damascus 33
TAIWAN
Tainan 22
Taipei 25
TANZANIA
Dar es Salaam 6
THAILAND
Bangkok 13
TRINIDAD
27' N 30
0' N 36
11' N 50
56' N 30
54' N 27
46' N 37
29' N 30
53' N 158
13' N 39
49' N 60
20' N 69
43' N 44
7' N 131
42' N 44
30' E
14' E
6' E
16' E
33' E
40' E
44' E
42' E
43' E
38' E
18' E
48' E
55' E
31' E
17' N 50 9' E
28' N 39 10' E
39' N 46 42' E
42' N 17 29' W
18' N 103 50' E
2' N 49 19' E
56' S 18 29' E
11' S 28 3' E
45' S 28 14' E
50' N 45 2' E
24' N 2 9' E
25' N 3 41' W
28' N 0 23' W
54' N 79 52' E
37' N 32 33' E
49' N 55 9' W
21' N 18 4' E
23' N 8 33' E
30' N 36 20' E
57' N 120 12' E
2' N 121 31' E
50' S 39 18' E
44' N 100 30' E
997-01520-02 Rev. G2.......................................................................... Page 169

Port of Spain
TUNISIA
Tunis
TURKEY
Adana
Ankara
Istanbul
Izmir
UNITED KINGDOM
Belfast
Birmingham
Cardiff
Edinburgh
Glasgow
London
URUGUAY
Montevideo
VENEZUELA
Caracas
Maracaibo
VIETNAM
Da Nang
Hanoi
Ho Chi Minh City
(Saigon)
YUGOSLAVIA
Belgrade
ZAIRE
Kinshasa (Leopoldville)
Kisangani (Stanleyville)
10 40' N 61 31' W
36 47' N 10 12' E
36
39
40
38
59'
57'
58'
26'
N
N
N
N
54
52
51
55
55
51
36'
29'
28'
55'
52'
29'
N
N
N
N
N
N
35
32
28
27
5
1
3
3
4
0
18'
53'
50'
10'
E
E
E
E
55' W
56' W
10' W
11' W
17' W
0' W
34 51' S 56 13' W
10 30' N 66 56' W
10 39' N 71 36' W
16 4' N 108 13' E
21 2' N 105 52' E
10 47' N 106 42' E
44 48' N 20 28' E
4 20' S 15 18' E
0 26' S 15 14' E
Page 170..........................................................................997-01520-02 Rev. G2

Login - Default Settings
User Name:admin
Password:symmetricom
Network Ports - default settings

Network Ports - Default Settings
Port IP Version IPv4 Address
LAN1 IPv4
LAN2
LAN3
Link Speed
State
Static - 192.168.0.100 Auto Negotiated Enabled

Disabled
Disabled
SNMP
SNMP - Default Settings
Basic Configuration
sysLocation:unknown
sysName:SyncServer
sysContact:admin@localhost
Read Comunity:symmpublic
Write CVommunity:symmprivate
NTP
NTP - Default Settings
997-01520-02 Rev. G2.......................................................................... Page 171
Associations
The following default associations are configured:
IP Address
Role
Poll Interval Burst MD5 Key
Hardware Clock Server

69.25.96.11
Server Default
69.25.96.12
Server Default
69.25.96.14
Server Default
iburst None
iburst None
iburst None
MD5 Keys
MD5 Keys - Default Settings
None defined
NTP Override Behaviour

NTP Override Behaviour - Default Settings
Configured to Follow Standard NTP Rules
TIMING
TimeZone
Time Zone - Default Settings
Local Time Zone is set to UTC
HardwareClockConfiguration
Hardware Clock Configuration - Default Settings
All installed Clock Sources are Enabled (e.g., on an S250, the installed references are: GPS,
IRIG-B, 1PPS, and 10MHz).
Forced Timing Source is set to Auto
Ignore UTC Corrections from GPS Reference (not present on S250i) Not Selected
Holdover
Holdover - Default Settings
Holdover Configuration Time Error Limit is set to 1 (one) millisecond
Page 172..........................................................................997-01520-02 Rev. G2
REFERENCES
Sysplex
Sysplex - Default Settings
Sysplex Output Configuration
Autostart is set to: No
Parity is set to: Odd
Flywheel Quality Character is set to: X
REFERENCES
GPS
GPS - Default Settings
GPS receiver set to Survey mode
GPS Antenna Cable Delay (nS) set to 0 (zero) nanoseconds
IRIG-B
IRIG-B Default Settings
Input Mode:Auto
Output Mode:IRIG-B with IEEE 1344 extension
Output Type:UTC
Cable Delay:0 (zero) nanoseconds
SYSTEM
System - Default Settings
General
Hostname - SyncServer
Check for software upgrades is Selected
ADMIN
LoginWebpageConfiguration
Login Webpage Configuration - Default settings
997-01520-02 Rev. G2.......................................................................... Page 173
Users
Users - Default Settings
Only the admin login is kept; all new users are deleted and their passwords cleared. The
admin user password is reset to the default value of symmetricom.
Alarms
Alarms - Default Settings
Alarms are configured as shown in the table below:
Alarm Name
Severity Auto
Clear
NTP System Peer Change Alarm

NTP Stratum Change Alarm
NTP Leap Change Alarm
System Network Alarm
System Upgrade Alarm
System Config Change Alarm
Notify
Major
Notify
Notify
Minor
Notify
X
X
X
Send
Trap
X
Write
Log
X
X
X
X
X
X
Send
Email
X
Page 174..........................................................................997-01520-02 Rev. G2
ADMIN
System Health Alarm
System Up/Down Alarm
System Authentication Alarm
Timing No Source Alarm
Timing GPS Source Alarm (not in S250i)
Timing IRIG-B Source Alarm (not in S200)
Timing PPS Source Alarm (not in S200)
Timing 10 MHz Source Alarm (not in S200)
Timing GPS Antenna Short Alarm (not in
S250i)
Timing GPS Antenna Open Alarm (not in
S250i)
Timing Oscillator DAC Range Alarm
Timing Rubidium Lock Alarm (Rb Models
Only)
Timing Oscillator Unlock Alarm
Timing Source Change Alarm
Timing Source Lower Accuracy Input Alarm
Timing PLL Unlock Alarm
Timing Quality 1e-6 Alarm
Timing Leap Event Alarm
LAN1 Link Alarm
LAN2 Link Alarm
LAN3 Link Alarm
System Reset Default Config Alarm
Major
Minor
Notify
Major
Major
Notify
Notify
Notify
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Major
Major
Notify
Notify
Notify
Notify
Notify
Notify
Notify
Notify
Notify
Notify
Notify
Major
Notify
Notify
Major
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
LogsConfig
Logs Config - Default Settings
997-01520-02 Rev. G2.......................................................................... Page 175
SERVICES
Startup
Startup - Default Settings
Daemon
Current State Startup
Web Server On
NTP
On
SNMP
On
SSH
On
Sysplex
On
Time
On
Time-UDP
On
Daytime
On
Daytime-UDP On
Telnet
Off
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Auto
HTTP
HTTP - Default Settings
n
Web Server Configuration Security - Standard (Port 80) Only.
Page 176..........................................................................997-01520-02 Rev. G2
SERVICES
n
Web Server Configuration Protocols SSL 3.0 and TLS 1.0 are checked. SSL 2.0 support, if
present, is removed.
SSH
SSH Security Configuration - Default Settings
n
n
n
n
Protocol - SSH-2 Only

Log Level - INFO
Server Key Bits 768 bits
Key Regeneration 3600 Seconds
Email
SMTP Gateway:smtp.example.com
User1:[email protected]
997-01520-02 Rev. G2.......................................................................... Page 177
Hardware Clock
Glossary
Hardware Clock
Introduction to GPS
Leap Indicator
NTP Daemon
Software Clock
Stratum
Timing Engine
Timing Source
UTC
179
179
180
180
180
181
181
181
181
Hardware Clock
The Hardware Clock manages the Input References:
n
n
n
Gets the time from the highest priority reference that is available.
Applies the UTC offset if the reference is GPS.
Passes the time to the NTP daemon.
The NTP daemon includes a preferred server association for the Hardware Clock that cannot be edited or removed.
Also see:
n
n
n
n
TIMING - HW Clock (on page 42)

NTP - Config
Input References
Timing Engine (on page 181)
Introduction to GPS
The Global Positioning System (GPS) is a worldwide radio-navigation system formed from a
constellation of at least 24 satellites that continuously orbit the earth. These GPS satellites
have several atomic clocks that are precisely synchronized to UTC from the U.S. Naval
Observatory (USNO). Coded signals are broadcast by each of the satellites with the exact
time and position of the satellite. All GPS receivers use an antenna to receive these signals.
Using a GPS receiver optimized for time (rather than position), it is possible to get extremely
precise synchronization with the satellites' atomic clocks.
997-01520-02 Rev. G2.......................................................................... Page 179
Glossary
Leap Indicator
The Leap Indicator (LI) is a two-bit binary number in the NTP packet header that provides
the following information:
n
Advance warning that a leap second adjustment will be made to the UTC timescale at the
end of the current day. Leap seconds are events mandated by the world time authority
(BIPM) in order to synchronize the UTC time scale with the earth's rotation.
Whether the NTP daemon is synchronized to a timing reference. The settings on the
NTP - Prefs (on page 40) page affect LI behavior.
LI Value Meaning
00 0
01 1
No warning.
Leap second insertion: Last minute of the day has 61 seconds.
10 2
11 3
Leap second deletion: Last minute of the day has 59 seconds.

Alarm condition (Not synchronized)
When the SyncServer or NTP daemon is started or restarted, the leap indicator is set to "11",
the alarm condition. This alarm condition makes it possible for NTP clients to recognize that
an NTP server (the SyncServer) is present, but that it has yet to validate its time from its time
sources. Once the SyncServer finds a valid source of time and sets its clock, it sets the leap
indicator to an appropriate value. The NTP Leap Change Alarm on the ADMIN - Alarms page can be
configured to generate an alarm and send notifications each time the leap indicator changes
state.
NTP Daemon
The Network Time Protocol (NTP) Daemon (a.k.a. "ntpd") listens for and responds to
requests from NTP clients. It also sends NTP requests to each of the NTP Associations and
qualifies each one. It synchronizes with the best NTP association and makes that time available to the
See the NTP - Config topics for more information.
Software Clock
The Software Clock time is initialized by the onboard real time clock (RTC) and controlled/adjusted by the NTP daemon (ntpd) when it has a valid peer (e.g., Hardware Clock/SYMM_TE, factory default NTP association, user-configured peer, etc.).
The software clock time is represented on the display
Page 180..........................................................................997-01520-02 Rev. G2
Stratum
Stratum
This is an eight-bit integer that indicates the position of an NTP node within an NTP timing
hierarchy. It is calculated by adding 1 to the stratum of the NTP system peer.
For the SyncServer, the stratum values are defined as follows:
Stratum Definition
0
Hardware Clock when locked.
1
Primary server
2-15
Secondary server
16-255 Unsynchronized, unreachable.
For example, the SyncServer is:

n
n
n
stratum 1 when the Hardware Clock (stratum 0) is synchronized to an input reference, in

holdover mode, or in freerun mode.
stratum 2 through 15 when it is synchronized to a remote NTP server.
stratum 16 when it is unsynchronized, indicating that it is searching for a valid source of
timing information.
The settings on the NTP - Prefs (on page 40) page affect stratum behavior.
Timing Engine
This is an equivalent term for "Hardware Clock". Please see the glossary entry for Hardware
Clock (on page 179).
Timing Source
A Timing Source is a reference source, such as GPS, that is available to the Hardware
Clock. The number and type of Timing Sources available varies by model. See TIMING - HW
Clock, Forced Timing Source for specific examples. See the TIMING - HW Clock (on page
42) topic for more information.
UTC
From Wikipedia: "Coordinated Universal Time (UTC) is a high-precision atomic time standard.
UTC has uniform seconds defined by International Atomic Time (TAI), with leap seconds
announced at irregular intervals to compensate for the earth's slowing rotation and other discrepancies. Leap seconds allow UTC to closely track Universal Time (UT), a time standard
based not on the uniform passage of seconds, but on Earth's angular rotation."
997-01520-02 Rev. G2.......................................................................... Page 181
Glossary
Page 182..........................................................................997-01520-02 Rev. G2
Index
1
10MHz In 92
10MHz Out 92
1PPS In 92
1PPS Out 91
8
86-611xPCB 145
A
Accuracy & Stability 86
Adding NTP Servers to the NTP Associations List 36, 109
Adding Server Associations 113, 117
ADMIN 173
ADMIN - Alarms 57, 75, 108
ADMIN - Logs Config 61
ADMIN - Users 56
ADMIN - Web 20, 55
ADMIN Tab 55
Alarm Descriptions 58-59
Alarms 26, 174
Alarms and Notification 58, 116
Apache Software License 125
B
Backing Up/Restoring Configurations 54, 118
C
Canada 147, 162
CAUTION
DHCP Not Available 112
Lithium Battery 89, 123
VAC Power 99
CE/WEEE/RoHS Conformance 89
Command Line Interface 79, 91, 116
Configuring GPS for Various Conditions 106
Configuring LAN1 54, 111, 122
Configuring SNMP 32, 120
Configuring the Network Ports 112, 117
Configuring the SyncServer 13
997-01520-02 Rev. G2.......................................................................... Page 183
Index
Connecting VAC Power 98

Connecting VDC Power 99
Console RS-232 Port 91
Creating a Backup File 108, 118-119, 122
D
Determining Latitude and Longitude 106, 147
Distance Between Antenna and Receiver 87, 102, 105
E
Email 177
EMC Standards 87
Environmental 88
ETX Module 145
F
Factory Default Settings 53, 171
Factory Default Settings for Alarms 116
Failure Detection and Reporting 89
Frequency Reference - Power-Down / Reboot 42, 45
G
Glossary 179
GNU General Public License 137
GPS 25, 173
GPS Receiver 86
Grounding the SyncServer 98
H
Halting the SyncServer 15, 111
Hardware Clock 179, 181
Hardware Clock Configuration 23, 172
HELP - Contacts 72
HELP - Docs 72
HELP Tab 72
Holdover 172
HTTP 66, 176
I
Installation Guide 97
Installing the GPS Antenna 102
International 147, 164
Introduction to GPS 179
IRIG-B 51, 173
IRIG-B In 93
Page 184..........................................................................997-01520-02 Rev. G2
IRIG-B Out 93
K
Key Features and Benefits 17
Keypad/Display 84
Keypad/Display Interface 13, 73, 84-85
L
Leap Indicator 23, 40, 180
Listing of Memory Devices 145
Logging in to the Web Interface 54, 112
Login 20
Login - default settings 171
Login Webpage Configuration 173
Logs Config 63, 175
LOGS Tab 68
M
Maintainability 88
MC9S12DG256 (U2) 146
MD5 Keys 172
MENU Button 76
Microsemi Customer Assistance 3, 6, 52, 79, 88, 98, 105-106, 115, 125
N
Net-SNMP Software License 143
NETWORK - Ethernet 27, 75, 112
NETWORK - Ping 33
NETWORK - SNMP 31, 70
NETWORK - SNMP Traps 32, 70
Network Ports 95
Network Ports - default settings 23, 171
Network Protocols 95
NETWORK Tab 27
Notices 5
NTP 25, 171
NTP - Assoc 35
NTP - Config 36
NTP - MD5 Keys 39
NTP - Prefs 40, 47, 180-181
NTP - Sysinfo 34
NTP Clients 117
NTP Daemon 180
NTP Override Behaviour 25, 172
NTP Software License 134
NTP Tab 34
997-01520-02 Rev. G2.......................................................................... Page 185
Index
O
Operating in 49-50, 102
P
Passwords 115
Port Bonding 29-30
Product Overview 17, 23
Properties of User Names and Passwords 20, 57, 111, 116, 171, 174
Q
Quick Start Guide 13, 97
R
Rack Mounting 98
Recovering a Password 20, 110
REFERENCES 173
REFERENCES - GPS 50
REFERENCES - IRIG-B 51, 93
REFERENCES Tab 50
Removing the Top Cover 120, 122
Replacing the Battery 122
RESTART button 34, 39
Restoring from a Backup File 119, 122
Restoring the Factory Default Configuration 110, 115, 118-119
S
Safety Considerations 13, 100
Safety Standards 87
Selecting a Site for the Antenna 100, 106
SERVICES 176
SERVICES - Email 67
SERVICES - HTTP 65
SERVICES - SSH 66
SERVICES - Startup 64
SERVICES Tab 64
Shock and Vibration 90
SNMP 171
SNMP MIB 189
Software 125
Software Clock 180
Software Features 18
Specifications 13, 83
SSH 67, 177
Startup 65, 176
STATUS - Alarms 25
Page 186..........................................................................997-01520-02 Rev. G2
STATUS - General 22
STATUS - GPS 23
STATUS - Network 22
STATUS - NTP 25, 59, 74
STATUS - Timing 23
STATUS Button 74
Status LEDs 14, 84
STATUS Tab 22
Steering with a Frequency Reference 42, 44-45
Stratum 15, 40, 46, 84, 181
SyncServer Signal Feature Comparison 17-18, 23, 42-43, 115
Sysplex 173
Sysplex Out 47, 94
SYSTEM 173
SYSTEM - Factory Reset 53, 71
SYSTEM - General 52, 76
SYSTEM - Upgrade 53, 76, 85, 108
SYSTEM Tab 52
T
Tasks 13, 97
TIME Button 42, 73-74
Time Zone 172
TIMING 172
TIMING - Holdover 23, 40, 45, 49
TIMING - HW Clock 42, 109, 179, 181
TIMING - Sysplex 47, 94
TIMING - Time Zone 42, 74
Timing Engine 179, 181
Timing Holdover 85, 104
Timing Source 181
TIMING Tab 42
Transferring Configurations 122
Troubleshooting 14, 84, 115
U
United States 147
Unpacking 97
Upgrading System Software 52-53, 107
USB Ports 85
Users 174
Using GPS 13, 100, 117
Using the 1st Setup Wizard 112
Using the Other Input References 115
UTC 181
V
VAC Power Supply 85
997-01520-02 Rev. G2.......................................................................... Page 187
Index
VCCI Compliance Information 88

VDC Power Supply 85
Verifying the GPS Installation 104
W
WARNING
Grounding 98
VDC Power 99
Web Interface 13, 19
Web Interface Browser Compatibility 96
Web Interface Troubleshooting 116
WIZARDS - 1st Setup 70
WIZARDS - Backup 70, 85, 108
WIZARDS - NTP 70
WIZARDS - Restore 71, 85
WIZARDS - SNMP 70
WIZARDS - Upgrade 71, 85
WIZARDS Tab 70
Page 188..........................................................................997-01520-02 Rev. G2
Appendix A: SNMP MIB

The following text comes from the SyncServer's Custom MIB, symm-smi.txt, located on the
Product Information CD:
See next page.
997-01520-02 Rev. G2.......................................................................... Page 189

SyncServer-S2xx User Guide

Uploaded by

Copyright:

Available Formats

SyncServer-S2xx User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SyncServer-S2xx User Guide

Uploaded by

Copyright:

Available Formats

..........

SyncServer S200, S250, S250i

..................Rev. G2, May 2015

..................Part Number: 997-01520-01

..................CD Number: 998-01520-01

Microsemi Customer Assistance

Worldwide Main Number: 1-408-428-7907

Limited Product Warranty

Quick Start Guide

Configuring the SyncServer

Key Features and Benefits

TIMING - Time Zone

Command Line Interface

Upgrading System Software

Using the Other Input References

Apache Software License

Listing of Memory Devices

Determining Latitude and Longitude

Factory Default Settings

Login - default settings

Appendix A: SNMP MIB

Configuring the SyncServer

Quick Start Guide

Web Interface (on page 19)

Configuring the SyncServer

997-01520-02 Rev. G2.......................................................................... Page 13

Quick Start Guide

Network Link failure on the

Link failure on the

SyncServer is synchronized to an Input

All configured ports

Page 14..........................................................................997-01520-02 Rev. G2

Halting the SyncServer

Halting the SyncServer

Press the MENU button.

Or, using the web interface:

997-01520-02 Rev. G2.......................................................................... Page 15

Key Features and Benefits

Key Features and Benefits

Ultra High-Bandwidth NTP Time Server

Synchronize Hundreds of Thousands of Client, Server & Workstation Clocks

997-01520-02 Rev. G2.......................................................................... Page 17

Multiple NTP Ports for Easy Network Configuration and Adaptation

Copy a SyncServer configuration to multiple units.

Encrypted username password.

SyncServer Signal Feature Comparison

Page 18..........................................................................997-01520-02 Rev. G2

997-01520-02 Rev. G2.......................................................................... Page 19

Log in to the SyncServer's web interface.

The Login page includes the following elements:

Username: Enter the username here. (Factory default: "admin")

Also see Recovering a Password (on page 110)

Upper case letters {A-Z}

Usernames may NOT contain any of the following:

Page 20..........................................................................997-01520-02 Rev. G2

Standard ASCII keyboard characters not described above, i.e. ! @ # $% ^ & * () = {} [] |

Upper case letters {A-Z}

Passwords may NOT be all-lowercase, all-uppercase, all-numeric, or match the username.

Single-quote / apostrophe {'}

997-01520-02 Rev. G2.......................................................................... Page 21