vCenter

 View Only

 vCHA network configuration - can each node be on a different subnet?

jalexander's profile image
jalexander posted Jun 18, 2024 10:35 AM

I can setup HA without issue if I put all nodes on the same subnet/portgroup either with or without a vlan. But I am being asked to put each node on a different portgroup/subnet/vlan and it fails.

 I am working through the article below and will report back my findings. I am using vCenter 8.0.2, so not sure if it still applies, but I would think it would at least in theory.

Update: I finished working through the article below. The active node can now ping the passive and witness nodes on the HA network. Same for the passive and witness nodes. But the status of both the passive and witness nodes is remaining as unknown and not coming up as healthy.

Some other information...this is a nested vCenter that is running inside a vCenter that is at 7.0.3 on hosts at 7.0.3. Would that be a factor? I am deploying 8.0.2. I can try 7.0.3 to see if that makes a difference if needed.

 Deploying vCenter High Availability with network addresses in separate subnets - vSphere 6.7 & 7.0

Broadcom remove preview
Deploying vCenter High Availability with network addresses in separate subnets - vSphere 6.7 & 7.0
This article provides steps to deploy vCenter High Availability (VCHA) in environments where the Primary and Secondary vCenter Server nodes are in separate subnets.
View this on Broadcom >

Jimmy15's profile image
Jimmy15

Make sure in each appliance
hostname with domain name 

NTP

DNS

Routes to all subnets
Assuming you cloned the Primary VM to Passive and Witness (not automatically)

if everything fine till now. run tail -f log on primary and passive nodes, you will see error in Hearbeat communication.