User Guide

ManualsBrandsLucent Technologies ManualsOtherR5SI

2531

DEFINITY Enterprise Communications Server Release 5

Maintenance and Test for R5vs/si

555-230-123

Issue 1

April 1997

Maintenance Object Repair Procedures

Page 10-1597UDS1-BD (UDS1 Interface Circuit Pack)

The DS1 Board Loopback (BLB) Test causes a loopback at the TN464F DS1

board edge and tests DS1 board internal circuitry.

The test is destructive and can only be initiated by a system technician

demanded

test ds1-loop PCSS ds1/csu-loopback-tests

command.

All trunks or ports on the UDS1 Interface circuit pack must be busied out via the

system technician busyout board command before running the BLB Test.

When the BLB Test is initiated, maintenance software sends an appropriate

message to the TN464F UDS1 Interface circuit pack to start the test. The board

will set up the BLB loopback, transmit a test pattern, and verify that the pattern is

received unaltered through the loopback. If the transmitted and received pattern

is different, the test fails.

When the test is complete, all trunks or ports on the TN464F UDS1 Interface

circuit pack are restored to the in-service state after the release board command

is entered.

Table 10-469. TEST #1209 DS1 Board Loopback Test

Error

Code

Test

Result Description/ Recommendation

ABORT Internal System Error

1. Retry the

test ds1-loop PCSS

ds1/csu-loopback-tests

command at 1-minute

intervals a maximum of 5 times.

2. If the test continues to abort, escalate the problem.

1005 ABORT DS1 Board Loopback Test cannot be executed in the

current configuration. To run this, the TN464F or later

suffix UDS1 must be administered for 24-channel

operation. The "Bit Rate" field on the DS1 circuit pack

administration form must be set to "1.544" for 24-channel

operation.

1015 ABORT Ports on the UDS1 Interface circuit pack have not been

busied out to out-of-service.

1. Enter the busyout board PCSS command to put all

trunks or ports of the UDS1 Interface circuit pack

into the out-of-service state.

2. Retry the command.

3. If the test continues to abort, escalate the problem.

Continued on next page