Simpler Navigation coming for Servers and Operating Systems
Coming soon: a much simpler Servers and Operating Systems section of the Community. We will combine many of the older boards, and you won't have to click through so many levels to get at the information you need. If you are looking for an older board and do not find it, check the consolidated boards, as the posts are still there.
Operating System - VMware
cancel
Showing results for 
Search instead for 
Did you mean: 

instaling esx on eva 4000

m.jamali
Advisor

instaling esx on eva 4000

hello,,
i want to instal vmware esx 4 on eva 4000,
in your opinion can i configure that,
3 REPLIES
Sheldon Smith
Honored Contributor

Re: instaling esx on eva 4000

Create the host(s) with host mode of "VMware".

---
Don't forget to rate the usefulness/quality of *all* responses to (all of) your question(s).

Note: While I work for Hewlett Packard Enterprise, all of my comments (whether noted or not), are my own and are not any official representation of the company.
----------
If my post was useful, click on my KUDOS! thumb below!
Jan Soska
Honored Contributor

Re: instaling esx on eva 4000

another usefull hints:

- set "failover/failback" when presenting LUNs to ESX's
- use Round Robin multipath policy in ESX for all EVA disks


Jan
Steven Clementi
Honored Contributor

Re: instaling esx on eva 4000

I assume you mean....

you want to Boot your server(s) from the SAN (an EVA4000).

If so, then first...

Reboot the server and enable the BIOS for the HBA.

Reboot again and enter the BIOS utility. This will effectively "log in the HBA to the fabric"

Create any zoning you need to talk to the EVA.

Create any host profiles on the EVA if needed.

Create a Virtual Disk of an appropiate size (at least 20GB or so).

Present the vDisk to the host.

Back on the host, ru na scan to "find" the EVA in the BIOS utility.

Set the Boot Device to disk you find during the scan.


1 thing to keep in mind...

Initially as you are setting this up... ONLY USE ONE PATH. make sure your only have 1 path zoned and presented to the server, and make sure it is from the managing controller.

You can and probably will run into problems if you don't do this.

After the OS is up and running, you can go back in and zone/configure the rest of the paths.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)