Posts made by Jphipps

I should also add that replication works as it should as well.

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04

Client

• Service Version:
• OS:

Description

I think I have a setting off some where. I can boot to the pxe menu and add a host from the location the node is at but I cannot deploy an image. Connection reset every time.

x.x.0.33 is the server/master node
x.x.9.15 is the storage node

@george1421 Yes it is, thanks.

@george1421 said in Dell Latitude 3570 pxe:

@jphipps well if you hit enter a few times at the screen with the text it should drop you to a linux command prompt

At the FOS command prompt key in cat /proc/cmdline and post the results here. My bet is that isdebug=yes is in the kernel parameters.

Make sure you don’t have a lingering task that someone has scheduled, where someone was doing a debug capture or deploy.

Made sure no tasks were scheduled, went ahead are updated the kernel again with most current and now all is working. I have been looking on the forums all day to figure out what was going on and it boiled down to one simple line and 2 seconds to update the kernel. Thanks for the help, it is appreciated!

@sebastian-roth said in Dell Latitude 3570 pxe:

@jphipps said in Dell Latitude 3570 pxe:

but when you issues any task, no matter which task it is, is when it boots into the FOS environment

Well, I still don’t get what you mean I think. What’s wrong with the client booting into the FOS environment if there is a task for this host scheduled??? From my point of view everything is working as expected. Which task did you schedule?

Doesn’t matter which task it is, capture is what I need to do but if i schedule deploy or any advanced task it loads FOS.

@george1421 said in Dell Latitude 3570 pxe:

@jphipps Just so I’m clear, every time you boot into FOG you get the first screen?

This is telling me you setup a capture / deploy with debugging enabled - OR - someone setup a global fog kernel parameter where isdebug=yes

I will look into the global parameter, never thought about that being the issue. I haven’t set one personally but I colleague that has messed about with the server who I have banned from touching it (was messing with this he shouldn’t have)

@sebastian-roth said in Dell Latitude 3570 pxe:

@Jphipps Do I understand this correctly? Even if there is no task scheduled for this hist it still boots right into the FOS linux environment?!

Can you please open the following URL in your browser and post the full text you see here in the forum:

http://10.78.0.33/fog/service/ipxe/boot.php?mac=10:7d:1a:10:f8:15

I should have worded that better. When there is no task it will load the menu correctly but when you issues any task, no matter which task it is, is when it boots into the FOS environment. My apologies, that was a misleading error on my part.

@jphipps

Stock kernal, I don’t see a point in manipulating what works. On the console for the specific host I have BIOS set to sanboot and EFI set to refind. I’ve tested several other stations and these 3570 seem to be the only ones having and issue.

Hate posting back to back threads but didn’t want 2 issues on the sames one. Ok, running 1.4.4 on Ubuntu 16.04 (Probably not the best choice). Now the Dell Latitude 3570 will register just fine BUT when i try to pxe boot, it just loads the grub, no matter what the task is. If i remove the host then I can access the FOG menu, but re-added the host and it’s back to loading gub. Since these 3570 are newer, is it a driver issue, not compatible with the current kernel? I will add that I did make sure I was on the latest kernel 4.12.3. Thanks.

@george1421 Sorry for the delayed reply, been SWAMPED. Anyway, so far it’s working with no issues, basically plug and play since I configured it here and had it delivered. Setup a bash to send me an email when it came online. As soon as it came up, I added it the console and replication took off… by the way, forgetting to limit bandwidth before replication start upsets a lot of users LOL. Now if I can figure out why these new Dell Latitude 3570’s will let me register them but not load the menu after I will be all set.

Note: No the firewall only filters external traffic, sorry I meant to start off with that.

@george1421

Do to HIPPA regulations a firewall is required at each site.

@sebastian-roth

Each site has its own DHCP server handing out different IP ranges. And yes by slave I mean regular storage node. I’m going to assume that the node will need to look back at the DHCP server for the site it will be at since it is in a different subnet.

Just making sure there isn’t any extra steps I’m missing with 1.4.4. The master node/server is setup at the main location where we are on a x.x.248.0 subnet. The second location where the slave node will be is x.x.255.0 subnet. I can ping the other locations work stations IPs and access every station via WIMS addresses. Is there anything outside of standard node install that needs done? Haven’t had the pleasure of setting one up offsite yet so wanted to make sure I’m ready when I go to configure everything.

Would like to take the time to thank the developers and the FOG community for all the hard work and documentation that’s out there. Once we go over our budget at then end of the year, we plan on making a donation to the FOG Project for your efforts.

Thanks in advance

Hi,
I’m looking for a guide on setting up a custom pxe boot menu on version 1.4.4. I’m needing to add a few bootable tools and add passwords to most menu option. A guide would be awesome! Thanks!