No DHCP Response on Eth0
-
just for clarity are you pxe booting a host with multiple network adapters or are you talking about the fog server with eno1 vs eth0?
What manufacturer and model of device are you trying to pxe boot?
My initial reaction is this is a spanning tree issue. Assuming this is a traditional desktop/laptop, lets place a dumb (unmanaged) switch between the pxe booting computer and the building switch. This unmanaged switch will mask the spanning tree issue.
-
@george1421 So I am trying to use an Lenovo T470 laptop. The server has the multiple network ports on the back of it. So when I do an ifconfig on Ubuntux 16.0.4 it comes up with 4 different adapters. I am using 1 which I have configured to a 192.168.1.1. My managed switched, Cisco Catalyst 2960 Series SI Po-E-8 is also set to 192.168.1.1. I will try an unmanaged switch.
My Server is a PowerEdge T710 Here is a picture of the back of the server
-
@george1421
SO I am now getting a new error with the unmanaged switched, maybe I am uploading an image wrong? I went into the management console, created a new imaged,named it Lenovo T470. PXE Booted, clicked ‘deploy image’, clicked Lenovo T470, and where I used to get the previous error I am now getting this one.
-
@bartont126 If you can plug a regular computer into the switch and get an IP address then at this point in time the FOG server is not at issue. Also the snapshot you posted is an image of FOS trying to get an IP address. This means that you successfully pxe booted, loaded the iPXE FOG menu and then bzImage and init,xz (FOS) was transferred from the FOG server to the target computer. So at the moment the fog server is working perfectly.
-
@bartont126 said in No DHCP Response on Eth0:
Cisco Catalyst 2960 Series
So you have a business class switch here. Either change the stp mode to rstp (or fast-STP what ever its called). That should address your issue, or as I said test with an unmanaged switch to see if you can get it past this point.
-
@bartont126 Sorry I didn’t see your second (third) image. That means that the target computer can’t reach the FOG server. Did you happen to change the IP address of the FOG server after FOG was installed? FOG doesn’t like having its IP address changed or assigned by dhcp.
-
@george1421 I made a little more progress.I am now using the unmanaged switch. I was able to register the host computer and the fog management console now sees the host. I then clicked the host, created a basic task to capture the host image computer. I rebooted to pxe which thus should begin to capture the image and now I am getting this error. Also, no I have no changed the IP address. I super appreciate your help so far! We’re making progress I feel like. This is the furthest progress I’ve made since I started this.
-
@bartont126 Can you get me a clear shot of the kernel parameters, I need to see the entire line. Its in the section kernel variables and settings. The target computer can’t reach the fog server. I have a felling the answer is in the settings
-
@george1421 Try this. Sorry it’s always sideways. It’s straight on my computer until I upload it.
-
@george1421 Kernel Variables and settings:
bzImage Loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.1/fog/ consoleblank =0 rootfstype=ext4 mac=54:e1:type=up -
@bartont126 ok on the FOG server, will you key in the following command
showmount -e 127.0.0.1That will show the NFS share on the fog server. It should present two lines one for /images and one for /images/dev I’m traveling right now so I don’t have immediate access to a fog server to give you an example. -
@george1421 No worries. I just got home from work. I will give this a shot in the morning and respond with my findings. Thank you George!
-
@george1421 Hi George. I did the showmont -e and the two lines i’m getting says
Export List for 127.0.0.1
/images/dev/ *
images * -
@bartont126 Any ideas what might be causing the issue from the showmount -e?
-
@bartont126 those settings are correct. You have 2 shares. /images and /images/dev. (I assume the missing slash in front of /images was a type-o).
I’m still a bit confused why your target computer is reporting “Unable to locate image store”. Did you do the prerequisites of disabling the firewall and setting selinux to permissive?
-
@bartont126 can you also run these commands? (hint if you connect to your FOG server using a terminal program like putty you can copy and paste outputs a bit easier).
ls -la /images/dev
ls -la /images -
@george1421 ls -la /images/dev
total 16
drwxrwxrwx 4 fog root 4096 Feb 12 19:06 .
drwxrwxrwx 4 fog root 4096 Feb 12 16:06 …
drwxrwxrwx 2 root root 4096 Feb 12 19:06 54e1adc29063
-rwxrwxrwx 1 fog root 0 Feb 12 16:06 .mntcheck
drwxrwxrwx 2 fog root 4096 Feb 12 16:06 postinitscripts
tyler@tyler-PowerEdge-T710:~$ls -la /images
total 16
drwxrwxrwx 4 fog root 4096 Feb 12 16:06 .
drwxr-xr-x 27 root root 4096 Feb 12 16:30 …
drwxrwxrwx 4 fog root 4096 Feb 12 19:06 dev
-rwxrwxrwx 1 fog root 0 Feb 12 16:06 .mntcheck
drwxrwxrwx 2 fog root 4096 Feb 12 16:06 postdownloadscriptsI also did not disable the firewall and setting selinux. I’m unsure of how to do that so I will look it up.
-
What OS did you use for the FOG server?
-
@george1421 I just disabled the firewall. Trying to enable Selinux right now and set to permissive. Running Ubuntu desktop 16.04.3
-
@george1421 George, looks like it was the firewall the whole time. It’s now copying the image.
