FOX61x TDM Services: User Manual

ABB Power Systems
FOX61x
TDM Services
User Manual
User Manual FOX61x
TDM Services
Release History: Release 1: December 2012
Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

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 ABB.
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 authorised by
contract or otherwise in writing by ABB.
Disclaimer: ABB has taken reasonable care in compiling this document, however ABB 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.
ABB 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.
ABB reserves the right to amend this document at any time without prior notice.
Blank pages: Any blank page present is to accommodate double-sided printing.
Document No.: 1KHW002467
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 2012 by ABB Switzerland Ltd
Table of Contents
1 Preface 7
1.1 Precautions and safety 7
1.2 Symbols and notations 7
1.3 Document history 7
2 Introduction 9
2.1 General 9
3 Specification 13
3.1 Feature licences 13
3.2 Functions and specification overview 13
4 Specification of TDM services 15

4.1 TDM services overview 15
4.2 Voice services 15
4.3 TDM data services 18
4.4 Packet data services 20
5 Functions 23
5.1 Implementation of the TDM cross connect functions 23
5.2 TDM connections 27
5.3 P12 functions 48
5.4 Synchronization 56
6 Commissioning 85
6.1 General prerequisites 85
6.2 PDH cross connections 86
6.3 SDH cross connections 90
6.4 Commissioning of the PDH synchronization 96
6.5 Commissioning of the SDH synchronization 99
6.6 Commissioning of a synchronization network 102
6.7 Connection test of readiness 115
7 Operation 117
7.1 Status and diagnostics 117
7.2 Fault management 119
7.3 Possible faults and related debugging 119
8 FOXCST reference 123

8.1 Introduction 123
FOX61xTDM Services 3
8.2 AP: / ne 128
8.3 AP: / unit-11 / neController / esi-z 141
8.4 TDM cross connections 142
9 Annex 157
9.1 Associated documents 157
4 FOX61xTDM Services
Figures
Figure 1: TDM signal bidirectional connection, unprotected 11

Figure 2: TDM signal bidirectional connection, protected 11
Figure 3: TDM signal unidirectional connection, unprotected 12
Figure 4: TDM signal unidirectional connection, protected 12
Figure 5: Order wire voice service with FOX61x 16
Figure 6: FXS and FXO voice service with FOX61x 17
Figure 7: E&M voice service with FOX61x 17
Figure 8: MCAS routing in FOX61x 18
Figure 9: TDM data access with FOX61x 19
Figure 10: Ethernet over PDH data access with FOX61x 20
Figure 11: Ethernet over SDH data access with FOX61x 21
Figure 12: PBUS access 24
Figure 13: CTP roles in a connection 28
Figure 14: Example for the creation of a channel on a port (LEDE1) 33
Figure 15: P0_nc protection switching without CAS AIS supervision 41
Figure 16: P0_nc protection switching with CAS AIS supervision 41
Figure 17: Multipoint application example with SPR 43
Figure 18: Multipoint application example with a line break 44
Figure 19: Transparent termination mode application example 49
Figure 20: Clock master termination mode application example 50
Figure 21: Skipping of time slot 16 55
Figure 22: Hierarchical synchronization network architecture 56
Figure 23: Synchronization network reference chain 57
Figure 24: Distributed PRC network architecture 58
Figure 25: Timing distribution over Ethernet 58
Figure 26: Timing distribution over the packet network 59
Figure 27: PETS clock source selection 61
Figure 28: PETS clock source selection with 2 external and 1 internal clock sources 63
Figure 29: PETS clock source selection with 2 external clock sources 64
Figure 30: SETS functions 66
Figure 31: SETS clock source selection with 2 external and 1 internal clock sources 68
Figure 32: SETS and PETS implementation in FOX61x 71
Figure 33: QL handling for PDH traffic signals and other clock sources 75
Figure 34: QL handling for SDH traffic signals and other clock sources on SAMO1 79
Figure 35: QL handling for SDH traffic signals and other clock sources on SAMO2 80
Figure 36: Set-up for the PDH cross connections 86
Figure 37: Set-up for the SDH cross connections 91
Figure 38: Synchronization via two independent paths 103
Figure 39: QL setting to “Do Not Use” 104
Figure 40: Ports configured to not to be used as timing source 105
Figure 41: QL mapping of selected timing sources to “Do Not Use” 106
Figure 42: QL mapping of selected and internal timing sources to “Do Not Use” 106
Figure 43: SDH ring, one source, no failure 108
Figure 44: SDH ring, one source, ESI at NE1 failed 109
Figure 45: SDH ring, one source, NE1 failed 110
Figure 46: SDH ring, two sources, no failure 111
Figure 47: SDH ring, two sources, ESI at NE1 failed 112
Figure 48: SDH ring, two sources, ESI at NE1 failed and link failure between NE3 and NE4 113
Figure 49: SDH ring, two sources, ESI at NE1 and NE3 failed and link failure between NE3 and NE4 114
Figure 50: PETS synchronization access point tree 125
Figure 51: SETS synchronization access point tree 127
Figure 52: LEDs on the CESM1 front 139
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 EN 60950 (Safety of Information Technology
Equipment).
Please refer to the following document:
1KHW002497 FOX61x 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

Date FOX61x Changes since previous version
release
December 2012 R1 First release of the document for the FOX61x.
PREFACE
INTRODUCTION
2 Introduction
This section presents a general introduction to the TDM services application
in the sections General (on page 9) and TDM connections overview (on
page 11).
Section Functions and specification overview (on page 13) covers the
offered services with the relevant standards.
2.1 General
TDM based services in the FOX61x are part of the FOX61x multi-service
functionality. They can be implemented in one subrack together with packet-
based services.
This document describes the principles and the use of the TDM-based con-
nections in the FOX61x. The connections are used for the interconnection
between different TDM based service units at the PDH traffic layers P12 and
P0_nc. TDM-based connections can also be established on the SAMO1 and
SAMO2 units to interconnect signals at the SDH traffic layers VC-4, VC-3
and VC-12.
The FOX61x implements a TDM based bus, called PBUS. The PBUS allows
unlimited cross connections between PDH data signals with and without
CAS up to the bus limit of 128 x P12 (2048 kbit/s) or 4096 x P0 (64 kbit/s). It
is used to inter-connect traffic signals of all FOX61x TDM based core and
service units.
There is no restriction in the unit placement except for the slot 11 which is
reserved for the core unit CESM1. A TDM based unit can be plugged in any
free slot of the FOX61x subrack.
This user guide does not cover the packet-based aspects of services. For
details on packet based applications, refer to 1KHW002468 FOX61x Ether-
net Services.
For more details on FOX615 or FOX612, refer to 1KHW002464 FOX61x
System Description.
INTRODUCTION
2.1.1 FOX61x TDM core and service units

• CESM1, core unit
PETS synchronization functions, two 2048 kHz synchronization input
interfaces, two 2048 kHz synchronization output interfaces.
DCN router function.
• LEDE1, E1 transport unit
8 E1 interfaces 2048 kbit/s, structured and unstructured modes.
• DATI1, SHDSL TDM service unit,
8 SHDSL interfaces 2048 kbit/s, structured and unstructured modes.
• LESU1, PSTN FXS service unit,
16 analogue voice interfaces, subscriber side.
• SAMO1, STM-4 SDH and Ethernet over SDH transport unit,
2 STM-4 or STM-1 interfaces, 2 STM-1 interfaces.
4 Ethernet interfaces for EoS applications.
SETS synchronization functions.
• SAMO2, STM-16 SDH and Ethernet over SDH transport unit,
2 STM-16 or STM-4 interfaces, 2 STM-4 or STM-1 interfaces.
4 Ethernet interfaces for EoS applications.
SETS synchronization functions.
• LEDS1, TDM data interface unit,
4 data interfaces
− V.24/V.28, or
− V.35 (Appendix II), or
− X.24/V.11, or
− RS485 2-wire, or
− RS485 4 wire,
up to 1984 kbit/s, synchronous mode.
1 Ethernet interface for EoP (Ethernet over PDH) applications.
• LEDA1, E&M interface unit,
8 E&M interfaces, consisting of one 2-wire or 4-wire voice port and two
E&M signalling ports.
• LEXI1, PSTN FXO service unit,
12 analogue voice interfaces, local exchange side.
• LECO1, E0 data interface unit,
8 E0 interfaces 64 kbit/s, synchronous mode with codirectional timing
operation.
• EPSI1, Ethernet and IP routing unit,
4 Ethernet interfaces for EoP (Ethernet over PDH) applications.
Ethernet switch, IP routing functions.
• TEPI1, Teleprotection interface unit,
4 command interfaces for teleprotection applications.
16 binary inputs, 8 binary outputs for general purposes.
6 auxiliary relays.
• OPIC1, Optical protection interface unit,
4 optical protection interfaces.
Please refer to 1KHW002460 FOX61x Product Features and Characteristics
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.
INTRODUCTION
2.1.2 TDM connections overview

TDM connections can basically be classified according to the following prop-
erties:
• Directionality:
− Bidirectional,
− Unidirectional.
• Protection:
− Unprotected,
− Protected.
This makes it possible to implement TDM connections as presented in the
sections below.
2.1.2.1 Bidirectional connection, unprotected
The bidirectional unprotected connection is the standard connection applied

in most cases.
It connects a bidirectional traffic signal to another bidirectional traffic signal
on the same or any other TDM service unit in the FOX61x.
FOX61x
traffic signal unit-1 unit-2 traffic signal
Figure 1: TDM signal bidirectional connection, unprotected
2.1.2.2 Bidirectional connection, protected
The bidirectional protected connection can be used to protect e.g. a traffic

signal in the access network from failures in the TDM transport network.
It connects a working bidirectional traffic signal to another bidirectional traffic
signal on the same or any other TDM service unit in the FOX61x. In parallel
it connects a protecting bidirectional traffic signal to the same (protected)
traffic signal. A switch selects the received working or protecting signal to
forward it to the traffic signal interface. In the transmit direction the traffic sig-
nal is bridged to the working and the protecting signal path.
FOX61x
traffic signal traffic signal
unit-1 unit-3
working protected
traffic signal
unit-2
protecting
Figure 2: TDM signal bidirectional connection, protected
INTRODUCTION
2.1.2.3 Unidirectional connection, unprotected
The unidirectional unprotected connection is used in special applications as

e.g. broadcast or timing distribution, where only one direction of a path is
required.
It connects an incoming unidirectional traffic signal to another outgoing unidi-
rectional traffic signal on the same or any other TDM service unit in the
FOX61x.
FOX61x
traffic signal unit-1 unit-2 traffic signal
Figure 3: TDM signal unidirectional connection, unprotected
2.1.2.4 Unidirectional connection, protected
The unidirectional protected connection can be used to protect e.g. a traffic

signal in the access network from failures in the TDM transport network.
It connects a working unidirectional traffic signal to another unidirectional
traffic signal on the same or any other TDM service unit in the FOX61x. In
parallel it connects a protecting unidirectional traffic signal to the same (pro-
tected) traffic signal. A switch selects the received working or protecting sig-
nal to forward it to the traffic signal interface.
FOX61x
traffic signal traffic signal
unit-1 unit-3
working protected
traffic signal
unit-2
protecting
Figure 4: TDM signal unidirectional connection, protected
SPECIFICATION
3 Specification
3.1 Feature licences
Part of the FOX61x functionality is subject to feature licences. For more

information on feature licences please refer to 1KHW002459 FOX61x
Release Notes.
3.2 Functions and specification overview
The FOX61x network element provides the functions and conforms to the
corresponding standards and recommendations (conformance to applicable
parts of the standards) as stated in the 1KHW002460 FOX61x Product Fea-
tures and Characteristics.
SPECIFICATION
SPECIFICATION OF TDM SERVICES
4 Specification of TDM services

This section presents the TDM services available in FOX61x.
4.1 TDM services overview
TDM based services are provided by specific service units as listed in sec-
tion FOX61x TDM core and service units (on page 10). These service units
are accessing the TDM based bus (PBUS) on the backplane of the FOX61x
for the interconnection of traffic signals. The TDM services allow to intercon-
nect PDH traffic signals from “any unit in any slot”.
SDH traffic signals can be cross connected at the SDH traffic layers VC-4,
VC-3 and VC-12 on the SAMO1 and SAMO2 unit. For a detailed description
of the available SDH cross connections on the SDH unit please refer to
1KHW002476 FOX61x SAMO1 and 1KHW002477 FOX61x SAMO2.
4.2 Voice services
In all voice applications the TDM links transporting the digitised voice and
the signalling are carried via one of the FOX61x P12 transport units:
• LEDE1,
• DATI1,
• SAMO1,
• SAMO2.
4.2.1 Order wire phone application

The implementation of the engineering order wire application using the FXS
interfaces with the FOX61x is shown in Figure 5.
This mode of operation is used in private networks. A PSTN user port is
directly cross connected with another PSTN user port without any exchange
in between. The analogue telephone sets are connected to the LESU1 unit.
The connection between the telephone sets can be extended via a TDM net-
work.
FOX61x
PBUS
FXS LESU1
P12 transport
PSTN FXS unit
TDM
Network
FOX61x
PBUS
FXS LESU1
P12 transport
PSTN FXS unit
Figure 5: Order wire voice service with FOX61x
4.2.2 FXS and FXO voice application

The implementation of the voice service using the FXS and FXO interfaces
with the FOX61x is shown in Figure 6.
The analogue (PSTN) voice from an analogue telephone set (FXO interface)
is transported to the FOX61x in the base-band using the LESU1 unit which
provides the matching FXS interface. The LESU1 unit simulates the func-
tions of a local exchange, supporting out-of-band signalling functions as e.g.
ringing, metering, powering, on/off-hook detection or pulse dialling detection.
The telephone connection to a local exchange (LE) can be extended via a
TDM network.
At the LE side the LEXI1 unit provides the FXO interface which is connected
to the local exchanges FXS interface. The LEXI1 unit simulates the functions
of a telephone set, supporting out-of-band signalling functions as e.g. on/off-
hook, pulse dialling, ringing or metering.
FOX61x
PBUS
FXS LESU1
P12 transport
PSTN FXS unit
TDM
Network
FOX61x
PBUS
Analogue FXO LEXI1
P12 transport
exchange PSTN FXO unit
Figure 6: FXS and FXO voice service with FOX61x
4.2.3 E&M voice application

The implementation of the voice service using E&M interfaces with the
FOX61x is shown in Figure 7.
The analogue (PSTN) voice is transported to the FOX61x in the base-band
using the LEDA1 unit. The signalling is connected to the E&M signalling
interface.
The LEDA1 unit can also be used for order wire applications where a 4-wire
telephone set with inband signalling is connected to the E&M voice port. In
this application the E&M signalling port is not used.
FOX61x
PBUS
E&M LEDA1
E&M interface P12 transport
unit
TDM
Network
FOX61x
PBUS
E&M LEDA1
E&M interface P12 transport
unit
Figure 7: E&M voice service with FOX61x
4.2.4 Mercury CAS multiplexer

The implementation of the voice service using Mercury CAS with the
FOX61x is shown in Figure 8.
The analogue (PSTN) voice from an analogue telephone set (FXO interface)
is transported to the FOX61x in the base-band using the LESU1 unit which
provides the matching FXS interface. The LESU1 unit simulates the func-
tions of a local exchange, supporting out-of-band signalling functions as e.g.
ringing, metering, powering, on/off-hook detection or pulse dialling detection.
The out of band signalling is converted to MCAS signalling by the LESU1

unit.
The telephone connection to an MCAS enabled local exchange (LE) can be
extended via a TDM network.
FOX61x
PBUS
FXS LESU1
P12 transport
PSTN FXS unit
TDM
Network
FOX61x
PBUS
Class 5 E1 LEDE1
Switch with E1 G.703 unit
P12 transport
MCAS
Figure 8: MCAS routing in FOX61x
4.3 TDM data services
TDM-based data services use either an n x 64 kbit/s (P0_nc) circuit or a

2048 kbit/s (P12) circuit. They provide the basis for leased lines or other data
services with legacy CPE equipment.
The subscriber interfaces can be
• E1 (2048 kbit/s, 1 to 31 x 64 kbit/s),
• E0 (64 kbit/s),
• X.24/V.11 (subrates 0.3 to 56 kbit/s, 1 to 31 x 64 kbit/s),
• V.24/V.28 (subrates 0.3 to 56 kbit/s, 1 to 4 x 64 kbit/s),
• V.35 (subrates 0.3 to 56 kbit/s, 1 to 31 x 64 kbit/s),
• RS485 (1 to 31 x 64 kbit/s),
• Data interface CPE via SHDSL (2048 kbit/s, 1 to 31 x 64 kbit/s),
• Teleprotection channel (1 to 2 x 64 kbit/s),
• Binary signal channel(1 to 2 x 64 kbit/s),
• Optical protection channel (1 to 4 x2048 kbit/s,
1 to 8 x (1 to 12 x 64 kbit/s)).
Please note:
The subrate interface bit rates, i.e. below 64 kbit/s, will be available in a
future release.
The TDM data service interfaces are provided by the following units:
• LEDE1,
• LECO1,
• LEDS1,
• DATI1,
• TEPI1,
• OPIC1.
The TDM links transporting the data services are carried via one of the
FOX61x P12 transport units:
• LEDE1,
• DATI1,
• SAMO1,
• SAMO2.
FOX61x
PBUS
Data E1 LEDE1
equipment E1 G.703 unit
Data E0 LECO1
X.24/V.11
V.24/V.28
V.35
Data RS485 LEDS1
equipment TDM data inter-
face unit
P12 transport
Data SHDSL SHDSL

DATI1
equipment modem SHDSL TDM
unit
Protection command
TEPI1
Protection
Teleprotection
relay Binary signals unit
C37.94
OPIC1
Protection
Optical telepro-
relay ABB TPE tection unit
TDM
Network
FOX61x
PBUS
Data E1 LEDE1
Data E0 LECO1
X.24/V.11
V.24/V.28
V.35
Data RS485 LEDS1
face unit
P12 transport
SHDSL
DATI1
Data SHDSL
SHDSL TDM
equipment modem
unit
Protection Protection command TEPI1

relay Teleprotection
Binary signals unit
C37.94
OPIC1
Protection
Optical telepro-
relay ABB TPE tection unit
Figure 9: TDM data access with FOX61x
4.4 Packet data services
4.4.1 Ethernet over PDH data service

PDH-based Ethernet data services use either an n x 64 kbit/s (P0_nc) circuit
or a 2048 kbit/s (P12) circuit for the transport of Ethernet data. This makes it
possible to transport packet based data over the PDH based TDM network.
The Ethernet interfaces for the Ethernet over PDH data service are provided
by the following units:
• LEDS1,
• EPSI1.
The TDM links transporting the Ethernet data services are carried via one of
the FOX61x P12 transport units:
• LEDE1,
• DATI1,
• SAMO1,
• SAMO2.
FOX61x
PBUS
Ethernet
LEDS1
Data
face unit
P12 transport
Data Ethernet
EPSI1
equipment Ethernet and IP
routing unit
TDM
Network
FOX61x
PBUS
LEDS1
Data Ethernet
TDM data inter-
equipment
face unit
P12 transport
EPSI1
Data Ethernet
Ethernet and IP
equipment
routing unit
Figure 10: Ethernet over PDH data access with FOX61x
4.4.2 Ethernet over SDH data service

SDH based Ethernet data services use either a single or concatenated VC-4,
VC-3 or VC-12 circuits for the transport of Ethernet data. This makes it pos-
sible to transport packet based data over the SDH based TDM network.
The Ethernet interfaces for the point-to-point, i.e. unswitched, Ethernet over
SDH data service are provided by the following units:
• SAMO1,
• SAMO2.
The SAMO2 unit supports also the switched Ethernet mode, where it partici-
pates in the FOX61x chassis switch. The Ethernet front ports and the EoS
groups are attached to the chassis switch, so any Ethernet traffic accessing
the FOX61x can be transported over an SDH transport network using the
chassis switch.
SDH traffic is carried via one of the FOX61x SDH units:
• SAMO1,
• SAMO2.
FOX61x
Ethernet
SAMO1
Data
SDH and EoS SDH transport
equipment
transport unit
SAMO2
Data Ethernet
equipment
transport unit
Data Ethernet Packet data Chassis

equipment interfaces switch
TDM
Network
FOX61x
SAMO1
Data Ethernet
equipment SDH and EoS SDH transport
transport unit
SAMO2
Data Ethernet
equipment
transport unit
Data Ethernet Packet data Chassis

equipment interfaces switch
Figure 11: Ethernet over SDH data access with FOX61x
FUNCTIONS
5 Functions
The section Implementation of the TDM cross connect functions (on
page 23) presents the basic models for the PDH and SDH implementation in
the FOX61x.
The TDM connections with their connection termination points (CTP) and the
protection features are described in section TDM connections (on page 27).
The section P12 functions (on page 48) describes all available modes of a
structured or unstructured P12 signal (2048 kbit/s) in the FOX61x and han-
dles the channel associated signalling (CAS) properties of the different CTP
types
The network element synchronization to an internal or external synchroniza-
tion source and the aspects of the PETS and the SETS are covered in the
section Synchronization (on page 56).
5.1 Implementation of the TDM cross connect functions
5.1.1 PDH architecture

The FOX61x network element is a PDH cross connect system. The cross
connect function is implemented as a distributed cross connect system using
the TDM bus (PBUS) in the backplane of the subrack. The PBUS provides a
non-blocking cross connect system with the equivalent capacity of 128 x
2048 kbit/s for traffic signals with and without CAS.
The main characteristics of the PBUS are
• Traffic signal formats
The traffic signal formats of the PBUS support
− P12 (2048 kbit/s) traffic signals. The P12 traffic signals are cross con-
nected transparently (data and timing), thus the P12 signal can be
structured or unstructured. P12 traffic signals are not terminated on
the service units.
− P0_nc (n = 1 … 31) traffic signals. On the PBUS the P0_nc signals
are transported in a 4096 kbit/s signal having a structure with 32 time
slots. Each of these time slots carries the traffic data, signalling data
and other internal communication data.
The P0 (n = 1) traffic signal uses a single time slot. The switching of
signals P0_nc (n = 2 … 31) uses multiple time slots which must
belong to a single P12 signal, but can be arranged in arbitrary order.
The formats are set individually for each termination and connection.
• Cross connections
The PBUS provides digital cross connections for the levels DXC 1/1 and
1/0.
− The 1/1 cross connect of the FOX61x allows the data and timing
transparent switching of structured and unstructured 2048 kbit/s sig-
nals.
− The 1/0 cross connect of the FOX61x allows the switching of n x
64 kbit/s signals with or without signalling, which are all synchronous
to the network element timing (PETS).
FUNCTIONS
All types of cross connections may be bidirectional, unidirectional or uni-

directional point to multipoint. Since the cross connect is distributed on
the PBUS, the cross connections are resistant to single points of failure.
Due to this design, the FOX61x provides a highly reliable and economic
cross connect.
• Physical bus structure
The PBUS consists of 32+1 physical bus lines each with a bitrate of
16‘384 kbit/s. Each PBUS line carries 4 x 2048 kbit/s of traffic signals and
the corresponding signalling information in additional time slots.
32 PBUS lines, equivalent to 128 x 2048 kbit/s, are available for traffic
signals. The remaining bus line is used for diagnostics and other system
purposes and is not available for traffic signals (payload).
The 32+1 PBUS lines are available in all 21 slots of the FOX615 subrack
and in all 8 slots of the FOX612.
FOX61x
PBUS
12 3 33
Pro- Pro-
Traffic Signal Service Core
cess- cess-
Unit Unit
ing ing
Pro-
Traffic Signal Service
cess-
Unit
ing
Figure 12: PBUS access
• Access
The architecture of the PBUS provides linear bus access. Any PBUS unit
can read all the information from the PBUS but can write to one (or more)
assigned PBUS line(s) only.
The number of PBUS lines accessed by the different PBUS units is as
follows:
Table 2: PBUS line write access per PBUS unit

Unit Traffic capacity PBUS lines
CESM1 8 P12 (DCN) 0…2
LESU1 16 P0 (PSTN FXS) 0…1
LEDE1 8 P12 (E1) 0…2
DATI1 8 P12 (SHDSL)a 0…2
SAMO1 67 P12 (SDH) 0 … 17
SAMO2 64 P12 (SDH) 0 … 16
LEDA1 8 P0 (PSTN E&M) plus 32 P0 (conference participants) 0 … 1
FUNCTIONS
Table 2: PBUS line write access per PBUS unit (continued)

Unit Traffic capacity PBUS lines
LEDS1 4 x 31 P0 (data interface) plus 1 x 31 P0 (Ethernet inter- 0 … 8
face) plus 848 P0 (conference participants)
LEXI1 12 P0 (PSTN FXO) 0…1
LECO1 8 P0 (data) 0…1
EPSI1 16 x P12 (Ethernet) 0…4
TEPI1 2 x P0 (teleprotection channel) 0…1
plus 2 x P0 (binary signal channel)
OPIC1 4 x P12 (optical protection channel) 0…1
plus 2 x P0 (binary signal channel)
a. 64 P12 will be available in a future release

As specified above a PBUS line has a capacity of 4 x 2048 kbit/s. A TDM
service unit with PBUS access always occupies the PBUS in steps of 1
PBUS line, i.e. 4 x 2048 kbit/s, independently of whether the whole
capacity of the PBUS line (4 x 2048 kbit/s) or just a single P0 time slot
(64 kbit/s) is required for the traffic signal(s). As soon as the first time slot
is cross connected, the complete capacity of the PBUS line is occupied,
thus reducing the remaining capacity by 4 x 2048 kbit/s.
This limits the number of physical PBUS accesses to 32.
Please note:
Only PBUS access circuits with configured PDH traffic connections occupy
PBUS lines.
• Timing
The PBUS timing is controlled by the PETS (plesiochronous equipment
timing source) located on the CESM1 unit. The PETS can be synchro-
nized to incoming TDM traffic and timing signals or it can be free running.
Refer to section Synchronization (on page 56).
The PETS timing is distributed via the PBUS to all TDM units of the
FOX61x.
In synchronous applications, e.g. with P0_nc traffic signals, the traffic sig-
nals must be synchronized to the PETS. Otherwise bit and frame slips
would occur.
In plesiochronous applications, e.g. P12 in transparent mode, the traffic
signals are not synchronized to the PETS.
PDH connections using the PBUS are all configured using the FOX61x ele-
ment manager (EM) tool FOXCST. The EM only allows the connection of
matching signal types.
FUNCTIONS
5.1.2 SDH architecture

The FOX61x offers on the SDH service units SAMO1 and SAMO2 an SDH
subsystem with SDH front interfaces and cross connect systems on the AU-
4, TU-3 and TU-12 layers:
Table 3: SDH subsystem on the SDH service units

SAMO1 SAMO2
SDH front interfaces 2 x STM-4 or STM-1, 2 x STM-16 or STM-4,
2 x STM-1 2 x STM-4 or STM-1 a
AU-4 cross connect 18 x 18 VC-4 128 x 128 VC-4
TU-3 cross connect 33 x 33 VC-3 48 x 48 VC-3
TU-12 cross connect 671 x 671 VC-12 1324 x 1324 VC-12
PBUS access capacity 67 x P12 32 x P12 b
a. The SAMO2 can access the 4 SDH front interfaces of a protecting SAMO2 unit.
b. 64 P12 will be available in a future release.
The cross connect functions are all implemented on the SDH service units,
allowing the unrestricted cross connections of the SDH traffic signals on a
single SDH service unit.
Please note:
VC-4, VC-3 or VC-12 signals cannot be cross connected between any two
SDH service units.
→ Cross connection of VC-4, VC-3 and VC-12 signals is only available
on a single SDH service unit.
The SDH service units can be configured to be an SDH add-drop multiplexer
(ADM) or an SDH terminal multiplexer (TM).
For a detailed description of the available SDH cross connections on the
SDH service units please refer to 1KHW002476 FOX61x SAMO1 and
r1KHW002477 FOX61x SAMO2.
SDH connections on the SAMO1 and SAMO2 unit are all configured using
the FOX61x element manager (EM) tool FOXCST. The EM only allows the
connection of matching signal types.
FUNCTIONS
5.2 TDM connections
5.2.1 Connection termination points

5.2.1.1 CTP properties
In the FOX61x a TDM connection is created between two connection termi-

nation points (CTP), where the starting point is the A-End CTP and the end-
ing point is the Z-End CTP. CTPs are managed objects (MO) on the TDM
service units.
A CTP can have no connection, one connection or several connections. A
CTP has the following connection related properties:
• Directionality of the connection:
− bidirectional,
− unidirectional.
• Local role of the CTP:
− A-End working,
− A-End protecting,
− Z-End.
• Protection of the Z-End CTP:
− unprotected,
− protected.
FUNCTIONS
Bidirectional connection, unprotected Unidirectional connection , unprotected
bidirectional unidirectional
bidirectional Z-End unidirectional Z-End
A-End working unprotected A-End working unprotected
CTP CTP CTP CTP
Bidirectional connection, protected Unidirectional connection, protected
bidirectional bidirectional unidirectional unidirectional

A-End working Z-End A-End working Z-End
protected protected
CTP CTP
CTP CTP
CTP CTP
bidirectional unidirectional
A-End protecting A-End protecting
Bidirectional connection, unprotected Bidirectional connection, unprotected

Unidirectional connection, unprotected Unidirectional connection , unprotected
bidirectional bidirectional
bidirectional Z-End bidirectional Z-End
A-End working unprotected A-End working unprotected
CTP CTP CTP CTP
CTP CTP unidirectional

A-End working
unidirectional unidirectional unidirectional
A-End working Z-End Z-End
unprotected unprotected
Figure 13: CTP roles in a connection
The configuration of additional connections on a CTP depends on the actu-

ally configured connection(s) and the role the CTP is acting in. A CTP can
always be used as A-End working or A-End protecting unidirectional CTP,
irrespective of any already existing connections on this CTP. The protection
configuration is irrelevant for the availability of additional connections.
Table 4: Additional connections on a CTP with already existing

connections
Existing connection For an additional con- A-End role summary Z-End role summary
Local role Directionality nection, the CTP can be
used as
A-End bidirectional A-End unidirectional bidirectional none
unidirectional A-End bidirectional bidirectional none
A-End unidirectional unidirectional none
Z-End bidirectional unidirectional bidirectional
Z-End unidirectional unidirectional unidirectional
Z-End bidirectional A-End unidirectional unidirectional bidirectional
unidirectional A-End unidirectional unidirectional unidirectional
FUNCTIONS
The list with all the configured connections and the local roles of a CTP is
available in the FOXCST at the Configuration - CTP dialogue of the port or
channel, e.g. AP: /unit-x/port-y, Configuration - CTP.
A CTP has the following traffic signal related properties:
• Layer rate:
The layer rate of a CTP can be VC4, VC3, VC12, P12 or P0_nc. The
layer rate can be fixed according to the service unit or MO type or it can
be predefined by the MO configuration.
The CTPs used as A-End and Z-End of a connection must have the
same layer rate.
• Number of time slots n:
The number of time slots of a CTP is available for the P0_nc layer rate
only. It indicates the traffic signal bandwidth and is in the range from 1 to
32 time slots (64 to 2048 kbit/s). The number of time slots can be fixed
according to the service unit or MO type or it can be configurable in the
CTP configuration. Configurable CTPs are called “channels”, refer to sec-
tion Dynamic CTP (on page 33).
The CTPs used as A-End and Z-End of a connection must have the
same number of time slots.
• time slots:
For CTPs with a P0_nc layer rate and belonging to a structured P12
transport signal, the time slots parameter shows which time slots in the
structured P12 signal are assigned to the CTP.
Service units which have no P12 transport signals, e.g. the POTS line-
card unit LESU1, the time slots property is empty.
• List of connections:
The list of connections shows all connections assigned to the CTP with
the connection related properties
− connection index,
− local CTP role (A-End or Z-End),
− remote CTP (MO address),
− remote CTP role (A-End or Z-End), and
− directionality (bidirectional or unidirectional).
Please note:
A Z-End CTP of a protected connection shows two connection entries, one
to the A-End working CTP and one to the A-End protecting CTP.
Please note:
A unidirectional connection on a CTP made to itself, i.e. acting as a loop, is
shown as a bidirectional connection in the CTP configuration dialogue.
→ A CTP connection is shown as bidirectional when it is sending and
receiving irrespective if the connected CTPs are different or the same.
• Z-End configuration:
− Revertive protection switching (true or false):
The protection operation type is configurable to be revertive or non-
revertive.
In the revertive mode the selector at the Z-End CTP selects the A-End
working CTP when the signal quality of the A-End working CTP is
equal or better than the signal quality of the A-End protecting CTP.
In the non-revertive mode the selector at the Z-End CTP performs a
switching action only when the signal quality of the currently selected
FUNCTIONS
A-End CTP is worse than the signal quality of the currently not
selected A-End CTP.
− CAS AIS supervision (true or false):
The CAS AIS supervision at a Z-End CTP is available for the P0_nc
layer rate only. CAS AIS supervision can be enabled or disabled.
CAS AIS supervision is used for the 1+1 linear trail protection (LTP) at
the P0_nc layer rate. For further information please refer to section
Linear trail protection LTP (on page 39)
− Switch-over logging (true or false):
The logging of switch-over events at a Z-End CTP can be enabled or
disabled.
Switch-over events can be stored in the event logbook and are used in
the syslog logging.
CTPs can be static or dynamic, refer to sections Static CTP (on page 30)
and Dynamic CTP (on page 33).
5.2.1.2 Static CTP
Static CTPs have fixed “layer rate” and “number of time slots” properties.
Static CTPs are available on the following units:
• CESM1,
• LESU1,
• LEXI1,
• LECO1,
• LEDA1,
• LEDS1,
• SAMO1,
• SAMO2,
• EPSI1,
• TEPI1,
• OPIC1.
The CTPs used for the DCN application, and physically implemented on the
CESM1 unit, are created on the “Management Interfaces” tab at the AP:/
managementNetwork/tdmInterfaces, Configuration - TDM, when a PPP
Interface is created. The CTP is deleted when the interface is deleted.
On the LESU1, LEXI1, TEPI1, OPIC1 and LECO1 units the CTPs are cre-
ated when the TDM service unit is assigned in the FOX61x and deleted
when the unit is unassigned.
On the LEDA1 unit the port CTPs are created when the unit is assigned in
the FOX61x and deleted when the unit is unassigned. The conference partic-
ipant CTPs are created when the conference is created and deleted when
the conference is deleted. All CTPs are deleted when the unit is unassigned.
On the LEDS1 unit the port CTPs are created when the TDM service unit is
assigned in the FOX61x and modified with the configuration of the Interface
Rate. The CTPs are deleted when the unit is unassigned. The conference
participant CTPs are created when the conference is created and deleted
when the conference is deleted. All CTPs are deleted when the unit is unas-
signed.
On the SAMO1 and SAMO2 unit static CTPs are available at different
access points:
FUNCTIONS
− the AU-4 CTPs of the STM-16, STM-4 and STM-1 ports are created
when the unit is assigned in the FOX61x and modified when the port
mode configuration is changed. The AU-4 CTPs are deleted when the
unit is unassigned.
− The PDH VC-12 CTPs are created when the unit is assigned in the
FOX61x. The PDH VC-12 CTPs are deleted when the unit is unas-
signed.
− The EoS VC-4, VC-3 and VC-12 CTPs are created when the EoS
group is created and deleted when the EoS group is deleted.
− The CTPs of the internal VC-4 resources are created when the VC-4
is created and deleted when the internal VC-4 is deleted.
− The CTPs of the internal VC-3 and VC-12 resources are created when
the TUG-3 structure of the corresponding internal VC-4 is configured
or modified and deleted when the internal VC-4 is deleted.
− The DCC CTPs for the RS or MS are created when the DCC type of
the SDH port configuration is set to RSOH or MSOH or both. The
DCC CTPs are deleted when the DCC type of the SDH port configura-
tion is set to None.
− All CTPs are deleted when the unit is unassigned.
On the EPSI1 unit the TDM interface CTPs are created when the MAC
HDLC, PPP or MLPPP interface is created and deleted when the TDM inter-
face is deleted. All CTPs are deleted when the unit is unassigned. TDM
interfaces for the MAC HDLC, PPP and MLPPP channels can be on the P12
or P0_nc layer. In the EPSI1 8x2 Mbit/s mode a P12 interface has the
“Transparent” termination mode, the P0_nc signal can be configured from
“n=1 (64 kbit/s) to n=32 (2048 kbit/s). In the EPSI1 16x2 Mbit/s mode a P12
interface has the “Clock Master” termination mode, the P0_nc signal can be
configured from “n=2 (128 kbit/s) to n=32 (2048 kbit/s), i.e. n must be even.
Please note:
When a static CTP is deleted, all connections assigned to this CTP are
deleted also.
Static CTPs have the following properties:
Table 5: Static CTPs

Unit MO type CTP MO address Layer rate Number of time slots
ne PPP interface ne/managementNetwork/ P0_nc 1 … 32
tdmInterfaces/ppp-x
ne PPP interface ne/managementNetwork/ P12 n.a., P12 termination mode:
tdmInterfaces/ppp-x - transparent
LESU1 PSTN port (FXS) unit-x/port-y P0_nc 1
LEXI1 PSTN port (FXO) unit-x/port-y P0_nc 1
LECO1 E0 port unit-x/port-y P0_nc 1
LEDA1 PSTN port (E&M) unit-x/port-y P0_nc 1
LEDA1 Conference participant unit-x/conf-y/part-z P0_nc 1
LEDS1 Data port unit-x/port-y P0_nc 1 (subrate) a
1 … 31 (nx64 kbit/s)
LEDS1 Conference participant, unit-x/conf-y/part-z P0_nc 1 (subrate) a
1 … 31 (nx64 kbit/s)
SAMO1 STM-4/STM-1 port unit-x/port-y/j-z VC4 n.a.
SAMO1 PDH VC-12 unit-x/pdh/vc12-y VC12 n.a.
FUNCTIONS
Table 5: Static CTPs (continued)

SAMO1 EoS VC-4 unit-x/port-y/eos/vc4-z VC4 n.a.
SAMO1 Internal VC-4 resource unit-x/vc4/vc4-y VC4 n.a.
SAMO1 Internal VC-3 resource unit-x/vc4/vc4-y/klm-z00 VC3 n.a.
SAMO1 Internal VC-12 resource unit-x/vc4/vc4-y/klm-zab VC12 n.a.
SAMO1 DCC in the MSOH unit-x/port-y/dcc P0_nc 9
SAMO1 DCC in the RSOH unit-x/port-y/dcc P0_nc 3
SAMO2 STM-16/STM-4/STM-1 port unit-x/sdh/sdh-y/j-z VC4 n.a.
SAMO2 PDH VC-12 unit-x/pdh/vc12-y VC12 n.a.
SAMO2 EoS VC-4 unit-x/eos/eos-y/eos/vc4-z VC4 n.a.
SAMO2 Internal VC-4 resource unit-x/vc4/vc4-y VC4 n.a.
SAMO2 Internal VC-3 resource unit-x/vc4/vc4-y/klm-z00 VC3 n.a.
SAMO2 Internal VC-12 resource unit-x/vc4/vc4-y/klm-zab VC12 n.a.
SAMO2 DCC in the MSOH unit-x/sdh/sdh-y/dccm P0_nc 9
SAMO2 DCC in the RSOH unit-x/sdh/sdh-y/dccr P0_nc 3
EPSI1 MAC HDLC interface unit-x/tdmInterfaces/ P0_nc 1 … 32 (8x2 Mbit/s mode),
machdlc-y 2, 4, … 32 (16x2 Mbit/s mode)
EPSI1 MAC HDLC interface unit-x/tdmInterfaces/ P12 n.a., P12 termination mode:
machdlc-y - transparent (8x2 Mbit/s mode),
- clock master (16x2 Mbit/s
mode)
EPSI1 PPP interface unit-x/tdmInterfaces/ppp-y P0_nc 1 … 32 (8x2 Mbit/s mode),
2, 4, … 32 (16x2 Mbit/s mode)
EPSI1 PPP interface unit-x/tdmInterfaces/ppp-y P12 n.a., P12 termination mode:
- transparent (8x2 Mbit/s mode),
mode)
EPSI1 MLPPP interface unit-x/tdmInterfaces/ P0_nc 1 … 32 (8x2 Mbit/s mode),
mlppp-y/member-z 2, 4, … 32 (16x2 Mbit/s mode)
EPSI1 MLPPP interface unit-x/tdmInterfaces/ P12 n.a., P12 termination mode:
mlppp-y/member-z - transparent (8x2 Mbit/s mode),
mode)
TEPI1 Teleprotection channel unit-x/applications/telepro- P0_nc 1
tectionsignalling/chan-y
TEPI1 Binary signal channel unit-x/applications/binary- P0_nc 1
signaltransmission/chan-y
OPIC1 Optical protection channel unit-x/chan-y P12 n.a.
OPIC1 Optical protection channel unit-x/chan-y P0_n 1...12
a. The subrate interface bit rates, i.e. below 64 kbit/s, will be available in a future re-
lease.
FUNCTIONS
5.2.1.3 Dynamic CTP
Dynamic CTPs can be created and deleted via the management interface by
creating and deleting a “channel” MO, called “chan-z”. The CTP is located as
a managed object on the channels.
<ap> <ap >

unit- x unit-x
1 ...8 <ap > 1...8 <ap >

port-y port-y
<mf>
Configuration 1...31 <ap >
chan -z
1
Create Channel... <attribute> the AP „chan-z“ <mf>

configure properties Channels is created Configuration
<attribute>
CTP
Figure 14: Example for the creation of a channel on a port (LEDE1)
The CTPs properties are configurable. Dynamic CTPs are available on the
following units:
• LEDE1,
• DATI1,
• SAMO1,
• SAMO2.
On the LEDE1 unit the E1 port channels are created on the AP: /unit-x/port-
y, Configuration - Channels.
On the DATI1 unit the SHDSL CPE channels are created on the AP: /unit-x/
logports/logport-y/cpe, Configuration - Channels. The SHDSL trunk channels
are created on the AP: /unit-x/logports/logport-y/trunk, Configuration - Chan-
nels.
On the user interface types X.21, V.35 and V.36 of the CPEs connected to a
DATI1 unit, the channels with the CTP are created when the SHDSL span is
created and deleted when the SHDSL span is deleted. Only one channel is
available per CPE. Per default the user data rate is 2048 kbit/s and therefore
the channel layer rate is P12. When reconfiguring the CPE to a user data
rate < 2048 kbit/s the channel layer rate is automatically changed to P0_nc
with the number of time slots corresponding to the user data rate.
On the SAMO1 and SAMO2 units the PDH P12 channels are created on the
AP: /unit-x/pdh/vc12-y/p12, Configuration - Channels.
The number of channels that can be created on a E1 port, CPE, Trunk or
PDH P12 signal is limited by the bandwidth of the P12 signal and the band-
widths of the created channels; e.g. a PCM signal without CAS has a capac-
ity for user traffic of 31 time slots which can be used for up to 31 channels
with a bandwidth of 1 time slot (64 kbit/s) each.
A channel with more than one time slot typically occupies consecutive time
slots. Note that it is possible to setup a channel from any time slots belong-
ing to a P12 signal, e.g. a channel with four time slots can be setup with time
slots 1, 6, 30 and 31.
FUNCTIONS
Please note:
When a dynamic CTP is deleted, all connections assigned to this CTP are
deleted also.
Dynamic CTPs have the following properties:
Table 6: Dynamic CTPs

LEDE1 E1 port / Channel unit-x/port-y/chan-z P0_nc 1 … 31
LEDE1 E1 port / Channel unit-x/port-y/chan-z P12 n.a.
DATI1 SHDSL trunk unit-x/logports/logport-y/trunk/chan-a P0_nc 1 … 32 a
DATI1 SHDSL trunk unit-x/logports/logport-y/trunk/chan-a P12 n.a.
DATI1 b SHDSL CPE / Channel unit-x/logports/logport-y/cpe/chan-a P0_nc 1 … 31 c
DATI1 b SHDSL CPE / Channel unit-x/logports/logport-y/cpe/chan-a P12 n.a.
SAMO1 PDH P12 / Channel unit-x/pdh/vc12-y/p12/chan-z P0_nc 1 … 31
SAMO1 PDH P12 / Channel unit-x/pdh/vc12-y/p12/chan-z P12 n.a.
SAMO2 PDH P12 / Channel unit-x/pdh/vc12-y/p12/chan-z P0_nc 1 … 31
SAMO2 PDH P12 / Channel unit-x/pdh/vc12-y/p12/chan-z P12 n.a.
a. When transporting the timing over the SHDSL payload (“Clock Over Payload” =
true) the time slot 0 carries framing data instead of user data.
b. On SHDSL CPEs with user interface type X.21, V.35 or V.36, the number of chan-
nels is fixed to 1 and is automatically created with the creation of the SHDSL span.
c. On SHDSL CPEs with user interface type X.21, V.35 or V.36, the number of time
slots corresponds to the configured CPE user data rate.
The layer rate property is predefined by the configuration of the P12 termina-
tion mode. In the “V5 uplink” termination mode also the number of time slots
is predefined.
Table 7: P12 termination modes and layer rates

P12 termination mode Layer rate Number of time slots
Transparent P12 n.a.
Clock master P12 n.a.
PCM30, PCM30C P0_nc 1 … 30
PCM31, PCM31C P0_nc 1 … 31
V5 uplink, V5 uplink NCI P0_nc 31
PCMnn, PCMnnC P0_nc 1 … 31 (64 … 1984 kbit/s)
Structured P0_nc 1 … 32 (64 … 2048 kbit/s) a
Structured With CAS P0_nc 16 … 31 (1024 … 1984 kbit/s) a
G.704 Customized with CAS P0_nc 15 … 30 (1024 … 1984 kbit/s)
G.704 Customized without CAS P0_nc 1 … 31 (64 … 1984 kbit/s)
a. When transporting the timing over the SHDSL payload (“Clock Over Payload” =
true) the time slot 0 carries framing data instead of user data.
For more information about P12 termination modes refer to section P12
functions (on page 48).
FUNCTIONS
Please note:
Changing the P12 termination mode results in most cases in incompatible
layer rates or number of time slots. The channel with its CTP and the
assigned connections are deleted automatically and must be newly created.
Only the following P12 termination modes are compatible, i.e. can be inter-
changed without deletion of the channel MO.
Table 8: Compatible P12 termination modes

P12 termination modes
Transparent compatible with Clock Master
PCM30 compatible with PCM30C
PCM31 compatible with PCM31C
PCM30, PCM30C compatible with G.704 Customized, 1984 kbit/s, with CAS
PCM31, PCM31C compatible with PCMnn, PCMnnC, 1984 kbit/s
PCM31, PCM31C compatible with G.704 Customized, 1984 kbit/s, without CAS

The data format on the PBUS of the “Clock Master” mode traffic is not com-
patible with the data format of the “Transparent” mode traffic.
→ An E1 port, SHDSL CPE, SHDSL Trunk or PDH P12 signal configured
for the P12 “Clock Master” mode must be connected to an E1 port,
SHDSL CPE, SHDSL Trunk or PDH P12 signal in the “Clock Master”
P12 mode only.
5.2.2 Protection
The SDH and PDH traffic in the FOX61x network element can be 1+1 pro-
tected on different layers. FOX61x supports protection switching according
to ITU-T G.841, §8:
• SNCP/I: Inherently monitored subnetwork connection protection.
• SNCP/N: Non-intrusively monitored subnetwork connection protection.
• LTP: Linear trail protection.
Table 9: Protection switching features

Feature SNCP/I SNCP/N LTP
Switching conditions derived from defects of the derived from defects of the derived from defects of the
(SF, SD) server layer server layer and from defects server layer and from defects
of the monitoring function of of the termination function of
the own layer the own layer.
Architecture type 1+1 1+1 1+1
Switching type unidirectional unidirectional unidirectional
Operation type revertive or non-revertive revertive or non-revertive revertive or non-revertive
Protocol no no no
The protection mode of a CTP (e.g. SNCP, LTP) is given by the capabilities
of the relevant unit or application respectively. The protection mode may be
fixed or configurable by the application (implicit or explicit configuration).
Please refer to the corresponding unit user manuals.
FUNCTIONS
In addition the SAMO1 and SAMO2 units support 1+1 multiplex section pro-
tection (MSP). Pease refer to FOX61x SAMO1 and refer to FOX61x SAMO2
for further information.
Please note:
The availability of protection parameters as
− holdoff time,
− guard time,
− wait to restore time,
− operation type revertive or non-revertive,
− CAS AIS supervision,
− switching type unidirectional or bidirectional,
is dependent of the unit and application.
→ Please refer to the relevant user manuals.
5.2.2.1 Subnetwork connection protection SNCP/I
SNCP/I is supported for the following traffic signal types:

• VC-4 unterminated,
• P12 unstructured (transparent mode),
• P0_nc without CAS AIS supervision.
Protection switching action can be driven by two different request types:
• Traffic signal requests according to the Table 9:
− SF = Signal Fail
− SD = Signal Degraded
• External command requests. Please refer to section External requests
(on page 47) for a description of the external commands.
Table 10: Traffic signal requests for SNCP/I

Failure Type VC-4 VC-3 VC-12 P12 P0_nc
AU-4 AIS SF X - - - -
AU-4 Loss Of Pointer SF X - - - -
VC-4 Unequipped SF X - - - -
VC-4 Degraded Signal SD X - - - -
TU-3 AIS SF - X - - -
TU-3 Loss Of Pointer SF - X - - -
VC-3 Unequipped SF - X - - -
VC-3 Degraded Signal SD - X - - -
TU-12 AIS SF - - X - -
TU-12 Loss Of Pointer SF - - X - -
VC-12 Unequipped SF - - X - -
VC-12 Degraded Signal SD - - X - -
E12 Loss Of Signal SF - - - X X a, b, c
E12 BER > 1E-3 SF - - - X X
P12 AIS SF - - - X X a, b, c
FUNCTIONS
Table 10: Traffic signal requests for SNCP/I (continued)

Failure Type VC-4 VC-3 VC-12 P12 P0_nc
P12 Loss Of Frame SF - - - - X a, b, c
P12 Loss of CRC4 MF d SF - - - - Xa
P12 Remote Loss of CRC4 MF - - - - - -
d
P12 Trace Identifier Mismatch SF - - - - Xb
P12 Remote Defect Indication - - - - - -
P12 Loss of CAS MF d SF - - - - Xc
P12 Remote Loss of CAS MF d SF - - - - X
P0 CAS AIS - - - - - -
E12 BER > 1E-5 SD - - - X X
P12 Degraded Signal SD - - - - X
a. Activates the P12 Remote Non CRC4 Interworking.

b. Activates the P12 Remote Defect Indication.
c. Activates the P12 Remote Loss of CAS MF.
d. Depending on the settings for CRC4, CAS and TTI supervision.
Please note:
Receiving a P12 Remote Loss of CAS MF signal replaces the received CAS
with a CAS AIS.
Please note:
The P0_nc protection switching of a traffic signal using CAS supervision per-
forms bidirectional protection switching.
On the P0_nc layer FOX61x supports a specific bidirectional protection
switching mode. Bidirectional SNCP/I ensures that both directions of the
transmission path use the same sections. This might be important for time
critical applications. It is also required to support the shared protection ring
(SPR) application.
Please note:
The bidirectional protection switching performs a switchover of all P0_nc sig-
nals (channels) contained in a failed P12 signal.
Please note:
In the shared protection ring application the working and the protecting paths
must be mapped to the same P12 signal.
→ The maximum bandwidth is limited to 15 x 64 kbit/s.
With bidirectional protection switching the following switching criteria and
remote indications to the far end apply:
Table 11: Traffic signal requests for bidirectional SNCP/I

Failure Type P0_nc Remote indications
E12 Loss Of Signal SF X P12 Remote Defect Indication
P12 Remote Non CRC4 Interworking a
P12 Remote Loss of CAS MF a
FUNCTIONS
Table 11: Traffic signal requests for bidirectional SNCP/I (continued)

E12 BER > 1E-3 SF X P12 Remote Defect Indication
P12 AIS SF X P12 Remote Defect Indication
P12 Loss Of Frame SF X P12 Remote Defect Indication
P12 Loss of CRC4 MF a - - P12 Remote Non CRC4 Interworking a
P12 Remote Loss of CRC4 MF - - -
P12 Trace Identifier Mismatch a SF X P12 Remote Defect Indication
P12 Remote Defect Indication SF X -
a
P12 Loss of CAS MF SF X P12 Remote Loss of CAS MF a
P12 Remote Loss of CAS MF a SF X -
P0 CAS AIS - - -
E12 BER > 1E-5 - - -
P12 Degraded Signal SD X P12 Remote Defect Indication
a. Depending on the settings for CRC4, CAS and TTI supervision.
5.2.2.2 Subnetwork connection protection SNCP/N
SNCP/N is supported for the following traffic signal types:

• VC-4 terminated,
• P12 structured (monitored mode, future release).
Table 12: Traffic signal requests for SNCP/N

Failure Type VC-4 VC-3 VC-12 P12
AU-4 AIS SF X - - -
AU-4 Loss Of Pointer SF X - - -
VC-4 Unequipped SF X - - -
VC-4 TTI Mismatch SF X - - -
VC-4 Excessive Bit Error Rate tbd SF X - - -
VC-4 Degraded Signal SD X - - -
TU-3 AIS SF - X - -
FUNCTIONS
Table 12: Traffic signal requests for SNCP/N (continued)

Failure Type VC-4 VC-3 VC-12 P12
TU-3 Loss Of Pointer SF - X - -
VC-3 Unequipped SF - X - -
VC-3 TTI Mismatch SF - X - -
VC-3 Excessive Bit Error Rate tbd SF - X - -
VC-3 Degraded Signal SD - X - -
TU-12 AIS SF - - X -
TU-12 Loss Of Pointer SF - - X -
VC-12 Unequipped SF - - X -
VC-12 TTI Mismatch SF - - X -
VC-12 Excessive Bit Error Rate tbd SF - - X -
VC-12 Degraded Signal SD - - X -
E12 Loss Of Signal SF - - - X
E12 BER > 1E-3 SF - - - X
P12 AIS SF - - - X
P12 Loss Of Frame SF - - - X
P12 Loss of CRC4 MF a SF - - - X
P12 Remote Loss of CRC4 MF - - - - -
P12 Trace Identifier Mismatch a SF - - - X
P12 Remote Defect Indication - - - - -
E12 BER > 1E-5 SD - - - X
P12 Degraded Signal SD - - - X
a. Depending on the settings for CRC4, CAS and TTI supervision.
On the VC-12 layer of selected access points the FOX61x supports a spe-
cific bidirectional protection switching mode. Bidirectional SNCP/N ensures
that both directions of the transmission path use the same sections. This
might be important for time critical applications.
The bidirectional protection mode provides the following functions:
• The FOX61x selects the received signal from one of the two VCs and
switches to the other VC if this signal fails. The selector state is signalled
to the remote termination function which switches its selector accordingly.
• 1+1 bidirectional protection switching uses a proprietary protocol trans-
ported in the RFI bit of the V5[4] byte.
• The operation type can be configured to revertive or non-revertive.
5.2.2.3 Linear trail protection LTP
LTP is supported for the following traffic signal types:

• P0_nc with CAS AIS supervision.
FUNCTIONS
Table 13: Traffic signal requests for LTP

E12 Loss Of Signal SF X P12 Remote Defect Indication
P12 Remote Loss of CAS MF
E12 BER > 1E-3 SF X -
P12 AIS SF X P12 Remote Defect Indication
P12 Loss Of Frame SF X P12 Remote Defect Indication
P12 Loss of CRC4 MF a SF X P12 Remote Non CRC4 Interworking a
P12 Remote Loss of CRC4 MF - - -
a
P12 Trace Identifier Mismatch SF X P12 Remote Defect Indication
P12 Remote Defect Indication - - -
P12 Loss of CAS MF SF X P12 Remote Loss of CAS MF
P12 Remote Loss of CAS MF SF X -
P0 CAS AIS SF X -
E12 BER > 1E-5 SD X -
P12 Degraded Signal SD X -
a. Depending on the settings for CRC4 and TTI supervision.
Please note:
Receiving a P12 Remote Loss of CAS MF signal replaces the received CAS
with a CAS AIS.
Please note:
The P0_nc protection switching of a traffic signal using CAS supervision per-
forms bidirectional protection switching.
Please note:
In a TDM network with connected traffic signals at the P0_nc layer the pro-
tection switching type depends on the CAS AIS supervision as switching cri-
terion:
• With CAS AIS supervision:
The protection switching type is P0_nc linear trail protection (LTP).
• Without CAS AIS supervision:
The protection switching type is P0_nc subnetwork connection protection
(SNCP/I).

A protected P0_nc connection not using CAS AIS supervision will not per-
form the required switching action, if a failure occurs at an intermediate net-
work element that terminates the P0_nc server layer.
→ Refer to the figure below.
FUNCTIONS
Alarm Monitor: Consequent Action: Alarm Monitor: Consequent Action:

P12: LOS P0_nc: AIS P12: no alarm No switchover
P0_nc: CAS AIS P0_nc: no alarm
Cross Connection:
P-12 TDM P-12 Layer: P0_nc P-12 TDM P-12
P12 TS0: regenerated
Figure 15: P0_nc protection switching without CAS AIS supervision
When CAS AIS supervision is enabled, the required switching action will be
performed.
Alarm Monitor: Consequent Action: Alarm Monitor: Consequent Action:

P12: LOS P0_nc: AIS P12: no alarm Protection
P0_nc: CAS AIS P0_nc: CAS AIS switchover
Cross Connection:
P-12 TDM P-12 Layer: P0_nc P-12 TDM P-12
P12 TS0: regenerated
Figure 16: P0_nc protection switching with CAS AIS supervision
5.2.2.4 Shared protection ring SPR
The principle of shared protection ring (SPR) provides an economical means

to protect a linear network against single failure events. The linear network
must be closed to a ring with a connection on the protecting path from the
last network element to the first network element.
The working and the protecting paths are both transported in the same P12
signal. It is therefore possible to have protection in a linear network with one
single P12 signal whereas the SNC or linear trail protection requires inde-
pendent P12 paths between any two network elements.
Please note:
The transport of the working and the protecting path on the same P12 signal
limits the available bandwidth of a path to 15x64 = 960 kbit/s.
The proposed implementation is based on the generic FOX61x feature of
subnetwork connection protection SNCP/I.
In conjunction with P2MP or MP2MP networks P0_nc SNCP/I is applied.
This protection mechanism offers revertive 1+1 protection switching on P0
level with the switching criterion SF (Signal Failure) derived from the underly-
ing server network layer terminations.
Please note:
The shared protection ring (SPR) application requires the protection type to
be revertive.
In order to be protected against unidirectional failures the bidirectional pro-
tection switching must be enabled. This feature is available on the following
P12 transport units:
• LEDE1,
• SAMO1,
FUNCTIONS
• SAMO2.
Under normal operating conditions, the working path is active and the pro-
tecting path is standby by default. The protecting path provides a closed bidi-
rectional ring.

In a closed ring the content of the circular traffic and signalling is not defined.
This has the consequence that the signalling in the shared protection ring
when it is not used for user traffic can be an AIS, which would result in a cor-
responding alarm.
→ To prevent the alarm generation the CAS AIS supervision must be dis-
abled in the tributary units port and conference participant CTP config-
uration.
For additional information on the FOX61x protection mechanism and the
E12/P12 traffic signal layer, please refer to sections Subnetwork connection
protection SNCP/I (on page 36), Subnetwork connection protection SNCP/N
(on page 38) and Linear trail protection LTP (on page 39).
FUNCTIONS
to to to
to SPR Master slave master
Intermediate slave slave
TDM TDM
Network Network
4 3
1
Σ 1 2
FOX61x 1 tributary FOX61x 2 tributary

Shared interface interface
protection
ring tributary
interface
TDM
Network
to to to
to SPR Tail end slave master slave Intermediate slave master
TDM
Network
3 2 3
Σ 1 2
Σ 1

interface interface
P12 transport working
tributary
P12 transport protecting interface
Conference on Working
tributary unit connection
Protecting
Tributary unit
connection
Figure 17: Multipoint application example with SPR
In case of a line break or a failure in a NE the adjacent NEs reroute the pro-
tected traffic to the protecting path.
FUNCTIONS
to to to
to SPR Master slave master
Intermediate slave slave
TDM TDM
Network Network
4 3
1
Σ 1 2

Shared interface interface
protection
ring tributary
interface
TDM
Network
to to to
to SPR Tail end slave master slave Intermediate slave master
TDM
Network
3 2 3
Σ 1 2
Σ 1
FOX61x 4 FOX61x 3
tributary tributary
interface interface
P12 transport working
tributary
P12 transport protecting interface
Conference on Working
tributary unit connection Failed path Switched connection
Protecting
Tributary unit Active protecting path
connection
Figure 18: Multipoint application example with a line break
The path from the conference in FOX61x 4 to the conference in FOX61x 3 is

rerouted via FOX61x 1 and FOX61x 2. Note that there is no change of the
path routing in the FOX61x 1 and FOX61x 2.
The following unidirectional cross connections have to be configured in all
involved NEs of the above example:
FUNCTIONS
Table 14: Multipoint linear application, protected cross connections

for SPR
NE Type Cross connections, unidirectional
A-End Working A-End Protecting Z-End
FOX61x 1 P12 transport to slave P12 transport to SPR Data interface 1
Master NE working protecting
Data interface 1 NA P12 transport to slave
working
P12 transport to SPR NA P12 transport to slave
protecting protecting
P12 transport to slave Data interface 1 P12 transport to SPR
FOX61x 2 P12 transport to master P12 transport to slave Conference participant
Intermediate slave NE working protecting “to master” a
P12 transport to slave P12 transport to master Conference participant
working protecting “to slave” b
Conference participant P12 transport to slave P12 transport to master
“to master” working working
P12 transport to slave Conference participant P12 transport to master
protecting “to slave” protecting
Conference participant P12 transport to master P12 transport to slave
“to slave” working working
P12 transport to master Conference participant P12 transport to slave
protecting “to master” protecting
Conference participant NA Data interface 1
“local” (3)
Data interface 1 NA Conference participant
“local” (3)
“local” (4)
“local” (4)
FOX61x 3 P12 transport to master P12 transport to slave Conference participant
Intermediate slave NE working protecting “to master”
P12 transport to slave P12 transport to master Conference participant
working protecting “to slave”
Conference participant P12 transport to slave P12 transport to master
“to master” working working
P12 transport to slave Conference participant P12 transport to master
protecting “to slave” protecting
Conference participant P12 transport to master P12 transport to slave
“to slave” working working
P12 transport to master Conference participant P12 transport to slave
“local” (3)
“local” (3)
FUNCTIONS
Table 14: Multipoint linear application, protected cross connections

for SPR (continued)
NE Type Cross connections, unidirectional
A-End Working A-End Protecting Z-End
FOX61x 4 P12 transport to master P12 transport to SPR Conference participant
Tail end slave NE working protecting “to master”
Conference participant NA P12 transport to master
“to master” working
P12 transport to SPR NA P12 transport to master
P12 transport to master Conference participant P12 transport to SPR
“local” (2)
“local” (2)
“local” (3)
“local” (3)
a. The “to master” is assumed to be in direction towards FOX61x 1

b. The “to slave” is assumed to be in direction towards FOX61x 4
The above listed cross connections protect the linear network also from a
failure of a conference unit in an intermediate network element. The failed
conference unit is bypassed.
5.2.2.5 Protection switching status
5.2.2.5.1 Signal status

When connections have been protected with SNCP or LTP it is possible to
check and control the status of the working and the protecting circuit and of
the protection switch via the CTP status function.
For the working and the protecting circuit the remote CTP managed object
address is displayed together with the circuit status:
− OK
The signal is fault free.
− SD
The signal is degraded. Refer to Table 10 to Table 13. for a descrip-
tion of the SD status.
− CAS AIS,
The signal is failed with a detected CAS AIS failure.
− SF.
The signal is failed. Refer to Table 10 to Table 13. for a description of
the SF status.
For protected Z-End CTPs it is indicated which trail is active:
− Working,
− Protecting,
− Protecting / Wait-To-Restore.
FUNCTIONS
This state is indicated for the revertive operation type as long as the
wait-to-restore timer is active.
Please note:
The status attributes are only available if the CTP acts as a connection sink,
i.e. is a Z-End (protected or unprotected) or a bidirectional A-End.
5.2.2.5.2 External requests

Protection switching is performed according to a priority list of requests. A
request can be a condition (e.g. signal fail) associated with a section, a state
(e.g. wait-to-restore) of the protection function or an external request (e.g.
forced switch):
Table 15: Protection switching requests

Order of priority Request Type
highest CLR Clear external request
| LP Lockout of protection external request
| FS Forced switch external request
| SF Signal Failed condition
| SD Signal Degraded condition
| MS Manual switch external request
| WTR Wait to restore state
| EXER Exercise external request
| RR Reverse request state
lowest NR No request state
The external requests and states used in the protection switching schemes
are defined as follows:
• CLR, Clear:
Clears all active external requests, i.e. the active request is a no-request.
• LP, Lockout of protection:
Fixes the actual protection switch status.
• FS, Forced switch:
Performs a switch to the selected channel if no LP is active.
• MS, Manual switch:
Performs a switch to the selected channel if no LP, FS, SF or SD is
active.
• WTR, Wait-to-restore:
During an active wait-to-restore a switched channel does not revert to the
default channel. Only used in revertive mode.
• EXER, Exercise:
Used to check the APS responses without performing a protection switch-
ing. Only used in dual-ended or revertive operation modes.
• RR, Reverse-request:
A part of the APS protocol. Only used in dual-ended or revertive opera-
tion modes.
• NR, No-request:
Default state without any external requests or conditions.
The external requests are available in the Status management function of
the Z-End CTPs. The FOX61x implements the following external requests:
• CLR, Clear:
FUNCTIONS
“Release”
• FS, Forced switch:
“Force Working”, “Force Protecting”
• MS, Manual switch:
“Manual Working”, “Manual Protecting”
The manual switch overrides the configuration parameter “Revertive”.
Applying a “Manual Protecting” request on a revertive CTP inverts the
revertive behaviour, i.e. the protecting input is preferred instead of the
working input.
Applying a “Manual Working” request on a revertive CTP has no effect.
Setting the external request to a state other than “Release” activates the
“maintenance function active” (MFA) alarm, if the CTP has fault manage-
ment.
The external requests are maintenance functions, i.e. they are not stored in
the units database.
Please note:
The availability of external requests is dependent of the unit and application.
→ Please refer to the description of the CTP Status managed objects in
the relevant user manuals.
5.3 P12 functions
The E1 ports, the PDH P12 signals and the SHDSL logports of the FOX61x
support different P12 termination modes for a variety of network applications.
The P12 termination mode defines the traffic signal structure and character-
istics.
Table 16: P12 termination mode defining the signal structure and
characteristics
Termination mode Signal CRC4 in CAS in time P12 timing P12 data Specific
structure time slot 0 slot 16 transparent transparent application
Transparent no n.a. n.a. yes yes no
Clock Master no n.a. n.a. no yes no
PCM30 G.704 no yes no no no
PCM30C G.704 yes yes no no no
PCM31 G.704 no no no no no
PCM31C G.704 yes no no no no
PCMnn G.704 no no no no no
PCMnnC G.704 yes no no no no
Structured n time slots n.a. no no no no
Structured With CAS n time slots n.a. yes no no no
G.704 Customized G.704 configurable configurable no no no
V5 Uplink G.704 yes no no no V5
V5 Uplink NCI G.704 no no no no V5
FUNCTIONS
5.3.1 Transparent
The transparent termination mode is used for the cross connection of
unstructured 2048 kbit/s signals or signals with an unknown structure. The
cross connection is transparent for data and timing, i.e. the P12 signal is in a
plesiochronous timing relationship to the network element timing source.
Transparent mode
LEDE1 SAMO1
E1 E1 P12 P12 P12 STM-x STM-x

port processing processing mapping port
P12 P12 STM-x STM-x

Transparent mode processing mapping port
DATI1 Transparent mode
SHDSL DSL P12 P12

port mapping processing PBUS
Transparent mode
Figure 19: Transparent termination mode application example
The two cross connected P12 signals must both be configured to the trans-
parent termination mode. The cross connection layer rate of transparent P12
signals is P12.
An E1 port or a PDH P12 signal in the P12 transparent mode can be used as
timing reference for the plesiochronous equipment timing source (PETS) of
the network element. Refer to section Plesiochronous equipment timing
source (PETS) (on page 60).
5.3.2 Clock Master

The clock master termination mode synchronizes a P12 signal to the net-
work element timing source (PETS) without terminating the P12 signal, i.e.
the through connected P12 signal is transparent for the data but not for the
timing.
This mode can be used for an application where no reliable clock source is
available in the terminating NEs of the P12 signal. The clock master mode
applies the reliable FOX61x PETS timing to the P12 signal which then trans-
ports this timing to the terminating NEs. The clock master mode is applied in
one NE only. All other intermediate NEs must be transparent for the timing.
The terminating equipment is required to loop the signal timing. If the incom-
ing P12 signals at the clock master NE would not be synchronous to the NE
timing then bit slips would occur, corrupting the data signals.
FUNCTIONS
Clock master mode

Clock master mode
LEDE1 SAMO1
E1 E1 P12 P12 P12 STM-x STM-x

port processing processing mapping port
P12 P12 STM-x STM-x

Clock master mode processing mapping port
DATI1
SHDSL DSL P12 P12 Clock master mode

port mapping processing
CESM1
NE timing
PBUS
(PETS)
PRC
Transparent Transparent
Terminating P12 Intermediate P12 P12 Clock master P12 P12 Intermediate P12 Terminating
NE NE NE NE NE
Timing looped Synchronisation Timing looped

network
PRC
Figure 20: Clock master termination mode application example
The two cross connected P12 signals must both be configured to the clock
master termination mode. The cross connection layer rate of clock master
P12 signals is P12.

The data format on the PBUS of the “Clock Master” mode traffic is not com-
patible with the data format of the “Transparent” mode traffic.
An E1 port, a PDH P12 signal or an SHDSL logport in the P12 clock master
mode can not be used as timing reference for the PETS of the network ele-
ment.
FUNCTIONS
5.3.3 PCM30 and PCM30C

An E1 port, a PDH P12 signal or an SHDSL logport of the FOX61x in the
PCM30 or PCM30C termination mode terminates a P12 signal with a struc-
ture according to ITU-T G.704. The PCM30 mode has CRC4 disabled, the
PCM30C mode has CRC4 enabled.
The signal has a structure with 32 time slots. time slot 0 is used for the frame
synchronization, time slot 16 is used for the CAS signalling transport. The 30
time slots 1 to 15 and 17 to 31 carry user data.
The cross connections are done at the P0_nc layer rate. It is possible to con-
nect P0_nc traffic signals from P12 trunks with CAS enabled to P12 trunks
with CAS disabled. Refer to section CAS handling (on page 53).
An E1 port or a PDH P12 signal in the P12 PCM30 or PCM30C mode can be
used as timing reference for the plesiochronous equipment timing source
(PETS) of the network element.
5.3.4 PCM31 and PCM31C

An E1 port, a PDH P12 signal or an SHDSL logport of the FOX61x in the
PCM31 or PCM31C termination mode terminates a P12 signal with a struc-
ture according to ITU-T G.704. The PCM31 mode has CRC4 disabled, the
PCM31C mode has CRC4 enabled.
synchronization. The 31 time slots 1 to 31 carry user data.
An E1 port or a PDH P12 signal in the P12 PCM31 or PCM31C mode can be
used as timing reference for the plesiochronous equipment timing source
(PETS) of the network element.
5.3.5 PCMnn and PCMnnC

An SHDSL logport of the FOX61x in the PCMnn or PCMnnC termination
mode terminates a P12 traffic signal with a structure according to ITU-T
G.704. The PCMnn mode has CRC4 disabled, the PCMnnC mode has
CRC4 enabled.
synchronization. The time slots 1 to nn carry user data. The valid range for
nn is 1 … 31. Unused time slots carry an AIS (all “1” signal).
The PCMnn and PCMnnC modes can operate with a reduced SHDSL line
rate corresponding to the configured number of traffic time slots plus time
slot 0 and additional DSL overhead. The minimum line rate without overhead
is 192 kbit/s (nn = 1 … 3).
FUNCTIONS
5.3.6 Structured and Structured With CAS

An SHDSL logport of the FOX61x configured as trunk signal in the “Struc-
tured” or “Structured With CAS” termination mode terminates a traffic signal
with a configurable number of time slots.
The “Structured” signal has a structure with 1 to 32 time slots. All time slots
carry user data, except if the “Clock Over Payload” is enabled. In this case
time slot 0 is used for the signal monitoring.
The “Structured With CAS” signal has a structure with 17 to 32 time slots.
time slot 16 carries the CAS, the other time slots carry user data, except if
the “Clock Over Payload” is enabled. In this case time slot 0 is used for the
signal monitoring.
The “Structured” and “Structured With CAS” modes can operate with a
reduced SHDSL line rate corresponding to the configured number of traffic
time slots plus additional DSL overhead. The minimum line rate without over-
head is 192 kbit/s.
5.3.7 G.704 customized

An SHDSL logport of the FOX61x in the G.704 customized termination mode
terminates a P12 signal with a structure according to ITU-T G.704. The
G.704 customized termination mode allows the individual configuration of the
CRC4 and CAS handling and of the time slot 0 processing. Please refer to
FOX61x DATI1 for further details.
synchronization. The 31 time slots 1 to 15 and 17 to 31 carry user data. time
slot 16 can be used for CAS or for user data.
5.3.8 V5 Uplink and V5 Uplink NCI

The V5 uplink termination modes are application specific PCM31C and
PCM31 modes available on the E1 interfaces and PDH P12 signals of the
FOX61x. The V5 uplink mode has CRC4 enabled, the V5 uplink NCI mode
has CRC4 disabled.
The V5 application uses the Sa7 spare bit of time slot 0 for the link identifica-
tion control.
An E1 port or a PDH P12 signal in the P12 V5 Uplink or V5 Uplink NCI mode
can be used as timing reference for the plesiochronous equipment timing
source (PETS) of the network element.
FUNCTIONS
5.3.9 CAS handling

Channel associated signalling (CAS) is used to transport signalling informa-
tion for different applications:
• Signalling for POTS subscribers,
• Signalling of E&M interfaces,
• Control signal transport of data interfaces,
• CAS supervision for P0_nc protection switching, available also without
signalling transport.
In a P12 signal the CAS is transported in time slot 16. A CTP using CAS on
a service unit, e.g. a POTS port on a LESU1 unit, can only be connected to a
P12 signal also supporting CAS. Otherwise the signalling information would
be lost.
In the FOX61x CAS is handled as an invisible property of the CTP. The CAS
setting is defined either by the unit type or by the P12 termination mode. The
following CAS settings apply:
.
Table 17: CAS setting on CTPs

Unit P12 termination mode CTP CAS setting
LESU1 n.a. unit-x/port-y true
LEXI1 n.a. unit-x/port-y true
LECO1 n.a. unit-x/port-y true
LEDA1 n.a. unit-x/port-y true or false a
LEDA1 n.a. unit-x/conf-y/part-z true or false a
LEDS1 n.a. unit-x/port-y true or false a
LEDS1 n.a. unit-x/conf-y/part-z true or false a
LEDE1 PCM30, PCM30C unit-x/port-y/chan-z true
LEDE1 PCM31, PCM31C unit-x/port-y/chan-z false
DATI1 PCM30, PCM30C unit-x/logports/logport-y/cpe/chan-a true
DATI1 PCM31, PCM31C unit-x/logports/logport-y/cpe/chan-a false
DATI1 PCMnn, PCMnnC unit-x/logports/logport-y/cpe/chan-a false
DATI1 G.704 Customized with CAS unit-x/logports/logport-y/cpe/chan-a true
DATI1 G.704 Customized without CAS unit-x/logports/logport-y/cpe/chan-a false
DATI1 Structured with CAS unit-x/logports/logport-y/trunk/chan-a true
DATI1 Structured unit-x/logports/logport-y/trunk/chan-a false
SAMO1 PCM30, PCM30C unit-x/pdh/vc12-y/p12/chan-z true
SAMO1 PCM31, PCM31C unit-x/pdh/vc12-y/p12/chan-z false
SAMO1 n.a. unit-x/port-y/dcc false
SAMO2 PCM30, PCM30C unit-x/pdh/vc12-y/p12/chan-z true
SAMO2 PCM31, PCM31C unit-x/pdh/vc12-y/p12/chan-z false
SAMO2 n.a. unit-x/logports/logSdhPorts/sdh-y/dccm false
SAMO2 n.a. unit-x/logports/logSdhPorts/sdh-y/dccr false
EPSI1 MAC HDLC, n=x (P0_nc) unit-x/tdmInterfaces/machdlc-y true or false b
EPSI1 MAC HDLC, P12 unit-x/tdmInterfaces/machdlc-y false
EPSI1 PPP, n=x (P0_nc) unit-x/tdmInterfaces/ppp-y true or false b
EPSI1 PPP, P12 unit-x/tdmInterfaces/ppp-y false
EPSI1 MLPPP, n=x (P0_nc) unit-x/tdmInterfaces/mlppp-y/member-z true or false b
FUNCTIONS
Table 17: CAS setting on CTPs (continued)

Unit P12 termination mode CTP CAS setting
EPSI1 MLPPP, P12 unit-x/tdmInterfaces/mlppp-y/member-z false
ne (CESM1) PPP, n=x (P0_nc) ne/managementNetwork/tdmInterfaces/ true or false b
ppp-y
ne (CESM1) PPP, P12 ne/managementNetwork/tdmInterfaces/ false
ppp-y
TEPI1 n.a. unit-x/applications/teleprotectionsignal- false
ling/chan-y
TEPI1 n.a. unit-x/applications/binarysignaltransmis- false
sion/chan-y
OPIC1 P0_nc unit-x/chan-y false
OPIC1 P12 unit-x/chan-y false
a. The CAS usage is configurable. Refer to the units user manual for more informa-
tion.
b. For n up to 30 a TDM interface can be connected to P12 transport signal with CAS.
For n=31 a TDM interface can only be connected to a P12 transport signal without
CAS. CAS can be used as protection switching criterion.
The CAS setting imposes the following TDM connection restrictions in the
FOX61x:
Table 18: Connection between CTPs with and without CAS

CTP Unit
LESU1 /port-y connects only to port or channel CTPs with CAS setting true
LEXI1 /port-y connects only to port or channel CTPs with CAS setting true
LECO1 /port-y connects to any other CTP, regardless of the CAS setting
LEDA1 /port-y, CAS enabled connects to any other CTP, regardless of the CAS setting
LEDA1 /port-y, CAS disabled connects to any other CTP, regardless of the CAS setting
LEDA1 /conf-y/part-z, CAS enabled connects to any other CTP, regardless of the CAS setting
LEDA1 /conf-y/part-z, CAS disabled connects to any other CTP, regardless of the CAS setting
LEDS1 /port-y, CAS enabled connects to any other CTP, regardless of the CAS setting
LEDS1 /port-y, CAS disabled connects to any other CTP, regardless of the CAS setting
LEDS1 /conf-y/part-z, CAS enabled connects to any other CTP, regardless of the CAS setting
LEDS1 /conf-y/part-z, CAS disabled connects to any other CTP, regardless of the CAS setting
LEDE1 /port-y/chan-z connects to any other channel CTP, regardless of the CAS setting;
connections to port CTPs with CAS require the CAS setting true
DATI1 /logports/logport-y/cpe/chan-a connects to any other channel CTP, regardless of the CAS setting;
DATI1 /logports/logport-y/trunk/chan-a connects to any other channel CTP, regardless of the CAS setting;
SAMO1 /pdh/vc12-y/p12/chan-z connects to any other channel CTP, regardless of the CAS setting;
SAMO1 /port-y/dcc connects to any other CTP, regardless of the CAS setting
SAMO2 /pdh/vc12-y/p12/chan-z connects to any other channel CTP, regardless of the CAS setting;
SAMO2 /logports/logSdhPorts/sdh-y/dccm connects to any other CTP, regardless of the CAS setting
SAMO2 /logports/logSdhPorts/sdh-y/dccr connects to any other CTP, regardless of the CAS setting
EPSI1 /tdmInterfaces/machdlc-y connects to any other CTP, regardless of the CAS setting
FUNCTIONS
Table 18: Connection between CTPs with and without CAS (contin-
CTP Unit
EPSI1 /tdmInterfaces/ppp-y connects to any other CTP, regardless of the CAS setting
EPSI1 /tdmInterfaces/mlppp-y/member-z connects to any other CTP, regardless of the CAS setting
ne /managementNetwork/tdmInterfaces/ppp-y connects to any other CTP, regardless of the CAS setting
TEPI1/applications/teleprotectionsignalling/chan-y connects to any other CTP, regardless of the CAS setting
TEPI1/applications/binarysignaltransmission/chan-y connects to any other CTP, regardless of the CAS setting
OPIC1/chan-y connects to any other CTP, regardless of the CAS setting

Connections between channel CTPs with CAS on the A-End and without
CAS on the Z-End (or vice versa) can lead to malfunctions.
→ It is the operators responsibilty to check the required CAS setting in
channel CTP connections.
Examples:
• The connection of a POTS port on a LESU1 unit to a channel with n = 1
on a LEDE1 port, configured to PCM30, is supported.
• The connection of a POTS port on a LESU1 unit to a channel with n = 1
on a LEDE1 port, configured to PCM31, is not supported.
• The connection of a channel with n = 2 on a LEDE1 port, configured to
PCM31, to a channel with n = 2 on a LEDE1 port, configured to PCM31,
is supported.
When creating a connection of a P0_nc traffic signal to another P0_nc traffic
signal, the connection will typically use consecutive time slots. If the source
or destination P12 signal uses CAS the P0_nc signals will still occupy con-
secutive time slots but will skip time slot 16 if required.
P12 A-End CTP 1
PCM30, n = 19, 0 1 15 16 17 20
timeslots = 1…15, 17...20
P12 A-End CTP 2

PCM30, n = 6, 0 1 6 16
timeslots = 1...6
connection 1 connection 2
CTP 2 to CTP 4 CTP 1 to CTP 3
P12 Z-End CTP 3

0 1 7 15 16 17 26
P12 Z-End CTP 4
P12 Z-End CTP 4 P12 Z-End CTP 3

PCM30, n = 6, PCM30, n = 19,
timeslots = 1…6 timeslots = 7...15, 17...26
Figure 21: Skipping of time slot 16
FUNCTIONS
5.4 Synchronization
5.4.1 Network reference timing distribution

TDM network elements (NE) are generally required to be synchronized to a
network reference clock, i.e. a centralized NE timing source provides the
synchronous timing signal to all NE functions requiring this signal.
There are several approaches how to bring the network timing to the TDM
network element:
• Master-slave strategy over synchronization networks,
• Distributed PRC strategy with e.g. GPS technologies,
• Reference timing distribution via a synchronous Ethernet,
• Reference timing distribution over packet networks.
The plesiochronous TDM applications require no PRC derived NE timing, but
still the service clock must fulfil the TDM timing requirements.
5.4.1.1 Master-slave timing distribution
Typically, a TDM circuit service provider will maintain a timing distribution

network, providing synchronization traceable to a primary reference clock.
The timing distribution network is based on a master-slave strategy and is
defined in the ITU-T G.803 and ITU-T G.823 recommendations.
One single timing source, the primary reference clock (PRC, ITU-T G.811)
provides the timing for all network elements in the TDM network. The timing
is distributed from the PRC via the SSU to the SEC network elements.
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 SEC = SDH equipment clock

G.813 G.813 G.813 G.813 (network element clock)
TDM TDM TDM TDM TDM

Equipment Equipment Equipment Equipment Equipment
Figure 22: Hierarchical synchronization network architecture
FUNCTIONS
Two alternative synchronization distribution methods may be used between

SSUs and between the PRC and SSUs:
• SDH distribution, using the SDH section layer. A number of sections may
be cascaded each containing an SEC.
• PDH distribution, using a 2048 kbit/s PDH path. Between two SSUs or
between the PRC and an SSU a number of intermediate PDH multiplex-
ing NEs and PDH line systems may be deployed. These NEs are not
shown in the figure below.
The maximum number of SSU and SEC in a synchronization network is
shown in the synchronization network reference chain, refer to the figure
below.
A PDH network element can be connected to any of the SEC network ele-
ments.
PRC
SEC
PDH
N SEC TDM distribution
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 23: Synchronization network reference chain
FUNCTIONS
5.4.1.2 Distributed PRC timing distribution
One approach to bring the network timing to the interworking function NE is

to follow a distributed PRC strategy. For instance, by means of GPS technol-
ogies.
A TDM network element can be connected directly to a PRC.
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
TDM TDM TDM TDM

Equipment Equipment Equipment Equipment
Figure 24: Distributed PRC network architecture
5.4.1.3 Synchronous Ethernet timing distribution
Traditional Ethernet networks are free-running. However, all the key ele-
ments exist within Ethernet technology in order to make it synchronous and
allow a master-slave synchronization architecture to be introduced at the
physical layer. The Ethernet physical layer can then be used to provide refer-
ence timing signal distribution over packet networks.
The general concept of delivering a physical layer clock from the Ethernet
switch to the TDM/IP NE with incorporated Ethernet interfaces is given in the
figure below.
PRC PRC
Switch Switch Switch Switch

TDM TDM TDM / IP Packet Switched TDM / IP TDM TDM
Equipment NE Network NE Equipment
data Switch Ethernet switch supporting

PRC timing synchronous Ethernet PHY
Figure 25: Timing distribution over Ethernet
A reference timing signal traceable to a PRC is injected into the Ethernet

switch using an external clock port. This signal is then used to inject the tim-
ing onto the Ethernet bit stream.
Any Ethernet switch between the element where the reference timing signal
is injected and the TDM/IP interworking function must be able to recover
FUNCTIONS
synchronization from the incoming bit stream and forward it towards the
TDM/IP NE.
5.4.1.4 Packet timing distribution
In cases where no PDH or SDH synchronization network is available and no

synchronous Ethernet can be used for the reference timing distribution a
packet based method can be used to transport the timing information to a
network element connected to a packet switched network. This packet based
method is called circuit emulation service (CES).
Such a method can be based on the time stamps carried by the CES pack-
ets or by the jitter buffer fill level in the receiving network element.
A packet based timing distribution method 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.
PRC PRC available at the IWF
Packet
CES Switched CES
TDM TDM Ethernet
Network Ethernet TDM TDM
Equipment
IWF IWF Equipment
PRC PRC available at the TDM end system
Packet
CES Switched CES
TDM TDM Ethernet
Equipment
IWF IWF Equipment
CT Customer Timing transported over the PSN
Packet
CES Switched CES
TDM TDM Ethernet
Equipment
IWF IWF Equipment
data
PRC timing
customer timing
Figure 26: Timing distribution over the packet network
FUNCTIONS
In the CES interworking function the TDM timing must be regenerated in the
clock recovery circuit and forwarded to customer equipment at the remote
end.
5.4.2 Plesiochronous equipment timing source (PETS)

A PDH network element with synchronous and plesiochronous traffic signal
transport requires an equipment timing source, called the PETS (Plesiochro-
nous Equipment Timing Source). Timing characteristics 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 Ether-
net equipment timing source). Timing characteristics are according to ITU-T
G.8262.
In the FOX61x NE one common timing source for PDH and synchronous
Ethernet is available on the CESM1 unit and is called the PETS. 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 50 ppm.
Depending of the selected synchronization approach the PETS configuration
requires the selection of the correct clock source.
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:
• esi-1 or esi-2 2048 kHz clock input on the CESM1 unit,
• E1 ports on the LEDE1 unit,
• SHDSL span on the DATI1 unit,
• SETS on the SAMO1 unit,
• SETS on the SAMO2 unit,
• PDH P12 signal on the DATI1 and SAMO1 unit.
Plesiochronous PDH and Ethernet applications can rely on a free running
PETS. The PETS can use one of the following sources:
• CESM1 internal clock oscillator,
• SETS on the SAMO1 unit (configured to internal),
• SETS on the SAMO2 unit (configured to internal).
FUNCTIONS
SAMO1 (STM-4/STM-1)
SAMO2 (STM-16/STM-4/STM-1)
SETS
clock
recovery
STM-16/4/1 SDH SDH P12

port multiplexer processing up to 4 clocks from
service units
PETS CESM1
DATI1 (SHDSL NT, Trunk To LT) EEC
Selector
clock to PBUS
clock clock SETG
recovery recovery
SHDSL SHDLSL SHDSL P12

port processing processing
Selector
Selector
DATI1 (SHDSL LT, Trunk To NT)
clock from
clock Eth Rx clock from clock to clock to
recovery esi-1/2 eso-1 Eth Tx
Front Front Front Front
interface interface interface interface
SHDSL SHDLSL SHDSL P12 Eth receive esi-1/2 eso-1 Eth transmit
port processing processing
LEDE1 (E1)
clock
recovery
E1 E1 P12
port processing
ETOP1 (Ethernet)
SAMO2 (Ethernet)
clock
recovery
PBUS
Ethernet ETH Ethernet

port Bridge PETS timing
timing source
Figure 27: PETS clock source selection
In a first step up to four PDH clock sources can be selected from the availa-
ble sources on the service units (E1 ports, SHDSL NT clock, SHDSL NT
payload clock, SHDSL LT clock, P12 clock, SETS). Together with the two
external synchronization inputs (ESI) and the local oscillator (Internal) up to
seven clock sources are available to synchronize the PETS.
In a second step the priority of each of the seven selectable clock sources
must be configured from 1 (highest priority) to 7 (lowest priority). These prior-
ities are used by the automatic clock source selection algorithm. Using the
priority based selection algorithm the available clock with the highest priority
will be used as synchronization source for the PETS. If this clock source fails
FUNCTIONS
the clock source with the next lower priority will be selected automatically.
When using the quality level (QL) based selection algorithm the received or
configured QL of each clock source is used by the automatic clock source
selection algorithm instead.
The synchronization output interface ESO-1 can be used for the synchroni-
zation of external elements, e.g. another FOX61x NE.
The PETS function is implemented on the CESM1 core unit. However, the
synchronization function is a network element function and hence most man-
agement functions are located on the NE access point.
The APs to access the synchronization functions are:
• AP: /ne, Configuration - PETS,
• AP: /ne, Configuration - ESO,
• AP: /ne, Fault Management: PETS related alarms,
• AP: /ne, Status - PETS,
• AP: /ne, Status - ESO.
The following synchronization related APs exist on CESM1:
• AP: /unit-11/neController/esi-1, Fault Management: ESI-1 loss of signal
• AP: /unit-11/neController/esi-2, Fault Management: ESI-2 loss of signal
5.4.2.1 PETS clock operation modes
There are three clock operation modes for the PETS in the FOX61x accord-
ing to ITU-T G.813:
• Locked
Normal operation mode. The output PETS clock signal is controlled by an
external input reference or the internal clock, so they have the same long
term average frequency.
• Holdover
If all configured clock sources fail, 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 opera-
tion command “Forced Holdover”.
• Free running
If the PETS does not have a clock reference input, it determines its out-
put clock by an internal default reference frequency. Note that the clock
operating mode shows “Locked” together with the selected clock source
“Free Running”.
You can also bring the PETS into this mode with the PETS clock opera-
tion command “Forced Free Running”.
Note that in the FOXCST the “free running” mode is displayed as
− Selected Clock Source = Internal, and
− Clock Operation Mode = Holdover.
In the “Auto Selection” mode, the PETS 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 “Hold-
off Time” and “Wait-To-Restore Time”:
• Holdoff Time
FUNCTIONS
When a clock source fails the PETS 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 PETS is operating with a low priority clock source and a previ-
ously failed higher priority clock source becomes available again, the
PETS waits for the wait-to-restore time (configured for the higher priority
clock source) before switching to the higher priority clock source.
PDH clock source 1
Priority 1
available
failed
time
PDH clock source 2
Priority 2
available
failed
time
Internal clock
Priority 7
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 operating
mode
locked holdover locked holdover locked locked locked
time
Figure 28: PETS clock source selection with 2 external and 1 internal
clock sources
FUNCTIONS
PDH clock source 1

Priority 1
available
failed
time
PDH clock source 2
Priority 2
available
failed
time
Internal clock
Priority 7
available
disabled
time

time
Clock operating
mode
locked holdover locked holdover locked locked
time
Figure 29: PETS clock source selection with 2 external clock sources
5.4.2.2 PETS clock source selection
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:
• Selection algorithm according to a configured priority
(AP: /ne, Configuration - PETS: Selection Algorithm = Priority):
The PETS selection process is only controlled by the priority. The selec-
tion algorithm disregards the quality level (QL).
• Selection algorithm according to the quality level (QL)
(AP: /ne, Configuration - PETS: Selection Algorithm = QL):
The PETS selection process first considers the QL and then the Priority.
The QL is transported in the synchronization status message (SSM) or
synchronization status indication (SSI) of the time slot 0 of a structured
P12 signal. For a description of the QL handling please refer to section
Quality level handling in SDH and PDH signals (on page 73).
To make a PETS clock source available it must be given a priority between 1
and 7 in the PETS clock selection configuration dialogue at the AP: /ne, Con-
figuration - PETS. Note that 1 is the highest priority.
A clock source is deselected by applying the priority value “Disabled”.
The PETS clock source selection is configured depending of the selected
synchronization strategy according to the following points:
• PDH or SDH synchronization network or distributed PRC strategy:
The timing interface to the synchronization network is a 2048 kHz clock
signal according to ITU-T G.703.
The clock signal is connected to one of the ESI-1 or ESI-2 front interfaces
on the CESM1 unit.
FUNCTIONS
The ESI-1 or ESI-2 must be enabled and given a high clock priority in the
PETS configuration. AP: /ne, Configuration - PETS: e.g. ESI-1: 1.
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-1 and esi-2 managed objects on the CESM1 are activated.
→ The fault management of the esi-1 and esi-2 managed objects on the
CESM1 is activated.
Please note:
The ESI-1 port or ESI-2 is enabled when a clock priority is assigned to it in
the SETS or ESO configuration on a SAMO1 or SAMO2 unit.
→ The esi-1 and esi-2 managed objects on the CESM1 are not acti-
vated.
CESM1 is not activated.
→ The fault management of the esi-1 and esi-2 managed objects is avail-
able on the SAMO1 or SAMO2 unit as SETS and ESO fault causes.
• Synchronization via the TDM network:
The timing interface to the TDM network is an
− E1 data signal according to ITU-T G.703, or an
− SHDSL trunk line to LT.
The E1 signal is connected to one of the E1 ports on the LEDE1 unit. The
SHDSL signal is connected to one of the SHDSL ports on the DATI11
unit.
The PETS can also be synchronized to a P12 signal demapped from an
STM-16, STM-4 or STM-1 signal or demapped from an SHDSL signal.
The E1 port or P12 signal 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 PDH clock source selection is done in the NE PETS configuration,
AP: /ne, Configuration - PETS.
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.
• SETS on SAMO1 or SAMO2:
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, e.g. /unit-5.
• Free running internal oscillator:
To synchronize the PETS to the internal oscillator, all external clock
sources must be disabled or the internal oscillator must be given the
highest priority.
FUNCTIONS
5.4.3 Synchronous equipment timing source (SETS)

All SDH ports and SDH processing on an SDH service unit (SAMO1 or
SAMO2) are synchronized to the synchronous equipment timing source
(SETS). Each SDH service unit provides one SETS that is used for the unit.
The SETS is handled as a unit function. It is possible to synchronize the
SETS functions of several SDH service units to one common clock source.
The SETS has three external clock input types (T1, T2, T3), one internal
clock source and provides two external clock output types (T0, T4) as shown
in the figure below.
SETS
Selector A
Selector C
ESO-2 T4
SDH port 1
Selector B
SDH port 2
T1 SETG T0
SDH port 3
PDH-1
SDH port 4
Distributor D
PDH-2
PDH-1 SEC
PDH-3
PDH-2
T2 PDH-4
PDH-3
PDH-4
T3 ESI
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 a 2 Mbit/s data signal
T3: Timing signal derived from a 2 MHz station clock signal
T4: Timing towards a 2 MHz station clock output signal
Figure 30: SETS functions
T1 is the synchronization signal derived from an SDH interface. Up to four

(SAMO1 and SAMO2) or eight (SAMO2 with unit redundancy) SDH clock
sources can be selected for the SETS synchronization in maximum per SDH
service unit.
T2 is the synchronization signal derived from a 2 Mbit/s data signal. Up to
four PDH (or SDH) clock sources are available for the SETS synchronization
in maximum. The T2 timing is distributed in the NE via the PDH clock source
lines of the PBUS.
T3 is the synchronization signal from an external synchronization clock input.
CESM1 provides 2 external clock inputs ESI-1 and ESI-2. The CESM1 con-
figuration selects one of these inputs which can then be used for the SETS
synchronization.
FUNCTIONS
Please note:
The ESI clock source selection on the SAMO1 and SAMO2 unit for SETS or
ESO is fixed to ESI-2.
→ The selection of the ESI-1 clock input for the SETS or ESO will be
available in a future release.
Please note:
The ESI-2 port is enabled when a clock priority is assigned to it in the SETS
or ESO configuration on an SDH service unit.
vated.
The internal reference clock has an accuracy of ± 4.6 ppm according to ITU-
T G.813 (clause 5, option 1).
T0 is the synchronization signal used for the unit internal synchronization. T0
is also distributed to all other units via one of the PDH clock source lines of
the PBUS.
T4 is the synchronization signal for an external synchronization clock output.
CESM1 provides 2 external clock outputs, ESO-1 is reserved for the PETS
clock output, ESO-2 can be used for the SETS synchronization output. T4
can be configured to SETS locked or non-SETS locked, i.e. derived directly
from a synchronization signal.
5.4.3.1 SETS clock operation modes
There are three clock operation modes for the SETS in the FOX61x accord-
ing to ITU-T G.813:
• Locked
Normal operation mode. The output SETS clock signal is controlled by an
external input reference so they have the same long term average fre-
quency.
• Holdover
If the clock reference fails, SETS 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 SETS into this mode with the SETS clock opera-
tion type command “Forced Holdover” (AP: /unit-x, Status - SETS - Gen-
eral).
• Free running
If the SETS does not have a clock reference input, it determines its out-
put clock by an internal default reference frequency.
You can also bring the SETS into this mode with the SETS clock opera-
tion type command “Forced Free Run” (AP: /unit-x, Status - SETS - Gen-
eral).
In the “Auto Selection” mode, the SETS selects its operation mode by itself,
depending on the conditions given by the availability of synchronization
sources.
FUNCTIONS
The clock selection process can be controlled by the two parameters “Hold-
off Time” and “Wait-To-Restore Time”:
• Holdoff Time
When a clock source fails the PETS 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 PETS is operating with a low priority clock source and a previ-
ously failed higher priority clock source becomes available again, the
PETS 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

time
Clock operation
mode
locked holdover locked holdover locked locked
time
Figure 31: 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.
FUNCTIONS
5.4.3.2 SETS clock source selection
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 selec-
tion algorithm disregards the quality level (QL).
• Selection algorithm according to the quality level (QL)
(AP: /unit-x, Configuration - SETS: Selection Algorithm = QL):
The SETS selection process first considers the QL and then the Priority.
The QL is transported in the synchronization status message (SSM) of
the SDH MS overhead or the time slot 0 of a structured P12 signal (future
release). For a description of the QL handling please refer to section
Quality level handling in SDH and PDH signals (on page 73).
To make a SETS clock source available it must be given a priority between 1
and 10 (SAMO1) or 14 (SAMO2) in the SETS clock selection configuration
dialogue on the SAMO1 or SAMO2 unit at the AP: /unit-x, Configuration -
SETS. Note that 1 is the highest priority.
A clock source is deselected by applying the priority value “Disabled”.
The SETS clock source selection is configured depending of the selected
synchronization strategy according to the following points:
• SDH synchronization network or distributed PRC strategy:
The timing interface to the synchronization network is a 2048 kHz clock
signal according to ITU-T G.703.
The clock signal is connected to the ESI-1 or ESI-2 front interfaces on the
CESM1 unit.
The ESI must be enabled and given a high clock priority in the SETS
clock selection configuration of the SAMO1 or SAMO2 unit.
Please note:
• Synchronization via the SDH TDM network:
The timing interface to the TDM network is an STM-16, STM-4 or STM-1
data signal according to ITU-T G.707.
The STM-16/STM-4/STM-1 signal must be enabled and given a high
clock priority in the SETS clock selection configuration.
• Synchronization via the PDH TDM network:
The timing interface to the TDM network is an
− E1 data signal according to ITU-T G.703, or an
− SHDSL trunk line to LT.
The E1 signal is connected to one of the E1 ports on the LEDE1 unit. The
SHDSL signal is connected to one of the SHDSL ports on the DATI1 unit.
The timing interface to the TDM network is an E1 (2048 kbit/s) data signal
according to ITU-T G.703. The E1 signal is connected to one of the E1
ports on the LEDE1 unit.
FUNCTIONS
The SETS can also be synchronized to a P12 signal demapped from an

STM-16, STM-4 or STM-1 signal or demapped from an SHDSL signal.
The E1 port or P12 signal transporting the timing information must be
operated in one of the following termination modes:
− Transparent,
− PCM30, PCM30C,
− PCM31, PCM31C,
The E1 port or P12 signal must
− first be selected as a PDH clock source in the PETS configuration and
− second the PDH clock source is given a high clock priority in the
SETS clock selection configuration.
Please note:
On the SAMO1 unit only the P12 signals from vc12-1 to vc12-4 can be
selected as PDH clock source.
Please note:
On the SAMO2 unit no P12 signals can be selected as PDH clock source.
• Free running internal oscillator:
To synchronize the SETS to the internal oscillator, all external clock
sources must be disabled or given a lower priority.
FUNCTIONS
5.4.4 SETS and PETS synchronization functions

A SETS (SDH equipment timing source) function is available on every
SAMO1 and SAMO2 unit.
The PETS (plesiochronous equipment timing source) function is available on
the CESM1 unit(s).
SAMO1 or SAMO2
SETS
Selector
SETS clock to eso -2
Selector
clock output
up to 4 or 8
Front STM clocks
interfaces Selector SEC SETS clock to PDH
STM-x-y timing sources
SETG
up to 4 PDH
timing sources
ESI timing source
CESM1
up to 4 PDH
clock sources
Front
esi-1 clock Front
Selector
interface clock from Eth Rx

esi-1 esi-2 clock interface
Eth receive
Front
interface
esi-2 PETS
EEC
Selector
esi-1 clock PETS clock to PBUS

SETG
esi-2 clock
Selector
Selector
esi-1 clock
PBUS
esi-2 clock
PETS clock clock to

to eso-1 Eth Tx
Front Front Front
interface interface interface
eso-1 Eth transmit eso-2
SETS timing esi timing source

PETS timing PDH timing source
eso-2 timing
Figure 32: SETS and PETS implementation in FOX61x
Timing signals are exchanged between the FOX61x units via the subrack
backplane:
FUNCTIONS
• 2 lines for the ESI timing, one line accessed by the active CESM1 unit,
the other line accessed by the standby CESM1 unit, and used by any ser-
vice 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 CESM1 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 clock source.
In case of a failure on the SDH service unit the ESO clock output is
squelched.
• 4 lines for the PDH clock sources, driven by a service or a core1 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 equip-
ment timing.
The PDH clock source in the PETS configuration is configured to the
SETS of an SDH service unit, e.g. /unit-5.
• 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 SAMO2 unit, and the other SAMO1 or SAMO2 units select
this PDH clock source in the SDH clock selection configuration.
Please note:
It is not possible to 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.
1. The Ethernet front interfaces on the CESM1 will be usable as PDH clock sources
in a future release.
FUNCTIONS
5.4.5 Quality level handling in SDH and PDH signals

5.4.5.1 Quality level with SSM
The QL (Quality Level) information for synchronization purposes is a part of

the SSM (Synchronization Status Message) signalling system for PDH and
SDH signals.
The SSM is a four bit code, defined in ITU-T G.704 for PDH and in ITU-T
G.707 for SDH. The following codes are defined:
• SSM = 0000: QL = 0 “Quality unknown”,
• SSM = 0010: QL = 2 “ITU-T G.811”,
• 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)”,
• SSM = 1111: QL = 15 “Do not use for synchronization”.
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 or to modify the
QL information of an SDH clock source via mapping tables. If the incoming
signal provides no QL information, a default QL will be assigned to these sig-
nals.
The FOXCST allows you to assign QL values from 1 to 15.
5.4.5.2 Quality level with SSI
For PDH signals the ABB proprietary synchronization status indication (SSI)
can be used alternatively to the SSM. The SSI is compatible to the FOX.
The SSI is transported in the Sa5 bit of the time slot 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.4.5.3 PETS quality level
The Figure 33 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,
− ESI synchronization signals ESI-1 to ESI-2,
FUNCTIONS
− Internal (local oscillator).

• Output signals:
− Network element PDH signal timing (PETS),
− ESO synchronization signal ESO-1.
FUNCTIONS
PDH or SDH or Ethernet CESM1 PDH or SDH or Ethernet

service unit service unit
QL received
or adjusted
QL based or
or fixed Priority based
can be used : QL = unchanged
SETS PDH clock PETS clock
do not use : QL = 15
(STM) source selection
QL override
Routing Table Interface
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
(PETS) (P12) (P12)
QL extraction
Interface PDH clock
from SSI
(P12) source
(P12)
QL override
QL received by QLfix
(PETS) Routing Table Interface
QL extraction (Ethernet ) (Ethernet )
Interface PDH clock
Selector B
from SSM
(P12) source QL override
(P12)
by QLfix
(PETS)
Routing Table Interface
no QL SETG (Ethernet ) (Ethernet )
Interface PDH clock QL override
(Ethernet ) source by QLfix
(PETS)
QL received
PETS locked
QL extraction QL override
Interface PDH clock
from SSM by QLfix
(Ethernet ) source
(Ethernet ) (PETS)
ESO selected clock source from
QL fixed selector A or selector B
Squelched by
Source and QL from the selected
Local clock source
Oscillator
Selector D
QL fixed Squelch ESO for

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

by QLfix
(ESO)
QL override
ESI-1
by QLfix
(active CESM1) QL based or
(ESO)
Priority based
ESO clock
no QL
QL override selection
ESI-2
by QLfix
(active CESM1) (ESO)
QL fixed
Figure 33: QL handling for PDH traffic signals and other clock sources
1
1. Synchronous Ethernet in FOX61x will be available in a future release.
FUNCTIONS
The PDH traffic and synchronous Ethernet based synchronization sys-

tem 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 time slot 0 Sa bit (QL received).
Note that P12 signals not supporting the SSM or SSI have no QL
assigned.
• QL extraction from SSM or SSI, assigned to the P12 layer:
The SSM or SSI is extracted from the time slot 0 Sa bit (QL received).
Note that P12 signals not supporting the SSM or SSI have no QL
assigned.
• PDH clock source:
The PDH clock sources from PDH service units and SDH clock sources
from SDH service units are transported via the FOX61x backplane. The
QL assigned to a clock source is forwarded transparently.
The QL of a PDH 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,
adjusted or fixed, refer to Figure 34 and Figure 35).
• QL override, assigned to the PETS access point:
It is possible to configure the timing system so that the received QL is for-
warded 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
14 (configuration QL = <specified value>) or even to “Do Not Use”.
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.
• PDH clock source output:
The PETS QL information (QL of the selector) is forwarded transparently
according to the selected clock source to the PDH clock source output.
• PDH routing table, assigned to the P12 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 routing table marks the traffic signal with
“Can be used” (QL = unchanged) or “Do not use” (QL = 15).
The routing table is fixed 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”.
Note that the routing table cannot be modified with the FOXCST.
Please note:
Only the PETS function configured to the “QL” based clock selection algo-
rithm interprets the SSM in the traffic signal. If the PETS function is config-
ured to the “Priority” based clock selection algorithm the received SSM or
SSI is not considered.
The ESI/ESO synchronization interface based synchronization system
provides the following functional blocks for the QL processing:
• ESI synchronization input:
The CESM1 unit provides two synchronization input interfaces, ESI-1 and
ESI-2. 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:
FUNCTIONS
The ESI clock source gets a fixed QL which is forwarded to the PETS
selector A and selector B. The fixed value is configurable in the range 1
to 14 (configuration QL = <specified value>) or even to “Do Not Use”.
• Selector A, assigned to the ESO access point:
Selector A is used for the clock source selection for the ESO-1 synchroni-
zation output interface in the “non PETS locked” mode.
clock source.
• Selector B, assigned to the PETS access point:
Selector B is used for the clock source selection for the ESO-1 synchroni-
zation output interface in the “PETS locked” mode.
clock source to the synchronous equipment timing generator (SETG).
• 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 synchroniza-
tion 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 wether 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.
• Selector D, assigned to the PETS access point:
Selector D will be available in a future release. The routing table is
directly controlled by the selector B state.
5.4.5.4 SETS quality level
The Figure 34 and the Figure 35 show the quality level (QL) information han-
dling as it is implemented on the SAMO1 and SAMO2 units for the following
input clock sources and output signals:
• Input signals:
− 4 STM-16, STM-4 and STM1 traffic signals,
− 4 additional STM-16, STM-4 and STM1 traffic signals on a protecting
SAMO2 unit (not shown in Figure 35),
− 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
SAMO2 unit (not shown in Figure 35),
− 1 PDH clock source signals (FOX61x internal),
− 1 ESO synchronization signal ESO-2.
The ESO-2 synchronization output interface used for the SDH timing oper-
ates in two different modes:
• SETS locked mode,
FUNCTIONS
• Non SETS locked mode,

In the “SETS locked” mode, the SETG of the SETS system provides the tim-
ing signal for the ESO-2 output. The clock sources for the ESO-2 are there-
fore 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 SAMO2 unit provides the 4 or 8 SDH traffic signals as
clock sources.
FUNCTIONS
CESM1 PDH clock

SAMO1 SDH service unit
source
(PETS) QL received
or adjusted
or fixed preselected timing source
PDH clock
source
(PETS)
PDH clock
Preselector
QL override
source by QLfix
(PETS) (SETS) can be used : QL = unchanged
QL based or QL adjusted 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 -1/ESI-2
active CESM1 no QL
Output Mapping SDH Routing Front
Local (MS) (MS) STM-x
ESI -1/ESI-2 Oscillator
standby CESM1
QL received QL adjusted Table for QL Table interface
QL fixed
(MS) (MS) STM-x
Front QL extraction Input Mapping QL override
interface from SSM Table for QL by QLfix
STM-x (MS) (MS) (SETS)
Selector B

SETG Table for QL Table interface
(MS) (MS) STM-x
to PDH clock
Front QL extraction Input Mapping QL override source
interface from SSM Table for QL by QLfix PDH clock
STM-x (MS) (MS) (SETS) source
SETS locked
Front QL extraction Input Mapping QL override selected
interface from SSM Table for QL by QLfix clock source
QL received
or adjusted
or fixed
ESO
Squelched by
QL override Source
by QLfix
(ESO)
Squelch ESO for Squelch ESO
certain Sources for certain QL
QL override
by QLfix
Selector C
(ESO) ESO Front

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

QL override
non SETS locked
by QLfix ESO clock
(ESO)
selection
QL override
by QLfix
(ESO) QL based or
Priority based
QL received ESO clock CESM1
or adjusted selection
or fixed
Figure 34: QL handling for SDH traffic signals and other clock sources
on SAMO1
FUNCTIONS
CESM1 PDH clock QL override

SAMO2 SDH service unit
source by QLfix
(PETS) QL received (SETS)
or adjusted QL based or
or fixed
PDH clock QL override Priority based
source by QLfix SETS clock
(PETS) (SETS) selection
PDH clock QL override

source by QLfix
(PETS) (SETS)

PDH clock QL override QL adjusted do not use : QL = 15
source by QLfix
(PETS) (SETS)
SETG Table for QL Table interface
(MS) (MS) STM-x
ESI -1/ESI -2
active CESM1 no QL
QL override
by QLfix Output Mapping SDH Routing Front
(SETS) Table for QL Table interface
ESI -1/ESI -2
Selector B
(MS) (MS) STM-x
standby CESM1 QL received
or adjusted
QL received QL adjusted or fixed
Front QL extraction Input Mapping QL override (MS) (MS) STM-x
Front QL extraction Input Mapping QL override Table for QL Table interface
interface from SSM Table for QL by QLfix (MS) (MS) STM-x
to PDH clock
Front QL extraction Input Mapping QL override source
interface from SSM Table for QL by QLfix PDH clock
STM-x (MS) (MS) (SETS) source

SETS locked
Local
Oscillator selected
clock source
QL = 11
ESO
QL received Squelched by
or adjusted Source
or fixed
Squelch ESO for Squelch ESO
certain Sources for certain QL
QL override
by QLfix
Selector C
(ESO) ESO Front

Squelched by interface
QL ESO-2
QL override
by QLfix
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 QLfix Priority based
(ESO) ESO clock CESM1
selection
Figure 35: QL handling for SDH traffic signals and other clock sources
on SAMO2
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).
FUNCTIONS
• 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
adjusted).
• QL override, assigned to the SETS access point:
It is possible to configure the timing system so that the adjusted QL is for-
warded to the SETS selector B (configuration QL = Received) or to over-
ride the QL with a fixed value. The fixed value is configurable in the range
1 to 15 (configuration QL = <specified value>).
• Selector B, assigned to the SETS access point:
• Output mapping table, assigned to the multiplex section (MS) layer:
The output mapping table for the STM-16, STM-4 and STM-1 traffic sig-
nals maps the QL at the SETG output (QL selector B) to new QL values
(QL adjusted).
• 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 routing 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 algo-
rithm interprets the SSM in the traffic signal. If the SETS function is config-
ured 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 CESM1 unit provides two synchronization input interfaces, ESI-1 and
ESI-2. One of these two timing signals, e.g. ESI-1, is brought to the back-
plane of the FOX61x and distributed to all units plugged in the FOX61x
subrack.
The ESI timing signal of a standby CESM1 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 CESM1 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 information 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:
FUNCTIONS
The ESI clock source gets a fixed QL which is forwarded to the SETS
selector A and selector B. The fixed value is configurable in the range 1
to 15 (configuration QL = <specified value>).
• Selector A, assigned to the ESO access point:
Selector A is used for the clock source selection for the ESO-2 synchroni-
zation output interface in the “non SETS locked” mode.
clock source.
• Selector B, assigned to the SETS access point:
Selector B is used for the clock source selection for the ESO-2 synchroni-
zation output interface in the “SETS locked” mode.

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
synchronization and the ESO-2 output.
Please note:
If ESO-2 is non SETS locked, on the SAMO2 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 synchroniza-
tion 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 wether 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.4.6 External synchronization outputs (ESO)

The enabling of the ESO-1 and ESO-2 synchronization output interfaces is
configurable at AP: /ne, Configuration - ESO.
The ESO-1 output is available as a timing output of the PETS functions in
FOX61x. It is described in section PETS quality level (on page 73).
The ESO-2 output is available as a timing output of one of the SETS func-
tions in FOX61x. It is described in section SETS quality level (on page 77).
It is possible to select one of the available SDH service units in the FOX61x.
The ESO-2 output is only active if a unit is configured and when the ESO
signal status on the configured SDH unit is active.
FUNCTIONS
Please note:
When using core unit redundancy the ESO-1 and ESO-2 synchronization
output interfaces are squelched on the standby CESM1 unit.
→ The ESO-1 and ESO-2 interfaces can only be enabled on the active
CESM1 unit.
5.4.7 Service timing
5.4.7.1 Synchronous Ethernet service timing 1
Synchronous service timing means that the Ethernet signals in transmit

direction are synchronized to the FOX61x internal PETS.
Synchronous Ethernet services are selected by the configuration of the
Ethernet ports on the core units:
− CESM1.
In the non synchronous applications the transmit timing of the Ethernet sig-
nals is derived from a free running oscillator.
5.4.7.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 syn-
chronized to a common clock derived from the same PRC. The different pos-
sibilities for the NE synchronization to the network reference clock are pre-
sented in section Plesiochronous equipment timing source (PETS) (on
page 60).
5.4.7.3 Plesiochronous PDH service timing
Plesiochronous service timing means that the PDH TDM signals in receive
and transmit direction 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.
1. Synchronous Ethernet according to ITU-T G.8261 in FOX61x will be available in a future release.
FUNCTIONS
In the plesiochronous applications the PETS of the involved network ele-

ments needs not to be synchronized to the network reference timing.
COMMISSIONING
6 Commissioning
This chapter describes the configuration and the placing into operation of the
TDM services with the FOX61x.
Section General prerequisites (on page 85) lists important prerequisites that
need to be fulfilled to be able to start the commissioning of TDM services.
Section PDH cross connections (on page 86) presents commissioning exam-
ples of a P12 and a P0_nc cross connection.
Section SDH cross connections (on page 90) presents commissioning exam-
ples of a VC-4, VC-3 and VC-12 cross connection.
The section Commissioning of the PDH synchronization (on page 96)
describes the PETS synchronization configuration of the FOX61x network
element.
The section Commissioning of the SDH synchronization (on page 99)
describes the SETS synchronization configuration on the SAMO1 unit.
The section Commissioning of a synchronization network (on page 102)
gives some information how to setup a synchronization network using priority
or quality level information.
Section Connection test of readiness (on page 115) gives an overview of all
items that have to be configured for the TDM services.
6.1 General prerequisites
In order to commission TDM services on the FOX61x, you will need to fulfil
the following prerequisites:
• you need a network planning with regard to TDM connections in the
FOX61x network element and TDM signal transport in the network, i.e.
you need to have a plan about how you want to use TDM signals in both
your access network and the regional TDM network.
• you need a TDM network with equipment that supports structured and/or
unstructured P12 signals and/or SDH STM-16, STM-4 or STM-1 signals;
• you need a FOX61x that is physically built into your access network. For
installation of the FOX61x, refer to 1KHW002461 FOX615 Installation or
1KHW002462 FOX612 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 1KHW002459 FOX61x Release Notes;
• you need a management connection to your FOX61x; for details about
connecting to your FOX61x, rrefer to 1KHW002466 FOXCST Operation;
• you need a network element manager that is connected to your FOX61x
or a management interface, i.e. FOXCST;
• you need configured port and channel properties. For details about TDM
service relevant port and channel properties, refer to the section Connec-
tion termination points (on page 27). For an appropriate configuration of
port and channel properties, please refer to the user manual of the
respective service unit(s).
COMMISSIONING
6.2 PDH cross connections
6.2.1 Set-up for the PDH cross connection configuration

Figure 36 shows the set-up for the implementation of the P12 and P0_nc
cross connections.
The P12 cross connection is used for the transport of an unstructured E1
signal with 2048 kbit/s over the SDH network. The E1 signal is connected to
the port-1 of the LEDE1 unit and transported via the PDH-VC12-1 signal of
the SAMO1 unit. The E1 port is configured to the “Transparent” termination
mode and has one channel (chan-1) at the P12 layer rate. The P12 signal of
the PDH-VC12-1 is also configured to the “Transparent” termination mode
and has one channel (chan-1) at the P12 layer rate. The cross connection
has to be configured between the chan-1 of the LEDE1 port-1 and the chan-
1 of the SAMO1 PDH-VC12-1 signal.
The P0_nc cross connection is used for the transport of an analogue voice
signal (FXS) with 64 kbit/s over the SDH network. The FXS signal is con-
nected to the port-1 of the LESU1 unit and transported via the PDH-VC12-2
signal of the SAMO1 unit. On the LESU1 unit the CTP is the port-1, at the
layer rate P0_nc and has a bandwidth of 1 time slot. The P12 signal of the
PDH-VC12-2 is configured to the “PCM30C” termination mode and has one
channel (chan-1) at the P0_nc layer rate with a bandwidth of 1 time slot. The
cross connection has to be configured between the LESU1 port-1 and the
chan-1 of the SAMO1 PDH-VC12-2 signal.
The LEDE1 unit is plugged in slot 1 (unit-1), the LESU1 unit is plugged in
slot 2 (unit-2) and the SAMO1 unit is plugged in slot 20 (unit-20).
unit-1/port-1: unit-20/pdh/vc12-1/p12:
termination mode: transparent termination mode: transparent
unit-20/port-1/chan-1: unit-20/pdh/vc12-1/p12/chan-1:
CTP layer rate: P12 CTP layer rate: P12
FOX61x
port-1 SAMO1
LEDE1
E1 E1
P12 PDH
TU-12 AU-4
PBUS
STM-4
port-1 cross VC4 cross STM-4 TDM
LESU1 connect connect
FXS
PSTN PDH
unit-2/port-1: unit-20/pdh/vc12-2/p12:
CTP layer rate: P0_nc (fixed) termination mode: PCM30C
CTP n: 1 (fixed) unit-20/pdh/vc12-2/p12/chan-1:
CTP layer rate: P0_nc
CTP n: 1
Figure 36: Set-up for the PDH cross connections
6.2.2 Procedure for the PDH cross connection configuration
The FOX61x configuration example procedure for the P12 and P0_nc cross
connections as shown in Figure 36 is given in the instructions below.
COMMISSIONING
The configuration of the synchronization is explained in the section Commis-

sioning of the PDH synchronization (on page 96).
P12 cross connection Create a P12 cross connection between the channel CTP on the LEDE1
configuration port-1 and the channel CTP on the SAMO1 P12 signal.
Create the P12 CTP on the Proceed as follows:

LEDE1 port
1. Navigate to the E1 port general configuration dialogue:
 AP: /unit-1/port-1, Configuration - General.
2. Configure the termination mode:
 Termination Mode = Transparent.
3. Navigate to the E1 port channels configuration dialogue:
 AP: /unit-1/port-1, Configuration - Channels.
4. Create a P12 channel:
 Execute “Create Channel …”.
 Index = 0 (auto-assignment, take the next free index number)
 Layer Rate = P12 (predefined)
 n = 32 (predefined)
 Start Timeslot = 0 (predefined)
5. Execute “OK”
 The P12 CTP is fully configured.
Create the P12 CTP on the Proceed as follows:

SAMO1 P12 signal 1. Navigate to the P12 general configuration dialogue:
 AP: /unit-20/pdh/vc12-1/p12, Configuration - General.
 Termination Mode = Transparent
3. Navigate to the P12 channels configuration dialogue:
 AP: /unit-20/pdh/vc12-1/p12, Configuration - Channels.
 Execute “Create Channel”
 Layer Rate = P12 (predefined)
 n = 32 (predefined)
 Start Timeslot = 0 (predefined)
5. Execute “OK”
 The P12 CTP is fully configured.
P12 cross connection Proceed as follows:

1. Select the “Cross connections” view of the FOXCST.
 Click on the “Create a new Cross Connection” button:
COMMISSIONING
 The “Create Cross Connection” dialogue opens.

 Select the Layer Rate = P12.
 Select the Directionality = Bidirectional.
 Select Protected = No.
 Select the A-End Working Unit = unit-1 (LEDE1).
 Select the CTP /unit-1/port-1/chan-1.
 Select the Z-End Unit = unit-20 (SAMO1).
 Select the CTP /unit-20/pdh/vc12-1/p12/chan-1.
2. Click “Create”.
 The P12 cross connection between the two created CTPs on LEDE1/
port-1/chan-1 and SAMO1/pdh/vc12-1/p12/chan-1 is established.
Activation Proceed as follows:

1. Select the “Tree View” of the FOXCST.
2. Set the administrative state of the LEDE1 port-1 to up
AP:/unit-1/port-1, Main - Admin And Oper Status:
 Set the Administrative Status to “Up”.
3. Execute “Apply”.
4. Set the administrative state of the SAMO1 P12 signal to up
AP:/unit-20/pdh/vc12-1, Main - Admin And Oper Status:
 The resources are activated.
End of instruction
P0_nc cross connection Create a P0_nc cross connection between the FXS CTP on the LESU1 port-
configuration 1 and the channel CTP on the SAMO1 P12 signal.
Create the P0_nc CTP on the Proceed as follows:

LESU1 port 1. Navigate to the E1 port general configuration dialogue:
 AP: /unit-2/port-1, Configuration - General.
2. The LESU1 has a static CTP. No cross connection related parameters
have to be configured.
 The P0_nc CTP is fully configured.
Create the P0_nc CTP on the Proceed as follows:

SAMO1 P12 signal 1. Navigate to the P12 general configuration dialogue:
 AP: /unit-20/pdh/vc12-2/p12, Configuration - General.
 Termination Mode = PCM30C
3. Navigate to the P12 channels configuration dialogue:
 AP: /unit-20/pdh/vc12-2/p12, Configuration - Channels.
COMMISSIONING

 Execute “Create Channel”
 Layer Rate = P0_nc (predefined)
 n=1
 Start Timeslot = 1
5. Execute “OK”
 The P0_nc CTP is fully configured.
P0_nc cross connection Proceed as follows:


 Select the Layer Rate = P0_nc.
 Select the A-End Working Unit = unit-2 (LESU1).
 Select the CTP /unit-2/port-1.
 Select the CTP /unit-20/pdh/vc12-2/p12/chan-1.
 The P0_nc cross connection between the two CTPs is established.

2. Set the administrative state of the LESU1 port-1 to up
4. Set the administrative state of the SAMO1 P12 signal to up
End of instruction
COMMISSIONING
6.3 SDH cross connections
6.3.1 Set-up for the SDH cross connection configuration
Figure 37 shows the set-up for the implementation of the VC-4, VC-3 and
VC-12 cross connections.
The VC-4 cross connections are used for the through connected VC-4 traffic
between two STM-4 ports and between an STM-4 port and an internal VC-4
resource on the SAMO1 unit.
The through connected VC-4 signal is connected to the port-1 and port-2 of
the SAMO1 unit, using the first VC-4 (j-1 on both ports). The SDH port-1 is
configured to the STM-1 port mode and has one VC-4 resource (j-1) at the
VC4 layer rate. The SDH port-2 is configured to the STM-4 port mode and
has four VC-4 resources (j-1, j-2, j-3, j-4) at the VC4 layer rate. The cross
connection has to be configured between the j-1 of the SAMO1 port-1 and
the j-1 of the SAMO1 port-2.
The terminated VC-4 signal is connected to the port-2 of the SAMO1 unit,
using the second VC-4 (j-2). The internal VC-4 resource has to be created
(vc4-1) and is configured with a TUG-3 structure VC3 - VC12 - VC12. The
cross connection has to be configured between the j-2 of the SAMO1 port-2
and the internal VC-4 resource vc4-1.
The VC-3 cross connection is used for an EoS application, with an EoS
group at the Ethernet port-5. The VC-3 signal transporting the EoS traffic is
connected to the VC-3 of the internal vc4-1 (klm-100) of the SAMO1 unit.
The EoS group is created on the Ethernet port-5, and is configured with one
VC-3 member (vc3-1). The cross connection has to be configured between
the klm-100 of the internal VC-4 resource vc4-1 and the EoS VC-3 member
vc3-1.
The VC-12 cross connection is used for a P12 transport application. The P12
signal is connected to the first PDH-VC12 (vc12-1). This VC-12 signal is
transported in the internal vc4-1 (klm-211) of the SAMO1 unit. The cross
connection has to be configured between the vc12-1 and the klm-211 of the
internal VC-4 resource vc4-1.
Further examples for SDH cross connections can be found in 1KHW002476
FOX61x SAMO1 and in 1KHW002477 FOX61x SAMO2.
Please note:
VC-4, VC-3 and VC-12 cross connections are only available on a single SDH
unit (SAMO1 or SAMO2). It is not possible to create FOX61x internal cross
connections between the VC-4, VC-3 or VC-12 resources of two SDH units.
COMMISSIONING
unit-20/port-5/eos/vc3-1: unit-20/port-1/j-1:
CTP layer rate: VC3 (fixed) CTP layer rate: VC4 (fixed)
port-5
FOX61x Ethernet
EoS Ethernet
unit-20/vc4/vc4-1/klm-100: AU-4
CTP layer rate: VC3 (fixed) cross port-1
connect
STM-1
STM-1
TU-3/
LEDE1 SAMO1 TU-12 port-2 TDM
PBUS
VC4
cross
E1 E1 connect STM-4
P12 PDH STM-4
unit-20/pdh/vc12-1: unit-20/vc4/vc4-1:
CTP layer rate: VC12 (fixed) CTP layer rate: VC4 (fixed)
TUG-3 structure: VC3, VC12, VC12
unit-20/vc4/vc4-1/klm-211: unit-20/port-2/j-1,
CTP layer rate: VC12 (fixed) unit-20/port-2/j-2:
CTP layer rate: VC4 (fixed)
Figure 37: Set-up for the SDH cross connections
6.3.2 Procedure for the SDH cross connection configuration
The FOX61x configuration example procedures for the VC-4, VC-3 and VC-
12 cross connection as shown in Figure 37 is given in the tables below.
The configuration of the synchronization is explained in the section Commis-
sioning of the SDH synchronization (on page 99).
Through connected VC-4 Create a VC-4 cross connection between the SAMO1 port-1 and port-2.
cross connection
configuration
Create the VC4 CTP on the Proceed as follows:

SAMO1 port-1
1. Navigate to the SDH port physical configuration dialogue:
 AP: /unit-20/port-1, Configuration - Physical.
2. Configure the port mode:
 Port Mode = STM-1.
 The SAMO1 port has a static CTP. No cross connection related
parameters have to be configured
3. Execute “Apply”
 The VC4 CTP is fully configured.

SAMO1 port-2 1. Navigate to the SDH port physical configuration dialogue:
 The SAMO1 port has four static CTPs. No cross connection related
COMMISSIONING
 The VC4 CTPs are fully configured.
VC4 cross connection Proceed as follows:


 Select the Layer Rate = VC4.
 Select the A-End Working Unit = unit-20 (SAMO1).
 Select the CTP /unit-20/port-1/j-1.
 The VC4 cross connection between the two CTPs is established.

2. Set the administrative state of the SAMO1 port-1 to up
End of instruction
Terminated VC-4 cross Create a VC-4 cross connection between the SAMO1 port-2 and an internal
connection configuration VC-4 resource.

SAMO1 port-2 1. Navigate to the SDH port physical configuration dialogue:
 The SAMO1 port has four static CTPs. No cross connection related
 The VC4 CTPs are fully configured.
COMMISSIONING
Create the internal VC4 CTP Proceed as follows:

on the SAMO1
1. Navigate to the internal VC-4 configuration dialogue:
 AP: /unit-20/vc4, Configuration - General.
2. Create the VC-4:
 Execute “Create VC4 …”.
 VC4 Index = 0 (auto-assignment, take the next free index number)
 k-1 = VC3
 k-2 = VC12
 k-3 = VC12
3. Click “OK”.


 Select the CTP /unit-20/vc4/vc4-1.

4. Set the administrative state of the SAMO1 vc4-1 to up
AP:/unit-20/vc4/vc4-1, Main - Admin And Oper Status:
End of instruction
VC-3 cross connection Create a VC-3 cross connection between the SAMO1 EoS group of the
configuration Ethernet port-5 and the VC-3 of the internal vc4-1 resource.

SAMO1 port-5 1. Navigate to the Ethernet port physical configuration dialogue:
 AP: /unit-20/port-5, Configuration - EoS.
COMMISSIONING
2. Create the EoS group:

 Execute “Create EoS Group …”.
 Layer Rate = VC3
 Number Of Members = 1
3. Click “OK”.

on the SAMO1
 The internal VC-4 resource vc4-1 has been created before for the
terminated VC-4 cross connection. The vc4-1 has a TUG-3 structure
with the VC-3 located at klm-100.


 Select the CTP /unit-20/port-5/eos/vc3-1.
 Select the CTP /unit-20/vc4/vc4-1/klm-100.

End of instruction
VC-12 cross connection Create a VC-12 cross connection between the SAMO1 internal PDH VC-12
configuration resource vc12-1 and the VC-12 of the internal vc4-1 resource.
COMMISSIONING

SAMO1
 AP: /unit-20/pdh/vc12-1, Configuration - General.
 The SAMO1 PDH VC-12 has a static CTP. No cross connection
related parameters have to be configured

on the SAMO1
 The internal VC-4 resource vc4-1 has been created before for the
terminated VC-4 cross connection. The vc4-1 has a TUG-3 structure
with the VC-12 located at klm-211.


 Select the CTP /unit-20/pdh/vc12-1.
 Select the CTP /unit-20/vc4/vc4-1/klm-211.

2. Set the administrative state of the SAMO1 PDH VC-12 to up
End of instruction
COMMISSIONING
6.4 Commissioning of the PDH synchronization
6.4.1 Synchronous application
6.4.1.1 Prerequisites
In the synchronous TDM applications based on the TDM bus of the FOX61x
(PBUS) the incoming and outgoing TDM signals are synchronized to the ple-
siochronous equipment timing source (PETS) of the FOX61x. The PETS
clock source must be traceable to a PRC.
The P12 signal termination mode must be configured to
− Clock Master, or
− PCM30, PCM30C, or
− PCM31, PCM31C, or
− PCMnn, PCMnnC, or
− Structured, Structured with CAS, or
− G.704 Customized, or
6.4.1.2 NE synchronization configuration
In this scenario the NE timing is synchronized to a PRC derived clock via the
ESI-1 clock input port. The PETS clock source has to be configured to the
ESI-1 input. The second priority clock source is the E1 port-1 of a LEDE1
unit plugged in slot 1. The clock selection algorithm is priority based.
The ESO-1 clock output shall be active when the PETS is synchronized to
the ESI-1 clock input and shall be squelched when the PETS is synchro-
nized to another clock source.
The ESO-2 clock output shall not be used.
For the synchronization configuration, the following steps have to be per-
formed.
PETS configuration, The PETS is synchronized to the ESI-1, alternatively to the LEDE1 port-1.
synchronous application
Select the PDH clock source Proceed as follows:

1. Navigate to the PETS configuration dialogue:
 AP: /ne, Configuration - PETS.
2. Select the PDH clock source 1:
 PDH Clock Source 1 = /unit-1/port-1.
 The PDH clock source is fully configured.
Configure the PETS clock 1. Navigate to the PETS configuration dialogue:

selection  AP: /ne, Configuration - PETS.
COMMISSIONING
2. Select the parameters of ESI-1:

 Priority = 1.
 Quality Level = 13.
 Holdoff Time = 0 s.
 Wait-To-Restore Time = 30 s.
3. Select the parameters of PDH clock source 1:
 PDH Clock Source 1, Priority = 2.
4. Select the clock selection algorithm:
 Selection Algorithm = Priority.
 The PETS clock selection is fully configured.
End of instruction
ESO configuration, The ESO-1 is active if ESI-1 is selected as clock source.

synchronous application
Configure the ESO-1 clock 1. Navigate to the PETS configuration dialogue:

sources  AP: /ne, Configuration - ESO.
2. Select the valid ESO-1 clock sources:
 ESI-1 = 
 ESI-2 = 
 PDH Clock Source 1 = 
 Internal = 
 Holdover = 
 The ESO-1 clock sources are fully configured.
End of instruction
After the configuration of the PETS and ESO check the fault free operation:
PETS and ESO status Check the fault free operation of the PETS, ESI-1 and ESO-1.
check, synchronous
application
Check ESI-1 1. Navigate to the ESI-1 fault management dialogue:

 AP: /unit-11/neController/esi-1, Fault Management - Status.
2. Check the fault cause state:
 LOS = Off
Check the PDH clock source 1. Navigate to the NE fault management dialogue:
1  AP: /ne, Fault Management - Status.
 LOSP1 = Off
Check the PETS clock 1. Navigate to the NE status dialogue:

sources  AP: /ne, Status - PETS.
COMMISSIONING
2. Check the status of ESI-1:

 Selected = 
 Available = 
3. Check the status of PDH clock source 1:
 Selected = 
 Available = 
Check the PETS status 1. Navigate to the NE status dialogue:

 AP: /ne, Status - PETS.
2. Check the PETS status:
 Clock Operating = Locked
Check the ESO-1 status 1. Navigate to the NE status dialogue:

 AP: /ne, Status - ESO.
2. Check the ESO-1 status:
 Clock Output Status = Active
 The PDH timing functions are completely checked.
End of instruction
6.4.2 Plesiochronous application
6.4.2.1 Prerequisites
In the plesiochronous TDM application the incoming and outgoing TDM sig-
nals are not synchronized to the plesiochronous equipment timing source
(PETS) of the FOX61x. The PETS clock source can be free running from its
internal oscillator.
The P12 signal termination mode must be configured to
− Transparent.
6.4.2.2 NE synchronization configuration
In this scenario the NE timing is free running, i.e. the PETS is synchronized
to the internal oscillator. No external clock inputs and outputs are used.
formed.
PETS configuration, The PETS is synchronized to the ESI-1, alternatively to the LEDE1 port-1.
plesiochronous application
Configure the PETS clock 1. Navigate to the PETS configuration dialogue:

selection  AP: /ne, Configuration - PETS.
2. Select the parameters of the internal clock:
 Priority = 1.
The internal clock source has priority 7 (= lowest) by default.
COMMISSIONING

 The PETS clock selection is fully configured.
End of instruction
After the configuration of the PETS check the fault free operation:
PETS status check, Check the fault free operation of the PETS.
plesiochronous application
Check the PETS clock 1. Navigate to the NE status dialogue:

sources  AP: /ne, Status - PETS.
2. Check the status of the internal clock:
 Selected = 
 Available = 
Check the PETS status 1. Navigate to the NE status dialogue:

 AP: /ne, Status - PETS.
2. Check the PETS status:
 Clock Operating = Locked
 The PDH timing functions are completely checked.
End of instruction
6.5 Commissioning of the SDH synchronization
6.5.1 Prerequisites
All SDH ports and SDH processing on a SAMO1 unit or SAMO2 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.
To be able to use an SDH or PDH traffic signal or an external timing signal
these signals must be connected to the FOX61x network element and the
ports must be in the operational state “up”.
Please note:
COMMISSIONING
Please note:
The ESI-2 port is enabled when a clock priority is assigned to it in the SETS
or ESO configuration on a SAMO1 or SAMO2 unit.
vated.
6.5.2 SDH synchronization configuration
In this scenario the SDH timing of the SAMO1 plugged in slot 20 is synchro-
nized 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).
formed.
SETS configuration The SETS is synchronized to the STM-4 signal, alternatively to the SETS of
SAMO1 in slot 21.
SETS clock selection. Proceed as follows:

SAMO1 in slot-21
1. Navigate to the SETS configuration dialogue:
 AP: /unit-21, Configuration - SETS.
2. Select the parameters of port 1:
 Priority = 1.
 Quality Level = Received.
 The SETS clock selection is fully configured.
Select the PDH clock source Proceed as follows:

1. Navigate to the PETS configuration dialogue:
 AP: /ne, Configuration - PETS.
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)
 The PDH clock source is fully configured.

COMMISSIONING
SETS clock selection. Proceed as follows:

SAMO1 in slot-20
1. Navigate to the SETS configuration dialogue:
 AP: /unit-20, Configuration - SETS.
2. Select the parameters of port 1:
 Priority = 1.
3. Select the parameters of PDH clock source 1:
 Priority = 2.
 The SETS clock selection is fully configured.
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 1. Navigate to the SAMO1 ESO configuration dialogue:
sources  AP: /unit-20, Configuration - ESO.
2. Operate the ESO-2 in the SETS locked mode:
 ESO SETS Locked = 
(The “ESO Squelched By Source” table is applied).
3. Select the valid ESO-2 clock sources:
 Port 1, ESO Squelched = 
 PDH Clock Source 1, ESO Squelched = 
 Internal, ESO Squelched = 
 The ESO-2 clock sources are fully configured.
Configure the ESO-2 selec- 1. Navigate to the NE ESO configuration dialogue:

tion  AP: /ne, Configuration - ESO.
2. Select the unit-20 as ESO-2 clock source:
 SDH Clock Source = /unit-20.
 The ESO-2 clock selection is fully configured.
End of instruction
After the configuration of the SETS and ESO check the fault free operation:
PETS and ESO status Check the fault free operation of the SETS and ESO-2.
check
Check the PDH clock source 1. Navigate to the NE fault management dialogue:
1  AP: /ne, Fault Management - Status.

COMMISSIONING

 LOSP1 = Off
Check the SETS clock 1. Navigate to the SAMO1 status dialogue:

sources  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 1. Navigate to the SAMO1 status dialogue:

 AP: /unit-20, Status - SETS.
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 1. Navigate to the NE status dialogue:

 AP: /ne, Status - ESO.
2. Check the ESO-2 status:
 Clock Output Status = Active
 The SDH timing functions are completely checked.
End of instruction
6.6 Commissioning of a synchronization network
6.6.1 NE timing sources

TDM network elements (NE) are generally required to be synchronized to a
network reference clock. This network reference timing can be brought to the
NE using several approaches, refer to section Network reference timing dis-
tribution (on page 56).
In order to be resistant to network failures the timing source should be
applied to a NE, i.e. to a SEC G.813, via at least two independent paths.

COMMISSIONING
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 38: Synchronization via two independent paths
6.6.2 NE timing source selection

PDH signals used as timing source in FOX61x are configured at the AP:/ne,
Configuration - PETS. PDH signals support priority based and quality level
(QL) based timing source selection. Note that the quality level information in
a P12 signal is carried in time slot 0 according to ITU-T G.704.
SDH signals used as timing source in FOX61x are configured on the SAMO1
or SAMO2 units at the AP:/unit-x, Configuration - SETS. SDH signals in
FOX61x support priority based and quality level based timing source selec-
tion. Note that the quality level information in a SDH signal is carried in the
S1 byte of the multiplex section overhead.
6.6.3 Synchronization networks using priority

When using the priority for the selection of a timing source the (possibly
available) quality level information will not be evaluated as selection criterion.
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 loss of signal defect at the cor-
responding interface.
From the available timing sources the NE autonomously selects the timing
source with the highest priority.
Synchronization networks using only the priority must be set up as tree net-
works. No ring or meshed networks are allowed.

COMMISSIONING
6.6.4 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 best quality. If two sources have the same QL the configured
priority decides which timing source will be selected.
As shown in Figure 38 above in a ring network also the timing signals are
transported in the ring. There is a risk to have a timing 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 struc-
ture. The logical tree must be maintained 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 behaviour.
To provide a logical tree for the timing distribution the following rules apply:
• The QL in direction of the selected timing source is set to “Do Not Use”.
The synchronization usability can be configured in the SDH routing table
at the AP:
− SAMO1: /unit-x/port-y, Configuration - MS.
− SAMO2: /unit-x/sdh/sdh-y, Configuration - MS.
SETS Clock Selection
Source Priority QL
port-1 1 received
Port-1 Routing Table port-2 2 received Port-2 Routing Table
Source Usability Source Usability
port-1 do not use port-1 can be used
port-2 can be used port-2 do not use
NE1
port-1 port-2
Selected Clock
do not use : QL = 15 Source: port-1

Source Priority QL
port-1 1 received
Port-1 Routing Table Port-2 Routing Table
port-2 2 received
NE1
port-1 port-2
Selected Clock
can be used : QL = unchanged Source: port-2 do not use : QL = 15
Figure 39: QL setting to “Do Not Use”

COMMISSIONING
The upper example in Figure 39 selects port-1 as timing source. Corre-

spondingly 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.
• With a single timing source in the 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 40: 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 inter-
nal timing sources. There will be two timing islands, NE2 to NE4 and NE5
to NE8.
• With two or more timing sources in the network the incoming timing
sources must be given a fixed quality level. At the ports of the NE provid-
ing the timing source towards the subtended NEs the incoming fixed tim-
ing source quality level must be mapped to “Do Not Use”, i.e. to QL=15.

COMMISSIONING
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 41: 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 synchronized with NE1. The timing loop with QL=1 is
interrupted at the incoming ports of NE1 through 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 syn-
chronized 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 internal 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 42: QL mapping of selected and internal timing sources to “Do

Not Use”

COMMISSIONING
6.6.5 Example of an SDH ring with one external timing source, QL

based
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.
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 43, 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 internal oscillator as timing source.

COMMISSIONING

Source Priority QL
ESI 1 1
port-1 disabled received
port-2 disabled received ESI
internal 10 11

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 Routing 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
port-2 2 received port-2 2 received
Selected Clock Selected Clock
Source: port-1 internal 10 11 Source : port-1
QL: 1 QL: 1
port-2 port-1
internal can be used

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

Source Priority QL
port-1 1 received active timing path
port-2 2 received standby timing path
Figure 43: SDH ring, one source, no failure

COMMISSIONING
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
Source: port-1 internal 10 11 Source : port-1
QL: 11 QL: 11
port-2 port-1

Source : port-1
QL: 11

Source Priority QL
Figure 44: SDH ring, one source, ESI at NE1 failed

COMMISSIONING
If NE1 fails NE2 switches to the internal timing source and becomes the tim-
ing 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 45: SDH ring, one source, NE1 failed

COMMISSIONING
6.6.6 Example of a SDH ring with two external timing sources, QL

based
NE1 is the timing master of the SDH ring, i.e. it provides the timing from the
ESI input to the subtended NEs. ESI is given a fixed QL=1. Port-1 and port-2
of NE1 map the incoming QL=1 and QL=11 to QL=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
port-1 internal can be used
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
Selected Clock port-2 2 received port-2 2 received Selected Clock
Source: port-1 Source : port-1
QL: 1 QL: 1
port-2 port-1

Source : port-1
QL: 1
Port-1 Input Mapping Table Port-2 Input Mapping Table
2 15 2 15

Source Priority QL
ESI
ESI 1 2 active timing path
port-2 3 received
Figure 46: SDH ring, two sources, no failure

COMMISSIONING
If the ESI timing source at NE1 fails NE3 selects its ESI timing source and
becomes the timing master. ESI is given a fixed QL=2. Port-1 and port-2 of
NE3 map the incoming QL=2 to QL=15.
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
QL: 2
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 47: SDH ring, two sources, ESI at NE1 failed

COMMISSIONING
If there is in addition a link break between NE3 and NE4 the timing distribu-
tion 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
QL: 2
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 48: SDH ring, two sources, ESI at NE1 failed and link failure
between NE3 and NE4

COMMISSIONING
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
QL: 11
2 15 2 15

Source Priority QL
ESI
port-2 3 received
Figure 49: SDH ring, two sources, ESI at NE1 and NE3 failed and link
failure between NE3 and NE4

COMMISSIONING
6.7 Connection test of readiness
The requested TDM services are only working if all involved parts of the
FOX61x are in a fault free state:
• The administrative and operational states have to be up on the
− used ports,
− logports
of the service units.
• The PETS must be synchronized to the applied synchronization signal in
the synchronous applications.
• The SETS must be synchronized to the applied synchronization signal.
• No fault is reported in FOXCST.
Due to the fact that TDM connections in the FOX61x are done on network
element level, the NE is aware of the required resources and will inhibit any
connection configuration attempt of incompatible CTPs, ports or channels.
In contrast to the connection configuration it is not possible for the NE to
check if the configured connections fit the application. It is therefore up to the
operator to compare the dynamic CTP parameters and the connection
parameters with the planning documents and correct any misconfigurations if
required.

COMMISSIONING

OPERATION
7 Operation
This section describes the operation functions of the TDM services with the
FOX61x. You will find the following information:
• A description of the status and diagnostic parameters of the TDM ser-
vices and the synchronization functions (section Status and diagnostics
(on page 117)).
• A description of the fault management parameters (section Fault man-
agement (on page 119)).
• TDM service debugging information (section Possible faults and related
debugging (on page 119)).
Please note:
The operation functions described in this section assume a correctly config-
ured and operational TDM service in the FOX61x.
7.1 Status and diagnostics
7.1.1 Connection and CTP status

The connections with their static and dynamic CTPs are visible in tabular
form in the “Cross Connection” tab. In addition the “Tree View” tab provides
the same information for the selected AP
− which is a TDM connection termination point (CTP), or
− which has subordinate APs which are TDM CTPs.
For further information please refer to section TDM cross connections (on
page 142).
The detailed CTP configuration with the used time slots in a structured P12
signal and the assigned connections is visible from the port, link or channel
configuration in the “Tree View” tab. The detailed CTP status with the remote
CTP information and the protection switching management is available from
the port, link or channel status in the “Tree View” tab. Please refer to Table
5: Static CTPs (on page 31) and to Table 6: Dynamic CTPs (on page 34) for
a list of all available CTP MO addresses.

OPERATION
7.1.2 Synchronization status

7.1.2.1 PETS status
The availability and selection of the PETS clock sources can be checked
with the PETS status function: AP: /ne, Status - PETS.
The same dialogue provides the PETS clock operating status. Refer to sec-
tion PETS clock operation modes (on page 62).
With the PETS clock operation type selection the PETS clock operation sta-
tus 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. “Inter-
nal” is the selected PETS clock source.
• 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 Selection”.
7.1.2.2 SETS status
The availability and selection of the SETS clock sources can be checked
with the SETS status function on the SAMO1 or SAMO2 unit: AP: /unit-x,
Status - SETS.
The same dialogue provides the SETS clock operating status. Refer to sec-
tion SETS clock operation modes (on page 67).
With the SETS clock operation type selection the SETS clock operation sta-
tus 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. “Holdover” (SAMO1) or “Internal” (SAMO2) is the selected
SETS clock source.
• Forced Free Run: The SETS is synchronized to the internal clock oscilla-
tor. “Holdover” (SAMO1) or “Internal” (SAMO2) is the selected SETS
clock source.
Please note:
An alarm MFA (Maintenance Function Active) is set on the SAMO1 or
SAMO2 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 Selection”.

OPERATION
The SETS clock source selection can be controlled for maintenance pur-
poses. The manual switch and lockout commands override the automatic
clock source selection.
• Lockout:
Any of the available clock sources can be locked out from being selected
by an automatic, forced or manual switch request.
• 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>” (SAMO2) 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 available. The source not available has been disabled or is
failed or in WTR state.
7.1.2.3 ESO status
The status of the ESO-1 and ESO-2 synchronization output signals can be
checked with the ESO status function: AP: /ne, Status - ESO.
Please refer to section AP: / ne, Status - ESO (on page 140) for a descrip-
tion of the available status parameters.
7.2 Fault management
The generic fault management aspects of the FOX61x are handled in the
FOXCST user manual. Please refer to 1KHW002466 FOXCST Operation.
Failure reporting for the TDM connection services is not available.
For the PDH synchronization fault management please refer to
1KHW002464 FOX61x System Description.
For the SDH synchronization fault management please refer to
1KHW002476 FOX61x SAMO1 and 1KHW002477 FOX61x SAMO2.
7.3 Possible faults and related debugging
If a TDM application has been created and configured but does not work,
please check the following hints to resolve the problem.
7.3.1 FOX61x active failures

• Check the FOXCST “Alarms” tab:
The active alarms window lists in a table all active failures of the whole
network element.

OPERATION
• The same information as with the FOXCST “Alarms” tab can be displayed
with the network element fault management at the AP: /ne:
The “Active Alarms” tab of the “Overview” management function lists in a
table all active failures of the whole network element.
You find the failure description and the possible failure causes in the cor-
responding unit user manual or application user guide.
• If there are no active failures displayed in the resources used for the ser-
vice or application that is not performing as required, you need to check
for other possible causes. Please refer to the sections below.
7.3.2 Unit not available (UNAV)

A reason for a service or application not performing as required can be a unit
that is not available, or a unit that is not assigned.
• All units required for the service should be in the “OK” state:
The FOXCST “Tree View” tab shows the AP tree with all units.
• If a unit is in the “Plugged” state, you have to assign the unit under the
AP: /unit-x, Main - Equipment or using the context menu of the unit:
• A valid embedded software (ESW) for the unit has to be downloaded and
configured under the AP: /unit-x, Main - Software. For details about the
ESW installation refer to 1KHW002466 FOXCST Operation.
• Configure the services and synchronization as described in section Com-
missioning (on page 85).
7.3.3 Port or logport down
• If you have not set the administrative state of a port or logport to “Up”,
the corresponding MO will be fault free, but a TDM service using this port
or logport will not perform since the resources required for the service to
work are inactive.
Check that the all the ports and logports are in the administrative status
“Up” using the MO context menu as shown above or selecting the Admin
And Oper Status dialogue, e.g. AP: /unit-x/port-y, Main - Admin And Oper
Status, or selecting the parent AP in the FOXCST “Commissioning” tab:
Set the administrative status to “Up”.
• “”.Check that all the ports and logports are in the operational status “Up”
by selecting the Admin And Oper Status dialogue, e.g. AP: /unit-x/port-y,
Main - Admin And Oper Status, or by selecting the parent AP in the
FOXCST “Commissioning” tab:
If the operational state is “Down” make sure
− that the failure status of the MO has no active defect (e.g. LOS or
AIS).
• Check that the port or logport is configured correctly according to the
application (e.g. Transparent):
• Check that the TDM connection is configured correctly according to the
application.
7.3.4 TDM service not working

• Check that the TDM connection is configured correctly according to the
application.
• Check the configuration parameters of the TDM connections under the
FOXCST “Cross Connections” tab:

OPERATION
Make sure that all configuration parameters are as required.

• Check the configuration parameters of the dynamic CTPs under the
channel APs: AP: /unit-x/…/chan-z.
Make sure that all configuration parameters are as required.

OPERATION

FOXCST REFERENCE
8 FOXCST reference
This section gives a complete reference of the managed objects, properties,
and commands of the TDM Services service unit as far as these are not cov-
ered in the generic descriptions in refer to 1KHW002466 FOXCST Opera-
tion.
In this section, you will find the following information:
• An introduction (section Introduction (on page 123)),
• Synchronization parameters (sections AP: / ne, Status - PETS (on
page 138), AP: / ne, Configuration - ESO (on page 134), AP: / ne, Status
- ESO (on page 140), AP: / ne, Status - PETS (on page 138) and AP: /
unit-11 / neController / esi-z (on page 141)),
• TDM connections management (section TDM cross connections (on
page 142).
For a description about how to configure and bring into operation the TDM
connections please refer to the sections Commissioning (on page 85) and
Operation (on page 117).
For a description of the SDH synchronization managed objects, properties,
and commands please rrefer to 1KHW002476 FOX61x SAMO1 and
1KHW002477 FOX61x SAMO2.
For a description of the CTP managed objects, properties, and commands
please refer to the corresponding unit user manuals, where the CTPs are
located.
8.1 Introduction
Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the spe-
cific parts of the TDM Services.
For each of the managed objects, properties and commands, the GUI “Tree
Views” are given.
This reference section comprises the management functions:
• Overview,
• Main,
• Configuration,
• Fault Management,
• Performance Management, and
• Status.
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in
accordance with the APs in the FOXCST AP tree and the availability of the
management functions of each AP.
In the tables of the sections below, the parameter default values for proper-
ties are underlined.

FOXCST REFERENCE
Please note:
For better legibility of numbers in this user guide, 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 configura-
tions or data that may not correspond to the view you see when managing
your FOX61x equipment.
8.1.1 MOM for the PETS synchronization
Figure 50 shows the AP tree and the NE management functions for the man-
agement of the PDH synchronization. This MOM allows the management of
the NE timing source (PETS) and of the synchronization input ports and out-
put ports.
With these MOs, the following functions are managed:
• 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 configuration of the clock source priorities and quality levels.
Configuration of the squelch parameters “Squelched By Source” and
“Squelched By QL”.
• esi-z:
Fault management of the external synchronization inputs ESI-1 and ESI-
2.
• P12 (the P12 layer can be an E1 port, an SHDSL trunk or a P12 signal
transported over SDH):
Configuration of the synchronization status message (SSM) or synchroni-
zation status indication (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 time slot 0.
→ This provides compatibility with the STIC1 implementation in FOX51x.

FOXCST REFERENCE
<ap >
FOX61x
<mf> <mf> <mf>

Configuration Status Fault Management
<attribute> <attribute> <attribute> <attribute> <attribute>

PETS ESO ESO PETS PETS
<ap >
unit-11: CESM1
1 <ap>
neController
2 <ap>
esi-z
<ap >
unit-x: LEDE1
<ap>
port-y
<mf> <mf>
<ap > Configuration Status
unit-x: DATI1
<attribute> <attribute>
<ap> Synchronization QL
logports
<ap>
logport- y
<ap >
unit-x: SAMO1
unit-x: SAMO2 <ap >
trunk
<ap> <mf> <mf>

pdh Configuration Status
<ap> <attribute> <attribute>

vc12-y Synchronization QL
<ap >
p12
<mf> <mf>
Configuration Status
Synchronization QL
Figure 50: PETS synchronization access point tree

FOXCST REFERENCE
8.1.2 MOM for the SETS synchronization
Figure 51 shows the AP tree and the NE management functions for the man-
agement of the SDH synchronization. This MOM allows the management of
the SETS and of the synchronization input ports and output ports.
With these MOs, the following functions are managed:
• 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 SDH unit for the external synchronization output ESO-2.
Selection of the clock sources for the ESO and configuration of the clock
source priorities and quality levels. Configuration of the squelch parame-
ters “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 SAMO1 unit.

FOXCST REFERENCE
<ap >
FOX61x
<mf> <mf>
Configuration Status
1 ...2 1 ...2
ESO ESO
<ap >
unit-x: SAMO1, or
unit-x: SAMO2
<mf>
<mf> <mf> <mf>
Performance
Configuration Status Fault Management
Management
<attribute> <attribute> <attribute> <attribute>

SETS, ESO SETS, ESO SETS, ESO SETS , ESO
4 <ap>
SAMO1: port-y
<mf>
Configuration
<attribute>
MS
1 <ap>
SAMO2: sdh
4 or 8 <ap>
sdh-y
<mf>
Configuration
<attribute>
MS
Figure 51: SETS synchronization access point tree

FOXCST REFERENCE
8.2 AP: / ne
Please note:
The Access Point (AP) named “ne” in the AP tree of the FOXCST shows the
additional information “FOX615” or “FOX612”. For reasons of simplicity and
clarity, this additional information is not shown in the following sections since
it is not used while navigating in the FOXCST.
Please note:
In the FOXCST dialogue windows the “ne” AP is identified with a forward
slash “/”. In the following sections the identifier “/” is used instead of the iden-
tifier “ne”.
8.2.1 AP: / ne, Configuration

8.2.1.1 AP: / ne, Configuration - PETS
This 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 automatic synchronization source selection
algorithm.
Table 19: AP: / ne, Configuration - PETS

Operation Name Parameter Name Range Descriptions / Details
PDH Clock Sources PDH Clock Source 1 <empty> No reference port selected as clock source 1, i.e.
this source is not used in the selection algorithm.
<MO address> Select a port from the list of available ports

FOXCST REFERENCE
Table 19: AP: / ne, Configuration - PETS (continued)

PDH Clock Source 2 <empty> No reference port selected as clock source 2, i.e.
<MO address> Select a port from the list of available ports.

FOXCST REFERENCE

PETS Clock Selec- Source ESI-1 Available timing sources for the PETS synchroni-
tion ESI-2 sation.
These values are read-only.
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
Internal
Priority 1…7 The priority of a timing source is used as a selec-
tion criterion if the selection algorithm is config-
ured to “priority based” (see below).
1 is the highest priority, 7 is the lowest priority.
It is possible to assign the same priority 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
SETS synchronisation.
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 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
standardised.
The ESI-1 and ESI-2 timing sources have a
default quality level of 13.
The internal timing source has a 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 PETS tim-
ing 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 (synchro-
nisation status message) or SSI (synchronisation
status indication).
Timing sources not providing the SSM or SSI
only have an assigned quality level
Holdoff Time 0 … 60 s During the holdoff time the timing source selec-
step 0.1 s tion 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.
The WTR timer is reset when the timing source
is in a failure state and starts when the timing
source becomes fault free.
The internal timing source has a default wait-to-
restore time of 0 s.

FOXCST REFERENCE

Selection Algorithm Priority Select the timing sources according to the
assigned priorities.
This selection algorithm disregards the quality
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:
The list contents for the PDH Clock Sources depend on the configuration
made on the respective units.
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.

FOXCST REFERENCE
8.2.1.2 AP: / ne, Configuration - ESO

FOXCST REFERENCE
Table 20: AP: / ne, Configuration - PETS

Operation Name Parameter Name Range Description / Details
PDH Clock Sources PDH Clock Source 1 <MO address> The managed object address of the four
PDH Clock Source 2 <MO address> 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 synchronisation output
ESO-1 on the CESM1 unit is synchro-
nised to the PETS function.
 The external synchronisation output
ESO-1 on the CESM1 unit is synchro-
nised to the selected ESO clock source.
ESO-1 Clock Selection Source ESI-1 Note that the ESO Clock Selection
ESI-2 parameters are only applicable for the
non PETS locked mode. Refer to the
PDH Clock Source 1 parameter above.
PDH Clock Source 2 Available timing sources for the ESO-1
PDH Clock Source 3 synchronisation.
PDH Clock Source 4
Internal
Priority 1…7 The priority of a timing source is used as
a selection criterion if the selection algo-
rithm is configured to “priority based” (see
below).
1 is the highest priority, 7 is the lowest
priority.
It is possible to assign the same priority 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 synchronisation.

FOXCST REFERENCE

QL 1 … 14 The quality level QL of a timing source is
used as a selection criterion if the selec-
tion 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 pro-
vide no QL or if you want to fix the QL for
a timing source.
Note that the use of some of the QL val-
ues is standardised.
The ESI-1 and ESI-2 timing sources have
a default quality level of 13.
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 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 (synchronisation status message).
Timing sources not providing the SSM
only have an assigned quality level.
Holdoff Time 0 … 60 s During the holdoff time the timing source
step 0.1 s selection process performs no switcho-
ver 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.
The WTR timer is reset when the timing
source is in a failure state and starts
when the timing source becomes fault
free.
wait to restore time of 0 s.
Selection Algorithm Priority Select the timing sources in the non
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.

FOXCST REFERENCE

ESO-1 Squelched By Source ESI-1 Note that the ESO-1 Squelched By
Source ESI-2 Source parameters are only applicable
for the PETS locked mode. Refer to the
PDH Clock Source 1 parameter above.
PDH Clock Source 2 Available timing sources for the ESO-1
PDH Clock Source 3 synchronisation.
PDH Clock Source 4
Internal
ESO-1 Squelched  The ESO-1 output on the CESM1 unit is
squelched, i.e. disabled, if the corre-
sponding source is selected.
 The ESO-1 output on the CESM1 unit is
active, i.e. enabled, if the corresponding
source is selected.
ESO-1 Squelched By QL QL 1 … 15 Note that the ESO Squelched By QL
parameters are applicable for the PETS
locked and the non SETS locked
modes.
Quality levels of the timing sources for the
ESO-1 synchronisation.
ESO-1 Squelched  The ESO-1 output on the CESM1 unit is
squelched for the selected QL.
 The ESO-1 output on the CESM1 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 pro-
viding the ESO-2 clock.
8.2.2 AP: / ne, Fault Management

For the a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to 1KHW002466 FOXCST Operation.
The fault causes of the AP: / ne are listed in refer to 1KHW002464 FOX61x
System Description.

FOXCST REFERENCE
8.2.3 AP: / ne, Status
8.2.3.1 AP: / ne, Status - PETS
“Clear WTR” dialogue:
Table 21: AP: / ne, Status - PETS

Source Status Source ESI-1 List of all timing sources.
ESI-2
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
Internal
Priority 1…7 Configured priority value of the timing source.
Disabled
QL 1 … 14 Adjusted or received quality level of the timing
Do Not Use source, as it is used by the selection algorithm in
the PETS selector B.
Unknown The timing source has the configured priority =
“disabled” and QL = “received”.

FOXCST REFERENCE
Table 21: AP: / ne, Status - PETS (continued)

Status Not Supervised Disposability of the timing source.
Available
Holdoff
Failed
Wait-To-Restore
Clock Status Selection Algorithm Priority Display of the configured selection algorithm for
QL 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:
Locked
- Locked: Locked to a traffic signal
Holdover - Free-running: PETS synchronised to the inter-
nal oscillator.
- Holdover: PETS keeps the acquired frequency
from a traffic signal which has been lost.
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 automatic
selection.
A forced clock operation state activates the
maintenance function active (MFA) alarm.
Clear WTR … Open the FOXCST dialogue 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 qual-
ity level timing source.
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
The LOCKED LED on the control unit CESM1 front indicates if the NE is
locked to a synchronization source:
• green: locked
• dark: not locked
XXXXx R1B
ANR_37900374
UNIT TRAFFIC
ACTIVE LOCKED
Figure 52: LEDs on the CESM1 front

FOXCST REFERENCE
Please note:
The SETS status is available on the SDH service unit. Please refer to
1KHW002476 FOX61x SAMO1 or refer to for further information.
8.2.3.2 AP: / ne, Status - ESO
“Clear ESO-1 WTR” dialogue:
Table 22: AP: / ne, Status - ESO

ESO-1 Source Sta- Source ESI-1 List of all timing sources.
tus ESI-2
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
Internal
Priority 1…7 Configured priority value of the timing source.
Disabled
QL 1 … 14 Adjusted or received quality level of the timing
Do Not Use source, as it is used by the selection algorithm in
the PETS selector A.
Unknown The timing source has the configured priority =
“disabled” and QL = “received”.

FOXCST REFERENCE
Table 22: AP: / ne, Status - ESO (continued)

Status Not Supervised Disposability of the timing source.
Available
Holdoff
Failed
Wait-To-Restore
ESO-1 Clock Status Selection Algorithm Priority Display of the configured selection algorithm for
QL 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
Free Running ESO-1:
- Locked: Locked to the selected timing source
Holdover
- Free-running: Synchronised to the internal
Squelched oscillator.
- Holdover: ESO-1 keeps the acquired frequency
from a traffic signal which has been lost.
- Squelched: ESO-1 is disabled when all clock
sources are disabled.
Clear ESO-1 WTR Open the FOXCST dialogue to select a timing
… source.
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 qual-
ity level timing source.
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESO-2 Clock Output Status Active Indicates that ESO-2 provides its timing signal.
Squelched Indicates that ESO-2 can not provide its timing
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 sub-
rack.
8.3 AP: / unit-11 / neController / esi-z
For a description of the esi-z related management functions, please refer to

1KHW002469 FOX61x CESM1.

FOXCST REFERENCE
8.4 TDM cross connections
8.4.1 Cross connection management

8.4.1.1 Management access
TDM cross connections can be created, displayed and deleted at several

places in the FOXCST:
• “Cross Connection” tab:
The “Cross Connection” tab provides the TDM cross connection manage-
ment for the whole FOX61x network element.
The view of existing cross connections can be filtered for the layer rate
and for a text string.
• “Tree View” tab:
The “Tree View” tab provides the TDM cross connection management for
the selected AP
− which is a TDM connection termination point (CTP), or
− which has subordinate APs which are TDM CTPs.
The view of existing cross connections of this AP can be filtered for the
layer rate and for the subordinate APs.
8.4.1.2 Command buttons
TDM cross connections are managed with the following FOXCST buttons:
• Create a new TDM connection:
When clicking on this button, the FOXCST launches the dialogue window
to create one or several TDM connections. Refer to section Create a new
TDM connection (on page 147).
• Create a new TDM connection using the Connection Wizard:
When clicking on this button, the FOXCST launches the dialogue suite to
create one or several TDM connections. Refer to section Create a new
TDM connection (on page 147).

FOXCST REFERENCE
• Delete a TDM connection:
When clicking on this button, all selected cross connections will be

deleted. Refer to section Delete a TDM connection (on page 154).
• Refresh the list of TDM connections:
When clicking on this button, the TDM cross connection table is

refreshed.
• Filter for the layer rate:
All TDM cross connections with a layer rate where the layer rate button is
dark shaded are displayed in the TDM cross connection table. When
clicking on a layer rate button, the button becomes light shaded and the
corresponding TDM cross connections are hidden.
Per default all TDM cross connections are displayed.
• Filter for a text string:
All TDM cross connections where the entered text string is contained in
one of the
− Label 1,
− Label 2,
− Z-End,
− A-End Working, and
− A-End Protecting
columns are displayed in the TDM cross connection table.
With an empty text string all TDM cross connections are displayed.
• Clear the text string:
The text string filter is removed.

• Filter for the subordinate access points (APs):
When this button is dark shaded, all TDM cross connections of subordi-
nate APs are displayed in the TDM cross connection table. When clicking
on the subordinate access point button, the button becomes light shaded
and the corresponding TDM cross connections are hidden.
Per default all subordinate TDM cross connections are displayed.
Note that this button is only available in the “Tree View”.

FOXCST REFERENCE
8.4.1.3 TDM cross connection table
The TDM cross connection table shows the created cross connections.
Existing cross connections cannot be modified, except the label 1 and the
label 2.
Table 23: TDM cross connection table

Cross connection ID 1 … 65‘535 Connection identifier.
table Layer P0_nc Connection layer rate.
P12
VC12
VC3
VC4
Dir Bidirectional connection.
Unidirectional connection.
N 0 … 2 characters Number of time slots when the layer rate is P0_nc.

The string is empty when the layer rate is not P0_nc.
Label 1 0 … 32 characters User defined connection label 1.
To modify a label 1 refer to section TDM cross connec-
tion details (on page 145).
Z-End <MO address> Address string of the connections Z-End CTP (e.g. /unit-
9/port-1).
A-End Working <MO address> Address string of the connections A-End Working CTP
(e.g. /unit-19/port-1).
A-End Protecting <MO address> Address string of the connections A-End Protecting
CTP (e.g. /unit-20/port-1).
The string is empty when the connection is unprotected.
To modify a label 2 refer to section TDM cross connec-
tion details (on page 145).

FOXCST REFERENCE
8.4.1.4 TDM cross connection details
When selecting a cross connection in the TDM cross connection table of the
“Cross Connections” view, the cross connections detail parameters are dis-
played in a window section right to the cross connection table.
When selecting more than one cross connection in the TDM cross connec-
tion table, the status displays the parameters of the topmost selected table
entry.
Table 24: TDM cross connection details

Cross connection Title <character string> The title shows the configured label 1 of the con-
details nection.
If no label 1 is configured the connections Z-End
and A-End CTPs are shown.
The label 1 can be modified.
The label 2 can be modified.
Layer P0_nc Connection layer rate.
P12
VC12
VC3
VC4
Directionality Bidirectional Bidirectional connection.
Unidirectional Unidirectional connection.
Protected Yes Protected connection.
No Unprotected connection.

FOXCST REFERENCE
Table 24: TDM cross connection details (continued)

Z-End Coloured alarm icon The alarm icon shows the colour of the most
severe alarm of this CTP.
<MO address> Managed object address of the Z-End CTP.
State Failure state of the signal transmitted by the Z-
End towards the A-End:
OK = no failure.
SF = Signal Fail.
CAS AIS = CAS is an all ‘1’ signal.
SD = Signal Degraded.
Not Available = The status of the signal is not
available.
A-End Coloured alarm icon The alarm icon shows the colour of the most
<MO address> Managed object address of the A-End Working
CTP.
State Failure state of the signal transmitted by the A-
End towards the Z-End:
OK = no failure.
SF = Signal Fail.
available.
A-End Prot. Coloured alarm icon The alarm icon shows the colour of the most
<MO address> Managed object address of the A-End Protecting
CTP.
State Failure state of the signal transmitted by the A-
End Prot. towards the Z-End:
OK = no failure.
SF = Signal Fail.
available.
SNCP Configuration Revertive Protection  Enable revertive protection switching.
Switching  The Z-End will preferably select the working A-
End.
This parameter can be modified.
CAS AIS Supervi-  Use CAS AIS as protection switching criterion.
sion  This parameter can be modified.
Switch-Over Log-  Enable the logging of the protection switch-over

ging  events.
This parameter can be modified.
Active Trail Working The trail from the A-End Working remote CTP
has been selected.
Protecting The trail from the A-End Protecting remote CTP
has been selected.
Not Available There is no active trail.

FOXCST REFERENCE
Table 24: TDM cross connection details (continued)

External Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the A-End
Working remote CTP.
Force Protecting Force the selector to use the trail from the A-End
Protecting remote CTP.
Manual Working Prefer the trail from the A-End Working remote
CTP. Use this trail only if the fault status is not
worse than the fault status of the protecting trail.
Manual Protecting Prefer the trail from the A-End Protecting remote
CTP. Use this trail only if the fault status is not
worse than the fault status of the working trail.
Please note:
The “SNCP Configuration” part is only available for protected TDM cross
connections. The same parameters are also available with the CTPs config-
uration and status management functions.
8.4.1.5 Affected traffic in the FOXCST “Alarms” view
When selecting an alarm in the alarm list of the FOXCST “Alarms” view, the
alarm status details displayed in a window section right to the alarm table
shows the probably affected cross connections.
8.4.2 Create a new TDM connection

TDM cross connections can only be created between existing TDM CTPs.
→ Create the required CTPs before creating the TDM connection. Please
refer to section Dynamic CTP (on page 33).

The creation of a protected cross connection with the working A-End and/or
protecting A-End CTP located on the
- LESU1 unit,
- OPIC1 unit,

FOXCST REFERENCE
- TEPI1 unit,
- LEXI1 unit, or
- LECO1 unit
is inhibited by the FOXCST.
→ The working A-End and protecting A-End of a protected TDM cross
connection must be located on a TDM transport unit.
Click on the “Create a new TDM connection” button and FOXCST opens the
first GUI window of the dialogue suite. Enter the required connection param-
eters:
Table 25: Create Cross Connections

Layer Rate P0_nc Connection layer rate.
P12
VC12
VC3
VC4
Directionality Bidirectional Connection directionality.
Unidirectional
Protected Yes Connection protection.
No The A-End Protecting field of the “Create Cross
Connection” dialogue is only enabled if the “Pro-
tected” parameter is set to “Yes”.

FOXCST REFERENCE
Table 25: Create Cross Connections (continued)

A-End Working Unit All Display all CTPs of all units and the ne with the
configured layer rate which can be the A-End of
a connection.
ne Display all CTPs of the ne with the configured
layer rate which can be the A-End of a connec-
tion.
A CTP at the ne can e.g. be a ppp-x TDM inter-
face of the management network.
unit-x (<unit type>) Display all CTPs of the selected unit with the
a connection.
<empty> Display no CTPs.
n 1 … 31 Number of time slots of a P0_nc CTP.
<empty> The CTP has another layer rate than P0_nc.
CTP <MO address> Click the table row of the CTP to be connected.
More than one CTP can be selected by pressing
the “CTRL” or the “SHIFT” button while clicking
another table row.
A-End Protecting Unit All Display all CTPs of all units and the ne with the
a connection.
layer rate which can be the A-End of a connec-
tion.
a connection.
another table row.

FOXCST REFERENCE
Table 25: Create Cross Connections (continued)

Z-End Unit All Display all CTPs of all units and the ne with the
configured layer rate which can be the Z-End of
a connection.
layer rate which can be the Z-End of a connec-
tion.
configured layer rate which can be the Z-End of
a connection.
another table row.
Create Create the cross connections between all
selected A-End and Z-End CTPs.
Note:
- The number of selected CTPs in the A-End
Working, A-End Protecting and Z-End tables
must match.
- The number of time slots of selected P0_nc
CTPs must match.
Refresh Refresh the view of the “Create Cross Connec-
tion” dialogue.
Close Close the “Create Cross Connection” dialogue
without creating any cross connections.
8.4.3 Create a new TDM connection using the connection wizard

TDM cross connections can only be created between existing TDM CTPs.
→ Create the required CTPs before creating the TDM connection. Please
refer to section Dynamic CTP (on page 33).

The creation of a protected cross connection with the working A-End and/or
protecting A-End CTP located on the
- LESU1 unit,
- OPIC1 unit,
- TEPI1 unit,

FOXCST REFERENCE
- LEXI1 unit, or
- LECO1 unit
is inhibited by the FOXCST.
→ The working A-End and protecting A-End of a protected TDM cross
connection must be located on a TDM transport unit.
Click on the “Connection Wizard” button and FOXCST opens the first GUI
window of the dialogue suite. Enter the required connection parameters:
Table 26: Create a new TDM connection, Parameters

Parameters Layer Rate P0_nc Connection layer rate.
P12
VC12
VC3
VC4
Directionality Bidirectional Connection directionality.
Unidirectional
Protected Yes Connection protection.
No
Number 0 … 10’000 Number of cross connections to be created.
Please note:
When creating a TDM cross connection with the “Connection Wizard” from
the “Tree View” tab the parameter “Layer Rate” is predefined according to
the layer rate property
- of the current AP address if this AP is a CTP, or otherwise
- of the first available subordinate CTP.

FOXCST REFERENCE

When the number of TDM connections to be created is 0 or higher than the
available number of CTPs that can be connected, the TDM connection crea-
tion process cannot be terminated successfully.
→ Select the number of TDM connections to be created according to the
available number of CTPs to be created.
Click on the “Next ->” button or the “Z-End” button and FOXCST opens the
next GUI dialogue. Select the Z-End CTP:
Table 27: Create a new TDM connection, Z-End

Z-End AP tree ne The management network and all units having
managementNetwork CTPs with the previously configured layer rate.
unit-x
AP list Navigate to the required AP and click in the
square box(es) placed left to the AP name.
When clicking in the square box of a superordi-
nate AP, FOXCST will automatically chose the
first available subordinate CTP(s) with the previ-
ously configured layer rate.
Please note:
When creating a TDM cross connection with the “Connection Wizard” from
the “Tree View” tab the Z-End CTP is predefined, and is
- the current AP address if this AP is a CTP, or otherwise
- the first available subordinate CTP.
Click on the “Next ->” button or the “A-End” button and FOXCST opens the
next GUI dialogue. Select the A-End (working) CTP:

FOXCST REFERENCE
Table 28: Create a new TDM connection, A-End

A-End AP tree ne The management network and all units having
unit-x
square box(es) placed left to the AP name.
first available subordinate CTP(s) with the previ-
ously configured layer rate.
If the TDM cross connection to be created is unprotected click on the “Cre-

ate” button.
If the TDM cross connection to be created is protected click on the “Next ->”
button or the “A-End Prot.” button and FOXCST opens the next GUI dia-
logue. Select the A-End protecting CTP:

FOXCST REFERENCE
Table 29: Create a new TDM connection, A-End Prot.

A-End Prot. AP tree ne The management network and all units having
unit-x
square box placed left to the AP name.
first available subordinate CTP.
Click on the “Create” button to create the TDM cross connection.
8.4.4 Delete a TDM connection
Existing cross connections can be deleted if they are selected in the cross
connection table. You can select single or multiple cross connections.
To select a single cross connection click on the cross connection row in the
cross connection table.
To select multiple non-consecutive cross connections click on the first cross

connection row in the cross connection table, press the “CTRL” key on your
keyboard while clicking on the other cross connection rows.

FOXCST REFERENCE
To select multiple consecutive cross connections click on the first cross con-
nection row in the cross connection table, press the “SHIFT” key on your
keyboard while clicking on the last cross connection row.
Click on the button. All selected cross connections will be deleted

after the confirmation of a warning message.

FOXCST REFERENCE

ANNEX
9 Annex
9.1 Associated documents
1KHW028514 FOX61x Terms and Abbreviations
1KHW002497 FOX61x Precautions and Safety
1KHW002459 FOX61x Release Notes
1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002463 FOX61x Lightning Protection
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002468 FOX61x Ethernet Services
1KHW002469 FOX61x CESM1
1KHW002470 FOX61x LESU1
1KHW002471 FOX61x ETOP1
1KHW002472 FOX61x ELET1
1KHW002473 FOX61x LEDE1
1KHW002474 FOX61x DATI1
1KHW002475 FOX61x EPSI1
1KHW002476 FOX61x SAMO1
1KHW002477 FOX61x SAMO2
1KHW002478 FOX61x LEDS1
1KHW002479 FOX61x LEDA1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1
1KHW002483 FOX61x TEPI1
1KHW002484 FOX61x OPIC1
1KHW002498 FOX61x Electrical Cables

ANNEX

Contact us
ABB Switzerland Ltd
1KHW002467 © Copyright 2012 ABB. All rights reserved.

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: communication.networks@ch.abb.com
www.abb.com/communicationnetworks

FOX61x TDM Services: User Manual

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

FOX61x TDM Services: User Manual

Uploaded by

Copyright:

Available Formats

ABB Power Systems

Release History: Release 1: December 2012

Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHW002467

ABB Switzerland Ltd

4 Specification of TDM services 15

8 FOXCST reference 123

Figure 1: TDM signal bidirectional connection, unprotected 11

1.2 Symbols and notations

This User Manual uses the following symbols:

Risk of operating trouble!

1.3 Document history

Table 1: Document history

2.1.1 FOX61x TDM core and service units

2.1.2 TDM connections overview

2.1.2.1 Bidirectional connection, unprotected

The bidirectional unprotected connection is the standard connection applied

traffic signal unit-1 unit-2 traffic signal

Figure 1: TDM signal bidirectional connection, unprotected

2.1.2.2 Bidirectional connection, protected

The bidirectional protected connection can be used to protect e.g. a traffic

Figure 2: TDM signal bidirectional connection, protected

2.1.2.3 Unidirectional connection, unprotected

The unidirectional unprotected connection is used in special applications as

traffic signal unit-1 unit-2 traffic signal

Figure 3: TDM signal unidirectional connection, unprotected

2.1.2.4 Unidirectional connection, protected

The unidirectional protected connection can be used to protect e.g. a traffic

Figure 4: TDM signal unidirectional connection, protected

Part of the FOX61x functionality is subject to feature licences. For more

3.2 Functions and specification overview

4 Specification of TDM services

4.1 TDM services overview

4.2 Voice services

4.2.1 Order wire phone application

Figure 5: Order wire voice service with FOX61x

4.2.2 FXS and FXO voice application

Figure 6: FXS and FXO voice service with FOX61x

4.2.3 E&M voice application

Figure 7: E&M voice service with FOX61x

4.2.4 Mercury CAS multiplexer

The out of band signalling is converted to MCAS signalling by the LESU1

Figure 8: MCAS routing in FOX61x

4.3 TDM data services

TDM-based data services use either an n x 64 kbit/s (P0_nc) circuit or a

Data SHDSL SHDSL

Protection Protection command TEPI1

Figure 9: TDM data access with FOX61x

4.4 Packet data services

4.4.1 Ethernet over PDH data service

Figure 10: Ethernet over PDH data access with FOX61x

4.4.2 Ethernet over SDH data service

Data Ethernet Packet data Chassis

Data Ethernet Packet data Chassis

Figure 11: Ethernet over SDH data access with FOX61x

5.1 Implementation of the TDM cross connect functions

5.1.1 PDH architecture

All types of cross connections may be bidirectional, unidirectional or uni-

Figure 12: PBUS access

Table 2: PBUS line write access per PBUS unit

Table 2: PBUS line write access per PBUS unit (continued)

a. 64 P12 will be available in a future release