ALCATEL-LUCENT 90-2904-01

2902 MainStreet Network Termination Unit | Release 1.0 H TECHNICAL PRACTICES Alcatel assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. Alcatel, the Alcatel logo, MainStreet, and Newbridge are registered trademarks of Alcatel. All other trademarks are the property of their respective owners. Copyright 2002 Alcatel. All rights reserved. Disclaimers Alcatel products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, licence or other distribution of the products for any such application without the prior written consent of Alcatel, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-Alcatel products. Please note that this information is provided as a courtesy to assist you. While Alcatel tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel product and contact the supplier for confirmation. Alcatel assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel products. Alcatel has made reasonable efforts to ensure that the 2902 MainStreet Network Termination Unit, Release 1.0, complies in all material respects with the "Referenced Detailed Functional Specification for Newbridge Product Date Compliance" (for Load H and beyond). To obtain this document and other information related to Year 2000 Date Compliance, visit the Alcatel Year 2000 Date Compliance website at the URL: http://www.cid.alcatel.com/year2000/index.html However, this does not constitute a representation or warranty. The warranties provided for Alcatel products, if any, are set forth in contractual documentation entered into by Alcatel and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail. PRINTED ON RECYCLED PAPER Preface This document describes the technical practices for the 2902 MainStreet Network Termination Unit, Release 1, software generic 82211. It includes the following volumes. • Installation describes how to install and ground a 2902 MainStreet system, connect it to data equipment, primary rate links and node management equipment, and how to power it up. • Configuration provides the instructions on how to configure the node, its modules and its connections. • Maintenance explains maintenance functions and how to perform them. • The glossary expands or defines acronyms and abbreviations. • The index lists entries for Installation, Configuration and Maintenance. Some systems do not include all the components or support all the features described in this documentation. The components and features supported depend on the components and system you have ordered and the system software generic release. Conventions This section describes the text conventions used throughout this document. 2902 MainStreet Technical Practices iii May 2002 90-2906-01 Preface Special information The following conventions are used to draw your attention to special information. Danger — Danger means that the described activity or situation may cause personal injury. Warning — Warning means that the described activity or situation may or will cause equipment damage. Caution — Caution means that the described activity or situation may or will cause service interruption. Note — Notes provide supplementary information. Procedure 1 Step procedure conventions Step procedures provide instructions to perform a task. Step procedures may consist of options and substeps. The following example outlines step procedure conventions. 1 Steps are denoted by arabic numerals and describe actions that must be performed. Complete each step in order. This step has substeps. i Substeps are denoted by roman numerals and detail the actions involved in a complex step. Complete each substep in order. ii At least two substeps appear. 2 This step has options. a Options are denoted by letters and are conditional actions that depend on your system requirements. Perform only the applicable option. i Options may contain substeps. ii At least two substeps appear. b At least two options appear. iv 2902 MainStreet Technical Practices 90-2906-01 May 2002 Mandatory regulations The sections that follow outline the mandatory regulations governing the installation and operation of the 2902 MainStreet Network Termination Unit. Adherence to these instructions is necessary to ensure regulatory compliance. 2902 MainStreet Technical Practices v May 2002 90-2906-01 Mandatory regulations General requirements Product safety This equipment must be configured only with those assemblies specified in the technical practices and must be mounted in the locations specified. Danger — There is a danger of explosion if the battery used in this device is incorrectly replaced. Do not attempt battery replacement. Return the equipment to your supplier for servicing when or if a battery fault is suspected to be the cause of the equipment failure. Where the law prohibits, do not discard the battery, or the equipment with the battery; return it to your supplier for proper disposal. The battery may present a fire or chemical burn hazard if mishandled. Do not recharge, disassemble, heat above 100°C (212°F) or incinerate. Warning 1 — This unit contains no user-serviceable parts. Refer servicing to qualified personnel. Warning 2 — This equipment is Class I type and must be permanently earthed for protection and for functional purposes. For safe operation and servicing, the ac outlet must be installed near the equipment and must be readily accessible. Use the appropriate ac power cord and plug, as required by national standards. Warning 3 — The equipment must be earthed. Where protection of the user relies on a protective earth derived from a plug (for example, the ac mains plug on the 2902 MainStreet unit), the connection to the public network must be unplugged before the earth is disconnected. The connection to the network must not be hard-wired. Warning 4 — The power supply does not contain any field-serviceable parts. Return it to the manufacturer for servicing. Warning 5 — The unit uses a slow-blow type fuse with a 2 A, 250 V rating (Sheet No V & Symbol T as per IEC60127). To ensure continued fire protection, the replacement fuse must have the same specifications as the original fuse. Caution — To prevent accidental shorting of the modules, they must be correctly aligned between the guides before insertion. Prevention of unauthorized access The 2902 MainStreet system is intended to be accessible only to authorized personnel. This apparatus must be installed in a restricted access location or similar environment, so that unauthorized user access is prevented. vi 2902 MainStreet Technical Practices 90-2906-01 May 2002 Mandatory regulations Earths The 2902 MainStreet system has three types of earth: • telecom safety earth (also known as functional earth) • protective earth • EDG (energy dumping ground) The telecom safety earth connection is through pins designated as signal ground. The telecom safety earth connector is located on the rear panel of the unit. See section 4.1 for specific instructions. A green- and yellow-colored earth wire must be connected from the site equivalent of the ac earth in accordance with IEEE Wiring Regulations (16th edition) and HD384. This connection is made to the protective earth ground stud located on the rear panel of the unit; see section 4.1 for specific instructions. The protective earth is also carried by the mains plug and socket (for ac systems only). The EDG connection is located on the rear panel of the unit. The wire used for telecom safety earth, protective earth and EDG should be a 2 minimum of 1.5 mm (AWG 16), green and yellow in color, and of sufficient length to connect the building earth point to the unit. See section 4.1 for specific instructions. Equipment interconnection points The interconnection points are defined as Safety Extra Low Voltage (SELV) (all connectors on rear panel, except P1 and P2 optical connectors). Connect SELV circuits on this equipment only to other circuits complying with the requirements of SELV circuits as defined in CSA C22.2 No 60950, UL60950, EN60950, AS/NZS 3260 and IEC60950. Laser interface The 2902 MainStreet unit uses a fiber-optic communications method and is a CLASS 1 LASER PRODUCT. Only trained, qualified service personnel thoroughly familiar with laser radiation hazards should install or remove the fiber-optic cables and cards in this system. Electromagnetic compatibility EMC compliance requires the use of: • ferrite beads on all interface cables • screened interface cables for Class B compliance All Alcatel cables are shipped with the necessary special accessories required for regulatory compliance. 2902 MainStreet Technical Practices vii May 2002 90-2906-01 Mandatory regulations Install the appropriate ferrite beads as indicated in Table 1, and use shielded cables for Class B installations. Ferrite beads must be attached at both ends of the cable, as close as possible to the connector headshell, and secured with tie wraps. In addition, the appropriate size must be selected to fit the cable diameter (see Figure 1). Table 1 Ferrite beads for cables Commercial part number Cable diameter Steward 28A2025-0A2 5.08 to 6.35 mm Steward 28A2029-0A2 7.62 to 9.91 mm Steward 28A2024-0A2 9.53 to 12.70 mm Figure 1 Ferrite beads and tie wraps on cables Connector Cable ties Cable ties Connector Ferrite bead Ferrite bead 16521 Product certification Note — Some products described in this manual may not comply with the requirements of all markets where this product is sold, and may only be placed on the market and installed where appropriately certified to local requirements. viii 2902 MainStreet Technical Practices 90-2906-01 May 2002 Mandatory regulations European regulations The unit has been CE-marked in accordance with the requirements of European Directive 1999/5/EC, the Radio and Telecommunications Terminal Equipment Directive. This product complies with the requirements of European Directive 73/23/ECC, 89/336/ECC and 91/263/ECC. See the “Product safety” and “Electromagnetic compatibility” sections in “General requirements” for installation requirements for regulatory approvals. Telecoms The E1 primary interface card (120 Ω) meets the requirements of European Directive 91/263/EEC. United Kingdom regulations This apparatus is intended to be accessible only to authorized personnel. This apparatus must be installed in a locked room or similar environment, such that unauthorized user access is prevented. Failure to prevent such user access will invalidate any approval given to this apparatus. Power supply cord wiring The instructions for power supply cord and plug wiring are no longer mandatory. If this information is required, consult the “Australian regulations” section for details, since both countries have identical power supply cord and plug wiring requirements. Norway regulations Apparatus maa tilkobles jordet stikkontakt. Jordet Stikkontakt skal benyttes naar apparatet tilkobles datanett. The equipment must be connected to an earthed mains socket-outlet. An earthed mains socket-outlet must be used when the equipment is connected to a data network. Sweden regulations Apparaten skall anslutas till jordat uttag nar den anslutas till ett natverk. The product should be connected to a mains socket-outlet with earthing contact. Switzerland regulations The mains plug must comply with SEV/ASE 1011. 2902 MainStreet Technical Practices ix May 2002 90-2906-01 Mandatory regulations Australian regulations Power supply cord wiring The cores in this mains lead are colored in accordance with the following code: • green and yellow: earth • blue: neutral • brown: live As the colors of the cores in the mains lead of this equipment may not correspond with the colored markings identifying the terminals in the plug, proceed as follows if power supply cord rewiring is required. • The core that is colored green and yellow must be connected to the terminal in the plug that is marked with the letter E or by the earth symbol, or colored green and yellow. • The core that is colored blue must be connected to the terminal that is marked with the letter N or colored black. • The core that is colored brown must be connected to the terminal that is marked with the letter L or colored red. Warning — This equipment must be earthed. x 2902 MainStreet Technical Practices 90-2906-01 May 2002 Contents Preface Mandatory regulations 1 — Introduction 1-1 1.1 Product overview ..............................................................................................1-2 1.2 Physical components ........................................................................................1-3 1.3 HDSL LIM overview .......................................................................................... 1-6 1.4 Optical LIM overview ........................................................................................ 1-8 1.5 Site selection ....................................................................................................1-9 1.6 Installation summary .......................................................................................1-11 1.7 Installation tools and hardware required ......................................................... 1-11 2 — Unpacking and inspecting the shipment 2-1 2.1 Antistatic precautions ........................................................................................2-2 2.2 Unpacking and inspecting the shipment ........................................................... 2-2 2.3 Performing a startup test .................................................................................. 2-4 2.4 Repacking the shipment ................................................................................... 2-4 3 — Mounting the unit 3-1 3.1 Setting up the unit on a desk ............................................................................ 3-2 3.2 Mounting the unit in a rack ................................................................................ 3-2 3.3 Mounting the unit in a slide assembly ............................................................... 3-3 2902 MainStreet Technical Practices xi May 2002 90-2906-01 Contents 4 — Ground and power connections 4-1 4.1 Ground connections ..........................................................................................4-2 4.2 Power connections ...........................................................................................4-4 4.3 Securing slide assembly cable connections ..................................................... 4-4 4.4 Startup diagnostics ...........................................................................................4-6 5 — Installing and removing modules 5-1 5.1 Control card modules ........................................................................................5-2 5.2 Opening the unit ............................................................................................... 5-2 5.3 Installing and removing primary rate modules .................................................. 5-3 5.4 Installing and removing data interface modules ............................................. 5-10 5.5 Installing and removing personality modules .................................................. 5-11 5.6 Replacing EPROMs ........................................................................................5-12 6 — Connecting to the network 6-1 6.1 Primary rate connections .................................................................................. 6-2 7 — Connecting to data devices 7-1 7.1 Data circuit connections ....................................................................................7-2 7.2 Assembling an adapter for EIA/TIA-232 connections ....................................... 7-9 7.3 DB25-to-M34 cable pin and signal assignment .............................................. 7-20 8 — Connecting node management equipment 8-1 8.1 Node management equipment connections ..................................................... 8-2 9 — Connecting to external alarm equipment 9-1 9.1 External alarm connections .............................................................................. 9-2 10 — Node management 10-1 10.1 Node management overview .......................................................................... 10-2 10.2 Logging in to the NMTI ................................................................................... 10-2 10.3 NMTI screen display ....................................................................................... 10-4 10.4 NMTI main menus ..........................................................................................10-6 10.5 Softkey menus ................................................................................................10-7 10.6 Logging out of the NMTI ................................................................................. 10-9 11 — Node parameters 11-1 11.1 System serial port parameters ........................................................................ 11-2 11.2 Date and time ................................................................................................. 11-6 11.3 Node number and node name ........................................................................ 11-7 11.4 Network Operations Center number ............................................................... 11-8 11.5 Access levels ..................................................................................................11-9 11.6 Passwords ....................................................................................................11-13 11.7 Viewing node parameters .............................................................................11-14 xii 2902 MainStreet Technical Practices 90-2906-01 May 2002 Contents 12 — Module position and circuit configuration 12-1 12.1 Module position and circuit identifiers ............................................................. 12-2 12.2 Module position configuration ......................................................................... 12-3 12.3 Module position displays ................................................................................. 12-4 12.4 Naming a module position .............................................................................. 12-8 12.5 Naming a circuit .............................................................................................. 12-8 12.6 Quick circuit configurations ............................................................................. 12-8 12.7 Viewing circuit status ......................................................................................12-9 13 — System timing and timing sources 13-1 13.1 System timing .................................................................................................13-2 13.2 Timing sources ...............................................................................................13-3 13.3 Types of synchronization ................................................................................ 13-6 13.4 Class number ..................................................................................................13-7 13.5 Failure threshold .............................................................................................13-8 13.6 Recovery condition .........................................................................................13-9 13.7 Intra- and inter-sector links .......................................................................... 13-10 13.8 Displaying the network configuration ........................................................... 13-12 14 — CPSS 14-1 14.1 CPSS overview ...............................................................................................14-2 14.2 CPSS channel connections ............................................................................14-2 15 — E1 module operating parameters 15-1 15.1 E1 module overview ....................................................................................... 15-2 15.2 Network connectors ........................................................................................15-3 15.3 E1 framing format ........................................................................................... 15-4 15.4 Signal earthing (E1 G.703 LIM only) ............................................................... 15-4 15.5 Master/slave operation (E1 HDSL and Optical LIMs only) ............................. 15-6 15.6 Trunk conditioning ..........................................................................................15-7 15.7 Fault classes .................................................................................................15-12 15.8 Alarm declaration and clearing times ............................................................ 15-13 15.9 E1 statistics ...................................................................................................15-14 16 — E1 circuit operating parameters 16-1 16.1 E1 signaling type ............................................................................................16-2 16.2 E1 fault signaling ............................................................................................ 16-2 17 — DNIC and 2B1Q modules 17-1 17.1 Understanding DNIC and 2B1Q modules ....................................................... 17-2 17.2 DNIC and 2B1Q circuit configuration and operating parameters .................... 17-2 17.3 Device mode ...................................................................................................17-3 17.4 Device gender .................................................................................................17-4 17.5 Duplex method ............................................................................................... 17-5 17.6 RTS/CTS delay ...............................................................................................17-5 17.7 Control signals ................................................................................................17-6 17.8 Data structure (asynchronous only) ................................................................ 17-7 2902 MainStreet Technical Practices xiii May 2002 90-2906-01 Contents 17.9 Clocking (synchronous only) ........................................................................... 17-9 17.10 Multidrop data bridge .................................................................................... 17-12 17.11 Super-rate configuration for DNIC or 2B1Q modules ................................... 17-13 17.12 Loss-of-synchronization debounce time (DNIC only) ................................... 17-14 18 — RS-232 DCM 18-1 18.1 Understanding the RS-232 DCM .................................................................... 18-2 18.2 RS-232 DCM circuit operating parameters .................................................... 18-2 18.3 Device mode ...................................................................................................18-3 18.4 Device gender .................................................................................................18-3 18.5 Full duplex ......................................................................................................18-4 18.6 RTS/CTS delay ...............................................................................................18-4 18.7 Control signals ................................................................................................18-5 18.8 Data structure (asynchronous only) ................................................................ 18-6 18.9 Clocking (synchronous only) ........................................................................... 18-7 18.10 Multidrop data bridge ...................................................................................... 18-9 19 — X.21 and V.35 DCMs 19-1 19.1 Understanding X.21 and V.35 DCMs .............................................................. 19-2 19.2 X.21 and V.35 circuit operating parameters ................................................... 19-2 19.3 Device mode ...................................................................................................19-4 19.4 Device gender .................................................................................................19-4 19.5 Duplex method ................................................................................................19-5 19.6 RTS/CTS delay ...............................................................................................19-6 19.7 Control signals ................................................................................................19-7 19.8 Data structure (asynchronous only) ................................................................ 19-8 19.9 Clocking (synchronous only) ........................................................................... 19-9 19.10 Multidrop data bridge .................................................................................... 19-12 19.11 Super-rate configuration for the X.21 and V.35 DCMs ................................. 19-13 20 — Codirectional DCM 20-1 20.1 Understanding the Codirectional DCM ........................................................... 20-2 20.2 Codirectional DCM Module and circuit parameters ........................................ 20-2 20.3 Trunk conditioning ..........................................................................................20-3 20.4 Alarm times .....................................................................................................20-3 20.5 8 kHz timing ................................................................................................... 20-4 20.6 All Ones alarm indication signal ...................................................................... 20-4 21 — Transparent rate adaption 21-1 21.1 Rate adaption overview ..................................................................................21-2 21.2 Transparent rate adaption overview ............................................................... 21-2 21.3 Transport bandwidth .......................................................................................21-3 21.4 Transport position ...........................................................................................21-5 22 — HCM rate adaption 22-1 22.1 Rate adaption overview ..................................................................................22-2 22.2 HCM rate adaption overview .......................................................................... 22-2 xiv 2902 MainStreet Technical Practices 90-2906-01 May 2002 Contents 22.3 Transport bandwidth .......................................................................................22-3 22.4 Transport position ...........................................................................................22-5 22.5 Signaling and the signaling bit stream ............................................................ 22-5 22.6 Interface speed ...............................................................................................22-6 22.7 Data position ...................................................................................................22-8 23 — Cross-connecting circuits 23-1 23.1 Types of cross-connections ............................................................................ 23-2 23.2 Simple connections .........................................................................................23-2 23.3 Connecting super-rate circuits ........................................................................ 23-4 23.4 Circuit connections display .............................................................................23-5 23.5 Protecting connections (RAPID protection switching) .................................... 23-5 23.6 Disconnecting connections ...........................................................................23-10 24 — Visual indicators 24-1 24.1 LEDs ...............................................................................................................24-2 24.2 Front panel LEDs ............................................................................................ 24-2 24.3 Rear panel LEDs ............................................................................................ 24-4 24.4 Interface module LEDs ................................................................................... 24-6 25 — Alarms 25-1 25.1 Alarms and alarm queues ............................................................................... 25-2 25.2 Viewing alarm queues ....................................................................................25-4 25.3 Acknowledging alarms ....................................................................................25-6 25.4 Deleting alarms ...............................................................................................25-7 25.5 Reclassifying configurable alarms ................................................................. 25-7 25.6 Logging alarms ...............................................................................................25-9 25.7 External alarms .............................................................................................25-10 26 — System diagnostics 26-1 26.1 Diagnostic tests ..............................................................................................26-2 26.2 Background diagnostics ..................................................................................26-3 26.3 Directed diagnostics .......................................................................................26-4 26.4 Viewing diagnostics ........................................................................................26-5 26.5 Busy-out circuits .............................................................................................26-6 26.6 Signaling leads ...............................................................................................26-7 26.7 Displaying module and Control card maintenance information .................... 26-10 26.8 Resetting a module or the Control card ........................................................ 26-10 27 — Loopbacks 27-1 27.1 Using loopbacks .............................................................................................27-2 27.2 2B1Q circuit loopbacks ...................................................................................27-3 27.3 DNIC circuit loopbacks ...................................................................................27-6 27.4 Data circuit loopbacks ...................................................................................27-11 27.5 Primary rate circuit loopbacks ....................................................................... 27-13 27.6 Primary rate link loopbacks ........................................................................... 27-15 2902 MainStreet Technical Practices xv May 2002 90-2906-01 Contents 28 — Statistics 28-1 28.1 Synchronization statistics ...............................................................................28-2 28.2 FAS and CRC4 statistics ................................................................................ 28-3 28.3 Codirectional DCM quality statistics ............................................................... 28-7 29 — CPSS maintenance 29-1 29.1 Routing information .........................................................................................29-2 29.2 CPSS grooming ..............................................................................................29-5 30 — Database management 30-1 30.1 Backing up, verifying, and restoring the configuration database .................... 30-2 30.2 Viewing and resetting the nonvolatile memory ............................................... 30-5 31 — Hardware maintenance procedures 31-1 31.1 Measuring the power rails ............................................................................... 31-2 31.2 Testing and replacing the fuse ........................................................................ 31-3 32 — Primary rate link bypass 32-1 32.1 Initiating a primary rate link bypass ................................................................ 32-2 Glossary lndex xvi 2902 MainStreet Technical Practices 90-2906-01 May 2002 1 — Introduction 1.1 Product overview 1-2 1.2 Physical components 1-3 1.3 HDSL LIM overview 1-6 1.4 Optical LIM overview 1-8 1.5 Site selection 1-9 1.6 Installation summary 1-11 1.7 Installation tools and hardware required 1-11 2902 MainStreet Technical Practices 1-1 May 2002 90-2906-01 System Status Out of Sync 2 Event Status Out of Sync 1 Network Termination Unit Power Processor 2902 MainStreet 1 — Introduction 1.1 Product overview The 2902 MainStreet Network Termination Unit is a high-speed NTU for data devices. The 2902 MainStreet unit also provides CEPT voice bypass capability. It supports two E1 primary rate interfaces and two data interface modules. HDSL technology allows connection to E1 lines using twisted copper pairs, without repeaters. The 2902 MainStreet unit gives customers access to public and private switched networks. It can be used in point-to-point, or drop and insert configurations. The unit also features circuit protection switching, bypass operation, subrate and super-rate connections, system diagnostics, statistics collection, line and circuit maintenance testing, alarm collection, and database management functions. The E1 HDSL and E1 Optical LIMs allow the 2902 MainStreet unit to serve as a high-speed NTU, providing low-cost, high-speed X.21 or V.35 circuits for LAN interconnection. E1 G.703 LIMs can also provide high-speed connections to an E1 network. Additionally, an E1 G.703 LIM can be used as a tributary connection to a PBX, allowing voice bypass connections to an E1 HDSL, E1 Optical, or another E1 G.703 LIM. Figure 1-1 shows the exterior of a desktop unit. The unit can be placed on a desktop or, with the appropriate hardware, adapted for a rack. Physical connections to primary rate lines can be made through BNC or RJ45 connectors. Figure 1-1 2902 MainStreet Network Termination Unit 8827 The system uses customer-installed modules to connect to E1 lines and data devices. E1 lines connect to a 2902 MainStreet unit through the following line interface modules: • E1 G.703 LIM • E1 HDSL LIM • E1 HDSL LIM2 • E1 Optical LIM 1-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 Loop Status U 1 2 Display Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 P1 P2 I O EDG Sig/Gnd 1 — Introduction Data devices connect to a 2902 MainStreet unit through the following data interface modules: • RS-232 DCM • V.35 DCM • X.21 DCM • Codirectional DCM • DNIC module • 2B1Q module 1.2 Physical components The 2902 MainStreet system has three major physical components: • chassis • power supply • Control card Figure 1-2 identifies the components for the unit. Figure 1-2 2902 MainStreet unit (interior, rear view) Data interface modules EDG position (1) position (2) and Sig/Gnd Control card Primary rate interface P2 (P2) modules (P1) P1 Slot 2 Personality modules Power Slot 1 supply Power Tx-1 receptacle Rx-1 Protective Rx-2 Tx-2 Alarm earth Modem Power Loopback Line-2 Fuse switch LEDs holder Line-1 Status LED Seven-segment Terminal display 9058 2902 MainStreet Technical Practices 1-3 May 2002 90-2906-01 1 — Introduction Chassis The chassis acts as a mechanical base for the Control card, power supply and connectors. The top is attached with screws and, once removed, provides access to the Control card, its modules and the power supply. The front panel has LEDs that indicate the status of the power supply, the alarms, the processor and the primary rate links. The rear panel has LEDs that indicate the status of the Control card and loopbacks, and a seven-segment display that indicates the number of major alarms. All power and signal connections are made at the rear panel. Power supply The self-contained power supply is mounted inside the unit, above the Control card. It receives its power connection from the power connector module, which contains an EMI filter, fuse holder and power switch. Control card The Control card is a multilayered printed circuit board that performs functions common to the entire system. It contains the system software and configuration memory, and supports up to two E1 primary rate LIMs and up to two data interface modules. Figure 1-3 shows the location of the modules. The Control card provides connectors for network interfaces, data devices, serial ports and external alarm devices. It also supports several LED indicators that can be seen from the back panel (see Figure 1-2). Figure 1-3 Control card modules LIM (P1) LIM (P2) EPROMs 1 2 3 4 Interface module (position 2) Interface module (position 1) Personality modules (Slot 2/Slot 1) Jumper blocks Jumper blocks (J37, J40) (J41, J44) 8840 1-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 1 — Introduction E1 primary rate line interface modules A LIM provides the line interface to a primary rate line. It contains the drivers and receivers, coupling transformers, and fuses needed for line buffering, impedance matching, isolation and protection. It also provides transmit and receive shield grounding. There are positions for two E1 primary rate LIMs on the Control card, labeled P1 and P2 in Figure 1-3. An E1 module must be installed to enable a network port on the 2902 MainStreet system. The unit supports four types of LIMs: • E1 G.703 LIM • E1 HDSL LIM • E1 HDSL LIM2 • E1 Optical LIM There are two E1 G.703 LIM variants—one for 75 Ω network termination and the other for 120 Ω termination. The 75 Ω G.703 LIM connects to the network through BNC connectors; the 120 Ω G.703 and HDSL LIMs connect through RJ45 connectors. The E1 Optical LIM connects to the network through FC_PC connectors. You can install any combination of primary rate LIMs on the Control card. One LIM is required for each E1 link. There are two jumper blocks for each primary rate LIM on the Control card. The jumpers are set to specify the termination impedance of each primary rate line: 75 Ω or 120 Ω termination. Data interface modules There are locations for two data interface modules on the Control card, as shown in Figure 1-3. Physical position 1 on the Control card maps to logical position M01 on the NMTI, while physical position 2 on the Control card maps to logical position M09 on the NMTI. Logical positions M02 to M08, and M10 to M16, on the NMTI cannot be configured and can only be reserved. All NMTI operations pertaining to physical position 2 are performed through logical position M09. See chapter 12 in Configuration for more information. All data modules except the Codirectional DCM support synchronous and asynchronous transmissions. The Codirectional DCM supports local G.703 64 kb/s NTU connections. External device connectors (Slot 1 and Slot 2) Slot 1 and Slot 2 connectors on the Control card provide the access points for user-changeable adapter modules (called personality modules). Each personality module presents the appropriate connector to the external data device and transfers signals between its DCM and the device. There is a personality module for each DCM. Slot 1 and Slot 2 connectors are stacked, with Slot 2 above Slot 1. 2902 MainStreet Technical Practices 1-5 May 2002 90-2906-01 1 — Introduction The personality module in Slot 1 connects to the data interface module in physical position 1 (NMTI logical position M01). The personality module in Slot 2 connects to physical position 2 (NMTI logical position M09). Primary rate link connectors (Rx-1, Tx-1, Rx-2, Tx-2, Line-1, Line-2, P1 and P2) The BNC connectors labeled Rx-1, Tx-1, Rx-2 and Tx-2 are for 75 Ω E1 network termination. Rx-1 and Tx-1 connect to LIM P1; Rx-2 and Tx-2 connect to LIM P2. The RJ45 connectors labeled Line-1 and Line-2 are for 120 Ω E1 or HDSL network termination. Line-1 connects to LIM P1; Line-2 connects to LIM P2. The FC_PC connectors labeled P1 and P2 are for optical network connections. P1 connects to LIM P1; P2 connects to LIM P2. Serial port connectors (Modem and Terminal) The two RJ45 connectors labeled Modem and Terminal are EIA/TIA-232 serial port connectors. The Terminal connector is configured for a direct connection to node management equipment. The Modem connector is configured for an indirect (or remote) connection to node management equipment through a modem. External alarm connector (Alarm) The connector labeled Alarm is an RJ11 connector. Through the Alarm connector, the 2902 MainStreet system can monitor external equipment for alarm conditions and can signal an alarm condition to an indicating device (such as a light or buzzer). LED indicators A Control card status LED, a seven-segment display, and a group of four loopback LEDs are mounted on the edge of the Control card. These provide information about card and module status and indicate activated loopbacks. 1.3 HDSL LIM overview HDSL is a technology that provides transport of E1 service over two pairs of unconditioned copper loops, allowing service providers and private network users to take advantage of their installed base of copper facilities. HDSL delivers bidirectional (full-duplex) 2.048 Mb/s transmission capability over two non-loaded, two-wire metallic pairs. This eliminates the need for additional conditioned lines and repeaters to achieve similar distances. The E1 HDSL LIM and E1 HDSL LIM2 can help to significantly reduce carrier provisioning cost, improve service response times and enhance transmission quality. Line conditioning is simplified, since bridge taps and mixed cable gauge concerns are eliminated. Also, binder separation is no longer required. The E1 HDSL LIMs pass all defined ETSI loops. For example, the LIMs can achieve a maximum reach of 3700 m (12 139 ft) with zero noise using 0.4 mm wire, or 2850 m (9350 ft) with 0 dB ETSI noise. Impairments such as noise, cross-talk, bridge taps, and splices can affect the quality of the signal and loop length. 1-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 1 — Introduction The 2902 MainStreet system supports two E1 HDSL LIMs, each providing separate HDSL transmission. A module is used at both ends of an E1 HDSL link to increase the distance between midspan repeaters in a carrier service area. Each loop carries 16 DS0s as well as overhead information. The modules use full duplex, 2B1Q line coding and continuous adaptive echo cancellation to improve loop reach and BER (bit error rate) performance. Note — The E1 HDSL LIM and E1 HDSL LIM2 are not end-to-end compatible. Both ends of an E1 HDSL link must have the same type of HDSL LIM installed. Bidirectional data is transmitted and received on each pair at a rate of 1168 kb/s. The data from both pairs are combined to form a DS1. The 1168 kb/s rate includes 1024 kb/s of timeslot information and 144 kb/s of HDSL overhead (see Figure 1-4). Figure 1-4 HDSL technology HDSL loop 1 30 DS0s E1 E1 E1 E1 30 DS0s 1168 kb/s HDSL HDSL interface interface master 1168 kb/s slave 2.048 2.048 Mb/s Mb/s HDSL loop 2 7661 The Control card on a 2902 MainStreet system supports E1 HDSL LIMs in the same way that it supports E1 G.703 LIMs. The E1 HDSL LIMs provide the same service as the E1 G.703 LIMs, except that they use HDSL technology and do not provide the monitoring or bypass functions that are available on the E1 LIMs. Figure 1-5 shows a typical application for E1 HDSL LIMs. Figure 1-5 Typical E1 HDSL LIM or E1 HDSL LIM2 application Ethernet LAN E1 HDSL LIM or E1 HDSL LIM2 Router X.21/V.35 3700 m (12 139 ft) 0.4 mm wire, zero noise X.21/V.35 Slave Master 2902 Video MainStreet 3600 MainStreet E1 conferencing NTU Multiservice Bandwidth Manager Centrex/PBX 2902 MainStreet Technical Practices 1-7 May 2002 90-2906-01 1 — Introduction Performance specifications The E1 HDSL LIM and E1 HDSL LIM2 meet the performance specification for ETSI ETR 152. 1.4 Optical LIM overview The E1 Optical LIM converts electrical signals to optical signals. The E1 Optical LIM supports up to 32 DS0s, with one DS0 (timeslot 0) used for synchronization. The 31 DS0s available for data transmission provide a bidirectional bandwidth of 2.048 Mb/s over a distance of 15 km (9 mi), using a 1300 nm single-mode fiber. Full-duplex transmission between two E1 Optical LIMs on separate nodes is achieved by sending data in one direction at a time, making the E1 Optical LIM immune to unwanted optical reflections. This method allows a simplex single-mode cable to be used in a full-duplex application. The E1 Optical LIM emulates an E1 G.703 LIM; however, the monitor and bypass modes on the E1 Optical LIM are not supported. The E1 Optical LIM operates transparently with the node software and has the same configuration and maintenance functions as the E1 G.703 LIM. Figure 1-6 shows the E1 Optical LIM in a point-to-point application. Figure 1-7 shows a feeder node application. Figure 1-6 E1 Optical LIM point-to-point application 2902 MainStreet NTU 2902 MainStreet NTU DNIC DNIC Data Data X.21 X.21 15 km E1 E1 E1 E1 (9 mi) G.703 Optical Optical G.703 LIM LIM LIM LIM Fiber cable (P2) (P1) (P1) (P2) Video Video PBX PBX 10450 1-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 1 — Introduction Figure 1-7 E1 Optical LIM feeder node application 2902 MainStreet NTU DNIC Data X.21 15 km (9 mi) Optical network E1 E1 Fiber cable G.703 Optical LIM LIM (P2) (P1) Video PBX 10451 1.5 Site selection Observe the site, space, power and grounding requirements that follow to ensure: • adequate access to equipment • fault-free operation • personal safety Site requirements Install the unit in an area that meets the following general site requirements: • clean and dry • well ventilated • well illuminated Table 1-1 lists the specific site requirements. 2902 MainStreet Technical Practices 1-9 May 2002 90-2906-01 1 — Introduction Table 1-1 Site specifications Item Specification Power source Unswitched, separate circuit providing one of the following ranges: • 90 to 110 V ac (100 V ac +6%/–10%) • 207 to 253 V ac (230 V ac ±10%) Temperature Operating: 0° to 40°C (32° to 104°F) Shipping and storage: –40° to 66°C (–40° to 150°F) Humidity 5 to 95% relative humidity, non-condensing (a maximum of 32 g of water per cubic meter of air, or 0.024 lb of water per pound of air) Altitude Between 60 m (197 ft) below sea level and 1800 m (5905 ft) above sea level Grounding Cables used for ground (earth) connections should comply to local practice requirements, and be a minimum of 65/34 stranded (1.5 mm nominal diameter [16 AWG]) Note — Although this unit has been designed and tested to all relevant standards of conducted and radiated electromagnetic interference, it may be affected by strong sources of electromagnetic radiation in the near field, such as elevators, air conditioners, photocopiers and facsimile machines. Space requirements The 2902 MainStreet unit is two rack units high and designed to be placed horizontally on a desktop or mounted in a rack. A rack-mounted unit can be in a fixed, permanent position or in a sliding drawer. The rack must be properly installed and stable, for example, bolted securely to the floor. Install the unit where it can be connected easily to primary rate links, data circuits and a power source. For mounting instructions, see chapter 3. Power requirements The unit is shipped with an ac power supply installed (230 V/50 Hz or 115 V/60 Hz) and a power cord. To prevent outages, and to minimize surges and drops in power, the unit must be connected to an unswitched, separate circuit power source. Power consumption depends on the number and types of modules installed, and the input voltage supplied. Power consumption is 14 W for the Control card and approximately 4 W for each optional module. See Table 1-2 for maximum power requirements. 1-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 1 — Introduction Table 1-2 Maximum power requirements Supplied voltage Minimum voltage Maximum Maximum power (1) voltage requirement 100 V ac 90 V ac 110 V ac 42 W 230 V ac 207 V ac 253 V ac 42 W Note (1) Occurs when two data interface modules and two LIMs are used. Grounding requirements The chassis must be connected to a building ground point, usually a metal water pipe or building steel. The cable must be long enough to connect the ground screw on the rear panel to the building ground point without splicing. Use a cable that is a minimum of 16 AWG (1.5 mm nominal diameter). A cable that is 10 AWG (2.6 mm nominal diameter) or 12 AWG (2 mm nominal diameter) is recommended. For grounding information and instructions, refer to chapter 4. 1.6 Installation summary Table 1-3 serves as a reference summary for the installation procedures. Table 1-3 Installation summary Step Reference 1. Unpack and inspect the components. Chapter 2 2. Mount the unit. Chapter 3 3. Ground the unit. Section 4.1 4. Connect to power and conduct the power-up test. Sections 4.2 and 4.4 5. Install the modules. Chapter 5 6. Connect to the network. Chapter 6 7. Connect the data devices. Chapter 7 8. Connect the node management terminal. Chapter 8 9. Connect the external alarm devices. Chapter 9 10. Switch on the power. Section 4.2 1.7 Installation tools and hardware required Table 1-4 lists the tools and hardware are required to install a 2902 MainStreet system (listed by activity). Some tools or hardware may not apply to your particular installation. 2902 MainStreet Technical Practices 1-11 May 2002 90-2906-01 1 — Introduction Table 1-4 Installation tools and hardware Activity Tools and hardware Assembling • Antistatic wrist strap • Small slot screwdriver • #1 and #2 Phillips screwdrivers Rack-mounting • #2 Phillips screwdriver • One rack-mount kit (19-inch) available from your supplier (part number 90-2901-01) • One rack-mount slide assembly (19-inch or 23-inch) available from your supplier (part numbers 90-2367-01 and 90-2367-02 respectively) Grounding • Wire stripper • Crimp tool • One ring lug • Three spade lugs • Slot screwdriver • 5/16-inch nut driver • 10, 12 or 16 AWG cable (2.6, 2.0 or 1.5 mm nominal diameter) Securing slide assembly • Wire cutter cables • Cable ties Installing modules • #1 and #2 Phillips screwdrivers • #2 nut driver • Module extraction tool • EPROM IC insertion tool • EPROM IC extraction tool Connecting primary rate • Adapters (as required) link • Cabling (as required) Connecting data circuit • Personality modules • Adapters and cabling (as required) Connecting node • Adapters (as required) management equipment • Cabling (as required) • Node management terminal (VT100-compatible terminal or VT100 (1) terminal emulator) Connecting external alarm • RJ11-to-spade lug cable equipment • RJ11-to-RJ11 cable • Distribution box Note (1) If you are using the Craft Interface Node Manager or a 5620 Network Manager for the node management, consult the Craft Interface Node Manager or 5620 NM documentation for installation requirements. 1-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 2 — Unpacking and inspecting the shipment 2.1 Antistatic precautions 2-2 2.2 Unpacking and inspecting the shipment 2-2 2.3 Performing a startup test 2-4 2.4 Repacking the shipment 2-4 2902 MainStreet Technical Practices 2-1 May 2002 90-2906-01 Loop Status U 1 2 Display P2 P1 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 2 — Unpacking and inspecting the shipment 2.1 Antistatic precautions Electronic circuitry is easily damaged by electrostatic discharge. Protect the unit and its components by wearing a properly grounded antistatic wrist strap throughout the assembly and installation procedure. Until the unit is permanently grounded, connect your antistatic wrist strap to a building ground point, usually a metal water pipe or building steel. Once the unit is grounded, you may connect the wrist strap to the ground stud on the rear of the unit (see Figure 2-1). For information on grounding, see chapter 4. Warning — To prevent damage due to electrostatic discharge, take the following precautions when unpacking and assembling the unit. • Always wear a properly grounded antistatic wrist strap. • Before handling any electronic component, touch a grounded metal surface to discharge static from your body. • Handle modules by the edges only. Do not touch any components or connectors. Figure 2-1 Attaching the antistatic strap Antistatic wrist strap 8993 2.2 Unpacking and inspecting the shipment Unpack and assemble the unit on a clean, flat surface such as a workbench or table. Report any missing or damaged components to your account or technical support representative. A part number label is shipped with each module. The label shows the marketing part number (an 8-digit number starting with 90-) and manufacturing code suffix (a single letter). The label is designed to be affixed to the configuration record on the side of the chassis cover. Figure 2-2 shows where the part number is located on the data module. 2-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 2 — Unpacking and inspecting the shipment Figure 2-2 Part number label on an interface module 10469 Procedure 2-1 To unpack the shipment and its components Warning — Observe the antistatic precautions described in section 2.1. 1 Check each package for any sign of damage. 2 Unpack and check each package against your order form and the packing slip to ensure that you have received all the components. The basic components are: • one 2902 MainStreet unit with a Control card, power supply and the latest software generic • four plastic feet • one ac power cord • one documentation package Optional items are packed separately, labeled for identification, and include: • one or two LIMs • one or two interface modules • one or two personality modules • one rack-mount kit (as applicable) • one rack-mount slide assembly (as applicable) 3 Inspect the system and all the components carefully for obvious signs of damage. 4 Check for a configuration record on the chassis exterior. It has part number labels (in text and bar code format) for any installed parts. 5 When you install a module, affix its part number label (enclosed with each module) to the configuration record as follows. 2902 MainStreet Technical Practices 2-3 May 2002 90-2906-01 90-1234-56-B System Status Out of Sync 2 Event Status Out of Sync 1 Network Termination Unit Power Processor 2902 MainStreet 2 — Unpacking and inspecting the shipment a Verify that the marketing part number on the module matches the marketing part number on the label. b Affix the label to the appropriate position on the system configuration record (see Figure 2-3). If you are removing or replacing a module, remove its label from the system configuration record and keep it with the module. 6 Store the packing material in a clean, dry place for use when the equipment is moved to another location. Figure 2-3 System configuration record System configuration record 9131 2.3 Performing a startup test We recommend that you perform a startup test before installing any LIMs or data interface modules, making any network or data device connections, or mounting the 2902 MainStreet unit. See section 4.4 for information on startup diagnostics. Before connecting to an ac power source, you must temporarily ground the unit by connecting the protective earth terminal (chassis ground) on the rear of the unit to the building ground. 2.4 Repacking the shipment Repack the shipment in its original packing material. Observe antistatic precautions. If the original packing material is not available when you want to move the equipment, place the components in antistatic bags and wrap them with several layers of air-cushion material. Place each wrapped component in a suitable container filled with paper or a similar non-static packing material, such that all items have minimal movement. Warning — Static protection of the repackaged system and modules is mandatory. 2-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 3 — Mounting the unit 3.1 Setting up the unit on a desk 3-2 3.2 Mounting the unit in a rack 3-2 3.3 Mounting the unit in a slide assembly 3-3 2902 MainStreet Technical Practices 3-1 May 2002 90-2906-01 L Lo oo op p Status Status U U 1 1 2 2 D Disp ispla lay y P1 P2 P1 P2 R Rx-1 x-1 Tx-1 Tx-1 RR x-2 x-2 Tx-2 Tx-2 Line-1 Line-1 Line-2 Line-2 M Modem odem Term Terminal inal Alarm Alarm Slot 1 Slot 1 Slot 2 Slot 2 II O O EDG Sig S/G ig/G nd nd EDG 3 — Mounting the unit 3.1 Setting up the unit on a desk The unit is designed to be set on a flat surface, such as a desktop or a table. If the rubber feet are not attached, place the unit upside down on a flat surface and attach them. Take care not to scratch the top cover. Set the unit down where it can be connected to a power source, external devices and the network. 3.2 Mounting the unit in a rack The unit can be mounted in a 19-inch rack by first attaching brackets to the unit. For site requirements, see section 1.5. Danger — Before installing any rack-mount assembly, secure the rack to the floor to ensure that it does not tip over. Procedure 3-1 To mount the unit in a rack Tools required: • #2 Phillips screwdriver • one rack-mount kit (19-inch) available from your supplier (part number 90-2901-01) 1 Position the brackets and attach them to the unit with six #8 flathead screws (supplied), as shown in Figure 3-1. Figure 3-1 Attaching the brackets to the unit 8834 2 Attach the shelf to the rack with the four panhead screws (supplied), as shown in Figure 3-2. 3-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 3 — Mounting the unit Figure 3-2 Attaching the unit to the rack Power Processor 2902 MainStreet Network Termination Unit Event Status Out of Sync 1 System Status Out of Sync 2 Mounting Mounting screws screws 8835 3.3 Mounting the unit in a slide assembly The unit can be rack-mounted in a 19- or 23-inch slide assembly. The rack-mount slide assembly contains two parts: a u-shaped slide bracket and a rack-mount shelf (see Figure 3-3). When shipped, the slide bracket is installed in the shelf. Before installing the unit, you must remove the bracket from the shelf. The general procedure to mount the unit in a slide assembly is as follows. 1 Install the slide assembly in a rack. 2 Attach the unit to the slide bracket. 3 Install the slide bracket in the rack. Figure 3-3 Slide assembly Rack-mount shelf Slide bracket 8965 2902 MainStreet Technical Practices 3-3 May 2002 90-2906-01 3 — Mounting the unit Procedure 3-2 To install the slide assembly in a rack Tools required: • #2 Phillips screwdriver • one rack-mount slide assembly kit (19- or 23-inch), available from your supplier (part numbers 90-2367-01 and 90-2367-02 respectively) 1 Secure the slide assembly to the rack with the panhead screws (supplied). a To install the unit flush with the rack, secure the slide assembly using the front set of brackets, as shown in Figure 3-4. Figure 3-4 Installing the assembly with the front brackets 7347 b To install the unit so that it extends beyond the front of the rack, attach the mid-mount brackets to the rack-mount assembly (see Figure 3-5). Secure the assembly to the rack. Figure 3-5 Installing the mid-mount brackets 8971 2 Loosen the thumbscrews, grasp the front edge of the slide bracket, and pull it forward until the slides lock into place on the slide rails (see Figure 3-6). 3 Depress the tabs on both sides of the slides while pulling the bracket free of the rack-mount shelf. 3-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 3 — Mounting the unit Figure 3-6 Removing the slide bracket from the rack-mount shelf Slide rails Tab Tab Slide 8638 Procedure 3-3 To attach the unit to the slide bracket You need a #2 Phillips screwdriver to perform this task. 1 Place the unit upside down on a flat surface and position the slide bracket upside down on top of the unit. Align the front edge of the bracket with the front panel of the unit (see Figure 3-7). 2 Secure the slide bracket to the unit with four #8-32 screws (supplied). 2902 MainStreet Technical Practices 3-5 May 2002 90-2906-01 3 — Mounting the unit Figure 3-7 Securing the slide bracket to the unit 8970 Procedure 3-4 To install the slide bracket in the rack 1 Fully extend the slide rails from the rack-mount shelf. 2 Align the slides on the slide bracket with the slide rails and push the bracket into the rails until the slides lock into place (see Figure 3-8). 3-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 2902 MainStreet t i ti it Ne work Term na on Un System Status Out of Sync 2 Event Status Out of Sync 1 Network Termination Unit Power Processor 2902 MainStreet 3 — Mounting the unit Figure 3-8 Installing the unit in the rack Slide rail Tab Thumbscrews Slide bracket 8969 3 Make all cable connections as described in chapters 6, 7, 8 and 9. 4 Secure all cables using service loops (see section 4.3 for details). Caution — All cables must be properly connected and secured to avoid the risk of pinching the cables when the drawer is opened and closed. Ensure that cables are secured before pushing the unit back into the rack. 2902 MainStreet Technical Practices 3-7 May 2002 90-2906-01 3 — Mounting the unit 3-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 4 — Ground and power connections 4.1 Ground connections 4-2 4.2 Power connections 4-4 4.3 Securing slide assembly cable connections 4-4 4.4 Startup diagnostics 4-6 2902 MainStreet Technical Practices 4-1 May 2002 90-2906-01 4 — Ground and power connections 4.1 Ground connections The three types of ground points are: protective earth, telecom safety earth (labeled Sig/Gnd) and energy dumping ground (labeled EDG). Figure 4-1 identifies the ground points on the unit. To avoid electrical damage to the 2902 MainStreet system, all three ground types must be permanently and separately grounded. Figure 4-1 Ground points on the 2902 MainStreet system EDG Sig/Gnd Protective earth I EDG Sig/Gnd O P1 P2 Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display 8973 The cables used for these ground connections must be long enough to reach the building ground point without splices. 2 The telecom safety earth cable should be 1.5 mm (16 AWG), and green and yellow in color. Procedure 4-1 To ground the unit Tools required: • wire stripper • crimp tool • one ring lug • three spade lugs • slot screwdriver • 5/16-inch nut driver • 10, 12 or 16 AWG wire (2.6 mm, 2 mm and 1.5 nominal diameter respectively) (10 or 12 AWG is recommended) 1 Ensure that the unit is turned off. 4-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 4 — Ground and power connections 2 Connect three cables to the building ground point and bring the cables to the back of the unit. Note — If the unit is rack-mounted in a slide assembly, leave enough extra cable to form a service loop approximately 40 to 46 cm (16 to 18 in.). See section 4.3 for details on creating service loops. 3 Strip away approximately 1 cm (1/2 in.) of insulation from each cable. 4 Connect each ground as shown in Figure 4-2. Do not overtighten. a For protective earth, attach a ring lug to the cable, connect the cable to the ground stud, and tighten the nut with the nut driver. If you have a PBX or key system, it should be grounded with the unit at a common point. b For telecom safety earth, attach a spade lug to the cable, connect the cable to the Sig/Gnd terminal, and tighten the screw. c For energy dumping ground, attach a spade lug to the cable, connect the cable to the EDG terminal, and tighten the screw. Figure 4-2 Ground connections Ring Star lug washer EDG Sig/Gnd Spade Ground Ground lug stud nut I EDG Sig/Gnd O Slot 2 P1 P2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display To building ground point 8972 2902 MainStreet Technical Practices 4-3 May 2002 90-2906-01 4 — Ground and power connections 4.2 Power connections If the unit is rack-mounted in a slide assembly, leave enough cable to form a service loop approximately 40 to 46 cm (16 to 18 in.). See section 4.3 for details on creating service loops. Procedure 4-2 To connect to power 1 Ensure that the power switch is in the Off position. 2 Connect the power cord to the ac receptacle at the back of the unit (see Figure 4-3). If the unit is mounted in a slide drawer, secure the power cord as described in section 4.3. 3 Plug the other end of the power cord into an unswitched ac outlet. 4 Turn on the unit power switch. The LEDs on the faceplate and rear panel run through their startup diagnostic patterns. See section 4.4 for more information on startup diagnostics. Figure 4-3 Connecting to ac power source I EDG Sig/Gnd O P1 P2 Unswitched Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm ac outlet Slot 1 Loop Status U 1 2 Display 8846 4.3 Securing slide assembly cable connections If the system is installed in a rack-mount slide assembly, you must ensure that the cables do not get pinched as the unit slides in and out of the rack. Procedure 4-3 To secure slide assembly cables Tools required: • wire cutters • plastic spiral wrap (supplied) • cable ties (supplied) 1 Route all cables to the back of the rack-mount shelf. 4-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 4 — Ground and power connections 2 Secure the cables to the shelf with the cable ties. Leave a service loop of 40 to 46 cm (16 to 18 in.) maximum, from the point of connection on the unit to the first cable tie fastening. This allows the unit to be pulled out freely (see Figure 4-4). i Secure the power cable and chassis ground wire in one loop. ii Secure the data device cables in a second loop. iii Secure all other cables in a third loop. Figure 4-4 Securing cables to the shelf with service loops (top view) Ground cables AC power cable Spiral wrap Cables for data devices Wrapped Cables power and for E1 and ground cables alarm devices Rack Rack Shelf 8974 3 Wind the supplied plastic spiral wrap around the power and ground cables from their point of exit to the first cable tie fastening. Trim any excess wrap with the wire cutters. The wrap protects the cables from pinching when the unit is moved in and out of the assembly. 4 Push the unit all the way into the shelf and verify that the cables are not pinched. 5 Lock the unit into place by tightening the two thumbscrews with the screwdriver. 2902 MainStreet Technical Practices 4-5 May 2002 90-2906-01 4 — Ground and power connections 4.4 Startup diagnostics At power-up, the unit goes through a startup sequence that includes a number of startup diagnostic tests (or self-tests). The startup sequence should last for less than 1 minute. Figures 4-5 and 4-6 show the location of the LEDs. When the 2902 MainStreet unit is powered up without any LIMs or data interface modules installed, the LEDs light up as described in Tables 4-1 and 4-2. Once the startup sequence is finished, the LED indications depend on the node configuration. See chapter 24 in Maintenance for descriptions of the visual indicators or if the indicators do not light in the pattern described. Note — Wait until the diagnostic tests are completed before attempting to rectify a problem. Once the diagnostic tests have run successfully, you are ready to initiate a node management session, as described in chapter 10 in Configuration. Figure 4-5 Front panel self-test indicators Power Processor Event Status Out of Sync 1 System Status Out of Sync 2 Power Processor 2902 MainStreet Network Termination Unit Event Status Out of Sync 1 System Status Out of Sync 2 8831 Figure 4-6 Rear panel self-test indicators Loop Status U 1 2 Display I EDG Sig/Gnd O P1 P2 Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display 8832 4-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 4 — Ground and power connections Table 4-1 Front panel indicators at power-up Indicator Description Power LED Turns on and stays on. Event Status LED Turn on for 1 second and then turn off. After approximately 40 seconds, these LEDs turn on again. System Status LED Processor LED Turns on for 1 second and then turns off. After approximately 40 seconds, the Processor LED flashes with a 50% duty cycle (0.5 second on, 0.5 second off). Out of Sync 1 LED Stay off for 1 second and then turn on. After approximately 40 seconds, (1) these LEDs turn on again. Out of Sync 2 LED Note (1) The exact behavior of the Out of Sync LEDs (after the startup sequence) depends on the node hardware configuration and network connections. Table 4-2 Rear panel indicators at power-up Indicator Description Power indicator The power indicator for the Control card is the decimal point on the seven-segment display. The decimal point is lit when the Control card power is on. Status LED The Status LED turns on after the self-tests are complete (after approximately 3 seconds). When lit, the Control card is functioning properly. Seven-segment display Runs through a sequence of indications. The display shows the letter S for approximately 1 second, indicating the start of the self-test sequence. There are 27 self-tests. See Table 4-3 for the self-test descriptions. (1) Before each test, the test number is shown . If the test fails, the number is flashed again, followed by the letter F. The test is repeated several times before the self-tests continue. At the end of the self-test sequence, the letter P or F is shown, indicating that all tests have passed or some tests have failed. If the seven-segment display cycles its outer segments during a test, this indicates that the current test is busy. The cycling segment affect applies to test numbers 1 (EPROM check) and 4 (RAM). Note (1) For numbers greater than 9, the first digit is shown first, followed by the second digit. Table 4-3 describes the self-tests. In most cases, if a test fails, you should contact your technical support representative. Exceptions are noted in the table. If any alarms are generated as a result of the self-tests, refer to chapter 10 in Configuration to familiarize yourself with node management, and to chapter 25 in Maintenance to display the Major alarm queue. 2902 MainStreet Technical Practices 4-7 May 2002 90-2906-01 4 — Ground and power connections Table 4-3 Diagnostic self-test descriptions Number Test Description Problem 1 EPROM A checksum is performed over the entire EPROM checksum (1) checksum program space. error 2 Data bus This test causes a bus interrupt and then Processor viability verifies that the interrupt is a bus interrupt. failure 3 Address bus This test checks the address lines used to Processor viability access RAM. failure (2) 4 DRAM This test writes and reads a byte, word, DRAM check failure and long word from a segment in DRAM, performs a walking bit test on a long word in DRAM, writes and reads a fixed long word over the entire DRAM and tests the address lines. 5 CPU This test generates a bus interrupt and CPU test failure verifies that the interrupt is a bus interrupt. 6 Install RDS This test installs the RDS from the main RDS software problem source code into RAM. 7 UART 1 presence This test verifies access to UART 1. UART not present or responding 8 UART 2 presence This test verifies access to UART 2. UART not present or responding 9UART This test sends data from one UART to the UART failure or send/receive other and verifies that the data has been communications received. failure 10 4 ms timer This test generates two 4 ms interrupts Timer check failure and verifies that the time between them is 4 ms. 11 Data EDX This test writes and reads data from all EDX test failure memory data EDX chips to verify data integrity. 12 Control DX This test writes and reads data from all DX test failure memory Control card DX chips to verify data integrity. 13 Data EDX and This tests writes and reads data over a EDX, DX or Xilinx IC Control DX loopback created on the data EDX or the problem loopback Control DX. 14 HDLC presence This test checks for the presence of the Control card HDLC (HDLC 1) first HDLC chip on the Control card. test failure 15 HDLC loopback This test checks the function of the first Control card HDLC (HDLC 1) HDLC chip on the Control card by making test failure a loopback through the DX and then sending a packet through. 16 HDLC presence This test checks for the presence of the Control card HDLC (HDLC 2) second HDLC chip on the Control card. test failure 17 HDLC loopback This test checks the function of the second Control card HDLC (HDLC 2) HDLC chip on the Control card by making test failure a loopback through the DX and then sending a packet through. 18 HDLC presence This test checks for the presence of the Control card HDLC (HDLC 3) third HDLC chip on the Control card. test failure (1 of 2) 4-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 4 — Ground and power connections Number Test Description Problem 19 HDLC loopback This test checks the function of the third Control card HDLC (HDLC 3) HDLC chip on the Control card by making test failure a loopback through the DX and then sending a packet through. 20 E1 Framer This test writes and reads data to the first E1 Framer failure loopback E1 framer and verifies the data integrity. (Framer 1) 21 E1 Framer This test writes and reads data to the E1 Framer failure loopback second E1 framer and verifies the data (Framer 2) integrity. 22 Thermometer This test writes and reads data from a Thermometer not register on the thermometer chip. present or circuit malfunction 23 SEEP This test writes and reads data from the SEEP test failure serial EPROM on the Control card. 24 125 µs timer This test generates a 125 µs interrupt and Timer check failure verifies that it is generated. 25 Loopback (LIM 1) This test sends and receives data over LIM 1 failure LIM 1 (LIM 1 must be installed). 26 Loopback (LIM 2) This test sends and receives data over LIM 2 failure LIM 2 (LIM 2 must be installed). 27 SMAC interrupt This test generates a SMAC interrupt and EDX or DX failure, or verifies that it is correctly generated. CPU interrupt failure (2 of 2) Notes (1) Check that the EPROMs are properly installed on the Control card. (2) Turn the power off, wait 30 seconds, then restart the system. If the problem persists, contact your technical support representative. 2902 MainStreet Technical Practices 4-9 May 2002 90-2906-01 4 — Ground and power connections 4-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 5 — Installing and removing modules 5.1 Control card modules 5-2 5.2 Opening the unit 5-2 5.3 Installing and removing primary rate modules 5-3 5.4 Installing and removing data interface modules 5-10 5.5 Installing and removing personality modules 5-11 5.6 Replacing EPROMs 5-12 2902 MainStreet Technical Practices 5-1 May 2002 90-2906-01 5 — Installing and removing modules 5.1 Control card modules Figure 5-1 shows the location of the primary rate, data interface, EPROM and personality modules on the Control card. Figure 5-1 Location of modules on the Control card LIM (P1) LIM (P2) EPROMs 1 2 3 4 Interface module (position 2) Interface module (position 1) Jumper blocks Jumper blocks (J37, J40) (J41, J44) 8839 5.2 Opening the unit To open the unit, you need a #2 Phillips screwdriver. Procedure 5-1 To open the unit Danger — Hazardous voltages inside—ensure that the power is off before removing the top cover. Warning — Electronic circuitry is easily damaged by electrostatic discharge. Wear a properly attached antistatic wrist strap before handling any electronic component. Handle the modules by their edges. 1 Ensure that the unit is turned off and that the power cord is unplugged. 2 Remove the seven top cover screws and slide off the top cover (see Figure 5-2). If the unit has rack-mount brackets attached, remove them also. 5-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 Loop Status U 1 2 Display P1 P2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 5 — Installing and removing modules Figure 5-2 Opening the unit 8975 5.3 Installing and removing primary rate modules Each primary rate module has a female connector that fits onto a male connector on the Control card. The modules are secured to mounting posts on the Control card with screws. The holes in the module should line up with the posts. If they do not, you are installing the module in the wrong location. There are two jumper blocks for each primary rate module on the Control card. The jumpers need to be configured for E1 G.703 and E1 HDSL LIMs. The jumper configurations do not affect operations for other primary rate modules. Warning 1 — Ensure that the power is off before inserting or removing primary rate modules. Warning 2 — Electronic circuitry is easily damaged by electrostatic discharge. Wear a properly attached antistatic wrist strap before handling any electronic component. Handle modules by their edges. Procedure 5-2 To install E1 G.703 or E1 HDSL LIMs You need a #2 Phillips screwdriver to install E1 G.703 or E1 HDSL LIMs. 1 Ensure that the unit is turned off and that the power cord is unplugged. 2 Open the unit. 3 Remove the screws from the appropriate Control card mounting posts. 4 Locate the jumper blocks on the Control card corresponding to the module position. Jumper blocks J37 and J40 correspond to LIM P1; jumper blocks J41 and J44 correspond to LIM P2 (see Figure 5-3). 2902 MainStreet Technical Practices 5-3 May 2002 90-2906-01 5 — Installing and removing modules Figure 5-3 Jumper block locations LIM (P1) LIM (P2) J39 J40 J37 J38 J41 J42 J43 J44 75 75 75 75 120 120 120 120 Jumper blocks Jumper blocks for LIM P1 for LIM P2 16567 5 Install the jumpers. The jumpers are factory-set to 75 Ω termination. a For E1 G.703 LIMs, the jumpers are configured for 75 Ω or 120 Ω termination depending on the variant (75 Ω for the BNC connector variant and 120 Ω for the RJ45 connector variant). For 75 Ω termination, set the jumpers on the top and middle pins (see Figure 5-4). For 120 Ω termination, set the jumpers on the middle and bottom pins (see Figure 5-4). b For E1 HDSL LIMs, the jumpers must be configured for 120 Ω termination. Set the jumpers on the middle and bottom pins (see Figure 5-4). 5-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 Loop Status U 1 2 Display P2 P1 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 5 — Installing and removing modules Figure 5-4 Jumper configuration 75 75 120 120 75 operation 120 operation 16566 6 Hold the module by its edges, align its connector and mounting holes with the Control card connector and mounting posts, and gently push down on the edge of the module nearest the female connector (see Figure 5-5). Do not force a module into position; you might bend the pins on the male connector. If the module does not fit properly, remove it, examine the pins for damage and try again if there is no damage. Figure 5-5 Installing E1 G.703 or E1 HDSL LIMs 8976 7 Screw the module to the mounting posts. 8 Affix the module’s label to the configuration record on the side of the unit. Procedure 5-3 To remove E1 G.703 or E1 HDSL LIMs 1 Ensure that the unit is turned off and that the power cord is unplugged. 2 Remove the screws that secure the module to its mounting posts. 3 Hold the module by the edges closest to its connector and gently pull the module off the Control card. 2902 MainStreet Technical Practices 5-5 May 2002 90-2906-01 5 — Installing and removing modules 4 Reinsert the screws into the posts. 5 Remove the module’s label from the configuration record. Procedure 5-4 To install an E1 Optical LIM Danger — The E1 Optical LIM is a CLASS 1 LASER PRODUCT. Only trained, qualified service personnel thoroughly familiar with laser radiation hazards should install or remove the fiber-optic cables and cards in this system. Warning — To prevent damage to a fiber cable, ensure that the minimum bend radius for the cable is 3 cm (1 1/4 in.). You need a #2 Phillips screwdriver to install an E1 Optical LIM. The E1 Optical LIM kit (part number 90-0568-08) is shipped with the following hardware: • one E1 Optical LIM • one optical fiber cable (1 m [3 ft]) • one #4-40 screw (1/2 in.) • one cable clamp • four cable ties The following hardware is included in the kit but is not used for E1 Optical LIMs installed in the 2902 MainStreet system: • one extension bracket • two #4-40 screws (3/8 in.) • two #4-40 hex nuts • two #4 flat washers • two #6-32 screws (1/4 in.) 1 Ensure that the unit is turned off and that the power cord is unplugged. 2 Open the unit. 3 Remove the screws from the appropriate Control card mounting posts. 4 Connect the fiber cable to the module (see Figure 5-6). Do not overtighten. 5-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 5 — Installing and removing modules Figure 5-6 Connecting the fiber cable to the E1 Optical LIM Fiber cable 9776 5 Hold the module by its edges, align its connector and mounting holes with the Control card connector and the two closest mounting posts, and gently push down on the edge of the module nearest the female connector (see Figure 5-7). Do not force a module into position; you might bend the pins on the male connector. If the module does not fit properly, remove it, examine the pins for damage and try again if there is no damage. Figure 5-7 Installing the E1 Optical LIM E1 Optical LIM 10471 6 Screw the module to the mounting posts. 2902 MainStreet Technical Practices 5-7 May 2002 90-2906-01 Slot 2 Rx-1 Slot 1 O I O I 5 — Installing and removing modules 7 Carefully wrap each fiber cable in three loops (counter-clockwise direction) (see Figure 5-8). Figure 5-8 Looping and connecting the fiber cable to the optical fiber connector Fiber cables E1 Optical LIMs P1 and P2 optical fiber connectors 10472 8 Loosely secure the fiber cables with the four cable ties (see Figure 5-9). Adjust the cable loops until they have similar diameters and secure the loops by tightening the cable ties. Do not overtighten. Figure 5-9 Securing the fiber cable Cable ties 10473 9 Remove the screw from the Control card mounting post closest to EPROM #1 (see Figure 5-10). 5-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 EDG Sig Gnd P2 P1 Slot 2 Loop Tx-2 Rx-2 Tx-1 Rx-1 Slot 1 EDG Sig Gnd P2 P1 Slot 2 Loop Tx-2 Rx-2 Tx-1 Rx-1 Slot 1 Modem Terminal Alarm Line-1 Line-2 Terminal Alarm Modem Line-1 Line-2 P1 P1 Status U 1 2 Display Status U 1 2 Display O I 5 — Installing and removing modules Figure 5-10 Securing the cable clamp EPROM #1 Cable clamp 10474 10 Open the cable clamp and place it around the looped fiber cables. 11 Secure the cable clamp to the Control card mounting post with the #4-40 screw (1/2 in.). Procedure 5-5 To remove an E1 Optical LIM The E1 Optical LIM can be removed without removing the fiber cable. 1 Ensure that the unit is turned off and that the power cord is unplugged. 2 Remove the two screws that secure the module to the mounting posts on the Control card. 3 Hold the module by the edges nearest to its connector and gently pull the module off the Control card. 4 Warning — To prevent damage to the fiber cable, handle it with care and ensure that the minimum bend radius for the cable is 3 cm (1 1/4 in.). Turn the module over and disconnect the fiber cable connector. 5 Reinsert the screws into the posts. 6 Remove the module’s label from the configuration record. 2902 MainStreet Technical Practices 5-9 May 2002 90-2906-01 EDG Sig Gnd P2 P1 Slot 2 Loop Tx-2 Rx-2 Tx-1 Rx-1 Slot 1 Terminal Alarm Line-2 Modem Line-1 P1 Status U 1 2 Display Loop Status U 1 2 Display P2 P1 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 5 — Installing and removing modules 5.4 Installing and removing data interface modules Figure 5-1 identifies the location of the data interface module positions. Each position has two male connectors. Any data module can be installed in either position. Warning — Electronic circuitry is easily damaged by electrostatic discharge. Wear a properly attached antistatic wrist strap before handling any electronic component. Handle modules by their edges. Note — Interface modules may be installed or removed while the system is powered up. Procedure 5-6 To install a data interface module 1 Hold the module by its tabs, align its connectors with the connectors on the module position, and gently push the module part way onto the male connectors (see Figure 5-11). Check that each pin is inserted in the proper position. If the pins are not in the proper position, they might bend or break when you push the module in all the way. Figure 5-11 Installing a data interface module 8838 2 Finish the installation by gently pushing down on the corners of the module. Do not force a module into position; you might bend the pins on the male connector. If the module does not fit properly, remove it, examine the pins for damage and try again if there is no damage. 3 Affix the part number labels to the configuration record. 5-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 Loop Status U 1 2 Display P2 P1 M Alarm Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 odem Terminal Slot 1 Slot 2 I O EDG Sig/Gnd 5 — Installing and removing modules Procedure 5-7 To remove a data interface module 1 Grasp the two plastic tabs on the module and gently lift the module off the Control card. 2 Remove the module’s label from the configuration record. 5.5 Installing and removing personality modules The 2902 MainStreet system is shipped with covering plates protecting the connectors for Slot 1 and Slot 2. The personality module in Slot 1 connects to the data interface module in physical position 1 (NMTI logical position M01). The personality module in Slot 2 connects to physical position 2 (NMTI logical position M09). Warning 1 — Ensure that the power is off before inserting or removing personality modules. Warning 2 — Electronic circuitry is easily damaged by electrostatic discharge. Wear a properly attached antistatic wrist strap before handling any electronic component. Handle modules by their edges. Procedure 5-8 To install a personality module 1 Remove the covering plate and store it for future use. Save the screws because they are used to secure the personality module. 2 Hold the personality module by its edges, insert it through the opening and align its connector with the male connector at the back of the mounting position. Gently push the module part way into the male connector (see Figure 5-12). Figure 5-12 Installing a personality module 8841 3 Finish the installation by gently pushing the module all the way in. Do not force the module into position; you might bend the pins on the male connector. If the module does not fit properly, remove it, examine the pins for damage and try again if there is no damage. 2902 MainStreet Technical Practices 5-11 May 2002 90-2906-01 5 — Installing and removing modules 4 Secure the module with the screws removed in step 1. Procedure 5-9 To remove a personality module 1 Remove the screws that secure the personality module. 2 Grasp the module by the edges of its faceplate and gently pull it out of its mounting position. 3 Install a new personality module or replace the covering plate. 5.6 Replacing EPROMs Replace the EPROMs to install a new software generic. The software generic identifies the system operating software. Note — When you replace the EPROMs, the current configuration settings are lost. Before you turn off the system, you should back up your configuration settings. The configuration can be restored once the new operating software has been installed. Backup and restoration of configuration settings are described in chapter 30 in Maintenance. If the configuration settings are not saved, they will have to be re-entered. Before starting Verify that the system software upgrade kit contains the correct number of EPROMs. The 2902 MainStreet unit, Release 1, uses two EPROMS. The EPROMs are labeled 80-2742-XX-YY, where XX identifies the variant number of the EPROM and YY identifies the revision number of the EPROM. The number 2902 should appear on each label. 5-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 5 — Installing and removing modules Procedure 5-10 To replace the EPROMs Tools required: • #1 Phillips screwdriver • IC extraction tool (for EPROM) • IC insertion tool (for EPROM) Warning 1 — Ensure that the power is off before inserting or removing EPROMs. Warning 2 — Always replace an old EPROM with a new EPROM having the same number, using the correct socket. Warning 3 — Electronic circuitry is easily damaged by electrostatic discharge. Wear a properly attached antistatic wrist strap before handling any electronic component. Handle modules by their edges. 1 Turn the power off and unplug the power cord. 2 Open the unit (see section 5.2). 3 Locate the currently installed EPROM #1 (part number 80-2742-01-YY) and remove it using the IC extraction tool. Figure 5-13 identifies the EPROMs. Figure 5-13 EPROM locations EPROMs 1 2 3 4 16572 4 Pick up the new EPROM #1 with the IC insertion tool. Align the dimpled side of the EPROM with the side of the socket marked with an arrow. Carefully align the pins of the EPROM with the notches in the socket (see Figure 5-14). Insert the EPROM. Warning — If an EPROM is incorrectly aligned, it will be damaged when the unit is turned on. 2902 MainStreet Technical Practices 5-13 May 2002 90-2906-01 5 — Installing and removing modules Figure 5-14 EPROM insertion Dimple Arrow 10449 5 Repeat steps 3 and 4 for EPROM #2 (part number 80-2742-02-YY). 6 Place the old EPROMs in the packaging supplied with the new EPROM set. Store the old EPROMs in a safe place. 5-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 6 — Connecting to the network 6.1 Primary rate connections 6-2 2902 MainStreet Technical Practices 6-1 May 2002 90-2906-01 6 — Connecting to the network 6.1 Primary rate connections Primary rate connections are made through connectors on the rear panel: RJ45 connectors for twisted pair (connectors Line-1 and Line-2), optical connectors for fiber cables (connectors P1 and P2) and BNC connectors for coaxial cables (connectors Rx-1, Tx-1, Rx-2 and Tx-2). Connectors Rx-1 and Rx-2 receive network transmissions; Tx-1 and Tx-2 transmit. Figure 6-1 identifies the connectors. The cable impedance and the primary rate module termination impedance must match. Use the RJ45 connectors for twisted pair, 120 Ω termination and the BNC connectors for coaxial cable, 75 Ω termination. Figure 6-1 Primary rate connectors P1 P2 First E1 link Second E1 link I EDG Sig/Gnd O P1 P2 Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display Rx-1 Rx-2 Line-2 Second Tx-1 Tx-2 E1 link Line-1 First Second First E1 link E1 link E1 link 10423 Primary rate module pin and signal assignments Figures 6-2 and 6-3 identify the RJ45 connector pin and signal assignments for the 120 Ω E1 G.703 and E1 HDSL LIMs respectively. Figure 6-4 identifies the BNC connector pin and signal assignments. Figure 6-2 RJ45 network connectors (line-1 and line-2) for the 120 Ω E1 G.703 LIM 1 Receive 2 Receive 3 Shield 4 Transmit 5 Transmit 6 Shield 7 nc 8 nc nc = no connection 8847 6-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 6 — Connecting to the network Figure 6-3 RJ45 network connectors (line-1 and line-2) for the E1 HDSL LIMs 1 Pair 1b 2 Pair 1a 3 nc 4 Pair 2b 5 Pair 2a 6 nc 7 nc 8 nc nc = no connection 10470 Figure 6-4 BNC network connectors (Rx-1, Tx-1, Rx-2 and Tx-2) Transmit (+) Receive (+) Transmit (-) Receive (-) TX BNC RX BNC (Tx-1 and Tx-2) (Rx-1 and Rx-2) 8849 Procedure 6-1 To connect to the network Warning — To avoid damage to the primary rate fiber cable(s) when installing other rear panel cables, handle all cables carefully and ensure that the minimum bend radius for the fiber cable is 3 cm (1.25 in.). 1 Attach the primary rate link cables to the appropriate primary rate connectors (see Figure 6-1). Note — The 2902 MainStreet system is shipped with covering plates protecting optical connectors P1 and P2. Using a #2 Phillips screwdriver, loosen the screws holding the covering plate(s) and remove the covering plate(s). Attach the primary rate link cables to the appropriate optical connectors (P1 and P2). 2 If the unit is installed in a sliding drawer, leave enough cable to create a service loop and secure it as described in section 4.3. 2902 MainStreet Technical Practices 6-3 May 2002 90-2906-01 6 — Connecting to the network 6-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices 7.1 Data circuit connections 7-2 7.2 Assembling an adapter for EIA/TIA-232 connections 7-9 7.3 DB25-to-M34 cable pin and signal assignment 7-20 2902 MainStreet Technical Practices 7-1 May 2002 90-2906-01 Loop Status U 1 2 Display P2 P1 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 7 — Connecting to data devices 7.1 Data circuit connections Data interface modules have one or two circuits that connect to data devices. Each module connects to its data devices through a plug-in adapter module, called a personality module. Personality modules are user-changeable, and are installed in Slot 1 and Slot 2 connectors, located on the rear panel of the unit (Slot 2 is stacked above Slot 1). Figure 7-1 identifies the data and personality module connectors. For information on installing personality modules, see section 5.5. Note — Personality modules are also known as interface adapters. Figure 7-1 Data and personality module connectors Interface module Interface module connectors connectors (position 2) (position 1) Slot 2 Slot 1 Personality module connectors 10452 Table 7-1 lists the data interface modules and their corresponding personality modules. There are two V.35 personality modules, one for each variant of the V.35 DCM. Table 7-1 Interface and personality modules Interface module Personality module Type of connector RS-232 DCM 90-0611-01 RS-232/RJ45 90-1308-04 Dual RJ45 socket (1) V.35 DCM 90-0523-01 V.35/DB25 90-1308-05 Single DB25 female (2) V.35/DB25 Type 2 90-1308-07 X.21 DCM 90-0423-01 X.21/DB15 90-1308-06 Single DB15 female DNIC 90-0158-01 2 wire/RJ11 90-1308-02 Dual RJ11 socket 2B1Q 90-2892-01 2 wire/RJ11 90-1308-02 Dual RJ11 socket Codirectional 90-1043-01 Codirectional/RJ45 90-2911-01 Dual RJ45 socket Notes (1) Personality module for V.35 internal and slave DCE modes. (2) Personality module for V.35 external DCE and all DTE modes. 7-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Personality module pin and signal assignments Table 7-2 lists the data interface modules and identifies the items needed to connect to the data device, including pin and signal assignment, cable and additional adapter (if required). Some connections to EIA/TIA-232 and V.35 devices require customized cables or adapters. These are described in sections 7.2 and 7.3 respectively. The pin and signal assignments for each personality module are given in Figures 7-2 to 7-7 and Tables 7-3 to 7-8. In these tables, nc stands for no connection. EIA/TIA-232 circuits must have a signal ground (telecom safety earth) connection to the signal ground point on the rear panel of the unit. If a DNIC module is installed, connect data devices via the 2600 MainStreet series DTUs. If a 2B1Q module is installed, connect data devices via the 2700 MainStreet series DTUs. Table 7-2 Data interface modules, connectors and cabling Interface module Pin and signal assignment Cable required Personality module Data equipment end reference of cable RS-232 Figure 7-2 Depends on adapter 1:1 RJ45-to-RJ45 cable configuration; see and an RJ45-to-DB25 section 7.2 adapter (1) (2) V.35 Figure 7-3 or 7-4 See section 7.3 DB25-to-M34 cable X.21 Figure 7-5 Same as Figure 7-5 1:1 DB15-to-DB15 cable (3) DNIC or 2B1Q Figure 7-6 Same as Figure 7-6 1:1 RJ11-to-RJ11 cable Codirectional Figure 7-7 Same as Figure 7-7 1:1 RJ45-to-RJ45 cable Notes (1) There are two kinds of V.35/DB25 personality modules; see Figures 7-3 or 7-4. (2) Do not use 90-0360-01 cables with the unit as these cables do not support all the clocking modes. (3) Only port 1 of the two RJ11 ports is used when a DTU is connected to the DNIC or 2B1Q module. Figure 7-2 RS-232 personality module pin and signal assignment 18 18 12 RS-232 8864 2902 MainStreet Technical Practices 7-3 May 2002 90-2906-01 7 — Connecting to data devices The signal names in Table 7-3 are the names at the 2902 MainStreet system connector. If an adapter is used, the pin and signal assignments at the adapter may be different. See section 7.2 for various EIA/TIA-232 adapter configurations. Table 7-3 RS-232 personality module pin and signal assignment Pin number Signal name 1 Handshake Out (HOUT) 2 Handshake In (HIN) 3 Receive Data (RXD) 4 Transmit Data (TXD) 5 Signal Ground (SGD) 6 Data Terminal Ready (DTR) 7 Data Set Ready (DSR) 8 Frame Ground (FGD) Figure 7-3 V.35 personality module pin and signal assignment (all DCE modes except external DCE) 13 1 V.35 25 14 8866 This adapter is used for internal and slave DCE modes; external DCE and all DTE modes require the V.35 Type 2 interface adapter (part number 90-1308-07). The signal names in Table 7-4 are the names at the 2902 MainStreet system connector. If a proprietary DB25-to-M34 cable is used, the pin and signal assignments at the M34 end of the DB25-to-M34 cable may be different. See section 7.3 for pin and signal assignments. Table 7-4 V.35 personality module pin and signal assignment (all DCE modes except external DCE) Pin number Signal name (if 2902 MainStreet circuit is DCE) 1 SCT(B) 2 RXD(A) (1 of 2) 7-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Pin number Signal name (if 2902 MainStreet circuit is DCE) 3 SCR(B) 4 DSR 5 CTS 6 nc 7 TXD(B) 8 nc 9 DTR 10 DCD 11 RTS 12 nc 13 nc 14 SCT(A) 15 RXD(B) 16 SCR(A) 17 nc 18 nc 19 nc 20 TXD(A) 21 nc 22 nc 23 nc 24 FGND 25 SGND (2 of 2) Figure 7-4 V.35 (Type 2) personality module pin and signal assignment (external DCE and all DTE modes) 13 1 V.35 (type 2) 25 14 8867 2902 MainStreet Technical Practices 7-5 May 2002 90-2906-01 7 — Connecting to data devices This interface adapter is used for external DCE and all DTE modes; internal and slave DCE modes require the V.35 interface adapter (part number 90-1308-05). The default mode is DCE. The signal names in Table 7-5 are the names at the 2902 MainStreet system connector. If a proprietary DB25-to-M34 cable is used, the pin and signal assignments at the M34 end of the DB25-to-M34 cable may be different. See section 7.3 for pin and signal assignments. Table 7-5 V.35 (Type 2) personality module pin and signal assignment (external DCE and DTE modes) Pin number Signal name Signal name (if 2902 MainStreet circuit is DCE) (if 2902 MainStreet circuit is DTE) 1 SCT(B) nc 2 RXD(A) TXD(A) 3 SCR(B) XCLK(B) 4DSR DTR 5CTS ALB 6 XCLK(A) SCR(A) 7 TXD(B) RXD(B) 8nc nc 9DTR DSR 10 DCD RTS 11 RTS DCD 12 nc nc 13 nc nc 14 SCT(A) nc 15 RXD(B) TXD(B) 16 SCR(A) XCLK(A) 17 nc nc 18 nc nc 19 XCLK(B) SCR(B) 20 TXD(A) RXD(A) 21 nc nc 22 nc nc 23 nc nc 24 FGND FGND 25 SGND SGND 7-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-5 X.21 personality module pin and signal assignment 8 1 X.21 15 9 8868 The signal names in Table 7-6 are the names at the 2902 MainStreet system connector. The default mode is DCE. If a 1:1 DB15-to-DB15 cable is used, the signal names will be the same at the cable end. Table 7-6 X.21 personality module pin and signal assignment Pin number Configured as DCE Configured as DTE 1 Frame GND Frame GND 2 T(A) R(A) 3 C(A) I(A) 4 R(A) T(A) 5 I(A) C(A) 6 S(A) S(A) 7 nc nc 8 Signal GND Signal GND 9 T(B) R(B) 10 C(B) I(B) 11 R(B) T(B) 12 I(B) C(B) 13 S(B) S(B) 14 nc nc 15 nc nc 2902 MainStreet Technical Practices 7-7 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-6 DNIC and 2B1Q personality module pin and signal assignment 16 16 12 DNIC 8869 Note — Only connector 1 can be used for connecting a DTU to the DNIC or 2B1Q module. In the United Kingdom, leased line connections must be made using typical Krone block or similar connections. As listed in Table 7-7, only the middle pair of wires is used by each connector (the other two pairs are reserved for future use). The signal names are the names at the 2902 MainStreet system connector. If a 1:1 RJ11-to-RJ11 cable is used, the signal names at the cable end will be the same. Table 7-7 DNIC and 2B1Q personality module pin and signal assignment Pin number Signal name 1 nc 2 nc 3 Ring 4 Tip 5 nc 6 nc Figure 7-7 Codirectional G.703 personality module pin and signal assignment 18 18 12 Codirectional 8865 7-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Table 7-8 Codirectional G.703 personality module pin and signal assignment Pin number Signal 1 Receive 2 Receive 3 nc 4 Transmit 5 Transmit 6 nc 7 nc 8 nc Procedure 7-1 To connect to data devices 1 Assemble the appropriate cable and adapter for your data device, as described in this section. 2 Connect one end of the cable to the personality module and the other end to your data device, using an adapter if necessary. 3 If you are connecting EIA/TIA-232 devices, use a 16 AWG common return ground to connect the telecom safety earth of each EIA/TIA-232 device to the signal ground point on the rear panel. 7.2 Assembling an adapter for EIA/TIA-232 connections If you are connecting to EIA/TIA-232 data equipment that has a DB25 port, you need a 1:1 RJ45-to-RJ45 cable and an RJ45-to-DB25 adapter. The adapter is either pre-configured (if purchased from us) or user-configurable. Figure 7-8 shows a user-configurable RJ45-to-DB25 adapter. Figure 7-8 User-configurable RJ45-to-DB25 adapter Cable To data equipment Adapter Headshell connector 2900 2902 MainStreet Technical Practices 7-9 May 2002 90-2906-01 7 — Connecting to data devices RJ45-to-DB25 adapter pin and signal assignment Figures 7-9 to 7-16 illustrate eight RJ45-to-DB25 adapter configurations. The figures show the inside of a female adapter connector. Select the figure that matches the adapter application (for example, straight-through CD), or the mode configuration of your EIA/TIA-232 circuit and data device (for example, synchronous DCE slave mode). Use these figures as follows. • Pin 6 on the RS-232 personality module is the DTR lead at the 2902 MainStreet system. The headshell wire is yellow if the adapter is a standard proprietary user-configurable adapter. • The insertion pin on the yellow wire inserts into hole number 24 on the inside of a female connector. The data device name for this lead is XCLK. • Adapter holes numbered 8, 20 and 6 are short circuited together with jumpers. • Headshell pin 7 (DSR) is spliced and goes to adapter pins 17 (SCR) and 15 (SCT). Assembly notes Figures 7-9 to 7-16 can also be used to determine pin and signal assignments for the data equipment side of the adapter. Note the following before you assemble an adapter. • If you have a standard proprietary user-configurable adapter, use the colors indicated in the figure to identify the headshell wires. • If you do not have a standard proprietary user-configurable adapter, you must determine and identify which headshell wires correspond to the EIA/TIA-232 personality module pins. • Each figure shows the inside of a female adapter connector; if you have a male adapter connector, the location of the numbered adapter connector holes differs from the figure. Use the hole numbers, not the hole locations, as your guide when configuring a male adapter connector. 7-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-9 EIA/TIA-232 sync DCE slave mode configuration 13 25 12 XCLK 24 11 23 10 22 9 6 DTR (yellow) 21 5 SGD (green) DCD 8 1 HOUT (blue) DTR 20 7 DSR (brown) SGND 7 2 HIN (orange) 19 3 RXD (black) DSR 6 4 TXD (red) 18 8 FGD (white) CTS 5 SCR 17 RTS 4 16 3 RXD SCT 15 2 TXD 14 GND 1 Inside of female adapter connector 2937 2902 MainStreet Technical Practices 7-11 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-10 EIA/TIA-232 sync DCE external mode configuration 13 25 12 24 XCLK 11 23 10 22 9 6 DTR (yellow) 21 5 SGD (green) DCD 8 1 HOUT (blue) DTR 20 7 DSR (brown) 7 SGND 2 HIN (orange) 19 3 RXD (black) DSR 6 4 TXD (red) 18 8 FGD (white) CTS 5 SCR 17 RTS 4 16 3 RXD SCT 15 2 TXD 14 GND 1 Inside of female adapter connector 2940 7-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-11 EIA/TIA-232 sync DTE external or DTE slave mode configuration 13 25 12 XCLK 24 11 23 10 22 9 7 DSR (brown) 21 2 HIN (orange) 8 DCD 5 SGD (green) DTR 20 6 DTR (yellow) SGND 7 1 HOUT (blue) 19 4 TXD (red) DSR 6 3 RXD (black) 18 8 FGD (white) 5 SCR 17 4 RTS 16 3 RXD 15 2 TXD 14 GND 1 Inside of female adapter connector 9079 Note — In Figure 7-11, for DTE slave mode, SCT must be phase-locked to SCR. 2902 MainStreet Technical Practices 7-13 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-12 EIA/TIA-232 sync DTE internal mode configuration 13 25 12 XCLK 24 11 23 10 22 9 7 DSR (brown) 21 5 SGD (green) 8 6 DTR (yellow) DTR 20 1 HOUT (blue) SGND 7 4 TXD (red) 19 2 HIN (orange) DSR 6 3 RXD (black) 18 8 FGD (white) 5 SCR 17 4 RTS 16 3 RXD SCT 15 2 TXD 14 GND 1 Inside of female adapter connector 2942 Note — In Figure 7-12, SCR and SCT must be frequency locked. 7-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-13 Straight-through configuration (EIA/TIA-232 asynchronous in DCE mode) 13 25 12 24 11 23 10 22 9 6 DTR (yellow) 21 5 SGD (green) 8 7 DSR (brown) DTR 20 1 HOUT (blue) SGND 7 2 HIN (orange) 19 3 RXD (black) 6 DSR 4 TXD (red) 18 8 FGD (white) 5 CTS 17 RTS 4 16 RXD 3 15 TXD 2 14 1 GND Inside of female adapter connector 2943 2902 MainStreet Technical Practices 7-15 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-14 Straight-through CD configuration (EIA/TIA-232 asynchronous in DCE mode) 13 25 12 24 11 23 10 22 9 21 1 HOUT (blue) 8 DCD 6 DTR (yellow) DTR 20 5 SGD (green) SGND 7 7 DSR (brown) 19 3 RXD (black) DSR 6 4 TXD (red) 18 8 FGD (white) CTS 5 17 RTS 4 16 RXD 3 15 TXD 2 14 1 GND Inside of female adapter connector 2938 7-16 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-15 Null-modem configuration (EIA/TIA-232 asynchronous in DTE mode) 13 25 12 24 11 23 10 22 9 7 DSR (brown) 21 5 SGD (green) 8 6 DTR (yellow) DTR 20 2 HIN (orange) SGND 7 1 HOUT (blue) 19 4 TXD (red) 6 DSR 3 RXD (black) 18 8 FGD (white) 5 CTS 17 RTS 4 16 RXD 3 15 TXD 2 14 1 GND Inside of female adapter connector 2939 2902 MainStreet Technical Practices 7-17 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-16 Null-modem CD configuration (EIA/TIA-232 asynchronous in DTE mode) 13 25 12 24 11 23 10 22 9 2 HIN (orange) 21 7 DSR (brown) 8 DCD 5 SGD (green) DTR 20 6 DTR (yellow) SGND 7 1 HOUT (blue) 19 4 TXD (red) DSR 6 3 RXD (black) 18 8 FGD (white) 5 17 RTS 4 16 3 RXD 15 2 TXD 14 GND 1 Inside of female adapter connector 2944 Procedure 7-2 To configure an adapter 1 Locate the appropriate adapter configuration in Figures 7-9 to 7-16. 2 Using the adapter configuration figure as a guide, insert the pins of the headshell wires part way into the holes on the inside of the adapter connector (see Figure 7-17). Splice and short circuit (jumper) connections as indicated in the configuration figure. Figure 7-17 Inserting pins 2949 7-18 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices 3 Verify pin placement and insert the pins all the way. 4 Cut the insertion pin off any unused lead and fold the wire into the adapter headshell (see Figure 7-18). Figure 7-18 Folding in unused wires 2950 5 Rotate the adapter connector 180° (to facilitate closing the adapter) (see Figure 7-19). Figure 7-19 Rotating the adapter connector o 180 2951 6 Snap the adapter connector into the headshell (see Figure 7-20). 2902 MainStreet Technical Practices 7-19 May 2002 90-2906-01 7 — Connecting to data devices Figure 7-20 Closing the adapter 2952 7.3 DB25-to-M34 cable pin and signal assignment For V.35 DCMs, DB25-to-M34 cables are available for connecting the personality module to a data device that uses an M34 connector. (Do not use 90-0360-01 DB25-to-M34 cabling with the system because this cabling does not support all the system clocking modes.) The pin and signal assignments at the M34 end of the cable are given in Figures 7-21 to 7-23 (pin and signal assignments at the personality module connector are given in Figures 7-3 and 7-4). Figure 7-21 M34 pin and signal assignment for V.35 data application (DCE internal and slave modes) A PGND SGND B RTS CTS D C DCD F E DSR J DTR nc H nc nc L K nc N M nc TXD(A) RXD(A) R P TXD(B) RXD(B) T S SCR(A) nc V U nc SCR(B) X W SCT(A) nc Z Y nc BB AA SCT(B) nc nc DD CC nc FF EE nc nc nc JJ HH nc nc LL KK nc NN MM nc 2964 7-20 2902 MainStreet Technical Practices 90-2906-01 May 2002 7 — Connecting to data devices Figure 7-22 M34 pin and signal assignment for V.35 data application (DCE external mode) (Type 2 V.35/DB25 adapter) PGND SGND B A CTS D C RTS DSR DCD F E J DTR nc H nc K nc L N M nc nc TXD(A) RXD(A) R P RXD(B) T S TXD(B) XCLK(A) SCR(A) V U XCLK(B) SCR(B) X W nc Z SCT(A) Y SCT(B) nc BB AA nc nc DD CC nc FF EE nc nc nc JJ HH nc LL KK nc NN nc nc MM 2945 Figure 7-23 M34 pin and signal assignment for V.35 data application (DTE modes) (Type 2 V.35/DB25 adapter) SGND B A PGND nc D C RTS DSR DCD F E nc J H DTR nc nc L K M nc nc N RXD(A) TXD(A) R P TXD(B) RXD(B) T S XCLK(A) SCR(A) V U SCR(B) X W XCLK(B) nc nc Z Y nc BB AA nc nc CC nc DD FF nc nc EE nc nc JJ HH nc nc LL KK nc nc NN MM 2946 2902 MainStreet Technical Practices 7-21 May 2002 90-2906-01 7 — Connecting to data devices 7-22 2902 MainStreet Technical Practices 90-2906-01 May 2002 8 — Connecting node management equipment 8.1 Node management equipment connections 8-2 2902 MainStreet Technical Practices 8-1 May 2002 90-2906-01 8 — Connecting node management equipment 8.1 Node management equipment connections Node management equipment connects to the 2902 MainStreet system through one of two serial ports. The ports use RJ45 connectors, labeled Modem and Terminal. Figure 8-1 identifies these connectors. Figure 8-1 Serial port connectors I EDG Sig/Gnd O P1 P2 Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display Modem Terminal 10424 Node management equipment connects directly to the Terminal connector. The NMTI refers to Terminal as serial port 1. The default setting for the Terminal connector is DCE. Node management equipment connects indirectly to the Modem connector (through a modem). The NMTI refers to Modem as serial port 2. The default setting for the Modem connector is DTE. Once you have established a node management session, you may change the serial port configuration for the 2902 MainStreet system. For information on establishing a node management session, see chapter 10 in Configuration. Note — If you plan to manage the 2902 MainStreet system from a 5620 NM, consult the network manager documentation for instructions on installing network management equipment. Modem connector pin and signal assignment Figure 8-2 shows the pin and signal assignment of the Modem connector. The arrows indicate signal direction. 8-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 8 — Connecting node management equipment Figure 8-2 Pin and signal assignment for the Modem connector 1 CTS 2 RTS 3 RXD 4 TXD 5 SGND* 6 DTR 7 DSR 8 *RS-232 signal ground 8991 Terminal connector pin and signal assignment Figure 8-3 shows the pin and signal assignment of the Terminal connector. The arrows indicate signal direction. Figure 8-3 Pin and signal assignment for the Terminal connector 1 not used 2 not used 3 RXD 4 TXD 5 SGND* 6 not used 7 not used 8 *RS-232 signal ground 8992 Procedure 8-1 To connect to the Modem and Terminal connectors Tools and equipment required: • node management terminal, such as: • a VT100 or compatible terminal • a personal computer with VT100 terminal emulation software • a personal computer with Craft Interface • a computer running 5620 NM software • cable (RJ45-to-RJ45) • RJ45 adapters (if necessary) Adapters and cables can be obtained from your sales representative. If your node management equipment does not have an RJ45 connector, you must use an adapter. 2902 MainStreet Technical Practices 8-3 May 2002 90-2906-01 8 — Connecting node management equipment If connecting to a rack-mount slide assembly, create a service loop long enough to allow the drawer to be fully opened. See section 4.3. 1 Connect one end of an RJ45 cable to the Modem or Terminal connector. Use Modem for an indirect connection and Terminal for a direct connection. 2 Connect the other end of the RJ45 cable to the modem or the node management terminal. 3 Power up the node management terminal and ensure that its serial communication settings are compatible with the 2902 MainStreet system serial port default settings. The serial port default settings for the 2902 MainStreet system are: • 1200 b/s (Modem) • 9600 b/s (Terminal) • 8 data bits • 1 stop bit • no parity • no local echo 4 Power up the 2902 MainStreet system. For information on powering up the unit, see chapter 4. 8-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 9 — Connecting to external alarm equipment 9.1 External alarm connections 9-2 2902 MainStreet Technical Practices 9-1 May 2002 90-2906-01 9 — Connecting to external alarm equipment 9.1 External alarm connections The external alarm connector allows connection to other devices for the following purposes: • to monitor an external circuit or piece of equipment that is part of your network (for example, an uninterruptible power source) by detecting the opening or closing of the Alarm In contacts • to activate an external alarm device, such as a light or buzzer, using the Event Status or the System Status relay If connecting permanently to a rack-mount slide assembly, create a service loop long enough to allow the drawer to be fully opened (see section 4.3). Figure 9-1 identifies the Alarm connector. Figure 9-1 Alarm connector I EDG Sig/Gnd O P1 P2 Slot 2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display Alarm 10434 The Alarm In pins connect to the relay contacts of the external device. The state of the Alarm In pins is configured through an NMTI session to detect normally open or normally closed contacts. The opening or closing of the Alarm In pins causes the alarm “External Alarm Raised” to appear in an alarm queue. The Event and Status relay contacts (pins) connect to the drive lines on the external devices. The Event Status and the System Status relays activate the external alarm devices. When there are unacknowledged alarms in the major alarm queue, the Event Status LED illuminates and the Event Status relay closes. When a system problem occurs, the System Status LED illuminates and the System Status relay closes. Pin and signal assignments The external alarm connector (labeled Alarm), is an RJ11 connector with the pin and signal assignments shown in Figure 9-2. Figure 9-3 shows the alarm circuit. 9-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 9 — Connecting to external alarm equipment Figure 9-2 Alarm connector pin and signal assignment 1 Alarm in 2 Alarm in 3 To system status alarm device 4 To system status alarm device 5 To event status alarm device 6 To event status alarm device 8986 Figure 9-3 External alarm circuit 2902 MainStreet External node Alarm equipment 1 Alarm Monitored 2 in device 3 System To external status 4 device relay 5 Event To external 6 status device relay 8981 Table 9-1 lists the Event status and System status relay contact ratings. The external device should be capable of closing or opening the relays. Table 9-1 External alarm connector contact ratings Rating Resistive load Maximum operating voltage 60 V ac, 60 V dc Maximum operating current 0.4 A 2902 MainStreet Technical Practices 9-3 May 2002 90-2906-01 9 — Connecting to external alarm equipment Procedure 9-1 To make connections for monitoring external alarm devices Tools required: • one RJ11-to-spade lug cable, or • one RJ11-to-RJ11 cable and a distribution box 1 Attach one end of the RJ11 cable to the Alarm connector. 2 Attach the other end of the cable. a For an RJ11-to-spade lug cable, connect pins 1 and 2 to the monitoring terminals of your device. Pin 1 is ground. b For an RJ11-to-RJ11 cable with a distribution box, connect the RJ11 connector to the box, then connect the proper box terminals to the monitoring terminals of your device. Procedure 9-2 To make connections for activating external alarm devices Tools required: • one RJ11-to-spade lug cable, or • one RJ11-to-RJ11 cable and a distribution box 1 Attach one end of the RJ11 cable to the Alarm connector. 2 Attach the other end of the cable. a For an RJ11-to-spade lug cable, connect pins 3 and 4, or pins 5 and 6 to the activation terminals of your device. b For an RJ11-to-RJ11 cable with a distribution box, connect the RJ11 connector to the box, then connect the proper box terminals to the activation terminals of your device. 9-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 10 — Node management 10.1 Node management overview 10-2 10.2 Logging in to the NMTI 10-2 10.3 NMTI screen display 10-4 10.4 NMTI main menus 10-6 10.5 Softkey menus 10-7 10.6 Logging out of the NMTI 10-9 2902 MainStreet Technical Practices 10-1 May 2002 90-2906-01 10 — Node management 10.1 Node management overview The 2902 MainStreet system is managed through a node management session using the NMTI, the Craft Interface Node Manager or a 5620 NM. These are menu-driven software programs used to configure, operate, monitor and maintain the 2902 MainStreet system. NMTI The NMTI is a user interface that resides on the Control card. It allows you to manage the 2902 MainStreet system with a VT100-compatible terminal. Craft Interface Node Manager The Craft Interface Node Manager is a user interface software package that runs on a DOS-compatible PC; it includes modem support for access to remote nodes over the PSTN. For information on using the Craft Interface Node Manager, see the Craft Interface User Guide. 5620 Network Manager The 5620 NM allows you to initiate a node management session through a computer running the 5620 NM software. The network manager and the 2902 MainStreet system communicate using the CPSS protocol, which is a proprietary protocol similar to X.25. The network manager can connect directly to the 2902 MainStreet system. It can also connect indirectly using a modem. For information on using the 5620 NM for node management, see the appropriate network manager documentation. 10.2 Logging in to the NMTI The following steps describe the initial login procedure once the node management device has been connected as described in Installation, chapter 8. Procedure 10-1 To log in to the NMTI Steps 1 to 6 are necessary only if this is the first login, or if the terminal is used infrequently. In a regularly used system, the login procedure starts at step 7. Note — The NMTI uses a lockout feature that limits access to one user at a time. 1 Check that the power cables for both the 2902 MainStreet system and the node management terminal are plugged into a power source. 10-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 10 — Node management 2 Check that the cable connecting the terminal to the 2902 MainStreet system is properly installed. 3 Set the power switch on the 2902 MainStreet system to the On (|) position. The unit performs diagnostic self-tests, as described in Installation, section 4.4. If these tests last more than 1 minute, see Maintenance, chapter 24. 4 Set the power switch on the node management terminal to the On position. 5 Check that the terminal is set up for: • 8 data bits • 1 stop bit • no parity • no local echo • 9600 b/s 6 Wait until the diagnostic self-tests are finished. The self-tests are over when the seven-segment display at the rear panel flashes the letter P. If the display flashes the letter F, there is a problem. See section 4.4 for information on self-tests. 7 Press the ↵ ( or ) key on the keyboard at approximately 1-second intervals until a startup message similar to the one below appears. Alcatel 2902 MainStreet, Generic 82211-ab-cd Copyright 1996, 1997 Alcatel All rights reserved. where ab-cd is the current software generic If the message does not appear, check the connections and setup of the node management terminal. 8 At the “Enter level” prompt, type your access level number and press the ↵ key. See section 11.5 for information on access levels. If this is the initial session, type <5> and press ↵. Level 5 users have read and write access to all areas of the NMTI. If you do not enter an access level within approximately 5 minutes, the screen displays the message “Session idle timeout. Connection closed”, and the session times out. 9 Enter your password at the password prompt and press ↵. If this is the initial session, type . This is the default password for all levels. The password is not case sensitive and is not displayed on the screen. If the password is entered incorrectly, the system responds with “Incorrect Password”. Press s↵ to begin again at step 7. If you do not enter a password within approximately 5 minutes, the screen displays the message “Session idle timeout. Connection closed”, and the session times out. Upon successful login, the system displays the NMTI top-level menu as shown in Figure 10-1. 2902 MainStreet Technical Practices 10-3 May 2002 90-2906-01 10 — Node management Figure 10-1 NMTI top-level menu 2902 MainStreet 82211-ab-cd Alarms:6 No Date 8:47R 1-CONFIG 2-HOUSE 3-MAINT 4-STATS 5-ALARMS 6- 7- 8- 9-QUIT 0- 10.3 NMTI screen display A sample NMTI screen is shown in Figure 10-2. The screen has five main areas: • header line • data area • command line • diagnostics line • softkey area 10-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 10 — Node management Figure 10-2 NMTI screen display Header line 2902 MainStreet 82211-ab-cd Alarm:6 No Date 8:46R * Configured Installed Status Name Options M01 DNIC DNIC OK Data area Command line CONFIG POSITION 1 Diagnostics line 1-TYPE 2-NAME 3- 4- 5- Softkey area 6- 7- 8-CANCEL 9-QUIT 0- 10435 Note — The actual menu displays may differ slightly from those shown in this manual. Header line The header line is located at the top of the screen. It displays: • product name • software generic and revision number • node name • number of alarms in the major alarm queue • date and time To assign the node name and set the date and time, see sections 11.2 and 11.3. Data area The data area occupies the 18 lines below the header line. It displays information associated with the current menu, for example, configuration information or statistical reports. Command line The command line is located directly below the data area. It displays user input—either the selected softkey or keyboard entries. 2902 MainStreet Technical Practices 10-5 May 2002 90-2906-01 10 — Node management Diagnostics line The diagnostics line is under the command line. It displays information relevant to the user input, such as: • prompts • warnings • error messages • valid ranges for numeric parameters Softkey area The softkey area is at the bottom of the screen. Softkeys represent the functions available for the particular menu. Functions are selected by pressing the associated function key (F1 to F10) or number key (1 to 9 and 0). 10.4 NMTI main menus The top-level menu displays the main menu titles in the softkey area of the screen. To access a menu, enter the relevant softkey (either a function key or number key). Configuration Configuration functions include: • programming a primary rate link • configuring the circuits on the primary rate link • configuring the interface modules • defining circuit cross-connections • specifying the system timing source and recovery mechanism Housekeeping Housekeeping functions include: • setting the date and time • specifying the node name • configuring the serial ports • assigning NMTI access levels and passwords 10-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 10 — Node management Maintenance Maintenance functions include: • performing system diagnostics • monitoring circuit status • performing loopbacks • testing circuits • backing up and restoring the system database data • checking the status of the system NVM Statistics Statistical functions include viewing and clearing performance monitoring statistics. Alarms The NMTI continuously monitors the system for abnormal conditions and significant events, and displays alarms when they are generated. Alarm functions include: • viewing and editing alarms • logging alarms • classifying alarms by priority • configuring external alarm devices The menu functions are described in detail in the following chapters. 10.5 Softkey menus For each menu function described in this manual, a softkey menu is provided to show the path to the function. Text in the form indicates user input, and ↵ indicates the (or ) key. Default settings are marked with an asterisk (*). To simplify the softkey structure, general menu functions are typically not shown on the softkey menus. These functions are described later in this section. 2902 MainStreet Technical Practices 10-7 May 2002 90-2906-01 10 — Node management Procedure 10-2 Sample softkey menu A sample softkey menu is shown below. CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE SYNC*/ASYNC SK000495 Note — Some softkeys toggle between two states (for example, ENABLE/DISABLE). The toggle position not shown is selected. General menu functions General menu functions are functions available to most menus. CANCEL (F8 or 8) The Cancel function undoes the last command or instruction entered. QUIT (F9 or 9) If you select Quit from the main menu, you are logged out. If you select Quit from any other menu, you are returned to the main menu. PROCEED (F10 or 0) The Proceed function executes a command or instruction. The system always prompts you to proceed when required. If the system is waiting for user input and you want to enter a softkey function, press and then the softkey. For example, to cancel or quit a function while the system is waiting for user input, enter <8> or <9>. If you enter only <8> or <9>, the system assumes that it is part of the user input, and will add the number to the command line. More The More function appears when there are more functions than softkeys available for the menu. The additional functions appear under the more menu. 10-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 10 — Node management SHOW functions Functions such as SHOW_ALL and SHOW_TABLE are referred to as display functions. They are used to display information while you are entering a command, without interrupting the procedure. Erasing the buffer Up to 100 characters can be stored in the keyboard buffer, allowing you to type in commands or other key sequences before being prompted for them. To clear the buffer, hold down the key and type . All unexecuted commands are canceled when the buffer is cleared. Refreshing the display To refresh the terminal screen, press . Refreshing the screen is useful when: • a database verification is in progress • you are monitoring system alarms and want to update the information displayed • you are examining the signaling leads • a transmission error or some other event corrupts the displayed information 10.6 Logging out of the NMTI You can log out manually, or, to prevent unauthorized use of an unattended terminal, you can program the length of time after which the NMTI automatically quits if there has been no activity. Logging out manually To log out from the main menu, select Quit (F9 or 9). To log out from any other menu, select Quit to return to the main menu, then select Quit again to log out. Procedure 10-3 To log out automatically Automatic logouts can be set to 5, 10, 15 or 30 minutes, or None. If None is selected, the session remains connected until you log out manually. HOUSE — MORE — SESSN_TIME 5_MIN 10_MIN 15_MIN 30_MIN* NONE SK000465 * Default If the connection is dropped, the NMTI session is terminated automatically. 2902 MainStreet Technical Practices 10-9 May 2002 90-2906-01 10 — Node management 10-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters 11.1 System serial port parameters 11-2 11.2 Date and time 11-6 11.3 Node number and node name 11-7 11.4 Network Operations Center number 11-8 11.5 Access levels 11-9 11.6 Passwords 11-13 11.7 Viewing node parameters 11-14 2902 MainStreet Technical Practices 11-1 May 2002 90-2906-01 11 — Node parameters 11.1 System serial port parameters The two serial ports can be configured for device type, baud rate and flow control. Serial port 1 (labeled Terminal) is configured as a DCE device. Serial port 2 (labeled Modem) is configured as a DTE device. The data format for both ports is 8 data bits, 1 stop bit, no parity and no local echo. Device type Configure the serial port device type to match the type of node management equipment connected to the port. If you change the device type of the serial port that is communicating with the node management equipment, the display is updated, but the change does not take effect until you log out of the node. Three types of node management equipment can be connected to a serial port: • a VT100-compatible terminal (VT100) • a printer (PRINTER) • a computer (VT100, CPSS, CPSS_MODEM) The default for serial port 1 is VT100. The default for serial port 2 is CPSS_MODEM. Typically, serial port 2 connects to a modem that connects to a 5620 NM or a PC running the Craft Interface Node Manager. VT100-compatible terminal A VT100-compatible ASCII terminal can be connected to a serial port either directly or indirectly (remotely through a Hayes-compatible auto-answer modem). The VT100 terminal is used for node management sessions. An EIA/TIA-232 compatible device, such as a PC, must be connected to the other serial port for certain node management activities (such as configuration database backup and restore). Printer A serial printer can be locally connected to a serial port so that alarms can be printed out; see section 25.6 in Maintenance for more information about how to enable or disable the printer. 11-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters Computer A PC can be connected to a serial port either directly or indirectly (remotely through a Hayes-compatible auto-answer modem). The computer must be running one of the following software packages: • terminal emulation software A PC running VT100-terminal emulation software can manage the node using the NMTI. An EIA/TIA-232 compatible device, such as a PC, must be connected to the other serial port for certain node management activities (such as configuration database backup and restore). • Craft Interface Node Manager A PC running the Craft Interface Node Manager software can manage the node using the Craft Interface Node Manager. • 5620 NM A PC or a Sun workstation running 5620 NM software can manage the node using the NMTI. The node manager is sometimes referred to as the NOC. A 5620 NM connected directly to a 2902 MainStreet system can back up, verify and restore the configuration database; connected indirectly (via modem), it can back up and verify, but not restore. For more details, see chapter 30 in Maintenance. • communications software A PC running communications software can manage the node using the NMTI. Table 11-1 lists guidelines for selecting serial port device types. Table 11-1 Guide for selecting device types Device type Select A VT100-compatible terminal connected directly or indirectly VT100 A computer running terminal emulation software connected directly or indirectly VT100 A computer running communications software connected directly or directly VT100 A computer running 5620 NM software or the Craft Interface Node Manager, CPSS connected directly A printer PRINTER A computer running 5620 NM software or the Craft Interface Node Manager, CPSS_MODEM connected through a modem 2902 MainStreet Technical Practices 11-3 May 2002 90-2906-01 11 — Node parameters Procedure 11-1 To set the device type HOUSE SER_PORT_1 SER_PORT_2 PORT_TYPE VT100* CPSS PRINTER CPSS_MODEM** SK000466 * Default for serial port 1 ** Default for serial port 2 Baud rate Baud rate is the speed of communication between the unit and the node management equipment. Set the baud rate to match the rate of the device that is connected to the serial port. Each serial port supports six baud rates: • 300 b/s • 600 b/s • 1200 b/s • 2400 b/s • 4800 b/s • 9600 b/s The default for serial port 1 is 9600 b/s; for serial port 2 it is 1200 b/s. If you use the NMTI to back up, verify or restore the configuration database to (or from) a separate computer (one that is not managing the unit), flow control is required for baud rates of 2400 b/s or higher. Flow control is discussed later in this section. If you change a serial port baud rate, the change takes effect when you select PROCEED. You must also change the baud rate of the node management equipment to match the new baud rate of the serial port. 11-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters Procedure 11-2 To set the baud rate HOUSE SER_PORT_1 SER_PORT_2 BAUD_RATE 300 600 1200** 2400 4800 9600* SK000467 * Default for serial port 1 ** Default for serial port 2 Flow control Bidirectional flow control can be set for both serial ports. The three flow control settings are: • software flow control (XON/XOFF) • hardware flow control (DTR) • no flow control (NONE) The default is no flow control. Serial port 1 supports only software flow control; serial port 2 supports software and hardware flow control. If you use the NMTI to back up, verify or restore the configuration database to (or from) a separate computer (one that is not managing the unit), flow control is required for baud rates of 2400 b/s or higher. Note — Setting the flow control has no effect on serial ports configured as port type CPSS or CPSS_MODEM; that is, flow control is not required for backing up, verifying or restoring the configuration database to a computer running 5620 NM software or the Craft Interface Node Manager. 2902 MainStreet Technical Practices 11-5 May 2002 90-2906-01 11 — Node parameters Procedure 11-3 To set the flow control HOUSE SER_PORT_1 SER_PORT_2 FLOW_CTRL FLOW_CTRL NONE* XON/XOFF DTR NONE* XON/XOFF SK000468 * Default 11.2 Date and time The date and time are user-configurable. Date No Date appears in the header line until the date is set for the first time or after a system reset or power failure. The format for entering the date is ; the hyphens must be entered. For example, January 9, 2002 is entered as <09-JAN-2002>. Time Until the time is set, the time elapsed since the last system reset appears in the header line in the form hh:mmR. For example, 4:03R indicates that 4 hours and 3 minutes have passed since the last system reset. When the time is set, real time appears in 12-hour format, followed by the letter A or the letter P to indicate a.m. or p.m., respectively. The format for entering the time is or . Time can be entered in either 12-hour or 24-hour format, but is displayed only in 12-hour format. For example, 4:30 p.m. is entered as <4:30P> or <16:30>. If you enter the time in 12-hour format without an or

, the system assumes an . 11-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters Procedure 11-4 To set the date and time HOUSE DATE TIME ↵ or ↵ SK000469 where dd is the date 1 to 31 MMM is the first three letters of the month yyyy is the four digits of the year hh is the hour (1 to 12 or 0 to 23) mm is the minutes (1 to 59) 11.3 Node number and node name A unique node number (CPSS address) identifies each node in a network. The system can also be given a node name. The node number and name are not saved as part of a configuration database backup. That is, when a database is loaded into a node from backup, the number and name return to their default values (unassigned). This helps prevent two or more nodes in a network from having the same number. See chapter 30 in Maintenance for more information. Node number The node number is the CPSS address used to uniquely identify your unit within a network managed by a proprietary network manager. If the unit is part of a network managed by a non-CPSS capable network manager, the node number does not need to be set. The node number can be any number from 1 to 999, inclusive. When assigned, it is displayed in the data area. For a node number to take effect, you may have to restart the system; the NMTI displays a message if this is the case. Caution — When the system is restarted, all active calls are dropped, in-progress maintenance operations are ended and the NMTI session with the system is ended. The restart does not affect configuration settings. Node name The unit may be assigned a 12-character name that appears in the header. You can delete the node name by pressing ↵ when you are prompted to enter a name. 2902 MainStreet Technical Practices 11-7 May 2002 90-2906-01 11 — Node parameters Procedure 11-5 To set the node name and number HOUSE NODE_NAME MORE ↵ NODE_NUM ↵ SK000470 where node name is up to 12 alphanumeric characters, upper case only, with no spaces or underscores node number is any unique number from 1 to 999 11.4 Network Operations Center number The NOC is the computer running 5620 NM system software. The NOC number is the telephone number of the modem serving the NOC computer. The unit uses the NOC number to establish communications with the NOC via the PSTN should the primary rate link fail. If the 2902 MainStreet system is not part of a network controlled by 5620 NM software, the NOC number does not need to be set. The NOC number is displayed in the data area if the user has read-only or read/write access to the NOC_NUM softkey (see Table 11-2). When setting the number, include any prefix digits, such as area code, that would be required if the call were dialed manually from a telephone. The number can include Hayes AT-compatible modem dial modifiers (such as a comma (pause), W (wait for dial tone) and @ (wait for silence). For example, to dial a long distance number from a PBX that provides a second dial tone after the digit 9, use 9W1-613-591-3600. By default, the unit instructs its modem to dial the NOC number using dial pulsing. For the modem to dial using DTMF, the NOC number must be preceded by the characters DT. By default, no NOC number is assigned. Procedure 11-6 To set the NOC number HOUSE — MORE — NOC_NUM — ↵ where number is the NOC number 11-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters 11.5 Access levels Access levels are entered as part of the login process, allowing different users to access different functions. The six access levels are numbered 5 to 0, with level 5 being the highest level. A separate password can be defined for each level, except level 0. Only level 5 users can define and modify access level definitions, and change passwords. Access for levels 4 to 1 can be defined as follows: • no access to the function (NO_ACCESS) • read-only access (READ_ONLY) • read/write access (READ/WRITE) The default is read/write access. Level 5 Level 5 is intended for use by system managers, providing read and write access to all functions. Level 5 cannot be redefined but it can be assigned a password. Levels 4 to 1 Levels 4 to 1 are used to meet the requirements of the following types of user. Table 11-2 lists suggested access level definitions. • Level 4 (system manager) The user is managing housekeeping functions related to user access and Control card non-volatile memory maintenance functions. • Level 3 (network configuration operator) The user configures network interfaces, signaling, data processing applications, system serial ports, date and time. • Level 2 (network performance operator) The user manages alarms, statistics, diagnostic tests and circuit or position maintenance. • Level 1 (network performance personnel) The user collects information on abnormal system conditions or significant events. Level 0 Level 0 is a read-only access defined for one or both serial ports. Level 0 users have access to all softkeys except PROCEED. When enabled, level 0 access has no effect on access levels 5 to 1. If a serial port is configured for level 0 access, a user may log in at level 0 or any other level. If a serial port is configured for no level 0 access, users must enter a level (5 to 1) and password to log on. 2902 MainStreet Technical Practices 11-9 May 2002 90-2906-01 11 — Node parameters Level 0 cannot be redefined or assigned a password. Table 11-2 Suggested access level definitions (1) Softkeys Suggested definition 1 2 3 4 CONFIG POSITION RO RO R/W R/W CIRCUIT RO RO R/W R/W CONNECT RO RO R/W R/W SYNC # RO RO R/W R/W HOUSE SER_PORT_1 RO RO R/W R/W SER_PORT_2 RO RO R/W R/W DATE RO R/W R/W R/W TIME RO R/W R/W R/W NODE_NAME RO RO RO R/W MORE SESSN_TIME RO RO RO R/W (2) CHNG_PSSWD n/a n/a n/a n/a NODE_NUM RO RO RO R/W NOC_NUM RO RO RO R/W MAINT DIAG RO R/W R/W R/W UNDO_MAINT RO R/W R/W R/W ON_CIRCUIT RO R/W R/W R/W ON_MODULE RO R/W R/W R/W MORE BACKUP RO RO R/W R/W RESTORE RO RO R/W R/W VERIFY RO RO R/W R/W (3) VIEW_NET n/a n/a n/a n/a (3) NVM_DATA n/a n/a n/a n/a STATS QUALITY RO R/W R/W R/W SYNCH RO R/W R/W R/W MAN_CLEAR/ RO R/W R/W R/W AUTO_CLEAR ALARMS MAJ/PROMPT RO R/W R/W R/W MINR/DEFER RO R/W R/W R/W DIAG/IN_STN RO R/W R/W R/W CONFIG RO R/W R/W R/W EXTNL_ALRM RO R/W R/W R/W MORE LOGGING RO R/W R/W R/W Notes (1) n/a = not applicable; RO = read only; R/W = read/write. (2) This softkey appears for level 5 users only. (3) These softkeys are read-only functions. Access level examples For levels 4 to 1, access can be defined for each of the softkeys listed in Table 11-2 except CHNG_PSSWD. 11-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters Access can also be defined at the top-level menu, which is the display that appears immediately after the login. If you define access at the top-level menu as no access, the user can only log out. The access definition for a softkey overrides the access level of any softkeys underneath it if the higher-level access definition is more restrictive. That is, read-only overrides read/write; no access overrides both read-only and read/write. For example, in the following three cases, assume the softkeys under CONFIG have the following access definitions: • POSITION: read/write • CIRCUIT: read/write • CONNECT: read-only • SYNCH: no access Case 1 If CONFIG has read/write access (the least restrictive definition), the access definitions for POSITION, CIRCUIT, CONNECT and SYNCH are as defined. Case 2 If CONFIG is defined as read-only access (more restrictive), it overrides the definitions for POSITION and CIRCUIT. Thus, POSITION, CIRCUIT and CONNECT have read-only access, and SYNCH has no access. Case 3 If CONFIG is defined as no access (the most restrictive), it overrides the definitions for POSITION, CIRCUIT and CONNECT; all four softkeys have no access. Access level definition display The softkey that you are defining appears in the top left corner of the data area, as shown in Figure 11-1 (for example, CONFIG POSITION “??” defines the POSITION softkey). The MORE softkey cannot be defined. If you try to define the access level for ALARMS MORE, only the word ALARMS appears. The data area shows the access definitions for the softkey; it does not indicate any override by a more restrictive definition on another softkey. 2902 MainStreet Technical Practices 11-11 May 2002 90-2906-01 11 — Node parameters Figure 11-1 Node management session screen showing access level definition 2902 MainStreet 82211-ab-cd ELMSTREET Alarms:1 09-JAN-2002 8:40A CONFIG POSITION “??” Level Access Type 1 Read/Write 2 Read/Write 3 Read/Write 4 Read/Write 5 Read/Write CHANGE_ACCESS 1-LEVEL_1 2-LEVEL_2 3-LEVEL_3 4-LEVEL_4 5- 6- 7- 8-CANCEL 9-QUIT 0- Procedure 11-7 To define access levels 4 to 1 1 Select a softkey. For example, to define access to module positions, select: CONFIG — POSITION 2 Enter: LEVEL_1 LEVEL_2 LEVEL_3 LEVEL_4 READ_ONLY READ/WRITE* NO_ACCESS SK000471 * Default The display remains at the same softkey so that you can define the other levels. 3 To define another softkey, select CANCEL. 4 To return to the main menu, select QUIT. 11-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 11 — Node parameters Procedure 11-8 To define access level 0 Level 0 access can be enabled (LEVEL_0) or disabled (NO_LEVEL_0). HOUSE SER_PORT_1 SER_PORT_2 LEVEL_0/NO_LEVEL_0* SK000472 * Default 11.6 Passwords The default password for all levels is “mainstreet”. The passwords for each level can be changed by a level 5 user (except for level 0 which has no password). The CHNG_PSSWD softkey does not appear for users logged on at other levels. Passwords must be between 8 and 12 alphanumeric characters long with no spaces. When the system is first commissioned, it is recommended that you change at least the level 5 password so that the node database is protected. If you make a typing error while entering a password, select CANCEL; the system returns to the previous menu. Access level passwords are not saved as part of a configuration database backup. That is, when a database is loaded into a node, the passwords revert to the default (mainstreet). See chapter 30 in Maintenance for more information on database management. 2902 MainStreet Technical Practices 11-13 May 2002 90-2906-01 11 — Node parameters Procedure 11-9 To set passwords HOUSE — MORE –– CHNG_PSSWD –– ↵ LEVEL_1 LEVEL_2 LEVEL_3 LEVEL_4 LEVEL_5 ↵ ↵ PROCEED SK000473 where level5 password and new password are 8 to 12 alphanumeric characters (default level5 password is “mainstreet”) 11.7 Viewing node parameters You can view the current node parameters by selecting the HOUSE softkey. Figure 11-2 shows the display. Figure 11-2 Node parameter display 2902 MainStreet 82211-ab-cd NEWYORK Alarms:1 09-JAN-2002 8:46A Port Baud Rate Port Type Flow Control Level Zero Access 1 9600 VT100 NONE NO 2 1200 CPSS_MODEM NONE NO Current Port : Serial port one Session Time : 30 Minutes Node Number : Unassigned NOC Number : Unassigned HOUSE 1-SER_PORT_1 2-SER_PORT_2 3-DATE 4-TIME 5-NODE_NAME 6- 7-MORE... 8-CANCEL 9-QUIT 0- 11-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 12 — Module position and circuit configuration 12.1 Module position and circuit identifiers 12-2 12.2 Module position configuration 12-3 12.3 Module position displays 12-4 12.4 Naming a module position 12-8 12.5 Naming a circuit 12-8 12.6 Quick circuit configurations 12-8 12.7 Viewing circuit status 12-9 2902 MainStreet Technical Practices 12-1 May 2002 90-2906-01 12 — Module position and circuit configuration 12.1 Module position and circuit identifiers For NMTI purposes, module positions and circuits have alphanumeric identifiers. Table 12-1 lists the formats and ranges, and gives examples. For example, P2-28 identifies circuit 28 on the primary rate module in module position P2. For interface modules, there is a logical mapping between their physical positions on the Control card (1 and 2) and their NMTI identifiers. Physical position 1 maps to logical position M01 on the NMTI; physical position 2 maps to logical position M09. Thus, all NMTI operations pertaining to position 2 are performed through logical position M09. For example, the second circuit on an RS-232 DCM in physical position 2 is identified by M09-2 (or 9-2). Logical module positions M02 to M08, and M10 to M16, are not user-configurable because they are not physically present. They are automatically reserved by the 2902 MainStreet system when a module capable of super-rate speeds over 128 kb/s (that is, an X.21 or V.35 DCM) is configured in logical positions M01 or M09 (see section 12.2 for more information). Table 12-1 Module position and circuit identifiers Identifier Format Range Examples Module position E1 primary rate p = 1 or 2 (1) Interface or pp = 1 or 9 or or <1> (2) DSP resource — — Circuit E1 primary rate c = 1 to 30 (3) — c = 1 to 31 DNIC, 2B1Q c = A or B <9-B> RS-232 DCM, Codirectional c = 1 or 2 <1-2> DCM X.21 DCM, c = 1 <1-1> V.35 DCM Notes (1) The latter form, , is usually used. (2) The DSP module position is not user-configurable and is configured for a super-rate module by default. (3) A thirty-first circuit is available if CCS is selected as the frame type. Figure 12-1 locates the positions for the primary rate and interface modules on the Control card. 12-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 12 — Module position and circuit configuration Figure 12-1 Module positions on the Control card LIM (P1) LIM (P2) EPROMs 1 2 3 4 Interface module (position 2) Interface module (position 1) Personality modules (Slot 2/Slot 1) Jumper blocks Jumper blocks (J37, J40) (J41, J44) 8840 12.2 Module position configuration Primary rate module positions are not user-configurable (except for the module name). Primary rate modules are recognized by the system during power-up and are automatically added to the configuration database. Interface module positions can be configured before or after the modules are physically installed. However, a position must be configured before its circuits can be configured or connected. Once a module is physically installed, you can configure its position to automatically match the module (AS_PRESENT). Once a position is configured, you can reconfigure it as EMPTY. After a module is installed and configured, its status should be Ok. If it is not, make sure that the module is properly installed. If there is still a problem, check the alarm queue (see chapter 25 in Maintenance). Rather than configure each module position separately, you can configure all positions for the modules currently installed. The positions are configured automatically to match the installed module and are set with default values. A position is not affected if: • it is correctly configured for the installed module type • an empty position is configured for a module type Note — Some modules have variants that are not recognized automatically by the system. The variant is selected during module position configuration. 2902 MainStreet Technical Practices 12-3 May 2002 90-2906-01 12 — Module position and circuit configuration Reserved module positions When logical module positions M01 or M09 are configured for an X.21 or V.35 DCM, the software automatically reserves positions M02 to M08, or M10 to M16 (respectively). This provides two super-rate connections of up to 1024 kb/s each. A single super-rate connection of up to 1920 kb/s is available to position M01 when position M09 is configured as EMPTY. In this case, position M09 is disabled and cannot be configured until position M01 releases it. See section 19.11 for more information on reserved module positions. Empty module positions If logical module positions M01 or M09 are configured for a module that does not support super-rate speeds over 128 kb/s, or as EMPTY, the seven adjacent positions are automatically configured as EMPTY by the software. Procedure 12-1 To configure an interface module position CONFIG — POSITION — ↵ — TYPE AS_PRESENT DATA EMPTY X.21_DCM V.35_DCM RS_232_DCM DNIC CODIRECTIONAL 2B1Q SK000484 where pp is 1 or 9 Procedure 12-2 To configure all interface module positions CONFIG — POSITION — CONFIG_ALL 12.3 Module position displays The node management terminal can display information about module positions in a variety of ways, depending on the softkey selection. It can show information about: • a single position • a group of positions (SHOW_1-8) or (SHOW_9-16) • all positions (SHOW_ALL) 12-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 12 — Module position and circuit configuration Figure 12-2 shows a display for a single position. Figure 12-3 is a sample display showing information on all positions (SHOW_ALL). It excludes module name and option information. The display for a group of positions is similar to the SHOW_ALL display. Table 12-2 describes the column headings and explains the status options. The DSP module position is automatically configured to support super-rate speeds because there are no user-installable DSP resource modules currently available for the 2902 MainStreet system. Figure 12-2 Sample module positions display (single module position) 2902 MainStreet 82211-ab-cd Alarms:8 No Date 3:21R # Configured Installed Status Name Options M09 DNIC DNIC Ok CONFIG POSITION 9 1-TYPE 2-NAME 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- 2902 MainStreet Technical Practices 12-5 May 2002 90-2906-01 12 — Module position and circuit configuration Figure 12-3 Sample module positions display (SHOW_ALL) 2902 MainStreet 82211-ab-cd Alarms:6 No Date 0:13R # Configured Installed Stat # Configured Installed Stat --------------------------------- --------------------------------- M01 X21_DCM X21_DCM Ok M09 DNIC DNIC Ok M02 RESERVED - Ok M10 EMPTY - - M03 RESERVED - Ok M11 EMPTY - - M04 RESERVED - Ok M12 EMPTY - - M05 RESERVED - Ok M13 EMPTY - - M06 RESERVED - Ok M14 EMPTY - - M07 RESERVED - Ok M15 EMPTY - - M08 RESERVED - Ok M16 EMPTY - - P1 E1 E1 Ok P2 E1 E1 Ok DSP SUPERRATE SUPERRATE CONFIG POSITION “??” Enter Module Position Number 1-TYPE 2-NAME 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- Table 12-2 Module position display information Module Description # The module position number Configured The type of module for which the position is configured Installed The type of module installed in that position Stat Empty: no module is installed in the position Ok: the module installed matches the type configured for the position Wrong Module: the module installed does not match the type configured for the position OOS: there is no signal on the E1 link (the link is out of service) (1) Fault On Module: there is something wrong with the module Bad Module ID: the module identification is not recognized by the (1) software Name The name that has been configured for the module position Options Options that have been selected for the module position Note (1) If the position status constantly displays “Fault On Module” or “Bad Module ID” and you have tried re-installing or resetting the module, or both, contact your technical support representative. 12-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 12 — Module position and circuit configuration Procedure 12-3 To view a single position CONFIG — POSITION — or ↵ where p is 1 or 2 pp is 1 or 9 Procedure 12-4 To view a group of positions CONFIG — POSITION SHOW_1-8 SHOW_9-16 SK000485 Procedure 12-5 To view all module positions To view all module positions, enter: CONFIG — SHOW_ALL or CONFIG — POSITION — SHOW_ALL 2902 MainStreet Technical Practices 12-7 May 2002 90-2906-01 12 — Module position and circuit configuration 12.4 Naming a module position Each module position can have a unique name. Procedure 12-6 To name a module position CONFIG — POSITION — or ↵ — NAME — ↵ where p is 1 or 2 pp is 1 or 9 position name is a unique combination of up to eight alphanumeric characters, with no spaces To delete a module name, do not enter a name before pressing ↵. 12.5 Naming a circuit Each primary rate and interface module circuit can have a unique name. Procedure 12-7 To name a circuit CONFIG — CIRCUIT — or ↵ — NAME — ↵ where p-c is a primary rate circuit, p is 1 or 2, and c is 1 to 31 pp-c is an interface circuit, pp is 1 or 9, and c is 1 or 2, or A or B circuit name is a unique combination of up to eight alphanumeric characters, with no spaces To delete a circuit name, do not enter a name before pressing ↵. 12.6 Quick circuit configurations Rather than configure each circuit separately, you can make a direct copy of a circuit configuration or you can copy and automatically adjust the data position of the second circuit. Procedure 12-8 To copy circuit configurations You can copy the configuration of one circuit to another or to all unconfigured circuits of the same type. The parameters of the original circuit (all but the name and connection) are copied to the other circuits. 12-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 12 — Module position and circuit configuration To copy circuit configurations, enter: CONFIG — CIRCUIT — or ↵ — COPY_TO — or ALL ↵ where p-c is a primary rate circuit, p is 1 or 2, and c is 1 to 31 pp-c is an interface circuit, pp is 1 or 9, and c is 1 or 2, or A or B Note — The COPY_TO and ALL commands have no effect on circuits that are already cross-connected. Procedure 12-9 To copy and adjust circuit configurations You can also copy the configuration of one circuit to another circuit of the same type and automatically adjust the data position of the second circuit to follow the data of the first circuit. This is used only for data circuits using transparent or HCM rate adaption. Its exact use varies in each case. Do not use this feature when configuring a multidrop data bridge. To copy and adjust circuit information, enter: CONFIG — CIRCUIT — ↵ — COPY_ADJ — ↵ where pp-c is an interface circuit, pp is 1 or 9, and c is 1 or 2, or A or B 12.7 Viewing circuit status You can view the status of primary rate and interface circuits one at a time or in groups. You can switch back and forth between the two displays by using the SHOW_GROUP/SHOW_CCT toggle softkey. Figure 12-4 shows a display for a primary rate circuit. Circuit status can be configured or connected. A circuit that protects another circuit is considered connected. See section 23.5 for information on protecting circuits. 2902 MainStreet Technical Practices 12-9 May 2002 90-2906-01 12 — Module position and circuit configuration Figure 12-4 Circuit status display 2902 MainStreet 82211-ab-cd Alarms:8 No Date 2:51R Circuit Name Type Function Fault Status P1 - 01 E1_DNIC DATA IDLE Configured CONFIG POSITION P1-1 1-SHOW_GROUP 2-NAME 3-COPY_TO 4- 5- 6- 7-MORE... 8-CANCEL 9-QUIT 0- Procedure 12-10 To view a single circuit or all circuits on a module CONFIG — CIRCUIT — or ↵ — SHOW_GROUP/SHOW_CCT* where p-c is a primary rate circuit, p is 1 or 2, and c is 1 to 31 pp-c is an interface circuit, pp is 1 or 9, and c is 1 or 2, or A or B * Default 12-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources 13.1 System timing 13-2 13.2 Timing sources 13-3 13.3 Types of synchronization 13-6 13.4 Class number 13-7 13.5 Failure threshold 13-8 13.6 Recovery condition 13-9 13.7 Intra- and inter-sector links 13-10 13.8 Displaying the network configuration 13-12 2902 MainStreet Technical Practices 13-1 May 2002 90-2906-01 13 — System timing and timing sources 13.1 System timing The various clock rates required for system timing are provided by the system synchronization unit, which is located on the Control card. The timing source that drives the SSU is user-configurable. System timing can be set for: • standalone (STANDALONE) • automatic network synchronization (AUTO_SYNC) The default is standalone system timing. Standalone Typically, standalone system timing is used when a 2902 MainStreet system is used in a single-ended or point-to-point application. When operating in standalone mode, the system uses only those timing sources that have been configured locally. Automatic network synchronization ANS is used when the 2902 MainStreet system is part of a network. In this case, each node has access to all timing sources in the network. This allows every node to receive timing signals from the same source, ensuring network synchronization. In addition, ANS allows you to divide a network into sectors where each sector has independent timing. Procedure 13-1 Standalone configuration summary Note — When the method of synchronization is changed (standalone to ANS, or ANS to standalone), timing sources are reset to their default clock and recovery configurations (free-run and manual recovery). 1 Enable standalone system timing on the node (see Procedure 13-3). The STANDALONE and AUTO_SYNC softkeys only appear when all synchronization sources have a status of disabled, undefined or unavailable. To disable a timing source, see section 13.2. 2 Configure the timing sources that can provide timing for the node. Timing source configuration parameters are described in section 13.2, and include setting the class number, failure threshold and recovery method. See sections 13.3 to 13.6. 13-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources Procedure 13-2 ANS configuration summary Note — When the method of synchronization is changed (standalone to ANS, or ANS to standalone), timing sources are reset to their default clock and recovery configurations (free-run and manual recovery). 1 Enable ANS system timing on the node (see Procedure 13-3). The STANDALONE and AUTO_SYNC softkeys only appear when all synchronization sources have a status of disabled, undefined or unavailable. To disable a timing source, see section 13.2. 2 Configure the timing sources that can provide timing for the network. Timing source configuration parameters are described in section 13.2, and include setting the class number, failure threshold and recovery method. See sections 13.3 to 13.6. 3 Define one CPSS channel per network link. See chapter 14 for information on configuring CPSS channels. See section 13.7 for information on using links in an ANS network. 4 Identify the CPSS links that are used for ANS and configure them as intra-sector links (see section 13.7). These links carry timing and source routing information. 5 Identify the CPSS links that are not used for ANS or the links that define sector boundaries, and configure them as inter-sector links (see section 13.7). These links do not carry timing and source routing information. Procedure 13-3 To set standalone or ANS system timing CONFIG — SYNCH — AUTO_SYNC/STANDALONE* * Default 13.2 Timing sources Two timing sources are available to the 2902 MainStreet system—one from each primary rate link. Timing source 1 is associated with the first primary rate link (P1) and timing source 2 is associated with the second primary rate link (P2). Only one timing source is active at any moment. The active timing source is referred to as the current timing source. If the current source fails, the other source takes over. 2902 MainStreet Technical Practices 13-3 May 2002 90-2906-01 13 — System timing and timing sources Timing sources can be configured for: • type of synchronization • class number • failure threshold • failure recovery When the timing sources have been configured and timing has been enabled, the 2902 MainStreet system automatically generates its own map of all timing sources. Each time a configuration change occurs (for example, when a new 2902 MainStreet node is brought on-line or a timing source is reconfigured), the map is updated. Each timing source is assigned a class number. The class number rates a source's preference. When assigning a class number, consider factors affecting the timing source's accuracy, reliability, and so on (which, in turn, depend on the node, the network and the timing sources available). Unless a timing source is specifically selected manually, the 2902 MainStreet system automatically selects the source with the highest preference as its timing source. If several sources in a network have the same preference, the node selects the source that is the fewest number of hops away. A hop is a link between two pieces of network equipment. Note — After a database configuration has been restored, all synchronization sources are unavailable to the system. Current source failure When the current timing source is lost (for example, due to a node or a link failure), the node switches to free-run operation for approximately 10 seconds. During this interval, the node determines if there is an alternate path to the master source of synchronization. If an alternate path is available, the node synchronizes to that link. If no path is available, the nodes determine the timing source with the highest preference (lowest class number) among the sources that are ready and all nodes synchronize to it. If all sources fail or if the class numbers of all sources and nodes remain in the default state, the network synchronizes to the internal clock of the active node with the lowest node number. Displaying timing sources You can display the current configuration and status information for both timing sources by entering: CONFIG — SYNCH Figure 13-1 shows the display. If the sources have not yet been configured, the default settings are displayed. 13-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources Figure 13-1 Synchronization display 2902 MainStreet 82211-ab-cd NEWYORK Alarms:2 09-JAN-1997 1:00P Auto Net Sync: Disabled Node Class: 15 Current Class: 15 Number Source Recovery Class Threshold Status 1 P1 Auto 14 5 Not Ready 2 P2 Auto 14 5 Not Ready Current source of synchronization is Default (Free Run) CONFIG SYNCH 1-SRC_NUM 2- 3- 4-NODE_CLASS 5- 6- 7- 8-CANCEL 9-QUIT 0- Table 13-1 describes the entries that can appear under Status. Table 13-1 Sychronization source status descriptions Status Description Disabled The source in manual recovery has failed. The system has unsuccessfully attempted timed recovery to the source. The source has exceeded the permissible failure rate (set under THRESHOLD). The source was disabled (by selecting DISABLE). The source is in the default state. The source was in the Cannot Lock state and an unsuccessful attempt to recover to the source was made. Not Ready The source is not available for system timing. Ready The source is available for system timing. Current The source is providing system timing. Auto Rec The source has failed and will be used by the system as soon as it becomes available. Time Rec The source has failed and the system is checking at timed intervals to see if it is available to provide system timing. Cannot Lock The system is unable to take timing from the source. It attempts to retake timing from the source shortly after this state is entered. 2902 MainStreet Technical Practices 13-5 May 2002 90-2906-01 13 — System timing and timing sources Enabling a timing source When a source is enabled, it becomes available to the system as a source of timing. If an enabled source has a higher preference (lower class number) than the current source of timing, the enabled source is automatically selected as the new source of timing. When a source is disabled, it becomes unavailable to the node as a source. A timing source must be disabled before its configuration can be changed. Selecting a timing source When you select a timing source, it becomes the current source regardless of its class number. Its status changes from Ready to Current. When you deselect a source, its status changes from Current to Ready. The system will then automatically select the Ready source with the highest preference (lowest class number) to be the new current source. Procedure 13-4 To enable and select a source CONFIG — SYNCH — SRC_NUMBER — ↵ ENABLE/DISABLE SELECT/DESELECT SK000474 where source number is 1 or 2 13.3 Types of synchronization Each timing source can be set for the following type of synchronization: • internal (FREE_RUN) • derived (DERIVED) If the current timing source is lost or becomes degraded or if the SSU cannot synchronize to it, the system automatically switches to the other source, providing it has been configured and is available. If this source fails and the first source is still unavailable, the system switches to its internal clock (free run). Note — Free-run mode should be used only as a last resort because the node is not fully synchronized with the network in this mode. 13-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources Internal For internal mode, the system uses its internal clock as its internal crystal oscillator. The oscillator supplies a timing reference accurate to ±25 ppm. When synchronized to this source, the timing is said to be free running. Derived For derived mode, an 8 kHz clock is derived from a primary rate link. Procedure 13-5 To configure the type of synchronization CONFIG — SYNCH — SRC_NUMBER — ↵ SOURCE DERIVED ↵ FREE_RUN SK000475 where source number is 1 or 2 p is 1 or 2 13.4 Class number Timing source selection is determined by class number. The class number is configurable and provides a means for specifying the preference of a timing source: the higher the preference, the lower the class number. For example, a timing source assigned a class number of 1 is assigned the highest preference. Class numbers can be assigned to timing sources and to nodes. When assigned to a node, the class number refers to the internal clock of the node. A class number of 15 indicates a source that does not normally supply network timing. For example, internal synchronization (free run) is assigned a class number of 15 so that it is the last source available. Class numbers from 1 to 14 establish preferences among the possible timing sources in the node or network. The node or network uses only at the class number to determine the source hierarchy—in a network, there is no distinction between node class numbers and timing source class numbers. A node class number of 0 is generated by a node in standalone mode that may be intimately linked with an ANS network but is not part of the ANS. Class 0 nodes derive their timing from a source configured at the node. Class 0 nodes can only be connected to the ANS network over inter-sector links. Class number 0 cannot be user-configured. 2902 MainStreet Technical Practices 13-7 May 2002 90-2906-01 13 — System timing and timing sources Timing sources can be assigned the same class number if they can be traced back to the same source along identical paths (that is, paths that provide no degradation or equivalent degradation of the timing signal). Procedure 13-6 To assign a class number to a timing source CONFIG — SYNCH — SRC_NUMBER — ↵ CLASS ↵ SK000476 where source number is 1 or 2 class number is 1 to 15 (1 is the highest preference) Procedure 13-7 To assign a class number to a node CONFIG — SYNCH — NODE_CLASS — ↵ where number is 1 to 15 (1 is the highest preference) 13.5 Failure threshold The failure threshold defines the number of failures per hour for a timing source. A timing source can fail because it is unreliable, or because of a node or link failure. The threshold can be set between 0 and 30, or for no threshold (unlimited). If the number of source failures exceeds the threshold, the source is disabled. To make the source available again, you must enable it as described in section 13.2. If the timing source recovers and the number of failures does not exceed the threshold, the source is made available. It will be used when it meets the timing source recovery condition (see section 13.6). If no threshold is set, the system uses the timing source when it recovers and meets the timing source recovery condition. If you want the source to be disabled when it fails, set the threshold to 0. Alternatively, you can set the source recovery condition to MANUAL (see section 13.6) If some other node detects a failure, that node raises an alarm; however, your node continues to use the same source. 13-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources Procedure 13-8 To assign the failure threshold CONFIG — SYNCH — SRC_NUMBER — ↵ THRESHOLD ↵ UNLIMITED* SK000477 where source number is 1 or 2 n is 0 to 30 * Default 13.6 Recovery condition If a failed source recovers and meets the source failure threshold, the 2902 MainStreet system attempts to reuse that source, if it has a higher preference (lower class number) than the current timing source. However, the system first checks that the recovered source is ready. You can specify the condition under which the system considers the recovered source as ready. The recovery conditions are: • automatic (default) • timed • manual Automatic When automatic recovery is selected, a failed source becomes available to the system (enters the ready state) as soon as it recovers. The system attempts to synchronize to the recovered source if it has a lower class number than the current source. Note — Automatic recovery cannot be used with an external source since system control does not monitor the stability of the external synchronized signal. Timed When timed recovery is selected, the system continues to use the new (current) source but checks up to four times during the specified interval to see if the failed source has remained recovered. If the source has remained recovered, it becomes available to the system (enters the ready state) and, if the class number is lower than that of the current source, becomes the current source. If the source has not recovered by the fourth check, the system places the source in the disabled state. 2902 MainStreet Technical Practices 13-9 May 2002 90-2906-01 13 — System timing and timing sources Manual When manual recovery is selected, the system places the failed source in the disabled state. The source is not used as a source of synchronization until manually enabled and selected. Procedure 13-9 To configure the recovery method CONFIG — SYNCH — SRC_NUMBER −− ↵ — RECOVERY AUTO* 30_SEC 1_MIN 10_MIN 30_MIN MANUAL SK000478 where source number is 1 or 2 * Default 13.7 Intra- and inter-sector links Within a network, it may be desirable or necessary to define sectors which have independent timing hierarchies. For example, a network that links North America to Europe would require a North American sector and a European sector to accommodate the differences between the two timing reference standards. Sectors are created by enabling or disabling the ANS option on CPSS links. When the ANS option is enabled, ANS timing and source routing information is included with the CPSS messages. A CPSS link with ANS enabled is called an intra-sector link; this type of link is part of a sector. A CPSS link with ANS disabled (the default state) is called an inter-sector link; this type of link provides a timing boundary between sectors. Inter-sector links can also exist within a sector when the link cannot be used for ANS messages. A link can only be used for ANS if there is one CPSS channel configured on that link. If a link is configured with more than one CPSS channel, the ANS option is automatically disabled. Note — Modem connections are not programmable; the system always sees these links as inter-sector links. Figure 13-2 shows an example where two sectors, A and B, have been formed using intra- and inter-sector links. 13-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 13 — System timing and timing sources Figure 13-2 Intra- and inter-sector links Node Node A1 A2 Node Node Intra-sector A3 A4 links Node Intra-sector A5 links Node Node A6 A7 Inter-sector link Node B1 Sector A Intra-sector Node links B3 Node B2 Sector B 8987 Procedure 13-10 To configure an intra- or an inter-sector link In the following softkey menu, select ENABLE for an intra-sector link and DISABLE for an inter-sector link. CONFIG — POSITION — ↵ — OPTIONS — MORE — ANS — ENABLE/DISABLE* where p is 1 or 2 * Default The ANS softkey only appears when one CPSS link has been defined on the specified position. Attempting to define a second CPSS link for that position displays the message “WARNING: Pressing PROCEED will disable ANS for the position”. Selecting PROCEED makes the CPSS connection, disables ANS for the position, and removes the ANS softkey. To access the ANS softkey again, disconnect one of the CPSS connections. If you select ANS when the synchronization is in standalone mode, a message to that effect appears on the diagnostics line. However, you can continue configuring for ANS. 2902 MainStreet Technical Practices 13-11 May 2002 90-2906-01 13 — System timing and timing sources 13.8 Displaying the network configuration When ANS system timing is used, it may be necessary to view the network configuration. Figure 13-3 shows a network configuration display, indicating the number of hops from the local node to other nodes, the local ANS links (primary rate circuit number) and the number of nodes in the network. Figure 13-3 Network configuration display 2902 MainStreet 82211-ab-cd Alarms:1 No Date 0:000R Node: 39 Clock Source: Free Run Clock Cl: 15 Nodes in Network: 7 Node Hops Cl Circuit Node Hops Cl Circuit Node Hops Cl Circuit 14 1 0 P1-01 52 2 0 P1-P1 78 3 0 P1-01 26 1 0 P2-17 65 2 0 P1-01 1023 2 0 P1-01 MAINT VIEW_NET SHOW_NODES 3 1- 2- 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- Procedure 13-11 To display the network configuration MAINT — MORE — VIEW_NET — SHOW_NODES — ↵ where node number is the node number from which to start, between 1 and 1023 13-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 14 — CPSS 14.1 CPSS overview 14-2 14.2 CPSS channel connections 14-2 2902 MainStreet Technical Practices 14-1 May 2002 90-2906-01 14 — CPSS 14.1 CPSS overview CPSS is a proprietary communication protocol, a packet-switched system similar to X.25. MainStreet products use CPSS messages to exchange information with each other and with the 5620 NM over the network. In case of network failure, CPSS can also be used to communicate with the network manager over modems connected to serial ports. CPSS messages carry: • status information, enabling nodes to construct routing tables • control information, allowing the network manager to send commands to nodes • timing information between nodes that have ANS enabled • alarm information, allowing the network manager to gather diagnostic information • performance information, enabling the network manager to gather statistics Products that are part of a proprietary network must dedicate at least one channel to CPSS. The 2902 MainStreet unit supports a 16 kb/s shared CPSS resource. CPSS messages can be carried by: • timeslot 0 on E1 links • a 64 kb/s channel (DS0) on all primary rate links • the serial ports (directly or through a modem) 14.2 CPSS channel connections CPSS channel connections can be made using: • timeslot 0 • a 64 kb/s channel • a serial port Timeslot 0 is a 64 kb/s channel reserved for signaling on E1 links. If CPSS is carried in timeslot 0, the CPSS channel occupies 16 kb/s of timeslot 0. CPSS is carried in timeslot 0 by connecting CPSS to timeslot 0. All or part of a 64 kb/s channel on a primary rate link can be designated as a CPSS channel. The Codirectional DCM also supports CPSS connections to a 64 kb/s channel. A 5620 NM can communicate with the 2902 MainStreet system by a direct serial port connection or an indirect connection (through a serial port using the PSTN and modems). The computer running the network manager can be referred to as the NOC. 14-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 14 — CPSS Procedure 14-1 To connect or disconnect timeslot 0 CPSS CONFIG — CONNECT ↵ ↵ TO_CIRCUIT DISC_FROM TO_CIRCUIT DISCONNECT ↵ ↵ SK000480 where p is 1 or 2 Procedure 14-2 To connect or disconnect a 64 kb/s CPSS channel CONFIG — CONNECT ↵ or ↵ TO_CIRCUIT DISC_FROM TO_CIRCUIT DISCONNECT ↵ or ↵ SK000481 where p-c is the primary rate circuit number, p is 1 or 2, and c is 1 to 30 (CAS) or 31 (CCS) pp-c is the Codirectional DCM circuit number, pp is 1 or 9, and c is 1 or 2 Procedure 14-3 To connect CPSS directly to the serial ports If the computer running the 5620 NM is plugged into a serial port, make the following changes for CPSS communication. 2902 MainStreet Technical Practices 14-3 May 2002 90-2906-01 14 — CPSS 1 Set the baud rate of the serial port to match the baud rate of the network manager. Enter: HOUSE SER_PORT_1 SER_PORT_2 BAUD_RATE 300 600 1200** 2400 4800 9600* SK000482 where * Default for serial port 1 ** Default for serial port 2 2 Set the device type for a personal computer running network management software. Enter: HOUSE SER_PORT_1 SER_PORT_2 PORT_TYPE CPSS SK000483 Note — The default data format for both serial ports is: • 8 data bits • 1 stop bit • no parity Procedure 14-4 To connect CPSS indirectly using the PSTN and modems If the computer running the 5620 NM is exchanging CPSS messages with the 2902 MainStreet system through modems and the PSTN, make the following changes for CPSS communication. 14-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 14 — CPSS 1 Set the baud rate of the serial port to match the baud rate of the network manager. Enter: HOUSE SER_PORT_1 SER_PORT_2 BAUD_RATE 300 600 1200** 2400 4800 9600* SK000482 where * Default for serial port 1 ** Default for serial port 2 2 Set the device type for a modem. Enter: HOUSE SER_PORT_1 SER_PORT_2 PORT_TYPE CPSS_MODEM SK000674 3 Enter the phone number of the modem connected to the network manager computer: HOUSE — NOC_NUM — ↵ where phone number is the NOC number (see section 11.4 for details) 2902 MainStreet Technical Practices 14-5 May 2002 90-2906-01 14 — CPSS 14-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters 15.1 E1 module overview 15-2 15.2 Network connectors 15-3 15.3 E1 framing format 15-4 15.4 Signal earthing (E1 G.703 LIM only) 15-4 15.5 Master/slave operation (E1 HDSL and Optical LIMs only) 15-6 15.6 Trunk conditioning 15-7 15.7 Fault classes 15-12 15.8 Alarm declaration and clearing times 15-13 15.9 E1 statistics 15-14 2902 MainStreet Technical Practices 15-1 May 2002 90-2906-01 15 — E1 module operating parameters 15.1 E1 module overview The 2902 MainStreet system supports four 2.048 Mb/s primary rate modules: • E1 G.703 LIM • E1 HDSL LIM • E1 HDSL LIM2 • E1 Optical LIM There are two E1 G.703 LIM variants—one for 75 Ω network termination and another for 120 Ω termination. The system recognizes whether you have installed a G.703, HDSL or Optical LIM when it powers up. You can install any combination of primary rate LIMs on the Control card. Note 1 — The system does not identify E1 G.703 LIM variants. Ensure that you use the network connector that matches the impedance of the LIM. Note 2 — It takes approximately 60 seconds for master and slave HDSL LIMs to synchronize. Synchronization is indicated on the front panel Out of Sync LEDs. Note 3 — Ensure that the jumpers for E1 G.703 and E1 HDSL LIMs are set to match the impedance of the LIMs (see section 5.3). Figure 15-1 shows an NMTI display with E1 G.703 LIM information. For the E1 HDSL LIMs and E1 Optical LIM, some softkeys differ, as described in this chapter. Figure 15-1 E1 G.703 LIM display 2902 MainStreet 82211-ab-cd Alarm:6 No Date 3:43R # Configured Installed Status Name Options P1 E1 E1 OOS CAS TS0 channel is unused E1 connector Type : BNC BNC shield levels : Receive is earthed Transmit is earthed FAS statistics gathered ANS Alarm Threshold : 5 CONFIG POSITION P1 OPTIONS 1-FRAME_TYPE 2-BNC_SHIELD 3-RJ45_CONN 4-CR4_STATS 5- 6- 7-MORE... 8-CANCEL 9-QUIT 0- 15-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters E1 module IDs The 2902 MainStreet NMTI identifies E1 LIMs by the module IDs listed in Table 15-1. See section 26.7 for information about displaying module IDs in the NMTI. Table 15-1 E1 module IDs LIM Module ID (1) E1 LIM $22 E1 HDSL LIM $28 (2) E1 HDSL LIM2 $32 E1 Optical LIM $38 Notes (1) The system does not identify E1 G.703 LIM variants. (2) Nodes using software generic 82211-H0-00 or 82211-H0-01 do not display the module type as HDSL for the E1 HDSL LIM2. 15.2 Network connectors The 2902 MainStreet system can be connected to an E1 network through BNC, RJ45 or FC_PC connectors. The BNC connectors provide 75 Ω termination (according to BS9210:N001:Part 2 specifications). The RJ45 connectors provide 120 Ω termination (according to ISO/IEC 10173:TBR12 specifications). The E1 G.703 LIMs can connect through BNC or RJ45 connectors. The BNC connectors are the default selection for E1 G.703 LIMs. The E1 HDSL LIMs can only connect through RJ45 connectors. The E1 Optical LIM can only connect through FC_PC connectors, and these network connectors are non-configurable. Note — For E1 G.703 LIMs, ensure that the impedance of your network connector matches the impedance of your LIM. When RJ45 connectors are selected for an E1 G.703 LIM, information on signal earthing for BNC shield levels is no longer applicable and does not appear on the display. See section 15.4 for more information on signal earthing. Procedure 15-1 To configure the network connectors for E1 G.703 or E1 HDSL LIMs CONFIG — POSITION — ↵ — OPTION — RJ45_CONN/BNC_CONN* where p is 1 or 2 * Default for E1 G.703 LIMs 2902 MainStreet Technical Practices 15-3 May 2002 90-2906-01 15 — E1 module operating parameters 15.3 E1 framing format The E1 framing options determine the framing structure and the timeslot usage of a 2.048 Mb/s E1 link. The framing type cannot be changed or configured if any circuits are connected. Two framing options are available: CAS and CCS. Channel associated signaling With CAS, timeslot 16 is used for channel associated signaling and is not user configurable. Timeslot 0 is used for framing. The rest of the timeslots are used for information. Common channel signaling With CCS, timeslot 16 is used for circuit 31, which can be configured as an additional 64 kb/s data channel (typically for the transport of common channel signaling messages). Timeslot 0 is used for framing. The rest of the timeslots are labeled as in CAS. Table 15-2 shows the timeslot-to-circuit relationships. In Table 15-2, a timeslot is the ITU-T specified channel designation of a primary rate channel, and a circuit is the node management designation of a primary rate channel. F stands for framing and S stands for signaling. Table 15-2 CAS and CCS timeslot-to-circuit relationships Timeslot 0 1 2 .... 15 16 17 .... 29 30 31 CAS circuit F 1 2 .... 15 S 16 .... 28 29 30 CCS circuit F 1 2 .... 15 31 16 .... 28 29 30 Procedure 15-2 To configure E1 framing format CONFIG — POSITION — ↵ — OPTIONS — FRAME_TYPE — CCS/CAS* where p is 1 or 2 * Default The FRAME_TYPE softkey does not appear if any circuits are connected. 15.4 Signal earthing (E1 G.703 LIM only) The signal earthing options configure the earth side of the receive and transmit lines as earthed or floating. 15-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters Transmit shielding can be configured for E1 G.703 LIM variants with 75 Ω termination impedance (BNC connection). The four options are: • receive line earthed (RX_EARTH) • receive line floating (RX_FLOAT) • transmit line earthed (TX_EARTH) • transmit line floating (TX_FLOAT) Lines earthed When a line is earthed, the earth side of the receive or transmit line is connected to the earth plane of the Control card and, through it, to the telecom safety earth. Normally, both the receive and transmit lines are earthed. Lines floating When a line is floating, the earth side of the receive or transmit line is allowed to float because the differential between the line potential and the telecom safety earth is causing unusually high noise problems. Procedure 15-3 To configure signal earthing for E1 G.703 LIMs If the network connector is configured for RJ45, selecting the BNC_SHIELD softkey is an invalid option that displays the message “Invalid option for slot connector type” when selected. CONFIG — POSITION — ↵ — OPTIONS BNC_SHIELD RX_EARTH*/RX_FLOAT TX_EARTH*/TX_FLOAT SK000678 where p is 1 or 2 * Default 2902 MainStreet Technical Practices 15-5 May 2002 90-2906-01 15 — E1 module operating parameters 15.5 Master/slave operation (E1 HDSL and Optical LIMs only) To establish a link, the E1 HDSL or Optical LIM at each end of the link must be configured as either a master or slave LIM. However, both LIMs cannot have the same configuration. The E1 HDSL LIMs do not connect any of the HDSL signal leads to ground (as do the E1 G.703 LIMs) because HDSL is a balanced signal interface. Caution — If the E1 HDSL or Optical LIM at each end of a link is configured as the same type (for example, master-to-master or slave-to-slave), the E1 HDSL or Optical LIMs cannot synchronize. Note — Once the HDSL or optical link is connected and the modules are programmed for either master or slave mode, it takes approximately 60 seconds for the HDSL or optical interfaces to synchronize. This time can also apply when loopbacks are applied or the link is in a fault condition. Procedure 15-4 To configure master/slave operation for E1 HDSL and Optical LIMs The method you use to configure master/slave operation for the E1 HDSL LIM2 depends on the node software generic you are using. The node software generic does not affect the configuration method for the E1 HDSL LIM or Optical LIM. If you are using an E1 HDSL LIM2 on a 2902 MainStreet node with software generic 82211-H0-00 or 82211-H0-01, you must use the BNC transmit shield option to program the LIM to be a master or slave. By default, the BNC shield option is set to TX_EARTH, which corresponds to the master mode on an E1 HDSL LIM2. To program one of the E1 HDSL LIM2s for slave mode, the BNC transmit shield option must be configured for floating. For E1 HDSL LIM2s with software generic 82211-H0-00 or 82211-H0-01, enter: CONFIG — POSITION — ↵ — OPTIONS BNC_SHIELD RX_EARTH*/RX_FLOAT TX_EARTH*/TX_FLOAT SK000678 where p is 1 or 2 * Default 15-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters For E1 HDSL LIM2s with software generic 82211-H0-10 or later, or for E1 HDSL LIMs or Optical LIMs with any software generic, enter: CONFIG — POSITION — ↵ — OPTIONS MASTER*/SLAVE SK000487 where p is 1 or 2 * Default 15.6 Trunk conditioning All connections have an information component and a signaling component. When a fault occurs on an E1 link, trunk conditioning defines the type of signal transmitted on the information and signaling paths. Trunk conditioning can be defined for all outgoing transmissions. Trunk conditioning can be configured as one-way or two-way for each primary rate module position. It can be enabled or disabled for various classes of link faults, and turned off for individual circuits. You can specify how long a fault must persist before an alarm is raised and how long a fault must be cleared before the alarm is cleared. The trunk conditioning configuration for a primary rate interface can be changed at any time. However, any change disrupts service. If any circuits on the link are cross-connected when the trunk conditioning attributes are being changed, the warning message “WARNING: Pressing PROCEED will result in a disruption of service” is displayed on the diagnostics line. The two types of trunk conditioning are two-way and one-way. The default is two-way trunk conditioning. Note 1 — Super-rate circuits do not support trunk conditioning. Control lead signals are not affected by primary rate circuit failure. Note 2 — Primary rate circuits configured to carry CPSS messages have two-way trunk conditioning applied regardless of the type of trunk conditioning selected for them. Two-way trunk conditioning When a link is configured for two-way trunk conditioning and a primary rate link fault occurs, the information and the signaling paths are broken in both directions. Figure 15-2 illustrates how two-way trunk conditioning is applied to a typical connection. 2902 MainStreet Technical Practices 15-7 May 2002 90-2906-01 15 — E1 module operating parameters Signaling path Both the primary rate circuit and the connected circuit undergo fault signaling as configured for the primary rate circuit (see section 16.2). For the primary rate circuit, the signaling path is driven to idle for 2.5 seconds (which drops any call that may be in progress), then to seized or idle (depending on how the E1 circuit fault signaling is configured). For the connected circuit, the signaling is driven to idle, then to seized or idle depending on how the circuit is configured. For E1 circuits configured with out-of-service A or B fault signaling, the signaling is not driven to idle first. Information path On the information path of a primary rate circuit, the system transmits all ones. On the information path of a connected circuit, the system transmits all ones if the circuit is a primary rate circuit; if not, it transmits all zeros. Example If a primary rate circuit is connected to an X.21 circuit and a fault occurs on the primary rate link, the information path is broken in both directions. On the information path of the primary rate circuit, the node transmits all ones. On the signaling path of the primary rate circuit, it transmits idle signaling, then fault signaling as configured for the primary rate circuit. On the information path of the X.21 circuit, the node transmits all zeros (because it is not a primary rate circuit). On the signaling path of the X.21 circuit, it transmits idle signaling, then fault signaling as configured for the X.21 circuit. 15-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters Figure 15-2 Two-way trunk conditioning Information Signaling All 1s SEIZED (primary rate circuit) or IDLE All 0s (not primary rate circuit) Fault Direction of transmission Fault Signaling path Information path Connected 2902 Primary rate circuit MainStreet circuit Information path Signaling path Direction of transmission Signaling Information 2.5 s All 1s SEIZED or IDLE Fault 8842 One-way trunk conditioning When a link is configured for one-way trunk conditioning, the information path or the signaling path or both (depending on the fault) are broken in the direction of the fault only. Transmission in the other direction is not affected. One-way trunk conditioning is different for three groups of alarms. Group 1 one-way trunk conditioning Figure 15-3 shows Group 1 one-way trunk conditioning. For Framing Alarm, Incoming AIS, Framing (FAS) Err Rate Exceeded and Failed State, the information path and the signaling path from the E1 primary rate circuit to the connected circuit are broken in the direction of the fault only. If the connected circuit is a primary rate circuit, the 2902 MainStreet system transmits seized, idle or out-of-service fault signaling (depending on the fault signaling selected for the connected circuit). 2902 MainStreet Technical Practices 15-9 May 2002 90-2906-01 15 — E1 module operating parameters Unlike two-way trunk conditioning, if the fault signaling is seized, a seized signaling code is transmitted without an idle signaling code first being outputted for a fixed period of time. If the connected circuit is not a primary rate circuit, the node continues to transmit the signaling being outputted. If the connected circuit is not a primary rate circuit, the system transmits all zeros on its information path; if it is a primary rate circuit, it transmits all ones. Figure 15-3 One-way trunk conditioning (Group 1) Signaling Information SEIZED If primary All 1s or rate circuit (primary rate circuit) IDLE If not primary All 0s Frozen rate circuit (not primary rate circuit) Fault Direction of transmission Fault Signaling path Information path Connected 2902 Primary rate circuit MainStreet circuit Information path Signaling path Direction of transmission 8843 Group 2 one-way trunk conditioning Figure 15-4 shows Group 2 one-way trunk conditioning. For Multiframe and Incoming TS16 AIS alarms, one-way trunk conditioning breaks only the signaling path in the direction of the fault. The information path is maintained in both directions. If the connected circuit is a primary rate circuit, the system transmits seized or idle fault signaling (depending on the fault signaling selected for the connected circuit). Unlike two-way trunk conditioning, if the fault signaling is seized, the seized signaling code is transmitted without the idle signaling code first being outputted for a fixed period of time. If the connected circuit is not a primary rate circuit, the system continues to transmit the signaling being outputted. 15-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters Figure 15-4 One-way trunk conditioning (Group 2) Signaling Information SEIZED If primary All 1s or rate circuit (primary rate circuit) IDLE If not primary All 0s Frozen rate circuit (not primary rate circuit) Fault Direction of transmission Fault Signaling path Information path Connected 2902 Primary rate circuit MainStreet circuit Information path Transmission not affected Signaling path Direction of transmission 8844 Group 3 one-way trunk conditioning For Distant alarm and TS16 Distant alarm, one-way trunk conditioning does not result in the information path or the signaling path being broken in either direction. No action is necessary because the fault lies in the transmit path of the primary rate circuit (with respect to the 2902 MainStreet system), not the receive path. Procedure 15-5 To configure the type of trunk conditioning This enables trunk conditioning for all primary link faults. CONFIG — POSITION — ↵ — OPTIONS — MORE — TRUNK_COND ONE_WAY/TWO_WAY* SK000488 where p is 1 or 2 * Default You can select classes of alarms that cause trunk conditioning to be applied (see section 15.7). 2902 MainStreet Technical Practices 15-11 May 2002 90-2906-01 15 — E1 module operating parameters Procedure 15-6 To disable trunk conditioning for an E1 circuit If you turn fault signaling off for any E1 circuit, no trunk conditioning is applied to that circuit regardless of how the link is configured for trunk conditioning. That is, the circuit connected to the link stays connected during any red or yellow alarms. See section 16.2 for more information on E1 circuit fault signaling. CONFIG — CIRCUIT — ↵ — FAULT_SIG — NONE where p is 1 or 2, and c is 1 to 31 15.7 Fault classes Trunk conditioning can be enabled or disabled for various classes of primary rate link faults. If trunk conditioning is enabled for an alarm class, one- or two-way trunk conditioning is applied as configured for the primary rate interface when an alarm in that class is raised. If trunk conditioning is disabled for an alarm class, no action is taken when an alarm in that class is raised. Table 15-3 lists the four configurable fault classes. Table 15-3 Fault classes and alarms Fault class Alarms Description Clearing Frame Framing Alarm Includes alarms associated with Cleared when frame Incoming AIS frame alignment or multiframe alignment or multiframe Multiframe Alarm alignment. alignment is regained. Incoming TS16 AIS Distant Distant Alarm TS16 Includes alarms that are received Cleared when the remote Distant Alarm from the equipment at the far end equipment is no longer of the primary rate link. transmitting the alarm. Failed Failed State Includes only the Failed State Cleared when alarm. This alarm is raised when 10 non-severely errored 10 severely errored seconds in a seconds have occurred in row have occurred. a row. Error Framing (FAS) Err Includes only the Framing Err Cleared when the FAS Rate Exceeded Rate Exceeded alarm. It is raised error rate is below -4 when the FAS error rate exceeds approximately 4 x 10 for -3 approximately 10 for a period of 9 to 11 seconds. 4 to 6 seconds. 15-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 15 — E1 module operating parameters Procedure 15-7 To configure fault classes Softkeys with the suffix _OFF disable trunk conditioning for their fault class; those with the suffix _ON enable trunk conditioning. CONFIG — POSITION — ↵ — OPTIONS — MORE — TRUNK_COND FRAME_OFF/ DIST_OFF/ FAILED_OFF/ ERROR_OFF/ FRAME_ON* DIST_ON* FAILED_ON* ERROR_ON* SK000489 where p is 1 or 2 * Default 15.8 Alarm declaration and clearing times Both ends of a primary rate link should use the same alarm declare time because it is desirable for both ends of the link to initiate and terminate trunk conditioning at approximately the same time. The alarm declare and clearing times can be configured for Frame and Distant faults, but not for Failed and Error faults, which have fixed times. Alarm declare time The alarm declare time determines how long a fault must persist before an alarm is declared. A longer alarm declaration time is useful when the primary rate link is subject to frequent short outages. A shorter alarm declaration time is useful when an alternate path exists so that the length of time that service is disrupted is minimized. The declaration time ranges from 0.1 to 30 seconds in 0.1-second increments (the default is 0.8 second). Alarm clear time The alarm clear time determines how long a fault must be cleared before a raised alarm is cleared. A longer alarm clear time is useful when an alternate route exists so that connections to the primary rate link that declared the fault are not restored until it appears that the link is stable again. A shorter alarm clear time is useful when no alternate path exists so that the length of time that service is disrupted is minimized. The clearing time ranges from 0.1 to 30 seconds in 0.1-second increments (the default is 10 seconds). 2902 MainStreet Technical Practices 15-13 May 2002 90-2906-01 15 — E1 module operating parameters Procedure 15-8 To set the alarm declaration and clearing times CONFIG — POSITION — ↵ — OPTIONS — MORE — ALARM_TIME DECLARE CLEAR ↵ ↵ SK000490 where p is 1 or 2 n is 1 to 300 (1 equals 0.1 second) 15.9 E1 statistics You can configure the primary rate link to collect FAS or CRC4 statistics. See chapter 28 in Maintenance for more information on E1 statistics. Procedure 15-9 To configure the statistics type CONFIG — POSITION — ↵ — OPTIONS FAS_STATS*/CRC4_STATS SK000491 where p is 1 or 2 * Default 15-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 16 — E1 circuit operating parameters 16.1 E1 signaling type 16-2 16.2 E1 fault signaling 16-2 2902 MainStreet Technical Practices 16-1 May 2002 90-2906-01 16 — E1 circuit operating parameters 16.1 E1 signaling type Signaling refers to the codes and protocol for call setup, call tear-down and status information between two devices over a primary rate link. The signaling type defines how signaling information is exchanged with the far-end device. The signaling type choices are: • transparent signaling (SIG) • clear channel signaling (NoSIG) For transparent signaling, signaling is passed without being tested for compatibility with the far-end signaling type. For clear channel signaling, a 64 kb/s clear channel is created for which signaling is not passed. Procedure 16-1 To configure E1 circuit signaling type CONFIG — CIRCUIT — ↵ — MORE — SIG_TYPE SIG* NoSIG SK000492 where p is 1 or 2, and c is 1 to 31 * Default Note — The SIG_TYPE softkey does not appear if CPSS is connected to the circuit. 16.2 E1 fault signaling Fault signaling is the signaling code that the node applies to an interface when the interface to which it is cross-connected is not available. The options are: • seized • idle • out-of-service type A • out-of-service type B • out-of-service type C • no trunk conditioning for circuit All primary rate circuits can be configured to appear seized or idle (default) to the outside world. 16-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 16 — E1 circuit operating parameters Fault signaling out-of-service type A or B codes are used by tandem nodes to notify remote circuits of link failures. Out-of-service type A signaling is an all ones signal. Out-of-service type B signaling (0110) can be used if an all ones signal cannot be used, for example, when an all ones signal has meaning for the cross-connected circuit. Out-of-service type C signaling generates a yellow alarm on the DS1 circuit. If fault signaling is turned off for any E1 circuit, trunk conditioning is not applied to that circuit, regardless of how it is configured for the link. That is, the circuit connected to the link stays connected during any red or yellow alarms. Trunk conditioning is described in section 15.6. Procedure 16-2 To configure E1 fault signaling CONFIG — CIRCUIT — ↵ — FAULT_SIG SEIZED IDLE* OOS_B OOS_C NONE OOS_A SK000493 where p is 1 or 2, and c is 1 to 31 * Default 2902 MainStreet Technical Practices 16-3 May 2002 90-2906-01 16 — E1 circuit operating parameters 16-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules 17.1 Understanding DNIC and 2B1Q modules 17-2 17.2 DNIC and 2B1Q circuit configuration and operating parameters 17-2 17.3 Device mode 17-3 17.4 Device gender 17-4 17.5 Duplex method 17-5 17.6 RTS/CTS delay 17-5 17.7 Control signals 17-6 17.8 Data structure (asynchronous only) 17-7 17.9 Clocking (synchronous only) 17-9 17.10 Multidrop data bridge 17-12 17.11 Super-rate configuration for DNIC or 2B1Q modules 17-13 17.12 Loss-of-synchronization debounce time (DNIC only) 17-14 2902 MainStreet Technical Practices 17-1 May 2002 90-2906-01 17 — DNIC and 2B1Q modules 17.1 Understanding DNIC and 2B1Q modules DNIC and 2B1Q modules are dual-circuit modules that connect to data devices through DTUs. These modules can be installed in either interface module position on the Control card. DNIC modules support remote connections of up to two X.21 or V.35 data devices, and up to eight EIA/TIA-232 data devices via a 2600 MainStreet series DTU; 2B1Q modules support up to two EIA/TIA-232, X.21 or V.35 data devices via 2700 MainStreet series DTUs. DNIC and 2B1Q modules support subrate interface speeds up to 64 kb/s, a super-rate speed of 128 kb/s (see section 17.11) and multidrop data bridge connections (see section 17.10). You must configure a module position for a DNIC or 2B1Q module before you can configure its circuits. Note — When you configure a data circuit on a DNIC or 2B1Q module, many of the parameters you are configuring are the operating parameters of the connected DTU. Procedure 17-1 To specify a DNIC or 2B1Q module CONFIG — POSITION — ↵ — TYPE — DATA DNIC 2B1Q SK000494 where pp is 1 or 9 17.2 DNIC and 2B1Q circuit configuration and operating parameters The circuits on a DNIC or 2B1Q module are numbered A and B. The DNIC module connects to two-port or eight-port DTUs. The 2B1Q module connects to two-port DTUs. When a module is used with a two-port DTU, circuit A communicates with DTU port A and circuit B communicates with DTU port B. Each circuit (that is, DTU port) can be configured independently. When a DNIC module is used with an eight-port DTU, the combined interface speed of the connected data devices can be less than, equal to, or greater than 64 kb/s. If it is less than or equal to 64 kb/s, circuit A serves all the devices. If it is greater than 64 kb/s, circuits A and B serve all the devices. In either case, circuit parameters are configured through circuit B, which sets both DTU ports with the same parameters. Configuring circuit A parameters has no effect on the connection. 17-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules DNIC and 2B1Q circuit operating parameters Once you configure the module position, the circuits assume the default settings for each of the following operating parameters: • device mode • device gender • duplex method (two-port DTUs only) • RTS/CTS delay (two-port DTUs only) • control signals • data structure (asynchronous only) • clocking (synchronous only) • multidrop data bridge • rate adaption • transport bandwidth • transport position • signaling and the signaling bit position • interface speed (or data rate) • data position • loss-of-synchronization debounce time (DNIC only) For information on configuring rate adaption, see chapters 21 and 22. 17.3 Device mode Data circuits support two device modes: • synchronous • asynchronous Synchronous devices transmit a continuous stream of characters. Synchronization between devices is maintained through timing signals that are transmitted on separate conductors. Select synchronous if the data device connected to the module uses synchronous data communication. When the circuit is configured as synchronous, clocking parameters must be set (see section 17.9). Asynchronous devices transmit data one character at a time. A character can be represented by five to eight bits with start and stop bits used to mark the beginning and end of the character. Select asynchronous if the data device connected to the module uses asynchronous data communication. When the circuit is configured as asynchronous, the data structure must be set (see section 17.8). Note — If asynchronous mode is selected, transparent rate adaption cannot be used. 2902 MainStreet Technical Practices 17-3 May 2002 90-2906-01 17 — DNIC and 2B1Q modules Procedure 17-2 To set the device mode CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE SYNC*/ASYNC SK000495 where pp is 1 or 9, and c is A or B * Default 17.4 Device gender Data circuits support two device genders: • DTE • DCE Data and control signals are transmitted on wire pairs. The device gender indicates which wire in the pair is used to send or receive the data or control signal. A DTE device sends data or control signals on one of the wires; a DCE device sends signals on the other wire. For example, the TXD signal means data is transmitted by a DTE and received by a DCE and the RXD signal means data is received by a DTE and transmitted by a DCE. In general, terminals and printers are DTE while modems are DCE. However, there are many exceptions. If the owner's manual for the device indicates that the TXD signal is outgoing, the device is DTE; if it is incoming, the device is DCE. The opposite is true for the RXD signal. Procedure 17-3 To set the device gender CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE DCE*/DTE SK000496 where pp is 1 or 9, and c is A or B * Default 17-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules 17.5 Duplex method Data circuits support two duplex modes: • half duplex • full duplex Half-duplex transmission uses a single transmission path. Two connected devices can transmit and receive, but not at the same time. If you select half duplex, the RTS/CTS delay option can be configured (described in section 17.6). Full-duplex transmission uses two independent transmission paths, one in each direction, allowing two connected devices to transmit and receive data simultaneously. The duplex method can be set for two-port DTUs. The 2606 MainStreet DTU cannot be set for half duplex. Procedure 17-4 To set the duplex method CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE HALF_DPLX/FULL_DPLX* SK000497 where pp is 1 or 9, and c is A or B * Default 17.6 RTS/CTS delay RTS and CTS are control signals used to regulate data flow on half-duplex lines. When one device wants to send a message to a second device, it sends an RTS. After receiving the RTS, the second device pauses and then returns a CTS. The pause must be long enough to clear any messages that might be coming into the second device. The pause is called the RTS/CTS delay. For example, using the RTS/CTS delay in multidrop data bridge connections makes a slave device wait long enough to guarantee that a transmission path has been established to the master device. An RTS/CTS delay that is too short results in messages being lost on the line. A delay that is too long decreases response time. The optimum value depends on your network. The range for RTS/CTS delay is 0 to 1250 ms in 10-ms increments (the default is 10 ms). 2902 MainStreet Technical Practices 17-5 May 2002 90-2906-01 17 — DNIC and 2B1Q modules Procedure 17-5 To set the RTS/CTS delay The RTS/CTS delay can be set for two-port DTUs. RTS/CTS delay cannot be set for the 2606 MainStreet DTU. The RTS/CTS delay can only be set when a circuit is configured for half-duplex mode (see section 17.5) or as a multidrop slave (see section 17.10). CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — RTS/CTS — ↵ where pp is 1 or 9, and c is A or B delay time is from 0 to 1250 ms in 10-ms increments (10 ms*) 17.7 Control signals Control signals provide the handshaking required for call setup, call tear-down and synchronization. Control signals can be configured as: • high (ON) • low (OFF) • end-to-end (END_TO_END) End-to-end means the state of the local signal follows that of the signal source at the remote end of the network. This option is only available when using HCM rate adaption. Note — Control signals are the only interface parameter that can be set for a circuit that is configured as a timing source. It is also the only interface parameter that can be changed when a circuit is connected. Table 17-1 shows default control signal settings. If the device is configured as synchronous, DTR and DSR are not functional. Table 17-1 DNIC and 2B1Q module control signal defaults Gender Inputs Outputs DCE RTS END_TO_END DCD END_TO_END DTR END_TO_END DSR FORCED_ON ALB END_TO_END CTS END_TO_END RDL END_TO_END RI FORCED_OFF DTE DCD END_TO_END RTS END_TO_END DSR END_TO_END DTR FORCED_ON CTS END_TO_END ALB END_TO_END RI END_TO_END RDL FORCED_OFF 17-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules For 56 kb/s transparent channels, when RTS is set for end-to-end operation, the value of RTS is forced into bit position 8. The far-end DTU maps RTS to its own DCD lead going to DTE devices. With both DTUs operating in end-to-end signaling, incoming RTS in bit position 8 is mapped to DCD. For the 2602, 2702 and 2752 MainStreet DTUs, which support X.21 devices, the control signal (C) is represented on the display by RTS (if DTE) or DCD (if DCE) and the indicator signal (I) is represented on the display by DCD (if DTE) or RTS (if DCE). The other control signals are not used. Procedure 17-6 To set DNIC or 2B1Q control signals Selecting ON or OFF for inputs configures them as ASSUMED_ON or ASSUMED_OFF. Selecting ON or OFF for outputs configures them as FORCED_ON or FORCED_OFF. CONFIG — CIRCUIT — ↵ — FUNCTION — CTRL_LEADS INPUTS OUTPUTS DTR RTS ALB RDL DSR DCD CTS RI ON OFF END_TO_END SK000498 where pp is 1 or 9, and c is A or B 17.8 Data structure (asynchronous only) The data structure of asynchronous transmission has three configurable characteristics: • character length • number of stop bits • type of parity Note — A character must be 8, 9, 10 or 11 bits. The number of bits in a character is the sum of the start bit (always 1), character length (5, 6, 7 or 8), stop bits (1 or 2) and parity bit (0 for no parity or 1 for odd, even, mark or space). For example, if the character length is set to 5 bits and the number of stop bits is set to 1, the parity cannot be set to no parity. If this rule is broken, the relevant softkeys are not displayed. 2902 MainStreet Technical Practices 17-7 May 2002 90-2906-01 17 — DNIC and 2B1Q modules Character length Character length is the number of data bits used to transmit a character in asynchronous transmission. Character length can be set to: • 5 bits • 6 bits • 7 bits • 8 bits (default) Stop bits Stop bits signify the end of a character in asynchronous transmission. The number of stop bits can be set to: • 1 bit (default) • 2 bits Parity Parity is an error detection method that adds an extra bit to each transmitted character. It is based on the number of zeros or ones in each character. Five parity schemes are supported: • no parity (default) • odd • even • mark • space Procedure 17-7 To set the data structure CONFIG — CIRCUIT — ↵ — FUNCTION STOP_BITS CHAR_LEN PARITY 5_BITS 6_BITS 7_BITS 8_BITS* 1_BIT* 2_BITS NONE* ODD EVEN MARK SPACE SK000499 where pp is 1 or 9, and c is A or B * Default 17-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules 17.9 Clocking (synchronous only) Synchronous data devices require two clocking signals: one for the receive data stream and one for the transmit data stream. The receive clock supplies timing for receive data; the transmit clock supplies timing for transmit data. Transmit data and receive data are defined relative to the data device configured as DTE; the transmit clock is used by the DTE device to transmit data and by the DCE device to receive data. Figure 17-1 shows these relationships. Figure 17-1 Transmit and receive clocks Transmit clock Transmit data DTE DCE data data device device Receive data Receive clock 1535 The two parameters for configuring clocking for synchronous transmissions are: • transmit clock source • type of synchronous clocking Transmit clock source When the device mode is synchronous, the clocking source between the DNIC or 2B1Q module and the attached data device is selectable. The transmit clock can be supplied by: • the attached device (EXTERNAL) • the data circuit to which the device is attached (INTERNAL) • a remote source (SLAVE) (default) The way this parameter is set depends on whether the circuit is in DCE or DTE mode. Table 17-2 gives the transmit clock options for DCE and DTE modes. Table 17-2 DNIC and 2B1Q clock sources Clocking source Meaning DCE Internal A baud rate generator in the DTU provides the transmit clock. The baud rate generator is locked to system timing. INTERNAL is only available with HCM rate adaption. (1 of 2) 2902 MainStreet Technical Practices 17-9 May 2002 90-2906-01 17 — DNIC and 2B1Q modules Clocking source Meaning External The user equipment provides the transmit clock; that is, the XCLK pin from the DTE. Slave The circuit extracts the transmit clock from the data stream. DTE Internal, These three options indicate the configuration of the transmit clock of the external or attached DCE device. slave (2 of 2) Type of synchronous clocking When you configure the type of synchronous clocking, you are configuring the effect that the 2902 MainStreet system has on clocks passing through it. The type can be set: • to the timing of the 2902 MainStreet system (LOCKED) (default) • to be passed through transparently (INDEPNT) If the clocking for a circuit is independent, the clock adjustment information is embedded in the signaling bit of an HCM frame and passed through the node transparently. In independent mode, deviations of up to 50 b/s relative to the nominal rate can be accommodated. For more information on clocking, ask your supplier representative for Configuration Note NCN305 entitled “Data Interface Clocking”. Clocking examples Figure 17-2 is an example of a DTU clocking application. Tables 17-3 and 17-4 provide some clocking combinations that describe their applications. Note — Clocking configurations are valid for data circuits using HCM rate adaption. If a circuit uses transparent rate adaption, only external locked or slave locked configurations can be used. Table 17-3 DTU clocking applications - DCE mode DTU #1 (DCE) DTU #2 (DCE) HCM Transparent Application Slave Locked Slave Locked Yes Yes Default. Used when data network is integrated with the 2902 MainStreet network. Slave Locked External Yes Yes Used when DTU #2 is configured as a Locked source of network timing Slave External Yes No Used when clocking is independent of Independent Independent the network 17-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules Table 17-4 DTU clocking applications - DTE mode DTU #1 (DTE) DTU #2 (DTE) HCM Transparent Application Slave Locked Slave Locked Yes Yes Default. Used when: • the data network is locked to the 2902 MainStreet network • DTU #1 is getting 2902 MainStreet network timing from the data network External Slave Locked Yes Yes Used when the data network timing is Locked locked to the 2902 MainStreet network timing Slave Slave Yes No Used when modems are providing the Independent Independent clocking independent of the 2902 MainStreet system clocking Figure 17-2 Sample DTU clocking application 2902 MainStreet network 2902 MainStreet NTU DTU #2 3630 MainStreet (DCE) node Host BA DTU #1 DTU #1 (DTE) (DCE) Data network Modem or NTU Modem or NTU Terminal Terminal 9130 Procedure 17-8 To configure the transmit clock CONFIG — CIRCUIT — ↵ — FUNCTION — CLOCKING INTERNAL EXTERNAL SLAVE* LOCKED*/INDEPNT SK000500 where pp is 1 or 9, and c is A or B * Default 2902 MainStreet Technical Practices 17-11 May 2002 90-2906-01 17 — DNIC and 2B1Q modules 17.10 Multidrop data bridge In a multidrop data bridge, several broadcast destination circuits (called slaves) take turns using the same bandwidth to communicate with one broadcast source circuit (called the master); for example, several terminals would take turns communicating with a host computer. The master device controls the use of the shared bandwidth by polling each slave in turn. Figure 17-3 shows a multidrop data bridge. Figure 17-3 Multidrop data bridge Responding Aggregate Branch Multidrop data bridge circuits circuit Master Slave device devices Polling 2285 To create a multidrop bridge, two components are needed: a data interface that supports the multidrop function and a multidrop data bridge. The 2902 MainStreet unit supports the multidrop interfaces but does not provide the multidrop data bridge. One way to use a 2902 MainStreet unit in this type of application is in conjunction with a 3600 MainStreet Multiservice Bandwidth Manager containing a Sub-Rate Interface module (SRM). Master and slave circuits must be configured with the same starting data position and transport bandwidth (see chapters 21 and 22). To facilitate this, the 2902 MainStreet system automatically sets the master circuit configuration to full duplex and signaling off, and the slave circuit configuration to half duplex and signaling off. These settings allow you to overlap the position of the data from these circuits. For circuits in a multidrop data bridge, if the circuit is configured as gender DCE, the DCD control signal must be forced on. If the circuit is configured as gender DTE, the RTS control signal must be forced on. Do not use the copy adjust function when configuring circuits that are to be part of the same multidrop data bridge. 17-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules Procedure 17-9 To configure a master or slave multidrop device CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — MULTIDROP DISABLE* SLAVE MASTER SK000501 where pp is 1 or 9, and c is A or B * Default 17.11 Super-rate configuration for DNIC or 2B1Q modules A super-rate circuit occupies more than one contiguous DS0 channel on a primary rate link. Each module position represents two DS0 channels, or 128 kb/s of bandwidth. A super-rate speed of 128 kb/s is available to a DNIC module connected to 2600 MainStreet series DTUs that support super-rate speeds, or a 2B1Q module connected to 2700 MainStreet series DTUs that support super-rate speeds. All DNIC and 2B1Q super-rate connections require two contiguous primary rate channels. The 2902 MainStreet system performs delay equalization through resources on the Control card. Super-rate circuits on a DNIC or 2B1Q module are subject to the following limitations. • Super-rate speeds can be configured for DTU port A, port B, or both. However, only one port may be cross-connected at any one time. If one port is configured for a super-rate connection and you try to connect the other, the system displays an error message. • If the circuit is already connected, the interface speed and transport bandwidth cannot be changed. • Protection switching for super-rate circuits is not supported. • Tandem super-rate connections (connections between two primary rate modules) are not supported on the 2902 MainStreet system. For information on connecting super-rate circuits, see section 23.3. To disconnect a super-rate circuit, see section 23.6. Configuration overview To configure a circuit for super-rate: 1 Configure the circuit for transparent rate adaption. 2 Set the transport bandwidth. 2902 MainStreet Technical Practices 17-13 May 2002 90-2906-01 17 — DNIC and 2B1Q modules 3 Set the interface speed. The interface speed must be a whole number multiple of the transport bandwidth. For DNIC and 2B1Q modules, this means the transport bandwidth is 64 kb/s and the interface speed is 128 kb/s. Procedure 17-10 To configure transparent rate adaption CONFIG — CIRCUIT — ↵ — FUNCTION — RATE ADAPT — METHOD — TRANSPAREN where pp is 1 or 9 Procedure 17-11 To set the transport bandwidth CONFIG — CIRCUIT — ↵ — FUNCTION— RATE_ADAPT — TRANSP_BW — <8> ↵ where pp is 1 or 9 Transport bandwidth is configured in 8 kb/s blocks, where transport bandwidth = m x8 kb/s (m is a multiplier). Since the transport bandwidth for DNIC and 2B1Q modules is 64 kb/s, m = 8. Procedure 17-12 To set the interface speed CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — I/F_SPEED — <128> ↵ where pp is 1 or 9 17.12 Loss-of-synchronization debounce time (DNIC only) DNIC modules, as well as 2600 MainStreet series DTUs, use debounce timers to distinguish loss of synchronization from random line noise. DTU debounce When synchronization between a DNIC module and a DTU is lost, the DTU automatically resets. This corrects any DTU hardware or software problems that can be fixed by initializing and reconfiguring the DTU. DTUs with firmware IDs at or greater than those listed in Table 17-5 have debounce times of 2000 ms. DTUs with IDs lower than those listed in Table 17-5 have lower debounce times. These times cannot be configured. 17-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 17 — DNIC and 2B1Q modules Table 17-5 Firmware IDs for DTUs with improved debounce time Mainstreet DTUs Firmware ID 2601, 2601AN, 2602, 2602AN, 2603 and 2603AN $11 2606 $1 2608 $7 2610 $5 DNIC module debounce The debounce timer on the DNIC module can be configured to accommodate various degrees of line noise that might produce a loss of synchronization. The options for debounce time settings are: • 50 ms • 250 ms (default) • 1s • 2s • CUSTOM The range of debounce times for the CUSTOM option is 1 to 32767 ms (5 minutes, 27 seconds) in 10-ms increments. Specify the debounce time in tens of ms from 1 to 32767 where, for example, 1 is 10 ms, 2 is 20 ms, 32767 is 327 670 ms. Procedure 17-13 To set the debounce time CONFIG — POSITION — ↵ — OPTIONS — SYNC_DEB — NODE_LOSS 50_ms 250_ms* 1_sec 2_sec CUSTOM ↵ SK001040 where pp is 1 or 9 debounce_time is an integer between 1 and 32767 in 10-ms increments Figure 17-4 shows a sample debounce time configuration display. 2902 MainStreet Technical Practices 17-15 May 2002 90-2906-01 17 — DNIC and 2B1Q modules Figure 17-4 Debounce time configuration display 2902 MainStreet 82211-ab-cd Alarms:1 No Date 1:28R # Configured Installed Status Name Options M01 DNIC Empty Empty Loss Of Sync Debounce - DTU end : 2000 ms (Not Configurable) Loss Of Sync Debounce - Node end: 250 ms CONFIG POSITION 1 OPTIONS SYNC_DEB NODE_LOSS 1-50_ms 2- 3-1_sec 4-2_sec 5-CUSTOM 6- 7- 8-CANCEL 9-QUIT 0- 17-16 2902 MainStreet Technical Practices 90-2906-01 May 2002 18 — RS-232 DCM 18.1 Understanding the RS-232 DCM 18-2 18.2 RS-232 DCM circuit operating parameters 18-2 18.3 Device mode 18-3 18.4 Device gender 18-3 18.5 Full duplex 18-4 18.6 RTS/CTS delay 18-4 18.7 Control signals 18-5 18.8 Data structure (asynchronous only) 18-6 18.9 Clocking (synchronous only) 18-7 18.10 Multidrop data bridge 18-9 2902 MainStreet Technical Practices 18-1 May 2002 90-2906-01 18 — RS-232 DCM 18.1 Understanding the RS-232 DCM The RS-232 DCM is a dual-circuit module that offers data connectivity conforming to EIA/TIA-232 standards. The module can be installed in either interface module position on the Control card. Data devices connect directly to this DCM, eliminating the need for an external DTU. Before you can set data circuit operating parameters, you must: • configure a module position for an RS-232 DCM • know the operating characteristics of the data device connected to each circuit Procedure 18-1 To specify an RS-232 DCM CONFIG — POSITION — ↵ — TYPE — DATA — RS-232 where pp is 1 or 9 18.2 RS-232 DCM circuit operating parameters Once you configure the module position, the two circuits (numbered 1 and 2) assume the default settings for each of the following operating parameters: • device mode • device gender • full duplex • RTS/CTS delay • control signals • data structure (asynchronous only) • clocking (synchronous only) • multidrop data bridge • rate adaption • transport bandwidth • transport position • signaling and the signaling bit position • interface speed (or data rate) • data position For information on configuring rate adaption, see chapters 21 and 22. 18-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 18 — RS-232 DCM 18.3 Device mode The RS-232 DCM supports two device modes: • synchronous • asynchronous When you configure a circuit as synchronous, clocking parameters must be set (see section 18.9). When configured as asynchronous, the data structure must be set (see section 18.8). For more information on device mode, see section 17.3. Note — If asynchronous mode is selected, transparent rate adaption cannot be used. Procedure 18-2 To set the device mode CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE SYNC*/ASYNC SK000495 where pp is 1 or 9, and c is 1 or 2 * Default 18.4 Device gender The RS-232 DCM supports two device genders: • DTE • DCE For more information on device gender, see section 17.4. 2902 MainStreet Technical Practices 18-3 May 2002 90-2906-01 18 — RS-232 DCM Procedure 18-3 To set the device gender Select DTE if the device connected to the RS-232 DCM circuit is DCE. Select DCE if the device is DTE. CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE DCE*/DTE SK000496 where pp is 1 or 9, and c is 1 or 2 * Default 18.5 Full duplex Full-duplex transmission uses two independent transmission paths, one in each direction, allowing two connected devices to transmit and receive data simultaneously. You cannot configure the duplex method for RS-232 DCMs; it is automatically set to full duplex. If the RS-232 DCM is designated as a multidrop slave, the duplex method is automatically set to half duplex. 18.6 RTS/CTS delay The RTS/CTS delay regulates data flow on half-duplex lines. For more information, see section 17.6. The range for RTS/CTS delay is 0 to 140 ms in 10-ms increments. Specify the delay in tens of ms from 0 to 14 where, for example, 0 is 0 ms, 2 is 20 ms, 14 is 140 ms. The default is 0 ms. The actual delay time may be up to 20 ms longer than the configured delay time. For example, by setting the RTS/CTS delay time to 0 ms, an actual delay of 0 to 20 ms could result. Procedure 18-4 To set the RTS/CTS delay The RTS/CTS softkey appears only if the circuit is configured as a multidrop data bridge slave. CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — RTS/CTS — ↵ where pp is 1 or 9, and c is 1 or 2 delay time is from 0 to 140 ms in 10-ms increments (0 ms*) 18-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 18 — RS-232 DCM 18.7 Control signals Control signals provide the handshaking required for call setup, call tear-down and synchronization. Control signals can be configured as: • high (ON) • low (OFF) • end-to-end (END_TO_END) End-to-end means the state of the local signal follows that of the signal source at the remote end of the network. This option is only available for HCM rate adaption. The supported control signals for the RS-232 DCM depend upon the operating mode of the circuit. Table 18-1 shows the default states of the supported control leads for the various operating modes. Table 18-1 RS-232 DCM control signals Operating mode Inputs Outputs Async DCE RTS END_TO_END CTS END_TO_END DTR END_TO_END DSR FORCED ON Async DTE DCD END_TO_END RTS END_TO_END DSR END_TO_END DTR FORCED ON (1) Sync DCE (Slave or External) RTS END_TO_END CTS END_TO_END Sync DTE (Internal) — — RTSEND_TO_END Sync DTE (Slave or External) DCD END_TO_END RTS END_TO_END Note (1) RTS-CTS signaling is supported locally when CTS is configured END-TO-END. RTS-DCD end-to-end signaling is not supported. DTR and DSR are not functional. An RTS lead raised on the local end is propagated to the remote end as DCD. The remote end must be able to extract the lead as DCD and pass it on to the user equipment. RS-232 DCMs have limited control lead capability; therefore, they cannot extract and pass on the DCD lead to be output as CTS. In order to operate in sync DCE mode, then, the user must have an EIA/TIA-232 DTU at the remote end providing full control lead support. 2902 MainStreet Technical Practices 18-5 May 2002 90-2906-01 18 — RS-232 DCM Procedure 18-5 To set RS-232 DCM control signals Selecting ON or OFF for inputs configures them as ASSUMED_ON or ASSUMED_OFF. Selecting ON or OFF for outputs configures them as FORCED_ON or FORCED_OFF. CONFIG — CIRCUIT — ↵ — FUNCTION — CTRL_LEADS INPUTS OUTPUTS DTR RTS DSR DCD CTS ON OFF END_TO_END SK000504 where pp is 1 or 9, and c is 1 or 2 18.8 Data structure (asynchronous only) The data structure of asynchronous transmission has three configurable characteristics: • character length • number of stop bits • type of parity Note — A character must be 8, 9, 10 or 11 bits. The number of bits in a character is the sum of the start bit (always 1), character length (5, 6, 7 or 8), stop bits (1 or 2) and parity bit (0 for no parity or 1 for odd, even, mark or space). For example, if the character length is set to 5 bits and the number of stop bits is set to 1, the parity cannot be set to no parity. If this rule is broken, the relevant softkeys are not displayed. Character length Character length is the number of data bits used to transmit a character in asynchronous transmission. Character length can be set to: • 5 bits • 6 bits • 7 bits • 8 bits (default) 18-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 18 — RS-232 DCM Stop bits Stop bits signify the end of a character in asynchronous transmission. The number of stop bits can be set to: • 1 bit (default) • 2 bits Parity Parity is an error detection method that adds an extra bit to each transmitted character. It is based on the number of zeros or ones in each character. Five parity schemes are supported: • no parity (default) • odd • even • mark • space Procedure 18-6 To set the data structure CONFIG — CIRCUIT — ↵ — FUNCTION STOP_BITS CHAR_LEN PARITY 5_BITS 6_BITS 7_BITS 8_BITS* 1_BIT* 2_BITS NONE* ODD EVEN MARK SPACE SK000499 where pp is 1 or 9, and c is 1 or 2 * Default 18.9 Clocking (synchronous only) Synchronous data devices require two clocking signals: one for the receive data stream and one for the transmit data stream. The receive clock supplies timing for receive data; the transmit clock supplies timing for transmit data. Transmit data and receive data are defined relative to the data device configured as DTE; the transmit clock is used by the DTE device to transmit data and by the DCE device to receive data. Figure 18-1 shows these relationships. 2902 MainStreet Technical Practices 18-7 May 2002 90-2906-01 18 — RS-232 DCM Figure 18-1 Transmit and receive clocks Transmit clock Transmit data DTE DCE data data device device Receive data Receive clock 1535 The two parameters for configuring clocking for synchronous transmissions are: • transmit clock source • type of synchronous clocking Transmit clock source Table 18-2 explains the clock sources for DCE and DTE circuit genders. Table 18-2 EIA/TIA-232 clock sources Clocking source Meaning DCE External The user equipment provides the transmit clock. Slave The circuit extracts transmit clock timing from the data stream. DTE Internal A baud rate generator on the DCM provides the transmit clock. The baud rate generator is locked to the system timing. External The user equipment provides the transmit clock. Slave The circuit extracts transmit clock timing from the data stream. Type of synchronous clocking When you configure the type of synchronous clocking, you define the effect the 2902 MainStreet system has on clocks passing through it. The type can be set: • to the timing of the 2902 MainStreet system (LOCKED) (default) • to be passed through transparently (INDEPNT) Receive clock The receive clock on RS-232 DCMs with revision 2 DRAGA can be inverted. The default is no inversion. Receive clock inversion can compensate for a phase shift between the transmit clock and receive data signals, if it occurs. 18-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 18 — RS-232 DCM If you are experiencing high bit error rates due to a combination of interface speed, cable length and DCM clocking configurations, try inverting the receive clock (RX_INV). Procedure 18-7 To configure clocking The INTERNAL softkey is not available when transparent rate adaption is selected. CONFIG — CIRCUIT — ↵ — FUNCTION — CLOCKING INTERNAL EXTERNAL SLAVE* LOCKED* RX_INV /INDEPNT /NO_RX_INV* SK000506 where pp is 1 or 9, and c is 1 or 2 * Default 18.10 Multidrop data bridge In a multidrop data bridge, several broadcast destination circuits (called slaves) take turns using the same bandwidth to communicate with one broadcast source circuit (called the master); for example, several terminals would take turns communicating with a host computer. The master device controls the use of the shared bandwidth by polling each slave in turn. Figure 18-2 shows a multidrop data bridge. Figure 18-2 Multidrop data bridge Responding Aggregate Branch Multidrop data bridge circuits circuit Master Slave device devices Polling 2285 To create a multidrop bridge, two components are needed: a data interface that supports the multidrop function and a multidrop data bridge. The 2902 MainStreet unit supports the multidrop interfaces but does not provide the multidrop data bridge. One way to use a 2902 MainStreet unit in this type of application is in conjunction with a 3600 MainStreet Multiservice Bandwidth Manager containing a Sub-Rate Interface module (SRM). 2902 MainStreet Technical Practices 18-9 May 2002 90-2906-01 18 — RS-232 DCM Master and slave circuits must be configured with the same starting data position and transport bandwidth (see chapters 21 and 22). To facilitate this, the 2902 MainStreet system automatically sets the master circuit configuration to full duplex and signaling off, and the slave circuit configuration to half duplex and signaling off. These settings allow you to overlap the position of the data from these circuits. For circuits in a multidrop data bridge, if the circuit is configured as gender DCE, the DCD control signal must be forced on. If the circuit is configured as gender DTE, the RTS control signal must be forced on. Do not use the copy adjust function when configuring circuits that are to be part of the same multidrop data bridge. Procedure 18-8 To configure a master or slave device CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — MULTIDROP DISABLE* MASTER SLAVE SK000501 where pp is 1 or 9, and c is 1 or 2 * Default 18-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs 19.1 Understanding X.21 and V.35 DCMs 19-2 19.2 X.21 and V.35 circuit operating parameters 19-2 19.3 Device mode 19-4 19.4 Device gender 19-4 19.5 Duplex method 19-5 19.6 RTS/CTS delay 19-6 19.7 Control signals 19-7 19.8 Data structure (asynchronous only) 19-8 19.9 Clocking (synchronous only) 19-9 19.10 Multidrop data bridge 19-12 19.11 Super-rate configuration for the X.21 and V.35 DCMs 19-13 2902 MainStreet Technical Practices 19-1 May 2002 90-2906-01 19 — X.21 and V.35 DCMs 19.1 Understanding X.21 and V.35 DCMs The X.21 and V.35 DCMs are single-circuit modules that offer data connectivity conforming to X.21 and V.35 standards respectively. The modules can be installed in either interface module position on the Control card. These modules support subrate interface speeds (up to 64 kb/s) and super-rate interface speeds (two connections up to 1024 kb/s each, or a single connection up to 1920 kb/s). If super-rate speeds are used, additional module positions must be reserved, as described in section 19.11. Data devices connect directly to these DCMs, eliminating the need for an external DTU. You must configure a module position for an X.21 or V.35 DCM before you can configure the circuits of the module. Procedure 19-1 To specify an X.21 or V.35 DCM CONFIG — POSITION — ↵ — TYPE — DATA X.21_DCM V.35_DCM SK000508 where pp is 1 or 9 19.2 X.21 and V.35 circuit operating parameters Before implementing any of the procedures in this chapter, you must know the operating characteristics of the data device to be connected to the circuit. Once you configure the module position, the circuit on the module assumes the default settings and can be cross-connected. If you try to modify or cross-connect the circuit on an unconfigured module position, the display presents an error message. 19-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs The circuit configuration parameters for the X.21 and V.35 DCMs are: • device mode • device gender • duplex method • RTS/CTS delay • control signals • data structure (asynchronous only) • clocking (synchronous only) • multidrop data bridge • rate adaption • transport bandwidth • transport position • signaling and the signaling bit position • interface speed (or data rate) • data position For information on configuring rate adaption, see chapters 21 and 22. Note — Some of the procedures in this chapter use the FUNCTION softkey. This softkey might not appear if the specified circuit is connected, in which case you must disconnect the circuit before changing its function. Figure 19-1 shows an example of the data circuit operating parameters, with defaults. This chapter describes the configuration of the parameters listed above. Figure 19-1 Data circuit operating parameters 2902 MainStreet 82211-ab-cd Alarms:1 No Date 1:07P DATA CCT: M01-01 NAME: B7 B6 B5 B4 B3 B2 B1 B0 Configured As : SYNC-CDE-FULL DUPLEX F0 F S D D D D D D Rate Adaption : HCM-64 Kbps F1 D D D D D D - - Transport Posn : B7 F2 - - - - - - - - Interface Speed : 9600 bps F3 - - - - - - - - Data Position : F0-B5 F4 - - - - - - - - Signalling : ON F5 - - - - - - - - Multi-Drop : DISABLED F6 - - - - - - - - Clock : SLAVE - LOCKED F7 - - - - - - - - F8 - - - - - - - - F9 - - - - - - - - D - DATA F - FRAMING BIT S - SIGNALLING BIT CONFIG CIRCUIT 1-1 1-SHOW_GROUP 2-NAME 3-COPY_TO 4-COPY_ADJ 5-FUNCTION 6- 7-MORE... 8-CANCEL 9-QUIT 0- 2902 MainStreet Technical Practices 19-3 May 2002 90-2906-01 19 — X.21 and V.35 DCMs 19.3 Device mode The circuit on the X.21 and V.35 DCMs supports two device modes: • synchronous • asynchronous When the circuit is configured as synchronous, clocking parameters must be set (see section 19.9). When the circuit is configured as asynchronous, the data structure must be set (see section 19.8). For more information on device mode, see section 17.3. Note — If asynchronous mode is selected, transparent rate adaption cannot be used. Procedure 19-2 To set the device mode CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE SYNC*/ASYNC SK000495 where pp is 1 or 9, and c is 1 * Default 19.4 Device gender The circuit on the X.21 and V.35 DCMs supports two device genders: • DTE • DCE For more information on device gender, see section 17.4. 19-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Procedure 19-3 To set the device gender CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE DCE*/DTE SK000496 where pp is 1 or 9, and c is 1 * Default 19.5 Duplex method Data circuits support two duplex modes: • half-duplex • full-duplex Half-duplex transmission uses a single transmission path. Two connected devices can transmit and receive, but not at the same time. If you select half duplex, the RTS/CTS delay option can be configured (described in section 19.6). Full-duplex transmission uses two independent transmission paths, one in each direction, allowing two connected devices to transmit and receive data simultaneously. X.21 circuits The duplex method is not configurable for X.21 DCMs; it is set to full-duplex automatically. V.35 circuits The duplex method is configurable except when a circuit is configured for a multidrop data bridge (see section 19.10), in which case the duplex method is the automatically changed to full-duplex for a multidrop master circuit or half-duplex for a multidrop slave circuit. 2902 MainStreet Technical Practices 19-5 May 2002 90-2906-01 19 — X.21 and V.35 DCMs Procedure 19-4 To set the duplex method CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE HALF_DPLX/FULL_DPLX* SK000497 where pp is 1 or 9, and c is 1 * Default 19.6 RTS/CTS delay The RTS/CTS delay regulates data flow on half-duplex lines. For more information, see section 17.6. X.21 circuits The RTS/CTS delay does not apply to X.21 circuits. V.35 circuits The range for RTS/CTS delay is 0 to 160 ms in 10-ms increments. Specify the delay in tens of ms from 0 to 16 where, for example, 0 is 0 ms, 2 is 20 ms, 16 is 160 ms. The default is 0 ms. The actual RTS to CTS delay time may be up to 5 ms longer than the configured delay time. For example, by setting the RTS/CTS delay time to 0 ms, an actual delay of 0 to 5 ms could result. This delay is in addition to any transmission delay (which may be up to 500 ms for satellite links). Procedure 19-5 To set the RTS/CTS delay The RTS/CTS softkey appears after the circuit has been configured as half-duplex. CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — RTS/CTS — ↵ where pp is 1 or 9, and c is 1 delay time is from 0 to 160 ms in 10-ms increments (0 ms*) 19-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs 19.7 Control signals Control signals provide the handshaking required for call setup, call tear-down and synchronization. Control signals can be configured as: • high (ON) • low (OFF) • end to end (END_TO_END) End-to-end means the state of the local signal follows that of the signal source at the remote end of the network. This option is only available when HCM rate adaption is used. Note — Control signals are the only interface parameter that can be set for a circuit that is configured as a timing source. It is also the only interface parameter that can be changed when a circuit is connected. Table 19-1 shows the default control signals settings. If the device is configured as synchronous, DTR and DSR are not functional for V.35 DCMs. Table 19-1 X.21 and V.35 DCM control signal defaults Operating mode Inputs Outputs X.21 module DTE I END_TO_END C END_TO_END DCE C END_TO_END I END_TO_END V.25 module DTE DCD END_TO_END RTS END_TO_END ALB DCE RTS END_TO_END DCD END_TO_END CTS 2902 MainStreet Technical Practices 19-7 May 2002 90-2906-01 19 — X.21 and V.35 DCMs Procedure 19-6 To set the X.21 and V.35 control signals CONFIG — CIRCUIT — ↵ — FUNCTION — CTRL_LEADS INPUTS OUTPUTS DCD CTS ALB RTS I C ON OFF END_TO_END SK000512 where pp is 1 or 9, and c is 1 19.8 Data structure (asynchronous only) The data structure of asynchronous transmission has three configurable characteristics: • character length • number of stop bits • type of parity Note — A character must be 8, 9, 10 or 11 bits. The number of bits in a character is the sum of the start bit (always 1), character length (5, 6, 7 or 8), stop bits (1 or 2) and parity bit (0 for no parity or 1 for odd, even, mark or space). For example, if the character length is set to 5 bits and the number of stop bits is set to 1, the parity cannot be set to no parity. If this rule is broken, the relevant softkeys are not displayed. Character length Character length is the number of data bits used to transmit a character in asynchronous transmission. Character length can be set to: • 5 bits • 6 bits • 7 bits • 8 bits (default) 19-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Stop bits Stop bits signify the end of a character in asynchronous transmission. The number of stop bits can be set to: • 1 bit (default) • 2 bits Parity Parity is an error detection method that adds an extra bit to each transmitted character. It is based on the number of zeros or ones in each character. Five parity schemes are supported: • no parity (default) • odd • even • mark • space Procedure 19-7 To set the data structure CONFIG — CIRCUIT — ↵ — FUNCTION STOP_BITS CHAR_LEN PARITY 5_BITS 6_BITS 7_BITS 8_BITS* 1_BIT* 2_BITS NONE* ODD EVEN MARK SPACE SK000499 where pp is 1 or 9, and c is 1 * Default 19.9 Clocking (synchronous only) Synchronous data devices require two clocking signals: one for the receive data stream and one for the transmit data stream. The receive clock supplies timing for receive data; the transmit clock supplies timing for transmit data. Transmit data and receive data are defined relative to the data device configured as DTE; the transmit clock is used by the DTE device to transmit data and by the DCE device to receive data. Figure 19-2 shows these relationships. 2902 MainStreet Technical Practices 19-9 May 2002 90-2906-01 19 — X.21 and V.35 DCMs Figure 19-2 Transmit and receive clocks Transmit clock Transmit data DTE DCE data data device device Receive data Receive clock 1535 The two parameters for configuring clocking for synchronous transmissions are: • transmit clock source • type of synchronous clocking Transmit clock source When the device mode is synchronous, the clocking source between X.21 or V.35 DCM and the attached data device is selectable. The transmit clock can be supplied by: • the attached device (EXTERNAL) • the data circuit to which the device is attached (INTERNAL) • a remote source (SLAVE) (default) How this parameter is set depends on whether the circuit is in DCE or DTE mode. Table 19-2 gives the transmit clock options for the DTE and DCE modes. Table 19-2 X.21 and V.35 DCM clock sources Gender of Clocking Meaning circuit source X.21 circuit DCE and Slave The circuit extracts the transmit clock from the data stream. DTE V.35 circuit DCE Internal A baud rate generator on the DCM provides the transmit clock. The baud rate generator is locked to the system timing. DTE Internal A baud rate generator on the DCM provides the transmit clock. The baud rate generator is locked to the system timing. External The user equipment provides the transmit clock. Slave The circuit extracts the transmit clock from the data stream. 19-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Type of synchronous clocking For both the X.21 and V.35 DCMs, when you configure the type of synchronous clocking, you are configuring the effect that the 2902 MainStreet system has on clocks passing through it. The type can be set: • to the timing of the 2902 MainStreet system (LOCKED) (default) • to be passed through transparently (INDEPNT) If the clocking for a circuit is independent, the clocking information is embedded in the signaling bit of an HCM frame and passed through transparently. Deviations of up to 50 b/s relative to the nominal rate can be accommodated. For more information, ask your supplier representative for Configuration Note NCN305, entitled “Data Interface Clocking”. Note — The INTERNAL softkey is not available if transparent rate adaption is selected. Receive clock The receive clock on X.21 DCMs with revision 2 DRAGA can be inverted. The default is no inversion. Receive clock inversion can compensate for a phase shift between the transmit clock and receive data signals, if it occurs. If you are experiencing high bit error rates (sometimes due to a combination of interface speed, cable length and DCM clocking configurations) try inverting the receive clock (RX_INV). Procedure 19-8 To configure clocking The RX_INV/NO_RX_INV softkey applies to the X.21 circuits only. CONFIG — CIRCUIT — ↵ — FUNCTION — CLOCKING INTERNAL EXTERNAL SLAVE* LOCKED* RX_INV /INDEPNT /NO_RX_INV* SK000506 where pp is 1 or 9, and c is 1 * Default 2902 MainStreet Technical Practices 19-11 May 2002 90-2906-01 19 — X.21 and V.35 DCMs 19.10 Multidrop data bridge In a multidrop data bridge, several broadcast destination circuits (called slaves) take turns using the same bandwidth to communicate with one broadcast source circuit (called the master); for example, several terminals would take turns communicating with a host computer. The master device controls the use of the shared bandwidth by polling each slave in turn. Figure 19-3 shows a multidrop data bridge. Figure 19-3 Multidrop data bridge Responding Aggregate Branch Multidrop data bridge circuits circuit Master Slave device devices Polling 2285 To create a multidrop bridge, two components are needed: a data interface that supports the multidrop function and a multidrop data bridge. The 2902 MainStreet unit supports the multidrop interfaces but does not provide the multidrop data bridge. One way to use a 2902 MainStreet unit in this type of application is in conjunction with a 3600 MainStreet Multiservice Bandwidth Manager containing a Sub-Rate Interface module (SRM). Master and slave circuits must be configured with the same starting data position and transport bandwidth (see chapters 21 and 22). To facilitate this, the 2902 MainStreet system automatically sets the master circuit configuration to full duplex and signaling off, and the slave circuit configuration to half duplex and signaling off. These settings allow you to overlap the position of the data from these circuits. For circuits in a multidrop data bridge, if the circuit is configured as gender DCE, the DCD control signal must be forced on. If the circuit is configured as gender DTE, the RTS control signal must be forced on. Do not use the copy adjust function when configuring circuits that are to be part of the same multidrop data bridge. X.21 circuits Multidrop data bridge is not supported by X.21 circuits. V.35 circuits Each data circuit is designated as one of the following: • master (MASTER) • slave (SLAVE) • not part of a multidrop data bridge (DISABLE) 19-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Procedure 19-9 To configure a master or slave device CONFIG — CIRCUIT — ↵ — FUNCTION — I/F_MODE — MULTIDROP DISABLE* MASTER SLAVE SK000501 where pp is 1 or 9, and c is 1 * Default 19.11 Super-rate configuration for the X.21 and V.35 DCMs A super-rate circuit occupies more than one contiguous DS0 channel on a primary rate link. Each logical module position represents two DS0 channels, or 128 kb/s of bandwidth. The 2902 MainStreet system supports two super-rate connections of up to 1024 kb/s (for X.21 or V.35 DCMs in logical module positions M01 or M09), or one super-rate connection of up to 1920 kb/s (for a module in logical position M01). The 2902 MainStreet system performs delay equalization using an EDX on the Control card. Super-rate circuits on an X.21 or V.35 module are subject to the following limitations. • If the circuit is already connected, the interface speed and transport bandwidth cannot be changed. • Protection switching for super-rate circuits is not supported. • Tandem super-rate connections (connections between two primary rate modules) are not supported on the 2902 MainStreet system. To make a super-rate circuit connection, cross-connect an X.21 or V.35 DCM circuit with the master primary rate circuit (the master circuit is the first of the contiguous channels on the primary rate link). The slave circuits are protected by the circuits associated with the reserved module positions (slave circuits are the channels contiguous with the master circuit). For more information on connecting super-rate circuits, see section 23.3. To disconnect a super-rate circuit, see section 23.6. Configuration overview To configure an X.21 or V.35 circuit for super-rate: 1 Configure the circuit for transparent rate adaption. 2 Determine the transport bandwidth and interface speed, and use these values to verify that they are compatible; that is, the ratio of interface speed to transport bandwidth is a whole number (see “Setting the super-rate interface speed”). 2902 MainStreet Technical Practices 19-13 May 2002 90-2906-01 19 — X.21 and V.35 DCMs 3 Set the transport bandwidth. 4 Set the interface speed. Setting the super-rate interface speed The interface speed and the transport bandwidth determine the number of channels required on the primary rate link for the super-rate circuit. This number, called the multiplier, is determined by the calculation: multiplier = interface speed / transport bandwidth where the interface speed is the data rate of the data device, the transport bandwidth is the bandwidth used in each primary rate channel, and the multiplier is a whole number between 1 and 30. The transport bandwidth must divide evenly into the interface speed. Table 19-3 lists the valid interface speeds for a given transport bandwidth, the number of primary rate channels used (the multiplier), and the number of reserved module positions. For example, for an interface speed of 400 kb/s and a transport bandwidth of 40 kb/s, the multiplier is 10. Ten channels are used for the super-rate circuit connection. Restrictions If the interface speed is not a whole number multiple of the transport bandwidth, the message “Invalid speed” is displayed. If the interface speed entered is too large for the number of available logical module positions, the entered interface speed is not accepted and the message “Not enough additional positions available to support I/F speed” is displayed. If you change the transport bandwidth after the super-rate circuit is configured but before it has been connected, the interface speed changes automatically to keep the same multiple. The reverse is not true: changing the interface speed does not change the transport bandwidth. 19-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Table 19-3 Super-rate speeds, required channels and module positions DS0s used Reserved Transport bandwidth (kb/s) positions 816 24 32 40 48 56 64 16 32 48 64 80 96 112 128 2 0 or 7 24 48 72 96 120 144 168 192 3 7 256 32 64 96 128 160 192 224 4 7 40 80 120 160 200 240 280 320 5 7 48 96 144 192 240 288 336 384 6 7 448 7 7 56 112 168 224 280 336 392 8 7 64 128 192 256 320 384 448 512 9 72 144 216 288 360 432 504 576 7 640 80 160 240 320 400 480 560 10 7 88 176 264 352 440 528 616 704 11 7 96 192 288 384 480 576 672 768 12 7 104 208 312 416 520 624 728 832 13 7 Interface speed 14 7 112 224 336 448 560 672 784 896 (kb/s) 15 7 120 240 360 480 600 720 840 960 16 128 256 384 512 640 768 896 1024 7 1088 136 272 408 544 680 816 952 17 15 144 288 432 576 720 864 1008 1152 18 15 152 304 456 608 760 912 1064 1216 19 15 1280 20 160 320 480 640 800 960 1120 15 168 336 504 672 840 1008 1176 1344 21 15 176 352 528 704 880 1056 1232 1408 22 15 1472 23 184 368 552 736 920 1104 1288 15 192 384 576 768 960 1152 1344 1536 24 15 200 400 600 800 1000 1200 1400 1600 25 15 1664 26 208 416 624 832 1040 1248 1456 15 216 432 648 864 1080 1296 1512 1728 27 15 224 448 672 896 1120 1344 1568 1792 28 15 232 464 696 928 1160 1392 1624 1856 29 15 240 480 720 960 1200 1440 1680 1920 30 15 9452 Reserved module positions To guarantee sufficient bandwidth on the primary rate link for super-rate connections greater than 128 kb/s, the 2902 MainStreet system automatically reserves module positions contiguous with the module position of the X.21 or V.35 DCM. The reserved positions protect their associated DS0s. Logical module position M01 can reserve 7 or 15 positions (for speeds of up to 1024 or 1920 kb/s, respectively); position M09 can reserve 7 positions (for speeds of up to 1024 kb/s). 2902 MainStreet Technical Practices 19-15 May 2002 90-2906-01 19 — X.21 and V.35 DCMs Before position M01 can reserve 15 positions, position M09 must be configured as EMPTY. This disables position M09. As long as position M09 is reserved (disabled), removing or installing a module in position M09 (physical position 2 on the Control card) does not generate module insertion or removal alarms. The display does not show that there is an installed module, if one is installed, and maintenance information about position M09 is not available. Figure 19-4 shows a display where position 1 has reserved 7 positions. Note — There is a maximum of 31 DS0 connections allowed between the interface modules and the primary rate modules. Thus, two super-rate connections of 1920 kb/s each (one to each primary rate aggregate) are not possible. Figure 19-4 Reserved module positions 2902 MainStreet 82211-ab-cd Alarms:25 No Date 2:18R # Configured Installed Stat # Configured Installed Stat --------------------------------- --------------------------------- M01 X21_DCM X21_DCM Ok M09 DNIC - Prob M02 RESERVED - Ok M10 - - - M03 RESERVED - Ok M11 - - - M04 RESERVED - Ok M12 - - - M05 RESERVED - Ok M13 - - - M06 RESERVED - Ok M14 - - - M07 RESERVED - Ok M15 - - - M08 RESERVED - Ok M16 - - - P1 E1 E1 OOS P2 E1 E1 OOS DSP - - - CONFIG 1-POSITION 2-CIRCUIT 3-CONNECT 4-SYNCH 5- 6-SHOW_ALL 7- 8-CANCEL 9-QUIT 0- Restrictions For logical module position M01, attempting to reserve a number of positions other than 7 or 15 displays the message “Only 7 or 15 positions can be reserved”. For position M09, attempting to reserve a number of positions other than 7 displays the message “Only 7 positions can be reserved”. If position M09 is reserved by position M01, position M09 cannot be configured. Attempting to configure position M09 displays the message “Cannot configure, position reserved by M01”. Attempting to reserve too few module positions displays the message “Not enough reserved positions to support I/F speed”. For example, the transport bandwidth is 64 kb/s, the interface speed is 1920 kb/s and the number of reserved positions is changed from 15 to 7. 19-16 2902 MainStreet Technical Practices 90-2906-01 May 2002 19 — X.21 and V.35 DCMs Attempting to set an interface speed above the maximum allowed by the transport bandwidth and the number of reserved module positions displays the message “Not enough additional positions to support I/F speed”. For example, the transport bandwidth is 64 kb/s, the number of reserved positions is 7, and an attempt to set the interface speed for 1088 kb/s is made. Attempting to change the number of reserved module positions when the super-rate circuit is connected displays the message “There is a circuit connected on the card. Disconnect it first.”. Attempting to configure a module position that is reserved displays the message “This logical position cannot be configured”. Procedure 19-10 To reserve module positions Module positions M01 and M09 can reserve seven module positions. If module position M09 is configured as EMPTY, module position M01 has the option of reserving 7 or 15 positions. CONFIG — POSITION — ↵ — OPTIONS — NUM_RESERV — ↵ where pp is the module position, either 1 or 9 n is the number of reserved module positions, 7 or 15 Procedure 19-11 To configure transparent rate adaption CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — METHOD — TRANSPAREN where pp is 1 or 9, and c is 1 Procedure 19-12 To set the transport bandwidth Transport bandwidth is configured in 8 kb/s blocks, where: transport bandwidth = transp_bw_multiplier × 8 kb/s CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — TRANSP_BW — ↵ where pp is 1 or 9, and c is 1 transp_bw_multiplier is an integer, 1 to 8 2902 MainStreet Technical Practices 19-17 May 2002 90-2906-01 19 — X.21 and V.35 DCMs Procedure 19-13 To set the interface speed CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — I/F_SPEED — ↵ where pp is 1 or 9, and c is 1 speed is the interface speed in kb/s 19-18 2902 MainStreet Technical Practices 90-2906-01 May 2002 20 — Codirectional DCM 20.1 Understanding the Codirectional DCM 20-2 20.2 Codirectional DCM Module and circuit parameters 20-2 20.3 Trunk conditioning 20-3 20.4 Alarm times 20-3 20.5 8 kHz timing 20-4 20.6 All Ones alarm indication signal 20-4 2902 MainStreet Technical Practices 20-1 May 2002 90-2906-01 20 — Codirectional DCM 20.1 Understanding the Codirectional DCM The Codirectional DCM provides an interface for two 64 kb/s full-duplex synchronous E1 circuits conforming to ITU-T G.703. ITU-T G.703 describes a codirectional interface which transmits 64 kb/s data over four wires. The Codirectional DCM does not support out-of-band DS0 signaling or super-rate connections. The Codirectional DCM can be installed in either interface module position on the Control card. An NTU that conforms to the ITU-T G.703 recommendation for a 64 kb/s codirectional interface is needed for each circuit. Before any of the procedures in this chapter can be implemented, you must: • specify the module position(s) for the Codirectional DCM • know the operating characteristics of the NTU to be connected to the circuit When you specify the module position, the circuits on the module in that position assume the default settings and can be cross-connected. If you try to modify or cross-connect circuits on a module position before it has been specified, the display presents an error message. Procedure 20-1 To specify a Codirectional DCM CONFIG — POSITION — ↵ — TYPE — DATA — CODIR_DCM where pp is 1 or 9 20.2 Codirectional DCM Module and circuit parameters The configurable module parameters for the Codirectional DCM are: • trunk conditioning • alarm times The configurable circuit parameters for the Codirectional DCM are: • 8 kHz timing • all ones alarm indication signal Note — The circuit configuration procedures use the FUNCTION softkey. This softkey might not appear if the specified circuit is connected, in which case you must disconnect the circuit before changing its function. 20-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 20 — Codirectional DCM 20.3 Trunk conditioning The Codirectional DCM performs trunk conditioning when it detects a loss of input. Trunk conditioning defines the type of data transmitted on the information path. Trunk conditioning can be defined for all outgoing transmissions on the Codirectional DCM. The two trunk conditioning options are: • two-way • one-way When using one-way trunk conditioning, the path is broken only in the direction of the fault. This means that the receive path will be broken and the transmit path will not. For two-way trunk conditioning, the path is broken in both directions. This means that both the receive path and the transmit path will be broken. If you change trunk conditioning, operation is disrupted. If you select two-way trunk conditioning, loss of input is raised for each input and must be cleared before circuits are reconnected. Note — CPSS circuits are disconnected on any link failure regardless of the configured trunk conditioning. Procedure 20-2 To configure trunk conditioning CONFIG — POSITION — ↵ — OPTIONS — TRUNK_COND ONE_WAY/TWO_WAY* SK000516 where pp is 1 or 9 * Default 20.4 Alarm times Alarm declaration and clearing times can be set for the Codirectional DCM. The range for both of these times is 0.1 to 10 seconds. The default for alarm declaration is 0.8 second and for alarm clearing is 10 seconds. 2902 MainStreet Technical Practices 20-3 May 2002 90-2906-01 20 — Codirectional DCM Procedure 20-3 To configure alarm times CONFIG — POSITION — ↵ — OPTIONS — ALARM_TIME DECLARE CLEAR ↵ ↵ SK000517 where pp is 1 or 9 time is 0.1 to 10 seconds in increments of 0.1 second 20.5 8 kHz timing You can configure the Codirectional DCM to generate 8 kHz timing when a circuit is disconnected. Generating 8 kHz timing after a circuit is disconnected prevents the far end from entering the AIS No 8K alarm condition. The AIS No 8K alarm condition is raised whenever 8 kHz timing is not on the input of a Codirectional DCM circuit. The two circuits on the Codirectional DCM can be set for: • 8 kHz timing upon circuit disconnection (8K_TIMING) • no 8 kHz timing upon circuit disconnection (NO_8K) (default) Procedure 20-4 To configure 8 kHz timing CONFIG — CIRCUIT — ↵ — FUNCTION — TRUNK_COND 8K_TIMING/NO_8K* SK000518 where pp is 1 or 9, and c is 1 or 2 * Default 20.6 All Ones alarm indication signal An AIS All Ones alarm is raised whenever an all ones pattern is received on the input of a Codirectional DCM circuit. The two circuits on the Codirectional DCM can be set to: • generate all ones upon circuit disconnection (AIS) (default) • not generate all ones upon circuit disconnection (NO_AIS) 20-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 20 — Codirectional DCM By default, the Codirectional DCM generates an all ones signal when a circuit is disconnected. You can configure the Codirectional DCM so that it does not generate the all ones signal, thereby preventing the far end from entering the AIS All Ones alarm condition. Procedure 20-5 To configure AIS CONFIG — CIRCUIT — ↵ — FUNCTION — TRUNK_COND AIS*/NO_AIS SK000519 where pp is 1 or 9, and c is 1 or 2 * Default 2902 MainStreet Technical Practices 20-5 May 2002 90-2906-01 20 — Codirectional DCM 20-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 21 — Transparent rate adaption 21.1 Rate adaption overview 21-2 21.2 Transparent rate adaption overview 21-2 21.3 Transport bandwidth 21-3 21.4 Transport position 21-5 2902 MainStreet Technical Practices 21-1 May 2002 90-2906-01 21 — Transparent rate adaption 21.1 Rate adaption overview Rate adaption techniques allow subrate data devices to use a 64 kb/s channel by formatting the data to conform to the primary rate framing structure. Using rate adaption, several subrate data devices can be multiplexed onto one primary rate channel. Setting rate adaption parameters defines data transport information, such as bandwidth allocation and data position within the channel. Data from each circuit must be positioned so that it does not overlap data from other circuits. Note 1 — A module position must be configured before its circuits can be configured with rate adaption parameters. Note 2 — Circuits configured as master or slave in a multidrop configuration are an exception in that they must be positioned to overlap. However, multidrop circuits should not overlap circuits that are not part of the multidrop data bridge. 21.2 Transparent rate adaption overview Transparent rate adaption provides a transparent channel (carrying data, signaling and framing information from a data device) through the node without adding any signaling or framing information. Transparent rate adaption divides a 64 kb/s channel into eight elements; each element is transmitted 8000 times per second. Each element represents 1 bit and, therefore, 8000 b/s of bandwidth. Transparent rate adaption supports synchronous data running at a rate that is a multiple of 8 kb/s. If a device is transmitting asynchronous data, transparent rate adaption cannot be used. After transparent rate adaption is selected, two parameters can be set: • transport bandwidth • transport position Figure 21-1 shows how a transparent channel is represented on an NMTI display, where each D represents 8 kb/s of bandwidth and B7 to B0 represent starting positions within the channel. Elements that do not contain a D represent unused bandwidth. Figure 21-1 shows a 32 kb/s transparent channel with starting position B7. The right side of the display shows all current circuit parameters, including the transport bandwidth (beside the Rate adaption heading) and the transport position. 21-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 21 — Transparent rate adaption Figure 21-1 Transparent frame 2902 MainStreet 82211-ab-cd Alarms:1 No Date 0:01R DATA CCT: M01-01 NAME: B7 B6 B5 B4 B3 B2 B1 B0 Configured as : SYNC-DCE-FULL DUPLEX D D D D Rate Adaption : TRANSPARENT-32 kbps Transport Posn : B7 Interface Speed : 32 kbps Data Position : NA Signalling : NA Multi-Drop : DISABLED Clock : SLAVE-LOCKED D - DATA CONFIG CIRCUIT 1-1 FUNCTION RATE_ADAPT 1-METHOD 2-TRANSP_BW 3-TRANSP_POS 4- 5-I/F_SPEED 6- 7- 8-CANCEL 9-QUIT 0- Procedure 21-1 To configure a data circuit for transparent rate adaption CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — METHOD — TRANSPAREN where pp is 1 or 9, and c is 1 or 2, or A or B 21.3 Transport bandwidth Transport bandwidth represents the bandwidth allocated to a data device. For transparent rate adaption, setting the transport bandwidth selects both the size of the channel (how much of the DS0 is used) and the interface speed (data rate) of the device. The interface speed can be any multiple of 8 kb/s up to 64 kb/s, but all speeds are not available to all DCMs. Table 21-1 lists the interface speeds supported by the DNIC, 2B1Q, RS-232 DCM, X.21 DCM and V.35 DCM. 2902 MainStreet Technical Practices 21-3 May 2002 90-2906-01 21 — Transparent rate adaption Table 21-1 Interface speeds (transparent rate adaption) Module Interface speeds (kb/s) (1) DNIC and 2B1Q 8, 16, 32, 48, 56, 64 RS-232 DCM 8, 16, 32, 48, 56, 64 (1) Manufacturing codes A and B RS-232 DCM 8, 16, 24, 32, 40, 48, 56, 64 (1) Manufacturing code D V.35 DCM 8, 16, 24, 32, 40, 48, 56, 64 X.21 DCM 8, 16, 24, 32, 40, 48, 56, 64 Note (1) For DNIC and 2B1Q modules connected to EIA/TIA-232 devices and for RS-232 DCMs, operation at interface speeds above 38.4 kb/s is not guaranteed. For speeds above 38.4 kb/s, V.35 or X.21 interfaces should be used. If speeds above 38.4 kb/s are being used for RS-232, short high-grade shield cable should be used. The transport bandwidth is configured by entering an integer (n) that represents the number of 8 kb/s elements (n = 1 to 8). The default is 64 kb/s (n = 8). In Figure 21-2, example a. shows the bandwidth allocation for a transparent channel with a transport bandwidth of 16 kb/s (n = 2); example b. shows 48 kb/s (n = 6) with transport position changed to B5. Figure 21-2 Transport bandwidth examples (transparent) B7 B6 B5 B4 B3 B2 B1 B0 a. DD – –– ––– B7 B6 B5 B4 B3 B2 B1 B0 b. – – D DDD DD 8989 21-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 21 — Transparent rate adaption Procedure 21-2 To set transport bandwidth Transport bandwidth and transport position are inter-related parameters, with transport position taking priority. Changing the transport position may change the transport bandwidth. See section 21.4 for details. CONFIG — CIRCUIT— ↵ — FUNCTION — RATE_ADAPT TRANS_BW ↵ SK000520 where pp is 1 or 9, and c is 1 or 2, or A or B n is 1 to 8 21.4 Transport position Transport position defines the starting position of the data within the 64 kb/s channel. There are eight possible starting position elements, identified as B7 to B0. The 2902 MainStreet system fills to the right of the starting element, with element B7 being the default setting. When assigning more than one subrate transparent channel to the same channel, you must arrange the starting elements and the transport bandwidth so that the data from different devices do not overlap. If you want to configure a number of circuits as a multidrop data bridge, you must arrange the starting elements and the transport bandwidth to be the same. See section 17.10 (for DNIC and 2B1Q modules), section 18.10 (for RS-232 DCMs) or section 19.10 (for X.21 and V.35 DCMs). Table 21-2 indicates the allowable transport position starting elements as determined by the transport bandwidth. Table 21-2 Valid transport positions for transparent rate adaption Transport bandwidth Transport position 64 kb/s (n = 8) B7 only 56 kb/s (n = 7) B7 or B6 48 kb/s (n = 6) B7, B6, B5 40 kb/s (n = 5) B7 to B4 32 kb/s (n = 4) B7 to B3 24 kb/s (n = 3) B7 to B2 16 kb/s (n = 2) B7 to B1 8 kb/s (n = 1) B7 to B0 2902 MainStreet Technical Practices 21-5 May 2002 90-2906-01 21 — Transparent rate adaption The 2902 MainStreet system gives priority to transport position over transport bandwidth. Changing the transport position may change the transport bandwidth. If there are not enough elements to the right of the transport position, the transport bandwidth is automatically reduced to the available amount, even if you have configured it for more. To increase the transport bandwidth, you may need to change the transport position first. Procedure 21-3 To set the transport position CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT TRANS_POS ↵ SK000521 where pp is 1 or 9, and c is 1 or 2, or A or B Bn is B7 to B0 21-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 22 — HCM rate adaption 22.1 Rate adaption overview 22-2 22.2 HCM rate adaption overview 22-2 22.3 Transport bandwidth 22-3 22.4 Transport position 22-5 22.5 Signaling and the signaling bit stream 22-5 22.6 Interface speed 22-6 22.7 Data position 22-8 2902 MainStreet Technical Practices 22-1 May 2002 90-2906-01 22 — HCM rate adaption 22.1 Rate adaption overview Rate adaption techniques allow subrate data devices to use a 64 kb/s channel by formatting the data to conform to the primary rate framing structure. Using rate adaption, several subrate data devices can be multiplexed onto one primary rate channel. Setting rate adaption parameters defines data transport information, such as bandwidth allocation and data position within the channel. Data from each circuit must be positioned so that it does not overlap data from other circuits. Note 1 — A module position must be configured before its circuits can be configured with rate adaption parameters. Note 2 — Circuits configured as master or slave in a multidrop configuration are an exception in that they must be positioned to overlap. However, multidrop circuits should not overlap circuits that are not part of the multidrop data bridge. 22.2 HCM rate adaption overview HCM rate adaption is an Alcatel proprietary rate adaption scheme. It allows users to establish data channels using a wider variety of interface speeds than is possible with other rate adaption techniques. HCM rate adaption divides a 64 kb/s channel into 80 elements; each element is transmitted 800 times per second. Each element represents 1 bit and, therefore, 800 b/s of bandwidth. After HCM rate adaption is selected, you can set: • transport bandwidth • transport position • signaling • interface speed • data position Figure 22-1 shows an HCM frame displayed in an NMTI screen. The HCM frame is a 10-row by 8-column matrix. The rows are named F0 to F9 and columns are named B7 to B0. An element is identified by its row and column, for example, F3-B2. The F represents an element reserved for the framing bit, which flags the start of the HCM frame. A framing bit is needed because the HCM frame pattern is independent of the primary rate framing pattern. The position of the F bit can be adjusted (see section 22.4). The S represents an element reserved for signaling when end-to-end signaling is required, which includes the clock adjustment if clocking is configured as independent. A signaling bit position is reserved only if signaling is turned on for the circuit (see section 22.5). The D represents data elements. The number of Ds is determined by the interface speed (see section 22.6). The position of the first D bit can be adjusted (see section 22.7). 22-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 22 — HCM rate adaption The F and S bits each occupy one element (800 b/s of bandwidth each). Any element that does not contain an F, S or D represents unused bandwidth. Note — Some combinations of transport bandwidth, transport position and data position parameters are incompatible. The first D bit must be in one of the columns defined by the transport position and the transport bandwidth. Figure 22-1 HCM frame 2902 MainStreet 82211-ab-cd Alarms: No Date 2:57R DATA CCT: M01-1 NAME: B7 B6 B5 B4 B3 B2 B1 B0 Configured as : SYNC-DCE-FULL DUPLEX F0 F S D D D D D D Rate Adaption : HCM - 64 kbps F1 D D D D D D - - Transport Posn : B7 F2 - - - - - - - - Interface Speed : 9600 bps F3 - - - - - - - - Data Position : F0-B5 F4 - - - - - - - - Signalling : ON F5 - - - - - - - - Multi-Drop : DISABLED F6 - - - - - - - - Clock : SLAVE-LOCKED F7 - - - - - - - - F8 - - - - - - - - F9 - - - - - - - - D - DATA F - FRAMING BIT S - SIGNALLING BIT CONFIG CIRCUIT 9-A FUNCTION RATE_ADAPT 1-METHOD 2-TRANSP_BW 3-TRANSP_POS 4-SIG_OFF 5-I/F_SPEED 6-DATA_POSN 7- 8-CANCEL 9-QUIT 0- In Figure 22-1, the transport bandwidth is 64 kb/s, the interface speed is 9600 b/s and the transport position is B7. The right side of the display shows all the current circuit parameters, including the transport bandwidth (beside the Rate adaption heading). Procedure 22-1 To configure a data circuit for HCM rate adaption CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — METHOD — HCM where pp is 1 or 9, and c is 1 or 2, or A or B 22.3 Transport bandwidth The transport bandwidth sets the number of D elements available to the data device. Unlike transparent rate adaption, setting the transport bandwidth does not set the interface speed. The interface speed is set separately (see section 22.6). 2902 MainStreet Technical Practices 22-3 May 2002 90-2906-01 22 — HCM rate adaption The transport bandwidth is set in 8 kb/s increments, where each column, having ten 800 b/s elements, represents 8 kb/s. Setting the number of columns (n = 1 to 8) sets the transport bandwidth (n x 8 kb/s). The default is 64 kb/s (n = 8). Since the default setting for transport bandwidth is 64 kb/s, you do not need to reduce the transport bandwidth unless the HCM channel is going to be: • subrate multiplexed with transparent channels • transported on a primary rate channel for which some of the bit positions are not available for data Figure 22-2 shows an example of an HCM circuit with a transport bandwidth of 48 kb/s (n = 6) and an interface speed of 9600 b/s. There are 6 columns and 12 D elements used. Figure 22-2 Transport bandwidth example (HCM) B7 B6 B5 B4 B3 B2 B1 B0 F0 FS D DD D F1 DDD DD D F2 DD–– –– F3 ––– –– – F4 ––– –– – F5 ––– –– – F6 ––– –– – F7 ––– –– – F8 ––– –– – F9 ––– –– – 8990 Note — The maximum bandwidth available to the data device is 63.2 kb/s (64 kb/s less 800 b/s for the framing bit). If signaling is on for the circuit, the signaling bit stream takes up an additional 800 b/s, leaving 62.4 kb/s of bandwidth available for data. Procedure 22-2 To set transport bandwidth CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — TRANS_BW — ↵ where pp is 1 or 9, and c is 1 or 2, or A or B n is 1 to 8 22-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 22 — HCM rate adaption 22.4 Transport position In HCM rate adaption, transport position defines the column where the F bit is located (B7 to B0). The default is B7. The F bit is always in the first row (F0). The transport position is set by entering Bn, where Bn is B0 to B7, with a default of B7. The transport position is indicated on the display by the position of the F in the circuit display and under Transport Posn on the right side of the display. Procedure 22-3 To set the transport position CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT — TRANS_POS — ↵ where pp is 1 or 9, and c is 1 or 2, or A or B Bn is B7 to B0 22.5 Signaling and the signaling bit stream The signaling parameter determines whether the data circuit in the HCM frame includes a signaling bit stream (the S in Figure 22-2). Turning signaling off means that no bandwidth is taken up by signaling and that signaling is not transmitted through the network. The signaling can be set to: • signaling on (default) • signaling off When signaling is turned on, the S bit appears in the element immediately before the first D bit. Procedure 22-4 To set the signaling CONFIG — POSITION — ↵ — FUNCTION — RATE_ADAPT SIG_ON*/SIG_OFF SK000522 where pp is 1 or 9 * Default 2902 MainStreet Technical Practices 22-5 May 2002 90-2906-01 22 — HCM rate adaption 22.6 Interface speed The interface speed (or data rate) is the rate at which the device is transmitting data. The speeds supported for HCM rate adaption are listed in Table 22-1. 22-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 22 — HCM rate adaption Table 22-1 Interface speeds (HCM rate adaption) Default Module Device mode Interface speed (b/s) (b/s) (1) DNIC and 2B1Q Asynchronous 150 300 600 1200 2400 9600 4800 9600 19 200 38 400 Synchronous 150 300 600 1200 2400 9600 4800 8000 9600 16 000 19 200 32 000 38 400 48 000 56 000 (1) (2) RS-232 DCM Asynchronous 150 300 600 1200 2400 9600 4800 9600 19 200 Synchronous 1200 2400 4800 9600 19 200 9600 32 000 38 400 48 000 56 000 (1) (3) RS-232 DCM Asynchronous 150 300 600 1200 1800 9600 2400 4800 7200 9600 14 400 19 200 38 400 Synchronous 150 300 600 800 1200 9600 1600 2400 4000 4800 7200 8000 9600 12 000 14 400 16 000 16 800 19 200 24 000 28 800 32 800 38 400 40 000 48 000 56 000 57 600 V.35 DCM Asynchronous 150 300 600 1200 1800 9600 2400 4800 7200 9600 14 400 19 200 38 400 Synchronous 150 300 600 800 1200 9600 1600 2400 4000 4800 7200 8000 9600 12 000 14 400 16 000 16 800 19 200 24 000 28 800 32 000 38 400 40 000 48 000 56 000 57 600 X.21 DCM Asynchronous 150 300 600 1200 1800 9600 2400 4800 7200 9600 14 400 19 200 38 400 Synchronous 150 300 600 800 1200 9600 1600 2400 4000 4800 7200 8000 9600 12 000 14 400 16 000 16 800 19 200 24 000 28 800 32 000 38 400 40 000 48 000 56 000 57 600 Notes 1. For DNIC and 2B1Q modules connected to EIA/TIA-232 devices and for RS-232 DCMs, operation at interface speeds above 38.4 kb/s is not guaranteed. For speeds above 38.4 kb/s, V.35 or X.21 interfaces should be used. If speeds above 38.4 kb/s are being used for RS-232, short high-grade shield cable should be used. 2. Manufacturing codes A and B. 3. Manufacturing code D. 10425 2902 MainStreet Technical Practices 22-7 May 2002 90-2906-01 22 — HCM rate adaption Oversampling Asynchronous rates of up to 2400 b/s that are not listed in Table 22-1 can be supported by oversampling. To oversample: 1 Set the device mode to synchronous (see the device mode section in the appropriate data module chapter). 2 Multiply the asynchronous rate you wish to support by 16. 3 Enter the next highest synchronous interface speed listed in Table 22-1. For example, to support 110 b/s (asynchronous), set the device mode to synchronous and the interface speed to 2400 b/s (16 x 110 b/s = 1760 b/s; 2400 b/s is the next highest synchronous rate supported). For interface speeds of 2400 b/s or less, 2.4 kb/s of bandwidth is allocated (represented by three D bits). Note — The tolerance for overspeed and underspeed is ±2.5% for asynchronous devices. Procedure 22-5 To set the interface speed CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT I/F_SPEED ↵ SK000523 where pp is 1 or 9, and c is 1 or 2, or A or B interface speed is in b/s 22.7 Data position The data position parameter specifies the location of the first data element, or D bit (see Figure 22-1). When signaling is turned on, the S bit appears in the element immediately before the first data bit. signaling is turned on by default, therefore the default data bit position is F0-B5. You need to change the data position if you are subrate multiplexing an HCM rate-adapted circuit with another HCM rate-adapted circuit (so that the S and D bits for the two circuits do not overlap). If you select a data position that is incompatible with transport position, transport bandwidth and signaling settings, an error message appears on the display. 22-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 22 — HCM rate adaption Procedure 22-6 To set the data position CONFIG — CIRCUIT — ↵ — FUNCTION — RATE_ADAPT DATA_POSN ↵ SK000524 where pp is 1 or 9, and c is 1 or 2, or A or B Ff-Bn is the data position identifier: Ff is the row number (F0 to F9), and Bn is the column number (B0 to B7) 2902 MainStreet Technical Practices 22-9 May 2002 90-2906-01 22 — HCM rate adaption 22-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits 23.1 Types of cross-connections 23-2 23.2 Simple connections 23-2 23.3 Connecting super-rate circuits 23-4 23.4 Circuit connections display 23-5 23.5 Protecting connections (RAPID protection switching) 23-5 23.6 Disconnecting connections 23-10 2902 MainStreet Technical Practices 23-1 May 2002 90-2906-01 23 — Cross-connecting circuits 23.1 Types of cross-connections Cross-connections can be basic or specialized. Basic cross-connections include the following types: • simple • super-rate • protecting Specialized cross-connections are used for the following applications: • multidrop data bridge connections (see section 17.10) • CPSS channel connections (see section 14.2) Note — Before a circuit can be cross-connected, its module position and circuit parameters must be configured. For information on module position and circuit configuration, see chapter 12. 23.2 Simple connections A simple connection is a connection between one primary rate circuit and one data circuit, or between two primary rate circuits on different primary rate modules. Simple connections are used for drop and insert as well as bypass applications (described below). They are not used for super-rate connections (see section 23.3) or protecting connections (see section 23.5). You cannot cross-connect a data circuit to a primary rate circuit and then cross-connect that primary rate circuit to another primary rate circuit. If you try to cross-connect a circuit that is already connected, a warning appears on the screen. If you proceed, the new connection is made and any existing connections involving the two original circuits are broken. When connecting a primary rate circuit to an endpoint circuit, the signaling types for both circuits must match. If the primary rate circuit is configured with its default signaling type, it automatically adopts the signaling type required by the endpoint circuit (until the circuit is disconnected). If the primary rate circuit is configured with a specific signaling type, the connection is not allowed unless the signaling types for both circuits are the same. Drop and insert configuration A drop and insert configuration uses three nodes connected in tandem, with the drop and insert node in the middle (see Figure 23-1, Node B). The drop and insert node cross-connects both through traffic and drop and insert traffic. In Figure 23-1, through traffic flows from Node A, through Node B, to Node C, using cross-connections between primary rate circuits on modules P1 and P2. 23-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits Drop traffic goes to the devices connected to the drop and insert node; insert traffic comes from the devices connected to the node. Drop and insert traffic between Nodes A and B cross-connect through P2; traffic between Nodes C and B cross-connect through P1. Figure 23-1 Drop and insert configuration Node A Node C Node B 2902 MainStreet 2902 MainStreet Power Processor Network Terminating Unit Event Status Out of Sync 1 System Status Out of Sync 2 P1 P2 Data circuit 8870 Bypass configuration A node is considered to be a bypass node when there is no traffic between its primary rate modules and its data modules. All primary rate traffic received on one primary rate module is passed to the other primary rate module. A node can be configured for bypass operation by cross-connecting circuits between the two primary rate modules. Note — If a 2902 MainStreet node loses power and there are two E1 G.703 LIMs installed, all connections are dropped and the node automatically operates as a bypass node. If one or both LIMs are E1 HDSL or E1 Optical LIMs, the node does not operate in bypass mode because E1 HDSL and E1 Optical LIMs do not have on-board bypass relays. Procedure 23-1 To cross-connect simple circuits CONFIG — CONNECT — or ↵ — TO_CIRCUIT— or ↵ where p is 1 or 2, pp is 1 or 9, and c is 1 to 31 (for primary rate), or 1, 2, A or B (for interface module) If the circuit is already connected, a warning appears on the screen. 2902 MainStreet Technical Practices 23-3 May 2002 90-2906-01 23 — Cross-connecting circuits 23.3 Connecting super-rate circuits A super-rate circuit connection is a connection between a circuit on a DNIC, 2B1Q, X.21 or V.35 module and two or more DS0 channels of a primary rate link. A super-rate connection uses a single cross-connection between the data module circuit and the master primary rate circuit (the first primary rate channel of the super-rate connection). The rest of the connection is made automatically to slave circuits (subsequent contiguous primary rate channels). DNIC and 2B1Q circuits can operate at a super-rate speed of 128 kb/s. The X.21 and V.35 circuits can operate at speeds up to 1920 kb/s. For details on configuring DNIC and 2B1Q modules for super-rate operation, see section 17.11. For details on configuring X.21 and V.35 DCMs, see section 19.11. Note — A super-rate DNIC or 2B1Q connection cannot be made unless Port B of the DNIC or 2B1Q module is disconnected. Cross-connections between super-rate circuits on two data interface modules are not supported. Table 23-1 lists the error messages that are displayed if there is a problem with the requested circuit connections. Table 23-1 Error messages for super-rate circuit connections Message Reason for message Couldn't make connection: The super-rate circuit extends beyond the number of primary rate insufficient bandwidth. channels. Cannot connect: Overlapping One of the primary rate channels is already connected in a subrate existing connection. connection or connected as a part of a super-rate connection. Circuit is in the middle of a The entered primary rate circuit is in the middle of a super-rate super-rate group. circuit. You must enter another circuit number. That circuit is already The master circuit of a super-rate connection is already connected connected. and has been entered as the first circuit in a new connection. Once the second circuit has been entered and the PROCEED softkey is selected, the first super-rate connection is removed. The second circuit is The master circuit of a super-rate connection is already connected connected, PROCEED will and has been entered as the second circuit in a new connection. override. Once the PROCEED softkey is selected, the first super-rate connection is removed. Procedure 23-2 To cross-connect super-rate circuits CONFIG — CONNECT — or ↵ — TO_CIRCUIT — or ↵ where pp is 1 or 9, p is 1 or 2, and c is 1 to 30 (for primary rate), or 1 (for X.21 or V.35 DCMs), or A (for DNIC or 2B1Q modules) 23-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits 23.4 Circuit connections display You can view a display of a single circuit connection or a group of connections. Figure 23-2 is an example of the SHOW_GROUP display, showing a simple RS-232 DCM circuit connection (P1-01 to M01-1) and a V.35 DCM super-rate cross-connection (P1-05 through P1-08 to M05-01). Current connections are indicated by an asterisk. Procedure 23-3 To display circuit connections CONFIG — CONNECT — or ↵ — SHOW_CCT*/SHOW_GROUP where pp is 1 or 9, p is 1 or 2, and c is 1 to 30 (for primary rate), or 1, 2, A or B (for interface module) * Default Figure 23-2 Circuit connections display 2902 MainStreet 82211-ab-cd OSLO Alarms:2 09-JAN-1997 10:19A Circuit Name Type Circuit Name Type P1-01 *E1_RS232_DCM M01-01 RS232_DCM P1-02 E1_SIG --- P1-03 E1_SIG --- P1-04 E1_SIG --- P1-05 *E1_V35_DCM M05-01 V35_DCM P1-06 *E1_V35_DCM M05-01 V35_DCM P1-07 *E1_V35_DCM M05-01 V35_DCM P1-08 *E1_V35_DCM M05-01 V35_DCM P1-09 E1_SIG --- P1-10 E1_SIG --- P1-11 E1_SIG --- P1-12 E1_SIG --- Asterisks indicate current connections CONFIG CONNECT P1-1 1-SHOW_CCT 2-DISCONNECT 3-TO_CIRCUIT 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- 23.5 Protecting connections (RAPID protection switching) The 2902 MainStreet NTU provides RAPID circuit protection. You can protect a connection by specifying an alternate connection in case of a circuit or link failure. The original connection is called the preferred connection and the alternate connection is the protecting connection. 2902 MainStreet Technical Practices 23-5 May 2002 90-2906-01 23 — Cross-connecting circuits The preferred connection is made up of a protected circuit and its preferred circuit. The protecting connection is made up of the protected circuit and its protecting circuit. The process of automatically switching from the preferred to the protected connection is called protection switching. In Figure 23-3, the preferred connection is 1-1 to P1-1; the protecting connection is 1-1 to P2-1. Circuit 1-1 is the protected circuit, P1-1 is the preferred circuit and P2-1 is the protecting circuit. If the preferred connection fails (due to a problem with preferred circuit P1-1 or the link it connects to), the node switches to protecting circuit P2-1 and the connection is maintained by the protecting connection. Caution — When a switch to a protecting connection occurs, there is a short service disruption. Figure 23-3 Example of a protecting connection 2902 MainStreet node Protected Preferred Data Control Primary circuit circuit module card rate module Data 1-1 DX device Primary P1-1 rate link Protecting connection Preferred connection Primary rate module Primary P2-1 rate link Protecting circuit 8871 In general, any two circuit types that can be used to form a preferred connection may also be used to form a protecting connection. Exceptions are discussed later in this section. Protection switching and fault signaling For protection switching that involves tandem nodes in an E1 environment, the fault signaling for each inter-node circuit must be set to out-of-service type A or B (OOS-A or OOS-B). This causes the failure of an inter-node link to be detected by other nodes and triggers a switch to alternate connections. For more details on fault signaling, see section 16.2. 23-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits Figure 23-4 shows an example of protection switching that involves tandem nodes. Each node #1 circuit on link E1(1) is protected by a circuit on link E1(3). Each node #3 circuit on link E1(2) is protected by a circuit on link E1(4). If link E1(1) fails: 1 An alarm is raised at node #1 and protection switching occurs; that is, the protected circuits are connected to their protecting circuits on link E1(3). 2 The fault signaling configured at node #2 is carried to node #3 on link E1(2). By configuring the circuits on link E1(1) for out-of-service signaling at node #2, node #3 is informed that link E1(1) is down. 3 Node #3 switches the protected circuits on link E1(2) to their protecting circuits on link E1(4). If the circuits on link E1(1) are configured for seized or idle fault signaling at node #2 (instead of OOS-A or OOS-B fault signaling), node #3 is not informed that link E1(1) is down. In this case, node #3 does not switch the circuits on link E1(2) to their protecting circuits on link E1(4). Figure 23-4 Out-of-service signaling for tandem nodes 2902 MainStreet Out-of-service node #2 fault signaling E1(1) E1(2) 2902 MainStreet 2902 MainStreet Data Data node #1 node #3 device E1(3) E1(4) device Fault 2902 MainStreet node #4 Protecting connection Active (and preferred) connection 8874 Pointers for protecting circuits It is possible to share a protecting circuit, using it for one connection while it waits to switch to its protecting mode. If a protection switch occurs, the original connection is automatically overridden by the protecting connection. There are several situations when protecting circuits should be used with caution, including: • automatic override • incompatible far-end devices • circuits on the same link 2902 MainStreet Technical Practices 23-7 May 2002 90-2906-01 23 — Cross-connecting circuits Automatic override Figure 23-5 shows an example where circuit 1-1 is connected to circuit P1-1 and is protected by circuit P2-1. Circuit 2-1 is connected to circuit P2-1. When all circuits are available, the connection between circuits 1-1 and P1-1 is active, as is the connection between circuits 2-1 and P2-1. If circuit P1-1 fails or becomes unavailable, circuit 1-1 switches to P2-1 and the connection between circuits 2-1 and P2-1 is overridden (see Figure 23-6). Circuit 1-1 switches back to its preferred connection when circuit P1-1 becomes available. Caution — A connection that shares a protecting circuit may be broken without warning at any time, because the protecting circuit must connect to the circuit it has been configured to protect. Figure 23-5 Preferred connections available 2902 MainStreet node Protected Preferred Data Control Primary circuit circuit module card rate module DX 1-1 Data device Primary P1-1 rate link Protecting connection Preferred connection Data Primary module rate module 2-1 P2-1 Primary rate link Not protected Protecting circuit inactive 8872 23-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits Figure 23-6 Protecting connection made 2902 MainStreet node Protected Preferred Data Control Primary circuit circuit module card rate module DX 1-1 Data device P1-1 Primary rate link Protecting connection Preferred connection Data Primary module rate module 2-1 P2-1 Primary rate link Not protected Protecting circuit inactive 8873 Incompatible devices When sharing a protecting circuit, avoid connections that connect incompatible device types. For example, do not use P2-1 to protect a DNIC circuit when its preferred connection is a V.35 DCM circuit to another V.35 DCM circuit at the far end. If link P1 goes out of service, the DNIC circuit would connect to a V.35 circuit. Same links The preferred and protecting circuits must not be on the same module. If the preferred circuit becomes unavailable for connection due to a link failure, the protecting circuit also becomes unavailable. For example, in Figure 23-5, do not try to connect circuit 1-1 to circuit P1-1 and protect it by circuit P1-2. Note — Although the examples and illustrations in this section use primary rate preferred and protecting circuits, it is also possible to protect a connection using an interface module circuit. Procedure 23-4 To make a protecting connection 1 Make the preferred connection according to the simple cross-connection instructions provided in section 23.2. 2902 MainStreet Technical Practices 23-9 May 2002 90-2906-01 23 — Cross-connecting circuits 2 Make the protecting connection. CONFIG — CONNECT — or ↵ PROT_BY PROTECTING ↵ ↵ SK000525 where pp is the interface module for the protected circuit, either 1 or 9 p is the primary rate module for the protecting circuit, 1 or 2 c is the circuit number, 1 to 31 (for primary rate), or 1, 2, A or B (for interface module) A protecting connection can be made from the perspective of the protected circuit (PROT_BY) or the protecting circuit (PROTECTING). For example, if P2-1 is the protecting circuit for circuit 1-1, you can configure the protection connection by entering: CONFIG — CONNECT <1-1> ↵ — PROT_BY — ↵ or CONFIG — CONNECT ↵ — PROTECTING — <1-1> ↵ 23.6 Disconnecting connections To disconnect a connection, specify one of the circuits. If the connection is protected, the softkeys PREFERRED and PROTECTION appear. The preferred and protected connections are disconnected independently. You can make disconnections one at a time or all at once. Note 1 — The DISCONNECT softkey appears only when the specified circuit is cross-connected to another circuit or CPSS. Selecting DISCONNECT breaks the existing connection without defining another one. Note 2 — Selecting CONFIG — CONNECT — DISCONN_ALL disconnects all interface circuits or cross-connect circuits, including super-rate connections; however, it does not disconnect bypass or CPSS connections. 23-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 23 — Cross-connecting circuits Procedure 23-5 To disconnect a simple circuit CONFIG — CONNECT — or ↵ — DISCONNECT PREFERRED PROTECTION SK000526 where pp is 1 or 9, c is 1, 2, A or B p is 1 or 2, c is 1 to 31 Procedure 23-6 To disconnect all circuits CONFIG — CONNECT — DISCONN_ALL Procedure 23-7 To disconnect a super-rate circuit A super-rate circuit is disconnected by using its data module circuit identifier or its master circuit number. If the primary rate circuit is not the master circuit, the message “Circuit is in the middle of a super-rate group” appears. CONFIG — CONNECT — or ↵ — DISCONNECT where pp is 1 or 9, c is 1 (for X.21 and V.35 DCMs), or A (for DNIC or 2B1Q modules) p is 1 or 2, c is 1 to 30 2902 MainStreet Technical Practices 23-11 May 2002 90-2906-01 23 — Cross-connecting circuits 23-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 24 — Visual indicators 24.1 LEDs 24-2 24.2 Front panel LEDs 24-2 24.3 Rear panel LEDs 24-4 24.4 Interface module LEDs 24-6 2902 MainStreet Technical Practices 24-1 May 2002 90-2906-01 24 — Visual indicators 24.1 LEDs LEDs are located on the front panel, the rear panel (mounted on the Control card), and the interface modules. Table 24-1 lists the colors of the LEDs. Table 24-1 LED colors LED location LED name Color Front panel Power Green Processor Green Event Status Yellow System Status Red Out of Sync 1 Red Out of Sync 2 Red Rear panel (mounted on the Control Card Status Red card) (1) Loopback (four) Red V.35 and X.21 DCM Module Status Green or yellow Circuit Status Green RS-232 and Codirectional DCM Module Status Green or yellow Circuit Status (two) Green or red DNIC module Module Status Yellow Line Status Red 2B1Q module Module Status Green Synchronization Status Yellow Note (1) Only LEDs labeled 1 and 2 are used. The other two loopback LEDs are not used. 24.2 Front panel LEDs The six LEDs on the chassis front panel are: Power, Processor, Event Status, System Status, Out of Sync 1 and Out of Sync 2, as shown in Figure 24-1. Table 24-2 describes their normal operation and gives troubleshooting advice. 24-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 24 — Visual indicators Figure 24-1 Front panel LEDs Power Processor Event Status Out of Sync 1 System Status Out of Sync 2 Power Processor 2902 MainStreet Event Status Out of Sync 1 Network Termination Unit System Status Out of Sync 2 8831 2902 MainStreet Technical Practices 24-3 May 2002 90-2906-01 24 — Visual indicators Table 24-2 Front panel LED operation LED Normal operation Troubleshooting Power Lit continuously If the Power LED is not lit continuously: • verify that the power switch is on • verify that the power cable is correctly attached to the system and to an unswitched power source • verify that the cable running from the power supply to the Control card is (1) securely attached • check the fuse to see if it is blown (follow the instructions given in section 31.2) • check the power rails (see section 31.1) Processor Flashes If the Processor LED stops flashing, check the alarm queues (as described in (0.5 s on, 0.5 s off) section 25.2). (2) Event Status Not lit If the Event Status LED is lit, there is an unacknowledged entry in the Major alarm queue. Check the queue for the alarm. See chapter 25 for more information on alarms. (2) System Status Not lit If the System Status LED is lit, there may be a problem with one or more of the following: • LIM • E1 interface • a module position configured as empty has a module • a circuit is out of synchronization with its associated DTU • trunk conditioning is being applied due to a E1 link failure When a problem occurs, the System Status LED is updated every 10 seconds. Out of Sync 1 Not lit If the Out of Sync 1 LED or the Out of Sync 2 LED is lit, communication with Out of Sync 2 the E1 network has been lost. • Check the E1 line. • Ensure that the E1 lines are properly connected to the Control card connectors. • Check that the LIMs are seated properly on the Control card. • Verify that the far end is transmitting. • Perform a loopback on primary rate module P1 or P2 to isolate the unit from the network. For more information on loopbacks, see section 27.6. The Out of Sync 1 LED or the Out of Sync 2 LED is also lit if the module position is configured as EMPTY and no module is installed. Notes (1) This requires opening the unit. See section 5.2 in Installation. (2) You can connect external alarm equipment, such as a light or buzzer, which will activate when the Event Status LED or the System Status LED lights. See section 25.7 for more information on external alarm equipment. 24.3 Rear panel LEDs The rear panel indicators are mounted on the Control card. The six indicators are: • Control card status LED • seven-segment display • four loopback LEDs 24-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 24 — Visual indicators The Control card indicators are shown in Figure 24-2. Table 24-3 describes their normal operation and gives troubleshooting advice. Figure 24-2 Control card indicators (rear panel) Loop Status U 1 2 Display I EDG Sig/Gnd O Slot 2 P1 P2 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Loop Status U 1 2 Display 8832 Table 24-3 Rear panel LED operation LED Normal operation Troubleshooting Status Lit continuously If the Control card Status LED is not lit or is flashing, there is a problem with the Control card. Contact your service representative for help. Seven-segment Flashes a number The decimal point acts as the Control card power display and has a constantly indicator. lit decimal point (1) A flashing number indicates the number of alarms in the Major alarm queue. If there are no flashing numbers and the decimal point is not lit: • ensure that the power switch is on • verify that the power cord is firmly plugged in at both ends • ensure that there is power at the outlet • turn the power switch off and on Call your technical support representative for help if, after performing the above actions: • there are still no flashing numbers and the decimal point still does not light • there are flashing numbers but the decimal point does not light • there are no flashing numbers but the decimal point is lit Loopback Not lit The LEDs labeled 1 and 2 indicate the status of loopbacks used to test the end-to-end connections over the primary rate lines: LED 1 is for module P1 and LED 2 is for module P2. LED 1 and LED 2 light when the entire link is looped back. The other two loopback LEDs are not used. For more information on loopbacks, see chapter 27. Note (1) For nine or fewer alarms, the display shows the number for 0.5 second, then goes blank for 0.5 second. For 10 or more alarms, the display shows the first and second digits for 0.25 second each, then goes blank for 0.5 second. 2902 MainStreet Technical Practices 24-5 May 2002 90-2906-01 24 — Visual indicators 24.4 Interface module LEDs The RS-232 and Codirectional DCMs have three LEDs, as shown in Figure 24-3. The X.21 and V.35 DCMs, and the DNIC and 2B1Q modules have two LEDs, as shown in Figure 24-4. Table 24-4 describes their operation. Figure 24-3 LEDs on the RS-232 DCM Circuit 2 status Circuit 1 Module status status 2830 Figure 24-4 LEDs on the X.21 DCM Circuit status Module status 5906 24-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 24 — Visual indicators Table 24-4 Interface module LED operation LED Operation RS-232 and Codirectional modules Module status In normal operation, the LED is lit continuously. If the LED is not lit, the installed module does not match the module position configuration. Reconfigure the module position to match the type of module installed. If the LED still does not light, make a note of the module type and the interface identification number (see section 26.7) and contact your technical support representative. If there is a problem, the LED flashes. Circuit 1 status For RS-232 DCMs: Circuit 2 status If the circuit is configured for HCM rate adaption, the LED is lit continuously when the circuit achieves HCM synchronization. If the circuit is configured for transparent rate adaption, the LED is lit continuously when the circuit is configured and connected. For Codirectional DCMs: The LED is not lit if there is no input signal. It is lit continuously when an input signal is present. DNIC module Module status In normal operation, the LED is lit continuously. If the LED is not lit, the installed module does not match the module position configuration. Reconfigure the module position to match the type of module installed. If the LED still does not light, make a note of the module type and the interface identification number (see section 26.7) and contact your technical support representative. If the LED is flashing, the module is defective. Replace the module. Line status The line status LED monitors the line that runs from the module to the 2600 MainStreet series DTUs. The LED is not lit if the module is not configured. If the LED is lit, the DNIC module is configured and synchronized with the DTU. If it is not lit, synchronization has been lost. 2B1Q module Module status In normal operation, the LED is lit continuously. If the LED is not lit, the installed module does not match the module position configuration. Reconfigure the module position to match the type of module installed. If the LED still does not light, make a note of the module type and the interface identification number (see section 26.7) and contact your technical support representative. If the LED is flashing, the module is defective. Replace the module. Synchronization The LED is lit when the 2B1Q module is synchronized to the DSL. If it is not lit, the module is not status synchronized. X.21 and V.35 modules Module status In normal operation, the LED is lit continuously. If the LED is not lit, the installed module does not match the module position configuration. Reconfigure the module position to match the type of module installed. If the LED still does not light, make a note of the module type and the interface identification number (see section 26.7) and contact your technical support representative. If the LED is flashing, a fault condition has been detected. Circuit status If the circuit is configured for transparent rate adaption, the LED is continuously lit. If the circuit is configured for HCM rate adaption, the LED is lit when HCM synchronization is achieved. 2902 MainStreet Technical Practices 24-7 May 2002 90-2906-01 24 — Visual indicators 24-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms 25.1 Alarms and alarm queues 25-2 25.2 Viewing alarm queues 25-4 25.3 Acknowledging alarms 25-6 25.4 Deleting alarms 25-7 25.5 Reclassifying configurable alarms 25-7 25.6 Logging alarms 25-9 25.7 External alarms 25-10 2902 MainStreet Technical Practices 25-1 May 2002 90-2906-01 25 — Alarms 25.1 Alarms and alarm queues The 2902 MainStreet system continuously monitors itself for abnormal conditions or significant events. When an abnormal condition is detected or a significant event occurs, an alarm is recorded in one of the three alarm queues: • Major/Prompt (event alarms) • Minor/Deferred • Diagnostic/In Station Each alarm queue can hold up to 64 alarms. For some alarms, you can configure in which queue the alarm is recorded. When an alarm is recorded in the Major/Prompt queue, the Event Status LED on the front panel lights. The LED remains lit until the alarm is acknowledged. See section 24.2 for more information about the Event Status LED. The 2902 MainStreet system has an external alarm function that allows you to monitor or activate an external device (see section 25.7). Note 1 — Maintenance on the module in physical position M2 is accessed through NMTI module position 9. Note 2 — Maintenance information on module position 9 is not available when position 9 is disabled by position 1 (during a super-rate connection). See section 19.11 in Configuration for details. Alarm codes and clearing codes Each alarm in an alarm queue includes information such as date and time of the alarm, as well as an alarm code. The alarm code is a brief description of the nature of the alarm. Some alarms codes have corresponding clearing codes, which inform you that the alarm condition no longer exists. Clearing codes are added to the appropriate alarm queue. Clearing codes have names that are similar to their corresponding alarm codes but include terms such as cleared, removed, restored and normal. For example, the alarm code “AIS - All Ones” has the clearing code “AIS - All Ones Cleared”, while the alarm code “Busy Out Applied” has the clearing code “Busy Out Removed”. Table 25-1 lists and describes the alarm codes. Alarm codes marked with an asterisk (*) have a corresponding clearing code. Some alarm codes have subcodes and parameters that are used by Alcatel field service representatives. Subcodes and parameters that are useful to maintenance functions are given in the table. 25-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms Table 25-1 Detailed alarm descriptions Alarm code Description of alarm AIS - 8K* 8 kHz timing has been received by the Codirectional DCM. AIS - All Ones* An all ones pattern has been received by the Codirectional DCM. Board Self Test Failed This alarm is used only during the production and factory testing of the 2902 MainStreet unit. Busy Out Applied* A 5620 NM has forced the link specified in the first parameter to be busied out. Card Activity Change A primary rate link has been switched from a preferred link to a protecting link. CPU Self Test Failed The CPU self-test described in Table 4-3 has failed. Device Failed The background or directed diagnostics have detected a failed module. Locate and replace the module. Distant/Yellow Alarms* The far end has lost frame alignment on a primary rate link. Check the first parameter of the subcode to identify the primary rate link. DX Self Test Failed The Control DX memory self-test described in Table 4-3 has failed. E1 Framer Self Test Failed One of the E1 Framer loopback self-tests described in Table 4-3 has failed. External Alarm Raised* If the external alarm is enabled as an open circuit, this alarm means the circuit has opened. If the external alarm is enabled as a closed circuit, this alarm means the circuit has closed. Failed State* A primary rate link has experienced 10 consecutive severely errored seconds and may have been taken out of service as a result. The first parameter identifies the failed link. Framing Err Rate Exceeded* The E1 link error threshold was exceeded. Framing/AIS/Red Alarms* Frame alignment has been lost on an E1 link. Check the first parameter of the subcode to identify the module, then check the cable connections to the module and the E1 link. HDLC Self Test Failed One of the HDLC presence or HDLC loopback self-tests described in Table 4-3 has failed. Interrupt Self Test Failed The SMAC interrupt self-test described in Table 4-3 has failed. LIM position 1 failed The Loopback (LIM 1) self-test described in Table 4-3 has failed. LIM position 2 failed The Loopback (LIM 2) self-test described in Table 4-3 has failed. LIS Alarm* Loss of input signal on a Codirectional DCM circuit. Module Dead A module has been marked as dead. (1) Module Failure A module is either not responding to the system or it failed the startup diagnostics on common circuitry. Check the first parameter to identify the module. Module Inserted A module was inserted. The first parameter identifies the module. Module Removed A module was removed. The first parameter identifies the module. Module Reset A module on the Control card has been reset. Multiframe Alarm / Incoming The E1 multiframe alignment has been lost. TS16 AIS* (1) NVM Error The Control card has a problem in the non-volatile RAM. Record the alarm subcode and parameters, then run directed test #3 (see section 26.3). After the test, record any information displayed when you enter MAINT — NVM_DATA. Power Rail Failed* One of the power rails does not have power. RAM Self Test Failed The Address Bus self-test described in Table 4-3 has failed. (1 of 2) 2902 MainStreet Technical Practices 25-3 May 2002 90-2906-01 25 — Alarms Alarm code Description of alarm Revision/Feature Mismatch The Control card and software versions are mismatched, or a necessary Control card module is missing. Check the second parameter in the subcode to identify the details of the mismatch as follows: 0 - unknown reason 1 - the card and software are incompatible ROM Self Test Failed The EPROM checksum self-test described in Table 4-3 has failed. SEEP Self Test Failed The SEEP self-test described in Table 4-3 has failed. Signaling Fault An over-active device has caused a signaling fault. Synch Source Changed The timing source has changed. Synch Source Failure The timing source has been lost. Synch Src Recovery Failed The system attempted to recover a lost timing source but did not succeed. System Advisory (DA) This is a diagnostic software alarm related to Device Administration. If you are reporting any problems to your representative, make sure you include this alarm as it can help to identify a failure mechanism. System Advisory (SA) This is a diagnostic software alarm related to System Administration. If you are reporting any problems to your representative, make sure you include this alarm as it can help to identify a failure mechanism. Tail Circuit Gone* The connection between a DNIC or 2B1Q module and a DTU or DSU has been lost. The first parameter identifies the module. This alarm is not raised if the module is removed from its position. Locate the trouble and reconnect or replace the equipment as necessary. Temperature Self Test Failed The Thermometer self-test described in Table 4-3 has failed. Timer Self Test Failed The 4 ms timer or 125 µs timer self-test described in Table 4-3 has failed. Too Many Alarms An alarm queue has overflowed. Delete some or all alarms. TS16 Distant Alarm* This is an E1 alarm that indicates that there has been a timeslot 16 multiframe alarm at the far end. UART Self Test Failed One of the UART presence or UART send/receive self-tests described in Table 4-3 has failed. Wrong Interface Card The installed interface card and the configuration do not correspond. Wrong Module in Position A module position is configured for a module type other than the type installed. Check the first parameter to determine the position number. Either reconfigure the position to match the module type installed or install the type of module for which the position is configured. (2) Wrong/No Module Installed The installed module and the configuration do not correspond or no module has been installed. (2 of 2) Notes (1) An abnormal operating condition has occurred which may or may not affect system operation. To verify that system operation is not negatively affected, advise the nearest field support office of the circumstances leading to this alarm and the details displayed with it. (2) This alarm is not generated for module position 9 when position 9 is reserved for a super-rate connection by position 1. 25.2 Viewing alarm queues Alarm queues are displayed with the most recent alarm at the top of the list. If there are too many alarms in the list for the data area to show them all, you can scroll through the list to view earlier or later alarms. 25-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms Each queue holds up to 64 alarms. If the number of alarms in the queue exceeds 64, a Too Many Alarms alarm occurs and additional alarms are not recorded in the queue until some or all of the alarms are deleted. The number of alarms in the queue is indicated in the header line. Figure 25-1 is an example showing four alarms in the Major/Prompt alarm queue. The column headings for the alarms are described in Table 25-2. Figure 25-1 Alarm queue display example 2902 MainStreet 82211-ab-cd Alarms:4 No Date 4:21R # Date Time Stat Id Code SubCode Parameters 4 No Date 0:17R U 4 Module Inserted M01 1,0,0 3 No Date 0:00R U 3 Framing Alarm P1 2 No Date 0:00R U 2 Module Inserted P1 11,0,0 1 No Date 0:00R U 1 Synch Source Changed 5,14,0 ALARMS MAJ/PROMPT 1-ACK_All 2- 3-DELETE_ALL 4-DELETE 5-ACK 6- 7- 8- CANCEL 9-QUIT 0- Table 25-2 Description of an alarm in an alarm queue Column heading Description # The queue number. The item at the top of the list is the most recent alarm in the queue. Use the alarm queue number when acknowledging or deleting an alarm. Numbers are updated each time an alarm is added or deleted. Date The date on which the alarm occurred. If “No Date” appears in the Date column, it indicates that the system has been reset and that the date has not yet been set (see section 11.2 in Configuration). Time The time that the alarm occurred: A for a.m., P for p.m., and R for hours since the last system reset. Stat The status of the alarm: U (unacknowledged) or A (acknowledged). Id The unique identification number for each alarm code. Unlike the queue #, the ID number does not change. (1 of 2) 2902 MainStreet Technical Practices 25-5 May 2002 90-2906-01 25 — Alarms Column heading Description Code A brief description of the abnormal condition or significant event. A complete list of alarm codes and detailed descriptions are included in Table 25-1. Each alarm code has a unique ID number. Subcode and The alarm subcode and parameters, if any. Subcodes and parameters are used Parameters by Alcatel field service personnel only. However, some subcodes and parameters are relevant to maintenance operations, as detailed in Table 25-1. (2 of 2) Procedure 25-1 To view an alarm queue ALARMS MAJ/PROMPT MINR/DEFER DIAG/INSTN EARLIER LATER SK000527 Circular alarm queue Queues hold up to 64 alarms. When the last alarm is posted to a queue, the queue can be configured to either stop recording alarms (FIXED) or start overwriting alarms, oldest alarm first (CIRCULAR). Procedure 25-2 To set the alarm queue options ALARMS — CONFIG — QUEUE MAJ/PROMPT MINOR/DEF DIAG/INSTN FIXED CIRCULAR SK000666 25.3 Acknowledging alarms Alarms can be acknowledged without clearing or deleting them from their respective queues. When an alarm is acknowledged, the letter in the Status column changes from U (unacknowledged) to A (acknowledged), and the alarm remains in the queue. You can acknowledge a specific alarm or all alarms in a queue. 25-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms Procedure 25-3 To acknowledge alarms ALARMS MAJ/PROMPT MINR/DEFER DIAG/INSTN ACK ACK_ALL ↵ SK000528 where alarm number is the number (in the # column) of the alarm you want to acknowledge 25.4 Deleting alarms You can delete a specific alarm or all the alarms in a queue. Alarm queue numbers are updated when an alarm is deleted. Procedure 25-4 To delete alarms ALARMS MAJ/PROMPT MINR/DEFER DIAG/INSTN DELETE DELETE_ALL ↵ SK000529 where alarm number is the number (in the # column) of the alarm you wish to delete 25.5 Reclassifying configurable alarms Configurable alarms allow you to determine which queue the alarm is recorded in. In the default configuration, all configurable alarms are classified as Major/Prompt. You may want to configure alarms that need attention but are not an immediate threat to service as Minor/Deferred, or alarms that are advisory as Diagnostic/In Station. 2902 MainStreet Technical Practices 25-7 May 2002 90-2906-01 25 — Alarms Figure 25-2 shows a display of alarm codes for configurable alarms and their current classification (listed under Priority). Use the numbers in the # column to identify the alarm code that you wish to reclassify. Press before selecting CANCEL, QUIT, PAGE_UP or PAGE_DOWN. Figure 25-2 Reclassifying a configurable alarm 2902 MainStreet 82211-ab-cd Alarms:4 No Date 4:29R # Code Priority # Code Priority ------------------------------------- --------------------------------------- 1 System Advisory MAJ/PROMPT 15 Module Failure MAJ/PROMPT 2 Wrong Module In Position MAJ/PROMPT 16 Module Removed MAJ/PROMPT 3 NVM Error MAJ/PROMPT 17 Tail Circuit Gone MAJ/PROMPT 4 Framing/AIS/Red Alarms MAJ/PROMPT 18 Power Rail Failed MAJ/PROMPT 5 Distant/Yellow Alarms MAJ/PROMPT 19 Failed State MAJ/PROMPT 6 External Alarm Raised MAJ/PROMPT 20 Card Activity Change MAJ/PROMPT 7 Synch Source Failure MAJ/PROMPT 21 Busy Out Applied MAJ/PROMPT 8 Wrong/No Module Installed MAJ/PROMPT 22 Signaling Fault MAJ/PROMPT 9 Wrong Interface Card MAJ/PROMPT 23 Module Reset MAJ/PROMPT 10 Device Failed MAJ/PROMPT 24 Module Dead MAJ/PROMPT 11 Framing Err Rate Exceeded MAJ/PROMPT 25 RAM Self Test Failed MAJ/PROMPT 12 Synch Source Changed MAJ/PROMPT 26 ROM Self Test Failed MAJ/PROMPT 13 Synch Src Recovery Failed MAJ/PROMPT 27 HDLC Self Test Failed MAJ/PROMPT 14 Revision/Feature Mismatch MAJ/PROMPT 28 DX Self Test Failed MAJ/PROMPT ALARMS CONFIG “?” Enter the alarm number. 1- 2-PAGE_UP 3- 4- 5- 6- 7- 8- CANCEL 9-QUIT 0- Note — An alarm code cannot be reclassified if it has any entries in an alarm queue. Procedure 25-5 To reclassify an alarm ALARMS — CONFIG — ↵ MAJ/PROMPT MINR/DEFER DIAG/INSTN SK000530 where alarm number is the number (in the # column) of the alarm code you wish to reclassify 25-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms 25.6 Logging alarms The 2902 MainStreet system offers three options for logging alarms: • remotely via CPSS (RMT_ON) • remotely via modem (MDM_ON) • locally to a device such as a printer (LCL_ON) All three options are disabled by default and can be enabled concurrently. When two or more options are enabled concurrently, logging priority is as follows: CPSS, then modem, then local printer. Remote logging via CPSS logs alarms to the NOC over the network using CPSS messages. Remote logging via modem logs alarms to the NOC over the PSTN and can serve as a backup method if the network CPSS link to the NOC fails. This option is available only if one of the two serial ports (typically serial port 1) has been configured to accept a modem (see section 11.1). Local logging logs alarms to a local device such as a printer. The serial port must be configured to accept a printer (see section 11.1). Procedure 25-6 To log alarms via CPSS 1 Establish CPSS communications over the network. 2 Enter: ALARMS — MORE — LOGGING RMT_ON/RMT_OFF* SK000531 * Default Procedure 25-7 To log alarms via a modem 1 Configure the 2902 MainStreet system serial port type for CPSS_MODEM and establish modem connections between the 2902 MainStreet system and the NOC. 2 Enter: ALARMS — MORE — LOGGING MDM_ON/MDM_OFF* SK000532 * Default 2902 MainStreet Technical Practices 25-9 May 2002 90-2906-01 25 — Alarms Procedure 25-8 To log alarms locally 1 Connect a printer to a serial port and configure the serial port type for PRINTER. 2 Enter: ALARMS — MORE — LOGGING LCL_ON/LCL_OFF* SK000533 * Default 25.7 External alarms The external alarm function allows you to monitor or activate external alarm devices. It is disabled by default. When the function is enabled and a monitored device signals an external alarm, an External Alarm Raised alarm is added to an alarm queue. The function can be disabled while External Alarm Raised alarms are listed in an alarm queue. Connections are made through the Alarm connector (RJ11-type). See chapter 9 in Installation for information on connecting external alarm devices. Monitoring a device To detect an external alarm, the 2902 MainStreet system monitors its Alarm In pins for a change of state. You can configure the external alarm function to assume the Alarm In contacts are normally open or closed. The default setting is normally closed. Activating a device If there is an unacknowledged alarm in the major alarm queue, the Event Status LED lights. If an alarm device is properly connected to the external alarm connector and the external alarm function is enabled, the device is activated. If a system problem exists, the System Status LED lights. If an alarm device is properly connected to the external alarm connector and the external alarm function is enabled, the device is activated. See section 24.2 for information on system problems. 25-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 25 — Alarms Procedure 25-9 To set the external alarm function ALARMS — EXTNL_ALRM ENABLE/DISABLE* OPEN_CCT/CLOSED_CCT* SK000534 * Default 2902 MainStreet Technical Practices 25-11 May 2002 90-2906-01 25 — Alarms 25-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics 26.1 Diagnostic tests 26-2 26.2 Background diagnostics 26-3 26.3 Directed diagnostics 26-4 26.4 Viewing diagnostics 26-5 26.5 Busy-out circuits 26-6 26.6 Signaling leads 26-7 26.7 Displaying module and Control card maintenance information 26-10 26.8 Resetting a module or the Control card 26-10 2902 MainStreet Technical Practices 26-1 May 2002 90-2906-01 26 — System diagnostics 26.1 Diagnostic tests The 2902 MainStreet system can perform a number of diagnostic tests on the whole system and on specific circuits. The tests can be run automatically or when directed. If a test is unsuccessful, or if the time taken to complete a test exceeds the preset limit, a Device Failed alarm is recorded. By accessing the fault list (see section 26.4), you can determine which circuit has failed a diagnostic test. Diagnostics do not run on modules which do not support them. Diagnostics do not busy out a circuit or remove it from service. If a circuit is required for a call while a test is in progress, the test on that circuit is aborted. Similarly, diagnostics skip over circuits that are engaged. Table 26-1 lists the diagnostic tests. You can run all the tests in the background (see section 26.2) or you can select a particular test (see section 26.3). Table 26-1 Diagnostic tests Test number Function Description 1 Program Integrity A checksum is performed over the processor program space. 2 RAM Integrity A cyclical byte-wide read/write test is performed over the entire range of RAM. 3 NV RAM Integrity A checksum is performed over the entire NVM. 4 Digital Loopback A digital loopback is performed on the data link between an Test idle module and the Control card. Diagnostic test restrictions In order to run diagnostics or a particular test: • diagnostics must be enabled for the circuit • the module(s) must be installed • the test must be supported by the module Test 4 cannot be run for the following types of circuits when they are connected: • cept_lgs_cbw_Type • cept_bypassSig_Type • cept_bypassNoSig_Type 26-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics While test 4 is applied to a Codirectional DCM circuit, 8 kHz timing is turned on and all ones is turned off. Even if the Codirectional DCM circuit has been configured not to generate 8 kHz timing (see section 20.5 in Configuration), it does generate 8 kHz timing during the test. Even if the Codirectional DCM circuit has been configured to generate all ones (see section 20.6 in Configuration), it does not generate all ones during the test. Note 1 — Maintenance on the module in physical position 2 is accessed through NMTI logical module position M9. Note 2 — Maintenance information on logical module position M9 is not available when position M9 is disabled by logical position M1 (during a super-rate connection). See section 19.11 in Configuration for details. Selecting MAINT — UNDO_MAINT does not disable background diagnostics, halt directed diagnostics, affect the state of the signaling leads (SET_SIGNAL) or remove a primary rate link loopback. 26.2 Background diagnostics System and circuit background diagnostics can be performed by the 2902 MainStreet system. System background diagnostics When system background diagnostics are enabled, the system tracks any fault that occurs. The system cycles continuously through the four diagnostics tests (as listed in Table 26-1). If testing is disabled and re-enabled, it resumes where it stopped. System background diagnostics are disabled by default and can be restarted from test 1. Circuit background diagnostics Circuit background diagnostics can be enabled or disabled for individual circuits. Background diagnostics for individual circuits are disabled by default. Procedure 26-1 To set system background diagnostics MAINT — DIAG ENABLE/DISABLE* RESTART SK000535 * Default The RESTART softkey only appears when background diagnostics are enabled. 2902 MainStreet Technical Practices 26-3 May 2002 90-2906-01 26 — System diagnostics Procedure 26-2 To set background diagnostics on a specific circuit CONFIG — CIRCUIT — or ↵ — MORE ENAB_DIAG/DISAB_DIAG* SK000536 where pp is 1 or 9, and c is 1, 2, A or B p is 1 or 2, and c is 1 to 31 * Default 26.3 Directed diagnostics Directed diagnostics run a specific test on a specific circuit. After the test has run, the system resumes background diagnostics, if enabled. Directed diagnostics do not run on circuits that have had diagnostics disabled. You can select a diagnostic test to run: • once (X1) • 10 times (X10) • 100 times (X100) • continuously (or locked) (LOCK) Directed diagnostics are supported for primary rate and interface module circuits. If the specified circuit is busy, the display shows the message “Device momentarily unavailable for testing” until the circuit is ready to be tested, at which time the directed test is carried out. Procedure 26-3 To set directed diagnostics on a circuit CONFIG — CIRCUIT — or ↵ — MORE ENAB_DIAG/DISAB_DIAG* SK000536 where pp is 1 or 9, and c is 1, 2, A or B p is 1 or 2, and c is 1 to 31 * Default 26-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics Procedure 26-4 To run directed diagnostics MAINT — DIAG — DIRECTED — ↵ X1 X10 X100 LOCK SK000537 where test number is 1, 2, 3 or 4 Note — If the diagnostic test is number 4, you must enter a circuit number (either or ) after the ↵. Procedure 26-5 To stop directed diagnostics MAINT — DIAG — DIRECTED — HALT 26.4 Viewing diagnostics You can view: • the diagnostic test currently being run (SHOW_CUR) • a list of all the supported diagnostic tests (SHOW_LIST) • the status of a circuit already tested, that is, whether it passed or failed the test (FAULT_LIST) Figure 26-1 shows a sample display where diagnostics have been enabled. 2902 MainStreet Technical Practices 26-5 May 2002 90-2906-01 26 — System diagnostics Figure 26-1 Diagnostics display 2902 MainStreet 82211-ab-cd Alarms:3 No Date 0:15R Diagnostic Test Number : 2 Test No. Function 1 Program Integrity 2 Ram Integrity 3 N.V. Ram Integrity 4 Digital Loopback Test MAINT DIAG 1-SHOW_CUR 2- SHOW_LIST 3-DISABLE 4-RESTART 5-DIRECTED 6-FAULT_LIST 7- 8-CANCEL 9-QUIT 0- Procedure 26-6 To view diagnostic tests MAINT — DIAG SHOW_CUR SHOW_LIST FAULT_LIST or ↵ SK000538 where p is 1 or 2 pp is 1 or 9 26.5 Busy-out circuits The busy-out feature is used to temporarily place a circuit out of service. When the circuit is out of service, you can perform maintenance functions such as loopbacks. A circuit that is busied out is blocked from attempts by others to place it back in service or change any part of its configuration. 26-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics A circuit remains in the busy-out state until it is changed by the operator to the unbusy state or the system is restarted. Procedure 26-7 To busy-out a circuit MAINT — ON_CIRCUIT — or ↵ BUSY_OUT/UNBUSY* SK000539 where p is 1 or 2, c is 1 to 31 pp is 1 or 9, c is 1, 2, A or B * Default 26.6 Signaling leads Digital circuits provide signaling information through signaling bits in the data stream. Incoming signaling information indicates what is happening at the remote end; outgoing signaling information transmits what is happening at the local end. The 2902 MainStreet system allows you to examine incoming and outgoing signaling leads. This troubleshooting tool provides a view of the far-end conditions with which to determine, for example, whether a telephone is off-hook or what signal patterns are being sent out. Outgoing signaling leads can be changed to force conditions at the far end. For example, it may be useful to cause a DTU to lose synchronization. DNIC and 2B1Q signaling leads For DNIC and 2B1Q incoming signaling leads, the Sync lead indicates whether or not the DTU is synchronized. If the Sync lead is off, the DTU is not synchronized and communication between the 2902 MainStreet system and the DTU is not possible. The LQ1 and LQ2 signals represent a two-bit binary number that indicates the quality of the link (proportional to the margin of noise) between the 2902 MainStreet system and the DTU. The higher the number, the higher the link quality. For DNIC and 2B1Q outgoing signaling leads, when the Force Unsync lead is turned on, the DTU loses synchronization. The DTU regains synchronization when the lead is turned off. Table 26-2 lists the incoming and outgoing signaling leads for the DNIC and 2B1Q modules. 2902 MainStreet Technical Practices 26-7 May 2002 90-2906-01 26 — System diagnostics Table 26-2 Incoming and outgoing signaling leads Incoming Outgoing Sync Force Unsync LQ1 — LQ2 — Viewing signaling leads Incoming and outgoing signaling leads, referred to as inputs and outputs respectively by the display, can be viewed. The data area is updated to show the status of the current incoming and outgoing signaling leads. Both the abbreviation and the digital representation of the signals are displayed, with 0 indicating an off state, and 1 indicating an on state. The signaling leads display is not updated automatically. To see the current states of the signaling leads at a given moment, you must refresh the screen by pressing . Procedure 26-8 To view signaling leads MAINT — ON_CIRCUIT — ↵ — SHOW_SIGNL — CTRL_LEADS where pp is 1 or 9, and c is A or B The display shows a screen like the one illustrated in Figure 26-2 for a DNIC module. 26-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics Figure 26-2 Signaling leads display for a DNIC module 2902 MainStreet 82211-ab-cd Alarms:18 No Date 0:12R Circuit Type Loopback Status Connection M01-A DNIC None Configured None Installed Type: 2603 9 Firmware ID : $14 Hardware ID : $2 Feature ID : $1 Status : Ok INPUTS: OUTPUTS: MAINT ON_CIRCUIT 1-A SHOW_SIGNL 1- 2- 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- Driving outgoing signaling leads Each bit of an outgoing signaling lead for a data or primary rate circuit can be driven to a new state: either 0 (off) or 1 (on). After you select a new signaling lead state, the system prompt remains on the display, allowing you to change the signaling lead as many times as you wish. Any change you enter is temporary; the signaling lead status is overridden if any normal network signaling is received. Procedure 26-9 To change outgoing signaling leads MAINT — ON_CIRCUIT — ↵ — SET_SIGNAL ↵ ↵ SK000540 where pp is 1 or 9, c is A or B signal is the signaling lead you wish to change signal state is 0 (off) or 1 (on) 2902 MainStreet Technical Practices 26-9 May 2002 90-2906-01 26 — System diagnostics 26.7 Displaying module and Control card maintenance information If you contact an Alcatel representative for technical advice about a module or card, you need to provide information from the MAINT — ON_MODULE display. A sample display is shown in Figure 26-3. When applicable, the display also identifies: • maintenance being performed on the module • protecting or protected links Procedure 26-10 To view module information for maintenance purposes MAINT — ON_MODULE — or or ↵ where pp is 1 or 9, and p is 1 or 2 Figure 26-3 Module information display for maintenance 2902 MainStreet 82211-ab-cd Alarms:6 No Date 1:11R There is no maintenance being performed on the interface Module Type : E1 Module ID : $28 Interface ID : $14 Interface Type : HDSL LIM MAINT ON_MODULE P2 1-LOOPBACK 2-BYPASS 3- 4- 5- 6-RESET_POSN 7- 8-CANCEL 9-QUIT 0- 26.8 Resetting a module or the Control card If you have problems with a module, for example, if an alarm indicates that there is a module failure, you may want to reset the module. Caution — Resetting the Control card resets the node. 26-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 26 — System diagnostics Procedure 26-11 To reset a module or the Control card MAINT — ON_MODULE — or or ↵ — RESET_POSN where pp is 1 or 9, and p is 1 or 2 2902 MainStreet Technical Practices 26-11 May 2002 90-2906-01 26 — System diagnostics 26-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks 27.1 Using loopbacks 27-2 27.2 2B1Q circuit loopbacks 27-3 27.3 DNIC circuit loopbacks 27-6 27.4 Data circuit loopbacks 27-11 27.5 Primary rate circuit loopbacks 27-13 27.6 Primary rate link loopbacks 27-15 2902 MainStreet Technical Practices 27-1 May 2002 90-2906-01 27 — Loopbacks 27.1 Using loopbacks A loopback is a maintenance function used to isolate faults in equipment and transmission lines. A signal is sent out from a test point and looped back at some other point along the transmission path. The outgoing signal is compared to the returning signal using external test equipment. The 2902 MainStreet system provides several types of loopbacks so that the signal can be returned at different points in the path. This allows you to check progressively longer sections of the transmission, knowing that the fault can be found between the last successful loopback and the first unsuccessful loopback. Up to five loopbacks can be active simultaneously. When this number is reached, loopback softkeys do not appear for circuits without a loopback and the display shows a cautionary message. All loopbacks are temporary in the sense that loopback information is not stored in non-volatile memory. Caution — Initiation of a loopback causes all calls in progress on the affected circuit to be dropped. No new calls can be initiated on the circuit while it is looped back. Note 1 — Maintenance on the module in physical position M2 is accessed through NMTI module position 9. Note 2 — Maintenance information on module position 9 is not available when position 9 is disabled by position 1 (during a super-rate connection). See section 19.11 in Configuration for details. Note 3 — Selecting UNDO_MAINT does not disable background diagnostics, halt directed diagnostics, affect the state of the signaling leads, or remove a primary rate link loopback. Types of loopbacks The 2902 MainStreet system performs loopbacks on circuits (primary rate and data) and primary rate links. Loopbacks on primary rate and data circuits can be unidirectional or bidirectional, and can include loopbacks A, B, C or E. Loopbacks on primary rate links include equipment and line loopbacks. Caution — For Loopback B, loss of input cannot be detected while the loopback is in progress, and no action can be taken until the loopback is removed. Bidirectional and unidirectional loopbacks Loopbacks are either bidirectional, unidirectional or unidirectional with pass-through (see Figure 27-1). 27-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-1 Loopback types Bidirectional loopback Unidirectional loopback Unidirectional loopback with pass-through 3622 For bidirectional loopbacks, the transmission path is interrupted and the signal is looped back to both ends of the connection. For unidirectional loopbacks, the transmission path is interrupted and the signal is looped back in one direction only. For unidirectional loopbacks with pass-through, the transmission path is interrupted and the signal is looped back to one end and passed through to the far end. Loopback indicators Primary rate loopback LEDs on the Control card (see section 24.3) indicate that the 2902 MainStreet system is running a primary rate loopback. When a loopback is in progress for a circuit, the circuit status has “-M” (for maintenance) appended to it. Procedure 27-1 To remove a specific loopback MAINT — ON_CIRCUIT — or ↵ — UNDO_MAINT where pp is 1 or 9, c is 1, 2, A or B p is 1 or 2, c is 1 to 31 Procedure 27-2 To remove all loopbacks MAINT — UNDO_MAINT The UNDO_MAINT softkey only appears when one or more loopbacks are set. 27.2 2B1Q circuit loopbacks 2B1Q modules support remote connection of data devices through 2700 MainStreet series DTUs. 2902 MainStreet Technical Practices 27-3 May 2002 90-2906-01 27 — Loopbacks For 2702 and 2703 MainStreet DTUs that support super-rate, super-rate circuit loopbacks can only be applied while the circuit is connected. If a loopback is applied to either port while neither is connected, the system displays the following error message: “Connect super-rate circuit before applying loopbacks.” If a loopback is applied to one port while the other is involved in a super-rate connection, the system displays the following error message: “Loopback invalid: other port involved in super-rate connection.” Loopback A Figure 27-2 shows loopback A, which occurs simultaneously on both circuits (DTU ports A and B). Loopback A extends from the DX on the Control card and loops back on the 2B1Q line driver located on the 2B1Q module. Figure 27-2 Loopback A for 2700 MainStreet series DTUs 2902 MainStreet 2B1Q Control DTU module card DRAGA 2B1Q DX line driver 2B1Q line driver Loopback A 16580 Loopback B Figure 27-3 shows loopback B, which is a bidirectional loopback that can be initiated on either circuit (port A or port B). The signal from the Control card is looped back within the DTU, in the DRAGA chip, at the end nearest to the 2B1Q module. The signal from the data device is also looped back in the DRAGA at the end nearest the 2B1Q module. 27-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-3 Loopback B for 2700 MainStreet series DTUs 2902 MainStreet 2B1Q Control DTU module card DRAGA Data 2B1Q DX device line driver DRAGA Loopback B 16581 Loopback E Figure 27-4 shows loopback E, which is a bidirectional loopback. The signal from the Control card is looped back within the DTU, in the DRAGA chip, at the end nearest the data device. The signal from the data device is also looped back in the DRAGA at the end nearest the data device. Figure 27-4 Loopback E for 2700 MainStreet series DTUs 2902 MainStreet 2B1Q Control DTU module card DRAGA 2B1Q Data DX line driver device DRAGA Loopback E 16582 2902 MainStreet Technical Practices 27-5 May 2002 90-2906-01 27 — Loopbacks Procedure 27-3 To set a 2B1Q circuit loopback MAINT ON_CIRCUIT UNDO_MAINT ↵ LOOPBACK_A LOOPBACK_B LOOPBACK_E UNDO_LPK SK000541 where pp is 1 or 9, and c is A or B 27.3 DNIC circuit loopbacks DNIC modules support remote connection of data devices through 2600 MainStreet series DTUs. For 2602 and 2603 MainStreet DTUs that support super-rate, super-rate circuit loopbacks can only be applied while the circuit is connected. If a loopback is applied to either port while neither is connected, the system displays the following error message: “Connect super-rate circuit before applying loopbacks.” If a loopback is applied to one port while the other is involved in a super-rate connection, the system displays the following error message: “Loopback invalid: other port involved in super-rate connection.” Loopback A for two-port DTUs For two-port DTUs, loopback A occurs on both lines (Port A and Port B) simultaneously (see Figure 27-5). Loopback A extends from the DX on the Control card and loops back on the DNIC line driver located on the DNIC module. 27-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-5 Loopback A for two-port DTUs 2902 MainStreet DNIC Control DTU module card DNIC DRAGA DX line driver DNIC line driver Loopback A 8850 Loopback A for eight-port DTUs For eight-port DTUs, loopback A occurs on circuit A and circuit B simultaneously (see Figure 27-6). Loopback A extends from the DX on the Control card and loops back on the DNIC line driver located on the DNIC module. Figure 27-6 Loopback A for eight-port DTUs 2902 MainStreet DNIC Control DTU module card Data DNIC DX DRAGA devices line driver 1 to 8 DNIC line driver Loopback A 8851 2902 MainStreet Technical Practices 27-7 May 2002 90-2906-01 27 — Loopbacks Loopback B for two-port DTUs For two-port DTUs, loopback B is a bidirectional loopback that can be initiated on either Port A or Port B (see Figure 27-7). The signal from the Control card is looped back within the DTU in the DRAGA chip, on the side closest to the DNIC module. The signal from the data device is looped back in the DRAGA chip also, but on the inside of the DRAGA. Figure 27-7 Loopback B for two-port DTUs 2902 MainStreet DNIC Control DTU module card Data DNIC DX DRAGA device line driver DRAGA Loopback B 8852 Loopback B for eight-port DTUs For eight-port DTUs, loopback B is a bidirectional loopback that can be initiated from either circuit A or B (see Figure 27-8). The signal from the Control card is looped back within the DTU inside the DRAGA chip. The signals from the data devices connected to the selected aggregate port are looped back on the side closest to the DNIC module. 27-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-8 Loopback B for eight-port DTUs 2902 MainStreet DNIC Control 2606 module card MainStreet DTU DNIC Data DX line driver devices DRAGA 1 to 8 DRAGA Loopback B 8962 Loopback C for two-port DTUs For two-port DTUs, loopback C is a bidirectional loopback. The signal from the Control card is looped back within the DTU inside the DRAGA chip (see Figure 27-9). The signal from the data device is looped back in the DTU, at the DRAGA, on the side closest to the data device. Figure 27-9 Loopback C for two-port DTUs 2902 MainStreet DNIC Control DTU module card DNIC Data DRAGA DX line driver device DRAGA Loopback C 8853 2902 MainStreet Technical Practices 27-9 May 2002 90-2906-01 27 — Loopbacks Loopback C for eight-port DTUs For eight-port DTUs, loopback C is a bidirectional loopback that can be initiated from either circuit A or B (see Figure 27-10). The signal from the Control card is looped back within the DTU inside the DRAGA chip. The signals from the data devices connected to the selected aggregate port are looped back on the side closest to the data devices. Figure 27-10 Loopback C for eight-port DTUs 2902 MainStreet DNIC Control DTU module card Data DNIC DX DRAGA devices line driver 1 to 8 DRAGA Loopback C 8854 Procedure 27-4 To set a DNIC circuit loopback MAINT UNDO_MAINT ON_CIRCUIT ↵ LOOPBACK_A LOOPBACK_B LOOPBACK_C UNDO_LPK SK000542 where pp is 1 or 9, and c is A or B 27-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks 27.4 Data circuit loopbacks The RS-232 DCM, Codirectional DCM, and subrate and super-rate circuits of the X.21 and V.35 DCMs support loopbacks B and C. Caution — Initiating a data circuit loopback may cause the data session on the selected circuit to be dropped. Loopback B for RS-232, X.21 and V.35 DCM circuits Loopback B for the RS-232, X.21 or V.35 DCM is a bidirectional loopback that extends from the DX and loops back in the gate array itself, as close as possible to the network side (see Figure 27-11). Each circuit on the RS-232 DCM can be looped back individually. Figure 27-11 Loopback B for RS-232, X.21 and V.35 DCMs 2902 MainStreet DCM Control Data card device Gate DX array Gate array Loopback B 8855 Loopback B Codirectional DCM circuits Loopback B for the Codirectional DCM occurs at the tributary output (see Figure 27-12). While Loopback B is applied to a Codirectional DCM circuit, 8 kHz timing is turned on and all ones is turned off. Even if the Codirectional DCM circuit has been configured not to generate 8 kHz timing, it generates 8 kHz timing during the test. Even if the Codirectional DCM circuit has been configured to generate all ones, it does not generate all ones during the test. 2902 MainStreet Technical Practices 27-11 May 2002 90-2906-01 27 — Loopbacks Figure 27-12 Loopback B for the Codirectional DCM 2902 MainStreet Codirectional Control Data DCM card interface Line DX interface Line interface Loopback B 8856 Loopback C for RS-232, X.21 and V.35 DCM circuits Loopback C for the RS-232, X.21 or V.35 DCM is a bidirectional loopback that extends from the DX and loops back in the gate array itself, as close as possible to the attached data device (see Figure 27-13). Each circuit can be looped back individually on the RS-232 DCM. Figure 27-13 Loopback C for RS-232, X.21 and V.35 DCMs 2902 MainStreet DCM Control Data card device Gate DX array Gate array Loopback C 8857 27-12 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Loopback C Codirectional DCM circuits Loopback C for the Codirectional DCM is a bidirectional loopback that loops back at the DX (see Figure 27-14). Figure 27-14 Loopback C for the Codirectional DCM 2902 MainStreet Codirectional Control Data DCM card interface Line DX interface DX Loopback C 8858 Procedure 27-5 To set a DCM circuit loopback MAINT UNDO_MAINT ON_CIRCUIT ↵ LOOPBACK_B LOOPBACK_C UNDO_LPK SK000543 where pp is 1 or 9, and c is 1 or 2 27.5 Primary rate circuit loopbacks The 2902 MainStreet system supports two types of primary rate circuit loopbacks—Loopback A and Loopback C. Both types can be performed on a LIM at the same time. 2902 MainStreet Technical Practices 27-13 May 2002 90-2906-01 27 — Loopbacks Loopback A Loopback A can only be selected for one circuit in a link at a time. Figure 27-15 shows Loopback A for a primary rate circuit. When Loopback A is initiated, the circuit is looped back on the E1 framer and is passed through to the far end. Figure 27-15 Loopback A for primary rate circuits 2902 MainStreet Control card E1 G.703, E1 Framer DX HDSL or Optical LIM E1 Framer 9114 Loopback C Loopback C is a bidirectional loopback. Figure 27-16 shows Loopback C. The signal from the system is looped back in the DX on the Control card. The signal from the primary rate circuitry is looped back at the side of the Control card closest to the primary rate circuitry. 27-14 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-16 Loopback C for primary rate circuits 2902 MainStreet Control card E1 G.703, E1 Framer DX HDSL or Optical LIM DX 9115 Procedure 27-6 To set a primary rate circuit loopback MAINT ON_CIRCUIT UNDO_MAINT ↵ LOOPBACK_A LOOPBACK_C UNDO_LPK SK000544 where p is 1 or 2, and c is 1 to 31 27.6 Primary rate link loopbacks The two types of primary rate link loopbacks—equipment and line—are used to test end-to-end connections over a primary rate link. When initiated, the entire link is looped back. Caution — Initiating a primary rate link loopback causes all calls in progress on the selected module to be dropped. No new calls can be initiated on the module while it is looped back. Primary rate loopbacks should be performed only in extreme cases or when node traffic is minimal. 2902 MainStreet Technical Practices 27-15 May 2002 90-2906-01 27 — Loopbacks An equipment and a line loopback cannot be performed on a LIM at the same time. Primary rate loopback LEDs are provided on the Control card to indicate that a loopback is in progress. See section 24.3. Note — It can take up to 60 seconds to establish an HDSL or optical link loopback. Figure 27-17 Equipment loopback for E1 G.703 and E1 Optical LIMs 2902 MainStreet E1 G.703 Control or card Optical LIM E1 LIM 9116 HDSL LIMs When an E1 HDSL LIM is configured for an equipment loopback, the signal is looped back toward the node and passed through to the far end, as shown in Figure 27-18. The loopback occurs as close to the HDSL output as possible. 27-16 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Figure 27-18 Equipment loopback for E1 HDSL LIMs 2902 MainStreet HDSL LIM Control or card HDSL LIM2 Loop 1 interface HDSL pair 1 MUX Loop 2 interface HDSL pair 2 11867 Line loopback The line loopback is unidirectional with pass-through. It can be initiated on both primary rate links at the same time. E1 G.703 and E1 Optical LIMs Figure 27-19 illustrates the line loopback for the E1 G.703 and E1 Optical LIMs. The signal originates from the E1 link, is looped back at the E1 LIM, and passes through to the DX on the Control card. 2902 MainStreet Technical Practices 27-17 May 2002 90-2906-01 27 — Loopbacks Figure 27-19 Line loopback for E1 G.703 and E1 Optical LIMs 2902 MainStreet Primary rate Control interface card DX DX LIM DX LIM Primary rate line loopback 8863 E1 HDSL LIMs An E1 HDSL LIM loops the signal received from the HDSL line back to the network, and passes it through to the Control card (see Figure 27-20). Figure 27-20 Line loopback for E1 HDSL LIMs 2902 MainStreet Control HDSL LIM card or HDSL LIM2 Loop 1 interface HDSL pair 1 MUX Loop 2 interface HDSL pair 2 11869 27-18 2902 MainStreet Technical Practices 90-2906-01 May 2002 27 — Loopbacks Procedure 27-7 To initiate a primary rate loopback MAINT — ON_MODULE — ↵ — LOOPBACK EQUIPMENT LINE SK000546 where p is 1 or 2 Procedure 27-8 To remove a primary rate loopback MAINT — ON_MODULE — ↵ — UNDO_LPK where p is 1 or 2 2902 MainStreet Technical Practices 27-19 May 2002 90-2906-01 27 — Loopbacks 27-20 2902 MainStreet Technical Practices 90-2906-01 May 2002 28 — Statistics 28.1 Synchronization statistics 28-2 28.2 FAS and CRC4 statistics 28-3 28.3 Codirectional DCM quality statistics 28-7 2902 MainStreet Technical Practices 28-1 May 2002 90-2906-01 28 — Statistics 28.1 Synchronization statistics Synchronization statistics report information about the synchronization sources in E1 or HDSL links, including the amount of time each synchronization source was in use and how many times it was switched. For more information on synchronization sources, see section 13.2 in Configuration. Procedure 28-1 To display synchronization statistics STATS — SYNCH A screen display similar to Figure 28-1 appears. Table 28-1 describes the fields on the display. Figure 28-1 Synchronization statistics display 2902 MainStreet 82211-ab-cd Alarms:6 No Date 3:01R System Synch Connect Time Current Synch Source: Free Run Curr. Interval Last Hr. Worst Hr. Accum. Src. Switches 0:00R Free Run 173 3600 0 10754 0 STATS SYNCH 1-CLR_STATS 2- 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- 28-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 28 — Statistics Table 28-1 Synchronization statistics fields Item Description Current Interval The number of seconds the source has been in use during the current 15-minute interval; you can update the information by refreshing the screen ( ). Last Hour The number of seconds the source was in use for the last hour. The listing does not include statistics for the current interval. Worst Hour The statistics for the hour having the greatest number of synchronization source switches. The Worst Hour statistics are based on the worst hour since the last time the statistics were cleared. Accumulated The total accumulated statistics since the last time the statistics were cleared. Source Switches The number of times that the synchronization source has changed. For example, a change from Free Run to Primary and then back to Free Run is counted as two source switches. Primary, Free Run The length of time (in seconds) that the particular synchronization source was in use. Procedure 28-2 To enable or disable automatic clearing of synchronization statistics When automatic clearing is enabled (AUTO_CLR), the synchronization statistics for every circuit are cleared daily. When automatic clearing is disabled (MAN_CLEAR), the synchronization statistics are not cleared daily. With automatic clearing selected, statistics can also be cleared manually. STATS — MAN_CLEAR/AUTO_CLR* * Default Procedure 28-3 To clear synchronization statistics manually All synchronization statistics can be cleared at once. Enter: STATS — SYNCH — CLR_STATS 28.2 FAS and CRC4 statistics The 2902 MainStreet system can gather FAS or CRC4 statistics to provide a measure of E1 or HDSL link performance. FAS and CRC4 statistics are updated every 15 minutes to reflect the previous 24-hour period, and can be cleared automatically or manually. 2902 MainStreet Technical Practices 28-3 May 2002 90-2906-01 28 — Statistics FAS statistics are similar to HDB3 statistics. HDB3 preserves the ones density of an electrical system by encoding strings of more than three zeros with bipolar violations. FAS statistics are used for link fault isolation. CRC4 statistics track CRC errors on E1 or HDSL links. CRC4 statistics are used for link fault isolation. FAS and CRC4 statistics include: • available time • local out of service time • remote out of service time • total slip count FAS and CRC4 statistics can either be cleared manually or cleared automatically every 24 hours at midnight (the error event count is not cleared automatically). Procedure 28-4 To configure the statistics type The type of statistics collected (FAS or CRC4) is selected when you configure the module position. CONFIG — POSITION — ↵ — OPTIONS FAS_STATS* CRC4_STATS SK000547 where p is 1 or 2 * Default Procedure 28-5 To display FAS or CRC4 statistics STATS — QUALITY — ↵ where p is 1 or 2 Figure 28-2 shows FAS statistics for an E1 link. Table 28-2 describes the fields on the display. The display for CRC4 statistics is similar. 28-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 28 — Statistics Figure 28-2 FAS statistics display 2902 MainStreet 82211-ab-cd Alarms:1 No Date 3:50P Link Quality Position: P1 Type: E1 FAS Status: Red Alarm Current Interval Accumulated Worst Interval (456 sec) 168 (2:00P) Available Time: 191 7310 900 Local Out of Service Time: 5 976 27 Remote Out of Service Time: 0 0 0 Total Slip Count: 64 298 37 Errored Seconds: 0 0 N/A Severely Errored Seconds 0 0 0 Failed Seconds 0 0 0 Error Events (since last clear): 0 STATS QUALITY P1 1-CLR_STATS 2-CLR_ERR_EV 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- 2902 MainStreet Technical Practices 28-5 May 2002 90-2906-01 28 — Statistics Table 28-2 FAS and CRC4 statistics fields Item Description Link Quality, The heading in the data area indicates the type of statistics, the position number of Position, the primary rate link, and the type of primary rate link. The current status of the link Type and is also given. Status Current The FAS statistics for the current 15-minute interval are listed in this column. The Interval current interval statistics are updated every second, but only appear on the screen when the screen is refreshed. To refresh the display, press . Accumulated For the categories Available Time, Local Out of Service Time, Remote Out of Service Time and Total Slip Count, this column lists the total accumulated statistics since the last time the statistics were cleared. The statistics are automatically cleared (reset to 0) every 24-hour period (at midnight) if automatic clearing is selected; otherwise, they must be cleared manually. Worst Interval For the categories Available Time, Local Out of Service Time, Remote Out of Service Time and Total Slip Count, this column lists the statistics for the interval in the last 24 hours with the most out of service time. The time at which the worst interval ended is given in parentheses at the top of the column. N/A is displayed whenever there are no previous intervals of recorded errors. Available Time The length of time (in seconds) during which the primary rate module was both installed and configured. Local Out of The length of time (in seconds) that the link was out of service due to a fault at the Service Time local end of the link. This includes time during which both ends were out of service. Remote Out of The length of time (in seconds) that the link was out of service due to a fault at the Service Time remote end of the link. The time during which both ends were out of service is not included in this statistic. Total Slip The number of slips. A slip indicates that a byte has been inserted (line rate too slow Count relative to system timing) or deleted (line rate too fast relative to system timing) at the receiver. Error Events The number of error events since the statistics were last cleared. Procedure 28-6 To enable or disable automatic clearing of FAS or CRC4 statistics When automatic clearing is enabled (AUTO_CLR), the FAS or CRC4 statistics for each primary rate module are cleared at midnight (error event count is not cleared). When automatic clearing is disabled (MAN_CLEAR), FAS or CRC4 statistics are not automatically cleared at midnight. With automatic clearing enabled, statistics can still be cleared manually (as described below). STATS — MAN_CLEAR/AUTO_CLR* * Default 28-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 28 — Statistics Procedure 28-7 To clear FAS or CRC4 statistics manually All statistics on the displayed screen, other than the error event count, can be cleared manually. STATS — QUALITY — ↵ — CLR_STATS where p is 1 or 2 Procedure 28-8 To clear error event count manually The error event count is cleared without clearing any other FAS or CRC4 statistics. STATS — QUALITY — ↵ — CLR_ERR_EV where p is 1 or 2 28.3 Codirectional DCM quality statistics Quality statistics for the Codirectional DCM display the slip count (see Figure 28-3). A slip indicates that a byte has been inserted or deleted at the receiver (the line rate is too slow [insert] or too fast [delete] relative to the system timing). Slips are counted until they are cleared manually or until they reach 32 000. If the counter reaches 32 000, it stops counting until it is manually cleared. 2902 MainStreet Technical Practices 28-7 May 2002 90-2906-01 28 — Statistics Figure 28-3 Codirectional DCM quality statistics display 2902 MainStreet 82311-ab-cd Alarms:1 No Date 3:50P Link Quality: Position: M01 Type: 64K_CODIR Status: Module Present CIRCUIT 1 Slip Count: 14 CIRCUIT 2 Slip Count: 35 STATS QUALITY P1 1-CLR_STATS 2- 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- Procedure 28-9 To display Codirectional DCM quality statistics STATS — QUALITY — ↵ where pp is 1 or 9 Procedure 28-10 To clear Codirectional DCM quality statistics STATS — QUALITY — ↵ — CLR_STATS where pp is 1 or 9 28-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 29 — CPSS maintenance 29.1 Routing information 29-2 29.2 CPSS grooming 29-5 2902 MainStreet Technical Practices 29-1 May 2002 90-2906-01 29 — CPSS maintenance 29.1 Routing information When a 2902 MainStreet system is part of a network of Alcatel proprietary products capable of sending CPSS messages, it constructs a routing table that contains information about the nodes in the network. The 2902 MainStreet system knows which nodes it can send CPSS messages to, how many hops separate it from those nodes, and which route it should use to send the messages. A hop is equivalent to one CPSS link between two nodes and is not related to physical distance. The routing table information can be displayed through the node management session to assist in diagnostic and maintenance operations. You can display three tables to show different routing information: • all nodes in the network (SHOW_NODES) • all nodes in the network that are a specified number of hops (CPSS links) away from the 2902 MainStreet system (HOPS_AWAY) • all nodes in the network that use a specific path to communicate with the 2902 MainStreet system (VIA_PATH) In each case, you specify a node number. The display lists all nodes having a node number equal to or greater than the number specified. Procedure 29-1 To view routing table information MAINT — MORE — VIEW_NET Figure 29-1 shows the routing information for network CPSS messages. Figure 29-1 Routing information display 2902 MainStreet 82211-ab-cd Alarms:1 No Date 0:00R Node: 39 Clock Source: Free Run Clock Cl: 15 Nodes in Network: 7 Node Hops Cl Circuit Node Hops Cl Circuit Node Hops Cl Circuit 14 1 0 P1-01 52 2 0 P1-P1 78 3 0 P1-01 26 1 0 P2-17 65 2 0 P1-01 1023 2 0 P1-01 MAINT VIEW_NET 1-SHOW_NODES 2-HOPS_AWAY 3-VIA_PATH 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- 29-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 29 — CPSS maintenance If the table contains no entries meeting these criteria, the display shows a message to this effect on the diagnostics line. There may be more routing information than can be displayed on a single screen. To view information for additional nodes, enter a higher or lower node number. Procedure 29-2 To display all nodes in the network MAINT — MORE — VIEW_NET — SHOW_NODES — ↵ where node number is the node number from which to start searching for routing table information Figure 29-2 illustrates a sample network and Figure 29-3 illustrates a SHOW_NODES display, where the node number entered is 3. Table 29-1 describes the column headings in the display. The top line of the data area shows the node number of the node you are logged on to, its current clock source and class, and the number of nodes in the network. Figure 29-2 Sample network 3600 MainStreet node #52 P1-01 P2-17 2902 MainStreet node #39 3600 MainStreet 3600 MainStreet 3600 MainStreet node #78 node #14 node #26 Serial port 1 3600 MainStreet node #65 Network Manager node #1023 8875 2902 MainStreet Technical Practices 29-3 May 2002 90-2906-01 29 — CPSS maintenance Figure 29-3 Node information display 2902 MainStreet 82211-ab-cd Alarms:1 No Date 0:00R Node: 39 Clock Source: Free Run Clock Cl: 15 Nodes in Network: 7 Node Hops Cl Circuit Node Hops Cl Circuit Node Hops Cl Circuit 14 1 0 P1-01 52 2 0 P1-P1 78 3 0 P1-01 26 1 0 P2-17 65 2 0 P1-01 1023 2 0 P1-01 MAINT VIEW_NET SHOW_NODES 3 1- 2- 3- 4- 5- 6- 7- 8-CANCEL 9-QUIT 0- Table 29-1 Node information display fields Column heading Description Node Indicates the node number (1) Hops Indicates the node distance in hops from the local node Cl Indicates the node class number Circuit Indicates the circuit used by the local node for CPSS message transmission to the node Note (1) For example, messages sent from node 39 to node 79 that pass through nodes 14 and 65 use three CPSS links. Therefore, node 78 is three hops away from node 39. 29-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 29 — CPSS maintenance Procedure 29-3 To view nodes a specified number of hops away MAINT — MORE — VIEW_NET — HOPS_AWAY ↵ ↵ SK000548 where number is the number of hops node number is the node number from which to start searching for routing table information A display similar to Figure 29-3 appears. Procedure 29-4 To display the nodes within a specific path MAINT — MORE — VIEW_NET — VIA_PATH or ↵ ↵ SK000549 where p is 1 or 2, and c is 1 to 30 (CAS) or 31 (CCS) pp is 1 or 9, and c is 1, 2, A or B node number is the node number from which to start searching for routing table information A display similar to Figure 29-3 appears. It shows information on the nodes to which the 2902 MainStreet system can send CPSS messages via the specified path. 29.2 CPSS grooming In a network made up of Alcatel proprietary equipment, only one channel per pair of adjacent nodes needs to be dedicated to CPSS messages. However, if Alcatel proprietary equipment is connected to a network made up of third-party equipment, the ability to dynamically cross-connect more than one CPSS channel to a single CPSS carrier is advantageous. This dynamic cross-connection is called CPSS grooming. Figure 29-4 shows an example of CPSS grooming. 2902 MainStreet Technical Practices 29-5 May 2002 90-2906-01 29 — CPSS maintenance Figure 29-4 CPSS grooming application 3600 MainStreet node #1 E1 3600 MainStreet node #2 E1 Many DS0s configured for CPSS E1 E1 Network equipment Dedicated 2902 MainStreet E1 link node #1 3600 MainStreet node #3 E1 E1 Single DS0s configured for CPSS 3600 MainStreet node #4 3600 MainStreet node #5 8876 In Figure 29-4, the 2902 MainStreet node performs CPSS grooming. It mediates between a single CPSS channel on one primary rate link and many CPSS channels on the other. The 2902 MainStreet system monitors the incoming CPSS channels from both links and makes a dynamic cross-connection as required. For example, if a CPSS message addressed to node #3 comes in on the E1 link shown on the left of the 2902 MainStreet node, the 2902 MainStreet node connects the single CPSS channel to the DS0 for node #3 for the message to pass. On the right-hand side of the 2902 MainStreet node, each CPSS channel is routed separately and transparently through the third party network, from the 2902 MainStreet node doing CPSS grooming to the other proprietary equipment. Note — Timeslot 0 and all 30 DS0s can be configured as CPSS channels. 29-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 30 — Database management 30.1 Backing up, verifying, and restoring the configuration database 30-2 30.2 Viewing and resetting the nonvolatile memory 30-5 2902 MainStreet Technical Practices 30-1 May 2002 90-2906-01 30 — Database management 30.1 Backing up, verifying, and restoring the configuration database The 2902 MainStreet system stores its configuration database in NVM on the Control card. You can back up, verify a backup, and restore the database using the NMTI, Craft Interface Node Manager or a computer running the 5620 NM software. However, you cannot restore the database from a 5620 NM connected to the 2902 MainStreet system through a modem. If you are using a VT100 terminal to run the node management session for a backup, verify or restore operation, both 2902 MainStreet system serial ports are used: one for the terminal and one for a data storage device, such as a PC or other EIA/TIA-232 compatible device. The device stores the backup files. Backing up the database The backup option creates a backup copy of the configuration database on an external device. When the backup commands are issued from a terminal running the NMTI session, the backup file is saved to a PC. When the backup commands are issued from a 5620 NM, the backup file is saved to the computer running the network management program. During a backup, calls in progress continue and new calls can be initiated. Before backing up the database, ensure that the backup device is ready to receive the data transfer. For example, a PC must be running software that captures incoming serial data to be stored in an ASCII file. The device must be connected to a properly configured 2902 MainStreet system serial port. For baud rates of 2400, 4800 and 9600 b/s, the flow control must be set. The backup procedure can last several minutes, depending on the selected baud rate and the complexity of the configuration database. It is recommended that you make a copy of the backup file in case the file becomes corrupted. If the current database has been corrupted and repaired (due to an NVM problem), it cannot be used as a backup. At the end of the backup procedure, the display shows “The NVM is corrupted and cannot be backed up”. The fault in the NVM does not necessarily interfere with the operation of the 2902 MainStreet system. Verifying a backup file The backup file should be verified with the current database on the 2902 MainStreet system. The file verification can be performed whenever the external device holding the backup file is accessible to the system. During a verify, calls in progress continue and new calls can be initiated. The same baud rate must be used for both the backup and verify procedures. For baud rates of 2400, 4800 and 9600 b/s, the flow control must be set. When the verification procedure is complete, the 2902 MainStreet system displays the message “Database successfully verified” if the two databases are identical. If they are not identical, an error message is displayed. 30-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 30 — Database management Restoring the database It may be necessary to restore the database when: • the system configuration file has been damaged • new software has been loaded and the system must be reconfigured • the Control card has been replaced You can restore a backup configuration file from a PC or 5620 NM connected directly to the 2902 MainStreet system. You cannot restore a database using a 5620 NM that is connected via a modem. Caution — The system is disabled while configuration settings are being restored. All calls in progress are dropped and no new calls can be initiated. Configuration settings should be restored when node traffic is minimal. Before restoring the database, ensure that the external device is ready to send the backup file to the 2902 MainStreet system, and that it is connected a properly configured 2902 MainStreet system serial port. For baud rates of 2400, 4800 and 9600 b/s, the flow control must be set. The same baud rate must be used for both the backup and restore procedures. If the data transfer finishes without errors, the system restarts automatically with the new configuration. If an error occurs, the system reloads the factory-set (default) configuration. The default database does not contain any user configurations (such as cross-connections or module parameter settings). When the configuration database is restored, the node name and number are maintained from the previous configuration, passwords and session time return to their defaults, and access levels are restored from the backup file. The restore procedure can last several minutes. The seven-segment display on the Control card flashes the letter L during data transfer. Note — The previous synchronization source configuration is restored but the synchronization source is not. After a restore, all synchronization sources are disabled (the default setting), and you must re-enable them. Procedure 30-1 To back up, verify a backup, or restore the database If you are using the NMTI and a VT100 terminal to run the node management session, connect your data storage device to the second serial port. 2902 MainStreet Technical Practices 30-3 May 2002 90-2906-01 30 — Database management 1 Set up the serial port parameters. HOUSE SER_PORT_1 SER_PORT_2 BAUD_RATE FLOW_CTRL PORT_TYPE NONE* XON/XOFF DTR 300 600 1200*** 2400 4800 9600** VT100** CPSS PRINTER CPSS_MODEM*** SK000550 * Default for both ports ** Default for serial port 1 *** Default for serial port 2 For baud rates of 2400, 4800 and 9600 b/s, the flow control must be set to XON/XOFF or DTR. DTR flow control is supported on serial port 2 only. If the device is not using flow control, ensure that it is able to receive the data continuously, regardless of the baud rate selected for the transfer. For a direct connection to a 5620 NM, select CPSS. For an indirect connection (via modem), select CPSS_MODEM. 30-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 30 — Database management 2 Enter: MAINT –– MORE BACKUP RESTORE VERIFY ↵ PROCEED ↵ ↵ SK000551 where filename is a name having up to eight characters (no spaces) description is a text string of up to 49 characters Filename and description do not apply to VT100 terminal management. When you select RESTORE — PROCEED, the display shows “Please wait for initialization”. When the message changes to “Processing incoming data stream –”, transmit the backup file. 3 Select Cancel to stop the procedure. If the restore procedure is canceled, the database returns to its default values. 30.2 Viewing and resetting the nonvolatile memory You can view information about the NVM, including the NVM block size, the number of blocks being used by the configuration database, the number of free blocks, the number of bad blocks detected, and the total number of NVM blocks. If the NVM has been corrupted and repaired, additional information about the repaired item(s) is displayed. When you reset the NVM, you erase all user configurations (including cross-connections or module parameters) and restore the default database. You can reset the NVM from a PC running the Craft Interface Node Manager or a 5620 NM connected directly to the node. 2902 MainStreet Technical Practices 30-5 May 2002 90-2906-01 30 — Database management Figure 30-1 NVM information display 2902 MainStreet 82211-ab-cd Alarms:5 No Date 7:23R Block Size : 48 Allocated Blocks : 171 Free Blocks : 510 Bad Blocks : 0 Total Blocks : 681 MAINT NVM_DATA 1- 2- 3- 4- 5- 6- 7- 8- CANCEL 9_QUIT 0- Procedure 30-2 To view the NVM MAINT — MORE — NVM_DATA If bad blocks exist, but no repair information is listed, the bad blocks occurred in unused space. You should reset the NVM to the default values. Procedure 30-3 To reset the NVM Caution — Resetting the NVM overwrites the current configuration database with the default configuration database. If you plan to restore the database, ensure that you have an up-to-date backup file before proceeding. MAINT — MORE — RESTORE — ↵ — CANCEL where filename is picked from a list of database filenames that appears on the display Check the NVM as described above. If no bad blocks appear, restore the configuration database. See section 30.1. If bad blocks reappear, the NVM must be replaced. Contact your technical support representative. 30-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 31 — Hardware maintenance procedures 31.1 Measuring the power rails 31-2 31.2 Testing and replacing the fuse 31-3 2902 MainStreet Technical Practices 31-1 May 2002 90-2906-01 Loop Status U 1 2 Display P2 P1 Rx-1 Tx-1 Rx-2 Tx-2 Line-1 Line-2 Modem Terminal Alarm Slot 1 Slot 2 I O EDG Sig/Gnd 31 — Hardware maintenance procedures 31.1 Measuring the power rails Test points for measuring power rail voltages are available at connectors A and B of either interface module position. Use a voltmeter to make measurements between ground (GND) and the desired test point. Figure 31-1 locates the connectors and Figure 31-2 identifies the pins. The expected voltages and tolerances are listed in Table 31-1. Figure 31-1 Interface module connector identification Connector B Connector A 9120 31-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 31 — Hardware maintenance procedures Figure 31-2 Power rail test points Connector B 22 21 - Ground 19 17 2 1 22 21 15 5 Ground - 2 1 Connector A 8961 Table 31-1 Power rail test points Pin number Voltage Tolerance Connector A 1 +5 V dc ±5% Connector B 17 +15 V dc ±5% 19 –15 V dc ±5% 22 +5 V dc ±5% 31.2 Testing and replacing the fuse The fuse for the 2902 MainStreet system is a slow blow type with a 2 A, 250 V rating. Warning — To ensure continued fire protection, the replacement fuse must be a slow blow type with a 2 A, 250 V rating. 2902 MainStreet Technical Practices 31-3 May 2002 90-2906-01 31 — Hardware maintenance procedures Procedure 31-1 To remove and check the fuse 1 Turn off the power switch. 2 Disconnect the power cord by unplugging it from the ac source, and then from the unit. 3 With a small blade screwdriver, pry the fuse holder away from the power connection module and pull the fuse holder out (see Figure 31-3). Figure 31-3 Removing the fuse holder 8958 4 Remove the fuse and test it for continuity. If it passes the test, put the fuse back in the fuse holder. If it fails the test, install a new fuse. A spare fuse may be kept in the spare fuse compartment (see Figure 31-4). Figure 31-4 Spare fuse compartment Fuse holder Fuse Spare fuse compartment 8959 5 Put the fuse holder back in the power connection module. 6 Turn on the power switch. See section 4.4 in Installation for a description of startup diagnostics. 31-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 32 — Primary rate link bypass 32.1 Initiating a primary rate link bypass 32-2 2902 MainStreet Technical Practices 32-1 May 2002 90-2906-01 32 — Primary rate link bypass 32.1 Initiating a primary rate link bypass Primary rate bypass is supported by E1 G.703 LIMs only. You can initiate a link bypass for maintenance purposes. The bypass operation must be configured or removed for each primary rate link. Caution — Initiation of a bypass operation breaks all data circuit connections to the affected node. Procedure 32-1 To initiate or remove a primary rate link bypass MAINT — ON_MODULE — ↵ — BYPASS/UNDO_BPASS* where p is 1 or 2 * Default 32-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 Glossary 2B1Q two binary, one quaternary An ISDN line encoding technique that uses two bits to represent four variations in amplitude and polarity. AIS alarm indication signal A code sent downstream in a digital network to indicate a traffic related defect has been detected. ALB analog loopback A method of testing modems and data terminals by disconnecting the device from the telephone line and looping a signal out through the device’s transmit side and in through its receive side. The test tells if the trouble is with the telephone line or with the modem. ANM advanced network management ANS automatic network synchronization ANS is a proprietary algorithm which automatically selects a synchronization pattern for a network. It allows networks to be divided into sectors with independent timing. Each sector has a master synchronization node. AWG American wire gauge A standard measuring gauge for non-ferrous conductors. BER bit error rate The ratio of incorrect bits to total number of bits transmitted. BNC A bayonet-locking connector (Bayonet-Neill-Concelman) 2902 MainStreet Technical Practices GL-1 May 2002 90-2906-01 Glossary b/s bits per second C signal control signal CAS channel associated signaling A type of E1 link where 4 bits of signaling per timeslot are multiplexed into timeslot 16. CBW central battery working CCS common channel signaling A type of E1 link where timeslot 16 is used for message-oriented signaling. CEPT Conférence des administrations Européennes des Postes et Télécommunications (European Conference of Postal and Telecommunications Administrations) CPSS control packet switching system A proprietary network protocol for communication between equipment. Similar to X.25, CPSS is a packet-switched system used to transfer configuration and status information between nodes. CRC4 cyclic redundancy check 4 bit CSA carrier serving area CSU channel service unit Provides the functionality for customer equipment to interface to a T1 line. CTS clear to send DCD data carrier detect DCE data communications equipment DCE refers to the gender of the interface on a data device, such as a modem or transceiver. The pinout wiring is such that pin 2 receives data and pin 3 transmits data. It must be connected to a DTE device. DCM direct connect module A module residing on a small multiplexer product. Either a low speed RS-232 variety, or a higher speed X.21, V.35 variety. DNIC Data Network Interface Circuit DNIC line cards/modules are supported on all 3600 MainStreet series nodes. They support high modularity connections from a great variety of remote data devices to the nodes, via the 2600 MainStreet series of DTUs. DRAGA dual rate adaption gate array A proprietary dual port chip for adapting common data speed to the Mitel ST-BUS. One of the rate adaption schemes built into the chip is HCM for speeds up to 56 kb/s. GL-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 Glossary DS0 digital service, level 0 DS0 is a worldwide standard for PCM digitized voice. It operates at 64 kb/s. DSL digital subscriber line DSP digital signal processor A microprocessor which is optimized for signal processing applications. DSR data set ready A V.24 control signal. DSU data service unit or digital service unit A unit which provides the functionality of the CSU and in addition, provides timing recovery and interfaces to the DTE of the customer. DTE data terminal equipment A communications interface such as a computer or terminal system. DTR data terminal ready V-series interface signal. DX digital cross-connect switch EDG energy dumping ground EDX equal-delay digital cross-connect switch EMC electromagnetic compatibility EMI electromagnetic interference EPROM erasable programmable read-only memory An EPROM is a read-only semiconductor memory device that can be erased with ultraviolet light and electronically reprogrammed. ETSI European Telecommunications Standards Institute FAS frame alignment signal On E1s, this is a seven bit sequence sent once per two frames of data for alignment. G.703 G703 is the ITU-T specification pertaining to several digital telecommunication interfaces. It relates to the physical and electrical levels only. One example is E1 (2.048 Mb/s). GND ground 2902 MainStreet Technical Practices GL-3 May 2002 90-2906-01 Glossary HCM high capacity multiplexing HCM is a proprietary rate adaption and SRM scheme that provides bandwidth granularity of 800 b/s, allowing 98% bandwidth utilization on aggregate links. HDB3 high-density bipolar 3 Method of preserving one’s density of an electrical signal by encoding strings of more than three zeroes with bipolar violations. HDLC High-level data link control An ISO standard for serial data communication. A family of bit-oriented protocols providing frames of information with address, control and frame check sequence fields. It is considered a superset of several other protocols such as SDLC, LAP, LAPB, LAPD. HDSL high bit-rate digital subscriber line An alternate technology to repeatered T1 lines. Supports repeaterless DS1 rate access over non-conditioned copper loops that conform to CSA guidelines. I signal indicator signal IC integrated circuit IEC International Electrotechnical Committee IEEE Institute of Electrical and Electronic Engineers The IEEE is the organization responsible for defining many of the standards used in the electrical and electronics industries. I/F interface ITU-T International Telecommunications Union - Telecommunications The ITU-T is the telecommunications standardization sector of the ITU. An advisory committee established under the United Nations to recommend international telecommunications standards. The ITU-T is an international standards body for the telecommunications industry. It was established by the United Nations and has membership from almost every government in the world. It was formerly known as CCITT. LAN local area network A LAN is a network that operates within a limited geographical area, such as within a building. It connects a variety of data devices, such as PCs, servers and printers. Communication between devices is at a very high rate, between 1 and 100 Mb/s. GL-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 Glossary LAPB link access procedure balanced LAPB is the most common data link control protocol used to interface X.25 DTEs. It is a full-duplex, point-to-point bit-synchronous protocol used in packet-switched networks. LAPD link access protocol for D channel A link access procedure for the D channel. Similar to LAPB, the main difference is the addition of more addressing information. LED light emitting diode An LED is a semiconductor diode that emits light when a current passes through it. LGS loop start/ground start - subscriber card Subscriber-end voice interface which supports loop start and ground start signaling. LIM line interface module A network terminator for CEPT and T1. It can be installed on a control card or in the NTI module positions on the E1/T1 card. LIS loss of incoming signal LQ1 link quality bit 1 LQ2 link quality bit 2 NMTI node management terminal interface The local user interface for a network product. NOC network operations centre NTU network termination unit NVM non-volatile memory NVM is memory which maintains its contents during power loss conditions. OOS out-of-service The status of a primary rate link when it is out of service. PBX private branch exchange A PBX is a private branch exchange within a company. PC personal computer PCB printed circuit board A specially manufactured board on which electronic components are mounted. 2902 MainStreet Technical Practices GL-5 May 2002 90-2906-01 Glossary PCM pulse code modulation PROM programmable read-only memory A programmable semiconductor memory device in which the contents cannot be modified. PSTN public switched telephone network PSTN is the worldwide voice telephone system. R2D signaling R2 digital signaling RAM random access memory The primary memory in a computer, RAM can be repeatedly read and overwritten. RAPID reserved alternate path with immediate diversion RAPID is a function that reserves an alternate path for a high priority path. If the primary path becomes unavailable due to a network problem, the network nodes automatically switch to the reserved path. RDL remote digital loopback RDS remote development system RI ring indicator RO read only ROM read only memory A semiconductor memory device that cannot be over-written. RTS request to send from V.24/RS-232 R/W read/write Rx receive RXD signal receive data signal SDLC synchronous data link control SDLC is a bit-oriented synchronous communications protocol developed by IBM. It typically operates in half-duplex mode and carries SNA traffic. SEEP serial electrically erasable PROM SEEP is the memory used to store and report product identity and other long-lasting information about hardware assembly. SELV safety extra low voltage SMAC state monitoring array controller A mechanism used for rapid detection of hardware state changes. GL-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 Glossary SNA systems network architecture SNA is IBM’s proprietary network architecture. It also refers to a class of networking protocols defined by IBM. SRM subrate multiplexer A device which allows data and compressed voice to be multiplexed together and put on a single DS0. SSU system synchronization unit The circuit which generates the system clocks (C4M, FP, C3M) from whatever master-clock source is selected. TS0 timeslot 0 The first timeslot in a CEPT frame. Timeslot zero can be used to carry CPSS messages. Tx transmit TXD signal transmit data signal UART universal asynchronous receiver transmitter A UART is an integrated circuit designed to perform character assembly/disassembly, and the conversion of parallel data into serial data for transmission over an asynchronous data channel. 2902 MainStreet Technical Practices GL-7 May 2002 90-2906-01 Glossary GL-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 Index Numerics A 2600 MainStreet series DTUs, 17-2 AC, powering up, 4-4 2700 MainStreet series DTUs, 17-2 access levels 2902 MainStreet description, 11-9 opening the unit, 5-2 examples, 11-10 physical components, 1-3 level 0, 11-9 product overview, 1-2 level 5, 11-9 2B1Q module levels 4 through 1, 11-9 circuit configuration, 17-2 passwords, 11-13 circuit identifier, 12-2 to define level 0 access, 11-13 circuit operating parameters, 17-3 to define levels 4 through 1, 11-12 clocking, 17-9 adapters control signals, 17-6 for RS-232 connections, 7-9 data structure, 17-7 to configure for RS-232 connections, 7-18 description, 17-2 AIS (all ones), Codirectional DCM, 20-4 device gender, 17-4 alarm clear time, 15-13 device mode, 17-3 alarm codes, 25-2 duplex method, 17-5 alarm connector, 1-6 loopbacks, 27-3 alarm declaration and clearing times multidrop data bridge, 17-12 to configure, 15-14 RTS/CTS delay, 17-5 alarm declare time, 15-13 signalling leads, 26-7 alarm queues super-rate configuration, 17-13 description, 25-2 to configure viewing, 25-4 RTS/CTS delay, 17-6 alarm times 8 kHz timing Codirectional DCM, 20-3 Codirectional DCM, 20-4 to configure for Codirectional DCM, 20-4 2902 MainStreet Technical Practices IN-1 May 2002 90-2906-01 Index alarms RS-232 DCM, 18-7 acknowledging, 25-6 V.35 DCM, 19-9 and alarm queues, 25-2 X.21 DCM, 19-9 and fault classes, 15-12 clocks (for system timing), 13-2 deleting, 25-7 Codirectional DCM external alarm function, 25-10 8 kHz timing, 20-4 logging, 25-9 alarm times, 20-3 reclassifying, 25-7 all ones AIS, 20-4 viewing alarm queues, 25-4 circuit identifier, 12-2 all ones AIS, Codirectional DCM, 20-4 circuit operating parameters, 20-2 ANS description, 20-2 and CPSS links, 13-10 loopbacks, 27-11 description, 13-2 module operating parameters, 20-2 antistatic precautions, 2-2 quality statistics, 28-7 trunk conditioning, 20-3 B command line (NMTI screen), 10-5 common channel signalling, 15-4 background diagnostics communications software, 11-3 circuit, 26-3 configuration database system, 26-3 and NVM, 30-2 busy-out, 26-6 backup, verify and restore, 30-2 bypass configuration (cross-connection), 23-3 resetting, 30-5 bypass, primary rate link, 32-2 connections AC power, 4-4 C adapters for RS-232 connections, 7-9 antistatic wrist strap, 2-2 CAS, 15-4 CPSS, 14-2 CCS, 15-4 cross-connections channel associated signalling, 15-4 types, 23-2 character length data devices, 7-2 2B1Q, 17-8 disconnecting circuits, 23-11 DNIC, 17-8 external alarm equipment, 9-2 RS-232 DCM, 18-6 ground, 4-2 V.35 DCM, 19-8 M34 cabling for V.35 connections, 7-20 X.21 DCM, 19-8 node management equipment, 8-2 chassis (description), 1-4 primary rate link, 6-3 circuit protecting, 23-5 fault signalling (E1), 16-2 securing slide assembly cables, 4-4 signalling type (E1), 16-2 connectors circuits external alarm equipment, 1-6 copying and adjusting configurations, 12-9 external device, 1-5 copying configurations, 12-8 pin and signal assignments naming a circuit, 12-8 primary rate, 6-2 quick configuration, 12-8 primary rate, 1-6 viewing circuit status, 12-9 serial port, 1-6 Circular alarm queue, 25-6 Control card class number description, 1-4 description, 13-7 installing modules, 5-2 to assign to a node, 13-8 LEDs (rear panel), 24-4 to assign to a timing source, 13-8 maintenance information, 26-10 clocking removing modules, 5-2 2B1Q, 17-9 resetting, 26-10 DNIC, 17-9 IN-2 2902 MainStreet Technical Practices 90-2906-01 May 2002 Index to install data position E1 G.703 or HDSL LIM and jumper HCM rate adaption, 22-8 blocks, 5-3 to configure E1 Optical LIM, 5-6 HCM rate adaption, 22-9 interface modules, 5-10 data structure personality modules, 5-11 2B1Q, 17-7 to remove DNIC, 17-7 E1 G.703 or HDSL LIM, 5-5 RS-232 DCM, 18-6 E1 Optical LIM, 5-9 V.35 DCM, 19-8 interface modules, 5-11 X.21 DCM, 19-8 personality modules, 5-12 database, 30-3 control signals backing up, 30-2 2B1Q, 17-6 resetting, 30-5 DNIC, 17-6 verifying backups, 30-2 RS-232 DCM, 18-5 DCM data circuit CPSS loopbacks, 27-11 channel connections, 14-2 debounce time description, 14-2 DNIC, 17-14 maintenance device gender CPSS grooming, 29-5 2B1Q, 17-4 routing information, 29-2 DNIC, 17-4 CPSS address, 11-7 RS-232 DCM, 18-3 CPSS grooming, 29-5 V.35 DCM, 19-4, 19-5, 19-6, 19-7 CPSS links X.21 DCM, 19-4, 19-5, 19-6, 19-7 and ANS, 13-10 device mode Craft Interface, 10-2, 11-3 2B1Q, 17-3 CRC4 statistics, 15-14, 28-3 DNIC, 17-3 cross-connections RS-232 DCM, 18-3 bypass configuration, 23-3 V.35 DCM, 19-4 disconnecting, 23-10 X.21 DCM, 19-4 drop and insert configuration, 23-2 diagnostics NMTI circuit display, 23-5 background diagnostics, 26-3 RAPID protection switching, 23-5 busy-out circuit, 26-6 simple, 23-2 directed diagnostics, 26-4 super-rate, 23-4 signalling leads, 26-7 to configure test descriptions, 26-2 protection switching, 23-9 viewing test display, 26-5 to connect diagnostics line (NMTI screen), 10-6 simple, 23-3 directed diagnostics, 26-4 super-rate, 23-4 disconnecting cross-connections to disconnect description, 23-10 all circuits, 23-11 distant fault class, 15-12 simple circuits, 23-11 DNIC module super-rate circuits, 23-11 circuit configuration, 17-2 types, 23-2 circuit identifier, 12-2 circuit operating parameters, 17-3 D clocking, 17-9 control signals, 17-6 data area (NMTI screen), 10-5 data structure, 17-7 data devices debounce time, 17-14 connecting to the node, 7-2 description, 17-2 device gender, 17-4 2902 MainStreet Technical Practices IN-3 May 2002 90-2906-01 Index device mode, 17-3 CAS, 15-4 duplex method, 17-5 CCS, 15-4 loopbacks, 27-6 E1 G.703 LIM, 1-5, 15-2 multidrop data bridge, 17-12 E1 HDSL LIMs, 1-5, 15-2 RTS/CTS delay, 17-5 E1 Optical LIM, 1-5, 15-2 signalling leads, 26-7 fault classes, 15-12 super-rate configuration, 17-13 network connectors, 15-3 to configure overview, 15-2 control signals, 17-7 statistics, 15-14 data structure, 17-8 to configure device gender, 17-4 alarm declaration and clearing times, device mode, 17-4 15-14 duplex method, 17-5 E1 framing format, 15-4 multidrop data bridge, 17-13, 18-10 fault classes, 15-13 RTS/CTS delay, 17-6, 18-4 network connectors, 15-3 super-rate speeds, 17-13 signal earthing (E1 G.703 LIMs), 15-5 transmit clock, 17-11 slave/master operation (HDSL and drop and insert configuration Optical LIMs), 15-6 (cross-connection), 23-2 statistics, 15-14 DTUs trunk conditioning, 15-11 and 2B1Q modules, 17-2 trunk conditioning, 15-7 and DNIC modules, 17-2 E1 Optical LIM loopbacks (2600 MainStreet series), 27-6 master/slave operation, 15-6 loopbacks (2700 MainStreet series), 27-3 to install, 5-6 duplex method to remove, 5-9 2B1Q, 17-5 earthing DNIC, 17-5 E1 signal, 15-4 empty module positions, 12-4 E EPROMs replacing, 5-12 E1 circuit to replace, 5-13 fault signalling, 16-2 error fault class, 15-12 signalling type, 16-2 event status LED, 24-2 to configure external alarm equipment E1 fault signalling, 16-3 connecting to node, 9-2 signalling type, 16-2 to connect for activating, 9-4 E1 framing format to connect for monitoring, 9-3 CAS, 15-4 external alarm function CCS, 15-4 description, 25-10 E1 G.703 LIM to configure, 25-11 signal earthing, 15-4 to install (module and jumper blocks), 5-3 F to remove, 5-5 E1 HDLS LIM failed fault class, 15-12 to install (module and jumper blocks), 5-3 failure threshold to remove, 5-5 description, 13-8 E1 HDSL LIMs to assign, 13-9 master/slave operation, 15-6 FAS statistics, 15-14, 28-3 E1 LIMs, 15-2 fault classes E1 modules and alarms, 15-12 alarm declaration and clearing, 15-13 to configure, 15-13 E1 framing format IN-4 2902 MainStreet Technical Practices 90-2906-01 May 2002 Index fault signalling I and protection switching, 23-6 E1 circuit, 16-2 installation format desktop unit in slide assembly in a rack, 3-3 E1 framing grounding requirements, 1-11 CAS, 15-4 power requirements, 1-10 CCS, 15-4 site selection, 1-9 frame fault class, 15-12 space requirements, 1-10 framing format tool and hardware requirements, 1-11 E1 (CAS), 15-4 unit, 3-2 E1 (CCS), 15-4 interface modules front panel 2B1Q, 17-2 LEDs, 24-2 Codirectional DCM, 20-2 full duplex DNIC, 17-2 RS-232 DCM, 18-4 general description, 1-5 fuse installing, 5-10 testing and replacing, 31-3 LEDs, 24-6 logical positions, 1-5, 12-2 G maintenance information, 26-10 personality module pin and signal grooming assignments, 7-3 CPSS, 29-5 physical positions, 1-5, 12-2 ground points removing, 5-11 EDG, 4-2 resetting a module, 26-10 protective earth, 4-2 RS-232, 18-2 Sig/GND, 4-2 to view module status information, 12-7 telecom safety earth, 4-2 V.35 DCM, 19-2 grounding requirements, 1-11 X.21 DCM, 19-2 grounding the unit, 4-2 interface speed group 1 one-way trunk conditioning, 15-9 HCM rate adaption, 22-6 group 2 one-way trunk conditioning, 15-10 setting super-rate speeds (X.21 and V.35 group 3 one-way trunk conditioning, 15-11 DCMs), 19-14 super-rate H for DNIC or 2B1Q, 17-13 X.21 or V.35 DCMs, 19-13 HCM rate adaption to configure description, 22-2 HCM rate adaption, 22-8 to configure inter-sector links, 13-10 data position, 22-9 intra-sector links, 13-10 HCM adaption, 22-3 interface speed, 22-8 J signalling, 22-5 transport bandwidth, 22-4, 22-5 J1 and J2 (personality modules) HDSL LIMs pin and signal assignments, 7-3 equipment loopback, 27-16 J11 (external alarm equipment) line loopback, 27-18 pin and signal assignment, 9-2 HDSL overview, 1-6 J3, J4, J5, J6, J7 and J8 (primary rate) header line (NMTI screen), 10-5 pin and signal assignments, 6-2 hop, 29-2 jumper blocks (for E1 G.703 or HDSL LIM), 5-3 2902 MainStreet Technical Practices IN-5 May 2002 90-2906-01 Index master/slave operation, 15-6 K HDSL and Optical LIMs, 15-6 keyboard buffer, 10-9 Modem pin and signal assignment, 8-2 L module circuits naming, 12-8 LEDs module positions colours, 24-2 configuring, 12-3 Control card (rear panel), 24-4 empty, 12-4 front panel, 24-2 logical, 12-2 interface modules, 24-6 naming, 12-8 locations, 24-2 physical, 12-2 startup sequence, 4-6 reserved, 12-4 level 0 access description, 11-9 to configure, 12-4 level 1 access description, 11-9 viewing status, 12-4 level 2 access description, 11-9 module status information level 3 access description, 11-9 viewing, 12-4 level 4 access description, 11-9 modules level 5 access description, 11-9 Control card LIM installation and removal, 5-2 installing, 5-3 naming a module position, 12-8 removing, 5-3 viewing status, 12-4 LIMs multidrop data bridge E1, 15-2 2B1Q, 17-12 line loopback, 27-17 DNIC, 17-12 links RS-232 DCM, 18-9 inter-sector, 13-10 V.35 DCM, 19-12 intra-sector, 13-10 lockout feature (NMTI), 10-2 N logging in to NMTI, 10-2 logging out of NMTI, 10-9 network configuration display, 13-12 logical module positions, 1-5, 12-2 network connections (physical), 6-2 loopbacks NMTI, 10-2 2B1Q module, 27-3 alarm functions, 10-7 data circuits (DCMs), 27-11 configuration functions, 10-6 DNIC module, 27-6 general functions, 10-8 DTU (2600 MainStreet series), 27-6 housekeeping functions, 10-6 DTU (2700 MainStreet series), 27-3 lockout feature, 10-2 indicators, 27-3 logging in, 10-2 line, 27-17 logging out, 10-9 overview, 27-2 main menu, 10-6 primary rate circuit, 27-13 maintenance functions, 10-7 primary rate link, 27-15 refreshing the display, 10-9 to remove a specific loopback, 27-3 screen display description, 10-4 to remove all loopbacks, 27-3 softkey menus, 10-7 types, 27-2 statistical functions, 10-7 NOC telephone number, 11-8 M node management (overview), 10-2 node management equipment M34 cabling (for V.35 DCM connections), 7-20 to connect to node, 8-3 MainStreetXpress 46020 Network Manager, node number, 11-7 10-2, 11-3 IN-6 2902 MainStreet Technical Practices 90-2906-01 May 2002 Index node parameters RS-232 adapters, 7-10 access levels, 11-9 V.35 connections baud rate, 11-4 DB25-to-M34 cables, 7-20 CPSS node identifier, 11-7 power connections, 4-4 date, 11-6 power LED, 24-2 device type, 11-2 power rails flow control, 11-5 measuring, 31-2 NOC telephone number, 11-8 power requirements, 1-10 node name, 11-7 power supply (description), 1-4 node number, 11-7 powering up passwords, 11-13 connections, 4-4 time, 11-6 LED sequence, 4-6 to view node information, 11-14 startup diagnostics, 4-6 NVM primary rate circuit loopbacks, 27-13 and configuration database, 30-2 primary rate connections, 6-2 resetting, 30-5 primary rate link bypass, 32-2 viewing information about, 30-5 primary rate link loopbacks, 27-15 primary rate modules O description, 1-5 installing and removing, 5-3 one-way trunk conditioning, 15-9 jumper blocks, 1-5 Optical LIM overview (description), 1-8 overview, 15-2 out of sync 1 LED, 24-2 printer, 11-2 out of sync 2 LED, 24-2 processor LED, 24-2 oversampling protecting connections HCM rate adaption, 22-8 description, 23-5 overspeed, 22-8 protection switching and fault signalling, 23-6 P to configure, 23-9 parity R 2B1Q, 17-8 DNIC, 17-8 rack-mounting RS-232 DCM, 18-7 desktop unit in a rack, 3-3 V.35 DCM, 19-9 desktop unit in a slide assembly, 3-3 X.21 DCM, 19-9 RAPID circuit protection, 23-5 passwords (for access levels), 11-13 rate adaption personality module HCM pin and signal assignment, 7-3 data position, 22-8 2B1Q, 7-8 description, 22-2 Codirectional DCM, 7-8 interface speed, 22-6 DNIC, 7-8 oversampling, 22-8 RS-232 DCM, 7-3 signalling, 22-5 V.35 DCM (type 1), 7-4 transport bandwidth, 22-3 V.35 DCM (type 2), 7-5 transport position, 22-5 X.21, 7-7 to configure personality modules HCM adaption, 22-3 installing, 5-11 HCM data position, 22-9 removing, 5-11 HCM interface speed, 22-8 pin and signal assignments HCM signalling, 22-5 external alarm connector, 9-2 HCM transport bandwidth, 22-4 personality modules, 7-3 HCM transport position, 22-5 primary rate connectors, 6-2 2902 MainStreet Technical Practices IN-7 May 2002 90-2906-01 Index transparent adaption, 21-3 S transparent transport bandwidth, 21-5 transparent transport position, 21-6 securing strap transparent to install, 5-10 description, 21-2 self-tests (startup), 4-6 transport bandwidth, 21-3 serial ports transport position, 21-5 baud rate, 11-4 rear panel description, 11-2 LEDs, 24-4 device type, 11-2 receive clock flow control, 11-5 RS-232 DCM, 18-8 to connect directly to CPSS, 14-3 X.21 DCM, 19-11 to connect indirectly to CPSS, 14-4 recovery condition signal earthing, 15-4 description, 13-9 signalling to configure, 13-10 HCM rate adaption, 22-5 repacking the shipment, 2-4 to configure reserved module positions HCM rate adaption, 22-5 and module position configuration, 12-4 signalling leads and super-rate speeds, 19-15 driving outgoing leads, 26-9 to configure, 19-17 maintenance functions, 26-7 resetting viewing, 26-8 configuration database, 30-5 signalling type Control card (node), 26-10 E1 circuit, 16-2 restoring from backup, 30-3 simple cross-connection routing information (CPSS), 29-2 description, 23-2 RS-232 DCM to connect, 23-3 circuit identifier, 12-2 to disconnect, 23-11 circuit operating parameters, 18-2 site selection, 1-9 clocking, 18-7 slide assembly control signals, 18-5 description, 3-3 data structure, 18-6 installing in a rack, 3-3 description, 18-2 securing cables, 4-4 device gender, 18-3 slide bracket, 3-3 device mode, 18-3 softkey area (NMTI screen), 10-6 full duplex, 18-4 softkey menus, 10-7 loopbacks, 27-11 software generic multidrop data bridge, 18-9 installing new generic, 5-12 receive clock, 18-8 stand-alone system timing, 13-2 RTS/CTS delay, 18-4 startup diagnostics, 4-6 to configure statistics clocking, 18-9 Codirectional DCM quality, 28-7 control signals, 18-6 CRC4, 28-3 data structure, 18-7 E1 types supported, 15-14 device gender, 18-4 FAS, 28-3 device mode, 18-3 synchronization, 28-2 RTS/CTS delay to configure E1 statistics type, 15-14 2B1Q, 17-5 stop bits DNIC, 17-5 2B1Q, 17-8 RS-232 DCM, 18-4 DNIC, 17-8 IN-8 2902 MainStreet Technical Practices 90-2906-01 May 2002 Index RS-232 DCM, 18-7 V.35 DCM, 19-10 V.35 DCM, 19-9 X.21 DCM, 19-10 X.21 DCM, 19-9 transmit shielding super-rate configuration E1 G.703 LIM, 15-4 2B1Q, 17-13 transparent rate adaption DNIC, 17-13 description, 21-2 V.35 DCM, 19-13 to configure, 21-3 X.21 DCM, 19-13 to configure transport bandwidth, 21-5, super-rate cross-connection 21-6 description, 23-4 transport bandwidth to connect, 23-4 HCM rate adaption, 22-3 to disconnect, 23-11 to configure super-rate interface speeds HCM rate adaption, 22-4 reserved module positions (X.21 and V.35 transparent rate adaption, 21-5 DCMs), 19-15 transparent rate adaption, 21-3 to reserve module positions, 19-17 transport position super-rate speeds HCM rate adaption, 22-5 setting interface speed (X.21 and V.35 to configure DCMs), 19-14 HCM rate adaption, 22-5 synchronization statistics, 28-2 transparent rate adaption, 21-6 synchronization types transparent rate adaption, 21-5 timing, 13-6 trunk conditioning, 15-7 to configure, 13-7 Codirectional DCM, 20-3 system status LED, 24-2 one-way system timing group 1, 15-9 ANS, 13-2 group 2, 15-10 configuration summary, 13-2, 13-3 group 3, 15-11 stand-alone, 13-2 overview, 15-9 to configure T for Codirectional DCM, 20-3 for E1 module, 15-11 Terminal two-way, 15-7 pin and signal assignment, 8-3 two-way trunk conditioning, 15-7 terminal emulation software, 11-3 timing (system), 13-2 U timing sources class number, 13-7 underspeed, 22-8 description, 13-3 unpacking the shipment, 2-2 enabling, 13-6 V failure, 13-4 failure threshold, 13-8 V.35 connections inter- and intra-sector links, 13-10 M34 cables recovery condition, 13-9 pin and signal assignments, 7-20 selecting, 13-6 V.35 DCM synchronization types, 13-6 circuit identifier, 12-2 to display, 13-4 circuit operating parameters, 19-2 transmit clock source clocking, 19-9 2B1Q, 17-9 data structure, 19-8 DNIC, 17-9 description, 19-2 RS-232 DCM, 18-8 2902 MainStreet Technical Practices IN-9 May 2002 90-2906-01 Index device gender, 19-4, 19-5, 19-6, 19-7 X device mode, 19-4 loopbacks, 27-11 X.21 DCM multidrop data bridge, 19-12 circuit identifier, 12-2 super-rate configuration, 19-13 circuit operating parameters, 19-2 to configure clocking, 19-9 clocking, 19-11 data structure, 19-8 control signals, 19-8 description, 19-2 data structure, 19-9 device gender, 19-4, 19-5, 19-6, 19-7 device gender, 19-5 device mode, 19-4 device mode, 19-4 loopbacks, 27-11 duplex method, 19-6 receive clock, 19-11 multidrop data bridge, 19-13 super-rate configuration, 19-13 RTS/CTS delay, 19-6 to configure super-rate speeds, 19-13 clocking, 19-11 visual indicators, 24-2 control signals, 19-8 VT100 terminal, 11-2 data structure, 19-9 device gender, 19-5 W device mode, 19-4 super-rate speeds, 19-13 wrist strap (antistatic), 2-2 IN-10 2902 MainStreet Technical Practices 90-2906-01 May 2002 © 2002 Alcatel. All rights reserved. 90-2906-01 95-1820-01-00-C