ESX Deployment Appliance (EDA) is a small and easy to use appliance
that makes deploying ESX servers a breeze. It has a very intuitive
web-interface that can configure and deploy dozens of ESX servers in
minutes. It has a script-builder that will allow any admin to create
%post-scripts that will do most anything one needs to get the ESX hosts
up and running! Even if deploying with RDP/Altiris or the UDA, this
script-builder can help setting those up very quickly.
Try removing the vNIC from your appliance and re-adding it.
Also, are you running this on workstation, or ESX(i) - either wya, make sure that you are using the correct networking type for the NIC to allow traffic flow
some more info:
To set it up, just attach a ESX3 iso to it. It will automatically mount it and with one click, import the PXE bootfiles and strip the HBA drivers to do a save install while SAN LUNs are attached!
It also shares files with samba which makes getting files to the ESX host during installation very easy. the scriptbuilder will insert the correct scriptpieces to read files from the DL share (this is a readonly share). to put files on the EDA, go to the DL$ share (with the dollarsign) as root user.
I am trying to set up the UDA but I am getting an error when trying to install the image. It tells me that it can not find the proper path. Unable to retrieve It will state http://192.168.20.1//'esx/esx301/vmware/base/Netstg2.img. Where is it getting the IP// from?
first, this is the EDA, not the UDA but that's ok, the UDA is a great appliance too.
but that IP address is the address you gave your EDA, or at least it should be. if it's not, try adding a new esx server. this will generate a new pxe-boot config where the ip is filled in.
if it still won't read the netstg2.img, try importing the pxe files from the CD with the link on the main page. could be the built-in pxeboot files are for a slightly differnet version of esx than the one you're using.
Couple of things... The fixed IP makes it a pain to configure. I am more of a RH linux type, so the debian Ubuntu made me figure out how to change the networking. No huge deal, I just changed /etc/network/interfaces. I could not figure out how to do a "service network restart", so i ended up rebooting. (How do you restart networking in debian??)
Maybe it would be better to set up as DHCP? I usually use UDA within VMware Workstation from my laptop for mass deployments. I had to tweak the .vmx to get it to work in Workstation.
I didn't get a chance to rattle its cage yet, but the kickstart build wizard looks promising....
to restart the network you can restart the init.d script (as you can with redhat) like '/etc/init.d/networking restart'.
but in the appliance you dont have to. in the bottom left there's a link to the appliance settings that lets you configure everything from the web interface. if you save that, the network is restarted automatically and the settings will work directly (no need to reboot).
i would use a dhcp number for the appliance if possible (all scripts and ks files it generates are changed automatically when the ip changes) but it runs it's own dhcp server so that wouldn't work too well.
You know...I wasn't thinking the pxe part!! And I completely forgot about the networking restart. Thanks.
that's odd.. i just tried an was perfectly able to get the files. just in case, here's the direct links:
scp it to a vmfs partition and then import it. Or use VMware converter.
exactly. i usualy run it on my laptop in vmware server or workstation and install the first couple of hosts, then create a VC (virtual) and import the appliance with the built-in converter. but creating a new VM and copying the diskfile over with winscp and importing it with vmkfstools works well too.
Edit the settings of the VM or edit the VMX and point to the ESX image.
Sorry, I mean how does one mount the ESX .iso which is to be used in the deployments get mounted for the appliance to use, in the UDA you have to put it in a folder on the appliance called DISK2, is it similar here, or as you state is it a case of just attaching the iso to the vm as if I was building a vm.
Read the top of the post...just attach it as a CD
if the CD is not mounted you can't import PXE files so that seems to be working.
as for the netstg2 error, that's unfortunately a common redhat error that doesn't seem to be easily solved. i get that too sometimes and it helps to move the EDA from vmware server to workstation or to ESX. or sometimes a different network card in the host or a different physical switch helps. no idea why this happens. if possible, try putting a crosscable between your host and the appliance (the host it runs on). at least you'll know it's got something to do with hardware.
i'm trying to find a fix for this because it's annoying even if it does only happen on one out of 10 setups. if i find it i'll put it in the next version.
just attach the iso to the appliance and it will automount it. you can check if it's mounted by trying to import the pxe files or by typing http://your.eda.ip.addr/esx.
if you move the diskfile to some other platform and create a new VM for the EDA, remember to make it a scsi cd or the automount will fail.