098-00251-000_rev_a TIME WATCH

TimeWatch Probe

Operation and Service GuideRevision 2.4.03 – April 2009

Symmetricom, Inc.2300 Orchard Parkway

San Jose, CA 95131-1017U.S.A.

http://www.symmetricom.com

Copyright © 2009 Symmetricom, Inc.All rights reserved. Printed in U.S.A.

All product names, service marks, trademarks, and registered trademarksused in this document are the property of their respective owners.

Contents

How to Use This GuidePurpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Structure of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Conventions Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Warnings, Cautions, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . .14Related Documents and Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Where to Find Answers to Product and Document Questions . . . . . . . . . . . . .15What’s New In This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Chapter 1 Introduction and General InformationIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

MTIE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20MRTIE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Standard Telecom MTIE Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Chapter 2 TimeWatch OverviewWhat is TimeWatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Deployment of TimeWatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26TimeWatch Probe Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

TimeWatch Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27TimeWatch Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

TimeWatch Architecture & Communications. . . . . . . . . . . . . . . . . . . . . . . . . . .29Distributed Probes and Centralized Server. . . . . . . . . . . . . . . . . . . . . . . .29Locally Connected Probe And TimeMonitor Application. . . . . . . . . . . . . .31Dry Relay Contact Closure Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Revision A – April, 2009 TimeWatch Operation and Service Guide 3

Table of Contents

Chapter 3 TimeWatch ProbeFront Panel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Rear Panel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

TimeWatch Probe REV0.x Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . .36TimeWatch Probe REV1.x Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . .36

TimeWatch Probe Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Rack Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Power Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Communications Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Input Signal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Dry Relay Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Operational Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

TimeWatch Probe Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Connecting to the TimeWatch Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Configuring the TimeWatch Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

TimeWatch Probe Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Fuse Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Probe Jumper Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Upgrading Probe Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Upgrading TimeWatch Probe Firmware . . . . . . . . . . . . . . . . . . . . . . . . . .49Probe GSM/GPRS SIM Card Fitting/Removal . . . . . . . . . . . . . . . . . . . . .52

TimeWatch Probe Features and Specifications . . . . . . . . . . . . . . . . . . . . . . . .53

Chapter 4 TimeWatch StandaloneProbe Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Using TimeWatch Standalone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Chapter 5 TimeWatch ServerWeb Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Starting a User Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Selecting a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Navigating the TimeWatch Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Viewing the TimeWatch Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Viewing the Status of Your Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Viewing the Data for a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

4 TimeWatch Operation and Service Guide Revision A – April, 2009

Table of Contents

Searching and Displaying Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Viewing and Printing Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Managing and Configuring Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Adding a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Configuring a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Moving Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Removing Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80MTIE Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Phase FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Chapter 6 Interpreting TimeWatch ResultsFrequency Offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Phase Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87GPS Alarm Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88


Table of Contents


Figures

2-1 TimeWatch Elements – Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242-2 TimeWatch Elements – Standalone Mode. . . . . . . . . . . . . . . . . . . . . . . . . .252-3 TimeWatch Standard Operation - Server. . . . . . . . . . . . . . . . . . . . . . . . . . .252-4 TimeWatch Standard Operation - Standalone . . . . . . . . . . . . . . . . . . . . . . .262-5 TimeWatch Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272-6 TimeWatch Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282-7 Ethernet Connectivity to TimeWatch Server . . . . . . . . . . . . . . . . . . . . . . . .302-8 Ethernet Connectivity to Customer-Owned TimeWatch Server. . . . . . . . . .302-9 Dialup Connectivity to Symmetricom TimeWatch Server . . . . . . . . . . . . . .312-10 Ethernet Connectivity to Standalone TimeWatch System . . . . . . . . . . . . . .312-11 Relay Closure Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

3-1 TimeWatch Probe, Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343-2 TimeWatch Probe Rear View Revision 0.x & Below . . . . . . . . . . . . . . . . . .363-3 TimeWatch Probe Rear View Revision 1.x & Above . . . . . . . . . . . . . . . . . .363-4 TimeWatch Probe, Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373-5 Example Cable Setup with Ref in and LAN . . . . . . . . . . . . . . . . . . . . . . . . .393-6 Example Cable Setup with GPS and GSM . . . . . . . . . . . . . . . . . . . . . . . . .403-7 Example of Initial Screen After Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423-8 Main Menu Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433-9 Probe Menu Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433-10 Features Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443-11 General Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443-12 Ethernet Menu Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453-13 Dialup Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .463-14 GPRS Menu Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473-15 Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

4-1 TimeMonitor Application Screenshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

5-1 TimeWatch Server Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615-2 Select Network Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615-3 Main Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .625-4 Example Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635-5 Example Location Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .645-6 Alarm State Process Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .655-7 Example of Exception Analysis by Date . . . . . . . . . . . . . . . . . . . . . . . . . . .665-8 Example of Exception Analysis by Time . . . . . . . . . . . . . . . . . . . . . . . . . . .665-9 Example Location Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .675-10 Example Event Note Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .695-11 Request Phase Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705-12 Example MTIE Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .715-13 Example Phase Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72


List of Figures

5-14 Add Location II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .735-15 Location Personality (Dialup Configuration) . . . . . . . . . . . . . . . . . . . . . . . .745-16 Location Personality (Location & Hardware) . . . . . . . . . . . . . . . . . . . . . . . .745-17 Location Personality (Alarm Notification Alerts). . . . . . . . . . . . . . . . . . . . . .755-18 Location Personality (Heartbeat Configuration). . . . . . . . . . . . . . . . . . . . . .765-19 Location Personality [MTIE Masks] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .775-20 Location Personality [MTIE Display Masks]. . . . . . . . . . . . . . . . . . . . . . . . .785-21 Move Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .795-22 Remove Location II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .795-23 Manage Network [General] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .805-24 Manage Network [MTIE Masks]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .805-25 Manage Network [Phase FTP]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .815-26 Manage Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

6-1 Mtie Showing Frequency Offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .866-2 Phase Graph for Frequency Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .876-3 Mtie for Phase Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .876-4 Phase Graph for Phase Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .886-5 Exception Caused by Loss of GPS Reference . . . . . . . . . . . . . . . . . . . . . .88



Tables

1-1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191-2 Standard Telecom MTIE Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

3-1 PCB Jumper Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483-2 Probe Features and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

5-1 User Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

List of Tables


How to Use This GuideThis section describes the format, layout, and purpose of this guide.

In This PrefacePurpose of This GuideWho Should Read This GuideStructure of This GuideConventions Used in This GuideWarnings, Cautions, Recommendations, and NotesRelated Documents and InformationWhere to Find Answers to Product and Document QuestionsWhat’s New In This GuideContacting Technical Support


How to Use This GuidePurpose of This Guide

Purpose of This Guide

The TimeWatch Operation and Service Guide describes the procedures for installing and using the Symmetricom TimeWatch (TimeWatch). It also provides an overview of TimeWatch operation.

Who Should Read This Guide

Chapter 1, Introduction and General Information, is written for non-technical audiences who need general information about the product. Chapter 2, TimeWatch Overview, and subsequent chapters contain technical information about the product. Other chapters describe installation and configuration instructions or details primarily intended for qualified maintenance personnel.

This Operation and Service Guide is designed for the following categories of users:

Systems Engineers – Chapter 1 provides an introduction to the TimeWatch, cross-references in this chapter direct you to detailed system information in other chapters as appropriate.

Installation Engineers – Chapter 2 through Chapter 6 provide detailed information and procedures to ensure proper installation, operation, configuration, and testing of the TimeWatch.

While Chapter 1 is written for non-technical audiences who need information about the TimeWatch system, others, such as Chapter 2 through Chapter 6 contain detailed information and instructions which are intended to be performed by qualified personnel only.

Structure of This Guide

This guide contains the following sections and appendixes:

Chapter, Title Description

Chapter 1, Introduction and General Information

Provides introductory information about TimeWatch.

Chapter 2, TimeWatch Overview Provides an overview of how TimeWatch monitors the performance of a synchronization network.

Chapter 3, TimeWatch Probe Describes the TimeWatch front and rear panel connections, and provides installation, configuration, and maintenance instructions. This chapter also provides a list of features and specifications.

Chapter 4, TimeWatch Standalone

Provides configuration information for the TimeWatch Probe to work with the TimeMonitor Application.


How to Use This GuideConventions Used in This Guide

Conventions Used in This Guide

This guide uses the following conventions:

Acronyms and Abbreviations – Terms are spelled out the first time they appear in text. Thereafter, only the acronym or abbreviation is used.

Revision Control – The title page lists the printing date and versions of the product this guide describes.

Typographical Conventions – This guide uses the typographical conventions described in the table below.

Chapter 5, TimeWatch Server Provides information on how to start, navigate through, manage, and configure a TimeWatch server user session.

Chapter 6, Interpreting TimeWatch Results

Provides detailed information on interpreting TimeWatch results.

When text appears this way... ... it means:

TimeWatch Operation and Service Guide

The title of a document.

SSUCRITICALIOC1

An operating mode, alarm state, status, or chassis label.

Select File, Open... Click the Open option on the File menu.

Press EnterPress ;

A named keyboard key.The key name is shown as it appears on the keyboard. An explanation of the key’s acronym or function immediately follows the first reference to the key, if required.

SSUSurname:

Text in a source file or a system prompt or other text that appears on a screen.

PINGSTATUS

A command you enter at a system prompt or text you enter in response to a program prompt. You must enter commands for case-sensitive operating systems exactly as shown.

A re-timing application A word or term being emphasized.

Symmetricom does not recommend...

A word or term given special emphasis.

Chapter, Title Description


How to Use This GuideWarnings, Cautions, Recommendations, and Notes

Warnings, Cautions, Recommendations, and Notes

Warnings, Cautions, Recommendations, and Notes attract attention to essential or critical information in this guide. The types of information included in each are explained in the following examples.

Warning: To avoid serious personal injury or death, do not disregard warnings. All warnings use this symbol. Warnings are installation, operation, or maintenance procedures, practices, or statements, that if not strictly observed, may result in serious personal injury or even death.

Caution: To avoid personal injury, do not disregard cautions. All cautions use this symbol. Cautions are installation, operation, or maintenance procedures, practices, conditions, or statements, that if not strictly observed, may result in damage to, or destruction of, the equipment. Cautions are also used to indicate a long-term health hazard.

ESD Caution: To avoid personal injury and electrostatic discharge (ESD) damage to equipment, do not disregard ESD cautions. All ESD cautions use this symbol. ESD cautions are installation, operation, or maintenance procedures, practices, conditions, or statements that if not strictly observed, may result in possible personal injury, electrostatic discharge damage to, or destruction of, static-sensitive components of the equipment.

Electrical Shock Caution: To avoid electrical shock and possible personal injury, do not disregard electrical shock cautions. All electrical shock cautions use this symbol. Electrical shock cautions are practices, procedures, or statements, that if not strictly observed, may result in possible personal injury, electrical shock damage to, or destruction of components of the equipment.

Recommendation: All recommendations use this symbol. Recommendations indicate manufacturer-tested methods or known functionality. Recommendations contain installation, operation, or maintenance procedures, practices, conditions, or statements, that provide important information for optimum performance results.

Note: All notes use this symbol. Notes contain installation, operation, or maintenance procedures, practices, conditions, or statements, that alert you to important information, which may make your task easier or increase your understanding.


How to Use This GuideRelated Documents and Information

Related Documents and Information

Other helpful documents and software tools are listed below. See your Symmetricom representative or sales office for a complete list of available documentation.

Where to Find Answers to Product and Document Questions

For additional information about the products described in this guide, please contact your Symmetricom representative or your local sales office. You can also contact us on the web at www.symmetricom.com.

What’s New In This Guide

This is the first release of the User's Guide.

Contacting Technical Support

If you encounter any difficulty installing the update or operating the product, contact Symmetricom Global Services at:

Europe, Middle East, and Africa (EMEA) Call Center:Symmetricom Global Services EMEAFichtenstr. 2585649 Hofolding Germany

Tel: +49 700 3288 6435Fax: +49 8104 662 433

E-mail: [email protected]: http://www.symmetricom.com

Note: Symmetricom offers training courses designed to enhance your knowledge of TimeWatch. Contact your local representative or sales office for a complete list of courses and outlines.


How to Use This GuideContacting Technical Support


Chapter 1 Introduction and General Information

This Chapter provides introductory information for using this manual and TimeWatch.

In This ChapterIntroductionAbbreviationsDefinitionsStandard Telecom MTIE Masks


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

Chapter 1 Introduction and General InformationIntroduction

Introduction

This manual covers features supported in TimeWatch Probe Firmware and Server Software version 2.4.03.

TimeWatch is a fully automated 24x7 Sync Audit® and Test and Measurement system.

The TimeWatch system can operate in one of two modes:

In a distributed network mode TimeWatch is a solution for continuously monitoring the performance of a synchronization network centrally without the need for site visits. The system consists of a number TimeWatch Probes, deployed at various locations in the synchronization network that is to be monitored, and a central TimeWatch Server, which communicates with system users via a Web-based interface.

In a standalone, lab-based, equipment testing or bench mode the TimeWatch probe communicates directly with Symmetricom’s TimeMonitor software to make live, real time measurements.

TimeWatch Probes are available in two variants:

TimeWatch Standard: TimeWatch Probe using an internal TimeWatch TIE engine making MRTIE measurements between two external clock signals.

TimeWatch Reference: TimeWatch Probe as for Standard but with the addition of an internal GPS-corrected reference oscillator – making MTIE measurements between one external clock signal and the internal GPS-derived clock signal.

Common hardware is used for both variants; the Reference version has additional hardware. Whether the probe communicates its measurement data to a centralized server or to a locally connected PC is determined by a firmware configuration setting.

Abbreviations

The abbreviations used in this document and their meanings are listed in the following table.


http://www.syncwatch.com

Chapter 1 Introduction and General InformationAbbreviations

Table 1-1. Abbreviations

Item Definition

DHCP Dynamic Host Configuration Protocol

DNS Domain Name ServerDPCE Data Processing and Communications Engine

ETSI European Telecommunications Standards InstituteFTP File Transfer Protocol

GPRS General Packet Radio ServiceGPS Global Positioning System

GSM Global System for Mobile communications

LAN Local Area NetworkLOS Loss Of Signal

MRTIE Maximum Relative Time Interval ErrorMTIE Maximum Time Interval Error

NMEA National Marine Electronics Association PCB Printed Circuit Board

PLL Phase Locked LoopPLMN Public Land Mobile Network

ppm parts per millionPRC Primary Reference Clock

PSTN Public Switched Telephone NetworkRAS Remote Access Server

SSH Secure Shell

SIM Subscriber Identity ModuleSNMP Simple Network Management Protocol

SMS Short Message ServiceTIE Time Interval Error


Chapter 1 Introduction and General InformationDefinitions

Definitions

This section provides a list of common acronyms and definitions.

MTIE

MTIE is one of the key quality metrics for telecom synchronization. It is defined as "The maximum peak-to-peak delay variation of a given timing signal with respect to an ideal timing signal within an observation period for all observation periods of that length (t) within the measurement period (T).” It is effectively the worst case wander measured on a signal over a certain period.

MRTIE

MRTIE is defined as "The maximum relative peak-to-peak delay variation of an output timing signal with respect to a given input timing signal within an observation period for all observation periods of that length (t) within the measurement period (T).” For example, time error measured between the input and output of a slave clock. It is effectively the worst case relative wander measured between two signals over a certain period.

GPS

Global Positioning System, a US government-owned orbiting satellite system. These satellites are primarily intended to give positioning information for navigation but can also be used to derive a highly accurate timing source of PRC quality. To use GPS, an antenna and a post-processing unit are required which can output signals meeting the G.811 and ETSI 300 462-6-1 standards.

PLL

Phase Locked Loop - A mechanism for locking a voltage controlled oscillator to a frequency reference of higher stability.

Standard Telecom MTIE Masks

The table below shows the MTIE mask values for the standard TimeWatch observation periods, as defined by the relevant standards bodies.


http://hp.vector.co.jp/authors/VA002416/teraterm.html

Chapter 1 Introduction and General InformationStandard Telecom MTIE Masks

Table 1-2. Standard Telecom MTIE Masks

Observation Period

EN 300 462-3-1 (G.823) Data

EN 300 462-3-1 PRC

EN 300 462-3-1 SSU

EN 300 462-3-1 SEC

1 9000 25 25 250

4 9000 25 40 40010 9000 25 100 1000

40 11200 25 400 2000100 18000 30 1000 2000

300 18000 90 2000 2000900 18000 270 2000 2000

1800 18000 300 2000 2000

3600 18000 300 2263 22637200 18000 300 2630 2630

14400 18000 300 3083 308328800 18000 300 3664 3664

86400 18000 864 5069 5069


Chapter 1 Introduction and General InformationStandard Telecom MTIE Masks


Chapter 2 TimeWatch Overview

This Chapter provides an overview of TimeWatch operation.

In This ChapterWhat is TimeWatchDeployment of TimeWatchTimeWatch Probe OverviewTimeWatch Architecture & Communications


Chapter 2 TimeWatch OverviewWhat is TimeWatch

What is TimeWatch

TimeWatch is a fully automated 24x7 Sync Audit® and Test and Measurement system: in its distributed network mode, it is a solution for continuously monitoring the performance of a synchronization network centrally without the need for site visits. It consists of a TimeWatch Probe, deployed at the location in the synchronization network that is to be monitored, and a central TimeWatch Server, which communicates with system users via a Web-based front end.

Email and SMS messages can be automatically sent to the appropriate engineers upon detection of a synchronization problem. In addition to the TimeWatch Server alert system, probes can optionally interface to a relay closure alarm system.

The TimeWatch Server can be owned and managed by Symmetricom or installed on a customer’s site. It is accessed via a standard Web browser (e.g. Mozilla Firefox or Microsoft Internet Explorer) and hosted on a Microsoft Windows server. The server contains a database of all probes and monitoring information received from them, can generate TIE and MTIE plots for measurement locations, and provides the ability to configure the locations individually.

Figure 2-1. TimeWatch Elements – Server Mode

TimeWatch is a fully automated 24x7 Sync Audit® and Test and Measurement system: in its standalone, lab-based, equipment testing or bench mode it is a solution to make live, real-time TIE measurements. It consists of a TimeWatch Probe connected locally to the TimeMonitor application running on the connected PC. Through the TimeMonitor Analyzer application which is a part of the TimeMonitor suite this measurement data can be post-processed into the industry-standard metrics MTIE, TDEV etc.

Sync Engineer

Email/SMS Alert!

LANPSTNPLMN

CentralServer

TimeWatch Probe

Database


Chapter 2 TimeWatch OverviewWhat is TimeWatch

Figure 2-2. TimeWatch Elements – Standalone Mode

TimeWatch Probes are available in two variants:

TimeWatch Standard: TimeWatch Probe using an internal TimeWatch TIE engine making MRTIE measurements between two external clock signals.

TimeWatch Reference: TimeWatch Probe as for Standard but with the addition of an internal GPS-corrected reference oscillator – making MTIE measurements between one external clock signal and the internal GPS-derived clock signal.

Common hardware is used for both variants; the Reference version has additional hardware. Whether the probe communicates its measurement data to a centralized server or to a locally connected PC is determined by a firmware configuration setting.

From an external perspective the basic functionality of each TimeWatch Probe variant is the same:

When operating with the centralized server they compare the calculated MTIE against a chosen MTIE threshold mask and generate an exception if the mask is exceeded. They send a regular heartbeat to the server to confirm that they are still operational. The heartbeat message contains the current MTIE measurement.

Figure 2-3. TimeWatch Standard Operation - Server

Time Monitor Application

TimeWatch Probe

2 MHz or 2 Mbit/sfrom E1 or STM -N line from c lient or reference signal

2 MHz or 2 Mbit/s from

network E1 or STM-N line

Exception if MRTIE is above

mask

Heartbeat if MRTIE is below

mask

Compare with MRTIE mask

Phase comparator and MRTIE calculator


Chapter 2 TimeWatch OverviewDeployment of TimeWatch

When operating standalone with the connected TimeMonitor application they calculate live TIE values between the signals under test and directly send this data to the PC Application for live display, storage and further off-line processing.

Figure 2-4. TimeWatch Standard Operation - Standalone

Deployment of TimeWatch

The TimeWatch system has been designed to be flexible and support a number of modes of operation to quantify and report on synchronization performance.

In its distributed network mode there are a number of possible scenarios for deployment. The probes can be used to monitor or police Service Level Agreements (SLAs), guarantee the delivered synchronization quality, detect and locate synchronization problems within the network and track/locate intermittent faults.

Probes can be located at:

Key service delivery points

Corporate clients

Major carrier interconnects

Critical traffic nodes

Trouble spots

In its lab-based, equipment testing or bench mode the TimeWatch system is suited to making direct measurements in a test scenario in a lab, or perhaps for equipment commissioning in the field.

2 MHz or 2 Mbit/sfrom E1 or STM -N line from c lient or reference signal

2 MHz or 2 Mbit/s from

network E1 or STM-N line

Data framingand comms

Phase comparator and TIE calculator


Chapter 2 TimeWatch OverviewTimeWatch Probe Overview

For example:

R&D testing

Equipment Qualification/Type Approval

Equipment/System commissioning

TimeWatch Probe Overview

There are two types of TimeWatch Probes: TimeWatch Standard and TimeWatch Reference.

TimeWatch Standard

The Standard variant of TimeWatch is designed to perform an MRTIE measurement between two external clock inputs. The inputs are independent and each can be either a 2.048 MHz clock or an E1 2.048 Mbit/s signal.

The probe uses an internal TIE measurement engine that compares two external inputs at 80 samples per second (80Hz) and calculates the relative phase. This data is averaged to produce one TIE value for each second, this is then used to calculate the MRTIE between the two inputs.

Figure 2-5. TimeWatch Standard

In the distributed network mode the data processing and communications engine computes the MRTIE from the individual TIE readings.

Data Processing &Communications

EngineTIE Measurement

Engine

Measure In Clock Source to bemonitored - E1 or

2.048 MHz

Ref In Reference clocksource - E1 or

2.048MHz 10/100 BaseT Ethernet

Ref OutOptional

2.048 MHz output

Modem ModulePSTN/GSM

Modem

AntennaCable

Phone Line

GSM AntennaOptional

TimeWatch Probe

RS232 Admin Port

Modem module option only

supported in server mode


Chapter 2 TimeWatch OverviewTimeWatch Probe Overview

The calculated MRTIE is a worst case MRTIE from the start of the measurement period which begins at probe initialization and is restarted if the mask is exceeded. The computed MRTIE is compared against the chosen mask, and an exception is generated if the mask is exceeded.

To aid with fault analysis, TIE data is sent to the server for both the 15 minute period before and the 15 minute period after the exception. The uploaded TIE data is at a reduced resolution of 1 value per 10 seconds. (At present no analysis is performed on the TIE data before reducing resolution, simply every 10th TIE sample is plotted; it is worth noting that this may produce aliasing effects.)

A 2.048 MHz output can be provided in the case that the reference input signal is 2.048 MHz. The auxiliary output is a copy of the reference input signal and is available for connection to measurement or other external equipment. Jumpers must be changed to enable the auxiliary output - the required settings are shown in Table 3-1 in Probe Jumper Settings, on page 48.

In its lab-based, equipment testing or bench mode the probe firmware handles communications with the attached PC application, formats and then streams the live TIE measurement data directly to the to the application. The application can then be used to view, store and further analyze the measurement data.

TimeWatch Reference

TimeWatch Reference uses the same hardware platform as TimeWatch Standard but with the addition of an internal GPS/PLL engine. This provides a known reference for the probe and in addition a 2.048 MHz auxiliary output which can be used to clock additional local measurement equipment.

Figure 2-6. TimeWatch Reference

GPS/PLL Engine

Data Processing&

CommunicationsEngine

TIE SensorPLL/VCTCXOGPS Rx 10/100 BaseT Ethernet

TimeWatch Probe

Modem ModulePSTN/GSM

Modem

AntennaCable

Phone Line

Measure InClock to be

monitored - E1 or2.048 MHz

Aux Out

2.048 MHz

GSM AntennaOptional

GPS Antenna Modem module

option only supported in server mode


Chapter 2 TimeWatch OverviewTimeWatch Architecture & Communications

The data processing and communications engine computes the MTIE from the individual TIE readings between the GPS/PLL clock and the measurement in signal. The calculated MTIE is a worst case MTIE from the start of the measurement period, which begins at probe initialization and is restarted if the mask is exceeded. The computed MRTIE is compared against the chosen mask, and an exception is generated if the mask is exceeded.

The auxiliary output is provided from a GPS-disciplined oscillator and is available for reference purposes.

In its lab-based, equipment testing or bench mode the probe firmware handles communications with the attached PC application, formats and then streams the live TIE measurement data directly to the to the application. The application can then be used to view, store and further analyze the measurement data.

TimeWatch Architecture & Communications

This section provides information on the methods of communication between the TimeWatch Probe and the server.

Distributed Probes and Centralized Server

There are a number of ways that a TimeWatch Probe can communicate with its server, which can be either customer-owned or provided by Symmetricom as part of a managed service.

Connectivity to the server can be via Ethernet or via a dialup service over PSTN or GSM/GPRS.

The use of Ethernet to connect via the LAN and corporate IT network to a Symmetricom server is shown in Figure 2-7.



Figure 2-7. Ethernet Connectivity to TimeWatch Server

If a customer wants their own server then communication between probe and server take place via the customer’s DCN and corporate network as shown in Figure 2-8.

Figure 2-8. Ethernet Connectivity to Customer-Owned TimeWatch Server

In some circumstances Ethernet communications will not be available at the site where the probe is deployed. In this case dialup connectivity can be utilized as shown in Figure 2-9. A socket modem must be fitted to the probe to allow GSM/GPRS or PSTN connectivity. In the case of GSM/GPRS the customer will supply the SIM card.

DC Corp IT

Network

Customer Network

Customer Owned TimeWatch

Server

Ethernet

Customer Sync Team

Server Access and Email Alerts

TimeWatch Probe



Figure 2-9. Dialup Connectivity to Symmetricom TimeWatch Server

Locally Connected Probe And TimeMonitor Application

The only method of communication supported in standalone mode is over the probe’s Ethernet LAN port to a locally connected PC running the TimeMonitor application.

Figure 2-10. Ethernet Connectivity to Standalone TimeWatch System

EquipmentUnderTest

Ethernet

Customer Sync Team

Time MonitorApplication

TimeWatch Probe



Dry Relay Contact Closure Alarms

The probes support relay closure alarms which can be connected to traditional alarm monitoring systems as shown in Figure 2-11. These can be used as the primary method of exception reporting if no other method of communication from the probe is available or as a backup or additional communications path when using LAN, PSTN or GSM/GPRS communications.

The relay will close for 15 minutes if the MTIE mask is exceeded. The relay is also switched to its alarm state if a hardware fault occurs, for example loss of measure in signal.

Figure 2-11. Relay Closure Monitoring

DCN DCN

TimeWatch Probe

Synchronisation Distribution

Shelf

Dry Relay Alarm

Relay Closure Management System

Contact Monitoring


Chapter 3 TimeWatch Probe

This chapter provides information on TimeWatch Probe connectors, installation, configuration, and details on upgrading firmware. The TimeWatch Probe is deployed in the network at the point where the synchronization quality is to be measured.

In This ChapterFront Panel Connections Rear Panel ConnectionsTimeWatch Probe InstallationTimeWatch Probe ConfigurationTimeWatch Probe MaintenanceUpgrading Probe FirmwareTimeWatch Probe Features and Specifications


Chapter 3 TimeWatch ProbeFront Panel Connections

Front Panel Connections

This section provides information on front panel connectors.

Figure 3-1. TimeWatch Probe, Front View

The front of the TimeWatch Probe contains the main interfaces and indicators.

The probe’s front-panel connectors are as follows:

Measure In (BNC)M(R)TIE is computed on the relative phase between this input and either the Ref In input (TimeWatch Standard) or internal GPS/PLL (TimeWatch Reference). The interface must be configured from the TimeWatch server to be a full height 2.048Mbit/s (G.703 sec. 9), a 30dB down 2.048Mbit/s signal (G.703 sec. 9) or a 2.048MHz signal (G.703 sec. 13).

Ref In (BNC)This input is only used in TimeWatch Standard. It is used for the input of a reference clock signal.

MRTIE is computed on the relative phase between this input and the Measure In interface.

The interface must be configured from the TimeWatch server to be a full height 2.048Mbit/s (G.703 sec. 9), a 30dB down 2.048Mbit/s signal (G.703 sec. 9) or a 2.048MHz signal (G.703 sec. 13).

Aux Out (BNC)This output has a different functionality on each of the TimeWatch variants:

Standard: Can optionally provide a buffered copy of the Ref In signal; this interface can only be used if the Ref In interface is a 2.048MHz signal.

Reference: A 2.048MHz (G.703 sec. 13) output. This output is driven from the built-in GPS PLL module. In normal operation this will be derived from the GPS receiver. If the GPS receiver fails, this output will not maintain good performance: no holdover mode is implemented.


Chapter 3 TimeWatch ProbeRear Panel Connections

GPS Antenna (SMA)This connector is used only for the TimeWatch Reference variant for connection to an external GPS antenna to enable reception of an MTIE reference signal.

GPS Antenna (LOS LED)If the GPS module experiences a ‘loss of lock’ event then the GPS LOS LED will illuminate until the event clears. The event will also be reported to the TimeWatch server for display. This feature is only available with the TimeWatch Reference Option fitted.

GSM Antenna (SMA)This connector is used for connecting the probe to an external GSM/GPRS antenna for communication with the server. An optional internal GSM/GPRS modem must be installed to enable this option.

PSTN Analogue Modem (RJ11)This connector is used for connecting the probe to a PSTN network for communication with the server. An optional internal PSTN modem must be installed to enable this option.

LAN (RJ45)This connector is used for connecting the probe to an Ethernet network to enable communication with the server. It is available on all TimeWatch variants. The probe will automatically detect the data rate of the network; however it may be necessary to configure other network parameters before normal operation. This port will auto-negotiate and run at speeds of either 10 or 100BASE-T.

Alarm Relay ContactThis interface uses a three pin terminal block with Normally Open, Common and Normally Closed pins. It can optionally be connected to an external alarm management system. If an MTIE exception occurs, the relays will be switched and will remain in the active state until a minimum of 15 minutes after MTIE is within the configured mask. The relay will also be in its alarm state if power fails to the probe or if any hardware fault is detected, for example loss of Measure In signal.

Power (-48vDC)This is the power supply connector and has four pins. Pin 1 is the positive voltage V+, nominally 0V; pin 2 is the negative voltage, nominally -48V; pin 3 is ground; pin 4 is unused.

Rear Panel Connections

There are two versions of the TimeWatch Probe rear panel and both panels have two RS-232 connectors. Figure 3-2 shows the rear panel version with a management port and SSU interface, and Figure 3-3 shows the rear panel version with a management port and GPS NMEA interface.


Chapter 3 TimeWatch ProbeTimeWatch Probe Installation

TimeWatch Probe REV0.x Rear Panel

Management Port (9-Way D-Type)This interface is used for configuration of the probe.

SSU Interface Rev0.0 & Below (9-Way D-Type)This interface is reserved for future use.

Figure 3-2. TimeWatch Probe Rear View Revision 0.x & Below

TimeWatch Probe REV1.x Rear Panel

Management Port (9-Way D-Type)This interface s used for configuration of the probe.

GPS NMEA (9-Way D-Type)This interface (if fitted) is an engineering tool used for obtaining GPS stats. Please contact your reseller or support representative for more information on this feature.

Figure 3-3. TimeWatch Probe Rear View Revision 1.x & Above

TimeWatch Probe Installation

This section provides information on installing the TimeWatch Probe including rack mounting and cable connections.

Rack Mounting

TimeWatch is designed for mounting in an ETSI (600mm wide), or 19” rack mounting. Two different bracket types are provided with a TimeWatch Probe, one for each of the rack widths. These brackets are fitted to the side of the probe using 4 small cross head screws (supplied). The smaller brackets are fitted for 19” and the larger for 600mm ETSI racks.



The brackets can be mounted so that the front of the probe is recessed in the rack to allow room for cabling. The front pair of fixing screws on the bracket are used for flush mounting, and the rear two for recessed mounting.

The shelf is mounted to the rack using four fixing bolts (not supplied as standard).

Figure 3-4. TimeWatch Probe, Front View

Power Connections

On installation -48VDC power should be connected via a 1amp fuse.

Pin 1 is the positive voltage V+, nominally 0V

Pin 2 is the negative voltage, nominally -48V

Pin 3 is ground. Pin 4 is unused.

Power supply rating: -48 Volts (-40.5V to -57V)

For safety reasons voltages of magnitude greater than 60V should never be connected to a TimeWatch Probe.

Communications Cabling

There are four options for communication between the TimeWatch Probe and its server:

Ethernet LAN

Note: Before connecting power or the PSTN line, the TimeWatch Probe case should be grounded using the external ground terminal. The earth fixing screw is on the rear of the probe.

2 x Bracket Fixing Screw

2 x Rack Fixing Bolts

PowerConnector

2 x Bracket Fixing Screw

LANConnectorGSM

AntennaGPS Antenna

Ref In Measure In

2 x R kFixing Bolts



GSM dialup

GPRS connection

PSTN dialup

The system should be either pre-configured with its communications settings or commissioned to set its communication settings after installation (see TimeWatch Probe Configuration, on page 41).

Communication cables should be fitted if required.

For LAN connection a 10 or 100BASE-T Ethernet cable is required with an RJ45 connector.

For PSTN dialup a telephone cable with an RJ11 connector is required; a PSTN socket modem must be pre-fitted to the Probe to enable this option.

For GSM dialup or GPRS an antenna connector should have been pre-fitted to the front of the probe, and a GSM/GPRS socket modem and SIM card internally installed.

When communicating directly with the TimeMonitor application only LAN based connection is supported.

Input Signal Cabling

Signals to be measured should be connected to Measure In, Ref In and GPS as appropriate.

Signal Input CablingMeasure In and Ref In signals should be 2.048Mbit/s (G.703 sec. 9) or 2.048MHz (G.703 sec. 13). The 2.048Mbit/s signal can be connected via a tap/monitor point (up to 30dB down).

Connector GPS Fitted GPS Not Fitted

Measure In Connect Connect

Ref In Disconnected Connect

GPS Antenna Connect No connector

Note: If GPS is not required no GPS receiver or antenna will be fitted to the probe.



The TimeWatch Server operator needs to be informed of the signal type and whether the signal is a tapped or direct connection.

The connectors used on the Measure In and Ref In are 75 BNC. If 120Ω signals are to be measured a balun should be fitted externally to the Probe to match the impedance.

Figure 3-5. Example Cable Setup with Ref in and LAN

GPS CablingThe standard TimeWatch antenna has a 3m cable and is a small magnetic mount antenna. It is ideal for fixing to the top of cabinets and cabins. If the roof is not magnetic, a metal plate can be fitted to ensure mechanical stability. A larger antenna is available for longer cable runs allowing up to 50m of cable if required.

The system has been fully tested with cables up to 50m in length and in standard usage cable lengths should be kept below this length.

Note: It may be necessary to use -25dB or -20dB passive taps if cable distances exceed 3 Meters from the tap. This is to ensure that when the signal reaches the probe it is within the range expected for -30dB.

Measure In

Full G.703 signals or via tap

Baluns fitted if required Power & Ground

DDF

LAN 10/100 BASE-T

Ref In



Figure 3-6. Example Cable Setup with GPS and GSM

Dry Relay Alarms

The alarm relay interface uses a three pin terminal block with Normally Open, Common and Normally Closed pins. It can optionally be connected to an external alarm management system. Relay alarm contacts can be connected if required. Most types of single strand cable are suitable for dry relay alarm connection.

Operational Verification

Before leaving the site the probe should be power-cycled by removing/replacing the power connector, and it should be confirmed that a startup heartbeat is received by the TimeWatch Server within 1-2 minutes.

For the probe to send a startup heartbeat it will need to be configured: this can be performed by following the steps in TimeWatch Probe Configuration, on page 41.

Measure In

GPS

GPS antenna on building r oof with c lear view of sky

DDF

Full G.703 s ignal or via t ap

Balun f itted if required

GSM a ntenna

Power & ground

Standard antenna 3m max imum


Chapter 3 TimeWatch ProbeTimeWatch Probe Configuration

TimeWatch Probe Configuration

This section provides information on configuring a TimeWatch Probe.

Connecting to the TimeWatch Probe

On or prior to installation the probe must be configured to setup its connection to the server. A menu-driven ASCII interface is available on the RS-232 Management Port and telnet/SSH on the Ethernet port.

Connecting Via EthernetUsing this configuration method a telnet or SSH connection is used to configure the Probe. A crossover Ethernet cable or Ethernet hub with no network connection is required to connect a PC to the Ethernet port if it is not on an existing network.

Configure the Management PCThe factory default address of the probe is 192.168.1.1. It will be necessary to change the IP address of the PC configuring the probe.

Under Windows this can be achieved by opening Network and Dial-up Connections from Control Panel, right-clicking on Local Area Connection, selecting Properties, selecting Internet Protocol, and selecting Properties. Set the IP address to 192.168.1.2 and subnet mask to 255.255.255.0.

If the IP address of the probe has been previously changed then the new IP address needs to be entered via telnet or SSH; the PC must be connected to the same network. If the IP address of the probe is not known this can be changed or retrieved as detailed in Connecting Via RS-232, on page 42.

Connect to the ProbeUsing a telnet/SSH client (not Windows telnet), connect to the probe.

After connection a login screen will show. Enter the username swconf and when prompted enter the password fr7ebi.

This will enter a menu-driven configuration interface as described in Configuring the TimeWatch Probe, on page 42.

Note: The Windows “telnet” program will not correctly connect to the probe, so an alternative application is required. Symmetricom recommends ‘Putty’, which is available from http://www.chiark.greenend.org.uk/~sgtatham/putty/

Note: It is good practice to note the current Windows network configuration so that it can be re-entered after the probe has been configured.



Connecting Via RS-232First, connect to the Management Port (9-way female D-Type) of the probe using an RS-232 cable. Use a terminal emulator like HyperTerminal to communicate with the probe; the interface is configured to operate at 115,200 baud with 8 data bits, no parity, 1 stop bit and no flow control.

The terminal emulator should be set to emulate VT102; under HyperTerminal this mode is not fully tested so use auto-detect or VT100J mode. In HyperTerminal the boxes will be drawn with other characters but the application will function correctly.

Tera Term Pro can emulate VT102 correctly and works well with TimeWatch. It can be downloaded from http://hp.vector.co.jp/authors/VA002416/teraterm.html

On connection to the probe a login prompt will be displayed – press enter if this does not occur. It may be necessary to power-cycle the probe to obtain the prompt, which will appear after startup messages.

After connection a login screen will show. Enter the username swconf and when prompted enter the password fr7ebi.

This will enter the menu-driven configuration interface as described in Configuring the TimeWatch Probe, on page 42.

Configuring the TimeWatch Probe

This section describes the TimeWatch Probe menus.

Navigating the Menu System

Upon login, the following screen will display for a few seconds:

Figure 3-7. Example of Initial Screen After Login

After this, the main menu screen will display:

Note: Depending on the application used to access these menus, the screen may be laid out slightly differently. These example screens are obtained using Putty interfacing via a LAN.



Figure 3-8. Main Menu Screen

Use the up and down arrows to select the desired menu item (Probe, Server, Ethernet, Dialup or GPRS) and press enter to select that menu option.

Probe Configuration

Figure 3-9. Probe Menu Screen

Serial #: This is the serial number of the probe and identifies it as a unique entity on the TimeWatch Server.

CW-10 GPS installed: Select whether TimeWatch Standard or TimeWatch Reference is to be used. Press the space bar to select or de-select this option. A hash [#] indicates that the option is enabled, a blank [ ] indicates it is disabled

[Main Menu]: After appropriate changes are made, use the down arrow to select this, then press enter.



Features

Figure 3-10. Features Menu

Lab License: This license key, if entered, unlocks the TimeMonitor application functionality. The License key is supplied with the probe or can be obtained from your support/channel partner.

General Configuration

Figure 3-11. General Menu Screen

Operate With: Select whether Remote Server (TimeWatch) or TimeMonitor application is to be used. Use left and right arrows to select the required option.

Comms: Select whether Ethernet, GSM, GPRS or PSTN is to be used to communicate to the server. Use left and right arrows to select the required method.

NOTE: if TimeMonitor is selected, the only configurable option is the Lab Configuration port.



Host: This is the IP address (e.g. 172.31.1.1) or domain name (e.g. www.timewatch.com) of the TimeWatch Server.

A domain name can only be used with DHCP, if a DNS address is entered in the Ethernet menu, or if GSM/PSTN dialup is used and the RAS can provide a DNS address. This is a mandatory field and must be completed for the probe to connect to the server.

Port: This is the port number on which access is provided at the TimeWatch Server (default 80).

HTTP Proxy Host: This is the IP address or domain name of the proxy server. This field should only be filled in if a proxy server is used.

HTTP Proxy Port: This is the port number on which HTTP proxying is available on the proxy server. This is not required to be filled unless a proxy server is used; it will be specific to the network that the probe is connected to.

Port (Lab Configuration): This is the port number that the TimeWatch probe will use to communicate with the TimeMonitor application. Only applicable if TimeMonitor has been specified in the Operate With field.

[Main Menu]: After appropriate changes are made, use the down arrow to select this, then press enter.

Ethernet Configuration

Figure 3-12. Ethernet Menu Screen

NOTE: When Operate With TimeMonitor is selected – the only communications medium that is supported is Ethernet.



Use DHCP: If this is enabled then the module will request its Ethernet configuration over the network. IP address, subnet mask, gateway and DNS addresses do not need to be entered unless DHCP is disabled. A hash [#] indicates that DHCP is enabled, a blank [ ] indicates it is disabled. Toggling between enabled and disabled is achieved using the space bar.

IP Address: The IP address of the probe (e.g. 172.31.2.5). It may only be entered if DHCP is disabled.

Subnet: The subnet mask of the network that the probe is connected to (e.g. 255.255.255.0). It may only be entered if DHCP is disabled.

Gateway: The IP address of the probe’s default gateway (e.g. 172.31.2.1). It may only be entered if DHCP is disabled.

DNS 1: The IP address of the primary Domain Name Server. This is not required if no domain names are used on this screen (i.e. all addresses are IP addresses). It may only be entered if DHCP is disabled.

DNS 2: The IP address of a secondary Domain Name Server. This is optional, and may only be entered if DHCP is disabled.

[Main Menu]: After appropriate changes are made, use the down arrow to select this, then press return.

Dial-Up Configuration

Figure 3-13. Dialup Menu Screen

Phone #: The Dialup number of the remote access server (RAS) that the probe will dial into. This field is only required if server communications is PSTN or GSM.

Username: The username for RAS dialup access.

Password: The password for RAS dialup access.


Chapter 3 TimeWatch ProbeTimeWatch Probe Maintenance

GPRS Configuration

Figure 3-14. GPRS Menu Screen

Gateway: The access point name (APN).

Username: The username for RAS dialup access.

Password: The password for RAS dialup access.

TimeWatch Probe Maintenance

This section describes fuse replacement and changes to Probe jumper settings.

Fuse Replacement

The TimeWatch Probe contains two fuses. If either of these fuses is suspected of being blown, the TimeWatch Probe should be disconnected from its -48V supply and the PSTN connector, if used, should also be disconnected. The applied voltage should be measured to check that it conforms to the -40.5 to -57V specification.

To confirm that fuses are blown, they should be removed and checked. The fuses are located inside the probe and the screws on the bottom of the probe and those associated with the RS-232 connectors on the rear need to be removed before the fuses can be accessed.

The fuses are located near the power connector. If a blown fuse is found it should be replaced with an identical new fuse (1A A/S fuse).


Chapter 3 TimeWatch ProbeUpgrading Probe Firmware

The fuse is replaced by removing the top of the fuse holder to access the fuse. The box should be re-assembled and re-mounted; the power can then be reapplied. If the fuse blows a second time the probe should be returned for repair.

Probe Jumper Settings

Jumpers on the TimeWatch Probe PCB are used to change between variants. Additionally in TimeWatch Standard, the jumpers can be changed to pass out a 2.048MHz clock derived directly from the Ref In signal to Aux Out. This output and the TimeWatch Probe when configured in this manner will only work correctly if Ref In is a 2.048MHz signal.

Upgrading Probe Firmware

Periodically, new versions of probe firmware will be made available;

Warning: Fuse replacement requires the case to be opened by competent personnel. This must only be done with the power and PSTN lines disconnected. Care must be taken when removing the case of a TimeWatch Reference probe REV1.1 (GPS option fitted) as a cable connects from the PCB to the GPS NMEA port on the inside rear of the case. Do not remove the two hex-head jack screws from the GPS NMEA port.

Warning: Probe Jumper setting changes requires the case to be opened by competent personnel. This must only be done with the power and PSTN lines disconnected. Care must be taken when removing the case of a TimeWatch Reference probe REV1.1 (GPS option fitted) as a cable connects from the PCB to the GPS NMEA port on the inside rear of the case. Do not remove the two hex-head jack screws from the GPS NMEA port.

Table 3-1. PCB Jumper Settings

Variant Aux Out LK4 LK5 LK6 LK7 LK8

Standard No 2-3 2-3 N/A1

Note:1 N/A = Not applicable: can be in any state

2-3 2-3

Yes 1-23-4

1-23-4

2-3

Reference Yes 1-2



(i) The Standalone probe firmware can be upgraded using a simple procedure that is included with the firmware release

(ii) The TimeWatch Server can automatically and remotely upgrade probe firmware if an upgrade is available and the administrator controls if the probes are to be upgraded. If so, the firmware will be placed into the firmware repository on the TimeWatch Server and be available for the probe to download.

To upgrade the firmware, the probe is flagged for firmware upgrade on the server. When the probe next communicates with the server it will download the firmware file.

To flag a probe for firmware upgrade, navigate to the “Manage Locations” main menu then the “Upgrade Firmware” sub-menu. This will bring up the “Upgrade Location” screen.

Figure 3-15. Upgrade Firmware

Check the upgrade checkbox for the probe(s) to be upgraded then click “Save”. Firmware download will be initiated on the next communication after upgrade has been selected for the selected probes.

During software download, normal TimeWatch functionality is suspended and no further synchronization monitoring will take place until the upgrade is complete, the probe has been automatically rebooted and a startup heartbeat has been received at the TimeWatch Server.

Upgrading TimeWatch Probe Firmware

Perform the following procedures to upgrade TimeWatch Probe firmware.

RequirementsSSH Client Software

Free SSH clients can be downloaded from http://www.openssh.com/ or from http://www.chiark.greenend.org.uk/~sgtatham/putty/).

or

Terminal Emulation Software



Hyper Terminal or Teraterm which is available from http://hp.vector.co.jp/authors/VA002416/teraterm.html

FTP Server

Firmware File

The firmware file for this upgrade is timewatch_v2.4.03.tgz.sh

Probe IP information

MethodHost the firmware file on the FTP server.

Ensure that the location can be connected to by the probes. Create a specific username for the upgrade if required.

The following steps will need to be repeated for all probes.

Connect to the probe

Network: Using the SSH client software connect to the probe using the SSH protocol. You may need to specify port 22.

Local: Connect to the Probe onto the serial port using a RS-232 cable.

Once connected login with the username / password root / arcom

Prepare Probe for upgrade

At the command prompt type the following sequence of commands. Each line should be followed by a carriage return:

Initiate FTP firmware transfer

When FTP has connected you will be prompted to login; enter the username and password then type the following commands (commands are in bold, output is normal):

Note: Replace SERVER with the hostname or IP address of the FTP server.

killall handler.sh standardcd /root/rm *rm -rf /timewatch/ftp SERVER



Install the file

Run the following commands to install the firmware file:

The downloaded firmware upgrade file will automatically extract and install the required components. If required to enter a password for the configuration user, enter fr7ebi.

Configure the probe

Run this command:

To complete the configuration for the TimeWatch Probe configuration, see TimeWatch Probe Configuration, on page 41.

Once configured, select Save and Exit to quit the menu.

Reboot the probe

Note: The exact output may differ depending on your FTP server.

ftp> binary200 Type set to Iftp> get timewatch_v2.4.03.tgz.sh200 Port command successful150 Opening data channel for file transfer.226 Transfer OK993929 bytes received in 6.32 secs (1.5e+02 Kbytes/sec)ftp> quit221 Goodbye

chmod +x timewatch_v2.4.03.tgz.sh./timewatch_v2.4.03.tgz.sh

su swconf



Reboot the probe to allow the new software to become active. At the command prompt type:

Probe GSM/GPRS SIM Card Fitting/Removal

This section provides details on inserting and removing the Probe GSM/GPRS SIM Card.

To insert or replace a SIM card the probe’s top must be removed. This requires unscrewing the 4 screws on the bottom of the probe and removing the two hex screws from the Management Port RS-232 connector.

The SIM card is located in the GSM/GPRS socket modem card in the middle of the probe; this can be found by tracing the GSM antenna cable back from the casing if required. Ensure that the SIM card is inserted correctly so that contact is made.

The following should be noted for operation of TimeWatch over GSM/GPRS:

The SIM card must be registered to the network and must not require a PIN.

For GSM the SIM must be enabled to communicate over the analogue data channel; contact your service provider to enable this.

Mobile networks are inherently unpredictable and as such are out of the control of Symmetricom and the TimeWatch product. We recommend that basic network connectivity is tested prior to on-site installation, and note that operation of TimeWatch on a mobile network may be subject to limitations, signal and traffic conditions on that network.

Warning: Probe GSM/GPRS fitting requires the case to be opened by competent personnel. This must only be done with the power and PSTN lines disconnected. Care must be taken when removing the case of a TimeWatch Reference probe REV1.1 (GPS option fitted) as a cable connects from the PCB to the GPS NMEA port on the inside rear of the case. Do not remove the two hex-head jack screws from the GPS NMEA port.

NOTE: GSM/Modem communications are not supported by the standalone mode of operation – the probe will only communicate with the TimeMonitor application over Ethernet.

Reboot


Chapter 3 TimeWatch ProbeTimeWatch Probe Features and Specifications

TimeWatch Probe Features and Specifications

The following table list timeWatch Probe features and specifications.

Table 3-2. Probe Features and Specifications

TimeWatch Probe Common to Both Variants

Communication interfaces Ethernet (RJ45)

PSTN modem

GSM/GPRS modemOperating temperature range

TimeWatch Standard: 0°C to 50°C

TimeWatch Reference: 0°C to 35°C

Storage & transport temperature range

-25°C to 70°C

EN300019-1 Storage class 1.2

EN300019-2 Transport class 2.2

Power supply -48V (-40.5V to -57V)

For safety reasons voltages of magnitude larger than –60V should never be connected to the TimeWatch Probe

Power consumption TimeWatch Standard:

Typically 100mA

Maximum 190mA

TimeWatch Reference:

Typically 190mA

Maximum 250mASize 45mm x 355mm x 130mm

Mounting Rack mounting: ETSI 300mm x 600mm or 19” desktop or Velcro fixing

Colour Matt black



Connectors Reference In: BNC 75 unbalanced

Measurement In: BNC 75 unbalanced

Aux Out: BNC 75 unbalanced

Power: 4-pin terminal block

Alarm contact closure: 3-pin terminal block

Analogue modem: RJ11

GPS antenna: SMA female (optional)

GSM/GPRS antenna: SMA female (optional)

SSU interface (Rev 1.0 and below): RS-232 9-way D-Type female

GPS NMEA (Rev 1.1 and above): RS-232 9-way D-Type female

Management interface: RS-232 9-way D-Type femaleCE Marking The following EMC standards are applicable:

Domestic, commercial and light industry emissions (EN50081-1)

Industrial environment immunity (EN50082-2)

Information technology equipment safety: general requirements (EN60950-1:2002)

CE marking currently applies to all variants of TimeWatch with the exception of PSTN dialup which has not currently been fully safety tested.

LED Indicators Power LED (green)

Loss of Ref In signal LED (red)

Loss of Measure In signal LED (red)

Loss of GPS (red) (Active on TimeWatch Reference only)

PSTN ACT LED (green)

GSM/GPRS ACT LED (green)

Ethernet ACT LED (green)

Ethernet 10Mbit/s connected LED (green)

Ethernet 100Mbit/s connected LED (green)

Table 3-2. Probe Features and Specifications (Continued)




Real Time Clock The RTC on the probe is updated from the server using a received timestamp on every communication or from the attached TimeMonitor application. No averaging or delay removal is performed.

Measured Input Signal Offset Tolerance

If the maximum offset tolerance between the measured signal and the reference is 12.5 ppm.

TimeWatch Standard Network clocks measured against each other and MRTIE calculated

Measurement Input 2.048Mbit/s G.703 section 9

Tapped 2.048Mbit/s G.703 section 9 (-30dB)

2.048MHz G.703 section 13Reference Input 2.048Mbit/s G.703 section 9


2.048MHz G.703 section 13

Aux Out 2.048MHz G.703 section 13 (copy of Ref In)TimeWatch Reference Network clock measured against GPS-disciplined clock

and MTIE calculatedMeasurement Input 2.048Mbit/s G.703 section 9


2.048MHz G.703 section 13

Reference Input Unused

GPS Antenna Connector SMA femaleAux Out 2.048MHz G.703 section 13 generated from GPS-disciplined

oscillator, no holdover if GPS fails

Table 3-2. Probe Features and Specifications (Continued)



Chapter 4 TimeWatch Standalone

This chapter describes how to configure and use the TimeWatch standalone.

In This ChapterProbe ConfigurationUsing TimeWatch Standalone


Chapter 4 TimeWatch StandaloneProbe Configuration

Probe Configuration

The configuration of the TimeWatch Probe to work with the TimeMonitor Application is covered in TimeWatch Probe Configuration, on page 41.

The only 2 parameters to set are “Operate With” on the General Menu which must be set to “TimeMonitor” and the TCP/IP port number for the probe to listen on. The default setting both in the probe and in the TimeMonitor application is 50000, which should be OK most cases.

Using TimeWatch Standalone

Installation and specification requirements for the TimeMonitor application are contained within the TimeMonitor suite – see TimeMonitor’s own documentation.

Configuring and making measurements with TimeWatch standalone using the TimeMonitor application is covered in a separate document – “TimeMonitor Watch User Guide.pdf”.

Figure 4-1. TimeMonitor Application Screenshot


Chapter 5 TimeWatch Server

This chapter provides information on how to start, navigate through, manage, and configure a TimeWatch server user session.

In This ChapterWeb Browser RequirementsStarting a User SessionSelecting a NetworkNavigating the TimeWatch ServerViewing the TimeWatch NetworkViewing the Status of Your LocationsViewing the Data for a LocationManaging and Configuring LocationsConfiguring the NetworkManaging Users


Chapter 5 TimeWatch ServerWeb Browser Requirements

Web Browser Requirements

The TimeWatch Server is accessed using a Web browser. It has been tested with the following:

Mozilla Firefox 2

Microsoft Internet Explorer 6.0

It should work with, but has not been extensively tested with, the following browsers:

Mozilla Firefox 1.5+

Microsoft Internet Explorer 6+

Safari 2+

Opera 9+

Cookies

To log into the server (required for all functionality) you must enable cookies on your browser. A cookie is a text file used to store information on your PC; TimeWatch only stores a unique identifier to enable your active login information to be found on the server, and which poses no security risk to your PC or to the server.

JavaScript

Many screens of the TimeWatch Server require JavaScript to be present and enabled on your Web browser to function. These include, but are not limited to:

Location Personality

– Copy masks

– Select and save display masks

Manage Network

Location Data

Performance Statistics

While the remainder of the server software should be unaffected, we strongly recommend the use of a JavaScript-enabled platform, and this may become a requirement in the future.


Chapter 5 TimeWatch ServerStarting a User Session

Starting a User Session

To start a TimeWatch Server session, enter the server’s URL or IP address, for example http://www.timewatch.com, into your Web browser. On the initial screen enter your username and password:

Figure 5-1. TimeWatch Server Login

The username and password entry allows access according to your configured access privileges.

Selecting a Network

If you have access to more than one TimeWatch network you will be presented with the Select Network screen.

Figure 5-2. Select Network Screen

Click on the TimeWatch network you wish to work with for this session. A different network may be selected at any time if the required privileges are held.

To select a different network, click on the network name displayed between Logout and your username on the top-right of the screen.

Note: If you only have access to one TimeWatch network then this screen will not be displayed: you will be taken straight to the Location Status screen.


Chapter 5 TimeWatch ServerNavigating the TimeWatch Server

Navigating the TimeWatch Server

Once you have logged in and have an active TimeWatch network you will be presented with the main menu system at the top of the screen:

Figure 5-3. Main Menu

The entries available in the menus will depend on your user privileges, which main menu item you last selected, and whether you have an active network or not.

The top bar displays TimeWatch, the date and time that the current screen was loaded and the time zone.

Below that, two lines contain the main menu and sub-menu respectively. The two menus have the following layout; some of the described items may not be present depending on your access privileges. Each of the items is described in the remainder of this chapter.

View Network

Location Status

Manage Locations

– Location Personality

– Upgrade Firmware

– Add Location

– Move Location

– Remove Location

Manage Users

Manage Server

– Settings

– Networks

The last line contains three entries for performing the following actions:

Logout - click this to log you off the TimeWatch Server


Chapter 5 TimeWatch ServerViewing the TimeWatch Network

The name of the currently selected network is displayed, or ??? if no network is selected; click it to select a different network if you have access to more than one.

Your username is displayed; click it to view your user profile where you may change your password.

Viewing the TimeWatch Network

The View Network screen is a quick and easy way to view the alarm status of all locations across your TimeWatch network.

Figure 5-4. Example Network View

The network is viewed on a hierarchical map; you can select a location to view by clicking on its colored circle. If it is a measurement location, the Location Data screen will be displayed. Otherwise it is a map location, and the display will zoom to show the selected map sub-layer.

Each location in the hierarchy has a measurement status indicator which looks like an LED indicating the following states:

The status of a map location indicates the worst status of all locations underneath that map.

OK There are no alarm conditions for the location, or all such alarms have been cleared by the operator.

Acknowledged All alarms for this location have been acknowledged by the operator but some have not yet been cleared.

New alarm(s) This is the status given to new alarms, so signifies that there is at least one new and unacknowledged alarm for the location.


Chapter 5 TimeWatch ServerViewing the Status of Your Locations

Viewing the Status of Your Locations

The Location Status screen lists all of your measurement locations in one place with their status and alarm condition, and provides the ability to acknowledge or clear alarms (where user privileges allow) and view performance graphs.

Figure 5-5. Example Location Status

LocationThis is the user-defined name given to a location during commissioning. Click this to view the Location Data screen, described in Viewing the Data for a Location, on page 67.

Probe StatusThree icons are display in the section representing, from left to right, measurement in LOS status, reference in LOS status, and communications status. The communications status icons are as follows:

Measurement StatusThis is equivalent to the Location Status LED icon described in Viewing the TimeWatch Network, on page 63.

The Acknowledge and Clear links allow the user to change the alarm status of a location.

Healthy The probe is communicating as expected.Failure The probe has missed its last expected heartbeat.Off The probe has not yet connected to the server.

Click to acknowledge all alarm events for the location.Click to clear all alarm events for the location. Note that current loss of signal alarms cannot be cleared manually.



Figure 5-6. Alarm State Process Diagram

Stats: (Network Statistics)From the Location Status screen it is possible to perform an analysis of MTIE exception occurrences by date or time of day. For a chosen time interval the number of exceptions occurring per day or the number of exceptions occurring during each hour of the day may be graphed.

Statistics can be viewed either for the entire network or for a single location. To view the graphs, click on one of the Date or Time links at the right of the table. The performance statistics feature is described further in Performance Statistics, on page 65.

Performance Statistics

To view performance statistics for a location, click one of the Date or Time links displayed on the Location Status screen. Performance statistics can be viewed for the entire network by selecting the top link in the location table.

The period to be monitored can be chosen by setting the start and end dates. The hour of day is indicated on the horizontal axis (e.g. 0 indicates all alarms from 00:00 to 01:00), and the number of exceptions that occurred in each hour is indicated on the vertical axis.



By DateView occurrence of exceptions on a per-date basis. This can be used to highlight when problems at a particular location started, or to correlate TimeWatch exceptions with physical changes such as engineering work or other network events.

Figure 5-7. Example of Exception Analysis by Date

The period to be monitored can be chosen by setting the start and end dates. The date is indicated on the horizontal axis, and the number of exceptions for each date is indicated on the vertical axis.

By TimeView occurrence of exceptions on a per-hour basis. This can be used to highlight any events that occur regularly at a certain time of day, which may highlight problems caused by congestion on a packet network at certain peak times or by some regular maintenance activity.

Figure 5-8. Example of Exception Analysis by Time


Chapter 5 TimeWatch ServerViewing the Data for a Location

Viewing the Data for a Location

To view a location’s data select it from one of the View Network or Location Status screens and the Location Data screen will be shown.

This screen lists events which have been generated for a particular measurement location. The capability to filter events by time and type is provided in the filter section at the top left.

The tabbed control panel on the right-hand side of the screen provides the ability to view MTIE graphs, access the Location Personality screen, acknowledge and clear alarms, and request phase data.

Figure 5-9. Example Location Data

Searching and Displaying Events

The Event Search panel is used to define criteria to search for, and display events at a particular location. With the exception of the Location drop-down box, changes will not take effect until the Search is clicked.

LocationThis indicates the name of the location whose data is being viewed. To view events for a different location, select it from the drop-down box.



Show From / To This shows the start and end date (inclusive) to search for events in. Both default to today’s date. To choose a different timeframe, click on the box or the calendar icon

, choose the desired dates from the displayed calendar, then click Search.

Event Type CheckboxesEvents may be filtered by type. To prevent an event type from being displayed, clear the check box and click Search. This defaults to showing all event types.

Search ButtonClick this to update the view for any changes to the search criteria (excluding Location, which is submitted automatically).

Types of EventThere are eight types of event which can be generated by a TimeWatch Probe, represented by seven colors in the event table:

MTIE Exception (red): This occurs when the MTIE calculated by a probe exceeds the configured threshold mask. No more exception events can be generated for the 15 minutes following an exception; this is to prevent flooding.

Startup Heartbeat (green): A probe sends this event to the network when it is powered up to record the time the measurement started and to retrieve its personality.

Missed Heartbeat (grey): This event is generated by the server if a heartbeat is more than 10 minutes late. It requires heartbeat monitoring to be turned on for the server and the location.

Loss of Signal (orange): A probe generates this event if it detects a loss of signal on a used input. If the condition has since been cleared the duration is displayed. Current loss of signal conditions cannot be cleared manually.

GPS Alarm (orange): A probe generates this event if it detects the GPS Module has lost lock or if it determines that the GPS reference may be unreliable and that any exception may be as a result of this rather than the measured signal. If the condition has since been cleared the duration is displayed. Current GPS Alarm conditions cannot be cleared manually.

Large Offset (yellow): A probe generates this event if it detects a large frequency offset (12.5ppm) between Measure In and Ref In / internal GPS reference.

Note: Only applicable for TimeWatch Reference probe



Requested Phase (blue): A probe generates the requested phase events in response to a user request. Fifteen minutes after the probe receives the request (usually after the next heartbeat) thirty minutes of phase data will be sent to the server. Requests for 24 hours of phase data are also displayed in this color and a Download link is shown to indicate that the data has been received.

Heartbeat (white): Heartbeats are events sent by a probe at regular intervals as configured in the location’s personality to inform the TimeWatch server that it is still online and operational.

Event NotesFor non-heartbeat events, note data can be added to the event to detail pertinent information; for example current status, known cause or resolution of a problem. Note text is restricted to a maximum of 255 characters.

Figure 5-10. Example Event Note Display

AddingOnly users with the status management privilege will have this option available.

For a non-heartbeat event without a note, the add note icon will be shown. Click on this then write the desired note text in the textbox. When finished, click the save icon to save the text and hide the display. To cancel without adding the note, click on the add note icon once more.

Viewing

For a non-heartbeat event which has a note, the view note icon will be shown. Click on this to display the note text. To hide the event note display, click it once more.

EditingOnly users with the status management privilege will have this option available.

To edit an existing note, view the note as described above, then click the edit icon . The text will be made editable and the save icon will appear. To cancel

without editing the note, click on the view note icon once more.

RemovingOnly users with the status management privilege will have this option available.



To remove an event note, view the note as described above, then click the remove icon . You will be asked to confirm the operation before it is performed. This can also be performed when editing the note.

Requesting Phase DataPhase data is always uploaded with an MTIE exception however you may wish to obtain phase data during periods where no exceptions are created, or at a higher sampling resolution than is usually available (1 sample per second rather than 1 sample per 10 seconds).

This may be achieved with the Request Phase tab of the control panel on the right-hand side of the Location Data screen.

Figure 5-11. Request Phase Tab

Request Half-Hour Phase SnapshotThis link makes a request for the latest 30 minutes of raw phase data to be uploaded. 15 minutes after the request being received by the probe (usually at next heartbeat), 30 minutes of phase data will be made available. The phase data is at a reduced resolution compared to that used to calculate MTIE data: 1 sample every 10 seconds, without averaging.

Request Single 24-Hour Phase UploadThis link makes a request for the last 24 hours of phase data to be uploaded. After the next heartbeat the probe will upload the last 24 hours of raw phase data at maximum resolution (1 sample per second).

The data is in GZip format and must be decompressed using a program like WinZip before it can be viewed. Symmetricom’s TimeMonitor software can be used to view and analyze the decompressed files.

Request Daily 24-Hour Phase UploadsThis link effects a 24-hour phase upload similar to the previous link, but the request will be automatically repeated every day for the specified duration. Available durations are 1 week, 2 weeks, 3 weeks and 4 weeks. The request may be cancelled or extended at any time.

A request for 24-hour phase will only be made to the probe in response to a heartbeat (note that this differs from version 2.3 and earlier).



When you make a multiple 24-hour phase request, the request will be sent to the probe every day on the first heartbeat after the current time. If, after making the request, the heartbeat start time or interval is changed, then the time of upload can change accordingly.

Viewing and Printing Graphs

MTIE GraphsTo view an MTIE graph for a particular event, check the MTIE boxes for the heartbeats, exceptions or phase requests whose data should be included. The MTIE graph is displayed on the right hand side of the screen (you may need to click the MTIE Graph tab to see it).

The MTIE of the selected events will be shown with the location’s MTIE threshold mask, standard masks, and an additional custom mask set if the location is configured for this.

Figure 5-12. Example MTIE Graph

Phase GraphsFor an MTIE exception or non 24-hour phase request, a View Phase link is provided for the event in the Information column of the event table. Clicking on the link will display a graph of the 30 minutes’ phase data centred on the time of the event. Hovering over the link will provide a popup thumbnail of the graph.

Note: The MTIE measurement is a continuous measurement from all phase data gathered since the last exception/phase request, or since start-up if no exception/phase request has been generated yet.


Chapter 5 TimeWatch ServerManaging and Configuring Locations

This type of graph is available 15 minutes after the exception occurs or the phase request is received by the probe. Until that point, the column will show Awaiting. If 20 minutes has passed since the event and the phase data has not been received from the probe, the column will show Unavailable. This can occur, for example, if the probe goes offline before the 15 minute window has ended; the phase data may still be uploaded even after this period, for example if a temporary loss of communications prevented the upload.

Figure 5-13. Example Phase Graph

Managing and Configuring Locations

A TimeWatch network is comprised of a set of measurement locations – each is a logical entity set up to receive data from a single TimeWatch Probe. For convenience measurement locations can be arranged in a multi-level map hierarchy allowing both high-level overviews and zoomed in detailed views to be presented to obtain the necessary separation between locations. Each level of this map is called a map location.

Before installing a probe to monitor a location in your synchronization network you will need to create a measurement location on your TimeWatch network for it. The probe can then be assigned to the measurement location, and all events and data generated by it are associated with that location – this means that if you move the probe elsewhere, your data will always be stored against the measurement location from which it was generated.

Adding a Location

Only users with the location management privilege will have this option available.

To add a location select the Manage Locations menu then Add Location from the submenu. You will then be presented with the top-level map (if it exists) of your TimeWatch network, with current locations and child map locations displayed in the usual way. If there is no top-level map yet you will be prompted to create one.



Click the area of the map which corresponds to the position of the new map/measurement location. Alternatively you may click on an existing map location to open it and place the new location there. You cannot click on existing measurement locations or place new locations on top of them.

When you have chosen the position of the new location you will be presented with the following screen:

Figure 5-14. Add Location II

Fill in the details as described then submit the form by clicking Add.

NameThis is the name of the location and will be used to refer to it after creation.

As it is the primary means of identifying a location, it must be distinct from the current network’s existing location names. Note that the name of a location cannot be changed after creation.

TypeThis must be set to the type of location you wish to create. For a map location to be created select Map. For a measurement location that can have a probe assigned to it for synchronization monitoring select Measurement.

Map ImageOnly required if type is Map, this is the image that the child map location will display; it must be either a JPEG, PNG or GIF type image. Other types, including bitmaps, are not supported and must be converted with external software before use.

Once the location has been added, if the new location is a map location then the new sub-level will be displayed. If it is a measurement location then the originally displayed map will be shown. Note that you may need to use the refresh function of your browser to see the new location on the map.

Note: The colors of the location marker LEDs may appear differently when the network map image is a GIF type due to the storage mechanism of the GIF image type. If this is undesirable then a GIF should be converted to a JPEG or PNG before upload.



Configuring a Location

Only users with the location management privilege will have this option available.

To configure an existing measurement location, select the Manage Locations menu then Location Personality from the submenu, or alternatively select the Location Personality link from the Location Data page.

The personality of a location can be defined as its individual configuration including heartbeat interval settings, SMS/email alert settings, description, input signal types, MTIE threshold and display masks. The sections of the screen and their meanings are detailed below.

Dial Up Configuration

Figure 5-15. Location Personality (Dialup Configuration)

Click the Dialup Configuration link to modify the dialup configuration of the location if it is using a dialup (GSM or PSTN) connection. Note that the current settings are not displayed.

Location and Hardware

Figure 5-16. Location Personality (Location & Hardware)

Note: If incorrect values are entered future communications to the probe could be lost requiring a site visit for reconfiguration.



LocationThe Location field is a drop-down box containing all of the measurement locations on the current network. To select the location to configure, choose its name from this list; the screen will automatically reload that location’s personality.

Probe Serial NumberThe serial number of the TimeWatch Probe is used to assign to this location. A probe may only be allocated to a single location at a time. To unlink the probe from the location, simply clear this box.

Probe Licence KeyThe hardware licence key for the probe is used to assign to the location. The licence key is unique to the probe serial number and is required to assign a probe.

Measurement / Reference SignalThese drop-down boxes are used to select the type of signal applied to the Measure / Ref In interfaces. They can be 2.048 MHz, 2 Mb/s or 2 Mb/s via 30 dB tap (i.e. 30 dB down from G.703 level).

DescriptionAny desired information associated with the location may be entered here and changed at any time. This is a useful place to detail the equipment connected to the external interfaces.

Alarm Notifications

Figure 5-17. Location Personality (Alarm Notification Alerts)

Here you can choose what type of alerting mechanism(s) will be used when an alarm event is generated. The alarm events are:

MTIE exception

Large offset exception

Loss of signal

Missed heartbeat

Send Email AlertCheck to send an email to the specified destination(s) when an alarm event is generated by the probe or server. Multiple addresses must be separated by commas.



Send SMS AlertCheck to send an SMS to the specified destination(s) when an alarm event is generated by the probe or server. Multiple numbers must be separated by commas.

Phone numbers must be formatted similar to the international call format, in the following format:

(country code)(network prefix)(number)

There must be no leading zeros or plus sign (+), and there must be no spaces in the number.

For example, the UK number (+44) 0848 9123 456 must be entered as 448489123456

Heartbeat ConfigurationThe heartbeat configuration specifies the interval at which heartbeats are to be generated by the probe, and also an absolute time from which the intervals should be offset.

Figure 5-18. Location Personality (Heartbeat Configuration)

Probes communicate to the server when there has been an exception or fault, and at a regular interval dictated by the heartbeat interval. The heartbeat enables any communications problems or probe failure to be detected quickly, and also provides regular MTIE data for viewing.

Start TimeThis is the time the heartbeat cycle starts. It is recommended that probes are given staggered start times to prevent all locations from generating heartbeats simultaneously. The start time is based on server time without the application of a network’s UTC offset.

IntervalThe interval between heartbeats; it may be 5 minutes, 15 minutes, 30 minutes, 1 hour, 6 hours, 12 hours or 24 hours.

MTIE Exception ThresholdThe MTIE exception threshold (or mask) is the limit above which a probe will generate an MTIE exception if the measured MTIE exceeds any point of the mask. Lower thresholds will usually result in more regular exceptions.



The mask values may be entered manually or by using a drop-down box to copy the values from other sources. The network specific masks (described in MTIE Masks, on page 80) are listed first, followed by industry standard masks interpolated for the observation periods used. Manually editing the values after copying from elsewhere will not modify the original source of the values.

Mask ValidityValid MTIE masks must always increase numerically for increasing observation intervals; the mask input fields make sure that the mask you enter is valid by cascading through all following/preceding fields if a value you enter renders the mask invalid.

For example, if you enter a value higher than the one following it, the following values will be increased to that value if lower than it; if you enter a value lower than the previous one, previous values will be decreased to that value if greater than it. Non-numeric characters will be rejected.

Figure 5-19. Location Personality [MTIE Masks]

MTIE Display MasksA set of masks may be chosen for display on all of this location’s MTIE graphs. Display masks may be selected from:

MTIE exception threshold mask

Network masks (see MTIE Masks, on page 80)

Industry standard masks



Figure 5-20. Location Personality [MTIE Display Masks]

The left box displays the available masks that are not currently selected; the right box displays those that are selected for display.

To move a mask from one box to the other you can either select it with the mouse and click the move left or move right icon, or you can double-click it. Multiple masks can be moved together by selecting several and using the icons as described; you cannot use double-click to move multiple masks.

Saving / Cancelling Modifications

Moving Locations

If you wish to modify the way the maps are laid out, for example by adding an additional map layer for closely-located locations, or to relocate a location that has been incorrectly positioned on a map, select the Manage Locations menu then Move Location from the submenu.

First select the location you wish to move:

Saves any information that has been changed on this screen to the server. Note that the location personality will not be updated until the probe next connects to the server.If changes have been made on the screen and Save Modifications has not been clicked, this will revert the changes.



Figure 5-21. Move Location

This will take you to the location’s parent map; navigate to the map you wish to position the location on, if different from the current, then click the position you would like the location to be moved to. Child maps are opened by clicking on the icon representing the map, parent maps are opened by clicking on Back Up above the map image. If the curser is hovered over an icon that location’s name will be displayed.

When the appropriate position is selected the map will be redrawn showing the updated position of the location. Note that you may have to refresh the page in your browser for the changes to be displayed.

Removing Locations

Removal of locations is not a necessary part of network management and should only be performed if it is certain that the location and its historic data is no longer required. To move a probe from one location to another it is sufficient to remove the probe’s serial number from the old location and add it to the new one. This has the benefit of maintaining historic data for old locations.

To remove a location select the Manage Locations menu then Remove Location from the submenu. The top-level map will be shown; navigate to and click on the location to be removed, and you will be asked to confirm the action:

Figure 5-22. Remove Location II


Chapter 5 TimeWatch ServerConfiguring the Network

Click Remove to confirm the removal, or navigate away from the screen to cancel.

Configuring the Network

To manage a network’s global configuration (the settings that apply to the network as a whole rather than individual locations), select the Manage Network menu. Only those with the manage network privilege will be able to view and modify this information.

General

Figure 5-23. Manage Network [General]

UTC OffsetIf local time is required to be used to display events an offset from UTC can be chosen. The required offset is selected from a drop-down list. Currently logged-in users must re-login for the changes to be displayed.

MTIE Masks

Figure 5-24. Manage Network [MTIE Masks]

Note: To remove a map location, you must first remove all child locations or move them elsewhere in the location hierarchy. When you have removed the last child location of a map you will automatically be prompted to remove the map location.

Note: The TimeWatch Server can utilize NTP to synchronize its clock to an internet or other time source, this is a function external to the TimeWatch server.


Chapter 5 TimeWatch ServerConfiguring the Network

A network manager can add custom MTIE masks to his network; these are then made available for use as MTIE exception threshold masks and displaying on MTIE graphs (see MTIE Exception Threshold, on page 76 for more details).

To add a new mask, type a name between 1 and 64 characters in the left-hand box, enter the mask values for the given observation periods, and then click the add icon

. Note that mask names must be unique within a network, and that numbers are validated before a mask is added; you will be asked to correct any problems.

To remove an existing mask, click the remove icon at the end of the corresponding row; you will be asked to confirm the action.

It is not possible to edit a mask – this can be achieved by adding a new mask and removing the old mask.

Phase FTP

When 24-hour phase data is requested, the phase data is uploaded from the probe to an FTP server. The FTP server to be used and its parameters are configured on a network-wide basis and sent to each probe when a request for 24-hour phase data upload is made.

Figure 5-25. Manage Network [Phase FTP]

Hostname / IP address: The domain name or IP address of the FTP server. If a hostname is specified the probe must be using DHCP over Ethernet or have a DNS server configured (explicitly for Ethernet or implicitly for dialup).

Login Username: The login username for the FTP server.

Login Password: The login password for the FTP server.

Note: This section relates only to probe firmware versions before 2.2.


Chapter 5 TimeWatch ServerManaging Users

Pathname: The folder to store data in on the FTP server. This must use forward-slashes ‘/’ instead of back-slashes ‘\’ to denote directories. A leading and trailing / are added if not present. The folder must exist on the server for the transfer to succeed.

Managing Users

To add user to or remove user from a network, or modify an existing user, select the Manage Users menu.

Figure 5-26. Manage Users

The screens for adding new users and modifying existing users are similar. To add a user, enter the new username in the box at the bottom of the list of existing users and click Add. To modify or remove an existing user, click on the appropriate link to the right of their username.

Username (Add User only)The user’s unique name. This is what they will use to login with; it must be unique to the server (a message will be displayed if the username is unavailable), and must be between 1 and 32 characters long.



PasswordThe user’s password: this may be used to set an existing user’s password if it has been forgotten. The password must be a minimum of 6 characters, include both numbers and letters, and not contain the username. Additionally, a user may not use a password they have used previously. To prevent mistakes, the password must be entered twice. When modifying an existing user, if the password does not need to be modified then leave these fields blank.

Force password to be changedThe administrator setting a user’s password can force the user to change their password the next time they log in.

PrivilegesThe remaining checkboxes correlate to server-based tasks. By checking or unchecking a box you can grant or deny the privilege to perform the corresponding action to the user. The available privileges are:

Once the user has been configured as required click Update (for an existing user) or Create (for a new user).

Table 5-1. User Privileges

Privilege Enabled Features

Basic network access & viewing

View and navigate the network using the View Network screen

View each location’s status and data, including phase and MTIE data

Request phase dataStatus management Acknowledge and clear alarms for locations and events

Add, edit and remove event notes

Location management Modify a location’s personality, e.g. MTIE masks

Add, move and remove map and measurement locations

Upgrade firmware Flag probes for firmware upgrade

User management Add, modify and remove usersNetwork management Change the UTC offset for display of local time

Configure the FTP server for 24-hour phase capture requests


Chapter 6 Interpreting TimeWatch Results

This chapter provides two examples of actual measured results along with an explanation of each one.

In This ChapterFrequency OffsetPhase StepsGPS Alarm Exception


Chapter 6 Interpreting TimeWatch ResultsFrequency Offset

Frequency Offset

Frequency offsets are easily detected by TimeWatch and will result in a straight line on both the MTIE and phase data graphs. The actual frequency offset can be calculated from either graph.

For example with a phase variation of 160ns over 30 minutes we can calculate the frequency offset:

The offset is 8 parts in 10-11.

This is a good clock but it would not give PRC accuracy if it remained at this offset for an extended period.

Figure 6-1. Mtie Showing Frequency Offset

Note: The offset in this example was only measured for 9000s hence the flattening of the MTIE after this time.

119

108603010160 −

−

×=××

==timephaseoffset

Region of MTIE graph caused by frequency offset


Chapter 6 Interpreting TimeWatch ResultsPhase Steps

Figure 6-2. Phase Graph for Frequency Offset

Phase Steps

In this example we have a phase jump of approximately 500ns occurring over 300s. This phase step implies instability in the synchronization distribution network.

Figure 6-3. Mtie for Phase Step


Chapter 6 Interpreting TimeWatch ResultsGPS Alarm Exception

Figure 6-4. Phase Graph for Phase Step

GPS Alarm Exception

In this example we have an exception caused by a GPS alarm, the exception has been caused by a loss of GPS reference, not the signal being measured.

Figure 6-5. Exception Caused by Loss of GPS Reference

Many more synchronization problems are detectable with TimeWatch. With the TimeWatch managed service, Symmetricom experts are on-hand to advise on synchronization problems and solutions.


098-00251-000_rev_a TIME WATCH

Documents

Transcript of 098-00251-000_rev_a TIME WATCH