LEDI - Gorgy timing · MDE-LEDI-NETWORK-TDS-4099V1.0 1 [email protected] LEDI® NETWORK TDS...

MDE-LEDI-NETWORK-TDS-4099V2.0 1

LEDI® NETWORK TDS V1

LEDI® NETWORK TDS GPS RAIL DIN TH35

TIME SERVER USER MANUAL

2 MDE-LEDI-NETWORK-TDS-4099V3.0

WARNING! The following section provides the safety instructions for installation. Please read it carefully before installing your device.

To protect your device, plug it into a grounded outlet.

The device must be connected to an electrical installation which is in accordance with the NF C15-100 standard.

The wiring installation must include an easily accessible breaking device (circuit breaker or disconnecting switch). This device must withstand the nominal voltage and current values indicated on the device.

In Europe: in accordance with European regulations on the protection of individuals and the environment, it is your responsibility to dispose of this equipment at a collection site designed for this purpose (separately from household waste). For further information, contact your reseller, your collection site or the relevant local authorities.

Any modification or opening of the product without the consent from the Customer service department will void the warranty.

The LEDI® NETWORK TDS must only be installed, maintained and handled by competent and knowledgeable persons.

All maintenance operations must be carried out with the power off, including for systems connected to any relay outputs.

As a general rule, to avoid any interferences, the power (230V supply) and signal (time information) cables must not be too close to each other. (keep a few centimetres apart)

CAUTION! After unplugging the LEDI® NETWORK TDS, there is a risk of electric shock from the power connector/plug socket for up to 2 seconds.

To avoid the risk of electrical interference, position the LEDI® NETWORK TDS as far as possible from sources of radiation (Loudspeakers, antennas, high-frequency equipment, electromagnetic alarms…).

Gorgy Timing disclaims all liability in the event of accident or damage caused by improper use of LEDI® NETWORK TDS.

All GORGY TIMING products comply with the following standards: CE, EN60950-1,

EN55022 class B, EN50024.

IMPORTANT SAFETY INSTRUCTIONS


EN

GLIS

H

General hazard – there is a risk of damage to the product if instructions are not followed

Electrical hazard – there is a risk of electrocution or personal injury if instructions are not followed.

Equipment fully protected by double insulation.

Warnings

Please follow the precautions and instructions indicated below in order to ensure the safety of you and your environment, and to prevent any potential damage to your device.

WARNING: An isolating switch in compliance with EN60947 standards is used as a disconnecting device. It must be easily accessible and installed close to the power supply. It must disconnect all active poles.

The LEDI® NETWORK TDS is intended for indoor use only, at an altitude of less than 2000 metres.

Waste disposal by users in private households within the European Union

This symbol on the product or its packaging indicates the product must not be disposed of with your general household waste. Instead, it is your responsibility to dispose of your waste by taking it to a designated collection point for the recycling of electrical and electronic appliances. The separate collection and recycling of your waste contributes to the conservation of natural resources and helps to ensure that recycling is environmentally and health friendly. For more information about your nearest recycling centre, please contact the shop where you purchased your device, the household waste disposal services or your local authorities.

Technical features

TDS v1 TDS GPS Rail Din TH 35

Power supply

Voltage 110-250 Vac 18-72 VDC

Frequency 50-60Hz

Maximum current 0.1-0.2 A Max

Dimensions

Length 482 mm 209 mm

Width 266 mm 136 mm

Height 44 mm 73 mm

Operating conditions Maximum operating temperature 50°C 55°C

Humidity (non-condensed) 90 %

EXPLANATION OF SAFETY SIGNS ON THE PRODUCT


CONTENTS

CONTENTS .......................................................................................................................... 4

1. INTRODUCTION........................................................................................................ 7

1.1. LEDI® NETWORK TDS V1 RACK .................................................................................... 7

1.2. LEDI® NETWORK TDS GPS – RAIL DIN TH35................................................................ 9

1.2.1. Version < 100m cable (solution with antenna GPS converter Part Number: 3Gxx) 10

1.2.2. Version > 100m cable (solution with RTBGPS Part number: 4048/xx)) ................. 10

A. RTB GPS antenna (part number: RTBGPS-4080) ................................................ 12

2. QUICKSTART ......................................................................................................... 13

2.1. PRODUCT CONNECTION .............................................................................................. 13

2.2. MANUAL NETWORK CONFIGURATION ........................................................................ 14

2.3. TIME OUTPUT CONFIGURATION .................................................................................. 14

2.4. ALARM CONFIGURATION ............................................................................................. 14

3. GENERAL INFORMATION ..................................................................................... 15

3.1. TIME ZONES .................................................................................................................. 15

3.2. LEAP SECOND ............................................................................................................... 16

3.2.1. Definitions ............................................................................................................ 16

3.2.2. Protocols incorporating a leap second .................................................................. 16

3.2.3. LEDI® Network TDS performance......................................................................... 16

3.2.4. Configuration recommendations ........................................................................... 17

3.3. SYNCHRONISATION CONCEPTS ................................................................................. 17

3.4. NOTIONS OF THE NTP PROTOCOL ............................................................................... 18

3.4.1 Client/Server mode ............................................................................................... 19

3.4.2. Broadcast mode ................................................................................................... 20

3.5. TIME SERVER STATUS ................................................................................................. 20

3.6. SNMP (SIMPLE NETWORK MANAGEMENT PROTOCOL) AND MIB (MANAGEMENT INFORMATION BASE) ........................................................................................................... 21

3.7 TIME INPUT INSTABILITY DETECTION .......................................................................... 23

4. FRONT LCD DISPLAY ............................................................................................ 24

4.1. LIGHTS AND BUTTONS ................................................................................................. 24

4.2. STARTUP ....................................................................................................................... 25

4.3. TIME DISPLAY ................................................................................................................ 25

4.4. ALARM DISPLAY ............................................................................................................ 26

4.5. IPV4 / IPV6 CONFIGURATION........................................................................................ 28

4.5.1. Display current IP addresses ................................................................................ 28


EN

GLIS

H

4.5.2. Menu .................................................................................................................... 28

4.5.3. IPv29 .................................................................................................................... 29

4.5.4. IPv6 ..................................................................................................................... 31

4.6. RESTARTING ................................................................................................................ 33

5. WEB INTERFACE ................................................................................................... 34

5.1. PRESENTATION ............................................................................................................. 34

5.2. DESCRIPTION OF WEB PAGES .................................................................................... 35

5.2.1. Navigation menu .................................................................................................. 35

5.2.2. "Index" Page ........................................................................................................ 38

5.2.3. "Network" Page .................................................................................................... 40

5.2.4. "Alarms" Page ...................................................................................................... 43

5.2.5. "SNMP" Page ....................................................................................................... 45

5.2.6. "NTP" Page .......................................................................................................... 48

5.2.7. NTP Server Statistics Page .................................................................................. 54

5.2.8. "Input" Page ......................................................................................................... 55

5.2.9. "Output" page ....................................................................................................... 59

5.2.10. "Interface" Page ................................................................................................. 64

A. User Accounts ...................................................................................................... 64

B. Front LCD ............................................................................................................. 65

C. Other interfaces .................................................................................................... 66

D. File system ........................................................................................................... 68

E. SNMP Interface .................................................................................................... 69

F. Telnet and SSH Interface ...................................................................................... 70

G. Command prompt................................................................................................. 70

H. File transfer .......................................................................................................... 74

I. "Restart" Button ..................................................................................................... 74

5.2.11. Update ............................................................................................................... 75

5.2.12. "Diagnostics" Page ............................................................................................. 78

6. APPENDIX A – CONNECTIONS ............................................................................. 81

6.1. INSTALLATION VIEW ..................................................................................................... 82

6.2. DCF-GPS ANTENNA ...................................................................................................... 84

6.2.1. DCF Antenna ....................................................................................................... 84

6.2.2. GPS antenna (converter unit) ............................................................................... 85

6.3. AFNOR-NFS-87500 / IRIG-B OUTPUT ........................................................................... 86

6.4. SERIAL IMPULSION OUTPUT ........................................................................................ 86

7. APPENDIX B – OUTPUT CODES FORMAT .......................................................... 87


7.1. AFNOR/IRIG-B NFS87500 .............................................................................................. 87

7.2. DESCRIPTION OF DCF AND TDF TIME CODES ........................................................... 90

7.3. POLARISED MINUTE PULSES ...................................................................................... 92

8. APPENDIX C – MAINTENANCE ............................................................................. 94

8.1. CARD REPLACEMENT + IMPULSION CARD POWER SUPPLY .................................... 94

8.2. MICROCONTROLLERS REPLACEMENT ....................................................................... 95

8.3. OUTPUT CARDS ADDRESSES SWITCHES .................................................................. 96

8.4. TOP AND IRIG-B DCLS TIME CODE OUTPUT SIGNALS .................................................. 97

8.5. SUPERVISION PROTOCOLS ......................................................................................... 98

8.5.1. Syslog messages catalogue ................................................................................... 98

9. APPENDIX D – TROUBLESHOOTING ................................................................... 99


EN

GLIS

H

1. INTRODUCTION

This document is the instruction manual for the LEDI® NETWORK TDS V1 and the LEDI®

NETWORK TDS GPS Rail Din TH 35. These products are accurate and easily configurable

time servers.

Each server communicates through the following network protocols:

► IPv4 et IPv6 ► HTTP(S) ► SNMP v1, v2c, v3 ► Telnet ► SSH

► FTP ► SMTP ► Syslog ► (S)NTP ► ENDMI (to detect Gorgy Timing

products on the IP network)

Security features ensure that the server delivers reliable and continuous timing information.

1.1. LEDI® NETWORK TDS V1 RACK

The server synchronises through an NTP Ethernet 10/100 base T or DCF or GPS time input.

In case of a DCF or GPS input, the heart of the time base is a temperature-compensated

quartz oscillator (TCXO) which limits deviation when the time source is unavailable.

There are 3 available time outputs: AFNOR NFS 87500 / IRIG B, IMPULSION, NTP.


The use of the LEDI® Network TDS V1 has several advantages:

► Ethernet + IP network interfacing.

► Simplified installation.

► Easy remote configuration and diagnostics.

► 1U 19” rack easily mounted in many installations.

► 3 configurable outputs:

- AFNOR NFS 87500 / IRIG-B

- NTP (V2, V3, V4): Unicast, Multicast et Broadcast

- Minute Impulses 24V //

ASSEMBLY

The rack must be fixed in a 19'' frame using 4 screws and cage nuts, shown in the image below. (Screw 10-32 M6, tightening torque: 1.13Nm).

BOX CONTENTS

The box should contain the following items

► The 19" 1u rack, with the words "LEDI® NETWORK TDS" on the front panel

NOTE: The device code and configuration can be checked on the identification label on the

bottom or back of the device. It must correspond to the following number: 94031/opt (opt

depending on the device options).

► A non-locking IEC 60320 C13 mains power cable

NOT: only for models with alternative current (AC) supply.

► A 2-pin connector for DC power input

NOTE: only for DC models.

► One RJ45 network cable ► A DVD containing software and documentation

☛ Please contact customer service if an item is missing


EN

GLIS

H

1.2. LEDI® NETWORK TDS GPS – RAIL DIN TH35

The time server has GPS synchronisation input providing SNMP supervised NTP time

synchronisation.

Both an alarm visible on the front LED display and quick configuration from the front panel

buttons are available.

209 x 73 x 136 mm (WxHxD)


1.2.1. Version < 100m cable (solution with antenna GPS converter Part Number: 3Gxx)

MOUNTING

Fixing by rear panel in Rail Din (see image below).

► Kit contents (cable and GPS antenna not included):

- LEDI® Network TDS Rail Din

- One RJ45 network cable

- A DVD containing software and documentation

☛ Please contact customer service if an item is missing.

► Power supply:

Direct current (DC) supply 24Vdc (18-72Vdc) on screw terminal block – 10W max

1.2.2. Version > 100m cable (solution with RTBGPS Part number: 4048/xx))

► Mounting:

Rear panel mounting in Rail Din

Antenna to be positioned on the roof of the property and cable (not included) to be

routed to the time server. See reference table for model selection (IRIGB input).


EN

GLIS

H

► Contents of kit (cable and RTB GPS antenna not included):

- LEDI® Network TDS Rail Din (RTB GPS),

- One RJ45 network cable

- A DVD containing software and documentation

☛ Please contact customer service if an item is missing

► Power supply:

Continuous power supply 24Vdc (18-72Vdc) on screw terminal block – 10W max


A. RTB GPS antenna (part number: RTBGPS-4080)

The RTB GPS generator is a GPS (Global Positioning System) satellite system receiver

device delivering time in IRIG B or AFNOR NFS 87500 code.


EN

GLIS

H

2. QUICKSTART

2.1. PRODUCT CONNECTION

It is strongly recommended to make a note of the serial number (written on the identification

label), the location and a brief description of the device. The table in Appendix A - 6.1

Installation View can be used for this purpose.

► Connect the synchronisation output cables to the devices to be synchronised. (See

appendix A - Connections)

► Connect the server to the network by using the supplied network cable or any other

compatible cable.

NOTE: The server can be connected directly to a computer using a crossed network cable.

This can also be done for configuration/test purposes.

► Connect the power supply to the server using an IEC 60320 C13 cable and switch ON

to start it.

► The server will take around 1 minute to initialise.

NOTE: If there is no network cable connection, initialisation may take longer (up to 3 minutes).

The system is set up to obtain its IPv4 and IPv6 addresses from a DHCP server by

default. If such a server is present on a network, the server can be accessed

immediately. Press any of the arrow keys on the server’s LCD front screen to find out

the IP addresses.

► The GT Network Manager software (supplied on the DVD) can also detect the server on

the network and display the IP address.

If you have more than one device to install, it is strongly recommended that you use the

document attached in Appendix A – 6.1 Installation View to make a note of the serial

number and physical location of each device during installation for future reference.

If it does not have an NTP input, the LEDI® Network TDS will automatically synchronise

and generate time signals on its output.

However, by default, all the output cards are configured to transmit UTC time.


2.2. MANUAL NETWORK CONFIGURATION

In the case of an NTP input, local time outputs and/or specific configurations of time outputs,

LEDI® Network TDS server configuration is required to synchronise equipment.

By default, the server is configured to obtain its IP addresses (v4 and v6) on a DHCP server.

There are several ways in which the IPv4 and IPv6 configurations can be manually modified:

► By accessing the web interface, on the ‘Network’ page. (See section 5.2.3)

► By using the buttons on the front (see section 4.5.2)

► By using the Telnet and SSH consoles (see 5.2.10. section F)

Additionally, the server will automatically take an IP address within the 169.254.0.0/16 and

fe80::/10 predefined scopes. The IP addresses of the LEDI® NETWORK TDS can be viewed

on the LCD display on the front panel at any time by pressing one of the arrow keys.

2.3. TIME OUTPUT CONFIGURATION

The default configuration for the output cards is to deliver their time code in UTC format and

only when the server is synchronised.

For most cards, the output time code format as well as the time zone and DST (Daylight

Saving Time) policy can be modified.

Refer to section 5.2.9. ‘Output’ page to change these settings.

2.4. ALARM CONFIGURATION

► The LEDI® NETWORK TDS has an embedded alarm system that alerts administrators

in the event of a problem.

► The LDC front screen displays the current alarm messages, and its backlight flashes to

indicate that at least one alarm is in progress.

► SNMP traps can be sent to one or several supervision stations.

► The server can send an email with details of the situation.

► The server can send Syslog data to one or two servers.

These 3 features are configurable in the ‘SNMP’ and ‘Alarm’ webpages

(see sections 5.2.4 and 5.2.5)


EN

GLIS

H

3. GENERAL INFORMATION

This section introduces the basic concepts of the LEDI® Network TDS. It can help you to

understand the functioning of the product in various circumstances.

The LEDI® Network TDS contains firmware that manages the time flow in the product and

the user interfaces.

3.1. TIME ZONES

The time zone defines the time offset from UTC (meridian time without DST policy) to

generate local time. It has two parameters: a fixed offset and optionally a DST which adds

summertime. For example, in France, the local time is set to UTC+1 :00 plus one hour in

summer by the European DST.

Here are the different summer/winter time changeover policies:

European Union Start: Last Sunday in March at 1:00 UTC

End: Last Sunday in October at 1:00 UTC

USA / Canada / St. Johns /

Bahamas / Turks and Caicos

Islands

Start: Second Sunday in March, at 2:00 local time

End: First Sunday in October at 2:00 local time

Australia – Standard Start: First Sunday in October at 2:00 local time

End: First Sunday in April at 3:00 local time

Chile Start: First Sunday after September 1st at 00:00 local time.

End: First Sunday after 1 April, at 00:00 local time

Egypt No more summer/winter changes since 2015

Namibia No more summer/winter changes since 2018

Iraq No more summer/winter changes since 2008

Syria Start: Last Friday in March at 00:00 local time

End: Last Friday in October at 00:00 local time

New Zealand Start: Last Sunday in September at 2:00 local time

End: First Sunday in April, at 3:00 local time

Paraguay Start: First Sunday in October at 00:00 local time

End: Fourth Sunday in March, at 00:00 local time

Falkland Islands No more summer/winter changes since 2010

State of Mexico Start: First Sunday in April at 2:00 local time.

End: Last Sunday in October at 2:00 local time


3.2. LEAP SECOND

3.2.1. Definitions

What is a leap second, what is its purpose, when does it occur?

Find answers here: https://en.wikipedia.org/wiki/Leap_second

3.2.2. Protocols incorporating a leap second

NTP, DCF, TDF and IRIG-B IEEE 1344 protocols include a field in their messages to indicate

that a leap second will occur. This information is given throughout the last day in NTP, the

last hour in TDF/DCF or the last minute in IRIG-B before it takes effect.

Unlike NTP, TDF and IRIG-B, the DCF code does not indicate whether a second should be

added or removed. In practice only additions are made.

3.2.3. LEDI® Network TDS performance

When an LEDI® Network TDS has a leap second indication (configured or received in NTP),

it continues to operate normally by propagating the indicator until the precise moment of

occurrence of the event (30th June or 31st December at midnight). At midnight, it will

authorise the jump of the second so as not to trigger an alarm, apply the insertion and stop

transmitting the indicator to the time outputs.

If the manual setting of the leap indicator (see section 5.2.8 > “input” page > Manual setting

of the leap indicator) is configured, the time entry indicator is ignored. This configuration will

be cancelled in January or July. The setting Manual setting of the leap indicator (see section

5.2.8. > “input” page > Return to "No additional second) allows you to select whether the

manual indicator returns to the deactivated state or “No additional second” at this

cancellation.

An LEDI® Network TDS that receives a second input more than 1 minute late or early can

invalidate the time input and continue autonomously or deactivate its time outputs if the

safety threshold is set to one second.

https://en.wikipedia.org/wiki/Leap_second


EN

GLIS

H

3.2.4. Configuration recommendations

To comply with legal time, if there is no indicator on the time input of an LEDI® Network TDS,

check in the latest IERS Bulletin C if a leap second will be inserted in June or December at

least one month in advance and configure the manual indicator on this product accordingly.

Certain NTP clients refuse to synchronise with servers that do not provide a leap second

indicator. On these NTP servers, the manual indicator must therefore be configured and its

return to 0 at insertions (by default it is disabled at insertions) in order to the clients to

synchronise.

3.3. SYNCHRONISATION CONCEPTS

Synchronisation refers to the process of setting a local clock (known as “internal”) by aligning

the information with a distant clock (the “reference”).

A local clock runs using a reference frequency, created by an oscillator. The LEDI®

NETWORK TDS integrates a temperature-compensated oscillator (TCXO).

In order to achieve this synchronisation, the device which is to be synchronised (called the

client) compares its clock with that of a reference device (called the server) and calculates

the following information:

► Offset: this is the instantaneous difference between the client’s time and the server’s

time. For example, if the server indicates 2:10:13 and the client displays 2:11:14, the

offset is 1:01.

► Drift: this is the difference in frequency between the two clocks. If not corrected, the

offset between the two clocks is constantly increasing or decreasing.

The following diagram shows how the two clocks evolve with or without drift:

https://hpiers.obspm.fr/eoppc/bul/bulc/


The aim of synchronisation is to reduce offset and drift as much as possible. The accuracy

and stability of the client clock are closely related to the efficiency of the reduction process.

3.4. NOTIONS OF THE NTP PROTOCOL

NTP (Network Time Protocol) allows time synchronisation of different devices via an IP

network.

Several communication modes are possible in NTP. They are described below.

The time information exchanged over the network is in UTC (GMT+0). Therefore, clients

(e.g., clocks) have to convert this time using their own time zone information. Section 3.1.

Time zones explains how time zones function.

A signature can be included in NTP time packets. When present, the receiver can verify the

identity of the sender and ensure the authenticity of the packet. In order to a receiver to verify

a signature, the same secret 128-bit key must be configured on the client and the server to

the same key number (from 0 to 4294967295 (232 numbers)) and the initiator of the

communication must be configured to use this key number. The identification codes contain

the key number and the signature (128-bit MD5 hash) of the packet (see section 5.2.6. "NTP"

page).

In addition to the NTP client software for Windows issued by Gorgy Timing (Gt Synchro),

other NTP client software for various devices can be found at www.ntp.org/software.


EN

GLIS

H

3.4.1 Client/Server mode

This mode is the most widely used as it is compatible with conventional network

infrastructures and is highly accurate.

The client regularly evaluates the current offset in relation to its servers. This measurement

is done using a message exchange mechanism as shown in the following diagram:

When the data contained in the server response and the time of receipt, the NTP client

calculates the offset of its clock by subtracting the server date from its clock to compensate

for transmission delays. For greater accuracy by simply subtracting the server’s sending date

from the client’s receiving date or the server’s receiving date from the client’s sending date,

the client can obtain the sum of the offset and transmission delay, but this would cause an

error in correcting its clock. In order to remove the transmission time from the result, the

client subtracts the average of the two server dates. The result obtained is equal to the offset

plus an error equal to half the difference between the two transmission times.

On average, over several acquisitions of the offset and over a single network, this error is

zero. The client can therefore increase the accuracy as the exchanges progress.

Starting from the second offset calculation, each calculation estimates the drift of the client

clock. Depending on the client, the drift can be used to regulate the clock in order to reduce

future drifts.


Depending on the client software, the accuracy provided can be close to a few tens of

microseconds.

For added security, clients can be configured to use a different secret key for each server.

3.4.2. Broadcast mode

An NTP server configured in broadcast mode regularly sends an NTP packet to a

configurable IP address. This address can be a broadcast address (all devices on the

network receive a packet), a multicast address (all devices configured to monitor the address

receive a packet) or a unicast address (only the device at the address receives the packet).

Caution: routing of packets to a broadcast or multicast address is usually disabled by default

on commercially available routers.

This mode can be used to synchronise clients with less network traffic (traffic with several

clients in this mode is then lower than with a single client in client/server mode) but the

transmission will not be compensated unlike in client/server mode.

3.5. TIME SERVER STATUS

The following diagram shows the different states of the time server:


EN

GLIS

H

Here are the meanings of the different states:

► Initial: The time server has just started up.

► Synchronising: The time input is valid. The time server has selected it. It is waiting until

the time information is sufficiently accurate and propagated on the server before

activating its time output.

► Synchronised: The synchronisation of the time server is complete. The synchronisation

outputs are operational It will continue to reduce the phase difference if possible.

► Autonomous: The time server can enter this state if a user activates the autonomous

mode or if its time output is unavailable and a duration of autonomy configured.

► Failing: The time server can enter this state if its time input is unavailable and no

autonomy time has been configured or the autonomy has been exhausted.

3.6. SNMP (SIMPLE NETWORK MANAGEMENT PROTOCOL) AND MIB (MANAGEMENT INFORMATION BASE)

Please see RFC 1157 for mor information on the SNMP protocol. It enables you to read and

modify data from an agent (produced on the IP network) through requests sent to transfer

traps (alerts) sent automatically by an agent to a trap server. The default UPD ports are 161

for requests and 162 for traps.

In versions 1 and 2c, an SNMP server only responds to requests containing the specified

community name configured on the server. It is therefore necessary to configure the same

name on the client. By default, the community usually used by different software is ‘public’

for reading and ‘private’ for writing. There is no authentication mechanism, and the data

circulates in clear text on the network. Version 3 offers the USM (User-based Security

Model). This makes it possible to authenticate the client and the server to protect against

identity theft and even to encrypt the data to hide it. Authentication and encryption each

require a password of at least 8 characters known in advance to the client and server.


The data accessible in SNMP are distributed in variables integrated in a universal tree

structure. Parts of this tree structure are commonly described in MIB-2 compatible files (RFC

1213) also called MIB files). These files can be opened with a MIB browser (iReasoning MIB

Browser, SNMPb, …) or with a text editor (Notepad, WordPad, …). For example, with

iReasoning MIB Browser the content of a MIB can be added to the displayed tree structure

by clicking on File → Load MIBs (see screenshot below).

iReasoning MIB Browser also provides a trap receiver that can be launched by clicking on

Tools → Trap Receiver.

In the tree structure, each node (folder or table) and each sheet (variable)| has a unique

number and name in the folder containing them. Thus each element in the tree structure

(folder, table or variable) can be identified by a sequence of names and/or numbers called

OID (Object Identifier) e.g. the folder containing all the variables specific to Gorgy Timing

products can be identified by "iso.org.dod.internet.private.enterprises.gorgy",

".1.3.6.1.4.1.8955" or a mixture of both.


EN

GLIS

H

The tables can be considered as files containing only variables. To raise an SNMP query,

you must give an OID variable followed by “.0” if the variable is not in the table, otherwise

the input index must be given in the table.

There are several possible forms of query:

► GetRequest asks for the value of a variable

► GetNextRequest asks for the value of a following variable

► GetBulk asks for grouped values of a set of variables

► SetRequest changing the value of a variable

► Walk absent from RFC, request for all of the following variables

If the requested variable is not available, responses to queries are accompanied by a

noSuchObject error.

3.7 TIME INPUT INSTABILITY DETECTION

Instability detection is performed independently on each synchronisation input when it is

selectable, and the time server is synchronised or has remaining autonomy but not in free-

running mode. It does not apply the NTP input because it can change the source server in

case of a problem.

When a deviation of more than 500 ms from the time server is detected on an input and until

the input returns below 500 ms, the server reaches the end of autonomy, the jump is

validated by a user or the free-running mode is activated, the time server has 2 contradictory

time indications. It therefore informs its users of this anomaly by switching the shifted entry

to the “Unstable” state and invalidating it. An external action is then required to return to a

consistent state by correcting or invalidating the incorrect time inputs and/or validating the

new time of the entries in the “Unstable” state.

In order to validate the new time of an “Unstable” entry, an “Allow this leap” checkbox is

displayed in the configuration of this entry in the “Input webpage as shown below. Once

checked and validated by clicking “Save Settings”, the time server accepts that the new time

for this input is correct and that this entry can be selected again to synchronise it.


4. FRONT LCD DISPLAY

4.1. LIGHTS AND BUTTONS

The front panel display can show 4 lines of up to 20 characters each. There are 6 buttons

which are used to navigate through the menus and to change the IPv4/IPv6 settings (see

section 4.5.2. ”Menu”) There is a “RESET” button to restart the product with the with the

exception of the GPS input card.

There are three light indicators on the front panel. There meanings are stated below:

Name Colour Meaning

POWER Green

ON: Normal operation

The device is connected to an external power supply.

OFF: No external power supply is detected by the server.

SYNC Yellow

ON: Normal operation

The device controls its internal clock based on its time input.

OFF: Time input is not available.

ALARM Red

FLASHES EVERY SECOND:

At least one alarm is currently active on the device. See section

5.2.4 “Alarms” page for more details.

OFF: Normal operation. No alarms are activated.


EN

GLIS

H

4.2. STARTUP

During start-up, the LCD screen displays the message "Init..." until the embedded software starts and shows the loading status of the different software modules:

The firmware version is displayed on the second line whilst it is loading.

4.3. TIME DISPLAY

Normal operating:

► Date and time are displayed at all times.

► The last line shows the current synchronisation source.

Here are the various possible messages:

► NTP synchronisation input


► DCF or GPS synchronisation input

► The third line shows the current alarms. If several alarms are active, each will be

displayed successively for a few seconds. The following section describes the

meaning of the alarms.

4.4. ALARM DISPLAY

When a short description alarm occurs, it appears on the third line of the display and the

LCD/OLED backlight flashes.

The following is a list of possible alarms and their meanings:

► FREE RUNNING: the server has been forced into autonomous operating mode. No time

input is used for synchronisation. Useful for test purposes.

► NO TIME CODE!: the time sources are not available (GPS signal not received, no NTP

server available…)

► AUTONOMY CRITICAL!: there is no available source of synchronisation and the server

is about to switch the outputs off (3 remaining minutes of autonomy).

► NEVER SYNC!: the server has been running for at least 15 minutes and there is still no

valid synchronisation source available.

► ETHERNET LINK ERROR: there is a problem with the network cable connection.

► OUTPUT ALARM!: one or more output cards are not detected by the main control

board. You can check the status of the output cards in the web page in the “Output”

tab. This status may occur temporarily during initialisation and in normal operation.

If the fault persists and the corresponding outputs no longer emit time codes, please

contact Gorgy Timing Customer Service.

► SERVER LOCKED: the time outputs have been disabled by a user.

► SYNC ALARM!: there is no time source available and the server has no more

autonomy.

► SECURITY LOCKDOWN!: the configuration interfaces are locked for 5 minutes

following 3 authentication failures.


EN

GLIS

H

► WAITING SAT INFO: the satellite synchronisation module expects certain information

from the system constellation (almanacs). This message should disappear after a few

minutes.

When an alarm with a long description occurs, it is displayed across the entire screen.

The following is a list of possible long description alarm messages:

WRITING TO FLASH

DO NOT RESET

The main ethernet interface of the time server is writing in flash.

Restart the product by clicking the RESET button or with a power failure and an empty battery can corrupt the data or even render the time server unusable.

UPDATING FIRMWARE

DO NOT RESET

The main ethernet interface of the time server is writing new firmware in flash.


REBOOTING

……

The main Ethernet interface of the time server is rebooting.

FACTORY DEFAULTS

DO NOT RESET

The main Ethernet interface of the Time Server is resetting the user settings.

FIRMWARE CORRUPTED

DO NOT RESET

UPDATE AGAIN

The flash firmware in the main Ethernet interface of the time server is corrupted.


The firmware must be sent back to the interface to replace the corrupted firmware.


4.5. IPV4 / IPV6 CONFIGURATION

The blue LCD screen and the buttons can be used to manually set up the IP settings of the

LEDI® NETWORK TDS.

4.5.1. Display current IP addresses

► Press any of the arrow keys to bring up a screen showing the IP addresses of the LEDI®

NETWORK TDS for a few seconds.

► Depending on the context, these addresses can be DHCP attributed, user-defined or

self-assigned.

4.5.2. Menu

► To access the menu from the main screen, press the “OK” button. A selection menu will

then appear.

► Use the “ ↓ ” and “ ↑ ” keys to navigate the menu. You can choose between IPv4 and

IPv6 configuration. Press “OK” to display the chosen configuration screen.


EN

GLIS

H

4.5.3. IPv29

The below diagram describes the IPv4 configuration menus tree. An explanatory paragraph

is provided after the diagram.

► Step 1

Use the direction keys “ ↑ ” and “ ↓ ” to switch between Static and DHCP mode. Use

the “ ESC ” key to return to the previous menu and the “ OK ” key to validate the selection

and move to step 2.


► Step 2

► Static mode:

This menu allows you to set up:

- The IPv4 address (IP field),

- The sub-mask (MASK field)

- The network gate (GATE field).

The field being modified flashes on the screen.

Use the “ ↑ ” and “ ↓ ” arrow keys to change the field value.

Use the “ → ” and “ ← ” arrow keys to switch between fields.

Use the “ESC” button to cancel the changes and return to the previous menu.

Use the “OK” button to validate the new IPv4 configuration and move on to step 3.

► DHCP mode:

This mode enables the DHCP client to obtain network settings automatically from

a DHCP server on the network.

Use the “ESC” button to cancel modifications and return to the previous menu.

Use the “OK button to validate the new IPv4 configuration and go to step 3 if the

settings have changed. Otherwise, go to the main menu.

► Steps 3 and 4

The server records the new settings (“WRITING TO FLASH” message) then reboots

(“REBOOTING” message) immediately after.

It is forbidden to attempt to stop the device or to disconnect the device from its power sources until the product has rebooted completely. This last step is complete when the device displays the date, time and synchronisation screen.


EN

GLIS

H

4.5.4. IPv6

The below diagram describes the IPv6 configuration menus tree. An explanatory paragraph

is provided after the diagram.


► Step 1

Use the “ ↑ ” and “ ↓ ” arrow keys to switch between Static and DHCPv6 mode,

Use the “ESC” key to return to the previous menu. Use the “OK” key to validate the

selection and more on to step 2.

► Step 2

► Manual mode:

Three successive menus allow you to configure:

- The host’s IPv6 address,

- The sub-network prefix,

- The network gateway’s IPv6 address.

The field being modified flashes on the screen.

Use the “ ↑ ” and “ ↓ ” arrow keys to change the field value.

Use the “ → ” and “ ← ” arrow keys to switch between fields.

Use the “ESC” button to cancel the changes and return to the previous menu.

Use the “OK” button to validate the new IPv6 configuration and move on to the next

step.

After the network gateway’s IPv6 address has been validated, move on to step 3.

► DHCPv6 mode:

This mode enables the DHCPv6 client to obtain network settings automatically from

a DHCPv6 server on the network.

Use the “ESC” button to cancel modifications and return to the previous menu.

Use the “OK button to validate the new IPv6 configuration and go to step 3 if the

settings have changed. Otherwise, go to the main menu.

► Steps 3 and 4

The server records the new settings (“WRITING TO FLASH” message) then reboots

(“REBOOTING” message) immediately after.

It is forbidden to attempt to stop the device or to disconnect the device from its power sources until the product has rebooted completely. This last step is complete when the device displays the date, time and synchronisation screen.


EN

GLIS

H

4.6. RESTARTING

► Press “OK” on this page to reboot the LEDI® Network TDS.


5. WEB INTERFACE

5.1. PRESENTATION

The LEDI® NETWORK TDS can be configured and supervised through a WEB interface

(website composed of several pages). This is accessible in http or https depending on the

configuration of the time server.

In https the LEDI® Network TDS is compatible with TLS 1.2,

TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA and

TLS_RSA_WITH_AES_256_CBC_SHA256.

This interface provides you with the following features:

► Configuration of network settings

► Configuration of SNMP supervision settings

► Configuration of time inputs

► Configuration of time output cards

Each LEDI® Network TDS and each NTP output card has its own WEB server.

To access the main “Index” page of the website, type the IP address or host name of your

device into the address field of your web browser (as shown below) and validate the entry.

It is recommended to use the most up-to-date versions of browsers to avoid experiencing

any display errors.

To access the server using its IPv6 address, enter it in square brackets:

To access the server in https, add “https://” before the address.


EN

GLIS

H

5.2. DESCRIPTION OF WEB PAGES

5.2.1. Navigation menu

When accessing the web interface, the “Index” page is displayed.

On the left, you will see a navigation menu which displays the different pages.

1. Index: General information about the product and quick disabling of the outputs.

See section 5.2.2.: "Index" Page

2. Network: Managing of network settings.

See section 5.2.3.: "Network" Page

3. Alarms: Configuration of sending and backing up logs.

See section 5.2.4.: "Alarms" Page

4. SNMP: Configuration of the SNMP module.

See section 5.2.5.: "SNMP" Page

5. NTP: Diagnostic and configuration of NTP Server/Client.

See section 5.2.6.: "NTP" Page

6. Input: Offset from input time code, autonomy and standalone mode configuration.

See section 5.2.8.: "Input" Page

7. Output: Diagnostic and configuration of output cards.

See section 5.2.9.: "Output" Page

8. Interface: Settings of web pages and other server interfaces.

See section 5.2.10.: "Interface" Page


Each time that this icon: is shown, it means that the user can hover over the icon with the

mouse for more information about the field in question.

With the exception of the index page, access to all pages is restricted. A valid connection to the site is required before

displaying these pages and modifying values.

By default, the connection to the site is made by typing:

Username: root Password: gtmt

See section “A. User Accounts” paragraph 5.2.10. “Interface” Page for user accounts management.

After 5 unsuccessful connection attempts (Web page, telnet, SSH, ftp) the product will enter a general lock state. The

interfaces will not be accessible for 5 minutes.

► One or more of the following buttons can be found on each Web page:

“Save Settings”1 button

Saves configuration changes in the flash memory as

opposed to the temporary memory. This memory retains

settings even if power is lost.

Certain settings require the device to be restarted to be

applied. When they have been changed, the message

“Warning! A reboot is required to apply some changes

saved” is displayed above the “Save Settings” button.

“Restart”1 button

Restarts the Ethernet interface which also manages the

synchronisation status of the time server.

The “Restart” button is displayed on Web pages where at

least one setting requires a restart once it has been changed.

“Cancel Changes” button

Cancels any changes. Equivalent to refreshing the web page

(shortcut: “F5” key in most web browsers).

1 - Notes about the use of the “Save Settings” and “Restart” buttons:


EN

GLIS

H

► From NTPServ 2.00 firmware release including 17.292:

The “Restart” button is available on Web pages with settings requiring the server to be

restarted when modified.

After clicking “Save Settings”, the message “Warning! A reboot is required to apply some

changes saved.” appears above the “Save Settings” button. The user may continue to

change the settings on different Web pages and restart the server once all the settings

have been configured or choose to restart the server immediately by clicking the

“Restart” button. The time outputs are then interrupted for a few seconds while the server

reboots.

When the Ethernet interface is in one of the sensitive states defined below, these Web pages

are replaced with a warning page.

Re-connection to the web interface in 1 minute…

This Ethernet interface is rebooting.

Updating firmware

Do not reset nor shut down the product.

This Ethernet interface is writing its new firmware in flash.

Restarting the device with the RESET button or by removing the power supply or battery makes the time server unusable.

Firmware corrupted


Please reupload a firmware.

The flash firmware in this Ethernet interface is corrupted.

Restarting the product with the RESET button or by removing the power supply or battery makes the time server unusable.

The firmware must be sent back to this interface to replace the corrupted firmware.


5.2.2. "Index" Page

This page displays general product information.

Product Information

► Product name ► Displays the server name.

► Serial number ► Displays the GORGY TIMING serial number of the product. It is a 6-digit number identical to the one labelled on the bottom or back of the product.

► Up Time ► Total running time of the Ethernet interface since it was last reset. The

Ethernet interface restarts when the LEDI® Network TDS is powered on, when the

RESET button is pressed and when the software is restarted (via web page, firmware

update, …).

Time Base

► Synchronisation source ► Input currently selected for synchronisation.

► Synchronization state ► Overall server synchronisation status.

► Current date/time ► The time currently delivered by the server in UTC format

(meridian time without DST policy)


EN

GLIS

H

System

► MAC Address ► Medium Access address of the Ethernet interface.

► Firmware version ► Current version of the firmware embedded in the Ethernet module.

Always starts with “2.00 release”. The first number corresponds to the year and the

second to the day of the year of the firmware release date.

► Time base version ► The number of the firmware managing the time base. This

number is "NTPINDF1/1805" for the products set up for GPS or DCF synchronisation and

“NTP Client” for the products set up for NTP input.

► Last reboot reason ► Indicate the reason for the last reboot of the Ethernet interface.

Lock Status

This section informs you of the lock status of the server and gives you setting options.

► Unlocked server:

Normal operating status.

Pressing the button will switch to “Locked server” status


► Locked server:

Degraded status.

The server has detected a time gap superior to the

authorised threshold on its synchronising input, or the status

was forced by clicking “Lock the server now”.

In this state, the server no longer delivers synchronisation

time output codes.

Pressing this button will switch to “Server not locked”. The

“Server not locked” status is also the default status after

rebooting.

5.2.3. "Network" Page

This page is intended for the network configuration of the LEDI® Network TDS.

IPv4 Settings

The current IPv4 settings are displayed.


EN

GLIS

H

► Address from DHCP server

If this box is checked, the LEDI® NETWORK TDS will attempt to get an IPv4 address

from a DHCP server at startup. Failure to obtain an address this way will result in the

server using its automatically configured address.

By unchecking the box, the following settings become available:

► IP Address

Configures the LEDI® NETWORK TDS IPv4 address in the format: xxx.xxx.xxx.xxx

where “xxx” are values from 0 to 255.

► Network submask

Configures the subnet mask to be used. For example, “255.255.255.0” (the network

address range is from 192.168.0.1 to 192.168.0.254).

► Gateway address

If the LEDI® NETWORK TDS is to communicate with elements outside the subnet, this

gateway address must be defined. If this is not the case, leave the gateway field empty.

► Auto-IP Address Enable

If this box is checked, an Auto-IP address (169.254.x.x/16 range) is assigned to the

server in addition to the DHCP or manual address.

Active by default.

IPv6 Settings

The current IPv6 settings are displayed.


The first section displays the current status, while the second section is used to configure

the settings:

► Address from DHCP server

If this box is checked, the LEDI® NETWORK TDS will attempt to get an IPv6 address from a

DHCP server at start-up. Failure to obtain an address this way will result in the server using

its automatically configured address.

By unchecking the box, the following settings become available:

► IP Address

Configures the IPv6 address of the LEDI® NETWORK TDS in either a reduced format (i.e.

fc00::0001) or in complete format (i.e. fc00:0000:0000:0000:0000:0000:0000:0001)

► Subnet Prefix length

Sets up the length of the submask prefix in bits. For example, a value of 64 means that

the first 64 bits (fc00:0000:0000:0000: in the previous example) define the subnet in

which the LEDI® Network TDS is located.

► Gateway address

If the LEDI® Network TDS is to communicate with devices outside the subnet, the IPv6

address of the subnet gateway must be specified. Can be written in short form (i.e.

fc00::8) or full form (i.e. fc00:0000 :0000:0000:0:0000:0000:0008).

If you do not wish to use a gateway for IPv6 communications, simply leave the default

value in the gateway field (0000:0000:0000:0000:0000:0000:0000:0000).

Additional settings

In the last part of the page, the following settings can be configured:


EN

GLIS

H

► DHCP client identifier:

This field can contain a customisable DHCP ID. The value is inserted as an argument of

DHCP option 61 in DHCP requests sent to the server. Your DHCP server can then store

the ID/IP address pair to reserve this IP address and redistribute it when the same ID is

provided. It can also register the product in your DNS (Domain Name System) server,

which allows the product to be addressed with its ID rather than its IP. For example, if

you give the LEDI® Network TDS the DHCP name ntpsrv1, simply type ntpsvr1 in the

address field of your web browser to access the product site.

► Disable Ethernet link failure alarm:

Checking this box will disable the display of the front panel alert message when the

Ethernet interface cable is disconnected.

5.2.4. "Alarms" Page

This Web page is used to configure all the alarms that the LEDI® Network TDS can send.

Syslog reporting

► This section allows you to configure the supervision device by sending event logs in

Syslog format.

NOTE: It is recommended to use SNMP supervision instead of Syslog reports (See section 5.2.5.

“SNMP” page).

If “Enable Syslog reporting” is checked, when an event/alarm occurs, the LEDI® Network

TDS sends a UDP packet to the ports of both IP addresses configured here. Syslog

messages have the format defined in RFC 5424. For example, “<14>1 2018-07-

02T07:21:00Z LEDI_NETWORK_TDS_V1_181192 - - - - - A new configuration

has been defined in the "Alarms" Webpage”.

☛ Syslog messages are described in “8. Appendix C – Maintenance – 8.5.1.

Syslog message catalogue” in this user manual.


E-Mail alerts Management

Use this part of the Web page to set up the device supervision to send event logs by e-mail.

If “Enable email alerts” is checked when an event/alarm is triggered, the LEDI® Network

TDS will send an email to the SMTP server port by authenticating as configured here. The

SMTP server address can be a DNS name or an IP address.

SD Card Management

Use this part of the Web page to configure the supervision of the unit by recording event logs

on the SD card.

If “Enable logging on SD card” is checked when an event/alarm is triggered, the LEDI®

Network TDS records it on the SD card.

Note: After removing the SD card from its socket, you will need to restart the server, for

example by using the front panel, for the card to be detected again.


EN

GLIS

H

Events / Alarms table

Use this part of the Web page to configure filter settings for two features for sending event

logs.

Use this table to choose which events trigger logging on the SD card and/or sending an e-

mail.

5.2.5. "SNMP" Page

Use this Web page to configure the SNMP supervision agent running on the LEDI® Network

TDS.

For general details about SNMP, see 3.6. SNMP.


System information

► The three fields Name, Location and Contact can be individually filled in to provide

information about the LEDI® Network TDS in the variables “sysContact”, “sysName” and

“sysLocation” of the classic .iso.org.dod.internet.mgmt.mib-2.system branch.

► Use the community field for SNMP versions 1 and 2c. The community of the SNMP

client connecting to the server must match this field for the server to respond to the

request.

► The default SNMP name for the LEDI® Network TDS (visible in an SNMP browser and

GTNetworkManager 2) is LEDI® NETWORK TDS nnnnnn where nnnnnn is the 6-digit

serial number.

► The default SNMP name for an additional NTP output is NTP SERVER OUTCARD a

nnnnnn where a is the a is the address of the card on the output bus and nnnnnn is the

LEDI® Network TDS 6-digit serial number. You can also find the address of the card in

the “Output” Web page of the Ethernet interface of the time server management.

Security options & SNMPv3 credentials

► The LEDI® Network TDS uses an SNMPv3 compatible server with security options.

► You can choose to disable SNMPv1 and SNMPv2c by checking the corresponding box.

Doing so will mean that the server will not respond to any SNMPv1 or SNMPv2c

requests.


EN

GLIS

H

► If you want to use the SNMPv3 protocol features, simply enter a username in the

Username fields.

► Filling in the Password field automatically activates the password check on incoming

SNMPv3 requests. Then the server will only respond to the requests with valid

credentials. The password must be at least 8 characters. The control uses the algorithm

selected from the Authentication Protocol drop-down list.

► In addition, specifying the Privacy key field will automatically enable the encryption of

SNMPv3 exchanges. Then, the server will only respond to requests encrypted with the

same key. The key must be at least 8 characters long. Encryption uses the algorithm

selected in the Privacy Protocol drop-down list.

These 5 SNMPv3 settings must be the same in the SNMP client configuration as in the

server configuration.

Traps

SNMP Traps are warning messages sent by the LEDI® Network TDS when an important event occurs. This part of the SNMP page allows you to configure which addresses these messages are sent to and in which format the traps will be sent.

► For each recipient, you can configure which combination of IPv4 address/port to send

the trap to. The Mode field allows you to choose if this recipient is used and, if so, which

version of SNMP to use.

► Please refer to the MIB for more information about the LEDI® Network TDS SNMP trap

messages.

☛ Changing the “Username”, “Password” and “Privacy Key” fields requires the

network interface to be restarted.


5.2.6. "NTP" Page

The NTP page shows the synchronisation mode used by the server or the mode selected by

the NTP software. It also shows the NTP servers defined by the user.

“NTP Server” Section

Use this section to manage the settings of the NTP server.


EN

GLIS

H

Enable NTP Server

► If this box is not checked, the server will not respond to any NTP requests.

Reference ID

► This field shows the current “Reference Identifier” used in NTP messages. This field is

automatically computed depending on the LEDI® NETWORK TDS synchronisation

status. It can be “DCF” (DCF or GPS synchronisation) XNOT if the product is not

synchronised, or correspond to the IP address of an NTP server (NTP synchronisation).

Override Reference Identifier et New Reference ID

► If the “Override Reference Identifier” box is checked and the product is synchronised by

its frequency input, the reference ID used in NTP messages is replaced with “New

Reference ID”.

Current stratum

► The value of the stratum stored in the NTP messages sent to NTP clients.

Authentication policy

► Use this field to choose whether the server will respond to an NTP request, based on

the presence of an MD5 hash value. You can choose to accept any request, or only

those that are secure, or only those that or not secure.

Serve symmetric active/passive requests

► Checking this box enables the NTP symmetric active/passive requests mode.

If synchronization lost

► Defines the effect on some NTP fields when the device is not synchronised.

► Stratum Level

The stratum level sent can be modified.

Values can be set from 1 to 16 or select the option “Do not modify Stratum” to not

change the STRATUM field when synchronisation is lost.

► Leap Indicator

The stratum level sent can be modified.

Available values are “3 (0b11)” or “do not modify Leap indicator” to avoid modifying

the LI field when synchronisation is lost


NTP Server statistics

► Enable NTP statistics logging

Checking this box allows a log to be recorded each time an NTP request arrives at

the server. The list of clients can be consulted on another page by clicking on the

“View NTP statistics” link.

Broadcast options

The LEDI® NETWORK TDS can send time to all addresses over the subnet. All you need to

do is to specify the broadcast address to be used. A multicast or unicast address can also

be used here.

☛ This mode allows a large number of clocks to be synchronised quickly.

Enable NTP broadcast on IPv4

► Checking this box enables the broadcast mode on IPv4.

“Use this broadcast address” fields

► In this field, the user can enter the broadcast destination’s IP address.

Broadcast period

► Use this field to set up the NTP broadcast message frequency.

Use MD5 encryption

► Enables MD5 signature on broadcast packets.

► To enable the MD5 signature, select the key from the drop-down menu (“Key #1” to “Key

#8”) and complete the corresponding field in the “MD5 Keys” section.

When the autonomy is depleted

► This list allows you to choose whether or not the server should continue to broadcast the time when synchronisation is lost, and the server no longer has autonomy.


EN

GLIS

H

"NTP Client" Section

If the option is installed, the LEDI® NETWORK TDS can synchronise with up to 5 NTP

servers. The NTP client actually sends requests to only one server at a time, but it is able to

automatically switch to another server in case the one it is using stops responding or does

not send enough responses.

Polling rate

► This list defines how often the LEDI® NETWORK TDS queries the NTP servers for

synchronisation.

Number of requests

► This list configures the number of NTP messages to be sent in a request stream at the

desired polling rate.


Client mode

► The NTP client sends queries to all servers one by one according to their position in the

list. The NTP client therefore first sends a query to the server at the top of the list at start-

up. If the first server is unavailable or if no NTP address is provided, the query is sent to

the second server and so on.

The “Client mode” defines how the NTP client switches from one server to another under

normal operation, in the event of loss and return of the servers’ availability (hardware

failure, network failure, etc.).

Sync these servers by

descending priority

The NTP client only changes server if the current server is unavailable.

For example:

- The NTP client is synchronised to server 1.

- An incident on server 1 makes it unavailable.

- The NTP client then synchronises to server 2.

- Server 1 becomes available again.

- The NTP client remails synchronised to server 2.

Note: in this mode, the transmission of NTP requests is minimised.

Sync highest available

server in the list

The NTP client tries to reach the server at the top of the list.

For example:

- The NTP client is synchronised to server 1.

- An incident on server 1 makes it unavailable.

- The NTP client then synchronises to server 2.

- The NTP client continues to send requests to monitor the availability of server 1.

- Server 1 becomes available again.

The NTP client switches back to server 1 and stops sending queries to server 2.

Note: in this mode, the NTP client continues to send queries to server(s)

located higher on the list than the server it is synchronised with.

Server list

► Use these fields to enter the IPv4 addresses of the NTP servers. If an MD5 key number

is specified, the LEDI® Network TDS will add the corresponding MD5 signature to NTP

requests sent to the servers.

The Use gateway box must be checked if the server to be contacted is outside of the

local network.

Statistics on server availability are also available:


EN

GLIS

H

NTP requests sent Number of queries sent by the server since the NTP

client was activated.

Received answers Number of responses received by the server from the

contacted NTP server.

Last Sync Data about the period during which the embedded NTP

client correctly contacted the distant server.

Last contacted server

► Displays the server currently being used as a synchronisation source.

MD5 Keys

MD5 keys number from 1 to 8 can be configured here.

They are limited to a maximum of 8 ASCII characters. They can be used in the configuration

of:

► the NTP client and/or

► the server in client/server mode and/or

► the server in broadcast mode.

"DSCP" Section


Use the DSCP (Differentiated Services Code Point) field to enable service differentiation.

Please see RFC 24741 for more information.

When this box is checked, the 1-byte the Type of Service (ToS) field in NTP packets is

replaced by the DS field. The first 6 bits (DSCP) of the DS field are then configurable here.

5.2.7. NTP Server Statistics Page

This page displays the list of clients which have requested the time from the server. It is also

possible to activate the NTP Client Supervisor (NTP Watcher Engine) here.

The NTP Client Supervisor is a feature that alerts the administrator when a client does not

request the time from the server for a specified period of time. (Alert via syslog, e-mail or

logging on SD card).

The user can remove the list of saved clients by clicking the “Reset Statistics” button.


EN

GLIS

H

5.2.8. "Input" Page

The input page regroups information and settings about the time base and the time input

available on the LEDI® Network TDS.

Time Base

State

► This field provides information about the type of oscillator and the current accuracy of

the time base in relation to the synchronisation input. For example, when the LEDI®

Network TDS is switched on, the time base needs time to control its oscillator. The type

of synchronisation source also influences this value.

Current Frequency Source

► This field indicates that the LEDI® Network TDS works with its own oscillator, not with

an external frequency input.

Enable autonomous mode

► This box allows you to switch the server to “Free Running” mode, where it will

autonomously run a synchronisation source. When this box is checked, the following

options appear.


► Modify internal time

Checking this box allows you to modify and force the internal time on the system

when it is in “Free Running” mode. The internal time and date will be displayed in

UTC. For example, if the local time in France is 20:59:00 on 01/02/2010, enter

19:59:00 on 01/02/2010 to get the UTC time (one hour earlier as France is UTC+1,

DST OFF at this time of year).

► Stratum

The stratum value can be forced in “Free Running” mode.

The default value is 1.

CAUTION: Free Running mode should only be used for test purposes. Time may be inaccurate as it may depend on the user’s setting.

Primary Input

Several options are available depending on the synchronisation input type

The images below show the available information according to each synchronisation input

type.

DCF input version NTP client input version


EN

GLIS

H

Description of available information and settings

► The table below shows the available features depending on the type of synchronisation

input.

DCF/GPS NTP

Type Series of fixed characters including the type of synchronisation (DCF or NTP). The GPS antenna transmits from the DCF.

Offset to

internal time Not available

Time offset between the input and the

management interface estimated at the last NTP

responses. The management interface integrates

the NTP client.

State

Indicates the status of the synchronisation source and the date of the last status

change.

• Ignored ([offset]) ► time input is ignored due to a leap

• Selectable ► time input is ready to synchronise with the time server

• Not selectable ► time input is not ready to synchronise with the time server

• Error ► time input is failing

Allow this leap Checking this box confirms the time difference between this input and the time server.

See section 3.7. Time input instability detection for more information.

Ignore this input Checking this box ignores the synchronisation input. In the case of an NTP input, it

also disables the NTP client. This causes the server to go into alarm, and “NO TIME

CODE” is displayed on the LCD display.

Automatic

stratum Not available

Activates the automatic configuration of the stratum value.

If enabled, the stratum value is calculated based

on the stratum value received in NTP packets.

Stratum Field for manually setting the

stratum value of the NTP server.

Value from 1 to 16.

Field for manually setting the stratum value of the NTP server.

Value from 1 to 16.

If the option “Automatic Stratum” is checked, this field is hidden.

Unsynchronization

threshold

Maximum time jump allowed on the input to remain synchronised to it (value in microseconds). The desynchronisation produced by a time jump above this threshold temporarily invalidates the time input, which currently only allows alarms to be generated. The resulting desynchronisation only lasts a few seconds. During desynchronisation, if the server has a non-zero configured autonomy, it continues to provide time as if there had been no jump. Otherwise, it stops providing time.

Trust frequency if

no date When this box is checked, the time entry is still selectable if the time information is no longer received (but was) but the frequency information is still received.


Options

Maximum autonomy when synchronization is lost

► If the time source is lost, the server can function autonomously. When the autonomy time is exhausted, the server stops providing time to its outputs. The autonomous operation time can be set here or replaced by “-1”, “disable” or an empty field to disable the autonomy limit.

Manual setting of the leap indicator

► Allows you to tell the time server that a leap second is announced on the following 31st

December or 30th June so that it can apply the second at the right time and issue a leap

second indicator (LI) to its NTP and DCF outputs. This indicator will be active one day

in advance for NTP and one hour in advance for DCF and will be automatically rest on

1st January or 1st July.

► When “Unset” is selected, the time server uses the information received from its time

input. In this configuration and without any information received from its time input it

does not apply a leap second and emits the “Unknown (unsynchronised)” indicator.

Some NTP clients refuses to synchronise when the indicator is “Unknown (unsynchronised)”.

Note: if the server no longer has a synchronisation source but still has enough battery life left, or is configured to be in free running mode, it will inset the programmed leap second and reset the indicator.

► Return to "No additional second" ➔ After the leap second is applied, the indicator is

automatically reset to “Unset” by default. Check this box to reset the indicator to “No

additional second” instead of “Unset”.


EN

GLIS

H

► Input Leap Indicator ➔ Gives the status of the leap second indicator derived from the

synchronisation input.

► Output Leap Indicator ➔ Gives the status of the leap second indicator sent from the

time outputs.

5.2.9. "Output" page

This page shows the output cards detected on the LEDI® NETWORK TDS and allows them

to be configured one by one.

The extension cards appear in a table at the top of the page.

► The different types of card are:

NAME

Description of card

NTP NTP output (V2, V3, V4): Unicast, Multicast, Broadcast

IRIG Output 1 x AFNOR NFS 87500/IRIG B (Modulated 1Khz)

POLAR PULSE Serial polarised pulse output


► Each detected card has its own configuration page which can be accessed by clicking

on the box containing the card’s name.

► The box with the thicker edges is the one currently displaying the configuration settings.

► The boxes also indicate the availability of the cards on the internal bus. A green

coloured box indicates that the output card is communicating properly with the main

card. A red coloured box indicates that there is an internal communication issue. In this

case, the card settings are not readable, and it is very likely that the card is not providing

the time code on its outputs.

In case of no internal communication with the output card, the front screen displays the

message “Output Alarm!”. If this issue persists over time or after restarting the device,

please contact Gorgy Timing Customer Service.

The previous image shows the configuration page of a 4 IRIG output card. It contains

information common to all the output cards: its address (internal to the rack), its type and its

firmware version (here the 4/1350 version of the 4AFN firmware).

Common standard options

The following image shows the information fields common to the configuration cards. All or

part of these fields can be found on each card configuration page.

Selected output

► Sends the card’s addresses on the internal communication bus. Also corresponds to the

physical location number of the output card.

Disable the output card

► All outputs can be disabled except the ALARM card. Disabling cards will have the

following effects:


EN

GLIS

H

CARTE Effects

NTP The output card will no longer respond to NTP requests.

IRIG The 1kHz carrier will be present but will no longer be modulated.

POLAR PULSE Polarised impulses will no longer be generated.

UTC (Time zone)

► Under normal operating conditions, the unit’s internal time is UTC. In order to send the

local time on the outputs, it is necessary to first apply an offset to UTC. This offset is

configurable in 2 fields.

► The first field allows you to select the sign of the offset (negative ‘-’ or positive ‘+’)

and the number of hours (from ‘00’ to ‘12’).

► The second field allows you to select the minutes of the offset (from ‘00’ to ‘55’).

For example, the offset in France is “+01:00”.

Chapter 3.1. Time Zones gives details on how time zones work.

DST (Daylight Saving Time)

► Besides UTC, some countries have summer/winter time changes. This must be set in

order to obtain local time. When summer/winter time changes are applied, there are two

“types” of time in the year:

- Summer time (UTC + 1 hour)

- Winter time (UTC)

► The table below details the available policies:

DST Start End

European Union Last Sunday of March at 1am UTC Last Sunday of November at 1am UTC

USA / Canada / St. Johns/ Bahamas / Turkey / Caicos Islands

Second Sunday of March at 2am local

time

First Sunday of November at 2am local

time

Australia – Standard First Sunday of October at 2am local time First Sunday of April at 3am local time

Example: in France, the DST policy is the “European Union” policy


Specific options

Certain output cards have their own specific configuration options.

AFNOR/IRIG-B

Choose your output time zone and frame format: AFNOR NFS 87500, IRIG-B 122, IRIG-B

123, IEEE 1344 or IEEE 1344 + binary second.

NTP

The ports of the NTP output cards integrate the same network interfaces (minus the NTP

client) as the management port on their own network interfaces. They can be accessed by

clicking on the IP addresses in the output Web page. However, the information and settings

available on an NTP output port are for that output only, and therefore may differ from port

to port. The operation of their network configurations is also identical to the management

port of the LEDI® Network TDS.

☛ See section 5.2.6. “NTP Page” for more information.


EN

GLIS

H

POLAR PULSE

► Alarm: alarm indicator (power, open serial circuit, parallel short-circuit).

► Output time: displaying the time sent to impulsion clocks.

► Period: impulsion selections every 30 or 60 seconds.

► Impulsion Duration: adjustment of the impulsion duration in quarters of a second.

► 12/24 Hours Format: allows the selection of the time format distributed to the

standard 0 to 23 hours (digital clocks|) or to the standard 1 to 12 hours (analogue

clocks).

► Relative Correction: allows you to add or subtract a number of impulses from 1 to 9

without modifying the time sent (example of application: polarity adjustment).

► Absolute Correction: adjustment of the distributed time on impulsion clocks.

Start-up procedure:

► Check the box “Disable the output card” and then press “Save Settings” to stop

pulse from being generated.

► Connect the clock line to the back slot.

► Set the offset and the DST policy.

► Set the period, pulse duration and format.

► Note the hour and minute displayed by the receiver clocks.


► Uncheck the “Disable the output card” box and press “Save Settings” to start the pulse

generation in high-speed (1 pulse every 2 seconds) or put it on hold if the time catchup

is too long (this time depends on the format and the 30 or 60 second mode). High-speed

(or standby) will be automatically stopped when the distributed time is equal to the time

base shown on the front panel display and corrected for any local time offset.

☛If an impulsion is shifted, adjust the polarity by selecting +1 or -1 in the “Relative

Correction” field and then press “Save Settings”.

5.2.10. "Interface" Page

On this page you can configure the various management interfaces of the LEDI® NETWORK

TDS.

A. User Accounts

This section allows you to configure the user accounts in order to limit access to the LEDI®

Network TDS.

Disable root account

► By default, the LEDI® Network TDS has a root account to connect to the server.

This account can be disabled to ensure maximum security. The only way to access

the server then is through the administrator account, which is defined in the next

field group. If the password for the administrator account is not known, the only way

to regain access to the server is to return to the default settings. All changes to the

settings will be lost and the root account will be reactivated.

Change admin/user password

► Check this box to modify the username

and password for the administrator

account.

The default administrator account credentials are:

Username: admin Password: password


EN

GLIS

H

B. Front LCD

Local time on front LCD

► Checking this box displays the local time on the front panel, otherwise it displays

UTC time.

If this box is checked, the time zones must be set. See chapter 3.1. Time Zones for

more information on the operation of time zones.

Custom LCD message

► If a custom message is written in this field, it will be displayed on the third line of the

LCD/OLED display. When an alert message appears, it will be displayed alternately

with the custom message.

Enable the front panel menu

► If enabled, the front panel menu will be accessible via the “OK” button. This menu

allows any user to configure the network settings of the Ethernet interface and to

restart it.

When this box is unchecked, the following setting is displayed:

Enable the IP addresses display

► If enabled, the IP addresses of the main Ethernet interface will be displayed by

pressing any of the arrow buttons. This setting is only available if the front panel

menu is disabled.


C. Other interfaces

HTTP(S) support

► Use this page to restrict access to the Web page to HTTP requests only, HTTPS

requests only, or both.

Users can provide their own security certificates for HTTPS.

To do this, two ssl.cert and ssl.key files must be placed in the .cfg folder at the root of

the embedded file system accessible via FTP or SCP. For example, in FTP with the

windows command prompt this procedure allows a certificate to be imported:

1. In the Start menu, type “cmd” in the search field and then launch cmd.exe

2. Enter the command cd <location>, where <location> is the path to the folder

containing the ssl.cert and ssl.key files

3. Enter the command ftp <<address>, where <address> is the IP address of the

module onto which you want to install the certificates

4. Enter login (default login: root)

5. Enter password (default password: gtmt)

6. Enter command cd .cfg

7. Enter command put ssl.cert

8. Enter command put ssl.key

9. Enter command quit

The image below shows the messages displayed. Here, the certificate files are in :\Users\

xgerault\Certificates and the IP address of the module is 192.168.0.128.


EN

GLIS

H

Enable Telnet console

► Disables the Telnet server if unchecked. The Telnet interface is described in section F.

Telnet interface and SSH in section 5.2.10. “Interface” page.

SSH Support

► Enables/disables password and/or username access to the SSH server. The SSH

interface is described in section F. Telnet interface and SSH in section 5.2.10.

“Interface” page.

Enable FTP server

► If enabled, file transfers between the product and other machines on the same IP

network are possible using FTP.

Enable ENDMI protocol

► If enabled, this protocol allows GTNetworkManager 2 and GT SCADA software to

discover this product over the IP network.

Enable the front panel menu

► If enabled, the main menu can be accessed on the front panel LCD display by pressing

the “OK” button (see Chapter 4.4. IPv4/IPv6 configuration).

► If disabled, pressing the “OK” button will be ignored. Users will no longer be able to

access the main menu of LCD display and change the IPv4/IPv6 settings from this

menu. These changes can only be made from the web server. A padlock icon will appear

in the top right corner of the screen.


D. File system

Files can be exchanged via FTP and SCP with the following Ethernet interfaces:

► LEDI® Network TDS management and

► NTP output

On each Ethernet interface the storage space is limited to 1472kb. The files are stored even

if the power is switched off. They are not deleted when returning to factory settings.

The following files are generated by the LEDI® Network TDS:

► .cfg/GT_Config.toml: configuration file generated with the command

generate_conf_file in Telnet or SSH

► .cfg/GT_Config.log: application log file of the last configuration file received by the

Ethernet interface

The following files affect the LEDI® Network TDS:

► GT_Config.toml: configuration file to be applied, automatically deleted once application

is complete.

► .cfg/ssl.cert: SSL certificate used by the HTTPS server when starting the Ethernet

interface.

► .cfg/ssl.key: SSL key used by the HTTPS server when starting the Ethernet interface.

► .ssh/authorized_keys: 2048-bit RSA public key of the user of the SSH server.

► image.bin: firmware to be loaded into the Ethernet interface.


EN

GLIS

H

E. SNMP Interface

The LEDI® Network TDS firmware incorporates an SNMP manager supporting versions 1,

2c and 3.

The SNMP manager mainly includes the variables described in thee MIB file

Gorgy_NTP_Srv_v2.mib. This file can be found on the CD-ROM supplies with the product in

the SNMP-Private-MIB-files folder. This MIB describes the contents of the folder with the

OID iso.org.dod.internet.private.enterprises.gorgy.software.ntpRangeProduct.

All information from the classic branch “.iso.org.dod.internet.mgmt.mib-2” is also available

for Gorgy Timing products. Among this information, the variables “sysContact”, “sysName”

and “sysLocation” in the “system” folder can be configured on the product via the other user

interfaces (website, Telnet and SSH).

Variable changes are limited to SNMPv3.

“DeviceSettings” Section

This section allows the user to change the configuration of the unit using the SNMPv3 agent

as an interface.

Its variables are organised in groups:

► Identification settings: the username/password for the administrator account.

► IP settings: IP configuration

► NTP settings: NTP servers used as a synchronisation source


To change a setting, the user must first change the relevant fields and then set the

applyXXXXXSettings variable (where XXXXX is the name of the setting group) to 1. No

changes will be applied to the unit configuration until the user activates the relevant

indicator.

Note: applying new IP settings will restart the main Ethernet interface of the LEDI® Network TDS

which also manages the synchronisation status of the time server.

In SNMPv3 the LEDI® Network TDS supports the HMAC-MD5-96 and HMAC-SHA-96

algorithms for authentication and the DES-CBC and AES-CFB-128 algorithms for data

confidentiality.

F. Telnet and SSH Interface

The LEDI® Network TDS and its NTP output cards feature a command prompt reachable by

Telnet (9999 port) and SSH (22 port). These commands can be used to read the status of

the server, its settings and to configure them.

In addition to the features offered by the Telnet protocol, the SSH protocol includes

authentication and data confidentiality through encryption. The LEDI® Network TDS SSH

server is compatible with:

► The key exchange methods "diffie-hellman-group-exchange-sha1", "diffie-hellman-

group14-sha1" and "diffie-hellman-group1-sha1",

► The hash-based message authentication codes (HMAC) "hmac-sha1" and "hmac-md5",

► The encryption algorithms (cipher) "aes128-cbc", "aes192-cbc", "aes256-cbc" and

"3des-cbc" and

► The 2048-bit “ssh-rsa” user keys (file imported on the product).

For more information about Telnet and SSH protocols, see

https://en.wikipedia.org/wiki/Telnet and https://en.wikipedia.org/wiki/SSH_(Secure_Shell)

G. Command prompt

Accessing the command prompt

The command prompt can be opened by several applications, e.g. Telnet, SSH, Putty and

Teraterm.

A username and a password are required to access the product. These are root/gtmt if the

root account has not been disabled or configurable user account credentials

(admin/password by default).

https://en.wikipedia.org/wiki/Telnet

https://en.wikipedia.org/wiki/SSH_(Secure_Shell)


EN

GLIS

H

It is also possible to log in with a public key. This key and its private key can be generated

with the “ssh-keygen” command under Linux or Cygwin under Windows in

“$HOME/.ssh/id_rsa.pub” (public key) and “$HOME/.ssh/id_rsa” (private key). Cygwin needs

the openssh package to run “ssh-keygen”. The file containing the public key (id_rsa.pub)

must then be copied to the server via the FTP or SCP in the “.ssh” folder with the file name

(authorised_keys”. Only one 2048-bit RSA key is supported by the server.

To reduce the risk of network attacks, SSH clients store the SSH servers they have

accessed. A warning message should appear the first time a server is connected or in the

event of a computer attack involving server identity theft. The user is then given the choice

of whether or not to access the server and whether or not to let the SSH client memorise the

server.

► Under Windows

To connect to a Gorgy Timing product via Telnet, run cmd.exe and enter “telnet <IP>

9999” replacing <IP> with the IP address of the product.

For the SSH protocol, there is no application included in Windows. You will need to install a

client such as Putty or Teraterm. If requested by these applications, the SSH connection

settings are:

SSH version 2 (or SSH2)

Port TCP 22

► Under Linux

To connect to a Gorgy Timing product using SSH, launch a terminal and enter ssh

<username>@<address> with the username and IP address of the product. The key

exchange method, authentication code and encryption algorithm can be forced

independently by inserting the following options between “ssh” and the username:

“-oKexAlgorithms=<method>” for the key exchange method,

“-m <code>” for the authentication code, and

“-c <algorithm>” for the encryption algorithm.

When authenticating with a key, if the error “Agent admitted failure to sign using key”

appears, run: eval "$(ssh-agent -s)" && rm ~/.ssh/known_hosts && ssh-

add


Using the integrated command prompt manual

The manual can be displayed with the “help” and “man” commands. These 2 commands

have the same effect.

If no command is given, they display the main page of the manual. If a specific page name

is given, they display the corresponding page of the manual.

There are 2 types of manual pages:

► Command manuals (one page per command)

► Manuals with names from other pages.


EN

GLIS

H

Use of status commands

The status commands display the state of a time server element. Some commands use

arguments to specify their functioning. For instance, to know if the NTP input is enabled:

Use of configuration commands

Most of the configuration commands can be used as status commands to display the current

value of a setting.

To modify a setting, the new value must be given at the end of a command. For instance, to

disable the NTP input:

Displayed warnings

In interactive mode the warnings listed may appear either at the login on the welcome

message or on a new line. If a command has been launched when a warning should appear,

the warning is only displayed after the result of the command is displayed.

Re-connection to the web interface in 1 minute…

The Ethernet interface is rebooting.

Updating firmware


This Ethernet interface is recording its new firmware in flash.

Restarting the product with the RESET button or with a power failure and an empty battery makes the time server unusable.

Firmware corrupted


Please reupload a firmware.

The flash firmware in this Ethernet interface is corrupted.

Restarting the product with the RESET button or with a power failure and an empty battery makes the time server unusable.

The firmware must be reuploaded to this interface to replace the corrupted firmware.

> sync_input ntp en

true

> sync_input ntp en false


H. File transfer

The SSH protocol can also be used to transfer files between the product and other devices

on the same IP network.

Under Windows

There is no application included in Windows to allow you to transfer a file from/to a Gorgy

Timing product via SSH. You will need to install a client such as Putty.

With Putty: run cmd.exe then type pscp <src> <dst> replacing <src> with the path of

the source file and <dst> with the destination path. The path on the Gorgy Timing product

should be written as follows: <user>@<IP>:FLASH0/<path> replacing <user> with the

username used on the product, <IP> with the IP address and <path> with the path of the

desired file/folder. For example, to import the key of an SSL certificate on a product:

pscp ssl.key [email protected]:FLASH0/.cfg/

Under Linux

To connect to a Gorgy Timing product in SSH, launch a terminal and enter scp <src>

<dst> replacing <src> with the path of the source file and <dst> with the destination path.

The path on the Gorgy Timing product should be written as follows:

<user>@<IP>:FLASH0/<path> replacing <user> with the username used on the product,

<IP> with the IP address and <path> with the path of the desired file/folder. For example, to

import the key of an SSL certificate on a product:

scp ssl.key [email protected]:FLASH0/.cfg/

I. "Restart" Button

Use the Restart button at the bottom of the page to restart the device remotely via the Web

page. After pressing the button, the device will be unavailable for about 1 minute until it has

finished rebooting.


EN

GLIS

H

5.2.11. Update

☛ WARNING: After a firmware update, the product may revert back to factory

settings depending on the update. Its IP configuration will therefore revert to DHCP

For each network port on the server, follow the NETWORK MODULE UPDATE PROCEDURE

below.

Note: To speed the process up, it is possible to launch the module update at the same time

(automatically or by making use of waiting times).

Please read the “WARNINGS” note carefully.

► Update via FTP interface

This method is generally used for problem solving or when then Web page interface is

inaccessible.

The FTP interface must be enabled in the device settings to carry out this operation.

1- Open a machine (Start menu → Run → “cmd”)

2- In the terminal, with the command “cd <location>”, change the folder for the one

containing “image.bin” file to be sent to the product

3- Type “ftp <module IP address”, ENTER

Username: “root”

Password: “gtmt”

4- Type:

"bin", ENTER

"put image.bin", ENTER

"quit", ENTER

The image below shows the exchanges observed. Here, the image.bin files is on the

desktop (C:\Users\jappaix\Desktop) and the module IP address is 192.168.0.22.


5- Wait for the module to restart, do not switch it off until it has completely rebooted.

6- In the terminal, with the “cd” command, change the folder to the one containing

the firmware (the “image.bin” file which is about 2MB) to be sent to the product.

7- Type "ftp <IP module address>", ENTER

Username: "root"

Password: "password"

If the password is rejected:

- Type "quit"

- Resume step 8 with the password "gtmt"

8- Type:

"bin", ENTER

"put image.bin", ENTER "quit", ENTER

9- Do not switch off the module before it has finished restarting.



EN

GLIS

H

► Updating the SSH interface

The SSH interface must be enabled in the device settings to carry out this operation.

1- Open a terminal (Start menu → run → “cmd”)

Type "pscp <firmware path> root@<module IP address>:/", ENTER

If PSCP is not available, install the Putty packet which is downloadable from:

https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html then repeat step 2.

Password: “gtmt”

9- Do not switch off the module before it has finished restarting.


☛ WARNINGS

Do not use or attempt to operate the product once the update has been initiated.

More specifically, do not interrupt the product’s functioning or reboot it during the

update. The device will reboot on its own when required.

Please also make sure to secure the power source(s) before and during the update.

The product can be used again when the Web pages can be loaded again in the browser and

the Up Time information displayed on the Index page is more than 1 minute.

During the update, the product will reboot once or twice. Theses reboots trigger the

reset of the Up Time. Therefore, the value displayed on the Index page must be

coherent with that information.

When in doubt, please wait 5 minutes before rebooting the product. This duration

corresponds to the approximate time needed for two secured product reboots

following an update.

Ignoring the recommendations above may result in corrupting the network cards (NTP

output cards or main/management Ethernet port). The related repairs will be billed

and are not covered by the warranty.


5.2.12. "Diagnostics" Page

The Diagnostics Web page can be accessed at <IP>/html/_diag.html.

Use this page to obtain diagnostic information and to launch tests on the associated network

module.


EN

GLIS

H

NTP statistics

► NTP Requests received indicates the number of queries received by the network

module since start-up.

► NTP Requests rejected indicates the number of NTP requests rejected by the network

module since start-up.

► NTP Requests served indicates the number of responses sent by the network module

since start-up.

The number of requests being processed is equal to the number of requests received minus

the number of responses minus the number of rejected requests.

Time corrections

This section provides a table logging time leaps over one second per synchronisation input.

► Date is the internal date before the leap.

► SRC is the IP address of the NTP server or the synchronisation source number at the

time of the leap.

► Offset is the new time minus the old time.

► Uptime is the server running time at the time of the leap.

NTP Configuration watcher

► This part is exclusively used by Gorgy Timing. It is not supported in the provided

software.

SCP Time Logging

► Enable SCP Logging enables the detailed logging of NTP responses by the client on an

SD card.

► Requests trains recorded is the number of recorded exchanges.


Memory management

► The Allocation Test button triggers the display of the volatile memory available on the

network module.

► Additional allocation size is the number of available bytes removed from the volatile

memory on the network module by the Allocate button.

► Size to allocate is the number of bytes to be removed from the volatile memory available

on the network module by the Allocate button.

► The Allocate button allows you to reduce/remove the amount of volatile memory

available on the network module.


EN

GLIS

H

6. APPENDIX A – CONNECTIONS

This section contains a description of every possible connection on the LEDI® NETWORK

TDS. All the connections are made at the back of the device.

The table below details the available equipment for each input/output port of the device as

well as the number and location of the useful signals.

Connector / Signals Connections

Management and NTP

input/output RJ45 plug

DCF/GPS input Antenna

AFNOR NFS 87500 / IRIG-B

Output

4 point screwed terminal

2 identical signals

No polarity

POLARISED IMPULSTIONS

Output

4 point screwed terminal

2 identical signals

No polarity


6.1. INSTALLATION VIEW

You can use the table in this appendix to obtain a summary view of all the GT products that

you have installed.

Description of the installation

Date of installation

Who carried out this installation?

Device designation Serial number Serial number


EN

GLIS

H

Device designation Serial number Serial number


6.2. DCF-GPS ANTENNA

External dimensions of the casing:

Height: 150mm - Width: 80mm - Depth: 50mm

Ip 54

► Install away from interference sources such as neon lights, computer screens etc…

6.2.1. DCF Antenna Part number: 3D6 (4 meters cable included)

Receipt frequency: 77.5 KHz

► Install the antenna vertically, then rotate it to

get a flashing light at the rhythm of one flash per second

and an extinction every minute (in theory, the antenna has

to be positioned facing the direction of the transmitter

located near Frankfurt in Germany).

☛ The antenna must be placed outside the building

to optimise the radio signal reception.

☛ If the conditions are right, the receiver time

setting requires less than 4 minutes.

☛ In case the time is still not set after fifteen

minutes, it is recommended to look for another location for the antenna.

DCF antenna characteristics

► Max connection length per shielded two-wire cable: 100 metres

► Maximum distance from the DCF transmitter (Frankfurt – Germany) or TDF transmitter

(Allouis – Cher (France)): 2000km

(Distance may decrease depending on the surrounding terrain and the current atmospheric

conditions)


EN

GLIS

H

6.2.2. GPS antenna (converter unit)

Part number: 3G and 3G1 (10m cable included)

► The antenna must be placed outside and at the top of the building so as to get the widest

possible reception angle.

☛ Any building or mound that is more than 5 degrees above the horizon line may

obscure one or more satellites, thus reducing the antenna performance.

☛ Although only minimally disrupted by other systems, the antenna should not

be installed directly under a radar.

► Install the antenna vertically. No specific orientation is required.

► The green light should flash every second to indicate that at least one satellite is being

detected. The green light will light up for 0 to 200ms depending on the number of

satellites detected.

► The red light starts flashing every second once the GPS system receives the time

indication. The length of time the red light lights up for depends on the bits transmitted

in DCF77 format (100ms for “0” and 200ms for “1”, no flashing at second 59).

► In certain cases (before 2018), the flashing of the green and red LEDs could overlap

generating an “orange” light.

► The GPS code is taken into account if the number of satellites is more than 2.

► If after receiving the number of satellites remains less than 3, the DFC code is stopped

after 20 seconds.

► The receiver should be set to the correct time within 12 and 15 minutes.

► If the time is not set after half an hour, disconnect and reconnect the antenna.


► 3G1 antenna time shift configuration switch

SW1

without

DST

DST

TIME OFFSET

US

EU

AU

1/2h

+

-

8h

4h

2h

1h

Positions

1

2

1

2

1

2

1

2

3

4

4

5

6

7

8

OFF

X

X

X

X

X

ON

X

X

X

X

X

X

X

X

X

X

GPS antenna characteristics

► Maximum length of each screened two-core cables: 100m

► Works anywhere in the world.

6.3. AFNOR-NFS-87500 / IRIG-B OUTPUT

The AFNOR-NFS-87500 / IRIG-B time code is delivered through a 4-pin connector.

A signal is available between the 1st terminal (left) and the second terminal. A second signal

identical to the first one is available between the 3rd and 4th terminal (right).

6.4. SERIAL IMPULSION OUTPUT

Impulsion signal is delivered through a 4-pin connector.

A signal is available between the 1st terminal (right) and the second terminal A second signal

identical to the first one is available between the 3rd and 4th terminal (right).


EN

GLIS

H

7. APPENDIX B – OUTPUT CODES FORMAT

7.1. AFNOR/IRIG-B NFS87500

The IRIG standard consists of a family of serial time codes whose formats contain up to 4

expressions of binary codes transmitting date and time information. There are 6 code formats

with different pulses. Among these 6 code formats, each signal is identified by digits that

describe its characteristics (transmission speed, modulation, carrier and coded expression.

IRIG-B is the most common in industrial equipment. It transmits information at 100 pulses

per second.


Frame format


EN

GLIS

H

Bit encoding

Receiver clocks connected to the line receive a complete time message every second. The

2 main signals are transmitted on a modulated or DCLS version. The signal is modulated

only on card ‘B’. The output signal of card ‘T’ is a TTL signal. The modulated signal reaches

a peak of 2.2V. The TTL signal changes from 0V to 5V.


7.2. DESCRIPTION OF DCF AND TDF TIME CODES

The DCF77 time signal is a long-range radio wave signal transmitted by the PTB

(Physikalisch-Technische Bundesanstalt) in Germany. The power of the DCF77 is about

30kW, which allows it to broadcast throughout Europe. The carrier has a very stable

frequency of 77.5kHz, amplitude modulated, and BCD (Binary Coded Decimal) coded.

The carrier is modulated with 24V pulses (1 per second). The duration of a pulse reflects the

level of the received bit:

► 100 ms represents one bit at 0;

► 200 ms represents one bit at 1.

The time signal is emitted by a one-minute frame divided into 60 pulses (the 59th corresponds

to a zero pulse to give the start of the frame). The frame contains the values of minutes,

hours, days, months, years and other parameters such as the leap second.


EN

GLIS

H

Details of the message transmitted over a minute:

Key:

J current day

JF public holiday

ES emergency transmitter used

E/H indicates a seasonal time change at the passage of the next hour

HE summer time

HH winter time

P1, P2, P3 Parity bits


7.3. POLARISED MINUTE PULSES

The server transmits a 24V impulse signal on a specific electric cable in series or in parallel

to the receiving clock. It delivers a current of 1A for clocks that use an average of 8mA. The

pulse output is active as soon as synchronisation is effective. On this output, it is also

possible to deliver a 24V DCF frame via a 1 pair cable.

► “Output” Page


EN

GLIS

H

Single pair cable

The configuration of the pulse output in series or parallel is done directly on the output board.

In parallel In series


8. APPENDIX C – MAINTENANCE

8.1. CARD REPLACEMENT + IMPULSION CARD POWER SUPPLY

Tools:

► Torx T15 screwdriver: front face (rack) or top plate (case)

► Torx T10 screwdriver: lid (rack) + front face (case) + output cards

► 5.5 wrench for M3 bolts: output cards + impulsion card power

► Unplug power

► Remove the four M3.5 screws from the front face

► Remove the six M3 screws from the lid

► Replace the defective card.


EN

GLIS

H

8.2. MICROCONTROLLERS REPLACEMENT

Tools:

► Torx T15 screwdriver: front face (rack) or tip plate (case)

► Torx T10 screwdriver: lid (rack) + front face (case) + output cards

► PLCC extractor: microcontroller

► Gorgy Timing reference: CIS8951RC2P

► Unplug every cable at the back of the product

► Remove the four M3.5 screws from the front face

► Remove the six M3 screws from the lid

► Use the PLCC extractor to remove the microcontroller

► Insert the new Microprocessor, making sure to match the indexing slots

☛ On one side of the micro there is a point (marked 1). Make sure that the support

arrow (marked 2) is on the same side as the point.

Note: the system has 2 indexing slots:

The bevelled corner of the micro must face one of the bevelled corners of the support.


8.3. OUTPUT CARDS ADDRESSES SWITCHES

Each LEDI® NETWORK TDS output card has an address which must be unique. These

addresses are determined by switches on each output card. When replacing/adding a new

card, the user must ensure that the cards’ addresses are unique.

Below is a recapitulative table of the addresses depending on the switches’ positions:

Output 1

(closest to the power supply card)

Output 2

Output 3

1 output

2 output

3 output

► Switches are read in a binary format. Each switch is a power of 2


EN

GLIS

H

8.4. TOP AND IRIG-B DCLS TIME CODE OUTPUT SIGNALS

TOP and IRIG DCLS output cards can provide several signal formats:

► TTL

► Differential TTL (RS422)

► Phototransistors or static relays, depending on the card type.

Signal format For each output

Switch 1 Switch 2 Switch 3

Phototransistor or

static relay ON (Right) ON (Right) ON (Right)

RS422

differential TTL ON (Right) OFF (Left) OFF (Left)

TTL OFF (Left) OFF (Left) OFF (Left)


8.5. SUPERVISION PROTOCOLS

8.5.1. Syslog messages catalogue

The table below shows Syslog messages sent by the device.

Category Type Sent text

user (1) Informational (6) - A new configuration has been defined.

user (1) Informational (6) - A new configuration has been defined through the front panel.

user (1) Informational (6) - A new configuration has been defined through the Telnet interface.

user (1) Informational (6) - A new configuration has been defined in the \"Alarms\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"Inputs\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"Interface\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"Network\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"NTP\" Webpage

user (1) Informational (6) - A new configuration has been defined in the \"PTP\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"Output\" Webpage.

user (1) Informational (6) - A new configuration has been defined in the \"SNMP\" Webpage.

kern (0) Informational (6) - System has restarted, reason: Reset / Power Failure.

kern (0) Informational (6) - System has restarted, reason: User Request with Configuration Changes.

kern (0) Informational (6) - System has restarted, reason: User Request without Configuration Changes.

kern (0) Informational (6) - System has restarted, reason: Automatic for Configuration Changes.

kern (0) Informational (6) - System has restarted, reason: Firmware Update.

auth (4) Informational (6) - A Web interface has been accessed.

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 4: NTP client software start learning environment&network

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 5: NTP client software entering normal behavior

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 6: Not enough replies of current synchronization server

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 7: New server elected for synchronization

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 8: NTP server software is starting

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 9: The hardware is synchronized on its time reference

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 10: The hardware is not synchronized on its time reference

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 11: NTP server locked by the user

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 13: NTP server software is rescaling on its PPS source

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 14: NTP server software is rescaled on its PPS source

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 15: Failure: no more time code and the time base has no more autonomy

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 16: Warning: no time code. The time base has less than 3 minutes of autonomy

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 17: The hardware has never been externally synchronized

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 19: Power supply is running again

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 20: Input 1 is no more selectable

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 21: Input 2 is no more selectable

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 22: Input 1 is selectable

daemon (3) Notice (5) - A SNMP trap has been sent, with ID 23: Input 2 is selectable

daemon (3) Error (3) - An error occurred with the SD-Card.

daemon (3) Error (3) - Ethernet link connection.

daemon (3) Error (3) - Ethernet link error. Check the cable.

ntp (12) Error (3) - NTP Client with MAC address <MAC> from IPvX address <IP> has not requested any synchronization for <duration> hour(s).


EN

GLIS

H

9. APPENDIX D – TROUBLESHOOTING

This section provides answers to frequently asked questions about using your NTP device.

First of all, make sure that the GTNetworkManager2 software is installed on your computer.

I HAVE RUN A SEARCH USING GTNETWORKMANAGER2, BUT I CAN’T

DETECT A DEVICE!

► Check the cable connection. If the ETHERNET LEDs are visible, the LED at the top left

should light up green. Otherwise, there must be a network connection error or a power

issue.

► If you are using several VLANs (Virtual Local Area Networks), check that the device is

on the same VLAN as your computer.

► Connect your computer directly to the device using a direct cable. The device

automatically takes an IP address (format 169.254.x.y). Change the IP address of your

computer to this type by using a network mask 255.255.0.0.

I CANNOT OPEN THE CONFIGURATION WEBPAGE!

► Firstly, can GTNetworkManager2 detect the device?

➔ YES

Your computer and the device must have the same IP address and the same network

mask,

➔ NO

See the question above.

► Has the browser found the web page (loading begins, but fails after a while)?

➔ NO, PAGE CANNOT BE FOUND

If you are using “Internet Explorer”, go to:

Tools → Internet Options → Connections → Network Settings

The browser must not use a proxy. Clear all the check boxes.

➔ YES

The web page can be attached, but the browser is unable to load it. Open a TELNET

session:

Telnet <IP address> 9999

Login: root

Password: gtmt

Enter “factory_default”, refresh the web page.


THE CONFIGURATION WEB PAGE DOES NOT SHOW ANY OUTPUT?

► Press ‘F5’ to refresh the web page. Then return to the output panel. If the output still

does not appear, go to the next step.

► Open a TELNET session:

Telnet <IP address> 9999

Login: root

Password: gtmt

Enter “factory_default”, refresh the web page.

► If the output still does not appear, remove the server cover. Check the black cables are

connected correctly and switch the switches are configured (see Appendix C –

MAINTENANCE).

THE DISPLAY SHOWS “NO TIME CODE!”

► “NO TIME CODE!”: The device is not synchronised: check your time source.

► “no time code!” followed by the date: if your device receives the time code, check in

the input panel of the configuration web page that “Enable autonomous mode” is

unchecked.


EN

GLIS

H

GORGY TIMING SAS

Quartier Beauregard

38350 La Mure d'Isère (Grenoble France)

Phone: +33 4 76 30 48 20 Fax: +33 4 76 30 85 33

email: [email protected] - www.gorgy-timing.com

TECHNICAL SUPPORT

RADIO TIMING®, LEDI®, LEDICA®, HANDI® are trademarks by GORGY TIMING.

Statement number for training provider activity: 82 38 04877 38

GORGY TIMING RC 74 B 38 – Any technical, aesthetic, color modification may be made without prior notice.

DEPUIS LA FRANCE SUR UN POSTE FIXE :

[email protected]

mailto:[email protected]

http://www.gorgy-timing.com/

mailto:[email protected]

LEDI - Gorgy timing · MDE-LEDI-NETWORK-TDS-4099V1.0 1 [email protected] LEDI® NETWORK TDS...

Documents

Transcript of LEDI - Gorgy timing · MDE-LEDI-NETWORK-TDS-4099V1.0 1 [email protected] LEDI® NETWORK TDS...