VMware Cloud Community
laieh
Contributor
Contributor
Jump to solution

setup MSCS on single ESX host

Hi,

I having some issue running MSCS on single ESX host.  I have setup one pair of MSCS and running MSSQL on top.  I'm facing ip conflict intermittent in my cluster node.  Anyone have experience on this.  Do I need to apply any configuration on the virtual switch level?

Reply
0 Kudos
1 Solution

Accepted Solutions
krishna_v78
Enthusiast
Enthusiast
Jump to solution

Hi,

Check for IP addresses on both the VMs.

Cluster name IP address

Public NIC IP addresses and subnet

Private NIC IP addresses and subnet (Heartbeat)

To, further troubleshoot this issue, Disable Heartbeat NIC on both the VMs and select Heartbeat communication using public LAN option in MSCS. This helps in isolating the issue.

View solution in original post

Reply
0 Kudos
7 Replies
unsichtbare
Expert
Expert
Jump to solution

MSCS usually requires 2 NICs on the VM. Is it possible that there is a gateway in both NICs? I don't think Windows likes multiple gateways.

On a single ESXi host, you would be creating a "Cluster in a box". Network configuration should be extremely easy. You can simply set the heartbeat NICs to IP addresses which are not part of the same network as the primary NIC, or you can create a new Port Group and set a VLAN (which will serve only to isolate that Port Group, so long as that VLAN has not been configured anywhere else) and put the heartbeat NIC there.

-J

+The Invisible Admin+ If you find me useful, follow my blog: http://johnborhek.com/
Reply
0 Kudos
laieh
Contributor
Contributor
Jump to solution

Hi,

I have set 2 nic for VM heartbeat and public network both are connected to different vswitch.

Reply
0 Kudos
krishna_v78
Enthusiast
Enthusiast
Jump to solution

Hi,

Check for IP addresses on both the VMs.

Cluster name IP address

Public NIC IP addresses and subnet

Private NIC IP addresses and subnet (Heartbeat)

To, further troubleshoot this issue, Disable Heartbeat NIC on both the VMs and select Heartbeat communication using public LAN option in MSCS. This helps in isolating the issue.

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

I did setup different MSCS configurations in my lab as well as in production, using VMware's MSCS guides at http://kb.vmware.com/kb/1004617 which worked without issues. Did you setup the MSCS according to this guide?

André

Reply
0 Kudos
laieh
Contributor
Contributor
Jump to solution

I have create two nic port for my vm one for heatbeat and one for client access and both are in different segment.  Do you think the v-switch need to configure anything?

Reply
0 Kudos
laieh
Contributor
Contributor
Jump to solution

when the IP conflict happen is only conflict on public IP not the heartbeat IP.

Reply
0 Kudos
laieh
Contributor
Contributor
Jump to solution

Yes, I have follow the guide.  on ESX server configuration is, each virtual switch I have two nic port for reduduncy purpose.  Do you think on v-switch need to change any setting?

Reply
0 Kudos