New Bridge 2902 Tech Manuel

Update to 2902 MainStreet Technical Practices Release 1.0 Issue 1

95-4676-01-00-A February 1999

Update Instructions and Update History2902 MainStreet Technical Practices Release 1.0

90-2906-01-B

Update instructions

This update lists changes to the 2902 MainStreet Technical Practices.

Chapter Reason for update Replace

1.1 Added information about the E1 HDSL LIM2. Pages 1.1-1 to 1.1-8.

3.1 Added information about the E1 HDSL LIM2. Pages 3.1-1 and 3.1-2.

3.3 Corrected Figure 3.3-3. Pages 3.3-1 and 3.3-2.

4.2 Corrected date and time information in section 4.2.2. Pages 4.2-5 and 4.2-6.

5.1 Added information about the E1 HDSL LIM2. Entire chapter.

8.2 Corrected Table 8.2-1 and Figure 8.2-2. Entire chapter.

8.3 Corrected Figure 8.3-3. Pages 8.3-9 and 8.3-10.

8.4 Added information about the E1 HDSL LIM2. Pages 8.4-17 to 8.4-20.

Index Added entries for the E1 HDSL LIM2. Pages IN-3 to IN-6.

Update history

Date Issue Part number of update Reason for update

February 1999 2 95-4676-01-00-A This update incorporated PTS fixes and documentation of the new E1 HDSL LIM2.

October 1997 1 95-1820-01-00-B Original release of 2902 MainStreet Technical Practices Release 1.0.

Please retain for your records.

2902 MainStreet Technical Practices 1.1 IntroductionNNP 95-1820-01-00-B Issue 2, February 1999

1. Pre-installation (200) 1.1-1

1.1 Introduction

This chapter introduces the 2902 MainStreet Multiservice NTU.

1.1.1 Product Overview

The 2902 MainStreet Multiservice NTU is a high-speed NTU for data devices. The 2902 MainStreet NTU 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 Multiservice NTU 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 HDSL and Optical LIMs allow the 2902 MainStreet NTU 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 HDSL, Optical, or another E1 G.703 LIM.

Figure 1.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-1: 2902 MainStreet Multiservice NTU

8827

2902 MainStreetNetwork Termination Unit

PowerEvent Status

System Status

ProcessorOut of Sync 1Out of Sync 2

1.1 Introduction 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

1.1-2 (200) 1. Pre-installation

The system uses customer-installed modules to connect to E1 lines and data devices. E1 lines connect to a 2902 MainStreet node through the following line interface modules:

• E1 G.703 LIM

• E1 HDSL LIM

• E1 HDSL LIM2

• E1 Optical LIM

Data devices connect to a 2902 MainStreet node through the following data interface modules:

• RS-232 DCM

• V.35 DCM

• X.21 DCM

• Codirectional DCM

• DNIC module

• 2B1Q module

1.1.2 Physical Components

The 2902 MainStreet system has three major physical components:

• chassis

• power supply

• Control card

Figure 1.1-2 identifies the components for the unit.



Figure 1.1-2: 2902 MainStreet Unit (Interior, Rear View)

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 power supply is a self-contained unit 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 multi-layered 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.1-3 shows the location of the modules.

9058

Powersupply

Protectiveearth

Powerswitch Fuse

holder

Powerreceptacle

Seven-segmentdisplay

LoopbackLEDs

Status LED

EDGand Sig/Gnd

Slot 1

Slot 2

(P1)

Primary rateinterfacemodules

Data interface modules

Control card

position (1)

Personalitymodules

Line-1Line-2

Modem

Terminal

Alarm

Rx-1Tx-1

Rx-2 Tx-2

Line-1

Slot 2

Slot 1

Line-2Modem Terminal

Rx-1Tx-1

Rx-2Tx-2

Alarm

Loop

Display

Status21U

O

IEDG Sig/Gnd

position (2)

P1P2

P2

P1

(P2)



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

Figure 1.1-3: Control Card Modules

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, labelled P1 and P2 in Figure 1.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.

8840

Personalitymodules

(Slot 2/Slot 1)

LIM(P1)

EPROMS

Interfacemodule

(position 2)

Interfacemodule

(position 1)

3 41 2

LIM(P2)



Data interface modules

There are locations for two data interface modules on the Control card, as shown in Figure 1.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 4.3 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.

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 labelled 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 labelled 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 labelled 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 labelled Modem and Terminal are RS-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 labelled 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.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 acheive a maximum reach of 3700 m with zero noise using 0.4 mm wire, or 2850 m 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.

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



Figure 1.1-4: HDSL Technology

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 that they do not provide the monitoring or bypass functions that are available on the E1 LIMs.

Figure 1.1-5 shows a typical application for E1 HDSL LIMs.

Figure 1.1-5: Typical E1 HDSL LIM or E1 HDSL LIM2 Application

Performance specifications

The E1 HDSL LIM and E1 HDSL LIM2 meet the performance specification for ETSI ETR 152.

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

HDSL loop 1

HDSL loop 2

E1interface

30 DS0s E1 E1

2.048Mb/s

2.048Mb/s

HDSLmaster

HDSLslave

E1interface

30 DS0s

1168 kb/s

1168 kb/s

7661

E1 HDSL LIMor E1 HDSL LIM2

3700 m (12 139 ft)0.4 mm wire, zero noise

Slave Master

E1

X.21/V.35

X.21/V.35

Videoconferencing

Ethernet LAN

Centrex/PBX

3600MainStreetBandwidthManager

Router

11868

2902MainStreet

NTU



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.1-6 shows the E1 Optical LIM in a point-to-point application. Figure 1.1-7 shows a feeder node application.

Figure 1.1-6: E1 Optical LIM Point-to-point Application

Figure 1.1-7: E1 Optical LIM Feeder Node Application

10450PBX

Video

Data

PBX

DNIC

X.21

Video

DataDNIC

X.21

E1G.703LIM(P2)

E1G.703LIM(P2)

E1Optical

LIM(P1)

E1Optical

LIM(P1)

2902 MainStreet NTU 2902 MainStreet NTU

15 km(9 mi)

Fibre cable

10451

PBX

Video

DataDNIC

X.21

E1G.703LIM(P2)

E1Optical

LIM(P1)

2902 MainStreet NTU

15 km(9 mi)

Fibre cable

Optical network

2902 MainStreet Technical Practices 3.1 Connecting to the NetworkNNP 95-1820-01-00-B Issue 2, February 1999

3. Physical Connections (200) 3.1-1

3.1 Connecting to the Network

This chapter describes connecting primary rate links to the network.

3.1.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 fibre 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 3.1-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 3.1-1: Primary Rate Connectors

10423

Line-1

Slot 2

Slot 1Line-2 Modem TerminalRx-1 Tx-1 Rx-2 Tx-2

FirstE1 link

SecondE1 link

Line-1First

E1 link

P1First E1 link

P2Second E1 link

Line-2SecondE1 link

Alarm

Loop

Display

Status

21U

O

I

P1 P2

EDG Sig/Gnd

Rx-1Tx-1

Rx-2Tx-2

3.1 Connecting to the Network 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

3.1-2 (200) 3. Physical Connections

Primary rate module pin and signal assignments

Figures 3.1-2 and 3.1-3 identify the RJ45 connector pin and signal assignments for the 120 Ω G.703 and HDSL LIMs respectively. Figure 3.1-4 identifies the BNC connector pin and signal assignments.

Figure 3.1-2: RJ45 Network Connectors (Line-1 and Line-2) for the 120 Ω G.703 LIM

Figure 3.1-3: RJ45 Network Connectors (Line-1 and Line-2) for the HDSL LIMs

Figure 3.1-4: BNC Network Connectors (Rx-1, Tx-1, Rx-2 and Tx-2)

nc = no connection

12345678

ncnc

ReceiveReceiveShieldTransmitTransmitShield

8847

nc = no connection

12345678

ncnc

Pair 1bPair 1ancPair 2bPair 2anc

10470

TX BNC(Tx-1 and Tx-2)

Transmit (+)

Transmit (-)RX BNC

(Rx-1 and Rx-2)

Receive (+)

Receive (-)

8849

2902 MainStreet Technical Practices 3.3 Connecting Node Management EquipmentNNP 95-1820-01-00-B Issue 2, February 1999

3. Physical Connections (200) 3.3-1

3.3 Connecting Node Management Equipment

This chapter describes connections for node management equipment.

3.3.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, labelled Modem and Terminal. Figure 3.3-1 identifies these connectors.

Figure 3.3-1: Serial Port Connectors

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 4.1 in Configuration.

Note

If you plan to manage the 2902 MainStreet system from a MainStreetXpress 46020 Network Manager, consult the network manager documentation for instructions on installing network management equipment.

10424

Line-1

Slot 2

Slot 1Line-2 Modem TerminalRx-1 Tx-1 Rx-2 Tx-2

TerminalModem

Alarm

Loop

Display

Status

21U

O

I

P1 P2

EDG Sig/Gnd

3.3 Connecting Node Management Equipment 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

3.3-2 (200) 3. Physical Connections

Modem connector pin and signal assignment

Figure 3.3-2 shows the pin and signal assignment of the Modem connector. The arrows indicate signal direction.

Figure 3.3-2: Pin and Signal Assignment for the Modem Connector

Terminal connector pin and signal assignment

Figure 3.3-3 shows the pin and signal assignment of the Terminal connector. The arrows indicate signal direction.

Figure 3.3-3: Pin and Signal Assignment for the Terminal Connector

*RS-232 signal ground

12345678

CTSRTSRXDTXDSGND*DTRDSR

8991

*RS-232 signal ground

12345678

not usednot usedRXDTXDSGND*not usednot used

8992

2902 MainStreet Technical Practices 4.2 Node ParametersNNP 95-1820-01-00-B Issue 2, February 1999

4. System Configuration (400) 4.2-5

To set the flow control

where * is the default

4.2.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 <dd-MMM-yyyy>; the hyphens must be entered. For example, January 9, 1999 is entered as <09-JAN-1999>.

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 <hh:mmA> or <hh:mmP>. 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 <A> or <P>, the system assumes an <A>.

SER_PORT_1 SER_PORT_2

FLOW_CTRL FLOW_CTRL

XON/XOFFNONE* DTRNONE* XON/XOFF

HOUSE

SK000468

4.2 Node Parameters 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

4.2-6 (400) 4. System Configuration

To set the date and time

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)

4.2.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 8.7 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 Newbridge 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.

DATE

<dd-MMM-yyyy> ↵

TIME

<hh:mmA> or <hh:mmP> ↵

HOUSE

SK000469

2902 MainStreet Technical Practices 5.1 E1 Module Operating ParametersNNP 95-1820-01-00-B Issue 2, February 1999

5. E1 Primary Rate Configuration (400) 5.1-1

5.1 E1 Module Operating Parameters

This chapter describes the operating parameters for the E1 primary rate modules, including:

• network connectors

• framing format

• signal earthing (E1 G.703 LIM only)

• master/slave operation (E1 HDSL and Optical LIMs only)

• trunk conditioning

• fault classes

• alarm declaration and clearing times

• statistics

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

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

5.1 E1 Module Operating Parameters 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

5.1-2 (400) 5. E1 Primary Rate Configuration

Figure 5.1-1: E1 G.703 LIM Display

E1 Module IDs

The 2902 MainStreet NMTI identifies E1 LIMs by the module IDs listed in Table 5.1-1. See section 8.3.7 for information about displaying module IDs in the NMTI.

Table 5.1-1: E1 Module IDs

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.

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

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-

LIM Module ID

E1 LIM (1) $22

E1 HDSL LIM $28

E1 HDSL LIM2 (2) $32

E1 Optical LIM $38



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 5.1.4 for more information on signal earthing.

To configure the network connectors for an E1 LIM

CONFIG — POSITION — <Pp> ↵ — OPTION — RJ45_CONN/BNC_CONN*

where

p is 1 or 2

* is the default

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

With CAS, timeslot 16 is used for channel associated signalling and is not user configurable. Timeslot 0 is used for framing. The rest of the timeslots are used for information. Table 5.1-1 shows the timeslot-to-circuit relationships.

Common channel signalling

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 signalling messages). Timeslot 0 is used for framing. The rest of the timeslots are labelled as in CAS. Table 5.1-2 shows the timeslot-to-circuit relationships.

In Table 5.1-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 signalling.



Table 5.1-2: CAS and CCS Timeslot-to-circuit Relationships

To configure E1 framing format

CONFIG — POSITION — <Pp> ↵ — OPTIONS — FRAME_TYPE — CCS/CAS*

where

p is 1 or 2

* is the default

The FRAME_TYPE softkey does not appear if any circuits are connected.

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

Transmit shielding can be configured for E1 G.703 LIM variants with 75 Ω termination impedance. 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.

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



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.

where

p is 1 or 2

* is the default

5.1.5 Master/Slave Operation (E1 HDSL and Optical LIMs only)

To establish a link, the E1 HDSL or Optical LIMs 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.

BNC_SHIELD

RX_EARTH*/RX_FLOAT TX_EARTH*/TX_FLOAT

CONFIG — POSITION — <Pp> ↵ — OPTIONS

SK000678



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 on software generic 82211-H0-00 or 82211-H0-01, enter:

where

p is 1 or 2

* is the default

For E1 HDSL LIM2s on software generic 82211-H0-10 or later, or for E1 HDSL LIMs or Optical LIMs on any software generic, enter:

where

p is 1 or 2

* is the default

5.1.6 Trunk Conditioning

All connections have an information component and a signalling component. When a fault occurs on an E1 link, trunk conditioning defines the type of signal transmitted on the information and signalling paths. Trunk conditioning can be defined for all outgoing transmissions.

BNC_SHIELD

RX_EARTH*/RX_FLOAT TX_EARTH*/TX_FLOAT


SK000678

MASTER*/SLAVE


SK000487



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 signalling paths are broken in both directions. Figure 5.1-2 illustrates how two-way trunk conditioning is applied to a typical connection.

Signalling path

Both the primary rate circuit and the connected circuit undergo fault signalling as configured for the primary rate circuit (see section 5.2.2).

For the primary rate circuit, the signalling 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 signalling is configured). For the connected circuit, the signalling 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 signalling, the signalling 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 signalling path of the primary rate circuit, it transmits idle signalling, then fault signalling 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 signalling path of the X.21 circuit, it transmits idle signalling, then fault signalling as configured for the X.21 circuit.

Figure 5.1-2: Two-way Trunk Conditioning

One-way trunk conditioning

When a link is configured for one-way trunk conditioning, the information path or the signalling 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.

8842

Information path

Signalling path

Primary ratecircuit

2902MainStreet

Connectedcircuit

Signalling path

Information path

Fault

2.5 s

SEIZEDor

IDLE

Signalling

Fault

Directionof transmission


All 1s(primary rate circuit)

All 0s(not primary rate circuit)

Information

All 1s

Information

SEIZEDor

IDLE

Signalling

Fault



Group 1 one-way trunk conditioning

Figure 5.1-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 signalling 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 signalling (depending on the fault signalling selected for the connected circuit).

Unlike two-way trunk conditioning, if the fault signalling is seized, a seized signalling code is transmitted without an idle signalling 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 signalling 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 5.1-3: One-way Trunk Conditioning (Group 1)


Figure 5.1-4 shows Group 2 one-way trunk conditioning. For Multiframe and Incoming TS16 AIS alarms, one-way trunk conditioning breaks only the signalling 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 signalling (depending on the fault signalling selected for the connected circuit).

8843

Information path

Signalling path

Primary ratecircuit

2902MainStreet

Connectedcircuit

Signalling path

Information path

Fault



Fault

Frozen

If primaryrate circuit

SEIZEDor

IDLEIf not primary

rate circuit

Signalling



Information



Unlike two-way trunk conditioning, if the fault signalling is seized, the seized signalling code is transmitted without the idle signalling 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 signalling being outputted.

Figure 5.1-4: One-way Trunk Conditioning (Group 2)


For Distant alarm and TS16 Distant alarm, one-way trunk conditioning does not result in the information path or the signalling 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.

To configure the type of trunk conditioning

This enables trunk conditioning for all primary link faults.

where p is 1 or 2

* is the default

You can select classes of alarms that cause trunk conditioning to be applied (see section 5.1.7).

Information path

Signalling path

Primary ratecircuit

2902MainStreet

Connectedcircuit

Signalling path

Information path



Fault

Frozen

If primaryrate circuit

SEIZEDor

IDLEIf not primary

rate circuit

Signalling

8844

Fault

Transmissionnot affected



Information

ONE_WAY/TWO_WAY*

CONFIG — POSITION — <Pp> ↵ — OPTIONS — MORE — TRUNK_COND

SK000488



To disable trunk conditioning for an E1 circuit

If you turn fault signalling 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 5.2.2 for more information on E1 circuit fault signalling.

CONFIG — CIRCUIT — <Pp-c> ↵ — FAULT_SIG — NONE

where

p is 1 or 2

c is 1 to 31

5.1.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 5.1-3 lists the four configurable fault classes.

Table 5.1-3: Fault Classes and Alarms

Fault Class Alarms Description Clearing

Frame Framing Alarm Incoming AIS Multiframe Alarm Incoming TS16 AIS

Includes alarms associated with frame alignment or multiframe alignment.

Cleared when frame alignment or multiframe alignment is regained.

Distant Distant Alarm TS16 Distant Alarm

Includes alarms that are received from the equipment at the far end of the primary rate link.

Cleared when the remote equipment is no longer transmitting the alarm.

Failed Failed State Includes only the Failed State alarm. This alarm is raised when 10 severely errored seconds in a row have occurred.

Cleared when 10 non-severely errored seconds have occurred in a row.

Error Framing (FAS) Err Rate Exceeded

Includes only the Framing Err Rate Exceeded alarm. It is raised when the FAS error rate exceeds approximately 10-3 for a period of 4 to 6 seconds.

Cleared when the FAS error rate is below approximately 4 x 10-4 for 9 to 11 seconds.



To configure fault classes

Softkeys with the suffix _OFF disable trunk conditioning for their fault class; those with the suffix _ON enable trunk conditioning.

where

p is 1 or 2

* is the default

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

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

FRAME_OFF/FRAME_ON*

ERROR_OFF/ ERROR_ON*

FAILED_OFF/FAILED_ON*

DIST_OFF/ DIST_ON*

CONFIG — POSITION — <Pp> ↵ — OPTIONS — MORE — TRUNK_COND

SK000489



To set the alarm declaration and clearing times

where

p is 1 or 2

n is 1 through 300, 1 equals 0.1 seconds

5.1.9 E1 Statistics

You can configure the primary rate link to collect FAS or CRC4 statistics. See chapter 8.5 in Maintenance for more information on E1 statistics.

To configure the statistics type

where

p is 1 or 2

* is the default

DECLARE

<n> ↵ <n> ↵

CLEAR

CONFIG — POSITION — <Pp> ↵ — OPTIONS — MORE — ALARM_TIME

SK000490

FAS_STATS*/CRC4_STATS


SK000491

2902 MainStreet Technical Practices 8.2 AlarmsNNP 95-1820-01-00-B Issue 2, February 1999

8. System Monitoring (500) 8.2-1

8.2 Alarms

This chapter describes alarms, including:

• viewing alarm queues

• acknowledging alarms in a queue

• deleting alarms from a queue

• reclassifying configurable alarms

• logging alarms

• setting external alarms

8.2.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 8.1.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 8.2.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 6.3.11 in Configuration for details.

8.2 Alarms 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

8.2-2 (500) 8. System Monitoring

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 8.2-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 Newbridge field service representatives. Subcodes and parameters that are useful to maintenance functions are given in the table.

Table 8.2-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 MainStreetXpress 46020 Network Manager 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 2.2-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 2.2-3 has failed.

E1 Framer Self Test Failed One of the E1 Framer loopback self-tests described in Table 2.2-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 2.2-3 has failed.



Interrupt Self Test Failed The SMAC interrupt self-test described in Table 2.2-3 has failed.

LIM position 1 failed The Loopback (LIM 1) self-test described in Table 2.2-3 has failed.

LIM position 2 failed The Loopback (LIM 2) self-test described in Table 2.2-3 has failed.

LIS Alarm* Loss of input signal on a Codirectional DCM circuit.

Module Dead A module has been marked as dead.

Module Failure (1) A module is either not responding to the system or it failed the start-up 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 TS16 AIS*

The E1 multiframe alignment has been lost.

NVM Error (1) The Control card has a problem in the non-volatile RAM. Record the alarm subcode and parameters, then run directed test #3 (see section 8.3.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 2.2-3 has failed.

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 2.2-3 has failed.

SEEP Self Test Failed The SEEP self-test described in Table 2.2-3 has failed.

Signalling Fault An over-active device has caused a signalling 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 Newbridge 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 Newbridge 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 2.2-3 has failed.




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

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

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 8.2-1 is an example showing four alarms in the Major/Prompt alarm queue. The column headings for the alarms are described in Table 8.2-2.

Timer Self Test Failed The 4 ms timer or 125 µs timer self-test described in Table 2.2-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 2.2-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.

Wrong/No Module Installed (2) The installed module and the configuration do not correspond or no module has been installed.




Figure 8.2-1: Alarm Queue Display Example

Table 8.2-2: Description of an Alarm in an Alarm Queue

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-

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

Code A brief description of the abnormal condition or significant event. A complete list of alarm codes and detailed descriptions are included in Table 8.2-1. Each alarm code has a unique Id number.

Subcode and Parameters

The alarm subcode and parameters, if any. Subcodes and parameters are used by Newbridge field service personnel only. However, some subcodes and parameters are relevant to maintenance operations, as detailed in Table 8.2-1.



To view an alarm queue

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

To acknowledge alarms

where alarm number is the number (in the # column) of the alarm you want to acknowledge

MAJ/PROMPT MINR/DEFER DIAG/INSTN

LATEREARLIER

ALARMS

SK000527


ACK_ALLACK

<alarm number> ↵

ALARMS

SK000528



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

To delete alarms

where alarm number is the number (in the # column) of the alarm you wish to delete

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

Figure 8.2-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 <Esc> before selecting CANCEL, QUIT, PAGE_UP or PAGE_DOWN.


DELETE_ALLDELETE

<alarm number> ↵

ALARMS

SK000529



Figure 8.2-2: Reclassifying a Configurable Alarm

Note

An alarm code cannot be reclassified if it has any entries in an alarm queue.

To reclassify an alarm

where alarm number is the number (in the # column) of the alarm code you wish to reclassify


# 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 Signalling 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-


ALARMS — CONFIG — <alarm number> ↵

SK000530



8.2.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 4.2.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 4.2.1).

To log alarms via CPSS

1. Establish CPSS communications over the network.

2. Enter:


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:


RMT_ON/RMT_OFF*

ALARMS — MORE — LOGGING

SK000531

MDM_ON/MDM_OFF*


SK000532



To log alarms locally

1. Connect a printer to a serial port and configure the serial port type for PRINTER.

2. Enter:


8.2.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 3.4 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 8.1.2 for information on system problems.

LCL_ON/LCL_OFF*


SK000533



To set the external alarm function


OPEN_CCT/CLOSED_CCT*ENABLE/DISABLE*

ALARMS — EXTNL_ALRM

SK000534

2902 MainStreet Technical Practices 8.3 System DiagnosticsNNP 95-1820-01-00-B Issue 2, February 1999


To change outgoing signalling leads

where

pp is 1 or 9, c is A or B

signal is the signalling lead you wish to change

signal state is 0 (off) or 1 (on)

8.3.7 Displaying Module and Control Card Maintenance Information

If you must contact your Newbridge 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 8.3-3. When applicable, the display also identifies:

• maintenance being performed on the module

• protecting or protected links

To view module information for maintenance purposes

MAINT — ON_MODULE — <Pp> or <pp> or <CTL> ↵

where

p is 1 or 2

pp is 1 or 9

<signal state> ↵

MAINT — ON_CIRCUIT — <pp-c> ↵ — SET_SIGNAL <signal> ↵

SK000540

8.3 System Diagnostics 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B


Figure 8.3-3: Module Information Display for Maintenance

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

To reset a module or the Control card

MAINT — ON_MODULE — <Pp> or <pp> or <CTL> ↵ — RESET_POSN

where

p is 1 or 2

pp is 1 or 9


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-

2902 MainStreet Technical Practices 8.4 LoopbacksNNP 95-1820-01-00-B Issue 2, February 1999


Figure 8.4-17: Equipment Loopback for E1 G.703 and Optical LIMs

HDSL LIMs

When an 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 8.4-18. The loopback occurs as close to the HDSL output as possible.

Figure 8.4-18: Equipment Loopback for HDSL LIMs

9116

2902 MainStreet

E1 G.703or

Optical LIM

Controlcard

E1 LIM

Controlcard

2902 MainStreet

HDSL LIMor

HDSL LIM2

11867

HDSLpair 1 MUX

Loop 1interface

Loop 2interface

HDSLpair 2

8.4 Loopbacks 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B


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 Optical LIMs

Figure 8.4-19 illustrates the line loopback for the E1 G.703 and 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.

Figure 8.4-19: Line Loopback for E1 G.703 and Optical LIMs

HDSL LIMs

An HDSL LIM loops the signal received from the HDSL line back to the network, and passes it through to the Control card (see Figure 8.4-20).

8863

2902 MainStreet

Primary rateinterface

Controlcard

DXDX

LIM

Primary rate line loopback

DX

LIM

2902 MainStreet Technical Practices 8.4 LoopbacksNNP 95-1820-01-00-B Issue 2, February 1999


Figure 8.4-20: Line Loopback for HDSL LIMs

To initiate a primary rate loopback

where p is 1 or 2

To remove a primary rate loopback

MAINT — ON_MODULE — <Pp> ↵ — UNDO_LPK

where p is 1 or 2

Controlcard

2902 MainStreet

HDSL LIMor

HDSL LIM2

11869

HDSLpair 1 MUX

Loop 1interface

Loop 2interface

HDSLpair 2

LINEEQUIPMENT

MAINT — ON_MODULE — <Pp> ↵ — LOOPBACK

SK000546

2902 MainStreet Technical Practices IndexNNP 95-1820-01-00-B Issue 2, February 1999

IN-3

CPSS linksand ANS, 4.4-10

Craft Interface, 4.1-1, 4.2-2CRC4 statistics, 5.1-13, 8.5-3cross-connections

bypass configuration, 7.1-3disconnecting, 7.1-11drop and insert configuration, 7.1-2NMTI circuit display, 7.1-5RAPID protection switching, 7.1-6simple, 7.1-2super-rate, 7.1-3to configure

protection switching, 7.1-10to connect

simple, 7.1-3super-rate, 7.1-4

to disconnectall circuits, 7.1-11simple circuits, 7.1-11super-rate circuits, 7.1-11

types, 7.1-1

D

data area (NMTI screen), 4.1-5data devices

connecting to the node, 3.2-1data position

HCM rate adaption, 6.6-8to configure

HCM rate adaption, 6.6-8data structure

2B1Q, 6.1-7DNIC, 6.1-7RS-232 DCM, 6.2-6V.35 DCM, 6.3-8X.21 DCM, 6.3-8

database 9.1-2backing up, 9.1-1resetting, 9.1-4verifying backups, 9.1-2

DCM data circuitloopbacks, 8.4-10

debounce timeDNIC, 6.1-15

device gender2B1Q, 6.1-4DNIC, 6.1-4RS-232 DCM, 6.2-3V.35 DCM, 6.3-4, 6.3-5, 6.3-6X.21 DCM, 6.3-4, 6.3-5, 6.3-6

device mode2B1Q, 6.1-3DNIC, 6.1-3RS-232 DCM, 6.2-2V.35 DCM, 6.3-3X.21 DCM, 6.3-3

diagnosticsbackground diagnostics, 8.3-3busy-out circuit, 8.3-6directed diagnostics, 8.3-4signalling leads, 8.3-7test descriptions, 8.3-1viewing test display, 8.3-5

diagnostics line (NMTI screen), 4.1-5directed diagnostics, 8.3-4disconnecting cross-connections

description, 7.1-11distant fault class, 5.1-11DNIC module

circuit configuration, 6.1-2circuit identifier, 4.3-1circuit operating parameters, 6.1-2clocking, 6.1-9control signals, 6.1-6data structure, 6.1-7debounce time, 6.1-15description, 6.1-1device gender, 6.1-4device mode, 6.1-3duplex method, 6.1-4loopbacks, 8.4-6multidrop data bridge, 6.1-12RTS/CTS delay, 6.1-5signalling leads, 8.3-7super-rate configuration, 6.1-14to configure

control signals, 6.1-7data structure, 6.1-9device gender, 6.1-4device mode, 6.1-3duplex method, 6.1-5multidrop data bridge, 6.1-13, 6.2-10RTS/CTS delay, 6.1-5, 6.2-4super-rate speeds, 6.1-14transmit clock, 6.1-12

drop and insert configuration (cross-connection), 7.1-2

DTUsand 2B1Q modules, 6.1-1and DNIC modules, 6.1-1loopbacks (2600 MainStreet series), 8.4-6loopbacks (2700 MainStreet series), 8.4-3

Index 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

IN-4

duplex method2B1Q, 6.1-4DNIC, 6.1-4

E

E1 circuitfault signalling, 5.2-2signalling type, 5.2-1to configure

E1 fault signalling, 5.2-2signalling type, 5.2-1

E1 framing formatCAS, 5.1-3CCS, 5.1-3

E1 G.703 LIMinstalling, 2.3-3removing, 2.3-4signal earthing, 5.1-4

E1 HDSL LIMsinstalling, 2.3-3master/slave operation, 5.1-5removing, 2.3-4

E1 LIMs, 5.1-1E1 modules

alarm declaration and clearing, 5.1-12E1 framing format

CAS, 5.1-3CCS, 5.1-3

E1 G.703 LIM, 1.1-4, 5.1-1E1 HDSL LIMs, 1.1-4, 5.1-1E1 Optical LIM, 1.1-4, 5.1-1fault classes, 5.1-11network connectors, 5.1-2overview, 5.1-1statistics, 5.1-13to configure

alarm declaration and clearing times, 5.1-13

E1 framing format, 5.1-4fault classes, 5.1-12network connectors, 5.1-3signal earthing (E1 G.703 LIMs), 5.1-5slave/master operation (HDSL and

Optical LIMs), 5.1-6statistics, 5.1-13trunk conditioning, 5.1-10

trunk conditioning, 5.1-6

E1 Optical LIMinstalling, 2.3-4master/slave operation, 5.1-5removing, 2.3-8

earthed signal lines, 5.1-4earthing

E1 signal, 5.1-4empty module positions, 4.3-3EPROMs

replacing, 2.3-12to replace, 2.3-13

equipment loopback, 8.4-16error fault class, 5.1-11event status LED, 8.1-2external alarm equipment

connecting to node, 3.4-1to connect for activating, 3.4-3to connect for monitoring, 3.4-3

external alarm functiondescription, 8.2-10to configure, 8.2-11

F

failed fault class, 5.1-11failure threshold

description, 4.4-8to assign, 4.4-8

FAS statistics, 5.1-13, 8.5-3fault classes

and alarms, 5.1-11to configure, 5.1-12

fault signallingand protection switching, 7.1-7E1 circuit, 5.2-2

floating signal lines, 5.1-4format

E1 framingCAS, 5.1-3CCS, 5.1-3

frame fault class, 5.1-11framing format

E1 (CAS), 5.1-3E1 (CCS), 5.1-3

front panelLEDs, 8.1-2

full duplexRS-232 DCM, 6.2-4

fusetesting and replacing, 9.2-3

2902 MainStreet Technical Practices IndexNNP 95-1820-01-00-B Issue 2, February 1999

IN-5

G

groomingCPSS, 8.6-5

ground pointsEDG, 2.2-1protective earth, 2.2-1Sig/GND, 2.2-1telecom safety earth, 2.2-1

grounding requirements, 1.1-11grounding the unit, 2.2-2group 1 one-way trunk conditioning, 5.1-8group 2 one-way trunk conditioning, 5.1-9group 3 one-way trunk conditioning, 5.1-10

H

HCM rate adaptiondescription, 6.6-1to configure

data position, 6.6-8HCM adaption, 6.6-3interface speed, 6.6-7signalling, 6.6-5transport bandwidth, 6.6-4, 6.6-5

HDSL LIMsequipment loopback, 8.4-17line loopback, 8.4-18

HDSL overview, 1.1-6header line (NMTI screen), 4.1-4hop, 8.6-1

I

installationdesktop unit in slide assembly in a rack,

2.1-2grounding requirements, 1.1-11power requirements, 1.1-11site selection, 1.1-10space requirements, 1.1-11tool and hardware requirements, 1.1-13unit, 2.1-1

interface modules2B1Q, 6.1-1Codirectional DCM, 6.4-1DNIC, 6.1-1general description, 1.1-5installing, 2.3-9LEDs, 8.1-6logical positions, 1.1-5, 4.3-1maintenance information, 8.3-9

personality module pin and signal assignments, 3.2-2

physical positions, 1.1-5, 4.3-1removing, 2.3-10resetting a module, 8.3-10RS-232, 6.2-1to view module status information, 4.3-6V.35 DCM, 6.3-1X.21 DCM, 6.3-1

interface speedHCM rate adaption, 6.6-6setting super-rate speeds (X.21 and V.35

DCMs) 6.3-14super-rate

for DNIC or 2B1Q, 6.1-14X.21 or V.35 DCMs, 6.3-13

to configureHCM rate adaption, 6.6-7

inter-sector links, 4.4-10intra-sector links, 4.4-10

J

J1 and J2 (personality modules)pin and signal assignments, 3.2-2

J11 (external alarm equipment)pin and signal assignment, 3.4-2

J3, J4, J5, J6, J7 and J8 (primary rate)pin and signal assignments, 3.1-2

K

keyboard buffer, 4.1-8

L

LEDscolours, 8.1-1Control card (rear panel), 8.1-4front panel, 8.1-2interface modules, 8.1-6locations, 8.1-1start-up sequence, 2.2-6

level 0 access description, 4.2-9level 1 access description, 4.2-8level 2 access description, 4.2-8level 3 access description, 4.2-8level 4 access description, 4.2-8level 5 access description, 4.2-8LIMs

E1, 5.1-1installing, 2.3-3removing, 2.3-3

Index 2902 MainStreet Technical PracticesIssue 2, February 1999 NNP 95-1820-01-00-B

IN-6

line loopback, 8.4-18links

inter-sector, 4.4-10intra-sector, 4.4-10

lockout feature (NMTI), 4.1-2logging in to NMTI, 4.1-2logging out of NMTI, 4.1-9logical module positions, 1.1-5, 4.3-1loopbacks

2B1Q module, 8.4-3data circuits (DCMs), 8.4-10DNIC module, 8.4-6DTU (2600 MainStreet series), 8.4-6DTU (2700 MainStreet series), 8.4-3equipment, 8.4-16indicators, 8.4-3line, 8.4-18overview, 8.4-1primary rate circuit, 8.4-14primary rate link, 8.4-16to remove a specific loopback, 8.4-3to remove all loopbacks, 8.4-3types, 8.4-2

M

M34 cabling (for V.35 DCM connections), 3.2-21

MainStreetXpress 46020 Network Manager, 4.1-1, 4.2-2

master/slave operationHDSL and Optical LIMs, 5.1-5

master/slave operation, 5.1-5Modem

pin and signal assignment, 3.3-2module circuits

naming, 4.3-7module positions

configuring, 4.3-3empty, 4.3-3logical, 4.3-1naming, 4.3-7physical, 4.3-1reserved, 4.3-3to configure, 4.3-4viewing status, 4.3-4

module status informationviewing, 4.3-4

modulesControl card

installation and removal, 2.3-1naming a module position, 4.3-7viewing status, 4.3-4

multidrop data bridge2B1Q, 6.1-12DNIC, 6.1-12RS-232 DCM, 6.2-9V.35 DCM, 6.3-11

N

network configuration display, 4.4-12network connections (physical), 3.1-1NMTI

alarm functions, 4.1-6configuration functions, 4.1-5general functions, 4.1-7housekeeping functions, 4.1-6lockout feature, 4.1-2logging in, 4.1-2logging out, 4.1-9main menu, 4.1-5maintenance functions, 4.1-6refreshing the display, 4.1-8screen display description, 4.1-4softkey menus, 4.1-7statistical functions, 4.1-6

NMTI, 4.1-1NOC telephone number, 4.2-7node management (overview), 4.1-1node management equipment

to connect to node, 3.3-3node number, 4.2-6node parameters

access levels, 4.2-8baud rate, 4.2-3CPSS node identifier, 4.2-6date 4.2-5device type, 4.2-1flow control, 4.2-4NOC telephone number, 4.2-7node name, 4.2-6node number, 4.2-6passwords, 4.2-12time, 4.2-5to view node information, 4.2-13

NVMand configuration database, 9.1-1resetting, 9.1-4viewing information about, 9.1-4

New Bridge 2902 Tech Manuel

Documents

Transcript of New Bridge 2902 Tech Manuel