Hello all:
We have been using AutoDeploy with host profiles in our environment for the last year or two and it has been working great with our Dell hardware. In our new UCS environment where all the nics and hba's are virtual we have hit a problem. We recently deployed 48 hosts later to find out that the MAC pool for the UCS environment was setup the way it needed to be. We had to delete the MAC pool and create a new one. Problem I knew we would have is that'd I'd have to change all the dhcp reservations so pxe would work for AutoDeploy. The problem we are having and this is really my question is this....... The blades are pxe booting just fine. ESX deploys. But then it starts talking about some host profile stuff and then the server doesn't get its IP again from DHCP. My guess on the reasoning for this is that we take all four of our "physical" nics and as part of the profile attach them to a vDS. I'm wondering if as part of the host profile and the fact that we have the vDS if the mac address is "cached" somewhere in a database or something. When I go to the console of a host and go in and edit the network information you can see that none of the nics are selected as being used for mgmt. I guess maybe this is working as designed since we use all our nics in a vDS. The only way I've been able to fix it thus far is by shutting down the host, removing them from vcenter. Power them backup and let autodeploy redeploy the image and have them get recreated in vcenter. I then had to redo all the answer files and redo applying the profiles. Sorry for the rambling.....Thanks for the help in advance!