Lucent Technologies R5SI User Manual
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-1059
PI-LINK (Processor Interface Link)
10
When the data module fails to respond to the EIA interface (query
request) the AUX_Data is set to 41. This may indicate problems
with the data module or connection to the data module. Other
errors specific to the data module may also be logged if this is the
case.
request) the AUX_Data is set to 41. This may indicate problems
with the data module or connection to the data module. Other
errors specific to the data module may also be logged if this is the
case.
j. TN765 PI-BD determined that the ISDN link went down. Check
connectivity with the other end. Busyout and then release the link to
recover. Occurs if DS1 maintenance detected a problem or the remote
end is busied out or is down. This also occurs if the ISDN link is unstable
or if there is excessive noise on the line. See the "Link Recovery" section.
recover. Occurs if DS1 maintenance detected a problem or the remote
end is busied out or is down. This also occurs if the ISDN link is unstable
or if there is excessive noise on the line. See the "Link Recovery" section.
k. Excessive LAPD (link-access procedure on the D-channel) invalid frame
errors. Could be a noisy line or problems with the TN765 Processor
Interface circuit pack. Also check DS1-BD Maintenance documentation.
See the "Link Recovery" section.
Interface circuit pack. Also check DS1-BD Maintenance documentation.
See the "Link Recovery" section.
l. Occurs 90 seconds after a 2817 Error Code if link does not recover. At this
time, all ISDN trunks associated with this link are put into a maintenance
far-end state (see ISDN-TRK for details). See the "Link Recovery" section.
far-end state (see ISDN-TRK for details). See the "Link Recovery" section.
m. The application level process associated with the link has failed to
establish a data connection with the far end. This problem prevents data
from being processed. The condition may exist even if the link is in a data
transfer state. Busyout, and release the link to restart it. This is not a
Processor Interface hardware problem.
from being processed. The condition may exist even if the link is in a data
transfer state. Busyout, and release the link to restart it. This is not a
Processor Interface hardware problem.
Aux values of concern; any others can be ignored.
n. Excessive (over threshold) HDLC transmit or receive error rates were
reported. Aux Data is the HDLC error rate reported. See the Link Recovery
section for troubleshooting this problem
section for troubleshooting this problem
Link Recovery
This section describes the general procedure to take to recover from link errors
and alarms. Refer to the "Troubleshooting ISDN-PRI Problems" section in
and alarms. Refer to the "Troubleshooting ISDN-PRI Problems" section in
, before proceeding with this "Link
Recovery" strategy.
1. Determine the link status using the
status link
command. If the link status
is "in-service" and (for X.25 links) all the pairs of processor channels are
complete under "LOCAL/REMOTE PROCESSOR CHANNELS" (that is,
every "/" is followed by a processor channel number, not a blank), then the
link is operating correctly and no further action should be taken. If the link
complete under "LOCAL/REMOTE PROCESSOR CHANNELS" (that is,
every "/" is followed by a processor channel number, not a blank), then the
link is operating correctly and no further action should be taken. If the link
433
OCM application did not start correctly. Reboot the
OCM adjunct.
OCM adjunct.
435
Application level process could not connect to session
layer process.
layer process.