No COS NICs have been added by the user

I’ve been struggling with this error message for moths and I’m not the only one. Duncan Epping over at Yellow-Bricks has experienced similar problems.

When using PXE and kickstart on ESX 4.x, the ESX boots from PXE but the installation fails and in the DHCP server logs there is a new unauthorized client requesting an IP. VMware has released a knowledge base article with the resolution for this problem.

During the installation of ESX 4.x, the VMkernel starts and it boots the service console in a virtual machine. As such, the service console is using a virtual MAC address that is generated randomly at runtime. During the install, the MAC address is written to disk and becomes persistent, but each time you boot the installer, the COS MAC is different.

If you are using MAC address based access control in DHCP, deny unknown-clients, you cannot authorize the service console to get an IP from DHCP. There is no way to predict what the vswif0 MAC address will be.

In large deployments, specifying static IP addresses is not convenient. You would need to create a separate PXE configuration for each host. To workaround this, put the IPAPPEND 1 parameter in the PXE configuration for the host.

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=1012248

Comments

Display comments as (Linear | Threaded)

Your issue may be unrelated but this is a common "error" when using the UDA to manage PXE based setups and it's known to be a red herring. The message is common even with successful installs but generally of no significance and the scripted install will continue if there are no genuine problems. However if a separate issue that causes the install script to fail this message is often the last message displayed which can be very confusing. In the UDA PXE config case the root cause of the failures in my experience has always been unrelated to the COS NICs despite the presence of this message. This VMware communities comment http://communities.vmware.com/message/1451945#1451945 identifies issues with the COS partition sizes as being a likely root cause.

#1 Joe Mansfield on 2010-05-19 23:59 (Reply)

Name
Email
Homepage
In reply to
Comment: Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.

Enter the string from the spam-prevention image above:
: Remember Information? Subscribe to this entry
Submitted comments will be subject to moderation before being displayed.

Eric Sloof - NTPRO.NL

Tuesday, 18 May 2010

No COS NICs have been added by the user

Recent Entries

Archive