Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11 (452 Views)
Reply
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 1 of 10 (453 Views)

Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

Hi,

 

I have a sd3200, with 2 npars, since yesterday when I launch the parstatus command it doesn't finish it just hangs...

 

I imagine is a communication problem between the npars and the gsp but there are a lot of things in the middle

 

I have tried giving the GSP a reset, but it didn't help, I checked SEL and FPL for errors couldn't find anything very helpfull(there is a power fault in cell4,but thats another problem..), i will attach the logs.

 

Nothing in syslog.log either.

 

Any idea what can solve this problem, Will a npar(reboot/reset(RS) help?

 

I also thought of reseting the gsp bus with the RU command, but need hp for that in the sd3200, no support anymore ..

 

I also attached the output of tusc command when launching parstatus.

 

 



Windows?, no thanks
Please use plain text.
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 2 of 10 (452 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

it didn't let me attach the files

Windows?, no thanks
Please use plain text.
Acclaimed Contributor
Torsten.
Posts: 23,193
Registered: ‎10-02-2001
Message 3 of 10 (450 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

When you say "since yesterday" - something changed? Maybe something related to the cimserver, any providers, etc ...?

Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! star in the left column!   
Please use plain text.
Acclaimed Contributor
Dennis Handly
Posts: 24,853
Registered: ‎03-06-2006
Message 4 of 10 (444 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

>it didn't let me attach the files

 

Did you give them a suffix like .txt?

Please use plain text.
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 5 of 10 (440 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

yes the files have a .log

Windows?, no thanks
Please use plain text.
Acclaimed Contributor
Dennis Handly
Posts: 24,853
Registered: ‎03-06-2006
Message 6 of 10 (437 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

>the files have a .log

 

You may have to use .txt.

Please use plain text.
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 7 of 10 (437 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

They told me about parstatus, and it was hanging since the 2nd of august, but looking further into the problem, i found out icod_stat commands also hanging since the 13th of june:

 

root 16290     1  0  Jun 13  ?         0:00 /usr/sbin/icod_stat
    root 16564     1  0  Jun 13  ?         0:00 /usr/sbin/icod_stat
    root   323   197  0  Jun 18  ?         0:00 icod_stat
    root 28488     1  0  Jun 19  ?         0:00 /usr/sbin/icod_stat
    root  4699  4553  0  Jun 22  ?         0:00 icod_stat
    root 19416     1  0  Jun 15  ?         0:00 /usr/sbin/icod_stat
    root  1064   942  0  Jun 15  ?         0:00 icod_stat
    root  8939     1  0  Jun 21  ?         0:00 /usr/sbin/icod_stat
    root  4501     1  0  Jun 14  ?         0:00 /usr/sbin/icod_stat
    root 11044 10904  0  Jun 14  ?         0:00 icod_stat
..................................

 

And that corresponds with the a problem we had in the cpd, with overtemperature, and the complex shutdown

 

30  PM   0     *5  0x582008516100406e 0x00006f050d07000a INLET_OVERTEMP
131  PM   0     *5  0x582008516100406e 0x00006f050d07000d INLET_OVERTEMP
132  PM   0     *6  0x582008616100406f 0x00006f050d070b09 INLET_OVERTEMP
133  PM   0     *14 0x5c2008e16100406d 0x00006f050d071011 INLET_OVERTEMP
134  PM   0     *2  0x5c20082944ff302f 0x00006f050d071012 CABPWR_OFF
135  PDHC 0,3   *14 0x246014e39201404f 0x00ffff01ffffff91 POWER_FAULT
135  PDHC 0,3   *14 0x58601c0000004040 0x00006f050d071012 06/13/2011 07:16:18

 

So it looks that once the npars booted again, they where not able to speak with the gsp.

 

And that brings us also to the power_fault we have in cell 0,3:

 

HW status for Cell 3 in cabinet 0: FAILURE DETECTED
Power status: on, 1.6V BRICK 1 UNDER VOLTAGE FAULT

 

does brick 1 refer to the power brick in the backplane HBPB1 ?

 

could be related, we have to fix it also..

 

 

On the other hand Torsten, no we didn't modify anithing cim related, and are very stable we hardly ever touch them

Windows?, no thanks
Please use plain text.
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 8 of 10 (436 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

triying with .txt

Windows?, no thanks
Please use plain text.
Acclaimed Contributor
Torsten.
Posts: 23,193
Registered: ‎10-02-2001
Message 9 of 10 (424 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

I would start now to check the components with GSP "ps" command.


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! star in the left column!   
Please use plain text.
Honored Contributor
likid0
Posts: 979
Registered: ‎03-01-2005
Message 10 of 10 (415 Views)

Re: Parstatus command hangs in 2 npars in sd3200 with hp-ux 11.11

Yes, In the ps output I have once cell with a power problem:

 

    B - Cabinet (UGUY)
    C - Cell
    G - GSP
    I - Core IO
        Select Device: c

    Enter cabinet number: 0
    Enter slot number: 3

HW status for Cell 3 in cabinet 0: FAILURE DETECTED

Power status: on, 1.6V BRICK 1 UNDER VOLTAGE FAULT
Boot is blocked; PDH memory is shared
Cell Attention LED is off
RIO cable status: not connected
RIO cable connection physical location: cannot be determined
Core cell is INVALID

PDH status LEDs:  _*__
                              CPUs
                            0 1 2 3
          Populated         * * * *
          Over temperature        

DIMMs populated:
+----- A -----+ +----- B -----+ +----- C -----+ +----- D -----+
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
* * * *         * * * *         * * * *         * * * *       


I have also seen this error in the df output:

 

ERROR: There has been an error retrieving FRU CPU: Location 3, 1
    RtnCodeUsbDevNotPresent

176 of 176 FRU IDs were retrieved and valid


------------------------------------------------------------------------------
Fru Name         Part Name   Loc  Serial Num   Art Eng  Scan R Fru Spec.     
  Manf Test Hist. 0  Manf Test Hist. 1  Manf Test Hist. 2  CC V  FR            
  Manf Test Hist. 3  Manf Test Hist. 4  Manf Test Hist. 5  Spare               
------------------------------------------------------------------------------
SBC Board        A1150-2094                             0x2020 B              
  202020202020202020 202020202020202020 202020202020202020 a7 Y  A
  202020202020202020 202020202020202020 202020202020202020 2020
             BPS AXXXX-XXXXX 0    NOT VALID        000E 0x3030              0x1
  000000000000000000 000000000000000000 000000000000000000 3b Y  A
  000000000000000000 000000000000000000 000000000000000000 0000
             BPS AXXXX-XXXXX 1    NOT VALID        000F 0x3030              0x2
  000000000000000000 000000000000000000 000000000000000000 3d Y  A
  000000000000000000 000000000000000000 000000000000000000 0000
             BPS AXXXX-XXXXX 2    NOT VALID        000E 0x3030              0x1
  000000000000000000 000000000000000000 000000000000000000 3b Y  A


 

Windows?, no thanks
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation