Posts made by dws88

@Junkhacker Thanks for your assistance

I did, guessing that’s an issue?

Operating System: Virtualized Ubuntu 16.04 server on ESXi 6.7
Hardware: Dell Poweredge R430
FOG version: 1.5.5

After installing FOG on my clean instance of Ubuntu, I am unable to log back into the Ubuntu server itself. I know the username and password and am still unable to login. Any idea as to why this is occurring?

@Tom-Elliott I am looking at the options under power management on the web interface, I check the perform immediately tick box and in the action drop-down there is an option there to shutdown the host. This is what I am referring to, none of the three options work for me.

@Tom-Elliott Wake on LAN, Restart, and shutdown doesn’t seem to work and the VMs are capable of PXE booting from FOG. The VM passes through a vswitch so it is able to get out to the physical network. I also have a physical box that can’t utilize WOL either even though it is connected on an isolated network that FOG manages and I have ensured that the network card allows WOL.

Server

• FOG Version: 1.3.4
• OS: Ubuntu 16.04
• Dell PE R610 (all physical systems)

Hello all,

I am having a bit of an issue with the power options in FOG, I’ve verified that my server has Wake on LAN enabled and that it will find DHCP from FOG and boot over PXE without an issue. I did have MaaS installed previously and my servers would boot using IPMI without fail, which was great. However; since MaaS only seems to let you use Ubuntu, Cent or Windows and will only let you download custom Ubuntu images from the web, it won’t be as flexible as I’d like for it to be. FOG seems to be content with pushing out any image I want and that is more important than integrated power controls.

I am testing this with both physical hosts and VMs on ESXi 5.5 and I have a private PXENET to serve images and control power on the servers and neither are able to wake, shutdown, or restart. Here are some articles that I have looked at to be sure that my systems had the right config:

http://en.community.dell.com/support-forums/servers/f/956/t/19663975

https://communities.vmware.com/thread/478640?start=0&tstart=0

https://forums.fogproject.org/topic/3767/wake-on-lan-does-not-work/9 (installed wakeonlan and ran as mentioned with the correct MAC in the last comment and it did not work either.)

Any help provided will be greatly appreciated, please let me know if you need any more details.

@george1421 Thanks again you’ve been a great help, I went through the install again and was able to PXE boot my first host on the private PXE net.

@george1421 Thank you for your time, you’ve been a great help. I am going to wipe this box and start clean, I’ll check back in a while later and update my progress. It is my opinion, it would be nice to have a simplified interface config page in the web UI.

@george1421 If I were to install a clean image would it be possible to have the web UI available on eno1 while the rest of the services act on eno2? That is the primary reason the system was configured the way it was.

@george1421 Every node has multiple NICs available and most servers are not going to require active directory. The main image I will have this serving will be for storage nodes, along with generic Linux systems, and some other applications as needed.

@george1421 I am running in an environment that already has an active DHCP server for another system being used by someone else. eno1 is just being used to connect out to our office. If I can prove FOG to be worthy, it could be used to deploy over 130 nodes once in production.

@george1421 Honestly, I am a complete noob to FOG, if you couldn’t tell by this thread. So as of right now my knowledge is lacking. I took a look at the storage page and it looks to be configured to use eno1 and its address. I assume that this is wrong and should be set to the interface intended for PXE booting, which is eno2.

I am running this on a Dell R610 with multiple 1gb ports built in. I have eno1 active for the management network, so I can access it from my desk, this net should not provide DHCP. The eno2 net should be the PXE net, as it is isolated from everything else and can provide DHCP without conflict. Thank you for your quick response.

Here is the output for ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 14:fe:b5:d1:a2:93 brd ff:ff:ff:ff:ff:ff
inet 10.254.125.216/23 brd 10.254.125.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::16fe:b5ff:fed1:a293/64 scope link
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 14:fe:b5:d1:a2:95 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.254 scope global eno2
valid_lft forever preferred_lft forever
inet6 fe80::16fe:b5ff:fed1:a295/64 scope link
valid_lft forever preferred_lft forever

Server

• FOG Version: 1.3.4
• OS: Ubuntu Server 16.04

Hello all,

I need to set up FOG with a management network for web console access and a separate network for PXE booting my machines. DHCP should only be allowed on the PXE net to avoid confrontation with the DHCP server already on the management network. Any assistance that can be provided would be of immense help and would be greatly appreciated.