Table of Contents Quick Start........................7 Network Timeserver with TCR synchronized time base..........8 The Modular System LANTIME...................9 Supported Network Services................11 Additional Features and Options................ 12 User Interface..................... 12 Options....................... 12 Why to use a Network Timeserver..............13 Network Time Protocol (NTP)..................13 NTP Target......................
Page 4
IRIG system configuration Bit 2 ... 0..............28 Menu Offset from UTC..................29 Menu IRIG Code....................29 Menu Simulation Mode..................29 Menu Initial Time and Date................29 The LANTIME configuration interfaces..............30 The web interface......................31 Configuration:Main Menu..................32 Configuration: Ethernet................... 33 Network interface specific configuration..............35 IPv4 addresses and DHCP..................35 IPv6 addresses and autoconf................
Page 5
Configuration: Manual.....................64 The Command Line Interface..................66 CLI Ethernet......................67 CLI Notification.......................70 Alarm events.......................70 E-mail messages....................71 Windows Popup Messages................. 72 SNMP-TRAP messages..................72 VP100/NET wall mount display................ 72 CLI Security......................73 Password......................73 SSH Secure Shell Login..................73 Generate SSL Certificate for HTTPS ..............74 NTP keys and certificates...................
Page 6
Technical Specifications TCR510................94 Signal description TCR510................96 Rear Connector Pin Assignments TCR510............97 Technical Specifications LAN CPU................ 98 Rear Connector Pin Assignments LAN CPU.............99 VGA, Keyboard Connector Pin Assignments............ 99 Technical Specifications Power Supply NLP65............ 100 Declaration of Conformity..................101 Manual VP100/NET Display configuration............
Quick Start When booting the system the following message will be displayed while dots will be counted up in the lower line:. MEINBERG TIMESERVER please wait..Main Menu will be displayed with some important status informations after booting has finished:...
Network Timeserver with TCR synchronized time base LANTIME (Local Area Network Timeserver) provides a high precision time base to a TCP/IP network (Stratum-1-Server). The NTP (Network Time Protocol) is used to synchronize all NTP clients with the reference. The several LANTIME variants differ from each other by the time reference.
The Modular System LANTIME LANTIME M300 is a set of equipment composed of a reference clock (e.g.: satellite controlled clock GPS167or Time Code Receiver TCR5xx), a single-board computer SBC LX800 500 MHz with integrated network card, and a power supply unit NLP65, all installed in a metal desktop case and ready to operate.
Page 10
The implemented NTPD distributes the reference time from the GPS receiver cyclic in the network. Information on the NTPD is monitored on the LC display or can be inquired via the network. The installation of LANTIME is very easy for the system/network administrator. The network address, the netmask and the default gateway have to be configured from the front panel of LANTIME.
Additional Features and Options - external NTP timeserver - free configuration of NTP: thereby MD5 authentication and access control via ad- dress & mask restriction - extended menu guidance for configuration and monitoring via Telnet, SSH or serial terminal interface - optional up to 3 RJ45/10/100 Mbit Ethernet interfaces - extended HTTP statistic support with long-term graphic and access statistic to - alarm messages can be displayed on external large display VP100/20/NET...
Why to use a Network Timeserver A network timeserver should be used if accurate time is essential for undisturbed operation. It is possible to synchronize computers in a network using Public Domain Time servers over the Internet, but there are good reasons not to use them: - The possibility to send notification via e-mail or SNMP-Trap to an administrator in the event of any synchronisation failure.
XP/2000/NT/95/98/3x, OS2 or MAC. The following WEB site is recommended to get the latest version of NTP: "http://www.eecis.udel.edu/~ntp/". More information you can find on our web page at "http://www.meinberg.de/english/sw/ntp.htm". NTP-Client Installation The following example shows the installation of a NTP client under UNIX. First make sure that there is no NTP installed on your computer because many UNIX operating systems include NTP already.
Page 15
The NTP daemon is started with "ntpd" or, using "rc.local", while booting the system. Status messages during operation are saved in /var/adm/messages and / var/adm/syslog (corresponding to the syslog configuration). e.g.: tail /var/log/messages shows the last lines from the file "messages" The status messages can also be redirected in a log file by using the following option: ntpd -llogfile The command "ntpq"...
IRIG receiver TCR510 The transmission of coded timing signals began to take on widespread importance in the early 1950´s. Especially the US missile and space programs were the forces behind the development of these time codes, which were used for the correlation of data.
AFNOR-Standard format Overview The Board TCR510 was designed for the decoding of unmodulated and modulated IRIG- and AFNOR-Timecodes. Modulated codes transport the time information by modulating a sinusoidal carrier signals amplitude whereas unmodulated signals employ a pulse width modulated DC signal. The receivers automatic gain control allows the reception of signals within a range from abt.
IRIG-signal. The DCF-Simulation is surpressed in this case. Time and date of the real time clock can be set by a Meinberg Standard Telegram via serial port COM0. Received IRIG-time can be re-calculated into UTC provided that no time zone changeovers such as daylight saving appear in the received IRIG- telegrams.
BCD time of year, SBS time of day A002: 1000 pps, DC Level Shift pulse width coded, no carrier BCD time of year B123: 100pps, amplitude modulated sine wave signal, 1 kHz carrier frequency BCD time of year, SBS time of day B122: 100 pps, amplitude modulated sine wave signal, 1 kHz carrier frequency...
( SMB ) to comply with the requirements of several systems. Meinberg IRIG-generators have an output impedance of 50 , to build a matched transmission system when using a coaxial cable. If such a generator is used to...
RAM disk after booting. Because of that it is guaranteed that the file system is in a defined condition after restart. This boot process takes approx. two minutes. During this time the following message appears on the display: MEINBERG TIMESERVER please wait..
Configuration User Interface There are several ways to configure the LANTIME parameters: Command Line Interface (CLI) via TELNET Command Line Interface via SSH Command Line Interface via serial interface terminal (BGT versions only) HTTP Interface Secure HTTP Interface (HTTPS) Front panel LCD Interface SNMP Management To put LANTIME into operation for the first time an IP address is entered via the front panel keys and LC display (refer to: DHCP IPv4 or AUTOCONF IPv6).
Configuration via LC Display On first installation of LANTIME the network parameters can only be configured by the front panels push buttons and the LC display. Press MENU until the SETUP menus appear on the display. The first setup menu are the LAN PARAMETERS. Pressing NEXT further setup menus appear.
The menus in Detail Root Menu The root menu is shown when the receiver has completed initialisation after power- up. With the four arrow buttons and the buttons „OK“, „ESC“, „F1“ and „F2“ the navigation and setting of parameters can be managed. Main menu can be reached by pressing „ESC“...
Page 26
The following main menus will be displayed when pressing the „UP“ and „DOWN“ arrow buttons: TCR: NORMAL OPERATION Thu, 20.07.2006 NTP: Offest PPS: 1ms 14:02:01 Referenz Clock TCR511 State: SYNC TCR511 :1.01 S/N: 024000000000 NTP State and Configuration NTP: Offest PPS: 1ms SETUP Parameter Configuration...
Menu: Reference Clock Information The Reference Clock menu and all its submenus will manage all status information and parameters of the reference clock (TCR5xx receiver). Reference Clock TCR511 State: SYNC TCR511 :1.01 S/N: 024000000000 This first menu will monitor the current state („sync“ or „not sync“). The next line will reflect the version number and the serial number of the TCR5xx.
IRIG system state: Bit 7 ... 0 Bit 7: Invalid UTC parameter Bit 6: TCAP exceeded, jitter out of range Bit 5: Lock on Bit 4: Telegramm error Bit 3: Data available Bit 2: Invalid sysconf Bit 1: Pulses enabled Bit 0: Warmed up Invalid UTC parameter: This bit is set to one if the checksum of the ‘Offset from...
Menu Offset from UTC In this menu the parameters of the IRIG-receiver can be set. The submenu „Offset from UTC“ lets the user set the offset from local time to UTC time. The IRIG-signal provided no information of the offset from UTC and the receiver has to generate this information for the NTP daemon.
The LANTIME configuration interfaces The LANTIME offers three different options for configuration and status management: Web interface, Command Line Interface Setup and SNMP. In order to use the SNMP features of your LANTIME, you need special software like management systems or SNMP clients. In order to use the web interface, all you need is a web browser (LANTIME supports a broad range of browsers).
The web interface Connect to the web interface by entering the following address into the address field of your web browser: http://198.168.10.10 (You need to replace 198.168.10.10 with the IP address of your LANTIME). If you want to use an encrypted connection, replace the http:// with https://...
Configuration:Main Menu After entering the right password, the main menu page shows up. This page contains an overview of the most important configuration and status parameters for the system. The start page gives a short overview of the most important configuration parameters and the runtime statistics of the unit.
Page 34
In the network configuration all parameters related to the network interfaces can be changed. In the first section you can change the hostname and domain name. You can also specify two nameserver and two SYSLOG server. In the nameserver and syslog server fields you may enter an IPv4 or IPv6 address (the syslog servers can be specified as a hostname, too).
Network interface specific configuration The interface specific parameters can be found in the Interface section. If your LANTIME is equipped with only one network interface, you will find only one sub section (Interface 0). Otherwise you see a sub section for each installed Ethernet port. Here, the parameters for the network port can be changed.
Examples: "::" is the address, which simply consists of zeros "::1" is the address, which only consists of zeros and a 1 as the last bit. This is the so-called host local address of IPv6 and is the equivalent to 127.0.0.1 in the IPv4 world "fe80::0211:22FF:FE33:4455"...
Additional Network Configuration You can configure additional network parameter like special network routes or alias definitions. For this you will edit a script file which will be activated every time after the network configuration will run. Also the Samba Configuration from „/etc/samba/smb.conf“ can be edited:...
Alarm events On this page you can set up different notification types for a number of events. This is an important feature because of the nature of a timeserver: running unobserved in the background. If an error or problem occurs, the timeserver is able to notify an administrator by using a number of different notification types.
Windows Popup Messages Most Microsoft Windows operating systems provide you with a local notification tool. You can send messages via the special Windows protocol in your local network. It is not necessary to enable the NETBIOS protocol of the LANTIME in order to use this notification.
User defined Alarm scripts You can define your own alarm script for every event by using the “Edit user defined notification script”. This script will be called automatically if one of the selected events occurs. This user alarm script will be stored on the Flash-Disk at “/mnt/flash/user_defined_notification”.
Password On the ““Security““ page you can manage all security relevant parameters for your timeserver. In the first section “Login” the administration password can be changed, which is used for SSH, TELNET, FTP, HTTP and HTTPS access. The password is stored encrypted on the internal flash disk and can only be reset to the default value “timeserver”...
SSH Secure Shell Login The SSH provides you with a secure shell access to your timeserver. The connection is encrypted, so no readable passwords are transmitted over your network. The actual LANTIME version supports SSH1 and SSH2 over IPv4 and IPv6. In order to use this feature, you have to enable the SSHD subsystem and a security key has to be generated on the timeserver by using the “Generate SSH key”...
Generate SSL Certificate for HTTPS HTTPS is the standard for encrypted transmission of data between web browser and web server. It relies on X.509 certificates and asymmetric crypto procedures. The timeserver uses these certificates to authenticate itself to the client (web browser). The first time a web browser connects to the HTTPS web server of your LANTIME, you are asked to accept the certificate of the web server.
NTP keys and certificates The fourth and fifth section of the “Security“ page allow you to create the needed crypto keys and certificates for secure NTP operation (please see NTP authentication below). The function “Generate new NTP public key“ is creating a new self-signed certificate for the timeserver, which is automatically marked as “trusted“.
Configuration: NTP The NTP configuration page is used to set up the additional NTP parameters needed for a more specific configuration of the NTP subsystem. The default configuration of the timeserver consists of a local clock, which represents the hardware clock of your LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronisation.
Page 48
interpreting the PPS (pulse per second) of the GPS reference clock. The default configuration looks like this: lantime # NTP.CONF for GPS167 with UNI ERLANGEN server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 12 # local stratum server 127.127.8.0 mode 135 prefer # GPS167 UNI Erlangen PPS fudge 127.127.8.0 time1 0.0042...
Page 49
The NTP Trusttime will specify the time how long the NTP will trust the reference time if this is not synchronized (free running). This time will be set in seconds or minutes or hours. The value 0 will be select the default value for the specific reference clock.
NTP Authentication NTP version 2 and version 3 support an authentication method using symmetric keys. If a packet is sent by the NTPD while using this authentication mode, every packet is provided with a 32 bit key ID and a cryptographic 64/128 bit checksum of the packet.
Page 51
The ntp.keys file mentioned above holds a list of all keys and their respective ID known by the server. This file should not be world-readable (only root should be able to look into this) and it may look like this: # ntp keys file (ntp.keys) 29233E0461ECD6AE # des key in NTP format...
NTP AUTOKEY NTP Version 4 supports symmetric keys and additionally provides the so-called AUTOKEY feature. The authentic of received time at the NTP clients is sufficiently ensured by the symmetric key technique. In order to achieve a higher security, e.g. against so-called replay attacks, it is important to change the used crypto keys from time to time.
Page 53
4 server time2.meinberg.de You find the server time.meinberg.de which is using the AUTOKEY feature, while time2.meinberg.de is used without any authentic checks. If you want to setup the LANTIME server as a trusted host, but need to use a different trusted authority, please create your own group key with this TA and include it with the web interface of your LANTIME (on page “Security Management”...
Page 54
Example: This autokey group is formed by one Stratum-1-server (B), two Stratum-2-servers (D and E) and a number of clients (in the diagram there are 4 clients shown, c1 – c4). B is the trusted host, he holds the group key and a self-signed certificate marked as “trusted”.
You should use this function only, if the NTPD has been synchronized to the internal reference clock for more than one day. This is done here at Meinberg directly before shipping the LANTIME unit to our customers, so you do not need to use this function during normal operation.
The first usage of “Save settings” will load the configuration from flash into memory and activate it. The point “Download SNMP MIB files“ can be used to download all Meinberg specific SNMP MIB files to your workstation. They can be distributed to all SNMP management clients afterwards.
Administrative Information The button “List all messages“ displays the SYSLOG of the LANTIME completely. In this log all subsystems create their entries, even the OS (upper case) kernel. The SYSLOG file /var/log/messages is only stored in the system’s ram disk, therefore it is lost after a power off or restart.
If you need to update the software of your LANTIME, you need a special file from Meinberg, which can be uploaded to the LANTIME by first choosing the file on your local computer with the “Browse” button and then press “Start firmware update”.
Automatic configuration check All parameters of the LANTIME can be checked for plausibility and all configured servers (e.g. SYSLOG servers, nameservers) are tested for reachability. All red coloured values should be reviewed by the administrator. Because all configured hostnames / IP addresses of the servers are processed during the reachabilitytests, the whole check process may take a while.
With the help of these informations the technical support from Meinberg can reproduce the current state of your Lantime. It takes some time to collect all information from the Lantime. Do not press the button again while this process is running - some web browsers will cancel the job if you press the button twice.
Statistical Information In the first section a graphical diagram shows the running synchronisation process. NTP is storing this statistical information in so-called “loopstats” files, which are used here to draw the curves. The red line is describing the offset between the internal reference clock (GPS) and the system clock.
Configuration: Manual This page gives you access to the documents stored on your LANTIME, especially the manuals and your own notes. The two lists include filename, language, file type, date and size of the documents/notes. The LANTIME documents can be downloaded from here in order to read / print them on your workstation.
Page 65
If you want to add a note (you can maintain more than one note on your LANTIME), after choosing the button “add note” you have to enter a filename (without a directory path, all notes are stored in a fixed directory on the flash disk of your LANTIME) and the language of your note first.
The Command Line Interface The command line interface (CLI) can be used within a TELNET or SSH session. After login, just enter “setup” to start the CLI setup tool. The start page gives a short overview of the most important configuration parameters and the runtime statistics of the unit.
CLI Ethernet In the network configuration all parameters related to the network interfaces can be changed. In the first section you can change the hostname and domain name. You can also specify two nameservers and two SYSLOG servers. In the nameserver and SYSLOG server fields you may enter an IPv4 or IPv6 address (the SYSLOG servers can be specified as a hostname, too).
Page 68
NETBIOS cannot be used over IPv6 in this version. IPv4 and IPv6 can be used together on one LANTIME. To manage the interface specific parameters, you can enter the Ethernet Configuration Line page by using one of the ETHERNET buttons. If your LANTIME is equipped with only one network interface, you will find only one button (ETHERNET 0).
Page 69
If the DHCP client has been activated, the automatically obtained parameters are shown in the appropriate fields (IPv4 address, netmask, gateway). You can specify up to three IPv6 addresses for your LANTIME timeserver. Additionally you can switch off the IPv6 AUTOCONF feature. IPv6 addresses are 128 bits in length and written as a chain of 16 bit numbers in hexadecimal notation, separated with colons.
CLI Notification Alarm events On this page you can set up different notification types for a number of events. This is an important feature because of the nature of a timeserver: running in the background. If an error or problem occurs, the timeserver is able to notify an administrator by using a number of different notification types.
Every event can use a combination of those four notification types, of course you can disable notification for events by disabling all notification types. The configuration of the four notification types can be changed in the upper section of the page, you can control which notification is used for which event by using the button “notification conditions”...
Windows Popup Messages Most Microsoft Windows operating systems provide you with a local notification tool. You can send messages via the special Windows protocol in your local network. It is not necessary to enable the NETBIOS protocol of the LANTIME in order to use this notification.
CLI Security Password On the “Security“ page you can manage all security relevant parameters for your timeserver. In the first section “Login” the administration password can be changed, which is used for SSH, TELNET, FTP, HTTP and HTTPS access. The password is stored encrypted on the internal flash disk and can only be reset to the default value “timeserver”...
If you enabled SSH, your LANTIME automatically is able to use secure file transfer with SCP or SFTP protocol. The usage of FTP as a file transfer protocol is as insecure as using TELNET for shell access. Generate SSL Certificate for HTTPS HTTPS is the standard for encrypted transmission of data between web browser and web server.
CLI NTP Parameter The NTP configuration page is used to set up the additional NTP parameters needed for a more specific configuration of the NTP subsystem. The default configuration of the timeserver consists of a local clock, which represents the hardware clock of your LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronisation.
CLI NTP Authentication Please see the corresponding chapter in the web interface description. CLI NTP Autokey Please see the corresponding chapter in the web interface description.
You should use this function only, if the NTPD has been synchronized to the internal reference clock for more than one day. This is done here at Meinberg directly before shipping the LANTIME unit to our customers, so you do not need to use this function during normal operation.
The function “Reset to factory defaults“ is setting all configuration parameters back to default values. The regular file /mnt/flash/global_configuration will be replaced with the file /mnt/flash/factory.conf, but first a copy of the configuration is saved under /mnt/flash/global_configuration.old for backup reasons. The default password “timeserver”...
If you need to update the software of your LANTIME, you need a special file update.tgz from Meinberg, which has to be uploaded to the LANTIME by using ftp, SCP or SFTP to the root dir (/update.tgz), after the file transfer is complete, press “Start firmware update”.
MD5 SHA1 Encryption support: By using the special Meinberg SNMP-agent all important status variables can be read with SNMP conformant client software. Where applicable, a variable is implemented as string and numeric value, for example allowing SNMP client software to use the information for drawing diagrams or monitor threshold levels.
Page 81
By using the standard MIB, no NTP get requests are allowed. Only the standard system and network parameters can be accessed (e.g. using the NET-SNMP command “snmpget”). Only by using the Meinberg MIB the change of configuration parameters is possible (the command “snmpset“ is used to alter a variable, for example).
Configuration over SNMP The LANTIME timeserver can be configured via several user interfaces. Besides the possibility to setup its parameters with the web interface (HTTP and/or HTTPS) and the direct shell access via Telnet or SSH, a SNMP based configuration interface is available.
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver1.0 = STRING: MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver2.0 = STRING: [...] To alter a parameter, with net-snmp you would use the snmpset command: root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de mbgLtCfghostname.0 string „helloworld“ MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: helloworld root@testhost:/# Please note that your SNMP request has to be sent with a sufficient timeout (in the above snmpset example this was achieved by using the “-t 10“...
Further configuration possibilities Because the timeserver uses a standard version of the net-snmp SNMP daemon (with extended features covering the timeserver-specific functions), all configuration parameters of the SNMPD can be used. The configuration file of the SNMP daemon is located at /usr/local/share/snmp after boot time, the filename is snmpd.conf. During the boot sequence, this file is created dynamically by using a template file and appending the SNMP parameters stored in the timeserver setup.
Page 85
(e.g. mail, winpopup, SYSLOG etc.). A few examples: (we are again using the snmpset command which comes with the net-snmp tools). root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de mbgLtCmdExecute.0 int 1 MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: Reboot(1) root@testhost:/# The command shown above is forcing the timeserver to reboot.
LANTIME SNMP traps mbgLantime.4 mbgLtCfg LANTIME configuration variables mbgLantime.5 mbgLtCmd LANTIME control commands Further detailed information can be found in the Meinberg MIB files. Reference of LANTIME SNMP configuration variables: SNMP branch Variable Data type Description mbgLtCfgNetwork mbgLtCfghostname string...
Page 87
SNMP branch Variable Data type Description mbgLtCfgNtpServer3KEY integer Link to the key which should be used for the third NTP-server mbgLtCfgStratumLocalClock integer(0..15) Stratum-value of the internal system clock of the timeserver mbgLtCfgNTPTrustedKey integer Link to the key which should be used for the internal reference time source mbgLtCfgNTPBroadcastIP string (IPv4 or IPv6-...
Page 88
SNMP branch Variable Data type Description mbgLtCfgNotify mbgLtCfgNotifyNTPNotSync Exactly one, none or a combination of string(combination the following notification types: email=sending an email wmail=sending a winpopup-message snmp=sending a SNMP-trap, disp=showing on wall mount display, syslog=sending a syslog-entry for the event „NTP not synchronized“ mbgLtCfgNotifyNTPStopped string (combination) (see mbgLtCfgNotifyNTPNotSync) for the event „NTP Daemon stopped“...
(-p is for output to stdout, -s would use the syslog for output). The corresponding MIB files can be found on the LANTIME at /usr/local/share/snmp/mibs/ , all Meinberg specific MIB files are named “MBG-SNMP….” . These MIB files can be downloaded by using the web interface (see “Local” page, “Download MIB files”...
SNMP Trap Reference All traps can be found under the mbgLtTraps section in the Meinberg MIB. A special trap exists for every notification event the timeserver knows. Please note that the traps are only sent if you configured the notification type “SNMP trap” for the event, otherwise no trap is generated.
Attachment: Technical Information Skilled/Service-Personnel only: Replacing the Lithium Battery The life time of the lithium battery on the board is at least 10 years. If the need arises to replace the battery, the following should be noted: ATTENTION! There is a Danger of explosion if the lithium battery is replaced incorrectly.
Safety instructions for building-in equipment This building-in equipment has been designed and tested in accordance with the requirements of Standard IEC 950 "Safety of Information Technology Equipment, including Electrical Business Equipment". During installation of the building-in equipment in an end application (i.e. rack) additional requirements in accordance with Standard IEC 950 have to be taken into account.
Rear Panel Connectors Name Type Signal Cabel 2x Network RJ-45 Ethernet shielded data line Time Sync Error relais screw terminal shielded koaxial line 10 MHz, shielded koaxial line Time Code In modulated 600 Ohm shielded koaxial line DCLS Optokopler shielded koaxial line power supply power cord receptable power supply cord...
INITIALIZATION: Initial time and date can be set by standard Meinberg telegram via serial port COM0 PULSE OUTPUTS: Pulse per second PPS, TTL-Level pulse, active high, 200 ms pulse width Pulse per minute PPM, TTL-Level pulse, active...
Page 95
9600Bd, 19200Bd FRAMINGS: 7E2, 8N1 OUTPUT CYCLE: Per second or per minute SERIAL TELEGRAM: Meinberg Standard Telegram REAR EDGE CONNECTOR: According to DIN41612, type C 64, rows a+c ( male ) POWER CONSUMPTION: VCC +5 V, abt. 300 mA VDD +5 V, abt. 50 mA with TCXO-HQ option Max.
Technical Specifications LAN CPU Geode TM LX800 with 500 MHz PROCESSOR: MAIN MEMORY: 256 MB CACHE-MEMORY: 16 KB 2nd Level Cache FLASHDISK: 64 MB (128 MB) NETWORK CONNECTOR: 10/100 MBIT with RJ45-Jack DAVICOM DM9102AEthernet NIC Controller SERIAL - INTERFACE: Four serial RS232-Ports 16550 compatible to FIFO - RS232 9-pol.
Rear Connector Pin Assignments LAN CPU VCC in (+5V) VCC in (+5V) VCC in (+5V) VCC in (+5V) VCC in (+5V) VCC in (+5V) PPS in /AFD out /STB out /ERR in /SLIN out /INIT out D5 in/out D6 in/out D7 in/out LPT1 D2 in/out...
Declaration of Conformity Hersteller Meinberg Funkuhren GmbH & Co. KG Auf der Landwehr 22 Manufacturer D-31812 Bad Pyrmont erklärt in alleiniger Verantwortung, dass das Produkt, declares under its sole responsibility, that the product NTP Timeserver Produktbezeichnung Product Name LANTIME/TCR Modell / Typ Model Designation auf das sich diese Erklärung bezieht, mit den folgenden Normen übereinstimmt.
Manual VP100/NET Display configuration send2display Version 0.1 usage: send2display -h hostname -s serialnumber [options] Valid options are: -h, --host H Uses H as the hostname of the display unit -s, --serialnumber S Uses S as the serialnumber of the display (e.g. 03A00C7F) -c, --clear M Clear message M (0-31)
Page 103
If you want the message (any type) to appear periodically, you can set the time in- terval with: -D, --periodday D Display message every D days -H, --periodhour H Display message every H hours -M, --periodminute M Display message every M minutes (You can combine these options.
Third party software The LANTIME network timeserver is running a number of software products created and/or maintained by open source projects. A lot of people contributed to this and we explicitly want to thank everyone involved for her/his great work. The used open source software comes with its own license which we want to mention below.
Network Time Protocol Version 4 (NTP) The NTP project, lead by David L. Mills, can be reached in the internet at www.ntp.org. There you will find a wealthy collection of documentation and information covering all aspects of the application of NTP for time synchronization purposes.
GNU General Public License (GPL) GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it.
Page 109
Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty;...
Page 110
making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the...
Page 111
the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
USB Stick Via front panel Lantime supports a USB connector to plug in a USB Memory Stick. This USB stick can be used for different tasks in combination with the Lantime: - Transfer configuration parameters between different Lantimes - Keypad locking for secure using the keypad of the LCD - Transfer of log files - Transfer for full or incremental Software Updates - Upload and download of secure certificates (SSL, SSH) and password...
Menu Configuration Files Every submenu will be defined by a spezial formated text file. The name of this file has to be started with „menu_“. This file is an ASCII file which can be created by a standard text editor with the following format: # Comment Menu-Name: get configuration from USB Stick Menu-Type: default...
Menu Script Files The name of the script file which will be activated when pressing the CLR/ACK button on a submenu will be defined in the Menu configuration file. The script files consists of commands using in a Telnet session (like „cp“ or „rm“). The following example will copy the Lantime configuration file from the USB stick to the internal flash of the Lantime.
Reference [Mills88] Mills, D. L., "Network Time Protocol (Version 1) - specification and implementation", DARPA Networking Group Report RFC-1059, University of Delaware, July 1988 [Mills89] Mills, D. L., "Network Time Protocol (Version 2) - specification and implementation", DARPA Networking Group Report RFC-1119, University of Delaware, September 1989 [Mills90] Mills, D.
Need help?
Do you have a question about the LANTIME M300 and is the answer not in the manual?
Questions and answers