Anyone? 🙂

I saw someone asking about it, but didn’t follow through to see if they had it up and working. I was asking more because I wanted input on the specific setup - the Pi is seriously underpowered for what I was thinking of doing

If you go to TCEA next year, maybe we could meet up - I went this year for the first time, but didn’t see your post about it until last week

Yes, and no.

Being that you are new to FOG, I will run through what I tell my staff when I set them up with a FOG server.

After your FOG server has been set up, You have to do as Gilou suggested and give the option 66 and 67 options to your DHCP router properties pointing to your FOG server. Set a machine to PXE boot and test to make sure that the FOG pxe boot menu displays.

(IF no PXE menu display we can troubleshoot)

Now that PXE is enabled, I would begin working on my image ( I work virtually but to each his own).
After your image is complete you are ready to upload.

[B]Image Management[/B] will allow you to create images, this [U][B]MUST BE DONE PRIOR TO IMPORTING A HOST TO YOUR FOG[/B][/U]
[U][B]SERVER[/B][/U], otherwise you will have to create one and select it later, manually.

Navigate to your FOG server web GUI. Click “[B]Image Management[/B]” the 5th icon over from the left. Click “[B]New Image[/B]” on the left. Give the image a name, a description, select “Default” for Storage, and give the file a name, [U]no spaces[/U]. Select Multiple Partition image
– Single Disk (Not resizeable) or Multiple Partition image – All Disks (Not resizeable) (these work best, you can use the others, but if you use Windows 7 I [B]HIGHLY[/B] recommend the Multiple Partition modes). Click Add.

[SIZE=2]Now that you have an Image store, you can begin [/SIZE]registering[SIZE=2] a host and imaging.[/SIZE]

You will need to register each unit as a host to the FOG machine, [B]INCLUDING THE MACHINE YOU MADE YOUR IMAGE ON[/B]! I normally register my “imaging machine” as Master or something so you can tell it apart from the rest. Boot your machine and select the PXE boot option. When you are confronted with the FOG PXE screen, register the host (quick registration will get the machine into the web GUI under host management but will still need to be assigned an image.) I recommend using the Full Registration mode, this will allow you to select the image store you previously set up. [B]DO NOT TRY TO QUICK IMAGE YET!!![/B]

Now that you have a registered host and an image store, you can tell the machine to upload it’s image to the FOG server.

Go back to the web GUI, select “[B]Host management[/B]” the 3rd icon over, click “[B]list all hosts[/B]” on the left. Select your “Master” from the list. This will load the machine information, here you can see how you can manually update the information (in case you want to rename, or remove) on the left click “[B]Basic Tasks[/B]”. Click “[B]Upload Image[/B]” your machine should reboot (if not power it off and back on the FOG server can use Wake-on-Lan to wake up and shut down machines but it is an unreliable technology.) Your host machine will begin uploading.

You may go forward with registering your T5370s buy registering the machine to the FOG server and selecting your image store, you may now complete the quick image from the registration menu.

Based on my understanding,

Your IP DHCP Range changed from 10.140.252.x to 10.140.190.x?

Was this an on the fly change?

Did you make the changes to your FOG Server configurations? TFTP, WEB_HOST, FTP?

Have you restarted your fog server since DHCP took over? Or at the very least the apache server?

The reason you’d not be able to access the web server (10.140.190.82/fog) sounds like you changed the network but did not restart the apache service.

You’ll run into all sorts of other issues though unless you make the configuration changes. Many of them will be on the Web GUI, but you’ll likely need to make the change to your /tftpboot/pxelinux.cfg/default file as well. All references to the old IP will need to be updated to the new server address.

Hi,

What does your C:\fog.log say about it?

Cheers
Gilou

Here is the thread mentioned by Raff:

[url]http://fogproject.org/forum/threads/minor-change-great-improvment-multicast-i-love-you.8005/[/url]

We haven’t tried it at our place yet, but the theory of it makes sense.

It is a good idea to try using a “dumb” switch as a multicast test. Smart switches might see heavy multicast sessions as a storm or flood control target. Or perhaps they will throttle the heavy traffic. I needed to tweak our switches to allow multicast at a decent rate - I got 700mb/min for multicast but 4gb/min unicast - in fact I could start 5 clients unicast and still finish before 5 clients multicast. Using a dumb 1gb switch I got close to 2gb/min multicast.

The sweetspot for me (multicast) seems to be >5

ok we are finally getting somewhere…[B]FYI if clients are trying to use FOG as the DHCP server you need to modify this directory as well if your modifying your pre-existing FOG servers ip information for a different site location.[/B]

/etc/dhcp/dhcp.conf - this was the culprit for me, it still had the old ip address information and I also discovered I can narrow down the dhcp address scope here as well.

You’re welcome,

For the future, when you’re building a base image, inventory into fog but tell fog not to join it to the domain. Then upload the image. This way you don’t have to disable the FOG Service.

Your method works, but if you have to restart for anything before the upload process, the Service will try to take over and could join the domain, lets just say you had to go to the bathroom while you waited for that restart.

Once the image is uploaded, then go ahead and enable join domain for that system should you need to.

So,

As you’re limited to the number of available DHCP addresses to hand out within your network, does your fog server have more than one interface?

You could install the DHCP Server tool onto the FOG Service and have it hand out requests through a specific interface. If you only have one interface, you can still do the same type of idea. Though it’d be better that your server is set to a static IP address if they at least provide the one. When you need PXE boot, have the FOG Server serve a range of IP’s outside the scope of your current setup.

For example,

Let’s say your 300 systems runs on the IP range of class B network: 172.16.xxx.xxx, (this ensures the 300 possible IP’s and then some) And you set your fog server to be dhcp for a class C network: 192.168.xxx.xxx. When the systems boot using ports 66/67, (PXE boot phase) they should pick up the IP address from the 192.168 series and be able to PXE boot to the fog server as it’s the only one handing out that IP range. When the systems boot up, they shouldn’t be requesting IP’s from the FOG Server, as they’ve already passed the TFTP phase of the process. I’ve never really had to test this too much, but if the FOG Server is handing out IP’s, you can set the scope inside the fog server to point the dhcp server to your main network so there’s less confusion.

If everything is working for you, i’d say just keep it the way it is. No need to fix it if it isn’t broke. The only reason you may want to upgrade the compatibility to level 10 is that you can up your hard drive space from 2TB to 62TB per drive. We needed to do this for a couple of our servers, but it’s rare that you would need a VM with that kind of space. But then again, you’d need VMWare Workstation or vSphere to edit it from there.

Now if they offered HA for 2 free ESXi servers, just for absolute basic redundancy, i’d be in thrilled. We are on a strong push to move our teams to VM’s instead of having actual boxes at their desk for testing.

While I don’t know if you’re trying to use a linux setup to host the deploystudio or trying to use a mac machine to host the fog server, I think the method that would, conceivably, work the best would be putting the FOG server on a mac machine. Deploystudio, to my knowledge works on different protocols than PXE so both can exist at the same time.

The best method I could think of would be to install FOG on the DeployStudio Server by porting the needed modules.

You’d probably need to install a tftp server, web server, mysql server, and depending on your needs, a dhcp server.

The install script from the site would probably not work for your setup, but you could install the components required individually. This is not something I could walk you through in one day or anything but I could try to think of all the components you’d need.

First,

apache, php 5.3 or higher, htmldoc, mysql, tftp, nfs, and ftp would be the first things to install and get working.

Once you know the setup is working with all those components, you’d probably have to do some heavy tweaking in the web gui side to get it to work properly with the system.

While it would be a lot of work, I don’t think its impossible.

the FUN just keeps on coming…

DAY 3
Decided to bond the NIC’s

again… googled the hell out of it, surprisingly, there is no result for Fedora 15 nic bonding, save the official docs from Fedora that clearly articulates how to achieve bonding…

HOWEVER, not once did they mention that you needed to chkconfig NetworkManager off, nor did they mention to service NetworkManager Stop…
They failed to mention that when bond0 comes up, for some reason eth1 still holds an ip address, and that ifdown eth1 then ifup eth1 gets it to behave… then ifdown bond0 followed by ifup bond0…

they failed to mention the horror when you can no longer ping anything… not even the router even though all settings in the ifcfg file are correct and you’ve quadruple checked ifconfig -a output…

endless googling finally reveals that “perhaps” you may need to add a route by tying route add default gw 192.168.x.x dev bond0 which doesn’t seem to persist on network restarts…

suffice it to say, blowing away the server and re-installing crossed my mind on several occasions…

the result???

I have internet access but I can only ping computers on the same subnet, all other computers on any subnet can ping me… thats fine for now because imaging is working… again…

note to self… charge more for this $h!t in future…

[COLOR=black][FONT=FangSong]This is an amazing deal, you get a Meraki MR12, the Power Supply, and 3 years of the cloud management license.Its Prise 700$.Youlern more clicl this site [/FONT][/COLOR][B]leadmesh.com Think you. click this linl [/B][B][URL=‘http://anonym.to/?http://www.leadmesh.com/’]:) [/URL][/B]

Solved, At first step in windows machine, I shared in haneWIN NSF server c:\FOG_IMG like /images.
And as you said, system cannot move /images/dev/${MAC} to /images/{IMAGENAME}.
I’ve created a subfolder c:\FOG_IMG\images and I mapped it to /images.
I don’t understand the reason but after this It works and moves the images.

Thank you

Awesome glad it worked out, have fun fogging 😄

I do the same thing.

I’m in East Coast