This post is more than 5 years old

2 Intern

 • 

234 Posts

962

March 2nd, 2008 04:00

VMWare ESX 3i 3.5

need to make this server as boot from SAN, I've a CX3-10,can you'll help me in this?

6 Operator

 • 

5.7K Posts

March 2nd, 2008 11:00

Create a lun as large as you need the boot lun to be;
Place this lun in a storage group for this server; preferably with host lun address 0;
Zone the server to the Clariion;
Register the Server using Navisphere;
Add the server to the storage group;
Reboot or start the server and go into the HBA BIOS setup (QLogic = CTRL-Q, Emulex = ALT-E ... or was it CTRL-E ?). When in the setup, add the lun you just created to the list as being the boot lun. You should do this for both HBAs as a precaution for a single HBA failure.
Boot the server again and install VMware... or any OS you want.

Done.

2 Intern

 • 

234 Posts

March 3rd, 2008 23:00

Thanks for the help RRR.

But the lun is not being mapped on VMWare server.
I tried to add a new HDD as RDM (both physical and virtual) but we didn't find this new space from CX3-10.

I'm not finding why it doesnt see this LUN.In Navisphere the server is Registered and Logged in as Yes.

2 Intern

 • 

215 Posts

March 4th, 2008 06:00

Hello,

I'm not sure if I understand your question.
you wrote that you want to make the ESX Server booting from SAN, right?
but AFAIK a ESX 3i Server already has a USB device onboard where the ESX kernel is running.
If you boot the server from SAN you would "loose" the "i" (meaning that the esx isn't integrated into the server anymore), wouldn't you?

BR
Manfred

6 Operator

 • 

5.7K Posts

March 4th, 2008 08:00

I don't know anything aboiut the "i" version of ESX.

Another possibility of not being able to see the boot lun would be some (Qlogic) settings:
- max luns should be 256
- queue depth should also be 256 (= execution throttle)

I've seen issues with cards where these 2 values weren't set.

13 Posts

March 12th, 2008 05:00

Thanks all for the help.
Its solved now.

6 Operator

 • 

5.7K Posts

March 12th, 2008 06:00

Could you tell us what made you solve this issue so we can all learn from it ? And if one of us gave the correct answer, mark that answer as being correct.

2 Intern

 • 

234 Posts

March 12th, 2008 23:00

The solution was to set the Qlogic Bios setting with the LUN ID.

6 Operator

 • 

2.1K Posts

March 13th, 2008 04:00

BTW - Thank you for not only marking the question answered and awarding points for the correct post, but also clearly summarizing the answer at the end. If more new users on the Forums did this (and I see you only have 9 posts... 3 of which were a part of this thread) it would prevent a lot of aggravation on the part of the Moderators and the regulars :-)

Welcome to the Forums and THANK YOU!!!

6 Operator

 • 

5.7K Posts

March 13th, 2008 05:00

Right on !!!
But remember: the following can be useful as well if this problem occurs:
- max luns should be 256
- queue depth should also be 256 (= execution throttle)

0 events found

No Events found!

Top