............................................................................................................................................................
5
An OOS-GQPHLB GQPH QPIPE has been removed because of a
local loopback failure in the PH or a failure to activate the appropriate
network processor (NP) channel. The parent physical PH is faulty,
operating in “degraded” mode if no STBY PH33 is on the same shelf.
This status is typically a transitional state but you may want to verify
the status:
OP:STATUS,GQPHPIPE,QPIPE=a-b-c-d-e;
Where:
a = Global switch module number
b = Packet switch unit 2 number
c = PSU2 shelf number
d = GQPH channel group number
e = QLPS network number
If it still shows
OOS-GQPHLB, obtain the status of the PH33:
118X,Y,ZZZ
Where:
X = Packet switch unit 2 shelf number
Y = PSU2 number
ZZZ = Global switch module number
The associated GQPH channel group
d should be assigned to a DEGR
PH33 and there should be at least one OOS PH33 on the shelf. Obtain
a list of
OOS PH33s and recover at least one of them using the SIP
for Packet Trunking Corrective Maintenance procedure, Clear
Protocol Handler Problems, 235-200-118.
If there is a spare or STBY PH33 on the shelf, it might help to switch
the GQPH channel group with the failed pipes to the STBY PH33.
After the PH33 is recovered, RE-ENTER this procedure at Step 1
because there may be other problems that inhibit the target GQPH
QPipe from being successfully restored.
............................................................................................................................................................
6
An OOS-QLPSLB GQPH QPipe cannot successfully loop back a test
frame to the QLPS. The TSI-QPH nailed-up path is established and
the NP channel is activated, and an undetected failure is presumed to
Resolve GQPH QPipe Problems
Maintenance Considerations
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
7-49