Posts made by jcook

The first image is my current config with both options passed. I have also put the fog IP in the “TFTP Server” of the second image. Either way it still asks for the tftp server IP, and once input it now boots to fog.

Here is where a new problems occurs. The fog boot options are only there for a second and I would like to make it just a few seconds longer, but I can load “Fog Configuration” in the web UI. I get a 404 error with the following text
“Not Found
The requested URL /static/index.html was not found on this server.”

It is something to do with a content filter we have. Its blocking the http traffic to the fog server and i will fix that. I still had to put in the tftp server IP. The router has a place to give the a tftp IP and setup option 66. I will try a few different ways and let you know. I feel dumb for totally forgetting about the content filter >_< doh!

Our DHCP is handled by a Adtran Netvanta 3140. I think at first the clients on the 165 subnet were trying to use 172.18.165.1 as the tftp server so a rule is in place to forward it to fog (172.18.164.6). Clients could get to the fog boot screen after those changes on old fog server running 0.32 so i thought we were all good.

You were correct about the previous cap, I’m a networking novice. Here is the capture file

0_1460744849002_bootup.pcap

Also as a test I set up a new router and move the fog and client to it on a dumb switch and everything seems to be working. I was a able to get to the fog boot screen so its must be something with network I just don’t know enough to figure it out. I am going to see if I can get STP disabled on the network to see if that does the trick.

I took a packet capture from the time the client booted to a minute or so after it asked for me to put in the tftp IP. The mac address for the client is
78:45:c4:0e:5d:a3 and fog server is 172.18.164.6 it that will help to filter. If more info would help interpret the cap let me know.

https://drive.google.com/file/d/0BxsOsMJZGNhYWklZNldIUWpCcU0/view?usp=sharing

@george1421 No they are on separate subnets.

@Wayne-Workman I get the following (I changed the IP to my fogserver):

#!ipxe
set fog-ip 172.18.164.6
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://172.18.164.6/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.quickimage Quick Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.18.164.6/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.18.164.6/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.quickimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.18.164.6/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://172.18.164.6/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

DHCP is much faster. It asks for the tftp server and after entering it I get the above and it seems to hang.

I am actaully a lone IT guy here at a small school. The firewall and core switches are in my “office”. My understanding ( and I may have things wrong) each vlan has its own DHCP server. Our “Wired” vlan has the fog tftp info, but the “Management” vlan has a tftp server for out access points. However for the “Management” vlan the tftp sever isn’t supplied via option 67 but another setting in the DHCP server. Should I try leaving the other tftp setting alone and adding the options 66 and 67?

Should I put the dumb switch between the client and the core, the firewall/dhcp, or just between the client and a smart switch( if that mkes since lol)?

EDIT: Also is this something I might be able to fix by adjusting RSTP timings?

I have upgraded to trunk and this is what my PXE boot looks like, I noticed another error I might have over looked. Since I’m not sure what any of it means Ill just let u see the screen shot. This is with undionly.kpxe.

Also I forgot to mention the fog server and the clients are on different vlans. I was thinking of moving fog to the same vlan and see if that helps just not sure it will.

When I go to the “Kernel Update” section of the GUI I don’t see an indication of my current kernel. I don’t mind trying updating kernel to make sure I have the latest, just not sure which to choose.

Also upgrading to trunk isn’t a problem either if someone can point to guide I can do that too or first.

Using ipxe.pxe i get the original error again. With undionly.kkpxe "Could not start download: Operation not supported (http://ipxe.org/3c092003).

In another post (that I think most of you were helping me with too :D) I was trying to use .032 and I think the error was the same. I am beginning to believe its the network and not fog. I might try to see if Adtran support can help me if I can explain the problem to them.

I get this on the server:

/var/www/html/fog/service/ipxe/bzImage: x86 boot sector
/var/www/html/fog/service/ipxe/bzImage32: x86 boot sector

I will also try those suggestions now and report back.

I didn’t make any changes really yet. I started getting the error after I first tried to PXE the 3010. How can check the kernel version?

Right now a Dell 3010.

Looks like RSTP was already enabled. I am trying to find if there are any green ethernet settings.

It looks like it does, networking is not my strong suite unfortunately. When I get in one of the switch UI’s i noticed there are setting in the STP section. EDIT: I did do some reading and then check the STP settings again and wanted to give an update incase it helps. The swithes are using Rapid STP (802.1w).

After a new install of Fog 1.2.0 on Ubuntu Server 14.04 LTS I having issues with getting to the PXE menu. I get something like “Error 040ee119”. The machines that I have tried it on get the same error, we have Dell 3010 and older Dells.

I set the option 66 to Fog server IP and 67 to undionly.kpxe.

I saw another thread about getting the latest version of undionly.kpxe which caused the PXE boot to hang it seemed.

I have not tried anything with the fog kernel. Any ideas are appreciated. I can provide any other troubleshooting information needed.

Thanks

Sorry for so many relies, seems to be an issue with mysql, after a restart of the service I’m able to log into the web UI.

After the 2nd install I rebooted the VM. When I try to go the web UI now it asks me update the schema, but when I do it fails. I think the database was already there and now there are issues. Since I have moved beyond my original question should I just start a new thread?