BladeSystem - General
1752782 Members
6628 Online
108789 Solutions
New Discussion юеВ

Re: After Virtual Connect configured cannot boot from SAN.....

 
BrianDoyle
Trusted Contributor

After Virtual Connect configured cannot boot from SAN.....

Integrity Blade
hpux 11i v3

Virtual Connect was configured on the blade enclosure.
When I power up the blade it tries the primary boot option but get this message:

Loading.: HP-UX Primary Boot: 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000
Load of HP-UX Primary Boot: 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000 failed: Not Found
Press any key to continue

Same result for the Secondary boot option.

I tried to boot from DVD and when I got to the place where you select the source and language.
It said that "Empty primary boot path reported by setboot: Promary bootpath"
See here:

Enter the index corresponding to the device to use
as the installation source, 'r' to rescan, or 'q' to reboot: 9
You selected: 0/0/2/0.0x0.0x10 disk USB_SCSI_Stack_Adaptor
Is this correct? ([y]/n):
NOTE: Empty primary boot path reported by setboot: Primary bootpath :

NOTE: Primary path not currently set to an existing disk device.
* Setting keyboard language.


Strange thing is, when I boot from the installation DVD and I get to the Install screen sees my 2 disks (LUNs).

Anyone know why this is happening?
thanks
4 REPLIES 4
Rob Leadbeater
Honored Contributor

Re: After Virtual Connect configured cannot boot from SAN.....

Hi,

Looking at the WWNs above, I'm guessing that your storage is presented by an EVA of some sort, probably an Active/Passive version such as an EVA3000 or EVA5000.

Maybe the primary and secondary boot options are pointing at the passive controller.

Hope this helps,

Regards,

Rob
BrianDoyle
Trusted Contributor

Re: After Virtual Connect configured cannot boot from SAN.....

I have an EVA4000 and using 11.31 so I think it must be Active/Active. How would I check this?
Rob Leadbeater
Honored Contributor

Re: After Virtual Connect configured cannot boot from SAN.....

Hi,

If it's an EVA4000 then it's Active/Active, so what I said previously probably isn't the problem...

Cheers,

Rob
BrianDoyle
Trusted Contributor

Re: After Virtual Connect configured cannot boot from SAN.....

Thanks Rob,

I've found the problem and need help finding a solution:

EFI has a primary boot path of 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000

I went into the installation process to have a look at what the server can see and now see that it currently sees 2 disks:
0/3/0/0/0/0.0x50001fe1500b0bbc.0x4001000000000000
0/3/0/0/0/0.0x50001fe1500b0bb8.0x4001000000000000

It used to connect through HBA2 cabled to the switch but now with Virtual Connect it connects through the first HBA (just on a different mezzanine in the blade).

How can I change the EFI primary boot path?