Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to deploy an installation of VMware VSA in my network, and for that I got 2xquad nics in each server (2x Dell PE 1950)

Everything seems fine so far, but then the installer complains about some NFS address conflicts, which I don't get, since it is a completely closed network.

A quick sketch of the network: Network setup

So, as you can see, I connect the servers VSA network directly between them.

But is this actually supported, or do I have to use a switch and a routable IP?

My vCenter server is connected via a Site-To-Site VPN on a different subnet.

ESXi servers are in the 192.168.99.X/24 subnet, and the vCenter server is in a 10.100.100.X/24 subnet.

I am configuring VSA for 192.168.253.X/24 as frontend network, and 192.168.254.X/24 as backend network.

I am configuring the portgroups myself, since the installer complains it is not a greenfield install.

VSA install configuration:
VSA Management Network Settings:
VSA Cluster IP Address:
VSA Cluster Service IP Address:

Subnet Mask:

Host Network Settings:
Management IP Address:
Datastore IP Address:
vSphere Feature IP Address:
Subnet Mask:
Back-end IP Address:
Back-end Subnet Mask:

Host Network Settings:
Management IP Address:
Datastore IP Address:
vSphere Feature IP Address:
Subnet Mask:
Back-end IP Address:
Back-end Subnet Mask:

VLAN ID Settings:
Management VLAN ID: 1381
Datastore VLAN ID:  1381
vSphere Feature VLAN ID:    1381
Back-end VLAN ID:   1382

Disk Formatting Option:
Format disks immediately

Storage Capacity Selection:
911.72 GB

Here is the warning I get upon starting the install:

Switch warning

This is the error I get when I try to begin the actual install:

Node error

This is the overview of the vswitch config:


This is the config of the frontend network on one of the servers. The rest is configured similary, where the active adapters for the frontend is configured as standby for vmotion and vice versa.

vsa front end

share|improve this question
I can't see the lack of a switch as being a problem, but you've not stated the actual errors you're getting, also does it work with just a single link? – Chopper3 Jul 27 '13 at 16:22
How about a screen snapshot of your vSwitch configurations? – SpacemanSpiff Jul 27 '13 at 16:33
@chopper3: More info and the actual error added. – Frederik Nielsen Jul 27 '13 at 16:40
@spacemanspiff: screens have been added :) – Frederik Nielsen Jul 27 '13 at 16:40
@FrederikNielsen - thanks for the extra information, I have to admit I'm not a VSA user, only ever set it up once as part of revision for VCAP but there IS a chance that it demands actual switch ports rather than direct connection - that's a bit stupid if it's the case but the only way to prove it would be to use a switch. I wish I knew a workaround or other answer for you but I don't sorry. I'll be very interested in any further work you do on this issue. – Chopper3 Jul 27 '13 at 18:48
up vote 0 down vote accepted

Allright, after some weeks of messing around with all this, I decided to put up a switch between the hosts, and it works perfect.

Also a note for the future: The vCenter server cannot be on a different subnet - the VSA installer simply won't let you continue.

share|improve this answer
How's the performance? – ewwhite Aug 24 '13 at 18:58
@ewwhite . Haven't had time to do some actual performance testing on it yet. – Frederik Nielsen Aug 24 '13 at 22:22
Disregard my comment; different vendor of VSA – Mark Henderson Aug 24 '13 at 22:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.