VMware Cloud Community
George_Yu
Contributor
Contributor
Jump to solution

After moved a existed Host to HA Cluster, got Misconfiguration in the host network setup

An existed Host worked well in datacenter, which only had one NIC card. But moved it to HA Cluster, got

Configuring HA

10.1.1.203

Cannot complete the configuration of the

HA agent on the host. See the task details

for additional information. Misconfiguration

in the host network setup.

Misconfiguration

in the host network setup.

Must it have more NIC card for HA? But, on procedure of creating HA, no this requirements.

Thanks!

George

0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

Looking at your screenshots I'd suggest you create the second and third vSwitch with the port groups 172 and 192 which exist on the other host.

André

View solution in original post

0 Kudos
15 Replies
a_p_
Leadership
Leadership
Jump to solution

George,

take a look at http://kb.vmware.com/kb/1019200. This explains possible configuration issues.

André

DSTAVERT
Immortal
Immortal
Jump to solution

Did you check the task details. Names for portgroups etc within vSwitches is often a problem. make sure that names and spellings match.

-- David -- VMware Communities Moderator
George_Yu
Contributor
Contributor
Jump to solution

Hi a.p.

I did followed the instruction. But, I wasn't able to see Advanced options on left pane. Please the picture

Also, you can see the Host with Red Alarm on the left picture

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

To see the advanced options you have to select "VMware HA" instead of "Cluster Features".

However disabling the compatibility check should only be the last option!

André

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

Hi DSTAVERT,

The names on the vSwitchs ware same. But, on different hosts they had different vNICs, for example, on 10.1.1.201, it had 3 vSwitchs. On network manager switch with Service Console, there were more 2 VMs. Please see the picture:

On 10.1.1.203 (second host), there were only onr vSwitch with Service Console, and no any VM

Are they source of the problem?

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

Sorry, the first picture here.

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

Sorry, the Name of portgroups on vSwitch on 10.1.1.201 has corrected. But, the proble is still there!

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

You should have the same network configuration/portgroups on all hosts in a HA/DRS enabled cluster. Otherwise the cluster wouldn't make sense since a failover of a VM to a host which does not provide the configured portgroup would not work.

André

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

On the Task Detail:

Cannot complete command 'hostname -s' or returned incorrectname format.

Hi a.p.:

Do you mean configuration of the vSwitch with Service Console should be same for all hosts?

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Looking at your screenshots I'd suggest you create the second and third vSwitch with the port groups 172 and 192 which exist on the other host.

André

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

Yes. You should be right.

"To see the advanced options you have to select "VMware HA" instead of "Cluster Features".

However disabling the compatibility check should only be the last option!"

I found out the right way to do it. But, the problem is still here.

I'll try to make the all vSwitch same to see the result.

thanks!

0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

I would also try to get into the habit of creating names without spaces. I also like to make all names lowercase as well but that's just me. Use the underscore or use dashes rather than a space. Far easier to find things or script things when you don't need to take care of escaping spaces.

-- David -- VMware Communities Moderator
0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

Hi,

I have changed name of portgroup and configured vSwitchs same. But, the problem is still here. Please see pictures.

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

I mean I only had one vSwitch on each host and no VMs on them.

0 Kudos
George_Yu
Contributor
Contributor
Jump to solution

I discoved vNICs still were able work well without any vSwitch.

I mean like I said I did not put any VMs on vSwitch before, these VMs can work well.

0 Kudos