Lucent Technologies Release 7 User Manual
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1212
PGATE-PT (Packet Gateway Port)
9
Identifying Maintenance Objects That Make Up a
Link
Link
When the location of the port and the channel number of an X.25 link is known,
the status sys-link command can be used to identify all of the components in
the path traveled by the link. Refer to the SYS-LINK section in this chapter for
more guidance in troubleshooting links.
the status sys-link command can be used to identify all of the components in
the path traveled by the link. Refer to the SYS-LINK section in this chapter for
more guidance in troubleshooting links.
Service problems may be reported in several different ways. Generally a problem
will be associated with a local adjunct, an alarmed link that involves hop
channels, or an alarmed port or trunk. The following procedures show how to
locate components of a link starting with:
will be associated with a local adjunct, an alarmed link that involves hop
channels, or an alarmed port or trunk. The following procedures show how to
locate components of a link starting with:
— The adjunct or DCS link name
— An associated hop channel number
— A port or trunk
Once the MOs making up the link are known, inspect the alarm and error logs or
run tests for each maintenance object located on a suspect link. These
procedures do not include isolating problems located on adjuncts or other
switches. The steps sometimes require logins on different switches or adjuncts.
In this discussion, the term machine refers to a switch or an adjunct.
run tests for each maintenance object located on a suspect link. These
procedures do not include isolating problems located on adjuncts or other
switches. The steps sometimes require logins on different switches or adjuncts.
In this discussion, the term machine refers to a switch or an adjunct.
The packet interface (PKT-INT), packet bus (PKT-BUS), and TDM-BUS are not
covered by these procedures because they are part of the fabric for the
connections. These components should be tested first if they are alarmed or
reporting errors.
covered by these procedures because they are part of the fabric for the
connections. These components should be tested first if they are alarmed or
reporting errors.
Tracing a Link to a Given Adjunct or DCS Link
1. display adjunct-names
Locate and record the adjunct name that was reported and the application
type. If the problem is with DCS this step can be ignored. DCS will
probably be called DCS.
type. If the problem is with DCS this step can be ignored. DCS will
probably be called DCS.
2. display communications-interface processor-channels
■
Find the row with the application name found in the previous step.
The application name if it is listed will be in the identification field.
The application name if it is listed will be in the identification field.
■
Record the processor-channel number, application, interface link
and channel, adjunct name and machine ID. For the message
server adjunct there may be more than one processor link.
and channel, adjunct name and machine ID. For the message
server adjunct there may be more than one processor link.
3. display communications-interface links
■
Find the line that has the link found in the previous step.