
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1146PDATA-PT (Packet Data Line Port)
9
Testing the System Port Pool
This section describes a method for isolating a bad system port when its location
is not known. A pool of system ports is used to service the set of application
features listed above. The system supports a maximum of 10 system ports. Since
each Data Line Circuit pack provides 8 ports and each PDATA provides 12 ports,
2 Data Line Circuit packs and one PDATA Circuit pack are required if all 10
system ports are to be administered. If a link failed due to a faulty system port
and that port is not currently connected to the feature, you will need to test the
entire pool to isolate the bad system port. Follow these steps to isolate a bad port
or exonerate the pool of system ports.
1. Enter
list data-module
and record the extension for each system port.
Note:
list data-module name
option can be used to match on the name of
the system ports if they are all named similarly.
2. For each system-port enter
display data-module ext
to find the Data Line
(DAT-LINE) and PDATA ports administered. Each system port has a single
extension that applies to both the Data Line and PDATA port. For historical
reasons the PDATA is considered the
associated port
.
3. Check each port for alarms and errors using
display alarms
and
display
errors
.
4. Check for SYS-LINK error or alarms for SAP-type links using
Display
alarms
and
errors
.
5. Follow the repair procedures for any ports with errors.
Identifying Components of an Application Link
Use this procedure to locate the maintenance objects that make up a given
application link. You can then follow the repair procedures for each MO. In the
steps given below all the MOs in a link are located before any ports are tested.
Problems with the application adjunct links are reported in two ways:
■ The data application experiences problems.
■ Errors or alarms are logged against a port or extension.