Maintenance Object Repair Procedure
555-233-142
8-930 Issue 1 May 2002
A demand reset of a standby Packet Interface circuit is not disruptive and is
allowed regardless of the service state of the associated maintenance software.
Service States
Packet Interface maintenance software maintains a state variable to monitor the
in-service/out-of-service state of each Packet Interface circuit. If maintenance
software detects that a Packet Interface has a “fatal fault”, it can attempt to reset
the circuit pack. An extensive set of diagnostic tests is run when the circuit pack is
reset.
An IPSI’s Packet Interface also goes out-of-service if the IPSI has either:
■ Reported a fatal fault at system initialization time
■ Been reset by background maintenance 3 times in the last 15 minutes,
whether or not reset succeeded.
The state of a Packet Interface circuit can be determined by using the status
packet-interface command.
Maintenance-Object Interactions
■ Packet Bus maintenance
A Packet Interface circuit physically interacts with the PKT-BUS. So, for
certain types of Packet Interface errors, it may be difficult to isolate faults to
one or the other component. In each of these cases, Packet Interface
maintenance forwards an error report to packet-bus maintenance, where it
records a packet-bus fault in the hardware error log and runs appropriate
Packet Bus tests.
■ Packet Interface maintenance
The operation of the IPSI circuit pack’s Packet Interface circuit affects the
operation and maintenance of other circuit packs connected to the packet
bus. This includes:
1. BRI applications (BRI-PT)
2. Universal DS1 applications (UDS1) for ISDN/PRI applications
Some packet errors may require examination of the Packet Interface
circuit’s operating status. To obtain this information:
■ Examine the Error and Alarm Logs for PKT-INT entries. You must
determine which PKT-INT the link is accessing.
■ Use status sys-link to identify the PKT-INT location in this EPN, or
use status sys-link to find the PKT-INT hardware used by the
faulted link.
■ Then use test sys-link command to troubleshoot that component.
To Next Page
Loading...
