Update, I thought the issue might be tied to the configuration of the vmnet interfaces in VMware Workstation but I have tried different configurations without success.

Right now I have:

vmnet0 : Host-Only -> em0 (int-a)

vmnet1 : Bridged -> em1 (ext-a)

As far as I can tell the networking on the first node is all working fine.  I tried doing packet captures in VMware Workstation using vmnet-sniffer and in the Isilon Admin GUI using NetGather.  It looks like the 2nd node gets the information about the existence of the first node using LLDP.  And when it tries to connect to the first node it sends UDP broadcasts on port 5041 which are received by the first node but no response is sent.

Thanks

Hello PunctuatedEquilbrium,

I would double check to make sure that you are installing your cluster as stated in the install guide. https://dell.to/2YOX9Q3

Here is also a link to a KB that could also help. https://dell.to/2YQ4FKH

Please let us know if you have any other questions.

@PunctuatedEquilbrium 

Go into node 2 console to join the cluster, it not automatic. Or from node 1 do these commands:

isi devices node list

isi devices node add --serial-number=

I was able to login to WebUI on Node 1 and add the additional nodes through Cluster Management->Hardware Configuration

The doc is not very detailed about the VM network configuration, I ended up using 2 'custom':

em0 -> /dev/vmnet0 (host-only) for int-a

em1 -> /dev/vmnet1 (bridged) ext-a

Thanks

Geoff

Hi Geoff,

From the cluster side, em0 is int-a (first back end network), em1 is ext-1 (front end network), and em2 is int-b (second back end network).

If you're trying to map the OVA names to actual interfaces networks (e.g. in ESXi), the mapping is

Even when deploying in workstation, I'd suggest creating two private network switches for the back end bridging the front end (the network labeled "nat") so that you can test client access to the simulator.