vpars and sanboot

[KPS]

Hi vPar Gurus,

I just created a vpar with a SANboot device I got the HW path of this device by putting the nPar into nPars mode on this rx8640. When I try to boot the new vpar that I have successfully created, I get the following messages:

Primary boot path not found.
Internal error in setting up vPars variables.
"" load failed.

Would anyone know of anything that needs to be set specifically when creating a vPar on a SAN Boot Device or anything else that may be causing these problems.

Again I got no errors when creating the vpar that I'm having no luck loading.

Thanks,
KPS

[Asif Sharif]

HI KPS,

did you set the nPartition to boot into vPars mode like this way??

# vparenv -m vPars


Regards,
Asif Sharif

[Torsten.]

Did you see the problem with the new vPar only?
Did you add the boot device to your config?

e.g.
vparmodiy -p myvpar2 -a io:0.0....0:BOOT

check with vparstatus -p ...

[Duncan Edmonstone]

When I've seen this sort of problem before, its usually been down to firmware/EFI versions on the FC cards (and general EFI version for the system). Make sure you are on the very latest version for starters. If you still have problems, come back after upgrading.

HTH

Duncan

[KPS]

Yes my syntax for putting it back into vPar mode from npar mode was:

vparenv -m vPars

(Doesn't look any different


Also, I did add the boot device to my config with a vparmodfiy -a io:0.0....0.0:BOOT

I guess we need to go verify EFI versions on the FC Cards and the EFI in general. I'll get back with those results...

Regards,
KPS

[Reshma Malusare]

Hi KPS,

Error itself is self explainatory.Pri boot path is not set or system is not anle get it

1] vparmodiy -p -a io:0.0....0:BOOT

-a --> alternate boot path

2] mon> setboot -p
or setboot -a

Thanks & Regards
Reshma

[Torsten. · Accepted solution]

" -a --> alternate boot path "

This is wrong!

a --> add
d --> delete

The command will add the primare boot path information to the vPar config.

[KPS]

Thanks everyone, I'm all set and have figure out my issue. I had a slightly wrong hw path the boot device configured.

Thx again!

KPS