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
Solved! Go to Solution.
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 ?
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 ?
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 ?
when I install esx it show the following values
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 ?
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 ?