DXC-fm

DXC-8R, DXC-10A, DXC-30, DXC-30E with DCL.3 Common Logic

Installation and Operation Manual

Multiservice Access Nodes

DXC-8R, DXC-10A, DXC-30, DXC-30E

with DCL.3 Common Logic Version 9.0

Multiservice Access Nodes Installation and Operation Manual

Notice This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD"). No part of this publication may be reproduced in any form whatsoever without prior written approval by RAD Data Communications.

Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other intellectual property or other proprietary rights relating to this manual and to the DXC-8R, DXC-10A, DXC-30, DXC-30E (“DXC”) and any software components contained therein are proprietary products of RAD protected under international copyright law and shall be and remain solely with RAD.

DXC is a registered trademark of RAD. No right, license, or interest to such trademark is granted hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to such trademark.

You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the DXC. You are prohibited from, and shall not, directly or indirectly, develop, market, distribute, license, or sell any product that supports substantially similar functionality as the DXC, based on or derived in any way from the DXC. Your undertaking in this paragraph shall survive the termination of this Agreement.

This Agreement is effective upon your opening of the DXC package and shall continue until terminated. RAD may terminate this Agreement upon the breach by you of any term hereof. Upon such termination by RAD, you agree to return to RAD the DXC and all copies and portions thereof.

For further information contact RAD at the address below or contact your local distributor.

International Headquarters RAD Data Communications Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719 Israel Tel: 972-3-6458181 Fax: 972-3-6498250 E-mail: [email protected]

U.S. Headquarters RAD Data Communications Inc. 900 Corporate Drive Mahwah, NJ 07430 USA Tel: (201) 529-1100, Toll free: 1-800-444-7234 Fax: (201) 529-5777 E-mail: [email protected]

© 1993–2004 RAD Data Communications Ltd. Publication No. 772-203-06/04

mailto:[email protected]


Limited Warranty RAD warrants to DISTRIBUTOR that the hardware in the DXC to be delivered hereunder shall be free of defects in material and workmanship under normal use and service for a period of twelve (12) months following the date of shipment to DISTRIBUTOR. 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.

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. 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.

Warning

Warning

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.

Ports Safety Status

V.11, V.28, V.35, V.36, X.21, RS-530, X.21, 10 BaseT, 100 BaseT, Unbalanced E1, E2, E3, STM, DS-2, DS-3, S-Interface ISDN, Analog voice E&M

SELV Safety Extra Low Voltage:

Ports which do not present a safety hazard. Usually up to 30 VAC or 60 VDC.

xDSL (without feeding voltage), Balanced E1, T1, Sub E1/T1

TNV-1 Telecommunication Network Voltage-1:

Ports whose normal operating voltage is within the limits of SELV, on which overvoltages from telecommunications networks are possible.

FXS (Foreign Exchange Subscriber) TNV-2 Telecommunication Network Voltage-2:

Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are not possible. These ports are not permitted to be directly connected to external telephone and data lines.

FXO (Foreign Exchange Office), xDSL (with feeding voltage), U-Interface ISDN

TNV-3 Telecommunication Network Voltage-3:

Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are possible.

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.

To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cords.

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.

Electromagnetic Compatibility (EMC) The equipment is designed and approved to comply with the electromagnetic regulations of major regulatory bodies. The following instructions may enhance the performance of the equipment and will provide better protection against excessive emission and better immunity against disturbances.

A good earth connection is essential. When installing the equipment in a rack, make sure to remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an external grounding lug is provided, connect it to the earth bus using braided wire as short as possible.

The equipment is designed to comply with EMC requirements when connecting it with unshielded twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be installed on certain cables. In such cases, special instructions are provided in the manual.

Disconnect all wires which are not in permanent use, such as cables used for one-time configuration.

The compliance of the equipment with the regulations for conducted emission on the data lines is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal conversion loss (LCL).

Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary protection against surges on the data lines. Primary protectors should be provided in the building installation.

The equipment is designed to provide adequate protection against electro-static discharge (ESD). However, it is good working practice to use caution when connecting cables terminated with plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines. Before connecting such cables, discharge yourself by touching earth ground or wear an ESD preventive wrist strap.

FCC-15 User Information This equipment has been tested and found to comply with the limits of the Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the Installation and Operation manual, may cause harmful interference to the radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

Caution

Attention

Canadian Emission Requirements This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing Equipment Regulation.

Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

Warning per EN 55022 (CISPR-22)

This is a class A product. In a domestic environment, this product may cause radio interference, in which case the user will be required to take adequate measures.

Cet appareil est un appareil de Classe A. Dans un environnement résidentiel, cet appareil peut provoquer des brouillages radioélectriques. Dans ces cas, il peut être demandé à l’utilisateur de prendre les mesures appropriées.

Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkströrungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.

DXC-30, DXC-30E, DXC-10A, DXC-8R Installation Instructions for

Compliance with EMC Requirements 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. To install the ferrite core: • Run the cable through the open core. • Wrap the cable around the core and run it

through again. Allow no more than 2 inches (50 mm) between the core and the connector to the unit.

• Snap the core shut. Note: Two cables from the same module can be run through a single ferrite core.

Warning

Avertissement

Achtung

Declaration of Conformity Manufacturer’s Name: RAD Data Communications Ltd. Manufacturer’s Address: 24 Raoul Wallenberg St. Tel Aviv 69719 Israel declares that the product: Product Name: DXC-30, DXC-30-1 Conforms to the following standard(s) or other normative document(s): EMC: EN 55022 (1994) Limits and methods of measurement of radio disturbance

characteristics of information technology equipment. EN 50082-1 (1992) Electromagnetic compatibility - Generic immunity standards

for residential, commercial and light industry. Safety: EN 60950 (1992/93) Safety of information technology equipment, including

electrical business equipment. 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. Tel Aviv, April 22nd, 1998

Haim Karshen VP Quality European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521Ottobrunn-Riemerling, Germany

Declaration of Conformity Manufacturer’s Name: RAD Data Communications Ltd. Manufacturer’s Address: 24 Raoul Wallenberg St. 69719 Tel Aviv Israel declares that the product: Product Name: DXC-30E-1 Conforms to the following standard(s) or other normative document(s): EMC: EN 55022 (1994) Limits and methods of measurement of radio disturbance


for residential, commercial and light industry. Safety: EN 60950/A4 (1996) Safety of information technology equipment, including

electrical business equipment. 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. Tel Aviv, December 14th, 2000


Declaration of Conformity Manufacturer’s Name: RAD Data Communications Ltd. Manufacturer’s Address: 24 Raoul Wallenberg St. 69719 Tel Aviv Israel declares that the product: Product Name: DXC-10A, DXC-10A-1 Conforms to the following standard(s) or other normative document(s): EMC: EN 55022 (1994) Limits and methods of measurement of radio disturbance


for residential, commercial and light industry. Safety: EN 60950 (1992/93) Safety of information technology equipment, including

electrical business equipment. 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. Tel Aviv, June 7th, 1998


Declaration of Conformity Manufacturer’s Name: RAD Data Communications Ltd. Manufacturer’s Address: 24 Raoul Wallenberg St. 69719 Tel Aviv Israel declares that the product: Product Name: DXC-8R-1 Conforms to the following standard(s) or other normative document(s): EMC: EN 55022 (1994) Limits and methods of measurement of radio disturbance


for residential, commercial and light industry. Safety: EN 60950 A4 (1996) Safety of information technology equipment, including

electrical business equipment. 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. Tel Aviv, August 16th, 2000


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 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.

Notes

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

A note draws attention to a general rule for a procedure, or to exceptions to a rule.

A caution warns of possible damage to the equipment if a procedure is not followed correctly.

A warning alerts to the presence of important operating and maintenance (servicing) instructions in the literature accompanying the equipment. If these instructions are not followed exactly, possible bodily injury may occur.

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.

Note

Caution

Warning

Configuring the DXC 1

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.

2. Configuring the DXC

Perform the following actions in the order given below.

Step Action Use the Command

1 Define terminal control codes F

2 Define control port characteristics DEF SP

3 Set DXC system time TIME

4 Set DXC system date DATE

5 Load default hardware configuration LOAD HW

6 Determine the optimal equipment configuration DSP BUS

7 Define system characteristics DEF SYS

8 Configure each port and its timeslot connections DEF PORT

Quick Start Guide DXC-8R/10A/30/30E Installation and Operation Manual

2 Ending the Configuration Procedure

Cont.

Step Action Use the Command

9 Define redundancy pairs for the desired ports DEF RDN

10 Define DCL redundancy parameters DEF DCL FLIP

11 Define the general system parameters DEF NAME DEF NODE DEF PWD

12 Define network port configuration and dial-up parameters DEF NP DEF CALL

13 Define parameters for SNMP and Telnet management DEF AGENT DEF MANAGER LIST

14 Store the desired configuration database UPD DB D

15 Load the desired configuration database LOAD DB D

3. Ending the Configuration Procedure

DXC is now ready for operation. Connect the required cables to its ports.

1. Turn DXC off, and return the PASSWRD and DP-SP sections of the internal switch S1 of each DCL.3 module to OFF.

2. Turn DXC on again.

DXC-8R/10A/30/30E Installation and Operation Manual i

Contents

Chapter 1. Introduction 1.1 Overview..................................................................................................................... 1-1

Purpose and Use ..................................................................................................................1-1 Main System Features ...........................................................................................................1-1 Management and Power .......................................................................................................1-3

1.2 Applications................................................................................................................. 1-3 PDH Network Access Application .........................................................................................1-3 SDH Network Access Application..........................................................................................1-4 Applications Requiring Wide Link Bandwidth........................................................................1-4

1.3 Physical Description..................................................................................................... 1-5 Versions................................................................................................................................1-5 DXC-30 Enclosure ................................................................................................................1-7 DXC-30E Enclosure...............................................................................................................1-9 DXC-10A Enclosure ............................................................................................................1-10 DXC-8R Enclosure ..............................................................................................................1-11 I/O Modules .......................................................................................................................1-13

1.4 Technical Specifications............................................................................................. 1-15 T1 Electrical Interfaces (DT1B, D4T1, and D8T1 Modules) ..................................................1-15 E1 Electrical Interfaces (DE1B, D4E1, and D8E1 Modules) ...................................................1-16 T1 Optical Interfaces (DT1B Modules).................................................................................1-17 E1 Optical Interfaces (DE1B Modules) .................................................................................1-17 HDSL Interface (DHL/E1 and DHL/E1/2W Modules) ...........................................................1-18 T3 Electrical Interfaces (DT3 Modules) ................................................................................1-18 T3 Optical Interfaces (DT3 Modules)...................................................................................1-19 E3 Electrical Interfaces (DE3 Module) ..................................................................................1-20 E3 Optical Interfaces (DE3 Module) ....................................................................................1-21 Fractional STM-1 Interfaces (DFSTM-1 Modules) .................................................................1-21 ISDN “U” Interfaces (D8U and D16U Modules) .................................................................1-23 SHDSL Interfaces (D8SL Module)........................................................................................1-24 Inverse Multiplexer (DIM Module) ......................................................................................1-26 System Characteristics.........................................................................................................1-27

Chapter 2. System Application Considerations 2.1 Introduction................................................................................................................. 2-1 2.2 Available Services ........................................................................................................ 2-2 2.3 T1/E1 Converter .......................................................................................................... 2-4 2.4 Media Converter ......................................................................................................... 2-5 2.5 Transport of T1 Frames over E1 and E3 Transmission Facilities ..................................... 2-6 2.6 Channel Relocation and Digital Cross-Connect Applications ........................................ 2-7 2.7 Fractional T1 and E1 Access Point................................................................................ 2-7 2.8 T1/E1 Drop-&-Insert .................................................................................................... 2-8 2.9 Multidrop (Broadcast) Applications .............................................................................. 2-8 2.10 HDSL Transmission Applications.................................................................................. 2-9 2.11 ISDN “U” Interface Applications ................................................................................ 2-10 2.12 High-Density Module Applications ............................................................................ 2-12 2.13 M13/T3 Multiplexing Applications ............................................................................. 2-15 2.14 SHDSL Transmission Applications .............................................................................. 2-15

Table of Contents

ii DXC-8R/10A/30/30E Installation and Operation Manual

2.15 Access to SDH Transmission Core.............................................................................. 2-16 2.16 Typical Multiservice Access Node Application............................................................ 2-17 2.17 Inverse Multiplexing Applications............................................................................... 2-19

Chapter 3. Functional Description 3.1 Introduction................................................................................................................. 3-1 3.2 System Structure.......................................................................................................... 3-1

General ................................................................................................................................3-1 Functional Block Diagram .....................................................................................................3-2 Automatic Timeslot Allocation Algorithm...............................................................................3-5 E1 Port Characteristics ........................................................................................................3-11 T1 Port Characteristics ........................................................................................................3-13 E3 Port Characteristics ........................................................................................................3-14 T3 Port Characteristics ........................................................................................................3-14 Fractional STM-1 Subsystem Characteristics.........................................................................3-15 HDSL Subsystem Characteristics .........................................................................................3-16 SHDSL Subsystem Characteristics........................................................................................3-17 High-Speed Data Port Interface Characteristics....................................................................3-17 ISDN “U” Data Port Interface Characteristics.......................................................................3-18

3.3 DXC System Timing ................................................................................................... 3-18 DXC Port Timing.................................................................................................................3-18 DXC System Master Timing.................................................................................................3-20

3.4 Timeslot Routing........................................................................................................ 3-21 Operation of Main Cross-Connect Matrix...............................................................................3-21 DXC System Capacity .........................................................................................................3-23

3.5 Inband Alarm Indications........................................................................................... 3-24 Indications in Individual Timeslots of E1 and T1 Ports..........................................................3-25 Link Alarms for E1 and T1 Ports ..........................................................................................3-26 Alarm Indications for E3 and T3 Ports..................................................................................3-26 Specific Alarm Indications for Fractional STM-1 Modules.....................................................3-27

3.6 Inverse Multiplexer Subsystem Characteristics............................................................ 3-28 Inverse Multiplexing Principles ............................................................................................3-28 Clock Waveform Characteristics ..........................................................................................3-29 Recovery from Fault Conditions ..........................................................................................3-30 DIM Synchronous Data Port Interface Characteristics ..........................................................3-30 DIM Ethernet Port Characteristics........................................................................................3-31 DIM E1 Interface Characteristics .........................................................................................3-31

3.7 Using Redundancy to Increase System Availability ..................................................... 3-32 General ..............................................................................................................................3-32 System-Level Redundancy ..................................................................................................3-32 I/O Redundancy .................................................................................................................3-35

3.8 System Management.................................................................................................. 3-40 Introduction........................................................................................................................3-40 Database Management .......................................................................................................3-40 Management Tools .............................................................................................................3-40 Supervision Terminal Capabilities........................................................................................3-41 Serial Port Interface Characteristics......................................................................................3-41 Handshaking Protocol with Supervision Terminals ...............................................................3-42 Handshaking Protocol with Dial-up Modem........................................................................3-44 AUTOBAUD Function ........................................................................................................3-44 Management Access through LANs and WANs ....................................................................3-45 SNMP and Telnet Management Access Options ..................................................................3-45

Table of Contents

DXC-8R/10A/30/30E Installation and Operation Manual iii

3.9 Diagnostics ................................................................................................................ 3-51 Loopbacks ..........................................................................................................................3-51 Evaluation of Transmission Performance..............................................................................3-51 Loopbacks Supported by E3 and T3 Modules ......................................................................3-51 Loopbacks Supported by Fractional STM-1 Modules ...........................................................3-52 Statistics Collection .............................................................................................................3-52

3.10 Alarm Collection........................................................................................................ 3-52 General ..............................................................................................................................3-52 Alarm Reporting..................................................................................................................3-53 Alarm Processing.................................................................................................................3-53

3.11 Software Updating..................................................................................................... 3-54 3.12 Transfer of Configuration Database ............................................................................ 3-54

Chapter 4. Installation and Operation 4.1 Introduction................................................................................................................. 4-1

Safety Precautions.................................................................................................................4-2 4.2 Site Requirements........................................................................................................ 4-3

General Requirements ..........................................................................................................4-3 Grounding ............................................................................................................................4-3 Power Supply Considerations................................................................................................4-4 Cooling Requirements...........................................................................................................4-5 Protection against ESD ..........................................................................................................4-6 Electromagnetic Compatibility Considerations .......................................................................4-6

4.3 Connection Requirements ........................................................................................... 4-6 Link Connections ..................................................................................................................4-6 External (Station) Clock Connections .....................................................................................4-7 Dry-Contact Alarm Relay Connections ..................................................................................4-8 External Alarm Input .............................................................................................................4-8 Management Port Connections .............................................................................................4-8

4.4 Installation of DXC-30 Enclosure.................................................................................. 4-9 General Description of DXC-30 Enclosure.............................................................................4-9 DXC-30 Enclosure Installation Procedure ............................................................................4-11

4.5 Installation of DPS Modules ....................................................................................... 4-12 Module Panels....................................................................................................................4-12 Internal Jumpers .................................................................................................................4-13 Module Installation .............................................................................................................4-14

4.6 Installation of DCL.3 Module ..................................................................................... 4-15 Module Panels....................................................................................................................4-15 Internal Settings ..................................................................................................................4-16 Module Installation .............................................................................................................4-19 Replacing a Faulty DCL.3 Module .......................................................................................4-20

4.7 Installation of I/O Modules......................................................................................... 4-20 Selection of I/O Slots...........................................................................................................4-20 Installation Procedures ........................................................................................................4-20

4.8 Installation of Optional Fan Tray ................................................................................ 4-20 Fan Tray Description...........................................................................................................4-20 Installation of Fan Tray........................................................................................................4-21

4.9 Cable Connections .................................................................................................... 4-22 Grounding ..........................................................................................................................4-22 Power and Feed Connections .............................................................................................4-22 Connections to DCL.3 Modules ..........................................................................................4-23

Table of Contents

iv DXC-8R/10A/30/30E Installation and Operation Manual

Connection to I/O Modules ................................................................................................4-24 Connections to Optional Fan Tray.......................................................................................4-24

4.10 DXC-30 Operating Instructions .................................................................................. 4-25 Turn-on ..............................................................................................................................4-26 Normal Front-Panel Indications...........................................................................................4-26 Turn-off ..............................................................................................................................4-26

4.11 Installation of DXC-30E Enclosure .............................................................................. 4-27 General Description............................................................................................................4-27 Installation of DXC-30E Enclosure .......................................................................................4-29

4.12 Installation of DPS Modules ....................................................................................... 4-30 Module Panels....................................................................................................................4-30 Internal Jumpers .................................................................................................................4-31 Internal Fuses......................................................................................................................4-32 Module Installation .............................................................................................................4-33

4.13 Installation of DCL.3 Module ..................................................................................... 4-33 Module Panels....................................................................................................................4-33 Internal Settings ..................................................................................................................4-33 Module Installation .............................................................................................................4-33

4.14 Installation of I/O Modules......................................................................................... 4-34 4.15 Installation of Fan Tray............................................................................................... 4-34 4.16 Cable Connections .................................................................................................... 4-35 4.17 DXC-30E Operating Instructions ................................................................................ 4-35

Turn-on ..............................................................................................................................4-35 Normal Front-Panel Indications...........................................................................................4-35 Turn-off ..............................................................................................................................4-36

4.18 Installation of DXC-10A Enclosure ............................................................................. 4-36 General Description............................................................................................................4-36 DXC-10A Installation ..........................................................................................................4-39

4.19 Installation of I/O Modules......................................................................................... 4-40 4.20 Cable Connections .................................................................................................... 4-40 4.21 DXC-10A Operating Instructions................................................................................ 4-40

Connecting the Power ........................................................................................................4-40 Turn-on ..............................................................................................................................4-40 Normal Front-Panel Indications...........................................................................................4-41 Turn-off ..............................................................................................................................4-41

4.22 Installation of DXC-8R Enclosure................................................................................ 4-41 General Description............................................................................................................4-41 Installation of DXC-8R with Replaceable DC Power Supply Modules ...................................4-44 Installation of DXC-8R with AC Power Supply Modules .......................................................4-46

4.23 Installation of I/O Modules......................................................................................... 4-46 4.24 Cable Connections .................................................................................................... 4-46 4.25 DXC-8R Operating Instructions.................................................................................. 4-47

Turn-on ..............................................................................................................................4-47 Normal Front-Panel Indications...........................................................................................4-47 Turn-off ..............................................................................................................................4-48

Chapter 5. Management Using Terminals and Telnet 5.1 Scope .......................................................................................................................... 5-1 5.2 Configuration and Management Activities .................................................................... 5-1

Overview..............................................................................................................................5-1 Preliminary Configuration .....................................................................................................5-2

Table of Contents

DXC-8R/10A/30/30E Installation and Operation Manual v

System Configuration ............................................................................................................5-2 Routine Management ...........................................................................................................5-2

5.3 Connection Methods ................................................................................................... 5-3 Connection of Supervision Terminals ....................................................................................5-3 Connection of Alarm Monitoring Terminals ............................................................................5-4 Connection of Telnet Hosts...................................................................................................5-5 Connections for SNMP Management.....................................................................................5-6

5.4 Preliminary Configuration ............................................................................................ 5-7 DXC Preparations .................................................................................................................5-7 Preparation of Supervision Terminal......................................................................................5-8 Preliminary Configuration .....................................................................................................5-8 Configuration for Using Terminals .........................................................................................5-8 Configuration for Telnet or SNMP Management ....................................................................5-9

5.5 DXC Supervision Language ........................................................................................ 5-11 General ..............................................................................................................................5-11 Supervision Language Syntax...............................................................................................5-12 Command Protocol.............................................................................................................5-12 Command Options .............................................................................................................5-13 Index of Commands ...........................................................................................................5-13

5.6 Supervision Terminal Operating Instructions .............................................................. 5-18 Power-Up with Supervision Terminal Connected ................................................................5-18 Starting a Session - Single DXC............................................................................................5-19 Starting a Session - Multiple DXC ........................................................................................5-19 Control Session...................................................................................................................5-20 Ending a Control Session.....................................................................................................5-20

Chapter 6. Configuring the DXC 6.1 Introduction................................................................................................................. 6-1 6.2 Outline of Configuration Procedure ............................................................................. 6-1 6.3 Determining the Optimal Equipment Configuration ..................................................... 6-2

Planning Timeslot Growth with the Static Allocation Mode ....................................................6-2 Evaluating Bandwidth Available for Modules to Be Installed...................................................6-2 Selecting Optimal I/O Slots for the Modules Installed in a DXC Chassis ..................................6-4

6.4 Defining the System Configuration............................................................................... 6-5 First Data Form Line .............................................................................................................6-5 Second Data Form Line ........................................................................................................6-6 Defining the Modules Installed in the DXC Chassis ................................................................6-7

6.5 Configuring Modules and Ports .................................................................................... 6-7 Timeslot Routing Guidelines..................................................................................................6-8

6.6 Defining I/O Redundancy Pairs.................................................................................... 6-9 Configuration for Line Redundancy Mode...........................................................................6-10 Configuration for Hardware Redundancy Mode ..................................................................6-11 Configuration for Combined Line and Hardware Redundancy.............................................6-11

6.7 Configuring the DCL Redundancy.............................................................................. 6-12 6.8 Configuring the General System Parameters............................................................... 6-12

General Parameters ............................................................................................................6-12 Management Parameters ....................................................................................................6-13

6.9 Configuring the Network Port for Dial-up .................................................................. 6-13 Configuring the Network Port Parameters............................................................................6-14 Configuring the Dial-Up Parameters....................................................................................6-14

6.10 Configuring the Alarm Handling Parameters............................................................... 6-15 Alarm Reporting Policy .......................................................................................................6-15

Table of Contents

vi DXC-8R/10A/30/30E Installation and Operation Manual

Alarm Processing.................................................................................................................6-15 6.11 Saving of Configuration Database .............................................................................. 6-17 6.12 Selecting the Active Database .................................................................................... 6-17

Chapter 7. Tests and Diagnostics 7.1 General ....................................................................................................................... 7-1 7.2 Performance Diagnostics Data ..................................................................................... 7-1

Performance Evaluation for T1 Ports......................................................................................7-1 Performance Evaluation for E1 Ports......................................................................................7-3 Performance Evaluation for T3 and E3 Ports ..........................................................................7-4 Performance Evaluation for HDSL Links ................................................................................7-6 Performance Evaluation for SHDSL Ports...............................................................................7-6 Performance Evaluation for STM-1 Modules..........................................................................7-8 Displaying the Performance Data ..........................................................................................7-9

7.3 User-Controlled Loopback Functions ......................................................................... 7-10 T1 and E1 Modules with T1 and E1 Ports ............................................................................7-10 DHS Modules.....................................................................................................................7-12 DIM Modules .....................................................................................................................7-14 DHL Modules.....................................................................................................................7-15 D8U, D16U Modules .........................................................................................................7-18 D8SL Interface Modules......................................................................................................7-20 E3 Interface Modules ..........................................................................................................7-23 T3 Interface Modules ..........................................................................................................7-25 Fractional STM-1 Module Test and Diagnostic Functions .....................................................7-26

7.4 Network-Controlled Loopback Functions................................................................... 7-30 Modules with T1 Line Interfaces..........................................................................................7-30 Modules with T3 Line Interfaces..........................................................................................7-31

7.5 BER Testing................................................................................................................ 7-31 DHS and D8HS Modules....................................................................................................7-32 DE1B, DT1B, DHL, D4E1, D8E1, D4T1, D8T1 Modules .....................................................7-32 DIM Modules .....................................................................................................................7-33 D8U, D16U Modules .........................................................................................................7-34 D8SL Modules ....................................................................................................................7-35

Appendix A. Connector Wiring Appendix B. Error and Alarm Messages Appendix C. SNMP Management Appendix D. Installing New Software Releases Appendix E. Operating Environment Appendix F. DXC Supervision Language Appendix G. Downloading of Configuration Files Appendix H. Current Versions of DXC Modules

Index

Table of Contents

DXC-8R/10A/30/30E Installation and Operation Manual vii

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 2-1. Typical T1/E1 Converter Applications ..................................................................................... 2-4 2-2. Typical Media Converter Application...................................................................................... 2-6 2-3. Typical T1 Transport Application ............................................................................................ 2-6 2-4. Typical Fractional T1/E1 Access Point Application................................................................... 2-7 2-5. Typical Drop-&-Insert Application .......................................................................................... 2-9 2-6. Typical Multidrop Application ................................................................................................ 2-9 2-7. Typical HDSL Transmission Application................................................................................ 2-10 2-8. Typical Application of D8U/D16U Modules Operating in the /I Mode.................................. 2-11 2-9. Typical Application of D8U/D16U Modules Operating in the /1 Mode................................. 2-12 2-10. Typical High-Density Grooming Application for DXC-30 .................................................... 2-13 2-11. High-Density T1/E1 Conversion and Cross-Connect Application for DXC-8R ...................... 2-13 2-12. E3 Multiplexer Application for DXC-10A ............................................................................ 2-13 2-13. Signaling Monitoring Application ....................................................................................... 2-14 2-14. High-Density High Speed Data Application ....................................................................... 2-14 2-15. T3 Multiplexer Application for DXC-10A ............................................................................ 2-15 2-16. Typical D8SL Application ................................................................................................... 2-16 2-17. Fractional SDH Terminal Multiplexer Application for Remote Access Nodes....................... 2-17 2-18. Multiservice Access Node Application ................................................................................ 2-18 2-19. Basic Inverse Multiplexing System Application .................................................................... 2-19 2-20. Direct Connection to Standalone Inverse Multiplexers........................................................ 2-19 2-21. Transport of E1 Frame across T1 or T3 Transmission Facilities............................................. 2-20 2-22. Fractional E3/T3 Service ..................................................................................................... 2-20 3-1. DXC System, Functional Block Diagram.................................................................................. 3-3 3-2. Typical Line Redundancy Configuration ............................................................................... 3-36 3-3. Typical Hardware (Y-Cable) Redundancy Configuration........................................................ 3-37 3-4. Typical Combined Line & Hardware Protection Configuration.............................................. 3-38 3-5. Connection of Network Management Station to Serial Out-of-Band DXC Supervisory Ports.. 3-47 3-6. Inband Management Access ................................................................................................. 3-48 3-7. Management Topology Illustrating Use of Management Access Options Supported by DXC . 3-49 3-8. Extended Management Topology Using Network Management Stations ............................... 3-50 4-1. DXC-30 Enclosure, Typical Rear View .................................................................................. 4-10 4-2. DXC-30 Enclosure Front Panel ............................................................................................. 4-10 4-3. Attachment of Brackets to DXC-30 ....................................................................................... 4-12 4-4. DXC-30M-PS/AC and DXC-30M-PS/DC Module Panels ....................................................... 4-13 4-5. DC-Powered DPS Module, Location of Internal Jumper ....................................................... 4-14

Table of Contents

viii DXC-8R/10A/30/30E Installation and Operation Manual

4-6. AC-Powered DPS Module, Location of Internal Jumper ........................................................ 4-14 4-7. Module DCL.3 Panels........................................................................................................... 4-15 4-8. Module DCL.3 – RS-232 Interface Board Settings................................................................. 4-18 4-9. Module DCL.3, Main Board Settings .................................................................................... 4-19 4-10. Fan Tray Front Panels ......................................................................................................... 4-21 4-11. Typical Connection to Relay Connectors ............................................................................ 4-25 4-12. DXC-30E Enclosure, Typical Rear View .............................................................................. 4-27 4-13. DXC-30E Enclosure Front Panel.......................................................................................... 4-28 4-14. Attachment of Brackets to DXC-30E ................................................................................... 4-29 4-15. DXC-30ME-PS/AC and DXC-30ME-PS/DC Module Panels.................................................. 4-31 4-16. DPS Modules, Location of Internal Jumper and Fuses ......................................................... 4-32 4-17. Module DCL.3 Panels ........................................................................................................ 4-34 4-18. AC-Powered DXC-10A, Rear View ..................................................................................... 4-37 4-19. DC-Powered DXC-10A, Rear View..................................................................................... 4-38 4-20. DXC-10A Enclosure Front Panel ......................................................................................... 4-38 4-21. Attachment of Brackets to DXC-10A................................................................................... 4-39 4-22. AC-Powered DXC-8R Enclosure, Rear View........................................................................ 4-42 4-23. DC-Powered DXC-8R Enclosure, Rear View ....................................................................... 4-42 4-24. DXC-8R Enclosure Front Panel ........................................................................................... 4-43 4-25. Attachment of Brackets to DXC-8R..................................................................................... 4-44 4-26. DXC-8R DC Power Supply Module, Location of Internal Jumper ........................................ 4-45 7-1. LOCAL LOOP Loopback (T1 and E1 Modules) ..................................................................... 7-10 7-2. REMOTE LOOP Loopback (E1 and T1 Modules) .................................................................. 7-11 7-3. Inband Code-Activated Loopback ........................................................................................ 7-11 7-4. LOOP TS REM Loopback ..................................................................................................... 7-12 7-5. LOCAL LOOP Loopback (DHS Module)............................................................................... 7-13 7-6. REMOTE LOOP Loopback (DHS Module) ............................................................................ 7-13 7-7. LOCAL LOOP Loopback (DIM Module) ............................................................................... 7-14 7-8. REMOTE LOOP Loopback (DIM Module) ............................................................................ 7-14 7-9. Inband Code-Activated Loopback on DIM – Signal Paths during Loopback Activation .......... 7-15 7-10. Inband Code-Activated Loopback on DIM – Signal Paths after Activation of Loopback ....... 7-15 7-11. LOOP L LINE Loopback (Typical DHL Module).................................................................. 7-16 7-12. LOOP L PORT Loopback (Typical DHL Module) ................................................................ 7-17 7-13. HDSL_INBAND Loopback on Remote DXC Unit (Typical DHL Modules)........................... 7-17 7-14. HDSL_INBAND Loopback on Remote Modem .................................................................. 7-18 7-15. Local Loopback Signal Paths............................................................................................... 7-18 7-16. Remote Loopback Signal Paths ........................................................................................... 7-19 7-17. Remote Loopback on Remote ASMi-31.............................................................................. 7-20 7-18. Typical Local Loopback Signal Path .................................................................................... 7-21 7-19. Typical Remote Loopback Signal Paths ............................................................................... 7-21 7-20. Remote Loopback on Remote Unit, Signal Paths ................................................................ 7-22 7-21. Typical Inband Code-Activated Loopback Signal Paths ....................................................... 7-22 7-22. Remote Timeslot Loopback ................................................................................................ 7-23 7-23. Local E3 Loopback (DE3 Modules) ..................................................................................... 7-24 7-24. Remote E3 Loopback (DE3 Modules) ................................................................................. 7-24 7-25. Local Internal E1 Port Loopback (DE3 Modules) ................................................................. 7-25 7-26. Local T3 Loopback (DT3 Modules) ..................................................................................... 7-25 7-27. Remote T3 Loopback (DT3 Modules) ................................................................................. 7-26

Table of Contents

DXC-8R/10A/30/30E Installation and Operation Manual ix

7-28. Local Internal Port Loopback (DT3 Modules) ...................................................................... 7-26 7-29. Local Loopback on External STM-1 Port ............................................................................. 7-27 7-30. Remote Loopback on External STM-1 Port ......................................................................... 7-27 7-31. Local Loopback on Internal E1 Port .................................................................................... 7-28 7-32. Remote Loopback on Internal E1 Port ................................................................................ 7-28 7-33. Local Loopback on Internal VC-12 Port .............................................................................. 7-29 7-34. Latching Network Line Loopback (T1 Module) ................................................................... 7-30 7-35. Network Payload Loopback (T1 Module)............................................................................ 7-31 7-36. BER Testing (DHS and D8HS Modules) .............................................................................. 7-32 7-37. BER Testing (DE1B, DT1B, DHL, D4E1, D8E1, D4T1, D8T1 Modules) ............................... 7-33 7-38. BER Testing (DIM Module) ................................................................................................. 7-33 7-39. BER Test on Remote ASMi-31-2 ......................................................................................... 7-34 7-40. BER Testing (D8SL Module) ................................................................................................ 7-35

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 4-1. DXC Power Supply Output..................................................................................................... 4-4 4-2. Power Consumption of DXC Modules .................................................................................... 4-4 4-3. DXC-30 Front Panel Indicators ............................................................................................. 4-11 4-4. DPS Module Panels .............................................................................................................. 4-13 4-5. DCL.3 Modules Panel Components...................................................................................... 4-16 4-6. Module DCL.3, Main Board User Settings ............................................................................ 4-17 4-7. Fan Tray Front Panel Components........................................................................................ 4-21 4-8. DXC-30E Front Panel Indicators ........................................................................................... 4-28 4-9. PS Module, Panel Components ............................................................................................ 4-30 4-10. DXC-10A Front Panel Indicators ......................................................................................... 4-38 4-11. DXC-8R Front Panel Indicators ........................................................................................... 4-43 5-1. General Command Options ................................................................................................. 5-13 5-2. DXC Command Set Index .................................................................................................... 5-14 6-1. Outline of Configuration Procedures ...................................................................................... 6-1

Table of Contents

x DXC-8R/10A/30/30E Installation and Operation Manual

Overview 1-1

Chapter 1 Introduction

1.1 Overview

Purpose and Use DXC-8R, DXC-10A, DXC-30, and DXC-30E are a family of highly versatile, user-configurable multiservice access nodes with SNMP management, which provide the following main classes of services: • Non-blocking DS0 cross-connect services for T1, E1 (frame and unframed),

n×56/n×64 kbps and ISDN BRI services. • E3 and T3 multiplexing services. • Fractional STM-1 multiplexing services. • Inverse multiplexing capabilities: DXC systems with an inverse multiplexing

subsystem support transparent transmission of high-speed data over up to eight E1 or T1 links (equivalent to user rates up to 15.360 Mbps for E1 lines, or 11.776 Mbps for T1 lines).

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.

E1 and T1 Cross-Connect Service

The DXC family offers user-programmable routing at the level of the individual timeslot, and thus allows connecting any incoming 64 kbps timeslot to any outgoing 64 kbps timeslot. For each timeslot, the user can select between the normal (bidirectional) routing mode, in which both the transmit and receive paths are connected, and a unidirectional mode, that enables to broadcast data transmitted by a source to several destinations.

For timeslots that carry voice channels, E1-to-T1 conversions can also include A-law/µ-law and signaling format conversions.

Chapter 1 Introduction DXC-8R/10A/30/30E Installation and Operation Manual

1-2 Overview

Fractional E1 and T1 Access

The DXC family supports fractional E1 and T1 applications (cross-connection of n×64 kbps and n×56 kbps channels), as well as grooming applications. For these applications, user's data is automatically inserted into E1 or T1 frames using the minimum number of timeslots.

E3 and T3 Multiplexing Service DXC systems can be equipped with E3 or T3 multiplexer modules:

• DXC systems equipped with an E3 multiplexer module enable the multiplexing of up to 16 independent E1 and fractional E1 data streams into one E3 data stream (34.368 Mbps), and grooming of n×64 kbps data, for direct connection over copper or fiber-optic media to E3 networks and E3 equipment ports. The E3 multiplexer modules perform third-order multiplexing using positive justification in accordance with ITU-T Rec. G.751.

• DXC systems equipped with a T3 multiplexer module enable the multiplexing of up to 28 independent DS1 and fractional DS1 data streams into one DS3 data stream (44.736 Mbps), and grooming of n×64 kbps data, for direct connection over copper or fiber-optic media to T3 networks and DS3 equipment ports. The T3 multiplexer modules support two application modes: synchronous M13 (SYNTRAN) and asynchronous C-bit parity multiplex applications in accordance with ANSI T1.107 and ANSI T1.107a.

Fractional STM-1 Multiplexing Service

A DXC system equipped with a fractional STM-1 multiplexer module can be used to provide direct access to the Synchronous Digital Hierarchy (SDH) transmission cores at the STM-1 level (155.520 Mbps).

The fractional STM-1 module operates as a terminal multiplexer (TM) and has a capacity of 30 E1 data streams. Each E1 data stream can be freely routed to any of the 63 TU-12 tributary units carried in the STM-1 data stream.

The dual-port fractional STM-1 module can also serve as an add/drop SDH multiplexer (ADM) for the DXC chassis. The total number of TU-12 tributaries that can be added/dropped to the local DXC bus is up to 30 (out of the maximum of 63 TU-12 carried in a VC-4). All the other tributaries (up to 63) can be bypassed between the two STM-1 interfaces.

DXC equipped with the DFSTM-1 module supports linear ADM topology only. A full SDH ring is not supported.

Inverse Multiplexing Service Inverse multiplexing is a technique that splits a high-speed data stream for parallel transmission over several lower-speed transmission lines. The DXC system can be equipped with the DIM inverse multiplexer module, that provides the high-speed interface for user’s data equipment, and processes the user’s data stream to enable its transmission over E1/E3, T1/T3 or STM-1 links. DXC systems with DIM modules provide high-speed data links at rates up to 11.776 Mbps when operating in T1 or T3 systems, or up to 15.360 Mbps when

Note

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 1 Introduction

Applications 1-3

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.

Management and Power The DXC equipment supports Telnet and SNMP management, both inband through the main links and out-of-band through RS-232 supervisory ports. SNMP enables fully graphical, user-friendly management using the RADview network management stations offered by RAD, as well as management by other SNMP-based management systems. In addition, a supervision terminal that provides full configuration and management capabilities can be connected to the RS-232 supervisory ports, either directly or through modem links. The DXC systems can be powered through AC and DC power supply modules. When necessary, two power supply modules can be installed to provide redundancy (except for the DXC-10A version).

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.

PDH Network Access Application Figure 1-1 shows a typical PDH network access application for DXC systems.

In this application, the DXC system, equipped with one E3 or T3 multiplexer modules, is used to perform the following functions: • Feeder for a T3 or E3 network.

• Provide access to channelized DS3 or E3 ports of higher-order switches in the plesiochronous (PDH) and synchronous (SDH) digital hierarchies.

• Multiplexing and grooming of T1, E1, fractional T1, fractional E1, and n×56 kbps/n×64 kbps data.

• Provide support for transmission of n×T1 or n×E1 inverse multiplexer traffic (when using the DIM inverse multiplexer module).


1-4 Applications

E3 or T3(Copper or

Fiber) DXC

E1/T1

4x"S" Interface (BRI)

n×64kbps

RouterFCD-E1A

DataVoiceISDNLANFrame Relay

T1/E1(Copper, Fiber)

Megaplex-2100

E1/Fractional E1(Copper, Fiber)

Voice Switch

Data Switch

HCD-E1

HDSL 2W/4W

n×64kbps

Router

Fractional T1

n×64kbps n×56kbps

RouterFCD-T1

T1/Fractional T1

128k

(NT)

ASMi-31or

ASM-312-wire Line

(Max 5.5 Km)

DTE

PBX

PBXFractional E1

ISDN “U”Interfaces

...

PDHNetwork

Figure 1-1. Typical DXC System Application – PDH Network Access

SDH Network Access Application Figure 1-2 shows a typical SDH access application for a DXC system equipped with a DFSTM-1 fractional STM-1 module. In this application, the fractional STM-1 module provides a wide bandwidth connection to the SDH transmission core over optical fibers. In this application, the DXC system provides multiplexing and grooming of T1, E1, fractional T1, fractional E1 and n×64 kbps data, and support for transmission of n×T1 or n×E1 inverse multiplexer traffic (when using the DIM inverse multiplexer module).

Applications Requiring Wide Link Bandwidth Figure 1-3 shows another application for a DXC equipped with an E3 or T3 module – providing a wide bandwidth, point-to-point link between two DXC systems. To increase system reliability and availability, two E3 or T3 modules, configured to operate as a redundant pair, can be installed in each DXC unit.

When using E3 or T3 modules with optical interfaces, the maximum range (without repeaters) is up to 70 km.


Physical Description 1-5

DXC withDFSTM-1 ModuleSTM-1

(Copperor Fiber)



MEGAPLEX-2100

Voice Switch Data Switch

HCD-E1

HDSLData

n×64kbps

Router

10/100BaseTEthernet

LAN

Fractional T1

n×64kbps n×56kbps

Router

PBX

FCD-T1

T1/Fractional T1

n×64kbps

Router

Router

HSSIDXC-10A

....

PDHNetwork

STM-N Network

ADM

ADM

ADM

ASMi-31

...

"S" Interface (BRI)

n×64kbps

RouterFCD-E1I

E1/Fractional E1

Figure 1-2. SDH Network Access Application

E3 or T3 (Copper or Fiber)

DXCDXC

Figure 1-3. Typical E3 or T3 Point-to-Point Link

1.3 Physical Description

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.


1-6 Physical Description

DXC-30

DXC-10A

DXC-30E

DXC-8R

Figure 1-4. DXC Enclosures, General View

Any system configuration includes the following subsystems:

• Control subsystem, can include one or two common logic modules, type DCL.3 (except for the DXC-10A, which has only one module). The use of two modules is an option that enhances system availability for critical applications: in case one of the modules fails, the other continues to provide service without any human intervention.

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.



• User interfacing subsystem, consisting of I/O modules. The number of I/O modules that can be installed in a chassis depends on the chassis type.

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 installation

2 (AC internal or DC)

2 4

DXC-10A 1U-high chassis for desktop and rack installation

1 (AC or DC, both

internal)

1 5

DXC-30 3U-high chassis for desktop and rack installation

2 (AC or DC)

2 15

DXC-30E 6U-high chassis for desktop and rack installation

2 (AC or DC)

2 15

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.

Module DCL.3 stores the DXC-30 database in a FLASH DISK. The configuration information stored in the FLASH DISK is downloaded to the module installed in the DXC-30 upon turn-on or after system reset. When redundancy is enabled, the DXC-30 database is automatically copied from the active DCL.3 module to the redundant module.

• One or two power supply modules, type DXC-30M-PS/AC/N or DXC-30M-PS/DC/N (the generic designation DPS module is used when the information is applicable to both module types). Two DPS modules are necessary for the optional redundancy feature: when both modules are operational, they share the load, whereas in case of failure or loss of input power the remaining module continues to supply the power alone. Switch-over is thus automatic and does not disturb normal operation.



• Up to 15 I/O modules (DT1B, DT3, DE1B, DE3, DFSTM-1, DHL/E1, DHL/E1/2W, DIM, DHS, D8U, D8HS, D8SL, D4T1, D8T1, D4E1, or D8E1).

Common LogicModules

15 I/OModules

Power SupplySubsystem

Figure 1-5. DXC-30 Enclosure, General View

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.



Figure 1-6. Fan Tray, General View

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.



Common LogicModules

15 I/OModules


Figure 1-7. DXC-30E Enclosure, General View

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/OModules

Common LogicModule

Figure 1-8. DXC-10A Enclosure, General View

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.

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.

Note



4 I/OModules

Common LogicModules

DC PS Modules(For DC-Powered

Version Only)

Figure 1-9. DXC-8R Enclosure, General View

DXC-8R contains the following main components:

• Control subsystem: this subsystem includes two DCL.3 modules, for redundancy.

• Power supply. In accordance with order, the DXC-8R may be delivered either with AC power supply modules, or with 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 (this is the version shown in Figure 1-9).

The two power supply modules operate in the load sharing mode, and provide redundancy in case of failure (the remaining operational module continues to supply the power alone). Switch-over is thus automatic and does not disrupt normal operation.

• I/O modules. DXC-8R has four I/O module slots, designated I/O1 through I/O4. 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.

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.

Optical interfaces provide a secure link in hazardous or hostile environments, increase the maximum connection range, and provide immunity against electrical interference and protection against the deleterious effects of ground loops.

Optical interfaces are available on the following modules: T1 interface module, DT1B, which comprises two T1 ports with optical

interfaces.

E1 interface module, DE1B, which comprises two E1 ports with optical interfaces.

T3 interface module, DT3, which comprises one T3 port with optical interface.

E3 interface module, DE3, which comprises one E3 port with optical interface.

Fractional STM-1 interface module, DFSTM-1, which comprises one STM-1 port with intra-office, short-haul or long-haul optical interface (a DFSTM-1 version with a second, redundant port is also available).

• HDSL interface modules, DHL/E1 and DHL/E1/2W, based on the DE1B modules. Each of these modules has two High-Bit Rate Digital Subscriber Line



(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


Technical Specifications 1-15

transmission over 2-wire unconditioned lines at ranges up to 5.5 km over 26 AWG wire, and can supply phantom feed voltage to the equipment connected to the remote end of the line from an external DC feed source.

• SHDSL multiport interface module, D8SL, an eight-port I/O module using the single-pair high-speed digital subscriber line (SHDSL) technology in accordance with ITU-T Rec. G.991.2. Each D8SL port is a multirate SHDSL modem supporting user-selectable data rates in the range of 64 kbps (1 timeslot) up to 2048 kbps (32 timeslots).

1.4 Technical Specifications

T1 Electrical Interfaces (DT1B, D4T1, and D8T1 Modules)

General Applicable Standards • AT&T TR-62411, ANSI T1.403

• ITU-T Rec. G.703, G.704

Framing • D4 (SF)

• ESF

• Unframed

Nominal Line Data Rate 1.544 Mbps

Line Code AMI

Zero Suppression • Transparent (no zero suppression)

• B7ZS

• B8ZS

Impedance 100Ω, balanced

Connectors RJ-45 connector per port, or two 25-pin D-type connectors for the D8T1 module

Signal Levels Transmit Levels

Nominal Level ±3V ±10%

Levels with CSU 0 dB, -7.5 dB, -15 dB, -22.5 dB, software-selectable

Levels without CSU Software-adjustable to be measured at 0 to 655 ft

Receive Levels • 0 to -36 dB with CSU

• 0 to -10 dB without CSU

Software-selectable:

Monitoring Mode (D4T1, D8T1 modules only) • 12 dB gain to compensate resistive attenuation

• 20 dB gain to compensate resistive attenuation

Jitter Performance Per AT&T TR-62411


1-16 Technical Specifications

E1 Electrical Interfaces (DE1B, D4E1, and D8E1 Modules)

General Applicable Standards ITU-T Rec. G.703, G.704, G.732

Framing • 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


Line Code HDB3

Line Impedance Selectable by jumpers:

• 120Ω, balanced

• 75Ω, unbalanced

Connectors

Balanced Interface RJ-45 per port, or 25-pin (D8E1 only)

Unbalanced Interface BNC or mini-BNC per port, or two 25-pin D-type connectors for the D8E1

Signal Levels Transmit Levels • Balanced interface: ±3V ±10%

• Unbalanced interface: ±2.37V ±10%

Receive Levels • 0 to -36 dB with LTU

• 0 to -10 dB without LTU

Software-selectable:

Monitoring Mode (D4E1, D8E1 modules only) • 12 dB gain to compensate resistive attenuation

• 30 dB gain to compensate resistive attenuation



T1 Optical Interfaces (DT1B Modules)

General Applicable Standards AT&T TR-62411, ANSI T1.403, ITU-T Rec. G.921, G.956

Framing • D4 (SF)

• ESF

• Unframed


Fiber-Optic Link Interface

Connectors SC, ST or FC/PC, in accordance with order

Performance Refer to Table below

Wavelength (nm)

Fiber Type (µm)

Transmitter Type

Typical Power Coupled into Fiber (dBm)

Receiver Sensitivity (dBm)

Typical Optical Budget (dB)

Typical Maximum Range (km / mi)

850 62.5/125 multimode

LED -18 -38 18 5 / 3

1310 9/125 single-mode

Laser -12 -39 25 62 / 38

1550 9/125 single-mode

Laser -12 -39 25 100 / 62

E1 Optical Interfaces (DE1B Modules)

General Applicable Standards ITU-T Rec. G.704, G.732, G.921, G.956

Framing • Timeslot 0 multiframe for CRC-4 protection, and 16-frame multiframe managed by means of timeslot 16 (G.732S) for use of CAS




• Unframed


Performance Refer to Table given for DT1B module Fiber-Optic Link Interface Connectors SC, ST or FC/PC, in accordance with order



HDSL Interface (DHL/E1 and DHL/E1/2W Modules)

General Number of Ports Two

Line Code 2B1Q

Signal Format • 1168 kbps (584 kbaud) on each of the two pairs

• 1160 kbaud (2320 kbps) on one pair

Transmit Pulse Shape ETSI ETR-152

Equalizer Automatic, adaptive

Transmit Signal Power +13 dBm ±1 dB

Loop Loss 31 dB max. at 150 kHz

Return Loss 16 dB min. in the range of 25 to 317 kHz, relative to 135Ω

T3 Electrical Interfaces (DT3 Modules)

General Function DS3 multiplexer

External Ports One T3 port

Internal Ports 28 DS1 ports

T3 Port Data Rate 44.736 Mbps

Electrical Characteristics Bellcore TR-NWT-000499, GR-253-CORE, ANSI T1.102, and ITU-T Rec. G.703

Framing Options • C-bit parity per ANSI T1.107 and ANSI T1.107a

• Synchronous M13 (SYNTRAN) per ANSI T1.107 and T1.107a

• Complies with DSX-3 requirements per ANSI T1.102

Line Code B3ZS

Line Impedance 75Ω

Pulse Shape Per ANSI T1.102

Connectors Two BNC female connectors

Applicable Standards AT&T TR-62411, ANSI T1.403, and ITU-T Rec. G.704

Framing • D4 (SF)

• ESF

• Unframed

Internal DS1 Ports (DT3)

Nominal Data Rate 1.544 Mbps



Module Timing

T3 Port Timing • Internal timing

• Loopback timing (transmit timing locked to clock recovered from received T3 signal)

Internal Ports Timing • Locked to the DXC master clock

• DXC master clock can be locked to one of the recovered internal DS1 port clock signals

T3 Optical Interfaces (DT3 Modules)

General Function DS3 multiplexer

External Ports One T3 port

Internal Ports 28 DS1 ports

T3 Port Data Rate 44.736 Mbps

Optical Characteristics ITU-T Rec. G.951

Framing Options • C-bit parity per ANSI T1.107 and ANSI T1.107a

• Synchronous M13 (SYNTRAN) per ANSI T1.107 and T1.107a

• Complies with DSX-3 requirements per ANSI T1.102

Connectors SC, ST or FC/PC connectors

Optical Characteristics See Table 1-2

Table 1-2. E3 and T3 Ports, Fiber-Optic Interface Characteristics

Wavelength Fiber Type Transmitter

Type

Power Coupled into Fiber (typical)

Receiver Sensitivity

Optical Budget

Maximum Receiver Input

Power

Receiver Dynamic Range

Typical Maximum

Range

850 nm 62.5/125 µm multimode LED -18 dBm -28 dBm 10 dB –12 dBm 16 db 2.5 km/1.5 mi

62.5/125 µm multimode LED -18 dBm -31 dBm 13 dB –14 dBm 17 db 5.5 km/3.4 mi

1310 nm 9/125 µm single-mode Laser -12 dBm -31 dBm 19 dB –12 dBm 30 db 38 km/23.6 mi

1550 nm 9/125 µm single-mode Laser -12 dBm -31 dBm 19 dB –12 dBm 30 db 68 km/42 mi

Applicable Standards • AT&T TR-62411, ANSI T1.403 • ITU-T Rec. G.704

Internal DS1 Ports (DT3)

Framing • D4 (SF) • ESF • Unframed




Module Timing

T3 Port Timing • Internal timing • Loopback timing (transmit timing locked to clock

recovered from received T3 signal)

Internal Ports Timing • Locked to the DXC master clock • DXC master clock can be locked to one of the

recovered internal DS1 port clock signals

E3 Electrical Interfaces (DE3 Module)

General Function E3 multiplexer

External Ports One E3 port

Internal Ports 16 E1 ports

E3 Port Nominal Data Rate 34.368 Mbps

Electrical Characteristics Per ITU-T Rec. G.703, G.823

Framing Options Per ITU-T Rec. G.751

Line Code HDB3

Line Impedance 75Ω

Pulse Shape ITU-T Rec. G.703

Connectors Two BNC female connectors

Applicable Standards ITU-T Rec. G.751, G.823, and ITU-T Rec. G.704 Internal E1 Ports Framing • Timeslot 0 multiframe for CRC-4 protection, and

16-frame multiframe managed by means of timeslot 16 (G.732S) for use of CAS




• Unframed


Module Timing

E3 Port Timing • Internal timing

• Loopback timing (transmit timing locked to clock recovered from received E3 signal)


• DXC master clock can be locked to one of the recovered internal E1 port clock signals



E3 Optical Interfaces (DE3 Module)

General Function E3 multiplexer

External Ports One E3 port

Internal Ports 16 E1 ports

E3 Port Nominal Data Rate 34.368 Mbps

Characteristics Per ITU-T Rec. G.951

Framing Per ITU-T Rec. G.751

Range See Table 1-2

Connectors ST, SC, or FC/PC

Applicable Standards ITU-T Rec. G.751, G.823, and ITU-T Rec. G.704 Internal E1 Ports Framing • Timeslot 0 multiframe for CRC-4 protection, and





• Unframed


Module Timing

E3 Port Timing • Internal timing

• Loopback timing (transmit timing locked to clock recovered from received E3 signal)



Fractional STM-1 Interfaces (DFSTM-1 Modules)

General Function STM-1 terminal multiplexer

External Ports One STM-1 port or two STM-1 ports with redundancy

Internal Payload Ports 30 E1 ports

Physical Layer ITU-T Rec. G.703, Para. 12

Line Code CMI

Electrical STM-1 Port

Bit Rate 155.520 Mbps ± 4.6 ppm



Physical Layer ITU-T Rec. G.957

Bit Rate 155.520 Mbps ± 4.6 ppm

Range See Table 1-3

Optical STM-1 Port

Connectors ST, SC, or FC/PC

Table 1-3. Optical STM-1 Port, Fiber-Optic Interface Characteristics

Wavelength Fiber Type Transmitter

Type Power Coupled

into Fiber Receiver

Sensitivity Optical Budget

Maximum Receiver Input

Power

Receiver Dynamic

Range

Typical Maximum

Range (km/mi)

1310 nm 9/125 µm single-mode

Laser -12 dBm -31 dBm 19 dB -12 dBm 30 dB 20/12.4

1550 nm 9/125 µm single-mode

Laser -12 dBm -31 dBm 19 dB -12 dBm 30 dB 20/12.4

Applicable Standards ITU-T Rec. G.732, G.823 and ITU-T Rec. G.704 Internal E1 Ports Framing Options • Timeslot 0 multiframe for CRC-4 protection, and





• Unframed


Module Timing

STM-1 Port Timing • System timing (transmit timing locked to DXC 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



Indicators L LOS (red) Local loss of STM-1 signal

R LOS (red) Remote loss of STM-1 signal



Timeslot Allocation

User-defined mapping, any timeslot to any timeslot

Routing of E1 Ports to TU-12s

User-defined mapping, any E1 port to any TU-12

Configuration Programmable via DXC management

ISDN “U” Interfaces (D8U and D16U Modules)

General Number of Ports

D8U

D16U

8 “U” ports

16 “U” ports

Compliance ITU-T Rec. G.961

Nominal Line Rate 160 kbps (ISDN basic rate access, 2B+D channels)

Line Signal Format 2B1Q

Transmission Format Full duplex

Line Type 2-wire unconditioned telephone loops (one twisted pair)

Nominal Line Impedance 135Ω

Transmit Level +13 dBm

Maximum Loop Loss 42 dB at 40 kHz, maximum resistance 1300Ω

Typical Range 5.5 km (3.4 miles) over 26 AWG (0.4 mm) pair

Connector 25-pin D-type female connector per group of eight ports

Port Timing • Transmit clock locked to the DXC nodal timing

• Receive clock recovered from line signal

Phantom Feeding

96 VDC provided by external source connected to the module connector, can be individually enabled/disabled for each module port

/I Configuration • 64 kbps on each B channel

• 16 kbps on each D channel Port Payload Rate

/1 Configuration 64 or 128 kbps



Diagnostics (per port)

Loopbacks • Local loopback

• Remote loopback

• Local loopbacks on the individual channels of a port

• Remote loopback on ASMi-31 (activated through the download channel by an /1 port)

BER testing BER testing on ASMi-31 (activated through the download channel by a /1 port)

SYNC LOSS (red) Lights up upon loss of synchronization Indicators (per port) TEST (yellow) Lights up when a loopback is active

Configuration • Programmable by the DXC system management

• Downloading from /1 port to ASMi-31

SHDSL Interfaces (D8SL Module)

General Function Multi-port I/O module

Number of Ports 8

External Ports Port Interface Type SHDSL

Applicable Standards ITU-T Rec. G.991.2

Line Type Single unloaded and unconditioned copper twisted pair

Nominal Line Impedance

135Ω

Range See Table 1-1.

Line Connector 25-pin D-type female connector for all the ports

Internal E1 Ports

Framing Options • G.732N

• G.732S

• Unframed

Applicable Standards ITU-T Rec. G.704, G.732

Timing Port Timing Locked to the DXC master clock

Diagnostics Loopbacks • User-activated local and remote loopback on each port

• Remote loopback activation by inband FT1 code (on all timeslots, or on specific timeslots)

• User-activated remote loopback on remote unit



BER Testing on each Port

Performance Monitoring

In accordance with ITU-T Rec. G.991.2

Indicators (per port)

TST Yellow, lights when a test is active on the port

SYNC LOSS • Lights steadily in red when the D8SL port is not synchronized to the remote unit

• Flashes in red during handshaking between the D8SL port and the remote unit

• Flashes in green during the synchronization process between the D8SL port and the remote unit

• Lights in green when the D8SL port is synchronized to the remote unit

Timeslot Routing

User-defined, any timeslot to any timeslot mapping

Physical Occupies a single DXC module slot

Power Consumption

18.5W at maximum data rate on all the ports

Configuration Programmable via DXC management

Table 1-4. Typical Ranges over 24 AWG and 26 AWG Lines

Data Rate 24 AWG 26 AWG

[kbps] [km] [miles] [km] [miles]

64 10.0 6.2 7.1 4.4

128 10.0 6.2 7.1 4.4

256 9.0 5.5 7.1 4.4

512 7.7 4.7 5.9 3.6

768 7.0 4.3 5.6 3.5

1024 6.2 3.8 4.4 2.7

1536 4.7 2.9 3.9 2.4

2048 4.0 2.4 3.5 2.1

Typical ranges are based on the error-free real-line laboratory tests without noise.

Note



Inverse Multiplexer (DIM Module)

General Number of Links Up to 8 T1 or E1 links, each routed to any desired E1 or T1 port

Maximum Differential Delay between Links

64 msec

Latency Equal to highest actual differential delay between links

User Port • V.35 Interface

• X.21 Interface

• HSSI Interface

• RS-530 Interface

• E1 Interface

• 10/100BaseT Ethernet bridge with VLAN support

• 10BaseT IP router

Data Rates Modules with HSSI, V.35, X.21, RS-530, Ethernet Bridge and IP Router User Ports

• Any multiple of 1.92 Mbps, up to 15.360 Mbps over E1 links

• Any multiple of 1.472 Mbps up to 11.776 Mbps over T1 links

• Automatic fallback to the next lower rate when a link fails

Modules with E1 User Port

2.048 Mbps over two T1 links in accordance with AT&T TR 54019

V.35 Ports 25-pin D-type female connector, and adapter cable terminated in 34-pin female connector

User Port Connector

X.21 Ports 15-pin D-type connector

RS-530 Ports 25-pin D-type female connector

HSSI Ports 50-pin SCSI-2 female connector

E1 Ports RJ-45 connector or two BNC connectors

Ethernet Ports RJ-45 shielded connector

Timing Modes Modules with V.35, X.21, RS-530 and HSSI User Ports

• DCE - supplies transmit and receive clocks to the user

• EXT_DCE - supplies receive clock to the user and accepts an external transmit clock from the user

• SMOOTH - same as DCE, except that a smooth receive clock waveform is provided

• EXT_SMOOTH - same as EXT_DCE, except that a smooth receive clock waveform is provided.

Modules with E1 User Port

• Receive clock: recovered from incoming E1 signal

• Transmit clock source: locked to the DXC nodal clock



E1 Port Same as DE1B ports

Standards IEEE.802.3/Ethernet V2 Ethernet Bridge Port Interface Type 10/100BaseT, half-duplex or full-duplex

(user-selectable)

LAN Table Size 512 MAC addresses

Buffer Size 85 frames

Filtering Rate 150,000 pps

Forwarding Rate 150,000 pps

Line Code • Manchester (10BaseT)

• MLT3 (100BaseT)

Ethernet Router Port

Standard Conforms to IEEE 802.3/Ethernet v2

Local IP Net Capacity Supports up to 256 hosts on the local LAN IP net

Data Rate 10 Mbps

Filtering Rate 35,000 packets per second

Forwarding Rate 30,000 packets per second

Buffer 256 frames (maximum size – 1534 bytes)

Delay 1 frame

Protocols • PPP (PAP/CHAP)

• Frame Relay (RFC 1490)

• HDLC-like framing

Operation Mode Full duplex or half duplex user-selectable

Configuration Telnet, through the 10BaseT interface

System Characteristics

Timeslot Mapping

Routing Capabilities • Any timeslot to any timeslot

• With/without A-law/µ-law and signaling conversion, selectable per timeslot

Routing Modes • Bi-directional (normal) mode

• Unidirectional mode

System Clock Sources

Main Source (software-selectable)

• Internal oscillator (accuracy: ±32 ppm)

• Locked to the receive clock of any port

• Locked to an external (station) clock source (2.048 MHz or 1.544 MHz, user-selectable)



Fallback Source (software-selectable)

• Locked to the receive clock of any port

• Locked to the external (station) clock

Elastic Buffer Buffer Length ±1 frame

Buffer Underflow 1 frame repeated without frame sync loss

Buffer Overflow 1 frame skipped without frame sync loss

Data Delay • T1 Ports: Up to 5 frames (625 µsec)

• E1 Ports: Up to 3 frames (375 µsec)

Unused Timeslot Code

Software-selectable, 00 to FF (hexa)

OOS Timeslot Code

Software-selectable, 00 to FF (hexa), separately for voice and data timeslots

Diagnostics Loopbacks • User-activated local (analog) E1 or T1 loopback

• User-activated remote (digital) E1 or T1 loopback

• Code-activated network loopbacks per ANSI T1.403 (T1 interfaces only)

• Inband code-activated loopback per ANSI T1E1.2/93-003

• User-activated E3, T3, STM-1 local and remote loopbacks

• User-activated local and remote loopbacks on each internal E1 port

• User-activated local loopbacks on each VC-12 port

BER Testing Built-in BERT on all external E1, T1, DHS and DIM ports

Statistics E1 CRC-4 Diagnostics • Per ITU-T Rec. G.706; RFC 1406, 1407

• Local support equivalent to AT&T 54016

T1 ESF Diagnostics • Full support according to ANSI T1.403

• Local support according to AT&T 54016 and RFC 1406

• Transparent transfer of the FDL between two T1 ports (software-selectable)

E3 diagnostics RFC 1407

T3 diagnostics RFC 1407, ANSI T1 107, ANSI T1 107a

STM-1 diagnostics RFC 2258

Redundancy • Two power supplies (DXC-8R, DXC-30, and DXC-30E only)

• Two common logic modules (DXC-8R, DXC-30, and DXC-30E only)



• Line, hardware or combined redundancy for E1, T1, E3, and T3 I/O modules

• Line hardware redundancy for dual-port DFSTM-1 modules

Indicators Major alarm

Minor alarm

Test active

On-line DCL.3 module (DXC-8R/DXC-30/DXC-30E only)

On-line DPS module (DXC-30/DXC-30E only)

Alarm Output Floating normally-open and normally-closed (software-configurable) contacts with common reference, activated in case of major alarm

Interface V.24/RS-232, asynchronous, DCE or DTE (selectable by internal switches and software)

Connector 9-pin D-type female connector

Data Rate 300, 1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps, with automatic detection of data rate (Autobaud)

Supported Protocols • Supervision terminal • SLIP or PPP protocols (supported only for DCE

interface)

CONTROL Serial Port

Routing Protocols RAD proprietary routing and RIP2 protocols

Interface V.24/RS-232, asynchronous, DCE or DTE (selectable by internal switches)

Connector 9-pin D-type female connector

MNG Serial Port

Data Rate Same as CONTROL port (no Autobaud support)

Dial-out Mode Hayes-compatible protocol for auto-answer modem (supported only for DTE interface)

Layer II Protocols SLIP or PPP protocols (supported only for DCE interface)


Interface 10/100BaseT

Connector RJ-45 connector

Layer II Protocol MAC

Ethernet Port


Electrical Interfaces G.703 or RS-422, software-selectable

Nominal Line Data Rate 2,048 Mbps or 1,544 Mbps, software-selectable

Station Clock Port

Line Impedance Selectable by jumpers:

• 120Ω, balanced

• 75Ω, unbalanced



Signal Level 0 to -10 dB

Connectors

Balanced Interface RJ-45 per port

Unbalanced Interface BNC

SNMP or Telnet inband and out-of-band management

Inband Management • Frame relay, PPP, or proprietary protocol in dedicated timeslot

• F-bit (FDL) for T1 lines with ESF framing • Sa bits for E1 lines • eoc management for HDSL and SHDSL interfaces

Network Management

Out-of-band Management

• SLIP or PPP via serial ports • MAC via Ethernet port

Power DXC-8R • 100 to 240 VAC, 50/60 Hz, 60W

• -48 VDC (-40 VDC to -60 VDC), 72W

DXC-10A • 100 to 240 VAC, 50/60 Hz, 60W

• -48 VDC (-40 VDC to -60 VDC), 75W

DXC-30 • 100 to 240 VAC, 50/60 Hz, 120W • -48 VDC (-40 VDC to -60 VDC), 120W

DXC-30E • 100 to 240 VAC, 50/60 Hz, 188W • -48 VDC (-40 VDC to -60 VDC), 185W

Physical Characteristics DXC-10A/DXC-8R DXC-30 DXC-30E

Height 4.4 cm/1.7 in (1U) 13.2 cm/5.25 in (3U)

26.6 cm/10.5 in (6U)

Width 44 cm/17.3 in 44 cm/17.3 in 43.8 cm/17 in

Depth 25.4 cm/10 in 25.4 cm/10 in 25.4 cm/10 in

Weight (fully equipped enclosure)

Max 2.5 kg/5.5 lb Max 8 kg/17.6 lb Max 16 kg/35.2 lb

Environment Operating Temperature

DXC-30, DXC-30E: 0 to +45°C (32 to 113°F)

DXC-8R, DXC-10A: 0 to +50°C (32 to 122°F)

Relative Humidity Up to 90%, non-condensing

Introduction 2-1

Chapter 2 System Application Considerations

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.

Chapter 2 System Application Considerations DXC-8R/10A/30/30E Installation and Operation Manual

2-2 Available Services

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.

2.2 Available Services

The timeslot routing capabilities described above enable DXC systems to perform various services, depending on the types of port interfaces being connected to the unit. Note that the routing between the various ports of the modules installed in the DXC system can be freely selected, thus the DXC system may simultaneously provide different services between different ports. • Connection between T1 and E1 ports: when timeslots are connected

between a T1 port and an E1 port, the DXC system operates as a T1-to-E1 converter, and can also provide digital cross-connect functions.

The cross-connect function also includes internal E1 and T1 ports of E3, T3 and fractional STM-1 modules. The DXC system can also support ITU-T Rec. G.802, Annex 2. For this purpose, the DXC system can be programmed to insert the F-bit of the T1 data stream in the most significant bit position of a separate timeslot. The user can connect this timeslot, if desired, to any timeslot of the E1 data stream. The DXC system can either transfer the data carried in connected timeslots transparently, or perform the signaling conversion required for the transfer of voice channels in compliance with the applicable T1 and E1 (CEPT) standards, for example, conversion from E1 CAS format to T1 robbed-bit signaling. DXC can also perform A-law/µ-law conversion in cross-connect applications. The user can specify for each individual timeslot whether it is to be handled as a data channel or as a voice channel. For voice channels, the DXC system can also transfer the signaling information of each channel while performing any necessary signaling conversions. In addition, the user can select whether to transfer the A and B channel signaling bits transparently, or to invert them, for compatibility with RAD Megaplex systems. Note however that signaling conversion is not available for connections between internal ports of E3 and T3 modules.

• Connection between ports of the same type (either two E1 ports, or two T1 ports, including internal E1 or T1 ports of E3, T3 or fractional STM-1 modules): in this case, the DXC system can either transmit transparently the E1 or T1 data stream, or operate as a digital cross-connect system (DCS).

In certain applications, it is necessary to enable the transparent transmission of the FDL between two T1 ports operating with ESF framing. The DT1B modules also support this option (note however that the FDL cannot be transparently transferred between ports located on different modules). The transparent transfer of the FDL can be enabled or disabled by the user. In addition to the basic DCS function, a DXC system connecting between two ports with the same type of interfaces can also be used to modify framing patterns. For example:

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 2 System Application Considerations

Available Services 2-3

A DXC system connecting between two T1 ports can perform conversion between D4 (SF) framing to ESF framing.

A DXC system connecting between two E1 ports can perform conversion between framing per ITU-T Rec. G.704 without CRC-4, to framing with CRC-4.

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.


2-4 T1/E1 Converter

2.3 T1/E1 Converter

DXC systems can be used as user-configurable T1/E1 converters. A typical system configuration is shown in Figure 2-1.

DXC Unit

DXC Unit

E1Network

T1Network

TE ST

MAJO R A LA RM

MIN O R ALA RMSY STE M

PO WE R SU PP LYC OMMO N LO G ICB A

O N LI NE O N LI NEB A

TE ST

MAJO R A LA RM




Figure 2-1. Typical T1/E1 Converter Applications

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.

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.

In addition to A-law/µ-law conversion, the DXC system can also perform conversion of the signaling formats. Signaling conversion is performed when robbed-bit signaling is used on the T1 trunk: the signaling information carried by the “robbed bits” in the T1 frame is converted, in accordance with user's

Note


Media Converter 2-5

selection, to channel-associated signaling (CAS) on the E1 trunk, and vice versa. The CAS information is inserted in timeslot 16, and therefore G732S framing is always used. Since timeslot 16 must be reserved for CAS, it is not cross-connected between the E1 and T1 trunks.

When CCS signaling is used, e.g., in ISDN PRI access applications, the E1 framing mode is G732N, and robbed-bit signaling is disabled on the T1 side. Thus, A-law/µ-law conversion can be performed on voice timeslots, and timeslot 16 of the E1 frame must be transferred to the T1 side, to continue the signaling path.

The processing of the payload data and signaling information is controlled by the user at the level of the individual timeslots. For this purpose, four types of timeslots are supported by the DXC system equipment:

• Data: channel data is transparently transferred (no A-law/µ-law conversion).

• Voice: A-law/µ-law conversion per ITU-T Rec. G.711 is performed on the channel data. In addition, signaling format conversion is also performed as explained above, as a function of the signaling formats selected on the two trunks.

• Voice-MP: this mode is similar to the regular voice mode, except that the DXC system does not invert the A and B signaling bits.

• Management: timeslot dedicated to inband management traffic.

2.4 Media Converter

DXC systems can be equipped with I/O modules having optical interfaces for operation over many types of fiber-optic media, as well as with modules having electrical interfaces for operation over copper media.

For example, at the E1 and T1 level, a DXC chassis can include DE1B and/or DT1B modules with optical interfaces, DE1B and/or DT1B modules with electrical G.703 interfaces, and DHL/E1, DHL/E1/2W modules with electrical HDSL interfaces.

Similar flexibility with respect to the selection of the interface type (electrical or optical) is also available for the higher-rate (E3, T3 and STM-1) modules.

The functional characteristics of fiber-optic and electrical I/O modules are identical, and both types are capable of supporting the same services. Therefore, in addition to their main function (cross-connect), DXC systems can also perform media conversion. A typical application of this type is shown in Figure 2-2.


2-6 Transport of T1 Frames over E1 and E3 Transmission Facilities

DXC Unit

T1 and E1 onCopper Media

T1 and E1 onFiber-Optic

Media Figure 2-2. Typical Media Converter Application

2.5 Transport of T1 Frames over E1 and E3 Transmission Facilities

The DXC system allows the transport of a T1 frame across E1 or E3 transmission facilities. This function can be performed as shown in Figure 2-3.

In transport applications, it is necessary to transfer the T1 trunk data, including the F-bit, transparently without any conversion from end to end, therefore the T1 frames must be processed in accordance with ITU-T Rec. G.802.

TE ST

MAJO R A LA RM




TE ST

MAJO R A LA RM




E1 or E3Transmission

Network

DXC Unit

T1

T1

E1 or E3

DXC Unit

E1 or E3MUX

MUX

Figure 2-3. Typical T1 Transport Application


Fractional T1 and E1 Access Point 2-7

2.6 Channel Relocation and Digital Cross-Connect Applications

In channel relocation and digital cross-connect system applications, the channels of a T1 and/or E1 trunk are moved from one timeslot to another, in accordance with user's programming. These capabilities are available in addition to the other capabilities described in the previous sections.

The channel relocation and digital cross-connect services can be performed between dissimilar trunks, e.g., between E1 and T1 trunks, or between similar links, e.g., between two E1 trunks or between two T1 trunks. The DXC system will also perform, when required, the conversion of the signaling formats (i.e., will convert robbed-bit signaling to CEPT channel-associated signaling), and will move the channel signaling information to the appropriate location in the signaling frame, in parallel with the change in channel numbers. Additionally, the digital cross-connect services can be performed between the nx64 kbps ports and E1/T1 trunks.

DXC systems can also perform A-law/µ-law conversion.

When the DXC is equipped with an E3, T3 or fractional STM-1 module, the same functions are also available between external E1 and T1 ports and internal E1 or T1 ports of that module, except that the A-law/µ-law conversion and the rearranging of the channel signaling information are not supported for connections to E3 and T3 modules.

The fractional STM-1 modules do not support grooming of E3 and T3 data streams.

2.7 Fractional T1 and E1 Access Point

The DXC system can be used to provide an access point for fractional T1 and E1 services, as a replacement for dedicated fractional CSU/DSU units.

For this service, the DXC system must include a DHS module that connects to the user's equipment. The DHS module supports connection at rates of n×56 kbps or n×64 kbps, where n = 1 to 31 (56 to 1736 kbps, or 64 to 1984 kbps, respectively). The user's data stream is then routed to the desired timeslots of a selected E1 or T1 port.

A basic application is shown in Figure 2-4.

DXC Unit

E1/T1Network

TE ST

MAJO R A LA RM




Figure 2-4. Typical Fractional T1/E1 Access Point Application

Note


2-8 Multidrop (Broadcast) Applications

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.

2.8 T1/E1 Drop-&-Insert

In a drop-&-insert application, channels from a trunk connecting two locations are dropped at an intermediate location.

In the basic application shown in Figure 2-5, some of the channels of trunk A are routed to trunk B, and others are routed to trunk C. Similarly, some of the channels of trunk B are routed to trunk C. This arrangement can be extended to any desired number of trunks.

2.9 Multidrop (Broadcast) Applications

The multidrop (or broadcast) feature enables a user at a central location to send data to multiple users connected to remote units (simplex communication), and still maintain normal communication with another user. Figure 2-6 shows a basic multidrop application.

The multidrop capability is achieved by separating the handling of the receive and transmit paths in the timeslot switching matrix of the DXC system: this matrix mode is called unidirectional mode, in contrast to the normal bidirectional mode, in which the DXC system automatically connects the transmit and receive paths between the same pair of ports, without user’s intervention.

In the basic application shown in Figure 2-6, port A communicates full-duplex with port B. In addition, user-selected timeslots (channels) of port A are routed to the receive paths of ports C and D. This arrangement can be extended to any desired number of ports. Note that the connection to the additional ports is a simplex connection, that is, additional ports can receive the data carried by the user-selected timeslots transmitted by the port designated as source, but cannot transmit data to the source port (the source port can only receive data from the port designated as its destination).


HDSL Transmission Applications 2-9

DXC Unit

LOCATION A

UsersConnected toLocation BUsersConnected toLocation C

UsersConnected toLocation BUsersConnected toLocation A

LOCATION C

LOCATION B

Users Connected toLocation A

Users Connected toLocation C

Figure 2-5. Typical Drop-&-Insert Application

Connected toLocation B

LOCATION B

Connected toLocation A

PortA

PortC

PortD

PortB

DXC Unit

LOCATION A

LOCATION C

ReceivesLocation A

ReceivesLocation A

LOCATION D Figure 2-6. Typical Multidrop Application

2.10 HDSL Transmission Applications

HDSL transmission provides significant savings in infrastructure costs because it uses unconditioned twisted-pairs. Another advantage of HDSL transmission is that equipment can be easily relocated, as the only transmission infrastructure requirement is to find enough free pairs to connect the equipment at its new location.

HDSL transmission is supported by the DHL/E1 and DHL/E1/2W modules, which provide services similar to the DE1B modules. Each DHL module has two High-Bit


2-10 ISDN “U” Interface Applications

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

PABX

Router

PABX

E1

n x 64 kbps

HCD-E1

HDSL4-wire

HTU-E1

HTU-2

DHL DE1

DXC

E1E1

E3

n x 64 kbpsRouter

Megaplex -2100

DataVoiceISDNLAN

FrameRelay

E1 HDSL4-wire

HDSL4-wire

HDSL4-wire

E1Network

SDHNetwork

Figure 2-7. Typical HDSL Transmission Application

2.11 ISDN “U” Interface Applications

The ISDN digital subscriber line (IDSL) technology offers a cost-effective and reliable solution for delivering service at up to 128 kbps (the ISDN basic rate access – BRI) to customer’s premises over the existing copper infrastructure.

The ISDN BRI is provided over ISDN “U” interfaces. For DXC systems, “U” interfaces are available on the D8U and D16U modules. The D8U/D16U modules support two main types of applications:

• Extension of ISDN lines to remote subscribers over non-ISDN facilities. This application is supported by the operation mode called /I

• Support for leased lines and the RAD ASM-31/ASMi-31/ASMi-31-2 family of short-range modems. This application is supported by the operation mode called /1.


ISDN “U” Interface Applications 2-11

/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.

DXC

ISDN (Voice)Switch

"U" Interfaces

E3 or T3

Network

Data Switch

"S" Interface (BRI)

RouterFCD-E1A

ISDN "U"Ports

(Copper, Fiber)

Megaplex

Router

E1/Fractional E1

LANFrame Relay

Data

PABX

HCD-E1/2W

HDSLData

Router

E1 or T1

n×1.920 Mbpsor

n×1.472 Mbps(n = 1, 2, ..., 8)

n×64kbps

n×64kbps

Figure 2-8. Typical Application of D8U/D16U Modules Operating in the /I Mode

When operating in the /I mode, the D8U/D16U modules provide 8, respectively 16 independent “U” ISDN basic rate access interfaces (ports). The ports can be configured to operate as LT (line termination) or NT (network termination). Each “U” interface carries two B (64 kbps) channels and one D (16 kbps) channel. Each B channel can be independently connected to any timeslot of any DXC link, and operates independently.

In this application, the D8U/D16U module ports (configured to operate in the NT mode) are connected directly to the ISDN voice switch. The D8U/D16U module transfers the data transparently in the 2B + D channels, and therefore operates independently of the ISDN switch in use.

The data streams generated by the D8U/D16U ports are routed to the desired timeslots in one of the E1 or T1 links connected to a Megaplex-2100. The Megaplex-2100 is equipped with HS-U modules, whose ports are configured to operate in the LT mode. These ports are connected directly to the “U” interfaces of a PBX, which gets direct access to the ISDN switch through the Megaplex-2100 link.

/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.


2-12 High-Density Module Applications

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).

E3 or T3

DXC

TransmissionNetwork

Data Switch

2-wire Line(Max 5.5 Km)

2-wire Line(Max 5.5 Km) (NT)

(NT)

64k

128k

ASMi-31or

ASM-31

ASMi-31or

ASM-31


2-wire Line

(NT)

64k

128k

ASMi-31or

ASM-31

ASMi-31or

ASM-31

...

DTE

DTE


2-wire Line(Max 5.5 Km) (NT)

(NT)

64k

128k

ASMi-31or

ASM-31

ASMi-31or

ASM-31


2-wire Line

(NT)

64k

128k

ASMi-31or

ASM-31

ASMi-31or

ASM-31

...

DTE

DTE

Figure 2-9. Typical Application of D8U/D16U Modules Operating in the /1 Mode

2.12 High-Density Module Applications

The high-density (multi-port) DXC modules (D4E1, D8E1, D4T1, D8T1, D8HS) provide most of the functions available on the other types of similar interface modules, such as DE1B, DT1B, or DHS. The main advantage of the multi-port modules is the large number of ports available on each module, which makes possible new applications.

Figure 2-10 shows a typical application that utilizes the large number of links that are supported by a DXC-30 chassis equipped with D8E1 modules: a DXC-30 chassis equipped with 14 D8E1 modules and one DE3 module can be used to groom up to 112 fractional E1 links into one E3 link, all this within a 3U-high enclosure which also includes redundant power supplies and redundant common logic modules.

This capability enables the DXC-30 system to serve as the feeder for an E3 network, or to access channelized E3 ports of higher-order switches in the plesiochronous (PDH) and synchronous (SDH) digital hierarchies.

Similar applications can be built with DT3 or DFSTM-1 as an uplink module.


High-Density Module Applications 2-13

DXC-30

14 D8E1Modules DE3

Module

E1 orFractional E1

Links

1

112

E3Network

.......

....

2

111

Figure 2-10. Typical High-Density Grooming Application for DXC-30

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.

T1TransportNetwork

E1 orFractional E1

Links

1

........

2

2423

D8E1Modules

DXC-8R

...1

8T1 Links

D8T1Module

PS

-BP

S-A

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.

E1 orFractional E1

Links

1

........

2

1615

DXC-10A

DE3Module

E3Network

E3 LinkD8E1Modules

Figure 2-12. E3 Multiplexer Application for DXC-10A

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.


2-14 High-Density Module Applications

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.

D8T1

DXC-8R

D8E1 ModulesSecurity

Fraud Detection

Billing

E1 Links1

31

Figure 2-13. Signaling Monitoring Application

The 8-port D8HS module provides additional applications to the DXC system, such as the one shown in Figure 2-14.

FCD-E1/FCD-T1

n x 56/64 kbps

FCD-IP

n x 56/64 kbps DXC

Up to 16 DFSTM-1 STM-1

E1/T1 FE1/FT1

FE1/FT1

SHDSL

D8HSD8HS

DXC

D8E1D8SL

DHS

Central Office POP

SDHNetwork

RADview ManagementStation

PBX

ASMi-52

Figure 2-14. High-Density High Speed Data Application

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.

Note


SHDSL Transmission Applications 2-15

2.13 M13/T3 Multiplexing Applications

The high port density of the D4T1, D8T1, D4E1 and D8E1 modules allows another important application: M13 multiplexing.

Figure 2-15 shows a 1U-high DXC-10A chassis used as a T3 multiplexer: for this purpose, the DXC-10A chassis is equipped with one DT3 module which provides the T3 link. The required number of T1 ports (28) is provided by installing in the DXC-10A chassis three D8T1 modules and one D4T1 module.

T1 orFractional T1

Links

1

...

........

2

2827

DXC-10A

T3NetworkT3 Link

D8T1Modules

D4T1Module

DT3Module

Figure 2-15. T3 Multiplexer Application for DXC-10A

2.14 SHDSL Transmission Applications

D8SL modules provide all the cross-connect services available on the other types of DXC modules with E1 ports, such as DE1B, D4E1 and D8E1. D8SL modules have three main advantages:

• The large number of ports available on each module

• The capability of providing cost-effective connections to equipment on the customer’s premises: typical ranges are 5.5 km (3.4 miles) over one 24 AWG unloaded pair at 2.048 Mbps, increasing to 7.5 km (4.6 miles) at 192 kbps

• Support for remote management of ASMi-52 modems, and other types of RAD equipment.

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.


2-16 Access to SDH Transmission Core

PABX

Central Office

Customers’ Premises

FCD-IP

ASMi-52

ASMi-52

ASMi-52

LAN

Standard HT

DXC-10A

ManagementStation

DXC-30E1, E3

orFSTM-1

SHDSL

SHDSL

SHDSL

SHDSL

SHDSL

V35/E1

E1

X.21

SubE1

BackboneNetwork

E1, E3 or

FSTM-1

POP

Figure 2-16. Typical D8SL Application

Considering the maximum number of timeslots supported by a DXC unit (960), each DXC-10A or DXC-8R unit can be equipped with up to three D8SL modules, each capable of connecting to eight independent end users located at distances of a few kilometers using just one pair per customer. Thus, up to 24 fractional E1 links are delivered from the POP, all this within a 1U-high enclosure which may also include redundant power supplies and redundant common logic modules.

Moreover, the D8SL module supports remote management of ASMi-52 or FCD-IP units installed on the customer’s premises, thereby enabling the service provider to fully control the remote equipment using the same network management station that controls the DXC equipment.

2.15 Access to SDH Transmission Core

DXC systems equipped with DFSTM-1 modules can serve as an SDH fractional terminal multiplexer, which can be used to provide direct access to the SDH network (see Figure 1-3).

DXC systems located at remote access nodes and serving as feeders can also use the DFSTM-1 module to provide direct STM-1 links to the SDH transmission network, as shown in Figure 2-17. The SDH network can provide the connectivity needed to interconnect the remote access nodes (daisy-chain configuration) , and/or to access higher-order digital switches in the synchronous (SDH) and plesiochronous (PDH) hierarchies.


Typical Multiservice Access Node Application 2-17

DXC with Dual-PortDSTM-1 Module

STM-1 Link

STM-1 Link

ADM

SDH Network

E1 E1

Multiplexers

E1

Remote Access Node

ADM

ADM

ADM

STM-1 Link

ADM

E1 E1

Multiplexers

DXC withDSTM1 Module

Remote Access Node

DXC withDSTM-1 Module

Remote Access Node

Figure 2-17. Fractional SDH Terminal Multiplexer Application for Remote Access Nodes

The routing flexibility needed in remote access applications is provided by the internal routing capabilities of the DFSTM-1 modules. To enhance availability, redundant links can be used by installing the dual-link module version, DFSTM-1, in the DXC systems. Dual-link DFSTM-1 modules also enable linear ADM applications, as shown in Figure 2-17.

2.16 Typical Multiservice Access Node Application

Figure 2-18 shows a system application that utilizes the wide range of services provided by DXC systems.


2-18 Typical Multiservice Access Node Application

E3 or T3(Copper or

Fiber) DXC

E1/T1



Megaplex-2100

Voice Switch

Data Switch

FCD-IP

SHDSL

Fractional E1

n x 64kbps

Router

Network

Fractional T1

n × 64kbpsn × 56kbps

Router

PBX

FCD-T1

T1/Fractional T1

64 kbps

RouterASMi-31IDSL

4 x "S" Interface (BRI)

n × 64kbps

RouterFCD-E1I

E1/Fractional E1

2W

128 kbps

Figure 2-18. Multiservice Access Node Application

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.


Inverse Multiplexing Applications 2-19

2.17 Inverse Multiplexing Applications

DXC systems can also be used in inverse multiplexing applications.

Figure 2-19 shows a typical application, in which a DXC system is used to interconnect two routers through a high-speed link, capable of transporting payload data at rates up to 15.360 Mbps.

8 E1Lines

Inverse Multiplexer Subsystem(DIM & D8E1 Module)

Router

Fast Ethernet

8 E1Lines

DXC

Network

Up to15.360 Mbps

HSSI

Router Up to

15.360 Mbps

Fast Ethernet

DXC

HSSI

Figure 2-19. Basic Inverse Multiplexing System Application

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).

Network

4 E1Lines

Inverse Multiplexer Subsystem(DIM & 2 DE1B Modules) Fast Ethernet

4 E1 or E3or STM-1

IMX-4E1

DXC

Router

Fast Ethernet

ISDN Switch

V.35 or10/100BaseT

V.35

Router

Figure 2-20. Direct Connection to Standalone Inverse Multiplexers


2-20 Inverse Multiplexing Applications

The DXC inverse multiplexer subsystem also allows to transport an E1 frame across T1 transmission facilities. This application is shown in Figure 2-21.

TransportNetwork

2 T1 Lines

DIM and DT1B orDT3 Module

2 T1 Linesor

T3 Line

IMX-2T1/E1

DXC

PBX

PBX

E1

E1

Figure 2-21. Transport of E1 Frame across T1 or T3 Transmission Facilities

For E1 transport applications, DIM modules with E1 interfaces would be installed in the two DXC systems. However, Figure 2-21 shows a more common application, in which the DXC system is installed in a central site, and is required to provide a link to a remote branch office.

In this case, the DXC inverse multiplexer subsystem operates in a link with an IMX-2T1/E1 standalone inverse multiplexer offered by RAD. The connection between the two systems is provided by means of two links, over a T1 network.

When the DXC system is equipped with a T3 module, the DIM module can be routed to two internal DS1 ports of the DT3 module.

To provide full network management capabilities, DXC systems enable the transfer of inband management traffic through the links used by the inverse multiplexer subsystem.

In addition to the applications described above, the DIM modules installed in a DXC system equipped with E3 or T3 modules can be used to provide fractional E3 or T3 service. A typical system configuration for fractional E3 or T3 applications is shown in Figure 2-22.

TransportNetwork

E3 or T3 Module

DXC

DIM Module

Up to15.360 Mbps

DXC

E3 or T3 Module DIM Module

Up to15.360 Mbps

10/100BaseT

Router

Fast Ethernet

Router

Fast EthernetFractionalE3 or T3or STM-1

Link

FractionalE3 or T3or STM-1

Link

10/100BaseT

Figure 2-22. Fractional E3/T3 Service

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.

Note

System Structure 3-1

Chapter 3 Functional Description

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.

3.2 System Structure

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.

Chapter 3 Functional Description DXC-8R/10A/30/30E Installation and Operation Manual

3-2 System Structure

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.

Functional Block Diagram Figure 3-1 shows the functional block diagram of the DXC system. The DXC system performs its various functions by controlling the flow of data among the I/O and common logic modules installed in the DXC chassis in accordance with customer’s requirements. The flow of data is performed through the DXC bus.

DXC Bus Functions

The DXC bus comprises four independent buses: • Two data buses:

Data from I/O bus – carries the data from I/O modules.

Data to I/O bus – carries data to I/O modules.

• One control bus, carries the various clock signals used by the DXC system, and housekeeping information.

• One address bus, carries routing information from the common logic subsystem to all the modules installed in the DXC chassis.

The two data buses serve as a highway through which all the information processed by the DXC flows. The information is deposited and collected in discrete time intervals, called timeslots (one timeslot supports a data rate of 64 kbps - see Appendix E). The total number of timeslots available on the DXC data buses is 960.

Any module deposits payload information received through its external ports on one bus, and simultaneously collects the information to be sent through its external ports through the other bus. Therefore, considerable flexibility is available with respect to routing, because each module has access to all the payload information, and can be instructed by the common logic subsystem located on the DCL.3 module to read and write the desired information in the desired timeslots of the DXC bus.

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-8R/10A/30/30E Installation and Operation Manual Chapter 3 Functional Description


The routing of timeslots in accordance with the user’s configuration is performed by a proprietary, automatic timeslot allocation algorithm described in the Automatic Timeslot Allocation Algorithm section below. Therefore, the operation of the routing functions located on the DIM, E3, T3 or fractional STM-1 modules is coordinated with the operation of the main cross-connect matrix located on the DCL.3 module. As a result of this coordination, the timeslots routed to these modules are handled only by the corresponding module, and therefore are not connected through the DCL.3 matrix.

DXC System

DCL.3 Module

Add

ress

Bus

Con

trol

Bus

E3/T3/Fractional STM-1Multiplexer Module

DXC Bus

Control Logic

Inverse MultiplexerModule

I/O Module

I/O Module

Dat

a fr

om I/

O

Dat

a to

I/O

Main Cross-ConnectMatrix

Figure 3-1. DXC System, Functional Block Diagram



Functions of Main Cross-Connect Matrix

The routing of high-speed data, the E1 and T1 cross-connect functions and the fractional E1 and T1 services (including E1 and T1 ports located on HDSL modules) are supported by means of the main cross-connect matrix located on the DCL.3 module. This matrix, which has a capacity of 960 × 960 timeslots, interconnects the two data buses (Data from I/O and Data to I/O) and enables routing individual timeslots between any E1, T1, HDSL, DHS and “U” interface ports.

The matrix capacity is sufficient to handle all the timeslots available on the DXC data buses.

The routing is performed by reading (under the control of the common logic subsystem) timeslots from the Data from I/O bus and applying them in the prescribed timeslots of the Data to I/O bus. Each of the E1, T1, HDSL, DHS or “U” interface modules then reads the information from the user-configured timeslots of the Data to I/O bus, to implement the timeslot connections defined by the user.

The operation of the routing subsystems is explained in Timeslot Routing on page 3-21.

Routing Subsystems of E3, T3 and Fractional STM-1 Modules

E3, T3 and fractional STM-1 multiplexing functions are performed internally, on the corresponding type of multiplexer module. Only one E3, T3 or fractional STM-1 port is needed to utilize the full traffic capacity of a DXC chassis, and therefore a DXC system supports one active module of these types. However, for redundancy, two E3 or T3 modules or one dual-port fractional STM-1 module can be installed in the DXC chassis.

E3, T3 and fractional STM-1 modules have internal routing subsystems that control the flow of payload through their external port. As shown in Figure 3-1, these multiplexer modules include two types of routing functions:

• Timeslot Routing Matrix. The timeslot routing matrix consists of two sections: an input section that takes data from the Data from I/O bus, and an output section that applies data on the Data to I/O bus.

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.

Routing Subsystem on DIM Modules

Each DIM module has its own timeslot routing subsystem, which is used to connect the DIM user’s port to the DXC data buses that provide the paths between the DIM routing subsystem to the desired E1, T1 or HDSL ports.

The DIM routing subsystem is similar to the routing subsystems of the network interface modules described above: it accepts input data from the Data from I/O bus, and applies output data on the Data to I/O bus. Through these buses, the DIM module can connect internally to the following types of ports:

• Individual E1 or T1 ports located on I/O modules

• Internal E1 or T1 ports of E3, T3 or fractional STM-1 multiplexer modules. On these modules, the data streams from DIM modules are routed by the module matrix bypass switches directly to one of the internal ports.

Automatic Timeslot Allocation Algorithm The number of timeslots on the DXC data buses, although it is rather large (960), is not unlimited. Considering the ongoing trend toward higher density modules, the DXC data bus bandwidth may eventually restrict the number of modules that can be installed in one chassis: for example, at this stage RAD offers up to 8 external E1, T1 or n x 64 kbps ports on one module (on the D8E1, D8T1 or D8HS modules), and up to 30 internal E1 ports on one module (on the DFSTM-1 module), where each port may require up to 32 timeslots.

To fulfill the system capacity requirements in the most cost-effective way, it is necessary to utilize the available bus bandwidth in an optimal way. For this purpose, DXC systems have an automatic timeslot allocation algorithm (this algorithm is available starting with software version 6.6).

Basically, the automatic timeslot allocation algorithm allocates DXC bus timeslots to each I/O module port installed in the DXC chassis that needs to be connected to another port (the user specifies the routing requests by means of the DEF PORT and DEF TS commands). The algorithm is implemented by the common logic subsystem located on the DCL module, and manages the utilization of timeslots on the DXC data buses in accordance with the user’s routing requests.

The algorithm operates in a completely automatic way, without any user's intervention. However, the algorithm uses as its inputs the system configuration (which module is installed in which slot) and the required connectivity (which is defined by the user’s routing requests). Thus, when a new module is inserted in the chassis, the algorithm may find it necessary to reallocate timeslots on the DXC data buses to accommodate the new module. This will result in a short disruption in the traffic carried by the existing modules.



For certain combinations of modules and connectivity requirements, it is possible to improve the DXC data bus utilization and minimize, or even avoid, traffic disruptions caused by installing a new module. However, this requires an understanding of the automatic timeslot allocation algorithm. The information necessary for this purpose is presented below.

DXC Data Bus Organization

The total number of timeslots on the DXC data buses, 960, is organized as 30 sets of 32 timeslots. Each set of 32 timeslots is called a bus link.

The DXC bus links are identified by two numbers, using a method similar to the method used to identify I/O module ports: the I/O slot number followed by the number of the bus link on that slot, 1 or 2.

Therefore, the range of bus links available in any DXC chassis is 1:1, 1:2; … ; 15:1, 15:2.

Note that the number of DXC bus links is always 30, that is, it does not depend on the actual number of physical I/O slots in a given chassis. For example, in the DXC-8R only the first 4 pairs of bus links are actually associated with physical slots, and in the DXC-10A – only the first 5 pairs.

Timeslot Allocation Approach

As explained in the Functional Block Diagram section above, DXC modules use several types of routing subsystems. Accordingly, the automatic timeslot allocation algorithm uses three different methods for the allocation of timeslots to DXC module ports:

• Fixed timeslot allocation

• Dynamic timeslot allocation

• Allocation to network interface 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.

Since the timeslot allocation is automatically performed, the term used for automatic allocation is timeslot capturing.

Note



Table 3-1. Classification of I/O Modules with Respect to Timeslot Allocation (Capturing) Mechanism

Type DXC I/O Modules Timeslot Capturing Mechanism

Type 1: fixed timeslot allocation modules

DE1B, DT1B, DHL/E1, DHL/E1/2W, DHS, D8U, D16U

When you insert a Type 1 module into the DXC chassis, the two bus links (64 timeslots) associated with the corresponding I/O slot are immediately assigned to this module and can be used only by this specific module. For example, a module installed in slot 10 will occupy the bus links identified as 10:1 and 10:2.

A Type 1 module configured in the database occupies the two associated bus links even if it is not inserted in the chassis

Type 2: dynamic timeslot allocation modules

D4E1, D4T1, D8E1, D8T1, D8SL, D8HS

When you insert a Type 2 module into the DXC chassis and configure its connectivity, the timeslot allocation algorithm assigns a minimum number of bus links to the module. This allocation is dynamic, meaning that it depends on the current system configuration and may change when the configuration changes. To avoid automatic timeslot allocation, you can select static timeslot allocation as described below on page 3-10.

A Type 2 module installed in the chassis and configured in the database does not occupy bus links, unless its timeslots are connected.

Type 3: network interface modules

DE3, DT3, DIM, DFSTM-1 A Type 3 module does not require the allocation of bus links, nor timeslots on the DXC data buses.

Therefore, the insertion and/or configuration of a Type 3 module in the DXC chassis and DXC database does not result in any changes in the current allocations

Timeslot Allocation to Type 1 (Fixed Allocation) Modules

For Type 1 modules (see Table 3-1), the 64 timeslots carried by the two bus links of each I/O slot are preassigned: this means that when a Type 1 module is physically installed in an I/O slot, each connected timeslot of an external port is always routed to the same data bus timeslot.

The timeslots of the fixed-allocation modules are routed by the main cross-connect matrix on the DCL.3 module. The result is that when a DE1B, DT1B, DHS, etc., timeslot is routed to a timeslot of another Type 1 module, it actually requires two timeslots on the DXC data buses:

• One data bus timeslot is used to transfer the payload from the source to the DCL module

• Another data bus timeslot is used to transfer the payload from the DCL module to the destination, after being copied to a different data bus timeslot.

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).



Timeslot Allocation to Type 3 (Network Interface) Modules

When analyzing the timeslot requirements of network interface modules, it is convenient to use the term source port for a port that sends data to a Type 3 module port (note that this term is not strictly correct, because generally data flows in both directions).

Since the routing of timeslots from any DXC data bus to any external port of a Type 3 module is performed by the module local routing subsystem (not by the main cross-connect matrix on the DCL.3 module), only a single bus link timeslot (that assigned to the source port routed to a Type 3 module port) is needed for each for each timeslot routed to a Type 3 module.

As a result, Type 3 modules do not capture bus links (only the source ports occupy timeslots on the DXC main cross-connect matrix). The local routing subsystem of any such module is dynamically configured in accordance with the current allocation of timeslots on the bus link.

Timeslot Allocation to Type 2 (Dynamic Allocation) Modules

When dealing with dynamic allocation modules, we will use the notion of the related and unrelated ports.

Related ports are those DXC ports that either have timeslots cross-connected between them, or some of their timeslots are groomed to the same port.

Unrelated ports are all other ports.

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.

Dynamic Timeslot Allocation to Type 2 Module Ports

The dynamic timeslot allocation mode automatically allocates timeslots to the ports of high-density (Type 2) modules, minimizing the number of bus links needed by this type module.

Note



The number of bus links is minimized by bundling the timeslots needed by fractional E1/T1 links served by Type 2 module ports as required to fill bus links. Only when one bus link is fully occupied, will the next bus link be captured; the process is continued until the last timeslot is placed in a bus link.

The rules for capturing bus links by a Type 2 module are as follows:

1. First priority: bus links having the same numbers as the module’s ports will be captured (the same as for Type 1 modules). For example, a D8E1 module installed in I/O slot 4 will first capture bus link 4:1, and then bus link 4:2.

2. Second priority: whenever available, the bus links associated with I/O slots with Type 3 modules will be captured. For example, if a DE3 module is installed in slot 8, the algorithm will capture bus link 8:1 and then bus link 8:2.

3. Third priority: bus links of unoccupied I/O slots will be captured in ascending order, starting with the I/O slot next to the Type 2 module itself (in this example, starting with slot 5).

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.

Note



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.

Static Timeslot Allocation to Type 2 Module Ports

As mentioned above, the dynamic timeslot allocation mode has a limitation consisting in that data traffic errors are possible not only on the port whose timeslot allocation is being modified, but also on ports whose timeslots had not been modified by the user. The alternative, “static”, mode allows you to avoid this inconvenience.

In both static submodes (STATIC and STATIC 1:1), you assign a maximum number of timeslots to each port. In the STATIC mode, any timeslot added or deleted within this maximum number in future 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.

This method requires you to estimate the maximum amount of timeslots (expected maximum capacity per port) that may be required on each port. In accordance with this parameter, the system will save the “timeslot growth space”, and use this spare space to avoid data traffic disruption on other ports in further allocated timeslots growth.

The difference between the STATIC and STATIC 1:1 modes in terms of timeslot allocation is as follows.

In the STATIC mode, any timeslot on the corresponding link can be allocated for traffic, as soon as their total number does not exceed the MAX TS parameter value. In the STATIC 1:1 mode, only timeslots in the range of TS[1] to TS[MAX_TS] can be allocated for traffic.

The number of connected timeslots may be less than MAX TS.

Note



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.

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.

Design Guidelines for High-Density Module Applications

When several I/O slots are free in a DXC chassis, it is necessary to check the DXC bus link utilization before physically inserting or configuring a new module. This check is performed by a dedicated command, DSP BUS (see Appendix F).

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 explained above, 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, as described in Evaluating Bandwidth Available for Modules to Be Installed in Chapter 6.

E1 Port Characteristics The DXC system supports external E1 ports with electrical and fiber-optic interfaces, and internal E1 ports of the DE3 module.

E1 Electrical Port Characteristics

The electrical E1 port interfaces, available on DE1B, D4E1 and D8E1 modules, meet the requirements of ITU-T Rec. G.703, G.704 and G.732. The ports support both 256N and 256S multiframes (2 or 16 frames per multiframe, respectively), as well as unframed operation in accordance with user's selection. The E1 port interfaces also support the CRC-4 option specified in ITU-T Rec. G.704. CRC-4 use is user-selectable.

The E1 ports on the DE1B module have two line interfaces:

• 120Ω balanced line interface terminated in a RJ-45 connector

• 75Ω unbalanced interface terminated in two BNC female coaxial connectors.

Note



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.

E1 Fiber-Optic Port Characteristics

The E1 fiber-optic ports, located on DE1B modules are available with a wide range of interfaces, to meet optimally a wide range of system requirements. The fiber-optic interfaces can be ordered for operation at 850 nm over 62.5/125 micron multimode fibers (typical attenuation - 3.5 dB/km), as well as over low-loss 9/125 micron single-mode fibers (typical attenuation of 0.4 dB/km at 1310 nm, and 0.25 dB/km at 1550 nm). Each option can be ordered with ST, FC/PC, or SC connectors.

Section 1.3 provides information on the characteristics of the optical subsystem, including the maximum range over typical fiber-optic cable.

All the fiber-optic interface options offer high performance and have a wide dynamic range, which ensures that the receiver will not saturate even when using short fiber-optic cables (saturation is caused when the optical power applied to the receiver exceeds its maximum allowed input power, and results in very high bit error rates).

With respect to framing, DE1B modules with fiber optic interface fully emulate the operation of the DE1B electrical interface modules. The same is true with respect to other characteristics not specific to electrical interfaces, e.g., jitter performance.

Internal E1 Port Characteristics

Internal E1 ports are located on E3 and fractional STM-1 multiplexer modules.

Note



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.

T1 Electrical Port Characteristics

The electrical T1 port interfaces, available on the DT1B, D4T1 and D8T1 modules, are compatible with virtually all carrier-provided T1 services. The T1 port interface supports both the D4 (SF) and ESF framing formats, in accordance with user's selection, as well as unframed operation. Zero suppression over the line is user-selectable (transparent (AMI) coding, B7ZS, or B8ZS).

The T1 line interface meets the requirements of AT&T TR-62411, ANSI T1.403, and ITU-T Rec. G.703, G.704. Jitter performance complies with the requirements of AT&T TR-62411.

The electrical T1 port has a 100-Ω balanced line interface. The nominal transmit level is ±3 V, and the line signal is software-adjustable for line lengths of 0 to 655 feet in accordance with AT&T CB-119. The maximum line attenuation, without CSU, is up to 10 dB; when ordered with an integral CSU, the maximum line attenuation is up to 36 dB. For shorter lines, the CSU transmit level can be set to -7.5, -15, or -22.5 dB.

Each T1 port of the DT1B and D4T1 modules is terminated in an RJ-45 eight-pin connector.

The T1 port interfaces on the D8T1 module depend on the module version:

• The T1 ports on the 3U D8T1 modules are terminated in two 25-pin D-type female connectors, one for the transmit pairs, and the other for the receive pairs of all the ports.

• The T1 ports on the 6U D8T1 modules have individual RJ-45 eight-pin connector for each port.

T1 Fiber-Optic Port Characteristics

The T1 fiber-optic ports located on DT1B modules are available with the same range of options listed above for E1 fiber-optic interfaces.

With respect to framing, the DT1B modules with fiber optic interface fully emulate the operation of the DT1B electrical interface modules. The same is true with respect to other characteristics not specific to electrical interfaces, e.g., jitter performance.

Internal DS1 Port Characteristics

Internal DS1 ports are located on T3 multiplexer modules.

Note



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.

E3 Electrical Interface Characteristics

The E3 port has a 75 Ω unbalanced line interface, terminated in two mini-BNC connectors. Line coding is HDB3.

The interface characteristics complies with the applicable requirements of ITU-T Rec. G.703 and G.823.

E3 Fiber-Optic Interface Characteristics

The E3 fiber-optic ports located on DE3 modules are available with a wide range of fiber-optic interfaces, to optimally meet a wide range of system requirements.

The fiber-optic interfaces can be ordered for operation at 1310 nm and 1550 nm over low-loss 9/125 micron single-mode fibers (typical attenuation - 0.4 dB/km at 1310 nm, and 0.25 dB/km at 1550 nm). Each option can be ordered with ST, SC, or FC/PC connectors.

Section 1.3 provides information on the characteristics of the optical subsystem. Assuming a 3 dB margin, the maximum range at 1310 nm is up to 25 km (16 mi) with the LED, or up to 40 km (25 mi) with the laser transmitter; the range at 1550 nm is up to 50 km (30 mi).

All the fiber-optic interface options offer high performance and have a wide dynamic range, which ensures that the receiver will not saturate even when using short fiber-optic cables (saturation is caused when the optical power applied to the receiver exceeds its maximum allowed input power, and results in very high bit error rates).

T3 Port Characteristics The DXC system supports external T3 ports with electrical and fiber-optic interfaces.

T3 Electrical Interface Characteristics

The T3 port has a 75Ω unbalanced line interface, terminated in two BNC connectors. The interface characteristics comply with the applicable requirements of Bellcore TR-NWT-000499, GR-253-CORE, ANSI T1.102, and ITU-T Rec. G.703. Line coding is B3ZS.

The T3 port supports two framing modes: synchronous M13 (SYNTRAN) and C-bit parity multiplex applications in accordance with ANSI T1.107 and ANSI T1.107a.

T3 Fiber-Optic Interface Characteristics

The T3 fiber-optic ports located on DT3 modules are available with the same range of options listed above for E3 fiber-optic ports.



Fractional STM-1 Subsystem Characteristics The function of the fractional STM-1 multiplexing subsystem is to multiplex the internal E1 port data streams into a STM-1 frame structure. The fractional STM-1 subsystem has a capacity of 30 E1 data streams.

For information on the SDH environment, refer to Appendix E.

Fractional STM-1 Multiplexing Subsystem Functions

The multiplexing operation is performed by inserting each internal E1 stream into the SDH frame structure called Virtual Container 12 (VC-12), (one VC-12 for each E1 stream).

To form the complete STM-1 frame structure, the VC-12 data streams are multiplexed by inserting each VC-12 into the user-selected tributary unit (TU-12) contained in the VC-4 payload data section of the STM-1 frame, and then adding the various SDH overhead and framing signals. Since there are 63 TU-12s but not more than 30 VC-12s can be in use, some of the TU-12s must always carry the unequipped signal label.

STM-1 Link Interface Functions

The link interface subsystem comprises the external STM-1 ports of the module (one or two, in accordance with the module type).

The DFSTM-1 module provides the following user-selectable operating modes:

• Fractional SDH terminal multiplexer (TM) for the DXC chassis, capable of multiplexing up to 960 timeslots taken from the DXC bus (structured as 30 E1 data streams (tributaries)) into one STM-1 data stream. The module supports free routing of any E1 data stream to any of the 63 TU-12 tributary units carried in the STM-1 VC-4 virtual container.

The TM function is supported by both the single-port and dual-port DFSTM-1 versions. When a dual-port DFSTM-1 module is used as a TM, the user can enable line redundancy (single-slot protection): in case the active STM-1 port or its link fails, the traffic is automatically switched to the other STM-1 port in less than 50 ms.

• Add/drop SDH multiplexer (linear ADM) for the DXC chassis, supported by the dual-port DFSTM-1 version. The total number of TU-12 tributaries that can be added/dropped to the local DXC bus is up to 30 (out of the maximum of 63 TU-12 carried in a VC-4), that is, up to 960 timeslots.

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.

Note

Note



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.

HDSL Subsystem Characteristics Two versions of HDSL subsystems are used, 4-wire and 2-wire:

• The HDSL subsystem located on DHL/E1 modules uses dual duplex transmission to enable the transport of E1, respectively T1, data over two 2-wire lines. The line code on each of the two HDSL lines is 2B1Q at a rate of 584 kbaud (equivalent to a data transfer rate of 1168 kbps).

• The HDSL subsystem located on the DHL/E1/2W module uses duplex transmission to enable the transport of E1 data over one 2-wire line. The line code on the HDSL line is 2B1Q at a rate of 1160 kbaud (equivalent to a data transfer rate of 2320 kbps).

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.

SHDSL Subsystem Characteristics D8SL is an eight-port I/O module using the single-pair high-speed digital subscriber line (SHDSL) technology.

The SHDSL technology, standardized in ITU-T Rec. G.991.2, is an efficient method for transmitting full-duplex data at high rates over a single unloaded and unconditioned twisted copper pair, of the type used in the local telephone distribution plant. Therefore, SHDSL provides a cost-effective solution for short-range data transmission and last-mile applications. D8SL modules can be configured by the user to operate either in accordance with ITU-T Rec. G.991.2 Annex A for compatibility with North American (or similar) networks, or Annex B for compatibility with European (and similar) networks.

Each D8SL module port is supported by an independent multi-rate SHDSL modem. Each modem supports user-selectable data rates in the range of 64 kbps (1 timeslot) up to 2048 kbps (32 timeslots).

Each D8SL port can transfer either G732N or G732S multiframes (2 or 16 frames per multiframe, respectively), in accordance with user's selection. D8SL ports can also be operated in an unframed mode, which supports transparent transmission of unframed 2.048 Mbps signals.

D8SL ports can operate only as central office (CO) SHDSL ports, a function referred to as STU-C (SHDSL terminal unit – CO) in ITU-T Rec. G.991.2. D8SL ports are intended for operation in a link with the ASMi-52 G.SHDSL Modems with Remote Management offered by RAD, as well as with other RAD equipment having SHDSL interfaces, for example, FCD-IP, etc. However, the D8SL modules will also operate in a link with ITU-T Rec. 991.2-compatible STU-R units (SHDSL terminal unit – remote) from other vendors.

High-Speed Data Port Interface Characteristics The high-speed data port interfaces available on the DHS and D8HS modules are V.24, RS-422, V.35 or X.21 (converted from RS-530 via adapter cables).

The high-speed data ports can operate at rates which are multiples of 56 kbps or 64 kbps (n×56 kbps or n×64 kbps, where n = 1 to 31; this corresponds to rates of 56 to 1736 kbps, or 64 to 1984 kbps, respectively).

Ethernet Port Interface Characteristics

The DHS module can be ordered with two Ethernet ports, instead of high-speed data interfaces.

The connection of the external Ethernet port to the internal chassis buses can be made either through a bridge, or through an IP router, in accordance with order.


3-18 DXC System Timing

• 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 IR-ETH/QN interface module includes a high performance self-learning Fast Ethernet bridge, which is connected to the LAN via a single 10BaseT or 100BaseT port, operating in full or half duplex and providing simple and cost-effective interconnection between 10/100BaseT LANs via E1 links. The IR-ETH/QN interface module also supports IEEE 802.1/P frames and IEEE 802.1/Q frames, enabling VLAN applications.

The module automatically learns MAC addresses of the LAN to which it is connected. Its LAN table stores up to 512 addresses with 5-minute automatic aging.

Filtering and forwarding is performed at the maximum theoretical rate of 150,000 packets per second (wire speed). The buffer with 0.512 Mbit SRAM can hold 85 frames (in average). The forwarding of the multicast messages from LAN to WAN can be disabled.

The bandwidth allocated to the WAN link of the bridge or router can be selected by the user, at rates which are multiples of 56 kbps or 64 kbps (n×56 kbps or n×64 kbps, where n = 1 to 31; this corresponds to rates of 56 to 1736 kbps, or 64 to 1984 kbps, respectively).

ISDN “U” Data Port Interface Characteristics The ISDN digital subscriber line (IDSL) technology offers a cost-effective and reliable solution for delivering service at up to 128 kbps to customer’s premises over the existing copper infrastructure.

The D8U/D16U modules are fully interoperable with the HS-U family of ISDN interface data modules for the Megaplex-2100 Modular T1/E1 Access Multiplexer Systems.

The D8U/D16U family modules provide 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 transmission over 2-wire unconditioned lines at ranges up to 5.5 km over 26 AWG wire, and can supply phantom feed voltage to the equipment connected to the remote end of the line from an external DC feed source.

3.3 DXC System Timing

DXC Port Timing This Section presents information on the timing modes supported by the various types of DXC ports.


DXC System Timing 3-19

Timing of External Fractional STM-1, E3 and T3 Ports

The timing of the receive path of the external fractional STM-1, E3 or T3 port is always derived from the clock signal recovered from the incoming signal: 155.520 MHz.

The timing of the transmit path can be selected by the user: • Internal Timing Mode: in this mode, the timing reference depends on the

external port type:

For external E3 and T3 ports, the timing reference for the module transmit path is the internal module clock generator.

For external fractional STM-1 ports, the timing reference for the module transmit path is the DXC master clock.

• Loopback Timing Mode: in this mode, the timing reference for the module transmit path is the clock signal recovered from the incoming E3 or T3 signal.

Timing of External E1 and T1 Ports

The timing of the external E1 and T1 ports is as follows:

• The receive clock of each external E1/T1 port is always derived from the incoming line signal.

• The transmit clock of each external E1/T1 port is locked to the DXC system master clock, and therefore the transmit timing of all the E1 and T1 ports is synchronized (see DXC System Master Timing section below).

Timing of Internal E1 and DS1 Ports

The timing of the receive path of an internal E1 or DS1 port of the DE3, DT3 or DFSTM-1 module is always derived from the clock signal recovered from the corresponding incoming data stream.

The timing of the transmit paths of all the internal E1 or DS1 ports is always locked to the DXC system master clock.

Timing of High-Speed Data Ports

The user can select the timing mode of each high-speed data port from the following three options:

• DCE: the high-speed data port provides the transmit and receive clock signals to the equipment (DTE) connected to it. The clock signals are locked to the internal master clock of the DXC system.

• DTE1: the high-speed data port provides the transmit clock signal, and accepts the receive clock signal from the equipment connected to the port. This mode is suitable for tail-end applications.

• DTE2: the high-speed data port accepts the receive and transmit timing signals from the equipment connected to the port, and buffers and retimes the incoming data. This requires the master clock signal of the DXC system to be either locked to the receive signal of that port, or to the same timing source that is used by the equipment connected to that port. This is practical when


3-20 DXC System Timing

the high-speed data port is connected to the national network or to private carrier data lines.

Timing of ISDN “U” Ports

The transmit timing used by D8U/D16U modules is locked to the DXC system nodal timing, however the nodal timing mode depends on the selected operating mode:

• LT Mode. In the LT mode, the system nodal timing, which can be selected in accordance with other system considerations, determines the timing of the data transmitted to the user’s network termination equipment (e.g., ASMi-31, ASM-31, etc.), connected to the D8U/D16U channels. The receive timing is recovered from the line signal received from the user’s equipment. Therefore, to ensure that the same timing is used on the receive direction (from the user’s equipment to the D8U/D16U channel), the user’s equipment must operate with loopback timing.

• NT Mode. In the NT mode, one of the active D8U/D16U channels can be selected as external clock source for the DXC system.

DXC System Master Timing Internally, DXC systems use one master timing reference (clock). This master timing reference is used to determine the transmit timing of all the E1, T1, HDSL, DIM, and ISDN “U” ports (for the high-speed data ports, additional timing options are available, as explained above).

To achieve maximum flexibility in system integration and enable hierarchical distribution of timing in the system, the DXC system enables the user to select the source to which the internal master clock is locked. The available options are as follows:

• Transmit clock source locked to the receive clock of a user-selected external port (E1, T1, STM-1, or nx64 kbps). If the desired port is a high-speed data port, its timing mode must be DTE2. If the desired port is an ISDN “U” port, its timing mode must be NT. If the desired port is an STM-1 port, its timing mode must be LBT.

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


Timeslot Routing 3-21

or “U” ISDN port selected as the main source, or when the RTS line of a DHS port is switched off).

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.

3.4 Timeslot Routing

Operation of Main Cross-Connect Matrix The main cross-connect matrix, located on the DCL.3 module, is used for routing at the level of the individual timeslots.

The control subsystem can change the timeslot routing during system operation, without disrupting the service to the users of timeslots that are not rerouted. This however does not apply to routing performed from the DIM modules to fractional STM-1, E3, T3, D4E1/D8E1 or D4T1/D8T1 modules: routing changes on these modules result in a short disruption while the corresponding matrix is reconfigured (see description of automatic timeslot allocation algorithm on page 3-5).

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.

Note


3-22 Timeslot Routing

Unidirectional mode (optional feature): 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, and is allowed only between E1, T1, HDSL, and high-speed data ports.

• Transparent Routing – in this mode, the routing subsystem transparently transfers the whole frame structure toward the external fractional STM-1, E3 or T3 port. The transparent mode, supported by DXC systems using software release 5 and higher, enables the transmission of a full data stream received from another I/O module with the same interface (including timeslot 0 and timeslot 16) through the corresponding link; this mode is also required to enable the transmission of the F-bit of a T1 port through the link.

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 expedite the routing, a sequential “bundle” routing mode is also available: one “bundle” (group of consecutive timeslots, identified by the number of the starting timeslot and the total number of timeslots) can be routed to the desired destination port, maintaining its integrity, and inserted in the destination frame sequentially, in consecutive timeslots. The user can also specify the starting timeslot in the source frame and in the destination frame.

• For high-speed data ports (including “U” ISDN ports operating in the LT-1 mode at the data rate of 128 kbps, the user's data stream can be connected to any desired E1, T1 or HDSL port (internal or external) as well as to another DHS port. Note that in this case, the 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:


Timeslot Routing 3-23

The sequential routing mode, described above.

The alternate 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.

DXC System Capacity The DXC system capacity is mainly determined by the number of timeslots available on the data buses; the second factor is the capacity of the main cross-connect matrix, located on the DCL.3 module. The third factor is the number of I/O slots available in any specific DXC chassis.

The total number of timeslots available on the data buses of any DXC chassis is 960; this is also the capacity of the main cross-connect matrix.

For applications which require different combinations of modules, the maximum capacity can be determined by considering the total number of available timeslots, and the routing methods described above:

• Each timeslot (or DS0 channel) routed to an internal port located on a fractional STM-1, E3 or T3 module requires one timeslot on the data buses.

• Each timeslot (or DS0 channel) routed to an E1/T1 (external or internal), DHS or D8U/D16U port requires two timeslots on the data buses.

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.

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.

Capacity Examples for DXC Systems with E3 Link

A DXC system with an E3 link requires one E3 multiplexer module (a second module can be installed for redundancy). A fully utilized E3 link carries 16 E1 streams, which require 512 payload timeslots. Therefore, 448 timeslots are free for other applications.

In a system without DIM module, the 512 payload timeslots can be provided by connecting the following modules to the internal ports of the E3 multiplexer module:

• 8 DE1B, 8 DT1B, or 8 DHS modules operating at maximum capacity

Note


3-24 Inband Alarm Indications

• Four D4E1 or D4T1 modules

• Two D8E1 or D8T1 modules

• 14 D16U modules

• Any combination of DE1B, DT1B, DHS, D8U and D16U modules that together fill 16 E1 or T1 data streams.

The additional 448 timeslots (equivalent to 14 E1 streams) can be assigned to cross-connections among other DE1B/DT1B/DHS/DHL/D8U/D16U modules.

When DIM modules are installed and configured for maximum bandwidth (which requires 8 links per DIM module), two DIM modules (i.e., 16 E1 or T1 data streams) can be connected to one E3 multiplexer module. The 448 free timeslots can be used to support up to 7 interconnected DE1B/DT1B/DHS/D8U/D16U modules.

Capacity Examples for DXC Systems with T3 Link

A DXC system with a T3 link requires one T3 multiplexer module (a second module can be installed for redundancy). A fully utilized T3 link carries 28 T1 streams. The number of data bus timeslots needed to connect to each internal T1 port of the T3 module is the same as for an E1 port, resulting in a maximum of 896 payload timeslots. This leaves 64 timeslots free for other applications.

As an example, in a system without DIM module, the payload timeslots can be provided by connecting 14 DE1B, DT1B or DHS modules operating at maximum capacity to the internal ports of the T3 multiplexer module. The remaining data bus capacity can be used to route two additional DE1B/DT1B/DHS/DHL/D8U/D16U ports to the T3 module, or to interconnect up to three such ports.

The maximum number of DIM modules (configured for maximum bandwidth, which requires 8 links per DIM module) that can be installed and connected to one T3 multiplexer module is 3 (24 links). The remaining free timeslots can be used to support up to 7 interconnected DE1B/DT1B/DHS/D8U/D16U modules.

Capacity Example for DXC System with Fractional STM-1 Link

A DXC system with fractional STM-1 link requires one fractional STM-1 multiplexer module.

The STM-1 port of the fractional STM-1 module can carry up to 30 E1 data streams connected from other DXC module: this number fully utilizes the 960 timeslots available on the DXC data buses.

3.5 Inband Alarm Indications

The DXC system provides indications regarding problems on one of its links to the other links. Two types of indications are provided: out-of-service (OOS) indications in the individual timeslots, and link alarms.


Inband Alarm Indications 3-25

Indications in Individual Timeslots of E1 and T1 Ports In many applications it is necessary to signal the equipment connected to one of the DXC E1 or T1 system ports that the link connected to the other port is out-of-service. This indication, called carrier group alarm (CGA), should be provided in each timeslot.

However, the appropriate signaling method depends on the application, because the transmission of such indications interferes to some extent with the transmission of the user's data.

The DXC system provides three CGA indication options:

NONE When one of the links connected to a DXC system port is in the out-of-service state, the timeslots transferred to the other port carry a user-selectable OOS code. The OOS code can be different from the idle code (the code inserted in timeslots not assigned to user traffic or housekeeping purposes). Moreover, two different OOS codes can be specified, one for data channels, and another for voice channels. In addition, the signaling bits of the port (designated A, B, C, D in Figures E-1 and E-2) also assume the OOS state specified by the user: • For T1 ports with ESF framing, all the four bits are affected; with SF framing, only bits A, B are

used.

• For E1 ports, OOS is indicated by setting the bits A and B to the user-selected state; the other two bits are preset as follows: C=0, D=1.

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.


3-26 Inband Alarm Indications

The C and D signaling bits are fixed at C=0, D=1, in accordance with ITU-T Rec. G.704, Table 9.

Link Alarms for E1 and T1 Ports The DXC system recognizes the following link alarm conditions:

• Local loss of port input signal

• Local loss of synchronization to port signal (red alarm condition).

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).

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.

Table 3-2. DXC Response to E1 and T1 Link Alarm Conditions

Port A Port B

Condition Send Yellow Alarm or MF Yellow Alarm

Send AIS

Send OOS Code

Send Signaling OOS Code

Send Yellow Alarm or MF Yellow Alarm

Send AIS

Send OOS Code

Send Signaling OOS Code

AIS Red Alarm A Yes No No No No No Yes (Note) Yes (Note) Yellow Alarm A No No No No No No No No MF Red Alarm A Yes No No No No No No No Red Alarm B No No Yes (Note) Yes (Note) Yes No No No Yellow Alarm B No No No No No No No No MF Red Alarm B No No No No Yes No No No

Legend: MF – multiframe

Response depends on CGA mode selected by the user.

Alarm Indications for E3 and T3 Ports The internal E1/T1 ports of the E3 and T3 modules support indications regarding problems on the link, such as local loss of synchronization, local AIS reception, or remote loss of synchronization. The following types of indications are provided: idle and out-of-service (OOS) indications in the individual timeslots, and link alarms.

• Idle Slot Indication. A special user-selectable code can be transmitted in empty timeslots (timeslots which do not carry payload) towards the network.

• OOS Indications. The OOS indications provided in individual timeslots are used to signal the equipment routed to one of the internal ports of the module

Note

Note

Note

Note


Inband Alarm Indications 3-27

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.

When an internal port of an E3 or T3 module is in the OOS state, it transmits the OOS service code toward the DXC bus. As a result, the E1, T1, DHS and D8U/D16U modules connected to that port will receive the OOS code in the timeslots mapped to the corresponding port; if the port is configured for transparent routing (full link), it will stop transmitting the frame alignment bits.

Specific Alarm Indications for Fractional STM-1 Modules

Specific Alarm Indications for VC-12 and VC-4 Internal Ports

In addition to the standard E1 internal ports, which are entities similar to those of PDH modules, the fractional STM-1 module includes internal VC-12 and VC-4 ports, which are SDH entities. The alarm conditions for SDH entities are described in Appendix E: the responses to these alarm conditions are in accordance with the applicable standards.

Considering the operating environment and typical applications in which DXC systems are used, the user can modify the standard behavior to minimize configuration overhead and even prevent the generation of certain type of alarms which may not be relevant in many typical DXC applications.

For example, the user can enable/disable the sending of a VC path trace. This is necessary for applications in which the equipment at the remote end of the VC-12 path cannot use, or does not need to monitor the path continuity: in this case, the user can disable the sending of the path trace string. In addition, the user can also enable/disable the monitoring of the received VC path trace string.

The sending of the AIS and RDI indications in response to the following alarm conditions can be enabled or disabled by the user:

• Excessive error rate (i.e., error rate exceeding a user-selected threshold) in the received VC data stream. The error rate is estimated on the basis of the parity errors detected by means of the error detection code carried within the VC path overhead bytes.

• Incorrect VC signal label. The signal label, which indicates the format of the data carried by the VC, is also carried in the VC path overhead bytes.

• Mismatch between the expected VC path trace bytes and that actually received. The path trace byte is a 16-character string assigned by the user, and inserted in the VC path overhead at the VC assembly point. Each VC should be assigned a distinct string. Therefore, the reception of the correct path trace bytes confirms path continuity.


3-28 Inverse Multiplexer Subsystem Characteristics

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).

Specific Alarm Indications for External STM-1 Port

The user can also configure the response to alarm conditions detected by the external STM-1 port. The options available for this port include:

• Setting of the excessive error rate degradation (EED) and signal degradation (SD) thresholds.

• Enable/disable the sending of AIS toward the internal E1 ports in case of a failure condition. The failure conditions which may result in AIS are as follows:

LOS (loss of SDH signal)

LOF (loss of SDH frame)

TIM (failure of internal timing generator)

SSF (synchronization source failure)

• Enable/disable the sending of RDI toward the remote side in case of a failure condition.

3.6 Inverse Multiplexer Subsystem Characteristics

Inverse multiplexing is a technique that splits a high-speed data stream for parallel transmission over several lower-speed transmission lines. The inverse multiplexer subsystem of the DXC is based on a DIM module that provides the high-speed interface for user’s data equipment, and processes the user’s data stream to enable its transmission over E1 or T1 links (including links passing through an E3 or T3 port). For a description of the transmission characteristics of the E1 and T1 links, refer to Section 3.2.

The DIM modules can use up to eight links. The links are routed to user-selected external E1 or T1 ports located on E1 or T1 modules, or internal ports of fractional STM-1, E3 or T3 modules. At any time, only one type of ports (either E1 or T1) can be used.

Inverse Multiplexing Principles The DIM module distributes the incoming user's data bits among the active links on a bit-by-bit basis. For all the DIM versions, except for the version with E1 interface, the number of active links is selected by the user (up to the maximum of eight links available on a given DIM module).

For the DIM version with E1 interface, the number of links is always 2, and only T1 links should be used.

The number of active links determines the user's data rate:

• On E1 links, the DIM module utilizes 30 timeslots of each frame transmitted on an E1 link for the transmission of user's data, therefore the user's data rate is 1.920 Mbps times the number of active links.

Note

Note


Inverse Multiplexer Subsystem Characteristics 3-29

The remaining timeslots of each E1 frame (timeslots 0 and 1) are used to transmit the overhead data.

• On T1 links, the DIM module utilizes 23 timeslots of each frame transmitted on a T1 link for the transmission of user's data, therefore the user's data rate is 1.472 Mbps times the number of active links. The remaining bits of each T1 frame (these are the eight bits of timeslot 1 and the 193rd bit of the frame) are used to transmit the overhead data.

The overhead data includes the standard E1 or T1 frame synchronization and housekeeping data (see Appendix E), and overhead information generated by the DIM module.

The information generated by the DIM module is used to determine the differential delays among the active links. The DIM module can tolerate differential delays up to 64 msec. This allows the routing of the lines used by a given DIM module over different paths or different facilities, for increased flexibility and reliability.

Note that although the DIM module can tolerate differential delays up to 64 msec, the actual latency of a DIM module link is similar to the maximum differential delay encountered on the lines being used. Moreover, for applications in which the differential delay is known to be smaller, the user can configure the DIM module to correct for lower differential delays (up to 16 msec).

Clock Waveform Characteristics The receive path of the DIM module provides the original user's data stream and a clock signal that is synchronized with the individual data bits. The DIM module can provide either a gapped clock signal, or a smoothed clock signal, obtained by filtering the gapped clock signal by means of a phase lock loop (PLL). The selection between the two modes is made by the user.

• Gapped Clock Characteristics. When the gapped clock mode is selected, the receive clock supplied to the user's DTE consists of bursts separated by gaps that appear during the transmission of overhead data. The basic frequency of the clock bursts is 2.048 MHz, irrespective of the link type (E1 or T1).

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


3-30 Inverse Multiplexer Subsystem Characteristics

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.

Recovery from Fault Conditions The DIM module supports the fallback feature: if one of the links fails, the DIM module will automatically select the next lower rate available and continue providing service at the fallback rate.

When the failed link recovers, the DIM module automatically returns to the original, user-selected rate. To make use of the fallback feature, the user's equipment must be able to tolerate changes in the data rate.

In case fallback is not desirable, the user can disable this feature.

DIM Synchronous Data Port Interface Characteristics DIM modules with synchronous data ports can be ordered with V.35, RS-530, X.21, or HSSI interfaces. The high data rates made possible by the DIM module (up to 11.776 Mbps when using T1 links, and up to 15.360 Mbps when using E1 links), exceed the capabilities of the slower interface types.

To achieve the maximum possible range, it is necessary to use high-quality shielded twisted-pair cable.

The DIM port operates as a DCE interface, and therefore the user can select the timing mode from the following options:

• DCE: the DIM data port provides the transmit and receive clock signals to the user’s equipment (DTE) connected to it. The clock signals are locked to the internal master clock of the DXC system.

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).


Inverse Multiplexer Subsystem Characteristics 3-31

• 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.

DIM Ethernet Port Characteristics The DIM module can be ordered an Ethernet port, instead of a high-speed data interface.

The connection of the external Ethernet port to the internal chassis buses can be made either through a bridge, or through an IP router, in accordance with order.

• 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 IR-ETH/QN interface module includes a high performance self-learning Fast Ethernet bridge, which is connected to the LAN via a single 10BaseT or 100BaseT port, operating in full or half duplex and providing simple and cost-effective interconnection between 10/100BaseT LANs via E1 links. The IR-ETH/QN interface module also supports IEEE 802.1/P frames and IEEE 802.1/Q frames, enabling VLAN applications.

The module automatically learns MAC addresses of the LAN to which it is connected. Its LAN table stores up to 512 addresses with 5-minute automatic aging.

Filtering and forwarding is performed at the maximum theoretical rate of 150,000 packets per second (wire speed). The buffer with 0.512 Mbit SRAM can hold 85 frames (in average). The forwarding of the multicast messages from LAN to WAN can be disabled.

DIM E1 Interface Characteristics The DIM module with E1 interface enables transparent transmission of one E1 data stream (2.048 Mbps) over two T1 links (1.544 Mbps) in accordance with AT&T TR 54019. The connection is transparent, i.e., is performed on a bit-by-bit basis (unframed mode).

The interface complies with ITU-T Rec. G.703 requirements. In general, the equipment connected to the DIM module E1 port should use loopback timing: that is, it recovers the clock from the data provided by the receive path of the DIM module, and uses the recovered clock signal to determine the transmit-to-DIM data rate.


3-32 Using Redundancy to Increase System Availability

3.7 Using Redundancy to Increase System Availability

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.

The utilization of redundancy is explained below.

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.

The implementation of redundancy at the system level is explained below.


Using Redundancy to Increase System Availability 3-33

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.

Common Logic Subsystem Redundancy

The common logic subsystem includes the DXC control and timing distribution circuits and the central switching matrix. These functions are implemented by the DCL.3 module. A single DCL.3 module per chassis is sufficient.

The DXC-8R chassis includes a redundant common logic subsystem (that is, two DCL.3 modules are always installed in the DXC-8R). For the DXC-30 and DXC-30E chassis, common logic redundancy function becomes available by installing a second DCL.3 module in the enclosure.

The redundancy function can then be activated by user's commands: when activated, one of the DCL.3 modules is selected as the active (on-line) module, and the other module is selected as the standby (off-line) module. Both modules use the same database, and both modules are automatically updated with any changes in the system configuration. The updating is performed under the control of the active module, transparently to the operator.

Using the built-in power-up and on-line diagnostic functions and an advanced redundancy control algorithm, DXC-30, DXC-30E, and DXC-8R can automatically detect a malfunction in the on-line DCL.3 module and transfer the control to the off-line module (“flip” to the other module).

The user can also configure the DCL.3 module to provide redundancy for the external (station) clock. When this function is enabled, the loss of the external clock signal connected to one DCL.3 module will result in switching to the other DCL.3 module.

If necessary, the user can force one DCL.3 module to be always online. This disables redundancy, even when two DCL.3 modules are installed.

The control subsystem is designed to ensure that the management link is always connected to the active module, irrespective of the management method:

• When using the RS-232 ports of the DCL.3 modules, only the interface of the on-line module is physically connected to the corresponding port connector.

Note



Therefore, it is sufficient to use a “Y” cable to connect, in parallel, the supervision terminal to the CONTROL connectors of the two DCL.3 modules: neither special sharing arrangements, nor any external equipment are required.

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.

Operation of Common Logic Redundancy Control Algorithm

The redundancy control algorithm is used to control the switching between the two DCL.3 modules. Basically, the redundancy control algorithm selects the operational module, and disconnects the other module.

Thus, if only one module is installed, it is always the on-line module, and if a fault is detected in only one of the modules, the other module is always selected as the on-line module.

To reduce the frequency of flipping events in case of maintenance activities, the operator can define a minimum interval between flips.

Upon power-up, when it is found that both DCL.3 modules are fully operational, the redundancy control algorithm selects the module installed in slot DCL-A as the online module. The operator can always override the decision made by the redundancy control algorithm, and command the DXC-8R/DXC-30/DXC-30E to use a certain DCL.3 module.

DXC-8R, DXC-30 and DXC-30E periodically transfer the database from the currently on-line module to the other module, to ensure the off-line module is fully updated. In case a flip decision is made during a database transfer operation, the switching to the other module is delayed until database transfer is successfully completed. During the switching to the other module, short disruptions in the user traffic may occur, as the data streams are rerouted to the other DCL.3 module.

To avoid the transfer of erroneous data when the flip is caused by the detection of a checksum error in the database of the on-line module, no database transfer takes place after the detection of such an error. Thus, the existing database of the off-line module is used at the time of flipping. Since in general the database of the off-line module is updated, this should be enough to ensure that the system continues to operate normally.



Replacing the Faulty DCL.3 Module

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 before removing the faulty DCL module and then enable it again, once the new module is installed. To do this, follow the procedure described in DCL Redundancy on page 6-3.

Handling of Exceptional Conditions in the Common Logic Subsystem

To ensure maximum availability even in the unlikely event of malfunctions in both DCL.3 modules, the redundancy control algorithm analyzes in detail the states of the two DCL.3 modules, and always selects the module which can provide most of the critical functions.

For example, if a module is taken off-line due to either the detection of a minor malfunction or a temporary problem, the redundancy control algorithm will return that module on-line if a more serious problem occurs in the other module.

In general, when an error is detected in the database stored by the on-line DCL.3 module, the DXC-8R/DXC-30/DXC-30E should be loaded with the default parameters stored in the flash memory. After loading the default parameters, it is necessary to build the database anew. However, in many cases the off-line DCL.3 module may store the correct database, or a database that needs little modifications. For such cases, a special command is provided, to enable the user to transfer the database stored by the off-line module to the on-line module. Note that if the new database is not good, the user can always reload the default values.

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).

The system-level redundancy described above is actually a form of hardware redundancy.

• Combined line and hardware redundancy mode, also called dual-slot protection mode. This mode is supported by the DE3 and DT3 modules.

All these modes support the transmission of inband management traffic.

Note



Line Redundancy (Single-Slot Protection) Mode

The line redundancy, or single-slot protection, mode is primarily intended to increase the system availability in case an external link fails. It also enables maintaining service in case the port hardware failures at level.

Figure 3-2 shows a typical system configuration using the line redundancy mode. In this mode, the two ports of an I/O module are connected to two different links, and transmit in parallel the same data.

Note that this requires the user to install two separate lines to the network. Therefore, this mode is usually used to protect critical lines, for example, the line connecting the POP to the regional communication center, or other critical links.

The receive path of each module port receives the data from one of the two links, and evaluates its quality. The receive path which provides the best signal quality is selected, and is connected to the timeslot routing matrix located on the DCL.3 module. If the two ports provide similar signals, port 1 is selected.

In case the currently selected port fails, the signal received by the other port is automatically selected. After switching to the standby port, this port remains selected even after the previously selected port returns to normal operation. Switching will take place only when a problem occurs with the current port. Port switching is basically hitless, because both ports receive the same data.

Network

DE1B/DT1B or D8E1/D8T1 Module

E1 or T1Lines

DXC DXC

E1 or T1Lines

DE1B/DT1B or D8E1/D8T1 Module

Figure 3-2. Typical Line Redundancy Configuration

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).

Hardware (Y-Cable) Redundancy Mode

The hardware redundancy mode is primarily intended to increase the system availability in case of hardware failures. Figure 3-3 shows a typical system configuration using this redundancy mode for two DE1B or DT1B modules.

In this mode, two I/O modules of the same type, installed in different slots, are configured to operate as a redundancy pair.

The corresponding ports of two I/O modules are connected in parallel to the same link. The connection is made using a Y-cable, and at each time only the ports of one module (the on-line module) are physically connected to the external lines. Normally, the ports of the off-line module are disconnected from the external lines.

The user can specify a primary module (the other module included in the redundancy pair, called secondary module, is automatically configured with identical parameters, including timeslot routing, and its configuration cannot be modified).

In case a hardware failure occurs, the module generates the appropriate alarm, which is processed by the DCL.3 module. In response, the DCL.3 module sends software commands that switch all the communication from the failed module to the backup module. As a result, the functions of the two modules are interchanged (the on-line module is switched off-line, and vice versa). The on-line module is selected by evaluating the flip criteria (see the Flip Criteria section below). The whole process can take up to 1 second.

The user can override the automatic selection and manually select the on-line module by entering a special command.

Network

Redundant Pair(2 DE1B or DT1B Modules)

Y-Cable forPort 2DXC

Y-Cable forPort 1

Figure 3-3. Typical Hardware (Y-Cable) Redundancy Configuration



Combined Line and Hardware Redundancy (Dual-Slot Protection) Mode

The combined line and hardware redundancy mode, supported by DE3 and DT3 modules, is intended to increase the system availability in case of hardware failure, as well as in case the external E3 or T3 link fails.

Figure 3-4 shows a typical system configuration using the dual-slot protection mode.

TransportNetwork

E3 or T3 Modules

DXC Figure 3-4. Typical Combined Line & Hardware Protection Configuration

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.

Redundancy Flip Criteria

The redundancy flip criteria for I/O modules are stored and evaluated by the DCL.3 module.

Upon power-up or after reset, the DCL.3 module selects port 1 of the module configured for line redundancy, or the primary module for hardware or combined redundancy, to be on-line, and then starts evaluating the status of the redundant ports/modules in accordance with the redundancy flip criteria.

The redundancy flip criteria compare the relative severity of the problems detected on the two ports (line redundancy) or modules (for hardware redundancy), and select the port/module with the least severe problems to carry the traffic. For this purpose, the various problems are assigned weights, and the software selects the port/module with the smaller total of weights as the on-line port/module.

The weights depend on the port type. Table 3-3 lists the weights assigned to the various problems in each redundancy mode for external and internal E1 and T1 ports, and Table 3-4 lists the weights assigned to the various problems for E3 and T3 ports.



Table 3-3. Fault Weights for Redundancy Flipping – Internal and External E1 and T1 Ports

Weight Hardware Redundancy Mode Line Redundancy Mode

30 Override by manual command Override by manual command

25 I/O module removed Red alarm/local sync loss AIS AIS red alarm/AIS sync loss Loss of signal Network LLB Network PLB Management port is looped

20 Not used Multiframe red alarm CRC alignment loss Excessive error ratio Excessive bipolar violations

10 I/O module hardware failure Not used

5 Red alarm/local sync loss Yellow alarm/remote sync loss AIS AIS red alarm/AIS sync loss

Not used

Table 3-4. Fault Weights for Redundancy Flipping – E3 and T3 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

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.

Note


3-40 System Management

3.8 System Management

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


System Management 3-41

links. The DXC system supports both point-to-point and multidrop connections.

The supervision terminal is controlled by the program stored in the DXC control subsystem.

• SNMP Management. The SNMP management capability enables fully graphical, user-friendly management using the RADview network management stations offered by RAD, as well as management by generic SNMP-based management systems.

• Telnet. Remote management is also possible using the Telnet communication protocol, which enables management using IP communication in parallel with the use of SNMP. Telnet support enables a remote IP host to control the operation of the DXC system using functions identical to those provided by a supervision terminal.

Supervision Terminal Capabilities The supervision terminal provides a simple, command-line based human interface. The terminals can communicate with the managed DXC systems via the CONTROL serial RS-232 communication ports of DCL.3 modules.

The serial port is generally configured as a DCE port, for direct connection to a terminal, but can also be configured as a DTE port when it is necessary to connect the terminal via a modem link, or a low-speed data multiplexer channel. Thus, a remote operator located at a central site can perform all the functions available from a supervision terminal directly connected to the DXC system. Optional password protection is also available.

The communication data rate of the serial port can be selected in accordance with system requirements (300, 1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps). Automatic data rate identification (Autobaud function) is also available. Data word format is configurable (one start bit, seven or eight data bits, selectable parity (odd, even, or none), and one stop bit).

Since continuous communication with the DXC system is necessary only when management activities are actually performed, one terminal can manage multiple DXC units using a polling protocol, with the connection to the individual units being made by means of multi-drop modems or digital sharing devices. For polling purposes, each DXC can be assigned an eight-bit address, for a maximum of 255 nodes (the zero address is reserved for non-polled communication).

Serial Port Interface Characteristics The serial ports of DXC systems are located on the DCL.3 module, and have standard RS-232 asynchronous interfaces, which can be configured to operate as DCE or DTE.

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.

Two types of modems are supported: •

• Dial-up Hayes compatible modems, e.g., the RAD miniature DLM/AT modem.

• Multidrop modems, e.g., the RAD SRM-6 miniature multidrop modem.

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.

Serial Port Communication Parameters

DXC can communicate with the supervision terminal or modem at rates of 300, 1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps. The word format consists of one start bit, 7 or 8 data bits, and one stop bit.

Parity can be odd, even or disabled. Always make sure the communication interfaces of the terminal/modem and the DXC are configured for operation with the same parameters.

Handshaking Protocol with Supervision Terminals The handshaking between the DXC and the supervision terminal uses the control lines in the CONTROL supervisory port connector. Since the interface mode is selected by software, the direction of the interface signals is the same in both the DCE and DTE mode, and a cross cable is required for the DTE mode.

The control lines being used in each mode, and the direction of the control signals, are detailed in Table 3-5.



Table 3-5. Control Lines in CONTROL Connector

CONTROL Interface Mode CONTROL Line

DCE DTE

CTS Out Not used

DCD Out Out

DSR Out Out

DTR In In

RTS In In

Data Terminal Ready (DTR)

The supervision terminal sets the DTR line ON (active) to gain control over the DXC and start a configuration/monitoring session.

When the DTR line is OFF (inactive), terminal control ends. If password protection is used, the password must be entered again the next time the DTR line is set ON to start a new session.

Request to Send (RTS)

The RTS line is normally ON (active) when the supervision terminal is in session.

When the RTS line is OFF (inactive), the DXC interprets any data received from the terminal on the TD line as MARK.

Clear to Send (CTS)

The state of the CTS line is determined by the CTS parameter: ON The CTS line is always ON (active). =RTS The CTS line follows the RTS line.

Data Carrier Detect (DCD)

The state of the DCD line depends on the communication address (node number):

• When the node address is 0, the DCD line is always ON (active).

• When a non-zero node address is used, the DCD line becomes ON (active) when data is detected on the RD line, provided the DXC recognizes its own address in the data stream.

To simulate DTE operation, the delay between these events can be set by the user (by means of the DCD-DELAY parameter).

Data Set Ready (DSR) • Usually, the DSR line is configured to follow the DTR line. In this case, if the

supervisory port interface is DTE, the DSR line will be set to ON for 5 seconds when the RI line is ON while the DTR line is OFF.

• If the supervisory port interface is DCE, the DSR line can also be configured to be continuously ON. However, if the DTR line switches to OFF, the DSR line will also switch to OFF for 5 seconds.



In addition, the DXC always sets DSR OFF (inactive) for 5 seconds when the EXIT command is executed, or the disconnect time-out expires.

Handshaking Protocol with Dial-up Modem The dial-out mode is supported only by the MNG port, provided it is configured as DTE. The handshaking procedure between the DXC and a dial-up modem uses the control signals in the MNG connector, and is essentially similar to the handshaking with a terminal, except the directions of the control signals are reversed relative to their direction in the CONTROL connector when the CONTROL interface is set to DCE.

The control lines, and the direction of the control signals, in the MNG connector are detailed in Table 3-6.

Table 3-6. Control Lines in MNG Connector

MNG Interface Mode MNG Control Line

DCE DTE

CTS Out In

DCD Out In

DSR In Out

DTR Out In

RI Not used In

RTS In Out

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.

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.

Note



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.

Management Access through LANs and WANs DCL modules equipped with Ethernet ports can connect directly to Ethernet LANs, thereby enabling local management stations attached to the same LAN to access the DXC management subsystem.

The DCL.3 Ethernet port supports the IP protocol, and therefore provides convenient access for Telnet hosts and SNMP management stations.

The 10/100BaseT interface is wired as a station interface, and can be connected directly to an Ethernet hub port using a straight cable. The 10/100BaseT interface supports automatic detection of LAN rate.

SNMP and Telnet Management Access Options The control subsystem of DXC systems supports both out-of-band and inband management access.

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.

Inband Management Options

Inband management is available for HDSL, E1, T1, E3, and T3 ports. The bandwidth necessary for management can be selected by the user:

• When sufficient bandwidth is available, the user can dedicate a full timeslot to the management traffic. When using a dedicated timeslot, the user can also select the transmission method:

RAD proprietary protocol.

PPP HDLC encapsulation.

Frame relay encapsulation in accordance with RFC 1490. In this mode, management messages are encapsulated in frames with a fixed DLCI



(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.

Remote Management using Telnet over IP

The DXC system supports the Telnet communication protocol, which enables any IP host to access the DXC system supervision facility using TCP/IP communication. The Telnet user has access to the same command-line interface that is available to the user of a supervision terminal, however it uses the management topologies described above for SNMP.

Prevention of Access Conflicts

The DXC system has a dedicated mechanism that prevents access conflicts when more than one management mode is active.

Table 3-7 lists DXC response to multiple-access conditions.



Table 3-7. Handling of Management Access Conflicts

Response to Second Access Type of First Access Telnet

Inband Telnet Out-of-Band

Supervision Terminal

Telnet Inband – Ignored Message

Telnet Out-of-Band

Message – Ignored

Supervision Terminal

Disconnects the terminal

Not possible –

SNMP Management Capabilities

The DXC system includes an SNMP agent that can communicate out-of-band and/or inband through the dedicated management router of the DXC system. To permit SNMP management, the SNMP agent must be configured and enabled by the user. Appendix C provides information on the required parameters.

Usually, network management stations are attached to Ethernet LAN’s.

• For DXC systems equipped with DCL.3 modules with Ethernet ports, the DCL.3 Ethernet port can be directly connected to the same LAN (or to a LAN that can be reached by the network management station, e.g., through standard routers).

• For DXC systems equipped with DCL.3 modules without Ethernet ports, a remote access LAN extender can be used, as shown in Figure 3-5.

Serial Ports

To SupervisoryConnectors ofManaged Equipment

NetworkManagement

Station MBE/RAS/A

LAN

Figure 3-5. Connection of Network Management Station to Serial Out-of-Band DXC

Supervisory Ports

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.

DXC

E1 or T1

FCD

FCD

MEGAPLEX

FCD

FrameRelay

NetworkFrame Relay

RouterNetwork

ManagementStation

E1 or T1

E1 or T1

Figure 3-6. Inband Management Access

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.

Combining Inband and Out-of-Band Management Capabilities

Figure 3-7 shows a management system topology that illustrates the use of the various management access options supported by the DXC.

• The network management station is connected to the CONTROL port of the DXC system No. 1. The CONTROL port must be configured to support IP traffic, but since it is directly connected to the management station, this port is not required to route IP traffic (it need only let the traffic pass through - this mode is designated as the NMS SLIP mode). Thus, the local SNMP agent communicates out-of-band with the management station.

• 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.

• On DXC system No. 2, two management ports are enabled:

Inband communication through the port connected to DXC system No. 1.

Out-of-band communication through the CONTROL port, which is connected to the out-of-band management port of a Megaplex located near



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.

MEGAPLEX-2100F

A

CONTROL Connector(SLIP NMS)

NetworkManagement

Station

CONTROL Connector(SLIP Agent)

SP-DTE Connector(SLIP NMS)

DXC No. 1DXC No. 2

Figure 3-7. Management Topology Illustrating Use of Management Access Options

Supported by DXC

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.

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.

Note



Thus, an entire wide-area networks can be managed by means of a network management station connected to any DXC unit (or to any of the other RAD equipment which supports SNMP management).

Note that the network shown in Figure 3-8 can be managed by a single network management station, because the flexible routing capabilities of the SNMP agent permit the transfer of management traffic over many different paths; however, for completeness, two management stations are illustrated.

DXC-30 #1

To OtherSystems

RemoteCommunication

Node

DXC-30 #2

MEGAPLEX-2100B

MEGAPLEX-2100B

MEGAPLEX-2100F

SP-DCEConnector

LAN

NetworkManagement

Station

NetworkManagement

Station

MEGAPLEX-2100F SP-DTEConnector

To OtherSystems

TEST

MAJOR ALARM

MINOR ALARMSYSTEM

POWER SUPPLYCOMMON LOGICB A

ON LINE ON LINEB A

TEST

MAJOR ALARM

MINOR ALARMSYSTEM


ON LINE ON LINEB A

Figure 3-8. Extended Management Topology Using Network Management Stations


Diagnostics 3-51

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.

Evaluation of Transmission Performance To enable rapid evaluation of transmission performance, the DXC system can perform BER testing on links terminated at user-selected internal and external ports, using a wide range of test patterns. The BER test is also available on DIM modules.

The maintenance staff can also monitor the received data stream of any E1 or T1 port (including ports of DHL modules) by routing the desired timeslots to test equipment connected to another E1, T1, DHL, or DHS port. Multiple ports can be simultaneously monitored, each through a different test port. The monitoring does not interfere with the flow of payload traffic. Moreover, the monitoring can be performed by temporarily configuring any free port to serve as a test port.

Maintenance is further enhanced by advanced self-test capabilities, and by an automatically performed power-up self-test that provides circuit-level diagnostics data.

Indicators located on the front panel of the DXC enclosure and on the DCL.3 modules, alert the user when test loops are present in the system.

Loopbacks Supported by E3 and T3 Modules The E3 and T3 modules support the following types of loopbacks:

• E3 or T3 Port Loopbacks. The E3/T3 port supports two basic types of user-activated loopbacks:

Local loopback: the output signal of the T3 port is looped back to the input, and is returned toward the local DXC.

Remote loopback: the signal received by the T3 port is regenerated and looped back to the transmit path of the port, and is returned toward the remote equipment.

In addition, T3 ports support the network-activated line loopback, which is a remote loopback activated by commands received within the DS3 data stream.

• Internal Port Loopbacks. The internal E1 or DS1 ports support one type of user-activated loopback, the local loopback: the signal transmitted by a selected internal port is looped back, and returned toward the DXC bus.


3-52 Alarm Collection

Loopbacks Supported by Fractional STM-1 Modules The test and diagnostic functions supported by fractional STM-1 modules are as follows:

• External STM-1 Port Loopbacks: user-activated local and remote loopbacks.

• Internal E1 Port Loopbacks: user-activated local and remote loopbacks.

• Internal VC-12 Port Loopbacks and Tests: user-activated local loopbacks, and sending of simulated alarm indications.

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.

3.10 Alarm Collection

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.


Alarm Collection 3-53

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.


3-54 Transfer of Configuration Database

• Inversion of selected alarm indications provided to the local operator by the indicator on the equipment front panels, and the alarm relay state. “Inverted” alarms are ignored while they are present, therefore the system operator will be alerted only upon return to normal operation.

3.11 Software Updating

The DCL.3 module stores the software that determines the operational and management capabilities of the DXC system. The software is stored in flash memory, and thus it can be easily updated by downloading new software releases. Software is distributed on diskette.

New software can be loaded off-line, using any PC directly connected to a serial port of the DCL.3 module, or on-line (without stopping system operation), using TFTP (Trivial File Transfer Protocol), part of the IP suite of protocols, e.g., through one of the management links connected to a network management station.

In addition to the operational software stored in the DCL.3 module, each module has its own operating system, stored in firmware.

3.12 Transfer of Configuration Database

The configuration database of DXC systems, stored in the DCL.3 flash memory, can also be transferred by means of the TFTP protocol. The transfer of configuration files is made on-line, through the serial supervisory port located on the DCL.3 module, without stopping the operation of the DXC system.

Downloaded configuration data is stored in the DXC as the edited database, and therefore the local user or the network administration can check and edit the configuration data before writing it to the flash memory.

Network administrators can use this capability 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.

Introduction 4-1

Chapter 4 Installation and Operation

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.

The installation of other modules is covered by the corresponding module Installation and Operation Manual.

After completing equipment installation, it is necessary to configure the DXC. For instructions regarding system management (including the preliminary configuration activities) by means of an ASCII supervision terminal, refer to Chapters 5, 6 and Appendix F. After the preliminary configuration, DXC systems can also be managed using SNMP or Telnet.

In case a problem is encountered, refer to Chapter 7 for test and diagnostics instructions.

Chapter 4 Installation and Operation DXC-8R/10A/30/30E Installation and Operation Manual

4-2 Introduction

Safety Precautions

No internal settings, adjustment, maintenance, and repairs may be performed by either the operator or the user; such activities may be performed only by a skilled technician who is aware of the hazards involved. Always observe standard safety precautions during installation, operation, and maintenance of this product.

Laser Safety Classification

DXC modules equipped with laser devices comply with laser product performance standards set by government agencies for Class 1 laser products. The modules do not emit hazardous light, and the beam is totally enclosed during all operating modes of customer operation and maintenance.

The following label, located near the optical connectors, is used to indicate that the module is classified as a Class 1 laser product.

LASERKLASSE1CLASS 1LASER

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.

Laser Safety Statutory Warning and Operating Precautions

All the personnel involved in equipment installation, operation, and maintenance must be aware that the laser radiation is invisible. Therefore, although protective device generally prevent direct exposure to the beam, the personnel must strictly observe the applicable safety precautions and in particular must avoid looking straight into optical connectors, neither directly nor using optical instruments.

In addition to the general precautions described in this section, be sure to observe the following warnings when operating a product equipped with a laser device. Failure to observe these warnings could result in fire, bodily injury, and damage to the equipment.

To reduce the risk of exposure to hazardous radiation: • Do not try to open the enclosure. There are no user-serviceable components inside. • Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein. Allow only authorized RAD service technicians to repair the unit.

Warning

Warning

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 4 Installation and Operation

Site Requirements 4-3

Section I General

4.2 Site Requirements

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 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.

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.

Caution

Warning


4-4 Site Requirements

Power Supply Considerations The tables below list the power requirements for the DXC power supply and I/O modules:

• Table 4-1 lists the output values of the AC and DC power supply modules for different DXC chassis at 45°C (maximum ambient temperature).

• Table 4-2 lists the power consumption values for different I/O modules. Table 4-2 also states the current PCB revision and configuration letter of each I/O module.

Table 4-1. DXC Power Supply Output

Chassis/Power Supply Power Supply Output

DXC-30M-PS/AC 120W/24A

DXC-30M-PS/DC 120W/24A

DXC-30ME-PS/AC 188W/37.6A

DXC-30ME-PS/DC 185W/37A

DXC-10A/AC 60W/12A

DXC-10A/DC 75W/15A

DXC-8R/AC (NEW) 60W/12A

DXC-8R/DC (NEW) 72W/14.4A

The maximum power consumption of each DXC-30E backplane section is 26A (130W), for a total of 40A per DXC-30E.

Table 4-2. Power Consumption of DXC Modules

Module PCB Rev. Config. Letter

Power Consumption from +5V

DCL.3 0.0 G 1.5A

DE1B 0.3 H 0.6A

DT1B 0.3 H 0.6A

DHL/E1 0.3 F 1.8A

DHL/E1/2W 0.3 G 1.2A

DHS/V35 1.1 A 0.6A

DHS/530 1.1 B 0.5A

DHS/V24 1.1 A 0.4A

DHS/X21 1.1 B 0.4A

DHS/ETUR 1.1 A 0.6A

DHS/ETUB 1.1 B 1.7A

Note


Site Requirements 4-5

Table 4-2. Power Consumption of DXC Modules (Cont.)

Module PCB Rev. Config. Letter


DHS/DATA 0.1 F 0.6A

D8HS 1.0 A 1.9A

DIM/HSSI 0.1 F 1.9A

DIM/ETUB 0.1 B 1.55A

DIM/ETUR 0.1 A 1.3A

Other DIM Versions 0.1 F 1.1A

DE3 copper 0.0 C 1.2A

DE3 fiber 0.0 C 1.4A

DT3 copper 0.0 D 1.4A

DT3 fiber 0.0 D 1.6A

D8E1 0.1 D 1.4A

D8T1 0.1 F 1.4A

D4E1 0.1 D 1.14A

D4T1 0.1 F 1.14A

D8SL 0.0 A 3.7A

D8U 0.0 F 1.2A

D16U 0.0 F 1.5A

Single-port DFSTM-1 1.0 A 3.5A

Dual-port DFSTM-1 1.0 A 4.0A

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.

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.

Note


4-6 Connection Requirements

Protection against ESD An electrostatic discharge occurs between two objects when an object carrying static electrical charges touches, or is brought near enough, the other object. Static electrical charges appear as result of friction between surfaces of insulating materials, separation of two such surfaces and may also be induced by electrical fields. Routine activities such as walking across an insulating floor, friction between garment parts, friction between objects, etc. can easily build charges up to levels that may cause damage, especially when humidity is low.

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. If you are not using a wrist strap, before touching a module, it is recommended to discharge the electrostatic charge of your body by touching the frame of a grounded equipment unit.

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.

Electromagnetic Compatibility Considerations The DXC is designed to comply with the electromagnetic compatibility (EMC) requirements of Sub-Part J of FCC Rules, Part 15, for Class A electronic equipment, and additional applicable standards.

To meet these standards, it is necessary to perform the following actions:

• Connect the DXC case to a low-resistance grounding system.

• Install blank panels to cover all empty slots. Appropriate blank panels can be ordered from RAD.

Covering all empty slots is also required for reasons of personal safety, and to ensure proper flow of cooling air within DXC enclosures.

4.3 Connection Requirements

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.

Caution

Warning


Connection Requirements 4-7

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

External (Station) Clock Connections The DCL.3 module includes the external (station) clock interface of the DXC chassis. This interface, located in the RJ-45 STATION CLK connector, can accept 2.048 MHz or 1.544 MHz signals, in accordance with the frequency selected by software commands. Two external clock interfaces are located on the module:

• 120Ω balanced interface, terminated in an eight-pin RJ-45 connector wired in accordance with Appendix A. This connector also includes the connections to the alarm relay contacts.

• 75Ω unbalanced interface, terminated in a BNC connector.

External clock interface characteristics comply with ITU-T Rec. G.703 or RS-422, according to software selection. The balanced or unbalance interface is selected by jumpers. To simplify the external clock connections in case DCL.3 redundancy is used, the DCL.3 module automatically disconnects the clock interface of the standby module from its STATION CLK connector, leaving only the active module connected to the external lines. This enables to connect the external clock in parallel to both modules, by means of a Y-cable. When using DCL.3 redundancy, a Y-cable can be used to connect in parallel to both DCL.3 modules.


4-8 Connection Requirements

Dry-Contact Alarm Relay Connections The dry-contact alarm interface is included in the RJ-45 STATION CLK connector. The relay is controlled by software, and therefore the default state (i.e., the contact closed to pin 4 during normal DXC operation) can be selected by the user in accordance with its specific requirements. Note however that when the DCL.3 module is not powered, the relay state is always as listed in Appendix A (pin 7 connected to pin 4), irrespective of the software selection. To simplify the connections to the alarm relay in case DCL.3 redundancy is used, the DCL.3 module automatically disconnects the alarm relay contacts of the standby module from its STATION CLK connector, leaving only the active module connected to the external lines. This enables to connect external alarm monitoring equipment in parallel to the alarm relay contacts of both modules, by means of a simple Y cable.

The alarm relay contacts are rated at maximum 60 VDC across open contacts, and maximum 1 ADC through closed contacts. Protection devices must be used to ensure that these ratings are not exceeded, e.g., use current limiting resistors in series with the contacts, and place voltage surge absorbers across the contacts.

External Alarm Input The RJ-45 STATION CLK connector of the DCL.3 module also includes an external alarm input, which enables monitoring the status of an external alarm sensor. This input accepts contact closure to ground, or a signal at RS-232 levels. To simplify the connections to the external alarm input in case DCL.3 redundancy is used, the DCL.3 module automatically disconnects the alarm input of the standby module from its STATION CLK connector, leaving only the active module connected to the external line. This enables to connect the external sensor in parallel to both modules by means of a Y cable.

Management Port Connections DXC systems have two types of out-of-band management ports, located on the DCL.3 modules:

• Supervisory port. This port has a 9-pin D-type connector with RS-232 interface. The interface (DCE or DTE) is software selectable. The default selection, DCE, enables direct connection to terminals and management stations; when the interface is configured as DTE, it is necessary to use an cross-cable.

• Network port, for connection to network management stations. DCL.3 modules are available with three types of network interface options:

9-pin D-type connector with user-selectable RS-232 DTE or DCE interface. When configured as a DTE interface, the network port can be used as a dial-out port, for direct connection to modems; when configured as a DCE interface, the network port can be used for direct connection to terminals and management stations.

Caution


Installation of DXC-30 Enclosure 4-9

10/100BaseT Ethernet interface with RJ-45 connector, for connection to LANs operating on UTP or STP media. The connector is wired for connection through a “straight” (point-to-point) cable to a hub port.

Appendix A provides the pin allocation for the connectors.

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.

Section II Installation and Operation of DXC-30 Enclosure

4.4 Installation of DXC-30 Enclosure

General Description of DXC-30 Enclosure The DXC-30 enclosure has 19 module slots. The modules are inserted from the rear side. Four slots are assigned to the system modules. Two slots each are assigned for modules type DCL.3 and DPS, respectively, to provide support for the redundancy option:

• System slots PS-A and PS-B: for DXC-30M-PS/AC and DXC-30M-PS/DC/N 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 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.

Note


4-10 Installation of DXC-30 Enclosure

2PS-B

1PS-A

1

I/O Slots2 3 4 5 9876 14 1513121110

RS-5

30/V

.35

RS-5

30/V

.35

CH1

CH2

System Slots

PowerSupply

RedundantPowerSupply

(Option)Redundant

DCL(Option)

DCL


Common LogicModules (DCL)

I/O Modulesas Required

RL

LOS

1

2

SOL

L R

2

1

RS-5

30/V

.35

RS-5

30/V

.35

CH1

CH2

IN

TUO

OUT

IN

RL

LOS

1

SOL

L R

2

RL

LOS

1

2

SOL

L R

TUO

OUT

IN

RL

LOS

1

SOL

L R

2

IN

TUO

OUT

IN

R

LOS

1

SOL

L R

2

2

1

RS-5

30/V

.35

RS-5

30/V

.35

CH1

CH2

RL

LOS

1

2

SOL

L R

TUO

OUT

RL

LOS

1

SOL

L R

2

IN

IN

TUO

OUT

RL

LOS

1

SOL

L R

2

IN

IN

RL

LOS

2

1

SOL

L R

CH2

CH1

RS-5

30/V

.35

RS-5

30/V

.35

1

2

2

RL

LOS

1

SOL

L R

TUO

OUT

IN

IN

2

1

RS-

530/

V.35

RS-

530/

V.35

CH1

CH2

10I/O 6 DHS

3CL-A DCL.3

4CL-B DCL.3

5I/O 1

6I/O 2 DHS

7I/O 3 DE1

8I/O 4 DT1

9I/O 5 DE1

11I/O 7 DE1

12I/O 8 DHS

13I/O 9 DT1 10I/O

14

DE1

15I/O 11 DE1 I/O 12

16

DT1 13I/O17

DHS 14I/O18

DE1 15I/O19

DHS

CAUTION: FOR CONTINUEDPROTECTION AGAINST RISK OF

FIRE, REPLACE ONLY WITH SAMETYPE AND RATING OF FUSE.

POWER

DPS

LK

DXC-30M-PS/DC/N

POWER

DPS

-48

0

VDC-IN

MJALM

MN

S

AT

ON

C

T

I

CONTROL

12

ONETHERNET

TST

ON MJALM

MN

S

AT

ON

CLK

T

I

CONTROL

12

ONETHERNET

TST

ON

Figure 4-1. DXC-30 Enclosure, Typical Rear View

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.

TEST

MAJOR ALARM

MINOR ALARMSYSTEM


ON LINE ON LINEB A

Figure 4-2. DXC-30 Enclosure Front Panel


Installation of DXC-30 Enclosure 4-11

Table 4-3. DXC-30 Front Panel Indicators

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)

Dangerous voltages may be present inside the DXC-30 enclosure when it is connected to power and to external cables. Do not connect cables to the DXC-30 before it is properly installed. Always connect the power cable first, and then other cables which are specified for connection to the DXC-30.

DXC-30 Enclosure Installation Procedure The DXC-30 enclosure is intended for installation in 19-inch racks. Although the DXC-30 can also be installed on shelves and desktops, this is not allowed when a DFSTM-1, D8SL or certain types of DIM modules are installed in the DXC-30, because in this case a fan tray must be installed under the DXC-30. Refer to Section 4.8 for fan tray installation instructions.

For rack installation, it is necessary to install two brackets with handles to the sides of the unit. The rack mount installation kit, RM-DXC30, is supplied with the unit. As illustrated in Figure 4-3, you may install the brackets in two ways, to orient the unit in accordance with your requirements (either with the DXC-30 front panel toward the front of the rack, or with the module panels toward the front).

After attaching the brackets, fasten the enclosure to the rack by four screws (two on each side).

In general, DXC-30 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 the DPS modules - in Section 4.5.

• For the DCL.3 module - in Section 4.6.

• For other modules - in the corresponding module Installation and Operation Manual.

Warning


4-12 Installation of DPS Modules

Install Brackets Here ifYou Want the Front Panel

toward the Front of the Rack

Install Brackets Here ifYou Want Access to Module Panels

from the Front of the Rack

Figure 4-3. Attachment of Brackets to DXC-30

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.

4.5 Installation of DPS Modules

Dangerous voltages may be present inside the DPS module when it is connected to power. Do not connect the DPS module to power before it is properly installed within the DXC-30 enclosure, and disconnect the input power from the module before removing it from the enclosure. The installation and preparation of the module shall be done by a skilled technician who is aware of the hazards involved.

Module Panels Typical panels of DPS modules are shown in Figure 4-4. Table 4-4 describes the functions of the panel components.

Warning


Installation of DPS Modules 4-13

DXC-30M-PS/DC/NDXC-30M-PS/AC

Label

DC PowerConnector

ON/OFF Switchand

Power Indicator

DXC-30M-PS/DC/N

POWER

DPS

-48

0

VDC-IN

GroundingScrew

ON/OFF Switchand

Power Indicator

Label

GroundingScrew

CAUTIONPROTECTION AGAINST RISK OF


FOR CONTINUED:

3.15A F 250V100-240VAC

DXC-30M-PS/AC

POWER

DPS

Fuse

AC PowerConnector

Figure 4-4. DXC-30M-PS/AC and DXC-30M-PS/DC Module Panels

Table 4-4. DPS Module Panels

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



Jumper JP3 FGND = DGND

Digital GroundConnectedto Frame Ground

Digital GroundNot Connectedto Frame Ground

NO

YES

YES

NO

JP3

Figure 4-5. DC-Powered DPS Module, Location of Internal Jumper

Jumper P101 FGND = DGND

Digital GroundConnectedto Frame Ground

Digital GroundNot Connectedto Frame Ground

YES

NO

Figure 4-6. AC-Powered DPS Module, Location of Internal Jumper

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.


Installation of DCL.3 Module 4-15

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.

4.6 Installation of DCL.3 Module

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.

Figure 4-7. Module DCL.3 Panels

DCL.3 withRS-232 Interface

DCL.3 with10Base2 Interface

DCL.3 with 10BaseTor 10/100BaseT Interface

K

N

CL

IO

T

TA

S

ALMMJ

MN TST

ON

K

CL

I

NO

T

TA

S

ALM

DCL.3

MJ

MN TST

ON

K

I

LC

ON

T

TA

S

ALM

DCL.3

MJ

MN TST

ON

T

L

RO

NOC

MNG N

TE

E

ER

TH

T

L

RO

NOC

N

TE

E

ER

TH

T

L

RO

NOC

DCL.3

12

ON 12

ON

Table 4-5 describes the functions of the panel components.

Note


4-16 Installation of DCL.3 Module

Table 4-5. DCL.3 Modules Panel Components

Item Function

CONTROL Connector

9-pin D-type female connector, for connection to an ASCII supervision terminal, network management station, or RS-232 CONTROL port of another module. Connector pin allocation is given in Appendix A.

DIP Switch (on DCL.3 versions with Ethernet interface)

Used to control supervisory port parameters.

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 (on DCL.3 versions with RS-232 interface)

9-pin D-type female connector, for connection to a modem (needed to support the dial-out function), or RS-232 supervisory port of another module. Connector pin allocation is given in Appendix A.

ETHERNET connector (on DCL.3 versions with Ethernet interface)

RJ-45 connector for 10/100BaseT interface, enables connection to Ethernet LAN.

Connector pin allocations are given in Appendix A.

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 Connectors

One RJ-45 connector and one BNC coaxial connector, for connection to an external (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).



Main Board Settings

The DCL.3 main board has several user-selectable jumpers (JP1, JP2, JP3, and JP4). Their locations are shown in Figure 4-9. Table 4-6 describes their functions.

Do not change the position of any other module jumpers (factory settings).

In addition to the jumpers listed above, the main board has an eight-section DIP switch, S1.

Table 4-6. Module DCL.3, Main Board User Settings

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


4-18 Installation of DCL.3 Module

Table 4-6. Name of Table (Cont.)

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 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.

RS-232 Interface Board Settings

The RS-232 interface board includes selectors for the selection of the interface type, DTE or DCE. The default selection is DTE, used for connection through modems. The DCE option enables direct connection to a network management station.

Figure 4-8 shows the location of the interface selectors, S1 and S2, on the RS-232 interface board. Both selectors must always be set to the same position.

S1

S2

DTE

DCEDTE

DCE

S1

S2

S1

S2

S1,S2 - Interface TypeDTE DCE

Figure 4-8. Module DCL.3 – RS-232 Interface Board Settings

Note



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.

DB INITPASSWRD

DEBUG 1WTCHDOG

PC/SPDP MNG

DP SPSW LOAD

OFF ON

JP4

NO

YESRXGND

JP1 NO

YES

FGND

JP3

UNBAL

BAL BAL

JP2

UBL

ResetPush-Button

S1

RESET

JP1

Pins 3, 6 in STATIONCLK ConnectorConnected toFrame GroundYES

JP1 NO

Jumper JP1 FGND

Pins 3, 6 in STATIONCLK Connectornot Connected toFrame Ground

JP4STATION CLK BNCShield not Connectedto Frame Ground

NO

JP4YES

Jumper JP4 RXGND

STATION CLK BNCShield Connectedto Frame Ground

Balanced(RJ-45)

JP3 JP2

BALBAL

JP3 JP2UBL

UNBAL

Unbalanced(BNC)

Station Clock InterfaceJumpers JP2, JP3

SW1

Figure 4-9. Module DCL.3, Main Board Settings


4-20 Installation of Optional Fan Tray

Replacing a Faulty DCL.3 Module When replacing a faulty DCL.3 module during DXC operation, short data disruption may occur. The procedure to follow to avoid this data disruption depends on the state of the DCL.3 module when it is removed from the chassis: offline or online.

• If the DCL.3 is to be replaced after a redundancy flip has occurred, the faulty module is offline. The procedure to follow in this case is described in DCL Redundancy on page 6-6.

• If the DCL.3 module that has to be replaced is the one which is currently online, perform the RESET command from the supervision terminal, wait until the flip occurs, and then replace the module using the procedure described in DCL Redundancy on page 6-6.

4.7 Installation of I/O Modules

Selection of I/O Slots When installing I/O modules in a DXC-30 chassis, it is recommended to consider the need to permit future expansion, for example, the need to install additional modules in the chassis. As explained in the Automatic Timeslot Allocation Algorithm section in Chapter 3, when Type 2 I/O modules (modules which use dynamic timeslot allocation) are installed in the chassis, a short disruption may occur when the internal timeslot allocation is changed. In many cases, it is possible to avoid such traffic disruptions by installing modules in I/O slots identified by means of the DSP BUS command.

To maximize flexibility, 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 leave additional empty I/O slots for future expansion after the last I/O slot occupied by a Type 1 module.

Installation Procedures Refer to corresponding module Installation and Operation Manual.

4.8 Installation of Optional Fan Tray

This section provides a description of the fan tray and installation instructions.

Fan Tray Description The fan tray is a 1U high unit supplied with brackets for installation in 19” racks, which must be installed just under the DXC-30 or DXC-30E when a DFSTM-1, D8SL or certain types of DIM modules are installed in the chassis. Leave at least 1U free space under the fan tray.


Installation of Optional Fan Tray 4-21

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.

PWR ALM

COM

N/O N/C

FAN-TRAY

~100-240 VAC 2A T 250V A. AC-Powered Fan Tray

PWR ALM

COM

N/O N/C

VDC-IN

0 -48

FAN-TRAY

B. DC-Powered Fan Tray

Figure 4-10. Fan Tray Front Panels

Table 4-7. Fan Tray Front Panel Components

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

Installation of Fan Tray Before installing the fan tray, carefully inspect the interior to detect and remove any foreign objects that may have entered the tray through the air inlets.

The fan tray must be installed just under the DXC-30 chassis.


4-22 Cable Connections

4.9 Cable Connections

BEFORE SWITCHING ON THIS EQUIPMENT, the protective ground terminals of this instrument must be connected to the protective ground conductor of the (mains) power cord. The mains plug shall only be inserted in a socket outlet provided with a protective ground contact. The protective action must not be negated by use of an extension cord (power cable) without a protective conductor (grounding). Any interruption of the protective (grounding) conductor (inside or outside the instrument) or disconnecting the protective ground terminal can make this instrument dangerous. Intentional interruption is prohibited. Make sure that only fuses of the required rating are used for replacement. The use of repaired fuses and the short-circuiting of fuse holders is forbidden. Whenever it is likely that the protection offered by fuses has been impaired, the instrument must be made inoperative and be secured against any unintended operation.

Grounding

Connect a short, thick copper braid between the grounding screw on each DPS module panel and a nearby grounding point.

Power and Feed Connections

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.

Warning

Caution


Cable Connections 4-23

When redundant power supplies are used, it is recommended to connect the power cables to outlets powered by different circuits.

Connection of External Feed and Ring Voltages

If the DXC-30 includes ISDN “U” interface modules, for example, D8U, it may be necessary to supply external feed voltages.

The recommended source for external voltages is the Ringer-2000 offered by RAD. The Ringer-2000 is a standalone unit intended for rack mounting, capable of providing power for up to twenty voice channels. Refer to the Ringer-2000 Installation and Operation Manual for connection instructions.

Turn on the Ringer-2000 external voltage source, or connect the external voltages, only after the DXC-30 is turned on. Always turn the Ringer-2000 or the external voltage source off before removing and installing an ISDN module in any connected chassis. After the module has been installed/removed, the Ringer-2000 can be turned back on.

Connections to DCL.3 Modules This section provides information on the connections required by the various DCL.3 module versions.

When two DCL.3 modules are installed in the chassis, for redundancy, you can connect the corresponding connectors on the two modules in parallel. For example, you can use Y-cables, because at any time the standby module is automatically disconnected from the external lines.

Connection Data for CONTROL Connector

The CONTROL connector is an RS-232 asynchronous DCE port, terminated in a 9-pin D-type female connector, intended for direct connection to terminals. Since terminals usually have DTE interfaces, the connection to this port is made by means of a straight-through cable. For connection to a modem, you need a cross cable (also called null modem cable).

Connection Data for MNG Connector

The MNG connector is an RS-232 asynchronous DTE port terminated in a 25-pin D-type male connector, intended for direct connection through a straight-through cable to a modem. The connector also includes the alarm relay contacts.

Connection Data for ETHERNET Connectors

The ETHERNET connector is wired as a station port, and can be connected directly to an Ethernet hub port using a straight cable.

Connection to the Station Clock Connectors

DCL.3 modules have two station clock connectors:

• BNC connector with unbalanced ITU-T Rec. G.703 Para. 6 interface

• RJ-45 connector, with balanced ITU-T Rec. G.703 Para. 6 interface.

Note

Caution



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.

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.

Connection to I/O Modules Refer to corresponding module Installation and Operation Manual.

Connections to Optional Fan Tray

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

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.

Connecting the Fan Tray Alarm Cable

The DCL.3 modules installed in the DXC-30 can monitor the alarm indication provided by the fan tray. For this purpose, the normally-open contacts of the fan tray alarm relay must be connected to the external alarm input (pins 5 and 6) in the DCL.3 RJ-45 STATION CLK connector.

The connection to the fan tray connector is made by means of a male mating header. The male connector has three screw terminals for the connection of the external alarm cable conductors.

Caution

Caution


DXC-30 Operating Instructions 4-25

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.

Figure 4-11. Typical Connection to Relay Connectors Mating Header

Common Contact (COM) :Connect to Pin 6

N/O Contact:Connect to Pin 5

Alarm Cableto DCL.3

RJ-45 STATIONCLK Connector

4.10 DXC-30 Operating Instructions

This section provides operating instructions for a DXC-30 enclosure prepared for operation and installed in accordance with the previous sections.

Turn-on is generally performed after installing all the prescribed modules in the DXC-30 enclosure, i.e., including I/O modules, as explained in the individual module Installation and Operation Manuals. However, you may also carry out the following instructions on a DXC-30 enclosure equipped only with DPS and DCL.3 modules. Modules may be installed and removed while the DXC-30 is powered on, provided that all the safety precautions listed in the installation procedures of the corresponding module are strictly observed. In particular, disconnect all the cables connected to a module before removing/inserting it in the DXC-30.

For your safety, make sure the DXC-30 grounding complies with the requirements listed in Section 4.2.

Note

Warning

Caution


4-26 DXC-30 Operating Instructions

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.

Normal Front-Panel Indications After turn-on, DXC-30 performs the power-up self-test. During this interval, the ON, MAJOR, MINOR and TEST indicators flash, for test purposes.

After successful completion of the power-up self-test, the DXC-30 starts operating in accordance with the configuration parameters prepared by means of the supervision terminal, or a network management station. Refer to Chapters 5 and 6 for instructions on the use of the supervision terminal.

Observe the following indications:

• The MAJOR ALARM and MINOR ALARM indicators must turn off. The TEST indicator should turn off, but may turn on if a test or loopback has been activated.

• The ON-LINE indicators of the DPS 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-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.


Installation of DXC-30E Enclosure 4-27

Section III Installation and Operation of DXC-30E

Enclosure

4.11 Installation of DXC-30E Enclosure

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.

OUT

IN

2

LOS

L R

OUT

IN

1

LOS

L RDE1/B

MJ

MN TST

ON

CONTROL

ETHERNET

ALM

STATION

CLK

DCL.26PS-A PS-B

1 2I/OCL-B I/O 1

3 4 5I/O2 3 I/O 54 I/O I/O

76 8 9 107I/O I/O 8 I/O 9 10I/O

11 12 13 14I/O 11 I/O 12 I/O 13 I/O 14

15 16 17 18I/O 15

19

2

1

DE1/B

LOSL R

L RLOS

LINK

1

DT1

RL

LOS

LINK

2

RL

LOS

TX

RX

TX

RX

RL

LOS

RL

LOS

DT1

LINK

1

TX

RX

LINK

2

TX

RX

LINK

1

DE1

RL

LOS

LINK

2

RL

LOS

TX

RX

TX

RX

DIMDCE-10BT

10 BASE-T

TX RX

COLL LINK

RL

LOS

RL

LOS

DE1

LINK

1

TX

RX

LINK

2

TX

RX

HDSL

RL

LOS

RL

LOS

DE1

HDSL

DIMDCE-V35

V.35

DPSDXC-30EM-PS/DC

48V

POWER

CAUTION: FOR CONTINUEDPROTECTION AGAINST RISK OF

FIRE, REPLACE ONLY WITH SAMETIPE AND RATING OF FUSE

DXC-30M-PS/AC100-240VAC

3A T 250V

POWER

DPS

MJ

MN TST

ON

CONTROL

ETHERNET

ALM

STATION

CLK

DCL.2CL-A

OUT

IN

2

LOS

L R

OUT

IN

1

LOS

L RDE1/B

LINK

1

DT1

RL

LOS

LINK

2

RL

LOS

TX

RX

TX

RX

LINK

1

DE1

RL

LOS

LINK

2

RL

LOS

TX

RX

TX

RX

LINK

1

DE1

RL

LOS

LINK

2

RL

LOS

TX

RX

TX

RX

DIMDCE-V35

V.35

HDSL

RL

LOS

RL

LOS

DE1

HDSL

ON12

ON12

CHASSISGND

+_

Figure 4-12. DXC-30E Enclosure, Typical Rear View


4-28 Installation of DXC-30E Enclosure

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.

TEST

MAJOR ALARM

MINOR ALARMSYSTEM


ON LINE ON LINEB A

Figure 4-13. DXC-30E Enclosure Front Panel

Table 4-8. DXC-30E Front Panel Indicators

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)


Installation of DXC-30E Enclosure 4-29

Dangerous voltages may be present inside the DXC-30E enclosure when it is connected to power and to external cables. Do not connect cables to the DXC-30E before it is properly installed, and always connect the power cable first, and then other cables which are specified for connection to the DXC-30E.

Installation of DXC-30E Enclosure The DXC-30E enclosure is intended for installation in 19" racks, however it can also be installed on shelves and desktops.

For rack installation, it is necessary to install two brackets with handles to the sides of the unit. The rack mount installation kit, RM-DXC30E, is supplied with the unit. As illustrated in Figure 4-14, you may install the brackets in two ways, to orient the unit in accordance with your requirements (either with the DXC-30E front panel toward the front of the rack, or with the module panels toward the front).




From the Front of the Rack

Figure 4-14. Attachment of Brackets to DXC-30E

After attaching the brackets, fasten the enclosure to the rack by four screws (two on each side).

Warning



In general, the DXC-30E 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 the DPS modules – in Section 4.12.

• For the DCL.3 module – in Section 4.13.

• For other modules – in the Installation and Operation Manual for the corresponding module.

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.

4.12 Installation of DPS Modules

Dangerous voltages may be present inside the DPS module when it is connected to power. Do not connect the DPS module to power before it is properly installed within the DXC-30E enclosure, and disconnect the input power from the module before removing it from the enclosure. The installation and preparation of the module shall be done by a skilled technician who is aware of the hazards involved.

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

Warning


Installation of DPS Modules 4-31

Figure 4-15. DXC-30ME-PS/AC and DXC-30ME-PS/DC Module Panels

DXC-30ME-PS/DC

DXC-30M-PS/AC100-240VAC

5A T 250V

POWER

DPS

CAUTIONPROTECTION AGAINST RISK OF


FOR CONTINUED:

DPS

POWER

CHASSISGND

DXC-30ME-PS/AC

AC PowerConnector

Fuse

Label

GroundingScrew

ON/OFF Switchand

Power Indicator

DXC-30EM-PS/DC48V

+_

DC PowerConnector

Label

GroundingScrew

ON/OFF Switchand

Power Indicator

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.



Jumper JP1 DGND = FGND

FGND

DGND

JP1

Digital Ground Connectedto Frame Ground

Digital Ground NotConnected to Frame Ground

Cooling Fan Fuse F5(1A Fast Blow)

Cooling Fan

F3

F4

F1

F2

DC InputFuses F1, F2

(Only for 48 DC Powered Modules)

InternalFuses F3, F4(Only for AC

Powered Modules)

Setting the jumper to NO mayrender the equipment unsafe forconnection to unprotectedtelecommunication networks incertain locations wherepermanent excessive voltagesare present on the line.

Figure 4-16. DPS Modules, Location of Internal Jumper and Fuses

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.

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.

4.13 Installation of DCL.3 Module

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.

Note


4-34 Installation of Fan Tray

Figure 4-17. Module DCL.3 Panels

MJ

MN TST

ON

DCL.3 with 10BaseT or10/100BaseT Interface

T

K

N

CL

IO

T

TA

S

ALM

L

RO

NOC

DCL.3

MNG

DCL.3 withRS-232 Interfaces

MJ

MN TST

ON

T

N

C

IO

N

T

TA

S

ALMTE

HER

TE

L

RO

NOC

DCL.3

12

ON


Refer to Section 4.7 for guidelines.

4.15 Installation of Fan Tray

Refer to Section 4.8 for guidelines.


DXC-30E Operating Instructions 4-35


Use the procedures described in Section 4.9 for the DXC-30 chassis.

4.17 DXC-30E Operating Instructions

This Section provides operating instructions for a DXC-30E enclosure prepared for operation and installed in accordance with the previous sections.

Turn-on is generally performed after installing all the prescribed modules in the DXC-30E enclosure, i.e., including I/O modules, as explained in the module Installation and Operation Manuals. However, you may also carry out the following instructions on a DXC-30E enclosure equipped only with DPS and DCL.3 modules. Modules may be installed and removed while the DXC-30E is powered on, provided all the safety precautions listed in the installation procedures of the corresponding module are strictly observed. In particular, disconnect all the cables connected to a module before removing/inserting it in the DXC-30E.

For your safety, make sure the DXC-30E grounding complies with the requirements listed in Section 4.2.

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.

Normal Front-Panel Indications After turn-on, the DXC-30E performs the power-up self-test. During this interval, the ON, MAJOR, MINOR and TEST indicators flash, for test purposes. After successful completion of the power-up self-test, DXC-30E starts operating in accordance with the configuration parameters prepared by means of the supervision terminal, or a network management station. Refer to Chapters 5 and 6 for instructions on the use of the supervision terminal.



Note

Warning


4-36 Installation of DXC-10A Enclosure

• 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.


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.

Section IV Installation and Operation of DXC-10A Enclosure

4.18 Installation of DXC-10A Enclosure

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 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.

Note


Installation of DXC-10A Enclosure 4-37

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.

I/O Slot 3

Fuse

GroundingScrew

Power SupplyUnit

I/O Slot 1

DCL.3 Module

I/O Slot 2 I/O Slot 5 I/O Slot 4

I/O 2

I/O 3

RL

L O S

21

SOL

LR

DT1

DT1 R

L

L O S

1 2

SOL

LR

DH

S

I/O 4

I/O 5

POWER

I/O 1

100-240V 2A T 250V

RS-530/V.35

2

RS-530/V.35

1

CL

S T A T I O N C L KALM MJ

MN

TST

ON

E T H E R N E TC O N T R O L

DC

L.3

1 2O

N

I/O 2

I/O 3

DT1

DH

S

I/O 1

100-240V 2A T 250V

CL

POWER

DC

L.3

MN

ALM

MJ

TST

ON

C O N T R O L E T H E R N E T

1 2O

N

S T A T I O N C L K

2

RL

L O S1SOL

LR

DE

1

TUO O U TI N I N

2

RL

L O S1SOL

LR

DE

1

TUO O U TI N I N

2

RL

L O S1SOL

LR

DE1

TUO O U TI N I N

Figure 4-18. AC-Powered DXC-10A, Rear View


4-38 Installation of DXC-10A Enclosure

I/O Slot3Grounding

ScrewPower Supply

UnitI/O Slot

1I/O Slot

2I/O Slot

5I/O Slot

4

I/O 2

I/O 3

RL

L O S

21

SOL

LR

DT1

DT1 R

L

L O S

1 2

SOL

LR

DH

S

I/O 4

I/O 5

I/O 1

RS-530/V.35

2

RS-530/V.35

1

C LD

CL.

3

POWER

DCL.3Module

VDC-IN

-48-240

S T A T I O N C L KALM

MJ

MN

TST

ON


1 2O

N

I/O 2

I/O 3

DT1

DH

S

I/O 1

CL

POWER

DC

L.3

MN

ALM

MJ

TST

ON

C O N T R O L E T H E R N E T

1 2O

N

S T A T I O N C L K

VDC-IN

-480 -24

2

RL

L O S1SOL

LR

DE

1

TUO O U TI N I N

2

RL

L O S1SOL

LR

DE1

TUO O U TI N I N

2

RL

L O S1SOL

LR

TUO O U TI N I N

DE1

Figure 4-19. DC-Powered DXC-10A, Rear View

Front Panel

Figure 4-20 shows the front panel of the DXC-10A enclosure.

TEST

MAJOR ALARM

MINOR ALARMSYSTEM

POWER SUPPLY

Figure 4-20. DXC-10A Enclosure Front Panel

Table 4-10 lists the functions of the indicators located on the DXC-10A front panel.

Table 4-10. DXC-10A Front Panel Indicators

Control or Indicator Function

TEST indicator Indicates that a test (or test loop) is being performed on one of the local DXC-10A modules

MAJOR ALARM indicator Indicates that a major fault has been detected in one of the DXC-10A modules

MINOR ALARM indicator Indicates that a minor fault has been detected in one of the DXC-10A modules

POWER Power supply is turned on and operates properly


Installation of DXC-10A Enclosure 4-39

Dangerous voltages are present inside the DXC-10A enclosure when it is connected to power and to external cables. Do not connect cables to the DXC-10A before it is properly installed. Always connect the power cable first, and then other cables which are specified for connection to the DXC-10A.

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).





Figure 4-21. Attachment of Brackets to DXC-10A

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.

Warning


4-40 DXC-10A Operating Instructions


Section 4.7 describes considerations regarding the selection of I/O slots for installation of I/O modules.

If you are planning to work with Type 2 I/O modules under dynamic timeslot allocation mode (see Timeslot Allocation to Type 2 (Dynamic Allocation) Modules in Chapter 3 for reference), 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.



4.21 DXC-10A Operating Instructions

This section provides operating instructions for a DXC-10A enclosure prepared for operation and installed in accordance with the previous sections.

Turn-on is generally performed after installing all the prescribed I/O modules in the DXC-10A enclosure, as explained in the module Installation and Operation Manuals. However, you may also carry out the following instructions on a DXC-10A enclosure without additional modules. Modules may be installed and removed while the DXC-10A is powered on, provided all the safety precautions listed in the installation procedures of the corresponding module are strictly observed. In particular, disconnect all the cables connected to a module before removing/inserting it in the DXC-10A.

For your safety, make sure the DXC-10A grounding complies with the requirements listed in Section 4.2.

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.

Warning

Note


Installation of DXC-8R Enclosure 4-41

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-10A, you may also turn it on.

Normal Front-Panel Indications After turn-on, the DXC-10A performs the power-up self-test. During this interval, the ON, MAJOR, MINOR and TEST indicators flash, for test purposes.

After successful completion of the power-up self-test, the DXC-10A starts operating in accordance with the configuration parameters prepared by means of the supervision terminal, or a network management station. Refer to Chapters 5 and 6 for instructions on the use of the supervision terminal.


• The POWER indicator must light.



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.

Section V Installation and Operation of DXC-8R Enclosure

4.22 Installation of DXC-8R Enclosure

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


4-42 Installation of DXC-8R Enclosure

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.

I/O Slot 3

I/O Slot 4

I/O Slot 1

I/O Slot 2DCL B

DCL AON/OFF Switch +Power Indicator

GroundingScrew

Power SupplyUnit

Fuse

POWER

~100-240V 2.0A T 250V RS-530/V.35

2

RS-530/V.35

1

DH

S

SOL

2

LR

O S

1

L

L

RD

T1

CL-

BC

L-A

I/O 2

I/O 3


MN

TST

ON


DC

L.3

1 2O

N


MN

TST

ON


DC

L.3

1 2O

N

TUONISL O

2

R

U TOO NIS

1

R

DE

1

L

L

I/O 1

TUONISL O

2

R

U TOO NIS

1

RD

E1

L

L

I/O 1

Figure 4-22. AC-Powered DXC-8R Enclosure, Rear View

RS-530/V.35

2

RS-530/V.35

1

DH

S

TUONISL O

2

R

U TOO NIS

1

RD

E1

L

L

SOL

2

LR

O S

1

L

L

RD

T1

I/O 2

I/O 1

I/O 4

I/O 3


MN

TST

ON


DC

L.3

1 2O

N

S T A T I O N C L KALM

MJ

MN

TST

ON


DC

L.3

1 2O

N

CL-

BC

L-A

PS-

BPS

-A

ς∆Χ−ΙΝ

0 −48ς∆Χ−ΙΝ

0 −48

I/O Slot 3

I/O Slot 4

I/O Slot 1

I/O Slot 2DCL B

DCL A

PS B

PS A

TUONISL O

2

R

U TOO NIS

1

R

DE1

L

L

Figure 4-23. DC-Powered DXC-8R Enclosure, Rear View

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.

Overvoltages from telecommunication networks may be present inside the DXC-8R enclosure when it is connected to external cables. Do not connect any cables to the DXC-8R before it is properly installed. Always connect the power cable first, and afterwards other cables which are specified for connection to the DXC-8R.

Warning



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

MAJOR ALARM

MINOR ALARMSYSTEM

POWER SUPPLYCOMMON LOGIC

A

B

A

B

Figure 4-24. DXC-8R Enclosure Front Panel

Table 4-11 lists the functions of the indicators located on the DXC-8R front panel.

Table 4-11. DXC-8R Front Panel Indicators

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 LOGIC A and B

Indicators for the DCL.3 modules, seen through the front panel. Their 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 indicator flashes when the module is operating properly, but is in standby (the other module of the same type is active)

POWER SUPPLY A and B

Indicators for the internal power supply modules, seen through the front panel. Their 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


4-44 Installation of DXC-8R Enclosure

Installation of DXC-8R with Replaceable DC Power Supply Modules

Dangerous voltages may be present inside the DPS module when it is connected to power. Do not connect the DPS module to power before it is properly installed within the DXC-8R enclosure, and disconnect the input power from the module before removing it from the enclosure. The installation and preparation of the module shall be done by a skilled technician who is aware of the hazards involved.

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).





Figure 4-25. Attachment of Brackets to DXC-8R

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.

Warning



Installation of DCL.3 Module

Refer to Section 4.6 for installation instructions for the DCL.3 modules.

Install one DCL.3 module in slot CL-A, and an additional DCL.3 module in slot CL-B.

Installation of DC Power Supply Modules

The DC power supply modules are installed in slots PS-A and PS-B.

Before installing the modules, check the position of the internal jumper: this jumper, designated JP2, controls the connection between the frame (enclosure) ground and the external ground.

The location of the jumper is shown in Figure 4-26. 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. Make sure that to set the jumper to the same position on both modules to be installed in 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.

JP2

Jumper JP2 FGND = GND

Frame GroundConnectedto GroundJP2

Frame GroundNot Connectedto GroundJP2

Figure 4-26. DXC-8R DC Power Supply Module, Location of Internal Jumper

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.

Warning



If the enclosure is already operating, you can install a backup power supply 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 the external switch controlling the connection of power to this module to ON.

Installation of DXC-8R with AC Power Supply Modules The installation of the DXC-8R versions with internal (pre-installed) AC power supply modules is similar to the installation procedure described above for the DXC-8R versions with replaceable power supply modules, except that it is not necessary to install power supply modules in the enclosure.

After installing the unit in the rack, connect a short, wide copper braided strap between the DXC-8R grounding screw and the rack ground bus.


Section 4.7 describes considerations regarding the selection of I/O slots for installation of I/O modules.

For the DXC-8R, 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.



The DXC-8R versions with replaceable power supply modules do not have power switches, and therefore will start operating as soon as power is applied to. Therefore, for these DXC-8R versions, connect the DC power cables only after setting the circuit breakers or power switches protecting their supply line to OFF.

Note

Caution


DXC-8R Operating Instructions 4-47

4.25 DXC-8R Operating Instructions

This Section provides operating instructions for a DXC-8R enclosure prepared for operation and installed in accordance with the previous sections.

Turn-on is generally performed after installing all the prescribed I/O modules in the DXC-8R enclosure, as explained in the corresponding module Installation and Operation Manuals. However, you may also carry out the following instructions on a DXC-8R enclosure without I/O modules. Modules may be installed and removed while the DXC-8R is powered on, provided all the safety precautions listed in the installation procedures of the corresponding module are strictly observed. In particular, disconnect all the cables connected to a module before removing/inserting it in the DXC-8R.

For your safety, make sure the DXC-8R grounding complies with the requirements listed in Section 4.2.

Turn-on

Turning On a DXC-8R with AC (Internal) Power Supply Modules

To turn the DXC-8R on, set its power switch to ON.

Turning On a DXC-8R with DC (Replaceable) Power Supply Modules

1. To turn the DXC-8R on, set the external circuit breakers or power switches protecting the two supply lines to ON.

2. If an external feed voltage source, for example, a Ringer-2000, is connected to one or more of the modules installed in the DXC-8R, you may also turn it on.

Normal Front-Panel Indications After turn-on, the DXC-8R performs the power-up self-test. During this interval, all the indicators are turned on, for test purposes.

After successful completion of the power-up self-test, the DXC-8R starts operating in accordance with the configuration parameters prepared by means of the supervision terminal, or a network management station.

Refer to Chapter 5 and Chapter 6 for instructions on the use of the supervision terminal.

Note

Warning


4-48 DXC-8R Operating Instructions


• At least one front panel POWER SUPPLY indicator must light steadily.

• The TEST, MAJOR ALARM and MINOR ALARM indicators must turn off.

• The COMMON LOGIC indicator of one DCL.3 module must light steadily. The COMMON LOGIC indicator of the standby module flashes.


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.

Configuration and Management Activities 5-1

Chapter 5 Management Using Terminals and Telnet

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.

This Chapter includes the following information: •

• Introduction to configuration and management activities - Section 5.2.

• Connection methods for terminals and Telnet hosts – Section 5.3.

• Preliminary configuration - Section 5.4.

• Concise description of the set of commands available for the supervision terminal - Section 5.5. The same set is available to Telnet users.

• Supervision terminal operating instructions - Section 5.6.

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.

5.2 Configuration and Management Activities •

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.

Chapter 5 Management Using Terminals and Telnet DXC-8R/10A/30/30E Installation and Operation Manual

5-2 Connection Methods

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.

The software necessary to run the DXC system supervision program is contained in the DCL.3 module of the DXC system. Moreover, the DCL.3 module stores all the configuration information generated or altered during the communication with the terminal: no information is stored in the terminal.

• Configure the DXC system from any IP host using the Telnet protocol. After establishing a Telnet session with the DXC system, the Telnet protocol offers the same functionality as the supervision terminal, and in addition enables remote access over IP networks.

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.

Chapter 6 provides an outline of the DXC system configuration activities.

Routine Management During regular operation, the DXC system can be managed using any of the options listed above for system configuration.

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 5 Management Using Terminals and Telnet

Connection Methods 5-3

5.3 Connection Methods

This section presents information regarding the connection of a management facility (supervision or alarm monitoring terminal, Telnet host, SNMP network management station, etc.) to a DXC system. General information on various system management topologies is presented in Chapter 3.

In addition to the information presented in this section, the DXC systems also support management by a remote facility, connected to another RAD equipment unit (e.g., KILOMUX-2100, Megaplex-2100/2100H/2200, MAXcess, FCD-E1, FCD-E1A, FCD-E1M, FCD-T1, etc.) that is connected to one of the DXC links (this management method is called inband management). Specific information regarding inband management is presented in Appendix C.

Connection of Supervision Terminals Supervision terminals are supported through the CONTROL port. CONTROL ports are located on all the DCL.3 module versions, and have standard RS-232 asynchronous interfaces, which can be configured to operate as DCE or DTE.

The supervision terminals can be connected either directly to the DXC system CONTROL port, or through a modem link (for convenience, the term modem link is also used to represent any other type of full-duplex data link).

CONTROL Port Interface Characteristics

The CONTROL port supports the following data rates: 300, 1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps. The word format consists of one start bit, 7 or 8 data bits, and one stop bit. Parity can be odd, even or disabled. Always make sure the communication interfaces of the equipment (terminal, modem, etc.) connected to the CONTROL port and the port itself are configured for operation with the same parameters.

To simplify the establishment of communication, the CONTROL port supports the AUTOBAUD function: when this function is enabled, the DXC system 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.

Direct Connection to CONTROL Port

The CONTROL port enables direct connection to terminals, provided its interface is configured as DCE (the selection is made by software commands).

Usually, terminals have DTE interfaces, therefore in this case the connection of the terminal to the CONTROL port is made by means of a straight cable (a cable wired point-to-point).


5-4 Connection Methods

Connection to CONTROL Port through a Modem Link

The CONTROL port also supports the connection of a remote supervision terminal through a modem link: in this case, configure the port interface as DTE. Note however that the CONTROL port supports only dial-in, that is, it cannot dial out.

For connection to a modem, you need a crossed cable, also called null modem cable (see Figure A-2). Appendix A presents wiring information for various types of cables.

Two types of modems are supported: •

• Dial-up Hayes compatible modems, e.g., the RAD miniature DLM/AT modem.

• Multidrop modems, e.g., the RAD SRM-6 miniature multidrop modem. Multidrop connections are explained in the following section.

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 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.

For the DXC-8R, always connect supervision cables to both DCL.3 modules.

Connection of Alarm Monitoring Terminals DXC systems using DCL.3 modules with RS-232 interfaces support automatic reporting of alarms to remote terminals. This function is supported through the MNG port (the MNG port does not support supervision terminals).

Generally, the alarm monitoring terminal is connected to the MNG port of a DXC system through a dial-up modem link.

Note

Note


Connection Methods 5-5

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.

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).

MNG Port Interface Characteristics

The MNG port supports the following data rates: 300, 1200, 2400, 4800, 9600, 19200, 38400 or 57600 bps. The port does not support the AUTOBAUD function.

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 word format consists of one start bit, 7 or 8 data bits, and one stop bit. Parity can be odd, even or disabled. Always make sure the communication interfaces of the equipment (e.g., dial-up modems, etc.) connected to the MNG port and the port itself are configured for operation with the same parameters.

Connection of Dial-Up Modem

If you are using a dial-up modem with 9-pin connector, connect a straight cable from the modem to the MNG connector of the DXC. If you are using a modem with 25-pin connector, use the cable of Figure A-3.

When DCL.3 redundancy is used, the MNG connectors of the two DCL.3 modules can be connected in parallel using a Y-cable, since at any time only the port of the main DCL.3 module is active.

Appendix A presents wiring information for various types of cables. •

For the DXC-8R, always connect supervision cables to both DCL.3 modules.

Connection of Telnet Hosts The Telnet protocol enables communication with multiple DXC system units, using either inband or out-of-band communication: • • For communicating out-of-band, the Telnet host can either be connected to

the Ethernet port, or to a serial port of a DXC system.

• For inband communication, the user can enable the transfer of management traffic through E1, T1, HDSL, E3, T3, and DIM ports.

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.).

Note

Note

Note


5-6 Preliminary Configuration

Connection to Serial Ports (Out-of-Band Communication)

Telnet hosts can connect to a serial DXC port: either to the CONTROL port, available on all the DCL.3 module versions, or to the MNG port, available only on DCL.3 modules with RS-232 interfaces.

• The connection to the CONTROL port is made as explained above in the Connection of Supervision Terminals section. Both direct connection, and connection through a modem link, are possible. The use of multidrop configurations is not recommended.

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).

Connection to Ethernet Port (Out-of-Band Communication)

The 10/100BaseT Ethernet port available on DCL.3 modules with Ethernet port can be directly connected to a LAN. This enables Telnet hosts attached to the same LAN to communicate with the DXC system.

Remote Telnet hosts can also communicate with the DXC system, provided IP communication can be established from their location to the LAN to which the DXC Ethernet port is attached.

Connections for SNMP Management The SNMP protocol also operates over IP, therefore all the requirements described above for Telnet management also apply to the connection of SNMP network management stations.

Multidrop configurations must not be used with SNMP, because multidrop operation requires that all the units strictly observe the rules of polled communication. This is not true for SNMP agents, because they can initiate transmissions on their own (whenever they have a trap to transmit).


Preliminary Configuration 5-7

5.4 Preliminary Configuration

The scope of the preliminary configuration activities is to enable management communication with the DXC system.

DXC Preparations See Chapter 4 for detailed information on internal settings, and for connection instructions.

Selection of Default Password

Note that in general you must enter a password when you start a control session. If the password is incorrect, the DXC will not respond. This can be corrected by appropriate setting of the PASSWRD section of S1, located on the DCL.3 module. Set the PASSWRD section of S1 as follows:

OFF In this position, you can define your own password and node address.

ON Set the section to ON to restore the default DXC password (RAD), and change the node address to the default value of 0. The change will be made after you turn the DXC off for a short time, and then back on.

After restoring the default values, return the switch section to OFF. If the section is left at ON, your changes will be discarded (i.e., replaced again by the default values) the next time the DXC is turned on.

Selection of Default Supervisory Port Parameters

If the supervisory port parameters are not correct, the DXC will not respond. This can be corrected by means of the DP SP section of S1, located on the DCL.3 module. Set the DP SP section of S1 as follows:

OFF In this position, you can define the desired supervisory port parameters.

ON Set the switch section to ON to restore the default supervisory port parameters. The default parameters are 9600 bps, one start bit, eight data bits, no parity, one stop bit and no flow control.

After restoring the default values, return the switch section to OFF. If the section is left at ON, your changes will be discarded (i.e., replaced again by the default values) the next time the DXC is turned on.

For DCL.3 modules with Ethernet interface, you can perform the same operation by means of section 1 of the front-panel DIP switch.

Note


5-8 Preliminary Configuration

Preparation of Supervision Terminal Configure the terminal for the communication parameters used by the CONTROL port, select the full-duplex mode, and turn the terminal echo off. For the preliminary configuration session, always use the default communication parameters.

Connect the RS-232 communication port of the terminal to the CONTROL port.

Preliminary Configuration

The database prepared during the preliminary configuration activities in database 1.

Perform the procedure explained below. If you need detailed instructions and explanations regarding each command, refer to Appendix F.

For detailed instructions regarding the use of the DXC command line interface, refer to Section 5.5.

1. To load the default parameters for the DXC system being configured, enter the LOAD HW command.

2. Enter the UPDATE DB command.

3. To select the terminal control sequences for the terminal type in use, enter the command INIT F 'terminal_type', where 'terminal_type' stands for one of the following types: ANSI, VT-52, VT-100, TV-920, FREEDOM100, FREEDOM110, FREEDOM220.

In case your terminal requires control sequences differing from those used by the terminals listed above, type the command INIT F and enter your terminal control sequences.

Configuration for Using Terminals To prepare the DXC system for configuration by means of a supervision terminal, perform the activities described below.

Even in case you will manage the DXC system using only Telnet hosts and/or SNMP management stations, first you must use the supervision terminal to configure the supervisory port and the SNMP agent.

To configure the CONTROL port of the DXC system:

1. Type DEF SP. You will see the supervisory port configuration data form. A typical form with the default values is shown below:

SPEED DATA PARITY INTERFACE CTS DCD_DEL DSR ALARM RELAY 9600 Bps 8 NO DCE =RTS 0 MSEC ON NORMAL POP_ALM PWD LOG_OFF AUXILIARY_DEVICE ROUTING PROTOCOL NO NO NO TERMINAL NONE

2. Select the desired parameters.

3. Enter UPDATE DB. •

Note


Preliminary Configuration 5-9

To configure the MNG port :

1. Type DEF NP. A typical form with the default values is shown below:

SPEED DATA PARITY CALL_OUT_MODE AUTO 8 NO NONE

LOG_OFF AUXILIARY_DEVICE ROUTING_PROTOCOL NO NMS-SLIP NONE

2. Select the desired parameters.

3. Enter UPDATE DB.

To set the time and date for the internal clock:

1. To set the time of the internal clock of the DXC system, enter the command TIME.

2. Set the date by entering the command DATE.

At this stage, you can start using the supervision terminal to perform DXC configuration in accordance with Chapter 6.

To prevent unauthorized modification of the DXC system parameters, you can use a password.

Set the password using the command DEF PWD, and then enter the UPDATE DB command.

Configuration for Telnet or SNMP Management To prepare the DXC system for configuration by means of Telnet hosts and/or SNMP management stations, use the supervision terminal to configure the supervisory port and the SNMP agent as explained below.

SNMP Agent Configuration • Define the DXC system name, using the DEF NAME command.

• Define the SNMP agent parameters using the DEF AGENT command. The IP address and the subnet mask, as well as the various community names, must match those of the IP host. A typical SNMP agent parameters data form is shown below:


5-10 DXC Supervision Language

OLD AGENT PARAMETERS

IP_ADDRESS IS : = XXX.XXX.XXX.XXX

DEFAULT GATEWAY IS : = XXX.XXX.XXX.XXX

SUBNET MASK IS : = XXX.XXX.XXX.XXX

READ COMMUNITY IS : = public

WRITE COMMUNITY IS : = private

TRAP COMMUNITY IS : = public

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.

Configuration of DCL.3 Ports for Telnet and SNMP Access

To use a DCL.3 serial port for Telnet and SNMP access, use the DEF SP and/or DEF NP commands, as applicable, and select the following parameters:

• Select the appropriate data rate in the SPEED field. Do not select AUTO.

• Select SLIP NMS or PPP NMS in the AUXILIARY DEVICE field.

• Select the ROUTING PROTOCOL:

If the DXC is directly connected to the management station, select NONE

If the DXC is connected through routers, select RIP2

If the DXC is connected to another unit out-of-band, select PROPRIET.

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.


DXC Supervision Language 5-11

5.5 DXC Supervision Language

This Section explains the DXC supervision language syntax, usage, and presents a concise description of the DXC set of commands.

For a detailed description of the DXC command set, refer to Appendix F.

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.

Preparation of New Configuration Parameters

During the preparation of the configuration parameters, the central control subsystem of the DXC dedicates a section of its RAM, called editing buffer, to this process. The editing buffer contains a copy of the current configuration parameters, and this copy is modified by the commands entered by the user. When the preparation of the new set of configuration parameters is ended, the user can make a preliminary check of its validity by means of a special command (CHK DB), which performs a “sanity check” on the configuration parameters stored in the editing buffer. This command provides messages which help identify conflicting parameters, inconsistent selection of related parameter values, etc., so that the parameters can be corrected before proceeding.

After the check is successfully passed, you can save the new configuration parameters and cause the DXC system to start operating in accordance with the new configuration, by means of the UPDATE DB D command, where D is the database number, 1 to 5. If parameters are changed but no UPDATE DB command is issued after the prompt returns, the DXC will display the following message:

CONFIGURATION DATA BASE WAS CHANGED, ENTER UPDATE DB TO ACTIVATE

to remind you to save the changes.

The UPDATE DB command also performs a “sanity check” on the configuration parameters before updating (modifying) the stored parameters. If the “sanity check” is successfully passed, this command stores the new set of configuration parameters in the non-volatile memory of the DCL.3 module, and initializes the hardware.

Since the last validated set of configuration parameters is stored in non-volatile memory, DXC configuration is not affected when the power is turned off.

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.

Supervision Language Syntax • Commands can only be entered when the DXC supervisory port prompt is

displayed. The default prompt is DXC30>, DXC30E>, DXC10A> or DXC8R> (the default can be replaced by a user-assigned name), and it always appears at the beginning of a new line. The cursor appears to the right of the prompt.

• Commands are case-insensitive, e.g., you can type commands in either lower case and/or upper case letters.

• To correct typing errors, backspace by pressing the BACKSPACE key until the error is cleared, and then type again the correct command.

• Use space as a separator between command fields and/or parameters.

• Commands must end with an <Enter>.

• To cancel the current command, press CTRL+C. You will obtain again the DXC prompt.

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.

• The command is executed only after it is validated.

• After each command, the DXC displays the date and time, followed by the DXC prompt.

• Use CTRL+A to display again the last command (without executing it). The display of last commands can be extended for up to 10 commands.

• Use CTRL+D to repeat and execute again the last command.

• Use CTRL+C to stop commands execution.

• If an idle disconnect time-out is specified, the DXC will automatically disconnect the ongoing session if no command is received from the terminal for the specified time-out interval.

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.

Table 5-1. General Command Options

Option Meaning Example of Usage

/A All CLR ALM /A Clears all the alarms stored by the alarm buffer

/C Clear DSP BERT 3:1 /C Displays the results of the BER test running on port 1 of I/O module 3, and then clears the results

/CA Clear all DSP PM 2:1 /CA Displays the performance monitoring data, and then clears all the performance counters

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.



LL is used to identify a specific alarm.

For a detailed description of the DXC command set, refer to Appendix F.

Table 5-2. DXC Command Set Index

Command Purpose Options

BYE End a Telnet management session

CHECK DB Perform a database sanity check

CLR ALM Clear the alarms stored in the DXC alarm buffer /A

CLR LOOP BERT A:B CLR LOOP BERT REM_UNIT A:B CLR LOOP DS_AIS A:B CLR LOOP HDSL_INBAND A:B CLR LOOP INBAND A:B CLR LOOP MONITOR A:B CLR LOOP L A:B CLR LOOP L LINE A:B CLR LOOP L PORT A:B CLR LOOP LB1 A:B CLR LOOP LB2 A:B CLR LOOP LBBD A:B CLR LOOP R A:B CLR LOOP R REM_UNIT A:B CLR LOOP SND_RDI A:B CLR LOOP TS REM A:B CLR LOOP TX-LLB A:B CLR LOOP TX-PLB A:B Note LP can be used instead of

LOOP

Clear user-initiated tests and/or loopbacks.

DATE Set the date for the DXC internal clock

DEF AGENT Defines SNMP agent parameters

DEF ALM ATTRIB Define the alarm handling attributes

DEF AP LL Define the priority (severity) of an alarm generated by the DXC. LL stands for the alarm number

DEF AP ALL Define the priority (severity) of all the alarms generated by the DXC

DEF AR Define the alarm reporting method and the alarm indications, for each alarm level

DEF BERT A:B Define the BERT test conditions for modules with E1 or T1 ports

DEF CALL Define the dial-out parameters for the dial-out port

DEF DCL FLIP Define the parameters related to the use of redundancy for DCL.3 modules. Not applicable for the DXC-10A

DEF MANAGER LIST Define or modify the network management stations to which the SNMP agent of this DXC system will send traps



Table 5-2. DXC Command Set Index (Cont.)


DEF NAME Define the logical name of the DXC

DEF NP Define the parameters of the network management port

DEF PORT A:B Define the parameters and time slot connections of a specified port

DEF PROMPT Define the supervisory port prompt

DEF PWD Define a new password

DEF RDN A:B Define the redundancy parameters

DEF SP Define serial port parameters

DEF SYS Define system parameters

DEF TERM Reset the codes for “clear the screen”, “cursor right”, and “cursor home” to the default values corresponding to a selected terminal type

DEF TEST PORT A:B Define the configuration parameters for a test port

DEF TS A:B:C Define a connection between two time slots

DSP AGENT Display the SNMP agent parameters

DSP ALM Display the contents of the alarm buffer, and optionally clear the buffer

/CA

DSP AS Display the status alarms. You can specify a specific module or module port to display

DSP BERT A:B Display the result of a BERT test running on a selected port /C /I /S

DSP BERT A:B REM Display the result of the BER test activated by the user on the ASMi-31-2 modem connected to the specified port of the D8U or D16U module.

DSP BUS Display the utilization of the internal DXC data bus

DSP CON A:B Show the connection table and time slot utilization for the selected port or module slot

DSP FDL A:B Display the contents of the last FDL message received via the specified port

DSP FLIP Display information on the latest DCL or I/O port/module redundancy switching event. Not applicable for the DXC-10A

/C

DSP HDR TST Display common logic hardware faults (detected during the power-on self-test, and during normal operation on the DCL module)

DSP MANAGER LIST Display the network management stations to which the SNMP agent of this DXC system sends traps





DSP PM A:B DSP PM L

Display the contents of the performance monitoring registers for the specified port, and optionally clear the registers L stands for the line number

/C /CA

DSP REV * DSP REV A

Display the hardware and software revisions of the specified modules, or of all the modules (including the DCL modules installed in slots DCL-A and DCL-B)

DSP REM AGENT Display information on the remote SNMP agents detected by the DXC system

DSP ST A DSP ST A:B DSP ST DCL A DSP ST DCL B

Display status information on selected port or module slot

DSP ST MANAGEMENT Display management status information

DSP ST RDN A Display the redundancy state for a module or redundancy pair *

DSP ST A:B REM Display status information on the remote unit managed via the DHL/E1/2W or D8U/D16U module

DSP ST SYS Display system status information

DSP TS ALLOC Displays the number of timeslots free for use on the port, module and system levels (for both dynamic and static modes)

DSP TS UTILIZATION Displays the number of connected timeslots and the MAX_TS parameter and calculates the utilization percent for each module port (static mode only)

EXIT End the current control session

FORCE ONLINE A Select the on-line module of a redundant pair

HELP Display a concise index of commands and option switches

INIT AP Return the alarm priorities to the default values

INIT DB Load the default configuration instead of the user configuration into the editing buffer of the DXC

INIT F Reset the codes for “clear the screen”, “cursor right”, and “cursor home” to the default values corresponding to a selected terminal type, or to zero

LOAD DB Load the current database stored in the DXC non-volatile memory, to the editing buffer of the DXC

LOAD HW Compares the actual system hardware configuration with the configuration data in the system database, and updates the edited database with default values for each slot in which a module is physically installed, but no module is configured

LOAD OFFLINE DB Load the database stored in the non-volatile memory of the off-line DCL module, into the non-volatile memory of the on-line DCL module





LOOP L A:B LOOP R A:B LOOP BERT A:B LOOP BERT REM_UNIT A:B LOOP DS_AIS A:B LOOP HDSL_INBAND A:B LOOP INBAND A:B LOOP L LINE A:B LOOP L PORT A:B LOOP MONITOR A:B LOOP R REM_UNIT A:B LOOP SND_RDI A:B LOOP TS REM A:B LOOP TX-LLB A:B LOOP TX-PLB A:B Note LP can be used instead of

LOOP

Activate a specified user-controlled loopback or test

PASSWORD Prompts for the password upon starting of control session

RESET Reset the DXC system

RESET I/O A Reset the selected module slot

TIME Set the time of the DXC internal clock

UPD DB UPDATE DB

Copy the contents of the editing buffer of the DXC to the current DXC database, stored in the non-volatile memory, after performing a complete sanity check. This changes accordingly the operating mode of the DXC hardware


5-18 Supervision Terminal Operating Instructions

5.6 Supervision Terminal Operating Instructions

Before using the supervision terminal, make sure that the preparations listed in Section 5.4 were completed and all the relevant equipment has been turned on.

Power-Up with Supervision Terminal Connected During the power-up procedure, the DXC system automatically sends information through its supervisory port, to allow the monitoring of the power-up self-test from a supervision terminal.

Upon power-up, the supervision terminal displays:

DXC SUPERVISORY PORT ON LINE, TYPE “H” FOR HELP

• While the DCL.3 module performs the power-up self-test, the supervision terminal displays:

CL MODULE SELF TEST IN PROGRESS ....

• After the self-test is completed, the result, OK or FAILED, is added to the displayed line. DXC starts reading the installed modules, and the supervision terminal displays:

READING INSTALLED MODULES .....

• 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

For the DXC-8R, the display ends at the I/O04 line.

For the DXC-10A, the display ends at the I/O05 line.

If you see FAILED for any module, replace that module.

Supervision Terminal Operating Instructions 5-19

Starting a Session - Single DXC When the terminal is used to control a single DXC, always assign node address 0 to the DXC. Use the following start-up sequence to connect to a DXC that has been assigned node number 0:

1. If you use the AUTO (AUTOBAUD) mode, press the <Enter> key three times. This allows the DXC to identify the terminal data rate.

2. Assuming that the DXC has successfully identified the data rate of the supervision terminal, you will be notified if the DXC failed the power-up self-test: If you see DXC SELFTEST FAILED, the DXC must be repaired before you

can continue using it. If DXC successfully passed the power-up self-test (DXC SELFTEST OK), it

sends the following message:

DXC SUPERVISORY PORT ON LINE. TYPE “H” FOR HELP

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.

Starting a Session - Multiple DXC Use the following procedure to establish a session with a specific DXC.

If you are using a multidrop configuration, do not assign address 0 to any of the DXC units connected to a given terminal. Make sure the interface type is set as DTE, and select the appropriate DCD_DEL parameter.

1. Press the <Enter> key three times.

2. Type NODE, space, the desired DXC node address and another space, and then type the desired command and press <Enter>. For example, with node address 234, type:

NODE<sp>234<sp> 'command' <Enter>

If the addressed DXC does not use password protection, it immediately executes the command.

Important

5-20 Supervision Terminal Operating Instructions

If the addressed DXC is password-protected, you will see the prompt:

PASSWORD>

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 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.

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.

Ending a Control Session • To end the control session, type:

EXIT

The DXC prompt disappears.

The command used to end Telnet sessions is BYE.

Note

Note

Note

Outline of Configuration Procedure 6-1

Chapter 6 Configuring the DXC

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.

6.2 Outline of Configuration Procedure

To prepare a typical DXC system for operation in accordance with customer’s requirements, perform the following activities in the order given in Table 6-1.

Table 6-1. Outline of Configuration Procedures

Step Activity Reference

1 Preliminary configuration Section 5.4

2 Define the optimal equipment configuration Section 6.3

3 Define the system configuration Section 6.4

4 Configure each port and its connections Section 6.5

5 Define redundancy pairs for the desired ports Section 6.6

6 Define DCL redundancy parameters Section 6.7

7 Define the general system parameters Section 6.8

8 Define network port configuration and dial-up parameters Section 6.9

9 Define alarm handling parameters Section 6.10

10 Save the configuration database Section 6.11

11 Selecting the active database Section 6.12

Chapter 6 Configuring the DXC DXC-8R/10A/30/30E Installation and Operation Manual

6-2 Determining the Optimal Equipment Configuration

During the configuration process, it is recommended to check the results of each command by displaying the new parameters, and then check the parameters for consistency with the previous selections and compliance with the prescribed system configuration requirements.

You should make the checks before entering the UPD DB command.

6.3 Determining the Optimal Equipment Configuration

The automatic timeslot allocation algorithm of the DXC, explained in Section 3.2, permits optimal utilization of the available matrix bandwidth, with particular emphasis on optimizing bandwidth utilization by I/O modules that use dynamic timeslot allocation (these modules are referred to as Type 2 modules, whereas the regular I/O modules, which use preassigned bandwidth, are referred to as Type 1 modules). To avoid possible errors in data traffic, you can select the static timeslot allocation to Type 2 module ports, as described in Static Timeslot Allocation to Type 2 Module Ports in Chapter 3. In this case, follow the guidelines described in Planning Timeslot Growth with the Static Allocation Mode below.

The next step in planning the configuration of a newly-installed DXC, is to determine the bandwidth available, and the optimal location (I/O slot numbers) for the various modules to be installed in the chassis.

If the chassis will include only Type 1 modules, sufficient matrix bandwidth is always available for all the modules that may be physically installed in the chassis, therefore no special planning steps are necessary.

Planning Timeslot Growth with the Static Allocation Mode When planning the timeslot growth space on a DXC dynamic (Type 2) module port, one has to consider two types of module functions:

• User/tributary module: a module connected to the user

• Trunk module: a module that is connected to the network and performs grooming functions.

For user/tributary modules, it is important to estimate carefully the maximum amount of timeslots that may be required on each port (expected maximum capacity per port). For trunk modules, try to allocate the maximum possible number of timeslots (31) per port, since it is most likely that all the bandwidth on the port with be fully utilized.

Evaluating Bandwidth Available for Modules to Be Installed When several I/O slots are free in a DXC chassis, it is necessary to check the DXC bus link utilization before physically inserting or configuring a new module. This check is performed by a dedicated command, DSP BUS (see Appendix F).

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 6 Configuring the DXC

Determining the Optimal Equipment Configuration 6-3

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:

TS = 960 – (64 × F) – ∑D

1TS 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:

SLOT PORT NUM OF CONNECTED TS MAX TS UTILIZATION

1 1 2 5 40.000

1 2 5 10 50.000

1 3 0 8 0.000

1 4 0 10 0.000

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.

6-4 Determining the Optimal Equipment Configuration

RAD recommends to use the DSP TS ALLOC command (see Appendix F) to have the 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 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.

BUS_LINK STATUS CAPTURED_BY BUS_LINK STATUS CAPTURED_BY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 01:01 < DYNAMIC > 01:01 01:02 < DYNAMIC > 01:02 02:01 < DYNAMIC > 01:03 02:02 < DYNAMIC > 01:04 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

Note

Note

Defining the System Configuration 6-5

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.

Therefore, although I/O slot 2 is physically free, it is not recommended to install a module in this slot, because this would result in reallocation of timeslots, which would cause a short disruption in traffic flow.

• Modules can be installed in I/O slots 4, 9, 10, 12, 13 and 14, because their bus links are free. No traffic disruption would be caused by installing and/or configuring a module in these slots.

6.4 Defining the System Configuration

The purpose of the system configuration activity is to define the modules to be included in the DXC database, and select the system timing sources. DXC enables the user to include in its database modules that are not physically installed in the enclosure. This enables the user to preprogram module parameters so that when the module is installed, it will start immediately to operate in the desired mode.

Before starting the configuration of a DXC in which new modules have been installed, it is recommended to enter the LOAD HW command, followed by the UPDATE DB command, for loading the default parameters for the newly installed modules. This command also identifies the modules physically installed in the chassis. If you are configuring a new DXC, you can use the INIT DB command, followed by the UPDATE DB command, to initialize the DXC database by loading the factory-default parameter values.

To start, type the command:

DEF SYS<Enter>

First Data Form Line After entering the command, you will see the first line of the system configuration data form. A typical line is shown below.

Note

6-6 Defining the System Configuration

CLOCK_MASTER CLOCK_FBACK REDUNDANCY STATION_CLOCK MATRIX_MODE DATE_FORMAT

INT NONE NO 1.544MHz BIDIRECT DD/MM/YYYY

Selection of Timing Sources

Refer to Section 3.3 for system timing selection guidelines. In most applications, the master clock source is the received clock signal of an I/O module port, however the station clock can also be used when it is necessary to synchronize several equipment units.

Pay attention to the following points:

• If you selected one of the ports as a main source, do not select the same port as the fallback source.

• A DHS port can be selected as a timing reference source only if its timing mode is DTE2.

• When using the station clock, make sure to select the correct frequency.

• A D8U/D16U port can be selected as a timing reference source only when it has an NT interface.

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.

Second Data Form Line After the parameter values of the selected, press <Enter>. A typical second line of the system parameters data form is shown below.

Configuring Modules and Ports 6-7

TS_ALLOC_MODE STATION_CLOCK_IF

STATIC G703

Timeslot Allocation Mode

If you have Type 2 (dynamic) modules in the chassis and you cannot plan in advance which modules will be installed in the chassis and how timeslots will be connected, you can use dynamic timeslot allocation (see description in Automatic Timeslot Allocation Algorithm in Chapter 3.

This mode, however, may cause data disruption on other ports/slots. To avoid such disruption, you can use the DEF PORT command to specify the maximum number of timeslots for a given port (MAX_TS parameter), to allow for “static” growth of timeslots on each port, in contrast to “dynamic” timeslot allocation.

Selection of External Clock Interface

Select the external clock interface: G-703 or RS-422.

Defining the Modules Installed in the DXC Chassis Having configured the parameters displayed on the first data form line, press <Enter> to display the second part of the system parameters data form. This part consists of several lines, which are used to define the I/O modules installed in the DXC.

Before performing these activities, review the guidelines presented in Section 6.3.

Since the DXC system automatically identifies the installed modules, the only reason for changing the modules displayed in this section of the data form is to include in the database a module not yet installed in this chassis. This permits preconfiguring the module parameters, with the result that when the module is inserted in its slot it immediately starts operating in accordance with the preconfigured parameters.

If necessary, change the module types as required. When the desired selection is displayed, press <Enter> to display the next line.

When done, press <Enter> to end.

6.5 Configuring Modules and Ports

After system configuration, you can define the parameters of the individual module and module ports, according to the required application.

To define all the parameters for an individual module (including all of its ports), type:

DEF PORT A:<Enter>

To define the parameters of an individual port and its connections, type:

DEF PORT A:B<Enter>

Note


6-8 Configuring Modules and Ports

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.

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.

Timeslot Routing Guidelines The timeslot routing capabilities depend on the port type:

• For connections between E1 and/or T1 ports, you can program the routing of each individual 64 kbps timeslot to any timeslot of any other E1, T1 or HDSL port. This capability applies to timeslot routing between external E1, T1 and/or HDSL ports, as well as to routing to the internal ports of a fractional STM-1, E3 or T3 module installed in DXC system.

To expedite the routing, a sequential “bundle” routing mode is also available: one “bundle” (group of consecutive timeslots, identified by the number of the starting timeslot and the total number of timeslots) can be routed to the desired destination port, maintaining its integrity, and inserted in the destination frame sequentially, in consecutive timeslots. The user can also specify the starting timeslot in the source frame and in the destination frame.

• For high-speed (DHS) data ports, as well as for ISDN “U” ports operating in the LT-1 mode at the data rate of 128 kbps, the user's data stream can be routed to any desired E1, T1 or HDSL port (internal or external), as well as to another DHS port.

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.

Note


Defining I/O Redundancy Pairs 6-9

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)

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.

6.6 Defining I/O Redundancy Pairs

The DXC system supports I/O redundancy, as explained in Section 3.7. 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.

Note

6-10 Defining I/O Redundancy Pairs

• Hardware redundancy mode, also called Y-cable redundancy mode. This mode is supported by the DT1B and DE1B modules (copper interface only).

• Combined line and hardware redundancy mode, also called dual-slot protection mode. This mode is supported by the DE3 and DT3 modules.

Configuration for Line Redundancy Mode 1. To configure a module for operation in the line redundancy mode, type:

DEF RDN A<Enter> where A stands for the number of the slot in which the desired module is installed.

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

2. To enable the line redundancy mode, select SINGLE_SLOT_PROTECTION in the REDUNDANCY_MODE field.

In this case, the RECOVERY_MODE field is configured to AUTO.

3. Select the desired TIME_OUT interval, during which the port state is ignored. This provides time for the port (and link) to stabilize after a flipping: the allowed range is 0 (no stabilization time) to 99 seconds.

The stabilization time should be sufficiently long, relative to the time needed to declare a port as synchronized (e.g., for T1 ports configured with default parameters, this requires at least 10 seconds).

4. After selecting the desired parameters, press <Enter>. The second line of the redundancy configuration data form appears. A typical line is shown below:

FLIP_MODE

SOFTWARE

The FLIP_MODE parameter is used to specify the method used to perform a redundancy flip 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 (refer to Section 3.7 for details).

HARDWARE - switching is automatically performed in case the active port loses frame synchronization.

5. Select the flip mode and press <Enter> to end.

Defining I/O Redundancy Pairs 6-11

• 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.

Configuration for Hardware Redundancy Mode 1. To configure two modules for operation in the hardware redundancy 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 be routed only to the primary module).

You will see the redundancy configuration data form (the same form used for the single-slot protection mode).

2. Under REDUNDANCY_MODE, select Y_CABLE.

3. Under RECOVERY_MODE, select the method used to switch (flip) between the active and redundant modules: MANUAL - the active module is manually selected, using the FORCE

ONLINE command. This selection is available only in the Y-cable redundancy mode.

AUTO - switching is automatically performed.

4. Select the other parameters as explained for the line redundancy mode.

Configuration for Combined Line and Hardware Redundancy 1. To configure two E3 or T3 modules for operation in the combined line and

hardware redundancy 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 be routed only to the primary module).

You will see the redundancy configuration data form (the same form used for the line redundancy mode).

2. Under REDUNDANCY_MODE, select DUAL_CABLE_PROTECTION.

3. Under RECOVERY_MODE, select the method used to switch (flip) between the active and redundant modules. The only supported selection is AUTO, which means that switching is automatically performed.

4. Select the other parameters as explained for the line redundancy mode, except that the FLIP_MODE parameter is not applicable.

Notes

6-12 Configuring the General System Parameters

6.7 Configuring the DCL Redundancy

The user can configure the parameters that control DCL redundancy (this feature, supported by all the DXC chassis versions except DXC-10A, is explained in Section 3.7).

1. To define the DCL redundancy parameters, type:

DEF DCL FLIP<Enter> The DCL.3 redundancy parameters data form appears. A typical data form is shown below.

ACTIVE_DCL FLIP_DELAY FLIP_ON_STATION_CLOCK

AUTO 1MIN YES

2. Under ACTIVE_ DCL, select the desired redundancy mode: AUTO - redundancy is enabled. The DXC system will use the DCL.3 module

selected by the redundancy control algorithm, as explained in Section 3.7.

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.

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.

6.8 Configuring the General System Parameters

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.


Configuring the Network Port for Dial-up 6-13

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.

Configuration of Out-of-Band Port

You can configure one of the DXC serial ports (either the CONTROL or MNG port) to support out-of-band management traffic. No configuration is required to use the ETHERNET port for management access.

When configuring a serial port for out-of-band management access, pay attention to the following points:

• Always configure the SPEED parameter in accordance with the actual data rate (do not use the AUTOBAUD function).

• Configure the port interface as DCE.

• Select the AUXILIARY DEVICE parameter in accordance with the connection method and management protocol:

NMS SLIP - The port connects directly to an SNMP management station and/or Telnet host, using the SLIP protocol.

AGENT SLIP - The 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.

• Select PROPRIET or RIP-II in the ROUTING PROTOCOL field. The RIP-II selection is needed only when the management traffic must pass through standard routers.

6.9 Configuring the Network Port for Dial-up

The DXC serial network port, MNG, can be used as a dial-up port for reporting alarms to remote terminals.

This activity includes two steps:

1. Selecting the network port parameters, using the DEF NP command.

2. Configuring the dial-up parameters, using the DEF CALL command.

6-14 Configuring the Network Port for Dial-up

Configuring the Network Port Parameters 1. To start the port configuration, enter the command:

DEF NP<Enter>

If the DCL.3 module has RS-232 interfaces, you will see the first line of the network port parameters data form. A typical form is shown below. The form presents the current parameter values as defaults.

SPEED DATA PARITY CALL_OUT_MODE

9600 8 NO NONE

2. Select the communication parameters in accordance with the modem parameters. For the CALL_OUT_MODE, select either ALL (in this case, DXC will initiate a call after each new alarm) or MAJOR (call only when a new major alarm condition is detected).

3. When done, press <Enter> to display the second line of parameters. A typical line, showing the parameters required for use as a dial-up port, is shown below.

LOG_OFF AUXILIARY_DEVICE ROUTING_PROTOCOL

NO DIAL_OUT NONE

Configuring the Dial-Up Parameters 1. To start the dial-up parameter configuration, enter the command:

DEF CALL

The first page of the call-out parameters data form appears. A typical display is shown below.

NUM_OF_RETRIES WAIT_FOR_CONNECT DIAL_MODE ALT_NUM_MODE

0 60SEC TONE YES

2. Select the dialing parameters in accordance with your requirements. If you have an alternate number to dial in case the first number cannot be reached, select YES under ALT_NUM_MODE.

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 YES, the third page of the call-out parameters data form appears, used to enter a new alternate directory number.

Configuring the Alarm Handling Parameters 6-15

A typical display is shown below.

NEW ALTERNATE NUMBER [MAX 20 CHARS] = CURRENT ALTERNATE NUMBER = 'alternate number'

5. Enter the desired directory number and press <Enter> to end.

6.10 Configuring the Alarm Handling Parameters

DXC systems provide a wide range of alarm handling parameters, which enable the user to customize alarm handling in accordance with the requirements of its specific application.

Moreover, DXC provides convenience tools that permit to modify temporarily the response to alarm conditions under special circumstances, e.g., during maintenance, trunk failure, etc.

The alarm handling parameters cover the alarm reporting policy and alarm processing.

Alarm Reporting Policy To meet the needs of large organizations for a standardized, unified alarm reporting method adapted to specific needs of each organization, the DXC system provides two functions:

• User-configurable alarm priorities. The priority (severity) of each alarm can be defined by means of the DEF AP command.

DXC supports two alarm priorities: minor and major.

The alarm priorities are stored in the DCL.3 flash (non-volatile) memory, and therefore remain in effect even after the DXC is turned off and then on again.

• User-configurable alarm indications. The indications provided at each priority level can be defined by means of the DEF AR command. The reporting options include:

Sending of alarm reports to the supervision terminal, and traps to SNMP management stations.

Activation of alarm relay.

Alarm Processing DXC supports two alarm processing features, controlled by means of the DEF ALM ATTRIB command: alarm inversion and alarm masking.

6-16 Configuring the Alarm Handling Parameters

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.

Selecting the Alarm Attributes

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

2. Select the group of alarms to be processed, and then press <Enter>. Selecting USER enables you to select attributes for each individual alarm, whereas a specific selection (NORMAL, MASK, or INVERT) affects the whole group of alarms.

3. Select the desired attributes in accordance with the selected method, and then press <Enter> to end.


Selecting the Active Database 6-17

6.11 Saving of Configuration Database

The user can save the edited set of configuration parameters as a database, by means of the UPD DB command. DXC can store 5 different databases, and the user can specify the desired number.

Before any update, a sanity check is automatically performed, and the database update is performed only if no errors are detected. The database will then be automatically activated on the DXC.

6.12 Selecting the Active Database

The active database, that is, the database that controls the current DXC operating parameters, can be selected by means of the LOAD DB command. The available selections are restricted to non-empty databases, which contain parameters selected by the user.

If necessary, the factory-default database can also be loaded, using the INIT DB command. In this case, all the modules installed in the DXC chassis are configured to use their factory-default parameters.


6-18 Selecting the Active Database

Performance Diagnostics Data 7-1

Chapter 7 Tests and Diagnostics

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.

7.2 Performance Diagnostics Data

Performance Evaluation for T1 Ports This section describes the performance evaluation and monitoring functions provided by the DXC for T1 ports. The functions actually available depend on the framing mode in use, ESF or SF (D4):

• ESF Framing: when ESF framing is used, it is possible to monitor end-to-end data transmission performance. With this type of framing (see Appendix E), the data stream transmitted end-to-end includes supervision and error detection information.

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.

Chapter 7 Tests and Diagnostics DXC-8R/10A/30/30E Installation and Operation Manual

7-2 Performance Diagnostics Data

ANSI T1.403-1989 ESF Statistics

When using ESF framing, DXC stores T1 line statistics in compliance with the ANSI T1.403-1989 requirements. The statistic data is gathered once per second. The statistics are collected over the last four seconds, and then transmitted via the 4 kbps control and supervision data port (FDL) of the ESF frames. This permits real-time monitoring of data transmission performance.

The performance parameters are displayed:

• For the current 15-minute interval.

• For all the previous 15-minute intervals for which valid data is available (up to a maximum of 24 hours, i.e., 96 15-minute intervals).

• For the last 24-hour interval.

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)

The number of seconds in the current measurement interval. A measurement interval has 900 seconds (15 minutes).

• Current errored seconds (ES)

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)

An unavailable second is any second in which a failed signal state exists. A failed signal state is declared when 10 consecutive severely errored seconds (SES) occur, and is cleared after 10 consecutive seconds of data are processed without a SES.

• Current severely errored seconds (SES)

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.

DXC-8R/10A/30/30E Installation and Operation Manual Chapter 7 Tests and Diagnostics


• Current slip second counter (CSS)

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.

Performance Evaluation for E1 Ports This section describes the performance evaluation and monitoring functions provided by the DXC for E1 ports. The functions actually available depend on the use of the CRC-4 option.

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.

Performance Evaluation for T3 and E3 Ports The DXC provides performance evaluation and monitoring functions for E3 and T3 ports in accordance with RFC 1407.





The performance parameters are explained below.

Performance Parameters for the Current 15-Minute Interval • Current line errored seconds (LES)

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.



A PSES is a second with 44 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).

• Current C-bit errored seconds (CES)

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 severely errored framing seconds (SEFS) in the current 15-minute interval. SEFS is a second with one or more OOF defects, or one or more incoming AIS defects (provided these defects do not occur during an unavailable second).

• Current unavailable seconds (UAS)

Number of unavailable seconds (UAS) in the current 15-minute interval. The UAS is calculated by counting the number of seconds the interface is unavailable (unavailability is declared when 10 contiguous PSESs occur, and ends when 10 contiguous seconds which are not PSESs are detected).

Note that all the error counts, except the UAS count itself, are stopped during UASs.

• Current Timer

The number of seconds in the current interval (1 through 900) for which the data is shown.

Performance Parameters for Previous 15-Minute Intervals

The performance parameters for previous 15-minute intervals include the LES, PES, PSES, CES, CSES, SEFS, and UAS for each previous interval with valid data.



Performance Parameters for Previous 24-Hour Interval

The performance parameters for the 24-hour interval include the LES, PES, PSES, CES, CSES, SEFS, and UAS collected during the previous 24-hour interval, and the number of degraded minutes.

In addition, the total number of 15-minute intervals in the previous 24-hour interval, for which valid data is available, is also displayed.

Performance Evaluation for HDSL Links The performance evaluation and monitoring functions provided by the DXC for HDSL links include ES, UAS, SES and BBE (block background error) statistics. The performance statistics are available for each line, separately.

Performance Evaluation for SHDSL Ports The DXC provides performance evaluation and monitoring functions for SHDSL ports in accordance with ITU-T Rec. G.991.2.

The basic performance data is calculated for each second, and accumulated over a 15-minute (900 second) interval. The accumulated data for each of the 96 15-minute intervals in a 24-hour interval is stored and is available for display, independently for each port. In addition, the performance data for the last seven 24-hour periods is also stored.



• For other 15-minute intervals in the current 24-hour interval.


• For previous 24-hour intervals

The performance parameters are explained below.

Performance Parameters for the Current 15-Minute Interval

• CRC events counter (CRC ANOMALIES COUNTER)

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 errored seconds in the current 15-minute interval.

An errored second is a second in which one or more CRC (Cyclic Redundancy Check) error events have been detected.

• Current unavailable seconds (CURRENT UAS)

The number of unavailable seconds in the current 15-minute interval.

An unavailable second is a second in which a failed signal condition occurred.



• Current severely errored seconds (CURRENT SES)

The number of severely errored seconds in the current 15-minute interval.

A severely errored second is a second in which 832 or more CRC error events occurred.

• Seconds with loss of sync word events (CURRENT LOSWS)

The number of seconds with loss of sync word events in the current 15-minute interval.

• Loop attenuation (LOOP ATTENUATION)

Indicates the currently measured value of the loop attenuation, in dB. 0 indicates no attenuation.

• Signal-to-noise ratio margin (SNR MARGIN)

Indicates the currently measured value of the signal/noise margin threshold, in dB. 0 indicates that the SHDSL link is disconnected.

• Current receive path input circuits gain (RECEIVE GAIN)

Indicates the current value of the receive path input circuits gain, in dB.

• Current transmit signal power (TRANSMIT POWER)

Indicates the currently measured value of transmit signal power, in dBm.

• Current actual power backoff (ACTUAL POWER BACKOFF)

Indicates the currently measured backoff value of the transmit circuits, in dB (relative to the transmit power value).

• Current timer (CURRENT TIMER)

The number of seconds elapsed since the beginning of the current interval.

Performance Parameters for Previous 15-Minute Intervals

The display includes one row for each interval, where the interval is identified by its number (1 to 96) within the current 24-hour interval. The 15-minute interval performance parameters include ES, UAS, SES, LOSWS, CRC and LOSW recorded during the interval.

Performance Parameters for the Last 24-Hour Interval

The 24-hour interval performance parameters include the total number of ES, UAS, SES, LOSWS, CRC and LOSW recorded during the 24-hour interval. In addition, the display includes a CURRENT DAY TIMER, which indicates the total number of seconds elapsed since the beginning of the current day (24-hour interval).

Performance Parameters for the Previous 24-Hour Intervals

D8SL stores up to seven sets of 24-hour interval performance data.



Performance Evaluation for STM-1 Modules I/O modules with STM-1 interfaces support performance evaluation in accordance with RFC2558: Definitions of Managed Objects for the SONET/SDH Interface Type. The following functions are available:

• External STM-1 port layer: supports local performance monitoring parameters from the SONET/SDH section group for each external port

• High-order (VC-4) layer: supports local performance monitoring parameters from the SONET/SDH path group for each external port

• Low-order (VC-12) layer: supports local performance monitoring parameters from the SONET/SDH VT/VC group for each of the supported VC-12s.

In addition, the performance monitoring parameters described in the Performance Evaluation for E1 Ports section above are available for each internal E1 port.

For a description of the SDH environment, refer to Appendix E.

Performance Monitoring Parameters for the External STM-1 Port

The performance monitoring parameters are displayed for the following intervals:




Performance Parameters for the Current 15-Minute Interval • Current timer

The number of seconds in the current measurement interval. A measurement interval has 900 seconds (15 minutes).

• Current errored seconds (ES)

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.



Loss of Pointer (LOP) defect:

A LOP defect is declared after no valid pointer is detected in eight consecutive frames. The LOP defect will not be reported while an AIS signal is present.

The LOP defect is terminated after a valid pointer is detected.

Alarm Indication Signal (AIS) received in the SDH overhead.

Coding Violation (CV): a coding violation is declared when a Bit Interleaved Parity (BIP) error is detected in the incoming signal. The BIP information is collected using the B1 byte in the Section Overhead.

• Current severely errored seconds (SES)

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).

Performance Monitoring Parameters for High-Order (VC-4) Paths

The types of performance monitoring parameters for the high-order path layer (VC-4) are similar to those described above for the external STM-1 port.

Performance Monitoring Parameters for Low-Order (VC-12) Paths

The types of performance monitoring parameters for the low-order path layer (VC-12) are similar to those described above for the external STM-1 port.

Displaying the Performance Data The performance data can be displayed on the supervision terminal by means of the DSP PM command, as explained in Appendix F. You can reset all the performance diagnostics registers by adding the /CA switch to the command.


7-10 User-Controlled Loopback Functions

7.3 User-Controlled Loopback Functions

The main types of test and loopback functions are described in the following paragraphs. The tests and loopbacks are identified by the designation displayed on a supervision terminal connected to the DXC.

Additional tests and loopbacks may be available on each specific type of module: such functions are described in the corresponding module Installation and Operation Manual.

It is forbidden to activate loopbacks towards user equipment with Ethernet interface.

T1 and E1 Modules with T1 and E1 Ports The general types of tests and loopbacks supported by I/O modules with E1 and T1 ports, are described below. The inband (LOOP INBAND) and remote timeslot (LOOP TS REM) loops are available also on DHL modules.

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.

E1 or T1Port

Interface

DXC Unit

"1"

DigitalProcessingUnit (DCL)

PortInterface

Figure 7-1. LOCAL LOOP Loopback (T1 and E1 Modules)

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.

Note


User-Controlled Loopback Functions 7-11

DXC Unit


PortInterface

E1 or T1Port

Interface

Figure 7-2. REMOTE LOOP Loopback (E1 and T1 Modules)

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.

DXC Unit

SequenceEvaluator


PortInterface

SequenceGenerator

PortInterface

Remote Unit

E1 or T1Interface

Figure 7-3. Inband Code-Activated Loopback

The loopback is activated by transmitting, within the defined timeslots, the loopback activation sequence specified in ANSI T1E1.2/93-003. The activation sequence is generated by the port sequence generator, and is inserted in the required timeslots of the E1 or T1 data stream sent by the port. When remote equipment which supports the inband code-activated loopback receives the loopback activation sequence, it connects a loopback at the output of the E1 or T1 port framer, as shown in Figure 7-3.



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.

E1 or T1Interface

DXC Unit

PortInterface


Figure 7-4. LOOP TS REM Loopback

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

DHS PortInterface


PortInterface

Figure 7-5. LOCAL LOOP Loopback (DHS Module)

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.


DXC Unit

DHS PortInterface


PortInterface

Figure 7-6. REMOTE LOOP Loopback (DHS Module)



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.

DXC Unit


User Interface

Port 1

T1/E1 PortsServing DIM

.....

Port 2

Port 8

DIM

.....

Figure 7-7. LOCAL LOOP Loopback (DIM Module)

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.


DXC Unit


UserInterface

Port 1

.....

Port 2

Port 8


DIM

.....

Figure 7-8. REMOTE LOOP Loopback (DIM Module)



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.

Local DXC Unit


DIM Port 1

.....

Port 2

Port 8


.....

.....

Port 1

.....

Port 2

Port 8


SequenceEvaluator

Remote DXC UnitT1/E1 PortsServing DIM

T1/E1Network

DIM

SequenceEvaluator

SequenceGenerator

Figure 7-9. Inband Code-Activated Loopback on DIM – Signal Paths during Loopback Activation

UserInterface

Local DXC Unit


UserInterface

Port 1

.....

Port 2

Port 8


.....

.....

Port 1

.....

Port 2

Port 8


Remote DXC UnitT1/E1 PortsServing DIM

T1/E1Network

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.

HDSLProcessing

DXC Unit


PortInterface

HDSLLine A

Interface

HDSLLine B

Interface

HDSLLine A

HDSLLine B

DHLModule

Figure 7-11. LOOP L LINE Loopback (Typical DHL Module)

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.



E1Framer

HDSLProcessing

DXC Unit


PortInterface

HDSLLine A

Interface

HDSLLine B

Interface

HDSLLine A

HDSLLine B

DHLModule

Figure 7-12. LOOP L PORT Loopback (Typical DHL Module)

LOOP HDSL_INBAND or LOOP R REM_UNIT

The HDSL_INBAND loopback (remote loopback on the remote unit) checks the complete HDSL link, including the transmission path connecting the remote equipment to the DXC, and the corresponding local port interface of the DXC.

The loopback is activated by the command LOOP HDSL_INBAND or LOOP R REM_UNIT, which results in the transmission of a loopback activation command, through the HDSL subsystem, to the remote DHL module. The activation command is also accepted by other HDSL transmission equipment, e.g., the HCD HDSL modems offered by RAD.

Figure 7-13 shows the typical signal paths when the loopback on a remote DXC unit is activated. The drawing shows the signal paths for the DHL/E1 module. The DHL/E1/2W has only one HDSL line interface, therefore ignore the line B interface in this case.

HDSLProcessing

Local DXC Unit


PortInterface

HDSLLine A

Interface

HDSLLine B

Interface

DHLModule

Remote DXC Unit

PortInterface

HDSLLine A

Interface

HDSLLine B

Interface

DHLModule

HDSL Processing


Figure 7-13. HDSL_INBAND Loopback on Remote DXC Unit (Typical DHL Modules)

When the HDSL_INBAND loopback is activated, the HDSL processing circuits of the remote DHL module return the received data signal toward the local DHL module.

The loopback is performed by internally connecting the receive signal to the input of the transmit path. The received data signal remains connected to the remote users. The test signal is provided by the local user’s equipment, that must receive its own transmission without errors while the loopback is activated.



Figure 7-14 shows the typical signal paths when the loopback on a remote HDSL modem for example, HCD-E1 is activated.

HDSLProcessing

Local DXC Unit


PortInterface

HDSLLine A

Interface

HDSLLine B

Interface

DHLModule

Remote HCD-E1

HDSLLine A

Interface

HDSLLine B

Interface

DHLModule

HDSLProcessing

PortInterface

Figure 7-14. HDSL_INBAND Loopback on Remote Modem

D8U, D16U Modules This section describes the loopbacks supported on the D8U or D16U modules. The available loopbacks activated on the D8U or D16U modules are: • Local loopbacks on external ports

• Remote loopbacks on external ports

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).

RoutingBusInterface

.....

Port 16

Port 1 .........

DXC Unit


Other PortInterface

Figure 7-15. Local Loopback Signal Paths



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).

RoutingBusInterface

.....

Port 16

Port 1

.........

DXC Unit


Other PortInterface

Figure 7-16. Remote Loopback Signal Paths

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.

Remote Loopback on Remote ASMi-31

When this loopback is activated (in response to a command received from the supervision terminal or the DXC management system), the D8U/D16U port sends through the in-band downloading channel, a remote loopback command to the ASMi-31 connected to that channel.

This function enables to check the operation of the external port, the line to the remote ASMi-31, and the ASMi-31 “U” interface. Figure 7-17 shows the signal paths of a typical remote loopback on the remote ASMi-31 (activated on external port 1).



DXC Unit


.........

RemoteLoopback

(NT)

ASMi-31

.....Port 16

Port 1

BusInterface Routing

Figure 7-17. Remote Loopback on Remote ASMi-31

D8SL Interface Modules This section describes the loopbacks supported on the external and internal D8SL ports.

The external D8SL ports support three types of user-controlled loopbacks, which can be independently activated for each port:

• Local loopback

• Remote loopback

• Remote loopback on remote unit.

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).

Local Loopback on External Port

The local loopback, activated by the command LP L A:B, is used to test the path of the signals intended for transmission through a selected D8SL port: this path starts with the other DXC port(s) and continues up to the D8SL circuits associated with the selected port (including the port interface and the operation of the routing circuits that handle the port signals within the D8SL module).

As a result, this loopback also 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 module.

Figure 7-18 shows the signal paths of a typical local loopback (activated on external port 1).



DXC Unit


Other PortInterface

BusInterface

.....

Port 8

Port 1

"1"

........

Figure 7-18. Typical Local Loopback Signal Path

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.

Remote Loopback on External Port

The remote loopback, activated by the command LP R A:B, is used to test the interface circuits of a given D8SL port. This test also checks the transmission plant connecting the remote equipment to the corresponding port interface of the D8SL module.

Figure 7-19 shows the signal paths of a typical remote loopback (activated on external port 1).

DXC Unit


Other PortInterface

BusInterface

.....

Port 8

Port 1

Figure 7-19. Typical Remote Loopback Signal Paths

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 Loopback on Remote Unit

The remote loopback on remote unit is relevant for D8SL ports connected to an ASMi-52. This loopback is used to test the interface circuits of the corresponding D8SL port, the line to the ASMi-52 and the operation of the whole ASMi-52 unit.

The loopback is activated by the command LP R REM_UNIT A:B. In response, the D8SL port sends a remote loopback request to the ASMi-52 connected to that channel, through the inband eoc channel.

The loopback is activated within the ASMi-52 user’s interface, which returns the received data through the transmit path.

Figure 7-17 shows the signal paths of a typical remote loopback on the remote ASMi-52 (activated on external port 1).

DXC Unit


.........

RemoteLoopback

ASMi-52

.....Port 8

Port 1

BusInterface Routing

Figure 7-20. Remote Loopback on Remote Unit, Signal Paths

Inband Code-Activated Loopback on Internal Port

The inband code-activated loopback, activated by the command LP INBAND A:B, is performed by transmitting, within all the active timeslots of the selected internal port, the loopback activation sequence specified in ANSI T1E1.2/93-003.

The activation sequence is generated by the test sequence generator of the port, and is inserted in the required timeslots of the data stream sent by the D8SL internal port.

When remote equipment which supports the inband code-activated loopback receives the loopback activation sequence, it connects a loopback at the output of its framer, as shown in Figure 7-21. This loopback affects only the timeslots defined by the user by means of the DEF BERT command.

.

Port 1

DXC Unit


Other PortInterface

.....Port 8

........

BusInterface

Test SequenceGenerator

Test SequenceEvaluator

Remote Unit

E1 PortInterface

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.

Remote Timeslot Loopback on Internal Port

The remote timeslot loopback is activated by means of the command LOOP TS REM. This loopback is similar to the remote loopback described above, except that it is activated only on the timeslots defined by the user by means of the DEF BERT command.

The loopback returns the data received within the timeslots defined by the user toward the remote equipment. Figure 7-22 shows the signal paths relevant to the affected timeslots.

DXC Unit


Other PortInterface

BusInterface

.....

Port 8

Port 1 Internal E1Port 1

Figure 7-22. Remote Timeslot Loopback

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


PortInterface

E3 Port Interface

"1"

Port 1Port 2

Port 16

.....

Figure 7-23. Local E3 Loopback (DE3 Modules)

Remote E3 Loopback (LOOP R)

The remote loopback fully checks the E3 data path, including the transmission path connecting the remote equipment to the DE3 module, and the port interface of the module. The remote loopback is activated on the selected port by the command LOOP R.

The remote E3 loopback is performed by connecting the E3 receive signal, after regeneration, to the transmit path. The test signal is provided by the equipment connected to the remote end of the link, which must receive its own transmission. The remote E3 loopback returns the received signal toward the remote E3 equipment port. Figure 7-24 shows a typical remote E3 loopback.

DXC Unit


PortInterface

E3 PortInterface

Port 1Port 2

Port 16

.....

Figure 7-24. Remote E3 Loopback (DE3 Modules)

Local Internal Port Loopback (LOOP L)

The local internal port loopback checks the DXC signal paths that end at the selected internal port and the connections to the equipment that provides the signal (or the individual timeslots, as applicable) reaching the port. The loopback is activated on the selected internal port by the command LOOP L.

The local internal port loopback returns the transmit signal of the selected internal port through its receive path (toward the DXC bus). The test signal is provided by the equipment whose signals (or timeslots) are routed to the selected internal port of the DE3 module: the equipment must receive its own transmission. During the loopback, the local E1 port sends an unframed “all-ones” signal to the E3 link. Figure 7-25 shows a typical internal port local loopback.



DXC Unit


PortInterface

Port 2

Port 16

.....

E3 PortInterface

Figure 7-25. Local Internal E1 Port Loopback (DE3 Modules)

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.

Local T3 Loopback (LOOP L)

The local T3 loopback fully checks the operation of the local DT3 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 T3 port. The loopback is activated on the selected port by the command LOOP L.

The loopback connects the transmit signal of the T3 port to the input of the T3 port receive path. The test signal is provided by the equipment whose signals (or timeslots) are routed to the DT3 module: each equipment must receive its own transmission.

During the loopback, the local T3 port sends an unframed “all-ones” signal to the T3 link. Figure 7-26 shows a typical local loopback.

DXC Unit


PortInterface

T3 PortInterface

"1"

Port 1Port 2

Port 28

.....

Figure 7-26. Local T3 Loopback (DT3 Modules)

Remote T3 Loopback (LOOP R)

The remote T3 loopback fully checks the T3 data path, including the transmission path connecting the remote equipment to the DT3 module, and the port interface of the module. The loopback is activated on the selected port by the command LOOP R.



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


PortInterface

T3 PortInterface

Port 1Port 2

Port 28

.....

Figure 7-27. Remote T3 Loopback (DT3 Modules)

Local Internal Port Loopback

The local internal port loopback checks the DXC signal paths that end at the selected internal port, and the connections to the equipment that provides the signal (or the individual timeslots, as applicable) reaching the port. The loopback is activated on the selected internal port by the command LOOP L.

The local internal port loopback returns the transmit signal of the selected DS1 internal port through its receive path (toward the DXC bus). The test signal is provided by the equipment whose signals (or timeslots) are routed to the selected internal port of the DT3 module: the equipment must receive its own transmission. During the loopback, the local port sends an unframed “all-ones” signal to the T3 link. Figure 7-28 shows a typical local internal port loopback.

RoutingBusInterface

.....

Port 16

Port 1

.........

DXC Unit


Other PortInterface

Figure 7-28. Local Internal Port Loopback (DT3 Modules)

Fractional STM-1 Module Test and Diagnostic Functions The test and diagnostic functions supported by DFSTM-1 modules are as follows:

• External STM-1 Port Loopbacks: user-activated local and remote loopbacks.

• Internal E1 Port Loopbacks: user-activated local and remote loopbacks.



• 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.

Local STM-1 Port Loopback

The local STM-1 port loopback connects the STM-1 transmit signal, generated by the SDH overhead (SOH) processor, to the receive input of the processor. Figure 7-29 shows signal paths when a local STM-1 port loopback is activated.

While the loopback is activated, the local STM-1 port sends an unframed “all-ones” signal to the STM-1 link, therefore the remote equipment may lose SDH frame alignment.

The test signal is provided by the equipment whose signals (or timeslots) are routed to the DFSTM-1 module: each equipment must receive its own transmission. This test fully checks the operation of the local DFSTM-1 module, except for the line interface (LIU); it also checks the DXC signal paths that end at the DFSTM-1 internal E1 ports.

DXC UnitDSTM1 Module


PortInterface

Port 2

Port 30

.....

E1Mapper

SOHProcessor

STM-1LIU

Port 1

"1"

Figure 7-29. Local Loopback on External STM-1 Port

Remote STM-1 Port Loopback

The remote STM-1 port loopback returns the recovered STM-1 receive signal provided by the STM-1 LIU toward the remote STM-1 equipment port. The loopback is activated at the line side of the SDH overhead processor signal. Figure 7-30 shows signal paths when a remote STM-1 port loopback is activated.



PortInterface

Port 2

Port 30

.....

E1Mapper

SOHProcessor

STM-1LIU

Port 1

"1"

Figure 7-30. Remote Loopback on External STM-1 Port



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.

Local Internal E1 Port Loopback

The local internal E1 port loopback returns the transmit signal of the selected internal E1 port through its receive path (toward the DXC bus). Figure 7-31 shows signal paths when the local loopback is activated.

The test signal is provided by the equipment whose signals (or timeslots) are routed to the selected internal E1 port of the DFSTM-1 module: the equipment must receive its own transmission.

While the loopback is activated, the transmit data of the local E1 port remains connected to the STM-1 link. This test checks the DXC signal paths that end at the selected internal port, and the connections to the equipment that provides the signal (or the individual timeslots, as applicable) reaching the port.



PortInterface

Port 2

Port 30

.....

E1Mapper

SOHProcessor

STM-1LIU

Figure 7-31. Local Loopback on Internal E1 Port

Remote Internal E1 Port Loopback

The remote internal E1 port loopback returns the receive signal of the selected internal E1 port, provided by the E1 mapper, to the transmit path of the same port (toward the STM-1 link). Figure 7-32 shows the signal paths when a remote loopback is activated.



PortInterface

Port 2

Port 30

.....

E1Mapper

SOHProcessor

STM-1LIU

Figure 7-32. Remote Loopback on Internal E1 Port



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.

Local Internal VC-12 Port Loopback

The local internal VC-12 port loopback returns the VC-12 transmit signal through the same VC-12 receive path (toward the DXC bus). Figure 7-33 shows signal paths when the local loopback is activated.

The test signal is provided by the equipment whose signals (or timeslots) are routed to the corresponding internal E1 port, to the selected VC-12 port of the DFSTM-1 module: that equipment must receive its own transmission.

While the loopback is activated, the transmit data of the local VC-12 port remains connected to the STM-1 link. This test checks the same DXC signal paths that are checked by a local internal E1 port loopback, and in addition checks the E1 mapper circuits that process the signals of the selected internal VC-12 port.



PortInterface

Port 2

Port 30

.....

E1Mapper

SOHProcessor

STM-1LIU

Port 1

Figure 7-33. Local Loopback on Internal VC-12 Port

SEND RDI Test

The SEND RDI test function, activated by means of the LOOP SND RDI command, enables the user to test the response of the transmission path to the reception of an RDI indication.

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.


7-30 Network-Controlled Loopback Functions

7.4 Network-Controlled Loopback Functions

Modules with T1 Line Interfaces When equipped with T1 line interfaces, the DXC supports two types of network-controlled loopbacks: network line loopback and network payload loopback.

The available network-controlled loopback functions are described in the following paragraphs. The loopbacks are identified by the designation displayed by the DXC.

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


PortInterface

T1 PortInterface

Figure 7-34. Latching Network Line Loopback (T1 Module)

The activation/deactivation code depends on the port framing mode:

SF (D4) The network line loopback is activated when the DXC detects the continuous transmission of the repeating sequence 10000..... for at least 5 seconds, and is deactivated by the transmission of the sequence 100...... for at least 5 seconds.

ESF The network line loopback is activated when the DXC detects the pattern 00001110 11111111 on the FDL, and is disconnected by the reception of the pattern 00111000 11111111 (rightmost bit transmitted first).

Alternately, the network line loopback is also activated by the pattern listed above for SF (D4) framing.

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.


BER Testing 7-31

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

T1 PortInterface


PortInterface

Figure 7-35. Network Payload Loopback (T1 Module)

Modules with T3 Line Interfaces Modules with T3 line interfaces support the network-activated T3 line loopback.

Network-Activated T3 Line Loopback

The T3 line loopback is similar to the remote T3 equipment port loopback, except that it is activated by a command sent through the DS3 inband path maintenance data link. The loopback signal path is as shown in Figure 7-27 for the remote T3 loopback.

7.5 BER Testing

The BER test is used to evaluate data transmission through a selected port of an I/O module or through the links serving a DIM module, without using external test equipment. BER test is activated by the LOOP BERT command.

To enable BER testing, the modules have a built-in test pattern generator and bit error detector. To provide compatibility with other BER testing equipment, the user can select the test pattern, and can rapidly check error detection by inserting errors at calibrated rates.

BER testing is performed only on the active timeslots. During BER testing, it is necessary to activate a remote loopback on the remote equipment. This action can be performed by means of the management system controlling the remote equipment. However, for convenience, you can also activate/deactivate the required remote loopback by transmitting inband codes in accordance with ANSI T1E1.2/93-003.


7-32 BER Testing

DHS and D8HS Modules Data transmission is checked by applying 27 - 1 (127) bit pseudo-random sequence generated by an internal test sequence generator towards the digital processing circuits in the DCL.3 module. The transmitted data is returned by means of a loop 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 evaluator output 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 255. The number of errors is accumulated from the BER test activation.

During the BER test, the tested port is disconnected from the user data equipment, and the DSR line is turned off (Figure 7-36).

DXC Unit



PortInterface


DHS Or D8HS PortInterface

Figure 7-36. BER Testing (DHS and D8HS Modules)

DE1B, DT1B, DHL, D4E1, D8E1, D4T1, D8T1 Modules For these modules, the BER test is used to evaluate data transmission through the link connected to a selected module port, and therefore the flow of test signals is different. Figure 7-37 shows the signal paths.

Data transmission is checked by applying the user-selected pseudo-random sequence, which is generated by the internal test sequence generator of the module, towards the remote equipment. The transmitted test sequence, returned by the loopback, is applied to the 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. 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 DCL.3 module.


BER Testing 7-33

DXC Unit



PortInterface


PortInterface

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).

DXC Unit


Port 1

.....

Port 2

Port 8

DIM




Figure 7-38. BER Testing (DIM Module)

During BER testing, it is necessary to activate a remote loopback on the remote DIM module, or on the equipment connected to the remote DIM module. This action can be performed by means of the management system controlling the remote equipment, however for convenience, the user can also activate the remote loopback by sending inband a special loopback activation code.


7-34 BER Testing

D8U, D16U Modules D8U and D16U modules support a BER test on the remote ASMi-31-2 activated through one of the ports on an ASMi-31-2 connected to that port (available only when the port is configured for /1 operation). The BER test, activated by the command LOOP BERT REM_UNIT A:B, is used to evaluate data transmission through a selected external port of the D8U or D16U module and the line connecting it to the ASMI-31-2, without using external test equipment.

The ASMi-31-2 has a built-in BER pattern tester and pattern generator. The pattern generator, normally activated together with the BER pattern tester, sends a 511 pattern according to ITU V.52 standard towards the external port of the D8U or D16U module. If errors are detected by the BER tester, an ERR LED indicator on the ASMi-31-2 unit blinks or remains ON.

In order to enable the pattern tester on the ASMi-31-2 to evaluate the correct pattern, three options are available:

• Perform the local loop on the D8U/D16U port connected to the ASMi-3-2 modem (LOOP L A:B command)

• Connect external testing equipment to the DXC port that is cross-connected to this D8U/D16U port

• Perform a local loopback on the port cross-connected to this D8U/D16U port.

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.

DXC Unit

DigitalProcessingUnit (DCL.3)

.....Port 16

Port 1

BusInterface

.........

ASMi-31-2 (NT)

PatternGenerator

PatternTester

Routing

Figure 7-39. BER Test on Remote ASMi-31-2


BER Testing 7-35

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


Other PortInterface

.....Port 8

Port 1 .........

BusInterface



Figure 7-40. BER Testing (D8SL Module)


7-36 BER Testing

Management Port Connectors A-1

Appendix A Connector Wiring

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.

A.2 Management Port Connectors

DCL.3 Module with RS-232 Interfaces The ports located on the DCL.3 module have standard RS-232 interfaces. The interfaces are terminated in two connectors, designated CONTROL and MNG:

• The CONTROL connector contains a DCE interface.

• The MNG connector can provide either a DCE or DTE interface, in accordance with the settings of the DCL.3 internal interface selectors (for information on internal settings, refer to Chapter 4).

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).

The connection to a terminal with 25-pin connector is made by means of a crossed cable, wired in accordance with Figure A-1.

• The connection of the CONTROL connector to a modem having a 9-pin connector, for connection to a remote supervision terminal, is made by means of a standard crossed cable, wired in accordance with Figure A-2.

The connection of the CONTROL connector to a modem having a 25-pin connector, for connection to a remote supervision terminal, is made by means of a crossed cable, wired in accordance with Figure A-1.

Appendix A Connector Wiring DXC-8R/10A/30/30E Installation and Operation Manual

A-2 Management Port Connectors

Table A-1. CONTROL Connector Wiring

Pin Line Direction

1 Data Carrier Detect (DCD) From DXC

2 Receive Data (RD) From DXC

3 Transmit Data (TD) To DXC

4 Data Terminal Ready (DTR) To DXC

5 Signal Ground (SIG) Common reference and DC power supply ground

6 Data Set Ready (DSR) From DXC

7 Request to Send (RTS) To DXC

8 Clear to Send (CTS) From DXC

9 Ring Indicator (RI) To DXC

To TerminalTo DCL.3CONTROLConnector

Module Side Terminal Side

TD

RTS

CTS

DSR

DCD

RI

DTR

GND

RD

3

2

7

8

6

1

9

4

5

2

3

4

5

6

8

22

20

7

25 PinConnector

9 PinConnector

Figure A-1. 25-Pin Terminal Cable Wiring - Connection to CONTROL Connector

To ModemTo DCL.3CONTROLConnector

Module Side Modem Side

TD

RTS

CTS

DSR

DCD

RI

DTR

GND

RD

3

2

7

8

6

1

9

4

5

2

3

8

7

4

1

9

6

5

9-PinConnector

9-PinConnector

Figure A-2. 9-Pin Crossed Cable Wiring - Connection to CONTROL Connector

DXC-8R/10A/30/30E Installation and Operation Manual Appendix A Connector Wiring

Management Port Connectors A-3

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.

Table A-2. MNG Connector Wiring

Pin Line Direction

1 Data Carrier Detect (DCD) To DXC

2 Receive Data (RD) To DXC

3 Transmit Data (TD) From DXC

4 Data Terminal Ready (DTR) From DXC

5 Signal Ground (SIG) Common reference and DC power supply ground

6 Data Set Ready (DSR) To DXC

7 Request to Send (RTS) From DXC

8 Clear to Send (CTS) To DXC

9 Ring Indicator (RI) To DXC

To ModemTo DCL.3

MNGConnector

Module Side Modem Side

TD

RTS

CTS

DSR

DCD

RI

DTR

GND

RD

3

2

7

8

6

1

9

4

5

2

3

4

5

6

8

22

20

7

25 PinConnector

9 PinConnector

Figure A-3. 25-Pin Modem Cable Wiring - Connection to MNG Connector

Appendix A Connector Wiring DXC-8R/10A/30/30E Installation and Operation Manual

A-4 Station Clock Connector

DCL.3 Module with 10/100BaseT Ethernet Interface The DCL.3 version with 10/100BaseT Ethernet interface has two connectors:

• A 9-pin female connector designated CONTROL, which is identical to the CONTROL connector described in Table A-1.

• An RJ-45 connector designated ETHERNET, which provides access to the Ethernet interface of the DCL.3 module.

The Ethernet interface is configured as a station port. ETHERNET connector wiring is given in Table A-3.

Table A-3. RJ-45 ETHERNET Connector Wiring

Pin Designation Function

1 TX+ Transmit + wire

2 TX- Transmit - wire

3 RX+ Receive + wire

4, 5 N/C Not connected

6 RX- Receive - wire

7, 8 N/C Not connected

A.3 Station Clock Connector

The balanced interface of the station clock port, located on DCL.3 modules installed in the DXC enclosure, is terminated in an eight-pin RJ-45 connector, wired in accordance with Table A-4. This connector includes the connections to the alarm relay contacts, and a +5V output that can supply up to 16 mA.

In addition, the DCL.3 station clock port can also include an unbalanced interface, terminated in a BNC connector. To use the station clock interface, first make the required internal settings, as explained in Chapter 4.

The station clock connector of the DCL.3 module cannot be used with cables prepared for DCL.2 modules.

Table A-4. Station Clock Connector, Pin Allocation

Pin Designation Function

1 CLK (T) Station clock (tip)

2 CLK (R) Station clock (ring)

3 FRAME GND Frame ground (through internal jumper)

4 RELAY COMMON Common alarm relay contact

5 ALARM IN Alarm input line (RS-232 levels)

6 +5V OUT +5V, max. 16 mA output (with current limiting)

7 RELAY Normally-open contact to pin 4

8 RELAY Normally-closed contacts to pin 4

Caution

Configuration Error Messages B-1

Appendix B Error and Alarm Messages This Appendix presents the messages sent by DXC systems to supervision terminals, to report configuration errors and alarm conditions.

B.1 Configuration Error Messages

The DXC reports configuration errors by sending messages to the supervision terminal. The messages are classified as error messages, and warning messages. The difference between a configuration error and a warning is that after an error is detected, it is not possible to update the hardware, whereas after a warning the user can choose whether to perform or not the hardware update.

The messages have the format ERROR or WARNING, followed by a three-digit code. The DXC displays a short description of the error message after the error code.

The error messages are explained below.

ERROR 000 MASTER AND FALLBACK CLOCKS ARE THE SAME

You are trying to select the same source as both master and fallback clock source. Check and change as required.

WARNING 001 MISMATCH BETWEEN HARDWARE AND DATABASE There is a mismatch between the module type configured in the specified slot in the temporary database (located in the editing buffer, in RAM) and the detected module type.

ERROR 002 INVALID MASTER CLOCK SOURCE The master clock source is invalid.

• Check that the port specified as master clock source is installed, and is of the correct type (T1 or E1).

• Check that the specified port is defined in the database.

ERROR 003 INVALID FALLBACK CLOCK SOURCE The fallback source is invalid.

• Check that the port specified as fallback clock source is installed, and is of the correct type (T1, E1, or DHS port with DTE2 timing mode).

• Check also that the specified port is defined in the database.

ERROR 004 ILLEGAL DCD DELAY AND INTERFACE COMBINATION You are trying to select a non-zero DCD_DEL value after the DXC supervisory port interface has been set as DCE.

ERROR 005 CONFLICT IN INTERFACE AND DSR PARAMETERS You selected DSR=ON after the supervisory port interface has been set to DTE.

Appendix B Error and Alarm Messages DXC-8R/10A/30/30E Installation and Operation Manual

B-2 Configuration Error Messages

ERROR 006 TIME-SLOT 16 OF E1-G732S FRAME IS MAPPED You are trying to connect a timeslot to timeslot 16 of an E1 port operating with G732S framing. This is not allowed.

WARNING 007 CONFLICT BETWEEN FRAME AND TIME-SLOT TYPES Conflict in timeslot type and link framing mode: the VOICE type can be selected on an E1 port only when the framing mode is G732S. Check and change as required.

ERROR 008 TIME-SLOT OUT OF RANGE The timeslot number is out of the range supported by the corresponding ports. The allowed range of timeslot numbers is as follows:

Source Type Destination Type Timeslot Range

T1 T1 1 to 24

E1 T1 1 to 24, F

T1 E1 1 to 31

E1 E1 1 to 31

ERROR 009 ILLEGAL CARD TYPE MAPPED IN THE MATRIX It is not allowed to route individual timeslots to DIM or E3/T3 destination ports.

ERROR 010 ILLEGAL DESTINATION PORT NUMBER FOR CARD Illegal port number for destination module type: the destination module does not support the specified port number. Check and change as required.

ERROR 011 MORE THAN ONE TS MAPPED TO THE SAME DEST Illegal timeslot mapping. You are trying to connect two or more source timeslots to the same destination. Check and change as required.

ERROR 012 SEQUENTIAL SOURCE TIME-SLOT OUT OF RANGE Illegal sequential allocation, i.e., the last source timeslot would exceed the number of timeslots available on the link (the sum of the starting source timeslot and the number of the timeslots to be connected is greater than the maximum number of timeslots). Check and change as required.

ERROR 013 SEQUENTIAL DESTINATION GREATER THAN 31 Illegal sequential allocation, i.e., the last destination timeslot would exceed the maximum allowed, 31 (the sum of the starting destination timeslot and the number of the timeslots to be connected is greater than 31). Check and change as required.

ERROR 014 SEQUENTIAL DESTINATION TS OUT OF RANGE Illegal sequential allocation, i.e., the last timeslot would exceed the number of timeslots available on the link (the sum of the starting source timeslot and the number of the timeslots to be connected is greater than the maximum number of timeslots). Check and change as required.

WARNING 015 VOICE OOS CODE IS NOT THE SAME FOR MODULE Different voice OOS codes have been selected for the two ports of the specified module. Check and change as required.

WARNING 016 DATA OOS CODE NOT THE SAME FOR MODULE Different data OOS codes have been selected for the two ports of the specified module. Check and change as required.

DXC-8R/10A/30/30E Installation and Operation Manual Appendix B Error and Alarm Messages


WARNING 017 TRYING TO CONNECT TS TO THE SAME PORT You are trying to connect a timeslot to another timeslot of the same port. This is not allowed. Check and change as required.

ERROR 018 FRAME TYPE OF PORT 1&2 MUST BE THE SAME Different E1/T1 framing types have been selected for the two ports of the same module. This is not allowed for E1/T1 modules. Check and change as required.

WARNING 019 TIME-SLOT ‘F’ IS MAPPED This messages notifies you that the F-bit has been routed to another timeslot.

ERROR 020 CHANNEL SPEED NOT MATCH OPEN NUMBER OF TS The number of timeslots allocated to a DHS port does not match the nominal data rate configured for that port.

ERROR 021 TIMESLOT TYPE NOT SUPPORTED BY CARD An E1 or T1 timeslot defined as a voice timeslot has been routed to a DHS port. DHS portssupport only data timeslots. Check and change as required.

WARNING 022 SYSTEM IN LOOP A test or loopback is activated on a DXC port. Changes in BERT parameters will not take effect while the BER test is running.

ERROR 023 MORE THAN ONE PORT IS MAPPED TO DHS More than one port is routed to a DHS port. This is not allowed, because all the timeslots of a DHS port must be routed to the same port. Check and change as required.

ERROR 024 MULTIPLIER, SPEED CONFLICT The DHS clock mode is DCE or DTE1, and the FIFO size is not AUTO. Check and change as required.

ERROR 025 ILLEGAL SPEED FOR AUXILIARY DEVICE The supervisory port interface has been set to AUTO (Autobaud), when the AUXILIARY_DEVICE is not TERMINAL. Check and change as required.

ERROR 026 CONFLICT IN MANAGEMENT AND PORT PARAMS You are trying to enable inband SNMP or Telnet management on a T1 port, but the port parameters are incorrect (e.g., the framing mode is SF, or you have enabled transparent transfer of the FDL). Check and change as required.

ERROR 027 MANAGEMENT ON AND F-BIT MAPPED You are trying to enable inband SNMP or Telnet management on a T1 port, but the port F-bit is mapped. Check and change as required.

ERROR 028 NUMBER OF MANAGEMENT PORTS EXCEEDED MAXIMUM The total number of ports using inband management cannot exceed 15. Check and change as required.

ERROR 029 TS NOT SYMMETRIC The current matrix mode is bidirectional, but asymmetric timeslot connections have been detected. Check routing and change as required.

ERROR 030 CONFLICT BETWEEN TS TYPES IN UNIDIRECT MODE The current matrix mode is unidirectional, and a connection between a voice timeslot and a data timeslot has been detected. All the timeslots connected by a unidirectional routing must be of the same type.

WARNING 031 ILLEGAL DHS PORT FOR DHS BERT MODE The port specified as destination during the definition of BERT conditions is not a DHS port. Check and enter the correct port number.



WARNING 032 BERT TS NOT SAME AS DEFINED DHS TS During the definition of BERT conditions with a DHS port destination, it has been found that the timeslot allocation has been changed.

ERROR 033 DIM DEST PORTS MUST BE FROM THE SAME TYPE All the ports configured as destinations to a DIM module must be of the same type (either only T1, or only E1 ports).

ERROR 034 SAME DEST PORT CONFIGURE MORE THAN ONCE Same destination port has been configured more than once as a DIM destination port.

ERROR 035 DIM DEST PORT MUST BE T1/E1 CARD All the DIM destination ports must be T1 or E1 ports.

ERROR 036 DIM DEST PORT CONFIGURED TO ANOTHER DIM A T1 or E1 port that has been connected to a DIM module is already configured to anotherDIM module.

ERROR 037 CONFLICT IN TS MAPPING A T1 or E1 port has been configured as a DIM destination port, but some of its timeslots are already mapped to another port, or timeslots of a T1 or E1 port already configured as a DIM destination port were connected to another port.

ERROR 038 CONFLICT BETWEEN PORT ALLOC & INTERFACE TYPE An E1 interface of a DIM module can be connected only to one E1 destination port, or to two T1 destination ports.

ERROR 039 ILLEGAL CLOCK MODE A DIM module is configured to DCE clock mode and INVERT polarity. Check and change as required.

ERROR 060 TOO MANY MANAGEMENT TIME SLOTS IN PORT Only one timeslot of any given port can be used for management traffic. Check timeslot assignment.

ERROR 061 BAD IP ADDRESS An invalid IP address has been entered. Check and correct.

ERROR 062 BAD SUBNET MASK An invalid subnet mask has been entered. Check and correct.

ERROR 063 BAD GATEWAY An invalid gateway IP address has been entered. Check and correct.

ERROR 064 MISSING ONE OPEN MANAGEMENT TIME-SLOT The selected management mode requires the allocation of a timeslot for management traffic, but no timeslot has been actually allocated to management.

ERROR 065 ILLEGAL OPEN MANAGEMENT TIME-SLOT The selected management mode does not require the allocation of a timeslot for management traffic, but a timeslot has been allocated to management.

WARNING 066 ILLEGAL PORT FRAME CONFIG ON SLOT For E1 I/O modules, if different framing modes must be used, always select G732S for port 1 and G732N for port 2.

ERROR 067 TEST PORT TIME-SLOT CONFLICT A timeslot has been connected to both a data port, and to a test port. This is not allowed.



ERROR 068 MONITOR ON TEST PORT IS ILLEGAL To enable monitoring, the monitored port must be defined as the destination of the test port. A test port cannot be defined as a monitored port.

ERROR 069 CAN’T CHANGE CARD TYPE OF TEST/MONITOR PORT The module installed in a slot that is programmed as either a test port, or a monitored port,has been replaced by a module of a different type. This is not allowed.

ERROR 070 BAD TEST PORT FRAME-TYPE It is not allowed to connect a voice timeslot of a monitored port to an E1 test port using G732N framing.

ERROR 071 BAD TIME-SLOT TYPE FOR TEST PORT It is not allowed to connect a voice timeslot of a monitored port to a DHS.2 test port.

ERROR 072 TS MAPPED INTO SECONDARY PORT When using Y-cable redundancy or single slot protection, it is not allowed to route timeslots to a port defined as the secondary port of the redundant pair, nor select the secondary port as a monitored port.

ERROR 073 TEST PORT MAPPED INTO SECONDARY PORT You are trying to route the test port to the secondary slot of a redundant pair. This is not allowed.

ERROR 074 MANAGER X BAD IP ADDRESS Check that the IP address of each network management station included in the manager list is in the dotted-quad format (see Appendix C).

ERROR 075 MANAGER X BAD SUBNET MASK Check that the subnet mask of each network management station included in the manager list is in the dotted-quad format (see Appendix C).

ERROR 076 TWO OR MORE MANAGERS WITH SAME IP ADDRESS Check that each network management station has a different IP address.

ERROR 077 MORE THAN ONE MANAGEMENT TS IN E3/T3 MODULE When configuring E3 or T3 modules, only one internal E1 or DS1 port can be configured to carry management traffic in a dedicated timeslot.

ERROR 078 C-BIT AND MANAGEMENT TS NOT ALLOWED When configuring T3 modules operating in the C-bit parity mode to use the C-bit data link for inband management, it is not allowed to configure any of the internal DS1 ports for inband management.

ERROR 079 TOO MANY E3/T3 CARDS Only one E3 or T3 module can be physically installed in a DXC enclosure and configured in the database. However, two modules of the same type may be installed, provided that they are configured to provide redundancy of the E3 or T3 link (i.e., the combined line and hardware redundancy mode is enabled)

ERROR 080 ILLEGAL TS ASSIGNMENT FOR TRANSPARENT MODE When a port is configured for operation in the transparent or unframed mode, all of its timeslots must be mapped one-to-one to the same destination slots, and must be defined as data timeslots.

ERROR 081 CONFLICT BETWEEN LINK MODES A link configured for operation in the transparent or unframed mode can be routed only toanother link configured for the transparent, respectively unframed, mode.



ERROR 082 ILLEGAL ROUTING PROTOCOL FOR AUXILIARY DEVICE When the AUXILIARY DEVICE=TERMINAL, you must select ROUTING_PROT=NONE.

WARNING 083 TWO E3/T3 CARDS MUST BE PARTS OF REDUND PAIR The DXC system supports only one active E3 or T3 module. Therefore, when the system detects that a second E3 or T3 module is installed or defined, it generates this warning to remind the user to configure the two modules as a redundant pair.

ERROR 084 E3/T3 CARD NOT DEFINED AS REDUNDANT See WARNING 083. This error is generated if during the sanity check performed after the UPDATE DB command is entered, two E3 or T3 modules not configured as a redundant pair, are detected.

ERROR 085 E3/T3 INT LINKS MAPPED INTO THEMSELVES It is not allowed to route timeslots between internal DS1 or E1 ports of the same E3 or T3 module.

ERROR 086 CONFLICT BETWEEN BERT AND MANAGEMENT TS You are trying to configure the BERT option on a timeslot that has already been defined as a management timeslot.

ERROR 088 MASTER CLOCK NOT CONNECTED The channel you are trying to select as the master clock source is either not connected, or its clock mode is not DTE2. Check and change as required.

ERROR 089 FALLBACK CLOCK NOT CONNECTED The channel you are trying to select as the fallback clock source is either not connected, or its clock mode is not DTE2. Check and change as required.

ERROR 090 BERT IS NOT DEFINED ON PORT You are trying to run the LOOP BERT command on the port of a D8U or D16U module, but you have not defined the BERT on this port.

ERROR 091 BERT IS DEFINED ON MORE THAN ONE PORT You have defined the BERT on more than one port of the D8U or D16U module. Check and change as required.

ERROR 092 D-CHANNEL CONFIGURATION ERROR The D-channel of the D8U or D16U module is configured incorrectly. Check and change as required.

ERROR 093 AGGREGATE SPEED AND DEDICATE TS CONFLICT No timeslot was open while DEDICATE TS was defined.

ERROR 094 TOO MANY D CHANNELS ON THE SAME INT PORT You are trying to associate more than four D-channels to the same internal port of the D8U/D16U module.

ERROR 095 D-CHANNEL START BIT CONFLICT You are trying to associate more than one D-channels to the same start bit.

ERROR 096 BAD TRANSPARENT/UNFRAMED MODE CONFIGURATION Not all timeslots of the corresponding ports (configured for transparent or unframed mode) are open.

ERROR 097 ILLEGAL FRAME TYPE FOR REDUNDANCY MODE The frame type of the two redundant ports is not the same.

ERROR 098 ILLEGAL FRAME TYPE FOR DIM DESTINATION The frame type of the two DIM destination ports is not the same.



ERROR 099 ILLEGAL FRAME TYPE FOR TEST PORT The frame type of the test and monitored ports is not the same.

ERROR 100 ILLEGAL FRAME TYPE FOR MONITORED PORT The frame type of the test and monitored ports is not the same.

ERROR 101 INDICATION PARAMETER GROUP IS NOT THE SAME For DFSTM-1 modules, each group of four consecutive internal VC-12 ports must be assigned the same set of routing alarm indication parameters, that is, the following parameters must be identical for all the four ports in a group:

• AIS & RDI TRANSMIT ON EED

• AIS & RDI TRANSMIT ON SIGNAL LABEL MISMATCH

• AIS & RDI TRANSMIT ON PATH TRACE MISMATCH.

The first VC-12 internal ports group includes the ports 64, 65, 66, 67; the second group includes 68, 69, 70, 71; etc.

ERROR 102 CONFLICT BETWEEN DEDICATE TS AND EOC MODE A dedicated management timeslot is activated on the DHL/E1 or DHL/E1/2W module, while the eoc management mode is enabled (RX EOC parameter is ENABLE)

ERROR 103 SIGNAL OOS CODE IS NOT THE SAME FOR MODULE For DFSTM-1 modules, the same OOS signaling code must be assigned to all the internal E1 internal ports

ERROR 104 VOICE AND DATA OOS ARE NOT THE SAME FOR PORT For DFSTM-1 modules, identical data and voice OOS codes code must be assigned to a given internal port

ERROR 106 ILLEGAL MAP - SOURCE TS IS RESERVED The source timeslot cannot be mapped to the specified destination timeslot (SS:PP:TT), because the source timeslot is defined as reserved (this attribute can be assigned by the path management NMS application).

ERROR 107 ILLEGAL MAP - DESTINATION TS IS RESERVED The source timeslot cannot be mapped to the specified destination timeslot (SS:PP:TT), because the destination timeslot it is defined as reserved (this attribute can be assigned by the path management NMS application).

ERROR 108 IP, SUBNET AND GATEWAY CANNOT BE THE SAME You cannot configure the IP_ADDRESS, the SUBNET MASK, or the DEFAULT GATEWAY to the same value.

ERROR 109 8E1 FRAME TYPE AND DEDICATE TS CONFLICT For the D8E1 module, do not configure port 8 to operate in the unframed mode when the D8E1 management mode is DEDICATE TS.

ERROR 110 FRAME TYPE AND CRC-4 CONFLICT Use of CRC-4 is not possible for E1 ports configured to operate in the unframed mode.

ERROR 111 MORE THAN ONE E1 MAPPED TO THE SAME TU Both internal E1 ports of the dual-port DFSTM-1 module cannot be mapped to the same TU-12.

ERROR 112 CONFLICT BETWEEN SA_BIT AND TS 0 When the management traffic is transferred through TS 0, at least one national bit (Sa4 through Sa8) should be defined, and vice versa.



ERROR 113 T3(E3) AND STM MODULES INSTALLED TOGETHER

The DE3, DT3 or DT3/747 modules cannot be installed in the same chassis with the DFSTM-1 module.

ERROR 114 UNFRAMED AND TRANSPARENT MODE CONFLICT When operating in the unframed mode, the LINK MODE parameter must be set to REGULAR.

WARNING 115 POSSIBLE DATA ERROR BURST DURING UPDATE DB You have changed the timeslot allocation mode. Error in data may occur during the subsequent UPD DB operation.

WARNING 116 CONFLICT IN NUM OF ALLOC TS AND MAX_TS PARAMETER The number of used timeslots you have specified exceeds the value of MAX_TS parameter.

ERROR 117 WRONG MAX_TS VALUE FOR UNFRM MODE The MAX_TS value for the port operating in the unframed mode must be set at 32.

WARNING 118 CHANGE OF USED TS MAY CAUSE DATA ERROR BURST You have modified the MAX_TS parameter. Next time you change the number of used timeslots (NUM_OF_TS), data error burst may occur.

ERROR 119 WRONG OPERATION MODE FOR STM REDUNDANCY

Redundancy operation is possible only when TERM MODE.is selested as the operation mode.

ERROR 120 WRONG 8(4)E1(T1) REDUNDANCY CONFIGURATION To define a redundancy pair of the D4E1, D4T1, D8E1 or D8T1 module, you have first to define all the previous ones. For example, to define the redundancy pair 3–4, you have first to define the 1–2 pair.

ERROR 121 ILLEGAL DEST START TS FOR DHS TO DHS CONFIG When mapping the DHS port timeslots to another DHS port, always set the START_DEST_TS parameter to 01.

ERROR 122 INCOMPATIBLE OPEN TS AND TS SPEED

The value of the RATE parameter defined on a port of the D8U, D16U module is lower than n x 64 kbps, where n is the number of connected timeslots.

ERROR 123 WRONG 8E1T1 MANAGEMENT AND REDUNDANCY CONFIG The management traffic via a dedicated timeslot cannot be defined on a port configured asredundant.

ERROR 124 DIFFERENT FRAME ON PRIMARY AND SECONDARY Framing mode should be the same on both ports configured as redundant.

ERROR 125 VC4 PORTS SHOULD HAVE SAME TU IN BP CONNECT When the DFSTM-1 module is operating in the BYPASS mode, the TU-12 numbers of the VC-4 port 133 and 134 must be the same.

ERROR 126 SAME E1 MAPPED IN BOTH VC4 TU PORTS

One internal E1 port cannot be mapped to both VC-4 internal ports of the dual-port DFSTM-1 module.

ERROR 127 ILLEGAL STM BYPASS CONFIGURATION BYPASS configuration is possible only for a dual-port DFSTM-1 module operating in the linear mode.



ERROR 128 ILLEGAL OPERATION MODE FOR MASTER CLK SRC The DXC master clock source cannot be set to receive clock of the STM-1 port when the DFSTM-1 module is operating in linear ADM mode.

ERROR 129 ILLEGAL OPERATION MODE FOR FBACK CLK SRC The DXC fallback clock source cannot be set to receive clock of the STM-1 port when the DFSTM-1 module is operating in linear ADM mode.

ERROR 130 D8SL's ANNEX SHOULD BE THE SAME IN ALL PORTS

The set of regional parameteres for all of the D8SL's ports should be set at the same value (either ANNEX A or ANNEX B).

ERROR 131 D8SL FRAME TYPE AND TS0 MODE CONFLICT

If the E1 framing method used by the selected internal port is set to G732S, the TS0_OVER_DSL parameter should be set to TRANSPARENT.

ERROR 132 D8SL FRAME TYPE AND REM CRC CONFLICT

If the E1 framing method used by the selected internal port is set to G732S, the REM_CRC-4 parameter should be set to NO.

ERROR 133 D8SL WRONG FRAME AND CRC FOR TS0 TRANSPARENT If the E1 framing method used by the selected internal port is set to G732N, and the REM_CRC-4 parameter is set to YES, the TS0_OVER_DSL parameter should be set to LOOPED.

ERROR 134 SA BITS TRANSPARENT MODE CONFLICT

SA bits transparent mode is applicable only between the adjacent ports (1 and 2, 3 and 4, etc.) If TRANS mode has been selected for a certain bit of the port, the same bit should be set to TRANS on the adjacent port.

ERROR 135 56 MULTIPLIER AND UNFRAME MODE CONFLICT

In the D8HS module, it is not allowed to set MULT=56 and SPEED=2048 (unframed mode) at the same time.

ERROR 501 ILLEGAL PORT LOOP COMBINATION One of the following conditions has been detected:

• You are trying to activate a local loopback on a T1 port when a network-activated loopback is active at that port. Wait until the network-activated loopback is released.

• You are trying to activate the remote loopback while the local loopback is already activated on the same port, or vice versa. First deactivate the currently active loopback.

• You are trying to activate the inband loopback while the BER test is activated on the same port. First deactivate the BER test.

ERROR 502 LOOP IS NOT ACTIVE You are trying to deactivate a loopback or test which is not active. Check and change as required.

ERROR 503 ILLEGAL COMMAND FOR CURRENT PORT MODE The command is not supported in the current port configuration (e.g., DSP PM A:B on a T1 port with SF framing or on an E1 port with CRC-4 disabled, or DSP FDL A:B on a T1 port with SF framing).

ERROR 504 ILLEGAL COMMAND FOR INSTALLED MODULE The selected module supports only commands of the type A:B and you are issuing a command of type A:* or A. Check and change as required.



ERROR 505 ILLEGAL COMMAND, MODULE NOT INSTALLED You are trying to issue a command that can be executed only if the module is installed, i.e., one of the LOOP, DSP PM A:B, DSP ST A:B (DSP ST A), or DSP FDL A:B commands.

ERROR 506 CURRENT LOOP ALREADY BEING PERFORMED You are trying to activate a loopback which is already active. Check and change as required.

ERROR 507 MODULE NOT DEFINED You are trying to execute a DEF PORT A:B command for a module that is not yet defined in the temporary database. Check and change as required.

ERROR 508 ILLEGAL COMMAND FOR CURRENT SYSTEM TYPE You are trying to execute a command that is not supported by the DXC-10A, e.g., DSP FLIP.

ERROR 511 SLOT TYPE OR PARAMETERS CONFLICT FOR REDUNDANCY It is not allowed to use the FORCE ONLINE command on ports which are not configured as redundant ports in a Y-cable configuration, and the redundant port must be on another module (slot).

ERROR 512 ILLEGAL RECOVERY MODE FOR FORCE OPERATION It is not allowed to use the FORCE ONLINE command on ports which are not configured for single slot protection, nor on redundant ports in a Y-cable configuration using AUTO recovery mode.

ERROR 514 ILLEGAL COMMAND ON SECONDARY PORT It is not allowed to use the DEF PORT, DEF BERT, or DEF TEST PORT commands on the secondary port of a Y-cable redundancy pair.

ERROR 515 SLOT ALREADY USED FOR REDUNDANCY You have defined a module already included in a Y-cable redundancy pair, or a port already included in a single-slot redundancy pair, in another redundancy pair.

ERROR 516 ILLEGAL COMMAND, HARDWARE AND DATABASE NOT THE SAME For some commands, e.g., DSP PM, the installed and programmed module types must be identical.

ERROR 517 ILLEGAL COMMAND ON OFFLINE PORT Some commands cannot be performed on the off-line port of an I/O redundancy pair.

ERROR 518 NEW IP ADDRESS WILL BE ACTIVE ONLY AFTER RESET Notifies you that new IP address will be used only after the DXC system is reset.

ERROR 519 NEW SUBNET MASK WILL BE ACTIVE ONLY AFTER RESET Notifies you that new subnet mask will be used only after the DXC system is reset.

ERROR 520 NEW DEFAULT GATEWAY WILL BE ACTIVE ONLY AFTER RESET Notifies you that new default gateway will be used only after the DXC system is reset.

ERROR 521 NEW READ COMMUNITY WILL BE ACTIVE ONLY AFTER RESET Notifies you that the new read community will be used only after the DXC system is reset.

ERROR 522 NEW WRITE COMMUNITY WILL BE ACTIVE ONLY AFTER RESET Notifies you that the new write community will be used only after the DXC system is reset..

ERROR 523 NEW TRAP COMMUNITY WILL BE ACTIVE ONLY AFTER RESET Notifies you that the new trap community will be used only after the DXC system is reset.



ERROR 524 TOO MANY E3/T3 CARDS Only one E3 or T3 module can be physically installed in a DXC enclosure and configured in the database. However, two modules of the same type may be installed, provided that they are configured to provide redundancy of the E3 or T3 link (i.e., the combined line and hardware redundancy mode is enabled)

ERROR 525 ILLEGAL FIELD VALUE The value entered in the field is not valid

ERROR 526 TOO MANY BERT PORTS FOR CARD You are trying to activate BERT on another port of a D8U or D16U module, while BERT is already activated on one of the module ports. This is not allowed, as the module has only one BERT circuit

ERROR 527 ILLEGAL COMMAND FOR INTERFACE TYPE The following loopbacks are supported only when a D8U or D16U port is configured as LT-1:

• LB1

• LB2

• LLBD

• LOOP REM LOOP ON REM UNIT

• BERT ON REM UNIT

ERROR 528 BUS EXCEEDED No free bus links left in the DXC matrix (all 30 bus links are occupied)

ERROR 529 TS NEED TO BE OPENED FOR BERT The BER test cannot be activated on an E1/T1 module before a timeslot is connected on the corresponding port

ERROR 530 TS NEED TO BE OPENED FOR TS REM The remote timeslot loopback cannot be activated on an E1/T1 module before a timeslot isconnected on the corresponding port

ERROR 531 TOO MANY OPEN TS FOR IDSL MODULE The number of timeslots connected on the D8U or D16U module port cannot exceed two.

ERROR 532 ILLEGAL COMMAND FOR TS ALLOCATION MODE This command is possible only if the static timeslot allocation mode has been selected under DEF SYS.

ERROR 533 CURRENT LOOP ALREADY WORK ON ANOTHER LINK The FORCE operation has been already activated on another link of the DFSTM-1 module.To cancel the FORCE operation, use CLR FORCE SS PP command.

ERROR 534 CHANNEL SPEED NOT MATCH OPEN NUMBER OF TS

The value of the RATE parameter defined on a port of the D8U, D16U module is not equal to n x 64 kbps, where n is the number of connected timeslots.


B-12 Alarm Messages

B.2 Alarm Messages

DXC maintains an alarm buffer. The buffer can store one alarm event of each type, and a maximum of 100 alarms can be displayed on the supervision terminal. The DXC operator can view the contents of the alarm buffer on the supervision terminal. In addition, alarms are also sent as traps to network management stations.

Table B-1 presents the alarm messages displayed on the supervision terminal in ascending order of their code numbers, specifies their type (event or state), severity (major or minor), and lists the actions required to correct the alarm condition. In these messages, A represents the I/O module number and B represents the module port number.

A state alarm is an alarm that is in the ON state while a certain condition is present, and automatically changes to OFF when the condition is no longer present. This type of alarm cannot be cleared (removed from the alarm buffer) while it is in the ON state. An event alarm is an alarm that records the occurrence of an event. This type of alarm can be cleared at any time.

To correct the reported problem, perform the corrective actions specified for the corresponding alarm message in the order given in the table, until the problem is corrected. If the problem cannot be corrected by carrying out the listed actions, have the DXC checked by the technical support personnel.

Table B-1. DXC Alarm Messages

No. Message Description Corrective Actions Default Severity and Type

01 REAL TIME CLOCK BATTERY FAILURE

The battery powering the DXC internal real-time clock while DXC is not powered has failed

Have the DXC-10A or the DCL.3 module repaired

Major (state)

02 PS-A FAILURE The power supply A is missing, is not turned on or failed.

Install, turn on, or replace the corresponding power supply module

Major (state)

04 PS-B FAILURE The power supply B is missing, is not turned on or failed.

Install, turn on, or replace the corresponding power supply module

Major (state)

08 ALARM BUFFER OVERFLOW

More than 100 alarms entries have been written in the buffer since the last clear command

Read the messages, and then send the CLR ALM command from the supervision terminal

Minor (event)

09 HARDWARE FAILURE IO-A

Technical failure in the module installed in the specified slot

Replace the DXC I/O module installed in the specified slot

Major (state)

10 MODULE WAS REMOVED, IO-A

The module installed in the specified slot has been removed

Check the reason for module removal Minor (event)

11 DB-INIT SWITCH IS ON

Section DB INIT of switch SW2 is set to ON

If it is no longer necessary to enforce the default database parameter values, change setting to OFF

Minor (event)

Note


Alarm Messages B-13

Table B-1. DXC Alarm Messages (Cont.)


12 CLOCK WAS CHANGED TO FALLBACK

The main clock source of the DXC failed, and the fallback clock source has been selected

Check the port providing the master clock source: • 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

Minor (event)

13 CLOCK WAS CHANGED TO INTERNAL

Both the main and fallback clock sources of the DXC failed, and the internal clock source has been selected

Check the port providing the master and fallback clock sources: • 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

Minor (event)

14 CLOCK WAS CHANGED TO MASTER

The DXC switched back to the clock source selected as the master source

Normal state - no action required Minor (event)

15 CL FLIP HAS OCCURRED

The other DCL.3 has been selected as the on-line module

Check the reason for flipping using the DSP FLIP command, and act accordingly

Major (event)

16 PROGRAMMED, INSTALLED MODULE MISMATCH, IO-A

The modules that have been read from the DXC do not match the modules programmed in the database

Either change the modules, or change the information appearing in the database

Major (state)

17 CLA, CLB DIFFERENT SOFT/HARD REVISION

The software and/or hardware revision of the DCL.3 module installed in slot CL-A differs from that of the DCL.3 module installed in slot CL-B

If the hardware versions differ, replace the DCL.3 module with the older version. Check the software versions of the 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.

Minor (event)


B-14 Alarm Messages



18 DP DIAL CYCLE FAILED

The current cycle of call attempts failed

Check the modem connected to the NETWORK connector. If the called numbers are often busy, you may also increase the number of call retries.

Major (event)

19 DATABASE CHECKSUM ERR

DXC technical failure (internal database error)

1. Load the default configuration in the place of the current database (from the supervision terminal, enter the INIT DB command).

2. Replace the DXC-10A, or replace DCL.3 modules one by one.

Major (state)

20 PSWRD SWITCH IS ON

Section PASSWORD of switch SW2 of the DCL.3 module is set to ON

Set the switch to OFF. Minor (event)

21 SP-PAR SWITCH IS ON

Section TERM of switch SW2 of the DCL.3 module is set to ON

If it is no longer necessary to enforce the default supervisory link parameters, change setting to OFF.

Minor (event)

22 PC-SP SWITCH IS ON

Section PC/SP of switch SW1 is set to ON

Set the switch to OFF. Minor (event)

23 LOSS OF STATION CLOCK

The external station clock signal is missing

1. Check cable connections to the port connector.

2. Check the equipment providing the external clock signal.

3. Replace the DXC-10A or the DCL.3 modules.

Minor (state)

24 DP PRIMARY CALL FAILED

The call attempts to the primary dial-out number failed

If the number is not busy, check the modem connected to the NETWORK connector. If the called number is often busy, you may also increase the number of call retries.

Major (event)

25 DP ALTERNATE CALL FAILED

The call attempts to the alternate dial-out number failed

If the number is not busy, check the modem connected to the NETWORK connector. If the called number is often busy, you may also increase the number of call retries.

Major (event)


Alarm Messages B-15



26 NETWORK LLB IO-A:B

Line loopback command received from the network (only for T1 ports)

Wait until the loopback condition is removed.

Minor (state)

27 NETWORK PLB IO-A:B

Payload loopback command received from the network (only for T1 ports)

Wait until the loopback condition is removed.

Minor (state)

28 DRIVER FAILURE IO-A:B

DXC technical failure (port line driver)

1. Check the transmit line pair. 2. Replace the I/O module installed

in the specified slot.

Major (state)

29 SIGNAL LOSS IO-A:B

Loss of port receive signal.

For the DFSTM-1 module, the loss of signal (LOS) state is entered when the received STM-1 signal level drops below the value at which an error ratio of 10-3 is predicted.

The LOS state is exited when 2 consecutive valid framing patterns are received, provided that during this time no new LOS condition has been detected


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 of the remote DXC.

Major (state)

30 EXCESSIVE BPV IO-A:B

The rate of bipolar violations in the port receive signal exceeds 1×10-6 during a measurement interval of 1000 seconds

Problem in network facilities Major (state)

31 AIS OCCURRED IO-A:B

Unframed “all ones” sequence is received in the specified port data stream

Problem at the remote equipment connected to the specified port

Major (state)

32 AIS RED ALM IO-A:B

Local loss of frame synchronization alarm on the specified port caused by AIS condition (only on T1 ports)


Major (state)


B-16 Alarm Messages

Table B-1 DXC Alarm Messages (Cont.)


33 AIS SYNC LOSS IO-A:B

Local loss of frame synchronization alarm on the specified port caused by AIS condition (only on E1 ports)


Major (state)

34 RED ALARM IO-A:B

Local loss of frame synchronization alarm on the specified port (only on 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.

Major (state)

35 LOCAL SYNC LOSS IO-A:B

Local loss of frame synchronization alarm on the specified port (only on E1 ports)


2. Check line and/or other communication equipment providing the link to the remote DXC.


Major (state)

36 LOCAL MF ALARM IO-A:B

Local loss of multiframe synchronization alarm on the specified port (only on E1 ports operating with G732S framing)



3. Replace the DXC I/O module installed in the specified slot.


Major (state)

37 REMOTE MF ALARM IO-A:B

Remote loss of multiframe synchronization alarm on the specified port (only on E1 ports with G732S framing)

Problem at the remote equipment Major (state)

38 YELLOW ALARM IO-A:B

Remote loss of frame synchronization alarm on the specified port (only on T1 ports)

Problem at the remote equipment Major (state)


Alarm Messages B-17



39 REMOTE SYNC LOSS IO-A:B

Remote loss of frame synchronization alarm on the specified port (only on E1 ports)

Problem at the remote equipment

40 FRAME SLIP IO-A:B

Frame slips are detected (not displayed during local loss of frame synchronization). Updated once per second

1. Incorrect selection of clock source.

2. Problem at far end (unstable clock source).

3. Replace the DXC-10A or the DCL.3 modules only if no problem has been detected in steps 1 and 2.

Minor (event)

41 BPV ERROR IO-A:B

Bipolar violations in the port receive signal. Updated once per second

Have the equipment connected to the specified port, and the connecting link, checked. If the remote equipment and the link is OK, the port may be defective

Minor (event)

42 EXCESSIVE ERR RATIO IO-A:B

The bit error rate of the port receive signal exceeds 1×10-3

Problem in network facilities. Major (state)

43 CRC-4 ERROR IO-A:B

CRC-4 errors detected in the E1 port receive signal. Updated once per second

Have the equipment connected to the specified port, and the connecting link, checked. If the remote equipment and the link is OK, the port may be defective.

Minor (event)

44 B.R.G FAILURE, IO-A:B

Hardware failure of the bit rate generator of port A:B

Replace the specified module. Major (state)

45 SFIFO SLIP IO-A:B

A slip event occurred in the SFIFO of port A:B

Check the selection of the clock source, and the cable connections.

46 MANAGEMENT PORT IS LOOPED

A test loopback has been activated on the management port, or the management port receives its own messages. Management is not possible while this condition is present

Check the location of the loop and request disconnection.

Major (state)

47 MANAGEMENT PORT IS DOWN

The DCL.3 module cannot communicate with the network management station. This may indicate incorrect set-up of the management port communication parameters, a disconnection along the communication path, or a hardware failure

1. Correct the parameters.

2. Check for disconnection.

3. Check for hardware failure.

Major (state)


B-18 Alarm Messages



48 DUPLICATE NAME IN THE NETWORK

Another RAD IP entity in the network uses the logical name assigned to the DXC

Check and correct the name Minor (state)

49 DUPLICATE MAC ADDRESS IN THE NETWORK

Another entity in the network used for SNMP management uses the MAC address configured on the SNMP agent of the DXC

Check and correct the MAC address Major (state)

50 MANAGEMENT NOT SUPPORTED IN SOFT REV, IO-A

The module software version is not supported by the management software

Check with your distributor or with RAD Technical Support department

Major (state)

51 DB CONTROL WAS TAKEN BY SNMP MMI

The DXC database is being edited from an ASCII terminal, while it is 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

Informative message - no action required

Minor (event)

52 DB CONTROL WAS TAKEN BY TERM MMI

The DXC database is being edited by an SNMP-based network 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

Informative message - no action required

Minor (event)

54 LOOP INBAND ON IO-A:B

A test loopback, controlled by inband activation codes, is activated on the specified module port

If the loopback is no longer required, use the CLR LOOP command to deactivate it

Minor (state)

55 CRC MULTIFRAME ALIGNMENT LOSS IO-A:B

Local loss of synchronization to the CRC-4 multiframe on the specified port (only on E1 ports operating with CRC-4 enabled)



3. Replace the DXC I/O module installed in the specified slot.


Major (state)


Alarm Messages B-19



59 60 61 62 63 64 65 66

DIM LINK 1 ERROR DIM LINK 2 ERROR DIM LINK 3 ERROR DIM LINK 4 ERROR DIM LINK 5 ERROR DIM LINK 6 ERROR DIM LINK 7 ERROR DIM LINK 8 ERROR

Errors have been detected in the data stream received by the DIM module through the link connected to the specified E1 or T1 port.

This message can appear only for DIM modules

1. Check for identical configuration of links on the DIM modules at the two DXC systems: link 1 at one end must be configured to connect to link 1 at the other end, etc.

2. Check for correct physical connections.

3. Check that good transmission quality on the various links.

Major (state)

67 LAN NOT CONNECTED

The 10BaseT port of a DIM module is not connected to an active Ethernet LAN

1. Check the connection between the DIM 10BaseT port and the LAN media, or hub port.

2. Check that the LAN equipment is operating normally, and at least one station is active on the LAN.

Minor (state)

68 I/O FLIP HAS OCCURRED

The active module of a redundancy pair operating in the Y-cable redundancy or combined line and hardware redundancy mode has been changed

Informative message. Check reason and act accordingly.

Minor (event)

69 I/O REDUNDANCY NOT SUPPORTED IN SW REV:IO-A

The software version installed on the specified I/O module does not support redundancy

Contact RAD Technical Support Department for upgrade information.

Major (event)

70 PORT FLIP HAS OCCURRED

The active port of a module operating in the single-slot redundancy mode has been changed

Information message. Check the reason and act accordingly.

Major (event)

71 HDSL TIMING OVERFLOW IO-A:B

The specified DHL module cannot recover the line clock because its frequency is not within the supported range

1. Check the equipment providing the E1 signal, and make sure its clock source is stable.

2. Replace the DHL module only if no problem has been detected in step 1.

Major (event)


B-20 Alarm Messages



72 HDSL STUFFING OVERFLOW IO-A:B

The stuffing mechanism of the DHL module cannot compensate for the frequency difference between the user’s port clock (E1 or T1) and the HDSL clock


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.

Major (event)

73 HDSL ELASTIC BUFFER OVERFLOW IO-A:B

The elastic buffer of the specified DHL module has overflown

1. Check the clock sources selected in the system, and make sure that they are derived from the same source.

2. Replace the DHL module.

Major (event)

74 HDSL LOOPS ARE INVERTED IO-A:B

The specified DHL module detected incorrect HDSL line connections

Check and correct the connections Minor (state)

75 HDSL FAR END ALARM IO-A:B

The specified DHL module reports that an alarm condition is reported 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.

Minor (event)

76 HDSL REMOTE LOOP IO-A:B

The specified DHL module reports that a remote loopback has been activated

Informative message - no action required. Deactivate the loopback when no longer required.

Major (state)

77 HDSL LINE 1 ELASTIC BUFFER ERROR IO-A:B

The specified DHL module reports that the elastic buffer serving HDSL line 1 is not supplying data

Major (event)

78 HDSL LINE 2 ELASTIC BUFFER ERROR IO-A:B

Same as above for HDSL line 2

1. Check HDSL line 1 connections. 2. Check the operation of the local

and remote DHL modules, and replace if necessary.

79 HDSL LINE 1 FAR END CRC ERROR IO-A:B

The specified DHL module reports that a CRC-6 error has been detected in the line 1 HDSL input signal at the remote end of the line

If the number of CRC-6 errors is significant (more than a few errors per hour), perform the following: 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.

Major (event)


Alarm Messages B-21



80 HDSL LINE 2 FAR END CRC ERROR IO-A:B


81 HDSL LINE 1 CRC ERROR IO-A:B

The specified DHL module reports that a CRC-6 error has been detected in the input signal of HDSL line 1

If the number of CRC-6 errors is significant (more than a few errors per hour), perform the following: 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.

Major (event)

82 HDSL LINE 2 CRC ERROR IO-A:B


83 HDSL LINE 1 SYNC LOSS IO-A:B

The specified DHL module reports loss of synchronization on HDSL line 1

1. Check the corresponding HDSL line.

2. Perform self-test on the two DHL modules and replace the DHL module that fails the self-test.

Major (state)

84 HDSL LINE 2 SYNC LOSS IO-A:B


85 HDSL LINE 1 SIGNAL LOSS IO-A:B

The specified DHL module reports loss of HDSL line 1 input signal

1. Check the corresponding HDSL line.

2. Perform self-test on the two DHL modules and replace the DHL module that fails the self-test.

Major (state)

86 HDSL LINE 2 SIGNAL LOSS IO-A:B


87 BUS CAPACITY EXCEEDS

The number of open timeslots exceeds the number of available links in the system

Decrease the number of open timeslots

Major (state)

88 PS-A FAN FAILURE

89 PS-B FAN FAILURE

The internal cooling fan of the corresponding power supply module does not operate

Check that the fan is indeed not operating. If not, replace the corresponding power supply module.

Major (state)

90 IDSL LB1 A loopback has been activated on the B1 channel of the specified D8U/D16U module port

If the loopback is no longer required, use the CLR LOOP command to deactivate it.

Minor (state)


B-22 Alarm Messages



91 IDSL LB2 A loopback has been activated on the B2 channel of the specified D8U/D16U module port


Minor (state)

92 IDSL LBBD A loopback has been activated on the B1, B2 and D channels of the specified D8U/D16U module port


Minor (state)

93 EXT UNIT CONFIG MISMATCH

The required configuration could not be downloaded to the ASMi-31 unit connected to the specified port of the D8U/D16U module

Change the ASMI-31 operation mode to permit configuration downloading.

Minor (state)

94 EXT UNIT NVRAM FAILED

The ASMi-31 unit connected to the specified port of the D8U/D16U module report failure of its non-volatile memory

Replace the ASMi-31. Major (state)

95 EXTERNAL UNIT NO INTERFACE

No user interface is installed on the ASMI-31 unit connected to the specified port of the D8U/D16U module

Install the required interface card in the ASMi-31, or replace the ASMi-31.

Major (state)

96 DTE INITIATED TEST ON EXT UNIT

A loopback (local or remote) has been activated on the remote unit managed by DHL/E1, DHL/E1/2W or D8U/D16U module

Deactivate the corresponding loopback.

Major (state)

97 EXT UNIT RTS OFF

RTS signal on the remote modem channel is in the OFF state

Connect the remote DTE equipment to the remote modem.

Minor (state)

101 STM LOSS OF POINTER

The loss of pointer (LOP) state is entered when N consecutive invalid 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.

Problem on the STM-1 link, or at the remote equipment unit.

Major (state)


Alarm Messages B-23



102 STM LOSS OF FRAME

The loss of frame (LOF) state is entered when an out-of-frame (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


Major (state)

103 STM OUT OF FRAME

The specified STM-1 port lost frame synchronization


Major (state)

104 STM SIGNAL LABEL LOSS OF LOCK

The DFSTM-1 module reports that it cannot detect the signal label


Major (state)

105 STM SIGNAL LABEL MISMATCH

The specified VC-4 or VC-12 port detects a signal label mismatch. This may indicate incorrect routing.of the corresponding VC.

This alarm condition may occur while a new route is being prepared

1. Check routing of corresponding signal

2. Problem on the STM-1 link, or at the remote equipment unit.

Major (state)

106 STM SIGNAL LABEL UNEQUIPPED

The specified VC-4 or VC-12 port receives an unequipped signal label

1. Check routing of the corresponding signal


Major (state)

107 STM SIGNAL DEGRADED ERROR

The specified port reports BER exceeding the preset signal degradation threshold


2. If the problem persists, replace the module

Major (state)

108 STM PATH TRACE ID MISMATCH

The specified VC-4 or VC-12 port detects a path trace mismatch. This may indicate incorrect routing.of the corresponding VC.

This alarm condition may occur while a new route is being prepared

1. Check routing of the VC-4 signal


Major (state)

109 STM PATH TRACE UNEQUIPPED

The DFSTM-1 module reports that it receives unequipped path trace

1. Check routing of the VC-4 signal


Major (state)


B-24 Alarm Messages



110 STM HW FAIL The DFSTM-1 module reports technical failure

Replace the DFSTM-1 module Major (state)

111 STM CRITICAL ALARM

The corresponding internal port reports that a critical alarm condition has occurred on an upper layer

1. Reset the DFSTM-1 module.

2. Replace the DFSTM-1 module

Major (state)

112 INPUT ALARM IS ACTIVE

The fan tray unit failed. Replace the fan tray. Major (state)

113 SNMP ALARM TRAP EXCEEDS

The number of SNMP alarm traps is too high for the proper device operation; new alarm traps will not be queued.

Once all the queued alarm traps are sent, the alarm disappears.

Major (state)

114 SHDSL SYNC LOSS LINE_A

Loss of SHDSL synchronization on the specified SHDSL line

Connect the SHDSL line to the D8SL port.

Major (state)

115 SHDSL LOSW FAILURE LINE-A

Loss of SHDSL synchronization word event on the specified SHDSL line

Check the SHDSL line. Major (state)

116 SHDSL CRC6 ERROR

CRC error event on the specified SHDSL line

Check the SHDSL line. Major (state)

117 SHDSL SNR MARGIN ERROR

SNR margin event on the specified SHDSL line

Set higher value of SNR_MARGIN _THRESHOLD parameter, or improve the line quality.

Major (state)

118 SHDSL LOOP ATTENUATION ERROR

High attenuation on the SHDSL line Set higher value of ATTENUATION_THRESHOLD parameter

Major (state)

119 SHDSL NO MANAGEMENT

The SHDSL inband management channel (eoc) is not operational


Major (state)

120 SHDSL TEST ACTIVE BY REMOTE UNIT

A test has been activated on the specified SHDSL line by the remote unit

Deactivate the test from the remote unit or wait until it is ended.

Minor (state)

121 REM LOSS OF SIGNAL

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports loss of signal

Check the remote unit. Minor (state)

122 REM BPV ERROR The remote ASMi-52/E1 unit connected to the specified SHDSL port reports bipolar violation error

Check the remote unit. Minor (event)

123 REM FRAME SLIP The remote ASMi-52/E1 unit connected to the specified SHDSL port reports frame slip



Alarm Messages B-25



124 REM EXCESSIVE BPV

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports high rate of bipolar violation errors


125 REM EXCESSIVE ERROR

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports excessive bit error rate (higher than 10-3


126 REM AIS OCCURED

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports reception of AIS


127 REM CRC4 ERROR

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports CRC-4 error event


128 REM AIS SYNC LOSS

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports AIS and loss of frame alignment


129 REM REMOTE SYNC LOSS

The remote ASMi-52/E1 unit connected to the specified SHDSL port reports loss of frame alignment to the user’s E1 signal


130 REM LOSW FAILURE LINE-A

The remote ASMi-52 unit connected to the specified SHDSL port reports loss of SHDSL synchronization

Check the SHDSL line. Minor (state)

131 REM SHDSL CRC6 ERROR

The remote ASMi-52 unit connected to the specified SHDSL port reports a SHDSL CRC error event

Check the SHDSL line. Minor (event)

132 REM SHDSL SNR MARGIN ERROR

The remote ASMi-52 unit connected to the specified SHDSL port reports low SHDSL SNR margin event.

Set higher value of REM_ SNR_ MARGIN_THRESHOLD parameter, or improve the line quality.

Minor (event)

133 REM SHDSL LOOP ATTENUATION ERROR

The remote ASMi-52 unit connected to the specified SHDSL port reports high SHDSL line attenuation

Set higher value of REM_ATTENUATION_THRESHOLD parameter

Minor (state)

134 REM LLB FROM DTE

The remote ASMi-52 unit connected to the specified SHDSL port reports the reception of a local loopback request from the user’s equipment

Deactivate the LLB test on the remote unit.

Minor (state)


B-26 Alarm Messages



135 REM RLB FROM DTE

The remote ASMi-52 unit connected to the specified SHDSL port reports the reception of a remote loopback request from the user’s equipment

Deactivate the RLB test on the remote unit.

Minor (state)

136 REM LAN NOT CONNECTED

The remote ASMi-52 unit connected to the specified SHDSL port reports that no LAN is connected to its Ethernet port

Connect the LAN to the Ethernet port of the remote unit.

Minor (state)

137 REM DATA LINE RATE MISMATCH

The remote ASMi-52 unit connected to the specified SHDSL port reports that its data rate does not match the number of timeslots open on the D8SL port to which it is connected

Set the MAX_BW parameter to match the number of open timeslots.

Minor (state)

138 REM CONFIG CHANGED

The remote ASMi-52 unit connected to the specified SHDSL port reports change of configuration

The ASMi-52 parameters should not be modified by the modem supervision terminal.

Minor (event)

139 REM ILLEGAL EXT CLOCK

The remote ASMi-52 unit connected to the specified SHDSL port reports incorrect selection of its nodal clock source

Set the ASMi-52 nodal clock to the correct value.

Minor (state)

140 CLOCK IS INTERNAL

The DFSTM-1 module switched to the internal clock because of one of the following conditions:

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

1. Set the clock to internal.

2. Check the remote unit.

3. Check the STM-1 link.

Minor (state)

141 PROPRIETARY PROTOCOL FAILED

The SHDSL inband proprietary protocol management channel (eoc) is not operational


Major (state)

SNMP Environment C-1

Appendix C SNMP Management

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.

C.2 SNMP Environment

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).

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.

Note

Appendix C SNMP Management DXC-8R/10A/30/30E Installation and Operation Manual

C-2 SNMP Environment

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.

The Management Information Base

The management information base (MIB) includes a collection of managed objects. A managed object is defined as a parameter that can be managed, such as a performance statistics value.

The MIB includes the definitions of relevant managed objects. Various MIB's can be defined for various management purposes, types of equipment, etc.

An object's definition includes the range of values and the “access” rights: Read-only Object value can be read, but cannot be set. Read-write Object value can be read or set. Write-only Object value can be set, but cannot be read. Not accessible Object cannot be read, nor set.

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.

DXC-8R/10A/30/30E Installation and Operation Manual Appendix C SNMP Management

SNMP Environment C-3

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.

MIB's Supported by the DXC SNMP Agent

The interpretation of the relevant MIB's is a function of the SNMP agent of each managed entity. The general MIB's supported by the DXC SNMP agent are as follows:

• RFC 1213 (standard MIB-II).

• RFC 1406 (standard E1/T1 MIB).

• RFC 1407 (standard E3/T3 MIB).

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

Enterprise-specific MIB's supported by RAD equipment, including those for the DXC, are available in ASN.1 format from the RAD Technical Support Department.

Management Domains Under SNMP In principle, SNMP enables any management station that knows the MIB's supported by a device to perform all the management operations available on that device. However, this is not desirable in practical situations, so it is necessary to provide a means to delimit management domains.

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.


C-4 IP Environment

Access Restriction Using SNMP Communities

In general, SNMP agents support two types of access rights:

• Read-only: the SNMP agent accepts and processes only SNMP getRequest and getNextRequest commands from management stations which have the same read-only community name.

• Read-write: the SNMP agent accepts and processes all the SNMP commands received from a management station with the same write 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).

DXC System Communities

The SNMP agents of DXC systems are programmed to recognize the following community types:

Read SNMP community that has read-only authorization, i.e., the SNMP agent will accept only getRequest and getNextRequest commands from management stations using that community.

Write SNMP community that has read-write authorization, i.e., the SNMP agent will also accept setRequest commands from management stations using that community.

Trap SNMP community which the SNMP agent will send within trap messages.

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.


IP Environment C-5

An IP address is logically divided into two main portions:

• Network Portion. The network portion is assigned by the Internet Assigned Numbers Authority (IANA). There are five IP address classes: A, B, C, D, and E. However, only the classes A, B and C are used for IP addressing. Consult your network manager with respect to the class of IP addresses used on your network.

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

Class A Network Portion Host Portion

Class B Network Portion Host Portion

Class C Network Portion Host Portion

The class of each IP address can be determined from its leftmost byte, in accordance with the following chart:

Address Class First Byte Address Range

Class A 0 through 127 0.H.H.H through 127.H.H.H

Class B 128 through 191 128.N.H.H through 191.N.H.H

Class C 192 through 223 192.N.N.H through 223.N.N.H

N – indicates bytes that are part of the network portion H – indicates bytes that are part of the host portion

• Host Portion. The host portion is used to identify an individual host connected to the network. The host identifier is assigned by the using organization, in accordance with its specific needs.

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.

Net and Subnet Masks Net and subnet masks are used to help filter the relevant traffic more efficiently: the function of the net and subnet mask is to specify how many of the IP address bits are actually used for the net identifier and for the subnet number.

The mask is a 32-bit word that includes “ones” in the positions used for net and subnet identifications, followed by “zeros” up to the end of the IP address. For example, the subnet mask corresponding to the Class C IP address 194.227.31.67 is 255.255.255.000.

Note


C-6 Handling of Management Traffic

Recommendations for Selection of IP Addresses When the DXC SNMP agent and its management station are connected to the same network, the network identifier part of the IP address assigned to the SNMP agent must be identical to the network identifier part of the IP address of the management station.

However, the agent and the DXC SNMP management station can also be on different IP networks. In this case, each one will be assigned IP addresses according to its IP network.

Automatic Routing of IP Traffic The SNMP agent of the DXC system includes an IP router function, that is used to route management messages automatically.

The IP router function operates both on the inband, as well as on the out-of-band traffic, depending on the communication methods enabled by the user.

C.4 Handling of Management Traffic

Handling of Out-of-Band Communication Out-of-band communication is performed via the management ports of the DCL.3 module. The communication method and protocol depends on the specific DCL.3 version.

DCL.3 Modules with Serial Interfaces When using out-of-band communication through a port of a DCL.3 module with serial interfaces, the IP router must know whether the serial port connectors, CONTROL and/or MNG, are to be used for management.

This information is provided during the configuration of the supervisory ports, using the DEF SP, respectively DEF NP, command:

• A port which is connected to the network management station, either directly or through a router, is defined as the NMS port.

• A port which is connected to a serial supervisory port of another equipment unit is defined as an AGENT port.

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.

Note


Handling of Management Traffic C-7

DCL.3 Modules with Ethernet Interfaces

When using out-of-band communication through the DCL.3 Ethernet port, the connection to the management station is generally made through the Ethernet port. For this port, the internal IP router of the DXC uses the IP protocol to transfer management traffic, and the RAD proprietary and/or RIP2 protocol for routing the management traffic. Moreover, in this case the DCL.3 module also serves as a proxy ARP agent that enables a management station connected to its Ethernet port to manage remote equipment, using inband communication.

The additional CONTROL port of the DCL.3 module can be used in two ways, in accordance with the configuration selected by the user:

• Typically, the serial CONTROL port is configured to serve as an access port for supervision terminals, for performing local configuration and maintenance activities.

• Alternately, the CONTROL port can be configured to serve as an extension port for the management link, by selecting the SLIP AGENT or PPP AGENT mode. In this case, the CONTROL port can be connected to the serial supervisory port of another equipment (e.g., an FCD unit, etc.), thereby enabling the management station to manage the additional equipment.

Handling of Inband Communication When using inband communication, the IP router can receive the management traffic through any link (E1, T1, DIM, DHL, E3, or T3). Different protocols and routing methods can be configured for each link.

The management traffic can also use the internal E1 ports of fractional STM-1 modules.

Inband Communication Ports and Protocols

When using inband communication, the user can select the link bandwidth allocated to management, and the transmission and routing management protocols:

• Management traffic carried within the E1 or T1 frame overhead. This communication mode uses a RAD proprietary protocol, which requires a small fraction of the link bandwidth:

For E1 links, the management traffic is carried by means of the national bit Sa4 in time slot 0 (corresponding to a management data rate of 4 kbps).

For T1 links, the management traffic is carried by the FDL channel (note that this requires using ESF framing on the link carrying the management traffic). The management data rate is 2 kbps.

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


C-8 Handling of Management Traffic

PPP, HDLC encapsulation, and frame relay encapsulation in accordance with RFC 1490; if required, the RIP2 routing protocol can also be used.

• Management traffic carried by the inband management data link of T3 links using the parity C-bit application mode. This communication mode supports the RAD proprietary protocol, and if required the RIP2 routing protocol.

• Management traffic carried by the inband management data link of DIM modules. This communication mode supports only the RAD proprietary protocol.

Inband Management Traffic Routing

The IP router function uses the RAD proprietary routing protocol whenever it operates in a network environment consisting of RAD products.

In addition, the IP router can be configured by the user to use standard protocols (PPP, frame relay) and also RIP2, when connecting directly to a router.

• The RAD proprietary routing protocol is used with the time slot 0 (or FDL) option, the dedicated time slot option, the inband management data link of T3 links using the C-bit parity application mode, and with the inband management option of DIM modules.

• The RIP2 protocol is available with the dedicated time slot, PPP, or frame relay options. In addition, it is also available for T3 links using the C-bit parity application mode.

When the IP router function is configured to use the RAD proprietary protocol, it collects information on the other SNMP agents by exchanging routing information (including the contents of each router's routing table), with its neighbors.

This automatic learning capability enables using any network topology, including topologies with closed loops.

Note that an SNMP agent accepts routing information messages only through the port defined as AGENT port, or through inband management.

To enable the routing of management traffic by standard routers, the IP router function can be configured to use the standard RIP2 protocol. In this case, the DXC SNMP agent does not learn IP addresses through this port.

• When the management traffic is carried in a dedicated time slot, it is also possible to use frame relay encapsulation in accordance with RFC 1490 (and if required, the RIP2 routing protocol). This enables using frame relay routers to carry the management traffic to the managed DXC.

• Frame relay encapsulation is used as follows:

In the transmit direction, the SNMP agent encapsulates the management messages in frames with a predetermined DLCI (always DLCI 100), and sends them at the selected rate through the selected main link time slot.

In the receive direction, the SNMP agent monitors the specified time slot, analyzes packets received with DLCI 100, and analyzes the received data to detect management messages (any such messages are then processed as usual).


SNMP Traps C-9

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.

Preventing Management Access to the Other Network Equipment

By default, the internal IP router function of the DXC SNMP agent will route management traffic received through any link configured for management access, to all the other links and ports that are also configured for management access.

There are certain applications in which this is not desirable: a particular configuration of this type is a link that ends in equipment managed by a “foreign” management station, which should not be able to access the other equipment in the network.

To prevent that management station from accessing other equipment through the IP router function of the DXC SNMP agent, the user can configure that link for operation using a dedicated time slot for management traffic, but without enabling any routing protocol (i.e., neither the RAD proprietary, not the RIP2 routing protocol).

C.5 SNMP Traps

The DXC SNMP agent supports the standard MIB-II traps.


C-10 SNMP Traps

Cold (Local) Installation Procedure D-1

Appendix D Installing New Software Releases

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.

Appendix D Installing New Software Releases DXC-8R/10A/30/30E Installation and Operation Manual

D-2 Cold (Local) Installation Procedure

D.2 Cold (Local) Installation Procedure

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’’.

6. The successful completion of the process is indicated by the message: FLASH WRITE SUCCESS, RESET TARGET.

7. Turn the DXC off and then back on, and wait until all the DCL.3 indicators turn off (if an alarm is present in the DXC, the ALM indicator may light).

If a problem occurs during downloading, perform the whole process again.

DXC-8R/10A/30/30E Installation and Operation Manual Appendix D Installing New Software Releases

Warm Installation (Upgrading) Procedure D-3

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.

D.3 Warm Installation (Upgrading) Procedure

If you manage the DXC using the RADview Windows-based network management station, or another network management station running SNMP client software in a Windows environment, you can upgrade the DCL.3 software in running time (there is no need to turn the DXC off during the whole process).

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.

Appendix D Installing New Software Releases DXC-8R/10A/30/30E Installation and Operation Manual

D-4 Warm Installation (Upgrading) Procedure

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.

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.

Resetting the DCL.3 in a Redundant System 1. Activate DEF SYS and set REDUNDANCY to YES.

2. Activate DEF DCL FLIP to make sure that ACTIVE_DCL is set to AUTO.

3. Activate UPD DB.

4. Perform the reset.

The DXC is reset safely, with minimum interruptions.

In a system with DCL.3 redundancy, remember to download the new software version to both modules.

Note

Notes

E1 (CEPT) Environment E-1

Appendix E Operating Environment

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.

E.2 E1 (CEPT) Environment

The E1 line interfaces of the DXC system comply with all the applicable requirements of the ITU-T Rec. G.703, G.704, G.732, G.736 and G.823.

E1 (CEPT) Signal Structure The E1 line operates at a nominal rate of 2.048 Mbps. The data transferred over the E1 line is organized in frames. Each E1 frame includes 256 bits. The structure of the E1 frame is shown in Figure E-1.

Time Slot 0 Time Slot 16 Time Slots 1-15, 17-31

FAS MAS

a. Even Frames (0,2,4-14)

b. Odd Frames (1,3,5-15)

a. Frame 0

b. Frames 1-15Channel Data

1 0 0 1 1 0 1 1

I 1 A N N N N N

0 0 0 0 X Y X X

A B C D A B C D 1 2 3 4 5 6 7 8

32 Time Slots/Frame

8 Bits perTime Slot

16 Frames/Multiframe

TS0

TS1

TS2

TS3

TS4

TS5

TS6

TS7

TS8

TS9

TS10

TS11

TS12

TS13

TS14

TS15

TS16

TS17

TS18

TS19

TS20

TS21

TS22

TS23

TS24

TS25

TS26

TS27

TS28

TS29

TS30

TS31

FR0

FR1

FR2

FR3

FR4

FR5

FR6

FR7

FR8

FR9

FR10

FR11

FR12

FR13

FR14

FR15

Notes

ABCDXYMAS

INAFAS

International BitNational Bits (Sa4 through Sa8)Alarm Indication Signal (Loss of Frame Alignment - Red Alarm)Frame Alignment Signal, occupies alternate(but not necessarily even) frames

ABCD Signaling BitsExtra BitLoss of Multiframe AlignmentMultiframe Alignment Signal

Figure E-1. E1 (CEPT) Frame Structure

Appendix E Operating Environment DXC-8R/10A/30/30E Installation and Operation Manual

E-2 E1 (CEPT) Environment

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

DXC-8R/10A/30/30E Installation and Operation Manual Appendix E Operating Environment

E1 (CEPT) Environment E-3

channel-associated signaling (CAS). CAS is typically used on links that transfer voice channels. In this mode, the maximum number of timeslots available for payload is 30 (maximum data rate of 1920 kbps).

The 256S multiframe requires a special multiframe alignment sequence (MAS), which is carried in timeslot 16 (see Figure E-1), together with the Y bit, which indicates loss of multiframe alignment. As shown in Figure E-1, four signaling bits, designated A, B, C, and D, are available for each channel, thereby enabling end-to-end transmission of four signaling states. Each frame in the multiframe carries the signaling information of two channels.

E1 Line Statistics Using CRC-4 Error Detection The DXC system supports the CRC-4 function in accordance with ITU-T Rec. G.704. The CRC-4 function is used to detect errors in the received data, and therefore can be used to evaluate data transmission quality over E1 links. To enable error detection, additional information must be provided to the receiving equipment. The additional information is transmitted to the receiving equipment by using a multiframe structure called CRC-4 multiframes. A CRC-4 multiframe is an arbitrary group of 16 frames. This group is not related in any way to the 256S 16-frame multiframe structures explained above. •

• A CRC-4 multiframe always starts with an even frame (a frame that carries the frame alignment signal). The CRC-4 multiframe structure is identified by a six-bit CRC-4 multiframe alignment signal, which is multiplexed into bit 1 of timeslot 0 of each odd-numbered (1, 3, 5, etc.) frame of the CRC-4 multiframe (up to frame 11 of the CRC-4 multiframe).

• Each CRC-4 multiframe is divided into two submultiframes of 8 frames (2048 bits) each. The detection of errors is achieved by calculating a four-bit checksum on each 2048-bit block (submultiframe). The four checksum bits calculated on a given submultiframe are multiplexed, bit by bit, in bit 1 of timeslot 0 of each even-numbered frame of the next submultiframe.

• At the receiving end, the checksum is calculated again on each submultiframe and then compared against the original checksum (sent by the transmitting end in the next submultiframe). The results are reported by two bits multiplexed in bit 1 of timeslot 0 in frames 13, 15 of the CRC-4 multiframe, respectively. Errors are counted and used to prepare statistic data on transmission performance.

E1 (CEPT) Line Signal The basic E1 line signal is coded using the High-Density Bipolar 3 (HDB3) coding rules. The HDB3 coding format is an improvement of the alternate mark inversion (AMI) code. 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.


E-4 E1 (CEPT) Environment

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.

E1 (CEPT) Line Alarm Conditions Excessive bit error rate. The bit error rate is measured on the frame alignment signal. The alarm threshold is an error rate higher than 10

-3 that persists for 4 to 5

seconds. The alarm condition is canceled when the error rate decreases below 10-4

for 4 to 5 consecutive seconds. Loss of frame alignment (also called loss of synchronization). This condition is declared when too many errors are detected in the frame alignment signal (FAS), e.g., when 3 or 4 FAS errors are detected in the last 5 frames. Loss of frame alignment is cleared after no FAS errors are detected in two consecutive frames. The loss of frame alignment is reported by means of the A bit (see Figure E-1). Loss of multiframe alignment (applicable only when 256S multiframes are used). This condition is declared when too many errors are detected in the multiframe alignment signal (MAS), as for loss of frame alignment. The loss of multiframe alignment is reported by means of the Y bit (see Figure E-1). Alarm indication signal (AIS). The AIS signal is an unframed “all-ones” signal, and is used to maintain line signal synchronization in case of loss of input signal, e.g., because an alarm condition occurred in the equipment that supplies the line signal. Note that the equipment receiving an AIS signal loses frame synchronization.

64 kbps Channel Characteristics Timeslots 1 through 31 carried by the E1 frame are available to the user (possibly with the above-mentioned exception of timeslot 16, when this timeslot is used for system purposes). The timeslots may be used as transparent data carriers for channelized data (n×64 kbps), or for audio (voice) transmission. A widely used method for voice digitizing is pulse-coded modulation (PCM). To improve transmission quality, a non-linear encoding law is used. ITU-T Rec. G.711 recommends that in E1 systems the non-linear encoding law designated the A-law be used. The signaling associated with voice channels is multiplexed within timeslot 16. Therefore, G.732S framing must be used when channel-associated signaling (CAS) is required.


T1 Environment E-5

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.

FR1

FR2

FR12

FR11

CH13

1 2 3 4 5 6 7

FtorFs

CH1

CH2

CH24

8AB

FR7

Byte Organization 8 Bits/Channel(D4 Frame - See NOTE)

Frame 24 Channels/FrameOrganization Frame = 193 Bits

MultiframeOrganization

NOTE:In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24

MultiframeSF (D4) 12 Frames ESF: 24 Frames

Other FramesFrame 6Frame 12

Bit B ConveysSignalingInformation

Figure E-2. T1 Frame Structure

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.

The SF format provides limited supervision capabilities such as end-to-end reporting of local loss-of-signal (yellow alarm).

The ESF format provides much improved supervision capabilities, and allows better utilization of the 8 kbps framing timeslots. The major advantage of the ESF format is that it supports on-line link performance monitoring (by means of a 2 kbps Cyclic Redundancy Check (CRC) channel), and in addition provides a 4 kbps end-to-end supervision and control data link.


E-6 T1 Environment

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.

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.

Note


T1 Environment E-7

In accordance with AT&T TR-62411, a system automatically recovers synchronization when there has been a period of 10 to 20 consecutive seconds free of the loss of sync condition. Since in many system applications this is a overly conservative specification, the DXC system offers faster frame synchronization algorithms, which allow the user to select a “fast” mode. In the “fast” mode, the time necessary to declare synchronization is reduced to approximately one second free of the loss of sync condition.

• Yellow Alarm. A yellow alarm is sent from the remote unit to inform the local unit that a red alarm exists at the remote end.

• Alarm indication signal (AIS). The AIS signal is an unframed “all-ones” signal, and is used to maintain line signal synchronization when an alarm condition occurs in the equipment that supplies the line signal.

64 kbps Channel Characteristics Timeslots 1 through 24 of the T1 frame are available to the user. The timeslots may be used as transparent data carriers for fractional T1 data, or for audio (voice) transmission. When voice digitizing is made by PCM, ITU-T Rec. G.711 recommends that in T1 systems the non-linear encoding law designated the µ-law be used.

To allow transparent transfer of channel signals between E1 trunks and T1 trunks, the DXC system allows the user to select on a channel-by-channel basis whether a conversion from A-law to µ-law is to be performed. This selection is made by defining the channel type: voice (with conversion) or data (no conversion).

The selected signaling transfer mode (common channel signaling – CCS, or channel associated signaling – CAS) applies to all the channels. The selection of a signaling transfer mode affects the transfer of the channel bits, a characteristic of importance in applications in which a trunk carries data channels together with voice channels:

• In the CCS mode, the bits are transparently transferred.

• In the CAS (robbed bit signaling) mode, the signaling information overwrites the least significant bit of the channel once in every six frames.

Thus, when signaling must be transferred for data channels, it is necessary to implement the system using CCS (this requires reserving timeslot 16 for the transfer of the CCS data).


E-8 E3 Environment

E.4 DXC Systems and ITU-T Rec. G.802

The ITU-T Rec. G.802 recommendation deals with the interworking between networks based on different digital hierarchies and speech encoding laws. Within this framework, the recommendation deals with the transport of a T1 signal within a framed E1 signal, and recommends that the T1 F-bit be transferred end to end.

When the T1 signal is framed, e.g., when it is a multiplexed signal, the DXC system uses its 32-timeslot handling capability to provide a separate user-controlled facility for the transfer of the F bit. For this purpose, the DXC system internally handles the F bit in an additional timeslot (that requires a total of 25 timeslots for carrying the T1 signal over an E1 link). Bit 1 of the timeslot carries the F bit of the T1 frame, and the other bits of that timeslot are not used. The user can then program the DXC system to connect the timeslot carrying the F bit to any desired E1 timeslot.

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.).


E3 Environment E-9

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.

NotesFASANCj1, Cj2, Cj3

Frame Alignment SignalAlarm Indicator to Remote EquipmentNational BitJustification Control Bits

D/J Data Bits, Available for Justification

1536

4 bits(D/J)

FAS (10 bits)

4 bits 376 bits

1152

1153

1156

1157

1160

1161

C13

C23

C33

C43

C12

C22

C32

C42

C11

C12

C13

C14A N

1

T1 T2 T3 T4 T1

772

773

768

769

384

385

Cj3Tributary Bits

Tributary Bits(380 bits) Cj2


Tributary Bits(372 bits)

388

38910 11 12 13

848

4 bits(D/J)

FAS (10 bits)

4 bits 204 bits

636

637

640

641

644

645

C13

C23

C33

C43

C12

C22

C32

C42

C11

C12

C13

C14A N

1

E1-1

E1-2

E1-3

E1-4

E1-1

428

429

424

425

212

213

Cj3Tributary Bits



Tributary Bits(200 bits)

216

21710 11 12 13

Typical Tributary Data Stream

Overhead

Overhead

4 bits4 bits

4 bits4 bits

Figure E-3. E3 Frame Structure

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


E-10 T3 Environment

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.

The justification is independently performed for each tributary, after deciding which word (000 or 111) is carried by the justification control bits of that tributary.

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.

E3 Line Alarm Conditions • Loss of frame alignment (also called loss of synchronization). This condition is

declared when too many errors are detected in the frame alignment signal (FAS), e.g., when 4 consecutive FAS errors are detected. Loss of frame alignment is cleared after no FAS errors are detected in two consecutive frames. The loss of frame alignment is reported by means of the A bit (see Figure E-3).

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

M-Frame(4760 bits)

. . . . . . . . . . . . . . .

679 bitsX1 679 bitsX2 679 bitsP1 679 bitsP2 679 bitsM1 679 bitsM2 679 bitsM3

Figure E-4. T3 Frame Structure


T3 Environment E-11

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.

= Status= Parity= M-Frame Alignment= Subframe Alignment= Control

XnPnMnFnCn,m

Legend

Block 1 Block 8 . . . . . . . . . . . . . . .

Stuff Blocks

M Subframe

1

2

3

4

5

6

7

Info(84 bits)X1 Info

(84 bits)F1 Info(84 bits)C1,1

Info(84 bits)F0 Info

(84 bits)C1,2Info


Info(84 bits)F1

Info(84 bits)X2 Info



(84 bits)C2,2Info


Info(84 bits)F1

Info(84 bits)P1 Info



(84 bits)C3,2Info


Info(84 bits)F1

Info(84 bits)P2 Info



(84 bits)C4,2Info


Info(84 bits)F1

Info(84 bits)M0 Info



(84 bits)C5,2Info


Info(84 bits)F1




(84 bits)C6,2Info


Info(84 bits)F1




(84 bits)C7,2Info


Info(84 bits)F1

Figure E-5. M-Subframe Organization in DS3 Signal

An M-subframe consists of eight 85-bit blocks. The blocks designated 1 through 7 always have the same structure, whereas the structure of block 8 changes in accordance with the M-subframe.

Each block comprises one overhead (OH) bit, followed by 84 information bits, resulting in a total of 56 overhead bits per frame. The functions of the overhead bits are as follows:

• M-Frame Alignment Channel. The M-frame alignment channel signal (bits M1=0, M2=1, and M3=0) is used to identify each of the seven M-subframes.

• M-Subframe Alignment Channel. The M-subframe alignment channel signal (bits F1=1, F2=0, F3=0, and F4=1) is used to identify the frame overhead bit positions.

• P-Bit Channel. The P-bit channel (bits P1 and P2) is used for performance monitoring.

• X-Bit Channel. The X-bit channel (bits X1 and X2) is used as an alarm channel.

• C-Bit Channel. The C-bit channel (bits C1, C2, and C3) are reserved for application-specific uses. The DXC system supports two applications, in accordance with ANSI T1.107a: M13 (also called SYNTRAN) and C-bit parity.


E-12 T3 Environment

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.

F1 S1 D2 D3 D4 D5 D6 D7 D1 D6 D7

F1 D1 S2 D3 D4 D5 D6 D7 D1 D6 D7

F1 D1 D2 S3 D4 D5 D6 D7 D1 D6 D7

F1 D1 D2 D3 S4 D5 D6 D7 D1 D6 D7

F1 D1 D2 D3 D4 S5 D6 D7 D1 D6 D7

F1 D1 D2 D3 D4 D5 S6 D7 D1 D6 D7

F1 D1 D2 D3 D4 D5 D6 S7 D1 D6 D7

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

M Subframe 1

M Subframe 2

M Subframe 3

M Subframe 4

M Subframe 5

M Subframe 6

M Subframe 7

Block 8

= Xn, Pn, M1, M0, F1, F0, or Cn,m

= Information Bit from DS2n : n = 1,2....7= Stuff Opportunity for DS2n : n =1,2....7

OHDnSn

Blocks 1 to 7 inAll M Subframes OH D1 D2 D3 D4 D5 D6 D7 D1 D6 D7

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

Figure E-6. Block Organization in DS3 Signal


T3 Environment E-13

Structure of Standard DS2 Tributary Data

Figure E-7 shows the structure of the DS2 frames, which are carried as payload in the DS3 signal. The DS3 signal carries seven DS2 streams, where each DS2 stream, having a nominal data rate of 6.312 Mbps, carries four DS1 (1.544 Mbps) signals. The multiplexing method is positive justification.

This arrangement ensures compatibility with the DSX-3 cross-connect requirements of ANSI T1.107.

The DS2 signal is organized using principles similar to those used for the DS3 signal:

• The DS2 frame (also called M-frame) contains 1176 bits.

• The 1176 bits are organized as four 294-bit M subframes.

• Each M subframe comprises six 49-bit blocks.

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.

Block 1 Block 6 . . . . . . . . . . . . . . . . . . . . .

293 bitsM3

M Subframe 1 M Subframe 4

M-Frame(1176 bits)

. . . . . . . . .

293 bitsX293 bitsM1 293 bitsM2


(48 bits)C1 Info(48 bits)F1 Info

(48 bits)C2 Info(48 bits)C3 Info

(48 bits)F2




(48 bits)F2




(48 bits)F2

Info(48 bits)X Info



(48 bits)F2

Stuff Blocks

M Subframe

1

2

3

4

= Status= M-Frame Alignment= Subframe Alignment= Control

XMnFnC

Legend

Figure E-7. Structure of Standard DS2 Tributary Data


E-14 T3 Environment

Structure of 6.312 Mbps G.747 Tributary Data Stream

The 6.312 Mbps data rate is also sufficient for carrying three E1 (2.048 Mbps) tributaries, instead of the four T1 (1.544 Mbps) tributaries carried by a standard DS2 tributary. The multiplexing method and the resulting 6.312 Mbps signal structure are defined ITU-T Rec. G.747.

Figure E-7 shows the structure of the 6.312 Mbps G.747 frames.

The 6.312 Mbps G.747 signal is organized using principles similar to those used for the standard DS2 signal:

• The signal frame contains 840 bits.

• The 840 bits are organized as five 168-bit subframes.

• Each subframe comprising several overhead bits, and tributary bits.

The overhead bits include frame alignment, alarm and error detection bits, and justification control channels, one for each tributary.

Subframe 1 Subframe 5

Frame(840 bits)

. . . . . . . . . . . . . .

FA Frame AlignmentA Alarm Indication Bit to Remote EquipmentP Even Parity Bit for Tributary DataR Reserved BitJC1JC2 Justification Control Bits for Corresponding TributaryJC3

Legend

Tributary BitsA P R

1 4 168

Tributary Bits

1 16810

FA

Tributary Bits

1 4 168

JC1

Tributary Bits

1 4 168

JC2

Tributary Bits

1 4 168

JC3

Subframe

1

2

3

4

5

Figure E-8. Structure of 6.312 Mbps G.747 Tributary Data Stream


T3 Environment E-15

Synchronous DS3 M13 Multiplex Application This section describes the synchronous DS3 M13 multiplex application (SYNTRAN), where 28 DS1 channels are multiplexed directly to the DS3 level.

M13 Multiplex Signal Characteristics

The M13 multiplex signal preserves the M, F, P, and X bits for compatibility with the DSX-3 cross-connect requirements of ANSI T1.107 (as well as for network elements and transmission facilities which recognize these overhead bits). The M13 application performs multiplexing of signals having a common timing source, and therefore stuffing is not necessary. As a result, the C-bit (C1, C2, and C3) positions in the M-subframes are not needed for stuff indication and are available for network operations and maintenance functions.

The payload bits are organized into 588 eight-bit octets (timeslots), which are used to directly multiplex 28 DS1 signals. An additional subframe is embedded inside the asynchronous DS3 frame structure to define a synchronous superframe of 699 M-frames that contains 595 synchronous subframes.

SYNTRAN Maintenance Features • DS3 Signal Performance Monitoring. An error detection cyclical redundancy

check code (CRC-9) is used to monitor SYNTRAN signal performance via a 9-bit code.

• FEBE Indicator. Bit C2 in the first M-frame in a triad is designated as a Far End Block Error (FEBE) bit. It is used to indicate CRC-9 errors detected at the receive side (by returning the FEBE bit to the transmitting side).

• Alarm Channel. Bit C3 of the M-frame in a triad designated as an alarm and control channel.

• Loopbacks. The alarm and control channel also supports the transmission of code words to activate and deactivate the line loopback.

Asynchronous DS3 C-Bit Parity Application This section describes the asynchronous DS3 C-bit parity signal structure, that is used to multiplex asynchronous 28 DS1 signals to the DS3 signal level.

The asynchronous DS3 C-bit parity signal preserves the M, F, P, X, and C-bits, to assure compatibility with DS3 equipment and transmission facilities.

C-Bit Maintenance Features • X-Bit Channel. The X-bit channel is used to transmit failure conditions from the

far end to the near end of the system in the same manner as the yellow alarm.

• Far-End Alarm and Control Signals. The third C-bit in M-subframe 1 is used as a Far-End Alarm and Control (FEAC) signal. This signal is used for two purposes:

To send alarm and status information from the far-end terminal back to the near-end terminal.


E-16 T3 Environment

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.

DS3 Line Signal The DS3 line signal is coded using the B3ZS zero suppression coding rules, a coding method similar to the HDB3 code (see Section E.2), except that it limits the maximum length of zero runs to 2.

DS3 Alarm and Status Signals • DS3 Alarm Indication Signal (AIS). The DS3 AIS is a signal with a valid

M-frame alignment channel, M-subframe alignment channel, and valid P-bits. The information bits are a 10... sequence, starting with a one (1) after each M-frame alignment bit, M-subframe alignment bit, X-bit, P-bit, and C-bit channel. In addition, the C-bits are set to zero (C1=0, C2=0, and C3=0), and the X-bits are set to one (X1=1 and X2=1).

• DS3 Yellow Alarm. The yellow alarm is declared when the DS3 receive path cannot detect the framing, or detects AIS reception. The yellow alarm is indicated by setting the X-bits to zero (X1=0 and X2=0) in the DS3 signal returned. In the non-alarm condition, the X bits are set to one (X1=1 and X2=1).

• Idle Signal. The idle signal is a signal with a valid M-frame alignment channel, M-subframe alignment channel, and P-bit channel. The information bits are set to a 1100... sequence, starting with a one-one (11) after each M-frame alignment, M-subframe alignment, X-bit, P-bit, and C-bit channels. In addition, the C-bits in M-subframe 3 are set to zero.


SDH Implementation Principles E-17

E.7 SDH Implementation Principles

This section describes the SDH implementation principles, as background for the detailed presentation of the STM-1 signal structures.

In the following explanations, the following terms are used to describe SDH networks:

• Network node. The SDH network node is a facility at which signals built in accordance with the SDH frame structure are generated and/or terminated. Therefore, a network node provides a convenient access point to add or drop payload signals, e.g., PDH tributary signals, for transmission over the SDH network.

• SDH transport system. An SDH transport system provides the technical means to transfer SDH signals between two network nodes.

• SDH network. An SDH network is formed by interconnecting the required number of network nodes by means of SDH transport systems.

Basic SDH Principles The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two principles:

1. Direct synchronous multiplexing of individual tributary signals within the structure of the higher-rate multiplexed signal.

2. Transparent transporting of each individual tributary signal through the network, without any disassembly except at the two network nodes that exchange information through that particular signal.

To permit synchronous multiplexing, SDH equipment is designed to permit efficient and reliable synchronization of the whole network to a single timing reference.

Direct Multiplexing Approach Direct multiplexing means that individual tributary signals can be inserted and removed into the SDH multiplexed signal without intermediate multiplexing and demultiplexing steps. This capability results in the following characteristics:

• Efficient signal transport, as the same SDH transport system can carry various types of payloads (tributary signals). For example, the link between two DSTM-1 modules can be adapted to transport E1, E3 or T3 PDH signals simply by changing the DFSTM-1 configuration parameters.

• Flexible routing, because any tributary can be inserted and removed into the SDH signal as a single unit, without affecting in any way the other tributary signals carried by the same SDH signal. This permits building cost-effective add/drop multiplexers, the key component of flexible networks, instead of implementing digital cross-connect systems as entities separated from multiplexing equipment.


E-18 SDH Implementation Principles

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.

General Structure of SDH Signals The SDH signal is a serial signal stream with a frame structure. Figure E-9 shows the general structure of SDH signals.

N x M Bytes

M Columns

F F F F

N Rows

B Signal ByteF Framing Byte

N x M Bytes

1

2Order of

Transmission

FB

B

BB

B

BB

B

Order ofTransmission

Legend

Figure E-9. General Structure of SDH Signals

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.


SDH Implementation Principles E-19

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.

SDH Frame Organization As shown in Figure E-10, an SDH frame comprises two distinct parts:

• Section Overhead (SOH)

• Virtual Container (VC).

Path

Ove

rhea

d (O

ne C

olum

n)

Virtual Container(VC)

M Columns

N RowsSection

Overhead

F F F F

Figure E-10. SDH Frame Organization

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.

Virtual Container (VC)

The VC is an envelope (i.e., a special type of signal structure, or frame) that is used to transport a tributary signal across the SDH network.

The path followed by a VC within the network may include any number of nodes, therefore the VC may be transferred from one SDH transport system to another, many times on its path through the network. Nevertheless, in most cases the VC is


E-20 STM-1 Frame Structure

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.

E.8 STM-1 Frame Structure

DFSTM-1 modules handle the base-level SDH signal, which is called Synchronous Transport Mode Level 1 (STM-1).

Description of STM-1 Frame Figure E-11 shows the STM-1 frame structure. The frames are transmitted at a fixed rate of 8000 frames per second.

At a transmission rate of 8000 frames per second, each byte supports a data rate of 64 kbps.

The STM-1 signal frame comprises 9 rows by 270 columns, resulting in a total signal capacity of 2430 bytes (19440 bits per frame). Considering the STM-1 frame repetition rate, 8000 frames per second, this yields a bit rate of 155.520 Mbps.

The STM-1 frame comprises the following parts:

• Section Overhead. The STM-1 section overhead occupies the first nine columns of the STM-1 frame, for total of 81 bytes.

• Virtual Container. The remaining 261 columns of the STM-1 frame, which contain a total of 2349 bytes, are allocated to the virtual container. The virtual container itself comprises a container for the payload signal (260 columns), preceded by one column of path overhead.

Note


STM-1 Frame Structure E-21

The virtual container carried in an STM-1 frame is referred to as a Virtual Container Level 4, or VC-4. VC-4, which is transported unchanged across the SDH network, provides a channel capacity of 150.34 Mbps.

The VC-4 structure includes one column (9 bytes) for the VC-4 path overhead, leaving 260 columns of signal carrying capacity (149.76 Mbps). This carrying capacity is sufficient for transporting a 139.264 Mbps tributary signal (the fourth level in the PDH signal hierarchy). The VC-4 signal carrying capacity can also be subdivided, to permit the transport of multiple lower-level PDH signals.

Path

Ove

rhea

d (9

Byt

es)

1 Column

STM-1 Virtual Container (VC-4)

Container Capacity = 150.34 MbpsPayload Capacity = 149.76 Mbps

260 Columns

9 Rows

2430 Bytes/Frame x 8 Bits/Byte x 8000 Frames/sec = 155.52 Mbps

Serial SignalStream

155.52 Mbps

2430 Bytes/Frame

9 Columns

SectionOverhead

F F F F

Figure E-11. STM-1 Frame Structure

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.

Identifying VC-4 Beginning in the STM-1 Frame

When a VC-4 is assembled into the STM-1 frame, a pointer (byte) located in the section overhead of the STM-1 frame indicates the location of the first byte (J1) of the VC-4 that starts in that STM-1 frame.


E-22 SDH Overhead Data

Using Pointers to Correct Timing Differences

SDH network are intended to operate as synchronous networks. Ideally, this means that all SDH network nodes should derive their timing signals from a single master network clock. However, in practical applications, network implementation must accommodate timing differences (clock offsets). These may be the result of an SDH node losing network timing reference and operating on its standby clock, or it may be caused by timing differences at the boundary between two separate SDH networks.

The VC-4 is allowed to float freely within the space made available for it in the STM-1 frame, therefore phase adjustments can be made as required between the VC-4 and the STM-1 frame.

To accommodate timing differences, the VC-4 can be moved (justified), positively or negatively three bytes at time, with respect to the STM-1 frame. This is achieved by simply recalculating and updating the pointer value at each SDH network node. In addition to clock offsets, updating the pointer will also accommodate any other adjustment required between the input SDH signal rate and the timing reference of the SDH mode.

Pointer adjustments introduce jitter. Excessive jitter on a tributary signal degrades signal quality and may cause errors. Therefore, SDH networks must be designed to permit reliable distribution of timing to minimize the number of pointer adjustments.

E.9 SDH Overhead Data

SDH Overhead Data Types In SDH networks, a transmission path can include three equipment functions:

• SDH terminal multiplexer – which performs the insertion/removal of tributary signals into SDH frames

• SDH cross-connect switch – permits to change the routing of tributary signals carried in SDH frames

• Regenerator – used to increase the physical range of the transmission path.

The resulting structure of an SDH transmission path is shown in Figure E-12.


SDH Overhead Data E-23

SDHTerminal

Multiplexer

VCAssembly

SDHTerminal

Multiplexer

TributarySignals

...

TributarySignals

...

MultiplexerSection

RegeneratorSection

RegeneratorSection

RegeneratorSection

Multiplexer Section

VCDisassemblyPath

SDH Cross-Connect

Figure E-12. Structure of Transmission Path in SDH Network

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.

To provide the support and maintenance signals associated with transmission across each segment, each of these segments is provided with its own overhead data, hence three types of overhead data:

• Section overhead, carried in the first nine columns of the STM-1 frame:

Multiplexer section (MS) overhead – carried in overhead rows 5 to 9

Regenerator section (RS) overhead – carried in overhead rows 1 to 3

AU pointers– carried in overhead row 4.

• Path overhead, carried in the first column of a VC-4. The path overhead carried in the VC-4 is called high-order path overhead; see Section E.10 for a description of the low-order path overhead.

Figure E-13 shows the detailed structure of the overhead data in STM-1 frames.



FramingA1

FramingA1

FramingA1

FramingA2

FramingA2

FramingA2

IDC1

BIP-8B1

OrderwireE1

UserF1

DCCD1

DCCD2

DCCD3

PointerH1

PointerH2

PointerH3

PointerH3

PointerH3

B2

APS

K1

APS

K2

DCCD4

DCCD5

DCCD6

DCCD7

DCCD8

DCCD9

DCCD10

DCCD11

DCCD12

OrderwireE2

B2 B2

PathOverhead

Path TraceJ1

BIP-8B3

Signal LabelC2

Path StatusG1

User ChannelF2

MultiframeH4

Bytes reserved for future use

FramingA1

MultiplexSection

Overhead(Rows 5 - 9)

RegeneratorSection

Overhead(Rows 1 - 3)

Section Overhead

BIP-24

AU Pointers(Row 4)

Figure E-13. Organization of STM-1 Overhead Data

Regenerator Section Overhead (RSOH) A regenerator section of an SDH network comprises the transmission medium and associated equipment between a network element and the adjacent regenerator, or between two adjacent regenerators. The associated equipment includes the aggregate interfaces and SDH processing equipment which either originates or terminates the regenerator section overhead.

The functions of the various bytes carried in the STM-1 regenerator section overhead are described below.

Framing (A1, A2 Bytes)

The six framing bytes carry the framing pattern, and are used to indicate the start of an STM-1 frame.

Channel Identifier (C1 Byte)

The C1 byte is used to identify STM-1 frames within a higher-level SDH frame (STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the binary representation of the STM-1 frame number in the STM-N frame.

Parity Check (B1 Byte)

A 8-bit wide bit-interleaved parity (BIP-8) checksum is calculated over all the bits in the STM-1 frame, to permit error monitoring over the regenerator section. The


SDH Overhead Data E-25

computed even-parity checksum is placed in the RSOH of the following STM-1 frame.

Data Communication Channel (D1, D2, D3 Bytes)

The 192 kbps Data Communication Channel (DCC) provides the capability to transfer network management and maintenance information between regenerator section terminating equipment.

Orderwire Channel (E1 Byte)

The E1 byte is used to provide a local orderwire channel for voice communications between regenerators and remote terminal locations.

User Communication Channel (F1 byte)

The F1 byte is intended to provide the network operator with a channel that is terminated at each regenerator location, and can carry proprietary communications.

The information transmitted on this channel can be passed unmodified through a regenerator, or can be overwritten by data generated by the regenerator.

AU Pointers (H1, H2, H3 bytes) The AU (Administration Unit) pointer bytes are used to enable the transfer of STM-1 frames within STM-N frames, and therefore are processed by multiplexer section terminating equipment. Separate pointers are provided for each STM-1 frame in an STM-N frame.

AU pointer function is to link between the section overhead and the associated virtual container(s).

Multiplexer Section Overhead (MSOH) A multiplexer section of an SDH network comprises the transmission medium, together with the associated equipment (including regenerators) that provide the means of transporting information between two consecutive network nodes (e.g., SDH multiplexers). One of the network nodes originates the multiplexer section overhead (MSOH) and the other terminates this overhead.

The functions of the various bytes carried in the STM-1 multiplexer section overhead are described below.

Parity Check (B2 Bytes)

A 24-bit wide bit-interleaved parity (BIP) checksum is calculated over all the bits in the STM-1 frame (except those in the regenerator section overhead). The computed checksum is placed in the MSOH of the following STM-1 frame.

Protection Switching (K1, K2 Bytes)

The K1 and K2 bytes carry the information needed to activate/deactivate the switching between the main and protection paths on a multiplexer section.



Data Communication Channel (D4 to D12 Bytes)

Bytes D4 to D12 provide a 576 kbps data communication channel (DCC) between multiplexer section termination equipment. This channel is used to carry network administration and maintenance information.

Orderwire Channel (E2 Byte)

The E2 byte is used to provide a local orderwire channel for voice communications between multiplexer section terminating equipment.

Alarm Signals

Alarm information is included as part of the MSOH. These functions are explained in Section E.11.

VC-4 Path Overhead Functions The path overhead (POH) is contained within the virtual container portion of the STM-1 frame. The POH data of the VC-4 occupies all the 9 bytes of the first column.

The functions of the various bytes carried in the VC-4 path overhead are described below.

Path Trace Message (J1 Byte)

The J1 byte is used to repetitively transmit a 64-byte string (message). The message is transmitted one byte per VC-4 frame.

A unique message is assigned to each path in an SDH network. Therefore, the path trace message can be used to check continuity between any location on a transmission path and the path source.

Parity Check (B3 Byte)

An 8-bit wide bit-interleaved parity even checksum, used for error performance monitoring on the path, is calculated over all the bits of the previous VC-4. The computed value is placed in the B3 byte.

Signal Label (C2 Byte)

The signal label byte, C2, indicates the structure of the VC-4 container. The signal label can assume 256 values, however two of these values are of particular importance:

• The all “0”s code represents the VC-4 unequipped state (i.e., the VC-4 does not carry any tributary signals)

• The code “00000001” represents VC-4 equipped.

Path Status (G1 Byte)

The G1 byte is used to send status and performance monitoring information from the receive side of the path terminating equipment to the path originating


Tributary Units E-27

equipment. This allows the status and performance of a path to be monitored from either end, or at any point along the path.

Multiframe Indication (H4 byte)

The H4 byte is used as a payload multiframe indicator, to provide support for complex payload structures, for example payload structures carrying multiple tributary units (TUs – see Section E.10).

If, for example, the TU overhead is distributed over four TU frames, these four frames form a TU multiframe structure. The H4 byte then indicates which frame of the TU multiframe is present in the current VC-4.

User Communication Channel (F2 Byte)

The F2 byte supports a user channel that enables proprietary network operator communications between path terminating equipment.

Alarm Signals

Alarm and performance information is included as part of the path overhead.

These functions are explained in Section E.11.

E.10 Tributary Units

The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the transport of a fourth level (139.264 Mbps) PDH multiplex signal.

To enable the transport and switching of lower-rate tributary signals within the VC-4, several special structures, called Tributary Units (TUs), have been defined. The characteristics of each TU type have been specifically selected to carry one of the standardized PDH signal rates. In addition, a fixed number of whole TUs may be mapped within the container area of a VC-4.

Preparing PDH Signals for Transmission through the SDH Network By their own definition, PDH signals are not suitable for transmission through a synchronous network. The method used to prepare a PDH signal for transmission through the SDH network is the use of containers.

The container is an information-carrying structure used for adapting the user’s payload signal for transmission through the SDH network. The adaptation is performed in two steps:

• Organizing the serial bit stream of the payload signal to be transported in accordance with the SDH signal structure

• Adding stuffing bits, which compensate for the difference between the actual user’s data rate and the higher transport rate provided for it within the SDH signal frame. This synchronizes the container bit rate to the SDH network bit rate.


E-28 Tributary Units

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.

Tributary Unit Frame Structure The structure of the tributary unit frame is rather similar to the SDH frame structure, described in Section E.7. With reference to Figure E-10, the tributary unit frame includes two main parts:

• Section overhead part

• Virtual container part, which also comprises two parts:

Container carrying the payload

Low-order path overhead.

Accordingly, this required structure of the tributary unit frame is generated in three steps: • A low rate tributary signal is mapped into the corresponding container.

• The low-path path overhead is added before the container, to form the corresponding virtual container (VC-11, VC-12, VC-2 or VC-3, depending on the TU type)

• A TU pointer is added to indicate the beginning of the VC within the TU frame. This is the only element of TU section overhead.

The TU frame is then multiplexed into a specific location within the VC-4.

Because of the byte interleaving method, a TU frame structure is distributed over four consecutive VC-4 frames. It is therefore more accurate to refer to the structure as a TU multiframe. The phase of the multiframe structure is indicated by the H4 byte contained in the VC-4 path overhead.

Tributary Unit Types As mentioned above, specific TU structures have been defined for each standard PDH multiplex signal level. These structures are explained below: • TU-11: Each TU-11 frame consists of 27 bytes, structured as 3 columns of 9

bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity of 1.728 Mbps and will accommodate the mapping of a North American DS1 signal (1.544 Mbps). 84 TU-11s may be multiplexed into the STM-1 VC-4.

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.


Tributary Units E-29

• TU-12: Each TU-12 frame consists of 36 bytes, structured as 4 columns of 9 bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity of 2.304 Mbps and will accommodate the mapping of a CEPT 2.048 Mbps signal. 63 TU-12s may be multiplexed into the STM-1 VC-4.

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.

VC-4

Pat

h O

verh

ead

260 Columns

9 Rows

Serial SignalStream

155.52 Mbps

2430 Bytes/Frame

SectionOverhead

TU-12 No.2to

TU-12 No.62

9 Columns

1 Column

TU-12No. 63

TU-12No. 1

F F F F

Figure E-14. VC-4 Carrying TU-12 Payload


E-30 Multiplexing Hierarchy

E.11 Multiplexing Hierarchy

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.

The specification of these two items enables the multiplexer/demultiplexer circuits to perform the insertion (multiplexing) and removal (demultiplexing) of the desired signal.

To complete the description of the SDH signal format, this section presents a formal description of the SDH multiplexing hierarchy, which is defined by ITU-T Rec. G.707.

Related Terms

Tributary Unit Group (TUG)

A tributary unit group is a group of similar tributary units that occupy fixed, defined positions in a higher-order virtual container payload area.

The following TUG types are relevant at the STM-1 level:

• TUG-2: consists of 4 TU-11 or 3 TU-12 or one TU-2

• TUG-3: consists of 3 TUG-2 or one TU-3.

Administrative Unit (AU)

An administrative unit is an information structure that is used to adapt between the higher-order path layer and the multiplex section layer.

The administrative unit consists of a higher-order virtual container and an administrative unit pointer that indicates the relative starting point (also called offset) of the virtual container frame within the multiplex section frame.

In order words, the administrative unit pointer simply indicates where a certain VC starts within the SDH signal frame (this information is also called the VC phase alignment).


Multiplexing Hierarchy E-31

The following AU types are relevant:

• AU-3: consists of a VC-3 and an administrative unit pointer that indicates the offset of the VC-3 frame relative to the SDH signal frame

• AU-4: consists of a VC-4 and an administrative unit pointer that indicates the offset of the VC-4 frame relative to the SDH signal frame

Administrative Unit Group (AUG)

An administrative unit group is a group of similar administrative units that occupy fixed, defined positions in the payload area of an STM signal.

Only the AUG-4 is relevant: this AUG consists of three AU-3 or one AU-4.

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.

SDH Multiplexing Methods In accordance with the terms defined above, it is apparent that several methods can be used to generate any given signal structure in the SDH multiplexing hierarchy. Figure E-15 illustrates the methods relevant to the lower STM-N levels (where N can be 1, 4, 16, etc.).

Figure E-15 actually explains the utilization of the various structures explained in the Related Terms section above. The interpretation of Figure E-15 is as follows:

• The TU-11 structure is obtained by inserting a 1.544 Mbps 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 TUG-2 structure can be obtained in three ways:

By combining (multiplexing) four TU-11, or

By multiplexing three TU-12, or

From a single TU-2.

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.


E-32 Multiplexing Hierarchy

STM-N AUG-4 AU-4 VC-4 C-4

TUG-2

TU-2 VC-2 C-2

TU-12 VC-12 C-12

TU-11 VC-11 C-11x4

x3

x1

AU-3 VC-3T3 (44.736 Mbps)

orE3 (34.368 Mbps)

C-3

TUG-3 TU-4 VC-3

x3

x3x1

x7

x7

xN x1

DS2 (6.312 Mbps)

E1 (2.048 Mbps)

T1 (1.544 Mbps)

E4 or DS4(139.264 Mbps)

AligningMappingMultiplexing

Legend

Structures Implementedin the DXC

Figure E-15. SDH Multiplexing Methods

• The VC-3 structure can be obtained in two ways:

By multiplexing seven TUG-2, or

From a single C-3.

• The TUG-3 structure can be obtained in two ways:

By multiplexing seven TUG-2, or

From a single TU-3.

• The VC-4 structure can be obtained in two ways:

By multiplexing three TUG-3, or

From a single C-4.

• The AUG-4 structure can be obtained in two ways:

By multiplexing three AU3, or

From a single AU-4.

• The STM-1 structure is obtained from one AUG-4, whereas the STM-N structure is obtained from N AUG-4.


Multiplexing Hierarchy E-33

TU-12 Numbering Systems According to the ITU-T G.707 recommendation, a TU-12 in the VC-4 structure is defined with the following three numbers:

• The number of the TU-12 inside the TUG-2

• The number of the TUG-2 inside the TUG-3

• The number of the TUG-3 inside the VC-4 payload.

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).

Table E-1. TU-12 Numbering Systems

RAD’s TU-12 No.

TUG-3 No.

TUG-2 No.

TU-12 No.

RAD’s TU-12 No.

TUG-3 No.

TUG-2 No.

TU-12 No.

RAD’s TU-12 No.

TUG-3 No.

TUG-2 No.

TU-12 No.

1 1 1 1 22 2 1 1 43 3 1 1

2 1 2 1 23 2 2 1 44 3 2 1

3 1 3 1 24 2 3 1 45 3 3 1

4 1 4 1 25 2 4 1 46 3 4 1

5 1 5 1 26 2 5 1 47 3 5 1

6 1 6 1 27 2 6 1 48 3 6 1

7 1 7 1 28 2 7 1 49 3 7 1

8 1 1 2 29 2 1 2 50 3 1 2

9 1 2 2 30 2 2 2 51 3 2 2

10 1 3 2 31 2 3 2 52 3 3 2

11 1 4 2 32 2 4 2 53 3 4 2

12 1 5 2 33 2 5 2 54 3 5 2

13 1 6 2 34 2 6 2 55 3 6 2

14 1 7 2 35 2 7 2 56 3 7 2

15 1 1 3 36 2 1 3 57 3 1 3

16 1 2 3 37 2 2 3 58 3 2 3

17 1 3 3 38 2 3 3 59 3 3 3

18 1 4 3 39 2 4 3 60 3 4 3

19 1 5 3 40 2 5 3 61 3 5 3

20 1 6 3 41 2 6 3 62 3 6 3

21 1 7 3 42 2 7 3 63 3 7 3


E-34 SDH Maintenance Signals

E.12 SDH Maintenance Signals

SDH Maintenance Signals The maintenance signals transmitted within the SDH signal structure are explained in Table E-2.

Table E-2. SDH Maintenance Signal Definitions

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.

Note

The AIS indication is an “all 1’s” pattern in pointer bytes.

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.


SDH Maintenance Signals E-35

Table E-2. SDH Maintenance Signal Definitions (Cont.)

Signal Description

Far End Receive Failure (FERF or MS-FERF)

Sent upstream by multiplexer section terminating equipment (MSTE) within 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 Alarm Indication (HO Path RAI, also known as HO Path FERF)

Generated by high order path terminating equipment (HO PTE) in response to received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of POH G1 byte to “1”. 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.

Note

TU Path AIS is only available when generating and/or receiving “floating mode” tributary unit payload structures.

Low Order Path Remote Alarm Indication (LO Path RAI, also known as LO Path FERF)

Generated by low order path terminating equipment (LO FTE) in response to received TU Path AIS. Sent upstream to peer LO PTE. Indicated by setting bit 8 of LO POH V5 byte to “1”. 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”.

Note

LO Path RAI is only available when generating and/or receiving “floating mode” tributary unit payload structures.



Response to Abnormal Conditions This section describes the response to the wide range of conditions that can be detected by the maintenance means built into the SDH frames, and the flow of alarm and indication signals.

Figure E-16 provides a graphical representation of the flow of alarm and indication signals through an SDH transmission path.

LO PTE HO PTE MS TE RS TE MS TE HO PTE LO PTE

RAI(VS)

BIP-2(VS)

FEBE(VS)

RAI(G1)

FERF(X2)

LOSLOF

LOSLOF

AIS (X2) AIS(H1H2)

TributaryAIS

RAI (G1)

RAI (VS)

B1(BIP-8)

B2(BIP-24)

B1(BIP-8)

B3(BIP-8)

FEBE(G1)

FEBE(G1)

FEBE(VS)

CollectionTransmissionGeneration

Legend

Low Order Path

High Order Path

Multiplexer Section

RegeneratorSection

RegeneratorSection

AIS(V1V2)

LOP LOP LOP

LO Low OrderHO High Low Order

PTE Path Terminating EquipmentRS TE Regenerator Section Terminating EquipmentMS TE Multiplexer Section Terminating Equipment

Figure E-16. Flow of Alarm and Indication Signals through an SDH Transmission Path

Flow of Alarm and Response Signals

The major alarm conditions such as Loss of Signal (LOS), Loss of Frame (LOF), and Loss of Pointer (LOP) cause various types of Alarm Indication Signals (AIS) to be transmitted downstream.

In response to the detection of an AIS signals, and detection of major receiver alarm conditions, other alarm signals are sent upstream to warn of trouble downstream:


SDH Maintenance Signals E-37

• 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.

Command Set Description F-1

Appendix F DXC Supervision Language

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.

F.2 Command Set Description

This Section describes the DXC commands. The commands are listed in alphabetical order (see Table 5-1 for a complete list).

The description given below includes the command format, use, and options. The following notational conventions are used below:

[ ] square brackets indicate optional entry/parameter indicates list of optional parameters, one of which must be selected <Enter> indicates the pressing of the Enter key <sp> indicates the pressing of the space key A indicates an I/O 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)

X indicates one of the I/O slot numbers or one of the DCL.3 slots: DCLA for CL-A and DCLB for CL-B

B indicates an external port number within an I/O module (1 or 2) iB indicates an internal port number within an I/O module. iB is 1

through 16 for E3 modules, 1 through 28 for T3 modules, and 1 through 30 for DFSTM-1 modules

TT indicates the timeslot number within the frame carried by a port (1 through 31 for an E1 port; 1 through 24 and F for a T1 port)

* indicates I/O module parameters L indicates an HDSL line (L1 or L2) (used only for DHL modules) LL indicates an alarm number D indicates a configuration database number.

Appendix F DXC Supervision Language DXC-8R/10A/30/30E Installation and Operation Manual

F-2 Command Set Description

The screens appearing in this Appendix are given for illustration purposes only, and 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

CLR ALM [/A]

Note

DXC-8R/10A/30/30E Installation and Operation Manual Appendix F DXC Supervision Language


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>

An inband loopback is deactivated by repeatedly transmitting the deactivation sequence, therefore the loopback can be considered as deactivated only after approximately 2 seconds.

• To send the deactivation command for the inband activated loopback on port B of the DHL module installed in slot A, type:

CLR LOOP HDSL_INBAND A:B <Enter> or CLR LP HDSL_INBAND A:B <Enter>

• To send the deactivation command for the local loopback on port B of the DHL module installed in slot A, type:

CLR LOOP L LINE A:B<Enter> or CLR LP L LINE A:B<Enter>

• To deactivate the remote loopback activated on the timeslots selected for BER testing on port B of the local I/O module A, type:

CLR LOOP TS REM A:B <Enter> or CLR LP TS REM A:B <Enter>

• To deactivate the BERT test on port B of I/O module A, type:

CLR LOOP BERT A:B <Enter> or CLR LP BERT A:B <Enter>

Note

• To deactivate the monitoring of port B of I/O module A, type:

CLR LOOP MONITOR A:B <Enter> or CLR LP MONITOR A:B <Enter>

• To deactivate the sending of RDI through port B of DFSTM-1 module A, type:

CLR LOOP SND_RDI A:B <Enter> or CLR LP SND_RDI A:B <Enter>

• To deactivate the sending of AIS through port B of DFSTM-1 module A, type:

CLR LOOP DS_AIS A:B <Enter> or CLR LP DS_AIS A:B <Enter> • To deactivate all the tests and loopbacks on port B of I/O module A, type:

CLR LOOP A:B <Enter> or CLR LP A:B <Enter>

DXC displays the time and date, followed by the DXC prompt. If the specified test is not active, DXC displays ERROR 502 (loop is not active).

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 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 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 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.

DEF ALM ATTRIB

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.

The alarm attributes can be defined at three levels: • • Module port: the attribute is modified only for alarms associated with a

user-selected module port.

• Module: the attribute is modified only for alarms associated with a user-selected module.

• System level: the attribute is modified for the DXC system alarms.

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 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 to display NORMAL.

To mask or invert all the alarms of the displayed group, press <F> or to display MASK, respectively INVERT.

When done, press <Enter> to end.

3. To change the attributes of individual alarms, proceed as follows: • Display the main group of alarms that includes the alarm whose attribute is

to be modified, and then select USER under the ATTRIBUTES heading.

After pressing <Enter>, you will see the first line of the alarm attribute definition data form for the first alarm in the selected main group (this data form includes the description and the current attribute of the alarm). A typical display is shown below:

ALARM NUMBER & DESCRIPTION STATE

01 REAL TIME CLOCK BATTERY FAILURE NORMAL

The functions of the fields are as follows: ALARM NUMBER Displays the number (code) and the description of the first

alarm in the selected group (refer to Appendix B for a list of the various alarms).

STATE Displays the current alarm attribute.

If the selected main group is an I/O module, then before displaying the alarm attribute definition data form you will be prompted to select the subgroup (level) for which the alarm attribute will be modified. A typical display is shown below:

SUB_GROUP ATTRIBUTE

GENERAL NORMAL

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 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 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 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 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.

During BER testing, it is necessary to activate a loopback at the desired location along the signal path, to return the port transmit data stream to the input of the port receive path.

The loopback can be a physical loopback connection, or a loopback activated by a management system command.

For modules with E1 and T1 ports (including DHL modules), you can use inband loopback activation by sending the LOOP INBAND command. The inband loopback activation code, defined in ANSI T1E1.2/93-003, is used to instruct the equipment located at the remote end of the link (e.g., another DXC port, or an FCD-E1 unit) to activate a remote loopback in the user-specified timeslots, and therefore should be sent before starting the BER test; the deactivation code (sent

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

The functions of the fields are as follows:

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_ INJECTION_RATE

Enables the injection of a calibrated rate of errors in the transmitted test 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.

2. After making the desired selections, press <Enter> to continue. If the selected MODE is DHS_PORT, you will be prompted to specify the

destination port. A typical display is shown below.

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 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.

NUM_OF_RETRIES WAIT_FOR_CONNECT DIAL_MODE ALT_NUM_MODE 0 60SEC TONE NO

2. Change the parameter values as follows: • Bring the cursor to the beginning of the first field to be changed by pressing

the spacebar.

To change the selected field, press <F> or to scroll among the available selections.

When the desired selection is displayed, press the spacebar to move to the next field.

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.

NEW ALTERNATE NUMBER [MAX 20 CHARS] = CURRENT ALTERNATE NUMBER = 'alternate number'

5. Enter the desired directory number, and press <Enter> to end.

DEF DCL FLIP

Purpose

Define the parameters related to the use of DCL.3 redundancy.

This command is applicable only for a DXC-8R, DXC-30, or DXC-30E equipped with two DCL.3 modules. 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

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 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.

FLIP_ON_STATION_CLOCK When redundancy is enabled, this parameter is used to enable flipping between the DCL.3 modules in case the external (station) clock signal connected to one module fails. The available selections are as follows:

NO Flipping as a result of external clock signal failure is disabled.

YES Flipping as a result of external clock signal failure is enabled. This selection is recommended when the DXC system is configured to use the external (station) clock as its nodal clock reference.

3. Select the desired parameter values and press <Enter> to end.

DEF MANAGER LIST

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

3. Repeat the procedure described above to define the additional management stations (No. 2 through 20). After pressing <Enter> for the IP address of the 20th manager, you will see the current list, in the following format:

CURRENT MANAGERS LIST PARAMETERS - - - - - - - - - - - - - - - - - MANAGER 1 IP ADDRESS IS := 999.999.999.999 MANAGER 2 IP ADDRESS IS := 999.999.999.999 MANAGER 3 IP ADDRESS IS := 999.999.999.999 MANAGER 4 IP ADDRESS IS := 999.999.999.999 MANAGER 5 IP ADDRESS IS := 999.999.999.999 MANAGER 6 IP ADDRESS IS := 999.999.999.999 MANAGER 7 IP ADDRESS IS := 999.999.999.999 MANAGER 8 IP ADDRESS IS := 999.999.999.999 MANAGER 9 IP ADDRESS IS := 999.999.999.999 MANAGER 10 IP ADDRESS IS := 999.999.999.999 MANAGER 11 IP ADDRESS IS := 999.999.999.999 MANAGER 12 IP ADDRESS IS := 999.999.999.999 MANAGER 13 IP ADDRESS IS := 999.999.999.999 MANAGER 14 IP ADDRESS IS := 999.999.999.999 MANAGER 15 IP ADDRESS IS := 999.999.999.999 MANAGER 16 IP ADDRESS IS := 999.999.999.999 MANAGER 17 IP ADDRESS IS := 999.999.999.999 MANAGER 18 IP ADDRESS IS := 999.999.999.999 MANAGER 19 IP ADDRESS IS := 999.999.999.999 MANAGER 20 IP ADDRESS IS := 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 =

where 'name' is the current DXC node name.

2. Type the desired name, and then press <Enter>.

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.

Refer to Appendix C for additional details.

Select the needed value as described below in step 2, and then press <Enter> to end. If the DCL.3 module has RS-232 interfaces, you will see the first line of the

network port parameters data form. A typical form is shown below. The form presents the current parameter values as defaults.


AUTO 8 NO NONE

the spacebar.



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_ PROTOCOL

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.

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 , 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>

The password entry screen appears:

NEW PASSWORD [4 to 6 CHARS] = CURRENT PASSWORD = 'password'

where 'password' is the current password.

2. Type the required password. Carefully check that the specified password has been indeed typed in, and then press <Enter>.

• It is highly recommended to change the default password provided by RAD. • Before entering a new password, make sure that section 2, PASSWRD, of the

internal switch S1 of module DCL.3 is not set to ON, because in such a case the default password (RAD) is enforced.

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

2. Change parameters as follows:

• Bring cursor to the beginning of changed field by pressing the space key (note that each digit under TIME_OUT is a separate field).

• Scroll among possible field values, using <F> or keys.

Notes

3. After the desired parameters are displayed, press <Enter>:

• If the selected redundancy mode is NONE, Y_CABLE or DUAL_CABLE_PROTECTION, this ends the command, and DXC displays the date and time, followed by the DXC prompt.

• If the selected mode is SINGLE_SLOT_PROTECTION, the second line of the redundancy configuration data form appears. A typical line is shown below:

FLIP_MODE SOFTWARE

4. Select the desired mode and press <Enter> to end the command.

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_ MODE

Selects the redundancy mode (refer to Chapter 3 for a 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.

Note

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 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_ DEVICE

Selects the management mode supported by the CONTROL port: 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_ PROTOCOL

Controls the transmission of routing tables, which enable the routing 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 spacebar.



After the desired parameter values are selected, press <Enter>. The next line of the system parameters data form is displayed. A typical form is shown below. The form presents the current parameter values as defaults. TS_ALLOC_MODE STATION_CLOCK_IF

STATIC G703

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.

5. After the desired values are selected, press <Enter>. • For the DXC-10A and DXC-8R, this ends the command and you will see

the TIME and DATE fields, followed by the DXC-10A prompt.

For the DXC-30 and DXC-30E, you will see the next line of the DXC system parameters data form, which covers the I/O slots 6 through 10. Repeat the procedure described above to change the modules types as required, and then press <Enter> to display the last line, which covers the I/O slots 11 through 15.

A typical last line of the system parameters data form is shown below:

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.

DEF TEST PORT

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

The parameters included on the first line are as follows:

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.

2. Change the displayed parameters as necessary using the procedure explained above. When done, press <Enter>: If the MAP_MODE is SEQ, after pressing <Enter> the command entry is

ended.

If the MAP_MODE is USER, after pressing <Enter> you will see the first page of the monitored timeslot selection map.

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.

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 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

4. Change the type as explained in step 3 above.

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 ports.

Note

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

The information displayed by this command is as follows. AGENT NAME Displays the logical name assigned to the DXC. AGENT IP ADDRESS Displays 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).

AGENT MAC ADDRESS Displays the MAC address assigned to the DXC SNMP agent (six groups of digits in the range of 0 through 255, separated by periods).

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

The display fields are as follows: ERROR_BITS Total number of bit errors detected (maximum 65535). RUN_TIME (SEC) Total time the test is running. ERRORS (SEC) Total number of seconds in which errors have been detected. SYNC LOSS (SEC) Total number of seconds in which loss of frame alignment

occurred. ERROR_INJECT Indicates whether errors are injected (ON) or not (OFF).

DSP BERT REM

Purpose

Display the result of the BER test activated by the user on the ASMi-31-2 modem connected to the specified port of the D8U or D16U module.

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.

The interpretation of the information displayed in the example given above is as follows: • The status of the bus links 03:01 and 03:02is FIXED: this indicates that a

Type 1 module is 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 is installed in I/O slot 1: port 1 of this module is assigned four bus links (01:01, 01:02, 02:01 and 02:02).

Therefore, although I/O slot 2 is physically free, it is not recommended to install a module in this slot, because this would result in reallocation of timeslots, which would cause a short disruption in traffic flow.

• Modules can be installed in I/O slots 4, 9, 10, 12, 13 and 14, because their bus links are free. No traffic disruption would be caused by installing and/or configuring a module in these slots.

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.

Display Format - DIM Modules

The display format depends on the module type. A typical display for a DIM module is shown below.

IO-SLOT-04 Online DB Slot Cross-Connect Mapping Configuration DEST: 1 2 3 4 5 6 7 8 SLOT: 02:01 02:02 NC NC NC NC NC NC

The display lists the module and port serving each of the eight links that may be used by a DIM module.

Display Format - Other Modules

A typical display for a D8E1 module is shown below.

IO-SLOT - 1 PORT -1 Online DB Time-Slot Cross-Connect Mapping Configuration

PORT TS UTILIZATION PERCENT: 40.000

TS : NO 1 NO 2 NO 3 NO 4 NO 5 NO 6 NO 7 TYPE: DATA (B) NC NC NC NC NC NC DEST: 02:01:01 01:01:01 01:01:01 01:01:01 01:01:01 01:01:01 01:01:01

TS : NO 8 NO 9 NO 10 NO 11 NO 12 NO 13 NO 14 TYPE: NC NC NC NC NC NC NC DEST: 01:01:01 01:01:01 01:01:01 01:01:01 01:01:01 01:01:01 01:01:01



TS : NO 29 NO 30 NO 31 TYPE: NC NC NC DEST: 01:01:01 01:01:01 01:01:01

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.

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).

Note

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

SE EVENT Severely-errored framing event (0, 1 or more)

FE EVENT Frame synchronization bit error event (0, 1 or more)

LV EVENT Line code violation event (0, 1 or more)

SL EVENT Controlled slip event (0, 1 or more)

LOOPBACK Loopback on information bits (YES or NO)

COUNTER Provides time reference (current second, one second before, two seconds before and four seconds before). The counter performs calculations in binary code.

FCS Indicates whether the message FCS is GOOD or BAD (if BAD, the message probably contains an error)

T Message time stamp, i.e., the time the message has been received at the supervision terminal (hours:minutes:seconds).

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>

After entering the command, DXC displays NO FLIP, to indicate that no flip occurred since the last time the DXC has been turned on or reset, or displays the cause of the last flip, in a format that depends on the module type.

For DCL.3 modules, the following format is used:

LAST FLIP CAUSED BY : 'cause'

where 'cause' shows NO FLIP if no flip has yet occurred, or consists of a message that explains the flip cause: FORCED FLIP The flip has been initiated by the operator, by means of the DEF

DCL FLIP command.

OFF LINE CL The flip occurred because the other module has REMOVED been removed from the DXC.

MATRIX ERROR The flip occurred because of a malfunction in the timeslot routing matrix of the DCL.3 module.

DCL HARDWARE The flip occurred because of a hardware failure. FAILURE

DCL DATABASE The flip occurred because a checksum error has CHECKSUM been detected in the configuration database FAILURE stored in the non-volatile memory of the module.

DCL EPROM The flip occurred because the module EPROM failed. FAILURE

NVRAM FAILURE The flip occurred because the battery that protects the contents BATTERY of the non-volatile memory of the module failed.

RESET OR MODULE The flip occurred because the other module has REMOVED been removed from the DXC, or because of a reset command.

For an I/O module or redundant pair, the cause of the last flip is displayed in the format:

SLOT FLIP_CAUSE FLIP_DATE FLIP_TIME 01 'cause' 12.07.98 14:13:12

where 'cause' shows NO FLIP if no flip has yet occurred, or consists of a message that explains the flip cause.

DSP HDR TST

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.

DSP MANAGER LIST

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:

MANAGERS LIST PARAMETERS - - - - - - - - - - - - - - - - - MANAGER 1 IP ADDRESS IS := 999.999.999.999 MANAGER 2 IP ADDRESS IS := 999.999.999.999 MANAGER 3 IP ADDRESS IS := 999.999.999.999 MANAGER 4 IP ADDRESS IS := 999.999.999.999 MANAGER 5 IP ADDRESS IS := 999.999.999.999 MANAGER 6 IP ADDRESS IS := 999.999.999.999 MANAGER 7 IP ADDRESS IS := 999.999.999.999 MANAGER 8 IP ADDRESS IS := 999.999.999.999 MANAGER 9 IP ADDRESS IS := 999.999.999.999 MANAGER 10 IP ADDRESS IS := 999.999.999.999 MANAGER 11 IP ADDRESS IS := 999.999.999.999 MANAGER 12 IP ADDRESS IS := 999.999.999.999 MANAGER 13 IP ADDRESS IS := 999.999.999.999 MANAGER 14 IP ADDRESS IS := 999.999.999.999 MANAGER 15 IP ADDRESS IS := 999.999.999.999 MANAGER 16 IP ADDRESS IS := 999.999.999.999 MANAGER 17 IP ADDRESS IS := 999.999.999.999 MANAGER 18 IP ADDRESS IS := 999.999.999.999 MANAGER 19 IP ADDRESS IS := 999.999.999.999 MANAGER 20 IP ADDRESS IS := 999.999.999.999

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.

For internal ports, B includes an identifier, usually i, added as a prefix before the port number.

• To display the performance monitoring registers of port A:B and clear only its performance monitoring event register, type:

DSP PM A:B /C<Enter>

• To display the performance monitoring registers of port A:B, clear all its performance monitoring registers, and restart the count intervals, type:

DSP PM A:B /CA<Enter>

• To display the performance monitoring registers of HDSL line L (applicable only for DHL modules), type:

DSP PM A:B /L<Enter>

• To display the performance monitoring registers of HDSL line L, clear all its performance monitoring registers, and restart the count intervals, type:

DSP PM A:B /L /CA<Enter>

Display Format - T1 Ports

The performance monitoring registers displayed for a T1 port with ESF framing are listed in the following order:

• The first section of the display shows the performance data for the current 15-minute interval:

ESF ERROR EVENTS = [0] ..... [65535] CURRENT ES = [0] ..... [900] CURRENT UAS = [0] ..... [900] CURRENT SES = [0] ..... [900] CURRENT BES = [0] ..... [900] CURRENT LOFC = [0] ..... [255] CURRENT CSS = [0] ..... [255] CURRENT TIMER = [0] ..... [900] INTERVAL mm ES=nnn UAS=nnn BES=nnn SES=nnn LOFC=nnn CS=nnn

where mm is 0 to 96, and nnn is 0 to 900.

• The second section of the display shows the performance data for the last 24 hours:

24 HOUR ES = [0] ..... [65535] 24 HOUR UAS = [0] ..... [65535] 24 HOUR SES = [0] ..... [65535] 24 HOUR BES = [0] ..... [65535] 24 HOUR LOFC = [0] ..... [255] 24 HOUR CSS = [0] ..... [255] LAST 24 DEGRADE MIN = [0] ..... [1440] 24 HOUR INTERVAL = [0] ..... [96]

The numbers in brackets indicate the range of values for each register.

The same display is applicable for both internal and external T1 ports.



Display Format - E1 Ports

For E1 ports with CRC-4 enabled, the performance monitoring registers are displayed in a format similar to that described above for T1 ports, except that in the first section (current 15-minute performance data) the ESF ERROR EVENTS line is replaced with the CRC ERROR EVENTS and CRC AVG ERR EVENTS lines. A typical display is shown below:

CRC ERROR EVENTS = [0] ..... [1000] CRC AVG ERR EVENTS = [0] ..... [1000] CURRENT ES = [0] ..... [900] CURRENT UAS = [0] ..... [900] CURRENT SES = [0] ..... [900] CURRENT BES = [0] ..... [900] CURRENT LOFC = [0] ..... [255] CURRENT CSS = [0] ..... [255] CURRENT TIMER = [0] ..... [900] INTERVAL mm ES=nnn UAS=nnn BES=nnn SES=nnn LOFC=nnn CS=nnn

The same display is applicable for both internal and external E1 ports.

Display Format - E3 and T3 Ports

A typical performance monitoring information display for E3 and T3 ports is shown below:

PM OF: I/O - 7 PORT - 1

CURRENT LES = 847 CURRENT PES = 10 CURRENT PSES = 10 CURRENT CES = 10 CURRENT CSES = 10 CURRENT SEFS = 847 CURRENT UAS = 847 CURRENT TIMER = 847

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



Display Format - HDSL Ports

A typical performance monitoring display for an HDSL line of a DHL/E1 module is shown below:

CURRENT ES = [0] ..... [65535] CURRENT UAS = [0] ..... [65535] CURRENT SES = [0] ..... [65535] CURRENT BBE = [0] ..... [65535] CURRENT TIMER = [0] ..... [900] INTERVAL mm ES=nnn UAS=nnn SES=nnn BBE=nnn 24 HOUR ES = [0] ..... [65535] 24 HOUR UAS = [0] ..... [65535] 24 HOUR SES = [0] ..... [65535] 24 HOUR BBE = [0] ..... [65535] 24 HOUR INTERVAL = [0] ..... [96]

Display Format - SHDSL Ports

A typical performance monitoring information display for an SHDSL port is shown below:

PM OF: I/O-7 PORT – 1 SIDE - LOC

CRC ANOMALIES COUNTER = 0 LOSW ERRORS COUNTER = 0 CURRENT ES = 0 CURRENT UAS = 0 CURRENT SES = 0 CURRENT LOSWS = 0 LOOP ATTENUATION = 0 SNR MARGIN = 13 RECEIVE GAIN = 0 TRANSMIT POWER = 0 ACTUAL POWER BACKOFF = 0 CURRENT DAY TIMER = 549

INTERVAL 1 ES = 0 UAS = 0 SES= 0 LOSWS = 0 CRC = 0 LOSW = 0 INTERVAL 2 ES = 0 UAS = 0 SES= 0 LOSWS = 0 CRC = 0 LOSW = 0

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.

Display Format – STM-1 Ports

A typical performance monitoring display for an external STM-1 port is shown below:

PM OF: I/O - 12 PORT - 1

CURRENT ES = 0 CURRENT SES = 0 CURRENT UAS(SEFS) = 0 CURRENT CV = 0 CURRENT TIMER = 26 INTERVAL 1 ES = 1 SES = 1 UAS(SEFS) = 128 CV = 0 INTERVAL 2 ES = 0 SES = 0 UAS(SEFS) = 0 CV = 0 INTERVAL 3 ES = 0 SES = 0 UAS(SEFS) = 0 CV = 0 INTERVAL 4 ES = 0 SES = 0 UAS(SEFS) = 0 CV = 0 INTERVAL 5 ES = 0 SES = 0 UAS(SEFS) = 0 CV = 0 INTERVAL 6 ES = 0 SES = 0 UAS(SEFS) = 0 CV = 0 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.

DSP REM AGENT

Purpose

Display information on the remote SNMP agents that are known to the DXC IP router, provided SNMP management is enabled.

The maximum number of agents that are stored in the table is 10.

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

The fields displayed for each agent are as follows: IP ADDRESS The IP address of the remote agent. MUX NAME The logical name of the remote agent. PHYSICAL DISTANCE The physical distance is a metric that indicates the number of

hops (through the management network) to the remote agent.

DISTANCE Metric that indicates the logical distance (through the management network) to the remote agent, and is used, among other factors, in the selection of the optimal route to be used by the management traffic.

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.

The general organization of the display is illustrated below:

CARD TYPE HARDWARE REV. SOFTWARE VER. CL-A DCL3 X.Y Z.WW CL-B DCL3 X.Y Z.WW I/O 01 DTI_CSU X.Y Z.W I/O 02 DTI_CSU X.Y Z.W I/O 03 DE1_LTU X.Y Z.W . . . . . . . . . . . . I/O 15 DE1_DSU X.Y ZZ.W

where X.Y stands for the hardware revision, and Z.W or Z.WW stands for the software revision of an I/O or DCL.3 module, respectively. UNDEF indicates a preliminary release.

• To display the information related to a specific I/O or DCL.3 module, type:

DSP REV X<Enter>

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>

• To display the status of a selected remote I/O port, type:

DSP ST A:B REM<Enter>

Display Format – DCL.3 Module

A typical status display for a DCL.3 module is shown below:

DATABASE: DCL.3 HARDWARE: DCL.3 SOFTWARE VERSION: XX.YY HARDWARE REVISION: XX.YY HARDWARE FAILURE: NO ACTIVE STATE : ONLINE SP DEFAULT PARAMETERS SWITCH : OFF PASSWORD SWITCH : OFF DATABASE INIT SWITCH : OFF PC SP SWITCH : OFF

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 VERSION

Displays the module software version.

HARDWARE REVISION

Displays the module hardware revision.

HARDWARE FAILURE

Displays the state of the module hardware:

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 PARAMETERS

Displays the state of the DP SP section of switch S1 of the selected module. The normal state of this switch is OFF.



Cont.

Parameters Function

PASSWORD SWITCH

Displays the state of the PASSWORD section of switch S1 of the selected module. The normal state of this switch is OFF.

DATABASE INIT SWITCH

Displays the state of the DB INIT section of switch S1 of the 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.

Display Format – Status Display for I/O Modules

The normal display format for I/O modules is shown below:

DATABASE: 'module type' HARDWARE: 'module type' SOFTWARE VERSION: X.YY HARDWARE REVISION: X.YY HARDWARE FAILURE: NO

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 VERSION

Displays the module software version.

HARDWARE REVISION

Displays the module hardware revision.

HARDWARE FAILURE

Displays the state of the module hardware:

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).

• If the module is configured to operate in the Y-cable redundancy mode, the following information is displayed:

IO REDUNDANCY MODE: Y_CABLE ACTIVE_STATE : ONLINE

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).

Display Format – Status Display for Individual Module Ports

Refer to the Installation and Operation Manual of the corresponding 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:

INBAND_MANAGEMENT ROUTE_PROTOCOL TIMESLOT STATUS

I0-01:I-01 DEDICATE PROPRIET 08 ON

IO-03:01 TSO/F PROPRIET N/A OFF

IO-03:02 DEDICATE PROPRIET 01 LOOPED

IO-06:01 D-FR RIP-II 01 ON

IO-12:01 PROPRIET PROPRIET N/A OFF



Display Fields – E1, T1 and DHS ports

The fields included in the status information display for the E1, T1 and DHS ports are listed below:

Parameter Function Values

INBAND_ MANAGEMENT

Controls the transfer of inband management traffic through the selected external port.

The D-PPP and D-FR traffic routing options are generally used with the RIP2 routing protocol.

For a description of the various traffic routing options, refer to Inband Management Traffic Routing in Section C.4.

NONE Transfer of management traffic is disabled.

TS0/F The transfer of management traffic is enabled. The management traffic is transferred using the national bits, Sa4 through Sa8.

DEDIC Transfer of management traffic is enabled. The management traffic is transferred in a dedicated timeslot, using a RAD proprietary protocol.

D-PPP Transfer of management traffic is enabled. The management traffic is transferred in a dedicated timeslot, using synchronous PPP HDLC encapsulation.

D-FR Transfer of management traffic is enabled. The management traffic is transferred in a dedicated timeslot, using frame relay encapsulation (under DLCI 100) in accordance with RFC 1490.

INBAND_ MANAGEMENT (Cont.)

Note The inband management data rate is as follows: • For the TS0 method, the supported data rates are 4 kbps (use of only one

Sa bit (always Sa4)), 8 kbps (two Sa bits), 12 kbps (three Sa bits), 16 kbps (four Sa bits), and 20 kbps (all the five Sa bits).

• For the DEDIC, D-PPP, and D-FR, the supported data rate is 64 kbps

ROUTE_ PROTOCOL

This field controls the transmission of routing tables, which enable the use of routing for management traffic carried through this port

NONE Routing not supported. PROPIET Routing of management traffic by means of

the RAD proprietary protocol. RIP-II Management traffic is also routed using the

RIP2 protocol, in addition to the RAD proprietary protocol.

Default: NONE

TIMESLOT Indicates the number of management timeslot for DEDIC, D-PPP and D-FR options.

Otherwise, displays N/A.

STATUS This field shows the status of the connection.

This field does not appear when the D-PPP and D-FR traffic routing options are selected.

ON The connection between the two end devices is established and the two ends of the link are synchronized.

OFF There is a problem in connection between the two end devices.

LOOPED There is a loop somewhere on the link passing through the selected port

Default: ON



Display Fields – DIM module

The fields included in the DIM module status information display are listed below:


INBAND_ MANAGEMENT


PROPRIET The management traffic (IP data) is transferred end-to-end through the DIM link, using a RAD proprietary protocol.

ROUTE_PROTOCOL Always shows PROPRIET.

TIMESLOT Always shows N/A.

STATUS This field shows the status of the connection.

ON The connection between the two end devices is established and the two ends of the link are synchronized.


LOOPED There is a loop on the link passing through the selected port

Default: ON

Display Fields – E3 and T3 modules

If the module is managed through an internal port, the fields included in the status information display are as follows:


INBAND_ MANAGEMENT


The D-PPP and D-FR traffic routing options are generally used with the RIP2 routing protocol.

For a description of the various traffic routing options, refer to Inband Management Traffic Routing in Section C.4.

NONE Transfer of management traffic is disabled. Always select this option when the selected port is configured for the TRANS (transparent) link mode, because this mode requires one-to-one mapping of time slots to the source port.

DEDIC Transfer of management traffic is enabled. The management traffic is transferred in a dedicated time slot, using a RAD proprietary protocol. This selection is not available when C-BIT_TX_RX_MNG is selected for the E3/T3 port INB_MNG parameter.

D-PPP Transfer of management traffic is enabled. The management traffic is transferred in a dedicated time slot, using synchronous PPP HDLC encapsulation. This selection is not available when C-BIT_TX_RX_MNG is selected for the T3 port INB_MNG parameter.

D-FR Transfer of management traffic is enabled. The management traffic is transferred in a dedicated time slot, using frame relay encapsulation (under DLCI 100) in accordance with RFC 1490. This selection is not available when C-BIT_TX_RX_MNG is selected for the E3/T3 port INB_MNG parameter.

Note The inband management data rate for the DEDIC, D-PPP, and D-FR is 64 kbps




ROUTE_ PROTOCOL


NONE Routing not supported. PROPIET Routing of management traffic by means of the

RAD proprietary protocol. RIP-II Management traffic is also routed using the RIP2

protocol, in addition to the RAD proprietary protocol.

Default: NONE

TIMESLOT Indicates the number of management timeslot for DEDIC, D-PPP and D-FR options.

Otherwise, displays N/A.

STATUS ON The connection between the two end devices is established and the two ends of the link are synchronized.



Default: ON

If a T3 module is managed through an external T3 port, the fields included in the status information display are as follows:


INBAND_ MANAGEMENT


C-BIT The DT3 module uses the asynchronous C-bit parity framing mode, and also supports

the transfer of management traffic through the 28.2 kbps terminal-to-terminal path maintenance data link. The management traffic is routed to the DCL.3 module, which can receive and transmit system management information through the data link. When this mode is selected, the option to use a dedicated time slot of one of the DS1 ports to carry the management traffic is disabled.

ROUTE_ PROTOCOL


NONE Routing not supported. PROPIET Routing of management traffic by means of

the RAD proprietary protocol. RIP-II Management traffic is also routed using the

RIP2 protocol, in addition to the RAD proprietary protocol.

Default: NONE

TIMESLOT Always displays N/A.

STATUS ON The connection between the two end devices is established and the two ends of the link are synchronized.

OFF There is a problem in connection between the two devices.


Default: ON

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>,

where A is the slot number of a module operating in the single-slot protection mode, or one of the slots in which modules configured to operate in the Y-cable redundancy mode are installed.

• To display the status of all the modules configured to use I/O redundancy in the system, type:

DSP ST RDN *<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.

OFFLINE For a module operating in the hardware redundancy mode, displays the number of the slot of the currently off-line module. For a module operating in the line redundancy mode, this field displays the number of the currently off-line port.

If redundancy is not active on the requested module, the following line is displayed:

NO IO REDUNDANCY

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

The system status fields are described below:

Parameter Function

NODE The node number of the DXC (0 through 255).

NAME The node name of the DXC.

PRODUCT Displays the equipment version, e.g., DXC-30.

MAJOR ALARM STATE

Indicates whether a major alarm is present (ON) or not (OFF).

MINOR ALARM STATE

Indicates whether a minor alarm is present (ON) or not (OFF).



Parameter Function

ALARM RELAY STATE

Indicates the state of the alarm relay: ON or OFF.

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 DATABASE NUMBER

Always displays 1.

INVERTED ALARMS

Indicates whether the alarms are inverted.

A typical installed-modules display is shown below:

INSTALLED MODULES

SLOT: PS-A PS-B CL-A CL-B HW: PS(ON) PS(ON) DCL.3 DCL.3

I/O: 1 2 3 4 5 DB: DT1_CSU DT1_DSU DE1_DSU DE1_LTU DHS HW: DT1_CSU DT1_DSU DE1_DSU DE1_LTU DHS

I/O: 6 7 8 9 10 DB: DHS DE1_LTU DT1_CSU DE1_DSU DE1_HDSL HW: DHS DE1_LTU DT1_CSU DE1_DSU DE1_HDSL

I/O: 11 12 13 14 15 DB: DE1_DSU DT1_F DIM DE1_DSU DT1_CSU HW: DHS DT1_F DIM DE1_DSU DT1_CSU

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.



The fields in this section are described below:

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).

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).

Note

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:

SLOT:PORT NUMBER OF FREE TS MAX TS

2:1 6 31

2:2 1 26

2:3 20 20

2:4 1 26

2:5 3 28

2:6 0 31

2:7 0 31

2:8 N/A 0

NUMBER OF FREE TS IN MODULE POOL

19

• Press spacebar to see the similar timeslot allocation screen for the next

module:



DSP TS ALLOCATION:

SLOT/PORT NUMBER OF FREE TS MAX TS

3:1 31 31

3:2 5 15

3:3 2 12

3:4 N/A 0

NUMBER OF FREE TS IN MODULE POOL

4

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.

NUMBER OF TS IN FREE LINKS POOL

589

NUMBER OF FREE TS IN SYSTEM POOL

612

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.

• 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.

Notes

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:

SLOT PORT NUM OF CONNECTED TS MAX TS UTILIZATION

1 1 2 5 40.000

1 2 0 0 0.000

1 3 0 0 0.000

1 4 0 0 0.000

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>

F

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

To define the codes for VT-100, TV-920, TV-52, FREEDOM 100/110, or FREEDOM 220 terminals, you can use the INIT F command.

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>

The following warning message will be displayed:

WARNING!! ALARM PRIORITIES MAY BE CHANGED. ARE YOU SURE (Y/N)

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

General

PASSWORD NODE CURSOR RIGHT CLEAR SCREEN CURSOR HOME

RAD 0 00000000 00000000 00000000

System

STATION_CLOCK STATION_CLOCK_IF CLOCK_MASTER CLOCK_FBACK REDUNDANCY MATRIX_MODE TS_ALLOC_MODE

1.544 MHz G703 INT NONE NO BIDIRECT DYNAMIC

E1 Port

FRAME LINK MODE SYNC CRC-4 OOS SIGNAL VOICE OOS DATA OOS CGA IDLE_TS_CODE INBAND_MGMT ROUTE_PROT

G732N REGULAR CCITT NO SPACE 00 3E NONE 7E NONE NONE

T1 Port

FRAME LINK MODE SYNC OOS SIGNAL VOICE OOS DATA OOS CGA IDLE_TS_CODE CODE MASK INBAND_MGMT SIGNALING_MODE ROUTE_PROT

ESF REGULAR 62411 SPACE 00 3E NONE 7E B8ZS 000 NONE ROBBED_BIT NONE

HS port

MULT SPEED FIFO_SIZE CLK_MODE CTS

64 NC AUTO DCE ON

DIM port

TX_MODE POLARITY CLK_MODE MAX_DELAY DOWNLOAD MODE

REGULAR NORMAL DCE 64MSEC NO



Table F-1. Default DXC Configuration (Cont.)

Parameter Type Parameter Designation Default Value

IDSL port INTERFACE ACTIVATION

NT-I NONE

SHDSL port

MAX_BW TS0_OVER_DSL SNR_MARGIN_THRESHOLD POWER_BACKOFF STANDARD_COMPATIBLE ATTENUATION_THRESHOLD REM_POWER_BACKOFF REM_ATTENUATION_THRESHOLD REM_ SNR_MARGIN_THRESHOLD

192 LOOPED OFF ENABLE ANNEX_B OFF ENABLE OFF OFF

E3 Port EXT_CLOCK_MODE INT

T3 Port FRAME TYPE EXT_CLOCK_MODE ROUTE_PROT

C_BIT_TX INT NONE

STM-1 Port

CLOCK MODE DCC MODE ROUTING OPERATION MODE CLK PROTOCOL S1 SD THRESHOLD EED THRESHOLD AIS ON FAIL RDI ON FAIL

INT N/A N/A TERM MODE DISABLE 6 3 ENABLE ENABLE

Timeslot Mapping All the timeslots MAX_TS

1:1:1 0

Timeslot Type All the timeslots NC

Supervisory Port

SPEED DATA PARITY INTERFACE PWD LOG_OFF CTS DSR DCD_DELAY POP_ALM AUXILIARY_DEVICE ROUTE_PROT

9600 8 NO DCE NO NO =RTS ON 0 MSEC NO TERMINAL NONE

SNMP Agent SUBNET MASK DEFAULT GATEWAY IP_ADDRESS

000.000.000.000 000.000.000.000 000.000.000.000

Dial-out Port (DTE Interface)


1200 8 NONE 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

To select other values, use the F command.

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>

The following warning message is displayed:

WARNING!! CHANGES WILL BE LOST. ARE YOU SURE (Y/N)

2. To confirm the database loading, type: Y


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)

2. To confirm the loading of the off-line database, type: Y


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>

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>

Note

For E1 and T1 modules, you can define the BERT conditions, and the timeslots on 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.

Syntax and Use

RESET [A]

You are requested to confirm the operation.

Note

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

2. Bring the cursor to the first field to be changed by pressing <Enter>.

3. Set the time about one minute beyond the current time, and then press <Enter> at the correct instant. DXC will display the TIME and DATE fields (note that TIME has changed), followed by the DXC prompt.

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:

PERFORMING SANITY CHECK .... FAILED

followed by the list of the detected sanity errors, and then by the message:

SANITY ERRORS DETECTED. NO HARDWARE UPDATE!!!

If one or more sanity warnings are detected, you will see the message:

PERFORMING SANITY CHECK .... FAILED

followed by the list of the detected sanity warnings, and then by the message:

SANITY WARNINGS DETECTED. CONTINUE (Y/N)?

3. To update despite the warnings, type Y and then press <Enter>. You will see the message:

PERFORMING SANITY CHECK ....

UPDATING SYSTEM’S HARDWARE ....

To cancel the hardware update, type N and then press <Enter>.

If no errors or warnings are detected, DXC displays the message:

PERFORMING SANITY CHECK .... OK

UPDATING SYSTEM’S HARDWARE ....

and the hardware is updated.

Transfer Procedure G-1

Appendix G Downloading of Configuration Files

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.

G.2 Transfer Procedure

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.

Appendix G Downloading of Configuration Files DXC-8R/10A/30/30E Installation and Operation Manual

G-2 Transfer Procedure

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.

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.

Note

DXC-8R/10A/30/30E Installation and Operation Manual Appendix G Downloading of Configuration Files

Transfer Procedure G-3

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.

When done, press the OK button.

Appendix G Downloading of Configuration Files DXC-8R/10A/30/30E Installation and Operation Manual

G-4 Transfer Procedure

H-1

Appendix H Current Versions of DXC Modules Table H-1 appendix lists the power consumption values and the current software and hardware versions for different I/O modules. The software and hardware versions are current to the date of the printed manual.

Table H-1. Power Consumption of DXC Modules

Module HW Rev. SW Ver. PCB Rev. Config. Letter


DCL3 0.1 7.21 0.0 G 1.5A

DE1B 0.3 3.2 0.3 H 0.6A

DT1B 0.3 3.2 0.3 H 0.6A

DHL/E1 0.3 3.1 0.3 F 1.8A

DHL/E1/2W 0.3 3.1 0.3 G 1.2A

DHS/V35 0.3 1.1 1.1 A 0.6A

DHS/530 0.3 1.1 1.1 B 0.5A

DHS/V24 0.3 1.1 1.1 A 0.4A

DHS/X21 0.3 1.1 1.1 B 0.4A

DHS/ETUR 0.3 1.1 1.1 A 0.6A

DHS/ETUB 0.3 1.1 1.1 B 1.7A

DHS/DATA 0.0 0.4 0.1 F 0.6A

D8HS 0.0 0.1 1.0 A 1.9A

DIM/HSSI 1.0 1.7 0.1 F 1.9A

DIM/ETUB 1.0 1.7 0.1 F 1.55A

DIM/ETUR 1.0 1.9 0.1 A 1.3A

Other DIM Versions

1.0 1.7 0.1 F 1.1A

DE3 copper 0.0 2.3 0.0 C 1.2A

DE3 fiber 0.0 2.3 0.0 C 1.4A

DT3 copper 0.0 2.3 0.0 D 1.4A

DT3 fiber 0.0 2.3 0.0 D 1.6A

Appendix H Current Versions of DXC Modules DXC-8R/10A/30/30E Installation and Operation Manual

H-2

Table H-1. Power Consumption of DXC Modules (Cont.)

Module HW Rev. SW Ver. PCB Rev. Config. Letter


D8E1 0.1 1.5 0.1 D 1.4A

D8T1 0.1 1.5 0.1 F 1.4A

D4E1 0.1 1.5 0.1 D 1.14A

D4T1 0.1 1.5 0.1 F 1.14A

D8SL 0.1 0.1 0.0 A 3.7A

D8U 0.0 0.9 0.0 F 1.2A

D16U 0.0 0.9 0.0 F 1.5A

Single-port DFSTM-1 0.0 2.1 1.0 A 3.5A

Dual-port DFSTM-1 0.0 2.1 1.0 A 4.0A

I-1

Index

—A— Alarms

clearing, F-2 defining attributes, 6-16, F-6 defining relay conditions, 6-15, F-10 defining severity, 6-15, F-9 defining traps, 6-15, F-10 displaying, F-35, F-36 general description, 3-53 index of, B-12 inversion, 3-54, 6-16 masking, 3-53, 6-16 processing, 3-53 reporting, 3-53 returning to default values, F-68

ANSI T1.403-1989 statistics, 7-2 Applications

channel relocation and digital cross-connect, 2-7 daisy-chain, 2-16 Fractional STM-1, 2-16 general description, 1-3, 1-4 grooming, 2-17 HDSL transmission, 2-9 high-density module, 2-12 inverse multiplexing, 2-19 ISDN 'U' interface, 2-10 media converter, 2-5 multidrop (broadcast), 2-8 providing fractional T1 and E1 access point, 2-7 SHDSL, 2-15 signal monitoring, 2-14 T1/E1 converter, 2-4 T1/E1 drop-&-insert, 2-8 transport of T1 frame over E1 facilities, 2-6 typical local or remote distribution, 2-18

AT&T Pub. 54016 statistics, F-47 AUTOBAUD function, 3-44

—B— BER Testing

DE1B, DT1B, D4E1, D8E1, D4T1, D8T1, DHL modules, 7-32

defining parameters, F-11 DHS and D8HS modules, 7-32 DIM module, 7-33 displaying results, F-36, F-37 general, 7-31

—C— CEPT, E-1 Channel relocation and digital cross-connect

applications, 2-7 Clear to Send, 3-43 Commands

BYE, F-2 CHECK DB, F-2 CLR ALM, F-2 CLR LOOP, F-3 command protocol, 5-12 DATE, F-4 DEF AGENT, F-4 DEF ALM ATTRIB, F-6 DEF AP, F-9 DEF AP ALL, F-9 DEF AR, F-10 DEF BERT, F-11 DEF CALL, F-13 DEF CON, F-40 DEF DCL FLIP, F-16 DEF MANAGER LIST, F-17 DEF NAME, F-18 DEF NP, F-19 DEF PORT, F-21 DEF PROMPT, F-22 DEF PWD, F-22 DEF RDN, F-23 DEF SP, F-25 DEF SYS, F-28 DEF TEST PORT, F-32 DEF TS, F-34 DSP AGENT, F-35 DSP ALM, F-35, F-36 DSP BERT, F-36, F-37 DSP BUS, F-38 DSP FDL, F-42 DSP FLIP, F-44 DSP HDR TST, F-45 DSP MANAGER LIST, F-46 DSP PM, F-47 DSP REM AGENT, F-51 DSP REV, F-52 DSP ST, F-53 DSP ST MANAGEMENT, F-56 DSP ST RDN, F-60 DSP ST SYS, F-61 EXIT, F-66 F, F-66

Index DXC-8R/10A/30/30E Installation and Operation Manual

I-2

FORCE ON LINE, F-67 general options, 5-13 HELP, F-67 index of, 5-13, F-67 INIT AP, F-68 INIT DB, F-68 INIT F, F-71 LOAD DB, F-71 LOAD HW, F-72 LOAD OFFLINE DB, F-72 LOOP, F-73 notational conventions, F-1 RESET, F-74 RESET I/O, F-75 TIME, F-75 UPDATE DB, F-75

Configuration Files uploading to management station, G-3

Configuring ports, 6-7, F-21 system, 6-5, F-28

Control session exiting, 5-20 starting, 5-19

Control signals Clear to Send, 3-43 Data Carrier Detect, 3-43 Data Set Ready, 3-43 Data Terminal Ready, 3-43 Request to Send, 3-43

—D— Daisy-chain application, 2-16 Data Carrier Detect, 3-43 Data Set Ready, 3-43 Data Terminal Ready, 3-43 Database

comparing with hardware configuration, F-72 downloading configuration files, 3-54 loading default values, F-68 loading off-line DCL.3 configuration, F-72 loading to the editing buffer, F-71 sanity check, F-2 saving configuration, 6-17 updating from the editing buffer, F-75 uploading configuration files, 3-54, G-3

Date, setting, F-4 DCL.3 module

configuring for Telnet and SNMP access, 5-10 connectors wiring, A-1, A-4 defining redundancy parameters, 6-12, F-16 displaying flipping cause, F-44 Ethernet port, C-7 handling of management traffic over IP, C-6 installing in DXC-30E, 4-33 loading off-line module configuration, F-72 main cross-connect matrix, 3-4 redundancy control algorithm, 3-34 redundancy function, 3-33

DXC data bus displaying timeslot utilization, F-38

DXC system block diagram, 3-3 bus functions, 3-2 configuring the ports, 6-7 functional description, 3-2 main cross-connect matrix, 3-4 main features, 1-1 management, 3-40 overview, 1-1 preliminary configuration, 5-7 technical specifications, 1-27

DXC-10A connecting management port, 4-8 installing the enclosure, 4-39 physical description, 4-36 site requirements, 4-3

DXC-30 connecting management port, 4-8 general description, 1-7 installing DPS module, 4-12 installing the enclosure, 4-11 operating the enclosure, 4-25 physical description, 4-9 site requirements, 4-3

DXC-30E connecting management port, 4-8 general description, 1-9 installing DCL.3 module, 4-33 installing the enclosure, 4-29 operating the enclosure, 4-35 physical description, 4-27 site requirements, 4-3

DXC-8R connecting management port, 4-8 general description, 1-11 installing the enclosure, 4-44 physical description, 4-41 site requirements, 4-3

—E— E1 environment

64 kbps channel characteristics, E-4 alarm conditions, E-4 CRC-4 error detection, E-3 line signal, E-3 line statistics, E-3 multiframe types, E-2 signal structure, E-1 timeslot 0, E-2

E1/T1 converter application, 2-4 E3 environment

line alarm conditions, E-10 line signal, E-10 signal structure, E-8

Error messages, B-1 Exiting control session, F-66, F-75

DXC-8R/10A/30/30E Installation and Operation Manual Index

I-3

—F— FDL messages, F-42 Flip, criteria, 3-38 Fractional STM-1 application, 2-16 Fractional T1 and E1 access point application, 2-7

—G— Grooming application, 2-17

—H— Hardware test results, F-45 HDSL transmission applications, 2-9 High-density module applications, 2-12

—I— Inband alarm indications, 3-24

E1/T1 OOS events, 3-25 E1/T1 ports link alarms, 3-26 E3/T3 link alarms, 3-26 E3/T3 OOS events, 3-26

Installing new software releases, D-1 Interface

defining port parameters, F-21 DS1 internal port (T3 module), 3-13 E1 electrical port, 3-11 E1 fiber-optic port, 3-12 E1 internal port (E3 module), 3-13 E3 electrical port, 3-14 E3 fiber-optic port, 3-14 HDSL system, 3-16 high-speed data port, 3-17 ISDN 'U' port, 3-18 SHDSL, 3-17 STM-1 port, 3-15 T1 electrical port, 3-13 T1 fiber-optic port, 3-13 T3 electrical port, 3-14 T3 fiber-optic port, 3-14

Inverse multiplexing, 3-28 clock waveform characteristics, 3-29 DIM E1 interface characteristics, 3-31 DIM synchronous data interface characteristics, 3-30 main principles, 3-28 typical applications, 2-19

IP environment, C-4 IP address structure, C-4 net and subnet masks, C-5 selecting IP address, C-6

ISDN 'U' interface applications, 2-10 ITU-T Rec. G.802, E-8

—L— Link alarms, 3-24 Loopback

activating, F-73 clearing, F-3 D8SL modules, inband code-activated on internal

port, 7-22

D8SL modules, local on external port, 7-20 D8SL modules, remote loopback on remote ASMi-52,

7-22 D8SL modules, remote on external port, 7-21 D8SL modules, remote timeslot on internal port, 7-23 D8U, D16U modules, local, 7-18 D8U, D16U modules, remote, 7-19 D8U, D16U modules, remote loopback on remote

ASMi-31, 7-19 DFSTM-1 module, local internal E1 port, 7-28 DFSTM-1 module, local internal VC-12 port, 7-29 DFSTM-1 module, local STM-1 port, 7-27 DFSTM-1 module, remote internal E1 port, 7-28 DFSTM-1 module, remote STM-1 port, 7-27 DHL module, HDSL_INBAND, 7-17 DHL module, L LINE, 7-16 DHL module, L PORT, 7-16 DHS or D8HS module, local, 7-12 DHS or D8HS module, remote, 7-13 DIM module, local, 7-14 DIM module, remote, 7-14 E1/T1 module, inband, 7-11 E1/T1 module, local, 7-10 E1/T1 module, remote, 7-10 E1/T1 module, TS REM, 7-12 E1/T1 module, TX LLB, 7-12 E1/T1 module, TX PLB, 7-12 E3 module, local, 7-23 E3 module, local internal port, 7-24 E3 module, remote, 7-24 FDL LLB, 7-30 general description, 3-51 Network LLB, 7-30 Network PLB, 7-30 T3 module, local, 7-25 T3 module, local internal port, 7-26 T3 module, network-activated line, 7-31 T3 module, remote, 7-25

—M— Management

combining inband and out-of-band options, 3-48 configuration options, 5-2 connecting a supervisory terminal, 5-3 connecting an alarm relay terminal, 5-4 connecting an SNMP management station, 5-6 connecting Telnet hosts, 5-5 connection methods, 5-3 displaying status, F-56 inband, 3-45 out-of-band, 3-45, C-6 power-up with supervisory terminal connected, 5-18 preparing new configuration parameters, 5-11 SNMP and Telnet access options, 3-45 supervision language syntax, 5-12

Management Information Base (MIB), C-2 Media converter application, 2-5 MIB, C-2 Multidrop (broadcast) applications, 2-8


I-4

—N— Network port

AUTOBAUD function, 3-44 connecting a dial-up modem, 5-5 connecting an alarm relay terminal, 5-4 connector wiring, A-3 defining call-out parameters, 6-14, F-13 defining parameters, 5-9, 6-14, F-19 general description, 3-42 handshaking with dial-up modem, 3-44 interface characteristics, 5-5 making connections, 4-8, 5-6

Node name, F-18

—O— OOS events, 3-24

—P— Password, F-22

selecting default password, 5-7 Payload Routing, 3-2 Performance monitoring, 7-1

ANSI T1.403-1989 statistics, 7-2 CRC-4 disabled, 7-4 CRC-4 enabled, 7-3 E1 ports, 7-3 E3/T3 ports, 7-4 ESF framing, 7-2 SF framing, 7-3 SHDSL links, 7-6 STM-1 links, 7-8 T1 ports, 7-1

Power supply considerations, 4-4

—R— Redundancy

configuring DCL.3 modules redundancy, 6-12 DCL.3 modules, 3-33, F-16 defining parameters, F-23 displaying module or pair parameters, F-60 dual-slot mode, configuring, 6-11 dual-slot protection mode, 3-38 flip criteria, 3-38 handling of exceptional conditions in DCL.2 modules,

3-35 I/O modules, 3-35 single-slot protection mode, configuring, 6-10 Y-cable mode, 3-37 Y-cable mode, forcing online module, F-67 Y-cable redundancy, configuring, 6-11

Request to Send, 3-43 Reset

DXC system, F-74 I/O module, F-75

Routing, 3-21 alternate T1 mode, 3-23, 6-9 bidirectional/unidirectional modes, 3-21 E3/T3 modules, 3-4 main cross-connect matrix, 3-4, 3-21

regular mode, 3-21 sequential 'bundle' mode, 3-22, 6-8 transparent mode, 3-22

—S— SDH environment

AU pointers, E-25 Frame, E-19 MSOH, E-25 Pointers, E-21 principles, E-17 Response to abnormal conditions, E-36 RSOH, E-24 SDH maintenance signals, E-34 SDH overhead data types, E-22 SDH signals structure, E-18 STM-1 frame structure, E-20 Tributary unit frame structure, E-28 Tributary unit types, E-28 VC assembly/disassembly, E-20 VC-4 path overhead functions, E-26

SHDSL application, 2-15 Signal monitoring application, 2-14 SNMP management

access options, 3-45 defining agent parameters, F-4 defining management stations, F-17 displaying agent parameters, F-35 displaying management stations, F-46 displaying remote agents, F-51 environment description, C-1 Management Information Base (MIB), C-2 managing SNMP communities, C-3 operation types, C-2 out-of-band, C-6 preliminary configuration, 5-9 preventing access to the other networks, C-9 sending traps, F-17

Software installation, 3-54, D-1 cold (local), D-2 warm (upgrading), D-3

Statistics Collection, 3-52

Status information, F-53 DCL.2 module, F-54 I/O module, F-55 installed I/O modules, F-61 system state, F-61

Supervisory port AUTOBAUD function, 3-44 connecting via a modem link, 5-4 connector wiring, A-1 defining parameters, 5-8, F-25 defining prompt, F-22 general description, 3-42 interface characteristics, 5-3 making connections, 4-8, 5-3 selecting default parameters, 5-7

Supervisory terminal

DXC-8R/10A/30/30E Installation and Operation Manual Index

I-5

control session, ending, 5-20 control session, starting, 5-19 display codes, defining, F-66 display codes, resetting, F-71 general description, 3-41 handshaking, 3-42

—T— T1 environment

64 kbps channel characteristics, E-7 alarm conditions, E-6 ITU-T Rec. G.802, E-8 line signal, E-6 signal structure, E-5

T1/E1 converter application, 2-4 T1/E1 drop-&-insert application, 2-8 T3 environment

6.312 Mbps G.747 tributary, E-14 asynchronous DS3 C-bit parity application, E-15 DS3 alarm and status signals, E-16 DS3 line signal, E-16 Standard DS2 tributary. synchronous DS3 M13 multiplex application, E-15 T3 signal structure, E-10

Telnet management access options, 3-45

connecting hosts, 5-5 preliminary configuration, 5-9

Test port configuration parameters, F-32

TFTP protocol, G-1 Time, setting, F-75 Timeslot

routing, 3-21 Timeslot Allocation

Automatic Algorithm, 3-5 Dynamic, 3-8 Static, 3-10

Timeslots defining destination and type, F-34 displaying connection table, F-40

Timing DXC system master timing, 3-20 external E1/T1 port, 3-19 external E3/T3 port, 3-19 high-speed data port, 3-19 internal E1/DS1 port, 3-19 ISDN, 3-20

Transporting T1 frame over E1 transmission facilities, 2-6


I-6

24 Raoul Wallenberg St., Tel Aviv 69719, IsraelTel: +972-3-6458181, Fax: +972-3-6483331, +972-3-6498250E-mail: , Web site:

Customer Response Form RAD Data Communications would like your help in improving its product documentation. Please complete and return this form by mail or by fax or send us an e-mail with your comments. Thank you for your assistance!

Manual Name: ______________________________________________________________

Publication Number: __________________________________________________________ Please grade the manual according to the following factors:

Excellent Good Fair Poor Very Poor

Installation instructions Operating instructions Manual organization Illustrations The manual as a whole

What did you like about the manual? ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________

[email protected] www.rad.com

DXC-8R/10A/30/30E

772-203-06/04


http://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. _________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

Please add any comments or suggestions you may have. _________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

You are: Distributor

End user

VAR

Other ________________________

Who is your distributor? _______________________________

Your name and company: ___________________________________________________________

Job title: __________________________________________________________________________

Address: __________________________________________________________________________

Direct telephone number and extension: _______________________________________________

Fax number: ______________________________________________________________________

E-mail: _____________________________________________________________________

900 Corporate Drive, Mahwah, N.J. 07430, Tel: (201) 529-1100

24 Raoul Wallenberg Street, Tel Aviv 69719, Israel, Tel: 972-3-6458181

U.S. HEADQUARTERS:

INTERNATIONAL HEADQUARTERS:

Publication No. 772-203-06/04

www.rad.com

Fax: 972-3-6498250, 972-3-6474436, Email: [email protected]

Toll Free: 1-800-444-7234, Fax: (201) 529-5777, Email: [email protected]

http://www.rad.com/



DXC-fm

Documents

Transcript of DXC-fm