Just got off the phone with VMware support. Bottom line per them is that it is a bug that needs to be fixed with VC so expect a patch to come out. Supposedly HA will work fine once installed, even with the warning message. It is there from an isolation response perspective and is a highly recommended setup. Me being the paranoid person I am an not wanting to see this 'warning' message, we worked through the process of removing it and what has already been discussed is the work around to getting rid of them.
What I did -->
First, I disabled HA. I had one vmnic dedicated to my service console and one dedicated to VMotion (2 separate VSwitches), I combined the 2 into 1 VSwitch with both port groups, teamed the vmnic's and made sure each physical nic was on a separate physical switch. re-enabled HA and viola, the warnings disappeared. All of my physical nics are 1000/Full so that helps.
Alternate method -->
You can also add a 2nd unclaimed nic to your existing vSwitch (already talked about in other posts) for this purpose and keep the VMotion separate from the service console or you can add another service console (service console2, to either an existing vSwitch or create a new one). I did not opt for either of these as combining them was the easiest and most cost effective solution for my environment. I tested my VMotion after I did this an have had no issues migrating sessions between hosts.
. Possibly to avoid human error? In any case, customers ask questions about it, and with this a 4 pNIC system becomes hard to configure properly for HA (allthough 4 pNIC systems are quite redundant!). So it is still a problem for us. So now we have to go and ship 6 pNIC systems just to satisfy this warning? Seems just a little overdone to me.