VPAR not booting from SAN

[rajeesh k menon]

Hi,

I have a 3 vpars all were booting from SAN and now its giving an error.

vPar "TEST" failed to load the kernel due to: non-bootable boot media; incorrect vPars software installed; or incorrect boot media EFI path in vPars database.
Try using "vparload -p TEST -E 0" to load the vPar.
Error loading "TEST". Shutting down "TEST"...
[MON] TEST has halted.

I tried vparload -p UAT -E 0 and was getting

0/0/4/1/0/4/0: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request;
Explanation: FC-4 Type not registered.
This may indicate that the HBA port is not part of a zone.
Please check zone configuration on your switch.

I re-checked zone config and confirmed its OK

I can see all disks from EVA in the npar mode..

How can I create new device files in EFI to make vpars bootable..

what is the procedure?..

pls help..

rgds
rajeesh

[Steven E. Protter]

Shalom,

Check for recent changes in the following areas.

HBA/Zoning on storage. If this worked and now does not then someone changed something. Could be an HBA card or fabric switch, could be LUN configuration.

Yet another reason why its better to boot vpars and other HP-UX machines off local disk.

Doc:
http://docs.hp.com/en/7408/HPUXSANBootWP_final_v2_update.pdf

SEP

[Pupil_1]

I've had a similar problem in past when the vpars won't boot from SAN. The fix was the make the HBA port speed and the switch port speed to match. we had the switch port speed to auto and on the HBA, it was 2Gig (on a 4Gig capable card). Once we had both the HBA and switch port speed to 4Gig, we have not had this error ever since.

what's the type of HBA u r having?

Cheers

[rajeesh k menon]

Hi,

FC card is (AD194A) HP PCI-x 2p 4GB FC and 2p 1000BT Adaptor ( combo).

How can I change the speed of adaptor?.. or only changing speed of switch port to 4gb is enough?

there is no other way to recover this by mapping the new device files to efi?

I can see all disks when I booted to npar mode..

rgds

rajeesh

[Geoff Wild]

If you can see all the disks in npar mode - then your SAN should be fine.

Verify that the vpar is pointing to the correct path for BOOT:

vparstatus -p TEST -v

Rgds...Geoff

[Torsten.]

"there is no other way to recover this by mapping the new device files to efi?

I can see all disks when I booted to npar mode.."


Was this working before?
Is something changed?

If it was not working before, you should check he vpar config again.

[rajeesh k menon]

Hi

it was working fine before..

I really dont know what happened to the whole system..

In case of a device file change, how can I create new boot disks for a vPar?..

rgds
rajeesh

[whiteknight]

Rajeesh,


Try Execute #vparefiutil -u on each vpar,
which should update the vpdb with correct mappings

WK

[Torsten.]

Why should a device file get changed?

If you don't change the config (e.g. use another switch port to connect the array) the device files will remain.

device files are not a problem here, but the config depends of the hardware path.

Unless you don't change the config, the path will remain.

[Pupil_1 · Accepted solution]

you can check / change speed of the HBA form EFI.

efi>reconnect -r
EFI>drivers
select the FC drivers, say 3a in this case

efi>drvcfg 3a
Configurable Components
Drv[3A] Ctrl[21] Lang[eng]
Drv[3A] Ctrl[22] Lang[eng]
Drv[3A] Ctrl[23] Lang[eng]
Drv[3A] Ctrl[24] Lang[eng]

efi> drvcfg -s 3a 21
this will open up the fc card config options
select 1 and change option 7 (Data Rate).
you might also want to consider "Connection Option" to Point 2 Point.

the numbers 21 to 24 indiates the number of ports on the HBA, if ur not sure which port is connected, you might want to update it for all the ports with drvcfg -s 31 22,
drvcfg -s 31 23 .....

[rajeesh k menon]

Hi all,

thats done..

reconnect -r & vparefiutil -u cleared everything..

thanks a lot,

rgds
rajeesh