Lucent Technologies R5SI Computer Hardware User Manual


  Open as PDF
of 2643
 
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-776ISDN-LNK (ISDN-PRI Signaling Link Port)
10
NPE Crosstalk Test (#6)
The NPE Crosstalk Test verifies that this port’s NPE channel talks on the selected
time slot and never crosses over to time slots reserved for other connections. If
the NPE is not working correctly, one-way and noisy connections may be
observed. This test is usually only part of a port’s Long Test Sequence and takes
about 20 to 30 seconds to complete. This test runs only if the Processor Interface
link corresponding to this ISDN-LNK MO is busied out by system technician. The
Processor Interface link number can be determined from the
Communication-Interface Links form.
1. D = Destructive; ND = Nondestructive
Table 10-217. TEST #6 NPE Crosstalk Test
Error
Code
Test
Result Description/ Recommendation
ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1000 ABORT System resources for this test are not available. The ISDN-PRI link
may be up and servicing calls. First obtain the ISDN-PRI link number
(lnk-no) from the Communication-Interface Links form by issuing the
display communication-interfaces links command. Then,
determine the status of the ISDN-PRI link via the status link lnk-no
command. If the link is in-service, this test aborts. Therefore, to run
this test, the link must be busied out. No new ISDN-PRI calls can be
made while the link is in the busied-out state.
1. If the test must be run, busyout the link.
2. Retry the command.
1001 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1002 ABORT The system could not allocate time slots for the test. The system may
be under heavy traffic conditions or it may have time slots
out-of-service due to TDM-BUS errors. Refer to TDM-BUS (TDM Bus)
Maintenance to diagnose any active TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy
traffic, repeat the test at 1-minute intervals a maximum of 5 times.
Continued on next page