separate ESXi 6.5 ISO for vSAN ?

[suhag79]

Hi,

We have downloaded and installed evaluation version of below CISCO Custom image but unable to find vSAN on it. SInce it is evaluation, it should come with vSAN,,is that correct ?

CISCO Custom Image for ESXi 6.5 GA Install CD
File size: 334.15 MB
File type: iso

Download Now

Download Manager

Name: Vmware-ESXi-6.5.0-5969303-Custom-Cisco-6.5.1.1.iso
Release Date: 2017-08-16
Build Number: 5969303

Regards,

[TheBobkin]

Hello suhag79,

vSAN is built into ESXi kernel and thus does not need a separate install or ISO.

Though check that the ISO you are using contains drivers for all the modules you require (e.g. lsi_mr3 for H730p) that are supported for vSAN and on the vSAN HCL for the function being used.

Bob

[suhag79]

Hi TheBobkin

Yes, i install it but unable to see create vSAN kernel port and also unable to vSAN services. pl see below. it is possible to create vSAN kernel only from vCenter ?

[daphnissov]

You're logged into the ESXi host client. You must use vCenter Server to join hosts to create and use vSAN.

[suhag79]

Yes, so even i can not create vSAN kernel network in advance before join the ESXi in to vCenter ? correct ?

[daphnissov]

You can using CLI but you need vCenter anyway to make use of vSAN properly, so what does that give you?

[suhag79]

Agreed with you all,

i got confused when i see this  (vSAN included)

i have installed custom CISCO ESXi 6.5 Hypervisor (Same build version) where it does not mention 'vSAN included".....nothing else....

i think, it will have it once i connect it to vCenter

[daphnissov]

As TheBobkin said earlier, vSAN is built-in to the ESXi kernel. It doesn't matter which vendor's custom ISO you download and install, the vSAN software is installed as well. But you need to use vCenter or CLI to set it up properly. This ability is not present in the ESXi host client interface.

[TheBobkin · Accepted solution]

Hello suhag79​,

I assure you - if you are using any 5.5 U1 or later ESXi install it contains the vSAN modules.

If for some reason you  are in doubt you can always just enable vSAN by creating single-member cluster via SSH using:

# esxcli vsan cluster new

And you can see the vSAN single-cluster member of that node using:

# esxcli vsan cluster get

This obviously won't be able to connect to other nodes without enabling vSAN on a vmk interface, you could do this temporarily on the default management interface (and of course change it later with a dedicated vmk and backing NICs):

# esxcli vsan network ip add -i vmk0

Then once this vSAN interface has been enabled on other nodes these can be added to the cluster using:

# esxcli vsan cluster join -u <Sub-Cluster UUID>

Complete list of esxcli vsan commands:

Online Documentation - vSphere Command-Line Interface Reference - VMware {code}

It is also possible to bootstrap vCenter onto a single vSAN node using temporary VMFS datastore:

http://vmusketeers.com/2016/07/23/bootstrap-a-single-node-vsan-cluster-under-running-vcenter-server/

https://blogs.vmware.com/virtualblocks/2017/04/25/bootstrap-vcsa-with-vsan-easy-install/

https://www.virtuallyghetto.com/2013/09/how-to-bootstrap-vcenter-server-onto.html

If you have alternate VMFS-datastore (local or SAN) to set up vCenter on then migrate it later (if you want it stored on vSAN) you can do this or use an existing vCenter even temporarily just for setting things up.

Bob