TimeProvider 2700

..................
TimeProvider 2700 Edge Grandmaster Clock
.................. TimeProvider 2300 Edge Boundary Clock
...................

....................User’s Guide
....................Revision B ‐ Draft 6 ‐ June, 2014
....................Part Number: 098‐00564‐000
User’s Guide updates are available at: www.microsemi.com/ftdsupport

© 2014 Microsemi All rights reserved. Printed in U.S.A.
All product names, service marks, trademarks, and registered trademarks used in this document are the property of their respective owners.
Contents
Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Structure of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Conventions Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Warnings, Cautions, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . .21
Where to Find Answers to Product and Document Questions . . . . . . . . . . . . .22
What’s New In This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Related Documents and Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Chapter 1 Overview
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
TimeProvider 2300/2700 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Software Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Communications Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Input Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Output Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Power and Ground Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Communication Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Time Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Frequency Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Synchronization and Timing Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Chapter 2 Installing
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Security Considerations for TP 2300/2700 Installation . . . . . . . . . . . . . . .42
Site Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Installation Tools and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 3

Table of Contents
Unpacking the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Rack Mounting the TimeProvider 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . .45
Making Ground and Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Ground Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
DC Power Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
AC Power Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Signal Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Communications Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
TP 2300/2700 Synchronization and Timing Connections . . . . . . . . . . . . .54
Connecting the GNSS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Installation Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Applying Power to the TimeProvider 2300/2700. . . . . . . . . . . . . . . . . . . . . . . .60
Normal Power Up Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Chapter 3 CLI Commands

CLI Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
TimeProvider 2300/2700 CLI Command Conventions . . . . . . . . . . . . . . .64
CLI Command Keyboard Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Command Line Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Command User Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
TimeProvider 2300/2700 CLI Command Set . . . . . . . . . . . . . . . . . . . . . . . . . .66
show alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
show alarm-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
set alarm-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
show bridge-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
set bridge-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
show clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
set clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
set configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
show eia-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
show ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
set ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
show firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
set firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
show gnss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
set gnss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
show hardware-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
show hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
4 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014
Table of Contents
set hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

show image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
set image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
show input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
set input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
show inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
set inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
show ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
set ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
show led . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
show license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
set license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
show log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
set log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
show log-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
set log-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
show output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
set output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
show output-gen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
set output-gen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
show port-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
set port-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
show pql-ssm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
show ptp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
set ptp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
reboot system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
show ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
set ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
show-session-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
set-session-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
show snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
set snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
show ssm-option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
set ssm-option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
show status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
show synce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
set synce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Table of Contents
test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
show user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
set user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
show vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
set vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Chapter 4 Provisioning
Establishing a Connection to the TimeProvider 2300/2700 . . . . . . . . . . . . . .206
Communicating Through the Serial Port. . . . . . . . . . . . . . . . . . . . . . . . .206
Communicating Through the Ethernet Port . . . . . . . . . . . . . . . . . . . . . .206
Managing the User Access List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
Adding a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Deleting A User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Displaying Current Users and User Access Levels . . . . . . . . . . . . . . . .211
Changing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Changing a User’s Access Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Provisioning the Ethernet Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Provisioning MGMT Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Provisioning the Service Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . .214
Provisioning VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
VLAN on the ETH2 Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
VLANs on the ETH1 Client Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Provisioning the Input Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Reference Switching Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Reference Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Provisioning Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
Setting PTP Input Client Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .225
Setting GNSS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
Setting E1/T1 Input Reference Parameters . . . . . . . . . . . . . . . . . . . . . .233
Provisioning SyncE Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Provisioning the PTP Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
PTP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
PTP Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

Table of Contents
Provisioning the Non-PTP Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Quality Levels for Output Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
Provisioning the T1/E1 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246
Provisioning TOD+1PPS Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
Provisioning the 10MHz & 1PPS Output. . . . . . . . . . . . . . . . . . . . . . . . .248
Provisioning SyncE Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
Provisioning Output Generation Behavior. . . . . . . . . . . . . . . . . . . . . . . .250
Setting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Provisioning Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Disabling Specific Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
Showing Current Alarm Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
Showing Current Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Displaying Alarm and Unit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Saving and Restoring Provisioning Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
Backing up Provisioning Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
Restoring Provisioning Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
Provisioning for SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
Adding or Deleting a Manager IP Address . . . . . . . . . . . . . . . . . . . . . . .256
Provisioning to Generate v2 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Provisioning to Generate v3 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Adding and Removing v2 Communities . . . . . . . . . . . . . . . . . . . . . . . . .257
Adding and Removing SNMP v3 Users . . . . . . . . . . . . . . . . . . . . . . . . .258
Adding and Removing SNMP v3 Trap Users . . . . . . . . . . . . . . . . . . . . .259
Testing TP 2300/2700 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
LED Indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Verifying the Port IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Verifying the Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
Verifying GNSS (TP 2700 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Verifying PTP Master/Server Functionality . . . . . . . . . . . . . . . . . . . . . . .266
Verifying PTP Input Client Functionality . . . . . . . . . . . . . . . . . . . . . . . . .267
Verifying SyncE Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
Verifying T1/E1 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Verifying TOD Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272
Verifying 10 MHz/ 1PPS Functionality . . . . . . . . . . . . . . . . . . . . . . . . . .272
Chapter 5 Maintenance, Troubleshooting & Part Numbers

Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
ESD Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276

Table of Contents
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Diagnosing the TP 2300/2700 By Symptom . . . . . . . . . . . . . . . . . . . . . .277
Diagnosing the TP 2300/2700- Reading LED Conditions. . . . . . . . . . . .282
Repairing the TimeProvider 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Upgrading the Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
TP 2300/2700 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
TimeProvider 2300/2700 Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
System and Accessory Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . .291
GNSS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Returning the TimeProvider 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Repacking the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Equipment Return Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295
User’s Guide Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295
Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296
Appendix A System Messages

Message Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
Facility codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
Severity codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
System Notification Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299
Appendix B Specifications and Factory Defaults

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
Compliance & Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
MGMT Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
Input Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
Output Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324
Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
GNSS Antenna Kits Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
GNSS Antennas with Internal LNA Specifications . . . . . . . . . . . . . . . . .333
GNSS Lightning Arrestor Specifications . . . . . . . . . . . . . . . . . . . . . . . . .335
GNSS Antenna Coaxial Cable Specifications. . . . . . . . . . . . . . . . . . . . .336

Table of Contents
Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337

TP 2300/2700 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337
Alarm Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
Appendix C Installing GNSS Antennas

Antenna Kits Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350
Considerations for Antenna Installation . . . . . . . . . . . . . . . . . . . . . . . . .350
Antenna Kits Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351
Lightning Arrestor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351
GNSS L1 In-line Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351
Antenna Coaxial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351
GNSS Antenna Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Planning the Antenna Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Antenna Installation Tools and Materials . . . . . . . . . . . . . . . . . . . . . . . .354
Cutting Antenna Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355
Installing the Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355
Connecting the Cable to the Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . .357
Installing the Lightning Arrestor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357
Connecting the GNSS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358
Antenna Installation Completeness Checklist. . . . . . . . . . . . . . . . . . . . .358
Available GNSS Antenna Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359
Antenna Coaxial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360
Appendix D PQL Mapping

Purpose of Input and Output Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . .362
Quality Levels Defined by ITU-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362
PQL Input Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
PQL Output Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366
Appendix E Software Licenses

Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370
Appendix F Asymmetry Feature

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374
Asymmetry Correction Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374
Typical Application of Asymmetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379

Table of Contents
Asymmetry Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380
Appendix G Glossary

Figures
1-1 TimeProvider 2700 DC Version Connectors and LEDs . . . . . . . . . . . . . . . .29
1-2 TimeProvider 2700 AC Version Connectors and LEDs . . . . . . . . . . . . . . . .29
1-3 TimeProvider 2300 DC Version Connectors and LEDs . . . . . . . . . . . . . . . .29
1-4 TimeProvider 2300 AC Version Connectors and LEDs . . . . . . . . . . . . . . . .30
1-5 Serial Port Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
1-6 GNSS Input Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
1-7 PTP Input Connections - R1 & S1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
1-8 T1/E1 Input Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
1-9 PTP Output Connections - R2 & S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
1-10 T1/E1 & TOD Output Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
1-11 10 MHz/1PPS Output Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
1-12 TimeProvider 2300/2700 DC Version Power and Ground . . . . . . . . . . . . . .34
1-13 TimeProvider 2300/2700 AC Version Power and Ground . . . . . . . . . . . . . .34
1-14 Functional Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
1-15 LEDs for TP2700 - DC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1-16 LEDs for TP2700 - AC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1-17 LEDs for TP2300 - DC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1-18 LEDs for TP2300 - AC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1-19 Web Interface - Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
1-20 Web Interface - Clients List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
1-21 Web Interface - Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
2-1 TP 2300/2700 - Location of Product Label . . . . . . . . . . . . . . . . . . . . . . . . .45
2-2 Dimensions for TimeProvider 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . .46
2-3 Mounting Hole Placements for TP 2300/2700 . . . . . . . . . . . . . . . . . . . . . .46
2-4 Rack Mounting the TP 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
2-5 TimeProvider 2700 Power & Ground Connections - DC Version . . . . . . . .48
2-6 TimeProvider 2700 Power & Ground Connections - AC Version. . . . . . . . .48
2-7 TimeProvider 2300 Power & Ground Connections - DC Version . . . . . . . .48
2-8 TimeProvider 2300 Power & Ground Connections - AC Version. . . . . . . . .48
2-9 Universal Ground Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
2-10 Installing DC Power Connector Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
2-11 DC Power Connector Cover - Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
2-12 Power and Ground Connections on DC Version of TP 2300/2700 . . . . . . .51
2-13 TimeProvider 2300/2700 AC Power Connector. . . . . . . . . . . . . . . . . . . . . .52
2-14 Serial Port Male Mating Connector Pins . . . . . . . . . . . . . . . . . . . . . . . . . . .54
2-15 PTP Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
2-16 Optical SFP Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
2-17 T1 / E1 and TOD Outputs RJ-45 Connection . . . . . . . . . . . . . . . . . . . . . . .57
2-18 10MHz/1PPS Output Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
2-19 GNSS Input Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
3-1 Clock States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
4-1 Set IP Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
4-2 Set Ethernet Command Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

List of Figures
4-3 Set Vlan-Mode Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

4-4 Fixed VLAN for Server Port— set vlan Commands. . . . . . . . . . . . . . . . . .218
4-5 Non-Fixed VLAN for Server Port — set vlan Commands . . . . . . . . . . . . .219
4-6 Fixed VLAN for Client Port— Set Vlan Commands . . . . . . . . . . . . . . . . . .221
4-7 Set Ref Command Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
4-8 Set PTP Client Command Hierarchy (partial) . . . . . . . . . . . . . . . . . . . . . .227
4-9 Set PTP Client Config Command Hierarchy (partial). . . . . . . . . . . . . . . . .228
4-10 Set PTP Client Config Command Hierarchy (cont’d). . . . . . . . . . . . . . . . .229
4-11 Set GNSS Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231
4-12 Set Port-Control Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
4-13 Set Input Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
4-14 Set SyncE Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
4-15 Set PTP Master Command Hierarchy - Active Profile . . . . . . . . . . . . . . . .237
4-16 Set PTP Master Command Hierarchy - Shared Parameters . . . . . . . . . . .238
4-17 Two-Step Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
4-18 One-Step Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
4-19 Set PTP Master Command Hierarchy - Default Profile . . . . . . . . . . . . . . .241
4-20 Set PTP Master Command Hierarchy - Ethernet Default Profile . . . . . . . .242
4-21 Set PTP Master Command Hierarchy - Unicast Profiles . . . . . . . . . . . . . .243
4-22 Set Output Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246
4-23 Set SyncE Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
4-24 Output Generation Behavior Commands. . . . . . . . . . . . . . . . . . . . . . . . . .250
4-25 Set Alarm-Config Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
4-26 Set Configuration Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . .254
4-27 Set SNMP Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
B-1 Timing Relationship Between 1PPS and TOD for 1 PPS+TOD Outputs . .326
B-2 TOD China Mobile Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
B-3 TOD Cisco Message Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . .330
C-1 Locating the GNSS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
C-2 GNSS Antenna Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356
D-1 PQL Input and Output Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362
F-1 Calibrated Path Algorithm for Asymmetry Feature . . . . . . . . . . . . . . . . . .376

Tables
2-1 System Management Ethernet Connector Pin Assignments . . . . . . . . . . . .53
2-2 Serial Port Connector Pin Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . .54
2-3 Recommended and Supported SFP Transceivers . . . . . . . . . . . . . . . . . . .56
2-4 T1/E1 Output Port Pin-Outs - RJ-48C Connector . . . . . . . . . . . . . . . . . . . .57
2-5 1PPS+TOD Port Pin-Outs - RJ45 Connector . . . . . . . . . . . . . . . . . . . . . . .58
2-6 Default Parameters for TOD Information Transmission . . . . . . . . . . . . . . . .59
2-7 Installation Completeness Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
2-8 LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
3-1 Ethernet Status - Hex Error Code Descriptions . . . . . . . . . . . . . . . . . . . . . .79
3-2 Show Input Status - Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
3-3 IP Status Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
3-4 PTP Client Status Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
3-5 PTP Client Asymmetry Information Descriptions . . . . . . . . . . . . . . . . . . . .140
3-6 PTP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
3-7 PTP Master - Default and Ethernet Default Profile (Multicast)
Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
3-8 Interval Values and PTP Message Rates . . . . . . . . . . . . . . . . . . . . . . . . .156
3-9 PTP Master - Telecom-2008 & ITU-G8265-1 Profiles (Unicast)
Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
3-10 PTP Client - Parameter Descriptions for Telecom-2008 Profile . . . . . . . . .159
3-11 System Status Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
3-12 Clock Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
3-13 Show SyncE Status Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . .188
4-1 User Level and Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
4-2 Default Priorities and PQL Values for Time and Frequency References . .224
4-3 PTP Profiles for the TP 2300/2700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
5-1 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
5-2 Troubleshooting Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
5-3 LED Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
5-4 TP 2300 Component Part Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
5-5 TP 2700 Component Part Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
5-6 Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
5-7 GNSS Antenna Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
A-1 System Notification Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299
A-2 Secondary Index Descriptions for System Notification Messages. . . . . . .312
B-1 TimeProvider 2300/2700 Mechanical Specifications . . . . . . . . . . . . . . . . .316
B-2 TimeProvider 2300/2700 Environmental Specifications. . . . . . . . . . . . . . .316
B-3 TimeProvider 2300/2700 Compliance Specifications. . . . . . . . . . . . . . . . .318
B-4 TimeProvider 2300/2700 Serial Port Specifications. . . . . . . . . . . . . . . . . .320
B-5 TimeProvider 2300/2700 LAN Port Specifications . . . . . . . . . . . . . . . . . . .320
B-6 TimeProvider 2700 GNSS Input Signal Specifications . . . . . . . . . . . . . . .320
List of Tables
B-7 TimeProvider 2300/2700 DS1 Input Signal Specifications. . . . . . . . . . . . .322

B-8 TimeProvider 2300/2700 E1 Input Signal Specifications . . . . . . . . . . . . . .322
B-9 TimeProvider 2300/2700 PTP Input Signal Specifications. . . . . . . . . . . . .322
B-10 TimeProvider 2300/2700 SyncE Input Signal Specifications . . . . . . . . . . .323
B-11 TimeProvider 2300/2700 PTP Output Signal Specifications . . . . . . . . . . .324
B-12 TimeProvider 2300/2700 SyncE Output Signal Specifications . . . . . . . . .324
B-13 TimeProvider 2300/2700 DS1 Output Signal Specifications . . . . . . . . . . .325
B-14 TimeProvider 2300/2700 E1 Output Signal Specifications . . . . . . . . . . . .325
B-15 TimeProvider 2300/2700 1PPS+TOD Output Signal Specifications . . . . .325
B-16 TOD China Mobile Frame Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
B-17 TOD China Mobile Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328
B-18 TOD China Mobile Time Information Message Payload Contents. . . . . . .328
B-19 TOD China Mobile Time Status Message Payload Contents. . . . . . . . . . .329
B-20 TOD Cisco Message Frame Structure Details . . . . . . . . . . . . . . . . . . . . . .330
B-21 TimeProvider 2300/2700 10 MHz Output Signal Specifications . . . . . . . .332
B-22 TimeProvider 2300/2700 1PPS Output Signal Specifications . . . . . . . . . .332
B-23 Holdover Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
B-24 GNSS Antennas with Internal Low-Noise Amplifier Specifications . . . . . .333
B-25 GNSS Antenna Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
B-26 Lightning Arrestor Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335
B-27 GNSS L1 Inline Amplifier Specifications . . . . . . . . . . . . . . . . . . . . . . . . . .335
B-28 Antenna Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336
B-29 General and Communication Parameters . . . . . . . . . . . . . . . . . . . . . . . . .337
B-30 GNSS Input Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
B-31 PTP Client ETH1 Port IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
B-32 PTP Client ETH1 Input Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .340
B-33 SyncE Input ETH1 Port IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .341
B-34 T1/E1 Input Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341
B-35 PTP Grand Master ETH2 Port IP Parameters . . . . . . . . . . . . . . . . . . . . . .342
B-36 PTP Grand Master ETH2 Port VLAN Parameters - Fixed Index (1-16). . .342
B-37 PTP Grand Master ETH2 Port VLAN Parameters - Non-Fixed . . . . . . . . .343
B-38 PTP Grand Master ETH2 Port Active Profile . . . . . . . . . . . . . . . . . . . . . . .343
B-39 PTP Grand Master Telecom-2008 Profile Unicast Parameters . . . . . . . . .343
B-40 PTP Grand Master ITU-T G.8265.1 Profile Unicast Parameters . . . . . . . .344
B-41 PTP Grand Master Default Profile Multicast (Layer 3) Parameters . . . . . .345
B-42 PTP Grand Master Ethernet Default Profile Multicast (Layer 2)
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346
B-43 T1/E1 Output Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347
B-44 T1/E1 Input / Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
B-45 10MHz/1PPS Output Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .348
B-46 SSM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
B-47 GNSS Port Alarm Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
C-1 GNSS Antenna Kits for TimeProvider 2700 . . . . . . . . . . . . . . . . . . . . . . . .359

List of Tables
C-2 LMR-400 Antenna Coaxial Cable Accessories . . . . . . . . . . . . . . . . . . . . .360

C-3 LMR-400/LMR-400FR Antenna Coaxial Cable Specifications. . . . . . . . . .360
D-1 G.781 QL and SSM values for Option I Network (2048 kbps hierarchy) . .362
D-2 G.781 QL and SSM values for Option II Network (1544 kbps hierarchy). .363
D-3 PQL Input Mapping for Option I Network - Converted from SSM or
PTP clockClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
D-4 PQL Mapping for Option II Networks - Converted from SSM or
PTP clockClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
D-5 Time and Frequency References - Default Priorities and PQL Values . . .365
D-6 PQL Output Mapping for Option I Network - Converted to SSM or
PTP clockClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366
D-7 PQL Output Mapping for Option II Network - Converted to SSM or
PTP clockClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
D-8 PQL Values for Clock States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
F-1 Description of Calibrated Path Algorithm for Asymmetry Feature . . . . . . .377
F-2 PTP Input Asymmetry Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381
G-1 Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383

List of Tables

How to Use This Guide
This section describes the format, layout, and purpose of this guide.
In This Preface
 Purpose of This Guide
 Who Should Read This Guide
 Structure of This Guide
 Conventions Used in This Guide
 Warnings, Cautions, Recommendations, and Notes
 Related Documents and Information
 Where to Find Answers to Product and Document Questions

Purpose of This Guide
Purpose of This Guide
The TimeProvider 2300/2700 User’s Guide describes the procedures for unpacking,
installing, using, maintaining, and troubleshooting the Microsemi TimeProvider 2700
Precision Timing Protocol Grand Master and TimeProvider 2300 Carrier-Class
Boundary Clock. It also includes appendixes that describe alarms and events, the
languages that you use to communicate with the TimeProvider 2300/2700, default
values, and other information.
Who Should Read This Guide
Chapter 1, Overview, is written for non-technical audiences who need general

information about the product. Chapters 2 through 5 contain detailed information
and instructions about the product. Other chapters and appendixes describe
installation, maintenance, and configuration instructions or details primarily intended
for qualified maintenance personnel.
This User’s Guide is designed for the following categories of users:
 Systems Engineers – Chapter 1 provides an introduction to the TimeProvider

2300/2700. Cross-references in this chapter direct you to detailed system
information in other chapters as appropriate.
 Installation Engineers – Chapter 2 through Chapter 5 and the appendixes
provide detailed information and procedures to ensure proper installation,
operation, configuration, and testing of the TimeProvider 2300/2700.
 Maintenance Engineers – Chapter 5 and the appendices provide preventive
and corrective maintenance guidelines, as well as procedures for diagnosing and
troubleshooting fault indications and alarms.
Structure of This Guide
This guide contains the following sections and appendixes:
Chapter, Title Description
Chapter 1, Overview Provides an overview of the product, describes the major

hardware and software features, and lists the system
specifications.
Chapter 2, Installing Contains procedures for unpacking and installing the system, and
for powering up the unit.
Chapter 3, CLI Commands Describes the CLI command conventions, functions, and features
and the SNMP protocol option.

Structure of This Guide
Chapter, Title Description
Chapter 4, Provisioning Describes the commands and procedures required to provision the
TimeProvider 2300/2700 after installing the unit.
Chapter 5, Maintenance, Contains preventive and corrective maintenance, and
Troubleshooting & Part Numbers troubleshooting procedures for the product. Also contains part
number and ordering information and procedures for returning the
TP 2300/2700.
Appendix A, System Messages Lists the alarms and events and provides basic indications of the
source of the alarm.
Appendix B, Specifications and Lists the specifications and factory defaults for the TimeProvider
Factory Defaults 2300/2700.
Appendix C, Installing GNSS Provides details about GNSS Antenna kits and procedures for
Antennas installing the GNSS antenna.
Appendix D, PQL Mapping Provides details about the mapping between PQL and various
frequency synchronization quality level scales for input and output
signals.
Appendix E, Software Licenses Contains licensing information for third party software.
Appendix F, Asymmetry Feature Provides details about the automatic asymmetry
compensation feature.
Appendix G, Glossary Provides descriptions of terms used in this document.

Conventions Used in This Guide
Conventions Used in This Guide
This guide uses the following conventions:
 Acronyms and Abbreviations – Terms are spelled out the first time they appear
in text. Thereafter, only the acronym or abbreviation is used.
 Revision Control – The title page lists the printing date and versions of the
product this guide describes.
 Typographical Conventions – This guide uses the typographical conventions
described in the table below.
When text appears

... it means:
this way...
TimeProvider 2300/2700 The title of a document.

User’s Guide
CRITICAL An operating mode, alarm state, status, or chassis label.
Select File, Open... Click the Open option on the File menu.
Press Enter A named keyboard key.

Press; The key name is shown as it appears on the keyboard.
An explanation of the key’s acronym or function
immediately follows the first reference to the key, if
required.
Username: Text in a source file or a system prompt or other text that

appears on a screen.
ping A command you enter at a system prompt or text you

status enter in response to a program prompt. You must enter
commands for case-sensitive operating systems exactly
as shown.
qualified personnel A word or term being emphasized.
Microsemi does not A word or term given special emphasis.

recommend...

Warnings, 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.

Where to Find Answers to Product and Document Questions
Where to Find Answers to Product and Document

Questions
For additional information about the products described in this guide, please contact
your Microsemi representative or your local sales office. You can also contact us on
the web at www.microsemi.com/ftdsupport.
When this manual is updated the updated version will be available for downloading
from Microsemi’s internet web site. Manuals are provided in PDF format for ease of
use. After downloading, you can view the manual on a computer or print it using
Adobe Acrobat Reader.
Manual updates are available at:
www.microsemi.com/ftdsupport
What’s New In This Guide
The following corrections and additions have been made to the TimeProvider
2300/2700 User’s Guide with Rev. B:
 Added Appendix D, PQL Mapping

 Moved PQL Usage and Mapping section and associated tables from Chapter 4 to
Appendix D, PQL Mapping
 Modified Reference Selection Criteria in Chapter 4 to improve PQL description
 Modified Reference Selection Criteria in Chapter 4 to remove the sections PQL
for Inputs and Configured PQL
 Added Appendix G, Glossary
 Modified set ptp command to add Ethernet-default profile (Layer 2 multicast) for
the PTP master
 Modified set ptp command to add “phase-offset” parameter for the PTP client
 Modified the Provisioning the PTP Output section in Chapter 4 to add
Ethernet-default profile (Layer 2 multicast) details
 Modified Holdover Performance parameter in Table B-23 in Appendix B from
“Frequency +/- 14 ppb” to “Frequency +/- 16 ppb”
 Modified set gnss command to add “antenna-current qualification” parameter
 Modified set vlan command for PTP client to add support for two VLANs
 Modified set ptp command for PTP client “vlan-attach” parameter to add support
for two VLANs

What’s New In This Guide
 Modified set ptp command for PTP client “service-tier” parameter to add
“prs-mask” and “extended-sync-mask” options, and to remove “traffic-mask”
option.
 Modified show ptp command for PTP client “service-tier” parameter to add
“prs-mask” option
 Added Table 3-11 to describe status fields in response to Show Status command
 Modified set ptp command for PTP master “config” parameter for all profiles to
add support for “service-load-alarm-threshold”.
 Added description of new PRS Mask license for PTP clients in Chapter 1.
 Added description table of PTP client asymmetry information in Table 3-5 and
added Appendix E to describe Asymmetry Feature.
 Added heat dissipation to Environmental Specifications table.
 Modified response of show Gnss command in Chapter 3 to change from category
from “Health” to “Status”. Also changed responses in this category from “healthy”
to “ok” and from “unhealthy” to “RAIM fault”.
 Reduced the number of significant digits after the decimal point shown in
response to show hardware-status command for voltages(2), GPS current (0),
and temperature (0).
 Modified response to show ptp command for “PTP client status eth1” to remove
“Flow Weight (%)”, “Percentile Clustering (%)”, and “Min Cluster Width (ns)”. Also
removed description of these parameters from Table 3-4.
 Modified response to show ptp command for “PTP client status eth1” to add
“FPP1 (%)”, “FPP2 (%)”, “FPP1 Cluster Width (us)”, and “FPP2 Cluster Width
(us)”. Also added description of these parameters to Table 3-4.
 Modified show ptp command for “PTP master status eth2” to change “Client
Load” to “Service Load” and to remove “PTP Max Number Clients”.
 Modified set ptp command for “PTP client config eth1” to add “fpp
cluster_width_1” and “fpp cluster_width_2” parameters
 Changed default setting for 10 MHz / 1PPS output port from 10 MHz to 1PPS.
 Deleted AlarmID 007 “Entered time/frequency extended holdover state” from
Table A-2 and from the show alarm-config command description.
 Deleted AlarmID 031 “T1E1 Input FREQUENCY ERROR” from Tables A-1 and
A-2 and from the show alarm-config command description.
 Added AlarmID 114 “SYNCE Ethernet Auto-Negotiation Configuration Failure” to
Tables A-1 and A-2 and to the show alarm-config command description.
 Modified set alarm-config command description, test command description, and
Fig. 4-25 to change alarm range from “0 - 300” to “1 - 155”.
 Removed “alias” command.
 Added descriptions of “show synce status” parameters.
 Added two Axcen optical SFPs to Table 2-3.
Related Documents and Information
 Added Table 3-3 to describe response fields to “show ip status” command.

 Added 300m cable kit option to Table 5-7 and Table B-25.
 Modified description of test command and set alarm-config to correct range of
alarms to “1 - 155”.
Related Documents and Information
See your Microsemi representative or sales office for a complete list of available
documentation.
To order any accessory, contact the Microsemi Sales Department. See

www.microsemi.com/sales-contacts/0 for sales support contact information. If you
encounter any difficulties installing or using the product, contact Microsemi
Frequency and Time Division (FTD) Services and Support:
U.S.A. Call Center:

including Americas, Asia and Pacific Rim
Frequency and Time Division
3870 N 1st St.
San Jose, CA 95134
Toll-free in North America: 1-888-367-7966

Telephone: 408-428-7907
Fax: 408-428-7998
email: ftd.support@microsemi.com
Internet: www.microsemi.com/ftdsupport
Europe, Middle East, and Africa (EMEA)

Microsemi FTD Services and Support EMEA
Altlaufstrasse 42
85635 Hoehenkirchen-Siegertsbrunn
Germany
Telephone: +49 700 3288 6435

Fax: +49 8102 8961 533
E-mail: ftd.emeasupport@microsemi.com
ftd.emea_sales@microsemi.com

Chapter 1 Overview
This chapter provides introductory information for the TimeProvider 2300/2700.
In This Chapter
 Overview
– TimeProvider 2300/2700 Features
– Software Options
– Security Features
 Physical Description
 Functional Description
 Configuration Management
 Alarms
098-00564-000 Revision B – June, 2014 Microsemi Confidential Information TimeProvider 2300/2700 User’s Guide 25
Chapter 1 Overview
Overview
Overview
The Microsemi® TimeProvider™ 2700 is an IEEE 1588 Precision Time Protocol

(PTP) Grandmaster scaled and optimized for deployment to support small cells and
to meet the stringent phase timing and synchronization requirements of 4G/LTE
networks.
With an integrated GNSS receiver (GPS or GLONASS) the TimeProvider 2700

meets requirements of the ITU-T G.8272 standard for a Primary Reference Time
Clock (PRTC). It can operate in Synchronous Ethernet (SyncE) networks, and
supports from 8 to 64 PTP clients. The TimeProvider 2700 offers the optional
capability to accept a PTP input or T1/E1 input to complement and backup the
GNSS signal. Additional output capabilities allow it to support legacy frequency
timing applications.
The TimeProvider 2300 Advanced Boundary Clock accepts PTP input. It can
operate in Synchronous Ethernet (SyncE) networks, and supports from 8 to 64 PTP
clients. The TimeProvider 2300 offers the optional capability to accept T1/E1 input
to complement and backup the PTP input signal. Additional output capabilities allow
it to support legacy frequency timing applications.
The TP2300/2700 supports both one-step and two-step clock operation. On the
PTP master port, the user has the option to enable or disable two-step clock
operation on that port. On the PTP client port, the client is capable of receiving and
processing messages from both one-step and two-step clock masters, without any
provisioning necessary. The client auto detects the two-step clock flag in Announce
messages from the master and, based on the setting, runs a one-step or two-step
clock operation.
TimeProvider 2300/2700 Features

 IEEE 1588 Precision Time Protocol Grandmaster
– ITU-T G.8265.1, Telecom-2008, Default (optional) and Ethernet Default
(optional) profiles
 Multi-Sync Enabled Boundary Clock (licensed on TP 2700)
 GNSS (GPS and GLONASS), Primary Reference Time Clock (PRTC)
(TP 2700 only)
 Support for 8 to 64 PTP clients
 SyncE Input and Output
 2 Gigabit Ethernet PTP/SyncE Interfaces (SFP or RJ45)
 E1/T1 Input or Output (optional)
 10 MHZ or PPS, and TOD output
 1 Gigabit Ethernet MGMT Port
26 Microsemi Confidential Information TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014
Chapter 1 Overview
Overview
 1 EIA-232 Serial (Craft) Port

 LED indicators
 Compact 1 RU Footprint
 CLI management and SNMP traps
 DC or AC power
 HTTP/HTTPS/SSL Network Support
Software Options
The TimeProvider 2300/2700 also provides several software options. An activation
key is required to access these options, which include:
 Greater client capacity: PTP client capacity in deployed units can be increased
to 16, 32, or 64 clients, allowing network engineers to design for capacity they
need today and be protected for increased requirements in the future.
 GPS and GLONASS: The base configuration of the TP 2700 allows the choice of
either the GPS or the GLONASS GNSS system for the primary reference signal.
A software license option enables support for both GPS and GLONASS
concurrently, providing a greater level of sync network protection. (The TP 2300
does not have GNSS.)
 PTP Input: Employing PTP distributed over the backhaul network provides a
backup to GNSS, allowing the oscillator to hold accurate timing longer than
otherwise possible. The PTP client option, enabling a boundary clock function,
includes advanced algorithms that compensate for network asymmetry 
particularly important for LTE-TDD and LTE-A networks with tight phase
synchronization requirements. The PTP Input License is included as part of the
TP 2300 base model.
 E1/T1 Input/Output: The E1/T1 software option activates this port for use as
either an input or output. As an input the signal provides a frequency reference to
the clock function. As an output it can be used for synchronization of equipment
using this established timing reference.
 Default Profile: Enables layer 3 multicast capabilities for operation in additional
network scenarios.
See TimeProvider 2300/2700 Part Numbers, on page 291 for part numbers for all
available options.
Activation keys are associated with the serial number of the device on which the
keys are stored and travel with that device. The user must manually enter key(s)
with CLI commands to gain access to the licensed software options.
Chapter 1 Overview
Overview
Security Features
The TP 2300/2700 was designed to provide a high level of security on the Ethernet
ports. The protocols running on the unit run from behind an internal firewall. This
allows access to the UDP ports to be limited or completely inaccessible by other
systems.
Each of the service ports only allows PTP, ICMP, and IGMP. The MGMT port allows
user-configuration of the firewall, which includes ICMP, FTP, SSH, telnet,
HTTPS/HTTP and SNMP.
The ETH1 and ETH2 service ports do not support routing protocols between the
ports. This prevents a malicious attack on the ETH1 port (network 1) to be used to
send a malicious attack via the ETH2 port (network 2) or vice-versa.
The ETH1 and ETH2 service ports also include a hardware traffic limiter. If the
number of packets per second exceeds the limit, the unit will generate an alarm
indicating excessive traffic is being seen. This could be an indication of a malicious
attack or it could also be a large number of clients requesting service from the
server. The system will drop packets received in excess of the limit. Packets
received below the limit will be handled normally.
If the ETH1 and ETH2 service ports do come under attack, only the ports under
attack will be affected due to the system's architecture. The MGMT port will
continue to provide all management facilities for the system during this type of
attack. To minimize system resource usage and deter denial of service attacks, the
system is configured to allow a maximum ICMP ping request rate of 16 per second.
Conclusions
 The TP 2300/2700's architecture isolates functional areas such as user
interfaces and output signal generation to minimize the possible corruption of
time and frequency outputs.
 Only service-specific UDP protocols are enabled.
 From a system security perspective the TP 2300/2700 provides the highest level
of security while providing very accurate time and frequency outputs. However, it
also requires that the user implement best-practice security safeguards in their
networks for the most robust levels of security.
Chapter 1 Overview
Physical Description
The TimeProvider 2300/2700 consists of a 19-inch (48 cm) rack mount chassis,
plug-in modules, and hardware.
Note: The TP 2300/2700 comes equipped with 19-inch rack

mounting brackets. 23-inch (58.42 cm) rack mounting adapters are
also available as a separately ordered item. 21-inch (ETSI) rack
mounting adapters are available as a separately ordered item.
All connections for the TimeProvider 2300/2700 are on the front panel. Figure 1-1 is
a front view of the DC version TimeProvider 2300/2700 showing connectors and
LEDs. Figure 1-2 show the AC version.
Figure 1-1. TimeProvider 2700 DC Version Connectors and LEDs
Figure 1-2. TimeProvider 2700 AC Version Connectors and LEDs
Figure 1-3. TimeProvider 2300 DC Version Connectors and LEDs
Chapter 1 Overview
Figure 1-4. TimeProvider 2300 AC Version Connectors and LEDs
Communications Connections
The TimeProvider 2300/2700 can be controlled through either the Ethernet
Management port or the serial port.
Ethernet Management Port

The Ethernet Management port on the front panel of the TimeProvider 2300/2700 is
a standard 10/100/1000 Base-T shielded RJ-45 receptacle. To connect the
TimeProvider 2300/2700 to an Ethernet network, use a standard twisted-pair
Ethernet RJ-45 cable (CAT5 minimum).
Serial (Craft) Port

The serial port connection is made through a DB-9 female connector on the front
panel of the TimeProvider 2300/2700. This port, which supports a baud rate of
57.6k (57600-8-1-N-1), allows you to connect to a terminal or computer using a
terminal emulation software package. When connecting to this port, use a shielded
serial direct connect cable.
Figure 1-5 shows the DB-9 female connector for the serial port.
Figure 1-5. Serial Port Connector
Input Connections
GNSS Connection
The TimeProvider 2700 features an SMA connector for input from GPS or
GLONASS navigation satellites to provide a frequency and time reference. GNSS is
not available on the TImeProvider 2300.
Chapter 1 Overview
Figure 1-6. GNSS Input Connection
PTP / SyncE Input Connections

The TimeProvider 2300/2700 provides two possible PTP/SyncE input connections,
labeled S1 and R1, although only one connection can be used at any time. The
TimeProvider 2300/2700 features a single Ethernet 1000 Small-form Factor
Pluggable (SFP) connection, labeled S1, for PTP/SyncE input (see Figure 1-7).
Only optical SFPs are supported. See Table 2-3 for a list recommended and
supported SFPs.
Note: A license is required to enable PTP/SyncE Input functionality

on the TP 2700.
Figure 1-7. PTP Input Connections - R1 & S1
T1/E1 Input Connections

The TimeProvider 2300/2700 provides an RJ48c connector (Figure 1-8) that can
accept the following signal types:
 2.048 Mb/s (G.703/9)

 2.048 MHz (G.703/13)
 1.544 Mb/s (G.703)
 1.544 MHz (G.703)
This port is also software configurable as a T1 or E1 output.
Note: A license is required to enable T1/E1 functionality.
Chapter 1 Overview
Figure 1-8. T1/E1 Input Connection
Output Connections
PTP / SyncE Output Connections
The TimeProvider 2300/2700 provides two possible PTP/SyncE output
connections, labeled S2 and R2, although only one connection can be used at any
time. The TimeProvider 2300/2700 features a single Ethernet 1000 Small-form
Factor Pluggable (SFP) connection (optical only), labeled S2, for PTP/SyncE output
(see Figure 1-9). The TimeProvider 2300/2700 features a single RJ45 connector,
labeled R2. The TimeProvider 2300/2700 supports a maximum from 8 to 64 clients
per system in various profiles.
Figure 1-9. PTP Output Connections - R2 & S2
T1/E1 Output Connections

The TimeProvider 2300/2700 provides an RJ48c connector (Figure 1-10) with the
following signal types:
 2.048 Mb/s (G.703/9)

 2.048 MHz (G.703/13)
 1.544 Mb/s (G.703)
 1.544 MHz (G.703)
This port is also software configurable as a T1 or E1 input.
Chapter 1 Overview
Figure 1-10. T1/E1 & TOD Output Connections
TOD Output Port

The TimeProvider 2300/2700 provides an RJ45 connector (Figure 1-10) with Time
of Day (TOD) output.
10MHz & 1PPS Output Connections

The TimeProvider 2300/2700 features a BNC male connector that is software
configurable for either 10 MHz or 1PPS output. See Figure 1-11.
Figure 1-11. 10 MHz/1PPS Output Port
Reset Button
The reset button has two functions. When pressed quickly, the system reboots.
When held for over 10 seconds, the system configuration is set to the factory default
settings. This feature is useful if you have forgotten your password.
Power and Ground Connections

The TimeProvider 2300/2700 is available with either –48 VDC power or 120/240
VAC power. The TimeProvider 2300/2700 is not equipped with a Power switch; DC
power is controlled by a power distribution panel connected to the power
connectors. AC power is controlled by the unplugging the AC power cord. Frame
ground connections on the TP 2300/2700 are made on the grounding stud located
on the left side and right side of the front panel, as identified with the international
Ground marking, as shown in Figure 1-12 and Figure 1-13.
Warning: To avoid serious personal injury or death, exercise caution

when working near high voltage lines and follow local building
electrical codes for grounding the chassis.
Chapter 1 Overview
Functional Description
Figure 1-12. TimeProvider 2300/2700 DC Version Power and Ground (TP 2700 shown)
Figure 1-13. TimeProvider 2300/2700 AC Version Power and Ground (TP 2700 shown)
See Figure 1-14 below for a representation of the functional architecture for the
TimeProvider 2300/2700.
Chapter 1 Overview
Figure 1-14. Functional Architecture.
Note: The TP 2300 does not include a GNSS receiver.
LEDs
The TimeProvider 2300/2700 provides from three to six LEDs on the front panel,
based on the specific model, that indicate the following:
 Power Status
 Battery A Status (DC power version only)
 Battery B Status (DC power version only)
 Alarm Status
 GNSS Signal Status (TP 2700 only)
 Clock Status
Figures 1-15 through 1-18 show the LEDs
Chapter 1 Overview
Figure 1-15. LEDs for TP2700 - DC Version
Figure 1-16. LEDs for TP2700 - AC Version
Figure 1-17. LEDs for TP2300 - DC Version
Figure 1-18. LEDs for TP2300 - AC Version
Communication Ports
Communication ports on the TimeProvider 2300/2700 allow you to provision,
monitor, and troubleshoot the chassis. You can communicate with the TimeProvider
2300/2700 using either CLI or SNMP protocols.
Local Craft Serial Port

The serial port supports local control; you can configure the TimeProvider
2300/2700 with CLI commands using a terminal or computer with terminal
emulation software. The connector is located on the front panel. The Local port is
configured as a DCE interface and the default settings are as follows:
 Baud = 57.6K
 Data Bits = 8 bits
 Parity = None
 Stop bits = 1
 Flow Control = None
Management Ethernet Port

The Management Ethernet connector provides connectivity to an Ethernet local
area network. Each Ethernet port has a unique internet protocol (IP) address. Once
the IP address is set and a connection is made to a Local Area Network (LAN), you
can access the TimeProvider 2300/2700.
Chapter 1 Overview
Time Inputs
The TimeProvider 2700 can use either GNSS, or PTP as external input references.
The TimeProvider 2300 can use PTP. The PTP signal connects to an SFP (S1) or
RJ45 (R1) connector on the front panel. The GNSS (GPS or GLONASS) reference
connects to an SMA connector on the front panel of the TP 2700.
Note: A license is required to enable PTP Input functionality on the

TP 2700.
Frequency Inputs
The TimeProvider 2700 can use either GNSS, PTP, SyncE, or E1/T1 signals as
external frequency input references. The TimeProvider 2300 can use either
PTP/SyncE or E1/T1 signals as frequency input references. The PTP/SyncE signals
connect to an SFP (S1) or RJ45 (R1) connector on the front panel. The GNSS (GPS
or GLONASS) reference connects to an SMA connector on the front panel. The
E1/T1 input connects to an RJ48c connector on the front panel.
A license is required to enable PTP/SyncE Input functionality on the

TP 2700.
Synchronization and Timing Outputs

The TimeProvider 2300/2700 can provide PTP/SyncE, E1/T1, 10 MHz/1PPS, or
TOD output signals. The PTP/SyncE signal connects to an SFP (S1) or RJ45 (R1)
connector on the front panel. The T1/E1 output connects to an RJ48c connector on
the front panel. The 10MHz/1PPS output connects to a BNC connector on the front
panel, and the TOD output connects to an RJ45 connector on the front panel.
Chapter 1 Overview
Configuration Management
The Command Line Interface (CLI), also called the ASCII command set, can be
used to control the TimeProvider 2300/2700 from a terminal connected to the
EIA-232 serial port, or the Ethernet MGMT port. Refer to Chapter 3, CLI Commands
for further details.
Note: Before you can communicate with the TimeProvider 2300/2700

through an Ethernet connection, you must first configure the Ethernet
port using the serial connection (see Provisioning the Ethernet
Ports, on page 213).
Web Interface
The TP 2300/2700 also allows the user to access information via the MGMT port
using HTTP or HTTPS protocol. To use the TP 2300/2700 web interface, enter the
MGMT port IP address into a web browser. Enter your user name and password for
the TP 2300/2700 when prompted.
Status View
See Figure 1-19 for an example of the status screen that will appear.
Figure 1-19. Web Interface - Status
Chapter 1 Overview
Clients List View

Click the Clients List button to view a list of all clients. Information displayed is:
 IP Address
 VLAN ID
 Priority
 Clock ID
 Announce Interval
 Sync Interval
 Delay Interval
 Connection Time
The connection time is in seconds and is a count of how long a client has been
getting service from the TP 2300/2700. The connection time gets initialized for a
client when the Sync flow is first requested in Unicast profiles (Telecom-2008 and
ITU-8265.1) and when Delay Request messages are first captured in multicast
profiles (Default and Ethernet-Default). See Figure 1-20 for an example of the
Clients List screen that will appear. See Table 3-4 for descriptions of client
information that is displayed.
Figure 1-20. Web Interface - Clients List
Alarms View
Click the Alarms button to view a list of all active alarms.See Figure 1-21 for an
example of the Alarms screen that will appear.
Chapter 1 Overview
Alarms
Figure 1-21. Web Interface - Alarms
Alarms
The TP 2300/2700 uses alarms to notify you when certain conditions are
deteriorating below specified levels or when issues arise like loss of power or loss of
connectivity. These alarms are indicated by status LEDs and by SNMP traps. You
can provision the alarm to either be enabled or disabled and the current alarm state
can be obtained via the communication ports. For more information, see
Provisioning Alarms, on page 251 and Appendix A, System Messages.
This chapter describes the procedures for installing the TimeProvider 2300/2700.
In This Chapter
 Getting Started
 Unpacking the Unit
 Rack Mounting the TimeProvider 2300/2700
 Installation Check List
 Signal Connections
– Communications Connections
– TP 2300/2700 Synchronization and Timing Connections
 Connecting the GNSS Antenna
 Installation Check List
 Applying Power to the TimeProvider 2300/2700

Getting Started
Getting Started
Before you begin to install the TimeProvider 2300/2700, review the information in
this section.
If you encounter any difficulties during the installation process, contact Microsemi
Frequency and Time Division (FTD) Services and Support. See Contacting
Technical Support, on page 296 for telephone numbers. Contact Microsemi FTD
Services and Support for technical information. Contact Customer Service for
information about your order, RMAs, and other information.
Security Considerations for TP 2300/2700 Installation

 The TP 2300/2700 should be installed in a physically secure and restricted
location.
 The TP 2300/2700's management Ethernet port should be installed behind the
company's firewall to prevent public access.
 Whenever possible, the TP 2300/2700's Ethernet service ports should be
installed behind the company's firewall to prevent public access.
Site Survey
The TimeProvider 2300/2700 is intended for installation in the following locations:
 Central Office intra-building

 Cell site intra-building
 NEC site
 Aggregate site
Before you begin installation, determine the chassis location, ensure the
appropriate power source is available (–48 VDC or 120/240 VAC), and ensure that
the equipment rack is properly grounded.
The TimeProvider 2300/2700 is designed to mount in a 19-inch (48 cm) rack,

occupies 1.75 in (4.5 cm, 1 RU) of vertical rack space, and has a depth of 10 in
(25.4 cm).
Note: 1RU above the TimeProvider 2300/2700 must be left

unoccupied for heat dissipation.
23-inch (58.42 cm) rack mounting adapters are available as a separately ordered
item. 21-inch (ETSI) rack mounting adapters are also available.

Getting Started
The DC version of the TimeProvider 2300/2700 is to be installed into a rack with

permanent connection to the -48VDC mains. This connection is to be made to a
branch over-current, short-circuit protection device with replaceable fusing of 1.5
amps, maximum. For permanently connected equipment, a readily accessible
disconnect device shall be incorporated in the building installation wiring.
The AC version of the TimeProvider 2300/2700 is to be installed into a rack. The AC

power connection is to be made to a 120 or 240 VAC power receptacle following
local codes and requirements. An external Surge Protective Device is required to be
used with the AC version of the TimeProvider 2300/2700.
Warning: The intra-building ports of the equipment is suitable for

connection to intra-building or unexposed wiring or cabling only. The
intra-building ports of the equipment MUST NOT be metallically
connected to interfaces that connect to the OSP or its wiring. These
interfaces are designed for use as intra-building interfaces only (Type
2 or Type 4 ports as described in GR-1089-CORE) and require
isolation from the exposed OSP cabling. The addition of Primary
Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
Environmental Requirements
To prevent the unit from malfunctioning or interfering with other equipment, install
and operate the unit according to the following guidelines:
 Operating temperature: –40Fto 149F (–20 C to 65C) for TP 2300/2700 with

quartz oscillator (OCXO); 23Fto 131F (–5 C to 55C) for TP 2300/2700 with
Rubidium oscillator. Startup temperature > -20C (-4F) for TP 2300/2700 with
OCXO.
 Operating Humidity: 5% to 95% RH, maximum, w/condensation
 Use only shielded cable for all signal wiring, including I/O, clocks and Ethernet.
Ground appropriately at both ends, or as required by local standards.
 Secure all cable screws to their corresponding connectors.
Caution: To avoid interference, you must consider the

electromagnetic compatibility (EMC) of nearby equipment when you
install the TP 2300/2700.
Electromagnetic interference can adversely affect the operation of

nearby equipment.
Installation Tools and Equipment

You will need the following tools and equipment to install the TimeProvider
2300/2700:
 Standard tool kit

Unpacking the Unit
 Cable ties, waxed string, or acceptable cable clamps

 1 mm² / 18 AWG (minimum) stranded wire at 300 volt insulation for –48 VDC
 1 mm² / 16 AWG wire to connect grounding lug to permanent earth ground
 Two UL listed Ring Lugs for grounding connections
 Crimping tool to crimp the ring lug
 Shielded cabling of the appropriate impedance required by the specific signal
type for signal wiring (including GNSS, and Ethernet)
 Mating connectors for terminating signal wiring
 ESD wrist strap for installing modules
 Fasteners for mounting the equipment in rack
 Digital multimeter or standard Voltmeter for verifying power connections to the
chassis
 Laptop computer with communications software (e.g., Microsoft Hyperterminal,
ProComm Plus or EmTec ZOC) for setting system parameters
Unpacking the Unit
The TimeProvider 2300/2700 is packaged to protect them from normal shock,

vibration and handling damage. (Each unit is packaged separately.)
Caution: To avoid ESD damage to parts that are packaged with the
TP 2300/2700, observe the following procedures.
Unpack and inspect the unit as follows:
1. Wear a properly grounded protective wrist strap or other ESD device.
2. Inspect the container for signs of damage. If the container appears to be

damaged, notify both the carrier and your Microsemi distributor. Retain the
shipping container and packing material for the carrier to inspect.
3. Open the container, being careful to cut only the packaging tape.
4. Locate and set aside the printed information and paperwork that is included in
the container.
5. Remove the unit from the container and place it on an anti-static surface.
6. Locate and set aside small parts which may be packed in the container.
7. Remove the accessories from the container.

Rack Mounting the TimeProvider 2300/2700
8. Remove the anti-static packaging from the unit and accessories.
9. Verify that the model and item number shown on the shipping list agrees with the
model and item number on the equipment. The item number can be found on a
label affixed to the bottom of the unit. See Figure 2-1 for the location of the label
on the TP 2300/2700. Contact your Microsemi distributor if the model or item
number do not match.
For a complete listing of item numbers, see Table 5-4 and Table 5-5.
Figure 2-1. TP 2300/2700 - Location of Product Label
The installation procedure described in this section provides general guidelines for
installing the TimeProvider 2300/2700. Always follow applicable local electrical
standards.
Use the following steps to mount the TimeProvider 2300/2700 in a rack.
Note: 1RU above the TimeProvider 2300/2700 must be left

unoccupied for heat dissipation.
The TimeProvider 2300/2700 comes equipped with 19-inch rack mounting brackets.
23-inch (58.42 cm) rack mounting adapters are available as a separately ordered
item. 21-inch (ETSI) rack mounting adapters are also available.
1. TimeProvider 2300/2700 is shipped with rack mounting brackets attached. The

rack mounting brackets can be removed and reattached in a different orientation,
if desired. See Figure 2-3 for mounting hole placements. See Figure 2-2 and for
chassis dimensions. Ensure that the mounting brackets on both sides are

attached to the chassis at equal distances from the front of the unit (see
Figure 2-4) using 6-32 x 1/4-inch screws.
2. Mount the chassis to the front of the equipment rack rails with four screws and
associated hardware. Use the proper screws for the equipment rack.
Figure 2-2. Dimensions for TimeProvider 2300/2700
Figure 2-3. Mounting Hole Placements for TP 2300/2700

Making Ground and Power Connections
Figure 2-4. Rack Mounting the TP 2300/2700
Warning: To avoid accidental power-up of the chassis, remove the A

and B fuses on the branch over-current protection unit before
beginning installation of the DC version of the TP 2300/2700. The unit
is not equipped with a power on/off switch.
The DC version of the TimeProvider 2300/2700 has –48 VDC power connectors
which are located on the left side of the front panel (see Figure 2-5). Separate frame
ground terminals are on the left side and right side of the front panel.
The AC version of the TimeProvider 2300/2700 has a 120/240 VAC connector,

which is located on the left side of the front panel. (see Figure 2-6). Separate frame
ground terminals are on the left side and right side of the front panel.

Ground Connections
Frame ground connections are made using the M4 Grounding Terminal Studs,
which are marked with the universal ground symbol, as shown in Figure 2-9. These
studs are located on the left and right sides of the front panel for the TP 2300/2700.
Figure 2-5. TimeProvider 2700 Power & Ground Connections - DC Version
Figure 2-6. TimeProvider 2700 Power & Ground Connections - AC Version
Figure 2-7. TimeProvider 2300 Power & Ground Connections - DC Version
Figure 2-8. TimeProvider 2300 Power & Ground Connections - AC Version

Figure 2-9. Universal Ground Symbol
Note: If only one ground connection is to be used, Microsemi

recommends connecting to the frame ground connection
closest to the power connector (AC or DC).
After installing the TimeProvider 2300/2700 into the rack, connect the chassis to the
proper grounding zone or master ground bar. The DC version of the TimeProvider
2300/2700 can be part of a Common Bonding network (CBN) or an Isolated
Bonding network (IBN). The AC version of the TimeProvider 2300/2700 can only be
part of a CBN. The System is to be connected as a DC-I configuration. All bonding
and grounding connection shall be made of copper (tinned or untinned), per
GR-1089, R9-17 [82].
Run a 16 AWG green/yellow-striped insulated wire from the TimeProvider

2300/2700 grounding lug to the earth Ground on the rack. The rack grounding
method is below.
Recommendation: Although there are a number of methods for

connecting the equipment to earth ground, Microsemi recommends
running a cable of the shortest possible length from the ground lug to
earth ground.
1. Crimp the customer-supplied UL listed Ring Lug to one end of the 16 AWG wire.
Connect the ring lug to the ground terminal on the left side of the front panel
using the supplied M4 Kept machine nut, tightening to a torque value of 15.95
in-lbs. The surface of the TimeProvider 2300/2700 earth grounding terminal must
be clean of contaminants and oxidation.
2. Crimp the appropriate customer-supplied UL listed Ring Lug to the other end of
the 1 mm² / 16 AWG green/yellow-striped wire. Remove the paint and sand the
area around the screw hole to ensure the proper conductivity. Coat the
connection with an electrically conductive antioxidant compound such as
Kopr-shield spray. Connect this Ring Lug to the rack with appropriate customer
supplied screws and external star lock washers, tightening to a torque value of
53.45 in-lbs.
3. Using a digital voltmeter, measure between the ground and chassis and verify
that no voltage exists between them.

DC Power Connections
Use the following procedure to make the power connections for the DC version of
the TimeProvider 2300/2700.
Warning: To avoid possible damage to equipment, you must provide

power source protective fusing as part of the installation. The
TimeProvider 2300/2700 is intended for installation in a
restricted-access location.
Caution: To avoid damage to the unit, remove the fuses in the fuse
panel which provides power to the TimeProvider 2300/2700 before
making power connections.
1. Ensure the power source is turned off.
2. Connect the two frame ground terminals to earth ground.
3. Locate the power connectors included in the installation kit.
4. Using 1 mm² / 18 AWG (minimum) stranded wire, connect primary and

secondary power to the connectors per the polarity markings. Use the polarity
markings of "A", “B” and "RTN" as a reference for the proper polarity
connections. Tighten the screws for Returns to a torque value of 9.6 in-lbs.
Note: The -48VDC power must be connected with the proper polarity.
The unit will not be damaged by reverse polarity, but the unit will not
operate if the polarity is reversed.

5. Attach the DC power connector cover, as shown in Figure 2-10, and tighten the
screws.
Figure 2-10. Installing DC Power Connector Cover
Figure 2-11. DC Power Connector Cover Installed
Testing DC Power Connections

To verify that the power connections to the TimeProvider 2300/2700 are correct,
follow the steps in this section. The primary DC power connections on the TP
2300/2700 are referred to as Power A and Return A. The secondary DC power
connections are referred to as Power B and Return B. Use a digital multimeter
(Fluke 77 or equivalent) to make the measurements.
1. Remove all fuses that supply power to the unit from the fuse panel.
2. Remove the power connector cover and disconnect the -48V battery leads from
the unit’s power connector terminals. See the primary and secondary power
connections in Figure 2-12. Leave the Return battery leads connected to the unit.
Figure 2-12. Power and Ground Connections on DC Version of TP 2300/2700

3. At the chassis end of the battery leads, use the multimeter to measure the
voltage between the following test points:
Test Point Test Point Result

Battery A lead Battery B lead 0V
Battery A lead Primary: Return A 0V
Battery A lead Earth Ground 0V
Battery B lead Secondary: Return B 0 V
Battery B lead Earth Ground 0V
4. Reconnect the –48V battery A and battery B leads to the –48V A and –48V B
terminal connectors.
5. Install the A fuse in the power source fuse panel.
6. Measure the voltage between the –48V A and Return terminals on the primary
power module. The multimeter should indicate –38.4 VDC to –72 VDC.
7. Install the B fuse in the power source fuse panel.
8. Measure the voltage between the –48V B and Return terminals on the secondary
power module. The multimeter should indicate –38.4 VDC to –72 VDC.
9. Reconnect the DC power connector cover.
The unit is now powered up.
AC Power Connection
Use the following procedure to make the power connections for the AC version of
the TimeProvider 2300/2700. An external Surge Protective Device is required to be
used with the AC version of the TimeProvider 2300/2700.
Figure 2-13. TimeProvider 2300/2700 AC Power Connector

power source protective fusing as part of the installation. The
TimeProvider 2300/2700 is intended for installation in a
restricted-access location.

Signal Connections
1. Insert the female end of the AC power cord into the AC power connector on the
TP 2300/2700.
2. Secure the power cord to the tab on the lower-left corner of the unit with a zip tie
(or similar) to prevent accidental removal of the power cord.
3. Plug the male end of the AC power cord into an active 120 VAC or 240 VAC
power socket.
The unit is now powered up.
Signal Connections
The connectors for the TP 2300/2700 and TP 2300 are located on the front panel.
Communications Connections
The communication connections allow user control of the TimeProvider 2300/2700.
The EIA-232 serial port and Ethernet Management port are located on the front
panel are shown in Figure 1-1.
System Management (MGMT) Port

The System Management port is standard 10/100/1000 Base-T shielded RJ-45
receptacle. To connect the TimeProvider 2300/2700 to an Ethernet network, use an
Ethernet RJ-45 cable. See Table 2-1 for connector pinouts.
Table 2-1. System Management Ethernet Connector Pin Assignments
10Base-T
1000Base-T
RJ-45 Pin 100Base-T
Signal
Signal
1 TX+ (Transmit positive) BI_DA+
2 TX- (Transmit negative) BI_DA
3 RX+ (Receive positive) BI_DB+
4 Not Used BI_DC+
5 Not Used BI_DC
6 RX- (Receive negative) BI_DB
7 Not Used BI_DD+
8 Not Used BI_DD

Signal Connections
Serial (Craft) Port

The serial port connection is made through a DB-9 female connector on the front
panel of the unit. This port, which supports a baud rate of 57.6k (57600-8-1-N-1),
allows you to connect to a terminal or computer using a terminal emulation software
package for remote monitoring and control. When connecting to this port, use a
shielded serial direct connect cable.
Figure 2-14 shows the DB-9 male connector that mates with the serial port on the
Figure 2-14. Serial Port Male Mating Connector Pins
Table 2-2 describes the DB-9 connector pin assignments for the serial port.
Table 2-2. Serial Port Connector Pin Assignments
Signal Pin
TXD (Received Data) 2
RXD (Transmitted Data) 3
Ground 5
TP 2300/2700 Synchronization and Timing Connections

The TimeProvider 2700 has one GNSS input, one PTP timing input (license
required), and one PTP timing output. The TimeProvider 2300 has one PTP timing
input and one PTP timing output. The TimeProvider 2300/2700 also has one E1 or
T1 output, one 10MHz or 1PPS output, and one TOD output.
GNSS Connection (TP 2700 Only)

To connect a GNSS signal to the TP 2700, you must install a GPS or GLONASS
antenna. See Connecting the GNSS Antenna, on page 59.
Caution: The GNSS cable should only be connected while the unit is
properly earth grounded.

Signal Connections

external lightning protection when installing the GNSS antenna to
prevent transients.
PTP Connections
The TimeProvider 2300/2700 features two Ethernet 1000 Small-form Factor
Pluggable (SFP) connections, S1 and S2. The S1 port is a PTP input connection.
The S2 port is a PTP output connection. See Figure 2-15.
Figure 2-15. PTP Input/Output
The TimeProvider 2300/2700 also features two standard 100/1000Base-T shielded

RJ-45 receptacles, R1 and R2, that can be used instead of the SFP ports. R1 is the
PTP input connection. R2 is the PTP output connection.
Note: The SFP ports, S1 and S2, are mutually exclusive of the RJ-45
ports, R1 and R2
Only the SFP transceivers in Table 2-3 are recommended and supported. Other
SFP transceivers are not supported and may cause the TimeProvider 2300/2700 to
not comply with regulatory requirements. Figure 2-16 shows a typical optical SFP
transceiver.
Figure 2-16. Optical SFP Transceiver

Signal Connections
Table 2-3. Recommended and Supported SFP Transceivers
Type Transceiver Distance (max)
Optical 1000 Base-LX Avago AFCT-5701PZ 10km on 9/125m

Single-Mode Ethernet 1310nm Finisar FTLF1319P1BTL single-mode fiber
(Microsemi 121-20621-10-2) Axcen AXGE-1354-0531
Optical 1000 Base-SX Avago AFBR-5710PZ 500m on 50/125m

Multi-Mode Ethernet 850nm Finisar FTLF8519P2BNL multi-mode fiber
(Microsemi 121-20621-11-2) Axcen AXGE-5854-0511
275m on 62.5/125m
multi-mode fiber
Note: Recommended and supported SFP connectors comply with

FDA radiation performance standards, 21 CFR Subchapter J.
T1/E1 Connection
The TimeProvider 2300/2700 features a single RJ-48C port for either a T1 or E1
output signal, as shown in Figure 2-17. This RJ-48C port is software configurable as
either a T1 output port or E1 output port.
The T1/E1 port can provide the following output signal types:
 2.048 Mb/s (G.703/9)

 2.048 MHz (G.703/13)
 1.544 Mb/s (G.703)

Signal Connections
 1.544 MHz (G.703)
Figure 2-17. T1 / E1 and TOD Outputs RJ-45 Connection
Table 2-4. T1/E1 Output Port Pin-Outs - RJ-48C Connector
Pin Signal
1 Rx Ring
2 Rx Tip
3 NC
4 Tx Ring
5 Tx Tip
6 NC
7 NC
8 NC

Signal Connections
TOD Connection
The TimeProvider 2300/2700 features a RJ-45 port for the TOD output signal, as
shown in Figure 2-17. See Table 2-5 for pin-outs for this RJ-45 connector. See Table
2-6 for TOD default parameters.
Table 2-5. 1PPS+TOD Port Pin-Outs - RJ45 Connector
Pin Signal Comment
1 422_1_Pos 1PPS
2 422_1_Neg 1PPS
3 No Connection Default state is open (high impedance)
7 422_2_Pos TOD time information
8 422_2_Neg TOD time information
See Table B-16, Table B-17, Table B-18, and Table B-19 in Appendix B for TOD
format details.

Connecting the GNSS Antenna
1PPS/10MHz Connections
Table 2-6. Default Parameters for TOD Information Transmission
Pin Default Comment
Baud Rate 9600 Cannot be changed

Parity Check None
Start Bit 1 (low level)
Stop Bit 1 (high level)
Idle Frame High level
Data Bits 8
The TimeProvider 2300/2700 features a single BNC male port for the 10 MHz or
1PPS signal. See Figure 2-18. This port is software-configurable to provide either a
1PPS or 10 MHz signal.
Figure 2-18. 10MHz/1PPS Output Connection
Caution: The GNSS cables should only be connected while the unit
is properly earth grounded.
The antenna connections for the TP 2700 are made at the SMA female connector
labeled GNSS. Allow at least one hour for the unit to track and lock to GPS or
GLONASS satellites.
Figure 2-19. GNSS Input Connection

Installation Check List
Proper cable, grounding techniques, and lightning arrestors should be used. Mount
the antenna outside, preferably on the roof with an unobstructed view of the sky. Do
not mount the antenna near a wall or other obstruction blocking part of the sky.
Mount the antenna well above roads or parking lots.
Note: Cable delay must be determined and entered into TP 2700 with
the “set gnss cable-delay” command. See Table B-25 for cable
delay values of TP 2700 GNSS antenna kits.
Warning: To avoid serious personal injury or death, exercise caution

when working near high voltage lines. In particular:
 Use extreme caution when installing the antenna near, under, or

around high voltage lines.
 Follow local building electrical codes for grounding the chassis.
Installation Check List
To verify that the installation of the TimeProvider 2300/2700 is complete, perform

the checks and procedures in Table 2-7.
Table 2-7. Installation Completeness Checklist
Operation Complete
Ensure the TimeProvider 2300/2700 chassis is securely attached to mounting

rack
Verify that all power and ground wires are installed correctly and securely
Verify that all communications cables are properly installed
Verify that all input and output cables are properly installed
Applying Power to the TimeProvider 2300/2700
The TimeProvider 2300/2700 is not equipped with a Power switch. DC power is

controlled by a power distribution panel. After installing the unit in a rack and making
the necessary connections described in previous sections, turn on power at the
distribution panel.

Normal Power Up Indications

As the TimeProvider 2300/2700 powers up and begins normal operation, the LEDs
all turn on. After the self-test is complete and the firmware is operational, the LED
states may change to indicate the appropriate state or status.
Table 2-8 provides a description of the TP 2300/2700 LEDs.
Table 2-8. LED Descriptions
Label LED Description
POWER Power Green - Power available

Module Power Indicator Off - Power not available
PWR A -48V A-Bus Off - A-No Power

A-Bus Battery Indicator Green - A-Bus power OK
PWR B -48V B-Bus Off - B-No Power

B-Bus Battery Indicator Green - A-Bus power OK
CLOCK Clock Status Green - Time or Frequency clock in Normal or

Bridging state
Flashing Green - Time or Frequency clock in
Fast Lock or Recovery state
Amber - Time or Frequency clock in Freerun or
Holdover state
Flashing Amber - Clock in Warmup state
ALARM Alarm Off -Operating normally

System alarm/fault indicator Amber - Minor Alarm(s)
Red - Major/Critical Alarm(s)
GNSS GNSS Status Green - GNSS enabled and GNSS

GPS / GLONASS engine status engine/interface is operating and tracking
indicator normally
Amber - GNSS enabled and GNSS engine or
antenna interface has operational issues, not
tracking normally
Red - Short circuit or open circuit
Off - GNSS disabled or not installed
MGMT Ethernet Management Port Left Flashing Green - Activity for 10/100/1000M
LEDs on the Ethernet connector Left Green - Link Established for 10/100/1000M
Left Off - Link has not been established
Right Amber - Link established for 100M
Right Green - Link established for 1000M
Right Off -No link for 100/1000M
ETH1 -S1 Ethernet Port 1 - SFP (s1) Green - Activity on link for 1000M
LEDs on the Ethernet connector Off - No Activity

Table 2-8. LED Descriptions (Continued)
Label LED Description
ETH1 - R1 Ethernet Port 1 - RJ45 (r1) Left Amber Flashing - Activity on link for 100M
LEDs on the Ethernet connector Left Amber On - Link established for 100M
Left Amber Off - No link for 100M
Right Green Flashing- Activity on link for 1000M
Right Green On - Link established for 1000M
Right Green Off - No Link for 1000M
ETH2 - S2 Ethernet Port 2 - SFP (S2) Green - Activity on link for 1000M
LEDs on the Ethernet connector Off - No Activity
ETH2 - R2 Ethernet Port 2 - RJ45 (R2) Left Amber Flashing - Activity on link for 100M
LEDs on the Ethernet connector Left Amber On - Link established for 100M
Left Amber Off - No link for 100M
Right Green Flashing- Activity on link for 1000M
Right Green On - Link established for 1000M
Right Green Off - No Link for 1000M

Chapter 3 CLI Commands
This chapter describes the CLI command conventions, the prompts, line editing
functions, and command syntax. The CLI command functions and features are
organized by user security access levels and are listed alphabetically.
In This Appendix
 CLI Overview
 TimeProvider 2300/2700 CLI Command Set

Chapter 3
CLI Overview
CLI Overview
The Command Line Interface (CLI), also called the ASCII command set, can be
used to control the TimeProvider 2300/2700 from a terminal connected to the
EIA-232 serial port, or the Ethernet port.
TimeProvider 2300/2700 CLI Command Conventions

The following are conventions used for the TimeProvider 2300/2700 CLI command
set.
 Commands are not case sensitive.

 { }  Braces indicate more than one parameter data option. When entering
options in the CLI command, enter one option from those available within the
braces. Options within braces { } are separated by a pipe ( | ).
 [ ]  Brackets provide information about the allowed range. The first value is the
minimum, and the last value is the maximum.
 Bold highlights keywords in the command syntax
 Italics indicate variable options.
CLI Command Keyboard Usage

 You must press the SPACE key, and then press the TAB key after entering a CLI
command. Also, after entering a command, you may see <enter>. This is a
prompt for you to press ENTER to execute the command that you entered.
 The interface has built-in features for navigating within the CLI command
hierarchy, which are as follows:
 The TAB key can be used at any time while typing a command (including at the
prompt) to provide continuation options. Press the TAB key to display a list of the
available commands. Press the TAB key at any time while typing a command 
TimeProvider 2300/2700 will respond with the completion of the keyword or
available completion choices based on the letters you typed.
 The ? (SHIFT+QUESTION MARK) accesses the CLI online help. It can be used
at any time while typing a command (including at the prompt) to provide
continuation options. These options include brief descriptions of commands, or
data type, format, and range.
 If typing of a keyword is partially complete, the completion will display if it is
unique, otherwise, the completion choices will be available.
 If the keyword is complete, and you press the TAB key or ? (SHIFT+QUESTION
MARK), the choices for the next syntax element will display.

Chapter 3
CLI Overview
In the following example, if you press the TAB key, or the ?

(SHIFT+QUESTION MARK), after typing s, the CLI commands set,
set-timeout, show, and sync display.
Typing s at the prompt:
TP2700> s
Then pressing the TAB key :

set set-timeout show sync
Or pressing the ? (SHIFT+QUESTION MARK)will display the available

commands that start with s (for this example) and brief descriptions of those
commands:
set -Set TP2700 information or setting
show -Display TP2700 information or setting
set-session-timeout -Set the inactivity timeout to the defined

seconds
 Previously typed commands can be recalled by using the UP ARROW key. You
can recall up to five previously typed commands. Continually pressing UP
ARROW will show previously typed commands but does not cycle. After pressing
the UP ARROW key five times, you will go back to the last command you
previously typed. Use the DOWN ARROW key to cycle the five prior typed
commands in the opposite direction.
 You can use the BACKSPACE to correct keystroke errors, or to reuse parts of a
previously typed command. When using BACKSPACE, the removed characters
will still appear on the screen, but they have been removed to the position shown
by the cursor. When you start typing, the removed characters are overwritten.
Command Line Format

The command line format is as follows:
[Verb] Command [Parameter] [Data] EOL
 Verb - the type of action to be taken with the command.

– Set - enables you to provision a defined parameter.
– Show - enables you to display the provisioned state of a parameter.
 Parameter - command input that defines the particular command element to be
shown or modified.
 Data - the data input for the parameter.
 EOL - this parser responds only to <CR Return>. When the parser receives
<CR Return>, the input is terminated, and the command line entry is processed.

Chapter 3
TimeProvider 2300/2700 CLI Command Set
Command User Levels

The TimeProvider 2300/2700 provides a hierarchy of CLI command user levels that
permit an increasing level of access to system parameters. This allows the system
administrator to add users who can only view but not change system parameters
and users who can view and change system parameters.
The users assigned to each security level have access options available as follows:
 Level 1 - user class, with read-only rights

 Level 2 - config user class, with read-write rights
 Level 3 - administrator user class, with read-write rights and can also configure
users and upgrade firmware
This section provides an alphabetical listing and details of all CLI commands.
show alarm
Displays the system's standing (active) alarms and events.
Command Syntax:
show {alarm | event}
Example 1:
TP2700> show alarm
Response 1:
--------------------------------------------------------------------------------
|ID |Severity|Date-Time |Descriptions |
|---|--------|-------------------|---------------------------------------------|
|111|minor |2013-05-09 17:14:49|Ethernet port ETH2 link down |
--------------------------------------------------------------------------------
Example 2:
TP2700> show event
Response 2:

Chapter 3
-------------------------------------------------------------------
|ID |Date-Time |Descriptions |
|---|-------------------|-----------------------------------------|
|4 |2013-05-09 17:53:26|Entered time normal-track state |
|...|...................|.........................................|
|4 |2013-05-09 17:53:26|Entered frequency normal-track state |
-------------------------------------------------------------------
Remarks: The information displayed is expected to be identical to an entry in the

Event/Alarm Log File.
Level : User, Config, and Admin

Chapter 3
show alarm-config
Displays the alarm configuration including alarm ID, severity, state, reporting delay
and description for the TP 2300/2700 alarms. This also displays if the alarm is
transitory.
Command Syntax:
show alarm-config
Example:
TP2700> show alarm-config
Response :
--------------------------------------------------------------------------------
|ID |Severity|State |Delay |Event/Alarm Descriptions |
|----|--------|-------|-------|------------------------------------------------|
|1 |minor |enable |0 |"Entered time/frequency warm-up state" |
|....|........|.......|.......|................................................|
|2 |minor |enable |0 |"Entered time/frequency free-run state" |
|....|........|.......|.......|................................................|
|3 |event |enable |0 |"Entered time/frequency fast-track state" |
|....|........|.......|.......|................................................|
|4 |event |enable |0 |"Entered time/frequency normal-track state" |
|....|........|.......|.......|................................................|
|5 |event |enable |0 |"Entered time/frequency bridging state" |
|....|........|.......|.......|................................................|
|6 |minor |enable |0 |"Entered time/frequency holdover state" |
|....|........|.......|.......|................................................|
|8 |minor |enable |0 |"Entered time/frequency holdover rec state" |
|....|........|.......|.......|................................................|
|21 |minor |enable |0 |"GNSS/SYNCE/PTP/T1E1 input poor quality" |
|....|........|.......|.......|................................................|
|22 |event |enable |0 |"GNSS/PTP input time qualified" |
|....|........|.......|.......|................................................|
|23 |event |enable |0 |"GNSS/SYNCE/PTP/T1E1 input freq qualified" |
|....|........|.......|.......|................................................|
|24 |event |enable |0 |"GNSS/PTP input selected as time reference" |
|....|........|.......|.......|................................................|
|25 |event |enable |0 |"GNSS/SYNCE/PTP/T1E1 input sel as freq ref" |
|....|........|.......|.......|................................................|
|26 |minor |enable |0 |"T1E1 input Loss Of Signal (LOS)" |
|....|........|.......|.......|................................................|
|27 |minor |enable |0 |"T1E1 input Alarm Indication Signal (AIS)" |
|....|........|.......|.......|................................................|
|28 |minor |enable |0 |"T1E1 input Out Of Frame (OOF)" |
|....|........|.......|.......|................................................|
|29 |minor |enable |0 |"T1E1 input CRC error (CRC)" |
|....|........|.......|.......|................................................|
|30 |minor |enable |0 |"T1E1 input Bipolar Violation (BPV)" |
|....|........|.......|.......|................................................|
|32 |event |enable |0 |"SYNCE/T1E1 input SSM changed" |
|....|........|.......|.......|................................................|
|51 |minor |enable |0 |"Incompatible transport type" |

Chapter 3
|....|........|.......|.......|................................................|
|52 |minor |enable |0 |"PTP input lost" |
|....|........|.......|.......|................................................|
|53 |event |enable |0 |"PTP master switched" |
|....|........|.......|.......|................................................|
|54 |event |enable |0 |"PTP time/frequency input not traceable" |
|....|........|.......|.......|................................................|
|71 |minor |enable |0 |"PTP server near client limit on ETH2" |
|....|........|.......|.......|................................................|
|72 |event |enable |0 |"PTP client dropped from ETH2 client list" |
|....|........|.......|.......|................................................|
|73 |event |enable |0 |"PTP client added to ETH2 client list" |
|....|........|.......|.......|................................................|
|74 |event |enable |0 |"PTP client list on ETH2 refreshed" |
|....|........|.......|.......|................................................|
|75 |event |enable |0 |"PTP state changed to disabled on ETH2" |
|....|........|.......|.......|................................................|
|76 |event |enable |0 |"PTP state changed to listening on ETH2" |
|....|........|.......|.......|................................................|
|77 |event |enable |0 |"PTP state changed to master on ETH2" |
|....|........|.......|.......|................................................|
|78 |event |enable |0 |"PTP state changed to passive on ETH2" |
|....|........|.......|.......|................................................|
|91 |minor |enable |0 |"GNSS receiver communications failed" |
|....|........|.......|.......|................................................|
|92 |minor |enable |0 |"GNSS receiver not tracking satellite" |
|....|........|.......|.......|................................................|
|93 |minor |enable |0 |"GNSS signal low" |
|....|........|.......|.......|................................................|
|94 |major |enable |0 |"GNSS antenna voltage out of range" |
|....|........|.......|.......|................................................|
|95 |major |enable |0 |"GNSS antenna current out of range" |
|....|........|.......|.......|................................................|
|96 |minor |enable |0 |"GNSS antenna short-circuit" |
|....|........|.......|.......|................................................|
|97 |minor |enable |0 |"GNSS antenna open-circuit" |
|....|........|.......|.......|................................................|
|111 |minor |enable |0 |"Ethernet port link down" |
|....|........|.......|.......|................................................|
|112 |minor |enable |0 |"Excessive traffic on port ETH{1|2}" |
|....|........|.......|.......|................................................|
|113 |minor |enable |0 |"Unsupported SFP on ETH{1|2}" |
|....|........|.......|.......|................................................|
|114 |major |enable |0 |"SYNCE Ethernet Configuration Failure" |
|....|........|.......|.......|................................................|
|131 |critical|enable |0 |"Power out of range" |
|....|........|.......|.......|................................................|
|132 |critical|enable |0 |"Operational failure" |
|....|........|.......|.......|................................................|
|133 |major |enable |0 |"Battery(-48V)-A failure" |
|....|........|.......|.......|................................................|
|134 |major |enable |0 |"Battery(-48V)-B failure" |
|....|........|.......|.......|................................................|
|135 |critical|enable |0 |"FPGA failure" |
|....|........|.......|.......|................................................|
|136 |critical|enable |0 |"Flash partition failure" |
|....|........|.......|.......|................................................|
|137 |critical|enable |0 |"PLL synthesizer unlock" |
|....|........|.......|.......|................................................|

Chapter 3
|138 |critical|enable |0 |"Rubidium unlock" |

|....|........|.......|.......|................................................|
|139 |event |enable |0 |"Temperature out of range" |
|....|........|.......|.......|................................................|
|151 |critical|enable |0 |"Production configuration data error" |
|....|........|.......|.......|................................................|
|152 |event |enable |0 |"Timeline has been changed" |
|....|........|.......|.......|................................................|
|153 |event |enable |0 |"Phase has been aligned" |
|....|........|.......|.......|................................................|
|154 |event |enable |0 |"System log time has been updated" |
|....|........|.......|.......|................................................|
|155 |event |enable |0 |"System reboot" |
--------------------------------------------------------------------------------
Level : User, Config and Admin
set alarm-config
Use this command to provision the alarm state, alarm level, and reporting delay time
for the specified alarms. The reporting delay time is the amount of time from when
the alarm occurred to when it is reported. The delay parameter will delay the
reporting of an alarm by the configured amount.
Note: If an alarm condition is set and then cleared before the delay
expires, then the alarm will not be reported.
Command Syntax:
 To provision the state of the specified alarm number:

set alarm-config state {alarm [1 to 155] | all} {enable |
disable}
 To provision the level of the specified Alarm number:

set alarm-config level {alarm [1 to 155] | all}
{2 |3 | 4 | 5}
where:
2 - Critical
3 - Major
4 - Minor
5 - Event

Chapter 3
 To provision the reporting delay of the specified Alarm number in seconds:

set alarm-config delay {alarm [1 to 155] | all}[0 to 500000]
Note: Use “show alarm-config” command to view the max-alarm-id of

current TP 2300/2700 release.
Example 1:
To Disable alarm #32
TP2700> set alarm-config state alarm 32 disable
Example 2:
To set the level of alarm #32 to Error - major (3):
TP2700> set alarm-config level alarm 32 3
Example 3:
To set the reporting delay of alarm #32 to 5 seconds:
TP2700> set alarm-config delay alarm 32 5
Remarks: The severity level and delay of transitory events cannot be changed.
Level : Config and Admin

Chapter 3
show bridge-time
Displays the bridging time that is used to allow the frequency servo to coast through
short periods when the system does not have qualified reference. The bridging time
is in seconds.
Command Syntax:
show bridge-time
Example:
TP2700> show bridge-time
Response:
Bridging Time : 900
Remarks: If the system has not qualified a time or frequency reference within the
specified bridging time the system transitions into holdover mode of operation.
set bridge-time
Provisions the amount of time, in seconds, the system remains in bridging mode
before transitioning into the holdover mode of operation. The bridge-time applies to
both clock-timing loop and clock-frequency.
Note: Updates to the bridging-time value are only used at the start of
the next bridging event. Any changes to this value while the unit is in
bridging mode will not be implemented until the next bridging event.
Command Syntax:
set bridge-time <bridge-time-value>
Example:
TP2700> set bridge-time 1000

Chapter 3
show clock
Displays the system date, time, and leapseconds in several formats.
– Current system date and time

– Accumulated leapseconds between TAI and UTC time
– Pending leapseconds
Command Syntax:
show clock
Example:
TP2700> show clock
Response 1:
system time: 2012-11-30 22:35:24

Leap sec: 34
Leap pending: 0
Response 2:
After the system powered up, the date and time are entered or not entered by user,
but the system has never been locked to GNSS, the response will be as follows:
System time : 2013-05-09 16:11:17

Leap Seconds : 35
Leap pending : +0
set clock
Provisions the user-assigned Date, Time, and accumulated leapseconds.
Note: The user can only enter the date and time, and accumulated
leap seconds when the system has never acquired time from PTP or
GNSS (GPS or GLONASS) satellite.
Command Syntax:
 To set the Date and Time:

Chapter 3
set clock date-time <date-time>
Enter date and time in YYYY-MM-DD,HH:MM:SS format (UTC)

 To set the Accumulated leapseconds:
set clock leapseconds <value>
Note: If your GNSS is in GLONASS tracking mode, this command

also provides the user-provisioned leap second to GPS-GLONASS.
Example 1:
To set date to June 09 2013, and time to 10:35 PM and 24 sec.(UTC):
TP2700> set clock date-time 2013-06-09,22:35:24
Example 2:
To set the accumulated leapseconds to 29 seconds:
TP2700> set clock leapseconds 29

Chapter 3
set configuration
Use this command to backup the current configuration, restore the current
configuration from a backup copy, or set the current configuration to factory default
values.
Command Syntax:
 To set the current configuration to factory or default values:

set configuration {default | factory}
– Default preserves user logins and communication attributes, such as ip

addresses of MGMT port.
– Factory resets all attributes, including user logins.
Note: The system will automatically reboot after receiving either

the "set configuration default" or "set configuration
factory" commands
 To backup the current configuration to a remote server:

set configuration backup local
– Backup “local” saves the configuration to local non-volatile storage

immediately.
 To backup the current configuration to a remote server:
set configuration restore remote <filename> <server_ip>
<user-id>
– Backup “remote” saves the configuration to a SCP server. The user needs
to type the file path, IP address of the SCP server, user id for the data file
transfer and press Enter. The system will prompt for the server password.
 To restore the current configuration from a backed-up file on a server:
set configuration restore remote <filename> <server_ip>
<user-id>
– Restore “remote” saves the system configuration from a stored file on the
SCP server back to the TP 2300/2700. The user needs to type the file
path, IP address of the SCP server, user id for the data file transfer and
press Enter. The system will prompt for the server password.
Example 1:
To backup the current configuration to non-volatile storage:
set configuration backup local
Example 2:

Chapter 3
To set the configuration to default levels (will not overwrite user login info or current IP
address of MGMT port):
TP2700>set configuration default
Example 3:
To backup the configuration to a remote SCP server with an IP address of 192.168.7.63,

user name of “maynard”, password of “123456789”, and file path of “/tmp/config”:
TP2700>set configuration backup remote /tmp/config

192.168.7.63 maynard <ENTER>
Press ENTER.
The system will prompt for the server password.
Example 4:
To restore a configuration file with file path of “/tmp/config” from a remote SCP server with an
IP address of 192.168.7.63, user name of “maynard”, and password of “123456789”:
TP2700>set configuration restore remote /tmp/config

192.168.7.63 maynard
Press ENTER.
The system will prompt for the server password.
Remarks :
 The “default” setting preserves user logins and communication attributes, such
as IP address of MGMT port.
 The “factory” setting resets all attributes, including user logins.
 Installed licenses are not affected by setting the configuration to “default” or
“factory” levels.
Level : Admin

Chapter 3
show eia-232
This command displays the serial port’s operating parameters: baud rate, parity,
word length, and stop bits.
Command Syntax:
show eia-232
Example:
TP2700> show eia-232
Response:
Baud rate : 57600

Data length : 8
Stop bit : 1
Parity : 0
Flow control : none
Remarks: The system's serial interface is fixed at 57.6K, 8, 1, 0; there is no

handshaking. There is no associated Set command.

Chapter 3
show ethernet
The show ethernet command displays the packet service ports auto-negotiation
state and speed for all Ethernet service ports. It also displays a hexidecimal code to
describe any clock faults.
Command Syntax:
show ethernet { config | status }
Example 1:
TP2700> show ethernet config
Response 1a:
-----------------------------------------------------------
| Port | Auto-neg | Speed | Active-connector |
|--------|-------------|-----------|----------------------|
| eth1 | enable | all | r1- rj45 |
|........|.............|...........|......................|
| eth2 | disable | 1000 | s2- sfp |
|.........................................................
Response 1b:
----------------------------------------------
|Port| Auto-neg | Speed | Active-connector|
|----|------------|--------|-----------------|
|eth1| enable | all | r1-rj45 |
|----|------------|--------|-----------------|
----------------------------------------------
Example 2:
TP2700> show ethernet status
Response 2:
ETH1 current speed : 1000M

ETH1 1000BT clock : slave
ETH2 current speed : 100M

ETH2 1000BT clock : fault (0x15)

Chapter 3
Note: The 1000BT clock status is only valid for 1000BT, and reports
the PHY status. It is not applicable if the port is unconnected, in
100BT mode, or the SFP is selected. The hex number provides more
detail of the 1000BT clock status and the value can be decoded by
using Table 3-1.
Status results only have meaning for 1000M electrical SFPs.
Table 3-1. Ethernet Status - Hex Error Code Descriptions
Bit Description
7 Master / Slave configuration fault
6 Master / Slave configuration : (1 = local link is master, 0 = local link slave)
5 Local Rx status : (1 = local Rx is OK, 0 = local Rc is not ok)
4 Remote Rx status : (1 = remote status is OK, 0 = remote status is not OK)
3 Link partner is capable of full duplex (1 = full duplex, 0 = no full duplex)
2 Link partner is capable of half duplex (1 = half duplex, 0 = no half duplex)
1 Reserved
0 Reserved
set ethernet
Use this command to configure the Ethernet ports: the port state, the connector
type, the auto-negotiation state and speed, and the Ethernet signal type. When
Ethernet auto-negotiation is enabled for the ETH1 or ETH2 packet service port, the
TP 2300/2700 will advertise connection speeds of 100M, 1000M, or 100/1000M for
that service port. The advertised connection speed will apply to the active connector
(RJ45 or SFP) of the specified port. Users can specify a connection speed for a
port, 100 MB, 1000 MB, or All (100/1000M), to configure speed used by
auto-negotiation. If auto negotiation is disabled, the Ethernet connection speed will
be forced to 100M for a RJ45 active connector and to 1000M for an Optical SFP
active connector.

Chapter 3
Note: Only 1000M is supported for optical SFPs. Electrical SFPs are
not supported.
Command Syntax:
 To provision the connector type, RJ45 (R1) or SFP (S1), for ETH1 packet service port:
set ethernet active-connector eth1 {r1-rj45 | s1-sfp}
 To provision the connector type, RJ45 (R2) or SFP (S2), for ETH2 packet service port:
set ethernet active-connector eth2 {r2-rj45 | s2-sfp}
 To set the Ethernet Auto Negotiation state for the specified packet service port:
set ethernet auto-neg state {eth1 | eth2} {enable | disable}
 To set the advertised speed for Ethernet Auto Negotiation:

set ethernet auto-neg speed {eth1 | eth2} {100m | 1000m |
all}
Note: If the auto negotiation state is DISABLE for a packet service

port, the Ethernet connection speed will be forced to 100M if the
active connector is RJ45, and to 1000M if the active connector is
Optical SFP.
Example 1:
To set the advertised speed for Ethernet auto negotiation speed to "all" (100/1000M)
for ETH1 port:
TP2700>set ethernet auto-neg speed eth1 all
Example 2:
To set the Ethernet auto negotiation state to ENABLE for ETH2:
TP2700>set ethernet auto-neg state eth2 enable
Example 3:
To set the Ethernet connector type to RJ45 for ETH2:
TP2700>set ethernet active-connector eth2 r2-rj45

Chapter 3
show firewall
This command displays the firewall configuration.
Command Syntax:
show firewall
Example:
TP2700> show firewall
Response:
TELNET Firewall : allow

SSH Firewall : allow
FTP Firewall : block
ICMP Firewall : allow
SNMP Firewall : allow
HTTPS Firewall : block
set firewall
Use this command to configure the system’s Ethernet management port firewall.
The firewall can control Telnet, SSH, FTP, SNMP, ICMP, and HTTPS on the
Ethernet management port. The HTTPS firewall controls both HTTPS and HTTP.
Command Syntax:
set firewall mgmt telnet {allow|block}

set firewall mgmt ssh {allow|block}
set firewall mgmt ftp {allow|block}
set firewall mgmt snmp {allow|block}
set firewall mgmt icmp {allow|block}
set firewall mgmt https {allow|block}
Example:
set firewall mgmt telnet allow
Remarks: Telnet and FTP are disabled by default on Ethernet management port.
On Ethernet sync service ports, all ports are blocked except ICMP and PTP. The
firewall configuration for packet service ports cannot be changed.
Level : Admin

Chapter 3
show gnss
This command displays the GNSS port state, position (latitude, longitude, height),
elevation mask value (positioning filter), mode of operation (manual or automatic),
and track-mode selection, GPS or GLONASS, or GPS+GLONASS. It also displays
information for all satellite vehicles being tracked: vehicle number, status, noise
ratio, satellite elevation, satellite azimuth.
Note: “OK” for status means the satellite is included in the current fix
calculation because the receiver deems that its signal is good enough
to produce a reliable fix.
“RAIM Fault” for status means the satellite is excluded from the
current fix calculation because the receiver deems that its signal is
not good enough to produce a reliable fix. RAIM = Receiver
autonomous integrity monitoring.
Command Syntax:
 To show the GNSS configuration:

show gnss config
 To show the GNSS status:

show gnss status
 To show the GNSS antenna current qualification:

show gnss antenna-current qualification
Example 1:
TP2700>show gnss config
Response 1 :
GNSS Configuration
State : enable
PosMode : auto
Track-Mode : gps
Mask : 10
Antenna Delay : 0
GNSS manual position

Chapter 3
Latitude : N37:22:43.425
Longitude : W121:55:34.815
Height : 13.7
Example 2:
TP2700>show gnss status
Response 2 :
GNSS Status:
Current Status : ok
Current Reference Status : selected
Current Position Status : positionHold
Current Antenna Position:
Latitude : N37:22:42.98
Longitude : W121:55:34.87
Height : 14.40
Current GNSS Satellite View:
--------------------------------------------------------------------
|Index |No |SNR |Status |Azimuth |Elevation |Sat Type |
|------|-----|-----|----------|----------|------------|------------|
|1 |2 |50 |ok |49 |72 |gps ||
|......|.....|.....|..........|..........|............|............|
|2 |4 |44 |ok |47 |22 |gps |
|......|.....|.....|..........|..........|............|............|
|3 |5 |48 |ok |146 |29 |gps |
|......|.....|.....|..........|..........|............|............|
|4 |10 |48 |ok |76 |31 |gps |
|......|.....|.....|..........|..........|............|............|
|5 |12 |52 |ok |333 |88 |gps |
|......|.....|.....|..........|..........|............|............|
|6 |24 |44 |ok |202 |19 |gps |
|......|.....|.....|..........|..........|............|............|
|7 |25 |49 |ok |314 |47 |gps |
|......|.....|.....|..........|..........|............|............|
|8 |29 |48 |ok |284 |27 |gps |
|......|.....|.....|..........|..........|............|............|
|9 |35 |30 |ok |211 |41 |gps |
|......|.....|.....|..........|..........|............|............|
|10 |47 |31 |ok |250 |14 |gps |
--------------------------------------------------------------------

Chapter 3
Example 3:
TP2700>show gnss antenna-current qualification
Response 3:
Antenna-current qualification : disable

Chapter 3
set gnss
Use this command to configure the GNSS port state, mask, position mode, and the
position configuration if the position mode is set as manual. It is also used to select
the track-mode as GPS, GLONASS , or GPS+GLONASS (if the concurrent GPS &
GLONASS feature is enabled by a license):
Command Syntax:
 To change GNSS state:

set gnss state {enable | disable}
 To select the GNSS track mode:

set gnss track-mode {gps | glonass | gps-glonass}
Note: The TimeProvider 2300/2700 requires a license to enable

access to the "gps-glonass" concurrent GPS and GLONASS option.
This option supports the use of GPS and GLONASS satellites
concurrently instead of either GPS or GLONASS.
 To change the GNSS position mode:

set gnss posmode auto
or
set gnss posmode manual latitude <lat-value> longitude
<lon-value> height <height-value>
– Position can only be provisioned manually when GNSS posmode is

“manual”.
Where
Latitude is in the format N|Sddd:mm:ss.sss, for example:

N37:22:45.123
S48:33:67.456
Longitude is in the format E|Wddd:mm:ss.sss, for example:
W121:55:36.123
E157:33:47.456
Height is in meters with one digit after the decimal point, for
example:
17.5
Note: Microsemi recommends that the Auto mode be used. Any error
in the manually-specified system position will generate timing errors.
See Table B-2 for default values and ranges.
 To set the GNSS mask value

Chapter 3
set gnss mask <mask-value>
The mask value is used to filter out signals from satellites below the specified angle
of elevation above the horizon
 To set the GNSS cable-delay value

set gnss cable-delay <delay-value>
The cable-delay value is used to compensate for cable propagation delays. It is

important to set the cable-delay value to ensure high accuracy timing by reducing
the effect of these delays on system timing. See Table B-25 for cable delay values.
The delay values shown are in nanoseconds, and correspond to the cable kit being
used in its entirety without modification. The values assume that a splitter is not
used. Splitters are not recommended.
 To enable or disable the antenna’s current qualification of the GNSS 1PPS signal
set gnss antenna-current qualification {enable | disable}
If antenna-current qualification is enabled, then the system will only qualify the
GNSS signal if there is sufficient antenna current to not generate the open-circuit
alarm. If antenna-current qualification is disabled, then the GNSS signal can be
qualified regardless of an open-circuit alarm.
Example 1:
To set GNSS position mode to auto:
TP2700>set gnss posmode auto
Example 2:
To manually set the GNSS with a system position of latitude of N37:22:45.123,

longitude of W121:55:36.123, and a height 17.5 meters
TP2700>set gnss posmode manual latitude N37:22:45.123

longitude W121:55:36.123 height 17.5
Example 3:
To enable GNSS on the GNSS port:
TP2700>set gnss state enable
Example 4:
To set the GNSS mask to a value of 25 degrees:
TP2700>set gnss mask 25
Example 5:

Chapter 3
To set the GNSS cable delay to a value of 220 nanoseconds:
TP2700>set gnss cable-delay 220
Example 6:
To enable the antenna’s current qualification of the GNSS 1PPS signal:
TP2700>set gnss antenna-current qualification enable
Restrictions: The system must have the GNSS posmode provisioned as “manual”
before you can successfully provision the position manually.

Chapter 3
show hardware-status
This command displays the status of the specified hardware.
Command Syntax:
show hardware-status
Example:
TP2700> show hardware-status
Response:
-48V-A : ok (DC only)

-48V-B : ok (DC only)
+1.2V : 1.21V
+3.3V : 1.83V
+2.5V : 2.51V
+5.0V : 5.01V
-5.0V : -5V
+1.5V : 1.5V
GPS Power : 5.04V
GPS Current : 37mA
GPS Antenna : ok
FPGA : ok
Temperature : 53 C

Chapter 3
history
This command shows the command history for the current session.
Command Syntax:
history
Example:
tp2700> history
Response:
0 2013-06-10 00:11:28 show eth-status

1 2013-06-10 00:12:24 show event
2 2013-06-10 00:13:15 show firewall
3 2013-06-10 00:16:02 set firewall ssh
4 2013-06-10 00:16:31 generate message
5 2013-06-10 00:17:07 show gnss
6 2013-06-10 00:19:59 set gnss posmode auto
7 2013-06-10 00:21:49 set gnss mask 10
8 2013-06-10 00:22:40 set gnss cable-delay 1
9 2013-06-10 00:22:48 set gnss cable-delay 0
10 2013-06-10 00:23:47 show hardware-status
11 2013-06-10 00:24:14 show hardware-status
12 2013-06-10 00:25:19 history

Chapter 3
show hostname
This command displays the host name for the TimeProvider 2300/2700.
Command Syntax:
show hostname
Example:
tp2700> show hostname
Response:
Host name : Timeprovider
set hostname
This command sets the host name for the TimeProvider 2300/2700. Hostname can
contain up to 20 characters.
Command Syntax:
set hostname <hostname_string>
Example:
To set the hostname to “EdgeMaster05” 
tp2700> set hostname EdgeMaster05

Chapter 3
show image
This command displays the firmware image and the firmware version in the system.
The backup image is the non-active image.
Command Syntax:
show image
Example:
tp2700> show image
Response:
SYSTEM IMAGE DETAILS
Active image : 2 1.0.3

Backup image : 1 1.0.2
Next boot image : 2
set image
Use this command to provision the firmware image from which to boot. The backup
image is the non-active image.
Note: Each image has its own set of configuration data. When Image
1 is set as the boot image, the configuration data for Image 1 is
applied when the TP 2300/2700 is rebooted. When Image 2 is set as
the boot image, the configuration data for Image 2 is applied when the
TP 2300/2700 is rebooted.
A firmware upgrade is applied to the backup image, and the backup

image is set to be the next boot image. The TP 2300/2700 copies the
currently running configuration data to the data used with the next
boot. Therefore, the configuration should be the same after rebooting,
except for changes due to differences in supported configuration
items between firmware revisions.
Command Syntax:
set image {1 | 2}
Example 1:

Chapter 3
To set the system to boot from image 1:
TP2700> set image 1
Example 2:
To set the system to boot from image 2:
TP2700> set image 2
Remark: The system must be rebooted to implement the boot image.

Chapter 3
show input
This command displays the current configuration or status for input signals for the
T1/E1 port. The values displayed with this command will be applied to the T1/E1
port only when the IO-direction of the port is configured as an Input with the set
port-control t1e1 io input command.
Command Syntax:
show input config <port-name>
show input status <port-name>
Example 1:
TP2700> show input config t1e1
Response 1a:
Input config
-------------------------------------------------|
| signal | Frame Type | CRC | ssmbit |
|------------|-------------|---------|-----------|
| e1 input | cas | enable | 6 |
|............|.............|.........|...........|
| t1 input | esf | enable | na |
|................................................|
Port config
----------------------------------------------
| Port | State | Io dir | Signal/format|
|--------|---------|----------|--------------|
| t1e1 | enable | input | e1 |
|........|.........|..........|..............|
Response 1b:
Input config
-------------------------------------------------|
| signal | Frame Type | CRC | ssmbit |
|------------|-------------|---------|-----------|
| e1 input | cas | enable | 6 |
|............|.............|.........|...........|
| t1 input | freq1544khz| na | na |
|.................................................|

Chapter 3
Port config
----------------------------------------------
| Port | State | Io dir | Signal/format|
|--------|---------|----------|--------------|
| t1e1 | enable | output | e1 |
|........|.........|..........|..............|
Example 2:
TP2700> show input status t1e1
Response 2a:
------------------------------------------------------------------------------
|Port |input status|ssm |los |ais |oof |bpv |crc |
|---------|------------|--------|--------|--------|--------|--------|--------|
|t1 input |fault |na |fault |ok |ok |ok |na |
------------------------------------------------------------------------------
Response 2b:
Status: Input port is disabled
Response 2c:
Status: Port is configured as output
Table 3-2. Show Input Status - Field Descriptions
Field Description Details
Status Shows current port status OK - state of the port is configured as “ENABLE”, port
I/O direction is set as input, and signal received at this
port is valid.
Fault - state of the port is configured as “ENABLE”,

port io direction is set as input, but the signal received
at this port is invalid.
SSM Shows the received SSM 0xFF represents not available or not applicable.
value for the input port.
LOS Loss of signal  Fault - Loss of signal

 OK - Normal signal
 NA - not applicable, when port state is “DISABLE”
or port is set as an output

Chapter 3
Table 3-2. Show Input Status - Field Descriptions (Continued)
Field Description Details
AIS Alarm indicator signal  Fault - Alarm indicator signal has been received
 OK - No alarm indicator signal
 NA - not applicable, when port state is
“DISABLE”, port is set as an output, or configured
as unframed signal
OOF Out of frame alarm  Fault - OOF alarm has been generated
 OK - No OOF alarm for the port
as unframed signal
BPV Bipolar violation alarm  Fault - BPV alarm has been generated
 OK - No BPV alarm for the port
as unframed signal
CRC Cyclic redundancy check  Fault - CRC error detected

error  OK - No CRC error for the port
as unframed and DS1 D4/ESF signal
Remarks:
– Line code, SSMBIT and CRC do not apply to freq2048khz, and

freq1544khz.
– CRC for T1 input is not user-configurable. It is always ENABLE for ESF,
and does not apply for D4.
– SSMBIT only applies to E1 frame signal CCS or CAS.
– Use the "show ref" command to display SSM state information.
set input
When the T1/E1 port is configured as an input port, use this command to provision
all other configurable parameters for the input signal on the T1/E1 port:
 Framing Type
– CCS, CAS, or freq 2048KHz for E1

Chapter 3
– D4, ESF, or freq 1544KHz for T1

 CRC state for E1
 SSM Bit position for E1
All the configurations provisioned by this command apply to the T1/E1 input port
only when the IO-direction of the port is configured as an Input with the set
port-control t1e1 io input command.
Command Syntax:
 To set the frametype, CRC, and SSM bit position for E1 Input:
set input e1 frametype t1e1 {ccs | cas | freq2048kz}
set input e1 crc t1e1 {enable | disable}
set input e1 ssmbit t1e1 {4 | 5 | 6 | 7 | 8}
 To set the frametype for T1 Input:

set input t1 frametype t1e1 {d4 | esf | freq1544kz}
Example 1:
To provision the T1/E1 port for E1 input with CAS frametype, CRC enabled, with
SSM bit position of 6:
TP2700> set input e1 frametype t1e1 cas
TP2700> set input e1 crc t1e1 enable
TP2700> set input e1 ssmbit t1e1 6
Example 2:
To provision the T1/E1 port for T1 input with D4 frametype:
TP2700> set input t1 frametype t1e1 d4
Remarks:
– The port state, IO direction (input or output) and signal type (e1 or t1) are
configured by set port-control command.
– No user provisioning for line code when the port is set as input by set
port-control command. It is hardcoded as HDB3 for E1 and B8ZS for
T1 (zs=enable, i.e., zero suppression is on), and in this way, the input port
will accepts both HDB3 (B8ZS for t1) and AMI code.
– SSM state is configured by set ref command.

Chapter 3
– No CRC required for framing types of D4, freq2048khz, and freq1544khz.

– No user provisioning CRC for ESF. It is hardcoded as ENABLE.

Chapter 3
show inventory
This command displays the following inventory information of the systems.
 Description of the product

 Part number
 CLEI number
 Serial number
 Software version
 Hardware version
 GNSS Device ID, Device type and firmware revision
 FPGA version
 Asset Number
Command Syntax:
show inventory
Example:
TP2700> show inventory
Response 1:
General Inventory Info
Product Model : TP2700-DC-OCXO

Part Number : 090-50201-111
CLEI Number : C000000
Serial Number : SYM31455
Software version : 1.0.3
Hardware version : A
GNSS Version : CSM23,0179, 0x02
FPGA Version : 0x14
Asset Number : A000000

Chapter 3
set inventory
Use this command to provision the system's user-assigned asset value information.
Command Syntax:
set inventory asset <asset-value>
Example:
To set the inventory asset to a value of "tcb121"
set inventory asset tcb121

Chapter 3
show ip
This command displays the Host, Mask, and Gateway IP addresses for Ethernet
interfaces. It also indicates if DHCP is enabled and if the port is enabled.
Command Syntax:
 To show the configuration of the Ethernet interface (some settings will only be
implemented after restarting the IP interface):
show ip config {mgmt | eth1 | eth2}
 To show the current status of the Ethernet interfaces for the specified module:
show ip status {mgmt | eth1 | eth2}
Note: Packet and byte counts do not include most PTP and NTP
packets.
Example 1:
To display the configuration of the Ethernet interfaces for the MGMT module:
tp2700> show ip config mgmt
Response 1:
MGMT PORT PARAMETERS

IP mode : dhcp
IP state : enable
Static mode Parameters

IP address : 192.168.0.100
IP mask : 255.255.255.0
IP gateway : 0.0.0.0
DNS Domain : 192.168.0.100
DNS nameserver1 : 0.0.0.0
Example 2:
To display the configuration of the Ethernet interfaces for the ETH1 port:
tp2700> show ip config eth1
Response 2:
ETH1 PORT PARAMETERS

IP state : enable

Chapter 3

IP address : 192.168.9.44
IP mask : 255.255.255.0
Example 3:
To display the status of the Ethernet interfaces for the Ethernet management port:
tp2700> show ip status mgmt
Response 3:
mgmt0 Link encap:Ethernet HWaddr 00:B0:AE:00:00:05

inet addr:192.168.5.14 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70867 errors:0 dropped:0 overruns:0 frame:0
TX packets:1986 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4511319 (4.3 MiB) TX bytes:162895 (159.0 KiB)
Interrupt:21 Base address:0xe000
Note: See Table 3-3 for descriptions of IP status fields.
Example 4:
To display the status of the Ethernet interfaces for the ETH2 port
tp2700> show ip status eth2
Response 4:
eth2 Link encap:Ethernet HWaddr 00:B0:AE:01:32:4A

inet addr:192.168.2.11 Bcast:192.168.2.255
Mask:255.255.255.0
RX bytes:360 (360.0 B) TX bytes:1920 (1.8 KiB)
Interrupt:128

Chapter 3
Table 3-3. IP Status Field Descriptions
IP Status Field Description
Link encap: This represents the frame type associated with this interface.
On a normal ethernet interface you'll see "Ethernet" as the
link encapsulation method.
HWaddr:  This represents the hardware address of the ethernet

interface, also commonly known as ‘MAC address’.
 MAC address consists of 6 octets (48 bits) and is divided
in two parts. First three octets (00:0C:29) represents the
manufacturer id and the last three octets (40:93:9C)
represents the serial number assigned to the device by
the manufacturer.
Inet addr: IPv4 address assigned to the interface.
Bcast: Broadcast address of the network associated with the

interface.
Mask: Network mask associated with the interface.
UP This flag indicates that the network interface is configured to

be enabled.
BROADCAST Indicates that the interface is configured to handle broadcast

packets.
This is important for obtaining the IP address via DHCP
server.
RUNNING Indicates that the network interface is operational and is

ready to accept the data.
MULTICAST Indicates that the interface is configured to handle multicast

packets.
MTU  The maximum transmission unit for which the interface is

configured.
 MTU is a link layer characteristic which provides limit on
the size of the Ethernet frame. If IP has a datagram to
send and the size of the datagram is larger than the link
layer’s MTU then IP layer breaks the datagram into
smaller pieces (fragments), so that each is smaller than
the MTU.
 1500 is the default value for all ethernet devices.
Metric: Interface metric is used to compute the cost of a route. It tells

the OS which interface a packet should be forwarded to,
when multiple interfaces could be used to reach the packet’s
destination.
RX packets: The number of packets received via the interface.

Chapter 3
Table 3-3. IP Status Field Descriptions (Continued)
IP Status Field Description
RX Errors: The number of damaged packets received.
RX Dropped: The number of dropped packets due to reception errors.
RX Overruns: The number of received packets that experienced data

overruns.
RX Frame: The number received packets that experienced frame errors.
TX packets: The number of packets transmitted via the interface.
TX Errors: The number of packets that experienced transmission error.
TX Dropped: The number of dropped transmitted packets due to

transmission errors.
TX Overruns: The number of transmitted packets that experienced data

overruns.
TX Carrier: The number received packets that experienced loss of

carriers.
TX Collisions: The number of transmitted packets that experienced Ethernet

collisions. A nonzero value of this field indicates possibility of
network congestion.
Txqueuelen: The field provides the information about the configured length
of transmission queue.
RX bytes: The total bytes received over this interface.
TX bytes: The total bytes transmitted over this interface.
Interrupt This field provides the information about the Interface

Request (IRQ) value assigned to this interface.
Base address: The I/O base address associated with this interface.
set ip
Use this command to provision the Host, Mask, and Gateway IPv4 addresses for
the Ethernet management port and ETH1 and ETH2 ports. It also supports the DNS
client function by provisioning the DNS server,
The IP addresses for the MGMT, ETH1 and ETH2 ports must be on different
networks/subnets.
Note: To configure a VLAN, use the command set vlan to provision

the IP addresses.

Chapter 3
The special value of 0.0.0.0 should be used for the gateway value if a gateway
router is not required. Support for IPv6 addresses will be added in a future release.
Command Syntax:
 To provision the state of the IPv4 Ethernet interfaces for the specified port:
set ip state {mgmt | eth1 | eth2} ipv4 [enable | disable |
restart]
 To set the IPv4 address, mask and gateway of the Ethernet interfaces for the
specified port:
set ip ip-address {mgmt | eth1 | eth2} ipv4 address
<addrv4_value> netmask <maskv4_value> gateway
<gatewayv4_value>
Note: For the configuration change to take effect, the interface must
be restarted with the set ip state {mgmt | eth2 | eth2} ipv4
restart command.
 To provision the IPv4 address mode on the Ethernet management port as DHCP
or STATIC:
set ip address-mode mgmt ipv4 {dhcp | static}
Note: For the configuration change to take effect, the interface must
be restarted with the set ip state mgmt ipv4 restart command.
 To provision the DNS servers and domain for support of the DNS client function
in Ethernet management port:
set ip mgmt dns nameserver1 { nameserver_ip_address }
nameserver2 {nameserver_ip_address } domain { domain_name }
Note: FQDN (fully qualified domain name) is supported for the ping
command.
Example 1:
To restart the Ethernet management interface after the IP address or address-mode

has changed:
tp2700> set ip state mgmt ipv4 restart
Example 2:
To enable the IP interface for packet service port ETH1:

Chapter 3
tp2700> set ip state eth1 ipv4 enable
Example 3:
To set the IPv4 address for the Ethernet management packet service port ETH1 to
192.168.2.11, the mask to 255.255.255.0, and the gateway 0.0.0.0:
tp2700> set ip ip-address eth1 ipv4 address 192.168.2.11 netmask

255.255.255.0
gateway 0.0.0.0
tp2700> set ip state eth1 ipv4 restart
Note: PTP will be restarted after the IPv4 interface is restarted for the
packet service ports ETH1 or ETH2.

Chapter 3
show led
This command displays the LED status for each LED on the front panel. See Table
2-8 for LED descriptions.
Command Syntax:
show led
Example 1:
TP2700> show led
Response 1:
------------------------------
|LED ID |LED Status |
|------------|---------------|
|power |green |
|............|...............|
|powerA |green |
|............|...............|
|powerB |off |
|............|...............|
|gnss |red |
|............|...............|
|alarm |amber |
|............|...............|
|Clock |green |
------------------------------

Chapter 3
show license
Use this command to display the licensed features.
Command Syntax:
show license
Example 1:
TP2700> show license
Response 1:
................................................................................|
|No. | Features | Description |
|....|...........................|..............................................|
| 1 | ptp-input | Precision Time Protocol Input |
|....|...........................|..............................................|
| 2 | gps-glonass | Concurrent GPS + GLONASS Satellite Tracking |
|....|...........................|..............................................|
| 3 | t1-e1 | TDM (T1/E1) with Input and Output |
|....|...........................|..............................................|
| 4 | ptp-default-profile | PTP Default Profile |
|....|...........................|..............................................|
| 5 | ptp-client-capacity-64 | PTP Master with max capacity of 64 clients |
|....|...........................|..............................................|
| 6 | pps-tod | 1PPS+TOD (One Pulse Per Sec with Time Of Day)|
|....|...........................|..............................................|
| 7 | syncE | Synchronous Ethernet Input and Output |
|....|...........................|..............................................|
| 8 | ptp-master | PTP Master functionality |
|....|...........................|..............................................|
Note: A license key is required to enable licensed features.

Please contact your local sales representative or Microsemi Technical
Support at 1-888-367-7966 (USA) or 1-408-428-7907 for additional
information.
set license
Use this command to enter the 40-character license key for new features, and to
delete features. The license is associated with the serial number of the system.
When a license key is added, all the states of that license’s features will be enabled.

Chapter 3
Command Syntax:
 To enter a license key for new features:

set license add
The TP 2300/2700 will prompt for the license key and the user needs to enter the
40-character key string.
 To remove an installed feature license:

set license delete
The TP 2300/2700 will respond with all installed features that can be deleted. The
user chooses from the list for the feature to delete
Note: When a feature license is deleted, the feature will still function
until the next reboot.
Reinstalling the license key with the “set license add” command will
enable the feature again.
Example 1:
To add a feature with a license key value of

“ABCDEFGHIJ1234567890KLMNOPQRST0987654321”:
TP2700> set license add
The TP 2300/2700 will prompt for the license key:
License key: ABCDEFGHIJ1234567890KLMNOPQRST0987654321
Note: Feature licenses require a valid key. The key shown in

this example is intended to illustrate the concept.
Example 2:
To delete the PTP_INPUT license:
TP2700> set license delete
The TP 2300/2700 will prompt the user with a list of features that can be deleted.

Chapter 3
ptp-input - Precision Time Protocol Input

t1-e1 - TDM (T1/E1) with Input and Output
ptp-client-capacity-64 - PTP Master with max capacity of 64
clients
syncE - Synchronous Ethernet Input and
Output
ptp-master - PTP Master functionality
Enter License Feature to be deleted:
Select the feature to be deleted from the list and press Enter. The TP 2300/2700
will prompt the user to verify that the license is to be deleted.
Are you sure you want to delete this license? (Yes | No)
Select “Yes” and press Enter.
Level : Admin

Chapter 3
show log
This command displays the specified log file from the local storage.
When showing the log content, the Index parameter selects one of the seven
rotated log files. The Head parameter, along with the count value, displays the
specified number of events from the beginning of the file. The Tail parameter, along
with the count value, displays the specified number of events from the end of the
file. If the Index is not specified or set to zero, the current log file is displayed. If
neither Head nor Tail parameter is issued, the 20 most recent entries are displayed.
The log files are:
 Alarm-Event Log
 Command Log
 Security Log
Command Syntax:
 To display a log:
show log {alarm-event | command | security}
[<index-value>][{head|tail} <number-of-lines>]
Note: If a log seems to disappear then it has probably rotated. If so,

use the index to specify the older log entries to be viewed.
 To display the state of diagnostic logging:

show log diag state
Example 1:
To display the first 5 entries of the alarm-event log (5 lines from the head of current
log):
TP2700> show log alarm-event head 5
Response 1:
2012-11-30 00:00:10 TIMEPROVIDER alarmid: 028,000,MINOR,

GNSS receiver not tracking satellite
2012-11-30 00:00:34 TIMEPROVIDER alarmid: 009,000,MAJOR,

GNSS input poor quality

GNSS receiver communications failed

Chapter 3

Management port link down
2012-11-30 00:01:09 TIMEPROVIDER alarmid: 011,000,MAJOR*,

GPS antenna current out of range (6mA)
*-- escalated alarm level
Example 2:
To display the last 10 entries of the alarm-event log (10 lines from the tail of current
log):
TP2700> show log alarm-event tail 10
Response 2:
2012-12-29 00:00:10 TIMEPROVIDER alarmid: 006,000,EVENT,

time Entered bridging state

freq Entered bridging state

GNSS input time qualified

GNSS input freq qualified
. . . . . .
Example 3:
To display the last 10 entries of the alarm-event log (10 lines from the tail of current
log):
TP2700> show log diag state
Response 3:
Diagnostics Logging State : disable

Config and Admin for show log diag state
set log
Use this command to provision the state of diagnostic messages sent to debug log.

Chapter 3
Command Syntax:
set log diag state {enable | disable}
Example 1:
To enable the diagnostic state of messages sent to debug log:
TP2700> set log diag state enable

Chapter 3
show log-config
Use this command to display the configuration for log size and remote-syslog.
Command Syntax:
 To show configuration of the log size:

show log-config size {alarm-event | command | security}
 To show configuration of the remote-syslog:

show log-config remote-syslog
Example 1:
To display size of the alarm log:
TP2700> show log-config size alarm-event
Response 1:
Log size of alarm-event log is : 100 kilobytes
Example 2:
To display the configuration of the remote-syslog:
TP2700> show log-config remote-syslog
Response 2:
Remote-syslog config:
State : disable
Remote Address : 0.0.0.0
set log-config
Use this command to provision the specified log file buffer size, the maximum
number of kilobytes to be stored in the file before it is rotated, and to configure a
remote syslog server to receive log messages from the TimeProvider 2700.
Command Syntax:
 To configure the size of the log:

Chapter 3
set log-config size {alarm-event | command | security}

<size-value>
 To enable the remote-syslog:

set log-config remote-syslog enable <host-addr>
 To disable the remote-syslog:

set log-config remote-syslog disable
Example 1:
To set the size of the alarm-event log to 100 kilobytes:
TP2700> set log-config size alarm-event 100
Example 2:
To set the size of the command log to 80 kilobytes:
TP2700> set log-config size command 80
Example 3:
To ensable the remote-syslog with host address 192.168.5.141:
TP2700> set log-config remote-syslog enable 192.168.5.141
Example e:
To disable the remote-syslog:
TP2700> set log-config remote-syslog disable
Remarks: Provisioning a log file size to zero disables the logging of that type of
data. See for Table B-29 default log file sizes and ranges.

Chapter 3
logout
This command terminates the current user connection.
Command Syntax:
logout
Example:
TP2700> logout

Chapter 3
show output
This command displays the current configuration or status for output signals for the
T1/E1 port and the PPS offset on the PPS/10M output port. The provisioning
displayed with the show output config t1e1 command will apply to the T1/E1
port only when the IO-direction of the port is configured as OUTPUT with the set
port-control t1e1 io output command.
Command Syntax:
 To display the configuration of the T1/E1 output port or 10MHz/PPS port:

show output config {t1e1 | pps10m}
 To display the status of the T1/E1 output port:

show output status t1e1
 To display the status of the TOD port:

show output status tod
Example 1:‘
TP2700> show output config t1e1
Response 1a:
Output Config
--------------------------------------------------------------
|Signal |FrameType |CRC |SSMBit |zero suppression|
|------------|------------|--------|--------|----------------|
|e1 output |ccs |enable |all |off |
|............|............|........|........|................|
|t1 output |esf |na |na |na |
--------------------------------------------------------------
Port Config
--------------------------------------------------------
|Port |state |io dir |Signal / Format |
|------------|------------|------------|----------------|
|t1e1 |enable |output |e1 |
--------------------------------------------------------
Response 1b:
Output Config

Chapter 3
--------------------------------------------------------------
|------------|------------|--------|--------|----------------|
|............|............|........|........|................|
--------------------------------------------------------------
Port Config
--------------------------------------------------------
|Port |state |io dir |Signal /Format |
|------------|------------|------------|---------------|
|t1e1 |enable |output |t1 |
--------------------------------------------------------
Example 2:‘
TP2700> show output config pps10m
Response 2a:
1PPS output phase offset compensation: 0 ns
Port config
--------------------------------------
| Port | state | Signal/format |
|---------|---------|----------------|
| pps10m | enable | pps |
|.........|.........|................|
Response 2b:
Port config
--------------------------------------
|---------|---------|----------------|
| pps10m | disable | pps |
|.........|.........|................|
Response 2c:

Chapter 3
Port config
---------------------------------------
|---------|----------|----------------|
| pps10m | enable | 10MHz |
|.........|..........|................|
Example 3:
TP2700> show output status t1e1
Response 3a:
---------------------------
|io status |port status |
|------------|------------|
|t1 output |on |
---------------------------
Response 3b:
---------------------------|
| io status | port status |
|------------|-------------|
| t1 output | off |
...........................|
Response 3c:
Status: port is configured as input.
Response 3d
Status: port is disabled.
set output
Use this command to configure output parameters for the T1/E1 and PPS/10M port.
When the T1/E1 port is configured as an output port, use this command to provision
all parameters for the output signal that are defined in ITU-T G.704:
 Framing Type
– CCS, CAS, or freq2048khz for E1
– D4, ESF, freq1544KHz or isolateOne for T1 (isolateOne is for test
purposes only)
 CRC state for E1

Chapter 3
 SSM Bit position for E1

 Zero-Suppression (On or Off) for E1
All the configurations provisioned by this command apply to the T1/E1 port only
when the IO-direction of the port is configured as an Output with the set
port-control t1e1 io output command.
The provisioning displayed with the show output config t1e1 command will
apply to the T1/E1 port only when the IO-direction of the port is configured as
OUTPUT with the set port-control t1e1 io output command.
Command Syntax:
 To provision the output frame type for an E1 output signal:

set output e1 frametype t1e1 {ccs | cas | freq2048khz}
 To provision CRC for an E1 output signal:

set output e1 crc t1e1 {enable | disable}
 To provision the output SSM Bit for an E1 output signal:

set output e1 ssmbit t1e1 {4 | 5 | 6 | 7 | 8 | all }
 To provision zero-suppression for an E1 output signal:

set output e1 zero-suppression t1e1 {on | off}
 To provision the output frame type for a T1 output signal:

set output t1 frametype t1e1 {d4 | esf | freq1544khz |
isolateOne}
 To provision the 1PPS time offset on the PPS/10M output port:

set output pps offset pps10m <offset-value>
Example 1:
To set the frame type to 2048 kHz for E1 output on the T1/E1 port:
TP2700> set output e1 frametype t1e1 freq2048khz
Example 2:
To Enable CRC for E1 output on T1/E1 port:
TP2700> set output e1 crc t1e1 enable
Example 3:
To provision the SSM Bit position to 6 for E1 output on T1/E1 port:

Chapter 3
TP2700> set output e1 ssmbit t1e1 6
Example 4:
To provision the frame type of the T1 output signal that might apply to T1/E1 port as
D4:
TP2700> set output t1 frametype t1e1 d4

Chapter 3
show output-gen
This command displays the configuration for Output Port behavior during the
warm-up, free-run, fast-track and holdover states.
Command Syntax:
show output-gen
Example:
TP2700> show output-gen
Response:
Output generation configuration:
--------------------------------------------------------------
|Port |warm-up |free-run |holdover |fast-track |
|--------|------------|------------|------------|------------|
|t1e1 |squelch |squelch |on |on |
|........|............|............|............|............|
|tod |squelch |squelch |on |on |
--------------------------------------------------------------
set output-gen
Use this command to provision the System's output port behaviors during the
warm-up, free-run, fast-track, and holdover states.
Command Syntax:
 To provision the output generation behavior for the T1/E1 port:

set output-gen {warm-up| free-run | holdover |fast-track}
t1e1 {on | ais | squelch}
 To provision the output generation behavior for the TOD port:

set output-gen {warm-up| free-run | holdover |fast-track}
tod {on | squelch}
Example 1:
To provision the output behavior to squelch during the free-run state for the T1/E1
port when it is configured as an output port:
TP2700> set output-gen free-run t1e1 squelch

Chapter 3
Example 2:
To provision the output behavior to ON during the holdover state for the TOD output
port:
TP2700> set output-gen holdover tod on

Chapter 3
password
Use this command to modify the password of the current user.
Command Syntax:
password
Example:
TP2700> password
Response:
For new user password, only chars {a-z, A-Z, 0-9, ! ( ) - _ .

? ~ *} are accepted
Password:
Prompt for password confirmation
Note: Be sure to not lose or forget the password. Contact Microsemi

support for the password recovery procedure if all admin-level user
passwords are lost.

Chapter 3
ping
Use this command to ping the host specified by the address (xxx.xxx.xxx.xxx) and
display ping statistics from Ethernet maintenance port or PTP service port. A fully
qualified domain name (FQDN) can be used for the management port, assuming
the DNS server address is available from DHCP or statically configured IP.
Note: To minimize system resource usage and deter denial of

service attacks, the system is configured to allow a maximum
ICMP ping request rate of 1 per second.
Command Syntax:
ping mgmt <ip-address>
ping {eth1 | eth2} [<vlan-id>] <ip-address>
Example 1:
To ping IPv4 address 192.168.5.100 from Ethernet management port
TP2700> ping mgmt 192.168.5.100 <enter>
Response 1:
Ping mgmt success
Response 1a:
Error: action failed

Ping mgmt failed
Example 2:
To ping IPv4 address 192.168.5.110, from ETH2 port, which has VLAN ID of 23:
TP2700> ping eth2 23 192.168.5.110
Response 2:
Ping eth2 success

Chapter 3
show port-control
This command provisions the sync service port, legacy port, or packet time service
ports configurations.
Command Syntax:
show port-control
Example 1:
TP2700>show port-control
Response 1:
--------------------------------------------
|# |Port |State |IO dir |Signal/Format|
|---|-------|--------|-------|-------------|
|1 |t1e1 |enable |input |t1 |
|...|.......|........|.......|.............|
|2 |pps10m |enable |output |10MHz |
|...|.......|........|.......|.............|
|3 |tod |enable |output |cisco |
--------------------------------------------
Note: The IO direction for the TOD and PPS10M ports are not
configurable - they are both hardcoded as “output”.
set port-control
Use this command to provision the sync service port, legacy port, or packet time
service port. This includes configuration of port states, port directions, port
connector types, and/or service types.
Command Syntax:
 To provision the state for the T1/E1 port:

set port-control t1e1 state {enable | disable}
 To provision the IO direction of the T1/E1 port:

set port-control t1e1 io {input | output}

Chapter 3
 To provision the signal type for the T1/E1 port:

set port-control t1e1 signal-type {e1 | t1}
 To provision the port state for the PPS/10M port:

set port-control pps10m state {enable | disable}
 To provision the signal type for the PPS/10M port:

set port-control pps10m signal-type {pps | 10m}
 To provision port state for the TOD output port:

set port-control tod state {enable | disable}
 To provision the TOD message format for the TOD output port:
set port-control tod format {cisco | china_mobile}
Note: The Cisco TOD message format reports leap seconds using
TAI-UTC. The China Mobile TOD message format reports GPS leap
second using GPS-UTC.
Example 1:
To set the T1/E1 port as an E1 input port and to enable it:
TP2700> set port-control t1e1 io input
TP2700> set port-control t1e1 signal-type e1
TP2700> set port-control t1e1 state enable
Example 2:
To set the TOD format for the TOD output port as Cisco format:
TP2700> set port-control tod format cisco
Example 3:
To set the PPS/10M port as an 10 MHz output port and to enable it:
set port-control pps10m signal-type 10m
set port-control pps10m state enable
Remarks: If the T1/E1 port is provisioned as an input port (with any signal types),
and the port state is set to DISABLE, all alarms related to this port will be cleared.
The alarm will be reported again if the alarm condition is still existing when the port
state is set to ENABLE.
Level: Config and Admin

Chapter 3
show pql-ssm
This command displays the Priority Quality Level (PQL) values for reference input
signal types. The PQL corresponds to the “ssm-value” parameter that is used with
the “set ref” command for reference selection. The PQL is a representation of
traceability for the signal presented at the input ports, where a PQL value of 16
represents an invalid SSM. If SSM is disabled for an input port (set ref
use-config-pql), then the TP 2300/2700 will use the user-assigned SSM-value
(PQL) for that input port.
Note: SSM during bridging will be the last SSM value of input
reference while clock was in normal lock state.
See PQL Mapping, on page 361 and Reference Selection Criteria, on page 223 for
more information.
Command Syntax:
show pql-ssm
Example:
TP2700> show pql-ssm
Response:
Note: The PTP clockClass value shown in response to this

command is included in the PTP Announce message to
advertise the quality level of the clock.
PQL-SSM-ClockClass Option I
-------------------------------------------------------------------------------
|PQL|E1 SSM |SyncE |clock |clock |Clock QL/ Option I, Description |
| | |SSM |class |class | |
| | | |g8265-1 |tele-2008| |
| | | | |default | |
|---|-------|-------|--------|---------|--------------------------------------|
|1 |0x2 |0x2 |80 |6 |QL-PRC/G.811 |
|...|.......|.......|........|.........|......................................|
|2 |0x0* |0x0* |82 |6 |input: QL-STU, output: QL-PRC |
|...|.......|.......|........|.........|......................................|
|3 |0x2 |0x2 |84 |6 |QL-PRC/G.811 |
|...|.......|.......|........|.........|......................................|
|4 |0x4 |0x4 |86 |7 |QL_SSU_A/g.812,Type I |
|...|.......|.......|........|.........|......................................|
|5 |0x4 |0x4 |88 |7 |QL_SSU_A/g.812,Type I |
|...|.......|.......|........|.........|......................................|
|6 |0x4 |0x4 |90 |7 |QL_SSU_A/g.812,Type I |
|...|.......|.......|........|.........|......................................|
|7 |0x8 |0x8 |92 |13 |QL_SSU_B/G.812 Type VI |

Chapter 3
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|12 |0xB |0xB |102 |52 |QL-SEC/EEC1/G.813 Opt1,G.8264 |
|...|.......|.......|........|.........|......................................|
|13 |0xB |0xB |104 |58 |QL-SEC/EEC1/G.813 Opt1,G.8264 |
|...|.......|.......|........|.........|......................................|
|14 |0xF |0xF |106 |248 |QL-SEC/EEC1/G.813 Opt1,G.8264 |
|...|.......|.......|........|.........|......................................|
|15 |0xF |0xF |108 |248 |QL-DNU |
|...|.......|.......|........|.........|......................................|
|16 |0xF |0xF |110 |248 |Any Invalid SSM or ClockClass |
-------------------------------------------------------------------------------
PQL-SSM-ClockClass Option II
-------------------------------------------------------------------------------
|PQL|T1 SSM |SyncE |clock |clock |Clock QL/ Description |
| | |SSM |class |class | |
| | | |g8265-1 |tele-2008| |
| | | | |default | |
|---|-------|-------|--------|---------|--------------------------------------|
|1 |0x04FF |0x1 |80 |6 |QL-PRS/G.811 |
|...|.......|.......|........|.........|......................................|
|2 |0x08FF |0x0 |82 |6 |QL-STU/G.811 |
|...|.......|.......|........|.........|......................................|
|3 |0x04FF |0x1 |84 |6 |QL-PRS/G.811 |
|...|.......|.......|........|.........|......................................|
|4 |0x0CFF |0x7 |86 |7 |QL-ST2/G.812, typeII |
|...|.......|.......|........|.........|......................................|
|5 |0x0CFF |0x7 |88 |7 |QL-TNC/G.812Type V |
|...|.......|.......|........|.........|......................................|
|6 |0x78FF |0x4 |90 |7 |QL-TNC/G.812Type V |
|...|.......|.......|........|.........|......................................|
|7 |0x7CFF |0xD |92 |13 |QL-ST3E/G.812 typeIII |
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|...|.......|.......|........|.........|......................................|
|12 |0x10FF |0xA |102 |52 |QL-ST3/G.812 typeIV |
|...|.......|.......|........|.........|......................................|
|13 |0x10FF |0xA |104 |58 |QL-SMC/EEC2/G.813/G.8262 OPT2 |
|...|.......|.......|........|.........|......................................|
|14 |0x30FF |0xF |106 |58 |QL-SMC/EEC2/G.813/G.8262 OPT2 |

Chapter 3
|...|.......|.......|........|.........|......................................|
|15 |0x30FF |0xF |108 |248 |QL-PROV |
|...|.......|.......|........|.........|......................................|
|16 |0x30FF |0xF |110 |248 |QL-DUS or Invalid SSM |
-------------------------------------------------------------------------------
* Item 2 in Option I Table:

For E1 or SycnE input with received SSM = 0x00, PQL = 2.
For E1 or SycnE output with the system PQL = 2, SSM = 0x02.
Related :SSM during bridging will be the last SSM value of input reference while
clock was in normal lock state.

Chapter 3
show ptp
Use this command to display the PTP master and PTP client configuration
information: the active profile selection, and all the parameters under different
profiles, the client list for PTP master, the grand master table for PTP client, and the
status for PTP master and PTP client.
Command Syntax:
PTP MASTER:
 To display the the active profile selected for PTP master on the ETH2 port:
show ptp master active-profile eth2
 To display PTP master’s configurable attributes under different profiles on the

ETH2 port:
show ptp master config eth2 {telecom-2008 | itu-g8265-1 |
default | ethernet-default}
 To display the client list of PTP master on the ETH2 port:

show ptp master client-list eth2 {all | clock-id}
 To display the status of PTP master on the ETH2 port:

show ptp master status eth2
PTP CLIENT:
 To display the active profile selected for PTP client on the ETH1 port:
show ptp client active-profile eth1
 To display the status of PTP client on the ETH1 port:

show ptp client status eth1
 To display the VLAN attachment for the master(s) of PTP client on ETH1 port:
show ptp client vlan-attach eth1
 To display the asymmetry information for PTP client on the ETH1 port:
show ptp client eth1 asymmetry
 To display the configuration of network transport type for PTP client on the ETH1
port:
show ptp client config eth1 transport
 To display the configuration of the service tier for PTP client on the ETH1 port:
show ptp client config eth1 service-tier

Chapter 3
 To display the asymmetry state for PTP client on the ETH1 port:
show ptp client config eth1 asymmetry state
 To display phase offset (manually configured) for PTP client on the ETH1 port:
show ptp client config eth1 phase-offset
 To display FPP cluster widths for PTP client on the ETH1 port:
show ptp client config eth1 fpp
 To display detailed configurable attributes for PTP client on the ETH1 port:
show ptp client config eth1 telecom-2008
Example 1:
To show info for PTP client with known clock ID 00:B0:AE:FF:FE:01:1A:85 for PTP
master on ETH2 port:
TP2700>show ptp master client-list eth2 clock-id

00:B0:AE:FF:FE:01:1A:85
Response 1:
Index IP Address VLAN PRI Clock Id Ann Sync Delay ConnTime

1 192.168.9.44 0 0 00:b0:ae:ff:fe:03:46:05 1 -6 -6 259531
Example 2:
To show all the clients for the PTP master on the ETH2 port:
TP2700> show ptp master client-list eth2 all
Response 2:
Index IP Address VLAN PRI Clock Id Ann Sync Delay ConnTime

1 192.168.5.13 0 0 00:b0:ae:ff:fe:03:46:07 1 -6 -6 259531
2 192.168.5.23 0 0 00:b0:ae:ff:fe:03:47:08 1 -6 -6 254356
3 192.168.5.33 0 0 00:b0:ae:ff:fe:03:48:09 1 -6 -6 282343
Example 3:
To show the active profile for the PTP master on the ETH2 port:
TP2700>show ptp master active-profile eth2 <enter>
Response 3a:
ETH2 PTP MASTER ACTIVE-PROFILE: telecom-2008

Chapter 3
Response 3b:
ETH2 PTP MASTER ACTIVE-PROFILE: itu-g8265-1
Response 3b:
ETH2 PTP MASTER ACTIVE-PROFILE: default
Example 4:
To show the PTP client active-profile:
TP2700>show ptp client active-profile eth1
Response 4:
ETH1 PTP CLIENT ACTIVE-PROFILE: telecom-2008
Example 5:
To show the Telecom-2008 configuration info for PTP master on ETH2 port:
TP2700>show ptp master config eth2 telecom-2008
Response 5:
ETH2 PTP MASTER CONFIGURATION WITH PROFILE TELECOM-2008:
PTP State : enable

PTP TTL : 64
PTP DSCP : 0
PTP Dither : disable
PTP Max Number Clients : 8
PTP Two Steps : disable
PTP Unicast Negotiation : enable
PTP Unicast Lease Limit : 1000
PTP Sync Limit : -7
PTP Announce Limit : -4
PTP Delay Limit : -7
PTP Clock Id : 00:b0:ae:ff:fe:03:46:05
PTP Priority 1 : 128
PTP Domain : 0
PTP Timescale : auto
PTP Service Load Alarm Threshold(%) : 90
Example 6:
To show the profile ITU-G.8265-1 configuration info for PTP master on ETH2 port:
TP2700>show ptp master config eth2 itu-g8265-1

Chapter 3
Response 6:
EHT2 PTP MASTER CONFIGURATION WITH PROFILE ITU-G8265-1:

PTP State : enable
PTP TTL : 64
PTP DSCP : 0
PTP Unicast Lease Limit : 1000
PTP Sync Limit : -7
PTP Domain : 4
Example 7:
To show the default profile (Layer 3 multicast) configuration info for PTP master on
ETH2 port:
TP2700>show ptp master config eth2 default
Response 7:
ETH2 PTP MASTER CONFIGURATION WITH PROFILE DEFAULT:

PTP State : enable
PTP Vlan ID : 0
PTP TTL : 16
PTP DSCP : 0
PTP Two Step : disable
PTP Announce Interval : 1
PTP Sync Interval : 0
PTP Delay Interval : 0
PTP Announce Receipt Timeout : 3
PTP Multicast Client Timeout : 300
PTP Domain : 0

Chapter 3
Example 8:
To show the ethernet-default profile (Layer 3 multicast) configuration info for PTP
master on ETH2 port:
TP2700>show ptp master config eth2 ethernet-default
Response 8:
ETH2 PTP MASTER CONFIGURATION WITH PROFILE ETH DEFAULT:
PTP State : enable

PTP Vlan ID : 0
PTP Two Step : disable
PTP Sync Interval : -6
PTP Delay Interval : -6
PTP Multicast Client Timeout : 300
PTP Domain : 0
Example 9:
To show the status of PTP master on ETH2 port:
TP2700>show ptp master status eth2
Response 9:
ETH2 PTP MASTER STATUS :
Port enabled : yes

Clock Id : 00:b0:ae:ff:fe:03:46:69
Port Number : 2
Profile : telecom-2008
Port state : master
Clock class : 6
Clock accuracy : within 100 ns
Timescale : ptp
Maximum allowed clients : 64
Number of attached clients : 1
Client load : 1%
Example 10:

Chapter 3
To show the Telecom-2008 configuration info for PTP client on ETH1 port:
TP2700>show ptp client config eth1 telecom-2008
Response 10:
ETH1 PTP CLIENT CONFIGURATION WITH PROFILE TELECOM 2008:
PTP State : enable

PTP TTL : 64
PTP DSCP : 0
PTP Unicast Lease Duration : 300
PTP Domain : 0
PTP master-table:
------------------------------
|Index |address |
|-------|--------------------|
|1 |192.168.9.41 |
|.......|....................|
|2 |0.0.0.0 |
------------------------------
Example 11:
To show the status for PTP clients on ETH1 port:
TP2700>show ptp client status eth1
Response 11:
ETH1 PTP CLIENT STATUS:
Client Status : normal flow

Minimal Round Trip Delay(us) : 0.00
System Date and Time : 2004-03-03,04:51:40
METRIC : FORWARD REVERSE

Transient free out of 900s : 900 900
Operational Min TDEV (ns) : 4.5 5.5
Operational MAFE (ppb) : 0.00 0.00

Chapter 3
Mode width (ns) : 30000.0 15000.0

FPP1 (%) : 100.0 99.9
FPP2 (%) : 100.0 99.9
Packet Rate (pkts/s) : 64 64
FPP1 Cluster Width (us) : 10.0
FPP2 Cluster Width (us) : 100.0
Currently Used Master:
IP Address : 192.168.9.41
Clock ID : 00:b0:ae:ff:fe:03:46:69
Port Number : 2
Clock Class : 6
Clock Accuracy : within 100 ns
Time Scale : PTP
Time Source : GPS
Time Traceable : true
Frequency Traceable : true
Steps Removed : 1
Table 3-4. PTP Client Status Descriptions
Status Parameter Description
Client Status Indicates whether the client has established flow

with the master.
Minimal Round Trip Delay (µs) Indicates the smallest round trip delay between
this slave port and its upstream master.
Transient free out of 900s Values are rolling 15 minute (900 s) metrics.
Transients include loss of sync flow, phase steps,
and pops against both dynamic and static
thresholds. If a given second includes a
transient, it is not considered "transient-free".
Generally if 80% or more of the time is
transient-free (720 s or more), transient packet
behavior should not be causing performance
issues.
Transient free out of 3600 Values are rolling 1 hour (3600 s) metrics.
Transients include loss of sync flow, phase steps,
and pops against both dynamic and static
thresholds. If a given second includes a
transient, it is not considered "transient-free".
Generally if 80% or more of the time is
transient-free (2880 s or more), transient packet
behavior should not be causing performance
issues.

Chapter 3
Operational Min TDEV (ns) An operational stability estimate using the

minimum TDEV metric defined in G.8261.
Smaller values correlate to better output
performance. This value is based on forward flow
(sync).
Operational MAFE (ppb) Operational stability estimate proposed to the

ITU-T. MAFE (maximum Average Frequency
Error) estimates the maximum frequency error of
a packet clock based on a clustering and
averaging window. The clustering window is 1
minute and the averaging window I 15 minutes.
Mode width (ns) Current estimate of the main mode width of the
forward packet delay variation. The mode width
is used in both weighting and compensation.
Mode width is a good indicator of loading.
FPP1 (%) Floor Packet Percentage (FPP) is an operational

measurement capability, a potentially valuable
component in managing/understanding the
ability of a given path to deliver sync to a
required performance level.
FPP1 is based on the packet delay variation
(PDV) cluster range starting from the PDV floor
as calculated. This calculation is performed from
the context of the client over the sample period
designated by the “cluster_width_1”
parameter in the “set ptp client config eth1
fpp” command. There are two FPP1 values
calculated, one for the forward flow and one for
the reverse flow.
FPP values relative to performance thresholds
(see G.8265.1) at different cluster widths can be
used to categorize usability of the PTP input
signal from the master. FPP results provided by
TP 2300/2700 should not be expected to provide
the same accuracy as a parallel measurement
made with test equipment.
FPP2 (%) Floor Packet Percentage 2 (FPP2) is based on

the packet delay variation (PDV) cluster range
starting from the PDV floor as calculated. This
calculation is performed from the context of the
client over the sample period designated by the
“cluster_width_2” parameter in the “set ptp
client config eth1 fpp” command. There are
two FPP2 values calculated, one for the forward
flow and one for the reverse flow.
(See description for FPP1 above.)

Chapter 3
Packet Rate (pkts/s) Measured rate of SYNC packets in the forward

path and the DELAY_RESP packet in the
reverse path.
FPP1 Cluster Width (us) Floor Packet Percentage 1 cluster width, which
defines the designated sample period for Floor
Packet Percentage 1 (FPP1).
FPP2 Cluster Width (us) Floor Packet Percentage 2 cluster width, which
defines the designated sample period for Floor
Packet Percentage 2 (FPP2).
IP address Identifies the IPv4 address of the master.
Clock ID Identifies the Clock ID of the master.
Clock Class Identifies the PTP clockClass of the

grandmaster.
Clock Accuracy Identifies the clock accuracy of the grandmaster.
Time Scale Timescale whether PTP or ARB is used by the

grandmaster.
Time Source Identifies the time source of the grandmaster.

Time source is defined in Table 7 of IEEE Std
1588-2008.
Time Traceable Identifies whether the slave clock time is

traceable to the grandmaster.
Frequency Traceable Identifies whether the slave clock frequency is

traceable to the grandmaster.
Steps Removed Identifies the number of hops between this slave

clock and the grandmaster clock.
Example 12:
To show the vlan attachments for masters of PTP client on ETH1 port:
TP2700>show ptp client vlan-attach eth1
Response 12:
PTP client port VLAN attachment : 0
Example 13:

Chapter 3
To display the configuration of network transport type for PTP client on ETH1 port:
TP2700> show ptp client config eth1 transport
Response 13:
ETH1 PTP client port transport type : Ethernet
Example 14:
To display the configuration of the service tier for PTP client on ETH1 port:
TP2700> show ptp client config eth1 service-tier
Response 14:
ETH1 PTP client port service-tier : sync-mask
Example 15:
To display the asymmetry state for PTP client port:
TP2700> show ptp client config eth1 asymmetry state
Response 15:
ETH1 PTP client port asymmetry state : disable
Example 16:
To display the asymmetry information for PTP client port:
TP2700> show ptp client eth1 asymmetry
Response 16:
ETH1 PTP client port asymmetry information:
Current table : Table 1

Current path calibration noise (ns) : 451
Table 1 Clock ID : 00-B0-AE-FF-FE-01-D8-86
Table 1 Path rearrangements per day : 4
Table 1 Number of total paths : 3
Table 2 Clock ID : 00-B0-AE-FF-FE-01-D8-45
Table 2 Path rearrangements per day : 4
Table 2 Number of total paths : 23

Chapter 3
Table 3-5. PTP Client Asymmetry Information Descriptions
Current table Which asymmetry table is currently being used.

This is based on which master is being used.
Current path calibration noise (ns) Estimate of uncertainty in asymmetry

calibration value
Table 1 Clock ID PTP Clock ID of master #1
Table 1 Path rearrangements per day Number of times per day that the system
detected a path rearrangement to master #1.
Table 1 Number of total paths Total number of unique paths to master #1 that
have been determined by the asymmetry
algorithm. Each unique path has an
asymmetry value stored for it.
Table 2 Clock ID PTP Clock ID of master #2
Table 2 Path rearrangements per day Number of times per day that the system
detected a path rearrangement to master #2.
Table 2 Number of total paths Total number of unique paths to master #2 that
have been determined by the asymmetry
algorithm. Each unique path has an
asymmetry value stored for it.

Chapter 3
Example 17:
To display the phase offset for PTP client port:
TP2700> show ptp client eth1 phase-offset
Response 17:
ETH1 PTP client port phase-offset (ns) : 0

Chapter 3
set ptp
The command is used to provision the configurable parameters for PTP output
(master) and PTP input (client), including the profile selection, the attributes under
different profiles, and to provision the Grand Master table for PTP client.
Table 3-6. PTP Profiles
PTP Profile Syntax Transport Mode Description
Default default Layer 3 Multicast IEEE 1588-2008 Annex J

multicast over UDP/IP
Ethernet-Default ethernet-default Layer 2 Multicast IEEE 1588-2008 Annex F

multicast over Ethernet
Telecom-2008 telecom-2008 Unicast Generic unicast profile created

for telecom before ITU-T
G.8265.1
ITU-T G.8265-1 g8265-1 Unicast Telecom profile for frequency

sync described in ITU-T
G.8265.1
See Table 3-7 for descriptions of the attributes specific to the Default and Ethernet
Default (multicast) PTP Master profile. See Table 3-9 for descriptions of the
attributes specific to the Telecom-2008 and ITU-T G.8265.1 (unicast) PTP Master
profile. See Table 3-10 for descriptions of the attributes specific to the PTP Client
profile.
Command Syntax:
PTP MASTER - Default Profile Multicast Attributes:
 To provision the active profile for PTP master with the Default (multicast) active
profile:
set ptp master active-profile eth2 default
 To provision the state of the Two-Step Clock mode for a Master with the Default
(multicast) active profile:
set ptp master config eth2 default two-step {enable |
disable}
– If the Two-Step Clock state is Disable, a One-Step Clock is used.

 To provision the timescale to Automatic, Arbitrary, or PTP for a Master with the
Default (multicast) active profile:
set ptp master config eth2 default timescale {auto| arb |
ptp}

Chapter 3
– If the timescale is set to “auto”, the TP 2300/2700 will make the decision
based on the input. The TP 2300/2700 will set the timescale to “ptp” if the
unit is locked to GNSS or PTP. The TP 2300/2700 will set the timescale to
“arb” if the unit is locked to any other reference besides GNSS or PTP (i.e.,
E1, T1 or SyncE).
 To provision the state for a Master with the Default (multicast) active profile:
set ptp master config eth2 default ptp-state {enable |
disable}
 To provision the PTP priority-1 value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default priority-1
<priority-1-value>
 To provision the PTP priority-2 value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default priority-2
<priority-2-value>
 To provision the PTP domain value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default domain <domain-value>
 To provision the PTP Diffserv Code Point value for a Master with the Default
set ptp master config eth2 default dscp <dscp-value>
 To provision the PTP dither value for a Master with the Default (multicast) active
profile:
set ptp master config eth2 default dither {enable | disable}
 To provision the IP Header Time to Live (TTL) field for PTP packets for the
Master with the Default (multicast) active profile:
set ptp master config eth2 default ttl <TTL-value>
 To provision the announce receipt timeout value for a Master with the Default
set ptp master config eth2 default announce-receipt-timeout
<timeout-value>
 To provision the announce interval value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default announce-interval
<announce-interval-value>
– The interval is 2z seconds, where z= <announce-interval-value>.

Chapter 3
 To provision the sync-interval value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default sync-interval
<sync-interval-value>
 To provision the minimum delay-interval value for a Master with the Default
set ptp master config eth2 default delay-interval
<delay-interval-value>
 To provision the client-timeout value for a Master with the Default (multicast)
active profile:
set ptp master config eth2 default client-timeout
<client-timeout-value>
 To provision the VLAN ID value for a Master with the Default (multicast) active
profile
set ptp master config eth2 default vlanid <vlanid-value>
 To provision the service load alarm threshold for a Master with the Default
set ptp master config eth2 default
service-load-alarm-threshold <threshold-value>
PTP MASTER - Ethernet Default Profile Multicast Attributes:
 To provision the active profile for PTP master with the Ethernet Default
set ptp master active-profile eth2 ethernet-default
 To provision the state of the Two-Step Clock mode for a Master with the Ethernet
set ptp master config eth2 ethernet-default two-step {enable
| disable}

 To provision the timescale to Automatic, Arbitrary, or PTP for a Master with the
Ethernet Default (multicast) active profile:
set ptp master config eth2 ethernet-default timescale {auto|
arb | ptp}
unit is locked to GNSS or PTP. The TP 2300/2700 will set the timescale to
“arb” if the unit is locked to any other reference besides GNSS or PTP (i.e.,
E1, T1 or SyncE).
Chapter 3
 To provision the state for a Master with the Ethernet Default (multicast) active
profile:
set ptp master config eth2 ethernet-default ptp-state
{enable | disable}
 To provision the PTP priority-1 value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default priority-1
<priority-1-value>
 To provision the PTP priority-2 value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default priority-2
<priority-2-value>
 To provision the PTP domain value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default domain
<domain-value>
 To provision the PTP dither value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default dither {enable |
disable}
 To provision the announce receipt timeout value for a Master with the Ethernet
set ptp master config eth2 ethernet-default
announce-receipt-timeout <timeout-value>
 To provision the announce interval value for a Master with the Ethernet Default
announce-interval <announce-interval-value>
– The interval is 2z seconds, where z= <announce-interval-value>.
 To provision the sync-interval value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default sync-interval
 To provision the minimum delay-interval value for a Master with the Ethernet
set ptp master config eth2 ethernet-default delay-interval
<delay-interval-value>

Chapter 3
 To provision the client-timeout value for a Master with the Ethernet Default
set ptp master config eth2 ethernet-default client-timeout
<client-timeout-value>
 To provision the VLAN ID value for a Master with the Ethernet Default (multicast)
active profile
set ptp master config eth2 ethernet-default vlanid
<vlanid-value>
 To provision the service load alarm threshold for a Master with the Ethernet
PTP MASTER - Telecom-2008 Profile Attributes:
 To provision the active profile to Telecom-2008 for PTP master:

set ptp master active-profile eth2 telecom-2008
 To provision the state of the Two-Step Clock mode, for a Master with the
Telecom-2008 (unicast) active profile:
set ptp master config eth2 telecom-2008 two-step {enable |
disable}

 To provision the timescale to Automatic, Arbitrary or PTP for a Master with the
set ptp master config eth2 telecom-2008 timescale {auto| arb
| ptp}
unit is locked to gnss or ptp. The TP 2300/2700 will set the timescale to
“arb” if the unit is locked to any other reference besides gnss or ptp (i.e.,
E1, T1 or SyncE).
 To provision the state for a Master with the Telecom-2008 (unicast) active profile:
set ptp master config eth2 telecom-2008 ptp-state {enable |
disable}
 To provision the PTP priority1 value for a Master with the Telecom-2008 (unicast)
active profile:
set ptp master config eth2 telecom-2008 priority-1
<priority-1-value>

Chapter 3
 To provision the PTP priority-2 value for a Master with the Telecom-2008
(unicast) active profile:
set ptp master config eth2 telecom-2008 priority-2
<priority-2-value>
 To provision the PTP domain value for a Master with the Telecom-2008 (unicast)
active profile:
set ptp master config eth2 telecom-2008 domain
<domain-value>
 To provision the PTP Diffserv Code Point value for a Master with the
set ptp master config eth2 telecom-2008 dscp <dscp-value>
 To provision the PTP dither value for a Master with the Telecom-2008 (unicast)
active profile:
set ptp master config eth2 telecom-2008 dither {enable |
disable}
 To provision the IP Header Time to Live (TTL) field for PTP packets for a Master
with the Telecom-2008 (unicast) active profile:
set ptp master config eth2 telecom-2008 ttl <TTL-value>
 To provision the PTP unicast negotiation state for a Master with the
set ptp master config eth2 telecom-2008 unicast-negotiation
{enable | disable}
 To set the PTP unicast maximum lease-limit value for a Master with the
set ptp master config eth2 telecom-2008 lease-limit
<limit-value>
 To provision the announce limit, the minimum interval (maximum rate) between
PTP announce messages, for a Master with the Telecom-2008 (unicast) active
profile:
set ptp master config eth2 telecom-2008 announce-limit
<announce-limit value>
– The interval is 2z seconds, where z= <announce-limit-value>.
 To provision the synchronization limit, the minimum interval (maximum rate)

between PTP synchronization messages, for a Master with the Telecom-2008
set ptp master config eth2 telecom-2008 sync-limit
<sync-limit value>
– The interval is 2z seconds, where z= <sync-limit-value>.

Chapter 3
 To provision the delay limit, the minimum interval (maximum rate) between PTP
delay response messages, for a Master with the Telecom-2008 (unicast) active
profile:
set ptp master config eth2 telecom-2008 delay-limit
<delay-limit-value>
– The interval is 2z seconds, where z= <delay-limit-value>.
 To provision the service load alarm threshold for a Master with the Telecom-2008
set ptp master config eth2 telecom-2008
PTP MASTER - ITU-G.8265-1 Profile Attributes:
 To provision the active profile for PTP master:

set ptp master active-profile eth2 itu-g8265-1
 To provision the state of the Two-Step Clock mode, for a Master with the
ITU-G.8265-1 (unicast) active profile:
set ptp master config eth2 itu-g8265-1 two-step {enable |
disable}

 To provision the timescale to Automatic, Arbitrary or PTP for a Master with the
set ptp master config eth2 itu-g8265-1 timescale {auto| arb
| ptp}
unit is locked to gnss or ptp. The TP 2300/2700 will set the timescale to
“arb” if the unit is locked to any other reference besides gnss or ptp (i.e.,
E1, T1 or SyncE).
 To provision the state for a Master with the ITU-G.8265-1 (unicast) active profile:
set ptp master config eth2 itu-g8265-1 ptp-state {enable |
disable}
 To provision the PTP priority1 value for a Master with the ITU-G.8265-1 (unicast)
active profile:
set ptp master config eth2 itu-g8265-1 priority-1
<priority-1-value>
 To provision the PTP priority-2 value for a Master with the ITU-G.8265-1 (unicast)
active profile:

Chapter 3
set ptp master config eth2 itu-g8265-1 priority-2

<priority-2-value>
 To provision the PTP domain value for a Master with the ITU-G.8265-1 (unicast)
active profile:
set ptp master config eth2 itu-g8265-1 domain <domain-value>
 To provision the PTP Diffserv Code Point value for a Master with the
set ptp master config eth2 itu-g8265-1 dscp <dscp-value>
 To provision the PTP dither value for a Master with the ITU-G.8265-1 (unicast)
active profile:
set ptp master config eth2 itu-g8265-1 dither {enable |
disable}
 To provision the IP Header Time to Live (TTL) field for PTP packets for a Master
with the ITU-G.8265-1 (unicast) active profile:
set ptp master config eth2 itu-g8265-1 ttl <TTL-value>
 To provision the PTP unicast negotiation state for a Master with the ITU-G.8265-1
set ptp master config eth2 itu-g8265-1 unicast-negotiation
{enable | disable}
 To set the PTP unicast maximum lease-limit value for a Master with the
set ptp master config eth2 itu-g8265-1 lease-limit
<limit-value>
 To provision the announce limit, the minimum interval (maximum rate) between
PTP announce messages, for a Master with the ITU-G.8265-1 (unicast) active
profile:
set ptp master config eth2 itu-g8265-1 announce-limit
<announce-limit value>
 To provision the synchronization limit, the minimum interval (maximum rate)

between PTP synchronization messages, for a Master with the ITU-G.8265-1
set ptp master config eth2 itu-g8265-1 sync-limit
<sync-limit value>
– The interval is 2z seconds, where z= <sync-limit-value>.

Chapter 3
 To provision the delay limit, the minimum interval (maximum rate) between PTP
delay response messages, for a Master with the ITU-G.8265-1 (unicast) active
profile:
set ptp master config eth2 itu-g8265-1 delay-limit
<delay-limit-value>
– The interval is 2z seconds, where z= <delay-limit-value>.
 To provision the service load alarm threshold for a Master with the ITU-G.8265-1
set ptp master config eth2 itu-g8265-1
PTP CLIENT:
Note: On the PTP Client Port, the client is capable of receiving

and processing messages from both one-step and two-step
clock masters, without any particular configuration. The client
auto-detects the two-step clock flag in Announce messages
from the master and, based on the setting, runs a one-step or
two-step clock operation.
 To provision the active profile for PTP client:

set ptp client active-profile eth1 telecom-2008
 To provision a VLAN for a master in the acceptable master table for PTP client:
set ptp client vlan-attach eth1 master-index {1 | 2}
vlanid <2-4094>
 To provision the transport for PTP client on ETH1 port:

set ptp client config eth1 transport ethernet
 To provision the service tier for PTP client on ETH1 port:

set ptp client config eth1 service-tier {sync-mask |
modified-traffic-mask | packet-prs | sync-extended-mask}
– The system will prompt to confirm the service tier change before executing
this command:
Are you sure you want to change the service tier, if yes, the
system will be restarted? (yes|no)
 To provision the asymmetry state for PTP client on ETH1 port:

set ptp client config eth1 asymmetry state
{enable | disable}

Chapter 3
 To clear the asymmetry for PTP client on ETH1 port:

set ptp client config eth1 asymmetry clear
 To set the phase offset value for PTP client on ETH1 port:
set ptp client config eth1 phase-offset <offset-value>
 To set the FPP cluster width 1 value for PTP client on ETH1 port:
set ptp client config eth1 fpp cluster_width_1 <fpp-value>
 To set the FPP cluster width 2 value for PTP client on ETH1 port:
set ptp client config eth1 fpp cluster_width_2 <fpp-value>
 To provision the PTP unicast negotiation state for the Client:

set ptp client config eth1 telecom-2008 unicast-negotiation
{enable|disable}
 To set the PTP unicast maximum lease duration value for the Client:
set ptp client config eth1 telecom-2008 lease-duration
<duration-value>
 To set the PTP announce receipt timeout value for the Client:
set ptp client config eth1 telecom-2008
announce-receipt-timeout <timeout-value>
 To provision the state for the ETH1 PTP Client port:

set ptp client config eth1 telecom2008 ptp-state {enable |
disable}
 To provision the acceptable master table for PTP client:

set ptp client config eth1 telecom2008 master-table add
index {1 | 2} address < ipv4-address>
Note: All master IP addresses configured in the master table

must be reachable, either by being in the same subnet as the
port (ETH1) IP address, or through a configured gateway. If
either of the master addresses is not reachable through the
network configuration, then neither of the masters will be
utilized for PTP even if one master is correctly addressed.
set ptp client config eth1 telecom2008 master-table delete

index {1 | 2}
set ptp client config eth1 telecom2008 master-table clear
 To provision the PTP domain value for the Client:

set ptp client config eth1 telecom2008 domain <domain-value>

Chapter 3
 To provision the PTP Diffserv Code Point value for the Client:
set ptp client config eth1 telecom2008 dscp <dscp-value>

 To provision the announce interval for the Client:
set ptp client config eth1 telecom2008 announce-interval
<announce-interval-value>

 To provision the sync interval for the Client:
set ptp client config eth1 telecom2008 sync-interval
– The interval is 2z seconds, where z= <sync-interval-value>.
 To provision the delay request interval for the Client:

set ptp client config eth1 telecom2008 delay-req-interval
<delay-req-interval-value>
– The interval is 2z seconds, where z= <delayReqInterval-value>.
 To provision the IP Header Time to Live (TTL) field for PTP packets for a Client:
set ptp client config eth1 telecom2008 ttl <TTL-value>
Table 3-7. PTP Master  Default and Ethernet Default Profile (Multicast) Parameter Descriptions
Parameter Description
two-step Use to enable the grandmaster for two-step clock mode on

the specified port. If two-step clock mode is disabled, the
grandmaster uses one-step clock mode.
timescale Use to select the timescale for the selected port. Use the
PTP timescale if the Grandmaster has a GNSS or PTP
connection for the clock. Use the ARB timescale if the
Grandmaster has an E1, T1, or SyncE signal for the clock.
Use the AUTO setting (recommended) to have the
Grandmaster automatically set the timescale based on the
selected clock source, GPS, T1/E1, PTP, or SyncE.
ptp-state Use to enable or disable PTP functionality for the specified

port.

Chapter 3
ttl Use to set the IP header Time-to-Live value This field is

used to limit how many hops a packet will be transmitted in
a network.
This parameter does not apply to the Ethernet Default

profile.
priority-1 Sets the advertised Priority 1 value for the Grandmaster for
the specified port. PTP clients use the Best Master Clock
(BMC) algorithm to determine which Grandmaster provides
the best signal by first comparing Priority 1 values, then
dynamic elements from the Grandmasters (such as clock
class, accuracy and variance), and then Priority 2 values.
priority-2 Sets the advertised Priority 2 value for the Grandmaster for
the specified port. Clients use the Best Master Clock (BMC)
algorithm to determine which Grandmaster provides the
best signal by first comparing Priority 1 values, then
dynamic elements from the Grandmasters (such as clock
class, accuracy and variance), and then Priority 2 values.
domain Sets the domain value for the Grandmaster clock.

IEEE-1588-2008 defines a domain as a logical grouping of
clocks that synchronize to each other using the protocol,
but that are not necessarily synchronized to clocks in
another domain.
dscp The Differentiated Services Code Point is an 6-bit field in

the 8-bit Differentiated Services (DS) field of the IP packet
header to specify what classes of traffic will be provided,
what guarantees are needed for each class, and how much
data will be sent for each class. When used with the TP
2300/2700, it provides a way to prioritize packets for PTP
traffic.
This parameter does not apply to the Ethernet Default

profile.
dither This is an advanced feature in which an intentionally

applied form of noise is used to randomize quantization
error, and thus to break up any undesirable synchronizing
effects with the network. With dither enabled, the TP
2300/2700 varies the T1 timestamp by a pseudo-random
sequence with peak variations of no more than +/- 800
msec.

Chapter 3
client-timeout Sets the client timeout value. If less than several hundred
delay request messages have been received from a client
before the specified client timeout value, the Grandmaster
removes that client from the client list. If delay requests are
sent at a slow rate, then the client-timeout value must be
increased.
Applies to Default (Multicast) ptp profile.
announce-receipt-timeout Sets the announce timeout value for Multicast. This should
be set to a consistent value in the PTP domain.
vlanid Sets the VLAN ID for the Grandmaster in Multicast (default)

profile. A VLAN ID of 0 is used to specify that no VLAN is
being used. Only one VLAN will be supported in this
profiles.
announce-interval Sets the announce interval for the TP 2700 Grandmaster,

how often to send announce messages to clients on the
specified port. Applies to Default (Multicast) PTP profiles
The interval is 2z seconds, where z= <announce-int-value>.
See Table 3-8 for interval values vs. message rates.
sync-interval Sets the synchronization interval for the TP 2300/2700

Grandmaster, how often to send synchronization messages
to clients on the specified port. Applies to Default (Multicast)
PTP profiles.
The interval is 2z seconds, where z= <sync-int-value>.

Chapter 3
delay-interval Sets the minimum delay interval for the TP 2300/2700

grandmaster. This value is put in the logMessageInterval
field in the delay response messages from the TP
2300/2700. The clients should use this field to determine
the minimum interval that the client will send delay request
messages to the TP 2300/2700. Applies to Default (Layer 3
Multicast) and Ethernet Default (Layer 2 Multicast) PTP
profiles.
The interval is 2z seconds, where z= <delay-int-value>.
service-load-alarm- Service load is a measure of the used service bandwidth.

threshold In Multicast Profiles, the service load calculations are based
on the total number of Delay Request packets per second
of all clients divided by the maximum number of licensed
packets. The maximum number of licensed packets is the
number of licensed clients multiplied by the maximum
number of Delay Request packets per second per client
= number of licensed clients * 128 Packets/second.
Example - max licensed packets:

If a 32-client license is installed, the maximum number of
licensed packets = 32 clients * 128 packets/sec
= 4096 packets per second.
Example - service load:

If a 32-client license is installed and the TP 2300/2700 is
servicing 16 clients at 32 packets per second, the total
number of packets = 16 clients * 32 packets per second =
512 packets per second. With a max number of licensed
packets for 32 clients at 4096 packets per second, the
service load = (512 p/s) / (4096 p/s ) * 100% = 12.5%
which is rounded to 13%.
An alarm will be triggered if the service load ever exceeds

this threshold value. Range is from 10% to 100%. The
alarm will not be generated if the threshold is set to 100%.
The alarm will get cleared when the service load drops to
5% below this provisioned value.
Note: The alarm threshold can be changed when the alarm

is active but the PTP service must be restarted. This can be
done by disabling PTP service and then re-enabling it
instead of rebooting the entire system.

Chapter 3
Table 3-8. Interval Values and PTP Message Rates
Interval Between Message Rate

Value (z) 2z Messages (s)
-7 2-7 1/128 128 PTP messages per second
0 20 1 1 PTP message per second
1 21 2 1 PTP message every 2 seconds

Chapter 3
Table 3-9. PTP Master  Telecom-2008 & ITU-G8265-1 Profiles (Unicast) Parameter Descriptions
two-step Use to enable the grandmaster for two-step clock mode on the
specified port. If two-step clock mode is disabled, the
grandmaster uses one-step clock mode.
timescale Use to select the timescale for the selected port. Use the PTP
timescale if the Grandmaster has a GNSS or PTP connection for
the clock. Use the ARB timescale if the Grandmaster has an E1,
T1, or SyncE signal for the clock. Use the AUTO setting
(recommended) to have the Grandmaster automatically set the
timescale based on the selected clock source, GPS, T1/E1, PTP,
or SyncE.
ptp-state Use to enable or disable PTP functionality for the specified port.
ttl Use to set the IP header Time-to-Live value This field is used to
limit how many hops a packet will be transmitted in a network.
priority-1 Sets the advertised Priority 1 value for the Grandmaster for the
specified port. PTP clients use the Best Master Clock (BMC)
algorithm to determine which Grandmaster provides the best
signal by first comparing Priority 1 values, then dynamic
elements from the Grandmasters (such as clock class, accuracy
and variance), and then Priority 2 values.
priority-2 Sets the advertised Priority 2 value for the Grandmaster for the
specified port. Clients use the Best Master Clock (BMC)
algorithm to determine which Grandmaster provides the best
signal by first comparing Priority 1 values, then dynamic
elements from the Grandmasters (such as clock class, accuracy
and variance), and then Priority 2 values.
domain Sets the domain value for the Grandmaster clock.

IEEE-1588-2008 defines a domain as a logical grouping of
clocks that synchronize to each other using the protocol, but that
are not necessarily synchronized to clocks in another domain.
dscp The Differentiated Services Code Point is an 6-bit field in the

8-bit Differentiated Services (DS) field of the IP packet header to
specify what classes of traffic will be provided, what guarantees
are needed for each class, and how much data will be sent for
each class. When used with the TP 2300/2700, it provides a way
to prioritize packets for PTP traffic.
dither This is an advanced feature in which an intentionally applied

form of noise is used to randomize quantization error, and thus to
break up any undesirable synchronizing effects with the network.
With dither enabled, the TP 2300/2700 varies the T1 timestamp
by a pseudo-random sequence with peak variations of no more
than +/- 800 sec.

Chapter 3
Table 3-9. PTP Master  Telecom-2008 & ITU-G8265-1 Profiles (Unicast) Parameter Descriptions
announce-limit Use to limit the minimum interval between announcements

(maximum rate) from the specified TP 2300/2700. This is a way
to restrict how network resources will be utilized.
The interval is 2z seconds, where z= <announce-limit-value>.
sync-limit Use to limit the minimum interval between synchronization

messages (maximum rate) from the specified TP 2300/2700
port. This is a way to restrict how network resources will be
utilized.
The interval is 2z seconds, where z= <sync-limit-value>.
delay-limit Use to limit the minimum interval between delay requests for the
specified TP 2300/2700 port. This is a way to restrict how
network resources will be utilized.
The interval is 2z seconds, where z= <delay-limit-value>.
unicast-negotiation Use to enable or disable the Grandmaster’s ability to dynamically

negotiate with clients for service in Unicast mode.
lease-limit Sets the maximum duration of the lease for clients that have
dynamically negotiated for service in Unicast mode.
service-load-alarm- Service load is a measure of the used service bandwidth.

threshold In Unicast Profiles, the service load is calculated based on the
number of serviced clients divided by the total number of allowed
clients per the installed license.
Example:
If a 32-client license is installed, and the TP 2300/2700 is
servicing 16 clients, then service load = (16 / 32) * 100% = 50%
An alarm will be triggered if the service load ever exceeds the

threshold value. The alarm will get cleared when the service load
drops to 5% below this provisioned value.

Chapter 3
Table 3-10. PTP Client  Parameter Descriptions for Telecom-2008 Profile
transport Network (PTP packet delivery): Ethernet
service-tier PTP sync service tier applies to PTP client port and is
defined by a performance mask which is used to monitor
performance.
asymmetry Use to enable or disable automatic compensation for

network path asymmetry between PTP client input port and
master. Also use to clear asymmetry information.
phase-offset Use to manually set the phase offset value for the PTP client
input port. Changes to outputs will occur anywhere from 10
minutes to 2 hours of setting the phase offset.
A positive offset value will make phase outputs earlier. A
negative offset value will make phase outputs later.
Value is in nanoseconds.
Example: If downstream path from GM to client has 3.4 s

more delay than the upstream path from client to GM, there
is an asymmetry for the round trip of 1.7 s. Use a phase
offset value of 1700.
Note: Manual PTP phase offset value should be set to zero

when the Asymmetry feature is enabled.
cluster_width_1 Floor Packet Percentage (FPP) 1 cluster width, which

defines the designated sample period for FPP1.
Value is in ns.
cluster_width_2 FPP 2 cluster width, which defines the designated sample

period for FPP2.
Value is in ns.
ptp-state Use to enable or disable PTP functionality for the specified

port.
ttl Use to set the IP header Time-to-Live value This field is

used to limit how many hops a packet will be transmitted in a
network.
announce-interval Used on client port to negotiate with master the announce

message rate. This parameter is applicable to Unicast
profiles only.
The interval is 2z seconds, where z=
<announce-limit-value>.

Chapter 3
Table 3-10. PTP Client  Parameter Descriptions for Telecom-2008 Profile (Continued)
sync-interval Used on client port to negotiate with master the Sync

message rate. This parameter is applicable to Unicast
profiles only.
The interval is 2z seconds, where z= <sync-limit-value>.
delay-req-interval Used on client port to negotiate with master the

delay-request message rate. This parameter is applicable to
Unicast profiles only.
The interval is 2z seconds, where z= <delay-limit-value>.
announce-receipt-timeout The announce-receipt-timeout specifies the announce

interval that has to pass without receipt of an announce
message before the occurrence of this event. If this event
happens on the client port, the client port will switch to the
backup Master.
unicast-negotiation Use to enable or disable the client’s ability to negotiate with

Grandmasters for service in Unicast profiles.
lease-limit Sets the PTP lease limit of service with the master. This
parameter is applicable to client port while running Unicast
profiles.
domain Sets the domain value for the Client clock. IEEE-1588-2008
defines a domain as a logical grouping of clocks that
synchronize to each other using the protocol, but that are not
necessarily synchronized to clocks in another domain.
dscp The Differentiated Services Code Point is an 6-bit field in the

8-bit Differentiated Services (DS) field of the IP packet
header to specify what classes of traffic will be provided,
what guarantees are needed for each class, and how much
data will be sent for each class. When used with the TP
2300/2700, it provides a way to prioritize packets for PTP
traffic.
QoS code = 0 means no special priority
master-table A list of IP address, priority, and vlan related to acceptable

PTP masters. The address 0.0.0.0 means no Master is
added under this index.
Vlanid = 0 means no vlan
Example 1:
To set the active-profile of PTP master in eth2 port as telecom-2008:
TP2700>set ptp master active-profile eth2 telecom-2008

Chapter 3
Example 2:
To provision the following attributes of profile telecom-2008 for PTP master in eth2
port:
 ptp state
 ttl
 dscp
 dither
 two-step
 unicast-negotiation
 lease-limit
 announce-limit
 sync-limit
 delay-limit
 priority-1
 priority-2
 domain
 timescale
 service-load-alarm-threshold
Refer to Table B-39, Table B-40, and Table B-41 in Appendix B for range and default
values for PTP parameters.
TP2700>set ptp master config eth2 telecom-2008 ptp-state enable
TP2700>set ptp master config eth2 telecom-2008 ttl 100
TP2700>set ptp master config eth2 telecom-2008 dscp 5
TP2700>set ptp master config eth2 telecom-2008 dither enable
TP2700>set ptp master config eth2 telecom-2008 two-step enable
TP2700>set ptp master config eth2 telecom-2008 unicast-negotiation

enable
TP2700>set ptp master config eth2 telecom-2008 lease-limit 300
TP2700>set ptp master config eth2 telecom-2008 announce-limit -4
TP2700>set ptp master config eth2 telecom-2008 sync-limit -7

Chapter 3
TP2700>set ptp master config eth2 telecom-2008 delay-limit -7
TP2700>set ptp master config eth2 telecom-2008 priority-1 128
TP2700>set ptp master config eth2 telecom-2008 priority-2 128
TP2700>set ptp master config eth2 telecom-2008 domain 8
TP2700>set ptp master config eth2 telecom-2008 timescale auto
TP2700>set ptp master config eth2 telecom-2008

service-load-alarm-threshold 50
Example 3:
To set the active-profile of PTP master in eth2 port as itu-g8265-1:
TP2700>set ptp master active-profile eth2 itu-g8265-1
Example 4:
To provision the following attributes of profile itu-g8265-1 for PTP master in eth2
port:
 ptp-state
 ttl
 dscp
 dither
 two-step
 lease-limit
 announce-limit
 sync-limit
 delay-limit
 priority-1
 priority-2
 domain
 timescale

Chapter 3
TP2700>set ptp master config eth2 itu-g8265-1 ptp-state enable
TP2700>set ptp master config eth2 itu-g8265-1 ttl 200
TP2700>set ptp master config eth2 itu-g8265-1 dscp 200
TP2700>set ptp master config eth2 itu-g8265-1 dither enable
TP2700>set ptp master config eth2 itu-g8265-1 two-step enable
TP2700>set ptp master config eth2 itu-g8265-1

unicast-negotiation enable
TP2700>set ptp master config eth2 itu-g8265-1 lease-limit 800
TP2700>set ptp master config eth2 itu-g8265-1 announce-limit -4
TP2700>set ptp master config eth2 itu-g8265-1 sync-limit -7
TP2700>set ptp master config eth2 itu-g8265-1 delay-limit -7
TP2700>set ptp master config eth2 itu-g8265-1 priority-1 0
TP2700>set ptp master config eth2 itu-g8265-1 priority-2 0
TP2700>set ptp master config eth2 itu-g8265-1 domain 0
TP2700>set ptp master config eth2 itu-g8265-1 timescale auto
TP2700>set ptp master config eth2 itu-g8265-1

Example 5:
To set the active-profile of PTP master on ETH2 port as default:
TP2700>set ptp master active-profile eth2 default
Example 6:
To provision the following attributes of profile default for PTP master in eth2 port:
 ptp-state

Chapter 3
 ttl
 dscp
 dither
 two-step
 priority-1
 priority-2
 timescale
 domain
 announce-receipt-timeout
 announce-interval
 sync-interval
 delay interval
 client-timeout
TP2700>set ptp master config eth2 default ptp-state enable
TP2700>set ptp master config eth2 default ttl 20
TP2700>set ptp master config eth2 default dscp 25
TP2700>set ptp master config eth2 default dither enable
TP2700>set ptp master config eth2 default two-step enable
TP2700>set ptp master config eth2 default priority-1 200
TP2700>set ptp master config eth2 default priority-2 200
TP2700>set ptp master config eth2 default domain 10
TP2700>set ptp master config eth2 default timescale auto
TP2700>set ptp master config eth2 default announce-interval 2
TP2700>set ptp master config eth2 default sync-interval -6
TP2700>set ptp master config eth2 default delay-interval 0
TP2700>set ptp master config eth2 default announce-receipt-timeout 4
TP2700>set ptp master config eth2 default client-timeout 100

Chapter 3
TP2700>set ptp master config eth2 default service-load-alarm-threshold

50
Example 7:
To set the active-profile of PTP master on ETH2 port as ethernet-default:
TP2700>set ptp master active-profile eth2 ethernet-default
Example 8:
To provision the following attributes of profile ethernet-default for PTP master in

eth2 port:
 ptp-state
 ttl
 dscp
 dither
 two-step
 priority-1
 priority-2
 timescale
 domain
 sync-interval
 delay interval
 client-timeout
TP2700>set ptp master config eth2 ethernet-default ptp-state enable
TP2700>set ptp master config eth2 ethernet-default ttl 20
TP2700>set ptp master config eth2 ethernet-default dscp 25
TP2700>set ptp master config eth2 ethernet-default dither enable

Chapter 3
TP2700>set ptp master config eth2 ethernet-default two-step enable
TP2700>set ptp master config eth2 ethernet-default priority-1 200
TP2700>set ptp master config eth2 ethernet-default priority-2 200
TP2700>set ptp master config eth2 ethernet-default domain 10
TP2700>set ptp master config eth2 ethernet-default timescale auto
TP2700>set ptp master config eth2 ethernet-default announce-interval 2
TP2700>set ptp master config eth2 ethernet-default sync-interval -6
TP2700>set ptp master config eth2 ethernet-default delay-interval -6
TP2700>set ptp master config eth2 ethernet-default

announce-receipt-timeout 4
TP2700>set ptp master config eth2 ethernet-default client-timeout 100
TP2700>set ptp master config eth2 ethernet-default

Example 9:
To set the active-profile of PTP client in eth1 port as telecom-2008:
TP2700>set ptp client active-profile eth1 telecom-2008
Example 10:
To provision the following attributes of profile telecom-2008 for PTP client in eth1
port:
 ptp-state
 ttl
 dscp
 lease-duration
 sync-interval
 delay-req-interval

Chapter 3
 domain
 service tier
TP2700>set ptp client config eth1 telecom-2008 ptp-state enable
TP2700>set ptp client config eth1 telecom-2008 ttl 10
TP2700>set ptp client config eth1 telecom-2008 dscp 8
TP2700>set ptp client config eth1 telecom-2008 unicast-negotiation

enable
TP2700>set ptp client config eth1 telecom-2008 lease-duration 300
TP2700>set ptp client config eth1 telecom-2008 announce-interval -4
TP2700>set ptp client config eth1 telecom-2008 announce-receipt-timeout

5
TP2700>set ptp client config eth1 telecom-2008 sync-interval -7
TP2700>set ptp client config eth1 telecom-2008 delay-req-interval -7
TP2700>set ptp client config eth1 telecom-2008 domain 5
TP2700>set ptp client config eth1 telecom-2008 service-tier packet-prs
Are you sure you want to change the service tier, if yes, the
system will be restarted? (yes|no)
Example 11:
To add masters to the PTP master table for PTP client in eth1 port:
TP2700>set ptp client config eth1 telecom-2008 master-table add index 1

address 192.168.1.11
TP2700>set ptp client config eth1 telecom-2008 master-table add index 2

address 192.168.5.11
Example 12:
To delete a master from the PTP master table for PTP client in eth1 port:
TP2700>set ptp client config eth1 telecom-2008 master-table delete

index 2

Chapter 3
Example 13:
To delete all masters from the PTP master table for PTP client in eth1 port:
TP2700>set ptp client config eth1 telecom-2008 master-table clear

Chapter 3
reboot system
This command restarts the TimeProvider 2300/2700 system. Using this command
can cause a loss of outputs.
Command Syntax:
reboot system
Remarks:
Example 1:
TP2700> reboot system
Response 1:
The system is going down for REBOOT NOW!

........................................
Microsemi TimeProvider:
login:
TP2700>
Level : Admin

Chapter 3
show ref
Use this command to display the configuration for reference selection including
reference selection criteria, input priorities and configured PQL values, switching
mode, and the reference status.
Command Syntax:
 To display the configuration for reference selection:

show ref config
 To display the reference status:

show ref status
Example 1:
TP2700> show ref config
Response 1:
Reference Criteria : priority

Reference Switch Mode : AutoReturn
Time Reference Config
--------------------------------------------------
|Reference |Priority |config-PQL |use-config-pql |
|----------|---------|-----------|---------------|
|GNSS |2 |3 | enable |
|..........|.........|...........|...............|
|PTP |1 |1 | enable |
--------------------------------------------------
Frequency Reference Config
--------------------------------------------------
|----------|---------|-----------|---------------|
|GNSS |2 |3 |enable |
|..........|.........|...........|...............|
|PTP |1 |1 |enable |
|..........|.........|...........|...............|
|SYNCE |4 |3 |enable |
|..........|.........|...........|...............|
|T1E1 |3 |3 |disable |
--------------------------------------------------

Chapter 3
Example 2:
TP2700> show ref status
Response 2:
Time Reference Status
------------------------------------
|Reference |final-pql|status |
|----------|---------|-------------|
|GNSS |1 |disqualified |
|..........|.........|.............|
|PTP |3 |selected |
------------------------------------
Frequency Reference Status
------------------------------------
|----------|---------|-------------|
|GNSS |1 |disqualified |
|..........|.........|.............|
|PTP |3 |selected |
|..........|.........|.............|
|SYNCE |3 |qualified |
|..........|.........|.............|
|T1E1 |16 |disqualified |
------------------------------------
set ref
Use this command to provision the system's reference port(s) priority, configured
quality Level (PQL), reference selection criteria, and reference switching mode.
The Timing References includes GNSS (GPS/GLONASS), and PTP (with PTP
timescale) inputs.
The frequency references includes GNSS, T1/E1, SyncE and PTP inputs.
Command Syntax:
 To set the priority for a time reference input:

Chapter 3
set ref time priority {gnss | ptp} {1 - 10}
 To set the config-PQL value for a time reference input:

set ref time config-pql {gnss | ptp} {1 - 16}
 To set the priority for a frequency reference input:

set ref frequency priority {gnss | ptp |synce | t1e1}
{1 - 10}
 To set the config-PQL value for a frequency reference input:

set ref frequency config-pql {gnss | ptp |synce | t1e1}
{1 - 16}
 To configure reference inputs (time or frequency) to use either the

user-provisioned PQL value or the received PQL value :
set ref use-config-pql {gnss | ptp |synce | t1e1}
{enable | disable
– A setting of enable for use-config-pql means that the system will

apply the user-provisioned PQL value rather than the received PQL value
for reference selection.
 To set the criteria for reference selection from reference inputs (time and
frequency)
set ref criteria {priority | pql}
– When reference criteria is set to PRIORITY, the system selects the

reference based on the priority setting. When reference criteria is set to
PQL, the system selects the reference based on the PQL (received or
provisioned).
– Manual selection of a reference input can be done by disabling all
reference input ports except the desired one.
 To set the reference switching mode
set ref switch-mode {auto-return | auto-switch}
– In auto-return mode, the reference auto selection algorithm switches to

the best reference immediately whenever it detects a better priority or PQL
value than the current reference among the qualified input ports. In this
mode, the system is fully automatic.
– In auto-switch mode, the current selected reference will not switch to
another valid input port until it is disqualified or the reference is manually
disabled.
Example 1:

Chapter 3
To set the priority to 2 for a GNSS time reference input:
set ref time priority gnss 2
Example 2:
To set the config-PQL value to 4 for a GNSS time reference input:
set ref time config-pql gnss 4
Example 3:
To set the priority value to 6 for a SyncE frequency reference input:
set ref frequency priority synce 6
Example 4:
To set the config-PQL value to 5 for a T1/E1 frequency reference input:
set ref frequency config-pql t1e1 5
Example 5:
To configure the PTP reference inputs to use either the user-provisioned PQL value:
set ref use-config-pql ptp enable
Example 6:
To set the unit for reference selection based on Priority values
set ref criteria priority
Example 7:
To set the reference switching to auto-return mode:
TP2700> set ref switch-mode auto-return
Defaults:
use-config pql = enable
reference switch = auto-return (for both time and frequency)
Reference Priority pql

-------------------------------------------
GNSS 1 1
PTP 2 3
SYNCE 3 3
T1E1 4 3

Chapter 3

Chapter 3
show-session-timeout
For current opened user interface session, this command displays the inactivity
timeout to the defined time interval, in seconds. 0 means the time-out for this
session is disabled.
Command Syntax:
 To display the session timeout:

show-session-timeout
Example:
TP2700>show-session-timeout
Response:
The current session timeout - 1800 sec
set-session-timeout
This command sets the inactivity timeout to the defined time interval, in seconds.
This setting is only used for the current CLI session.
Command Syntax:
set-session-timeout <value>
Example:
TP2700>set-session-timeout 1800
Range: 0, 600 to 86400 seconds
Default: 900 seconds

Chapter 3
show snmp
Use these commands to display the SNMP Manager assigned to the agent, all
assigned users (username only), and the SNMP trap version and SNMP trap user.
Command Syntax:
 To display the SNMP manager assignment:

show snmp manager
 To display the SNMPv3 user configuration:

show snmp user
 To display the SNMP TRAP user information (user names only):

show snmp trapuser
 To display the SNMP v2-community information:

show snmp v2-community
 To display the SNMP V2 state:

show snmp state-v2
 To display the SNMP trap version:

show snmp trapversion
Example 1:
TP2700> show snmp manager
Response 1:
-----------------------------------------------------------------------------
|Index|Manager ID |Manager Addr |Engine ID |
|-----|---------------|--------------------|--------------------------------|
|1 |m192.168.5.187 |192.168.5.187 |0x63000000a1c0a805bb |
|.....|...............|....................|................................|
|2 |m192.168.5.144 |192.168.5.144 |0x0123456789010384 |
|.....|...............|....................|................................|
|3 |m192.168.5.171 |192.168.5.171 |0x63000000a1c0a805bb |
|-----------------------------------------------------------------------------
Example 2:
TP2700> show snmp user
Response 2:

Chapter 3
--------------------------------------------------------------------------
|Index|User Name |User Type |Auth. Key |Priv. Key |
|-----|--------------------|-------------|---------------|---------------|
|1 |test |snmpnoauth |********** |********** |
|.....|....................|.............|...............|...............|
|2 |harsha |snmpshades |********** |********** |
--------------------------------------------------------------------------
Example 3:
TP2700> show snmp trapuser
Response 3:
No SNMP trap user configured.
Example 4:
TP2700> show snmp v2-community
Response 4:
-----------------------------------------
|Index|Community Name |Access Level|
|-----|--------------------|------------|
|1 |test |readwrite |
|.....|....................|............|
|2 |testteam |readwrite |
-----------------------------------------
Example 5:
TP2700> show snmp state-v2
Response 5:
SNMP v2 state : enable
Example 6:
TP2700> show snmp trapversion
Response 6:
Trap version - v3

Chapter 3
set snmp
Use this command to provision the SNMP v2 state, trap version, user assignment,
manager assignment, and trapuser and v2 community assignments.
Role Max Number
SNMP User 10
Trapuser 3
Manager 3
v2 Community 10
Command Syntax:
 To add an SNMP user or trapuser:

set snmp add {user | trapuser} <name> securelvl {noauth |
auth | priv}
 To add an SNMP v2-community:

set snmp add v2-community <name> securelvl {read-only|
read-write}
 To add an SNMP manager:

set snmp add manager <ip-address> engineid <engine-id>
 To delete an SNMP user, trapuser, or v2-community:

set snmp delete {user | trapuser | v2-community} <name>
 To delete an SNMP manager:

set snmp delete manager <ip-address>
 To set the SNMP trap version to either v2c or v3:

set snmp trapversion {2|3}
 To provision the state of SNMP v2 communities:

set snmp state-v2 {enable | disable}
Example 1:
To add SNMP user named “maynard”, with a security level of “priv”:
TP2700> set snmp add user maynard securelvl priv
Response 1:

Chapter 3
For security level of priv, the TP 2300/2700 will prompt for:
Authentication protocol (MD5 or SHA):

Authentication key [Only chars {a-z,A-Z,0-9,! ( )- _ . ? ~ * @ ^ +
= : / %} are accepted] :
Privacy protocol (DES or AES):
Privacy key [Only chars {a-z,A-Z,0-9,! ( )- _ . ? ~ * @ ^ + = : / %}
are accepted]:
If the security level is auth, the TP 2300/2700 will prompt for:
authkey <authkey-value>
authtype {MD5 | SHA}
Example 2:
To add SNMP v2-community named “groupv2”, with a security level of read-write:
TP2700> set snmp add v2-community groupv2 securelvl

read-write
Example 3:
To add SNMP manager with the IP address 192.168.5.177 and engine ID of

0x12345678901234:
set snmp add manager 192.168.5.177 engineid 0x12345678901234
Example 4:
To delete SNMP trap user named “george3”:
set snmp delete trapuser george3
Example 5:
To delete SNMP manager at IP address 192.168.5.177:
TP2700> set snmp delete manager 192.168.5.177
Example 6:
To set the trap version to SNMP v3:
TP2700> set snmp trapversion 3
Example 7:
To enable SNMP v2 on the TP 2300/2700:
TP2700> set snmp state-v2 enable
Level : Admin

Chapter 3
show ssm-option
Use this command to display whether the E1 or T1 sync network option is selected,
as defined in G.781, for the ETH1 and ETH2 SyncE ports.
Command Syntax:
show ssm-option
Example:
tp2700> show ssm-option
Response:
------------------------------
|Ethernet port|SSM Option |
|-------------|--------------|
|eth1 |ITU option I |
|.............|..............|
|eth2 |ITU option I |
------------------------------
set ssm-option
Use this command to select either E1 or T1 sync network options as defined in
G.781 and used for SyncE.
Command Syntax:
set ssm-option all {option1 | option2}
Example:
To set the ssm-option for ETH1 and ETH2 ports to option1:
tp2700> set ssm-option all option1
Note: The ssm-option only applies to syncE and the ITU-G.8265.1

profile of PTP.

Chapter 3
show status
Use this command to display the following system status information:
 Assigned System Name

 System Date And Time
 System Uptime
 Time Traceable
 Clock Frequency Status
 Clock Timing Status
 Frequency State Duration in Minutes
 Time State Duration in Minutes
 Currently Selected Timing reference Input
 Currently Selected Frequency reference Input
 Packet Service Eth1 mode: PTP client
 Packet Service Eth2 mode: PTP Master
 Eth1 active connector interface: RJ45
 Eth2 active connector interface: SFP
 Frequency Offset
 Phase Offset Value (Valid in fast-lock and normal states)
 Active Alarms #
 System Frequency PQL
See Table 3-11 for descriptions of these status fields.
Command Syntax:
show status
Example:
TP2700> show status
Response:
System name : Timeprovider

System Date and time : 2014-06-27,05:26:38
Time Traceable : YES
System uptime (sec) : 536555
Clock Frequency Status : NORMAL
Clock Time Status : NORMAL
Frequency State Duration (min) : 5001

Chapter 3
Time State Duration (min) : 5001

Currently Selected Frequency reference : GNSS
Currently Selected Timing reference : GNSS
Packet Service Eth1 mode : CLIENT PORT
Packet Service Eth2 mode : MASTER PORT
Eth1 Active connector interface : R1-RJ45
Eth2 Active connector interface : R2-RJ45
Frequency Offset (MDEV ppb) : 0.01
Phase Offset (TDEV ns) : 3.16
Active Alarms : 1
System Frequency PQL : 1
Last Config time : 2014-06-23,17:57:19
Table 3-11. System Status Details
Status Field Description
Assigned System Name Displays assigned system name

System Date And Time Displays system date and time
Time Traceable Indicates if time for the system is traceable. Time is
traceable if time clock state is not warm up or freerun.
SeeTable 3-12 for details about clock states.
System Uptime Number of seconds since the system as rebooted
Clock Frequency Status Frequency clock states can be warmup, freerun, fast,
normal, bridging, holdover, extended holdover, and
recovery
Clock Timing Status Time clock states can be warmup, freerun, fast,
normal, bridging, holdover, extended holdover, and
recovery
Frequency State Duration Indicates how long the clock has been in the current
clock state (in minutes)
Time State Duration Indicates how long the clock has been in the current
clock state (in minutes)
Currently Selected Indicates which input is selected as frequency
Frequency reference reference. Only enabled inputs can be selected as a
reference.
Currently Selected Timing Indicates which input is selected as timing reference.
reference Only enabled inputs can be selected as a reference.
Packet Service Eth1 Indicates whether the ETH1 port is configured as a
mode: PTP client client port or a master port

Chapter 3
Table 3-11. System Status Details (Continued)
Status Field Description
Packet Service Eth2 Indicates whether the ETH2 port is configured as a

mode client port or a master port
Eth1 active connector Indicates whether the active connector for ETH1 is
interface RJ45 or SFP
Eth2 active connector Indicates whether the active connector for ETH2 is
interface RJ45 or SFP
Frequency Offset (MDEV MEDV = square root of the Modified Allan Variation, a
ppb) measure of the average clock stability. It is a unit-less
measure and can be expressed as a ratio.
Phase Offset Value TDEV = Time Variation, a measure of the average
(TDEV ns) clock stability when measured within a time
observation window.
Active Alarms Indicates the number of alarms that have not been
cleared
System Frequency PQL Indicates the PQL value of the frequency output
quality level.
See Appendix D, PQL Mapping for details
Last Config time Indicates the time at which the system was last
configured.

Chapter 3
Table 3-12. Clock Status
Conditions Required
TP 2300/2700 Possible Next
Description for Next Transition
Clock Status State
State
Warmup The unit is warming up. This is Freerun Warm-up complete

the first clock state following
power-up or reboot.
Typical Warm-up time is:
Quartz: 6 minutes
Rubidium: 9 minutes
Note: Warm-up times may vary

based on environmental
conditions and other factors.
Freerun The unit is operating without Fast-track Input becomes qualified

an input reference, but is
ready to use one. This state
will persist if no qualifiable
input reference is provided.
While in this state, the stability
of the clock output is tied to
the internal reference
oscillator.
Fast-track The selected input has been Freerun The unit no longer has a
qualified and the firmware qualified input.
clock servo begins to actively
converge the output to the Normal Clock stabilized
selected input. This is the
transitional phase that leads
to the Normal clock state.
Typical duration for Quartz

and Rubidium: 20 minutes
Normal The unit has a qualified input Recovery Clock not stabilized
and is locked to the reference. adequately
Bridging The unit no longer has a

qualified input.
Bridging The unit no longer has a Holdover Bridging time exceeded

qualified reference, but
remains operating within Normal Input reference re-qualified
performance associated with in less than bridging time.
Normal operation.

Chapter 3
Table 3-12. Clock Status (Continued)
Conditions Required
TP 2300/2700 Possible Next
Description for Next Transition
Clock Status State
State
Holdover The unit no longer has a Recovery Input becomes qualified

qualified reference.
See Table B-23 for typical
holdover times.
Recovery The selected input has been Holdover The unit no longer has a
qualified and the firmware qualified input.
clock servo begins to actively
converge the output to the Normal Clock stabilized
selected input.
Typical Convergence Times

from Holdover to Normal
(Rb and Qz) are:
GPS Reference:
 Time: For error of
<2 s, 1 ns/s slew rate
to within 100ns.
For error of >2s,
system may
instantaneously move
the phase to correct
value.
 Frequency: 15 minutes
PTP Reference:
 Time: <2 hours for
sync-mask using
G.8261 tests, with unit
warmed up
4 hours for sync-mask
and
sync-extended-mask
(time not specified for
other service tiers)
 Frequency: 15 minutes

Chapter 3
Figure 3-1. Clock States

Chapter 3
show synce
Use this command to display SyncE status and configuration.
Command Syntax:
show synce status {eth1 | eth2 | all}
show synce config {eth1 | eth2 | all}
Example 1:
TP2700> show synce config eth1
Response 1:
SyncE Config:
----------------------------
|Port |State |QL State|
|------|----------|--------|
|eth1 |enable |enable |
----------------------------
Example 2:
TP2700> show synce config eth2
Response 2:
----------------------------
|------|----------|--------|
----------------------------
Example 3:
TP2700> show synce config all
Response 3:
----------------------------
|------|----------|--------|
|......|..........|........|
----------------------------

Chapter 3
Note: QL is always ENABLE on ETH1.
Example 4:
TP2700> show synce status eth1
Response 4:
--------------------------------------------------------
| Port | Direction | Ethernet Mode | RxSSM | TxSSM |
|.......|...........|................|........|........|
| Eth1 | input | asynchronous | 0x0f | 0x0f |
|......................................................|
Table 3-13. Show SyncE Status Parameter Descriptions
Direction Direction that syncE is configured for - input or output.
PHY status Status of 1000BT PHY. This is not applicable for 100M or SFP.
Ethernet Mode Displays whether port is in synchronous or asynchronous mode.
RxSSM Displays syncE SSM value received via ESMC messaging.
TxSSM Displays syncE SSM value being transmitted via ESMC messaging.
Example 5:
TP2700> show synce status eth2
Response 5:
--------------------------------------------------------
|.......|...........|................|........|........|
| Eth2 | output | synchronous | 0x0f | 0x0f |
............................................ ...........
Example 6:
TP2700> show synce status all
Response 6:

Chapter 3
--------------------------------------------------------
|.......|...........|................|........|........|
| Eth1 | input | asynchronous | 0x0f | 0x0f |
|.......|...........|................|........|........|
| Eth2 | output | synchronous | 0x0f | 0x0f |
............................................ ...........
set synce
Use these commands to:
 enable or disable the state for SyncE on the PTP-SyncE service port
 enable or disable the QL state for PTP-SyncE service port
Command Syntax:
 To set the SyncE state for the specified PTP/SyncE port:

set synce state {eth1 | eth2} {enable | disable}
 To set the SyncE QL state:

set synce ql-state eth2 {enable | disable}
Note: SyncE direction is not user-configurable for the initial release.

The ETH1 port is a SyncE Input, and ETH2 is a SyncE Output.
Example 1:
To enable SyncE for the ETH2 port:
TP2700> set synce state eth2 enable
Example 2:
To disable QL-state for ETH2 port:
TP2700> set synce ql-state eth2 disable
Remarks: This command only applies to PTP/SyncE ports.

Chapter 3
Note: With 1000BT Ethernet, one device is the master and the other
is the client. For SyncE, the source of synchronization must be the
1000BT master. Therefore, the Ethernet port for the source of SyncE
synchronization will be configured as master and the other device will
be configured as a client. If both devices are configured as masters or
both as clients, then an error condition exists and the TP 2300/2700
will generate an alarm. If SyncE is enabled, the TP 2300/2700 will
configure the ETH1 port as a client and the ETH2 port as a master. If
the "SyncE Ethernet Configuration Failure" alarm is active, then the
configuration of the device connected to the TP 2300/2700 should be
corrected.

Chapter 3
test
Use this command to generate event/alarm test messages. Test messages can be
generated for an individual event/alarm number or for all events/alarms.
Command Syntax:
test alarm-event {all | [1 to 155]}
Note: Responses to the test command will use a value of 0 for

the secondary index for all events. This value may not be
normally be used for actual alarm/events. See Table A-2 for
details of valid values for the secondary index.

Chapter 3
transfer
Use this command to transfer the debug log file to a remote computer. Specify the
filename, IP address, user ID and password of the SCP server.
Command Syntax:
transfer diag index <0..6> filepath

scp:<scp-server-ip-address> <username>
Example:
To transfer the internal debug log to a user specified file path of

“symm/TimeProvider_EdgeMaster/debuglog”, scp server IP address 192.168.5.56,
username: “bob321”, Password: “bob123!”.
TP2700> transfer diag index 1

symm/TimeProvider_EdgeMaster/debuglog scp:192.168.5.56
bob321 <enter>
Response:
Password: bob123! <enter>
Related Commands:
set log diag state

Chapter 3
upgrade
Use this command to upgrade TimeProvider 2300/2700 firmware with the specified
filename. The user must provide the IP address, username, and password (when
prompted) of the FTP or SCP server where the firmware file is stored. The upgrade
will take approximately 7 minutes to complete.
Command Syntax:
upgrade <filepath> {ftp: | scp:} <ftp-ip-address> <username>
Note: The FTP firewall is set to “Block” by default. Use the following
command to set the firewall to “Allow” for ftp communications:
set firewall mgmt ftp allow
Note: The TimeProvider 2700 only supports active FTP; it does not
support passive (PASV) mode.
Remarks: Firmware upgrades will not be implemented until the system is rebooted.
Example 1:
To upgrade the TimeProvider 2300/2700 using the upgrade file path of

“/symm/TimeProvider_EdgeMaster/current_upd”, FTP server IP address
192.168.5.56, username: “bob321”, Password: “bob123!”.
TP2700> upgrade /symm/TimeProvider_EdgeMaster/current_upd

ftp:192.168.5.56 bob321 <enter>
Response 1:
Do you want to restart the module after the firmware is

upgraded?
Please Confirm (yes|no): <enter>
Upgrade of TIMEPROVIDER is in progress
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade of TIMEPROVIDER is successfully completed
Example 2:

Chapter 3

“/symm/TP2700/current_upd”, SCP server IP address 192.168.5.57, and a user
name of “bob321”.

scp:192.168.5.57 bob321
Response 2:
See Response 1.
Level : Admin

Chapter 3
show user
This command displays the list of users assigned access privileges to the system.
Command Syntax:
show user
Example:
TP2700> show user
Response:
-----------------------------------------
|Index|User Name |Access Level|
|-----|--------------------|------------|
|1 |admin |admin |
|.....|....................|............|
|2 |bobo |admin |
-----------------------------------------
set user
Use this command to provision the local user password and access level, to delete
the specified user, and to modify the password of a specified user.
Command Syntax:
 To add a new user:

set user add name <username> access-level {user | config |
admin}
 To modify the password of an existing user:

set user modify <username> password
 To delete a user:
set user delete <username>
Example 1:
To add a new user “tester123” with an access level of “config”:
TP2700> set user add name tester123 access-level config
Response 1:

Chapter 3
Prompt for password
Example 2:
To modify the password for user “tester123”:
TP2700> set user modify tester123 password
Response 2:
Prompt for new password
Example 3:
To delete user “tester123” 
TP2700> set user delete tester123
Level : Admin
Note: Take care to avoid losing admin passwords or deleting all

admin users. Adding new users requires at least one admin user.
Contact Microsemi support for the password recovery procedure if all
admin-level user passwords are lost.

Chapter 3
show vlan
Use this command to display the VLAN mode and VLAN configuration for a
specified service port, including VLAN ID, Index value, priority, state, and Host,
Netmask, and Gateway IP address.
Command Syntax:
 To display the VLAN mode for all packet service ports:

show vlan mode
 To display the VLAN configuration for the specified port:

show vlan config {eth1 | eth2}
Example 1:
To display the VLAN mode for ETH1 and ETH2:
TP2700> show vlan mode
Results 1:
VLAN Mode Configuration:
eth1: enable
eth2: disable
Example 2:
To display the VLAN configuration info for PTP client port ETH1:
TP2700> show vlan config eth1
Results 2:
Vlan configuration for eth1 port:
Idx VID P STATE Address Netmask Gateway/NextHop Destnetwork
1 11 0 en 10.11.11.101 255.255.255.0 0.0.0.0 n/a

2 12 0 en 10.12.11.101 255.255.255.0 0.0.0.0 n/a
Example 3:
To display the VLAN configuration info for PTP server port ETH2:
TP2700> show vlan config eth2

Chapter 3
Results 3:
Vlan configuration for eth2 port:
Idx VID P STATE Address Netmask Gateway/NextHop Destnetwork
1 11 0 en 10.11.11.101 255.255.255.0 0.0.0.0 n/a

2 12 0 en 10.12.11.101 255.255.255.0 0.0.0.0 n/a
3 13 0 en 10.13.11.101 255.255.255.0 0.0.0.0 n/a
4 14 0 en 10.14.11.101 255.255.255.0 0.0.0.0 n/a
. . .
15 34 0 en 10.34.11.101 255.255.255.0 0.0.0.0 n/a

16 44 0 en 10.44.11.101 255.255.255.0 0.0.0.0 n/a
17 22 0 en 10.21.21.101 255.255.255.0 20.20.20.1 20.20.20.0/24
18 23 0 en 10.31.31.101 255.255.255.0 30.30.30.1 30.30.30.0/24
19 24 0 en 10.41.41.101 255.255.255.0 40.40.40.1 40.40.40.0/24
20 25 0 en 10.51.51.101 255.255.255.0 50.50.50.1 50.50.50.0/24
21 26 0 en 10.61.61.101 255.255.255.0 60.60.60.1 60.60.60.0/24
22 27 0 en 10.71.71.101 255.255.255.0 70.70.70.1 70.70.70.0/24
23 82 0 en 10.81.81.101 255.255.255.0 80.80.80.1 80.80.80.0/24
24 29 0 en 10.91.91.101 255.255.255.0 90.90.90.1 90.90.90.0/24
25 30 0 en 10.101.101.101 255.255.255.0 100.100.100.1 100.100.100.0/24
26 31 0 en 10.111.111.101 255.255.255.0 10.110.110.1 10.110.110.0/24
27 32 0 en 10.121.121.101 255.255.255.0 10.120.120.1 10.120.120.0/24
28 33 0 en 10.131.131.101 255.255.255.0 10.130.130.1 10.130.130.0/24
29 34 0 en 10.141.141.101 255.255.255.0 10.140.140.1 10.140.140.0/24
30 35 0 en 10.151.151.101 255.255.255.0 10.150.150.1 10.150.150.0/24
31 36 0 en 10.161.161.101 255.255.255.0 10.160.160.1 10.160.160.0/24
32 ..
33 ..
..
64 ..m
Note: The first 4 VLAN in the index are the default VLANs which can
use the default gateway. The rest of the VLANs are non-default
VLANs, static routes in which the next hop and the destination
network must be defined.
set vlan
This command is used to enable or disable the VLAN mode for an Ethernet port,
and to provision all the VLAN and IP parameters under VLAN structure.

Chapter 3
In VLAN enable mode, all the IP configurations are provisioned by set vlan config
command. If VLAN mode is disabled, the IP configurations are provisioned by set
ip command.
The command is also used to add a new VLAN configuration to an Ethernet port
and provision its Host, Mask, and Gateway IP addresses. This command also can
be used to modify or delete an existing VLAN configuration. Each VLAN must be
configured with its own IP address on a separate network/subnet.
Note: If the Ethernet interface is not to be part of a VLAN, use the

command set ip, on page 103 to provision the IP addresses instead.
The PTP server port, ETH2 (R2 or S2) can support up to 64 VLAN channels.
– The first 16 VLANs (Index = 1 to 16) on the PTP server port can be
configured with the default gateway.
– The non-fixed VLANs (up to 48) can be configured with one static route.
When a non-fixed VLAN is removed, the route will be automatically
deleted.
The PTP client port, ETH1 (r1 or s1) can support 2 VLAN channels.
When using VLANs, the network administrator should configure the Ethernet
switches and/or router to handle the VLANs.
Command Syntax:
 To provision the VLAN mode for the specified port or expansion shelf:
set vlan mode {eth1 | eth2} {enable | disable}
Note: Wait 30 seconds after executing the command "set vlan mode
ethx" before issuing the next command.
To provision PTP Client Port ETH1:
 To add a fixed VLAN (default) with IPv4 address for the PTP client port, ETH1:
set vlan config eth1 add index {1 | 2} vlan-id <vlan-id>
priority <priority> ipv4 address <ipv4-address> netmask
<ipv4-mask> gateway <ipv4-gateway>
Note: If a gateway router is not required, then set the gateway value
to the special value of 0.0.0.0

Chapter 3
 To modify the IP address, netmask, or gateway for an existing fixed (default)

VLAN configuration with IPv4 address for the PTP client port, ETH1:
set vlan config eth1 modify index {1 | 2} vlan-id <vlan-id>
ipv4 address <ipv4-address> netmask <ipv4-mask> gateway
<ipv4-gateway>
 To delete a fixed VLAN configuration for the specified index for the PTP client
port, ETH1:
set vlan config eth1 delete index {1 | 2}
 To provision the state of the fixed VLAN for the specified index for the PTP client
port, ETH1:
set vlan config eth1 state index {1 | 2} {enable | disable}
To provision PTP Server Port ETH2:
 To add a fixed VLAN (default) with IPv4 address for the specified port:
set vlan config eth2 add index <1-16> vlan-id <vlan-id>
<ipv4-mask> gateway <ipv4-gateway>
Note: If a gateway router is not required, then set the gateway value
to the special value of 0.0.0.0
 To add a non-fixed VLAN with IPv4 address:

set vlan config eth2 add non-fixed vlan-id <vlan-id>
<ipv4-mask> next-hop <ipv4-addr> dest-network
<ipv4-network-prefix/prefix-length>
 To modify the IP address, netmask, or gateway for an existing fixed (default)

VLAN configuration with IPv4 address on the specified port:
set vlan config eth2 modify index <1-16> vlan-id <vlan-id>
ipv4 address <ipv4-address> netmask <ipv4-mask> gateway
<ipv4-gateway>
 To modify the IP address, netmask, or gateway for an existing non-fixed VLAN

configuration on the specified port:
set vlan config eth2 modify non-fixed vlan-id <vlan-id> ipv4
address <ipv4-address> netmask <ipv4-mask> next-hop
<ipv4-addr> dest-network <ipv4-network-prefix/prefix-length>
 To delete a fixed VLAN configuration for the specified index on the specified port:
set vlan config eth2 delete index <1-16>
 To delete a non-fixed VLAN configuration for the specified VLAN ID on the

specified port:

Chapter 3
set vlan config eth2 delete non-fixed vlan-id <vlan-id>
 To provision the state of the fixed VLAN for the specified index on the specified
port:
set vlan config eth2 state index <1-16> {enable | disable}
 To provision the state of the non-fixed VLAN for the specified VLAN ID on the
specified port:
set vlan config eth2 state non-fixed vlan-id <vlan-id>
{enable | disable}
Use set ip state <port> restart after modifying VLAN configuration using the
command “.set vlan-config modify...”.
Note: Each VLAN must be configured on a separate network/subnet.
Range: Index = 1  16 (for default)

vlan-id = 2  4094
priority = 0  7
Default: No VLAN configured
Example 1 PTP Server Port:
To Enable the VLAN mode on PTP server port ETH2:
TP2700> set vlan mode eth1 enable
Note: Wait 30 seconds after executing the command "set vlan mode
ethx" before issuing the next command.
Note: To Enable the VLAN mode for a port, at least one VLAN
(indexed or non-fixed) must be already be configured and Enabled on
the VLAN for that port. See the set vlan config ethx state
command.
To add a fixed VLAN on PTP server port ETH2 with VLAN ID = 25, Index=3,
Priority=0, where the IP address= 192.168.1.5 Netmask=255.255.255.0, and
Gateway=192.168.1.1:
TP2700> set vlan-config eth2 add index 3 vlan-id 25 priority

0 ipv4 address 192.168.1.5 netmask 255.255.255.0 gateway
192.168.1.1

Chapter 3
Example 2a PTP Server Port:
To add a non-fixed VLAN on PTP server port ETH2 with VLAN ID = 99, Priority=5,
where the IP address= 192.168.3.20, Netmask=255.255.255.0, Next
Hop=192.168.3.1 and Destination Network/Net-Prefix=192.168.3.0/24
TP2700> set vlan config eth2 add non-fixed vlan-id 99

priority 5 ipv4 address 192.168.3.20 netmask 255.255.255.0
next-hop 192.168.3.1 dest-network 192.168.3.0/24
To modify Index 3 on an existing fixed VLAN on PTP server port ETH2 with the new
IP address of 192.168.1.7, Netmask=255.255.255.0, and Gateway=192.168.1.1:
TP2700> set vlan config eth2 modify index 3 ipv4 address

192.168.1.7 netmask 255.255.255.0 gateway 192.168.1.1
To modify the existing non-fixed VLAN with VLAN ID of 99 on PTP server port ETH2
with the new IP address of 192.168.3.35, Netmask=255.255.255.0, Next
Hop=192.168.3.1 and Destination Network/Net-Prefix=192.168.3.0/24:
TP2700> set vlan config eth2 modify non-fixed vlan-id 99

ipv4 address 192.168.3.35 netmask 255.255.255.0 next-hop
192.168.3.1 dest-network 192.168.3.0/24
To delete the fixed VLAN configuration for Index 4 on ETH2 port:
TP2700> set vlan config eth2 delete index 4
To delete the non-fixed VLAN configuration for VLAN ID=75 on ETH1 port:
TP2700> set vlan config eth2 delete non-fixed vlan-id 75
To Enable the fixed VLAN configuration for Index 3 on ETH1:
TP2700> set vlan config eth2 state index 3 enable
To Enable the non-fixed VLAN configuration for VLAN ID=75 on PTP server port
ETH2:

Chapter 3
TP2700> set vlan-config eth2 state non-fixed vlan-id 75

enable
Example 6 PTP Client Port:
To add a fixed VLAN on PTP client port ETH1 with VLAN ID = 25, Index=1,
Priority=0, where the IP address= 192.168.1.5 Netmask=255.255.255.0, and
Gateway=192.168.1.1:
TP2700> set vlan-config eth1 add index 1 vlan-id 25 priority

0 ipv4 address 192.168.1.5 netmask 255.255.255.0 gateway
192.168.1.1
To modify Index 2 on an existing fixed VLAN on PTP client port ETH1 with the new
IP address of 192.168.1.7, Netmask=255.255.255.0, and Gateway=192.168.1.1:
TP2700> set vlan-config eth1 modify index 2 ipv4 address

192.168.1.7 netmask 255.255.255.0 gateway 192.168.1.1
To delete the fixed VLAN configuration for Index 2 on PTP client port ETH1:
TP2700> set vlan-config eth1 delete index 2
To enable the fixed VLAN configuration for Index 1 on PTP client port ETH1:
TP2700> set vlan-config eth1 state index 1 enable
Level : Admin

Chapter 3

This chapter describes the procedures for provisioning the TimeProvider

2300/2700. Use the procedures in this chapter after you have installed and powered
up the TimeProvider 2300/2700 (see Chapter 2, Installing).
In This Chapter
 Establishing a Connection to the TimeProvider 2300/2700
 Managing the User Access List
 Provisioning MGMT Ethernet Port
 Provisioning the Service Ethernet Ports
– Ethernet Active Connector
– Ethernet Auto-Negotiation
 Provisioning VLAN
 Provisioning the Input Reference
– Reference Switching Modes
– Reference Selection Criteria
 Provisioning Input Parameters
– Setting PTP Input Client Parameters
– Setting GNSS Parameters
– Setting E1/T1 Input Reference Parameters
– Provisioning SyncE Input
 Provisioning the PTP Output
 Provisioning the Non-PTP Outputs
– Provisioning the T1/E1 Output
– Provisioning TOD+1PPS Output
– Provisioning the 10MHz & 1PPS Output
– Provisioning SyncE Output
– Provisioning Output Generation Behavior
– Quality Levels for Output Signals
 Setting the System Date and Time
 Provisioning Alarms
 Saving and Restoring Provisioning Data
 Provisioning for SNMP
 Testing TP 2300/2700 Provisioning

Establishing a Connection to the TimeProvider 2300/2700
To set up and manage the TimeProvider 2300/2700 with a terminal or a computer

with terminal emulation, you must establish either a serial connection or an Ethernet
connection. To connect through the serial port, see Communicating Through the
Serial Port, on page 206. If the TimeProvider 2300/2700 is connected to an Ethernet
LAN, use the procedure described in Communicating Through the Ethernet Port, on
page 206.
Communicating Through the Serial Port

An EIA-232 serial port is available on the front panel for a direct serial connection to
a terminal or a computer with terminal emulation. Use the following procedure to
connect the TimeProvider 2300/2700 to a terminal or a computer with terminal
emulation via a straight through serial cable:
Note: For information on restricting user access, see Managing the

User Access List, on page 208.
1. Connect one end of a straight through serial cable to the serial port on the
computer or terminal and the other end to the EIA-232 connector on the TP
2300/2700.
2. Configure the emulation software for 8 data bits, 1 stop bit, no parity, 57600 baud
rate, and no flow control.
3. Start the terminal emulation software and press Enter. The system prompt
should appear. If it does not, recheck each step in this procedure.
4. Type your user name and press Enter. The system prompts for a password.
5. Type your password and press Enter. The system prompt appears.
Note: The default user name is “admin”. The default password is:
symmadmin**.
Communicating Through the Ethernet Port

To communicate with the TimeProvider 2300/2700 using an Ethernet LAN
connection, you must first configure the Ethernet port through the EIA-232 serial
port.

Configuring the Ethernet Port

Use the following procedures to configure the TimeProvider 2300/2700 Ethernet
parameters (IP Address, Subnet Mask, and Gateway Address).
Note: The TimeProvider 2300/2700 default IP address is

192.168.0.100, the subnet mask is 255.255.255.0, and the gateway
address is 0.0.0.0 (no gateway). If these defaults are acceptable, the
following procedure using the serial port is not required.
1. Establish a direct serial connection to the TimeProvider 2300/2700 as described

in Communicating Through the Serial Port, on page 206.
2. Provision the IP, Gateway, and Subnet Mask addresses for the TimeProvider
2300/2700. The IT department or site administrator for your location can
recommend specific addresses for these parameters. Use the dotted decimal
format xxx.xxx.xxx.xxx to enter the address parameters with the following
commands:
Note: The telnet firewall is set to Block by default. Use the following
command to set the firewall to Allow for telnet communications:
Example 1  Using Static IP:
TP 2700> set ip address-mode mgmt ipv4 static
TP 2700> set ip ip-address mgmt ipv4 address 192.168.0.10 netmask

255.255.255.0 gateway 192.168.0.254
TP 2700> set ip state mgmt ipv4 restart
Example 2  Using DHCP:
TP 2700> set ip address-mode mgmt ipv4 dhcp
TP 2700> set ip state mgmt ipv4 restart
Connecting Through an Ethernet LAN

1. Ensure that the TimeProvider 2300/2700 is connected to a LAN (see
Communications Connections, on page 53 for details).
2. Telnet from your computer to the IP address assigned to the TimeProvider

2300/2700 (see Configuring the Ethernet Port, on page 207).

Managing the User Access List
Note: SSH can be used to connect to the TP 2300/2700. The SSH

firewall is set to Allow by default.
3. Type your user name and press Enter. If you are not assigned as a user in the
system, contact the system administrator or see Adding a User, on page 210.
4. Type your assigned password and press Enter. The system prompt appears.
When you are logged in at the Admin level you can add, edit, or delete user names
in the user access list. The user list can contain up to 20 names and users can be
set to one of three different security levels described in Table 4-1. Users are
required to enter a user name and password to log in to the system. Users can
access or modify only the parameter settings allowed by their assigned security
level.
Caution: Be sure to not lose or forget the password. Contact

Microsemi support for the password recovery procedure if all
admin-level user passwords are lost.
Table 4-1. User Level and Access
Security Level Description
User Users can edit their password and show information, or access any
command at the User security level.
Config Users are allowed to change configuration and issue User-level

commands.
Admin Users are allowed to modify the security database or download new
firmware and issue commands at any level.
Use the procedures in this section to manage user access to the TimeProvider
2300/2700.

Logging In
Use the following procedure to log in to the system at the admin level.
1. Ensure that the TimeProvider 2300/2700 is connected to a LAN, or directly

connected to a computer through the EIA-232 serial port. See Communications
Connections, on page 53.
2. If the TimeProvider 2300/2700 is connected to a LAN, Telnet or SSH from your

computer to the assigned IP address.
Note: The telnet firewall is set to Block by default. Use the following
command to set the TP 2300/2700 firewall to Allow for telnet
communications:
If the TimeProvider 2300/2700 is connected to a computer directly through the

serial port, start a Terminal session and press Enter.
3. Type your user name and press Enter. The system prompts for a password.
4. Type your password and press Enter. The system prompt appears.
Note: The default user name is “admin” and the default password is:
symmadmin**.
To avoid unauthorized access, you should change the default

password.

Adding a User
Use the following procedure to add a user to the system access list. For this
example, the user name is “tester123” with an access level of “config”,
Note:
User passwords can consist of alphanumeric characters, “~”, “*”, “(“,

“)”, “!”, “?”, “-”, “_”, and “.” with a minimum of 8 characters and a
maximum of 32 characters.
Usernames can consist of numbers, upper and lower case letters,

dash "-", and underscore "_", with a maximum of 20 characters.
Usernames cannot use a leading dash “-” or underscore "_" as the
first character.
For a description of user access levels, see Managing the User

Access List, on page 208.
1. Login at the Admin level (see Logging In, on page 209).
2. Type show user and press Enter to view the current list of users.
3. Type set user add name set user add name tester123 access-level
config and press Enter.
The system will respond with:
For user password, only chars {a-z, A-Z, 0-9, ! ( ) - _ . ? ~ *}

are accepted
Password:
4. Type a password and press Enter. The password you enter will be the log-in
password for the user. The system responds with:
Confirm Password:
5. Retype the password and press Enter. The system responds with:
CLI user has been added: tester123
6. Type show user and press Enter to verify that the account exists.
7. Repeat steps 3 through 6 of this procedure to add other users.

Deleting A User
Use the following procedure to delete user ABCD1234 from the system access list.
Do not delete the default username and password.
3. Type set user delete ABCD1234 and press Enter.
Displaying Current Users and User Access Levels

Use the following procedure to show a list of all assigned users and their access
levels.
2. Type show user and press Enter. The system displays the current list of users.
Changing a User’s Password

Use the following procedure to change a user’s password.
Note:


first character.

3. Type set user modify <user name> password and press Enter.
Follow the prompts. Change the password when prompted.
4. Repeat Steps 2 and 3 to modify other user passwords.

Changing a User’s Access Level

To change a user’s access level you must delete and then re-create the user. This
also provides an opportunity to change the password, if desired. Use the following
procedure to change the access level to “admin” for user “tester123”:
Note:


first character.

3. Type set user delete tester123 and press Enter.
4. Type set user add name set user add name tester123 access-level
admin and press Enter.
The system will respond with:
For user password, only chars {a-z, A-Z, 0-9, ! ( ) - _ . ? ~ *}

are accepted
Password:
5. Type a password and press Enter. The password you enter will be the log-in
password for the user. The system responds with:
Confirm Password:
6. Retype the password and press Enter. The system responds with:
CLI user has been added: tester123
7. Type show user and press Enter to verify that the account exists.
8. Repeat Steps 3 through 7 to modify other user access levels.

Provisioning the Ethernet Ports
Provisioning MGMT Ethernet Port

The TimeProvider 2300/2700 supports static as well as dynamically allocated IP
addresses on the MGMT (Management) port. The dynamically allocated address
requires a connection to a DHCP server. When provisioning the unit for static IP
address, you can set the Host address, Mask address, and Gateway address, or
you can set the addresses to the factory default. See Table B-29 in Appendix B,
Specifications and Factory Defaults for addresses.
Figure 4-1. Set IP Command Hierarchy
DHCP Mode
You can either enable or disable DHCP mode on the MGMT port. See Figure 4-1.
Use the following procedure to configure the TimeProvider 2300/2700 to enable
DHCP on the MGMT port.

Example
1. Login at the Admin or Config-user level (see Logging In, on page 209).
2. Type set ip address-mode mgmt ipv4 dhcp and press Enter.
Static IP Mode
Use the following procedure to configure the TimeProvider 2300/2700 IP
parameters (Host Address, Subnet Mask, and Gateway Address) in Static IP mode
on the MGMT port. Use the dot-decimal notation format xxx.xxx.xxx.xxx to enter the
address parameter. See Figure 4-1.
Example
2. Type set ip address-mode mgmt ipv4 static and press Enter.
3. Type set ip ip-address mgmt ipv4 address 10.6.1.76 netmask

255.255.255.0 gateway 10.6.1.1 and press Enter.
4. Type set ip state mgmt ipv4 restart and press Enter.
DNS Server
You can provision the DNS servers and domain for the Ethernet MGMT port. See
Figure 4-1.
Example
2. Type set ip mgmt dns nameserver1 168.192.0.200 nameserver2

168.192.0.210 domain exampledomain.com
Provisioning the Service Ethernet Ports

The service Ethernet ports, ETH1 and ETH2 can only be configured with static IP
addresses. The IP addresses for the MGMT, ETH1 and ETH2 ports must be on
different networks/subnets.
Ethernet Active Connector

The Ethernet ports on the TP 2300/2700 can be mapped for use with either the
RJ45 connectors, R1 and R2, or the SFP connectors, S1 and S2. The SFP
connectors require 1000M optical transceivers.
1. Login at the admin or Config-user level.
2. Type set ethernet active-connector eth1 s1-sfp and press Enter.

3. Type set ethernet active-connector eth2 s2-sfp and press Enter.
Figure 4-2. Set Ethernet Command Hierarchy
Ethernet Auto-Negotiation
The ETH1 and ETH2 Ethernet ports can be configured to allow automatic
negotiation of their connection speeds. When Ethernet auto-negotiation is enabled,
the TP 2300/2700 will advertise connection speeds of 100/1000M for the RJ45
connectors, R1 and R2, and 1000M for the SFP connectors, S1 and S2. The user
can also specify a connection speed for a port, 100M, 1000M, or All, to configure
the speed used by auto-negotiation. The default for auto-negotiation state is
“enable”. The default value for auto-negotiation speed is “All”.
Note: The SFP ports, S1 and S2, only support optical SFPs,
which are 1000M.
Use the following procedure to configure both Ethernet ports, ETH1 and ETH2, to
allow Ethernet auto-negotiation. In this example, ETH1 port allows all connection
speeds, and ETH2 port only allows a connection speed of 1000M.
1. Login at the admin or Config-user level.
2. Type set ethernet auto-neg state eth1 enable and press Enter.
3. Type set ethernet auto-neg speed eth1 all and press Enter.
4. Type set set ethernet auto-neg state eth2 enable and press Enter.
5. Type set ethernet auto-neg speed eth2 1000m and press Enter.

Provisioning VLAN
Provisioning VLAN
The command for enabling VLAN mode for the Ethernet ports is shown in Figure
4-3.
Note: VLAN mode will not enable unless there is at lease one VLAN
configured and enabled within that Ethernet port.
Figure 4-3. Set Vlan-Mode Command Hierarchy
VLAN on the ETH2 Server Port

The TP 2300/2700 supports up to 64 VLANs on the ETH2 server port. Each VLAN
must be within it own unique network/subnet. There is no default VLAN
configuration.
There are 16 VLANs that can accessed by index. These VLANs can be configured
with a default gateway and are considered “fixed” VLANs. These VLANs can be
deleted with the set vlan config eth2 delete command. The command
hierarchy for configuring fixed VLANs is shown in Figure 4-4. Fixed VLANs include
a gateway address.
The remaining 48 VLANs are considered to be “non-fixed” VLANs, each of which

can be configured with one static route. When a non-fixed VLAN is removed, the
route will be automatically deleted. A non-fixed VLAN can also be deleted by the
user with the set vlan config eth2 delete non-fixed vlan-id command.
The command hierarchy for configuring non-fixed VLANs is shown in Figure 4-5.
Non-fixed VLANs require specification of an IP address for the “next hop” and
network prefix/prefix length for the destination network, instead of the gateway
address.
Example 1

Provisioning VLAN
Use the following procedure to configure a fixed VLAN on the ETH2 port with an
index of 1, an ID of 2 and priority of 3, IPv4 address of 192.168.3.20, a netmask of
255.255.255.0, and a gateway of 192.168.3.1:
1. Login at the Admin or Config-user level.
2. Type set vlan config eth2 add index 1 vlan-id 2 priority 3 ipv4
address 192.168.3.20 netmask 255.255.255.0 gateway 192.168.3.1 and
press Enter.
3. Type set vlan config eth2 state index 1 enable and press Enter.
4. Type set vlan mode eth2 enable and press Enter.
Note: Wait 30 seconds after executing the command set vlan-mode

ethx before issuing the next command.
If a script is used to execute commands, wait for the "reply prompt" to

come back before executing the next command.
5. Type show vlan config eth2 and press Enter to verify the configuration.
6. Type show ip status eth2 and press Enter to verify VLAN is up.
Example 2
Use the following procedure to configure a non-fixed VLAN on ETH2 with VLAN ID
of 99, priority of 5, IPv4 address of 192.168.7.20, a netmask of 255.255.255.0, a
next-hop of 192.168.3.1, and destination network of 192.168.4.0/24:
2. Type set vlan config eth2 add non-fixed vlan-id 99 priority 5 ipv4
address 192.168.7.20 netmask 255.255.255.0 next-hop 192.168.3.1
dest-network 192.168.4.0/24 and press Enter.
3. Type set vlan config eth2 state non-fixed vlan-id 99 enable and
press Enter.
6. Type show ip status eth2 and press Enter to verify VLAN is up.

Provisioning VLAN
Figure 4-4. Fixed VLAN for Server Port— set vlan Commands

Provisioning VLAN
Figure 4-5. Non-Fixed VLAN for Server Port — set vlan Commands

Provisioning VLAN
VLANs on the ETH1 Client Port

The TP 2300/2700 supports one VLAN on the ETH1 client port. Each VLAN must
be within it own unique network/subnet. There is no default VLAN configuration.
Figure 4-6 shows the command for configuring VLANs for the ETH1 client ports.
Example
Use the following procedure to configure a fixed VLAN on ETH1 with index of 1,
VLAN ID of 120, priority of 5, IP address of 192.168.3.100, netmask of
255.255.255.0 and gateway of 192.168.3.1:
2. Type set vlan config eth1 add index 1 vlan-id 120 priority 5 ipv4
address 192.168.3.100 netmask 255.255.255.0 gateway 192.168.3.1
and press Enter.
3. Type set vlan config eth1 state index 1 vlan-id 120 enable and press
Enter.
Note: Wait 30 seconds after executing the command set vlan mode
ethx before issuing the next command.
If a script is used to execute commands, wait for the "reply prompt" to

come back before executing the next command.
6. Type show ip status eth1 and press Enter to verify VLAN is up. For example,
you should see "eth1.120 Link" with the IP address attached.

Provisioning VLAN
Figure 4-6. Fixed VLAN for Client Port— Set Vlan Commands

Provisioning the Input Reference
When operating in normal (locked) mode, the TimeProvider 2300/2700 uses an

external reference, such as GNSS, to acquire the frequency and/or TOD alignment.
Selection among multiple references inputs is based on the priority or PQL value of
each qualified input. (See Appendix D: PQL Mapping, on page 361.) Reference
switching behavior is determined by the switching mode. The reference mode,
criteria, and switching behavior are all configured with the set ref command.
Figure 4-7 shows the set ref command hierarchy.
Figure 4-7. Set Ref Command Hierarchy
Reference Switching Modes

Auto Return Mode
The reference auto selection algorithm switches to the best reference immediately
whenever it is better than the current reference according to the priority or PQL
value among the qualified input ports.

Auto Switch Mode

In Auto-switch mode, the currently selected reference will not switch to another valid
input port until it is disqualified or the reference is manually disabled.
Reference Selection Criteria

Use either the Priority settings or the PQL settings (mapped input PQL values or
user-configured PQL) for each qualified input port to determine which input port to
use as the reference.
Priority
The TP 2300/2700 uses the Priority settings for each qualified input port to
determine which input port to use as the reference. Priority values can be from 1 to
10, where 1 is the highest priority level. If two input ports are set to the same priority
value and both are qualified, the predefined preference is used (see Table 4-2).
Predefined preference has the same value as the default priority value, but cannot
be changed. Reference selection among inputs with the same priority is
non-revertive.
PQL
Different inputs have different ways of specifying their quality levels which are
typically included in their signals. All of them are mapped to a uniform internal
quality ranking called priority quality level (PQL). After all input quality levels are
converted to PQL, the PQL will be used as one of the reference selection criteria.
See Appendix D: PQL Mapping, on page 361 for details on how quality levels are
mapped to PQL values.
SyncE, E1 and T1 synchronization signal quality levels are characterized by SSM.

PTP synchronization signal quality level is characterized by clockClass, which is
included in the Announce message. Input signals like GNSS do not carry a
synchronization signal quality indicator; they are assigned an input PQL value
appropriate to their known quality level. For example, GNSS and cesium clocks are
usually given a PQL value of 1 (the highest quality). See Table 4-2 for default PQL
values for different reference types.
The TP 2300/2700 also allows the user to apply a provisioned PQL value rather
than the received PQL value for each input for reference selection. By inputting a
"configured PQL value", the user implicitly chooses the quality of an input signal
relative to others in the input conversion table. Use the set ref frequency
config-pql or set ref time config-pql command to configure the PQL value
for a reference source. Use the set ref use-config-pql command to enable or
disable use of the configured PQL value.

Table 4-2. Default Priorities and PQL Values for Time and Frequency References
Reference Priority PQL

Input Port
Type (Default) (Default)
Time GNSS Port 1 1
Time ETH1 Port - PTP 2 3
Frequency GNSS Port 1 1
Frequency ETH1 Port - PTP 2 3
Frequency ETH1 Port - SyncE 4 3
Frequency T1 / E1 3 3
Example
To provision the GNSS reference for a TimeProvider 2300/2700, reference selection

criterion of “Priority”, with a priority value of 1 for Time, in GNSS position mode of
“auto”, perform the following steps:
2. Type set ref criteria priority and press Enter.
3. Type set ref switch-mode auto-return and press Enter.
4. Type set ref time priority gnss 1 and press Enter.
5. Type set ref frequency priority gnss 1 and press Enter.
6. Type set gnss track-mode gps and press Enter.
7. Type set gnss posmode auto and press Enter.
8. Type set gnss state enable and press Enter.

Provisioning Input Parameters
Setting PTP Input Client Parameters

The TP 2300/2700 supports the Telecom-2008 unicast profile for the PTP client.
Use the “set ptp client” command to provision the PTP profile and master VLAN
parameters for the client, as shown in Figure 4-8. Use the set ptp client config
command to provision the master table parameters for the client, as shown in Figure
4-9. Use the set ptp client config command to provision the PTP input client
parameters for the ETH1 port, as shown in Figure 4-9 and Figure 4-9. See Table
3-10 for descriptions of PTP client parameters for the Telecom-2008 profile.
The PTP client is capable of receiving and processing messages from both
one-step and two-step clock masters, without any provisioning necessary. The
client auto detects the two-step clock flag in Announce messages from the master
and, based on the setting, runs a one-step or two-step clock operation.
Note: All master IP addresses configured in the master table

must be reachable, either by being in the same subnet as the
port (ETH1) IP address, or through a configured gateway. If
either of the master addresses is not reachable through the
network configuration, then neither of the masters will be
utilized for PTP even if one master is correctly addressed.
Asymmetry Feature
Ethernet ports are usually full-duplex, which means upstream and downstream PTP
packets go through different physical links, such as fibers. The length difference
between the physical fiber lines of the upstream and downstream paths causes a
delay asymmetry. For example, the transport delay of optical fiber is 5us per 1km,
so a length difference of 100 meters between the upstream and downstream path
will introduce a 250ns error. However, PTP(1588v2) can't eliminate delay
asymmetry of physical fiber line. When GNSS is available it can be used as a
calibrated reference to determine asymmetry that may be present on an active PTP
input which has full event flow occurring.
If a PTP input becomes selected as the phase reference upon loss of the GNSS
reference, the Asymmetry feature of the TP 2300/2700 can provide automatic
phase compensation for path asymmetry of the physical line between the 1588v2
client and master. If a calibrated path is available, a positive or negative
compensating value is added to the path delay value from the client to the master,
making the delay symmetric and equal to the path from the master to the client. If no
calibrated path is available, only the usual PTP-based frequency adjustments will be
applied, which introduces error on phase/time outputs of half the amount of
asymmetry that is present. See Appendix F, Asymmetry Feature for more details.

The TP 2300/2700 maintains asymmetry tables associated with the PTP masters
that provide the active flow to its PTP client input port. The clockID of the master is
used as an identifier to match to the correct asymmetry table. The tables can
contain multiple asymmetry signatures for calibrated paths that have been seen for
a particular grandmaster, such as would be likely if the path from the grandmaster to
the client port of the TP 2300/2700 is part of a ring topology.
The following are requirements for using the Asymmetry feature:
 Asymmetry feature must be enabled with the CLI command "set ptp client
config eth1 asymmetry state enable". The Default asymmetry state is
disable.
 GPS must be enabled and qualified. It is not required that GPS be selected for
the feature to be actively updating the asymmetry tables. The GPS phase
solution is used as the calibration value, PTP paths are judged vs. this calibration
and offset corrections (if any) are mapped into the appropriate asymmetry table.
 If GNSS/GPS is lost and PTP becomes the source for time/phase output
(PPS/PTP Master), asymmetry compensation will be applied as long as there is a
single entry in the asymmetry table. In this situation the table entry can be used
as a link back to the original GPS-based calibration. If a new asymmetry
appears, its relationship back to this calibration can still be established and a new
table entry created.
 The system requires a practical minimum of 1 hour of available GNSS/GPS and
a given Asymmetry to be present on the active PTP input for the path to be
calibrated and asymmetry table entries to occur.
 The asymmetry table entries do not age but table information is lost on
power-cycle.
 Asymmetry tables can be cleared with the command "set ptp client
config eth1 asymmetry clear".

Figure 4-8. Set PTP Client Command Hierarchy (partial)

Figure 4-9. Set PTP Client Config Command Hierarchy (partial)

Figure 4-10. Set PTP Client Config Command Hierarchy (cont’d)
Note: A license is required to enable PTP input client functionality on

the TP 2700.
Example 1 - Telecom-2008 Profile

Use the following procedure to configure the ETH1 port as a PTP client input with
the Telecom-2008 profile, no VLAN:
1. Type set ptp client active-profile eth1 telecom-2008 and press

Enter.
2. Type set ptp client config eth1 telecom-2008 ptp-state enable and
press Enter.
3. Type set ptp client config eth1 telecom-2008 ttl 10 and press Enter.
4. Type set ptp client config eth1 telecom-2008 dscp 8 and press Enter.
5. Type set ptp client config eth1 telecom-2008 unicast-negotiation

enable and press Enter.

6. Type set ptp client config eth1 telecom-2008 lease-duration 300 and
press Enter.
7. Type set ptp client config eth1 telecom-2008 announce-interval 1

and press Enter.
8. Type set ptp client config eth1 telecom-2008 sync-interval -6 and

press Enter.
9. Type set ptp client config eth1 telecom-2008 delay-req-interval -6

and press Enter.
10.Type set ptp client config eth1 telecom-2008 domain 5 and press
Enter.
11.Type set ptp client config eth1 telecom-2008 phase-offset 0 and

press Enter.
12.Type set ptp client config eth1 telecom-2008 master-table add

index 1 address 192.168.5.100 and press Enter.
13.Type set ptp client config eth1 transport ethernet and press Enter.
14.Type set ptp client config eth1 service-tier sync_mask and press
Enter.
Setting GNSS Parameters

When the GNSS reference is enabled, you can set the satellite position parameters
either automatically or manually. The GNSS reference input is enabled by default.
In manual mode, you must specify the latitude, longitude, and height. Manual mode
should not be used unless antenna location has been accurately surveyed. See the
set gnss command description for details about setting GNSS position parameters
manually.
You can specify the elevation mask which filters the satellites used by the system.
You can also specify the cable delay.
Note: It is important the cable delay be configured with the proper

value. This can be determined from the cable length.

Figure 4-11. Set GNSS Command Hierarchy
To provision the TimeProvider 2300/2700 for GNSS, use the set ref time gnss
command to set the priority and config-pql values for GNSS. Use the set gnss
command to provision the GNSS port state and GNSS parameters.
GNSS Mode
The Priority setting for GNSS is for the GNSS port itself. However, the GNSS port
can receive GPS and GLONASS satellite RF inputs. The GNSS tracking mode
parameter is used to specify the tracking priority for the GNSS port.
 GPS: Only checks for qualified GPS on this port

 GLONASS: Only checks for qualified GLONASS on this port
 GLONASS-GPS:Checks for qualified GLONASS and GPS concurrently.
A license is required for the GLONASS-GPS mode.
Example
To provision the TimeProvider 2300/2700 for a GNSS reference in auto mode, with
a track-mode of GPS with a cable delay of 315 ns, perform the following steps:

2. Type set gnss posmode auto and press Enter.
3. Type set gnss track-mode gps and press Enter.
4. Type set gnss cable-delay 315 and press Enter.
5. Type set gnss state enable and press Enter.
6. Type show gnss status and press Enter to verify that GNSS is enabled.

Setting E1/T1 Input Reference Parameters

The T1/E1 port can be configured as an E1 or T1 input frequency reference. The
set ref command is used to provision the T1/E1 port as a reference, as shown in
Figure 4-7. The set port-control command is used to provision the T1/E1 port
as an input and to select the signal type as T1 or E1, as shown in Figure 4-12.The
set input command is used to configure the frametype and associated
parameters for the T1/E1 port. See Figure 4-13 for the set input command
hierarchy.
The priority value or user-configured PQL value for the T1/E1 port is provisioned
with the set ref command. See Reference Selection Criteria, on page 223 for
additional information.
Figure 4-12. Set Port-Control Command Hierarchy

Figure 4-13. Set Input Command Hierarchy
Frame Type
The T1 and E1 inputs each have two common framing standards available, as well
as the unframed frequency signal.
SSM Bit
The SSM bit indicates which bit of the framing signal carries the SSM.
CRC State
CRC is a cyclic redundancy checking protocol which is applicable for E1 signals.
CRC must be enabled for the T1/E1 port in order to use the input SSM information
for PQL conversion with the CAS or CCS framing types for that port.
Provisioning T1 Input
Use the following procedures to provision the T1/E1 port as a T1 input:
Example:
To provision TI/E1 port as a T1 input port with frametype freq1544khz and to enable
the port:
2. Type set port-control t1e1 io input and press Enter.
3. Type set port-control t1e1 signal-type t1 and press Enter.

4. Type set input t1 frametype t1e1 freq1544khz and press Enter.
5. Type set port-control t1e1 state enable and press Enter.
Provisioning E1 Input
Use the following procedure to provision the T1/E1 port as a E1 input:
Example:
To provision TI/E1 port for an E1 output with a frametype of CCS, CRC enabled,
SSM bit of 7, and to enable the port:
2. Type set port-control t1e1 io input and press Enter.
3. Type set port-control t1e1 signal-type e1 and press Enter.
4. Type set input e1 frametype t1e1 ccs and press Enter.
5. Type set input e1 crc t1e1 enable and press Enter.
6. Type set input e1 ssmbit t1e1 7 and press Enter.
Note: Disabling the input port will clear all alarms and events related
to this port.

Provisioning SyncE Input

Synchronous Ethernet (SyncE) provides a method of distributing timing using the
physical layer of Ethernet devices. All intermediate nodes must have hardware and
software support for syncE. SyncE is used to distribute frequency through the
network. Synchronization Status Messaging (SSM) is passed between nodes in
ESMC messages. This allows nodes to determine the quality level of the upstream
node, to prevent timing loops, and also to reconfigure the timing path. The TP
2300/2700 receives the SSM information from a SyncE input and converts it to a
PQL value that can be used for reference selection. See Reference Selection
Criteria, on page 223 for details.
Other than the ESMC state (see Figure 4-14), the only parameters that can be
configured for a SyncE input reference on the ETH1 port are the port state, port
priority value, and the user-configurable PQL value. These parameters are all
configured with the set ref command, as shown in Figure 4-7.
Figure 4-14. Set SyncE Command Hierarchy
Example:
To enable the ETH1 port for SyncE, use the RJ45 connector, R1, for the connection,
and enable to ESMC on the ETH1 port:
2. Type set ethernet active-connector eth1 r1-rj45 and press Enter.
3. Type set synce state eth1 enable and press Enter.
4. Type set synce ql-state eth1 enable and press Enter.

Provisioning the PTP Output
The TP 2300/2700 ETH2 PTP output port can be configured for different profiles,
along with parameters for each profile.
PTP Profiles
Table 4-3 shows the profiles with which the TP 2300/2700 can be configured. The
ETH2 PTP output port can run only one of these profiles at one time. See Figure
4-15 for the hierarchy of active profile set ptp commands.
Table 4-3. PTP Profiles for the TP 2300/2700
PTP Profile Transport Mode Description
Default Layer 3 Multicast Default profile in IEEE1588-2008 Annex J,

multicast over UDP/IP. See Table 3-7.
Ethernet Default Layer 2 Multicast Default profile in IEEE1588-2008 Annex F,
multicast over Ethernet. See Table 3-7.
Telecom-2008 Unicast Generic unicast profile for telecom before ITU-T
G.8265-1. See Table 3-9.
Proprietary implementation, but commonly used.
ITU G.8265-1 Unicast Telecom profile for frequency sync. See Table 3-9.
See ITU-T G.8265.1 for details.
Figure 4-15. Set PTP Master Command Hierarchy  Active Profile

PTP Server Parameters

By default, the ETH2 port of the TP 2300/2700 is provisioned as a PTP master
enabled for PTP Telecom-2008 unicast negotiation. The set ptp master
command is used to provision PTP parameters for the Default (Layer 3 multicast),
Ethernet Default (Layer 2 multicast), Telecom-2008 (unicast), and ITU-G.8265.1
(unicast) profiles. Figure 4-16 shows the command hierarchy for parameters shared
by all profiles.
Figure 4-16. Set PTP Master Command Hierarchy  Shared Parameters

The TP2300/2700 supports both one-step and two-step clock operation. On the
PTP master port, the user has the option to enable or disable two-step clock
operation on that port. See Figure 4-17 for a diagram of packet flow for the two-step
clock setting. See Figure 4-18 for a diagram packet flow for the one-step clock
setting.
Figure 4-17. Two-Step Clock

Figure 4-18. One-Step Clock
Default and Ethernet-Default Profiles

The TP 2300/2700 grandmaster with the Default (Layer 3 multicast) or Ethernet
Default(Layer 2 multicast) profile operates per the multicast communication model,
which specifies that each PTP message sent from the grandmaster is capable of
being received and processed by all PTP ports on the same PTP communication
path. See Figure 4-16 for the hierarchy of the set ptp commands that are shared
by all profiles. See Table B-39 for defaults and ranges. See Figure 4-19 for the
hierarchy of multicast profile set ptp commands. See Table 3-7 for descriptions of
the parameters for the Default and Ethernet Default profiles, and Table B-41 for
defaults settings and ranges.
In multicast mode, there are no client leases or client limits. All delay requests will
be responded to. There is no limit applied to the number of delay responses
supported, other than the maximum capacity of the Ethernet link and the TP
2300/2700.

In multicast mode, the TP 2300/2700 creates a client list by examining the received
PTP delay request messages. For a client to be reliably added to the client list and
not removed, the TP 2300/2700 needs to receive several hundred delay request
messages during the client timeout period. If delay requests are sent at a slow rate,
then the client-timeout value must be increased. Since one-way PTP operation
does not use delay request and delay response messages, the client list will not be
populated in this mode.
Note: The TP 2300/2700 uses the clock ID as a unique identifier for

PTP clients and can only allow for one instance of the clock id to be
serviced. If a PTP client with a single clock ID requests service using
two different IP addresses or VLANs, the TP 2300/2700 will use the
IP address/VLAN of the latest request.
Figure 4-19. Set PTP Master Command Hierarchy - Default Profile

Figure 4-20. Set PTP Master Command Hierarchy - Ethernet Default Profile
ITU-G.8265-1 and Telecom-2008 Profiles

The TP 2300/2700 grandmaster with the Telecom-2008 or ITU-G8265-1 (unicast)
profile operates per the unicast communication model, which specifies that each
PTP message sent from the grandmaster is capable of being received and
processed by a single PTP port on the PTP communication path. See Figure 4-21
for the hierarchy of set ptp commands unique to the unicast profiles. See Table
3-9 for descriptions of the parameters for the Telecom-2008 and ITU-G8265-1
(unicast) profiles. and Table B-40 for default values and ranges.

Figure 4-21. Set PTP Master Command Hierarchy - Unicast Profiles
Example 1 - Telecom-2008 Profile

Use the following procedure to configure the ETH2 port as a PTP master with the
Telecom-2008 profile:
1. Type set ptp master active-profile eth2 telecom-2008 and press

Enter.
2. Type set ptp master config eth2 telecom-2008 ptp-state enable and
press Enter.
3. Type set ptp master config eth2 telecom-2008 ttl 100 and press Enter.
4. Type set ptp master config eth2 telecom-2008 dscp 5 and press Enter.
5. Type set ptp master config eth2 telecom-2008 two-step disable and
press Enter.

6. Type set ptp master config eth2 telecom-2008 timescale auto and
press Enter.
7. Type set ptp master config eth2 telecom-2008 priority-1 128 and
press Enter.
8. Type set ptp master config eth2 telecom-2008 priority-2 128 and
press Enter.
9. Type set ptp master config eth2 telecom-2008 domain 8 and press
Enter.
10.Type set ptp master config eth2 telecom-2008 unicast-negotiation

Enable and press Enter.
11.Type set ptp master config eth2 telecom-2008 lease-limit 300 and
press Enter.
12.Type set ptp master config eth2 telecom-2008 announce-limit -4 and

press Enter.
13.Type set ptp master config eth2 telecom-2008 sync-limit -7 and

press Enter.
14.Type set ptp master config eth2 telecom-2008 delay-limit -7 and

press Enter.
Example 2 - Default (Layer 3 Multicast) Profile

Use the following procedure to configure the ETH2 port as a PTP master with the
Default (multicast) profile:
1. Type set ptp master active-profile eth2 default and press Enter.
2. Type set ptp master config eth2 default ptp-state enable and press
Enter.
3. Type set ptp master config eth2 default ttl 20 and press Enter.
4. Type set ptp master config eth2 default dscp 25 and press Enter.
5. Type set ptp master config eth2 default dither enable and press
Enter.
6. Type set ptp master config eth2 default two-step enable and press
Enter.
7. Type set ptp master config eth2 default priority-1 200 and press
Enter.

Provisioning the Non-PTP Outputs
8. Type set ptp master config eth2 default priority-2 200 and press
Enter.
9. Type set ptp master config eth2 default domain 10 and press Enter.
10.Type set ptp master config eth2 default timescale auto and press
Enter.
11.Type set ptp master config eth2 default vlanid 0 and press Enter.
12.Type set ptp master config eth2 default announce-interval 2 and

press Enter.
13.Type set ptp master config eth2 default sync-interval -6 and press
Enter.
14.Type set ptp master config eth2 default delay-interval -2 and press
Enter.
15.Type set ptp master config eth2 default announce-receipt-timeout 4

and press Enter.
16.Type set ptp master config eth2 default client-timeout 500 and
press Enter.
Quality Levels for Output Signals

Output signal quality level is determined by the quality level of the internal clock.
When the internal clock is tracking a reference, the quality level (PQL value) of the
internal clock is the PQL of the selected reference. At the outputs, the frequency
PQL is converted to the appropriate quality levels for different output signal types.
When the internal clock is not tracking a reference, the quality level of the internal
clock is determined by its clock state and its oscillator quality. See Appendix D: PQL
Mapping, on page 361 for details.

Provisioning the T1/E1 Output

The set output command is used to provision the output characteristics for the
T1/E1 port. See Figure 4-22. The set port-control command is used to
provision the T1/E1 port as an output and to provision the signal type as T1 or E1,
as shown in Figure 4-12.
Figure 4-22. Set Output Command Hierarchy
The SSM function is supported for the frame types CCS, CAS, and ESF. However,
the SSM-bit parameter only applies to the E1 frame types, CCS and CAS. If the
output frame type supports SSM and SSM is enabled for the output port, then the
output signal will contain the system SSM value.
Provisioning T1 Output
Use the following procedure to provision the T1/E1 port as a T1 output:
Example:

To provision TI/E1 port as a T1 output port with a frametype of D4 and to enable the
port:
2. Type set port-control t1e1 io output and press Enter.
3. Type set port-control t1e1 signal-type t1 and press Enter.
4. Type set output t1 frametype t1e1 d4 and press Enter.
Provisioning E1 Output
Use the following procedures to provision the T1/E1 port as a E1 output:
Example:
To provision TI/E1 port for an E1 output with a frametype of CAS, CRC enabled,
SSM-bit of 5, zero-suppression on, and to enable the port:
2. Type set port-control t1e1 io output and press Enter.
3. Type set port-control t1e1 signal-type e1 and press Enter.
4. Type set output e1 frametype t1e1 cas and press Enter.
5. Type set output e1 crc t1e1 enable and press Enter.
6. Type set output e1 ssmbit t1e1 5 and press Enter.
7. Type set output e1 zero-suppression t1e1 on and press Enter.
Provisioning TOD+1PPS Output

The TOD output port uses an RS-422 balanced signal level and RJ-45 connector. It
contains the TOD message and the 1PPS signal. The TOD message can be one of
two supported TOD formats: Cisco and China Mobile. At the connector, the 1PPS
signal shares the same timing characteristics as the standalone 1PPS signal from
the 10M/1PPS coaxial connector. These timing characteristics are pulse width, rise
time of the timing edge, and offset from UTC second, but they are separately
configured.

TOD+1PPS Output Example

To configure the TOD port as a TOD+1PPS output with the Cisco TOD format, and
to enable the port, use the following procedure:
2. Type set port-control tod format cisco and press Enter.
3. Type set port-control tod state enable and press Enter.
Provisioning the 10MHz & 1PPS Output

Use the following procedures to provision the 10M/1PPS port as a 1PPS output or
10 MHz output.
1PPS Output Example

To configure the 1PPS/10M port as a 1PPS output, with an offset of +50,000 ns, and
to enable the port, use the following procedure:
2. Type set port-control pps10m signal-type pps and press Enter.
3. Type set output pps offset pps10m 50000 and press Enter.
4. Type set port-control pps10m state enable and press Enter.
10 MHz Port Example

To configure the 1PPS/10M port as a 10MHz output and to enable the port, use the
following procedure:
2. Type set port-control pps10m signal-type 10m and press Enter.
3. Type set port-control pps10m state enable and press Enter.

Provisioning SyncE Output

SyncE provides a method of distributing timing using the physical layer of Ethernet
devices. All intermediate nodes must have hardware and software support for
SyncE. SyncE is used to distribute frequency through the network. SSM is passed
between nodes in ESMC messages. This allows nodes to determine the quality
level of the upstream node, to prevent timing loops, and also to reconfigure the
timing path. The TP 2300/2700 provides the master function of providing
synchronization via SyncE.
Ethernet can be run in either asynchronous or synchronous modes. Electrical SFP

do not support the transmission of timing and therefore are asynchronous. Optical
SFP support synchronous operation and therefore can be used with SyncE.
Normally, SyncE nodes use the ESMC messages. However, if the downstream
devices do not use the ESMC messages, then the messages can be disabled.
The system PQL value is normally sent in the QL -value (SSM) field in the ESMC
message. If desired, this can be disabled and a value of DNU will be inserted in the
ESMC message.
Figure 4-23 shows the command hierarchy for provisioning SyncE.
The TP 2300/2700 only support the unidirectional output QL mode. With

unidirectional, the SyncE output port supports a reduced SyncE, i.e. it transmits
ESMC messages and ignores ESMC messages from the downstream SyncE
Network Element.
Figure 4-23. Set SyncE Command Hierarchy
QL State for SyncE Output Example

2. Type set synce ql-state eth2 enable and press Enter

Enable ESMC Message for SyncE Output Example

2. Type set synce state eth2 enable and press Enter.
Provisioning Output Generation Behavior

The behavior of the output ports during warm-up, free-run, and holdover states can
be provisioned using the set output-gen warm-up, set output-gen free-run,
and set output-gen holdover commands, as shown in Figure 4-24.
Figure 4-24. Output Generation Behavior Commands
Example:
To provision the port 1 output behavior as squelch for the warm-up state, squelch for
the free-run state, ON for the holdover state, and AIS for the fast-track state:
2. Type set output-gen warm-up t1e1 squelch and press Enter.
3. Type set output-gen free-run t1e1 squelch and press Enter.
4. Type set output-gen holdover t1e1 on and press Enter.
5. Type set output-gen fast-track t1e1 ais and press Enter.

Setting the System Date and Time
Setting the System Date and Time
The TimeProvider 2300/2700 Time of Day can be set either by an external source,
or manually with the “set clock” command. You can set the time and date only for
the frequency references.
Example
2. Type show ref status and press Enter to check the reference mode.
3. Type set ref frequency state t1e1 enable and press Enter.
4. Type set clock date-time <value> and press Enter. Enter the value in
format yyyy-mm-dd,hh:mm:ss.
Provisioning Alarms
This section describes the commands used to provision and manage alarms in the
TimeProvider 2300/2700. The user can provision the alarms to be enabled or
disabled and set thresholds to turn the alarms on and off. For a list of all alarms, see
Appendix A, System Messages.
Software commands allow you to perform the following:
 Provision the severity level

 Provision the alarm (enable or disable)
 Show current alarm settings
 Show current alarms
 Display alarm status
Alarms are also indicated by an LED on the front panel.
Note: Disabling an input port will clear all alarms and events related
to the port.

Provisioning Alarms
Figure 4-25. Set Alarm-Config Commands
Disabling Specific Alarms

The Set Alarm-Config command allows you to enable or disable specified alarms.
Example
To disable the GNSS antenna open-circuit alarm (alarm #33), enter the following:
2. Type set alarm-config state alarm 33 disable and press Enter.
Showing Current Alarm Settings

The Show Alarm-Config command displays the set and clear alarm thresholds for
every alarm type.
Example

Provisioning Alarms
To display the configuration for all alarm types, enter the following:
1. Type show alarm-config and press Enter.
Showing Current Alarms

The Show Alarm command displays all current alarms.
Example
To display a list of all current alarms enter the following:
1. Type show alarm and press Enter.
Displaying Alarm and Unit Status

The Show Status command displays the system status information as follows:
 Assigned System Name

 System Date And Time
 System Uptime
 Time Traceable
 Clock Frequency Status
 Clock Timing Status
 Frequency State Duration in Minutes
 Time State Duration in Minutes
 Currently Selected Timing reference Input
 Currently Selected Frequency reference Input
 Packet Service Eth1 mode: PTP client
 Packet Service Eth2 mode: PTP Master
 Eth1 active connector interface: RJ45
 Eth2 active connector interface: SFP
 Frequency Offset
 Phase Offset Value (Valid in fast-lock and normal states)
 Active Alarms #
 System Frequency PQL
Example
To display the system status, type show status and press Enter.

Saving and Restoring Provisioning Data
Saving and Restoring Provisioning Data
Microsemi recommends that you keep an electronic version and/or a written version
of the provisioning changes you make to the TimeProvider 2300/2700. Use the set
configuration command to back up or restore provisioning data. See Figure 4-26.
Figure 4-26. Set Configuration Command Hierarchy
Backing up Provisioning Data

The configuration is automatically backed up one minute after a configuration
change.
Example 1
To backup up the current configuration immediately, type set configuration

backup local and press Enter.

Provisioning for SNMP
Restoring Provisioning Data

Example 1
To change the current configuration to factory default while preserving user and IP
information, type set configuration default and press Enter.
Note: The system will automatically reboot after receiving either

the "set configuration default" or "set configuration
factory" commands
Example 2
To change the current configuration to the factory default, type set configuration
factory and press Enter.
Notes: Setting the configuration to default will not overwrite the

user login information or the IP address of MGMT port. Setting the
configuration to factory will overwrite the user login information and
return the IP address of MGMT port to the factory set address.
The Simple Network Management Protocol (SNMP) is an application layer protocol

that allows you to manage network devices. SNMP is based on a client-server
query-response mode that requires an Ethernet connection. A manager application
(software installed on a computer) is the client generating the queries, and an agent
(software on the TimeProvider 2300/2700) is the server generating responses. The
TimeProvider 2300/2700 SNMP supports traps and the MIB-II system MIB.
TimeProvider 2300/2700 supports SNMPv2c and SNMPv3. SNMPv3 provides

additional security features not available in SNMPv2c. In addition to the functions of
SNMPv2c, SNMPv3 allows user and trapuser levels that are based on
authentication and privacy settings. The authentication algorithm is either
HMAC-SHA-1-96 or MD5, with a 20-character key. The privacy settings are based
on either the CBC-DES or AES encryption standard, with a 16-character key. All
keys are uppercase.
Port 161 is the port of standard SNMP interactive communications and port 162 is
the trap port.
SNMP functionality is provisioned on the TP 2300/2700 using the CLI command

“set snmp” (see Figure 4-27).
Each alarm trap OID from the TP 2300/2700 represents a unique alarm.

Each container contains the following sub-info in its own OID:
 Alarm/Event ID
 Date&Time
 Severity
 Alarm/Event Description
 Index
 Alarm Action
 Sequence Number
The alarm OIDs are under 1.3.6.1.4.1.9070.1.2.5.7.3.1.2.
The Alarm/Event ID element should be used to determine which alarm or event was
generated. Alarm and Event IDs are listed in Appendix A, System Messages.
Figure 4-27. Set SNMP Commands
Adding or Deleting a Manager IP Address

Use the “set snmp add manager” command to add a manager IP address. Use the
“set snmp delete manager” command to delete a manager IP address. The TP
2300/2700 will support a maximum of 3 manager IP addresses.
Example:

To add the SNMP manager IP address 192.100.100.100, using an engineID

0x12345678901234567890:
1. Type set snmp add manager 192.100.100.100 engineid

0x12345678901234567890 then press Enter.
Provisioning to Generate v2 Traps

Use the set snmp trapversion command to provision the trap version to v2.
By default, the TP 2300/2700 will generate v2 traps.
Example:
Type set snmp trapversion 2 then press Enter.
Provisioning to Generate v3 Traps

Use the set snmp trapversion command to provision the trap version to v3.
Example
Type set snmp trapversion 3 then press Enter.
Adding and Removing v2 Communities

Use the set snmp add v2-community command to add a SNMP v2 community.
Use the set snmp delete v2-community command to remove an existing SNMP
v2 community. The TP 2300/2700 will support a maximum of ten v2 communities.
Note: To use v2 communities, the v2 state must be set to Enable

using the command set snmp state-v2 enable.
Example
To add a v2 community named “tech27”, with a security level of “read-only” and

remove an existing v2 community named “bob321”:
1. Type set snmp add v2-community tech27 securelvl read-only then press
Enter.
2. Type set snmp delete v2-community bob321 then press Enter.

Adding and Removing SNMP v3 Users

SNMPv3 provides additional security features not available in SNMPv2c. In addition
to the functions of SNMPv2c, SNMPv3 allows user and trapuser levels that are
based on authentication and privacy settings. The authentication algorithm is either
HMAC-SHA-1-96 or MD5, with a key of up to 32 characters in length. The privacy
settings are based on either the CBC-DES or AES encryption standard, with a key
of up to 32 characters in length. All keys are uppercase.
Use the set snmp add user command to add a v3 user. Use the set snmp
delete user command to remove an existing v3 user. The TP 2300/2700 will
support a maximum of ten v3 users.
Example - Add User
To add a user named “test12”, with a security level of “priv”, with a 20-character
MD5 authentication key “123456789ABCDEFGHIJK” and a 16-character DES
privacy key “ABCDEFG123456789”:
1. Type set snmp add user test12 securelvl priv then press Enter.
2. Enter MD5 at the authentication protocol prompt.
3. Enter 123456789ABCDEFGHIJK at the authentication key prompt.
4. Enter DES at the privacy protocol prompt.
5. Enter ABCDEFG123456789 at the privacy key prompt.
Note: Do not use spaces within keys.

Only characters {a-z,A-Z,0-9,! ( ) - _ . ? ~ * @ ^ + = : / %} are
accepted for SNMP authentication or privacy keys.
Example - Remove User
To remove an existing user named “dave123”, type set snmp delete user
dave123 then press Enter.

Testing TP 2300/2700 Provisioning
Adding and Removing SNMP v3 Trap Users

Use the set snmp add trapuser command to add a v3 trap user. Use the set
snmp delete trapuser command to remove an existing v3 trap user. The TP
2300/2700 will support a maximum of 3 v3 trap users.
Note: In order to access trap information, a trap user must also

be added as a user. The same name, authentication protocol,
authentication key, privacy protocol, and privacy key must be
used for both the user and trap user.
Example - Add Trap User
To add a trap user named “test12” with a security level of “priv”, with the
20-character MD5 authentication key “123456789ABCDEFGHIJK” and
16-character DES privacy key “ABCDEFG123456789”:
1. Type set snmp add trapuser test12 securelvl priv then press Enter.
2. Enter MD5 at the authentication protocol prompt.
3. Enter 123456789ABCDEFGHIJK at the authentication key prompt.
4. Enter DES at the privacy protocol prompt.
5. Enter ABCDEFG123456789 at the privacy key prompt.
Example - Remove Trap User
To remove an existing trapuser named “dave123”, type set snmp delete

trapuser dave123 then press Enter.
Perform the tests in this section to verify that the TP 2300/2700 is provisioned and
operating correctly.
LED Indications
The LEDS on the front panel of the TP 2300/2700 illuminate in the following way
when the TP 2300/2700 is installed and provisioned:
 The Power LED should be green.

 The PWR A and/or PWR B LEDs should be green.
(DC power versions of TP 2300/2700 only)

 The GNSS LED will be green if the reference is GNSS and the GNSS
engine/interface is operating normally. (TP 2700 only)
– The GNSS LED will be amber if the reference is GNSS and GNSS engine
or antenna is not tracking satellite.
– The GNSS LED will be OFF if the reference is not GNSS.
 The Clock LED should be GREEN.
 The Alarm LED should be OFF.
 The Ethernet MGMT port, LEDs on connector.
– LED on right side of connector should be green if link has been
established. (Left side is amber if there is a 100M link.)
– LED on left side of connector should flash amber if there is activity.
 ETH1 port LED will be green if a link has been established, flashing green if there
is activity. (Left side is amber if there is a 100M link.)
 ETH2 port LED will be green if a link has been established, flashing green if there
is activity. (Left side is amber if there is a 100M link.)
See Table 5-3 for additional details about LED conditions.
Verifying the Port IP Addresses

The IP addresses for the MGMT, ETH1 and ETH2 ports must each be on different
network/subnet.
MGMT Port
1. Log in to the TP 2300/2700 with a valid username and password.
2. Type show ip config mgmt and press Enter.
a. Verify that the IP address-mode has the desired setting of DHCP or Static.
b. If the IP address-mode is set to “static”, verify that the IP address and mask
are the desired values.
c. Verify the State for the port is “enable”.
tp2700> show ip config mgmt
MGMT PORT PARAMETERS

IP mode : dhcp
IP state : enable


IP address : 192.168.0.100
IP mask : 255.255.255.0
DNS Domain : 192.168.0.100
4. Type show ip status mgmt and press Enter.
a. Verify that the IP address and mask match the configured values.
b. Verify that the third line of the results shows that the link is “UP”.
mgmt0 Link encap:Ethernet HWaddr 00:B0:AE:03:46:04

RX bytes:83053919 (79.2 MiB) TX bytes:592651 (578.7 KiB)
ETH1 Input Port

1. Type show ethernet config and press Enter.
a. Verify that the auto-negotiation and speed settings match the desired values.
b. Verify that the active-connector setting matches the connector being used.
----------------------------------------------
|----|------------|--------|-----------------|
|----|------------|--------|-----------------|
----------------------------------------------
3. Type show ethernet status and press Enter.
a. Verify that the speed for the port matches the settings.
eth1 current speed: 100M

2. Type show ip config eth1 and press Enter.
a. Verify that the IP address and mask are the desired values.
b. Verify the State for the port is “enable”.


IP state : enable

IP address : 192.168.1.12
IP mask : 255.255.255.0
3. Type show ip status eth1 and press Enter.
eth1 Link encap:Ethernet HWaddr 00:B0:AE:03:46:05

RX bytes:3079100330 (2.8 GiB) TX bytes:1457475560 (1.3 GiB)
Interrupt:128
ETH2 Output Port

1. Type show ethernet config and press Enter.
a. Verify that the auto-negotiation and speed settings match the desired values.
b. Verify that the active-connector setting matches the connector being used.
----------------------------------------------
|----|------------|--------|-----------------|
|----|------------|--------|-----------------|
----------------------------------------------
3. Type show ethernet status and press Enter.
a. Verify that the speed for the port matches the settings.
eth1 current speed: none

2. Type show ip config eth2 and press Enter.
a. Verify that the IP address and mask are the desired values.
b. Verify the State for the port is “enable”.


IP state : enable

IP address : 192.168.2.12
IP mask : 255.255.255.0
3. Type show ip status eth2 and press Enter.
eth2 Link encap:Ethernet HWaddr 00:B0:AE:03:46:06

RX bytes:0 (0.0 b) TX bytes:16764776 (15.9 MiB)
Interrupt:128
Verifying the Reference

1. Type show ref config and press Enter.
– Verify that Reference Critera and Switch Mode settings match desired
values.
– Verify that Priority and Config-PQL and Use-Config-PQL settings match
desired values for Time Reference and Frequency Reference.
Reference Criteria : priority
Reference Switch Mode : AutoReturn
Time Reference Config
--------------------------------------------------
|----------|---------|-----------|---------------|
|..........|.........|...........|...............|
|PTP |2 |3 |disable |
--------------------------------------------------
Frequency Reference Config

--------------------------------------------------
|----------|---------|-----------|---------------|
|..........|.........|...........|...............|
|PTP |2 |3 |disable |
|..........|.........|...........|...............|
|SYNCE |4 |3 |enable |
|..........|.........|...........|...............|
|T1E1 |3 |3 |disable |
--------------------------------------------------
2. Type show ref status and press Enter.
– Verify that GNSS is qualified for Time Reference and Frequency

Reference. If GNSS is configured to be the main reference, verify that
GNSS is “selected”.
Time Reference Status
------------------------------------
|----------|---------|-------------|
|GNSS |1 |selected |
|..........|.........|.............|
|PTP |16 |disqualified |
------------------------------------
Frequency Reference Status
------------------------------------
|----------|---------|-------------|
|GNSS |1 |selected |
|..........|.........|.............|
|PTP |16 |disqualified |
|..........|.........|.............|
|SYNCE |3 |disqualified |
|..........|.........|.............|
|T1E1 |16 |disable |
------------------------------------
Verifying GNSS (TP 2700 only)

1. Type show gnss config and press Enter.
– Verify that the State is “enable”.

– Verify that the settings for PosMode, Track-mode, Mask, and Antenna
Delay match the desired values.

tp2700> show gnss config
GNSS Configuration
State : enable
PosMode : auto
Track-Mode : gps
Mask : 10
Antenna Delay : 0
GNSS manual position
Latitude : N37:22:43.425
Longitude : W121:55:34.815
Height : 13.7
2. Type show gnss status and press Enter.
– Verify that Current Status for GNSS is “OK”.

– Verify that at least several satellites with SNR values greater than 40 are in
the table.
tp2700> show gnss status
GNSS Status:
Current Status : ok
Current Position Status : positionHold
Current Antenna Position:
Latitude : N37:22:43.11
Longitude : W121:55:34.65
Height : 11.10
Current GNSS Satellite View:
--------------------------------------------------------------------
|Index |No |SNR |Status |Azimuth |Elevation |Sat Type |
|------|-----|-----|----------|----------|------------|------------|
|1 |2 |50 |ok |49 |72 |gps ||
|......|.....|.....|..........|..........|............|............|
|2 |4 |44 |ok |47 |22 |gps |
|......|.....|.....|..........|..........|............|............|
|3 |5 |48 |ok |146 |29 |gps |
|......|.....|.....|..........|..........|............|............|
|4 |10 |48 |ok |76 |31 |gps |
|......|.....|.....|..........|..........|............|............|
|5 |12 |52 |ok |333 |88 |gps |
|......|.....|.....|..........|..........|............|............|
|6 |24 |44 |ok |202 |19 |gps |

|......|.....|.....|..........|..........|............|............|
|7 |25 |49 |ok |314 |47 |gps |
|......|.....|.....|..........|..........|............|............|
|8 |29 |48 |ok |284 |27 |gps |
|......|.....|.....|..........|..........|............|............|
|9 |35 |30 |ok |211 |41 |gps |
|......|.....|.....|..........|..........|............|............|
|10 |47 |31 |ok |250 |14 |gps |
--------------------------------------------------------------------
3. Use the procedure Verifying the Reference, on page 263 to check the reference
configuration and status.
Verifying PTP Master/Server Functionality

1. Verify the IP address for ETH2 Output Port per the above procedure.
2. Type show ptp master active-profile eth2 and press Enter.
– Verify that the active profile setting matches the desired profile type.
ETH2 PTP MASTER ACTIVE PROFILE : telecom-2008
3. Display the configuration details for the active profile type, whether “default”,
“itu-g8265-1” or “telecom-2008”. Each profile will have configuration settings,
even if is not the active profile. For this example, type show ptp master config
eth2 telecom-2008 and press Enter.
– Verify that the PTP State is “enable”.

– Verify that the PTP parameter settings for the profile match the desired
settings.
ETH2 PTP MASTER CONFIGURATION WITH PROFILE TELECOM-2008:
PTP State : enable

PTP TTL : 64
PTP DSCP : 0
PTP Sync Limit : -7
PTP Domain : 0

4. Type show ptp master status eth2 and press Enter.
– Verify that the port is enabled.

– Verify that the profile matches the desired setting.
– If clients are configured to use this master, verify that number of attached
clients matches the number of clients configured.
ETH2 PTP MASTER STATUS :
Port enabled : yes

Clock Id : 00:b0:ae:ff:fe:03:46:05
Port Number : 2
Profile : telecom-2008
Port state : master
Clock class : 6
Clock accuracy : within 100 ns
Timescale : ptp
Maximum allowed clients : 64
Number of attached clients : 8
Client load : 12%
Verifying PTP Input Client Functionality

1. Type show ptp client config eth1 telecom-2008 and press Enter.
– Verify that the PTP State is “enable”.

– Verify that the PTP settings match the desired values.
– Verify that the IP address for the master is set to the correct value.
ETH1 PTP CLIENT CONFIGURATION WITH PROFILE TELECOM-2008:
PTP State : enable

PTP TTL : 64
PTP DSCP : 0
PTP Domain : 0
PTP master-table:

------------------------------
|Index |address |
|-------|--------------------|
|1 |192.168.9.41 |
|.......|....................|
|2 |0.0.0.0 |
------------------------------
2. Type show ptp client status eth1 and press Enter.
– Verify that flow weights are non-zero values.

ETH1 PTP CLIENT STATUS:
Client Status : OK
Minimal Round Trip Delay(us) : 0.72
METRIC : FORWARD REVERSE
Flow Weight (%) : 47.78 52.22

Percentile Clustering (%) : 100.0 100.0
Operational Min TDEV (ns) : 3.2 3.2
Operational MAFE (ppb) : 0.00 0.00
Min Cluster Width (ns) : 15000.0 7500.0
Mode width (ns) : 30000.0 15000.0
Packet Rate (pkts/s) : 64 64
Currently Used Master:
IP Address : 192.168.9.41
Clock ID : 00:b0:ae:ff:fe:03:46:69
Port Number : 2
Clock Class : 6
Clock Accuracy : within 100 ns
Time Scale : PTP
Time Source : GPS
Time Traceable : true
Frequency Traceable : true
Steps Removed : 1

Verifying SyncE Functionality

Input
1. Type show synce config all and press Enter.
SyncE Config:
----------------------------
|------|----------|--------|
|......|..........|........|
----------------------------
2. Type show synce status all and press Enter.
– Verify that the Ethernet Mode is “synchronous”.

– Verify that the RxSSM value for ETH1 port is consistent with the quality
needed for your network.
-------------------------------------------------------
|Port |Direction |Ethernet Mode |RxSSM |TxSSM |
|--------|----------|---------------|--------|--------|
|eth1 |input |synchronous |0x02 |0x0f |
|........|..........|...............|........|........|
|eth2 |output |synchronous |0xff |0x02 |
-------------------------------------------------------
Output
1. Type show synce config all and press Enter.
SyncE Config:
----------------------------
|------|----------|--------|
|......|..........|........|
----------------------------
2. Type show synce status all and press Enter.
– Verify that the Ethernet Mode for ETH2 port is “synchronous”.

– Verify that the TxSSM values is consistent with quality needed for your
network.

-------------------------------------------------------
|Port |Direction |Ethernet Mode |RxSSM |TxSSM |
|--------|----------|---------------|--------|--------|
|eth1 |input |synchronous |0x02 |0x0f |
|........|..........|...............|........|........|
|eth2 |output |synchronous |0xff |0x02 |
-------------------------------------------------------
Verifying T1/E1 Functionality

T1/E1 Input
1. Type show input config t1e1 and press Enter.
– Verify that the Input Configuration settings match the desired values.
– Verify that the IO Direction is “input”.
– Verify that the Port State is “enable”.
– Verify that the Signal/Format is set to the desired value.
Input config
----------------------------------------------
|signal |Frame Type |CRC |ssmbit |
|----------|---------------|--------|--------|
|e1 input |ccs |enable |8 |
|..........|...............|........|........|
|t1 input |esf |na |na |
----------------------------------------------
Port config
--------------------------------------------
|Port |State |IO dir |Signal |
|--------|--------|--------|---------------|
|t1e1 |enable |output |t1 |
--------------------------------------------
2. Type show input status t1e1 and press Enter.
– Verify that IO status matches the configured setting.

– Verify that the input status is “OK”.
------------------------------------------------------------------------|
| Port | io status | input status | ssm | los | ais | oof | bpv | crc |
|------|-----------|--------------|-------|-----|-----|-----|-----|-----|
| t1e1 | e1 input | ok | ok | ok | ok | ok | ok | ok |
|.......................................................................|

or
------------------------------------------------------------------------------
|Port |input status|ssm |los |ais |oof |bpv |crc |
|---------|------------|--------|--------|--------|--------|--------|--------|
|t1 input |dis |na |na |na |na |na |na |
------------------------------------------------------------------------------
Output
1. Type show output config t1e1 and press Enter.
– Verify that the Output Configuration settings match the desired values.
– Verify that the IO Direction is “Output”.
– Verify that the Port State is “enable”.
– Verify that the Signal/Format is set to the desired value.
tp2700> show output config t1e1
Output Config
--------------------------------------------------------------
|------------|------------|--------|--------|----------------|
|............|............|........|........|................|
--------------------------------------------------------------
Port Config
--------------------------------------------------------
|Port |state |io dir |Signal /Format |
|------------|------------|------------|---------------|
|t1e1 |enable |input |e1 |
--------------------------------------------------------
2. Type show output status t1e1 and press Enter.
– Verify that the IO Status shows the desired signal format and “output”.
– Verify that the Port Status is “on”.
------------------------------------
| Port | io status | port status |
|------|-----------|---------------|
| t1e1 | e1 output | on |
|..................................|

Verifying TOD Functionality

1. Type show port-control and press Enter.
– Verify that the State for the TOD port is “enable”.

– Verify that the Signal/Format is the desired type.
--------------------------------------------
|# |Port |State |IO dir |Signal/Format|
|---|-------|--------|-------|-------------|
|1 |t1e1 |enable |output |t1 |
|...|.......|........|.......|.............|
|2 |pps10m |enable |output |10MHz |
|...|.......|........|.......|.............|
|3 |tod |enable |output |cisco |
--------------------------------------------
2. Type show output status tod and press Enter.
– Verify that the State for the TOD port is “enable”.

TOD CISCO output message
*,A,56415,13/05/02,03:52:17,000.0,0,37N22.716,121W55.581,+00
14
or
TOD China Mobile output message
GPS time of week : 347953

GPS week : 1738
Leap second : 16
PPS status : 0
PPS Tacc : 7
Clock source : 2
Clock status : 6
Clock alarms : 0x2
Verifying 10 MHz/ 1PPS Functionality

1. Type show output config pps10m and press Enter.

– Verify that the State is “enable”.

Port config
--------------------------------------
|---------|---------|----------------|
| pps10m | enable | pps |
|.........|.........|................|


This chapter describes maintenance and troubleshooting procedures for the

In This Chapter
 Preventive Maintenance
 Safety Considerations
 ESD Considerations
 Troubleshooting
– Diagnosing the TP 2300/2700 By Symptom
– Diagnosing the TP 2300/2700- Reading LED Conditions
 Repairing the TimeProvider 2300/2700
 Upgrading the Firmware
 TimeProvider 2300/2700 Part Numbers
 Returning the TimeProvider 2300/2700
 User’s Guide Updates
 Contacting Technical Support

Preventive Maintenance
Preventive Maintenance
The TimeProvider 2300/2700 requires minimal preventive maintenance. Ensure the

unit is not exposed to hazards such as direct sunlight, open windows, water, or
extreme heat. See Environmental Requirements, on page 43, for electromagnetic
compatibility conditions that may cause damage.
Caution: To avoid electromagnetic discharge damage to the circuitry,

never attempt to vacuum the TimeProvider 2300/2700.
Table 5-1 lists preventive maintenance measures to be performed periodically. Do

not disassemble components just for the purpose of inspection.
Table 5-1. Preventive Maintenance
Item Inspection Corrective Action Interval
Chassis Inspect for dirt or foreign Clean the exterior of chassis with Periodically
material a soft dry cloth
Cables Inspect for pinched, worn or Replace pinched, worn or Periodically

damaged cable damaged cable at the first
opportunity
Connectors Inspect for loose or damaged Tighten loose connectors. If Periodically

connector damaged, replace the connector
and/or cable at the first opportunity
Safety Considerations
Follow your company’s safety guidelines and policies when working on or around
live equipment.
ESD Considerations
Maintenance personnel should wear ESD wrist straps when installing or working on
all TimeProvider 2300/2700 equipment. Plug the user-supplied wrist strap into the

Troubleshooting
Troubleshooting
Symptoms, LEDs, and System Messages can all be very helpful in troubleshooting
the TP 2300/2700. Use the show alarm and show event commands to view
system messages.
Note: The TP2300/2700 incorporates a system reboot function

(watchdog) if any of the system's software become unresponsive. If
the system's software is unresponsive for 15 minutes, then the
watchdog timer will report an event in the event log (add the actual
event here), and the system will reboot.
Diagnosing the TP 2300/2700 By Symptom

Table 5-2 presents troubleshooting information for the TP 2300/2700 based on
symptoms. Table 5-3 presents diagnostic information for the TP 2300/2700 using
front panel LEDs. See Table A-1 in Appendix A, System Messages for Event IDs,
system messages and associated corrective actions.
Table 5-2. Troubleshooting Symptoms
Troubleshooting Procedure /
Symptom Probable Cause
Corrective Action
No LED lit No power to unit Check power supply
Check to ensure that UPS (if applicable) is

operating correctly
Both A and B fuses on Remove both fuses and replace

the branch over-current
protection unit are blown
Loss of ground Re-attach ground wires
Loose power cabling to Check that power cables to unit are

unit securely fastened
Chassis is faulty Contact Microsemi FTD Services and

Support

Troubleshooting
Corrective Action
No PTP flow between TP Cable connections Check the cable connections and SFP or
2300/2700 Grandmaster Ethernet connections.
and client
Verify that SFP connector models are
(If LED for port is OFF) recommended and supported.
Ethernet Auto Negotiation Check that either Ethernet Auto

settings Negotiation is enabled or that speed has
been set to a compatible level with the
connecting network element (show
ethernet config command).
Make sure that only full-duplex network

devices are used. The TP 2300/2700
does not support half-duplex devices,
such as hubs, for PTP connections.
No PTP flow between TP VLAN / non-VLAN  Verify that VLAN configuration is

2300/2700 Grandmaster configuration is incorrect correct with show vlan-config eth2
and client
 Check VLAN and IP configuration of
(If LED for port is ON PTP client
and ping to client is
unsuccessful) Note: The TP 2300/2700 uses the clock
ID as a unique identifier for PTP clients
and can only allow for one instance of the
clock id to be serviced. If a PTP client with
a single clock ID requests service using
two different IP addresses or VLANs, the
TP 2300/2700 will use the IP
address/VLAN of the latest request.
IP address configuration  Verify that IP configuration is correct

is incorrect with show ip config eth2
 Verify that IP status is correct with

show ip status eth2
If status does not look correct, restart

interface with set ip state eth2
ipv4 restart
IP address of ETH1 and Make sure the IP addresses for MGMT,

ETH2 ports are in the ETH1 and ETH2 ports are on different
same network/subnet networks/subnets.

Troubleshooting
Corrective Action
No PTP flow between TP Client configuration for Check master table setting of client.
2300/2700 Grandmaster master table is incorrect
and client
PTP state set to Disable Change PTP state to Enable with set ptp
(If LED for port is ON
master config eth2 command for the
and ping to client is
ETH2 port.
successful)
PTP Max Clients for TP If number of clients exceeds max for TP
2300/2700 exceeded 2300/2700, extra clients are ignored.
Purchase license for additional clients.
PTP domain setting for Verify domain setting for GM matches the
GM does not match domain setting for the client. Check GM
client’s domain domain setting with show ptp master
config eth2 command for the port.
PTP max allowable rate Check sync-limit and delay-limit settings

settings for sync and of GM with show ptp master config
delay less than values of eth2 command for the profile used on
client ETH2 port. If max allowable rates of GM
are less than those of client, use the set
ptp master config eth2 command for
the profile on the ETH2 port to increase
sync-limit and delay-limit rates to meet or
exceed rate values for clients. Or
decrease rate settings for client to a value
less than or equal to settings of GM.
Profile and profile Verify settings for master match the client.
settings do not match
client

Troubleshooting
Corrective Action
No PTP flow between TP VLAN / non-VLAN Verify that VLAN configuration is correct
2300/2700 client and configuration is incorrect with show vlan config eth1
master
Check VLAN and IP configuration of PTP
(If LED for port is ON master
and ping to master is IP address configuration  Verify that IP configuration is correct
unsuccessful) is incorrect with show vlan config eth1
 Verify that IP status is correct with

show ip status eth1
If status does not look correct, restart

interface with set ip state eth1
ipv4 restart.
IP address of ETH1 and Make sure the IP addresses for MGMT,

ETH2 ports are in the ETH1 and ETH2 ports are different
same network/subnet networks/subnets.
No PTP flow between TP ETH1 port client Check master table setting of ETH1 port
2300/2700 client and configuration for master client with show ptp client config
master table is incorrect eth1 telecom-2008 command.
(If LED for port is ON

PTP state for ETH1 client Change PTP state to Enable with set ptp
and ping to master is port set to Disable client config eth1 command for the
successful) ETH1 client port.
PTP domain setting for Verify domain setting for ETH1 port client
ETH1 port client does not matches the domain setting for the
match master’s domain master. Check ETH1 port client domain
setting with “show ptp client config eth1”
command for the port.
PTP max allowable rate Check sync-limit and delay-limit settings

settings for sync and of ETH1 client with show ptp client
delay more than values of config eth1 command. If max allowable
master rates of client are more than those of
master, use the set ptp client config
eth1 command to decrease rates to be
less than or meet rate values for master.
Or increase rate settings for master to a
value more than or equal to settings of
ETH1 client port.
Profile and profile Verify profile settings for master match the
settings for the ETH1 client.
client do not match
master

Troubleshooting
Corrective Action
Upgrading firmware Firewall set to “Block” for Use show firewall command to check
retrieving file failed FTP or SCP firewall settings.
Use set firewall command to change
firewall settings.
FTP/SCP server file path Ensure that the file name and path in the
configured incorrectly command line string exactly matches the
file name, including extension name, and
path to the upgrade file.
User name / password Verify that the user name and password
for the FTP/SCP server is correct. Retry
upgrading firmware.
Passive (PASV) FTP Enable active mode on FTP server. The

mode being used. TimeProvider 2700 only supports active
FTP.
Linux, Windows, and other third-party FTP
servers can be used in the upgrade
process of the TP 2300/2700.
Using Up and Left arrows Some terminal programs produce

to move the cursor in unreadable characters when using the Up
terminal program and Left arrow buttons to retrieve and
modify previous commands. Type
commands in directly with alpha-numeric
keys.
Upgrading firmware failed Flash memory failed Retry upgrade. If upgrade fails again,
contact Microsemi.
System in Holdover No visible satellites Check if GNSS is set to auto or manual

using set gnss command. If set to
GNSS not tracking manual, verify that latitude and longitude
settings are correct. Try setting GNSS to
(GNSS LED is Amber) auto mode with set gnss command.
Wrong antenna type, Check GPS/GLONASS antenna for

cable length, or power approved power ratings, cabling for
level into GNSS port approved lengths, and actual power level
into GNSS port. The GPS/GLONASS
engine requires a gain at the antenna
connector input of the chassis to be
between 15 dB and 30 dB.

Troubleshooting
Corrective Action
System in Holdover Loss of Signal (LOS) of Check connection for T1/E1 input
E1 Input
Not tracking T1/E1 Input Check T1/E1 input source
Alarm Indication Signal Check T1/E1 input source

(GNSS LED is OFF)
(AIS)
Out of Frame (OOF) Check T1/E1 input source
Signal amplitude level Check T1/E1 input source
Check cables
System stays in warm-up Warm-up still in progress Typical warm-up time is:
Quartz 6 minutes
Rubidium 9 minutes
Note: Warm-up times may vary based on

environmental conditions and other factors.
Diagnosing the TP 2300/2700 Reading LED Conditions

Table 5-3 shows the function of the LED indicators on the front panel of the unit.
Table 5-3. LED Conditions
Indicator Label Description Corrective Action
Power POWER Green - Power available n/a

Indicator
Off - Power not available Check power supply
See Table 5-2 ,“No LED lit ” for

probable causes and more
corrective actions.

Troubleshooting
Table 5-3. LED Conditions (Continued)
-48V A-Bus PWR A Off - A-Bus power Off Check power level from power
A-Bus Battery supply to power A.
Indicator
Check connections to primary
power A.
Check ground connections.
Check A fuse on the branch

over-current protection unit, and
replace if it is blown.
Green - A-Bus power On n/a
-48V B-Bus PWR B Off - B-Bus power Off Check power level from power
B-Bus Battery supply to power module B.
Indicator
Check connections to primary
power module B.
Check ground connections.
Check B fuse on the branch

over-current protection unit, and
replace if it is blown.
Green - B-Bus power On n/a
Clock Status CLOCK Green - operating normally n/a
Flashing Green - Time or

Frequency clock in Fast
Lock or Recovery state
Amber - Time or Frequency clock Use show alarm command to

in Freerun or Holdover view alarm IDs and descriptions.
state
See Table 5-2 or Table A-1 in
Appendix A, System
Messages for corrective actions.
Flashing Amber - Warmup state n/a

Troubleshooting
Alarm/fault ALARM Off - Operating normally n/a

indicator
Amber - Minor Alarm(s) Use show alarm command to
view alarm IDs and descriptions.
See Table A-1 in Appendix A,

System Messages for
corrective actions.
Red - Major/Critical Alarm(s) Use show alarm command to

view alarm IDs and descriptions.

System Messages for
corrective actions. After taking
corrective actions, use “reboot”
command.
GNSS Status GNSS Green - GNSS engine/interface is n/a

GNSS engine operating normally
status
indicator Amber - GNSS engine is not Use show alarm command to
tracking satellite view alarm IDs and descriptions.
See Table 5-2 or Table A-1 in

Appendix A, System
Messages for corrective actions.
Use show gnss status

command to see detected
satellites and their signal levels.
Red - GNSS Hardware alarm or Use show alarm command to

antenna fault view alarm IDs and descriptions.

System Messages for
corrective actions.
Off - GNSS is disabled This LED should only be OFF if

the TP 2700 is not using GNSS.
If GNSS is being used and the
light is off, contact support.

Troubleshooting
Ethernet MGMT Left Amber Flash - Activity n/a

Management
Port Left Off - No Activity n/a
LEDs on the Right Green - Link has been n/a
Ethernet established
connector
Right Off - Link has not been Check cable and connections
established
Ethernet Port 1 ETH1 Green - Link has been established n/a

ETH1 port
Off - Link has not been Check the cable connections and
link/activity S1
established SFP connections.
indicator
Verify that interface is enabled.

with set ip config command.
Verify that SFP connector

models are recommended and
supported.
Check that either Ethernet Auto

Negotiation is enabled or that
speed has been set to a
compatible level with the
connecting network element with
show ethernet command.
Make sure that only full-duplex

network devices are used. The
TP 2300/2700 does not support
half-duplex devices, such as
hubs, for PTP connections.

Troubleshooting
Ethernet Port 1 ETH1 Left Amber On or Flashing - n/a

ETH1 port 100M link has been
link/activity R1 established or is active
indicator
Right Green On or Flashing -
1000M link has been
established or is active
Left Amber Off - 100M link has not Check the cable connections.
been established
Right Green Off - 1000M link has with set ip config command.
not been established


Troubleshooting
Ethernet Port 2 ETH2 Green - Link has been established n/a

ETH2 port
Off - Link has not been Check the cable connections and
link/activity S2
established SFP connections.
indicator
Verify that interface is enabled

with set ip config command.
Verify that SFP connector

models are recommended and
supported.



Repairing the TimeProvider 2300/2700
Ethernet Port 2 ETH2 Left Amber On or Flashing - n/a

ETH2 port 100M link has been
link/activity R2 established or is active
indicator
Right Green On or Flashing -
1000M link has been
established or is active
Left Amber Off - 100M link has not Check the cable connections.
been established
Right Green Off - 1000M link has with show ip config command
not been established

Repairing the TimeProvider 2300/2700
The TimeProvider 2300/2700 cannot be repaired in the field.
There are no field-serviceable fuses in the TimeProvider 2700. If a fuse blows in a

TimeProvider 2700, the unit must be returned to the factory for repair.

Upgrading the Firmware
You can upgrade the firmware using CLI commands and software available from
Microsemi. Only users with Admin level access can execute the upgrade command.
The command places the TP 2300/2700 in the firmware download mode and
prevents all other sessions from making changes to the configuration. During the
upgrade process, no new sessions are allowed. Refer to Chapter 3, CLI Commands
and the command upgrade, on page 193 for details on the upgrade process.
Upon receipt of any new/repaired equipment, perform the relevant software

upgrade procedure below prior to putting the shelf into service.
Caution: To avoid a possible service call, do not issue a command to

the TimeProvider 2300/2700 during an upgrade and do not remove
power from the TimeProvider 2300/2700 during an upgrade. Doing so
could corrupt the flash memory, disabling the TimeProvider
2300/2700.
Note: Linux, Windows, and other third-party FTP servers can be used
in the upgrade process of the TP 2300/2700.

TP 2300/2700 Upgrade
This method is the easiest and quickest upgrade method, but there will be Loss of
Service (LOS) at reboot. The upgrade will take approximately 7 minutes to
complete. The TP 2300/2700 must be rebooted after it has been upgraded for the
new version of firmware to take effect.
1. Verify that SSH or telnet connection to the TP 2300/2700 is available
2. Upgrade using the command "upgrade <filepath> [ftp: | scp:]

<ftp-ip-address> <username>"
Note: The FTP firewall is set to “Block” by default. Use the following
command to set the MGMT firewall to “Allow” for telnet
communications:
set firewall mgmt ftp allow
Note: The TimeProvider 2700 only supports active FTP; it does not
support passive (PASV) mode.
3. Enter the password for the server when prompted.
4. Enter “Yes” when queried if you want to reboot the system after the firmware is
upgraded.
5. Verify that the TimeProvider 2700 is running correctly by issuing commands

"show status", "show alarm", and "show inventory". If the system is showing
an alarm for a setting that is disabled, re-enable and disable that setting and the
alarm will be cleared.
Note: Configuration changes made after the upgrade but before the
reboot will not be available after the reboot. The configuration after
reboot will be the same as that immediately after the upgrade.
Example:

“/symm/TimeProvider_EdgeMaster/current_upd”, FTP server IP address
192.168.5.56, username: “bob321”, Password: “bob1231”.

ftp:192.168.5.56 bob321 <enter>

TimeProvider 2300/2700 Part Numbers
The following sections provide part numbers for the system, accessories, and
GNSS antenna kits.
System and Accessory Part Numbers

This section provides part numbers and descriptions for the system and accessories
available for the TimeProvider 2300/2700. Also available as separately ordered
items are 23-inch (58.42 cm) rack mounting adapters and 21-inch (ETSI) rack
mounting adapters. See Table 5-4 for TP 2300 component part numbers. See Table
5-5 for TP 2700 component part numbers. See Table 5-6 for accessories.
Table 5-4. TP 2300 Component Part Numbers
Item Part Number
Base Units
Includes 8 PTP Output Clients, PTP (Input), Sync-E (Input/Output), 10 MHz/1PPS
(Output), TOD (Output), and 19" rack mount kit. T1/E1 support available via SW
license.
TP 2300 Boundary Clock, DC, OCXO, 8 Clients 090-50240-101
TP 2300 Boundary Clock, DC, Rubidium, 8 Clients 090-50240-102
TP 2300 Boundary Clock, AC, OCXO, 8 Clients 090-50240-201
TP 2300 Boundary Clock, AC, Rubidium, 8 Clients 090-50240-202
Installation and Rack Mounting Adaptor Kits
21-inch (ETSI) Bracket Rack Mounting Adaptor Kit 093-00011-000
23-inch (58.42 cm) Bracket Rack Mounting Adaptor Kit 093-00012-000
Software Licenses
TP 2300 License - Enable TDM (E1/T1) 920-50260-102
TP 2300 License - Default L3 Multicast Profile 920-50260-103
TP 2300 License - 8 to 16 PTP Output Clients 920-50260-016

Table 5-4. TP 2300 Component Part Numbers (Continued)
Item Part Number
Note: The TP2700 Grand Master does not include PTP Input
Reference License (ordered separately).
Table 5-5. TP 2700 Component Part Numbers
Item Part Number
Base Configuration
Includes 8 PTP Output Clients, Sync-E (Input/Output), integrated high performance
GNSS receiver (GPS or GLONASS), 10 MHz/1PPS (Output), TOD (Output), 19" rack
mount kit. T1/E1 support available via SW license.
TP 2700 PTP Grandmaster, DC, GNSS, OCXO, 8 Clients 090-50201-111
TP 2700 PTP Grandmaster, DC, GNSS, Rubidium, 8 Clients 090-50201-112
TP 2700 PTP Grandmaster, AC, GNSS, OCXO, 8 Clients 090-50201-211
TP 2700 PTP Grandmaster, AC, GNSS, Rubidium, 8 Clients 090-50201-212
Software Licenses
TP 2700 License - PTP Input Reference 920-50220-010
TP 2700 License - Concurrent GNSS (GPS & GLONASS) 920-50220-100
TP 2700 License - PTP Default Profile (L3 Multicast) 920-50220-103

Table 5-5. TP 2700 Component Part Numbers (Continued)
Item Part Number
TP 2300 License - PTP Default Profile (L3 Multicast) 920-50260-103
Table 5-6. Accessories
Item Part Number
Optical 1000 Base-LX Single-Mode Ethernet 1310nm SFP 121-20621-10-2

Transceiver
Optical 1000 Base-SX Multi-Mode Ethernet 850nm SFP 121-20621-11-2

Transceiver
TP 21-inch Rack Mount Adaptor Kit 093-00011-000
TP 23-inch Rack Mount Adaptor Kit 093-00012-000
AC Power Cable, US Connector 160-00004-02
AC Power Cable, UK Connector 160-00004-03
AC Power Cable, EU Connector 161-30307-00-2
TP GNSS Adapter Cable 1.2M SMA(M) TYPE-N(F) 060-00039-000

Returning the TimeProvider 2300/2700
GNSS Antenna
Table 5-7 lists the GNSS antenna kits. GNSS Antenna Kits include: a High
Performance GNSS (GPS/GLONASS) L1 Antenna, a Coaxial Lightning Surge
Suppressor, two outdoor rated Type N Coax Cables, and an SMA-to-Type N
adapter cable (PN: 060-00039-000).
Table 5-7. GNSS Antenna Kits
Antenna Amplifier Coax Cable

Antenna Kit Part Number
Gain Gain Length
TP 2700 GNSS (GPS/GLONASS) 990-13180-020 26 dB NA 20M

Antenna Kit, 20 M

Antenna Kit, 40 M

Antenna Kit, 70 M
TP 2700 GNSS (GPS/GLONASS) 990-13180-150 26 dB 25 dB 150M

Antenna Kit, 150 M
TP 2700 GNSS (GPS/GLONASS) 990-13180-230 40 dB 25 dB 230M

Antenna Kit, 230 M
TP 2700 GNSS (GPS only) 990-13180-300 40 dB 25 dB 300M

Antenna Kit, 300 M
Returning the TimeProvider 2300/2700
You should return the equipment to Microsemi only after you have exhausted the
troubleshooting procedures described earlier in this chapter, or if Microsemi FTD
Services and Support has advised you to return the unit.
Note: Please retain the original packaging for re-shipping the

product. If the original packaging is not available, contact Microsemi
FTD Services and Support for assistance.
Repacking the Unit

Return all units in the original packaging. If the original packaging is not available,
contact Microsemi FTD Services and Support. Use standard packing procedures for
products being returned for repair to protect the equipment during shipment.
Connectors should be protected with connector covers or the equipment should be
wrapped in plastic before packaging. Ensure that the display and connectivity
panels are protected when packaged.

User’s Guide Updates
Equipment Return Procedure

To return equipment to Microsemi for repair:
1. Call Microsemi FTD Services and Support at 888-367-7966 (toll-free in USA

only), 408-428-7907, or +49 700 3288 6435 in Europe, Middle East, or Africa to
obtain a return material authorization number (RMA) before returning the product
for service.
You can request an RMA on the internet at

Retain the assigned RMA number for future reference.
2. Provide a description of the problem, product item number, serial number, and
warranty expiration date.
3. Provide the return shipping information (customer field contact, address,

telephone number, and so forth.)
4. Ship the product to Microsemi, transportation prepaid and insured, with the
Return Material Authorization (RMA) number and item numbers or part numbers
clearly marked on the outside of the container to the address given with the RMA.
Repaired equipment is returned to you with shipping costs prepaid by Microsemi.
User’s Guide Updates
When this manual is updated the updated version will be available for downloading
from Microsemi’s internet web site. Manuals are provided in PDF format for ease of
use. After downloading, you can view the manual on a computer or print it using
Adobe Acrobat Reader.
Manual updates are available at:
Note: If you are downloading a product manual for the first time, you
will need to register with Microsemi for a username and password. If
you are currently registered, login and download the manual update.

Contacting Technical Support
Contacting Technical Support
To order any accessory, contact the Microsemi Sales Department. See

www.microsemi.com/sales-contacts/0 for sales support contact information. If you
encounter any difficulties installing or using the product, contact Microsemi
Frequency and Time Division (FTD) Services and Support:
U.S.A. Call Center:

including Americas, Asia and Pacific Rim
Frequency and Time Division (FTD)
3870 N 1st St.
San Jose, CA 95134
Toll-free in North America: 1-888-367-7966

Telephone: 408-428-7907
Fax: 408-428-7998
email: ftd.support@microsemi.com
Internet: www.microsemi.com/ftdsupport
Europe, Middle East, and Africa (EMEA)

Microsemi FTD Services and Support EMEA
Altlaufstrasse 42
85635 Hoehenkirchen-Siegertsbrunn
Germany
Telephone: +49 700 3288 6435

Fax: +49 8102 8961 533
E-mail: ftd.emeasupport@microsemi.com
ftd.emea_sales@microsemi.com

This section provides information about the system messages that are displayed in
response to a provisioning event or to an alarm that occurs when an associated
threshold or timer is outside of the provisioned setting.
In This Appendix
 Message Provisioning
 System Notification Messages

Message Provisioning
Message Provisioning
The TimeProvider 2300/2700 and its expansion shelves support logging of events
using syslog defined facility and severity codes and system defined facility codes as
follows:
Facility codes
4 Security/authorization messages
20 TimeProvider 2300/2700 Messages (events and alarms)
21 TimeProvider 2300/2700 Command History
22 TimeProvider 2300/2700 Messages (events and alarms)
Severity codes
2 (critical) Critical: critical conditions
3 (major) Error: error conditions
4 (minor) Warning: warning conditions
5 (event) Notice: normal but significant condition
Notes: Severity codes 2, 3, and 4, are also indicated by the Alarm

LED(s) on the front panel.
The syslog message format is as follows:
Mmm dd hh:mm:ss
host_name Process-name AlarmID,Index,Severity, MsgText
Where:
 Mmm = Month; dd = date; hh:mm:ss = system time

 host_name = hostname
 process-name = alarmd
 AlarmID = 000 thru Max_AlarmID
 Index = 0 thru 155
 Severity = Event | Minor | Major | Critical (defined by severity code)
 MsgText = (see tables)

System Notification Messages
Syslog messages are stored according to facility code and/or severity:
 Syslog messages with facility code 4 are stored in the Security Log.
 Syslog messages with facility code 20 and a severity of 2 | 3 | 4 are stored in the
Alarm Log.
 Syslog messages with facility code 20 and a severity of 5 are stored in the Event
Log.
 Syslog messages with facility code 21 are stored in the Command Log.
 Syslog messages with facility code 22 are not stored in the TP 2300/2700. They
can be forwarded to the remote syslog server.
Table A-1 provides a list of system notification messages. These messages are
logged and sent to a remote syslog server if configured. Alarms will also generate
an SNMP trap. See Table A-2 for secondary index values, where applicable.
Notes: Transitory Events represent transitions that are short-lived,

such as when GNSS is selected as the Time reference (ID 024) or
when the SSM for the SYNCE/T1E1 input changes (ID 032).
Table A-1. System Notification Messages
Event Msg Trans-

Description MsgText Corrective Action
ID Level itory
Entered 001 Minor No Entered time/frequency No action required

time/frequency warm-up state
warm-up state
Transitioned out of No action required

warm-up state

time/frequency free-run state
free-run state
Transitioned out of
free-run state No action required

Table A-1. System Notification Messages (Continued)
Event Msg Trans-

ID Level itory
Entered 003 Event No Entered time/frequency No action required

time/frequency fast-track state
fast-track state
fast-track state

time/frequency normal-track state
normal-track state
normal-track state

time/frequency bridging state
bridging state
bridging state
Entered 006 Minor No Entered time/frequency  Check input

time/frequency holdover state references
holdover state  Check configuration
for correct reference
selection
 Check reference
status
 Check ref
configuration for
Priority and PQL
values. See Show
REF command.

holdover state

time/frequency holdover recovery state
holdover recovery
state
holdover recovery state

Event Msg Trans-

ID Level itory
GNSS/SYNCE/PTP 021 Minor No GNSS/SYNCE/PTP/T1E1  If this persists for

/T1E1 Input Poor Input Poor Quality > 1hr check input
Quality reference.
 For GNSS check
signal quality.
 For PTP check PTP
input Status
 For T1/E1 check T1
or E1 status
Input poor quality cleared No action required
GNSS/PTP input 022 Event No GNSS/PTP input time No action required

time qualified qualified
Exit Input Time qualified No action required

cleared
GNSS/SYNCE/PTP 023 Event No GNSS/SYNCE/PTP/T1E1 No action required

/T1E1 input input frequency qualified
frequency qualified
Input frequency qualified No action required
GNSS/PTP input 024 Event Yes GNSS/PTP input selected No action required
selected as time as time reference
reference
n/a n/a
GNSS/SYNCE/PTP 025 Event Yes GNSS/SYNCE/PTP/T1E1 No action required

/T1E1 input input selected as
selected as frequency reference
frequency reference
n/a n/a

Event Msg Trans-

ID Level itory
T1E1 Input LOSS 026 Minor No T1E1 Input LOSS OF  Check if cable is
OF SIGNAL (LOS) SIGNAL (LOS) securely connected.
 Check signal source
is present and
configured properly.
E1T1 Input LOSS OF No action required

SIGNAL cleared
T1E1 Input ALARM 027 Minor No T1E1 Input ALARM Check alarm condition
INDICATION INDICATION SIGNAL and frame format of input
SIGNAL (AIS) (AIS) source signal in T1/E1
port.
T1E1 Input ALARM

INDICATION SIGNAL No action required
cleared
T1E1 Input OUT OF 028 Minor No T1E1 Input OUT OF Check frame format of
FRAME (OOF) FRAME (OOF) input source signal in
T1/E1 port. It should
match with the input
configuration for the port.
E1T1 Input OUT OF

FRAME cleared No action required
T1E1 Input CRC 029 Minor No T1E1 Input CRC ERROR Enable CRC in input
ERROR (CRC) (CRC) source signal, or disable
CRC in TimeProvider
2300/2700 T1/E1 input
port.
E1T1 Input CRC ERROR

cleared No action required
T1E1 Input 030 Minor No T1E1 Input BIPOLAR Check input source
BIPOLAR VIOLATION (BPV) signal or the connection
VIOLATION (BPV) cable.
E1T1 Input BIPOLAR

VIOLATION cleared No action required

Event Msg Trans-

ID Level itory
SYNCE/T1E1 input 032 Event Yes SYNCE/E1T1 input SSM No action required
SSM changed changed
n/a n/a
INCOMPATIBLE 051 Minor No INCOMPATIBLE

TRANSPORT TRANSPORT TYPE
TYPE
INCOMPATIBLE No action required

TRANSPORT TYPE
cleared
PTP input lost 052 Minor No PTP INPUT LOST  Check Ethernet
connection.
 Check PTP input
configuration
 Check that PTP
Master is functioning
PTP INPUT LOST

PTP master 053 Event Yes PTP master switched Check Status of
switched configured masters.
n/a n/a
PTP input 054 Event No PTP input time/frequency

time/frequency not not traceable
traceable
PTP INPUT NOT No action required

TRACEABLE cleared
PTP server 071 Minor No PTP server exceeded # Buy additional client
exceeded # percent percent of client limit on licenses
of client limit on ETH2
ETH2
PTP server near packet No action required

limit cleared

Event Msg Trans-

ID Level itory
PTP client 072 Event Yes PTP client  Check configuration

xx:xx:xx:xx:xx:xx:xx: xx:xx:xx:xx:xx:xx:xx:xx on Client device
xx dropped from dropped from ETH2 client  Check both physical
ETH2 client list list and IP connectivity
on ETH2.
 Check that client
devices have unique
clock ID's
n/a n/a
PTP client 073 Event Yes PTP client No action required

xx:xx:xx:xx:xx:xx:xx: xx:xx:xx:xx:xx:xx:xx:xx
xx added to ETH2 added to ETH2 client list
client list
n/a n/a
PTP client list on 074 Event Yes PTP client list on ETH2 No action required
ETH2 refreshed refreshed
n/a No action required
PTP state changed 075 Event Yes PTP state changed to Check if you deleted the
to disabled on ETH2 disabled on ETH2 PTP license or disabled
PTP.
n/a n/a
PTP state changed 076 Event Yes PTP state changed to No action required
to listening on ETH2 listening on ETH2
n/a n/a
PTP state changed 077 Event Yes PTP state changed to No action required
to master on ETH2 master on ETH2
n/a n/a

Event Msg Trans-

ID Level itory
PTP state changed 078 Event Yes PTP state changed to Another master has been
to passive on ETH2 passive on ETH2 selected because of
better quality.
n/a n/a
GNSS receiver 091 Minor No GNSS receiver  Reboot

communications communications failed  If problem persists
failed call SGS for support.
GNSS receiver
communications No action required
failure cleared
GNSS receiver not 092 Minor No GNSS receiver not  Check Antenna
tracking satellite tracking satellite installation
 Check if Antenna
cable is connected
properly.
 Installation should
conform to the
guidelines as
described in
Appendix C.
GNSS receiver not

tracking satellite cleared No action required
GNSS signal low 093 Minor No GNSS signal low  Check Antenna
installation
 Check if Antenna
cable is connected
properly.
 Installation should
conform to the
guidelines as
described in
Appendix C.
GNSS signal normal No action required

Event Msg Trans-

ID Level itory
GNSS antenna 094 Major No GNSS antenna voltage Check for short circuit in
voltage out of range out of range (#) the antenna cable.
(#)
GNSS antenna voltage No action required

out of range cleared
GNSS antenna 095 Major No GNSS antenna current Not supported at this
current out of range out of range (#) time.
(#)
GNSS antenna current Not supported at this

out of range cleared time.
GNSS antenna 096 Minor No GNSS antenna Check for short circuit in
short-circuit short-circuit the antenna cable.
If shorted antenna, then

out-of-range and
short-circuit alarms will
be generated.
GNSS antenna No action required

short-circuit cleared
GNSS antenna 097 Minor No GNSS antenna Check for Antenna not
open-circuit open-circuit connected or AC coupled
splitter. If using a splitter
you must at least draw
10mA of current from the
TP2700. This can be
achieved by adding a 50
ohm termination.
If no antenna, then
open-circuit and
out-of-range alarms both
will be generated
GNSS antenna No action required

open-circuit cleared

Event Msg Trans-

ID Level itory
Ethernet port link 111 Minor No Ethernet port ETH# link  Check cable.
down down  Check the box the
interface is
connected to.
 Check
Auto-negotiation.
Ethernet port link down No action required

cleared
Excessive traffic on 112 Minor No Excessive traffic on port  Check traffic level on
port ETH{1|2} ETH# network
 Check for intrusion
attempts.
 Check broadcast
traffic.
(See Footnote 1)
Excessive traffic cleared No action required

on Ethernet port
Unsupported SFP 113 Minor No Unsupported SFP on  Copper SFP's are

on ETH{1|2} ETH# not supported and
will generate this
alarm.
 Replace SFP with
Microsemi-
approved optical
SFP listed in User
Guide
Unsupported SFP cleared

on Ethernet port No action required

Event Msg Trans-

ID Level itory
SYNCE Ethernet 114 Major No SYNCE Ethernet Restart Ethernet

Auto-Negotiation Auto-Negotiation Interface by issuing the
Configuration Configuration Failure command:
Failure set ip state eth[x]
ipv4 restart
With 1000BT Ethernet,

one device is the master
and the other is the
client. For SyncE, the
source of synchronization
must be the 1000BT
master. Therefore, the
Ethernet port for the
source of SyncE
synchronization will be
configured as master and
the other device will be
configured as a client. If
both devices are
configured as masters or
both as clients, then an
error condition exists and
the TP2700/TP2300 will
generate an alarm. If
SyncE is enabled, the
TP2700/TP2300 will
configure the ETH1 port
as a client and the ETH2
port as a master. If the
"SyncE Ethernet
Configuration Failure"
alarm is active, then the
configuration of the
device connected to the
TP2700/TP2300 should
be corrected.
No action required
SYNCE Ethernet
Auto-Negotiation
Configuration Failure
Cleared

Event Msg Trans-

ID Level itory
Power out of range 131 Critical No +1.2V out of range  If alarm persists
(1.0)/-5.0V out of range power cycle/reboot
(#V)/  Call SGS support if it
persists after
reboot/power cycle.
Power out of range No action required

cleared
Operational Failure: 132 Critical No Operational failure: 1PPS  If alarm persists

interrupt. GNSS upgrade power cycle/reboot
failure after the 1PPS  Call SGS support if it
interrupt. persists after
reboot/power cycle.
Operational failure
Battery(-48V)-A 133 Major No Battery(-48V)-A failure Check power

failure connections and external
DC supply that is
supplying DC power to
your unit
Battery(-48V)-A failure No action required

cleared
Battery(-48V)-B 134 Major No Battery(-48V)-B failure Check power

failure connections and external
DC supply that is
supplying DC power to
your unit
Battery(-48V)-B failure

Event Msg Trans-

ID Level itory
FPGA failure 135 Critical n/a FPGA failure  If alarm persists

power cycle/reboot
 Call SGS support if it
persists after
reboot/power cycle.
FPGA failure cleared No action required
Flash partition 136 Critical No Flash partition failure Not supported at this time
failure
Flash partition failure No action required

cleared
PLL synthesizer 137 Critical No PLL synthesizer unlock  If alarm persists

unlock power cycle/reboot
persists after
reboot/power cycle.
PLL unlock cleared No action required
Rubidium unlock 138 Critical No Rubidium unlock  If alarm persists

power cycle/reboot
persists after
reboot/power cycle.
Rubidium unlock cleared No action required
Temperature out of 139 Minor No Temperature out of range Check your operating
range environment.
Temperature out of range No action required

cleared

Event Msg Trans-

ID Level itory
Production 151 Critical No Production configuration  If alarm persists

configuration data data error power cycle/reboot
error  Call SGS support if it
persists after
reboot/power cycle.
Production configuration No action required

data error cleared
Time Line has been 152 Event Yes Time Line has been No action required
Changed Changed
n/a n/a
Phase Has Been 153 Event Yes Phase Has Been Aligned No action required
Aligned
n/a n/a
System log time has 154 Event Yes System log time has been Not supported at this time
been updated updated
n/a n/a
System reboot 155 Event Yes System reboot No action required
n/a n/a
1. The excessive traffic alarm is set if the count of Ethernet packets received in one second exceeds a
threshold. All traffic received by the TP2700 Ethernet ports is counted, such as ARP, ICMP, IGMP, PTP
unicast signaling, multicast, and PTP management messages.
Threshold:
 1200 packets/sec for each port

Table A-2. Secondary Index Descriptions for System Notification Messages
Event Secondary Secondary Index

Description
ID Index Description
001 Entered time/frequency warm-up 0-1 0=time

state 1=freq
002 Entered time/frequency free-run 0-1 0=time

state 1=freq
003 Entered time/frequency fast-track 0-1 0=time

state 1=freq
004 Entered time/frequency 0-1 0=time

normal-track state 1=freq
005 Entered time/frequency bridging 0-1 0=time

state 1=freq
006 Entered time/frequency holdover 0-1 0=time

state 1=freq
008 Entered time/frequency holdover 0-1 0=time

recovery state 1=freq
021 GNSS/SYNCE/PTP/T1E1 Input 0-3 0=GNSS

Poor Quality 1=SYNCE
2=PTP
3=T1E1
022 GNSS/PTP input time qualified 0, 2 0=GNSS

2=PTP
023 GNSS/SYNCE/PTP/T1E1 input 0-3 0=GNSS

frequency qualified 1=SYNCE
2=PTP
3=T1E1
024 GNSS/PTP input selected as time 0, 2 0=GNSS

reference 2=PTP
025 GNSS/SYNCE/PTP/T1E1 input 0-3 0=GNSS

selected as frequency reference 1=SYNCE
2=PTP
3=T1E1
026 T1E1 Input LOSS OF SIGNAL 3 3=T1E1

(LOS)
027 T1E1 Input ALARM INDICATION 3 3=T1E1

SIGNAL (AIS)


Description
028 T1E1 Input OUT OF FRAME 3 3=T1E1

(OOF)
029 T1E1 Input CRC ERROR (CRC) 3 3=T1E1
030 T1E1 Input BIPOLAR VIOLATION 3 3=T1E1

(BPV)
032 SYNCE/T1E1 input SSM 1, 3 1=SYNCE

changed 3=T1E1
051 INCOMPATIBLE TRANSPORT n/a n/a

TYPE
052 PTP input lost n/a n/a
053 PTP master switched n/a n/a
054 PTP input time/frequency not 0-1 0=TIME

traceable 1=FREQ
071 PTP server exceeded # percent 2 2=ETH2

of client limit on ETH2
072 PTP client xx:xx:xx:xx:xx:xx:xx:xx 2 2=ETH2

dropped from ETH2 client list
073 PTP client xx:xx:xx:xx:xx:xx:xx:xx 2 2=ETH2

added from ETH2 client list
074 PTP client list on ETH2 refreshed 2 2=ETH2
075 PTP state changed to disabled 2 2=ETH2
076 PTP state changed to listening 2 2=ETH2
077 PTP state changed to master 2 2=ETH2
078 PTP state changed to passive 2 2=ETH2
091 GNSS receiver communications 0 0=GNSS

failed
092 GNSS receiver not tracking 0 0=gnss

satellite
093 GNSS signal low 0 0=gnss
094 GNSS antenna voltage out of 0 0=gnss

range (#)
095 GNSS antenna current out of 0 0=gnss

range (#)
096 GNSS antenna short-circuit 0 0=gnss


Description
097 GNSS antenna open-circuit 0 0=gnss
111 Management port link down link down 0-2 0=mgmt

1=eth1
2=eth2
112 Excessive traffic on port ETH{1|2} 1-2 1=eth1, 2=eth2
113 Unsupported SFP on ETH{1|2} 1-2 1=eth1, 2=eth2
114 SYNCE Ethernet Auto-Negotiation 1-2 1=eth1, 2=eth2

Configuration Failure
131 Power out of range 0-3, 6-7 0=+1.2v,

1= - 5.0
2=+2.5v,
3=+3.3v,
6=+1.5V
7= + 5.0V(ocxo)
132 Operational failure: 1PPS interrupt 0 0-=1pps

133 Battery(-48V)-A failure n/a n/a
134 Battery(-48V)-B failure n/a n/a
135 FPGA failure n/a n/a
136 Flash partition failure: 0-3 0: fail-fix-control

fail-fix-control 1: fail-fix-config.1
2: fail-fix-config.2
3: fail-fix-pst
137 PLL synthesizer unlock 0 0=synthesizer
138 Rubidium unlock n/a n/a
139 Temperature out of range n/a n/a
151 Production configuration data n/a n/a

error
152 Time Line has been Changed n/a n/a
153 Phase Has Been Aligned n/a n/a
154 System log time has been n/a n/a

updated
155 System reboot n/a n/a

This appendix provides mechanical and electrical specifications and factory defaults
for the TimeProvider 2300/2700.
In This Appendix
 Specifications
 Factory Defaults

Specifications
Specifications
This section provides the specifications for the TimeProvider 2300/2700 input and
output signals.
Mechanical
Table B-1. TimeProvider 2300/2700 Mechanical Specifications
Mounting 19 in. or 23 in. Rack
Rack Mounting For front mounting location unit protrudes 0.77 in /

1.956 cm
See Figure 2-2 and Figure 2-3 for drawings with

detailed chassis dimensions.
Width 17.24 in. / 438 mm
Height 1.73 in. / 44 mm; 1 RU
Depth 9.3 in. / 237 mm

10.07 in. / 256 mm - including connectors on faceplate
Weight
AC model 7.6 lb. / 16.72 kg
DC model 8.1 lb. / 17.82 kg
Environmental
Table B-2. TimeProvider 2300/2700 Environmental Specifications
Operating Temperature -40 to 65C, -40 to 149 F  OCXO [startup > -20C (-4F)]
-5 to 55C, 23 to 131 F  Rubidium oscillator
Storage Temperature -40 to 70C, -40 to 158 F
Heat Dissipation DC Version: 30.95 BTUs

AC Version: 47.12 BTUs.
Operating Humidity 5% to 95% RH, maximum, w/condensation
Operating Altitude -200 feet (-60 m) to 13000 feet (4000 m)
Acoustic Noise 0 dBA (negligible due to passive cooling)

Specifications
Power
TimeProvider 2300/2700 Power Specifications
Input Voltage Range –38.4 VDC to –72.0 VDC
or
90–264 VAC, 50/60 Hz
DC Recommended 1.5 A, maximum

Battery Feed Fuse
DC Power - OCXO
Maximum, Warmup 20 W, 417 mA @ ‐48V

Operating 17 W, 354 mA @ ‐48V
DC Power - Rubidium
Maximum, Warmup 28 W, 583 mA @ ‐48 V

Operating 20 W, 417 mA @ ‐48 V
AC Power - OCXO
Maximum, Warmup 43 W, 350 mA @ 120V

Operating 37 W, 300 mA @ 120V
AC Power - Rubidium
Maximum, Warmup 60 W, 500 mA @ 120V

Operating 43 W, 350 mA @ 120V

Specifications
Compliance & Certifications
Table B-3. TimeProvider 2300/2700 Compliance Specifications
Safety Certifications  IEC 60950-1:2005 (Second Edition) + Am

1:2009
 EN 60950-1:2006/A11:2009/A1:2010/
A12:2011 CB Scheme
 UL60950-1/CSA C22.2 No. 60950-1, Second
Edition
EMC Immunity
Resistibility ESD ETSI: EN 61000-4-2

NEBS: GR-1089-CORE Sec. 2.1
KN 61000-4-2
Electrical Fast Transient (EFT) ETSI: EN 61000-4-4

NEBS: GR-1089-CORE Sec. 2.2
KN 61000-4-4
Radiated Emissions ETSI: EN 61000-4-3, EN 55022 (CISPR 22): 2010

NEBS: GR-1089-CORE Sec. 3.2.1.1
Conducted Emissions ETSI: EN 61000-3-2, 61000-3-3, 61000-3-4,

- AC Voltage & AC/DC Current 61000-4-5, 61000-4-6, 61000-4-11
EN 55022 (CISPR 22): 2010
NEBS: GR-1089-CORE Sec. 3.2.2.1 & 3.2.2.2
KN 61000-4-5, KH 61000-4-11
VZ.TPR.9205 (TEER) Issue 5, October 2011: 9.0
Conducted Emissions ETSI: EN 55022 (CISPR 22): 2010

- Telecom Ports NEBS: GR-1089-CORE Sec. 3.2.3
Immunity Radiated GR-1089-CORE Sec. 3.3.1

KN 61000-4-3
Immunity Conducted ETSI: EN 61000-4-6

GR-1089-CORE Sec. 3.3.2 & 3.3.3.1
EMC Compliance  FCC Part 15 (Class A)

 AS/NZS CISPR22 (Class A)
 EN55022 (Class A)
 KN55022 (Class A)
 ICES 003 (Class A)
 VCCI, Class A
 EU 2004/108/EC Electromagnetic
Compatibility Directive
 EN 300 386 Telecommunications Network
Equipment (EMC)

Specifications
Table B-3. TimeProvider 2300/2700 Compliance Specifications (Continued)
Environmental & Physical
Environmental Compliance  EN300-019-2-3, Class T3.2

 ETSI EN 300 019-2-2 (1999) - Transportation,
Class T2.3
 ETSI EN 019-2-1 (2000) - Storage, Class T1.2
 RoHS (6 of 6)
Low-Temperature Exposure & NEBS: GR-63-CORE Sec. 4.1.1.1

Thermal Shock
High Relative Humidity Exposure NEBS: GR-63-CORE Sec. 4.1.1.2
High-Temperature Exposure & NEBS: GR-63-CORE Sec. 4.1.1.3

Thermal Shock
Operating Temperature and NEBS: GR-63-CORE Sec. 4.1.2

Humidity Criteria
Altitude NEBS: GR-63-CORE Sec. 4.1.3
Temperature Margin Evaluation NEBS: GR-63-CORE Sec. 4.1.4
Heat Dissipation and Energy NEBS: GR-63-CORE Sec. 4.1.6

Efficiency (ATIS TEER)
Surface Temperature NEBS: GR-63-CORE Sec. 4.1.7
Equipment Assembly Fire Tests NEBS: GR-63-CORE Sec. 4.2.2
Needle Flame NEBS: GR-63-CORE Sec. 4.2.3
Packaged Equipment Shock Criteria NEBS: GR-63-CORE Sec. 4.3.1
Unpackaged Equipment Shock NEBS: GR-63-CORE Sec. 4.3.2

Criteria
Earthquake Environment and NEBS: GR-63-CORE Sec. 4.4.1

Criteria
Office Vibration Environment and NEBS: GR-63-CORE Sec. 4.4.4

Criteria
Transportation Vibration Criteria NEBS: GR-63-CORE Sec. 4.4.5
Gaseous Contaminants (Indoor NEBS: GR-63-CORE Sec. 4.5.1

Levels)
Hygroscopic Dust NEBS: GR-63-CORE Sec. 4.5.1
Illumination NEBS: GR-63-CORE Sec. 4.7

Specifications
Serial Port
Table B-4. TimeProvider 2300/2700 Serial Port Specifications
Item Description
Connector Type 9-pin, female D connector
Connector Label Craft
Interface RS-232, data terminal equipment (DTE)
Baud Rate 57.6 Kbps
Data Bits 8
Parity Bit None
Stop Bits 1
Flow Control None
MGMT Port
Table B-5. TimeProvider 2300/2700 LAN Port Specifications
Connector Type RJ-45 (10/100/1000 Base-T) - Supports telnet

sessions and SSH sessions over TCP/IP.
Connector Label MGMT
Input Signals
GNSS Receiver
Table B-6. TimeProvider 2700 GNSS Input Signal Specifications
Parameter Specification
Signal Type GNSS L1
Gain Between 15 dB and 30 dB, including gain of antenna

and loss of cable

Specifications
Table B-6. TimeProvider 2700 GNSS Input Signal Specifications (Continued)
Frequency GPS: 1575.42 MHz center frequency

GLONASS: 1602 MHz center frequency
Impedance 50 ohms
Coupling DC (center pin provides DC power to the GNSS

antenna or in-line amplifier)
Antenna voltage 4.5  5.6 V

current 180 mA (max)
Connector Type SMA connector, female
Connector Label GNSS

Specifications
DS1 Input
Table B-7. TimeProvider 2300/2700 DS1 Input Signal Specifications
Signal Type ANTSI T1.403. G.703 Section 5 Framed T1

or Format: D4, ESF, 1544 kHz
Impedance 100 ohms
Connector Type RJ48c, balanced pair (shares with E1)
Connector Label T1/E1
E1 Input
Table B-8. TimeProvider 2300/2700 E1 Input Signal Specifications
Signal Type G.703 Section 9 Framed E1

or G.703 Section 13 2048 kHz
Format CAS or CCS, CRC4 enable/disable
Impedance 120 ohms
Connector Type RJ48c, balanced pair (shares with DS1)
PTP Input
Table B-9. TimeProvider 2300/2700 PTP Input Signal Specifications
Ports ETH1
Connector Type
S1 Ethernet Small Form-factor Pluggable (SFP)
Optical 1000 Base-X
R1 RJ45, 100/1000 Base-T

Specifications
Table B-9. TimeProvider 2300/2700 PTP Input Signal Specifications (Continued)
Connector Label ETHERNET, R1 and S1
PTP Profile Telecom-2008
SyncE Input
Table B-10. TimeProvider 2300/2700 SyncE Input Signal Specifications
Ports ETH1
Connector Type
Optical 1000 Base-X
R1 RJ45, 100/1000 Base-T

Specifications
Output Signals
PTP Output
Table B-11. TimeProvider 2300/2700 PTP Output Signal Specifications
Ports ETH2
Connector Type
Optical 1000 Base-X
R2 RJ45, 100/1000 Base-T
PTP Profile Telecom-2008 and ITU G-8265.1 (Unicast)

Default and Default Ethernet (Multicast)
SyncE Output
Table B-12. TimeProvider 2300/2700 SyncE Output Signal Specifications
Ports ETH2
Connector Type
Optical 1000 Base-X
R2 RJ45, 100/1000 Base-T

Specifications
DS1 Output
Table B-13. TimeProvider 2300/2700 DS1 Output Signal Specifications
Signal Type ANTSI T1.403. G.703 Section 5 Framed T1

or Format: D4, ESF, 1544 kHz
Connector Type RJ48c (shares with E1)
Impedance 100 ohms
Coupling Transformer coupled
Extra framing Isolated pulse for testing
E1 Output
Table B-14. TimeProvider 2300/2700 E1 Output Signal Specifications
Type G.703 Section 9 Framed E1

or G.703 Section 13 for 2048 kHz
Format CAS or CCS, CRC4 enable/disable
Connector Type RJ45 (shares with DS1)
Impedance 120 ohms
Coupling Transformer coupled
1PPS+TOD Output
Table B-15. TimeProvider 2300/2700 1PPS+TOD Output Signal Specifications
Connector Type RJ45
Connector Label TOD
Signal Level RS-422

Specifications
Table B-15. TimeProvider 2300/2700 1PPS+TOD Output Signal Specifications (Continued)
Timing Relationship between 1PPS Transmission of a TOD message starts 10 ms

and TOD (default) after the rising edge of 1PPS signal,
and the transmission is completed within 500
ms, as shown in Figure B-1. This TOD
message indicates the time of the current 1
PPS rising edge, and is sent at a rate of once
per second.
Rise Time -1PPS Pulse 50 ns
Pulse Width 50 ms
TOD Frame TOD messages use whole 8-bit bytes for

transmission, with check sum protection.
Message type and message ID are used to
clarify messages. Follows Big Endian
convention when a field is longer than one byte,
where bit 0 represents the least significant bit
(LSB), and bit 0 of each byte is transmitted first.
See Figure B-2.
See Table B-16 for TOD frame field

descriptions.
TOD Transmission Parameters Baud Rate: 9600

Parity Check: None
Start Bit: 1 (low level)
Stop Bit: 1 (high level)
Idle Frame: High level
Data Bits: 8
TOD Message Encoding Binary
Figure B-1. Timing Relationship Between 1PPS and TOD for 1 PPS+TOD Outputs

Specifications
Figure B-2. TOD China Mobile Frame Structure
Table B-16. TOD China Mobile Frame Details
Field Name Field Length Description
Sync Char 1 1 byte Part of Frame Header

0x43 = ASCII character “C”
Sync Char 2 1 byte Part of Frame Header

0x4D = ASCII character “M”
Class 1 byte Basic classification of TOD China Mobile

message
ID 1 byte Serial number of TOD China Mobile message
Length 2 bytes Length of payload only

(Does not include Frame Header, Message Header,
Length Field itself, or FCS)
Payload 16 bytes Contains the message content

See Table B-17, Table B-18, and Table B-19
for Time Message details.
Frame Check 1 byte Generating polynomial FCS is:

Sequence G(x) = x8 + x5 + x4 +1
(FCS) Initial value of FCS is set to 0xFF, and there is
no need to negate the input data. Checksum
calculation uses right-shift calculation, and
there is no need to negate the output frame
check data. When the frame check sequence
is transmitted, the LSB (bit 0) is transmitted
first.

Specifications
Table B-17. TOD China Mobile Message Details
Message Type Class ID Length (bytes)
Time Information 0x01 0x20 16
Time Status 0x01 0x03 16
Table B-18. TOD China Mobile Time Information Message Payload Contents
Data
Byte Offset Name Unit Notes
Type
0 U4 Time of week (TOW) - GPS Second time of week
4 I4 Reserved - Reserved
8 U2 Week number - GPS week (GPS time)
10 I1 LeapS s Leap Seconds (GPS-UTC)
11 U1 1PPS status - 0x00 = normal

0x01 = Time sync equipment
(atomic clock) in holdover mode
0x02 = do not use
0x03 = Time sync equipment
(high stability crystal clock) in
holdover mode
0x04 = Transport carrier
equipment in holdover mode
Other values: reserved
12 U1 TAcc - PPS jitter category (0 - 255):

0 = 0 ns
1 = 15 ns
2 = 30 ns
…
255 = no defined
Note: this value is fixed to 255
for transmission and base
station equipment
13 U1 Reserved - Reserved

Specifications
Table B-19. TOD China Mobile Time Status Message Payload Contents
Data
Byte Offset Name Unit Notes
Type
0 U1 Clock source type - 0x00 = GLONASS

0x01 = GPS
0x02 = 1588
0x03 = others
1 U2 Status of the clock - GPS fix type, range 0 - 3

source 0x00 = no fix
0x01 = dead reckoning only
0x02 = 2D fix
0x03 = 3D fix
0x04 = GPS + dead reckoning
combined
0x05 = reserved
0x06 = tracking (PTP only)
0x07 - 0xff = reserved
3 U2 Monitor alarm - Clock source status alarms:

Bit 0: Reserved
Bit 1: Antenna open
Bit 2: Antenna shorted
Bit 3: Not tracking satellites
Bit 4: Reserved
Bit 5: Survey in progress
Bit 6: No stored position
Bit 7: Leap second pending
Bit 8: In test mode
Bit 9: Position is questionable
Bit 10: Reserved
Bit 11: Almanac not complete
Bit 12: Reserved
Note: For GNSS only.

For other references, only bits
1, 2, and 7 are used.
5 U1 Reserved - -
6 U1 Reserved - -
7 U1 Reserved - -
8 U4 Reserved - -
12 U4 Reserved - -

Specifications
Figure B-3. TOD Cisco Message Frame Structure
Example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1 Satellite availability: * = valid, ! = not valid

2 Revision
3 Modified Julian date (number of days past midnight, Nov 17, 1858)
4 Year/month/day
5 Hours:minutes:seconds
6 Indicator of time zone offset (+, –, or 0)
7 Time zone offset
8 Leap second indicator
9 Latitude
10 Longitude
11 Altitude above mean sea level in meters
12 Alarm severity: EV = event, MN = minor, MJ = major, CL = critical
13 Alarm source
14 Alarm cause: holdover, BT3 warm-up, or hardware fault
Note: The Cisco TOD message format reports leap second using
TAI-UTC. The China Mobile TOD message reports GPS leap
seconds using GPS-UTC.
Table B-20. TOD Cisco Message Frame Structure Details
Position Description Units Notes
1 Satellite Availability  * = available

! = not available
2 Revision 
3 Modified Julian Date days Number of days past midnight,
November, 17, 1858
4 Date  Date in the format yy/mm/dd
5 Time hours, Hours:Minutes:Seconds

minutes and
seconds
6 Indicator of time zone  +, , or 0

offset
Indicates if offset is to added,
subtracted, or no offset

Specifications
Table B-20. TOD Cisco Message Frame Structure Details
Position Description Units Notes
7 Time zone offset hours
8 Leap second indicator 

9 Latitude degrees Value will b 0 if no valid position is
available.
10 Longitude degrees Value will b 0 if no valid position is

available.
11 Altitude above mean sea meters Value will b 0 if no valid position is

level available.
12 Alarm severity  CL= Critical

MJ = Major
MN = Minor
EV = Event
13 Alarm source 
14 Alarm cause 

Specifications
10 MHz Output
Table B-21. TimeProvider 2300/2700 10 MHz Output Signal Specifications
Signal type LV TTL square wave

Duty cycle 50% +/- 5%
Connector type BNC male, shared with 1PPS output
Connector Label 10M / 1PPS
Impedance 50 
Amplitude 15 dBm to17 dBm
Jitter and Wander When tracking GNSS: per G.811 (PRS/PRC)

When tracking E1/T1/SyncE: per G.812
When tracking PTP GM w/o freq: per G.8261
1PPS Output Signal Specifications
Table B-22. TimeProvider 2300/2700 1PPS Output Signal Specifications
Signal type LV TTL square wave

Pulse width 20 s typical
Connector type BNC male, shared with 10 MHz output
Connector Label 10M / 1PPS
Impedance 50 
Amplitude 15 dBm to17 dBm
Rise Time < 10 ns
Jitter and Wander When tracking GNSS: per G.811 (PRS/PRC)

When tracking E1/T1/SyncE: per G.812
When tracking PTP GM w/o freq: per G.8261
Time accuracy 100 ns with respect to UTC when locked to

GNSS

GNSS Antenna Kits Specifications
Clocks
Table B-23. Holdover Performance
Phase Phase Phase Frequency

Oscillator
+/- 1.5 sec +/- 5 sec +/- 10 sec +/- 16 ppb
OCXO 1 hour 4 hours 12 hours 1 month
Rubidium 24 hours 3 days 5 days 5 years
Note: Holdover values are approximate and assume operation at

constant temperature, no initial frequency or phase offset, and that
the unit has been powered on for 2 weeks and locked to GNSS for
three consecutive days.
GNSS Antennas with Internal LNA Specifications

Table B-24 provides specifications for GNSS antennas with internal LNA
Table B-24. GNSS Antennas with Internal Low-Noise Amplifier Specifications
Characteristic Specification
Mechanical
Connector TNC jack
Mounting 19-mm diameter center mounting threaded stud with TNC

connector
Diameter 66.5 mm
Height 76.2 mm including radome and mounting threaded stud

with TNC connector
Weight 150 grams
Environmental
Operating Temperature -40 to +85 C
Vibration 3G, 10 to 200 Hz sweep
Humidity IP67 compliant

Table B-24. GNSS Antennas with Internal Low-Noise Amplifier Specifications
ESD Protection 15 kV air discharge
Electrical
Power +2.3 to +10 VDC, up to 15 ma at +2.3 VDC
Polarization Right-hand circular
LNA Gain, 26 dB antenna 26 dB +/- 2 dB
LNA Gain, 40 dB antenna 40 dB +/- 2 dB
Bandwidth 1575 to 1606 MHz
Noise Figure 2.5 dB typical
Output Impedance 50 ohms
Table B-25. GNSS Antenna Kits
Net
Delay
Antenna Kit Part Number Gain
(ns)
(dB)
TP 2700 GNSS (GPS/GLONASS) Antenna Kit, 20 meter 990-13180-020 76 22.5
TP 2700 GNSS (GPS/GLONASS) Antenna Kit, 150 meter1 990-13180-150 575 22.5
TP 2700 GNSS (GPS/GLONASS) Antenna Kit, 230 meter1 990-13180-230 902 22.5
TP 2700 GNSS (GPS/GLONASS) Antenna Kit, 300 meter 990-13180-300 1150

Note:
1
Kit includes a 25 dB coax low noise amplifier
Note: The cable delay and gain values correspond to the cable kit
being used in its entirety without modification. The values assume
that a splitter is not used. Splitters are not recommended.

GNSS Lightning Arrestor Specifications
Table B-26. Lightning Arrestor Specifications
Type Gas
Impedance 50 
Insertion Loss < 0.25dB
VSWR < 1.6:1
Dissipation Capacity 1000 Amperes, impulse 8/20 µsec
Connector Type N-Type
Temperature –50C to + 70C
Relative Humidity 100% Non-immersed
GNSS L1 Inline Amplifier Specifications
The GNSS L1 Inline Amplifier (112-00076-000) option boosts the signal from the
antenna. Use this amplifier on longer cable runs to maintain sufficient gain; it
receives power from the GNSS radio receiver through the antenna coaxial cable
connections. Table B-27 provides mechanical and electrical specifications for the
amplifier.
Table B-27. GNSS L1 Inline Amplifier Specifications
Mechanical
Connectors, (In/Out) TNC
Gain 25 dB +4/-0 dB
Dimensions, includes connectors Length: 2.32 in (59 mm)
Electrical
Power +3 VDC to +10 VDC
Current 25 mA typical
Noise Figure <1.5 dB

GNSS Antenna Coaxial Cable Specifications

Other cable types are available. Table B-28 provides antenna cable specifications.
Before using additional cables, verify that the total antenna system gain is
acceptable.
Table B-28. Antenna Cable Specifications
Loss
DC Resistance Type Center
Cable Type (@1.575 GHz dB Flammability
( per foot) Conductor
per foot)
RG213/U 0.093 dB 0.0030 Stranded 13 AWG U/L CSA

(Belden 8267)
RG213/U 0.093 dB 0.0030 Stranded 2.62 mm2 U/L CSA

(Belden 8267)
UHF/VHF 0.058 dB 0.0027 Solid 10 AWG

(Belden 9913)
UHF/VHF 0.058 dB 0.0027 5.26 mm2

(Belden 9913)
UHF/VHF 0.089 dB 0.0027 Solid 10 AWG Plenum U/L

(Belden 89913) CSA
UHF/VHF 0.089 dB 0.0027 5.26 mm2 Plenum U/L

(Belden 89913) CSA
LMR-400 0.051 dB Shield – 0.00165 0.109 inch Solid

Center – 0.00139
LMR-400 0.051 dB Shield – 0.00165 0.27686 cm2 Solid

Center – 0.00139
LMR/CNT 240 0.101 dB Inner Conductor – .056 inch diameter

0.0032 Solid BC
Outer Conductor –
0.00389
LMR/CNT 600 0.034 dB Inner Conductor – .176 inch diameter

0.00053 Solid BCCAI
Outer Conductor –
0.0012

Factory Defaults
Factory Defaults
TP 2300/2700 Defaults
Table B-29. General and Communication Parameters
Description Default Value Value Range
Telnet Firewall Block Allow | Block
ICMP Firewall Allow Allow | Block
SSH Firewall Allow Allow | Block
SNMP Firewall Block Allow | Block
FTP Firewall Block Allow | Block
HTTPS Firewall Block Allow | Block
User #1 Name admin 20 ASCII Characters
User #1 Password symmadmin** 32 ASCII Characters, a Minimum of 8
User #1 Access level admin user | config |admin
EIA-232 Port 57.6k-8-N-1 fixed
MGMT IP Mode Static DHCP | Static
MGMT IP State Enable Enable | Disable
MGMT IP Address 192.168.0.100 Valid IPv4 Address
MGMT Gateway Address 0.0.0.0 Valid IPv4 Address, where value of

0.0.0.0 is used for no gateway
MGMT Network Mask 255.255.255.0 Valid IPv4 Mask
Hostname Timeprovider 20 ASCII Characters
Image None 1, 2
Asset Number “unknown” 20 ASCII Characters
SNMP Manager (Up to 3) None Address: Valid IPv4 Address

Engine ID: Max of 32 ASCII Characters

Factory Defaults
Table B-29. General and Communication Parameters (Continued)
SNMP User (Up to 10) None Username: Max of 20 ASCII Characters

Security Level: noauth, auth, priv
Auth Type: MD5, SHA
Auth Key: Max of 32 ASCII Characters,
Min of 8 ASCII Characters
Privacy Protocol: DES, AES
Privacy Key : Max of 32 ASCII
Characters, Minimum of 8
SNMP Trap User (Up to 3) None Username: Max of 20 ASCII Characters

Security Level: noauth, auth, private
Auth Type: MD5, SHA
Auth Key: Max of 32 ASCII Characters
Min of 8 ASCII Characters
Privacy Protocol: DES, AES
Privacy Key : Max of 32 ASCII
Characters, Minimum of 8
SNMP v2 Community (Up to None Name: Max of 20 ASCII Characters

10) Access: read-only | read-write
SNMP Trap Version 2 2, 3
SNMP v2 State Enable Enable | Disable
UTC to TAI offset 35 20 to 255
Remote Syslog Host 0.0.0.0 Valid IPv4 Address
Remote Syslog State Disable Enable | Disable
Local Alarm Log Buffer Size 100 0 to 100 Kbytes
Local Event Log Buffer Size 100 0 to 100 Kbytes
Local Command Log Buffer 100 0 to 100 Kbytes

Size
Local Security Log Buffer 100 0 to 100 Kbytes

Size
Log Diagnostic State Disable Enable | Disable
Auto-Sync Enable Enable | Disable
Bridging Time 300 100 to 100000

Factory Defaults
Table B-30. GNSS Input Port Parameters
GNSS Priority - Time 1 1 to 10
GNSS Priority - Frequency 1 1 to 10
GNSS Use Configured PQL - Enable Enable | Disable

State
GNSS Configured PQL - Time 1 1 to 16
GNSS Configured PQL - Freq. 1 1 to 16
GNSS Antenna Cable Delay 0 0 to 999 ns
GNSS Position Mode Auto Auto | Manual
GNSS Position Lat - LAT = Ndd:mm:ss.ss or

N37:22:43.425 Sdd:mm:ss.sss
Long - 0 to 90 degrees
W121:55:34.815 LONG = Eddd:mm:ss.ss or
Elevation - 13.7m Wddd:mm:ss.sss
0 to 180 degrees
HEIGHT= ±hhhh.h height in
meters,
-10000.0 to 10,000.0 meters
GNSS Elevation Mask 10 5 to 60 degrees

Step size is 1 deg
GNSS Track Mode GPS GPS | GLONASS

| GLONASS-GPS
GNSS Antenna Current Enable Enable | Disable

Qualification
Table B-31. PTP Client ETH1 Port IP Parameters
IP Address 192.168.1.12 Valid IPv4 Address
IP Mask 255.255.255.0 Valid IPv4 Mask
Gateway 0.0.0.0 Valid IPv4 Address, special

value of 0.0.0.0 is used for
no gateway
State Enable Enable | Disable

Factory Defaults
Table B-31. PTP Client ETH1 Port IP Parameters (Continued)
Auto Negotiation Enable Enable | Disable
Speed All 100M | 1000M | All
Note: On the PTP Client Port, the client is capable of receiving

and processing messages from both one-step and two-step
clock masters, without any provisioning necessary,. The client
auto detects the two-step clock flag in Announce messages
from the master and based on the setting, runs a one-step or
two-step clock operation.
Table B-32. PTP Client ETH1 Input Port Parameters
PTP Active Profile Telecom-2008 Telecom-2008
PTP Priority - Time 2 1 to 10
PTP Priority - Frequency 2 1 to 10
PTP Use Configured PQL State Disable Enable | Disable
PTP Configured PQL - Time 3 1 to 16
PTP Configured PQL - Freq. 3 1 to 16
PTP State Enable Enable | Disable
TTL 64 1 - 255
DSCP 0 0 - 63
Unicast-negotiation Enable Enable | Disable
Lease-duration 300 60 - 1000 seconds
Announce-interval 1 -3 to 4
Sync-interval -6 -7 to -5
Delay-req-interval -6 -7 to -5
Announce-receipt-timeout 3 2 to 10
Domain 0 0 -255
Transport Ethernet Ethernet

Factory Defaults
Table B-32. PTP Client ETH1 Input Port Parameters (Continued)
Service-tier sync-mask sync-mask | modified-traffic-mask

| packet-prs |
sync-extended-mask
Asymmetry State Disable Enable | Disable
Asymmetry n/a Clear
Phase Offset 0 -1000000 to 1000000 ns
A positive offset value will make

phase outputs earlier. A negative
offset value will make phase
outputs later.
Master Table 192.168.1.11 valid IPv4 address
FPP Cluster Width1 10000 1000 to 10000000 ns
FPP Cluster Width2 100000 1000 to 10000000 ns
Table B-33. SyncE Input ETH1 Port IP Parameters
QL-State Enable Enable | Disable
Table B-34. T1/E1 Input Port Parameters
T1/E1 Input Port State Enable Enable | Disable
T1/E1 Input Port Priority 3 1 - 10
T1/E1 Input Port Configured 3 1 - 16

PQL
T1/E1 Input Port Disable Enable | Disable

User-Configured PQL State

Factory Defaults
Table B-34. T1/E1 Input Port Parameters (Continued)
T1/E1 Input Port Signal Type T1 T1 | E1
E1 Input Port Frame Type CCS CCS | CAS | freq2048khz
E1 Input Port CRC Enable Enable | Disable
E1 Input Port 1 SSM Bit 8 4|5|6|7|8
T1 Input Port Frame Type ESF D4 | ESF | freq1544khz
Table B-35. PTP Grand Master ETH2 Port IP Parameters
IP Address 192.168.2.12 Valid IPv4 Address
IP Mask 255.255.255.0 Valid IPv4 Mask
Gateway 0.0.0.0 Valid IPv4 Address, special

value of 0.0.0.0 is used for
no gateway
Auto Negotiation Enable Enable | Disable
Speed All 100M | 1000M | All
Table B-36. PTP Grand Master ETH2 Port VLAN Parameters - Fixed Index (116)
Address No VLAN configured Valid IPv4 Address
Mask No VLAN configured Valid IPv4 Mask
Gateway No VLAN configured Valid IPv4 Address
ID 0 2 to 4094
(not visible in VLAN table)
Priority 0 0 to 7

Factory Defaults
Table B-36. PTP Grand Master ETH2 Port VLAN Parameters - Fixed Index (116)
Mode Disable Enable | Disable
State Disable Enable | Disable
Table B-37. PTP Grand Master ETH2 Port VLAN Parameters - Non-Fixed
Ethernet Port Address No VLAN configured Valid IPv4 Address
Ethernet Port Mask No VLAN configured Valid IPv4 Mask
Ethernet Port Gateway No VLAN configured Valid IPv4 Address
ID 0 2 to 4094
(not visible in VLAN table)
Priority 0 0 to 7
Mode Disable Enable | Disable
State Disable Enable | Disable
Table B-38. PTP Grand Master ETH2 Port Active Profile
PTP Active Profile Telecom-2008 Telecom-2008 |

ITU-G.8265-1 | Default
Table B-39. PTP Grand Master Telecom-2008 Profile Unicast Parameters
PTP Timescale Auto Auto | PTP | Arb
PTP Priority 1 128 0 to 255

Factory Defaults
Table B-39. PTP Grand Master Telecom-2008 Profile Unicast Parameters (Continued)
PTP Domain 0 0 to 255
PTP TTL Value 64 1 to 255
PTP DSCP Value 0 0 to 63
PTP Max Number of Clients max 1 to max

(max # of clients determined by
the PTP client license
PTP Dither Disable Enable | Disable
PTP Two Step Disable Enable | Disable
PTP Unicast Negotiation Enable Enable | Disable
PTP Unicast Lease Limit 1000 60 to 1000 seconds
PTP Sync Limit –7 –7 to 7

Rate (2^y)
PTP Announce Limit –3 –4 to 4

Rate (2^y)
PTP Delay Limit –7 –7 to 7

Rate (2^y)
Service Load Alarm 90 10 to 100

Threshold
Table B-40. PTP Grand Master ITU-T G.8265.1 Profile Unicast Parameters
PTP TTL Value 4 to 23

Factory Defaults
Table B-40. PTP Grand Master ITU-T G.8265.1 Profile Unicast Parameters (Continued)

(max # of clients determined
by the PTP client license
PTP Unicast Negotiation Enable Enable | Disable
PTP Unicast Lease Limit 1000 60 to 1000 seconds
PTP Sync Limit –7 –7 to 7

Rate (2^y)
PTP Announce Limit –3 –3 to 4

Rate (2^y)
PTP Delay Limit –7 –7 to 7

Rate (2^y)
Service Load Alarm Threshold 90 10 to 100
Table B-41. PTP Grand Master Default Profile Multicast (Layer 3) Parameters
PTP TTL Value 64 1 to 255

PTP Client Timeout 300 10 to 3600 seconds

Factory Defaults
Table B-41. PTP Grand Master Default Profile Multicast (Layer 3) Parameters (Continued)
PTP Multicast Announce Receipt 3 2 to 10

Timeout
PTP Multicast VLAN ID 0 0 to 4094,

0 is used to signify no VLAN
PTP Multicast Sync Interval 0 –7 to 7

(2^y)
PTP Multicast Delay Interval 0 –7 to 7

(2^y)
PTP Multicast Announce Interval 1 –4 to 4

(2^y)
Table B-42. PTP Grand Master Ethernet Default Profile Multicast (Layer 2) Parameters

PTP Client Timeout 300 10 to 3600 seconds
PTP Multicast Announce Receipt 3 2 to 10

Timeout
PTP Multicast VLAN ID 0 0 to 4094,

0 is used to signify no VLAN
PTP Multicast Sync Interval -6 –7 to 7

(2^y)

Factory Defaults
Table B-42. PTP Grand Master Ethernet Default Profile Multicast (Layer 2) Parameters (Continued)
PTP Multicast Delay Interval -6 –7 to 7

(2^y)
PTP Multicast Announce Interval 1 –4 to 4

(2^y)
Table B-43. T1/E1 Output Port Parameters
T1/E1 Input/Output Port Output Input | Output
T1/E1 Output Port State Enable Enable | Disable
T1/E1 Input Port Priority 3 1 - 10
T1/E1 Input Port Configured 3 1 - 16

PQL
T1/E1 Input Port Disable Enable | Disable

User-Configured PQL State
T1/E1 Output Port Signal Type T1 T1 | E1
E1 Output Port Frame Type CCS CCS | CAS | freq2048khz
E1 Output Port CRC State Enable Enable | Disable
E1 Output Port SSM State Enable Enable | Disable
E1 Output Port 1 SSM Bit All 4 | 5 | 6 | 7 | 8 | All
E1 Output Port Zero Disable Enable | Disable

Suppression
T1 Output Port Frame Type ESF D4 | ESF | freq1544khz
T1 Output Port SSM State Enable Enable | Disable
Output Generation - Warm-up Squelch Squelch | On | AIS
Output Generation - Free-run Squelch Squelch | On | AIS
Output Generation - Holdover On Squelch | On | AIS
Output Generation - Fast-track On Squelch | On | AIS

Factory Defaults
Table B-44. T1/E1 Input / Output Parameters
T1/E1 IO Port Input Input | Output
Table B-45. 10MHz/1PPS Output Port Parameters
Description Default Value Value range
Output Port State Enable Enable | Disable
Signal Type PPS 10M | PPS
PPS Offset 0 -1000000 to 1000000
Table B-46. SSM Settings
SSM Option Option 1 Option 1 | Option 2
Alarm Default Values
Table B-47. GNSS Port Alarm Parameters
Alarm Delay Time 0 0 to 500000
Alarm State (for each alarm) Enable Enable | Disable
Alarm Severity Level See System 2 to 5

Notification
Messages, on
page 299

The GNSS L1 Reference Antenna is one component of a complete line of GNSS

accessories for your GNSS antenna system provided by Microsemi. These
accessories are designed to deliver precise GNSS signals over a wide temperature
range and in harsh environmental conditions.
In This Chapter
 Antenna Kits Overview
 Antenna Kits Accessories
 GNSS Antenna Installation
 Available GNSS Antenna Kits
 Antenna Coaxial Cable

Antenna Kits Overview
Antenna Kits Overview

When deciding on which of the available antenna kits meets your needs, the key
factor is the distance between the GNSS antenna and the TP 2700. There are
several coaxial cable lengths available to assist in receiving proper gains from the
GNSS antenna. Microsemi offers five antenna kits for the TP 2700.
Considerations for Antenna Installation

When installing the GNSS receiver, it is important to select the proper gain antenna
and coaxial cable to account for the insertion loss between the antenna and the
GNSS receiver. Selecting the proper gain avoids under-driving or over-driving the
receiver antenna input. To acquire satellites, the gain required for a L1 signal at
1575 to 1606 MHz (with some level of signal attenuation allowed) for a GNSS
receiver input is defined in the receiver’s manufacturer’s specification.
L1 antenna gains are usually specified as the maximum effective gain. Such an
antenna can have 4.5 to 10 dB less signal strength at different satellite azimuths
and elevations, depending on their reception pattern. The GNSS engine requires a
net gain at the antenna connector input of the chassis to be between 15 to 30 dB.
All antenna kits include the GNSS L1 antenna, mounting pipe, floor flange, lightning
arrestor, pre-assembled coaxial cable (for antenna to lightning arrestor), roll of 3M
2150 weatherproof tape, and a SMA cable adapter. The antennas and in-line
amplifiers have TNC connectors and the lightning arrestor has N connectors.
All antenna kits supplied use a LMR-400, or equivalent, low-loss coaxial cable. The
L1 signal loss of LMR-400 is 0.167 dB/meter. The L1 signal loss of a 90 V lightning
arrestor is typically 0.25 dB. See Antenna Coaxial Cable, on page 351.
GNSS Antennas with Low Noise Amplifiers

The GNSS antenna kits provide reception of GPS and GLONASS satellite RF
signals in the range 1575 to 1606 MHz, each with the correct gain required to
provide timing stability for the coaxial cable length included in the kit. Additions or
changes to these kits may change the gain and prevent adequate satellite
reception.
For kit information, see Available GNSS Antenna Kits, on page 359.
Accuracy of the antenna position determined using receiver survey depends on

providing RF gain to the GNSS receiver within a required range of 15 to 30 dB and
locating the antenna with an unobstructed field of view in a low multipath
environment. If these conditions are not met, the receiver survey will either require
longer than 20 minutes to complete or will not complete, preventing the GNSS input
from being used by the system as a reference. Also, timing stability will not be
optimized if these conditions are not met.

Antenna Kits Accessories
Antenna Kits Accessories

Lightning Arrestor
Microsemi offers the lightning arrestor for installations that require antenna coaxial
lead-in protection. The lightning arrestor passes DC power and frequencies in the
1.5 GHz range with L1 GNSS antennas. In most installations, the lightning arrestor
mounts near the point at which the antenna lead enters the facility. See the GNSS
Lightning Arrestor Specifications, on page 335 for specifications.
GNSS L1 In-line Amplifier

The GNSS L1 in-line amplifier (112-00076-000) option boosts the signal from the
antenna with total cable lengths of 150 and 230 meters. The amplifier receives
power from the GNSS receiver through the antenna coaxial cable connections. See
the GNSS L1 In-line Amplifier, on page 351 for specifications.
Antenna Coaxial Cable

Microsemi provides LMR-400 coaxial cables with N-type connectors on both ends.
Table C-2 lists the part numbers for the cables and its crimp kit and Table C-3 lists
cable specifications.

GNSS Antenna Installation

This section provides information about planning and installing a GNSS antenna.
Planning the Antenna Location

Prior to installing the antenna, you should plan the site, antenna location, grounding
scheme, cable route, and all other details.
Locating the Antenna

Use Figure C-1 as a guide to locate the antenna.
Figure C-1. Locating the GNSS Antenna
Warning: The TimeProvider 2700 GNSS interface uses the electrical

current it supplies to power a GNSS antenna to determine whether or
not the antenna is properly connected and functional. If the
TimeProvider 27000 does not detect any current, it will assume a
failed GNSS antenna and will consequently generate an alarm and
switch to another timing (non-GNSS) source.
Some GNSS splitters can block the DC current, and if used with
TimeProvider 2700, will cause the alarm condition described above.
Usage of such GNSS splitters with the TimeProvider 2700 will require
the installation of a 50 OHM load so that the TimeProvider 2700
GNSS interface is able to detect current and operate normally.

Caution: To avoid damage to the GNSS antenna, do not place the

antenna where high-power radio signals are beamed directly at the
unit. Such signals can damage the preamplifier of the GNSS antenna.
Warning: To avoid serious injury to personnel or damage to

equipment, exercise caution when working near high voltage lines.
In particular:
 Use extreme caution when installing the GNSS antenna near,
under, or around high voltage lines.
 Follow local building electrical codes for grounding using the
frame ground lugs on the shelf.
 The in-line amplifier receives 5 VDC power from the GNSS
receiver, and is supplied on the center conductor of the LMR-400
or equivalent coaxial cable.
 Microsemi does not recommend cutting the antenna cables
provided in the GNSS Antenna Kit.
Recommendation: Microsemi recommends that you consider the

following location and environment influences before installing the
GNSS antenna:
 If possible, provide the antenna with an unobstructed 360-degree

view of the sky from the horizon.
 In general, do not allow obstructions that obscure the horizon (as
viewed from the antenna) by more than 10 degrees, as shown in
Figure C-1.
 Locate the antenna well away from, and preferably in a plane
above electrical equipment such as elevators, air conditioners, or
other machinery.
 To reduce the risk of lightning damage, do not place the antenna at
the highest point of the building.
 Locate the GNSS antenna at least 3.7 m (12 ft.) from metallic
objects, if possible.
 Locate the antenna high enough to avoid drifted snow.
 Locate the lightning arrestor in a protected area to avoid contact
with standing water.
 Locate the antenna within 9.1 m (30 ft.) of the point at which the
antenna cable enters the building.
 Allow at least 3.0 m (10 ft.) of separation distance between GNSS
antennas.
 Surfaces above the plane of the unit that are between the antenna
and the horizon can produce reflected (multi-path) signals, which
can degrade the performance of the GNSS receiver.

Developing a Grounding Scheme

In addition to determining where to locate and mount the antenna and cabling, you
should develop a grounding scheme. The purpose of the grounding scheme is to
provide some protection against voltage surges and static discharge. If lightning
arrestors are used, they also need to be connected to the perimeter ground system
or to the bulkhead entrance panel that is connected to the perimeter ground system.
Caution: To ensure proper grounding, observe these precautions

when installing the antenna:
 Allow no sharp bends in the ground conductors. The ground

conductor must have a 9.1 m (30-ft.) radius for any bends made.
 Ensure that no painted surface insulates the lightning arrestor or
grounding clamps.
 Ensure that ground conductors are bonded to the metal enclosure
box (if used) and do not enter through an access hole.
 Do not use soldered connections for grounding purposes.
 Secure all grounding connections with mechanical clamp type
connectors.
 In general, follow local building codes when selecting a grounding scheme, wire
size, and installation.
Use #6 AWG (16 mm2) copper ground wire or larger, depending on the distance
to the earth ground electrode. Refer to your local electrical codes for specific
details. In most cases, #1/0 AWG (50 mm2) ground wire will maintain 1/10 the
resistance of the coaxial shield.
Note: Larger ground conductors provide better transient elimination;

that is, the larger the ground conductor, the less likely the chance of
transients.
 Connect lightning arrestors, if part of the grounding scheme, to earth ground

through a conductor.
Note: Do not connect the outside lightning arrestor ground to the

inside equipment rack ground. Doing so can defeat the protection
afforded by the lightning arrestor.
 Never connect antenna systems to the same earth ground connector as heating
and cooling systems, elevator or pump motors, or other motors or machinery
which can induce noise in the antenna system.
Antenna Installation Tools and Materials

These standard tools and materials are not supplied in the antenna kit, but may be
required for installing the GNSS antenna.

 Extra cable ties or acceptable cable clamps
 #6 AWG (16 mm2) copper ground wire (minimum)

 Eight-foot (2.9 m) ground electrode
 Custom mounting plates, U-bolts, PVC pipes, masonry bolt, etc. as needed for
mounting to a tower, roof, or wall of a building
 A cable puller may be required for installing the antenna coaxial cable
 Digital multivoltmeter (DVM)
Caution: To avoid damage to the connectors, do not use the

connectors to pull the cable. If at all possible, avoid bundling the
coaxial cable with other cables (and possible noise sources). Use
appropriate cable-pulling devices when pulling the coaxial cable
through conduit or a weather head.
Cutting Antenna Cables

Microsemi recommends that you coil excess cable to avoid gain mismatch between
the GNSS antenna and the GNSS receiver. Coiling the excess cable also allows
you to use the factory-installed crimped connector.
Microsemi does not recommend cutting the antenna cables provided in the GNSS
Antenna Kits. If you must cut the cables, please ensure that the following
requirements are met.
Cable Requirements – The total cable length from the GNSS receiver to the
antenna must not be shorter than the minimum cable lengths indicated in the GNSS
Antenna Kits (see Table C-1).
Connector Requirements – The cables provided with the GNSS antenna kit have
factory installed crimped connectors. If you cut these cables, you must supply and
add a connector. Microsemi recommends that you use only crimp-style N-type
connectors in the crimper kit for this application (see Table C-2).
Installing the Antenna

This section provides procedures for installing the GNSS antenna (see Figure C-2).
1. Insert the antenna into the right-angle mounting bracket and tighten it using the
antenna nuts.
2. Mount the right-angle bracket to the mast using for example, U-bolts.
3. To secure the coaxial cable to the mast, use 8-inch cable ties or appropriate
cable clamps.

4. Adhere to local building codes to determine the type and number of fasteners,
screws, bolts, etc. that may be required.
Note: Follow local building electrical codes when installing the GNSS
antenna.
Figure C-2. GNSS Antenna Installation
No in-line 3 In-line
amplifier amplifier
required for required for
Kits -020, Kits
-040, -070 5 4 -150, -230
6 8
7 9
1 GNSS antenna, TNC(f) (27 dB with kits -020, -040, -150; 41 dB with kits -070, -230)
2 Mounting Bracket Antenna (193-00044-000)
3 TNC(m) to TNC(m) straight adapter (121-00148-000)
4 In-line amplifier 25 dB, TNC(f) to TNC(f) (13813160-025-0)
5 TNC(m) to N(f) straight adapter (371-004)
6 10 m cable N(m) - N(m) (58521A-010)
7 Lightning arrestor, N(f) (112-43400-00-3)
8 Long cable N(m) - N(m) 58521A-xxx
9 1.2 m Cable adapter N(f) to SMA(m) 060-00039-000

Connecting the Cable to the Antenna

This section describes how to connect the coaxial cable to the mounted antenna.
Refer to Figure C-2 for the numbered references in the following procedure.
1. If an in-line amplifier is not required:
– Connect the TNC-N adapter (#5) to the antenna (#1).

– Connect the 10 m cable (#6) to the TNC-N adapter (#5).
2. If an in-line amplifier is required:
– Connect TNC-TNC adapter (#3) to the antenna (#1).

– Connect the in-line amplifier (#4) to the TNC-TNC adapter (#3).
– Connect the TNC-N adapter (#5) to the In-line amplifier (#4.)
– Connect the 10 m cable (#6) to the TNC-N adapter (#5).

coaxial cable with other cables (and possible noise sources). Use
appropriate cable-pulling devices when pulling the coaxial cable
through conduit or a weather head.
3. Connect the other end of the 10 m cable (#6) to the lightning arrestor (#7).
4. Connect the lightning arrestor (#7) to the long cable (#8).
5. Connect the other end of the long cable (#8) with the cable adapter (#9).
Caution: To avoid damage to internal solder connections, do not

over-tighten the connector.
Installing the Lightning Arrestor

Lightning arrestors should be installed in accordance with your antenna system
grounding scheme. To install a lightning arrestor, follow these steps:
1. Mount the lightning arrestor within 30 ft. (9 m) of the GNSS antenna.
2. Connect the ground wire between the lightning arrestor and the proper grounding
zone (building ground, master ground bar, or other) for the mounting location.
Recommendation: Microsemi does not recommend soldered

connections for grounding purposes. All grounding connections
should be secured with mechanical clamp connectors.

3. Wrap the connectors with weatherproof tape for added protection.
4. Verify that the antenna coaxial cable center conductor is not shorted to the shield of
the cable.

You should install the antenna cable from the lightning arrestor to the TimeProvider
2700 using the shortest route possible. Follow all applicable building and electrical
codes to ensure a water-tight and fire-resistant installation.

cable with other cables (and possible noise sources). Use appropriate
cable-pulling devices when pulling the cable through conduit or a
weather head.
To connect the GNSS antenna, perform the following steps:
1. Using a DVM, Verify that the center conductor is not shorted to the shield.
If the reading shows a short or open, you may have a shorted or open cable or
lightning arrestor. Therefore, apply the same measurements directly to the GNSS
antenna. This requires disconnecting the antenna cable at the antenna.
Note: The open-circuit range of an individual ohmmeter can cause

readings to vary among meters.
2. Secure the free end of the antenna cable to the SMA (f) antenna connector on
the front panel of the TP 2700.
Recommendation: Microsemi recommends coiling excess cable to

avoid gain mismatch between the GNSS antenna and the TP 2700.
Coiling the excess cable also allows you to use the factory-installed
crimped connector.
Antenna Installation Completeness Checklist

To verify that antenna installation is complete:
 Verify that all power and ground wires are installed correctly and securely
fastened.
 Verify that all input and output cables are properly installed.
 Verify that all antenna connectors are secure, tight, and weatherproofed.

Available GNSS Antenna Kits
 Microsemi does not recommend the use of GNSS splitters. However, if one is
used, it must provide a load of at least 10mA.
Available GNSS Antenna Kits

Each of the GNSS antenna kits are available with cable lengths of 20, 40, 70, 150
and 230 meters each providing RF gain to the GNSS receiver of between 15 and 30
dB using combinations of a GNSS 26 dB gain active antenna, a GNSS 40 dB gain
active antenna and a 25 dB gain GNSS in-line amplifier. Components are
weather-proof packaged per IP67 for exposed locations. The GNSS Input Card
provides power to the active antenna and in-line amplifier and then detects alarms
on antenna connection open conditions.
Microsemi does not recommend the use of GNSS splitters. Splitters reduce the
reliability of the overall system, add additional delay, and may not provide a DC load
to the unit. The TimeProvider 2700 requires at least 10mA of DC current load on the
antenna port to prevent an open-circuit alarm. This alarm will prevent using GNSS
as a reference.
All GNSS antenna kits include the antenna, mounting bracket, coaxial cable,
required adapters, a lightning arrestor, and other kit components. The GNSS
antenna kits are listed in Table C-1.
Table C-1. GNSS Antenna Kits for TimeProvider 2700
Cable Length Cable

(meters)
Antenna Kit Part Number Delay
(ns)
min max
TP 2700 GNSS (GPS/GLONASS) Antenna Kit, 990-13180-020 10 20 76

20 meter

40 meter

70 meter

150 meter

230 meter
Note: The cable delay values correspond to the cable kit being used
in its entirety without modification. The values assume that a splitter is
not used. Splitters are not recommended.

Table C-2. LMR-400 Antenna Coaxial Cable Accessories
Part Number Description
121-32212-00-2 Type N (male) connector for LMR-400 cable
12813080-000-0 Crimp Kit for LMR-400 or equivalent (10 ea. N-Type connector,
crimp tool, weatherproof tape)
Contact your sales office for available cable lengths and specific cable item number.
Table C-3. LMR-400/LMR-400FR Antenna Coaxial Cable Specifications
Type Center
Cable Type Measured Loss DC Resistance ()
Conductor
LMR-400 17.25 dB per 100 m Shield – 0.00165 per ft. 0.109 inch Solid
5.25 dB per 100 ft. Center – 0.00139 per ft. (0.27686 cm or
Shield – 0.005 per m (0.0602 cm2)
Center – 0.0045 per m

Appendix D PQL Mapping
This appendix provides details about the mapping between PQL and various
frequency synchronization quality level scales for input and output signals.
In This Appendix
 Purpose of Input and Output Mapping Tables
 PQL Input Mapping
 PQL Output Mapping

Appendix D Appendix I PQL Mapping
Purpose of Input and Output Mapping Tables

Reference inputs may use different scales for quality level. For example, the PTP
clockClass value, which is included in the Announce message, is used to advertise
the quality level of the clock. At the input, these different scales of quality level are
mapped to a common scale called PQL (priority quality level). The PQL scale is a
number from 1 to 16, with 1 being the highest quality and 16 being the lowest. Once
all input quality levels are mapped to PQL, internal processing (such as input
selection) will only use PQL as the quality indicator. See PQL Input Mapping, on
page 364 for PQL mapping of frequency inputs.
Figure D-1. PQL Input and Output Mapping
After an input is selected, the internal clock tracks this selected input and assumes
the quality indicated by the PQL of the selected input. At the output, the clock signal
is translated into various output formats, and the clock PQL is mapped to the scale
that is appropriate for each of the output formats. PQL Output Mapping, on page
366 shows how PQL is mapped for frequency outputs.
Quality Levels Defined by ITU-T

The mapping between PQL and various frequency synchronization quality level
scales conforms to the frequency synchronization quality levels defined in ITU-T
G.781 (for SSM) and ITU-T G.8265.1 (SSM and PTP clockClass).
G.781 defines five valid QL and SSM values for Option I network (2048 kbps
hierarchy), as shown in Table D-1.
Table D-1. G.781 QL and SSM values for Option I Network (2048 kbps hierarchy)
SSM
QL Clock Quality Definition
(Binary)
PRC 0x2 G.811
SSU-A 0x4 G.812 type I or V

Table D-1. G.781 QL and SSM values for Option I Network (2048 kbps hierarchy) (Continued)
SSM
(Binary)
SSU-B 0x8 G.812 type VI
SEC 0xB G.813, or G.8262 option I
DNU 0xF Should not be used for synchronization
G.781 defines ten valid QL and SSM values for Option II network (1544 kbps
hierarchy), as shown in Table D-2.
Table D-2. G.781 QL and SSM values for Option II Network (1544 kbps hierarchy)
SSM SSM
(Hex) (Binary)
PRS 04FF 0x1 G.811
STU 08FF 0x0 Synchronized - traceability unknown
ST2 0CFF 0x7 G.812 type II
TNC 78FF 0x4 G.812 type V
ST3E 7CFF 0xD G.812 type III
ST3 10FF 0xA G.812 type IV
SMC 22FF 0xC G.813, or G.8262 option I
ST4 28FF - Traceable to Stratum 4 freerun
PROV 40FF 0xE Provisionable by network operator
DUS 30FF 0xF Should not be used for synchronization
ITU-T G.8265.1 uses up all 16 binary SSM values defined in G.781 and maps them
to 16 values of PTP clockClass in the ITU telecom profile for frequency. The Option
II network QL-ST4 never had a binary SSM in G.781 and was not included in
G.8265.1. QL-ST4 is dropped in Microsemi implementation because Microsemi
products disqualify ST4 inputs and do not produce ST4 outputs.

PQL Input Mapping
PQL Input Mapping

Table D-3 shows PQL values converted from SSM or PTP clockClass for Option I
Network frequency references. Table D-4 shows PQL values converted from SSM
or PTP clockClass for Option II Network frequency references.
Table D-5 shows default PQL values for different reference types. Table D-8 shows
PQL values associated with various clock states for rubidium and quartz oscillators.
The Show pql-ssm command displays the Priority Quality Level (PQL) values for all
reference input signal types.
Table D-3. PQL Input Mapping for Option I Network - Converted from SSM or PTP clockClass
Input PTP Input PTP

Input E1 Input SyncE
To Input
Input QL
clockClass clockClass PQL
SSM SSM
G.8265.1 Tele2008/Default
80 1
0x0 0x0 QL-STU 82 2
0x2 0x2 QL-PRC 84 6 3
86 4
88 5
0x4 0x4 QL-SSU-A 90 7 6
92 13 7
94 8
0x8 0x8 QL-SSU-B 96 14 9
98 10
100 11
102 52 12
0xB 0xB QL-SEC/EEC1 104 58 13
106 14
108 15
0xF 0xF QL-DNU 110 248 16
invalid_SSM invalid_SSM

PQL Input Mapping
Table D-4. PQL Mapping for Option II Networks - Converted from SSM or PTP clockClass
Input PTP Input PTP

Input T1 Input SyncE To
Input QL Input
clockClass clockClass
SSM SSM PQL
04FF 0x1 QL-PRS 80 1
08FF 0x0 QL-STU 82 2
84 6 3
0CFF 0x7 QL-ST2 86 4
88 5
78FF 0x4 QL-TNC 90 7 6
92 13 7
94 8
96 14 9
98 10
7CFF 0xD QL-ST3E 100 11
10FF 0xA QL-ST3 102 52 12
104 58 13
22FF 0xC QL-SMC/EEC2 106 14
40FF 0xE QL-PROV 108 15
30FF 0xF QL-DUS 110 248 16
invalid SSM invalid_SSM
Table D-5. Time and Frequency References - Default Priorities and PQL Values

Input Port
Time GNSS Port 1 1
Time ETH1 Port - PTP 2 3
Frequency GNSS Port 1 1
Frequency ETH1 Port - PTP 2 3

PQL Output Mapping
Table D-5. Time and Frequency References - Default Priorities and PQL Values (Continued)

Input Port
Frequency ETH1 Port - SyncE 4 3
Frequency T1 / E1 3 3
PQL Output Mapping

Output signal quality level is determined by the quality level of the internal clock.
When the internal clock is tracking a reference, the quality level (PQL value) of the
internal clock is the PQL of the selected reference. At the outputs, the frequency
PQL is converted to the appropriate quality levels for different output signal types,
as shown in Figure D-1. See Table D-6 below for PQL output mapping for Option I
networks. See Table D-7 below for PQL output mapping for Option II networks.
When the internal clock is not tracking a reference, the quality level of the internal
clock is determined by its clock state and its oscillator quality. Table D-8 shows the
internal clock quality level for different oscillator types and clock states.
Table D-6. PQL Output Mapping for Option I Network - Converted to SSM or PTP clockClass
Output Output PTP Output PTP

From Output E1
SyncE
Output Output QL
PQL SSM
SSM G.8265.1 Tele2008/Default
1 0x2 0x2 QL-PRC 80 6
2 82
3 84
4 0x4 0x4 QL-SSU-A 86 7
5 88
6 90
7 0x8 0x8 QL-SSU-B 92 13
8 94
9 96 14
10 98
11 100

PQL Output Mapping
Table D-6. PQL Output Mapping for Option I Network - Converted to SSM or PTP clockClass (Continued)
Output Output PTP Output PTP

From Output E1
SyncE
Output Output QL
PQL SSM
SSM G.8265.1 Tele2008/Default
12 0xB 0xB QL-SEC/EEC1 102 52
13 104 58
14 106 248
15 0xF 0xF QL-DNU 108
16 110
Table D-7. PQL Output Mapping for Option II Network - Converted to SSM or PTP clockClass
Output PTP Output PTP

From Output T1 Output SyncE
Output Output QL
PQL SSM SSM
1 04FF 0x1 QL-PRS 80 6
2 08FF 0x0 QL-STU 82
3 04FF 0x1 QL-PRS 84
4 0CFF 0x7 QL-ST2 86 7
5 78FF 0x4 QL-TNC 88
6 90
7 7CFF 0xD QL-ST3E 92 13
8 94
9 96 14
10 98
11 100
12 10FF 0xA QL-ST3 102 52
13 22FF 0xC QL-SMC/EEC2 104 58
14 106

PQL Output Mapping
Table D-7. PQL Output Mapping for Option II Network - Converted to SSM or PTP clockClass (Continued)
Output PTP Output PTP

From Output T1 Output SyncE
Output Output QL
PQL SSM SSM
15 40FF 0xE QL-PROV 108 248
16 30FF 0xF QL-DUS 110
invalid SSM invalid_SSM
Table D-8. PQL Values for Clock States
CLOCK STATE Rb OCXO
Warmup 16 16
Freerun 4 6
Fast 4 6
Normal Freq PQL for Freq PQL for

Selected Ref. Selected Ref.
Bridging Freq PQL for Freq PQL for

Selected Ref. Selected Ref.
Holdover 4 6
Extended Holdover 4 6
Recovery 4 6

This product contains licensed third party software, including software available
under the GPL licensing scheme. You can obtain these licenses and the
open-source software by contacting Microsemi Technical support at the following
numbers:
 Worldwide (Main Number): 1-408-428-7907

 USA, Canada, Latin America including Caribbean, Pacific Rim including Asia,
Australia and New Zealand: 1-408-428-7907
 USA toll-free: 1-888-367-7966 (1-888-FOR-SYMM)
 Europe, Middle East & Africa: 49 700 32886435
An administrative fee may be charged to obtain the source code.
By using the TimeProvider 2300/2700, the user agrees to the terms of these
licenses.
In This Appendix
 Third-Party Software

Third-Party Software
The following is a list of third-party software applications provided with the

 dhcp
 dhcphd
 dhcpv6
 dropbear
 dtc
 elfutils
 ethtool
 expect
 glibc
 iproute2
 iptables
 iputils
 libnss-mdns
 libpam
 libpcap
 libxml2
 linux
 logrotate
 mtd-utils
 net-snmp
 net-tools
 openssh
 openssl
 popt
 sudo
 syslogd
 tcl
 tcpdump
 tftpd-hpa

 u-boot
 wget
 zlib


Appendix F Asymmetry Feature
This appendix provides details about the Asymmetry feature of the TP 2300/2700.
This feature can provide automatic phase compensation for path asymmetry of the
physical line between the 1588v2 client of the TP 2300/2700 and its PTP master.
In This Appendix
 Introduction
 Asymmetry Correction Process
 Asymmetry Metrics

Appendix F Appendix I Asymmetry Feature
Introduction
Introduction
Ethernet ports are usually full-duplex, which means upstream and downstream PTP
packets go through different physical links, such as fibers. The length difference
between the physical fiber lines of the upstream and downstream paths causes a
delay asymmetry. An offset error equal to one-half of the asymmetry value will be
created. For example, the transport delay of optical fiber is 5s per 1km, so a length
difference of 100 meters between the upstream and downstream path will introduce
a 250ns error. However, PTP(1588v2) can't eliminate delay asymmetry of physical
fiber line. When GNSS is available it can be used as a calibrated reference to
determine asymmetry that may be present on an active PTP input which has full
event flow occurring.
If a PTP input becomes selected as the phase reference upon loss of the GNSS
reference, the Asymmetry feature of the TP 2300/2700 can provide automatic
phase compensation for path asymmetry of the physical line between the 1588v2
client and master. If a calibrated path is available, a positive or negative
compensating value is added, making the delay symmetric.
The TP 2300/2700 maintains asymmetry tables associated with the PTP masters
that provide the active flow to its PTP client input port. The clockID of the master is
used as an identifier to match to the correct asymmetry table. The tables can
contain multiple asymmetry signatures for calibrated paths that have been seen for
a particular grandmaster, such as would be likely if the path from the grandmaster to
the client port of the TP 2300/2700 is part of a ring topology.
Note: Manual phase offset value for PTP client port (ETH1) should be
set to zero when the Asymmetry feature is enabled.
Asymmetry Correction Process

There are two major states for the Asymmetry feature:
 No Calibrated Path Available means that TP 2300/2700 is currently not able to

apply PTP-based asymmetry correction. Obvious conditions for this include
asymmetry feature disabled or no PTP flow to TP 2300/2700 client.
 Calibrated Path Available means that TP 2300/2700 is currently able to apply
PTP-based asymmetry correction.
The PTP input and the Asymmetry feature must both be enabled to calibrate
asymmetry paths. GNSS must be available in order to provide the information for
calibration, as shown in Figure F-1.

The PTP input must be the selected reference in order for the Asymmetry feature to
provide corrections to the TP 2300/2700 output. Just because the current PTP input
path is calibrated doesn’t mean that the Asymmetry feature is actually providing
corrections to TP 2300/2700 output.

Figure F-1. Calibrated Path Algorithm for Asymmetry Feature

Table F-1. Description of Calibrated Path Algorithm for Asymmetry Feature
State Step Description
No Calibration Path n/a TP 2300/2700 is currently not able to

Available apply PTP-based asymmetry
correction. Obvious conditions for this
include asymmetry feature disabled or
no PTP flow to TP 2300/2700 client.
Stability Assessment See steps below: Stability Assessment is always the entry
point into No Calibrated Path Available.
While in this substate the asymmetry
algorithm evaluates the PTP path for
suitable phase stability. This evaluation
consists of two components.
In the event of no PTP input flow, the

algorithm remains stuck in the Stability
Assessment substate, clearly not able
to move past the first step since there is
no signal to assess.
PTP Input Observed Long The first part of the stability assesment
Enough to Make Phase is observation of the PTP input long
Stability Determination? enough to make a determination.
Phase Stability Acceptable? If the phase stability of the PTP input is

acceptable, the Signature Detection
substate is entered

Table F-1. (Continued)Description of Calibrated Path Algorithm for Asymmetry Feature (Continued)
Signature Detection See steps below: Signature Detection is the final substate
needed to progress to having a
calibrated path available. The state will
transition to Calibrated Path Available in
the following conditions:
 If a match can be found in an
asymmetry table
 If no match can be found but it is
possible to create a new table entry
Table Entry Found? While in the Signature Detection

substate, the Asymmetry algorithm
looks for a sufficiently matching entry in
the appropriate asymmetry table (based
on the Master Clock ID).
If a match can be found, then the state

directly transitions to Calibrated Path
Available. Note that this transition does
not require that GNSS is currently
available.
The YES path out of Table Entry

Found? can only occur after at least one
calibrated path has been created. which
requires a prior successful exit from
GNSS Available?
GNSS Available? If no match can be found in an

asymmetry table, the algorithm will
transition to this step. This decision
makes it clear that new asymmetry path
entries cannot be created without
GNSS availability, which is used to
provide the calibration reference.
If GNSS is not available then the
algorithm remains here until it does
become available or until the entire
Signature Detection state is exited due
to re-arrangement. If GNSS is never
available for the installation, the
auto-asymmetry correction feature will
not be able to generate any calibrated
paths.

Table F-1. (Continued)Description of Calibrated Path Algorithm for Asymmetry Feature (Continued)
Signature Detection Create New Table Entry This is the process that adds a new
(cont’d) calibrated path into the asymmetry table
that matches the clock ID of the master
that is currently supplying PTP
timestamps to the TP 2300/2700 client.
Calibrated Path n/a This state means that TP 2300/2700 is

Available currently able to apply PTP-based
asymmetry correction.
If GNSS reference is lost, and the PTP

input become the reference driving the
phase/time outputs, the phase
correction from the calibrated path will
be applied.
Significant Change to n/a This is any significant change in PTP

PTP Flow? input flow characteristic, such as
complete loss of flow, change in flow
noise characteristics (significant FPP
change), or change of round-trip time.
This will cause re-arrangement, which
is the condition causing transition from
having a calibrated path to having no
calibrated path.
The way to look at it is that when a

significant change occurs in the PTP
flow it needs to be re-evaluated and
then, if criteria are met, become a
calibrated path.
Typical Application of Asymmetry

When PTP input is the selected reference and is driving phase/time outputs (e.g.
PPS, PTP Master) and the asymmetry feature is enabled, phase adjustments will
occur only if there is a calibrated path available (see Figure F-1). If there is no
calibrated path available, only PTP-based frequency adjustments will be applied
(assuming here that PTP is the selected frequency reference). This behavior
protects phase/time outputs from being impacted by unknown PTP asymmetry,
which is what would occur if phase/time adjustments were applied when there is no
calibrated path available. If the asymmetry feature is disabled, then phase
adjustments would always be applied since asymmetry is not being compensated
anyway. As an example, consider the following scenario:

Asymmetry Metrics
 Initially running with GNSS and PTP, asymmetry feature enabled. GNSS is
driving outputs.
 Assume that a signature is identified for the current PTP path which has an offset
correction (due to asymmetry) of 3 us. This becomes the current calibrated path
available.
 GNSS is lost, so PTP takes over driving of outputs. PPS does not move because
the path is calibrated (the asymmetry adjustment is automatically applied behind
the scenes).
 Now a new PTP signature appears (for example, the path exhibits a significant
change in round trip time), which generates a re-arrangement (see Figure F-1). .
Since GNSS is not available to establish the asymmetry associated with this
path, it cannot be calibrated. The state will remain in GNSS Available? step of the
Signature Detection state. Since this is part of no calibrated path available, there
will be no phase adjustments, only frequency corrections.
 There are two main possibilities from here:
– The originally calibrated PTP path returns. This will cause re-arrangment
and subsequent signature detection resulting in a calibrated path
available. Active phase control resumes.
– GNSS returns, which allows the new PTP signature to become calibrated,
producing a new table entry. From this point forward, this signature can be
identified and used for phase control without GNSS after the calibrated
path is added to the asymmetry table.
Asymmetry Metrics
The “show ptp” CLI command provides asymmetry metrics for the TP 2300/2700,
as shown below. These parameters are explained in Table F-2.
TP2700> show ptp client eth1 asymmetry:
ETH1 PTP client port asymmetry information:
Current path calibration noise (ns) : 345

Current table : 1
Table 1 clock ID : 00-B0-AE-FF-FE-01-D8-86
Table 1 path rearrangements per day : 4
Table 1 total paths : 3

Asymmetry Metrics
Table F-2. PTP Input Asymmetry Metrics
Current path calibration noise (ns) In the case where there is a calibrated path
currently available this value provides an
uncertainty metric for the current path offset
value, which is continually evaluated. The
calibration noise essentially indicates a
1-sigma uncertainty of the offset correction
estimate.
Current table Identifies which clockID table is being

currently used. If there is a current calibrated
path it must be coming from this master.
[ 1 | 2]
Table 1 clock ID Clock ID of master (if any) that is sourcing the

client port of TP 2300/2700.
Table 1 path rearrangements per day Every time a rearrangement process occurs
(see Figure F-1) this counter increments. The
reported result is the count for the past 24
hours.
Table 1 total paths This is the number of paths that are currently
entered into the table.
Table 2 clock ID Clock ID of second master that is sourcing the

client port of TP 2300/2700 which is used for
Table 2 calibrated paths.
Table 2 path rearrangements per day Every time a rearrangement process occurs
(see Figure F-1) this counter increments. The
reported result is the count for the past 24
hours.
Table 2 total paths This is the number of paths that are currently
entered into Table 2.

Asymmetry Metrics
Example response with no PTP full flow yet:
Current path calibration noise (ns) : na

Current table : 1
Table 1 clock ID : 00-00-00-00-00-00-00-00
Table 2 clock ID : 00-00-00-00-00-00-00-00
Example response with full PTP flow, but asymmetry disabled:
Current path calibration noise (ns) : na

Current table : 1
Table 2 clock ID : 00-00-00-00-00-00-00-00
The only difference between these examples is that clock ID will appear if there is
PTP flow. This also shows that only one clock ID has ever been seen.

Appendix G Glossary
Table G-1. Glossary of Terms
Term Description
1588 IEEE-1588 is a precision clock synchronization protocol for networked

measurement and control systems.
AIS Alarm Indication Signal – An in-band, unframed, “all ones” signal. AIS
is used to indicate that the sending device is experiencing problems
that may degrade its output.
ANSI American National Standards Institute
ARP Address Resolution Protocol
B8ZS Binary with 8 Zero Substitution – The zero suppression scheme

associated with DS1.
BEIDOU BeiDou Navigation Satellite System - China’s satellite-based

augmentation system
BITS Building Integrated Timing Supply
BMCA Best Master Clock Algorithm
Bonding The ability of Ethernet ports to share IP addresses, either by having a

single Ethernet port active at a single time or multiple ports operating
at the same time (load sharing).
Boundary Clock A boundary clock is a clock with more than a single PTP port, with
each PTP port providing access to a separate PTP communication
path. Boundary clocks are used to eliminate fluctuations produced by
routers and similar network elements.
BPV Bipolar Violation – An error caused when a port receives two

consecutive pulses of the same polarity, violating the alternate mark
inversion format for framed signals.
BPV-ES BPV Errored Seconds –Testing for BPVs can be performed over a
significant period of time (hours, days, weeks). The BPV-ES is a
measurement of how many seconds during the test period had a BPV
associated with them.
BPV-SES BPV Severely Errored Seconds – BPV-SES is similar to BPV-ES with

an additional test of the magnitude of the BPV rate, if the BPV rate
(per second) is greater than 1E-3, then that “second” would be
considered to be in “severe error.”
BSC Base Station Controller
BTS Base Transceiver Station
CAR Corrective Action Request

Appendix G Appendix I Glossary
Term Description
Carrier Class A system classification that indicates superior performance and

“hitless” failover redundancy for the major functional areas of the
system.
CBRS CDMA Backhaul and Routing System
CDMA Code Division Multiple Access
Cesium oscillator An oscillator that adheres to the cesium standards generating highly
reliable Stratum 1 synchronization signals to telecom network
services.
CLEI Common Language Equipment Identification
CLI Command Line Interface – A user interface that is typically for

human-to-machine interface.
Clock A device providing a measurement of the passage of time since a

defined epoch. There are two types of clocks in 1588: boundary
clocks and ordinary clocks.
Clock Timestamp Point 1588 requires the generation of a timestamp on transmission or

receipt of all 1588 Sync and Delay_Req messages. The point in the
outbound and inbound protocol stacks where this timestamp is
generated is called the clock timestamp point.
CM Cable Modem
CMTS Cable Modem Termination System
CO Central Office
Composite Clock (CC) Composite clock is a framed telecom signal that uses 8KHz framing
with a 64KHz signal rate.
Controller SPI interface controller, typically either a clock or communications

card
CORE Configuration Resource
CPC Common Product Code
CPT Coherent Population Trapping
CPU Watchdog The CPU watchdog will reset the CPU if its timeout expires.
CRC Clock Redundancy Check
CRC6 A cyclic redundancy checking protocol used with DS1 signaling.
CTS Clear to send
CUC Command Use Case – A definition of a system command.
Current Configuration The card’s current provisioned settings are stored in FLASH on the
card and all controllers (Communications & Clock cards).

Term Description
D4/ESF The framing modes associated with DS1 signaling. D4 uses

super-frame for information transfer, while ESF uses extended
super-frame.
DAC Digital-to-Analog Converter
Daemon Daemon is an agent program that operates on a UNIX server and

continually provides resources to client systems on the network.
Daemon is a background process used for handling low-level
processes.
DHCP Dynamic Host Configuration Protocol
DiffServ Codepoint Differentiated Services (DiffServ) – The Diffserv codepoint is defined

in the first six bits in TOS byte; the TOS byte is used to define how a
specific packet (type of packet) is transported through a network. The
mechanism provides a simple method of traffic differentiation.
Direct communication The communication of PTP information between two PTP clocks with
no intervening boundary clock is termed a direct communication.
DLL Delay Locked Loop
DMPI DOCSIS MAC PHY Interface
DNU Do not use
DOP Dilution of Precision
DSCP Differentiated Services Code Point - Networking architecture that

specifies a mechanism for classifying, managing network traffic, and
providing Quality of Service (QoS) on modern IP networks.
DUT Device under test
E1 European Basic Multiplex Rate (30 voice channels; 2.048 Mbps)
EDI Electronic Data Interchange
EEC Ethernet Equipment Clock (synchronous)
EGNOS European Geostationary Navigation Overlay System - Europe’s

satellite-based augmentation system
EMI Electromagnetic Interference
EMS Element Management System
Epoch The reference time defining the origin of a time scale.
ERMI Edge Resource Manager Interface
ESMC Ethernet Synchronization Message Channel

Term Description
ETSI European Telecommunications Standard – defines environmental and

operational standards for network elements, similar to NEBS in North
America.
External Synchronization It is often desirable to synchronize a single clock to an external source

of time. For example, using a GPS system to establish a UTC time
base. This synchronization is accomplished by means other than
those specified by IEEE 1588 and is referred to as external
synchronization.
Factory Configuration The factory default settings for this card, which are defined by the
card’s executable software.
FCAPS Fault, Configuration, Accounting, Performance, Security
FDMA Frequency Division Multiple Access
FE Fast Ethernet/Framing Error
FMEA Failure Mode Effects Analysis
FPGA Field Programmable Gate Array
Fraction Frequency Offset The difference in frequency between two signals of the same
fundamental frequency. dF = (F2 – F1) / F1
FTP File Transfer Protocol
GA General Availability
GAGAN GPS-Aided Geo-Augmented Navigation - India’s satellite-based

augmentation system
GM GrandMaster - refers to a PTP grandmaster
GNSS Global Navigation Satellite System
GigE Gigabit Ethernet
GLONASS Global'naya Navigatsionnaya Sputnikovaya Sistema is a global

satellite navigation system operated by the Russian Ministry of
Defence.
GPS Global Positioning System, American GNSS, used as a source of time

and frequency
GPSTM Global Positioning System Timing card
Grandmaster Clock Within a collection of 1588 clocks, one clock– the grandmaster clock–
will serve as the primary source of time to which all others are
ultimately synchronized.

Term Description
Hardware Timestamper An implementation that allows accurate timestamping or time

association of TCP/UDP packets. The implementation requires that
the timestamping be performed as close to the physical media as
possible, for example, MAC/PHY interface.
HDB3 High Density Bipolar of order 3, used with E1 lines. Similar to B8ZS
for T1. It’s basically a form of run-length limited coding that prevents
endless sequences of all zeros or ones, which can have adverse
effects on clock-recovery loops downstream.
HSR Hardware Status Register
ICMP Internet Control Message Protocol
IEEE Institute of Electrical and Electronic Engineers
IEEE-1588 Standard for a Precision Clock Synchronization Protocol (PCSP) for

Networked Measurement and Control Systems, aka Precision Time
Protocol (PTP)
IMC Information Management Controller – A card that is part of the

architecture responsible for system management.
Input The input for a port.
IOC Input/Output Controller – A card that is part of the TP-5000

architecture that is responsible for input/output management and
frequency/timing control servo.
IP Internal Protocol
IP-E A standard for the transmission of IP datagrams over Ethernet

networks.
IP-DSLAM Internal Protocol – Digital Subscriber Line Access Multiplexer
IPTV Internet Protocol Television
IPv4 Internet Protocol version 4 – 32-bit layer 3 IP addressing
IPv6 Internet Protocol version 6 – 128-bit layer 3 IP addressing, IPSec,

Auto renumbering, etc.
ITU-T International Telecommunication Union – Standards body that defines

telecom standards for the international telecom community.
L1 Frequency used by civilian GPS receivers, which is 1575.42 MHz

(wavelength 19.05 cm). The L1 frequency carries the navigation data
as well as the SPS code (standard positioning code).
LA Limited Availability
LIU Line Interface Unit

Term Description
Load Sharing 802.3AD describes a method to allow multiple Ethernet ports on a

single device to distribute inbound or outbound traffic over the
available ports – for example, to share the load over multiple ports.
LOS Loss of Signal – An indication that a port has stopped receiving an

inbound signal.
LPF Low Pass Filter
LRU Line Retiming Unit – The combination of LRM and cut-thru assembly.
LTIB Linux Target Image Builder
LVDS Low-Voltage Differential Signal
MAAS Multi-functional Satellite Augmentation System - Japan’s

satellite-based augmentation system
MAC Media Access Control – Provides a method of access control

(addressing) at the Data Link Layer of the OSI network model.
MAC Miniature Atomic Clock
Master clock A system of IEEE-1588 clocks may be segmented into regions

separated by boundary clocks. Within each region there will be a
single clock, the master clock, serving as the primary source of time.
These master clocks will in turn synchronize to other master clocks
and ultimately to the Grandmaster clock.
MD5 Message Digest – A common hashing algorithm historically used by

many UDP or TCP protocols. This hash has been compromised, and
there are stronger methods of encryption, but MD5 continues to be
used for NTP authentication.
Message Timestamp Point IEEE 1588 Sync and Delay_Req messages contain a distinguished
feature, which is the message timestamp point. This message
timestamp point serves as a reference point in these messages.
When the message timestamp point passes the clock timestamp
point, a timestamp is generated, which is used by IEEE 1588 to
compute the necessary corrections to the local clock.
MLLRS Maximal-Length Linear Recursive Sequence
MSAN Multi Service Access Nodes
MSO Mixed Signal Oscilloscope
MTIE Maximum Time Interval Error – An input performance measurement.
Multicast Communication IEEE 1588 requires that PTP messages be communicated via a
multicast configuration. In this style of communication, any node may
post a message and all nodes in the same segment of a subdomain
will receive this message. Boundary clocks define the segments
within a subdomain.

Term Description
NE Network Element - a manageable logical entity (facility or equipment)

uniting one or more physical devices used in the provisioning of a
telecommunications service.
NEBS Network Equipment-Building System – Defines environmental and

operational requirements for network elements that are similar to
ETSI in international markets. Relies on Telcordia General
Requirements for performance profiles.
NEM Network Equipment Manufacturer
NGN Next Generation Networks – Networks for integrated data, voice, and
video services, typically transported over TCP/IP.
NMEA National Marine Electronics Association
NPI New Product Introduction
NTP Network Time Protocol – This protocol is specified by RFC-5905 with

reference to RFC-2030.
OAM&P Operation, Administration, Maintenance and Provisioning
OCXO Oscillator The OCXO oscillator is consistent with the telecommunications class
of oscillators known as Stratum 3E.
OOF Out of Frame – Indication that the input card hardware cannot
decipher the framing of an incoming signal.
Ordinary Clock An ordinary clock is an IEEE1588 clock with a single PTP port.
OSR Operations Status Register
OSSP Organizational Specific Slow Protocol
oTCXO Oscillator A high-stability oscillator that uses a combination of a miniature oven

and temperature compensation.
OTH Optical Transport Hierarchy
OTN Optical Transport Network
OUI Organizational Unique Identifier
PCB Printed Circuit Board - The circuit board itself, independent of whether
it has components.
PCBA Printed Circuit Board Assembly - The circuit board with components.
PDH Plesiochronous Digital Hierarchy (PDH) – A technology used in

telecommunications networks to transport large quantities of data
over digital transport equipment such as fiber optic and microwave
radio systems. PDH is now being replaced by Synchronous Digital
Hierarchy (SDH) equipment in most telecommunications networks.
PDU Protocol Data Unit

Term Description
PDV Packet Delay Variation
PEC Product Engineering Code
PHY Physical Layer - PHYsical (layer)
PID Packet ID
PLD Programmable Logic Device
PLL Phase Locked Loop
Port One input or output signal connection
POC Proof-of-Concept
PPB Parts per Billion
PPS Pulse per Second
PPP point-to-point protocol
PQL Priority Quality Level – An internal representation of traceability of

signal presented at the input ports.
Preferred Master Clock Set IEEE 1588 allows a definition of a set of clocks that will be favored
over other clocks and are designated in the selection of the
Grandmaster clock.
Primary card Primary card means the master card. The master card is in charge of
coordinating the synchronization of the master and the slave cards in
redundant mode.
PRC Primary Reference Clock
PRS Primary Reference Source
PTP Precision Time Protocol
PTP Domain A PTP domain is a collection of one or more PTP subdomains. A

subdomain is a logical grouping of IEEE 1588 clocks that synchronize
to each other using the PTP protocol but that are not necessarily
synchronized to PTP clocks in another PTP subdomain. Subdomains
provide a way of implementing disjointed sets of clocks that share a
common network but maintain independent synchronization within
each set.
PTP Message There are five designated messages types defined by IEEE 1588:
Sync, Delay_Req, Follow-up, Delay_Resp, and Management.
PTP Port A PTP port is the logical access point for IEEE 1588 communications
to the clock containing the port.
PWA Printed Wire Assembly - The circuit board itself, independent of

whether it has components.

Term Description
QL Quality Level
QoS Quality of Service
Quartz oscillator An oscillator which meets or exceeds the performance requirements

for ITU and ETSI Type 1 Slave clocks.
RADIUS Remote Authentication Dial-In User Service, RFC 2865
Redundant card The operating mode, in which two output cards are connected by the
summing adapter. That way, the output signal remains the same even
if one of the two output cards fails.
RAIM Receiver Autonomous Integrity Monitoring
RDB Reference Design Board
RF Radio Frequency
RIP Routing Information Protocol
RNC Radio Network Controller – The controller of a cell base station

topology.
ROM Rough Order of Magnitude
PRC Remote Procedure-call Protocol
RPS Requests per Second (NTP requests)
Rubidium oscillator An oscillator that meets or exceeds the performance requirements for
ITU and ETSI Type I Transit and Type II Local Node clocks and ANSI
and Telcordia Technologies (Bellcore) Stratum 2 clocks.
SBAS Satellite-Based Augmentation Systems are designed to dramatically

improve GPS performance. Countries use different naming
conventions such as Europe’s (EGNOS), Japan’s (MSAS), India’s
(GAGAN), China’s (BEIDOU), and USA’s (WAAS). are designed to
dramatically improve GPS performance.
SCPI Standard Commands for Programmable Instruments
SDH Synchronous Digital Hierarchy – Synchronous optical networking

(SONET) and Synchronous Digital Hierarchy (SDH) are two closely
related multiplexing protocols for transferring multiple digital bit
streams over the same optical fiber using lasers or light-emitting
diodes (LEDs).
SDU Synchronization Distribution Unit
Secondary card With redundant output cards, the secondary card will cooperate with
the master card in the synchronization process.
SFP Small Form-factor Pluggable – A type of standardized Ethernet

interface.

Term Description
SNMP Simple Network Management Protocol
SONET Synchronous Optical Network
SP Standard Precision
SPI Serial Peripheral Interface – A Motorola serial communications

protocol used for inter-card communications.
SSM Synchronization Status Messages – A means by which elements in a

synchronization network can communicate the traceability of their
sync quality level.
SSU Synchronization Supply Unit
Synchronized Clock Two clocks are synchronized to a specified uncertainty if they have
the same epoch and measurements of any time interval by both
clocks and differ by no more than the specified uncertainty. The
timestamps generated by two synchronized clocks for the same event
will differ by no more than the specified uncertainty.
TCP Transmission Control Protocol
T1 T1 is a T-carrier signaling scheme devised by Bell Labs – also known

as DS1 or DS-1 (Digital Signal 1).
TAI International Atomic Time (Temps Atomique International), which is

the results from the averaging and coordination of several hundred of
the best atomic clocks around the world.
TAU Time constant used to characterize the frequency response of various

signal processing systems. Tau is expressed in seconds and
determines the PLL time constant for following a step in phase for the
reference.
TCP Transport Control Protocol – Internet Protocol that guarantees reliable

delivery of a datagram.
TDEV Time Deviation (akin to Allen Variance) – input performance

measurement
TDM Time Division Multiplexer
TDMA Time Division Multiple Access
Telcordia Previously known as Belcore – an organization that is responsible for

defining requirements for the US and other networks.
TFTP Trivial File Transfer Protocol
TL-1, TL1 Transaction Language 1 – A Telcordia command-line interface (digital

transmission line, 1.544 Mbps, 24 voice channels).
TLV Type-Length-Value – A method of optionally extending the contents of

a datagram or protocol.

Term Description
TOD Time of Day (wall clock): the default timescale shall be UTC.
TPS Transactions per Second
TRAIM Timing Receiver Autonomous Integrity Monitoring
TTFF Time to First Fix – the time and process required for a GNSS device to
acquire enough usable satellite signals and data to provide accurate
navigation.
TTL Transistor-Transistor Logic
UART Universal Asynchronous Receiver Transmitter
UC Use case - defines how a system behaves and functions
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications System
User Configuration The card’s user-provisioned settings. These settings are stored in
FLASH via a user command and are stored on the card and all
controllers (Comm & Clock cards). The card’s provisioned settings
can be retrieved via a user command.
USC User Selected Channel
UTC Coordinated Universal Time is TAI with leaps seconds added at

various times. As of 2006, UTC is 33 seconds behind TAI.
UTC (SU) UTC timescale in GLONASS constellation mode
VCSEL Vertical Cavity Surface Emitting Lasers
VCXO Voltage-Controlled Crystal Oscillator
VDSL/VHDSL Very-high Data-digital Subscriber Line
VLAN Virtual Local Area Network – A method used to create independent

logical network(s) within a physical network(s). A group of host
machines that share a common network identification (NIC) that allow
the host machines to operate as if they exist on the same physical
network.
VoIP Voice-over Internet Protocol
VSWR Voltage Standing Wave Ratio
WAAS Wide Area Augmentation System - USA’s satellite-based

augmentation system
WiMAX Worldwide Interoperability for Microwave Access


TimeProvider 2700

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TimeProvider 2700

Hochgeladen von

Copyright:

Verfügbare Formate

..................

User’s Guide updates are available at: www.microsemi.com/ftdsupport

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 3

Unpacking the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Chapter 3 CLI Commands

set hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 5

6 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

Provisioning the Non-PTP Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Chapter 5 Maintenance, Troubleshooting & Part Numbers

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 7

Appendix A System Messages

Appendix B Specifications and Factory Defaults

8 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337

Appendix C Installing GNSS Antennas

Appendix D PQL Mapping

Appendix E Software Licenses

Appendix F Asymmetry Feature

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 9

Asymmetry Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380

10 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 11

4-3 Set Vlan-Mode Command Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

12 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

B-7 TimeProvider 2300/2700 DS1 Input Signal Specifications. . . . . . . . . . . . .322

14 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

C-2 LMR-400 Antenna Coaxial Cable Accessories . . . . . . . . . . . . . . . . . . . . .360

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 15

16 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 17

Purpose of This Guide

Who Should Read This Guide

Chapter 1, Overview, is written for non-technical audiences who need general

This User’s Guide is designed for the following categories of users:

 Systems Engineers – Chapter 1 provides an introduction to the TimeProvider

Structure of This Guide

This guide contains the following sections and appendixes:

Chapter, Title Description

Chapter 1, Overview Provides an overview of the product, describes the major

18 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

Chapter, Title Description

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 19

Conventions Used in This Guide

This guide uses the following conventions:

When text appears

TimeProvider 2300/2700 The title of a document.

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

Press Enter A named keyboard key.

Username: Text in a source file or a system prompt or other text that

ping A command you enter at a system prompt or text you

qualified personnel A word or term being emphasized.

Microsemi does not A word or term given special emphasis.

20 TimeProvider 2300/2700 User’s Guide 098-00564-000 Revision B – June, 2014

Warnings, Cautions, Recommendations, and Notes

Warnings, Cautions, Recommendations, and Notes attract attention to essential or

Warning: To avoid serious personal injury or death, do not disregard

Caution: To avoid personal injury, do not disregard cautions. All

ESD Caution: To avoid personal injury and electrostatic discharge

Electrical Shock Caution: To avoid electrical shock and possible

Recommendation: All recommendations use this symbol.

098-00564-000 Revision B – June, 2014 TimeProvider 2300/2700 User’s Guide 21

Where to Find Answers to Product and Document

Manual updates are available at: