vPars on rx7620 with SAN boot disks does it work?

[R Cardwell]

Hi,

Does anyone know if this works? as have a rx7620 running HPUX 11.23 which has been divided into 2 equal chunks with nPars then one of the nPars is then going to be split in two again.

However I am having major problems getting this to work, as the server will not boot off the SAN 8 times out of 10 when configured in vPars mode (in nPars it seems fine) and when it does, and I get the following crash message:


+++++++++++++++++++++++++++++++++++++++++++++++++++
panic: addImageToDatabase: bad image pointer

+++++++++++++++++++++++++++++++++++++++++++++++++++


Event log:

INFO:CPU0:MON:vPar Monitor version 1.0 started
INFO:CPU0:MON:Version string: @(#) $Revision: vmunix: jazz @ 20050610.14:06:51PDT; jmkvw -proj kern -RW -c Task: A.04.01.07 jholly_A.04.01.07 cup2_vpar_i380_dev(CUP2_VPAR_I380_DEV_BL_2005-JUN-10-
INFO:CPU0:MON:gen_proc_init: root_cell = 1
DEBUG:CPU0:MON:Completed IPMI initialization
INFO:CPU0:MON:MFS is defined: base= 0x6000000103e93000 size= 28 KB
INFO:CPU0:MON:mfs_get_header: successful - hdr size 28672
INFO:CPU0:MON:mfs_open: successful
INFO:CPU0:MON:mfs_get_header: successful - hdr size 28672
INFO:CPU0:MON:open: file /stand/vpdb size= 12344 bytes
INFO:CPU0:MON:addImageToDatabase: bad image pointer (6000000102c96288)
FATAL:CPU0:MON:panic: addImageToDatabase: bad image pointer

FATAL:CPU0:MON:Crash event detected: panic
FATAL:CPU0:MON:Panic detected by CPU 0
INFO:CPU0:MON:CPU 1/120 in NO VP changed state from MPMON to MPCRASH for MPCRASH_CPT_UPDATE

The OS (HPUX 11.23) has been loaded onto each of the vPars boots disks via Ignite when the server was in nPars mode, and boot fine when in nPars mode.

I have updated the server FW, and the Dual port Fibre cards FW to the latest revision, incase that helped but it didn't.

Anyone got any ideas?

[Florian Heigl (new acc)]

I dimly remember Ignite-recovery of SAN-booting VPars was unsupported, maybe this is the same issue, maybe not.

[Steven E. Protter]

Shalom,

That server is without npar/vpar definitely supposed to be able to boot off a SAN.

If it boots off the SAN at all, which you indicate it does, there may be a problem with the SAN configuration, or with one of the Fiber cards.

Is a settup with npars and vpars running inside the npars possible? This would put you in the reliable place.

Still, I'd run down the other issues. It should never boot or always boot, anything in between points to issues outside the software.

SEP

[R Cardwell]

Seems strange that it will boot in nPar mode (most of the time) and not in vPars mode.

I reckon I will try with local disks for the nPar and vPars and see if that helps otherwise I am completely stuck.