FOX61x Leds1: User Manual

ABB Power Systems
FOX61x
LEDS1
User Manual
User Manual FOX61x
LEDS1
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.: 1KHW002478
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 2012 by ABB Switzerland Ltd
Table of Content
1 Preface 13
1.1 Precautions and safety 13
1.2 Symbols and notations 13
1.3 Interfaces and circuit categories 13
1.4 Document history 14
1.5 Definition of terms 14
2 Introduction 15
2.1 General 15
2.2 Unit view 17
2.3 Block diagram 18
3 Functions and specifications 19

3.1 Feature licences 19
3.2 Summary of standards 19
3.3 DCE functions and specifications 21
3.4 DCE physical layers 23
3.5 MAC bridging 26
3.6 General 27
4 Installation 31
4.1 Prerequisites 31
4.2 Slots and deployment scenarios for the LEDS1 unit 31
4.3 Interoperability and compatibility 32
4.3.1 FOX61x units 32
4.3.1.1 Interoperability of LEDS1 configured as DCE 32
4.3.1.2 Interoperability of LEDS1 configured as MAC bridge 33
4.3.2 FOX units 33
4.3.2.1 Interoperability of LEDS1 configured as DCE 33
4.3.2.2 Interoperability of LEDS1 configured as MAC bridge 34
4.3.3 Previous ESW revisions 34
4.4 Connections and cables 34
4.4.1 Connectors and signals 34
4.4.2 DCE cables 37
4.4.2.1 Cable for X.24/V.11 interfaces 37
4.4.2.2 Cable for V.35 interfaces 37
4.4.2.3 Cable for V.24/V.28 interfaces 37
4.4.2.4 Cable for RS485 interfaces 38
4.4.2.5 Cable accessing every connector pin 38
4.4.3 Ethernet cables 38
4.4.4 Fixing the cables to the cable tray 38
LEDS1User Manual 3
5 Functional Description 41
5.1 Data interface functions 41
5.1.1 DCE interfaces 41
5.1.2 RS485 2-wire control 43
5.1.2.1 RTS controlled mode 43
5.1.2.2 Data controlled mode 44
5.1.3 Transport modes 44
5.1.3.1 nx64 kbit/s transport mode 44
5.1.4 Transmission modes 45
5.1.4.1 Synchronous transmission mode 45
5.1.4.2 Oversampling transmission mode 45
5.1.5 MAC bridging 47
5.1.5.1 LAN modes 47
5.1.5.2 WAN mode 47
5.1.5.3 Queues and priority mappings 47
5.2 Network applications 49
5.2.1 Point-to-point (P2P) 49
5.2.2 Point-to-multipoint (P2MP) 49
5.2.2.1 Linear network setup 50
5.2.2.2 Star network setup 51
5.2.3 Multipoint-to-multipoint (MP2MP) 52
5.2.3.1 Linear network setup 52
5.2.3.2 Star network setup 52
5.3 Conferencing 53
5.3.1 Resources 53
5.3.1.1 Conference resources 53
5.3.1.2 PBUS resources 55
5.3.2 Local Conferences 57
5.3.3 Conferences in the P2MP application 58
5.3.4 Conferences in the MP2MP application 58
5.3.5 Conference control 59
5.4 Data handling 60
5.4.1 Port data handling 60
5.4.2 Conference data handling 62
5.5 Control signal handling 64
5.5.1 Overview 64
5.5.2 CAS signalling transport 67
5.5.3 Port control signal handling 67
5.5.4 Conference control signal handling 70
5.6 Timing handling 74
5.6.1 DTE synchronization 74
5.6.1.1 Codirectional timing 74
5.6.1.2 Contradirectional timing 74
5.6.2 Port timing signals 75
5.6.3 Conference timing 78
5.7 Protection 78
5.7.1 Subnetwork connection and linear trail protection 78
5.7.1.1 Protection configuration 79
5.7.2 Equipment protection (EQP) 80
5.7.2.1 EQP features 80
4 LEDS1User Manual
5.7.2.2 EQP prerequisites 80
5.7.2.3 EQP configuration 81
5.7.2.4 EQP status 81
5.7.2.5 DTE cabling for 1+1 equipment protection 83
6 Commissioning 85
6.1 Profiles 85
6.1.1 General 85
6.1.2 LEDS1 profile handling 86
6.2 Commissioning of a DCE interface 86
6.2.1 Prerequisites 86
6.2.1.1 CESM1 unit 86
6.2.1.2 LEDS1 unit 86
6.2.1.3 TDM transport unit (optional) 87
6.2.1.4 FOXCST 87
6.2.1.5 PETS 87
6.2.2 Configuration of a DCE interface 87
6.3 Commissioning of a conference 90
6.3.1 Prerequisites 90
6.3.2 Configuration of a conference 90
7 Operation 95
7.1 Unit optical indicators 95
7.2 Loops 96
7.2.1 Loop 2b 97
7.2.2 Loop 3b 98
7.2.3 Loop 3c 98
7.3 DCE interface line state maintenance 99
7.4 DTE send and idle time restrictions 101
7.5 Maintenance 103
7.5.1 Inventory data 103
7.5.2 Unit ESW download 103
7.5.3 ESW upgrade with EQP 103
8 FOXCST Reference 107

8.1 Introduction 107
8.2 Profiles 109
8.2.1 QoS mapping profile 109
8.3 AP: / unit-x: LEDS1 110
8.3.1 AP: / unit-x, Overview 110
8.3.2 AP: / unit-x, Main 110
8.3.3 AP: / unit-x, Configuration 111
8.3.3.1 AP: / unit-x, Configuration - Conferencing 111
8.3.3.2 AP: / unit-x, Configuration - EQP 112
8.3.4 AP: / unit-x, Fault Management 113
8.3.5 AP: / unit-x, Status 115
8.3.5.1 AP: / unit-x, Status - Conferences 115
8.3.5.2 AP: / unit-x, Status - EQP 117
8.4 AP: / unit-x / conf-z 118
8.4.1 AP: / unit-x / conf-z, Main 118
8.4.1.1 AP: / unit-x / conf-z, Main - General 118
8.4.2 AP: / unit-x / conf-z, Main 119
8.4.2.1 AP: / unit-x / conf-z, Main - General 119
8.4.3 AP: / unit-x / conf-z, Configuration 119
8.4.3.1 AP: / unit-x / conf-z, Configuration - General 119
8.5 AP: / unit-x / conf-z / part-a 120
8.5.1 AP: / unit-x / conf-z / part-a, Overview 120
8.5.2 AP: / unit-x / conf-z / part-a, Main 120
8.5.2.1 AP: / unit-x / conf-z / part-a, Main - General 120
8.5.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status 120
8.5.3 AP: / unit-x / conf-z / part-a, Configuration 120
8.5.3.1 AP: / unit-x / conf-z / part-a, Configuration - General 121
8.5.3.2 AP: / unit-x / conf-z / part-a, Configuration - CTP 122
8.5.4 AP: / unit-x / conf-z / part-a, Fault Management 124
8.5.5 AP: / unit-x / conf-z / part-a, Performance Management 124
8.5.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection 125
8.5.6 AP: / unit-x / conf-z / part-a, Status 125
8.5.6.1 AP: / unit-x / conf-z / part-a, Status - General 125
8.5.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance 127
8.5.6.3 AP: / unit-x / conf-z / part-a, Status - CTP 128
8.6 AP: / unit-x / port-y, y = 1 … 4 129
8.6.1 AP: / unit-x / port-y, Overview 129
8.6.2 AP: / unit-x / port-y, Main 129
8.6.2.1 AP: / unit-x / port-y, Main - General 129
8.6.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status 130
8.6.3 AP: / unit-x / port-y, Configuration 130
8.6.3.1 AP: / unit-x / port-y, Configuration - General 131
8.6.3.2 AP: / unit-x / port-y, Configuration - Signal Structure 132
8.6.3.3 AAP: / unit-x / port-y, Configuration - Control Signals 135
8.6.3.4 AP: / unit-x / port-y, Configuration - Error Handling 138
8.6.3.5 AP: / unit-x / port-y, Configuration - Test Loops 140
8.6.3.6 AP: / unit-x / port-y, Configuration - CTP 141
8.6.4 AP: / unit-x / port-y, Fault Management 143
8.6.5 AP: / unit-x / port-y, Performance Management 145
8.6.5.1 AP: / unit-x / port-y, Performance Management - Protection 145
8.6.5.2 AP: / unit-x / port-y, Performance Management - G.826 145
8.6.5.3 AP: / unit-x / port-y, Performance Management - Unfiltered Events 146
8.6.6 AP: / unit-x / port-y, Status 147
8.6.6.1 AP: / unit-x / port-y, Status - General 147
8.6.6.2 AP: / unit-x / port-y, Status - Maintenance 150
8.6.6.3 AP: / unit-x / port-y, Status - CTP 151
8.7 AP: / unit-x / port-y, y = 5 152
8.7.1 AAP: / unit-x / port-y, Overview 152
8.7.2 AP: / unit-x / port-y, Main 153
8.7.2.1 AP: / unit-x / port-y, Main - General 153
8.7.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status 153
8.7.2.3 AP: / unit-x / port-y, Configuration - QoS 153
8.7.2.4 AP: / unit-x / port-y, Configuration - PHY 154
8.7.3 AP: / unit-x / port-y, Configuration 155
8.7.3.1 AP: / unit-x / port-y, Configuration - QoS 155
8.7.3.2 AP: / unit-x / port-y, Configuration - PHY 156
8.7.3.3 AP: / unit-x / port-y, Configuration - TDM 156
8.7.3.4 AP: / unit-x / port-y, Configuration - CTP 157
8.7.4 AP: / unit-x / port-y, Fault Management 158
8.7.5 AP: / unit-x / port-y, Performance Management 159
8.7.5.1 AP: / unit-x / port-y, Performance Management - Protection 160
8.7.5.2 AP: / unit-x / port-y, Performance Management - MIB-2 Ethernet Interface 160
8.7.5.3 AP: / unit-x / port-y, Performance Management - MIB-2 TDM Interface 160
8.7.6 AP: / unit-x / port-y, Status 161
8.7.6.1 AAP: / unit-x / port-y, Status - PHY 161
8.7.6.2 AP: / unit-x / port-y, Status - TDM 162
8.7.6.3 AP: / unit-x / port-y, Status - Bridge 162
8.7.6.4 AP: / unit-x / port-y, Status - CTP 163
9 Annex 165
9.1 Associated documents 165
Figures
Figure 1: DTEs connected in a star network, with conference 15

Figure 2: LEDS1 unit view 17
Figure 3: LEDS1 functional block diagram 18
Figure 4: FOX615 subrack with 19 LEDS1 units and 1 SAMO1 unit 31
Figure 5: FOX612 subrack with 6 LEDS1 units and 1 LEDE1 unit 32
Figure 6: Front view of the front panel connectors 35
Figure 7: Side view of the FOX615 cable tray and cables 39
Figure 8: RS485 2-wire and 4-wire modes 43
Figure 9: RS485 2-wire receive data driver control 44
Figure 10: Oversampling when DTE delivers a clock signal 46
Figure 11: Oversampling when DTE delivers no clock signal 46
Figure 12: WAN encapsulation 47
Figure 13: WAN encapsulation 48
Figure 14: Point-to-point application with LEDS1 49
Figure 15: Point-to-multipoint linear application with LEDS1 50
Figure 16: Point-to-multipoint star application with LEDS1 51
Figure 17: Multipoint-to-multipoint linear application with LEDS1 52
Figure 18: Multipoint-to-multipoint star application with LEDS1 53
Figure 19: Conference resource usage example with 4 conferences 55
Figure 20: PBUS resource usage example with 4 conferences 56
Figure 21: Local conference on LEDS1 58
Figure 22: Conference in the P2MP application 58
Figure 23: Conference in the MP2MP application 59
Figure 24: Data transport 60
Figure 25: Conference data transport, MP2MP 62
Figure 26: Conference data transport, P2MP 63
Figure 27: Control signal handling overview 65
Figure 28: Control signal status to a-bit and b-bit mapping 67
Figure 29: Control signal transport 68
Figure 30: Conference control signal transport, MP2MP 71
Figure 31: Conference control signal transport, P2MP 72
Figure 32: Codirectional timing 74
Figure 33: Contradirectional timing 75
Figure 34: Port timing signals 76
Figure 35: Transmit timing 77
Figure 36: Unidirectional 1+1 protection 79
Figure 37: 1+1 equipment protection 83
Figure 38: Fault indication LEDs on the LEDS1 unit 95
Figure 39: Loops 2b, 3b and 3c 96
Figure 40: Loop 2b 97
Figure 41: Loop 3b 98
Figure 42: Loop 3c 98
Figure 43: Send time and idle time supervision 102
Figure 44: MOM (managed object model) of the LEDS1 unit 107
Tables
Table 1: Electrical interfaces and circuit categories 13

Table 2: Document history 14
Table 3: Specific terms 14
Table 4: Standards 19
Table 5: DCE functions and specifications 21
Table 6: V.24/V.28 DCE physical layer functions and specifications 23
Table 7: X.24/V.11 DCE physical layer functions and specifications 23
Table 8: V.35 DCE physical layer functions and specifications 24
Table 9: RS485 DCE physical layer functions and specifications 25
Table 10: MAC bridging functions and specifications 26
Table 11: General functions and specifications 27
Table 12: Interoperability with DATI1 + DTM 32
Table 13: Interoperability with EPSI1, DATI1 + DTM 33
Table 14: Interoperability with DATAx, UNIDA, SULIC + NTU, STICx + DTM 33
Table 15: Interoperability with DATAx, ETER1, LAWA4, LEMU6, STICx + DTM 34
Table 16: DCE interface connectors 36
Table 17: Ethernet interface connector 36
Table 18: Ethernet media types 38
Table 19: Data, control and timing signals with their electrical characteristics 41
Table 20: Function relationship 43
Table 21: Control signal handling 66
Table 22: CAS bits usage 67
Table 23: Profile applicability to managed objects 86
Table 24: LED signalling on LEDS1 95
Table 25: Maintenance function signal replacement 100
Table 26: Managed objects (MOs) for LEDS1 108
Table 27: QoS mapping profile 109
Table 28: AP: / unit-x, Configuration - Conferencing 111
Table 29: AP: / unit-x, Configuration - EQP 112
Table 30: AP: / unit-x, Fault Management 113
Table 31: AP: / unit-x, Status - Conferences 115
Table 32: AP: / unit-x, Status - EQP 117
Table 33: AP: / unit-x / conf-z, Configuration - General 119
Table 34: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status 120
Table 35: AP: / unit-x / conf-z / part-a, Configuration - General 121
Table 36: AP: / unit-x / conf-z / part-a, Configuration - CTP 122
Table 37: AP: / unit-x / conf-z / part-a, Fault Management 124
Table 38: PM counter interval availability 124
Table 39: PM group: Unfiltered Events 125
Table 40: AP: / unit-x / conf-z / part-a, Status - General 125
Table 41: AP: / unit-x / conf-z / part-a, Status - Maintenance 127
Table 42: AP: / unit-x / conf-z / part-a, Status - CTP 128
Table 43: AP: / unit-x / port-y, Main - Admin And Oper Status 130
Table 44: AP: / unit-x / port-y, Configuration - General 131
Table 45: AP: / unit-x / port-y, Configuration - Signal Structure 132
Table 46: AAP: / unit-x / port-y, Configuration - Control Signals 135
Table 47: AP: / unit-x / port-y, Configuration - Error Handling 138
Table 48: AP: / unit-x / port-y, Configuration - Error Handling 140
Table 49: AP: / unit-x / port-y, Configuration - CTP 142
Table 50: AP: / unit-x / port-y, Fault Management 143
Table 52: PM group: Protection 145
Table 53: PM group: G.826 145
Table 54: PM group: Unfiltered Events 146
Table 55: AP: / unit-x / port-y, Status - General 147
Table 56: AP: / unit-x / port-y, Status - Maintenance 150
Table 57: AP: / unit-x / port-y, Status - CTP 151
Table 58: AP: / unit-x / port-y, Main - Admin And Oper Status 153
Table 59: AP: / unit-x / port-y, Configuration - QoS 154
Table 60: AP: / unit-x / port-y, Configuration - PHY 154
Table 61: AP: / unit-x / port-y, Configuration - QoS 155
Table 62: AP: / unit-x / port-y, Configuration - PHY 156
Table 63: AP: / unit-x / port-y, Configuration 156
Table 64: AP: / unit-x / port-y, Configuration - CTP 157
Table 65: AP: / unit-x / port-y, Fault Management 158
Table 67: PM group: Protection 160
Table 68: PM group: MIB-2 Ethernet Interface 160
Table 69: PM group: MIB-2 TDM Interface 160
Table 70: AAP: / unit-x / port-y, Status - PHY 161
Table 71: AP: / unit-x / port-y, Status - TDM 162
Table 72: AP: / unit-x / port-y, Status - Bridge 162
Table 73: AP: / unit-x / port-y, Status - CTP 163
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 Interfaces and circuit categories
Table 1: Electrical interfaces and circuit categories

LEDS1 interface Circuit category according Max. rating
to EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC <2A
V.35 / Appendix II SELV <1V < 10 mA
V.35 / V.28 SELV < 25 V < 100 mA
X.24 / V.11 TNV1 <6V < 150 mA
V.24 / V.28 SELV < 25 V < 100 mA
RS485 TNV1 <6V < 200 mA
Ethernet SELV < 15 V < 300 mA
FOX61xLEDS1 13
PREFACE
1.4 Document history
Table 2: Document history

Date FOX61x Release Changes since previous version
December 2012 R1 This is the first release for FOX61x
1.5 Definition of terms
Table 3: Specific terms

Term Explanation
Receive direction Direction from the DCE interface (LEDS1) towards the DTE
transmit
LEDS1
DTE
receive (DCE)
Transmit direction Direction from the DTE towards the DCE interface (LEDS1)
14 FOX61xLEDS1
INTRODUCTION
2 Introduction
This section presents a general introduction to the LEDS1 unit.
The section is closed with a unit view in section Installation (page 31) and a
block diagram overview in section Block diagram (page 18).
2.1 General
This document describes the architecture and functions of the LEDS1 unit
and shows, how this unit is commissioned and operated as part of the
FOX61x.
The LEDS1 unit is a 1-slot wide service unit of FOX61x. It supports four data
interfaces and one Ethernet bridge port.
Each data interface is independently configurable as DCE interface type
• V.24/V.28,
• V.35 (Appendix II),
• X.24/V.11, or
• RS485.
The DCE interfaces support the following transmission modes:
• Asynchronous mode for subrates from 0.6 kbit/s to 38.4 kbit/s (future
release).
• Synchronous mode for subrates from 0.6 kbit/s to 56 kbit/s (future
release).
• Synchronous mode for nx64 data rates from 1x64 kbit/s to 31x64 kbit/s.
• Oversampling mode for data rates from 0 kbit/s to 600 kbit/s.
The synchronous nx64 transmission modes provide the codirectional or con-
tradirectional timing operation.
The Ethernet bridge port is implemented as 10BASE-T/100BASE-TX inter-
face according to IEEE Std. 802.3-2002.
Beside the data access LEDS1 offers the possibility to establish data confer-
ences with participants from the LEDS1 unit or any data circuit available in
the FOX61x.
FOX61x FOX61x
TDM data
LEDS1
Network
LEDS1 DTE
Data
Confer-
FOX61x
ence
data TDM data
DTE Network
LEDS1 DTE
P12 transport unit
Figure 1: DTEs connected in a star network, with conference
FOX61xLEDS1 15
INTRODUCTION
The LEDS1 unit as a FOX61x TDM unit provides PBUS (FOX61x TDM bus)
access.
LEDS1 has an access capacity of 32 x 2 Mbit/s towards the FOX61x internal
cross connection backplane, PBUS, allowing access of the four data user
ports, the Ethernet bridge port and of up to 212 data conferences with up to
848 participants in total.
The following network features will help to enhance the systems availability:
• 1+1 linear trail protection switching.
• 1+1 linear subnetwork connection protection switching.
A more economical use of the network resources can be achieved by the
features like:
• Point-to-multipoint linear networks (P2MP)
• Multipoint-to-multipoint linear networks (MP2MP)
The multipoint networks are using the data conferences.
LEDS1 is connected to a TDM transport unit as e.g. a SAMO1 unit via the
PBUS in the backplane of FOX61x.
16 FOX61xLEDS1
INTRODUCTION
2.2 Unit view
Figure 2: LEDS1 unit view
Figure 2 shows the LEDS1 unit hardware. On the front plate are two LEDs
for the unit- and traffic failure indication. The connectors for the four data
interfaces are of type Metral ® with 4x6 male contacts.
The Ethernet interface uses a standard RJ-45 connector.
FOX61xLEDS1 17
INTRODUCTION
2.3 Block diagram
PBUS Access
Cross 1 x P12 nx64 kbit/s Ethernet
Connect - 1+1 protection interface
Front Connectors
DCE interface 1
PBUS Access
nx64 kbit/s - X.24/V.11 2

Cross 4 x P12
- CAS time slot - V.35 3
Connect
- 1+1 protection Subrate - V.24/V.28 4
< 64 kbit/s - RS485
PBUS Access
Cross 27 x P12 Conferencing

Connect - 1+1 protection
Host processor
Backplane access
Subrack
internal
communication
Power
Figure 3: LEDS1 functional block diagram
Please note:
Subrates will be supported in a future release.
18 FOX61xLEDS1
FUNCTIONS AND SPECIFICATIONS
3 Functions and specifications

The LEDS1 unit provides the following functions and conforms to the corre-
sponding standards and recommendations (conformance to applicable parts
of the standards).
3.1 Feature licences
This unit is not subject to feature licences.
3.2 Summary of standards
Table 4: Standards
Feature Standard
Data transport r1a
- ETSI EN 300 417-5-1 V1.2.1, 2001-10
Transmission and Multiplexing (TM); Generic
requirements of transport functionality of equip-
ment; Part 5-1: Plesiochronous Digital Hierarchy
(PDH) path layer functions
- ETSI EN 300 417-2-1 V1.2.1, 2001-10
ment; Part 2-2: Synchronous Digital Hierarchy
(SDH) and Plesiochronous Digital Hierarchy (PDH)
physical section layer functions
- ETSI EN 300 417-1-1 V1.2.1, 2001-10
ment; Part 1-1: Generic processes and perfor-
mance
FOX61xLEDS1 19
Table 4: Standards (continued)

Feature Standard
Data interfaces - ITU-T V.11, X.27, 10/96 r1a
Electrical characteristics for balanced double-cur-
rent interchange circuits operating at data signal-
ing rates up to 10 Mbit/s
- ITU-T V.24, 02/2000
List of definitions for interchange circuits between
data terminal equipment (DTE) and data circuit-ter-
minating equipment (DCE)
- ITU-T V.28, 03/93
Electrical characteristics for unbalanced double-
current interchange circuits
- ITU-T V.35, 10/84
Data transmission at 48 kilobits per second using
60-108 kHz group band circuits
- ITU-T X.21, 09/92
Interface between Data Terminal Equipment and
Data Circuit-terminating Equipment for synchro-
nous operation on public data networks
- ITU-T X.21bis, 11/88
Use on public data networks of Data Terminal
Equipment (DTE) which is designed for interfacing
to synchronous V series modems
- ITU-T X.24, 11/88
List of definitions for interchange circuits between
Data Terminal Equipment (DTE) and Data Circuit-
terminating Equipment (DCE) on public data net-
works
- TIA/EIA-485-A, 1998
Electrical characteristics of generators and receiv-
ers for use in balanced digital multipoint systems
Synchronisation and timing - ISO/IEC 9543, 1989-04-01 r1a
Information processing systems – Information
exchange between systems – Synchronous trans-
mission signal quality at DTE/DCE interfaces
Ethernet transport - ISO/IEC 13239 r2a
Information technology -- Telecommunications and
information exchange between systems -- High-
level data link control (HDLC) procedures
- ANSI/IEEE Std 802.1D, 1998

IEEE Standard for Information technology. Tele-
communications and information exchange
between systems. Local and metropolitan area
networks. Common specifications Part 3: Media
Access Control (MAC) Bridges
- IEEE Std 802.3-2002
IEEE Standard for Information technology — Tele-
communications and information exchange
between systems — Local and metropolitan area
networks — Specific requirements Part 3: Carrier
sense multiple access with collision detection
(CSMA/CD) access method and physical layer
specifications
20 FOX61xLEDS1
Table 4: Standards (continued)

Feature Standard
Ethernet management - RFC1493 r3a
Definitions of Managed Objects for Bridges
- RFC2011
SNMPv2 Management Information Base for the
Internet Protocol using SMIv2
- RFC2131
Dynamic Host Configuration Protocol
- RFC2132
Dynamic Host Configuration Protocol
- RFC2674
Definitions of Managed Objects for Bridges with
Traffic Classes, Multicast Filtering and Virtual LAN
Extensions
- RFC3396
Encoding Long Options in the Dynamic Host Con-
figuration Protocol (DHCPv4)
- RFC3442
The Classless Static Route Option for Dynamic
Host Configuration Protocol (DHCP) version 4
- RFC3942
Reclassifying Dynamic Host Configuration Proto-
col version 4 (DHCPv4) Options
Performance parameters and limits - ITU-T G.826, 12/2002 r1a
End-to-end error performance parameters and
objectives for international, constant bit-rate digital
paths and connections
Maintenance functions - ITU-T V.54, 11/88 r1a
Loop test devices for modems
- ITU-T X.150, 11/88
Principles of maintenance testing for public data
networks using Data Terminal Equipment (DTE)
and Data Circuit terminating Equipment (DCE) test
loops
3.3 DCE functions and specifications
Table 5: DCE functions and specifications

Feature Rating or standard Release
Number of available DCE interfaces 4 r1a
Type of interfaces individually selectable by the configuration manage-
ment:
X.24/V.11
V.24/V.28
V.35
RS485 4-wire
RS485 2-wire
User data rates of nx64 kbit/s synchronous r1a
nx64 kbit/s, n = 1 to 31, without CAS
nx64 kbit/s, n = 1 to 30, with use of CAS for control
signal transport
FOX61xLEDS1 21
Table 5: DCE functions and specifications (continued)

Synchronization r1a
- DCE interface synchronous mode Synchronized to the network element (NE) timing
source.
With X.24/V.11, V.24/V.28 and V.35 type interfaces:
Contradirectional or codirectional timing
DCE output jitter, nx64 kbit/s r1a
- Intrinsic jitter peak-peak on the clock signals ≤ 50 ns in the frequency range of 20 Hz to 100 kHz
- timing accuracy better than 50 ppm peak
DCE output jitter, nx64 kbit/s in accordance with ISO 9543 r1a
(data, control and timing signals)
- jitter peak-peak S, 114, 115 ≤ 30%
- duty cycle S, 114, 115 50 ± 10%
DCE jitter tolerance, nx64 kbit/s in accordance with ISO 9543 r1a
(data, control and timing signals)
- jitter peak-peak X, 113 (ON to OFF) ≤ 1%
- duty cycle X, 113 50 ± 10%
- timing displacement of the transmit data and control ≤ 45%
signals (peak, codirectional timing) in relation to X,
113 (ON to OFF)
- timing displacement of the transmit data and control ≤ 30%
signals (peak, contradirectional timing) in relation to S,
114 (OFF to ON)
DCE to DCE transfer delay Maximum one way transfer delay from DCE inter- r1a
face to DCE interface excluding any network delays
- nx64 kbit/s, contradirectional timing ≤ 600 μs with fixed transmit timing. r1a
≤ 600 μs + 250/n μs with phase adaptive transmit
timing
- nx64 kbit/s, codirectional timing ≤ 600 μs + 250/n μs r1a
22 FOX61xLEDS1
3.4 DCE physical layers
Table 6: V.24/V.28 DCE physical layer functions and specifications

Interface circuits V.24 - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103 TxD transmitted data
- 104 RxD received data
- 105 RTS request to send
- 106 CTS ready for sending
- 107 DSR data set ready
- 108 DTR data terminal ready
- 109 DCD data channel rec. line sig. det.
- 113 TT transmitter signal element timing
- 114 ST transmitter signal element timing
- 115 RT receiver signal element timing
- 141 LL local loopback
- 142 TM test indicator
- Signal direction to DCE circuits 103, 105, 108, 113, 141
- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142
Electrical characteristics r1a
- circuits 103, 105, 108, 113 and 141 as receivers according to V.28
- circuits 104, 106, 107, 109, 114, 115 and 142 as trans- according to V.28
mitters
Polarities r1a
- 103, 104 = 0 - UA > 3 V (system logic: level low)
- 103, 104 = 1 - UA < -3 V (system logic: level high)
- all other circuits = ON - UA > 3 V (system logic: level low)
- all other circuits = OFF - UA < -3 V (system logic: level high)
User data rates available nx64 kbit/s synchronous, n = 1 to 2 r1a
nx64 kbit/s oversampling, n = 1 to 30, with CAS
nx64 kbit/s oversampling, n = 1 to 31, without CAS
Maximum line length at the maximum available data 15 m r1a
rate
Table 7: X.24/V.11 DCE physical layer functions and specifications

Interface circuits X.24 - G signal ground or common return) r1a
(unused circuits are kept in the OFF state) - T transmit
- R receive
- C control
- I indication
- S signal element timing
- B byte timing
- F frame start indication
- X DTE transmit signal element timing
- Signal direction to DCE circuits T, C, X
- Signal direction from DCE circuits R, I, S, B, F
FOX61xLEDS1 23
Table 7: X.24/V.11 DCE physical layer functions and specifications

- Circuits T, C and X as receivers according to V.11 (X.27)
- Equivalent terminating resistor 125 Ω ± 10%.
- Circuits R, I, S, B and F as transmitters according to V.11 (X.27)
Polarities r1a
- R, T = 0 - UA-UB ≥ 0.3 V(system logic: level low)
- R, T = 1 - UA-UB ≤ -0.3 V(system logic: level high)
- C, I, S, B, F, X = ON - UA-UB ≥ 0.3 V(system logic: level low)
- C, I, S, B, F, X = OFF - UA-UB ≤ -0.3 V(system logic: level high)
User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CAS r1a
nx64 kbit/s synchronous, n = 1 to 31, without CAS
Maximum line length at the maximum available data 15 m with contradirectional timing r1a
rate 50 m with codirectional timing
Table 8: V.35 DCE physical layer functions and specifications

Interface circuits V.35 - 102 GND signal ground or common return r1a
- 105 RTS request to send
- 106 CTS ready for sending
- 107 DSR data set ready
- 113 TT transmitter signal element timing.
- 114 ST transmitter signal element timing
- 115 RT receiver signal element timing
- 141 LL local loopback
- 142 TM test indicator
Note: The signal list is according to ITU-T V.36, i.e.

the signals 113, 141 and 142 are added to the sig-
nal list of V.35. The signal 108 has been added
from the V.24 signal list.
- Signal direction to DCE circuits 103, 105, 108, 113, 141
- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142
- Circuits 103 and 113 as receivers according to V.35
- Circuits 105, 108 and 141 as receivers according to V.28
- Circuits 104, 114 and 115 as transmitters according to V.35
- Circuits 106, 107, 109 and 142 as transmitters according to V.28
24 FOX61xLEDS1
Table 8: V.35 DCE physical layer functions and specifications (con-

Polarities r1a
- 103, 104 = 0: - UA-UB > 0 V (system logic: level low)
- 103, 104 = 1: - UA-UB < 0 V (system logic: level high)
- 113, 114, 115 = ON: - UA-UB > 0 V (system logic: level low)
- 113, 114, 115 = OFF: - UA-UB < 0 V (system logic: level high)
- all other circuits = ON: - UA > 3 V (system logic: level low)
- all other circuits = OFF: - UA < -3 V (system logic: level high)
User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CAS r1a
nx64 kbit/s synchronous, n = 1 to 31, without CAS
Maximum line length at the maximum available data 15 m with contradirectional timing r1a
rate 50 m with codirectional timing
20 m if V.28 signals are used
Table 9: RS485 DCE physical layer functions and specifications

Interface circuits RS485 4-wire - 102 GND signal ground or common return r1a
The signal 103 acts as a single receiver with multi-

ple drivers (DTEs).
The signal 104 acts as a single driver with multiple
receivers (DTEs).
Note: The signals 103 and 104 shall not be con-

nected together outside LEDS1.
Interface circuits RS485 2-wire - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103/104 TxD/RxD transmitted/received data
The signal 103 acts as a single receiver with multi-

ple drivers (DTEs).
The signal 104 acts as a single driver with multiple
receivers (DTEs).
- Signal direction to DCE circuits 103
- Signal direction from DCE circuits 104
- Circuit 103 as receivers according to RS485
- Bus terminating resistor of the circuit 103 125 Ω ± 10%
Note: It is assumed, that a second bus terminating

resistor with the same value as above is placed at
the end of the bus cables.
- Circuit 104 as transmitters according to RS485
Polarities r1a
- 103, 104 = 0: - UA-UB > 0.2 V(system logic: level low)
- 103, 104 = 1: - UA-UB < -0.2 V(system logic: level high)
FOX61xLEDS1 25
Table 9: RS485 DCE physical layer functions and specifications

User data rates available 0 to 600 kbit/s in oversampling mode r1a
Maximum line length at the maximum available data 50 m r1a
rate
3.5 MAC bridging
Table 10: MAC bridging functions and specifications

Ethernet ports r2a
- Number of Ethernet ports 1
electrical
- Interface type 10BASE-T/100BASE-TX
- Interface mode Auto - MDI/MDI-X
- Electrical connection Connector RJ-45
Impedance 100 ± 15 Ω for the frequency band from
1 to 100 MHz
Ethernet traffic layers r2a
- Ethernet modes - 10BASE-T half duplex
- 10BASE-T full duplex
- 100BASE-TX half duplex
- 100BASE-TX full duplex
- Autonegotiation
- Bridging Transparent MAC bridging according to IEEE
802.1D, using one bridge instance.
Note: The spanning tree protocol is not supported.
- Packet forwarding Packets are forwarded from the LAN to the WAN
port and vice versa, i.e. between the Ethernet inter-
faces and the P0-nc channel.
Packets that can not be forwarded are discarded:
- filtered according to the information in the bridge
hash table.
- lack of system resources
- MAC learning Dynamic MAC address table, 4000 entries.
- Frame format IEEE Std. 802.3-2005
- Frame size up to 1600 Bytes
- Ingress buffer sizes (towards TDM port) 4x 64 frames
- Egress buffer size (towards Ethernet port) 128 frames
- Number of ingress queues 4
- Number of egress queues 1
- Support of profiles for the four ingress queue mapping
- Throughput over P0-31c, frame size 64 to 1’518 bytes 1.9 Mbit/s r2a
26 FOX61xLEDS1
Table 10: MAC bridging functions and specifications (continued)

WAN protocols r2a
- HDLC HDLC is used as logical link control protocol as
underlying layer of the MAC frames.
3.6 General
Table 11: General functions and specifications

Front connectors data interface Metral ® r1a
4x6 male contacts
Front connector Ethernet interface RJ-45 r1a
No hardware settable options on the unit All unit parameters are software settable with the r1a
element manager
Hot swapping You can replace a LEDS1 unit without interfering r1a
with any other units. No actions on powering, con-
figuration or commissioning need to be taken if you
remove/replace a LEDS1 unit
PBUS access 32 x P12 r1a
Cross connections Flexible cross connections to any other FOX61x r1a
TDM unit on the P0_nc traffic layer
Conferences Logical addition of the data signals: r1a
- Wired-AND
Logical addition of the CAS signalling signals:
- Wired-AND
- Conference type Multipoint-to-multipoint,
Point-to-multipoint
Conferences nx64 kbit/s r1a
- Maximum number of conferences per unit 212 with up to 4 participants, 1x64 kbit/s
106 with up to 8 participants, 1x64 kbit/s
53 with up to 16 participants, 1x64 kbit/s
- Maximum number of participants per conference 16, 1 … 31x64 kbit/s
- Maximum bandwidth per participant 31x64 kbit/s
- Maximum bandwidth per conference 496x64 kbit/s
- Maximum bandwidth per unit 848x64 kbit/s
Equipment protection r1a
- Switching type 1:1 equipment protection
- Protection mode non revertive
- Switching time 1 conference:
< 6 s with removal of the active unit
< 1 s with manual or forced switching
212 conferences:
< 60 s
FOX61xLEDS1 27
Table 11: General functions and specifications (continued)

Traffic protection r1a
- Linear trail protection 1+1 unidirectional, revertive
1+1 unidirectional, non revertive
- SNC/I protection 1+1 unidirectional, revertive
1+1 unidirectional, non revertive
- Switching time < 50 ms
Performance monitoring G.826 parameters r1a
Octet slips
Protection switchover events
MIB-2 statistics r2a
Alarm reporting ITU-T X.733 (1992) r1a
Information technology – open systems intercon-
nection – systems management: Alarm reporting
function
Maintenance r1a
- Test pattern insertion Per user port and conference participant
- Out of service Per user port and conference participant
Loops Data and signalling r1a
- Loop 2b Remote loop, back-to-back
- Loop 3b Local loop, front-to-front
- Loop 3c Local loop, front-to-front
Power consumption r1a
- Power supply range VBAT refer to 1KHW002460 FOX61x Product Fea-
tures and Characteristics
- Maximum current consumption, IVBAT 115 mA
VBAT = -48 V
- Maximum total power requirement from battery, PTOT 5.5 W
VBAT = nominal voltage
Mechanical parameters r1a
- Construction practice 19 inch
- Height of unit (1 HU = 44.45 mm) 6 HU
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
- Weight 400 grams
- RoHS Directive 2002/95/EC of the European Parliament
and of the Council of 27.1.2003 on the Restriction
of the use of certain hazardous substances in elec-
trical and electronic equipment
- WEEE Directive 2002/96/EC of the European Parliament
and of the Council of 27.1.2003 on waste electrical
and electronic equipment
Reliability r1a
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 77 years
Emission refer to 1KHW002460 FOX61x Product Features r1a
and Characteristics
CENELEC EN 50121-4, 07/2006 r1a
28 FOX61xLEDS1
Table 11: General functions and specifications (continued)

Immunity refer to 1KHW002460 FOX61x Product Features r1a
and Characteristics
CENELEC EN 50121-4, 07/2006 r1a
Safety refer to 1KHW002460 FOX61x Product Features r1a
and Characteristics
CENELEC EN 50124-1, 03/2001 r1a
Ambient conditions refer to 1KHW002460 FOX61x Product Features r1a
and Characteristics
ETSI EN 300 019-1-8 V2.1.4, 04/2003 r1a
Class 8.1 and class Special (3M5)
FOX61xLEDS1 29
30 FOX61xLEDS1
INSTALLATION
4 Installation
This chapter presents the prerequisites for the installation of the LEDS1 unit
in section Prerequisites (page 31).
The section Slots and deployment scenarios for the LEDS1 unit (page 31)
shows the available slots for the unit and some application examples.
The section Interoperability and compatibility (page 32) handles the compati-
bility of the LEDS1 unit within FOX61x and with FOX51x, while section Con-
nections and cables (page 34) handles any external connections and cables.
4.1 Prerequisites
Before installing a LEDS1 unit take care to follow the safety advice as listed
in Precautions and safety (page 13).
Valid combinations of hardware (HW) and embedded software (ESW) ver-
sions are given in 1KHW002459 FOX61x Release Notes.
For the installation of FOX61x HW, refer to 1KHW002461 FOX615 Installa-
tion or refer to 1KHW002462 FOX612 Installation.
4.2 Slots and deployment scenarios for the LEDS1 unit
The LEDS1 unit uses one slot in the FOX61x subrack.

In a FOX61x, the LEDS1 unit can be operated in any of the following slots:
• FOX615: 1 … 10, 12 … 21.
• FOX612: 7 … 10, 12 … 14.
Slot 11 is reserved for the working CESM1 unit.
In maximum 20 LEDS1 units (without network connection) can be operated
in a FOX615. The number of LEDS1 units is reduced when using TDM trans-
port units as connection to the TDM network.
FOX615
Slot Slot Slot
1 11 21
L L L L L L L L L L C L L L L L L L L L S TDM
E E E E E E E E E E E E E E E E E E E E A Network
D D D D D D D D D D S D D D D D D D D D M
S S S S S S S S S S M S S S S S S S S S O
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
n x 2 Mbit/s
Figure 4: FOX615 subrack with 19 LEDS1 units and 1 SAMO1 unit
FOX61xLEDS1 31
INSTALLATION
The example above shows a FOX615 subrack equipped with 19 LEDS1

units, i.e. 76 user data ports, which can be transported over a number of 2
Mbit/s links over the TDM network.
FOX612
Slot Slot Slot
7 11 14
L L L L C L L L TDM
E E E E E E E E
Network
D D D D S D D D
S S S S M S S E
1 1 1 1 1 1 1 1
n x 2 Mbit/s
Figure 5: FOX612 subrack with 6 LEDS1 units and 1 LEDE1 unit
The example above shows a FOX612 subrack equipped with 6 LEDS1 units,
i.e. 24 user data ports, which can be transported over a number of 2 Mbit/s
Pseudo Wires through a packet network to another TDM network.
4.3 Interoperability and compatibility
4.3.1 FOX61x units

The deployment of a LEDS1 unit in FOX61x is compatible with any other
FOX61x unit.
4.3.1.1 Interoperability of LEDS1 configured as DCE
Table 12: Interoperability with DATI1 + DTM

Interworking Criteria Units to interwork with LEDS1
DATI1 + DTM
DCE interfaces X.24/V.11 Yes (X.21)
V.35 Yes
V.24/ V.28 Yes (n ≤ 2)
RS485 No a
Interface rates n x 64 kbit/s Yes (n ≤ 31)
Network functions SNCP/I Yes (n ≤ 31)
LTP No
Point to multipoint No b
Control signal transport Yes
105 → 109
Control signal transport No
108 → 107
a. Interoperability is possible if the remote side DCE interface is not RS485.

b. It is possible to connect a DTE attached to a DATI1 port to a LEDS1 conference.
32 FOX61xLEDS1
INSTALLATION
4.3.1.2 Interoperability of LEDS1 configured as MAC bridge
Table 13: Interoperability with EPSI1, DATI1 + DTM

EPSI1 DATI1 + DTM
LAN-WAN bridge HDLC Supported Supported
WAN-WAN bridge Supported Not supported
Maximum frame length 1500 1600
WAN interface nx64 kbit/s n ≤ 31 n ≤ 31
4.3.2 FOX units
4.3.2.1 Interoperability of LEDS1 configured as DCE
Table 14: Interoperability with DATAx, UNIDA, SULIC + NTU, STICx +

DTM
DATAx UNIDA SULIC + NTU STICx + DTM
431 - 438
DCE interfaces X.24/V.11 DATAS, DATAT, 433/436/438 Yes Yes (X.21)
DATA1, DATA5
V.35 DATAS, DATAV, 432/437 Yes Yes
DATA3, DATA5
V.24/ V.28 DATAS, DATAR, 431 Yes (n ≤ 2) Yes (n ≤ 2)
DATA4, DATA5
RS485 DATAS, DATA5 No a No a No a
Interface rates n x 64 kbit/s Yes (n ≤ 31) Yes (n ≤ 31) Yes (n ≤ 2) Yes (n ≤ 31)
Network SNCP/I DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) Yes (n ≤ 31)
functions DATAT, DATAV 433/436
LTP DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) No
DATAT, DATAV 433/436
Point to multi- DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) Yes (n ≤ 31)
point DATAT, DATAV 433/436
Control signal Yes Yes Yes b Yes
transport 105 →
109
Control signal Yes b Yes b Yes b No
transport 108 →
107
a. Interoperability is possible if the remote side DCE interface is not RS485.

b. Control signal transport is available for subrates only. Subrates will be available in a
future release.
FOX61xLEDS1 33
INSTALLATION
4.3.2.2 Interoperability of LEDS1 configured as MAC bridge
Table 15: Interoperability with DATAx, ETER1, LAWA4, LEMU6, STICx

+ DTM
DATAx ETER1 LAWA4, STICx + DTM
LEMU6
LAN-WAN bridge HDLC Supported Supported Not supported Supported
WAN-WAN bridge Not supported Supported Supported Not supported
Maximum frame length 1600 1500 1500 1600
WAN interface nx64 kbit/s n ≤ 31 n ≤ 31 n ≤ 31 n ≤ 31
4.3.3 Previous ESW revisions

The LEDS1 unit with ESW release leds1_r2a is the first release for the
FOX61x Release 1.
4.4 Connections and cables
4.4.1 Connectors and signals

The LEDS1 unit provides individual connectors for each of the five front
interfaces. The four DCE interface connectors use a 24 pin Metral connector,
the Ethernet interface uses a RJ-45 connector.
The pin assignment of the five front panel connectors is shown in Figure 6
and in Table 16 below.
The Ethernet interface connector exhibits 2 LEDs indicating the status of the
Ethernet connection:
• Upper LED (yellow): Blinking when a packet is received (activity LED).
• Lower LED (green): Steady light when the link is up and running (link
LED).
There is no difference in the indications if the link is half or full duplex or if
the link speed is 10BASE-T or 100BASE-TX.
34 FOX61xLEDS1
INSTALLATION
LEDS1 R1A Connector port-5

ANR_37900358
untiltet front view
pin 1
pin 8
port-5
Connectors port-1 to port-4

port-4 untiltet front view
A B C D
1
port-3
2
4
port-2
5
6
port-1
Notch for the cable
latching clip
Figure 6: Front view of the front panel connectors
Please note:
The connectors of port-1 to port-5 are tilted by 39°.
The pin assignment of the DCE connector is dependent of the configured
interface type:
FOX61xLEDS1 35
INSTALLATION
Table 16: DCE interface connectors

Pin X.24/V.11 V.35 V.24/V.28 RS485
A1
A2 103a a
A3 103b a
A4 Ta 103a 103
A5 Tb 103b
A6 Ground Ground Ground Ground
B1 141 141
B2 X/B/Fa 113a 113
B3 X/B/Fb 113b
B4 Ra 104a 104 104a b
B5 Rb 104b 104b b
B6 Ground Ground Ground Ground
C1 Ca 105 105
C2 Cb
C3 Ia 109 109
C4 Ib
C5 114a 114
C6 114b
D1 107 107
D2 108 108
D3 106 106
D4 142 142
D5 Sa 115a 115
D6 Sb 115b
a.In the RS485 2-wire mode this pin is used for transmit and receive.
b.In the RS485 2-wire mode this pin is not used.
The pin assignment of the Ethernet connector is as follows:
Table 17: Ethernet interface connector

Pin MDI MDI-X
1 Tx+ Rx+
2 Tx- Rx-
3 Rx+ Tx+
4 - -
5 - -
6 Rx- Tx-
7 - -
8 - -
36 FOX61xLEDS1
INSTALLATION
4.4.2 DCE cables

For each interface type, cables are available which provide the adaptation of
the universal unit connector to the dedicated interface type connector:
Since no DCE connector is standardized for RS485 only the unterminated
cable, i.e. without connector, is offered for the RS485 interface type.
Cables are also offered without the dedicated interface connector, i.e. unter-
minated.
Please note:
The latching clips of the unit side connectors must be positioned to the left
side to insert the connector correctly.
4.4.2.1 Cable for X.24/V.11 interfaces
4.4.2.1.1 Terminated cable

A terminated cable is used to connect the X.24/V.11 data interface to the
DTE. The DCE end of the X.24/V.11 cable uses a 15-pole D-sub female con-
nector, according to ISO 4903.
4.4.2.1.2 Unterminated cable

An open ended or unterminated cable with 8 pairs is used to connect the
X.24/V.11 data interface to the MDF or can be equipped with a customer
specific connector.
4.4.2.2 Cable for V.35 interfaces

A terminated cable is used to connect the V.35 data interface to the DTE.
The DCE end of the V.35 cable uses a 34-pole female connector, according
to ISO 2593.
Please note:
The signal list of the V.35 interface is according to ITU-T V.36, i.e. the sig-
nals 113, 141 and 142 are added to the signal list of V.35. The circuit 108
has been added from the V.24 signal list.

An open ended or unterminated cable with 12 pairs is used to connect every
pin of the data interface connector to the MDF or can be equipped with a
customer specific connector.
4.4.2.3 Cable for V.24/V.28 interfaces

A terminated cable is used to connect the V.24/V.28 data interface to the
DTE. The DCE end of the X.24/V.11 cable uses a 25-pole D-sub female con-
nector, according to ISO 2110.
FOX61xLEDS1 37
INSTALLATION

4.4.2.4 Cable for RS485 interfaces

An unterminated cable with 4 pairs is used to connect the RS485 data inter-
face to the MDF or can be equipped with a customer specific connector.
Since no DCE connector is standardized for RS485 only the unterminated
cable, i.e. without connector, is offered for the RS485 interface type
It is up to the customer to attach the desired type of connector.
4.4.2.5 Cable accessing every connector pin

4.4.3 Ethernet cables

The Ethernet interface layout is per default according to the host layout, but
implements automatic crossover functionality (MDI/MDI-X), i.e. it can adapt
itself automatically to work with a host or a switch. The interface therefore
works with crossover and straight cables.
The following media types are supported:
Table 18: Ethernet media types

IEEE standard Distance Media type
10BASE-T 100 m Category 3 SF/UTP or better
100BASE-TX 100 m Category 5 SF/UTP or better
Please note:
A straight Ethernet cable is available from ABB.
4.4.4 Fixing the cables to the cable tray

The cables must be attached to the cable tray of the FOX615 or the corre-
sponding device of the FOX612.
The figure below shows the cable/cable tray assembly of the FOX615.
38 FOX61xLEDS1
INSTALLATION
In
L e te rf
N u n g a ce
m th ty
be pe
r
In
te
rf
L ace
N e ngt ty
um h p e
be
r
In
te
Le rf ac
N n
um gth e ty
be pe
r
In
Len terf
Nu gth ace
m ty
be pe
r
285 mm
Number
Length
Interface type
265 mm
Number
Length
Interface type
235 mm
Number
Length
Interface type
205 mm
Number
Length
Interface type
175 mm
Figure 7: Side view of the FOX615 cable tray and cables
Please note:
The cable route on the cable tray should follow approximately the projection
of the unit slot on the cable tray.
With the FOX612 the cable tray functionality is implemented differently and
depends on the type of installation (rack-, wall-mounted).
For more information on fixing the cables with the FOX612 refer to
1KHW002462 FOX612 Installation.
FOX61xLEDS1 39
INSTALLATION
40 FOX61xLEDS1
FUNCTIONAL DESCRIPTION
5 Functional Description
This chapter gives the detailed functional description of the LEDS1 unit in
the FOX61x subrack:
• Data interface functions of the LEDS1 unit (section Data interface func-
tions (page 41).
• Network applications with the LEDS1 unit (section Network applications
(page 49)).
• Description of the data and signalling conferencing features (section Con-
ferencing (page 53)).
• All data signal related functions and transport features (section Data han-
dling (page 60)).
• All control signal related functions and transport features (section Control
signal handling (page 64)).
• All timing and timing signal related functions and transport features (sec-
tion Timing handling (page 74)).
• Traffic and equipment protection functions (section Protection (page 78)).
5.1 Data interface functions
5.1.1 DCE interfaces

Each data port of the LEDS1 unit is individually configurable to one of the fol-
lowing DCE interface types:
• X.24 / V.11
• V.35
• V.24 / V.28
• RS485 4-wire
• RS485 2-wire
The following data, control and timing signals are available, depending of the
interface type and the transmission mode:
Table 19: Data, control and timing signals with their electrical charac-
teristics a
Signal description Signal Signal DCE interface type DCE interface type
X.24 / V.24 type direction synchronous oversampling
X.24/ V.35 b V.24/ RS485 X.24/ V.35 b V.24/ RS485
V.11 V.28 V.11 V.28
Signal ground or common - - G 102 102 - G 102 102 102
return - - - - - - -
Transmit / Transmitted Data to T 103 103 - T 103 103 103
data DCE (V.11) (V.35) (V.28) (V.11) (V.35) (V.28) (RS485)
Receive / Received data Data from R 104 104 - R 104 104 104
DCE (V.11) (V.35) (V.28) (V.11) (V.35) (V.28) (RS485)
Control / Request to send Control to C 105 105 - C 105 105 -
DCE (V.11) (V.28) (V.28) (V.11) (V.28) (V.28)
FOX61xLEDS1 41
Table 19: Data, control and timing signals with their electrical charac-
teristics a (continued)
Signal description Signal Signal DCE interface type DCE interface type
X.24 / V.24 type direction synchronous oversampling
X.24/ V.35 b V.24/ RS485 X.24/ V.35 b V.24/ RS485
V.11 V.28 V.11 V.28
- / Ready for sending Control from - 106 106 - - 106 106 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Data set ready Control from - 107 107 - - 107 107 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Data set to line Control to - 108 108 - - 108 108 -
DCE (V.28) (V.28) (V.28) (V.28)
Indication / Data channel Control from I 109 109 - I 109 109 -
received line signal detec- DCE (V.11) (V.28) (V.28) (V.11) (V.28) (V.28)
tor
DTE transmit signal ele- Timing to Xc 113 113 - - - - -
ment timing / Transmitter DCE (V.11) (V.35) (V.28)
signal element timing
(DTE)
Signal element timing / Timing from S 114 114 - - - - -
Transmitter signal element DCE (V.11) (V.35) (V.28)
timing (DCE)
Signal element timing / Timing from S 115 115 - - - - -
Receiver signal element DCE (V.11) (V.35) (V.28)
timing (DCE)
Byte timing, Frame start Timing from B/F c - - - - - - -
identification / Transmitted DCE (V.11)
character timing
- / Local loopback Control to - 141 141 - - 141 141 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Test indicator Control from - 142 142 - - 142 142 -
DCE (V.28) (V.28) (V.28) (V.28)
a. Table entries in brackets designate the electrical interface characteristics.

b. The signal list of the V.35 interface is according to ITU-T V.36, i.e. the signals 113,
141 and 142 are added to the signal list of V.35. The circuit 108/1 has been added
from the V.24 signal list.
c. Only one of the X.24 signals X, B and F can be used at the same time since they all
use the same connector pin.

The byte and frame timing signals should only be used with user signals with
a bit rate ≤ 4x64 kbit/s. With higher user data rates the probability of timing
problems is increased.
Please note:
The transmit data or timing signals can not be used to synchronize the net-
work element.
The following table shows which functions are available in which combina-
tions:
42 FOX61xLEDS1
Table 20: Function relationship

Transmission User data rate Timing signal Transport DCE interface type
mode [kbit/s] [kHz] mode V.35 V.24/V.28 RS485
X.24/V.11
Synchronous nx64 nx64, n ≤ 2 nx64 kbit/s yes yes no
a
Synchronous nx64 nx64, n ≤ 31 nx64 kbit/s yes no no
a, b
Oversampling 0 … 128 nx64, n ≤ 31 nx64 kbit/s yes yes yes
Oversampling 0 … 600 nx64, n ≤ 31 a, b nx64 kbit/s yes no yes
a. With CAS enabled the timing signal is n ≤ 30.

b. This signal is only used internally to sample the data signal. On the DCE interface
none of the timing interchange circuits will be activated.
The V.11 and RS485 receivers are terminated with a 125 Ω resistor.
The RS485 interface can be configured to 4-wire (full duplex mode) or to 2-
wire (half duplex mode). In the 4-wire mode the circuit 103 and circuit 104
must be connected to separate wire pairs. In the 2-wire mode the connector
pins of the transmit interface (103) are used:
LEDS1 LEDS1
RS485 2-wire RS485 4 -wire
Transmit 103 Transmit 103
Receive 104 Receive 104
Figure 8: RS485 2-wire and 4-wire modes
5.1.2 RS485 2-wire control

With the RS485 2-wire interface type the receive and transmit data signals
share the same wire pair. Only half duplex transmission mode is allowed for
the DTE and the DCE.
As a consequence the receive data driver (R/104) is active only when
receive data has to be applied to the line. During the receive idle phases the
receive data driver is inactive, i.e. not driving.
The LEDS1 unit offers two possibilities to control the receive data driver:
• RTS controlled mode,
• Data controlled mode.
In order to avoid flow back of receive data to the transmit direction, the trans-
mit data signal in the DCE is fixed to “1” as long as the receive data driver is
active.
5.1.2.1 RTS controlled mode
In the RTS controlled mode the receive data driver is kept active as long as
the control signal RTS (C, 105) from the remote end is active (“0”). The
receive data driver is set to inactive as long as the control signal RTS from
the remote end is inactive (“1”).
The RTS (C, 105) from the remote end is transported in the CAS bit a, i.e.
control signal transport with CAS must be available and enabled.
FOX61xLEDS1 43
Please note:
Control signal transport via CAS bits is a ABB proprietary feature.
Please note:
The data port at the remote end must be configured to interface type X.24-
V.11, V.24-V.28 or V.35, since the interface type RS485 does not support
the control signal interfaces.
5.1.2.2 Data controlled mode
In the data controlled mode the receive data driver is kept active as long as
the data is 0 and for a configurable timer period after the 0 to 1 data transi-
tion. After the expiry of the timer the receive data driver is set to inactive.
Receive data R/104

timer period
Receive data driver enabled
timer expired
Figure 9: RS485 2-wire receive data driver control
The timer period is configurable between 20 and 1500 samples of the over-
sampling clock rate. The timer has to be set at least to the duration of the
maximum continuous “1” period of the data signal, during which the driver
must be kept enabled.
Example:
Assume a data signal structure with a maximum of 9 consecutive “1” data
bits. The data signal has a data rate of 64 kbit/s, the oversampling rate is
320 kbit/s.
The timer has to be set at least to 320/64 * 9 = 45 samples
Please note:
The data controlled mode requires knowledge of the data signal structure,
i.e. about the maximum length of “1” periods.
5.1.3 Transport modes
5.1.3.1 nx64 kbit/s transport mode
The LEDS1 DCE ports support synchronous nx64 kbit/s user data rates.
For the transport over the TDM network the nx64 kbit/s data signals are
mapped to n time slots in a G.704 framed 2048 kbit/s signal.
Depending on the usage of CAS up to 30 time slots or up to 31 time slots are
available for the user data transport.
44 FOX61xLEDS1
5.1.4 Transmission modes
5.1.4.1 Synchronous transmission mode
The synchronous transmission mode is supported by LEDS1 for the nx64

kbit/s user data rates.
In transmit direction, LEDS1 expects that the incoming user signal at the
DCE interface is synchronous to the network element timing (PETS).
The incoming nx64 kbit/s user data is mapped directly to n 64 kbit/s time
slots, i.e. without any bit rate adaptation.
In receive direction, the user data rate is derived from the network element
timing. The data, control and clock signals are fed to the DCE interface with
this user data rate.
With the interface type X.24/V.11 and nx64 kbit/s user data, LEDS1 supports
the byte timing (B) or frame timing (F) signal at the DCE interface.
Please note:
Since the same DCE connector pins are used for the byte timing (B), the
frame timing (F) and the codirectional transmit signal element timing (X),
only one of these three signals can be active at the same time.
5.1.4.2 Oversampling transmission mode
The oversampling transmission mode can be used to transport DCE signals

with user data rates not corresponding to the configurable data rates. The
user data signals can be asynchronous (start-stop) signals or synchronous
signals.
This mode can also be used to have low and constant delays with low user
data rate signals.
In transmit direction, the data and control signals at the DCE interface are
oversampled with a (synchronous) clock, which is the configured clock rate.
The oversampling frequency has to be at least three to four times higher
than the user data rate. The resulting isochronous distortion corresponds to
the relation of the user data rate to the oversampling frequency, e.g. 19.5%
with a 25 kbit/s user data rate, oversampled with 2x64 kHz = 128 kHz (25/
128 = 0.195).
In receive direction, the data and control signals are output at the DCE inter-
face with the oversampling clock.
The oversampling transmission mode can be used in point-to-point, point-to-
multipoint and multipoint-to-multipoint network applications. Refer to section
Network applications (page 49).
Please note:
With the V.24/V.28 interface, the data signal rate is limited to 128 kbit/s.
Please note:
In oversampling mode, no clock signal is available at the DCE interface.
If the DTE is working in synchronous mode, i.e. with clock signals, two cases
must be considered:
FOX61xLEDS1 45
1 The DTE delivers a clock signal (X, 113): A second DCE interface must
be used to oversample and transport the clock signal to the remote DTE
in parallel to the data signal. The clock signal is handled the same as a
data signal.
LEDS1 A LEDS1 B
Transmit T/104 Receive R/103

TDM
oversampling
Receive R/103 Network Transmit T/104
DTE A
DTE B
Clock X/113 Clock S/115
TDM
oversampling
Clock S/115 Network Clock X/113
Figure 10: Oversampling when DTE delivers a clock signal
2 The DTE requires a clock signal (S, 114, 115): A second DCE interface
must be used to oversample and transport the clock signal to the remote
DTE. A third DCE interface must be used to generate the required user
clock signal.
This application is limited to the configurable user data rates of LEDS1
(nx64 kbit/s).
LEDS1 A LEDS1 B
Transmit T/104 Receive R /103
Receive R/103 oversampling Transmit T/104

TDM
DTE A Network DTE B
Clock S/114/115 oversampling Clock S/114/115
user data rate
Figure 11: Oversampling when DTE delivers no clock signal
Please note:
Specifically tailored cables have to be used for the above applications.
46 FOX61xLEDS1
5.1.5 MAC bridging
5.1.5.1 LAN modes
The port-5 on the front of the LEDS1 unit is a 10BASE-T/100BASE-TX

Ethernet port supporting the following LAN modes:
• Auto-negotiation
• 10 Mbit/s, Half duplex
• 10 Mbit/s, Full duplex
• 100 Mbit/s, Half duplex
• 100 Mbit/s, Full duplex

The LAN mode of the host connected to the LEDS1 Ethernet port must be
configured to the same PHY mode as the LEDS1 Ethernet port, e.g. both
ports configured to “auto-negotiation” or both ports configured to “100 Mbit/s
full duplex”.
→ Mixed configurations result in a non operational state of the Ethernet
interface.
5.1.5.2 WAN mode
The Ethernet frames are mapped to a nx64 kbit/s transport signal, constitut-
ing the WAN port to the TDM network.
Depending on the usage of CAS up to 30 time slots or up to 31 time slots are
available for the user data transport.
The WAN port encapsulates the MAC frames from the Ethernet port into
HDLC frames.
HDLC encapsulation at the
flag MAC frame FCS flag
WAN port
Figure 12: WAN encapsulation
5.1.5.3 Queues and priority mappings
In direction from the Ethernet port to the WAN port the LEDS1 unit offers
four queues with a size of 64 frames each. The queues can be used for the
priorisation of the user traffic according to the 802.1p priority (VLAN priority)
or the DSCP value.
In direction from the WAN port to the Ethernet port the LEDS1 unit offers one
queue with a size of 128 frames.
FOX61xLEDS1 47
LEDS1
Q1
Q2 priority
PBUS
to queue
Q3 mapping
TDM Ethernet
WAN port Q4 port
Figure 13: WAN encapsulation
The assignment of priorities to the four queues is controlled by a QoS map-

ping profile. Please refer to section Profiles (page 109) for information about
the profile handling and refer to section Profiles (page 109) for the configura-
tion of the profile parameters.
The LEDS1 unit supports four algorithms for the priority to queue mapping:
• IP
The DSCP field of the IP header determines the packet priority.
• MAC
The 802.1p priority bits of the MAC header determine the packet priority.
Untagged packets get the default priority assigned. The default priority
value is configurable.
• IP Then MAC
The DSCP field of the IP header, if it exists, determines the packet prior-
ity. Otherwise the 802.1p priority bits determine the packet priority.
Untagged packets get the default priority assigned.
• MAC Then IP
The 802.1p priority bits of the MAC header, if they exist, determine the
packet priority. Otherwise the DSCP field of the IP header determines the
packet priority.
The scheduling of the frames in the queues towards the TDM WAN interface
uses the strict priority algorithm.
Packets in the higher priority queues are handled first. Packets in lower pri-
ority queues are only processed when there are no packets left in the higher
priority queue. Q1 is the highest priority queue, Q4 is the lowest priority
queue.
Please note:
The priority mechanism does not modify the Ethernet frames.
48 FOX61xLEDS1
5.2 Network applications
The main network applications with the LEDS1 unit are

• LEDS1 in a point-to-point application.
• LEDS1 in a point-to-multipoint application.
• LEDS1 in a multipoint-to-multipoint application.
5.2.1 Point-to-point (P2P)

The point-to-point application connects one data interface (data and signal-
ling) with another data interface through a TDM network.
The connection can be protected with 1+1 SNC protection on the transport
layer.
Network element 1 Network element 2
TDM
Network
data data
interface interface
P12 transport unit
LEDS1 unit
Figure 14: Point-to-point application with LEDS1
5.2.2 Point-to-multipoint (P2MP)

In the point-to-multipoint mode of operation a master data terminal equip-
ment (master DTE) communicates via a data interface to several subordi-
nated DTEs, the so called slave DTEs through a TDM network.
Communication is established in the polling mode. The data signal from the
master DTE is sent simultaneously to all slave DTEs. The master DTE
addresses one specific slave DTE. This addressed DTE activates its trans-
mit interface to respond to the polling request. After the complete message
transfer the slave DTE deactivates its transmit interface.
Collisions must be prevented by using suitable communication protocols
between the DTEs.
The slave DTEs can be distributed across several FOX61x sites. The maxi-
mum number of slave DTEs is therefore practically limited only by the com-
munication protocol applied.
Using the RS485 interface type up to 32 RS485 unit loads can be connected
to one LEDS1 user port simultaneously.
FOX61xLEDS1 49
Using the V.35, X.24/V.11 or V.24/V.28 interface type only one DTE can be
connected to one LEDS1 user port simultaneously.
The connection in the TDM network can be protected with 1+1 SNC protec-
tion on the transport layer.
The combination of the data signals and the signalling is accomplished with
one central conference (preferred solution for a star network) or with several
conference circuits placed at all network elements with connected slave
DTEs (preferred solution for a linear network).
Please note:
The point-to-multipoint network setup supports the multi-master type network
topology.
5.2.2.1 Linear network setup
The point-to-multipoint application in a linear network connects one master

data interface located at one end of the linear network with several slave
data interfaces through a TDM network.
When the master terminal sends, it sends in direction towards the slaves,
and all slave terminals can receive the sent signal.
When a slave terminal sends, it sends in direction towards the master, and
only the master can receive the sent signal.
The connection between any two network elements can be protected with
1+1 SNC protection on the transport layer
It is also possible to implement a shared protection ring (SPR) for the protec-
tion of the complete LEDS1 network. For further information please refer to
1KHW002467 FOX61x TDM Services.
to to
Master master
Intermediate slave slave
Tail end slave
Network element 1 Network element k Network element n
TDM TDM
Network Network
data data
interface local
interface
master
data
interface
P12 transport unit
Conference on
LEDS1 unit
LEDS1 unit
Figure 15: Point-to-multipoint linear application with LEDS1
50 FOX61xLEDS1
5.2.2.2 Star network setup
The point-to-multipoint application in a star network connects one master

data interface with several slave data interfaces through a TDM network.
When the master terminal sends, it broadcasts towards the slaves, and all
slave terminals can receive the sent signal.
When a slave terminal sends, it sends in direction towards the master, and
only the master can receive the sent signal.
In case that more than one DTE is connected to a slave network element a
local conference can be setup at this location. This is shown in the Figure 16
below at the Slave 3 network element.
The connection between any two network elements can be protected with
1+1 SNC protection on the transport layer
to
master
Slave 1
to slave
Master or local
TDM data
1 1
Network interface
2
to
master Slave 2
3
TDM 1
data
Network interface
to
to master
Slave 3
data master
interface TDM
master Network to slave
or local
P12 transport unit

1 2
Conference on
LEDS1 unit
data
interface
LEDS1 unit
data
interface
Figure 16: Point-to-multipoint star application with LEDS1
FOX61xLEDS1 51
5.2.3 Multipoint-to-multipoint (MP2MP)

The multipoint-to-multipoint mode of operation is very similar to the point-to-
multipoint mode of operation. Differences are outlined below.
Please note:
The multipoint-to-multipoint network setup supports the multi-master type
network topology.
5.2.3.1 Linear network setup
In the multipoint-to-multipoint application, when a slave terminal sends, it

sends in direction towards the master and towards the tail end slave, and all
master and slave terminals can receive the sent signal.
Please note:
At an intermediate slave in the multipoint-to-multipoint application the differ-
entiation between “to master” and “to slave” is done from a protocol point of
view. The conferencing is the same for all participants, irrespective if they
are “local”, “to master” or “to slave”.
to to
Master master
Intermediate slave slave
Tail end slave
Network element 1 Network element k Network element n
TDM TDM
Network Network
data data
interface interface
master
local
data
P12 transport unit interface
Conference on
LEDS1 unit
LEDS1 unit
Figure 17: Multipoint-to-multipoint linear application with LEDS1
5.2.3.2 Star network setup
In the multipoint-to-multipoint application, when a slave terminal sends, it

sends in direction towards the master and towards the locally connected
slaves, and the master forwards the received signal to all other slaves. All
the master and slave terminals can receive the sent signal.
52 FOX61xLEDS1
to
master
Slave 1
to slave
Master or local
TDM data
1 1
Network interface
2
to
master Slave 2
3
TDM 1
data
Network interface
1
to
to master Slave 3
data master
interface TDM
master Network to slave
or local
P12 transport unit
Conference on
1 2
LEDS1 unit
LEDS1 unit
data
interface
data
interface
Figure 18: Multipoint-to-multipoint star application with LEDS1
5.3 Conferencing
5.3.1 Resources
5.3.1.1 Conference resources
The LEDS1 unit has a fixed amount of resources available for data confer-
ences. Each conference that is created consumes resources according to
the maximum number of conference participants and to the participants
bandwidth.
• The maximum number of conference participants must be configured
when the conference is created. The following values are available:
− Maximum number of participants p = 4, or
− Maximum number of participants p = 8, or
− Maximum number of participants p = 16.
FOX61xLEDS1 53
If later on a higher number of participants is required the conference must

be deleted and newly created with the appropriate maximum number of
participants.
• The conference participants bandwidth must be configured when the con-
ference is created. The following values are available:
− Rate = 64 kbit/s, i.e. number of time slots n = 1, to
− Rate = 1984 kbit/s, i.e. number of time slots n = 31.
The conference participants bandwidth can’t be modified.
The resources consumed by a conference is calculated with
RC = p x n
Example:
A conference with 8 participants and a participant bandwidth of
6x64=384 kbit/s requires conference resources of
RC = 8 x 6 = 48 time slots.
The sum of all conference resources is restricted to 848 time slots per
LEDS1 unit:
RU = Σ RC ≤ 848 time slots.
The maximum number of conferences with 4 participants is
C4max = 848/4 = 212.
C8max = 848/8 = 106.
C16max = 848/16 = 53.
Due to the fact that the building block for data conferences is a 16 participant
conference with a bandwidth of 1 time slot, one building block can be used to
create one conference with 16 participants, or two conferences with 8 partici-
pants, or four conferences with 4 participants.
The following formulas apply for the calculation of the used conference
resources, where np is the number of time slots used in conferences with p
participants:
• Number of conferences with 4 participants =
C4 = Σ n4 + Σ 2xn8 + Σ 4xn16
C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16
C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16
Example:
Assume four conferences:
− conference 1 with 4 participants and 192 kbit/s (n=3),
The used resources are as follows:
C4 = Σ n4 + Σ 2xn8 + Σ 4xn16
= (3+10) + 2x5 + 4x31 = 147
C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16
= round-up ((3+10)/2) + 5 + 2x31 = 74
54 FOX61xLEDS1
C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16

= round-up ((3+10)/4) + 5/2) + 31 = 37
The remaining resources are as follows:
C4 = 212 - 147 = 65, or
C8 = 106 - 74 = 32, or
C16 = 53 - 37 = 16.
conference 1, 3 time slots conference 2, 10 time slots
1
2 conference 3, 5 time slots
3
4
5
6 conference 4, 31 time slots
7
10
15
20
25
30
35 remaining resources
37
40
45
50
53
Legend:
conference, 4 participants, 1 time slot
Figure 19: Conference resource usage example with 4 conferences
Please note:
The remaining conference resources can be read from the LEDS1 unit sta-
tus dialogue.
5.3.1.2 PBUS resources
The LEDS1 unit accesses the PBUS (FOX61x TDM bus) with a maximum
capacity of 32 P12 signals, each having 32 time slots. Five P12 signals are
reserved for the user ports and 27 P12 are reserved for the conference par-
ticipants.
Each participant can only access one P12 signal, i.e. it is not possible to split
the participants data signal to more than one P12 signal. This has the conse-
FOX61xLEDS1 55
quence that depending of the participants bandwidths not the full available
PBUS bandwidth can be used.
In the example below the remaining PBUS resources are:
• 7 participants with maximum 31x64 = 1984 kbit/s,
• 1 participant with maximum 27x64 = 1728 kbit/s,
• 2 participants with maximum 4x64 = 256 kbit/s,
• 24 participants with maximum 1x64 = 64 kbit/s.
P12 TS
0 4 9 14 19 24 29 31
P12-0
5 x P12 reserved for user ports

P12-4
conference 1,
P12-9 4 participants,
3 time slots,
conference 2,
P12-14 4 participants,
10 time slots,
conference 3,
P12-19
8 participants,
5 time slots,
P12-24 conference 4,
16 participants,
31 time slots,
P12-29
P12-31 remaining resources
Legend:
conference participant with 31 time slots
Figure 20: PBUS resource usage example with 4 conferences
Please note:
A P12 resource with 32 free timeslots is shown as two remaining resources:
→ 1 participant with maximum 31x64 = 1984 kbit/s, and
→ 1 participant with maximum 1x64 = 64 kbit/s.
To make best use of the available PBUS bandwidth, the resource usage
strategy must be taken into account when creating conferences. The
resource usage strategy is as follows:
• The P12 resources for conferences are grouped, according to the PBUS
line usage. Each PBUS line multiplexes 4 P12 resources:
− group 1: P12-5 to P12-7 (only 3 P12 resources),
− group 2: P12-8 to P12-11,
− group 3: P12-12 to P12-15,
− group 4: P12-16 to P12-19,
− group 5: P12-20 to P12-23,
− group 6: P12-24 to P12-27,
− group 7: P12-28 to P12-31.
• The groups are populated with participants from group 1 to group 7. A
new group is accessed when there are no remaining resources left for a
participant.
56 FOX61xLEDS1
• Each group is populated with participants

− first from the lowest numbered timeslot on any of the groups P12 to
the highest numbered timeslot, and
− second from the groups lowest numbered P12 to the highest num-
bered P12.
Example with conference 3 (8 participants, 5 timeslots):
• The group 1 is occupied with conference1 and conference 2 as follows:
− P12-5: timeslot 0 to timeslot 15,
− P12-6: timeslot 0 to timeslot 22,
− P12-7: timeslot 0 to timeslot 12.
• Participant-1 of conference-3 is placed on timeslots 13 to 17 of P12-7.
• Participant-8 of conference-3 has to be placed in group 2 since the maxi-
mum available resource in group 1 is 4 timeslots in P12-6 and P12-7. It is
placed on timeslots 0 to 4 of P12-8.
Please note:
Only created participants make use of PBUS resources.
→ The parameter “maximum number of participants” of a conference
does not influence the PBUS resource usage.
Please note:
The remaining PBUS resources usable for additional participants can be
read from the LEDS1 unit status dialogue.
5.3.2 Local Conferences

Conferences are accessible for local participants, i.e. from LEDS1 ports or
any other data unit in the network element. The conferences include also the
participants from the “to master” and “to slave” direction, i.e. from other net-
work elements, transported via the TDM network.
The data conference function performs the addition of the data signals. The
data signals are combined with a wired-AND operation. The wired-AND
requires all inactive terminals to send a continuous “1”-signal.
It is possible to control the data access of a participant to the conference by
the associated C/105 control signal. Refer to section Conference control
(page 59) for further information.
The control signals transported in the CAS a and b bits of all participants are
combined in a wired-AND function, i.e. if any of the participants exhibits an
active state (CAS-bit = 0), this active state is inherited to the combined CAS
signal.
FOX61xLEDS1 57
P12 transport,
master /slave
participants
1+1 protection
switching,
Data
AND Data
e.g. LEDE1 cross connect

CAS
AND CAS
remote
P12 transport, participants
e.g. LEDE1 conference
PBUS
local LEDS1
participants
LEDS1
local
participants 1
local
participants
DTU/DTM DATI1 nx64 kbit/s DCE
processing interface
4
Figure 21: Local conference on LEDS1
5.3.3 Conferences in the P2MP application

Conferences in the point-to-multipoint application add the data and control
signals of the local participants to the signal going towards the master. The Σ
symbol stands for the wired-AND function.
There is no addition in the direction to the last slave or towards the local par-
ticipants.
to master to slave
PBUS
PBUS
local local
1 n
Figure 22: Conference in the P2MP application
5.3.4 Conferences in the MP2MP application

Conferences in the multipoint-to-multipoint application consist of a number of
sub-conferences. The number of sub-conferences corresponds to the num-
ber of participants. The sub-conference of each participant adds the data
and control signals of all participants except the own signal.
The designation “to master” or “to slave” has no relevance for the conference
itself, since the setup is symmetrical in relation to the network directions. The
“to master” and “to slave” participants are nevertheless required for the setup
of the transport cross connections.
58 FOX61xLEDS1
to master to slave
PBUS
Σ Σ
1 2 3 4 n 1 2 3 4 n
1
2 2
3
4
n
Σ 1
3
4 Σ n
PBUS
local 2 3 4 local
1 n
Figure 23: Conference in the MP2MP application
5.3.5 Conference control

In a conference all inactive participants must access the conference with a
constant “1” signal state. Only the active participant is allowed to access the
conference with “1” and “0” signal states.
There are two methods to have the inactive participants in the constant “1”
state:
• Intrinsic access:
− In the inactive state the connected DTEs must send constantly a “1”
state.
− If a slave DTE is polled from the master DTE it immediately can start
to send.
• Controlled access:
− In the inactive state the connected DTEs must set the C/105 control
signal to OFF. The state of the C/105 control signal must be forwarded
to the conference, i.e.
- the ports control signal “105 (RTS, C)” must be set to “From-DTE”,
- the ports “signalling to network” parameter must be set to “Yes”,
- the participants “signalling to conference” parameter must be set to
“Yes”,
- the participants “signalling from conference” parameter must be set
to “Yes”,
- the participants “conditional interconnection” parameter must be
set to “Yes”.
The participants data signal entering the conference is set to “1”.
− If a slave DTE is polled from the master DTE it sets the C/105 control
signal to ON. The DCE (i.e. LEDS1 port) responds by setting the I/109
control signal to ON with a configurable delay. Now the DTE can start
to send. The participants data signal enters the conference transpar-
ently.
To permit the master DTE to synchronize it is recommended to transmit a
short bit sequence (e.g. flag stream or idle code) from the slave DTE prior to
the user data.
FOX61xLEDS1 59
Please note:
The controlled access of a participant to a conference is only available if
CAS is available (nx64 kbit/s data rate).
Please note:
If using the control signal 109/I to enable the DTE transmitter the delay time
in the LEDS1 at the slave DTE location from control signal 105/C = ON to
control signal 109/I = ON must be configured to at least 20 ms when using
the oversampling transmission mode.
The DCE interfaces of LEDS1 are able to supervise the send time and idle
time of the DTE and to detach it from the connection point if the correspond-
ing limits are exceeded. This prevents that the system will be locked by a
slave DTE which continuously sends data. Refer to section DTE send and
idle time restrictions (page 101).
5.4 Data handling
5.4.1 Port data handling

With each of the 4 user ports the LEDS1 unit offers a DCE interface with
data, control and timing signals. The data signals are the transmit signal T/
103 and the receive signal R/104.
Signal Signal Consequent Out of

Squelch Loop 3c Loop 2b Loop 3b
monitor inversion action service
T/103 1
1
0 0
1 Data signal
01
1 1 0
01 Processing 1 to PBUS
2-wire / Signal Test pattern Out of Consequent Protection

4-wire monitor Loop 3c Loop 2b insertion Loop 3b service action switch
1 Working data signal

Processing 0
from PBUS
R/104 1 1 Protecting data signal
0
01 from PBUS
1
01
Figure 24: Data transport
The data handling can be configured with the following control and mainte-
nance mechanisms:
• Interface mode 2-wire or 4-wire:
The RS485 interface type can be configured to 2-wire mode, i.e. half
duplex mode of the RS485 bus, or to 4-wire mode, i.e. full duplex mode
of the RS485 bus.
With the 2-wire mode the squelch function inserts a “1” signal in transmit
direction as long as the driver in receive direction is active.
All other interface types use the full duplex mode with separate transmit
and receive signals.
60 FOX61xLEDS1
Please note:
The signal monitoring status on the receive data signal shows the signal sta-
tus before the buffer in receive direction.
→ With the RS485 2-wire interface type and RTS controlled mode there
can be activity on the data signal also when the buffer in receive direc-
tion is disabled. The activity is shown in the port status “To DTE”
parameters.
• Data signal inversion (transmit signal T/103 and receive signal R/104):
In order to be compatible with DTEs using inverted logic, the transmit and
the receive data signal can be inverted.
• Consequent action (transmit signal T/103):
On a detected failure in the transmit data signal T/103 or the transmit tim-
ing signal X/113, the data is replaced with a “1” or “0” signal. The conse-
quent action can be disabled.
On a detected send or idle time filter violation the data is replaced with a
“1” signal. The consequent action can be disabled.
Please note:
The level detection on the transmit data signal T/103 is not available for the
RS485 2-wire interface type.
• Loop 3c:
The maintenance function “Loop 3c” loops the transmit data signal back
to the receive direction. For details please refer to section Loop 3c
(page 98).
• Loop 2b:
The maintenance function “Loop 2b” loops the receive data signal back to
the transmit direction. For details please refer to section Loop 2b
(page 97).
• Loop 3b:
The maintenance function “Loop 3b” loops the transmit data signal back
to the receive direction. For details please refer to section Loop 3b
(page 98).
• Interface line state “out of service”:
The maintenance function “out of service” of an interface replaces the
transmit signal going to the PBUS by a “1” signal.
In receive direction the data signal from the PBUS is replaced by a “1”
signal.
• Interface line state “test pattern insertion”:
The maintenance function “test pattern insertion” replaces in receive
direction the data signal by a continuous test pattern “1010”.
• Protection switching:
In receive direction a working and a protecting channel can be config-
ured. Switching criteria are “trail signal fail” and “trail signal degrade” from
the P12 transport unit. With CAS enabled in the CTP configuration, CAS
AIS is an additional switching criterion.
• Consequent action (receive signal R/104):
On a detected failure in the receive signal the data is replaced with a “0”
or “1” signal.
FOX61xLEDS1 61
5.4.2 Conference data handling

The LEDS1 unit offers data conferences with a maximum of 16 participants
per conference. The transmit data signals of all participants are combined in
a wired-AND function, i.e. if any of the participants exhibits an active state
(“0”), this active state is inherited to the combined data signal.
With X-interface type conferences the byte and frame timing is maintained.
In the multipoint-to-multipoint (MP2MP) application, all participants are han-
dled identically. Each participant has its own sub-conference. The sub-con-
ference of each participant adds the data signals of all participants except
the own signal.
Test pattern Set out of Conditional Signalling to Consequent Protection

insertion service interconnection conference action switch
C/105
0 1 Working data signal

01
P1 1 from PBUS
Protecting data signal Participant 1:
1
1 from PBUS local or
to master or
P2
to slave
P3
Pn
Σ 1
data signal
to PBUS

C/105

01
P2 1 from PBUS
1
to master or
P1
to slave
P3
Pn
Σ 1
data signal
to PBUS

C/105
01
P3 1 from PBUS
1
to master or
P1
to slave
Σ
P2
data signal
Pn 1 to PBUS

C/105

01
Pn 1 from PBUS
Protecting data signal Participant n :
1
to master or
P1
to slave
Σ
P2
P3 data signal
1 to PBUS
Figure 25: Conference data transport, MP2MP
62 FOX61xLEDS1
In the point-to-multipoint (P2MP) application, only the participant “to master”

has a sub-conference, adding the data signals of all other participants except
the own signal. The other participants (“local” or “to slave”) receive their data
signal from the “to master” participant.

C/105

01
P1 1 from PBUS
Protecting data signal
1
1 from PBUS Participant 1:
to master
P2
P3
Pn
Σ 1
data signal
to PBUS

C/105

01
P2 1 from PBUS
1 Participant 2:
to slave
P1 data signal
1 to PBUS

C/105
01
P3 1 from PBUS
1 Participant 3:
to slave
P1 data signal
1 to PBUS

C/105

01
Pn 1 from PBUS
1 Participant n :
to slave
P1 data signal
1 to PBUS
Figure 26: Conference data transport, P2MP
The data handling can be configured with the following control mechanisms:
• Participant configuration “signalling to conference”:
The “signalling to conference” parameter allows to control the forwarding
of control signals towards the conference. This parameter influences also
the forwarding of the data signal in case of the conditional interconnection
(see below). If “signalling to conference” is set to “No” the “conditional
interconnection” parameter set to “Yes” disables the forwarding of the
data signal.
FOX61xLEDS1 63
• Participant configuration “conditional interconnection”:

The conditional interconnection function allows to control the access of a
participants data signal to the conference by the signal state of the con-
trol signal C/105, which has to be available at the conference input, i.e.
the port configuration must enable the forwarding of control signals to the
network (“signalling to network” = “Yes”) and the participant configuration
must enable the forwarding of control signals to the conference (“signal-
ling to conference” = “Yes”.
• Participant line state “out of service”:
The maintenance function “out of service” of a participant replaces the
transmit signal going to the PBUS by a “1” signal.
In receive direction the data signal from the PBUS is replaced by a “1”
signal.
• Participant line state “test pattern insertion”:
The maintenance function “test pattern insertion” replaces in receive
direction the data signal by a continuous test pattern “1010”.
• Consequent action (receive direction):
signal.
5.5 Control signal handling
5.5.1 Overview
Depending on the interface type used different control signals are available.
Refer to Table 19: Data, control and timing signals with their electrical char-
acteristics (page 41).
• C/105 (to DCE)
In normal operation the control signal C/105 is used by the DCE as an
indication that the DTE is ready to transmit data.
When using CAS the state of the control signal C/105 can be transported
to the remote DCE in the CAS a bit.
• 106 (from DCE)
The control signal 106 informs the DTE that it can start to send data.
The state of the control signal 106 can be controlled by the local control
signal 105 with various delay settings. The delay time can be configured
to
− 0, 10, 20 or 40 ms.
The delay is active for the OFF to ON and ON to OFF state transitions.
• 107 (from DCE)
The control signal 107 informs the DTE that the remote DTE is in fault
free operation.
When using CAS the state of the control signal 107 can be controlled by
the remote DCE via the CAS b bit which transports the remote state of
the control signal 108.
64 FOX61xLEDS1
• 108 (to DCE)

The control signal 108 is used to inform the DCE that the DTE is fault free
and in operation.
When using CAS the state of the control signal 108 can be transported to
the remote DCE in the CAS b bit.
• I/109 (from DCE)
The control signal I/109 is used to ready the DTE for receiving data from
the DCE.
The state of the control signal I/109 can be controlled by the local control
signal C/105 with various delay settings. The delay time can be config-
ured to
− 0, 10, 20 or 40 ms.
The delay is active for the OFF to ON and ON to OFF state transitions.
When using CAS the state of the control signal 109/I can be controlled by
the remote DCE via the CAS a bit which transports the remote state of
the control signal C/105.
LEDS1
C/105 from DTE
ON
CAS a bit
OFF
V.110/SB bit
X.30/S bit
108 from DTE
ON CAS b bit
OFF
V.110/SA bit
∆T
TDM
DTE Network
CAS b bit
107
ON
OFF V.110/SA bit
CAS a bit
I/109
ON
V.110/SB bit
OFF X.30/S bit
106 V.110/X bit

ON
OFF
Figure 27: Control signal handling overview
The control signals can be configured according to the tables below:
FOX61xLEDS1 65
Table 21: Control signal handling

Control signal X.24 V.35 V.24
C/105 from DTE from DTE from DTE
ON, fixed ON, fixed ON, fixed
OFF, fixed OFF, fixed OFF, fixed
OFF, from defect a OFF, from defect a OFF, from defect a
106 - from local 105 from local 105
ON, fixed ON, fixed
OFF, fixed OFF, fixed
OFF, from defect b OFF, from defect b
107 - from b bit (CAS) from b bit (CAS)
ON, fixed ON, fixed
OFF, from defect b OFF, from defect b
108 - from DTE from DTE
ON, fixed ON, fixed
OFF, from defect a OFF, from defect a
I/109 from local C from local 105 from local 105
from a bit (CAS) from a bit (CAS) from a bit (CAS)
ON, fixed ON, fixed ON, fixed
OFF, fixed OFF, fixed OFF, fixed
OFF, from defect b OFF, from defect b OFF, from defect b
a.The control signal towards the network is set to OFF as a consequent action when a
defect is detected in the transmit data or clock signal from the DTE.
b.The control signal is set to OFF as a consequent action when a defect is detected in
the signal from the network and the signal is not fixed to ON.
Please note:
The a bit and the b bit are only transmitted to the PBUS when CAS is ena-
bled, i.e. when the “signalling to network” parameter is set to “yes”.
Please note:
With active loops the control signals are controlled according to the specific
loop.
→ Refer to section Loops (page 96).
Please note:
The RS485 interface type supports no control signals.
66 FOX61xLEDS1
5.5.2 CAS signalling transport

The CAS provides the four signalling bits abcd. The bits a and b can be used
to transport the control signal status from the local DCE to the remote DCE.
Table 22: CAS bits usage

CAS bits abcd Description
1101 CAS bits not used (idle)
1xxx Control signal transport C to I (X-type),
Control signal transport 105 to 109 (V-type),
signal state OFF
0xxx Control signal transport C to I (X-type),
Control signal transport 105 to 109 (V-type),
signal state ON
x1xx Control signal transport 108 to 107 (V-type),
signal state OFF
x0xx Control signal transport 108 to 107 (V-type),
signal state ON
xx01 Default value
1111 Forward alarm indication (AIS)
LEDS1 A LEDS1 B
105 a bit a bit 109
DTE CAS CAS DTE
TDM
A 108 b bit Network b bit 107 B
LEDS1 A LEDS1 B
DTE C a bit CAS CAS a bit I DTE

TDM
A Network
B
Figure 28: Control signal status to a-bit and b-bit mapping
The abcd bits of a time slot are sampled every 2 ms in the P12 transport sig-
nal.
5.5.3 Port control signal handling

With each of the 4 DCE interfaces the LEDS1 unit offers up to 3 control sig-
nal inputs and up to 4 control signal outputs, refer to Table 19: Data, control
and timing signals with their electrical characteristics (page 41).
FOX61xLEDS1 67
Failure on Signalling
Loop 3c Loop 2b Configuration Loop 3b Out of service
T/103 to network
C/105
OFF
OFF
ON
OFF
108
CAS signalling
OFF
1101
1111 to PBUS
OFF
OFF
ON
OFF
OFF
∆T
Test pattern
Config Loop 3c Loop 2b Loop 3b Consequent Protection
Out of service
action switch
Working data signal

from PBUS
107 CAS b bit Protecting data signal
ON OFF 1111 from PBUS
OFF OFF
I/109 CAS a bit

ON OFF
OFF OFF
106
ON
OFF
141 Loop
3c
Configuration
Loop state
142
ON
OFF
Figure 29: Control signal transport
The control signal handling can be configured with the following control and
maintenance mechanisms:
• Consequent action on a failure of the T/103 data signal or of the X/113
timing signal:
On a detected failure in the transmit signal the control signals C/105 and
108 towards the network are set to OFF.
• Configuration in transmit direction:
The incoming control signals C/105 and 108 can be replaced by a fixed
ON or OFF value.
• Loop 3c:
The maintenance function “Loop 3c” loops the control signal 108 back to
the control signal 107 and loops the control signal C/105 back to the con-
trol signal I/109. In transmit direction the control signals C/105 and 108
are set to OFF. The loop is near the DCE interface. For details please
refer to section Loop 3c (page 98).
68 FOX61xLEDS1
• Loop 2b:
If the control signals C/105 or 108 are configured to “from DTE”, the
maintenance function “Loop 2b” loops the control signal I/109 received
from the network back to the control signal C/105 and loops the control
signal 107 received from the network back to the control signal 108. If the
control signals C/105 or 108 are not configured to “from DTE”, the control
signals C/105 and 108 towards the network remain unchanged.
In receive direction the control signals 107, I/109 and 106 are set to OFF.
The loop is near the DCE interface. For details please refer to section
Loop 2b (page 97).
• Loop 3b:
The maintenance function “Loop 3b” loops the control signal 108 back to
the control signal 107 and loops the control signal C/105 back to the con-
trol signal I/109. In transmit direction the control signals C/105 and 108
are set to OFF. The loop is near the PBUS interface. For details please
refer to section Loop 3b (page 98).
• Control signal transport, transmit direction:
If CAS is used in the nx64 kbit/s mode the state of the control signal C/
105 is transported to the remote DCE via the CAS a bit and the state of
the control signal 108 is transported to the remote DCE via the CAS b bit.
The CAS pattern is inserted in all positions of the used time slots.
The transport of signalling information towards the network can be disa-
bled with the “signalling to network” parameter set to “No”:
In the nx64 kbit/s mode the CAS abcd pattern is the idle pattern “1101”.
• Interface line state “out of service”, transmit and receive direction:
In transmit direction the AIS-CAS pattern (1111) is inserted in all posi-
tions of the used time slots and the TSD and TSF signals are activated.
TSF and TSD are the FOX61x internal failure signals used to control the
protection switching.
In receive direction the control signals 106, 107 and I/109 are all set to
OFF.
• Consequent action (receive control signals):
or “0” signal (refer to the section Port data handling (page 60)). The CAS
is replaced with the CAS-AIS pattern. Consequently all control signals are
set to OFF.
• Control signal transport, receive direction:
If CAS is used in the nx64 kbit/s mode the state of the control signal I/109
can be controlled from the remote DCE via the CAS a bit and the state of
the control signal 107 can be controlled from the remote DCE via the
CAS b bit. The CAS pattern of the first used time slot is evaluated.
• Interface line state “test pattern insertion”:
The maintenance function “test pattern insertion” sets in receive direction
the control signals 106, 107 and I/109 to OFF.
• Configuration in receive direction:
The outgoing control signal 106 can be replaced by a fixed ON or OFF
value.
The outgoing control signal 107 can be replaced by a fixed ON or OFF
value or can be controlled by the control signal 108.
FOX61xLEDS1 69
The outgoing control signal I/109 can be replaced by a fixed ON or OFF

value or can be controlled by the control signal C/105 with a configurable
delay.
Please note:
The nx64 kbit/s mode not using CAS provides no means for the transport of
control signals to the remote DCE.
→ Use CAS to enable control signal transport. This is an ABB proprietary
feature.
→ CAS is enabled when the configuration parameter “Signalling to net-
work” is set to “Yes”
Please note:
If a port requires CAS for the control signal transport CAS must be enabled
on the P12 transport signal.
→ The termination mode of the P12 transport signal must be set to
“PCM30” or “PCM30C”.

It is possible to create a cross connection from a LEDS1 port using CAS to
another CTP not using CAS.
→ This would result in a non operational control signal transport.
5.5.4 Conference control signal handling

The LEDS1 unit offers conferences with a maximum of 16 participants per
conference. The transmit control signals of all participants are combined in a
wired-AND function, i.e. if any of the participants exhibits an active state
(ON), this active state is inherited to the combined control signal.
With nx64 kbit/s the control signals are extracted from the CAS a and b bits
of the first used time slot. The combined signal is reinserted into the CAS a
and b bits in all positions of the used time slots.
With X-interface type conferences the byte and frame timing is maintained.
In the multipoint-to-multipoint (MP2MP) application, all participants are han-
dled identically. Each participant has its own sub-conference. The sub-con-
ference of each participant adds the control signals of all participants except
the own signal.
70 FOX61xLEDS1
Test pattern Conditional Signalling to Consequent Protection

Out of service interconnection conference action switch
C/105 Working data signal

0 from PBUS
CAS a bit Protecting data signal
1111 from PBUS
OFF
a1 OFF
b1
OFF
CAS b bit
Participant 1:
OFF local or
OFF
to master or
to slave
a2
a3
an
& Signalling from
conference
Out of
service
b2
&
b3
CAS signalling
bn
1101 1111 to PBUS

C/105
Working data signal
0 from PBUS
1111 from PBUS
OFF
a2 OFF
b2
OFF
CAS b bit
Participant 2:
OFF local or
OFF
to master or
to slave
a1
a3
an
& Signalling from
conference
Out of
service
b1
&
b3
CAS signalling
bn
1101
1111 to PBUS


0 from PBUS
1111 from PBUS
OFF
an OFF
bn
OFF
CAS b bit
Participant n :
OFF local or
OFF
to master or
to slave
a1
&
a2 Signalling from Out of
conference service
b1
b2
& 1101
1111
CAS signalling
to PBUS
Figure 30: Conference control signal transport, MP2MP
In the point-to-multipoint (P2MP) application, only the participant “to master”

has a sub-conference, adding the control signals of all other participants
FOX61xLEDS1 71
except the own signal. The other participants (“local” or “to slave”) receive
their control signal from the “to master” participant.


0 from PBUS
1111 from PBUS
OFF
a1 OFF
b1
OFF
CAS b bit
OFF Participant 1:
OFF
to master
a2
a3
an
& Signalling from
conference
Out of
service
b2
&
b3
CAS signalling
bn 1101 1111 to PBUS

C/105
Working data signal
0 from PBUS
1111 from PBUS
OFF
a2
OFF
b2
OFF
CAS b bit
OFF Participant 2:
OFF local or
to slave
Signalling from Out of

conference service
a1
b1 CAS signalling
1101
1111 to PBUS


0 from PBUS
1111 from PBUS
OFF
an OFF
bn
OFF
CAS b bit
OFF Participant n :
OFF local or
to slave
Signalling from Out of

conference service
a1
b1 CAS signalling
1101 to PBUS
1111
Figure 31: Conference control signal transport, P2MP
72 FOX61xLEDS1
The control signal handling can be configured with the following control
mechanisms:
• Consequent action:
or “0” signal (refer to the section Conference data handling (page 62)).
The CAS is replaced with the CAS-AIS pattern. Consequently all control
signals are set to OFF.
• Control signal transport, receive direction:
If CAS is used in the nx64 kbit/s mode the a and b bits are demapped
from the CAS. The CAS pattern of the first used time slot is evaluated.
Control signals can be blocked from accessing the conference circuit with
the “signalling to conference” parameter set to “No”. In this case the con-
trol signals are set to OFF.
If the “conditional interconnection” parameter is set to “Yes”, the control
signals are only forwarded to the conference if the CAS a bit, correspond-
ing to the control signal C/105, is ON.
• Participant state “out of service”:
The maintenance function “out of service” of a participant simulates a fail-
ure of the participant in receive and transmit direction.
In the nx64 kbit/s mode the a and b bits are set to OFF in receive direc-
tion. In transmit direction the CAS-AIS pattern (1111) is inserted in all
positions of the used time slots and the TSD and TSF signals are acti-
vated. TSF and TSD are the FOX61x internal failure signals used to con-
trol the protection switching.
• Participant state “test pattern insertion”:
If CAS is used in the nx64 kbit/s mode the a and b bits are set to OFF in
receive direction.
• Control signal transport, transmit direction:
If CAS is used in the nx64 kbit/s mode the a and b bits are mapped to the
CAS. The CAS pattern is inserted in all positions of the used time slots.
Control signals can be blocked from accessing the network with the “sig-
nalling from conference” parameter set to “No”:
In the nx64 kbit/s mode the CAS pattern in transmit direction is replaced
by the default pattern (1101).
Please note:
The nx64 kbit/s mode not using CAS provides no means for the transport of
control signals to the remote DCE.
→ Use CAS to enable control signal transport. This is an ABB proprietary
feature.
→ CAS is enabled with the following configuration parameters set to
“Yes”:
“Signalling to conference”,
“Signalling from conference”.
FOX61xLEDS1 73
Please note:
If a conference participant requires CAS for the control signal transport CAS
must be enabled on the P12 transport signal.
→ The termination mode of the P12 transport signal must be set to
“PCM30” or “PCM30C”.

It is possible to create a cross connection from a LEDS1 conference partici-
pant using CAS to another CTP not using CAS.
→ This would result in a non operational control signal transport.
5.6 Timing handling
5.6.1 DTE synchronization

In the connection to a DTE, LEDS1 acts as a DCE.
5.6.1.1 Codirectional timing
With codirectional timing the data signal is in both directions, to and from the
DTE, accompanied by its corresponding clock signal. The source for the
receive timing signal is the DCE, the source for the transmit timing signal is
the DTE.
Since the LEDS1 expects the transmit data signal to be synchronous to the
network element timing (PETS), the transmit timing signal must be synchro-
nized to the receive timing signal inside the DTE (loop timing).
Transmitted data 103
Transmitter signal element timing (DTE) 113 LEDS1
DTE DCE
V-type Received data 104 V-type
Receiver signal element timing 115
Transmit T
DTE transmit signal element timing X LEDS1
DTE DCE
X-type Receive R X-type
Signal element timing S
Figure 32: Codirectional timing
5.6.1.2 Contradirectional timing
With contradirectional timing the DCE is the source for the transmit and the
receive timing signals.
With the X.24/V.11 interface type, the byte timing or frame start identification
signal is available.
74 FOX61xLEDS1
Transmitted data 103

Transmitter signal element timing (DTE) 113 LEDS1
DTE DCE
V-type Received data 104 V-type
Receiver signal element timing 115
Transmit T
DTE transmit signal element timing X LEDS1
DTE DCE
X-type Receive R X-type
Signal element timing S
Figure 33: Contradirectional timing
Please note:
Contradirectional timing is problematic with higher user data rates, i.e. when
the delay time on the interconnection from the DCE to the DTE and back to
the DCE is in the range of a half unit interval (UI) of the user data rate. In this
case the correct sampling of the data signal can not be guaranteed with the
fixed timing configuration. The adaptive timing configuration should be used
instead.
Please note:
The adaptive timing configuration should not be used together with the byte
timing since the timing relationship between signal element timing and byte
timing is then no more defined.
5.6.2 Port timing signals

Timing signals are used in the synchronous transmission mode of the DCE
interface. With the oversampling transmission mode the timing signals are
not used and are correspondingly disabled.
All timing signals generated by the LEDS1 unit, i.e. 114, 115, S, B and F are
synchronous to the network element timing source, i.e. the PETS. The
nx64 kHz timing signals are derived with appropriate dividers from the PETS.
The frame timing signal F is synchronous to the G.704 frame on the PBUS.
Frame timing is only available for nx64 kbit/s signals.
The byte timing signal B is synchronous to the octet boundaries of the
receive data signal.
Frame timing and byte timing are only available with the X-type DCE inter-
faces. They are exclusively used with the DTE transmit timing signal X.
FOX61xLEDS1 75
Signal Consequent Transmit

Loop 2b
monitor action timing
X/113
T/103
∆φ
B/F Loop 2b B or F
timing Configuration timing
X/B/F/113 B/F OFF Frame

timing
Byte
114 timing
PBUS
S/115 timing
Timing from PBUS
nx 64
Figure 34: Port timing signals
The timing signals can be configured with the following control and mainte-
nance mechanisms:
• Signal monitor and consequent action:
The transmit timing signal X/113 is supervised for a loss of signal.
A missing clock signal X/113 is detected when LEDS1 counts at least 4xn
(n ≤ 10, i.e. rate ≤ 640 kbit/s) octet slips in 2.5 seconds. This corresponds
to a clock offset of ± 200 ppm in relation to the network element timing.
With n > 10, the number of octet slips to be counted is fixed to 40.
As a consequent action a missing clock signal X/113 is replaced by the
LEDS1 internal timing signal S/114.
The consequent action on the transmit data signal can be enabled or dis-
abled.
If the consequent action is enabled
− the data signal T/103 is replaced by “1” or “0”,
− the control signals C/105 and 108 towards the network are set to “1”
(i.e. “OFF”).
• B or F timing:
With X-type interfaces with synchronous user data rates the B/F/X timing
signal can be disabled, used as an input (X/113) or used as an output (B/
F):
− None (B/F):
The B/F timing signal output is disabled or configured as an input to
the LEDS1 and used for the transmit signal synchronization.
− Byte Timing (B):
The B/F/X timing signal is configured as an output to the DTE and sig-
nals the last bit of each data byte sent to the DTE on the receive user
data signal.
− Frame Timing (F):
The B/F/X timing signal is configured as an output to the DTE and sig-
nals the beginning of each frame of data bytes sent to the DTE on the
receive user data signal.
76 FOX61xLEDS1
• Transmit Timing
DTE R/104 Q D LEDS1

S/115
S/114
T/103 D Q
∆φ
1 1 = contradirectional adaptive
2 2 = contradirectional fix
X/113 3 3 = codirectional
Figure 35: Transmit timing
The timing signal used for the LEDS1 internal sampling of the transmit
user data signal T/103 can be configured to the following modes:
− Contradirectional fix:
The transmit user data signal (T/103) is sampled with the timing signal
S/114. The nominal delay from clocking out the receive data signal (R/
104) to the sampling of the transmit data signal (T/103) is half a bit
width.
In this mode the signal X/113 is not used and the corresponding con-
nector pins can be used as byte/frame timing (B/F) signal output.
− Contradirectional adaptive:
The transmit user data signal (T/103) is sampled with a phase
adjusted timing signal S/114. The sampling phase is adjusted to the
signal state changes of the transmit signal T/103. The transmit user
data signal can have any phase in relation to the transmit timing signal
(S/114).
In this mode the signal X/113 is not used.
This mode is used for relatively long lines and high user data rates
where the signal delay is of the same order of magnitude as the half
bit width or more.
Please note:
The byte or frame timing (B/F) signal output can not be used since the phase
relationship between the transmit data signal and the B/F timing signal can
not be determined by LEDS1.
− Codirectional:
The transmit user data signal (T/103) is sampled with the transmit tim-
ing signal received from the DTE (X/113). Note that the receive timing
signal (S/115) must be looped in the DTE so that the transmit timing
signal (X/113) is synchronous to the network element timing.
In this mode the signal X/113 is used and the corresponding connec-
tor pins are configured as inputs. The timing circuit B/F can’t be used,
i.e. the X.24 timing circuits must be configured to “None (B/F)”.
• Loop 2b:
The maintenance function “Loop 2b” loops the receive timing signal S/
115 back to the transmit direction where it replaces the transmit timing
signal from the DTE X/113. With an active loop 2b the B or F timing sig-
nal can be set to OFF. For details please refer to section Loop 2b
(page 97).
FOX61xLEDS1 77
5.6.3 Conference timing

All conference participants are synchronous to the network element timing
source, i.e. the PETS.
There are no participant specific timing signals used in a conference.
5.7 Protection
5.7.1 Subnetwork connection and linear trail protection

LEDS1 supports 1+1 linear trail protection and 1+1 inherently monitored sub-
network connection protection (SNCP/I). 1+1 protection is available for the
DCE interfaces and for the conference participants.
The difference between the two protection scenarios lies in the availability of
CAS.
• If CAS is available the CAS AIS failure can be detected, which represents
then the 1+1 linear trail protection. Linear trail protection protects against
server failures and disconnected matrix connections (via CAS AIS detec-
tion).
• If CAS is not available only the server layer defects can be detected,
which represents then the 1+1 SNCP/I protection. SNCP/I protects
against server failures.
1+1 protection provides the 1+1 unidirectional protection. The operation type
can be configured to revertive or non-revertive.
Please note:
Non-revertive operation is only available for n=1 (64 kbit/s).
The switching of the working and the protecting channel is done in sink
direction only. On the source side a fixed bridge is used.
78 FOX61xLEDS1
working working
TDM
protecting Network protecting
P12 P12 P12 P12

transport transport transport transport
P-12 P-12 P-12 P-12
PBUS PBUS
P12 P12 P12
P0-nc P0-nc P0nc
LEDS1 Data Data LEDS1
Figure 36: Unidirectional 1+1 protection
5.7.1.1 Protection configuration
P0-nc protection switching takes place in the LEDS1 cross connect function.
Protection switching action can be driven by two different request types:
• Traffic signal requests:
− Signal fail (SF)
The SF state is activated if the analysis of the incoming server signal
on the transport unit reports a signal failure, e.g. loss of signal.
− CAS-AIS
The CAS signalling pattern abcd of the received signal exhibits an
AIS, i.e. abcd = 1111.
− Signal degraded (SD)
The SD state is activated if the analysis of the incoming server signal
on the transport unit reports a degraded signal, e.g. BER 10-6.
• External command requests
− Forced switch to working
− Forced switch to protecting
− Manual switch to working
− Manual switch to protecting
Note that a forced switch is executed even when there is a failure on the tar-
get signal. A manual switch is executed only if the target signal exhibits no
degradation or a less severe degradation than the active signal.
The external command requests are maintenance functions, i.e. they are not
stored in the units database.
FOX61xLEDS1 79
It is possible to check the status of the protection switch (working, protecting

circuit) via the CTP status function.
For more information on cross connections and protection switching please
refer to 1KHW002467 FOX61x TDM Services.
5.7.2 Equipment protection (EQP)
5.7.2.1 EQP features
To protect the LEDS1 functions against a failure on the LEDS1 unit, FOX61x
offers the possibility to equip the subrack with a second LEDS1 unit as a pro-
tecting unit.
EQP protects the conference function. The DCE interfaces can not be pro-
tected. If protection of the DCE interfaces is required, external equipment
performing the switching of the interface signals between the working and
the protecting unit must be used. Refer to section DTE cabling for 1+1 equip-
ment protection (page 83).
In case of a failure on the active (working or protecting) unit the user traffic is
rerouted from the failed LEDS1 unit to the standby LEDS1 (protecting or
working) unit.
The working and the protecting LEDS1 units can be plugged in any free slot
of the FOX61x subrack.
Please note:
The protection switching is non revertive, i.e. after the repair of a failed
LEDS1 unit, the currently active LEDS1 unit remains the active unit irrespec-
tive if it is the working or protecting unit.
Please note:
During a protection switching event the user traffic is interrupted for up to
6 s.
5.7.2.2 EQP prerequisites
To enable equipment protection for the LEDS1 unit some prerequisites must
be met:
• The protecting LEDS1 unit must be in the unassigned state. Otherwise
the unit will not be selectable in the EQP configuration in AP: /unit-x, Con-
figuration - EQP: Create Group…, EQP Group Creation, Protecting Unit.
• The protecting unit must be hardware compatible with the working unit.
Check the hardware compatibility status after the EQP group configura-
tion in the AP: /unit-x, Status - EQP: Units Status, HW Compatible.
• The protecting unit must be software compatible with the working unit.
Check the software compatibility status after the EQP group configuration
in the AP: /unit-x, Status - EQP: Units Status, SW Compatible.
The compatible software must be installed on the LEDS1 unit before the
EQP group creation.
• The unit configuration of an equipment protection group is always done
on the active unit. The configuration on the standby unit is not possible.
80 FOX61xLEDS1

The configuration of an equipment protection group must be saved (AP: /
Configuration - Configuration Management: Save).
Otherwise, in case of a protection switch event, the NE will load an outdated
configuration from the internal configuration database and the NE configura-
tion will be corrupted.
5.7.2.3 EQP configuration
The working LEDS1 unit of an EQP group is assigned and configured the
same way as a stand alone LEDS1 unit.
The protecting LEDS1 unit is running with the same ESW as the working unit
and must be in the unassigned state.
The 1+1 equipment protection group is configured on the working unit:
• AP: /unit-x, Configuration - EQP.
− Execute the command “Create Group…”.
− Select the Protecting unit, e.g. /unit-18.
− Execute “OK”.
• Save the NE configuration.
Further on any changes on the LEDS1 configuration must be done on the
active unit. To find out which unit is the active unit check the AP tree or the
unit status of the working or protecting LEDS1 unit.
5.7.2.4 EQP status
The unit status of the working and protecting units shows the actual status of
the units belonging to the equipment protection group. The unit status offers
also the commands for the EQP manipulation:
• Manual switch
The currently standby unit is set as active unit and the currently active
unit is set as standby unit. This requires that the currently standby unit is
in operational state, i.e.
− has no failure,
− is not isolated.
A manual switch is possible if it is indicated with the “Manual Switch-Over
Allowed” parameter.
Note that this command can only be activated on the working unit status
window.
• Forced switch
The currently standby unit is set as active unit, independent of the failure
state of the currently standby unit.
Note that there is a risk that the user traffic will be permanently inter-
rupted if the currently standby unit is in a failure state.
The currently active unit is set as standby unit.
Note that this command can only be activated on the working unit status
window.
• Isolate unit
To be able to perform a maintenance action, e.g. update of the embed-
ded software, on an active unit without activating a protection switch-
over, the working unit can be isolated. This means that the protection
FOX61xLEDS1 81
switching state machine is frozen and no protection switch will be done

until the isolation of the unit is removed.
Note that the isolate unit command can only be applied to the working
unit.
• Join unit
Remove the isolation of a previously isolated unit.
Note that the join unit command can only be applied to the working unit.
The table in the EQP status window displays the following items:
• Unit
MO address of the unit belonging to the EQP group.
• EQP unit mode
The working unit is the unit where the protection group has been config-
ured.
The protecting unit is the unit that has been set to the unassigned state
before configuring the protection group.
• Active
Active true means the unit is the active unit, i.e. it is the operational unit.
Active false means the unit is the standby unit, i.e. it is not the operational
unit.
The active state can be changed with the “Manual Switch” and “Forced
Switch” commands.
• Failure
Failure true means the unit is in a failure state.
Failure false means the unit is not in a failure state.
The failure state can not be changed manually.
• Substituted
Substituted true on the working unit means the unit has been substituted
by the protecting unit. A substituted unit is also in the “active false” state.
Substituted false on the working unit means the unit has not been substi-
tuted, i.e. it is the active unit or it has been isolated.
The substituted state of the protecting unit is always false.
• Isolated
Isolated true means the unit has been isolated with the “Isolate Unit”
command.
Isolated false means the unit is not isolated.
The isolation state can be changed with the “Isolate Unit” and “Join Unit”
commands.
The isolated state of the protecting unit is always false.
• HW Compatible
HW compatible true means the working HW unit is compatible with the
protecting HW unit.
HW compatible false means the working HW unit is not compatible with
the protecting HW unit. Equipment protection is not possible.
• SW Compatible
SW compatible true means the working unit embedded software (ESW) is
compatible with the protecting unit ESW.
SW compatible false means the working unit ESW is not compatible with
the protecting unit ESW. Equipment protection is not possible.
• DB Saved
DB saved true means the current configuration of the working unit has
been saved to the FOX61x internal database.
82 FOX61xLEDS1
DB saved false means the current configuration of the working unit has
not been saved to the FOX61x internal database. A protection switching
event will load an outdated configuration and traffic will be disturbed.
5.7.2.5 DTE cabling for 1+1 equipment protection
Due to the fact that LEDS1 has front interfaces that are doubled when using
the 1+1 equipment protection function, the DTE cabling must be set up
accordingly.
1+1 equipment protection with LEDS1 works only with V.24/V.28, V.35 or
X.24/V.11 type DTEs providing two separate interfaces. One of the inter-
faces is the working interface while the other is in standby mode.
DTE LEDS1
working
active
PBUS
LEDS1
protecting
standby
Figure 37: 1+1 equipment protection

When connecting a V.24/V.28, V.35 or X.24/V.11 type DTE to a working and
protecting LEDS1 port in parallel the electrical interface parameters will be
violated.
1+1 equipment protection with a RS485 type DTE is possible as long as the
electrical interface parameters are not violated.
When using the Ethernet port of LEDS1 with 1+1 protection switching, the
Ethernet cabling must be connected with an external switch box or a hub.
Great care should be taken when using additional switch boxes, as these
devices must be considered as single points of failure in the sensitive path of
the 1+1 equipment protection scheme.
FOX61xLEDS1 83
84 FOX61xLEDS1
COMMISSIONING
6 Commissioning
In this section, you will find the following information:
• Purpose and commissioning example of the profile used for the LEDS1
unit (section Profiles (page 109)).
• Commissioning example of the LEDS1 unit and the configuration of an
interface (section Commissioning of a DCE interface (page 86)).
• Commissioning example of the LEDS1 unit and the configuration of a
data conference (section Commissioning of a conference (page 90)).
Please refer to 1KHW002466 FOXCST Operation for details on the general
GUI aspects, and to 1KHW002460 FOX61x Product Features and Charac-
teristics for specific characteristics of the FOX61x.
6.1 Profiles
6.1.1 General
A profile is a set of configuration parameters that can be applied to a certain
managed object.
Profiles are created offline with the CPS & Profile tool contained in the
FOXCST GUI (Menu: Tools / CPS & Profile …) and then downloaded to the
network element in order to make the profiles applicable.
For more information concerning profile handling please refer to
1KHW002466 FOXCST Operation.
Please note:
The creation of profiles is based upon templates that are provided with the
ESW versions.
→ The templates are available only after importing the respective service
unit’s ESW in FOXCST
Please note:
Make sure that you only use profiles from templates that have been installed
with the ESW running on the respective unit. If you use profiles from other
ESW versions, you may get an error message when trying to apply the pro-
file to the unit’s configuration.

Applying a new profile will lead to a service interruption.
FOX61xLEDS1 85
COMMISSIONING
6.1.2 LEDS1 profile handling

The LEDS1 unit supports one profile type:
• QoS mapping profile
The QoS mapping profile defines the mapping of incoming frames to the
four ingress queues according to the VLAN priority or the DSCP value
Please note:
LEDS1 supports the provisioning of up to 8 different QoS mapping profiles.
The profile is applicable to the managed objects according to the following
table.
Table 23: Profile applicability to managed objects

Profile Profile type Applicable to MO
QoS mapping QoSMappingProfile_1.00.00 unit-x/port-5: 10/100BASE-TX
6.2 Commissioning of a DCE interface
6.2.1 Prerequisites
Before starting the commissioning of a DCE interface on the LEDS1 unit, the
following prerequisites need to be fulfilled.
6.2.1.1 CESM1 unit
In a FOX61x, a CESM1 needs to be in operation in slot 11 of the FOX61x

subrack.
6.2.1.2 LEDS1 unit
In a FOX61x, the LEDS1 service unit is inserted into one of the following
slots:
− FOX615:
slot 1 … 10,
slot 12 … 21.
− FOX612:
slot 7… 10,
slot 12 … 14.
For the installation of the unit, refer to 1KHW002461 FOX615 Installation or
refer to 1KHW002462 FOX612 Installation.
A valid ESW is installed on the LEDS1 unit. For the management of ESW,
refer to 1KHW002466 FOXCST Operation. For details about compatible
ESW versions, refer to 1KHW002459 FOX61x Release Notes.
Port-y of the LEDS1 unit is connected to a DTE with the matching interface
type.
86 FOX61xLEDS1
COMMISSIONING
6.2.1.3 TDM transport unit (optional)
A TDM transport unit is inserted in the FOX61x and is running with a proper
ESW:
− LEDE1,
− DATI1,
− SAMO1,
− SAMO2.
6.2.1.4 FOXCST
FOXCST needs to be installed on a PC, and a management connection from

the FOXCST to the FOX61x needs to be up and running. For details about
the installation and operation of the FOXCST, please refer to 1KHW002466
FOXCST Operation.
The amount and accessibility of operations depend on the user profile with
which you are logged in. For more information, please refer to 1KHW002466
FOXCST Operation.
6.2.1.5 PETS
The PETS on the FOX61x network element must be configured to an appro-

priate synchronization clock source, i.e. a clock source traceable to a PRC.
For the PETS configuration refer to 1KHW002467 FOX61x TDM Services.
6.2.2 Configuration of a DCE interface

For the configuration of the user port, the following steps have to be per-
formed.
Port configuration This action list shows step by step how to configure a user port. The given
example uses mostly the default values.
The following assumptions and identifiers are used:
 The LEDS1 unit is assumed to be plugged in slot 7 of a FOX515.
 The LEDS1 unit is assigned.
 The port to be configured has the identifier port-1.
 The interface type is V.35 with a synchronous transmission rate of
64 kbit/s.
Configure the port general Proceed as follows:

parameters
1. Navigate to the general parameters:
 AP:/unit-7/port-1, Configuration - General.
2. Select the interface type:
 Interface Type = V.35.
3. Select the transmission mode:
 Transmission = Synchronous.
4. Select the interface rate:
 Rate = 64 kbit/s.
5. Disable the data signal inversion:
 Data Signal Inversion = .
FOX61xLEDS1 87
COMMISSIONING
6. Execute “Apply”.
Configure the port signal Proceed as follows:

structure parameters
1. Navigate to the signal structure parameters:
 AP:/unit-7/port-1, Configuration - Signal Structure.
2. Select the synchronous timing mode with contradirectional timing:
 Timing = Contradirectional-Fix.
Configure the port control sig- Proceed as follows:

nal parameters
1. Navigate to the control signal parameters:
 AP:/unit-7/port-1, Configuration - Control Signals.
2. Select the control signal parameters from DTE, all control signals set to
ON, with control signal transport:
 105 (RTS,C) = ON,
 108 (DTR) = ON,
 Signalling To Network = “Yes”.
3. Select the control signal parameters to DTE, all control signals set to ON
or OFF:
 106 (CTS) = ON,
 107 (DSR) = ON,
 109 (DCD, I) = ON,
 142 (Loopback Indication) = OFF.
4. Select the delay time for the control signals:
 105 (RTS,C) -> 106 (CTS) / 109 (DCD, I) = 0 ms,
Configure the port error han- Proceed as follows:

dling parameters
1. Navigate to the error handling parameters:
 AP:/unit-7/port-1, Configuration - Error Handling.
2. Select the receive failure error handling:
 Consequent Action 104 (RXD, R) = 1.
3. Select the transmit failure error handling, no level detection:
 Level Detection 103 (TXD, T) = False,
 Consequent Action 103 (TXD, T) = None.
4. Select the transmit send time filter parameters, no send or idle time fil-
ters:
 DTE Max Send Time Filter = ,
 DTE Max Idle Time Filter = .
Configure the port test loops Proceed as follows:

parameters 1. Navigate to the test loops parameters:
 AP:/unit-7/port-1, Configuration - Test Loops.
2. Select the loop activation device, activation by the element manager:
 Activation By = EM.
3. Select the transmit signal during loop 3c and loop 3b:
 103 (TXD, T) = 1.
88 FOX61xLEDS1
COMMISSIONING
4. Select the receive signal during loop 2b:

 104 (RXD, R) = 1.
Configure the port CTP Proceed as follows:

parameters
1. Navigate to the CTP parameters:
 AP:/unit-7/port-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parame-
ters are read-only.
3. Configure the z-End:
 Enable the Revertive Protection Switching = .
 Disable the CAS AIS Supervision = .
 Disable the Switch-Over Logging = .
 The user port is completely configured.
Create the cross connection Proceed as follows:

1. Configure the cross connection from the user port to a time slot on a
LEDE1 unit. It is assumed that the connection termination point (CTP) on
the LEDE1 unit has been created before on port-8, time slot 1. Please
note that the termination mode of the LEDE1 port must be configured to
PCM30 or PCM30C, i.e. using CAS.
2. Select the “Cross connections” view of the FOXCST.
 Click on the “Connection Wizard” button:
 The “Create TDM Connection” dialogue opens.

3. Set the connection parameters:
 Layer Rate = P0-nc.
 Directionality = Bidirectional.
 Protected = No.
 Label 1 = <anyName>.
 Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
 Select the LEDS1 unit, port-1.
7. Select the A-End CTP:
 Select the LEDE1 unit, port-8/chan-1.
8. Execute “Create”.
 The bidirectional cross connection from the LEDE1 channel to the
LEDS1 port is created.
FOX61xLEDS1 89
COMMISSIONING
Activation Proceed as follows:

1. Set the administrative state of the port-1 to up
AP:/unit-7/port-1, Main - Admin And Oper Status:
 Set Administrative Status to “Up”.
- The “Operational Status” changes to “Up”.
 The port is activated.
End of instruction
6.3 Commissioning of a conference
6.3.1 Prerequisites
Refer to section Prerequisites (page 86).
6.3.2 Configuration of a conference

For the configuration of a conference, the following steps have to be per-
formed.
Conference configuration This action list shows step by step how to configure a conference. The given
example uses mostly the default values.
The following assumptions and identifiers are used:
 The LEDS1 unit is assumed to be plugged in slot 7 of a FOX615.
 The LEDS1 unit is assigned.
 The conference to be configured has the identifier conf-1.
 The maximum number of participants is 4.
 The initial number of participants is 3.
 The rate is 64 kbit/s.
 The conference is of the multipoint-to-multipoint type.
 The conference has one “local” participant, one participant “to master”
and one participant “to slave”.
 The participants use CAS for the control signal transport.
 The participants data and control signals are interconnected without
conditional control.
Configure the unit parameters Proceed as follows:

1. Navigate to the conferencing parameters:
 AP:/unit-7, Configuration - Conferencing.
2. Create a data conference:
 Execute “Create Conference…”.
 The “Create Conference” dialogue opens.
3. Enter the conference parameters:
 Index = 1.
 Maximum Number Of Participants = 4.
 Initial Number Of Participants = 3.
 Rate = 64 kbit/s.
 Type = MP2MP.
90 FOX61xLEDS1
COMMISSIONING
4. Execute “OK”.
 The unit parameters are configured.
Configure the participant 1 Proceed as follows:

general parameters
1. Navigate to the general parameters:
 AP:/unit-7/conf-1/part-1, Configuration - General.
2. Enable the control signals towards the conference:
 Signalling To Conference = Yes.
3. Enable the control signals from the conference:
 Signalling From Conference = Yes.
4. Select the participants role:
 Role = To Master.
5. Disable the conditional interconnection:
 Conditional Interconnection = No.

CTP parameters 1. Navigate to the CTP parameters:
 AP:/unit-7/conf-1/part-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parame-
ters are read-only.
3. Configure the z-End:
 Enable the Revertive Protection Switching = .
 Disable the CAS AIS Supervision = .
 Disable the Switch-Over Logging = .
 The participant 1 is completely configured.

1. Configuration analogue to participant 1, but with the participants role set
to “To Slave”.

1. Configuration analogue to participant 1, but with the participants role set
to “Local”.

for participant 1
1. Configure the cross connection from the participant 1 to a time slot on a
FOX61xLEDS1 91
COMMISSIONING

 Protected = No.
 Number = 1.
 Select the LEDS1 unit, part-1 of conf-1.
 The bidirectional cross connection between LEDS1 and LEDE1 is config-
ured.

for participant 2 1. Configure the cross connection from the participant 2 to a time slot on a

 Protected = No.
 Number = 1.
92 FOX61xLEDS1
COMMISSIONING
 The bidirectional cross connection between LEDS1 and LEDE1 is config-
ured.

for participant 3
1. Configure the cross connection from the participant 3 to a user port on
the same LEDS1 unit (port-1).

 Protected = No.
 Number = 1.
 Select the LEDS1 unit, port-1.
 The bidirectional cross connection between LEDS1 port and conference
participant is configured.
Activation Proceed as follows:

1. It is assumed that the administrative state of the port-1 has been set to
up before.
The conference and the participants don’t need any activation.
End of instruction
FOX61xLEDS1 93
COMMISSIONING
94 FOX61xLEDS1
OPERATION
7 Operation
This section describes the operation functions of the LEDS1 unit. You will
find the following information:
• Optical indicators description found on the LEDS1 unit front (section Unit
optical indicators (page 95)).
• Diagnostic loops at LEDS1 DCE interfaces (section Loops (page 96)).
• Maintenance functions for ports and conference participants (section
DCE interface line state maintenance (page 99)).
• DTE send time supervision function (section DTE send and idle time
restrictions (page 101)).
• Generic maintenance functions of the unit (section Maintenance
(page 103)).
Please note:
The operation functions described in this section assume a correctly config-
ured and operational LEDS1 unit.
7.1 Unit optical indicators
LEDs on the front of the LEDS1 unit are used to indicate to the user the
alarm status summary of the unit and of the network traffic signals.
XXXXx R1B
ANR_37900374
UNIT TRAFFIC
Figure 38: Fault indication LEDs on the LEDS1 unit
Table 24: LED signalling on LEDS1

LED name Colour State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide the requested function due to
- equipment failure (total breakdown),
- mismatch of HW and SW.
Recovery from this error situation is done usually by replacement
of unit HW or ESW.
Green / Red Booting or Unit has not been taken in service yet or the unit has not been pro-
(blinking 1 Hz) waiting visioned.
Recovery from this situation is done by taking this unit into service
with FOXCST.
FOX61xLEDS1 95
OPERATION
Table 24: LED signalling on LEDS1 (continued)

LED name Colour State Meaning
Green Running Unit is up and running, it is ready to provide the required service.
Off Failure System is not powered or outage of power supply on unit or outage
of LED.
TRAFFIC Red Failure One or more active failures on the unit, independent of the sever-
ity.
More detailed information is provided by FOXCST.
Off Normal Normal (error free) operation.
7.2 Loops
For maintenance purposes LEDS1 offers for the DCE interfaces three differ-
ent types of diagnostic loops.
LEDS1
R/104
PBUS
DTE Loop 3c Loop 2b Processing Loop 3b
T/103
Figure 39: Loops 2b, 3b and 3c
• Loop 2b (remote loop)

The loop 2b redirects the received data from the network back to the net-
work. The network connection between the local DCE and the remote
DCE can be tested.
• Loop 3b (local loop)
The loop 3b sends the user data transmitted by the DTE back to the DTE.
The connection between DTE and local DCE can be tested.
• Loop 3c (local loop)
The loop 3c sends the user data transmitted by the DTE back to the DTE
without processing of the data signal. The connection between DTE and
local DCE can be tested.
The loop signal conditions are according to ITU-T X.150. With V-type inter-
faces the loops are according to ITU-T X.20bis, X.21bis and V.54. With X-
type interfaces the loops are according to ITU-T X.20 and X.21.
Only one loop 2b or 3b or 3c can be active at the same time per port.
All loops can be activated by the element manager FOXCST. The loop 3c
can also be activated from the DTE via the control signal 141. Loops can
only be activated by the FOXCST or the DTE. This is done to prevent two
users performing maintenance functions at the same time.
96 FOX61xLEDS1
OPERATION
Please note:
An active loop 2b, 3b or 3c is traffic disturbing.
Please note:
An active loop generates the alarm “Maintenance Function Active”.
Please note:
There are no diagnostics loops available with MAC bridging.
7.2.1 Loop 2b
The loop 2b is the so called remote loop. The loop selector is located close
to the DCE interface.
LEDS1 A, LEDS1 B,
local remote
T/103
R/104
DTE TDM Processing Loop 2b DTE

A Network B
T/103
R/104
fixed pattern
Figure 40: Loop 2b
The loop 2b at location B can be activated from the FOXCST at location B.

During an active loop 2b the signals towards the DTE A are as follows:
• The transmit data signal T/103 is replaced by the receive data signal R/
104.
• The control signal C/105 is replaced by the received control signal I/109 if
the control signal C/105 is configured to “From-DTE”. With another con-
figuration the control signal is not modified.
• The control signal 108 is replaced by the received control signal 107 if the
control signal 108 is configured to “From-DTE”. With another configura-
tion the control signal is not modified.
• The transmit timing signal X/113, if used, is replaced by the receiver tim-
ing signal S/115.
During an active loop 2b the signals towards the DTE B are as follows:
• The receive data signal R/104 is a fixed pattern, configurable to “1, “0” or
“0101”
• The control signals I/109, 106 and 107 are all set to OFF.
• The control signal 142 is set to ON, indicating to the DTE that a test func-
tion is active.
• The timing signals S/114 and S/115 remain active.
• The timing signal B/F remains active or can be set to OFF.
FOX61xLEDS1 97
OPERATION
7.2.2 Loop 3b
The loop 3b is the so called local loop. The loop selector is located close to
the PBUS interface of the LEDS1 unit.
LEDS1 A, LEDS1 B,
local remote
T/103
R/104
DTE Processing Loop 3b TDM DTE

A T/103 Network B
R/104
fixed pattern
Figure 41: Loop 3b
The loop 3b at location A can be activated from the FOXCST at location A.

During an active loop 3b the signals towards DTE A are as follows:
• The receive data signal R/104 is replaced by the transmit data signal T/
103.
• The control signal I/109 is replaced by the transmitted control signal C/
105 if the control signal I/109 is configured to “Remote-105”. With another
configuration the control signal is not modified.
• The control signal 107 is replaced by the transmitted control signal 108 if
the control signal 107 is configured to “Remote- 108”. With another con-
figuration the control signal is not modified.
• The control signal 106 is not modified by a loop 3b.
• The control signal 142 is set to ON, indicating to the DTE that a test func-
tion is active.
• The timing signals S/114, S/115 and B/F remain active.
During an active loop 3b the signals towards the DTE B are as follows:
• The transmit data signal T/103 is a fixed pattern, configurable to “1, “0” or
“0101”
• The control signal C/105 is set to OFF.
• The control signal 108 is set to OFF.
7.2.3 Loop 3c
The loop 3c is the so called local loop. The loop selector is located close to
the DCE interface of LEDS1.
LEDS1 A, LEDS1 B,
local remote
T/103
R/104
DTE Loop 3c Processing TDM DTE

A Network B
T/103
R/104
fixed
pattern
Figure 42: Loop 3c
The loop 3c at location A can be activated
98 FOX61xLEDS1
OPERATION
• from the FOXCST at location A

• from the DTE at location A with the control signal 141 = ON with V-type
interfaces.
The data, control and timing signals towards DTE A and DTE B are the
same as with the loop 3b.
Please note:
With higher user data rates and long cables, the timing condition of the data
sampling in the DTE can not be fulfilled anymore since the looped data sig-
nal is not resampled in LEDS1.
→ Use loop 3b instead.
7.3 DCE interface line state maintenance
The port and participant line state maintenance functions allow to take a
DCE interface or a conference participant out of service or to insert a test
signal towards the front port or towards the conference.
The line state maintenance function provides the following parameters:
• In service:
This parameter restores the normal operating state of the front port or of
the conference participant.
• Out of service:
Take a front port or a conference participant out of service, i.e. replace
the data signal by an all-1 signal in receive and transmit direction, set all
control signals towards the DTE to OFF and replace the signalling
towards the network by an AIS (abcd = 1111) and activate the TSD and
TSF signals. TSF and TSD are the FOX61x internal failure signals used
to control the protection switching.
The timing signals remain active.
− Port maintenance:
This parameter can be used to simulate a failed path towards the front
port.
− Participant maintenance:
This parameter can be used to test the protection switching in a point-
to-multipoint or multipoint-to-multipoint application due to a failed
LEDS1 unit.
Please note:
The line states of both the “to master” and the “to slave” participants must be
set to “out of service” to check the correct protection switching.
• Test pattern insertion:
Replace the receive data signal at the front port or a conference partici-
pants data signal by a test signal 0101, set all control signals towards the
DTE or a conference participant to OFF.
The timing signals remain active.
− Port maintenance:
This parameter provides an easy way to check the connection from
the LEDS1 unit to a connected DTE.
FOX61xLEDS1 99
OPERATION
To insert a test signal towards the TDM network, a loop 2b or an

external hardware loop must be applied at the corresponding inter-
face.
− Participant maintenance:
This parameter provides an easy way to check the connection from
the LEDS1 unit to any other conference participant.
In a point-to-multipoint application a test pattern inserted at the “to
master” participant is sent to all “local” and the “to slave” participants.
A test pattern inserted at a “local” or “to slave” participant is sent to the
“to master” participant.
In a multipoint-to-multipoint application a test pattern inserted at any
participant is sent to all other participants.
When applying a maintenance function the following signals are sent
towards the front port or the conference and towards the PBUS:
Table 25: Maintenance function signal replacement

Function Signal Towards front port or Towards PBUS
conference
Out of service Data signals 1111’1111 1111’1111
Control signals OFF -
CAS - 1111
Failure signal - TSF, TSD a
Insert test signal Data signals 0101’0101 -
Control signals OFF -
CAS - -
Failure signal - -
a. TSF and TSD are the FOX61x internal failure signals used to control the protection
switching
For the location of the signal insertion points please refer to the figures in the
sections Port data handling (page 60), Conference data handling (page 62),
Port control signal handling (page 67) and Conference control signal han-
dling (page 70).
Please note:
Active maintenance functions generate the MFA alarm (maintenance func-
tion active).
Please note:
Only one maintenance functions can be active at the same time on a port or
conference participant.
100 FOX61xLEDS1
OPERATION
7.4 DTE send and idle time restrictions
A supervision circuit of the DTEs send and idle times helps to improve the
network’s availability by preventing the network from remaining blocked as a
result of a defective DTE. This function is mainly used in the point-to-multi-
point and multipoint-to-multipoint applications.
The activity check of a DTE is done by checking the logic content of the
transmit data signal T/103: A “0” means an active state, a “1” means an inac-
tive state.
The send time supervision checks the number of consecutive seconds with
observed activity of the DTE, i.e. each second containing a data bit with a
logic “0” counts as a “send time second”. If the number of “send time sec-
onds” exceeds the configured limit an alarm is activated.
The send time limit can be configured from 1 s to 255 s.
The idle time supervision checks the number of consecutive seconds with no
observed activity of the DTE, i.e. each second containing only data bits with
a logic “1” counts as an “idle time second”. If during the observation period
the number of “idle time seconds” is below the configured limit an alarm is
activated.
The idle time limit can be configured from 1 s to 255 s. The observation
period for the idle time can be configured from 2 s to 65’535 s. The idle time
limit is required to be smaller than the observation period.
FOX61xLEDS1 101
OPERATION
Interface out of service

Send time OK
Idle time OK
Cs = 0 Cs: Counter for the send time seconds
Ci = 0 Ci: Counter for the idle time seconds
Co = 0 Co: Counter for the idle time observation
period
Interface in service
Check activity for

1s
Co = Co + 1
N Y
Activity
Cs = 0 Cs = Cs + 1
Ci = Ci + 1 Ci = 0
Send time OK
N N N
Ci ≥ limit Co ≥ limit Cs ≥ limit
Y Y Y
Ci = 0 Ci = 0
Cs = 0
Co = 0 Co = 0
Idle time OK Idle time violated Send time violated
Figure 43: Send time and idle time supervision
When one of the send time or idle time limits is violated the interface can be
taken out of service (refer to section AP: / unit-x / port-y, Configuration -
Error Handling (page 138)). All DTEs connected to this port will be detached
in this case. The DTEs remain detached until the interface is taken into ser-
vice again 30 s after the defect clearing or with the corresponding port status
command, refer to section AP: / unit-x / port-y, Status - Maintenance
(page 150).
102 FOX61xLEDS1
OPERATION
7.5 Maintenance
7.5.1 Inventory data

It is possible to read inventory data from the LEDS1 unit via the FOXCST
with the following access point:
AP: /unit-x, Main - Inventory.
7.5.2 Unit ESW download

It is possible to update the embedded software (ESW) of the LEDS1 unit via
software download.
Please refer to 1KHW002466 FOXCST Operation for the description of the
ESW download.

The assignment of new embedded software restarts the LEDS1 unit.
Thus, the installation of new ESW on the unit affects all traffic functions of
the LEDS1 unit.
7.5.3 ESW upgrade with EQP

When upgrading the ESW on 1:1 equipment protected LEDS1 units, care
must be taken concerning the traffic interruptions and which unit will finally
be the active unit. At the end of the upgrade procedure the working unit shall
be the active unit.
It is assumed that the working unit is plugged in slot 7 and the protecting unit
is plugged in slot 18 of the FOX615 subrack.
ESW upgrade procedure 1 The following procedure provides the upgrade process with one traffic inter-
ruption of about 60 s.
Isolate the working unit Proceed as follows:

1. Isolate the working LEDS1 unit:
 AP: /unit-7, Status – EQP.
 Execute the “Isolate Unit” command.
 The working LEDS1 unit is isolated, i.e. it will not perform a protection
switchover.
ESW download and start Proceed as follows:

1. Configure the new ESW file for the working LEDS1 unit:
 Menu Tools - Software Download ….
 Click on the table row with ID “/unit-7”.
 In the “Software to install” column select the software to be down-
loaded.
 Tick the “Delete unused Software” box.
FOX61xLEDS1 103
OPERATION
2. Configure the new ESW file for the protecting LEDS1:

loaded.
3. Execute the “Download and Start …” command.
 The “Parameters for command Download and Start” dialogue opens.
 Select the “Upgrade Units Only” algorithm.
 Click “OK”.
 The new ESW is downloaded and becomes active on the working
and the protecting units.
 Traffic will be interrupted for about 60 s.
 The new ESW is active on the working and the protecting LEDS1 units.
The working LEDS1 unit in slot 18 remains the active unit.
Join the working unit Proceed as follows:

1. Join the working LEDS1 unit:
 AP: /unit-7, Status – EQP.
 Execute the “Join Unit” command.
 The working LEDS1 unit is able again to perform a protection switchover.
End of instruction
ESW upgrade procedure 2 An alternative procedure requires two short interruptions of about 1 s instead
of one long interruption. 1
ESW download Proceed as follows:

1. Configure the new ESW file for the working LEDS1 unit:
 Menu Tools - Software Download ….
loaded.
2. Configure the new ESW file for the protecting LEDS1:
loaded.
3. Execute the “Download” command.
 The new ESW is downloaded to the working and the protecting units.
 The ESW download is complete.
ESW upgrade on the protect- Proceed as follows:

ing unit 1. Apply the new ESW on the protecting LEDS1 unit:
 AP: /unit-18, Main - Software
 Select the downloaded software in the “Software” selection box.
 Execute the “Apply” command.
2. Save the configuration:
 Execute the “Save to NE” command.
1. The 1 s interruption time is valid for configurations with up to 1 conference only.

With 212 conferences the interruption is up to 60 s.
104 FOX61xLEDS1
OPERATION
3. Start the new ESW on the protecting LEDS1 unit:

 Execute the “Start Software” command.
 The new ESW becomes active on the protecting unit. This takes
about 60 s.
 The ESW upgrade on the protecting unit is complete.
Manual switch to protecting 1. Perform a manual switch-over from the working to the protecting LEDS1
unit unit:
 AP: /unit-7, Status - EQP
 Execute the “Manual Switch-Over” command.
 Traffic will be switched to the protecting unit.
2. Wait until the working unit has rebooted (about 60 s).
ESW upgrade on the working 1. Apply the new ESW on the working LEDS1 unit:
unit  AP: /unit-7, Main - Software
 Select the downloaded software in the “Software” selection box.
 Execute the “Apply” command.
2. Save the configuration:
 Execute the “Save to NE” command.
3. Start the new ESW on the working LEDS1 unit:
 Execute the “Start Software” command.
 The new ESW becomes active on the working unit.
4. Wait until the working unit has rebooted (about 60 s).
Manual switch to working unit 1. Perform a manual switch-over from the protecting to the working LEDS1
unit:
 AP: /unit-7, Status - EQP
 Execute the “Manual Switch-Over” command.
 Traffic will be switched to the working unit.
2. Wait until the protecting unit has rebooted (about 60 s).
 The ESW upgrade is complete.
End of instruction
FOX61xLEDS1 105
OPERATION
106 FOX61xLEDS1
FOXCST REFERENCE
8 FOXCST Reference
This section gives a complete reference of the managed objects, properties,
and commands of the LEDS1 service unit of the FOX61x.
In this section, you will find the following information:
• An introduction (section Introduction (page 107)),
• Profile configuration parameters (section Profiles (page 109)),
• Unit management commands and parameters (section AP: / unit-x:
LEDS1 (page 110)),
• Conference management commands and parameters (section AP: / unit-
x / conf-z (page 118)),
• Conference participants management commands and parameters (sec-
tion AP: / unit-x / conf-z / part-a (page 120)),
• Data port commands and parameters (section (page 129)).
• Ethernet port commands and parameters (section (page 152)).
For a description on how to configure and bring into operation the LEDS1
unit and its main functions, please refer to section Commissioning (page 85).
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
LEDS1 service unit.
The Figure 44 shows the access point (AP) tree for the LEDS1 unit with its
managed objects.
<ap >
FOX61x
0...20 <ap >

unit-x: LEDS1
0...212 <ap>
conf-z
0 ...16 <ap>
part-a
5 <ap>
port-y
Figure 44: MOM (managed object model) of the LEDS1 unit
With these managed objects (MOs) the following functions are covered:
FOX61xLEDS1 107
FOXCST REFERENCE
Table 26: Managed objects (MOs) for LEDS1

MO Description of the management functions
unit-x: LEDS1 Rxx Restart of the unit, management of the unit ESW, labelling,
(leds1_r2a) indication of equipment status, read of inventory data, access
to logbooks. Configuration of unit parameters and equipment
protection parameters, creating or deleting of data confer-
ences.
The detailed properties are described in AP: / unit-x: LEDS1
(page 110).
conf-z Management of a data conference. Creating or deleting of con-
ference participants.
The detailed properties are described in AP: / unit-x / conf-z
(page 118)
part-a Management of a participant of a data conference. Parameters
as e.g. participant role, signalling handling, maintenance func-
tions.
The detailed properties are described in AP: / unit-x / conf-z /
part-a (page 120)
port-y Management of the DCE and Ethernet interface related func-
tions, like the interface type, transmission mode, user bit rate
and maintenance functions.
The detailed properties are described in (page 129)
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.
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.
108 FOX61xLEDS1
FOXCST REFERENCE
8.2 Profiles
For a detailed description of the profile creation and download to the NE

please refer to 1KHW002466 FOXCST Operation.
Please note:
The profile templates are only available if the ESW of the LEDS1 unit has
been imported into the FOXCST.
8.2.1 QoS mapping profile
Table 27: QoS mapping profile

Operation Name Parameter Name Range Description / Details
Profile Templates Template LEDSQoSMappingProfile_ Select the QoS mapping profile template as a
1.00.00 base for the parameter editing.
Profile, Information Name 3 … 64 characters User editable name for the profile.
Valid characters are a-z, A-Z, 0-9 and _.
Description 0 … ∞ characters User editable description for the profile.
Valid characters are a-z, A-Z, 0-9 and _.
FOX61xLEDS1 109
FOXCST REFERENCE
Table 27: QoS mapping profile (continued)

Profile, Data, Map- MAC Tag PRI 0…7 Priority of a VLAN tagged packet or priority
ping Profile, 802.1q tagged MAC frame.
Mapping TX Queue Q1 … Q4 Queue number for the ingress traffic.
Q1 is the lowest priority queue,
Q4 is the highest priority queue.
Modify … Modify a selected 802.1p mapping table entry.
Select the table entry to be modified by clicking
on it.
After modifying a table entry press also Apply or
OK in the profile window.
Profile, Data, Map- DSCP 0 … 63 Priority of an IP packet given by the Differenti-
ping Profile, DSCP ated Services Codepoint (DSCP).
Mapping TX Queue Q1 … Q4 Queue number for the ingress traffic.
Q1 is the lowest priority queue,
Q4 is the highest priority queue.
Modify… Modify a selected DSCP mapping table entry.
Select the table entry to be modified by clicking
on it.
After modifying a table entry press also Apply or
OK in the profile window.
8.3 AP: / unit-x: LEDS1
8.3.1 AP: / unit-x, Overview

For a description of the
− “Overview - Alarms”, and
− “Overview - Cross Connections”
management functions, please refer to 1KHW002466 FOXCST Operation.
8.3.2 AP: / unit-x, Main

For the
− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
management functions description, please refer to 1KHW002466 FOXCST
Operation.
110 FOX61xLEDS1
FOXCST REFERENCE
8.3.3 AP: / unit-x, Configuration
8.3.3.1 AP: / unit-x, Configuration - Conferencing
“Create Conference” and “Delete Conference” dialogues:
Table 28: AP: / unit-x, Configuration - Conferencing

Create Conference Open the dialogue to create a confer-
… ence.
Create Conference Index 0 … 255 Select the conference index number.
0 is a reserved value used for the auto-
assignment of a conference index: The
auto-assigned index is the lowest availa-
ble index number.
In the FOXCST GUI the default value is
the autoassigned index number.
Maximum Number 4 Maximum number of participants that can
Of Participants be assigned to the data conference.
8
This maximum number is used for the
16 unit internal resource handling.
If the number of conference participants
has to be increased above the configured
maximum number the conference must
be deleted and newly created.
Initial Number Of 0 … 3 …16 Number of participants initially assigned
Participants to the data conference. The initial number
of participants must be smaller or equal
than the maximum number of partici-
pants.
Note that the total number of participants
per LEDS1 unit is limited.
Please refer to section Conference
resources (page 53) for a description of
the available resources for conferences.
FOX61xLEDS1 111
FOXCST REFERENCE
Table 28: AP: / unit-x, Configuration - Conferencing (continued)

Rate 64 …1984 kbit/s Data rate of the conference in kbit/s. All
participants of the conference are set up
with this data rate.
When using CAS the maximum data rate
is limited to 1920 kbit/s.
Note that the rate value influences the
conference resource handling.
Please refer to section Conference
resources (page 53) for a description of
the conference resource handling on the
LEDS1 unit.
Type MP2MP The conference type can be configured to
point-to-multipoint (P2MP) or multipoint-
P2MP
to-multipoint (MP2MP) in linear network
applications.
Please refer to sections Conference con-
trol signal handling (page 70) and Confer-
ence data handling (page 62) for a
description of the data and signalling
transport in the point-to-multipoint and
multipoint-to-multipoint applications.
Delete Conference Open the dialogue to delete a confer-
… ence.
Delete Conference Conference All Delete all or a specific
conference.
conf-1 … conf-n
8.3.3.2 AP: / unit-x, Configuration - EQP
“Create EQP Group” and “Delete EQP Group” dialogues:
Table 29: AP: / unit-x, Configuration - EQP

Create EQP Group Open the dialogue for the creation of an equip-
… ment protection (EQP) group.
A unit must be in the unassigned state to be
selectable as a protecting unit.
112 FOX61xLEDS1
FOXCST REFERENCE
Table 29: AP: / unit-x, Configuration - EQP (continued)

EQP Group Crea- Group Type 1:1 Type of the EQP group.
tion MO address of the working unit, e.g. /unit-4.
Working Unit /unit-x
In the FOXCST GUI the working unit MO
address is read-only.
Protecting Unit - List of the MO addresses of all HW compatible
units which are not assigned, e.g. /unit-18.
/unit-y
Default is no unit selected.
Delete EQP Group Open the dialogue for the deletion of an existing
equipment protection (EQP) group.
Traffic on the protecting unit will be interrupted
and services will be re-established on the work-
ing unit.
The protecting unit will become unassigned.
Please note:
With equipment protection of a LEDS1 unit it is only possible to protect the
conferences on the unit.
Equipment connected to user ports can not be protected.
8.3.4 AP: / unit-x, 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
following table lists the fault causes of the current AP.
Table 30: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWM Software Mismatch Equipment  Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment  Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to the
unit.
RSWNA a Running Software Not Equipment  Major The running ESW has been deleted from
Available Alarm the unit flash memory.
The unit is still able to provide its service,
but a new ESW is required to be down-
loaded to the unit and assigned.
SWIN Software Incompatible Equipment  Major The running ESW is not compatible with
With Network Element Alarm the version required by the NE type or
version.
PRC PBUS Resource Con- Processing  Major Unit has been plugged into a slot which
flict Error Alarm conflicts with another unit, e.g. when
using an outdated ESW on an ISDN-BA
linecard.
FOX61xLEDS1 113
FOXCST REFERENCE
Table 30: AP: / unit-x, Fault Management (continued)

Affecting Severity
EQM Equipment Malfunction Equipment  Critical The LEDS1 controller detects any anom-
Alarm alies on the unit, e.g. a voltage is miss-
ing, a chip does not respond, etc.
HWIC Hardware Incompatible Equipment  Major The plugged HW is not compatible with
With Configuration Alarm the unit configuration HW stored in the
database. You may need to change the
HW or re-create the configuration for the
unit.
SWIC Software Incompatible Equipment  Major The ESW running on the unit is not com-
With Configuration Alarm patible with the unit configuration stored
in the database. You may need to
upgrade, or downgrade the ESW, or re-
create the configuration with the cur-
rently running ESW.
GSW General Software Equipment  Major An ESW internal error has been detected
Alarm Alarm that might inhibit the ESW from running
correctly.
MFA Maintenance Function Communica-  Warning A maintenance function has been acti-
Active tion Alarm vated by the operator from the unit status
dialogue.
UNAV Unit Not Available Equipment  Critical The unit that is configured is either not
Alarm plugged or not recognized due to a fail-
ure.
NSW No Application Soft- Equipment  Major There is no application ESW installed on
ware Alarm the unit, or the application ESW has not
yet finished its boot process.
UNAS Unit Not Assigned Equipment  Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, execute
the “Assign” command in the “Main”
function of the unit.
UIC Unit Incompatible Equipment  Major The inserted unit is not compatible with
Alarm the assigned unit.
PWRSVE Battery Power Saving Equipment  Critical Power saving is active on the unit, i.e. it
Alarm is kept in the “reset” state during battery
power backup.
EQPUNV EQP Unit Not Available Equipment  Major The standby unit is not available, i.e. not
Alarm plugged in or has an equipment failure.
This alarm is available on the working
and the protecting unit of an EQP group.
EQPHWI EQP Hardware Incom- Equipment  Major The actual hardware is not compatible
patible With Configura- Alarm with the hardware of the protecting unit.
tion This alarm is available on the working
unit of an EQP group only.
EQPSWI EQP Software Incom- Equipment  Major The running software (ESW) is not com-
patible With Configura- Alarm patible with the software on the protect-
tion ing unit.
114 FOX61xLEDS1
FOXCST REFERENCE
Table 30: AP: / unit-x, Fault Management (continued)

Affecting Severity
EQPNPR EQP Group Not Pro- Equipment  Major The working or the protecting unit is not
tected Alarm available, i.e. not plugged in or has an
equipment failure.
EQPWUI EQP Working Unit Iso- Equipment  Major The working unit has been isolated with
lated Alarm the “Isolate Unit” status command.
No protection is available in this state.
EQPUNA EQP Working Unit Not Equipment  Major An automatic protection switch or a
Active Alarm “manual switch” or a “forced switch” to
the protecting unit has been done.
a. The running ESW cannot be deleted. The alarm will never be activated.
8.3.5 AP: / unit-x, Status
8.3.5.1 AP: / unit-x, Status - Conferences
Table 31: AP: / unit-x, Status - Conferences

Number Of Availa- Number Of Availa- 0 … 53 Available number of 64 kbit/s conferences with
ble Conferences a ble 16 Participant 16 participants on the LEDS1 unit.
Conferences
Number Of Availa- 0 … 106 Available number of 64 kbit/s conferences with 8
ble 8 Participant participants on the LEDS1 unit.
Conferences
Number Of Availa- 0 … 212 Available number of 64 kbit/s conferences with 4
ble 4 Participant participants on the LEDS1 unit.
Conferences
FOX61xLEDS1 115
FOXCST REFERENCE
Table 31: AP: / unit-x, Status - Conferences (continued)

Available Partici- Max Participant 64 … 1984 Maximum participant rate available on the PBUS
pant Resources, Rate (kbit/s) resources.
Participant
Resource Table b It is only possible to create conference partici-
pants with the maximum or a smaller rate.
Available 0 … 27 Available number of participants with the corre-
sponding maximum participant rate.
It is only possible to create conference partici-
pants with the maximum rate up to the available
number.
Note that when creating conferences with
smaller rates also the resources with higher
rates can be used.
a. The number of available conferences shows the number of available conferences

with 16 OR 8 OR 4 participants.
b. The participant resource table shows all available resources, it is NOT an OR oper-
ation.
Please note:
Refer to section Conference resources (page 53) for a description of the confer-
ence resource handling on the LEDS1 unit.
Please note:
Refer to section PBUS resources (page 55) for a description of the PBUS
resource handling on the LEDS1 unit.
116 FOX61xLEDS1
FOXCST REFERENCE
8.3.5.2 AP: / unit-x, Status - EQP
Table 32: AP: / unit-x, Status - EQP

EQP Group Manual Switch-Over  Indication that the standby unit, i.e. the working
Allowed or the protecting unit is operational and can take
over the service.
 Indication that the standby unit, i.e. the working
or the protecting unit is not operational due to a
failure or to isolation or that the database has not
been saved. A manual protection switching with
the “Manual Switch-Over” command is not possi-
ble.
EQP Group - Units Unit <MO address> MO address of the unit belonging to the EQP
Status group.
EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.
Working Unit
Protecting Unit
Active  The unit is active (operational).
 The unit is standby (not operational).
Failure  The unit has detected failure(s).

Substituted  The working unit has been substituted by the
 protecting unit.
Isolated  The working unit has been isolated with the “Iso-
 late Unit” command.
HW Compatible  The working unit is hardware compatible with the

 protecting unit in the EQP group.
Please refer to section EQP prerequisites
(page 80).
SW Compatible  The working unit is embedded software compati-
 ble with the protecting unit in the EQP group.
Please refer to section EQP prerequisites
(page 80).
DB Saved  The configuration of the unit has been saved.

FOX61xLEDS1 117
FOXCST REFERENCE
Table 32: AP: / unit-x, Status - EQP (continued)

Manual Switch-Over Manual switch of the unit in the EQP group.
A switch over is performed only when the other
unit is error free and is not isolated and the data-
base has been saved.
Refer to the “Manual Switch-Over Allowed” prop-
erty above.
Note: The traffic will be interrupted for about
1 s. a
Forced Switch-Over Forced switch of the unit in the EQP group.
A switch over is performed independent of the
error state of the other unit, but the unit must not
be isolated.
Note: The traffic will be interrupted for about
1 s. a
Note: Traffic will remain interrupted if the active
unit is not operational.
Isolate Unit Isolate the working unit from the EQP group.
An isolated working unit will not perform any pro-
tection switch action. The protection switching
state of the unit is frozen.
Join Unit Join the isolated working unit to the EQP group,
i.e. remove the isolation.
a. The 1 s interruption time is valid for configurations with up to 1 conference only. With
212 conferences the interruption is up to 60 s.
Please note:
Automatic, manual and forced protection switching is available from the
working to the protecting unit and vice versa.
→ Please refer to section Equipment protection (EQP) (page 80).
8.4 AP: / unit-x / conf-z
8.4.1 AP: / unit-x / conf-z, Main
8.4.1.1 AP: / unit-x / conf-z, Main - General

− “Overview - Alarms”, and
− “Overview - Cross Connections”
118 FOX61xLEDS1
FOXCST REFERENCE
8.4.2 AP: / unit-x / conf-z, Main
8.4.2.1 AP: / unit-x / conf-z, Main - General

− “Main - General”
management function, please refer to 1KHW002466 FOXCST Operation.
8.4.3 AP: / unit-x / conf-z, Configuration
8.4.3.1 AP: / unit-x / conf-z, Configuration - General
“Create Participant” and “Delete Participant” dialogues:
Table 33: AP: / unit-x / conf-z, Configuration - General

Create Participant Open the dialogue to add a participant to a
… conference.
Create Participant Index 0 … 255 Select the participant index number.
0 is a reserved value used for the auto-
assignment of a participant index: The auto-
assigned index is the lowest available index
number.
In the FOXCST GUI the default value is the
autoassigned index number.
Delete Participant Open the dialogue to delete a conference.
…
Delete Participant Participant All Delete all or a specific con-
ference participant.
part-1 … part-n
FOX61xLEDS1 119
FOXCST REFERENCE
8.5 AP: / unit-x / conf-z / part-a
8.5.1 AP: / unit-x / conf-z / part-a, Overview

− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
8.5.2 AP: / unit-x / conf-z / part-a, Main
8.5.2.1 AP: / unit-x / conf-z / part-a, Main - General

8.5.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status
Table 34: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status
Operational Status State Up Display of the IETF operational status of the par-
Down ticipant (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.5.3 AP: / unit-x / conf-z / part-a, Configuration

Please note that the fields for some of the configuration parameters are con-
text sensitive. Configuration parameters that are not available due to a
higher-ranking configuration parameter are indicated as “NA” (not available).
The steering parameters for the participant configuration are
• Conference Rate,
• CAS usage.
120 FOX61xLEDS1
FOXCST REFERENCE
8.5.3.1 AP: / unit-x / conf-z / part-a, Configuration - General
Table 35: AP: / unit-x / conf-z / part-a, Configuration - General

Participant Signalling To Con- Yes The control signal processing of a participant
ference at the conference input can be enabled or
No
disabled.
Please refer to section Conference control
signal handling (page 70) for a description of
this parameter.
NA NA (not available) is the only configurable
value if the participant rate is 1984 kbit/s (no
CAS available).
Signalling From Yes The control signal processing of a participant
Conference at the conference output can be enabled or
No
disabled.
this parameter.
CAS available).
Role Local In the point-to-multipoint and multipoint-to-
multipoint linear network applications the
conferences used in the different network
elements (NE) have local connections, a con-
To-Master
nection towards the master NE head end and
a connection towards the slave NE tail end.
The connection role of a participant must be
To-Slave configured according to the NE type.
Please refer to section Network applications
(page 49) for a description of the different NE
types” connections.
Conditional Inter- Yes This parameter allows to disconnect partici-
connection pants from a conference input if the control
No
signal C/105 is in the inactive state.
this parameter.
CAS available).
FOX61xLEDS1 121
FOXCST REFERENCE
8.5.3.2 AP: / unit-x / conf-z / part-a, Configuration - CTP
Please note:
All layer rate, number of time slots and time slot allocation parameters are
read only.
→ To change a parameter the conference has to be deleted and newly
created with the modified parameters.
Table 36: AP: / unit-x / conf-z / part-a, Configuration - CTP

CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is
P0_nc, i.e. n x 64 kbit/s.
The layer rate property of a LEDS1 conference
participant is fixed to P0_nc.
n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-
sible range is from 1 to 32.
The number of time slots of a LEDS1 conference
participant is fixed in the range 1 to 31.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 conference
participant is empty.
Connected to CTPs Remote CTP <MO address> Address string of a connections remote end.
Without a connection the parameter is empty
Connection Index 0 … 65’535 Index of a connection assigned to the partici-
pant. Without a connection the parameter is
empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
122 FOX61xLEDS1
FOXCST REFERENCE
Table 36: AP: / unit-x / conf-z / part-a, Configuration - CTP (contin-

Local Role z-End The participant is the ending point of a connec-
tion.
Please refer to 1KHW002467 FOX61x TDM
Services
a-End Working The participant is the working starting point of a
protected or unprotected connection.
a-End Protecting The participant is the protecting starting point of
a protected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Services
a-End Working The CTP at the connections remote end is the
working starting point of a protected or unpro-
tected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected connec-
tion.
z-End Configuration Revertive Protection  Enable revertive protection switching.
Switching  The z-End will preferably select the working a-
End.
Non-revertive protection switching is only availa-
ble for participants with the number of timeslots
n=1.
Non-revertive protection switching for n>1 will be
available in a future release,
CAS AIS Supervi-  Use CAS AIS as protection switching criterion.
sion  The CAS AIS supervision can be disabled in the
shared protection ring application, where the
closed protection ring can have an AIS in the
CAS, to prevent an alarm during normal opera-
tion.
Switch-Over Log-  Enable the logging of the protection switch-over
ging  events.
Please note:
The z-End of a protected connection shows two entries in the “Connected to
CTPs” table, one for the working and one for the protecting path.
FOX61xLEDS1 123
FOXCST REFERENCE
8.5.4 AP: / unit-x / conf-z / part-a, Fault Management

For a description of the general aspects of the fault management, please
refer to 1KHW002466 FOXCST Operation. The following table lists the fault
causes of the current AP.
Table 37: AP: / unit-x / conf-z / part-a, Fault Management

Affecting Severity
Active tion Alarm vated by the operator from the partici-
pant status dialogue.
TSF Trail Signal Failure Communica-  Major Trail signal fail (TSF) from the P12 trans-
tion Alarm port unit is active, or
CAS AIS active (only available if CAS is
enabled).
In a protected connection the working
AND the protecting path have failed.
RTSF Redundant Trail Signal Communica-  Minor Trail signal fail (TSF) from the P12 trans-
Failure tion Alarm port unit is active, or
enabled).
OR the protecting path has failed.
In an unprotected connection this fault
cause is not applicable.
Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.
8.5.5 AP: / unit-x / conf-z / part-a, Performance Management

For the a description of the general aspects of the performance management
(PM) functions, please refer to 1KHW002466 FOXCST Operation.
The PM parameters are presented in different groups. The following counter
group is available for the LEDS1 conference participants:
• “Protection” group, see section AP: / unit-x / conf-z / part-a, Performance
Management - Protection (page 125),
The following counter intervals are available:
Table 38: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
124 FOX61xLEDS1
FOXCST REFERENCE
8.5.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection
Table 39: PM group: Unfiltered Events

PM parameter Description
Switch-Over The protection switch-over count gives information
about the number and distribution of protection
switching events.
8.5.6 AP: / unit-x / conf-z / part-a, Status
8.5.6.1 AP: / unit-x / conf-z / part-a, Status - General
Table 40: AP: / unit-x / conf-z / part-a, Status - General

To Conference Data 0 Logical state of the data signal going to the con-
1 ference.
Activity On Data Yes Activity on the data signal going to the confer-
ence since the last status refresh.
No
CAS 0000 … 1111 Signalling bits abcd going to the conference.
NA NA (not available) is the displayed if CAS is disa-
bled.
FOX61xLEDS1 125
FOXCST REFERENCE
Table 40: AP: / unit-x / conf-z / part-a, Status - General (continued)

S 0 Logical state of the subrate frame S bit (X.30)
going to the conference.
1
NA NA (not available) is the displayed if the rate is at
64 kbit/s or above, i.e. without subrates, or when
the subrate framing is V.110.
SA 0 Logical state of the subrate frame SA bit (V.110)
1
the subrate framing is X.30.
SB 0 Logical state of the subrate frame SB bit (V.110)
1
X 0 Logical state of the subrate frame X bit (X.30 or
V.110) going to the conference.
1
64 kbit/s or above, i.e. without subrates.
From Conference Data 0 Logical state of the data signal coming from the
1 conference.
Activity On Data Yes Activity on the data signal coming from the con-
ference since the last status refresh.
No
CAS 0000 … 1111 Signalling bits abcd coming from the conference.
NA NA (not available) is the displayed if CAS is disa-
bled.
S 0 Logical state of the subrate frame S bit (X.30)
coming from the conference.
1
the subrate framing is V.110.
SA 0 Logical state of the subrate frame SA bit (V.110)
1
SB 0 Logical state of the subrate frame SB bit (V.110)
1
X 0 Logical state of the subrate frame X bit (X.30 or
V.110) coming from the conference.
1
64 kbit/s or above, i.e. without subrates.
126 FOX61xLEDS1
FOXCST REFERENCE
Please note:
The overhead bits S, SA, SB and X will be available with subrates in a future
release.
8.5.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance
Table 41: AP: / unit-x / conf-z / part-a, Status - Maintenance

Line Status Line Status In-Service Restore the normal operating state of the partici-
pant.
Test-Signal-Insertion Insert a test signal “01” towards the participants
conference.
For more information refer to section DCE inter-
face line state maintenance (page 99).
Out-Of-Service Simulate a failed LEDS1 unit.
For more information refer to section DCE inter-
face line state maintenance (page 99).
FOX61xLEDS1 127
FOXCST REFERENCE
8.5.6.3 AP: / unit-x / conf-z / part-a, Status - CTP
Table 42: AP: / unit-x / conf-z / part-a, Status - CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc signal is
connected to, e.g. /unit-21/port-1/chan-1.
Working Trail, Sta- OK No failure on the received signal.
tus
SF Signal Fail status on the received signal.
CAS AIS CAS AIS status in the received signal, i.e. a
“1111” signal in the signalling pattern of the first
used time slot.
SD Signal Degraded status on the received signal.
Not Available The status of the received signal is not available,
e.g. when the CTPs role is a-end in a unidirec-
tional connection.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Protecting Trail, OK No failure on the received signal.
Status
used time slot.
tional connection.
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.
128 FOX61xLEDS1
FOXCST REFERENCE
Table 42: AP: / unit-x / conf-z / part-a, Status - CTP (continued)

External Request 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
worse than the fault status of the working trail.
8.6 AP: / unit-x / port-y, y = 1 … 4
8.6.1 AP: / unit-x / port-y, Overview

8.6.2 AP: / unit-x / port-y, Main
8.6.2.1 AP: / unit-x / port-y, Main - General

FOX61xLEDS1 129
FOXCST REFERENCE
8.6.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status
Table 43: AP: / unit-x / port-y, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the port
tus (RFC 2863).
Down
Operational Status State Up Display of the IETF operational status of the port
Down (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.6.3 AP: / unit-x / port-y, Configuration

Please note that the fields for some of the configuration parameters are con-
text sensitive. Configuration parameters that are not available due to a
higher-ranking configuration parameter are indicated as “NA” (not available).
The steering parameters for the port configuration are
• Interface Type
• Interface Transmission Mode
• Interface Rate
• Synchronous B/F Signal Usage
• CAS Usage
The configuration strategy to be followed is from the leftmost tab (General) to
the rightmost tab (CTP), and on the tabs from the top parameter downwards.
After completing the parameter configuration of a tab press the “Apply” but-
ton to assign the applicable values to the lower-ranking parameters.
130 FOX61xLEDS1
FOXCST REFERENCE
8.6.3.1 AP: / unit-x / port-y, Configuration - General
Table 44: AP: / unit-x / port-y, Configuration - General

Interface Interface Type V.35 Select the interface type of the DCE port.
X.24-V.11 For valid combinations of the interface type
and other configuration parameters refer to
V.24-V.28 Table 20: Function relationship (page 43).
RS485-2-wire
RS485-4-wire
Transmission Oversampling Select the interface transmission mode.
Synchronous Please refer to section Transmission modes
(page 45) for a description of this parameter.
Asynchronous
Rate 64 … 1984 kbit/s Select the interface rate in steps of 64 kbit/s.
The rate corresponds to the number of time
slots used, i.e. 1 … 31 time slots.
Data Signal Inver-  Invert the logical state of the transmit and
sion receive data signal.

Please note:
The V.24-V.28 interface type in Synchronous transmission mode only sup-
ports interface rates up to 128 kbit/s.
Please note:
The RS485 interface types only support the Oversampling transmission
mode.
Please note:
The Oversampling transmission mode is only available for interface rates at
64 kbit/s and above.
Please note:
The Asynchronous transmission mode is only available for subrates up to
38.4 kbit/s. It will be available in a future release.
FOX61xLEDS1 131
FOXCST REFERENCE
8.6.3.2 AP: / unit-x / port-y, Configuration - Signal Structure
Table 45: AP: / unit-x / port-y, Configuration - Signal Structure

Signal Structure Synchronous, Tim- Contradirectional-Fix Use the contradirectional interface timing
ing with fixed phase alignment.
Only available with the Synchronous trans-
mission mode.
Please refer to section Port timing signals
(page 75).
Contradirectional-Adaptive Use the contradirectional interface timing
with adaptive phase alignment.
mission mode and with interface rates at
Codirectional Use the codirectional interface timing.
mission mode and with interface rates at
value if the transmission mode is Oversam-
pling or Asynchronous.
132 FOX61xLEDS1
FOXCST REFERENCE
Table 45: AP: / unit-x / port-y, Configuration - Signal Structure (con-

Synchronous, B/F None Use no byte (B) or frame (F) timing signal.
Only available with the X.24-V.11 interface
type and the Synchronous transmission
mode.
Please refer to section Port timing signals
(page 75).
Byte-Timing Use the byte (B) timing signal.
mode and interface rates up to 256 kbit/s.
Frame-Timing Use the frame (F) timing signal.
mode and interface rates between 64 and
256 kbit/s.
value
- if the interface type is not X.24-V.11 or
- if the transmission mode is not Synchro-
nous or
- if the interface rate is above 256 kbit/s.
Asynchronous, Data 7 Use 7 or 8 data bits in the start-stop charac-
Bits ter.
8
value if the transmission mode is not Asyn-
chronous
Asynchronous, Stop 1 Use 1 or 2 stop bits in the start-stop charac-
Bits ter.
2
chronous
Asynchronous, Par- No Use or don’t use a parity bit in the start-stop
ity Bit character.
Yes
Note that the parity bit is not evaluated in
LEDS1, it is transported transparently.
chronous
Asynchronous, Sig- Basic Use the basic or extended rate adaptation
nalling Rate Range range for the start-stop characters.
Extended
chronous
FOX61xLEDS1 133
FOXCST REFERENCE
Table 45: AP: / unit-x / port-y, Configuration - Signal Structure (con-

104 Control (RS485 RTS-Control The CAS bit a, set by the control signal RTS
2-wire), Control (C/105) at the remote end, controls the trans-
Mode mitter circuit at the RS485 interface.
The CAS usage limits the maximum interface
rate to 1920 kbit/s.
Refer to section RTS controlled mode
(page 43).
Data-Control The activity of the receive data signal con-
trols the transmitter circuit at the RS485 inter-
face.
Refer to section Data controlled mode
(page 44).
value if the interface type is not RS485 2-
wire.
104 Control (RS485 20 … 1500 samples Time to keep the transmitter circuit active
2-wire), Hold Active after the last 0 to 1 transition.
Time
Please note:
The B/F signal output is only available with the Contradirectional timing
modes.
Please note:
The Asynchronous signal structure parameters will be available in a future
release.
134 FOX61xLEDS1
FOXCST REFERENCE
8.6.3.3 AP: / unit-x / port-y, Configuration - Control Signals

A
Table 46: AAP: / unit-x / port-y, Configuration - Control Signals

Control Signals, 105 (RTS, C) ON Set the local control signal C/105 to 0.
From DTE Please refer to section Control signal han-
dling (page 64).
OFF Set the local control signal C/105 to 1.
From-DTE Set the local control signal C/105 according
to the control signal state received from the
DTE.
value if the interface type is RS485.
108 (DTR) ON Set the local control signal 108 to 0.
Please refer to section Control signal han-
dling (page 64).
OFF Set the local control signal 108 to 1.
From-DTE Set the local control signal 108 according to
the control signal state received from the
DTE.
value if the interface type is X.24-V.11 or
RS485.
FOX61xLEDS1 135
FOXCST REFERENCE
Table 46: AAP: / unit-x / port-y, Configuration - Control Signals (con-

Signalling To Net- No Set the CAS a and b bits to 1 (OFF).
work Please refer to section Port control signal
handling (page 67).
Yes Set the CAS a and b bits according to the C/
105 and 108 control signal state.
value
- if the interface type is RS485 or
- if the interface rate is 1984 kbit/s (no CAS
available).
V/X Compatibility NA NA (not available) is the only configurable
Mode value
- if the interface type is X.24-V.11 or RS485
or
- if the interface rate is 64 kbit/s or above.
Control Signals, To 106 (CTS) ON Set the control signal 106 to ON.
DTE Please refer to section Control signal han-
dling (page 64).
OFF Set the control signal 106 to OFF.
Local-105 Set the control signal 106 according to the
local control signal state C/105.
The activation and deactivation of the control
signal 106 can be without delay or with a
configurable delay. Refer to the “105 (RTS,
C) -> 106 (CTS) / 109 (DCD, I)” parameter
below.
RS485.
107 (DSR) ON Set the control signal 107 to ON.
dling (page 64).
Local-108 Set the control signal 107 according to the
local control signal state 108.
Remote-108 Set the control signal 107 according to the
received CAS b bit.
RS485.
136 FOX61xLEDS1
FOXCST REFERENCE
Table 46: AAP: / unit-x / port-y, Configuration - Control Signals (con-

109 (DCD/I) ON Set the control signal I/109 to ON.
dling (page 64).
OFF Set the control signal I/109 to OFF.
Local-105 Set the control signal I/109 according to the
local control signal state C/105.
The activation and deactivation of the control
signal I/109 can be without delay or with a
configurable delay. Refer to the “105 (RTS,
C) -> 106 (CTS) / 109 (DCD, I)” parameter
below.
Remote-105 Set the control signal I/109 according to the
received CAS a bit.
RS485.
142 (Loopback Indi- ON Set the control signal 142 to ON.
cation) Please refer to section Control signal han-
dling (page 64).
From-DCE Set the control signal 142 according to the
local loop state, i.e.
- Back-To-Back-2b or
- Front-To-Front-3b or
- Front-To-Front-3c.
RS485.
Control Signals, 105 (RTS, C) -> 106 0 ms Propagation delay in ms between the local
Delay Local Control (CTS) / 109 (DCD, control signal C/105 and the control signals
10 ms
Signals I) 106 and I/109, if they are configured to
20 ms “Local-105”.
40 ms Please refer to section Control signal han-
dling (page 64).
FOX61xLEDS1 137
FOXCST REFERENCE
8.6.3.4 AP: / unit-x / port-y, Configuration - Error Handling
Table 47: AP: / unit-x / port-y, Configuration - Error Handling

Error Handling, Consequent Action 0 Replace the receive data signal R/104 by a 0
Receive Failure 104 (RXD, R) or a 1 in case of a downstream failure
1
(server-layer).
Consequent Action OFF Set the byte-timing or frame-timing signal to
B/F OFF in case of a downstream failure (server-
layer).
Active Keep the byte-timing or frame-timing signal
active also in case of a downstream failure.
value if the interface type is not X.24-V.11 or
the B/F parameter is not configured to byte-
timing or to frame-timing.
Error Handling, Level Detection 103 False Supervise the electrical signal levels on the
Transmit Failure (TXD, T) transmit data signal T/103.
True
Please refer to section Port control signal
handling (page 67)
value if the interface type is RS485 2-wire.
138 FOX61xLEDS1
FOXCST REFERENCE
Table 47: AP: / unit-x / port-y, Configuration - Error Handling (contin-

Consequent Action None Apply no consequent action in case of a
103 (TXD, T) detected failure on the transmit data signal T/
103 or transmit clock signal X/113.
0 In case of a detected failure on the transmit
data signal T/103 or transmit clock signal X/
1
113 set the local transmit data signal to 0 or 1
and set the local control signals C/105 and
108 to OFF.
The consequent action on the control signals
affects only the control signal transport via
the CAS.
Note that the “Level Detection 103 (TXD, T)”
must be set to “True”.
Error Handling, DTE Max Send  Supervise the maximum send time on the
Transmit Send Time Time Filter  transmit data signal T/103, i.e. check for
Filter 103 (TXD, T) activity on the data signal.
Please refer to section DTE send and idle
time restrictions (page 101)
DTE Max Send 1 … 10 … 255 s Maximum allowed number of consecutive
Time seconds with observed activity on the trans-
mit data signal T/103.
DTE Min Idle Time  Supervise the minimum idle time on the
Filter transmit data signal T/103, i.e. check for

inactive periods on the data signal.
Please refer to section DTE send and idle
time restrictions (page 101)
DTE Min Idle Time 1 … 10 … 255 s Minimum required number of consecutive
seconds with no activity during the observa-
tion period on the transmit data signal T/103.
DTE Idle Time Win- 2 … 20 … 65’535 s Observation period for the minimum idle
dow time.
Note that the “DTE Idle Time Window” must
be higher than “DTE Min Idle Time”.
FOX61xLEDS1 139
FOXCST REFERENCE

Consequent Action None Apply no consequent action in case of a
On Port detected send or idle time failure on the
transmit data signal T/103.
Persistent In case of a detected send or idle time failure
on the transmit data signal T/103
Auto-Reset
- set the local transmit data signal T/103 to 1,
- set the local control signals C/105 and 108
to OFF,
With “Persistent” the consequent action must
be removed manually in the port status main-
tenance dialogue. Refer to AP: / unit-x / port-
y, Status - Maintenance (page 150).
With “Auto-Reset” the consequent action is
automatically reset 30 s after the clearing of
the failure.
Note that the “DTE Max Send Time Filter” or
the “DTE Min Idle Time Filter” must be set to
“true” to be able to configure “Persistent” or
“Auto-Reset”.
Please note:
The consequent action in case of a detected send or idle time failure over-
rides the consequent action in case of a detected signal level failure.
8.6.3.5 AP: / unit-x / port-y, Configuration - Test Loops
Table 48: AP: / unit-x / port-y, Configuration - Error Handling

Test Loops, Loop Activation By EM All loops can be activated by the element
Activation manager (EM).
The loop activation by the control signal 141
is blocked.
DTE The front-to-front loop 3c can be activated by
the control signal 141.
The loop activation of all loops by the ele-
ment manager (EM) is blocked.
140 FOX61xLEDS1
FOXCST REFERENCE

Test Loops, Signal 103 (TXD, T) 1 Replace the transmit data signal T/103 by a
States When Loop 0, a 1 or a 01 signal in case of an active loop
Active, Loop 3b, 3c 0
3b or loop 3c.
01
Test Loops, Signal 104 (RXD, R) 1 Replace the receive data signal R/104 by a
States When Loop 0, a 1 or a 01 signal in case of an active loop
Active, Loop 2b 0
2b.
01
B/F OFF Set the byte-timing or frame-timing signal to
OFF in case of an active loop 2b.
Active Keep the byte-timing or frame-timing signal
active also in case of an active loop 2b.
value if the interface type is not X.24-V.11 or
the B/F parameter is not configured to byte-
timing or to frame-timing.
8.6.3.6 AP: / unit-x / port-y, Configuration - CTP
Please note:
read only.
→ To change a parameter the port has to be deleted and newly created
with the modified parameters.
FOX61xLEDS1 141
FOXCST REFERENCE
Table 49: AP: / unit-x / port-y, Configuration - CTP

The layer rate property of a LEDS1 port is fixed
to P0_nc.
The number of time slots of a LEDS1 port is
fixed in the range 1 to 31.
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 port is
empty.
Connected to CTPs Connection Index 0 … 65“535 Index of a connections assigned to the port.
Local Role z-End The port is the ending point of a connection.
Please refer to 1KHW002467 FOX61x TDM Ser-
vices
a-End Working The port is the working starting point of a pro-
tected or unprotected connection.
a-End Protecting The port is the protecting starting point of a pro-
tected connection.
Remote CTP <MO address> Address string of a connections remote end.
Please refer to 1KHW002467 FOX61x TDM Ser-
vices
tected connection.
tion.
Unidirectional
142 FOX61xLEDS1
FOXCST REFERENCE
Table 49: AP: / unit-x / port-y, Configuration - CTP (continued)

Switching The z-End will preferably select the working a-
End.

ble for ports with the number of timeslots n=1.
sion The CAS AIS supervision can be disabled in the

tion.
ging events.

Please note:
8.6.4 AP: / unit-x / port-y, Fault Management

The following table lists the fault causes of the current AP.
Table 50: AP: / unit-x / port-y, Fault Management

Affecting Severity
LOS Loss Of Signal Communica-  Major Loss of the incoming transmit data sig-
tion Alarm nal.
Only available if the transmit data signal
level detection is enabled in the port con-
figuration dialogue.
LOC Loss Of Clock Communica-  Major Loss of the incoming transmit clock sig-
tion Alarm nal, evaluated from the physical interface
state and from octet slips.
DTESL DTE Send Time Limit Communica-  Major The connected DTE send time period is
Exceeded tion Alarm longer than allowed.
Only available if the send time limit
supervision is enabled in the port config-
uration dialogue.
If the consequent action is set to “Persis-
tent” the consequent action must be
removed manually in the port status
maintenance dialogue.
FOX61xLEDS1 143
FOXCST REFERENCE
Table 50: AP: / unit-x / port-y, Fault Management (continued)

Affecting Severity
DTEIL DTE Idle Time Below Communica-  Major The connected DTE idle time period is
Limit tion Alarm shorter than allowed during the observa-
tion period.
Only available if the idle time limit super-
vision is enabled in the port configuration
dialogue.
If the consequent action is set to “Persis-
tent” the consequent action must be
removed manually in the port status
maintenance dialogue.
LOF Loss Of Frame Communica-  Major Loss of the V.110 or X.30 frame align-
tion Alarm ment.
Available in a future release.
RLOF Remote Loss Of Frame Communica-  Minor Loss of the V.110 or X.30 frame align-
tion Alarm ment at the remote equipment. The
alarm indication is transported in the X
bit of the V.110 or X.30 frame.
Available in a future release.
NDPF Near End Degraded Quality Of  Warning SES ≥ 22 over a 24 hour interval at the
Performance Service Alarm near end.
The alarm status is reset after a 24 hour
interval with SES = 0.
SES is a second with an active LOS or
LOC fault cause.
The alarm can be cleared by resetting
the corresponding PM alarm counter.
NUPF Near End Unacceptable Quality Of  Warning SES ≥ 15 over a 15 min. interval at the
Performance Service Alarm near end.
The alarm status is reset after a 15 min.
interval with SES = 0.
SES is a second with an active LOS or
LOC fault cause.
The alarm can be cleared by resetting
the corresponding PM alarm counter.
Active tion Alarm vated by the operator from the port sta-
tus dialogue.
enabled), or
LOF is active.
enabled), or
LOF is active.
144 FOX61xLEDS1
FOXCST REFERENCE
Please note:

With the V.24-V.28 interface type and synchronous transmission mode,
there can be crosstalk on the connected cable from the clock to the transmit
data signal.
→ The “Loss Of Signal” alarm is possibly not detected.
8.6.5 AP: / unit-x / port-y, Performance Management

For the description of the general aspects of the performance management
groups are available for the LEDS1 ports:
• “Protection” group, see section AP: / unit-x / port-y, Performance Man-
agement - Protection (page 145),
• “G.826” group, see section AP: / unit-x / port-y, Performance Manage-
ment - G.826 (page 145),
• “Unfiltered Events” group, see section AP: / unit-x / port-y, Performance
Management - Unfiltered Events (page 146),
The following counter intervals are available, depending of the counter
group:

Counter interval Protection G.826 Unfiltered Events
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no yes no
Alarm 24h no yes no
8.6.5.1 AP: / unit-x / port-y, Performance Management - Protection
Table 52: PM group: Protection

switching events.
8.6.5.2 AP: / unit-x / port-y, Performance Management - G.826
Table 53: PM group: G.826

Near End SES Near end count of Severely Errored Seconds.
A second with a defect signal (LOS or LOC) and not
part of unavailable time (UAT).
FOX61xLEDS1 145
FOXCST REFERENCE
Table 53: PM group: G.826 (continued)

Near End UAT Near end count of Unavailable Time.
Unavailable time starts with 10 consecutive SES
(included in UAT) and ends with 10 consecutive
error free seconds (not included in UAT).
8.6.5.3 AP: / unit-x / port-y, Performance Management - Unfiltered Events
Table 54: PM group: Unfiltered Events

Positive Slips Count of the positive octet slips between the incom-
ing X/113 timing and the local S/114 timing.
The DTE source clock is higher than the DCE
source clock.
Negative Slips Count of the negative octet slips between the incom-
ing X/113 timing and the local S/114 timing.
The DTE source clock is lower than the DCE source
clock.
146 FOX61xLEDS1
FOXCST REFERENCE
8.6.6 AP: / unit-x / port-y, Status
8.6.6.1 AP: / unit-x / port-y, Status - General
Table 55: AP: / unit-x / port-y, Status - General

From DTE 103 (TXD, T) 1 Signal state of the transmit data signal T/103.
Note that the state at the interface circuit is dis-
0
played. The data signal inversion configuration
does not influence the status indication.
Activity On 103 Yes Observed activity on the transmit data signal T/
(TXD, T) 103 since the last status refresh.
No
FOX61xLEDS1 147
FOXCST REFERENCE
Table 55: AP: / unit-x / port-y, Status - General (continued)

105 (RTS,C) On Signal state of the control signal C/105.
Off
NA NA (not available) is the displayed if the interface
type is RS485.
108 (DTR) On Signal state of the control signal 108.
Off
NA NA (not available) is displayed if the interface
type is X.24-V.11 or RS485.
141 (LL) On Signal state of the control signal 141 (loop com-
mand).
Off
To Network CAS 0000 … 1111 CAS abcd pattern sent towards the network.
With a P0-nc data signal the CAS abcd pattern is
sent with every time slot.
The a bit can be controlled by the control signal
C/105.
The b bit can be controlled by the control signal
108.
Note: With a P0-nc data signal with n=31
(1984 kbit/s) it is not possible to transport this
CAS abcd pattern in a P12 transport signal.
S 0 Signal state of the sent subrate frame S bit
(X.30).
1
The S bit can be controlled by the control signal
C.
rate is at 64 kbit/s or above, i.e. without subrates,
or when the interface type is not X.24-V.11.
SA 0 Signal state of the sent subrate frame SA bit
(V.110).
1
The SA bit can be controlled by the control signal
108.
or when the interface type is X.24-V.11.
SB 0 Signal state of the sent subrate frame SB bit
(V.110).
1
The SB bit can be controlled by the control signal
105.
X 0 Signal state of the sent subrate frame X bit (X.30
or V.110).
1
The X bit is controlled by the state of the subrate
frame alignment.
rate is at 64 kbit/s or above, i.e. without subrates.
148 FOX61xLEDS1
FOXCST REFERENCE

From Network CAS 0000 … 1111 CAS abcd pattern received from the network.
With a P0-nc data signal the CAS abcd pattern
of the lowest numbered time slot is displayed.
The a bit can control the control signal I/109.
The b bit can control the control signal 107.
S 0 Signal state of the received subrate frame S bit
(X.30).
1
The S bit can control the control signal I.
or when the interface type is V.24-V.28 or V.35.
SA 0 Signal state of the received subrate frame SA bit
(V.110).
1
The SA bit can control the control signal 107.
SB 0 Signal state of the received subrate frame SB bit
(V.110).
1
The SB bit can control the control signal 109.
X 0 Signal state of the received subrate frame X bit
(X.30 or V.110).
1
The X bit can control the control signal 106.
rate is at 64 kbit/s or above, i.e. without subrates.
To DTE 104 (RXD, R) 1 Signal state of the receive data signal R/104.
Note that the state before the interface circuit is
0
displayed.
Activity On 104 Yes Observed activity on the receive data signal R/
(RXD, R) 104 since the last status refresh.
No
106 (CTS) On Signal state of the control signal 106.
Off
107 (DSR) On Signal state of the control signal 107.
Off
109 (DCD/I) On Signal state of the control signal 109.
Off
type is RS485.
FOX61xLEDS1 149
FOXCST REFERENCE

142 (TM) On Signal state of the control signal 142 (loop indi-
cation).
Off
Please note:
The overhead bits S, SA, SB and X will be available with subrates in a future
release.
8.6.6.2 AP: / unit-x / port-y, Status - Maintenance
Table 56: AP: / unit-x / port-y, Status - Maintenance

Line Status State In-Service Restore the normal operating state of the
front port.
Test-Pattern-Insertion Insert a test pattern “01” towards the front
port.
Note that in the oversampling transmission
mode the test pattern is generated with the
sampling rate.
For more information refer to section DCE
interface line state maintenance (page 99).
Out-Of-Service Simulate a failed LEDS1 unit.
For more information refer to section DCE
interface line state maintenance (page 99).
Loop Status State None Deactivate any loop.
Back-To-Back-2b Activate the back-to-back loop 2b.
For more information refer to section Loops
(page 96).
Front-To-Front-3b Activate the front-to-front loop 3b.
(page 96).
This loop is not available for the interface
type RS485 2-wire.
Front-To-Front-3c Activate the front-to-front loop 3c.
(page 96).
This loop is not available for the interface
type RS485 2-wire.
150 FOX61xLEDS1
FOXCST REFERENCE
Table 56: AP: / unit-x / port-y, Status - Maintenance (continued)

Reset Send Time Reset the consequent action from a violation
Filter Consequent of the transmit signal send time or idle time
Action filter condition.
The consequent action can be reset if the
consequent action mode is set to “Persistent”
or to “Auto-Reset”.

When resetting the send time filter consequent action while the input signal
still violates the filter conditions, traffic can be disturbed.
8.6.6.3 AP: / unit-x / port-y, Status - CTP
Table 57: AP: / unit-x / port-y, Status - CTP

tus
used time slot.
tional connection.
FOX61xLEDS1 151
FOXCST REFERENCE
Table 57: AP: / unit-x / port-y, Status - CTP (continued)

Status
used time slot.
tional connection.
been selected.
has been selected.
working remote CTP.
8.7 AP: / unit-x / port-y, y = 5
8.7.1 AAP: / unit-x / port-y, Overview

152 FOX61xLEDS1
FOXCST REFERENCE
8.7.2 AP: / unit-x / port-y, Main
8.7.2.1 AP: / unit-x / port-y, Main - General

8.7.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status
Table 58: AP: / unit-x / port-y, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the port
tus (RFC 2863).
Down
Operational Status State Up Display of the IETF operational status of the port
Down (RFC 2863).
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.7.2.3 AP: / unit-x / port-y, Configuration - QoS
FOX61xLEDS1 153
FOXCST REFERENCE
Table 59: AP: / unit-x / port-y, Configuration - QoS

QoS, Mapping Pro- Name <List of downloaded QoS map- Select the appropriate profile from the drop
file ping profiles> down list.
Preview This command opens a window displaying
the parameters of the actually selected pro-
file. The contents are identical to those
described in the section Profiles (page 109).
Default Priority 0…7 Default 802.1p priority for untagged packets
Priority Source IP Check the DSCP field of the IP header to
determine the priority of the packet.
MAC Check the 802.1p priority bits of the MAC
header to determine the priority of the
packet.
IP Then MAC Check the DSCP field if it exists, otherwise
check the 802.1p priority bits to determine
the priority of the packet.
MAC Then IP Check the 802.1p priority bits if they exist,
otherwise check the DSCP field to determine
8.7.2.4 AP: / unit-x / port-y, Configuration - PHY
Table 60: AP: / unit-x / port-y, Configuration - PHY

PHY Mode PHY Mode Autonegotiation Select the LAN mode of the Ethernet inter-
10 Mbit/s Full Duplex face.
10 Mbit/s Half Duplex

100 Mbit/s Full Duplex

full duplex”.
interface.
154 FOX61xLEDS1
FOXCST REFERENCE
8.7.3 AP: / unit-x / port-y, Configuration
8.7.3.1 AP: / unit-x / port-y, Configuration - QoS
Table 61: AP: / unit-x / port-y, Configuration - QoS

QoS, Mapping Pro- Name <List of downloaded QoS map- Select the appropriate profile from the drop
file ping profiles> down list.
Preview This command opens a window displaying
the parameters of the actually selected pro-
file. The contents are identical to those
described in the section Profiles (page 109).
Default Priority 0…7 Default 802.1p priority for untagged packets
Priority Source IP Check the DSCP field of the IP header to
determine the priority of the packet.
MAC Check the 802.1p priority bits of the MAC
header to determine the priority of the
packet.
IP Then MAC Check the DSCP field if it exists, otherwise
check the 802.1p priority bits to determine
MAC Then IP Check the 802.1p priority bits if they exist,
otherwise check the DSCP field to determine
FOX61xLEDS1 155
FOXCST REFERENCE
8.7.3.2 AP: / unit-x / port-y, Configuration - PHY
Table 62: AP: / unit-x / port-y, Configuration - PHY

PHY Mode PHY Mode Autonegotiation Select the LAN mode of the Ethernet inter-
face.

full duplex”.
interface.
8.7.3.3 AP: / unit-x / port-y, Configuration - TDM
Table 63: AP: / unit-x / port-y, Configuration

TDM Rate 64 … 1984 kbit/s Select the transport rate of the TDM WAN
interface.
Values can be selected in steps of 64 kbit/s.
156 FOX61xLEDS1
FOXCST REFERENCE
8.7.3.4 AP: / unit-x / port-y, Configuration - CTP
Please note:
read only.
→ To change a parameter the port has to be deleted and newly created
with the modified parameters.
Table 64: AP: / unit-x / port-y, Configuration - CTP

The layer rate property of a LEDS1 Ethernet port
is fixed to P0_nc.
The number of time slots of a LEDS1 Ethernet
port is fixed in the range 1 to 31.
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 port is
empty.
Connected to CTPs Remote CTP <MO address> Address string of a connections remote end.
Connection Index 0 … 65’535 Index of a connection assigned to the port. With-
out a connection the parameter is empty
Unidirectional
FOX61xLEDS1 157
FOXCST REFERENCE
Table 64: AP: / unit-x / port-y, Configuration - CTP (continued)

Local Role z-End The port is the ending point of a connection.
Services.
a-End Working The port is the working starting point of a pro-
tected or unprotected connection.
a-End Protecting The port is the protecting starting point of a pro-
tected connection.
Services.
tected connection.
tion.
Switching  The z-End will preferably select the working a-
End.
ble for ports with the number of timeslots n=1.
sion  The CAS AIS supervision can be disabled in the
tion.
ging  events.
Please note:
8.7.4 AP: / unit-x / port-y, Fault Management

The following table lists the fault causes of the current AP.
Table 65: AP: / unit-x / port-y, Fault Management

Affecting Severity
LOSETH Ethernet Link Down Communica-  Major Loss of the incoming Ethernet signal.
tion Alarm
158 FOX61xLEDS1
FOXCST REFERENCE
Table 65: AP: / unit-x / port-y, Fault Management (continued)

Affecting Severity
LOSTDM TDM Link Down Communica-  Major Loss of the incoming TDM data signal.
tion Alarm The alarm is activated if no activity is
detected in the TDM signal.
The alarm is also activated if the

remote station sends no HDLC-flags in
the idle state. In this case disable the
alarm monitoring.
CAS AIS active (only available if CAS
AIS supervision is enabled).
CAS AIS active (only available if CAS
AIS supervision is enabled).
Please note:
8.7.5 AP: / unit-x / port-y, Performance Management

For the a description of the general aspects of the performance management
groups are available for the LEDS1 Ethernet port:
• “Protection” group, see section AP: / unit-x / port-y, Performance Man-
agement - Protection (page 160),
• “MIB-2 Ethernet Interface” group, see section AP: / unit-x / port-y, Perfor-
mance Management - MIB-2 Ethernet Interface (page 160).
• “MIB-2 TDM Interface” group, see section AP: / unit-x / port-y, Perfor-
mance Management - MIB-2 TDM Interface (page 160).
The following counter intervals are available, depending of the counter
group:

Counter interval Protection MIB-2 Ethernet MIB-2 TDM Inter-
Interface face
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no no no
Alarm 24h no no no
FOX61xLEDS1 159
FOXCST REFERENCE
8.7.5.1 AP: / unit-x / port-y, Performance Management - Protection
Table 67: PM group: Protection

switching events.
8.7.5.2 AP: / unit-x / port-y, Performance Management - MIB-2 Ethernet Interface
Table 68: PM group: MIB-2 Ethernet Interface

In Octets The total number of octets received on the interface,
including framing characters
In Unicast Packets The number of unicast packets, i.e. packets with a
single address delivered to a higher-layer protocol.
In Non-unicast Packets The number of multicast or broadcast packets deliv-
ered to a higher-layer protocol.
In Discards The number of inbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol. One possible reason for dis-
carding such a packet could be to free up buffer
space.
In Errors The number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.
Out Octets The total number of octets transmitted out of the
interface, including framing characters.
Out Unicast Packets The total number of unicast packets that higher-level
protocols requested to be transmitted, including
those that were discarded or not sent.
Out Non-unicast Packets The total number of multicast or broadcast packets
that higher-level protocols requested to be transmit-
ted, including those that were discarded or not sent.
Out Discards The number of outbound packets which were cho-
sen to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space.
Out Errors The number of outbound packets that could not be
transmitted because of errors.
8.7.5.3 AP: / unit-x / port-y, Performance Management - MIB-2 TDM Interface
Table 69: PM group: MIB-2 TDM Interface

In Octets The total number of octets received on the interface,
including framing characters
160 FOX61xLEDS1
FOXCST REFERENCE
Table 69: PM group: MIB-2 TDM Interface

In Unicast Packets The number of unicast packets, i.e. packets with a
single address delivered to a higher-layer protocol.
In Non-unicast Packets The number of multicast or broadcast packets deliv-
ered to a higher-layer protocol.
In Discards The number of inbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol. One possible reason for dis-
carding such a packet could be to free up buffer
space.
In Errors The number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.
Out Octets The total number of octets transmitted out of the
interface, including framing characters.
Out Discards The number of outbound packets which were cho-
sen to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space.
Out Errors The number of outbound packets that could not be
transmitted because of errors.
8.7.6 AP: / unit-x / port-y, Status
8.7.6.1 AP: / unit-x / port-y, Status - PHY

A
Table 70: AAP: / unit-x / port-y, Status - PHY

PHY State Speed Link Down Speed state of the Ethernet port.
100 Mbit/s
10 Mbit/s
Unknown
Duplex Link Down Duplex state of the Ethernet port.
Full Duplex
Half Duplex
Unknown
FOX61xLEDS1 161
FOXCST REFERENCE
Table 70: AAP: / unit-x / port-y, Status - PHY (continued)

IEEE 802.3 Flow  State of the flow control configuration.
Control 
8.7.6.2 AP: / unit-x / port-y, Status - TDM
Table 71: AP: / unit-x / port-y, Status - TDM

Link Status State Up The TDM link status is up if there is activity on
Down the TDM link.
The TDM link status is down if there is no activity
Unknown on the TDM link.
Note that the port operational state follows the
link status.
8.7.6.3 AP: / unit-x / port-y, Status - Bridge
Table 72: AP: / unit-x / port-y, Status - Bridge

MAC Table MAC Address 00:00:00:00:00:00 … Shows the MAC address of the remote port.
ff:ff:ff:ff:ff:ff
Ingress Interface TDM Shows the local bridge ingress interface.
Ethernet
Expires In 0 … 300 [s] MAC address expiration time in seconds.
The MAC address aging timer has a fixed value
of 300 s.
162 FOX61xLEDS1
FOXCST REFERENCE
8.7.6.4 AP: / unit-x / port-y, Status - CTP
Table 73: AP: / unit-x / port-y, Status - CTP

tus
used time slot.
tional connection.
Status
used time slot.
tional connection.
been selected.
has been selected.
FOX61xLEDS1 163
FOXCST REFERENCE
Table 73: AP: / unit-x / port-y, Status - CTP (continued)

working remote CTP.
164 FOX61xLEDS1
ANNEX
9 Annex
9.1 Associated documents
1KHW028514 FOX61x Abbreviations and Terms

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
1KHW002467 FOX61x TDM Services
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
1KHW002479 FOX61x LEDA1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1
1KHW002482 FOX61x Electrical Cables
FOX61xLEDS1 165
ANNEX
166 FOX61xLEDS1
Contact us
ABB Switzerland Ltd
1KHW002478 © 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: [email protected]
www.abb.com/utilitycommunication

FOX61x Leds1: User Manual

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

FOX61x Leds1: 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 Leds1: 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.: 1KHW002478

ABB Switzerland Ltd

3 Functions and specifications 19

8 FOXCST Reference 107

Figure 1: DTEs connected in a star network, with conference 15

Table 1: Electrical interfaces and circuit categories 13

1.2 Symbols and notations

This User Manual uses the following symbols:

Risk of operating trouble!

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

1.4 Document history

Table 2: Document history

1.5 Definition of terms

Table 3: Specific terms

P12 transport unit

Figure 1: DTEs connected in a star network, with conference

2.2 Unit view

Figure 2: LEDS1 unit view

2.3 Block diagram

nx64 kbit/s - X.24/V.11 2

Cross 27 x P12 Conferencing

Figure 3: LEDS1 functional block diagram

3 Functions and specifications

3.1 Feature licences

This unit is not subject to feature licences.

3.2 Summary of standards

Table 4: Standards (continued)

- ANSI/IEEE Std 802.1D, 1998

Table 4: Standards (continued)

3.3 DCE functions and specifications

Table 5: DCE functions and specifications

Table 5: DCE functions and specifications (continued)

3.4 DCE physical layers

Table 6: V.24/V.28 DCE physical layer functions and specifications

Table 7: X.24/V.11 DCE physical layer functions and specifications

Table 7: X.24/V.11 DCE physical layer functions and specifications

Table 8: V.35 DCE physical layer functions and specifications

Note: The signal list is according to ITU-T V.36, i.e.

Table 8: V.35 DCE physical layer functions and specifications (con-

Table 9: RS485 DCE physical layer functions and specifications

The signal 103 acts as a single receiver with multi-

Note: The signals 103 and 104 shall not be con-

The signal 103 acts as a single receiver with multi-

Note: It is assumed, that a second bus terminating

Table 9: RS485 DCE physical layer functions and specifications

3.5 MAC bridging

Table 10: MAC bridging functions and specifications

Table 10: MAC bridging functions and specifications (continued)

Table 11: General functions and specifications

Table 11: General functions and specifications (continued)

Table 11: General functions and specifications (continued)

4.2 Slots and deployment scenarios for the LEDS1 unit