This section describes the format, layout, and purpose of this guide.
In This Preface
Purpose of This Guide
Who Should Read This Guide
Structure of This Guide
Conventions Used in This Guide
Warnings, Cautions, Recommendations, and Notes
Related Documents and Information
Where to Find Answers to Product and Document Questions
The SyncServer S6x0 User’s Guide describes the procedures for unpacking,
installing, using, maintaining, and troubleshooting the Microsemi SyncServer S6x0.
It also includes appendixes that describe alarms and events, the languages that you
use to communicate with the SyncServer S6x0, default values, and other
information.
Who Should Read This Guide
Chapter 1, Overview, is written for non-technical audiences who need general
information about the product. Chapters 2 through 5 contain detailed information
and instructions about the product. Other chapters and appendixes describe
installation, maintenance, and configuration instructions or details primarily intended
for qualified maintenance personnel.
This User’s Guide is designed for the following categories of users:
Systems Engineers – Chapter 1 provides an introduction to the SyncServer
S6x0. Cross-references in this chapter direct you to detailed system information
in other chapters as appropriate.
Installation Engineers – Chapter 2 through Chapter 7 and the appendixes
provide detailed information and procedures to ensure proper installation,
operation, configuration, and testing of the SyncServer S6x0.
Maintenance Engineers – Chapter 7 and the appendicesprovide preventive
and corrective maintenance guidelines, as well as procedures for diagnosing and
troubleshooting fault indications and alarms.
Structure of This Guide
This guide contains the following sections and appendixes:
Chapter, TitleDescription
Chapter 1, OverviewProvides an overview of the product, describes the major
hardware and software features, and lists the system
specifications.
Chapter 2, InstallingContains procedures for unpacking and installing the system, and
for powering up the unit.
Chapter 3, Keypad / Display
Interface
Chapter 4, Web InterfaceDescribes the Web Interface.
Describes the CLI command conventions, functions, and features.
Interface (CLI)
Chapter 6, ProvisioningDescribes the commands and procedures required to provision the
SyncServer S6x0 after installing the unit.
Chapter 7, Maintenance,
Troubleshooting & Part Numbers
Contains preventive and corrective maintenance, and
troubleshooting procedures for the product. Also contains part
number and ordering information and procedures for returning the
SyncServer S6x0.
Appendix A, System MessagesLists the alarms and events and provides basic indications of the
source of the alarm.
Appendix B, Specifications and
Factory Defaults
Appendix C, Installing GNSS
Antennas
Lists the specifications and factory defaults for the SyncServer
S6x0.
Provides details about GNSS Antenna kits and procedures for
installing the GNSS antenna.
Appendix D, Software LicensesContains licensing information for third party software.
Appendix E, IP Port DetailsProvides details about Ethernet, Management, and Timing ports.
How to Use This Guide
Conventions Used in This Guide
Conventions Used in This Guide
This guide uses the following conventions:
Acronyms and Abbreviations – Terms are spelled out the first time they appear
in text. Thereafter, only the acronym or abbreviation is used.
Revision Control – The title page lists the printing date and versions of the
product this guide describes.
Typographical Conventions – This guide uses the typographical conventions
described in the table below.
When text appears
this way...
SyncServer S6x0 User’s
The title of a document.
... it means:
Guide
CRITICALAn operating mode, alarm state, status, or chassis label.
Select File, Open...Click the Open option on the File menu.
Press Enter
Press;
A named keyboard key.
The key name is shown as it appears on the keyboard.
An explanation of the key’s acronym or function
immediately follows the first reference to the key, if
required.
Username:Text in a source file or a system prompt or other text that
appears on a screen.
ping
status
A command you enter at a system prompt or text you
enter in response to a program prompt. You must enter
commands for case-sensitive operating systems exactly
as shown.
Warnings, Cautions, Recommendations, and Notes attract attention to essential or
critical information in this guide. The types of information included in each are
explained in the following examples.
Warning: To avoid serious personal injury or death, do not disregard
warnings. All warnings use this symbol. Warnings are installation,
operation, or maintenance procedures, practices, or statements, that
if not strictly observed, may result in serious personal injury or even
death.
Caution: To avoid personal injury, do not disregard cautions. All
cautions use this symbol. Cautions are installation, operation, or
maintenance procedures, practices, conditions, or statements, that if
not strictly observed, may result in damage to, or destruction of, the
equipment. Cautions are also used to indicate a long-term health
hazard.
ESD Caution: To avoid personal injury and electrostatic discharge
(ESD) damage to equipment, do not disregard ESD cautions. All ESD
cautions use this symbol. ESD cautions are installation, operation, or
maintenance procedures, practices, conditions, or statements that if
not strictly observed, may result in possible personal injury,
electrostatic discharge damage to, or destruction of, static-sensitive
components of the equipment.
Electrical Shock Caution: To avoid electrical shock and possible
personal injury, do not disregard electrical shock cautions. All
electrical shock cautions use this symbol. Electrical shock cautions
are practices, procedures, or statements, that if not strictly observed,
may result in possible personal injury, electrical shock damage to, or
destruction of components of the equipment.
Recommendation: All recommendations use this symbol.
Recommendations indicate manufacturer-tested methods or known
functionality. Recommendations contain installation, operation, or
maintenance procedures, practices, conditions, or statements, that
provide important information for optimum performance results.
Note: All notes use this symbol. Notes contain installation, operation,
or maintenance procedures, practices, conditions, or statements, that
alert you to important information, which may make your task easier
or increase your understanding.
How to Use This Guide
Where to Find Answers to Product and Document Questions
Where to Find Answers to Product and Document
Questions
For additional information about the products described in this guide, please contact
your Microsemi representative or your local sales office. You can also contact us on
the web at www.microsemi.com/ftdsupport.
When this manual is updated the updated version will be available for downloading
from Microsemi’s internet web site. Manuals are provided in PDF format for ease of
use. After downloading, you can view the manual on a computer or print it using
Adobe Acrobat Reader.
Manual updates are available at:
www.microsemi.com/ftdsupport
What’s New In This Guide
The following corrections and additions have been made to the SyncServer S6x0
User’s Guide with Rev. D1:
Added section with 10 GbE Input/Output Connections to Chapter 1.
Added Table 2-3 with recommended and supported SFP+ (10 GbE)
Transceivers.
Added details about Dynamic Position Mode to References - Reference GNSS
Modern networks require accurate, secure and reliable time services as provided by
the Microsemi SyncServer S600. The security hardened S600 network time server
is purpose built to deliver exact hardware-based NTP time stamps. The unparalleled
accuracy and security is rounded out with outstanding ease-of-use features for
reliable network time services ready to meet the needs of your network and
business operations today and tomorrow.
SyncServer S650
The modular Microsemi SyncServer S650 combines the best of time and frequency
instrumentation with unique flexibility and powerful network/security based features.
The base Timing I/O module with 8 BNC connectors comes standard with the most
popular timing I/O signals (IRIG B, 10MHz, 1PPS, etc.). When more flexibility is
required, the unique Microsemi FlexPort™ Technology option enables 6 of the
BNCs to output any supported signal (time codes, sine waves, programmable rates,
etc.) all configurable in real time via the secure web interface. This incredibly flexible
BNC by BNC configuration makes very efficient and cost effective use of the 1U
space available. Similar functionality is applied to the two input BNCs as well. Unlike
legacy modules with fixed count BNCs outputting fixed signal types per module,
with FlexPort™ Technology you can have up to 12 BNCs output any combination of
supported signal types.
This level of timing signal flexibility is unprecedented and can even eliminate the
need for additional signal distribution chassis and there is no degradation in the
precise quality of the coherent signals.
SyncServer S650i
The Microsemi SyncServer S650i is a S650 base chassis with no GNSS receiver.
The S650i also includes a single installed Timing I/O module. All software upgrade
options are applicable except GLONASS/BEIDOU/SBAS.
SyncServer S6x0 Key Features
<15ns RMS to UTC(USNO) for S650
1 x 10
Modular timing architecture with unique and innovative FlexPort™ technology
Most popular timing signal inputs/outputs are standard in the base Timing I/O
Overview
module (IRIG B, 10MHz, 1PPS, etc.) available for the S650.
Four (4) GbE ports standard, all with NTP hardware time stamping
Ultra high-bandwidth NTP time server
Stratum 1 Operation via GNSS satellites
DoS detection/protection (optional)
Web-based management with high security cipher suite
TACACS+, RADIUS, LDAP, and more (optional)
-20C to +65C operating temperature (Standard and OCXO)
IPv6/ IPv4 on all ports
Rubidium Atomic clock or OCXO oscillator upgrades
Dual power supply option
PTP and GLONASS/Beidou/SBAS (optional)
Dual 10G Ethernet module option
Low Phase Noise (LPN) module option
Ultra Low Phase Noise (ULPN) module option
Dual DC power supply option
Software Options
The SyncServer S600/S650 includes built-in hardware features enabled via
software license keys.
Security Protocol License Option: The SyncServer S600/S650 can be seriously
hardened from both an NTP perspective and an authentication perspective via
this option. This license option includes:
– NTP Reflector - high capacity and accuracy
– Per port packet monitoring and limiting
FlexPort Timing License Option: The FlexPort™ Technology option enables the 6
output BNCs (J3-J8) to output any supported signal (time codes, sine waves,
programmable rates, and so on.) all configurable in real time through the secure
web interface. The 2 input BNCs (J1-J2) can support a wide variety of input
signal types.
GNSS License Option: This option enables the SyncServer S600/S650 to use
1PPS TI Measurement License:: This license enable 1PPS measurements to be
made on the J1 port of a timing card.
See SyncServer S6x0 Part Numbers, on page 241 for all available options.
Activation keys are associated with the serial number of the device on which the
keys are stored and travel with that device. The user must enter key(s) with web
interface via LAN1 port to gain access to the licensed software options web page.
Security Features
Security is an inherent part of the SyncServer S600/S650 architecture. In addition to
standard security features related to the hardening of the web interface, NTP and
server access, unsecure access protocols are deliberately omitted from the S6x0
while remaining services can be disabled. Advanced authentication services such
as TACACS+, RADIUS, and LDAP are optionally available.
The four (4) standard GbE ports, and optional two (2) 10GbE ports, combined easily
handle more than 10,000 NTP requests per second using hardware time stamping
and compensation (360,000 is max capacity for NTP reflector, 13,000 is max
capacity for NTPd). All traffic to the S6x0 CPU is bandwidth limited for protection
against DoS (denial of service) attacks.
Physical Description
The SyncServer S6x0 consists of a 19-inch (48 cm) rack-mountable chassis, plug-in
modules (S650 only), and hardware.
All connections for the SyncServer S6x0 are on the rear panel. Figure 1-1 is a front
view of the SyncServer S600 version showing LEDs, display screen, navigation
buttons and entry buttons. Figure 1-2 and Figure 1-3 show the rear panel
connections for the Single AC versions of the SyncServer S600. Figure 1-4 and
Figure 1-5 show the rear panel connections for the Dual AC versions of the
SyncServer S600. Figure 1-6 and Figure 1-7 shows the rear panel connections for
the Dual DC versions of the SyncServer S600.
Figure 1-8 is a front view of the SyncServer S650 version showing LEDs, display
screen, navigation buttons and entry buttons. Figure 1-9 and Figure 1-10 show the
rear panel connections for the Single AC versions of the SyncServer S600. Figure
1-11 and Figure 1-12 show the rear panel connections for the Dual AC versions of
the SyncServer S600. Figure 1-13 and Figure 1-14 show the rear panel connections
for the Dual AC versions of the SyncServer S600.
Figure 1-15 is a front view of the SyncServer S650 version showing LEDs, display
screen, navigation buttons and entry buttons. Figure 1-16 shows the rear panel
connections for the Single AC version of the SyncServer S600. Figure 1-17 shows
the rear panel connections for the Dual AC version of the SyncServer S600.
Figure 1-16. SyncServer S650i Rear Panel - Single AC Version
Figure 1-17. SyncServer S650i Rear Panel - Dual AC Version
Chapter 1 Overview
Physical Description
Communications Connections
The SyncServer S6x0 is primarily controlled through the web interface available on
LAN 1. Limited functionality is available via the console serial port.
Ethernet Management Port - LAN1
Ethernet port 1 is the management port that is used to access the web interface.
This port is located on the rear panel of the SyncServer S6x0 and is a standard
100/1000 Base-T shielded RJ-45 receptacle. To connect the SyncServer S6x0 to an
Ethernet network, use a standard twisted-pair Ethernet RJ-45 cable (CAT5
minimum). Configurable to 100_Full or 1000_Full or Auto :100_Full / 1000_Full.
Serial Console Port
The serial port connection is made through a DB-9 female connector on the rear
panel of the SyncServer S6x0. This port, which supports a baud rate of 115.2k
(115200-8-N-1), allows you to connect to a terminal or computer using a terminal
emulation software package. When connecting to this port, use a shielded serial
direct connect cable.
This port is also used for serial data (NENA ASCII time code, Response mode).
Figure 1-18 shows the DB-9 female connector for the serial port.
The SyncServer S6x0 features a BNC connector for input from GNSS navigation
satellites to provide a frequency and time reference. This port also provides 9.7V
tothe power a Microsemi GNSS antenna (see Antenna Kits Overview in Appendix
C, Installing GNSS Antennas). See Figure 1-19. This connector is not present on
the SyncServer S650i.
Figure 1-19. GNSS Input Connection
NTP Input/Output Connections
The S600 / S650 has four dedicated and software isolated GbE Ethernet ports,
each equipped with NTP hardware time stamping. These are connected to a very
high-speed microprocessor and an accurate clock to assure high bandwidth NTP
performance. See Figure 1-20. See Appendix E, IP Port Details for information on
Ethernet port isolation and management port rules.
Figure 1-20. NTP Input/Output Connections
10 GbE Input/Output Connections
The S600 / S650 10 GbE option adds two SFP+ ports equipped with hardware
timestamping that supports NTP, PTP, and NTP Reflector operations. The 10 GbE
ports are in addition to the standard four 1 GbE ports for a total of 6 ports. These
ports are ideal for interoperability with 10 GbE switches. SFP modules supported
are limited to 10 GbE speeds only, and overall system time stamping capacity
remains as specified.
The serial data/timing port connection is made through a DB-9 female connector on
the rear panel of the SyncServer S6x0, as shown in Figure 1-22. When connecting
to this port, use a shielded serial direct connect cable.
The dedicated Data/Timing port is provided to output NMEA-0183 or NENA PSAP
strings. If NENA is selected, the serial Console port also supports the two-way
timing aspects of the standard. In addition, the F8 and F9 Microsemi legacy time
strings are available.
With the optional time interval measurement option, this port can alternatively be
used to send timestamps and measurements.
Figure 1-22. Serial Data/Timing Connection
1PPS Output Connection
The SyncServer S6x0 provides a BNC female connector (Figure 1-23):
The SyncServer S6x0 features a Phoenix connector for an alarm relay output. See
Figure 1-24. The relay is open when the configured alarm classes (Figure 1-25)
occur. If the SyncServer S6x0 is not powered, then the alarm relay will be open. The
relay is energized (shorted), when the SyncServer S6x0 is powered and no
configured alarms are active.
Figure 1-24. Alarm Relay Connector
Figure 1-25. Alarm Relay Configuration Web GUI
Note: The alarm relay is shorted when the alarm is active for
firmware releases 1.0 and 1.1.
Timing I/O Card Connections
The Timing I/O Module is an exceedingly versatile time and frequency input and
output option. In the standard configuration, it supports the most popular input and
output time codes, sine waves, and rates.
The standard configuration offers a broad yet fixed selection of signal I/O on its eight
BNC connectors (see Figure 1-26). J1 is dedicated to time code and rate inputs, J2
to sine wave inputs, and J3-J8 to mixed signal outputs. The standard Timing I/O
Module configuration is 1PPS or IRIG B AM-In, 10 MHz- In, IRIG AM and IRIG
DCLS-Out, 1PPS-Out and 10 MHz-Out.
The FlexPort™ Technology option enables the 6 output BNCs (J3-J8) to output any
supported signal (time codes, sine waves, programmable rates, etc.), all
configurable in real time via the secure web interface. Similarly, the 2 input BNCs
(J1-J2) can support a wide variety of input signal types. This uniquely flexible BNC
by BNC configuration makes very efficient and cost effective use of the 1U space
available.
The SyncServer S6x0 is available with either single or dual 120/240 VAC power, or
dual DC power. The SyncServer S6x0 is not equipped with a Power switch. AC
power is controlled by the unplugging the AC power cord. Frame ground
connections on the SyncServer S6x0 are made on the grounding stud located on
the left side of the rear panel, as identified with the international Ground marking, as
shown in Figure 1-30 and Figure 1-31.
Warning: To avoid serious personal injury or death, exercise caution
when working near high voltage lines and follow local building
electrical codes for grounding the chassis.
The SyncServer S6x0 provides three LEDs on the front panel, as shown in Figure
1-33, that indicate the following:
Sync Status
Network Status
Alarm Status
Figure 1-33. LEDs for SyncServer S3x0
See Figure 2-6 for details about the LEDs.
Communication Ports
Communication ports on the SyncServer S6x0 allow you to provision, monitor, and
troubleshoot the chassis with CLI commands.
Management Ethernet Port
The system web interface for full control is located on Ethernet port 1 (LAN1) and is
used as the Management Ethernet connector to provide connectivity to an Ethernet
local area network. The front panel can be used to configure an IPv4 address (static
or DHCP) or enable DHCP for IPv6. Once the IP address is set and a connection is
made to a Local Area Network (LAN), you can access the SyncServer S6x0 web
interface.
Local Console Serial Port
The serial port supports very limited local control; you can configure the SyncServer
S6x0 with CLI commands using a terminal or computer with terminal emulation
software. The connector is located on the front panel. The Local port is configured
as a DCE interface and the default settings are as follows:
The SyncServer S6x0 can use GNSS, NTP, and IRIG as external input references
(depending on model and configuration). The NTP signals use the RJ45 (1 - 4)
connectors on the rear panel. The GNSS reference uses a BNC connector on the
rear panel. The IRIG signal uses a BNC connector (J1) on the optional Timing I/O
module on the rear panel, as described in Table 1-1.
Frequency Inputs
The SyncServer S6x0 can use either 1PPS, 10 MPPS, 10 MHz, 5 MHz, or 1 MHz as
external frequency input references. The 1PPS/10 MPPS use the J1 BNC and the
10 / 5 / 1 MHz signals use a BNC connector (J2) on the Timing I/O module on the
rear panel, as described in Table 1-1.
Frequency and Timing Outputs
The SyncServer S6x0 can provide NTP,10 / 5 / 1 MHz, 1PPS, IRIG, or TOD output
signals. The NTP signals use the RJ45 (1 - 4) connectors on the rear panel. The
serial TOD output connects to a DB9 connector (DATA/SERIAL) on the rear panel.
The IRIG, PPS, 10 MPPS, and 10 / 5 / 1 MHz signals use BNC connectors (J3 - J8)
on the Timing I/O module on the rear panel. A 1PPS output is also available using a
BNC connector (1PPS) on the rear panel.
Note: The SyncServer S6x0 uses IRIG 1344 version
C37.118.1a-2014.
On the input side, the code performs a subtraction using control
bits 14 - 19 from the supplied IRIG time with the expectation that
this will produce UTC time. This aligns with the C37.118.1a-2014
definition.
On the output side, control bits 14 - 19 will always be zero, and
the encoded IRIG time will be UTC (if using an input 1344 IRIG
as the reference the 2014 rules are applied to get that value).
Hence, any code receiving S6x0 IRIG 1344 output should work
regardless of which version they are decoding (since there is
nothing to add or subtract).
Configuration Management
The SyncServer S6x0 can be configured using the keypad interface, web interface
or Command Line Interface.
Keypad/Display Interface
The keypad/display interface displays the time, system status, and provides the
following functions:
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
Web Interface
The SyncServer S6x0 also allows the user to access information via the LAN1
Ethernet port using HTTPS protocol. To use the SyncServer S6x0 web interface,
enter the IP address for Ethernet port 1 into a web browser. Enter your user name
and password for the SyncServer S6x0 when prompted.
Dashboard View
See Figure 1-34 for an example of the dashboard status screen that will appear.
The Command Line Interface can be used to control specific function of the
SyncServer S6x0 from a terminal connected to the EIA-232 serial port or the
Ethernet LAN1 port. Refer to Chapter 5, Command Line Interface (CLI) for further
details.
Alarms
The SyncServer S6x0 uses alarms to notify you when certain conditions are
deteriorating below specified levels or when issues arise, such as loss of power ,
loss of connectivity, or excess traffic on a port. These alarms are indicated by LEDs,
WebGUI status, CLI status, alarm connector (configurable), SNMP Trap
(configurable), message log (configurable), and email (configurable). For more
information, see Provisioning Alarms, on page 226 and Appendix A, System
Messages.
Note: Before you can communicate with the SyncServer S6x0
through an Ethernet connection, you must first configure the Ethernet
port using the serial connection or front panel (see
Before you begin to install the SyncServer S6x0, review the information in this
section.
If you encounter any difficulties during the installation process, contact Microsemi
Frequency and Time Division (FTD) Services and Support. See Contacting
Technical Support, on page 248 for telephone numbers. Contact Microsemi FTD
Services and Support for technical information. Contact Customer Service for
information about your order, RMAs, and other information.
Security Considerations for SyncServer S6x0 Installation
The SyncServer S6x0 should be installed in a physically secure and restricted
location.
Whenever possible, the SyncServer S6x0's Ethernet ports should be installed
behind the company's firewall to prevent public access.
Site Survey
The SyncServer S6x0 can be installed in a wide variety of locations.
Before you begin installation, determine the chassis location, ensure the
appropriate power source is available (120/240 VAC), and ensure that the
equipment rack is properly grounded.
The SyncServer S6x0 is designed to mount in a 19-inch (48 cm) rack, occupies 1.75
in (4.5 cm, 1 RU) of vertical rack space, and has a depth of 15” (38.1 cm).
The SyncServer S6x0 is to be installed into a rack. The AC power connection is to
be made to a 120 or 240 VAC power receptacle following local codes and
requirements. An external Surge Protective Device is required to be used with the
AC version of the SyncServer S6x0.
Environmental Requirements
To prevent the unit from malfunctioning or interfering with other equipment, install
and operate the unit according to the following guidelines:
Operating temperature: –40Fto 149F (–20 C to 65C) for SyncServer S6x0
with quartz oscillator (standard or OCXO); 23Fto 131F (–5 C to 55C) for
SyncServer S6x0 with Rubidium oscillator.
Operating Humidity: 5% to 95% RH, maximum, w/condensation
Secure all cable screws to their corresponding connectors.
Caution: To avoid interference, you must consider the
electromagnetic compatibility (EMC) of nearby equipment when you
install the SyncServer S6x0.
Electromagnetic interference can adversely affect the operation of
nearby equipment.
Installation Tools and Equipment
You will need the following tools and equipment to install the SyncServer S6x0:
Standard tool kit
Cable ties, waxed string, or acceptable cable clamps
1 mm² / 16 AWG wire to connect grounding lug to permanent earth ground
One UL listed Ring Lugs for grounding connections
Crimping tool to crimp the ring lug
Shielded cabling of the appropriate impedance required by the specific signal
type for signal wiring (including GNSS)
Mating connectors for terminating signal wiring
ESD wrist strap for installing modules
Fasteners for mounting the equipment in rack
Digital multimeter or standard Voltmeter for verifying ground connections to the
chassis
Unpacking the Unit
The SyncServer S6x0 is packaged to protect them from normal shock, vibration and
handling damage. (Each unit is packaged separately.)
Caution: To avoid ESD damage to parts that are packaged with the
SyncServer S6x0, observe the following procedures.
Unpack and inspect the unit as follows:
1. Wear a properly grounded protective wrist strap or other ESD device.
2. Inspect the container for signs of damage. If the container appears to be
damaged, notify both the carrier and your Microsemi distributor. Retain the
shipping container and packing material for the carrier to inspect.
Chapter 2 Installing
Rack Mounting the SyncServer S6x0
3. Open the container, being careful to cut only the packaging tape.
4. Locate and set aside the printed information and paperwork that is included in
the container.
5. Remove the unit from the container and place it on an anti-static surface.
6. Locate and set aside small parts which may be packed in the container.
7. Remove the accessories from the container.
8. Remove the anti-static packaging from the unit and accessories.
9. Verify that the model and item number shown on the shipping list agrees with the
model and item number on the equipment. The item number can be found on a
label affixed to the top of the unit. See Figure 2-1 for the location of the label on
the SyncServer S6x0. Contact your Microsemi distributor if the model or item
number do not match.
For a complete listing of item numbers, see Table 7-4, Table 7-5 and Table 7-6.
Figure 2-1. SyncServer S6x0 - Location of Product Label
Rack Mounting the SyncServer S6x0
The installation procedure described in this section provides general guidelines for
installing the SyncServer S6x0. Always follow applicable local electrical standards.
SyncServer S6x0 is shipped with 19-inch rack mounting brackets attached.
Mount the chassis to the front of the equipment rack rails with four screws and
associated hardware, as shown in Table 2-3. Use the proper screws for the
equipment rack.
Chapter 2 Installing
Making Ground and Power Connections
Making Ground and Power Connections
The SyncServer S6x0 has either one or two 120/240 VAC connectors, depending
on the specific model, which are located on the left side of the rear panel. (see
Figure 2-4 and Figure 2-5).
Ground Connections
The frame ground connection is made using the grounding screw, which is marked
with the universal ground symbol, as shown in Figure 2-6. This screw is located on
the left side of the rear panel for all models of the SyncServer S6x0, as shown in
Figure 2-4 and Figure 2-5.
Figure 2-4. SyncServer S600/S650 Power & Ground Connections - Single AC Version
Figure 2-5. SyncServer S600/S650 Power & Ground Connections - Dual AC Version
Figure 2-6. Universal Ground Symbol
After installing the SyncServer S6x0 into the rack, connect the chassis to the proper
grounding zone or master ground bar per local building codes for grounding.
Run a 16 AWG green/yellow-striped insulated wire from the SyncServer S6x0
grounding lug to the earth Ground on the rack. The rack grounding method is below.
Recommendation: Although there are a number of methods for
connecting the equipment to earth ground, Microsemi recommends
running a cable of the shortest possible length from the ground lug to
earth ground.
1. Remove the grounding screw from the rear panel of the SyncServer S6x0.
2. Crimp the customer-supplied UL listed Ring Lug to one end of the 16 AWG wire.
Coat the lug with an electrically conductive antioxidant compound such as
Kopr-shield spray. Use the grounding screw to connect the ring lug to the left side
of the rear panel. The surface of the SyncServer S6x0 rear panel and threads
where the grounding screw attaches must be clean of contaminants and
oxidation.
3. Connect the other end of the 1 mm² / 16 AWG green/yellow-striped wire to earth
ground using local building electrical codes for grounding
.
The suggested method is to crimp the appropriate customer-supplied UL listed
Ring Lug to the other end of the 1 mm² / 16 AWG green/yellow-striped wire.
Remove the paint and sand the area around the screw hole to ensure the proper
conductivity. Coat the connection with an electrically conductive antioxidant
compound such as Kopr-shield spray. Connect this Ring Lug to the rack with
appropriate customer supplied screws and external star lock washers, tightening
to a torque value of 53.45 in-lbs.
4. Using a digital voltmeter, measure between the ground and chassis and verify
that no voltage exists between them.
Chapter 2 Installing
Making Ground and Power Connections
AC Power Connection
Use the following procedure to make the power connections for the AC version of
the SyncServer S6x0. An Over-Current Protection Device must be placed in front of
the shelf power.
Figure 2-7. SyncServer S6x0 Single AC Power Connector
Figure 2-8. SyncServer S6x0 Dual AC Power Connector
Warning: To avoid possible damage to equipment, you must provide
power source protective fusing as part of the installation. The
SyncServer S6x0 is intended for installation in a restricted-access
location.
1. Insert the female end of the AC power cord into the AC power connector on the
SyncServer S6x0. The power receptacles support IEC cable with V-locks. The
V-lock will latch the cable to prevent accidental removal of the power cord.
2. Plug the male end of the AC power cord into an active 120 VAC or 240 VAC
power socket.
3. For dual AC versions, repeat steps 1-2 for the second AC power connector.
DC Power Connection
Use the following procedure to make the power connections for the DC version of
the SyncServer S6x0. An Over-Current Protection Device must be placed in front of
the shelf power. The SyncServer S6x0 uses a Molex HCS-125 series connector.
Warning: To avoid possible damage to equipment, you must provide
power source protective fusing as part of the installation. The
SyncServer S6x0 is intended for installation in a restricted-access
location.
1. Create a custom cable using the supplied Molex connector housing and
terminals. The terminals need to be crimped to the wires.
2. Connect the other end of the DC cable to nominal 24VDC or 48 VDC.
3. Repeat steps 1-2 for the second DC power connector.
4. The positive wire must be connected to the positive terminal (+) and the negative
wire to the negative terminal (-). The ground connection should only be
connected to ground and not to a power supply.
Figure 2-9. SyncServer S6x0 Dual DC Power Connectors
Signal Connections
The connectors for the SyncServer S6x0 are located on the rear panel.
Communications Connections
The communication connections allow user control of the SyncServer S6x0. The
EIA-232 serial port and Ethernet port 1 (LAN1) are located on the rear panel are
shown in Figure 1-9.
Ethernet port 1 is a standard 100/1000 Base-T shielded RJ-45 receptacle on the
rear panel of the unit. It is used to provide connectivity to a web interface and to an
Ethernet local area network (as well as for NTP input/output). To connect the
SyncServer S6x0 to an Ethernet network, use an Ethernet RJ-45 cable. See Table
2-2 for connector pinouts.
Serial (Console) Port
The serial port connection is made through a DB-9 female connector on the rear
panel of the unit. This port, which supports a baud rate of 115.2k (115200-8-1-N-1),
allows you to connect to a terminal or computer using a terminal emulation software
package for remote monitoring and control. This port is also used for serial data
(NENA ASCII time code, Response mode). When connecting to this port, use a
shielded serial direct connect cable.
Figure 2-10. Serial Port Male Mating Connector Pins
Figure 2-11 shows the DB-9 male connector that mates with the serial port on the
SyncServer S6x0.
Figure 2-11. Serial Port Male Mating Connector Pins
Table 2-1 describes the DB-9 connector pin assignments for the serial port
SyncServer S6x0 Synchronization and Timing Connections
The SyncServer S6x0 has one GNSS input and four NTP input/output connections.
The SyncServer S6x0 has one 1PPS output. The SyncServer S650 may also have
an optional Timing I/O Module.
GNSS Connection
To connect a GNSS signal to the SyncServer S6x0, you must install a GPS
antenna. See Connecting the GNSS Antenna, on page 61.
Caution: The GNSS cable should only be connected while the unit is
properly earth grounded.
Warning: To avoid possible damage to equipment, you must provide
external lightning protection when installing the GNSS antenna to
prevent transients.
Ethernet Connections
The Ethernet ports are standard 100/1000 Base-T shielded RJ-45 receptacles,
which are used for NTP inputs. To connect the SyncServer S6x0 to an Ethernet
network, use an Ethernet RJ-45 cable. See Table 2-2 for connector pinouts.
Table 2-2. System Management Ethernet Connector Pin Assignments
The two SFP+ ports are only available with the 10 GbE option. These SFP+ ports
are equipped with hardware timestamping that supports NTP, PTP, and NTP
Reflector operations. These ports are ideal for interoperability with 10 GbE
switches. SFP modules supported are limited to 10 GbE speeds only, See Table 2-3
for a list or recommended and supported SFP+ transceivers.
Figure 2-13. 10 GbE Connections
Table 2-3. Recommended and Supported SFP+ (10GbE) Transceivers
Table 2-3. Recommended and Supported SFP+ (10GbE) Transceivers
Chapter 2 Installing
Signal Connections
Vendor
Ciscosingle modeSFP-10G-LR
Junipermulti-modeSFPP-10G-SR
Junipersingle modeSFPP-10G-LR
Junipermulti-modeEX-SFP-10G-SR
Junipersingle modeEX-SFP-10G-LR
Mode Item Code or P/N
Timing I/O Module Connections
The standard configuration offers a broad yet fixed selection of signal I/O on its eight
BNC connectors (see Figure 1-26). J1 is dedicated to time code and rate inputs, J2
to sine wave inputs, and J3-J8 to mixed signal outputs. The standard Timing I/O
Module configuration is 1PPS or IRIG B AM-In, 10 MHz- In, IRIG AM and IRIG
DCLS-Out, 1PPS-Out and 10 MHz-Out.
The FlexPort™ Technology option enables the 6 output BNCs (J3-J8) to output any
supported signal (time codes, sine waves, programmable rates, and so on.) on all
configurable in real time via the secure web interface. Similarly, the 2 input BNCs
(J1-J2) can support a wide variety of input signal types. This uniquely flexible BNC
by BNC configuration makes very efficient and cost effective use of the 1U space
available.
See Figure 1-27 to view the signal types for the standard configuration and the
configuration with the FlexPort™ option. See Figure 2-14.
This module provides low phase noise 10 MHz signals on all eight ports (J1-J8).
See Figure 2-15.
Figure 2-15. LPN BNC Connections
Serial Timing Connection
The SyncServer S6x0 features a DB-9 female connector on the rear panel of the
unit. This port supports a baud rate of 4800 to 115.2k (115200-8-1-N-1). When
connecting to this port, use a shielded serial direct connect cable. See Figure 2-16.
See Table 2-4 for pin-outs for this RJ-45 connector.
Figure 2-16. Data/Timing Connection
.
Table 2-4. Serial Data/Timing Port Pin-Outs - DB9 Connector
The SyncServer S6x0 features a single BNC female connector for the 1PPS signal.
See Figure 2-17.
Figure 2-17. 1PPS Output Connection
Connecting the GNSS Antenna
Caution: The GNSS cables should only be connected while the unit
is properly earth grounded.
Connecting the GNSS Antenna
Chapter 2 Installing
The antenna connections for the SyncServer S6x0 are made at the BNC female
connector labeled GNSS. Allow at least one hour for the unit to track and lock to
GNSS satellites, though it typically takes far less time provided the antenna has an
adequate view of the sky.
Note: The SyncServer S650i does not include a GNSS antenna
connector.
Figure 2-18. GNSS Input Connection
Proper cable, grounding techniques, and lightning arrestors should be used. Mount
the antenna outside, preferably on the roof with an unobstructed view of the sky.
Avoid mounting the antenna near a wall or other obstruction blocking part of the sky.
Mount the antenna well above roads or parking lots.
Note: For the best possible timing accuracy the cable delay must be
determined and entered into SyncServer S6x0 with the web interface.
See
Table C-1 for cable delay values of SyncServer S6x0 GNSS
The SyncServer S6x0 is not equipped with a Power switch. After installing the unit
in a rack and making the necessary connections described in previous sections,
turn on power at the distribution panel.
Normal Power Up Indications
As the SyncServer S6x0 powers up and begins normal operation, the LEDs all turn
on. After the self-test is complete and the firmware is operational, the LED states
may change to indicate the appropriate state or status.
Table 2-6 provides a description of the SyncServer S6x0 LEDs.
Table 2-6. LED Descriptions
LabelLEDDescription
Chapter 2 Installing
SYNCClock StatusGreen - Time or Frequency clock in Normal or
Bridging state
Amber - Time or Frequency clock in Freerun or
Holdover state
NETWORKNetwork StatusRed - Management port (LAN1) is not configured
or is down
Amber - Some configured ports are down (LAN2
to LAN4)
Green - All configured ports are up
ALARMAlarm
System alarm/fault indicator
Off -Operating normally
Amber - Minor Alarm(s)
Red - Major/Critical Alarm(s)
The SyncServer 6x0 does not contain a battery-backed real time clock. Therefore, it
will always boot up with a default value for the system time. This time will be
updated when it obtains time from a time reference such as GNSS, IRIG, or NTP.
The default value for the date is the software build date. This date will be used for
the first log entries when booting up the unit. The time will change to local time
during the boot-up process if a time zone has been configured.
This chapter describes the keypad / display interface.
Overview
The keypad / display interface displays the time, system status, and provides the
following functions:
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.
When the SyncServer starts, the display shows "Booting SyncServer please wait...".
Shortly thereafter, the SyncServer displays the default time screen.
The following buttons are user-input devices for the keypad/display interface.
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, will change where the next number will be
entered left or right. In status, scrolls a screen horizontally when
"<previous:next>" is displayed.
Up/Down Arrow Buttons: In functions, will change where the next number will be
entered. In status, scrolls a screen vertically, 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.
TIME: Changes the format and contents of the time display.
STATUS: Displays status of basic SyncServer operational conditions.
MENU: Displays a menu of functions.
The following sections cover these three buttons in more detail.
Cycling the TIME button changes the predefined format and contents of the time
display:
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
Small date and time, reference, and NTP stratum.
The time display also indicates a time scale:
If the time zone setting on the TIMING - Time Zone web 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 display leaves the time scale blank, or adds AM/PM if the user
selects the 12-hour time scale. (Press the MENU button and select 2) Display > 3)
12/24 > 1) 12 (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 -
STATUS Button
Pressing the STATUS button repeatedly displays a series of status screens for:
NTP
Alarms
Network Ports
Clock
GNSS Receiver
SyncServer model, serial number, software version, and software upgrade
availability. If installed, the configuration for each port of the timing/IO module.
Some screens have a "Next>" in the upper right. This means more information is
available by pressing the right arrow button. This cycles through screens on that
topic.
NTP Status Screen
Network Time Protocol (NTP) status.
Stratum: The Stratum number of the SyncServer. Stratum 1 means it is locked to a
Hardware Clock.
Hardware Clock Input Reference that is a Stratum 0 source. Stratum 2-15 means
the SyncServer is locked to another NTP time source. Stratum 16 means that the
SyncServer is unsynchronized.
Reference: 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.
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).
Alarm Status Screen
Current alarm status. Use the right or left arrow to show details about the alarms.
Major: List of up to three current major alarms
Minor: List of up to three current minor alarms
LAN Status Screens
Multiple screens, four for each network port. There are two screen for IPv4 and two
for IPv6. Use Next> to see the entire IP address configuration.
2. On/Off: Use On to enable the LAN1 network port. Off disables the LAN1 network
port for all traffic types.
Figure 3-4. Select LAN1 IP Mode Screen
1. IPv4: Select IPv4address mode for LAN1 port.
If IPv4 is selected, the Select Addressing Type screen will appear, as shown in
Figure 3-5.
2. IPv6: Select IPv6 address mode for LAN1 port.
If IPv6 (DHCPv6) is selected, the SyncServer automatically configures LAN1 with
a dynamic IPv6 address.
Figure 3-5. Select IPv4 Addressing Type Screen
1. Static Addr: Select IPv4address mode for LAN1 port.
If Static Address is selected, the Enter LAN1 Address screen will appear, as
shown in Figure 3-6. After the address is entered press the ENTER button and
you will be prompted to enter the Subnet mask (then ENTER) followed by the
Gateway address. Once the gateway address has been entered the LAN 1 port
will be reconfigured.
2. DHCP: Select DHCP addressing type for LAN1 port. DHCP automatically
configures LAN1 with a dynamic IPv4 address.
Figure 3-6. Enter LAN1 Static IPv4 Address Screen
Display
Selecting Display brings up the Display menu screen on the display, as shown in
1. Set Time: Enter the UTC date and time using 24-hour format. Select OK to apply
the entered time to the Hardware Clock and not use external time references.
See Figure 3-8.
Figure 3-8. Set Time Screen
2. Brightness: Adjust the brightness of the front panel display. See Figure 3-9.
Figure 3-9. Set Brightness Screen
3. 12/24 (non-UTC Only): Select a 12 (AM/PM) or 24-hour clock format. See Figure
3-10.
Note: The 12/24 and 24 Hour only appear if a local time zone has
been specified via the web inteface.
Figure 3-10. Select Time Format Screen
Many keypad functions timeout after approximately 10 seconds of inactivity (no user
inputs).
Sys Control
Selecting Sys Control brings up the Shutdown / Factory Default screen on the
display, as shown in Figure 3-11.
See Factory Defaults in Appendix B for default settings.
1. Shutdown: Halts the SyncServer. The message Press the ENTER button to
Confirm appears in the display, as shown in Figure 3-12.
2. Factory Default
Figure 3-12. Confirmation Screen
Keypad
Selecting Keypad brings up the Keypad Control screen on the display, as shown in
Figure 3-13.
Figure 3-13. Keypad Control Display Screen
1. Set Password: Sets the password for the Lockout function. The *first time* the
interface asks for the "Current Password", enter 95134. No password recover or
reset feature is available for the keypad, except to reset factory defaults using the
Sys Control - Factory Reset page.
2. Lockout: The Lockout function password protects the keypad from changes.
Asks for confirmation. The factory default password for the keypad is “95134”.
This chapter describes the web interface for the SyncServer S6x0.
See Communicating Through LAN1 Ethernet Port, on page 176 for details on how
to access the web interface.
In This Chapter
System Information
Status / Information Windows
Navigation Windows
Note: For security reasons, the SyncServer S6x0 only supports https
However, the user will get warnings from most web browsers that a
self-signed certificate is being used (not from a recognized certificate
authority). Users should accept the warnings and proceed to the login
page.
The internal self-signed certificate can be renewed and updated on
the Security->https page. Users can also request and install a https
certificate
Figure 4-1. Login
For security reasons, the SyncServer S6x0 will lock out a user if an invalid
password is entered three times. The user is locked out for 1 hour. The lockout is
also removed if the unit is rebooted.
Note: The default user name is “admin” and the default password is:
Microsemi .
To avoid unauthorized access, you should change the default
password.
Note: UTC and local time are displayed in the upper right portion of
the page. Local time is based on the timezone setting in the
SyncServer unit. Daylight saving time is also applied to the local time
if applicable. Local time is not determined by the location of the web
browser.
Note: If the browser is displaying a busy indicator, then please wait
until the previous action is complete before starting another action.
Depending on the browser used, the web page responsiveness will
vary due to the use of the encryption cipher suite used in the S6x0.
Microsemi recommends using the Google Chrome browser.
System Information
The System information window in the Dashboard, as shown in Figure 4-3, displays
an overall summary of the system.
The Timing window in the dashboard, as shown in Figure 4-5, displays status
details and information about system timing, including current reference, lock
status, and status of input references. See Table 4-1.
Note: The SyncServer 6x0 does not contain a battery-backed
real time clock. Therefore, it will always boot up with a default
value for the system time. This time will be updated when it
obtains time from a time reference such as GNSS, IRIG, or
NTP. The default value for the date is the software build date.
This date will be used for the first log entries when booting up
the unit. The time will change to local time during the boot-up
process if a time zone has been configured.
Table 4-1. Timing Window Descriptions
ItemDetailsColor Scheme
Status / Information Windows
Chapter 4
Time of Day StatusThis row is essentially showing the
time clock state.
See
Table 4-2 for descriptions of
clock states.
Current ReferenceThis row shows the input reference
that is currently “driving” the
SyncServer. It could be a timing
source (best case), an external
holdover source, or the SyncServer
internal reference (worst case).
See
Table 4-3 for details of current
sources.
Timing ReferencesThis row shows all enabled time
references.
Warmup
Freerun
Handset
Locking
Locked
Bridging
Holdover
Holdover
Recovering
Green if any externally
selected reference,
Amber color only if internal
oscillator.
If a time reference is ready to
be used it will be
Leap PendingThis row indicates if a Leap second is
This row shows all enabled
frequency-only references.
The use of a frequency reference is
thought of as a method for
holding-over time when there either
was never an active time source or it
was lost.
pending.
The SyncServer S600/S650 has separate timing and frequency clock controls. The
time and frequency clocks are usually in the same clock state. If they are different,
then the “Current Reference” row will include text after the icon which displays the
frequency clock state. The “Time of Day Status” always shows the time clock state.
While locking to a new reference, the two states may be different for a brief time.
If a holdover source is ready
to be used it will be
If it is not ready it will be
If there is no warning of a
Leap second pending it will
be
green.
If there is a warning of a Leap
second pending it will be
green.
red.
red.
If there are no valid timing references, but there is a valid frequency reference, then
there should be text shown since the frequency and time clock states are different.
The system time locks, but does not frequency lock to an NTP reference.
Therefore, the frequency status will display free-run while the system is locked to an
NTP reference and there are no frequency references connected.
synchronization functionality. This is a
one-time status following power-up
FreerunSyncServer does not have a time
reference and never has had one since
powerup.
HandsetFor future use.
LockingSyncServer has selected a qualified
active time input for use and is now in
process of aligning all outputs to it.
LockedSyncServer outputs are now aligned to a
selected active time source.
BridgingSyncServer no longer has a selected
active time source, but it hasn’t been that
way for very long.
Directly equal to the common
warmup clock state (to both freq
and time)
In this status, the Current
Source row will, by definition,
have a “green” item that has a
match to it in the Timing
Sources row.
An “active” time source just
means one that is continuously
providing time (where
continuous is a relative term –
in general it is an update per
second).
This is really just the beginning
of holdover, but is a period
where the output performance
should be as good as when in
Locked. It provides a hysteresis
buffer to prevent nuisance
Locked-Holdover-Locked
transitions.
In this state the Current Source
row will NOT have a green item
from the Timing Sources row.
HoldoverSyncServer no longer has a selected
active time source, and it has been that
way for longer than the Bridging
duration. Also the condition for “red
holdover” (next row) is not met.
Either we are holdover using an
external frequency reference
OR we are in holdover using the
SyncServer internal reference
AND the duration is less than a
user-specified time duration.
1
Page 80
Chapter 4
Note:
Status / Information Windows
Table 4-2. Status - Clock State Descriptions (Continued)
Status IndicationMeaningDetails
HoldoverSame as prior row but specific additional
conditions are met.
This condition occurs if the current
source is the internal oscillator and the
duration in time holdover has exceeded
the time defined by user in the Timing >
Holdover window.
The unit has been in holdover
for more than a user-specified
duration and the holdover is
based on the SyncServer
internal reference.
In this case the Holdover
Sources row will not contain any
green items.
RelockingSyncServer has selected a qualified
active time input for use and is now in
process of aligning all outputs to it.
1
The main purpose of holdover is to allow the S6xx time server to continue to operate as "normal" using the
internal oscillator or external frequency reference even though the connection the GNSS is lost. The user
defines how long this holdover period will last. During this time the NTP Reference Time Stamp is updated
regularly indicating the S6xx is still connected to a time reference. Once the user defined holdover period is
exceeded the reference time stamp is no longer updated. This is important information to provide to NTP
clients as they can then determine whether or not to continue to synchronize to the S6xx. Once the S6xx
reacquires GNSS and relocks, the NTP Reference Time Stamp will again be updated regularly.
By NTP protocol definition, once an NTP server locks to a time reference and sets the Leap Indicator to 00
from 11 it never returns to 11. In other words, once the unit has left stratum 16 it should never return to
stratum 16. Instead it uses the reference time stamp behavior mentioned above.
No current sourceWarmupDirectly equal to the common warmup
clock state (to both freq and time)
Current Source taken
from Timing
References
Locking
Locked
Relocking
When the status is any of these there
MUST be a selected time source, which
takes precedence in the Current Reference
row (more important than if there is also a
qualified frequency reference). There must
be at least one green item in the Timing
References row. The leftmost green one
will be identically indicated in the Current
Reference row. This is because the
leftmost green item in Timing References is
the highest priority time source and
therefore must be selected. For example, if
it is GNSS it will appear identically as
Current Reference and in Timing
References row.
Current Source taken
from Frequency
References
Freerun
Bridging
Holdover
Holdover
For any Status in this category there cannot
be a qualified Timing Reference (nothing
green in that row), so it is certain that
SyncServer is using frequency-only
reference. If there is a qualified Frequency
Reference (meaning something green in
this row), then the leftmost green one will
be the current source.
If there is no qualified Frequency
Reference (nothing green in that row) then
all that remains is the SyncServer internal
reference, which is what appears in the
Current Reference row. In this case the
entry will be one of the following,
depending on the specific SyncServer
product oscillator type:
The GNSS window in the dashboard, as shown in Figure 4-6, displays status details
and information about GNSS. C/No is the carrier-to-noise density which is defined
as the carrier power divided by the noise power spectral density. Higher C/No
results in better tracking and performance.
The GNSS signal strength (C/No) can vary from 1 to 63. Typical values for a good
GNSS installation will be between 35 and 55.
The NTP window in the dashboard, as shown in Figure 4-8, displays status details
and information about the NTP configuration.
Figure 4-8. NTP Window
Note: The dashboard will provide Leap indicator information as soon
as it is available. For GPS, this is usually many months ahead.
The Leap indicator information in the NTP messages sent out the
Ethernet port(s) will only be sent out the last 24 hours before the
event for the "01" or "10" values of this parameter. See
more details about the Leap indicator.
Table 4-5 for
Timing Services Information
The Timing Services window in the dashboard, as shown in Figure 4-9, displays
status details and information about the NTP reflector and PTP configuration.
Figure 4-9. Timing Services Window
Timing Services Status
The Timing Services Status window in the dashboard, as shown in Figure 4-10,
displays status details and information for the NTP reflector and PTP.
Note: The row labeled with "Service" is a configuration of the port.
The Timing Services Status window shows this configuration. For
PTP, the actual PTP Grandmaster operational state as either Passive
or Master is found in the window Network Timing > NTPr/PTP Status,
in the row "Port State". See
Note: The update available feature will only function if LAN1 has
been configured with an IPv4 address and a DNS server is
configured. The DNS server can be either automatically configured
via DHCP or manually when using a static IP address. The update
available feature can be disabled on the Admin->General page.
Note: You can check for the latest version number of SyncServer
S600 and S650 software at these URLs:
http://update.microsemi.com/SyncServer_S600
http://update.microsemi.com/SyncServer_S650
The number of the most current version of the software will appear.
You can compare this to the version number installed in the
SyncServer by proceeding to the web GUI Dashboard and finding the
version number in the About drop down on the right side. If you do not
have the latest version installed consider contacting Technical
Support.
Navigation Windows
The navigation portion of the web interface is used to access the various pages to
configure different aspects of the SyncServer S6x0 and to view status information.
See Figure 4-14. The navigation menu will expand and contract depending on the
current selection.
The Network tab on the dashboard provides access to windows for Ethernet, SNMP,
SNMP Trap configuration, and Ping.
Network - Ethernet Configuration
Use this window to configure or modify the Ethernet setting for LAN1 - LAN6, and to
manually set the DNS server address for LAN1. There is a separate "Apply" button
for each Ethernet port and the DNS server address configuration.
The following Ethernet parameters can be configured:
Speed
– Auto | Full 100 | Full 1000
IP format
– IPv4 | IPv6
Config
–Static | Dynamic
– IPv6 Auto Config
IP address
Subnet mask for IPv4, prefix length for IPv6
Gateway address
DNS server addresses can be added for LAN1. This will usually be necessary if
LAN1 is configured with a static IP address.
See Figure 4-15. See Appendix E, IP Port Details for information on Ethernet port
isolation, management port rules, and timing port rules.
Note: Each Ethernet port should be configured on a different subnet.
Note: Some SNMP browsers and trap managers require that an
SNMPv3 user be created with the same username and authentication
as used for the trap configuration in order for the SNMPv3 discovery
process to complete properly.
Note: SNMP is designed to be used with LAN1. Do not configure a
SNMP manager address in a subnet used by the other LAN ports
(LAN2 - LAN6).
Use this window to perform network ping tests. Use ping to test network connectivity
out the LAN ports as needed. The result of the ping will be displayed in the window
when completed. An IPv4 or IPv6 address should be entered in the IP address field.
System PeerThe IP address of the clock source. The source is selected by the NTP daemon
that is most likely to provide the best timing information based on: stratum,
distance, dispersion and confidence interval. The address of the local
SyncServer Hardware Clock can be viewed in the hardware reference clock
section of the NTP associations page.
System Peer
Mode
The relationship of the SyncServer to a system peer, usually a "client".
Depending the configuration, the mode can be:
Client: A host operating in this mode sends periodic messages regardless of
the reachability state or stratum of its peer. By operating in this mode the
host, usually a LAN workstation, announces its willingness to be
synchronized by, but not to synchronize the peer.
Symmetric Active: A host operating in this mode sends periodic messages
regardless of the reachability state or stratum of its peer. By operating in this
mode the host announces its willingness to synchronize and be synchronized
by the peer.
Symmetric Passive: This type of association is ordinarily created upon
arrival of a message from a peer operating in the symmetric active mode and
persists only as long as the peer is reachable and operating at a stratum level
less than or equal to the host; otherwise, the association is dissolved.
However, the association will always persist until at least one message has
been sent in reply. By operating in this mode the host announces its
willingness to synchronize and be synchronized by the peer.
A host operating in client mode (a workstation, for example) occasionally sends
an NTP message to a host operating in server mode (the SyncServer), perhaps
right after rebooting and at periodic intervals thereafter. The server responds by
simply interchanging addresses and ports, filling in the required time information
and returning the message to the client. Servers need retain no state information
between client requests, while clients are free to manage the intervals between
sending NTP messages to suit local conditions.
In the symmetric modes, the client/server distinction (almost) disappears.
Symmetric passive mode is intended for use by time servers operating near the
root nodes (lowest stratum) of the synchronization subnet and with a relatively
large number of peers on an intermittent basis. In this mode the identity of the
peer need not be known in advance, since the association with its state variables
is created only when an NTP message arrives. Furthermore, the state storage
can be reused when the peer becomes unreachable or is operating at a higher
stratum level and thus ineligible as a synchronization source.
Symmetric active mode is intended for use by time servers operating near the
end nodes (highest stratum) of the synchronization subnet. Reliable time service
can usually be maintained with two peers at the next lower stratum level and one
peer at the same stratum level, so the rate of ongoing polls is usually not
significant, even when connectivity is lost and error messages are being returned
for every poll.
Leap IndicatorThe Leap Indicator (LI) is a two-bit binary number in the NTP packet header that
provides the following information:
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.
LI
Meaning
00 No Warning
01 Leap second insertion: Last minute of the day has 61 seconds.
10 Leap second deletion: Last minute of the day has 59 seconds.
11 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.
StratumThis 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
Meaning
0 Hardware Clock when locked
1 Primary server
2-15 Secondary server
16-255 Unsynchronized, unreachable
For example, the SyncServer is:
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.
Log2 PrecisionThis is a signed integer indicating the precision of the selected peer clock, in
seconds to the nearest power of two. A typical value is -18 for a Hardware Clock
where the uppermost 18 bits of the time stamp fractional component have value,
indicating a precision in the microsecond range.
Root DelayThis is a measure of the total round trip delay to the root of the synchronization
tree. A typical value for a SyncServer operating at stratum 1 would be 0 since the
SyncServer is a root of the synchronization tree For other stratum levels, an
appropriate value is displayed. Depending on clock skew and dispersion, this
value could be positive or negative.
Root
Dispersion
This is a signed fixed-point number indicating the maximum error relative to the
primary reference source at the root of the synchronization subnet, in seconds.
Only positive values greater than zero are possible.
Reference IDThis is a four-byte field used to identify the reference clock source. At
initialization, while the stratum is 16, this field shows the progression of the NTP
clock PLL. The field will start with a value of INIT (may be displayed as
73.78.73.84, the ASCII decimal values). Once a peer has been selected, the
clock may be stepped, in which case the reference ID field will change to STEP
(or 83.84.69.80). Once the PLL is locked, the stratum will be updated and the
reference ID will identify the selected peer. In the case of a SyncServer operating
at stratum 1, the reference ID will display the source for the local timing reference
(e.g., GNSS, IRIG, FREE). In the case where the selected peer is another NTP
server, the reference ID will display the IP address of the server or a hash unique
to the association between the SyncServer and the remote server.
Reference
Time
The time when the SyncServer last received an update from the selected peer.
Represented using time stamp format in local time. If the local clock has never
been synchronized, the value is zero. A time stamp of zero corresponds to a local
time of Thu, Feb 7 2036 6:28:16.000. This value is typically updated every 16
seconds for a locally attached hardware reference (e.g., GNSS, IRIG) and in an
interval of 64- 1024 seconds for a readily accessible remote NTP server.
System JitterJitter (also called timing jitter) refers to short-term variations in frequency with
components greater than 10 Hz.
Clock JitterJitter (also called timing jitter) refers to short-term variations in frequency with
components greater than 10 Hz.
Clock Wander
Broadcast
Delay
The broadcast and multicast modes require a special calibration to determine
the network delay between the local and remote servers. Typically, this is done
automatically by the initial protocol exchanges between the client and server.
This is the broadcast or multicast delay reported by the NTP daemon.
Symm Auth
Delay
When NTP authentication is enabled and performed on outgoing NT
P packets,
this adds a trivial amount of fixed delay that can be removed based on the
authdelay value. This value is always set to zero on the SyncServer.
RemoteThe 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:
(space) reject
The peer is discarded as unreachable, synchronized to this server (synch
loop) or outrageous synchronization distance.
x = falsetick
The peer is discarded by the intersection algorithm as a falseticker.
,(period) = excess
The peer is discarded as not among the first ten peers sorted by
synchronization distance and so is probably a poor candidate for further
consideration.
- (minus) = outlier
The peer is discarded by the clustering algorithm as an outlier.
+ (plus) = candidate
The peer is a survivor and a candidate for the combining algorithm.
# (pound sign) = selected
The peer is a survivor, but not among the first six peers sorted by
synchronization distance. If the association is ephemeral, it may be
demobilized to conserve resources.
* (asterisk) = sys.peer
The peer has been declared the system peer and lends its variables to the
system variables.
o = pps.peer
The peer has been declared the system peer and lends its variables to
thesystem variables. However, the actual system synchronization is derived
from a pulse-per-second (PPS) signal, either indirectly via the PPS reference
clock driver or directly via kernel interface.
Ref IdThis is a four-byte field used to identify the reference clock source. At
initialization, while the stratum is 16, this field shows the progression of the NTP
clock PLL. The field will start with a value of INIT (may be displayed as
73.78.73.84, the ASCII decimal values).
Once a peer has been selected, the clock may be stepped, in which case the
reference ID field will change to STEP (or 83.84.69.80). Once the PLL is locked,
the stratum will be updated and the reference ID will identify the selected peer. In
the case of a SyncServer operating at stratum 1, the reference ID will display the
source for the local timing reference (e.g., GNSS, IRIG, FREE). In the case where
the selected peer is another NTP server, the reference ID will display the IP
address of the server or a hash unique to the association between the
SyncServer and the remote server.
StratumThe 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 GNSS. 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).
Chapter 4
ReachThis 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 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.
Offset (ms)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.
Delay (ms)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.
Disp (ms)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.
Poll (s)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.