Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

ESX Installation date

$
0
0

 

Hello all,

 

 

 

 

 

I am in a bit of a dilemna, the time has come for me to rebuild some of my ESX servers.  It used to be such an easy process, I have configured the UDA appliance to assist in my ESX deployments.  The UDA is running DHCP and it is correctly configured, I know this because I can create a new test VM and set it to boot from the network card and I get my UDA "Select OS to install" screen.  But when I boot a ESX server, it will not acquire an IP address from the UDA and when I review the UDA's DHCP logs there is no indication that the ESX is communicating with it as opposed to my test VM where I do see events in the UDA's logs.

 

Now to the question of this posts subject, recently we applied some patches to the blade center chasis.  How can I verify my ESX installation dates to see if the update broke something related to the NIC's ability to brodcast a DHCP request, rigth now I am going off of the modification date of the anaconda-ks.cfg file located in /root.  Am I wrong in assuming that was the installation date?

 

 

 

 

 

As I mentioned before this was an easy proccess and it has worked wonderfully before, I am racking my brain trying to recall what changes I have made and right now all I can think of is the update to the blade center.  FYI, I am running 10+ ESX 3.0.2 patched up to date hosts in two datacenters with VirtualCenter 2.5.

 

 

 

 

 

Thank you

 

 


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>