Invalid mac address format
-
Hello popol,
I had a similar problem 2 weeks before while testing a new model, and the problem was that the network driver wasn’t installed. If this is your problem, run ‘ipconfig /all’ at a command line and you should see that no IP is configured and the MAC address is 00:00:00:00:00:00.
If this doesn’t work (or you already have done it) try the following:
[LIST]
[]If you have a DHCP server, check that it is giving an IP to the client.
[]Check that the machine is correctly registered in FOG. MAC address should be in xx:xx:xx:xx:xx:xx format, do not use hyphens, spaces, etc. Only : is allowed.
[*]Check that the client is correctly installed and configured.
[/LIST]
Tell us whatever the result is. -
Hello,
This is not an NIC issue, the MAC address is valid, my DHCP server gives an IP to the computer, and the NIC driver (Marvell Yukon 88E8072 PCI-E Gigabit Ethernet Controller) is up to date.
Fog client is also installed and configured.
The computer is working fine, I can join the domain manually, the problem is that I can’t join automatically the domain via fog…
Any ideas ?
Thanks -
I’d hazard a guess that it has something to do with your wireless card. Did you add the wireless card’s MAC address as an additional MAC on the host page in FOG?
-
No I didn’t because the wireless card is disabled in bios but maybe I uploaded the image with a computer with its wireless card enabled ! I’ll try to reupload the image with a computer with wireless disabled and I’ll tell you the result.
-
So I reuploaded the image with wireless card enabled, drivers up to date, I added the additionnal mac adress in fog host settings, I reinstalled fog client and I still have this error : “unable to continue MAC is null” Any suggestions ?
-
Hmmmm… what do you get from running ipconfig /all? I wouldn’t be surprised if it was something like a bluetooth adapter or VPN tunnel adapter being used instead of the NIC.
-
Hello,
I don’t work today so I don’t have access to the problematic computer, but as far as I can remember with ipconfig/all I only get my ethernet card (no bluetooth or vpn). But if it would be a conflict between NIC and bluetooth adapter for example, I won’t be able to deploy the image right ? And I don’t have any problem with imaging, only with snappins deployment and AD integration. Weird… -
I’m not deeply familiar with the FOG client service, as I haven’t used it for a while and I never really examined all the code, so perhaps there is somebody else who might better understand how it works and help you with these issues, but I’ll take a shot at explaining it as best as I understand it.
All these various MAC addresses are used to identify the host. I’m pretty sure that the first MAC listed needs to be the addresses of the NIC that the host will be PXE booting from, as that is the address used for creating tasks. The additional MAC addresses are alternate ways of identifying the host to handle situations with the FOG client service seeing other addresses than that of the NIC used for PXE booting.
Example: The host boots into Windows and the FOG client service starts; the first thing the service does is attempt to contact the server and check for tasks (reboot for an image task, pull down snapins, etc.) and provides the first MAC address it finds. While the MAC address provided to the server by the client may not be the address used to create the tasks, the server will check against all known MAC addresses to discover the host ID, and then check against that host ID to discover any tasks associated with that host. I’m not sure how the service is grabbing a MAC address, and it appears to have trouble occasionally with grabbing the wrong one, which is why its a good idea to add all of them.
-
Hello, We bought a new motherboard and I am not able to register it on fog server. Though fog web page give me an error which says “Unable to register host: reason Invalid mac address” and the computer already have network connection though domain controler. Also the same computer gave me error hdparm (bla bla [URL=‘http://forums.fedoraforum.org/showthread.php?t=277735’][COLOR=#660099][FONT=arial][SIZE=3][COLOR=#000000]inappropriate ioctl for device[/COLOR][/SIZE][/FONT][/COLOR][/URL][FONT=arial][SIZE=3][COLOR=#000000]) [/COLOR][/SIZE][/FONT]when I tryed to register it via tftpboot. Now I am not able to push snapins on that computer. This only have ethernet connection. There is a huge database with every mac address and this one is not loaded or something like? Thanks in advance
-
Orphen,
It sounds like the reason you received the Invalid MAC address is the kernel recognizes the loopback, (which doesn’t have a MAC address, therefore it’s invalid) but it doesn’t recognize the physical interface itself. To verify, boot PXE and select Compatibility to find out if the kernel recognizes the HDD and Network. My guess is that it can’t find your network adapter.
The hdparm issue is not really an issue. That, from what I’ve found, is just letting you know that the kernel has HDD Drivers and has found support, but the drive isn’t loaded in that particular mode. It’s nothing bad, just letting you know that it’s not the appropriate controller to how the device is setup.
I’d recommend starting by finding out if your kernel has your network adapter which is what my best guess is the issue here.
I have built a kernel that, for linux, contains all Ethernet and USB Networking adapters.
You can download it at: [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
Or you can wget it with:
[code]wget --no-check-certificate http://mastacontrola.com/fogboot/kernel/bzImage[/code]Hopefully this will help you out.
