that shouldn't happen.. are you sure you hit 'import PXE files' in the EDA?
can you post a (partial) screenshot of your eda where you type 'cat /var/lib/tftpboot/boot.cfg' in the 'exec' box from the 'patch' menu?
Although the person who had the problem don't respond anymore i can confirm that a "Import PXE files" is the solution for the '/tardisks/scsi_bnx.v01' problem.
thanks for that feedback. usually when people don't reply anymore it means that things are working again
I love the appliance as is, use it all the time. I have a thought. Ever thought about adding a multi-script option? This would make it easier to deploy several different hardware configs from one EDA appliance rather than deploy several EDA appliances for each spec.
i've had that request a couple of times but because of the way i built it, that would require quite a large rewrite. i usually advice people to use the backup/restore function on the EDA to do basically the same thing with a couple of extra clicks. i could extend the backup/restore option so switching between configs would be a bit easier (=intuitive). would that help?
Hmm, that might. I'm always up for 'easier'. Thanks.
Hi, can someone please tell me how can I use EDA to do SAN boot. Please explain with examples.
So, unfortunately it's not always a straight forward answer. I only demonstrate for UCS systems, but here is my best attempt from that perspective.
Assuming the following:
- Fiber Channel SAN
- ESXi 5.0
For EDA in the "installdisk" parameter: =fnic
Standard 5.0 U2 or newer ISO will work.
Boot Order, 1. LAN (So you can PXE boot), 2, SAN
You need to target your Directors/Storage Processors where the LUN will be delivered from.
LUN ID delivered should be standardized from your array. Most often this should be LUN ID 0 or 1, but that is your preference. I would just recommend you remember that 'preference'.
Nevermind, I've just realized my incredibly dumb mistake. I imported the OpenManage vib into my ESXi image and importing the PXE boot image using that causes the above error. I made a new image w/o it and it worked just fine. The perils of shortcuts.
On the other hand, not sure why EDA has a problem w/ this particular vib since booting directly off the iso works just fine.
actually, eda should have picked that up. the pxe import reads the boot file from CD and redirects the files on it to the webserver in the eda. the vib builder generates that file and points to the openmanage.v00 which in turn gets redirected by the eda.
so building vibs into your image should work. HP and Dell images work fine and they do exactly the same. if it boots from CD, it should boot from eda as well. it's how eda works
how exactly did you build the image?
Using PowerCLI. Not sure why it was having such issues. Oh well, not an issue anymore.
Any news on v1.10? I've got about 30 hosts to install 5.5 on.
Thanks, EDA is awesome.
I'm probably skipping 1.10
The 1.05 version runs 5.5 perfectly so there's no need for it.
The two small patches on the ntp and syslog targets I built in my 1.10 aren't big enough to go through the whole process of applianicing a new version
Awesome. I'll give it a try then. Thanks!