Using my poor mans VM lab I always get this error when I am rebuilding the lab …
I always end up forgetting it and have to dig this great post : http://yuridejager.wordpress.com/2009/10/16/remove-the-host-currently-has-no-management-network-redundancy-warning-from-your-whitebox-ha-enabled-esx-cluster/
This is my own little reminder, kudos to Yuri ….
the solution is to add “das.ignoreRedundantNetWarning = true” under ha advanced settings and disable/enable HA
This message appears if the Service Console does not have network redundancy configured properly and can be safely ignored.
To prevent this message from appearing and to comply with proper network redundancy, VMware recommends that you add a second service console on a different vSwitch and subnet. Alternatively, you can add a second vmnic to the service console vSwitch.
To suppress this message on ESX hosts in the VMware High Availability (HA) cluster or if the warning appears for a host already configured in a cluster, set the VMware HA advanced option das.ignoreRedundantNetWarning to true and reconfigure VMware HA on that host. This advanced option is available in VMware Virtual Center 2.5 Update 3 and later.
Note: If the warning continues to appear, disable and re-enable VMware High Availability in the cluster.
To set das.ignoreRedundantNetWarning to true:
1. From VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
2. Select VMware HA and click Advanced Options.
3. In the Options column, enter das.ignoreRedundantNetWarning.
4. In the Value column, enter true.
Note: Steps 3 and 4 create a new option.
5. Click OK.
6. Reconfigure HA.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004700
on install : press TAB and add “nocheckCPUIDLimit” after “vmkernel.gz”
mboot.c32 vmkernel.gz nocheckCPUIDLimit
on first boot : press shift + O at the ESX load screen and type
nocheckCPUIDLimit
Once installed using vSphere client disable CPUID check by unchecking the option:
Configuration -> Advanced Settings -> VMkernel -> Boot -> VMKernel.Boot.checkCPUIDLimit
After a long day restoring my mac from backups I finally started up my virtual machines only to find out my network settings are configured wrong , I use static ip’s on my vm’s so the easy way was to just get my old settings back , here’s how:
Stop all your vm’s , exit fusion and follow the process
1. remove current settings :
cd /Library/Application\ Support/VMware\ Fusion/
sudo rm locations
2. rebuild config ( script does not need your answers ) :
sudo ./vmware-config-net.pl
sudo ./boot.sh –restart
3. change your ip in the locations file :
sudo vi locations
change this line ( for hostonly address )
answer VNET_8_HOSTONLY_HOSTADDR 192.168.119.1
4. apply settings
sudo ./vmware-config-net.pl
sudo ./boot.sh –restart
5. verify
ifconfig -a