Topics created by David Schneider

The NIC bonding isn’t difficult to achieve, I just followed the guide at [url]https://help.ubuntu.com/community/UbuntuBonding[/url]. There’s also a handy guide on a similar vein at [url]http://www.beyondvm.com/2014/03/quick-tip-bonding-lacp-and-vlans-in-linux/[/url] which adds some of the Cisco CLI commands

My etc/network/interfaces ended up as:

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet manual
bond-master bond0

auto eth2
iface eth2 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
address 192.168.1.60
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 8.8.8.8 8.8.4.4
bond-mode 4
bond-miion 100
bond-lacp-rate 1
bond-slaves eth1 eth2

… which provides for a single ‘bond0’ virtual network interface that you set up beforehand and refer to as the main interface when installing Fog. If you want even more network bandwidth you could add another two port card and add these interfaces as eth3 and eth4 into the mix too but the limit would be the disk throughput I guess - and the network infrastructure. As everything is isolated and local the latter isn’t an issue for me.

Of course you do need a lan switch that supports LACP (a.k.a 802.3ad). On my sandpit system at home I have another N36L Microserver with a two port pcie-e (Intel) network card running into ports 1 &2 on a DLink DGS-3324SR switch. The latter was pretty easy to set up for LACP from its web interface. For the Cisco '3750 I may need to do some reading 😉

I’m very interested to see what performance the ssd’s will achieve on my new box. I figured that the vast majoriy of the time as I’ll be reading from them when imaging back to the G1 tablets I shouldn’t see problems related to trim settings. Time will tell !

HTH
Robin

[quote=“David Schneider, post: 26216, member: 23828”]A request that I got for the machines is that the machine cannot be booted up after imaging the laptops. I don’t know why he just said that they need to be on the domain for the laptop to be loaded up. What I did was took his sysprepped .gho image sent to me on a thumb drive and loaded one of the laptops. After loading the laptop I pulled the image off of it using fog. He just want to be sure that the laptops get shutdown after imaging not booted up to the my sysprep screen. Something there gets corrupted if the initial settings are done off of the Domain.[/quote]

Are the machines you are imaging suppose to be part of a domain? if that is no longer required, I would disable these settings before pushing the image to FOG.

I kind of gathered that you are using a .gho image and loading it to the laptop, did you boot the laptop to windows before you pushed it to FOG?

Windows has a process called Sysprep that generalizes the installation so it can be pushed to mulitple machines, if you allowed the laptop to boot after it was imaged and before it was uploaded to fog… Delete your image store, load the .GHO image to a laptop but DO NOT BOOT IT, instead set up a task on the server for an image upload. After the process completes, try to push your image to the laptops.

I normally append a sudo to every command that installs, or edits, you will usually need the root permissions to complete the actions properly.

if you run a command and ti doesn’t work because you for got to sudo you can use what is called a Bang Bang to recall your last command and just put sudo in front of it.

For example:
[code]
ln -s var/www/fog /var/www/html/fog[/code]

Would fail, you need root privileges to move things to that folder, or you have to be an owner of that folder.
so to re run the command with the terminal still open you can either press the up arrow and scroll back to the beginning and type sudo, which sometimes is the best bet. Sometimes I make errors when my fingers get excited and type isntall 😛

or you can use the BangBang
[code]
sudo !![/code]

There are others this is just easiest.