1 of 1 people found this helpful
This sounds like a hardware issue.
Can you run kickstart on this box w/ the same settings w/o blade ?
Perhaps you need to pass some specific kernel options during the build for this hardware ? like disabling acpi or something ?
I've been told that there is an issue with the NICs on the ESX hardware on which the BBSA infrastructure is sitting, and have been told by the customer that they want the datastore migrated to a NAS. This is a great idea and all, but since linux provisioning requires(afaik) http connectivity to the datastore, the fact that the data will live on the NAS won't really make any difference, as the only machines they'll provide with a webserver on them would just be a VM with NAS access, which means that the file transfers for linux would be entirely unchanged.
So then, my question is, is it possible to force a linux provisioning job to use samba or nfs, instead of http?
is there any hope to resolve the issue w/ the nics? or more details about it? is bsa the only thing affected by this?
you can customize the kickstart file and change the url to use nfs or whatever else anaconda supports. you will however still need an agent that has access to that location so the appserver can write the ks.cfg file in the root of the datastore.
The problem, it seems, was the firmware level on the hardware. Or at least, updating it to the latest level seems to have resolved our problem.
Thanks for the help, Bill. I have a feeling we'll talk again.