cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
830
Views
0
Helpful
12
Replies

Unable to boot from SAN, despite ESX 55u2 is installed on a LUN0 properly

Hello there

I configured the UCS server profile to boot from SAN, creating an hba with a WWN and LUN ID = 0

when I install operating system booting the blade from a virtual cd of VMware 5.5u2, it found as disk the LUN0, the installation complete properly.

When the blade reboot, I'm unable to tell it to boot from the LUN.

boot order in the profile is set first from the SAN, second from the CD.

what's wrong ?

 

thanks in advance

regards

GB

 

1 Accepted Solution

Accepted Solutions

I believe the problem is that your policy refers to FC0 and FC1, with enforce exact name; however in the SP you talk about vhba0, 1 ?

Change the names to match exactly, or remove the tag for enforcing exact name

View solution in original post

12 Replies 12

Walter Dey
VIP Alumni
VIP Alumni

This has been discussed many times before.

If you see your lun, and can install ESXi, it means that FC zoning and lun masking / mapping is ok.

If boot fails, the boot policy is wrong, please post a screenshot of your boot policy ?

Is this a storage subsystems connected to a SAN or directly to UCS ?

hi

thank you for your reply.

I attached the boot profile screenshot.

I attached the storage policy and status details. too.

UCS fabric 6248UP is connected to a brocade switch then to the VNX disk array.

thanks

GB

 

 

I believe the problem is that your policy refers to FC0 and FC1, with enforce exact name; however in the SP you talk about vhba0, 1 ?

Change the names to match exactly, or remove the tag for enforcing exact name

hi

situation appears to be improved, but not solved.

I renamed in the profile the hba name as used in the hba list.

when the blade boot, now it show two msg (boot_fc image), then show that adapter bios is disabled (where is this in the profile ?) so no logical virtual drive on HA 0 are visible and enter in the BIOS.

where I can configure this in the profile ?

thanks again

GB

 

Sorry, but your setup must be wrong ?

Are you really using FC end host mode (see screenshot ehm) and vsan's with zoning disabled (see screenshot vsan) ?

Go to the physical blade and check actual and configured boot order (see screenshot boot)

Hi wdey,

thank you for your reply.

fabric is set in end host mode and zoning is disabled.

the only dubt is on the WWN value that I set in the primary and secondary boot.

I see values start from 50:xx:xx... not seems to be UCS values. Instead I used the WWPN values that I assigned to the boot vHBA. is it correct ?

I set boot order from 1. SAN, 2. Cdrom

If I'm able to install OS on the LUN, how can show the port WWN used ?

thanks again.

Regards

GB

 

Hi GB

The pwwn values which appear in the boot policy are the pwwn of your storage controller ? is this the case ?

Hi wdey

pwwn set in the primary and secondary boot profile is not the storage controller value.

could be this the problem ?

 

 

 

 

Yes, this is the problem; please change it, and it should work.

when I install esx it show the following values

60:06:01:60:20:45:34:00_7e:ec:53:b6:39:6b:e4:11

If I try to set into boot SAN WWN port value 60:06xxx, it enable to save the value.

if I try the 7e:ec:xxxx it doesn't enable to save the value.

LUNid set is 0

which is the value I have to consider ?

 

any other idea ?

thanks

GB

 

This values look very strange to me; why don't you check on the Brocade switch for the flogi database, for the ports where you connect the storage ?

hi wdey

I don't have access to the storage devices, only ask and try to obtain.