If the nodes are identical they are differently patched at the back. 

hello Jeroen. thanks for your reply,

The reason I am trying to change this is because, our core switch went down and came back in 15 minutes and all vms were restarted on this cluster with eth2 and eth3 only whereas other clusters with eth2 and eth4 configuration were not restarted.

Could this be the reason of VMs restarted on this cluster and will the vm’s restart if the core switch goes down as per the design.

Note: There is no core switch high availability.

do you have eth2,eth3 both configured to one core switch?what about other nodes with eth3,eth4?
are they all connected to same core switch which was restarted?
if the answer is yes (there is no core switch high availability, I believe the cluster could have somehow was restarted.is the host version is same on all clusters in your environment?

Settings>Network Configuration>edit the virtual switch (vs0)>next>select the desired interfaces.

I would definitely involve Nutanix support and switch vendor to find out more details about this incident.

Dear Ahmed, 

Thanks for your reply.

do you have eth2,eth3 both configured to one core switch? yes both configure on same switch 

what about other nodes with eth3,eth4? other nodes did not restart

are they all connected to same core switch which was restarted? YES to the same switch

Yes there is no core switch HA

is the host version is same on all clusters in your environment? YES 

But what I was thinking is because the eth3 was not configured on the problem cluster that's why the vm’s went off.

Let me know your feedback about this.

I don’t think so! at the end they are all connected to same switch, something went wrong on that cluster, if this is a production cluster, I suggest you open a case with Nutanix to find out the reason behind it.

you need to check from switch side as well, if the configuration is same for all nodes.

Thanks for your response.