DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1215PGATE-PT (Packet Gateway Port)
9
If the destination number is a loc al extension, then it is probabl y a
local data-module. If the num ber is remote or the word "external",
look at the comment field for an ind ication of the data-module’ s
extension or administered conne ction. More information on the
local extension can be ob tained by running display data-module
extension.
3. display communications-interface processor-channels
a. Find the row with the link number found in the p revious step.
b. Record the processor-c hannel number, appl ication, interface link
and channel, adjunc t name and machine ID. For the Message
Server Adjunct there can be more than o ne link.
4. display communications-interface hop-channels
a. Check if the link and proc essor channel found in the previous steps
is listed in this form. If it isn’t, then the major p ieces of the link on
this switch have been loc ated. If the link is connected to another
link, copy down all the info rmation for that hop-channel. With the
link and channel that are c onnected, repeat step s 2 - 4. This should
be repeated until there are no more links that are c onnected to any
of the links of concern.
b. For each extension located run display data-module ext to find the
port and the board . The port and board should then be tested to
find out if this MO is having p roblems. The repair section for eac h
MO should be consulted to understand and fix the problem.
c. For each TAC located, run display trunk-group tac tac# to find out
the trunk group. The trunk group should then be tested using test
trunk-group E4trunk number. The repair section should be
consulted to understand and fix problems found for an MO.
X.25 Protocol Errors
All of the X.25 port errors are generated as p art of error procedures spec ified by
the X.25 protocol. The reader is referred to the X.25 spec ification for more
detailed explanation of these errors and their implications. These errors are
logged as a result of errors d etected by the far end and received b y the port in
X.25 packets, and as a result of errors detec ted by the near end and sent by the
port in X.25 packets to the far end .
All of these errors are conveyed in three typ es of X.25 packets:
■Restart Request (Indication) Packets
■Reset Request (Indication) Packets
Restart packets cause reinitialization of the X.25 packet layer (Level 3) causing
all links to be reset which are associat ed with the X.25 link. These packets are
sent when the packet layer is first initiali zed or when certain errors are detec ted.