Maintenance Object Repair Procedures
555-233-123
10-1294 Issue 4 May 2002
Service States
Packet Interface maintenance software monitors the in-service/out-of-service
state of each Packet Interface instance. In a system equipped with a single SPE, if
maintenance software detects that a Packet Interface instance has a “fatal fault,” it
automatically attempts to reset that instance as quickly as possible. An extensive
set of diagnostic tests are run when the Packet Interface is reset.
If the Packet Interface diagnostic tests do not pass in a system without duplicated
SPEs, the failing Packet Interface instance is placed in an out-of-service state. All
links handled by that instance go out of service, except for those than can be
transferred or “migrated” to the other Packet Interface instance.
If the system is equipped with duplicated SPEs and if the standby SPE has an
acceptable state-of-health, an SPE interchange occurs instead of a reset of the
Packet Interface. This is less disruptive than a reset, since stable calls are not
disconnected.
A Packet Interface also is put in the “out-of-service” state if it has reported a fatal
fault at system initialization time or if the Packet Interface has been reset by
background maintenance four times within the last 15 minutes, whether or not the
Reset test passes. The state of all Packet Interfaces can be determined by using
the status packet-interface command.
Duplication Impact
The following concepts apply only for duplicated SPE systems:
■ Packet Bus Connection
In a system equipped with duplicated SPEs, the Packet Interfaces in the
Standby SPE cannot access the Packet Bus to write data except during the
time of a planned SPE interchange and when the Peer Link Test (#888)
runs. Consequently, the Maintenance Looparound Test (#886) that requires
access to the Packet Bus is not run on Packet Interfaces on the Standby
SPE.
■ SPE Interchange
Severe Packet Interface faults that cause system and application links to
go down are detected within 1 second. A fatal fault error message is
generated and the Packet Interface maintenance software attempts to run
the Packet Interface Reset test. High Reliability or Critical Reliability
systems request an SPE interchange instead of a reset of the Packet
Interface, since stable calls are preserved during an SPE interchange.