Release Note PDF

UMUX from KEYMILE covers your communication requirements
Release Note
UMUX & UCST R8B SP02
UMUX & UCST R8
Page iii Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
Introduction: The provision of UMUX and UCST software is subject to the terms of the relevant KEYMILE software license. This document is provided
for information purposes only, and in no way amends or invalidates the terms of such licence.
The provision of Embedded Software (ESW) is subject to the terms of the relevant KEYMILE software license. This document is provided
for information purposes only, and in no way amends or invalidates the terms of such licence.
Copyright and Confidentiality: Copyright in this document vests in KEYMILE AG. The information in this document is confidential, and may only be used by recipient for
the purposes of operating and maintaining UMUX and UCST software. The contents of this document may not be copied or disseminated
to any third party without the prior written agreement of KEYMILE.
Disclaimer: KEYMILE has taken reasonable care in compiling this document, however KEYMILE accepts no liability whatsoever for any error or omis-
sion in the information contained herein and gives no other warranty or undertaking as to its accuracy.
KEYMILE reserves the right to amend this document at any time without prior notice.
KEYMILE PEC: EN/LZTBU 980 415/512 RA
KEYMILE AG
Schwarzenburgstrasse 73
CH-3097 Bern-Liebefeld
Switzerland © May 2008 by KEYMILE AG
© KEYMILE AG
Table of contents i
1 Introduction 1
1.1 About this document 1
1.2 Overview of the multiservice access platform R8B 5
1.2.1 The UMUX platform 5
1.2.2 Network elements and units 5
1.2.3 Traffic services and interfaces 5
1.2.4 Remote units and services 9
1.2.5 Management tools and interfaces 10
1.2.6 Signal layers 11
2 New content 14
2.1 Functionality 14
2.1.1 R8B SP01 14
2.1.2 R8B SP02 14
2.2 Correction of deficiencies 19
2.2.1 Cleared limitations 19
2.2.2 New ESW for current function units 19
3 Summary of network elements 22

3.1 UMUX 1500 22
3.1.1 Features 22
3.1.2 System cores 25
page iii Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
Table of contents © KEYMILE AG
3.1.3 Auxiliary equipment 25

3.2 UMUX 1200 27
3.2.1 Features 27
3.3 UMUX 900 32
3.3.1 Features 32
3.4 Patch panels 36
3.5 Legacy equipment 37
4 Summary of units 38
4.1 Control, power and fan units 38
4.1.1 Control units 38
4.1.2 Power units 41
4.1.3 Fan units 41
4.2 ABUS units 42
4.3 PBUS units 45
4.4 SBUS units 55
4.5 UBUS units 60
4.6 Special units 65
4.7 Obsolete function units 68
4.8 Desktop units 72
4.9 Modules 78
4.9.1 PC memory cards 78
4.9.2 SFP modules 78
page iv Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
5 UCST R8B 80
5.1 PC / OS requirements 80
5.1.1 General 80
5.1.2 Windows® 2000 80
5.1.3 Windows® XP Professional 81
5.1.4 Windows® Vista Enterprise (32-bit version) 81
5.1.5 Windows® Server 2003 81
5.1.6 RS-232C interface 82
5.2 Installation of UCST service packs 83
6 Compatibility and upgrades 84

6.1 Support of legacy UMUX 84
6.2 Configuration 85
6.2.1 Compatibility with previous configurations 85
6.2.2 Procedures 85
6.3 Control units 87
6.3.1 Support of units 87
6.3.2 Upgrade process 88
6.4 Support of PC flash memory cards 89
6.5 New unit hardware 90
6.6 IPSMG conversion 90
6.7 NE traffic 90
6.8 Ordering of units 91
6.8.1 Ordering process 91
6.8.2 Background information 91
page v Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
7 Software carriers and documentation 93

7.1 Software and software packages 93
7.1.1 UCST 93
7.1.2 Embedded Software 94
7.2 Customer documentation 95
7.2.1 Overview 95
7.2.2 UMUX / UCST customer documentation 95
7.2.3 Associated customer documentation 98
8 Limitations 99
8.1 Overview 99
8.2 ACONV 100
8.3 ADACA / ADACB 101
8.4 ADACS 102
8.5 ATIOP 102
8.6 COBUX 103
8.7 GECOD 105
8.8 IPLMx 106
8.9 IPSMG 107
8.10 ISBUT 108
8.11 LAWA4 109
8.12 LECAF - LECA2 109
8.13 LEMU6 111
8.14 LESA8 - LESI8 112
8.15 LOMIF - LOMI4 114
8.16 MIRIG 115
page vi Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
8.17 MUSIC 100 116

8.18 MUSIC 200 116
8.19 MUSIC 700 117
8.20 NEBRO / NEBRA 117
8.21 NEMCA 118
8.22 PCONV - PCON2 119
8.23 PHLC1 - PHLC2 - PHLC3 120
8.24 POTS Splitter 121
8.25 SLIM1/2 - SLID1/2 122
8.26 STIC1 - STIC2, LRD1A - LRD1B - LRD2A, SREG1 - SREG2 123
8.27 SYNAM - SYNIx - SYNOT - SYNVA – SYNUF – SYN4E 124
8.28 TUNOx 125
8.29 TUPON 126
8.30 UNIDA 127
8.31 Miscellaneous 128
page vii Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
© KEYMILE AG
1 Introduction
1.1 About this document
KEYMILE AG proudly announces the new release R8B of the UMUX multiservice access plat-
form.
This release note provides important information of the features and functions released for the
UMUX multiservice access platform. It describes the elements released and the requirements
for the installation and operation of the UCST management software:
• Chapter 1, «Introduction» describes the subject of the release note and provides a short over-
view of the structure and the contents of the release note.
• Chapter 2 «Functions and systems» on page Fehler! Textmarke nicht definiert. provides an
overview of traffic services and functions provided with the UCST / UMUX platform R8B. Sepa-
rate paragraphs are dedicated to new and enhanced functions and units introduced with the
platform and its service packs (if any).
• Chapter 3 «Summary of network elements» on page 22 describes the network elements of
the current platform release. It provides an overview of the supported units per network element
and a description of the required/available core units for the NEs.
Descriptions of the available system cores (subracks and core units) and options available are
provided as well.
• Chapter 4 «Summary of units» on page 38 has tables which provide an overview of the com-
patible unit hardware and software (ESW) for the UMUX function units. The function units are
divided in groups according to their physical bus access or system functionality where applica-
ble. Within the groups the function units are alphabetically sorted.
A separate table describes obsolete function units and their substitutes where applicable.
A further paragraph is dedicated to the description of compatible hardware and software of the
UMUX supported desktop units.
page 1 of 129 Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
Introduction
• Chapter 5 «UCST R8B» on page 80 describes the requirements on PC / Laptop hardware and
software for the installation and operation of the UCST software and gives details for the instal-
lation of the UCST service packs.
• Chapter 6 «Compatibility and upgrades» on page 84 describes the aspects of compatibility of
UCST and ESW upgrades with the current NE configurations and functions. Where required,
descriptions of the upgrade procedures are provided as well.
• Chapter 7 «Software carriers and documentation» on page 93 lists the software packages
available with UCST management software and embedded (unit) software.
An separate section describes the customer documentation released for the UMUX multiservice
platform and lists the packages available. For information of the current training offers, please
read the training program provided on KEYMILE’s homepage «www.keymile.com/»on under
«Services → Training → ...».
• Chapter 8 «Limitations» on page 93 lists the known limitations on a per unit basis.
If you need additional information, please contact your KEYMILE sales representative or consult
KEYMILE via its homepage «www.keymile.com/».
Page 2 of 129 Release Note UMUX & UCST R8B SP02 and related functions EN/LZTBU 980 415/512 RA
Introduction
Abbreviations used in the tables of this document:

Abbreviation Plain text Description (optional)
AC Accessory Extension of the short name (<name>-AC) describing the
category of the short named item.
AP Application Extension of the short name (<name>-AP) describing the
APDSW Application Download Soft- UMUX software which loads the ESW from the MIB of the
ware NE to the units.
BF Bug Fix Here used in context with ESW: New ESW that has been re-
leased asynchronously to the Releases and Service Packs to fix
bugs.
CS Core System Extension of the short name (<name>-CS) describing the
ESW Embedded Software Application software which is downloaded to the UMUX
control and service units.
FU Function Unit Extension of the short name describing the category of the
short named item.
HK Hardware Key Part of the inventory data which identifies the type of the
hardware for the ESW.
HP-UX Hewlett Packard UniX Hewlett Packard proprietary version of the UNIX operating
system for HP workstations.
HW Hardware
MG MileGate Generic abbreviation for KEYMILE’s MileGate network ele-
ments and the MileGate product family.
n.a. not applicable
NE Network Element Generic term for managed elements in a network.
OS Operating System Operating system (and version) required to run the specified
application software. The application software is released
for the specified OS(s) only.
PEC Product Engineering Code The KEYMILE Product Engineering Code technically identi-
fies and describes the product, its state and evolution. The
PEC cannot be used for ordering or other commercial pur-
poses.
PH PBUS Highway access per Maximum number of PBUS highways (2 Mbit/s of traffic
unit signals plus corresponding signalling) accessed per unit.
Rel. Release Release (version).
RHE Red Hat Enterprise Provider of the Linux OS software for the UNEM software.
Introduction
Abbreviation Plain text Description (optional)

SE Set Extension of the short name (<name>-SE) describing the
SP Service Pack Extension of the short name (<name>-SP) describing the
SL Software Lizence Extension of the short name (<name>-SL) describing the
SW Software
TIU Template Introduced with the Describes the UCST version with which the corresponding
indicated UCST version unit template has been introduced.
TOU Template Obsolete with the Describes the UCST version with which the corresponding
indicated UCST version unit template became obsolete.
UG
UMUX UMUX Generic abbreviation for UMUX network elements and the
UMUX product family.
Vers. Version
[NM] [Network Management] Index for the reference numbers of the UNEM and network
management platform (e.g. reference [NM].[101]).
[UX] [UMUX] Index for the reference numbers of the UMUX/UCST plat-
form (e.g. reference [UX].[101]).
Introduction
1.2 Overview of the multiservice access platform R8B
1.2.1 The UMUX platform
The UMUX platform offers a range of compact, flexible, migration capable and managed systems,
offering unequalled multi-service & multi-transmission capability.
The services supported by UMUX range from traditional telephony, broadband Internet access and
private circuits to new services such as broadband Ethernet Private Lines / LANs, Triple Play and
Voice over Packet.
The UMUX Multiservice Access Platform is composed of the following components:
• Network elements (with units)
• Desktops (remote units)
• Management Systems
1.2.2 Network elements and units
UMUX is available in 3 subrack versions, UMUX 1500, UMUX 1200 and UMUX 900. Each version
is particularly suited for a range of applications and the corresponding installation requirements
while the system features remain the same. Each subrack uses the same units (release of the unit
for the UMUX type provided).
1.2.3 Traffic services and interfaces
The UMUX/ UCST R8B platform with Service Pack 02 supports traffic types as follows:
• PDH traffic
The UMUX can multiplex and cross connect both P0-nc and P12x traffic. The cross connect ca-
pacity is in total 128 x 2 Mbit/s (for signals with and without signalling) for the UMUX 1500. The
practically used capacity with the UMUX 1200 and especially the UMUX 900 is well below this
capacity because of the reduced number of slots available for traffic units in the UMUX 1200
and UMUX 900 subracks.
The cross-connect handles structured and unstructured P12 traffic signals for transparent cross
connecting. Structured P12s signals with or without signalling are either switched transparently
or de-multiplexed and switched as P0-nc traffic signals.
Introduction
Various traffic units allow the UMUX to connect a big variety of traffic signal types from PSTN,
ISDN-BA and standard data services up to V5 and IP services (IP over PDH).
• SDH traffic
The UMUX provides STM-4 and STM-1 interfaces which allow you to groom E12/P12, E31/32
and IP (Ethernet) tributary traffic for SDH transmission. The UMUX provides electrical STM-1
and optical STM-4/1 interfaces for the aggregate traffic. It is possible to directly connect VC-12
and VC-3 traffic between 2 STM-1 aggregate interfaces and up to VC-4 traffic between the
STM-4 interfaces.
The units with STM-4 and STM-1 aggregate interfaces provide the SETS timing function for the
UMUX.
To cope with the tributary traffic, the UMUX provides units with P12 or E12 interfaces for inter-
nal and external tributaries and an E31/32 interface for external tributaries. A further unit with an
optical STM-1 tributary interface handles high volume tributary traffic for the STM-1 aggregate
interfaces.
• IP traffic
The UMUX provides various units and desktop units with local and remote Ethernet interfaces.
Traffic units with bridging and routing capabilities are available for the processing of IP traffic
between remote interfaces (desktops) and the internal PDH traffic structures.
The processing of IP traffic not only includes routing and bridging but allows for Ethernet over
SDH applications (VLAN) and includes Voice over IP for Access Gateway applications with
NGN.
• ATM traffic
With the ABUS traffic units, it is possible to implement an ATM core for various services in the
UMUX. The UMUX supports ATM as follows:
− ATM layer (according to ATM Forum AF-TM-0121.000, Traffic Management Specification,
Version 4.1)
– Permanent virtual connections (PVCs) only, up to 2048 connections per NE
– Point to point, bi-directional, asymmetric VCCs and VPCs
– UNI cell format
– Service categories supported: CBR, VBR-rt, VBR-nrt and UBR
– Conformance definitions: CBR.1, VBR.1 and UBR.1
– Ingress traffic control functions: Usage parameter control (UPC),
Connection admission control (CAC)
− Egress traffic control functions: VP shaping (STM-1 UNI), CAC
Introduction
− ATM cross connect

– Switching capacity 515'160 kbit/s (1'215'000 cells/s)
– Up to 2048 connections per network element
– Accessible by up to 8 units (slots), depending on type of subrack
− Although the cross connect fabric allows connections to be set up from any port to any
port or service, the UMUX has still to be considered as an ATM multiplexer or concentra-
tor with a maximum aggregate bandwidth according to STM1 towards the regional ATM
network.
– ECC over ATM
– QoS: CBR (CBR.1)
– PCR: 80.1 kbit/s, 240.4 kbit/s and 720.4 kbit/s
– CDVT: 5000 µs
− «PPP over AAL5», encapsulation method «VC-multiplexed PPP» according to
RFC 2364.
− ATM UNI (User-to-Network Interface) physical
− STM-1 optical interface for the transmission of ATM cells (in VC-4) in the ATM network
(ATM-UNI).
The STM-1 (ATM) interface supports
- 149760 kbit/s corresponding to 353207 cells/s.
- Multiplex Section protection
− IMA (Inverse Multiplexing of ATM) for the transmission of ATM cells via a set of P12s
(P0-nc) TDM links.
An IMA group supports from 2 up to 16 links, each link with a bandwidth of 1920 kbit/s
(4528 cells/s).
− ADSL and SHDSL modem interfaces for the transmission of ATM cells and the access to
remote CPE (IAD) with PSTN and ISDN-BA user ports.
- The ADSL interface supports transmission rates as follows
- Upstream: 32 kbit/s … 1024 kbit/s
- Downstream: 32 kbit/s … 8064 kbit/s
- The SHDSL interface supports transmission rates (up-/downstream) as follows

- 1 pair: 200 kbit/s … 2320 kbit/s
- Pair bonding (2 pairs): 400 kbit/s … 4640 kbit/s
The UMUX supports the configuration of the ADSL and SHDSL interfaces with profiles.
− ATM Services
− Circuit Emulation Service: CES 2048 kbit/s (AAL1)
CES supports the emulation of P12 TDM circuits which are transmitted via an ATM UNI
Introduction
in the ATM network. CES includes various synchronisation modes depending on the con-
nection modes on the PBUS
- Adaptive or SRTS for transparent or monitored P12 cross connection
- Synchronous, SRTS or adaptive for terminated or clock master P12 cross
connection modes
The UMUX builds its ATM core with dedicated ATM traffic units around the ABUS. The ABUS is
physically identical with the SBUS. However, the traffic signal structure of the ABUS uses cells
instead of the SDH frames on the SBUS. The ABUS transports the cells from one connection
point to another connection point.
The transport rate of the ABUS for ATM cells is 1215 kcells/s. This is equivalent to a bit rate of
515160 kbit/s (53 bytes per cell).
Depending on the implemented units, the ATM core uses SETS or PETS for system and unit
timing purposes.
• V5.x services
The V5.x options of the UMUX allow you resolve the V5.1 and V5.2 protocol in the UMUX
1500/1200 and to connect local and remote PSTN and ISDN-BA user ports in the UMUX net-
work. The UMUX supports user port access via PDH.
The UCST provides custom parameter sets which allow fast installation and uniform commis-
sioning of new V5 units in the UMUX network. The custom parameter set defines parameters
for the V5.x protocol implementation as well as traffic related parameters.
• NGN services
Telephony NGN (New Generation Network) provides telephony services to legacy terminals
such as analogue and ISDN phones that are not NGN capable. With telephony NGN, the tele-
communication network has distributed switching functionality which is separated from the con-
trol mechanism. The UMUX provides the Access Gateway functionality for telephony NGNs.
The UMUX and its units support functions for NGN as follows:
− Processing of the user port signalling and circuit set-up/release and exchanging of corre-
sponding messages via IP traffic with its MGC (Media Gateway Controller). This includes
– Conversion of analogue telephone traffic into IP traffic (RTP) and vice versa
– POTS: H.248 / MEGACO (ITU-T, H.248.v1) for PSTN signalling conversion from/into
H.248 messages.
− POTS and ISDN BA: H.248 / MEGACO for setting up / tearing down the connection be-
tween a TDM based voice channel and an IP based channel.
− ISDN BA: Signalling gateway for the transport of D-channel frames between the Access
Gateway and the ASP (Application Server Process) using SIGTRAN (IUA/SCTP).
Introduction
− Support of Customer Parameter Sets for commissioning of soft switch interoperability

− Provisioning of POTS and ISDN-BA user ports (local and remote)
• IP DSLAM with real Broadband Triple Play services
The UMUX supports a modular IP DSLAM implementation with the IPLM1/2/4 units which have
24 ADSL/ADSL2(+) and the IPLM6 unit has 24 G:SHDSL/G.SHDSL.bis interfaces and provide
the interworking functions for the termination of the ATM layer and adaptation of the Ethernet
traffic for IP services. IPLM unit versions support ADSL over POTS (IPLM1/2) and ISDN-BA
(IPLM4). With the new IPLM units the UMUX supports triple play services as follows:
− Broadband internet access
− (TV) Multicasting and video on demand
− Voice over IP
− Access:
– ADSL/ADSL2(+) loop access to the residential gateway (CPE)
– G.SHDSL/G.SHDSL.bis loop access to the residential gateway (CPE)
− Gbit-Ethernet uplink for the access to the service provider
It is possible to cascade several units for the implementation of IP DSLAMS with n x 24 ADSL /
ADSL2(+) or G.SHDSL / G.SHDSL.bis interfaces with a common uplink. The UCST supports
the management of the basic unit functions and management access of the DSLAM unit. A
dedicated CLI – also launched via UCST - allows for the configuration of the DSLAM parame-
ters and the DSLAM fault management.
The high density of the IP DSLAM interfaces on the units and the corresponding power dissipa-
tion require imperatively forced ventilation for the UMUX subrack.
1.2.4 Remote units and services
The UMUX Multiservice Access Platform includes a set of desktop units for the remote installation
(customer premises) which allow the deployment of remote traffic interfaces and services. The re-
mote units have electrical (xDSL) interfaces for the data transmission with the UMUX NEs. Some
of the desktop units operate in standalone applications as well.
The desktop units (xDSL transmission) provide remote interfaces for
• PDH traffic with various interfaces (G.703, V<xx> , X<xx> interface series)
• Ethernet traffic
Desktop units with Ethernet traffic interfaces include additional traffic functions for IP traffic
processing (e.g. bridging, routing).
Introduction
• PSTN and ISDN interfaces

Desktop units with PSTN and ISDN interfaces can provide user ports for V5 and NGN applica-
tions.
A desktop unit for optical 8 Mbit/s transmission with 4 x 2 Mbit/s G.703 or V.11 traffic interfaces
completes the remotes units of the UMUX multiservice platform.
Remote units connected to the UMUX are fully managed by the UMUX management system.
1.2.5 Management tools and interfaces
1.2.5.1 Management software
The UMUX Multiservice Access Platform has two management toots:

• UCST
The UCST is recommended for the management of single UMUXs or small UMUX networks.
The UCST runs on an ordinary PC/notebooks under Windows® operating systems as specified
in the paragraph «PC / OS requirements» on page 80.
• UNEM
The UNEM is comprehensive management software managing network elements and net-
works. It is suited for medium to large sized UMUX networks. The UNEM has a modular archi-
tecture which allows distributed and scalable installations. Operation control and NE access
have multi-session capabilities, while the UNEM core manages one central database and all the
north bound interfaces.
The UNEM runs on PCs with Linux (Red Hat Enterprise) and HP workstations with UNIX (HP-
UX 11i) operating systems as specified in the applicable UNEM release note.
1.2.5.2 Management interfaces
The UMUX features local interfaces for NE management and the ECC (Embedded Communication
Channel) functionality for remote management with the UCST and UNEM:
The ECC is a high performance in-band channel, which allows the implementation of versatile in-
band MCN (Management Communication Networks) for the management of the UMUX 1500,
UMUX 1200 and UMUX 900 networks. The ECC functionality includes OSPF routing for the UMUX
management traffic in the NEs and the transport of the ECC over SDH (OSI tunnelling) and ATM
(ECC over ATM) networks.
The UMUX supports interfaces for management communication as follows
Introduction
• External management interfaces for local NE access

− The QX-interface is an Ethernet interface (10BaseT) for management access via LANs.
− The F-interface is a serial interface (RS 232) and is functionally compatible to the corre-
sponding interface of the legacy UMUX 1100(E) and UMUX 1300.
− The Q1-interfaces is a serial bus interface (RS 485)
All the UMUX support the Q1-(slave) interface which is functionally compatible to the corre-
sponding interface of the legacy UMUX 1100(E) and UMUX 1300.
The UMUX 1500 and UMUX 1200 provide the Q1-master interfaces which allows you to sub-
tend legacy UMUX for NE management via the Q-bus. The Q1-master interface provides a
remote replication of the UCST / UNEM Q-bus access via the ECC DCN.
• Internal management interfaces
The router of the control unit supports up to 32 ECC interfaces which internally connect to
− ECC transported in standard PDH channels (normally embedded in P12 as P0-nc traffic) in
the PDH network.
− ECC transported in the SOH (Section Overhead) of the STM-1 frame in SDH networks. In
open SDH networks these ECC require encapsulation in the OSI stack which is used in SDH
networks for management communication. This functionality is implemented on the control
unit.
− ECC transported via ATM networks. This requires the encapsulation of the ECC in ATM cells.
This functionality is implemented on the units with the ATM UNI. (STM-1, IMA).
For compatibility with legacy UMUX, the UMUX 1500 and UMUX 1200 can connect via the SIFOX
unit to the EOC (Embedded Operation Channel). The EOC provides the management communica-
tion network for the legacy UMUX 1300 and UMUX 1100(E).
Because of its low throughput and the use of dedicated units, the EOC is not suited for the man-
agement communication of the current UMUX systems.
1.2.6 Signal layers
The UCST uses unified names for traffic signal layers according to the ETSI nomenclature (if ap-
plicable). The UCST and UNEM use the same terms for the same things.
For details and layer names, refer to the table below:
Introduction
Table 1-1: Traffic signal layers UCST R8B

Layer Specification
UCST R8B Signal rate Layer Description
ATM - - Functional ATM layer on the unit level
ADSL Channel variable path Unit functional layer and UNEM ADSL path interface on the unit level
ADSL Line variable section Unit functional layer and UNEM ADSL section interface
P0 64 kbit/s path UCST TDM cross connections
P0_nc n x 64 kbit/s path UCST TDM cross connections
E0 64 kbit/s section Unit functional layer and UNEM
P12 2 Mbit/s path UCST TDM cross connections
E12 2 Mbit/s section Unit functional layer and UNEM
P0 … E12 - - Functional layers 64 kbit/s … 2 Mbit/s on the unit level

P22 8 Mbit/s path IF on the unit level
O22 8 Mbit/s section Unit functional layer and UNEM Physical Medium Section
P31 34 Mbit/s path IF on the unit level (FUTURE OPTION)
P32 45 Mbit/s path IF on the unit level (FUTURE OPTION)
Ethernet Phy variable section Unit functional layer and UNEM CSMACD section interface
P-DSL variable path Unit functional layer and UNEM xDSL path interface on the unit level
(can adapt to P0_nc or P12 or VC-12)
E-DSL variable section Unit functional layer and UNEM
xDSL section interface
VC variable path UCST ATM cross connections
VC-12 2 Mbit/s path UCST TDM cross connections
Virtual Container 12 of STM-1
VC-3 34 or 45 path UCST TDM cross connections
Mbit/s Virtual Container 3 of STM-1
VC-4 139 Mbit/s path Unit functional layer and UNEM
Virtual Container 4 of STM-1
VP variable path UCST ATM cross connections
Introduction
Layer Specification
UCST R8B Signal rate Layer Description
P-SHDSL variable path Unit functional layer and UNEM SHDSL path interface on the unit level
(can adapt to P0_nc or P12 or VC-12)
E-SHDSL variable section Unit functional layer and UNEM SHDSL section interface
STM-<x> MSP - section Unit functional layer and UNEM
Multiplex Section Protection of STM-4/1
STM-<x> MS - section Unit functional layer and UNEM
Multiplex Section of STM-4/1
STM-<x>- RS - section Unit functional layer and UNEM
Regenerator Section of STM-4/1
STM-<x> PMS: - section Unit functional layer and UNEM
OS Physical Medium Section of STM-4/1
ES (OS = optical, ES = electrical, STM-1 only)
Undefined - - Rate not yet defined

Unknown - - Existing rate but inherently unknown (typically serial interfaces)
The number of functional layers available depends on the selected unit and the type of configura-
tion (unit parameter, alarms).
© KEYMILE AG
2 New content
2.1 Functionality
This paragraph describes the new functionality of the UMUX and UMUX units.
For details of hardware, ESW and a short list of features please refer to chapter 4: «Summary of units».
2.1.1 R8B SP01
SYN4E
The platform R8B introduces the new SYN4E function unit, which is released with the R8B
SP01 for general deployment.
The SYN4E 610 unit provides 2 STM-4/1 and 2 STM-1 SFP based interfaces. The STM-1 inter-
faces support SPF modules with optical or electrical STM-1 interfaces. The STM-4 interfaces
support SFP modules for optical transmission. A local cross connect allows for the cross con-
nection of VC-12, VC-3 and VC-4 traffic between the local STM-x interfaces. For the traffic ac-
cess to other traffic units in the UMUX subrack the SYN4E.provides also access to the SBUS
and to the PBUS for locally terminated SDH traffic. The SYN4E unit implements also the SETS
function for the NE.
Beside the SDH interfaces, SYN4E offers also four electrical 10/100/1000BASE-T interfaces.
The SYN4E handles the encapsulation of the tributary Ethernet traffic into the SDH signals (VC-
12, VC-3 and VC-4).
Please note that the operation of the SYN4E requires a COBU<X> with R5 ESW (≥R5H).
2.1.2 R8B SP02
2.1.2.1 NEMSG
The platform R8B with the Service Pack 02 introduces the new NEMSG function unit.
Functions and systems © KEYMILE AG
The NEMSG unit has just like the NEMCA / NEMGE eight E&M voice and signalling interfaces. In
addition to this, the NEMSG provides conference circuits allowing the combination of voice and sig-
nalling information of up to 17 participants per conference. The NEMSG also supports P0 data
conferences.
These enhancements make the NEMSG unit even fitter to address multipoint network scenarios in
utilities and private networks. NEMSG is not only able to address new network topologies but of-
fers also an easier user interface to configure these functions. The functionalities of NEMSG in-
clude:
• 8 E&M interfaces with 2-wire or 4-wire voice interface
• 2 signalling interfaces per voice channel
• Support of the E&M signalling interface types I to V
• Support of different network topologies (point-to-point, point-to-multipoint, multipoint-to-
multipoint)
• 8 conference circuits with up to 17 participants per conference, maximum 32 participants per
NEMSG unit
• Equipment protection with slot switching
• Simulation of channel failure for debugging or decoupling of a faulty slave
• Unit reset button in GUI
• Using the new UCST wizard, point-to-multipoint and multipoint-to-multipoint network topologies
with «Shared Protection Ring» can be easily configured
The NEMSG is a functional replacement for the NEMCA / NEMGE units and adds with its confer-
ence features substantial new functionality to the UMUX.
2.1.2.2 NEBRE
The platform R8B with the Service Pack 02 introduces the new NEBRE function unit.
Ethernet based business services are a growing need for public and private network operators.
The UMUX module NEBRE brings wire-speed switching into the UMUX platform to address high
speed Ethernet services. The NEBRE is ideal for bandwidth intensive applications like corporate
internet access, LAN interconnections and VPNs (Virtual Private Networks). The NEBRE offers six
Ethernet interfaces to connect your customers: 4 x 10/100Base-T and 2 x SFP cages for 100Base-
FX or Gigabit Ethernet. When used in conjunction with the STM-4 unit SYN4E in the UMUX, the
NEBRE allows high flexibility in the range of Ethernet services plus the carrier grade reliability of
SDH transport.
The NEBRE is a functional replacement for the existing ETHUB unit of the UMUX. In addition to a
significantly superior Ethernet switching function, the NEBRE is also a managed solution under the
umbrella of the UCST/UNEM system.
Compatibility of the NEBRE
• Control units:
The NEBRE unit requires COBUX R3 at least. If equipment protection for the NEMSG shall be
implemented, both the COBUX ESW and the COBUX template must be R5 or higher.
2.1.2.3 DATA<X> R3
The platform R8B with the Service Pack 02 introduces the R3 of the DATA<X> function units which
provide substantial feature enhancements with respect to the DATA<X> R2. The new features are:
• Direct encapsulation of the DATA<X> Ethernet traffic for the transport via HDLC to DTM (with-
out PPP encapsulation)
• Point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) connectivity between stations
in linear networks with SPRING (Shared Protection Ring) topology.
The table below gives a synoptical overview of the full DATA<X> R3 feature set and the supported
data rates and interfaces respectively.
Table 2-1: Overview of DATA<X> features and supported data rates
1 1
Transmission User data rate Timing signal Transport mode DCE interface type P2MP/I and P2MP/S P2MP/I
mode [kbit/s] [kHz]
V.35, X.24/V.11 V.24/V.28 RS485 V.35, X.24/V.11 V.24/V.28 RS485
Transparent 2048 2048 P12 yes no no na na na
Clock master 2048 2048 P12 yes no no na na na
Terminated nx64 2048 P12 yes no no na na na
Synchronous nx64 nx64, n ≤ 31 nx64 kbit/s yes no no av na na
Synchronous nx64 nx64, n ≤ 2 nx64 kbit/s yes yes no av av na
Synchronous 48/56 48/56 Subrate yes yes no av av na
Synchronous 0.6 ... 38.4 0.6 … 38.4 Subrate yes yes no av av na
Synchronous 0.6 … 19.2 0.6 … 19.2 Subrate Mux yes yes no na na na
Asynchronous 0.6 … 38.4 0.6 … 38.4 Subrate yes yes no av av na
1 1
Transmission User data rate Timing signal Transport mode DCE interface type P2MP/I and P2MP/S P2MP/I
mode [kbit/s] [kHz]
V.35, X.24/V.11 V.24/V.28 RS485 V.35, X.24/V.11 V.24/V.28 RS485
Asynchronous 0.6 … 19.2 0.6 … 19.2 Subrate Mux yes yes no na na na

2
Oversampling 0 … 600 nx64, n ≤ 31 nx64 kbit/s yes no yes av na av
2
Oversampling 0 … 96 nx64, n ≤ 4 nx64 kbit/s yes yes yes av av av
2
Oversampling 0 … 0.3 ≤ 19.2 Subrate yes yes no av av na
na: not applicable

av: available
1
Although marked as “available”, P2MP/* cannot be activated on a path in combination with
CAS, PM TS being enabled.
2
This signal is only used internally to sample the data signal. On the DCE interface none of
timing interchange circuits will be activated.
The R3 DATAS release continues the support of scaled DATA<X> versions application optimised
feature sets. The features quoted in table 2-1 are available with unit templates (DATA<X>) and
hardware as follows:
Table 2-2: Availability of features vs. DATA<X> units
No. Short name DCE interface type Network functions
Function unit
HW unit X.24/V.11 V.35 V.24/V.28 RS485 Subrate multiplexing
1+1 linear trail protection
Performance monitoring time slot
Point to multipoint application
1 DATAS 9 9 9 9 9
2 DATA5 9 9 9 9 -
3 DATAV - 9 - - 9
4 DATA3 - 9 - - -
5 DATAR - - 9 - 9
6 DATA4 - - 9 - -
7 DATAT 9 - - - 9
8 DATA1 9 - - - -
Compatibility of the DATA<X> R3

• Hardware and features:
The DATA<X> R1A and R1B hardware do not support P2MP/I with subrates. The support of
this feature requires a DATA<X> R3 hardware. All other features are fully supported with the
R1A and R1B DATA<X> hardware.
• Hardware and ESW:
The embedded DATA<X> ESW versions R1A, R2A, R2B and R3A support all the DATA<X>
hardware versions R1A (HW key x02), R1B (HW key x02) and R3A (HW key x03) with one ex-
ception:
The hardware R3A (HW key x03) and ESW R1A are not compatible.
• Control units:
The DATA<X> R3 requires COBUX ESW R5 and COBUX templates R4 at least. If equipment
protection for the DATA<X> shall be implemented, both the COBUX ESW and the COBUX tem-
plate must be R5 or higher.
2.2 Correction of deficiencies
2.2.1 Cleared limitations
Please check the current state of identified and not yet cleared deficiencies for UMUX units and
functions in the letter of limitations in chapter 8: «Limitations».
The state of identified limitations for the UNEM management software as known at the time of the
compilation of the release note is available in the UNEM release note [NM].[152].
The release notes are updated as required to reflect the current state of identified and corrected
deficiencies.
For registered customers, up-to-date release notes for the UMUX/UCST and UNEM platform are
available for download from KEYMILE's Extranet (access via www.keymile.com).
After the login to the Extranet follow the path «Documentation & Software →UMUX/UCST → Re-
lease Information» and «Documentation & Software → UNEM → «Release Information».
2.2.2 New ESW for current function units
To eliminate identified limitations of the UMUX units and functions, updated ESW for released func-
tion units is also released asynchronously to the platform releases. To this purpose the ESW for
units as follows has been updated and released since the initial release of the UMUX / UCST R8B
package (most recent on top):
Table 2-3: ESW maintenance releases within the platform period R8B
ESW Rev. notes Correction of deficiencies Features changed with ESW
LOMIF R5C 08-06-08 No issues to fix In case of CRC BER 1E-3 an RDI is
inserted.
Protection switching between LOMIF-
terminated traffic becomes bi-directional
(SPRING applications).
Function available with UCST R8B
SP02 (and higher) only.
ISBUQ R3L 26-03-08 Several fixes for issues related to None

- Collection of performance data
- Performance monitoring
and other minor issues.
ISBUT R3L 26-03-08 Several fixes for issues related to None

- Collection of performance data
NEBRO_R2F 10-03-08 No issues related to NEBRO and NRBRA to Support of the new NEBRE unit intro-
fix duced with UMUX / UCST R8B SP02.
SYNAC R3D 11-02-08 Several fixes for issues related to None

- resilience against high traffic load
(SYNAM, SYNAD) improved
- protection switching time improved
SYN4E R1C 10-01-08 Several fixes for issues related to Synchronisation goes to free-run in-
- timing system (SETS, PETS) stead of remaining in hold-over when a
- protection switching clock source is removed.
- Interoperation with PCONV and PCON2 in
V5 mode
- inactive subunits (TIM, PBUS)
IPLMA R1G 16-11-07 Several fixes for issues related to None

- ATM-based bonding groups frozen
- Trap Log overflow
- Telenet session gets occasionally blocked
- CLI blocks occasionally
- Support of new DSP versions
- SHDSL device ID check fails
- IVM MAC address check rang to small
IPLMB R1G 16-11-07 Ditto. None
IPLMS R1G 16-11-07 Ditto None
COBUX R5H 20-07-07 Issue of not reliable SNCP cross connection None
with SYNAC solved
SYN4E R1B 19-07-07 Issue with ECC traffic delay solved None
STICx R2B 16-07-07 Several fixes for issues related to None

- Set-up of clock output on NT not properly
working
- CPE inventory blocked
- Wetting current feature not properly work-
ing
- Synch behaviour with SREG1
- Synch loss STIC<X> - DATA<X>
- Loss of data transmission after reconfigu-
ration fixed the way same as for STIM<X>
- Improvement of transmission characteris-
tics with 0.8 mm wires
- P12 transparent mode on 2 pair links not
properly working
- S/N inventory for regenerator
and other minor issues
ISBUQ R3K 20-06-07 Several fixes for issues related to None

- Loop 2 not properly working
ISBUT R3K 20-06-07 Several fixes for issues related to None

- Permanently disturbed channels with
“Festverbindungs” mode
- Activation failures
- Activation failure of U-interface with new
hardware
- Recovery time after channel reset for
“Festverbindungs” mode increased
If you need more information on the above issues, please contact your KEYMILE sales representa-
tive or KEYMILE’s customer support desk.
© KEYMILE AG
3 Summary of network elements
3.1 UMUX 1500
3.1.1 Features
The UMUX 1500 subrack is for 19-inch and ETSI rack installation with DC power supply from the
battery. The UMUX 1500 has a dual power supply option for the subrack and a fan (external fan
unit) option. Forced ventilation of the UMUX subrack is mandatory for the operation of some traffic
units and for the IP DSLAM functionality.
The UMUX 1500 subrack R2 with the FANU5 fan unit (option) has a power capacity of up to 30 A
with up to 1200 Watt of power dissipation. The DUPI4 dual power supply unit (option) is mechani-
cally integrated in the UMUX 1500 subrack R2.
The UMUX 1500 can be used to interface the UMUX Access Network to a Backbone Network. This
implies the ability to
• terminate high capacity aggregate signals (STM-1 ATM, STM-4/1 SDH) down to 64 kbit/s cir-
cuits
• provide physical user service interfaces (POTS, ISDN, data leased lines, IP traffic)
• provide transmission capability to remote systems over optical fibre and copper cables (xDSL
transmission interfaces).
• support UMUX CPE for the remote connection of service interfaces including interfaces for IP
traffic.
The UMUX 1500 offers 21 standard slots for traffic, control and power units.
The figure below shows the UMUX 1500 architecture and compatible units.
Summary of network elements © KEYMILE AG
Figure 3-1: UMUX 1500 block diagram
SYNIO SYNUF SYNIF SYNIC SYNAM SYTEL SYNOT NEBRO NEBRE ATIOP ADACA ADACS
VC-12 VC-12 VC-12 VC-12 SYNAD VC-12 NEBRA ATM ADACB
VC-3 VC-3 VC-3 VC-3 VC-12 VC-3 VC-3 VC-12/3 STM1 ATM ATM
2 x STM-1 [AD] 2) <--> 1 x STM-1 [X] 3) Sector B [OR]

4)
ATM 1215 kcells/s Sector B
SBUS ABUS
2) 3)
2 x STM-1 [AD] <--> 1 x STM-1 [X] Sector A [OR]
4)
ATM 1215 kcells/s Sector A
SYN4E (STM4) SYNAC SYNVA IPSMG ACONV

VC-4/3, VC-12 ATM
P-12, Ethernet P-12 TU-12 P-12 P-12
LOMIF TUPON PCONV PHLC SUBH NEMSG LAWA4 LEMU6 DATA

LOMI4 PCON2 <X> <X> LEMQ6 <X>
P0_nc
1)
PBUS 128 x 2 Mbit/s
DUPI4
-U1 STIC1 LESA8 SLIM1 SLIM2
Supply &
control STIC2 LESI8 SLID1 SLID2
-U2
-48 Vdc -48 Vdc

-48 Vdc
System Control Management

POSU<X> COBU<X> Alarming
POSU<X>
POSU System Control Management
POSU<X>S COBU<X>
Management Alarming
POSU<X>
Synchronisation
POSUM Synchronisation
Diagnostics
POSUS
Power PBUS Access of the
supply UBUS Synchronisation
1)
Capacity availability depends on COBU<X> con-
trol unit
2)
UBUS 8 x 2 Mbit/s
1) [AD] Add Drop connections
3)
[X] Through connections
4)
TUNxy LECA2 SIFOX MEGIF UNIDA NEMCA EXBAT EXLAx NEMCA
EXLIx lSBUQ PHOV5 Special IPLM1 IPLM6 [OR] Each section is either operated
LE2Q2 GECOD SUBAT SUBLx SULIx ISBUT PHONE units IPLM2 as S-bus or A-bus
IPLM4
Please note that the UMUX 1500 supports

• Control units
− COBUX 219/223 units (R5)
− COBUV 220/224 units (R5)
Other control units (R4 and below) do not support all traffic functions (refer to 6.3.1) and do not
allow to fully benefit from the enhanced MIB and configuration data handling provided with the
R5 control units.
• Power units (exclusively)
− POSUM 206 unit.
− POSUS 106 unit (obsolete function unit)
Power supply from mains via the POSUA power converter is not released for the UMUX 1500.
• DUPI4 dual power unit for the redundant power supply of the UMUX 1500 subrack R2. The
DUPI4 is mechanically integrated into the UMUX 1500 subrack R2 (functional supervision via
the COBU<X> interfaces for external alarms).
• FANU5 fan unit for forced subrack ventilation. The FANU5 is mechanically and functionally in-
dependent of the UMUX 1500 subrack (functional supervision via the COBU<X> interfaces for
external alarms).
• Special Units without or limited access to the UMUX internal traffic bus structures.
Among other units these are the ALCAR, ETHUB, IPLM<x>, LECAF, MAGIC, MAGI8 and
TUNOF.
• Simultaneous operation of its 2 ABUS/SBUS Sectors.
The 2 ABUS/SBUS sectors of the UMUX 1500 constitute one logical SETS system (SETS is a
NE level function). The physical SETS systems in the 2 sectors run synchronously. The SETS
system of one of the sectors is the leading Prime SETS Sector and the other sector is the
slave Agent SETS Sector. The Prime SETS Sector provides all the SETS functions and the
ESO-4 signal. The Agent SETS Sector just synchronises to the output signal of the Prime
SETG to create a synchronous signal for its sector.
It is not possible to protect the Prime SETS Sector with the Agent SETS Sector.
The sector with the first configured unit with SETS (SYN4E, SYNUF, SYNI<X>, ATIOP) be-
comes automatically the Prime SETS Sector.
3.1.2 System cores
The UMUX & UCST R8B supports the following UMUX 1500 system cores:
Table 3-1: UMUX 1500 system cores
Name KEYMILE PEC Functions
U1500-CU 11/ZFEBU 150 101 R2A UMUX 1500 R2 Core Unit including the following items:
BFDBU 101 101/1 R2A UMUX 1500 subrack R2 including
- front cover
- cable tray
- DC power cable for the subrack
- packing
FALBU 150 104/1 R1A UCST RTU (Right to Use) for the UMUX 1500.
U1500-CS …/ZFEBU 150 …. ….. UMUX 1500 Core Systems are available with different assemblies of units.
Core Systems include typically
- UMUX U1500-CU
- Control unit (COBUX, COBUV, COBUL)
- Power converter
- UCST RTU (Right to Use)
- Network management licence fee
Please contact KEYMILE for details.
U1500-AP …/ZFEBU ………. ….. UMUX 1500 Core Systems tailored to customer specific applications are
available where applicable,.
Applications include typically
- UMUX U1500-CU
- installation options
- Power converter
- additional units
U1500-SL FALBU 150 201/1 R1A UCST & UNEM RTU (Right to Use) for the UMUX 1500.
3.1.3 Auxiliary equipment
Auxiliary equipment is not directly related to the UMUX & UCST R8B release. These functions are
not configurable via the Element Managers:
Table 3-2: Auxiliary equipment

DUPI4-FU BMKBU 101 102/1 R1A DUPI4 dual power connection unit for the UMUX 1500 subrack R2.
The DUPI4 includes features as follows:
- interfaces for 2 independent battery power supply circuits for the UMUX
1500 subrack R2.
- monitoring of both supply circuits for failures
- alarm cable connection to the FANU5 or COBU<X> interfaces for exter-
nal alarms.
UMUX 1500 subracks R2 are upgradeable with DUP4 at any time.
FANU5-207 FANU5 fan unit for 19-inch rack installation:
- 10 fans (temperature controlled speed)
- interfaces for external alarms (e.g. DUPI4)
- 1 HU (44.45 mm)
Adapters for ETSI rack installation available
COZBU 102 207/1 FANU5 for operation with UMUX 1500 subrack R2 including FANU5
- power cable for the UMUX 1500 subrack R2
- alarm cable for the COBU<X>
COZBU 102 207/3 FANU5 for operation with UMUX 1500 subrack R1 without DUPOS includ-
ing FANU5
- power cable for the UMUX 1500 subrack R1
- alarm cable for the COBU<X>
(FANU5 retrofit in UMUX 1500 R1 without DUPOS)
COZBU 102 207/4 FANU5 for operation with UMUX 1500 subrack R1 with DUPOS including
FANU5
- power and alarm cable for the DUPOS (UMUX 1500 subrack R1)
(FANU5 retrofit in UMUX 1500 R1 with DUPOS)
BFD01-AC BFYBU 150 103/2 R1A Heat deflection shield for 19-inch rack installation (UMUX 1500 subrack
R2):
- operates with the FANU5 unit
- 2 HU (88.90 mm)
Adapters for ETSI rack installation available
Adapters for UMUX installation in ETSI racks:
BFD01-AC For UMUX 1500 subrack R2 and related equipment (FANU5 etc.):
BFYBU 201 106/2 R1A - 1 HU (44.45 mm) FANU5 unit only
BFYBU 201 106/3 R2A - 2 HU Heat deflection shield only
BFYBU 201 106/1 R2A - 8 HU UMUX 1500 subr./cable tray
BFYBU 201 106/6 R2A - 9 HU UMUX 1500 subr./cable tray + FANU5
BFYBU 201 106/4 R2A - 10 HU UMUX 1500 subr./cable tray + Heat defl. shield
BFYBU 201 106/7 R2A - 11 HU UMUX 1500 subr./cable tray + FANU5 +
Heat defl. shield
3.2 UMUX 1200
3.2.1 Features
The UMUX 1200 is designed for stand alone installation while still supporting 19-inch and ETSI
rack installations. It operates from standard DC power supply and provides power supply options
for AC mains power supply with battery backup. The UMUX 1200 has a dual subrack power supply
option and fan (internal fan unit) option. Forced ventilation of the UMUX subrack is mandatory for
the operation of some traffic units and for the IP DSLAM functionality. The fan unit is imperatively
required if the UMUX 1200 is operated horizontally (rack installation).
The UMUX 1200 subrack R2 with the FANU2 R2 fan unit (option) has a power capacity of up to
10 A with up to 480 Watt of power dissipation. Please not that the power capacity with the AC pow-
ering option is restricted to 2.8 A / 140 Watt.
The UMUX 1200 can be used to interface the UMUX Access Network to a Backbone Network. This
implies the ability to
• terminate high capacity aggregate signals (STM-1 ATM, STM-4/1 SDH) down to 64 kbit/s cir-
cuits
• provide physical user service interfaces (POTS, ISDN, data leased lines, IP traffic)
• provide transmission capability to remote systems over optical fibre and copper cables (xDSL
transmission interfaces).
• support UMUX CPE for the remote connection of service interfaces including interfaces for IP
traffic.
The UMUX 1200 has a compact subrack and offers 8 standard slots for traffic, control and power
units
SYNIO SYNUF SYNIF SYNIC SYNAM SYNOT SYTEL NEBRO NEBRE ATIOP ADACA ADACS
VC-12 VC-12 VC-12 SYNAD VC-12 NEBRA ATM ADACB
VC-3 VC-3 VC-3 VC-12 VC-3 VC-3 VC-12/3 STM1 ATM ATM
ABUS
2 x STM-1 [AD] 2)
<--> 1 x STM-1 [X] 3)
Sector A [OR] 4)
ATM 1215 kcells/s Sector A
SBUS
SYN4E (STM4) SYNAC SYNVA IPSMG ACONV
VC-4/3, VC-12 ATM
P-12, Ethernet P-12 TU-12 P-12 P-12
LOMIF TUPON PCONV PHLC SUBH NEMSG LAWA4 LEMU6 DATA

LOMI4 PCON2 <X> <X> LEMQ6 <X>
P0_nc
PBUS 128 x 2 Mbit/s 1)
DUPOS
Supply &
STIC2 LESI8 SLID1 SLID2
-U2 control
-48 Vdc
-48 Vdc
-48 Vdc

COBU<X> Alarming
-48 Vdc
POSU<X> COBU<X>
Management Alarming
POSU<X>
POSUA Synchronisation
Mains Diagnostics
POSUS
115 / 230 Vac PBUS Access of the
Power
supply UBUS Synchronisation
1)
Capacity availability depends on COBU<X>
control unit
2)
[AD] Add Drop connections
UBUS 8 x 2 Mbit/s
1)
3)
4)
[OR] Each section is either operated
TUNxy LECA2 SIFOX MEGIF UNIDA NEMCA EXBAT EXLAx EXLIx
NEMCA lSBUQ PHOV5 Special IPLM1 IPLM6 as S-bus or A-bus
LE2Q2 GECOD SUBAT SUBLx SULIx ISBUT PHONE units IPLM2 5)
IPLM4 The 6 slots available for traffic units in the
UMUX 1200 subrack do normally not require

• Control units
− COBUV 220/224 units (R5)
R5 control units.
− POSUM 206 unit.
• POSUA AC/DC power supply unit (limited to 2.8 A / 140 Watt).

• FANU2 fan unit (optional) for forced subrack ventilation. The FANU2 is mechanically and func-
tionally integrated in the UMUX 1200 subrack.
• Special Units without or limited access to the UMUX internal traffic bus structures.
Among other units these are the ALCAR, ETHUB, LECAF, MAGIC, MAGI8 and TUNOF.
The UMUX 1500 and UMUX 1200 have the following main differences:
• UMUX 1200 provides a maximum of 6 slots for traffic units.
• UMUX 1200 has only 1 SBUS Sector.
• FANU2 fan unit is proprietary for the UMUX 1200 subrack
• POSUA is only released for the UMUX 1200.
3.2.2 System cores
U1200-CU 11/ZFEBU 120 106 R2A UMUX 1200 R2 Core Unit for
- horizontal 19-inch rack installation
- DC powering
including the following items:
BFDBU 101 102/1 R2A UMUX 1200 basic subrack R2 including:
- front cover
- packing

BFYBU 201 104/2 R1A 19-inch installation set (cable tray)
1/COZBU 102 209/1 R2A FANU2 R2 fan unit
TSRBU 101 191/3 R1B DC power cable for the subrack
U1200-CU 11/ZFEBU 120 109 R2A UMUX 1200 R2 Core Unit for
- AC powering
BFDBU 101 102/1 R2A UMUX 1200 basic subrack R2 including:
- front cover
- packing
BFYBU 201 104/2 R1A 19-inch installation set (cable tray)
1/COZBU 102 209/1 R2A FANU2 R2 fan unit
TSRBU 101 220/3000 R1A Mains power cable for the POSUA
U1200-CU 11/ZFEBU 120 …. The above UMUX 1200 Core Units are 2 examples of U1200-Cus. Various
U1200-Cus are available for the different UMUX 1200 installation options.
U1200-CS …/ZFEBU 120 …. ….. UMUX 1200 Core Systems are available with different assemblies of units.
- UMUX1200-CU
- Power converter
U1200-AP …/ZFEBU 120 ……. ….. UMUX 1200 Core Systems tailored to customer specific applications are
available where applicable:
Applications include typically
- UMUX U1200-CU
- Power converter
- additional units
U1200-SL FALBU 150 202/1 R1A UCST & UNEM RTU (Right to Use) for the UMUX 1200 or UMUX 900.
DUPOS-FU BMKBU 101 101/1 R1C DUPOS connection box for dual power supply circuits with UMUX 1200
and UMUX 900.
The DUPOS includes features as follows:
- connection points for 2 independent battery power supply circuits for the
UMUX
- cable connections to the COBU<X> interfaces for external alarms.
UMUX 1200 and 900 subracks are upgradeable with DUPOS at any time.
BFD01-SE UMUX 1200:
BFYBU 201 108/1 R1A - 4 HU
FANU2 209 COZBU 102 209/1 R2A FANU2 R2 fan unit
BFD01-SE BFYBU 401 109/1 R1A Air filter set for UMUX 1200
BATMO-SE BFYBU 401 104/1 R1A Battery module for the battery backup with the POSUA (UMUX 1200
only!).
The batteries are not included with the BATMO package.
3.3 UMUX 900
3.3.1 Features
The UMUX 900 is designed for the installation in slim racks while still supporting 19-inch and ETSI
rack installations. It operates from standard DC power supply only. The UMUX 900 has a dual
subrack power supply option and fan (internal fan unit) option. Forced ventilation of the UMUX
subrack is mandatory for the operation of some traffic. The fan unit is imperatively required if the
UMUX 900 is operated horizontally (rack installation).
The UMUX 900 can be used to interface dedicated services to a Backbone Network. Accordingly,
the UMUX 900 has the ability to terminate high capacity aggregate signals (STM-1 ATM, STM-4/1
SDH) down to 64 kbit/s circuits. With a subset of released traffic units it provides physical user in-
terfaces (data, data leased lines) and xDSL and optical transmission interfaces and supports
UMUX CPE for the remote connection of service interfaces including interfaces for IP traffic.
The UMUX 900 has 6 standard slots for traffic, control and power units.
SYNIO SYNUF SYNIF SYNIC SYNAM SYNOT SYTEL NEBRO NEBRE ATIOP ADACA ADACS
VC-12 VC-12 VC-12 VC-12 SYNAD VC-12 NEBRA ATM ADACB
VC-3 VC-3 VC-3 VC-3 VC-12 VC-3 VC-3 VC-12/3 STM1 ATM ATM
ABUS
2) 3) [OR] 4)
2 x STM-1 [AD] <--> 1 x STM-1 [X] Sector A ATM 1215 kcells/s Sector A
SBUS
SYN4E (STM4) SYNAC SYNVA ACONV
VC-4/3, VC-12 ATM
P-12, Ethernet P-12 TU-12 P-12
LOMIF TUPON
LOMI4
PBUS 128 x 2 Mbit/s
DUPOS
Supply & STIC2 LESI8 SLID1 SLID2
-U2 control
-48 Vdc
-48 Vdc
-48 Vdc

COBUX
5)
Management Alarming
POSUS Diagnostics
Power PBUS Access of the
1)
supply UBUS Synchronisation Use of the UBUS depends on units released for
the UMUX 900
2)
[AD] Add Drop connections
3)
4)
[OR] Each section is either operated
UBUS 8 x 2 Mbit/s 1)
as SBUS or ABUS
5)
The subrack has 4 slots for traffic units. 1 PO-
Special SUS/POSUM unit provides enough power for all
units
applications.

• Control units
R5 control units.
− POSUM 206 unit.
Power supply from mains via the POSUA power converter is not released for the UMUX 900.
• FANU3 fan unit (optional) for forced subrack ventilation. The FANU3 is mechanically and func-
tionally integrated in the UMUX 900 subrack.
The UMUX 1500 and UMUX 900 have the following main differences:
• UMUX 900 provides a maximum of 4 slots for traffic units.
• UMUX 900 does not support equipment protection of the control unit.
• UMUX 900 has only 1 SBUS Sector.
• UMUX 900 supports a subset of all the traffic units that are released for the UMUX 1500.
• FANU3 fan unit is proprietary for the UMUX 900 subrack.
3.3.2 System cores
U900-CU 11/ZFEBU 090 101 R1A UMUX 900 Core Unit for
- DC powering
BFDBU 101 107/1 R1A UMUX 900 basic subrack including:
- front cover
- packing
1/COZBU 102 210/1 R1A FANU3 fan unit

U900-CU 11/ZFEBU 090 102 R1A UMUX 900 Core Unit for
- vertical installation
- DC powering
BFDBU 101 107/1 R1A UMUX 900 basic subrack including:
- front cover
- packing
BFYBU 201 102/1 R1A Dummy bezel
U900-CS 1/ZFEBU 090 … … UMUX 900 Core Systems are available with different assemblies of units.
- UMUX U900-CU
- Control unit COBUX
- Power converter
U1200-SL FALBU 150 202/1 R1A UCST & UNEM RTU (Right to Use) for the UMUX 1200 or UMUX 900.
DUPOS-FU BMKBU 101 101/1 R1C DUPOS connection box for dual power supply circuits with UMUX 1200
and UMUX 900.
The DUPOS includes features as follows:
- connection points for 2 independent battery power supply circuits for the
UMUX
- cable connections to the COBU<X> interfaces for external alarms.
UMUX 1200 and 900 subracks are upgradeable with DUPOS at any time.

BFD01- UMUX 900:
BFYBU 201 103/1 R1A - 3 HU
FANU3 210 COZBU 102 210/1 R2A FANU3 R2 fan unit
3.4 Patch panels
Patch panels are not UCST relevant but hardware oriented.

19-inch patch panel for Cable Modules with 75 Ohm connectors:
1/BGKBU 202 101/2 R1A - 2 HU (44.45 mm) for up to 4 single height Connector Modules
1/BGKBU 202 104/1 R1B - 1 HU (44.45 mm) for up to 4 single height Connector Modules
Connector Modules:
- 1 single height (1 HU) Connector Module:
- TSRBU 102 214/<m> - LOMIF/LOMI4/SYNAM (Minicoax)
- TSRBU 102 208/<m> - LOMIF/LOMI4/SYNAM (BT43)
- 2 single height (1 HU) Connector Modules:
- TSRBU 102 194/<m> - SYNAD (Minicoax)
- TSRBU 102 196/<m> - SYNAD (BT43)
- 1 double height (2 HU) Connector Module:
- TSRBU 102 209/<m> - LOMIF/LOMI4/SYNAM (BNC)
- 2 double height (2 HU) Connector Modules:
- TSRBU 102 193/<m> - SYNAD (BNC)
3.5 Legacy equipment
Please note that the UCST R8B is backward compatible within the UMUX and DSL System plat-
form and still supports the legacy system members of the UMUX and DSL System platforms:
• UMUX 1300 (CENCA)
• UMUX 1100(E) (CENCA)
• DSL System (SUCO2)
• Desktop units
© KEYMILE AG
4 Summary of units
4.1 Control, power and fan units
4.1.1 Control units
Table 4-1: Preferred functions of control units and compatible hardware/software

UMUX (UCST R8B SP02)
Functions Unit hardware PEC Bootloader SW ESW Functional Description / Remarks
or APDSW or System SW
Template TIU UMUX Name Vers. HK PH Name Vers. Name Vers.
COBUX R5C 1500 ROFBU 367 103/1 R2A 103 8 BCOBU R2A06 COBUX R5H.. Control Unit for the UMUX 1500/1200 and 900.
212 1200 - supports all the PDH and SDH functionalities
900 - access to 8 UBUS Hwys
- support of 128 PBUS Hwys
- supports remote units with CPE-rcu files
TCP/IP tunnelling, Q1-master IF
ECC, diagnostics.
ROFBU 367 103/1 R2B 105 BCOBU R2B01 Ditto plus symmetrical Ifs for the ESI-1 and ESO-4.
ROFBU 367 103/1 R2C 107 Ditto.
COBUX R5C 1500 ROFBU 367 103/1 R2A 103 8 BCOBU R2A06 COBUX R5H.. Control Unit for the UMUX 1500/1200 and 900.
ECC, diagnostics.
Summary of units © KEYMILE AG


COBUX R6A 1500 ROFBU 367 103/1 R2A 103 8 BCOBU R2A06 COBUX R5H.. New Control Unit for the UMUX 1500/1200 and 900.
219 1200 - supports all the PDH, SDH and ATM functionalities
- support of compressed MIB
ECC, diagnostics.
COBUX R6A 1500 ROFBU 367 103/1 R2A 103 8 BCOBU R2A06 COBUX R5H.. New Control Unit for the UMUX 1500/1200 and 900.
ECC, diagnostics.
COBUV R5C 1500 ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R5H.. Control Unit UMUX 1500/1200
- access to 8 UBUS Hwys
ECC, diagnostics and conference function, symmetrical Ifs for the ESI-1 and ESO-4.
ROFBU 367 103/2 R1B 207 Ditto.
COBUV R5C 1500 ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R5H.. Control Unit UMUX 1500/1200


COBUV R6A 1500 ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R5H.. New Control Unit UMUX 1500/1200
COBUV R6A 1500 ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R5H.. New Control Unit UMUX 1500/1200
COBUL R5C 1500 ROFBU 367 215/1 R1A 403 4 BCOBU R2A06 COBUX R5H.. Control Unit UMUX 1500/1200
216 1200 - supports PDH functionalities
- access to 4 UBUS Hwy.s
- support of 128 PBUS Hwy.s
Ethernet IF, F-, Q1- and Q1-master IF.
All synchronisation interfaces are 75 Ohm impedance.
ROFBU 367 215/1 R1B 407 BCOBU R2B01 COBUX R5H.. Ditto.
ESI-1 provides additionally 120 Ohm impedance and ESO-1 has galvanic isolation.
Please note that:

• Empty fields are «not applicable» for the corresponding function.
• The «Bootloader» software is included in the table. The data is readable with the in-
ventory function of the EM.
• You can compose the name of the files with compressed unit software (ESW) by compos-
ing the expressions from the columns «Name» and «Version» as follows (example):
«Name»: COBUX
«Version»: R5F02
«Filename»: COBUX_R5.F02
4.1.2 Power units
Table 4-2: Preferred functions of power units and compatible hardware

POSUM R5B 1500 COZBU 110 306/1 1 - - - - DC/DC power converter for UMUX 1500 / 1200
306 1200 R1B Vin –48/-60 V, Pmax. 85 W
900
POSUA R4E 1200 COZBU 110 206/1 R1A 1 - - - - - Power converter unit for the UMUX 1200. POSUA provides:
206 - AC/DC power conversion to the primary voltage (-48 VDC) and charging (tempera-
ture controlled) of the external backup battery (with the BATMO option)
VIN = 110/230 VAC
PMAX = 140 W
- DC/DC power conversion for the secondary power supply
+IMAX = 16 A (+5 VDC)
-IMAX = 1 A (-5 VDC)
Please note that empty fields are «not applicable» for the corresponding function:
4.1.3 Fan units
Table 4-3: Preferred functions of fan units and compatible hardware

Template TIU UMUX Name Vers. HK PH Name Ver- Name Vers.
sion
FANU2 R4E 1200 COZBU 102 209/1 R1A 1 - - - - - Fan unit for the UMUX 1200.
209 Integrated in the UMUX subrack
FANU3 R5C 900 COZBU 102 210/1 R1A 1 - - - - - Fan unit for the UMUX 900.
210 Integrated in the UMUX subrack
- n.a. 1500 COZBU 102 207/1 - - - - - - Note: The FANU5 fan unit for the UMUX 1500 is independent of the UMUX 1500
subrack and is no manageable object of the UCST. Accordingly, the
FANU5 has no UCST template (functional supervision via the COBU<X> in-
terface for external alarms).
Please note that empty fields are «not applicable» for the corresponding function:
4.2 ABUS units
Table 4-4: Preferred functions of ABUS units and compatible hardware/software

Functions Unit hardware PEC Bootloader Unit Software Functional Description / Remarks
Software ESW
ACONV R6A 1500 ROFBU 367 751/1 R1A 2 16 BTLP3 R1A08 ACONV R1D.. Traffic processing unit for ATM and P12 traffic providing
751 1200 - CES 2 Mbit/s (Circuit Emulation Service for Unstructured Data Transfer) for up to
900 16 CES instances (reduced functionality only 8 CES instances).
- Support of the same P12 layer features (CES) as the LOMIF.
- IMA (Inverse Multiplexing for ATM) functionality for up to 14 instances:
- IMA-1: Premium IMA service class
- IMA-2 … 14: Regular IMA
service class
(full functionality licence only)
- Synchronous, adaptive and SRTS synchronisation for P12 traffic (IMA).
- 16 x P12 PBUS access for CES and IMA.
- ABUS master capability
- Support of ECC over ATM (IMA)
Note: The compatibilities of the UCST template with the unit hardware and ESW
apply for the full and reduced functionality ACONV licence.
ROFBU 367 751/1 R1B 01003 Ditto but with IMA support as follows:
- Premium IMA service class
for all IMA groups (IMA-1 … 14)
Note: Same ACONV licensing.
ADACA R6A 1500 ROFBU 367 738/1 R1A 1 - BTLP3 R1A08 ADACX R1C.. Unit with ADSL interfaces and access to the ABUS providing
738 SP01 1200 - 16 subunits (ADSL ports)
900 - DMT (ITU-T G.992.1) line code
- Transport of ATM cells via ADSL
- 8064 kbit/s downstream and 1024 kbit/s upstream
- Support of parameter Profiles
- Compatible with ADSL modems that comply with ITU-T G.992.1.
- Operation with splitter for simultaneous ADSL and POTS service via the same
pair.
- ATM QoS classes:
CBR, UBR, rt-VBR, nrt-VBR
- Up to 10 VCs per ADSL port
ROFBU 367 738/1 R2A 02002 B82xx R1B05 Ditto.
Software ESW
ADACB R6A 1500 ROFBU 367 738/2 R1A 101 - BTLP3 R1A08 ADACX R1C.. Same as ADACA 738 but
739 SP01 1200 - Operation with splitter for simultaneous ADSL and ISDN-BA service via the same
900 pair.
Note: The ESW ADACX_R1.B.. is not released for ADACB!
ROFBU 367 738/2 R2A 02102 B82xx R1B05 Ditto.
ADACS R6B 1500 ROFBU 367 738/3 R1B 02201 - B82xx R1B05 ADACS R1B.. Unit with SHDSL interfaces and access to the ABUS providing
740 1200
- 16 subunits (SHDSL ports)
900
- PAM-16 (ITU-T G.991.2) line code
- Transport of ATM cells via SHDSL
- Symmetrical bit rates for up- and downstream with up to
- 2320 kbit/s
- 4640 kbit/s (with pair bonding)
- Support of parameter Profiles
- Compatible with SHDSL modems (IADs) that comply with ITU-T G.991.2.
- ATM QoS classes:
CBR, UBR, rt-VBR, nrt-VBR
- Up to 10 VCs per SHDSL port
Note: Simultaneous operation for SHDSL and POTS service via the same pair is
not possible.
ATIOP R6A 1500 ROFBU 367 731/1 R1A 1 - BTLP3 R1A08 ATIOP R1F.. STM-1 aggregate interface for ATM traffic providing
731 SP01 1200 - 1 optical STM-1 IF S1.1 (L1.1 or L1.2)
900 - ABUS access
- Multiplexing of ATM cells into the VC-4
- SETS function
- SETS equipment protection.
- Supports additionally the simultaneous operation of 2 ABUS/SBUS Sectors
(UMUX 1500)
- ABUS master capability
- Support of ECC over ATM
ROFBU 367 731/2 R1A Ditto but
- 1 optical STM-1 IF L1.1
ROFBU 367 731/1 R1B 01002 Ditto (1 optical STM-1 IF S1.1)
ROFBU 367 731/2 R1B Ditto but
ROFBU 367 731/3 R1B Ditto but
ROFBU 367 704/1 R1A 04003 B82xx R1E01 Ditto.
Software ESW
IPSMG R7B 1500 ROFBU 367 702/1 R1B/3 01002 16 BTLP3 R1A08 IPSMG R3B.. Access Gateway unit for telephony NGN supporting PSTN and ISDN-BA user ports.
706 1200 - TDM to RTP (UDP/IP)
- H.248 / MEGACO protocol for TDM/IP channel set-up/release
- PSTN signalling conversion in H.248 messages
- Voice modem ITU-T G.711, 64 kbit/s, A-law
- 64 kbit/s clear channel (B-ch.)
- Echo cancellation ITU-T G.168 up to 64 ms tail length
- Signalling Gateway (ISDN-BA)
SIGTRAN (IUA/SCTP
- DTMF relay service according to RFC 2833
- User port access: up to 16 P12s
corresponding to 480 POTS
- Uplink interface
- H.248.1 v1
- 10BASE-T / 100BASE-TX
- Capacity (active channels/unit):
- 200 (G.711 codec)
- 10000 BHCA (< 0.04% PDR)
- Class of service: Differentiated services.
- VLAN tagging IEEE 802.1Q
- User priority IEEE 802.1p
- N+1 equipment protection
- Silence suppression for voice modem ITU-T G.711, 64 kbit/s, A-law
- Voice modem G. 729 A with silence suppression G.729 B
- Amet-package (metering) for signalling Gateway
- DTMF relay service according to RFC 2833 is de/selectable
Note: The IPSMG requires a COBUX ESW ≥ R5D
Please note that:

• Operation of the above (ABUS) units requires COBU<X> R5 units.
• The version of the «Bootloader» software is included in the table. The data is readable
with the inventory function of the EM.
• You can compose the name of the files with compressed unit software (ESW) by com-
posing the expressions from the columns «Name» and «Version» as follows (exam-
ple):
«Namew: ATIOP
«Version»: R1F10
«Filename»: ATIOP_R1.F10
4.3 PBUS units
The table below shows the preferred set of PBUS function units available with the UCST R8B.
KEYMILE recommends the use of these templates and the most recent ESW to implement the cor-
responding functions.
The UCST supports legacy function units as documented in the paragraph «Obsolete function
units».
Table 4-5: Preferred functions of PBUS units and compatible hardware/software
Software ESW
Template TIU UMUX Name Vers HK PH Name Vers. Name Vers.
DATAS R8B 1500 ROFBU 367 070/1 R1A 02002 4 BL8xx R2A00 DATAS R3A Traffic unit providing serial data interfaces with P0, P0-nc and P12 PBUS access as
522 SP02 1200 follows:
- DCE serial interfaces
- X.24/V.11
- V.35
- V.24/V.28
- RS-485 serial bus IF
- Data rates and modes
- P12 modes
(V.35, X.24/V.11 IFs only!)
- P0, P0-nc
- 4 serial front IFs (only 3 serial IFs are available if the Ethernet IF is active!)
- Simultaneous support of all IFs
(multiprotocol unit)
- Subrate multiplexing
- P0-nc path protection
- Point to multipoint
- Ethernet 10BaseT / 100Base-TX LAN interface according to IEEE Std. 802.3-
2002 (half and full duplex).
- LAN modes
- MAC bridging
- WAN
- Direct Ethernet traffic encapsulation on HDLC (no PPP encapsulation)
- Point-to-multipoint (P2MP) connectivity in linear networks with SPRING (Shared
Protection Ring) topology (no support of subrates with HW R1A, R1B)
Note: The DATAS requires a COBUX ESW ≥ R5 and COBUX template ≥ R4
COBUX ESW and template ≥ R5 are required for DATAS EQP.
ROFBU 367 070/1 R1B 03002 4 BL8xx R2B00 Ditto.
Software ESW

ROFBU 367 070/1 R3A 05003 4 BL8xx R2C00 Ditto.
The R3A hardware supports additionally P2MP/I with subrates.
DATAV ROFBU 367 070/3 R1A 02202 BL8xx R2A00 Same as DATAS (HW R1A), with exceptions for the support of serial interfaces as
524 follows:
The DATAV supports 4 serial V.35 DCE IFs (single protocol unit).
ROFBU 367 070/3 R1B 03202 BL8xx R2B00 Ditto.
ROFBU 367 070/3 R3A 05203 BL8xx R2C00 Ditto.
DATAR ROFBU 367 070/5 R1A 02402 BL8xx R2A00 Same as DATAS (HW R1A), with exceptions for the support of serial interfaces as
526 follows:
The DATAR supports 4 serial V.24 / V.28 DCE IFs (single protocol unit).
DATAT ROFBU 367 070/7 R1A 02602 BL8xx R2A00 Same as DATAS (HW R1A) with exceptions for the support of serial interfaces as
528 follows:
The DATAT supports 4 serial X.24 / V.11 DCE IFs (single protocol unit).
DATA5 ROFBU 367 070/2 R1A 02102 BL8xx R2A00 Traffic unit providing serial data interfaces with P0, P0-nc and P12 PBUS access as
523 follows:
- DCE interfaces
- X.24/V.11
- V.35
- V.24/V.28
- RS-485 serial bus IF
- Data rates and modes
- P12 modes
(V.35, X.24/V.11 IFs only!)
- P0, P0-nc
- 4 serial front IFs (only 3 serial IFs are available if the Ethernet IF is active!)
- Simultaneous support of all IFs
(multiprotocol unit)
- Ethernet 10BaseT / 100Base-TX LAN interface according to IEEE Std. 802.3-
2002 (half and full duplex).
- LAN modes
- MAC bridging
- WAN
- Direct Ethernet traffic encapsulation on HDLC (no PPP encapsulation)
Software ESW
Note: The DATA5 requires a COBUX ESW ≥ R5 and COBUX template ≥ R4

COBUX ESW and template ≥ R5 are required for DATAS EQP.
DATA3 ROFBU 367 070/4 R1A 02302 BL8xx R2A00 Same as DATA5 (HW R1A), with exceptions for the support of serial interfaces as
525 follows:
The DATA3 supports 4 serial V.35 DCE IFs (single protocol unit).
527 follows:
The DATA4 supports 4 serial V.24 / V.28 DCE IFs (single protocol unit).
529 follows:
The DATA1 supports 4 serial X.24 / V.11 DCE IFs (single protocol unit).
LAWA4 R5C 1500 ROFBU 367 135/1 R1A 1 8 BLEMU R1A01 LAWA4 R4E.. Connects a local area network (LAN) over a 10BaseT interface to the UMUX units
265 SP03 1200 with aggregate interfaces.
- Flexible Layer 2 or 3 IP concentration
- Cascadable over the UMUX internal cross connect
- Frame Relay FRAD functionality
- Static routing
- Supported routing protocol: OSPF2 (optional)
- Supports port-based and circuit based VLANs
- Spanning Tree Protocol
- Hardware prepared for NAT and for Voice over IP applications
- Filters for IP traffic
- Handling of Quality of Service for IP packets via process on LAWA4 and MUSIC
100 (R4C).
LEMU6 R5C 1500 ROFBU 367 134/1 R1A 2 8 BLEMU R1A01 LEMU6 R4E.. xDSL multi-user unit that concentrates the xDSL IP-packed oriented traffic of 6
266 SP03 1200 subscribers and transfers it to the local 10BaseT front interface or to the PBUS
cross connect.
The LEMU6 uses CAP encoding and provides:
- Bridging, with diverse sub modes
- IP static routing
Software ESW

- IP OSPF V2 dynamic routing
- Unnumbered IP links on DSL and PBUS interfaces
- Spanning Tree Protocol
- Frame Relay FRAD functionality
- DHCP relay configurable for MUSIC 100
- IP managed bridge configurable for MUSIC 100.
- Filters for IP traffic
- Handling of Quality of Service for IP packets via process on LAWA4 and MUSIC
100 (R4C).
LESA8 R5B 1500 ROFBU 367 161/1 R1A/A 203 8 BLESA R1B00 LESAC R2D.. xDSL unit with 8 x 2 Mbit/s PBUS access and
086 1200 - 8 DSL services via 1 pair
900 - 4 DSL services via 2 pairs
- a mixture of the above
- nx64 kbit/s and P12
- Operation with CAP regenerator (1168 kbit/s)
- SW download for the MUSIC 200.
No remote powering
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
ROFBU 367 161/1 R1B 202 LESAE R2D.. Ditto with line code / speed
R1C - 2B1Q: 1168 kbit/s
R1D - PAM16: 2320 kbit/s
LESAF R2D.. Ditto with line code / speed
- PAM16: 1168 kbit/s
Software ESW

LESI8 092 R5C 1500 ROFBU 367 161/1 1A/A 203 8 BLESA R1B00 LESIC R1D.. Same as LESA8 086.
SP05 1200 The LESI8 092 supports additionally:
900
- nx64 kbit/s, P12 and VC-12
- SW download for CPE remote units (e.g. MUSIC 200).
- operation of different types of remote units within the pairs 2n-1 and 2n (n = 1, 2,
3, 4)
No remote powering
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
ROFBU 367 161/1 R1B 202 LESIF R1D.. Ditto, but with line code / speed
R1C - PAM16: 1168 kbit/s
R1D - PAM16: 2320 kbit/s
- MUSIC 710λ, MUSIC 703λ and 711λ CPEs as follows:
- 1168 kbit/s 2 links: PAM16
- 2320 kbit/s 1 link: PAM16
LOMI4 R5C 1500 ROFBU 367 152/1 R1A 101 4 B302I R1B00 LOMIF R5C.. 2 Mbit/s IF, G.703
151 SP02 1200 4 ports 120 / 75 Ohm
900 Supports the same features as the LOMIF 152
LOMIF R5C 1500 ROFBU 367 101/1 R1A 1 8 B302I R1A21 LOMIF R5C.. 2 Mbit/s IF, G.703
152 SP02 1200 8 ports 120 / 75 Ohm and
900 - P12-modes (terminated, monitored, transparent, clock master mode)
- Sa-modes (handling of TS0-bites)
- SSI, ECC, SSM G.704
- V5.X
- PRA modes
- NT1-Lease Line modes
- CRC-4 MFA Status/Maintenance functions
- PM according to ITU-T G.826
- Bi-directional protection switching (ESW ≥ R5C, UCST ≥ R8B SP02)
The LOMIF 152 supports additionally a special AIS handling (terminated mode
only) between LOMIF in the same subrack.
The R5C ESW adds bi-directional protection switching for SPRING applications.
ROFBU 367 101/1 R1B 1 8 B302I R1B00
NEMSG R8B 1500 37540009 NEMSG R1A 1 4 BL8xx R2C02 NEMSG R1A.. Voice interface unit with E&M signalling 8 ports
540 SP02 1200 - 4- and 2-wire voice interfaces selectable
- E&M and E’&M‘ signalling
- Voice level adjustment in receive and transmit direction
- Conference circuits with local and remote participants
- Point-to-point, point-to-multipoint and multipoint-to-multipoint applications
- 1+1 path protection
- Equipment protection (switching of external cabling required)
Software ESW

PCON 2 R6B 1500 ROFBU 367 115/1 R1A 103 20 B360I R1C00 PCONV R5C.. V5.x protocol processing unit for PSTN and ISDN service
170 1200 - 480 PSTN user ports
- 224 ISDN-BA user ports with
- processing of p- and f-data
- digital leased lines
- IE pulsed reversed battery
All features implemented with PCONV 149 fully comply with V5.x Edition 2:
- V5.1: EN 300 324-1 V2.1.1
- V5.2: EN 300 347-1 V2.2.2
- Identical V5 core implementation for PCONV and PCON2 (R5)
PCONV R6B 1500 ROFBU 367 108/1 P1B 2 12 B360I R1A12 PCONV R5C.. V5.x protocol processing unit for PSTN and ISDN services
149 1200 - 240 PSTN user ports
- 112 ISDN-BA user ports with
- processing of p- and f-data
- digital leased lines
- IE pulsed reversed battery
All features implemented with PCONV 149 fully comply with V5.x Edition 2:
- V5.1: EN 300 324-1 V2.1.1
- V5.2: EN 300 347-1 V2.2.2
- Identical V5 core implementation for PCONV and PCON2 (R5)
- E12/P12 traffic layer same as LOMIF/LOMI4 R4 (LOMIF 159, LOMI4 159).
ROFBU 367 108/1 R1A 2 12 B360I R1B00 Ditto
ROFBU 367 108/1 R1A/1 3 12 B360I R1C00 Ditto
R1B
R2A
PHLC1 R5C 1500 ROFBU 367 107/1 R1B 2 4 B302I R1A21 PHLC1 R5C.. Unit with subscriber line IFs as follows:
183 SP03 1200 - 60 a/b-wire PSTN interfaces
- Configurable parameters common for all user ports (voice impedance, ringing
frequency, metering pulse, parameters for the subscriber line test)
- 1 provisioning set for all user ports (V5.x, MCAS Direct Line, Carrier adapter,
Phone Exchange modes, loop current)
- Input and output levels configurable per user port
- Application of subscriber line test is configurable per user port
- Maintenance functions (manual testing, test results, operational state, shut-
down/lock user ports etc.)
- Thermal management and overload protection
- - The new MCAS modes:
- Loop Calling PBX
- Earth Calling PBX
- PBX Extension
- 2 provisioning set for all user ports (V5.x, MCAS Direct Line, Carrier adapter,
Phone Exchange modes, loop current)
Ring over b-wire.
Software ESW

ROFBU 367 107/2 R1B 3 Ditto but ring over b-wire with earth back
1B/A
ROFBU 367 107/1 R1B 5 Ditto ring over b-wire
R1D New unit HW/ESW
ROFBU 367 107/2 R1B 6 Ditto but ring over b-wire with earth back.
R1D New unit HW/ESW.
PHLC2 R5C 1500 ROFBU 367 128/1 R1A 2 4 B302I R1A21 PHLC1 R5C.. Unit with subscriber line IFs as follows:
184 SP03 1200 - 30 a/b-wire PSTN interfaces
- other features are the same as PHLC1 183
Ring over b-wire
ROFBU 367 128/2 R1A 3 Ditto ring over b-wire with earth back
R1C New unit HW/ESW
ROFBU 367 128/2 R1B 6 Ditto but ring over b-wire with earth back.
R1C New unit HW/ESW.
PHLC3 R5B 1500 ROFBU 367 126/1 R1A 2 4 B302I R1A21 PHLC1 R5C.. Unit with subscriber line IFs as follows:
127 1200 - 10 a/b-wire PSTN interfaces
- 2 provisioning set for user ports
- V5.x, multiple MCAS,
Carrier adapter,
Phone Exchange and
multiple Phone-Phone modes
- loop current
- parameters depending on
selected mode
- provisioning set selectable per user port
- other features are the same as PHLC1 183
Ring over b-wire
New unit HW/ESW
ROFBU 367 126/2 R1A 6 Ditto but ring over b-wire with earth back.
SLID1 493 R5C 1500 ROFBU 367 491/1 R1A 102 4 BSLIM R1A01 SLIDC R1D.. Same as SLIM1 491.
SP05 1200 The SLID1 493 supports additionally:
900
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
SLIDF R1D.. Ditto, but with line code / speed
Software ESW

SLID2 494 R5C 1500 ROFBU 367 492/1 R1A 202 BSLIM R1A01 SLIDC R1D.. Same as SLIM1 491.
SP05 1200 The SLID2 494 supports additionally:
900
- remote powering for the remote equipment (CAP only!).
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
SLIDF R1D.. Ditto, but with line code / speed
SLIM1 R5B 1500 ROFBU 367 491/1 R1A 102 4 BSLIM R1A01 SLIMC R2D.. xDSL unit with 4 x 2 Mbit/s PBUS access and
491 1200 - 2 DSL services via 1 pair
- n x 64 kbit/s, P12
- SW download for the MUSIC 200
- clock backup if the COBUX<X> fails
The SLIM1 provides no remote powering for remote equipment.
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
SLIM2 R5C 1500 ROFBU 367 492/1 R1A 202 BSLIM R1A01 SLIMC R2D.. Same as SLIM1 491.
492 1200 The SLIM2 492 supports additionally:
900
- remote powering for the remote equipment.
Line code / speed
- CAP: 1168 kbit/s
- CAP: 2320 kbit/s
STIC1 R7B 1500 ROFBU 367 200/1 R1A 02002 8 BL8xx R2A00 STICX R2B.. xDSL unit with 8 x 2 Mbit/s PBUS access and
257 SP02 1200 - 8 DSL services via 1 pair
- nx64 kbit/s, P12
- SW download for CPE remote units (e.g. Line Runner DTM).
- wetting current for line IFs
- operation of different types of remote units within the pairs 2n-1 and 2n (n = 1, 2,
3, 4)
- Partial operation for 2-pair trunk connection (continued transmission of first half of
Software ESW

timeslots on failure of one pair)
- Operation with regenerators (1 or 2 pairs) if locally powered
No remote powering
The STICX R2B fixes some bugs of the R2A ESW.
Line code / speed
- TC 16-PAM: 192 ...2048 kbit/s
STIC2 R7B 1500 ROFBU 367 200/2 R1A 02102 Ditto but with remote powering.
256 SP02 1200 - Operation with regenerators (1 or 2 pairs) remotely powered
900
SUBH1 R6B 1500 ROFBU 367 187/2 R1A 03101 1 BL8xx R1C00 SUBHX R2B.. Unit with subscriber line IFs as follows:
- Configurable parameters common for all user ports (voice impedance, ringing
frequency, metering level, parameters for the subscriber line test)
- 2 provisioning sets selectable per port (V5.x, MCAS, Carrier adapter, Phone
Exchange and Phone-Phone modes, loop current)
- Configurable per user port
- provisioning set
- Input and output levels
- line echo cancellation
- channel optimisation for
modem transmission
- Balanced ringing signal superposed on a- and b-wire.
- Application of subscriber line test is configurable per user port
- Maintenance functions (manual testing, test results, operational state, shut-
down/lock user ports etc.)
- Thermal management and overload protection
- Enhanced subscriber line test
Notes: SUBH1 substitutes the PHLC 3
The SUBH1 requires a COBUX ESW ≥ R5
ROFBU 367 187/2 R1B 04101 Ditto.
SUBH3 R6B 1500 ROFBU 367 187/1 R1A 03001 1 BL8xx R1C00 SUBHX R2B.. Unit with subscriber line IFs as follows:
- other features are identical with SUBH1
Notes: SUBH3 substitutes the PHLC 1 and 2
The SUBH3 requires a COBUX ESW ≥ R5
ROFBU 367 187/1 R1B 04001 Ditto.
TUPON R5B 1500 ROFBU 367 397/1 R1A 2 4 B302S R1A03 TUPON R1B.. - Unit with optical and electrical front interfaces , PBUS access and
397 1200 - 1 optical 8 Mbit/s IF ST.1
900 (1300 nm)
- Typical optical range (single mode): 55 km
- 4 x 2 Mbit/s multiplexer
- 4 electrical 2 Mbit/s interfaces G.703 for 120 Ohm and 75 Ohm
- PBUS access: 4 x 2 Mbit/s
Software ESW

- P12 traffic signals with features and Sa-modes as LOMIF 158.
- Standalone mode of operation (operation without COBU<X> support) for local
TUPON traffic.
- Management channel 64/128 kbit/s in the optical overhead.
- The TUPON 397 optical interface is compatible with the
- TUPON 397
- TUNOR (ESW version R5B01)
Note: For the 4 x 2 Mbit/s payload, the TUPON 397 is compatible with the optical
interfaces of the legacy TUNO<X> units.
- 1 optical 8 Mbit/s IF LT.2
(1550 nm)
- Typical optical range (single mode): 70 km
Please note that:

posing the expressions from the columns «Name» and «Version» as follows (exam-
ple):
«Name»: LOMIF
«Version»: R5A10
«Filename»: LOMIF_R5.A10
4.4 SBUS units
Table 4-6: Preferred functions of SBUS units and compatible hardware/software

Software ESW
IPSMG R8A 1500 ROFBU 367 702/1 R1B/3 01002 16 BTLP3 R1A08 IPSMG R4D.. Access Gateway unit for telephony NGN supporting PSTN and ISDN-BA user ports.
707 SP01 1200 - TDM to RTP (UDP/IP)
- H.248 / MEGACO protocol for TDM/IP channel set-up/release
- PSTN signalling conversion in H.248 messages
- Voice modem ITU-T G.711, 64 kbit/s, A-law
- 64 kbit/s clear channel (B-ch.)
- Echo cancellation ITU-T G.168 up to 64 ms tail length
- Signalling Gateway (ISDN-BA)
SIGTRAN (IUA/SCTP
- DTMF relay service according to RFC 2833
- User port access: up to 16 P12s
corresponding to 480 POTS
- Uplink interface
- H.248.1 v1
- 10BASE-T / 100BASE-TX
- Capacity (active channels/unit):
- 200 (G.711 codec)
- 10000 BHCA (< 0.04% PDR)
- Class of service: Differentiated services.
- VLAN tagging IEEE 802.1Q
- User priority IEEE 802.1p
- N+1 equipment protection
- Silence suppression for voice modem ITU-T G.711, 64 kbit/s, A-law
- Voice modem G. 729 A with silence suppression G.729 B
- Amet-package (metering) for signalling Gateway
- DTMF relay service according to RFC 2833 is de/selectable
- Support ISDN PRA
- Support of MCAS
- Support of RTCP
The IPSMG R4D fixes some bugs of the previous ESW (voice quality etc.) and
provides
- soft-switch controlled fax support
- improved interoperability with soft-switches
Note: The IPSMG requires a COBUX ESW ≥ R5D
Software ESW
NEBRE R8B 1500 ROFBU 367 195/1 R1A 05104 - BL8xx R1B05 NEBRO R2F.. Managed Ethernet switch
195 SP02 1200 - 4 electrical IFs:
10BASE-T / 100BASE-TX s
- 2 optical IFs with SFP cages for 100BASE-FX / 1000BASE-SX/LX transceivers
- Ethernet bridge/switch with
- 14 ports (6 Ethernet, 8 EoS)
- Port and tag based VLAN
- Tag stacking
- RSTP
- Traffic prioritisation (QoS)
- Flow control for Ethernet IfFs
Note: The NEBRE requires a COBUX ESW ≥ R5
NEBRO R6B 1500 ROFBU 367 196/1 R1A 02001 - BL8xx R1B05 NEBRO R2F.. Encapsulation of Ethernet traffic (front interfaces) for Ethernet over SDH transport:
197 SP01 1200 - 4 electrical IFs:
900 10BASE-T / 100BASE-TX s
- 2 optical IFs with SFP cages for 100BASE-FX / 1000BASE-SX/LX transceivers
- Ethernet over SDH
- GFP according to G.7041
- VCAT at VC-12, VC-3 level
- LCAS according to G.7042
- Ethernet over SDH transport layer
- VC-12 / VC-3 transport layer with up to 63 VC-12 / 3 VC-3
- SNCP
- Ethernet bridge/switch with
- 14 ports (6 Ethernet, 8 EoS)
- Port and tag based VLAN
- Tag stacking
- RSTP
- Traffic prioritisation (QoS)
- Flow control for Ethernet Ifs
The NEBRO R2F ESW provides compatibility with the NEBREswitch functionality.
Note: The NEBRO requires a COBUX ESW ≥ R5
ROFBU 367 196/1 R1B 04003 BL8xx R1C00 Ditto with new unit HW.
ROFBU 367 196/1 R1E 05004 Ditto with new unit HW.
NEBRA R6B 1500 ROFBU 367 198/1 R1A 01002 - BL8xx R1C00 NEBRO R2F.. Same features as NEBRO but with interfaces as follows:
198 SP01 1200 - 4 optical IFs 100BASE-FX
900 - 2 optical IFs 100BASE-FX or 1000BASE-SX/LX transceivers
(all IFs are equipped with SFP cages)
The NEBRO R2F ESW provides compatibility with the NEBRE switch functionality.
Note: The NEBRO requires a COBUX ESW ≥ R5
Software ESW
SYNAC R5C 1500 ROFBU 367 113/1 R1A 3 8 B302I R1B00 SYNAC R3D.. Termination of VC-12 tributary from the SBUS and access to the 2 Mbit/s traffic on
167 1200 the PBUS.
900 - 8 subunits
- Termination of VC-12 traffic
- Identical features for the P12 traffic signal layer as LOMIF 140.
- No external interfaces
- Identical features for the P12 traffic signal layer as LOMIF 158.
i.e. PRA and Leased Line modes
(2 Mbit/s).
The R3D ESW provides improved performance and protection switching behaviour.
ROFBU 367 113/1 R1B 4 Ditto with new unit HW/ESW.
SYNAD R5B 1500 ROFBU 367 123/1 R1A 1 - B302T R1A03 SYNAC R3D.. E12 tributary interfaces for the SDH aggregate traffic providing
123 1200 - 16 electrical 2 Mbit/s interfaces ITU-T G.703 (75/120 Ohm)
900 - Mapping of the E12 tributary traffic into the VC-12 containers
- Connection of the VC-12 traffic via SBUS to the SDH aggregate traffic
- Linear Trail Protection for VC-12 traffic (SDH network)
The R3D ESW has improved performance and protection switching behaviour.
SYNAM R4D 1500 ROFBU 367 116/1 R1A 1 - B302I R1B00 SYNAC R3D.. E12 tributary interfaces for the SDH aggregate traffic providing
116 1200 R1A/1 - 8 electrical 2 Mbit/s interfaces ITU-T G.703 (75/120 Ohm)
900 - other features are the same as SYNAD 123
The R3D ESW has improved performance and protection switching behaviour.
ROFBU 367 116/1 R1B 2 Ditto with new unit HW/ESW.
SYNIC R5A 1500 ROFBU 367 118/1 R1A 1 - B360I R1D00 SYNIF R3B.. STM-1 aggregate interface for SDH aggregate traffic providing
168 1200 - 1 electrical STM-1 port
900 - aggregate SBUS access
- SETS
- SETS equipment protection.
-
ROFBU 367 118/1 R1B 2 Ditto with new unit HW.
SYNIF R5A 1500 ROFBU 367 104/1 R1A 105 - B360I R1D00 SYNIF R3B.. STM-1 aggregate interface for SDH aggregate traffic providing
604 1200 - 1 optical STM-1 port S1.1
- SETS
- SETS equipment protection
-
ROFBU 367 104/2 R1A Ditto 1 optical STM-1 port L1.1
ROFBU 367 104/3 R1A Ditto 1 optical STM-1 port L1.2
ROFBU 367 104/1 R1B 106 Ditto with new unit HW and
- 1 optical STM-1 port S1.1
ROFBU 367 104/2 R1B - 1 optical STM-1 port L1.1
ROFBU 367 104/3 R1B - 1 optical STM-1 port L1.2
Software ESW
ROFBU 367 104/1 R1C 108 Ditto with new unit HW and
- 1 optical STM-1 port S1.1
ROFBU 367 104/2 R1C - 1 optical STM-1 port L1.1
ROFBU 367 104/3 R1C - 1 optical STM-1 port L1.2
SYNIO R5A 1500 ROFBU 367 105/1 R1A 3 - B360I R1D00 SYNIF R3B.. STM-1 aggregate interface for SDH aggregate traffic providing
605 1200 - 2 optical STM-1 S1.1 interfaces
- SETS
- Multiplex Section Protection with unit IFs
ROFBU 367 105/1 R1B 5 Ditto 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1B Ditto 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1A Ditto 2 optical STM-1 ports L1.2
ROFBU 367 105/1 R1C 6 Ditto with new unit HW and
- 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1C - 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1B - 2 optical STM-1 ports L1.2
ROFBU 367 105/1 R1D 8 Ditto with new unit HW and
- 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1D - 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1C - 2 optical STM-1 ports L1.2
SYNOT R5B 1500 ROFBU 367 160/1 R1A 2 - B360I R1D00 SYNOT R1A.. STM-1 tributary interface for SDH aggregate traffic providing
160 1200 - 1 optical STM-1 S1.1 interface
900 - Termination of STM-1 tributary signal and corresponding VC-12 and/or VC-3
tributary traffic
- Connection of traffic via SBUS to the VC-12 and VC-3 aggregate traffic
- SNCP for VC-12 and VC-3 traffic (SDH network)
- Flexible allocation of bandwidth for data channels via the RS- and MS-SOH (ECC
applications)
ROFBU 367 160/2 R1A Ditto but with optical IF
- STM-1 L1.1
ROFBU 367 160/3 R1A Ditto but with optical IF
- STM-1 L1.2
SYNVA R5B 1500 ROFBU 367 119/1 P1B 1 32 B302I R1B00 SYNVA R1A.. Connection of VC-12 tributary traffic between PBUS and SDH aggregate traffic
119 1200 R1A - 32 subunits per unit
900 - Connection of VC-12 traffic from the PBUS via the SBUS to the SDH aggregate
traffic
- Support of TCM towards the SDH network including TCM maintenance functions
- VC-12 monitoring and TCM selectable per subunit
- SNCP/N for VC-12 traffic (SDH network) with individual definition of switching
criteria
Software ESW
SYNUF R7B 1500 ROFBU 367 120/1 R1A 2002 - BL8xx R2A00 SYNUF R1B.. STM-1 aggregate interface for SDH aggregate traffic providing
606 1200
- 1 SFP cage for SFP modules with optical and electrical STM-1 interfaces
900
- Support of SFP modules with diagnostics (optical IFs)
- aggregate SBUS access
- SETS
- SETS equipment protection
- MSP for the physical section with 2 SYNUF units
- Substitute for SYNIF, SYNIC and SYNIO.
Notes: The SYNUF requires a COBUX ESW ≥ R5.
KEYMILE provides a list of approved SFP modules.
SYN4E R8B 1500 ROFBU 367 610/1 R1A 2001 4 B82xx R2C00 SYN4E R1C.. STM-4/1 aggregate interfaces for SDH aggregate traffic providing
SP01 1200
- 4 SFP cages for SFP modules with optical STM-4/1 and electrical STM-1 inter-
900
faces (up to 2 STM-4 interfaces)
- Local cross connection for VC-12, VC-3 and VC-4 traffic
- SBUS access (aggregate) for local SDH traffic
- PBUS access (4 x P0/P0_nc)
- SETS with support of SETS equipment protection
- MSP for the physical sections of local STM-<x> interfaces
- Substitute for SYNIF, SYNIC, SYNIO, SYNUF and SYNAC.
- 4 Gigabit Ethernet interfaces
- Encapsulation of Ethernet traffic in VC-12, VC-3 and VC-4 containers
The SYN4E R1C fixes some bugs of the SYN4E.
Notes: The SYN4E requires a COBUX ESW ≥ R5H.
KEYMILE provides a list of approved SFP modules.
SYTEL R5B 1500 ROFBU 367 163/1 P1A 1 - B302S R1A03 SYTEL R1A.. E31 and E32 tributary interface for the SDH aggregate traffic providing
162 1200 R1A - 1 electrical E31 (34 Mbit/s) and E32 (45 Mbit/s)
900 R1B - Mapping of the E31 / E32 tributary traffic into the VC-3 container
- Connection of traffic via SBUS to the VC-3 aggregate traffic
- Linear Trail Protection for VC-3 traffic (SDH network)
- Coaxial front connectors 75 Ω (Series 1.6/5.6 ms)
Please note that:

posing the expressions from the columns «Name» and «Version» as follows (example):
«Name»: SYNIF
«Version»: R3B10
«Filename»: SYNIF_R3.B10
4.5 UBUS units
Table 4-7: Preferred functions of UBUS units and compatible hardware/software

Functions Unit hardware PEC Bootloader Unit Description / Remarks
Software Firm/Software
Template TIU UMUX Name Vers. HK Name Vers. Name Vers.
EXLA6 ≤ 2.5.d 1500 COZBU 103 352/3 R1J 6 - - EXLA6 R2F PSTN exchange line IF
352 1200 12 ports a/b, imp. 600 Ohm
1300
1100
EXLAN ≤ 2.5.d 1500 COZBU 103 342/4 R1J 7 - - EXLAN R2F PSTN exchange line IF
342 1200 12 ports a/b, complex imp.
1300
1100
EXLIC ≤ 2.5.d 1500 COZBU 103 451/4 R1C 7 - - EXLIC R1C ISDN BA exchange line IF
451 1200 12 ports, 2B1Q line code
1300
1100
GECOD ≤ 2.5.d 1500 COZBU 103 371/5 R1C 7 - - GECOD R1B Data IF 64 kbit/s G.703, co-directional
371 1200 8 ports
1300
1100
GECOD ≤ 2.5.d 1500 COZBU 103 372/2 R1B 7 - - GECOD R2A Ditto plus
372 1200 1+1 protection
1300
1100
ISBUQ R4E 1500 ROFBU 367 109/1 R1A/1 1 B302U R1A22 ISBUQ R3L.. Subscriber line IF ISDN BA
141 1200 96 V remote powering for NT-1:
1300 - 8 ports
1100 - 2B1Q line code
- p- and f-data
- permanent activation of digital section
- extended test and maintenance functions
Additionally:
- accelerated status functions
- alarm for active test loops
- control of the remote powering via status for test purposes
For subscribers with “Permanent activation”:
If the NT is disconnected
- the ISBUQ blocks the U-IF and sends a corresponding message to the switch.
- the ISBUQ creates a corresponding status for the U-IF.
- the PCON<X> may show an inconstant state for the interface. The PCON<X> consid-

ers the ISBUQ initiated blocking the same as a UCST controlled blocking.
This mode is required for switches which do not correctly process the NT-disconnected
status of subscribers with “Permanent activation” of the U-IF.
The ISBUQ R1K ESW fixes of previous releases.
Note: This ESW only runs on the ISBUQ hardware.
ROFBU 367 109/1 R1B 4 Ditto with new unit HW.
ISBUT R4C 1500 ROFBU 367 110/1 R1A 102 B302U R1A22 ISBUT R3L.. Subscriber line IF ISDN BA
110 1200 R1B 8 ports, 4B3T line code, 96 V remote powering for NT-1
1300 Additionally support of
1100
- p- and f-data
- permanent activation of digital section
- extended test and maintenance functions
- digital leased lines (“Standard Festverbindungs Modus”)
The ISBUT R1K ESW fixes among other bugs deficiencies of the “Festverbindungs”
mode of previous releases.
ROFBU 367 110/1 R1C 104 Ditto with new unit HW/ESW
NEMCA ≤ 2.5.d 1500 COZBU 103 311/2 R1A 6 - - NEMCA R2A Analogue telephone. IF, 2/4w
311 1200 8 ports
1300
1100
NEMCA ≤ 2.5.d 1500 COZBU 103 312/2 R1C 6 - - NEMCA R3A Ditto including 1+1 protection
312 1200
1300
1100
NEMGE ≤ 2.5.d 1500 COZBU 103 315/1 R1B 7 - - NEMGE R1A German parameter version of NEMCA
315 1200
1300
1100
PHOV5 4E 1500 COZBU 103 424/1 R1A/1 9 - - PHOV5_1 R1b Subscriber line IF ISDN BA for the P-Phone premium business telephone service:
424 1200 PHOV5_2 R1a - Six 2-wire speech interfaces over non-loaded copper wire pair
1300 - Six P-Phone 8 kHz signalling interfaces over the same pair as the speech channels
1100 - V5.2 protocol extended to support P-Phone signalling and speech paths
- Simultaneous speech and signalling transmission
- No ringer generator requirement
SULIC ≤ 2.5.d 1500 COZBU 103 391/5 R1F 7 - - SULIC R1C Trunk IF for NTU
1300
1100
SULIC ≤ 2.5.d 1500 COZBU 103 392/2 R1D 7 - - SULIC R2A Ditto including 1+1 protection
392 1200
1300
1100

SULIC ≤ 2.5.d 1500 COZBU 103 396/1 R1C 7 - - SULIC R3B Ditto including PM
396 1200
1300
1100
SULIS ≤ 2.5.d 1500 COZBU 103 393/2 R1E 7 - - SULIS R1C Trunk IF for ISDN NT1
1300
1100
UNIDA ≤ 2.5.d 1500 COZBU103431/2xx R1E 6 - - UNIDA R1G Data interface V.24 (0 … 38.4 kbit/s)
431 1200 4 ports:
1300
xx = 00 No options
1100
xx = 011+1 protection (1)
xx = 02Point-to-multipoint (2)
xx = 08Subrate multiplexer (4)
xx = 15All options (1, 2, 4)
This UNIDA 431 supports the rates
n = 1 (64 kbit/s) … 4 (256 kbit/s) to allow the implementation of the workaround for the
PM with subrate traffic signals.
Note: Do not use rates ≥ 64 kbit/s for other traffic signals!
The interface may not operate for these rates.
UNIDA ≤ 2.5.d 1500 COZBU103432/2xx R1E 6 - - UNIDA R1G Data interface n x 64 kbit/s, V.35
432 1200 (0.6 … 64 kbit/s) 4 ports:
1300 xx = 00 No options
1100 xx = 01 1+1 protection (1)
xx = 02 Point-to-multipoint (2)
xx = 04 Performance Monitoring (3) *)
xx = 08 Subrate multiplexer (4)
xx = 15 All options (1, 2, 3, 4)
UNIDA ≤ 2.5.d 1500 COZBU103433/2xx R1E 6 - - UNIDA R1G Data interface n x 64 kbit/s, V.11/X.24 (0.6 … 64 kbit/s) 4 ports:
433 1200
1100 xx = 01 1+1 protection (1)
xx = 15 All options (1, 2, 3, 4)

UNIDA ≤ 2.5.d 1500 COZBU103434/2xx R1E 6 - - UNIDA R1G Data interface n x 64 kbit/s,
434 1200 V.36/RS-449 2 ports:
1300
xx = 01 1+1 protection (1)
xx = 15 All options (1, 2, 3, 4)
UNIDA ≤ 2.5.d 1500 COZBU103435/2xx R1E 6 - - UNIDA R1G Data interface n x 64 kbit/s, V.36/V.11
435 1200 (48 … 64 kbit/s) 4 ports:
1300
xx = 01 1+1 protection (1)
xx = 15 All options (1, 2, 3, 4)
UNIDA R4C 1500 COZBU 103436/1x R1B 5 - - UNIDA R1H Data interface X.24/V.11
436 1200 4 ports
1300 without Subrate Multiplexing
1100
x= No options
x=1 1+1 protection (1)
x=2 Point-to-multipoint (2)
x=3 Performance Monitoring (3) *)
x=4 All options (1, 2, 3)
UNIDA R4C 1500 COZBU 103437/1x R1B 5 - - UNIDA R1H Data interface n x 64 kbit/s, V.35
437 1200 4 ports
1300 without Subrate Multiplexing
1100
x= No options
x=1 1+1 protection (1)
x=2 Point-to-multipoint (2)
x=4 All options (1, 2, 3)
UNIDA R4E 1500 COZBU 103438/1x R1A 5 - - UNIDA R1D Data interface X.24/V.11
438 1200 4 ports
1300
- without Subrate Multiplexing
1100
- with Scrambler (ITU-T V.38)
x= No options
x=1 Point-to-Multipoint (2)
x=3 Both options (2, 3)
Note: With the active scrambler PM is not available
*) The UNIDA supports PM only for bit rates ≥ 64 kbit/s. For bit rates < 64 kbit/s a workaround
(as described in the Letter of Limitations) is available.
Please note that:
• Partial inventory data means that the units only provide a part of the standard informa-
tion for inventory management.
• If the UMUX 1500 implementation of a particular function (unit) goes with functional
restrictions compared to the features quoted in the unit description, the table shows
the limitations.
• The tables include the version of the «Bootloader» software. The inventory function of
the EM can read the data (if applicable).
• New UBUS units and some of the existing UBUS units feature SW download as well.
• You can compose the name of the files with (compressed) unit software (ESW) by
composing the expressions from the columns «Name» and «Version» as follows (ex-
ample):
«Name»: ISBUQ
«Version»: R3E11
«Filename»: ISBUQ_R3.E11
4.6 Special units
Table 4-8: Preferred special units and compatible hardware/software

Functions Unit hardware PEC Bootloader SW ESW or Functional Description / Remarks
or APDSW System SW
ALCAR ≤ 2.5.d 1500 COZBU 103 804/1 R1B 7 - - ALCAR R1A Alarm unit with 24 binary inputs/ 4 command outputs and 4 ports for serial communication
804 1200
1300
1100
ETHUB R4E 1500 COZBU 110 194/1 R1B 1 - - - - The ETHUB is an Ethernet switch with 5 10/100BaseT interfaces (front access). The
194 1200 ETHUB provides the full UMUX inventory and alarm and Ifs.
The ETHUB 194 is included with the Service Pack 02 and provides a separate alarm for
failures of the local 3.3 VDC power supply.
IPLM1 R7B 1500 ROFBU 367 742/1 R1A 1 - - IPLMA R1G The IPLM1 unit provides an IP (Ethernet) DSLAM for the UMUX:
742 - 24 ADSL/ADSL2(+) interfaces
- Interworking functions for the termination of the ATM layer
- Adaptation of the Ethernet traffic for IP services, such as VoIP, Broadband Internet
Video on Demand (Triple Play).
- VLAN support up to 512
- 2 Gbit Ethernet uplinks (1 electrical, 1 SFP module)
- Up to 6 units in daisy chain
The IPLM<X> R1G ESW fixes some bugs of the previous version.
Note: The IPLM1 requires a COBUX ESW ≥ R5E
IPLM2 ROFBU 367 743/1 R1A - - Ditto but with 2 electrical Gbit-Ethernet front interfaces (Uplinks)
743
IPLM4 R7B ROFBU 367 753/1 R1A - - IPLMB R1G Ditto but with support of ADSL2+ over ISDN-BA (annex B).
753 SP03

or APDSW System SW
IIPLM6 R7B ROFBU 367 763/1 R1A - - IPLMS R1G Ditto but with the support of SHDSL line interfaces:
763 SP03
- 24 SHDSL line interfaces
- SHDSL support
- single pair
- G.SHDSL, ITU-T G.991.2
- G.SHDSL.bis, ITU-T G.991.2 annex F/G
- pair bonding.
- SHDSL ITU-T G.994.1 annex B
LECAF R4E 1500 COZBU 402 070/1 R2C 10 - - LECAF R6C DSL transmission IF (CAP)
070 1200 2 HDSL Ifs for twisted pairs.
1300 - Data IF with front access, no highway access
1100 - Support of LECAR
- Support of MUSIC 100
- Support of the regenerator
- Supports 120 and 75 Ohm termination.
The LECAF (COZBU … R2A) front panel is compatible with the legacy UMUX and oper-
ates in all the UMUX including the UMUX 1300/1100(E).
1500 NTMBU 201 953/6 R1B LECAF R7B Same functionality as the LECAF 070 (FW R6A), but can only be used as an NT in a
1200 (Upgrade kit only) connection to
- LESA8
- SLIM1/2
The FW R7B is only available as an upgrade kit for the LECAF and LECA2.
COZBU 402 070/1 R1A 10 - - LECAF R6A Same features as above.
Operates in the UMUX 1500 / 1200 only and is no longer available!
MAGIC ≤ 2.5.d 1500 COZBU 103 317/1 R1A - - - The MAGIC converts the E&M signalling of NEMCA to the magneto line signalling.
317 1200 - 8 magneto subscriber line interfaces
1300 - signalling conversion E&M <-> magneto line.
1100
For more information please contact KEYMILE
MAGI8 R7B 1500 COZBU 103 319/1 R1A - - - The MAGI8 converts the E&M signalling of NEMCA to the magneto line signalling.
319 SP03 1200 - 8 magneto subscriber line interfaces
- signalling conversion E&M <-> magneto line.
- Onboard generation of ringing signal.
MAGI8 is a substitute for MAGIC in the UMUX 1500 and UMUX 1200.

or APDSW System SW
TUNOF R4E 1500 COZBU 110 284/1 R2B 3 - - TUNOF R2B Optical/electrical transmission IF:
284 1200 - 1 optical 8 Mbit/s interface
1300 - 4 el. 2 Mbit/s front Ifs (G.703)
1100 - 2 to 8 Mbit/s DMX
- Front access for the 4 electrical 2 Mbit/s Ifs, 120/75 Ohm
- Overhead channel
The TUNOF (COZBU … R2A) front panel is compatible with the legacy UMUX.
With the UCST R5C and more recent UCST releases the TUNOF is supported in all the
UMUX including UMUX 1300/1100(E).
COZBU 110 284/1 R1A 3 - - TUNOF R2B Same features as above.
Operates in the UMUX 1500 / 1200 only and is no longer available!
Empty fields are «not applicable» for the corresponding function.
4.7 Obsolete function units
The UCST R8B supports the obsolete function units listed in the table below. If available, KEYMILE
recommends the upgrading of these functions to compatible preferred functions and substitutes as
shown in the previous paragraphs.
Table 4-9: Obsolete functions and templates
Function Description Preferred substitute
Template
TIU TOU UMUX
EXBAT 401 ≤ 2.5.d R5A ISDN BA exchange line IF None
8 ports, 4B3T line code
EXLAN 343 ≤ 2.5.d R5A PSTN exchange line IF, remote op. None
12 ports a/b, complex imp.
Sensitive metering detection
HIRAC 810 R4A R5B AM64/512 2B1Q None
IPSMG 704 R6B R7A Access Gateway unit for telephony NGN supporting PSTN and ISDN-BA user ports. IPSMG 706
IPSMG 707
ISBUQ 130 R4A R5A Subscriber line IF ISDN BA ISBUQ 141
8 ports, 2B1Q line code, 96 V remote powering for NT-1
LAWA4 235 R4E R6A Connects a local area network (LAN) over a 10BaseT interface to the UMUX units with aggregate interfaces LAWA4 265
LE2Q2 244 R4E R5A 2 Mbit/s transmission IF SLIM 1 491
Line IF for 2 twisted pairs with 2B1Q encoding. Supports LECAR (LESA8 086)
LECA2 050 ≤ 2.5.d R5A 2 Mbit/s transmission IF SLIM 1 491
Line IF for 2 twisted pairs with CAP encoding. Supports LECAR (LESA8 086)
LECA2 052 R3.3a R5A Ditto including SLIM 1 491
operation of LECAR and MUSIC 100 (LESA8 086)
LECA2 054 R4A R5A Ditto including SLIM 1 491
LECA2 056 R4E R5A Ditto including SLIM 1 491
LEMQ6 148 R4E R6A Concentrates the xDSL (2B1Q) IP-packed oriented traffic of 6 subscribers and transfers it to the local 10BaseT front interface or to the PBUS LEMQ6 248
cross connect.
LEMQ6 248 R5C R7A Ditto. None
SP03
LEMU6 236 R4A R6A Concentrates the xDSL (CAP) IP-packed oriented traffic of 6 subscribers and transfers it to the local 10BaseT front interface or to the PBUS LEMU6 266
cross connect.
LESA8 085 R5A R5B DSL 4-8 ports LESA8 086

Template
TIU TOU UMUX
LOMI4 150 R4E R5B 2Mbit/s Unit, 4 ports, PRA, PM LOMI4 151
LOMI4 159 R5C R6A ditto LOMI4 151
SP02
LOMIF 101 3.2.a R5A 2Mbit/s Unit, 8 ports LOMIF 152
LOMIF 120 3.3a R5A 2Mbit/s Unit, 8 ports, SNC, PM LOMIF 152
LOMIF 140 R4B R5B 2Mbit/s Unit, 8 ports, PRA, PM LOMIF 152
LOMIF 158 R5C R6A ditto LOMIF 152
SP02
LORAX 815 R4E R5B AM192/64 X50 None
MEGIF 261 ≤ 2.5.d R5A 2 x 2 Mbit/s, G.703 LOMI4 151, LOMIF 152
2 ports 75 Ohm
MEGIF 262 ≤ 2.5.d R5A Ditto including PM LOMI4 151, LOMIF 152
MEGIF 264 R4C R5A Ditto including PM and SSI-mode LOMI4 151, LOMIF 152
MEGIF 271 ≤ 2.5.d R5A 2 Mbit/s, G.703 LOMI4 151, LOMIF 152
2 ports 120 Ohm
MEGIF 272 ≤ 2.5.d R5A 2 Mbit/s, G.703 None
2 ports 120 Ohm, GWF
MEGIF 273 ≤ 2.5.d R5A 2 Mbit/s, G.703 LOMI4 151, LOMIF 152
2 ports 120 Ohm and PM
MEGIF 274 R4C R5A Ditto including PM and SSI-mode LOMI4 151, LOMIF 152
ML70A087 R5C R6A Desktop unit (MUSIC 700 λ) with G.SHDSL line interfaces and POTS and LAN interfaces ML70A091
SP03
NEBRO 196 R6B R7A Ethernet over SDH transport NEBRO 197
PCON2 115 R4A R5A V5.x 480 PSTN / 224 ISDN UP PCON2 142
PCON2 142 R4E R7A ditto PCON2 170
PCONV 121 R3D R5A V5.x 240 PSTN / 112 ISDN UP PCONV 149
PCONV 131 R4A R5A ditto PCONV 149
PCONV 143 R4E R7A ditto PCONV 149
PHLC1 122 R3D R5A PSTN 60 Sub/LT/V5/MCAS PHLC1 183, SUBH3 189
PHLC1 125 R4A R5B PSTN 60 Sub/LT/V5/MCAS/P-E/CA PHLC1 183, SUBH3 189
PHLC1 185 R5B R6A PSTN 60 Sub/LT/V5/MCAS/P-E/CA PHLC1 183, SUBH3 189
PHLC2 128 R3D R5A PSTN 30 Sub/LT/V5/MCAS PHLC2 184, SUBH3 189
PHLC2 129 R4A R5B PSTN 30 Sub/LT/V5/MCAS/P-E/CA PHLC2 184, SUBH3 189
PHLC2 186 R5B R6A PSTN 30 Sub/LT/V5/MCAS/P-E/CA PHLC2 184, SUBH3 189

Template
TIU TOU UMUX
PHLC3 126 R4E R5B PSTN 10 Sub/LT/V5/MCAS/P-E/CA PHLC3 127, SUBH1 191
PHONE 324 R3D R5B 6 Subscriber line Ifs P-Phone service PHOV5 424
(no V5 services)
PODIS 033 ≤ 2.5.d R7A Power distribution unit for the remote powering of 4 HDSL CAP desktops None
POSUS 106 3.2a R7A DC/DC power converter for UMUX 1500 / 1200 POSUM 306
RIGEN 241 ≤ 2.5.d R5A Ringing Generator f. SUB<xx> None
16 / 25 / 50 Hz, b-wire
RIGEN 251 ≤ 2.5.d R5A Ringing Generator f. SUB<xx> None
25 Hz, a-wire
SIFOX 381 ≤ 2.5.d R5A Data IF 64 kbit/s IF X.24/V.11 None
4 ports
SIFOX 382 ≤ 2.5.d R5A Ditto including 1+1 protection None
SUBAT 461 3.2a R5A Trunk IF for ISDN NT1 None
4 ports, 4B3T line code
SUBH1 188 R6B R7A PSTN 10 Sub/LT/V5/MCAS/P-E/CA SUBH1 191
SUBH3 187 R6B R7A PSTN 30 Sub/LT/V5/MCAS/P-E/CA SUBH3 189
SUBL6 327 3.3a R5A Subscriber line IF PSTN PHLC3 127, SUBH1 191
12 ports a/b, imp. 600 Ohm
hot line
SUBL6 335 R4A R5A Subscriber line IF PSTN PHLC3 127, SUBH1 191
12 ports a/b, 600 Ohm,
hot line, auto ring down
SUBLA328 3.3a R5A Subscriber line IF PSTN PHLC3 127, SUBH1 191
12 ports a/b, imp. complex, hot line
SUBLA334 R4A R5A Subscriber line IF PSTN PHLC3 127, SUBH1 191
12 ports a/b, imp. complex,
SUBLA 336 R4A R5A Subscriber line IF PSTN PHLC3 127, SUBH1 191
12 ports a/b, imp. complex,
Iloop = 44 mA
SUBUK 333 3.3a R5A Subscriber line IF (UK/LINTE) PHLC3 127, SUBH1 191
12 ports a/b, hot line
SYNAC 163 R4D R5C Termination of VC-12 tributary from the SBUS and access to the 2 Mbit/s traffic on the PBUS. SYNAC 167
8 subunits
SYNIC 118 R4D R5B STM-1, electrical 1 port, SETSP SYNIC 168
SYNIF 164 R4D R5B STM-1, optical 1 port, SETSP SYNIF 604

Template
TIU TOU UMUX
SYNIO 165 R4D R5B STM-1, optical 2 port, MSP SYNIO 605
TUNEL 481 ≤ 2.5.d R5A Electrical IF 8 Mbit/s None
2 el. ports 8 Mbit/s, G.703/75 Ohm
TUNOL 286 R5C R5C 1500 Same features as the TUNOL 299. TUPON 397
1200 Additional features:
Automatic laser shutdown/restart
Alarm for bit errors BER > 1E-9
Please note that the TUNOL 286
is an obsolete function unit.
does not operate with the TUNOR.
is not released for the UMUX 1300/1100(E)!.
TUNOL 299 ≤ 2.5.d R5A Optical/electrical transmission IF: TUPON 397
1 optical 8 Mbit/s interface
4 el. 2 Mbit/s front Ifs (G.703)
UBUS and front access for the 4 electrical 2 Mbit/s Ifs, 120/75 Ohm
2 to 8 Mbit/s DMX
Cross connect configurable
Overhead channel
TUNOP 292 ≤ 2.5.d R5A Opt. IF 8 Mbit/s single and multi-mode fibres TUPON 397
2 ports
TUNOS 293 ≤ 2.5.d R5A Opt. IF 8 Mbit/s TUPON 397
single mode fibres 1300 nm
2 ports
TUNOS 294 ≤ 2.5.d R5A Opt. IF 8 Mbit/s TUPON 397
single mode fibres 1500 nm
2 ports
ULCAS 471 R3D R5A AM 64/128 None
ULCAS 472 R4E R5B AM 64/128 None
Please note that:

• Obsolete functions are still compatible with the UCST R8B.
• The corresponding templates are available in the Obsolete directory in the UCST
Data directory.
• For information on compatibility of hardware with former ESW consult the correspond-
ing release notes.
4.8 Desktop units
Table 4-10: Interoperability and software of desktop units (UCST R8B SP02)
Functions Unit hardware PEC System SW Functional Description / Remarks
Name TIU Compatible Units TIU Name Vers. Name Vers.
LE2RG LECA2 056 R4E ZHTBU 401 019/1 R1A LE2RG R2A CAP Regenerator in aluminium outdoor box for remote powering
LECAF 070 R4E
(POSUR/PODIS
required)
SLIM2 492 R5C
SLID2 494
LE2RG LECA2 056 R4E COZBU 401 019/3 R1A LE2RG R2A CAP Regenerator subrack unit with local DC powering
LECAF 070 R4E
LESA8 085 R5A
LESA8 086 R5B
LESI8 092 R5C
SLIM1 491 R5B
SLIM2 492 R5C
SLID1 493 R5C
SLID2 494
LECAR R5A LESA8 086 COZBU 405 105/1 R1B LECA2 R7B Desktop HDSL/CAP 230 V without IF
SLIM1 491 special version for use as NT only
Supports 1-pair and 2-pair DSL operation mode
LECAR LECA2 056 R4E COZBU 405 100/1 R1C LECA2 R6A HDSL/CAP 230 V without IF
LECA2 057 R4E
LECAF 070 R4E
LECAR LE2Q2 244 R4E COZBU 405 244/1 R1B LECA2 R6A HDSL/2B1Q 230 V without IF
(LE2QR)
LECAR LECA2 056 R4E COZBU 405 101/1 R1D LECA2 R6C HDSL/CAP 115 V without IF
LECA2 057 R4E
LECAF 070 R4E
LECAR LECA2 052 3.3°/1 COZBU 405 069/1 R2E LECA2 R4.2 HDSL/CAP 230 V without IF
LECA2 053 3.3°/1 (R4C)
LECAR LECA2 052 3.3°/1 COZBU 405 068/1 R2E LECA2 R4.2 HDSL/CAP 115 V without IF
LECA2 053 3.3°/1 (R4C)
LECAR LECA2 050 2.5d/2 COZBU 405 061/1 R2C LECA2 3.1 HDSL/CAP 230 V without IF
LECA2 051
LRD1A 044 R7B STIC1 257 R7B 37 853 406 LRD1A R3C LineRunner DTM
SP02 STIC2 256 R7B - 1 pair
SREG1 081 R7B - maximum user data rate 2048 kbit/s
(SREG2 082) R7B - AC power supply

LRD1B 062 R7B STIC1 257 R7B 37 854 305 LRD1B R3C LineRunner DTM
SP02 STIC2 256 R7B - 1 pair
LRD2A 045 R7B STIC1 257 R7B 37 853 805 LRD2A R3C LineRunner DTM
SP02 STIC2256 R7B - 1 pair and 2 pairs
37 853 600 LineRunner DTM
- 1 pair and 2 pairs
- maximum user data rate 2048 kbit/s
- DC power supply
- AC power supply
- remote powering source
- DC power supply
- remote powering
MUSIC 100 R5C LECA2 056 R4E ZATBU 121 060/2 R3E _MCAP R4E MSDSL (all speeds, with LEMU6) and HDSL (with LECA2/F) CAP
MCAP LECA2 057 R4E
LECAF 070 R4E
LEMU6 236 R4E
MUSIC 100 R5C LEMU6 236 R4E ZATBU 121 060/5 R3E _LMCAP R4E LMSDSL (128/256 kbit/s) CAP
LMCAP
MUSIC 100 R5C LE2Q2 244 R4E ZATBU 121 060/8 R1E _2B1Q R4E HDSL 2B1Q
2B1Q LEMQ6 148 R4E
MUSIC 200 R5B LESA8 086 with R5B ZATBU 121 086/1 R1C LESRC R1C Supports the speed/line code
ESW LESAC - 1168 kbit/s: CAP
SLIM1 491 and R5B - 2320 kbit/s: CAP
SLIM2 492 with Power supplies 230 VAC and –48 VDC.
ESW SLIMC
LE2RG
ZATBU 121 086/21 R1B Ditto but for operation with AC power supplies only
1)
110 … 240 VAC.
MU20A 012 R5C LESI8 092 with R5C ZATBU 121 012/1 R1C MU20C R2C Power supplies 230 VAC and –48 VDC.
(MUSIC 200) SP03 ESW LESIC
SLID1 493 and R5C Supports the speed/line code

SLID2 494 with - 1168 kbit/s: CAP
ESW SLIDC - 2320 kbit/s: CAP
LE2RG
ZATBU 121 012/21 R1B Ditto but with AC power supplies only
1)
110 … 240 VAC
MUSIC 200 R5B LESA8 086 with R5B ZATBU 121 086/2 R1C LESRE R1C Supports the speed/line code
ESW LESAE - 1168 kbit/s: 2B1Q
- 2320 kbit/s: PAM16
Power supplies 230 VAC and –48 VDC.
MUSIC 200 R5B LESA8 086 with R5B ZATBU 121 086/3 R1C LESRF R1C Supports the speed/line code
ESW LESAF - 1168 kbit/s: PAM16
- 2320 kbit/s: PAM16
Power supplies 230 VAC and –48 VDC.
MU20A 012 R5C LESI8 092 with R5C ZATBU 121 012/3 R1C MU20F R2C Supports the speed/line code
(MUSIC 200) SP03 ESW LESIF - 1168 kbit/s: PAM16
SLID1 493 and R5C - 2320 kbit/s: PAM16
SLID2 494 with Power supplies 230 VAC and –48 VDC.
ESW SLIDF
ZATBU 121 012/23 R1B Ditto but for operation with AC power supplies only
1)
110 … 240 VAC.
ML70A 091 R5C LESI8 092 with R5C ZATBU 121 091/1 R1A ML700 R2C Desktop unit with G.SHDSL line interfaces and POTS and LAN interfaces:
(MUSIC 710λ) SP05 ESW LESIF - 2 DSL lines (copper pairs)
SLID1 493 and R5C - 2 independent 10BaseT / 100 BaseTx Ethernet interfaces
SLID2 494 with - routing and bridging for data traffic of the Ethernet interfaces
ESW SLIDF - 8 (indoor) POTS interfaces for telephone services
- operational parameters configurable
- general operational parameters for all user ports configurable
- voice impedance
- ringing frequency
- metering pulse
- parameters for subscriber line test
- 2 provisioning sets for all user ports
- V5.x, Carrier adapter modes
- MCAS mode Direct Line
- PHLC1 183 supports additionally new MCAS modes:
- Loop Calling PBX
- Earth Calling PBX
- PBX Extension
Phone Exchange modes
- loop current
- parameters depending on mode
- input and output levels configurable per user port
- local interface for unit configuration
- local DC (nominal 12 VDC) or mains (230 VAC) power supply

- metallic indoor case
- intelligent heat management for locally dispipated power
- 1168 kbit/s via 2 links: PAM16
- 2320 kbit/s via 1 link: PAM16
ML70C 089 R5C LESI8 092 with R5C ZATBU 121 089/1 R1A ML700 R2B Ditto.
(MUSIC 711λ) SP05 ESW LESIF The MUSIC 711λ additionally supports a serial data interface n x 64 kbit/s (up to 2048 kbit/s) for interfaces as
SLID1 493 and R5C follows
SLID2 494 with - X.21/V.11
ESW SLIDF - V.35
- V.36
ML70E 093 R5C LESI8 092 with R5C ZATBU 121 093/1 R1A ML700 R2B Same basic features as the MUSIC 710λ but without POTS services.
(MUSIC 703λ) SP05 ESW LESIF Instead, the MUSIC 703λ supports 3 serial data interface n x 64 kbit/s (up to 2048 kbit/s) for interfaces as
SLID1 493 and R5C follows
SLID2 494 with - X.21/V.11
ESW SLIDF - V.35
- V.36
NTU 421 COZBU 405 421/4 R1H NTUL R1D Network Terminating (Desktop) Unit with 2B1Q data transmission over a twisted pair for the
operation with
- SULIC 391, 392, 396 (UMUX)
remote powering of the NTU is supported (33 … 96 VDC).
- NTU (point-to-point)
local powering of the NTU required
(+5.5 VDC).
The NTU supports data interfaces as follows:
- V.24/V.28 (600 bit/s … 38.4 kbit/s)
- X.21/V.11 (600 bit/s … 56 kbit/s,
64 and 128 kbit/s T, R signals only)
- V.35 (with adapter and local power supply only!)
COZBU 405 039/1 R1C - - V.35 adapter for the NTU 421.
SREG1 081 R7B LR DTM R7B 378 507 17 SREG1 R2A LineRunner Regenerator
STIC1 200 R7B 1 pair
STIC2 199 R7B
SREG2 082 R7B LR DTM R7B 378 507 25 SREG2 R2A LineRunner Regenerator
STIC1 200 R7B 2 pairs
STIC2 199 R7B
TUNOR 297 TUPON 397 R5B COZBU 405 297/1 R1E TUNOR R1C Desktop unit with optical 8 Mbit/s IF for 4 x 2 Mbit/s traffic (G.703 or V.11)
TUNOL 299 R3D The TUNOR 297 is for 230 VAC mains powering
TUNOF 284 R4E
TUNOR 298 TUPON 397 R5B COZBU 405 298/1 R1E TUNOR R1C Desktop unit with optical 8 Mbit/s IF for 4 x 2 Mbit/s traffic (G.703 or V.11). 1 IF supports the
TUNOL 299 R3D ISDN PRA service.
TUNOF 284 R4E The TUNOR 298 is for 230 VAC mains powering

TUNOR 300 TUPON 397 R5B COZBU 405 300/1 R1E TUNOR R1C Desktop unit with optical 8 Mbit/s IF for 4 x 2 Mbit/s traffic (G.703 or V.11).
TUNOL 299 R3D The TUNOR 300 is for 115 VAC mains powering
TUNOF 284 R4E
TUNOR 280 TUPON 397 R5B COZBU 405 280/1 R1E TUNOR R1C Desktop unit with optical 8 Mbit/s IF for 4 x 2 Mbit/s traffic (G.703 or V.11). 1 IF supports the
TUNOL 299 R3D ISDN PRA service.
TUNOF 284 R4E The TUNOR 280 is for 115 VAC mains powering
1)
FUTURE OPTION.
For details of availability, please contact your KEYMILE sales channel.
Please note that the table above
• does not show compatible desktop devices (for this information, refer to the table be-
low).
• describes only standard versions. For customer specific versions, please contact
KEYMILE or use your customer specific ordering codes.
The table below shows the released interoperability between the units.
Tab. 4-1: Summary interoperability of xDSL units (UCST R8B SP02)
LE2RG local power

LE2RG line power
LEMU6 236 (R3)
LEMU6 266 (R4)
ML70A 087 (R1)

ML70A 091 (R2)
ML70C 089 (R2)
LESA8 085 (R1)
LESA8 086 (R2)
ML70E 093 (R2)

SLIM1 491 (R2)
SLIM2 492 (R2)
SLID1 493 (R1)

SLID2 494 (R1)
NT
LESI8 092 (R1)

LECA2/F R7.B
MUSIC 100 R1
MUSIC 100 R2
MUSIC 100 R3
MUSIC 100 R4
MUSIC 200 R1
MUSIC 200 R2
LECAR R7B
LECA2/F R6
LECAR R6
LT
LECA2/F R6 X - - - - - - - - - - X - X X X X - - - - - - X X
LEMU6 236 (R3) - - X - - - - - - - - - - - - X X - - - - - - - -

LEMU6 266 (R4) - - - X - - - - - - - - - - - - X - - - - - - - -
LESA8 085 (R1) - - - - X - - - - - - - X - - - - - - - - - - - X

LESA8 086 (R2) - X - - - X X X - - - - X - - - - X - - - - - - X
SLIM1 491 (R2) - X - - - X X X - - - - X - - - - X - - - - - - X
SLIM2 492 (R2) - X - - - X X X - - - - X - - - - X - - - - - X X
LESI8 092 (R1) - - - - - - - - X X X - - - - - - - X X X X X - X

SLID1 493 (R1) - - - - - - - - X X X - - - - - - - X X X X X - X
SLID2 494 (R1) - - - - - - - - X X X - - - - - - - X X X X X X X
LECAR R6 - - - - - - - - - - - X - X X X X - - - - - - - -
-
MUSIC 100 R1 - - - - - - - - - - - - - X - - - - - - - - - - -
MUSIC 100 R2 - - - - - - - - - - - - - - X - - - - - - - - - -
MUSIC 100 R3 - - - - - - - - - - - - - - - X - - - - - - - - -
MUSIC 100 R4 - - - - - - - - - - - - - - - - X - - - - - - - -
MUSIC 200 R2 - - - - - - - - - - - - - - - - - - X - - - - - -
This chart shows the ESW release only – in addition the same line code must be used
for both the LT and the NT
Please note:
• The regenerators (LE2RG) are only available for the line code CAP at 1168 kbit/s.
• LT operation is not supported for LECA2/F R7B, LECAR R7B, MUSIC200 R1 and all
MUSIC 700 versions.
• LESA8 simultaneously supports MUSIC 200 and LECAR on the same unit (however
not within the same set of copper pairs).
• LECAR and LECA2 must have matching FW. The change of FW requires the ex-
change of EPROM devices since the units do not support remote software download.
4.9 Modules
4.9.1 PC memory cards
Table 4-11: PC memory cards

UMUX-UG KDYBU 201 101/1 R1B Upgrade 16 MBytes PC memory card for COBU<X>
4.9.2 SFP modules
Table 4-12: SFP modules

IPLM1-AC SFP modules with Ethernet interfaces for IPLM1:
KRCBU 101 103/1 - SFP Trans. 1000BASE-SX MM (duplex LC)
KRCBU 101 104/1 - SFP Trans. 1000BASE-LX SM (duplex LC)
NEBRO-AC SFP modules with Ethernet interfaces for NEBRO/NEBRA :
NEBRA-AC KRCBU 101 101/1 - SFP Trans. 100BASE-FX MM (duplex LC)
KRCBU 101 102/1 - SFP Trans. 100BASE-FX SM (duplex LC)
KRCBU 101 103/1 - SFP Trans. 1000BASE-SX MM (duplex LC)
KRCBU 101 104/1 - SFP Trans. 1000BASE-LX SM (duplex LC)
SYNUF-AC SFP modules with SDH STM-1 interfaces for SYNUF and SYN4E:
SYN4E-AC KRCBU 101 105/1 - SFP Trans. S-1.1 SM (duplex LC)
KRCBU 101 106/1 - SFP Trans. L-1.1 SM (duplex LC
KRCBU 101 107/1 - SFP Trans. L-1.2 SM (duplex LC)
KRCBU 101 108/1 - SFP Trans. X-1.2 SM (duplex LC)
KRCBU 101 110/x - SFP Trans. CWDM 1610 nm … 1470 nm LR SM (duplex LC)
KRCBU 101 112/x - SFP Trans. CWDM 1610 nm … 1470 nm XR SM (duplex LC)
KRCBU 101 109/1 - SFP Trans. STM-1 electrical (DIN 1.0/2.3 75 Ohm, female)
SYN4E-AC SFP modules with SDH STM-4 interfaces for SYN4E:
KRCBU 101 113/1 - SFP Trans. S-4.1 SM (duplex LC)
KRCBU 101 114/1 - SFP Trans. L-4.1 SM (duplex LC
KRCBU 101 115/1 - SFP Trans. L-4.2 SM (duplex LC)
KRCBU 101 116/1 - SFP Trans. X-4.2 SM (duplex LC)
For detailed and updated information of supported and recommended SFP modules
please contact your KEYMILE sales representative or retrieve the corresponding informa-
tion from KEYMILE’s Extranet.
For registered customers, the UCST software is available for download from KEYMILE's
Extranet (access via www.keymile.com).
After the login to the Extranet follow the path «Documentation & Software
→ UMUX/UCST → Techn. Documentation → Bulletins».
© KEYMILE AG
5 UCST R8B
5.1 PC / OS requirements
5.1.1 General
The UCST software (32-bit versions) is released for PC/computers running Microsoft Windows®
operating systems as follows:
• Windows® 2000
• Windows® XP Professional
• Windows® Vista Enterprise (32-bit version)
• Windows® Server 2003
The above list of operating systems is definitive.
Principally, it is also possible to operate the UCST R8B SP02 under Windows® Vista
Home Basic. However, some operational restriction applies.
When starting the «Communication Manager», the check for running UCST instances
fails. Accordingly, no error is reported if there are running instances and the changes
of the RAS/Modem configuration applied via the «Communication Manager» are lost
when closing the UCST (instances).
5.1.2 Windows® 2000
If your PC/computer runs the Windows® 2000 operating system, the PC/computer meets the ba-
sic requirements (microprocessor type/speed, RAM, hard disk, CD-ROM drive) to run the UCST
(32-bit versions) software.
For your convenience and a reasonable performance, your desktop or laptop PC/computer should
meet the following additional requirements:
UCST R8B © KEYMILE AG
• 256 Mbytes RAM min., 512 Mbytes strongly recommended

A small memory installed on the computer reduces the access times and hence the life of the
Hard Disk. This could result in the replacement (swapping) of the hard disk.
• Microsoft Mouse or compatible pointing device.
• SXGA colour screen system, min. resolution 1024 x 768 pixels.
• Additional memory requirements for UCST and unit software on hard disk drive:
80 Mbytes minimum, 100 Mbytes recommended.
• Serial interface RS-232 C (UMUX F- and Q1-interface, modems etc.)
Recommended options:
• Ethernet interface 10BaseT
5.1.3 Windows® XP Professional
The same requirements and recommendation apply as for running the UCST under the Windows®
2000 operating system.
5.1.4 Windows® Vista Enterprise (32-bit version)
5.1.5 Windows® Server 2003
The additional requirements quoted are not requirements to run Windows® 2000/ XP
Professional/Server 2003 but complementary requirements to run the UCST under
Windows® 2000/XP Professional/Server 2003.
5.1.6 RS-232C interface
Recent PC/notebook hardware may have no physical RS-232C interface. With a USB to RS-232C
serial converter it is possible to physically implement the RS-232 C interface for the UMUX F- and
Q1-interfaces, modems etc. for these PC/notebooks.
A dedicated Engineering Bulletin (EN/LZTBU 880 148) is available which describes the installation
and commissioning of such devices for the application with the UCST. The EB includes a list of
recommended USB to RS-232C serial converters that have been successfully tested with Win-
dows® XP Professional and the UCST.
5.2 Installation of UCST service packs
The installation of the current Service Pack automatically updates the UCST with the contents of
the previously released Service Packs (if applicable). Thus, with your new Service Pack you do not
need any of the previously released Service Packs.
1. Login to your PC with administrator rights (if applicable).
2. Ensure that all running UCST programs and instances are closed.
3. Run UCST_R8B_SPxx.exe on the CD-ROM containing the UCST Service Pack software.
The Service Pack installation utility searches automatically for the appropriate UCST installation
and guides you through the Service Pack installation process.
The current service pack for UNEM R8B is SP02.
Please note that the upgrade procedure for customer specific UCST versions may dif-
fer from the above upgrade description.
© KEYMILE AG
6 Compatibility and upgrades
6.1 Support of legacy UMUX
The UMUX network element types

• UMUX 1300
• UMUX 1100
• UMUX 1100E
are basically supported with UMUX / UCST R8 and its service packs.
UNEM R8 under HP-UX still offers serial communication ports (RS232) and therefore supports all
existing management communication networks.
In contrast, UNEM R8 under LINUX does not support serial communication. Legacy UMUXs can
still be reached via terminal servers or via a gateway UMUX 1500 / 1200 / 900. Existing manage-
ment networks to legacy UMUXs may have to be modified.
Compatibility and upgrades © KEYMILE AG
6.2 Configuration
6.2.1 Compatibility with previous configurations
Rules for compatibility:

• The new UCST can read configurations created with earlier UCST versions (UCST R3.3a/1 and
higher) if the configuration describes only units (the template number is not relevant) that are
still supported (this includes obsolete function units).
• If the configuration contains units that are not supported anymore with the new UCST, the con-
figuration cannot be read and failure is reported.
In such a case you must eliminate these units with the original UCST version and replace the
unit (if available) with a functional substitute that is supported by the new UCST.
KEYMILE strongly recommends upgrading obsolete units in legacy configurations with current pre-
ferred units.
6.2.2 Procedures
Before upgrading (UCST, embedded software, unit templates, configuration), it is of ultimate impor-
tance to save the configuration of all affected NEs using the existing (old) UCST. Although not
imperative in all cases of upgrades, this measure will prevent any possible loss of configuration
data.
To upgrade an existing configuration to a configuration with more recent templates and ESW pro-
ceed as follows:
• Install the new UCST on the PC (that you want to use to upgrade NEs)
• Upload the configuration from the NE
(refer to comments on compatibility of configurations above)
• Save configuration
(refer to comments above)
• Only if applicable: Replace hardware with compatible new unit(s)
• Deliver and install new ESW, corresponding to the unit to upgrade (download)
• Convert unit to the new template (download)
• Update the NE configuration if necessary (download)
Please note:
If you want to upgrade and the control unit is affected, the COBU<x> unit must be up-
graded in a first step before you upgrade the other units and functions.
In systems with redundant COBU<x> units, the ESW must also be installed in the redun-
dant unit (“update redundant unit”).
Because of enhanced function implementation in the new UCST, legacy configuration can loose
(depending on the upgrade step) particular configuration information when upgrading.
This applies in particular for
• Cross connections of the SDH ECCs via the SDH SOH (MS and RS path overhead)
(Flexible SOH byte use with the UCST R5B and higher)
• Cross connections of UBUS units with 1+1 protection
(Unified traffic protection for all units with the UCST R5A and higher)
• Special upgrade procedure for the PHLC3
If upgrades affect any of the above functions you must recreate the affected cross connections af-
ter the upgrade.
6.3 Control units
6.3.1 Support of units
To support all functions of the new UMUX / UCST release, the NEs must operate with R5 Control
Units running the latest COBUX ESW (If applicable you must upgrade your Control Units to R5
as described below).
Functions and units as follows require R5 templates and/or R5 ESW:
>= R5D ESW:
- ATM, NGN (IPSMG) functionality (R5 templates and ESW)
- Enhanced handling of configuration data (R5 templates and ESW)
- NEBRO, NEBRA Ethernet over SDH functionality (R5 ESW)
- NEBRE Ethernet switch (R5 ESW)
- SUBH subscriber line interfaces (R5 ESW)
- DATA<X> versatile data interface unit (R5 ESW)
>= R5E or more recent ESW:
- IPLM1/2/4 and IPLM6 IP DSLAM (R5 templates and ESW)
- SYNUF (R5 ESW)
>= R5H ESW:
- SYN4E (R5 ESW)
Please note that intermediate ESW for COBU<X> has also been released to correct func-
tional deficiencies. Accordingly, an unconditional update to R5 Control Units with the
most recent ESW is strongly recommended.
6.3.2 Upgrade process
To the upgrade of your control units in the UMUX NEs to R5 you should always use the current
UCST and the most recent released COBUX ESW version – currently the COBUX_R5H ESW.
Please note that the upgrade of control units is crucial. To upgrade proceed as follows:
• Install the new UCST on your PC/computer.
• Connect the EM to the NE that you want to upgrade.
• Load the NE configuration from the NE to the EM (upload).
• Save the configuration file (strongly recommended).
• Deliver the new COBU<X> R5H ESW. Do not remove old APDSW files from the NE!
• Configure the installation of the new ESW for the control unit.
• Download this configuration (e.g. via a partial download) to the NE.
• Check if the new COBUX ESW is running via the Inventory dialogue (the Software Installation
Status dialogue is only available with the COBU<X> R5).
• If the NE has a protecting COBU<X>,
Open the COBU<X> status dialogue (Board tab) and make sure, that the redundant control unit
is synchronised with the active control unit.
To achieve synchronism, you must press the button [Update Redundant Control Unit]. The up-
date can take a couple of minutes, depending on the number of ESW files that are stored in the
active COBU<X> MIB.
• Convert the templates of the control unit to the new R5 templates if required (via the NE Con-
figuration… → Convert Units… menu)
• Download the configuration with the new templates to the NE
(e.g. via a partial download).
The upgrade of control units is crucial
Never upgrade to a new COBU<X> R5 template unless you have checked that a COBUX
R5 ESW is active on master and slave unit!
Please note that it is
• not allowed to downgrade a NE (SW installation of COBUX ESW R1 … R4 is not ac-
cepted if COBUX R5 ESW (or higher) is running).
• no longer possible to manage a NE with UNEM/UCST R5<X> if its COBU<X> has
been upgraded to R5 (both COBUX ESW and COBU<X> template).
However, it is possible to upgrade the COBU<X> ESW to R5 and continue to manage

the COBU<X> R4 templates with the UNEM/UCST R5<X>.
The ATM and NGN functionalities have increased requirements on the capacity of the database
(MIB) of the COBU<X> control unit. The use of the COBU<X> with the 16 MBytes PC memory card
option is highly recommended. However, the 16 MBytes PC memory card option is not generally
required to operate the ATM core or NGN functions. Current COBU<X> units are delivered with 16
MBytes PC memory cards (8 Mbytes cards are no longer available).
Converting the control unit to R5 ESW is a good opportunity to upgrade the capacity of the local
PC memory card(s). For other aspects of PC memory card upgrades, refer also to «Support of PC
flash memory cards» on page 89.
6.4 Support of PC flash memory cards
The UMUX control units support different brands of PC memory cards. To this end, the control unit
is able to detect the type of the memory card and use the appropriate software driver.
The introduction of new PC memory card products requires an upgrade of the corresponding driv-
ers, which are provided with the APDSW software. The most recent APDSW_R1.C03 (introduced
with the UCST R4C) supports all the PC memory card products used with the UMUX control units.
Running COBUX ESW older than COBUX_R3.B32 is not possible with some of the currently used
PC memory card products. Trying to run such an ESW with these memory cards will create a soft-
ware installation error. To eliminate this failure, the control unit requires the upgrade of its ESW
and APDSW to remain compatible with all the PC memory card products:
• Delivery of the APDSW_R1.C03 to the NE.
• Delivery of the COBUX_R5.H02 ESW or a more recent ESW (but at least the COBUX_R3.B32
ESW) to the NE.
• Configuration of the new ESW installation for the control unit.
• Download of the new configuration, which activates the new ESW.
Please note that
• It is always preferable to run the most recent control unit ESW.
The COBUX_R5.F02 is currently the most recent ESW available.
• The COBU<X> is delivered with a 16 MBytes PC memory card (8 Mbytes cards are
no longer available).
6.5 New unit hardware
Over production time some of the components of the unit hardware are no longer available as
standard components and have been replaced by functionally compatible components and circuits.
Such a replacement provides new hardware for the affected units.
The new unit hardware implies a new hardware key and thus an adaptation of the ESW for com-
patibility with the new hardware (HW key). The new ESW is backward compatible. You can run the
new ESW on old unit hardware. However, it is not possible to run old ESW on the new unit hard-
ware. The new unit hardware imperatively requires the new ESW versions.
Refer to «Summary of units» on page 38 for the old and new compatible ESW and, if applicable,
for special entries («Ditto with new HW/ESW») concerning functions with new unit hardware.
6.6 IPSMG conversion
The units IPSMG 705 and 706 are handled as ABUS units, while the IPSMG 707 is an SBUS unit.
• Adding of an IPSMG 707 to a bus sector with an already equipped IPSMG 705 or 706, is not
possible. The equipped IPSMG 705 or 706 units must first be converted to IPSMG 707 units.
• It is not possible to add an IPSMG 707 unit to a bus sector that already contains ABUS units. If
available, use the second bus sector of the subrack to add the IPSMG 707.
6.7 NE traffic
The standard upgrade procedure can disturb the NE traffic. However, if the upgrade requires the
restart of the COBU<X>, the (UBUS) traffic is shortly interrupted. Upgrades with loss of cross con-
nections create interruptions for the traffic signals.
6.8 Ordering of units
6.8.1 Ordering process
To order UMUX units proceed as follows:

Specify the generic name of the unit that you want to order and the corresponding unit name
and the Keymile ordering code.
Examples are
− COBUX-FU: A24A3651
− LOMIF-FU: A24A3323
− SYN4E-FU: A31A5296
− etc.
Upon this order, you will receive the ordered unit hardware and a CD-ROM which contains the
complete collection of the most recent unit software (Embedded Software ESW).
The unit hardware together with compatible unit software (ESW) and your UCST unit template
(configuration file) will create the required function unit.
For refer to «Summary of units» on page 38 in this release note or in previous release notes if re-
quired.
6.8.2 Background information
The UCST unit template (e.g. COBUX 212) is specific for the features and functions of a function
unit as described in the UMUX customer documentation (e.g. «UMUX Technical Descriptions Units
COBUX 219, 223, 212, 213 & COBUV 220, 224, 217, 218»).
Such a function unit is introduced with a particular UCST & UNEM release and is supported by
subsequent releases of the management software for as long as required. Typically, a function unit
is no longer supported when an updated function unit (with a new UCST unit template) with en-
hanced features and functions is introduced.
Each new release of an ESW supports all earlier UCST unit templates, provided that it is compati-
ble with the unit hardware. Such an incompatibility is only possible if a new modified hardware ver-
sion for the function unit replaces previous hardware and this new hardware is more recent than
the locally available ESW (Please note that ESW delivered with the unit hardware is always com-
patible with this hardware).
For registered customers, the most recent ESW is also available for download from KEYMILE's Ex-
tranet.
Example:
Assumption: You operate the COBUX 145 in the NEs of your UMUX network.
The COBUX 145 has been initially introduced with the
− UCST & UNEM R4C
− COBUX R3D ESW
To order a new compatible COBUX for your NEs, just specify the generic function unit
«COBUX-FU» with the KM ordering code A24A3651.
With this, you will receive the COBUX hardware (unit) and the most recent COBUX ESW.
The configuration of your NE with the COBUX 145 template and any COBUX ESW equal to or
newer than COBUX R3D will create the COBUX 145 functionality in your NE.
© KEYMILE AG
7 Software carriers and documentation
7.1 Software and software packages
7.1.1 UCST
Table 7-1: UCST R8B package

Name Order No. KEYMILE PEC Functions
UCST R8B + SP02 A32A0145 EN/LZYBU 199 026/1 R1C UCST R8B package (KEYMILE standard version) including the following items:
package - CD-ROM with the UCST R8B software.
- CD-ROM with the UCST R8B SP02 software.
- CD-ROM with current ESW for all supported units and Custom Parameter Sets
for V5 and NGN applications.
The CD-ROM contains the most recent ESW and is in a package together with
the UCST CD-ROM
There are several customer versions of the UCST R8B package (including
SP02) available. For more information, please contact KEYMILE.
UCST R8B SP02 A32A0620 EN/LZYBU 199 029/1 R1A UCST R8B Service Pack 02 package including the following items:
package - CD-ROM with the UCST R8B SP02 software.
The UCST R8B SP02 package updates all customer specific versions of the
UCST R8B software.
For registered customers, the UCST software is also available for download from KEYMILE's Ex-
tranet (access via www.keymile.com).
After the login to the Extranet follow the path «Documentation & Software → UMUX/UCST
→ Software → UCST».
Software carriers and documentation © KEYMILE AG
7.1.2 Embedded Software
The current ESW (embedded software) for function units and public CPSs (customer parameter
sets) are available on CD-ROM.
Table 7-2: Embedded software and CPSs
Name Order No. KEYMILE PEC FW Functions
Embedded SW A22A2397 EN/LZYBU 251 850/1 (Date) current CD-ROM with current ESW for all supported units and public Cus-
tom Parameter Sets for V5 and NGN applications.
This CD-ROM is automatically provided with new unit deliveries.
ESW is backward compatible with existing unit functions and tem-
plates. For details, please consult the corresponding release notes.
KEYMILE recommends the use of current ESW in all installations,
since the current ESW eliminates bugs and deficiencies of legacy
ESW.
For registered customers, the most recent ESW is also available for download from KEYMILE's Ex-
tranet (access via www.keymile.com).
→ Software → Embedded Software».
7.2 Customer documentation
7.2.1 Overview
The tables below describe the customer documentation related to the UMUX / UCST R8B.
The customer documentation is divided into two groups:
• UMUX / UCST R8B customer documentation
• Associated customer documentation
The tables for «associated customer documentation» show customer documentation which is re-
lated to the UMUX (and MileGate) network management system.
7.2.2 UMUX / UCST customer documentation
7.2.2.1 UMUX / UCST documentation CD ROM version
Table 7-3: UMUX/UCST R8B customer documentation CD-ROM

Name Order No. KEYMILE PEC Type Functions
UMUX / UCST R8B SP02 A32A1490 EN/LZYBU 801 156/1 RC CD ROM UMUX platform documentation on CD-ROM (pdf format) for the
Customer Documentation UCST/UMUX R8B SP02:
The CD ROM contains:
- Collection of technical descriptions for the UMUX family (UMUX
1500, UMUX 1200 and UMUX 900)
(contents of collection EN/LZABU 150 205 RA)
- Collection of user guides for the UMUX family (UMUX 1500,
UMUX 1200 and UMUX 900)
(contents of collection EN/LZABU 150 305 RA)
- Engineering bulletins
- Technical bulletins
- V5 / H.248 check lists
- UMUX cables manual
- Ordering codes
- Release Note UMUX / UCST R8B SP02
(EN/LZTBU 980 415/512 RA)
Note: For the contents of EN/LZABU … refer to «Printed version»
below.
For registered customers up-to-date customer documentation is available for download from
KEYMILE's Extranet (access via www.keymile.com) as follows:
• Remote access to the customer documentation CD-ROM.
• Up-to-date release note
• New engineering bulletins
• Up-to-date information on supported transceivers and modems
• Product change notices
→ Techn. Documentation → ...».
7.2.2.2 UMUX / UCST documentation hardcopies
Table 7-4: UMUX/UCST R8B customer documentation hardcopies

UMUX / UCST R8B SP02 A32A3397 EN/LZABU 150 205 RA Collection Collection of technical descriptions for the UMUX family (UMUX
1)
Technical Descriptions 1500, UMUX 1200 and UMUX 900) with binders as follows:
Binder Technical Description – Systems: Part 1
- NE System Descriptions
- UMUX 1500 Technical Description
- UMUX Functional Descriptions
- UMUX TDM Traffic System
- UMUX ATM Traffic System
- UMUX Special Traffic Functions
- UMUX Units
- UMUX Operation & Maintenance
- UMUX Management
- UMUX System Specification
Binder Technical Description – Units: Part 1
- Control units
- Power units
- ABUS units
- SBUS units
Binder Technical Description- Units: Part 2
- PBUS units
- UBUS units
- Special units
- Remote units
Note: Formerly released units are documented in the User Guide –
Legacy Units.

UMUX / UCST R8B SP02 A32A3398 EN/LZABU 150 305 RA Collection Collection of user guides for the UMUX family (UMUX 1500,
1)
User Guides UMUX 1200 and UMUX 900) with binders as follows:
Binder User Guide – Systems: Part 1
- Installation Guides
- UMUX 1500 (DUPI4, FANU5)
- UMUX 1200 (DUPOS, FANU2)
- UMUX 900 (FANU3)
- Patch Panel,
- Over voltage & Lightning Protection
- UMUX User Guides
- UMUX User Guide
- UMUX TDM System & Cross Connect
- UMUX ATM System & Cross Connect
- UMUX Synchronisation
Binder User Guide – Systems: Part 2
- UCST Installation & Commissioning
- UCST / System Operation Basics
- UMUX Management Communication Networks
- UMUX EOC
- UMUX Network Functions
Binder User Guide – Units: Part 1
- Control units
- Power units
- ABUS units
- SBUS units
Binder User Guide – Units: Part 3A
- PBUS units (set A)
Binder User Guide – Units: Part 3B
PBUS units (set B)
- UBUS units
- Special units
- Remote units
Note: Formerly released units are documented in the User Guide –
Legacy Units.
Binder User Guide – Legacy Units:
- Legacy traffic units (UBUS)
(documentation for legacy units released for the UMUX
1500/1200/900 only).
- Legacy desktop/remote units
1)
The UMUX/UCST R8B customer documentation collections (hardcopies) are available on
request only.
7.2.3 Associated customer documentation
Table 7-5: UNEM customer documentation (CD-ROM compilation for Linux)

Name Order No. KEYMILE PEC Description
Customer documentation A32A0268 EN/LZYBU 801 076/12 RD CD-ROM with the UNEM R8B customer documenta-
UNEM R8B SP02 tion compiled for the RHE Linux operation system.
for RHE Linux
Release note UNEM R8B The UNEM R8B SP02 release note [NM].[152] which
SP02 includes the corresponding LoL is included in the CD
compilation of the UNEM R8B customer documenta-
tion.
Note: Please note that the release notes are updated
as required and published in KEYMILE’s Ex-
tranet.
Table 7-6: UNEM customer documentation (CD-ROM compilation for HP-UX)

Name Order No. KEYMILE PEC Description
Customer documentation A32A0267 EN/LZYBU 801 076/11 RD CD-ROM with the UNEM R8B customer documenta-
UNEM R8B SP02 tion compiled for the RHE Linux operation system.
for HP-UX
Release note UNEM R8B The UNEM R8B SP02 release note [NM].[152] which
SP02 includes the corresponding LoL is included in the CD
compilation of the UNEM R8B customer documenta-
tion.
Note: Please note that the release notes are updated
as required and published in KEYMILE’s Ex-
tranet.
For registered customers up-to-date customer documentation is available for download from
KEYMILE's Extranet (access via www.keymile.com) as follows:
• Remote access to the customer documentation CD-ROM.
• Up-to-date release note
• New engineering bulletins
After the login to the Extranet follow the path «Documentation & Software → UNEM → Techn.
Documentation → ... ».
© KEYMILE AG
8 Limitations
8.1 Overview
This chapter describes known limitations and deviations from specified system behaviour of the
UMUX/UCST R8B SP02 release. In this document both types are handled under the term «limita-
tions».
A limitation can have temporary or permanent significance:
• Temporary
Limitations are temporary if it is it is possible to fix them. Typically this type of limitation is due to
deficiencies of the system implementation.
For temporary limitations, a release is specified which clears the limitation. Depending on the
impact of the deficiency and its correction, it is not always possible to precisely schedule such a
release.
• Permanent
Limitations are permanent if it is not (reasonably) possible to fix them. Typically this type of limi-
tation is inherent to the system implementation or given by the chip sets used.
If available, KEYMILE provides a workaround to eliminate or reduce the impact of a limitation.
Limitations © KEYMILE AG
8.2 ACONV
Id System Function Area SW system Limitation Description Workaround Limitation

Unit involved cleared
UCST ESW UCST / ESW
Platform
6247 ACONV IMA R1B IMA Link alarms show incorrect persis- The following IMA Link alarms have To obtain the persist and absent times as - -
tence/absence times. incorrect persistence/absence time be- specified in IMA Spec 1.1, set the two
haviour parameters to their minimum in the con-
- Loss of IMA Frame figuration.
- Link Out of Delay Synchronization
- Remote Defect Indication
- Tx Fault
- Rx Fault
The UMUX Fault Management adds the
configured persistence/absence times to
the required 2.5 s persistence / 10 s
absence time filter (IMA Spec. 1.1 R-
152). Given the UCST defaults of 2.5 s
persistence / 10 s absence time, these
alarms will have over-all persis-
tence/absence times of 5 s / 20 s.
6247 ACONV ATM OAM R1B f4 and f5 alarms with incorrect persis- The integration time for VCC-AIS, VCC- To obtain the persist and absent times as - -
tence/absence time behaviour. RDI, VCC-LOC, VPC-AIS, VPC-RDI and specified in I.641, set the two parameters
VPC-LOC is specified in I.610 and is to their minimum in the configuration.
fixed. The user defined persist time is
added to the integration time. The same
behaviour applies for the absent time.
7443 ACONV IMA All The cell counts of the connection point The cell in and cell out counts of a con- No workaround - -
statistics for IMA group 1 are not accurate nection point differ by a few cells.
7905 ACONV IMA R1D Interrupting many IMA links simultane- All IMA links and CES channels are down - to be
ously causes errors on CES and IMA for less than 1 second, then recover defined
channels automatically.
7909 ACONV IMA R1D IMA link identifications >15 are not ac- This may cause interoperation problems, to be
cepted i.e. if in a third party product the IMA link defined
ID is configured with values >15.
7948 ACONV IMA R1D Heavy re-configurations of IMA groups The following re-configuration scenarios Heavy re-configurations should be split to be
may lead to reboot of ACONV or can stall work (light re-configurations): up in a sequence of light re- defined
traffic. Heavy re-configurations are re- - Addition of a new IMA group configurations.
configurations that modify existing groups - Removal of an existing IMA group
and links at the same time. - Addition of links to an existing IMA group
Work-around: " - Removal of links from an existing IMA
group

UCST ESW UCST / ESW
Platform
8055 ACONV CES R1D In certain configurations, PM elapsed The problem occurs if IMA links allocate to be
time clock is not running (shows 00:00:00 lower UVC12 subunits than the CES defined
and CES layer status is «NCI» channels
8128 ACONV SNCP R1D The protecting path does not work prop- When a defect causes a switchover to the No workaround to be
erly protecting path, sometimes an alarm defined
«Trail Signal Fail» is generated and the
transmitted signal may is not usable
8.3 ADACA / ADACB

UCST ESW UCST / ESW
Platform
7260 ADACB ADSL R1C Power management is not implemented. With ADACB, power management is not No workaround - to be
working, i.e. there is no power reduction defined
on the DSL line due to short loops. This
limitation has no impact on the transmis-
sion quality.
7261 ADACA ADSL R1C No output power indication for the down- In the downstream direction the output No workaround - to be
stream direction. power cannot be indicated, i.e. it is dis- defined
played as n/a.
7262 ADACA/B ADSL R1C The alarms «CPE not available» and The alarms «CPE not available» and The alarm «Loss of Link» will appear, if - to be
«CPE not available (LRP)» are not work- «CPE not available (LRP)» will never there is no CPE at the far end. defined
ing. appear.
7443 ADACA All The cell counts of the connection point The cell in and cell out counts of a con- No workaround - -
statistics are not accurate nection point differ by a few cells.
8.4 ADACS

UCST ESW UCST / ESW
Platform
8143 ADACS SHDSL R1B ADACS in worst case mode does not fall In worst case mode, the SHDSL link Specify more SNR margin than required - to be
within the configured SNR margin in all trains with the specified target SNR mar- defined
cases gin and a worst case self NEXT noise
model (49 SHDSL disturbers). In the
current implementation, the specified
SNR margin is not guaranteed for all test
loops.
8.5 ATIOP

UCST ESW UCST / ESW
Platform
6039 ATIOP ATM Counter R1B STM1 port statistic counters (cell in and The accuracy of the STM1 port statistic - -
cell out) are not accurate. cell counters is about
1 cell per counted 100'000 cells.
6247 ATIOP ATM OAM R1B f4 and f5 alarms with incorrect persis- The integration time for VCC-AIS, VCC- To obtain the persist and absent times as - -
tence/absence time behaviour. RDI, VCC-LOC, VPC-AIS, VPC-RDI and specified in I.610, set the two parameters
VPC-LOC is specified in I.610 and is to their minimum in the configuration.
fixed. The user defined persist time is
added to the integration time. The same
behaviour applies for the absent time.
7088 ATIOP ATM OAM R1B On VP endpoints, no VP (f4) segment Sending/receiving as well as looping of f4 Use f4 end-to-end OAM loop-back cells - -
loop-back OAM behaviour is supported. segment OAM loop-back cell is not pos- instead.
sible on terminated VP.
8.6 COBUX
Id System SW system Limitation Generation of erroneous situation Error description Workaround Limitation
UCST ESW UCST / ESW
Platform
2391 COBUX - ≥ R3B49 Loss of connectivity to In a generic network After interruption of the ECC to border No workaround - -
selected NEs in an AS - You create a backbone (area 0) and a router A, the router A is no longer able to
with redundant border nd
2 area. Each area has a network of communicate with some of the NEs in the
routers NEs. area with the interrupted ECC.
- The 2 areas are connected via 2 redun- However,
dant border routers. - there is still an ECC path (via the redun-
- Each border router connects via an ECC dant border router B) to the lost NEs
to an NE in the 2 areas. The border - the border router A has the lost NEs in
routers connect to different NEs. in the its database.
areas
- You interrupt the ECC connecting the
area network to the border router A.
2481 COBUX - ≥ R3B49 OSPF stub areas don’t - you configure stub areas. Destinations outside the AS are unreach- No workaround - -
work correctly - you want OSPF to reach destinations able from the stub area and vice versa.
outside the AS from the stub area. The UMUX OSPF implementation does
not add a summary route to the stub
areas.
2482 COBUX <R5C External OSPF default You add a default route (destination The External OSPF Default Route does None. - -
routes don’t work 0.0.0.0) as External Route to OSPF. not work: UCST R5C does not permit a
- OSPF doesn’t advertise this route to the configuration of a default with
other routers (over unnumbered PPP OSPF enabled
links)
- but it deletes the other routes learned by
OSPF
4408 COBUX Ping fails with the - You have an ECC via LAWA to a far end The ping returns no echo although the Implement a static route to the - -
COBU<X> COBU<X>. route is established (no routing errors) and far end COBU<X> if appropri-
Status/Maintenance - Use the ping function available from the it is possible to ping the far end COBU<X> ate.
function COBU<X> Status/Maintenance dialogue with the MS-DOS ping function.
to ping the far end COBU<X>. This error occurs if there is no static route
from the far end COBU<X> to the local
COBU<X>.
When pinging the COBU<X> sends first
the node Id (IP address of the F-interface)
and not its Ethernet IP address.
UCST ESW UCST / ESW
Platform
4839 COBUX R5B R3E02 Software installation for - Configure a scheduled software installa- The software installation for the remote With COBUX releases <R4, the R5C COBUX
LESA8 remote unit does not tion for a LESA8 or SLIM1 remote unit. units starts at the time that is defined for ESW for MUSIC 200 has to be R4A
SLIM1 work properly - Download the configuration to the NE. the board level (LESA8, SLIM) software loaded locally (via CLI). To
installation. avoid alarms you must config-
ure an ESW for MUSIC 200 in
Occasionally the immediate software the SW installation dialogue.
installation does not perform. The configured and the installed
ESW release on MUSIC 200
must be the same.
5206 COBUX all all The OSPF database is - You have an OSPF AS with COBUX, The OSPF data base of the routers is Use few OSPF areas in your - -
LEMU6 blown up in an OSPF AS LEMU6 and/or LAWA4 routers. blown up with the number of NEs and AS if the AS is small (few
LAWA4 with areas - You add areas to the backbone of the areas instead of being reduced. NEs).
Please note that this AS. The units operating as border routers Split a big AS (many NEs) into
limitation is not applica- - COBUX, LEMU6 and/or LAWA4 are between should only advertise an area several smaller AS and con-
ble for AS with COBUX border routers between the backbone summary to the other areas to keep the nect the AS with external links.
routers only. and the areas. OSPF traffic and data base small.
The COBUX, LEMU6 and LAWA4 border
routers promote via all their active OSPF
interfaces both, the area summaries and the
detailed network and router information.
7031 COBUX R3, 4B COBUX Protection A slave COBUX with ESW R4 is not up- If a COBUX with ESW R4 is inserted in the After pressing the button - -
graded correctly, if inserted in a subrack slave slot of a system, that is running an «Update Redundant Control
running R5 COBUX ESW and configura- R5 configuration, the slave COBUX is not Unit» you have to wait for
tion upgraded correctly to R5 ESW and R5 about 2 minutes. Then you
configuration. There is no problem, if the can remove the slave COBUX
ESW of master AND slave COBUX is from the subrack and insert it
upgraded to R5 BEFORE the configuration again. Now the upgrade will
is upgraded. be done correctly.
8.7 GECOD
UCST ESW UCST / ESW
Platform
3132 GECOD R4D10 - Unexpected alarm se- - GECOD 371: You might expect in all these cases the Change the default values to - -
verity defaults Loss of signal: Log Book Only (->UA) alarm option indicated in brackets instead your preferred severity option.
Loss of octet: Log Book Only (-> UA) of the logbook only.
Test loop active: Log Book Only (-> NA)
These alarm severities are typical for all
- GECOD 372: the 64 kbit/s traffic interfaces.
Loss of signal: Log Book Only (-> UA)
Loss of octet: Log Book Only (-> UA)
Test loop active: Log Book Only (-> NA)
(only if converted from a GECOD 371 unit)

4129 GECOD ≥ R4E70 R1B00 No AIS with Test loop 3b - Applies for UBUS units with EPIC in the With the UMUX 1500 and UMUX 1200 the No workaround - -
UBUS UMUX 1500 and UMUX 1200 only. loop 3b (or equivalent) sends instead of
units - Configure the Test loop 3b for GECOD. AIS the signal from the front interface to
This loop should loop the signal from the the UBUS.
front IF back to the front and feed AIS to The customer documentation describes
the UBUS. the behaviour for the loop 3b (or equiva-
lent) in the UMUX 1300 and
UMUX 1100(E) only.
8.8 IPLMx
UCST ESW UCST / ESW
Platform
IPLMx R1B In order to enable the Enable port provider status on uplink: Of the three listed commands, the first There are two workarounds: n/a >R1
use of two VLAN tags on $modify bridge port intf portid 193 command will disable port 193. As port - Use Management via ECC
the IPLM uplink, the status disable 193 is also used for the management of
- Download the commands to
IPLM Administrator must $modify gvrp port info portid 193 ppstatus the IPLM this will have the effect of dis-
the IPLM and apply the
enable the port provider enable abling ip comms to the IPLM, thus render-
script.
status on the uplink ing the IPLM un-reachable
bridge port (usually $modify bridge port intf portid 193 status
bridge port 193). enable
If the IPLM is managed
via the uplink this proce-
dure will disrupt man-
agement communica-
tions to the IPLM.
IPLMx R1B The administrator will Issue the following commands while the While the TPID value is 0x9100, and the To avoid the loss of comms to > R1
observe a loss of comms TPID is set to 0x9100: listed commands are issued, the IPLM will the IPLM, the administrator
if the port provider status $modify bridge port intf portid 193 status no longer be reachable by a PC telnet should modify the TPID in the
is enabled on port 193 disable session which does not use 0x9100 as the IPLM sizing table to the de-
and 0x9100 is the TPID. TPID. sired value before enabling
$modify gvrp port info portid 193 ppstatus
enable the port provider status.
0x8100 is supported for PC
$modify bridge port intf portid 193 status
telnet sessions and therefore
enable
recommended. It is recom-
mended that the following
commands are issued:
$modify nbsize svlanprotocolid
0x8100
$commit
$reboot
UCST ESW UCST / ESW
Platform
12786 IPLMx R1B IPLMx not manageable After reconfiguration the units did not This happens if the uplink port belongs to Proceed as follows: >R1
after change of IP ad- respond on the new IP address for a VLAN. - Set up an extra ECC man-
dress Ethernet in-band management. An ECC agement channel and log in
management connection was created in to the unit
addition to the in-band on all three units. - Restart the unit with “reboot
All units were accessible over ECC now config default” and the
and showed (cli command "get ip ad- IPLMx starts up with the cor-
dress"), there was still the former IP ad- rect IP address, but without
dress stored in the configuration. default gateway
- Remove the ECC manage-
ment channel in the UCST
menu and perform a partial
download
- Login to the IPLMx from a
local node, which is located
in the same IP subnet and
execute another “reboot con-
fig default”
- The IPLMx starts up with the
correct IP and gateway ad-
dress
See also EB "IPLMx Man-
agement Access - Change of
IP Address for Ethernet IF"
8.9 IPSMG
UCST ESW UCST / ESW
Platform
9489 IPSMG R2 Jitter Buffer is always in The customer configures the Jitter Buffer Though the Jitter Buffer is configured to be No workaround To be
adaptive mode. to be in fixed mode. in fixed mode, it is actually running in defined
adaptive mode.
9685 IPSMG R2 Five special characters Enter a subunit name containing at least No performance data can be retrieved Do not use the mentioned To be
cannot be used in the one of the following five characters: from the subunits containing any of the characters in subunit names. defined
subunit name <>"'& mentioned characters
UCST ESW UCST / ESW
Platform
15114 IPSMG R4D Termination IDs for The termination IDs for the ISDN ports are The termination IDs for the ISDN ports can No workaround To be
ISDN ports are not edited. be edited, but the IDs in the MEGACO and defined
configurable IUA messages remain on the default
values.
15130 IPSMG R4D Modem calls not possi- The “T.38 support for Non-V.34 Fax” Modem to modem (INTER) calls are not Disable T.38 support option on To be
ble when T.38 support option of the IPSMG (media path) is en- possible if the T.38 support option is used all involved IPSMG. defined
and the G.729 codec is abled. An attempt to set up a data com- together with the G.729 codec. The prob- Please note that the T.38
enabled munication with a modem connected to lem is that the codec is not autonomously functionality is not released for
the ISMG user port fails. switched to G.711. live applications. However, it
can be used for test purposes
only.
15989 IPSMG R4D Unit reboots after a Enable the T.38 functionality and perform The unit reboots after a certain number None. To be
certain number of fax fax calls. (30 … 50) of fax calls if T.38 functionality Please note that the T.38 defined
calls with T.38 function- is enabled. This limitation was only seen functionality is not released for
ality enabled with fax test equipment. It has not been live applications. However, it
seen with authentic fax equipment. can be used for test purposes
only.
16092 IPSMG R4D Digits are not reported To do speed dialling a short number (0 … If a digit-by-digit collection with a call Do not use speed dialling with To be
after digit-by-digit collec- 9) and after this the number to be dialled progress tone is followed by a digit-by-digit call progress tone defined
tion followed by call must be programmed via a special se- collection without a call progress tone, the
progress tone quence – initiated by dialling *10 - to the IPSMG does not send any more digits to
soft switch. the soft switch.
# terminates the digit-by-digit collection.
8.10 ISBUT
UCST ESW UCST / ESW
Platform
5405 PHLC2/3 ESW changes its name Install and configure a PHLC2, PHLC3 or In spite of the ESW name being PHLC1 or For the inventory: None - -
ISBUT depending on the in- ISBUT. ISBUQ, the inventory shows an ESW
stalled unit name PHLC2 for a PHLC2 card, PHLC3 For the SW installation error:
for a PHLC3 card and ISBUT for an ISBUT Upgrade the COBUX ESW to
card. In addition, a COBUX with ESW R3D >R3E
shows a permanent SW installation error.
8.11 LAWA4
UCST ESW UCST / ESW
Platform
5475 LEMU6 R5C - Pinging default network - The router knows an external route to The ping creates an answer although the No workaround - -
LAWA4 address 0.0.0.0 returns the address 0.0.0.0 (with some netmask route leads to no 0.0.0.0 host address (the 0.0.0.0 is no reasonable host
answer. mask). router finds a route for the required ad- address.
- From the Status/Maintenance dialogue dress).
you ping 0.0.0.0. There is no answer if the router does not
know a route for 0.0.0.0.
6142 LAWA4 All Loss of large packets Set up a PPP connection over the WAN Throughput between WAN port and LAN No workaround - -
over the Ethernet and port of the LAWA interface of the LAWA4 is limited to about
PPP interfaces 2100 packets/second.
8.12 LECAF - LECA2
UCST ESW UCST / ESW
Platform
3251 LECAF - - LECAF mechanically - You can configure the LECAF 070 for The LECAF hardware uses the new front Replace the LECAF with the - -
does not fit the legacy the UMUX 1300/1100/1100E. panel that is not compatible with the leg- second version, which uses
UMUX - It is not possible to physically insert the acy UMUX (UMUX 1300/1100/1100E). the old type front panel.
unit into the subrack. The LECAF with order number
COZBU 402 070/1 R2A and
up are compatible with all
UMUX subracks.
UCST ESW UCST / ESW
Platform
5625 LECAF All R7B LECAF/LECA2 with R7B You want to configure the LECAF or LECAF and LECA2 unit with R7B SW Use a LECA2 056 (R6A SW) - -
LECA2 SW cannot be used in LECA2 unit with the R7B SW in the UMUX cannot be configured in a UMUX instead.
UMUX1300/1100(E) 1300 or UMUX 1100(E) 1300/1100(E), as there is no template for Applications using 1 DSL pair
it. at 2320 kbit/s are not sup-
The UMUX 1300/1100(E) can support the ported (i.e. do not start up).
LECAF 070 and LECA2 056 templates The UMUX 1500/1200 sup-
with the R6A SW only. ports the LECAF 070 and
LECA2 056 templates with the
R7B SW.
8.13 LEMU6
UCST ESW UCST / ESW
Platform
5475 LEMU6 R5C - Pinging default network - The router knows an external route to The ping creates an answer although the No workaround - -
LAWA4 address 0.0.0.0 returns the address 0.0.0.0 (with some netmask route leads to no 0.0.0.0 host address (the 0.0.0.0 is no reasonable host
answer. mask). router finds a route for the required ad- address.
- From the Status/Maintenance dialogue dress).
you ping 0.0.0.0. There is no answer if the router does not
know a route for 0.0.0.0.
6005 LEMU6 R4C If a logical interface has - Two LEMU6s are connected with a Traffic may cease between the LEMU6s Delete the logical interface - -
neither ip nor bridge bridge over the PBUS causing a «protocol down» alarm. instead of disabling the proto-
enabled, a «protocol - One LEMU6 has several MUSIC100s col.
down» situation can connected
occur - Disable the network IF of a MUSIC100
and do a partial download
6570 LEMU6 R5C SP03 R4B Status enquiry not pos- Configure a LEMU6 266 and activate it. The error message «Communication error LEMU6 236 must be used - -
sible with LEMU6 266 Open the «Status/Maintenance» dialogue - Remote Layer 7: The intended register instead of LEMU6 266. Alter-
and press«Get» does not exist» is displaced. natively upgrade the LEMU6
ESW to R4C.
8.14 LESA8 - LESI8
UCST ESW UCST / ESW
Platform
4763 LESA8 R5B - Unfiltered PM is not - Select Performance Monitoring for a The PM functions are not correctly imple- Ignore unfiltered PM functions - -
SLIM1 implemented terminated or monitored NT. mented: for LESA8 / SLIM1.
- Select the User E12/P12 or Network - The unfiltered mode is not implemented Upgrade to LESI8 / SLID1
P12 layer. correctly for terminated or monitored where unfiltered PM is imple-
traffic. mented..
- The dialogue for the transparent mode is
not up to date.
LESA8 remote unit does not tion for a LESA8 or SLIM1 remote unit. units starts at the time that is defined for ESW for MUSIC 200 has to be R4A
must be the same.
5031 LESA8 all all DSL backend loop on The customer wants to set a DSL backend If the DSL link is down, the DSL backend On NT side it is possible to - -
SLIM1 NT side loop, when the DSL connection is not loop will not work correctly. have a DSL-backend loop,
established. only if the DSL connection is
running.
5703 LESA8 / All Communication failure - Configure a LESA8 or LESI8 with more UCST may suddenly display the following After activating a DSL restart, - -
LESI8 on activating DSL restart than 4 desktop units error message: «Communication Error, let the link complete the start-
with for several subunits in - Press DSL Restart for all links in suc- Remote Layer 7: Error at the system up procedure before activating
LECAR / quick succession cession as quickly as possible interface between L7 and system FW». the next restart.
MUSIC The last command is not executed, no
200 system malfunctioning occurs.
5726 LESA8 / R2B / R1B / When getting the inven- Repeat the following: Every so often the CPE is missing in the Repeat getting the inventory - -
SLIM1/2 / R2B / R1B / tory, sometimes a re- - Interrupt a DSL link to a CPE inventory
MUSIC R1B R2B mote unit is missing - Get the inventory
200
5942 LESA8 R2B Wrong alarm «Remote A LESA8 is connected to several desktop Occasionally the service channel of a Activate the DSL restart. This - -
unit not available» units LESA8. subunit is lost, resulting in «Remote Unit will produce a short interrup-
Unavailable» alarm. The data traffic is not tion of the data traffic..
affected.
6141 SLID1 / R1B / When getting the inven- Repeat the following: Every so often the CPE is missing in the Repeat getting the inventory - -
LESI8 / R1B / tory, sometimes a re- - Interrupt a DSL link to a CPE inventory
MU20A R2B mote unit is missing - Get the inventory
UCST ESW UCST / ESW
Platform
6145 LESA8 Invalid information for - Interrupt the DSL link to a MUSIC 200 or The status displays data in spite of the fact Get the P-DSL status to ascer- - -
NT state of LESA8 a LECAR that none is available. tain that the relevant service
- Read the NT status channel is available before
getting the NT status
8131 LESA8 R2D In SNCP, the protecting Create a defect that causes a switchover When a defect causes a switchover to the No workaround to be
LESI8 R1D path does not work to the protecting path protecting path, sometimes an alarm defined
properly «Trail Signal Fail» is generated and the
8.15 LOMIF - LOMI4
UCST ESW UCST / ESW
Platform
4198 LOMI4 R5A15 - Fault indicator LED - 1 or more subunits report a failure. The The lower fault indicator LED remains No workaround - -
LOMIF remains active traffic failure LED is on. active.
- you delete the unit via UCST or UNEM
from the configuration.
4527 LOMIF R3, R4 Wrong thresholds for - Configure a LOMIF with ESW R3 as The thresholds for SES/ES are now A LOMIF with ESW R3 must LOMIF
performance monitoring LOMIF 120 or 2500/650 instead of 430/22. be configured as LOMIF 140 R5A
- Configure a LOMIF with ESW R4 as A LOMIF with ESW R4 must
LOMIF 120 or LOMIF 140 or be configured as LOMIF 158
- Configure a LOMI4 with ESW R4 as A LOMI4 with ESW R4 must
LOMI4 150 be configured as LOMI4 159
4592 LOMIF - - Loop LT-U not inserted - Subunit operates in PRA LT-V3 mode The loop is not inserted although the Use LOMIF hardware more - -
- Loop insertion expected in LT-U con- corresponding Sa6 bit pattern has been recent than 1/ROFBU 367
trolled via Sa6 bits received in PRA LT- sent to LT-V3. 101/1 R1A.
V3. This error appears with LOMIF hardware
1/ROFBU 367 101/1 P1A only. Please
note that this information is available on
the LOMIF board only! It is not possible to
read this information via the inventory
function.
5754 LOMIF - - Unable to upgrade - A LOMIF has HW R1A (bootloader An error message «Layer 7 Generic Time- Workaround: - -
HW R1A LOMIF firmware via PDH R1A21) out» is generated. The activity list of the - Configure a scheduled ESW
ECC - The UMUX receives its management UNEM shows «Partial download failed» upgrade instead of an im-
channel via an ECC in that LOMIF. and the management channel fails. After mediate one.
- Configure an ESW upgrade for this communication is restored, the activity list - Fix the problem:
LOMIF in the SW installation as «Imme- reports «NE configuration changed by - Exchange the LOMIF with
diate» and do a partial download. another EM» in spite of there being only HW R1A for one with HW
one EM present. No ESW upgrade has R1B.
been performed.
8.16 MIRIG
UCST ESW UCST / ESW
Platform
1252 MIRIG - - Use of MIRIG in the Documentation error in EN/LZTBU 341 These statements are wrong or incom- Correct statements: - -
2119 UMUX 1100(E) versus 213 RA (User Guide 2.5d, Units, chapter plete. - In the UMUX 1100E it is not
slots Analogue Units, page 5-4, paragraph possible to use the MIRIG in
Mechanical) it is stated: the slots 13 and 14 (UCST
- «In the UMUX 1100E the MIRIG can be does not allow).
used in slot positions 13 and 14». - You can use the MIRIG in
- «The MIRIG can be used only in slot slots 16, 17 and 15 (not rec-
positions 16 or 17 in the UMUX 1100». ommended). However, the
MIRIG implementation in
slot 15 uses slot 16 as well.
2119 MIRIG all - UCST graphical imple- - Implement MIRIG in slot 16 Graphical implementation errors: Implement MIRIG as stated in - -
mentation of the MIRIG - Implement MIRIG in slot 17 - The UCST shows the logical width the customer documentation
in the UMUX 1100(E) - Implement 2 MIRIGs in the subrack. (narrow) of the MIRIG in slot 16. (refer to Id 1252).
- The UCST shows the logical width
(narrow) of the MIRIG in slot 17.
- The UCST allows you to implement 2
MIRIGs in the subrack. It is not possible
to operate 2 MIRIGs in the subrack.
The units marked in grey are obsolete.
8.17 MUSIC 100
UCST ESW UCST / ESW
Platform
0992 MUSIC «Destination Unreach- RFC 972: No workaround - -
100 able Message» not If, according to the information in the
implemented gateway's routing tables, the network
specified in the internet destination field of
a datagram is unreachable (e.g., the
distance to the network is infinity), the
gateway may send a destination unreach-
able message to the internet source host
of the datagram.
5050 MUSIC R5C R4E Rebooting Music 100 - LAW4 and LEMU6 build up an OSPF Traffic disruptions occur in all nodes con- No workaround - -
100 causes traffic problems network. nected to that network. This is a limitation of the
across OSPF network - MUSIC 100 are connected to LEMU6 This effect is caused by the OSPF and the OSPF stack.
- A MUSIC 100 reboots updates of the routing tables. The router of
the LEMU6, which connects to the Music
100 that is rebooted, updates his routing
table and advertise this to the other nodes.
This OSPF update disrupts the traffic for
some seconds.
8.18 MUSIC 200
UCST ESW UCST / ESW
Platform
5038 MUSIC all all X.21 byte timing with With 2Mb/s user rate (n=32), the byte Can only be cleared by a new - -
200 2Mbit/s user rate timing is not available. For all other data HW version of Music 200
rates (n=1,...,31) the byte timing is correct.
8.19 MUSIC 700
UCST ESW UCST / ESW
Platform
5831 MUSIC R1B Error count in «Common Retrieve common or interface statistics of While input and output values are correct, No workaround to be
700 Statistics» and «Inter- a MUSIC 700 error counts are not reliable (0 or even defined
face Statistics» not negative)
reliable
6030 MUSIC R1B Deactivating a POTS - Disable a POTS port in the configuration Data is interrupted for 8 seconds or voice No workaround to be
700 port leads to voice and of a MUSIC 700 calls may be dropped defined
data interruption of 8 - Do a partial download
seconds
6107 MUSIC Any Throughput between the - Configure the MUSIC700 using the two High packet loss rates are measured. This No workaround - -
700 2 LAN ports is limited to LAN ports is due to the processor capacity, which
around 7-8 Mb/s in both - Use a traffic generator to measure the allows for a maximum transfer of approxi-
routed and bridged throughput between the ports mately 4000 packets per second.
mode
8.20 NEBRO / NEBRA

UCST ESW UCST / ESW
Platform
9685 NEBRO Performance R2B The following five characters cannot be No performance data can be retrieved Do not use the mentioned characters in To be
NEBRA management used in the subunit name: from the subunits containing any of the subunit names. defined
<>"'& mentioned characters
8.21 NEMCA
UCST ESW UCST / ESW
Platform
9167 NEMCA R5C and NEMCA 301 cannot be - In UCST, select an existing NEMCA 301 The error message «Unable to convert - Delete the existing NEMCA -
later converted to NEMCA - Use menu «NE Configuration - Convert layer Traffic NEMCA301 R1 into 301.
311 Unit(s)» NEMCA311 R2» is displayed. - Create a NEMCA 311 and
- Select NEMCA 311 and click «Open» reconfigure it.
8.22 PCONV - PCON2
UCST ESW UCST / ESW
Platform
0347 PCONV all - Front End Loop not Apply a front end loop on the E12/P12 The front end loop of the E12/P12 inter- None. - -
available interface of the PCONV. face of the PCONV unit is not working. This limitation applies for
A «Frame Sync Loss» is generated for the PCONV with bus access ASIC
subunit. version 1.
3146 PCONV ≥ R4D10 ≥ R3D10 IC channels not opera- you install a V5.1. The IC-channels are creating alarms for Restart the PCONV unit. - -
PCON2 tional after PCONV the configuration seems to be ok ISBUQ and PCONV and the ISDN ports
restart are «unlocked / disable / local».
you start the IF
st
PCONV - R4C10 Only 1 P12 link is - You select a DMS CPS (Customer The P-Phone functionality is only sup- No workaround - -
PCON2 available with P-Phone Parameter Set) ported for the first P12 link subunit. CPSs for the DMS switch are
functionality and multiple - You configure several V5 interfaces only released for the support of
V5 (V5.1) V5.2 services (including the P-
- You select the P-Phone functionality. Phone service).
The erroneous situation is not
applicable for released services.
PCONV - R4C10 No status message if the - The PCONV SW detects unknown The PCONV SW sends no STATUS No workaround - -
PCON2 PCONV detects un- PSTN information elements in the na- message to the LE: only an error is logged This behaviour is not errone-
known information ele- tional PSTN protocol. in the protocol logbook. ous but according to the rele-
ments vant standard .
8132 PCONV R5C In SNCP, the protecting - Create a defect that causes a switchover When a defect causes a switchover to the No workaround to be
PCON2 path does not work to the protecting path protecting path, sometimes an alarm defined
8.23 PHLC1 - PHLC2 - PHLC3
UCST ESW UCST / ESW
Platform
4525 PHLC3 ≥ R5B - PHLC3 conversion You have a configuration with PHLC3 126 The UCST does not allow this conversion Before you convert the PHLC3 - -
R3 -> R4 does not work (R3) and want to upgrade the configura- and issues a generic error message. units you must manually
properly tion with PHLC3 127 (R4). delete all the cross connec-
You apply the standard upgrade proce- tions with PHLC3 126.
dure (delivery of new ESW, upload of After the conversion you must
configuration, installation of new ESW and re-create the cross connec-
download, unit conversion, download of tions for the PHLC3 127.
updated configuration).
4847 PHLC3 PHLC3 ring generator - PHLC3 is configured and inserted in the The PHLC3 ring generator creates a Remove the PHLC3 unit from - -
creates failure alarm UMUX subrack «Ring generator failure» alarm. This prob- the subrack and re-insert the
after UMUX power up. - The UMUX is not powered lem appears only occasionally. PHLC 3 unit .
- The UMUX is powered up HW problem in ring generator component,
fixed in latest production batches.
5105 PHLC3 R5B - Special upgrade proce- Refer to 4525 Refer to 4525 Refer to 4525 - -
dure R3 -> R4 for
PHLC3
5405 PHLC2/3 ESW changes its name Install and configure a PHLC2, PHLC3 or In spite of the ESW name being PHLC1 or For the inventory: None - -
ISBUT depending on the in- ISBUT. ISBUQ, the inventory shows an ESW
stalled unit name PHLC2 for a PHLC2 card, PHLC3 For the SW installation error:
for a PHLC3 card and ISBUT for an ISBUT Upgrade the COBUX ESW to
card. In addition, a COBUX with ESW R3D >R3E
shows a permanent SW installation error.
8905 PHLC1 R5C Changing the Provision- Change the Provisioning Set from 1 to 2 The port is blocked (no megaco messages Lock and unlock the port using -
ing Set blocks the port. and download the configuration. when doing an off-hook). This happens the status/maintenance func-
(seen with IPSMG and even if the two sets are identical. tion
uplink to CS2k)
8.24 POTS Splitter
UCST ESW UCST / ESW
Platform
6568 POTS Pulse dialling and hook Set up a DSL link with POTS splitters. During dialling and on hook off bit errors Change the telephone link to - -
Splitter off cause bit errors in the Connect a telephone link to the splitters are injected into the DSL link. tone dialling. Use telephones
DSL link that uses pulse dialling. with «soft hook off».
8.25 SLIM1/2 - SLID1/2
UCST ESW UCST / ESW
Platform
4763 SLIM1 R5B - Unfiltered PM is not - Select Performance Monitoring for a The PM functions are not correctly imple- Ignore unfiltered PM functions - -
LESA8 implemented terminated or monitored NT. mented: for SLIM1 / LESA8.
- Select the User E12/P12 or Network - The unfiltered mode is not implemented Upgrade to LESI8 / SLID1
P12 layer. correctly for terminated or monitored where unfiltered PM is imple-
traffic. mented.
- The dialogue for the transparent mode is
not up to date.
LESA8 remote unit does not tion for a LESA8 or SLIM1 remote unit. units starts at the time that is defined for ESW for MUSIC 200 has to be R4
must be the same.
5031 LESA8 all all DSL back end loop on The customer wants to set a DSL back If the DSL link is down, the DSL back end On NT side it is possible to - -
SLIM1 NT side end loop, when the DSL connection is not loop will not work correctly. have a DSL back end loop,
established. only if the DSL connection is
running.
5726 LESA8 / R2B / R1B / When getting the inven- Repeat the following: Every so often the CPE is missing in the Repeat getting the inventory - -
SLIM1/2 / R2B / R1B / tory, sometimes a re- - Interrupt a DSL link to a CPE inventory
MUSIC R1B R2B mote unit is missing - Get the inventory
200
6141 SLID1 / R1B / When getting the inven- Repeat the following: Every so often the CPE is missing in the Repeat getting the inventory - -
LESI8 / R1B / tory, sometimes a re- - Interrupt a DSL link to a CPE inventory
MU20A R2B mote unit is missing - Get the inventory
8131 SLIM1/2 R2D In SNCP, the protecting Create a defect that causes a switchover When a defect causes a switchover to the No workaround to be
SLID1/2 R1D path does not work to the protecting path protecting path, sometimes an alarm defined
8.26 STIC1 - STIC2, LRD1A - LRD1B - LRD2A, SREG1 - SREG2
UCST ESW UCST / ESW
Platform
15475 STICx -- COBUX G.SHDSL lines are An G.SDHL-line is terminated at each end If the clock source for the UMUX is To avoid interruptions of the to be COBUX
interrupted if the STICx on a STIC unit in 2 different UMUX NEs. switched from some source to the STICx G.SHDSL-lines in networks defined (to be
interfaces is become the There is at least 1 regenerator imple- interface or vice versa, the G.SHDSL-line where the UMUX synchronisa- defined)
synchronisation source mented in the G.SHDSL line. gets interrupted. tion can be taken from the
for the UMUX One of the STIC interfaces is configured The line interruptions occur also with short G.SHDSL interface of STICx,
as a timing source for the hosting UMUX. loops (with regenerators!) however less it is recommended that no
frequently. Thus, If regenerators are used regenerators are implemented
in networks where the UMUX synchronisa- in the G.SHDSL-lines connect-
tion is taken from the G.SHDSL interface ing 2 UMUX NEs via STICx
of a STICx, a re-synchronisation on the interfaces.
G.SHDSL line may occur that will lead to
service interruption.
10670 STICx R1A Operation of loops not Install and configure a STIC to DTM link Sometimes loops cannot be deactivated. Do not use «Network Clock to be
10680 LRDxx possible with «Refer- without or with regenerators using «Net- False alarms are registered. In some Synch» for «Reference defined
10681 SREGx ence clock» set to «Net- work Clock Synch». Activate a loop in cases bit errors occur during the time a Clock».
work Clock Synch» DTM or SREG. loop is activated. The errors may persist
after the loop has been released.
10934 SREGx SREG cannot sink wet- Line configuration with at least one SREG. No wetting current is flowing. No workaround - -
ting current Configure DSL line for «Wetting current This is a hardware limitation on current
source». SREGxx.
8.27 SYNAM - SYNIx - SYNOT - SYNVA – SYNUF – SYN4E
UCST ESW UCST / ESW
Platform
2811 SYNI<X> - ≤ R3B10 RDI and AIS are conse- - Poisson distribution is selected In contrast to the standards (refer to the No workaround - to be
quent action for Exces- - Excessive bit error rate on the MS, VC-4 paragraph below) and up to the defined
sive Bit Error Rate (Pois- layer. SYNIF_R3A72 ESW, a SYNI<X> with an
son) excessive bit error rate on the MS and VC-
4 layers generates RDI and AIS in the MS
or VC-4 and all the lower layers.
The ITU G.783 and ETSI 300 417 1-1 …-6
standards do not specify particular actions
in the case of an excessive bit error rate
on the MS and VC-4 layers.
3438 SYNAM - - SW-upgrade not possi- - you configure a new ESW for your The installation of the (new) ESW fails. Exchange SYNAM hardware. - -
ble SYNAM
- you download the new configuration. The error applies for ROFBU 367 116/1
R1A hardware only.
3527 SYNVA ≥ R5A - Unit disturbed alarm - NE configuration with SYNVA The SYNVA issues the «Unit disturbed Implement a correct SDH - -
after unit start up - SYNVA starts up alarm». configuration that implies at
One possible reason is that the SBUS least 1 unit with an STM-1
sector with the SYNVA has no SETS aggregate interface (SETS) for
(SYNI<X>, SYNIO). the (each) SBUS sector.
5230 SYNOT - R1A25 Excessive Bit Error Rate - Poisson distribution is selected In contrast to the standards (ITU G.783 No workaround - to be
(Poisson) is not a crite- - Excessive bit error rate on the MS, VC-4 and ETSI 300 417 1-1 … 6) the Excessive defined
rion for protection layer. bit error rate (Poisson) provides not trigger
switching for the protection switch.
9685 SYNUF R1A Five special characters Enter a subunit name containing at least No performance data can be retrieved Do not use the mentioned - To be
cannot be used in the one of the following five characters: from the subunits containing any of the characters in subunit names. defined
subunit name <>"'& mentioned characters
16174 SYN4E < R8C - P12 signal with P12 - Set the P12 mode for a particular P12 Only P12 signals with mode "terminated" Set the P12 to “terminated”. R8C -
mode "monitored" not signal to “monitored”. can be selected as synchronisation Selection as synch source will
selectable as synch - .Select the “Timing Sources -> Configu- source, in contrast to SYNAC, LOMIF etc be possible.
source ration” menu und lock for selections in where only P12 signals with mode "moni-
“units/subunits” for PETS. tored" can be selected as sync. source
- “Monitored” P12 traffic of the SYN4E is
not available for selection.
-
8.28 TUNOx
UCST ESW UCST / ESW
Platform
1532 TUNOS all - Limitation of cross con- - Optional: You configure the 1+1 protec- Possible errors No workaround - -
nections tion mode. - 1+1 mode: The protection fails if a fail-
- You create 4 cross connections DMX2 - ure happens. UCST reports no error.
> (UBUS and/or E12) and E12 -> UBUS - Without protection: The UCST creates
within 1 segment of the cross connect. «Connection not allowed» error.
- You want to create a 5th cross connec- The connections DMX2 -> (UBUS and/or
tion within that segment. E12) and E12 -> UBUS share a cross
connect segment with 4 lines (= cross
connections) in total.
th
If you select a 5 connection, the error is
created.
2490 TUNOP ≥ R3.3a/1 - ACFA loop does not - An external signal is connected on the Errors: No workaround - -
work, if no cross connect 1st subunit of a MEGIF that is cross - The loop does not work, no signal will be
on 2Mb/s is set connected (bi-directionally) to the 3rd received from the MEGIF.
subunit of the TUNOP. - However, if you cross connect ACFA 3
- All the TUNOP Board layer 2Mbit/s to DMX1 3 and vice versa, (but without
cross connections are disabled. enabling the laser) the loop will be cor-
- An ACFA loop is set from subunit 3 to rectly set.
subunit 3 (under diagnostics parameter).
5275 TUNOF - TUNOF cannot be in- It is not possible to physically insert the The TUNOF hardware uses the new front If the unit is not compatible - -
serted in legacy UMUX unit into the subrack. panel that is not compatible with the leg- you need a recent TUNOF
acy UMUX (UMUX 1300/1100(E)). version.
The TUNOF
COZBU 110 284/1 R2A and
up are compatible with all the
UMUX.
6343 TUNOP R1.4 Traffic interruption on a TUNOP is installed in U1500/1200 The traffic on the active channel will be No workaround - -
TUNOP installed in - Change the configuration of TUNOP interrupted for about 6 seconds
U1500/1200 after partial leaving an active channel untouched
download of a configura- - Download the configuration
tion change
The entries marked in grey are from obsolete units.
8.29 TUPON
UCST ESW UCST / ESW
Platform
8135 TUPON R1A In SNCP, the protecting Create a defect that causes a switchover When a defect causes a switchover to the No workaround to be
path does not work to the protecting path protecting path, sometimes an alarm defined
8.30 UNIDA
UCST ESW UCST / ESW
Platform
3278 UNIDA ≥ R4E70 - Spare signal with Loop - no CAS, signal rate ≥ 64 kbit/s The spare signal (towards the backplane) Set test loop options for «X.24 - -
3c not correct with - set Loop 3c signal T 0101. is not fixed but alternating 0101 and 1010. interface states if test loop
UNIDA 433, 436, 438 - external plesiochronous clock X The time between changes depends on active», «Loop 3c» set option
(X.24) - Loop 3c active the frequency offset to the external clock «1».
Do not select the option 0101.
5196 UNIDA all R1.1 PM not available for - You configure the UNIDA subunits for Although it is possible to access PM func- Do not configure or use PM for (R5C) (R1F)
R1E UNIDA subrate traffic subrate traffic (< 64 kbit/s). tions, the PM does not perform with UNIDA with subrate traffic (R4E +
- You want to use PM for subrate traffic UNIDA subrate traffic. signals (<64 kbit/s). SP06)
(bit rates < 64 kbit/s). This applies for single subrate traffic Use bit rates n = 1 (64 kbit/s)
signals and multiplexed subrate signals. up to n = 4 (256 kbit/s) for
oversampling the subrate
traffic. The oversampling rate
must be at least 3 times the
subrate traffic signal. This
requires additional TS in the
network to transport the
subrate signal!
The UCST R5C and R4E +
SP06 provide n =1 … 4 for the
UNIDA 431. These rates are
not released for standard
traffic.
This workaround is not appli-
cable for multiplexed subrate
signals.
8.31 Miscellaneous
UCST ESW UCST / ESW
Platform
3177 CPS ≥ R4E - Dead lock if the custom - you open a configuration with a custom It is not possible to quit the NE parameters Always configure the NE - -
parameter set is un- parameter set that is not known to your dialogue via [OK] if the custom parameter Default custom parameter set
known. UCST version. set is not known to your UCST (not avail- for all the applications that do
(if set marked with an *). able, no alias). not use V5 (in particular for
- you may modify parameters in the NE You cannot select the NE Default custom COLT-2 configurations).
parameters dialogue. parameter set.
- you want to quit the dialogue with [OK].
3341 Cross - - Missing connection The erroneous situations are generated as Some legacy units (working with the Manage and check connection - -
connect points on the UBUS follows (samples for the GECOD unit): UBUS) have loops (e.g. Loop 3b with points on the UBUS via the
GECOD) that can be implemented only via menus
a) You set a loop 3b.
configuration of the cross connect. When- UBUS Connection Points
The UCST issues the warning ‘A
ever a loop requires such «manually (create, delete) for tributary
connection point must be defined
configured» connection points, the UCST units only.
for this subunit !’
asks for the implementation of the connec-
The loop may work or not. BUS usage → UBUS
tion points. However, the UCST cannot
(check)
b) You find inconsistent traffic signals check their implementation:
on the interfaces of the UBUS unit a) If there are no connection points
(inconsistent between subunits). set the loop does not work.
However, the UCST accepts the
loop whether a connection point is
set or not.
b) The output traffic signal depends
on the existence of connection
points. E.g. the traffic signal with
CAS on the GECOD is :
- ‘AIS with octet timing’, if no con-
nection points are set.
- ‘AIS without octet timing’, if con-
nection points are defined but
there is no connection (a
download error with AIS on CAS is
simulated)
3481 SOH ≥ R4E70 - No CAS for SOH chan- Despite the fact that the SDH overhead The cross connected channel does not To solve the problem: - -
nels supports no CAS, it is possible to connect work. via unit configuration, disable
a traffic signal with CAS (e.g. from the CAS for the traffic signal
SIFOX) with the SDH overhead E- and F-
re-create the cross connection
bytes.
with the SDH overhead
channel
UCST ESW UCST / ESW
Platform
3498 ECC ≥ R4E70 - ECC cross connection - select ECC with 3 x 64 kbit/s The configuration is accepted, the ECC Do not use TS0 for this cross - -
via TS0 - cross connect to TS0, TS1 and TS3 of a does not work. connection.
suited subunit. The TS0 is special and provides
only a rate 16 kbit/s.
4975 E12/P12 - all In monitored mode, the - In a configuration of an E12/P12 inter- The received QL may be modified before it Do not use the Sa mode - -
layer received QL may be face (LOMIx, PCONV, SLIDx, SYNAC, reaches the control card for the timing «SSM G.704» for the P12
modified causing unex- TUPON etc.) select P12 mode «Moni- source decision. This can lead to the mode «Monitored».
pected reactions in the tored» and Sa Mode «SSM G.704» selection of the wrong timing source.
clock network. - Use this interface as a traffic source for
the UMUX timing.(QL based).
5404 E12/P12 R5C - Loops on the P12 layer - The NE has a subunit with a configured The loop on the P12 layer of the subunit is The «Maintenance Function - -
layer remain active after full P12 layer (e.g. of the LOMIF, LOMI4, still active. Active» alarm alerts you and
download of a new SLIM1/2, TUPON, SYNAC etc.). The «Maintenance Function Active» alarm informs on the affected sub-
configuration - There is an active loop on the P12 layer. is generated. unit.
- With the UCST you create a new con- Clear the loop.
figuration (e.g. via New) that configures
the same P12 layer of the same subunit.
- You perform a full download for the new
configuration.
5645 Voice R5B - P12 sublayers fail to - You have distributed conference nodes The 2 Mbit/s links loose the CAS MF and For voice conferences with - -
confer- synchronise the CAS MF (multiple COBUV) in your network are not able to re-synchronise the CAS MF distributed conference nodes,
ences with voice conferences - The NEMCA unit is the voice tributary after interruption and reconnection of the 2 the timeslots in the 2 Mbit/s
and the signalling is inband Mbit/s links. links that are used to transport
- CAS is enabled in the 2 Mbit/s links that the voice conference traffic
transport the conference traffic between between the nodes must be in
the nodes the TS17 to TS 31, if CAS is
enabled in the 2 Mbit/s links.
If this slot arrangement is not
possible you must disable
CAS in the 2 Mbit/s links.
11390 UCST The self-extracting - Execute the UST installation file An error message saying that there is not Use «winzip» to open the to be
executable for UCST UCST_R7x_yyy_inst.exe. enough memory available is displayed, or executable, extract the files to defined
can sometimes not be the operation is aborted without message. a temporary location and then
opened. run «setup.exe».

Release Note PDF

Uploaded by

Document Information

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

Release Note PDF

Uploaded by

Copyright:

Available Formats

UMUX from KEYMILE covers your communication requirements

UMUX & UCST R8B SP02

UMUX & UCST R8

KEYMILE PEC: EN/LZTBU 980 415/512 RA

3 Summary of network elements 22

3.1.3 Auxiliary equipment 25

6 Compatibility and upgrades 84

7 Software carriers and documentation 93

8.17 MUSIC 100 116

1.1 About this document

Abbreviations used in the tables of this document:

Abbreviation Plain text Description (optional)

1.2 Overview of the multiservice access platform R8B

1.2.1 The UMUX platform

1.2.2 Network elements and units

1.2.3 Traffic services and interfaces

− ATM cross connect

- The SHDSL interface supports transmission rates (up-/downstream) as follows

− Support of Customer Parameter Sets for commissioning of soft switch interoperability

1.2.4 Remote units and services

• PSTN and ISDN interfaces

1.2.5 Management tools and interfaces

1.2.5.1 Management software

The UMUX Multiservice Access Platform has two management toots:

1.2.5.2 Management interfaces

• External management interfaces for local NE access

1.2.6 Signal layers

Table 1-1: Traffic signal layers UCST R8B

UCST R8B Signal rate Layer Description

ATM - - Functional ATM layer on the unit level

P0 64 kbit/s path UCST TDM cross connections

P0_nc n x 64 kbit/s path UCST TDM cross connections

E0 64 kbit/s section Unit functional layer and UNEM

P12 2 Mbit/s path UCST TDM cross connections

E12 2 Mbit/s section Unit functional layer and UNEM

P0 … E12 - - Functional layers 64 kbit/s … 2 Mbit/s on the unit level

E31 34 Mbit/s section Unit functional layer and UNEM

P32 45 Mbit/s path IF on the unit level (FUTURE OPTION)

E32 45 Mbit/s section Unit functional layer and UNEM

UCST R8B Signal rate Layer Description

Undefined - - Rate not yet defined

2.1.1 R8B SP01

2.1.2 R8B SP02

Transparent 2048 2048 P12 yes no no na na na

Clock master 2048 2048 P12 yes no no na na na

Terminated nx64 2048 P12 yes no no na na na

Synchronous nx64 nx64, n ≤ 31 nx64 kbit/s yes no no av na na

Synchronous nx64 nx64, n ≤ 2 nx64 kbit/s yes yes no av av na

Synchronous 48/56 48/56 Subrate yes yes no av av na

Synchronous 0.6 ... 38.4 0.6 … 38.4 Subrate yes yes no av av na

Synchronous 0.6 … 19.2 0.6 … 19.2 Subrate Mux yes yes no na na na

Asynchronous 0.6 … 38.4 0.6 … 38.4 Subrate yes yes no av av na

Asynchronous 0.6 … 19.2 0.6 … 19.2 Subrate Mux yes yes no na na na

na: not applicable

Compatibility of the DATA<X> R3

2.2 Correction of deficiencies

2.2.1 Cleared limitations

2.2.2 New ESW for current function units

ESW Rev. notes Correction of deficiencies Features changed with ESW

ESW Rev. notes Correction of deficiencies Features changed with ESW

ISBUQ R3L 26-03-08 Several fixes for issues related to None

ISBUT R3L 26-03-08 Several fixes for issues related to None

SYNAC R3D 11-02-08 Several fixes for issues related to None

IPLMA R1G 16-11-07 Several fixes for issues related to None