Synchronization Um

USER MANUAL
FOX61x
TDM and Packet Based Synchronization
PDH, SDH and Packet based Synchroniza-
tion Applications
TDM and Packet Based Synchronization User Manual
Document ID 1KHW029105
Document edition FOX61x System Release: R15B

Revision: A
Date: 2022-01-31
Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine
scannable form is not permitted, either in whole or in part. The contents of the
manual may not be disclosed by the recipient to any third party, without the prior
written agreement of Hitachi Energy.
An exception is the preparation of a backup copy of the software for your own use.
For devices with embedded software, the end-user license agreement on the
enclosed CD applies.
This document may not be used for any purposes except those specifically
authorized by contract or otherwise in writing by Hitachi Energy.
Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Energy company.
Hitachi Energy Switzerland Ltd (hereinafter referred to as Hitachi Energy) has taken
reasonable care in compiling this document, however Hitachi Energy accepts no
liability whatsoever for any error or omission in the information contained herein and
gives no other warranty or undertaking as to its accuracy.
Hitachi Energy can accept no responsibility for damages, resulting from the use of
the network components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
Hitachi Energy reserves the right to amend this document at any time without prior
notice.
The product/software/firmware or the resulting overall solution are designed for data
processing and data transmission and may therefore be connected to communication
networks. It is your sole responsibility to provide and continuously ensure a secure
connection between the product/software/firmware or the resulting overall solution
and your network or any other networks (as the case may be). You shall establish
and maintain any appropriate measures (such as but not limited to the installation of
firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc.) to protect the product/software/firmware or the resulting
overall solution, the network, its system and all the interfaces against any kind of
security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. Hitachi Energy and its affiliates are not liable for damages and/
or losses related to such security breaches, any unauthorized access, interference,
intrusion, leakage and/or theft of data or information.
Although Hitachi Energy provides functionality testing on the products including
related firmware and software that we release, you should institute your own testing
program for any product updates or other major system updates (to include but not
limited to firmware/software changes, configuration file changes, third party software
updates or patches, hardware exchanges, etc.) to ensure that the security measures
that you have implemented have not been compromised and system functionality in
your environment is as expected.
Copyright 2022 Hitachi Energy. All rights reserved. 2

FOX61x | SYNCHRONIZATION
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 FOX61x Core and Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Functions and Specification Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Synchronization Related Standards Documents . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Synchronization Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1 Network Reference Timing Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.1 Master - Slave Timing Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.2 Distributed PRC Timing Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.3 Mixed PRC Timing Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1.4 Timing Source Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Synchronization Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.1 Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2.2 Logical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2.3 PTP Packet Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.4 Circuit Emulation Service Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3 Timing Source Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.3.1 Priority Based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3.2 Quality Level Based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4 Commissioning of a Synchronization Network . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4.1 Synchronization Network Planning Principles . . . . . . . . . . . . . . . . . . . . . 24
4.4.2 Planning Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.4.3 Specific Applications in Synchronization Networks . . . . . . . . . . . . . . . . . . . 30
5 FOX61x Synchronization Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2 SETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2.1 Timing Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.2.2 Timing Source Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2.3 SETS Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.4 SETS Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.5 SETS Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.3 PETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.3.1 Timing Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.3.2 Timing Source Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.3 PETS Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.3.4 PETS Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.3.5 PETS Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.4 SETS and PETS Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.5 External Synchronization Inputs ESI-1 and ESI-2 . . . . . . . . . . . . . . . . . . . . . . . . 52
5.5.1 ESI-1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.5.2 ESI-2 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.5.3 ESI-1 and ESI-2 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.6 External Synchronization Output ESO-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.6.1 ESO-1 Timing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.6.2 ESO-1 Timing Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.6.3 ESO-1 Timing Source Selection PETS-Locked Mode . . . . . . . . . . . . . . . . . 54
5.6.4 ESO-1 Timing Source Selection Non PETS-Locked Mode . . . . . . . . . . . . . . . 55

5.6.5 ESO-1 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.6.6 ESO-1 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.7 External Synchronization Output ESO-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.7.1 ESO-2 Timing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.7.2 ESO-2 Timing Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.7.3 ESO-2 Timing Source Selection SETS-Locked Mode . . . . . . . . . . . . . . . . . 57
5.7.4 ESO-2 Timing Source Selection Non SETS-Locked Mode . . . . . . . . . . . . . . . 58
5.7.5 Manual Timing Source Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.7.6 ESO-2 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.7.7 ESO-2 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.7.8 ESO-2 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.8 Quality Level Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.8.1 Quality Level Handling in FOX61x . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.8.2 Quality Level Transport in FOX61x . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.8.3 Quality Level Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.8.4 PETS Quality Level Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.8.5 SETS Quality Level Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.9 Service Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.9.1 Synchronous Ethernet Service Timing . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.9.2 Synchronous PDH Service Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.9.3 Plesiochronous PDH Service Timing . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.1 General Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2 SDH Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2.2 SETS Synchronization via SDH Traffic Signals. . . . . . . . . . . . . . . . . . . . . 76
6.2.3 SETS Synchronization via Synchronous Ethernet Signals . . . . . . . . . . . . . . . 79
6.2.4 SETS Synchronization via the Local Oscillator . . . . . . . . . . . . . . . . . . . . . 81
6.3 PDH Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.3.2 PETS Synchronization via PDH Traffic Signals. . . . . . . . . . . . . . . . . . . . . 83
6.3.3 PETS Synchronization via PTP and SyncE, Port Based (Pure Hybrid) . . . . . . . . 87
6.3.4 PETS Synchronization via PTP, Port Based . . . . . . . . . . . . . . . . . . . . . . 91
6.3.5 PETS Synchronization via PTP, Ethernet VLAN Based . . . . . . . . . . . . . . . . 94
6.3.6 PETS Synchronization via PTP, IP VLAN Based . . . . . . . . . . . . . . . . . . . . 98
6.3.7 Plesiochronous Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.4 ESO Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.4.1 ESO-1 Synchronization, PETS Locked . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.4.2 ESO-1 Synchronization, non PETS Locked . . . . . . . . . . . . . . . . . . . . . . 104
6.4.3 ESO-2 Synchronization, SETS Locked . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.4.4 ESO-2 Synchronization, non SETS Locked . . . . . . . . . . . . . . . . . . . . . . 107
6.5 SDH/PDH Synchronization Setup in a Tree Network . . . . . . . . . . . . . . . . . . . . . . . 111
6.5.1 One External Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6.6 SDH/PDH Synchronization Setup in a Ring Network . . . . . . . . . . . . . . . . . . . . . . . 116
6.6.1 One External Timing Source, Without SSU. . . . . . . . . . . . . . . . . . . . . . . 117
6.6.2 Two External Timing Sources, Without SSU . . . . . . . . . . . . . . . . . . . . . . 121
6.6.3 One External Timing Source, With SSU . . . . . . . . . . . . . . . . . . . . . . . . 125
6.7 PTP Synchronization Setup in a Ring Network . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.7.1 PTP Port Based. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.7.2 PTP Ethernet VLAN Based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.7.3 PTP IP VLAN Based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
6.7.4 PTP IP VLAN Based, two Rings, two External Timing Sources . . . . . . . . . . . . 136
6.7.5 PTP Port and Ethernet VLAN Based, two Rings, two External Timing Sources . . . . 140
7 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.1 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.1.1 SETS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.1.2 PETS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7.1.3 Ethernet Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7.1.4 PTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7.1.5 PTP Port Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7.1.6 PTP Stream Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7.1.7 ESO Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7.1.8 QL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7.2 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3.1 SETS Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3.2 ESO-2 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3.3 PTP Stream Performance Management . . . . . . . . . . . . . . . . . . . . . . . . 146
8 User Interface Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
8.1 MOM for the Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
8.1.1 MOM for the FOXCST Synchronization View. . . . . . . . . . . . . . . . . . . . . . 147
8.1.2 MOM for the PDH Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.1.3 MOM for the SDH Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8.2 AP: / Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8.3 AP: / Synchronization / SyncE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8.3.1 AP: / Synchronization / SyncE, Ports . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8.4 AP: / Synchronization / PTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.4.1 AP: / Synchronization / PTP, Ports & Streams . . . . . . . . . . . . . . . . . . . . . 167
8.4.2 AP: / Synchronization / PTP, Configuration. . . . . . . . . . . . . . . . . . . . . . . 194
8.4.3 AP: / Synchronization / PTP, ETR . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
8.4.4 AP: / Synchronization / PTP, LSP Configuration . . . . . . . . . . . . . . . . . . . . 197
8.4.5 AP: / Synchronization / PTP, Status . . . . . . . . . . . . . . . . . . . . . . . . . . 198
8.4.6 AP: / Synchronization / PTP, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.4.7 AP: / Synchronization / PTP, Alarm Status and Alarm Configuration. . . . . . . . . . 200
8.5 AP: / Synchronization / PETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
8.5.1 AP: / Synchronization / PETS, Configuration . . . . . . . . . . . . . . . . . . . . . . 201
8.5.2 AP: / Synchronization / PETS, Status. . . . . . . . . . . . . . . . . . . . . . . . . . 204
8.5.3 AP: / Synchronization / PETS, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 206
8.5.4 AP: / Synchronization / PETS, Alarm Status and Alarm Configuration . . . . . . . . . 206
8.6 AP: / Synchronization / ESO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
8.6.1 AP: / Synchronization / ESO, Configuration . . . . . . . . . . . . . . . . . . . . . . 207
8.6.2 AP: / Synchronization / ESO, Status . . . . . . . . . . . . . . . . . . . . . . . . . . 210
8.6.3 AP: / Synchronization / ESO, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 212
8.6.4 AP: / Synchronization / ESO, Alarm Status and Alarm Configuration . . . . . . . . . 212
8.7 AP: / ne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
8.7.1 AP: / ne, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
8.8 AP: / unit-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.8.1 AP: / unit-11 / neController / esi-z. . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.8.2 AP: / unit-11 / sync / esi-z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.9 AP: / unit-x (SDH Service Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
9 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
9.1 Associated FOX61x Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

FOX61x | SYNCHRONIZATION PREFACE
1 Preface
1.1 Precautions and Safety

Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety requirements as
defined in IEC 62368-1 (Safety of audio/video, information and communication technology
equipment).
Please refer to the following document:
[1KHW002497] Operating Instruction “Precautions and safety”.
1.2 Symbols and Notations

This User Manual uses the following symbols:
Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
→ Possible actions are given.
Please note:
Shows significant information.
→ Possible actions are given.
1.3 Document History

Table 1: Document history
Document ID FOX61x Rev. Date Changes since previous version
release
1KHW029105 R15B A January 2022 - Updated for current system release.
1KHW029105 R15A C June 2021 - ETR: Support of the PPS output.
- PTP transport: Support of UDP/IPv4 in addition to
Ethernet (L2).
- Hierarchical PTP networks with “PTP Master” mode
on IP VLANs.
- Update copyright statement.
1KHW029105 R14A B June 2020 - Support of “PTP Ordinary/Boundary and Transparent
Clock” mode on the CESM1 unit with PTP VLAN
based synchronization.
- Display of the PTP VLAN source MAC address.
- New PTP timestamping performance management
counters for PTP ports.
- PTP configuration parameters Clock Mode, PTP Mode
and PTP Awareness modified. PTP Grand Master
mode is no longer available.
- Maximum number of “Announce” messages is
reduced to 8 per second.
1KHW029105 R3B_SP01 A December 2019 - First revision of the document for the FOX61x system
release R3B_SP01.

FOX61x | SYNCHRONIZATION PREFACE
1.4 Target Audience

This User Manual is targeted at persons who are entrusted with the installation, provisioning,
operation and administration of the system.
The persons targeted are
• the installation personnel, and/or
• the provisioning personnel, and/or
• the operation and administration personnel
Please note:
Only instructed or skilled persons as per IEC 62368-1 may install and maintain the
system.
1.5 Definition of Terms

Table 2: Specific terms
Term Explanation
CESM1 Designates the core and control unit CESM1 or CESM1-F of FOX61x.
CESM2 Designates the core and control unit CESM2 or CESM2-F of FOX61x.
Core Unit Designates the core and control unit CESM1, CESM1-F, CESM2, CESM2-F or
CESM3 of FOX61x.
Where certain features or characteristics apply to a specific core unit only, the
CESM1, CESM1-F, CESM2, CESM2-F or CESM3 is named explicitly.
SAMO5 Designates the STM-4 SDH transport unit SAMO5 or SAMO5-F for TDM and Ether-
net traffic of FOX61x
SAMO2 Designates the STM-16 SDH transport unit SAMO2 or SAMO2-F for TDM and Ether-
net traffic of FOX61x
SAMOx In this User Manual, the term SAMOx is used to name the SAMO5, SAMO5-F,
SAMO2, SAMO2-F or SAMO3.
Where certain features or characteristics apply to a specific unit only, this unit is
named explicitly.
SAMO1 is excluded.
WAN port exten- Designates the WAN port extension unit EPEX1. Up to two EPEX1 units can be
sion unit operated in a FOX615 R2 subrack together with a CESM3 core unit.

FOX61x | SYNCHRONIZATION INTRODUCTION
2 Introduction
2.1 General
PDH and SDH traffic signals transported through a TDM network require all network elements
terminating a traffic signal to be frequency synchronized to one common timing source. A
synchronization network is used to distribute the timing information from a timing master to all
network elements. Each network element has to be equipped with the corresponding synchroni-
zation functions:
• Select the highest quality incoming synchronization signal.
• Synchronize the local equipment timing source to the selected synchronization signal.
• Forward the synchronization information to some or all neighbored network elements.
The FOX61x provides the SETS (Synchronous Equipment Timing Source) and the PETS (Ple-
siochronous Equipment Timing Source) functions for the network element and traffic signal syn-
chronization.
The FOX61x operating as PDH network element uses the PETS function for the network ele-
ment and traffic signal frequency synchronization. The PETS is located on the core unit. Two
redundant core units automatically provide equipment protection for the PETS function.
The PETS can be synchronized to any of the following PDH clock sources:
• External synchronization input (ESI, 2048 kHz),
• E1 port,
• SHDSL trunk port,
• SHDSL payload signal,
• CES (Circuit Emulation Service) Pseudo Wire,
• SDH tributary signal (P12),
• SETS function on a SDH service unit.
For the synchronization support of applications which are connected via an Ethernet traffic sig-
nal the PETS can be frequency synchronized to Synchronous Ethernet (SyncE). As a conse-
quence the PETS operates as an EEC (Ethernet Equipment Clock), providing the same clock
quality as a SEC (SDH (or Synchronous) Equipment Clock).
In addition the PETS supports the frequency, phase and time (of day) synchronization using the
Precision Time Protocol (PTP). PTP packets can be transported on the Ethernet layer, Ethernet
VLAN layer, or in MPLS VLANs. As a consequence the PETS operates as a PEC (Packet-
based Equipment Clock), providing the same clock quality as a SEC (SDH (or Synchronous)
Equipment Clock).
Please note:
In the current release the Ethernet ports supporting SyncE and PTP are located on
the core unit as well as on the WAN port extension unit EPEX1.
All five ports on EPEX1 support SyncE while activation of SyncE is possible on just
two of them at a time.
The PETS provides also an external synchronization output (ESO, 2048 kHz) which can be
used to synchronize other equipment. Two redundant core units automatically provide equip-
ment protection for the ESO function.

Core Unit, protecting

Network Element
Core Unit, working PETS Timing
PTP from Eth/WAN port Network Element
PTP from VLAN PETS Timing
Synchronization output
SyncE from Eth/WAN port
Synchronization input Synchronization output
PDH or SDH
E1 port
SHDSL trunk port
Service Unit
SHDSL payload PETS
CES Pseudo Wire clock
SETS function source
SDH tributary
Figure 1: PETS function in the FOX61x
An FOX61x SDH service unit operating as SDH network element uses the SETS function for the
traffic signal frequency synchronization. A SETS is located on each SDH service unit. Two
redundant SAMOx units automatically provide equipment protection for the SETS function.
The SETS can be synchronized to any of the following clock sources:
• External synchronization input (ESI, 2048 kHz),
• STM-1, STM-4, STM-16 port,
• any of the PETS clock sources,
• SyncE from a core unit port.
The SETS provides also an external synchronization output (ESO, 2048 kHz) which can be
used to synchronize other equipment. Two redundant SAMOx units automatically provide equip-
ment protection for the ESO function. The core unit selects one of the available SDH service
units to drive the ESO output.
Please note:
The SAMO1 unit does not provide equipment protection for the SETS and ESO
function.

Core Unit, protecting

Synchronization output
Core Unit, working
Synchronization input Synchronization output
SyncE from Eth port
E1 port
PDH or SDH
SHDSL trunk port Service Unit
SHDSL payload PETS
CES Pseudo Wire clock
SETS function source
SDH tributary
SDH Service Unit, prot.

SDH Service
SETSUnit, working
SETS
SDH Timing
SDH port SDH Timing
Figure 2: SETS function in the FOX61x
2.2 FOX61x Core and Service Units

The FOX61x core and service units listed below provide synchronization functions for the net-
work element:
• CESM3, core unit
PETS synchronization functions, two 2048 kHz synchronization input interfaces, two 2048
kHz synchronization output interfaces. ETR synchronization interface.
The ETR interface provides a PPS output. For further details please refer to [1KHW028774]
User Manual “CESM3”.
Please note:
The “Time of Day” input and output, and the “PPS” input of the ETR synchroniza-
tion interface will be supported in a future release.
5 Ethernet interfaces can be used as PTP Ordinary Clock, Boundary Clock or Transparent
Clock port.
5 Ethernet interfaces can be used as SyncE clock source.
kHz synchronization output interfaces.
Clock port.
kHz synchronization output interfaces.
Clock port.

• LEDE1, E1 transport unit

8 E1 interfaces 2048 kbit/s, can be used as PDH clock sources.
• CEPI1, circuit emulation service and E1 transport unit
8 E1 interfaces 2048 kbit/s, can be used as PDH clock sources.
8 CES Pseudo Wires 2048 kbit/s, can be used as PDH clock sources.
1 local clock oscillator (TCXO), can be used as PDH clock sources.
• DATI1, SHDSL TDM service unit,
8 SHDSL interfaces 2048 kbit/s, NT function with trunk mode, can be used as PDH clock
sources.
8 P12 signals, with trunk mode, can be used as PDH clock sources.
• DEFM1, SHDSL EFM service unit,
24 SHDSL interfaces, NT function with trunk mode, can be used as PDH clock sources.
• SAMO1, STM-4 SDH and Ethernet over SDH transport unit,
SETS synchronization functions, can be used as PDH clock source.
2 STM-4 or STM-1 interfaces, 2 STM-1 interfaces, can be used as SDH clock sources.
4 P12 signals, demapped from VC-12, can be used as PDH clock sources.
2 STM-4 interfaces, 2 STM-4 or STM-1 interfaces, can be used as SDH clock sources.
2 STM-16 or STM-4 interfaces, 2 STM-4 or STM-1 interfaces, can be used as SDH clock
sources.
2 STM-16 or STM-4 interfaces, 2 STM-4 or STM-1 interfaces, can be used as SDH clock
sources.
Please refer to [1KHW002460] System Description “FOX61x R15B” for a short description of all
FOX61x units or refer to the corresponding user manuals for the detailed description of the core
or service unit.

FOX61x | SYNCHRONIZATION SPECIFICATION
3 Specification
3.1 Feature Licenses

Part of the FOX61x functionality is subject to feature licenses. For more information on feature
licenses please refer to [1KHW028777] Release Note “FOX61x System Release R15B” and to
[1KHW028776] Product Description “Feature Licenses for FOX61x”.
3.2 Functions and Specification Overview

The FOX61x network element provides the functions and conforms to the corresponding stan-
dards and recommendations (conformance to applicable parts of the standards) as stated in the
[1KHW002460] System Description “FOX61x R15B”.
3.3 Synchronization Related Standards Documents

Below is a selection of synchronization related standards documents of ETSI and ITU-T. Note
that the FOX61x network element does not comply to all these standards.
• ETSI EN 300 417-6-1 V1.1.3 (05/1999)
Synchronization layer functions
• ETSI EN 300 462-2-1 V1.2.1 (06/2002)
Synchronization network architecture based on SDH networks
• ETSI EG 201 793 (10/2000)
Synchronization network engineering
• ITU-T G.803 (03/2000)
Architecture of transport networks based on the synchronous digital hierarchy (SDH)
• ITU-T G.810 (08/1996)
Definitions and terminology for synchronization networks
• ITU-T G.811 (09/1997)
Timing characteristics of primary reference clocks
• ITU-T G.811.1 (08/2017)
Timing characteristics of enhanced primary reference clocks
• ITU-T G.812 (06/2004)
Timing requirements of slave clocks suitable for use as node clocks in synchronization net-
works
• ITU-T G.813 (03/2003)
Timing characteristics of SDH equipment slave clocks (SEC)
• ITU-T G.823 (03/2000)
The control of jitter and wander within digital networks which are based on the 2048 kbit/s
hierarchy
• ITU-T G.825 (03/2000)
The control of jitter and wander within digital networks which are based on the synchronous
digital hierarchy (SDH)
• ITU-T G.7721 (11/2018)
Management requirement and information model for synchronization
• ITU-T G.8260 (08/2015)
Definitions and terminology for synchronization in packet networks

FOX61x | SYNCHRONIZATION SPECIFICATION
• ITU-T G.8261/Y.1361 (08/2019)

Timing and synchronization aspects in packet networks
• ITU-T G.8261.1/Y.1361.1 (02/2012)
Packet delay variation network limits applicable to packet-based methods (Frequency syn-
chronization)
• ITU-T G.8262/Y.1362 (11/2018)
Timing characteristics of synchronous equipment slave clock
• ITU-T G.8262.1/Y.1362.1 (01/2019)
Timing characteristics of enhanced synchronous equipment slave clock
• ITU-T G.8263/Y.1363 (08/2017)
Timing characteristics of packet-based equipment clocks
• ITU-T G.8264/Y.1364 (08/2017)
Distribution of timing information through packet networks
• ITU-T G.8265/Y.1365 (10/2010)
Architecture and requirements for packet-based frequency delivery
• ITU-T G.8265.1/Y.1365.1 (07/2014)
Precision time protocol telecom profile for frequency synchronization
• ITU-T G.8266/Y.1376 (11/2016)
Timing characteristics of telecom grandmaster clocks for frequency synchronization
• ITU-T G.8271/Y.1366 (08/2017)
Time and phase synchronization aspects of telecommunication networks
• ITU-T G.8271.1/Y.1366.1 (10/2017)
Network limits for time synchronization in packet networks
• ITU-T G.8271.2/Y.1366.2 (08/2017)
Network limits for time synchronization in packet networks with partial timing support from
the network
• ITU-T G.8272/Y.1367 (11/2018)
Timing characteristics of primary reference time clocks
• ITU-T G.8272.1/Y.1367.1 (11/2916)
Timing characteristics of enhanced primary reference time clocks
• ITU-T G.8273/Y.1368 (03/2018)
Framework of phase and time clocks
• ITU-T G.8273.2/Y.1368.2 (01/2017)
Timing characteristics of telecom boundary clocks and telecom time slave clocks
• ITU-T G.8273.3/Y.1368.3 (10/2017)
Timing characteristics of telecom transparent clocks
• ITU-T G.8275/Y.1369 (08/2017)
Architecture and requirements for packet-based time and phase distribution
• ITU-T G.8275.1/Y.1369.1 (06/2016)
Precision time protocol telecom profile for phase/time synchronization with full timing support
from the network
• ITU-T G.8275.2/Y.1369.2 (06/2016)
Precision time protocol telecom profile for phase/time synchronization with partial timing sup-
port from the network
• ITU-T G.Sup36 (11/1988)
Jitter and wander accumulation in digital networks
• ITU-T Series G.Sup65 (10/2018)
Simulations of transport of time over packet networks

FOX61x | SYNCHRONIZATION SYNCHRONIZATION APPLICATIONS
4 Synchronization Applications
4.1 Network Reference Timing Distribution

TDM network elements (NE) are generally required to be synchronized to a network reference
clock. Other NEs can be required to be synchronized to a network reference clock and phase,
including time of day. In these NEs a centralized NE timing source provides the synchronous
timing signal to all NE functions requiring this signal.
There exist several approaches how to bring the network timing to the NE:
• Master-slave strategy over synchronization networks,
• Distributed PRC (Primary Reference Clock) strategy with e.g. GPS technology,
• Mixed PRC strategy as a combination of master-slave strategy and distributed PRC strategy.
Please note:
The plesiochronous TDM applications require no PRC derived NE timing, but still
the service clock must fulfill the TDM timing requirements.
4.1.1 Master - Slave Timing Distribution

In a master-slave synchronization network usually several hierarchy levels of node clocks exist:
• On the highest hierarchy level, one single timing source, the Primary Reference (Time) Clock
(PRC, ITU-T G.811 or PRTC, ITU-T G.8272) provides the timing for all network elements. In
the following only the term “PRC” will be used.
• The timing is distributed from the PRC to the next lower hierarchy level timing source called
Synchronization Supply Unit (SSU, ITU-T G.812), or
to a PTP Ordinary Clock or Boundary Clock (ITU-T G.8273.2) via PTP Transparent Clocks
(ITU-T G.8273.3).
• The timing is further on distributed from the SSU to the next lower hierarchy level timing
source called Synchronous Equipment Clock (SEC, ITU-T G.813 or ITU-T G.8262).
The master-slave synchronization network uses the communication network for the transport of
the synchronization information from the PRC to the network nodes.
The TDM and Synchronous Ethernet (SyncE) timing distribution network is defined in the ITU-T
G.803, ITU-T G.823, and ITU-T G.8261 recommendations.
UTC UTC = universal time coordinated
PRC PRC = primary reference clock

G.811
SSU SSU SSU = synchronization supply unit

G.812 G.812 (node clock)
SEC SEC SEC SEC

G.813 G.813 G.813 G.813 SEC = synchronous equipment clock
G.8262 G.8262 G.8262 G.8262 (network element clock)
Figure 3: Hierarchical TDM and SyncE synchronization network architecture
The PTP timing distribution network is defined in the ITU-T G.8271.1 and ITU-T G.8271.2 rec-
ommendations.

UTC UTC = universal time coordinated
PRTC
PRTC =primary reference time clock
G.8272
(grand master clock)
BC
BC = boundary clock
G.8273.2
TC TC TC = transparent clock
G.8273.3 G.8273.3
OC OC OC OC OC = ordinary clock
G.8273.2 G.8273.2 G.8273.2 G.8273.2
Figure 4: Hierarchical PTP synchronization network architecture
The maximum number of SSU and SEC in a PDH/SDH synchronization network is shown in the
synchronization network reference chain, refer to the Figure 5 below.
A TDM network element can be connected to any of the SEC network elements.

PRC
SEC
PDH
SEC TDM distribution
N
SEC TDM
SSU SSU
SEC TDM
SEC TDM
N PDH
distribution
SEC TDM
SSU SSU
SEC TDM SEC TDM
The number N of SEC between two

SEC TDM SEC TDM SSU is in maximum 20.
N
The sum of all N is in maximum 60.
SEC TDM SEC TDM The number of SSU in a distribution

chain is in maximum 10.
Figure 5: Synchronization network reference chain
The maximum number of Ordinary Clocks and Transparent Clocks in a PTP synchronization
network depends on the network setup and if the frequency distribution is supported by the
physical layer. For further information please refer to ITU-T G.8271.1 and ITU-T G.8271.2.
4.1.2 Distributed PRC Timing Distribution

One approach to bring the network timing to the interworking function NE is to follow a distrib-
uted PRC strategy. For instance, by means of GPS technologies.
The main objective of the synchronization network is to synchronize each SSU with a PRC,
while the transport network elements (SEC) are still master-slave-synchronized.
The network is running in the pseudo-synchronous mode. The G.811 recommendation specifies
a PRC frequency tolerance of 1 part in 1011 for observation periods greater than one week. This
can lead to a phase deviation between two PRC timing sources of 1 bit in 1 day (at 2048 kbit/s)
if the distributed PRC are not synchronized to one common clock source.
PRC PRC PRC PRC PRC = primary reference clock

G.811 G.811 G.811 G.811
SSU SSU SSU SSU SSU = synchronization supply unit

G.812 G.812 G.812 G.812 (node clock)
Figure 6: Distributed PRC network architecture

4.1.3 Mixed PRC Timing Distribution

The mixed PRC architecture combines the advantages of the master-slave and the distributed
PRC timing distribution.
The synchronization network is in principle set up as master-slave network but places the GPS
receivers at selected locations of the network, e.g. at important network nodes with many pieces
of equipment or nodes with few suitable reference signals.
4.1.4 Timing Source Redundancy

In order to be resistant to network failures the timing source should be applied to a NE, e.g. to a
SEC G.813, via at least two independent and, if possible, diversely routed paths.
UTC UTC
PRC PRC
G.811 G.811
SSU SSU SSU SSU

G.812 G.812 G.812 G.812
SEC SEC SEC SEC SEC SEC SEC SEC

G.813 G.813 G.813 G.813 G.813 G.813 G.813 G.813
SEC SEC SEC SEC SEC SEC SEC SEC

G.813 G.813 G.813 G.813 G.813 G.813 G.813 G.813
tree network ring network
active timing path

standby timing path
Figure 7: Synchronization via two independent paths
4.2 Synchronization Paths

For the transport of timing information within the synchronization network, mainly two distribu-
tion methods can be used:
• TDM based distribution.
The TDM based method can be split into two different approaches:
− Physical layer distribution.
The timing information is carried in the physical layer of the transport signal. The signal
state changes can be evaluated at the receiver and be used to regenerate the timing
information.
This method of timing distribution is restricted to frequency information.
− Logical layer distribution.
The timing information is carried in the logical layer of the transport signal. Typically the
logical layer is mapped into a signal of the transport layer, e.g. P12 signal mapped to

SDH. The signal state changes can be evaluated at the receiver and be used to regener-
ate the timing information.
• Packet based distribution.
The packet based method can be split into two different approaches:
− The PTP method carries timing information in specific PTP packets which can be evalu-
ated at the receiver to extract frequency, phase and time (of day) information.
The physical layer needs not to be synchronous to the network element timing, but can
be used in addition to accelerate the frequency acquisition time.
− The CES (Circuit Emulation Service) method evaluates the time stamps or the number of
received packets, which are expected in known and regular intervals, to regenerate the
timing information.
4.2.1 Physical Layer
4.2.1.1 SDH
The SDH physical layer is a STM-1, STM-4, STM-16, … traffic signal. The SDH traffic signals
can be used to synchronize the SEC of a SETS function in a SDH network element.
4.2.1.2 PDH
The PDH physical layer is a E1 traffic signal. The PDH traffic signals can be used to synchro-
nize the NEC (Network Equipment Clock) of a PETS function in a PDH network element.
4.2.1.3 DSL
The DSL physical layer can be a SHDSL signal or any other flavor of DSL signal. The DSL sig-
nal can transport timing information from the LT function to the NT function, i.e. the timing infor-
mation can be extracted at the NT function be used to synchronize the NEC (Network Equip-
ment Clock) of a PETS function in a PDH network element.
4.2.1.4 SyncE (Synchronous Ethernet)

Traditional Ethernet networks are free-running. However, all the key elements exist within Ether-
net technology in order to make it synchronous and allow a master-slave synchronization archi-
tecture to be introduced at the physical layer. The Ethernet physical layer can then be used to
provide reference timing signal distribution over packet networks.
The SyncE traffic signals can be used to synchronize the EEC (Ethernet Equipment Clock).
In a chain of Ethernet based network elements all NEs must support SyncE, otherwise the tim-
ing information flow is interrupted.
4.2.2 Logical Layer
4.2.2.1 PDH via SDH

The PDH signal is a P12 data signal (2048 kbit/s) according to ITU-T G.704, transported in an
SDH signal. At the receiver the P12 data signal is demapped from an SDH virtual container VC-
12 and used to synchronize the NEC (Network Equipment Clock) of a PETS function in a PDH
network element.

A P12 signal demapped from an SDH signal is impaired with demapping jitter and
pointer adjustment jitter.
→ It is not recommended to use a demapped P12 as PDH clock source.

4.2.2.2 PDH via DSL

The PDH signal is a P12 data signal (2048 kbit/s) according to ITU-T G.704, transported in an
DSL signal. At the receiver the P12 data signal is demapped from an DSL frame and used to
synchronize the NEC (Network Equipment Clock) of a PETS function in a PDH network ele-
ment.
The PDH signal can transport timing information in both directions, i.e. from the LT function to
the NT function and from the NT function to the LT function.
4.2.3 PTP Packet Method

The PTP packet based method for timing distribution is based on timing information which is
carried in timing protocol packets. Timing protocol packets can be used for the distribution of
frequency information and also phase and time of day information.
UTC
Boundary Transparent Ordinary

Clock Clock Clock
Slave
Residence time
correction
PTP PTP
MAC MAC MAC MAC
TSU TSU TSU TSU
Master PHY PHY PHY Slave PHY
data
PRC timing
TSU = Time Stamping Unit
Figure 8: PTP timing distribution over the packet network
PTP defines the following clock types:
4.2.3.1 PTP Boundary Clock

Boundary clocks are defined within a PTP system to sit in place of standard network switches or
routers.
Boundary clocks have several PTP ports.
The boundary clock acts as an interface between separate PTP domains intercepting and pro-
cessing all PTP messages and passing all other network traffic.
The BMC (Best Master Clock) algorithm is used by the boundary clock to select the best clock
any port can see. The chosen port is set as a slave and all other ports of the boundary clock are
asserted as masters to their domain.
In the FOX61x a PTP Boundary Clock can be a slave or a master. A slave can be port based,
Ethernet VLAN based or IP VLAN based. A master can be port based or IP VLAN based.
IP VLAN based PTP master clocks are typically used at the boundary between a core PTP net-
work and an access PTP network, making the PTP distribution scalable by reducing the amount
of PTP traffic in the core network.

Please note:
An IP VLAN master clock which is not phase locked will send the quality level 0
towards the slaves.
→ This prevents the slaves to synchronize to the non phase locked master.
Please note:
The “Master” role for an IP VLAN (UDP/IPv4 (L3) PTP transport) is not available for
the CESM1 and CESM2 units.
4.2.3.2 PTP Transparent Clock

Transparent clocks correct the transit delay of PTP packets running through a switch or router.
Transparent clocks update a time-interval field allowing for delay asymmetry corrections.
There are two types of transparent clocks, end-to-end and peer-to-peer.
• End-to-end transparent clocks cancel queuing and processing delays in a switch.
• Peer-to-peer transparent clocks cancel queuing and processing delays in a switch and the
link delay to the peer switch.
In transparent clock network elements the local clock is typically not synchronized to the PTP
timing.
In the FOX61x a PTP Transparent Clock is Ethernet VLAN based or IP VLAN based.
4.2.3.3 PTP Ordinary Clock

An ordinary clock is a PTP clock with a single PTP port.
It can be selected as a master or slave within a segment according to the BMC algorithm.
Ordinary clocks are used as the end nodes within a network connected to devices needing syn-
chronization.
In the FOX61x a PTP Ordinary Clock is always a slave. It can be port based, Ethernet VLAN
based or IP VLAN based.
4.2.4 Circuit Emulation Service Method

The circuit emulation service (CES) method for timing distribution is based on timing information
which is carried in the service signal itself and is extracted with conventional methods as e.g.
buffer fill level controlling an clock oscillator.
The CES approach can be used to distribute
• the network timing, when the TDM timing source is derived from a PRC, or
• the service timing (customer timing), when the TDM signal uses an autonomous timing
source.
Such a method can be based on the time stamps carried by the CES packets or by the jitter buf-
fer fill level in the receiving network element, i.e. the timing information is carried in the service
signal. The packet network itself carries no timing information.

PRC PRC available at the IWF
Packet
CES Switched CES
TDM TDM IWF Ethernet Et hernet IWF TDM TDM
Network
Equipment Equipment
PRC PRC available at the TDM end system
Packet
CES Switched CES
Network
Equipment Equipment
CT Customer Timing transported over the PSN
Packet
CES Switched CES
Network
Equipment Equipment
data
PRC timing
customer timing
Figure 9: CES timing distribution over the packet network
In the CES interworking function the TDM timing must be regenerated in the clock recovery cir-
cuit and forwarded to customer equipment at the remote end.
4.3 Timing Source Selection

A network element receiving timing information from more than one source has to make a deci-
sion which timing source shall be used for the NE synchronization.
There are two approaches for this selection process:
• Priority based
The NE assigns a fixed priority to each of the available timing sources. It selects the timing
source according to the assigned priority.
This approach restricts the synchronization network layout because it must be strictly tree
based. Otherwise there might be a risk of a timing loop.
See section 4.3.1 Priority Based (on page 22).

• Quality Level based

The NE evaluates the quality of the incoming timing sources. The quality information is car-
ried within the synchronization signals. It selects the timing source with the highest quality.
The quality information is forwarded to the outgoing timing signal, but can be modified
according to a specified rule or according to the currently selected timing source.
This approach is more flexible than the priority based approach. It is also applicable for syn-
chronization distribution in ring networks because the quality level information modifications
can create a virtual tree structure for the synchronization.
See section 4.3.2 Quality Level Based (on page 22).
4.3.1 Priority Based

When using the configured priority for the selection of a timing source the NE autonomously
selects the timing source with the highest priority from the available timing sources. When the
selected timing source fails the NE selects the timing source with the next lower priority.
Synchronization networks using only the priority must be set up as tree networks. No ring or
meshed networks are allowed.
Using the priority based selection algorithm the (possibly available) quality level information of a
timing source will not be evaluated. It is therefore not possible to disable a timing signal which is
based on a low quality source or to disable a timing signal which is based on a looped timing
signal. A timing signal is only disabled with a traffic signal failure, e.g. loss of signal, on the cor-
responding signal.
The upper example in Figure 10 selects port-1 as timing source because it has a higher priority
(1 is the highest priority value).
The lower example in Figure 10 selects port-2 as timing source because the timing source on
port-1 has failed.
Clock Selection
Source Priority
port-1 1
port-2 2
NE1
port-1 port-2
Selected Clock
Source: port-1
NE1
port-1 port-2
Selected Clock
Source: port-2
Figure 10: Priority based clock source selection
4.3.2 Quality Level Based
4.3.2.1 Introduction
The QL (Quality Level) information for synchronization purposes, carried within the synchroniza-
tion signals, is a part of the SSM (Synchronization Status Message) signaling system for PDH,
SDH, DSL, and synchronous Ethernet signals.
The SSM is a four bit code, defined in ITU-T G.704 for PDH, in ITU-T G.707 for SDH, and in
ITU-T G.8264 for SyncE. The following codes are defined:

• SSM = 0000: QL = 0
“Quality unknown”,
• SSM = 0010: QL = 2
“ITU-T G.811 (PRC)”,
• SSM = 0100: QL = 4
“ITU-T G.812 (SSU-A)”,
• SSM = 1000: QL = 8
“ITU-T G.812 (SSU-B)”,
• SSM = 1011: QL = 11
“ITU-T G.813 Option I (SEC)” or
“ITU-T G.8264 Option I (EEC)”,
• SSM = 1111: QL = 15 “Do not use for synchronization”.
The remaining 4-bit codes are reserved for quality levels defined by individual operators.
Please note:
A QL = 14 value is applied if the PETS on the core unit makes corrections on the
PPS signal, or if the PETS is in free running mode.
→ Packet based teleprotection units will immediately stop timing related opera-
tions.
Please note:
A lower QL value designates a higher clock quality.
Please note:
The QL value “0” is generally not used.
The QL value is transported
• in the SSM of the timeslot 0 of a structured P12 signal, or
• in the SSM of the multiplex section overhead of an SDH signal, or
• in the SSM of the Ethernet synchronization messaging channel (ESMC) for SyncE, or
• in the Clock Class parameter of the PTP Announce messages.
4.3.2.2 Synchronization Networks Using Quality Level Information

When using the quality level for the selection of a timing source each timing signal carries the
information about the quality of its timing source, i.e. if it can be used as a timing source or not.
Synchronization networks can be set up as tree networks, ring or meshed networks.
From the available timing sources the NE autonomously selects the timing source with the high-
est quality. If two sources have the same QL the configured priority decides which timing source
will be selected.
In a ring network also the timing signals are transported in the ring. There is a risk to have a tim-
ing loop. A looped timing is free running and will drift to the lower or upper clock frequency limit
of the involved oscillators. The timing of theses NEs is no longer derived from a PRC.
Measures must be taken to prevent timing loops in ring or meshed networks. The forwarding of
timing information must be based on a logical tree structure. The logical tree must be main-
tained also in failure situations, e.g. with line breaks or loss of timing sources.

Without a logical tree a timing loop will be generated, leading to undefined timing
behavior.
To provide a logical tree for the timing distribution the following rules apply:
• The QL in direction of the selected timing source (backwards direction) is set to “Do Not
Use”, i.e. the currently active QL value is set to “15”.
• The QL in direction of the non-selected timing sources (forward direction) is set to “Can Be
Used”, i.e. that currently active QL value is not changed.
The upper example in Figure 11 selects port-1 as timing source. Correspondingly the outgoing
QL of port-1 is set to “Do Not Use”, i.e. QL=15. The QL in forwarding direction at port-2 is the
unchanged or optionally modified QL that has been received on port-1.

The lower example in Figure 11 selects port-2 as timing source because it has a higher quality
than port-1. Correspondingly the outgoing QL of port-2 is set to “Do Not Use”, i.e. QL=15. The
QL in forwarding direction at port-1 is the unchanged or optionally modified QL that has been
received on port-2.
Port-1 QL Transmission Clock Selection Port-2 QL Transmission
Source Usage Source Priority QL Source Usage
port-1 do not use port-1 1 received port-1 can be used
port-2 can be used port-2 2 received port-2 do not use
do not use: QL = 15 QL = 4
NE1
port-1 port-2
Selected Clock
Source: port-1
QL = 2 can be used: QL = 2
can be used: QL = 4 QL = 4
NE1
port-1 port-2
Selected Clock
Source: port-2
QL = 11 do not use: QL = 15
Figure 11: QL based clock source selection
4.4 Commissioning of a Synchronization Network

Please note:
The synchronization network planning rules and guidelines listed below are based
on the descriptions in
→ ETSI EG 201 793, and
→ ITU-T G.803.
Please refer to these documents for a detailed and in-depth description.
4.4.1 Synchronization Network Planning Principles

A synchronization network is based on several classes of slave clocks with different properties
and different roles:
• The PRC (Primary Reference Clock)
is the timing source of the synchronization network and determines the long-term stability of
the reference frequency.
• The SSU (Synchronization Supply Unit)
regenerates the clock signal after it has passed a chain of SECs and serves as temporary
reference for parts of the network when the connection to the PRC is lost in failure situations.
Usually SSUs are located in network nodes where they distribute a timing signal to all net-
work elements in the node.
• The SEC (Synchronous Equipment Clock, or SDH Equipment Clock)
is the clock incorporated in SDH network elements. The term SEC is also used in this docu-
ment to designate a EEC (Ethernet Equipment Clock) in Ethernet based equipment or a PEC
(Packet-based Equipment Clock). SEC, EEC and PEC provide all the same clock quality.
As shown in section 4.1.1 Master - Slave Timing Distribution (on page 14) the number of cas-
caded SEC, EEC and/or PEC must be limited. The jitter and wander limit specification in larger
synchronization networks can only be respected with the deployment of SSUs.
The following principles should be observed when planning a synchronization network:

• Distribute the reference timing signal from the PRC to all network elements requiring syn-
chronization.
• The method used for propagating the reference timing signal in the network is the master-
slave method, i.e. from the PRC (master) to the SEC (slave), possibly via a SSU, using a
(logical) tree based network structure. See section 4.1.1 Master - Slave Timing Distribution
(on page 14).
• A slave clock must always be synchronized to a clock of higher (or at least equal) quality.
For example a SSU is never synchronized to a SEC running in holdover mode. If no ade-
quate clock source is available the slave clock changes to the holdover mode.
• Timing loops must be prevented because all clocks in a timing loop are isolated from a PRC
and are subject to unpredictable frequency instabilities. Even multiple failures in a synchroni-
zation network must not lead to timing loops.
The insertion of SSUs with an absolute frequency offset detection at strategic places in the
network can raise an alarm if the frequency drifts away because of a timing loop.
• The selection of a clock source for a slave clock must be deterministic, i.e. no failure state
should lead to an oscillating or unstable behavior.
• In case the synchronization network operates (temporarily) without reference the synchroni-
zation network must maintain its jitter and wander limit specification. Use one of the methods
below to counter this problem:
− Use clocks with very good hold-over performance, which allows to operate without refer-
ence during the repair period of the reference link. This method is mainly used in the PRC
and SSU layer.
− Duplicate the clock reference inputs, preferably over geographically separated links from
independent sources. This provides protection against single failures of the synchroniza-
tion distribution network. This method is mainly used in the SSU and SEC layer.
4.4.2 Planning Procedures
4.4.2.1 Introduction
The engineering of the synchronization network in a synchronization area should be carried out
before the equipment is commissioned. The synchronization area is a geographic area in which
all equipment which needs to operate synchronously is synchronized to the one master-clock in
that area.
The results of the network synchronization engineering process should be described in a syn-
chronization plan. The synchronization plan should be revised each time new equipment is
installed in a synchronization area. The plan contains …
− maps of the area and all offices with the normal and fall-back references indicated,
− the values of all provisioned parameters that affect the synchronization in the area,
− specification of test cases to verify the quality and robustness of the synchronization net-
work,
− results of measurements and evaluations on the synchronization network,
− a log of all synchronization related maintenance activities.
A synchronization responsible person is usually nominated to maintain the synchronization plan
and to co-ordinate the synchronization related activities in the synchronization areas.
4.4.2.2 Engineering Steps Overview

The engineering of a synchronization network is done in several steps, which can be handled in
order as follows:
• Decide about the PRC-level strategy to be followed.
The PRC-level is the collection of PRC compliant clocks in an operator domain that are the
master clocks for the different synchronization areas when the synchronization network does
not experience failures.

• Place the PRC(s) and SSUs in the synchronization area taking into account the allowed
maximum length of SEC synchronization chains.
• Divide the synchronization area into an SSU-level and into SEC sub-networks.
The SSU-level is the collection of SSU compliant clocks in a synchronization area and their
interconnections. SECs are not part of the SSU-level, but are considered to be transparent
on connections between SSUs. Under failure free conditions, there is only one intercon-
nected SSU-level in a synchronization area.
The SEC sub-network is a collection of SEC clocks interconnected by timing reference sig-
nals. When engineering the synchronization in a SEC sub-network, the directly connected
SSUs need also to be considered.
• Group the SSUs according to their quality, defined as PRC autonomy period, in a number of
classes.
The PRC autonomy period is the period of time over which a clock, after it has lost all its ref-
erence inputs, can restrict its phase drift within the bounds given by the network limits for
synchronization signals.
• Engineer the SSU-level synchronization network in the synchronization area, i.e. considering
only PRCs and SSUs.
• Engineer the SEC-level synchronization networks in the synchronization area, i.e. consider-
ing only SECs in a SEC sub-network.
The SEC-level is the collection of SEC compliant clocks in a synchronization area and their
interconnections. SSUs are not part of the SEC-level.
The above steps are described in more detail in the sections below.
4.4.2.3 PRC-Level Options

In each synchronization area one PRC is active at any moment (but additional stand-by PRCs
can be part of a synchronization area). Two strategies can be followed to determine the size of
each synchronization area:
• Master - slave timing distribution:
This strategy makes one big synchronization area. It has the advantage that the number of
synchronization areas that an end-to-end traffic connection has to cross is minimized.
However, the synchronization network is more complex. The synchronization trails become
longer, and are more susceptible to impairments and wander accumulation.
• Distributed PRC timing distribution:
This strategy makes each node a separate synchronization area. The engineering of each
synchronization area almost trivial. The synchronization network will be very reliable.
In fact, these two strategies can be considered as “extremes” on a continuous scale. Actual
sizes of synchronization areas can be anywhere in between these “extreme” positions.
4.4.2.4 PRC and SSU Placement

Check the layout of the transport network to be synchronized and place the PRC and SSU into
the network so the maximum length of SEC synchronization chain is respected. Preferably the
PRC is located in the middle of the network to have as short synchronization trails as possible.

SEC
Figure 12: Transport network in a synchronization area
PRC
SSU SSU
SEC
Figure 13: Transport network with deployed PRC and SSUs in a synchronization area
4.4.2.5 SSU-Level Synchronization

The SSU-level of the synchronization network consists of the PRCs and SSUs in a synchroniza-
tion area. The links between the PRC and SSUs, including the SECs, are considered transpar-
ent for the timing information in the SSU-level view.

PRC
SSU SSU
Figure 14: SSU-level synchronization network in a synchronization area
The SSUs in the SSU-level view can be grouped according to their quality in a number of
classes. The quality criterion is the “PRC autonomy period”. Knowing the PRC autonomy period
of a clock, one can e.g. determine if the SSU can be operated with a single reference. This
requires that the PRC autonomy period is longer than the time it takes to repair a failure.
In most cases two SSU classes are sufficient for one synchronization area.
Now engineer the SSU-level synchronization network. Assign primary and secondary reference
timing signals to each SSU. Avoid to synchronize a higher class SSU from a lower class SSU.
Verify that no timing loops are formed or can be formed in case of a failure.
Typically the reference timing selection algorithm in a SSU is priority based.
Please note:
A methodology called “labeling scheme” can be used as a simple tool to check
whether a proposed scheme has a risk of timing loops.
→ Refer to ETSI EG 201 793, or
→ refer to ITU-T G.803.
PRC
SSU SSU
1 2
primary timing path

secondary timing path
Figure 15: SSU-level synchronization timing paths
SSU1 of the example in Figure 15 has a high PRC autonomy period

SSU2 of the example in Figure 15 has a low PRC autonomy period

4.4.2.6 SEC-Level Synchronization

After engineering the SSU-level synchronization network the SEC-level synchronization sub-
networks have to be engineered.
The SEC-level consists of a number of unconnected SEC sub-networks, each consisting of
SECs connected by traffic and/or synchronization links. These SEC sub-networks can be engi-
neered separately. See Figure 16 for an example.
SEC
Figure 16: SEC-level with 2 SEC sub-networks and the SSU-level synchronization paths
Within the SEC sub-network automatic restoration is mandatory because the PRC autonomy
period of a SEC is generally below 1 minute. Typically the reference timing selection algorithm
in a SEC is quality level based. Define the SSM protocol parameters for each SEC sub-network,
taking into account the directly interconnected SSUs.
Under normal conditions the flow of the timing information between the SSUs is according to the
plan engineered for the SSU-level. In failure situations the synchronization restores as well as
possible without creating timing loops, hierarchy violations, or instabilities. The variables at dis-
posal are
− the selection of possible references,
− the setting of priorities for the assigned references,
− using fixed SSM assignments to certain reference inputs, and
− setting the squelch thresholds for synchronization outputs.
Assignment and priority setting have in general to be provisioned both for the internal oscillator
and for the external clock output of an SEC network element.
Each SEC network element should have a primary and a secondary timing reference to chose
from. This is realized in the SEC sub-networks in Figure 17, except for NE5 which has only one
connection to the synchronization network.

NE 5
primary timing path

secondary timing path
SEC
Figure 17: SEC sub-networks with primary and secondary timing paths
The examples in Figure 17 show implementations which are resilient to a single failure in the
synchronization network. If the network should be robust also in case of more than one network
failure some more sophisticated solutions must be envisaged. See section 4.4.3 Specific Appli-
cations in Synchronization Networks (on page 30).
4.4.3 Specific Applications in Synchronization Networks
4.4.3.1 Single Timing Source in Ring Networks

With a single timing source in a ring network the ports of the NE providing the timing source
towards the subtended NEs are disabled from being used as a timing source to avoid a timing
loop.
SSU
NE1 NE2 NE3 NE4
disable ports as
timing source
NE5 NE6 NE7 NE8
active timing path

standby timing path
Figure 18: Ports configured to not to be used as timing source
NE1 is synchronized with the SSU timing. If the SSU timing fails NE1 is synchronized to its
internal timing source. The subtended NE2 to NE8 are all synchronized with NE1.
If the NE1 fails the NE2 and NE5 will both be synchronized to their internal timing sources.
There will be two timing islands, NE2 to NE4 and NE5 to NE8.

4.4.3.2 Two or More Timing Sources in Ring Networks

With two or more timing sources in a ring network the incoming timing sources must be given a
fixed quality level. At the ports of the NE providing the timing source towards the subtended NEs
the incoming fixed timing source quality level must be mapped to “Do Not Use”, i.e. to QL=15.
SSU1 SSU2
fixed fixed
QL=1 QL=2
NE1 NE2 NE3 NE4
map incoming map incoming

QL 1 to QL 15 QL 2 to QL 15
NE5 NE6 NE7 NE8
active timing path

standby timing path
Figure 19: QL mapping of selected timing sources to “Do Not Use”
NE1 is synchronized with the SSU1 timing with QL=1. The subtended NE2 to NE8 are all syn-
chronized with NE1. The timing loop with QL=1 is interrupted at the incoming ports of NE1 by
configuring the QL input mapping QL=1 to QL=15.
If the SSU1 timing fails NE1 is synchronized to its internal timing source until NE4 selects and
distributes the SSU2 timing with QL=2 as active timing source. The subtended NE1 to NE3 and
NE5 to NE8 are all synchronized with NE4. The timing loop with QL=2 is interrupted at the
incoming ports of NE4.
If both SSU timings fail one of the NEs must take over the role as timing master, using its inter-
nal timing source. Also in this case the timing loop must be interrupted by mapping QL=11 (from
the internal timing source) to QL=15. In the example below NE1 will use its internal timing
source since it will not synchronize to the internal timing sources of other NEs.
SSU1 SSU2
fixed fixed
QL=1 QL=2
NE1 NE2 NE3 NE4
map incoming
QL 1 to QL 15, map incoming
map incoming QL 2 to QL 15
QL 11 to QL 15
NE5 NE6 NE7 NE8
active timing path

standby timing path
Figure 20: QL mapping of selected and internal timing sources to “Do Not Use”

4.4.3.3 Selecting the Synchronization Priority

If two network elements are connected with a (bidirectional) synchronization link the priority of
the timing source selection must not be set to the highest value at both sides of the link (port-1
of the examples in Figure 21). Otherwise the synchronization forwarding direction is selected by
chance. There is also a risk of instability.
“A” in Figure 21 shows the case where NE2 has first chosen to select port-1 as timing source.
NE2 sends “do not use” towards NE1. NE1 then choses port-2 as timing source. This is a stable
situation.
“B” in Figure 21 shows the case where NE1 has first chosen to select port-1 as timing source.
NE1 sends “do not use” towards NE2. NE2 then choses port-2 as timing source. This is a stable
situation.
“C” in Figure 21 shows the instable case where NE1 and NE2 will both make the decision to
chose port-1 as timing source since both receive a valid QL at port-1. If this happens at the
same time both NEs will then send the QL “do not use” to their neighbors and consequently
both NEs will make the decision to chose port-2 as timing source, and so on.
Clock Selection Port-1 QL Transmission Port-1 QL Transmission Clock Selection
Source Priority QL Source Usage Source Usage Source Priority QL
port-1 1 received port-1 do not use port-1 do not use port-1 1 received
port-2 2 received port-2 can be used port-2 can be used port-2 2 received
A
do not use: QL = 15 do not use: QL = 15 QL = 2
NE1 NE2
port-2 port-1 port-1 port-2
Selected Clock Selected Clock
Source: port-2 Source: port-1
QL = 2 can be used: QL = 2 can be used: QL = 2
B
can be used: QL = 2 can be used: QL = 2 QL = 2
NE1 NE2
QL = 2 do not use: QL = 15 do not use: QL = 15
C
do not use: QL = 15 can be used: QL = 2 QL = 2
NE1 NE2
QL = 2 can be used: QL = 2 do not use: QL = 15
Figure 21: Arbitrary and instable timing source selection

FOX61x | SYNCHRONIZATION FOX61X SYNCHRONIZATION FUNCTIONS
5 FOX61x Synchronization Functions
5.1 Overview
Figure 22 shows an overview of the synchronization functions available in the FOX61x network
element. The central components are the
• PETS (Plesiochronous Equipment Timing Source), and the
• SETS (Synchronous Equipment Timing Source).
PTP
Timing Sources PETS Network Element
Timing
SyncE
Timing Sources
External External
Synchronization Synchronization
Inputs Outputs
PDH
Timing Sources SETS
SDH Timing
SDH
Timing Sources
Figure 22: Synchronization implementation in FOX61x
The PETS provides the timing for the network element:

• Transmit timing for PDH traffic signals (E1, P12, DSL),
• Transmit timing for Synchronous Ethernet ports,
• Transmit time stamps of PTP packets,
• External synchronization output.
The PETS can be synchronized from the following timing sources:
• Receive timing from PDH traffic signals (E1, P12, DSL),
• Receive timing from Synchronous Ethernet ports,
• Receive time stamps of PTP packets,
• External synchronization input,
• SETS timing.
With the network element manager FOXCST the PETS functions are managed via the synchro-
nization access points available in the FOXCST “Synchronization” view. For a detailed descrip-
tion of the PETS please refer to section 5.3 PETS (on page 39).
The SETS provides the timing for the SDH subsystem:
• Transmit timing for SDH traffic signals (STM-1, STM-4,STM-16),
• Timing source for the PETS,
• External synchronization output.
The SETS can be synchronized from the following timing sources:
• Receive timing from SDH traffic signals (STM-1, STM-4,STM-16),

• Receive timing from PDH traffic signals (E1, P12, DSL),

• Receive timing from Synchronous Ethernet ports,
• External synchronization input.
With the network element manager FOXCST the SETS functions are managed via the SDH ser-
vice unit access points available in the FOXCST “Tree View”. For a detailed description of the
SETS please refer to section 5.2 SETS (on page 34).
For a detailed description of the external synchronization inputs please refer to section 5.5
External Synchronization Inputs ESI-1 and ESI-2 (on page 52).
For a detailed description of the external synchronization outputs please refer to section 5.6
External Synchronization Output ESO-1 (on page 53) and section 5.7 External Synchronization
Output ESO-2 (on page 56).
5.2 SETS
The FOX61x provides one SETS instance per SDH service unit, i.e. on every SAMO1 and
SAMOx unit. All SDH ports and SDH processing on an SDH service unit are synchronized to the
synchronous equipment timing source (SETS).
The SETS is handled as a unit function. It is possible to synchronize the SETS functions of sev-
eral SDH service units to one common clock source.
The SETS has three external clock input types (T1, T2, T3), one internal clock source and pro-
vides two external clock output types (T0, T4) as shown in the figure below.
SETS
Selector A
Selector C
ESO-2 T4
SEC
SDH port 1
SDH port 2
T1 T0
Selector B
SETG PDH-1
SDH port n
Distributor D
PDH-2
PDH-1
PDH-3
PDH-2
T2 PDH-4
PDH-3
PDH-4
T3 ESI-2 SETS: Synchronous Equipment Timing Source

SEC: SDH Equipment Clock
SETG: Synchronous Equipment Timing Generator
T0: NE internal timing distribution
T1: Timing signal derived from an STM-N signal
T2: Timing signal derived from E1, P12, DSL, SyncE or SETS
T3: Timing signal derived from a 2 MHz station clock signal
T4: Timing towards a 2 MHz station clock output signal
Figure 23: SETS functions

Please note:
The selector A in Figure 23 incorporates a PLL, maintaining an output clock during
the ESO-2 clock source holdoff time.
Please note:
In Figure 23 the number of T1 inputs is as follows:
→ 4 for an SAMO1 unit.
→ 4 for an SAMOx unit.
→ 8 for an equipment protected SAMOx unit.
Please note:
The T2 and T3 inputs and the internal clock source of Selector A in Figure 23 are
only available on the SAMO1 unit.
The timing sources T1 to T3 are explained in section 5.2.1 Timing Sources (on page 35).
T0 is the synchronization signal used for the unit internal synchronization. T0 is also distributed
to all other core and service units via one of the PDH clock source lines of the PBUS.
For a description of T4 see section 5.7 External Synchronization Output ESO-2 (on page 56).
The SETS function is implemented on every SDH service unit. The SDH synchronization man-
agement functions are located on the SDH service unit access point. For a description of the
FOXCST management functions refer to [1KHW002476] User Manual “SAMO1” and refer to
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”.
5.2.1 Timing Sources
5.2.1.1 SDH Clock Sources

The T1 timing sources of Figure 23 are the synchronization signals derived from an SDH inter-
face. Up to 4 (SAMO1 and SAMOx) or 8 (SAMOx with unit equipment protection) SDH clock
sources can be selected for the SETS synchronization in maximum per SDH service unit.
The timing interface is an STM-16, STM-4 or STM-1 data signal according to ITU-T G.707.
When using the quality level for the timing source selection the “SSM” parameter must be
enabled on the multiplex section (MS) of the SDH traffic signal.
5.2.1.2 PDH Clock Sources

The T2 timing sources of Figure 23 are the synchronization signals derived from a E1, P12, DSL
or SyncE data signal or from another SETS. In the FOX61x these synchronization signals are
called “PDH clock sources”. Up to four PDH clock sources are available for the SETS synchroni-
zation in maximum. The T2 timing is distributed in the NE via the PDH clock source lines of the
PBUS.
Please note:
If the SETS on a SAMO1 or SAMOx unit is locked to any of the PDH Clock
Sources it will forward the QL 15 (do not use) inside the FOX61x network element,
i.e. towards the PDH clock source.
→ This avoids a clock loop if e.g. two SETS functions on two SAMOx units use the
PDH Clock Source of the other SAMOx unit as a (secondary) clock source.
→ It is therefore not possible to synchronize the PETS to a SETS function if the
SETS function is synchronized to one of the PDH Clock Sources.
If you have to synchronize the PETS to the SETS function either
• use the Priority based clock selection mode, or
• synchronize the PETS to the same PDH Clock Source as the SETS.

For a detailed description of the PDH timing sources see section 5.3.1 Timing Sources (on
page 41).
A PDH clock source must be selected as a “PDH Clock Source” in the PETS configuration, oth-
erwise it will not be available as SETS PDH clock source.
5.2.1.3 ESI-2 Clock Source

The T3 timing source of Figure 23 is the synchronization signal from an external 2048 kHz clock
input.
The core unit provides 2 external 2048 kHz clock inputs ESI-1 and ESI-2. The core unit selects
the ESI-2 to be used for the SETS synchronization.
The timing interface is a 2048 kHz clock signal according to ITU-T G.703.
Please note:
The ESI clock source selection on the SAMO1 and SAMOx unit for SETS or ESO
is fixed to ESI-2.
Please note:
The ESI-2 port on the CESM3 core unit must be manually enabled when it shall be
used in the SETS or ESO configuration on a SAMO1 or SAMOx unit.
→ The esi-2 managed object on the core unit is activated.
→ The fault management of the esi-2 managed objects on the core unit is acti-
vated.
→ The fault management of the esi-2 managed object is available on the SAMO1
or SAMOx unit as SETS and ESO fault causes.
Please note:
The ESI-2 port on the CESM1 and CESM2 core units is enabled when a clock pri-
ority is assigned to it in the SETS or ESO configuration on an SDH service unit.
→ The esi-2 managed object on the core unit is not activated.
→ The fault management of the esi-2 managed object on the core unit is not acti-
vated.
5.2.1.4 Internal Clock Source

The SEC internal reference clock has an accuracy of ± 4.6 ppm according to ITU-T G.813
(clause 5, option 1).
5.2.2 Timing Source Selection
5.2.2.1 Selection Algorithm

From the available SETS clock sources the SETS autonomously selects the clock source with
the best clock quality. The FOX61x supports two approaches to define the clock quality:
• Selection algorithm according to a configured priority
(AP: /unit-x, Configuration - SETS: Selection Algorithm = Priority):
The SETS selection process is only controlled by the priority.
The algorithm selects the timing source with the highest priority. Note that “1” is the highest
priority. If the selected source fails, the algorithm selects the source with the next highest pri-

ority. If a source with a higher priority becomes available, the algorithm selects this source
(revertive switching).
When two sources have the same priority the algorithm selects any of the sources. In the
case where the selected timing source fails, another source of the same level of priority is
selected (non-revertive switching).
The selection algorithm disregards the quality level (QL).
• Selection algorithm according to the quality level (QL)
(AP: /unit-x, Configuration - SETS: Selection Algorithm = QL):
The algorithm selects the timing source with the best QL. Note that “1” is the best QL. If
there are signals with the same QL, the priorities assigned to the timing sources decide on
the selection.
The SETS selection process first considers the QL and then the Priority.
For a description of the QL handling see section 5.8 Quality Level Handling (on page 60).
5.2.2.2 SETS Clock Source Selection

To make a SETS clock source available it must be configured with a priority value between
− 1 and 10 (SAMO1), or
− 1 and 14 (SAMOx)
in the SETS clock selection configuration dialog on the SAMO1 or SAMOx unit at the AP: /unit-
x, Configuration - SETS.
A clock source is deselected by applying the priority value “Disabled”.
When using the selection algorithm “QL” the QL parameter of the SETS clock sources must be
configured in addition. If the clock source supports the quality level feature set the QL parameter
to “Received”, otherwise assign a fixed quality level in the range 1 to 14.
5.2.2.3 SETS Clock Operation Modes

There are three clock operation modes for the SETS in the FOX61x according to ITU-T G.813:
• Locked
Normal operation mode. The output SETS clock signal is controlled by an external input ref-
erence so they have the same long term average frequency.
• Holdover
If the clock reference fails, SETS will continue operating but in holdover mode. This opera-
tion mode functions with previously stored clock data, acquired during “Locked” operation
mode.
You can also bring the SETS into this mode with the SETS clock operation type command
“Forced Holdover” (AP: /unit-x, Status - SETS - General).
• Free running
If the SETS does not have a clock reference input, it determines its output clock by an inter-
nal default reference frequency.
You can also bring the SETS into this mode with the SETS clock operation type command
“Forced Free Run” (AP: /unit-x, Status - SETS - General).
In the “Auto Selection” mode, the SETS selects its operation mode by itself, depending on the
conditions given by the availability of synchronization sources.
The clock selection process can be controlled by the two parameters “Holdoff Time” and “Wait-
To-Restore Time”:
• Holdoff Time
When a clock source fails the SETS will go to the holdover mode for the configured holdoff
time (configured for the failed clock source) before switching to the next lower priority clock
source.

• Wait-To-Restore Time
When the SETS is operating with a low priority clock source and a previously failed higher
priority clock source becomes available again, the SETS waits for the wait-to-restore time
(configured for the higher priority clock source) before switching to the higher priority clock
source.
SDH clock source 1
Priority 1
available
failed
time
SDH clock source 2
Priority 2
available
failed
time
Internal clock
Priority 10
available
disabled
time
Selected holdoff time holdoff time wait-to-restore wait-to-restore

clock source clock 1 clock 2 time clock 2 time clock 1
clock source 1 clock source 2 internal clock source 2 clock source 1
time
Clock operation
mode
locked holdover locked holdover locked locked
time
Figure 24: SETS clock source selection with 2 external and 1 internal clock sources
Please note:
The clock operation mode “Free Running” is only displayed if no other than the
internal clock source is configured.
5.2.2.4 Manual Timing Source Control

The SETS status dialog at the AP: /unit-x, Status - SETS - General allows you to read the status
of the SETS timing system and to temporarily override the automatic selection to debug and test
the NE timing:
• Clock Operation Type = Forced Holdover
• Clock Operation Type = Forced Free Run
See section 5.2.2.3 SETS Clock Operation Modes (on page 37).
5.2.2.5 Switch Commands

Perform a forced or manual switch to a specific timing source for the SETS at the AP: /unit-x,
Status - SETS - Sources:
• Forced switch:
Perform a forced switch to a specific timing source for the SETS.
The switch command is only accepted if the source is enabled, i.e. has a priority configured.
If the source is not available, i.e. failed or in WTR state, “Holdover” (SAMO1) or “<forced
clock source>” (SAMOx) is selected.

• Manual switch:
Perform a manual switch to a specific timing source for the SETS.
The switch command is only accepted if no forced switch is active and the source is avail-
able. The source is not available if it has been disabled or is failed or in WTR state.
5.2.2.6 Lockout Commands

Any of the available clock sources can be locked out from being selected by an automatic,
forced or manual switch request at the AP: /unit-x, Status - SETS - Sources.
5.2.3 SETS Protection

SETS equipment protection requires the implementation of two SAMO5 or two SAMO2 or two
SAMO3 units constituting an equipment protection pair. The two units must be plugged in pre-
defined paired slots. The unit in the left slot provides the working SETS circuit which is active
under regular operating conditions. The unit in the right slot provides the protecting SETS cir-
cuit.

The switchover from the working to the protecting unit and vice versa is not hitless
for the internal clock signals and thus may affect the synchronization and the traffic
signals.
For details of implementation, refer to [1KHW028668] User Manual “SAMO2, SAMO2-F,
SAMO3, SAMO5, SAMO5-F”.
Please note:
Two SAMO1 units constituting an equipment protection pair provide two indepen-
dent SETS functions.
5.2.4 SETS Fault Management

The generic fault management aspects of the FOX61x are handled in the FOX61x User Manual.
Please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
For the SDH synchronization fault management please refer to [1KHW002476] User Manual
“SAMO1” and refer to [1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5,
SAMO5-F”.
5.2.5 SETS Performance Management

The number and distribution of SETS timing source changes are available for the SDH service
units and can be checked with the unit Performance Management functions in the FOXCST
“Tree View” view at the AP: /unit-x, Performance Management.
5.3 PETS
The FOX61x provides one PETS instance per network element, located on the core unit. All
synchronous PDH ports, the synchronous Ethernet ports and the PTP timing are synchronized
to the plesiochronous equipment timing source (PETS).
A PDH network element with synchronous PDH traffic signal transport requires an equipment
timing source, called the PETS (Plesiochronous Equipment Timing Source). The timing charac-
teristics are according to ITU-T G.823.
An Ethernet network element supporting the synchronous Ethernet also requires an equipment
timing source, called the EETS (synchronous Ethernet equipment timing source). The timing
characteristics are according to ITU-T G.8262.

An Ethernet network element supporting the precision time protocol (PTP) requires an equip-
ment timing source, which is frequency and phase synchronized to the grand master clock.
The PETS of the FOX61x core unit is a hybrid PDH/SyncE/PTP network element function, i.e. it
is the common timing source for PDH, synchronous Ethernet and PTP. Timing characteristics
are according to ITU-T G.8262, while the PETS is still able to synchronize to timing sources with
a frequency tolerance of 9 ppm.
The PETS has three external clock input types (PDH-x, ESI-1 and ESI-2, PTP-x), one internal
clock source and provides two external clock output types (T0, ESO-1) as shown in the figure
below.
PETS
PDH-1
Selector A
PDH-2
PDH-3
PDH-4
NEC
Selector C
ESI-1/2 ESO-1
Selector B
NETG T0
PTP-1
PTP-2
PTP-3
PTP-4
PETS: Plesiochronous Equipment Timing Source

NEC: Network Element Clock
NETG: Network Element Timing Generator
T0: NE internal timing distribution
PDH-x: Timing signal derived from a PDH, SyncE or DSL signal, or from a SETS
ESI-1/2: Timing signal derived from a 2 MHz station clock signal
PTP-x: Timing signal derived from a PTP packet stream
ESO-1: Timing towards a 2 MHz station clock output signal
Figure 25: PETS functions
Please note:
The selector A in Figure 25 incorporates a PLL, maintaining an output clock during
the ESO-1 clock source holdoff time.
Please note:
The ESI-2 input in Figure 25 usable for the PETS is only available on the CESM1
and CESM2 core unit.
The timing sources PDH-x, ESI-x and PTP-x are explained in section 5.3.1 Timing Sources (on
page 41).
T0 is the synchronization signal used for the network element internal synchronization. T0 is dis-
tributed to all service units via the PDH clock line of the PBUS.
For a description of ESO-1 see section 5.6 External Synchronization Output ESO-1 (on
page 53).

The PETS function is implemented on the core unit. However, the synchronization function is a
network element function and hence most management functions are located on the NE access
point.
The synchronization functions of a FOX61x network element are located in the FOXCST “Syn-
chronization” view. For a description of the FOXCST “Synchronization” view see section 8.2 AP:
/ Synchronization (on page 153).
The FOXCST “Synchronization” view presents the following Access Points:
• AP: /Synchronization/SyncE, Ports - Port Configuration,
• AP: /Synchronization/SyncE, Ports - Port Status,
• AP: /Synchronization/PTP, Ports & Streams - Port Configuration,
• AP: /Synchronization/PTP, Ports & Streams - Stream Configuration,
• AP: /Synchronization/PTP, Ports & Streams - Port Status,
• AP: /Synchronization/PTP, Ports & Streams - VLAN Configuration,
• AP: /Synchronization/PTP, Ports & Streams - VLAN Status,
• AP: /Synchronization/PTP, Ports & Streams - PTP Status,
• AP: /Synchronization/PTP, Ports & Streams - Stream Status,
• AP: /Synchronization/PTP, Configuration,
• AP: /Synchronization/PTP, Status,
• AP: /Synchronization/PTP, Alarms,
• AP: /Synchronization/PTP, Alarm Status,
• AP: /Synchronization/PTP, Alarm Configuration,
• AP: /Synchronization/PETS, Configuration,
• AP: /Synchronization/PETS, Status,
• AP: /Synchronization/PETS, Alarms,
• AP: /Synchronization/PETS, Alarm Status,
• AP: /Synchronization/PETS, Alarm Configuration,
• AP: /Synchronization/ESO, Configuration,
• AP: /Synchronization/ESO, Status.
• AP: /Synchronization/ESO, Alarms,
• AP: /Synchronization/ESO, Alarm Status,
• AP: /Synchronization/ESO, Alarm Configuration.
The ESI fault management functions of a FOX61x network element are located at the following
Access Points of the FOXCST “Tree View”:
• AP: /unit-11 or /unit-13/sync/esi-1, Fault Management (CESM3),
• AP: /unit-11 or /unit-13/sync/esi-2, Fault Management (CESM3),
• AP: /unit-11 or /unit-13/neController/esi-1, Fault Management (CESM1 or CESM2),
• AP: /unit-11 or /unit-13/neController/esi-2, Fault Management (CESM1 or CESM2).
For a description of the above management functions see section 8 User Interface Reference
(on page 147).
5.3.1 Timing Sources

Synchronous applications require the synchronization of the PETS to a PRC (primary reference
clock) derived timing signal. The synchronization signal can be fed to the network element
through one of the following interfaces:

up to 4 PDH clock sources up to 4 PTP

from service or core units clock sources
DATI1 (SHDSL NT, Trunk To LT) PETS Core Unit

PTP from Eth
port or VLAN
clock clock NEC
Selector
recovery recovery clock to PBUS
NETG
SHDSL SHDLSL SHDSL P12

port processing processing
internal
Selector
DATI1 (SHDSL LT, Trunk To NT)
Selector
clock
clock
recovery
clock
recovery clock from clock to clock to
esi-1/2 eso-1 Eth Tx
SHDSL SHDLSL SHDSL P12
port processing processing Front Front Front Front
interface interface interface interface
Eth receive esi-1/2 eso-1 Eth transmit
DEFM1 (SHDSL NT)
clock Synchronous Ethernet Synchronous Ethernet or PTP
recovery
SAMO1 (STM-4/STM-1)
SHDSL SHDLSL SHDSL Ethernet
port processing processing SETS
clock
recovery
LEDE1 or CEPI1 (E1) clock
recovery P12 SDH SDH STM-4/1
processing multiplexer port
E1 E1 P12
port processing
SAMOx (STM-16/STM-4/STM-1)
CEPI1 (CESoP) SETS

TCXO clock
recovery
clock
recovery P12 SDH SDH STM-16/4/1
processing multiplexer port
PBUS
GbE GbE Pseudo Wire P12

star processing processing PDH clock source
PTP clock source
ESI or internal clock source
PETS timing
ESO timing
Figure 26: PETS clock sources
5.3.1.1 PDH Clock Sources

The PDH clock sources of Figure 26 are the synchronization signals derived from different
sources. Up to 4 PDH clock sources can be configured and selected for the PETS synchroniza-
tion. The administrative state of a PDH clock source must be up to be selectable.
The following timing sources are available:
• E1 port according to ITU-T G.703 on a LEDE1 or CEPI1 unit.
The E1 signal is connected to one of the E1 ports on the LEDE1 or CEPI1 unit. The E1 port
transporting the timing information must be operated in one of the following termination
modes:
− Transparent,
− PCM30, PCM30C,

− PCM31, PCM31C,
− V5 Uplink, V5 Uplink NCI.
The E1 port as a PDH clock source is identified as e.g. /unit-5/port-1.
• P12 data signal according to ITU-T G.704, transported in an SDH signal on a SAMO1 or
SAMOx unit.
The P12 signal is demapped from an SDH virtual container VC-12. The P12 signal transport-
ing the timing information must be operated in one of the following termination modes:
− Transparent,
− PCM30, PCM30C,
− PCM31, PCM31C,
The P12 data signal as a PDH clock source is identified as e.g. /unit-4/pdh/vc12-1/p12.

A P12 signal demapped from an SDH signal is impaired with demapping jitter and
pointer adjustment jitter.
→ It is not recommended to use a demapped P12 as PDH clock source.
Please note:
On the SAMO1 unit only the P12 signals from vc12-1 to vc12-4 can be selected as
PDH clock source.
→ The vc12-5 to vc12-67 are not selectable as PDH clock source.
Please note:
On the SAMOx unit only the P12 signals from vc12-1 to vc12-4 can be selected as
PDH clock source.
→ The vc12-5 to vc12-64 are not selectable as PDH clock source.
• P12 data signal according to ITU-T G.704, transported via a circuit emulation service on a
CEPI1 unit.
The timing interface to the packet network is a 1 GbE or 10 GbE signal.
The 1 GbE or 10 GbE signal is connected to one of the Ethernet trunk ports on the core unit
or to any port of an Ethernet service unit participating in the FOX61x Switch.
The CEPI1 Pseudo Wire transporting the timing information must be operated in the adap-
tive clock recovery mode (AP: /unit-x/pw/[p12-c/]pw-y, Configuration - CET) and use one of
the following termination modes (AP: /unit-x/pw/pw-y, Configuration - SAToP or AP: /unit-x/
pw/p12-c, Configuration - Termination):
− Transparent,
− PCM30, PCM30C,
− PCM31, PCM31C,
− PCMnn, PCMnn_CAS,
The Pseudo Wire as a PDH clock source is identified as e.g. /unit-5/pw/pw-1.
• P12 data signal according to ITU-T G.704, transported via a DSL link on a DATI1 unit.
The P12 signal is demapped from an SHDSL trunk signal. The trunk mode can be “Trunk To
LT” or “Trunk To NT”, the “Clock Over Payload” parameter must be set to “true”. The P12
signal transporting the timing information must be operated in one of the following termina-
tion modes:
− Transparent,
− Structured, Structured With CAS,
The P12 data signal as a PDH clock source is identified as e.g. /unit-8/logports/logport-1/
trunk.

• DSL link on a DATI1 or DEFM1 unit.

The SHDSL signal is connected to one of the SHDSL ports on the DATI1 or DEFM1 unit.
The PDH timing is derived from the NT function of an SHDSL signal.
On the DATI1 unit the logport must be configured to the “Trunk To LT” mode, the “Clock
Over Payload” parameter must be set to “false”.
On the DEFM1 unit the port termination mode must be configured to “NT”.
The SHDSL signal as a PDH clock source is identified as e.g. /unit-8/logports/logport-1/trunk
(DATI1) or /unit-7/port-1 (DEFM1).
• SETS function on an SAMO1 or SAMOx unit.
To synchronize the PETS to the SETS timing of an SDH service unit, the SDH service unit
must be selected as a PDH clock source in the PETS configuration.
Please note:
→ In the PETS and ESO configuration on the NE the working and protecting
SAMO1 units are available as PDH clock sources.
Please note:
Two SAMO5 or two SAMO2 or two SAMO3 units constituting an equipment protec-
tion pair provide one protected SETS function.
→ In the PETS and ESO configuration on the NE only the working SAMOx unit is
available as PDH clock source.
The SETS of an SDH service unit as a PDH clock source is identified as e.g. /unit-4.
• Synchronous Ethernet data signal on a core unit.
The Ethernet signal is connected to one of the Ethernet front ports on the core unit. The tim-
ing interface to the synchronous Ethernet is a 100BASE-x, 1000BASE-x or 10GBASE-x sig-
nal.
The Synchronous Ethernet signal as a PDH clock source is identified as e.g. /unit-11/port-1.

An electrical SFP based Ethernet port (operating in 1000BASE-T mode) does not
support synchronous Ethernet.
Please note:
Only two of the three electrical Ethernet interfaces (port-3 to port-5) on the CESM1
unit can be selected as PETS clock sources at the same time.
Please note:
Only two of the three 1 Gbit/s Ethernet interfaces (port-3 to port-5) on the CESM2
The transmit clock of the Ethernet ports supporting the synchronous Ethernet are synchro-
nized to the PETS timing.
• TCXO on a CEPI1 unit.
To synchronize the PETS to the CEPI1 unit internal TCXO, the CEPI1 unit must be selected
as a PDH clock source.
The TCXO of a CEPI1 unit as a PDH clock source is identified as e.g. /unit-2.
Please note:
The TCXO on the CEPI1 unit provides a timing signal with similar quality as the
CESM1 and CESM2 core unit internal oscillator. If no PRC derived timing signal is
available the PETS can be synchronized to the core unit internal oscillator or to the
TCXO of the CEPI1 unit.

Please note:
The CESM3 core unit has an OCXO as internal oscillator which provides a higher
quality timing signal than the TCXO on the CEPI1 unit.
5.3.1.2 PTP Ordinary or Boundary Clock Sources

A PTP Ordinary or Boundary Clock is available as PETS clock source if the PTP mode is config-
ured to “Frequency And Phase” or to “Pure Hybrid”:
• Frequency And Phase (frequency and phase are derived from PTP):
The PTP-1 to PTP-4 clock sources are available in the PETS clock source table. The PDH
clock sources are not available.
When selecting the ESI-1, ESI-2 or Internal clock source the PETS phase will be free run-
ning.
• Pure Hybrid (frequency is derived from SyncE, phase is derived from PTP):
The PTP clock source is not visible in the PETS clock source table. The PTP clock source is
implicitly selected when the linked SyncE port is selected as PDH clock source.
The Ethernet signal is connected to one of the Ethernet front ports on the core unit. The timing
interface to a PTP clock master is a 100BASE-x, 1000BASE-x or 10GBASE-x signal.
The Ethernet port must be selected as a PTP source in the PTP configuration in the FOXCST
“Synchronization” view at the AP: /Synchronization/PTP, Configuration: e.g. PTP-1: /unit-11/
port-1.

The optical 1 Gbit/s Ethernet interfaces on the CESM1 or CESM2 (port-1 and port-
2) unit cannot be used as PTP sources.
→ Use the 10 Gbit/s SFP-based interfaces instead.
The timing output interface to a PTP clock slave is synchronized to the PETS frequency, and
possibly phase.

With PTP only one synchronization path direction is active. This is the forward path
(Master to Slave).
→ The PTP quality level information in reverse direction (Slave to Master) is not
applicable.

The WAN port extension unit EPEX1 supports the VLAN Master and VLAN slave
modes. There is no support for port based PTP boundary clock.

QL with PTP using the “Frequency And Phase” PTP mode is not supported in ring
networks.
→ QL with PTP in ring networks is only supported with the “Pure Hybrid” PTP
modes, i.e. the PETS frequency is derived from a synchronous Ethernet port
and the PETS phase is derived from PTP.
→ The QL used for the clock selection algorithm is taken from the synchronous
Ethernet port.
PTP ports are available on the core unit and on the WAN port extension unit EPEX1. Please
refer to [1KHW028774] User Manual “CESM3”, [1KHW028642] User Manual “CESM2, CESM2-
F”, [1KHW002469] User Manual “CESM1, CESM1-F” or [1KHW029154] User Manual “EPEX1”.

5.3.1.3 PTP Transparent Clock

The FOX61x supports the end-to-end transparent clock. Transparent clocks in the FOX61x can-
not be used as clock source.
Please note:
The FOX61x supports the simultaneous usage of a port as Ordinary Clock or
Boundary Clock, and Transparent Clock.
→ A VLAN based PTP stream can be used to synchronize the local network ele-
ment and can be forwarded transparently to other network elements.
5.3.1.4 ESI-1 and ESI-2 Clock Sources

The ESI-1/2 timing sources of Figure 26 are the synchronization signals from external 2048 kHz
clock inputs.
The core unit provides 2 external 2048 kHz clock inputs ESI-1 and ESI-2. The core unit selects
the ESI-1 and/or ESI-2 to be used for the PETS synchronization.
Please note:
The ESI-2 used for the PETS synchronization is only available on the CESM1 or
CESM2 unit.
Please note:
The ESI-1 (or ESI-2) port is enabled when a clock priority is assigned to it in the
PETS configuration.
→ The esi-z managed object on the core unit is activated.
→ The fault management of the esi-z managed object on the core unit is activated.
The timing interface is a 2048 kHz clock signal according to ITU-T G.703.
The ESI-1 (or ESI-2) must be enabled in the PETS configuration in the FOXCST “Synchroniza-
tion” view at the AP: /Synchronization/PETS, Configuration.
5.3.1.5 Internal Clock Source

The NEC internal reference clock on the core unit has an accuracy of ± 4.6 ppm according to
ITU-T G.813 (clause 5, option 1).
NEC is a collective term standing for Network Equipment Clock, where the NEC plays at the
same time the roles of a
• EEC, (synchronous) Ethernet Equipment Clock,
• PEC, Packet-based Equipment Clock, and
• PDH Equipment Clock.
5.3.2 Timing Source Selection
5.3.2.1 Selection Algorithm

From the available PETS clock sources the PETS autonomously selects the clock source with
the best clock quality. The FOX61x supports two approaches to define the clock quality:
(AP: /Synchronization/PETS, Configuration: Selection Algorithm = Priority):
The PETS selection process is only controlled by the priority.

(AP: /Synchronization/PETS, Configuration: Selection Algorithm = QL):
the selection.
The PETS selection process first considers the QL and then the Priority.
5.3.2.2 PETS Clock Source Selection

To make a PETS clock source available it must be given a priority between 1 and 7 in the PETS
clock selection configuration dialog in the FOXCST “Synchronization” view at the AP: /Synchro-
nization/PETS, Configuration.
Depending on the synchronization application the following steps have to be performed:
• Frequency synchronization without PTP:
− Set the managed object of the PDH clock sources to the administrative state “up”, e.g. set
an E1 port of a LEDE1 unit or an Ethernet port of a core unit to the administrative state
“up”.
− Configure up to 4 PDH clock sources.
− In the “PETS Clock Selection” table configure the priority of the PDH clock sources.
• Frequency and phase synchronization with PTP:
− In the AP: /Synchronization/PTP, Configuration set the PTP Mode to “Frequency And
Phase”.
− In the AP: /Synchronization/PTP, Ports & Streams set the PTP Mode of the used ports or
VLANs to “Ordinary/Boundary Clock”. Add a PTP stream.
− Set the managed object of the PTP clock sources to the administrative state “up”, e.g. set
an Ethernet port of a core unit to the administrative state “up”.
− In the AP: /Synchronization/PTP, Configuration select the PTP sources, e.g. /unit-11/port-
1 or VLAN-100.
− In the “PETS Clock Selection” table configure the priority of the PTP clock sources.
• Frequency and phase synchronization with SyncE and PTP:
− In the AP: /Synchronization/PTP, Configuration set the PTP Mode to “Pure Hybrid”.
− In the AP: /Synchronization/PTP, Ports & Streams set the PTP Mode of the used ports to
“Ordinary/Boundary Clock”. Add a PTP stream.
− Set the managed object of the SyncE and PTP clock sources to the administrative state
“up”, e.g. set an Ethernet port of a core unit to the administrative state “up”.
− Configure up to 4 PDH clock sources using the SyncE ports.
− In the “PETS Clock Selection” table configure the priority of the PDH clock sources.
When using the selection algorithm “QL” the QL parameter of the PETS clock sources must be
Plesiochronous PDH and Ethernet applications can rely on a free running PETS. The PETS can
use one of the following sources:
• Core unit internal clock oscillator,

• TCXO on the CEPI1 unit,

• SETS on the SAMO1 unit (configured to internal),
• SETS on the SAMOx unit (configured to internal).
5.3.2.3 PETS Clock Operation Modes

There are five clock operation modes for the PETS in the FOX61x according to ITU-T G.813:
• Locked
Normal operation mode. The output PETS clock signal is frequency controlled by an external
input reference, so they have the same long term average frequency. The PTP mode is dis-
abled.
• Frequency-Locked
Normal operation mode, a PTP mode is enabled. The output PETS clock signal is frequency
controlled by an external input reference, so they have the same long term average fre-
quency.
• Phase-Locked
Normal operation mode. The output PETS clock signal is frequency and phase controlled by
an external input reference, so they have the same long term average frequency and phase.
Please note:
It can take several minutes until a clock reaches the phase-locked state.
• Holdover
If all configured clock sources fail, the PETS will continue operating but in holdover mode.
This operation mode functions with previously stored clock data, acquired during “Locked”
operation mode.
You can also bring the PETS into this mode with the PETS clock operation command
“Forced Holdover” (AP: /Synchronization/PETS, Status).
Please note:
The alarm PHO (PETS Holdover) is not activated during a forced holdover.
• Free running
If the PETS does not have a clock reference input, it determines its output clock by an inter-
nal default reference frequency. Note that the clock operating mode shows “Free Running”
together with the selected clock source “Internal”.
You can also bring the PETS into this mode with the PETS clock operation command
“Forced Free Running” (AP: /Synchronization/PETS, Status).
In the “Auto Selection” mode, the PETS selects its operation mode by itself, depending on the
conditions given by the availability of synchronization sources.
To-Restore Time”:
• Holdoff Time
When a clock source fails the PETS will go to the holdover mode for the configured holdoff
source.
When the PETS is operating with a low priority clock source and a previously failed higher
priority clock source becomes available again, the PETS waits for the wait-to-restore time
source.

PDH clock source 1

Priority 1
available
failed
time
PDH clock source 2
Priority 2
available
failed
time
Internal clock
Priority 7 or Disabled
available
disabled
time
Selected holdoff time clock holdoff time clock wait-to-restore wait-to-restore

clock source 1 2 time clock 2 time clock 1
clock source 1 clock source 2 internal clock source 2 clock source 1
time
Clock operating
mode
locked holdover locked holdover locked locked
time
Figure 27: PETS clock source selection with 2 external and optionally 1 internal clock sources
5.3.2.4 Manual Timing Source Control

The PETS status dialog at the AP: /Synchronization/PETS, Status allows you to read the status
of the PETS timing system and to temporarily override the automatic selection to debug and test
the NE timing:
• Clock Operation Type = Forced Holdover
• Clock Operation Type = Forced Free Run
See section 5.3.2.3 PETS Clock Operation Modes (on page 48).
5.3.3 PETS Protection

The equipment protection for the core unit provides at the same time the PETS equipment pro-
tection.
Only the PETS function of the active core unit provides the timing signals for the network ele-
ment and the external synchronization outputs.
For details on the protection of the core unit refer to [1KHW002469] User Manual “CESM1,
CESM1-F” or refer to [1KHW028642] User Manual “CESM2, CESM2-F” or refer to
[1KHW028774] User Manual “CESM3”.
5.3.4 PETS Fault Management

For a description of the PTP and PETS synchronization alarms please refer to [1KHW002464]
User Manual “FOX615 R2/FOX615/FOX612/FOX611”.

5.3.5 PETS Performance Management

The number and distribution of PTP stream messages can be checked with the PTP stream
User Counter and History functions in the FOXCST “Synchronization” view at the following
access points:
• AP: /Synchronization/PTP, Ports & Streams - Port,
• AP: /Synchronization/PTP, Ports & Streams - Port Stream,
• AP: /Synchronization/PTP, Ports & Streams - VLAN Stream.

5.4 SETS and PETS Interoperability
SAMO1 or SAMOx SETS clock

SETS to STM Tx Front interfaces
SEC STM transmit
Selector
SETG
SETS clock to PDH clock sources
up to 4 or 8 internal
Front *
clock
Selector
STM clocks
Selector
interfaces clock to eso-2
STM receive
* internal clock, esi-2, and
PDH clock sources are avail-
able as eso-2 sources only up to 4 PDH clock sources
on the SAMO1 unit esi-2 clock source
Core Unit
Front clock from Eth Rx
interface
Eth receive
up to 4 PTP esi-2 clock
clock sources
PTP port
PETS up to 4 PDH
clock sources
PTP VLAN NEC
PETS clock to PBUS
Selector
*
NETG
Front esi-2 clock
interface PTP VLAN
esi-2 esi-1 clock
Front PTP port
interface
PBUS
esi-1 internal
Selector
clock
Selector
*
esi-2 clock
esi-1 clock
PETS
clock to clock to clock to
eso-1 Eth Tx eso-2
* esi-2 is available as a PETS Front Front Front
clock source only for CESM1 interface interface interface
and CESM2 eso-1 Eth transmit eso-2
PDH clock source ESI or internal clock source PETS timing SETS timing
SDH clock source PTP clock source ESO timing
Figure 28: SETS and PETS implementation in FOX61x
Timing signals are exchanged between the FOX61x units via the subrack backplane:
• 2 lines for the ESI timing, one line accessed by the active core unit, the other line accessed
by the standby core unit, and used by any service unit. These lines have a dedicated drive
access, i.e. only one unit can drive the line.
• 1 line for the ESO-2 timing, driven by an SDH service unit and used by the active and
standby core units. This line has a shared drive access, i.e. the access is controlled by the

NE management with the configuration of an SDH service unit that is used as ESO-2 clock
source.
In case of a failure on the SDH service unit the ESO-2 clock output is squelched.
• 4 lines for the PDH clock sources, driven by a service or a core unit and used by any unit
having a PETS or SETS function. These lines have a shared drive access, i.e. the access is
controlled by the NE management.
The synchronization system of the FOX61x can operate in the following modes:
• The PETS and SETS functions can be operated autonomously. There is no synchronization
between the SDH and the PDH equipment parts.
• The PETS function can be synchronized to one of the available SETS functions. The PDH
equipment timing is synchronized to the SDH equipment timing.
The PDH clock source in the PETS configuration is configured to the SETS of an SDH ser-
vice unit, e.g. /unit-5.
Please note:
→ In the PETS and ESO configuration on the NE the working and protecting
SAMO1 units are available as PDH clock sources.
Please note:
→ In the PETS and ESO configuration on the NE only the working SAMOx unit is
available as PDH clock source.
• The SETS functions of several SDH units can be synchronized. The SDH equipment timing
uses one common clock source.
The SETS timing is distributed inside the FOX61x via one of the PDH clock source lines, i.e.
the PETS is configured to the SETS of one SAMO1 or SAMOx unit, and the other SAMO1 or
SAMOx units select this PDH clock source in the SDH clock selection configuration.
Please note:
It is not possible to directly synchronize a SETS function to the PETS.
→ In order to have the SETS synchronous to the PETS use the same PDH clock
source for the PETS and the SETS functions.
5.5 External Synchronization Inputs ESI-1 and ESI-2

The FOX61x network element provides 2 external clock inputs ESI-1 and ESI-2 on the front of
the core unit. The inputs are implemented as 2048 kHz timing interfaces according to ITU-T
G.703.
5.5.1 ESI-1 Input

The ESI-1 input can be used as clock source for the PETS function.
Please note:
The ESI-1 port is enabled when a clock priority is assigned to it in the PETS or
ESO-1 configuration.
→ The fault management of the esi-1 managed object on the core unit is activated.

5.5.2 ESI-2 Input

The ESI-2 input can be used as clock source for the SETS function.
On the CESM1 and CESM2 core unit the ESI-2 input can also be used as clock source for the
PETS function.
Please note:
vated.
Please note:
The ESI-2 port on the CESM1 and CESM2 core units is enabled when a clock pri-
ority is assigned to it in the SETS or ESO configuration on an SDH service unit.
→ The esi-2 managed object on the core unit is not activated.
vated.
Please note:
The ESI-2 port is enabled when a clock priority is assigned to it in the PETS or
ESO-1 configuration.
→ The fault management of the esi-2 managed object on the core unit is activated.
5.5.3 ESI-1 and ESI-2 Protection

The equipment protection for the core unit provides at the same time the ESI-1 and ESI-2 equip-
ment protection.
Only the ESI inputs of the active core unit provide the timing signals for the PETS or SETS.
5.6 External Synchronization Output ESO-1

The FOX61x network element provides the external clock output ESO-1 on the front of the core
unit. The output is implemented as 2048 kHz timing interfaces according to ITU-T G.703.
The ESO-1 output can be used as clock output of the PETS function. The ESO-1 management
functions are located at the AP: /Synchronization/ESO.
5.6.1 ESO-1 Timing Modes

The ESO-1 has two modes of operation with significant differences for the timing signal:
• ESO-1 PETS-Locked:
The selector C in Figure 25: "PETS functions" (on page 40) selects the NETG as output for
ESO-1. The output clock signal is identical to the PETS timing signal.

• ESO-1 non PETS-Locked:

The selector C in Figure 25: "PETS functions" (on page 40) selects the selector A as output
for ESO-1. The output clock signal is identical to the selected clock source of selector A. This
mode is used for the filtering of the timing signal with an external SSU equipment.
5.6.2 ESO-1 Timing Sources

In the ESO-1 PETS-Locked mode the output signal is selected by selector B of the NEC func-
tion.
In the ESO-1 non PETS-Locked mode the output signal is selected by selector A from the fol-
lowing clock sources:
• PDH Clock Source 1 to 4
See section 5.3.1.1 PDH Clock Sources (on page 42) for the available PDH clock source sig-
nals.
• ESI-1 and ESI-2
See section 5.3.1.4 ESI-1 and ESI-2 Clock Sources (on page 46) for the available ESI clock
source signals.
• Internal
See section 5.3.1.5 Internal Clock Source (on page 46) for a description of the PETS internal
clock source signal.
5.6.3 ESO-1 Timing Source Selection PETS-Locked Mode
5.6.3.1 Selection Algorithm ESO-1

In the ESO-1 PETS-Locked mode the ESO-1 clock output signal is locked to the PETS timing
generator.
ESO-1 can be squelched for specific clock sources.
ESO-1 can be squelched for specific quality level values.
5.6.3.2 ESO-1 Clock Operation Modes

There are five clock operation modes for the ESO-1 in the FOX61x according to ITU-T G.813:
• Locked
Normal operation mode. The ESO-1 clock output signal is frequency controlled by the PETS
which is controlled by an external input reference, so they have the same long term average
frequency.
• Holdover
If all configured clock sources of the PETS fail, ESO-1 will continue operating but in holdover
mode. This operation mode functions with previously stored clock data, acquired during
“Locked” operation mode.
• Free running
If the PETS does not have a clock reference input, it determines its output clock by an inter-
nal default reference frequency. Note that the clock operating mode of the ESO-1 shows
“Free Running” together with the selected clock source “Internal”.
• Acquiring
The PETS is in a transient state when e.g. a clock source has recovered.
• Squelched
The selected PETS clock source has been squelched or the QL value of the selected PETS
clock source has been squelched.

5.6.4 ESO-1 Timing Source Selection Non PETS-Locked Mode

In the ESO-1 non PETS-Locked mode the output signal is selected autonomously from the
available ESO-1 clock sources, selecting the clock source with the best clock quality. The FOX-
61x supports two approaches to define the clock quality:
(AP: /Synchronization/ESO, Configuration: ESO-1 Selection Algorithm = Priority):
The ESO-1 selection process is only controlled by the priority.
(AP: /Synchronization/ESO, Configuration: ESO-1 Selection Algorithm = QL):
the selection.
The ESO-1 selection process first considers the QL and then the Priority.
5.6.4.2 ESO-1 Clock Source Selection

To make a ESO-1 clock source available it must be given a priority between 1 and 7 in the
ESO-1 clock selection configuration dialog in the FOXCST “Synchronization” view at the AP: /
Synchronization/ESO, Configuration.
When using the selection algorithm “QL” the QL parameter of the PETS clock sources must be

There are five clock operation modes for the ESO-1 in the FOX61x according to ITU-T G.813:
• Locked
Normal operation mode. The ESO-1 clock output signal is frequency controlled by an exter-
nal input reference, so they have the same frequency.
• Holdover
The active clock source of the ESO-1 fails, but the holdoff time has not yet expired. The
ESO-1 will continue operating but in holdover mode. This operation mode functions with pre-
viously stored clock data, acquired during “Locked” operation mode.
• Free running
The ESO-1 is synchronized to the internal clock source. Note that the clock operating mode
shows “Free Running” together with the selected clock source “Internal”.
• Acquiring
The ESO-1 is in a transient state when e.g. a clock source has recovered.

• Squelched
All ESO-1 clock sources have failed and the holdoff time has expired, or the QL value of the
selected ESO-1 clock source has been squelched.
To-Restore Time”:
• Holdoff Time
When a clock source fails the ESO-1 will go to the holdover mode for the configured holdoff
source.
When the ESO-1 is operating with a low priority clock source and a previously failed higher
priority clock source becomes available again, the ESO-1 waits for the wait-to-restore time
source.
5.6.5 ESO-1 Protection

The equipment protection for the core unit provides at the same time the ESO-1 equipment pro-
tection.
Only the active core unit provides the timing signal for the external synchronization outputs.
5.6.6 ESO-1 Fault Management

For a description of the ESO-1 synchronization alarms please refer to [1KHW002464] User
Manual “FOX615 R2/FOX615/FOX612/FOX611”.
5.7 External Synchronization Output ESO-2

The FOX61x network element provides the external clock output ESO-2 on the front of the core
unit. The output is implemented as 2048 kHz timing interfaces according to ITU-T G.703.
The ESO-2 output can be used as clock output of a SETS function of a SDH service unit. The
ESO-2 management functions are located on the SDH service unit at the AP: /unit-x. The selec-
tion which SDH service unit feeds the ESO-2 output on the core unit is located at the AP: /Syn-
chronization/ESO.
5.7.1 ESO-2 Timing Modes

The ESO-2 has two modes of operation with significant differences for the timing signal:
• ESO-2 SETS-Locked:
The selector C in Figure 23: "SETS functions" (on page 34) selects the SETG as output for
ESO-2. The output clock signal is identical to the SETS timing signal.
• ESO-2 non SETS-Locked:
The selector C in Figure 23: "SETS functions" (on page 34) selects the selector A as output
for ESO-2. The output clock signal is identical to the selected clock source of selector A. This
mode is used for the filtering of the timing signal with an external SSU equipment.

5.7.2 ESO-2 Timing Sources

In the ESO-2 SETS-Locked mode the output signal is selected by selector B of the SEC func-
tion.
In the ESO-2 non SETS-Locked mode the output signal is selected by selector A from the fol-
lowing clock sources:
• SDH Clock Source 1 to 4 (SAMO1 and unprotected SAMOx unit) or 1 to 8 (protected
SAMOx unit)
See section 5.2.1.1 SDH Clock Sources (on page 35) for the available SDH clock source sig-
nals.
• PDH Clock Source 1 to 4 (SAMO1 unit only)
See section 5.3.1.1 PDH Clock Sources (on page 42) for the available PDH clock source sig-
nals.
• ESI-2 (SAMO1 unit only)
See section 5.2.1.3 ESI-2 Clock Source (on page 36) for the available ESI clock source sig-
nal.
• Internal (SAMO1 unit only)
See section 5.2.1.4 Internal Clock Source (on page 36) for a description of the SETS internal
clock source signal.
5.7.3 ESO-2 Timing Source Selection SETS-Locked Mode
Please note:
→ In the ESO-2 configuration on the NE the working and protecting SAMO1 units
are available as PDH clock sources.
Please note:
→ In the ESO-2 configuration on the NE only the working SAMOx unit is available
as PDH clock source.

In the ESO-2 SETS-Locked mode the ESO-2 clock output signal is locked to the SETS timing
generator.
ESO-2 can be squelched for specific clock sources.

There are two clock operation modes for the ESO-2 in the FOX61x according to ITU-T G.813:
• Locked
Normal operation mode. The ESO-2 clock output signal is frequency controlled by the SETS
which is controlled by an external input reference, so they have the same long term average
frequency.
If the active clock source of the SETS fails, but the holdoff time has not yet expired, the
ESO-2 will continue operating with previously stored clock data.
• Squelched
The selected SETS clock source has been squelched or the QL value of the selected SETS
clock source has been squelched.

5.7.4 ESO-2 Timing Source Selection Non SETS-Locked Mode
Please note:
→ In the ESO-2 configuration on the NE the working and protecting SAMO1 units
are available as PDH clock sources.
Please note:
→ In the ESO-2 configuration on the NE only the working SAMOx unit is available
as PDH clock source.

In the ESO-2 non SETS-Locked mode the output signal is selected autonomously from the
available ESO-2 clock sources, selecting the clock source with the best clock quality. The FOX-
61x supports two approaches to define the clock quality:
(AP: /unit-x, Configuration - ESO-2: Selection Algorithm = Priority):
The ESO-2 selection process is only controlled by the priority.
(AP: /unit-x, Configuration - ESO-2: Selection Algorithm = QL):
the selection.
The ESO-2 selection process first considers the QL and then the Priority.
5.7.4.2 ESO-2 Clock Source Selection

To make a ESO-2 clock source available it must be given a priority between 1 and 14 in the
ESO-2 clock selection configuration dialog at the AP: /unit-x, Configuration - ESO-2.
When using the selection algorithm “QL” the QL parameter of the SETS clock sources must be

There are two clock operation modes for the ESO-2 in the FOX61x:

• Active
Normal operation mode. The ESO-2 clock output signal is frequency controlled by an exter-
nal input reference, so they have the same frequency.
If the active clock source of the ESO-2 fails, but the holdoff time has not yet expired, the
ESO-2 will continue operating with previously stored clock data.
• Squelched
All ESO-2 clock sources have failed and the holdoff time has expired, or the QL value of the
selected ESO-2 clock source has been squelched.
To-Restore Time”:
• Holdoff Time
When a clock source fails the ESO-2 will remain active for the configured holdoff time (con-
figured for the failed clock source) before switching to the next lower priority clock source.
When the ESO-2 is operating with a low priority clock source and a previously failed higher
priority clock source becomes available again, the ESO-2 waits for the wait-to-restore time
source.
5.7.5 Manual Timing Source Control
5.7.5.1 Switch Commands

Perform a forced or manual switch to a specific timing source for the ESO-2 at the AP: /unit-x,
Status - ESO-2 - Sources:
• Forced switch:
Perform a forced switch to a specific timing source for the ESO-2.
The switch command is only accepted if the source is enabled and has a priority configured.
If the source is not available, i.e. failed or in WTR state, the ESO-2 signal status is “Active”.
• Manual switch:
Perform a manual switch to a specific timing source for the ESO-2.
5.7.5.2 Lockout Commands

forced or manual switch request at the AP: /unit-x, Status - ESO-2 - Sources.
5.7.6 ESO-2 Protection

The equipment protection for the ESO-2 output is related to the
• equipment protection of the SDH service unit, and
• equipment protection of the core unit.
The equipment protection for the SAMO1 unit does not provide the ESO-2 protection since the
SETS end ESO-2 functions operate independently on the two SAMO1 units. In the AP: /Syn-
chronization/ESO, Configuration dialog only one of the two protected SAMO1 units can be
selected.
For details on the protection of the SAMO1 unit refer to [1KHW002476] User Manual “SAMO1”.
The equipment protection for the SAMOx unit provides the ESO-2 protection since the SETS
end ESO-2 functions are also equipment protected on the two SAMOx units. In the AP: /Syn-
chronization/ESO, Configuration dialog the (protected) SAMOx units can be selected.

For details on the protection of the SAMOx unit refer to [1KHW028668] User Manual “SAMO2,
SAMO2-F, SAMO3, SAMO5, SAMO5-F”.
The equipment protection for the core unit provides at the same time the ESO-2 equipment pro-
tection.
Only the active core unit provides the timing signal for the external synchronization outputs.
Please note:
When using core unit redundancy the ESO-1 and ESO-2 synchronization output
interfaces are squelched on the standby core unit.
→ The ESO-1 and ESO-2 interfaces can only be enabled on the active core unit.
5.7.7 ESO-2 Fault Management

For a description of the ESO-2 synchronization alarms please refer to [1KHW002476] User
Manual “SAMO1” or refer to [1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3,
SAMO5, SAMO5-F”.
5.7.8 ESO-2 Performance Management

The number and distribution of ESO-2 timing source changes are available for the SDH service
units and can be checked with the unit Performance Management functions in the FOXCST
“Tree View” view at the AP: /unit-x, Performance Management.
5.8 Quality Level Handling
5.8.1 Quality Level Handling in FOX61x
5.8.1.1 Quality Level with SSM

The QL (Quality Level) information for synchronization purposes is a part of the SSM (Synchro-
nization Status Message) signaling system for PDH, SDH, DSL, and synchronous Ethernet
(SyncE) traffic signals.
In the FOX61x separate processes handle the QL information of the timing signal sources. The
SETS and PETS system can use the QL of a clock source as one of the parameters for the
selection of their reference timing source.
It is possible to manually override the QL of a clock source (see section 5.8.3.2 Quality Level
Override (on page 63) or to modify the QL information of an SDH or SyncE clock source via
mapping tables (see section 5.8.3.1 Quality Level Input and Output Mapping (on page 63)). If
the incoming signal provides no QL information, a default QL will be assigned to these signals.
The FOXCST allows you to assign QL values from 1 to 15.
For more information about the SSM see section 4.3.2 Quality Level Based (on page 22).
5.8.1.2 Quality Level with SSI

For PDH signals the Hitachi Energy proprietary synchronization status indication (SSI) can be
used alternatively to the SSM. The SSI is compatible to the FOX51x.
The SSI is transported in the Sa5 bit of the timeslot 0 of a structured P12 signal. It transport two
states:
• SSI = 1: “Can be used for synchronization”,

• SSI = 0: “Do not use for synchronization”.

FOX61x internally the received SSI is mapped to a QL value:
• SSI = 1: mapped to QL = 13,
• SSI = 0: mapped to QL = 15,
and the QL value is mapped to a transmitted SSI:
• QL < 15: mapped to SSI = 1,
• QL = 15: mapped to SSI = 0.
5.8.1.3 Quality Level with PTP Clock Class

The QL (Quality Level) information in a PTP system is carried in the Clock Class parameter of
the PTP Announce messages, received by a Slave Clock or sent by a Master Clock.
Table 1 of ITU-T G.8265.1 defines the following mapping between the Clock Class parameter
and the QL.
Table 3: Mapping between QL values and Clock Class values

Clock Class → QL (binary) QL (decimal) → Clock Class
82, 83 0000 0 82
0 … 81 0001 1 80
84, 85 0010 2 84
88, 89 0011 3 88
90, 91 0100 4 90
92, 93 0101 5 92
94, 95 0110 6 94
86, 87 0111 7 86
96, 97 1000 8 96
98, 99 1001 9 98
102, 103 1010 10 102
104, 105 1011 11 104
106, 107 1100 12 106
100, 101 1101 13 100
108, 109 1110 14 108
110 … 255 1111 15 110
5.8.2 Quality Level Transport in FOX61x
5.8.2.1 Quality Level Transport in SDH Signals

The QL (Quality Level) information transport on the SDH signals is supported on the SDH ports
Multiplex Section (MS) layer of the FOX61x SDH service units. When using the SSM quality
level for the timing source selection the “SSM” parameter must be enabled on the MS layer.
For more information please refer to [1KHW002476] User Manual “SAMO1” and refer to
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”.
5.8.2.2 Quality Level Transport in PDH Signals

The QL (Quality Level) information transport on the PDH signals is supported
• on the E1 ports of the LEDE1 and CEPI1 service units.
• on the structured P12 signals of the circuit emulation pseudo wires of the CEPI1 service
units.
• on the structured P12 signals transported via an SDH service unit SAMO1 or SAMOx.

When using the SSM quality level for the timing source selection the “SSM” parameter must be
enabled on the E1 port, P12 pseudo wire or P12 transport signal.
When using the SSI quality level for the timing source selection the “SSI” parameter must be
enabled on the E1 port, P12 pseudo wire or P12 transport signal.
5.8.2.3 Quality Level Transport on DSL Traffic Signals

The QL (Quality Level) information transport on the DSL service units of the FOX61x is sup-
ported as follows:
• DATI1 unit:
With the DATI1 unit the SSM transport is supported in the trunk mode. The SSM is for-
warded from the LT function (Trunk To NT) to the NT function (Trunk To LT) in the DSL over-
head. SSM transport is always active.
The SSM can also be transported in the DSL payload. The trunk termination mode must be
configured to “Structured”. SSM transport in the payload works in both directions, LT to NT
and NT to LT.
For more information please refer to [1KHW002474] User Manual “DATI1”.
• DEFM1 unit:
With the DEFM1 unit the SSM transport is supported in the trunk mode. The SSM is for-
warded from the LT function to the NT function in the DSL overhead. When using the SSM
quality level for the timing source selection the synchronization QL transmission parameter
must be enabled on the physical port.
For more information please refer to [1KHW028775] User Manual “DEFM1, DEFM1-F”.
5.8.2.4 Quality Level Transport on SyncE Traffic Signals

The QL (Quality Level) information transport on synchronous Ethernet (SyncE) ports is sup-
ported on the core units of the FOX61x. SyncE uses specific ESMC (Ethernet Synchronization
Messaging Channel) frames transporting the SSM.
When using the SSM quality level for the timing source selection the synchronization method
“ESMC” must be selected for the physical port in the FOXCST “Synchronization” view at the AP:
/Synchronization/SyncE.
5.8.2.5 Quality Level Transport with PTP

The QL (Quality Level) information transport on PTP ports is supported on the core units of the
FOX61x. The PTP port must be configured to be a Boundary Clock or Ordinary Clock port.
The QL transport in a PTP system is always enabled.
The PTP QL value is displayed in the PTP status dialog of a PTP enabled port.
The Clock Class parameter is displayed in the PTP status dialog of a PTP enabled port and in
the PTP status dialog of the network element.
5.8.3 Quality Level Management

In order to set up a synchronization network using defined quality level values the received and
transmitted QL values can be adjusted using the following mechanisms:
A received quality level value can be modified with an input mapping table or can be overridden
by a fixed QL value.
A transmitted quality level value can be modified with an output mapping table or can be over-
ridden with a routing table.
For a detailed description see the sections below.

QL ext raction Input Mapping QL override PETS or Output Mapping QL insertion into
Routing table
from SSM Table for QL by QLfix SETS Table for QL SSM
QL received QL received QL received QL transmitt ed QL transmitted or can be used: QL = unchanged

or adapted or adapted adapted do not use: QL = 15
or f ixed
Figure 29: Quality level management
Please note:
The input mapping table and output mapping table are only supported for SDH traf-
fic signals and SyncE ports.
5.8.3.1 Quality Level Input and Output Mapping

A received quality level of an SDH traffic signal in the range 1 to 15 can be adapted to any
other quality level in the range 1 to 15 which will then be used in the SETS and ESO-2 selection
process.
The input mapping table for the STM-16, STM-4 and STM-1 traffic signals maps the received
QL information (Received QL) to new QL values (Adapted QL). The input mapping table is
assigned to the multiplex section (MS) layer of the SDH signal.
A SETS internally used quality level in the range 1 to 15 can be adapted to any other quality
level in the range 1 to 15 which can then be used in the SSM of the corresponding transmit sig-
nal.
The output mapping table for the STM-16, STM-4 and STM-1 traffic signals maps the QL at the
SETG output (Transmitted QL) to new QL values (Adapted QL). The output mapping table is
assigned to the multiplex section (MS) layer of the SDH signal.
A received quality level of a SyncE traffic signal in the range 1 to 14 can be adapted to any
other quality level in the range 0 to 15 which will then be used in the PETS and ESO-1 selection
process.
The input mapping table for a SyncE port maps the received QL information (Received QL) to
new QL values (Adapted QL). The input mapping table is assigned to the SyncE port at the AP:
/Synchronization/SyncE.
A PETS internally used quality level in the range 1 to 14 can be adapted to any other quality
level in the range 0 to 15 which can then be used in the SSM of the corresponding transmit sig-
nal.
The output mapping table for a SyncE port maps the QL at the NETG output (Transmitted QL)
to new QL values (Adapted QL). The output mapping table is assigned to the SyncE port at the
AP: /Synchronization/SyncE.
Please note:
The default mapping is a 1:1 mapping.
Please note:
The quality level 0 means “quality unknown”.
The quality level 15 means “do not use for synchronization”.
5.8.3.2 Quality Level Override

In synchronization applications using the clock source selection algorithm “QL” the SETS,
PETS, ESO-1 and/or ESO-2 clock source QL parameter is configured to “Received”, i.e. the
received QL value is used as selection criterion.
In cases where the clock source provides no quality level, e.g. the ESI-1 input, or the application
requires to apply a fixed quality level value, the QL parameter can be overridden by configuring
a fixed QL value in the range 1 to 14 (configuration QL = <specified value>) or even to “do not
use”.

The QL value configuration is done at the following access points:

• SETS: AP: /SDH service unit, Configuration - SETS - SETS Clock Selection table
• PETS: AP: /Synchronization/PETS, Configuration - PETS Clock Selection table
• ESO-1: AP: /Synchronization/ESO, Configuration - ESO-1 Clock Selection table
• ESO-2: AP: /SDH service unit, Configuration - ESO-2 - ESO-2 Clock Selection table
Please note:
A clock source not supporting a quality level must be configured with a fixed QL
value.
→ Otherwise the value “do not use” will be assigned to the corresponding traffic
signal.
5.8.3.3 Quality Level Routing

In order to prevent a timing loop the outgoing quality level on a signal which is used as timing
source of the SETS or PETS shall signal the “do not use” QL value. This behavior is controlled
with the “SDH Routing Table” on the SETS clock sources or with the “QL Transmission” table
for the PETS clock sources.
The SDH routing table or QL transmission table shows for all available clock sources if the
transmitted QL shall be unchanged (= “Can be used”) or if the transmitted QL shall be set to 15
(=”Do not use”).
The table has the following default behavior:
• The clock source of the current access point has the usage parameter set to “DoNotUse”,
i.e. in reverse direction the timing shall not be used as clock source.
• The clock source of all other access points have the usage parameter set to “CanBeUsed”,
i.e. in forward direction the timing can be used as clock source.
The usage parameter can be modified with the FOXCST.
The SDH routing tables are available at the following access points:
• SAMOx SDH traffic signal:
AP: /unit-x/sdh/sdh-y, Configuration - MS - SDH Routing Table
• SAMO1 SDH traffic signal:
AP: /unit-x/port-y, Configuration - MS - SDH Routing Table
The QL transmission tables are available at the following access points:
• LEDE1 and CEPI1 PDH traffic signal:
AP: /unit-x/port-y, Configuration - Synchronization - QL Transmission
• CEPI1 pseudo wire:
AP: /unit-x/pw/pw-y, Configuration - Synchronization - QL Transmission
• SAMOx and SAMO1 P12 transport signal:
AP: /unit-x/pdh/vc12-y/p12, Configuration - Synchronization - QL Transmission
• DEFM1 DSL trunk:
AP: /unit-x/port-y, Configuration - Synchronization - QL Transmission
• DATI1 DSL trunk:
AP: /unit-x/logports/logport-y/trunk, Configuration - Synchronization - QL Transmission
• SyncE:
AP: /Synchronization/SyncE, Ports - Port Configuration - QL Transmission
• PTP:
AP: /Synchronization/PTP, Ports & Streams - Port Configuration - QL Transmission

5.8.4 PETS Quality Level Overview

The Figure 30 shows the quality level (QL) information handling as it is implemented on the
FOX61x network element for the following input clock sources and output signals:
• Input signals:
− PDH clock source 1 to PDH clock source 4,
− PTP source 1 to PTP source 4,
− ESI synchronization signals ESI-1 to ESI-2,
− Internal (local oscillator).
• Output signals:
− Network element synchronous Ethernet and PDH signal timing (PETS),
− PTP output timing,
− ESO synchronization signal ESO-1.

Core Unit
QL received QL override
by QLfix
select up to 4 PTP sources

(PETS)
QL extraction QL based or
PTP VLAN PTP source Priority based PTP VLAN
from PTP
QL override PETS clock
by QLfix selection
(PETS)
Interface QL extraction QL insertion Interface
PTP source
(Ethernet) from PTP in PTP (Ethernet)
QL override
by QLfix
QL received (PETS)
QL override
PDH or SDH or Ethernet by QLfix
(PETS)
unit
PDH or SDH or Ethernet
QL received unit
or adapted
or fixed
can be used: QL = unchanged
SETS PDH clock
do not use: QL = 15
(STM) source
QL override
Routing Table Interface
Selector B
no QL by QLfix
(P12) (P12)
Interface PDH clock (PETS)
select up to 4 PDH clock sources
(P12) source
QL received QL override
by QLfix Routing Table Interface
QL extraction (PETS) (P12) (P12)
Interface PDH clock
from SSI
(P12) source QL adapted
(P12) QL override
QL received by QLfix
(PETS) Output Mapping Routing Table Interface
QL extraction Table for QL (Ethernet) (Ethernet)
Interface PDH clock
from SSM
(P12) source QL override
(P12)
by QLfix
(PETS)
Output Mapping Routing Table Interface
no QL NETG Table for QL (Ethernet) (Ethernet)
Interface PDH clock QL override
(Ethernet) source by QLfix
(PETS)
QL received QL adapted PETS locked
QL extraction QL override
Interface Input Mapping PDH clock
from SSM by QLfix
(Ethernet) Table for QL source
(Ethernet) (PETS)
ESO selected clock source from
QL fixed
Squelched by selector B and QL from the
Source selected clock source
Local
Oscillator
QL fixed Squelch ESO for

certain Sources
QL received
or fixed
Squelch
QL override
ESO
by QLfix for certain
PETS locked or
(ESO)
non PETS locked QL
ESO clock
QL override selection
by QLfix
Selector C
(ESO) ESO
ESO-1
Squelched by
(active Core Unit)
Selector A
QL override QL
by QLfix
(ESO)
QL override non PETS locked

by QLfix
(ESO)
QL override
ESI-1
by QLfix
(active Core Unit) QL based or
(ESO)
Priority based
ESO clock
no QL
* esi-2 is available as a PETS ESI-2 * QL override selection
by QLfix
clock source only for CESM1 (active Core Unit) (ESO)
and CESM2
QL fixed
Figure 30: QL handling for PDH traffic signals and other clock sources
Please note:
The Ethernet interfaces supporting synchronous Ethernet are all located on the
core unit or on the WAN port extension unit (EPEX1).


All five ports on the WAN port extension unit EPEX1 support synchronous Ether-
net, but just two of them at the same time.
Please note:
The Ethernet interfaces supporting PTP are all located on the core unit or on the
WAN port extension unit (EPEX1).

The WAN port extension unit EPEX1 supports the VLAN Master and VLAN slave
modes. There is no support for port based PTP boundary clock.
The PDH traffic, PTP and synchronous Ethernet based synchronization system provides
the following functional blocks for the QL processing:
• QL extraction from SSM or SSI, assigned to the P12 layer:
The SSM or SSI is extracted from the timeslot 0 Sa bit (QL received).
Note that P12 signals not supporting the SSM or SSI have no QL assigned.
• QL extraction from PTP, assigned to the Ethernet port layer:
The QL is transported in the PTP packets received from a clock master.
• QL extraction from SSM, assigned to the Ethernet port layer:
The SSM is transported in the Ethernet Synchronization Messaging Channel (ESMC).
• Input mapping table, assigned to the port layer supporting synchronous Ethernet:
The input mapping table for the Ethernet traffic signals maps the received QL information
(QL received) to new QL values (QL adapted).
• PTP source:
The PTP sources are all located on the core unit(s) or on the WAN port extension unit
(EPEX1). The QL assigned to a clock source is forwarded transparently.
The QL of a PTP source is the QL received.
• PDH clock source:
The PDH clock sources from PDH service units, Ethernet clock sources from Ethernet core
units and SDH clock sources from SDH service units are transported via the FOX61x back-
plane. The QL assigned to a clock source is forwarded transparently, except for synchronous
Ethernet ports.
The QL of a PDH or Ethernet clock source is the QL received or no QL. The QL of a SDH
clock source is the SETS QL (QL selector B = QL received, adapted or fixed, refer to Figure
31 and Figure 32).
• QL override, assigned to the PETS access point:
It is possible to configure the timing system so that the received QL is forwarded to the PETS
selector (configuration QL = Received) or to override the QL with a fixed value. The fixed
value is configurable in the range 1 to 15.
When a clock source has no QL assigned it will get a fixed QL.
• Selector B, assigned to the PETS access point:
The QL information is forwarded transparently according to the selected clock source.
• PTP source output:
The PETS QL information (QL of the selector) is forwarded transparently according to the
selected clock source to the PTP source output.
• PDH clock source output:
The PETS QL information (QL of the selector) is forwarded according to the selected clock
source to the PDH clock source output.
• Output mapping table, assigned to the port layer supporting synchronous Ethernet:
The output mapping table for the Ethernet traffic signals maps the QL at the NETG output
(QL selector B) to new QL values (QL adapted).

• PDH routing (QL transmission) table, assigned to the P12 layer,

Ethernet routing (QL transmission) table, assigned to the Ethernet port layer,
DSL routing (QL transmission) table, assigned to the DSL trunk layer:
The routing table defines for each traffic signal (leaving the NE) whether the signal can be
used for synchronization purposes or not. Depending on the selected clock source the rout-
ing table marks the traffic signal with “Can be used” (QL = unchanged) or “Do not use” (QL =
15).
The routing table has default values as follows:
− Traffic signal of the own interface is selected as PDH clock source:
“Do not use”.
− Traffic signal of another interface is selected as PDH clock source:
“Can be used”.
The routing table can be modified with the FOXCST.
Please note:
Only the PETS function configured to the “QL” based clock selection algorithm
interprets the QL in the traffic signal. If the PETS function is configured to the “Pri-
ority” based clock selection algorithm the received QL is not considered.
The ESI/ESO synchronization interface based synchronization system provides the following
functional blocks for the QL processing:
• ESI synchronization input:
The core unit provides two synchronization input interfaces, ESI-1 and ESI-2. On the CESM3
core unit the ESI-1 can be used as PETS clock source. On the CESM1 and CESM2 core
units both interfaces can be used as PETS clock sources.
Note that the ESI timing signal has no QL assigned.
• QL override, assigned to the PETS and ESO access points:
The ESI clock source gets a fixed QL which is forwarded to the PETS selector A and selec-
tor B. The fixed value is configurable in the range 1 to 15.
• Selector A, assigned to the ESO access point:
Selector A is used for the clock source selection for the ESO-1 synchronization output inter-
face in the “non PETS locked” mode.
• Selector B, assigned to the PETS access point:
Selector B is used for the clock source selection for the ESO-1 synchronization output inter-
face in the “PETS locked” mode.
The QL information is forwarded transparently according to the selected clock source to the
network element timing generator (NETG).
• ESO squelched by source, assigned to the ESO access point:
In the PETS locked mode for ESO-1, the ESO squelched by source table defines whether
the synchronization signal can be used for synchronization purposes or not. Depending on
the selected clock source the ESO-1 output is squelched.
• Selector C, assigned to the ESO access point:
Selector C is used for the selection between the “PETS locked” and “non PETS locked”
mode for the ESO-1 synchronization output.
• ESO squelched by QL, assigned to the ESO access point:
The ESO squelched by QL table for the ESO-1 synchronization output defines whether the
QL from selector B (PETS locked mode) or from selector A (non PETS locked mode)
squelches the output, i.e. the ESO-1 output signal is squelched for some configurable QL
values.

5.8.5 SETS Quality Level Overview

The Figure 31 and the Figure 32 show the quality level (QL) information handling as it is imple-
mented on the SAMO1 and SAMOx units for the following input clock sources and output sig-
nals:
• Input signals:
− 4 STM-16, STM-4 and STM1 traffic signals,
− 4 additional STM-16, STM-4 and STM1 traffic signals on a protecting SAMOx unit (not
shown in Figure 32),
− 4 P12 clock source signals,
− 1 ESI synchronization signal,
− 1 Internal (local oscillator).
• Output signals:
− 4 STM-16, STM-4 and STM1 traffic signals,
− 4 additional STM-16, STM-4 and STM1 traffic signals on a protecting SAMOx unit (not
shown in Figure 32),
− 1 PDH clock source signal (FOX61x internal),
− 1 ESO synchronization signal ESO-2.
The ESO-2 synchronization output interface used for the SDH timing operates in two different
modes:
• SETS locked mode,
• Non SETS locked mode.
In the “SETS locked” mode, the SETG of the SETS system provides the timing signal for the
ESO-2 output. The clock sources for the ESO-2 are therefore the same as for the selector B.
In the “non SETS” locked mode, the ESO-2 output uses its own selector switch (selector A) for
the selection of the timing signal. The selector A on the SAMO1 unit provides the same clock
sources as the selector B. The selector A on the SAMOx unit provides the 4 or 8 SDH traffic sig-
nals as clock sources.

Core Unit PDH clock SAMO1 SDH service unit

source
(PETS) QL received
or adapted
or fixed preselected timing source
PDH clock
source
(PETS)
PDH clock
Preselector
QL override
source by QLf ix
(PETS) (SETS) can be used: QL = unchanged
QL based or QL adapted do not use: QL = 15
PDH clock Priority based
source SETS clock Output Mapping SDH Routing Front
(PETS) selection Table for QL Table interface
(MS) (MS) STM-x
ESI-2
active no QL
Core Unit Output Mapping SDH Routing Front
Table for QL Table interface
Local (MS) (MS) STM-x
ESI-2 Oscillator
standby
Core Unit
Output Mapping SDH Routing Front
QL received QL adapted Table for QL Table interface
QL fixed
(MS) (MS) STM-x
Front QL ext raction Input Mapping QL override
interface from SSM Table for QL by QLf ix
STM-x (MS) (MS) (SETS)
Selector B
SETG Table for QL Table interface
Front QL ext raction Input Mapping QL override (MS) (MS) STM-x
to PDH clock
Front QL ext raction Input Mapping QL override source
interface from SSM Table for QL by QLf ix PDH clock
STM-x (MS) (MS) (SETS) source
SETS locked
Front QL ext raction Input Mapping QL override selected
interface from SSM Table for QL by QLf ix clock source
QL received
or adapted
or f ixed
ESO Squelched
by Source
QL override
by QLf ix
(ESO) Squelch ESO for Squelch ESO
certain Sources for certain QL
QL override
by QLf ix
Selector C
(ESO) Front
Selector A
ESO Squelched
interface
by QL
QL override ESO-2
by QLf ix
(ESO)
non SETS locked SETS locked or

QL override non SETS locked
by QLfix ESO clock
(ESO) selection
QL override
by QLf ix
(ESO) QL based or
Priority based
ESO clock Core Unit
QL received
or adapted selection
or f ixed
Figure 31: QL handling for SDH traffic signals and other clock sources on SAMO1

Core Unit PDH clock QL override SAMOx SDH service unit

source by QLf ix
(PETS) QL received (SETS)
or adapted QL based or
or f ixed Priority based
PDH clock QL override
source by QLf ix SETS clock
(PETS) (SETS) selection
PDH clock QL override

source by QLf ix
(PETS) (SETS)
can be used: QL = unchanged

PDH clock QL override QL adapted do not use: QL = 15
source by QLf ix
(PETS) (SETS)
SETG Table for QL Table interface
(MS) (MS) STM-x
ESI-2
active no QL
Core Unit QL override
by QLf ix Output Mapping SDH Routing Front
(SETS) Table for QL Table interface
ESI-2
Selector B
(MS) (MS) STM-x
standby QL received
Core Unit or adapted
QL received QL adapted or f ixed
Table for QL Table interface
Front QL ext raction Input Mapping QL override (MS) (MS) STM-x
Front QL ext raction Input Mapping QL override Table for QL Table interface
interface from SSM Table for QL by QLf ix (MS) (MS) STM-x
to PDH clock
Front QL ext raction Input Mapping QL override source
interface from SSM Table for QL by QLf ix PDH clock
STM-x (MS) (MS) (SETS) source
Front QL ext raction Input Mapping QL override

SETS locked
Local
Oscillator selected
clock source
QL = 11
ESO Squelched
QL received by Source
or adapted
or f ixed
Squelch ESO for Squelch ESO
certain Sources for certain QL
QL override
by QLf ix
Selector C
(ESO) ESO Front

Squelched by interface
QL override QL ESO-2
by QLf ix
Selector A
(ESO)
non SETS locked SETS locked or

QL override non SETS locked
by QLfix ESO clock
(ESO) selection
QL override QL based or
by QLf ix Priority based
(ESO) ESO clock Core Unit
selection
Figure 32: QL handling for SDH traffic signals and other clock sources on SAMOx
The SDH traffic based synchronization system provides the following functional blocks for
the QL processing:
• QL extraction from SSM, assigned to the multiplex section (MS) layer:
The SSM is extracted from the S1 byte and accepted if the same code is present in three
consecutive frames (QL received).
• Input mapping table, assigned to the multiplex section (MS) layer:
The input mapping table for the STM-16, STM-4 and STM-1 traffic signals maps the received
QL information (QL received) to new QL values (QL adapted).

• QL override, assigned to the SETS access point:

It is possible to configure the timing system so that the adapted QL is forwarded to the SETS
selector B (configuration QL = Received) or to override the QL with a fixed value. The fixed
value is configurable in the range 1 to 15.
• Selector B, assigned to the SETS access point:
synchronous equipment timing generator (SETG).
Please note:
If the SETS on a SAMO1 or SAMOx unit is locked to any of the PDH Clock
Sources it will forward the QL 15 (do not use) inside the FOX61x network element,
i.e. towards the PDH clock source.
→ This avoids a clock loop if e.g. two SETS functions on two SAMOx units use the
PDH Clock Source of the other SAMOx unit as a (secondary) clock source.
→ It is therefore not possible to synchronize the PETS to a SETS function if the
SETS function is synchronized to one of the PDH Clock Sources.
If you have to synchronize the PETS to the SETS function either
• use the Priority based clock selection mode, or
• synchronize the PETS to the same PDH Clock Source as the SETS.
• Output mapping table, assigned to the multiplex section (MS) layer:
The output mapping table for the STM-16, STM-4 and STM-1 traffic signals maps the QL at
the SETG output (QL selector B) to new QL values (QL adapted).
• SDH routing table, assigned to the multiplex section (MS) layer:
The routing table defines for each traffic signal (leaving the NE) whether the signal can be
used for synchronization purposes or not. Depending on the selected clock source the rout-
ing table marks the traffic signal with “Can be used” (QL = unchanged) or “Do not use” (QL =
15).
Please note:
Only the SETS function configured to the “QL” based clock selection algorithm
interprets the SSM in the traffic signal. If the SETS function is configured to the
“Priority” based clock selection algorithm the received SSM is not considered.
The ESI/ESO synchronization interface based synchronization system provides the following
functional blocks for the QL processing:
• ESI synchronization input:
The core unit provides two synchronization input interfaces, ESI-1 and ESI-2. One of these
two timing signals, i.e. ESI-2, is brought to the backplane of the FOX61x and distributed to all
units plugged in the FOX61x subrack.
The ESI timing signal of a standby core unit is also brought to the backplane of the FOX61x
and distributed to all units plugged in the FOX61x subrack.
Only the ESI timing signal of the active core unit is used for the SETS synchronization.
Note that the ESI timing signal has no QL assigned.
Please note:
The ESI clock source selection on the SDH service units for SETS or ESO is fixed
to ESI-2.
• Preselector, assigned to the SETS access point (SAMO1 only):
The preselector selects one of the PDH clock sources or ESI clock sources. The QL informa-
tion is forwarded transparently to the selectors A and B according to the preselected clock
source.

• QL override, assigned to the SETS and ESO access points:

The ESI clock source gets a fixed QL which is forwarded to the SETS selector A and selec-
tor B. The fixed value is configurable in the range 1 to 15.
• Selector A, assigned to the ESO access point:
Selector A is used for the clock source selection for the ESO-2 synchronization output inter-
face in the “non SETS locked” mode.
• Selector B, assigned to the SETS access point:
Selector B is used for the clock source selection for the ESO-2 synchronization output inter-
face in the “SETS locked” mode.
synchronous equipment timing generator (SETG).

If ESO-2 is non SETS locked, on the SAMO1 unit only one single input from the
preselector (PDH and ESI clock sources) can be used for both the SETG synchro-
nization and the ESO-2 output.
Please note:
If ESO-2 is non SETS locked, on the SAMOx unit only the SDH traffic sources can
be used for the ESO-2 output.
• ESO squelched by source, assigned to the ESO access point:
In the SETS locked mode for ESO-2, the ESO squelched by source table defines whether
the synchronization signal can be used for synchronization purposes or not. Depending on
the selected clock source the ESO-2 output is squelched.
• Selector C, assigned to the ESO access point:
Selector C is used for the selection between the “SETS locked” and “non SETS locked”
mode for the ESO-2 synchronization output.
• ESO squelched by QL, assigned to the ESO access point:
The ESO squelched by QL table for the ESO-2 synchronization output defines whether the
QL from selector B (SETS locked mode) or from selector A (non SETS locked mode)
squelches the output, i.e. the ESO-2 output signal is squelched for some configurable QL
values.
5.9 Service Timing
5.9.1 Synchronous Ethernet Service Timing

Synchronous service timing means that the Ethernet signals in transmit direction are synchro-
nized to the FOX61x internal PETS.
The PETS can be synchronized to a received synchronous Ethernet traffic signal.
The transmit timing of the Ethernet ports on the core unit or on the WAN port extension unit is
always synchronized to the PETS timing.
Synchronous Ethernet services are selected by the configuration of the Ethernet ports on the
core unit at the AP: /Synchronization/SyncE - Ports - Port Configuration.
5.9.2 Synchronous PDH Service Timing

Synchronous service timing means that the PDH TDM signals in receive and transmit direction
are synchronized to the FOX61x internal PETS.
Synchronous services are selected by the configuration of the E1 or DATI1 - CPE or PDH P12
signal termination mode:

− Clock Master,
− PCM30, PCM30C,
− PCM31, PCM31C,
− PCMnn, PCMnnC (DATI1 only),
− G.704 Customized (DATI1 only),
− Structured, Structured with CAS (DATI1 only),
In the synchronous applications all involved network elements must be synchronized to a com-
mon clock derived from the same PRC. The different possibilities for the NE synchronization to
the network reference clock are presented in section 5.3 PETS (on page 39).
5.9.3 Plesiochronous PDH Service Timing

Plesiochronous service timing means that the PDH TDM signals in receive and transmit direc-
tion are not synchronized to the PETS. The timing of these signals is transparent.
Plesiochronous services are selected by the configuration of the E1 or DATI1 - CPE or PDH
P12 signal termination mode:
− Transparent.
In the plesiochronous applications the PETS of the involved network elements needs not to be
synchronized to the network reference timing.

FOX61x | SYNCHRONIZATION COMMISSIONING
6 Commissioning
This chapter describes the configuration and the placing into operation of the synchronization
applications with the FOX61x.
6.1 General Prerequisites

In order to commission synchronization applications on the FOX61x, you will need to fulfill the
following prerequisites:
• you need a network planning with regard to synchronization signal connections in the FOX-
61x network element and synchronization signal transport in the network, i.e. you need to
have a plan about how you want to use synchronization signals in your network.
• you need a TDM and/or packet network with equipment that supports timing transport in
PDH, SDH, Synchronous Ethernet and/or PTP;
• you need a FOX61x that is physically built into your access network. For installation of the
FOX61x
− refer to [1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”, or
− refer to [1KHW002462] Installation Instruction “FOX612 Installation”, or
− refer to [1KHW029142] Installation Instruction “FOX611 Installation”;
• you need released ESW installed on all of your FOX61x units supporting the functionality of
the current release; for details about released ESW, refer to [1KHW028777] Release Note
“FOX61x System Release R15B”;
• you need a management connection to your FOX61x; for details about connecting to your
FOX61x, refer to [1KHW028522] User Manual “Management Communication”;
• you need a network element manager that is connected to your FOX61x or a management
interface, i.e. FOXCST.
6.2 SDH Synchronization

All SDH ports and SDH processing on a SAMO1 unit or SAMOx unit are synchronized to the
onboard SETS. The SETS can be synchronized to one of the received STM-16, STM-4 or STM-
1 signals, to an external timing input signal, to any received PDH signal or can be operated in
the free running mode.
6.2.1 Prerequisites
To be able to use an SDH or PDH traffic signal or an external timing signal for synchronization
these signals must be connected to the FOX61x network element and the ports must be in the
operational state “up”.
Please note:
The ESI clock source selection on the SAMO1 and SAMOx unit for SETS or ESO
is fixed to ESI-2.
Please note:
vated.

Please note:
The ESI-2 port on the CESM1 or CESM2 core unit is enabled when a clock priority
is assigned to it in the SETS or ESO configuration on a SAMO1 or SAMOx unit.
→ The esi-2 managed object on the core unit are not activated.
vated.
6.2.2 SETS Synchronization via SDH Traffic Signals

In this scenario the SDH timing of the SAMO1 unit plugged in slot 20 is synchronized to the
STM-4 traffic signal connected to the port-1. The SETS clock source has to be configured to the
“Port 1” input.
The second priority clock source is the SETS timing of another SAMO1 unit plugged in slot 21.
The timing signal of this unit is fed to the PDH clock source 1.
The ESO-2 clock output shall be active when the SETS is synchronized to one of the STM-4
traffic signals and shall be squelched when the SETS has selected the internal oscillator (free
running mode).
The clock selection algorithm is priority based.
SETS SETS clock to SDH Timing

port-1 SEC
Selector
STM-4 clock to eso-2

SETG
SAMO1
slot-20
up to 4 PDH clock sources
SAMO1
slot-21
SETS
port-1
STM-4
Core Unit
clock to
eso-2
eso-2
2048 kHz
Figure 33: SETS synchronization via SDH traffic signals
For the synchronization configuration, the following steps have to be performed.
SETS configuration
The SETS is synchronized to the STM-4 signal, alternatively to the SETS of SAMO1 in slot 21.

→ SETS clock selection. SAMO1 in slot-21. Proceed as follows:

1. Navigate to the SETS configuration dialog:
- AP: /unit-21, Configuration - SETS.
2. Select the parameters of port 1:
- Priority = 1.
- Quality Level = Received.
- Holdoff Time = 0 s.
- Wait-To-Restore Time = 30 s.
3. Select the clock selection algorithm:
- Selection Algorithm = Priority.
4. Execute “Apply”.
Result: The SETS clock selection is fully configured.
→ Select the PDH clock source. Proceed as follows:

1. Navigate to the PETS configuration dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/PETS, Configuration.
2. Select the PDH clock source 1:
- PDH Clock Source 1 = /unit-21.
(Select the SETS timing of the SAMO1 unit plugged in slot 21)
Result: The PDH clock source is fully configured.

2. Select the parameters of port 1:
- Priority = 1.
3. Select the parameters of PDH clock source 1:
- Priority = 2.
4. Select the parameters of the internal clock source:
- Priority = 10.
- Quality Level = 11.
End of instruction
ESO configuration
The ESO-2 is SETS locked, ESO-2 is squelched if the internal clock is selected as clock source.

→ Configure the ESO-2 clock sources. Proceed as follows:

1. Navigate to the SAMO1 ESO configuration dialog:
- AP: /unit-20, Configuration - ESO-2.
2. Operate the ESO-2 in the SETS locked mode:
- ESO-2 SETS Locked = true
(The “ESO-2 Squelched By Source” table is applied).
3. Select the valid ESO-2 clock sources:
− Port 1, ESO-2 Squelched = false
− PDH Clock Source 1, ESO-2 Squelched = false
− Internal, ESO-2 Squelched = true
Result: The ESO-2 clock sources are fully configured.
→ Configure the ESO-2 selection. Proceed as follows:

1. Navigate to the ESO configuration dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/ESO, Configuration.
2. Select the unit-20 as ESO-2 clock source:
- SDH Clock Source = /unit-20.
Result: The ESO-2 clock selection is fully configured.
End of instruction
After the configuration of the SETS and ESO check the fault free operation:
SETS and ESO status check

Check the fault free operation of the SETS and ESO-2.
→ Check the PDH clock source 1. Proceed as follows:

1. Navigate to the NE fault management dialog:
- AP: /ne, Fault Management - Status.
2. Check the fault cause state:
- LOSP1 = Off
→ Check the SETS clock sources. Proceed as follows:

1. Navigate to the SAMO1 status dialog:
- AP: /unit-20, Status - SETS.
2. Check the status of port 1:
- Priority = 1
- Quality Level= <received>
- Status = Available
3. Check the status of PDH clock source 1:
- Priority = 2
- Quality Level= <received>
4. Check the status of the internal clock:
- Priority = 10
- Quality Level= 11

→ Check the SETS status. Proceed as follows:

2. Check the SETS status:
- Selection Algorithm = Priority
- Selected Clock Source = Port 1
- Clock Operation Mode = Locked
- Clock Operation Type = Auto Selection
→ Check the ESO-2 status. Proceed as follows:

1. Navigate to the ESO status dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/ESO, Status.
2. Check the ESO-2 status:
- Clock Output Status = Active
Result: The SDH timing functions are completely checked.
End of instruction
6.2.3 SETS Synchronization via Synchronous Ethernet Signals

In this scenario the SDH timing of the SAMO1 unit plugged in slot 20 is synchronized to the syn-
chronous Ethernet signal connected to the port-1 of the core unit. This timing signal is fed to the
PDH clock source 1.
The second priority clock source is the synchronous Ethernet signal connected to the port-2 of
the core unit. This timing signal is fed to the PDH clock source 2.
SEC
Selector
SETS clock to SDH Timing

SETG
SETS
SAMO1
slot-20
Core Unit
port-1
Ethernet
port-2
Ethernet
Figure 34: SETS synchronization via SyncE signals
SETS configuration
The SETS is synchronized to the SyncE signals of port-1 and alternatively port-2 of the core
unit.

→ Select the PDH clock source. Proceed as follows:

- PDH Clock Source 1 = /unit-11/port-1.
(Select the port-1 SyncE timing of the core unit plugged in slot 11)
(Select the port-2 SyncE timing of the core unit plugged in slot 11)
Result: The PDH clock source is fully configured.

- Priority = 1.
- Priority = 2.
- Priority = 10.
End of instruction
After the configuration of the SETS check the fault free operation:
SETS status check

Check the fault free operation of the SETS.

1. Navigate to the SAMO1 fault management dialog:
- AP: /unit-20, Fault Management - Status.
- LOSP1 = Off
- LOSP1 = Off


- Priority = 1
- Quality Level= <received>, or 15 if ESMC is disabled
- Priority = 2
- Quality Level= <received>, or 15 if ESMC is disabled
- Priority = 10
- Quality Level= 11

- Selected Clock Source = PDH Clock Source 1
- Clock Operation Mode = Locked
End of instruction
6.2.4 SETS Synchronization via the Local Oscillator

In this scenario the SDH timing of the SAMO1 unit plugged in slot 20 is synchronized to the
SETS internal oscillator (free running mode).
SEC
SETS clock to SDH Timing
SETG
SETS
SAMO1
slot-20
Figure 35: Free running SETS from internal oscillator
SETS configuration
The SETS is synchronized to the internal oscillator.



- Priority = 10.
End of instruction
After the configuration of the SETS check the fault free operation:
SETS status check

Check the fault free operation of the SETS.

- Priority = 10
- Quality Level= 11

- Selected Clock Source = Internal
- Clock Operation Mode = Free Running
End of instruction
6.3 PDH Synchronization

In the synchronous TDM applications based on the TDM bus of the FOX61x (PBUS) the incom-
ing and outgoing TDM signals are synchronized to the plesiochronous equipment timing source
(PETS) of the FOX61x. The PETS can be synchronized
• to a received P12 signal (via PDH or SDH or DSL or CES),
the received P12 signal must be operated in one of the following termination modes:
− Transparent, or
− PCM30, PCM30C, or
− PCM31, PCM31C, or
− V5 Uplink, V5 Uplink NCI, or
− PCMnn, PCMnn_CAS (CEPI1), or
− Structured, Structured with CAS (DATI1).
• to a DSL trunk signal,

• to a SyncE port,
• to a received PTP packet stream,
• to a SETS function on a SDH service unit,
• to a fixed oscillator (TCXO) on the CEPI1 service unit,
• to an external timing input signal, or
• can be operated in the free running mode.
6.3.1 Prerequisites
To be able to use an PDH, DSL, SyncE or PTP traffic signal, or an external timing signal for
synchronization these signals must be connected to the FOX61x network element and the ports
must be in the operational state “up”.
Please note:
The PETS or ESO-1 on the CESM1 and CESM2 core units can use the ESI-1 and/
or ESI-2 external timing input.
Please note:
The PETS or ESO-1 on the CESM3 core unit can only use the ESI-1 external tim-
ing input.
Please note:
The ESI-1 port on the CESM3, CESM1 or CESM2 core unit is automatically
enabled when it is enabled in the PETS or ESO-1 configuration.
The ESI-2 port on the CESM1 or CESM2 core unit core unit is automatically
enabled when it is enabled in the PETS or ESO-1 configuration.
The esi-1 or esi-2 managed object on the core unit is activated.
→ The fault management of the esi-1 or esi-2 managed objects on the core unit is
activated.
6.3.2 PETS Synchronization via PDH Traffic Signals

In this scenario the NE timing is synchronized to a synchronization signal derived from different
clock sources:
• ESI-1 external timing input (highest priority),
• Ethernet port-1 on the core unit,
• SETS function of the SAMO1 unit plugged in slot 20,
• E1 port-1 on the LEDE1 unit plugged in slot 1,
• SHDSL port-1 on the DEFM1 unit plugged in slot 2,
• core unit internal clock source (lowest priority).
The ESO-1 clock output is locked to the PETS and shall be active when the PETS is synchro-
nized to the ESI-1 clock input and shall be squelched when the PETS is synchronized to
another clock source.

Core Unit
port-1 SyncE clock to PDH clock sources
Ethernet
NEC
Selector
es1-1 PETS clock to PDH Timing
NETG
2048 kHz PETS
eso-1
2048 kHz
SAMO1
slot-20
SETS
port-1
STM-4
LEDE1
slot-1
port-1 E1 clock to PDH clock sources

E1
DEFM1, NT function
slot-2
port-1 DSL clock to PDH clock sources

SHDSL
Figure 36: PETS synchronization via ESI, SyncE, SETS, E1, and SHDSL signals
PETS configuration, synchronous application
→ Select the PDH clock sources. Proceed as follows:

- PDH Clock Source 1 = /unit-11/port-1 (SyncE port on the core unit).
- PDH Clock Source 2 = /unit-20 (SETS of the SAMO1 unit).
- PDH Clock Source 3 = /unit-1/port-1 (E1 port on the LEDE1).
- PDH Clock Source 4= /unit-2/port-1 (SHDSL port on the DEFM1 unit).

Result: The PDH clock sources are fully configured.
→ Configure the PETS clock selection. Proceed as follows:

2. Select the parameters of ESI-1:
- Priority = 1.
- PDH Clock Source 1, Priority = 2.
- Internal, Priority = 7.
Result: The PETS clock selection is fully configured.
End of instruction
ESO configuration, synchronous application

The ESO-1 is active if ESI-1 is selected as clock source.

2. Set the ESO-1 to PETS locked:
- ESO-1 PETS-locked = true

3. Select the valid ESO-1 clock sources:

- ESI-1 squelched = false
- ESI-2 squelched = true
- PDH Clock Source 1 squelched = true
- Internal = true
End of instruction
After the configuration of the PETS and ESO check the fault free operation:
PETS and ESO status check, synchronous application

Check the fault free operation of the PETS, ESI-1 and ESO-1.
→ Check ESI-1. Proceed as follows:

1. Navigate to the ESI-1 fault management dialog:
- AP: /unit-11/neController/esi-1, Fault Management - Status (CESM1 or CESM2), or
- AP: /unit-11/sync/esi-1, Fault Management - Status (CESM3).
- LOS = Off
→ Check the PDH clock sources. Proceed as follows:

- LOSP1 = Off
- LOSP2 = Off
- LOSP3 = Off
- LOSP4 = Off
→ Check the PETS clock sources. Proceed as follows:

1. Navigate to the PETS status dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/PETS, Status.
2. Check the status of ESI-1:
- Priority = 1
- Quality Level = 13
- Priority = 2
- Quality Level = <received>
- Priority = 3
- Priority = 4


- Priority = 5
7. Check the status of the internal clock source:
- Priority = 7
→ Check the PETS clock status. Proceed as follows:

2. Check the PETS status:
- Selected Clock Source = ESI-1
- Clock Operating Mode = Locked

Result: The PDH timing functions are completely checked.
End of instruction
6.3.3 PETS Synchronization via PTP and SyncE, Port Based (Pure Hybrid)
In the synchronization application using the PTP pure hybrid mode the PETS frequency is
derived from a synchronous Ethernet port and the PETS phase is derived from a PTP port. The
same core unit port is used for synchronous Ethernet and PTP.
In this scenario the FOX61x network element is placed in a synchronization ring, i.e. it is a
boundary clock in the PTP terminology and requires two PTP ports.
The core unit port can be configured to any port type, e.g. CVP or MPLS-TP, depending of the
application. The administrative state of the ports is set to “Up”.

The WAN port extension unit EPEX1 does not support port based PTP and there-
fore no pure hybrid clock.

Port Type:
- CVP or
- PWAC or
- MPLS-TP or
- MPLS-TP VLAN subinterface Ordinary/Boundary Clock and
- None Stream
CESM3 PETS
PTP phase
Front port-1 SyncE NEC
frequency
Selector
NETG
PTP phase
Front port-2 SyncE
frequency
ESMC
Figure 37: Set-up for the PTP pure hybrid synchronization
An application with network elements using the PTP Pure Hybrid based synchronization is
shown in section 6.7.5 PTP Port and Ethernet VLAN Based, two Rings, two External Timing
Sources (on page 140).
In this scenario the NE timing is synchronized to the synchronous Ethernet/PTP port-1 of the
core unit. The second priority clock source is the core unit port-2. The clock selection algorithm
is quality level based.
The following main configuration steps have to be performed:
• The network element uses the pure hybrid PTP mode.
• The core unit port-1 and port-2 are boundary clock ports, operating as master or slave.
Enable ESMC for synchronous Ethernet.
• The core unit port-1 and port-2 are PDH (and PTP) clock sources.
PTP pure hybrid synchronization

The PETS is frequency and phase synchronized to the CESM3 port-1, alternatively to the
CESM3 port-2.
→ Configure the network element PTP clock type. Proceed as follows:

1. Navigate to the PTP configuration dialog in the FOXCST Synchronization” view:
- AP: /Synchronization/PTP, Configuration.
2. Select the PTP parameters:
- Administrative State = Up.
- PTP Transport = Ethernet (L2).
- Clock Mode = One Step.
- Clock Domain = 0.
- PTP Mode = Pure Hybrid.
- Awareness = Full Aware.
Result: The network element PTP clock type is fully configured.
→ Configure the core unit ports. Proceed as follows:

1. Navigate to the PTP port-1 configuration dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/PTP, Ports & Streams: port-1 Port Configuration.

2. Select the PTP port parameters:

- PTP Mode = Ordinary/Boundary Clock.
- Encapsulation = Ethernet.
- Forward Multicast = false.
4. Add a stream for port-1:
- Select port-1 in the ports table.
- Click the button.
5. Select the PTP stream parameters:
- Role = Master Or Slave.
- Addressing Mode = Unicast.
- Destination MAC Address = 01:1B:19:00:00:00.
6. Navigate to the SyncE port-1 configuration dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/SyncE, Ports: port-1 Port Configuration.
7. Select the synchronous Ethernet parameters:
- Method = ESMC.
9. Repeat the above steps for port-2.
Result: The core unit PTP ports are fully configured.
→ Configure the PDH clock sources. Proceed as follows:

Please note:
The PTP clock sources are automatically configured the same as the PDH clock
sources.

2. Select the parameters of PDH Clock Source 1:
- Priority = 1.
3. Select the parameters of PDH Clock Source 2:
- Priority = 2.
- Selection Algorithm = QL.

End of instruction
After the configuration of the PETS and PTP check the fault free operation:
PETS and PTP status check

Check the fault free operation of the PETS and PTP.
→ Check core unit ports. Proceed as follows:

1. Navigate to the core unit port-1 fault management dialog:
- AP: /unit-11/port-1, Fault Management - Status.
- LOS = Off.
- CLKMIS = Off (only available for non-SFP based ports).
- LOS = Off.
- CLKMIS = Off (only available for non-SFP based ports).
→ Check the PTP and PDH clock sources. Proceed as follows:

- LOSP1 = Off.
- LOSP2 = Off.
- LOPT1 = Off.
- LOPT2 = Off.

- Priority = 1
- Quality Level = <Received>
- Priority = 2
4. Check the status of PTP 1:
- Priority = 1
5. Check the status of PTP 2:
- Priority = 2


- Selection Algorithm = QL
- Clock Operating Mode = Phase-Locked
→ Check the PTP status. Proceed as follows:

1. Navigate to the PTP status dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/PTP, Status.
2. Check the PTP status:
- Clock Mode = Hybrid
- Phase Reference = PTP-1
Result: The PTP timing functions are completely checked.
End of instruction
6.3.4 PETS Synchronization via PTP, Port Based

The PETS synchronization via PTP ports is supported for the “Frequency And Phase” PTP
mode.
In this scenario the FOX61x network element is placed in a synchronization ring, i.e. it is a
boundary clock in the PTP terminology and requires two PTP ports.
The core unit port can be configured to any port type, e.g. CVP or MPLS-TP, depending of the
application. The administrative state of the ports is set to “Up”.

The WAN port extension unit EPEX1 does not support port based PTP.
Port Type:
- CVP or
- PWAC or
- MPLS-TP or
- MPLS-TP VLAN subinterface Ordinary/Boundary Clock and
- None Stream
CESM3 PETS
PTP phase
Front port-1 NEC
frequency
Selector
NETG
PTP phase
Front port-2
frequency
Figure 38: Set-up for the PTP frequency and phase synchronization
In this scenario the NE timing is synchronized to the PTP port-1 of the core unit. The second pri-
ority clock source is the core unit port-2. The clock selection algorithm is priority based. PTP
packets travel always from a PTP master to a PTP slave, i.e. they cannot reverse the synchroni-
zation direction.
• The network element uses the “Frequency And Phase” PTP mode.

• The core unit port-1 and port-2 are boundary clock ports, operating as master or slave.
• The core unit port-1 and port-2 are PTP clock sources.
PTP frequency and phase synchronization

The PETS is frequency and phase synchronized to the CESM3 port-1, alternatively to the
CESM3 port-2.

- Clock Domain = 0.
- PTP Mode = Frequency And Phase.

1. Navigate to the PTP port-1 configuration dialog in the FOXCST “Synchronization” view:
- PTP Mode = Ordinary/Boundary Clock.
- Encapsulation = Ethernet.
4. Add a stream for port-1:
- Select port-1 in the ports table.
- Click the button.
5. Select the PTP stream parameters:
- Role = Master Or Slave.
- Addressing Mode = Unicast.
- Destination MAC Address = 01:1B:19:00:00:00.
→ Configure the PTP clock sources. Proceed as follows:

2. Select the PTP-1 source:
- PTP-1 = /unit-11/port-1.
3. Select the PTP-2 source:
- PTP-2 = /unit-11/port-2.
Result: The PTP clock sources are fully configured.


2. Select the parameters of PTP-1:
- Priority = 1.
3. Select the parameters of PTP-2:
- Priority = 2.
End of instruction

→ Check core unit ports. Proceed as follows:

- LOS = Off.
- LOS = Off.

- LOPT1 = Off.
- LOPT2 = Off.

2. Check the status of PTP-1:
- Priority = 1


- Priority = 2

- Selected Clock Source = PTP-1

- Clock Mode = Packet
End of instruction
6.3.5 PETS Synchronization via PTP, Ethernet VLAN Based

The PETS synchronization via PTP Ethernet VLANs is supported for the “Frequency And
Phase” PTP mode.
Please note:
The PTP Ethernet VLAN ID must not be used as management VLAN ID. Select a
VLAN ID that is not used by a management VLAN.
→ Please refer to [1KHW028522] User Manual “Management Communication”
In the synchronization application using the PTP Ethernet VLAN based mode the PETS fre-
quency and phase are derived from a PTP port.
The PTP Ethernet VLAN is a member of the FOX61x Switch.
The example FOX61x network element is placed at the border of a MPLS-TP network. It derives
its timing information directly from a PTP Grand Master via an Ethernet link, and forwards it as a
transparent clock towards the MPLS-TP network, i.e. it is an ordinary clock and an end-to-end
transparent clock in the PTP terminology and requires two PTP ports.
The core unit port type connecting to the PTP Grand Master is set to CVP with the port VLAN ID
100 corresponding to the PTP Ethernet VLAN ID. The PTP VLAN has to be added as a member
of the FOX61x Switch.
The core unit port type connecting to the MPLS-TP network is set to MPLS-TP. The administra-
tive state of the ports is set to “Up”.

PTP Transport = Ethernet (L2)

PTP Mode = Frequency And Phase
PTP VLAN (Ordinary/Boundary Clock)

and Stream
Port Type: Ordinary/Boundary and
- CVP Transparent Clock
CESM3 PETS
NEC
Port Mode: Access PTP VLAN ID PTP VLAN ID frequency
Front port-1 PTP PTP NETG
PVID = PTP VLAN ID and phase
FOX61x Switch
Ordinary/Boundary and PW TN
Transparent Clock
PTP VLAN ID VPLS
SVI
Port Type: Forwarder
- MPLS-TP PW TN
Front port-2 PTP
Figure 39: Set-up for the PTP Ethernet VLAN interface synchronization
An application with network elements using the PTP Ethernet VLAN based synchronization is
shown in section 6.7.5 PTP Port and Ethernet VLAN Based, two Rings, two External Timing
Sources (on page 140).
In this scenario the NE timing is synchronized to the PTP VLAN received on port-1 of the core
unit. The PTP timing is forwarded to the core unit port-2. The clock selection algorithm is priority
based.
• The network element uses the “Ethernet (L2)” PTP Transport and the “Frequency And
Phase” PTP mode.
• The core unit port-1 is operating as ordinary and end-to-end transparent clock port. The core
unit port-2 is operating as end-to-end transparent clock port. The PTP VLAN stream is oper-
ating as slave.
• The core unit PTP Ethernet VLAN is a PTP clock source. It has to be selected as PETS
clock.
• The PTP Ethernet VLAN is transported via the MPLS-TP network in a specific VPLS.
PTP VLAN interface synchronization

The PETS is frequency and phase synchronized to the PTP Ethernet VLAN received on the
CESM3 port-1.

- Clock Domain = 0.


1. Navigate to the core unit port-1 configuration dialog in the FOXCST “Synchronization” view:
- PTP Mode = Ordinary/Boundary and Transparent Clock.
- Encapsulation = According Port Type.
→ Configure the PTP VLAN interface. Proceed as follows:

1. Navigate to the core unit Ports & Streams configuration dialog in the FOXCST “Synchroniza-
tion” view:
- AP: /Synchronization/PTP, Ports & Streams.
2. Add a PTP VLAN interface:
- Click the button.
- VLAN ID = 100.
- Role = Slave.
- CoS = CoS 7.
3. Execute “OK”.
4. Add a stream for the VLAN:
- Select the VLAN-100 in the interfaces table.
- Click the button.
5. Select the VLAN-100 stream parameters:
- Stream = stream-1.
- Destination MAC Address = <MAC address of the PTP Grand Master>.
Result: The core unit PTP ports and VLAN are fully configured.

2. Select the PTP source 1:
- PTP Source PTP-1 = VLAN-100/stream-1.
Result: The PTP clock source is fully configured.

2. Select the parameters of PTP Source PTP-1:
- Priority = 1.


→ Configure the MPLS-TP VPLS service. Proceed as follows:

1. For the transport of the PTP VLAN a specific VPLS has to be set up using MPLS LSP labels
from the PTP LSP label range. The SVI VLAN ID is the same as the PTP VLAN ID.
2. For the configuration of a VPLS MPLS-TP service please refer to [1KHW028618] User Man-
ual “MPLS-TP Services”.
Result: The PTP VLAN VPLS is fully configured.
End of instruction

→ Check the core unit ports. Proceed as follows:

- LOS = Off.
- LOS = Off.

- LOPT1 = Off.

- Priority = 1



End of instruction
6.3.6 PETS Synchronization via PTP, IP VLAN Based

The PETS synchronization via PTP IP VLANs is supported for the “Frequency And Phase” PTP
mode.
Please note:
The PTP IP VLAN ID must not be used as management VLAN ID. Select a VLAN
ID that is not used by a management VLAN.
In the synchronization application using the PTP IP VLAN based mode the PETS frequency and
phase are derived from a PTP port.
The PTP IP VLAN is a member of the FOX61x Switch.
The example FOX61x network element is placed at the border of a MPLS-TP network. It derives
its timing information directly from a PTP Grand Master via a PTP slave IP VLAN. At the same
time the example FOX61x network element acts as a clock master for the subordinate network
elements. It provides the local PTP timing via another PTP master IP VLAN towards the MPLS-
TP network, i.e. it is an ordinary clock and a boundary clock in the PTP terminology and
requires two PTP ports.
The core unit port type connecting to the PTP Grand Master is set to CVP with the port VLAN ID
100 corresponding to the PTP slave IP VLAN ID. The PTP slave IP VLAN has to be added as a
member of the FOX61x Switch.
The core unit and/or WAN port extension unit port type connecting to the MPLS-TP network is
set to MPLS-TP. The VPLS service transports the PTP master IP VLAN. The PTP master IP
VLAN has to be added as a member of the FOX61x Switch
The administrative state of the ports is set to “Up”.

PTP Transport = UDP/IPv4 (L3)

PTP Mode = Frequency And Phase
PTP slave VLAN

(Ordinary/Boundary Clock) and Stream
Port Type: Ordinary/Boundary and
- CVP Transparent Clock CESM3 PETS
NEC
Port Mode: Access PTP slave VLAN ID frequency
Front port-1 PTP PTP NETG
PVID = PTP VLAN ID and phase
PTP
FOX61x Switch
PTP master VLAN

Ordinary/Boundary and (Ordinary/Boundary Clock) PW TN
Transparent Clock
PTP master VLAN ID VPLS
SVI
Port Type: Forwarder
- MPLS-TP PW TN
Front port-2 PTP
Figure 40: Set-up for the PTP IP VLAN interface synchronization
An application with network elements using the PTP IP VLAN based synchronization is shown
in section 6.7.4 PTP IP VLAN Based, two Rings, two External Timing Sources (on page 136).
In this scenario the NE timing is synchronized to the PTP slave IP VLAN received on port-1 of
the core unit. The PTP timing is forwarded to the core unit port-2 via the PTP master IP VLAN.
• The network element uses the “UDP/IPv4 (L3)” PTP Transport and the “Frequency And
Phase” PTP mode.
• The core unit port-1 is operating as ordinary and end-to-end transparent clock port. The PTP
VLAN stream is operating as slave. The core unit port-2 is operating as master clock port.
There is no PTP VLAN stream.
• The core unit PTP slave IP VLAN is a PTP clock source. It has to be selected as PETS
clock.
• The PTP master IP VLAN is transported via the MPLS-TP network in a specific VPLS.
PTP VLAN interface synchronization

The PETS is frequency and phase synchronized to the PTP slave IP VLAN received on the
CESM3 port-1.

- PTP Transport = UDP/IPv4 (L3).
- Clock Domain = 0.


1. Navigate to the core unit port-1 configuration dialog in the FOXCST “Synchronization” view:
- PTP Mode = Ordinary/Boundary and Transparent Clock.
- Encapsulation = According Port Type.
→ Configure the PTP slave IP VLAN interface. Proceed as follows:

tion” view:
2. Add the PTP slave VLAN interface:
- Click the button.
- VLAN ID = 100.
- Role = Slave.
- Local IP Address = <local source IP address>.
- Netmask = <netmask of the PTP network towards the PTP Grand Master>.
- CoS = CoS 7.
4. Add a stream for the slave VLAN:
- Select the VLAN-100 in the interfaces table.
- Click the button.
5. Select the VLAN-100 stream parameters:
- Stream = stream-1.
- Destination IP = <IP address of the PTP Grand Master>.
Result: The core unit PTP ports and slave VLAN are fully configured.
→ Configure the PTP master IP VLAN interface. Proceed as follows:

tion” view:
2. Add the PTP slave VLAN interface:
- Click the button.
- VLAN ID = 101.
- Role = Master.
- Local IP Address = <local source IP address>.
- Netmask = <netmask of the PTP network towards the MPLS-TP network>.
- CoS = CoS 7.
Result: The core unit PTP ports and master VLAN are fully configured.


2. Select the PTP source 1:
- PTP Source PTP-1 = VLAN-100/stream-1.
Result: The PTP clock source is fully configured.

2. Select the parameters of PTP Source PTP-1:
- Priority = 1.
→ Configure the MPLS-TP VPLS service. Proceed as follows:

1. For the transport of the PTP VLAN a specific VPLS has to be set up using MPLS LSP labels
from the PTP LSP label range. The SVI VLAN ID is the same as the PTP slave IP VLAN ID.
2. For the configuration of a VPLS MPLS-TP service please refer to [1KHW028618] User Man-
ual “MPLS-TP Services”.
Result: The PTP VLAN VPLS is fully configured.
End of instruction

→ Check the core unit ports. Proceed as follows:

- LOS = Off.
- LOS = Off.

- LOPT1 = Off.


- Priority = 1


→ Check the port PTP counters. Proceed as follows:

1. Navigate to the PTP counters dialog in the FOXCST “Synchronization” view:
- AP: /Synchronization/PTP, Port & Streams - User Counters (of a Ordinary/Boundary
Clock).
2. Check the number of PTP packets:
- The packet counters must increase.
→ Check the VLAN stream PTP counters. Proceed as follows:

- AP: /Synchronization/PTP, Port & Streams - User Counters (of a VLAN stream).
2. Check the number of PTP packets:
- The packet counters must increase, except the “Lost Messages” counters.
- If there is no contract with the Master, only the Signaling Messages will increase.
End of instruction
6.3.7 Plesiochronous Application

In the plesiochronous TDM application the incoming and outgoing TDM signals are not synchro-
nized to the plesiochronous equipment timing source (PETS) of the FOX61x. The PETS clock
source can be free running from its internal oscillator or be synchronized to the TCXO located
on the CEPI1 unit (if available), which provides a clock stability of an SDH equipment clock
(SEC).
The P12 signal termination mode must be configured to
− Transparent.

Core Unit
PETS
NEC
PETS clock to PDH Timing
NETG
port-1 plesiochronous P12 timing

E1 LEDE1
slot-1
port-2
E1
Figure 41: PETS free running
In this scenario the NE timing is free running, i.e. the PETS is synchronized to the internal oscil-
lator. No external clock inputs and outputs are used.
PETS configuration, plesiochronous application

The PETS is synchronized to the internal oscillator.

2. Select the parameters of the internal clock:
- Priority = 1.
The internal clock source has priority 7 (= lowest) by default.
End of instruction
After the configuration of the PETS check the fault free operation:
PETS status check, plesiochronous application

Check the fault free operation of the PETS.



- Priority = 1

- Selected Clock Source = Internal
- Clock Operating Mode = Free Running
End of instruction
6.4 ESO Synchronization
6.4.1 ESO-1 Synchronization, PETS Locked

An application with the PETS-locked ESO-1 output is described in section 6.3.2 PETS Synchro-
nization via PDH Traffic Signals (on page 83).
6.4.2 ESO-1 Synchronization, non PETS Locked

In this scenario the ESO-1 signal is directly synchronized to a synchronization signal derived
from the E1 port-1 on the LEDE1 unit plugged in slot 1. The ESO-1 clock source has to be con-
figured to the “unit-1/port-1” input.
The ESO-1 timing signal is regenerated in an external SSU (Synchronization Supply Unit) and
fed to the ESI-1 input. The PETS is consequently synchronized to the ESI-1 clock source.
The ESO-1 output is squelched when the E1 clock source is not available.

LEDE1
slot-1
port-1 E1 clock to PDH clock sources

E1
Core Unit PETS

NEC
Selector
PETS clock to PDH Timing
NETG
clock from esi-1
Selector
clock to eso-1
esi-1 eso-1
2048 kHz 2048 kHz
SSU
Figure 42: ESO-1 non PETS-locked synchronization via an E1 signal
ESO-1 configuration, non PETS-locked application

The ESO-1 is active if the clock source 1 is selected as clock source.

2. Set the ESO-1 to non PETS locked:
- ESO-1 PETS-locked = false
3. Select the parameters of the PDH clock source 1:
- Priority = 1.
- Internal, Priority = Disabled.


- ESO-1 Selection Algorithm = Priority.
End of instruction
PETS configuration, synchronous application
→ Select the PDH clock sources. Proceed as follows:

- PDH Clock Source 1 = /unit-1/port-1 (E1 port on the LEDE1).

- Priority = 1.
- Quality Level = 4 (QL of SSU-A, primary level SSU).
- Internal, Priority = 7.
- Quality Level = 11 (QL of SEC).
End of instruction
After the configuration of the PETS and ESO check the fault free operation:
PETS and ESO status check, synchronous application

Check the fault free operation of the PETS, ESI-1 and ESO-1.

- LOS = Off

→ Check the ESO-1 clock sources. Proceed as follows:

- ECSL = Off
- ESOSNP = Off


- Priority = 1
- Quality Level = 4
- Priority = 7

End of instruction
6.4.3 ESO-2 Synchronization, SETS Locked

An application with the SETS-locked ESO-2 output is described in section 6.2.2 SETS Synchro-
nization via SDH Traffic Signals (on page 76).
6.4.4 ESO-2 Synchronization, non SETS Locked

In this scenario the ESO-2 output signal of the SAMO1 unit plugged in slot 20 is directly syn-
chronized to the STM-4 traffic signal connected to the port-1. The ESO-2 clock source has to be
configured to the “Port 1” input.
The ESO-2 timing signal is regenerated in an external SSU (Synchronization Supply Unit) and
fed to the ESI-2 input. The SETS is consequently synchronized to the ESI-2 clock source.
The ESO-2 output is squelched when the STM-4 clock source is not available.

SAMO1 SETS
slot-20
SEC
Selector
SETS clock to STM Tx
SETG
port-1
Selector
STM-4 clock to eso-2
esi-2 clock source
clock from esi-2

clock to eso-2
esi-2 eso-2
2048 kHz 2048 kHz
SSU
Figure 43: ESO-2 non SETS-locked synchronization via an STM-4 signal
ESO configuration
The ESO-2 is non SETS locked, ESO-2 is squelched if the internal clock is selected as clock
source.

1. Navigate to the SAMO1 ESO configuration dialog:
- AP: /unit-20, Configuration - ESO-2.
2. Operate the ESO-2 in the non SETS locked mode:
- ESO-2 SETS Locked = false.
4. Select the parameters of the Port 1 (STM-4/STM-1) clock source:
- Priority = 1.


- Internal, Priority = Disabled.
- ESO-2 Selection Algorithm = Priority.
→ Configure the ESO-2 selection. Proceed as follows:

1. Navigate to the ESO configuration dialog in the FOXCST “Synchronization” view:
2. Select the unit-20 as ESO-2 clock source:
- SDH Clock Source = /unit-20.
Result: The ESO-2 clock selection is fully configured.
End of instruction
SETS configuration
The SETS is synchronized to the ESI-2 timing signal.

- Priority = 1.
- Quality Level = 4 (QL of SSU-A, primary level SSU).
- Priority = 10.
- Quality Level = 11 (QL of SEC).
6. Set the administrative state of the esi-2 port on the core unit to up (not required on the
CESM1 and CESM2 unit:
- AP: /unit-11/sync/esi-2, Main - Admin And Oper Status.
- Administrative Status, State = Up.
End of instruction
After the configuration of the SETS and ESO check the fault free operation:

SETS and ESO status check

- LOS = Off
→ Check the ESO-2 clock sources. Proceed as follows:

1. Navigate to the SAMO1 fault management dialog:
- AP: /unit-20, Fault Management - Status.
- ECSL = Off
- ESOSNP = Off
→ Check the ESO-2 status on the SDH service unit. Proceed as follows:
- AP: /unit-20, Status - ESO-2.
- Selected Clock Source = Port 1 (STM-4/STM-1)

- Clock Output Status = Active

1. Navigate to the SETS status dialog:
- Priority = 1
- Quality Level = 4
- Priority = 10
→ Check the SETS clock status. Proceed as follows:

1. Navigate to the SETS status dialog:


End of instruction
6.5 SDH/PDH Synchronization Setup in a Tree Network

SDH or PDH synchronization setups in tree networks have a low risk of timing loops, provided
that the tree structure is maintained even with failures in the synchronization network. The prior-
ity based clock selection algorithm is applied.
The synchronization with tree networks can be setup with the FOX61x for SDH and PDH net-
works using any of the available SDH and/or PDH clock sources.
The detailed configuration of the FOX61x network element is described in section 6.2 SDH Syn-
chronization (on page 75) and section 6.3 PDH Synchronization (on page 82).
6.5.1 One External Timing Source

The synchronization setup in this example is based a simple network structure with 5 network
elements, see “A” in Figure 44. The 5 network elements are interconnected with 7 links.
Following the rules listed in section 4.4 Commissioning of a Synchronization Network (on
page 24) an active synchronization tree is applied from the top layer (NE11, connected to the
PRC) via the middle layer (NE21 and NE22) to the lowest layer (NE31 and NE32), see “B” in
Figure 44.
In order to have at least two synchronization paths to each network element some standby syn-
chronization paths are defined in addition to the active synchronization paths, see “C” in Figure
44.
Please note:
The NE21 can only be synchronized from NE11. There is no standby synchroniza-
tion path available. In a failure case the NE21 timing is free running, or in holdover
state.
→ In order to provide a high quality timing source the NE21 could be equipped
with an SSU.
With the setup chosen in “C” of Figure 44
• the synchronization is distributed in a tree structure top down,
• the synchronization is forwarded on a link always in the same direction,
• no timing loops are possible,
• all network elements except NE11 and NE21 have two timing sources.

NE11
A
NE21 NE22
NE31 NE32
B PRC
C PRC
NE11 NE11
NE21 NE22 NE21 NE22
NE31 NE32 NE31 NE32
active timing path

standby timing path
Figure 44: SDH/PDH synchronization tree, one source
The synchronization network example in Figure 45 shows an SDH network, but the same princi-
ple can be applied to a PDH network.
NE11 is the timing master of the synchronization tree, i.e. it provides the timing from the ESI
input to the subtended NEs. Port-1 and port-2 of NE11 are not used for synchronization.

ESI
SETS Clock Select ion

Source Priority
ESI 1 NE11
port-1 disabled
port-2 disabled Selected Clock
Source: ESI
internal 10
port-2 port-1
SETS Clock Selection

port-1 Source Priority port-1
port-1 1 SETS Clock Select ion
port-2 disabled Source Priority
port-3 disabled port-1 1
NE21 internal 10
NE22 port-2 2
port-2 port-2 port-3 disabled
Source: port-1 Source: port-1 port-4 disabled
internal 10
port-3 port-4
port-3
SETS Clock Selection port-1

Source Priority
port-1 port-2 port-1 1
port-2 2
SETS Clock Select ion NE31 internal 10
NE32
Source Priority port-3 port-2
port-1 2 Selected Clock Selected Clock
port-2 1
port-3 disabled
internal 10
active timing path
standby timing path
Figure 45: SDH synchronization tree, no failure
If the ESI timing source at NE11 fails NE11 selects its internal timing source. For NE11 there is
no other timing source available.
All other NEs keep their clock selection unchanged.

ESI

Source Priority
ESI 1 NE11
port-1 disabled
Source: Internal
internal 10
port-2 port-1

NE21 internal 10
NE22 port-2 2
internal 10
port-3 port-4
port-3

Source Priority
port-2 2
NE32
port-2 1
port-3 disabled
internal 10
active timing path
standby timing path
Figure 46: SDH synchronization tree, ESI at NE11 failed
If NE11 fails NE21 switches to the internal timing source and becomes the timing master. NE22
switches to port-2. The other NEs keep their clock selection unchanged.

ESI

Source Priority
ESI 1 NE11
port-1 disabled
Source: Internal
internal 10
port-2 port-1

NE21 internal 10
NE22 port-2 2
Source: Internal Source: port-2 port-4 disabled
internal 10
port-3 port-4
port-3

Source Priority
port-2 2
NE32
port-2 1
port-3 disabled
internal 10
active timing path
standby timing path
Figure 47: SDH synchronization tree, NE11 failed
In case the link between NE11 and NE22 fails the NE22 receives no valid timing signal on port-
1. NE22 selects the timing from port-2. The other NEs keep their clock selection unchanged.

ESI

Source Priority
ESI 1 NE11
port-1 disabled
Source: Internal
internal 10
port-2 port-1

NE21 internal 10
NE22 port-2 2
internal 10
port-3 port-4
port-3

Source Priority
port-2 2
NE32
port-2 1
port-3 disabled
internal 10
active timing path
standby timing path
Figure 48: SDH synchronization tree, link between NE11 and NE22 failed
6.6 SDH/PDH Synchronization Setup in a Ring Network

SDH or PDH synchronization setups in ring networks have a high risk of timing loops. The qual-
ity level based clock selection algorithm with the associated routing tables avoids the timing dis-
tribution in reverse direction, i.e. in the direction the timing information is received the QL value
“do not use” is inserted.
In many cases this feature is sufficient to avoid timing loops. There are scenarios, e.g. when
using more than one timing source in a ring network, where QL mapping tables must be used to
interrupt a circular QL forwarding.
Please note:
The SDH clock sources of the SETS support QL mapping tables at the SETS input
and output.
Please note:
The SyncE clock sources of the PETS support QL mapping tables at the PETS
input and output.
The other PETS clock sources (PDH, PTP, …) do not support QL mapping tables.
The detailed configuration of the FOX61x network element is described in section 6.2 SDH Syn-
chronization (on page 75) and section 6.3 PDH Synchronization (on page 82).

6.6.1 One External Timing Source, Without SSU

The synchronization network example in Figure 49 shows an SDH network, but the same princi-
ple can be applied to a PDH network.
NE1 is the timing master of the SDH ring, i.e. it provides the timing from the ESI input to the
subtended NEs. Port-1 and port-2 of NE1 are not used for synchronization to prevent a timing
loop. No QL mapping tables are used.
The port routing tables have to be interpreted as follows:
• The QL of the outgoing signal at the port is set according to the usability entry of the selected
network element timing source.
Example: NE2 in Figure 49, port-1:
− The QL is set to “do not use” (= 15) if the NE2 selects port-1 as timing source.
− The QL is set to the incoming QL value of port-2 if the NE2 selects port-2 as timing
source.
− The QL is set to the QL value of the internal oscillator (= 11) if the NE2 selects the inter-
nal oscillator as timing source.


Source Priority QL
ESI 1 1
port-1 disabled received
port-2 disabled received ESI
internal 10 11
Port-2 Rout ing Table Port-1 Rout ing Table

Source Usability Source Usability
ESI can be used NE1 ESI can be used
internal can be used port-2 Selected Clock
port-1 internal can be used
Source: ESI
QL: 1
Port-1 Rout ing Table

Source Usability Port-2 Routing Table
port-1 do not use Source Usability
port-2 can be used port-1 can be used
internal can be used port-2 do not use
port-1 port-2
SETS Clock Selection SETS Clock Selection
Source Priority QL Source Priority QL
NE2 port-1 1 received port-1 1 received NE4
Selected Clock port-2 2 received port-2 2 received Selected Clock
Source: port-1 internal 10 11 Source: port-1
QL: 1 QL: 1
port-2 port-1
Port-2 Rout ing Table Port-1 Routing Table
port-1 can be used port-1 do not use
port-2 do not use port-2 can be used
internal can be used

Source Usability NE3 Source Usability
port-1 do not use port-1 Selected Clock
port-2 port-1 can be used
Source: port-1
QL: 1

Source Priority QL
port-1 1 received active timing path
port-2 2 received standby timing path
Figure 49: SDH ring, one source, no failure
If the ESI timing source at NE1 fails NE1 selects its internal timing source. For NE1 there is no
other available timing source.
NE2 still selects port-1 as clock source. The QL of port-1 and of the internal timing source are
both 11, but port-1 has the higher priority.


Source Priority QL
ESI 1 1
internal 10 11

Source: internal
QL: 11

port-1 port-2
QL: 11 QL: 11
port-2 port-1

Source: port-1
QL: 11

Source Priority QL
Figure 50: SDH ring, one source, ESI at NE1 failed
If NE1 fails NE2 switches to the internal timing source and becomes the timing master.


Source Priority QL
ESI 1 1
internal 10 11

Source: ESI
QL: 1

port-1 port-2
Source: internal internal 10 11 Source: port-1
QL: 11 QL: 11
port-2 port-1

Source: port-1
QL: 11

Source Priority QL
Figure 51: SDH ring, one source, NE1 failed
In case the link between NE2 and NE3 fails the NE3 receives no valid timing signal on port-1.
NE3 selects the timing from port-2 and sends “do not use” on this port towards NE4. Conse-
quently NE4 selects the timing also from port-2 and receives its timing from NE1.


Source Priority QL
ESI 1 1
internal 10 11

Source: ESI
QL: 1

port-1 port-2
QL: 1 QL: 1
port-2 port-1

Source: port-2
QL: 1

Source Priority QL
Figure 52: SDH ring, one source, link between NE2 and NE3 failed
6.6.2 Two External Timing Sources, Without SSU

The synchronization network example in Figure 53 shows an SDH network. But since most
PETS clock sources do not support the routing tables the same principle cannot be applied to a
PDH network.
subtended NEs. ESI is given a fixed QL=1. The potential circular forwarding of timing informa-
tion in the ring network is interrupted at NE1 for the QL values 1 and 11. Correspondingly the
input mapping tables of port-1 and port-2 of NE1 map a received QL value 1 or 11 to the QL
value 15.

NE3 is the backup timing master of the SDH ring, i.e. it provides the timing from the ESI input to
the other NEs if the ESI clock source at NE1 fails. ESI is given a fixed QL=2. The potential cir-
cular forwarding of timing information in the ring network is interrupted at NE3 for the QL value
2. Correspondingly the input mapping tables of port-1 and port-2 of NE3 map a received QL
value 2 to the QL value 15.
Source Priority QL
ESI 1 1
port-1 2 received
port-2 3 received
internal 10 11
ESI
ESI can be used ESI can be used
port-2 do not use
NE1 port-2 can be used
port-2 Selected Clock
Source: ESI
Port-2 Input Mapping Table QL: 1 Port-1 Input Mapping Table
Received QL Adapted QL Received QL Adapted QL
1 15 1 15
11 15 11 15

port-1 port-2
QL: 1 QL: 1
port-2 port-1

Source: port-1
2 15 2 15

Source Priority QL
ESI
ESI 1 2 active timing path
port-2 3 received
Figure 53: SDH ring, two sources, no failure
If the ESI timing source at NE1 fails NE3 selects its ESI timing source and becomes the timing
master.


Source Priority QL
ESI 1 1
port-1 2 received
port-2 3 received
internal 10 11
ESI
port-2 do not use
Source: port-1
1 15 1 15
11 15 11 15

port-1 port-2
QL: 2 QL: 2
port-2 port-1

Source: ESI
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 54: SDH ring, two sources, ESI at NE1 failed
If there is in addition a link break between NE3 and NE4 the timing distribution is rerouted clock
wise via NE2 and NE1 to NE4.


Source Priority QL
ESI 1 1
port-1 2 received
port-2 3 received
internal 10 11
ESI
port-2 do not use
Source: port-2
1 15 1 15
11 15 11 15

port-1 port-2
QL: 2 QL: 2
port-2 port-1

Source: ESI
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 55: SDH ring, two sources, ESI at NE1 failed and link failure between NE3 and NE4
Assume a third failure with the ESI loss of signal at NE3. In this case NE1 takes over the timing
master role and switches to its internal timing source.


Source Priority QL
ESI 1 1
port-1 2 received
port-2 3 received
internal 10 11
ESI
port-2 do not use
Source: internal
1 15 1 15
11 15 11 15

port-1 port-2
QL: 11 QL: 11
port-2 port-1

Source: port-1
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 56: SDH ring, two sources, ESI at NE1 and NE3 failed and link failure between NE3 and
NE4
6.6.3 One External Timing Source, With SSU

An SSU connected with 2048 kHz clock signals is not able to transport an SSM, i.e. cannot
receive a QL value via ESI and cannot transmit a QL value via ESO. It is therefore necessary to
use a fixed QL value for the ESI source in the SETS configuration.
In an NE that outputs a received timing from a traffic signal to ESO (non SETS-locked mode)
and synchronizes itself to the SSU timing from ESI, the fixed ESI QL value and the routing

tables for the traffic ports must be controlled according to the used timing source synchronizing
the SSU. See Figure 57:
A Source Usability
QL = 15
NE
QL = 2
Source Usability
ESI do not use ESI can be used
port-1 do not use Selected Clock port-1 can be used
port-2 can be used
port-1 Source: esi port-2 port-2 do not use
QL: 2
internal can be used internal can be used
SETS
QL = 2 QL = 2
squelch > 4 eso esi
ESO Clock Select ion SETS Clock Select ion
port-1 1 received ESI 1 2
port-2 2 received SSU port-1 2 received
Selected Clock port-2 3 received
Source: internal 10 11
eso from port-1

B Source Usability
QL = 2
NE
QL = 2
Source Usability
ESI can be used ESI do not use
port-2 can be used
QL: 2
SETS
QL = 11 QL = 15
ESO Clock Select ion

squelch > 4 eso esi SETS Clock Select ion
port-1 1 received ESI 1 2
eso from port-2

C Source Usability
QL = 4
NE
QL = 11
Source Usability
port-2 can be used
QL: 4
SETS
QL = 11 QL = 4
squelch > 4 eso esi
ESO Clock Select ion SETS Clock Select ion
port-1 1 received squelched ESI 1 4
holdover
active timing path
standby timing path
Figure 57: Control of routing tables and QL with SSU
In case A the SSU is synchronized to the received timing signal of port-1. The ESI QL value has
to be set to the received QL value “2”. In the routing table of port-1 the usability of ESI must be
set to “do not use”.
In case B the SSU is synchronized to the received timing signal of port-2 since the QL value of
port-1 is 11. The ESI QL value has to be set to the received QL value “2”. In the routing table of
port-1 the usability of ESI can be set to “can be used”, in the routing table of port-2 the usability
of ESI must be set to “do not use”.
In case C the SSU is in holdover mode since the QL values of port-1 and port-2 are 11, and as
a consequence the ESO output is squelched. An SSU in holdover or free running mode has a

QL value of 4. The ESI QL value has to be set to “4”. In the routing table of port-1 and port-2 the
usability of ESI can be set to “can be used”.
Please note:
The FOX61x does not support the automatic control of the routing tables and ESI
QL values when it is synchronized via an SSU. These features will be available in a
future release.
→ Use a higher layer management system to control the routing tables and ESI
QL values, or
→ do not use the SSU timing to synchronize networks elements which transport
the synchronization signals for the SSU, i.e. no backward synchronization, or
→ use other measures to avoid a timing loop in the synchronization network. See
section 4.4.3 Specific Applications in Synchronization Networks (on page 30).
The synchronization example setup described below is the same as in section 6.6.1 One Exter-
nal Timing Source, Without SSU (on page 117), with the addition of an SSU that forwards the
regenerated PRC timing to NE5. This scenario does not make use of ESI QL value modifica-
tions.
subtended NEs. The potential circular forwarding of timing information in the ring network is
interrupted at NE1 for the QL values 2 and 11. Correspondingly the input mapping tables of
port-1 and port-2 of NE1 map a received QL value 2 or 11 to the QL value 15.
The SSU is synchronized to one of the timing signals received at NE3. The SSU timing is then
fed back to NE3 and forwarded to NE5. The ESI QL value in NE3 is set to “4” reflecting the fact
that the timing source has at least the quality of an SSU. The potential circular forwarding of tim-
ing information in the ring network is interrupted at NE3 for the QL value 4. Correspondingly the
input mapping tables of port-1 and port-2 of NE3 map a received QL value 4 to the QL value 15.
The ESI QL value in NE5 is set to “2” reflecting the fact that it is initially synchronized to a PRC.
Alternatively the ESI QL value in NE5 can be set to “4” reflecting the fact that the timing source
has at least the quality of an SSU.
This quality level is then forwarded by the NE5 on all its traffic ports.

PRC
ESI

Source: ESI
2 15 2 15
11 15 11 15
Source Priority QL
ESI 1 2
port-1 2 received
port-2 3 received
Port-1 Rout ing Table internal 10 11
port-2 do not use
port-1 port-2
QL: 2 QL: 2
port-2 port-1

Source Priority QL
ESI 1 4
Port-1 Rout ing Table port-1 2 received
Source Usability port-2 3 received
ESI can be used
port-1 do not use
port-2 can be used Port-2 Routing Table
NE3 Source Usability
Port-1 Input Mapping Table port-1 port-2 ESI can be used
Received QL Adapted QL Selected Clock port-1 can be used
Source: ESI
4 15 QL: 4 port-2 do not use
ESO Clock Selection Port-2 Input Mapping Table

Source Priority QL Received QL Adapted QL
port-1 1 received eso esi 4 15
port-2 2 received squelch > 4
SSU
Selected Clock
Source:
eso from port-1
esi
Source Priority QL
NE5 ESI 1 2
internal 10 11
Selected Clock
Source: esi Port-n Routing Table
QL: 2
active timing path Source Usability
ESI can be used
standby timing path
Figure 58: SDH ring with SSU, one source, no failure
In case the link between the PRC source and NE1 fails the NE1 first switches to its internal tim-
ing source with QL value 11. This QL value is propagated to NE3 and the ESO output is

squelched: The SSU goes to the holdover state. The NE3 still receives a valid timing signal on
the ESI port. The corresponding QL value 4 is then propagated into the ring network.
PRC
ESI

Source: port-1
2 15 2 15
11 15 11 15
Source Priority QL
ESI 1 2
port-1 2 received
port-2 3 received
Port-1 Rout ing Table internal 10 11
port-2 do not use
port-1 port-2
QL: 4 QL: 4
port-2 port-1

Source Priority QL
ESI 1 4
Port-1 Rout ing Table port-1 2 received
Source Usability port-2 3 received
ESI can be used
port-1 do not use
port-2 can be used Port-2 Routing Table
NE3 Source Usability
Port-1 Input Mapping Table port-1 port-2 ESI can be used
Received QL Adapted QL Selected Clock port-1 can be used
Source: ESI
4 15 QL: 4 port-2 do not use
ESO Clock Selection Port-2 Input Mapping Table

Source Priority QL Received QL Adapted QL
port-1 1 received eso esi 4 15
port-2 2 received squelch > 4
SSU
Selected Clock
Source:
holdover
esi
Source Priority QL
NE5 ESI 1 2
internal 10 11
Selected Clock
Source: esi Port-n Routing Table
QL: 2
active timing path Source Usability
ESI can be used
standby timing path
Figure 59: SDH ring with SSU, one source, link between PRC and NE1 failed

6.7 PTP Synchronization Setup in a Ring Network
6.7.1 PTP Port Based

The synchronization using the PTP port based approach is handled the same way as with any
other PDH clock source. Please refer to section 6.6 SDH/PDH Synchronization Setup in a Ring
Network (on page 116).
The detailed configuration of the FOX61x network element is described in section 6.3.3 PETS
Synchronization via PTP and SyncE, Port Based (Pure Hybrid) (on page 87) and section 6.3.4
PETS Synchronization via PTP, Port Based (on page 91).

The PTP port based mode is not supported with the WAN port extension unit
EPEX1.
6.7.2 PTP Ethernet VLAN Based

The synchronization using the PTP Ethernet VLAN based approach can make use of an MPLS
VPLS service transporting the PTP packets from a network element connected to the PTP
Grand Master Clock to all other network elements.
The example network is a ring network with four network elements NE1 to NE4, see “A” in Fig-
ure 60.
The network element NE1 is connected to the Grand Master Clock. By distributing the PTP
packets with a VPLS service the ring structure is modified to a logical tree structure where three
VPLS Pseudo Wires connect the NE2, NE3 and NE4 with the NE1, see “B” in Figure 60.
PTP packets inside the MPLS-TP network are encapsulated in Ethernet and MPLS.

NE1
A
NE2 NE4
NE3
B PRC
NE1
ordinary clock transparent clock
NE1
PTP in a VPLS PW
NE2 NE4
NE3
Figure 60: MPLS-TP network with a ring structure
The example network in Figure 61 has the following features:

− Each NE (NE1 to NE4) maintains a PTP stream with the Grand Master Clock. Inside the
MPLS-TP network the PTP streams are encapsulated in VLAN-100, carried by a VPLS
service. Outside the MPLS-TP network the PTP stream is untagged.
− The clock selection is priority based, selecting the timing from the Grand Master Clock or
the internal timing.
− With this setup the synchronization distribution is not protected: There are no redundant
Grand Master Clock and no redundant tunnels for the VPLS.
Please note:
The synchronization distribution in the MPLS network could easily be protected by
using protected tunnels for the VPLS Pseudo Wire transport.
As a prerequisite to the configuration of the synchronization network an MPLS network consist-
ing of the four network elements NE1, NE2, NE3 and NE4 has to be established:
• The port-1 and port-2 of NE1, NE2, NE3 and NE4 are all MPLS-TP ports that are configured
to:
− Port Type = MPLS-TP.
• Tunnels must be created
− from NE1 to NE2,
− from NE1 to NE3, passing via NE2, and
− from NE1 to NE4.

• Then create a PTP VPLS service with the SVI VLAN set to 100. Add three Pseudo Wires to
this service using the three tunnels created before. The Pseudo Wires for the PTP packets
are carried by unprotected MPLS tunnels.
• The VLAN ID 100 of the SVI VLAN must be added to the FOX61x VLAN.
With the above steps the MPLS network used for the PTP packet transport is ready.
For a detailed description of the MPLS setup in a FOX61x network element please refer to
[1KHW028618] User Manual “MPLS-TP Services”.
The NE1 is connected to the Grand Master Clock and represents the hub for the timing in Fig-
ure 61. The port-3 of NE1 has to be setup so that the untagged PTP stream to/from the Grand
Master Clock is VLAN tagged with the VLAN ID 100 inside the FOX61x Switch:
− Port Type = CVP.
− Port Mode = Access.
− Port VLAN ID = 100.
Regarding the PTP and PETS setup the NE1, NE2, NE3 and NE4 are all configured identically:
• PTP configuration
− PTP Transport = Ethernet (L2).
− PTP Mode = Frequency And Phase.
− Source for PTP-1 = VLAN-100.
• PTP Ports & Streams
− port-1 and port-2, PTP Mode = Ordinary/Boundary And Transparent Clock.
− add a PTP VLAN Interface with VLAN ID 100.
− add a stream to the VLAN interface.
− set the stream destination MAC address to AA:BB:CC:DD:EE:FF, corresponding to the
Grand Master Clock MAC address.
• PETS configuration
− Source PTP-1, Priority = 1.
− Source Internal, Priority = 7.
− Selection Algorithm = Priority.
The detailed PTP configuration of the FOX61x network element is described in section 6.3.5
PETS Synchronization via PTP, Ethernet VLAN Based (on page 94).

PTP Grand Master

PRC MAC address
AA:BB:CC:DD:EE:FF
untagged
Port-3 configuration
Port Type CVP
Port Mode Access
PVID 100
PTP port configuration
PTP Mode
Ordinary/Boundary and port-3
Transparent Clock
NE1
port-2 port-1
Selected Clock
Source: PTP-1
VPLS, PTP and PETS configuration for

NE1, NE2, NE3 and NE4
PTP configuration VPLS configuration
PTP Transport Ethernet (L2) SVI VLAN 100
PTP Mode Frequency And Phase Binding Mesh
port-1 Source PTP-1 VLAN-100/ stream-1
PETS Clock Select ion
port-1
PTP VLAN configuration (VLAN-100) Source Priority
VLAN ID 100 PTP-1 1
NE2 internal 7
NE4
PTP stream conf iguration (VLAN-100)
Selected Clock Unicast Dest. MAC AA:BB:CC: DD:EE:FF Selected Clock
Source: PTP-1 Source: PTP-1
Port and PTP port configuration for all

port-2 port-1 and port-2
Port configuration
Port Type MPLS-TP

PTP Mode Ordinary/Boundary and Transparent Clock
Encapsulat ion According Port Type
NE3
port-1
Selected Clock
Source: PTP-1
Figure 61: Synchronization in an MPLS-TP network with a ring structure
6.7.3 PTP IP VLAN Based

The synchronization using the PTP IP VLAN based approach can make use of an MPLS VPLS
service transporting the PTP packets from a network element connected to the PTP Grand Mas-
ter Clock to all other network elements.
The example network is a ring network with four network elements NE1 to NE4, see “A” in Fig-
ure 62.

The network element NE1 is connected to the Grand Master Clock. By distributing the PTP
packets with a VPLS service the ring structure is modified to a logical tree structure where three
VPLS Pseudo Wires connect the NE2, NE3 and NE4 with the NE1, see “B” in Figure 60.
PTP packets inside the MPLS-TP network are encapsulated in Ethernet, MPLS, IPv4 and UDP.
NE1
A
NE2 NE4
NE3
B PRC
NE1
ordinary clock transparent clock
NE1
PTP in a VPLS PW
NE2 NE4
NE3
Figure 62: MPLS-TP network with a ring structure
The example network in Figure 63 has the following features:

− Each NE (NE1 to NE4) maintains a PTP stream with the Grand Master Clock. Inside the
MPLS-TP network the PTP streams are encapsulated in VLAN-100, carried by a VPLS
service. Outside the MPLS-TP network the PTP stream is untagged.
− The clock selection is priority based, selecting the timing from the Grand Master Clock or
the internal timing.
− With this setup the synchronization distribution is not protected: There are no redundant
Grand Master Clock and no redundant tunnels for the VPLS.
Please note:
The synchronization distribution in the MPLS network could easily be protected by
using protected tunnels for the VPLS Pseudo Wire transport.
As a prerequisite to the configuration of the synchronization network an MPLS network consist-
ing of the four network elements NE1, NE2, NE3 and NE4 has to be established:
• The port-1 and port-2 of NE1, NE2, NE3 and NE4 are all MPLS-TP ports that are configured
to:
− Port Type = MPLS-TP.

• Tunnels must be created

− from NE1 to NE2,
− from NE1 to NE3, passing via NE2, and
− from NE1 to NE4.
• Then create a PTP VPLS service with the SVI VLAN set to 100. Add three Pseudo Wires to
this service using the three tunnels created before. The Pseudo Wires for the PTP packets
are carried by unprotected MPLS tunnels.
• The VLAN ID 100 of the SVI VLAN must be added to the FOX61x VLAN.
With the above steps the MPLS network used for the PTP packet transport is ready.
For a detailed description of the MPLS setup in a FOX61x network element please refer to
[1KHW028618] User Manual “MPLS-TP Services”.
The NE1 is connected to the Grand Master Clock and represents the hub for the timing in Fig-
ure 63. The port-3 of NE1 has to be setup so that the untagged PTP stream to/from the Grand
Master Clock is VLAN tagged with the VLAN ID 100 inside the FOX61x Switch:
Regarding the PTP and PETS setup the NE1, NE2, NE3 and NE4 are all configured identically:
• PTP configuration
− PTP Transport = UDP/IPv4 (L3).
− PTP Mode = Frequency And Phase.
− Source for PTP-1 = VLAN-100.
• PTP Ports & Streams
− port-1 and port-2, PTP Mode = Ordinary/Boundary And Transparent Clock.
− add a PTP VLAN Interface with VLAN ID 100, the source IP address and netmask.
− add a stream to the VLAN interface.
− set the stream destination IP address to aaa.bbb.ccc.ddd, corresponding to the Grand
Master Clock IP address.
• PETS configuration
− Source PTP-1, Priority = 1.
− Source Internal, Priority = 7.
− Selection Algorithm = Priority.
The detailed PTP configuration of the FOX61x network element is described in section 6.3.6
PETS Synchronization via PTP, IP VLAN Based (on page 98).

PTP Grand Master

PRC IPv4 address
<GM IP address>
untagged
Port-3 configuration
Port Type CVP
Port Mode Access
PVID 100
PTP Mode
Ordinary/Boundary and port-3
Transparent Clock
NE1
port-2 port-1
Selected Clock
Source: PTP-1
VPLS, PTP and PETS configuration for

NE1, NE2, NE3 and NE4
PTP configuration VPLS configuration
PTP Transport UDP/IPv4 (L3) SVI VLAN 100
PTP Mode Frequency And Phase Binding Mesh
Source PTP-1 VLAN-100/ stream-1
PETS Clock Select ion
port-1 PTP VLAN configuration (VLAN-100) Source Priority port-1
VLAN ID 100 PTP-1 1
Role Slave internal 7
NE2 Address <source IP address> NE4
Netmask <netmask>
Source: PTP-1 PTP stream configuration (VLAN-100) Source: PTP-1
Destination IP <GM IP address>
port-2 Port and PTP port configuration for all

port-1 and port-2
Port configuration
Port Type MPLS-TP

PTP Mode Ordinary/Boundary and Transparent Clock
Encapsulat ion According Port Type
NE3
port-1
Selected Clock
Source: PTP-1
Figure 63: Synchronization in an MPLS-TP network with a ring structure
6.7.4 PTP IP VLAN Based, two Rings, two External Timing Sources
The synchronization in the example MPLS-TP network in Figure 64 is distributed from two inde-
pendent PTP Grand Masters to all network elements using PTP packets. The example makes
use of the PTP application as shown in section 6.3.6 PETS Synchronization via PTP, IP VLAN
Based (on page 98), where the network elements connecting the access network operate as
Master Clocks for the access network:

• In the core network (NE1 to NE4) the PTP application is IP VLAN based. Two PTP VPLS are
created with a tree topology each carrying a PTP VLAN. PTP packets inside the MPLS-TP
network are encapsulated in Ethernet, MPLS, IPv4 and UDP.
− NE1 is connected to the Grand Master Clock 1 and represents the hub for the red timing
in Figure 64. The VPLS Pseudo Wires for the PTP packets are carried by protected
MPLS tunnels, connecting NE2 to NE4 to the NE1.
− Each NE (NE1 to NE4) maintains a PTP stream with the Grand Master Clock 1. Inside
the MPLS-TP network the PTP streams are encapsulated in VLAN-101, carried by VPLS
1. Outside the MPLS-TP network the PTP stream is untagged.
− NE4 is connected to the Grand Master Clock 2 and represents the hub for the green tim-
ing in Figure 64. The VPLS Pseudo Wires for the PTP packets are carried by protected
− NE2 acts as Master Clock for the access network (NE5 to NE8). It provides the IP VLAN-
103 with the “Master” role, carried by VPLS 3. VPLS 3 connects the NEs in the access
network to NE2.
− NE3 acts as Master Clock for the access network (NE5 to NE8). It provides the IP VLAN-
104 with the “Master” role, carried by VPLS 4. VPLS 4 connects the NEs in the access
network to NE3.
− The clock selection is priority based, selecting the red timing from the Grand Master
Clock 1 or the green timing from the Grand Master Clock 2.
− With this setup there is no single point of failure: Redundant Grand Master Clocks and
redundant tunnels for the VPLS 1 and VPLS 2.
• In the access network (NE5 to NE8) the PTP application is IP VLAN based. Two PTP VPLS
are created with a tree topology each carrying a PTP VLAN. PTP packets inside the MPLS-
TP network are encapsulated in Ethernet, MPLS, IPv4 and UDP.
− NE5 is connected to the Master Clock in NE2 and represents the hub for the blue timing
MPLS tunnels, connecting NE5 to NE8 to the Clock Master NE2.
− Each NE (NE5 to NE8) maintains a PTP stream with the Master Clock in NE2. Inside the
MPLS-TP network the PTP streams are encapsulated in VLAN-103, carried by VPLS 3.
− NE8 is connected to the Master Clock in NE3 and represents the hub for the brown timing
MPLS tunnels, connecting NE5 to NE8 to the Clock Master NE3.
− Each NE (NE5 to NE8) maintains a PTP stream with the Master Clock in NE3. Inside the
MPLS-TP network the PTP streams are encapsulated in VLAN-104, carried by VPLS 4.
− The clock selection is priority based, selecting the blue timing from the Master Clock in
NE2 or the brown timing from the Master Clock in NE3.
For the configuration of the network elements refer to Figure 64. Only the main parameters are
shown. All other parameters use the default values.
NE1 to NE4 are all configured identically with the following exceptions:
• NE1:
Port 13 has to be setup so that the PTP stream to/from the Grand Master Clock 1 is VLAN
tagged with VID 101 inside the FOX61x Switch.

• NE2:
In addition to VPLS 1 and VPLS 2 the NE2 provides the VPLS 3, transporting the Master
VLAN-103 to the access network (NE5 to NE8).
Port 23 is an MPLS-TP port.
• NE3:
In addition to VPLS 1 and VPLS 2 the NE3 provides the VPLS 4, transporting the Master
VLAN-104 to the access network (NE5 to NE8).
Port 33 is an MPLS-TP port.
• NE4:
• The NE5 to NE8 use different source IP addresses for the VLAN-103 and for the VLAN-104:
− NE5: 3.3.3.15 for VLAN-103 and 4.4.4.15 for VLAN-104.

Grand Master Clock 1 Grand Master Clock 2

UTC UTC
IP address IP address
1.1.1.10 2.2.2.10
Port 13 configuration
Port Type
Port Mode
CVP
Access
Port Type CVP PTP IP VLAN based
Port Mode Access
PVID 101 PT P configur ation
PVID 102
PT P Transport UDP/IPv4 (L3)
PT P Mode Frequency And Phase
Transparent Clock Transparent Clock Awareness Full Aware
Source PTP-1 VLAN-101/stream-1
PT P port configuration
Port 11 configuration Port 41 configuration PT P Mode Ordinary/Boundar y and Transparent Clock
Port Type MPLS-TP Port Type MPLS-TP Encapsulation According Port Type
NE1 PT P VLAN-101 configur ation

VLAN ID 101
VPLS 1 configuration NE4 Role Slave
SVI VLAN 101 Address 1.1.1.11 … 1.1.1.14 (NE1 … NE4)
Binding Mesh Netmask 255.255.255.0
Port 12 configuration VLAN Mode No Change Port 42 configuration
Port Type MPLS-TP Port Type MPLS-TP PT P stream configuration (VLAN-101)
VPLS 2 configuration Destination IP Address 1.1.1.10
SVI VLAN 102
Binding Mesh PT P VLAN-102 configur ation
VLAN Mode No Change VLAN ID 102
Role Slave
Port 21 configuration Port 31 configuration Address 2.2.2.11 … 2.2.2.14 (NE1 … NE4)
Port Type MPLS-TP Port Type MPLS-TP Netmask 255.255.255.0
PT P stream configuration (VLAN-102)

Destination IP Address 2.2.2.10
NE2 NE3 PETS configuration, Clock Selection
Source Priority
Port 22 configuration Port 32 configuration PT P-1 1
Port Type MPLS-TP Port Type MPLS-TP PT P-2 2
Selection Alogorithm Priority
VPLS 3 configuration VPLS 4 configuration

PT P VLAN-103/VLAN-104 configuration
SVI VLAN 103 SVI VLAN 104
VLAN ID 103 104
Binding Mesh Binding Mesh
Role Master Master
Port 23 configuration VLAN Mode No Change VLAN Mode No Change Port 33 configuration
Address 3.3.3.10 4.4.4.10
Port Type MPLS-TP Port Type MPLS-TP
Transparent Clock Transparent Clock Netmask 255.255.255.0 255.255.255.0
Port 53 configuration Port 83 configuration

PTP IP VLAN based
Transparent Clock Transparent Clock PT P configur ation
PT P Transport UDP/IPv4 (L3)
Awareness Full Aware
Port 51 configuration Port 81 configuration Source PTP-2 VLAN-104/stream-1
NE5 PT P Mode Ordinary/Boundar y and Transparent Clock
Encapsulation According Port Type
NE8
PT P VLAN-101 configur ation
VLAN ID 103
Port 52 configuration VPLS 3 configuration Port 82 configuration Role Slave
Port Type MPLS-TP SVI VLAN 103 Port Type MPLS-TP Address 3.3.3.15 … 3.3.3.18 (NE5 … NE8)
Binding Mesh Netmask 255.255.255.0
VLAN Mode No Change
VPLS 4 configuration Destination IP Address 3.3.3.10
SVI VLAN 104
Port 61 configuration Binding Mesh Port 71 configuration PT P VLAN-104 configur ation
Port Type MPLS-TP VLAN Mode No Change Port Type MPLS-TP VLAN ID 104
Role Slave
Address 4.4.4.15 … 4.4.4.18 (NE5 … NE8)
Netmask 255.255.255.0
NE6 NE7 PT P stream configuration (VLAN-104)
Destination IP Address 4.4.4.10
Port Type MPLS-TP Port Type MPLS-TP PETS configuration, Clock Selection
Source Priority
PT P-1 1
PT P-2 2
Transparent Clock Transparent Clock
Figure 64: MPLS-TP network with one main ring in the core network and one subring in the
access network

6.7.5 PTP Port and Ethernet VLAN Based, two Rings, two External Timing
Sources
The synchronization in the example MPLS-TP network in Figure 65 is distributed from two inde-
pendent PTP Grand Masters to all network elements using PTP packets. The example makes
use of the two PTP applications as shown in section 6.3.3 PETS Synchronization via PTP and
SyncE, Port Based (Pure Hybrid) (on page 87) and section 6.3.5 PETS Synchronization via
PTP, Ethernet VLAN Based (on page 94):
• In the core network (NE1 to NE4) the PTP application is Ethernet VLAN based. Two PTP
VPLS are created with a tree topology each carrying a PTP VLAN. PTP packets inside the
MPLS-TP network are encapsulated in Ethernet and MPLS.
− NE1 is connected to the Grand Master Clock 1 and represents the hub for the red timing
− NE4 is connected to the Grand Master Clock 2 and represents the hub for the green tim-
ing in Figure 65. The VPLS Pseudo Wires for the PTP packets are carried by protected
− The clock selection is priority based, selecting the red timing from the Grand Master
Clock 1 or the green timing from the Grand Master Clock 2.
• In the access network (NE5 to NE8) the PTP application is point-to-point based. The network
elements are connected in a chain. PTP packets inside the MPLS-TP network are encapsu-
lated in Ethernet.
− NE5 is synchronized to the NE timing of NE2 and forwards the blue timing to NE6. NE6
forwards the blue timing to NE7. NE7 forwards the blue timing to NE8.
− NE8 is synchronized to the NE timing of NE3 and forwards the brown timing to NE7. NE7
forwards the brown timing to NE6. NE6 forwards the brown timing to NE5.
− The clock selection is priority based, selecting the blue timing from NE2 or the brown tim-
ing from NE3.
− With this setup there is no single point of failure: Redundant master clocks (NE2 and
NE3) and each NE has access to the timing information from two neighbor NEs.
For the configuration of the network elements refer to Figure 65. Only the main parameters are
shown. All other parameters use the default values.
• NE1:
• NE2:
Port 23 has to be setup so that the PTP stream to/from NE5 is untagged.
− PTP Mode = Ordinary/Boundary Clock.
− Encapsulation = Ethernet.

• NE3:
Port 33 has to be setup so that the PTP stream to/from NE8 is untagged.
− PTP Mode = Ordinary/Boundary Clock.
− Encapsulation = Ethernet.
• NE4:
• Port 51 on NE5 and port 81 on NE8 have a stream with the Role = Slave.
• All other streams have the Role = Master Or Slave.

Grand Master Clock 1 Grand Master Clock 2

UTC UTC
MAC address MAC address

AA:BB:CC:DD:EE:01 AA:BB:CC:DD:EE:02
Port Type CVP
Port Type CVP
Port Mode Access
PVID 101
Port Mode
PVID
Access
102
PTP Ethernet VLAN based
PT P configur ation
Transparent Clock Transparent Clock PT P Transport Ethernet (L2)
PT P Mode Ordinary/Boundar y and Transparent Clock
Encapsulation According Port Type
NE1
NE4 VLAN ID 101

Port 12 configuration VPLS 1 configuration Port 42 configuration
Role Slave
Port Type MPLS-TP SVI VLAN 101 Port Type MPLS-TP
Addressing Unicast
Binding Mesh
Destination MAC Address AA:BB:CC:DD:EE:01
VLAN Mode No Change
VPLS 2 configuration
VLAN ID 102
SVI VLAN 102
Port 21 configuration Binding Mesh Port 31 configuration
Port Type MPLS-TP VLAN Mode No Change Port Type MPLS-TP
Role Slave
Addressing Unicast
Destination MAC Address AA:BB:CC:DD:EE:02
NE2 NE3 PETS configuration, Clock Selection

Source Priority
PT P-1 1
PT P-2 2
Transparent Clock Transparent Clock
PT P Mode Ordinary/Boundary Clock
Encapsulation Ethernet
PT P stream configuration (ports 23, 33)
Role Master
Addressing Unicast
Destination MAC Address 01:1B:19:00:00:00

PTP point-to-point based

PT P configur ation
PT P Transport Ethernet (L2)
NE5 NE8 PT P Mode Pure Hybrid
PT P Mode Ordinary/Boundary Clock
Encapsulation Ethernet
PT P stream configuration (ports 51, 81)

Role Slave
Addressing Unicast
PT P stream configuration (ports 52, 61, 62, 71, 72, 82)
Role Master Or Slave
Addressing Unicast
PETS configuration, PDH Clock Sour ces
PDH Clock Source 1 /unit-11/port-1
PDH Clock Source 2 /unit-11/port-2
PETS configuration, Clock Selection

Source Priority
PDH Clock Source 1 1
PDH Clock Source 2 2
NE6 NE7
Figure 65: MPLS-TP network with one main ring in the core network and one subring in the
access network

FOX61x | SYNCHRONIZATION OPERATION
7 Operation
This section describes the operation functions of the synchronization applications with the FOX-
61x.
The main purpose of these operation functions is to dynamically test or debug the NE synchro-
nization system and if applicable to monitor the influence on the network synchronization.
Please note:
The operation functions described in this section assume a correctly configured
and operational synchronization application in the FOX61x.
7.1 Status
7.1.1 SETS Status

The availability and selection of the SETS clock sources can be checked with the SETS status
function on the SAMO1 or SAMOx unit: AP: /unit-x, Status - SETS.
The same dialog provides the SETS clock operating status. Refer to section 5.2.2.3 SETS Clock
Operation Modes (on page 37).
With the SETS clock operation type selection the SETS clock operation status can be forced to
any of the available states for testing purposes:
• Auto Selection:
The SETS autonomously selects the highest priority or highest quality clock source.
• Forced Holdover: The SETS is running with the previously acquired clock frequency. “Inter-
nal” is the selected SETS clock source.
• Forced Free Run: The SETS is synchronized to the internal clock oscillator. “Internal” is the
selected SETS clock source.
Please note:
An alarm MFA (Maintenance Function Active) is set on the SAMO1 or SAMOx unit
level if one of the forced SETS clock operation modes is active.
To return to the normal operating condition set the SETS clock operating mode to “Auto Selec-
tion”.
The SETS clock source selection can be controlled for maintenance purposes. The manual
switch and lockout commands override the automatic clock source selection.
• Lockout:
forced or manual switch request.
• Forced switch:
Perform a forced switch to a specific timing source for the SETS.
If the source is not available, i.e. failed or in WTR state, the clock operation mode “Holdover”
is selected.
• Manual switch:
Perform a manual switch to a specific timing source for the SETS.

7.1.2 PETS Status

The availability and selection of the PETS clock sources can be checked with the PETS status
function in the FOXCST “Synchronization” view at the AP: /Synchronization/PETS, Status.
The same dialog provides the PETS clock operating status. Refer to section 5.3.2.3 PETS Clock
Operation Modes (on page 48).
With the PETS clock operation type selection the PETS clock operation status can be forced to
any of the available states for testing purposes:
• Auto Selection:
The PETS autonomously selects the highest priority or highest quality clock source.
• Forced Holdover:
The PETS is running with the previously acquired clock frequency. “Internal” is the selected
PETS clock source.
Please note:
The alarm PHO (PETS Holdover) is not activated during a forced holdover.
• Forced Free Running:
The PETS is synchronized to the internal clock oscillator. “Internal” is the selected PETS
clock source.
Please note:
An alarm MFA (Maintenance Function Active) is set on the NE level if one of the
forced PETS clock operation modes is active.
To return to the normal operating condition set the PETS clock operating mode to “Auto Selec-
tion”.
7.1.3 Ethernet Port Status

The usage of the core unit Ethernet port-1 to port-5 and the WAN port extension unit port-1 to
port-5 as PDH clock sources can be checked with the status dialog in the FOXCST “Synchro-
nization” view at the AP: /Synchronization/PETS, Status.
The dialog displays if the port is available as a PDH clock source, i.e. if the port is in the opera-
tional state “up” and if it is used as a PDH clock source.
The core unit ports status which are used as SyncE ports can be checked in the FOXCST
“Synchronization” view at the AP: /Synchronization/SyncE, Port Status.
The dialog displays if the port has the Master and/or Slave Role active.
For the Ethernet port status functions used as PTP sources see section 7.1.5 PTP Port Status
(on page 144).
7.1.4 PTP Status

The availability and selection of the PTP sources can be checked with the PTP status function
in the FOXCST “Synchronization” view at the AP: /Synchronization/PTP, Status.
The same dialog provides the PTP parents status and the PTP time properties status.
7.1.5 PTP Port Status

The core unit ports status which are used as PTP sources can be checked in the FOXCST
“Synchronization” view at the AP: /Synchronization/PTP, Ports & Streams - Port Status.
The dialog displays the PTP parent data set and the PTP time properties.

7.1.6 PTP Stream Status

The usage of the PTP VLANs as PTP sources can be checked in the FOXCST “Synchroniza-
tion” view at the AP: /Synchronization/PTP, Ports & Streams - Stream Status.
The dialog displays the PTP parent data set and the PTP time properties.
7.1.7 ESO Status

The status of the ESO-1 and ESO-2 synchronization output signals can be checked with the
ESO status function in the FOXCST “Synchronization” view at the AP: /Synchronization/ESO,
Status.
Please refer to section 8.6.2 AP: / Synchronization / ESO, Status (on page 210) for a description
of the available status parameters.
The availability and selection of the ESO-2 clock sources can be checked with the ESO-2 status
function on the SAMO1 or SAMOx unit at the AP: /unit-x, Status - ESO-2.
In the same dialog the ESO-2 clock source selection can be controlled for maintenance pur-
poses. The manual switch and lockout commands override the automatic clock source selec-
tion. These management functions are only usable if the ESO-2 operates in “non SETS Locked”
mode:
• Lockout:
forced or manual switch request.
• Forced switch:
Perform a forced switch to a specific timing source for the ESO-2.
If the source is not available, i.e. failed or in WTR state, the source remains selected and the
signal status remains active.
• Manual switch:
Perform a manual switch to a specific timing source for the ESO-2.
7.1.8 QL Status
The status of the transmitted and received quality level (QL) is available at the following access
points:
• SAMOx:
AP: /unit-x/sdh/sdh-y, Status - MS
• SAMO1:
AP: /unit-x/port-y, Status - MS
• LEDE1:
AP: /unit-x/port-y, Status - QL
• CEPI1:
AP: /unit-x/port-y, Status - QL
AP: /unit-x/pw/pw-y, Status - QL
AP: /unit-x/pw/p12-c/pw-y, Status - QL (not available for the PCMnn and PCMnn_CAS termi-
nation modes)
• DATI1:
AP: /unit-x/logports/logport-z/trunk, Status - QL

• Core unit:
AP: /Synchronization/SyncE, Ports - Port Status
AP: /Synchronization/PTP, Ports & Streams - Port Status
AP: /Synchronization/PTP, Ports & Streams - PTP Status (Master VLAN)
AP: /Synchronization/PTP, Ports & Streams - Stream Status (Slave VLAN)
7.2 Fault Management

For the PDH and PTP synchronization fault management please refer to [1KHW002464] User
Manual “FOX615 R2/FOX615/FOX612/FOX611”.
For the SDH synchronization fault management please refer to [1KHW002476] User Manual
“SAMO1” and refer to [1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5,
SAMO5-F”.
7.3 Performance Management
7.3.1 SETS Performance Management

See section 5.2.5 SETS Performance Management (on page 39).
7.3.2 ESO-2 Performance Management

See section 5.7.8 ESO-2 Performance Management (on page 60).
7.3.3 PTP Stream Performance Management

See section 5.3.5 PETS Performance Management (on page 50).

FOX61x | SYNCHRONIZATION USER INTERFACE REFERENCE
8 User Interface Reference

The following sections give a complete user interface reference of the FOX61x synchronization
applications related management functions, as far as these are not yet covered in the generic
description in the document [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/
FOX611”.
The chapter starts with an overview of the managed object models (MOM) of the synchroniza-
tion related functions in section 8.1 MOM for the Synchronization (on page 147).
FOX61x synchronization related management functions are handled at different places in the
FOXCST:
• FOXCST “Synchronization” view:
The FOXCST “Synchronization” view provides the TDM (PDH) and packet based synchroni-
zation management functions for the whole FOX61x network element. See section 8.2 AP: /
Synchronization (on page 153) and subsequent sections.
Please note:
SDH related synchronization functions are described in the SDH service unit User
Manuals.
→ Please refer to [1KHW002476] User Manual “SAMO1” and refer to
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-
F”.
• FOXCST “Shelf View” and “Tree View”:
The FOXCST “Shelf View” and “Tree View” provide management functions as follows:
− Fault management for the PDH synchronization and packet based synchronization. See
section 8.7 AP: / ne (on page 212)
− Management functions for the external synchronization inputs (esi). See section 8.8 AP: /
unit-11 (on page 213).
− Management functions for the SDH synchronization. See section 8.9 AP: / unit-x (SDH
Service Unit) (on page 213).
For a description about how to configure and bring into operation the FOX61x synchronization
applications please refer to section 6 Commissioning (on page 75) and section 7 Operation (on
page 143).
In the tables of the sections below, the parameter default values for properties are underlined.
Please note:
For better legibility of numbers in this User Manual, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter entry
fields of the FOXCST, these inverted commas must not be entered. Instead, the
numbers are entered without these inverted commas (e.g. 40000).
Please note:
Screenshots presented in this reference are examples and show configurations or
data that may not correspond to the view you see when managing your FOX61x
equipment.
8.1 MOM for the Synchronization
8.1.1 MOM for the FOXCST Synchronization View

Figure 66 shows the AP tree and the management functions for the management of the syn-
chronization functions available in the FOXCST “Synchronization” view. This MOM allows the
management of the NE timing source (PETS, PTP and SyncE) and of the synchronization input
ports and output ports used for PTP and/or SyncE.

With these MOs, the following functions are managed:

• SyncE:
Configuration of the synchronization method and the quality level for synchronous Ethernet
signals.
• PTP:
Configuration of the PTP clock configuration, PTP mode and the PTP timing sources on net-
work element, port and VLAN level.
• PETS:
Selection of the clock sources for the PETS (plesiochronous equipment timing source) and
configuration of the clock source priorities and quality levels.
• ESO:
Selection of the clock sources for the external synchronization output ESO-1 and configura-
tion of the clock source priorities and quality levels. Configuration of the squelch parameters
“Squelched By Source” and “Squelched By QL”.
Selection of the SDH unit for the external synchronization output ESO-2.

Synchronization
<a p>
Synchroni zation
<a p>
SyncE
<a p>
Por ts
<mf> <mf>
Configuration Status
<a ttribute> <a ttribute>

SyncE SyncE
<a p>
PTP
<mf>
<mf> <mf> <mf>
Fault
Configuration LSP Configur atio n Status
Manag ement
<a ttribute> <a ttribute> <a ttribute> <a ttribute>

PTP PTP PTP PTP
<a p> <a p>

Por ts VLA Ns
<mf> <mf> <mf> <mf>
Configuration Status Configuration Status

PTP PTP PTP PTP
<a p> <a p>

Streams Streams
<mf> <mf> <mf> <mf>

Configuration Counters Configuration Counters

PTP PTP PTP PTP
<a p>
PETS
<mf>
<mf> <mf>
Fault
Manag ement
<a ttribute> <a ttribute> <a ttribute>

PETS PETS PETS
<a p>
ESO
<mf>
<mf> <mf>
Fault
Manag ement
<a ttribute> <a ttribute> <a ttribute>

ESO ESO ESO
Figure 66: Synchronization access point tree

Please note:
The synchronization related management functions of TDM based ports
• port-y, Configuration - Synchronization, and
• port-y, Status - QL
are located at the corresponding access points of the TDM service unit.
→ For a description of these management functions please refer to the User Man-
ual of the TDM service unit.
8.1.2 MOM for the PDH Synchronization

Figure 67 shows the AP tree and the NE management functions for the management of the
PDH synchronization which are not available in the FOXCST “Synchronization” view. This MOM
allows the management of the TDM based synchronization input ports and output ports.
• esi-z:
Fault management of the external synchronization inputs ESI-1 and ESI-2.
• General, Synchronization, QL:
Configuration of the synchronization method and the quality level for PDH signals.
• P12 (the P12 layer can be an E1 port, a Pseudo Wire, an SHDSL trunk or a P12 signal
transported over SDH):
Configuration of the synchronization status message (SSM) or synchronization status indica-
tion (SSI) (not for DATI1). Fixed routing table.
Please note:
The DATI1 unit supports the SSM for the “clock over payload” modes in the “Trunk
to NT” and “Trunk to LT” applications. The SSM is transported in the Sa4 bit of the
timeslot 0.
→ This provides compatibility with the STIC1 implementation in FOX51x.
For a description of the PDH synchronization managed objects, properties, and commands that
are related to a FOX61x service unit please refer to the corresponding units User Manual,
where the access points and connection termination points are located.

<a p>
FOX61x
<a p>
unit-11: Core Unit
<a p>
1 sync (CESM3)
neController (CESM1)
neController (CESM2)
<a p>
<a p> 2
esi-z
unit-x: LEDE1 etr (CESM3)
<a p>
port-y
<mf> <mf>
<a ttribute>
<a p> <a ttribute>
Gen eral
unit-x: CEPI1 QL
Synchroni zation
<a p>
port-y
<mf> <mf>
<a p> <a ttribute> <a ttribute>

unit-x: DEFM1 Synchroni zation QL
<a p>
port-y
<a p> <mf> <mf>

unit-x: CEPI1
<a p>
pw [ / p12-c ]
<a p> Synchroni zation QL
unit-x: DATI1
<a p>
pw-y
<a p> <mf> <mf>

logp orts Configuration Status

logp ort-y Synchroni zation QL
<a p>
unit-x: SAMO1
unit-x: SAMOx <a p>
trunk
<a p> <mf> <mf>

pdh Configuration Status

vc1 2-y Synchroni zation QL
<a p>
p12
<mf> <mf>

Synchroni zation QL
Figure 67: PDH synchronization access point tree

8.1.3 MOM for the SDH Synchronization
Please note:
SDH related synchronization functions are described in the SDH service unit User
Manuals.
→ Please refer to [1KHW002476] User Manual “SAMO1” and refer to
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-
F”.
Figure 68 shows the AP tree and the NE management functions for the management of the
SDH synchronization. This MOM allows the management of the SETS and of the synchroniza-
tion input ports and output ports.
• SETS:
Selection of the clock sources for the SETS (Synchronous Equipment Timing Source) and
configuration of the clock source priorities and quality levels.
• ESO:
Selection of the clock sources for the ESO-2 and configuration of the clock source priorities
and quality levels. Configuration of the squelch parameters “Squelched By Source” and
“Squelched By QL”.
• MS (multiplex section):
Configuration of the synchronization status message (SSM) with the input mapping table,
output mapping table and routing table for the SDH ports of the SDH unit.
For a description of the SDH synchronization managed objects, properties, and commands
please refer to [1KHW002476] User Manual “SAMO1” and refer to [1KHW028668] User Manual
“SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”.

<a p>
FOX61x
<a p>
unit-x: SAMO1, or
unit-x: SAMOx
<mf> <mf>
<mf> <mf>
Fault Per forman ce
Manag ement Manag ement

SETS, ESO SETS, ESO SETS, ESO SETS, ESO
4 <a p>
SAMO1: port-y
<mf>
Configuration
<a ttribute>
MS
1 <a p>
SAMOx: sdh
4 or 8 <a p>
sdh-y
<mf>
Configuration
<a ttribute>
MS
Figure 68: SDH synchronization access point tree
8.2 AP: / Synchronization

This AP provides no management function.
8.3 AP: / Synchronization / SyncE
8.3.1 AP: / Synchronization / SyncE, Ports

The Ports table gives an overview of all ports that are available for the SyncE application. To
have access to the detail configuration and status parameters of a port click the port row in the
table, which makes the management functions of this port visible below the overview table. See
section 8.3.1.1 AP: / Synchronization / SyncE, Ports - Port Configuration (on page 154) and sec-
tion 8.3.1.2 AP: / Synchronization / SyncE, Ports - Port Status (on page 156).

Table 4: AP: / Synchronization / SyncE, Ports

Operation Name Parameter Name Range Descriptions / Details
Ports Physical <MO address> Managed object address of the physical port
that can be used for the SyncE application.
Source PDH Clock Source 1 … Shows if the physical port is used as a PDH
PDH Clock Source 4 clock source.
<empty> The physical port is not used as a PDH clock
source.
Method None Do not use a synchronization method
ESMC Use the Ethernet Synchronization Message
Channel (ESMC) for the transport of the syn-
chronization status message (SSM).
CoS CoS 0 … CoS 7 Select the VLAN priority for the ESMC frames.
Received QL Unknown The synchronization method “None” has been
configured, or no ESMC messages are
received.
Do Not Use The received SSM value is = 15, or the port
operational state is down.
1 … 14 The received SSM value is < 15.
Transmitted QL Unknown The synchronization method “None” has been
configured.
The port transmits no ESMC messages.
Do Not Use The “Do Not Use” quality level is transmitted
as SSM value = 15 in the following cases:
- The ports “QL Transmission Usage” param-
eter is “DoNotUse.
- The port is operating in 1000BASE-T mode
as clock slave.
1 … 14 Display of the transmitted SSM value < 15.
8.3.1.1 AP: / Synchronization / SyncE, Ports - Port Configuration
Please note:
In the “Port Configuration” tab the “QL Transmission”, “Input Mapping Table” and
“Output Mapping Table” management functions are only available for ports config-
ured to the Synchronization Method = ESMC.

Table 5: AP: / Synchronization / SyncE, Ports - Port Configuration

Port Configuration Method None Do not use a synchronization method
ESMC Use the Ethernet Synchronization Message
Channel (ESMC) for the transport of the syn-
chronization status message (SSM).
Priority CoS 0 … CoS 7 Select the VLAN priority for the ESMC frames.
QL Transmission Source ESI-1 Synchronization sources are all the PDH clock
ESI-2 sources as they are configured at the AP: /
Synchronization/PETS, Configuration.
<PDH Clock Source 1> The PTP-x sources are only available if the PTP
<PDH Clock Source 2> mode is not disabled at the AP: /Synchroniza-
tion/PTP, Configuration.
<PDH Clock Source 3>
The ESI-2 PDH clock source is only available
<PDH Clock Source 4> with the CESM1 and CESM2 core units.
PTP-1 These values are read-only.
PTP-2
PTP-3
PTP-4
Internal
Usage NA No synchronization method has been
selected.
CanBeUsed Transmit the QL value of the selected syn-
chronization source
DoNotUse Transmit the QL value 15, i.e. indicating that
the traffic signal cannot be used as a synchro-
nization source.

Table 5: AP: / Synchronization / SyncE, Ports - Port Configuration (continued)

Input Mapping Received QL 1 … 14 A received quality level in the range 1 to 14 can
Table Adapted QL Unknown be adapted to any other QL which will then be
used in the PETS and ESO selection process.
1 … 14 The default is a 1:1 mapping.
Do Not Use Note that a lower QL means a higher clock
quality.
Output Mapping Transmitted QL 1 … 14 A PETS internally used quality level in the
Table Adapted QL Unknown range 1 to 14 can be adapted to any other QL
which will then be used in the SSM of the cor-
1 … 14 responding transmit signal.
Do Not Use The default is a 1:1 mapping.
Note that a lower QL means a higher clock
quality.
See section 5.8 Quality Level Handling (on
page 60) for a description of the quality level
handling.

An electrical SFP based Ethernet port does not support synchronous Ethernet.

An Ethernet port operating in 1000BASE-T mode supports only unidirectional syn-
chronous Ethernet.
→ A 1000BASE-T Ethernet port transports timing information only from the clock
master to the clock slave. See section 8.3.1.2 AP: / Synchronization / SyncE,
Ports - Port Status (on page 156).

An Ethernet port operating in 10BASE-T mode cannot be used for the synchronous
Ethernet.
Please note:
An Ethernet port operating in 100BASE-TX half duplex mode can be used for syn-
chronous Ethernet.
→ The half duplex mode applies only for the layer 2 and above, the physical layer
operates in full duplex mode.
Please note:
For more information regarding quality level handling see section 5.8 Quality Level
Handling (on page 60).
8.3.1.2 AP: / Synchronization / SyncE, Ports - Port Status
Please note:
In the “Port Status” tab the “Clock Quality” management functions are only avail-
able for ports configured to the Synchronization Method = ESMC.

Table 6: AP: / unit-x / port-a, Status – SyncE

Clock Quality Received QL Unknown The synchronization method “None” has been
configured, or no ESMC messages are
received.
Do Not Use The received SSM value is = 15, or the port
operational state is down.
1 … 14 The received SSM value is < 15.
Transmitted QL Unknown The synchronization method “None” has been
configured.
The port transmits no ESMC messages.
Do Not Use The “Do Not Use” quality level is transmitted
as SSM value = 15 in the following cases:
- The ports “QL Transmission Usage” param-
eter is “DoNotUse.
- The port is operating in 1000BASE-T mode
as clock slave.
1 … 14 Display of the transmitted SSM value < 15.
Master Role Master role of a 1000BASE-T Ethernet port. If
enabled the port can be used as timing
source for SyncE.
100BASE-TX and optical port types have the
Master Role always enabled.
Slave Role Slave role of a 1000BASE-T Ethernet port. If
enabled the port can be used as timing sink.
100BASE-TX and optical port types have the
Slave Role always enabled.
Please note:
For more information regarding quality level handling see section 5.8 Quality Level
Handling (on page 60).
Please note:
For more information regarding the selection of Master Role and Slave Role please
refer to the core unit User Manuals:
→ [1KHW002469] User Manual “CESM1, CESM1-F”,
→ [1KHW028642] User Manual “CESM2, CESM2-F”,
→ [1KHW028774] User Manual “CESM3”.
8.4 AP: / Synchronization / PTP

The FOX61x supports two main applications with PTP:
• Point-to-point application, port based with ordinary/boundary clock.
• VLAN based application, with ordinary/boundary and transparent clock.

Both applications support a range of port and PTP parameters which must match the applica-
tion. The sections below show the valid parameter ranges.
PTP Point-to-Point Application:
Message Interval
- Sync
- Delay
PTP Sources
Clock Mode - PTP-1
Clock Domain - PTP-2
PTP Mode - PTP-3
Message Intervals - PTP-4
- Announce PTP Awareness
- Sync Message Intervals
- Delay - Announce
- Sync
- Delay
Role
Addressing Mode
Role
Destination MAC Address
Addressing Mode
Grand Stream Stream
PTP Mode Destination MAC Address
Master
Encapsulation
Clock Forward Multicast PTP Mode
PTP PTP
VLAN ID Encapsulation
UTC Forward Multicast
CoS
QL Transmission port-y port-z VLAN ID
CoS
Port Type Usage QL Transmission
Port Type Usage
Figure 69: PTP point-to-point application parameters
Please note:
In the point-to-point application a PTP stream is forwarded via physical Ethernet
ports of the core unit. This mode is not supported by the WAN port extension unit
EPEX1.
Table 7: Point-to-point application parameters

AP Parameter Valid values Comment
/unit-x/port-y, Main - Port Type Port Type Usage CVP The Ethernet port stacks
PWAC used are independent of
the Port Type Usage.
MPLS-TP See Figure 70.
VLAN Subinterfaces /
MPLS-TP

Table 7: Point-to-point application parameters (continued)

/Synchronization/PTP, Configuration PTP Transport Ethernet (L2) Must match with the net-
UDP/IPv4 (L3) work elements where the
PTP VLAN streams are
connected to.
Clock Mode One Step Must match with all other
network elements.
Clock Domain <any> Must match with all other
network elements.
PTP Mode Frequency And Phase
Pure Hybrid
Awareness <any> Must match with all other
network elements.
PTP Sources PTP-1 … PTP-4 Select a PTP port with a
configured stream.
Message Interval <any> Must match with all ports
and all other network ele-
ments.
It is recommended to use
the default values.
/Synchronization/PTP, Ports & PTP Mode Ordinary/Boundary Add a stream for a PTP
Streams - Port Configuration Clock port that is used as a PTP
source.
Encapsulation Ethernet See Figure 70.
Ethernet + VLAN
Forward Multicast <any> Must match with the
Grand Master configura-
tion.
VLAN ID <any> Configure according to
the application.
CoS <any>
QL Transmission <any> Configure according to
the application.
/Synchronization/PTP, Ports & Role Slave Configure according to
Streams - Stream Configuration Master the application.
Master Or Slave
Addressing Mode Unicast Configure according to
Multicast the application.
Destination MAC 01:1B:19:00:00:00 This is a forward-able

Address multicast MAC address.
Message Intervals <any> Should match with all
ports and all other net-
work elements.

Ethernet Ethernet +
VLAN
FCS FCS
PTP PTP
Type Type
0x88F7 0x88F7
Et hernet VLAN
DA SA <VID ETH>
Type
0x8100
Et hernet
DA SA
Figure 70: PTP point-to-point application encapsulation stacks
PTP Ethernet VLAN Based Application:
Message Interval
- Sync
Network Protocol - Delay
- PTP Transport
PTP Sources
Clock Mode - PTP-1
Clock Domain - PTP-2
Message Intervals PTP Mode - PTP-3
- Announce PTP Awareness - PTP-4
- Sync
- Delay
Addressing Mode
Destination MAC Address
Stream
VLAN ID
PTP Transport
Grand Role VLAN
Master CoS Residence time
Clock correction PTP Mode
PTP Mode PTP PTP Encapsulation
Encapsulation Forward Multicast
UTC Forward Multicast QL Transmission
QL Transmission port-y port-z
Port Type Usage
Port Type Usage
Figure 71: PTP Ethernet VLAN based application parameters
Please note:
In the Ethernet VLAN based application a PTP stream is forwarded via physical
Ethernet ports of the core unit or the WAN port extension unit EPEX1 or via the
logical SVI port of a MPLS-TP VPLS.

Table 8: Ethernet VLAN based application parameters

/unit-x/port-y, Main - Port Type Port Type Usage The Ethernet port stacks
used are dependent of
See Figure 72.
CVP PTP stream via physical
Ethernet port.
MPLS-TP PTP stream via logical SVI
VLAN Subinterfaces / port of a VPLS.
MPLS-TP
/Synchronization/PTP, Configuration PTP Transport Ethernet (L2) Must match with the net-
work elements where the
connected to.
network elements.
network elements.
network elements.
configured stream.
ments.
the default values.
/Synchronization/PTP, Ports & PTP Mode Ordinary/Boundary No stream allowed.
Streams - Port Configuration and Transparent
Clock
Encapsulation According Port Type See Figure 72.
Forward Multicast <any> Must match with the
Grand Master configura-
tion.
the application.
/Synchronization/PTP, Ports & VLAN ID <VLAN ID> VLAN ID used inside the
Streams - VLAN Configuration FOX61x Switch 1.
PTP Transport Ethernet (L2)
Role Slave
Priority <any>
/Synchronization/PTP, Ports & Addressing Mode Unicast
Streams - Stream Configuration Destination MAC <MAC address> MAC address of the PTP
Address Grand Master.
work elements.
1. The PTP VLAN must be configured to be a member of the FOX61x Switch.

Port type usage:

Port type usage: Port type usage:
CVP MPLS-TP
MPLS-TP
Ethernet Ethernet + According According

encapsulation
VLAN Port Type Port Type
FCS FCS FCS FCS
PTP PTP PTP PTP
Type Type Type Type

0x88F7 0x88F7 0x88F7 0x88F7
Et hernet VLAN VLAN VLAN
DA SA <VID ETH> <VID ETH> <VID ETH>
stream stream stream
Type Type Type
0x8100 0x8100 0x8100
Ethernet Et hernet Et hernet
DA SA DA SA DA SA
MPLS PW MPLS PW
<Label PW> <Label PW>
MPLS LSP MPLS LSP
<Label LSP> <Label LSP>
Type Type
0x8847 0x8847
Et hernet VLAN
DA SA <VID EVPL>
Type
0x8100
Et hernet
DA SA
Figure 72: PTP VLAN based application encapsulation stacks

A MPLS-TP Pseudo Wire must have the optional Control Word enabled from sys-
tem release R15B onwards to transport PTP.

PTP IP VLAN Based Application:
Message Interval
- Sync
Network Protocol - Delay
- PTP Transport
PTP Sources
Clock Mode - PTP-1
Message Intervals Clock Domain - PTP-2
- Announce PTP Mode - PTP-3
- Sync PTP Awareness - PTP-4
- Delay
Addressing Mode
Destination IP Address
VLAN ID
PTP Transport Stream
Role
Local IP Address
Grand Netmask VLAN
Master CoS Residence time
Clock correction PTP Mode
PTP Mode PTP PTP Encapsulation
UTC Encapsulation Forward Multicast
Forward Multicast QL Transmission
QL Transmission port-y port-z
Port Type Usage

Port Type Usage
Figure 73: PTP IP VLAN based application parameters
Please note:
In the IP VLAN based application a PTP stream is forwarded via physical Ethernet
ports of the core unit or via the logical SVI port of a MPLS-TP VPLS.
Table 9: IP VLAN based application parameters

See Figure 74.
Ethernet port.
MPLS-TP

Table 9: IP VLAN based application parameters (continued)

/Synchronization/PTP, Configuration PTP Transport UDP/IPv4 (L3) Must match with the net-
connected to.
network elements.
network elements.
“44” to be compatible
with the default value
according to ITU-T
G.8275.2.
network elements.
configured stream.
ments.
the default values.
Clock
Forward Multicast false According to ITU-T
G.8275.2.
the application.
PTP Transport UDP/IPv4 (L3)
Role Slave
Local IP Address <IPv4 address> Source IPv4 address.
Netmask <IPv4 address>
CoS <any>
/Synchronization/PTP, Ports & Addressing Mode Unicast
Streams - Stream Configuration Destination IP <IPv4 address> Destination IPv4 address.
Address
work elements.

Port type usage:

Port type usage: Port type usage:
CVP MPLS-TP
MPLS-TP
Ethernet Ethernet + According According

encapsulation
VLAN Port Type Port Type
FCS FCS FCS FCS
PTP PTP PTP PTP
UDP UDP UDP UDP
IPv4 IPv4 IPv4 IPv4
Type Type Type Type

0x0800 0x0800 0x0800 0x0800
Et hernet VLAN VLAN VLAN
DA SA <VID ETH> <VID ETH> <VID ETH>
stream stream stream
Type Type Type
0x8100 0x8100 0x8100
Ethernet Et hernet Et hernet
DA SA DA SA DA SA
MPLS PW MPLS PW
<Label PW> <Label PW>
MPLS LSP MPLS LSP
<Label LSP> <Label LSP>
Type Type
0x8847 0x8847
Et hernet VLAN
DA SA <VID EVPL>
Type
0x8100
Et hernet
DA SA
Figure 74: PTP IP VLAN based application encapsulation stacks

A MPLS-TP Pseudo Wire must have the optional Control Word enabled from sys-
tem release R15B onwards to transport PTP.
PTP IP VLAN Based Master Application:
Please note:
The IP VLAN based PTP Master application is not available on the CESM1 and
CESM2 core units.

Message Interval
Network Protocol - Sync
- PTP Transport - Delay
Clock Mode
Clock Domain
PTP Mode
PTP Awareness
VLAN ID
PTP Transport
Role
Local IP Address
VLAN Netmask
CoS
PTP PTP Mode

Encapsulation
Forward Multicast
port-z QL Transmission
Port Type Usage
Figure 75: IP VLAN based PTP Master application parameters
Please note:
In the IP VLAN based PTP Master application a PTP stream is forwarded via physi-
cal Ethernet ports of the core unit or the WAN port extension unit EPEX1 or via the
logical SVI port of a MPLS-TP VPLS.
Table 10: IP VLAN based application parameters

See Figure 72.
Ethernet port.
MPLS-TP

Table 10: IP VLAN based application parameters (continued)

/Synchronization/PTP, Configuration PTP Transport UDP/IPv4 (L3) Must match with the net-
connected to.
network elements.
network elements.
“44” to be compatible
with the default value
according to ITU-T
G.8275.2.
network elements.
ments.
the default values.
Clock
Forward Multicast false According to ITU-T
G.8275.2.
the application.
PTP Transport UDP/IPv4 (L3)
Role Master
Local IP Address <IPv4 address> Source IPv4 address.
Netmask <IPv4 address>
CoS <any>
8.4.1 AP: / Synchronization / PTP, Ports & Streams

The Ports & Streams table gives an overview of all ports and VLANs that are available for the
PTP application. To have access to the detail configuration and status parameters of a port or
VLAN click the port or VLAN row in the table, which makes the management functions of this
port or VLAN visible below the overview table.
See section 8.4.1.1 AP: / Synchronization / PTP, Ports & Streams - Port Configuration (on
page 175) and section 8.4.1.2 AP: / Synchronization / PTP, Ports & Streams - Port Status (on
page 177).
The stream information of a port or VLAN is only available if the stream rows are visible:
1 Click on the expansion icon of the corresponding port or VLAN, left most in the
Ports & Streams table:
− This opens the stream rows of the ports or VLANs table entry.

2 Alternatively click on the expansion icon for all rows in the table header:
− This opens the stream rows of all ports and VLANs table entries.
See section 8.4.1.4 AP: / Synchronization / PTP, Ports & Streams - Stream Configuration (Port)
(on page 180).
Table 11: AP: / Synchronization / PTP, Ports & Streams

Ports & Streams Interface <MO address> Managed object address of the physical port,
the VLAN or the logical stream that can be
used for the PTP application.
Source PTP-1 … PTP-4 Shows if the physical port or the VLAN is used
as a PTP source.
<empty> The physical port or VLAN is not used as a
PTP source.

Table 11: AP: / Synchronization / PTP, Ports & Streams (continued)

PTP Mode Disabled The port is not used as a PTP port.
The PTP port cannot be used as PETS syn-
chronization source.
In the Disabled PTP Mode no stream must be
present.
Ordinary/Boundary Clock Use the port or VLAN as PTP port of an ordi-
nary or boundary clock.
Up to 10 PTP ports can be configured to
“Ordinary/Boundary Clock”. The number of
these PTP ports must be shared with the number
of created PTP VLANs. This mode is not sup-
ported on a WAN port extension unit EPEX1.
PTP VLANs are not supported on ports con-
figured as “Ordinary/Boundary Clock”.
Ordinary/Boundary and The port is simultaneously used as “Ordinary
Transparent Clock Clock” or “Boundary Clock”, and “Transparent
Clock”.
PTP VLANs must be used on ports configured
as “Ordinary/Boundary and Transparent Clock”.
EPEX1 units just support Ordinary/Boundary and
Transparent clock mode.
Encapsulation 1 Ethernet PTP packets are encapsulated in Ethernet
MAC frames.
Ethernet + VLAN PTP packets are encapsulated in Ethernet
MAC frames with a VLAN tag.
According Port Type This encapsulation format applies for ports
with the PTP Mode “Ordinary/Boundary and
Transparent Clock”.
PTP VLAN packets are encapsulated accord-
ing to the encapsulation format used by the
port used by the PTP VLAN, e.g.:
- CVP, access port type: Ethernet MAC frames
without VLAN tag.
- CVP, trunk port type: Ethernet MAC frames
with VLAN tag.
- MPLS-TP port type: Ethernet MAC frames
with MPLS tags.
- MPLS-TP port on a VLAN subinterface:
Ethernet MAC frames with a VLAN and MPLS
tags.
UDP/IPv4 PTP packets are encapsulated in UDP/IPv4
packets and transported in a VLAN.
Forward Multicast Forwarding of multicast PTP messages is
required if the physical port acts as Transpar-
ent Clock for multicast PTP messages.
Multicast PTP packets are terminated at the
port and not forwarded.
VLAN ID 1 … 4089 VLAN ID to be used with Ethernet + VLAN
encapsulation, or with PTP transport via a
VLAN interface.
CoS CoS 0 … CoS 7 VLAN Class of Service to be used with Ether-
net + VLAN encapsulation, or with PTP trans-
port via a VLAN interface.

Table 11: AP: / Synchronization / PTP, Ports & Streams (continued)

Role Slave The PTP stream has the slave role.
The PTP stream can be used as PETS synchro-
nization source.
Master The PTP stream has the master role.
The PTP stream cannot be used as PETS syn-
Master Or Slave The PTP stream has the master or slave role,
depending of the forwarding direction of the
timing information.
The PTP port can be used as PETS synchroni-
zation source.
If the port streams role is configured to “Mas-
ter Or Slave” the “Unicast” addressing mode
must be used.
Addressing Unicast The stream uses unicast PTP messaging.
Multicast The stream uses multicast PTP messaging.
This parameter value is not available for the
“Master Or Slave” role.
Received QL Do Not Use The received QL value is = 15, or the port oper-
ational state is down, or the port is a trans-
parent port.
Unknown The received PTP QL is 0 (Clock Class = 82).
1 … 14 The received QL value is < 15.
Transmitted QL Do Not Use The “Do Not Use” quality level is transmitted
as QL value = 15 (Clock Class = 110).
Unknown The “Unknown” QL is sent as long as the PETS
is not phase locked. This inhibits the phase
locking of the downstream PTP slave clock.
The “Unknown” QL is sent if the port is a
transparent port.
1 … 14 Display of the transmitted QL value < 15.
1. See note below
Please note:
When the PTP Transport is configured to “UDP/IPv4 (L3)” and the PTP Mode is
configured to “Ordinary/Boundary And Transparent Clock” the following restrictions
apply with the CESM1 and CESM2 core units:
→ Both ports must use the “CVP” or “PWAC” port type, or both ports must use the
“MPLS-TP” or “VLAN Subinterfaces” port type.
VLANs and streams are managed with the following FOXCST command buttons:
• Create a new PTP VLAN interface:
When clicking on this button, the FOXCST launches a dialog to create a new PTP VLAN
interface.
Please note:
Up to 10 PTP VLANs can be created. The number of PTP VLANs must be shared
with the number of PTP ports configured to “Ordinary/Boundary Clock”.

Please note:
The configured PTP VLAN must also be added to the FOX61x Switch VLANs.
Please note:
The port mode of a PTP VLAN is fixed to “Ordinary/Boundary Clock”.
Please note:
The configured PTP VLAN is transported and time stamped via a physical port con-
figured to the PTP mode “Ordinary/Boundary and Transparent Clock”.
Please note:
The PTP VLAN ID must not be used as management VLAN ID. Select a PTP
• Create a new stream:
When clicking on this button, a new stream is added to the port or VLAN. The PTP Mode of
the port must be configured to Ordinary/Boundary Clock before adding a stream.
Please note:
A PTP port or VLAN is not operable as Ordinary/Boundary clock if no stream is
available.
→ Add a stream to every port or VLAN operated in the Ordinary/Boundary Clock
mode.
Please note:
Only one stream can be created for a port or a VLAN.
→ The creation of more than one stream will be available in a future release.
Please note:
A PTP port operating in the “Ordinary/Boundary And Transparent Clock” mode
requires no stream.
• Delete a stream or a VLAN:
When clicking on this button, the selected stream or VLAN will be deleted.
• Expand all rows in the Ports & Streams table:
When clicking on this button, all port and VLAN rows will be expanded to show the available
streams.
• Collapse all rows in the Ports & Streams table:
When clicking on this button, all port and VLAN rows will be collapsed, hiding the streams.
Depending of the “PTP transport mode” parameter configuration (see section 8.4.2 AP: / Syn-
chronization / PTP, Configuration (on page 194)), the PTP VLAN interfaces that are created use
different parameters.
“Create PTP VLAN Interface” dialog using the “PTP transport” mode = Ethernet (L2):

Table 12: AP: / Synchronization / PTP, Ports & Streams - Create PTP VLAN Interface
VLAN Configura- VLAN ID 1 … 4095 Enter the PTP VLAN ID.
tion Default is the next unused VLAN ID ≥ 100.
PTP Transport Ethernet (L2) PTP messages use Ethernet (MAC) address-
ing.
Role Slave The PTP interface acts as a slave, i.e. it is con-
nected to a master interface (e.g. a grand-
master).
CoS CoS 0 … CoS 7 VLAN Class of Service to be used with PTP
transport via a VLAN interface.
“Create PTP IP VLAN Interface” dialog using the “PTP transport” mode = UDP/IPv4 (L3):

Table 13: AP: / Synchronization / PTP, Ports & Streams - Create PTP IP VLAN Interface
IP VLAN Configura- VLAN ID 1 … 4095 Enter the PTP VLAN ID.
tion Default is the next unused VLAN ID ≥ 100.
PTP Transport UDP/IPv4 (L3) PTP messages use IPv4 addressing.
The used UDP ports are 319 and 320.
Role Slave The PTP interface acts as a slave, i.e. it is con-
nected to a master interface (e.g. a grand-
master).
Master The PTP interface acts as a master for other
slave interfaces.
See notes below the table.
Local IP Address <IPv4 address> Enter the IP address of the local interface to
be used as source IP address.
Each layer 3 VLAN interface must use a sepa-
rate subnet.
Default is empty
Netmask <IPv4 address> Enter the network mask of the local interface.
Default is empty.
Please note:
The “Master” role of a PTP IP VLAN is not available for the CESM1 and CESM2
units.
Please note:
The maximum number of “Master” role instances is limited to 3 per network ele-
ment.
Please note:
The “Master” role of a PTP IP VLAN supports up to 20 slaves.
→ An additional slave is only served if the contract of one of the currently active
slaves terminates. See section 8.4.1.8 AP: / Synchronization / PTP, Ports &
Streams - PTP Status (on page 187).
Please note:
The maximum number of PTP messages of a “Master” role instances is limited to 2
Announce, 32 Sync and 32 Delay messages per second. If a connected slave
requests higher values, the request will be silently discarded.
Please note:
A VLAN slave will send signaling messages towards the master, even if it is not
configured as a PTP source.
“Create ETH VLAN Stream” dialog using the “PTP transport” mode = Ethernet (L2):

Table 14: AP: / Synchronization / PTP, Ports & Streams - Create ETH VLAN Stream
Create ETH VLAN Stream stream-1 Select the stream identifier.
Stream Destination MAC <MAC address> Enter the MAC address of the PTP Grand Mas-
address ter Ethernet port.
The Destination MAC Address must be unique
over all streams.
Default is empty
“Create IP VLAN Stream” dialog using the “PTP transport” mode = UDP/IPv4 (L3):
Please note:
A stream can only be added for IP VLANs having the “Slave” role.
Table 15: AP: / Synchronization / PTP, Ports & Streams - Create IP VLAN Stream
Create IP VLAN Stream stream-1 Select the stream identifier.
Stream Destination IP <IPv4 address> Enter the IP address of the remote interface
Address to be used as destination IP address.
rate subnet.
Default is empty

The SFP-based 1 GbE interfaces port-1 and port-2 on the CESM1 and CESM2
units are not operable as PTP timing sources.
→ The port-1 and port-2 must use the 10 GbE mode to be usable as PTP timing
source.
Please note:
A core unit port is only selectable as PTP source if the PTP configuration is set up
correspondingly:
→ AP: /Synchronization/PTP, Ports & Streams:
PTP Mode = Ordinary/Boundary Clock.
Role = Slave, or Master Or Slave.
→ The port must have at least one stream.
Please note:
A PTP VLAN or PTP IP VLAN is only selectable as PTP source if the PTP configu-
ration is set up correspondingly:
The PTP (IP) VLAN must be added to the table
→ The PTP (IP) VLAN must have at least one stream.

8.4.1.1 AP: / Synchronization / PTP, Ports & Streams - Port Configuration
Table 16: AP: / Synchronization / PTP, Ports & Streams - Port Configuration
Port Configuration PTP Mode Disabled The port is not used as a PTP port.
In the Disabled PTP Mode no stream must be
present.
Ordinary/Boundary Clock Use the port or VLAN as PTP port of an ordi-
nary or boundary clock.
PTP VLANs are not supported on ports con-
figured as “Ordinary/Boundary Clock”.
Ordinary/Boundary and The port is simultaneously used as “Ordinary
Transparent Clock Clock” or “Boundary Clock”, and “Transparent
Clock”.
PTP VLANs must be used on ports configured
as “Ordinary/Boundary and Transparent
Clock”.
Encapsulation 1 Ethernet PTP packets are encapsulated in Ethernet
MAC frames.
This encapsulation format applies for ports
with the PTP Mode “Ordinary/Boundary
Clock”.
Ethernet + VLAN PTP packets are encapsulated in Ethernet
MAC frames with a VLAN tag.
This encapsulation format applies for ports
with the PTP Mode “Ordinary/Boundary
Clock”.

Table 16: AP: / Synchronization / PTP, Ports & Streams - Port Configuration (continued)
According Port Type This encapsulation format applies for ports
with the PTP Mode “Ordinary/Boundary and
Transparent Clock”.
PTP VLAN packets are encapsulated accord-
ing to the encapsulation format used by the
port used by the PTP VLAN, e.g.:
- CVP, access port type: Ethernet MAC frames
without VLAN tag.
- CVP, trunk port type: Ethernet MAC frames
with VLAN tag.
- MPLS-TP port type: Ethernet MAC frames
with MPLS tags.
- MPLS-TP port on a VLAN subinterface:
Ethernet MAC frames with a VLAN and MPLS
tags.
Forward Multicast Forwarding of multicast messages is
required if the grand master clock generates
multicast frames.
VLAN ID 1 … 4089 VLAN ID to be used with Ethernet + VLAN
encapsulation.
CoS CoS 0 … CoS 7 VLAN Class of Service to be used with Ether-
net + VLAN encapsulation.
QL Transmission The QL Transmission table is only available if
a stream has been configured for the port
which has the “Role = Master” or “Role = Mas-
ter Or Slave”.
Source PTP-1 Synchronization sources are all the PTP clock
PTP-2 sources as they are configured at the AP: /
Synchronization/PTP, Configuration.
PTP-4
Internal
Usage CanBeUsed Transmit the QL value of the selected syn-
chronization source
DoNotUse Transmit the QL value 15, i.e. indicating that
the traffic signal cannot be used as a synchro-
nization source.
1. See note below
Please note:
When the PTP Transport is configured to “UDP/IPv4 (L3)” and the PTP Mode is
configured to “Ordinary/Boundary And Transparent Clock” the following restrictions
apply with the CESM1 and CESM2 core units:

The SFP-based 1 GbE interfaces port-1 and port-2 on the CESM1 and CESM2
units are not operable as PTP timing sources.
→ The port-1 and port-2 must use the 10 GbE mode to be usable as PTP timing
source.

Please note:
A core unit port is only selectable as PTP source if the PTP configuration is set up
correspondingly:
PTP Mode = Ordinary/Boundary Clock.
Role = Slave, or Master Or Slave.
→ The port must have at least one stream.
8.4.1.2 AP: / Synchronization / PTP, Ports & Streams - Port Status

The port uses the “Ordinary/Boundary Clock” mode and the port stream has the “Master Or
Slave” role (left), or the stream has the “Slave” role (right):
The port uses the “Ordinary/Boundary Clock” mode and the port stream has the “Master” role
(left), or the port uses the “Ordinary/Boundary and Transparent Clock” mode (right):

Please note:
The “Received QL” parameter is only available if the port stream has the “Master
Or Slave” or “Slave” role.
Please note:
The “Transmitted QL” parameter is only available if the port stream has the “Master
Or Slave” or “Master” role.
Table 17: AP: / Synchronization / PTP, Ports & Streams - Port Status
MAC Address Local MAC Address <MAC address> MAC address of the local physical port.
This address is used as the source address of
the PTP stream.
Clock Quality Received QL Do Not Use The received QL value is = 15, or the port oper-
ational state is down, or the port is a trans-
parent port.
Transmitted QL Do Not Use The “Do Not Use” quality level is transmitted
The “Unknown” QL is sent if the port is a
transparent port.
Clock Quality, Par- Grandmaster Iden- 16 hex characters Clock identity attribute of the grandmaster
ent Data Set tity clock.
Clock Class 0 … 255 Attribute of an ordinary or boundary clock
that denotes the traceability of the time or
frequency distributed by the grandmaster
clock.
See table 5 of IEEE1588-2008.
In the FOX61x the Clock Class parameter car-
ries the Quality Level information in the
Announce messages (table 1 of ITU-T
G.8265.1).
Refer to section 5.8.1.3 Quality Level with PTP
Clock Class (on page 61).
Clock Accuracy Unknown Characterizes a clock for the purpose of the
25 ns … 10 s best master clock (BMC) algorithm.
See table 6 of IEEE 1588-2008.
Worse than 10 s
Grandmaster Pri- 0 … 255 The attribute is used in the execution of the
ority 1 best master clock algorithm.
Lower values take precedence.

Table 17: AP: / Synchronization / PTP, Ports & Streams - Port Status (continued)
Steps Removed 0 … 255 The number of communication paths (Bound-
ary Clocks) traversed between the local clock
and the grandmaster clock.
“1” means the Ordinary/Boundary Clock is
directly connected to the Grandmaster Clock.
If the “Steps Removed” parameter is ≥ 255 it
is assumed that there is a timing loop. The
clock is qualified as invalid and is no longer
used timing source.
Note: There is a risk that the clock source
selection will toggle between two clock
sources if the preferred clock source relies on
a looped timing.
Offset Scaled Log 0 … 65’535 A static constant determined by the manufac-
Variance turer, or
based on measured or modeled behavior of
the components of the local clock and its
environment.
Clock Quality, Current UTC Off- -215 … 215 s Offset between International Atomic Time
Time Properties set (TAI) and Universal Coordinated Time (UTC).
Current UTC Off- The parameter is true if the “Current UTC Off-
set Valid set” is known to be correct.
Leap 59 The parameter is true if the last minute of the

current UTC day contains 59 seconds.

Time Traceable The parameter is true if the timescale and the

value of “Current UTC Offset” are traceable to
a primary reference.
Frequency Trace- The parameter is true i if the frequency deter-
able mining the timescale is traceable to a primary
reference.
PTP Timescale The parameter is true if the clock timescale of
the grandmaster clock is PTP.
Time Source Atomic Clock Source of time used by the grandmaster

GPS clock.
Terrestrial Radio
PTP
NTP
Hand Set
Internal Oscillator
Other
8.4.1.3 AP: / Synchronization / PTP, Ports & Streams - Port Performance Management
The performance management (PM) management functions are available within the following
tabs:
• AP: / Synchronization / PTP, Ports & Streams - User Counters
• AP: / Synchronization / PTP, Ports & Streams - History 15min

• AP: / Synchronization / PTP, Ports & Streams - History 24h

• AP: / Synchronization / PTP, Ports & Streams - Chart History 15min
• AP: / Synchronization / PTP, Ports & Streams - Chart History 24h
For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The port PTP PM parameters are presented in the “PTP Timestamping Counters” group.
The “PTP Timestamping Counters” group provides the following PM parameters:
Table 18: PM group: PTP Timestamping Counters

PM parameter Description
RX PTP Timestamped Packets Number of received packets with PTP timestamps.
TX PTP Timestamped Packets Number of transmitted packets with PTP timestamps.
RX PTP Packets FCS Error Number of received packets with FCS errors.
TX PTP Packets FCS Error Number of transmitted packets with FCS errors.
8.4.1.4 AP: / Synchronization / PTP, Ports & Streams - Stream Configuration (Port)
Table 19: AP: / Synchronization / PTP, Ports & Streams - Port Stream Configuration
Stream Configura- Role Slave The PTP stream has the slave role.
tion The PTP stream can be used as PETS synchro-
nization source.
Master The PTP stream has the master role.
Master Or Slave The PTP stream has the master or slave role,
depending of the forwarding direction of the
timing information.
The PTP port can be used as PETS synchroni-
zation source.
If the port streams role is configured to “Mas-
ter Or Slave” the “Unicast” addressing mode
must be used.

Table 19: AP: / Synchronization / PTP, Ports & Streams - Port Stream Configuration (continued)
Stream Configura- Mode Unicast The stream uses unicast PTP messaging.
tion, Addressing If the role is configured to “Master Or Slave”
this is the only addressing parameter value.
Multicast The stream uses multicast PTP messaging.
This parameter value is not available for the
“Master Or Slave” role.
Destination MAC <MAC address> Enter the MAC address of the remote Ether-
Address net port (Master) when using the unicast
addressing scheme.
Default: 01:1B:19:00:00:00.
over all streams, except the specific multicast
address 01:1B:19:00:00:00.
Local MAC Address <MAC address> MAC address of the local physical port.
the PTP stream.
Stream Configura- Announce 1 Message every 2 Sec- Number of messages per interval for the
tion, Message onds Announce message type, used for the unicast
Intervals 1 Message Per Second negotiation.
This type of messages is only applicable for
2 Messages Per Second PTP ports in the master role.
4 Messages Per Second
Sync 2 Messages Per Second Number of messages per interval for the Sync
4 Messages Per Second message type and the follow up messages,
used for the unicast negotiation.
8 Messages Per Second The message interval should match the PTP
16 Messages Per Second message intervals configured at the AP: /Syn-
chronization/PTP, Configuration.
Delay 2 Messages Per Second Number of messages per interval for the
4 Messages Per Second Delay Request message type and the
response messages, used for the unicast
8 Messages Per Second negotiation.
message intervals configured at the AP: /Syn-

On the CESM1 and CESM2 units the total number of messages on physical port
streams is limited to 640 messages per second.
→ When using the maximum message interval values the number of physical
ports is limited to 640/104 = 6. Consider to decrease the message interval val-
ues when operating more than 6 physical port streams. Otherwise messages
will be lost.
→ When using the default message interval values on 10 physical port streams
the total number of messages is 340 messages per second. There is no restric-
tion.
8.4.1.5 AP: / Synchronization / PTP, Ports & Streams - Stream Performance Management (Port)
The performance management (PM) management functions are available within the following
tabs:
• AP: / Synchronization / PTP, Ports & Streams - User Counters

• AP: / Synchronization / PTP, Ports & Streams - History 15min

• AP: / Synchronization / PTP, Ports & Streams - History 24h
• AP: / Synchronization / PTP, Ports & Streams - Chart History 15min
• AP: / Synchronization / PTP, Ports & Streams - Chart History 24h
For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The stream PTP PM parameters are presented in the “PTP Counters” group.
The “PTP Counters” group provides the following PM parameters:
Table 20: PM group: PTP

PM parameter Description
Announce RX Messages Number of received announce messages.
Announce RX Processed Messages Number of received and processed announce messages.
Announce RX Lost Messages Number of lost announce messages.
Announce TX Messages Number of transmitted announce messages.
Signaling RX Messages Number of received signaling messages.
Signaling RX Processed Messages Number of received and processed signaling messages.
Signaling RX Lost Messages Number of lost signaling messages.
Signaling TX Messages Number of transmitted signaling messages.
Sync RX Messages Number of received sync messages.
Sync RX Processed Messages Number of received and processed sync messages.
Sync RX Lost Messages Number of lost sync messages.
Sync TX Messages Number of transmitted sync messages.
Delay Request RX Messages Number of received delay request messages.
Delay Request RX Processed Messages Number of received and processed delay request mes-
sages.
Delay Request RX Lost Messages Number of lost delay request messages.
Delay Request TX Messages Number of transmitted delay request messages.
Delay Response RX Messages Number of received delay response messages.
Delay Response RX Processed Mes- Number of received and processed delay response mes-
sages sages.
Delay Response RX Lost Messages Number of lost delay response messages.
Delay Response TX Messages Number of transmitted delay response messages.
The PTP performance management history counters can be displayed in graphical charts:
• Chart History 15min, for the History 15min counters,
• Chart History 24h, for the History 24h counters.


Table 21: Chart History 15min and History 24h

PTP Loaded at <yyyy-mm-dd Timestamp of the last refresh of the graphical
hh:mm:ss> charts.
Refresh Refresh the graphical charts.
Measurements Display of all 15 minutes measurement intervals
(15 Min) available in the History 15min counters.
The first captured interval is left most, the last
captured interval is right most.
Measurements Display of all 24 hours measurement intervals
(24 Hours) available in the History 24h counters.
The first captured interval is left most, the last
captured interval is right most.
Announce Announce RX Mes- Number of received announce messages.
sages
Announce RX Pro- Number of received and processed announce
cessed Messages messages.
Announce RX Lost Number of lost announce messages.
Messages
Announce TX Mes- Number of transmitted announce messages.
sages
Signaling Signaling RX Mes- Number of received signaling messages.
sages
Signaling RX Pro- Number of received and processed signaling
Signaling RX Lost Number of lost signaling messages.
Messages
Signaling TX Mes- Number of transmitted signaling messages.
sages
Sync Sync RX Messages Number of received sync messages.
Sync RX Processed Number of received and processed sync mes-
Messages sages.
Sync RX Lost Mes- Number of lost sync messages.
sages
Sync TX Messages Number of transmitted sync messages.
Delay Request Delay Request RX Number of received delay request messages.
Messages
Delay Request RX Pro- Number of received and processed delay request
Delay Request RX Lost Number of lost delay request messages.
Messages
Delay Request TX Number of transmitted delay request messages.
Messages
Delay Response Delay Response RX Number of received delay response messages.
Messages
Delay Response RX Number of received and processed delay
Processed Messages response messages.
Delay Response RX Number of lost delay response messages.
Lost Messages
Delay Response TX Number of transmitted delay response mes-
Messages sages.

Please note:
Pointing with the mouse pointer on an (inflection) point of a counter curve displays
the counter value with the corresponding time stamp at this point.
8.4.1.6 AP: / Synchronization / PTP, Ports & Streams - VLAN Configuration
“PTP transport” mode = Ethernet (L2):
Table 22: AP: / Synchronization / PTP, Ports & Streams - VLAN Configuration
Ethernet VLAN VLAN ID 1 … 4095 Display of the configured PTP VLAN ID.
Configuration This parameter is read-only.
PTP Transport Ethernet Display of the PTP transport address mode.
This parameter is read-only.
Role Slave Display of the configured PTP role.
“PTP transport” mode = UDP/IPv4 (L3):

Table 23: AP: / Synchronization / PTP, Ports & Streams - IP VLAN Configuration
IP VLAN Configura- VLAN ID 1 … 4095 Display of the configured PTP VLAN ID.
tion This parameter is read-only.
PTP Transport UDP/IPv4 (L3) Display of the PTP transport address mode.
The used UDP ports are 319 and 320.
Role Slave Display of the configured PTP role.
Master This parameter is read-only.
Local IP Address <IPv4 address> Display of the IP address of the local interface
to be used as source IP address.
rate subnet.
Netmask <IPv4 address> Display of the network mask of the local inter-
face.
Please note:
A VLAN slave will send signaling messages towards the master, even if it is not
configured as a PTP source.
Please note:
A VLAN master which is not phase locked will send the quality level 0 towards the
slaves.
→ This prevents the slaves to synchronize to the non phase locked master.
Please note:
ment.
Please note:
slaves terminates. See section 8.4.1.8 AP: / Synchronization / PTP, Ports &
Streams - PTP Status (on page 187).
Please note:
The PTP VLAN ID must not be used as management VLAN ID. Select a PTP
Please note:
A PTP VLAN or PTP IP VLAN is only selectable as PTP source if the PTP configu-
ration is set up correspondingly:
The PTP (IP) VLAN must be added to the table
→ The PTP (IP) VLAN must have at least one stream.

8.4.1.7 AP: / Synchronization / PTP, Ports & Streams - VLAN Status
Table 24: AP: / Synchronization / PTP, Ports & Streams - VLAN Status
MAC Address MAC Address <MAC address> MAC address of the local VLAN port.
the PTP stream.
8.4.1.8 AP: / Synchronization / PTP, Ports & Streams - PTP Status

This management function is only available for PTP IP VLANs operating in the “Master” role.
Table 25: AP: / Synchronization / PTP, Ports & Streams - PTP Status
Clock Quality Transmitted QL Do Not Use The “Do Not Use” quality level is transmitted
Stream Table The stream table shows all PTP slaves which
exchange Announce, Sync or Delay Response
messages with the PTP Master.
A PTP Master supports up to 20 slaves.
See the warning below the table.
# 1 … 20 Table entry identifier of a PTP slave.
Destination <IPv4 address> IPv4 address of the PTP slave.
Address
Announce Interval 1 Message every 4 Sec- Number of Announce messages per interval.
onds A contract request is refused by the Master if
1 Message every 2 Sec- the requested message rate is higher than 2
onds messages per second.
1 Message Per Second

No Messages The PTP slave is disconnected from the PTP
Master. No Announce messages are
exchanged.

Table 25: AP: / Synchronization / PTP, Ports & Streams - PTP Status (continued)
Sync Interval 1 Message every 4 Sec- Number of Sync messages per interval.
onds A contract request is refused by the Master if
1 Message every 2 Sec- the requested message rate is higher than 32
onds messages per second.

No Messages The PTP Slave is not synchronized to the PTP
Master. No Sync messages are exchanged.
Delay Response 1 Message every 4 Sec- Number of Delay Response messages per
Interval onds interval.
1 Message every 2 Sec- A contract request is refused by the Master if
onds the requested message rate is higher than 32
messages per second.
No Messages The slave is not synchronized to the PTP Mas-
ter. No Delay Response messages are
exchanged.
Contract Duration 300 The contract duration for the message
[s] exchange with the PTP slaves is fixed to
300 s.
Remaining Time [s] 0 … 300 Time until the contract for the message
exchange with the PTP slave terminates.
PTP slaves that do not exchange messages
with the PTP master will be removed from the
Stream Table at the contract termination.

The FOX61x software firewall limits the number of ingress PTP packets to 2’500
per second on port 319 and to 400 per second on port 320.
Please note:
ment.
Please note:
slaves terminates.

8.4.1.9 AP: / Synchronization / PTP, Ports & Streams - Stream Configuration (VLAN)
“PTP transport” mode = Ethernet (L2):
Table 26: AP: / Synchronization / PTP, Ports & Streams - VLAN Stream Configuration
Stream Configura- Role Slave The PTP VLAN stream has the slave role.
tion The PTP VLAN stream can be used as PETS
synchronization source.
tion, Addressing Destination MAC <MAC address> Enter the MAC address of the PTP Grand Mas-
Address ter Ethernet port.
Default: 00:00:00:00:00:00
over all streams.
Local MAC Address <MAC address> MAC address of the local VLAN port.
the PTP stream.


Table 26: AP: / Synchronization / PTP, Ports & Streams - VLAN Stream Configuration (continued)
“PTP transport” mode = UDP/IPv4 (L3):
Table 27: AP: / Synchronization / PTP, Ports & Streams - IP VLAN Stream Configuration
Stream Configura- Role Slave The PTP VLAN stream has the slave role.
tion The PTP VLAN stream can be used as PETS
synchronization source.
tion, Addressing Local IP Address <IPv4 address> Display of the IP address of the local interface
to be used as source IP address.
rate subnet.
Netmask <IPv4 address> Display of the network mask of the local inter-
face.
Destination IP <IPv4 address> Display of the IP address of the PTP Grand
Address Master IPv4 interface.


Table 27: AP: / Synchronization / PTP, Ports & Streams - IP VLAN Stream Configuration (continued)
8.4.1.10 AP: / Synchronization / PTP, Ports & Streams - Status (VLAN Stream)

Table 28: AP: / Synchronization / PTP, Ports & Streams - VLAN Stream Status
Clock Quality Received QL Do Not Use The received QL value is = 15, or the VLAN is
not operational.
Clock Quality, Par- Grandmaster Iden- 16 hex characters Clock identity attribute of the grandmaster
ent Data Set tity clock.
clock.
See table 5 of IEEE1588-2008.
In the FOX61x the Clock Class parameter car-
ries the Quality Level information in the
Announce messages (table 1 of ITU-T
G.8265.1).
Refer to section 5.8.1.3 Quality Level with PTP
Clock Class (on page 61).
Worse than 10 s
used timing source.
a looped timing.
Variance turer, or
environment.
Clock Quality, Current UTC Off- -215 … 215 s Offset between International Atomic Time
Time Properties set (TAI) and Universal Coordinated Time (UTC).



Table 28: AP: / Synchronization / PTP, Ports & Streams - VLAN Stream Status (continued)
reference.

GPS clock.
Terrestrial Radio
PTP
NTP
Hand Set
Internal Oscillator
Other
Please note:
A PTP VLAN stream has always the PTP slave role.
→ It provides no transmitted QL.
Please note:
A PTP IP VLAN having the PTP master role has no stream access point.
→ The transmitted QL is available in the PTP Status management function. See
section 8.4.1.8 AP: / Synchronization / PTP, Ports & Streams - PTP Status (on
page 187).
8.4.1.11 AP: / Synchronization / PTP, Ports & Streams - Stream Performance Management (VLAN)
The performance management (PM) management function of a VLAN stream is identical to the
PM management function of a port stream. Refer to section 8.4.1.5 AP: / Synchronization / PTP,
Ports & Streams - Stream Performance Management (Port) (on page 181).

8.4.2 AP: / Synchronization / PTP, Configuration
Table 29: AP: / Synchronization / PTP, Configuration

Administrative State Down The FOX61x is not used as a PTP ordinary or boundary
Status clock.
It can be used as a PTP transparent clock.
No PTP port can be used as PETS timing source.
Up The FOX61x is used as a PTP boundary clock and/or
ordinary clock and/or transparent clock.
Network Protocol PTP Transport Ethernet (L2) The PTP messages are transported on the Ethernet
layer (layer 2).
UDP/IPv4 (L3) The PTP messages are transported on the UDP/IPv4
layer (layer 3).
Note: This applies for VLAN based PTP transport
only. Port based PTP transport is always Ethernet
based.

Table 29: AP: / Synchronization / PTP, Configuration (continued)

Clock Configura- Clock Mode One Step Time information uses a single event message.
tion Clock Domain 0 … 255 A domain consists of one or more PTP devices com-
municating with each other.
0 is the default domain.
Notes:
The default clock domain value according to ITU-T
G.8275.2 is 44.
The clock domain range 128 … 255 is reserved. Any
value configured in this range is translated to 0.
PTP Mode Mode Disabled The PTP mode is disabled. No PTP source is available
to be used as PETS clock source.
Frequency And The PETS frequency and the phase are recovered
Phase from the PTP.
Pure Hybrid The PETS frequency is recovered from a synchro-
nous Ethernet port and the phase is recovered from
the PTP. The synchronous Ethernet and PTP are
located at the same physical port.
Only the PDH Clock source has to be configured in
the PETS configuration. The PTP source is set auto-
matically and cannot be modified.
Awareness Full Aware All switches and routers in the packet network are
PTP aware, i.e. are a Boundary Clock or a Transpar-
ent Clock.
PTP Sources PTP-1 … PTP-4 <empty> No reference port selected as PTP source 1 to 4.
<MO address> Select a port or a VLAN from the list of available
ports and VLANs.
If the PTP Mode is configured to “Pure Hybrid” the
PTP Source is automatically configured to the same
source as the corresponding PDH Clock Source in
the PETS configuration.

Table 29: AP: / Synchronization / PTP, Configuration (continued)

Message Interval Sync 1 Message Per Sec- Number of messages per second for the Sync mes-
ond sage type and the follow up messages.
2 Messages Per The message interval should match the message
Second intervals configured on the PTP port at the AP: /Syn-
chronization/PTP, Ports & Streams - Port Configura-
4 Messages Per tion.
Second
8 Messages Per
Second
16 Messages Per
Second
32 Messages Per
Second
64 Messages Per
Second
Delay 1 Message Per Sec- Number of messages per second for the Delay
ond Request message type and the response messages.
2 Messages Per The message interval should match the message
Second intervals configured on the PTP port at the AP: /Syn-
chronization/PTP, Ports & Streams - Port Configura-
4 Messages Per tion.
Second
8 Messages Per
Second
16 Messages Per
Second
32 Messages Per
Second
64 Messages Per
Second

On the CESM1 and CESM2 units the total number of messages on physical port
streams is limited to 640 messages per second.
→ When using the maximum message interval values the number of physical
ports is limited to 640/104 = 6. Consider to decrease the message interval val-
ues when operating more than 6 physical port streams. Otherwise messages
will be lost.
→ When using the default message interval values on 10 physical port streams
the total number of messages is 340 messages per second. There is no restric-
tion.
Please note:
Only the Ethernet interfaces (port-1 to port-5) on the working core unit and the
redundant core unit, and port-1 to port-5 on the WAN port extension unit EPEX1
can be selected as PTP sources.

The optical 1 Gbit/s Ethernet interfaces on the CESM1 or CESM2 (port-1 and port-
2) unit cannot be used as PTP sources.
→ Use the 10 Gbit/s SFP-based interfaces instead.


The 1 Gbit/s electrical Ethernet interfaces can forward synchronous Ethernet only
in one direction. The forwarding direction is negotiated at startup of the Ethernet
link.
→ Restart the Ethernet link after the synchronization configuration.
→ For details please refer to [1KHW028774] User Manual “CESM3” or refer to
[1KHW028642] User Manual “CESM2, CESM2-F” or refer to [1KHW002469]
User Manual “CESM1, CESM1-F”.
Please note:
Using PTP in ring networks requires the timing selection based on the quality level
(QL). PTP makes not full use of the QL.
→ Use the “Pure Hybrid” PTP mode, where the QL handling is based on the syn-
chronous Ethernet ports QL.
8.4.3 AP: / Synchronization / PTP, ETR
Table 30: AP: / Synchronization / PTP, ETR

PPS Output PPS Mode Disabled The PPS output of the ETR interface is disabled
Enabled if Phase- The PPS output of the ETR interface is enabled as
Locked long as the PETS is phase locked.
Please note:
The ETR interface is only available on the CESM3 core unit.
8.4.4 AP: / Synchronization / PTP, LSP Configuration

Table 31: AP: / Synchronization / PTP, LSP Configuration

LSP Label Range The core unit ports inspect and time stamp
only MPLS packets with an LSP label value
inside the configured LSP label range.
A tunnel transporting the PTP VPLS Pseudo
Wires must use a label from the LSP label
range. All other traffic tunnels must use a
label outside this range.
Otherwise there is a risk that an encrypted
non-PTP packet is interpreted as decrypted
PTP packet and gets the time stamps errone-
ously updated.
The WAN port extension units EPEX1 do not
support this label range feature. See the list of
limitations of the EPEX1 unit embedded soft-
ware.
Minimum 16 … 1’048’575 Minimum inbound and outbound LSP MPLS
Header label value for PTP transport using
MPLS-TP.
Maximum 16 … 2’999 … 1’048’575 Maximum inbound and outbound LSP MPLS
Header label value for PTP transport using
MPLS-TP.
8.4.5 AP: / Synchronization / PTP, Status
Table 32: AP: / Synchronization / PTP, Status

PTP Status Clock Mode Electric Synchronized to an electrical reference.
Hybrid Synchronized to a hybrid reference.
Packet Synchronized to a packet reference.

Table 32: AP: / Synchronization / PTP, Status (continued)

Phase Reference PTP-1 … PTP-4 The PTP phase is synchronized to the indi-
cated timing source.
Internal The PTP phase is free running
<empty> PTP mode is disabled.
Time Stamp YYYY-MM-DD hh:mm:ss Shows the local time of the GUI.
PTP Parents Source PTP-1 … PTP-4 PTP clock source name.
Internal
Grandmaster Iden- 16 hex characters Clock identity attribute of the grandmaster
tity clock.
clock (table 5 of IEEE1588-2008).
The Clock Class parameter carries the Quality
Level information in the Announce messages
(table 1 of ITU-T G.8265.1).
See section 5.8.1.3 Quality Level with PTP Clock
Class (on page 61).
Worse than 10 s
used timing source.
a looped timing.
Variance turer, or
environment.
Time Properties Source PTP-1 … PTP-4 PTP clock source name.
Internal
Current UTC Off- -215 … 215 s Offset between International Atomic Time
set (TAI) and Universal Coordinated Time (UTC).


Table 32: AP: / Synchronization / PTP, Status (continued)


reference.

GPS clock.
Terrestrial Radio
PTP
NTP
Hand Set
Internal Oscillator
Other
Phase Adjustment Ongoing A phase adjustment is ongoing
No phase adjustment is ongoing
Size us Phase error that has to be corrected as long
as the phase adjustment is ongoing.
If no phase adjustment is ongoing the “size”
is 0.
Elapsed Time s Elapsed time of the ongoing phase adjust-
ment.
If no phase adjustment is ongoing the
“elapsed time” is 0.
Network Quality % Indication of the timing network quality:
10%: very poor
25%: poor
75%: good
8.4.6 AP: / Synchronization / PTP, Alarms

For a description of the
− “Alarms”
management function, please refer to the “Overview - Alarms” description in [1KHW002464]
8.4.7 AP: / Synchronization / PTP, Alarm Status and Alarm Configuration

The alarms located at this access point are also available in the FOXCST “Tree View” at the AP:
/ne, Fault Management.
The following alarms are available:
• LOPT1 … LOPT4
• POPL
Please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611” for a
description of the alarms.

For a description of the parameters of the

− “Alarm Status”, and
− “Alarm Configuration”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.
8.5 AP: / Synchronization / PETS

Please note:
The synchronization related management functions of TDM based ports
• port-y, Configuration - Synchronization, and
• port-y, Status - QL
are located at the corresponding access points of the TDM service unit.
→ For a description of these management functions please refer to the User Man-
ual of the TDM service unit.
8.5.1 AP: / Synchronization / PETS, Configuration

This dialog allows you to configure the clock sources for the PETS to select from, and to assign
priorities to the available sources. The priorities determine which source is selected by the auto-
matic synchronization source selection algorithm.

Table 33: AP: / Synchronization / PETS, Configuration

PDH Clock Sources PDH Clock Source 1 … <empty> No reference port selected as clock source,
PDH Clock Source 4 i.e. this source is not used in the selection
algorithm.
<MO address> Select a port from the list of available ports.
The administrative state of the clock source
must be “up” to be selectable.
PETS Clock Selec- Source ESI-1 Available timing sources for the PETS syn-
tion ESI-2 chronization.
The PTP-x clock sources are only used for the
PDH Clock Source 1 PETS frequency evaluation if the PTP mode is
PDH Clock Source 2 “Frequency and Phase”.
The PTP-x clock sources are only available if the
PDH Clock Source 3
PTP mode is configured to “Frequency And
PDH Clock Source 4 Phase”. See section 8.4.2 AP: / Synchronization
PTP-1 / PTP, Configuration (on page 194).
PTP-2
with the CESM1 and CESM2 core units.
PTP-4
Internal
Priority 1…7 The priority of a timing source is used as a
selection criterion if the selection algorithm is
configured to “priority based” (see below).
1 is the highest priority, 7 is the lowest prior-
ity.
It is possible to assign the same priority to
more than one source.
The internal timing source has a default prior-
ity of 7.
Disabled A disabled timing source is not used for the
PETS synchronization.
QL 1 … 14 The fixed quality level (QL) of a timing source
is used as a selection criterion if the selection
algorithm is configured to “QL based” (see
below).
1 is the highest QL, 14 is the lowest QL.
Assign a QL for timing sources that provide
no QL or if you want to fix the QL for a timing
source.
Note that the use of some of the QL values is
standardized.
The ESI-1 and ESI-2 timing sources have a
default quality level of 13.
The internal timing source has a default qual-
ity level of 11. The internal timing source QL is
applied when the PETS is running in Holdover
mode.
Do Not Use Assign the quality level value 15 to a source. A
source with QL = 15 is not selected as PETS
timing source if the selection algorithm is
configured to “QL based”.
Received Use the QL as received with the timing
source. The QL is transported within the SSM
(synchronization status message) or SSI (syn-
chronization status indication).
Timing sources not providing the SSM or SSI
only have an assigned (fixed) quality level.

Table 33: AP: / Synchronization / PETS, Configuration (continued)

Holdoff Time 0 … 60 s During the holdoff time the timing source
step 0.1 s selection process performs no switchover to
a lower priority or lower quality level timing
source.
The holdoff timer starts when the timing
source enters a failure state.
Wait-To-Restore Time 0 … 30 … 720 s During the wait to restore (WTR) time the
timing source selection process performs no
switchover from a lower priority or lower
quality level timing source to a higher priority
or higher quality level source.
The WTR timer is reset when the timing
source is in a failure state and starts when the
higher priority or higher quality level timing
source becomes fault free.
The internal timing source has a default wait-
to-restore time of 0 s.
Please note: If the Wait-To-Restore Time is
configured to a value in the range 0 … 10 s, a
time of 10 s is applied.
Selection Algorithm Priority Select the timing sources according to the
assigned priorities.
This selection algorithm disregards the qual-
ity levels (QL).
QL Select the timing sources according to the
received or assigned quality levels (QL).
The selection algorithm first considers the QL
and then the priority.
Please note:
Only two of the three electrical Ethernet interfaces (port-3 to port-5) on the CESM1
Please note:
Only two of the three 1 Gbit/s Ethernet interfaces (port-3 to port-5) on the CESM2
Please note:
The selection list for the PDH Clock Sources depends on the configuration made
on the respective units.

The 1 Gbit/s electrical Ethernet interfaces can forward synchronous Ethernet only
in one direction. The forwarding direction is negotiated at startup of the Ethernet
link.
→ Restart the Ethernet link after the synchronization configuration.
→ For details please refer to [1KHW028774] User Manual “CESM3” or refer to
[1KHW028642] User Manual “CESM2, CESM2-F” or refer to [1KHW002469]
User Manual “CESM1, CESM1-F”.
Please note:
Leave the selection for a PDH Clock Source undefined (empty) if you do not want
to select a reference port as clock source 1, 2, 3, or 4.

8.5.2 AP: / Synchronization / PETS, Status
“Clear WTR” dialog:
Table 34: AP: / ne, Status - PETS

Source Status Source ESI-1 List of all enabled timing sources.
ESI-2 The PTP-x clock sources are only available if the
PDH Clock Source 1 Phase” or “Pure Hybrid”. See section 8.4.2 AP: /
PDH Clock Source 2 Synchronization / PTP, Configuration (on
page 194).
PDH Clock Source 3
PDH Clock Source 4 with the CESM1 and CESM2 core units.
PTP-1
PTP-2
PTP-3
PTP-4
Internal
Priority 1…7 Configured priority value of the timing
Disabled source.
QL 1 … 14 Adapted or received quality level of the timing

Do Not Use source, as it is used by the selection algo-
rithm in the PETS selector B.
Unknown The timing source has the configured priority
= “disabled”, and QL = “received”.
Status Not Supervised Disposability of the timing source.
Available Please note:
- If the WTR Time has been configured to a
Holdoff value in the range 0 … 10 s the status WTR is
Failed not displayed.
Wait-To-Restore
value > 10 s the status displayed during the
first 10 s of WTR is “Failed”.

Table 34: AP: / ne, Status - PETS (continued)

Clock Status Selection Algo- Priority Display of the configured selection algorithm
rithm QL for the timing sources:
- Priority Table based
- Quality Level based
Selected Clock <Timing Source> Display of the selected timing source.
Source
Clock Operation Free Running Display of the current operation mode of the
Mode PETS system:
PETS synchronized to the internal oscillator.
Locked Locked to a traffic signal
Frequency-Locked The PETS frequency is locked to a traffic sig-
nal or to a PTP source.
Phase-Locked The PETS phase is locked to a PTP source 1.
Holdover The PETS keeps the acquired frequency from
a traffic signal which has been lost.
Regarding the used QL value see the note
below the table.
Clock Operation Auto Selection With the clock operation type it is possible to
Type Forced Free Running force the PETS to change its clock operation
mode for maintenance purposes.
Forced Holdover These manual commands override the auto-
matic selection.
A forced clock operation state activates the
maintenance function active (MFA) alarm.
The alarm PETS Holdover (PHO) is not acti-
vated.
Clear WTR … Open the FOXCST dialog to select a timing
source.
Clear WTR Source List ESI-1 The WTR timer can be cleared to immediately
ESI-2 switch back from the lower priority or lower
quality level timing source.
PDH Clock Source 1 The ESI-2 PDH clock source is only available
PDH Clock Source 3
PDH Clock Source 4
PTP-1
PTP-2
PTP-3
PTP-4
1. A valid PTP quality level (QL) is sent only when the clock operation mode is “Phase-Locked”.
Please note:
The PETS running in Holdover mode uses the QL value that has been configured
for the “Internal” PETS clock source. See section 8.5.1 AP: / Synchronization /
PETS, Configuration (on page 201).
The LOCKED LED on the core unit front indicates if the NE is locked to a synchronization
source:
• green: locked
• dark: not locked

XXXXx R1B
37900374
UNIT TRAFFIC
ACTIVE LOCKED
Figure 76: LEDs on the core unit front
Please note:
The SETS status is available on the SDH service unit. Please refer to
[1KHW002476] User Manual “SAMO1” or refer to [1KHW028668] User Manual
“SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F” for further information.
8.5.3 AP: / Synchronization / PETS, Alarms

− “Alarms”
8.5.4 AP: / Synchronization / PETS, Alarm Status and Alarm Configuration

• LOSP1 … LOSP4
• PCSL
• PHO
• POOL
• PPLL
• PSNP
FOX612/FOX611”.

8.6 AP: / Synchronization / ESO
8.6.1 AP: / Synchronization / ESO, Configuration
Table 35: AP: / Synchronization / ESO, Configuration

Operation Name Parameter Name Range Description / Details
PDH Clock Sources PDH Clock Source 1 <MO address> The managed object address of the
PDH Clock Source 2 <MO address> four PDH clock sources.
These parameters are read-only.
PDH Clock Source 3 <MO address>
PDH Clock Source 4 <MO address>
ESO-1 PETS Locked The external synchronization output
ESO-1 on the core unit is synchronized
to the PETS function.
The external synchronization output
ESO-1 on the core unit is synchronized
to the selected ESO clock source.

Table 35: AP: / Synchronization / ESO, Configuration (continued)

ESO-1 Clock Selection Source ESI-1 Note that the ESO Clock Selection
ESI-2 parameters are only available for the
non PETS locked mode. Refer to the
PDH Clock Source 1 parameter above.
PDH Clock Source 2 The “Source” column shows the avail-
able timing sources for the ESO-1 syn-
PDH Clock Source 3
chronization.
PDH Clock Source 4 These values are read-only.
Internal The ESI-2 PDH clock source is only avail-
able with the CESM1 and CESM2 core
units.
Priority 1…7 The priority of a timing source is used
as a selection criterion if the selection
algorithm is configured to “priority
based” (see below).
1 is the highest priority, 7 is the lowest
priority.
It is possible to assign the same prior-
ity to more than one source.
The internal timing source has a
default priority of 7.
Disabled A disabled timing source is not used
for the PETS synchronization.
QL 1 … 14 The quality level QL of a timing source
is used as a selection criterion if the
selection algorithm is configured to
“QL based” (see below).
1 is the highest QL, 14 is the lowest QL.
Assign a fixed QL for timing sources
that provide no QL or if you want to fix
the QL for a timing source.
Note that the use of some of the QL
values is standardized.
The ESI-1 and ESI-2 timing sources
have a default quality level of 13.
default quality level of 11.
Do Not Use Assign the quality level value 15 to a
source. A source with QL = 15 is not
selected as ESO timing source if the
selection algorithm is configured to
“QL based”.
Received Use the QL as received with the timing
source. The QL is transported within
the SSM (synchronization status mes-
sage).
Timing sources not providing the SSM
only have an assigned quality level
Holdoff Time 0 … 60 s, During the holdoff time the timing
step 0.1 s source selection process performs no
switchover to a lower priority or lower
The holdoff timer starts when the tim-
ing source enters a failure state.


Wait-To-Restore Time 0 … 30 … 720 s During the wait to restore (WTR) time
the timing source selection process
performs no switchover from a lower
priority or lower quality level timing
source to a higher priority or higher
quality level source.
The WTR timer is reset when the timing
source is in a failure state and starts
when the higher priority or higher qual-
ity level timing source becomes fault
free.
default wait-to-restore time of 0 s.
Please note: If the Wait-To-Restore
Time is configured to a value in the
range 0 … 10 s, a time of 10 s is
applied.
ESO-1 Selection Algo- Priority Select the timing sources in the non
rithm PETS locked mode according to the
assigned priorities.
This selection algorithm disregards
the quality levels (QL).
QL Select the timing sources in the non
PETS locked mode according to the
received or assigned quality levels
(QL).
The selection algorithm first considers
the QL and then the priority.
ESO-1 Squelched By Source ESI-1 Note that the ESO-1 Squelched By
Source ESI-2 Source parameters are only available
for the PETS locked mode. Refer to the
PDH Clock Source 1 parameter above.
PDH Clock Source 2 The “Source” column shows the avail-
able timing sources for the ESO-1 syn-
PDH Clock Source 3
chronization.
PDH Clock Source 4 The ESI-2 PDH clock source is only avail-
PTP-1 able with the CESM1 and CESM2 core
units.
PTP-2
PTP-3
PTP-4
Internal
Squelched The ESO-1 output on the core unit is
squelched, i.e. disabled, if the corre-
sponding source is selected.
The ESO-1 output on the core unit is
active, i.e. enabled, if the correspond-
ing source is selected.


ESO-1 Squelched By QL QL 1 … 15 Note that the ESO Squelched By QL
parameters are available for the PETS
locked and the non SETS locked
modes.
The “QL” column shows the quality lev-
els of the timing sources for the ESO-1
synchronization.
These values are read-only.
Squelched The ESO-1 output on the core unit is
squelched for the selected QL.
The ESO-1 output on the core unit is
active for the selected QL.
ESO-2 Clock Source SDH Clock Source <empty> The clock output signal ESO-2 is not
used.
<MO address> MO address of an available SDH unit
providing the ESO-2 clock on the core
unit.
8.6.2 AP: / Synchronization / ESO, Status
“Clear ESO-1 WTR” dialog:

Table 36: AP: / ne, Status - ESO

ESO-1 Source Sta- Source ESI-1 List of all enabled timing sources.
tus ESI-2 The PTP-x clock sources are only available if the
PDH Clock Source 1 Phase” or “Pure Hybrid”. See section 8.4.2 AP: /
PDH Clock Source 2 Synchronization / PTP, Configuration (on
page 194).
PDH Clock Source 3
PTP-1
PTP-2
PTP-3
PTP-4
Internal
Priority 1…7 Configured priority value of the timing
Disabled source.
QL 1 … 14 Adapted or received quality level of the timing

Do Not Use source, as it is used by the selection algo-
rithm in the PETS selector A.
Unknown The timing source has the configured priority
= “disabled” and QL = “received”.
Status Not Supervised Disposability of the timing source.
Available Please note:
Holdoff value in the range 0 … 10 s the status WTR is
Failed not displayed.
Wait-To-Restore
value > 10 s the status displayed during the
first 10 s of WTR is “Failed”.
ESO-1 Clock Status Selection Algorithm Priority Display of the configured selection algorithm
QL for the timing sources:
- Priority Table based
- Quality Level based
Selected Clock Source <Timing Source> Display of the selected timing source.
Clock Operation Mode Locked Display of the current operation mode of the
Acquiring ESO-1:
- Locked: Locked to the selected timing
Free Running source
Holdover - Acquiring: ESO-1 is not yet locked to the
selected timing source.
Squelched
- Free-running: Synchronized to the internal
oscillator.
- Holdover: ESO-1 keeps the acquired fre-
quency from a traffic signal which has been
lost (PETS-Locked mode only).
- Squelched: ESO-1 is disabled when all clock
sources are disabled.
Clear ESO-1 WTR Open the FOXCST dialog to select a timing
… source.

Table 36: AP: / ne, Status - ESO (continued)

Clear ESO-1 WTR Source List ESI-1 The WTR timer can be cleared to immediately
ESI-2 switch back from the lower priority or lower
PDH Clock Source 1 The PTP-x sources are only available for the
PDH Clock Source 2 ESO-1 PETS-locked mode.
Clearing the WTR timer of a PTP-x source
PDH Clock Source 3
clears the sources WTR timer of the PETS
PDH Clock Source 4 function, i.e. it has the same effect as the
PTP-1 “Clear WTR” operation in the PETS Status
management function.
PTP-2
PTP-3 with the CESM1 and CESM2 core units.
PTP-4
ESO-2 Clock Output Status Active Indicates that ESO-2 provides its timing sig-
nal.
Squelched Indicates that ESO-2 can not provide its tim-
ing signal; the output is squelched.
Not Available The configured SDH unit as ESO-2 source is
not available, e.g. has been removed from the
subrack.
8.6.3 AP: / Synchronization / ESO, Alarms

− “Alarms”
8.6.4 AP: / Synchronization / ESO, Alarm Status and Alarm Configuration

• ECSL
• ESOSNP
FOX612/FOX611”.
8.7 AP: / ne
8.7.1 AP: / ne, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”


FOX612/FOX611”.
The fault causes of the AP: /ne are listed in [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.
8.8 AP: / unit-11
8.8.1 AP: / unit-11 / neController / esi-z

For a description of the esi-z related management functions, please refer to [1KHW002469]
User Manual “CESM1, CESM1-F” or refer to [1KHW028642] User Manual “CESM2, CESM2-F”.
8.8.2 AP: / unit-11 / sync / esi-z

For a description of the esi-z and etr related management functions, please refer to
8.9 AP: / unit-x (SDH Service Unit)

For a description of the SDH synchronization related management functions, please refer to
[1KHW002476] User Manual “SAMO1” and refer to [1KHW028668] User Manual “SAMO2,
SAMO2-F, SAMO3, SAMO5, SAMO5-F”.

FOX61x | SYNCHRONIZATION ANNEX
9 Annex
9.1 Associated FOX61x Documents

[1KHW028777] Release Note “FOX61x System Release R15B”
[1KHW002460] System Description “FOX61x R15B”
[1KHW002497] Operating Instruction “Precautions and safety”
[1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”
[1KHW002462] Installation Instruction “FOX612 Installation”
[1KHW029142] Installation Instruction “FOX611 Installation”
[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”
[1KHW028522] User Manual “Management Communication”
[1KHW028618] User Manual “MPLS-TP Services”
[1KHW002467] User Manual “TDM Services”
[1KHW002469] User Manual “CESM1, CESM1-F”
[1KHW028642] User Manual “CESM2, CESM2-F”
[1KHW028774] User Manual “CESM3”
[1KHW029154] User Manual “EPEX1”
[1KHW002476] User Manual “SAMO1”
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”
[1KHW002474] User Manual “DATI1”
[1KHW028775] User Manual “DEFM1, DEFM1-F”
[1KHW028776] Product Description “Feature Licenses for FOX61x”

Hitachi Energy Switzerland Ltd
Bruggerstrasse 72
5400 Baden - Switzerland
Phone: please refer to https://www.hitachienergy.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
Email: communication.networks@hitachienergy.com
www.hitachienergy.com/communication-networks
Document ID: 1KHW029105
Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.

Synchronization Um

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Synchronization Um

Uploaded by

Copyright:

Available Formats

USER MANUAL

Document edition FOX61x System Release: R15B

Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Copyright 2022 Hitachi Energy. All rights reserved. 2

Copyright 2022 Hitachi Energy. All rights reserved. 3

5.6.5 ESO-1 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Copyright 2022 Hitachi Energy. All rights reserved. 4

7.1.4 PTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Copyright 2022 Hitachi Energy. All rights reserved. 5

1.1 Precautions and Safety

1.2 Symbols and Notations

Risk of operating trouble!

1.3 Document History

Copyright 2022 Hitachi Energy. All rights reserved. 6

1.4 Target Audience

1.5 Definition of Terms

Copyright 2022 Hitachi Energy. All rights reserved. 7

Copyright 2022 Hitachi Energy. All rights reserved. 8

Core Unit, protecting

Figure 1: PETS function in the FOX61x

Copyright 2022 Hitachi Energy. All rights reserved. 9

Core Unit, protecting

SDH Service Unit, prot.

SDH port SDH Timing

Figure 2: SETS function in the FOX61x

2.2 FOX61x Core and Service Units

Copyright 2022 Hitachi Energy. All rights reserved. 10

• LEDE1, E1 transport unit

Copyright 2022 Hitachi Energy. All rights reserved. 11

3.1 Feature Licenses

3.2 Functions and Specification Overview

3.3 Synchronization Related Standards Documents

Copyright 2022 Hitachi Energy. All rights reserved. 12

• ITU-T G.8261/Y.1361 (08/2019)

Copyright 2022 Hitachi Energy. All rights reserved. 13

4.1 Network Reference Timing Distribution

4.1.1 Master - Slave Timing Distribution

UTC UTC = universal time coordinated

PRC PRC = primary reference clock

SSU SSU SSU = synchronization supply unit

SEC SEC SEC SEC

Figure 3: Hierarchical TDM and SyncE synchronization network architecture

Copyright 2022 Hitachi Energy. All rights reserved. 14

UTC UTC = universal time coordinated

Figure 4: Hierarchical PTP synchronization network architecture

Copyright 2022 Hitachi Energy. All rights reserved. 15

SEC TDM SEC TDM

The number N of SEC between two

SEC TDM SEC TDM The number of SSU in a distribution

Figure 5: Synchronization network reference chain

4.1.2 Distributed PRC Timing Distribution

PRC PRC PRC PRC PRC = primary reference clock

SSU SSU SSU SSU SSU = synchronization supply unit

Figure 6: Distributed PRC network architecture

Copyright 2022 Hitachi Energy. All rights reserved. 16

4.1.3 Mixed PRC Timing Distribution

4.1.4 Timing Source Redundancy

SSU SSU SSU SSU

SEC SEC SEC SEC SEC SEC SEC SEC

SEC SEC SEC SEC SEC SEC SEC SEC

tree network ring network

active timing path