Skip to main content

Hello all,



I've run into an issue with the NetBoot/SUS Appliance has halted all progress in evaluating the Casper Suite.



When logged into the web page for appliance administration, I am unable to upload any NetBoot images. I've tested this on multiple browsers and client OS versions. The button simply doesn't respond. No prompts, no errors, no upload file dialog, nothing (In Safari). When I tried in Google Chrome, I at least got an error:



external image link



I got around that by simply mounting the smb share by guessing smb://hostaddress/NetBoot. Once I uploaded my .nbi to that directory, it showed properly in the NetBoot Appliance Administration page. I entered in the server's IP address for the subnet (not sure if that is the accurate information to place there) and I entered our mask. When I press the "Enable NetBoot" button, nothing happens in all browsers I attempt to enable in.



external image link



I've got no ideas left as to what to try next. Any help is appreciated. Thanks so much.

Try changing your subnet to 10.10.24.0

Thank you, I did that but it still will not enable. I also verified that the upload button doesn't work as well.

If you look at "/etc/network/if-up.d/configurefornetboot", you will see that the variable $ip needs to have the NIC pointing at eth0. If you check "/etc/udev/rules.d/70-persistant-net.rules", make sure there are no entries allocated to eth0 as it will jump to the next availble NIC. Moving the VM to different VLAN's can cause the NIC to change.



Also, if you have copied the .nbi to your smb share, and have not been able to upload it, you need to ensure that the name of you.nbi name is set in "/etc/dhcpd.conf". Make sure that the "next-server" option lists your server IP, and that you ammend the .nbi name to mirror your .nbi naming convention.



As long as those two references have been set, a restart should activate the NetBoot service.



Hope that helps.

That is very helpful as I believe I have found what the disconnect may be. Simply running an ifconfig shows that the configured interface for the VM is labeled eth1 instead of eth0. Could a resolution be something as simple as renaming eth1 to eth0? Is that possible? Thank you very much for your help!

Here's what resolved my web interface issues with the NetBoot Appliance. The problem was that my VM had somehow taken on eth1 as the primary network interface and there was no record present for eth0. All I had to do was remove the interface configuration file, reboot, and reconfigure my static entries to reflect eth0. Steps are below:



First, remove the configuration file:



# cd /etc/udev/rules.d

# sudo cp 70-persistent-net.rules /root/

# sudo rm 70-persistent-net.rules

# sudo reboot


Then, edit your interface configuration:



sudo nano /etc/network/interfaces


I simply changed the eth1 entries to eth0 and then ran:



sudo /etc/init.d/networking restart


My particular setup requires a static IP address and since I'm running this VM through VMware Workstation, I needed to manually configure my IP address through the appliance. The link below was endlessly useful in accomplishing this in a quick and efficient manner.



Linux Basics - Set A Static IP
http://www.howtoforge.com/linux-basics-set-a-static-ip-on-ubuntu

jflory,



I have my dhcpd.conf file open and the name appears to match, but there is a lot to look at that I am unfamiliar with. Would you please let me know if the following appears normal, as far as the readout goes. For testing purposes, I only have one .nbi file which is named "108NetBoot.nbi"



next-server 10.10.24.24;

filename "108NetBoot.nbi/i386/booter";

option root-path "nfs:10.10.24.24:/srv/NetBoot/NetBootSP0:108NetBoot.nbi/NetBoot.dmg";


Everything looks great in the admin control panel, but I have yet to see the NBI appear as an available startup volume. That could be any number of other variables, but I need to first ensure configuration is proper at the server end.



Thank you.

Terms & ConditionsCookie settings