Tellabs 8100 Managed Access System Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Reference Manual

Tellabs ® 8100 Managed Access System
Tellabs ® 8184 Access Switch and Tellabs ® 8188

Access Switch Reference Manual
12348_04
30.05.08
Document Information
Revision History
Docu- Date Description of Changes

ment
No.
12348_04 30.05.08 SFP order codes removed from chapter 3.14.
Jitter generation specification in STM-16, STM-4 and STM-1 optical interfaces
changed from G.825 to G.813 Option 1 in chapter 3.14.
Jitter generation specification in STM-1 electrical interfaces changed from
G.825 to G.812 in chapter 3.14 and in the reference table.
12348_03 08.04.08 SCZ545 software version data removed in chapter 2.2.2.
IUM-5T and IUM-10T removed from the table for applicable interface units
in chapter 2.2.3.
12348_02 29.02.08 GMX2 power supply data added in chapter 3.1.
P12s (E1) Termination fault table updated in chapter 3.12.2.
A detailed module list removed and a reference to Technical Specifications
chapter added in chapter 3.13.
GMX2 input voltage added in chapter 3.14.
STM-4 data edited and distance values added in chapter 3.14.
Node-level information improvements added in chapter 4.2.3.
PAU-10T added in chapter 4.3.4.
SCU-H power data table added in chapter 4.7.1.
The term power feed unit changed to power fuse unit throughout the document.
Figures 10 and 12 edited.
© 2008 Tellabs. All rights reserved.
This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and
treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws.
Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties.
The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or
other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, and T symbol ®.
Any other company or product names may be trademarks of their respective companies.
The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.
Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Tellabs ® 8100 Managed Access System 12348_04

Tellabs ® 8184 Access Switch and Tellabs ® 8188 Access Switch Reference Manual © 2008 Tellabs.
2
Terms and Abbreviations
Term Explanation
ADM Add-Drop Multiplexer
AIS Alarm Indication Signal
ATM Asynchronous Transfer Mode
BBE Background Block Errors
CAS Channel Associated Signalling
CLT Circuit Loop Test
DMA Deferred Maintenance Alarm
DSL Digital Subscriber Line
ECC Embedded Communication Channel
ES Electrical Section
ES Errored Seconds
GUI Graphical User Interface
LED Light Emitting Diode
LAN Local Area Network
LOF Loss of Frame
LOP Loss of Pointer
MLOF Loss of Multiframe
MEI Maintenance Event Information
MLM Multi-Longitudinal Mode
MSP Multiplex Section Protection
NE Network Element
NTU Network Terminating Unit
OS Optical Section
PDH Plesiochronous Digital Hierarchy
PMA Prompt Maintenance Alarm
PMS Performance Monitoring System
POH Path Overhead
PSC Protection Switch Count
PSD Protection Switch Duration
QoS Quality of Signal
QoSTR Quality of Signal Threshold Reset
RDI Remote Defect Indicator
RS Regenerator Section
12348_04 Tellabs ® 8100 Managed Access System

© 2008 Tellabs. Tellabs ® 8184 Access Switch and Tellabs ® 8188 Access Switch Reference Manual
3
SDH Synchronous Digital Hierarchy

SEC Synchronous Equipment Clock
SES Severely Errored Seconds
SFP Small Form-Factor Pluggable
SLM Signal Label Mismatch
SLM Single-Longitudinal Mode
SNC/I Sub-Network Connection Protection - Inherent
SNC/N Sub-Network Connection Protection - Non-Intrusive
SOH Section Overhead
SSF Server Signal Fail
TIM Trace Identifier Mismatch
UART Universal Asynchronous Receiver/Transmitter
UAS Unavailable Seconds
VLAN Virtual Local Area Network
VTP Virtual Token Protocol
Compliance Statement
Hereby, Tellabs Oy declares that this product is in compliance with the essential requirements and
other relevant provisions of Directive 1999 / 5 /EC.

4
Table of Contents
Table of Contents
About This Manual ............................................................................................................ 7
Objectives....................................................................................................................................................................... 7
Audience......................................................................................................................................................................... 7
Related Documentation .................................................................................................................................................. 7
Discontinued Products.................................................................................................................................................... 7
Document Conventions .................................................................................................................................................. 8
Documentation Feedback............................................................................................................................................... 8
1 System Overview......................................................................................................... 9
1.1 General................................................................................................................................................................. 9
1.2 Applications......................................................................................................................................................... 10
1.3 Management ........................................................................................................................................................ 11
1.4 Features................................................................................................................................................................ 11
2 Network Element Overview ........................................................................................ 12
2.1 Introduction ......................................................................................................................................................... 12

2.2 NE Structure ........................................................................................................................................................ 13
2.2.1 Subrack and Equipping........................................................................................................................ 13
2.2.2 Core Units............................................................................................................................................ 15
2.2.3 Interface Units ..................................................................................................................................... 16
2.3 NE Features ......................................................................................................................................................... 17
2.3.1 Backplane Cross-Connect Buses ......................................................................................................... 17
2.3.2 Synchronization ................................................................................................................................... 18
2.3.3 Network Management Communication............................................................................................... 18
2.4 Technical Specifications ...................................................................................................................................... 19
3 GMX2 SDH Interface and Cross-Connect Unit ......................................................... 20
3.1 Main Features ...................................................................................................................................................... 20

3.2 Termination and Cross-Connection Capacities ................................................................................................... 22
3.3 VC-12 Mapping Modes ....................................................................................................................................... 23
3.3.1 Byte Synchronous Mapping without E1 Frame .................................................................................. 23
3.3.2 Byte Synchronous Mapping with E1 Frame........................................................................................ 23
3.3.3 Asynchronous Mapping with E1 Frame.............................................................................................. 24
3.3.4 Asynchronous Mapping of Full E1 Signal with E1 Monitoring ......................................................... 24
3.3.5 Asynchronous Mapping of Full 2048 kbit/s Signal............................................................................. 25

5
Table of Contents
3.3.6 Signal Timing in Receive Direction .................................................................................................... 25

3.3.7 Signal Timing in Transmit Direction................................................................................................... 25
3.4 Traffic Protection ................................................................................................................................................. 25
3.4.1 Subnetwork Connection (SNC) Protection.......................................................................................... 25
3.4.2 Multiplex Section (MS 1+1) Trail Protection...................................................................................... 26
3.4.3 Trunk Recovery ................................................................................................................................... 26
3.5 GMX2 Protection ................................................................................................................................................ 27
3.6 Synchronization ................................................................................................................................................... 28
3.7 Virtual Concatenation .......................................................................................................................................... 29
3.8 Software Updates................................................................................................................................................. 29
3.9 Management Communication Channels.............................................................................................................. 30
3.10 Test Functions...................................................................................................................................................... 30
3.11 Performance Monitoring...................................................................................................................................... 31
3.11.1 Monitored Events and Layers.............................................................................................................. 31
3.11.2 Threshold Function.............................................................................................................................. 31
3.12 Fault Monitoring.................................................................................................................................................. 33
3.12.1 Terminology......................................................................................................................................... 33
3.12.2 Fault Tables.......................................................................................................................................... 33
3.13 Mechanics, Connectors and LEDs....................................................................................................................... 45
4 SCU-H Control Unit ..................................................................................................... 53
4.1 General................................................................................................................................................................. 53
4.2 Operation ............................................................................................................................................................. 53
4.2.1 General................................................................................................................................................. 53
4.2.2 Data Links for Internal Use ................................................................................................................. 54
4.2.3 Voltage Monitoring.............................................................................................................................. 56
4.2.4 Fan Unit Interface and Temperature Monitoring................................................................................. 56
4.3 Node Level Operations........................................................................................................................................ 56
4.3.1 Node Inventory Management .............................................................................................................. 56
4.3.2 Backup of Unit Settings....................................................................................................................... 57
4.3.3 Protection of Cross-Connection System.............................................................................................. 57
4.3.4 Subrack Alarms ................................................................................................................................... 57
4.3.5 Event Reporting to Network Management System ............................................................................. 58
4.3.6 N x 64 kbit/s Channel Test Functions.................................................................................................. 58
4.4 Faults and Actions ............................................................................................................................................... 59
4.4.1 Terminology......................................................................................................................................... 59
4.4.2 Fault Tables.......................................................................................................................................... 59
4.5 Front Panel and Connectors................................................................................................................................. 64
4.5.1 Service Computer (SC) Interface ........................................................................................................ 65
4.5.2 Ethernet Interface ................................................................................................................................ 66
4.5.3 Alarm Interface.................................................................................................................................... 66
4.6 Cabling................................................................................................................................................................. 67
4.7.1 Control Interface Specifications .......................................................................................................... 68
References......................................................................................................................... 69

6
About This Manual
About This Manual

This section discusses the objectives and intended audience of this manual, Tellabs ® 8100 Managed
Access System Tellabs ® 8184 Access Switch and Tellabs ® 8188 Access Switch Reference
Manual and consists of the following sections:
• Objectives
• Audience
• Related Documentation
• Document Conventions
• Documentation Feedback
Objectives
The goal is to describe the network element features of Tellabs 8184 access switch and Tellabs 8188
access switch including GMX2, SCU-H and FAN2.
Audience
This manual is intended for system specialists and personnel involved in network planning.
Related Documentation
Tellabs ® 8100 Managed Access System Node Describes Tellabs 8100 network element features.
Technical Description (12118_XX)
Tellabs ® 8100 Managed Access System Describes Tellabs 8100 network element interfaces.
Interface Guide (12322_XX)
Discontinued Products
Tellabs ® 8100 Managed Access System Discontinued Products list can be found in Tellabs Portal,
www. portal.tellabs.com by navigating to Product Information -> Technical Documentation ->
Managed Access - Tellabs 8100 -> Network Element Manuals -> 8100 List of Discontinued
Products.

7
About This Manual
Document Conventions
This is a note symbol. It emphasizes or supplements information in the document.
This is a caution symbol. It indicates that damage to equipment is possible if the instructions
are not followed.
This is a warning symbol. It indicates that bodily injury is possible if the instructions are not
followed.
Documentation Feedback
Please contact us to suggest improvements or to report errors in our documentation:
Email: fi-documentation@tellabs.com
Fax: +358.9.4131.2430

8
1 System Overview
1 System Overview
1.1 General
Tellabs ® 8100 managed access system is a flexible and fully managed access solution for service
providers. The Tellabs 8100 system consists of various modular cross-connect elements, a number
of Network Terminating Units (NTUs) and an intelligent network management system, Tellabs ®
8000 network manager.
Tellabs ® 8184 access switch and Tellabs ® 8188 access switch are high capacity Network
Elements (NEs) belonging to the Tellabs 8100 system. The main node functionality is based
on a GMX2 cross-connect unit which is a Tellabs 8184 access switch and Tellabs 8188 access
switch specific plug-in unit. Both switches are 4/1/0 cross-connect nodes supporting most of the
interface units used in the other Tellabs 8100 network elements. The high capacity Synchronous
Digital Hierarchy (SDH) interfaces, including STM-16, STM-4 and STM-1 offer a flexible way to
connect to the SDH core network. It is also possible to operate the NEs without STM-N interfaces
as PDH cross-connects. Element and service management operations can be executed through
Tellabs 8000 network manager GUI-based tools. The NEs are designed for indoor installation at
telecommunication centers.
GMX2 as a part of Tellabs 8184 access switch and Tellabs 8188 access switch architecture provides
cross-connection functionality at 4/4, 4/1 and 1/0 levels. The functionality of both switches is
identical, but the physical size and 1/0 capacity differs. Tellabs 8184 access switch has 17 slots in
total in a single subrack, whereas Tellabs 8188 access switch is based on a double subrack and
provides 32 slots in total. There are several X-buses in both nodes, which also enable the use of the
existing Tellabs 8100 interface units in the configuration. The X-bus capacity is 128 x 2M in Tellabs
8184 access switch and 256 x 2M in Tellabs 8188 access switch.
The two-slot wide GMX2 cross-connect unit itself provides five SDH interfaces. There is one
STM-16 interface and four STM-1/STM-4 interfaces, which can be independently configured.
If GMX2 is duplicated for redundancy, the number of SDH interfaces available on GMX2s is
ten. All the previously mentioned interfaces use standard Small Form-Factor Pluggable (SFP)
optical/electrical transceiver modules which can be chosen based on the reach requirements.
Resulting from the fact that the SDH interfaces are integrated with the GMX2 unit, there is more
space for the user-selectable interface units that connect to the X-bus.
When the common units are placed to the nodes there are 10-11 slots in Tellabs 8184 access switch
and 23 slots in Tellabs 8188 access switch available for the Tellabs 8100 interface units. These
units have various types of external ports such as E1, E3, V.35, voice, xDSL. In the element
backplane the X-buses traverse through 3..4 contiguous slots, which should be taken into account in
the element configuration.

9
1 System Overview
1.2 Applications
The flexibility of Tellabs 8184 access switch and Tellabs 8188 access switch allows deploying the
elements to different network topologies and locations. The element can function as a multiservice
access grooming element or purely as a 1/0 cross-connect element or as a combination of the two.
Fig. 1 Tellabs 8184 Access Switch and Tellabs 8188 Access Switch in the Network
A typical way to deploy both switches is to use them for access grooming and consolidate various
services over copper, fiber or leased lines from the access towards the network. The interface slots
provided by the switches can be used, for instance, for the following:
• Digital Subscriber Line (DSL) termination from Tellabs 8110 NTUs

• Ethernet services including Ethernet Virtual Local Area Network (VLAN) switching
• Plesiochronous Digital Hierarchy (PDH) transport through framed E1, E2 or E3 interfaces
• SDH aggregation from Tellabs 8100 or 3rd party access devices

10
1 System Overview
Another possibility is to take advantage of the vast 1/0 cross-connection capacity of GMX2 and
utilize Tellabs 8184 access switch or Tellabs 8188 access switch as a 1/0 cross-connection server on
a site where timeslot-level traffic optimization is justified. Tellabs 8184 access switch or Tellabs
8188 access switch could be colocated with an SDH node to perform the 1/0 traffic optimization
and provide savings in port and transport related costs. In this application both switches could be
equipped with the GMX2 unit(s) without any other interface units.
1.3 Management
As a part of the Tellabs 8100 system, Tellabs 8184 access switch and Tellabs 8188 access switch
are fully managed with Tellabs 8000 network manager. All interface, service and connection level
parameters are configured remotely via the Tellabs 8000 network manager GUI-based tools. The
8100 Service Computer is available for on-site connection to the NE. The same management
processes used with any Tellabs 8100 element apply to both Tellabs 8184 access switch and Tellabs
8188 access switch as well.
1.4 Features
• STM-N ADM 4/1/0 and DXC 4/1/0 applications

• STM-16, STM-4, STM-1 interfaces, SFP modules
• MSP 1+1 protections (G.841 unidir, bidir APS)
• max. 72 x AU-4 port 4/4
• max. 16 x TUG port 4/1 (TU-12 ... TU-12-mc)
• 4/4 and 4/1 SNC/I, N protections
• max. 760 x 2M port 1/0 (VC-12, VC-12-mc, P12s)
• 1/0 with 64 k granularity and w/wo CAS
• 4/4, 4/1, 1/0 matrix equipment protection
• max. 8 x X-bus = 256 x 2M (existing Tellabs 81xx 1/0 tributary units)
• Tellabs 8100 management communication in RS, MS, VC-4, VC-12 and P12s OH, up to 60 links
• RS, MS, VC-4, Vc-12, P12s [G.826] PMS
• [G.813] option 1 (SEC) node clock
• Test features as in earlier Tellabs 8100 nodes (loops, Tellabs 8000 manager CLT)

11
2 Network Element Overview
2.1 Introduction
Tellabs 8184 access switch and Tellabs 8188 access switch support a number of existing Tellabs
8100 interface units with various types of external ports adapting their port signals to the internal
n x 64 kbit/s format of the NE. The 64 kbit/s layer can connect only synchronous signals and
therefore all NEs as well as customer equipment connected to Tellabs 8100 networks must be
synchronized to a common clock source. Tellabs 8184 access switch and Tellabs 8188 access
switch have a [G.813]-compatible clock and provide all necessary functions for the NE and network
synchronization. See the functional blocks of both Tellabs 8184 access switch and Tellabs 8188
access switch in the figure below.
Fig. 2 Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Block Diagram

12
2.2 NE Structure
2.2.1 Subrack and Equipping
Tellabs 8184 access switch with the dimensions of 434 x 431 x 239 mm (w x h x d) is a 19” subrack
RXS2-S. A fan unit, a cable duct and an air baffle are integrated into the subrack and included in
the subrack height. The backplane provides wiring between the plug-in units and has no active
components. Four subracks can be installed into a 43U high rack.
The plug-in units are inserted and removed at the front of the subrack. Unit live insertion and
removal is allowed without interference with other units. All cable connectors are seated in the front
panel of the plug-in units. The plug-in units come in two types: the core units and the optional
interface units.
At the minimum, the RXS2-S subrack is equipped with single core units: the power fuse unit
PFU-A, the control unit SCU-H and the SDH unit GMX2 with the required STM-N modules. The
fixed slots for the core units are depicted in the figure below. Up to 11 interface units (X-IFU) can
be equipped into any vacant slots.
PFU-A and GMX2 may be duplicated for protection independently from each other. If PFU-B is
added, 10 slots are left for the interface units. Interface units cannot be inserted in the GMX2 slots.
Fig. 3 Tellabs 8184 Access Switch Equipped with Duplicated Core Units (Left) and Single
Core Units (Right)
Tellabs 8188 access switch with the dimensions of 436 x 736 x 239 mm (w x h x d) is a dual shelf
19” subrack RXS2-D. Two subracks can be installed into one 43U high rack.
At the minimum, the RXS2-D subrack is equipped with single core units: the power fuse unit
PFU-H, the control unit SCU-H and the SDH Unit GMX2 with the required STM-N modules.
The fixed slots for the core units are depicted in the figure below. Up to 23 interface units can be
equipped into any vacant slots. Slots 8 and 9 are reserved for cooling purposes.
PFU-H and GMX2 may be duplicated for protection independently from each other. 23 slots are
available for the interface units even when both are duplicated.

13
Fig. 4 Tellabs 8188 Access Switch Equipped with Duplicated Core Units (Left) and Single
Core Units (Right)
FAN2 Unit
The subrack is shipped with the mandatory FAN2 unit (RXS 808) in place. The FAN2 unit is placed
beneath the subrack and it takes in air from the front below the subrack and forces air through the
plug-in units and out from the top of the subrack. The FAN2 unit has three fans and an air filter. The
FAN2 unit and the air filter for FAN2 can be replaced while the NE is in operation.
SCU-H monitors the operation of the fan (see the monitored alarms in the SCU-H technical
description). SCU-H controls the fan speed based on the measured temperature within the SCU-H
and GMX2 units. Should the SCU-H unit fail totally the fans will automatically assume their
maximum speed. In case one of the three fans fails cooling is still sufficient for prolonged operation.
The front panel of the FAN2 unit has three LEDs.
LED Name Color Description

Power ON GREEN Battery voltage on
Alarm PMA RED ON when more than one fan has failed
Alarm DMA YELLOW ON when one fan has failed

14
FAN2 Unit Specifications

Dimensions 433 x 65 x 184 mm (w x h x d)
Weight 2.5 kg
Power consumption Min 9 W (at minimum fan speed)
Max. 40 W (fans at full speed)
Recommended time to replace the FAN2 unit when less than three days
a single fan has failed
Maximum time to replace the FAN2 unit when less than one day
more than one fan has failed
GMX2 temperature should be followed. If an
alarm is generated urgent replacement is needed.
Expected fan lifetime 70 000 hours at 40 °C
Recommended filter renewal period 6 months
2.2.2 Core Units
Power Fuse Units
Tellabs 8184 access switch and Tellabs 8188 access switch can be powered from -48 V DC nominal
battery voltage. The power fuse units supply the battery voltage to the backplane. Other plug-in
units generate their required voltages with on-board DC/DC converters. The power fuse unit and the
power supply cable can be duplicated for protection.
Tellabs 8184 access switch uses PFU-A as the power fuse unit and PFU-B is added for the protected
operation. Tellabs 8188 access switch uses PFU-H as the power fuse unit and PFU-H is duplicated
for the protected operation.
PFU-A, PFU-B and PFU-H are the same units that can also be used in other Tellabs 8100 NEs. For
further details refer to the technical descriptions of the power supply units.
SCU-H Control Unit
The SCU-H control unit supervises the operation of the NE and communicates with Tellabs 8000
manager. SCU-H is the same unit that can also be used in other Tellabs 8100 NEs. The control
unit in the Tellabs 8100 NEs has not been deemed critical for the operation of transmission and
cross-connection and thus duplication of SCU-H is not supported.
Chapter 4 SCU-H Control Unit provides more details.
GMX2 SDH Interface and Cross-Connect Unit
The GMX2 unit has STM-N interfaces and it does cross-connection at three levels.
More details and the supported SFP interface module types are listed in chapter 3 GMX2 SDH
Interface and Cross-Connect Unit.

15
2.2.3 Interface Units
The following table lists the applicable interface units supported by Tellabs 8184 access switch and
Tellabs 8188 access switch.
Refer to Tellabs ® 8100 Managed Access System Interface Guide (document number 12322_XX)
for more information on the product compatibilities for nodes/switches, interface units and
interface modules in the Tellabs 8100 system and the restrictions in the context of the EMC
and safety-related issues with discontinued products.
Unit Name Unit Description

AIU1:11 ATM interface unit
AIU1:41
CAE Voice frequency interface unit
CEU1 ATM circuit emulation unit
CCO-UNI POTS interface unit, PBX end
CCS-UNI POTS interface unit, subscriber end
E3C G.751 framed 34 Mbit/s interface unit with 16
G.704 signals
ESU Ethernet switching unit
FBU1 Flexbus interface unit
FRU1 Frame relay switch unit
GMH G.704 framed interface unit, 2 interfaces
GMM T1 interface unit
GMU1 SDH interface unit
GMU-M1
GMU-A SDH interface unit
IUM-81 DSL interface unit for Tellabs 8110 STU-160 DSL
NTUs
ISD-LT1 Transparent basic rate ISDN U-interface unit
ISD-LT161 Transparent basic rate ISDN U-interface unit
ISD-NT1 Transparent basic rate ISDN U-interface unit

LIU-H1 LAN interconnect unit
OMH/OMH-A G.704 framed interface unit, 8 interfaces
QMH G.704 framed interface unit, 4 interfaces

QMH-M1 G.703 unframed 2048 kbit/s interface unit
VCM-5T-A Unframed data interface unit in n x 64 kbit/s mode
VCM-10T-A
1The product has been discontinued.

16
2.3 NE Features
2.3.1 Backplane Cross-Connect Buses
Tellabs 8184 access switch realizes four internal 64 kbit/s buses (X-bus, each with 64 Mbit/s
capacity) each of which spans over two or three unit slots. The X-buses in neither of the NEs are
duplicated for protection. The interface units in adjacent slots share one bus as follows (slot 2
available when PFU-B is not equipped):
Fig. 5 X-bus Segments in Tellabs 8184 Access Switch
Tellabs 8188 access switch realizes eight internal 64 kbit/s buses each of which spans over two
or three unit slots. Four buses are in the lower shelf and four in the upper shelf. The slots are
grouped as follows:

17
Fig. 6 X-bus Segments in Tellabs 8188 Access Switch
2.3.2 Synchronization
Both Tellabs 8184 access switch and Tellabs 8188 access switch provide complete synchronization
functions with multiple reference clocks, automatic clock selection, holdover and clock downstream
distribution. The NE has an internal timing generator compliant with the Synchronous Equipment
Clock (SEC) defined in G.813 Option 1. The SEC functions mainly reside in the GMX2 unit. The
required quality of the reference clocks depends on the application. For SDH equipment having at
least one STM-N ports the quality of the reference clocks must comply with [G.823]
2.3.3 Network Management Communication
Communication messages between Tellabs 8000 network manager and Tellabs 8100 NEs use a
proprietary protocol. The messages can be carried in channels embedded in the frame structure of
inter-NE signals and routed in the NEs. Several options are available for the placement of the
embedded communication channel (ECC): for example the STM-N frame in the GMX2 unit and the
E1 frame in the QMH unit (when furnished).

18
2.4 Technical Specifications
Tellabs 8188 access switch subrack 436 x 736 x 239 mm (w x h x d)

physical size Standard 19-inch rack or cabinet mounting.
The height is 17U (1U = 44.45 mm)
Tellabs 8184 access switch subrack 434 x 431 x 239 mm (w x h x d)
physical size Standard 19-inch rack or cabinet mounting.
The height is 10U (1U = 44.45 mm)
Tellabs 8188 access switch subrack 15.0 kg without adapters and plug-in units.
weight 35.0 kg when fully equipped.
Tellabs 8184 access switch subrack 9.0 kg without adapters and plug-in units.
weight 19.5 kg when fully equipped.
Safety compatibility [EN 60950-1:2001]
Electromagnetic compatibility [EN 300 386 V1.3.3: 2005]
Climatic/mechanical compatibility Storage:
[ETSI EN 300 019-1-1] Class 1.1
Temperature: -5° C to +45° C
Transportation:
[ETSI EN 300 019-1-2] Class 2.3
Temperature: -40° C to +70° C2
Operating Conditions:
[ETSI EN 300 019-1-3] Class 3.23
Temperature: -5° C to +45° C
Relative humidity: 5% to 95%
Usage altitude up to 3000 m above sea level (i.e. air pressure
70–106 kPa )
Input voltage Nominal -48 V DC
Absolute range -40.5 to -60 V DC
Power consumption Tellabs 8184 access switch max. 240 W (PFU-A limit)
Tellabs 8188 access switch max. 500 W
Maximum current Tellabs 8184 access switch 6 A
Tellabs 8188 access switch 12.4 A
N x 64 kbit/s signal pass-through – for connections from E1 port in e.g. QMH to STM-N port
delay for Tellabs 8184 access switch when QMH buffer is configured short < 375 µs
and Tellabs 8188 access switch – for connections from STM-N port to E1 port in QMH when
QMH buffer is configured short < 400 µs
– for connections from E1 port in e.g. QMH to STM-N port
when QMH buffer is configured long (effect of X-bus allocation
disregarded) < 510 µs
– for connections from STM-N port to E1 port in QMH when
QMH buffer is configured long < 515 µs
– for PDH connections from E1 port to another E1 port in QMH
with short buffers < 375 µs
– for PDH connections from E1 port to another E1 port in QMH
with long buffers < 625 µs
– for 1/0 server applications from STM-N port to n x 64 kbit/s
matrix and back to STM-N port < 400 µs
2Rain is not allowed.

3Condensation is not allowed.

19
3 GMX2 SDH Interface and Cross-Connect Unit
3.1 Main Features
In the role of SDH ADM/multiplexer GMX2 is equipped with up to five STM-N ports and it
connects AU-4 and TU-12 between the STM-N ports, n x 64 kbit/s signals between the STM-N
ports and X-IFUs and n x 64 kbit/s signals between X-IFUs.
In the role of 1/0 server (n x 64 kbit/s grooming) GMX2 connects n x 64 kbit/s (and AU-4 and
TU-12) signals between the STM-N ports. In the 1/0 server role the NE usually does not have
X-IFUs equipped.
In the role of PDH cross-connect GMX2 operates without STM-N ports and cross-connects n x
64 kbit/s signals between X-IFUs.
The main features of GMX2 are listed in the following:
• several port types

• one STM-16 optical port plus
• four STM-4 optical ports or
• four STM-1 optical/electrical ports
• total port capacity 32 STM-1 equivalents, with two GMX2 units 64 STM-1 equivalent capacity
• STM-N ports realized with SFP modules (types listed in chapter 3.13 Mechanics, Connectors and
LEDs)
• optional GMX2 unit 1+1 protection
• add/drop capacity 8 VC-4 per NE
• 72 port AU-4 cross-connection (32 + 32 + 8 drop) per NE
• 1008 port TU-12 cross-connection per NE
• termination of 8 VC-4 and 504 VC-12 per NE
• VC-12 asynchronous or byte synchronous mapping
• optionally termination of E1 [G.704] frame in each VC-12
• n x 64 kbit/s cross-connection with 504 E1 equivalent capacity upstream and 256 E1 equivalent
capacity downstream per NE
• MS 1+1 uni/bidirectional protection
• SNC/I or SNC/N protection for 24 VC-4 pairs
• SNC/I or SNC/N protection for 252 VC-12 pairs
• VC-12-mc Tellabs proprietary virtual concatenation
• NE synchronization as specified in [G.813]

20
• 72 HDLC channels for management communication per NE

• performance and fault monitoring on all SDH and PDH layers
• power supply: -48 V nominal input voltage
Fig. 7 GMX2 unit

21
3.2 Termination and Cross-Connection Capacities
The GMX2 unit provides the following cross-connection capacities stated as bidirectional AU-4,
TU-12 or E1 equivalent ports:
• the AU-4 matrix (VC-4_C) has 64 ports for the STM-N interfaces plus 8 add/drop ports.
• the TU-12 matrix (VC-12_C) has 504 ports towards the STM-N interfaces plus 504 ports towards
the n x 64 kbit/s matrix.
• the n x 64 kbit/s and Channel Associated Signalling (CAS) matrix has 504 E1 port equivalents
towards the STM-N interfaces and 256 E1 port equivalents towards the backplane buses and the
interface units.
Fig. 8 Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Cross-Connect Capacities

22
GMX2 has the following VC-4, VC-12 and E1 trail termination capacities:
• 8 VC-4 trail terminations

• 504 VC-12 trail terminations
• 504 E1 trail terminations with optional CAS
Additionally, GMX2 provides 32 VC-4 and 504 VC-12 non-intrusive monitoring resources which
can be used in SNC/N protection.
The stand-by GMX2 does not terminate VCs but passes AU-4s in its STM-N ports via internal links
to the active GMX2 which terminates the VCs as required.
3.3 VC-12 Mapping Modes
GMX2 provides several VC-12 mapping modes as in [G.783] but also provides some proprietary
extensions. The mapping mode can be configured per VC-12 to suit the application. The choice
of the mapping mode should mainly depend on whether the VC-12 is used for a trunk connection
between Tellabs 8100 NEs or for a customer access port.
3.3.1 Byte Synchronous Mapping without E1 Frame
On trunk lines through SDH networks byte synchronous mapping without E1 frame provides most
payload capacity, 32 or 34 bytes per VC-12 if the R bytes are configured into use. Signal integrity
end-to-end is supervised using VC-12 overhead (E1 frame would be an unnecessary duplication).
An embedded communication channel for Tellabs 8000 manager can be configured to a VC-12
byte as described later.
In this mapping GMX2 terminates the received VC-12 overhead and forwards the payload, which
may consist of one or more n x 64 kbit/s signals plus possible CAS, to the 64 kbit/s cross-connect
matrix. In the transmit direction GMX2 adds the VC-12 overhead and one or more n x 64 kbit/s
signals plus possible CAS coming from the matrix. It is recommended to enable CAS capacity to all
trunk lines if CAS is used in the network so that Tellabs 8000 manager does not reserve timeslot
16 for n x 64 kbit/s payload.
3.3.2 Byte Synchronous Mapping with E1 Frame
On trunk lines traversing PDH and SDH networks E1 frame must be added for end-to-end
supervision. Payload capacity is 31 bytes per VC-12. A control channel can be configured to a
timeslot (1 to 31) in the E1 frame.
In this mapping GMX2 terminates the received VC-12 and E1 overhead and forwards the
payload, which may consist of one or more n x 64 kbit/s signals plus possible CAS, to 64 kbit/s
cross-connection. Timeslot 0 mode is set to FSW/RAI regenerate and CRC4 in B1 is activated.

23
3.3.3 Asynchronous Mapping with E1 Frame
VC-12 access ports must usually use asynchronous mapping with E1 frame as this mode is used by
most equipment. Payload capacity is 31 bytes per VC-12. This mode can also be used on trunk
lines. In this mapping GMX2 terminates the received VC-12 and E1 overhead and forwards the
payload, which may consist of one or more n x 64 kbit/s signals plus possible CAS, to 64 kbit/s
cross-connection.
GMX2 can forward a part or all of the E1 overhead in timeslot 0 (TS0) in the customer signal to the
Tellabs 8100 transport network to allow end-to-end supervision by the customer or to support the
use of TS0 bits for special customer applications. In the transport network TS0 bits are connected as
a 64 kbit/s payload byte. The following three configuration options are possible:
• standard TS0 termination (regeneration) mode is selected with FSW/RAI regenerate. Then the
Frame Synchronization Word (FSW) and Remote Alarm Indication (RAI) are inserted into the
transmit signal and removed and monitored in the receive direction as defined in [G.704] and
[G.706]. Also possible CAS multriframe and RAI is generated towards the customer equipment.
This mode must also be selected on E1 trunk lines.
• FSW and RAI X-connect mode where FSW and RAI are copied to the transmit E1 signal towards
the customer from the 64 kbit/s matrix and where FSW and RAI coming in from the STM-N
port are forwarded to the 64 kbit/s matrix. In the transmit direction GMX2 synchronizes to the
alternation of even and odd frames and the alarm X-bus AIS is reported if this synchronization
fails. It means that the connection is broken somewhere in the Tellabs 8100 network and that
GMX2 must insert AIS to the egress E1.
• FSW and RAI X-connect plus invert mode which is similar to the above but GMX2 inverts TS0
bits in both transmission directions. This is important when TS0 is transported on E1 links (not
using CRC4) where it could be harmful if a payload permanently contains a byte simulating FSW.
The following additional configurations to TS0 bits are possible:
• The state of the transmitted free bits (B4...B8) can be configured to 0, 1 or one of the bits can be
used to transmit Synchronization Status Messages (SSM) This applies also for trunk lines.
• Any or all of bits B4-B8 can be passed to/from the 64 kbit/s matrix and cross-connected in the
Tellabs 8100 network in a payload byte.
• B1 can be transmitted as 0, 1 or used for CRC4. It can also be cross-connected permitting CRC4
supervision of E1 by the customer in the following situation: all E1 bytes sent to customer equip-
ment must be identical with the bytes entering the Tellabs 8100 network. All TS0 bits which may
change must be transported. If any payload bytes are not transported, their content must be fixed
and inserted to the E1 signal to customer.
3.3.4 Asynchronous Mapping of Full E1 Signal with E1 Monitoring
Asynchronous mapping of full E1 signal with E1 monitoring is used in VC-12 access ports when
G.704 framed E1 signal from the customer is transported in Tellabs 8100 network. A P12s function
is activated to non-intrusively monitor the signal as it enters the Tellabs 8100 network.
In this mode GMX2 terminates the received VC-12 overhead and forwards the payload, which
GMX2 treats as a single E1 framed payload, to cross-connection. GMX2 supervises the E1 frame
and can report faults and performance in the E1 frame. GMX2 can act on the signal during faults
AIS and LOF and depending on configuration, forward AIS.

24
3.3.5 Asynchronous Mapping of Full 2048 kbit/s Signal
Asynchronous mapping of full 2048 kbit/s signal is used in VC-12 access ports when framed or
unframed 2048 kbit/s signal from the customer is transported in Tellabs 8100 network.
In this mode GMX2 terminates the received VC-12 overhead and forwards the payload, which
GMX2 treats as a single 2048 kbit/s payload, to the cross-connection. The signal is not supervised.
3.3.6 Signal Timing in Receive Direction
In all mapping modes the incoming payload rate must be in synchronism with the n x 64 kbit/s
matrix (NE) clock. This is necessary because the n x 64 kbit/s layer provides no means to carry
timing information. Thus, the end device which generates the n x 64 kbit/s payloads and which may
reside at customer premises at remote sites must be synchronized to a common clock with the NE.
In the transmission network jitter and wander may accumulate to the signals. In the receive direction
GMX2 has buffers which can absorb the amount of jitter and wander specified in [G.823] plus
wander caused by pointer adjustments.
If synchronization fails the incoming signals may have permanent frequency offset relative to the
NE clock. GMX2 then must adapt the signals by producing slips of one frame in the receive buffers.
The slip interval will depend on the frequency offset. It can be calculated as follows:
125s/ f, where offset f is in ppm (parts per million).
3.3.7 Signal Timing in Transmit Direction
In all mapping modes the transmit signals are timed from the NE clock. Also VC-4 and VC-12
which are terminated in the NE are timed from the NE clock.
3.4 Traffic Protection
3.4.1 Subnetwork Connection (SNC) Protection
The standard SNC/N (non-intrusive) and SNC/I (inherent) protection is supported for the full
capacity. Any two VC-4 or VC-12 can be selected to the protection group. After the protected
section the single unprotected VC-4/12 may continue to the drop direction or to any STM-N port.
The monitoring resources needed in SNC/N are dedicated and do not consume other terminating
resources. SNC is also supported for concatenated trails. The capacities are as follows:
• max. 24 VC-4 groups (32 not possible even in theory because eight VC-4 trails are needed for
the exiting VC-4)
• max. 252 VC-12 groups
The following configurations can be made:
• revertive or non-revertive mode

• wait-to-restore time in revertive mode from 0 to 65535 s in steps of 1 s

25
• hold-off time from 0 to 10 s in steps of 0.1 s

• commands via Tellabs 8000 manager: Clear, Lockout, Forced switch to protected, Manual switch
to working, Manual switch to protecting
3.4.2 Multiplex Section (MS 1+1) Trail Protection
GMX2 supports the unidirectional (single-ended) and bidirectional (dual-ended) modes defined in
[G.783] and [G.841]. The APS protocol used in the bidirectional mode is compatible with 1:n
operation. In unidirectional operation the protection switch operates independently at both ends
based on MS layer defects which are detected locally and on possible commands via Tellabs 8000
manager. In bidirectional operation the protection switch is also affected by requests from the
remote end carried in APS messages. 1:1 mode or extra traffic is not supported.
Any two STM-N ports with the same capacity and in different GMX2 units can be set to MS 1+1
mode. The working section is always in the main GMX2 (left) and the protecting section, which
transmits the APS bytes, is in the protecting GMX2.
The following configurations can be made:
• revertive or non-revertive mode

• wait-to-restore time in revertive mode from 0 to 65535 s in steps of 1 s
• commands via Tellabs 8000 manager: Clear, Lockout to working, Forced switch to working,
Forced switch to protected, Manual switch to working, Manual switch to protecting
3.4.3 Trunk Recovery
GMX2 supports trunk recovery operations actuated by Tellabs 8000 manager for interface units
(X-IFUs) which have similar X-bus ports (for example E1 port in the E3C and QMH units). The
X-IFUs may reside on the same or on a different X-bus. E1 trunks in VC-12 in GMX2 cannot
participate in the trunk recovery configurations.

26
3.5 GMX2 Protection
GMX2 can be optionally duplicated for protection. One GMX2 is active and the other is in stand-by
mode. When the NE boots up, the main GMX2 (left) will normally assume the active role. Each
GMX2 processes the SDH layers OS/ES, RS and MS in its local STM-N interfaces. The stand-by
unit passes its AU-4s to/from the active GMX2 which processes the payload in all ports.
GMX2 monitors its internal operation and SCU-H supervises the operation of the GMX2 units and
forces a switchover if it deems that the active unit fails to operate correctly. The protection mode is
non-revertive. The protected layers include AU-4 and above up to the backplane bus interface. The
STM-N interfaces are not protected and if one GMX2 fails totally, the traffic in its STM-N ports
will be lost (unless traffic protection is used). The stand-by unit should never be removed unless
the unit has failed and has to be replaced or it has no traffic in its STM-N ports or all traffic is
protected and can be switched to the other unit.
When a replacement unit is inserted it will automatically copy configuration and cross-connections
from SCU-H and the active GMX2.
When GMX2 is not protected, the NE cannot hold all backup information. Then Tellabs 8000
manager delivers backup information to the replacement GMX2 when the unit is raised to In Use
state.
Switchovers are hitless for AU-4s and TU-12s passing through the GMX2s unterminated. Hitless
switchover cannot be guaranteed for n x 64 kbit/s signals passing through GMX2s in server
applications and for n x 64 kbit/s signals connected to/from X-IFUs.

27
3.6 Synchronization
GMX2 synchronization system for SDH equipment includes automatic clock selection, multiple
reference clocks and Synchronous Equipment Clock (SEC) generator compliant with [G.813]
Option 1. The synchronization system can also be applied for NEs without STM-N ports and
accepting lower quality reference clocks.
In the NEs having at least one STM-N port the received signal from the following ports can be
selected to supply a reference clock:
• STM-N traffic ports in GMX2s and in GMU-A

• 2048 and 8448 kbit/s ports in X-IFUs (fixed clock quality must be used and the NEs with lower
than SEC level clocks such as e.g. Tellabs 8150 basic node should be used as a reference)
• framed/unframed station clock ports (2048 kbit/s/2048 kHz) in GMX2s
Jitter and wander in the reference clocks must comply with [G.823] and jitter and wander tolerance
of synchronization interfaces referred to in [G.813].
In the NEs without any STM-N ports the received signal from the following ports can be selected
to supply a reference clock:
• 2048, 8448 and n x 64 kbit/s ports in X-IFUs

• framed/unframed station clock ports (2048 kbit/s/2048 kHz) in GMX2s
Jitter and wander in the reference clocks must comply with [G.823] jitter and wander tolerance of
traffic interfaces. It is important that these interfaces are not used as a clock reference with STM-N
ports because wander in the STM-N ports could exceed specifications.
The user can enter up to 10 ports to the clock selection priority list (fallback list). Traffic ports can
be used after the corresponding modules have been locked (Installed or In Use state). The station
clock has to be enabled before it can be selected.
The use of the standard Synchronization Status Messages (SSM) and quality levels can be enabled.
In such cases the clock selection process automatically selects the reference with the highest
quality and priority.
GMX2 has one station clock input port (SCI) and one station clock output port (SCO). When
GMX2 is duplicated the two SCI ports are independent inputs which are configured and entered
to the clock selection list separately. However, only one set of parameters defines the two SCO
ports. Each GMX2 drives its own SCO port.

28
3.7 Virtual Concatenation
GMX2 implements the Tellabs proprietary VC-12-mc virtual concatenation, which is compatible
with GMU, GMX and certain Tellabs 6300 products. VC-12-mc can be applied on trunk lines
between the Tellabs 8100 NEs to support higher capacity payloads and also to enhance capacity
utilization. The main features are listed in the following:
• one VC-12-mc can consist of 2 to 63 VC-12s (VC-12-2c to VC-12-63c)

• all VC-12 capacity can be concatenated (to multiple groups)
• any free VC-12 can be assigned to any VC-12-mc
• VC-12s in one group can have 32 or 34 payload bytes (using R bytes)
• configuration of AIS sending downstream when one received VC-12 is defective either to all
group members or to single VC-12
• not compatible with the standard VC-12-xv
• propagation delay difference between VC-12s within one group max. 250 µs
• uses the 500 µs H4-multiframe to align the frame phase of the received VC-12
• uses byte synchronous mapping with 4-frame receive buffer
When Tellabs 8000 manager/Router allocates TU-12s from SDH 4/1 trunks, all TU-12s in a group
are chosen from one VC-4 to avoid adding delay difference to VC-12. When the group members
are in one VC-4, the VC-12s can pass through a fairly large number of NEs which process the
signals down to the VC-12 level. NEs which only have VC-4 or lower layer processing do not add
to the delay difference. If the members in one group should belong to more than one VC-4, be
sure not to route the VC-4s through different physical paths which could easily lead to excessive
delay difference.
3.8 Software Updates
The software GMZ802 can be downloaded to GMX2 with Tellabs 8000 manager and SC.
Downloading causes GMX2 software and hardware to reset before the downloaded software can be
taken into use.
When GMX2 is not duplicated a reset shuts down all interfaces until GMX2 has booted up. The
boot up time depends on the configuration and on the number of cross-connections and is typically
from 5 to about 60 seconds.
When GMX2 is duplicated software is downloaded to the stand-by unit whose STM-N ports will be
shut down whereas the active GMX2 continues normal operation. Traffic in the STM-N ports during
shut down will be lost unless line protection is used.
The yellow LED will blink during software download. It is important neither to switch off the
power nor configure the unit simultaneously.

29
3.9 Management Communication Channels
For the Tellabs 8000 manager communication, GMX2 provides 8 + 64 HDLC resources for creating
64 kbit/s Embedded Communication Channels (ECC) to trunk lines. Eight resources are for use
in the Section Overhead (SOH) and the VC-4 Path Overhead (POH) bytes. 64 resources can be
configured to the VC-12 bytes. The number of available HDLC channels is the same irrespective of
GMX2 duplication. The large number of HDLC channels allows GMX2 to be used as a hub where
messages are routed to several directions. By configuring ECCs to VC-4 or VC-12, the remote
Tellabs 8100 NEs can be reached through foreign SDH networks.
ECCs can be configured to the following SOH bytes:
• Regenerator SOH: E1, F1

• Multiplex SOH: E2
ECCs can be configured to the following VC-4 POH bytes:
• F2, F3
ECCs can be configured to the following bytes in the payload of any VC-12:
• TS1/2/3/ .../31 (also TS0 in byte synchronous mapping without E1 frame)

• R0/R1 in byte synchronous mapping
R1 in asynchronous mapping
ECCs should be protected against link and equipment failures by setting up redundant paths with
the Tellabs 8000 manager. Tellabs 8000 manager monitors the ECCs and switches to the backup
route in case it cannot reach the target NE within a timeout period. The NEs can also autonomously
recover ECCs when traffic protection is used. For example, when ECCs are set up within VC-4
or VC-12, which are protected by SNC/I or SNC/N, the protection switch by the NE will restore
communication before Tellabs 8000 manager has time to react. However, ECCs in SOH of MS
1+1 protected trails can not be restored by NEs. Instead, Tellabs 8000 manager must in this case
restore communication using the backup route.
When the two GMX2 units operate normally they can route incoming messages irrespective of
which GMX2 is active. However, message routing will fail if the main (left) GMX2 fails or is
removed from the subrack. In this case Tellabs 8000 manager must restore communication by
switching to a backup route.
3.10 Test Functions
GMX2 supports the following tests:
• n x 64 kbit/s Circuit Loop Tests (CLT) tool in Tellabs 8000 manager

• VC-4/-12 CLT tool in Tellabs 8000 manager
• GMX2 STM-N Interface equipment loop activated via Node Manager or 8100 Service Computer
• error counters accessible via Node Manager or 8100 Service Computer

30
3.11 Performance Monitoring
3.11.1 Monitored Events and Layers
GMX2 implements bidirectional performance data collection for 15-minute and 24-hour periods
following the models in [EN 300 417-7-1] and [EN 301 167]. The monitoring function produces
the performance parameters Errored Seconds (ES), Severely Errored Seconds (SES), Background
Block Errors (BBE) and Unavailable Seconds (UAS), accumulates their values over 15 minutes and
24 hours for the near end and far end and reports alarms to Tellabs 8000 manager if the near end
error counts reach the provisioned thresholds.
Event counts are collected for regenerator, multiplex and protected multiplex sections and for the
termination functions on higher, lower and P12s path layers and protected subnetwork layers for
the near end and far end where applicable. The NEs also support the additional events Protection
Switch Count (PSC) and Protection Switch Duration (PSD) as listed in the following table:
Moni- RS MS MSP VC-4 SNC VC-12 P12s

tored (E1)
Events
nES x x – x – x x
fES – x – x – x x
nSES x x – x – x x
fSES – x – x – x x
nBBE x x – x – x x
fBBE – x – x – x x
nUAS x x – x – x x
fUAS – x – x – x x
PSC – – x – x – –
PSD – – x – x – –
3.11.2 Threshold Function
The threshold mechanism generates alarm reports to Tellabs 8000 manager when the performance of
a transport entity falls below the configured level.
As soon as the threshold is reached in a 24-hour period for an event, Quality of Service (QoS) alarm
is reported. The QoS alarm is removed at the end of the 24-hour period. The threshold values can be
configured with Tellabs 8000 manager. The NE supports 30 sets of different values.
As soon as the upper threshold is reached for an event in a 15-minute period, Quality of Service
Threshold Reset (QoSTR) alarm is reported. No reports are generated in the subsequent periods
until the count at the end of a period stays below the lower limit. Then the QoSTR alarm is removed
from the fault list.
QoS and QoSTR alarms in GMX2 are common to the events BBE, ES and SES. QoS or QoSTR is
reported if any of the three events reaches its threshold. Other simultaneous events are not reported.
QoSTR stays on until all events that have reached the upper limit stay below the lower limit.

31
The supported threshold functions and their default values are shown below. The lower limit for a
15-minute SES is zero.
Blocks/s 24 h 24 h 24 h 15 15 15 15 15
nBBE nES nSES min min min min min
nBBE nBBE nES nES nSES
lower up- lower up- up-
per per per
RS-1 8000 48000 1500 20 200 9000 20 180 15
RS- 8000 48000 N/A 20 200 9000 N/A N/A 15
4/16
MS-1 192000 432000 150 15 2400 288000 5 50 10
MS-4 768000 3456000 N/A 15 19200 76800 N/A N/A 10
MS- 3072000 13824000 N/A 15 2304000 9216000 N/A N/A 10
16
VC-4 8000 48000 1500 20 200 36000 20 180 15
VC- 2000 12000 350 20 50 9600 5 120 15
12
P12s 1000 6000 350 20 25 4500 5 120 15
(CRC4)

32
3.12 Fault Monitoring
The processing of transmission related faults follows the standard model in [EN 300 417-7-1]. It
includes filters (f1...f3) to find out the fault cause and to report failures to Tellabs 8000 manager. It
also drives the unit LED indicators.
The criteria for detecting and clearing defects in received STM-N and E1 signals follows [G.783].
3.12.1 Terminology
Maintenance Status
PMA = Prompt Maintenance Alarm
DMA = Deferred Maintenance Alarm

MEI = Maintenance Event Information
Service Status
S = Service alarm
LED Indications
R = Red alarm LED
Y = Yellow alarm LED
3.12.2 Fault Tables
Optical and Electrical Section (OS, ES) Termination and Adaptation

Fault Condition Status Conse-
and LED quent Ac-
tions
“LOS” PMA, S + RxAIS
Loss of Signal. Loss of signal defect is declared when a supervised signal R
has not had any transitions for a period of time or the signal indicating
degradation of level in the received signal is activated.
“Equipment loop” MEI, S + Y -
Signal transmitted out is also looped back to the receiver of the interface.

33

and LED quent Ac-
tions
“Unexpected SFP module type” MEI + Y -
SFP transceiver module type does not match with the expected type.
“Faults masked” MEI + Y -
Reporting of the faults on this layer may be set ON, OFF or Faults masked
(like OFF but reports the Fault masked reminder to Tellabs 8000 manager).
The fault is activated when the interface Fault mask setting is on.
Regenerator Section (RS) Termination

and LED quent Ac-
tions
“LOF” PMA, S + RxAIS
Loss of Frame. Frame alignment of the STM-N frame is lost. R
“TIM” PMA, S + RxAIS
Trace Identifier Mismatch. The received TI (RxTI) does not match the R
expected one (ExTI).
“TIM” MEI + Y -
Trace Identifier Mismatch. The received TI (RxTI) does not match the
expected one (ExTI) and TIM actions disabled.
“DEGraded errors” DMA + R -
Signal degrade. Once every second, block errors shall be compared with
the limit value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise is shall be declared GOOD. The Signal Degrade defect
(dDEG) shall be detected if M consecutive BAD seconds have occurred.
The signal Degrade defect (dDEG) shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2...9.
“UNAVAIL” PMA, S -
Performance monitoring in an unavailable state [G.774.01]. The
bidirectional UAT begins when 10 consecutive SES seconds are detected.
UAT ends when 10 consecutive non-SES seconds are detected.
“QOS” DMA -
Quality of Signal. A configured performance threshold in any of the events
ES, SES, BBE is reached in 24 h period. Cleared when a period changes.
“QOSTR” DMA -
Quality of Signal Threshold Reset. A configured performance threshold
in any of the events ES, SES, BBE is reached in 15 min period. Cleared
when found a period where none of the ES, BBE or SES limits has been
exceeded.
Note that ES and BBE have upper/lower limit so that the upper must be
exceeded to get a fault and the lower is used as a limit when the fault
is activated.
“SSF” MEI, S + Y RxAIS
Server Signal Fail. The layer below this layer indicates a defect which
disrupts the signal. SSF may be reported on this layer if enabled.

34

and LED quent Ac-
tions
“Performance event” MEI -
This delta alarm tells Tellabs 8000 manager that the performance registers
hold non-zero data to collect, i.e. as least one of the performance event
counters differs from zero during the last 15-minute period.
Multiplex Section (MS) Termination

and LED quent Ac-
tions
“AIS” MEI, S + Y RxAIS,
Alarm Indication Signal. The received K2[6–8] = 111 in five consecutive TxRDI
frames.
“RDI” MEI + Y -
Remote defect indicator. The received K2[6–8] = 110 in five consecutive
frames.
“QOS” DMA -
“QOSTR” DMA -
exceeded.
is activated.
“SSF” MEI, S + Y -
Server Signal Fail. The layer below this layer indicates a defect which

35

and LED quent Ac-
tions
MS/VC-4 Adaptation
and LED quent Ac-
tions
“AIS” MEI, S + Y RxAIS
Alarm Indication Signal. AU-4 AIS received.
“LOP” PMA, S RxAIS
Loss of Pointer. AU-4 pointer invalid. +R
VC-4 Termination
and LED quent Ac-
tions
“TIM” PMA, S + RxAIS,
Trace Identifier Mismatch. The received TI (RxTI) does not match the R TxRDI
“TIM” MEI + Y -
“UNEQ” PMA, S + RxAIS,
Unequipped signal received. The received signal label is all zeroes in five R TxRDI
consecutive frames.
“RDI” MEI + Y -
frames.

36

and LED quent Ac-
tions
Performance monitoring in an unavailable state [G.774.01]). The
“QOS” DMA -
“QOSTR” DMA -
exceeded.
is activated.
“SSF” MEI, S + Y RxAIS,
Server Signal Fail. The layer below this layer indicates a defect which TxRDI
“VC-4 loop” MEI, S + Y -
The received VC-4 is looped back to STM-N.
“SLM” PMA, S + RxAIS
Signal Label Mismatch. The received Signal Label (RxSL) does not R
match the expected one (ExSL) in five consecutive frames.
“MLOF” PMA, S + RxAIS
Loss of Multiframe Alignment. Detected if the H4 OOM state persists R
for 16 frames.
VC-4/VC-12 Adaptation
and LED quent Ac-
tions
“AIS” MEI, S + Y RxAIS
Alarm Indication Signal. TU-12 AIS received.
“LOP” PMA, S RxAIS
Loss of Pointer. TU-12 pointer invalid. +R

37
VC-12 Termination
and LED quent Ac-
tions
“TIM” PMA, S + RxAIS,
Trace Identifier Mismatch. The received TI (RxTI) does not match the R TxRDI
“TIM” MEI + Y -
“UNEQ” PMA, S + RxAIS,
Unequipped signal received. The received signal label is all zeroes in five R TxRDI
consecutive frames.
“RDI” MEI + Y -
frames.
Performance monitoring in an unavailable state [G.774.01]). The
“QOS” DMA -
“QOSTR” DMA -
exceeded.
is activated.
“SSF” MEI, S + Y RxAIS,
Server Signal Fail. The layer below this layer indicates a defect which TxRDI
“VC12 loop” MEI, S + Y -
The received VC-12 is looped back to STM-N.

38

and LED quent Ac-
tions
“SLM” PMA, S + RxAIS
Signal Label Mismatch. The received Signal Label (RxSL) does not R
match the expected one (ExSL) in five consecutive frames.
VC-12/P12s Adaptation
and LED quent Ac-
tions
“AIS” MEI, S + Y RxAIS,
Alarm Indication Signal. An all 1’s signal detected in the received E1 TxRDI-E1
signal.
“LOF” PMA, S + RxAIS,
Loss of Frame. Frame alignment of the E1 [G.704] frame lost. R TxRDI-E1
P12s (E1) Termination

and LED quent Ac-
tions
When CRC4 in E1 frame is disabled: Detected if N or more errored
Frame Alignment Signals occurred in M consecutive seconds. Cleared if
less than N errored Frame Alignment Signals occurred in M consecutive
seconds. This fault is detected when CRC4 in E1 frame is disabled
When CRC4 in E1 frame is enabled: Detected if M consecutive bad
seconds occurred. A second is bad if near end block error count pNEBC
>= N (=DEGTHR).
“RDI” MEI + Y -
Remote defect indicator. The received RDI is one in three consecutive
frames.
“QOS” DMA -

39

and LED quent Ac-
tions
“QOSTR” DMA -
exceeded.
is activated.
“Faults masked” MEI+Y -
“AIS from 1/0 direction” MEI, S+Y TxAIS-E1
This fault is detected only in configurations where TimeSlot0 FSW and
RAI are transported in the Tellabs 8100 network.
P12s-TS16 (CAS) Termination

and LED quent Ac-
tions
“MAIS” MEI, S + Y RxAIS-
Alarm Indication Signal. TS16 AIS received. TS16,
TxRDI-
TS16
“MLOF” PMA ,S + RxAIS-
Loss of Multiframe. Alignment of the TS16 multiframe lost. R TS16,
TxRDI-
TS16
“CAS multiframe RDI” MEI, S + Y -
Remote defect indicator. The received RDI is one in three consecutive
frames.
Multiplex Section 1+1 Protection

and LED quent Ac-
tions
“Group Failed” PMA, S + RxAIS
Both working and protecting channels failed when using MS 1+1 or SNC R
protection.
“Group degraded” DMA + R -
Block errors indicated read from MS 1+1 protected TTP or connection
protection group.

40

and LED quent Ac-
tions
“Failure of APS protocol” DMA + R -
In bi-directional mode: incompatible mode at remote end or request active
but no reply from remote end or protection switching time not within
50 ms.
“SSF (working)” DMA + R -
Server Signal Fail. Protected channel has a serious fault (MS 1+1 or SNC
protection).
“SSF (protecting)” DMA + R -
Server Signal Fail. Protecting channel has a serious fault (MS 1+1 or
SNC protection).
Subnetwork Connection (SNC) Protection

and LED quent Ac-
tions
“Protection group failed” PMA, S + RxAIS
Both the working and the protecting signal failed. R
“Protection group degraded” DMA + R -
The selected, better signal has DEG defect.
“SSF (working)” DMA + R -
Server Signal Fail. Protected channel has a serious fault (MS 1+1 or SNC
protection).
“SSF (protecting)” DMA + R -
Server Signal Fail. Protecting channel has a serious fault (MS 1+1 or
SNC protection).
Synchronization
and LED quent Ac-
tions
“Loss of Timing Inputs” DMA + Y -
All references on the fallback list failed. SEC in holdover.
“Fallback list warning” MEI -
More than one entry on the fallback list but only one entry is usable.
This warning is blocked if quality levels are enabled (for the ring
synchronization case).
“Excessive frequency offset fallback list entry i” DMA -
Frequency of the reference clock is out of the PLL locking range of the
fallback list entry i.

41

and LED quent Ac-
tions
“Fallback list i priority used” MEI + Y -
The i (i = 2nd to 10th) clock in the order of priority on the fallback list
is selected.
“Forced clock selection” MEI + Y -
The user has in Node Manager forced the selection of a clock entry on the
fallback list with external command.
Station Clock Input (SCI)

Fault Condition (the SCI is Monitored Only When Enabled) Status Conse-
and LED quent Ac-
tions
“Station Clock Input Loss of Signal” DMA + Y -
External clock enabled and failed.
“Station Clock Input Loss of Frame” DMA + Y -
External clock enabled and failed. Frame alignment of the E1 [G.704]
frame is lost.
“Station Clock Input AIS” DMA + Y -
Alarm Indication Signal. An all 1’s signal is detected in the E1-framed
mode.
X-bus Interface Unit Fault

and LED quent Ac-
tions
“Unit IA fault” PMA, S + -
The interface unit in slot N failed to return the test pattern sent by GMX2 Y
on the X-bus.
GMX2 Equipment Faults

and LED quent Ac-
tions
“Reset” PMA, S + -
The unit has been reset (the fault is reported always after power-up). R
“FLASH checksum error” PMA + R -
Non-volatile memory error. The calculated checksum does not match
the stored one.
“FLASH list checksum error” PMA, S + -
One of the FLASH lists (e.g. port descriptor list) has been corrupted. R
“X-connect FLASH list conflict” MEI -
A corrupt cross-connect record has been detected after unit reset. The
record has been deleted.
“PortDesc FLASH list conflict” MEI -
A corrupt port descriptor record has been detected after unit reset. The

42

and LED quent Ac-
tions
“Swapped trunk FLASH list conflict” MEI -
A corrupt swap-trunk record has been detected after unit reset. The record
has been deleted.
“Passivate trunk FLASH list conflict” MEI -
A corrupt passivate-trunk record has been detected after unit reset. The
“Reconfiguring X-connect database” PMA + R -
The stand-by GMX2 has detected that its cross-connection records are not
identical with the active GMX2 and it is copying those records.
“SW unpredicted” PMA, S + -
This fault condition should never occur (or is not yet supported). R
“Missing settings” PMA, S + -
The structure of the unit’s settings has been corrupted in FLASH. R
“Settings corrupted” PMA + R -
Corrupted data detected in the unit’s functional settings block in FLASH.
Fatal setup corruption. The unit must be configured again, or it must be
replaced with a slot where compatible unit is registered; the unit inherits
the settings.
“Start permission denied” PMA, S + Rx X-bus
Most likely the unit does not belong to the NE configuration. R IF off
Tx idle
“Extended backup unit fault” PMA + Y -
The SCU-H unit holding extended backups is not responding. Probably it
is missing or not in the inventory.
“No extended backup unit address” PMA + R -
The SCU-H unit does not return the address of the extended backup unit.
Capacity of the extended backup unit may have run out.
“Reading extended backup settings” PMA + R -
Unit is reading its extended backup setting from the ext. backup unit.
Do not interrupt.
“Parameter inconsistency with the peer unit (resetting)” PMA, S + -
Unit has copied parameters from the peer unit and needs to reset in order R
to take the parameters into use.
“Reading backup from peer unit” PMA + R -
The unit is reading parameter backups from the peer unit. The copy
operation is ongoing. It may take a few minutes.
“Peer backup unit fault” PMA + R -
The unit holding backups is not responding. Probably it is missing.
Parameter copying from peer unit has failed.
“X-connect bus alarm” PMA, S + -
One or more of the internal data buses has failed the bus tests. The cause R
probably is in GMX2.
“Inter cross-connection unit bus fault” DMA + R -
One or more of the internal AU-4 links (SSI) between the two GMX2s
is faulty.
“SEC is not functioning” PMA, S + -

SEC hardware is not operating correctly. R

43

and LED quent Ac-
tions
“Framer master clock is missing” PMA, S + -
The master clock of the framer is not operating correctly. R
“78 Mhz is missing” PMA, S + -
The 78 MHz oscillator is not operating correctly. R
“SEC is missing auxiliary frequency” PMA, S + -
Baseboard is not supplying auxiliary frequency to SEC. R
“Temperature too high” MEI + Y -
Unit temperature has exceeded the limits of guaranteed proper operation.
“Operation degraded due to too high temperature (resetting)” DMA, S + -
Some of the unit operations are disabled to cool the unit. Unit will reset R
after cooling period.

44
3.13 Mechanics, Connectors and LEDs
The GMX2 unit measures 163 x 233 mm and is 9.5 T ( T =5.08 mm) wide. The unit consists of
the GMX2 hardware with the unit software GMZ802 and 0...5 STM-N SFP modules. The only
changeable physical modules are the SFP modules. GMX2 is shipped without the SFP modules.
Only modules approved by Tellabs are allowed to be used. The SFP modules can be changed to a
live unit. GMX2 can be removed from and inserted to a powered NE.
Fig. 9 GMX2 Connectors and LEDs

45
GMX2 has three LEDs as listed in the following:
• Red LED: PMA alarm, generally indicates that this unit has detected a major fault in incoming
signals or in the unit itself.
• Yellow LED: DMA/MEI alarm, generally indicates that this unit has detected a secondary fault
(e.g. AIS, RDI) in incoming signals or a minor fault in the unit itself.
• Blinking yellow LED: Unit is programming FLASH device (e.g. storing parameters or down-
loading software). Do not switch off the power nor remove the unit from the NE.
• Green LED indicates which of the two GMX2 units is the active unit. Note that also the stand-by
unit may have active STM-N ports and cannot be removed from the subrack without causing loss
of signal in these ports.
The STM-N ports are realized with SFP modules. The optical SFP modules have duplex LC
connectors for single mode fibre. There are five SFP slots in GMX2. The optical ports are designed
for class I laser and outside-plant use. Interface 1 supports only STM-16 optical modules. The rest
of the interfaces support STM-4 optical or STM-1 optical/electrical modules. For more details on
module types approved by Tellabs and their specifications, refer to 3.14 Technical Specifications.
The synchronization interface has connectors for both 75 ohm coaxial and 120 ohm symmetrical
signals. One of the interfaces is selected by connecting a suitable cable. Cables can be connected to
only one (75 or 120 ohm) interface at a time. The coaxial interface uses 50 ohm SMB receptables.
The 120 ohm interface uses a 9-pin D-type connector receptable. The synchronization interface
is for intrastation use only.
9-Pin D-Type Connector Pin Numbering

Pin Name Pin Name
1 Input B 6 Ground
2 Input A 7 Ground
3 Ground 8 Ground
4 Output B 9 Ground
5 Output A

46
GMX2
Dimensions (w x h 48 x 160 x 233 mm
x d)
Weight 0.8 kg
Power consumption • Typical 24 W
• Max. 30 W
Input voltage • Nominal -48 V DC
• Absolute range -40.5 to -60 V DC
GMX2 - Matrix 4/4 Matrix type 72-port (40 if GMX2 is not protected)
T-S, non-blocking
Cross-connection VC-4
level
Connection types • Unidirectional
• Bidirectional
• Loop
Connection capacity 72 x STM-1 port equivalent (64 aggregate ports and 8
tributary ports)
GMX2 - Matrix 4/1 Matrix type 16-port; 8 ports towards 1/0 Matrix and 8 ports towards
4/4 Matrix
T-S, non-blocking
Cross-connection VC-12
level
Connection types • Unidirectional
• Bidirectional
• Loop
Connection capacity 16 x STM-1 port equivalent (8 aggregate ports and 8
tributary ports)
GMX2 - Matrix 1/0 Cross-connection Synchronous timeslot interleaving
method
Granularity 64 kbit/s and 2 kbit/s (CAS)
Capacity 16 x 64 Mbit/s
Termination and Frame structures STM-1, STM-4 and STM-16 [G.707]
mapping
Trail termination • 8 x VC-4
• 504 x VC-12
• 504 x G.704
Mapping • Asynchronous (32 TS port)
• Byte synchronous (34 TS port)
Virtual VC-12-mc
concatenation

47
Node timing data Node master clock SEC, [G.813]/[G.781] compliant

Master clock • Locking to the STM-1 aggregate interface Rx clock
functional modes
• Locking to external clock input
• Hold-over mode as in [G.813]
• Clock fallback list (5 levels + internal mode)
Pull-in range ± 4.6 ppm
External clock input • Frequency 2048 kHz
• [G.703] synchronization interface 75/120 Ω
External clock • Frequency 2048 kHz
output
• Locked to node master clock
• [G.703] synchronization interface 75/120 Ω
External clock • 75 Ω, SMB-type connector
connector type
• 120 Ω, D-type 9-pin female connector
Signal pass-through • in the receive buffers < 230 µs
delays in the GMX2
blocks • in the transmit buffers < 3 µs
• in the n x 64 kbit/s matrix in receive and transmit direction 125 µs (average,
disregards effects of change of timeslot in the cross-connection)
• in the TU-12 matrix in receive and transmit direction < 4 µs
• in the TU-12 pointer processor in the receive direction < 30 µs
• in the AU-4 matrix in receive and transmit direction < 1 µs
• For concatenated signals the above holds true but the delay in the receive
buffers < 440 µs.
The total delay for • from X-bus to STM-N (transmit direction) < 135 µs
n x 64 kbit/s signals
in GMX2 • from STM-N to X-bus (receive direction) < 390 µs
• from STM-N to X-bus (receive direction) for concatenated signals < 600 µs

48
STM-16 Optical Interfaces

Parameter Value Unit
General
Specifications [G.957]
according to
Nominal bit rate 2 488 320 kbit/s
Jitter generation [G.813] Option 1
Jitter tolerance [G.825]
Class S-16.1 L-16.1 L-16.2
Connector Duplex LC Duplex LC Duplex LC
Distance 15 40 80 km
Transmitter
Source type SLM SLM SLM
Operating 1260 – 1360 1280 – 1335 1500 – 1580 nm
wavelength
Mean launched -5 to 0 -2 to 3 -2 to 3 dBm
power
Min. extinction 8.2 8.2 8.2 dB
ratio
Optical path
Attenuation 0 to 12 10 to 24 10 to 24 dB
range
Max. discrete -27 -27 -27 dB
reflectance
Receiver
Min. sensitivity -18 -27 -28 dBm
Min. overload 0 -9 -9 dBm

49

General
according to
Nominal bit rate 622 080 kbit/s
Class S-4.1 L-4.1 L-4.2
Transmitter
Source type MLM SLM SLM
Operating 1293 – 1334/ 1280 – 1335 1480 – 1580 nm
wavelength 1274 – 1356
Mean launched -15 to -8 -3 to 2 -3 to 2 dBm
power
Min. extinction 8.2 10 10 dB
ratio
Optical path
range
Max. discrete NA -25 -27 dB
reflectance
Receiver
Min. overload -8 -8 -8 dBm

50

General
according to
Class S-1.1 L-1.1 L-1.2
Transmitter
Source type MLM SLM SLM
Operating 1261 – 1360 1263 – 1360 1480 – 1580 nm
wavelength
Mean launched -15 to -8 -5 to 0 -5 to 0 dBm
power
Min. extinction 8.2 10 10 dB
ratio
Optical path
range
Max. discrete NA NA -25 dB
reflectance
Receiver
Min. overload -8 -10 -10 dBm

51
STM-1 Electrical Interfaces

Parameter Value
General
Specifications according to [G.703]
Jitter generation [G.812]
Class STM-1-E
Connector DIN 1.0/2.3
Output port specifications Table 12/[G.703]
Input port specifications Max. insertion loss of 12.7 dB at 78 MHz (√f law)
Cross-connect point specifications Power level -2.5 to +4.3 dBm, no DC power (> 300 MHz
measurement bandwidth)
Distance This is for intrastation use only (typical distance 100 m)

52
4 SCU-H Control Unit
4.1 General
The SCU-H control unit can be used in Tellabs 8184 access switch, Tellabs 8188 access switch and
in Tellabs 8160 A111 accelerator node, Tellabs 8150 basic node and in the slave subracks of Tellabs
8170 cluster node. The structure of the SCU-H unit is based on the standard mechanics of the
Tellabs 8100 system. SCU-H consists of the base unit (SCU 587), the processor module (SCM 725),
the power supply module (PDF 593 or PDF 594) and the unit software (SCZ545). For use in Tellabs
8184 access switch or in Tellabs 8188 access switch the software version must be V2.3 or higher.
The width of SCU-H is 5T or one card slot.
An optional control channel expansion and Ethernet interface module SCP-H (SCP 586) is available,
refer to the SCP-H module technical description for detailed information. SCP-H has an Ethernet
interface and 16 HDLC resources.
The power supply module makes regulated output voltages for the SCU-H unit from the -48 V (PDF
593) or +24 V (PDF 594) battery voltage in the backplane.
4.2 Operation
4.2.1 General
All data processing in the SCU-H unit is done in the processor module which contains the processor
(Intel 386EX), page-mode DRAM memory, sectored flash memory and flash file memory. The
processor module also includes a Universal Asynchronous Receiver/Transmitter (UART), which is
needed for the Service Computer interface. The base unit connects to the X-bus, the Virtual Token
Protocol (VTP) buses and the Service Computer.
The start-up and initialization program of the unit is permanently stored in a sectored flash memory.
The application program is stored in a non-volatile flash file memory and can be updated via Tellabs
8000 manager. The flash file memory is also used to store the system operating parameters.

53
Fig. 10 Block Diagram of the SCU-H Unit with the Optional Module SCP-H
4.2.2 Data Links for Internal Use
VTP Bus
The local VTP bus is used for communication between the units within one subrack. SCU-H
connects to the bus at the backplane. VTP is a collision-free media access method based on the
principle of token passing implemented with the aid of the timers. Fig. 11 shows the VTP bus
configuration.
The VTP bus implements two redundant interfaces and buses. SCU-H controls the protection of the
VTP bus and monitors the state of both interfaces. SCU-H controls the selection of the interfaces
in a synchronized way so that the data transmission on the bus is never disturbed. Both interfaces
are periodically used to detect possible problems as soon as possible, no matter which interface
has failed. A checking procedure is activated when any unit has disappeared from the inventory
monitoring process. The checking procedure determines whether the unit is accessible by only one
interface. If so, then the other interface is faulty and the corresponding fault condition is detected. A
test window can be used to check the local VTP bus status and to clear the fault condition.

54
Fig. 11 VTP Bus Configuration
Cluster VTP Bus
The cluster VTP bus (CBUS) is used for communication between the subracks of the Tellabs 8170
cluster node. The CBUS interface is used only when SCU-H is in the slave subrack of Tellabs
8170 cluster node.
The 15-pin female D-type connector is used. The protocol is proprietary and the maximum cable
length is 20 meters. CBUS cables are available at 2/4/8 m lengths (cabling and connector pin
numbering are depicted in the CCU technical description).
CBUS has a redundant set of wires, drivers and receivers. A local control activates one of the two
receiver circuits. Data is always sent to both physical buses. SCU-H monitors the performance of
the buses. When one bus is found to be worse than the other, the corresponding fault condition
is detected.
HDLC Links with SCP-H
With the optional SCP-H module SCU-H can provide 16 HDLC channels for the Tellabs
8000 manager communication. The channels can be configured to rates 8/16/32/64 kbit/s and
cross-connected as "HDLC trunks" through the Tellabs 8100 network in order to provide direct
(TDM pipes) communication paths between two Tellabs 8100 nodes. The HDLC channels can be
cross-connected to another SCP-H or to the older HDLC-4CH modules in the SCU units.

55
4.2.3 Voltage Monitoring
SCU-H monitors the voltages of its power supply module, on-card regulators and in the backplane
buses plus the power off alarms of the PFU and PAU-10T units. One or two duplicated voltages are
supplied to the backplane by PFU or PAU-10T units depending on the NE type and use of protection.
In RXS2-S, RXS-S, RXS-D and RXS-CD, there is a duplicated 5 V bus on the backplane. Both bus
voltages are fed by PFU-A or PAU-10T. In RXS2-D and RXS-H, there are duplicated buses for 5 V
and 3.3 V bus voltages on the backplane. One PFU-H feeds one 5 V bus and one 3 V bus. Thus, if
PFU-H is duplicated, all voltage buses are active. An alarm is raised if any voltage decreases below
its defined limit. The measurement is permanently calibrated at the factory to improve accuracy.
4.2.4 Fan Unit Interface and Temperature Monitoring
The SCU-H unit controls the subrack fan if one exists. When the temperature of the SCU-H unit is
between the lower (+5°C) and the upper (+50°C) limit, the fans are kept rotating at 50…90% of the
maximum speed depending on the internal temperature. If the temperature rises above the upper
limit the fans are working at maximum speed. The fan unit sends an alarm to SCU-H if one or more
fans are not working properly. SCU-H will forward a DMA alarm to Tellabs 8000 manager and
PFU when one has failed. SCU-H will forward a PMA alarm to Tellabs 8000 manager and PFU
when two or more fans have failed. If the temperature of the SCU-H unit exceeds 65°C, SCU-H
will raise its temperature alarm as a PMA alarm. This might indicate that the filter of the fan unit
needs to be changed.
In Tellabs 8184 access switch and Tellabs 8188 access switch GMX2 also has a temperature sensor.
If the temperature of GMX2 rises above the limit (+70°C) fans are turned to maximum speed.
Tellabs 8184 access switch and Tellabs 8188 access switch also have temperature high alarms
which can be an indication of a filter change need. The temperature alarm is risen when the GMX2
temperature is above +90°C.
4.3 Node Level Operations
4.3.1 Node Inventory Management
The Node Inventory Management software includes functions to get and set node and subrack
identifications, to create and delete inventory, to add and remove units, to get inventory reports and
to monitor the presence of registered or unregistered units. The Create Inventory operation is
used to register all existing units for the inventory. The Add Unit operation is used to register a
given unit for the inventory. The Delete Inventory makes all units unregistered - in other words
all units are removed from the inventory. The Remove Unit operation is used to remove a given
unit from the inventory.
The Inventory Report provides the node and subrack identification data and the list of existing
or registered units. The fault condition Installation Error is detected if the inventory data is not
unambiguous and consistent. The fault condition Missing Unit is detected if a registered unit is
not present. The fault condition Extra Unit is detected if there is an unregistered unit present
in the subrack.

56
4.3.2 Backup of Unit Settings
The SCU-H unit stores the backup settings of the parameters of all registered units for possible unit
replacements. A new replacement unit will inherit the backup settings of the unit registered for the
unit slot. The compatibility of settings is checked based on hardware and software types.
The backup settings are updated to the SCU-H unit when a unit is registered or when the settings of
the unit have been changed. The backup settings are copied from the SCU-H unit when a registered
unit is replaced by another compatible unit. The backup settings of the SCU-H unit itself are kept in
the cross-connect unit of the subrack. The backup of cross-connection data is available only in the
redundant cross-connect units if the node has a protected cross-connection system.
Most interface units do not require extended backup capacity. A node with SCU-H can be fully
equipped with such interface units. However, some interface units (AIU4, CCO-UNI, CCS-UNI,
CEU4, E3C, ESU, GMU4, FBU4, FRU4, LIU-H4, OMH) require extended backup capacity (see the
corresponding unit description). SCU-H provides 800 blocks of extended backup memory.
4.3.3 Protection of Cross-Connection System
The SCU-H unit controls the protection of the cross-connect units (SXU-A, SXU-B, GMX or
GMX2 depending on the NE type). The protection option can be set on or off. In a protected
system SCU-H monitors the condition of both cross-connect units and if the active cross-connect
unit fails, it activates the redundant cross-connect unit. One of the cross-connect units can be
forced to active state by a management operation.
4.3.4 Subrack Alarms
If a unit sets an alarm (or SCU-H gets an external alarm), SCU-H decides the severity of the
alarm/alarms and passes an alarm on to Tellabs 8000 manager, and to its own PMA or DMA LED
and to PFU-A’s, PFU-H’s or PAU-10T’s PMA, DMA or MEI LED and to PFU-A’s, PFU-H’s or
PAU-10T’s PMA, DMA or MEI alarm output relay.
Fig. 12 Subrack Alarm LEDs and Relays
4The unit has been discontinued.

57
4.3.5 Event Reporting to Network Management System
The SCU-H unit does not only supervise the registered units of the subrack for the rack alarms but
also supports subrack-level and node-level status polling from the centralized network management
system as well. The node state report contains the status of the subracks that are not in the normal
state.
The subrack state report contains the status of the units that are not in the normal state. For example,
all changes in fault conditions and configuration are indicated for all units. These reports make it
possible to get detailed information from the correct units for different purposes.
While the subrack state report is created, the route to the polling DXX Server is updated to the
local routing table of the SCU-H unit from the invoke message. This route can be used to send
spontaneous event reports to the DXX Server. The unit reporting modules can send event reports to
the local SCU-H unit, which sends them to the DXX Server. The most important application is the
reporting of trunk fault changes in the trunk recovery management.
4.3.6 N x 64 kbit/s Channel Test Functions
The SCU-H unit contains a test resource which can be configured for n x 8 kbit/s and n x 64 kbit/s
circuit test functions via the Circuit Loop Test (CLT) tool in Tellabs 8000 manager. The test resource
contains a configurable cross-connection port, test loop functions, a test pattern generator and a
receiver. SCU-H can connect the test resource to one X-bus (in NEs with multiple X-buses). The
test functions include create and delete operations which are used to allocate and deallocate the test
resource for a given circuit. They also include operations to determine the test configuration, actions
to activate and deactivate the test port, actions to activate and deactivate test operation and a get
operation to read the test status and the test results. Due to the ASIC code restrictions, there can be
conflicts in CLT if HDLC channels are used and the tested circuit is either in asynchronous timing
mode or the bit rate is higher than 66 x 64 kbit/s.
The test status and the test results include the following data.
• Test status: active (true/false), running (true/false)

• Elapsed time
• Test control performance data
• Error counters
• Slip counters
• Error performance

58
4.4 Faults and Actions
4.4.1 Terminology
Maintenance Status
PMA = Prompt maintenance alarm
DMA = Deferred maintenance alarm

MEI = Maintenance event information
Service Status
S = Service alarm
LED Indications
R = Red alarm LED
Y = Yellow alarm LED
4.4.2 Fault Tables
SW Faults
Fault Condition Status LED Note
"Reset" PMA R
There has been a unit reset (detected always
after the power-up of the unit).
"SW unpredicted" PMA R
This fault condition should never occur (or
not yet supported).
Power Supply and Temperature Faults

"Power +5.0 V (PDF)" PMA R PDF
SCU-H power module failure.
"Power -10.0 V (PDF)" PMA R PDF

59

"Power +5.0 V (Baseboard)" PMA R SCU 587
SCU-H baseboard power failure.
"Power +5.1 V VCC1 (BUS)" PMA R subrack
Node power failure.
"Power +5.1 V VCC2 (BUS)" PMA R subrack
Node power failure.
"Power +3.3 V (Baseboard)" PMA R SCU 587
SCU-H baseboard power failure.
"Power +3.4 V VP3_1 (BUS)" PMA R subrack
Node power failure.
" Power +3.4 V VP3_3 (BUS)" PMA R subrack
Node power failure.
"Temperature (Baseboard)" PMA R SCU 587
The fault is generated if the SCU-H

temperature is below +5 or above +65
Celsius degrees. The fault disappears when
the temperature is above +10 and below +60
Celsius degrees.
Memory Faults
"RAM fault" PMA R
A background process has detected a RAM
location where the read value does not
match with the written test pattern.
"SW chksum error on ROM" PMA R
The calculated check sum does not
match with the stored one on ROM.
"SW chksum error on RAM" PMA R
match with the stored one on RAM.
"EEP(IO)ROM write error" PMA, S R
Error when writing to the memory.
"EEP(IO)ROM check sum error" PMA, S R
The calculated check sum does not match
with the stored one on EEPROM.
"FAN/PFU-H EEP(IO)ROM PMA, S R
Checksum Error"
The calculated check sum does not match
with the stored one on FAN or PFU-H
EEPROM.
"File system fatal error " PMA, S R
Flash system failed. Replace unit
with spare unit.

60

"File system bad block found" MEI Y
One of the blocks in the flash system
is not in use anymore.
"Flash setup check sum error" PMA R
match with the stored one on flash.
"Flash list check sum error" PMA R
One of the flash lists (e.g. port descriptor
list) has been corrupted.
"Missing settings" PMA R
One of the setting structures is missing in
the non-volatile memory.
"Incompatible SW in ROM and FLASH" PMA R
The downloaded software (on the flash) is
not compatible with the system software on
the ROM.
Control Bus Faults

DMA Y 5
"Local VTP Bus 1"
Problems detected in the local control
bus 1. The local control bus 2 is used
permanently from now on. Test the local
control bus and clear the fault from the test
window.
DMA Y 5
"Local VTP Bus 2"
Problems detected in the local control
bus 2. The local control bus 1 is used
permanently from now on. Test the local
window.
"Cluster VTP Bus 1" DMA Y 6
Problems detected in the cluster con-

trol bus 1. The cluster control bus 2 is used
permanently from now on. Test the cluster
window.
DMA Y 6
"Cluster VTP Bus 2"
Problems detected in the cluster con-
trol bus 2. The cluster control bus 1 is used
permanently from now on. Test the cluster
window.
5A test window can be used to check the local VTP status and clear the fault.
6Possible in a slave subrack of a Tellabs 8170 cluster node.

61
Cross-connection Protection Faults

PMA, S Y 7
"Faulty cross-connection system"
Both of the redundant cross-connection
units are faulty.
"Forced state in cross-con- MEI Y
nection unit activation"
One of the redundant cross-connec-
tion units has been forced to be active. The
automatic change-over is not possible.
Inventory Faults
PMA, S R 7
"Installation error"
The inventory must be created.
"Missing unit" PMA, S Y 8
A registered unit is not in its place.

MEI Y 8
"Extra unit"
There is a unit which has not been registered
as a part of the subrack inventory.
Extended Backup Settings Faults

"Initialization errors" PMA R
Initialization phase failed.
"Setup inconsistency" PMA R
Bookkeeping data of backed up units
is corrupted (While this is on, it is rec-
ommended not to replace any units with
compatible ones because it is not guaranteed
that the new unit inherits all of the old unit’s
settings).
PMA R 9
"No Backup Settings (Un)"
No backup settings from unit in address n.
Security Faults
"Authorised access" MEI Y
Authorised access.
"Unauthorised access attempt" PMA Y
Unauthorised access attempted.
7Servicealarm
8The block number indicates the unit address.
9The block number n (1…32) indicates the unit address.

62
Alarms
DMA R 10
"I/O Input alarm"
The fault is activated by the input of the
alarm I/O module.
Protection Faults
"SXU 1 (Primary) activated" MEI
Primary SXU unit is activated.
"SXU 2 (Secondary) activated" MEI
Secondary SXU unit is activated.
"Loss of primary PFU" DMA Y
Primary PFU is not working.
"Loss of secondary PFU" DMA Y
Secondary PFU is not working.
Fan Faults
"FAN unit failure" PMA, S R
FAN unit failure. Two or more fans are
stopped.
"FAN unit failure" DMA Y
FAN unit failure. One fan is stopped.
"FAN unit missing" PMA, S R
FAN2 (RXS 808) unit is missing.
SCP-H Module Faults

"Ethernet chip reset" PMA R
Problems in Ethernet communication
have caused Ethernet chip to reset.
"Incorrect/missing IF module" PMA R
The setup of the SCU-H requires a
specific interface module. The setup or the
module must be changed.
10Contact closure in the external alarm input

63
4.5 Front Panel and Connectors
Fig. 13 shows the mechanical design of SCU-H.
Connectors and LEDs in the Front Panel

Item Description
D1 Red LED for PMA alarm
D2 Yellow LED for DMA alarm
J5 Service Computer Interface
J6 Cluster VTP interface
J4 Alarm interface
D3 Green LED for Activity of the optional LAN interface
D4 Yellow LED for Link Status of the optional LAN interface
J10 Ethernet interface (optional)

64
Fig. 13 Mechanical Design of the SCU-H Unit
4.5.1 Service Computer (SC) Interface
The asynchronous SC interface is a proprietary data link between SCU-H and the Service Computer
or the Tellabs 8000 manager DXX Server. The electrical characteristics are as in V.24/V.28 and bit
rate 9600 bit/s.
The interface type is V.24, except that the connector is a 9-pin female D-type connector instead of an
ISO 2110 25-pin female D-type connector. The electrical interface is V.28. The character format is
8-bit, no parity and 1 stop bit. Protocol levels 2…7 are proprietary.

65
Pin Name I/O Signal

1 Carrier Detect (CD) O 109
2 Transmit Data (TxD) O 104
3 Receive Data (RxD) I 103
4 Data Set Ready (DSR) I 108
5 Ground - 102
6 Data Terminal Ready (DTR) O 107
7 Clear To Send (CTS) I 105
8 Request To Send (RTS) O 106
9 Not connected - -
4.5.2 Ethernet Interface
With the optional SCP-H module SCU-H provides a 10Base-T Ethernet interface for communication
over LANs and IP networks. Pin numbering is shown below.
Pin Name I/O

1 Transmit Data (TxD+) O
2 Transmit Data (TxD-) O
3 Receive Data (RxD+) I
4 - -
5 - -
6 Receive Data (RxD-) I
7 - -
8 - -
4.5.3 Alarm Interface
The alarm interface provides two external alarm outputs and ten inputs. The inputs may be used to
collect alarms from the site, e.g. door alarms. Both outputs and inputs are configurable to high or
low active. A DMA alarm is reported to Tellabs 8000 manager if an input becomes active.
The inputs are current sensing; they are closed when current > 0.5 mA and open when current <
0.1 mA. Sensing voltage is +12 V.
The outputs are relay contacts. Maximum switching voltage is 60 V and maximum switching
current 200 mA. Close state resistance < 100 mohm.
The connector is 25-pin female D-type connector.

66
Pin Name Pin Name

1 Ground 14 Input 1
2 Ground 15 Input 2
3 Ground 16 Input 3
4 Ground 17 Input 4
5 Ground 18 Input 5
6 Ground 19 Input 6
7 Ground 20 Input 7
8 Ground 21 Input 8
9 Ground 22 Input 9
10 Input 10 23 Normally open 2
11 Common 2 24 Normally closed 2
12 Normally closed 1 25 Common 1
13 Normally open 1
4.6 Cabling
The CBUS cable (D15F/M-D15F/M, 2/4/8 m) and CBUS cable H-F (D15F/M-D15F/M, 2/4/8 m)
is depicted in the CCU technical description.
A cable (D9F-D9M, 5m) for the Service Computer is available.
Fig. 14 The Service Computer Cable (D9F-D9M, 5 m)

67
4.7.1 Control Interface Specifications
SC Interface
Purpose Management interface for SC/Tellabs 8000
manager
Electrical interface V.28
Data bit rate 9600 b/s asynchronous
Character format 8 bit, no parity, 1 stop bit
Connector type D-type 9-pin female connector
Interface signals 102, 103, 104, 105, 106, 107, 108 and 109
Protocol Layers 2…7 proprietary
CBUS Interface
Purpose Cluster VTP bus
Electrical levels V.11, redundant drivers and receivers
Data bit rate 1024 kbit/s synchronous
Connector type ISO 4903, D-type 15-pin female connector
Interface signals VTDT1, VTDT2 and VTCL1, VTCL2
Protocol Layers 2…7 proprietary
Physical length of the bus 20 m, maximum
Power Data
Power consumption Max. 9.7 W
Input voltage with PDF593 Nominal -48 V DC
Absolute range -40.5 to -60 V DC
Input voltage with PDF594 Nominal +24 V DC
Absolute range +19 to +32 V DC
Mechanical Data
Size (w x h x d) 25 (5T) x 160 x 233 mm
Weight 0.7 kg

68
References
References
Reference Description
[EN 300 386] EN 300 386 V1.3.3 (2005), Electromagnetic compatibility and radio
spectrum matters (ERM); Telecommunication network equipment;
Electromagnetic compatibility (EMC) requirements
[EN 60950-1] EN 60950-1 (2001), Information technology equipment - Safety -
Part 1: General requirements
[ETSI EN 300 019-1-1] ETSI EN 300 019-1-1 V2.1.4 (2003-04), Environmental conditions
and environmental tests for telecommunication equipment, Part 1-1:
Classification of environmental conditions, storage
Classification of environmental conditions, transportation
Classification of environmental conditions, stationary use at weather
protected locations
[ETSI EN 300 417-2-1] ETSI EN 300 417-2-1 v1.1.3 (1995-05), Transmission and
Multiplexing (TM); Generic requirements of transport functionality
of equipment; Part 2-1: Synchronous Digital Hierarchy (SDH) and
Plesiochronous Digital Hierarchy (PDH) physical section layer
functions
of equipment; Part 3-1: Synchronous Transport Module-N (STM-N)
Regenerator and Multiplex Section Layer Functions
of equipment; Part 4-1: Synchronous Digital Hierarchy (SDH) path
layer functions
[ETSI EN 300 417-7-1] ETSI EN 300 417-7-1 V1.1.1 (2000-10), Transmission and
multiplexing (TM); Generic requirements of transport functionality
of equipment; Part 7-1: Equipment management and auxiliary layer
functions
[ETSI EN 301 164] ETSI EN 301 164 V1.1.1 (1998-08), Transmission and Multiplexing
(TM); Management of Synchronous Digital Hierarchy (SDH)
transmission equipment; Fault management and performance
monitoring; Functional description
[G.703] ITU-T Recommendation G.703 (2001-11), Physical/electrical
characteristics of hierarchical digital interfaces
[G.704] ITU-T Recommendation G.704 (1998-10), Synchronous frame
structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s
hierarchical levels
[G.705] ITU-T Recommendation G.705 (2000-10), Characteristics of
plesiochronous digital hierarchy (PDH) equipment functional blocks

69
References
Reference Description
[G.706] ITU-T Recommendation G.706 (1991-04), Frame alignment and
cyclic redundancy check (CRC) procedures relating to basic frame
structures defined in Recommendation G.704
[G.707/Y.1322] ITU-T Recommendation G.707/Y.1322 (2003-12), Network node
interface for the synchronous digital hierarchy (SDH)
[G.732] ITU-T Recommendation G.732 (1988-11), Characteristics of primary
PCM multiplex equipment operating at 2048 kbit/s
[G.774.01] ITU-T Recommendation G.774.01 (1994-11), Synchronous Digital
Hierarchy (SDH) performance monitoring for the network element
view
[G.775] ITU-T Recommendation G.775 (1998-10), Loss of Signal (LOS),
Alarm Indication Signal (AIS) and Remote Defect Indication (RDI)
defect detection and clearance criteria for PDH signals
[G.781] ITU-T Recommendation G.781 (1999-07), Synchronization layer
functions
[G.783] ITU-T Recommendation G.783 (2004-02), Characteristics of
synchronous digital hierarchy (SDH) equipment functional blocks
[G.803] ITU-T Recommendation G.803 (2000-03), Architecture of transport
networks based on the synchronous digital hierarchy (SDH)
[G.806] ITU-T Recommendation G.806 (2004-02), Characteristics of transport
equipment - Description methodology and generic functionality
[G.812] ITU-T Recommendation G.812 (2004-06), Timing requirements
of slave clocks suitable for use as node clocks in synchronization
networks
[G.813] ITU-T Recommendation G.813 (2003-03), Timing characteristics of
SDH equipment slave clocks (SEC)
[G.823] ITU-T Recommendation G.823 (2000-03), The control of jitter and
wander within digital networks which are based on the 2048 kbit/s
hierarchy
[G.825] ITU-T Recommendation G.825 (2000-03), The control of jitter and
wander within digital networks which are based on the synchronous
digital hierarchy (SDH)
[G.826] ITU-T Recommendation G.826 (2002-12), End-to-end error
performance parameters and objectives for international, constant
bit-rate digital paths and connections
[G.841] ITU-T Recommendation G.841 (1998-10), Types and characteristics
of SDH network protection architectures
[G.957] ITU-T Recommendation G.957 (2006-03), Optical interfaces for
equipments and systems relating to the synchronous digital hierarchy

70

Tellabs 8100 Managed Access System Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Reference Manual

Uploaded by

Copyright:

Available Formats

Tellabs 8100 Managed Access System Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Reference Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tellabs 8100 Managed Access System Tellabs 8184 Access Switch and Tellabs 8188 Access Switch Reference Manual

Uploaded by

Copyright:

Available Formats

What are some of the standards referenced in the document?

What are some of the standards referenced in the document?

What are some of the terms defined in the document?

What are some of the terms defined in the document?

Tellabs ® 8100 Managed Access System

Tellabs ® 8184 Access Switch and Tellabs ® 8188

Docu- Date Description of Changes

© 2008 Tellabs. All rights reserved.

Tellabs ® 8100 Managed Access System 12348_04

Terms and Abbreviations

12348_04 Tellabs ® 8100 Managed Access System

SDH Synchronous Digital Hierarchy

Tellabs ® 8100 Managed Access System 12348_04

About This Manual ............................................................................................................ 7

2 Network Element Overview ........................................................................................ 12

2.1 Introduction ......................................................................................................................................................... 12

3 GMX2 SDH Interface and Cross-Connect Unit ......................................................... 20

3.1 Main Features ...................................................................................................................................................... 20

12348_04 Tellabs ® 8100 Managed Access System

3.3.6 Signal Timing in Receive Direction .................................................................................................... 25

4 SCU-H Control Unit ..................................................................................................... 53

Tellabs ® 8100 Managed Access System 12348_04

About This Manual

12348_04 Tellabs ® 8100 Managed Access System

This is a note symbol. It emphasizes or supplements information in the document.

Please contact us to suggest improvements or to report errors in our documentation:

Tellabs ® 8100 Managed Access System 12348_04

12348_04 Tellabs ® 8100 Managed Access System

• Digital Subscriber Line (DSL) termination from Tellabs 8110 NTUs

Tellabs ® 8100 Managed Access System 12348_04

• STM-N ADM 4/1/0 and DXC 4/1/0 applications

12348_04 Tellabs ® 8100 Managed Access System

2 Network Element Overview

Tellabs ® 8100 Managed Access System 12348_04

2.2.1 Subrack and Equipping

12348_04 Tellabs ® 8100 Managed Access System

The front panel of the FAN2 unit has three LEDs.

LED Name Color Description

Tellabs ® 8100 Managed Access System 12348_04

FAN2 Unit Specifications

2.2.2 Core Units

Power Fuse Units

SCU-H Control Unit

Chapter 4 SCU-H Control Unit provides more details.

GMX2 SDH Interface and Cross-Connect Unit

12348_04 Tellabs ® 8100 Managed Access System

2.2.3 Interface Units

Unit Name Unit Description

ISD-LT161 Transparent basic rate ISDN U-interface unit

ISD-NT1 Transparent basic rate ISDN U-interface unit

OMH/OMH-A G.704 framed interface unit, 8 interfaces

QMH G.704 framed interface unit, 4 interfaces

1The product has been discontinued.

Tellabs ® 8100 Managed Access System 12348_04

2.3.1 Backplane Cross-Connect Buses

Fig. 5 X-bus Segments in Tellabs 8184 Access Switch

12348_04 Tellabs ® 8100 Managed Access System

Fig. 6 X-bus Segments in Tellabs 8188 Access Switch

2.3.3 Network Management Communication