VMware Cloud Community
RParker
Immortal
Immortal
Jump to solution

vmxnet - MAC Not valid range?

00:50:56:a1:25:34

What's wrong with that MAC address? Edit a VM (powered off). Copy the MAC address of the existing VM, now remove that NIC, add a enhanced vmxnet NIC. Now edit the MAC to be manual, paste that SAME MAC you just copied, you will get an error MAC must be in valid range 00:50:56:00:00:00 to 00:50:56:3f:ff:ff.

OK, so what's wrong with that MAC that was JUST being used, it's not valid even when it's removed? And the error message says its not valid, why not?

0 Kudos
1 Solution

Accepted Solutions
Troy_Clavell
Immortal
Immortal
Jump to solution

maybe you can try to set it at the OS level instead?

http://kb.vmware.com/kb/1008473

I could be wrong, but according to the KB below, you are out of range

http://kb.vmware.com/kb/507

your vswitch or port group is set at the default to accept mac and forged transmits?

View solution in original post

0 Kudos
5 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

maybe you can try to set it at the OS level instead?

http://kb.vmware.com/kb/1008473

I could be wrong, but according to the KB below, you are out of range

http://kb.vmware.com/kb/507

your vswitch or port group is set at the default to accept mac and forged transmits?

0 Kudos
Jasemccarty
Immortal
Immortal
Jump to solution

Was it originally setup as automatic?

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

Please consider awarding points if this post was helpful or correct

Jase McCarty - @jasemccarty
RParker
Immortal
Immortal
Jump to solution

Was it originally setup as automatic?

Yes but I figured (I don't do this very often) I wanted to keep the same MAC so I don't have to release / renew every time. So I changed it to static hoping it would accept it. It's in the 'valid' range but apparently not...

So if you want to switch VM's to enhanced you have to do a lot of work, which is now yet another issue.. fun!

0 Kudos
mcowger
Immortal
Immortal
Jump to solution

the valid ranges for generated MAC addresses and static mac addresses are different. Both are in 00:50:56, but different subranges of that.






--Matt

VCP, vExpert, Unix Geek

--Matt VCDX #52 blog.cowger.us
RLX
Contributor
Contributor
Jump to solution

Hi howdy, I found a solution.

You can set custom MAC addresses but only for flexible adapters.  Here's how:

1. Shut down virtual guest

2. Remove your E1000 / VMXNET3 adapter

3. Add a new NIC and select the flexible option

4. Set the new NIC to manual and put in an addresses VMWare is happy with (e.g. 00:50:56:3f:ff:ff)

5. Remove virtual guest from inventory

6. Edit .vmx file (via command line or download from datastore)

    ethernetX.address = "Whatever MAC Address you want"

7. If you downloaded the .vmx file upload it

8. Add .vmx file to inventory

9. Edit settings to verify 'correct' MAC addresses is present

10. Boot virtual guest

I have not tested this with VMXNet2, it may work for that as well.

0 Kudos