Ran into an issue last night during a 4.1 upgrade, that I'm a bit stumped on at this point and just wanted to get some clarification.
I was upgrading an existing environment that I had not setup. I patched the hosts from 3.5 to 4.1 along with vCenter. The upgrade went fine and everything was working beautifully. I then enabled HA on the cluster, which configured fine, but I was given the message that the management console was not redundant. So, I went and saw that the management console only had 1 physical NIC assigned.
Well... i removed one of 4 NICs from the VM network and assigned it to the management console network. At this point I was unable to communicate with the host and the VMs that were hosted on it were unreachable as well!
HA was configured to shutdown all VMs in the case of a HA event so, I'm assuming this is what happened.... but my question is.... is this normal behavior when adding a 2nd NIC to the management console? I left the original NIC that was there alone... so I was kinda surprised at this behavior. Was wondering if I could get clarification on what happened.
Thanks!
Welcome to the community.
this normal behavior when adding a 2nd NIC to the management console?
No. Check switch configuration and also if you are using a team policy different than the default one.
Andre
Forgot to respond back to this one several months back. Found out after looking into the networking a bit more that the previous IT guy had setup etherchannel. Removing the NIC broke the channel. Problem solved in case anyone was wondering.