Manual FOX ABB Teleprotecciones.pdf

FOX from ABB
covers all your communication require-
ments in one system
FOX Manual "Units"
Part 1
4th
Edition
1KHW001447R0001
The
universal
multiplexer
FOX

Control Units
1. COBUX 212, 213, 219, 223 &
COBUV 217, 218, 220, 224 [315]
1
Power Units
1. POSUS 106 [311]
2. POSUA 206 & BATMO [329]
3. POSUM 306 [344]
2
UBus Units
1. GECOD 371, 372 [002]
2. NTU 411, 412 [002]
3. EXBAT 401 and SUBAT 461 [002]
4. EXLIC 451 and SULIS 493 [002]
5. UNIDA 431, 432, 433, 434, 435 [002]
6. UNIDA 436, 437 & 438 [343]
3
UBus Units
7. ISBUQ 141 [318]
8. ISBUT 110 [325]
9. TUNOL 299, 286 & TUNOR [332]
4
UBus Units
10. ALCAR 804 [002]
11. ETHUB 194 [002]
12. OTERM [002]
13. TEBIT [002]
5
ABB
FOX Manual
„Units“
Part 1
1KHW001447R0001
UBus Units (Extract of FOX-U Manual)
14. NEMCA 301, 311, 312 and NEMGE 315, 316 [002]
15. EXLAx/SUBLx POTS Interface Units [002]
6

ABB
FOX from ABB, covers all your communication
requirements in one system.
FOX Manual Units, Part 1
(4th Edition)
COBUX 219, 223, 212, 213
COBUV 220, 224, 217, 218

COBUX/COBUV
Copyright and Confidentiality: Copyright in this document vests in ABB Ltd. This document contains
confidential information which is the property of ABB. It must be held in
confidence by the recipient and may not be used for any purposes
except those specifically authorised by contract or otherwise in writing
by ABB. This document may not be copied in whole or in part, or any of
its contents disclosed by the recipient to any third party, without the
prior written agreement of 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 reserves the right to amend this document at any time without
prior notice.
Document number: 1KW001447R0001 / Ref [315]
ABB Switzerland Ltd
Bruggerstrasse 72
CH-5400 Baden
Switzerland © January 2005 by ABB Ltd

ABB © ABB Ltd
Contents i
Safety 1
Referenced documents 1
Introduction 2
Functions 2
Common functions of the COBUX and COBUV 2
Conference function (COBUV only) 3
Functional versions 3
Definition of terms 5
Front panel 5
Architectural description 6
Block diagram 8
Descriptions 8
CPU block 8
Clock Supply and Synchronisation 8
Intra Unit Communication 9
Highway Access and DXC 9
NE Database 9
QX-interface 9
F-/Q1-interface 9
Q1-master interface 9
OSPF router 10
Alarm Interface 10
Metering Pulse Generator 10
1+1 Unit Protection Control 10
Diagnostics 10
Conference Processing (COBUV only) 10
Functional description 11
Clock supply & synchronisation PDH domain (PETS) 12
Timing sources and signals 12
Timing signal outputs 12
PLL and clock signals 13
Modes 14
Jitter transfer function 14
Intra unit communication 15
Overview 15
Hardware control 16
µC-LAN 16
ICN 17
1KHW001447R0001 FOX Manual Units, Part 1 iii

ABB Contents © ABB Ltd
NE MIB / PC memory card 17
Cross connect 18
Principles 18
Capacities 19
1+1 equipment protection 19
Metering pulse generator 19
Diagnostic function 19
Conference function (COBUV only) 21
Analogue Conference 21
Digital Conference (signalling) 22
Example 23
NE management and control 23
Handling of configuration data 24
Software Management 24
Fault Management 25
Interfaces for management communication 27
QX-interface: 27
F-interface: 28
Q1-(slave) interface: 28
Q1-master interface: 29
PDH ECC 29
SDH ECC 29
ECC over ATM 30
Bandwidth for the allocation of PDH and SDH ECCs 30
Alarm Interfaces 30
Alarm state outputs 30
Inputs for external alarm signals 31
Interfaces for timing signals 32
Installation 33
Prerequisites 33
Use of slots 34
Connections and cables 34
F- interface (9-pin submini D) 34
QX-interface (RJ-45 connector) 37
DIN 41 612 front connector 38
Q1-(slave) interface 40
Q1-master interface 40
Alarm interfaces 41
Synchronisation interfaces 42
Fixing the cables to the cable tray 45
Configuration and Operation 46
Overview 46
Setting basic parameters 47
Board 47
Communication IF 49
NE MCN parameters 52
Guidelines for the configuration of the NE MCN part 52
SDH ECC 57
iv “Units” Part 1 1KHW001447R0001

OSI DCN 57
PDH ECC 58
IP Router 58
Setting a conference (COBUV only!) 58
Name 59
Conference 59
Input attenuation 59
Noise suppression 60
Output attenuation 60
Setting diagnostics 60
Test set-up 60
Configuration of the diagnostic function 61
Enable diagnostics 62
Bit rate 62
Test signal (data) 62
Test pattern (signalling) 62
Error insertion 63
Cross connections for diagnostics 63
Download configuration or configuration changes 64
Setting 1+1 equipment protection for COBU<X> 64
Implementation 64
Switching criteria 66
Status/Maintenance functions 66
Board 67
Communication IF 72
NE MCN parameters 73
IP Router 73
IP Ping 73
Diagnostics 74
Operating states of the COBU<X> 87
COBU<X> start up 90
Cold/warm start up 90
Influence on traffic and services 90
Removal of operating COBU<X> 91
Setting Alarm Parameters 91
Summary of UCST default parameters 91
Board layer 91
Communication IF layer 91
SDH ECC layer 92
OSI DCN layer 92
PDH ECC layer 92
IP Router 92
Conference Parties layer (COBUV only) 92
Diagnostics layer 92
Unit alarms 92
Performance monitoring 93
Definition of terms 93
Filtered PM 93
Diagnostics 93
1KHW001447R0001 FOX Manual Units, Part 1 v

Examples of COBU<X> PM 94
Unfiltered PM 95
Alarms and Notifications 96
Fault cause tables 96
Board Layer 96
Communication IF layer 99
SDH ECC layer 99
PDH ECC layer 99
Notifications 100
Notifications control unit board layer 100
Notifications NE unit board layer 101
Notifications IP router layer 103
Notifications OSI DCN layer 103
Maintenance 104
Unit top component and front panel view 104
General aspects 105
Inventory Management 105
Software Download 105
Upgrades 106
Exchange of the PC Card 107
PC Card Handling Precautions 107
PC Card exchange procedure 107
vi “Units” Part 1 1KHW001447R0001

Figures
Figure 1: Released Control units/FOX applications 2
Figure 2: Front panel view of COBU<X> unit 6
Figure 3: Block diagram of COBU<X> unit 8
Figure 4: COBU<X> PDH clock supply and synchronisation block diagram 13
Figure 5: Timing sources sample dialogue 15
Figure 6: Communication structures vs. unit category 16
Figure 7: Principles of traffic channel diagnostics 21
Figure 8: Example of a conference party with 3 participants 22
Figure 9: Example for the signalling in a conference with 3 participants 23
Figure 10: Internal wiring of the alarm state relays 31
Figure 11: Internal wiring of the alarm inputs 32
Figure 12: Signal/pin layout for the F- interface connector 34
Figure 13: COBUX/C3.1-1 cable drawing 35
Figure 16: COBUX/C3.1-3 cable application drawing 36
Figure 17: Signal/pin layout for the QX-interface connector 37
Figure 20: Signal/pin layout for the DIN 41 612 connector 39
Figure 21: COBUX/C1.4 cable drawing 40
Figure 28: Fixing the cables to the cable tray (example for the FOX 515) 45
Figure 29: Unit Configuration Parameters - Board layer dialogue 47
Figure 30: Unit Configuration Parameters - Communication IF layer
dialogue 49
Figure 31: Flow chart configuration of the management communication 54
Figure 32: Unit Configuration Parameters – Conference Part. layer
dialogue 59
Figure 33: Unit Configuration Parameters – Diagnostics layer dialogue 61
Figure 34: Create Cross Connections dialogue 63
Figure 35: NE Configuration – Add Protecting Unit dialogue 65
Figure 36: Status/Maintenance - Board dialogue 67
Figure 37: State messages of COBU<X> 69
Figure 38: Status/Maintenance – Communication IF dialogue 72
Figure 39: Status/Maintenance – IP Router IP Ping Request dialogue 74
Figure 40: Summary of analysis and quality assessment functions 75
Figure 41: Diagnostics – No Status Available dialogue 76
Figure 42: Status/Maintenance – Diagnostics dialogue 76
Figure 43: Test set-up for timeslot monitoring 78
1KHW001447R0001 FOX Manual Units, Part 1 vii

Figure 44: Status/Maintenance – Diagnostics dialogue Analysis of a n x 64
kbit/s test signal 79
Figure 45: Status/Maintenance – Diagnostics dialogue Analysis of a n x 64
kbit/s test signal, AIS on signalling 80
Figure 46: Status/Maintenance – Diagnostics dialogue Analysis of a 64
kbit/s test signal (data) 81
Figure 47: Status/Maintenance – Diagnostics dialogue Analysis of a 64
kbit/s test signal (signalling) 81
Figure 48: Status/Maintenance – Diagnostics dialogue Analysis of 2 Mbit/s
transparent test signals, no offset 82
Figure 49: Status/Maintenance – Diagnostics dialogue Analysis of 2 Mbit/s
transparent test signals, with offset 83
Figure 50: Test set-up for delay measurements 84
Figure 55: Operating states and NE activities indicated via the unit LED 87
Figure 56: Operating states indicated via the Unit LED 89
Figure 57: COBU<X> - Performance Monitoring sample dialogue 93
Figure 58: COBU<X> - Performance Monitoring sample dialogue Events
presentation 94
Figure 59: COBU<X> - Performance Monitoring sample dialogue Ratio
presentation 95
Figure 60: Fault Causes and alarms of the Board Layer 96
Figure 61: Fault Causes and alarms of the Communication IF Layer 99
Figure 62: Fault Causes and alarms of the SDH ECC Layer 99
Figure 63: Fault Causes and alarms of the PDH ECC Layer 99
Figure 64: Notifications on the Control Unit Board Layer 100
Figure 65: Notifications on the NE Unit Board Layer (proxy function of the
COBU<X>) 101
Figure 66: Notifications on the IP Router Layer 103
Figure 67: Notifications on the OSI DCN Layer 103
Figure 68: COBU<X> top component side and front panel view 104
Figure 69: To remove the PC Memory Card 108
Figure 70: To insert the PC Memory Card 108
viii “Units” Part 1 1KHW001447R0001

ABB COBUX/COBUV © ABB Ltd
Safety
For generic information on precautions and safety refer to [033].
Except for the standard precautions for ESD outlined in the installation
section when handling the unit, there are no special safety precautions to be
followed in installing and commissioning the COBUV and the COBUX units.
Referenced documents [033] 1KHW001445R0001 Precautions and safety
[301] 1KHW001445R0001 FOX 515 Installation Guide
[302] 1KHW001445R0001 FOX User Guide (R6)
[303] 1KHW001445R0001 FOX 512 Installation Guide
[401] 1KHW001446R0001 UCST/System Operation Basics (R6)
[402] 1KHW001446R0001 UCST Installation & Commissioning (R6)
[901] 1KHW001446R0001 FOX Management Communication
Networks (R6)
[914] 1KHW001446R0001 FOX EOC (Embedded Operation Channel)
1KHW001447R0001 FOX Manual Units, Part 1 page 1 of 108

Introduction
Functions
Common functions of the
COBUX and COBUV
The COBUX and COBUV are control units for the FOX 515/512 Multiservice
Access Systems.
Please note, that not all control units are released for all FOX subracks
(refer to the table below).
With the UCST R6A the R5 and R4 control units are available for the FOX
system configuration. The control units are released for the FOX and
corresponding applications as follows:
Figure 1: Released Control units/FOX applications
Control
Unit
Function Unit Release FOX
R5 R4
40HW 128HW 40HW 128HW
515 512
COBUX 223 219 213 212 R5, R4 R5, R4
COBUV 224 220 218 217 R5, R4 R5, R4
The functions common to all COBUX and COBUV control units are:
• Clock supply and synchronisation for the PDH domain (PETS) for the NE
• Integration of 2 external timing signals for the synchronisation of the NE
(1 PETS only and 1 SETS or PETS), 3 outputs with timing signals
synchronised to PETS and 1 output SETS locked or non SETS locked.
• NE database
• NE management/control to allow:
− Configuration of peripheral units
− Surveillance and alarm generation for peripheral units
− Provision of the NE fault list and NE alarm/event logbook
− Access for local and remote management communication with the
UCST (EM) via the following management interfaces:
− F-interface (external)
− QX-interface (external)
− Q1-interface (external)
− PDH and SDH ECC (internal)
− ECC over ATM, as PDH ECC (internal)
− Provision of the Q1-master interface (external) to manage a co-located
LEGACY FOX on the local Q-Bus via the management
communication of the FOX 515/512.
− Handling of data transactions for the database
(configuration download and upload, backup database)
− Software download for the embedded software (ESW)
− Autonomous restart of the NE after a power failure (no interaction by
EM required)
− Inventory management
• 1+1 equipment protection
• UBUS ↔ PBUS access
• UBUS digital cross connect
page 2 of 108 FOX Manual Units, Part 1 1KHW001447R0001

The COBUX and COBUV provide a UBUS access capacity of
8 highways, each highway for traffic signals (signalling included)
− 31 x 64 kbit/s (depending on the unit as a bundle access for 31 TSs or
as n x 64 kbit/s TS access)
− the highways access in the slots of the subrack depends on the
FOX subrack.
The even numbered highways are reserved exclusively for signalling.
• PBUS access control
The COBUX and COBUV provide a PBUS access capacity (signalling
included) of up to 128 highways depending on the functional units, each
highway configurable for traffic signals
− 2 Mbit/s transparent or
− 31 x 64 kbit/s (depending on the unit as a bundle access for 31 TSs or
as n x 64 kbit/s TS access)
• Integrated central diagnostic function
• Integration of 4 external alarm sources in the NE fault management
• Capability to output the NE alarm status "Urgent Alarm" and "Non-urgent
Alarm" by means of:
− two pairs of change-over relay contacts
− optical LED indicators on the control unit front panel
• Generation of 12 kHz or 16 kHz metering pulses
Conference function (COBUV
only)
The COBUV control units also provide the possibility to create up to 21 bi-
and uni-directional conferences, each conference with up to 64 participants
(64 kbit/s traffic signals). The conferences also process the signalling
associated with the traffic signals.
Functional versions The UCST R6A supports 2 x 4 functional units for the COBU<X> control
unit, each with its corresponding R4 and R5 template:
• COBUX 223
− ATM, SDH and PDH functionality
− PBUS capacity (signalling included):
40 highways each 2 Mbit/s equivalent to 40 x VC-12 or 1280 x 64
kbit/s
− UBUS capacity (signalling included):
2 x 4 highways each 2 Mbit/s equivalent to 8 x 31 x 64 kbit/s
− OBUX 213 supports additionally:
− SW download for remote units (via local units))
− Compressed MIB (storage and transfer)
• COBUX 219
128 highways each 2 Mbit/s equivalent to 128 x VC-12 or 4096 x
64 kbit/s
− SW download for remote units (via local units)
• COBUX 213
− SDH and PDH functionality

kbit/s
• COBUX 212
kbit/s
• COBUV 224
kbit/s
− Conference function
• COBUV 220
kbit/s
• COBUV 218
kbit/s

• COBUV 217
kbit/s
The list above shows only the features that are different between the three
types of the control unit.
The hardware versions provided for the COBU<X> differ in the
implementation of the interfaces for synchronisation signals. The COBU<X>
templates and hardware
- COBUX 219, 223 & 212, 213: ROFBU 367 103/1 R2B
R2C
- COBUV 220, 224 & 217, 218: ROFBU 367 103/2 R1A
R1B
or more recent hardware provide the interfaces for synchronisation as
specified in this document (i.e. 120 Ω impedance for ESI-1 and ESO-4 and
galvanic isolation for ESO-1 and 4).
Definition of terms In this document, the generic names
• FOX is used to name the following systems released with the UCST R6A:
− FOX 515
− FOX 512
• legacy FOX is used to name the following systems:
− FOX-U
− FOX-U/M (-U/E)
• COBU<X> is used to name the following control units and templates
released with the UCST R6A:
− COBUX 219 (R5)
− COBUX 223 (R5)
− COBUX 212 (R4)
− COBUX 213 (R4)
− COBUV 220 (R5)
− COBUV 224 (R5)
− COBUV 217 (R4)
− COBUV 218 (R4)
The FOX Manual [302] provide complementary information.
Front panel The front panel view below applies for all versions of the COBU<X>:

Figure 2: Front panel view of COBU<X> unit
Q1-unit interface module (C1.4)
D-Sub 9-pin male connector (C3.1)
for the F-interface
RJ-45 8-contact female connector (C2.1)
Optical Fault Indication
Unit LED
(bicolor red-green)
UA LED
(red)
Traffic LED
(red)
NA LED
(yellow)
...............
...............
...............
Fixing screw
Pull-out handle
Fixing screw
Pull-out handle
Identification (HW) label
DIN 41 612 connector type C,
2 x 32 contacts, male,
4 modules with coding
Alarm interface module (C1.2)
- 2 x 2048 kHz clock input
- (3 + 1) x 2048 kHz clock output
Q1-master interface module (C1.3)
Synchronisation interface module (C1.1)
for the QX-interface
Architectural description
The COBU<X> function is implemented using the following functional
blocks:
• CPU block with micro-controller, memory and peripheral logic
• Clock supply and synchronisation (PETS)
• Peripheral unit communication
• DXC and Highway Access
• NE Database
• Unit protection control
• OSPF Router (NE management communication)
• IS-IS Router (NE management communication)
• Metering Pulse Generator
• Diagnostics

• Management interfaces
− F-Interface
− QX-interface
− Q1-(slave) interface
− Q1-master interface
• Alarm interface
• COBUV only: Conference processing
For more information on the functions, also refer to the paragraphs
"Functional and operational description".

The figure below shows the functional block diagram of the COBU<X> unit:
Block diagram
Figure 3: Block diagram of COBU<X> unit
UBUS
PBUS
UBUS
IF
PBUS
IF
Highway Access
and
DXC
Peripheral Unit
Communication
Diagnostics
OSPF Router
1+1 Unit
Protection
control
Metering Pulse
Generator
Hardware Control
ICN
uC-LAN
Master/Slave control
Metering Pulses
Clock Supply
and
Synchronisation
(PETS)
Clock Signals for PBUS and UBUS
Clock Bus Lines 1, 2, 3, 4
ESI clock signals 2048 kHz (PETS & SETS)
ESO clock signals 2048 kHz (PETS & SETS)
Conference
processing
Alarm Interfaces
Q1-(slave)
interface
Qx-interface
NE Database
PCMCIA card
Qx
F
Q1-(slave)
Digital inputs
Relay contacts outputs
Q1-master
interface
Q1-master
CPU
Clock signals from SETS
F-interface
Conference processing block: COBUV only
Descriptions
CPU block The CPU functional block controls and monitors all the other functional
blocks of the COBU<X>. The local CPU executes the COBUX program and
provides all the COBU<X> internal functions.
Clock Supply and
Synchronisation
The most important part of the Clock Supply and Synchronisation
functional block is a phase locked loop (PLL) which allows the PETS system
of the NE to synchronise on one of the PETS timing sources.
The Clock Supply and Synchronisation functional block provides the NE
internal interfaces for the NE synchronisation to the PETS timing sources
(used in conjunction with the PLL) and to allow the distribution of the clock
signals within the NE.
The control units provide the interfaces for the external timing signals ESI-
PDH/SDH and ESO-PDH/SDH:
• Inputs:
− ESI-PDH: ESI-1 and 2
− ESI-SDH: ESI-1
• Outputs:
− ESO-PDH: ESO-1 … 3
− ESO-SDH: ESO-4

The Clock Supply and Synchronisation functional block provides toggle or
frequency detectors for the most important clock signals that are used for
clock recovery and distribution.
Intra Unit Communication The Peripheral Unit Communication functional block provides the
interfaces that allow the COBU<X> to manage the peripheral units of the NE.
This includes the interfaces for the management communication with the
units and the control signals to monitor and reset the unit hardware.
Highway Access and DXC The Highway Access and DXC functional block provides the COBU<X>
access to the UBUS and PBUS highways. The implementation of the
highway access interfaces allows you to insert and remove a slave control
unit without disturbing the traffic signals on the UBUS and PBUS.
Additionally, the Highway Access and DXC functional block provides the
digital cross connect that allows the cross connection of traffic signals
between:
• PBUS ↔ UBUS
• UBUS ↔ UBUS.
The Highway Access and DXC functional block also handles the access of
the management communication (ECC) and diagnostic function to the
PBUS.
NE Database The NE Database functional block holds the MIB of the NE. The MIB is
physically implemented on a PC memory Card and has an assigned partition
on the card.
With platform release R6, configuration information is transferred and stored
in compressed format making a more efficient use of space in the PC
memory Card and reducing transfer time
QX-interface The QX-interface functional block provides the
• Physical Medium Attachment (PMA) which attaches the NE to a 10
BaseT Ethernet LAN.
• Physical LAN Signalling (PLS) and the Media Access Control (MAC) as
required by the QX-interface.
F-/Q1-interface The F-interface Q1-(slave) interface functional block provides the:
• Universal asynchronous receiver/transmitter (UART) which handles the
data transmission over the F-interface and the Q1-(slave) interface.
• Transceivers which adapt the internal signals for RS-232 (F-interface)
and RS-485 (Q1-(slave) interface) transmission.
The F-interface Q1-(slave) interface share the same UART, thus it is only
possible to use one of the two interfaces at a time.
Q1-master interface The Q1-master interface functional block provides the:
• Universal asynchronous receiver/transmitter (UART) which handles the
data transmission over the Q1-master interface.
• Transceivers which adapt the internal signals of the Q1-master interface
for the RS-485 transmission.

The Q1-(master) interface doesn't share its hardware with other interfaces.
OSPF router The OSPF router functional block provides Version 2 OSPF routing
capabilities and the logical access to the internal PDH- and SDH ECC
management communication channels.
The OSPF router re-directs IP data packets for management communication
between the appropriate management interfaces (F-, QX-interfaces and a
number of PDH- and SDH-ECCs).
Alarm Interface The Alarm Interface functional block provides:
• 4 inputs which accept digital signals
• 2 outputs with change-over relay contacts
Metering Pulse Generator The Metering Pulse Generator functional block provides 12/16 kHz clock
signals and filters which create the required signal shape for the
corresponding metering pulses.
The Metering Pulse Generator feeds its signal to the FOX backplane.
Some of the units (e.g. SUBL<X>) switch this metering signal to their
subscriber line interfaces.
Other units (e.g. PHLC<x>) generate the metering pulses for their PSTN
interfaces locally, according to the metering information provided with the
signalling (CAS). However, they generate the local metering with the
frequency that is specified as a NE level parameter.
1+1 Unit Protection Control The 1+1 Unit Protection Control functional block provides software-
independent control circuits which recognise the active and the standby unit
and which control the switchover from the active to the standby unit.
Diagnostics The Diagnostics functional block provides a versatile pattern generator and
a test pattern analyser with interfaces to the Highway Access and DXC
functional block. The generator and analyser functions allow you to check
the traffic signal channels via the NE cross connect across the network.
Conference Processing
(COBUV only)
The Conference Processing functional block processes the traffic signal
data and the corresponding signalling information for conference circuits
between the traffic signals.
Only the COBUV unit provides the Conference Processing functional
block.

Functional description
The COBU<X> unit provides functions and processes, which affect the
services and operation of the NE.
Depending on the function or process the UCST provides the corresponding
menus and dialogues for their control on the NE or the unit level:
• Configuration and control on the NE level
− Synchronisation (PETS, ESI, ESO)
(NE Configuration → NE Timing Source)
The NE provides the corresponding alarms on the unit level!
− Implementation of redundant control unit
(NE Configuration → Add Protecting unit(s))
− Software Installation
(NE Configuration → Software Installation)
− Metering Pulses
(NE Configuration → Parameters)
− Inventory information retrieval
− Management Network
(Management Network → Set-up)
For the description of the configuration and (if applicable) operation of
these functions, refer to [302] and [401].
This document provides for these items additional functional and
operational descriptions on the unit level.
• Configuration and control on the COBU<X> unit level
− Communication IF
(Unit Configuration → Parameters)
− Management communication
(Unit Configuration → Parameters)
− Operation control for redundant control units
(Unit Configuration → Status/Maintenance)
− Conference function (COBUV only)
(Unit Configuration →Parameters)
− PETS and ESI, ESO alarms (alarms only!)
(Unit Configuration →Parameters)
For the description of the configuration and operation of these functions,
refer to the corresponding paragraphs in this document.
The documents [401] and [302] provide detailed information on the local
management access to the NE.
The document [901] provide detailed information on the configuration of
the Management Communication Network (MCN) with the FOX and on
the techniques of MCN implementation.
The paragraphs below provide functional and operational descriptions as
stated above and for the functions and processes that are not configurable.

Clock supply &
synchronisation PDH
domain (PETS)
Timing sources and signals It is possible to configure the PETS system of the NE to synchronise to one
of the following timing sources:
• External 2048 kHz timing signals according ITU-T G.703
The PETS system uses the inputs (timing sources):
− ESI-1 (PDH and SDH)
− ESI-2 (PDH)
• Traffic signals 2048 kbit/s
The NE terminates or monitors the incoming (received) logical 2048 kbit/s
traffic signal according to ITU-T G.704. The traffic units extract the timing
and quality information from the incoming traffic signal and supply a
corresponding clock signal and the quality information (if applicable) to
the COBU<X>.
• Traffic signals n x 64 kbit/s
The incoming (received) traffic signal is a n x 64 kbit/s signal. The traffic
units extract the timing information from the incoming traffic signal and
supply a corresponding clock signal to the COBU<X>.
• Internal source
The COBU<X> (i.e. the entire system) synchronises to the timing signal
of the internal source.
Timing signal outputs The PETS system of the COBU<X> can provide timing signals via
corresponding interfaces and traffic interfaces that allow you to synchronise
other equipment to the PETS system of the NE:
• Timing signals for external equipment
The COBU<X> provides 3 interfaces according to ITU-T G.703, section
10 - 75 Ω case for 2048 kHz clock signals:
− ESO-1 (PDH)
− ESO-2 (PDH)
− ESO-3 (PDH)
It is possible to configure for each of the outputs whether it shall provide
its timing signal or not depending on the selected timing source. This
helps to prevent undefined synchronisation states such as
synchronisation loops in complex network structures.
• Structured 2 Mbit/s traffic signals (outgoing)
It is vital for meshed networks to avoid undefined synchronisation states
such as synchronisation loops. To control the use of the traffic signals for
synchronisation purposes it is possible to insert corresponding
information in the TS0 spare bits. The TS0 carries SSI or SSM data to
signal the neighbouring NEs the disposability of the timing information in
the traffic signal.
For additional information, refer to „Synchronisation Distribution“ in [302].
The SETS system of the NE provides its ESO timing signal via the
COBU<X> unit to external equipment. The COBU<X> does not process this
signal but provides just the signal interface.

The central system clock supply and synchronisation for the PETS system is
a system function. It relies on a PLL that delivers a 32768 kHz reference
clock signal at the output of its VCXO (Voltage Controlled Crystal Oscillator).
The PLL's phase detector operates at a frequency of 256 kHz.
PLL and clock signals
Most of the NE internal PDH clock and frame synchronisation signals are
derived from the VCXO reference clock:
− 4096 kHz UBUS clock signals
− 8 kHz UBUS frame synchronisation signals
− 16384 kHz PBUS clock signal
− 2 kHz PBUS frame synchronisation signal
With terminated 2 Mbit/s traffic signals, the FOX operates internally in clock
and frame synchronism for both the transmit and the receive direction.
The figure below shows the block diagram of the PETS system clock supply
and synchronisation:
Figure 4: COBU<X> PDH clock supply and synchronisation
block diagram
MUX
6 : 1
Signal
Monitoring
PDH-4 clock source
PDH-3 clock source
PDH-2 clock source
PDH-1 clock source
ESI-1 (2048 kHz signal input)
CPU
MUX
2 : 1
Clock
Signals
Metering
Pulses
ESI-1 (2048kHz signal input)
for the SETS system
to UBUS, PBUS and SBUS
PETS locked Synchronisation
Outputs:
ESO-1 ... 3 (2048 kHz signals)
Meter Pulse
Generator
Internal
Divider
Divider
PLL
ESI-2 (2048 kHz signal input)
The figure shows only the PETS (PDH domain) aspect of the NE
synchronisation.
For information on the SETS system and the interoperability
between SETS and PETS, refer to [302].
The 2 external ESI-1, ESI-2 interfaces (2048 kHz clock signals according
ITU-T G.703) and 4 internal PDH-1 … 3 clock bus lines with the clock
information extracted from incoming traffic signals provide clock signals of
the allocated timing sources. The signal frequency on the internal bus lines
is 256 kHz.
The configuration of the PETS system via the NE Timing sources menu
defines the allocation of the traffic unit interfaces to one of the internal clock

bus lines. The traffic unit interface supplies its clock signal as long as the
received traffic signal satisfies the quality requirements.
If the traffic signal does not satisfy the quality requirements for timing
sources, the traffic unit disconnects the interface from the clock bus line. The
timing Signal Monitoring circuit of the COBU<X> detects the absence of the
corresponding clock signal. This forces the PETS system to select a new
timing source according the configured selection algorithm (priority table
based or quality level based).
The Signal Monitoring circuit monitors the presence or absence of timing
signals as follows:
− ESI-1, ESI-2: by means of signal frequency detectors
− PDH-1 … 4 : by means of signal toggle detectors
Failed timing sources create alarms.
For more information and the configuration of this selection process, refer to
[302].
Modes The FOX runs in one of two basic modes of synchronisation:
• Free-running:
The COBU<X> (i.e. the entire system) synchronises to the timing signal
of the internal source. The NE oscillates freely with respect to the traffic
signals and external timing sources.
This synchronisation mode corresponds to the timing source selection
„Internal“ source.
• Locked:
The COBU<X> (i.e. the entire system) synchronises to one of the six
timing sources (ESI-1, ESI-2, PDH-1 … 4).
The synchronisation mode is Locked if the PETS system is synchronised
to the timing source according to the timing source selection <Source
Name> (as allocated to the PDH-1 … 4 clock bus lines), ESI-1 and ESI-
2.
Jitter transfer function In the „locked“ mode, the PLL generates a timing signal that follows the
frequency of the timing source. The jitter transfer function of the PLL defines
how the jitter in the timing source signal influences the jitter at the output of
the PLL.
The PLL can operate alternatively with one of two predefined jitter transfer
functions that provide the following characteristics:
• Type „wide band“ (PLL quality factor low Q)
If you select the clock extraction mode „Low Q" for the PETS system in
the Timing sources dialogue the jitter transfer function is of type „wide
band“ (low PLL quality factor Q).
The corresponding filter features a low Q, wide band filter with a cut off
frequency of 40 Hz (attenuating jitter above 40 Hz).
This filter is used for normal applications and public networks. The
requirement for the jitter transfer of 2 Mbit/s (G.703) signals is specified
by G.736.
This is the most commonly used setting.

• Type „narrow band“ (PLL quality factor high Q)
If you select the clock extraction mode „High Q“ for the PETS system in
the Timing sources dialogue the jitter transfer function is of type „narrow
band“ (high PLL quality factor Q).
This filter is used for ONP (Open Network Provision) applications. To
avoid potential synchronisation problems (slips) in the public PDH
transmission network due to synchronisation processes in the private
networks, ONP specifies additional jitter filtering for frequencies below 40
Hz.
As the ONP setting of the filter (high Q) results in a slower reacting PLL,
the high-Q filter is only recommended at the nodes connecting to the
public network, and when required by the public network operator.
Figure 5: Timing sources sample dialogue
UCST
ABB
Intra unit communication
Overview The COBU<X> controls the communication between the control unit and the
peripheral units in the subrack.
From the perspective of intra unit management communication, there exist 3
categories of peripheral units:
• Units with CPU for FOX and legacy FOX
• PBUS and ABUS/SBUS units (always have a CPU)
• Units without CPU (FOX and legacy FOX)
The table below shows what communication structure the COBU<X> uses
with which category of peripheral unit:

Figure 6: Communication structures vs. unit category
Units µC-LAN ICN Hardware Control
with CPU for FOX
& legacy FOX
X X
PBUS, ABUS/SBUS units
exclusive for FOX
X X
without CPU for FOX
& legacy FOX
X
Hardware control The Hardware Control controls the peripheral unit at the „hardware“ level
(i.e. independently of the units SW system and its state). The Hardware
Control of the COBU<X> supports the following functions:
• Check the presence of the peripheral unit
• Activate/deactivate the unit (UBUS, PBUS and ABUS/SBUS units)
• Reset the unit (UBUS, PBUS and ABUS/SBUS units)
• Turn On/Off the unit LED (UBUS, PBUS and ABUS/SBUS units)
• Read the unit alarm status (Units without CPU only)
• Read the unit Inventory Data
The Hardware Control enables the COBU<X> to control a peripheral unit
independently of whether the peripheral unit is properly working or not. This
allows the COBU<X> e.g. to deactivate a faulty peripheral unit and prevent
this unit from further bus accesses, which might disturb the bus systems on
the backplane and traffic signals.
The COBU<X> uses individual address lines to select and control each of
the slots and thus peripheral units.
µC-LAN The µC-LAN (micro-Controller Local Area Network) provides NE internal
management communication and allows the COBU<X> to manage the
following functions of units with a CPU if the units are compatible with the
FOX and legacy FOX:
• Peripheral unit configuration and fault management
− Configuration of the peripheral units
− Monitoring of the peripheral units
− Collection of the peripheral units alarms
− Software installation on peripheral and remote units
• Broadcasting of operational parameters
(COBU<X> → peripheral unit)
− Time and date information
− Synchronisation source that currently synchronises the system
− Metering pulse synchronisation message
− etc.
The µC-LAN uses a proprietary protocol stack. The physical layer of this
stack relies on asynchronous serial communication at the speed of
375 kbit/s. The communication is based on a master-slave principle where
the COBU<X> unit is always the master of the µC-LAN.

The ICN (Internal Communication Network) provides NE internal
management communication and allows the COBU<X> to manage the
following functions of units with a CPU if the units are not compatible with
the legacy FOX:
ICN
• Peripheral unit configuration and fault management
− Configuration of the peripheral units
− Monitoring of the peripheral units
− Collection of the peripheral units alarms
− Software installation on peripheral and remote units
• Broadcasting of operational parameters
− COBU<X> → peripheral unit
− Time and date information
− Synchronisation source that currently synchronises the system
− Metering pulse synchronisation message
− Communication of the quality level of allocated synchronisation
sources
− etc.
• Exchange of data between redundant control units
Exchange or update of configuration data and fault management
information from one COBU<X> to the other unit:
− Configuration information to allow the COBU<X> to update its MIB
and to achieve MIB redundancy
− Status and alarm information
• Peripheral unit to peripheral unit communication
The communication of the ICN uses a proprietary protocol stack. The lower
layers of the stack rely on an HDLC synchronous bus with a speed of about
2 Mbit/s. The communication of the ICN is based on a multi-master principle.
NE MIB / PC memory card The NE configuration data and the ESW (Embedded SW) for the units
implemented in the NE make up the MIB (Management Information Base) of
the NE. The COBU<X> saves this data on the PC Memory Card of the
control unit.
The PC Flash card stores the data as follows:
• Configuration data of the NE.
The COBU<X> reserves 1.5 MBytes of the PC memory card for
configuration data.
• Application Download Software (APDSW)
The APDSW file(s) allow the COBU<X> to decompress and install the
ESW on the units.
• Files with compressed software code for the control unit and the other
peripheral units that support software download.
The COBU<X> reserves the remaining capacity of the PC memory card
for ESW and the APDSW (e.g. 6.5 MBytes for an 8 MByte PC memory
card).
From release R6, configuration information is transferred and stored in
compressed format. The main benefits of this are:
− It makes a more efficient use of space in the PC memory Card
− It reduces transfer time (specially significant in ESW transfers)

The PC memory card is a solid-state non-volatile storage media. The PC
memory card of the COBU<X> provides a total memory capacity of
8 MBytes to satisfy all the possible NE configurations. However, if higher
capacity is required a 16Mbytes card can be used.
Please note that:
• For proper operation, you must only use the PC memory card
type delivered with the COBU<X> e.g.:
− Intel Value Series 100, iMC008FLSC
− M-Systems, LDPC-FD - 08
• The COBU<X> supports only Type 1 form factor.
The PC memory card is an integral part of the control unit!
A COBU<X> without PC memory card is not operating (unit
failure). The NE signals this state via a steady active unit LED of
the control unit.
Although generally not recommended, it is possible to move the PC memory
card from one control unit to another control unit of the same type.
For instructions on how to do this, refer to [302] and the instructions for the
handling of the PC memory card at the end of this document.
Do not try to copy files to or remove files from the PC memory
card via file service functions of your PC or programs other than
the UCST!
Unpredictable system behaviour might result because of
inappropriate organisation or content.
Cross connect
Principles The cross connect circuit of the COBU<X> provides at the same time 2
functions:
• UBUS ↔ UBUS cross connections
Central logical cross connect for the UBUS.
From the point of view of the UBUS architecture, the COBU<X> provides
a central cross connect as it is required for the operation of the UBUS
units in the FOX.
• UBUS ↔ PBUS bridge
Distributed PBUS cross connect.
From the point of view of the PBUS architecture, the UBUS is now a
tributary to the PBUS and in that sense, the cross connect is now a part
of the decentralised PBUS cross connect of the FOX.
Therefore, any UBUS ↔ UBUS cross connection is established indirectly
over two levels (i.e. UBUS → PBUS → UBUS). This two level connection
demonstrates that the UBUS ↔ PBUS bridge is the first step of any UBUS
↔ UBUS cross connection.
The COBU<X> provides an additional access to the PBUS cross connect
that is reserved for the diagnostic function, the ECC management
communication channels, the digital conference (COBUV only) and other

internal purposes. This PBUS access does not contribute to the specified
PBUS capacity.
Capacities The COBU<X> has the following traffic handling capacity for UBUS traffic
signals:
• In the direction UBUS → PBUS,
The COBU<X> unit can provide user traffic up to a capacity of 248 x
64kbit/s (with or without CAS).
• In the direction PBUS → UBUS,
The PBUS cross connect provides traffic signals for the UBUS. The
COBU<X> can pick individual timeslots carrying user traffic up to a total
capacity of 248 x 64kbit/s (with or without CAS) from all the PBUS lines
available.
Please note that:
• As soon as you add a UBUS unit, the PBUS provides capacity
to carry the UBUS traffic.
• In contrast to the legacy FOX, it is not possible to double the
above mentioned user traffic capacity if you disable the CAS for
the UBUS traffic in the FOX.
Signal toggle detectors monitor the UBUS clock signals, the PBUS clock
signal and the PBUS data signals. If a clock or data signal fails, the fault
management system generates a corresponding alarm.
For additional information on these alarms, refer to the corresponding
paragraphs in the section "Alarms and Notifications".
1+1 equipment protection The 1+1 control unit protection relies on 2 COBU<X> with identical MIB and
hot standby of the inactive unit.
The active unit controls the NE and the management communication. The
inactive unit permanently updates its MIB and remains in hot standby mode.
For operational topics, refer to the corresponding paragraphs in the section
"Operation".
The implementation of redundant control units requires special
considerations for the cabling of the COBU<X> interfaces. For information
on the cabling, refer to [302] or [303].
Metering pulse generator The configuration of the metering pulses parameters (selection of the
metering pulse frequency, pulse duration and break duration) is an NE level
function.
You can access the corresponding dialogue via NE Configuration →
Parameters.
For details, refer to [302].
Diagnostic function The COBU<X> control units provide a versatile diagnostic function for the
analysis of the traffic channels performance. The diagnostic function allows

you to test transmission channels before the commissioning of payload
traffic and for maintenance purposes.
The test function is implemented by means of a pattern generator and a
pattern analyser which each access the channel under test from one end.
Both of the functions (the pattern generator and analyser) are implemented
on the control unit.
To test a channel you set up a uni- or bi-directional transmission path in the
network between the access point of the generator and analyser
respectively. If this channel uses the same interfaces and resources in the
network as your traffic signal, the test result accurately reflects the
performance of the traffic channel.
The access points to the traffic channel under test can be:
• on the same COBU<X> unit
• on 2 different COBU<X> units
• on the COBU<X> unit and an external measurement equipment
(providing it is compatible with the test signal and the testing method).
Due to standardised test signals, most external generators and analysers
can be used in conjunction with the complementary function of the
COBU<X> board.
The test signal is cross connected via a separate PBUS line between the
generator and/or the analyser of COBU<X> and the physical interface of the
NE to the network. The diagnostic function does not reduce the PBUS
capacity available for traffic signals.
The following figure illustrates the principles of traffic channel diagnostics:

Figure 7: Principles of traffic channel diagnostics
FOX Any NE
Transmission Network
COBUX
COBUV
PI PI
FOX
Transmission Network
COBUX
COBUV
PI
FOX
COBUX
COBUV
PI
Symbols and abbreviations:
PI:
Pattern Generator
Pattern Analyser
Physical Interface
Cross Connect
For information on the configuration and application of the diagnostic
function, refer to the corresponding paragraphs in the sections
"Configuration" and "Operation".
Conference function
(COBUV only)
The COBUV control unit provides conference functions for 64 kbit/s traffic
signals. These signals mostly represent digitised voice signals. The
conference function also processes the signalling information accompanying
the traffic signals.
The cross connect allows you to create uni-directional and bi-directional
conference parties.
Each conference party consists of an analogue and a digital conference.
Analogue Conference For each participant the Analogue Conference circuit sums the contribution
of all the other participants (except of the participants own contribution) and
sends this signal back to the participants. However, with ordinary telephone
sets each participant hears its signal via the signal feedback provided in the
handset.
It is possible to specify per participant the following parameters:
• Attenuation for the traffic signal
− fed to the analogue conference circuit:
0 dB … 9 dB in steps of 3 dB
− received from the analogue conference circuit:
0 dB, 3 dB

• Noise suppression for the traffic signal
Noise suppression in 3 steps (5th
, 9th
and 16th
step) or no noise
suppression. The steps of noise suppression are specified as follows:
− 5th
: Least noise suppression.
The "idle signal" pattern replaces the first 5 positive and negative
PCM codes generated during conversion of the traffic signal.
− 9th
:
PCM codes generated during conversion of the traffic signal.
− 16th
: Most noise suppression.
PCM codes generated during signal conversion of the traffic signal.
Digital Conference
(signalling)
The Digital Conference performs a logical AND function between the
signalling bits provided by all the participants of the conference.
For this purpose, the Digital Conference circuit processes the signalling
provided from and fed to the participants as follows:
• The Digital Conference circuit applies a bit wise AND function to the
signalling patterns received with the traffic signals from the participants of
the conference party.
• This newly created signalling pattern is sent together with the traffic
signal to all participants of the conference party.
Figure 8: Example of a conference party with 3 participants
+
x
Analogue Conference
Digital Conference
voice
sig.
voice
sig.
voice
sig.
A
B
C
Subscriber
Subscriber
Subscriber
A(t)
B(t) + C(t)
B(t)
A(t) + C(t)
C
(
t
)
A
(
t
)
+
B
(
t
)
SA(t) x SB(t) x SC(t)
SA(t)
S
A (t) x S
B (t) x S
C (t)
SC(t)
SB
(t)
SA
(t) x SB
(t) x SC
(t)
You can assign up to 64 participants to up to 21 conferences. To maintain a
reasonable signal-to-noise ratio in the conference it is recommended that
you assign not more than 8 participants to one conference.

If one of the channels connected to a conference is faulty (channel gives an
AIS signal), its input signal is automatically replaced by the "idle signal". This
prevents the other channels in the conference from being disturbed. The
faulty participant receives an AIS signal.
Example The conference function of the COBUV allows you to set up conferences
where for example the idle subscribers of the conference receive a ringing
signal if one of the participants goes off-hook (like phone-phone mode with
e.g. the SUBL<X>).
You must define appropriate signalling patterns for the different states of the
participants to create the required resulting pattern with the AND function.
The table below shows the signalling bits for a conference party with 3
participants. Each participants has the following settings:
• Phone-Phone mode with 4-second or ground key ringing
• Signalling bits towards Exchange :
− On-hook = 0111
− Off-hook = 0011
− Ground = 0001
Figure 9: Example for the signalling in a conference with 3 participants
Time State Subscriber A Subscriber B Subscriber C
↓ Sig. towards
Exchange
a b c d
Sig. from
Exchange
a b c d
Sig. towards
Exchange
Sig. from
Exchange
Sig. towards
Exchange
Sig. from
Exchange
t1
Idle On-hook 0111
(On-hook)
0111 0111
(On-hook)
0111 0111
(On-hook)
0111
t2
Subs. A seizes
the line
0011
(Off-hook)
0011 0111
(On-hook)
0011 0111
(On-hook)
0011
t3
Subs. A rings
up all parties
0001
(Ground)
0001 0111
(On-hook)
0001
(Ringing)
0111
(On-hook)
0001
(Ringing)
t4
Subs. B first
answers
0001
(Ground)
0001 0011
(Off-hook)
0001
(Ringing)
0111
(On-hook)
0001
(Ringing)
t5
Subs. C last
answers
0011
(Off-hook)
0011 0011
(Off-hook)
0011 0011
(Off-hook)
0011
For information on the configuration and application of the diagnostic
function, refer to the corresponding paragraphs in the sections
"Configuration" and "Operation".
NE management and
control
The NE Management/Control is an important system function that includes
all types of unit. Depending on the function, each unit of the NE physically
contributes to the management functions (inventory management,
configuration management, software management, fault management and
performance monitoring).
The COBU<X> control unit has particular functions for the management of
the NE and the management communication:
• Loading the NE configuration and making the configuration effective in
the whole NE (configuration management)

• Installation of delivered NE software on the peripheral units (software
management)
• Monitoring of all the COBU<X> unit functions, collection and classification
of the failures and creation of triggers for consequent actions (fault
management)
• Management of the NE configuration database and NE software
database (NE MIB management). Although important, this function is an
auxiliary function of the configuration and software management
functions.
• Management communication with the outside world to allow operation
and maintenance of the NE, i.e. support of all the provided management
functions.
The COBU<X> does not directly monitor the traffic functions of the other
units.
Handling of configuration data The COBU<X> executes and controls the following processes for the
Configuration Download:
1) Download of configuration Data
The control unit receives the *.cfg file (via FTP session) from the EM
and stores the data on its PC memory card.
2) Update of the NE MIB
The control unit updates its NE MIB, i.e. updates the files on the PC
memory card in the directories, which are related to the slots and the
NE.
3) Update of the unit configuration
The control unit updates the peripheral units according to the new
configuration data (configuration changes).
4) Creation of new Upload.cfg file
The control unit prepares a new (Upload.cfg) file for a possible upload
to the EM on its PC memory card.
Software Management The COBU<X> executes and controls the following processes for the
Software Download:
1) Software Delivery
The software delivery adds new software (function controlled via the
Software Delivery dialogue). The control unit receives the compressed
software files (via FTP session) from the EM and stores them on its
PC memory card.
2) Configuration Download
The download provides configuration data for the Software Installation
on the units with ESW. The control unit receives the *.cfg file (via FTP
session) from the EM and stores the data on its PC memory card.

3) Update of the NE MIB
The control unit updates its NE MIB, i.e. updates the files on the PC
memory card in the directories, which are related to the slots and the
NE.
4) Software Installation
The control unit installs the ESW according to the configuration data
on the peripheral units: The control unit transfers the compressed
software files to the peripheral units. Each peripheral unit then
decompresses the software file and installs the program code on its
program memory.
5) Creation of new Upload.cfg file
The control unit prepares a new (Upload.cfg) file for a possible upload
to the EM on its PC memory card.
Practically, the Configuration Download is a function that provides
at the same time the parameters for the unit configuration and the
parameters for the Software Installation on the units with ESW.
Fault Management The control unit contributes to the NE fault management with the following
processes and functions:
• Control/monitoring (collection of failures) for peripheral units with
defined configuration and compatible HW and SW for units
− Compatible with the FOX and legacy FOX:
The control unit polls each unit via the µC-LAN for unit status changes
(master-slave principle). The polling period is 100 ms. If the status
changes, the control unit requests detailed information.
If there is no reply or the answer is erroneous, the control unit controls
the unit via the Hardware Control interface.
− Not compatible with the legacy FOX:
The units communicate their unit status changes autonomously via
ICN to the control unit. If the status changes on a peripheral unit, the
control unit requests detailed information.
Additionally the control unit polls each peripheral unit for failures and
changes. The polling period is 2 s. This polling process allows a quick
detection of failures or changes of the subrack provisioning (e.g.
removed units).
If there is no reply or the answer is erroneous, the control unit controls
the unit via the Hardware Control interface.
− Units without CPU:
The control unit polls each unit via the Hardware Control interface.
The polling period is 100 ms.
With the polling the control unit reads the alarm status directly.
• Control/monitoring for peripheral units with undefined configuration
(no data registered in the NE MIB) or incompatible HW and SW:
The control unit polls the slots in the NE subrack without configured
peripheral units via the Hardware Control interface. The polling period is
2 s. Thus, the control unit detects missing or inserted units, but not
configured units.

However, it is still possible to read the unit inventory data for all units
inserted in the subrack. For more information on the inventory
management, refer to [401].
• Logbook
The NE logbook is created in the volatile memory of the control unit. The
control unit collects the last 256 alarm status changes
(activation/deactivation) and NE notifications together with the
corresponding time/date and stores this information in the logbook.
If the control unit powers off or restarts, the content of the logbook is lost.
For more information on the logbook, refer to [401].
• Classification of failures and NE fault list
Depending on the severity defined for each NE fault cause, the control
unit creates an Urgent Alarm, a Non-urgent Alarm or just an entry to the
logbook. The NE fault list is a summary of the pending fault causes and
indicates the NE alarm state.
The NE fault list is permanently updated.
The control unit updates the optical fault indication and the state of the
alarm outputs. For more information on the fault indication and the fault
list, refer to [302] and [401].
• Monitoring of the 5 VDC supply
A dedicated monitor circuit permanently monitors the internal 5 V power
supply of the control unit for drop of the supply voltage. If the voltage
drops below 4.75 V, the control unit is reset. This mechanism avoids loss
of data and maintains data integrity even if the system voltage drops are
spurious.
This reset causes the NE to restart autonomously after the 5 V supply
has recovered properly (cold start).
All traffic services of the NE are down until the control unit has recovered
its „active“ operating state.
• Monitoring of the control unit software
A watchdog circuit permanently monitors the processing of the control
unit software for failures. If the watchdog detects a software execution
failure, the control unit is reset.
This reset causes the NE to restart autonomously. The watchdog reset
does not affect the traffic services provided by the NE.

The control unit provides the following external and internal interfaces for
management communication:
Interfaces for management
communication
• QX-interface
• F-interface
• Q1-(slave) interface
• Q1-master interface
• Internal access for
− PDH ECC
− SDH ECC
− ECC over ATM
For more information on "Management Communication", refer to
additional documents as follows:
• [401] provides detailed descriptions of the generic aspects of
the installation and the use of the UCST. These descriptions
include the following topics and functions:
− Installation of the UCST
− Commissioning your PC/computer for management
communication
− Getting Started with UCST
− UCST System Administration
− Management Access to NEs
− Basic Configuration
− Configuring Units
− Cross Connections & Bus Usage
− Synchronisation
− UCST File and Data Services
− Maintenance and Diagnostic Functions
(The items represented with bold letters in the list above
contribute in particular to the UG COBU<X>).
• [901] provides detailed descriptions for the implementation of
MCN. These descriptions include the following topics:
− Implementation of FOX MCN with ECC
− OSPF Routing (FOX aspects)
− OSI routing (FOX aspects)
− Examples
− Maintenance and Diagnostic Functions
• [914] provides detailed descriptions for the implementation of
FOX MCN with the legacy EOC.
• [301] and [303] provide detailed descriptions for the cabling of the
management interfaces with redundant control units.
QX-interface: The QX-interface allows you to connect the FOX to an Ethernet LAN. The
UCST or UNEM can access each individual NE via its QX-interface and the
LAN.
The QX-interface supports „local“ LAN connections and „remote“ LAN
connections. This means that the client (i.e. the UCST or UNEM) can reside
in a different IP subnetwork to the server (i.e. the FOX).
Since the QX-interface is a router interface, it is possible to access the ECC
network via the QX-interface.

F-interface: The F-interface allows you to connect the FOX to the PC that runs the UCST
or to the WS that runs the UNEM software. The connection is possible either
directly between the PC/computer and the equipment or via PSTN.
The F-interface also allows remote access to a LAN/WAN and/or ECC
based management network. ECC based management access is possible
since the F-interface is a host interface of the router.
The direct ECC network access via the F-interface is provided only
if you use the DUN connection type UCST RAS direct on F to
establish the required route in the PC or WS towards the ECC
network.
The F-interface provides the following possibilities for management
communication:
• Local (direct):
The host PC or WS is directly connected via its serial interface to the
FOX (via the null-modem cable as described in the paragraphs
"Installation"), i.e. the host is at the same location as the FOX.
• Remote via modem:
The host PC or WS is connected via the PSTN and modems to the FOX
(via the modem cable as described in the paragraphs "Installation"), i.e.
the host is remote with respect to the FOX location.
• Remote via ATU:
The host PC or WS is connected remotely to the FOX via the ATU. For
more information on this access, refer to the corresponding application
note.
• Remote via legacy EOC network:
The host PC or WS is connected via the legacy EOC network (based on
the SIFOX unit) to the FOX.
For information on the implementation of the legacy EOC and the
required cables for the SIFOX unit, refer to [914]. The paragraph
"Installation" provides the description of the adapter cable for the F-
interface of the COBU<X>.
Please note that
• it is not possible to subtend the EOC access via the PSTN for
the FOX.
• the EOC is the management communication network for legacy
FOX with a slow throughput (9600 kbit/s) and thus not suited for
the FOX MCN.
Q1-(slave) interface: The Q1-(slave) interface of the NEs connects to the local Q-bus which links
the Q1-(slave) interfaces directly to the UCST (UNEM). The UCST (UNEM)
is the master on the bus and controls the communication.
Please note that it is not possible to access the ECC network via
the Q1-(slave) interface.
The Q1-(slave) interface of the COBU<X> provides the following possibilities
for management communication:

• Local:
The UCST (UNEM) is locally connected via its serial interface to the Q-
bus as described in [901], i.e. the master UCST (UNEM) is at the same
location as FOX.
• Remote:
It is not possible for the UCST (UNEM) to access a FOX that has its Q1-
(slave) interface of its COBU<X> connected to a remote Q-bus via
modem or similar devices.
For detailed information on the possibilities of management access, refer
to [401].
Q1-master interface: The COBU<X> provides in addition to the Q1-(slave) interface the Q1-master
interface.
The Q1-master interface allows the FOX to provide the Q-bus interface of the
UCST (UNEM) for a remote Q-bus. The Q1-master interface of the FOX
drives the management communication on the local Q-bus for legacy FOX
and DSL Systems equipment.
It is not possible to subtend the Q1-(slave) interface of the FOX via the Q1-
master interface.
PDH ECC The PDH ECC interfaces are internal interfaces of the COBU<X> that allow
you to connect the router interfaces of the COBU<X> to the PDH ECC
network.
The traffic handling capacity of the COBU<X>'s PDH ECC interface is as
follows:
• The OSPF router of the COBU<X> provides 32 internal interfaces for the
PDH ECC network.
This allows you to create up to 32 PDH ECCs per COBU<X>.
• The maximum bandwidth that you can allocate to all the PDH ECC
interfaces of a COBU<X> is 2048 kbit/s.
You can assign:
− n x 64 kbit/s up to 31 x 64 kbit/s (corresponding to 1984 kbit/s) per
PDH ECC transported via an E1 signal.
− 16 kbit/s in the TS0 of an E1 signal connected to a PDH ECC port.
Transmission of the ECC via TS0 uses no traffic signal bandwidth and
requires a LOMIF type 2 Mbit/s interface (2 Mbit/s mode set to
‘terminated’, Sa Mode set to ‘ECC’).
SDH ECC The SDH ECC interfaces are internal interfaces that allow you to connect the
router interfaces of the COBU<X> to the SDH ECC network.
The traffic handling capacity of the COBU<X>'s SDH ECC interface is as
follows:
• The OSPF router of the COBU<X> provides up to 8 internal interfaces
towards the SDH ECC network.
This allows you to create up to 8 SDH ECCs per COBU<X>.
• The maximum bandwidth that you can allocate to all the SDH ECC
interfaces of a COBU<X> is 2048 kbit/s.

You can assign:
− 192 kbit/s (= 3 x 64 kbit/s) for the bytes D1 … D3 of the SDH overhead
channel connected to an SDH ECC port or
− 576 kbit/s (= 9 x 64 kbit/s) for the bytes D4 … D12 of the SDH
overhead channel connected to an SDH ECC port.
ECC over ATM The ATM ECC interfaces are internal interfaces that allow you to connect the
router interfaces of the COBU<X> to the ATM network.
ECC over ATM links must be cross connected to the COBU<X> unit via
PDH ECC links and the ATM part is done automatically provided that the
ATM port, VPI/VCI and bandwidth are defined.
The ECC traffic handling capacity of the different ATM units interfaces are as
follows:
• ATIOP provides two ECC interfaces per port.
• ACONV provides two ECC interfaces for each of its 14 IMA groups.
• Each ATM ECC link can support one of the following predefined
bandwidth capacities:
− 64 Kbit/s
− 192 Kbit/s
− 576 Kbit/s
• ECC over ATM is treated as CBR (Constant Bit Rate) traffic in order to
ensure the best throughput.
Bandwidth for the allocation
of PDH and SDH ECCs
It is not possible to allocate PDH and SDH ECCs independently from each
other. The bandwidth resource for ECCs applies at the same time for the
allocation of SDH and PDH ECCs:
The maximum bandwidth for all the PDH and SDH ECCs is 2048 kbit/s.
Alarm Interfaces
Alarm state outputs The outputs for the electrical indication of the NE alarm state are solid-state
„change-over relay contacts“:
• One output indicates the NE alarm status Urgent Alarm (UA)
• The other the alarm status Non-urgent Alarm (NA).
The 2 alarm outputs are permanently driven and are an active part of the NE
fault management. Two LED indicators on the COBU<X> front panel
indicate the 2 UA and NA NE alarm status optically.
Please note that:
• The NE alarm status is exclusive. This means that the NE has either
the UA or the NA alarm state at a time (or has no alarm at all).
• For equipment without power (e.g. after a power fail) the Urgent
Alarm output is active and the Non-urgent Alarm output is not active.
For more information on the fault management system of the FOX, refer to
[302].
Depending on the requirements of the external equipment, you can select
between 2 types of active alarm contacts:
• Active Open (AO)

• Active Closed (AC)
The functional diagram below shows the internal wiring for the alarm state
relays:
Figure 10: Internal wiring of the alarm state relays
COBU<X>
UA
NA
UA_AO
UA_AC
UA_COM
NA_AO
NA_COM
NA_AC
The diagram above shows the NE alarm state for power fail:
• The Urgent Alarm output is active
• The Non-urgent Alarm output is not active.
For information on the cabling of the alarm interfaces with protected control
units, refer depending on your FOX to [301] or [303].
Inputs for external alarm
signals
The COBU<X> provides inputs for 4 external alarm signals that you can
integrate into the NE fault management:
It is possible for each of the 4 alarm inputs to:
• enable or disabled the input
• configure the active signal level for the input to:
− active ground
− active open
The default setting is active ground.
You can assign a name to each external alarm (input). If you assign a name
the UCST (UNEM) uses this name for the alarm description in the fault
management.
For the details on the configuration, refer to the corresponding paragraphs in
"Configuration".
The functional diagram below shows the internal wiring for the inputs for
external alarm signals:

Figure 11: Internal wiring of the alarm inputs
External
Alarm <x>
Contact
+5V
-UTF
COBU<X>
1)
Input <x>
1) You should connect the alarm signal ground to the appropriate pin of
the alarm interface module on the front connector.
However, it is possible to omit this connection in low noise
environment and if there are low potential differences between the NE
and the equipment, that provides the alarm signal.
For a reliable operation, the external alarm contact (includes the external
wiring!) has to meet the following specifications:
1) Open contact: Leakage current ≤ 800 µA at +16 V
2) Closed contact: Residual voltage ≤ 8 V at 4 mA
For information on the cabling of the alarm interfaces with protected control
units, refer depending on your FOX to [301] or [303].
Interfaces for timing
signals
The interfaces for the ESI-1 and ESI-2 timing signals require hardware and
software (via UCST) configuration for the impedance of the signal
termination.
For
• Functional information on the interfaces for timing signals, refer to the
corresponding paragraphs in the functional description and in [302].
• Physical layout of the interfaces for timing signals, refer to the
corresponding paragraphs on installation below.
• Impedance configuration for the ESI-1 and ESI-2, refer to the paragraphs
on "Maintenance".
For information on the cabling of the interfaces for timing signals with
protected control units, refer depending on your FOX to [301] or [303].

Installation
Prerequisites The implementation of the COBU<X> depend on the FOX subrack and the
control unit release:
• COBUX 219, 223 and COBUV 220, 224 require for operation and
configuration
− COBU<X> unit hardware
− FOX 515 or FOX 512 subrack
− Cobux_R5C ESW or a more recent version
− UCST R6A or a more recent version
• COBUX 212, 213 require for operation and configuration
− FOX 515 or FOX 512 subrack
− Cobux_R4E ESW or a more recent version
− UCST R5C or a more recent version
• COBUV 217, 218 require for operation and configuration
− FOX 515 and FOX 512 subrack
− Cobux_R4E ESW or a more recent version
− UCST R5C or a more recent version
Please note that:
• Keep unit in the ESD protection bag as long as the unit is not
inserted into the subrack.
• Before taking the unit out of its ESD protection bag, make sure
that you have not accumulated electro-static charges.
The COBU<X> unit requires hardware configuration for the input impedance
of the ESI-1 and ESI-2 for external 2048 kHz clock signals. Before you start
the installation of the COBU<X>, make sure that you know the required
setting of the impedance for the control units in the subrack.
The required impedance depends on the clock signal source, on the cabling
of the clock signals in the subrack and on the implementation of 1+1
protection for the control units.
For more information on this topic, refer to [302].
The COBU<X> provides a jumper to define either a 75 Ω termination (or 120
Ω termination for the ESI-1) or high impedance inputs for each ESI:
• Jumper X4700 for the ESI-1
• Jumper X4701 for the ESI-2
For details, refer to the corresponding paragraphs in the section
"Maintenance".
To avoid the alarm Wrong imp ext clk <x> it is essential that you
select an identical setting for both COBU<X> units in subracks with
redundant control units.

The insertion of units into the subrack requires the technique and the steps
as shown in [301] or [303].
Use of slots
Never use force to insert the unit into the subrack or to remove the
unit from the subrack!
Forcing insertion or extraction can damage the backplane and/or
unit connectors!
The implementation of equipment protection for the control units defines use
of slots in the NE subrack:
• NE without 1+1 equipment protection for the control unit
If you implement only one control unit in the NE, you must insert the
COBU<X> into slot 11.
No restrictions apply for the implementation of neighbouring units.
• NE with 1+1 equipment protection for the control unit
If you implement redundant control units in the NE, you must insert the
first COBU<X> into slot 11 (master slot for the default active unit) and a
second identical COBU<X> into slot 12 (slave slot for the default inactive
unit).
No restrictions apply for the implementation of neighbouring units.
For information on the cabling for the COBU<X> interfaces in NEs
with 1+1 equipment protection, refer depending on your FOX to
[301] or [303].
Connections and cables Depending on the local requirements and the NE configuration, the
COBU<X> requires connections and cables for all or only for a part of its
front panel interfaces.
F- interface (9-pin submini D) The F-interface uses a male D-Submini connector with 9 contacts.
The interface is of the type DTE according to the EIA 574 standard for the
signals and the pin layout.
Figure 12: Signal/pin layout for the F- interface connector
5
4
3
2
1
9
8
7
6
GND
DTR
TD
RD
DCD
NC
CTS
RTS
DSR
C3.1

The COBUX/C3.1-1 cable connects to the F- interface of the COBU<X>
directly to the serial interface of your PC/computer that runs the UCST. The
cable implements the null-modem function required for such a point-to-point
connection.
COBUX/C3.1-1 cable
Figure 13: COBUX/C3.1-1 cable drawing
C3.1 View A on side to connect View B on side to connect
View A
COBUX/C3.1-2 cable The COBUX/C3.1.2 cable connects the F-interface of the COBU<X> to a
modem device. The cable implements no null-modem function.
C3.1
View A
View A on side to connect
View B on side to connect
9 pin D-SUB
female
25 pin D-SUB
male
9 p. D-SUB
contact nr.
Signal

The COBUX/C3.1-3 cable connects to the F- interface of the COBU<X> to
the EOC. The cable allows you to connect F-interface of the COBU<X> to
the standard EOC F-interface cable provided with the SIFOX.
COBUX/C3.1-3 cable
C3.1
Signal jumper
View A on wire wrap side
View B on wire wrap side
A
B
View A 9 pin D-Sub female
25 pin D-Sub female
SIFOX-COBUX
9 pin D-SUB
female
25 pin D-SUB
female
To connect the COBU<X> to the EOC you must connect the 25 pin
connector of the COBUX/C3.1-3 adapter cable to a standard SIFOX-EOC
cable.
Figure 16: COBUX/C3.1-3 cable application drawing
Signal cable SIFOX - 4 EOC
Adapter cables SIFOX EOC - COBUX
COBUX/C3.1-3
540
This part of the cable remains on the cable tray
Connects to the SIFOX
1
2
1
1
1
2
2
2
For more information on the implementation of the EOC with the COBU<X>,
refer to [302] and [901].

The QX-interface uses a shielded RJ-45 connector with 8 contacts.
QX-interface (RJ-45 connector)
The signals and the pin layout of the QX-interface are implemented
according to the ISO/IEC 8802-3 (1993) standard.
Figure 17: Signal/pin layout for the QX-interface connector
1 : TD+
2 : TD-
3 : RD+
6 : RD-
4, 5, 7, 8 : not connected
and not used
1 2 3 4 5 6 7 8
C2.1
COBUX/C2.1-1 cable The COBUX/C2.1-1 cable connects to the QX- interface of the COBU<X>
directly to the Ethernet interface of your PC/computer that runs the UCST.
The cable implements the null-modem function required for such a point-to-
point connection.
C2.1
Wiring: 1 - 3 (S)
2 - 6 (gn) /
3 - 1 (r)
6 - 2 (og) /
4 - 4 (w)
5 - 5 (bl) /
7 - 7 (gb)
8 - 8 (bn) /
Pairs
B
View B

The COBUX/C2.1-2 cable connects the QX-interface of the COBU<X> to a
hub. The cable implements no cross over functionality. This type of cable is
normally used to connect the COBU<X> to a LAN.
COBUX/C2.1-2 cable
C2.1
View A
Wiring: 1 - 1 (S)
2 - 2 (gn) /
3 - 3 (r)
6 - 6 (og) /
4 - 4 (w)
5 - 5 (bl) /
7 - 7 (gb)
8 - 8 (bn) /
B
View B
DIN 41 612 front connector This multi-purpose interface uses a male DIN 41 612 connector type C with
2 x 32 contacts.
The contacts of the 2 rows a and c are arranged in 4 modules with module
specific coding for the connectors. The 4 modules are allocated to signal
groups as follows (top down):
• Q1-(slave) interface
• Q1-master interface
• Alarm interfaces
• Interfaces for external 2048 kHz clock signals

Figure 20: Signal/pin layout for the DIN 41 612 connector
Pin a b c
32 n.c. n.p. n.c. 
31 GND n.p. GND 
30 Q1_S_TX_A n.p. Q1_S_TX_B 
29 GND n.p. GND  Q1-(slave) interface
28 Q1_S_RX_A n.p. Q1_S_RX_B 
27 GND n.p. GND 
26 n.c. n.p. n.c. 
25 n.c. n.p. n.c. 
24 n.c. n.p. n.c. 
23 GND n.p. GND 
22 Q1_M_TX_A n.p. Q1_M_TX_B 
21 GND n.p. GND  Q1-master interface
20 Q1_M_RX_A n.p. Q1_M_RX_B 
19 GND n.p. GND 
18 Do not connect! n.p. n.c. 
17 n.c. (reserved) n.p. GND 
16 n.c. n.p. n.c. 
15 GND n.p. GND 
14 ALARM_IN_3 n.p. ALARM_IN_4 
13 ALARM_IN_1 n.p. ALARM_IN_2  Alarm Interfaces
12 n.c. n.p. n.c. 
11 UA_AO n.p. NA_AO 
10 UA_COM n.p. NA_COM 
9 UA_AC n.p. NA_AC 
8 n.c. n.p. n.c. 
7 ESI-1_75_signal n.p. ESI-2_75_signal 
6 ESI-1_75_screen
ESI-1_120_signal_b
n.p. ESI-2_75_screen 

5 ESI-1_120_signal_a n.p. ESO-4_120_signal_a  Synchronisation
4 ESO-1_75_signal n.p. ESO-2_75_signal  Interfaces
3 ESO-1_75_screen n.p. ESO-2_75_screen 
2 ESO-3_75_signal n.p. ESO-4_75_signal 
X100
1 ESO-3_75_screen n.p. ESO-4_75_screen
ESO-4_120_signal_b


n.c.: not connected
n.p.: no pin
Please note that:
• You must never connect the pin 18a!
This pin carries a signal for future use.
• You must not connect the pin 17a!
This pin is reserved for future use.

• The 120 Ω ESI and ESO interfaces are only available with the
COBU<X> hardware
− ROFBU 367 103/1 R2B (COBUX)
− ROFBU 367 103/2 R1A (COBUV)
or with more recent hardware.
Q1-(slave) interface
COBUX/C1.4 cable This cable connects to the Q1-(slave) interface. This interface provides the
NE standard management interface for the connection to a local Q-BUS.
Figure 21: COBUX/C1.4 cable drawing
C1.4
(The figures in brackets correspond
to the pin numbers of the
DIN 41 612 unit connector)
View A
A
Q1-master interface
COBUX/C1.3 cable This cable connects to the Q1-master interface of the COBU<X> to the local
Q-Bus. This interface provides the bus master for the local Q-BUS.
C1.3
View A
(23) 1
(21) 3
(20) 4
(19) 5
(18) 6
(17) 7
(22) 2
a c
A

Alarm interfaces
Cable COBUX/C1.2 This cable connects the signals of the COBU<X> alarm interface.
C1.2
View A
Cable FANUV/C1.1-1 and
FANUV/C1.1-2
The FANUV/C1.1-1/2 cables provide among other a connector for the C1.2
position in the COBU<X> connector frame. The connector connects the
FANUV alarm signal to the External Input-1 of the COBU<X>.
Please note:
• The FANUV/C1.1-1/2 cables exclusively connect the External
Input-1 (via pins 3a and 1c). No other pins are connected.
• If you want to connect additional alarm signals (for input or
output) you have the option to
− open the connector of the FANUV/C1.1 alarm signal cable
and connect your alarm signals to the corresponding signal
pins of the connector.
− integrate the FANUV alarm signal cable into a custom-made
alarm signal cable/connector.
For details of the FANUV/C1.1-1/2 cables, refer to the corresponding
paragraphs in [301].

Synchronisation interfaces
COBUX/C1.1-1 cable This cable connects to the PETS synchronisation interfaces (all 75 Ω) of the
COBU<X> as follows:
• In 1: ESI-1/PETS (and the ESI-1/SETS 75 Ω option)
• Out 1: ESO-1/PETS
C1.1
View A
ESI-1 (2 MHz In1)
ESO-1 (2 MHz Out1)
ESO-3 (2 MHz Out3)
ESO-2 (2 MHz Out2)

This cable connects to the SETS and PETS synchronisation interfaces (all
75 Ω) of the COBU<X> as follows:
COBUX/C1.1-3 cable
• In 1: ESI-1/PETS and ESI-1/SETS (75 Ω option)
• Out 4: ESO-4/SETS
C1.1
View A
ESI-1 (2 MHz In1)
ESO-1 (2 MHz Out1)
ESO-4 (2 MHz Out4)
ESO-2 (2 MHz Out2)

This cable connects to the SETS and PETS synchronisation interfaces (all
75 Ω) of the COBU<X> as follows:
COBUX/C1.1-4 cable
• In 1: ESI-1/PETS and ESI-1/SETS (75 Ω option)
• In 2: ESI-2/PETS
• Out 4: ESO-4/SETS
C1.1
ESI-1 (2 MHz In1)
ESO-1 (2 MHz Out1)
ESI-2 (2 MHz In2)
ESO-4 (2 MHz Out4)
View A
COBUX/C1.1-6 cable This cable connects to the SETS (and ESI-1/PETS) synchronisation
interfaces (all 120 Ω) of the COBU<X> as follows:
• In 1: ESI-1/SETS and ESI-1/PETS (120 Ω option)
• Out 4: ESO-4/SETS (120 Ω option)
C1.1
ESI-1 (2 MHz In1)
View A
ESO-4 (2 MHz Out4)

The figure below illustrates the distances required between the front of the
cable tray and the connector to allow the correct attachment of the cables to
the cable tray.
Fixing the cables to the
cable tray
Figure 28: Fixing the cables to the cable tray
(example for the FOX 515)
185
145
165
205
275
280
Synchronisation IF
Alarm IF
Q1-master IF
Q1-(slave) IF
Qx- IF
F-IF
The cable route on the cable tray should follow approximately the
projection of the control unit slot on the cable tray.

Configuration and Operation
Overview The COBU<X> provides parameters for traffic services and management
communication. All these parameters are grouped in functional layers that
are represented as tabs in the UCST dialogues.
With the UCST R6A all the COBU<X> provide 7 functional layers of
parameters for configuration. The COBUV has an additional layer for the
configuration of the conference parameters:
• COBU<X> basic parameters
− Board
The Board Layer provides the parameters for the configuration of the
− ESI (External Synchronisation Inputs) interfaces
− Inputs for external alarm signals
− Communication IF
The Communication IF Layer provides the parameters for the
configuration of the
− Access to the NE
− Serial interface (host address, F-interface)
− Ethernet interface (QX-interface)
− Q1-master gateway (Q1-master interface)
The parameters of this layer are at the same time basic parameters
for the NE and parameters in connection to the FOX MCN.
• NE MCN parameters (COBU<X> router)
− SDH ECC
The SDH ECC Layer provides the parameters for the configuration of
up to 8 SDH ECCs.
− OSI DCN
The OSI DCN Layer provides the parameters for the configuration of the
− CLNP functionality
− IS addresses for the NE
− OSI tunnel for the tunnelling of the IP routing
− PDH ECC
The PDH ECC Layer provides the parameters for the configuration of
up to 32 PDH ECCs. (It can also be used to cross connect ECC over
ATM links with COBU<X>).
− IP Router
The IP Router Layer provides the parameters for the configuration of the
− Router functionality
− Router interfaces
− OSPF areas
− External routes
− Virtual links
• COBU<X> special functions
− Conference Parties (COBUV only)
The Conference Layer provides the parameters for the configuration
of up to 64 conference parties.
− Diagnostics
The Diagnostic Layer provides the parameters for the configuration of the
− Diagnostic functionality
− Test pattern (rate, structure)
− Signalling bits
− Artificial error insertion

Most of the COBU<X> functional layers define parameters for the NE that
are linked to the FOX MCN. It is only possible to set these parameters in
connection with the FOX MCN definitions. Accordingly, these layers are not
described in detail in this document.
However, the paragraph "Guidelines for the configuration of the NE MCN
part" under "NE MCN parameters" provide an overview and guidelines for
the configuration of the NE MCN part in the COBU<X>.
For detailed information on the FOX MCN configuration, refer to [901].
Setting basic parameters
Board The Board layer provides the parameters for the alarm interfaces and the
interfaces for the external timing signals.
Double click on the COBU<X> to open the Parameters… dialogue or click
on the COBU<X> and select the dialogue via the menu Unit Configuration
→ Parameters….
select the tab Board if not already selected.
Figure 29: Unit Configuration Parameters - Board layer dialogue
UCST
ABB
The following are settable parameters on the Board Layer:
• Synchronisation inputs ESI-1 and ESI-2
− Impedance (75/120 Ohm or 75 Ohm, high impedance)
• External alarms input 1 … 4
− State (enabled, disabled)
− Polarity (active open, active ground)
− Name (alarm name of up to 31 characters)

The ESI-1 and ESI-2 interfaces of the COBU<X> accept external 2048 kHz
timing signals according to ITU-T G.703.
Timing signals
It is possible to terminate each of the ESI timing signals with „high
impedance“ or „75/120 Ω“ and „75 Ω“ respectively on the COBU<X>:
• High impedance
Use this setting if
− you want to use an external termination for the timing signal
− you feed the external timing signal in parallel to redundant control
units.
• 75/120 Ω and 75 Ω impedance
Use this setting if
− you want have no external termination for the timing signal
− you feed the external timing signal separately to each of the
redundant control units.
Please note that
• The ESI-1 interface provides pins for 75 Ω and 120 Ω timing
signals. If you select 75/120 Ω signal termination for the ESI-1
the
− pins for the 75 Ω ESI-1 signal provide the required 75 Ω
termination.
− pins for the 120 Ω ES-1 signal automatically provide the
required 120 Ω termination.
• The ESI-2 interface provides only 75 Ω (and high impedance)
timing signal termination.
The interfaces for the ESI-1 and ESI-2 timing signals require software
configuration (via the UCST) and hardware configuration (via jumpers) for
the signal termination.
The corresponding paragraphs in "Maintenance" provide the description for
the hardware configuration.
Mismatching settings between the hardware configuration and the
UCST configuration creates a corresponding alarm. For the
description of the alarm, refer to the paragraphs „Alarms and
Notifications“.
External alarms To enable the monitoring for an external alarm
Select the Input <x> and
tag the box [Enabled] in the State column to enable the
monitoring for input <x>
select the active level from the Polarity column to define
the active level:
- active Ground
- active Open
specify <Alarm Name> in the Alarm Name column
(optionally).

If you specify an Alarm Name for the external alarm, the fault management
system uses your name for the configuration of the alarm parameters and in
the NE alarm list and NE logbook.
If you do not specify such a name, the fault management uses the default
name External alarm <x>.
Communication IF The Communication IF layer provides the parameters for the Ethernet and
serial interface and if applicable for the Q1-master Gateway and the NE
access password.
The parameters of the Communication IF layer are at the same time basic
parameters for the NE and parameters in connection to the FOX MCN.
Double click on the COBU<X> to open the Parameters… dialogue or click
on the COBU<X> and select the dialogue via the menu Unit Configuration
→ Parameters….
select the tab Communication IF if not already selected.
Figure 30: Unit Configuration Parameters - Communication IF layer
dialogue
UCST
ABB
The following are settable parameters on the Communication IF Layer:
• Host name (host name of up to 32 characters)
• NE password (password of up to 7 characters)
• Serial Interface
− IP Host Address (Node Id) (any valid IP address)
− HDLC Address (1 … 254)
− Default Speed (9600 … 115200)
• Ethernet Interface
− Enable the Ethernet interface
− IP Host Address (any valid IP address)
− Subnet Mask (any valid subnet mask)

• Q1 Master Gateway
− State (enabled, disabled)
− TCP/IP Port (20736)
The Serial and Ethernet Interface layers define parameters for
the NE that are linked to the FOX MCN. After the initial
commissioning of the NE you must consider the FOX MCN
definitions when setting these parameters.
For a detailed description of the FOX MCN parameter configuration, refer to
[901].
Host name The UCST R6A does not use the parameter Host Name.
You can use the Host Name field for your NE related notes.
NE password The NE Password allows you to protect the access to the NE with a password.
To specify the NE Password
select the field New Entry and type in your password (max. 7
characters).
Confirmation and repeat your password.
You must specify the NE Password for the Management Network.
If the Management Network does not know the password, it is no
longer able to access the NE and reports a "Login error" (layer 7
error).
To specify the NE Password in the Management Network you must select all
the Element Agents (from Management Network Parameters) that have the
corresponding NE in their list of Managed NEs.
Select then the corresponding NE and open the Modify Network Element
dialogue. Add the NE Password in the Password field.
For details on the configuration of the Element Agent and the Managed NEs,
refer to the corresponding paragraphs in [401].
Serial interface The Serial Interface provides parameters for the 2 basic types of NE access:
• Direct access
The UCST (UNEM) always uses the IP address to identify and access
the COBU<X>.
The IP Host Address (Node Id) is mandatory since it also defines the
Node Id of the NE.
• Access via HDLC tunnelling
The second set of parameters define the HDLC based communication
parameters:
− HDLC Address
The UCST (UNEM) uses the HDLC address to access the NE via the
Q-bus and the legacy EOC.
− Data Speed
The Data Speed defines the speed for all HDLC based accesses (Q-
bus and legacy EOC, ATU).

The parameter does not affect the speed for direct NE access via the
F-interface. With direct access the COBU<X> adapts the speed
automatically to the speed of the client interface (UCST (UNEM)).
For all the access types that use the HDLC address (Q-interface,
legacy EOC, ATU) it is essential that the speed setting in the
Communication IF dialogue corresponds exactly to the settings in
the RAS phonebook for the corresponding RAS connection!
If the speeds are not matching, the management communication fails!
If you change the Host IP Address in the NE configuration and
download that change to the NE, the NE restarts (warm start).
This restart is required to allow the NE to build up all the protocol
stacks on the new Host IP Address.
The (warm) restart does not affect the traffic and services of the
NE. However, the NE fault management is not available during the
restart phase.
Ethernet interface The Ethernet Interface parameters allow you to define the operation of the
QX-interface for IP:
• Enable
If the interface is enabled
− you must specify the parameters as described below.
− the COBU<X> monitors the QX-interface for signal integrity. If the
Ethernet signal fails the COBU<X> issues an alarm (if configured).
• IP Host Address
Any valid IP address. The address is required only if the QX-interface is
enabled.
• Subnet Mask
Any valid Subnet mask. The mask is required only if the QX-interface is
enabled.
The Ethernet Interface (QX-interface) provides 4 modes of
operation which you configure via the Communication IF and the
OSI DCN dialogue:
• Disabled (in Communication IF and OSI DCN dialogue)
• Enabled for TCP/IP (in Communication IF dialogue only)
• Enabled for CLNP (in OSI DCN dialogue only)
• Enabled for TCP/IP and CLNP
(in Communication IF and OSI DCN dialogue)
This means that the QX-interface can simultaneously carry TCP/IP
and CLNP traffic. This functionality of the QX-interface allows you
to transport the TCP/IP traffic and the CLNP traffic on the same
physical LAN.
For example, from the QX-interface to the UCST (UNEM) (=
TCP/IP traffic) and from the QX-interface to the STM-1 device (=
CLNP traffic) that provides the IP tunnel.

Manual FOX ABB Teleprotecciones.pdf

Manual FOX ABB Teleprotecciones.pdf

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Manual FOX ABB Teleprotecciones.pdf

Similar to Manual FOX ABB Teleprotecciones.pdf (20)

Recently uploaded

Recently uploaded (20)

Manual FOX ABB Teleprotecciones.pdf