The prefix- and range-based MAC address allocation schemes are not supported on pre-5.1 hosts because pre-5.1 hosts explicitly validate if an assigned MAC address uses the VMware OUI 00:50:56 prefix. "Prefix- and range-based MAC address allocation is supported only in vCenter Server 5.1 and ESXi 5.1 Now, when reading through the ESXi 5.1 release notes ( ) I came over the following point: Which means, that our configuration - static MAC in 00:0c:29 range is not supported and should not even work (but it did - there seemed to be no verification). Which says that generated MAC addresses should be generally in the 00:0c:29 range, and static MAC addresses should be in the 00:50:56 range. I started googling and found some articles which said to add ethernet0.checkMACAddress = “FALSE” in the VMX file, but this did not work too. In the meanwhile I have upgraded the HP VSAs to 9.5 and the hosts were reinstalled with ESXi 5.0, and recently I started upgrading the hosts to 5.1.Īfter trying to power up the VSA on the first upgraded host, I received the same message as you:Ĭould not set up "macAddress" for ethernet0.Ġ0:0c:29:5f:a0:0c is not an allowed static Ethernet address. Unfortunately I - as well as maybe you - created the VSA cluster on top of that and licensed the VSAs in this way too. As far as I remember the VSA's VMX and VMDK files had to be uploaded onto each hosts datastore and one created the virtual machine by importing it to the host.Īfter that you had to edit the VM's properties to add a disk as RDM for storing the data and if I remember well the next step was to change the MAC address from dynamic to static - and after clicking "OK" this left you with a VM containing a MAC address beginning with 00:0C:29:xx:xx:xx. In my case I installed ESXi 4.0 on two HP D元70 G6 Hosts in 2009 and installed a P4000 VSA (which was Version 8.1 by then) using the enclosed Documentation. I'm having the same problem with the HP P4000 VSA too.
0 kommentar(er)
