FOG Server and IP Phone TFTP server
-
Hi Uncle Frank
Thanks for the welcome!
I am indirectly in control of the DHCP server (have to ask the boss to change settings for me)
Its a windows DHCP server, we have recently enabled option66 to allow our Cisco IP phones to download their firmware files. These are served up via Pumkin TFTP server on a different computer, which I have access to to copy files to etc.
Thanks for the help! -
@Rusty Just curious, but are your phones not on a separate VLAN? Most of the time companies run phones in parallel, but different LANs.
-
@Rusty It might help a lot to know more about the IP Phones and the boot files they use and their model.
-
what windows server version? the options available in server 2012 are likely needed for this…
-
@Marcus-Allen No they are on the same network as everything else. Not sure why, I guess it was just set up without much thought on that.
@Wayne-Workman I’m not sure why, but we have Cisco 7961/7941 and Yealink T42, and T22 I think, and a polycom conference phone.
They just talk to a Pumpkin (http://kin.klever.net/pumpkin) TFTP server and get the files they need.
@Junkhacker it is Server 2012 -
@Rusty If you have a list of all of their MAC addresses, you can set their next-boot server and any needed boot files via DHCP Reservations.
The reservation would override a global setting for FOG network booting. I’m fairly certain you can import reservations into Windows Server.
OR - the easer way - is to figure out their architecture names when booting. You can use Wireshark for this. Check this article out - it’s written JUST for co-existing items and network booting and talks about the various architecture names and how to set it up for each one. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
-
@Wayne-Workman So it will not work if all the FOG files plus the files for the IP phones just sit in the same place and the FOG clients just get the files they need ?
Sorry I guess I dont really understand it fully -
@Rusty I sent you an IM (top right chat bubble icon, also shows up in bottom right).
it’s a simple “What file does this phone need, what file does that phone need, what vendor class identifiers do each use” kind of thing… and then finding out the vendor class identifiers via TCPDump and wireshark.
If the vendor class identifiers are unique and not efi or legacy, and are each unique, you would simply setup a vendor class identifier filter in either Windows or Linux DHCP. Else, you simply use dhcp reservations in either Windows or Linux to specify options 066 and 067 for each device.
I’m willing to help out, but you have to get with me via chat.
-
Rusty has Windows Small Business Server 2011 available to him, and it does not support DHCP policies.
over the last two days - I’ve helped Rusty to create vendor class identifier filters for ISC-DHCP on his CentOS 7 FOG server so that his IP phones get what they need, and the PXE booting computers get what they need too.
We worked together to do extensive testing on a test network to make sure the IP phones received the correct options and then tried to go and get the correct resources.
With any luck, Rusty will try this out during non-production hours and maybe turn off Windows DHCP forever in favor of a much more powerful and capable DHCP solution that is open source
He’s going to hopefully share the finalized dhcpd.conf file with us for addtion to the WiKi.
-
Just a quick update, I will post a more complete one once I have properly documented my progress.
Since it seems too painful to work out how to get it working in windows server SBE 2011 domain controller (which I THINK seems to be similar to server 2008?) I have managed to convince the IT guy to use one of our other 3 running server 2012 instances to run the DHCP server.
I have created a windows 2012 server VMWare VM and set the DHCP server up as per @Wayne-Workman’s excellent article https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
I added a Vendor class for the IP phones and the PC types listed here https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1
I then added the scope polices as described in the example. It is this ability to add scope policies that Windows Server 2008 is lacking.
I find it incredible that the DHCP service cannot just be upgraded/replaced to have this functionality.FOG is installed on a CentOS VMWare VM that @Wayne-Workman generously helped my set up. I had installed it all but for some reason the installer did not complete (probably my fault) as /opt/fog/.fogsettings did not exist.
I have since captured and redeployed and XP and a Win7 image for testing purposes. The next step I assume is to try and build a universal HAL image.
-
@Rusty Great to hear that you got things sorted. I am marking this solved for now. You are more than welcome to post a more detailed article about this here. Or get in contact with us so we can add this to the wiki! Thanks.
