Avaya S8700 Series, Maintenance Manual

Page: 132 / 2618

Alarms, Errors, and Troubleshooting
555-233-143 4-58 Issue 1 May 2002
Unusual ATM Trouble Conditions
There are a few failure modes in the S8700 Multi-Connect/A500 combination that
are particularly difficult to diagnose. One example might be that you can’t make a
completely successful call, even though most indications from S8700
Multi-Connect and the A500 look pretty good. This section documents some hints
and clues that may help diagnose the following failure modes:
■
Incorrect EPN Route or End System Identifier (A500)
■
Swapped Routes, End System Identifiers, or Fiber between a PPN and an
EPN
■
Swapped Routes, End System Identifiers, or Fiber between A and B side
TN230Xs on an EPN
■
Swapped Routes, End System Identifiers, or Fiber between two EPNs
Incorrect EPN Route or End System Identifier
(A500)
Symptoms
One-way talk paths from the PPN to an EPN. You can hear tones from the PPN’s
end station to an EPN’s end station, but not vice versa. Since a signaling channel
is a bidirectional VC established from the PPN to an EPN, these can be routed
correctly and come up just fine. However, a single call’s talk path consists of two
unidirectional VCs — one from the PPN to an EPN (which is routed correctly) and
another from the EPN to the PPN (which cannot be routed).
Diagnostics
1. At the A500 use the show signaling routes or show signaling esi
command(s) as appropriate to check the ATM addresses.
2. Use show signaling stats port q93b on the EPN port and look for cause
code 3 (
No route to destination
).
Action
Correct the ATM address translations in the A500.