rx8640 san boot form NetApp storage

[halt007]

Our customer design to configure FCP SAN boot HPUX host.
When we boot the server and enter the "EFI shell" and use command :map ,it just found internal disk, we can't find NetApp lun.
we boot the server to OS use internal disk and mirror the OS to the NetApp lun and run command: setboot -p 0/4/1/0.1.2.0.0.0.0 (NetApp lun) ---set primary boot path to NetApp lun, then we reboot the server and select boot the os from this path ,
/----------------------------------\
| Boot Menu |
| HP-UX Primary Boot: 0/4/1/0.1.2...|
| Core LAN Gb A |
| HP-UX Alternate Boot: 0/1/1/... |
| EFI Shell [Built-in] |
| Internal Bootable DVD |
| Core LAN Gb B |
| ------------------------------- |
| Boot Configuration |
| System Configuration |
| Security Configuration |
| |
\----------------------------------/,
it appear this error:
" HP XL2 Fibre Channel Driver v1.36 (0x1.24)
.fc_locate FAILED: 384
Loading.: HP-UX Primary Boot: 0/4/1/0.1.2.0.0.0.0
Load of HP-UX Primary Boot: 0/4/1/0.1.2.0.0.0.0 failed: Not Found
Press any key to continue"
We upgrade HBA card firmware to the 1.24 (newest),but problem still.

Environment:
OS: HPUX 11i v2 sep.2006
FS type:vxfs
Server:RX8640 (Itanium 2 cpu,virtual partations )
EFI Boot Manager ver: 1.10 [14.62]
HBA: A6795A (firmware:1.24)
FC Switch: Brocade SW4100 (FAS6030 one port and server HBA in the same zone)
FAS6030 Data Ontap:7.2
Cfmode: SSI (Single System Image);
LUN and igroup mapping ready,

[Torsten.]

Hi,

your storage device must be supported (known) from the server and OS point of view.

I doubt the netapp is. See this document:

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

And also this link:

(it says "NO" in column "boot support" for NetApp)

http://www.hp.com/products1/serverconnectivity/mass_storage_devices.html

[Jason Ray]

I have run into the same problem with the fc_locate error during the load of a SAN disk. From what HP is telling me, it is a problem with the A6795A card. The workaround that they gave me, was to perform a 'reconnect -r' and the EFI shell. That will reattach the drivers for the card and it should attempt to reconnect to the SAN/switch.

I am actually still in the middle of working through this but my problem is made worse because I am creating vPars that boot off of the SAN.

But interrupt the boot process and jump into the EFI shell. Perform the 'reconnect -r' and then try the boot.