DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-100Packet Bus Fault Isolation and Repair
5
j. The answer is yes if any of the following apply:
■ The TN771D in standalone mode indicates any faulty leads.
■ Test #572 in the PKT-BUS test sequence fails.
■ The
status port-network P
display indicates that faulty leads are
present and the TN771D in the port network is known to be
functioning correctly.
k. If the non-functional endpoints are isolated to a single circuit pack, that
circuit pack is probably the cause of the problem.
l. Investigate errors and alarms in the following order:
1. Circuit pack-level
2. Ports
3. Endpoints
m. Follow the
‘‘Troubleshooting Procedures’’
outlined later in this discussion.
If the packet bus problem cannot be resolved with these procedures,
follow normal escalation procedures.
Correcting Packet Bus Faults
The Status Port-Network Command
Status port-network P
displays include the service state, alarm status, and, if
the Maintenance/Test packet bus port is present, the number of faulty and open
leads for the packet bus in the specified port-network. This information can be
used to determine the urgency of the repair. In general, a service state of “out”
indicates extreme urgency, while a service state of “reconfig” indicates moderate
urgency.
NOTE:
Ultimately, the urgency of a repair is determined by the customer’s
requirements. A customer who uses ISDN-BRI for station sets, or who relies
heavily on packet bus supported system adjunct features like DCS, Audix,
or CDR, probably considers a packet bus failure critical. On the other hand,
a customer with little ISDN-BRI service and no adjunct features may
consider even an uncorrectable packet bus fault unimportant, and may
prefer to delay repairs due to their disruptive nature.
If background maintenance is running on the packet bus when the status
port-network command is issued, the data reported for the packet bus may be
inconsistent due to updating by the tests. If the data seems inconsistent, enter
the command again.
