Avaya Definity SI, Maintenance Manual, Page: 184 / 2968

Routine Maintenance Procedures
555-233-123 5-80 Issue 4 May 2002
a. If an A500 port to which a DEFINITY port network is attached is not
listed in this display, it is likely that the port was administered
incorrectly as having no UNI signaling (admin link command).
Ensure that fields listed have the values indicated below.
2. If the A500 was administered using hard-coded PNNI routes to identify
each endpoint, enter show signaling routes on the A500 console. Screen
5-18 shows the screen output.
Screen 5-18. Screen output from the show signaling routes command
Check that the
Address
field (administered using admin signaling route
add) matches those administered in DEFINITY.
3. If the A500 was administered using End System Identifiers, enter show
signaling esi on the A500 console. Screen 5-19 on page 5-81 shows the
output.
Field Value
IntType Network
If
User
, links will not come up between the PPN and the
EPN.
Signaling UNI3.1
If it is
UNI3.0
, links will not come up between the PPN
and the EPN.
ILMI
Preferred value of is
No
, however this alone does not
prevent links from coming up between the PPN and an
EPN.
SAP State
May or may not be
UP
. Their values depend on more than
just whether the port was marked as UP. (See highlighted
data for SAP State in
Screen 5-17 on page 5-79 .)
A500:show signaling routes
Number of Local Static Routes Allowed: 30
Current number of Local Static Routes: 2
Address: 47.00.05.80.ff.e1.00.00.00.f2.07.2a.01.00.00.00.00.00.00.00
mask:152 cost: 0 node:self port:A1.2 state:UP
Address: 47.00.05.80.ff.e1.00.00.00.f2.07.1b.02.00.00.00.00.00.00.00
mask:152 cost: 0 node:self port:A1.1 state:UP