Professional Documents
Culture Documents
DXC FM
DXC FM
DXC-8R, DXC-10A,
DXC-30, DXC-30E
with DCL.3 Common Logic
If, during the warranty period, any component part of the equipment becomes defective by reason of
material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect, RAD shall have
the option to choose the appropriate corrective action: a) supply a replacement part, or b) request
return of equipment to its plant for repair, or c) perform necessary repair at the equipment's location.
In the event that RAD requests the return of equipment, each party shall pay one-way shipping costs.
RAD shall be released from all obligations under its warranty in the event that the equipment has been
subjected to misuse, neglect, accident or improper installation, or if repairs or modifications were
made by persons other than RAD's own authorized service personnel, unless such repairs by others
were made with the written consent of RAD.
The above warranty is in lieu of all other warranties, expressed or implied. There are no warranties
which extend beyond the face hereof, including, but not limited to, warranties of merchantability and
fitness for a particular purpose, and in no event shall RAD be liable for consequential damages.
RAD shall not be liable to any person for any special or indirect damages, including, but not limited to,
lost profits from any cause whatsoever arising from or in any way connected with the manufacture,
sale, handling, repair, maintenance or use of the DXC, and in no event shall RAD's liability exceed the
purchase price of the DXC.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes relating
to DXC and for ensuring that replacements and other adjustments required in connection with the said
warranties are satisfactory.
Software components in the DXC are provided "as is" and without warranty of any kind. RAD disclaims
all warranties including the implied warranties of merchantability and fitness for a particular purpose.
RAD shall not be liable for any loss of use, interruption of business or indirect, special, incidental or
consequential damages of any kind. In spite of the above RAD shall do its best to provide error-free
software products and shall offer free Software updates during the warranty period under this
Agreement.
RAD's cumulative liability to you or any other party for any loss or damages resulting from any claims,
demands, or actions arising out of or relating to this Agreement and the DXC shall not exceed the sum
paid to RAD for the purchase of the DXC. In no event shall RAD be liable for any indirect, incidental,
consequential, special, or exemplary damages or lost profits, even if RAD has been advised of the
possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of Israel.
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates
potential safety hazards regarding product operation or maintenance to
operator or service personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while
the product is energized or connected to outdoor telecommunication lines.
Protective earth: the marked lug or terminal should be connected to the building
protective earth bus.
Some products may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may be also attached.
Warning Please observe the following precautions:
• Before turning on the equipment, make sure that the fiber optic cable is
intact and is connected to the transmitter.
• Do not attempt to adjust the laser drive current.
• Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
• The use of optical devices with the equipment will increase eye hazard.
• Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
Always observe standard safety precautions during installation, operation and maintenance of this
product. Only qualified and authorized service personnel should carry out adjustment, maintenance or
repairs to this product. No installation, adjustment, maintenance or repairs should be performed by
either the operator or the user.
Handling Energized Products
General Safety Practices
Do not touch or tamper with the power supply when the power cord is connected. Line voltages may
be present inside certain products even when the power switch (if installed) is in the OFF position or a
fuse is blown. For DC-powered products, although the voltages levels are usually not hazardous,
energy hazards may still exist.
Before working on equipment connected to power lines or telecommunication lines, remove jewelry
or any other metallic object that may come into contact with energized parts.
Unless otherwise specified, all products are intended to be grounded during normal use. Grounding is
provided by connecting the mains plug to a wall socket with a protective earth terminal. If an earth lug
is provided on the product, it should be connected to the protective earth at all times, by a wire with a
diameter of 18 AWG or wider. Rack-mounted equipment should be mounted only in earthed racks
and cabinets.
Always make the ground connection first and disconnect it last. Do not connect telecommunication
cables to ungrounded equipment. Make sure that all other cables are disconnected before
disconnecting the ground.
Connection of AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power to
the product is 16A. The circuit breaker in the building installation should have high breaking capacity
and must operate at short-circuit current exceeding 35A.
Always connect the power cord first to the equipment and then to the wall socket. If a power switch is
provided in the equipment, set it to the OFF position. If the power cord cannot be readily
disconnected in case of emergency, make sure that a readily accessible circuit breaker or emergency
switch is installed in the building installation.
Connection of DC Mains
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference to the
ground. Any single pole can be externally grounded.
Due to the high current capability of DC mains systems, care should be taken when connecting the DC
supply to avoid short-circuits and fire hazards.
DC units should be installed in a restricted access area, i.e. an area where access is authorized only to
qualified service and maintenance personnel.
Make sure that the DC supply is electrically isolated from any AC source and that the installation
complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power to
the product is 16A. The circuit breaker in the building installation should have high breaking capacity
and must operate at short-circuit current exceeding 35A.
Before connecting the DC supply wires, ensure that power is removed form the DC circuit. Locate the
circuit breaker of the panel board that services the equipment and switch it to the OFF position. When
connecting the DC supply wires, first connect the ground wire to the corresponding terminal, then the
positive pole and last the negative pole. Switch the circuit breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated in
the building installation.
Connection of Data and Telecommunications Cables
Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port differs from
the standard one, a notice will be given in the manual.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance of a
qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables. Do
not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both ends. The
earthing and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk, there are
restrictions on the diameter of wires in the telecom cables, between the equipment and the mating
connectors.
Caution To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cords.
Attention Pour réduire les risques s’incendie, utiliser seulement des conducteurs de
télécommunications 26 AWG ou de section supérieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In such
cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
To comply with electromagnetic compatibility requirements, a ferrite core (such as FAIR-RITE catalog
number 0443164151 or equivalent) should be installed on any unshielded data cable connected to an
RJ-45 connector. This limits the electromagnetic energy emitted from the unshielded cables.
Note: Two cables from the same module can be run through a single ferrite core.
Declaration of Conformity
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC and the Low
Voltage Directive 73/23/EEC. The product was tested in a typical configuration.
Haim Karshen
VP Quality
European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521Ottobrunn-Riemerling, Germany
Declaration of Conformity
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC, the Low
Voltage Directive 73/23/EEC and the R&TTE Directive 99/5/EC. The product was tested in a typical
configuration.
Haim Karshen
VP Quality
European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521Ottobrunn-Riemerling, Germany
Declaration of Conformity
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC and the Low
Voltage Directive 73/23/EEC. The product was tested in a typical configuration.
Haim Karshen
VP Quality
European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521Ottobrunn-Riemerling, Germany
Declaration of Conformity
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC and the Low
Voltage Directive 73/23/EEC. The product was tested in a typical configuration.
Haim Karshen
VP Quality
European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521Ottobrunn-Riemerling, Germany
Preface
Foreword
This manual describes the technical characteristics, applications, installation and operation of
the DXC family of Multiservice Access Nodes, which includes the DXC-30, DXC-30E,
DXC-10A, and DXC-8R.
This release of the manual covers the characteristics of equipment equipped with Common
Logic Module, DCL.3, running software version 9.0 and higher.
1. In this manual, the generic term DXC is used when the information is applicable to all of
Notes the equipment versions. The complete equipment designation is used when the
information is applicable only to specific equipment versions.
2. The DE1B, DT1B, DE3, DT3 and DFSTM-1 I/O modules are available with either copper or
fiber optic interfaces. In this manual, the generic terms DE1B, DT1B, DE3, DT3, DFSTM-1
are used when the information is applicable to both copper and fiber optic module interface
versions. We will distinguish between the copper interface or fiber optic interface when the
information is applicable only to a specific version.
3. The following conventions are used:
• The transmit direction is the outgoing direction of each port.
• The receive direction is the incoming direction.
Manual Organization
This manual is organized as follows:
Chapter 1. Introduction
presents the main features and describes the various equipment versions, and lists the
technical characteristics of the DXC systems.
Chapter 2. System Application Considerations
describes typical applications of the DXC family and presents system application guidelines.
Chapter 3. Functional Description
presents a functional description of the DXC equipment.
Chapter 4. Installation and Operation
provides detailed installation and operation instructions for DXC systems.
Chapter 5. Management Using Terminals and Telnet
provides general instructions for managing DXC systems by means of terminals and Telnet
hosts.
Chapter 6. Configuring the DXC
provides typical configuration procedures for DXC systems.
Chapter 7. Tests and Diagnostics
describes the diagnostic and performance monitoring functions supported by DXC systems.
Appendix A. Connector Wiring
provides connection data for the basic modules used in the DXC system.
Appendix B. Error & Alarm Messages
explains the alarm and configuration error messages generated by DXC systems.
Appendix C. SNMP Management
describes the SNMP and IP environments, and provides background information regarding
the handling of management traffic.
Appendix D. Installing New Software Releases
provides instructions for the installation of new software releases.
Appendix E. Operating Environment
describes the DXC operating environment.
Appendix F. DXC Supervision Language
provides a command reference and detailed instructions for using the DXC supervision
language.
Appendix G. Downloading of Configuration Files
provides instructions for uploading and downloading the DXC configuration files.
Appendix H. Current Versions of DXC Modules
lists the power consumption values and the current software and hardware versions for
different I/O modules.
Conventions
Related Documentation
In addition to this manual, separate Installation and Operation Manuals are available for each
of the DXC I/O modules.
Each module Installation and Operation Manual presents the technical characteristics,
applications and specific configuration information for the corresponding module.
Quick Start Guide
If you are familiar with the DXC system, use this guide to prepare it for operation.
1. Preliminary Preparations
Perform the following actions in the order given below.
1. Disconnect the DXC from all the cables.
2. Remove the DCL.3 modules, set the sections PASSWRD and DP-SP (sections 2
and 7, respectively) of the internal switch S1 to ON, and then reinstall the
modules.
3. Connect the DXC to power, turn it on, and wait at least two minutes.
4. Connect the communication port of a PC running a terminal emulation
program to the CONTROL connector of the DCL.3 module (use a straight
cable). Configure the PC for eight data bits, no parity, and one stop bit. You
can use 1200, 2400, 4800, 9600, 19200, 38400, or 57600 bps.
5. Press the <Enter> key several times in sequence: you should see the DXC
prompt: DXC8R>, DXC10A, >DXC30>, or DXC-30E>.
If you see PASSWORD>, type RAD and then press <Enter> to obtain the
prompt.
Cont.
List of Figures
1-1. Typical DXC System Application – PDH Network Access........................................................ 1-4
1-2. SDH Network Access Application........................................................................................... 1-5
1-3. Typical E3 or T3 Point-to-Point Link ....................................................................................... 1-5
1-4. DXC Enclosures, General View ............................................................................................... 1-6
1-5. DXC-30 Enclosure, General View ........................................................................................... 1-8
1-6. Fan Tray, General View ......................................................................................................... 1-9
1-7. DXC-30E Enclosure, General View ....................................................................................... 1-10
1-8. DXC-10A Enclosure, General View....................................................................................... 1-11
1-9. DXC-8R Enclosure, General View ......................................................................................... 1-12
List of Tables
1-1. DXC Versions ......................................................................................................................... 1-7
1-2. E3 and T3 Ports, Fiber-Optic Interface Characteristics........................................................... 1-19
1-3. Optical STM-1 Port, Fiber-Optic Interface Characteristics ..................................................... 1-22
1-4. Typical Ranges over 24 AWG and 26 AWG Lines................................................................ 1-25
3-1. Classification of I/O Modules with Respect to Timeslot Allocation (Capturing) Mechanism ...... 3-7
3-2. DXC Response to E1 and T1 Link Alarm Conditions ............................................................. 3-26
3-3. Fault Weights for Redundancy Flipping – Internal and External E1 and T1 Ports.................... 3-39
3-4. Fault Weights for Redundancy Flipping – E3 and T3 Ports .................................................... 3-39
3-5. Control Lines in CONTROL Connector................................................................................. 3-43
3-6. Control Lines in MNG Connector ......................................................................................... 3-44
3-7. Handling of Management Access Conflicts........................................................................... 3-47
1.1 Overview
DXC equipment is built to meet the stringent reliability and safety requirements of
telecom operators, and some versions have already been qualified to NEBS
Level 3.
Main System Features
The DXC units are modular systems that can be equipped with various types of
modules, to provide the required services and interfaces for various types of
equipment.
The various chassis versions offered in the DXC family meet a wide range of system
requirements, including redundancy for enhanced system availability and support
for high-density applications, yet maintain the same common set of advanced
features.
Overview 1-1
Chapter 1 Introduction DXC-8R/10A/30/30E Installation and Operation Manual
1-2 Overview
DXC-8R/10A/30/30E Installation and Operation Manual Chapter 1 Introduction
operating in E1, E3 or STM-1 systems. The DIM modules also support fractional E3
(n×1.920 Mbps) and fractional T3 (n×1.472 Mbps) service, where n is up to 8.
The DIM modules are available with a wide range of user data port interfaces:
• Synchronous data ports with V.35, RS-530, X.21, or HSSI interfaces.
• Ethernet 10/100BaseT interface.
• E1 interface, for transmission of an E1 signal over T1 facilities.
1.2 Applications
This section provides basic applications, which illustrate the wide range of services
available when using DXC systems.
For additional descriptions of DXC applications and detailed system application
considerations, refer to Chapter 2.
Applications 1-3
Chapter 1 Introduction DXC-8R/10A/30/30E Installation and Operation Manual
.. ISDN “U”
. Interfaces
PBX
Fractional T1
T1/Fractional T1
n×64kbps
n×56kbps
FCD-T1 Router
ASMi-31 DTE
or
Voice Switch ASM-31
2-wire Line 128k
E1/T1 (Max 5.5 Km)
PDH (NT)
Network E3 or T3 4x"S" Interface (BRI)
(Copper or
Fiber) DXC E1/Fractional E1
(Copper, Fiber)
n×64kbps
FCD-E1A Router
T1/E1 Data
(Copper, Fiber) Voice
ISDN
Data Switch LAN
Frame Relay
Megaplex-2100
PBX
Fractional E1
HDSL 2W/4W
n×64kbps
HCD-E1 Router
1-4 Applications
DXC-8R/10A/30/30E Installation and Operation Manual Chapter 1 Introduction
n×64kbps
FCD-E1I Router
PBX
Fractional T1
T1/Fractional T1
n×64kbps
n×56kbps
FCD-T1 Router
DXC-10A
ADM ... HSSI
ADM
T1/E1 Data
(Copper, Fiber) Voice
ISDN
LAN
Frame Relay
PDH MEGAPLEX-2100
Network LAN
10/100BaseT
Ethernet
Data
HDSL
n×64kbps
HCD-E1 Router
DXC DXC
E3 or T3 (Copper or Fiber)
Versions
The DXC family includes four versions, designated DXC-8R, DXC-10A, DXC-30,
and DXC-30E. All the DXC versions use modular 19" chassis. Each chassis provides
various physical slots in which modules can be installed by the user to obtain the
desired configuration. Figure 1-4 shows a general view of the DXC-8R, DXC-10A,
DXC-30, and DXC-30E enclosures.
DXC-10A
DXC-30
DXC-8R
DXC-30E
The DCL.3 module can be ordered with two serial management ports, or with
one serial port and one 10/100BaseT Ethernet port.
• Power supply subsystem, can include one or two power supply modules
(except for the DXC-10A, which has only one module). The use of two
modules is an option that enhances system availability: when two power
supply modules are installed, they share the load current, and in case one of
them fails the other takes over the full load without disrupting the normal
operation.
Table 1-1 lists the main characteristics of the various DXC versions.
Table 1-1. DXC Versions
Number of Slots
Designation Description
PS DCL.3 I/O
DXC-8R 1U-high chassis for rack 2 2 4
installation (AC internal or DC)
DXC-10A 1U-high chassis for desktop and 1 1 5
rack installation (AC or DC, both
internal)
DXC-30 3U-high chassis for desktop and 2 2 15
rack installation (AC or DC)
DXC-30E 6U-high chassis for desktop and 2 2 15
rack installation (AC or DC)
DXC-30 Enclosure
Enclosure Description
The DXC-30 system is installed in a 3U, 19" enclosure that contains the control
subsystem, the system power supplies, and has slots for the installation of up to 15
I/O modules.
Each I/O module occupies one slot, except for the DHL modules, which occupy
two slots. All the modules are inserted from the rear. The cable connections are
also made at the rear. Figure 1-5 shows a general view of the DXC-30 enclosure.
The DXC-30 enclosure can accept the following system modules:
• One or two common logic modules, type DCL.3. The main functions of the
DCL.3 module are control of cross-connect operations, timeslot routing,
system management, and interfacing with the supervision terminal or with
network management systems. DXC-30 requires only one DCL.3 module,
however by installing an additional DCL.3 module, redundancy becomes
available for this critical subsystem.
15 I/O
Modules
Common Logic
Modules
Power Supply
Subsystem
Cooling Considerations
DXC-30 does not include internal cooling fans, and does not require the supply of
cooling air by an external fan tray when sufficient space is left above and below
the unit in accordance with the guidelines given in Section 4.2. However, when a
DFSTM-1, D8SL or certain types of DIM modules are installed in the chassis, it is
necessary to supply forced cooling. RAD offers a suitable fan tray, which has a
height of 1U and in intended for installation just under the DXC-30 chassis, or any
other rack-mounted equipment that requires forced air cooling.
The fan tray is available in two versions: AC-powered and DC-powered.
Figure 1-6 shows a general view of a typical fan tray (the figure shows the
DC-powered version). The tray includes 7 fans, where each fan is controlled by an
internal control circuit. When all the fans operate normally, they rotate at less than
their maximum allowed speed. In case one of the fans fails, the rotating speed of
the operational fans is increased to maintain the rated air supply.
DXC-30E Enclosure
The DXC-30E system is installed in a 6U, 19" enclosure that contains the control
subsystem, the system power supplies, and has slots for the installation of up to
15 I/O modules.
• Each I/O module occupies one slot. All the modules are inserted from the rear.
The cable connections are also made at the rear. Figure 1-7 shows a general
view of the DXC-30E enclosure.
The DXC-30E system supports module types which functionally are similar to those
available for the DXC-30 system, except for two differences:
• Modules intended for use in DXC-30E systems are 6U high
• The D16U module is supported only by DXC-30E.
The DXC-30E is cooled by free air convection. However, when a DFSTM-1, D8SL
or certain types of DIM modules are installed in the chassis, it is necessary to install
a fan tray under the DXC-30E chassis, as explained above in the Cooling
Requirements section for the DXC-30.
15 I/O
Modules
Common Logic
Modules
Power Supply
Subsystem
DXC-10A Enclosure
The DXC-10A system is installed in a 1U, 19" enclosure. The DXC-10A system uses
3U-high modules. All the I/O modules are inserted from the rear. The cable
connections are also made at the rear. Figure 1-8 shows a general view of the
DXC-10A enclosure.
DXC-10A contains the following main components:
• Control subsystem: this subsystem includes one DCL.3 module.
• Power supply. The DXC-10A is delivered with one pre-installed power supply
module. In accordance with order, the DXC-10A may be delivered either with
an AC power supply, or with a DC power supply, which operates on -48VDC.
• I/O modules. The DXC-10A enclosure has five I/O module slots, designated
I/O1 through I/O5. These slots can be fitted with DT1B, DT3, DE1B, DE3,
DFSTM-1, DHL/E1, DHL/E1/2W, DIM, DHS, D8HS, D8U, D8SL, D4T1,
D8T1, D4E1, or D8E1 modules.
5 I/O
Modules
Common Logic
Module
DXC-10A includes internal cooling fans. The number of cooling fans in the current
DXC-10A chassis version is larger than in older chassis versions, thereby ensuring a
sufficient flow of cooling air even when the chassis includes a DFSTM-1 or D8SL
module.
If you intend to install a DFSTM-1 or D8SL module in the DXC-10A chassis, make
sure the front panel of your DXC-10A looks as in Figure 1-8. If not, check that you
have the appropriate chassis version: if you are not sure, contact RAD Technical
Support Department for help.
DXC-8R Enclosure
The DXC-8R system is installed in a 1U, 19" enclosure. The DXC-8R system uses
3U-high modules. All the I/O and DCL.3 modules are inserted from the rear. The
cable connections are also made at the rear. Figure 1-9 shows a general view of
the DXC-8R enclosure.
Note DXC-8R is also available in a version without front panel. If you need information on
this DXC-8R version, contact RAD Technical Support Department.
4 I/O
Modules
Common Logic
Modules
DC PS Modules
(For DC-Powered
Version Only)
DXC-8R includes internal cooling fans. The number of cooling fans in the current
DXC-8R chassis version is larger than in older chassis versions, thereby ensuring a
sufficient flow of cooling air even when the chassis includes a DFSTM-1 or D8SL
module.
If you intend to install a DFSTM-1 or D8SL module in the DXC-8R chassis, check
its front panel. If the front panel is not similar to that shown in Figure 1-9, contact
RAD Technical Support Department for help.
I/O Modules
The following types of I/O modules are currently available:
• Network interface modules with electrical interfaces:
T1 line interface modules, DT1B, which comprise two T1 ports with
electrical interfaces. Each port can be ordered with a built-in CSU.
E1 line interface modules, DE1B, which comprise two E1 ports with
electrical interfaces. Each port can be ordered with a built-in LTU. Two
versions of this module are available: a standard version with balanced and
unbalanced interfaces for each port, and an optional version with balanced
interfaces only.
T3 line interface modules, DT3, which comprise one T3 port with electrical
interface.
E3 line interface modules, DE3, which comprise one E3 port with electrical
interface.
Fractional STM-1 interface modules, DFSTM-1, which comprises one
STM-1 port with electrical intra-office interface (a DFSTM-1 version with a
second, redundant, port is also available).
• Network interface modules with optical interfaces. The optical interfaces
comply with ITU-T Rec. G.921 and G.956, for direct connection to fiber-optic
network ports. The offered interfaces include LED and laser sources operating
at 850, 1310, and 1550 nm over single-mode and multimode fiber, and
therefore can optimally meet a wide range of system requirements.
(HDSL) ports. Each HDSL port enables the transmission of an E1 data stream,
over unconditioned twisted-pair lines:
Each DHL/E1 port requires two unconditioned twisted-pair lines, and
supports transmission at ranges up to 4.5 km.
Each DHL/E1/2W port requires one unconditioned twisted-pair, and
supports transmission at ranges up to 3 km.
• High-speed data interface modules, DHS and D8HS. The DHS module has
two high-speed synchronous data ports, while D8HS has eight such ports. Each
port can provide RS-530, V.35, V.24, RS-422, or X.21 interface, and can
support user-selectable bit rates of n×56 kbps or n×64 kbps, where n = 1 to
31 (56 to 1736 kbps, or 64 to 1984 kbps, respectively). Additionally, D8HS
supports the 2048 kbps data rate. The interfaces are ordering options with the
DHS module and software-configurable with the D8HS module.
In addition, the DHS module can also be ordered with two Ethernet bridge
(10/100BaseT) or IP router (10BaseT) ports.
• High-speed inverse multiplexer module, DIM. The DIM modules have one
user port, which can be ordered with one of the following options:
V.35, RS-530, X.21 or HSSI port, which operates as a synchronous DCE
interface
10/100BaseT interface with a full-function remote Ethernet bridge
supporting VLANs
10BaseT IP Router interface
E1 interface.
The DIM modules support user-selectable payload data rates of n×1.472 Mbps
for operation on T1 links, and n×1.920 Mbps for operation on E1 links, where
n is 1 through 8 (corresponding to rates of 1.472 to 11.776 Mbps, or 1.92 to
15.360 Mbps, respectively).
The DIM module with E1 interface enables the transmission of one E1 data
stream (2.048 Mbps) over two T1 links (1.544 Mbps), in accordance with
AT&T TR 54019.
• E1 and T1 multiport interface modules, D4E1, D8E1, D4T1, and D8T1.
The D4E1/D8E1 family provides four or eight independent E1 ports that
comply with the requirements of ITU-T Rec. G.703, G.704, G.706 and
G.732. Each port supports up to 31 timeslots, for a maximum payload
capacity of up to 248 timeslots per module.
The D4T1/D8T1 family provides four or eight independent T1 ports that
comply with the requirements of AT&T TR-64111, ANSI T1.403, and ITU-T
Rec. G.703, G.704. Each port supports up to 24 timeslots, for a maximum
payload capacity of up to 192 timeslots per module.
• ISDN “U” interface modules, D8U and D16U, fully interoperable with the
HS-U family of ISDN interface data modules for the Megaplex-2100 Modular
T1/E1 Access Multiplexer Systems. Each of these modules provides
independent ISDN “U” ports, each supporting 2B + D channels, for a total
payload data rate up to 128 kbps per port. Each port enables full-duplex
Levels with CSU 0 dB, -7.5 dB, -15 dB, -22.5 dB, software-selectable
Wavelength Fiber Type Transmitter Typical Receiver Typical Optical Typical Maximum
(nm) (µm) Type Power Coupled Sensitivity Budget Range
into Fiber (dBm) (dBm) (dB) (km / mi)
62.5/125 µm
850 nm LED -18 dBm -28 dBm 10 dB –12 dBm 16 db 2.5 km/1.5 mi
multimode
62.5/125 µm
LED -18 dBm -31 dBm 13 dB –14 dBm 17 db 5.5 km/3.4 mi
multimode
1310 nm
9/125 µm
Laser -12 dBm -31 dBm 19 dB –12 dBm 30 db 38 km/23.6 mi
single-mode
9/125 µm
1550 nm Laser -12 dBm -31 dBm 19 dB –12 dBm 30 db 68 km/42 mi
single-mode
Internal E1 Applicable Standards ITU-T Rec. G.732, G.823 and ITU-T Rec. G.704
Ports Framing Options • Timeslot 0 multiframe for CRC-4 protection, and
16-frame multiframe managed by means of
timeslot 16 (G.732S) for use of CAS
• 16-frame multiframe managed by means of
timeslot 16 (G.732S) for use of CAS
• Timeslot 0 multiframe for CRC-4 protection, and no
multiframe (G.732N), intended for use with CCS
• No multiframe (G.732N), intended for use with CCS
• Unframed
Nominal Data Rate 2.048 Mbps
Module STM-1 Port Timing • System timing (transmit timing locked to DXC
Timing nodal clock)
• Loopback timing (transmit timing locked to clock
recovered from received STM-1 signal)
• DXC system clock can be locked to one of the
recovered STM-1 port signals
Internal Ports Timing • Locked to the DXC master clock
• DXC master clock can be locked to one of the
recovered internal E1 port clock signals
Indicators L LOS (red) Local loss of STM-1 signal
R LOS (red) Remote loss of STM-1 signal
Note Typical ranges are based on the error-free real-line laboratory tests without noise.
System Characteristics
Timeslot Routing Capabilities • Any timeslot to any timeslot
Mapping • With/without A-law/µ-law and signaling conversion,
selectable per timeslot
Routing Modes • Bi-directional (normal) mode
• Unidirectional mode
System Clock Main Source • Internal oscillator (accuracy: ±32 ppm)
Sources (software-selectable) • Locked to the receive clock of any port
• Locked to an external (station) clock source
(2.048 MHz or 1.544 MHz, user-selectable)
2.1 Introduction
This Chapter presents typical DXC applications and explains special application
considerations.
The Chapter covers the services provided by DXC systems, and explains in detail
capabilities, limitations, and specific considerations for the following main
applications:
• T1/E1 conversion applications
• Media conversion applications
• Transport of T1 frames over E1 and E3 transmission facilities
• Channel relocation and digital cross-connect applications
• Fractional T1 and E1 access point applications
• T1/E1 drop-&-insert applications
• Multidrop (broadcast) applications
• HDSL transport module applications
• High-density module applications
• Signaling monitoring applications
• ISDN “U” interface applications
• IDSL applications supporting 64 kbps/128 kbps services
• SHDSL applications
• Inverse multiplexing applications (LAN over WAN)
• Connection of DXC systems through E3 or T3 links (direct grooming from
nx56/nx64 kbps ports)
• M13/T3/E3 multiplexing applications
• Transport of E1 frames over T1 and T3 transmission facilities
• Fractional STM-1 applications.
Introduction 2-1
Chapter 2 System Application Considerations DXC-8R/10A/30/30E Installation and Operation Manual
The wide range of services supported by each DXC unit, together with the large
number of ports supported by the various modules available for DXC systems
enable efficient and flexible utilization in high-density applications.
Note that for DT1B modules, the DXC system does not allow selection of
different framing modes on ports located on the same module: ports using
different framing modes must be located on different modules.
• Connection between a high-speed data port and an E1 or T1 port
(including an internal port of an E3, T3 or fractional STM-1 module): the
DXC system operates primarily as a fractional E1, respectively T1, access point.
• Multidrop (or broadcast) connection: when the unidirectional timeslot
routing mode is used, the DXC system enables multiple ports to receive the
data stream transmitted by a selected E1 or T1 (source) port. The user can
define the timeslots that will be broadcast, and the destination ports. In
addition, the same data stream can be routed bidirectionally between the
source port, and another user-selected destination port.
• ISDN “U” interface applications: in the /I mode, the D8U/D16U ports of the
DXC enable the extension of ISDN lines over non-ISDN facilities; in the /1
mode, the module ports can serve as dedicated line termination units for RAD’s
ASMi-31 and ASM-31 short-range modems, supporting 64 kbps/128 kbps
services for IDSL applications.
• HDSL interface applications: the HDSL ports of the DXC can serve as
dedicated line termination units for RAD’s HTU and HCD family devices
supporting n x 64 kbps services.
• SHDSL interface applications: the SHDSL ports of the DXC can serve as
dedicated line termination units for RAD’s ASMi-52 or FCD-IP devices,
supporting n x 64 kbps services.
• High-density applications: the DXC multi-port modules enable larger number
of links to be serviced by a single DXC chassis.
• Signaling monitoring: probing and transferring of SS7 (or other) signaling to
an analyzer or other application servers.
• Inverse multiplexing: some of the DXC E1 or T1 ports (including internal E1
or T1 ports) can be used in conjunction with the DIM module to provide
inverse multiplexing services.
The user can select the type of links (E1 or T1), the number of links
(determines the data rate, up to 8), and the individual ports to be used.
• Connection through E3 or T3 links: enables the connection of DXC systems
through an E3 or T3 link to the network or to another DXC system, and
provides extensive grooming capabilities.
• Connection through SDH networks: enables the connection of DXC systems
to the SDH transmission cores, as well as efficient distribution of multiple E1
streams to different locations.
TE ST O N LI NE O N LI NE
B A B A
MAJO R A LA RM
C OMMO N LO G IC PO WE R SU PP LY
MIN O R ALA RM
E1
SY STE M
Network
DXC Unit
TE ST O N LI NE O N LI NE
B A B A
MAJO R A LA RM C OMMO N LO G IC PO WE R SU PP LY
T1
MIN O R ALA RM
SY STE M
Network
DXC Unit
To perform the required conversion, the DXC system must include both T1 and E1
line interface modules, and the timeslots must be routed as required between a T1
port and an E1 port.
Note With respect to the routing of timeslots, DHL/E1 and DHL/E1/2W ports are handled in
the same way as E1 ports.
The conversion services can be selected by the user, in accordance with the
specific requirements of each system:
• Transparent full-duplex transfer of data from all the T1 timeslots to the
corresponding E1 timeslots, and vice versa, and the addition of the appropriate
frame synchronization and housekeeping signals, as specified by the applicable
standards.
The user can define the channels (timeslots) to be transferred from trunk to
trunk: to instruct the DXC system to transfer transparently the information
carried in these timeslots, they are defined as data timeslots. The DXC system
inserts a user-selectable idle code in empty timeslots.
This service is sufficient for applications in which the equipment that forms the
T1 or E1 line signal is a data multiplexer. The service also supports fractional
T1 service or channelized E1 data (n×56 kbps or n×64 kbps) received in T1,
respectively E1, formats.
• When the equipment that generates the T1 or E1 line signal is a voice
multiplexer, the DXC system can perform A-law/µ-law conversion in
accordance with ITU-T Rec. G.711. The conversion can be performed on all
the channels, or on channels individually selected by the user: for this
purpose, the user defines the timeslots for which A-law/µ-law conversion is
desired, as voice timeslots.
DXC Unit
T1 and E1 on T1 and E1 on
Copper Media Fiber-Optic
Media
TE ST O N LI NE O N LI NE
T1
B A B A
MAJO R A LA RM
E1 or E3
C OMMO N LO G IC PO WE R SU PP LY
MIN O R ALA RM
SY STE M
MUX
DXC Unit
E1 or E3
Transmission
Network
TE ST O N LI NE O N LI NE
B A B A
MAJO R A LA RM C OMMO N LO G IC
E1 or E3
PO WE R SU PP LY
T1
MIN O R ALA RM
SY STE M
MUX
DXC Unit
Note The fractional STM-1 modules do not support grooming of E3 and T3 data streams.
TE ST O N LI NE O N LI NE
B A B A
MAJO R A LA RM C OMMO N LO G IC PO WE R SU PP LY
E1/T1
MIN O R ALA RM
SY STE M
Network
DXC Unit
By installing an equal number of DHS and DE1B and DT1B modules, it is possible
to provide, simultaneously, fractional access to several users: for example, a fully
equipped DXC containing seven DHS modules and seven DE1B and/or DT1B
modules can replace 14 E1 or fractional E1 (respectively T1) CSU/DSU units.
In addition, DHS module ports can also be connected to the internal E1 and T1
ports of E3, T3 and fractional STM-1 modules.
DXC Unit
LOCATION A LOCATION C
Users Users
Connected to Connected to
Location B Location B
Users Users
Connected to Connected to
Location C Location A
LOCATION B
DXC Unit
LOCATION A LOCATION B
Receives
Receives
Location A
Location A
LOCATION C LOCATION D
Rate Digital Subscriber Line (HDSL) ports. Each HDSL port enables the
transmission of an E1 or T1 data stream over one or two unconditioned
twisted-pair lines (depending on the HDSL interface type).
Figure 2-7 shows a system configuration which uses HDSL transmission for
short-range applications. In the application shown in Figure 2-7, DHL modules
installed in the DXC system enable using regular pairs to connect equipment
located within a few kilometers of the DXC (e.g., on a university campus or within
a company headquarters).
PABX/PBX
E1
PABX HDSL
4-wire
HCD-E1
n x 64 kbps
Router
E1 HDSL
4-wire E1
HTU-E1 Network
DHL DE1
PABX
E1
E1
Data E3
Voice DXC
ISDN HDSL
LAN 4-wire SDH
Frame Network
Relay
Megaplex -2100
HDSL
4-wire
HTU-2
n x 64 kbps
Router
/I Mode Applications
Figure 2-8 shows a typical application for D8U/D16U ports configured to operate
in the /I mode. The /I mode is intended to enable the connection of ISDN
equipment to an ISDN switch over non-ISDN facilities, as shown in Figure 2-8.
Data
HDSL
n×64kbps
Network
HCD-E1/2W
n×1.920 Mbps Router
or
E3 or T3 n×1.472 Mbps
Data Switch
DXC (n = 1, 2, ..., 8)
Router
E1/Fractional E1
n×64kbps
"U" Interfaces Router
FCD-E1A
(Copper, Fiber)
LAN
PABX
Frame Relay
Megaplex
/1 Mode Applications
In the /1 mode, the D8U/D16U ports can serve as dedicated line termination units
for the ASM-31, ASMi-31 and ASMi-31-2 short-range modems, offered by RAD.
This configuration enables the connection of various types of remotely located
data equipment such as computer terminals, statistical multiplexers, etc., via the
DXC.
Figure 2-9 shows a typical application for the /1 mode.
In the application shown in Figure 2-9, each module port serves as a line
termination unit (LT) for one ASM-31, ASMi-31 or ASMi-31-2 modem. Each unit
operates as a network termination unit (NT).
ASMi-31
or DTE
ASM-31
2-wire Line 64k
(Max 5.5 Km)
(NT)
..
. ASMi-31
Data Switch or DTE
ASM-31
2-wire Line 128k
(Max 5.5 Km)
(NT)
DXC
Transmission E3 or T3
Network
ASMi-31
or DTE
ASM-31
2-wire Line 64k
(Max 5.5 Km)
(NT)
..
. ASMi-31
or DTE
ASM-31
2-wire Line 128k
(Max 5.5 Km)
(NT)
1
2 DXC-30
.
.
. E3
E1 or . ..
Fractional E1 . .. Network
Links .
.
111
112 14 D8E1
DE3
Modules
Module
Figure 2-11 shows another application that illustrates the high density which can
be achieved with D4E1/D8E1 modules: a 1U-high DXC-8R chassis can be used to
provide T1/E1 conversion and cross-connect services for up to 32 links. For
example, the DXC-8R can be equipped with three D8E1 and one D8T1 modules
to provide conversion from up to 24 fractional E1 links into 8 T1 links, for
transmission through a T1 transport network.
1
2 DXC-8R
.. 1 T1
E1 or .. .. ... Transport
Fractional E1 .. T1 Links
PS-B
PS-A
Links 8 Network
23
24
D8E1 D8T1
Modules Module
Figure 2-11. High-Density T1/E1 Conversion and Cross-Connect Application for DXC-8R
Figure 2-12 shows a 1U-high DXC-10A chassis used as an E3 multiplexer: for this
purpose, the DXC-10A chassis is equipped with one DE3 and two D8E1 modules.
The two additional slots of the DXC-10A chassis can then be used to provide other
services.
1
2
.. DXC-10A
E1 or .. E3
Fractional E1 .. .. Network
Links
15
16
D8E1 DE3 E3 Link
Modules Module
The high port density of the D4E1, D8E1, D4T1 and D8T1 modules allows
another important DXC application: signal monitoring. The DXC collects signaling
timeslots from many leased lines and grooms them over a full link to the protocol
analyzer at a central site. The analyzer reads the signals that identify each user,
checks the user profile and activates the appropriate response. The solution is
based on a probe (passive T-sampler or patch panel) that duplicates the traffic on
each voice channel and sends it to the DXC.
Figure 2-13 shows a DXC-8R chassis equipped with the D8E1 module in a
signaling monitoring application, with a patch panel as a probe.
Billing
1
D8E1 ModulesD8T1
E1 Links Security
31
DXC-8R
Fraud Detection
The 8-port D8HS module provides additional applications to the DXC system,
such as the one shown in Figure 2-14.
n x 56/64 kbps
E1/T1
FE1/FT1
DHS
SDH FCD-E1/FCD-T1
D8HS Network
Up to 16 STM-1
D8HS DFSTM-1 PBX
FE1/FT1
n x 56/64 kbps DXC D8E1
D8SL
DXC FCD-IP
SHDSL
ASMi-52
RADview Management
Station
Note Since high-density modules usually require more than two bus links, they have been
designed as modules with dynamic timeslot allocation. When designing a DXC
application with these modules, it is important to understand the Automatic
Timeslot Allocation for various DXC modules described on page 3-5 of this manual
and follow a number of important design and configuration guidelines
recommended by RAD. For design guidelines refer to Design Guidelines for
High-Density Module Applications in Chapter 3. For configuration guidelines, refer
to Determining the Optimal Equipment Configuration in Chapter 6.
Figure 2-16 shows a typical D8SL application that utilizes the large number of links
that are supported by a DXC-10A or DXC-8R unit equipped with D8SL modules.
In this application, a DXC-30 unit located at the central office or network hub
communicates with one or more DXC-10A or DXC-8R units installed at the
points-of-presence (POPs) of an ISP, data carrier or service provider. The
communication link between the CO and the POP can be provided by multiple E1
links supported by D8E1 modules, or by a wideband link supported by DE3 or
fractional STM-1 (DFSTM-1) module.
Customers’ Premises
SHDSL E1
ASMi-52
SHDSL X.21
Central Office POP
ASMi-52
DXC-30 DXC-10A
E1, E3 Backbone E1, E3 SHDSL V35/E1
or Network or
FSTM-1 FSTM-1 ASMi-52
SHDSL
Standard HT
Management
Station LAN
SHDSL
Sub
E1
FCD-IP
PABX
ADM
ADM ADM
SDH Network
ADM ADM
Multiplexers
Multiplexers
Figure 2-17. Fractional SDH Terminal Multiplexer Application for Remote Access Nodes
64 kbps
128 kbps
Router
IDSL ASMi-31
PBX
Fractional T1
T1/Fractional T1
n × 64kbps
n × 56kbps
FCD-T1
Router
Voice Switch
T1/E1 Data
(Copper, Fiber) Voice
ISDN
LAN
Data Switch
Frame Relay
Megaplex-2100
Fractional E1
SHDSL
2W n x 64kbps
FCD-IP Router
In the application shown in Figure 2-18, DXC systems are used in local or remote
distribution (“grooming”) nodes, to provide local loop access solutions over copper
and optical fiber cables. The DXC systems have the flexibility necessary to perform
all the functions needed in this particular application (support for drop & insert,
channel rerouting, processing of voice and data channels, fiber-optic and copper
interfaces, etc.).
Moreover, all these functions can be controlled by remote management stations,
thereby enabling the system operator to fully control DXC functions from its
network management center.
DXC 8 E1 8 E1 DXC
Lines Lines
HSSI HSSI
Up to Up to
Router 15.360 Mbps 15.360 Mbps Router
The DXC inverse multiplexer subsystem is compatible with other E1- and T1-based
inverse multiplexers offered by RAD, provided the maximum number of links
supported by the other inverse multiplexers is not exceeded. For example:
• DIM modules with synchronous data ports can operate in a link with IMX-4E1
or IMX-4T1 inverse multiplexers (in accordance with the link type, E1 or T1,
respectively), using a maximum of four links.
• DIM modules with E1 interface can operate in a link with the IMX-2T1/E1
inverse multiplexer.
Figure 2-20 shows a typical application for a DXC inverse multiplexer subsystem
operated in a link with an IMX-4E1 standalone inverse multiplexer. The
connection between the two systems is made through an E1 network (for
operation over a T1 network, an IMX-4T1 standalone inverse multiplexer can be
used).
Inverse Multiplexer Subsystem
(DIM & 2 DE1B Modules) Fast Ethernet
IMX-4E1
Network V.35
4 E1 Router
DXC 4 E1 or E3 Lines
or STM-1
Fast Ethernet
V.35 or
10/100BaseT
ISDN Switch
Router
The DXC inverse multiplexer subsystem also allows to transport an E1 frame across
T1 transmission facilities. This application is shown in Figure 2-21.
E1
When using T1 links, the data rates supported by the DIM module are
n×1.472 Mbps, when n=1, 2, ... 8 (this corresponds to a maximum data rate of
11.776 Mbps); with E1 links, the data rate is n×1.536 Mbps, corresponding to a
maximum rate of 15.360 Mbps.
3.1 Introduction
This Chapter provides a technical description of the DXC system, and presents
additional information regarding the system characteristics. This Chapter covers the
following issues:
• Functional description of the DXC system
• Main characteristics of the various system interfaces (E1, T1, E3, T3, fractional
STM-1, HDSL, IDSL and synchronous data ports)
• System timing characteristics and requirements
• Routing capabilities, including the generation of inband alarm indications
• Functional description of inverse multiplexing subsystem
• Use of redundancy to increase system availability
• Management system characteristics and capabilities
• Diagnostic and fault management capabilities.
General
Each DXC chassis version has physical slots in which modules are installed by the
user to obtain the desired system configuration. Any DXC configuration includes
the following subsystems:
• Control subsystem, can include one or two DXC common logic (DCL)
modules.
• Power supply subsystem, can include one or two power supply (PS) modules.
• User interfacing subsystem. The number of user interfacing modules that can
be installed in a chassis depends on the chassis version (minimum 4,
maximum 15 – see Section 1.3 for details).
• Chassis. The main function of the chassis is to provide interconnections
between the various modules, and in particular to connect among the user
interfacing (I/O) modules, and the common logic modules.
The common logic and power supply modules are always installed in their
dedicated chassis slots, whereas the user interfacing modules can be installed in
any of the other chassis slots (called I/O slots).
Any DXC system must include at least one common logic module, and one power
supply module. These modules are thus referred to as system modules. User
interfacing modules, called I/O modules, are added to this basic configuration.
Where necessary, additional system modules may also be added, to obtain
configurations with extended capabilities, e.g., redundancy.
Payload Routing
The entire payload within the DXC system flows through the two data buses,
however the routing can be performed by three different functions:
• The main cross-connect matrix located on the DCL.3 module.
• The routing matrix of DIM modules.
• The routing subsystems of E3, T3 and fractional STM-1 multiplexer module.
DXC System
DXC Bus
I/O Module
Data from I/O
Control Bus
Address Bus
Data to I/O
I/O Module
Inverse Multiplexer
Module
E3/T3/Fractional STM-1
Multiplexer Module
Main Cross-Connect
Matrix
Control Logic
DCL.3 Module
Each section is a non-blocking matrix that can map timeslots from the DXC bus
to the timeslots of the internal ports of the module.
An internal port is the port that enables the module to accept one of the data
streams that can be multiplexed in accordance with the applicable standard, as
explained in the corresponding module Installation and Operation Manual:
E3 multiplexer modules have 16 internal E1 ports
T3 multiplexer modules have 28 internal DS1 ports
Fractional STM-1 modules have 30 internal E1 ports.
In addition to payload data, the timeslot routing matrix also enables assigning
one timeslot per external port to inband management traffic.
• Matrix Bypass Switches. These switches enable direct connection of timeslots
from the DXC bus to the internal timeslots of the module. This function is used to
route data from DIM modules to the external port located on the module (E3, T3
or fractional STM-1, in accordance with the module type). Therefore, the input
matrix bypass switch takes data from the Data to I/O bus, and the output matrix
bypass switch applies data on the Data from I/O bus. The resulting direction of
data flow simulates the data flow from regular I/O modules.
The allocation of timeslots to any DXC module is made in accordance with one of
the methods listed above (see allocation details in the following sections).
Therefore, it is possible to classify each DXC module in accordance with these
three types. The three types of modules are identified in Table 3-1.
Note Since the timeslot allocation is automatically performed, the term used for
automatic allocation is timeslot capturing.
Table 3-1. Classification of I/O Modules with Respect to Timeslot Allocation (Capturing) Mechanism
This approach does not prevent the DXC data buses from supporting 15 dual-port
Type 1 modules, which is the maximum number of Type 1 modules that can
installed in any type of DXC chassis, including the DXC-30 and DXC-30E (see the
Functions of Main Cross-Connect Matrix section above).
The DXC Common Logic, starting from version 7.1 and higher, provides two
modes of allocating timeslots to the Type 2 (Dynamic Allocation) modules. These
modes are called dynamic timeslot allocation mode and static timeslot allocation
mode.
The dynamic mode is automatic timeslot allocation mode, which minimizes the
number of bus links needed by the module. This mode, however, may cause
temporary disruption of data traffic, both in related and unrelated ports, when
changing timeslot configuration.
To avoid this inconvenience, you can use the static mode. This mode allows you
to assign a maximum number of timeslots to each port. Starting from DXC version
7.1, the static mode is divided into two submodes: STATIC and STATIC 1:1. In the
STATIC mode, any timeslot added or deleted within this maximum number will
not affect the traffic on unrelated ports. In the STATIC 1:1 mode, any timeslot
added or deleted within this number will not affect traffic on any other system
port, including the related ports. The “static” mode on the “dynamic” module
ports makes the timeslot allocation behavior similar (however, not completely
identical) to that of fixed type modules.
Both timeslot allocation modes for Type 2 modules are explained below.
Note Bus links captured by a Type 1 module will never be allocated to Type 2 modules,
even when the Type 1 module ports are not connected.
Note that bundling is possible only for timeslots routed to ports of a given I/O slot,
but not for ports located on modules installed in other I/O slots.
In other words, a bus link cannot be shared between two or more modules. The
result is that any Type 2 module is always assigned a number of timeslots which is
a multiple of 32 timeslots (that is, a total of n×32 timeslots, where n = 1, 2, etc.). If
the module does not use a total number of timeslots which is a multiple of 32
timeslots (that is, n×32 timeslots, where n = 1, 2, etc.), the last captured bus link
will not be fully utilized. Any unused timeslots in that last bus link cannot be used
by other modules, thus decreasing the total capacity of the matrix accordingly.
This situation is illustrated by the following example.
Two D4E1 modules are installed in slots 1 and 2 of a DXC-30. The DXC data bus
links that will be assigned for the connections described below are as follows:
• For connecting 31 timeslots from port 1:1 to port 1:2: one bus link must
be assigned to each port. Therefore, the two bus links identified as 1:1 and
1:2 are captured for this connection.
• For connecting 3 timeslots from port 1:3 to port 1:4: one more bus link
(the bus identified as 2:1) is captured. Note that only 3 out of the 32
timeslots of that bus link are used.
• For connecting 3 additional timeslots from port 2:1 to port 2:2: these
timeslots cannot be allocated on bus link 2:1 (although there are sufficient
empty timeslots on this bus link, it is already assigned to another I/O slot).
Therefore, it is necessary to capture an additional bus link: in accordance
with the priority rules listed above, the additional bus link is 2:2.
Note that any Type 2 module which has at least one timeslot configured as
connected in the database captures as a minimum one bus link, that is, it captures
a minimum of 32 timeslots.
The dynamic timeslot allocation algorithm described above enables full utilization
of the available DXC data bus capacity. It also has the advantage that the routing of
timeslots to modules with preassigned (fixed) allocation (for example, DE1B,
DT1B, DHS, etc.) can be changed without disrupting the traffic to other modules
with fixed allocation.
However, if Type 2 modules are installed in the chassis, whenever a new module
is installed and assigned timeslots, the list of data bus timeslots that remain free
changes. This may require the common logic subsystem on the DCL module to
change the local routing on the other modules, an event that may result in a short
disruption to the traffic flowing through these modules.
A temporary disruption of traffic flow to Type 2 modules may occur in the following
situations:
1. When a configuration change forces the local routing subsystem of a Type 2
module to rebuild its internal timeslot allocation.
2. When a new Type 1 module is physically inserted in a slot whose bus links are
already captured by a Type 2 module.
3. When a new Type 1 module, not yet inserted in the chassis, is configured in
the database into an I/O slot whose bus links have been captured by a Type 2
module.
4. When a new Type 2 module is configured in the database not in the first slot
marked as RSVD (reserved): see DSP ST SYS command.
When using the static mode (both submodes), the timeslots on each port can be
actually divided into three types:
• Allocated timeslots which currently transfer data
• Allocated timeslots which are not currently transferring data but can potentially
transfer data without errors (reserved for future growth)
• Not allocated timeslots.
When calculating the DXC matrix occupancy, the sum of the first two types should
be taken into consideration. In other words, the reserved timeslots are considered
as occupied.
Note In both static modes, the max number of timeslots that can be allocated in the DXC
system is 900, while in the dynamic mode it is 930.
E1 Port Characteristics
The DXC system supports external E1 ports with electrical and fiber-optic
interfaces, and internal E1 ports of the DE3 module.
The E1 ports on the D4E1 module can be ordered with one of the following line
interfaces:
• 120Ω balanced line interface terminated in a RJ-45 connector
• 75Ω unbalanced interface terminated in two mini-BNC female coaxial
connectors.
The E1 port interfaces on the D8E1 module depend on the ordered module version:
• The E1 ports on the 3U D8E1 modules are terminated in two 25-pin D-type
female connectors. These connectors are used for both module versions (120Ω
balanced or 75Ω unbalanced interfaces).
• The E1 ports on the 6U D8E1 modules can be ordered with one of the
following line interfaces:
120Ω balanced line interface terminated in a RJ-45 connector
75Ω unbalanced interface terminated in two mini-BNC female coaxial
connectors.
Line coding is HDB3. The nominal balanced interface transmit level is ±3V, and
the unbalanced interface transmit level is ±2.37V. Jitter performance complies
with the requirements of ITU-T Rec. G.823. The maximum line attenuation,
without LTU, is up to 10 dB; when ordered with an integral LTU, the maximum
line attenuation is up to 40 dB.
The internal E1 ports support the G.732N and G.732S framing modes, with or
without use of CRC-4 timeslot 0 multiframe, as well as the unframed mode.
You can select the frame synchronization algorithm: standard algorithm in
accordance with ITU-T Rec. G.704, in accordance with AT&T TR-62411, or a
proprietary fast algorithm.
T1 Port Characteristics
The DXC system supports external T1 ports with electrical and fiber-optic
interfaces, and internal ports.
The internal DS1 ports support the SF (D4) and ESF framing modes, as well as
unframed operation in accordance with user’s selection. You can select the frame
synchronization algorithm: standard (in accordance with AT&T TR-62411), or a
proprietary fast algorithm.
E3 Port Characteristics
The DXC system supports external E3 ports with electrical and fiber-optic interfaces.
T3 Port Characteristics
The DXC system supports external T3 ports with electrical and fiber-optic interfaces.
Note DXC equipped with the DFSTM-1 module supports linear ADM topology only. A full
SDH ring is not supported.
All the other tributaries (up to 63) can be bypassed between the two STM-1
interfaces.
The following interface types are available for the external STM-1 ports:
• Electrical interfaces, for intra-office applications which require direct
connection to higher-level SDH multiplexers
• Optical interfaces for short-haul and long-haul applications, complying with
ITU-T Rec. G.957. These interfaces require two fibers per port (a transmit fiber
and a receive fiber). RAD offers a wide range of optical interfaces, which
include LED and laser sources operating at 1310, and 1550 nm over
single-mode fiber, and therefore can optimally meet a wide range of system
requirements. The long-haul optical interface supports a range of up to 50 km
(31 miles), thereby enabling remote access to regional and national SDH
transmission networks.
Using advanced equalization, adaptive filtering, and echo cancellation techniques, the
HDSL subsystem compensates for line impairments, bridged taps, and mixed cables
commonly encountered in the local distribution network. Moreover, due to the high
immunity to background noise, the DHL/E1 and DHL/E1/2W modules enable the
transmission of multiple HDSL signals in the same physical cable without requiring pair
selection.
The DHL/E1 modules can operate on unloaded AWG-22, AWG-24, and AWG-26
twisted-wire pairs, and other similar pairs. Up to two bridged taps, having a length
of up to 500m, are tolerated. The HDSL subsystem meets all the margin
requirements over all the DLL (digital local line) physical model loops according to
ETSI ETR-152.
The transmission of data on each twisted-wire pair (HDSL line) is full duplex; for the
DHL/E1 modules, which use two lines, each HDSL line operates independently,
except for the distribution of payload data bits between the two lines.
The HDSL subsystem operates in a master-slave mode:
• The unit located at the central office side of the link, called line termination
unit (LTU), serves as the master that determines the distribution of payload
data between the HDSL lines. In addition, it controls the system start-up
procedure and provides the timing reference for HDSL line transmission.
• The slave unit, located at the remote end of the link (customer side), is called
the network termination unit (NTU).
The DHL/E1 and DHL/E1/2W modules support both central (LTU) and remote
(NTU) operating modes. The actual operating mode (LTU or NTU) is selected by
internal jumpers.
The DHL/E1 modules can connect to other RAD equipment with four-wire HDSL
interfaces, e.g., HCD-E1, HTU-E1, Megaplex, etc; the DHL/E1/2W module can
connect to the HCD-E1/2W offered by RAD.
• The bridge filters the Ethernet frames received by the local Ethernet interface,
and forwards to the WAN only frames not addressed to local nodes. The
bridge can also block broadcasts and multicasts, and supports VLANs.
• The IP router forwards to the WAN only packets destined to the WAN.
The transmit clock source can also be locked to the receive clock of a
user-selected internal E1 or DS1 port (located on an fractional STM-1, E3 or T3
multiplexer module).
• Transmit clock source locked to the internal crystal oscillator, which has an
accuracy of ±32 ppm.
• Transmit clock source locked to an external (station) clock signal. The nominal
frequency of the external clock source is user-selectable (1.544 MHz or
2.048 MHz).
In addition to the selection of a main transmit clock source, the user can specify a
fallback source. The fallback source is automatically selected when the main
source fails (a failure is declared in case of either a loss of signal on the station
clock, or a red alarm (loss of signal) condition on the HDSL, E1, T1, E3, T3, STM-1
or “U” ISDN port selected as the main source, or when the RTS line of a DHS port
is switched off).
Note When using the external (station) clock as the reference source, the clock signal can
be connected in parallel to both DCL.3 modules. In this case, when one signal is
lost, the other module can still provide a reference signal, without switching to the
fallback source. See also Section 3.7.
The clock signals are exchanged through the control bus, part of the DXC bus.
Routing Modes
To expedite the handling of the E1 and T1 data streams (in particular those
multiplexed via internal ports into fractional STM-1, E3 or T3 data streams), the
user can specify the routing mode of E1 and T1 ports:
• Regular Routing - in this mode, the routing subsystem can independently
route the individual timeslots of the port. This mode supports the timeslot
cross-connect function, and therefore the timeslots of an internal E1 port using
regular routing can also be routed to other types of I/O modules, e.g., T1 or
DHS modules.
This mode enables the transmission of a full E1 data stream from an external or
internal port; it also enables the transmission of a full T1 data stream (including
the F-bit) received from an I/O module with T1 interface through an external
E1 port, in accordance with ITU-T Rec. G.802, as well as through an internal
E1 port of a fractional STM-1 or E3 module.
To increase flexibility, in the regular mode the user can select between two
routing modes:
Bidirectional mode: in this mode, the routing is always symmetrical (the
transmit path of the source timeslot is connected to the receive path of the
destination timeslot, and vice versa).
Unframed mode: enables transparent routing of unstructured E1 or T1
data.
The regular routing mode is suitable for data traffic, for which it is not necessary to
support end-to-end transmission of channel-associated signaling.
In addition, when transmitting inband management traffic through a fractional
STM-1, E3 or T3 link in a dedicated timeslot, the port that carries the management
timeslot must always be configured for regular routing.
The transparent mode enables the transmission of an E1 or T1 data stream carrying
voice traffic through the fractional STM-1, E3 or T3 link, because it preserves the
original multiframe structure. Note that in this mode, the internal E1 port can only
be routed to another E1 port, and that port must also use the transparent mode;
similarly, an internal T1 port can only be routed to another T1 port using the
transparent mode.
Routing Methods
The routing capabilities depend on the port type:
• For connections between external E1 and/or T1 ports, the user can program
the routing of each individual 64 kbps timeslot to any timeslot of any other E1,
T1 or HDSL port. This capability also applies to routing between external E1,
T1 and/or HDSL ports and internal ports of an fractional STM-1, E3 or T3
module installed in DXC system.
To determine the number of ports that can be supported with the available
number of timeslots, you must also take into consideration the number of timeslots
needed to support the various types of trunks: for example, a full E1 trunk requires
32 timeslots, whereas T1 trunks require only 24 or 25 timeslots. Therefore, 960
timeslots are sufficient to permit the routing of up to 30 fully-utilized E1 ports that
are routed to a high-bandwidth external port, e.g., the STM-1 port of fractional
STM-1 modules. A larger number of E1 ports can be supported when E1 ports are
used for fractional E1 service: in any case, the maximum number of timeslots in
use cannot exceed 960.
The following sections provide several examples intended to help you determine
the maximum number of ports that can be installed in a given DXC system.
Note The following system capacity examples are given for the DXC-30 and DXC-30E
chassis versions. For other chassis versions, it is also necessary to consider the
number of slots available for I/O modules.
The NONE mode is a non-transparent mode, and is often used when the T1 or E1
data stream carries voice channels, e.g., in PABX applications.
TRANS Same as for NONE, except that the signaling bits are not forced to the OOS state.
This mode is suitable for use in voice and DATAPORT applications.
FULL The DXC system does not change the state of the timeslots of the other port, nor the
state of the signaling bits.
This mode is the fully-transparent mode, and is often used when the T1 or E1 data
stream carries channelized or unchannelized data.
When the NONE mode is selected, the DXC system offers four additional
user-selectable options. These options determine the states assumed by the A, B
signaling bits of the corresponding channels during out-of-service periods:
SPACE (SP) The A and B signaling bits are forced to the state that corresponds
to on-hook (idle) during out-of-service periods.
MARK (MK) The A and B signaling bits are forced to the state that corresponds
to off-hook (busy) during out-of-service periods.
SP_MK The A and B signaling bits are forced to on-hook state for 2.5
seconds, and then are switched to the off-hook state until the
out-of-service condition disappears.
MK_SP The A and B signaling bits are forced to the off-hook state for 2.5
seconds, and then are switched to the on-hook state until the
out-of-service condition disappears.
Note The C and D signaling bits are fixed at C=0, D=1, in accordance with ITU-T
Rec. G.704, Table 9.
Note The DXC system uses elastic buffers having a length of exactly ±1 frame. Therefore,
in case of buffer underflow one frame is repeated without loss of frame alignment,
and in case of buffer overflow one frame is skipped, also without loss of frame
alignment.
• Local reception of AIS signal (AIS red alarm condition).
• Indication of remote loss of synchronization (yellow alarm condition).
Note For convenience, the terms used in this section to identify the various alarm
conditions are the terms used for T1 ports. The equivalence of the terms is
explained in the E1 Alarm Conditions and T1 Alarm Conditions sections in
Appendix E.
Table 3-2 lists the response of the DXC system to link alarm conditions.
Legend: MF – multiframe
that the internal link is out-of-service. This indication, called carrier group
alarm (CGA), is provided in each timeslot. All the internal ports of module use
the same OOS code. The code inserted in individual timeslots is
user-selectable.
• External Link Alarms. When the external port of the module is in the OOS
state, it transmits the OOS code toward the DXC bus through all its internal
ports. As a result, all the E1, T1, DHL, DHS and D8U/D16U modules
connected to the fractional STM-1, E3 or T3 module receive the OOS code.
Note AIS is sent downstream (toward the internal E1 port connected to the VC port), whereas
the RDI is sent upstream (toward the equipment at the far end of the VC path).
The gap duration is always an integer multiple of the bit interval at the
2.048 MHz clock burst rate, however the actual duration depends on the
number of active links, n, and the link type:
For E1 links, the gap duration is n×16 bits, followed by a clock burst of
n×240 bits (without TS0, TS16).
For example, at a user's data rate of 7.680 Mbps (four active links), the gap
has a duration of 64 bit intervals (4×16 bits) and appears after every group
of 960 user's data bits (4×240 bits); for the maximum rate, 15.760 Mbps
(eight active links), the gap has a duration of 128 bit intervals and appears
after every group of 1920 user's data bits.
For T1 links, the gap duration is n ×72 bits, followed by a clock burst of
n×184 bits (without F-bit and TS1).
For example, at a user's data rate of 5.888 Mbps (four active links), the gap
has a duration of 288 bit intervals (4×72 bits) and appears after every group
of 736 user's data bits (4×184 bits); for the maximum rate, 11.776 Mbps
(eight active links), the gap has a duration of 576 bit intervals and appears
after every group of 1472 user's data bits.
The gapped clock mode is suitable for equipment which can tolerate changes
in the instantaneous clock rate (most types of data transmission equipment
can).
• Smooth Clock Characteristics. When the smooth clock mode is selected, the
receive clock supplied to the user's DTE has a constant rate, which is equal to
the average data rate.
The actual clock rate depends on the number of active links, n, and the link
type:
For E1 links, the clock rate is n ×1.920 MHz.
For T1 links, the clock rate is n ×1.472 MHz.
The user's DTE must read the data sent by the DIM module at the rate of the
receive clock signal, and the DIM module samples the transmit data arriving
from the user's DTE in accordance with the transmit clock signal provided to
the user's DTE.
For flexibility, the user can select the polarity of the clock signal relative to data
(normal, i.e., in accordance with the interface standards, or inverted).
• External DCE: this mode is similar to the DCE mode, except that the DIM data
port samples the transmit data arriving from the user's DTE in accordance with
an external transmit clock signal returned by the user's DTE. This clock signal
must be derived from the transmit signal provided by the DIM data port to the
user's DTE.
For flexibility, the user can select the polarity of the clock signal relative to data
(normal, i.e., in accordance with the interface standards, or inverted).
This mode is suitable for tail-end applications.
General
DXC systems are designed for high reliability and high availability. To achieve high
availability, it is necessary to use redundancy. Redundancy is a protective measure
implemented by deliberately introducing additional components (for example,
modules) beyond those necessary to implement the designated function or reach
the desired capacity. These additional components are “redundant” in the sense
that they are not normally used, but are kept in a “standby” state, that is, ready to
take over functions performed by other similar components.
The DXC system is designed to automatically put a redundant module in service in
case the corresponding module fails, thereby ensuring that service can continue in
the event of any single module failure. Redundant modules may be inserted or
removed even while the system operates, without disrupting the traffic or
degrading system performance.
To cover all the system functionality aspects, DXC systems offer three types of
redundancy:
• System-level redundancy
• Line (link) redundancy
• Hardware redundancy.
System-Level Redundancy
System redundancy refers to the features available for protecting the system against
failure in the two subsystems which are critical to its operation: the power supply
subsystem and the common logic subsystem.
A failure in any one of these subsystems could disable the whole system, whereas a
failure in an I/O module affects only a small part of the system, and can be
generally overcome by using alternate routes, putting unused capacity into service,
etc.
Depending on the chassis type selected by the user, some of the system
redundancy features are always available, whereas others are optional and
therefore depend on user’s decisions.
• The DXC-8R chassis has full system redundancy as a built-in feature.
• The DXC-30 and DXC-30E chassis support full system redundancy, but the
user can select whether to implement or not redundancy (that is, can decide
whether to install or not redundant power supply and common logic modules)
• The DXC-10A chassis does not support system redundancy.
PS Subsystem Redundancy
The PS subsystem supplies the operating voltages to the DXC chassis. A single PS
module per chassis is sufficient to supply the full chassis power requirements.
As mentioned above, the DXC-8R chassis includes redundant built-in power
supplies. For critical applications, an additional, redundant power supply module
can be installed in the DXC-30 and DXC-30E chassis.
With a redundant PS module, both PS modules are connected to power and share
the load when the system is operating. If one module fails, the second module
automatically takes up the full load.
The two PS modules installed in a chassis can be of the same type (AC powered or
DC powered), or of different types. This provides the flexibility to match the
implementation of the power distribution at each location: for example, in a site
based on DC power, two DC powered modules should be installed, whereas in a
site using utility (AC) power as the main source and battery backup, one AC
powered and one DC powered module would be installed.
A similar arrangement can be made with respect to the other RS-232 port,
which is available on DCL.3 modules with two RS-232 ports (the dial-out or
network access port, terminated in the NETWORK connector), and with
respect to the external (station) clock ports.
• When using the Ethernet ports of the DCL.3 modules, the control subsystem
uses only the information received through the port of the active module, and
prevents transmission through the Ethernet port of the standby module. In case
of the DCL.3 module flip, the discovery speed of the new online DCL.3
module depends on the ARP table refresh time of the LAN or network
management station router. Two different cables (not a Y-cable) should be
used for connecting the two Ethernet ports to different ports of Ethernet hubs.
I/O Redundancy
The flexible timeslot routing capabilities of the DXC system can be used to offer
redundancy at the I/O module and port level. Redundancy is available for I/O
modules with E1, T1, and HDSL ports, as well as for fractional STM-1, E3 and T3
modules. Redundancy enables the DXC system to continue normal service in case
an external link fails, or a technical failure occurs in an I/O module.
To meet the requirements of various system applications in the most effective way,
the following redundancy modes are offered:
• Line redundancy mode, also called single-slot protection mode. This mode is
supported by the dual-port DFSTM-1, DT1B, DE1B (both fiber optic and
copper interfaces), DHL/E1 and DHL/E1/2W modules, as well as by D4E1,
D8E1, D4T1 and D8T1 modules.
• Hardware redundancy mode, also called Y-cable redundancy mode. This
mode is supported by the DT1B and DE1B modules (copper interface only).
Network
E1 or T1 E1 or T1
Lines Lines
DXC DXC
The line redundancy mode uses software and hardware located on the module
itself to automatically switch the traffic to a backup line. The switching takes place
within 50 msec (this switch-over interval is widely used in many
telecommunication standards to specify the time to wait before switching to an
alternate path in case the current path fails).
To use line redundancy, it is necessary to configure one module port as the main
port and the other as the redundant (standby) port. The main port is then selected
as the default active port.
The approach used to select the active port can be specified by the user:
• Switching in accordance with the local loss of synchronization indication (this
mode is called hardware switching mode). Switching to the alternate port
takes place immediately upon detection of the loss of synchronization
condition.
• Switching in accordance with a set of criteria (flip criteria) evaluated by the
module software (this mode is called software switching mode). The criteria
used in the software mode are described in the Flip Criteria section below.
To reduce the occurrence of switching under marginal conditions, the user can
specify a recovery time after each port switching: during this interval, the
collection of status data is stopped and therefore no switching can take place.
When configuring the timeslot connections, it is necessary to configure only port 1
(the other module port is automatically configured with identical parameters,
including the timeslot routing).
Redundant Pair
(2 DE1B or DT1B Modules)
Y-Cable for
Port 1
Network
Y-Cable for
DXC Port 2
E3 or T3 Modules
Transport
Network
DXC
In this mode, two E3 or T3 modules are installed in the DXC, and their ports are
connected to the remote equipment (another DXC system, or any other
equipment that supports the 1+1 protection feature through different links.
The two modules are configured as a redundant pair, and therefore only one of
them actually carries the traffic. In case of failure (either of the external link or of a
module), the traffic is automatically transferred to the other module, thereby
ensuring that traffic can continue to flow. Since the redundancy is implemented
between two modules, the switch-over can take up to 1 second.
Table 3-3. Fault Weights for Redundancy Flipping – Internal and External E1 and T1 Ports
Weight Events/Alarm
255 I/O module removed
10 I/O module hardware failure
5 Local sync loss
Remote sync loss
AIS
AIS and sync loss
Note For STM-1 ports, the redundancy flipping is controlled by the K1 byte, carried in the
SDH overhead, in accordance with ITU-T Rec. G. 783. The following K1 byte
values are used (listed in decreasing order of priority):
OD Signal fail, high priority. Caused by LOS, LOF, line AIS and clock fail
conditions.
OC Signal fail, low priority. Caused by an EED condition.
OB Signal degrade, high priority. Caused by an SD condition.
Introduction
The DXC supervision and configuration activities can be performed using
supervision terminals, SNMP-based network management stations, and IP hosts
using the Telnet protocol.
The activities that can be performed include:
• DXC system configuration.
• Reading of DXC system status.
• DXC system testing.
• Display of alarm status and history.
• Reading of external alarm conditions and generating control signals by means
of relay contacts.
Database Management
The DXC system is designed for unattended operation. The configuration of the
DXC system, that is, a complete collection of operating parameters, is determined
by databases stored in flash memory on the DCL.3 module (when two DCL.3
modules are installed, both modules store the same databases). A copy of the
currently active database, which determines the actual operating parameters, is
loaded upon power-up and stored in RAM.
To simplify the preparation of databases, and to provide network administrators
with better control over the individual DXC units in their responsibility area, DXC
systems support the uploading and downloading of DXC databases by transferring
configuration files using the TFTP protocol. This enables the network
administrators to distribute verified configuration files to all the managed DXC
units in the network, from a central location.
To further expedite the process, it is also possible to upload the configuration data
stored by a DXC unit to the management station as a standard disk file, and then
distribute this file to other units which use similar configuration. The uploading and
downloading of configuration files is made online, through any DCL port configured
to carry management traffic, without stopping the operation of the DXC system. Any
PC that supports the TFTP protocol can be used for file transfer.
Management Tools
DXC database management, as well as the other configuration, test, and
monitoring activities (equipment status reading, alarm status and history, activation
of test loops, reading of performance statistics, etc.) can be performed in three
ways:
• Supervision Terminal. A “dumb” ASCII terminal (or a PC running a terminal
emulation program), connected to one of the RS-232 serial ports of the DCL.3
module installed in the DXC, can be used as a supervision terminal. The
connection can be made either directly, or through modem or low-speed data
CONTROL Port
All the DCL.3 module versions have an RS-232 port, designated CONTROL. This
port enables direct connection to terminals, provided its interface is configured as
DCE (the selection is made by software commands). Since terminals usually have
DTE interfaces, in this case the connection to the port is made by means of a
straight-through cable.
The CONTROL port also supports the connection of a remote supervision terminal
through a modem link. For connection to a modem, you need a DCE to DCE cross
cable (also called null modem cable), and the port interface must be set to DTE.
For multidrop operation, each DXC system can be assigned a node address in the
range of 1 through 255. Assigning address 0 to a DXC system means that it will
accept and answer any message: this is not permitted in multidrop operation.
Address 0 is however recommended for use with both point-to-point and dial-up
modes.
MNG Port
The other serial port available on DCL.3 modules with RS-232 interfaces, which is
terminated in the connector designated MNG, generally operates as a DTE
interface and is intended for direct connection to a dial-up modem, for automatic
reporting of alarms. This port does not support the connection of a supervision
terminal.
When the MNG port serves for communication with a network management
station using the SLIP or PPP protocol, its interface must be configured as DCE.
The selection of the interface type (DCE or DTE) is made by means of internal
switches.
To simulate DTE operation, the delay between these events can be set by the user
(by means of the DCD-DELAY parameter).
In addition, the DXC always sets DSR OFF (inactive) for 5 seconds when the EXIT
command is executed, or the disconnect time-out expires.
Note that an addition line, RI, is available in the MNG connector. The RI line is
normally OFF (inactive), and is switched to the ON (active) state when the modem
attached to the MNG connector detects an incoming call.
AUTOBAUD Function
When the AUTOBAUD function is enabled, the DXC can identify the data rate of
the signal received at the CONTROL port by analyzing the timing of three
consecutive Carriage Return + Line Feed characters (generated by pressing three
times the carriage return key). The detected data rate is then used for the current
communication session.
Note The data rate used by the MNG port is always equal to the data rate configured by the
user, and therefore it need not be equal to the data rate used at the CONTROL port.
The automatic baud rate identification procedure is performed (or repeated)
whenever three consecutive carriage returns are received after one of the following
events occurs:
• The DTR line has been switched OFF.
• The EXIT command has been executed.
• The idle disconnect time-out expired because no data has been exchanged
with the supervision terminal.
In case one of these events occurred, the DXC assumes that the current
communication session has been terminated. Therefore, when the password
protection is enabled, the password must be entered again before the supervision
communication with the DXC can be resumed.
The AUTOBAUD function is supported only by the CONTROL port, and must not
be used when SLIP or PPP communication is desired.
Out-of-Band Management
For out-of-band management, the connection is made through one of the DCL.3
ports. For serial ports, the user can select either the SLIP (Serial Link IP) or the PPP
(Point-to-Point) protocol; Ethernet ports support the IP and ARP protocols.
When several DXC units are managed by daisy-chaining the out-of-band
management ports, a RAD proprietary routing protocol is used for management
traffic handling. The user can also enable the transmission of RIP2 routing tables
through each port upwards toward the external network (in the various
configuration commands, these ports are referred to as SLIP AGENT or PPP
AGENT ports), thereby enabling the transfer of the internal network topology to
routers using the RIP2 protocol.
(always DLCI 100). Note that the SNMP agent does not support frame relay
management protocols (ANSI T1.617 Annex D, LMI, etc.).
When using PPP and frame relay protocols, the user can enable the
transmission of RIP2 routing tables (separately through each main link), to
enable the use of standard routers using the RIP2 protocol to reach the
SNMP agent through the assigned main link timeslots.
• When all the link timeslots are assigned to payload traffic, the management
traffic can use the Sa4 national bit (Sa4 to Sa8 bits in the D8E1 module) in
timeslot 0 of E1 ports or the FDL of T1 ports using ESF framing. In this mode,
the RAD proprietary protocol is used.
• For T3 ports configured to use the C-bit parity application mode, the user can
configure the T3 module to transfer management traffic through the 28.2 kbps
data link facility (see Section E.6).
Note that each E1 or T1 port (whether internal or external) supports only one
dedicated management timeslot. The maximum number of dedicated timeslot
connections supported for any module depends on the number of links available
on the module, however the total number of dedicated timeslot connections in
one DXC chassis is 64.
This includes both links using a dedicated timeslot, and links using timeslot 0 or
the FDL. However, the total number of management links (for DE1B cards) using
timeslot 0 or the FDL, is maximum 15 (one per module).
The dedicated IP router enables the DXC system to transfer inband IP and SNMP
management messages generated by or addressed to other DXC units, and inband
management traffic addressed to other RAD equipment that operates over E1 and
T1 links, such as the Megaplex, FCD-E1, FCD-E1A, FCD-E1M, FCD-T1, FCD-T1M,
HCD, etc.
In addition, the dedicated IP router can also be reached through the DCL.3 port
configured for out-of-band management, therefore a Telnet host or a network
management station connected to the DXC system can reach all the other equipment
using inband management communication through the desired E1 and T1 ports.
To Supervisory
Connectors of
Managed Equipment
Serial Ports
Network
Management
Station MBE/RAS/A
In the example given in Figure 3-5, a remote access LAN extender type
MBE/RAS/A (available from RAD), is located near the managed equipment
(e.g., DXC, Megaplex, FCD-E1, FCD-T1, etc.), and its serial ports are
connected via cables to the supervisory connectors of the equipment.
The network management station can also connect to the managed equipment
inband. A common inband access method is shown in Figure 3-6. In this
configuration, a frame relay router connects the LAN to the frame relay network,
and the management traffic reaches the DXC units through dedicated timeslots on
the various E1 or T1 links assigned to frame relay management.
FCD
E1 or T1
Frame E1 or T1 FCD
Relay
Network
Network Frame Relay
Management Router DXC
Station
E1 or T1 MEGAPLEX
FCD
The dedicated management traffic routers of DXC systems are able to determine
network topology in accordance with the capabilities of the routing algorithm,
without requiring the user to provide a priori topology information on the network.
Moreover, the routing algorithm also supports automatic switching to an alternate
route in case the currently-selected route fails. The dedicated router operates on
the inband traffic; the user can also enable the routing of out-of-band traffic.
the DXC. Thus, this CONTROL port must be configured to route IP traffic to
other agents (this mode is designated as the AGENT SLIP mode).
The IP router of DXC system No. 2 receives the IP traffic through the port
connected to the DXC system No. 1, and determines whether the traffic is
directed to the local SNMP agent, or to other equipment (in which case, it
transfers the traffic to the CONTROL port).
• DXC system No. 1 is required to transfer the IP traffic along the path selected
by the user toward DXC system No. 2. This is performed by configuring the
appropriate port to transfer inband management traffic. The local IP router,
however, lets pass to the selected port only traffic which is not addressed to
the local SNMP agent.
CONTROL Connector
(SLIP NMS)
Network
Management
Station
DXC No. 1
DXC No. 2
SP-DTE Connector
(SLIP NMS)
CONTROL Connector
(SLIP Agent)
MEGAPLEX-2100F
The advanced capabilities of the DXC system SNMP agents allow easy integration
of the DXC system in wide-area managed communication systems. Its capabilities
support any practical communication network topology, as illustrated in the
example shown in Figure 3-8.
Note When the RIP2 protocol is enabled, the DXC internal router “advertizes”
(broadcasts) its routing tables, thereby enabling other standard RIP2 routers to
detect its presence. However, for management security reasons, the internal DXC
router will not learn routing information from the routing tables advertized by other
RIP2 routers. As a result, the DXC must not be configured to use the RIP2 protocol
when working in a link with any other RAD equipment, except for RAD routers.
In Figure 3-8, the network management station connected through the LAN to the
DXC system No. 1 can manage, using inband communication over the
user-selected links, all the units (another DXC unit, and several Megaplex units),
connected to the remote ends of the corresponding links.
MEGAPLEX-2100F
To Other
Systems
SP-DCE
Connector
MEGAPLEX-2100B
TEST
MAJOR ALARM
B
ON LINE
COMMON LOGIC
A B
ON LINE
POWER SUPPLY
A
Remote
Communication
MINOR ALARM
SYSTEM
Node
Network DXC-30 #2
Management
Station
To Other
Systems
LAN
Network
Management DXC-30 #1
Station
MEGAPLEX-2100B
3.9 Diagnostics
Loopbacks
The DXC system has comprehensive diagnostics capabilities that include various
types of local and remote loopbacks on each port.
In addition, E1, T1, and HDSL ports support the code-activated network loopback,
in accordance with ANSI T1.403 requirements, and the inband activated loopback
in accordance with ANSI T1E1.2/93-003. T1 ports operating with ESF framing also
support the FDL-activated network line loopback and payload loopback
commands.
Diagnostics 3-51
Chapter 3 Functional Description DXC-8R/10A/30/30E Installation and Operation Manual
In addition, each STM-1 port of the DFSTM-1 module includes indicators that light
in case of local or remote loss of signal.
Statistics Collection
For each T1 port operating with the ESF frame format, the DXC system stores T1 line
statistics in compliance with the ANSI T1.403-1989 requirements. The DXC system
also supports local statistics in accordance with AT&T Pub. 54016 and RFC 1406.
For each E1 port operating with the CRC-4 function enabled, the DXC system collects
and stores E1 line statistics in compliance with ITU-T Rec. G.706 and RFC 1406.
The DXC system also supports the collection of performance statistics for the E3 port
in accordance with RFC 1407, for the T3 port in accordance with RFC 1407,
ANSI T1 107, ANSI T1 107a, and for the STM-1 port in accordance with
RFC 2258. No statistics are collected for the internal ports.
General
The DXC system stores alarms detected during its operation in a buffer that can
hold up to 100 alarms.
In addition to the alarms detected within the chassis, the DXC can also report the
status of an external alarm sensor (dry contacts), connected to the alarm input lines
in the station clock connector of the DCL.3 module. For unattended installations,
the external alarm sensor can be used to report an emergency condition at the
remote site (fire or intrusion alarm), excessive temperature, etc.). Another
application for the alarm input is to monitor the status of the fan tray installed
under a DXC-30 or DXC-30E.
The alarm input is active only on the active DCL.3 module, therefore when
common logic subsystem redundancy is used, it is necessary to connect the alarm
sensor in parallel to both DCL.3 modules installed in the chassis.
The presence of an alarm condition is indicated by status indicators located on the
front panel of the DXC enclosure, and on the DCL.3 modules. Separate indications
are provided for major and minor alarms.
In addition, the DXC system has an alarm relay that enables the activation of bay
alarms, remote indication of alarms, etc.
The relay includes one set of normally-open contacts, and one set of
normally-closed contacts, with a common reference contact. The relay contacts
are rated at maximum 60 VDC across open contacts, and maximum 1A through
closed contacts, and are floating with respect to the equipment chassis.
The alarm relay is energized when the DXC system is powered and operating
normally, and is de-energized when DXC system power is off. In addition, the user
can select the state of the relay contacts (closed or open) during major and minor
alarm conditions.
Alarm Reporting
The alarms stored in the DXC alarm buffer can be transmitted automatically
through the serial management access ports, for display on a supervision terminal;
when SNMP management is used, alarms are also sent to certain management
stations as traps.
DCL.3 modules with RS-232 interfaces have an additional serial port that can be
configured to operate as a dial-out port, for automatic reporting of alarms to
remote locations. This port is intended for connection to a Hayes or
Hayes-compatible dial-up modem.
The reporting method can be programmed in accordance with the following
options:
• Always send a report whenever a new alarm condition is detected.
• Send a report only upon the detection of a major alarm.
• Reporting disabled (no dial-out function).
When it is necessary to report an alarm condition, the DXC system initiates the call
set up, and then, after the destination answers, sends the complete contents of the
alarm buffer. Following the transmission of the alarm buffer contents, the DXC
system disconnects automatically.
To increase reporting reliability, the user can define the number of dialing retries,
and an alternate directory number to be called in case the primary directory
number cannot be reached. If nevertheless the call cannot be established, the full
contents of the buffer will be sent the next time a call is set up.
Alarm Processing
As explained above, alarms can be read on-line by the system operator using a
network management station, a Telnet host, or a supervision terminal. The system
operator can then perform comprehensive testing on each type of module, to
determine the causes of alarm messages and to return the system to normal operation.
To expedite the handling of alarms and reduce the information load during system
malfunctions, the system operator can use two dedicated tools:
• Masking of alarm conditions, to prevent continuous reporting of known alarm
conditions, e.g., during maintenance activities.
4.1 Introduction
This Chapter provides installation and operation instructions for the DXC-8R,
DXC-10A, DXC-30 and DXC-30E enclosures, and for system modules that are part
of the basic system configuration.
This Chapter includes five sections:
• Section I – GENERAL – presents general information related to site
requirements, power supply considerations, installation and operation
procedures.
• Section II – INSTALLATION AND OPERATION OF DXC-30 ENCLOSURE –
provides mechanical and electrical installation and operation instructions for
the DXC-30 enclosure and the system modules, DPS and DCL.3.
• Section III – INSTALLATION AND OPERATION OF DXC-30E ENCLOSURE –
provides mechanical and electrical installation and operation instructions for
the DXC-30E enclosure and the system modules, DPS and DCL.3.
• Section IV – INSTALLATION AND OPERATION OF DXC-10A ENCLOSURE –
provides mechanical and electrical installation and operation instructions for
the DXC-10A enclosure, and for the Common Logic module, DCL.3.
• Section V – INSTALLATION AND OPERATION OF DXC-8R ENCLOSURE –
provides mechanical and electrical installation and operation instructions for
the DXC-8R enclosure, and for the Common Logic module, DCL.3.
Introduction 4-1
Chapter 4 Installation and Operation DXC-8R/10A/30/30E Installation and Operation Manual
Safety Precautions
LASER
KLASSE1
CLASS 1
LASER
PRODUCT
DXC modules are shipped with protective covers installed on all the optical
connectors. Do not remove these covers until you are ready to connect optical
cables to the connectors. Keep the covers for reuse, to reinstall the cover over the
optical connector as soon as the optical cable is disconnected.
4-2 Introduction
DXC-8R/10A/30/30E Installation and Operation Manual Chapter 4 Installation and Operation
Section I General
General Requirements
AC-powered DXC-8R, DXC-10A, DXC-30 and DXC-30E units should be installed
within 1.5m (5 feet) of an easily-accessible grounded AC outlet capable of
furnishing the required supply voltage, in the range of 100 to 240 VAC. The
DC-powered DXC-8R, DXC-10A, DXC-30 and DXC-30E units require a -48 VDC
power source.
Allow at least 90 cm (36 inches) of frontal and rear clearance for operator access.
As a minimum, always allow at least 10 cm (4 inches) clearance at the rear of the
unit for interface cable connections.
The ambient operating temperature of DXC systems should be 0 to 45°C
(32 to 104°F). Relative humidity can be up to 90%, non-condensing.
Grounding
The DXC enclosures must be grounded at all times during operation, and must
remain grounded whenever connected to power or telecommunication
networks. For your safety, remember that under certain external fault
Warning conditions, dangerous voltages may appear on the cables connected to the
DXC enclosure. Therefore, as long as cables are connected to the DXC
enclosures, the enclosure must be grounded to a reliable grounding system.
All the DXC enclosures support grounding through the protective (grounding)
conductor of the power cable. In addition, the DXC enclosures have a grounding
screw located on the power supply panel.
When the DXC is installed in racks, the rack itself should also be grounded in
accordance with the standard practice and the locally-applicable regulations.
Installing the DXC in a grounded rack provides additional protection against fault
conditions.
Any interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnection of the protective earth terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Caution DXC modules contain components sensitive to electrostatic discharge (ESD). To
prevent ESD damage, always hold a module by its sides, and do not touch the
module components or connectors.
Before touching a module, it is recommended to discharge the electrostatic charge
of your body by touching the frame of a grounded equipment unit.
Note The maximum power consumption of each DXC-30E backplane section is 26A
(130W), for a total of 40A per DXC-30E.
Cooling Requirements
The DXC-8R and DXC-10A chassis have internal cooling fans, which improve
internal airflow within the system.
The DXC-30 and DXC-30E units are cooled by free air convection, therefore in
rack installations it is necessary to leave sufficient space (at least 1U) above and
below the units, to enable free air flow. Additionally, DXC-30E features an internal
cooling fan on the power supply module, to improve local air flow within the
system.
For extreme environmental conditions, an external fan tray is available for the
DXC-30 and DXC-30E units. The fan tray is always required when a DFSTM-1,
D8SL or certain types of DIM modules (see DIM Installation and Operation
Manual) are installed in the chassis.
Note Do not block ventilation holes on the DXC units.
To ensure proper flow of cooling air within DXC enclosures always install blank
panels over all the unused slots.
Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistivity,
yet are not insulators.
Covering all empty slots is also required for reasons of personal safety, and to
ensure proper flow of cooling air within DXC enclosures.
Warning
Link Connections
DXC systems have one RJ-45 or D-type connector for each balanced E1 or T1
port, and for each HDSL port. For E1 interfaces, there are two additional BNC
connectors for the unbalanced interface. Appendix A provides the pin allocation
for the connectors.
North American Users: The D4T1, D8T1, D8U, and D16U modules are not
intended to be directly connected to exposed plant subject to power crosses and
induction.
Fractional STM-1, E3 and T3 ports with copper interfaces have two BNC
connectors. Fiber-optic interfaces are equipped with ST, FC/PC or SC connectors,
in accordance with order.
The maximum allowable line attenuation between the DXC ports and the network
interface depends on the type of port interface:
• Balanced T1 and E1 interfaces, and balanced station clock interface:
For a port interface without CSU or LTU, the maximum range is 10 dB.
For a port interface with CSU or LTU, the maximum range is 36 dB.
• Unbalanced E1 interface, and unbalanced station clock interface. The range
complies with the requirements of ITU-T Rec. G.703 (up to 10 dB attenuation).
For an unbalanced E1 interface with LTU, the maximum range is 36 dB.
• Unbalanced fractional STM-1, E3 and T3 electrical interfaces. The range
complies the requirements of ITU-T Rec. G.703 (450 feet).
• HDSL interfaces - comply with ETS 101 135 requirements.
• Fiber-optic interfaces - refer to Section 1.4.
• DIM and DHS interfaces. The range depends on the characteristics of the
serial interfaces: V.24 (DHS only), V.35, X.21, or HSSI, depending on module
version.
• IDSL interface – complies with ITU-T Rec. G.961.
• SHDSL interface – complies with ITU-T Rec. G.991.2
Note When using redundant DCL.3 modules, you can connect the terminal, respectively
the modem, in parallel to the corresponding serial port connectors of the two
modules by means of a simple Y-cable, because at any time only one module
interface is active.
Ethernet ports of redundant DCL.3 modules do not require any special connections.
The other 15 slots, designated I/O1 through I/O15, are intended for I/O modules.
Each I/O slot can accept any type of I/O module, except for the D16U, i.e., DT1B,
DT3, DE1B, DE3, DHL/E1, DHL/E1/2W, DIM, DHS, D8HS, D8U, D8SL, D4T1,
D8T1, D4E1, or D8E1. A DFSTM-1 module must always be installed in I/O slot 1.
Rear View
Figure 4-1 shows a typical rear view of the DXC-30 enclosure and identifies the
enclosure slots and their use. Note that each slot is marked with a label, which
indicates the type of module that can be installed in each slot.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
System Slots I/O Slots
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
PS-A PS-B CL-A CL-B I/O 1 I/O 2 I/O 7
DPS DPS DCL.3 DCL.3 DHS I/O 3 DE1 I/O 4 DT1 I/O 5 DE1 I/O 6 DHS DE1 I/O 8 DHS I/O 9 DT1 I/O 10 DE1 I/O 11
DE1
I/O 12 DT1 I/O 13 DHS I/O 14 DE1 I/O 15 DHS
L R CH1 L R L R L R CH1 R CH1 L R L R L R L R CH1 L R CH1
C C
O O L L L L L L L L L L
N N O O O O O O O O O O
POWER T T S S S S S S S S S S
R R
RS-530/V.35
RS-530/V.35
RS-530/V.35
RS-530/V.35
RS-530/V.35
O O 1 1 1 1 1 1
L L 1 1 1 1
POWER 1 I 1 1 1
I I I I I
N N N N N N
E 1 ON E 1 ON
T 2 T 2
H H
E E O O O O O O
R R U U U U U U
N N T T T T T T
E E
T T
DXC-30M-PS/DC/N L R CH2 L R L R L R CH2 L R CH2 L R L R L R L R CH2 L R CH2
L L L L L L L L L L
VDC-IN ALM ALM O O O O O O O O O O
MJ ON MJ ON S S S S S S S S S S
MN TST MN TST 2 2 2 2 2 2
RS-530/V.35
RS-530/V.35
RS-530/V.35
RS-530/V.35
RS-530/V.35
0
CAUTION: FOR CONTINUED S S 2 2 2 2
PROTECTION AGAINST RISK OF 2 I 2 I I 2 I 2
FIRE, REPLACE ONLY WITH SAME T T I
TYPE AND RATING OF FUSE.
N N N N N
A A
-48
T T
I I
O O O O O O O O
U U U U U U
N N
T T T T T T
C C
L L
K K
Front Panel
The front panel of the DXC-30 enclosure includes labels for the show-through
areas of the status indicators located on each system module. Note that the
indicators are arranged in groups (one group for each system module), that are
positioned before the corresponding module slot.
Figure 4-2 shows the front panel of the DXC-30 enclosure. Table 4-3 lists the
functions of the indicators located on the DXC-30 front panel.
Indicator Function
TEST Indicates that a test (or test loop) is being performed on one of the local DXC-30 modules
MAJOR ALARM Indicates that a major fault has been detected in one of the DXC-30 modules
MINOR ALARM Indicates that a minor fault has been detected in one of the DXC-30 modules
ON LINE The ON-LINE indicators, located on the DCL.3 and DPS modules, are seen through the
front-panel. Their functions are as follows:
• The ON-LINE indicator of a module lights steadily when the module is operating
properly and is active
• The ON-LINE indicator of a module is off when the corresponding module is
defective, or is not installed.
• For DCL.3 modules, the ON-LINE indicator flashes when the module is operating
properly, but is in standby (the other module of the same type is active)
However, if you are installing a DXC-30 already equipped with modules, make
sure you disconnect all the cables from the enclosure before installing the DXC-30.
Module Panels
Typical panels of DPS modules are shown in Figure 4-4. Table 4-4 describes the
functions of the panel components.
DPS DPS
Grounding
Screw ON/OFF Switch
and
POWER Power Indicator
ON/OFF Switch
and POWER
Power Indicator
Grounding
Label Screw
DXC-30M-PS/AC
100-240VAC
Label
3.15A F 250V
AC Power
DXC-30M-PS/DC/N
Connector
VDC-IN
DC Power
Connector
Fuse
CAUTION : FOR CONTINUED
0
PROTECTION AGAINST RISK OF
FIRE, REPLACE ONLY WITH SAME
TYPE AND RATING OF FUSE.
-48
DXC-30M-PS/AC DXC-30M-PS/DC/N
Item Description
ON/OFF Switch Turns the power on/off. The switch includes an internal power indicator, which
lights when the input voltage is connected
Label Indicates the nominal mains operating voltage of the module and the fuse rating
Grounding Screw Connection of protective ground
Power Connector Connector for the module input power
Internal Jumpers
DC-powered DPS modules include one internal jumper, designated JP3.
AC-powered DPS modules include one internal jumper, designated P101. These
jumpers control the connection between the internal digital ground and the frame
(enclosure) ground. The location of the jumper for the DC-powered and
AC-powered modules is shown in Figure 4-5 and Figure 4-6, respectively.
Setting the jumper to NO may render the equipment unsafe for connection to
unprotected telecommunication networks in certain locations where
permanent excessive voltages are present on the line.
Warning
Digital Ground
YES
NO
Connected
to Frame Ground
JP3
Digital Ground
YES NO
Not Connected
to Frame Ground
Digital Ground
Not Connected
NO to Frame Ground
The module is delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground. If
redundant modules are installed, make sure that the jumper is set to the same
position on both modules.
Module Installation
Install the DPS modules as follows:
1. Set the power switch of the DPS module to OFF.
2. Insert the DPS module in slot PS-A of DXC-30.
If an additional DPS module is to be used as backup, install it in slot PS-B.
If the enclosure is already operating, you can install a backup DPS module in an
Note operating enclosure without turning off the enclosure power. In this case, after the
module is installed, connect its power cable, and then set its power switch to ON.
Module Panels
Figure 4-7 shows the panels of the various DCL.3 module versions. The module
panels are similar, except for the network interface connector, which depends on
the DCL.3 version and a DIP switch located on modules with Ethernet interface.
1 ON 1 ON
E 2 E 2
T T
H H
M E E
N R R
G N N
E E
T T
ALM ALM ALM
Figure 4-7. Module MJ
O
N
MJ
O
N
MJ
O
N
S S S
T T T
A A A
T T T
I I I
O O O
N N N
C C C
L L L
K K K
Item Function
CONTROL 9-pin D-type female connector, for connection to an ASCII supervision terminal, network
Connector management station, or RS-232 CONTROL port of another module.
Connector pin allocation is given in Appendix A.
DIP Switch (on Used to control supervisory port parameters.
DCL.3 versions
with Ethernet
interface)
Section 1 This section selects the source of the parameters for the supervisory ports.
OFF The supervisory ports operate according to the user-defined parameters.
ON The DXC uses the factory-default supervision port parameters (9600 bps,
eight data bits, no parity, one stop bit, terminal mode).
The DCL.3 module is shipped with both sections set at OFF (the left-hand position, as
shown in Figure 4-6). This is also the position required during normal operation,
therefore make sure that both switch sections are set to OFF.
Section 2 Not used.
MNG Connector 9-pin D-type female connector, for connection to a modem (needed to support the
(on DCL.3 dial-out function), or RS-232 supervisory port of another module.
versions with Connector pin allocation is given in Appendix A.
RS-232 interface)
ETHERNET RJ-45 connector for 10/100BaseT interface, enables connection to Ethernet LAN.
connector
Connector pin allocations are given in Appendix A.
(on DCL.3
versions with
Ethernet interface)
TST indicator Lights when a test (or test loop) is being performed on one of the local DXC modules
MJ ALM indicator Blinking when a major fault has been detected in one of the DXC modules
MN ALM indicator Lights when a minor fault has been detected in one of the DXC modules
ON indicator Lights steadily when the module is the active DCL.3 module and is operating properly.
Flashes when the module is operating properly, but is in standby (the other DCL.3
module is active)
STATION CLK One RJ-45 connector and one BNC coaxial connector, for connection to an external
Connectors (station) clock source. The RJ-45 connector also includes the external alarm input and the
alarm relay contacts.
Connector pin allocations are given in Appendix A.
Internal Settings
The DCL.3 module consists of a main board and an interface board for the second
RS-232 interface or Ethernet port.
Internal settings are required on the main board, and on the RS-232 interface
board (no user settings are required on the Ethernet interface boards).
Item Function
Jumper FGND JP1 Controls the connection of pins 3 and 6 (shields) in the RJ-45 connector
serving the balanced STATION CLK interface to frame ground:
YES Pins 3 and 6 (shields) connected to frame ground.
NO Pins 3 and 6 (shields) not connected to frame ground.
Default: NO
Jumpers JP2, JP3 Selects the STATION CLK interface:
UNBAL Unbalanced STATION CLK interface (use BNC connector).
BAL Balanced STATION CLK interface (use RJ-45 connector).
Default: BAL
Jumper RXGND JP4 Controls the connection of the shield of the STATION CLK BNC connector
serving the unbalanced interface to frame ground:
YES Shield connected to frame ground.
NO Shield not connected to frame ground.
Default: NO
Switch S1 Used to select housekeeping options
Section 1: DB INIT Allows you to load the default (factory-preset) configuration:
OFF Configuration parameters determined by the user
ON Enforces the default configuration parameters. The change will be
made after you turn the DXC-30 off for a short time and then turn
it back on.
Default: OFF
Section 2: PASSWRD Selects the source of the password and management address (node number)
for the supervisory port:
OFF Password and node number selected by the user.
ON Enforces the default password (RAD) and node number 0. The
change will be made after you turn the DXC-30 off for a short time
and then turn it back on.
Default: OFF
Section 3 Not used. Must be set to OFF.
Section 4 Not used. Must be set to ON.
Section 5 Not used. Must be set to OFF.
Section 6: DP MNG Selects the source of the MNG port parameters:
OFF Parameters defined by the user.
ON Enforces the default parameters (9.6 kbps, 8 data bits, no parity,
1 stop bit, operation in the terminal mode).
Default: OFF
Item Function
Switch S1 (Cont.)
Section 7: DP SP Selects the source of the CONTROL port parameters:
OFF Parameters defined by the user.
ON Enforces the default parameters (9.6 kbps, 8 data bits, no parity,
1 stop bit, operation in the terminal mode).
Default: OFF
This switch section is connected in parallel with section 1 of the DIP switch
located the module panel. For normal operation, both switches must be set
to OFF; the default parameters are enforced by setting either switch to ON.
Section 8: SW LOAD Not used. Must be set to OFF.
You should reload the default supervisory port password and communication
Note
parameters if the current parameters are not known, and the supervision terminal
cannot communicate with the DXC-30. In such a case, set sections 7 (DP SP) and 2
(PASSWRD) of the internal DIP switch S1 to ON, turn the DXC-30 off for a short
time, and then turn it back on.
S1 S1
S2 S2
S1 DTE
DCE
DTE
S2 DCE
Module Installation
Install the DCL.3 module in slot CL-A of DXC-30. If an additional DCL.3 module is
used, install it in slot CL-B of the DXC-30.
Jumper JP1 FGND
Pins 3, 6 in STATION
CLK Connector
JP1 Connected to
YES Frame Ground
Pins 3, 6 in STATION
NO CLK Connector
Reset JP1
not Connected to
Push-Button
Frame Ground
RESET
SW1
FGND DB INIT
NO
PASSWRD
JP1
YES DEBUG 1
WTCHDOG
BAL
BAL
PC/SP S1
DP MNG
JP2
JP3
UBL DP SP
SW LOAD
UNBAL
NO
OFF ON
JP4
YES
RXGND
BAL
NO STATION CLK BNC
BAL
JP4 Shield not Connected JP3 JP2 Balanced
to Frame Ground (RJ-45)
Installation Procedures
Refer to corresponding module Installation and Operation Manual.
Figure 4-10.A shows the front panel of an AC-powered fan tray, DXC-30M-FT/AC
and Figure 4-10.B shows the front panel of a DC-powered fan tray
DXC-30M-FT/48. Table 4-7 explains the functions of the front panel items.
FAN-TRAY
N/O N/C
PWR ALM
PWR ALM
0 -48
COM
Item Function
PWR Indicator Green indicator, lights when the fan tray is powered
ALM Indicator Red indicator, lights when a malfunction is detected in the fan tray (for example, when
one of the fans does not operate)
Alarm Connector 3-contact connector, for connection to the contacts of the fan tray status indication relay.
• During normal operation, the N/C contact is internally connected to the COM
contact, and the N/O contact is open circuited.
• When a problem is detected, the N/O contact is internally connected to the COM
contact
Power Connector Connection of external power source:
• AC-powered fan tray: 3-prong IEC connector.
• DC-powered fan tray: 3-pin connector
Grounding
Connect a short, thick copper braid between the grounding screw on each DPS
module panel and a nearby grounding point.
Caution When a D8U module is installed in the DXC-30, it is necessary to supply a feed
voltage from an external source, for example, a Ringer-2000. Since an external
voltage source can supply voltage even when the DXC is not operating, observe
the following precautions:
1. Never connect external voltages to modules installed in a DXC enclosure if the
DXC is not operating: first turn it off.
2. Do not connect/disconnect the external voltage source while it is operating.
3. Always turn the DXC enclosure on before turning the external feed voltage
source on.
4. Always turn the external feed voltage source off, before the DXC enclosure is
turned off.
Power Connection
• Check that the POWER switches on the DPS modules, and when applicable,
on any Ringer-2000 unit connected to the DXC, are set to OFF.
• Connect the power cable(s) first to the connector on the DPS module, and
then to the power outlet. For DC cables, pay attention to polarity.
Note When redundant power supplies are used, it is recommended to connect the
power cables to outlets powered by different circuits.
Connect the station clock signal to the connector corresponding to the interface
type needed by your external (station) clock source. Do not connect clock signals
to both interfaces at the same time!
The RJ-45 connector has additional functions (DXC alarm relay contacts,
±5V/16mA auxiliary output and external alarm input). To use the additional
functions, it is recommended to connect the RJ-45 STATION CLK connectors, by
means of an appropriate cable, to a distribution panel. Refer to Appendix A for a
description of the connector pin functions.
Caution To prevent damage to relay contacts, it is necessary to limit, by external means, the
maximum current that may flow through the contacts (maximum allowed current
through closed contacts is 1 A). The maximum voltage across the open contacts
must not exceed 60 VDC.
Grounding
The fan tray is grounded by installing it in a properly grounded equipment rack.
In addition, the power connector also includes a protective ground pin. See
Warning on page 4-22 for grounding precautions.
Power Connections
Caution The fan tray does not have a power switch, and therefore it starts operating as soon as
power is applied. A customer-provided circuit breaker with appropriate ratings, placed
at a accessible location, must be installed in series with the fan tray power line, to limit
the maximum current in case of fault, and to serve as on/off switch.
rfer
Refer to the site installation plan to identify the power cable intended for
connection to the fan tray.
Make sure that the power is not connected, for example, set the corresponding
circuit breaker on the rack power distribution panel to OFF.
Connect the power cable to the fan tray power connector.
Caution Prepare the connections to the header before inserting the header into the mating
relay connector. After fastening the screw terminals, isolate the screws, to prevent
the possibility of ESD when touched by the bare hand.
Figure 4-11 shows the connection method of the cable to the header. Check for
correct connections.
N/O Contact:
Connect to Pin 5
For your safety, make sure the DXC-30 grounding complies with the
requirements listed in Section 4.2.
Warning
Turn-on
1. If a fan tray is installed, turn it on by applying power. Check that the fan tray
PWR indicator turns on, and the ALM indicator is off.
2. To turn the DXC-30 on, set the power switch of the DPS module to ON.
If the DXC-30 is equipped with two DPS modules, it starts operating as soon as
the power switch of the first module is set to ON. To use redundancy, turn on
the other DPS module as well.
3. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-30, you may also turn it on.
Turn-off
1. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-30, turn it off.
2. To turn the DXC-30 off, set the power switch of the DPS module to OFF.
If the DXC-30 is equipped with two DPS modules, you must set both power
switches to OFF.
3. If a fan tray is installed, turn it off by disconnecting its power.
General Description
The DXC-30E enclosure has 19 module slots. Four slots are assigned to the system
modules. Two slots each are assigned for DCL.3 and DPS modules, respectively, to
provide support for the redundancy option:
• System slots PS-A and PS-B: for DXC-30ME-PS/AC and DXC-30ME-PS/DC
modules (referred to below as DPS modules).
• System slots CL-A and CL-B: for DCL.3 modules.
The other 15 slots, designated I/O1 through I/O15, are intended for I/O modules.
Each I/O slot can accept the following types of I/O modules: DT1B, DT3, DE1B,
DE3, DHL/E1, DHL/E1/2W, DIM, DHS, D8HS, D16U, D8SL, D8T1 or D8E1. A
DFSTM-1 module must always be installed in I/O slot 1. The modules are inserted
from the rear side.
Rear View
Figure 4-12 shows a typical rear view of the DXC-30E enclosure and identifies the
enclosure slots and their use. Note that each slot is marked with a label, which
indicates the type of module that can be installed in each slot.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
PS-A PS-B CL-A CL-B I/O 1 I/O 2 I/O 3 I/O 4 I/O 5 I/O 6 I/O 7 I/O 8 I/O 9 I/O 10 I/O 11 I/O 12 I/O 13 I/O 14 I/O 15
DPS DPS DCL.2 DCL.2 DE1/B DE1/B DT1 DT1 DE1/B DT1 DE1 DE1 DE1 DE1 DE1 DIM DIM DIM DE1
DXC-30EM-PS/DC L R L R L R DCE-V35 DCE-V35 DCE-10BT
C C L R L R L R L R L R L R L R
48V LOS
O O L L LOS LOS LOS LOS LOS LOS LOS
N N O O
T T S S
POWER R R RX RX RX RX RX RX RX
POWER
O O
L L 1 1
L L L L L L L
I I I I I I I
I I N N N N N
N N 1 N N
1 ON 1 ON K K K K K K K
E 2 E 2
T T
H H 1 1 1 1 1 1 1
E E O O
R R U U TX TX TX TX TX
DXC-30M-PS/AC TX TX
N N T T
100-240VAC E E
T T COLL LINK
3A T 250V L R L R L R
L R L R L R L R L R L R L R
ALM ALM LOS
L L LOS LOS
MJ ON MJ ON LOS LOS LOS LOS TX RX LOS
O O
+ S S
V.35
V.35
MN TST MN TST RX RX RX RX RX RX RX
_ 2 2
S S L L L L L L L
T T
CHASSIS I I I I I I I
A A I I
GND T T N N N N N N N
N N 2
I I K K K K K K K
O O
N N 10 BASE-T
2 2 2 2 2 2 2
CAUTION: FOR CONTINUED
O O
PROTECTION AGAINST RISK OF C C
FIRE, REPLACE ONLY WITH SAME
L L U U TX TX TX TX TX TX TX
TIPE AND RATING OF FUSE
K K T T
L R L R
L L
O O
S S
HDSL HDSL
L R L R
L L
O O
S S
HDSL HDSL
Front Panel
The front panel of the DXC-30E enclosure includes labels for the show-through
areas of the status indicators located on each system module. Note that the
indicators are arranged in groups (one group for each system module) that are
positioned before the corresponding module slot.
Figure 4-13 shows the front panel of the DXC-30E enclosure. Table 4-8 lists the
functions of the indicators located on the DXC-30E front panel.
Indicator Function
TEST Indicates that a test (or test loop) is being performed on one of the local DXC-30E modules
MAJOR ALARM Indicates that a major fault has been detected in one of the DXC-30E modules
MINOR ALARM Indicates that a minor fault has been detected in one of the DXC-30E modules
ON LINE The ON LINE indicators located on the DCL.3 and DPS modules are seen through the
front-panel. Their functions are as follows:
• The ON LINE indicator of a module lights steadily when the module is operating
properly and is active.
• The ON LINE indicator of a module is off when the corresponding module is
defective, or is not installed.
• For DCL.3 modules, the ON LINE indicator flashes when the module is operating
properly, but is in standby (the other DCL.3 module is active)
After attaching the brackets, fasten the enclosure to the rack by four screws (two
on each side).
However, if you are installing a DXC-30E already equipped with modules, make sure
you disconnect all the cables from the enclosure before installing the DXC-30E.
Module Panels
Typical DPS module panels are shown in Figure 4-15. Table 4-9 describes the
functions of the panel components.
Table 4-9. PS Module, Panel Components
Item Description
ON/OFF Switch Turns the power on/off. Includes an internal power indicator, which lights when
the input voltage is connected
Label Indicates the nominal mains operating voltage of the module and the fuse rating
Grounding Screw Connection of protective ground
Power Connector Connector for the module input power
Label Label
DXC-30M-PS/AC DXC-30EM-PS/DC
100-240VAC 48V
5A T 250V
AC Power DC Power
Connector Connector
+
_
Fuse
CHASSIS
GND
DXC-30ME-PS/AC DXC-30ME-PS/DC
Internal Jumpers
The DPS module includes one internal jumper, designed JP1. This jumper controls
the connection between the internal digital ground and the frame (enclosure)
ground. The location of the jumper is shown in Figure 4-16.
The module is delivered with the jumper set to FGND. If necessary, you can set
the jumper to DGND to float the signal ground with respect to the frame ground. If
redundant modules are installed, make sure that the jumper is set to the same
position on both modules.
DC Input Internal
Fuses F1, F2 Fuses F3, F4
(Only for 48 DC (Only for AC
Powered Modules) Powered Modules)
F1
F2 F3
F4
JP1
Internal Fuses
In addition to the jumper, the DPS modules include several fuses:
• Fuse F5 (1A fast-blow) protects the supply line to the cooling fan. The fuse can
be replaced in maintenance facilities.
• Fuses F1, F2 protect the DC input line of DC-powered DPS modules. The
fuses can be replaced by field service personnel.
• Fuses F3, F4 are located only on AC powered modules (in addition to the fuses
located in the AC power connector). These fuses protect internal lines, and
should be replaced only in maintenance facilities.
Module Installation
Install the DPS modules as follows:
1. Set the power switch of the DPS module to OFF.
2. Insert the DPS module in slot PS-A of DXC-30E.
3. If an additional DPS module is to be used as backup, install it in slot PS-B.
Note If the enclosure is already operating, you can install a backup DPS module in an
operating enclosure without turning off the enclosure power. In this case, after the
module is installed, connect its power cable and then set its power switch to ON.
Module Panels
Figure 4-17 shows the panels of the various DCL.3 module versions intended for
installation in the DXC-30E. The module panels are similar, except for the network
interface connector, which depends on the DCL.3 version. Table 4-5 describes the
functions of the panel components.
Internal Settings
The internal settings of the DCL.3 module for the DXC-30E enclosure are similar to
those required for the 3U-high DCL.3 version. Refer to Section 4.6 for details.
Module Installation
Install the DCL.3 module in slot CL-A of DXC-30E. If an additional DCL.3 module
is used, install it in slot CL-B of the DXC-30E.
DCL.3 DCL.3
C C
O O
N N
T T
R R
O O
L L
1 ON
E 2
T
H
M E
N R
G N
E
T
ALM ALM
MJ ON MJ ON
MN TST MN TST
S S
T T
A A
T T
I I
O O
N N
C C
L
K
For your safety, make sure the DXC-30E grounding complies with the
requirements listed in Section 4.2.
Warning
Turn-on
1. To turn the DXC-30E on, set the power switch of the DPS module to ON.
If the DXC-30E is equipped with two DPS modules, it starts operating as soon
as power is applied to the first DPS module. To use redundancy, turn on the
other DPS module as well.
2. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-30E, you may also turn it on.
• The ON-LINE indicators of the power supply modules, and the ON-LINE
indicator of one DCL.3 module must light steadily. If two DCL.3 modules are
installed, the ON-LINE indicator of the standby module flashes.
Turn-off
1. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-30E, turn it off.
2. To turn the DXC-30E off, set the power switch of the DPS module to OFF.
If the DXC-30E is equipped with two DPS modules, you must set both power
switches to OFF.
General Description
The DXC-10A enclosure consists of a system section, and a section for I/O
modules.
• The system section includes two modules:
One DCL.3 module. The network interface can be ordered in accordance
with the management desired connection method: RS-232 or 10/100BaseT
interface.
One pre-installed power supply module. DXC-10A is delivered either with
an AC power supply which operates on 100 through 240 VAC, or with a
DC power supply that operates on -48 VDC (nominal), in accordance with
order.
In the DXC-10A power supply, the signal ground is permanently connected to the
Note
frame ground.
• The I/O section of the DXC-10A enclosure has five I/O module slots,
designated I/O 1 through I/O 5. Each of these slots can be fitted with a DT1,
DT1B, DE1, DE1B, DT3, DE3, DIM, DHS, D8HS, D8E1, D8T1, D4E1, D8T1,
D8SL or D8U module. The DHL/E1 or DHL/E1/2W modules can be installed
in I/O slot 2 or 4. A DFSTM-1 module must always be installed in I/O slot 1.
The modules are inserted from the rear side.
Rear View
Figure 4-18 and Figure 4-19 show typical rear views of DXC-10A enclosures and
identify the slots and their use.
• Figure 4-18 shows an AC-powered DXC-10A.
• Figure 4-19 shows a DC-powered DXC-10A.
Both DXC-10A units are shown with the DCL.3 module version with 10/100BaseT
network interface.
Note the labels which designate the type of module that can be installed in each
I/O slot; in addition, each slot is keyed, therefore it is not possible to install the
wrong module type.
Fuse DCL.3 Module
DE1
R
R
2
1
DHS
TST
ON
ON
DCL.3
POWER
I/O 3
L
I/OU 5
N
N
1
2
O
I
U
S
S
T
T
L
L
1
2
ALM
CL
MN
MJ
RS-530/V.35 RS-530/V.35
O
O
C
R
T
K
S
H
R
N
E
L
T
DT1
DT1
DE1
R
R
2
1
1
I/O 4
I/O 2
I/O 1
L
L
L
N
O
S
S
L
L
I
O
O
U
O
I
U
S
100-240V 2A T 250V
T
T
L
L
1
Power Supply Grounding I/O Slot 1 I/O Slot 3 I/O Slot 2 I/O Slot 5 I/O Slot 4
Unit Screw
TST
ON
DHS
DCL.3
ON
POWER
I/O 3
ALM
1
E 2
MN
CL
MJ
H
R
N
E
E
T
O
O
O
C
C
S
K
T
L
I
DE1
R
DT1
I/O 2
I/O 1
L
N
N
I
O
O
I
U
U
S
S
T
T
L
L
1
2
100-240V 2A T 250V
DCL.3
Module
DCL.3
2
DHS
TST
1
ON
DE1
ON
R
POWER
VDC-IN
I/O 3
I/O 5
1
2
L
ALM
MN
MJ
C
N
L
RS-530/V.35 RS-530/V.35
I
U
U
O
O
S
S
T
T
L
L
1
2
O
O
C
K
O
T
S
H
R
N
L
T
DT1
DT1
DE1
R
R
1
2
I/O 4
I/O 2
0 -24
I/O
-48
L
1
N
I
O
O
S
U
U
T
T
S
L
L
L
1
2
I/O Slot I/O Slot I/O Slot I/O Slot I/O Slot
Power Supply Grounding
Unit 1 3 2 5 4
Screw
TST
ON
DHS
DCL.3
ON
POWER
VDC-IN
I/O 3
ALM
1
E 2
MN
CL
MJ
H
R
N
E
E
T
O
O
O
C
C
S
K
T
L
I
DT1
R
R
DE1
0 -24
I/O 2
I/O 1
L
-48
N
O
O
U
U
S
S
T
T
L
2
1
Figure 4-19. DC-Powered DXC-10A, Rear View
Front Panel
Figure 4-20 shows the front panel of the DXC-10A enclosure.
TEST
POWER SUPPLY
MAJOR ALARM
MINOR ALARM
SYSTEM
Table 4-10 lists the functions of the indicators located on the DXC-10A front panel.
DXC-10A Installation
The DXC-10A enclosure is intended for installation in 19-inch racks, however it
can also be installed on shelves and desktops.
For rack installation, it is necessary to install two brackets to the sides of the unit.
The rack mount installation kit, RM-DXC10A, is supplied with the unit. As
illustrated in Figure 4-21, you may install the brackets in two ways, to orient the
unit in accordance with your requirements (either with the DXC-10A front panel
toward the front of the rack, or with the module panels toward the front).
Install Brackets Here if
You Want Access to Module Panels
From the Front of the Rack
After fastening the DXC-10A to the rack, connect a short, wide copper braided
strap between the grounding screw, and the rack ground bus.
In general, the DXC-10A is installed in its designated location before it is equipped
with modules, and then it is equipped with the prescribed modules. You can find
installation instructions for I/O modules in the corresponding module Installation
and Operation Manual.
However, if you are installing a DXC-10A already equipped with modules, make
sure you disconnect all the cables from the enclosure before installing the
DXC-10A.
For your safety, make sure the DXC-10A grounding complies with the
requirements listed in Section 4.2.
Warning
Connecting the Power
Make sure the power switch on the DXC-10A enclosure is set to OFF, and then
connect the power cable first to the DXC-10A power connector, and then to a
grounded AC power outlet, or DC distribution box, providing the required supply
voltage.
When connecting the DC voltage, pay attention to correct polarity.
Turn-on
1. To turn the DXC-10A on, set its power switch to ON.
Turn-off
1. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-10A, turn it off.
2. To turn the DXC-10A off, set its power switch to OFF.
General Description
The DXC-8R enclosure consists of a power supply section, and a module section
with six slots.
• The power supply section includes either AC power supply modules or DC
power supply modules, which operate on -48 VDC.
The AC-powered version includes two pre-installed power supply modules
with a common panel.
The DC-powered version includes two separate, field replaceable DC
power supply modules.
• The module section includes two slots, designated CL-A and CL-B, for the
installation of two Common Logic modules, type DCL.3 (Section 4.6), and four
I/O module slots, designated I/O1 through I/O4. Each of these slots can be
fitted with a DT1B, DE1B, DT3, DE3, DIM, DHS, D8HS, D8E1, D8T1, D4E1,
D8T1, D8SL or D8U module. The DHL/E1 or DHL/E1/2W modules can be
installed in I/O slot 2 or 4. A DFSTM-1 module must always be installed in I/O
slot 1. The modules are inserted from the rear side.
Rear View
Figure 4-22 and Figure 4-23 show typical rear views of the DXC-8R enclosure, and
identify the slots and their use. The figures show DXC-8R enclosures with two DCL.3
modules, and DHS, DT1B, and DE1B modules:
• Figure 4-22 shows an AC-powered DXC-8R.
• Figure 4-23 shows the DXC-8R version with two separate, user-replaceable DC
power supply modules. Each module has its own DC power connector, and
therefore each module can be connected to a different power circuit. This
DXC-8R version requires the installation of circuit breakers for each module, to
provide protection and to serve as power on/off switches.
2
ON
2
DCL.3
ON
POWER
DE1
DT1
R
R
R
1
2
CL-A
I/O 1
I/O 3
ALM
TST MN
MJ
L
O
O
C
O
A
O
N
K
T
U
E
H
E
R
N
E
O
T
T
T
S
L
L
I
I
ON
2
1
2
ON
DCL.3
DHS
DE1
R
R
1
2
CL-B
I/O 1
I/O 2
ALM
MN
MJ
L
RS-530/V.35 RS-530/V.35
O
O
C
O
N
K
T
S
E
H
E
R
N
E
O
~100-240V 2.0A T 250V
T
U
N
N
I
T
O
O
S
S
L
L
I
I
Power Supply Grounding DCL B I/O Slot 2 I/O Slot 4
Unit Screw
ς∆Χ−
TST
ON
2
DCL.3
ON
DE1
ΙΝ
DT1
R
R
R
R
PS-A
CL-A
I/O 3
I/O 1
1
2
ALM
−
MN
L
MJ
0
O
O
C
O
N
C
T
U
L
R
N
T
O
O
T
L
E
T
E
T
S
L
L
I
2 I
48
ς∆Χ−
1
TST
ON
2
ON
DCL.3
DHS
ΙΝ
DE1
R
R
PS-B
I/O 4
CL-B
I/O 2
1
2
−
ALM
MN
MJ
0 RS-530/V.35 RS-530/V.35
O
O
C
O
S
K
T
R
N
E
O
N
U
T
O
T
T
I
48
L
L
I
Note the labels that designate the type of module that can be installed in each slot;
in addition, each slot is keyed, therefore it is not possible to install the wrong
module type.
Front Panel
Figure 4-24 shows the front panel of the DXC-8R enclosure. The front panel
includes labels for the show-through areas of the status indicators located on each
system module. Note that the indicators are arranged in groups (one group for
each system module) that are positioned before the corresponding module slot.
TEST
A A
MAJOR ALARM
MINOR ALARM
SYSTEM
B B
COMMON LOGIC POWER SUPPLY
Table 4-11 lists the functions of the indicators located on the DXC-8R front panel.
Indicator Function
TEST Indicates that a test (or test loop) is being performed on one of the local DXC-8R modules
MAJOR ALARM Indicates that a major fault has been detected in one of the DXC-8R modules
MINOR ALARM Indicates that a minor fault has been detected in one of the DXC-8R modules
COMMON Indicators for the DCL.3 modules, seen through the front panel. Their functions are as
LOGIC A and B follows:
• The indicator of a module lights steadily when the module is operating properly and is
active
• The indicator of a module is off when the corresponding module is defective, or is not
installed
• The indicator flashes when the module is operating properly, but is in standby (the
other module of the same type is active)
POWER SUPPLY Indicators for the internal power supply modules, seen through the front panel. Their
A and B functions are as follows:
• The indicator of a module lights steadily when the module is operating properly and is
active
• The indicator of a module is off when the corresponding module is defective, or is not
installed
The DXC-8R enclosure is intended for installation in 19" racks, however it can also
be installed on shelves and desktops, provided it can be connected to a suitable
nearby grounding point.
For rack installation, it is necessary to install two brackets to the sides of the unit.
The appropriate rack mount installation kit is supplied with the unit. As illustrated
in Figure 4-25, you may install the brackets in two ways, to orient the unit in
accordance with your requirements (either with the DXC-8R front panel toward
the front of the rack, or with the module panels toward the front).
Install Brackets Here if
You Want Access to Module Panels
From the Front of the Rack
DXC-8R is installed in 19" racks by fastening the side brackets of the DXC-8R
enclosure to the rack side rails, by means of four screws.
In general, the DXC-8R is installed in its designated location before it is equipped
with modules, and then it is equipped with the prescribed modules. If you are
installing a DXC-8R already equipped with modules, make sure you disconnect all
the cables from the enclosure before installing the DXC-8R.
Setting the jumper to NO may render the equipment unsafe for connection to
unprotected telecommunication networks in certain locations where
permanent excessive voltages are present on the line.
Warning
JP2
Frame Ground
Not Connected
JP2 to Ground
After checking that the internal jumpers are correctly set, install the power supply
modules as follows:
1. Insert the first module in slot PS-B.
2. Insert the additional power supply in slot PS-A.
If the enclosure is already operating, you can install a backup power supply module
Note in an operating enclosure without turning off the enclosure power. In this case, after
the module is installed, connect its power cable, and then set the external switch
controlling the connection of power to this module to ON.
For your safety, make sure the DXC-8R grounding complies with the
requirements listed in Section 4.2.
Warning
Turn-on
Turn-off
1. If an external feed voltage source, for example, a Ringer-2000, is connected to
one or more of the modules installed in the DCX-8R, turn it off.
2. To turn the DXC-8R off:
To turn a DXC-8R with internal (pre-installed) AC power supply modules
off, set its power switch to OFF.
To turn a DXC-8R with replaceable DC power supply modules off, set both
of the external circuit breakers or power switches protecting the two supply
lines to OFF.
5.1 Scope
This Chapter provides general information related to the management of DXC
systems by means of ASCII terminals. IP hosts using the Telnet protocol can also
manage the DXC system using the procedures described in this Chapter.
The instructions appearing in this Chapter assume that the supervision terminal
operator is familiar with the DXC system and its configuration parameters. If
necessary, review Appendix E for a description of the DXC operating environment,
Appendix F for a detailed description of the DXC supervision language, and refer to
Chapter 3 for a functional description of the DXC system.
Overview
Before a DXC system can be used in its intended application, it is necessary to
perform two types of activities:
• Preliminary configuration, which prepares the DXC system for using any of the
management facilities supported by the system.
• System configuration, used to specify the system operational parameters
needed by the DXC system to fulfill its intended function in the user’s
environment.
Preliminary Configuration
The preliminary configuration of the DXC system must always be performed using
an ASCII terminal equipped with an RS-232 communication interface, directly
connected to the DCL.3 supervisory port (the CONTROL connector).
The ASCII terminal can be a standard “dumb” communication terminal, or a
personal computer running a communication program that emulates an ASCII
terminal.
The preliminary configuration activities are covered by Section 5.4.
System Configuration
After performing the preliminary configuration, you can configure the DXC system
using any of the following options:
• Use the terminal as a supervision terminal, for performing all the management
activities supported by the DXC system.
Typically, the Telnet host is a PC or a UNIX station with the appropriate suite
of TCP/IP protocols. The host can be directly connected to the managed DXC
system unit using one of the DCL.3 communication ports (serial or Ethernet).
However, the host may also be located at a remote site, the only requirement
being that IP communication be established between that site and the
managed DXC system (either out-of-band, through a separate network, or
through inband channels).
• Configure the DXC system by means of SNMP-based network management
stations.
Routine Management
During regular operation, the DXC system can be managed using any of the
options listed above for system configuration.
Multidrop Connections
You may use a multidrop configuration to connect the supervisory ports of several
DXC system units to a common supervision terminal. For example, you can
connect the CONTROL ports of several DXC systems in a daisy-chain configuration
to a common supervision terminal.
Alternately, you can use multidrop modems or digital sharing devices to connect a
single terminal to many DXC system units.
For multidrop operation, each DXC system must be assigned a node address in the
range of 1 through 255.
DXC systems also support address 0: assigning address 0 to a DXC system means
Note
that it will accept and answer any message: this is not permitted in multidrop
operation. Address 0 is however recommended for use both with direct
connections, and point-to-point or dial-up modem links.
DCL.3 Redundancy
When two DCL.3 modules are installed in the DXC system, the transmit outputs of
the slave module in the serial port connectors are disconnected, to enable
simultaneous connection of both module ports by means of a Y-cable.
Therefore, when DCL.3 redundancy is used, the CONTROL connectors of the two
DCL.3 modules can be connected in parallel, since at any time only the port of the
main DCL.3 module is active.
Note For the DXC-8R, always connect supervision cables to both DCL.3 modules.
MNG ports are located only on DCL.3 module versions with RS-232 interfaces,
and have standard RS-232 asynchronous interfaces, which can be configured to
operate as DCE or DTE. For alarm reporting, always select the DTE interface.
Note When the MNG port is used for communication with a Telnet host or SNMP
management station, its interface must be configured as DCE.
The selection of the interface type (DCE or DTE) is made by means of internal
switches (see Chapter 4).
Note For the DXC-8R, always connect supervision cables to both DCL.3 modules.
The Telnet protocol operates over IP. Since the IP traffic is automatically routed to
the desired unit through the internal IP routers of chained equipment (see
Appendix C), the connection of a Telnet host to one DXC system unit may provide
management access to many interconnected DXC system units, as well as to many
other types of equipment that support this type of management (this includes
many RAD network products, e.g., Megaplex-2100/2100H/2200, Kilomux-2100,
FCD-E1, FCD-E1A, FCD-E1M, FCD-T1, FCD-T1M, etc.).
When connecting to the CONTROL port, make sure that the AUTOBAUD
function is disabled, otherwise communication using the SLIP or PPP protocol
is not possible.
• The connection to the MNG port is made as explained above in the
Connection of Alarm Monitoring Terminals section.
To enable using the appropriate protocol (SLIP or PPP) at the MNG port, make
sure to configure the MNG port interface as DCE (this is performed by internal
switches on the DCL.3 module).
DXC Preparations
See Chapter 4 for detailed information on internal settings, and for connection
instructions.
Note For DCL.3 modules with Ethernet interface, you can perform the same operation by
means of section 1 of the front-panel DIP switch.
TELNET_APATHY_TIME
10 MIN
IP_ADDRESS 999.999.999.999
DEFAULT GATEWAY 999.999.999.999
SUBNET MASK 999.999.999.999
SNMP READ COMMUNITY : = public
SNMP WRITE COMMUNITY : = private
SNMP TRAP COMMUNITY : = public
where X stands for the digits of the current IP and MAC addresses.
• After selecting the desired parameters, enter the UPDATE DB command.
No special configuration is required to use an Ethernet port for Telnet and SNMP
access.
After selecting the desired parameters, enter the UPDATE DB command.
At this stage, you can start using Telnet hosts or SNMP management stations to
perform DXC configuration in accordance with Chapter 6.
General
DXC operating mode, and all of its functions, are controlled by a set of
configuration parameters. These parameters can be determined by the user, in
accordance with the requirements of the specific applications.
The desired set of configuration parameters is prepared in accordance with a set of
rules, which together form the DXC supervision language. The supervision
language is used to communicate with the central control subsystem of the DXC
located in the DCL.3 module, using a supervision terminal physically connected to
the supervisory port (CONTROL) of the DCL.3 module. The same language can
also be used by Telnet hosts.
Power-up Process
Upon turn-on, the DXC central control subsystem checks the validity of the stored
configuration data, and if everything is OK, it loads the data into the working
memory and thus assumes the last configuration. Therefore, if the stored
configuration does not require modification, the DXC is ready for operation
immediately after power is applied. However, if the configuration data is not valid,
DXC lets you load instead a default configuration. The default configuration,
prepared by the manufacturer, is stored in the program EPROM.
After the operating parameters have been loaded (a process called configuration
setup), the DXC no longer requires operator attendance.
Command Protocol
• If AUTOBAUD is on, start any session by pressing the <Enter> key three
times in sequence. This will ensure identification of terminal data rate.
• When the DXC uses a non-zero node address, it expects an address before
responding to the terminal commands. No response will occur until the node
number is received and acknowledged by the addressed DXC.
Acknowledgment is indicated by the echoing of the node address part, i.e.
NODE<sp>nnn<sp>, where <sp> stands for space.
• The address is in the range of 1 through 255 (0 indicates that the selective
addressing function is disabled). The address is a prefix sent in the following
format: NODE<sp>nnn<sp>.
• When password protection is on, the addressed DXC waits for the password
before continuing. After the correct password is received, the DXC sends the
working prompt (DXC8R>, DXC10A, >DXC30> or DXC30E>, respectively).
If password protection is off, this step is omitted and the working prompt
appears after the node address conditions are fulfilled.
• After the working prompt is displayed, every character typed on the terminal
keyboard is immediately evaluated by the DXC and echoed to the terminal
screen. Full duplex communication with the terminal is therefore necessary, to
provide on-line feedback to the terminal operator.
• Command evaluation starts only when the <Enter> key is pressed.
• In case an error is detected during command evaluation, the command is not
executed. Instead, the DXC will send the erroneous command back to the
terminal, and you will see BAD COMMAND OR PARAMETER. TYPE “H” FOR
HELP in the next row. The correct command must then be sent again.
Command Options
Table 5-1 lists general types of options that are available with some commands.
See details in the command set index, Table 5-2.
Index of Commands
Table 5-2 lists the DXC commands in alphabetical order, and provides a concise
description of each command.
In this table, as well as in the whole manual, A stands for the module slot number
and B stands for the port number within the module. To specify an internal port,
add the prefix i before a port number. The slots used for DCL.3 modules are
identified as DCLA and DCLB.
• While the DCL.3 module performs the power-up self-test, the supervision
terminal displays:
• After the reading is completed, the state of the installed modules is displayed
in the following format:
PS-A OK
PS-B OK
CL-A OK
CL-B OK
I/O01 OK
I/O02 OK
I/O03 OK
I/O04 OK
I/O05 OK
I/O06 OK
I/O07 OK
I/O08 OK
I/O09 OK
I/O10 OK
I/O11 OK
I/O12 OK
I/O13 OK
I/O14 OK
I/O15 OK
3. By now, the DXC prompt should already be displayed on the terminal screen,
after the ON-LINE announcement.
If you see
PASSWORD>
this indicates that password protection is enabled. In this case, type the
password:
'password'<Enter>
where 'password' stands for the current password (four to eight characters). For
each password character typed by you, the terminal displays an asterisk *.
The default password is RAD.
If your password is accepted, you will see the working prompt: DXC8R>,
DXC10A>, DXC30>, or DXC30E>.
4. The DXC is now in session, under your control.
3. Type again the node address and then the password. For example, for node
address 234, type :
NODE<sp>234<sp>'password'<Enter>
If you do not know the password, try the default password (RAD). If the default is no
Note
accepted, refer to DXC Preparations in Section 5.4.
4. If the password is correct, the DXC will execute the command.
Otherwise, you will see again:
PASSWORD>
Control Session
1. During the control session, type the desired commands at the terminal
keyboard. You must see the DXC echo character by character.
If an incorrect character is entered, backspace to clear the error, and then type
again the correct character.
When you see the correct and complete command in the echo line, press
<Enter> to execute the command. The DXC will process the command
and display the appropriate response.
At the end of the command execution, the DXC displays the current time
and date, and then provides a new prompt for the next command line.
If you changed your mind, and want to abort the command, press BREAK
or CTRL+C. You will again receive the prompt, so you can enter another
command.
Note You can also use BREAK or CTRL+C to stop the automatic repetition of commands
sent with the /R option.
2. If your command is not correct, DXC will not execute it, but echo again the
command, with a bad command message in the following line. Type again the
correct command.
3. If the terminal screen fills up during the exchange with the DXC, the following
message appears:
HIT ANY KEY TO CONTINUE
When you pressing any key except BREAK, the terminal scrolls to the next
page.
6.1 Introduction
This Chapter provides configuration guidelines for DXC systems.
The configuration activities presented in this Chapter include examples that
assume that the configuration is made using a standard ASCII terminal, and show
the maximum number of module slots available on DXC systems (15).
However, after performing the preliminary configuration of the terminal and the
DXC in accordance with Chapter 5, the same configuration activities can also be
performed by means of a Telnet host, or an SNMP network management station.
For general information regarding the supervision language syntax, usage and
commands, refer to Chapter 5. Appendix F provides detailed descriptions of each
command and explains its use.
In addition, the occupied links can also be seen in the data form displayed by
means of the DSP ST SYS command: RESERVED in the H/W module type field
indicates that the links associated with the corresponding I/O slot are used by
another module.
Taking into consideration the capabilities and limitations of the automatic timeslot
allocation algorithm, whenever both Type 1 (for example, DE1B) and Type 2 (for
example, D8E1) modules are installed in a DXC chassis, it is recommended to
check the number of free timeslots available for further modules to be installed in
the chassis.
To do this, use the following formula:
D
TS = 960 – (64 × F) – ∑
1
TS occupied (n)
Where:
TS Number of timeslots available
F Total number of the Type 1 (“fixed”) modules configured in
the database (even if not yet installed in the chassis)
D Total number of Type 2 (“dynamic”) modules installed in the
chassis and configured to static or dynamic mode
TS occupied (n) Total number of timeslots occupied on the module n. The
calculation of this number depends on the timeslot allocation
mode selected for the chassis.
For dynamic mode:
TS occupied (n) is the smallest multiple of 32, exceeding the total number of
allocated timeslots on the module n (n=1, … ,D). For example, if 35 timeslots are
allocated on module n, TS occupied (n) is equal to 64.
For static mode:
TS occupied (n) is the smallest multiple of 32, exceeding the sum of the MAX TS
parameters assigned to the ports of module n (n=1, … ,D). For example, suppose
that the DSP TS UTILIZATION command displays the screen shown below:
Then we should first calculate the sum of MAX TS over the module ports, which is
5+10+8+10=33, and then “round it up” to the smallest multiple of 32, which is
64. In this case TS occupied (1)=64.
RAD recommends to use the DSP TS ALLOC command (see Appendix F) to have the
Note numbers of free timeslots automatically calculated by the DXC. This calculation,
however, does not take into account the TS 0’s available on each port.
Selecting Optimal I/O Slots for the Modules Installed in a DXC Chassis
Correct selection of module locations in a DXC chassis can help the matrix
maximize bandwidth utilization. The following guidelines should be used for
selecting the optimal I/O slots for modules to be installed in a new DXC chassis, as
well as when adding modules in an existing chassis:
• DXC-30 and DXC-30E: To maximize flexibility and bandwidth utilization, it is
recommended to install Type 1 I/O modules in the first I/O slots; Type 2 I/O
modules should be installed starting with the first free I/O slot after those
occupied by Type 1 modules. You may also want to leave additional empty
I/O slots for future expansion after the last I/O slot occupied by a Type 1
module.
If the DSP ST SYS command shows some I/O slots as reserved (RSVD), configure a
Note
new Type 2 module in the database in the first I/O slot marked as reserved, to
avoid possible data disruption.
• DXC-8R and DXC-10A: install Type 2 I/O modules in the last I/O slot of the
chassis. This ensures that the automatic timeslot allocation algorithm will not
attempt to allocate to the module bus links that may be used by Type 1
modules installed in the first slots.
When planning the configuration of a DXC chassis that is to include both Type 1
and Type 2 modules, you can use the DSP BUS command to display the current
utilization of the bus.
The result of entering the DSP BUS command for a DXC-30 chassis is shown below.
The display includes one row for each I/O slot. The row is divided into two
sections, one for each bus link associated with the corresponding I/O slot, for
example, for slot 3 one bus link is identified as 03:01 and the other bus link is
identified as 03:02. The interpretation of the information displayed in the example
given above is as follows:
• The status of the bus links 03:01 and 03:02 is FIXED: this indicates that a Type
1 module is either installed or configured in the database to occupy I/O slot 3.
The CAPTURED BY field indicates the module and port using these bus links:
for this slot, the bus links are used by the ports 1 and 2, respectively, of the
module installed in I/O slot 3.
• A Type 2 module (in this example, a D4E1 module) is installed in I/O slot 1:
the module occupies four bus links (01:01, 01:02, 02:01 and 02:02), each
port being assigned one link.
DCL Redundancy
If you enable DCL.3 redundancy, make sure to configure the flip parameters, using
the DEF DCL FLIP command.
When replacing a faulty DCL.3 module during DXC operation, data disruption
may occur. To avoid this, it is important to disable the DCL redundancy and then
enable it again, once the new module installed. To do this, use the following
procedure:
1. Run the DEF SYS command.
2. Set the REDUNDANCY parameter to NO.
3. Perform the UPD DB command.
4. Replace the faulty DCL.3 module in the DCL slot.
5. Run the DEF SYS command again and set REDUNDANCY to YES.
6. Perform the UPD DB command.
Matrix Mode
For DXC software version 5 and above, external E1 and T1 ports can be
configured to operate in the unidirectional mode. This feature is not relevant for
DIM modules, and for internal E1 or T1 ports such as those located on fractional
STM-1, E3 or T3 modules.
TS_ALLOC_MODE STATION_CLOCK_IF
STATIC G703
where A is the slot number in which the module is installed, and B is its port
number.
The complete set of parameters supported by each module port is explained in the
corresponding module Installation and Operation Manual, together with the
applicable configuration guidelines.
In general, the set of parameters includes two main sections:
• Configuration parameters, which determine the operating mode of the module
port, and when applicable – the handling of inband management traffic
• Routing parameters, which control the routing of the information processed by
the port. In most cases, the routing parameters control the routing of timeslots
between the port being configured and other destination ports.
Note You can also change the routing of any individual timeslot without opening the
module or port configuration data form: for this purpose, use the DEF TS command.
Note that for these types of ports, the data stream is not structured (it simply
consists of a stream of bits which are inserted in accordance with their order of
arrival into consecutive bit slots of the destination port).
Therefore, a high-speed data stream cannot be split into individual timeslots
for routing to several ports. The user can however select individual destination
timeslots in which the user's data is to be inserted, or can specify a “bundle” of
destination timeslots. DHS ports support two “bundle” routing modes:
The sequential “bundle” routing mode, described above.
The alternate “bundle” routing mode, which is available for connection to
T1 destinations: in this mode, the bundle timeslots are inserted in alternate
timeslots of the destination frame, starting with a specified timeslot.
To create a new connection for an individual timeslot, you start with the source
timeslot and select a new destination timeslot, as well as the timeslot type (. In the
bundle modes, a similar procedure is performed: first you specify the timeslot
bundle at the source port, and then specify the destination timeslots by indicating
the destination port and the starting timeslot.
To expedite the routing and minimize the effort needed to change timeslot
routing, the specification of a new connection automatically disconnects any
timeslot previously connected to the source timeslot, as well as any timeslots
previously connected to the new destination timeslot.
After completing the routing for a new port, you may still have to disconnect any
connections specified in the previous configuration that are no longer needed but
have not been replaced by new connections. For this purpose, use the DSP CON
command to check the current connections to the desired port.
The default value for the destination and type of timeslots is 1:1:1 and NC,
respectively. Because of the automatic disconnection feature, this default value
may sometimes lead to unexpected results, because the selection of the default
value is equivalent to specifying a destination slot (which is 1:1:1) and
simultaneously entering the instruction to disconnect the destination slot.
What this means it that you can inadvertently disconnect timeslot 1 of port 1 of
the module in I/O 1. These are the situations that may lead to this effect:
• When you try to disconnect a timeslot by selecting the default routing value
(1:1:1 and NC)
Note Even if you select MGMT (management) for the timeslot type, the effect is the same
as selecting NC.
• When you change the destination of a timeslot to the default (1:1:1)
• When you use the LOAD HW command to load default values for newly
installed modules (this results in specifying the default routing value for all the
timeslots of the new modules).
Since this error is quite common, it is recommended to note down the routes
connected to the default destination (1:1:1) before making any configuration
activities on an operating DXC chassis. After ending the configuration activities,
check and if necessary restore the original connections to timeslot 1:1:1.
Notes • The D4E1, D8E1, D4T1 and D8T1 modules support the hardware mode only.
• The second line of the data form for the DFSTM-1 module is different from other
DXC modules. For instructions, refer to the DFSTM-1 Installation and Operation
Manual.
4. Select the other parameters as explained for the line redundancy mode.
3. If you are using the AUTO mode, it is necessary to select the minimum
acceptable interval, in minutes, between consecutive decisions to flip between
the DCL.3 modules. The available selections are 1MIN, 2MIN, 3MIN, and
4MIN.
4. Under FLIP_ON_STATION_CLOCK, when AUTO is selected for the
ACTIVE_DCL parameters, select YES to flip to the other DCL.3 module
when the station clock signal connected to its interface is lost; select NO
otherwise.
5. Having selected the desired parameter values, press <Enter> to end.
General Parameters
The general system parameters include:
• Password: define using the DEF PWD command.
• System logical name: define using the DEF NAME command.
• Custom prompt: define using the DEF PROMPT command.
Management Parameters
For management purposes, you must also define the following parameters:
• To enable out-of-band management access, configure the CONTROL or MNG
port to support IP traffic using the DEF SP or DEF NP command, respectively.
• SNMP agent parameters: define using the DEF AGENT command.
• Management stations: define using the DEF MANAGER LIST command.
The second page is used to enter a new primary directory number, and the
second row displays the current primary directory number. The directory
number can include up to 20 digits, including the * and # symbols.
4. Enter the desired directory number and press <Enter>. If the
ALT_NUM_MODE parameter is YES, the third page of the call-out parameters
data form appears, used to enter a new alternate directory number.
Alarm Processing
DXC supports two alarm processing features, controlled by means of the DEF ALM
ATTRIB command: alarm inversion and alarm masking.
Alarm Inversion
This feature is used to change (invert) the interpretation of any desired alarm
condition occurring at a user-specified module or port with respect to DXC visual
indications and alarm relay:
• Normally, an alarm is interpreted as being active when the associated
condition is present (true).
• When the alarm is inverted, the normal condition is the presence of an alarm
condition, and the condition that requires alerting is the absence of the alarm
state.
For example, when a link is temporarily out of service, the alarm indication related
to loss-of-sync on the corresponding link can be inverted: the result is that the
ALARM indicator on the front panel of the DXC system and the corresponding
MAJ or MN ALM indicator on the DCL.3 panel is turned off as long as the
loss-of-sync condition is present, and will turn on when the link returns to normal
operation.
Alarm inversion does not affect the state of the alarm recorded in the alarm buffer
(the alarm buffer shows the true state). Moreover, when an alarm is inverted, it is
not masked.
Alarm Masking
Each specified alarm can be masked at the level of a module port, at the level of a
module, or at the level of the DXC system.
A masked alarm does not effect the DXC alarm status.
The masking of alarms is stored together with the other configuration parameters,
and therefore the masking is retained even if the DXC is reset or is turned off.
7.1 General
The DXC diagnostics functions include:
• Performance diagnostics - Section 7.2
• User-controlled loopback functions - Section 7.3
• Network-controlled loopback functions - Section 7.4
• BER Testing - Section 7.5.
The error detection information is derived from the data payload included in
each extended super-frame, by performing a cyclic redundancy check (CRC).
The resulting CRC checksum is transmitted in addition to the raw data bits.
The receiving end recalculates the checksum and compares the results with
the received checksum: any difference between the two checksums indicates
that one or more bit errors are contained in the current data block (ESF) being
evaluated.
• SF Framing: the SF-framed signal does not support the capabilities listed
above. However, the DXC is capable of gathering the number of out-of-service
(OOS) events caused by red alarms when operating with SF (D4) framing, and
the number of bipolar violations measured during the last minute and during
the worst minute.
The performance parameters defined for AT&T Pub. 54016 and in accordance
with RFC 1406 statistics are listed below:
Performance Parameters for the Current 15-Minute Interval
• Current ESF error events (ERROR EV)
An ESF error event is any extended super-frame containing a CRC error and/or
OOF event. The number of events is collected in a current ESF error events
register.
• Current seconds (SECS)
An errored second is any second containing one or more CRC error events, or
one or more OOF events, or one or more controlled slip events. The data is
collected for the current 15-minute interval.
• Current unavailable seconds (UAS)
A SES is a second with 320 or more CRC error events, or one or more OOF
events. The data is collected for the current 15-minute interval.
• Current bursty errored seconds (BES)
A BES is a second with 2 to 319 CRC error events. The data is collected for the
current 15-minute interval.
• Current loss of frame counter (LOFC)
The loss of frame (LOF) counter counts the loss of frame alignment events. The
data is collected for the current 15-minute interval.
A CSS is a second with one or more controlled slip events. The data is
collected for the current 15-minute interval.
Performance Parameters for Previous 15-Minute Intervals
The performance parameters for previous 15-minute intervals include the ES, UAS,
SES, LOFC, CSS, and BES for each previous interval with valid data.
Performance Parameters for Previous 24-Hour Interval
The performance parameters for the 24-hour interval include the ES, UAS, SES,
LOFC, CSS, and BES collected during the previous 24-hour interval, and the
number of degraded minutes (LAST 24 DEGRADE MIN).
In addition, the total number of 15-minute intervals in the previous 24-hour
interval, for which valid data is available, is also displayed (24 HOUR INTERVAL).
SF Statistics
The performance evaluation and monitoring parameters collected by the DXC for
SF framing are listed below:
• Bipolar violations count (BPV last minute)
The total number of bipolar violations counted in the last minute. This number
is updated every minute.
• Bipolar violations worst count
The number of bipolar violations counted in the worst minute since the last
resetting of the BPV count. This number is updated every minute.
CRC-4 Enabled
With the CRC-4 option enabled, the DXC provided performance data essentially
similar to that available on T1 ports with ESF framing.
The difference is that the error events count is no longer applicable, and instead
the following two parameters are provided:
• Current CRC-4 error events (ERROR CRC)
A CRC-4 error event is any multiframe containing a CRC error and/or OOF
event. The number of CRC events in the current second is collected in a
current CRC error events register.
• Current average CRC-4 errors (AVG ERR CRC)
The average number of CRC events per second. The average is updated every
second.
CRC-4 Disabled
With the CRC-4 option disabled, the DXC units provide performance data similar
to that available on T1 ports with SF framing, i.e., BPV last minute and BPV worst
minute data.
The number of line errored seconds (LES) is the number of seconds with one
or more coding violations (CVs), or with one or more LOS defects.
The line coding violations count includes bipolar violations (BPVs) and excess
zeros (EXZs) events:
For B3ZS or HDB3 signals, a BPV error event is the occurrence of a pulse of
the same polarity as the previous one which is not part of the zero
substitution code. For these codes, a BPV error event may also include
other error patterns such as three (four for HDB3) or more consecutive
zeros, and incorrect polarity-coded signals.
An EXZ error event is any zero string having a length of at least 3 zeros for
B3ZS, or 4 zeros for HDB3. An EXZ event increments the LCV count by 1,
irrespective of the zero string length.
• Current P-bit errored seconds (PES)
The number of P-bit errored seconds (PES) in the current 15-minute interval.
A PES is a second with one or more P-bit coding violations (PCVs), or one or
more OOF defects, or one or more incoming AIS defects (provided these
defects do not occur during an unavailable second).
A PCV is a P-bit parity error event, that is, the received P-bit code does not
match the corresponding locally-calculated code.
• Current P-bit severely errored seconds (PSES)
The number of P-bit severely errored seconds (PSES) in the current 15-minute
interval.
The number of C-bit errored seconds (CES) in the current 15-minute interval.
This data is relevant only for C-bit parity and DS3 SYNTRAN applications.
A CES is a second with one or more CCVs, or one or more OOF defects, or
one or more incoming AIS defects (provided these defects do not occur during
an unavailable second).
The CCV is the number of C-bit coding violations (CCV) in the current
15-minute interval. A CCV is an error event reported through the C-bits. For
C-bit parity applications, this is the count of CP-bit parity errors, and for DS3
SYNTRAN, it is the CRC-9 error count.
• Current C-bit severely errored seconds (CSES)
The number of C-bit severely errored seconds (CSES) in the current 15-minute
interval. This data is relevant only for C-bit parity and DS3 SYNTRAN
applications.
A CSES is a second with 44 or more CCVs, or one or more OOF defects, or
one or more incoming AIS defects (provided these defects do not occur during
an unavailable second).
• Current severely errored framing seconds (SEFS)
The number of seconds in the current interval (1 through 900) for which the
data is shown.
The number of CRC error events recorded in the current 15-minute interval.
• Current loss of sync word events counter (LOSW ERRORS COUNTER)
The number loss of sync word events in the current 15-minute interval.
• Current errored seconds (CURRENT ES)
The number of seconds with loss of sync word events in the current 15-minute
interval.
• Loop attenuation (LOOP ATTENUATION)
Indicates the current value of the receive path input circuits gain, in dB.
• Current transmit signal power (TRANSMIT POWER)
The number of seconds elapsed since the beginning of the current interval.
An errored second is any second containing one or more of the following types
of errors:
Severely Errored Frame (SEF) defect (also called Out-of-Frame (OOF)
event):
A SEF defect is declared after detection of four contiguous errored
frame alignment words.
The SEF defect is terminated when two contiguous error-free frame
words are detected.
Loss of Signal (LOS) defect:
A LOS defect is declared after when no transitions are detected in the
incoming line signal (before descrambling) during an interval of 2.3 to
100 microseconds.
The LOS defect is terminated after a 125-microsecond interval (one
frame) during which no LOS defect is detected.
A SES is a second during which multiple error events of the types taken into
consideration for an ES occur.
• Current unavailable seconds (UAS(SEFS))
An unavailable second is any second in which one or more SEF defects have
been detected.
Performance Parameters for Previous 15-Minute Intervals
The performance monitoring parameters for previous 15-minute intervals include
ES, CV, SES and UAS(SEFS) for each previous interval with valid data.
Performance Parameters for Previous 24-Hour Interval
The performance monitoring parameters for the 24-hour interval include the ES,
CV, SES and UAS(SEFS) collected during the previous 24-hour interval, and the
number of degraded minutes (LAST 24 DEGRADE MIN).
In addition, the total number of 15-minute intervals in the previous 24-hour
interval for which valid data is available, is also displayed (24 HOUR INTERVAL).
LOOP LOCAL
The local loopback fully checks the operation of the local DXC, and the
connections to the equipment that provides the signal (or the individual timeslots,
as applicable) reaching the tested port through the DCL.3 module. The local
loopback is activated on the selected port by the command LOOP L.
Figure 7-1 shows a typical local loopback.
DXC Unit
"1"
Digital E1 or T1
Port
Processing Port
Interface
Unit (DCL) Interface
The local loopback connects the port transmit signal to the input of the receive
path. The test signal is provided by the equipment whose signal (or timeslots) are
routed by the DCL.3 module to that port: this equipment must receive its own
transmission. During the loopback, the local DXC sends an unframed “all-ones”
signal to the link.
LOOP REMOTE
The remote loopback fully checks the data port, including the transmission path
connecting the remote user equipment to the DXC, and the corresponding port
interface of the DXC. The remote loopback is activated on the selected port by the
command LOOP R. Figure 7-2 shows a typical remote loopback.
DXC Unit
Digital E1 or T1
Port Port
Processing
Interface Interface
Unit (DCL)
The remote loopback returns the received signal toward the remote user
equipment connected to the same port. The loopback is performed by connecting
the port receive signal, after regeneration, to the input of the transmit path. The
test signal is provided by the user equipment connected to the remote end of the
link, that must receive its own transmission.
LOOP INBAND
The inband code-activated loopback tests the signal path between a DXC port and
any remote equipment unit that supports loopback in accordance with ANSI
T1E1.2/93-003, including the E1 or T1 interface of the remote equipment. The
inband code-activated loopback is activated on the selected port by the command
LOOP INBAND, but only on the timeslots defined by the user by means of the
DEF BERT command. Therefore, this loopback does not disrupt service to other
users connected through the selected port.
Figure 7-3 shows a typical remote loopback.
Digital Sequence
E1 or T1
Port Processing Generator
Interface
Interface Unit (DCL)
Sequence
Evaluator
LOOP TS REM
The remote timeslot loopback is similar to the remote loopback (see LOOP
REMOTE section above), except that the loopback is performed only within the
timeslots defined by the user by means of the DEF BERT command. The loopback
is activated and deactivated by the command LOOP TS REM.
The loopback returns the data received within the timeslots defined by the user
(by means of the DEF BERT command) toward the remote equipment. Figure 7-4
shows the signal paths relevant to the affected timeslots.
DXC Unit
Digital
Port E1 or T1
Processing
Interface Interface
Unit (DCL)
TX LLB
This test function, available only on T1 ports with ESF framing, causes the
transmission of the line loopback (LLB) activation sequence through the FDL. This
results in the activation of the line loopback (see Figure 7-34) on the equipment
connected to the remote end of the link.
The transmission of the loopback activation sequence is activated by the command
LOOP TX-LLB.
TX PLB
This test function, available only on T1 ports with ESF framing, causes the
transmission of the payload loopback (LLB) activation sequence through the FDL.
This results in the activation of the payload loopback (see Figure 7-35) on the
equipment connected to the remote end of the link.
The transmission of the loopback activation sequence is activated by the command
LOOP TX-PLB.
DHS Modules
The loopbacks available on DHS modules are described below. The same
loopbacks are available on each of the D8HS ports.
LOOP LOCAL
The local loopback checks the data port, including the transmission path
connecting the user equipment to the DXC, and the corresponding port interface
of the DXC. The local loopback is activated on the selected port by the command
LOOP L.
The local loopback returns the received signal toward the remote user equipment
connected to the same port. The local loopback is performed by connecting the
port receive signal, after processing by the interface circuits, to the input of the
transmit path. The test signal is provided by the user equipment connected to the
remote end of the link, which must receive its own transmission.
Figure 7-5 shows a typical local loopback.
DXC Unit
Digital
Port DHS Port
Processing
Interface Interface
Unit (DCL)
LOOP REMOTE
The remote loopback checks local DXC operation, and the connections to the
equipment connected to the other port. The remote loopback is activated on the
selected port by the command LOOP R.
The remote loopback connects the port transmit signal to the input of the port
receive path. The test signal is provided by the equipment whose signal (or
timeslots) are routed by the DCL.3 module to that port: this equipment must
receive its own transmission.
Figure 7-6 shows a typical remote loopback.
DXC Unit
Digital
Port DHS Port
Processing
Interface Interface
Unit (DCL)
DIM Modules
The loopbacks available on DIM modules are described below.
LOOP LOCAL
The local loopback checks the DIM user interface, and the connections between
the user’s equipment, and the DIM module. The local loopback is activated on the
selected port by the command LOOP L.
When activated on a DIM module, the local loopback returns the transmit signal
provided by the user’s equipment connected to the DIM module through the receive
path. The local loopback is performed by connecting the DIM port transmit signal,
after processing by the interface circuits, to the input of the receive path.
The test signal is provided by the user’s equipment connected to the DIM module,
that must receive its own transmission. Figure 7-7 shows a typical local loopback.
Digital Port 2
User
Interface
Processing
.. ..
Unit (DCL)
. .
.. .
.
Port 8
LOOP REMOTE
The remote loopback fully checks the operation of the local and remote DXC
systems, and the connections to the user’s equipment at the remote end. The
remote loopback is activated on the selected port by the command LOOP R.
When activated on a DIM module, the remote loopback connects the restored
module receive signal to the input of the transmit path. The test signal is provided
by the remote equipment whose signal is received by the DIM module: this
equipment must receive its own transmission.
Figure 7-8 shows a typical remote loopback.
DXC Unit
T1/E1 Ports
Serving DIM
Port 1
DIM
Digital Port 2
User
Processing
. .
Interface
Unit (DCL) . ..
.. .
. .
Port 8
LOOP INBAND
The inband code-activated loopback is activated by means of the command
LOOP INBAND A:1, and deactivated by means of the command
CLR LOOP INBAND A:1.
The inband code-activated loopback is initiated by disconnecting the local user’s
transmit signal, and transmitting a loopback activation sequence generated by the
local sequence generator (Figure 7-9).
After the sequence evaluator of the remote DIM module detects the activation
sequence, that module connects a remote loopback (Figure 7-10). To ensure that
the received sequence is indeed the loopback activation sequence, and not
caused by incidental reception of a similar sequence within normal payload data,
activate the loopback only after the activation sequence is continuously received
for a few seconds.
After the remote equipment connects the loopback, the sequence evaluator of the
local DIM module starts detecting its own activation sequence, and the
transmission of the loopback activation sequence stops. The loopback activation
process typically requires two to four seconds.
Figure 7-9. Inband Code-Activated Loopback on DIM – Signal Paths during Loopback Activation
Port 1 Port 1
DIM DIM
Figure 7-10. Inband Code-Activated Loopback on DIM – Signal Paths after Activation of Loopback
DHL Modules
In addition to the INBAND and TS REM loopbacks described for the E1/T1
modules, the DHL modules support additional loopbacks on the HDSL subsystem.
These loopbacks are described below.
LOOP L LINE
The local line loopback fully checks the operation of the local DXC (including the
operation of the local DHL module, except for the two HDSL line interfaces), and
the connections to the equipment that provides the signal (or the individual
timeslots, as applicable) reaching the tested port through the DCL.3 module. The
loopback is activated on the selected port by the command LOOP L LINE.
The local line loopback returns the signal received from the DCL.3 module, after
passing through the HDSL processing circuits of the DHL module. For the DHL/E1
module, the loopback is simultaneously performed on both HDSL lines.
The loopback returns the digital transmit signal, provided by the processing circuits
receive path, thereby replacing the signals received by the HDSL line interfaces.
The test signal is provided by the local user’s DTE, which must receive its own
transmission without errors while the loopback is activated.
Figure 7-11 shows a typical local HDSL loopback on a DHL/E1 module; the
DHL/E1/2W module has only one HDSL line interface, and therefore for this
module ignore the line B interface appearing in Figure 7-11.
DXC Unit
HDSL
DHL Line A
Module HDSL
Line A
Interface
Digital
Port HDSL
Processing
Interface Processing
Unit (DCL) HDSL
Line B
HDSL
Line B
Interface
LOOP L PORT
The local port loopback fully checks the operation of the local DXC, up to the local
DHL module (including only its E1 framer), and the connections to the equipment
that provides the signal (or the individual timeslots, as applicable) reaching the
tested port through the DCL.3 module. The loopback is activated on the selected
port by the command LOOP L PORT.
When activated, the local port loopback returns the signal received from the
DCL.3 module, after passing through the E1 framer of the DHL module.
The test signal is provided by the local user’s DTE, which must receive its own
transmission without errors while the loopback is activated.
Figure 7-12 shows a typical local port loopback on a DHL/E1 module. The
DHL/E1/2W has only one HDSL line interface, and therefore for this module
version ignore the line B interface appearing in Figure 7-12.
DXC Unit
HDSL
DHL Line A
Module HDSL
Line A
Interface
Digital
Port E1 HDSL
Processing
Interface Framer Processing
Unit (DCL) HDSL
Line B
HDSL
Line B
Interface
DHL DHL
Module HDSL HDSL Module
Line A Line A
Interface Interface
HDSL HDSL
Line B Line B
Interface Interface
Figure 7-13. HDSL_INBAND Loopback on Remote DXC Unit (Typical DHL Modules)
Figure 7-14 shows the typical signal paths when the loopback on a remote HDSL
modem for example, HCD-E1 is activated.
DHL DHL
Module HDSL HDSL
Module
Line A Line A
Interface Interface
Port Digital
HDSL HDSL Port
Interface Processing
Processing Processing Interface
Unit (DCL)
HDSL HDSL
Line B Line B
Interface Interface
In addition, D8U and D16U modules support the remote loopback on the remote
ASMi-31, which is activated through one of the module ports on an ASMi-31
connected to that port (available only when the port is configured for /1 operation).
The following sections describe the available loopbacks. The loopback signal paths
illustrated below include the DCL.3 module, which is actually involved only when
routing individual timeslots from other ports to the D8U or D16U ports.
Local Loopback
The local loopback, activated by the command LOOP L A:B, is used to test the
circuits associated with a given port (including the port interface and the operation
of the routing circuits that handle the port signals within the D8U/D16U module).
Figure 7-15 shows the signal paths of a typical local loopback (activated on external
port 1).
DXC Unit
Port 1
..
Digital .. ..
Other Port
Processing
Bus
Routing .. ..
Interface
Unit (DCL)
Interface . ..
.
Port 16
When the local loopback is activated, the D8U/D16U routing subsystem returns
the received data streams of the external port being tested (i.e., the B1, B2 and
when applicable - the D channel) back to the transmit path of the external port
interface. This loopback returns the signal received through the line toward its
source, after being regenerated and processed by the external port circuits and the
associated section of the routing subsystem.
Remote Loopback
The remote loopback, activated by the command LOOP R A:B, is used to test the
path of the signals intended for transmission through a selected D8U/D16U
external port, from the other DXC port to the D8U/D16U circuits serving the
desired external port.
Figure 7-16 shows the signal paths of a typical remote loopback (activated on
external port 1).
DXC Unit
Port 1
Digital ..
Other Port .. ..
Processing Routing .. ..
Interface Bus . ..
Unit (DCL) Interface .
Port 16
The remote loopback is performed within the bus interface of the module. This
loopback returns the digital data streams received from the DXC data bus and
directed to the port being tested, back toward the DXC data bus, through the
receive path of the bus interface.
ASMi-31
DXC Unit
Port 1
..
Digital .. .. Remote (NT)
Processing Bus .. .. Loopback
Unit (DCL) Interface
Routing . ..
.
Port 16
The loopback signal paths illustrated below include the DCL module, which is
involved when routing individual timeslots from other ports to the D8SL ports (see
Section 1.4).
The internal D8SL ports support three types of tests and loopbacks, which can be
independently activated for each port:
• Inband code-activated loopback (on all timeslots, or on specific timeslots)
• Remote timeslot loopback
• BER testing (see page 7-35).
Port 1
Digital .. ..
Other Port
Processing
Bus .. ..
Interface
Unit (DCL)
Interface . ..
..
Port 8
When the local loopback is activated on a selected port, the port interface returns
the port transmit signal to the input of the receive path, within the SHDSL modem
(see Section 1.4). The test signal is provided by the equipment whose data stream
(or timeslots) are routed by the DCL module to that port: this equipment must
receive its own transmission.
While the local loopback is activated, the local D8SL port sends an unframed
“all-ones” signal to the link.
DXC Unit
Port 1
Digital ..
Other Port
Processing
Bus ..
Interface
Unit (DCL)
Interface .
Port 8
The remote loopback is performed by connecting the port receive signal, after
regeneration by the SHDSL modem, to the transmit path of the SHDSL modem.
The test signal is provided by the user equipment connected to the remote end of
the link, that must receive its own transmission.
Remote Unit
DXC Unit
E1 Port
Port 1 Interface
Digital .. ..
Other Port
Processing
Bus .. ..
Interface
Unit (DCL)
Interface . ..
..
Port 8
.
Figure 7-21. Typical Inband Code-Activated Loopback Signal Paths
After the remote equipment connects the loopback, the test sequence evaluator of
the D8SL port starts detecting its own activation sequence, and the transmission of
the loopback activation sequence stops. The loopback activation process typically
requires two to four seconds. The loopback is deactivated by transmitting the
inband loopback deactivation sequence.
DXC Unit
Internal E1
Port 1
Port 1
Digital ..
Other Port
Processing
Bus ..
Interface
Unit (DCL)
Interface .
Port 8
E3 Interface Modules
This section describes the loopbacks supported on the E3 interface modules, DE3.
The loopback signal paths illustrated below include the DCL.3 module, which is
actually involved only when routing individual timeslots to the internal ports of the
DE3 modules.
Local E3 Loopback (LOOP L)
The local loopback fully checks the operation of the local DE3 module and of the
DXC signal paths that end at the internal ports, and the connections to the
equipment that provides the signal (or the individual timeslots, as applicable)
reaching the E3 port.
The local loopback is activated on the selected port by the command LOOP L.
The local E3 loopback connects the transmit signal of the module E3 port to the
input of the E3 receive path. The test signal is provided by the equipment whose
signals (or timeslots) are routed to the DE3 module: each equipment must receive
its own transmission.
During the loopback, the local E3 port sends an unframed “all-ones” signal to the
E3 link.
Figure 7-23 shows a typical local loopback.
DXC Unit
"1"
Port 1
Digital Port 2
Port .. E3 Port
Processing ..
Interface Interface
Unit (DCL) .
Port 16
DXC Unit
Port 1
Digital Port 2
Port .. E3 Port
Processing ..
Interface Interface
Unit (DCL) .
Port 16
DXC Unit
Digital Port 2
Port .. E3 Port
Processing ..
Interface Interface
Unit (DCL) .
Port 16
T3 Interface Modules
This section describes the loopbacks supported on the DT3 interface modules. The
loopback signal paths illustrated below include the DCL.3 module, which is
actually involved only when routing individual timeslots to the DT3 internal ports.
DXC Unit
"1"
Port 1
Digital Port 2
Port .. T3 Port
Processing ..
Interface Interface
Unit (DCL) .
Port 28
The remote T3 loopback returns the received signal toward the remote T3
equipment port.
Figure 7-27 shows a typical remote T3 loopback. The remote T3 loopback is
performed by connecting the DS3 receive signal, after regeneration, to the transmit
path. The test signal is provided by the equipment connected to the remote end of
the link, that must receive its own transmission.
DXC Unit
Port 1
Digital Port 2
Port .. T3 Port
Processing ..
Interface Interface
Unit (DCL) .
Port 28
DXC Unit
Port 1
Digital .. ..
Other Port .. ..
Processing Bus Routing ..
Interface . ..
Unit (DCL) Interface .
Port 16
• Internal VC-12 Port Loopbacks and Tests: user-activated local loopback, and
sending of simulated alarm indications.
The loopback signal paths illustrated below include the DCL module, which is
actually involved only when routing individual timeslots to the DFSTM-1 internal
E1 ports.
The test signal is provided by the equipment connected to the remote end of the
link, that must receive its own transmission.
While the loopback is activated, all the internal E1 ports receive an “all-ones”
signal.
This test fully checks the STM-1 path, including the transmission path connecting
the remote equipment to the DFSTM-1 module, and the STM-1 port interface of
the DFSTM-1 module.
Port 2
Digital ..
Port E1 SOH STM-1
Processing ..
Interface Mapper Processor LIU
Unit (DCL)
.
Port 30
Port 2
Digital ..
Port E1 SOH STM-1
Processing ..
Interface Mapper Processor LIU
Unit (DCL)
.
Port 30
The test signal is provided by the remote equipment whose signals (or timeslots)
are routed to the selected internal E1 port of the DFSTM-1 module: the remote
equipment must receive its own transmission.
While the loopback is activated, the receive data of the local E1 port remains
connected to the DXC bus.
This test fully checks the operation and the transmission path from the remote
equipment routed to this internal port, down to the internal E1 port output to the
local DXC bus, including most of the circuits of the local DFSTM-1 module.
DS AIS Test
The DS AIS test function, activated by means of the LOOP DS AIS command,
enables the user to test the response of the transmission path to the reception of
an AIS indication.
Network LLB
The latching network line loopback is connected upon the reception of the
appropriate code from the network. Typical loopback connections are shown in
Figure 7-34.
DXC Unit
Digital
Port T1 Port
Processing
Interface Interface
Unit (DCL)
FDL LLB
The FDL-activated line loopback is connected upon the reception of the appropriate
code through the FDL. The loopback connections are shown in Figure 7-23.
The activation code is the pattern 11111110 11111111, and the deactivation
code is 00111000 11111111.
Network PLB
The latching network payload loopback is connected upon the reception of the
appropriate code through the FDL. Typical loopback connections are shown in
Figure 7-35.
The loopback can only be connected when ESF framing is used. The connection is
performed by means of commands transmitted through the FDL port:
• The network payload loopback is activated when the DXC detects the pattern
00010100 11111111 on the FDL.
• The network payload loopback is disconnected by the reception of the pattern
00110010 11111111 (rightmost bit transmitted first).
DXC Unit
Digital
Port T1 Port
Processing
Interface Interface
Unit (DCL)
DXC Unit
DXC Unit
Port
Interface
Figure 7-37. BER Testing (DE1B, DT1B, DHL, D4E1, D8E1, D4T1, D8T1 Modules)
DIM Modules
Data transmission is checked by sending a user-selected pseudo-random sequence
generated by an internal test sequence generator. The transmitted data is returned
by a loopback somewhere along the data path to the sequence evaluator. The
evaluator compares the received data, bit by bit, to the original data and detects
any difference (bit error). The results are displayed on a supervision terminal. The
displayed information includes the accumulated time in test, the number of errors
accumulated from the activation of the BER test, the number of seconds in which
errors were detected, and the number of seconds with loss-of-sync errors. In
addition, the user can also see if error injection has been activated.
During the BER test, the tested port is disconnected from the user’s data
equipment (Figure 7-38).
DIM Port 1
Test Sequence
Evaluator Digital Port 2
Processing
Unit (DCL)
..
Test Sequence .
Generator ..
Port 8
In all these options DXC allows displaying the BER test results by means of the
command DSP BERT A:B REM. The test results are displayed as a number in the
range of 0 (no errors detected during the current measurement interval) through
63535. The number of errors is accumulated from the activation of the BER test.•
Figure 7-39 shows the signal paths during BER testing on the remote ASMi-31-2,
activated on external port 1. This is the first option from the list, which does not
require using external test equipment.
Port 1
..
Digital .. ..
Processing
Bus .. .. Routing
Unit (DCL.3)
Interface . ..
.
Port 16
Pattern Pattern
Generator Tester
D8SL Modules
The BER test, activated by the command LP BERT A:B, is used to evaluate data
transmission through selected timeslots of the link connected to a selected D8SL
internal port without using external test equipment.
The BER test setup is shown in Figure 7-40.
• Data transmission is checked by applying a test sequence generated by an
internal test sequence generator towards the remote equipment. The test
sequence, and the timeslots in which the sequence is transmitted, are defined
by means of the DEF BERT command.
• The transmitted data is returned by means of a loop, somewhere along the
data path, to the test sequence evaluator. The evaluator compares the
received data, bit by bit, to the original data and detects any difference (bit
error). The output of the evaluator is sampled during module polling, to check
whether errors were detected in the interval between consecutive pollings.
The test results are displayed on a supervision terminal as a number in the range of
0 (no errors detected during the current measurement interval) through 63535.
The number of errors is accumulated from the activation of the BER test. During
the BER test, the tested port is disconnected from the DCL module.
DXC Unit
Port 1
..
Digital .. ..
Other Port
Processing
Bus .. ..
Interface
Unit (DCL)
Interface . ..
.
Port 8
A.1 Scope
This Appendix provides information on the connectors installed on the common
system modules of the DXC-8R, DXC-10A, DXC-30, and DXC-30E.
For information regarding the connectors located on the I/O modules, refer to the
corresponding Installation and Operation Manuals.
CONTROL Connector
The CONTROL connector is a 9-pin female connector intended for direct
connection to a supervision terminal, wired in accordance with Table A-1:
• The connection of the CONTROL connector to a supervision terminal having a
9-pin connector is made by means of a straight cable (a cable wired
point-to-point).
9 Pin 25 Pin
Connector Connector
TD 3 2
RD 2 3
RTS 7 4
CTS 8 5
To DCL.3
CONTROL DSR 6 6 To Terminal
Connector DCD 1 8
RI 9 22
DTR 4 20
GND 5 7
9-Pin 9-Pin
Connector TD 3 2 Connector
RD 2 3
RTS 7 8
CTS 8 7
To DCL.3
CONTROL DSR 6 4 To Modem
Connector DCD 1 1
RI 9 9
DTR 4 6
GND 5 5
MNG Connector
The MNG connector is a 9-pin female connector. Connector pin functions are
listed in Table A-2.
• When the MNG port is configured for operation as a DTE interface, the port
can be directly connected to a dial-up modem:
The connection of the MNG connector to a dial-up modem having a 9-pin
connector is made by means of a straight cable.
The connection to a dial-up modem with 9-pin connector is made by
means of a crossed cable, wired in accordance with Figure A-2.
The connection to a dial-up modem with 25-pin connector is made by
means of a crossed cable, wired in accordance with Figure A-3.
• When the MNG port is configured for operation as a DCE interface, the port
can be directly connected to a terminal or to a serial PC port. Connector pin
functions, and cable wiring, are then in accordance with Table A-1 and
Figure A-1.
9 Pin
25 Pin
Connector
TD 3 2 Connector
RD 2 3
RTS 7 4
CTS 8 5
To DCL.3
MNG DSR 6 6 To Modem
Connector DCD 1 8
RI 9 22
DTR 4 20
GND 5 7
Caution The station clock connector of the DCL.3 module cannot be used with cables
prepared for DCL.2 modules.
Default
No. Message Description Corrective Actions Severity
and Type
01 REAL TIME The battery powering the DXC Have the DXC-10A or the DCL.3 Major
CLOCK BATTERY internal real-time clock while DXC module repaired (state)
FAILURE is not powered has failed
02 PS-A FAILURE The power supply A is missing, is Install, turn on, or replace the Major
not turned on or failed. corresponding power supply module (state)
04 PS-B FAILURE The power supply B is missing, is Install, turn on, or replace the Major
not turned on or failed. corresponding power supply module (state)
08 ALARM BUFFER More than 100 alarms entries have Read the messages, and then send Minor
OVERFLOW been written in the buffer since the the CLR ALM command from the (event)
last clear command supervision terminal
09 HARDWARE Technical failure in the module Replace the DXC I/O module Major
FAILURE IO-A installed in the specified slot installed in the specified slot (state)
10 MODULE WAS The module installed in the Check the reason for module removal Minor
REMOVED, IO-A specified slot has been removed (event)
11 DB-INIT SWITCH Section DB INIT of switch SW2 is If it is no longer necessary to enforce Minor
IS ON set to ON the default database parameter (event)
values, change setting to OFF
Default
No. Message Description Corrective Actions Severity
and Type
12 CLOCK WAS The main clock source of the DXC Check the port providing the master Minor
CHANGED TO failed, and the fallback clock source clock source: (event)
FALLBACK has been selected • For E1 and T1 ports, the DXC
replaces the recovered clock
when the corresponding port
loses frame synchronization or its
input signal is missing.
• For DHS ports, the clock is
replaced when the RTS line in
the port connector is OFF
13 CLOCK WAS Both the main and fallback clock Check the port providing the master Minor
CHANGED TO sources of the DXC failed, and the and fallback clock sources: (event)
INTERNAL internal clock source has been • For E1 and T1 ports, the DXC
selected replaces the recovered clock
when the corresponding port
loses frame synchronization or its
input signal is missing.
• For DHS ports, the clock is
replaced when the RTS line in
the port connector is OFF
14 CLOCK WAS The DXC switched back to the clock Normal state - no action required Minor
CHANGED TO source selected as the master source (event)
MASTER
15 CL FLIP HAS The other DCL.3 has been selected Check the reason for flipping using Major
OCCURRED as the on-line module the DSP FLIP command, and act (event)
accordingly
16 PROGRAMMED, The modules that have been read Either change the modules, or change Major
INSTALLED from the DXC do not match the the information appearing in the (state)
MODULE modules programmed in the database
MISMATCH, database
IO-A
17 CLA, CLB The software and/or hardware If the hardware versions differ, Minor
DIFFERENT revision of the DCL.3 module replace the DCL.3 module with the (event)
SOFT/HARD installed in slot CL-A differs from older version.
REVISION that of the DCL.3 module installed Check the software versions of the
in slot CL-B two DCL.3 modules: if the versions
differ, update the software version as
required. If the software and
hardware versions are identical,
perform self-test and replace the
defective DCL.3 module.
Default
No. Message Description Corrective Actions Severity
and Type
18 DP DIAL CYCLE The current cycle of call attempts Check the modem connected to the Major
FAILED failed NETWORK connector. (event)
If the called numbers are often busy,
you may also increase the number of
call retries.
19 DATABASE DXC technical failure (internal 1. Load the default configuration in Major
CHECKSUM ERR database error) the place of the current database (state)
(from the supervision terminal,
enter the INIT DB command).
2. Replace the DXC-10A, or replace
DCL.3 modules one by one.
20 PSWRD SWITCH Section PASSWORD of switch SW2 Set the switch to OFF. Minor
IS ON of the DCL.3 module is set to ON (event)
21 SP-PAR SWITCH Section TERM of switch SW2 of the If it is no longer necessary to enforce Minor
IS ON DCL.3 module is set to ON the default supervisory link (event)
parameters, change setting to OFF.
22 PC-SP SWITCH IS Section PC/SP of switch SW1 is set Set the switch to OFF. Minor
ON to ON (event)
23 LOSS OF The external station clock signal is 1. Check cable connections to the Minor
STATION CLOCK missing port connector. (state)
2. Check the equipment providing
the external clock signal.
3. Replace the DXC-10A or the
DCL.3 modules.
24 DP PRIMARY The call attempts to the primary If the number is not busy, check the Major
CALL FAILED dial-out number failed modem connected to the NETWORK (event)
connector.
If the called number is often busy,
you may also increase the number of
call retries.
25 DP ALTERNATE The call attempts to the alternate If the number is not busy, check the Major
CALL FAILED dial-out number failed modem connected to the NETWORK (event)
connector.
If the called number is often busy,
you may also increase the number of
call retries.
Default
No. Message Description Corrective Actions Severity
and Type
26 NETWORK LLB Line loopback command received Wait until the loopback condition is Minor
IO-A:B from the network (only for T1 ports) removed. (state)
27 NETWORK PLB Payload loopback command Wait until the loopback condition is Minor
IO-A:B received from the network (only for removed. (state)
T1 ports)
28 DRIVER FAILURE DXC technical failure (port 1. Check the transmit line pair. Major
IO-A:B line driver) 2. Replace the I/O module installed (state)
in the specified slot.
29 SIGNAL LOSS Loss of port receive signal. 1. Check cable connections to the Major
IO-A:B port connector. (state)
For the DFSTM-1 module, the loss
of signal (LOS) state is entered when 2. Check line and/or other
communication equipment
the received STM-1 signal level
providing the port to the remote
drops below the value at which an
DXC.
error ratio of 10-3 is predicted.
3. Replace the I/O module installed
The LOS state is exited when 2 in the specified slot of the remote
consecutive valid framing patterns DXC.
are received, provided that during
this time no new LOS condition has
been detected
30 EXCESSIVE BPV The rate of bipolar violations in the Problem in network facilities Major
IO-A:B port receive signal exceeds 1×10-6 (state)
during a measurement interval of
1000 seconds
31 AIS OCCURRED Unframed “all ones” sequence is Problem at the remote equipment Major
IO-A:B received in the specified port data connected to the specified port (state)
stream
32 AIS RED ALM Local loss of frame synchronization Problem at the remote equipment Major
IO-A:B alarm on the specified port caused connected to the specified port (state)
by AIS condition (only on T1 ports)
Default
No. Message Description Corrective Actions Severity
and Type
33 AIS SYNC LOSS Local loss of frame synchronization Problem at the remote equipment Major
IO-A:B alarm on the specified port caused connected to the specified port (state)
by AIS condition (only on E1 ports)
34 RED ALARM Local loss of frame synchronization 1. Check cable connections to the Major
IO-A:B alarm on the specified port (only on port connector. (state)
T1 ports) 2. Check line and/or other
communication equipment
providing the port to the remote
DXC.
3. Replace the I/O module installed
in the specified slot.
4. Replace the DCL.3 modules.
35 LOCAL SYNC Local loss of frame synchronization 1. Check cable connections to the Major
LOSS IO-A:B alarm on the specified port (only on port connector. (state)
E1 ports) 2. Check line and/or other
communication equipment
providing the link to the remote
DXC.
3. Replace the DXC-10A or the
DCL.3 modules.
36 LOCAL MF Local loss of multiframe 1. Check cable connections to the Major
ALARM IO-A:B synchronization alarm on the port connector. (state)
specified port (only on E1 ports 2. Check line and/or other
operating with G732S framing) communication equipment
providing the link to the remote
DXC.
3. Replace the DXC I/O module
installed in the specified slot.
4. Replace the DXC-10A or the
DCL.3 modules.
37 REMOTE MF Remote loss of multiframe Problem at the remote equipment Major
ALARM IO-A:B synchronization alarm on the (state)
specified port (only on E1 ports with
G732S framing)
38 YELLOW ALARM Remote loss of frame Problem at the remote equipment Major
IO-A:B synchronization alarm on the (state)
specified port (only on T1 ports)
Default
No. Message Description Corrective Actions Severity
and Type
39 REMOTE SYNC Remote loss of frame Problem at the remote equipment
LOSS IO-A:B synchronization alarm on the
specified port (only on E1 ports)
40 FRAME SLIP Frame slips are detected (not 1. Incorrect selection of clock Minor
IO-A:B displayed during local loss of frame source. (event)
synchronization). 2. Problem at far end (unstable
Updated once per second clock source).
3. Replace the DXC-10A or the
DCL.3 modules only if no
problem has been detected in
steps 1 and 2.
41 BPV ERROR Bipolar violations in the port receive Have the equipment connected to Minor
IO-A:B signal. Updated once per second the specified port, and the connecting (event)
link, checked. If the remote
equipment and the link is OK, the
port may be defective
42 EXCESSIVE ERR The bit error rate of the port receive Problem in network facilities. Major
RATIO IO-A:B signal exceeds 1×10-3 (state)
43 CRC-4 ERROR CRC-4 errors detected in the E1 Have the equipment connected to Minor
IO-A:B port receive signal. Updated once the specified port, and the connecting (event)
per second link, checked. If the remote
equipment and the link is OK, the
port may be defective.
44 B.R.G FAILURE, Hardware failure of the bit rate Replace the specified module. Major
IO-A:B generator of port A:B (state)
45 SFIFO SLIP A slip event occurred in the SFIFO Check the selection of the clock
IO-A:B of port A:B source, and the cable connections.
46 MANAGEMENT A test loopback has been activated Check the location of the loop and Major
PORT IS on the management port, or the request disconnection. (state)
LOOPED management port receives its own
messages. Management is not
possible while this condition is
present
47 MANAGEMENT The DCL.3 module cannot 1. Correct the parameters. Major
PORT IS DOWN communicate with the network (state)
2. Check for disconnection.
management station. This may
indicate incorrect set-up of the 3. Check for hardware failure.
management port communication
parameters, a disconnection along
the communication path, or a
hardware failure
Default
No. Message Description Corrective Actions Severity
and Type
48 DUPLICATE Another RAD IP entity in the Check and correct the name Minor
NAME IN THE network uses the logical name (state)
NETWORK assigned to the DXC
49 DUPLICATE MAC Another entity in the network used Check and correct the MAC address Major
ADDRESS IN THE for SNMP management uses the (state)
NETWORK MAC address configured on the
SNMP agent of the DXC
50 MANAGEMENT The module software version is not Check with your distributor or with Major
NOT supported by the management RAD Technical Support department (state)
SUPPORTED IN software
SOFT REV, IO-A
51 DB CONTROL The DXC database is being edited Informative message - no action Minor
WAS TAKEN BY from an ASCII terminal, while it is required (event)
SNMP MMI also being edited by an
SNMP-based network management
station.
It is user's responsibility to prevent
possible conflicts by stopping the
editing from either the terminal or
the management station
52 DB CONTROL The DXC database is being edited Informative message - no action Minor
WAS TAKEN BY by an SNMP-based network required (event)
TERM MMI management station, e.g.,
RADView, while it is also being
edited using an ASCII terminal.
It is user's responsibility to prevent
possible conflicts by stopping the
editing from either the terminal or
the management station
54 LOOP INBAND A test loopback, controlled by If the loopback is no longer required, Minor
ON IO-A:B inband activation codes, is activated use the CLR LOOP command to (state)
on the specified module port deactivate it
55 CRC Local loss of synchronization to the 1. Check cable connections to the Major
MULTIFRAME CRC-4 multiframe on the specified port connector. (state)
ALIGNMENT port (only on E1 ports operating
2. Check line and/or other
LOSS IO-A:B with CRC-4 enabled)
communication equipment
providing the link to the remote
DXC.
3. Replace the DXC I/O module
installed in the specified slot.
4. Replace the DXC-10A or the
DCL.3 modules.
Default
No. Message Description Corrective Actions Severity
and Type
59 DIM LINK 1 Errors have been detected in the 1. Check for identical configuration Major
ERROR data stream received by the DIM of links on the DIM modules at (state)
60 DIM LINK 2 module through the link connected the two DXC systems: link 1 at
ERROR to the specified E1 or T1 port. one end must be configured to
61 DIM LINK 3 connect to link 1 at the other
This message can appear only for
ERROR end, etc.
DIM modules
62 DIM LINK 4
2. Check for correct physical
ERROR
connections.
63 DIM LINK 5
ERROR 3. Check that good transmission
64 DIM LINK 6 quality on the various links.
ERROR
65 DIM LINK 7
ERROR
66 DIM LINK 8
ERROR
67 LAN NOT The 10BaseT port of a DIM module 1. Check the connection between Minor
CONNECTED is not connected to an active the DIM 10BaseT port and the (state)
Ethernet LAN LAN media, or hub port.
2. Check that the LAN equipment is
operating normally, and at least
one station is active on the LAN.
68 I/O FLIP HAS The active module of a redundancy Informative message. Check reason Minor
OCCURRED pair operating in the Y-cable and act accordingly. (event)
redundancy or combined line and
hardware redundancy mode has
been changed
69 I/O The software version installed on Contact RAD Technical Support Major
REDUNDANCY the specified I/O module does not Department for upgrade information. (event)
NOT support redundancy
SUPPORTED IN
SW REV:IO-A
70 PORT FLIP HAS The active port of a module Information message. Check the Major
OCCURRED operating in the single-slot reason and act accordingly. (event)
redundancy mode has been
changed
71 HDSL TIMING The specified DHL module cannot 1. Check the equipment providing Major
OVERFLOW recover the line clock because its the E1 signal, and make sure its (event)
IO-A:B frequency is not within the clock source is stable.
supported range 2. Replace the DHL module only if
no problem has been detected in
step 1.
Default
No. Message Description Corrective Actions Severity
and Type
72 HDSL STUFFING The stuffing mechanism of the DHL 1. Incorrect selection of clock Major
OVERFLOW module cannot compensate for the source. (event)
IO-A:B frequency difference between the 2. Problem at equipment providing
user’s port clock (E1 or T1) and the the E1 signal (unstable clock
HDSL clock source).
3. Replace the DHL module only if
no problem has been detected in
steps 1 and 2.
73 HDSL ELASTIC The elastic buffer of the specified 1. Check the clock sources selected Major
BUFFER DHL module has overflown in the system, and make sure that (event)
OVERFLOW they are derived from the same
IO-A:B source.
2. Replace the DHL module.
74 HDSL LOOPS The specified DHL module Check and correct the connections Minor
ARE INVERTED detected incorrect HDSL (state)
IO-A:B line connections
75 HDSL FAR END The specified DHL module reports 1. Incorrect selection of clock Minor
ALARM IO-A:B that an alarm condition is reported source. (event)
by the remote module 2. Problem at equipment providing
the E1 signal (unstable clock
source).
3. Replace the DHL module only if
no problem has been detected in
steps 1 and 2.
76 HDSL REMOTE The specified DHL module reports Informative message - no action Major
LOOP IO-A:B that a remote loopback has been required. Deactivate the loopback (state)
activated when no longer required.
77 HDSL LINE 1 The specified DHL module reports 1. Check HDSL line 1 connections. Major
ELASTIC BUFFER that the elastic buffer serving HDSL 2. Check the operation of the local (event)
ERROR IO-A:B line 1 is not supplying data and remote DHL modules, and
replace if necessary.
78 HDSL LINE 2 Same as above for HDSL line 2
ELASTIC BUFFER
ERROR IO-A:B
79 HDSL LINE 1 FAR The specified DHL module reports If the number of CRC-6 errors is Major
END CRC ERROR that a CRC-6 error has been significant (more than a few errors (event)
IO-A:B detected in the line 1 HDSL input per hour), perform the following:
signal at the remote end of the line 1. Check the HDSL lines to the
remote DHL module.
2. Perform self-test on the two DHL
modules and replace the DHL
module that fails the self-test.
Default
No. Message Description Corrective Actions Severity
and Type
80 HDSL LINE 2 FAR Same as above for HDSL line 2
END CRC ERROR
IO-A:B
81 HDSL LINE 1 The specified DHL module reports If the number of CRC-6 errors is Major
CRC ERROR that a CRC-6 error has been significant (more than a few errors (event)
IO-A:B detected in the input signal of per hour), perform the following:
HDSL line 1 1. Check the HDSL lines to the
remote DHL module.
2. Perform self-test on the two
DHL modules, and replace the
module that fails the self-test.
82 HDSL LINE 2 Same as above for HDSL line 2
CRC ERROR
IO-A:B
83 HDSL LINE 1 The specified DHL module reports 1. Check the corresponding HDSL Major
SYNC LOSS loss of synchronization on HDSL line. (state)
IO-A:B line 1
2. Perform self-test on the two DHL
modules and replace the DHL
module that fails the self-test.
84 HDSL LINE 2 Same as above for HDSL line 2
SYNC LOSS
IO-A:B
85 HDSL LINE 1 The specified DHL module reports 1. Check the corresponding HDSL Major
SIGNAL LOSS loss of HDSL line 1 input signal line. (state)
IO-A:B
2. Perform self-test on the two DHL
modules and replace the DHL
module that fails the self-test.
86 HDSL LINE 2 Same as above for HDSL line 2
SIGNAL LOSS
IO-A:B
87 BUS CAPACITY The number of open timeslots Decrease the number of open Major
EXCEEDS exceeds the number of available timeslots (state)
links in the system
88 PS-A FAN
FAILURE The internal cooling fan of the Check that the fan is indeed not Major
corresponding power supply operating. (state)
89 PS-B FAN
module does not operate If not, replace the corresponding
FAILURE
power supply module.
90 IDSL LB1 A loopback has been activated on If the loopback is no longer required, Minor
the B1 channel of the specified use the CLR LOOP command to (state)
D8U/D16U module port deactivate it.
Default
No. Message Description Corrective Actions Severity
and Type
91 IDSL LB2 A loopback has been activated on If the loopback is no longer required, Minor
the B2 channel of the specified use the CLR LOOP command to (state)
D8U/D16U module port deactivate it.
92 IDSL LBBD A loopback has been activated on If the loopback is no longer required, Minor
the B1, B2 and D channels of the use the CLR LOOP command to (state)
specified D8U/D16U module port deactivate it.
93 EXT UNIT The required configuration could Change the ASMI-31 operation mode Minor
CONFIG not be downloaded to the ASMi-31 to permit configuration downloading. (state)
MISMATCH unit connected to the specified port
of the D8U/D16U module
94 EXT UNIT The ASMi-31 unit connected to the Replace the ASMi-31. Major
NVRAM FAILED specified port of the D8U/D16U (state)
module report failure of its
non-volatile memory
95 EXTERNAL UNIT No user interface is installed on the Install the required interface card in Major
NO INTERFACE ASMI-31 unit connected to the the ASMi-31, or replace the ASMi-31. (state)
specified port of the D8U/D16U
module
96 DTE INITIATED A loopback (local or remote) has Deactivate the corresponding Major
TEST ON EXT been activated on the remote unit loopback. (state)
UNIT managed by DHL/E1, DHL/E1/2W
or D8U/D16U module
97 EXT UNIT RTS RTS signal on the remote modem Connect the remote DTE equipment Minor
OFF channel is in the OFF state to the remote modem. (state)
101 STM LOSS OF The loss of pointer (LOP) state is Problem on the STM-1 link, or at the Major
POINTER entered when N consecutive invalid remote equipment unit. (state)
pointers are received by the
specified VC-4 or VC-12 port
(N = 8, 9 or 10).
LOP state is exited when 3 equal
valid pointers or 3 consecutive AIS
indications are received.
Default
No. Message Description Corrective Actions Severity
and Type
102 STM LOSS OF The loss of frame (LOF) state is Problem on the STM-1 link, or at the Major
FRAME entered when an out-of-frame remote equipment unit. (state)
(OOF) state exists at the specified
STM-1 port for up to 3 ms. If OOFs
are intermittent, the timer is not
reset to zero until an in-frame state
persists continuously for 0.25 ms.
The LOF state is exited when an
in-frame state exists continuously for
1 to 3 ms
103 STM OUT OF The specified STM-1 port lost frame Problem on the STM-1 link, or at the Major
FRAME synchronization remote equipment unit. (state)
104 STM SIGNAL The DFSTM-1 module reports that it Problem on the STM-1 link, or at the Major
LABEL LOSS OF cannot detect the signal label remote equipment unit. (state)
LOCK
105 STM SIGNAL The specified VC-4 or VC-12 port 1. Check routing of corresponding Major
LABEL detects a signal label mismatch. This signal (state)
MISMATCH may indicate incorrect routing.of
2. Problem on the STM-1 link, or at
the corresponding VC.
the remote equipment unit.
This alarm condition may occur
while a new route is being prepared
106 STM SIGNAL The specified VC-4 or VC-12 port 1. Check routing of the Major
LABEL receives an unequipped signal label corresponding signal (state)
UNEQUIPPED
2. Problem on the STM-1 link, or at
the remote equipment unit.
107 STM SIGNAL The specified port reports BER 1. Problem on the STM-1 link, or at Major
DEGRADED exceeding the preset signal the remote equipment unit. (state)
ERROR degradation threshold
2. If the problem persists, replace
the module
108 STM PATH The specified VC-4 or VC-12 port 1. Check routing of the VC-4 signal Major
TRACE ID detects a path trace mismatch. This (state)
2. Problem on the STM-1 link, or at
MISMATCH may indicate incorrect routing.of
the remote equipment unit.
the corresponding VC.
This alarm condition may occur
while a new route is being prepared
109 STM PATH The DFSTM-1 module reports that it 1. Check routing of the VC-4 signal Major
TRACE receives unequipped path trace (state)
2. Problem on the STM-1 link, or at
UNEQUIPPED
the remote equipment unit.
Default
No. Message Description Corrective Actions Severity
and Type
110 STM HW FAIL The DFSTM-1 module reports Replace the DFSTM-1 module Major
technical failure (state)
111 STM CRITICAL The corresponding internal port 1. Reset the DFSTM-1 module. Major
ALARM reports that a critical alarm condition (state)
2. Replace the DFSTM-1 module
has occurred on an upper layer
112 INPUT ALARM IS The fan tray unit failed. Replace the fan tray. Major
ACTIVE (state)
113 SNMP ALARM The number of SNMP alarm traps is Once all the queued alarm traps are Major
TRAP EXCEEDS too high for the proper device sent, the alarm disappears. (state)
operation; new alarm traps will not be
queued.
114 SHDSL SYNC Loss of SHDSL synchronization on the Connect the SHDSL line to the Major
LOSS LINE_A specified SHDSL line D8SL port. (state)
115 SHDSL LOSW Loss of SHDSL synchronization word Check the SHDSL line. Major
FAILURE LINE-A event on the specified SHDSL line (state)
116 SHDSL CRC6 CRC error event on the specified Check the SHDSL line. Major
ERROR SHDSL line (state)
117 SHDSL SNR SNR margin event on the specified Set higher value of SNR_MARGIN Major
MARGIN ERROR SHDSL line _THRESHOLD parameter, or (state)
improve the line quality.
118 SHDSL LOOP High attenuation on the SHDSL line Set higher value of Major
ATTENUATION ATTENUATION_THRESHOLD (state)
ERROR parameter
119 SHDSL NO The SHDSL inband management Connect the SHDSL line to the Major
MANAGEMENT channel (eoc) is not operational D8SL port. (state)
120 SHDSL TEST A test has been activated on the Deactivate the test from the remote Minor
ACTIVE BY specified SHDSL line by the remote unit or wait until it is ended. (state)
REMOTE UNIT unit
121 REM LOSS OF The remote ASMi-52/E1 unit Check the remote unit. Minor
SIGNAL connected to the specified SHDSL port (state)
reports loss of signal
122 REM BPV ERROR The remote ASMi-52/E1 unit Check the remote unit. Minor
connected to the specified SHDSL port (event)
reports bipolar violation error
123 REM FRAME SLIP The remote ASMi-52/E1 unit Check the remote unit. Minor
connected to the specified SHDSL port (event)
reports frame slip
Default
No. Message Description Corrective Actions Severity
and Type
124 REM EXCESSIVE The remote ASMi-52/E1 unit Check the remote unit. Minor
BPV connected to the specified SHDSL port (state)
reports high rate of bipolar violation
errors
125 REM EXCESSIVE The remote ASMi-52/E1 unit Check the remote unit. Minor
ERROR connected to the specified SHDSL port (state)
reports excessive bit error rate (higher
than 10-3
126 REM AIS The remote ASMi-52/E1 unit Check the remote unit. Minor
OCCURED connected to the specified SHDSL port (state)
reports reception of AIS
127 REM CRC4 The remote ASMi-52/E1 unit Check the remote unit. Minor
ERROR connected to the specified SHDSL port (event)
reports CRC-4 error event
128 REM AIS SYNC The remote ASMi-52/E1 unit Check the remote unit. Minor
LOSS connected to the specified SHDSL port (state)
reports AIS and loss of frame alignment
129 REM REMOTE The remote ASMi-52/E1 unit Check the remote unit. Minor
SYNC LOSS connected to the specified SHDSL port (state)
reports loss of frame alignment to the
user’s E1 signal
130 REM LOSW The remote ASMi-52 unit connected Check the SHDSL line. Minor
FAILURE LINE-A to the specified SHDSL port reports (state)
loss of SHDSL synchronization
131 REM SHDSL The remote ASMi-52 unit connected Check the SHDSL line. Minor
CRC6 ERROR to the specified SHDSL port reports a (event)
SHDSL CRC error event
132 REM SHDSL SNR The remote ASMi-52 unit connected Set higher value of REM_ SNR_ Minor
MARGIN ERROR to the specified SHDSL port reports MARGIN_THRESHOLD parameter, (event)
low SHDSL SNR margin event. or improve the line quality.
133 REM SHDSL The remote ASMi-52 unit connected Set higher value of Minor
LOOP to the specified SHDSL port reports REM_ATTENUATION_THRESHOLD (state)
ATTENUATION high SHDSL line attenuation parameter
ERROR
134 REM LLB FROM The remote ASMi-52 unit connected Deactivate the LLB test on the Minor
DTE to the specified SHDSL port reports remote unit. (state)
the reception of a local loopback
request from the user’s equipment
Default
No. Message Description Corrective Actions Severity
and Type
135 REM RLB FROM The remote ASMi-52 unit connected Deactivate the RLB test on the Minor
DTE to the specified SHDSL port reports remote unit. (state)
the reception of a remote loopback
request from the user’s equipment
136 REM LAN NOT The remote ASMi-52 unit connected Connect the LAN to the Ethernet Minor
CONNECTED to the specified SHDSL port reports port of the remote unit. (state)
that no LAN is connected to its
Ethernet port
137 REM DATA LINE The remote ASMi-52 unit connected Set the MAX_BW parameter to Minor
RATE MISMATCH to the specified SHDSL port reports match the number of open (state)
that its data rate does not match the timeslots.
number of timeslots open on the D8SL
port to which it is connected
138 REM CONFIG The remote ASMi-52 unit connected The ASMi-52 parameters should not Minor
CHANGED to the specified SHDSL port reports be modified by the modem (event)
change of configuration supervision terminal.
139 REM ILLEGAL The remote ASMi-52 unit connected Set the ASMi-52 nodal clock to the Minor
EXT CLOCK to the specified SHDSL port reports correct value. (state)
incorrect selection of its nodal clock
source
140 CLOCK IS The DFSTM-1 module switched to the 1. Set the clock to internal. Minor
INTERNAL internal clock because of one of the (state)
2. Check the remote unit.
following conditions:
3. Check the STM-1 link.
1. The DXC operates with LBT
(loopback) timing, and a local
STM-1 port loopback is activated.
2. The DXC operates in the terminal
mode with LBT (loopback) timing,
the S1 mechanism is ON, and the
far end reports a fault that
degrades clock quality
3. When operating in the linear mode
with protection – switching to the
internal clock because of signal
disconnection
141 PROPRIETARY The SHDSL inband proprietary Connect the SHDSL line to the Major
PROTOCOL protocol management channel (eoc) is D8SL port. (state)
FAILED not operational
C.1 Scope
This Appendix provides specific information required for the management of DXC
systems by means of the Simple Network Management Protocol (SNMP). Some of
this information is also applicable for management by means of the Telnet
application.
General
The SNMP management functions of the DXC are provided by an internal SNMP
agent, which can use inband and out-of-band communication.
The SNMP management communication uses the User Datagram Protocol (UDP),
which is a connectionless-mode transport protocol, part of the suite of protocols of
the Internet Protocol (IP).
Note Telnet management uses the TCP protocol over IP for management communication.
After a Telnet session is started, the management interface is similar to that used for
the supervision terminal (Chapter 4).
This section covers the information related to the SNMP environment. For a
description of the IP environment, refer to Section C.3.
SNMP Principles
The SNMP management protocol is an asynchronous command/response polling
protocol: all the management traffic is initiated by the SNMP-based network
management station, which addresses the managed entities in its management
domain. Only the addressed managed entity answers the polling of the
management station (except for trap messages).
The managed entities include a function called an “SNMP agent”, which is
responsible for interpretation and handling of the management station requests to
the managed entity, and the generation of properly-formatted responses to the
management station.
SNMP Operations
The SNMP protocol includes four types of operations:
getRequest Command for retrieving specific management information from the
managed entity. The managed entity responds with a getResponse
message.
getNextRequest Command for retrieving sequentially specific management information
from the managed entity. The managed entity responds with a
getResponse message.
setRequest Command for manipulating specific management information within the
managed entity. The managed entity responds with a setResponse
message.
trap Management message carrying unsolicited information on extraordinary
events (e.g., alarms) reported by the managed entity.
MIB Structure
The MIB has an inverted tree-like structure, with each definition of a managed object
forming one leaf, located at the end of a branch of that tree. Each “leaf” in the MIB is
reached by a unique path, therefore by numbering the branching points, starting with
the top, each leaf can be uniquely defined by a sequence of numbers. The formal
description of the managed objects and the MIB structure is provided in a special
standardized format, called Abstract Syntax Notation 1 (ASN.1).
Since the general collection of MIB's can also be organized in a similar structure,
under the supervision of the Internet Activities Board (IAB), any parameter
included in a MIB that is recognized by the IAB is uniquely defined.
To provide the flexibility necessary in a global structure, MIB's are classified in
various classes (branches), one of them being the experimental branch, and
another the group of private (enterprise-specific) branch.
Under the private (enterprise-specific) branch of MIB's, each enterprise
(manufacturer) can be assigned a number, which is its enterprise number. The
assigned number designates the top of an enterprise-specific sub-tree of non-
standard MIB's. Within this context, RAD has been assigned the enterprise number
164. Therefore, enterprise MIB's published by RAD can be found under
1.3.6.1.4.1.164.
MIB's of general interest are published by the IAB in the form of a Request for
Comment (RFC) document. In addition, MIB's are also often assigned informal
names that reflect their primary purpose. Enterprise-specific MIB's are published
and distributed by their originator, which is responsible for their contents.
In addition, the DXC SNMP agent supports the RAD-private (enterprise-specific) MIB
identified as (read the following as a continuous string):
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).
rad(164).radGen(6).systems(1).radSysWAN(3).X
where X stands for the specific DXC version as follows:
DXC Chassis X
DXC-30 20
DXC-30E 23
DXC-10A 21
DXC-8R 22
SNMP Communities
To enable the delimitation of management domains, SNMP uses “communities”.
Each community is identified by a name, which is an alphanumeric string defined
by the user.
Any SNMP entity (this term includes both managed entities and management
stations) is assigned by its user a community name.
In accordance with the SNMP protocol, the SNMP community of the originating
entity is sent in each message.
When an SNMP message is received by the addressed entity, first it checks the
originator's community: if the community name of the message originator differs
from the community name specified for that type of message in the agent, the
message it discarded (SNMP agents of managed entities report this event by means
of an authentication failure trap).
C.3 IP Environment
This section provides general information on the IP environment.
IP Address Structure
Under the IP protocol, each IP network element (SNMP agents, network
management stations, etc.) is called an IP host and must be assigned an IP address.
An IP address is a 32-bit number, usually represented as four 8-bit bytes. Each byte
represents a decimal number in the range of 0 through 255.
The address is given in decimal format, with the bytes separated by decimal points,
e.g., 164.90.70.47. This format is called dotted quad notation.
C-4 IP Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix C SNMP Management
The network portion of an IP address can be one, two or three bytes long, in
accordance with the IP address class. This arrangement is illustrated below:
IP ADDRESS
Byte 1 Byte 2 Byte 3 Byte 4
The class of each IP address can be determined from its leftmost byte, in
accordance with the following chart:
Note The all-zero host identifier is always interpreted as a network identifier, and must
not be assigned to an actual host.
Often, the host portion is further sub-divided into two portions:
Subnet number. For example, subnet numbers can be used to identify
departmental subnetworks. The subnet number follows the network
identifier.
Host number - the last bits of the IP address.
IP Environment C-5
Appendix C SNMP Management DXC-8R/10A/30/30E Installation and Operation Manual
Note A serial port can be configured for management access only when its interface is
configured as DCE.
Typically, the CONTROL port is used for out-of-band communication, and the
MNG port is used as a dial-out port.
The user can select, for each port, between the Serial Link Internet Protocol (SLIP)
and the Point-to-Point Protocol (PPP).
Out-of-band management uses a RAD proprietary protocol for management traffic
handling. The user can also enable the transmission of RIP2 routing tables through
each port, thereby enabling the transfer of management traffic through routers
using the RIP2 protocol.
This option is not available for the internal E1 or DS1 ports of fractional STM-1,
E3 and T3 interface modules.
• Management traffic carried in a dedicated time slot. This communication
mode is available for all the links, except for DIM links. For T3 links using the
C-bit parity application mode, this mode is available only on the internal DS1
ports. The dedicated time slot mode supports the RAD proprietary protocol,
Note that the DXC SNMP agent does not support frame relay management
protocols (ANSI T1.617 Annex D, LMI, etc.), nor is such support required.
The RAD proprietary protocol provides better routing capabilities, therefore it is
recommended to use it whenever feasible.
D.1 Scope
This Appendix presents procedures for installing new software releases in the
DCL.3 module.
The DCL.3 module stores the software in flash memory. The software is stored in
compressed format, and is decompressed and loaded into the module RAM upon
power-up. Since the flash memory is not used to run the software, new software
can be loaded in two ways:
• Off-line, using any PC directly connected to the serial port of the DCL.3
module. In this case, the DXC system cannot carry traffic while software
downloading takes place. This procedure can be used both to upgrade the
module software version, as well as to install software in a new DCL.3 module,
e.g., a repaired module. This installation method is called cold, or local,
software installation.
The cold software installation process must be performed from the DOS
prompt; do not use a DOS window under Windows.
The downloading is performed at a data rate of 115.2 kbps. Make sure that
the serial port of the PC does support this rate.
• Online, through the management link connecting a RADview network
management station using the TFTP protocol. In this case, the connection can
be made either directly or through other RAD systems which support
management communication (e.g., DXC, Megaplex-2100, etc.), without
stopping the operation of the DXC system in which the DCL.3 module is
installed.
This procedure can be used to upgrade the module software version only
while the equipment operates, and therefore it is called warm, or remote,
software installation.
Software releases are distributed on diskettes. The diskettes carry the compressed
software file, WORK.ARJ, and the downloading programs, LDXRY98.EXE and
LFARJ.BAT, which are required only for performing the cold installation.
Preparations
1. Copy the distribution files, WORK.ARJ, LDXRY98.EXE, LFARJ.BAT to the root
directory of your PC.
2. Connect the serial port of the PC to the 9-pin connector designated
CONTROL on the front panel of the DCL.3 module. Use a standard straight
communication cable.
Downloading Procedure
1. Turn the DXC power off.
2. Double-click on the LFARJ.BAT icon.
3. After the program starts, you will see a RESET TARGET prompt. Turn the DXC
power back on.
4. After restarting, the PC attempts to establish communication with the DXC.
The PC displays a FAST LOAD 115200 BPS message. After communication is
established, you will see the DXC response string, 12345.
5. The PC displays an APPLICATION ARJ FILE TO FLASH message, and starts the
downloading process. During this process, all the four DCL indicators flash
together, and you will see messages that indicate the progress of the
downloading process:
Before starting, the DCL flash memory will be erased. At this stage, a WAIT
FOR FLASH message is displayed.
After the DCL flash memory has been erased, you will see a 678 string.
The PC then accesses the file to be downloaded: you should see a FILE
OPEN OK message.
File transfer starts. The progress is indicated by an increasing byte count,
###, in the TRANSMITTING ### BYTES message.
After the file is transmitted, you will see a SENDING FS message, followed
by the total number of bytes: CODE SIZE = ‘byte-number’’.
Troubleshooting
If there is a problem in downloading new software release, do the following:
1. Make sure that the file Lfarj.bat contains the right serial port number (COM1
or COM2). Edit the batch file, if necessary.
2. Make sure that the file Work.arj is not marked as read-only. Otherwise,
remove the read-only attribute.
3. Make sure that all the three files from the installation diskette are in the same
directory on your computer.
4. Make sure that the serial port (COM1 or COM2) configured in the file Lfarj.bat
is not already in use by another program.
5. If the above steps do not help, reset your computer.
Preparations
1. Copy the distribution file, DXC30.ARJ, to the desired directory of the PC used
as a management station.
2. Make sure the network management station can communicate with the DXC.
Downloading Procedure
1. Run the TFTP application.
2. Open the TIME-OUT menu and fill in the fields of the dialog box as follows:
Retransmission 20 seconds.
Total Retransmission 200 seconds.
Time-Out Any desired time, but not less than one minute.
3. Open the TRANSFER menu and fill in the fields of the dialog box as follows:
Host Name Enter the IP address of the destination DXC system, in dotted quad
notation.
Remote File Enter the file name, DXC30.ARJ.
Transfer Type Select Send.
Transfer Mode Select Binary.
Local File Enter the full path needed to reach the file DXC30.ARJ.
4. When done, press the OK button.
The file DXC30.ARJ is now sent to the DXC. The TFTP window displays the
number of bytes already sent to the DXC. If a fault occurs, an error
message will be displayed: in this case, wait at least 30 seconds and then
start again by displaying the TRANSFER menu. Wait until the transfer is
successfully completed.
Note To make the changes in the software effective, you have to reset the DXC, which
may cause data disruption. If you have a redundant DCL.3 module, you can
minimize the data loss by following the safe reset procedure described in the
section below. In a system without redundancy, reset operation will cause data
errors for a time period up to 30 sec. To minimize data loss in this case, wait for a
moment the least critical for data traffic (such as night time or pre-scheduled idle
time) and only then perform a reset.
E.1 Scope
This Appendix includes a concise description of the E1, T1, E3, T3 and SDH
environments, to provide the background information required for the
understanding of the DXC system configuration parameters.
FAS MAS
Channel Data
b. Odd Frames (1,3,5-15) b. Frames 1-15
I 1 A N N N N N A B C D A B C D 1 2 3 4 5 6 7 8
32 Time Slots/Frame TS
0
TS
1
TS
2
TS
3
TS
4
TS
5
TS
6
TS
7
TS
8
TS
9
TS
10
TS
11
TS
12
TS
13
TS
14
TS
15
TS
16
TS
17
TS
18
TS
19
TS
20
TS
21
TS
22
TS TS
23 24
TS
25
TS
26
TS
27
TS
28
TS
29
TS
30
TS
31
FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR
16 Frames/Multiframe 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Notes
I International Bit ABCD ABCD Signaling Bits
N National Bits (Sa4 through Sa8) X Extra Bit
A Alarm Indication Signal (Loss of Frame Alignment - Red Alarm) Y Loss of Multiframe Alignment
FAS Frame Alignment Signal, occupies alternate MAS Multiframe Alignment Signal
(but not necessarily even) frames
Each E1 frame includes 256 bits. The 256 bits are arranged in 32 timeslots of eight
bits each, that carry the data payload. The frame repetition rate is 8,000 per
second, and therefore the data rate supported by each timeslot is 64 kbps. The
number of timeslots available for user data is maximum 31, because timeslot 0 is
reserved.
Timeslot 0
• Timeslot 0 is used for two main purposes:
• Delineation of frame boundaries. For this purpose, in every second frame
timeslot 0 carries a fixed pattern, called frame alignment signal (FAS). Frames
carrying the FAS are defined as even frames, as they are assigned the numbers
0, 2, 4, etc. when larger structures (multiframes) are used.
The receiving equipment searches for this fixed pattern in the data stream
using a special algorithm, a process called frame synchronization. Once this
process is successfully completed, the equipment can identify each bit in the
received frames.
• Interchange of housekeeping information. In every frame without FAS (odd
frames), timeslot 0 carries housekeeping information. This information is
carried as follows:
Bit 1 - this bit is called the international (I) bit. Its main use is for error
detection using the optional CRC-4 function (CRC-4 stands for Cyclic
Redundancy Check, using a fourth-degree polynomial).
Bit 2 is always set to 1, a fact used by the frame alignment algorithm.
Bit 3 is used as a remote alarm indication (RAI), to notify the equipment at
the other end that the local equipment lost frame alignment, or does not
receive an input signal.
The other bits, identified as Sa4 through Sa8, are designated national bits,
and are actually available to the users, provided agreement is reached as to
their use. RAD equipment with SNMP agents can use the Sa4 bit for inband
management traffic. The total data rate that can be carried by a national bit,
including the Sa4 bit, is 4 kbps.
Multiframes
To increase the information carrying capacity without wasting bandwidth, the
frames are organized in larger patterns, called multiframes. Two types of
multiframes are generally used:
• 256N, which consists of 2 frames (one odd frame and one even frame). The
256N multiframe is generally used when timeslot 16 is available to the user. In
this mode, the maximum number of timeslots available for payload is 31
(maximum payload data rate of 1984 kbps). For systems which use the
common-channel signaling (CCS) method, the CCS information is often
transmitted in timeslot 16.
• 256S, which consists of 16 frames. The 256S multiframe is generally used
when timeslot 16 serves for the transmission of end-to-end signaling using
The HDB3 coding rules restrict the maximum length of a “zero” string to 3 pulse
intervals. Longer strings are encoded at the transmit end to introduce non-zero
pulses.
To allow the receiving end to detect these artificially-introduced pulses and to
enable their removal to restore the original data string, the encoding introduces
intentional bipolar violations in the data sequence. The receiving end detects these
violations and when they appear to be part of an encoded “zero” suppression
string – it removes them.
Bipolar violations which are not part of the HDB3 zero-suppression string are
assumed to be caused by line errors, and are counted separately, to obtain
information on the quality of the transmission link when the CRC-4 function is not
used.
E.3 T1 Environment
The T1 line interface of the DXC system complies with the applicable
requirements of AT&T TR-62411, and ITU-T Rec. G.703 and G.704.
T1 Signal Structure
The T1 line operates at a nominal rate of 1.544 Mbps. The data transferred over
the T1 line is organized in frames. Each T1 frame includes 193 bits.
T1 frame structure is shown in Figure E-2.
Frame 24 Channels/Frame Ft CH CH CH CH
Organization Frame = 193 Bits or
1 2 13 24
Fs
Multiframe
Organization FR FR FR FR FR
1 2 7 11 12
Multiframe
SF (D4) 12 Frames
ESF: 24 Frames
NOTE:
In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24
The 193 bits consist of 24 timeslots that carry the data payload. Each timeslot
consists of eight bits. An additional timeslot, including one bit (the F bit) carries
framing and supervision information. As a result, the data rate supported by each
payload timeslot is 64 kbps. The data rate of the framing slot is 8 kbps.
The T1 frame does not include a dedicated timeslot for the transfer of channel
signaling. When end-to-end transfer of signaling is necessary, a technique called
“robbed-bit signaling” is used. The robbed-bit is the least significant bit (bit 8) of
the channel byte, and is actually “robbed” only once in every six frames.
To enhance link/system supervision capabilities, the frames are organized in larger
patterns, called super-frames. Two types of super-frames are used:
• SF (also called D4), consists of 12 T1 frames.
• Extended SF (ESF), consists of 24 T1 frames.
T1 Environment E-5
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
The implementation of the multiframing format is based on the use of various F-bit
sequences. The F-bit is used to carry three types of information:
• Framing Pattern Sequence (FPS), defines frame and multiframe boundaries.
• Facility Data Link (FDL), allows transfer of supervisory data, e.g., alarms, error
performance, test loop commands, etc., to be passed through the T1 link.
Note RAD equipment with SNMP agents can use the FDL to carry inband management
traffic. The management data rate is then 2 kbps.
• Cyclic Redundancy Check (CRC), allows the measurement of bit error rate and
enhances the reliability of the framing algorithm.
The F-bit pattern thus defines the structure of frames and multiframes. In the D4
(SF) frame format, the F-bit of consecutive frames is alternately interpreted as an
Ft bit (terminal framing bit) or Fs bit (frame signaling bit).
• Ft pattern: alternating 0's and 1's, defines the frame boundaries.
• Fs pattern: fixed 001110 pattern, defines the multiframe boundaries, so that one
frame may be distinguished from another. In particular, the Fs pattern is needed so
that frames 6 and 12 may be identified for the recovery of signaling bits.
In the ESF frame format, the multiframe structure is extended to 24 frames, but the
frame and channel structure are the same as in the D4 (SF) format.
T1 Line Signal
The basic T1 line signal is coded using the alternate mark inversion (AMI) rules. In
the AMI format, “ones” are alternately transmitted as positive and negative pulses,
whereas “zeros” are transmitted as a zero voltage level. The AMI format cannot
transmit long strings of “zeros”, because such strings do not carry timing
information. Therefore, the AMI signal source must generate a signal with
guaranteed minimum “ones” density.
The minimum average “ones” density is 1:8, so when a T1 signal is transmitted
over an AMI line each frame timeslot must include at least one “1" bit. In certain
applications, this would effectively reduce the data rate available to the user to
only 56 kbps per timeslot, and would preclude the provision of clear channel
capability (CCC). To circumvent this problem, modified line codes, which perform
zero suppression by substituting special codes for long strings of “zeros”, are used.
A widely used zero suppression method is B8ZS. The B8ZS zero suppression
method provides clear channel capability, and the “ones” density requirement no
longer restricts user data characteristics. This means that each T1 frame timeslot
can support the full 64 kbps.
T1 Alarm Conditions
The basic alarm conditions are the red alarm and the yellow alarm.
• Red Alarm. A red alarm is generated when the local unit has lost frame
synchronization for more than 2.5 consecutive seconds. Loss of frame
synchronization may be caused by Fs or Ft errors, by the reception of an AIS
signal, or by the loss of input signal.
E-6 T1 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
T1 Environment E-7
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
E.5 E3 Environment
The E3 line interfaces of the DXC system comply with all the applicable
requirements of ITU-T Rec. G.703, G.742, G.751, and G.823.
E3 Signal Structure
The E3 line operates at a nominal rate of 34.368 Mbps. The data transferred over
the E3 line is organized in frames in accordance with ITU-T Rec. G.751. The
structure of the E3 frame is shown in the lower section of Figure E-3.
Each E3 frame includes 1536 bits. The 1536 bits are divided in five groups:
• One set of overhead bits, appearing at the beginning of each E3 frame.
• Four payload groups, each carrying tributary data.
Overhead Bits
The E3 frame overhead includes the following bits:
• Frame alignment signal (FAS) in accordance with ITU-T Rec. G.751 (10 bits).
• A bit, used to carry local alarm indications to the remote equipment.
• N bit, reserved for national use.
Payload Group 1
The first group of payload bits, comprising 372 bits, is located after the overhead
bits.
The group consists of bits cyclically taken from the four internal E2 tributary
streams (in Figure E-3, T1 designates a bit taken from E2 tributary 1, T2 - a bit from
E2 tributary 2, etc.).
E-8 E3 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
Each E2 tributary carries four E1 data streams. The structure of the internal E2 data
streams is identical to the second-order (8448 kbps) multiplexing structure using
positive justification defined by ITU-T Rec. G.742.
The E2 signal structure is shown in the top section of Figure E-3.
E1-1
E1-2
E1-3
E1-4
E1-1
C11
C12
C13
C14
C12
C22
C32
C42
C13
C23
C33
C43
FAS (10 bits) A N
1
13
10 11 12
848
212
213
424
425
428
429
636
637
640
641
644
645
216
217
4 bits 4 bits 4 bits 4 bits 204 bits
(D/J)
C11
C12
C13
C14
C12
C22
C32
C42
C13
C23
C33
C43
T1
T2
T3
T4
T1
1536
13
10 11 12
1152
1153
1156
1157
1160
1161
384
385
768
769
772
773
388
389
Notes
FAS Frame Alignment Signal
A Alarm Indicator to Remote Equipment
N National Bit
Cj1, Cj2, Cj3 Justification Control Bits
D/J Data Bits, Available for Justification
Payload Groups 2, 3, 4
Each of the payload groups 2, 3, and 4 contains a 380-bit payload section similar
in its structure to the payload group 1, except that it has eight additional bits. The
first four payload bits in each 380-bit group (one bit for each E2 tributary, starting
with tributary 1) can carry two types of data:
• One payload bit from the corresponding tributary.
• One stuffing bit, which is discarded by the receiving end. The stuffing bits are
necessary for performing positive justification in accordance with ITU-T Rec.
G.751 (the same method is used for E2 streams multiplexed in accordance
with ITU-T Rec. G.742): with positive justification, the average transmission
rate of any tributary is slightly higher than the actual tributary rate. The
difference, although it is rather small, is enough to exceed the highest allowed
tributary rate, considering the allowed data rate tolerances (±20 ppm). As a
E3 Environment E-9
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
result of positive justification, from time to time no payload bits are available
for transmission, and then stuffing bits are inserted.
Each E3 frame has three payload/stuffing positions for each E2 tributary. The type
of data carried in the positions assigned to a given tributary is indicated by the
justification control bits, designated Cj1, Cj2, Cj3, where j is the tributary number (1,
2, 3, or 4):
• 000 indicates payload data.
• 111 indicates stuffing.
E3 Line Signal
The E3 line signal is coded using the High-Density Bipolar 3 (HDB3) coding rules
(see Section E.1), in accordance with ITU-T Rec. G.703.
During this condition, all the tributaries receive the AIS signal (see Section E.2).
• Loss of input signal. This condition is reported by means of the A bit, and
results in the application of the AIS signal to all the tributaries.
E.6 T3 Environment
The T3 line interface of the DXC system complies with the applicable
requirements of ANSI T1.102, ANSI T1.107, and ANSI T1.107a.
T3 Signal Structure
The T3 line operates at a nominal rate of 44.736 Mbps. The data transferred over
the T3 line is organized in frames. The general structure of a T3 frame (also called
M-frame) is shown in Figure E-4.
M Subframe 1 . . . . . . . . . . . . . . . M Subframe 7
X1 679 bits X2 679 bits P1 679 bits P2 679 bits M1 679 bits M2 679 bits M3 679 bits
M-Frame
(4760 bits)
E-10 T3 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
Each T3 frame includes 4760 bits. The 4760 bits consist of seven M-subframes of
680 bits each, that carry the data payload, framing, and supervision information.
M-Subframe Organization
Figure E-5 shows the organization of the seven M-subframes.
M Subframe Block 1 . . . . . . . . . . . . . . . Block 8
Info Info Info Info Info Info Info Info
X1 F1 C F0 C F0 C F1
1 (84 bits) (84 bits) 1,1 (84 bits) (84 bits) 1,2 (84 bits) (84 bits) 1,3 (84 bits) (84 bits)
Stuff Blocks
Legend
Xn = Status
Pn = Parity
Mn = M-Frame Alignment
Fn = Subframe Alignment
Cn,m = Control
T3 Environment E-11
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
The application type of a DS3 data stream is identified by means of the first
C-bit in M-subframe 1: this bit serves as an application identification channel
(AIC) signal:
For SYNTRAN applications, the AIC signal is a repeating 100,100... pattern
that is used to identify the start of an M-frame triad.
For C-bit parity applications, the AIC signal is a continuous “1”.
Block Organization
Figure E-6 shows the structure of the eight types of blocks contained in
M-subframes.
• The first seven blocks, 1 through 7, are used to carry DS2 tributary data and
overhead data. The overhead bit of these blocks is shared among the five
channels described above.
• The eighth block is used for stuffing, to implement positive justification. For
this purpose, one bit of each block can serve as a stuffing bit for the
corresponding DS2 tributary (the bit is identified as Sj, where j is the tributary
number (1 to 7). For applications that use stuffing, the type of bit (stuffing or
data) is indicated by means of the justification control bits in that subframe
(these bits are designated Cj1, Cj2, Cj3, where j is the tributary number).
The overhead bit of the eighth block is always part of the subframe alignment
channel.
................
Blocks 1 to 7 in
OH D1 D2 D3 D4 D5 D6 D7 D1 D6 D7
All M Subframes ................
Block 8 ................
M Subframe 1 F1 S1 D2 D3 D4 D5 D6 D7 D1 D6 D7
................
................
M Subframe 2 F1 D1 S2 D3 D4 D5 D6 D7 D1 D6 D7
................
................
M Subframe 3 F1 D1 D2 S3 D4 D5 D6 D7 D1 D6 D7
................
................
M Subframe 4 F1 D1 D2 D3 S4 D5 D6 D7 D1 D6 D7
................
................
M Subframe 5 F1 D1 D2 D3 D4 S5 D6 D7 D1 D6 D7
................
................
M Subframe 6 F1 D1 D2 D3 D4 D5 S6 D7 D1 D6 D7
................
................
M Subframe 7 F1 D1 D2 D3 D4 D5 D6 S7 D1 D6 D7
................
E-12 T3 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
The DS2 signal structure includes M-frame and M-subframe alignment channels, an
X-bit status channel, and a C-bit control channel. The control channel is used, among
other functions, to control the justification at the DS2 level.
M-Frame
(1176 bits)
M Subframe 1 . . . . . . . . . M Subframe 4
Stuff Blocks
Legend
X = Status
Mn = M-Frame Alignment
Fn = Subframe Alignment
C = Control
T3 Environment E-13
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
The overhead bits include frame alignment, alarm and error detection bits, and
justification control channels, one for each tributary.
Frame
(840 bits)
Subframe 1 . . . . . . . . . . . . . . Subframe 5
Subframe
FA
1 Tributary Bits
1 10 168
1 4 168
3 JC1
Tributary Bits
1 4 168
JC2
4 Tributary Bits
1 4 168
5 JC3
Tributary Bits
1 4 168
Legend
FA Frame Alignment
A Alarm Indication Bit to Remote Equipment
P Even Parity Bit for Tributary Data
R Reserved Bit
JC1
JC2 Justification Control Bits for Corresponding Tributary
JC3
E-14 T3 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
T3 Environment E-15
Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual
To initiate DS3 and DS1 loopbacks at the far-end terminal from the
near-end terminal.
• DS3-Path Parity Bits. The three C-bits in M-subframe 3, designated CP-bits,
are used to carry DS3 path parity information. The receiver uses these bits to
determine if an error has occurred in M-frame, by computing the parity based
on the contents of M-frame n and comparing this parity value with the parity
received in the CP-bits in M-frame n+1.
• Terminal-to-Terminal Path Maintenance Data Link. The three C-bits in
M-subframe 5 (designated as DL-bits) are used as a 28.2 kbps
terminal-to-terminal path maintenance data link.
The data link uses the Link Access Procedure on the D-channel (LAPD). The
LAPD messages carry DS3 path identification, DS3 idle signal identification,
and DS3 test signal identification information.
In the DXC system, the data link can be used to transmit management traffic.
E-16 T3 Environment
DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore provides the network operator full
control over all the operational aspects of SDH networks and equipment units.
This overhead permits the integration of the network management and
maintenance functions within the transport network itself.
F B B
B B B
N x M Bytes 1
N Rows
2
Order of
Transmission
B B B
M Columns
Legend
B Signal Byte
F Framing Byte
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure.
Each SDH frame starts with framing bytes, which enable equipment receiving the
SDH data stream to identify the beginning of each frame. The location of the other
bytes within this frame structure is determined by its position relative to the
framing byte.
The organization of the frame can be easily understood by representing the frame
structure as a rectangle comprising boxes arranged in N rows and M columns,
where each box carries one byte.
In accordance with this representation, the framing byte appears in the top
left-hand box (the byte located in row 1, column 1), which by convention is
referred to as byte 1 of the SDH frame.
The frame bytes are transmitted bit by bit, sequentially, starting with those in the
first row (see arrow in Figure E-9). After the transmission of a row is completed, the
bits in the next lower row are transmitted. The order of transmission within each
row is from left to right.
After transmission of the last byte in the frame (the byte located in row N, column
M), the whole sequence repeats - starting with the framing byte of the following
frame.
F F F F
Section
Virtual Container
N Rows Overhead
(VC)
M Columns
Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type (see Section E.9).
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
assembled at the point of entry to the SDH network and disassembled only at the
point of exit.
Since the VC is handled as an envelope that is opened only at the path end points,
some of its signal carrying capacity is dedicated to path overhead. The path
overhead provides the facilities (e.g., alarm and performance monitoring), required
to support and maintain the transportation of the VC between the end points.
VC Assembly/Disassembly Process
The concept of a tributary signal being inserted into a virtual container, to be
transported end-to-end across a SDH network, is fundamental to the operation of
SDH networks. This process of inserting the tributary signal into the proper
locations of a VC is referred to as “mapping”.
In all the SDH signal structures, the carrying capacity provided for each individual
tributary signal is always slightly greater than that required by the tributary rate.
Thus, the mapping process must compensate for this difference. This is achieved
by adding stuffing bytes, e.g., path overhead bytes, to the signal stream as part of
the mapping process. This increases the bit rate of the composite signal to the rate
provided for tributary transport in the SDH structure.
At the point of exit from the SDH network, the tributary signal must be recovered
from the virtual container, by removing the path overhead and stuffing bits. This
process is referred to as “demapping”. After demapping, it is necessary to restore
the original data rate of the recovered tributary data stream.
1 Column
Pointers
In Figure E-11, the VC-4 appears to start immediately after the section overhead
part of the STM-1 frame.
Actually, to facilitate efficient multiplexing and cross-connection of signals in the
SDH network, VC-4 structures are allowed to float within the payload part of
STM-1 frames. This means that the VC-4 may begin anywhere within the STM-1
payload part. The result is that in most cases, a given VC-4 begins in one STM-1
frame and ends in the next.
Were the VC-4 not allowed to float, buffers would be required to store the VC-4
data up to the instant it can be inserted in the STM-1 frame. These buffers (called
slip buffers), which are often used in PDH multiplex equipment, introduce long
delays. Moreover, they also cause disruptions in case a slip occurs.
Multiplexer
Section Multiplexer Section
Tributary Tributary
Signals Signals
. SDH SDH .
. Terminal Terminal .
. Multiplexer Multiplexer
.
SDH Cross-Connect
VC VC
Assembly Path Disassembly
As shown in Figure E-12, a transmission path can comprise three types of segments:
• Multiplexer section – a part of a transmission path located between a terminal
multiplexer and an adjacent SDH cross-connect equipment, or between two
adjacent SDH terminal multiplexers.
• Regenerator section – a part of a transmission path located between a
terminal multiplexer or SDH cross-connect equipment and the adjacent
regenerator, or between two adjacent regenerators. A multiplexer section can
include up to three regenerator sections.
• Path – the logical connection between the point at which a tributary signal is
assembled into its virtual container, and the point at which it is disassembled
from the virtual container.
Figure E-13 shows the detailed structure of the overhead data in STM-1 frames.
Path
Section Overhead Overhead
Regenerator
BIP-8 Orderwire User BIP-8
Section B1 E1 F1 B3
Overhead
(Rows 1 - 3)
DCC DCC DCC Signal Label
D1 D2 D3 C2
Multiplex
DCC DCC DCC
Section D7 D8 D9
Overhead
(Rows 5 - 9)
DCC DCC DCC
D10 D11 D12
Orderwire
E2
Alarm Signals
Alarm information is included as part of the MSOH. These functions are explained
in Section E.11.
equipment. This allows the status and performance of a path to be monitored from
either end, or at any point along the path.
Alarm Signals
Alarm and performance information is included as part of the path overhead.
These functions are explained in Section E.11.
The specific container structures for each standard PDH multiplex signal level are
listed below:
• C-11: used to carry the North American 1.544 Mbps DS1 signal.
• C-12: used to carry the CEPT 2.048 Mbps signal.
• C-2: used to carry the North American 6.312 Mbps DS2 signal.
• C-3: used to carry the CEPT 34.368 Mbps E3 signal or the North American
44.768 Mbps DS3 signal.
• C-4: used to carry the 139.264 Mbps CEPT E4 signal or the North American
DS4 signal.
The TU-11 is obtained by inserting the DS1 signal into a C-11 container,
adding the low-path path overhead to obtain the VC-11, and then adding the
TU-11 pointer.
The TU-12 is obtained by inserting the E1 signal into a C-12 container, adding
the low-path path overhead to obtain the VC-12, and then adding the TU-12
pointer.
• TU-2: Each TU-2 frame consists of 108 bytes, structured as 12 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity of
6.912 Mbps and will accommodate the mapping of a North American DS2
signal. 21 TU-2s may be multiplexed into the STM-1 VC-4.
The TU-2 is obtained by inserting the DS2 signal into a C-2 container, adding
the low-path path overhead to obtain the VC-11, and then adding the TU-2
pointer.
• TU-3: Each TU-3 frame consists of 774 bytes, structured as 86 columns of 9
bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity of
49.54 Mbps and will accommodate the mapping of a CEPT 34.368 Mbps E3
signal or a North American 44.768 Mbps DS3 signal. Three TU-3s may be
multiplexed into the STM-1 VC-4.
The TU-3 is obtained by inserting the E3 or DS3 signal into a C-3 container,
adding the low-path path overhead to obtain the VC-3, and then adding the
TU-3 pointer.
Figure E-14 illustrates the assembly of TUs in the VC-4 structure, for the specific
case of the TU-12. 63 TU-12s can be packed into the 260 columns of payload
capacity (i.e., the C-4 container) provided by a VC-4. This leaves 8 columns in the
C-4 container unused. These unused columns result from intermediate stages in
the TU-12 to VC-4 multiplexing process, and are filled by fixed stuffing bytes.
2430 Bytes/Frame
Serial Signal
Stream
F F F F
155.52 Mbps
VC-4 Path Overhead
1 Column
Scope
Sections E.8 through E.10 provide a simplified description of the SDH signal
structure and its main components.
In most applications, to obtain a useful signal, the SDH signal must be generated
by multiplexing various types of payloads. The payload may consist of PDH signals
provided by external PDH multiplexers (for example, E1, T1, E3 or T3 signals) as
well as lower-level SDH signals, which appear within an SDH multiplexer as a
result of the processing of at the STM-1 and/or higher-level (STM-N) signals
received from another SDH multiplexer (for example, in add&drop applications).
Given the complex structure of the SDH frames and its flexibility with respect to
the number and type of signals being transported, the multiplexing and
demultiplexing operations are managed by providing two information items:
• One item specifies the types of signals carried in the SDH frame
• The second item identifies the beginning of the frame structure carrying the
desired signal within the SDH frame.
Related Terms
SDH Mapping
The procedure used to insert a tributary into the corresponding virtual container.
SDH Multiplexing
The procedure used to insert several lower-order path layer signals into a
higher-order path, or the procedure used to insert several higher-order path layer
signals into a multiplex section signal.
SDH Aligning
The procedure used to incorporate the frame offset information into a tributary
unit or administrative unit, to indicate the beginning of that unit’s frame in the
frame of the SDH signal that transports the TU or AU.
Note that for the higher multiplex levels, once a TUG-2 structure is formed, it
is processed as one entity and its detailed structure is no longer relevant.
xN x1
STM-N AUG-4 AU-4 VC-4 C-4 E4 or DS4
(139.264 Mbps)
x3
x3
x1
TUG-3 TU-4 VC-3
x7
T3 (44.736 Mbps)
AU-3 VC-3 C-3 or
E3 (34.368 Mbps)
x7
RAD numbers the TU-12s in accordance with their physical position in the
payload, from 1 to 63. This numbering also best matches the DXC data bus
organization.
Table E-1 has been compiled to match these two numbering systems. It lists the
RAD numbers and the corresponding three ITU G.707 numbers in the same line.
Thus, TU-12 No. 22 in RAD notation matches (2,1,1) in the ITU-T G.707 notation,
and RAD’s TU-12 No. 52 corresponds to G.707 (3,3,2).
Signal Description
Loss of Signal (LOS) LOS state entered when received signal level drops below the value at which
an error ratio of 10-3 is predicted.
LOS state exited when 2 consecutive valid framing patterns are received,
provided that during this time no new LOS condition has been detected
Out of Frame (OOF) OOF state entered when 4 or 5 consecutive SDH frames are received with
invalid (errored) framing patterns. Maximum OOF detection time is therefore
625 µs.
OOF state exited when 2 consecutive SDH frames are received with valid
framing patterns
Loss of Frame (LOF) LOF state entered when OOF state exists for up to 3 ms. If OOFs are
intermittent, the timer is not reset to zero until an in-frame state persists
continuously for 0.25 ms.
LOF state exited when an in-frame state exists continuously for 1 to 3 ms
Loss of Pointer (LOP) LOP state entered when N consecutive invalid pointers are received where N
= 8, 9 or 10.
LOP state exited when 3 equal valid pointers or 3 consecutive AIS indications
are received.
Multiplexer Section AIS Sent by regenerator section terminating equipment (RSTE) to alert
downstream MSTE of detected LOS or LOF state. Indicated by STM signal
containing valid RSOH and a scrambled “all 1’s” pattern in the rest of the
frame.
Detected by MSTE when bits 6 to 8 of the received K2 byte are set to “111”
for 3 consecutive frames. Removal is detected by MSTE when 3 consecutive
frames are received with a pattern other than “111” in bits 6 to 8 of K2.
Signal Description
Far End Receive Failure Sent upstream by multiplexer section terminating equipment (MSTE) within
(FERF or MS-FERF) 250 µs of detecting LOS, LOF or MS-AIS on incoming signal. Optionally
transmitted upon detection of excessive BER defect (equivalent BER, based on
B2 bytes, exceeds 10-3).
Indicated by setting bits 6 to 8 of transmitted K2 byte to “110”.
Detected by MSTE when bits 6 to 8 of received K2 byte are set to “110” for 3
consecutive frames. Removal is detected by MSTE when 3 consecutive frames
are received with a pattern other than “110” in bits 6 to 8 of K2.
Transmission of MS-AIS overrides MS-FERF
AU Path AIS Sent by MSTE to alert downstream high order path terminating equipment
(HO PTE) of detected LOP state or received AU Path AIS. Indicated by
transmitting “all 1’s” pattern in the H1, H2, H3 pointer bytes plus all bytes of
associated VC-3 and VC-4).
Detected by HO PTE when “all 1’s” pattern is received in bytes H1 and H2
for 3 consecutive frames. Removal is detected when 3 consecutive valid AU
pointers are received
High Order Path Remote Generated by high order path terminating equipment (HO PTE) in response to
Alarm Indication received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
(HO Path RAI, also known as POH G1 byte to “1”.
HO Path FERF) Detected by peer HO PTE when bit 5 of received G1 byte is set to “1” for 10
consecutive frames. Removal detected when peer HO PTE receives 10
consecutive frames with bit 5 of G1 byte set to “0”
TU Path AIS Sent downstream to alert low order path terminating equipment (LO PTE) of
detected TU LOP state or received TU path AIS. Indicated by transmitting “all
1’s” pattern in entire TU-1, TU-2 and TU-3 (i.e., pointer bytes V1-V3, V4 byte,
plus all bytes of associated VC-1, VC-2 and VC-3 loaded by “all 1’s” pattern).
Detected by LO PTE when “all 1’s” pattern received in bytes V1 and V2 for 3
consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Low Order Path Remote Generated by low order path terminating equipment (LO FTE) in response to
Alarm Indication received TU Path AIS. Sent upstream to peer LO PTE.
(LO Path RAI, also known as Indicated by setting bit 8 of LO POH V5 byte to “1”.
LO Path FERF) Detected by peer LO PTE when bit 8 of received V5 byte is set to “1” or 10
consecutive multiframes. Removal detected when peer LO PTE receives 10
consecutive multiframes with bit 8 of V5 byte set to “0”.
Multiplexer Section
Regenerator Regenerator
Section Section
LOS LOS
LOF LOF
Tributary
AIS (X2) AIS AIS AIS
(H1H2) (V1V2)
FERF
(X2)
RAI RAI (G1)
(G1)
RAI
(VS) RAI (VS)
B1(BIP-8) B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE FEBE
(G1)
(G1)
BIP-2
(VS)
FEBE FEBE
(VS) (VS)
Legend
Collection LO Low Order PTE Path Terminating Equipment
Transmission HO High Low Order RS TE Regenerator Section Terminating Equipment
Generation MS TE Multiplexer Section Terminating Equipment
Figure E-16. Flow of Alarm and Indication Signals through an SDH Transmission Path
• Far End Receive Failure (FERF) is sent upstream in the multiplexer overhead
after multiplexer section AIS, or LOS, or LOF has been detected by equipment
terminating in a multiplexer section span;
• A Remote Alarm Indication (RAI) for a high order path is sent upstream after a
path AIS or LOP condition has been detected by equipment terminating a
path
• A Remote Alarm Indication (RAI) for a low order path is sent upstream after
low order path AIS or LOP condition has been detected by equipment
terminating a low order path.
Performance Monitoring
Performance monitoring at each level in the maintenance hierarchy is based on
the use of the byte interleaved parity (BIP) checksums calculated on a frame by
frame basis. These BIP checksums are sent downstream in the overhead associated
with the regenerator section, multiplexer section and path maintenance spans.
In response to the detection of errors using the BIP checksums, the equipment
terminating the corresponding path sends upstream Far End Block Error (FEBE)
signals.
F.1 Introduction
This Appendix provides a detailed description of the DXC supervision language.
The information appearing in this Appendix assumes that you are familiar with the
DXC system and with its configuration parameters. If necessary, review Appendix E
for a description of the DXC operating environment, Chapter 5 for a general
description of the DXC supervision language syntax, and Chapter 3 for a functional
description of the DXC system.
The screens appearing in this Appendix are given for illustration purposes only, and
Note
must not be construed as providing typical parameter values. Parameter values must
be selected in accordance with the specific requirements of each particular
application. If necessary, contact RAD Technical Support Department.
BYE
Purpose
End the current Telnet management session. This command is used only for
management sessions using the Telnet protocol. For management sessions
performed by means of a terminal, use the EXIT command.
Syntax
BYE
Use
Type:
BYE<Enter>
CHECK DB
Purpose
Perform a sanity check on the temporary database stored in the editing buffer
located in RAM. The scope of the sanity check is to detect incorrect parameter
values, or inconsistent selection of parameter values.
Syntax
CHECK DB
Use
To perform a sanity check on the current contents of the editing buffer, type:
CHECK DB<Enter>
CLR ALM
Purpose
Clear the alarm buffer.
Syntax
Use
• To clear only the event alarms stored in the alarm buffer, type:
CLR ALM<Enter>
• To clear all the alarms stored in the alarm buffer (including state alarms), type:
CLR ALM/A<Enter>
DXC performs the command and displays the date and time, followed by
the DXC> prompt.
CLR LOOP
Purpose
Deactivate the specified user-initiated loopback.
Syntax
CLR LOOP [loop type] [A:B], or CLR LP [loop type] [A:B]
Use
• To deactivate a local (L) or a remote (R) loopback or a network loopback (LLB
or PLB) on port B of I/O module A, type:
CLR LOOP L A:B<Enter> or CLR LP L A:B<Enter>
CLR LOOP R A:B<Enter> or CLR LP R A:B<Enter>
CLR LOOP TX-LLB A:B<Enter> or CLR LP TX-LLB A:B<Enter>
CLR LOOP TX-PLB A:B<Enter> or CLR LP TX-PLB A:B<Enter>
• To send the deactivation command for the inband activated loopback on port
B of I/O module A, type:
CLR LOOP INBAND A:B <Enter> or CLR LP INBAND A:B <Enter>
DATE
Purpose
Set the date for the DXC internal real-time clock.
Syntax
DATE
Use
1. Enter:
DATE<Enter>
DXC displays the date entry form.
DAY = 01
MONTH = 01
YEAR = 1999
2. Bring the cursor to the first field to be changed by pressing <Enter>, and then
press <F> to increase and <B> to decrease the displayed values. When
done, press <Enter> to move to the next field.
3. Pressing <Enter> after the WEEK DAY field ends the command.
DXC displays the new date and time, followed by the DXC prompt.
DEF AGENT
Purpose
Define the SNMP agent parameters. Refer to Appendix C for additional
explanations.
To enable SNMP and Telnet management, it is necessary to define all the agent
parameters.
Syntax
DEF AGENT
Use
1. To define the SNMP agent parameters, type:
DEF AGENT<Enter>
The first line of the agent data form appears:
TELNET_APATHY_TIME:
2. Select the desired value by pressing the <F> or <B> keys, and then press
<Enter> to continue.
3. You will see the next parameter: to change it, bring the cursor to the value
field, type in the new value, and then press <Enter> to display the next
parameter.
Continue until all the parameters are defined, and then press <Enter> to end.
Remember that community names are case-sensitive.
A typical display, as seen after all the parameters are selected, is shown
below.
CURRENT AGENT PARAMETERS
IP_ADDRESS IS : = 164.202.103.004
SUBNET MASK IS : = 255.255.255.000
DEFAULT GATEWAY IS : = 164.202.103.001
READ COMMUNITY IS : = public
WRITE COMMUNITY IS : = private
TRAP COMMUNITY IS : = public
Display Fields
The agent parameters displayed on the data form, their range of values and user
instructions are given below:
TELNET_APATHY_TIME Press the <F> or <B> keys to select the time, in minutes,
after which a Telnet connection will be automatically
terminated if no incoming activity is detected. The available
values are 10MIN, 15MIN, and 20MIN.
IP_ADDRESS Type in the IP address assigned to the DXC SNMP agent in the
dotted-quad format (four groups of digits in the range of 0
through 255, separated by periods).
DEFAULT GATEWAY Type in the IP address of the router to be used to
communicate with the management station (needed only
when the station is located on a different IP network). To
disable the use of a default gateway, enter 0.0.0.0.
SUBNET MASK Type in the subnet mask in the dotted-quad format. The mask
consists of four groups of digits in the range of 0 through 255,
separated by periods.
READ COMMUNITY Type in the name of the SNMP community that has read-only
authorization (the DXC SNMP agent will accept only
getRequest and getNextRequest commands from management
stations using that community). You may enter up to seven
alphanumeric characters.
WRITE COMMUNITY Type in the name of the SNMP community that has read-write
authorization (the DXC SNMP agent will also accept
setRequest commands from management stations using that
community). You may enter up to seven alphanumeric
characters.
TRAP COMMUNITY Type in the name of the SNMP community to which the DXC
SNMP agent will send traps. You may enter up to seven
alphanumeric characters.
Purpose
Display and modify the alarm attributes. DXC systems support three types of
attributes, explained in the following table:
Type Function
NORMAL Alarm indications and alarm messages are activated in
accordance with the normal conditions:
• The normal indications of DXC units and DCL.3 modules are
described in Chapter 4.
• The normal indications for the various I/O modules are
described in the Installation and Operation Manual for the
corresponding module).
MASKED A masked alarm does not change the DXC alarm status, i.e., it is
neither reported, nor indicated by the DXC system indicators
and alarm relays.
INVERTED For an inverted alarm, the interpretation of alarm conditions with
respect to DXC system visual indications and alarm relay is
inverted, but the state of the alarm recorded in the alarm buffer
is not affected (the alarm buffer shows the true alarm state):
• Normally, an alarm is interpreted as being active when the
associated condition is present (true).
• When the alarm is inverted, the normal condition is when an
alarm condition is present, and the condition that requires
alerting is when the alarm condition is absent.
For example, when a link is temporarily out of service, the alarm indication related to
loss-of-sync on the corresponding link can be inverted: the result is that the ALARM
indicator on the front panel of the DXC system and the corresponding ALM indicator
on the DCL.3 panel is turned off as long as the loss-of-sync condition is present, and
will turn on when the link returns to normal operation.
The same is true with respect to the alarm relay: if the alarm relay is to be
activated by that alarm, then inverting the alarm returns the alarm relay to its
non-alarm state while the alarm state is present.
For convenience, at each level the user can simultaneously change the attributes of
all the alarms that may be generated at that level, or can define the attributes for
individual alarms.
The alarm attributes defined by the user are stored in the non-volatile memory and
therefore are retained even after the DXC is turned off or is reset.
Syntax
DEF ALM ATTRIB
Use
1. To display the alarm attributes data form, type:
DEF ALM ATTRIB<Enter>
The first line, used to select the group of alarms to be processed, appears.
A typical display is shown below:
MAIN_GROUP ATTRIBUTE
SYSTEM USER
The functions of the fields are as follows:
Parameter Function
MAIN_GROUP Selects the main group of alarms to be processed. The full range of
selections, which is available only for a DXC-30 or DXC-30E system,
is as follows:
SYSTEM System alarms.
CL-A DCL.3 module A alarms.
CL-B DCL.3 module B alarms.
IO-1, IO-2, ... IO-15 Alarms related to the module installed in the
corresponding slot.
ATTRIBUTE Selects the alarm attribute to be applied to the selected group of
alarms:
NORMAL None of the alarms in the selected main group is
masked, nor inverted.
MASK All the alarms in a selected main group are masked.
INVERT All the alarms in the selected main group are
inverted.
USER You can select the individual alarms whose
attributes must be modified.
2. To change the attributes of all the alarms in a specific main group, proceed as
• follows:
Select the desired group of alarms: bring the cursor at the beginning of the
MAIN_GROUP field by pressing the spacebar, and then press <F> or
<B> as required.
To reset the alarm attributes of the displayed group to the default (normal)
values, move the cursor to the beginning of the ATTRIBUTES field, and
then press <F> or <B> to display NORMAL.
To mask or invert all the alarms of the displayed group, press <F> or <B>
to display MASK, respectively INVERT.
When done, press <Enter> to end.
The selections available for the SUB_GROUP field are GENERAL (attribute
applicable to the module alarms), PORT_1 (attribute applicable for the alarms
generated by port 1 of the selected module), PORT_2, and so on up to the
maximum number of ports available on the corresponding module.
Select the desired state for the currently displayed alarm by pressing the
<F> or <B> key, and then press <Enter> to display the next alarm
number.
Repeat the procedure until all the alarms in the selected group have been
defined. After the last alarm, you will see again the date and time, followed
by the DXC prompt.
DEF AP
Purpose
Define the priority (severity) of an alarm generated by the DXC.
DXC supports two alarm priorities: minor and major. The indications provided at
each priority level can be defined by means of the DEF AR command. The alarm
priorities are stored in non-volatile memory, and therefore remain in effect even
after the DXC is turned off and then on again.
Syntax
DEF AP LL
Use
1. To define the priority of an alarm, type:
DEF AP LL<Enter>
where LL is the alarm number (see Appendix B for a list of alarms).
The alarm priority data form appears. A typical data form is shown below:
Alarm Number & Description Priority
(67)LAN NOT CONNECTED MINOR
The Alarm Number & Description field displays the code number of
the alarm and its description, and the Priority field displays the alarm priority.
2. To change the current priority, bring the cursor to the Priority field, press the
<F> or <B> keys to display the desired priority, and then press <Enter> to
confirm.
DEF AP ALL
Purpose
Define the priority (severity) of all the alarms generated by the DXC. With this
command, the alarms are automatically displayed, one by one.
For a description of alarm priorities, refer to the DEF AP command.
Syntax
DEF AP ALL
Use
1. To define the priority of an alarm, type:
DEF AP ALL<Enter>
The priority data form for the first alarm appears. A typical data form is
shown in the previous section, covering the DEF AP command.
2. To change the current priority, bring the cursor to the Priority field, press the
<F> or <B> keys to display the desired priority, and then press <Enter> to
confirm. This will display the next alarm.
3. Repeat the procedure until the last alarm is displayed. After making the desired
changes to the last alarm, you will see the DXC prompt.
DEF AR
Purpose
Control the reporting of alarms by means of traps and alarm relay.
Syntax
DEF AR
Use
1. To define the alarm reporting and relay indications, type:
DEF AR<Enter>
The alarm data form appears. A typical data form is shown below:
ALARM REPORT RELAY LOG LED ON BLINK LED
CRITICAL ON YES YES YES YES YES
CRITICAL OFF YES N/A YES N/A N/A
MAJOR ON YES YES YES YES YES
MAJOR OFF YES N/A YES N/A N/A
MINOR ON YES YES YES YES YES
MINOR OFF YES N/A YES N/A N/A
WARNING ON YES YES YES YES YES
WARNING OFF YES N/A YES N/A N/A
EVENT YES YES YES YES YES
2. To change the current selections, bring the cursor to the desired field, and
then press the <F> or <B> keys to display the desired mode (YES or NO).
When done, press <Enter> to end.
Command Fields
The data form includes a list of the alarm conditions of interest, and five columns
which are used to select the action to be taken for each alarm condition. The fields
appearing on the data form are explained below.
ALARM The alarm condition.
REPORT YES indicates that the corresponding alarm condition is reported by
means of messages sent to the terminal, and traps sent to management
stations.
RELAY YES indicates that the alarm relay is activated when the corresponding
condition occurs. Default setting is to be activated for major and critical
alarm levels.
LOG YES indicates that the corresponding alarm condition is recorded in the
alarm buffer.
LED ON YES indicates that the front panel MINOR ALARM and the DCL ALM MN
LEDs light steadily when the corresponding condition occurs. Default
setting is “active for all alarm levels (event level and higher)”.
BLINK LED YES indicates that the front panel MAJOR ALARM and the DCL ALM MJ
LEDs flash when the corresponding condition occurs. Default setting is
“active for all alarm levels (event level and higher)”.
Special Considerations
To ensure consistent display and reporting of alarm conditions, pay attention to
the following points:
• For any alarm function, once it is set to YES at a certain alarm level, it needs to
be set to YES for all the alarm levels above it. For example, if the MINOR LED
is set to be activated for minor alarms, it must also be activated for major and
critical alarms.
• For any alarm condition, once it is set to NO at a certain alarm level, it needs
to be set to NO for all the lower alarm levels. For example, if the MAJOR LED
is set to be deactivated for major alarms, it must also be deactivated for minor,
warning and event alarms.
DEF BERT
Purpose
Define the test conditions for bit error testing.
This command is applicable only for modules with E1 or T1 ports, and for DHL
modules (the DHS and D8HS modules include a fixed-pattern test sequence
generator, and therefore does not require configuration before performing a BER
test).
The command can be used to define two types of parameters:
• The pattern used for BER testing, which is a global parameter (applicable to all
the modules with E1 and T1 ports, including HDSL modules, installed in the
DXC system).
• Parameters applicable for individual module ports, e.g., the timeslots on which
the BER test is performed.
by means of the CLR LOOP INBAND command) is used to disconnect the remote
loopback after the BER test is ended.
To prevent false activation of loopbacks, the user can disable loopback activation
by means of inband codes, and use only activation by means of management
commands.
Syntax
DEF BERT A:B
Use
1. To define the BER test parameters for the desired module port, type:
DEF BERT A:B<Enter>
For DIM modules, type:
DSP BERT A:1<Enter>
You will see the first line of the BERT parameters data form. A typical
display is shown below:
PATTERN ERROR_INJECTION_RATE MODE RX_INBAND
2E15-1 NO ERR USER DISABLE
Parameter Function
PATTERN Selects the test pattern to be used during BER testing. The available
selections are the following pseudo-random sequences: 2E3-1 (23-1),
2E4-1, 2E5-1, 2E6-1, 2E7-1, 511, 2E10-1, 2047, 2E17-1, 2E18-1, QRSS,
2E21-1, 2E22-1, 2E25-1, 2E28-1, 2E29-1, 2E31-1, 2E32-1 (232 - 1).
ERROR_ Enables the injection of a calibrated rate of errors in the transmitted test
INJECTION_RATE pattern. Select NO ERR to disable the injection of errors, select SINGLE
to inject a single error, or enable the injection of errors at a rate of 10E-1,
10E-2, 10E-3, 10E-4, 10E-5, 10E-6, or 10E-7.
MODE Selects the method used to insert the test pattern (and to monitor the
returned data stream). This field is not displayed for DIM modules.
The selections available for this parameter are as follows:
USER Enables the user to define the port timeslots that will carry
the BER test pattern.
Always select USER for testing timeslots routed to another
E1 or T1 port.
DHS_PORT Use this selection for ports routed to a DHS port. In this
case, the test pattern is automatically inserted in the
timeslots routed to the desired port.
RX_INBAND Controls the response to inband loopback activation codes:
ENABLE The port will activate a remote loopback when a
loopback activation code is detected in the data stream.
DISABLE The port will ignore loopback activation codes.
PORT_NUM: A:B
Where A stands for the I/O module number (1 through 15 for the DXC-30
and DXC-30E, 1 through 5 for the DXC-10A, and 1 through 4 for the
DXC-8R), and B stands for the port number within the I/O module (1 or 2).
Make sure to specify a DHS port routed to the port being tested.
If the selected MODE is USER, after pressing <Enter> you will see the first
line of the timeslot selection data form. A typical display is shown below.
TS 1 2 3 4 5 6 7 8 9
CONNECT NO NO NO NO NO NO NO NO NO
3. Move the cursor under each timeslot number in the CONNECT row using the
spacebar, and then change to the desired state (YES for each timeslot to be
tested, and NO for all the other timeslots) using the <F> or <B> keys. After
making the desired selections, press <Enter> to display the next group of
timeslots.
4. Repeat the procedure until all the timeslots (24 for T1 ports, and 31 for E1
ports) have been defined, and then press <Enter> to end.
DEF CALL
Purpose
Define the call-out parameters for the DXC dial-out port (connector MNG of
DCL.3 modules with RS-232 interfaces). The call-out function is enabled by means
of the DEF NP command, and is available only when the network port is
configured as DTE.
The specified call-out parameters are used by the DXC to build the call command
that is sent to the dial-out modem. The modem connected to the MNG connector
must be set up as follows (for convenience, the Hayes commands required to
• select the specified parameters are listed in brackets):
• Auto-answer mode (AT S0=1)
• Call set up in response to the CONNECT string (AT X0)
• No echo (AT E0)
• Verbose mode (no codes, e.g., CONNECT string instead of 0) (AT V1).
Syntax
DEF CALL
Use
1. To define the DXC call-out parameters, type:
DEF CALL<Enter>
The first page of the call-out parameters data form appears. A typical display
is shown below.
The call-out parameters displayed on the first page of the data form, and their
range of values, are as follows:
Parameter Function
NUM_OF_RETRIES This parameter is used to control the number of dialing retries.
0 no redialing attempts are made in case the call is
not established on the first attempt.
1 through 8 in case the call is not established on the first
attempt, DXC will redial the specified number of
times.
The NUM_OF_RETRIES parameter applies to both the primary
and the alternate numbers:
If the call is not established after dialing the primary directory
number the specified number of times, DXC attempts to
establish the call by dialing the alternate directory number
(provided the use of an alternate number is enabled by means of
the ALT_NUM_MODE parameter).
If the call cannot be established within the specified number of
redialing attempts on neither of the two directory numbers, DXC
stops the call attempts. When a new alarm report must be sent,
the call attempts are started again.
The user is notified that the call attempts failed by a message
recorded in the alarm buffer (separate messages are provided for
each directory number).
Parameter Function
WAIT_FOR_CONNECT This parameter specifies the time the DXC will wait for an
answer after each dialing attempt.
If the called station does not answer within the specified time,
the DXC disconnects. If additional call attempts are allowed, the
DXC will redial immediately after disconnecting.
The available selections are 30, 45, or 60 seconds
DIAL_MODE This parameter is used to select the dialing mode:
TONE The modem is instructed to use DTMF dialing.
PULSE The modem is instructed to use pulse dialing.
The appropriate dialing mode depends on the dialing mode
supported by the telephone network
ALT_NUM_MODE This parameter is used to control the use of an alternate number.
The alternate number is dialed used after the specified number
of call attempts on the primary number failed:
NO No alternate number. In this case, the DXC stops the
call attempts after the specified number of call attempts
on the primary number failed.
YES The use of an alternate number is enabled
3. When done, press <Enter> to display the second page of the call-out
parameters data form. A typical display is shown below.
NEW PRIMARY NUMBER [MAX 20 CHARS] =
CURRENT PRIMARY NUMBER = 'primary number'
The second page is used to enter a new primary directory number, and the
second row displays the current primary directory number. The directory
number can include up to 20 digits, including the * and # symbols.
4. Enter the desired directory number, and press <Enter>:
If the ALT_NUM_MODE parameter is NO (no alternate number), the DXC
will display the time and date fields, followed by the DXC prompt.
If the ALT_NUM_MODE parameter is YES, you will see the third page of
the call-out parameters data form, used to enter a new alternate directory
number. A typical display is shown below.
Syntax
DEF DCL FLIP
Use
1. To define the DCL redundancy parameters, type:
DEF DCL FLIP<Enter>
The DCL.3 redundancy parameters data form appears. A typical display is
shown below.
ACTIVE_DCL FLIP_DELAY FLIP_ON_STATION_CLOCK
AUTO 1MIN YES
2. Change the parameter values by pressing the spacebar to bring the cursor to
the beginning of the first field to be changed, and then pressing <F> or <B>
to scroll among the available selections. When the desired selection is
displayed, press the spacebar to move to the next field.
The redundancy parameters and their range of values are as follows:
ACTIVE_ DCL This parameter is used to enable/disable the use of redundancy,
and to enforce the selection of the desired DCL.3 module.
AUTO Redundancy is enabled. The DXC system will use the
DCL.3 module selected by the redundancy control
algorithm, as explained in Chapter 3.
DCL-A Redundancy is disabled. The DXC system will use the
DCL.3 module installed in the CL-A slot.
DCL-B Redundancy is disabled. The system will use the DCL.3
module installed in the CL-B slot.
FLIP_ DELAY This parameter is used to select the minimum acceptable interval,
in minutes, between consecutive decisions to flip between the
DCL.3 modules. The available selections are 1MIN, 2MIN, 3MIN,
and 4MIN.
Purpose
Define or modify the network management stations to which the SNMP agent of
this DXC system will send traps. You can define up to 20 managers. Each network
management station is defined by entering its IP address.
Syntax
DEF MANAGER LIST
Use
1. To define a management station, type:
DEF MANAGER LIST<Enter>
The first line of the managers list data form appears, which is used to
define the IP address of the first management station.
2. Type in the IP address of the desired management station. Use the
dotted-quad format (four groups of digits in the range of 0 through 255,
separated by periods).
A typical data form, as seen after both lines used to define the first
management station have been filled in, is shown below:
MANAGER 1 IP ADDRESS 999.999.999.999
DEF NAME
Purpose
Define the DXC node name (up to eight alphanumeric characters).
Syntax
DEF NAME
Use
1. To define the DXC node name, type:
DEF NAME<Enter>
DXC displays the current name, followed by the name entry form:
OLD NAME = 'name'
ENTER NODE NAME (MAX 8 CHARACTERS) =
CURRENT NAME =
DEF NP
Purpose
Define the configuration parameters of the network port. The configuration
parameters depend on the DCL.3 module version:
• For DCL.3 modules with RS-232 interfaces, this command is used to define
the communication parameters of the MNG port, select its operating mode
(network management access port or dial-out), and when applicable control
the use of the call-out function. The communication parameters of the MNG
port can be different from the communication parameters of the CONTROL
port, which are selected by means of the DEF SP command.
• For DCL.3 modules with Ethernet interfaces, there is only one
user-configurable parameter, the routing protocol.
Syntax
DEF NP
Use
1. Type:
DEF NP<Enter>
If the DCL.3 module has an Ethernet interface, you will see the following
display:
ROUTING_PROTOCOL
NONE
This field controls the transmission of routing tables, which enable the use of the
• routing for management traffic carried through the network port:
NONE – Routing not supported.
PROPRIET – Routing of management traffic by means of the RAD
proprietary protocol.
RIP-II – Management traffic routed using the RIP2 protocol.
3. When done, press <Enter> to display the second line of parameters. A typical
display is shown below.
LOG_OFF AUXILIARY_DEVICE ROUTING_PROTOCOL
NO NMS-SLIP NONE
4. Change the parameter values as explained above, and then press <Enter> to
end.
Parameter Values
The network port parameters and their range of values are as follows:
Parameter Function
SPEED This parameter selects the network port data rate. The available
selections are 300, 1200, 2400, 4800, 9600, 19,200, 38,400,
and 57,600 bps.
DATA This parameter selects the number of data bits in the network
port word format: 7 or 8 data bits.
PARITY This parameter controls the use of parity:
ODD Odd parity
EVEN Even parity
NO Parity disabled (available only with 8 data bits).
CALL_OUT_MODE This parameter controls the use of the call-out function:
NONE The call-out function is disabled.
ALL The DXC will initiate a call after each new alarm.
MAJOR The DXC will initiate a call only when a new major
alarm condition is detected.
If the network port interface is configured as DCE, this field
displays NONE to indicate that the call-out function is disabled.
LOG_OFF Controls the idle disconnect time:
NO Automatic session disconnection disabled.
10_MIN Automatic disconnection after 10 minutes, if no input
data is received by the network port.
Cont.
Parameter Function
AUXILIARY_DEVICE Selects the management mode supported by the network port:
NMS SLIP The network port connects to an SNMP
management station and/or Telnet host, using the
SLIP protocol.
AGENT SLIP The network port is connected to another agent
port using the SLIP protocol.
NMS PPP Same as NMS SLIP, except the PPP protocol is
used.
AGENT PPP Same as AGENT SLIP, except the PPP protocol is
used.
Note: The SLIP and PPP selections are supported only when the
MNG port interface (selected by means of the internal DCL.3
switches) is DCE.
DIAL-OUT The network port operates as a dial-out port. This
selection is supported only when the network port
interface (selected by means of the internal DCL.3
switches) is DTE.
Note: At any time, only one of the two ports of the DCL.3 module
can be used for management access.
ROUTING_ This field controls the transmission of routing tables, which enable
PROTOCOL the use of the routing for management traffic carried through the
network port:
NONE Routing not supported.
PROPRIET Routing of management traffic by means of the
RAD proprietary protocol.
RIP-II Management traffic routed using the RIP2
protocol.
See Appendix C for additional details.
DEF PORT
Purpose
Define the port parameters and the timeslot connections of the specified port.
Syntax
DEF PORT {[A:B] [A:iB] [A:*]}
Use
• To define the parameters of an external port, type:
DEF PORT A:B<Enter>
• To define the parameters of an internal port, type:
DEF PORT A:iB<Enter>
The port parameters data form of the selected I/O module is displayed.
The data form includes several lines; to proceed from line to line, press the
<Enter> key.
The contents of the data form depend on the module type. Refer to the
corresponding module Installation and Operation Manual for detailed
configuration instructions.
DEF PROMPT
Purpose
Select the supervisory port prompt.
Two options are available: the equipment type or the name defined by means of
the DEF NAME command.
Syntax
DEF PROMPT
Use
1. To select the supervisory port prompt, type:
DEF PROMPT <Enter>
The prompt selection form is displayed. A typical form is shown below:
PROMPT_TYPE
PRODUCT_NAME
2. To change the current selection, press <F> or <B>, and then press <Enter>
to end.
The available selections are as follows:
PRODUCT_NAME The prompt consists of the equipment type, followed by
‘>’: DXC8R>, DXC10A>, DXC30>, or DXC30E>.
GIVEN_NAME The prompt consists of the logical name assigned by
means of the DEF NAME command, followed by ‘>’.
DEF PWD
Purpose
Define a new user password for the DXC. The password must have 4 to 6
characters.
Syntax
DEF PWD
Use
1. Type:
DEF PWD<Enter>
DEF RDN
Purpose
Configure a module or module pair for operation in the redundancy mode.
Syntax
DEF RDN A [A]
Use
1. To configure a module for operation in the line redundancy mode (also called
single-slot protection mode), type:
DEF RDN A<Enter>
where A is the number of the slot in which the desired module is installed.
To configure two modules for operation in the hardware (Y-cable) redundancy
or combined line and hardware redundancy (dual-slot protection) mode, type:
DEF RDN A1 A2<Enter>
where A1 is the number of the primary module slot, and A2 is the number of
the secondary module (timeslots need to be routed only to the primary
module).
The first line of the redundancy configuration data form appears. A typical
first line is shown below:
REDUNDANCY_MODE RECOVERY_MODE TIME_OUT
NONE AUTO 10
FLIP_MODE
SOFTWARE
4. Select the desired mode and press <Enter> to end the command.
Note
The second line of the data form for the DFSTM-1 module is different from other
DXC modules. For instructions, refer to the DFSTM-1 Installation and Operation
Manual.
Display Fields
The fields displayed on the redundancy configuration data form are explained
below:
Parameter Function
REDUNDANCY_ Selects the redundancy mode (refer to Chapter 3 for a
MODE description of each mode):
NONE – redundancy is disabled.
SINGLE_SLOT_PROTECTION – operates the selected module
in the line redundancy mode.
Y_CABLE – operates the selected modules in the hardware
redundancy mode.
DUAL_CABLE_PROTECTION – operates the selected modules in
the combined line and hardware redundancy mode. This mode is
supported only by E3 and T3 modules.
RECOVERY_MODE Selects the method used to switch (flip) between the active and
redundant port/module (in accordance with the selected mode:
MANUAL – the active module is manually selected, using the
FORCE ONLINE command. This selection is available only in
the hardware (Y-cable) redundancy mode.
AUTO – switching is automatically performed in accordance
with the method selected with the FLIP_MODE parameter.
This is the only allowed selection in the
SINGLE_SLOT_PROTECTION and DUAL_CABLE_PROTECTION
modes.
Cont.
Parameter Function
TIME_OUT Used to specify the interval following a redundancy flipping (change
of active port/module), in seconds, during which the collection of
the data used to initiate automatic flipping is disabled. No switching
is possible during this interval, therefore the newly selected active
port/module can stabilize and enter normal operation.
The allowed range is 0 (no stabilization interval) to 99 seconds.
FLIP_MODE Used to specify the method for performing redundancy flips in
the AUTO mode:
SOFTWARE – switching is automatically performed in
accordance with a fixed set of criteria, which evaluates the
operational state of the two ports/modules and selects the
alternative capable of providing the best service under the
current conditions (see Chapter 3 for details).
HARDWARE – switching is automatically performed in case the
active port loses frame synchronization.
DEF SP
Purpose
Define the supervisory (CONTROL) port parameters.
The communication parameters of the supervisory port can be different from the
communication parameters of the network port, which are selected by means of
the DEF NP command.
Syntax
DEF SP
Use
1. To define the supervisory port parameters, type:
DEF SP<Enter>
The first line of the supervisory port parameters data form is displayed. A
typical form is shown below. The form presents the current parameter values
as defaults.
SPEED DATA PARITY INTERFACE CTS DCD_DEL DSR ALARM RELAY
9600 Bps 8 NO DCE =RTS 0 MSEC ON NORMAL
2. Change the parameter values by bringing the cursor to the beginning of the
first field to be changed using the spacebar, and then press <F> or <B> to
scroll among the available selections. When the desired selection is displayed,
press the spacebar to move to the next field.
3. When done, press <Enter> to display the second line of the supervisory port
parameters data form. A typical display is shown below.
POP_ALM PWD LOG_OFF AUXILIARY_DEVICE ROUTING_PROTOCOL
NO NO NO TERMINAL NONE
4. After the desired parameter values are selected, press <Enter> to end, and
then press <Enter> again to reconnect to the DXC.
Parameter Values
The supervisory port parameter values are as follows:
Parameter Function
SPEED Selects supervisory port data rate. The available selections are 300,
1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps.
In addition, you can also select AUTO (Autobaud operation). In
this mode, the DXC automatically identifies the incoming traffic
data rate. To enable positive identification, the transmission must
start with three consecutive carriage returns.
Do not use Autobaud when the CONTROL port is configured for
using the SLIP or PPP protocol.
DATA Selects the number of data bits in the CONTROL port word
format: 7 or 8 data bits.
PARITY Controls the use of parity:
ODD Odd parity.
EVEN Even parity.
NO Parity disabled (available only with 8 data bits).
INTERFACE Selects the CONTROL port interface:
DCE The CONTROL port appears as a DCE, for direct
connection to the supervision terminal.
DTE The CONTROL port appears as a DTE, for connection via
modem to the supervision terminal.
CTS Controls the state of the CTS line in the CONTROL port.
ON The CTS line is always ON (active).
=RTS The CTS line follows the RTS line.
DCD_DEL With the CONTROL port defined as DTE, indicates the delay (in
msec) between DCD=ON and sending of data. The available
values are 0, 10, 50, 100, 200, and 300 msec. If you select a
non-zero value when the port interface is programmed as DCE,
you receive ERROR 004 (ILLEGAL DCD_DEL AND INTERFACE
COMBINATION).
Cont.
Parameter Function
DSR Controls the state of the DSR line:
ON The DSR line is continuously on. It will switch to OFF for
five seconds after the DTR line is switched OFF. If you
select DSR=ON when INT=DTE, you will receive
ERROR 005 (conflict in interface and DSR parameters).
=DTR The DSR line tracks the DTR line.
ALARM RELAY Used to select the indication type provided by the alarm relay:
NORMAL The relay contacts are open when the required
indication (as defined by means of the alarm
configuration commands) is normal.
INVERT The relay contacts are closed when the required
indication (as defined by means of the alarm
configuration commands) is normal.
POP_ALM Controls the automatic sending of alarms to a terminal connected
to the CONTROL port:
YES The terminal automatically displays every 10 minutes the
alarm status (or whenever an alarm changes state to ON).
NO The automatic display feature is disabled.
PWD Controls password protection: select YES or NO.
LOG_OFF Controls the idle disconnect time of the CONTROL port.
NO Automatic session disconnection disabled. To
disconnect the session, use the BYE command.
10_MIN Automatic disconnection after ten minutes if no input
data is received by the CONTROL port.
Cont.
Parameter Function
AUXILIARY_ Selects the management mode supported by the CONTROL port:
DEVICE TERMINAL The CONTROL port supports only management by
means of a supervision terminal.
NMS SLIP The CONTROL port connects to an SNMP
management station and/or Telnet host, using the
SLIP protocol.
AGENT SLIP The CONTROL port is connected to another agent
port using the SLIP protocol.
NMS PPP Same as NMS SLIP, except that the PPP protocol is
used.
AGENT PPP Same as AGENT SLIP, except that the PPP protocol
is used.
Notes:
• The SLIP and PPP selections are supported only when the CONTROL port interface
(selected by means of the internal DCL.3 switches) is DCE.
• At any time only one of the two ports of the DCL.3 module can be used for
management access.
ROUTING_ Controls the transmission of routing tables, which enable the routing
PROTOCOL of management traffic carried through the supervisory port:
NONE Routing not supported.
PROPRIET Routing of management traffic by means of the RAD
proprietary protocol.
RIP-II Management traffic routed using the RIP2 protocol.
For additional details on routing protocols, see
Appendix C.
DEF SYS
Purpose
Define the system parameters.
Syntax
DEF SYS
Use
1. To define the system parameters, type:
DEF SYS<Enter>
The first line of the system parameters data form is displayed. A typical form is
shown below. The form presents the current parameter values as defaults.
CLOCK_MASTER CLOCK_FBACK REDUNDANCY STATION_CLOCK MATRIX_MODE DATE_FORMAT
INT NONE NO 1.544MHZ BIDIRECTIONAL DD/MM/YYYY
The table below lists the parameter values for the first two lines.
Parameter Values
Parameter Function
CLOCK_MASTER Selects the master timing reference of the DXC system:
INT Internal oscillator.
RX_CLOCK Receive clock locked to the external device.
A:BEXT Locked to the external clock received from the indicated port. A is the
module number (1 through 15 for the DXC-30 and DXC-30E, 1 through 5
for the DXC-10A, and 1 through 4 for the DXC-8R), and B is an external
port number on the I/O module (1 to 16).
A:BINT Locked to the external clock received from the indicated internal port of a
DE3, DT3, or DFSTM-1 module. A is the module number (see A:BEXT
above), and B is an internal port number within the I/O module (1 to 30).
STATION External (station) clock.
CLOCK_FBACK Selects the alternate (fallback) timing reference for the DXC, to be used in case the master
reference fails.
NONE No fallback source is used.
RX_CLOCK Receive clock locked to the external device.
A:BEXT Locked to the external clock received from the indicated port. A is the
module number (1 through 15 for the DXC-30 and DXC-30E, 1 through 5 for
the DXC-10A, and 1 through 4 for the DXC-8R), and B is an external port
number on the I/O module (1 to 16).
A:BINT Locked to the external clock received from the indicated internal port of a
DE3/DT3 module. A is the module number (see A:BEXT above), and B is
an internal port number within the I/O module (1 to 28).
STATION External (station) clock.
Notes • If you selected one of the ports as a main source, do not select the same port as the
fallback source.
• A DIM module can be selected as timing reference source only if it has an E1 interface.
Cont.
Parameter Function
REDUNDANCY Controls the use of DCL.3 redundancy. The parameters required for controlling the
redundancy function must be defined by means of the DEF DCL FLIP command.
NO Redundancy is disabled.
YES Redundancy is enabled. This value can be selected only for the DXC-30 or
DXC-30E. For the DXC-8R, the redundancy is always enabled.
Note: When replacing a faulty DCL.3 module, always disable the redundancy. Enable
it again once the new DCL.3 module is installed.
STATION_CLOCK Specifies the frequency of the external (station) clock supplied to the DXC: 1.544 MHz or
2.048 MHz.
MATRIX_MODE Selects the operating mode of the DXC central switching matrix, which controls the
routing of individual timeslots among the I/O module ports:
BIDIRECT Bidirectional mode. This is the normal mode of operation. In this
mode, timeslot routing is always symmetrical (the transmit path of each
source timeslot is connected to the receive path of the destination
timeslot, and vice versa).
UNIDIRECT Enables independent control over routing in each direction. The
unidirectional mode enables broadcasting (i.e., simultaneous
transmission) from one source timeslot to multiple destination
timeslots.
Note: The DXC does not allow going back from the unidirectional to bidirectional matrix
mode, if at least one unidirectional connection is present in the system. However,
when needed, you can redefine the symmetric timeslot connections on the source and
destinations timeslots by means of the DEF PORT command.
DATE_FORMAT Selects the date display format:
DD/MM/YYYY
MM/DD/YYYY
YYYY-MM-DD
TS_ALLOC_MODE Selects static or dynamic timeslot allocation mode:
STATIC Allows you to specify the maximum number of timeslots for a given
port (MAX_TS parameter), to allow for static growth of timeslots and
thus prevent dynamic timeslot allocation and possible data disruption
on related ports. Any timeslot on the port may be allocated for traffic,
provided the number of allocated timeslots does not exceed MAX_TS.
STATIC 1:1 Allows you to specify the maximum number of timeslots for a given
port (MAX_TS parameter), to allow for static growth of timeslots and
thus prevent dynamic timeslot allocation and possible data disruption
on all the system ports. In this mode, only TS[1] to TS[MAX_TS] can be
allocated for traffic.
DYNAMIC Allows dynamic timeslot allocation (may cause data disruption on other
ports/slots).
For more information, see Timeslot Allocation to Type 2 (Dynamic Allocation) Modules
on page 3-3.
Note : When you change TS_ALLOC_MODE values from STATIC to DYNAMIC and
vice versa, the cross-connect matrix is rebuilt, thus possibly causing data errors.
Parameter Function
STATION_CLOCK_IF Selects the external clock interface:
G703 ITU-T Rec. G.703, Para. 10 clock interface
RS422 RS-422 clock interface
3. After the desired parameter values are selected, press <Enter>. The third line
of the system parameters data form, which is displayed for all the DXC
versions, is displayed. A typical form is shown below:
SLOT: NO 1 NO 2 NO 3 NO 4 NO 5
TYPE: DT1_CSU DT1_DSU DT1_DSU DT1_F DE1_F
4. Change the module type for each slot. The available selections are:
DT1_CSU DT1B module with CSU interface
DT1_DSU DT1B module with DSU interface
DT1_F DT1B module with fiber optic interface
DT3 DT3 module
DT3_F DT3 module with fiber optic interface
DE1_DSU DE1B module with DSU interface
DE1_LTU DE1B module with LTU interface
DE1_F DE1B module with fiber optic interface
DE1_HDSL DHL/E1 or DHL/E1/2W module
DE1_HDSL/S Single-slot (6U high) DHL/E1 or DHL/E1/2W module
DE3 DE3 module
DE3_F DE3 module with fiber optic interface
DHS DHS module
D8HS D8HS module
DIM_V35 DIM module with V.35 interface
DIM_RS530 DIM module with RS-530 interface
DIM_HSSI DIM module with HSSI interface
DIM_X21 DIM module with X.21 interface
DIM_10_100 DIM module with 10/100BaseT interface
DIM_IR_IP DIM module with IP router interface
DIM_E1 DIM module with E1 interface
D4T1 D4T1 module
D8T1 D8T1 module
D4E1 D4E1 module
D8E1 D8E1 module
D8U D8U module
D16U D16U module
D8SL D8SL module
DFSTM-1 Single-port DFSTM-1 module
DFSTM-1/2 Dual-port DFSTM-1 module.
IO : NO 11 NO 12 NO 13 NO 14 NO 15
TYPE: DT1_CSU DT1_DSU DE1_DSU DT1_CSU DHS
6. Change the module type for each I/O slot as described above, and then press
<Enter> to end.
Purpose
Define a test port and the corresponding configuration parameters.
The test port is used to monitor the data received in user-selectable timeslots of a
selected E1, T1, or DHL port. Any port of a DHS, DE1B, or DT1B module can
serve as a test port.
Syntax
DEF TEST PORT A:B
Use
1. To define the test port and its configuration parameters, type:
DEF TEST PORT A:B<Enter>
where A is the slot number for the test port, and B is the port number. You will
see the first line of the test port data form. A typical line is shown below:
MAP_MODE MON_ENABLE START_TS NUM_OF_TS MON_PORT
USER DISABLE 01 01 01:1
Parameter Function
MAP_MODE Selects the timeslot mapping mode for the test port. The available
selections are as follows:
SEQ - sequential mapping.
USER - Timeslots are individually mapped by the user.
Note that the test port timeslot mapping mode can differ from that
used on the monitored port.
Parameter Function
MON_ENABLE This parameter enables/disables monitoring operation.
START_TS This parameter is applicable only when the SEQ mode is selected.
Its function is to indicate the number of the first timeslot in the
bundle of timeslots being monitored.
The allowed range of timeslots depends on the type of monitored
port: 1 through 31 for an E1 port, and 1 through 24 for a T1 port.
NUM_OF_TS This parameter is applicable only when the SEQ mode is selected.
Its function is to indicate the number of the slots to be monitored.
The allowed range of timeslots is 1 through 31 for an E1 port, and 1
through 24 for a T1 port, however when selecting this number it is
necessary to consider the starting timeslot, and the total number of
timeslots available on the destination port (e.g., when the destination
port is a T1 port, the maximum number of timeslots is 24).
MON_PORT This parameter is used to indicate the monitored port, using the
format A:B, where A is the destination slot number (1 through 15
for the DXC-30 and DXC-30E, 1 through 5 for the DXC-10A, and
1 through 4 for the DXC-8R), and B is the destination port
number:
• 1 or 2 for external E1 or T1 ports.
• 1 to 16 for an internal E1 port of an E3 interface module.
• 1 to 21 for an internal E1 port of a T3/747 interface module.
• 1 to 28 for an internal T1 port of a T3 interface module.
• 1 to 30 for an internal E1 port of a fractional STM-1 interface
module
Only E1 and T1 ports can be monitored.
3. The timeslot selection map is used to select the desired timeslots of the
monitored port. The map consist of several sections, where each section
covers seven timeslots:
The first timeslot map section covers the timeslots 1 through 7 (the timeslot
number appears in the TS line).
A typical first section is shown below:
TS 1 2 3 4 5 6 7
MONITOR : YES YES NO NO YES NO YES
For each timeslot, NO means that the corresponding timeslot is not monitored.
Select YES to route it to the test port.
4. When done, press <Enter> to display the next page, showing timeslots 8
through 14.
5. Repeat the procedure until the last page (ending with timeslot 24 or 31, in
accordance with the monitored port type) is completed. After pressing
<Enter> on the last page, the command is ended.
Note The selections made by means of the DEF TEST PORT take effect only after the UPD
DB command is executed.
DEF TS
Purpose
Define the destination and type of a specific timeslot.
Syntax
DEF TS A:B.TT
Use
1. To configure a specific timeslot, type:
DEF TS A:B:TT<Enter>
Make sure that the slot specified by this command has a module with E1 or
T1 ports (this includes DHL modules).
You are prompted to enter the destination, in the format A:B:TT:
DEST: 01:01:01
2. To change, bring the cursor to beginning of the desired field by pressing the
space key, and then select the desired value using the <F> or <B> keys. The
range of timeslot numbers is 1 through 31 for an E1 port, and 1 through 24
and 25/F for a T1 port. Timeslot 25/F carries the F bit of the original T1 frame.
3. When done, press <Enter> to select the type of timeslot:
TYPE: NC
VC-MP Similar to VOICE, except that the A and B bits are not inverted when the
timeslot is connected to a different type of link (e.g., a T1 slot is
connected to an E1 link, or vice versa). Not applicable to DHS ports.
5. When done, press <Enter> to end the command.
DSP AGENT
Purpose
Display the SNMP agent parameters.
Syntax
DSP AGENT
Use
To display the DXC system SNMP parameters, type:
DSP AGENT<Enter>
The SNMP parameters data form appears. A typical form is shown below:
Agent Name: DXC
Agent IP Address: 192.112.011.024
Agent MAC Address: 40.01.00.10.11.02
DSP ALM
Purpose
Display the contents of the alarm buffer. This buffer can contain up to 100 alarms.
Syntax
DSP ALM [/CA]
Use
• To display the contents of the buffer, type:
DSP ALM <Enter>
• To display the buffer contents, and then clear all the alarms in the buffer, type:
DSP ALM /CA<Enter>
Display Format
The contents of the alarm buffer are displayed as a table with six columns, which
display the alarm number, alarm type (event or state), alarm syntax (description),
the source of the alarm (I/O module and port, when applicable), and the alarm
occurrence time. Each block of alarms received from a DXC is preceded by a
header. The header lists the assigned node name and the node number of the
DXC unit which sent the alarm block, and thus it serves as an easily-identified
separator between alarms transmitted by different DXC units.
Appendix B lists all the alarm messages that can be displayed by the terminal.
DSP AS
Purpose
Display the state alarms for the DXC system, or for a selected module or module
port.
Syntax
DSP AS {[SYS] [A] [A:*] [A:B]}
Use
• To display the state alarms detected at the system level, type:
DSP AS SYS<Enter>
• To display all the state alarms detected at the module level for a specific
module, type:
DSP AS A<Enter>
• To display the state alarms detected for a specific port of a desired module,
type:
DSP AS A:B<Enter>
• To display all the state alarms detected for a specific module (at both the
module and the port levels), type:
DSP AS A:*<Enter>
DSP BERT
Purpose
Display the result of the BER test running on the specified I/O module port.
When monitoring the BER results for DIM modules, and modules with E1 or T1
ports (including DHL modules), you can also perform the following actions:
• Start and stop error injection.
• Restart the error count by clearing the accumulated error results.
The error injection rate is defined by means of the DEF BERT command.
Syntax
DSP BERT A:B [/C] [/I] [/S]
Use
• To display the current result of the BER test (i.e., the BERT error counter), type:
DSP BERT A:B<Enter>
• To display the BER counter, and then clear the counter, type:
DSP BERT A:B /C<Enter>
• For DIM modules, and for modules with E1 or T1 ports (including DHL
modules), you can start the injection of errors by means of the command:
DSP BERT A:B /I<Enter>
• To stop error injection, use the command:
DSP BERT A:B /S<Enter>
Display Format
For DHS and D8HS modules, the terminal displays the current value of the BERT
counter of the selected port. The BERT count range is 0 through 255. If the
maximum value is reached, the counter holds the value until cleared.
For DIM modules, and for modules with E1 or T1 ports, the results are presented in
the following format:
ERROR_BITS RUN_TIME(SEC) ERRORS(SEC) SYNC_LOSS(SEC) ERROR_INJECT
0 100 0 0 OFF
Syntax
DSP BERT A:B REM
Use
Type:
DSP BERT A:B REM<Enter>
Display Format
The results are presented in the following format:
BERT COMMAND
~~~~~~~~~~~~~
BERT IO 9:1
RUN TIME: 469 BIT ERRORS: 524
DXC displays the total number of bit errors detected since launching the LOOP
BERT REM UNIT command to the total time (sec) the test is running.
If the line loses synchronization, the remote BER test automatically disconnects.
DSP BUS
Purpose
Display the utilization of the internal data bus.
When installing a new I/O module in the DXC system or configuring the DXC
system to use additional modules, the information displayed by this command
enables to select a free I/O slot for the new module in a way that minimizes traffic
disruptions caused by reallocation of timeslots on the DXC data buses.
For a description of the DXC data buses and the automatic timeslot allocation
algorithm, refer to Section 3.2.
Syntax
DSP BUS
Use
To display the current utilization of the DXC data buses, type:
DSP BUS<Enter>
Display Format
A typical display for a DXC-30 or DXC-30E is shown below.
BUS_LINK STATUS CAPTURED_BY BUS_LINK STATUS CAPTURED_BY
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
01:01 < DYNAMIC > 01:01 01:02 < DYNAMIC > 01:01
02:01 < DYNAMIC > 01:01 02:02 < DYNAMIC > 01:01
03:01 < FIXED > 03:01 03:02 < FIXED > 03:02
04:01 < --FREE--- > --:-- 04:02 < --FREE--- > --:--
05:01 < FIXED > 05:01 05:02 < FIXED > 05:02
06:01 < FIXED > 06:01 06:02 < FIXED > 06:02
07:01 < FIXED > 07:01 07:02 < FIXED > 07:02
08:01 < FIXED > 08:01 08:02 < FIXED > 08:02
09:01 < --FREE--- > --:-- 09:02 < --FREE--- > --:--
10:01 < --FREE--- > --:-- 10:02 < --FREE--- > --:--
11:01 < FIXED > 11:01 11:02 < FIXED > 11:02
12:01 < --FREE--- > --:-- 12:02 < --FREE--- > --:--
13:01 < --FREE--- > --:-- 13:02 < --FREE--- > --:--
14:01 < --FREE--- > --:-- 14:02 < --FREE--- > --:--
15:01 < FIXED > 15:01 15:02 < FIXED > 15:02
The display includes one row for each I/O slot. The row is divided into two
sections, one for each internal link associated with the corresponding I/O slot. Each
section includes three fields, explained below:
BUS_LINK Displays the identification of the corresponding bus link, in the
format A:L, where A is the I/O slot number and L is the link
number, 01 or 02.
STATUS Displays the status of the corresponding link:
FREE Not allocated. Whenever possible, insert a new module
in an I/O slot whose both links are free.
DYNAMIC The link is allocated to a port of a Type 2 I/O module
(for example, a D4E1, D8E1, D4T1, D8T1, D8SL or
D8HS module). This allocation is dynamic, that is, the
timeslot allocation algorithm may reassign this link to
another port as necessary. Such reassignment may
result in a short disruption of the traffic through this
port.
FIXED The link is allocated to a port of a Type 1 I/O module,
for example DE1B, DT1B, DHS, etc. This allocation is
fixed – the link is always assigned to the module
installed in that slot (or configured in the database,
even if the module is not physically installed).
CAPTURED_BY Displays the identification of the module and port using the
corresponding bus link, in the format A:B, where A is the I/O slot
number and B is the port number.
DSP CON
Purpose
Display the current connection table and timeslot utilization for a selected port or
I/O module.
The displayed information is taken from the working database stored in the
non-volatile memory, therefore it does not reflect changes made by means of the
DEF PORT command in the temporary database stored in the editing buffer
located in RAM.
Syntax
DSP CON {[A:B] [A:X]}
Use
• To display the timeslot data form for a specified port, type:
DSP CON A:B<Enter>
The timeslot connection data form appears.
The display lists the module and port serving each of the eight links that may be
used by a DIM module.
The contents of the data form depend on the module type (refer to the module
Installation and Operation Manual for detailed information), however all the data
• forms have a similar organization:
• The data form header identifies the module port.
• Each data form has several display pages, each presenting data on a group of
timeslots. To proceed from page to page, press <Enter>.
• The information presented on the data form includes the following fields:
Parameter Function
TS Displays the timeslot number. The range of timeslot numbers is:
• 1 through 31 for an E1 port (or for a DHS port connected to an E1 port).
• 1 through 24 and 25/F for a T1 port (or for a DHS port connected to a T1 port).
The timeslot 25/F carries the F bit of the original T1 frame; this enables the user to
select whether to transfer transparently the F bit in connections between E1 and T1
ports, or to generate locally the F bit.
TYPE Displays the timeslot utilization. The available options are:
NC Timeslot is not connected.
DATA The data carried in the timeslot is transparently transferred to the
connected port, without any processing. This provides a clear channel,
suitable for timeslots carrying data.
VOICE The data carried in the timeslot is handled as a voice channel. Therefore,
when the timeslot is connected to a different type of link (e.g., a T1 slot is
connected to an E1 slot, or vice versa), the DXC performs automatically
µ-law to A-law conversion, as well as the conversion of the signaling
format. Not applicable to DHS or D8HS ports.
VC-MP Similar to VOICE, except that the A and B bits are not inverted when the
timeslot is connected to a different type of link (e.g., a T1 slot connected
to an E1 link, or vice versa). Not applicable to DHS or D8HS ports.
Parameter Function
MGMT Timeslot dedicated to management traffic.
DEST Displays the destination timeslot.
• For E1 and T1 ports, the destination timeslot is specified in the format A:B:TT
(module:port:timeslot).
• For DHS ports, all the timeslots are routed to a single port, therefore only the
module and port are indicated.
Note
The second line of the data form (PORT TS UTILIZATION PERCENT) indicates what
percentage of the allocated timeslots is utilized. It appears only for the “dynamic”
(Type 2) modules, when static timeslot allocation mode has been selected.
DSP FDL
Purpose
Display the contents of the last FDL message received by DXC via the selected
link. This option is available on T1 links with ESF framing.
Syntax
DSP FDL A:B
Use
• To see the last FDL message received on the desired port, type:
DSP FDL A:B<Enter>
If the current framing mode of the specified port is SF (D4) or if the port type is E1,
you will receive ERROR 503 (illegal command for current link mode). If the port is
a DHS or D8HS port, you will receive ERROR 504 (illegal command for installed
module).
Display Format
A typical FDL message display is shown below.
FACILITY DATA LINK FROM: I/O-13 PORT-1
SAPI =14 C/R=[0] EA=[0]
TEI =00 EA=[0]
REPORT HH HH HH HH HH HH HH HH
CONTROL =HH
INTERPRETATION T T-1 T-2 T-3
CRC ERR =1 1<N≤5 10<N≤100 N≥320
SE EVENT =NONE NONE NONE NONE
FE EVENT =NONE YES NONE NONE
LV EVENT =NONE NONE YES NONE
SL EVENT =YES NONE NONE NONE
LOOPBACK =YES NONE YES NONE
RESERVED =00 00 00 00
COUNTER =00 01 10 11
FCS =GOOD
T +01:54:33
The message fields are listed below, line by line, from top to bottom:
SAPI Service Access Point Identifier
C/R Command/Response:
C/R = 1 Command
C/R = 0 Response
EA Extended address
TEI Terminal Endpoint Identifier
CONTROL One byte (00 through FF)
REPORT Eight bytes that carry the message contents (see INTERPRETATION
below)
FCS Two bytes that carry the Frame Check Sequence
INTERPRETATION Interpretation of the current message contents (T) and of the three
T, T1, T-2, T-3 previous messages
CRC ERR Number of CRC errors, specified in seven ranges:
NONE
1
1–5
5–10
10–100
100–319
320 or more
DSP FLIP
Purpose
Display the cause of the last switching (flipping) between the DCL.3 modules
installed in a DXC-30, DXC-30E or DXC-8R, or between I/O modules defined as a
redundant pair. This command is relevant only when the DCL.3 and/or I/O
redundancy function is enabled.
If this command is sent to a DXC-10A, the command is rejected and you will see
an error message (Error 508: illegal command for system type).
Syntax
DSP FLIP [X][/C]
Use
• To display the cause of the last flip in the DXC system, type:
DSP FLIP<Enter>
• To display the cause of the last flip for a specific DCL.3 module, type:
DSP FLIP DCLA<Enter> or DSP FLIP DCLB<Enter>
• To display the cause of the last flip for a specific DCL.3 module, and clear the
criteria table of that module, type:
DSP FLIP DCLA /C<Enter> or DSP FLIP DCLB /C<Enter>
• To display the cause of the last flip for a specific I/O module or redundant pair,
type
DSP FLIP A<Enter>
where A stands for the I/O number slot.
• To display the cause of the last flip for a specific module or I/O redundant pair,
and clear the corresponding criteria table, type
DSP FLIP A /C<Enter>
Purpose
Display the results of the last hardware test. The results show the status detected
during the power-on self-test, and any faults detected during regular operation.
Syntax
DSP HDR TST
Use
• To display the local unit hardware test report, type:
DSP HDR TST<Enter>
Display Format
The display has one field that shows NO HARDWARE FAILURE if everything
checks good, or else lists the detected problem:
• DATABASE 1 CHKSUM ERROR
• DATABASE 2 CHKSUM ERROR
• PS-A 5 VOLT FAILURE
• PS-B 5 VOLT FAILURE
• I/O EXPANDER FAILURE
• COUNTER ERROR
• MATRIX FAILURE.
Purpose
Display the network management stations to which the SNMP agent of this DXC
system sends traps. The information provided for each network management
station includes its IP address and the corresponding subnet mask.
Syntax
DSP MANAGER LIST
Use
To display the current list of network management stations, type:
DSP MANAGER LIST<Enter>
DXC displays the list of network management stations that receive traps generated
by this DXC system. A typical display is shown below:
DSP PM
Purpose
Display the contents of the performance monitoring registers specified by AT&T
Pub. 54016. For an explanation of the performance monitoring parameters, refer
to Section 7.2.
The performance monitoring function is available on fractional STM-1 ports, E3
and T3 ports, on T1 ports with ESF framing, on E1 ports with the CRC-4 function
enabled, and on DHL modules.
• For T1 ports using SF (D4) framing, and for E1 ports with the CRC-4 function
disabled, DXC displays ERROR 503 (illegal command for current port mode).
• For DHS ports, DXC displays ERROR 504 (illegal command for card).
Syntax
DSP PM {[A:B] [L]} [/C] [/CA]
Use
• To display the performance monitoring registers of port A:B, type:
DSP PM A:B<Enter>
For external ports, B is a number in the range of ports supported by the
module installed in the I/O slot identified by A.
• The first section of the display shows the performance data for the current
15-minute interval:
The numbers in brackets indicate the range of values for each register.
The same display is applicable for both internal and external T1 ports.
The same display is applicable for both internal and external E1 ports.
INTERVAL 1 LES = 900 PES = 10 PSES = 10 CES = 10 CSES = 10 SEFS = 900 UAS = 900
INTERVAL 2 LES = 900 PES = 10 PSES = 10 CES = 10 CSES = 10 SEFS = 900 UAS = 900
INTERVAL 3 LES = 900 PES = 10 PSES = 10 CES = 10 CSES = 10 SEFS = 900 UAS = 900
INTERVAL 4 LES = 900 PES = 10 PSES = 10 CES = 10 CSES = 10 SEFS = 900 UAS = 900
24 HOUR LES = 65535
24 HOUR PES = 821
24 HOUR PSES = 821
24 HOUR CES = 820
24 HOUR CSES = 820
24 HOUR SEFS = 65535
24 HOUR UAS = 65535
24 DEGRADE MIN = 0
LAST 24 DEGRADE MIN = 0
24 INTERVAL = 82
24 HOUR ES = 0
24 HOUR UAS = 0
24 HOUR SES = 0
24 HOUR LOSWS = 0
24 HOUR CRC = 0
24 HOUR LOSW = 0
CURRENT DAY TIMER = 2154
In addition, D8SL can store and display up to seven sets of 24-hour interval
performance data. The displays are similar to the above.
24 HOUR ES = 1
24 HOUR SES = 1
24 HOUR UAS(SEFS) = 128
24 HOUR CV = 0
24 DEGRADED MIN = 2
LAST 24 DEGRADED MIN = 2
24 INTERVAL = 6
The displays for both low-order (VC-12) and high-order (VC-4) internal ports of an
STM-1 module are similar to the one for the external port.
Syntax
DSP REM AGENT [/A]
Use
• To display the remote agent information, type:
DSP REM AGENT<Enter>
• To display the information for all the remote agents known to the DXC IP
router, type:
DSP REM AGENT [A]<Enter>
A table listing the remote agents appears. A typical table is shown below:
IP ADDRESS MUX NAME DISTANCE PHYSICAL DISTANCE
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
01) 192.114.050.002 New-York 013 004
02) 192.114.150.122 Chicago 009 006
DSP REV
Purpose
Display the list of modules installed in the DXC, and the hardware and software
versions of each module.
Syntax
DSP REV { [X] [*] }
Use
To display information on all the modules, type:
DSP REV *<Enter>
The supervision terminal displays the list of slots in which modules that
include programmable components can be installed, the type of module
installed in each slot, and the module hardware and software revision.
X stands for the I/O module number (1 through 15 for the DXC-30 and
DXC-30E, 1 through 5 for the DXC-10A, and 1 through 4 for the DXC-8R), or
for the DCL.3 module slot (DCLA or DCLB).
A typical display is shown below:
MODULE TYPE HARDWARE REV. SOFTWARE VER
I/O 01 DT1_DSU XX.Y ZZ.W
DSP ST
Purpose
Display status information for a selected module or port. The displayed
information depends on the module or port type, and on its operating mode (with
or without redundancy).
Syntax
DSP ST {[A] [A:B] [A:iB][A:B REM]}
Use
• To display the status information for a selected DCL.3 module, type:
DSP ST DCLA<Enter> or DSP ST DCLB<Enter>
where DCLA or DCLB is the slot of the desired DCL.3 module.
• To display the status of a selected I/O module, type:
DSP ST A<Enter>
• To display the status of a selected external I/O port, type:
DSP ST A:B<Enter>
• To display the status of a selected internal I/O port, type:
DSP ST A:iB<Enter>
The fields included in the status information display are listed below:
Parameters Function
DATABASE Displays the description of the module (DCL.3), as indicated by its
database. The description is the module name.
HARDWARE Displays the description of the module hardware (DCL.3). The
description is the module name.
SOFTWARE Displays the module software version.
VERSION
HARDWARE Displays the module hardware revision.
REVISION
HARDWARE Displays the state of the module hardware:
FAILURE
NO No hardware failure has been detected in this module.
YES A hardware failure has been detected in the module.
ACTIVE STATE Displays the state of the DCL.3 module:
ONLINE The DCL.3 module is the online module, which actively
manages the DXC-30, DXC-30E or DXC-8R.
OFFLINE The DCL.3 module is offline.
SP DEFAULT Displays the state of the DP SP section of switch S1 of the selected
PARAMETERS module. The normal state of this switch is OFF.
Cont.
Parameters Function
PASSWORD Displays the state of the PASSWORD section of switch S1 of the
SWITCH selected module. The normal state of this switch is OFF.
DATABASE INIT Displays the state of the DB INIT section of switch S1 of the
SWITCH selected module. The normal state of this switch is OFF.
PC SP SWITCH Displays the state of the PC/SP section of switch SW1 of the
selected module. The normal state of this switch is OFF.
The fields included in the I/O module status information display are listed below:
Parameter Function
DATABASE Displays the description of the module, as indicated by its
database (as defined by DEF SYS command). The description is
the module name.
HARDWARE Displays the description of the module hardware. The description
is the module name.
SOFTWARE Displays the module software version.
VERSION
HARDWARE Displays the module hardware revision.
REVISION
HARDWARE Displays the state of the module hardware:
FAILURE
NO No hardware failure has been detected in this module.
YES A hardware failure has been detected in the module.
If the module is configured for operation in one of the redundancy modes, the
display also provides information on the selected mode and the current state.
• If the module is configured to operate in the single-slot protection mode, the
following information is displayed:
IO REDUNDANCY MODE: SINGLE_SLOT_PROTECTION
PORT 1 STATE : ONLINE
PORT 2 STATE : OFFLINE
The additional fields display the redundancy mode selected for the module,
and the state of each port (ONLINE for the active port, and OFFLINE for the
standby port).
The additional fields display the redundancy mode selected for the module,
and the state of the module (ONLINE for the active module of the redundant
pair, and OFFLINE for the standby module).
DSP ST MANAGEMENT
Purpose
Display the management status of the system.
Syntax
DSP ST MANAGEMENT
Use
• To display the management status of the system, type:
DSP ST MANAGEMENT <Enter>
Display Format
A typical display format is shown below:
DSP ST RDN
Purpose
Display the redundancy state for a module or redundancy pair.
Syntax
DSP ST RDN {[A] [*]}
Use
• To display the redundancy status of a module, type:
DSP ST RDN A<Enter>,
You will see redundancy status data form. The number of lines depends on
the requested information (one module, or all the modules in the system
that use redundancy).
The display includes the following fields:
PRIMARY Displays the number of the slot, A, of the module defined as
the primary module of the redundancy pair. For a module
operating in the line redundancy mode, this field displays A:1,
meaning that port 1 is always the primary port.
SECONDARY Displays the number of the slot, A, of the module defined as
the secondary module of the redundancy pair. For a module
operating in the line redundancy mode, this field displays A:2,
meaning that port 2 is always the secondary port.
ONLINE For a module operating in the hardware redundancy mode,
displays the number of the slot of the currently on-line module.
For a module operating in the line redundancy mode, this field
displays the number of the currently on-line port.
DSP ST REM
See the DHL/E1, DHL/E1/2W Installation and Operation Manual, D8SL Installation
and Operation Manual and D8U, D16U Installation and Operation Manual.
DSP ST SYS
Purpose
Display system status and information on the installed I/O modules.
Syntax
DSP ST SYS
Use
• To view the current system status, type:
DSP ST SYS<Enter>
Display Format
The display includes two pages: a system status section and an installed-modules
section.
A typical status section display is shown below.
NODE = 0 NAME = 'DXC name' PRODUCT = ‘DXC30’
MAJOR ALARM STATE = OFF MINOR ALARM STATE = OFF ALARM RELAY STATE = OFF
NODAL CLOCK = INT ONLINE DCL = CL-A ACTIVE DATABASE NUMBER = 1
INVERTED ALARMS = NO
Parameter Function
ALARM RELAY Indicates the state of the alarm relay: ON or OFF.
STATE
NODAL CLOCK Indicates the source for the DXC nodal clock:
INT Internal clock oscillator.
STATION The external clock signal applied to the STATION
connector of the DCL.3 module.
A:B The nodal clock is locked to the recovered clock of
the specified port.
ONLINE DCL Displays the slot of the active (on-line) DCL.3 module: CL-A or
CL-B.
ACTIVE Always displays 1.
DATABASE
NUMBER
INVERTED Indicates whether the alarms are inverted.
ALARMS
The installed-modules display includes one group of modules for the DXC-8R and
the DXC-10A, and three groups for the DXC-30 and DXC-30E.
Parameter Function
I/O I/O module number.
DB Database type for the module (as defined by DEF SYS command).
HW Module type:
DT1_CSU DT1 or DT1B module with CSU interface
DT1_DSU DT1 or DT1B module with DSU interface
DT1_F DT1B module with fiber-optic interface
DT3 DT3 module
DT3_F DT3 module with fiber-optic interface
DE1_DSU DE1 or DE1B module with DSU interface
DE1_LTU DE1 or DE1B module with LTU interface
DE1_F DE1B module with fiber-optic interface
DE1_HDSL DHL/E1 or DHL/E1/2W module
DE1_HDSL/S Single-slot (6U high) DHL/E1 or DHL/E1/2W module
DE3 DE3 module
DE3_F DE3 module with fiber-optic interface
DHS DHS module
D8HS D8HS module
DCL DCL.3 module
PS Power supply module and its status:
PS (ON) Module installed and ON
- - - - - - Module not installed or installed, but not ON
DIM_V35 DIM module with V.35 interface
DIM_RS530 DIM module with RS-530 interface
DIM_HSSI DIM module with HSSI interface
DIM_X21 DIM module with X.21 interface
DIM_10_100 DIM module with 10/100BaseT interface.
DIM_IR_IP DIM module with IP router interface.
DIM_E1 DIM module with E1 interface.
D4T1 D4T1 module
D8T1 D8T1 module
D4E1 D4E1 module
D8E1 D8E1 module
D8SL D8SL module
D8U D8U module
D16U D16U module
DFSTM-1 Single-port DFSTM-1 module
DFSTM-1/2 Dual-port DFSTM-1 module
RSVD Reserved (the bus links associated with this slot have
been allocated to a type 2 module).
Note To avoid data disruption, configure a new Type 2 module in the database in the
first I/O slot marked as RSVD (if there are such I/O slots in the HW display).
DSP TS ALLOC
Purpose
This command displays the number of timeslots free for use on the port, module
and system levels.
Syntax
DSP TS ALLOC
Use
• To view the number of timeslots free for use, type:
DSP TS ALLOC <Enter>
Display Format
DXC displays the timeslot allocation for each port of the first dynamic type module
with connected timeslots, followed by the number of free timeslots in the module
pool. This number is automatically calculated by the DXC as a sum of free
timeslots left beyond MAX TS (between the [MAX TS] and 31), all over the module
ports. For those ports where MAX TS was not defined, DXC shows MAX TS as 0
and NUMBER OF FREE TS N/A. If the timeslot allocation mode was defined as
dynamic, this screen displays N/A in all the fields. A typical display for the DXC-30
with the DE1B, D8E1, and D4E1 modules installed in the first, second and third
slot, respectively, is shown below:
DSP TS ALLOCATION:
• Press spacebar to see the similar timeslot allocation screen for the next
module:
DSP TS ALLOCATION:
By the end DXC displays the number of timeslots available on the free links. This
number is calculated as 31 (TS) x number of ports/links whose timeslots are not
connected and/or MAX TS not defined. A typical screen is shown below.
The number of free timeslots in the system pool is calculated as the number of
timeslots on free links plus the sum of free timeslots over all the dynamic modules
installed in the system. In our case it is 589+4+19=612.
Notes • The numbers of free timeslots automatically calculated by the DXC does not take
into account the TS 0’s available on each port. To take the TS 0’s into account,
use the formula given in Evaluating Bandwidth Available for Modules to Be
Installed on page 6-2.
• If the number of timeslots in the free pool is less than 30, a problem of bus
shortage may arise. In this case, the ERROR 528 (BUS EXCEEDED) message
appears after the UPD DB command has been performed. Since this may affect
the existing configuration, you should reduce the number of connected timeslots
used and perform the UPD DB command again.
DSP TS UTILIZATION
Purpose
This command runs over all the dynamic timeslot allocation (Type 2) I/O modules
included into the database and goes through all their ports. For each port, it
displays the number of connected timeslots and the MAX_TS parameter and
calculates the utilization percent.
Syntax
DSP TS UTILIZATION
Use
• To view the current status of timeslot utilization, type:
DSP TS UTILIZATION <Enter>
Display Format
If the static timeslot allocation mode has been selected under DEF SYS, a typical
display is as follows:
If the dynamic timeslot allocation mode has been selected, the following error
message appears: ERROR 532: ILLEGAL COMMAND FOR TS ALLOCATION
MODE.
EXIT
Purpose
End the current management session.
This command is used for management sessions performed by means of a
terminal. For Telnet sessions, use the BYE command.
Syntax
EXIT
Use
• To end the current control session, type:
EXIT<Enter>
Purpose
Define the special codes to be sent to the supervision terminal to perform the
following terminal control functions:
• Clear screen
• Move cursor to screen home position
• Move cursor to the right by one position
Syntax
F
Use
1. To display the current codes, type:
F<Enter>
The terminal function entry screen is displayed. The screen includes three
separate lines, displayed one after the other. A typical screen, showing all
three lines, is shown below.
CLEAR SCREEN = 1B2A0000 (clear screen code)
CURSOR HOME = 1E000000 (cursor home code)
CURSOR RIGHT = 0C000000 (cursor right code)
2. To change a code, press <Enter> to bring the cursor under the first digit of
the code to be changed, then enter the appropriate hexadecimal digits of the
code.
3. Repeat the procedure until all the necessary codes are changed.
FORCE ON LINE
Purpose
Select the online module of a redundancy-configured pair for operation in the
Y-cable redundancy mode.
Syntax
FORCE ON LINE A
Use
To cause one of the two modules of the redundant pair to be the online module,
irrespective of the other conditions, type:
FORCE ONLINE A<Enter>
where A is the desired slot number.
If you specify the slot number of a module configured for single-slot protection, the
command is rejected.
H or HELP
Purpose
Display an index of the supervisory port commands and the options available for
each command.
Syntax
H or HELP
Use
Type:
H or HELP<Enter>
DXC displays the first HELP page.
Press any key to display the next page.
INIT AP
Purpose
Return the alarm priorities to the default values.
Syntax
INIT AP
Use
1. To return the alarm priorities to the default values, type:
INIT AP<Enter>
2. To confirm, type: Y
To cancel the command, type: N.
INIT DB
Purpose
Load a specified set of default parameters values instead of the user configuration
(Table F-1). This command does not update the hardware: to actually start using
the default values, enter the UPDATE DB command.
Syntax
INIT DB [/A]
Use
• To load the set of default parameters values not including the SNMP agent
parameters, type:
INIT DB<Enter>
• To load the set of default parameters values including the SNMP agent
parameters, type:
INIT DB/A<Enter>
DXC loads the default parameters and displays the TIME and DATE fields,
followed by the DXC prompt.
Table F-1. Default DXC Configuration
Parameter Type Parameter Designation Default Value
PASSWORD RAD
NODE 0
General CURSOR RIGHT 00000000
CLEAR SCREEN 00000000
CURSOR HOME 00000000
STATION_CLOCK 1.544 MHz
STATION_CLOCK_IF G703
CLOCK_MASTER INT
System CLOCK_FBACK NONE
REDUNDANCY NO
MATRIX_MODE BIDIRECT
TS_ALLOC_MODE DYNAMIC
FRAME G732N
LINK MODE REGULAR
SYNC CCITT
CRC-4 NO
OOS SIGNAL SPACE
E1 Port VOICE OOS 00
DATA OOS 3E
CGA NONE
IDLE_TS_CODE 7E
INBAND_MGMT NONE
ROUTE_PROT NONE
FRAME ESF
LINK MODE REGULAR
SYNC 62411
OOS SIGNAL SPACE
VOICE OOS 00
DATA OOS 3E
T1 Port CGA NONE
IDLE_TS_CODE 7E
CODE B8ZS
MASK 000
INBAND_MGMT NONE
SIGNALING_MODE ROBBED_BIT
ROUTE_PROT NONE
MULT 64
SPEED NC
HS port FIFO_SIZE AUTO
CLK_MODE DCE
CTS ON
TX_MODE REGULAR
POLARITY NORMAL
DIM port CLK_MODE DCE
MAX_DELAY 64MSEC
DOWNLOAD MODE NO
INIT F
Purpose
Reset the codes used to clear the terminal screen, to move the cursor to the right,
and to return the cursor to the home position, to the default values corresponding
to a selected terminal type, or to zero.
The codes used by the terminals supported by this command are listed in the
following chart:
Terminal Type
Function
TV920 VT52 VT100 Freedom 100/110 Freedom 220
Clear Screen 1B2A0000 N/A 1B5B324A 1B2A0000 1B5B324A
Cursor Home 1E000000 1B480000 1B5B4800 1E000000 1B5B4800
Cursor Right 0C000000 1B430000 1B5B3143 0C000000 1B5B0143
Syntax
INIT F {'terminal'}
Use
• To reset the codes to zero, type:
INIT F<Enter>
• To reset the codes to the codes used by a supported terminal, type:
INIT F ‘terminal’<Enter>
where 'terminal' stands for one of the following terminal types:
VT100, TV920, VT52, FREEDOM100, or FREEDOM220.
The codes are immediately updated and stored in the flash memory,
without requiring the use of the UPDATE DB command.
LOAD DB
Purpose
Load the desired configuration database, stored in the DXC flash memory, to the
editing buffer of the DXC. This replaces the temporary database currently stored in
the editing buffer located in RAM. Therefore, any changes made to the temporary
database will be lost.
Syntax
LOAD DB
Use
1. To load a database from the flash memory to the editing buffer, type:
LOAD DB<Enter>
LOAD HW
Purpose
Compare the actual system hardware configuration with the configuration data in
the system database (i.e., compare the modules actually installed in the DXC
enclosure with the modules defined in the current system database), and update
the edited database with default values for each slot in which a module is
physically installed, but no module is configured.
No changes are made for slots in which a module is defined in the database, even if
that module is not of the type actually installed in the corresponding slot.
To start using the modified database values, use the UPDATE DB command.
The LOAD HW command provides a convenient starting point for system
configuration, after installing/removing modules.
Syntax
LOAD HW
Use
1. To perform the check described above, type:
LOAD HW<Enter>
The following warning message will be displayed:
WARNING!! SYSTEM CONFIGURATION MAY BE CHANGED,
ARE YOU SURE (Y/N)
2. To confirm, type:
Y<Enter>
To cancel, type:
N<Enter>
LOAD OFFLINE DB
Purpose
Load the database stored in the flash memory of the off-line DCL.3 module, into
the flash memory of the on-line DCL.3 module.
This command is applicable only to the DXC-30, DXC-30E, and DXC-8R. If this
command is sent to a DXC-10A, the command is rejected and you will see an
error message (ERROR 508: ILLEGAL COMMAND FOR SYSTEM TYPE).
Syntax
LOAD OFFLINE DB
Use
1. To load the database stored in the non-volatile memory of the off-line DCL.3
module, into the non-volatile memory of the on-line DCL.3 module, type:
LOAD OFFLINE DB<Enter>
DXC displays the following warning message:
WARNING!! DATABASE WILL BE LOST, ARE YOU SURE (Y/N)
LOOP
Purpose
Activate a user-controlled loopback or test (see Chapter 7 for loopback
descriptions).
Syntax
LOOP [looptype] A:B or LP [looptype] A:B
Use
• To activate a local (L) or remote (R) loopback on a selected port, type:
LOOP L A:B<Enter> or LP L A:B<Enter>
LOOP R A:B<Enter> or LP R A:B<Enter>
• To activate a remote (R) loopback on the ASMi-31-2 modem connected to the
specified port of the D8U or D16U module, type:
LOOP R REM_UNIT A:B<Enter>
• To activate the inband activated loopback on port B of I/O module A, type:
LOOP INBAND A:B<Enter> or LP INBAND A:B<Enter>
Note The activation of an inband loopback is made by repeatedly transmitting the
activation sequence, therefore the loopback can be considered as activated only
after approximately 2 to 4 seconds.
• To transmit a line loopback (LLB) or payload loopback (PLB) activation
command through a selected T1 port, type:
LOOP TX-LLB A:B<Enter> or LP TX-LLB A:B<Enter>
LOOP TX-PLB A:B<Enter> or LP TX-PLB A:B<Enter>
• To activate a BERT test on a selected module port, type:
LOOP BERT A:B<Enter> or LP BERT A:B<Enter>
For E1 and T1 modules, you can define the BERT conditions, and the timeslots on
Note
which the test is made, by means of the DEF BERT command.
• To activate a BERT test on a selected module port, type:
LOOP BERT A:B<Enter> or LP BERT A:B<Enter>
• To activate a BER test on the ASMi-31-2 modem connected to the specified
port of the D8U or D16U module, type:
LOOP BERT REM_UNIT A:B <Enter>
• To send the inband loopback activation code on port B of the DHL module
installed in slot A, type:
LOOP HDSL_INBAND A:B <Enter>
or
LP HDSL_INBAND A:B <Enter>
• To activate the local line loopback on port B of the DHL module installed in
slot A, type:
LOOP L LINE A:B<Enter> or LP L LINE A:B<Enter>
• To activate the local loopback on port B of a DHL module, type:
LOOP L PORT A:B
• To activate the remote loopback on the timeslots selected for BER testing on
port B of the local I/O module A, type:
LOOP TS REM A:B <Enter> or LP TS REM A:B <Enter>
• To activate the monitoring of port B of I/O module A, type:
LOOP MONITOR A:B <Enter> or LP MONITOR A:B <Enter>
• To activate the sending of RDI through port B of DFSTM-1 module A, type:
LOOP SND_RDI A:B <Enter> or LP SND_RDI A:B <Enter>
• To activate the sending of AIS through port B of DFSTM-1 module A, type:
LOOP DS_AIS A:B <Enter> or LP DS_AIS A:B <Enter>
At any time, you can activate only one loopback on a given port (however, you can
also activate the BERT test). If you try to activate a second loopback on the same
port, you will see ERROR 501 (illegal link loop combination). You must deactivate
the other loopback before you can activate the new one.
RESET
Purpose
Reset the DXC system.
RESET I/O
Purpose
Reset one of the I/O modules.
Syntax
RESET IO A
Use
To reset the desired single I/O module, type:
RESET IO A <Enter>
where A stands for the I/O number slot.
You are requested to confirm the operation.
TIME
Purpose
Set the time for the DXC internal clock.
Syntax
TIME
Use
1. Type:
TIME<Enter>
DXC sends the time entry form:
HOUR = 12
MINUTE = 25
SECOND = 16
UPDATE DB
Purpose
Copies the contents of the editing buffer of the DXC to the DXC active database,
stored in the non-volatile memory, after performing a complete sanity check. This
changes accordingly the operating mode of the DXC hardware. If errors are
detected during the sanity check, you will be notified.
The update does not include the following parameters, which are updated only by
entering the corresponding command.
• Supervisory port parameters (use DEF SP command).
• Terminal control codes (use F or INIT F command).
Syntax
UPDATE DB or UPD DB
Use
1. To update the database, type:
UPDATE DB<Enter> or UPD DB<Enter>
2. DXC performs a sanity check. The following message is displayed during this
check:
PERFORMING SANITY CHECK ....
If problems are detected during the sanity check, you will be notified:
If one or more sanity errors are detected, you will see the message:
3. To update despite the warnings, type Y and then press <Enter>. You will see
the message:
PERFORMING SANITY CHECK ....
UPDATING SYSTEM’S HARDWARE ....
G.1 Scope
This Appendix presents procedures for uploading and downloading DXC
configuration files, using the TFTP protocol.
Network administrators can use these procedures to distribute verified
configuration files to all the managed DXC units in the network, from a central
location.
To further expedite the process, it is also possible to upload the configuration data
stored by a DXC unit to the management station as a standard disk file, and then
distribute this file to other units, which use similar configuration.
General
The configuration file is named DB1CONF.OL. The transfer of configuration files is
made online, through the serial or Ethernet supervisory port located on the DCL.3
module, without stopping the operation of the DXC system. The transfer can also
be made via inband management, through a dedicated timeslot. Any PC that
supports the TFTP protocol can be used for file transfer.
Preparations
Before starting, make sure that the PC or network management station can
communicate with the DXC through one of its management ports.
Downloading Procedure
1. Perform the command “DIR” to check whether the file DB1CONF.OL exists. If
it doesn’t exist, run the UPD DB 1, LOAD DB 1 and then UPD DB commands.
Now the file DB1CONF.OL exists.
2. Perform the command “DIR” to check whether the file DB2CONF.CFG exists. If
it exists, backup the file (if needed) by performing the command
COPY DB2CONF.CFG <any file name>.
3. Run the TFTP application.
4. Open the TIME-OUT menu and fill in the fields of the dialog box as follows:
Retransmission 20 seconds.
Total Retransmission 200 seconds.
Note If your TFTP application does not support retransmission, this menu will not appear.
In this case, the transfer of files may fail if frames are lost in the network.
5. Open the TRANSFER menu and fill in the fields of the dialog box as follows:
Host Name Enter the IP address of the destination DXC, in dotted quad
notation.
Remote File Enter the configuration file name, DB2CONF.CFG.
Transfer Type Select Send /Put.
Transfer Mode Select Binary.
Local File Enter the full path needed to reach the CNFG.DAT file.
6. When done, press the OK button.
The file CNFG.DAT is now sent to the selected DXC unit. The TFTP
window displays the number of bytes already sent to the DXC. If a fault
occurs, an error message will be displayed: in this case, wait at least
3 minutes and then start again by displaying the TRANSFER menu.
After the transfer is successfully completed, the downloaded database is
stored in the file DB2CONF.CFG.
7. Perform the command LOAD DB 2. Check the contents of the received
configuration file, and make sure that it matches the desired configuration.
You may also edit the configuration to modify parameters that are specific to
the local DXC, e.g., node addresses, IP addresses, etc.
8. After you are sure that the contents of the downloaded database are correct,
perform the command UPD DB 1.
9. Perform the commands LOAD DB 1 and then UPD DB.
Now the downloaded database is stored in the DB1CONF.OL.
10. Delete the file DB2CONF.CFG by performing the command
DEL DB2CONF.CFG.
Uploading Procedure
To prepare the DXC system for sending (uploading) its configuration file to the
management station, load the configuration database to the edit buffer by entering
the command LOAD DB 1 and then UPD DB.
Perform Steps 2-4 of the procedure described above, with the following
differences in Step 4:
• for Remote File type DB1CONF.OL
• for Transfer Type select Receive/Get/Fetch.
H-1
Appendix H Current Versions of DXC Modules DXC-8R/10A/30/30E Installation and Operation Manual
H-2
Index
—A— —C—
Alarms CEPT, E-1
clearing, F-2 Channel relocation and digital cross-connect
defining attributes, 6-16, F-6 applications, 2-7
defining relay conditions, 6-15, F-10 Clear to Send, 3-43
defining severity, 6-15, F-9
Commands
defining traps, 6-15, F-10
BYE, F-2
displaying, F-35, F-36
CHECK DB, F-2
general description, 3-53
CLR ALM, F-2
index of, B-12
CLR LOOP, F-3
inversion, 3-54, 6-16
command protocol, 5-12
masking, 3-53, 6-16
DATE, F-4
processing, 3-53
DEF AGENT, F-4
reporting, 3-53
DEF ALM ATTRIB, F-6
returning to default values, F-68
DEF AP, F-9
ANSI T1.403-1989 statistics, 7-2 DEF AP ALL, F-9
Applications DEF AR, F-10
channel relocation and digital cross-connect, 2-7 DEF BERT, F-11
daisy-chain, 2-16 DEF CALL, F-13
Fractional STM-1, 2-16 DEF CON, F-40
general description, 1-3, 1-4 DEF DCL FLIP, F-16
grooming, 2-17 DEF MANAGER LIST, F-17
HDSL transmission, 2-9 DEF NAME, F-18
high-density module, 2-12 DEF NP, F-19
inverse multiplexing, 2-19 DEF PORT, F-21
ISDN 'U' interface, 2-10 DEF PROMPT, F-22
media converter, 2-5 DEF PWD, F-22
multidrop (broadcast), 2-8 DEF RDN, F-23
providing fractional T1 and E1 access point, 2-7 DEF SP, F-25
SHDSL, 2-15 DEF SYS, F-28
signal monitoring, 2-14 DEF TEST PORT, F-32
T1/E1 converter, 2-4 DEF TS, F-34
T1/E1 drop-&-insert, 2-8 DSP AGENT, F-35
transport of T1 frame over E1 facilities, 2-6 DSP ALM, F-35, F-36
typical local or remote distribution, 2-18 DSP BERT, F-36, F-37
AT&T Pub. 54016 statistics, F-47 DSP BUS, F-38
AUTOBAUD function, 3-44 DSP FDL, F-42
DSP FLIP, F-44
—B— DSP HDR TST, F-45
BER Testing DSP MANAGER LIST, F-46
DE1B, DT1B, D4E1, D8E1, D4T1, D8T1, DHL DSP PM, F-47
modules, 7-32 DSP REM AGENT, F-51
defining parameters, F-11 DSP REV, F-52
DHS and D8HS modules, 7-32 DSP ST, F-53
DIM module, 7-33 DSP ST MANAGEMENT, F-56
displaying results, F-36, F-37 DSP ST RDN, F-60
general, 7-31 DSP ST SYS, F-61
EXIT, F-66
F, F-66
I-1
Index DXC-8R/10A/30/30E Installation and Operation Manual
I-2
DXC-8R/10A/30/30E Installation and Operation Manual Index
I-3
Index DXC-8R/10A/30/30E Installation and Operation Manual
I-4
DXC-8R/10A/30/30E Installation and Operation Manual Index
I-5
Index DXC-8R/10A/30/30E Installation and Operation Manual
I-6
24 Raoul Wallenberg St., Tel Aviv 69719, Israel
Tel: +972-3-6458181, Fax: +972-3-6483331, +972-3-6498250
E-mail: erika_y@rad.com, Web site: www.rad.com
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
Error Report
Type of Error(s) ❒ Incompatibility with product
or Problem(s): ❒ Difficulty in understanding text
❒ Regulatory information (Safety, Compliance, Warnings, etc.)
❒ Difficulty in finding needed information
❒ Missing information
❒ Illogical flow of information
❒ Style (spelling, grammar, references, etc.)
❒ Appearance
❒ Other _________
Please list the exact page numbers with the error(s), detail the errors you found (information missing,
unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
E-mail: _____________________________________________________________________
www.rad.com
INTERNATIONAL HEADQUARTERS:
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel, Tel: 972-3-6458181
Fax: 972-3-6498250, 972-3-6474436, Email: market@rad.com
U.S. HEADQUARTERS:
900 Corporate Drive, Mahwah, N.J. 07430, Tel: (201) 529-1100
Toll Free: 1-800-444-7234, Fax: (201) 529-5777, Email: market@radusa.com