This post is more than 5 years old

5 Posts

2292

January 12th, 2011 07:00

Boot from SAN (ESXi)

I am working on a project where we are implementing VMWare on CISCO UCS blades that are connected to a Clariion SAN. To take advantage of the UCS technology we want to boot our ESXi servers from SAN. Therefore I have created a Storage Group for each server which contains their boot LUN. I have read that a host can only be a member of one Storage Group so does this mean that I need to add the "shared LUNs" to each of the ESXi Storage Groups? Someone told me to just create another Storage Group and add all the ESXi hosts and "shared LUNS" but I do not think you can do this. Any advice would be appreciated. Thanks.

9 Legend

 • 

20.4K Posts

January 12th, 2011 07:00

you will need to create an individual storage group for each ESX server, each storage group will contain the individual boot LUN for that particular ESX host and the shared LUNs.

9 Legend

 • 

20.4K Posts

January 12th, 2011 08:00

you are on a mission ..aren't you ?

4 Operator

 • 

5.7K Posts

January 12th, 2011 08:00

Oh and please don't call a Storage Array a SAN. A SAN is a network, so the SAN switches are the SAN.

5 Posts

January 12th, 2011 09:00

OK, sorry about that. I do understand what a SAN is but have got lazy recently and referred to the array as a SAN. Will not happen again

3 Apprentice

 • 

542 Posts

January 12th, 2011 09:00

Going off Dynamox's info,  one thing you will need to do is since you are going to have multiple storage groups that need to see the same datastore lun's, you need to make sure that the host ID is the same across all of them.

I would suggest adding the boot luns to each storage group  and making them hostID 0.  Then add the datastore lun's to one storage group and get the host ID # for each.  Then when you add those same lun's to the other storage groups with the other ESX servers, you will have to manually  assign the host ID to each.  (or you can add one at a time in hostID order)  Once you get that done, you can scan the bus within ESX

9 Legend

 • 

20.4K Posts

January 12th, 2011 09:00

not a bad idea ..take a look at this integration paper

White Paper: EMC CLARiiON Integration with VMware ESX—Applied Technology

3 Apprentice

 • 

542 Posts

January 12th, 2011 09:00

Creating another post is up to you.  I would say that if you ask a question in a post and mark it as answered, if you post another question in that same thread, it might not get the attention it needs since most will think it has been answered to your liking.

Dont worry about asking  questions.  This is what this place it for.  There are many folks here that will respond when they can. And alot of us have a wide range of skill sets (except Dynamox who seems to have them all)   thatyou will get an answer sooner or later.  If it is urgent then call support or open a live chat.

That live shat is pretty usefull for asking general questions.  I have used it alot!!

5 Posts

January 12th, 2011 09:00

That is what I thought. Thank you.

5 Posts

January 12th, 2011 09:00

Thank you for this. When creating the boot LUNS is it best to create them on different RAID Groups (separate disks). For instance if I created the boot LUNS on one RAID 5 group and two disks were to fail in that group could I potentially lose all my ESX servers?

Sorry if I should have create a new post for this. Apologies if I am asking silly questions but I am pretty new to Storage Arrays and VMware.

5 Posts

January 13th, 2011 02:00

Thank you dynamox and kenn2347 for such quick replies.

dynamox, I think I have read through that document before as I remember reading that ESXi and boot from SAN was not supported. I know ESXi is now supported. Looking at the document it does state to use LUN masking to ensure that hosts only have access to "their" LUNs as we have discussed previously. It does not mention anything about ensuring that you do not have all your boot LUNs in the same RAID Group (using the same disks). Do you think it makes sense to separate my ESXi boot LUNs over two or three RAID groups instead of having all five of them in the same one?

If I have anymore questions I will post a new thread. Thank you to everyone that has taken the time to give me help and advice. It is greatly appreciated.

9 Legend

 • 

20.4K Posts

January 13th, 2011 06:00

dynamox, I think I have read through that document before as I remember reading that ESXi and boot from SAN was not supported. I know ESXi is now supported. Looking at the document it does state to use LUN masking to ensure that hosts only have access to "their" LUNs as we have discussed previously. It does not mention anything about ensuring that you do not have all your boot LUNs in the same RAID Group (using the same disks). Do you think it makes sense to separate my ESXi boot LUNs over two or three RAID groups instead of having all five of them in the same one?

from availability perspective, sure you can put them in separate raid groups and make sure LUNs are "balanced" between SPs.. but from performance perspective it does not matter on ESX ..once the kernel is booted all the workload is on VMFS datastores.

No Events found!

Top