Avaya DEFINITY Server CSI, Руководство по обслуживанию, Страница: 151 / 1930

Unusual ATM trouble conditions
Issue 5 October 2002
151
555-233-119
Unusual ATM trouble conditions
There are a few failure modes in the Avaya Definity Server CSI/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 the Avaya
Definity Server CSI and the A500 look pretty good. This section documents some
hints and clues that may help diagnose the following failure modes:
■
Incorrectly typed or omitted 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
Incorrectly typed or omitted EPN Route or End
System Identifier (A500)
Symptoms
Talk paths are one-way, from the PPN to the EPN: you can hear tones from the
PPN end station to the EPN end station but not vice versa. Because the signaling
channels are bidirectional virtual circuits (VCs) established from the PPN to the
EPN, these can be routed correctly and come up just fine. Talk paths are two
unidirectional virtual circuits, so a single call has one VC from the PPN to the EPN
(which is routed correctly) and one VC 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
1. Correct the ATM address translations in the A500.