Orolia TTS 220 Network Time Server Instruction manual


Add to my manuals
121 Pages

advertisement

Orolia  TTS 220 Network Time Server  Instruction manual | Manualzz

MODEL TTS 220

Network Time Server

INSTRUCTION MANUAL

95 Methodist Hill Drive

Suite 500

Rochester, NY 14623

Phone: 585.321.5800

Fax: 585.321.5219 www.spectracomcorp.com

Revisions, if any, are located at the end of the manual.

Part number 1126-5000-0050

Manual Revision C

December 2004

Current to software version 2.2.0

Copyright© 2004 Spectracom Corporation. All rights reserved. Contents of this publication may not be reproduced in any form without the written permission of Spectracom Corporation

SPECTRACOM 95 Methodist Hill Drive Suite 500 Rochester, NY 14623

+1.585.321.5800 FAX: +1.585.321.5218 www.spectracomcorp.com [email protected]

LIMITED WARRANTY

Spectracom warrants each new product manufactured and sold by it to be free from defects in software, material, workmanship, and construction, except for batteries, fuses, or other material normally consumed in operation that may be contained therein AND AS

NOTED BELOW, for five years after shipment to the original purchaser (which period is referred to as the “warranty period”).

This warranty shall not apply if the product is used contrary to the instructions in its manual or is otherwise subjected to misuse, abnormal operations, accident, lightning or transient surge, repairs or modifications not performed by Spectracom.

The GPS receiver is warranted for one year from date of shipment and subject to the exceptions listed above. The power adaptor, if supplied, is warranted for one year from date of shipment and subject to the exceptions listed above.

THE ANALOG CLOCKS ARE WARRANTED FOR ONE YEAR

FROM DATE OF SHIPMENT AND SUBJECT TO THE EXCEPTIONS

LISTED ABOVE.

THE TIMECODE READER/GENERATORS ARE WARRANTED FOR

ONE YEAR FROM DATE OF SHIPMENT AND SUBJECT TO THE

EXCEPTIONS LISTED ABOVE.

The Rubidium oscillator, if supplied, is warranted for two years from date of shipment and subject to the exceptions listed above.

All other items and pieces of equipment not specified above, including the antenna unit, antenna surge suppressor and antenna pre-amplifier are warranted for 5 years, subject to the exceptions listed above.

WARRANTY CLAIMS

Spectracom’s obligation under this warranty is limited to in-factory service and repair, at Spectracom’s option, of the product or the component thereof, which is found to be defective. If in

Spectracom’s judgment the defective condition in a Spectracom product is for a cause listed above for which Spectracom is not responsible, Spectracom will make the repairs or replacement of components and charge its then current price, which buyer agrees to pay.

SPECTRACOM 5-YEAR WARRANTY

Spectracom shall not have any warranty obligations if the procedure for warranty claims is not followed. Users must notify

Spectracom of the claim with full information as to the claimed defect. Spectracom products shall not be returned unless a return authorization number is issued by Spectracom.

Spectracom products must be returned with the description of the claimed defect and identification of the individual to be contacted if additional information is needed. Spectracom products must be returned properly packed with transportation charges prepaid.

Shipping expense: Expenses incurred for shipping Spectracom products to and from Spectracom (including international customs fees) shall be paid for by the customer, with the following exception. For customers located within the United States, any product repaired by Spectracom under a “warranty repair” will be shipped back to the customer at Spectracom’s expense unless special/faster delivery is requested by customer.

Spectracom highly recommends that prior to returning equipment for service work, our technical support department be contacted to provide trouble shooting assistance while the equipment is still installed. If equipment is returned without first contacting the support department and “no problems are found” during the repair work, an evaluation fee may be charged.

EXCEPT FOR THE LIMITED WARRANTY STATED ABOVE,

SPECTRACOM DISCLAIMS ALL WARRANTIES OF ANY KIND

WITH REGARD TO SPECTRACOM PRODUCTS OR OTHER

MATERIALS PROVIDED BY SPECTRACOM, INCLUDING

WITHOUT LIMITATION ANY IMPLIED WARRANTY OR

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Spectracom shall have no liability or responsibility to the original customer or any other party with respect to any liability, loss, or damage caused directly or indirectly by an Spectracom product, material, or software sold or provided by Spectracom, replacement parts or units, or services provided, including but not limited to any interruption of service, excess charges resulting from malfunctions of hardware or software, loss of business or anticipatory profits resulting from the use or operation of the Spectracom product or software, whatsoever or howsoever caused. In no event shall

Spectracom be liable for any direct, indirect, special or consequential damages whether the claims are grounded in contract, tort (including negligence), or strict liability.

EXTENDED WARRANTY COVERAGE

Extended warranties can be purchased for additional periods beyond the standard five-year warranty. Contact Spectracom no later than the last year of the standard five-year warranty for extended coverage.

SPECTRACOM 95 Methodist Hill Drive Suite 500 Rochester, NY 14623

+1.585.321.5800 FAX: +1.585.321.5218 www.spectracomcorp.com [email protected]

Table of Contents

1 GENERAL INFORMATION ...........................................................................................................1

1.1 Introduction............................................................................................................................................... 1

1.2 Warranty Information and Product Support ........................................................................................ 2

1.3 Unpacking.................................................................................................................................................. 3

1.4 Model TTS 220 Specifications.................................................................................................................. 4

1.4.1 Receiver .............................................................................................................................................. 4

1.4.2 RS-232 Setup Port............................................................................................................................... 4

1.4.3 10/100 Ethernet Port ........................................................................................................................... 4

1.4.5 RS-232 Communication Port.............................................................................................................. 5

Output .................................................................................................................................... 5

1.4.8 Front Panel LED Indicators ................................................................................................................ 5

Outputs...................................................................................................................................... 6

Power......................................................................................................................................... 6

2 INSTALLATION ............................................................................................................................7

2.1 Power and Ground Connection ............................................................................................................... 7

2.2 GPS Antenna Installation......................................................................................................................... 8

2.2.1 Antenna Cable for Outdoor Antenna .................................................................................................. 8

Lengths ..................................................................................................................................... 8

2.2.3 Model 8226 Impulse Suppressor ........................................................................................................ 8

2.2.4 Model 8227 GPS Inline Amplifier...................................................................................................... 9

2.3 Ethernet Network Cabling..................................................................................................................... 10

2.4 RS-485 Wiring and Set up...................................................................................................................... 11

2.4.2 Remote Output Usage ....................................................................................................................... 12

Guidelines ............................................................................................................................ 12

2.4.5 Termination....................................................................................................................................... 17

3 PRODUCT CONFIGURATION....................................................................................................19

3.1 Network Configuration .......................................................................................................................... 19

3.1.1 Using the Web Interface to Configure the Network ......................................................................... 19

3.1.2 Login................................................................................................................................................. 21

3.1.3 To Change the Default Login Password Values............................................................................... 23

3.2 Configuring SSH and SSL ..................................................................................................................... 24

Overview ............................................................................................................................ 24

3.3 Configuring HTTPS ............................................................................................................................... 32

3.3.1 Overview........................................................................................................................................... 32

3.3.2 Deleting Certificates, Private Keys, and Certificate Requests.......................................................... 32

3.3.3 Restoring Self Signed Certificates and Private Keys........................................................................ 33

3.3.4 Creating Self Signed Certificates, a Private Key, and a Certificate Request.................................... 33

3.3.7 Using Externally generated Certificates and Private Keys ............................................................... 36

3.3.8 What to do if you cannot get into a secure Spectracom Product ...................................................... 38

3.4 NTP/SNTP ............................................................................................................................................... 39

3.4.1 Configure

Support ..................................................................................................................................... 40

3.4.3 Application Note: MD5 Authentication using a Cisco Router ........................................................ 41

3.5 Local System Clocks Setup .................................................................................................................... 42

3.5.1 Time Zone and DST.......................................................................................................................... 45

3.6 Interface Setup ........................................................................................................................................ 48

3.7 Front Panel Display ................................................................................................................................ 50

3.8 Alarms...................................................................................................................................................... 53

Outputs................................................................................................................................... 53

3.9 Relays ....................................................................................................................................................... 55

3.9.1 Configuring the relays....................................................................................................................... 55

3.10 Event Timer............................................................................................................................................. 57

3.10.1 Configuring the Event Timer ............................................................................................................ 57

3.11 Logs .......................................................................................................................................................... 61

3.11.1 Display Alarm Log ........................................................................................................................... 61

3.11.2 Display Dial Out Log........................................................................................................................ 61

3.11.3 Display Operational Log................................................................................................................... 62

3.11.4 Display Oscillator Log...................................................................................................................... 64

3.11.6 Display Event Relay Log .................................................................................................................. 67

3.11.7 GPS Qualification Log...................................................................................................................... 67

3.12 SNMP ....................................................................................................................................................... 69

Configuration ........................................................................................................................ 69

MIB ............................................................................................................................... 70

4 OPERATION ...............................................................................................................................72

4.1 Status Indicator....................................................................................................................................... 72

4.2 GPS........................................................................................................................................................... 73

Operation .................................................................................................................................. 73

4.2.2 Set System Mode .............................................................................................................................. 74

4.2.3 GPS Signal Status ............................................................................................................................. 75

Troubleshooting............................................................................................................... 79

5 TROUBLESHOOTING ................................................................................................................81

5.1 Front Panel Power and Sync Lamps..................................................................................................... 81

5.2 Front Panel LAN Connector.................................................................................................................. 82

5.3 Customer Service .................................................................................................................................... 83

6 APPENDICES .............................................................................................................................84

6.1 Software Commands............................................................................................................................... 84

6.2 Serial Data Formats.............................................................................................................................. 101

6.3 SW License Notices............................................................................................................................... 109

List of Figures

Figure 2.2-1: Model 8226 Impulse Suppressor ....................................................................................9

Figure 2.2-2: Model 8227 Inline Amplifier ............................................................................................9

Figure 2.4-1: Remote Outputs............................................................................................................11

Figure 2.4-2: RS-485 Output..............................................................................................................11

Figure 2.4-3: One-Way Bus Installation .............................................................................................13

Figure 2.4-4: Split Bus Configuration .................................................................................................14

Figure 2.4-5: Wire Strain Relief..........................................................................................................15

Figure 2.4-6: TimeView RS-485 Interface..........................................................................................16

Figure 2.4-7: Model 8179T TimeTap RS-485 Interface......................................................................16

Figure 2.4-8: Model 9188/8188 RS-485 Interface ..............................................................................17

Figure 2.4-9: TimeBurst RS-485 Interface .........................................................................................17

Figure 3.1-1: Log-in Permissions .......................................................................................................22

Figure 3.2.2-1: SSH configuration Screen ..........................................................................................25

Figure 3.2.2-2 Creating SSH host key files .........................................................................................26

Figure 3.2.2-3 Selecting SSH authentication modes...........................................................................27

Figure 3.2.2-4 Adding SSH public key to authorized keys ..................................................................28

Figure 3.2.2-5 Adding a new SSH public key file ................................................................................29

Figure 3.3.2-1 Deleting SSL Certificate, Certificate Request and Private Key Files............................33

Figure 3.3.3-1 Restoring user’s Self Signed Certificate and Private Key Files....................................33

Figure 3.3.4-1 Creating a new Certificate Request and Self Signed Certificate..................................34

Figure 3.3.5-1 A new Certificate Request and Self Signed Certificate ................................................35

Figure 3.3.6-1 Installing a new Certificate...........................................................................................36

Figure 3.3.7-1 Using External Certificate and Private Key ..................................................................37

Figure 3.4-1: NTP Screen ..................................................................................................................39

Figure 3.5-1 Local System Clocks Setup Screen................................................................................42

Figure 3.5-2 Time Zone and DST Setup Screen.................................................................................43

Figure 3.6-1: Interface Screen ............................................................................................................49

Figure 3.7-1: Front Panel Display Screen ..........................................................................................50

Figure 3.8-1: Alarm Setup Screen......................................................................................................54

Figure 3.9-1 Relay Output Screen .....................................................................................................55

Figure 3.10-1: Event Timer Relay Screen..........................................................................................57

Figure 3.10-2 Event Timer Relay Screen............................................................................................58

Figure 3.11-1 NTP Statistics ...............................................................................................................66

Figure 3.12-1: SNMP Setup Screen...................................................................................................69

Figure 4.2-1: GPS Set-up Screen ......................................................................................................73

Figure 4.2-2: GPS Signal Status Setup Screen .................................................................................75

List of Tables

Table 2-1: Cable Sources for RS-485 Lines Over 1500 Feet.............................................................12

Table 2-2: Cable Sources for RS-485 Lines Under 1500 Feet...........................................................13

Table 4-1: Status Indicator .................................................................................................................72

Table 4-2: Typical Antenna Cable Resistance Values .......................................................................79

Table 6-1: Alphabetical List of Commands ........................................................................................84

Table 6-2: Table of Quality Indicators ..............................................................................................103

1 General Information

1.1 Introduction

Spectracom Corporation is a leading manufacturer of synchronized, precise time-keeping devices meeting the demands for accuracy, reliability and trace ability in mission-critical systems across networks. Our NetClock is a direct response to customer needs for cutting-edge synchronization technology at an affordable price.

Spectracom NetClock Master Clocks are based on GPS (Global Positioning System) technology – tracking up to twelve satellites simultaneously and synchronized to their atomic clocks. This enables computer networks to synchronize all elements of network hardware and software (including system logs) down to the millisecond over LANs or WANs – anywhere on the planet.

Technology advancements, including an embedded processor, make it possible to obtain Legally

Traceable Time

tags on log files and simplify digital forensics. The NetClock allows users to accurately time stamp video surveillance systems, access points, card readers, time clocks and alarm systems to provide necessary evidence and validation of events.

Set-up and reporting are web-enabled – a NetClock can be accessed, under appropriate security policies, anywhere within a network. The product features browser-based remote diagnostics, configuration and control as well as Flash memory for remote software upgrades. A 10/100 Mbps

Ethernet LAN port provides support for Network Time Protocol (NTP) over a variety of platforms including Win2K and XP, Win 95/98/ME, NT, Cisco, UNIX, Linux and more. Remote control and monitoring can also be done through SNMP and Telnet.

Time code outputs are available to meet the requirements of diverse systems – RS-232 serial ports,

RS-485 data bus ports. Alarm outputs and programmable timer outputs are also provided.

The NetClock Master Clock system includes a CE/UL-approved power supply for international use,

GPS antenna and associated mounting hardware.

TTS220 Manual Rev C Page 1

1.2 Warranty Information and Product Support

Warranty information is found on the leading pages of this manual.

Spectracom continuously strives to improve its products and therefore greatly appreciates any and all customer feedback given. Please participate in Spectracom’s Customer Satisfaction Survey found on our web site at: http://www.spectracomcorp.com/

The online survey is also used for warranty registration of your new Spectracom products. All completed entries are automatically entered into a monthly prize give away drawing.

Technical support is available by telephone. Please direct any comments or questions regarding application, operation, or service to Spectracom Customer Service Department. Customer Service is available Monday through Friday from 8:00 A. M. to 5:00 P.M. Eastern time.

Telephone Customer Service at: 585-321-5800.

In addition, please contact customer service to obtain a Return Material Authorization Number

(RMA#) before returning any instrument to Spectracom Corporation. Please provide the serial number and failure symptoms. Transportation to the factory is to be prepaid by the customer. After obtaining an RMA# ship the unit back using the following address:

Spectracom Corporation

Repair

Drive, 500

Rochester,

Product support is also available by e-mail. Questions on equipment operation and applications may be e-mailed to Spectracom Sales Support at: mailto:[email protected]

Repair or technical questions may be e-mailed to Spectracom Technicians at: mailto:[email protected]

Visit our web page for product information, application notes and upgrade notices as they become available at: http://www.spectracomcorp.com/

TTS220 Manual Rev C Page 2

1.3 Unpacking

Upon receipt, carefully examine the carton and its contents. If there is damage to the carton that results in damage to the unit, contact the carrier immediately. Retain the carton and packing materials in the event the carrier wishes to witness the shipping damage. Failing to report shipping damaging immediately may forfeit any claim against the carrier. In addition, notify Spectracom Corporation of shipping damage or shortages, to obtain a replacement or repair services.

Remove the packing list from the envelope on the outside of the carton. Check the packing list against the contents to be sure all items have been received, including an instruction manual and ancillary kit.

1. Unit

3. CE/UL-approved power supply for international use

5. Rack mount kit (2 ears, 4 side screws)

6. Rubber footpads for desktop installation

7. Two 3-pin terminal block connector for RS-485 connections

8. 10-pin terminal block connector

Resistor,

Spectracom models that have the modem dial out feature will also receive the following:

10. Serial Modem kit

11. Null modem adapter

TTS220 Manual Rev C Page 3

1.4 Model TTS 220 Specifications

1.4.1 Receiver

Received standard: L1 C/A Code transmitted at 1575.42 MHz.

Satellites tracked:

Acquisition time:

Up to twelve simultaneously.

Typically <4 minutes from a cold start.

Antenna requirements: Active antenna module, +5V, powered by the NetClock, with 18 to 36 dB gain

Antenna connector: Type N, female.

Function:

Connector:

Character structure:

Function:

Accepts commands to locally configure the IP network parameters for initial connectivity

DB9 female, pin assignments conform to EIA/TIA-574 standard, data communication equipment

ASCII, 9600 baud, 1 start, 8 data, 1 stop, no parity.

10/100 Base T auto sensing LAN connection for NTP and remote monitoring, diagnostics, configuration and upgrade.

Networked NTP Stratum 1 Time Server (RFC 1305), SNTP (RFC 1361) NTP:

Loading:

Accuracy:

Clients supported:

HTTP, HTTPS:

SCP:

SSH:

SSL:

675 requests per second without encryption.

345 requests per second with encryption.

Output jitter within +/-50 microseconds of UTC typical.

Up to 128 users may be supported in a single sub-network.

A gateway greatly increases the number of users.

For browser-based configuration and monitoring using Internet Explorer 5 or Netscape 6 per RFC 1945 and 2068.

Secure Copy Protocol for remote upload of event logs and download of upgrades.

Secure Shell for remote login capability

Secure Sockets Layer for supporting https, SCP, and SSH protocol. Uses

OpenSSL ver 0.9.7c

SNMP:

TTS220 Manual Rev C

As of release 2.1.0 (future) will support v1, v2, v2c, and v3. Compliant with RFCs 1155, 1157, 1212, 1213, 12 15, 1901-8.

Page 4

Telnet:

Security Features:

For limited remote configuration per RFC 854.

Up to 16-character Telnet password, Telnet Disable, TFTP Disable, SNMP

Disable and MD5 Authentication.

RJ-45, Network IEEE 802.3. Connector:

1.4.5 RS-232 Communication Port

Signal: Selected time Data Format in RS-232 levels when interrogated by the connected device. This port may also be configured to provide a continuous once-per-second output.

Connector:

Character structure:

Accuracy:

Configuration:

DB9 female, pin assignments conform to EIA/TIA-574 standard, data communication equipment (DCE). No flow control.

ASCII, 1 start, 8 data, 1 stop, and no parity.

Data stream on time marker within ± 100 microseconds of UTC on Sync in

Formats 0, 1, and 3. Formats 2 and 4 within ±1 millisecond of UTC.

Baud rate and output Data Formats are selected using the web interface.

Bit rate selections are 1200, 2400, 4800 and 9600 baud. There are six

Data Format selections available.

Signal:

Connector:

Character structure:

Accuracy:

Configuration:

Selected time Data Format in RS-485 levels, output once-per-second.

Removable 3-position terminal block (supplied).

ASCII, 1 start, 8 data, 1 stop, and no parity.

Data stream on time marker within ± 100 microseconds of UTC on Sync.

Baud rate and output Data Formats are selected using the web interface.

Bit rate selections are 1200, 2400, 4800, and 9600 baud. There are six

Data Format selections available.

1.4.7 Front Panel Display

Display Type: Two separate Back-lit LCD displays.

Display Options: Each display is configurable via the Web Interface. Choices consist of

Time, Date, Day of Year, Software Versions, Fonts, and Date Formats.

1.4.8 Front Panel LED Indicators

Power: Green, always on

Sync:

LAN:

Tri-color LED indicates the time data accuracy and equipment fault

Green: Good Link indicator

TTS220 Manual Rev C Page 5

Three separate outputs provided for either Programmable Event Timer Output or Major/Minor Alarm indication.

Relay contacts:

Contact rating:

Connector:

NO, NC, and Common.

30 VDC, 2 amps.

10-position 3.81 mm terminal block (mate supplied).

Programmable Timer Output:

128 On/Off events standard, 1024 events optional. Timer events that are hourly, daily or weekly only count as a single event so many events can be programmed in even the standard product.

Major/Minor Alarms: Relay contacts allow remote monitoring of operational status. A power failure, CPU failure loss of time sync, etc cause the alarm relay to deenergize. The alarm relay returns to normal operation (energized) when the fault condition is corrected.

Power source:

DC input:

90 to 240 VAC, 47 to 63 Hz through an IEC 320 universal connector.

North American AC power cord supplied. AC cables for other countries available locally.

9.5 to 30 VDC, 10 watts, through a CE/UL/CSA-approved power adapter

(supplied).

Barrel, 5.5mm O.D., 2.5 mm I. D.

Negative shell, positive center.

Connector:

Polarity:

1.4.11 Mechanical and Environmental

Dimensions: EIA 19” rack mount W x 1.75” H [1U] x 11.00” D

(483 mm W x 44 mm H x 305 mm D).

Weight: 4.8 lbs. (2.2 kg).

Temperature: 32

° to 122°F (0° to 50°C) operating range.

-40

° to 185°F (-40° to 85°C) storage range

Humidity: 10% - 95% relative humidity, non-condensing

TTS220 Manual Rev C Page 6

2 Installation

2.1 Power and Ground Connection

An external AC to DC power adapter powers the NetClock.

The adapter is available in two forms:

1. US Only Wall Mount adapter, which plugs into any standard North American outlet.

2. The International and US Desk Top adapter, which has a detachable AC power cord to an IEC

320 connector.

This power adapter is shipped with a line cord compatible with AC receptacles (NEMA 5-15R) commonly found in the United States and Canada. Alternate type line cords or adapters may be obtained locally.

The chassis ground stud allows the NetClock chassis to be connected to an earth ground or single point ground. Connecting the chassis to a single point ground system may be required in some installations to ensure optimum lightning protection. An earth ground is also recommended in installations where excessive noise on the power line degrades receiver performance.

Note: Auto Negotiate, which determines the network settings to use, only occurs at power-on.

Always connect the Ethernet cable before powering-on the unit for the first time. If the Ethernet cable is connected after power-on, the unit will default to 10 Mbps and half duplex.

TTS220 Manual Rev C Page 7

2.2 GPS Antenna Installation

2.2.1 Antenna Cable for Outdoor Antenna

When using the Model 8225 GPS outdoor antenna, Spectracom recommends using LMR-400 low loss type cable, Spectracom CAL7xxx for the GPS antenna cable. RG-213 type coax, such as

Belden 8267,may also be used but low loss cable offers the best performance. To simplify the installation process, Spectracom offers GPS cable assemblies terminated with Type N Male connectors. Specify part number CAL7xxx, where xxx equals the length in feet. Standard lengths are 10, 25, 50, 100, 150 and 200 feet.

If the antenna cable is purchased locally, select coax suitable for outdoor use. Consider the cable's weather ability, temperature range, UV resistance, and attenuation characteristics.

Do not allow the antenna cable to be placed in standing water, as water may permeate through the coax jacket over time. On flat roof installations, the coax can be suspended by cable hangers or placed in sealed PVC conduit. Apply a weather proofing sealant or tape over all outdoor connections.

Installation of a surge protection device in the antenna line is recommended to protect the NetClock receiver and connected devices from lightning damage. Spectracom offers the Model 8226 Impulse

Suppressor to shunt potentially damaging voltages on the antenna coax to ground. Refer to the

Model 8226 Impulse Suppressor Section for a complete description of the Model 8226.

2.2.2 Cable Lengths

Using Spectracom CAL7xxx or Times Microwave LMR-400 coax, the maximum antenna cable length permitted is 200 feet because the 91XX series allows 12 dB loss. An amplifier is needed whenever antenna cable lengths exceed 200 feet. Installations requiring longer antenna cables may use the

Model 8227 Inline Amplifier, or lower loss cable. Refer to the Model 8227 Section for additional information on the Model 8227.

When selecting alternate antenna cable sources, the attenuation characteristics at the GPS frequency of 1575.42 MHz must be known. To ensure optimum receiver performance, the total antenna cable attenuation must not exceed 12 dB. Cable attenuation of greater than 12 dB requires the use of a Model 8227 Inline Amplifier.

2.2.3 Model 8226 Impulse Suppressor

Spectracom recommends the use of an inline coaxial protector for all products with an outside antenna. Spectracom offers the Model 8226, Impulse Suppressor, to protect the receiver from damaging voltages occurring on the antenna coax. Voltages exceeding the impulse suppresser trip point are shunted to the system ground. The Model 8226 is designed to withstand multiple surges.

Mount the suppressor indoors, preferably where the coax enters the building. Install the suppressor on a grounding panel or bulkhead as shown in Figure 2.2-1.

TTS220 Manual Rev C Page 8

.0625 inch (15.88mm)

DIAMETER

INSTALL "O" RING

.203 inch (5.16mm)

DIAMETER

MOUNTING

HOLE PATTERN

SINGLE POINT GROUNDING

PANEL OR BULKHEAD

Figure 2.2-1: Model 8226 Impulse Suppressor

Refer to the Model 8226 Manual for proper installation.

2.2.4 Model 8227 GPS Inline Amplifier

An inline amplifier is required whenever GPS antenna cable lengths cause greater than 12 dB attenuation. Using Spectracom CAL7xxx coax, an amplifier is needed whenever antenna cable lengths exceed 200 feet.

The Model 8227 GPS Inline Amplifier, shown in Figure 2.2-2, extends the maximum cable length to

600 feet. The Model 8227 provides 20 dB of gain and is powered by the NetClock/ receiver.

Figure 2.2-2: Model 8227 Inline Amplifier

Refer to the Model 8227 Manual for proper installation.

TTS220 Manual Rev C Page 9

2.3 Ethernet Network Cabling

Spectracom’s 91xx products provide a 10/100 Ethernet port for full NTP functionality as well as full web enabled configuration, monitoring and diagnostic support.

The Ethernet port is provided on the front panel for easy connection to routers and hubs.

• Use standard CAT 5 cable with RJ45 connectors.

• When connecting to a hub or router use a straight-through wired cable.

• When connecting directly to a PC, use a crossover wired cable.

TTS220 Manual Rev C Page 10

2.4 RS-485 Wiring and Set up

2.4.1 Remote Connections

The NetClock has two Remote Connections labeled RS-485 1 and RS-485 2. On NetClocks without a GPS reference, port 1 is used as a time output port and port 2 is a time input port. On NetClocks with a GPS reference, both ports are output ports. These outputs provide a continuous once-persecond time data stream in the selected Data Format. There are two input time Data Formats and five-output time Data Format selections and one position data stream in NMEA 0183 format available.

Refer to Section 6.2

for a complete description of the data format structures.

In addition to Data Formats, baud rate and UTC time difference of each output is selectable. Refer to the Interface Set-up Section 3.6 for configuring these outputs.

A 3-position terminal block is supplied in the ancillary kit for each Remote Connections. Connector pin assignments are shown in Figure 2.4-1.

RS-485 REMOTE

Figure 2.4-1: Remote Outputs

RS-485 is a balanced differential transmission requiring twisted pair cabling.

RS-485 characteristics make it ideal to distribute time data throughout a facility. Each Remote Output can provide time to 32 devices at cable lengths up to 4,000 feet. Refer to Figure 2.4-2 for a schematic representation of each RS-485 output driver. Relative to RS-485 specifications, the A terminal (Pin 2) is negative with respect to the B terminal (Pin 1) for a mark or binary 1. The A terminal is positive to the B terminal for a space or binary 0.

Shield

B

A

1

2

3

B Terminal (+)

A Terminal (-)

Figure 2.4-2: RS-485 Output

TTS220 Manual Rev C Page 11

Spectracom offers many devices that accept the RS-485 data stream as an input reference. These products include display clocks, RS-485 to RS-232 converters, NTP time provider, and radio link products to meet various time applications and requirements. For information on Remote Output usage refer to Section 2.4.2

of this chapter.

2.4.2 Remote Output Usage

The Remote Outputs provide a continuous once-per-second time data stream in RS-485 levels.

RS-485 is a balanced differential transmission, which offers exceptional noise immunity, long cable runs and multiple loading. These characteristics make RS-485 ideal for distributing time data throughout a facility. Each Remote Output can drive 32 devices over cable lengths up to 4000 feet.

Spectracom manufactures wall clocks, NTP time providers, RS-485 to RS-232 converters and radio link products that utilize the RS-485 data stream as an input. Figure 2-5 and Figure 2.6 illustrate typical RS-485 time data bus interconnections. Follow the guidelines listed below when constructing the RS-485 data bus.

2.4.3 RS-485 Guidelines

Cable selection: Low capacitance, shielded twisted pair cable is recommended for installations where the RS-485 cable length is expected to exceed 1500 feet. Table 2-1 suggests some manufacturers and part numbers for extended distance cables. These cables are specifically designed for RS-422 or RS-485 applications; they have a braided copper shield, nominal impedance of 120 ohms, and a capacitance of 12 to 16 picofarads per foot.

RS-485 cable may be purchased from Spectracom. Specify part number CW04xxx, where xxx equals the length in feet.

MANUFACTURER

Belden Wire and Cable Company

1-800-BELDEN-1

Carol Cable Company

606-572-8000

National Wire and Cable Corp.

232-225-5611

PART NUMBER

9841

C0841

D-210-1

Table 2-1: Cable Sources for RS-485 Lines Over 1500 Feet

TTS220 Manual Rev C Page 12

For cable runs less than 1500 feet, a lower-cost twisted pair cable may be used. Refer to Table 2-2 for possible sources. In addition, Category 5 cables may be used for cable runs less than 1500 feet.

PART NUMBER MANUFACTURER

Alpha Wire Corporation

1-800-52ALPHA

Belden Wire and Cable Company

1-800-BELDEN-1

5471

9501

Carol Cable Company

606-572-8000

C0600

Table 2-2: Cable Sources for RS-485 Lines Under 1500 Feet

2.4.4 Connection Method

The RS-485 transmission line must be connected in a daisy chain configuration as shown in Figure

2.4-3: One-Way Bus Installation. In a daisy chain configuration, the transmission line connects from one RS-485 receiver to the next. The transmission line appears as one continuous line to the RS-485 driver.

A branched or star configuration is not recommended. This method of connection appears as stubs to the RS-485 transmission line. Stub lengths affect the bus impedance and capacitive loading which could result in reflections and signal distortion.

N e tC lo c k

A U D IO

T im e T a lk

R e m o te

In p u t

D B 9 R e m o te

O u tp u t

R S 4 8 5

O u tp u t

T e rm in a l

B lo c k

R S 4 8 5

In /O u t

T e r m in a l

B lo c k

T im e V ie w 4 0 0

D IS P L A Y

T w is te d

P a ir C a b le

T e r m in a l

B lo c k

8 1 7 9 T

T im e T a p

R S-2 3 2

D IS P L A Y

T im e V ie w 2 3 0

R S - 4 8 5

In /O u t

T e rm in a l

B lo c k

T E R M IN A T E

E N D D E V IC E

R S - 2 3 2

8 1 7 9 T

T im e T a p

T e r m in a l

B lo c k

C H I

R S

T e rm in a l B lo c k to D B 2 5 A d a p te r

8 1 8 8 T im e S e r v e r

E T H E R N E T

1 0 B A S E T

4 8 5

T im e D a ta B u s

Figure 2.4-3: One-Way Bus Installation

The RS-485 Output could be split in two directions as shown in Figure 2.4-4. This allows the

NetClock/GPS to be centrally located. Connecting in this method can simplify installation and possibly reduce the amount of cable required.

TTS220 Manual Rev C Page 13

DISPLAY

Tim eView 400

R S-485

In/O ut

Term inal

Block

TERM IN ATE

END DEVICE

RS-232

8179T

Tim eTap

Term inal

Block

Twisted

Pair Cable

DIG ITAL

M ESSAG E

Tim eB urst

R S-485

Input

Term inal

Block

TERM IN ATE

END DEVICE

RS-232

8179T

Tim eTap

T erm inal

Block

R S-485

T im e D ata Bus

RS-485

In/O ut

T erm inal

Block

Tim eView 230

DISPLAY

R S-485

O utput

Term inal

Block

N etC lock

C HI

Term inal Block to DB25 Adapter

8188 Tim e Server

ETHERNET

10 B ASE T

Figure 2.4-4: Split Bus Configuration

Most RS-485 connections found on Spectracom equipment are made using a removable terminal strip. A jaw that compresses the wires when tightened secures the wires. When using small diameter wire, 22-26 gauge, a strain relief can be fashioned by wrapping the stripped wire over the insulating jacket as shown in Figure 2.4-5. Wrapping the wires in this manner prevents smaller gauge wires from breaking off when exposed to handling or movement.

TTS220 Manual Rev C Page 14

STRIP

WIRE

WRAP WIRE OVER

INSULATING JACKET

INSERT AND

TIGHTEN

Figure 2.4-5: Wire Strain Relief

TTS220 Manual Rev C Page 15

TimeView display clocks use a 6-position terminal block to connect to the RS-485 data bus. Connect the TimeView to the NetClock/GPS RS-485 Output as shown in Figure 2.4-6. The TimeView display clocks accept only Data Formats 0 or 1.

Figure 2.4-6: TimeView RS-485 Interface

The Model 8179T TimeTap is an RS-485 to RS-232 converter. The Model 8179T has a DB9

RS-232 interface that receives operational power from the RS-232 flow control pins RTS or DTR.

Connect the TimeTap to the RS-485 data bus as shown in Figure 2.4-7.

Figure 2.4-7: Model 8179T TimeTap RS-485 Interface

TTS220 Manual Rev C Page 16

Spectracom Model 9188/8188, NetClock/ is an Ethernet Time Server that supports NTP and SNTP time protocols. The Model 9188/8188 accepts either Format 0 or Format 2 and connects to the RS-

485 data bus through a three-position terminal block. Connect the Model 9188/8188 to the

Netclock/GPS as shown in Figure 2.4-8.

Figure 2.4-8: Model 9188/8188 RS-485 Interface

The Model 8185, TimeBurst

, provides a digital time-of-day data burst to a radio transmitter. The

TimeBurst accepts only Format 0. Connect the TimeBurst to the RS-485 data bus using a 3-position terminal block as shown in Figure 2.4-9.

Figure 2.4-9: TimeBurst RS-485 Interface

2.4.5 Termination

A termination resistor is required on devices located at the ends of the RS-485 transmission line.

Terminating the cable end preserves data integrity by preventing signal reflections.

For a one-way bus installation (Figure 2-5), terminate the last device on the bus. The RS-485 data bus can be split in two directions as shown in Figure 2-6. In a split bus configuration, terminate the devices installed on each end of the bus. Most Spectracom products include a built in termination switch to terminate the RS-485 bus when required.

If your unit comes with the modem dial out feature, you will need to connect a serial modem to the unit to allow it to connect to the modem time references.

TTS220 Manual Rev C Page 17

• The cable needed to connect the unit to the modem is a DB9 male to DB25 male null modem serial cable. This should come with the modem package.

• Connect the null modem converter that comes with the serial cable to the DB9 end of the cable to modify the standard cable to work with the Spectracom unit.

• Connect the DB25 side to the modem and the modified DB9 side to the serial setup port on the unit.

• Connect the CAT2 telephone cable from the phone line to the modem.

• Connect the modem power adapter to a power outlet.

• Refer to the Modem Dial Out Setup in section three of this manual for instructions on how to configure and use the modem dial out feature.

TTS220 Manual Rev C Page 18

3 Product Configuration

3.1 Network Configuration

3.1.1 Using the Web Interface to Configure the Network

The product has a 10/100 Mbps Ethernet port, which can be used to connect the unit to a network.

The unit will need to be initially configured via the setup port, and can thereafter be modified through either the serial port or web interface. The values to enter into the fields described below will be specific to your setup, and can be obtained from your network administrator.

IP Address: This is the unique 32-bit address assigned to the product. The default address is 10.10.200.1

Subnet Mask: This is a 32-bit mask that specifies the range of IP addresses of the

Ethernet segment the unit is connected to. The default value is

255.255.255.0.

Gateway: When the gateway IP is disabled on the product, the unit cannot be accessed from subnets outside the local subnet. When enabled, the IP address of the subnet's gateway will need to be specified. The default is disabled

Telnet: This is a toggle option to enable or disable the unit's telnet interface.

FTP:

HTTP

*

:

This is a toggle option to enable or disable the unit's FTP interface.

This is a toggle option to enable or disable the unit's HTTP interface on secure Spectracom products only.

SSH

*

: This is a toggle option to enable or disable the unit's SSH interface on secure Spectracom products only.

Note: Auto Negotiate, which determines the network settings to use, only occurs at power-on.

Always connect the Ethernet cable before powering-on the unit for the first time. If the Ethernet cable is connected after power-on, the unit will default to 10 Mbps and half duplex.

*

This feature is only available for secure Spectracom products

TTS220 Manual Rev C Page 19

TO CONFIGURE THE PRODUCT TO WORK ON A NETWORK VIA SETUP PORT:

Serial Setup Interface

1. Connect the serial port of your PC to the 9-pin Serial Set-up Interface connector.

2. Use a Terminal Emulator program such as HyperTerminal or equivalent to connect to the

NetClock®. Port settings should be 9600 Baud, No parity, 8 data bits, 1 stop bit, No flow control.

3. Power on the NetClock.

Initial network setup

If the unit has not yet been configured for a network, it will boot with the default settings and the

Spectracom login:’ prompt will appear; Login as administrator to change the default settings.

Note: To make changes to the settings, you must be logged in with configuration or administrator privileges. To Login with configuration- or administrator-level permissions with the ‘login’ command:

- For admin mode, type: login admin<enter>

- The unit will response with Password:

- Type admin123<enter> (the unit will not show what you type)

- For config mode, type: login config<enter>

- The unit will response with Password:

- Type config12<enter> (the unit will not show what you type)

If you hit enter during any part of the above commands, it will prompt you for the next value.

'net ip' will display or change the current IP address of the unit.

'net mask' will display or change the current subnet mask.

'net gateway' will display or change the current default gateway settings.

Example: To put the product on the network as 10.10.200.5 with a subnet mask of 255.255.255.128 and no gateway:

Connect to the serial port of the unit.

1. Connect to the serial port of the unit.

2. Login with configuration- or administrator-level permissions with the ‘login’ command.

3. Type ‘net ip 10.10.200.5 to set the IP address.

4. Type ‘net mask 255.255.255.128’ to set the subnet mask.

5. Type ‘net gateway no’ to disable the gateway feature.

TTS220 Manual Rev C Page 20

TO CONFIGURE THE PRODUCT TO WORK ON A NETWORK VIA WEB INTERFACE:

Connect to the web interface after booting the unit. Use a PC with a web browser (Such as Internet

Explorer version 5.0 or greater or Netscape) and connect to the product by typing in the IP address into the address window of the browser as follows: http://10.10.200.50 (or your IP address). Then, click on “Enter Main Page”.

Login to configuration or administrator level mode if changes are desired. Refer to 3.1.2

for instructions on Web Interface login.

Choose "System Setup" from the bottom frame, and "Network" from the left frame.

All fields will display the current system settings. At the bottom of the frame, clicking Reset will revert any changes made at this window since last pressing Submit.

The IP Address and Gateway Address fields must be entered in 'dotted-quad' format.

The Subnet Mask is displayed as pull down menu showing a list of possible subnet masks.

Setting the gateway to Disabled will cause the values in the Gateway Address field to be ignored.

The Telnet and FTP settings are displayed as radio buttons.

Example: To put a unit on the network as 10.10.200.5 with a subnet mask of 255.255.254.0, a gateway of 10.10.200.10, with Telnet disabled and FTP enabled:

1. Connect to the web interface of the product.

2. Login to configuration- or administrator-level mode and browse to the Network configuration page.

3. Enter ‘10’, ‘10’, ‘200’, and ‘5’ in the corresponding IP Address fields.

4. Select ‘255.255.254.0’ from the Subnet Mask pull down menu.

5. Choose the Gateway Enabled radio button.

6. Enter ‘10’, ‘10’, ‘200’, and ‘10’ in the corresponding Gateway Address fields.

7. Choose the Telnet Disabled radio button.

8. Choose the FTP Enabled radio button.

9. Review the changes made and click Submit. The browser will display the status of the change.

3.1.2 Login

There are two login modes:

1. Configuration Mode allows basic control over configuration parameters.

2. Administrator Mode allows full control over all parameters

TTS220 Manual Rev C Page 21

Both modes require a password.

Refer to Figure 3.1-1 for a list of the permission requirements.

Figure 3.1-1: Log-in Permissions

CAUTION:

The Administrator login provides the most power to change settings but an erroneous entry could cause the NetClock® to malfunction or not perform within specifications. Only technicians trained in NetClock® operations should be given access to the Administrator mode.

No Password?

That’s OK; you can still view the unit’s configuration settings in the read-only mode.

TTS220 Manual Rev C Page 22

Default Password

The default access settings for the Configuration and Administrator Modes are:

Username: config

Password: config12

Username: admin

Password: admin123

For security reasons, we recommend you change the password (and the user name) and don’t lose them! [You can write them down here.]

Username [config]: ______________

Password: ____________________

Username [admin]: ___________________

Password: __________________________

Once you have access to the settings web pages, you can set up each page.

3.1.3 To Change the Default Login Password Values

For security reasons, the account passwords cannot be changed using either the Web

Browser or telnet command. Password changes must be made using the RS-232 Serial Setup

Interface connection on the rear panel. To change the account passwords, connect to the

Serial Setup Interface with a straight-thru serial cable. Using HyperTerminal, Procomm or any other terminal emulator, login as admin using the current password. At the command prompt, type the following: sec password [admin or config]<enter>

Where [admin or config] is the account name desired to be changed.

The unit will then ask you to type in the old password and then to type the new password (twice).

Example:

Type: sec password <ent>

Response: Account:

Type: [current account name] <ent>

Response: Old Password:

Type: [current password for this account] <ent>

Response: New Password:

Type: [New password for this account] <ent>

Response: New Password (again):

Type: [New password for this account] <ent>

Response: New Password set

For additional information on the sec command, refer to the software command appendix (sec command).

NOTE: Always LOGOUT and EXIT CONNECTION TO THE PRODUCT prior to closing the Web

Browser when you are finished viewing the Ethernet Time Server settings. For security reasons, only one connection session is supported at any one time, so this ensures that a new session can be activated immediately. If you don’t log out or exit the connection, you will have to wait a time-out period or reset the unit to begin a new session.

TTS220 Manual Rev C Page 23

3.2 Configuring SSH and SSL

In addition to providing login accounts with up to 16-character passwords supporting different privileges for the config and admin users, Spectracom products providing security features use

OpenSSH and OpenSSL. OpenSSH is the Open Source version of the Secure Shell; which provides a set of server side tools allowing secure remote telnet like access and secure file transfer using remote copy like (RCP) and FTP like utilities. OpenSSL is the Open Source version of Secure

Sockets Library; which is used to provide the encryption libraries. Together OpenSSH and OpenSSL provide industrial strength encryption allowing for secure remote administration via command line,

HTTPS web pages and secure file transfers.

A convenient and simple Web User Interface is provided on secure Spectracom products under the

“System Setup” tab’s “Network” and “Security” sub menus. Users can configure their product and control the network access to the product by selecting options found under these menus. The

Network sub menu allows the user to choose to enable or disable protocols such as Telnet and FTP.

The user can also as described in the Network menu section control their subnet and gateway. On secure products the user is permitted to enable or disable HTTP and SSH as well. The secure product can be configured to allow access only via NTP and the secure protocols such as HTTPS or

SSH or to operate in a less secure mode. Spectracom secure products also provide a Security submenu. The security submenu provides the user with the means to configure their use of SSH and

SSL.

Pop up help text is available for most Security Web UI features. Allow your cursor to hover over the box and help text box should appear.

OpenSSH implements a free version of Secure Shell. Secure Shell is a set of server and client tools supporting secure telnet like remote access and secure, authenticated file transfers using passwords and/or public key cryptography. The tools supported by the secure Spectracom products are SSH – secure shell, SCP – secure copy, and SFTP – secure file transfer protocol. The secure Spectracom products implement the server components of SSH, SCP and SFTP.

For more information on OpenSSH please see www.openSSH.org

.

1.1.1.2 Managing Host Keys

1.1.1.2.1 Overview

SSH uses Host Keys to uniquely identify each SSH server. Host Keys are used for server authentication and identification. The secure Spectracom product allows the user to create or delete

RSA1 keys for the SSH1 protocol or RSA or DSA keys for the SSH2 protocol.

The user may choose to delete individual Host Keys. To delete a key simply select a radio button for the key you wish to delete and press submit at the bottom of the page.

TTS220 Manual Rev C Page 24

Figure 3.2.2-1: SSH configuration Screen

If the user chooses to delete the RSA1 key, the SSH1 protocol is not available and SSH1 clients will be unable to connect.

If the user chooses to delete the RSA or DSA key only the SSH2 protocol will function but that form of server authentication will not be available. If the user chooses to delete both the RSA and DSA keys the SSH2 protocol is not available and SSH2 clients will be unable to connect.

If the users chooses to simultaneously delete the RSA1, RSA and the DSA keys, SSH will not function. In addition, if SSH Host Keys are being generated at the time of deletion, the key generation processes are stopped, any keys created will be deleted, and all key bit sizes are set to 0.

The user may choose to delete existing keys and request the creation of new keys, however it is often simpler to make these requests separately.

The user may create individual RSA1, RSA and DSA Host Public/Private Key pairs. Host Keys must first be deleted before new Host Keys can be created. To create a new set of host keys first delete the old keys, then select the create host keys checkbox and enter the key sizes you desire. Then select the submit button at the bottom of the screen.

TTS220 Manual Rev C Page 25

A typical Host Key generation request is shown below.

Figure 3.2.2-2 Creating SSH host key files

Spectracom secure products typically have their initial Host Keys created at the factory. The default key size for all key types is 1024. Host Key sizes can vary between 768 and 4096 bits. The recommended key size is 1024. Though many key sizes are supported, it is recommended that users select key sizes that are powers of 2 or divisible by 2. The most popular sizes are 768, 1024, and

2048. Large key sizes up to 4096 are supported, but are discouraged because they take hours to generate.

Host Keys are generated in the background. Creating an RSA1, RSA and DSA keys each with 1024 bits length, typically takes about 10 minutes. Keys are created in the order of RSA, DSA and finally

RSA1. When the keys are created you can successfully make SSH client connections. If the unit is rebooted with Host Key creation in progress or the unit is booted and no host keys exist the key generation process is restarted. The key generation process uses either the previously specified key sizes or if a key size is undefined it defaults to 1024. A key with a zero length or blank key size field is not created.

Note also that when you delete a Host Key and recreate a new one, SSH client sessions will warn you that the host key has changed for this particular IP address. The user will either have to override

TTS220 Manual Rev C Page 26

the warning and accept the new Public Host Key and start a new connection or they may need to remove the old Host Public Key from their client system and accept the new Host Public Key. Please consult your specific SSH client’s software’s documentation.

1.1.1.3 Selecting SSH Authentication Mode

The SSH client utilities SSH, SCP and SFTP allow for several modes of user authentication. SSH allows the user to remotely login or transfer files by identifying the user’s account and the target machines IP address. Users can be authenticated by either using their account passwords or by using a Public Private Key Pair. Users keep their private key secret within their workstations or network user accounts and provide the Spectracom secure product a copy of their public key.

To select an Authentication mode admin users select an option from the Authentication section and select submit at the bottom of the page.

Figure 3.2.2-3 Selecting SSH authentication modes

The modes of authentication supported include:

• Either Public Key with Passphrase or Login Account Password

• Login Account Password only

• Public Key with Passphrase only

TTS220 Manual Rev C Page 27

The first option allows users to login using either method. This is the default. Whichever mode works is allowed for logging in. If the Public Key is not correct or the passphrase is not valid the user is then prompted for the login account password. The second option simply skips public/private key authentication and immediately prompts the user for password over a secure encrypted session avoiding sending passwords in the clear. Finally the last option requires the user to load a public key into the Spectracom secure product. This public key must match the private key found in the users account and be accessible to the SSH, SCP or SFTP client program. The user must then enter the passphrase after authentication of the keys to provide the second factor for 2-factor authentication.

1.1.1.4 Managing Public Keys used for SSH Authentication

SSH using public/private key authentication is the most secure method of authenticating users for

SSH, SCP or SFTP sessions.

The Web UI provides the means for the user to delete the /sys/.SSH/authorized_keys file, to add individual Public Keys and comments to the existing file, and to copy a file containing Public Keys from the /sys/update folder to a file named /sys/.SSH/authorized_keys. Using FTP, SCP or SFTP the user may also retrieve the read-only authorized_keys file from the /sys/.SSH directory.

An example of a user adding a public key to the authorized_keys file is shown below.

Figure 3.2.2-4 Adding SSH public key to authorized keys

Users are required to create private and public key pairs on their workstation or within a private area in their network account. These keys may be RSA1, RSA or DSA and may be any key bit length as supported by the SSH client tool. These public keys are stored in a file in the /sys/.SSH directory

TTS220 Manual Rev C Page 28

named authorized_keys. The file permissions are to be read-write for root and read-only for all other users. The file is to be formatted such that the key is followed by the optional comment with only one key per line. The Spectracom application terminates each line with a carriage return and separates each line with a blank line. The file format, line terminations and other EOL or EOF characters should correspond to Unix conventions, not Windows.

If a user deletes all Public Keys Public/Private Key Authentication is disabled. If the user has selected

SSH authentication using the “Public Key with Passphrase” option login and file transfers will be forbidden. The user must select a method allowing the use of account password authentication to enable login or file transfers using SCP or SFTP.

If a user wants to completely control the public keys used for authentication a correctly formatted authorized_keys file formatted as indicated in the OpenSSH web site can be loaded onto a secure

Spectracom product. The user transfers a new public key file using an insecure FTP client or a secure SCP or SFTP client using only account password authentication. The user should place the new public key’s file in the /sys/update directory. The user then selects the delete all public key’s checkbox, selects the update public key’s checkbox and enters the filename in the space provided.

An example of a user adding a new public key file is shown below.

TTS220 Manual Rev C

Figure 3.2.2-5 Adding a new SSH public key file

Page 29

The MyPublicKeys.txt file in the /sys/update directory is renamed and placed in the /sys/.SSH directory under the new name authorized_keys after the user selects the submit button at the bottom of the screen. Users can now authenticate using Private Keys, which match these public keys if the authentication mode supports “Public Key with Passphrase” authentication.

1.1.1.5 Secure Shell Sessions

Secure shell sessions using an SSH client can be performed using the admin or config accounts.

The user may use Account Password or Public Key with Passphrase authentication. Please be patient it can take a few minutes to establish a secure SSH session. The OpenSSH tool SSH-

KEYGEN is used to create RSA1, RSA and DSA keys used to identify and authenticate user login or file transfers.

The following command lines for OpenSSH SSH client tool are given as examples of how to create a secure SSH session.

1. Creating an SSH session with Password Authentication for the admin account. ssh [email protected]

[email protected]'s password: admin123

The user is now presented with Boot up text and/or a “>” prompt which allows the use of the Spectracom command line interface.

2. Creating an SSH session with Password Authentication for the admin account. ssh [email protected]

[email protected]'s password: config12

The user is now presented with Boot up text and/or a “>” prompt which allows the use of the Spectracom command line interface.

3. Creating an SSH session using Public Key with Passphrase Authentication for the admin or config account.

The user must first provide the secure Spectracom product a RSA public key found typically in the OpenSSH id_rsa.pub file. The user may then attempt to create an SSH session. ssh -i ./id_rsa [email protected]

Enter passphrase for key './id_rsa': mysecretpassphrase

Please consult the SSH client tool’s documentation for specifics on how to use the tool, select SSH protocols, and provide user private keys.

1.1.1.6 Secure File Transfer

The secure Spectracom products provide secure file transfer using the SSH client tools SCP and

SFTP. Authentication is performed using either Account Passwords or Public Key with Passphrase.

However unlike SSH where the config or admin accounts are used, a special user account is provided named “SCP” for these tools. The “SCP” user account has the same password as the admin account. It differs from the admin and config accounts in that it does not run the Spectracom product shell. It is a limited account that only allows the user to transfer files to and from the

/sys/update folder and to retrieve files from folders which the SCP account has read permission.

Some sample OpenSSH SCP and SFTP client commands are shown below.

TTS220 Manual Rev C Page 30

1. Perform an SCP file transfer to the device using Account Password authentication scp publickeys [email protected]

:/sys/update [email protected]'s password: admin123 (Always use same password as admin) publickeys 100% |***************************************************| 5 00:00

2. Perform an SCP file transfer from the device using Public Key with Passphrase authentication. scp -i ./id_rsa publickeys [email protected]

:/sys/update

Enter passphrase for key './id_rsa': mysecretpassphrase publickeys 100% |***************************************************| 5 00:00

3. Perform an SFTP file transfer to the device using Account Password authentication. sftp -i ./id_rsa [email protected] [email protected]'s password: admin123 (Always use same password as admin)

sftp>

The user is presented with the SFTP prompt allowing interactive file transfer and directory navigation.

4. Perform an SFTP file transfer from the device using Public Key with Passphrase authentication sftp -i ./id_rsa [email protected]

Enter passphrase for key './id_rsa': mysecretpassphrase

sftp>

The user is presented with the SFTP prompt allowing interactive file transfer and directory navigation.

1.1.1.7 Recommended SSH Client Tools

Spectracom does not make specific recommendations as to which specific SSH client, SCP client, or

SFTP client tools. However, there are many SSH based tools available at cost or free to the user.

Two good, free examples of SSH tool suites are the command line based OpenSSH running on a

Linux or OpenBSD x86 platform and the excellent and free putty SSH tool suite.

The OpenSSH tool suite in source code form is freely available at www.openSSH.org

though you must also provide an OpenSSL library, which can be found at www.openssl.org

.

The putty SSH tools and instructions regarding their use can be found at:

HTTP://www.chiark.greenend.org.uk/~sgtatham/putty/

Note that it is strongly recommended to exit all SSH client sessions preferably using the “exit” command or “control-C” to avoid leaving the sshd daemon running. Exiting the putty tool (or SSH clients tools) by selecting the windows “X” button can leave the SSHd session running and result in

TTS220 Manual Rev C Page 31

refused connections until it times out after extremely long timeout delays. In such a case a reboot might be preferable rather than waiting.

3.3 Configuring HTTPS

3.3.1 Overview

The OpenSSL library provides the encryption algorithms used for secure HTTP (HTTPS). The

OpenSSL package also provides tools and software, which is used to create x509 Certificate

Requests, Self Signed Certificates and Private/Public Keys. The secure Spectracom products use

OpenSSL library with a simple GUI interface to create certificate Requests and self-signed certificates. Users can then send these certificate requests to an external Certificate Authority (CA) for the creation of a third party verifiable certificate or use an internal corporate CA. If a Certificate

Authority is not available the user can simply use the self-signed certificate that comes with the unit until it expires or create their own self-signed certificates to allow the use of HTTPS.

Each Spectracom secure product comes with a default Spectracom self-signed certificate, which will outlast the product warranty. The typical expiration of the certificate is about 10 years. HTTPS is available using this certificate until this certificate expires. If deleted however, this certificate cannot be restored.

For more information on OpenSSL please see www.openssl.org

.

The user is has the option of deleting the current certificate, certificate requests and private key.

To choose the delete option simply check the delete checkbox and press the submit button at the bottom of the screen. Once the current certificate is deleted HTTPS is unavailable.

TTS220 Manual Rev C Page 32

Figure 3.3.2-1 Deleting SSL Certificate, Certificate Request and Private Key Files

3.3.3 Restoring Self Signed Certificates and Private Keys

The user has an option to restore the last self signed certificate and private key created by the user.

To restore these files the user needs to select the “Restore User’s Self Signed Certificate and Private

Key” checkbox. The user then selects the submit button at the bottom of the screen. The default

Spectracom self-signed certificate and private key cannot be restored when deleted.

Figure 3.3.3-1 Restoring user’s Self Signed Certificate and Private Key Files

3.3.4 Creating Self Signed Certificates, a Private Key, and a Certificate Request

The user can create a customer specific x509 self-signed certificate, an RSA private key and x509 certificate request using the Web UI. RSA private keys are supported because they are the most widely accepted. At this time DSA keys are not supported.

The user is required to select a signature algorithm, a private key passphrase of at least 4 characters, a private key bit length, the certificates expiration in days and at least one of the remaining fields. It is recommended that the user consult their Certificate Authority for the required fields in an x509 certificate request. Spectracom recommends all fields be filled out and match the information given to your certificate authority. For example, use all abbreviations, spellings, URLs, and company departments recognized by the Certificate Authority. This helps in avoiding issues with the Certificate

Authority having issues to reconciling certificate request and company record information.

If using only self-signed certificates the user should choose the fields based upon the company’s security policy.

A sample input screen to create a certificate request is shown below.

TTS220 Manual Rev C Page 33

Figure 3.3.4-1 Creating a new Certificate Request and Self Signed Certificate

Note that it can take several minutes for the certificate request, the private key, and self-signed certificate are created. The larger the key the longer amount of time is required. It is recommended that a key bit length be a power of 2 or multiple of 2. The key bit length chosen is typically 1024, but can range from 512 to 4096. Long key bit lengths of up to 4096 are not recommended because they can take hours to generate. The most common key bit length is the value 1024.

The user is provided with several signature algorithm choices. The signature algorithm or message digest is most commonly MD5. Other secure options include SHA1 and RMD160.

Consult your Web Browser documentation and Certificate Authority for key bit lengths and signature algorithms supported.

If a system is rebooted during this time, the certificate will not be created. When the operation is completed, the user will see a certificate request in the certificate request text box. A digital file copy of the certificate request can be found in the /sys/update directory with the file name cert.csr. This file

TTS220 Manual Rev C Page 34

can be retrieved using FTP, SCP or SFTP. The certificate request can also be cut and paste from the certificate request text box on the Web UI.

Once the processing to create the certificate request, RSA private key and self-signed certificate is completed the Web UI will display the certificate request.

A certificate request is shown below.

Figure 3.3.5-1 A new Certificate Request and Self Signed Certificate

The user can submit this certificate request to the company’s Certificate Authority for a real verifiable, authenticable third party certificate. Until this certificate is received the user’s self-signed certificate displaying the information shown above can be used.

The secure Spectracom products web server will load this new self-signed certificate and private key after the user selects a few more web page options or when the user selects the “Exit connection to product” button at the top of the screen. The user will see a pop up window in Windows operating systems. The certificate and be installed or viewed using this pop up window. Other operating systems may vary in how they install and accept certificates. External Internet access may be required by your Certificate Authority to verify your third party certificate.

TTS220 Manual Rev C Page 35

After your Certificate Authority issues you a Certificate you need to install it on the secure

Spectracom product. Certificates may be installed via the Web UI and stored. Or they may be copied to the /sys/update directory using file transfer and installed using the Web UI.

A sample certificate installation using the Certificate text box on the Web UI is shown below.

Figure 3.3.6-1 Installing a new Certificate

The user needs to cut and paste the certificate into the Update Certificate text box and select the checkbox. The user then enters submit at the bottom of the page and the current self-signed certificate is overwritten.

If the file transfer method is chosen FTP, SCP, SFTP may be used to copy the certificate text file to the /sys/update/ directory using any file name. The user then selects the “Update Certificate with file named” check box and enters the file name in the space. The user then enters submit at the bottom of the page and the current self-signed certificate is overwritten with the specified file name.

In both cases the secure Spectracom product’s web server loads this new self-signed certificate and private key after the user selects a few more web page options or when the user selects the “Exit connection to product” button at the top of the screen.

3.3.7 Using Externally generated Certificates and Private Keys

The user is provided with another means to load certificates and RSA private keys onto the secure

Spectracom product. Spectracom does not recommend this method of external private key generation. It requires the assumption the user creates an x509 certificate and RSA private key fully compatible with the OpenSSL library version used in this product. There is no limit on the private key bit length. Longer more secure key bit lengths may be used up to the maximum length supported by

TTS220 Manual Rev C Page 36

OpenSSL. Only the shown digest algorithms may be used. Only RSA private keys are supported.

Both the certificate and the private key must be in PEM format.

The user may install the externally generated certificate and private key using the Web UI. A sample external private key and certificate install are shown below.

Figure 3.3.7-1 Using External Certificate and Private Key

Both the private key and the certificate should be installed at the same time.

It is strongly recommended that HTTPS be used to install the private key otherwise it is transferred in the clear. The original private key must be kept in an extremely secure location, offline or deleted after HTTPS transfer to ensure the security of this method.

The private key and certificate can also be installed using file transfer and the Web UI. The user simply needs to transfer the private key and certificate files to the /sys/update directory using either

SCP or SFTP. Once the files are transferred the user simply selects the “Update Certificate with file named” and “Update Private Key with file named” checkbox and provide the respective file names.

The user then enters the submit button.

In both cases the secure Spectracom product’s web server loads this new self-signed certificate and private key after the user selects a few more web page options or when the user selects the “Exit connection to product” button at the top of the screen.

Spectracom does not encourage the use of this method except for customers with very specific reasons to control their key generation.

To successfully use this means of private key and certificate generation the user must correctly create a certificate and RSA private key which complies with the requirements of the currently used

OpenSSL release. To safely transfer the private key to the secure Spectracom product the user must

TTS220 Manual Rev C Page 37

securely install the private key. A secure install is possible using HTTPS, SCP or SFTP. A point-topoint transfer between a standalone PC and a secure Spectracom product using a cross over cable would also be a very secure way to install this private key especially if used in conjunction with

HTTPS, SCP, or SFTP. The use of HTTP or FTP with this install method for private keys cannot be considered and is considered insecure.

3.3.8 What to do if you cannot get into a secure Spectracom Product

Spectracom assumes that the customer is responsible for the physical security of the product.

Spectracom secure products are required to be locked in a secure enclosure, cabinet or room.

Unauthorized persons are not to be given access to the product nor should a serial cable and terminal program be attached unless the system administrator is configuring or performing maintenance.

If your company disables HTTPS, loses the system passwords, allows the certificate to expire, deletes the certificate the certificate and private keys and deletes the Host Keys or forgets the passphrase access to the secure Spectracom product can become denied.

To restore access to your system you must utilize the setup port to restore the admin accounts default password. The admin account can then be used to enable HTTP using the “net HTTP” command. Contact Spectracom Technical Support for details on how to do this.

TTS220 Manual Rev C Page 38

3.4 NTP/SNTP

NTP (Network Time Protocol) and SNTP (Simple Network Time Protocol) are client-server protocols for synchronizing the time on IP networks. NTP provides greater accuracy and error checking than

SNTP. NTP and SNTP can be used to synchronize the time on any computer equipment that is compatible with the Network Time Protocol. This includes CISCO routers and switches, UNIX machines and Windows machines with a suitable client. To synchronize just one workstation, several freeware or shareware NTP clients are available on the Internet. The software running on the PC determines if NTP or SNTP is used.

The NTP setup page provides full control of the operation of your NTP server. Follow the simple steps below to quickly set up your unit as an NTP server on your network.

Connect to your unit through its web-based interface.

Click on the System Setup link on the bottom of the screen to open the menu for system configuration.

TTS220 Manual Rev C

Figure 3.4-1: NTP Screen

Page 39

Click on the NTP link on the left side of the screen to enter the NTP setup page. Note: you must be logged in as an administrator to modify the NTP settings.

The NTP server can operate in Unicast mode, multicast mode, or both concurrently. Simply place a checkmark in the boxes labeled “NTP Unicast” or “NTP Multicast …” or in both.

In the Unicast mode the unit will send a time packet response to an NTP “request” sent by a client.

The Spectracom NTP server can handle up to 570 NTP requests per second typical without MD5 encryption (read below).

The Multicast mode sets the unit to send out NTP time packets at a user-specified rate. Enter the desired frequency in seconds into the Multicast field on the setup page.

Secure data transfer can be enabled using MD5 Security Protocol. The Encryption feature does not mean that the time packet will be encrypted. This feature is used to authenticate that the received time packet came from the desired time-server.

To use the authentication in Unicast mode both the NTP client and the Spectracom NTP server must contain the same “Key ID – Key String” pairs and the client must be set to use one of these MD5 pairs. The key ID must be a number between 1 and 4,294,967,295; the key string can contain any alphanumeric characters and can be from 1 to 16 characters long. No duplicate key IDs are permitted.

To enable MD5 authentication in Unicast mode, check the “Secure Mode” box under the NTP Unicast setting. The unit will respond to any request which contains an authentication checksum, and will in turn append an authentication checksum based on the MD5 (Message Digest 5) hashing algorithm.

To use MD5 authentication in multicast mode, check the “Use MD5 authentication with key …” box under the NTP Multicast setting, and enter the key ID to be used for authentication when sending out

NTP packets.

The Session statistics checkbox will enable or disable logging of NTP usage statistics. This is displayed as part of the status and log. Refer to the status and log section for details.

At any time during the setup, press “Submit” to save the settings or “Reset” to restore the settings to their previous state.

Spectracom cannot provide technical assistance for configuring and installing NTP on Unix-based applications. Please refer to http://www.ntp.org/ for NTP information and FAQs. Another good source for support is the Internet newsgroup at news://comp.protocols.time.ntp/ .

Spectracom can provide support for the Windows NT and Windows 2000 time synchronization. Refer to the Spectracom Web page for application notes at: http://www.spectracomcorp.com/computernetworks.html

.

TTS220 Manual Rev C Page 40

3.4.3 Application Note: MD5 Authentication using a Cisco Router

According to the Cisco Manual located on their website to configure NTP Authentication the user would use the following commands: set ntp key public_keynum {trusted | untrusted} [md5 secret_keystring]

where:

public_keynum is a number from 1 to 4,292,945,295 and is a key ID number

“trusted" is used to activate the key, "untrusted" to disable the key md5 means the keyword (the type of key, Cisco only uses md5)

"secret_keystring" is the key value, it is from 1 to 32 printable characters.

To interoperate with the Ethernet Time Server, the "secret_keystring" must be eight printable characters and the public_keynum must be a number from 1 to 6.

For example: to define key id number 3 with the secret_keystring TICKTOCK" would require the following commands into the Cisco Router: set ntp key 3 trusted md5 TICKTOCK

This will define the key and enable it in one step. The command "show ntp" can be used to display the key definitions.

On the NetClock side you would enable MD5 authentication with key 3 and then enter TICKTOCK into the Key Table with ID 3.

TTS220 Manual Rev C Page 41

3.5 Local System Clocks Setup

You can define up to 5 Local Clocks or Time Zones to be used with any of the remote serial interfaces, event timers, or front panel displays. Once defined, these Local Clocks can be used by any interface and will cause that interface to be automatically updated for its time zone and DST conditions. To configure a local clock:

Connect to the web interface after booting the unit. Login to administrator-level mode if changes are desired. Choose "System Setup" from the bottom frame, and the “Local System Clocks” from the left frame and you will see this screen:

Figure 3.5-1 Local System Clocks Setup Screen

Choose “Create/New” and click on the “Submit” button. This screen will appear ():

TTS220 Manual Rev C Page 42

Figure 3.5-2 Time Zone and DST Setup Screen

Enter any name you wish for the Local Clock Name, up to 20 characters long. It can be any meaningful name that helps you know your point of reference (example: New York, Wall Clock in

Bldg27, Eastern HQ, etc.)

Time Zone Setup:

This field allows the user to manually select which time zone to use when sending data. The default is UTC.

DST Setup:

Four options for Daylight Savings Time are available here. There is no DST observed. This is the default.

Manually specify a pre-defined DST rule.

• Europe

• North America

• Australia-1

• Australia-2

TTS220 Manual Rev C Page 43

Define a DST rule by the [n]th [day of week] in [month] method.

Define a DST rule by the [day of month] in [month] method.

Example 1: To create a Local System Clock to UTC+1 with no DST rule:

1. Connect to the web interface of the unit.

2. Login to administrator-level mode and browse to the System Setup, Local System Clocks page.

3. Select Create/New and assign the clock a meaningful name.

4. Click on the “Manually Defined UTC Offset” button.

5. Select 'UTC+1:00' from the Time Zone pull down menu.

6. Select the 'No DST rule' radio button.

7. Review the changes made and click Submit. The browser will display the status of the change.

Example 2: To configure an RS-485 port to go in DST at 2:00am on the 3rd Friday in April and out of

DST at 1:00am on the 1st Sunday in October, with a DST change of 1 hour:

1. Connect to the web interface of the unit.

2. Login to administrator-level mode and browse to the System Setup, Local System Clocks page.

3. Select Create/New and assign the clock a meaningful name.

4. Under “DST Setup”, select the 'Manually defined by week and day' radio button.

5. Enter/select '3rd', 'Friday', 'Apr', '2', and '0' in the DST In Date section.

6. Enter/select '1st', 'Sunday', 'Oct', '1', and '0' in the DST Out Date section.

7. Enter '1' and '0' in the corresponding fields of the Change Amount section.

8. Review the changes made and click Submit. The browser will display the status of the change.

9. Browse to the “Interface Setup, Remote Port” page and Select the proper System Clock.

TTS220 Manual Rev C Page 44

Example 3: To change a Local System Clock to be in DST at 1:01am on October 2nd and out of DST at 2:00am on April 17th, with a DST change of 30 minutes:

1. Connect to the web interface of the unit.

2. Login to administrator-level mode and browse to the System Setup, Local System Clocks page.

3. Select the desired Clock Name.

4. Select the 'Manually defined by month and day' radio button.

5. Enter/select ‘2’, ‘Oct’, ‘1’, and ‘1’ in the DST In Date section.

6. Enter/select ‘17’, ‘Apr’, ‘2’, and ‘0’ in the DST Out Date section.

7. Enter ‘0’ and ‘30’ in the corresponding fields of the Change Amount section.

8. Review the changes made and click Submit. The browser will display the status of the change.

3.5.1 Time Zone and DST

How to set up Time Zone and DST Rule:

The unit will allow you to define different Time Zone and DST rules for different Interfaces and a front panel display (if so equipped). In order to use this feature properly, users have to know the correct

Time Zone offset and DST rule for your area.

The general Time Zone and DST rule information can be found from the following web sites: http://www.worldtimeserver.com/ , http://webexhibits.org/daylightsaving/b.html

.

Since the Time Zone and DST rules are set up for each Interface and front panel display separately, you should click the “Interface setup” hyperlink, and then select the Interface you want to modify.

Then you will see the Time Zone setup and DST setup option on the web page.

Time Zone

Under the “TIME ZONE SETUP”, you will see two choices:

• Automatically configure to unit’s physical locality

• Manually defined UTC offset

TTS220 Manual Rev C Page 45

Auto Time Zone

By selecting this option, the unit will compute the Time Zone Offset automatically based on the location of the unit provided by GPS receiver.

If you select this feature before the GPS receiver completes the position calculation, a message will be displayed to explain that this feature is not valid until the position is available.

If you select this feature after the GPS receiver determines its position, the computed Time Zone

Offset information will be shown.

Note: that Automatic Time Zone calculations are imprecise because the time zones are determined by local political boundaries and may change often. This feature is made available as an aid only.

To apply the computed Time Zone, select the check box for the desired Interface.

Manual Time Zone

A drop down box is provided for the choice. Left click the drop down box and select the time zone offset you want to use.

Note: All of the Time Zone Offset drop-downs in the web browser are configured as UTC plus or minus a set number of hours. For Eastern, chose UTC–5, for Central, chose UTC-6, for Mountain, chose UTC-7 and for Pacific, chose UTC-8.

DST rule

Under the “DST SETUP”, you will see four radio buttons. , The four options are “No DST rule, always standard time”; “Manually defined by region”; “Manually defined by week and day”; “Manually defined by month and day”.

No DST Rule, always standard time

This option should only be used when you do not want to apply any DST rule to this Interface output.

Auto DST

This feature is designed to compute the DST rule automatically based on the location of the unit provided by GPS receiver.

If you select this feature before the GPS receiver completes the position calculation, a message will be displayed to explain that this feature is not valid until the position is available.

If you select this feature after the GPS receiver determines its position, the computed DST rule information will be shown.

Note: that Automatic DST calculations are imprecise because the rules for DST are determined by local political boundaries and may change often. This feature is made available as an aid only.

To apply the computed DST rule, select the check box for the desired Interface.

Manually defined by region

TTS220 Manual Rev C Page 46

This option is recommended if you do not need to define a special rule. Under this option, there is one drop down box. Left click the drop down box and you will see four regional choices: “Europe”, “North

America”, “Australia-1” and Australia-2”.

The official DST rules for these four regions are as follows:

Europe

Start: Last Sunday in March at 1am UTC

End : Last Sunday in October at 1am UTC

North America

Start: First Sunday in April at 2am local time

End : Last Sunday in October at 2am local time

Australia-1

Start: Last Sunday in October at 2am local time

End : Last Sunday in March at 3am local time

Australia-2

Start: First Sunday in October at 2am local time

End : Last Sunday in March at 3am local time

Manually defined by week and day

This option is provided for advanced users. You can input start time, end time and the hour to change for the daylight saving. By selecting this option, the DST rule can be defined based on the weekday, week, and month of the local time you defined for this Interface.

Manually defined by month and day

This option is provided for advanced users. You can input start time, end time and the hour to change for the daylight saving. By selecting this option, the DST rule could be defined based on the day and month of the local time defined for this Interface. If you select the February 29th as the start time or end time, the unit will treat it as March 1st during non-leap year.

TTS220 Manual Rev C Page 47

3.6 Interface Setup

Using the web interface to configure any Interface:

The product can have RS-232 ports (also called Serial Ports) and RS-485 ports (also called Remote

Output Ports) that support independent output of date/time stamps. Optionally the product can support Front Panel Displays providing human readable visual output. The web interface is the method by which these can be configured, and the available options are described below:

Baud Rate:

This is the speed at which this Interface will output data. Supported values are 1200, 2400, 4800, and 9600. 9600 baud is the default.

Data Format:

This is the format in which data/time stamps are output. Available formats are 00, 01, 02, 03, 04, and

90; and are described in detail in the "Data Format" section above. Format 00 is the default.

Request Char (feature not available on RS-485 port):

If Multicast is selected, the unit will automatically broadcast once per second. If User Defined is selected, the unit will only send data upon reception of the character in the textbox. The default is the user-defined character 'T'.

System Clock:

This field allows the user to select which Local System Clock (time zone) to use when sending data.

The default is UTC. See Section 3.5 Local Systems Clocks for more information on how to set these.

To configure a product's Interface via web interface:

Connect to the web interface after booting the unit. Login to configuration- or administrator-level mode if changes are desired. Choose "Interface Setup" from the bottom frame, and the desired port from the left frame. Serial Ports correspond to RS-232 outputs and Remote Output Ports correspond to RS-485 outputs. All fields will display the current system settings. At the bottom of the frame, clicking Reset will revert any changes made at this window since last pressing Submit.

TTS220 Manual Rev C Page 48

Figure 3.6-1: Interface Screen

Example 1: To configure an RS-232 port to run at 2400 baud, and output Format 90 to run in Eastern

Standard Time:

1. Connect to the web interface of the unit.

2. Login to configuration- or administrator-level mode and browse to the Serial Port page.

3. Select '2400' from the Baud Rate pull down menu.

4. Select '90' from the Data Format pull down menu.

5. Select a Local System Clock defined for the proper time zone.

6. Review the changes made and click Submit. The browser will display the status of the change.

TTS220 Manual Rev C Page 49

3.7 Front Panel Display

Using the web interface to configure the Front Panel Display:

You can change the Front Panel Display formats to suit your needs. Both of the displays are independently programmable. The left side display is LCD 1, the right side is LCD 2.

Figure 3.7-1: Front Panel Display Screen

LCD # Display Format:

Each of the two LCD Displays has a user selectable Display Format. This display format defines the type of information provided the user. The following is description of the nine available display options:

1. None - No Display is shown, LCD is blank.

2. Product - Product Name, Hardware Revision and Firmware Revision is shown for several seconds after which the default display is resumed.

3. Revision - Firmware Revision of Data Port outputs is shown for several seconds after which the default display is resumed.

TTS220 Manual Rev C Page 50

4. Time View - Time is displayed with Large Font for Hours:Minutes and Small Font for

Seconds.

5. Time - Time is displayed in Large Font for Hours:Minutes:Seconds.

6. Day of Year - Day of Year (DOY) is displayed in Large Font.

7. Date - Date is displayed in a user selectable format in a Large Font.

8. Date-Time - Date and Time are displayed in a Small Font. Date is displayed in the user selected format.

9. DOY-Time - Day of Year and Time are displayed in a Small Font.

LCD1 Display Format Setup:

This field allows the user to select the Display Formats described above to be used for this LCD screen.

LCD2 Display Format Setup:

This field allows the user to select the Display Format described to be used for this LCD screen.

Date Format Setup:

This field allows the user to select the Date Format. The available choices are as follows (Where

YY=Year, MM=Month, DD=Day):

MM_DD_YY, DD_MM_YY, YY_MM_DD, MM_DD_YYYY, DD_MM_YYYY, YYYY_MM_DD

Time Format Setup:

This field allows the user to select 12 Hour or 24 Hour time format.

Font Setup:

This field allows the user to select one of the supported Fonts for the Numeric display fields for Date,

Time and Day of Year. The available choices are as follows:

Arial - Arial style font (This is the factory default)

Mark - Curved, strong font

LED - LED Style rectangular thick font

Thin - LED Style rectangular thin font

System Clock Setup:

This field allows the user to manually select which time zone to use when displaying time. See

Section 3.5 on Local System Clocks.

To configure a product's Front Panel Display via web interface:

Connect to the web interface after booting the unit.

Login to configuration- or administrator-level mode if changes are desired.

Choose "Interface Setup" from the bottom frame, and the “Front Panel Display” from the left frame.

All fields will display the current system settings. At the bottom of the frame, clicking Reset will revert any changes made at this window since last pressing Submit.

TTS220 Manual Rev C Page 51

Example 1: To configure the Front Panel Display to show Day of Year and Time View displays using an Arial font while displaying 12 Hour, Local time.

1. Connect to the web interface of the unit.

2. Login to configuration- or administrator-level mode and browse to the Front Panel Display page.

3. Select 'Day of Year' from the LCD1 Display Format pulldown menu.

4. Select 'Time View' from the LCD2 Display Format pulldown menu.

5. Select '12 Hour' from the Time Format pulldown menu.

6. Select ‘Arial’ from the Font pulldown menu

7. Select the Time Zone by selecting the appropriate System Clock in the pulldown menu.

8. Review the changes made and click Submit. The browser will display the status of the change.

TTS220 Manual Rev C Page 52

3.8 Alarms

The operational status of the NetClock can be monitored via the condition of its alarms. The alarm states may be obtained using any of the following mechanisms:

Timer/Alarm Relays output connector

For detailed information about the rear panel connectors, see the “Rear Panel Functions” section.

For detailed information about configuring the relays to signal alarms, see Section 5.3.1

.

System Status displayed on a web browser

Dynamic system information including the current state of the alarms can be obtained by clicking

“Status & Log” along the bottom of the main browser screen, followed by clicking “System Status” on the left side of the screen. The alarm status is displayed in a table labeled “Dynamic System

Information”

Alarm transition information is recorded in the alarm log.

An alarm is asserted whenever any of the following conditions exist:

Time Sync Alarm: The period of time allotted for operation without tracking a satellite has expired. Factory default period is 2 hours. This is a Major alarm.

GPS Receiver Fault: The CPU is unable to communicate with the GPS receiver. This is a

Major alarm.

Frequency Error*: Measured oscillator frequency error exceeds 1 x 10 alarm.

-7

. This is a Major

Power Failure: The NetClock/NTP has lost power. This is both a Major and Minor alarm.

Antenna Problem: The antenna sense circuitry warns when the antenna is not connected or a cable short or open is detected. This is a Minor alarm.

Oscillator Adjust*: Warns that the TCXO time base oscillator requires an adjustment to maintain operation within specifications. This is a Minor alarm.

* These alarm conditions only exist on products that feature a corrected oscillator (TTS220, TTS240, TTS260, 9183).

TTS220 Manual Rev C Page 53

An alarm is asserted whenever any of the following conditions exist AND the alarm has been enabled on the alarm setup screen via a web browser:

User-defined Alarm: The user-specified period of time allotted for operation while tracking less than a user-specified number of satellites has expired. This can be a

Major and/or Minor alarm.

Software Fault: One or more software sub-systems has experienced a major run-time error. This is a Major alarm.

Figure 3.8-1: Alarm Setup Screen

User-defined alarms are configured using the Alarm Setup screen (Figure 3.8-1) from a web browser.

The Alarm Setup screen may be viewed by clicking “System Setup” along the bottom of the main browser screen, followed by clicking “Alarm” on the left side of the screen. The default is a major alarm for tracking less than 1 satellite for 5 seconds.

NOTE: The Alarm Setup screen will not allow modification of any of the fields unless you have logged into the system in either configuration mode or administration mode.

Clicking the check box to the left of a particular user-defined alarm will enable that alarm condition.

Each alarm condition may be set to exist for a specified duration before activating the alarm. This is done by filling in the Timeout fields directly beneath the alarm condition.

TTS220 Manual Rev C Page 54

3.9 Relays

3.9.1 Configuring the relays

The operational status can be monitored remotely using the TIMER/ALARM RELAYS connector on the rear panel. This connector provides the common, NO and NC contacts for three relays. These relays can be connected to an alarm lamp, horn, or other indicator to warn when the clock accuracy or operation has been affected, or to signal the triggering of a programmed event. The relay contacts are rated at 2.0 amps, 30VDC.

The web interface allows the assignment to each relay of one of three functions: Major Alarm, Minor

Alarm, and Event Timer. For more details on these functions, see the "Alarm Outputs" section and the "Configuring the Event Timer" section.

To configure or view the relay assignments:

connect to the web interface. If configuring, login to configuration mode (or administration mode). If just viewing, no login is needed. Along the bottom of the interface select Relay Setup. Along the left hand side select Relay Output. A page showing the relays along the left side and the functions along the top will appear. To assign a function to a relay, click the dot that lines up with both the function and the relay. If just viewing, no assignments can be changed. See the below example.

Figure 3.9-1 Relay Output Screen

TTS220 Manual Rev C Page 55

Example: To assign “Major Alarm” to relay 1, “Minor Alarm” to relay 2, and “Event Timer” to relay 3, click on the following dots.

Major alarm to relay 1: the dot in row 1, column 1.

Minor alarm to relay 2: the dot in row 2, column 2.

Event Timer to relay 3: the dot in row 3, column 3.

A single relay can only be assigned one function but a function can be assigned to multiple relays.

By default, all three relays are assigned “Major Alarm.”

TTS220 Manual Rev C Page 56

3.10 Event Timer

3.10.1 Configuring the Event Timer

The web interface allows for the configuration of 128 events that can turn any one of the event timer relays on or off. Make sure the rear panel relay that is going to be associated with an event is configured to be the event timer relay in order to use this feature (see Section 3.5.1

for details on relay configuration).

To configure the events:

Connect to the web interface. Login to configuration mode (or administration mode).

Along the bottom of the interface select Relay Setup.

Along the left hand side select Event Timer Relay.

Figure 3.10-1: Event Timer Relay Screen

TTS220 Manual Rev C Page 57

A new page will load. This is where the user specifies which event to edit/view. If any events are already configured, they will be displayed by event number on this page. There are no requirements on the order of the events; each one is completely independent of the others. Enter the number of the event that you wish to edit/view and click the Edit/View button.

Now a page that displays the settings of the selected event appears and if logged in to configuration mode (or administration mode) the settings can be changed.

Choose a Time Zone

On the left side pane, select “Set Event Clock”. Choose an already defined Clock (Time Zone) or define a new one. See Section 3.5 for more details on Local System Clock settings.

Note: All times entered for the Event Timers will use the same Local System Clock reference for

Time Zone and DST rules. It is best to choose this reference first before entering your schedule.

TTS220 Manual Rev C

Figure 3.10-2 Event Timer Relay Screen

Page 58

Relay#: Select the relay number that the event is to be associated with.

Enabled/Disabled/Delete: If the event is enabled, the event will occur when scheduled. If the event is disabled, it will not occur at the scheduled time, but will still appear in the list of scheduled events on the previous page. If the event is deleted, all fields of event are cleared and it is removed from all event lists.

ON/OFF: Each event can turn the specified event timer relay on or off.

The next section of the page describes when the event will occur and how often it will occur. The relay can be set to occur hourly, daily, weekly, monthly, and yearly.

Hourly: The event will happen every hour at the minute, second, and millisecond that is specified (within 100 milliseconds).

Daily: The event will happen every day at the hour, minute, second, and millisecond specified (within 100 milliseconds).

Weekly: The event will happen every week at the weekday, hour, minute, second, and millisecond specified (within 100 milliseconds).

Monthly: The event will happen every month at the day of month, hour, minute, second, and millisecond specified (within 100 milliseconds). If the day is set to be a day that isn't in short months, the event will happen on the last day of the short months.

Yearly: The event will happen every year at the month, day of month, hour, minute, second, and millisecond specified (within 100 milliseconds). If the month and day of month are programmed for February 29th (this can only be done while currently in a leap year), the event will happen on March first on non-leap years and February 29th on leap years.

If configuring, clicking the submit button will save the settings. The reset button undoes any changes that were made before the submit button is clicked.

Example: Program event relay #3 to turn on at 5:00PM (Eastern Standard Time) for five seconds every day.

Get to the Event Timer Relay page and “Edit/View” event 1.

Configure the event as relay #3, enabled, and to turn the event relay on daily at 22:00:00.000. Click the submit button.

If all the information was correctly entered, the “Event Scheduler update successful.” message will appear.

Click Event Timer Relay and the newly configured event will appear in the list of configured events.

“Edit/View” event 2.

TTS220 Manual Rev C Page 59

Configure the event as relay #3, enabled, and to turn the event relay off daily at 22:00:05.000. Click the submit button.

If all the information was correctly entered, the “Event Scheduler update successful.” message will appear.

Click Event Timer Relay and the newly configured events will appear in the event list.

To view the events:

Connect to the web interface. No login is needed to just view the events.

Along the bottom of the interface select Relay Setup.

Along the left hand side you have two options to view the events:

Event Timer Relay: Selecting this option will display all events that are either, enabled or disabled.

The events are ordered by event number (1-128).

Current Event Schedule: Selecting this option will display a list of only enabled events. The events are ordered by next occurrence.

TTS220 Manual Rev C Page 60

3.11 Logs

Note: The times indicated in all log entries are UTC (No correction for Local time / Daylight Saving

Time).

3.11.1 Display Alarm Log

To Display the Alarm log do the following:

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http://10.10.200.1 (or your IP address).

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item. On the left side menu, select the "Alarm Log" item. The Alarm History Log is then displayed in the center of the screen. Each time a change in alarm status occurs an alarm log is created. An alarm log includes the UTC time and date of the log, the alarm relay status and lists the conditions causing the alarms. The alarm log is displayed one page at a time, and can be navigated by using the scroll bar control on the right hand side.

Example response:

TIME= 10:17:19 DATE= 2000-03-21 STATUS CHANGE

ALARM RELAY= OFF

ACTIVE ALARMS: NONE

TIME= 13:51:29 DATE= 2000-05-05 STATUS CHANGE

ALARM RELAY= ON

ACTIVE ALARMS: MINOR

Antenna Problem

TIME= 15:51:30 DATE= 2000-05-05 STATUS CHANGE

ALARM RELAY= ON

ACTIVE ALARMS: MAJOR AND MINOR

TIME SYNC ALARM

Antenna Problem

TIME= 18:23:39 DATE= 2000-05-05 STATUS CHANGE

ALARM RELAY= ON

ACTIVE ALARMS: MAJOR

Time Sync Alarm

TIME= 18:24:44 DATE= 2000-05-05 STATUS CHANGE

ALARM RELAY= OFF

ACTIVE ALARMS: NONE

In the example above, the antenna cable was damaged at 13:51:29 on May 5, 2000. Note that a

Minor Alarm was asserted at that time due to an "Antenna Problem". Since no GPS signal could be received, the Sync Time-out counters expired, causing a Major Alarm due to loss of time sync. The cable was repaired at 18:23:39, clearing the Minor and Antenna Problem messages. The receiver then reacquired and qualified at least one satellite for one minute, which cleared all alarms at

18:24:44.

3.11.2 Display Dial Out Log

If you have the optional Dial Out Modem Interface, display the log by doing the following:

TTS220 Manual Rev C Page 61

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http://10.10.200.1 (or your IP address).

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item. On the left side menu, select the "Dial out Log" item. The Dial out History Log is then displayed in the center of the screen. Each time an operation in the dial out process occurs, a dial out log entry is created. A dial out log includes the UTC time and date of the log, the operation that was just completed or the status from the previous operation. The log can be navigated by using the scroll bar control on the right hand side.

Example response:

TIME= 15:48:21 DATE= 2004-03-22

Modem dial out to 9 1-303-494-4774.

TIME= 15:48:03 DATE= 2004-03-22

Synced clock to modem time.

TIME= 15:48:55 DATE= 2004-03-22

Dial out successful. Sync'ing system 1PPS.

TIME= 15:48:58 DATE= 2004-03-22

Synced 1PPS to modem time.

In the example above, the unit initiated a dial out at 15:48:21 to the number (9)1-303-494-4774. It receives an in-sync time message at 15:48:03 and adjusted the unit’s clock to the modem time. At

15:48:55 it finished the call and disconnected the modem from the phone line. It then process the collected time messages and finally synced the unit’s 1PPS to the modem time’s 1PPS at 15:48:58.

During the dial out operation, errors and timeouts can occur. These are also logged in the Dial out log. The exception log entries are as follows:

Failed to sync during call:

This log entry records a dial out attempt that was successful in communicating with the modem time reference, but was unable to sync the time messages during the call.

Dial out failed or aborted:

This log entry records a dial out attempt that was aborted due to system state change or an error response from the modem. For example, if the unit regain time sync with GPS during a dial out attempt he operation will be aborted. Changing the setup serial port mode to console mode or receiving a BUSY message from the modem can also trigger this log entry. This log entry is usually following with a disconnect command to the modem.

Timeout occurs, operation is aborted:

During time message acquisition and 1PPS sync process, if the process takes too long, it will be automatically aborted and retried if possible. For example, if a time message acquisition receive no response from the modem for two minutes, the operation is aborted and the dial out process is restarted again.

3.11.3 Display Operational Log

To Display the Operational log do the following:

TTS220 Manual Rev C Page 62

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address).

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item.

On the left side menu, select the "Operational Log" item.

The Operational History Log is then displayed in the center of the screen. The operational log response begins with a header containing all firmware version levels and the time and date since power up. Entries are made to this log when the following events occur:

Unit Started:

The unit started log contains a UTC time and date stamp.

This log is created when power is restored to the clock.

For example:

Unit Started 19:13:06 2003-07-29

First Satellite Acquired:

This log time stamps when the receiver acquires a satellite for the first time.

For example:

First Satellite Acquired 19:21:34 2003-07-29

GPS Signal Qualified:

This log entry records when the receiver acquires or re-acquires and qualifies at least one satellite for one minute. A satellite is considered qualified if the received vehicle ID number is greater than 1 and if the satellite can be used for Position Fix. The time and date contained in the log reflect UTC time.

For example:

GPS Signal Qualified 19:32:00 2003-07-29

System is synced to modem time: (For units with modem dial out feature)

This log entry records when the modem dial out software has just completed a dial out operation and was able to collect time message that was used to sync the unit’s time to the modem time. The date and time in the log reflect UTC time.

For example:

TIME= 18:36:15 DATE= 2004-03-13

Synced 1PPS to modem time.

Example response:

Spectracom Corporation Model 9189

Software Version 1.0.0 Date: 7/29/2003

Unit Started 19:13:06 2003-07-29

Serial Port 1 Version 2.03

Remote Port 1 Version 2.03

GPS Receiver = 12 Channel M12+ Version 2.0

TIME= 19:26:21 DATE= 2003-07-29

First Satellite Acquired

TTS220 Manual Rev C Page 63

Spectracom Corporation Model 9189

Software Version 1.0.0 Date: 7/29/2003

Unit Started 19:13:06 2003-07-29

Serial Port 1 Version 2.03

Remote Port 1 Version 2.03

GPS Receiver = 12 Channel M12+ Version 2.0

TIME= 18:36:15 DATE= 2004-03-13

Synced 1PPS to modem time.

The Operational log is output in a continuous format, and can be navigated by using the scroll bar control on the right hand side.

Note: The oscillator log is not available for rubidium-based units.

To Display the Oscillator log do the following:

Use a PC with a web browser and connect to the product by typing the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address)

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item.

On the left side menu, select the "Oscillator Log" item. The Oscillator Log is then displayed in the center of the screen. The oscillator log will list a history of oscillator disciplining events. Entries are made to this log when the following events occur:

Power on reset:

Time stamps the event of the unit recovering from a power cycle.

Coarse Adjust Mode:

Marks the beginning of the Coarse Adjustment of the oscillator. The coarse adjust samples and adjust the D/A setting to stabilize the oscillator to the desired frequency. Once the setting is close enough, the unit switches to Fine Adjust Mode.

Fine Adjust Mode:

Marks the beginning of the Fine Adjustment of the oscillator. This process begins once the Coarse adjust places the oscillator close to the desired frequency. The Fine Adjust mode will further tune the oscillator. The difference between coarse and fine adjust mode is that fine adjustment is done over a larger amount of samples and adjust the D/A slower than the Coarse adjust.

Reference 1PPS Unstable:

Time stamps the event when the 1PPS becomes unstable. When this happens, no disciplining will be performed until this situation is corrected.

Periodic Frequency measurement:

This is the most common entry in the oscillator log. This entry displays the timestamp followed by the current D/A settings. It also displays the current frequency error and the measured frequency count.

The Frequency error is calculated as:

Freq Error = (Measured Freq Count – Ideal Freq Count) / (Ideal Freq Count)

TTS220 Manual Rev C Page 64

Automatic D/A adjustment:

Usually, small D/A adjustments are made to keep the oscillator disciplined to GPS. These small adjustments are only sampled periodically and shown as part of the periodic frequency measurement described above. If a large adjustment is made to the D/A it is logged immediately to inform the user.

Example response:

TIME= 13:19:57 DATE= 2004-09-03 POWER ON RESET

TIME= 13:20:42 DATE= 2004-09-03 COARSE ADJUST MODE

TIME= 13:22:22 DATE= 2004-09-03 D/A= 7E46 FREQ ERROR= 1.22E-07 FREQ CNT= 1000000122

TIME= 13:22:48 DATE= 2004-09-03 FINE ADJUST MODE

TIME= 13:23:02 DATE= 2004-09-03 AUTOMATIC D/A ADJUSTMENT

D/A= 7E39 MATCH CNT= 47

TIME= 13:24:02 DATE= 2004-09-03 D/A= 7E38 FREQ ERROR= 4.00E-09 FREQ CNT= 1000000004

TIME= 13:25:42 DATE= 2004-09-03 D/A= 7E36 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:27:22 DATE= 2004-09-03 D/A= 7E37 FREQ ERROR= 1.00E-09 FREQ CNT= 1000000001

TIME= 13:29:02 DATE= 2004-09-03 D/A= 7E35 FREQ ERROR= 2.00E-09 FREQ CNT= 1000000002

TIME= 13:30:42 DATE= 2004-09-03 D/A= 7E35 FREQ ERROR= 2.00E-09 FREQ CNT= 1000000002

TIME= 13:30:51 DATE= 2004-09-03 AUTOMATIC D/A ADJUSTMENT

D/A= 7E33 MATCH CNT= 69

TIME= 13:32:22 DATE= 2004-09-03 D/A= 7E35 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:34:02 DATE= 2004-09-03 D/A= 7E32 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:35:42 DATE= 2004-09-03 D/A= 7E34 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:37:22 DATE= 2004-09-03 D/A= 7E35 FREQ ERROR= -1.00E-09 FREQ CNT= 999999999

TIME= 13:39:02 DATE= 2004-09-03 D/A= 7E35 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:40:42 DATE= 2004-09-03 D/A= 7E36 FREQ ERROR= -1.00E-09 FREQ CNT= 999999999

TIME= 13:42:22 DATE= 2004-09-03 D/A= 7E38 FREQ ERROR= 0.00E+00 FREQ CNT= 1000000000

TIME= 13:44:02 DATE= 2004-09-03 D/A= 7E34 FREQ ERROR= 3.00E-09 FREQ CNT= 1000000003

TIME= 13:45:42 DATE= 2004-09-03 D/A= 7E33 FREQ ERROR= 2.00E-09 FREQ CNT= 1000000002

TIME= 13:46:15 DATE= 2004-09-03 REFERENCE 1PPS UNSTABLE

TIME= 13:52:00 DATE= 2004-09-03 COARSE ADJUST MODE

TIME= 13:52:12 DATE= 2004-09-03 FINE ADJUST MODE

TIME= 13:52:15 DATE= 2004-09-03 AUTOMATIC D/A ADJUSTMENT

D/A= 7E3B MATCH CNT= 107

The example shows a unit that recovered from a power cycle. It immediately began coarse mode adjustment, followed by Fine adjustment. Periodic frequency measurements and Large D/A adjustments are then logged. After sometime, this unit loses a stable 1PPS reference. When the

1PPS reference is recovered, the unit began disciplining the oscillator again from coarse mode.

TTS220 Manual Rev C Page 65

The NTP statistics is controlled from the NTP configuration described in the NTP section of this manual. To display the NTP Statistics do the following:

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address)

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item.

On the left side menu, select the "NTP Statistics" item. The NTP Statistics is then displayed in the center of the screen as shown:

Figure 3.11-1 NTP Statistics

The overall statistics provides a quick overview of all the NTP activities from the unit while the client statistics displays the details of each client’s interaction with the unit. Invalid requests are colored in red to improve the readability of the statistic list. If you need to find a specific client, you can use the find (Ctrl + F) function of the browser and search for the client’s I.P. address.

TTS220 Manual Rev C Page 66

3.11.6 Display Event Relay Log

To Display the Event Relay log do the following:

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address)

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item.

On the left side menu, select the "Event Relay Log" item. The Event Relay Log is then displayed in the center of the screen. The event relay log will list a history of event relay actions. Entries are made to this log when the following events occur:

An Event Timer Relay is triggered to OPEN the relays.

An Event Timer Relay is triggered to CLOSE the relays.

Sample Response:

TIME= 13:09:09 DATE= 2003-07-30

EVENT RELAYS: OPEN

EVENT #: 3

TIME= 13:12:25 DATE= 2003-07-30

EVENT RELAYS: CLOSE

EVENT #: 7

The Event Relay log is output in a continuous format, and can be navigated by using the scroll bar control on the right hand side.

3.11.7 GPS Qualification Log

The GPS Qualification Log records the number of qualified satellites tracked each second. At the end of every hour a log entry is created and the counters start again. The GSP qualification log is useful in verifying receiver and antenna performance.

The GPS qualification log is output in the following format:

TIME= HH:MM:SS DATE= YYYY-MM-DD

N = XXXX

N = XXXX …

Q = QQQQ

Where:

HH:MM:SS= UTC time log was created

YYYY-MM-DD= Date log was created

N= The quantity of satellites

XXXX= Number of seconds the receiver tracked the listed quantity of satellites since the beginning of the hour, 1…3600.

QQQQ= Number of seconds since the beginning of the hour the GPS signal was qualified, 0…3600

Typically, the receiver tracks two to three satellites when using a Model 8228 Window Mount GPS antenna. When using the Model 8225 Outdoor antenna, the receiver will typically track five or more satellites.

They may occasionally be short periods when the receiver is unable to track any satellites. When this occurs, the Time Sync alarm count down timer is started. The Sync Alarm Timer resets whenever the receiver reacquires and qualifies at least one satellite for one minute. If a receiver is unable to receive and qualify any satellites within the sync alarm period (two hours), a Time Sync Alarm is asserted.

TTS220 Manual Rev C Page 67

Satellites are qualified as valid when the received vehicle ID number is greater than 1 and the satellite is available for Position Fix usage. The qualification count “Q” is incremented for each second these conditions are met. Typically, the Q value for each hour should exceed 3000.

To view the GPS Qualification Log, do the following:

1. Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address).

2. Press the "Enter Main Page" button.

3. On the lower menu line, select the "Status & Log" item.

4. On the left side menu, select the "GPS Qualification Log" item. The GPS Qualification Log is then displayed in the center of the screen.

Create a Report from the GPS Qualification Log

Since the GPS qualification log includes lots of information, we also provide a comma-separated value (.CSV) file to use with Microsoft Excel™ or a similar program to convert the text data to a graph.

To get a “column” graph in Microsoft Excel, do the following:

Use a PC with a web browser and connect to the product by typing in the IP address into the address window of the browser as follows: http:// 10.10.200.1 (or your IP address).

Press the "Enter Main Page" button. On the lower menu line, select the "Status & Log" item.

On the left side menu, select the "Create report from GPS Qualification Log" item. A status message will inform you, whether or not the qualification report is created successfully. If the file is created successfully, FTP to the unit. Go the sys/logs directory and get the file named “GPSLog.csv”. Please remember to get the file using ASCII data transfer option. Open Microsoft Excel, select File/Open and then open the file saved on you local drive. A spreadsheet should open with all the GPS log information.

To create a chart, Select “Insert/chart…” on the top menu in Excel.

A “Chart Wizard” window will pop-up, select “column” and then click “next”. Click the data range box and then select all the data you want to chart, select “columns”, then click “Next” button. Define a chart title and category for the X and Y axes. If you do not want to define them, click the “Finish” button. A chart is then created based on the GPS qualification log data you selected.

TTS220 Manual Rev C Page 68

3.12 SNMP

SNMP (Simple Network Management Protocol) is a set of standards for managing network devices, which includes a protocol, a database structure specification, and a set of data objects. The communication protocol involves one or more network management stations monitoring one or more network devices. SNMP enabled devices must have a SNMP agent application that is capable of handling network management functions requested by a network manager. The agent is also responsible for controlling the database of control variables defined in the product’s MIB

(Management Information Base).

The SNMP setup page is used to configure the device’s SNMP agent. The following steps can be used to quickly configure the device’s SNMP agent while explaining the configuration options.

Login to the unit through its web-based interface as administrator.

Click on the System Setup link on the bottom of the screen to open the menu for system configurations.

Click on the SNMP link on the left side of the screen to enter the SNMP setup page.

TTS220 Manual Rev C

Figure 3.12-1: SNMP Setup Screen

Page 69

The SNMP agent has a number of access schemes that can be enabled/disabled, depending on your specific needs. The four schemes are described below.

SNMPv1/SNMPv2c – By enabling this access scheme, SNMP network managers may use SNMP version 1 or SNMP version 2 protocols to manage the device. Along with enabling/disabling this access scheme, you may change the read, read-write, and trap community names. The Trap

Destination should be the network IP address of the management station handling any traps from the

SNMP agent.

SNMPv3 (noAuth) – By enabling this access scheme, SNMP network managers may use SNMP version 3 protocol to manage the device. No form of PDU (Protocol Data Units) authentication or

DES encryption is used. You may specify your own user name for this level of access.

SNMPv3 (auth) – By enabling this access scheme, SNMP network managers may use SNMP version

3 protocol to manage the device. This level of SNMPv3 has you select a form of PDU authentication

(MD5 or SHA) but does not use DES encryption. You may specify your own user name and pass phrase for this level of access. The pass phrase is the secret key shared between the SNMP agent and manager, used in the MD5 or SHA authentication algorithm. The Pass phrase must be a minimum of 8 characters long.

SNMPv3 (authPriv) – By enabling this access scheme, SNMP network managers may use SNMP version 3 protocol to manage the device. This level of SNMPv3 also has you select a form of PDU authentication (MD5 or SHA) and performs DES encryption on all PDU’s. You may specify your own user name and pass phrase for this level of access. The pass phrase is the secret key shared between the SNMP agent and manager, used in the MD5 or SHA authentication and DES encryption algorithms. The pass phrase must be a minimum of 8 characters long. NOTE: This access method is only available on secure products.

Spectracom has been assigned the enterprise identifier 18837 by the IANA (Internet Assigned

Numbers Authority). Spectracom’s MIB for its time and frequency products resides under this enterprise identifier @ 18837.3.1 which is illustrated below. is o

1 o r g

3 d o d

6 in t e r n e t

1 m g m t

2 m ib - 2

1 e x p e r im e n t a l

3 p r iv a t e

4 e n t e r p r is e s

1 s p e c t r a c o m

1 8 8 3 7 s p e c P r o d u c t s

3 s p e c T im e F r e q M I B

1

TTS220 Manual Rev C Page 70

Spectracom’s private enterprise MIB can be obtained from customer service.

TTS220 Manual Rev C Page 71

4 Operation

4.1 Status Indicator

At power up a quick LED test is run. The unit displays a RedGreen – Orange sequence to ensure the operation of the LEDs.

The table on the following page describes the operation of the LEDs. In this table, the terms “Blink” and “Flash” are used.

Blink is defined as ½ second on, ½ second off

Flash is defined as

1

/

20

second on,

19

/

20 second off

LABEL COLOR ACTIVITY DESCRIPTION

POWER Green On

SYNC Multi

Off

Off

Power is supplied to the NetClock.

Power is disconnected.

No fault but not synchronized to GPS. Holdover spec has not been met.

Green On Synced to GPS. Time is valid and within the

Locked to GPS accuracy specs.

Blinking

Green

Holdover mode. Not synced to GPS but time is still within Holdover accuracy specs.

Yellow On No longer synced to GPS but no unit fault. Time accuracy may not be meeting holdover specs.

Blinking

Yellow

Unit is in power-up initialization mode. The unit is in this mode for the brief period between power on and when it is operationally ready to receive satellite data.

Flashing

Red

GPS antenna fault. This flash may occur over any of the other color conditions at runtime.

Red On Unit fault. Time may not be valid. Overrides all other indicators.

Blinking

Red

If the unit fails Power On Self Test (POST) then the indicator will blink in a sequence indicating the failure code (consult factory)

Ethernet

(left)

Yellow On

Off

Ethernet

(right)

Green On

Off

LAN Activity.

No LAN traffic detected.

LAN Link established 10 or 100 Mb/s.

No link established.

Table 4-1: Status Indicator

TTS220 Manual Rev C Page 72

4.2 GPS

4.2.1 GPS

HOW TO SET UP GPS RECEIVER:

Using the web browser, you will find the GPS configuration web page under the System Set up category. The GPS configuration web page is designed to allow a user to configure the GPS receiver to provide more accurate results and faster start up, but you do not have to configure them for the unit to run properly.

Figure 4.2-1: GPS Set-up Screen

ANTENNA CABLE DELAY:

To set this value, you must be logged into the unit with the Configuration or Administrator Mode. By setting the correct antenna cable delay, the on-time point is offset by the delay value to compensate for the antenna and in-line amplifier delays. Under typical condition, the expected cable and amplifier delays are negligible. You can calculate the delay based upon the manufacture’s specification.

The range of the cable delay is from 0 to 999999 nanoseconds, the default value is 0 nanosecond, and the resolution is 1 nanosecond.

TTS220 Manual Rev C Page 73

The following formula is used to calculate the cable delay:

D = (L * C) / V

Where:

D = Cable delay in nanoseconds

L = Cable length in feet

C = Constant derived from velocity of light: 1.016

V = Nominal velocity of propagation expressed as decimal, i.e. %66 = 0.66 Value is provided by cable manufacturer.

LOCATION OF THE UNIT:

You can read the current location of the unit calculated by the GPS receiver without logging in. The

GPS receiver will automatically update this field when it has a Position Fix. Check the GPS Signal

Status web page, and if the status is “Position Fix”, then the location showed on this page is the right location.

You can only write the new location value to the unit when logged in under the Configuration or

Administrator mode. The location input by the user may only help to speed up the time to first fix during the initial installation. The unit will automatically check the status of the GPS receiver after receiving the location input from the user, then based on the status of the GPS receiver, the unit will either tell the user that the GPS receiver already has finished the first fix and the input was abandoned, or send the location to the GPS receiver. To find the location for your city, please refer to the position table.

4.2.2 Set System Mode

The system supports two modes known as single satellite mode and standard mode.

Use single satellite mode if you are using a window mount antenna and cannot get more than four satellites. This will switch the qualification algorithm used, and allow the system to operate normally with fewer number of satellites, but the accuracy will be decreased because of the poor GPS antenna visibility.

Note: Always use standard mode if you are using a roof mount antenna and can get at least four satellites. This is the default.

To set the System Mode using the webUI:

1. Using a PC with a web browser connect to the product by typing in the product’s IP address into the address window of the browser as follows: http://10.10.200.1 (or your product’s IP address).

2. Press the “Enter Main Page” button.

3. Select the login link on the top right corner to login as administrator.

4. On the lower menu line select the “System Setup” item.

5. On the left side menu select the “Set System Mode” item.

The setup window for system mode is then displayed in the center of the screen.

TTS220 Manual Rev C Page 74

4.2.3 GPS Signal Status

HOW TO READ THE GPS SIGNAL STATUS:

The GPS Signal Status pages provide insight into the GPS receiver’s operation and the signal quality from the satellites. This information is useful to verify proper antenna placement and receiver performance during installation and later troubleshooting.

The overall tracking status, position solution and a table containing individual satellite data is on this page.

Figure 4.2-2: GPS Signal Status Setup Screen

Tracking X satellites:

Where: X = Number of satellites currently tracking (0 – 12)

GPS Status = SSSS

Where: SSSS = Receiver Status

TTS220 Manual Rev C Page 75

Acquiring satellites is possible if the GPS Receiver is still looking for qualified satellites.

Bad Geometry is possible if the GPS Receiver is tracking qualified satellites, but the number of satellites or their relative position is not sufficient for calculating position.

2D Fix is possible if the receiver is tracking at least three qualified satellites.

3D Fix is possible if the receiver is tracking at least four qualified satellites.

Position Hold is possible if the GPS receiver has collected enough information to determine the location of the GPS receiver.

DOP = ##.#

Where: DOP means dilution of precision. The range is from 00.0 to 99.9

This value indicates the degree of uncertainty of a Position Fix due to the geometry of the Satellites used in the solution. The lower the DOP value, except 0, the lower the degree of uncertainty.

Antenna Sense = SSSSS

Where: SSSSS reports the status of the antenna sense circuit. There are three main flags (OK, Over

Current, and Under Current). The three flags are described below:

Flag

The OK flag is displayed if both antenna sense bits are cleared. This indicates that the antenna is drawing current within the normal range.

Over Current Flag

This flag is displayed if the over current bit is set. This indicates that too much current is being drawn through the circuit and the overload protection circuit is limiting the feed current. The receiver will attempt to continue the normal acquisition and tracking process regardless of the antenna status.

Under Current Flag

This flag is displayed if the undercurrent bit is set. This indicates that little or no current is being drawn through the circuit, which may be due to a disconnected antenna, a severed antenna cable, or a damaged antenna. The receiver will attempt to continue the normal acquisition and tracking process regardless of the antenna status.

Undercurrent indication < 8 mA

Overcurrent indication > 80 mA

Latitude = [N:S][DD MM SS.SSSS]

Longitude = [E:W][DDD MM SS.SSSS]

Where: N = North latitude

S = South Latitude

E = East Longitude

W = West Longitude

D = Degree

M = Minute

S = Second

Quality = QQQQQ

TTS220 Manual Rev C Page 76

Where: QQQQQ = Result of GPS qualification, either PASSED or FAILED. The GPS signal is considered qualified when at least one satellite is received having a vehicle ID greater than 1 and is available for Position Fix Usage.

Information on each satellite the receiver is currently tracking is presented in table form. The table columns are described below:

CHANNEL = Channel Number of the GPS receiver, 1…12

VID = Vehicle (satellite) Identification Number, 1…37

MODE = Channel Tracking Mode,

Where:

0 = Code Search

1 = Code Acquire

2 = AGC set

3 = Freq Acquire

4 = Bit Sync Detect

5 = Message Sync Detect

6 = Satellite Time Available

7 = Ephemeris Acquire

8 = Avail for position

Note: Mode 8 is the normal state for a valid satellite in use

STRENGTH = Signal strength value relative to the Signal to Noise Ratio [SNR]. Range: 0…255, the higher the number, the greater the receiver signal.

STATUS = Channel status flag. Convert the hexadecimal code word to binary to find the status flag set.

Bit 11: Used for time

Bit 10: Differential Correction Available

Bit 9: Invalid Data

Bit 8: Parity Error

Bit 7: Used for Position Fix

Bit

Bit 5: Satellite Anti-Spoof Flag Set

Bit 3-0: Satellite Accuracy as follows:

TTS220 Manual Rev C Page 77

(Per para 20.3.3.3.13 ICD-GPS-200)

0000 (0) 0.00 <URA<=2.40

0001 (1) 2.40 <URA<=3.40

0010 (2) 3.40 <URA<=4.85

0011 (3) 4.85 <URA<=6.85

0100 (4) 6.85 <URA<=9.65

0101 (5) 9.65 <URA<=13.65

0110 (6) 13.65 <URA<=24.00

0111 (7) 24.00 <URA<=48.00

1000 (8) 48.00 <URA<=96.00

1001 (9) 96.00 <URA<=192.00

1010 (10) 192.00 <URA<=384.00

1011 (11) 384.00 <URA<=768.00

1100 (12) 768.00 <URA<=1536.00

1101 (13) 1536.00 <URA<=3072.00

1110 (14) 3072.00 <URA<=6144.00

1111 (15) 6144.00 <URA*

(* means No accuracy prediction is available – unauthorized users are advised to use the Space

Vehicle at their own risk.)

Normal values for Status Field are

8A0

Which is 1000 1010 000x binary

Bit 11 = 1: Used for time

Bit 10 = 0: Differential Correction Not Available

Bit 9 = 0: Not Invalid Data

Bit 8 = 0: No Parity Error

Bit 7 = 1: Used for Position Fix

Bit 6 = 0: No Satellite Momentum Alert Flag

Bit 5 = 1: Satellite Anti-Spoof Flag Set

Bit 4 = 0: Satellite Reported as Healthy

Bit 3-0=low number: Satellite is Accurate

TTS220 Manual Rev C Page 78

Please review this section prior to calling the Spectracom Customer Service Department. If the reception problem cannot be solved following the guidelines outlined in this section, please call for

Customer Service at 585.321.5800.

No Reception

Cable or connector problem: Measure the antenna cable resistance to verify the integrity of the cable and connectors. Remove the antenna cable from the rear panel of the receiver and measure the resistance from the coax center to shield. Refer to Table 4-2 for typical resistance values of the antenna and inline amplifier alone and when combined.

DEVICE DESCRIPTION RESISTANCE (SP)

8228

8225

Indoor Antenna

Outdoor Antenna

140 ohms

180 ohms

8227 In-line Amplifier 165 ohms

8225 and 8227 Antenna/Amplifier 85 ohms

Table 4-2: Typical Antenna Cable Resistance Values

Failed Impulse Suppressor: The Model 8226 provides lightning protection when the outdoor GPS antenna is used. The Model 8226 has high impedance when measuring from the center conductor to ground and a low throughput resistance. A failing impulse suppressor may be tripping prematurely.

The easiest way to test the Model 8226 is to temporarily replace it with a Type N barrel connector. If the receiver begins tracking satellites within 20 minutes, the impulse suppressor has failed and must be replaced.

Cable Length: The Model 8228 Indoor Antenna is supplied with 50 feet of antenna cable. Do not add cable. Excessively long or improper cable type may prevent the receiver from tracking satellites.

Refer to Section 2.2 for cable recommendations when using the Model 8225 Outdoor Antenna.

Antenna Location: The antenna must have a good view of the sky. Refer to Section 2.1 for indoor antenna guidelines and Section 2.2 for outdoor antenna guidelines.

Window Type: Windows with metal film coatings, metal screens or blinds may impede GPS reception.

TTS220 Manual Rev C Page 79

Low GPS Quality

Cable Length: Excessively long or improper cable type may cause low GPS quality due to cable attenuation. Long GPS antenna lengths may require an inline amplifier or lower loss cable. Refer to

Section 2.2.2 for GPS cable recommendations and Section 2.2.4 for inline amplifier information when using the Model 8225 Outdoor Antenna.

The Model 8228 Indoor Antenna is provided with a 50-foot antenna cable. Do not substitute or add coax to the provided cable.

Antenna Location: The antenna must have a view of the sky with views to the horizon. Nearby obstructions can reduce the receiver’s ability to track the maximum number of satellites available.

Window Type: Windows with metal film coatings, metal screens or blinds may reduce GPS reception.

TTS220 Manual Rev C Page 80

5 Troubleshooting

5.1 Front Panel Power and Sync Lamps

Symptom CAUSE

Power

LED is off

No power to the unit

Sync LED

Corrective Action

• Ensure the AC power is live to the power adapter

• Ensure the adapter is plugged in properly into the unit

• Ensure no other connecting cables to the unit are pinched or shorted

• Replace the power adapter

New install and

Sync LED is not lit

Flashing

Green

Yellow

Flashing

Red

Red stays

On

Blinking

Red

Not enough time has elapsed or can’t track satellites

Recently stopped

Tracking satellites

(The unit has not timed-out of holdover mode).

Not tracking

Satellites (No longer in holdover mode).

GPS antenna fault.

If less than 20 minutes since power-on, continue monitoring. If longer than about 20 minutes, refer to section 4.2.4 reception troubleshooting

(Time is still valid. Other devices will still be synced). Refer to section 4.2.4 reception troubleshooting. Review the Alarm and

Qualification logs.

(Time is no longer valid). Other devices will not be synced). Refer to section 4.2.4 reception troubleshooting. Review the Alarm and

Qualification logs.

There is a short or open in the GPS antenna cable.

Verify the antenna is connected. Using a multimeter, measure continuity of the cable to verify no open or shorts in the GPS cable. Refer to section 4.2.4 reception troubleshooting.

Contact Customer Service Unit fault. Time may not be valid.

Overrides all other indicators.

If the unit fails

Power On Self Test

(POST) then the indicator will blink in a sequence indicating the failure code

(consult factory)

Contact Customer Service

TTS220 Manual Rev C Page 81

5.2 Front Panel LAN Connector

Symptom Cause

LAN Green

LED is off (This

LED also known as Good

Link indicator).

Unit is not connected to the network

LAN Green on the Time Server but the Gold

Link indicator on the

HUB/Switch is not lit.

The Time Server and the

HUB/Switch are not communicating at the correct port speed.

Can “Ping” the unit but can’t point web browser to the unit

Can use web browser to configure the unit but can’t synchronize any PC’s with the Time Server

• Gateway not configured correctly

• Web Browser proxy settings not correct

PC software not installed or configured correctly.

Corrective Action

• Check LAN cable connections (Straight-thru network cable if connected to Hub/Switch, crossover if connected direct to a PC).

• Be sure to use a straight-through cable when connecting to a hub, a cross-over cable when connecting directly to a PC.

• Check that the hub/switch/router device port is active and set to the correct port speed.

• If the Hub/switch is set to auto, power cycle the

Time Server with the network cable connected.

This will cause Auto-Negotiate to determine the settings of the HUB/Switch (Auto-Negotiate only occurs at power-on).

• Try setting the HUB/Switch to 100mbps and

10mpps

• If the network has a Gateway, verify the Gateway has been set correctly and is enabled.

• Verify the proxy settings in the web browser program are correct.

• Install YATS32 shareware program from www.dillobits.com

. This program will allow you to view the raw NTP data to verify that the Time Server is outputting time data. Refer to the Spectracom website

Support page for additional information on YATS32.

• Refer to Spectracom website Support page for additional information on syncing PC’s.

• Verify the Sync lamp is solid green.

Unable to communicate with the unit on the network

Improper IP addressing • Make sure your IP address and subnet mask are set correctly.

• Make sure the unit is within the same Class and/or subnet range as the computers with which you are trying to communicate

• Check that the hub/switch/router device port is active and set to the correct port speed.

• Be sure to use a straight-through cable when connecting to a hub, a cross-over cable when connecting directly to a PC.

• Consult your Network System Administrator.

TTS220 Manual Rev C Page 82

5.3 Customer Service

Refer to Section 1.2, Warranty Information and Product Support for information on contacting

Spectracom Customer Service for assistance.

TTS220 Manual Rev C Page 83

6 Appendices

6.1 Software Commands

From the rear panel RS-232 Serial Setup Port, the user can manage files and configure network settings for the product. Table 6-1 provides a listing of the command set in alphabetical order and the page where you can find the description of the command. These commands may contain a set of subcommands that that are used to configure individual attributes for that subsystem.

logout Log out of the current security level

net gateway

Enable/disable or set the default gateway

Display summaries of the network subcommands

ip mac mask show

Set the Mac Address

Set the subnet mask

Show network parameters

http Enable/disable http access to the unit

reboot Reboot the unit

sec

Display summaries of the security subcommands

Display the current security level

password

update Firmware

Update the Boot Monitor

csl

help

Update the CSL

Display summaries of the update subcommands

Table 6-1: Alphabetical List of Commands

NOTE: The commands shown in this section are all in lower case format.

The NetClock/NTP accepts commands in upper or lower case formats.

TTS220 Manual Rev C Page 84

help

The command, help, displays a summary of the available commands at the current security level.

The user may specify a particular command or set of commands to display more detailed help information. The help command is intended for novice users. The novice user can use this command to aid them learning the individual syntax for system commands.

The help command is available at the user security level.

To list the available commands at the current security level, issue the help command as shown below:

Type: help <ent>

Example Response:

help Commander Help Function dir dir [path] - list current directory pwd pwd - print working directory cd cd [path] - change directory delete delete [file] - remove a file type type [file] - print the contents of a file sec sec <command> <arguments> - invoke security commands login login <account> <password> - access secure areas logout logout - exit secure areas net net <command> <arguments> - invoke network commands

To list the files and directories in the parent directory of the current working directory, issue the dir command as follows:

Type:

Where: help COMMAND <ent>

COMMAND = the command to obtain help on.

Example, The current working directory is /test and it contains a file named data.txt.

Follow the example below to display help about the net command.

Type: help net <ent>

Response: the 'net' group of commands is used to access and manage the network interface

login

The command, login, is used to change the current security level. The user may specify the security level and password after the command or fill them in when prompted. The login command is intended for advanced users. The advanced user can use this command to log in to the unit at either the config or admin level.

The login command is available at the user security level.

To log in to the unit at a different security level, issue the login command as shown below:

TTS220 Manual Rev C Page 85

Type:

Password:

PASSWORD <ent> (the terminal will not show what you type)

Login

Security Level is now: LEVEL Level

Where: LEVEL = the security level to log in as.

PASSWORD for the specified security level.

To log in to the unit at a different security level and be prompted for the level and password, issue the

login command as follows:

Type:

Type:

Account:

<ent>

Type:

Password:

PASSWORD <ent> (the terminal will not show what you type)

Security Level is now:

Where:

LEVEL Level

LEVEL = the security level to log in as.

PASSWORD for the specified security level.

Follow the example below to log in to the unit at the config security level.

Type

Password: config12 <ent> (the terminal will not show what you type)

Login

Security Level is now: Config Level

TTS220 Manual Rev C Page 86

logout

The command, logout, is used to change the current security level to the user level. The logout command is intended for advanced users. The advanced user can use this command to restore the security level back to the user level after they have completed any commands that required a higher security level.

The logout command is available at the user security level.

To log out of the unit to the user security level, issue the logout command as shown below:

Response: now

net

The command, net, is used to configure the network interface. The net command consists of a set of subcommands that are used to get, set or change each individual network setting. Some of the network settings require config level security in order to set or change them.

To invoke one of the net subcommands, issue the net command as shown below:

Where: subcommand.

SUBCOMMAND = The subcommand to invoke.

ARGUMENTS = The arguments required for the specified

To display a list of the available subcommands for the net command along with a summary description of each, issue the net command as follows:

net

Response: use the 'net help' command to see a list of net commands use the 'net help <sub-command>' to get detailed help about that command help mask ip show default net help - list of net commands net mask mmm.mmm.mmm.mmm - set new network mask net ip nnn.nnn.nnn.nnn - set new ip address net show - display network configuration to the user net default - set all net parameters back to default values gateway mac http

* net gateway [yes,no] [address] – enable gateway net mac [xx:xx:xx:xx:xx:xx] - get or set MAC address net http [yes,no] – enable or disable http access to the unit

The following are the set of subcommands for the net command:

*

This feature is only available for secure Spectracom products

TTS220 Manual Rev C Page 87

net gateway

The net subcommand, gateway, is used to display, enable/disable, and/or set the IP address of the default gateway. The gateway subcommand is intended for advanced users. The advanced user can use this command to configure the address of the router that will be used as the default gateway for sending information beyond the local area network (LAN).

The gateway subcommand is available at the user security level to display the current setting.

The gateway subcommand is available at the config security level to set a new value.

To display the current gateway setting, issue the gateway subcommand as shown below:

net

Response:

GATEWAY_ADDRESS =The IP address of the gateway.

To enable or disable the gateway, issue the gateway subcommand as shown below:

Type:

Type

Password:

PASSWORD <ent> (the terminal will not show what you type)

Security Level is now:

Where:

Config Level

PASSWORD

ENABLE = yes or no.

SETTING = Enabling or Disabling..

GATEWAY_ADDRESS = The IP address of the gateway.

To enable the gateway and set the gateway IP address, issue the gateway subcommand as shown below:

Type

Password:

PASSWORD <ent> (the terminal will not show what you type)

Login

Security Level is now: Config Level

net

Response:

Follow the example below to enable a gateway with IP address 192.168.0.200.

TTS220 Manual Rev C Page 88

Type

Security Level is now:

Type: config12 <ent> (the terminal will not show what you type)

Config Level net gateway yes 192.168.0.200 <ent>

NOTE: Attempting to enable or set a gateway with an invalid IP address or an IP address that is not on the same subnet will result in an error. Be sure the desired gateway exists and is reachable on the LAN before setting/enabling it with the net gateway subcommand.

net help

The net subcommand, help, is used to display a list of the available subcommands and a brief usage summary for each of them. The help subcommand is intended for novice users. The novice user can use this command to aid them learning the individual syntax for net subcommands.

The help subcommand is available at the user security level.

To display a list of the available subcommands and brief usage of each, issue the help subcommand as shown below:

Response: help mask ip show default gateway mac

net ip

net help - list of net commands net mask mmm.mmm.mmm.mmm - set new network mask net ip nnn.nnn.nnn.nnn - set new ip address net show - display network configuration to the user net default - set all net parameters back to default values net gateway [yes,no] [address] – enable gateway net mac [xx:xx:xx:xx:xx:xx] - get or set MAC address

The net subcommand, ip, is used to set the IP address for the unit. The ip subcommand is intended for advanced users. The advanced user can use this command to statically configure the IP address of the unit so that it may be accessed via the network.

The ip subcommand is available at the config security level to set a new value.

To set the IP address for the unit, issue the ip subcommand as shown below:

Type

Password:

Response:

PASSWORD <ent> (the terminal will not show what you type)

Successful

Security Level is now: Config Level

TTS220 Manual Rev C Page 89

Stack IP address: IP_ADDRESS

New IP address set

Follow the example below to set the unit to have an IP address of 192.168.0.100.

Type

Password:

Response: config12 <ent> (the terminal will not show what you type)

Successful

Security Level is now: Config Level

net

Response:

Stack IP address: 192.168.0.100

New IP address set

NOTE: The Stack IP address reflects the value that the TCP/IP stack is set to. This should match the IP address being set.

net mac

The net subcommand, mac, is used to display the Ethernet MAC address for the unit. The mac subcommand is intended for advanced users. The advanced user can use this command to retrieve the Ethernet MAC address of the unit for uses such as network traffic monitoring.

The mac subcommand is available at the user security level to get the value.

To get the Ethernet MAC address for the unit, issue the mac subcommand as shown below:

Type:

net mask

The net subcommand, mask, is used to set the subnet mask for the unit. The mask subcommand is intended for advanced users. The advanced user can use this command to configure the subnet mask of the unit so that it may be accessed via the network.

The mask subcommand is available at the config security level to set a new value.

To set the IP address for the unit, issue the mask subcommand as shown below:

Type

Password:

TTS220 Manual Rev C

PASSWORD <ent>

Page 90

(the terminal will not show what you type)

Security Level is now: Config Level

PASSWORD

Type: <ent>

Stack netmask: NETMASK

Has set

Follow the example below to set the unit to have an IP address of 255.255.0.0.

Type

Password:

Response: config12 <ent> (the terminal will not show what you type)

Successful

Security Level is now: Config Level

net 255.255.0.0 new

<ent>

255.255.0.0

Has set

net show

NOTE: The Stack netmask reflects the value that the TCP/IP stack is set to.

This should match the netmask value being set.

The net subcommand, show, is used to display a list of the available subcommands and a brief usage summary for each of them. The show subcommand is intended for novice users. The novice user can use this command to aid them learning the individual syntax for net subcommands.

The show subcommand is available at the user security level.

To display a list of the current network parameters, issue the show subcommand as shown below:

Type: <ent>

Netmask address:

Network gateway:

NETMASK

STATUS

IP_ADDRESS =The IP address for the unit.

NETMASK =The subnet mask for the unit.

STATUS =enabled or disabled.

GATEWAY_ADDRESS =The IP address for the default gateway.

XX:XX:XX:XX:XX:XX =The Ethernet MAC address for the unit.

The example below displays the network settings for an example unit

TTS220 Manual Rev C Page 91

net <ent>

Network

10.10.200.104

Netmask address:

Network gateway:

255.255.0.0 enabled

Gateway IP:

MAC address:

10.10.200.201

00:0c:ec:00:01:cc

net http

*

The net subcommand, http, is used to enable or disable the HTTP protocol.

The http subcommand is available at the administrator security level only.

To display the current http setting, issue the http subcommand as shown below:

Type

Password: password <ent> (the terminal will not show what you type)

Security Level is now:

Where:

Admin Level

PASSWORD

Response: Network HTTP status

where

To disable HTTP issue the following command:

Type

Password: password <ent> (the terminal will not show what you type)

Login

Security Level is now: Admin Level

Response: HTTP Disabled

To enable HTTP issue the following command:

Type:

Type

Password: password <ent> (the terminal will not show what you type)

Security Level is now:

Where:

Admin Level

PASSWORD

Response: HTTP Enabled

*

This feature is only available for secure Spectracom products

TTS220 Manual Rev C Page 92

reboot [bootloader]

The reboot is used to warm-boot the unit without having to disconnect or reconnect the power supply. The reboot command is intended only for administrators, and is available at the admin security level. The optional bootloader argument is used to reboot into the bootloader for software upgrade; which cannot be performed from the application.

To reboot the unit, login as administrator, then issue the reboot command as shown here:

Type

Password:

PASSWORD <ent> (the terminal will not show what you type)

Login

Security Level is now: Admin Level

reboot

Rebooting...

NOTE: This command provides a convenient way to remotely update application software in that the unit will automatically execute the most recent image in /sys/bin/.

CAUTION: Do not reboot the unit while file uploads are in progress. Do not reboot the unit with non-application images are located in /sys/bin/. If either of these conditions is not fulfilled, the unit may fail to boot the application image, which could result in a unit that function incorrectly or not at all.

TTS220 Manual Rev C Page 93

sec

The command sec is used to configure the security feature. The sec command consists of a set of subcommands that are used to get, set or change each individual security feature setting. Some of the sec settings require config level security or admin level in order to set or change them.

To invoke one of the sec subcommands, issue the sec command as shown below:

sec

Where: SUBCOMMAND = the subcommand to invoke.

ARGUMENTS = the arguments required for the specified subcommand.

To display a list of the available subcommands for the sec command along with a summary description of each, issue the sec command. Based on the security level you are in, the response will be different. We list them all in the following.

1. If you are in user level

Response: level help sec level - show the current security level sec help - list of sec sub-commands and detailed information on each

2. Under config level

Response: level sec level - show the current security level help sec help - list of sec sub-commands and detailed information on each

3. Under admin level

Response: account sec account <Account-Name> <new-name> level sec level - show the current security level password sec password <Account-Name> help sec help - list of sec sub-commands and detailed information on each

The following are the set of subcommands for the sec command:

sec level

The sec subcommand, level is used to show the current security level.

The level subcommand is available at the user security level.

To show the current security level, issue the level subcommand as shown below:

TTS220 Manual Rev C Page 94

Response:

sec help

Security Level is: User Level

The sec subcommand help is used to list of sec sub-commands and detailed information on each.

The help subcommand is available at the any security level. You will get different result based on the security level you are in now.

To get a list of sec sub-commands and detailed information on, issue the help subcommand as shown below:

1. Under user mode

Login

Security Level is now: Config Level

2. Under config mode

Type

Password: config12 <ent> (the terminal will not show what you type)

Security Level is now:

Type:

Config Level

sec

Response: level help sec level - show the current security level sec help - list of sec sub-commands and detailed information on each

3. Under admin mode

Type

Password: admin123 <ent> (the terminal will not show what you type)

Login

Security Level is now: Admin Level

Response: account sec account <Account-Name> <new-name> level sec level - show the current security level password sec password <Account-Name> help sec help - list of sec sub-commands and detailed information on each

TTS220 Manual Rev C Page 95

sec password

The sec subcommand password is used to set an account name. The password subcommand is only available at the admin security level.

To set the account under admin mode, issue the password subcommand as shown below:

Type

Password: admin123 <ent> (the terminal will not show what you type)

Security Level is now:

Type:

Admin Level

sec

Type:

Account:

[current

Type:

Old Password:

[current

Type:

New Password:

[New password for this account] <ent>

Type:

New Password (again):

[New password for this account] <ent>

update

The command, update, is used to install a new bootloader into the unit. The update command consists of a set of subcommands that are used to update each portion that can be modified. Since correct installation of the bootloader is critical to operation, this entire menu requires admin level security in order to use them.

To invoke one of the update subcommands, issue the update command as shown below:

Type:

Where: SUBCOMMAND =The subcommand to invoke.

ARGUMENTS =The arguments required for the specified subcommand.

To display a list of the available subcommands for the update command along with a summary description of each, issue the update command as follows:

Type: update <ent>

Response: help update help - list each subcommand and its description csl update csl <filename> - install a new CSL image boot update boot <filename> - install a new bootload image app update app <filename> - install a new application kern update kern <filename> - install a new kernel

The following are the set of subcommands for the update command:

TTS220 Manual Rev C Page 96

update app

The update subcommand, app, is used to update the application image for the unit. The app subcommand is intended only for advanced users that have been provided with an updated application image.

The app subcommand is only available at the admin security level.

To install a new CSL image into the unit, upload the image to the unit's /update directory via FTP or secure copy. Then issue the update app command as shown here:

Type

Password:

PASSWORD<ent>

Login

Security Level is now: Admin Level

PASSWORD password for admin security level.

update

Response:

APPFILE name of the application image.

CAUTION: Do not power down or reboot the unit while running this command. Do not install files that are not application images. If a non-application image is installed it can be overwritten by re-updating with a correct application image. The unit will operate incorrectly or completely fail to run if this command is not used with care.

TTS220 Manual Rev C Page 97

update boot

The update subcommand, boot, is used to update the bootloader image for the unit. The boot subcommand is intended only for advanced users that have been provided with an updated bootloader image.

The boot subcommand is only available at the admin security level.

To install a new bootloader image into the unit, upload the image to the unit's /update directory via

FTP or secure copy. Then issue the update boot command as shown here:

Type

Password:

PASSWORD<ent>

Login

Security Level is now: Admin Level

PASSWORD password for admin security level.

update

Response:

CAUTION: Do not power down or reboot the unit while running this command. Do not install files that are not bootloader images. If a non-bootloader image is installed it can be overwritten by re-updating with a correct bootloader image. The unit will operate incorrectly or completely fail to run if this command is not used with care.

TTS220 Manual Rev C Page 98

update csl

The update subcommand, csl, is used to update the CSL image for the unit. The csl subcommand is intended only for advanced users that have been provided with an updated CSL image.

The csl subcommand is only available at the admin security level.

To install a new CSL image into the unit, upload the image to the unit's /update directory via FTP.

Then issue the update csl command as shown here:

Type

Password:

PASSWORD<ent>

Security Level is now:

Where:

Admin Level

PASSWORD

Response:

Where:

CSL

CAUTION: Do not power down or reboot the unit while running this command. Do not install files that are not CSL images. If a non-CSL image is installed it can be overwritten by reupdating with a correct CSL image. The unit will operate incorrectly or completely fail to run if this command is not used with care.

TTS220 Manual Rev C Page 99

update kern

The update subcommand, kern, is used to update the kernel image for the unit. The kernel subcommand is intended only for advanced users that have been provided with an updated kernel image.

The kern subcommand is only available at the admin security level.

To install a new kernel image into the unit, upload the image to the unit's /update directory via FTP.

Then issue the update kern command as shown here:

Type

Password:

PASSWORD<ent>

Login

Security Level is now: Admin Level

PASSWORD password for admin security level.

update

Response:

CAUTION: Do not power down or reboot the unit while running this command. Do not install files that are not kernel images. If a non-kernel image is installed it can be overwritten by reupdating with a correct kernel image. The unit will operate incorrectly or completely fail to run if this command is not used with care.

update help

The update subcommand, help, is used to display a list of the available subcommands and a brief usage summary for each of them. The help subcommand is intended for novice users. The novice user can use this command to aid them learning the individual syntax for update subcommands.

The help subcommand is available at the admin security level.

To display a list of the available subcommands and brief usage of each, issue the help subcommand as shown below:

Type: update help <ent>

Response: help update help - list each subcommand and its description csl update csl <filename> - install a new CSL image boot update boot <filename> - install a new bootload image app update app <filename> - install a new application kern update kern <filename> - install a new kernel

TTS220 Manual Rev C Page 100

6.2 Serial Data Formats

This section describes each of the data format selections available on the RS-232 (Serial Comm) and

RS-485 (Remote Port) outputs. Format selection is made as part of the Serial Comm and Remote port configuration. Most applications utilize Data Format 0 or Data Format 2.

Format 0:

Format 0 includes a time sync status character, day of year, time reflecting time zone offset and DST corrections when enabled. Format 0 also includes the DST/Standard Time indicator, and the time zone offset value. Format 0 data structure is shown below:

CR LF I ^ ^ DDD ^ HH:MM:SS ^ DTZ=XX CR LF where:

CR = Carriage Return

I =

^

DDD =

HH =

Time Sync Status (space, ?, *)

Day of Year (001 - 366)

Hours (00-23)

: Colon

= separator

(00-59)

SS =

=

TZ

XX =

Seconds (00- 60)

Time Zone offset (00-23)

The leading edge of the first character (CR) marks the on-time point of the data stream.

The time sync status character I is defined as described below:

(Space) = Whenever the front panel Time Sync lamp is green.

? = When the receiver is unable to track any satellites and the Time Sync lamp is red.

* = When the receiver time is derived from the battery backed clock or set manual through the Setup Port Interface.

The Daylight Saving Time indicator D is defined as:

S = During periods of Standard time for the selected DST schedule.

I = During the 24-hour period preceding the change into DST

D = During periods of Daylight Saving Time for the selected DST schedule

O = During the 24-hour period preceding the change out of DST

Example: 271 12:45:36 DTZ=08

The example data stream provides the following information:

Sync Status: Time synchronized to GPS

Date:

Time:

Day 271

12:45:36 Pacific Daylight Time

D = DST, Time Zone 08 = Pacific Time

TTS220 Manual Rev C Page 101

Format 1:

This format provides the fully decoded time data stream. Format 1 converts the received day of year data (001-366) to a date consisting of day of week, month, and day of the month. Format 1 also contains a time sync status character, year, and time reflecting time zone offset and DST correction when enabled. Format 1 data structure is shown below:

CR LF I ^ WWW ^ DDMMMYY ^ HH:MM:SS CR LF where:

CR = Carriage Return

LF = Line Feed

I = Time Sync Status (space, ?, *)

^ = space separator

WWW = Day of Week (SUN, MON, TUE, WED, THU, FRI, SAT)

DD = Numerical Day of Month (^1-31)

MMM = Month (JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC)

YY = Year without century (99, 00, 01 etc.)

HH = Hours (00-23)

: = Colon separator

MM = Minutes (00-59)

SS = Seconds (00 - 60)

The leading edge of the first character (CR) marks the on-time point of the data stream.

The time sync status character I is defined as described below:

(Space) = Whenever the front panel Time Sync lamp is green.

? = When the receiver is unable to track any satellites and the Time Sync lamp is red.

* = When the receiver time is derived from the battery backed clock or set manually through the Setup Port Interface.

Example: * FRI 20APR01 12:45:36

The example data stream provides the following information:

Sync Status: The clock is not time synchronized to GPS. Time is derived from the battery backed clock or set manually

Date:

Time:

Friday, April 20, 2001

12:45:36

TTS220 Manual Rev C Page 102

Format 2:

This format provides a time data stream with millisecond resolution. The Format 2 data stream consists of indicators for time sync status, time quality, leap second and Daylight Saving Time. Time data reflects UTC time and is in the 24-hour format. Format 2 data structure is shown below:

CR LF IQYY ^ DDD ^ HH:MM:SS.SSS ^ LD where:

CR = Carriage Return

LF = Line Feed

I = Time Sync Status (space, ?, *)

Q = Quality Indicator (space, A, B, C, D)

YY = Year without century (99, 00, 01 etc.)

^ = space separator

DDD = Day of Year (001 - 366)

HH = Hours (00-23 UTC time)

: = Colon separator

MM = Minutes (00-59)

SS = Seconds (00-60)

. = Decimal Separator

SSS = Milliseconds (000-999)

L = Leap Second Indicator (space, L)

D = Daylight Saving Time Indicator (S,I,D,O)

The leading edge of the first character (CR) marks the on-time point of the data stream.

The time sync status character I is defined as described below:

(Space) = Whenever the front panel Time Sync lamp is green.

? = When the receiver is unable to track any satellites and the Time Sync lamp is red.

* = When the receiver time is derived from the battery backed clock or set manually through the Setup Port Interface.

The quality indicator Q provides an inaccuracy estimate of the output data stream. When the receiver is unable to track any GPS satellites, a timer is started. Table 6-2: Table of Quality Indicators lists the quality indicators and the corresponding error estimates based upon the GPS receiver 1 PPS stability and the time elapsed tracking no satellites. The Tracking Zero Satellites timer and the quality indicator reset when the receiver reacquires a satellite.

Inaccuracy Code Time Error (mSec) Time Since Unlock (Hours)

Space <1 Locked

A <10 <10

TTS220 Manual Rev C

Table 6-2: Table of Quality Indicators

Page 103

The leap second indicator L is defined as:

(Space) = When a leap second correction is not scheduled for the end of the month.

L = When a leap second correction is scheduled for the end of the month.

The Daylight Saving Time indicator D is defined as:

S = During periods of Standard time for the selected DST schedule.

I = During the 24-hour period preceding the change into DST.

D = During periods of Daylight Saving Time for the selected DST schedule.

O = During the 24-hour period preceding the change out of DST.

Example: ?A01 271 12:45:36.123 S

The example data stream provides the following information:

Sync Status: The clock has lost GPS time sync. The inaccuracy code of “A” indicates the expected time error is <10 milliseconds.

Date: Day 271 of year 2001.

Time: 12:45:36 UTC time, Standard time is in effect.

TTS220 Manual Rev C Page 104

Format 3:

Format 3 provides a format identifier, time sync status character, year, month, day, time with time zone and DST corrections, time difference from UTC, Standard time/DST indicator, leap second indicator and on-time marker. Format 3 data structure is shown below:

FFFFI^YYYYMMDD^HHMMSS±HHMMD L # CR LF where:

FFFF =

I =

^ =

YYYY =

MM =

DD =

HH =

MM =

SS =

Format Identifier (0003)

Time Sync Status (Space, ? *) space separator

Year (1999, 2000, 2001 etc.)

Month Number (01-12)

Day of the Month (01-31)

Hours (00-23)

Minutes (00-59)

Seconds (00-60)

± = Positive or Negative UTC offset (+,-) Time Difference from UTC

HHMM = UTC Time Difference Hours, Minutes (00:00-23:00)

D =

L =

Daylight Saving Time Indicator (S,I,D,O)

Leap Second Indicator (space, L)

# =

CR =

LF =

On time point

Carriage Return

Line Feed

The time sync status character I is defined as:

(Space) = Whenever the front panel Time Sync lamp is green.

? = When the receiver is unable to track any satellites and the Time Sync lamp is red.

* = When the receiver time is derived from the battery backed clock or set manually through the Setup Port Interface.

The time difference from UTC, ±HHMM, is selected when the Serial Comm or Remote port is configured. A time difference of -0500 represents Eastern Time. UTC is represented by +0000.

The Daylight Saving Time indicator D is defined as:

S = During periods of standard time for the selected DST schedule.

I = During the 24-hour period preceding the change into DST.

D = During periods of Daylight Saving Time for the selected DST schedule.

O = During the 24-hour period preceding the change out of DST.

The leap second indicator L is defined as:

(Space) = When a leap second correction is not scheduled at the end of the month.

L = When a leap second correction is scheduled at the months end.

TTS220 Manual Rev C Page 105

Example: 0003 20010415 124536-0500D #

The example data stream provides the following information:

Data Format: 3

Sync Status:

Date:

Time Synchronized to GPS.

April 15, 2001.

Time: 12:45:36 EDT (Eastern Daylight Time), The time difference is 5 hours

Leap Second: No leap second is scheduled for this month.

TTS220 Manual Rev C Page 106

Format 4:

Format 4 provides a format indicator, time sync status character, modified Julian date, time reflecting

UTC with 0.1 millisecond resolution and a leap second indicator. Format 4 data structure is shown below:

FFFFIMJDXX^HHMMSS.SSSS^L CR LF where:

FFFF =

I =

Format Identifier (0004)

Time Sync Status (Space, ? *)

MJDXX = Modified Julian Date

HH =

MM =

SS.SSSS =

L =

CR =

LF =

Hours (00-23 UTC time)

Minutes (00-59)

Seconds (00.0000-60.0000)

Leap Second Indicator (^, L)

Carriage Return

Line Feed

The start bit of the first character marks the on-time point of the data stream.

The time sync status character I is defined as:

(Space) = Whenever the front panel Time Sync lamp is green.

? = When the receiver is unable to track any satellites and the Time Sync lamp is red.

* = When the receiver time is derived from the battery backed clock or set manually through the Setup Port Interface.

The leap second indicator L is defined as:

(Space) = When a leap second correction is not scheduled at the end of the month.

L = when a leap second correction is scheduled at the months end.

Example: 0004 50085 124536.1942 L

The example data stream provides the following information:

Data format:

Sync Status:

Modified Julian Date:

4

Time synchronized to GPS.

50085

Leap Second: A leap second is scheduled at the end of the month.

TTS220 Manual Rev C Page 107

Format 90:

Format 90 provides a position data stream in NMEA 0183 GPGGA GPS Fix data format.

The Format 90 data structure is shown below:

$GPGGA,HHMMSS.SS,ddmm.mmmm,n,dddmm.mmmm,e,Q,SS,YY.y,+AAAAA.a,M,,,,*CC CR LF where:

$GP = GPS System Talker

GGA = GPS Fix Data Message

HHMMSS.SS = Latest time of Position Fix, UTC. This field is blank until a 3D fix is acquired

ddmm.mmmm,n = Latitude

dd = degress, 00...90 mm.mmmm =

n = minutes, 00.0000....59.9999 direction, N = North, S = South

dddmm.mmmm,e = Longitude

ddd = degress, 000...180 mm.mmmm = minutes, 00.0000....59.9999

e = direction, E = East, W = West

Q = Quality Indicator,

0 = No 3D fix

1 = 3D fix

SS = Number of satellites tracked, 0...8

YY.Y = Dilution of precision, 00.0...99.9

+AAAAA.a,M = Antenna height in meters, referenced to mean sea level

,,,, = Fields for geoidal separation and differential GPS not supported

cc = Check sum message, HEX 00...7F

Check sum calculated by Xoring all bytes between $ and *.

CR =

LF =

Carriage Return

Line Feed

Example:

$GPGAA,151119.00,4307.0241,N,07729.2249,W,1,06,03.2,+00125.5,M,,,,*3F

The example data stream provides the following information:

Time of Position Fix:

Latitude:

Longitude:

Dilution of Precision:

Antenna Height:

Check Sum:

15:11:19.00 UTC

43° 07.0241’ North

77° 29.2249’ West

3D

Satellites Used: 6

3.2

+125.5 meters above sea level

3

TTS220 Manual Rev C Page 108

6.3 SW License Notices

This file is automatically generated from html/copyright.htm

Copyright Notice

[sheepb.jpg] "Clone me," says Dolly sheepishly

_________________________________________________________________

The following copyright notice applies to all files collectively

called the Network Time Protocol Version 4 Distribution. Unless

specifically declared otherwise in an individual file, this notice

applies as if the text was explicitly included in the file.

***********************************************************************

* *

* Copyright (c) David L. Mills 1992-2001 *

* *

* Permission to use, copy, modify, and distribute this software and *

* its documentation for any purpose and without fee is hereby *

* granted, provided that the above copyright notice appears in all *

* copies and that both the copyright notice and this permission *

* notice appear in supporting documentation, and that the name *

* University of Delaware not be used in advertising or publicity *

* pertaining to distribution of the software without specific, *

* written prior permission. The University of Delaware makes no *

* representations about the suitability this software for any *

* purpose. It is provided "as is" without express or implied *

* warranty. *

* *

***********************************************************************

The following individuals contributed in part to the Network Time

Protocol Distribution Version 4 and are acknowledged as authors of

this work.

1. [1]Mark Andrews <[email protected]> Leitch atomic clock

controller

2. [2]Bernd Altmeier <[email protected]> hopf Elektronik serial

line and PCI-bus devices

3. [3]Viraj Bais <[email protected]> and [4]Clayton Kirkwood

<[email protected]> port to WindowsNT 3.5

4. [5]Michael Barone <michael,[email protected]> GPSVME fixes

5. [6]Karl Berry <[email protected]> syslog to file option

6. [7]Greg Brackley <[email protected]> Major rework of WINNT

port. Clean up recvbuf and iosignal code into separate modules.

7. [8]Marc Brett <[email protected]> Magnavox GPS clock driver

8. [9]Piete Brooks <[email protected]> MSF clock driver,

Trimble PARSE support

9. [10]Reg Clemens <[email protected]> Oncore driver (Current maintainer)

10. [11]Steve Clift <[email protected]> OMEGA clock driver

11. [12]Casey Crellin <[email protected]> vxWorks (Tornado) port and

help with target configuration

12. [13]Sven Dietrich <[email protected]> Palisade reference

clock driver, NT adj. residuals, integrated Greg's Winnt port.

13. [14]John A. Dundas III <[email protected]> Apple A/UX port

14. [15]Torsten Duwe <[email protected]> Linux

port

15. [16]Dennis Ferguson <[email protected]> foundation code for

NTP Version 2 as specified in RFC-1119

16. [17]Glenn Hollinger <[email protected]> GOES clock driver

17. [18]Mike Iglesias <[email protected]> DEC Alpha port

18. [19]Jim Jagielski <[email protected]> A/UX port

19. [20]Jeff Johnson <[email protected]> massive prototyping

overhaul

20. [21]Hans Lambermont <[email protected]> or

[22]<[email protected]> ntpsweep

21. [23]Poul-Henning Kamp <[email protected]> Oncore driver (Original

author)

22. [24]Frank Kardel [25]<[email protected]>

PARSE <GENERIC> driver (14 reference clocks), STREAMS modules for

PARSE, support scripts, syslog cleanup

23. [26]William L. Jones <[email protected]> RS/6000 AIX

modifications, HPUX modifications

24. [27]Dave Katz <[email protected]> RS/6000 AIX port

25. [28]Craig Leres <[email protected]> 4.4BSD port, ppsclock, Magnavox

GPS clock driver

26. [29]George Lindholm <[email protected]> SunOS 5.1 port

27. [30]Louis A. Mamakos <[email protected]> MD5-based authentication

28. [31]Lars H. Mathiesen <[email protected]> adaptation of foundation

code for Version 3 as specified in RFC-1305

29. [32]David L. Mills <[email protected]> Version 4 foundation: clock

discipline, authentication, precision kernel; clock drivers:

Spectracom, Austron, Arbiter, Heath, ATOM, ACTS, KSI/Odetics;

audio clock drivers: CHU, WWV/H, IRIG

30. [33]Wolfgang Moeller <[email protected]> VMS port

31. [34]Jeffrey Mogul <[email protected]> ntptrace utility

32. [35]Tom Moore <[email protected]> i386 svr4 port

33. [36]Kamal A Mostafa <[email protected]> SCO OpenServer port

34. [37]Derek Mulcahy <[email protected]> and [38]Damon

Hart-Davis <[email protected]> ARCRON MSF clock driver

35. [39]Rainer Pruy <[email protected]>

monitoring/trap scripts, statistics file handling

36. [40]Dirce Richards <[email protected]> Digital UNIX V4.0 port

37. [41]Wilfredo Sánchez <[email protected]> added support for

NetInfo

38. [42]Nick Sayer <[email protected]> SunOS streams modules

39. [43]Jack Sasportas <[email protected]> Saved a Lot of

space on the stuff in the html/pic/ subdirectory

40. [44]Ray Schnitzler <[email protected]> Unixware1 port

41. [45]Michael Shields <[email protected]> USNO clock driver

42. [46]Jeff Steinman <[email protected]> Datum PTS clock

driver

43. [47]Harlan Stenn <[email protected]> GNU automake/autoconfigure

makeover, various other bits (see the ChangeLog)

44. [48]Kenneth Stone <[email protected]> HP-UX port

45. [49]Ajit Thyagarajan <[email protected]>IP multicast/anycast

support

46. [50]Tomoaki TSURUOKA <[email protected]>TRAK clock

driver

47. [51]Paul A Vixie <[email protected]> TrueTime GPS driver, generic

TrueTime clock driver

48. [52]Ulrich Windl <[email protected]> corrected and

TTS220 Manual Rev C

validated HTML documents according to the HTML DTD

_________________________________________________________________

[53]gif

[54]David L. Mills <[email protected]>

References

1. mailto:[email protected]

2. mailto:[email protected]

3. mailto:[email protected]

4. mailto:[email protected]

5. mailto:[email protected]

6. mailto:[email protected]

7. mailto:[email protected]

8. mailto:[email protected]

9. mailto:[email protected]

10. mailto:[email protected]

11. mailto:[email protected]

12. mailto:[email protected]

13. mailto:[email protected]

14. mailto:[email protected]

15. mailto:[email protected]

16. mailto:[email protected]

17. mailto:[email protected]

18. mailto:[email protected]

19. mailto:jagubox.gsfc.nasa.gov

20. mailto:[email protected]

21. mailto:[email protected]

22. mailto:[email protected]

23. mailto:[email protected]

24. http://www4.informatik.uni-erlangen.de/~kardel

25. mailto:[email protected]

26. mailto:[email protected]

27. mailto:[email protected]

28. mailto:[email protected]

29. mailto:[email protected]

30. mailto:[email protected]

31. mailto:[email protected]

32. mailto:[email protected]

33. mailto:[email protected]

34. mailto:[email protected]

35. mailto:[email protected]

36. mailto:[email protected]

37. mailto:[email protected]

38. mailto:[email protected]

39. mailto:[email protected]

40. mailto:[email protected]

41. mailto:[email protected]

42. mailto:[email protected]

43. mailto:[email protected]

44. mailto:[email protected]

45. mailto:[email protected]

46. mailto:pebbles.jpl.nasa.gov

47. mailto:[email protected]

48. mailto:[email protected]

49. mailto:[email protected]

50. mailto:[email protected]

51. mailto:[email protected]

52. mailto:[email protected]

53. file://localhost/backroom/ntp-stable/html/index.htm

54. mailto:[email protected]

This file is part of the OpenSSH software.

The licences which components of this software fall under are as follows. First, we will summarize and say that all components are under a BSD licence, or a licence more free than that.

OpenSSH contains no GPL code.

1)

* Copyright (c) 1995 Tatu Ylonen <[email protected]>, Espoo, Finland

* All rights reserved

*

* As far as I am concerned, the code I have written for this software

* can be used freely for any purpose. Any derived versions of this

* software must be clearly marked as such, and if the derived work is

* incompatible with the protocol description in the RFC file, it must be

* called by a name other than "ssh" or "Secure Shell".

[Tatu continues]

* However, I am not implying to give any licenses to any patents or

* copyrights held by third parties, and the software includes parts that

* are not under my direct control. As far as I know, all included

* source code is used in accordance with the relevant license agreements

* and can be used freely for any purpose (the GNU license being the most

* restrictive); see below for details.

[However, none of that term is relevant at this point in time. All of

these restrictively licenced software components which he talks about

have been removed from OpenSSH, i.e.,

- RSA is no longer included, found in the OpenSSL library

- IDEA is no longer included, its use is deprecated

- DES is now external, in the OpenSSL library

- GMP is no longer used, and instead we call BN code from OpenSSL

- Zlib is now external, in a library

- The make-ssh-known-hosts script is no longer included

- TSS has been removed

- MD5 is now external, in the OpenSSL library

- RC4 support has been replaced with ARC4 support from OpenSSL

- Blowfish is now external, in the OpenSSL library

[The licence continues]

Note that any information and cryptographic algorithms used in this

software are publicly available on the Internet and at any major

bookstore, scientific library, and patent office worldwide. More

information can be found e.g. at "http://www.cs.hut.fi/crypto".

The legal status of this program is some combination of all these

Page 109

permissions and restrictions. Use only at your own responsibility.

You will be responsible for any legal consequences yourself; I am not

making any claims whether possessing or using this is legal or not in

your country, and I am not taking any responsibility on your behalf.

NO WARRANTY

BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY

FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN

OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES

PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED

OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS

TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE

PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,

REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING

WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR

REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,

INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING

OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED

TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER

PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES.

2)

The 32-bit CRC implementation in crc32.c is due to Gary S. Brown.

Comments in the file indicate it may be used for any purpose without

restrictions:

* COPYRIGHT (C) 1986 Gary S. Brown. You may use this program, or

* code or tables extracted from it, as desired without restriction.

3)

The 32-bit CRC compensation attack detector in deattack.c was

contributed by CORE SDI S.A. under a BSD-style license.

* Cryptographic attack detector for ssh - source code

*

* Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina.

*

* All rights reserved. Redistribution and use in source and binary

* forms, with or without modification, are permitted provided that

* this copyright notice is retained.

*

* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED

* WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE

* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR

* CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OR MISUSE OF THIS

* SOFTWARE.

*

* Ariel Futoransky <[email protected]>

* <http://www.core-sdi.com>

4)

ssh-keygen was contributed by David Mazieres under a BSD-style

license.

* Copyright 1995, 1996 by David Mazieres <[email protected]>.

*

* Modification and redistribution in source and binary forms is

* permitted provided that due credit is given to the author and the

* OpenBSD project by leaving this copyright notice intact.

5)

The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers

and Paulo Barreto is in the public domain and distributed

with the following license:

* @version 3.0 (December 2000)

*

* Optimised ANSI C code for the Rijndael cipher (now AES)

*

* @author Vincent Rijmen <[email protected]>

* @author Antoon Bosselaers <[email protected]>

* @author Paulo Barreto <[email protected]>

*

* This code is hereby placed in the public domain.

*

* THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS

* OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE

* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

* EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

6)

One component of the ssh source code is under a 4-clause BSD license,

held by the University of California, since we pulled these parts from

original Berkeley code. The Regents of the University of California

have declared that term 3 is no longer enforceable on their source code,

but we retain that license as is.

* Copyright (c) 1983, 1990, 1992, 1993, 1995

* The Regents of the University of California. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

TTS220 Manual Rev C Page 110

* This product includes software developed by the University of

* California, Berkeley and its contributors.

* 4. Neither the name of the University nor the names of its contributors

* may be used to endorse or promote products derived from this software

* without specific prior written permission.

*

* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

7)

Remaining components of the software are provided under a standard

2-term BSD licence with the following names as copyright holders:

Friedl

Theo de Raadt

Provos

Song

Campbell

Miller

Steves

Kouril

Allansson

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

*

* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR

* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,

* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF

* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style

Open Source licenses. In case of any license issues related to OpenSSL

please contact [email protected].

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* [email protected].

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* ([email protected]). This product includes software written by Tim

* Hudson ([email protected]).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young ([email protected]).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson ([email protected]).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young ([email protected])"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson ([email protected])"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

---- Part 1: CMU/UCD copyright notice: (BSD like) -----

Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright 1996, 1998-2000 The Regents of the University of California

Reserved

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL

WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR

THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,

INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING

FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF

CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN

CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----

Copyright (c) 2001-2003, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

* Neither the name of the Networks Associates Technology, Inc nor the

names of its contributors may be used to endorse or promote

products derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS

IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

TTS220 Manual Rev C Page 111

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----

Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

* The name of Cambridge Broadband Ltd. may not be used to endorse or

promote products derived from this software without specific prior

written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY

EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN

IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----

Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,

California 95054, U.S.A. All rights reserved.

Use is subject to license terms below.

This distribution may include materials developed by third parties.

Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

* Neither the name of the Sun Microsystems, Inc. nor the

names of its contributors may be used to endorse or promote

products derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS

IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 5: Sparta, Inc copyright notice (BSD) -----

Copyright (c) 2003-2004, Sparta, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

* Neither the name of the Networks Associates Technology, Inc nor the

names of its contributors may be used to endorse or promote

products derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS

IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE

This open software is available for at least three

years, to give any third party, for a charge no more than your

cost of physically performing source distribution, a complete

machine-readable copy of the corresponding source code, to be

distributed under the terms of Sections 1 and 2 above on a medium

customarily used for software interchange

TTS220 Manual Rev C Page 112

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Key Features

  • Provides accurate and reliable time synchronization
  • Utilizes multiple time sources for redundancy and stability
  • Supports various time protocols (NTP, SNTP, PTP)
  • Offers versatile connectivity options (Ethernet, USB, RS-232)
  • Includes GPS receiver for precise timekeeping
  • Compact and rack-mountable design for easy integration
  • User-friendly web interface for easy configuration and management
  • Supports time zone and daylight saving time adjustments
  • Monitors and logs timekeeping performance for reliability and accuracy

Related manuals

Frequently Answers and Questions

What is the accuracy of the TTS 220?
The TTS 220 provides time accuracy within nanoseconds, ensuring precise timekeeping for critical applications.
How does the TTS 220 handle time redundancy?
The TTS 220 utilizes multiple time sources, including GPS and other reference clocks, to ensure time redundancy and reliability.
What time protocols does the TTS 220 support?
The TTS 220 supports various time protocols, including NTP, SNTP, and PTP, allowing for compatibility with a wide range of devices and networks.
Can the TTS 220 be remotely managed?
Yes, the TTS 220 features a user-friendly web interface that allows for remote configuration and management, simplifying its operation and maintenance.
Is the TTS 220 suitable for rack-mounting?
Yes, the TTS 220 has a compact and rack-mountable design, making it suitable for integration into rack-based systems.

advertisement