The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Subnet and Routing issues in VMware vCenter Heartbeat (1008783)
- The VMware Channel disconnects or fails to connect in a LAN deployment.
- The VMware Channel disconnects or fails to connect in a WAN deployment.
The VMware Channel may disconnect or fail to connect due to the principal (public) NIC and/or one or more channels sharing the same subnet
If VMware vCenter Server Heartbeat is deployed in a LAN environment, the principal (public) IP address and the channel IP address on a server must be in separate subnets. If there are multiple redundant channels, each needs to have its own subnet. Check the network configuration for each NIC on both servers in the pair, and correct any issues.
When the VMware Channel disconnects or fails to connect in a WAN deployment it may be the result of the static route not being configured or that it has been configured incorrectly.
When VMware vCenter Server Heartbeat is deployed in a WAN, it is generally not possible for the principal (public) IP address and the channel IP addresses to be in different subnets, since there is usually a single network path between the two servers. To ensure that channel traffic is routed only between the endpoints of the channel, it is necessary to configure a static route between these endpoints.
See vCSHB-Ref-466 where the channel and principal (public) IP addresses are on the same subnet in a WAN environment, for a detailed discussion about WAN channel routing issues, and for instructions on how to configure a static route for the VMware Channel.
For related troubleshooting information, see VMware vCenter Server Heartbeat channel drops (1008551).
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.