Error in parstatus command

[carodn]

Hello, I need your help with this problem, on a SD32 with HP-UX11i V2, we have 2 partitions, with 5 vpars, in one of them, when I execute the parstatus command, the last part of the output is this error:

The total number of partitions present : 2
Empty HTTP response message.
Note: Unable to get any HP_NParPowerCoolingDomain information.

Error: Unable to get any cabinet information.
Empty HTTP response message.
Note: Unable to get any HP_NParCellSlot information.

Error: Unable to get any cell information.
Empty HTTP response message.
Note: Unable to get any HP_NParIOChassisSlot information.

Error: Unable to get any I/O chassis information.
Empty HTTP response message.
Note: Unable to get any partition information.

Error: Unable to get any partition information.

and if I try the parstatus -I this error display:
CIM_ERR_FAILED: A general error occurred that is not covered by a more specific error code: "index out of bounds"
Note: Unable to get any iochassis information.

Error: Unable to get any I/O chassis information.

But is not the same with the vpar commands that no have problems.

On the others partitions the parstatus command it's Ok, only we have problems with the partition manager web environment in one vpar, but the parstatus display all the information.

Do you know which processes have to run for the parmgr or parstatus command?
We reboot the partition and re-start the cimserver..but we don't have any idea for this behavior, because all the partitions have the same software and patches.

Thanks in advanced for your help.
Regards, Caro.

[Todd McDaniel_1]

Did you start from /stand/vpmon on all vpars?
Do a:

#lifcp /dev/dsk/:Auto -

And see what your output is for each vpar.

Are your Npars/vpars all running the same version of the software?

Try running vparstatus and see what you get.

[Todd McDaniel_1]

that is your primary root disk...

[carodn]

Hello Todd!, first thank you for your response, I made a mistake in my question , because in the same npar, the vpars have the same error, but in the other npar no problem.
And in this machine there was a change of memory and process before start with this problem.
The output of the commands that you told me are:

NPAR0-VPAR0:
# lifcp /dev/dsk/c1t0d0s2:AUTO -
hpux
# lifcp /dev/dsk/c2t0d0s2:AUTO -
hpux

vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ============ ======================= =====
vpar00 Up Dyn,Auto,Nsr /stand/vmunix
vpar01 Up Dyn,Auto,Nsr /stand/vmunix

[Virtual Partition Resource Summary]
CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ========== ==========
vpar00 1/ 8 6 6 1024 1024
vpar01 1/ 8 6 7 1024 1024

Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
============================== ====================== ======================
vpar00 0/ 0 32768 0/ 0 0
vpar01 0/ 0 32768 0/ 0 0

# uname -a
HP-UX B.11.23 U ia64

NPAR0-VPAR1:
lifpc same as vpar0
vparstatus same as vpar0
system same as vpar0

NPAR1-VPAR10:
# lifcp /dev/dsk/c3t0d0s2:AUTO -
hpux
# lifcp /dev/dsk/c4t0d0s2:AUTO -
hpux
# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ============ ======================= =====
vpar10 Up Dyn,Auto,Nsr /stand/vmunix
vpar11 Up Dyn,Auto,Nsr /stand/vmunix
vpar12 Up Dyn,Auto,Nsr /stand/vmunix

[Virtual Partition Resource Summary]
CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ========== ==========
vpar10 1/ 8 4 6 1024 1024
vpar11 1/ 8 2 8 1024 1024
vpar12 1/ 8 2 6 1024 1024

Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
============================== ====================== ======================
vpar10 0/ 0 32768 0/ 0 0
vpar11 0/ 0 32768 0/ 0 0
vpar12 0/ 0 32251 0/ 0 0
# uname -a
HP-UX B.11.23 U ia64

NPAR1-VPAR11:
lifpc same as vpar10
vparstatus same as vpar10
system same as vpar10

NPAR1-VPAR12:
lifpc same as vpar10
vparstatus same as vpar10
system same as vpar10


and another point is the syslog there is several entries like this:

cimserverd[2323]: cimserver[14286] not running, attempting restart
cimserver[29693]: Listening on HTTPS port 5989.
cimserver[29693]: Listening on local connection socket.
cimserver[29693]: Started HP-UX WBEM Services version A.02.00.07.

and again cimserver not running, attempting restart...

Thanks a lot
Regards, Caro.

[Todd McDaniel_1]

Can you double check your software versions on all 5 vpars? Well at least 1 vpar on each Npar.

Also, your recent work to add/replace hardware. Did you run the vparmodify command on the affected Vpartitions to add/change the hardware config?

Also, post your entire parstatus output for the bad partition output.

[Todd McDaniel_1]

One more thing...

your vpar output for the lifcp command should be similar to the following:


# lifcp /dev/dsk/c0t8d0:AUTO -
hpux -lq /stand/vpmon [ vparload -auto ]

that last bit isnt usually required.

[Torsten. · Accepted solution]

Hi,

your AUTO file should contain the vpmon to ensure the vPars monitor is started:

hpux vpmon -a

To achive this, you could do something like this:

# echo "hpux vpmon -a" >/tmp/AUTO
# efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO /EFI/HPUX/AUTO

(replace c3t2d0s1 with your current device)

[carodn]

Hello!
Yes, I did check the software version and is the same, on the other hand, also was made the vparmodify for the change of hardware.
This is the output of the parstatus command:

# parstatus
Note: No action specified. Default behavior is display all.
[Complex]
Complex Name : AWD1
Complex Capacity
Compute Cabinet (8 cell capable) : 1
Active MP Location : cabinet 0
Original Product Name : superdome server SD32B
Original Serial Number : ADERF000
Current Product Order Number : 0004A
OEM Manufacturer :
Complex Profile Revision : 1.0
The total number of partitions present : 2
Empty HTTP response message.
Note: Unable to get any HP_NParPowerCoolingDomain information.

Error: Unable to get any cabinet information.
Empty HTTP response message.
Note: Unable to get any HP_NParCellSlot information.

Error: Unable to get any cell information.
Empty HTTP response message.
Note: Unable to get any HP_NParIOChassisSlot information.

Error: Unable to get any I/O chassis information.
Empty HTTP response message.
Note: Unable to get any partition information.

Error: Unable to get any partition information.

and finally I made :

# echo "hpux vpmon -a" >/tmp/AUTO
# efi_cp -d /dev/rdsk/c1t0d0s1 /tmp/AUTO /EFI/HPUX/AUTO

and I noticed that in the efi_ls the AUTO entry is missing,

# efi_ls -d /dev/rdsk/c1t0d0s1
FileName Last Modified Size
EFI/ 9/27/2006 0
STARTUP.NSH 9/27/2006 296

total space 523251712 bytes, free space 519745536 bytes

# lifls -l /dev/rdsk/c1t0d0s2
volume ISL10 data size 7984 directory size 8 05/09/22 09:37:09
filename type start size implement created
===============================================================
ISL -12800 584 242 0 05/09/22 09:37:09
AUTO -12289 832 1 0 05/09/22 09:37:09
HPUX -12928 840 1024 0 05/09/22 09:37:09
PAD -12290 1864 1468 0 05/09/22 09:37:09
LABEL BIN 3336 8 0 06/09/27 13:24:33


Thanks a lot for your help..
Regards, Caro.

[Todd McDaniel_1]

Caro,

I am thinking you can only do a few things before you call HP for support.

First, try to reset your MP and see if that corrects the issue. You are having some kind of communication issue to/from the firmware on that first Npar/Vpars.

Second, How did you create the partitions on this System? Did you ignite them from a single image or create each one from scratch? There might be some confusion created when you ignite from a different version of hardware to a cell-based system as this one is.


Also, read this other thread and see if it offers any ideas.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1010524


Sorry I cant be of more help. If you still cant solve it, best call HP and ask them.


Best wishes, Todd McDaniel

[Duncan Edmonstone]

Whether your AUTO files are corerct or not, I suspect the issue with vpartstatus and partstatus is more likely to do with a problem with WBEM services. Both parstatus and vparstatus use WBEM providers to gather the info required, and this is generally managed by the cimserver process.

A good place to start would be the troubleshooting guide for WBEM services in this manual here:

http://docs.hp.com/en/B8465-90012/ch06s01.html

Probably worth checking you have the latest/patched versions of WBEM and the approapriate WBEM providers as well:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B8465BA

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=nParProvider

http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_34963&sel={hpux:11.23,}&BC=main|search|

http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_34429&sel={hpux:11.23,}&BC=main|search|

HTH

duncan