DHCP Scope Options for PXE on swtiches

Hello,
I am trying to get PXE support for OSD in a sccm 2012 environment.
WSD resides on the same server as my SCCM 2012 Primary server.
I currently have one dp with PXE enabled.
My networking team asked what I needed for PXE support.
I responded:
DHCP discover package contains option 60
DHCP discover uses port 67 UDP
DHCP Offer uses port 68 UDP
Server ack from PXE server including options 66 and 67
Client unicast request for options 66 (boot server) and option 67 (boot file) (port 4011 UDP)
They responded with what do I need from below
The above response
was from a different job and location. Now they are asking for info on boot file and hostname. Hostname I would think be the dp or in our case, the sccm primary server. The boot file, I have no idea
Thanks so much for your help,
Mark

Ok, networking agrees to use IPhelpers, but needs "official documentation" of exactly what to do. Does anyone have a link that I may give to network to use. I really do appreciate it. I never thought I would have to do the network
part for them. :(
Thanks,
Mark
The general gist is that your router interfaces need to relay/forward bootp/dhcp "discover" & "request" to *both* your DHCP and your PXE-enabled DP.
This will cause the DHCP-client's discover/requests to be relayed to both, but the PXE-enabled DP won't respond to the initial discover/request because it can't issue IP addresses.
But once the client *does* have an IP address, and it issues a PXE request, the PXE request will be relayed to both, the DHCP server will ignore it but the PXE-enabled DP will process it and offer the NBP and then the TFTP of the boot image etc.
This is recommended/preferred over using DHCP options 66/67.
It's recommended in lots of places, but here's a great reference:
http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
For "official documentation" on how to configure the router, the router manufacturer will help with that.
Cisco refer to their implementation as "ip helper-address", which is why the feature is often referred to as "iphelpers".
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

DHCP scope options: How TO

Hi,
I have a 10.4 server as DHCP for several VLANs. I need to setup DHCP scope options on two VLANs to be able to direct DHCP requests from a specific device (IP phones) to the relevant VLAN for obtianing IP addresses.
I cannot see bootpd.plist in /etc and not much information available online about this.
Found these two relevant posts but not much of help:
http://discussions.apple.com/message.jspa?messageID=7200952
http://discussions.info.apple.com/message.jspa?messageID=5054131
I can export the serveradmin settings out and can see the entries but where and how do I make the scope entries? plist editor won't open the file and if i convert to csv in excel the existing data is there and logical but where do i enter my scope options?
any help in the right direction will be much appreciated.
cheers
Muhammad

You didn't try hard enough... ;). You need to use the Get-DhcpServerv4OptionValue cmdlet (or ...v6...).
Get-DhcpServerv4OptionValue -ComputerName <computername> | Where-Object OptionID -eq 6 | Select-Object Value
Edit: I think it's important that you know how I solved this problem. Perhaps you can put it to use yourself some time. The first thing I did was return all the 'get' DHCP cmdlets using this command: Get-Command -Module dhcp* -Name get-*. I quick scanned
the cmdlets (actually, they're functions) and found the word 'option.' I jumped over to the DHCP MMC snap-in and quickly figured out why that sounded familiar. In the GUI, you right-click Server Options to get to this setting. I then ran the function in my
example without piping it to the Where-Object cmdlet, and it return a value property. I then added the | Where-Object to filter down what was returned.
In writing this edit, I determined there's actually an -OptionID parameter, which means I could have better written my example. Here's that now:
Get-DhcpServerv4OptionValue -ComputerName <computername> -OptionID 6 | Select-Object Value
Always filter as close to the left as possible. That's means we don't want to pipe to something when we can filter with a built-in parameter.

DHCP SCOPE Option 67 string value for OS deployment

I am completely new to OS Deployment and very less knowledge on dhcp. We are using SCCM2012 in our environment. I am confused on what should be the string value for DHCP 67 OPTION . Does the \ back slash make any
difference when setting a string value. for example- \\smsboot\x64\wdsnbp.com or \smsboot\x64\wdsnbp.com or would i need to specify the complete path where remote install folder is located for example \\server name\c$\remoteinsall\smsboot\x64\wdsnbp.com
.I cant test myself due to restrictions in our organization as the DHCP servers are handled by other team . Appreciate your help!!!

Hi,
>>what should be the string value for DHCP 67 OPTION
The Option 67 should be SMSBoot\x86\wdsnbp.com
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Configure DHCP Server options for Internet Sharing?

Good morning, all.
I have a Sprint (Sierra 595U) AirCard internet connection, which I'm sharing over my AirPort (using OS X's built-in Internet Sharing) to several Windows clients in my office. I see that when Sharing is enabled, en1 takes on the address 10.0.2.1 by default, as well as the role of default gateway/router and DHCP server for the Windows clients.
My question is: Can I configure the IP addresses and DHCP options for Internet Sharing to another address/mask scheme?
Just like I changed my home wireless network away from the default 192.168.1.0/24 for security reasons, I'd like to do the same here.
Thanks and Regards,
BrooklynWalker

Some paranoia is good.
Yes, of course security paranoia can be cultured. like yogurt
I googled.
This might help:
http://www.aleph0.com/computing/macosx/dhcp-setup/
but from what I just read, changing away from the default net & mask might be putzy.Some other discussions for you:
http://www.macosxhints.com/article.php?story=20050331194834746
or you might see something here that helps.
Sorry not to be more specific. Hard to tell if you already googled for yourself.
I'll let someone smarter than I am take a look for you, here.

DHCP scope only for WiFi

Hi. Is it possible to configure some DHCP scope on Windows Server 2012 R2
only for WiFi devices?
Maybe some policy?
Thank you!

Hi,
Base on my experience, in the enterprise environment, we usually create a private vlan for the wireless terminal.
Therefore you can create a dedicated scope for the wireless terminal device.
More information:
What's New in DHCP in Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn305900.aspx
Configuring a DHCP Superscope
http://technet.microsoft.com/en-us/library/dd759168.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DHCP scope setup for 3702 APs on Microsoft server

Hello all, thanks for taking a look - I need some help.
5508s running 7.6
3502s widely deployed, but wanting to start planning for 3702s.
Here's my dilemna. Option 43 as-is, simply doesn't work, and I'm having trouble figuring out how to add in the right VCI, or custom DHCP options on our Microsoft DHCP servers...
Can anyone provide me with some screen grabs or PDF instructions to help walk me through this configuration?
Thanks much,
Jason W.
(Here's a link to the doc that led me to believe I need to go down this road, and that there's just s custom DHCP option missing for my 3702 deployment. This link is outdated though.)
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43.html

Hi Jason,
There is a very good explanation from Jeff.(52.50 explains option43/60 on Windows DHCP)
https://www.youtube.com/watch?v=pKEiPCLO3Qk&list=PL_mADa_gji1MYUz-C-VGkLLMl56L4x5Mh&index=4
I believe VIC should be Cisco AP c3700.
Hope this helps.
Regards,
Christos.

MDT/WDS PXE Deployment - DHCP Options for both x64 and x86

Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
Configure DHCP option 67 with the right boot image file.
For 32-bits systems \boot\x86\wdsnbp.com
For 64-bits systems \boot\x64\wdsnbp.com
I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.

DHCP Options (specifically 067) can have a significant impact on which NBP your client can access. If you specify \Boot\x86\Wdsnbp.com you are forcing the client to the 32bit NBP.
If you specify \Boot\x64\Wdsnbp.com you are forcing the client to the 64bit NBP.
Niether option is an ideal solution, especially if you have a varied environment.
I would take a look at the following article and see if it sheds some light on your question:
PXE booting with WDS – DHCP Scope vs IP Helpers

How to tell N6.5 DHCP to use a W2k8 for PXE?

Hello,
could anyone give me a hint, how to tell my netware DHCP to use a Windows Server 2008 R2 running Acronis with PXE Server?
Actual Situation:
Netware 6.5 Sp8 Server with ZENWORKS in Cluster mode
Netware DHCP Server
ZEN7 SP1 Imaging
--> works fine so far, and no problem in other subnets, IP-helper are configured in the switches
New Situation:
Netware 6.5 Sp8 Server with ZENWORKS in Cluster mode
Netware DHCP Server
Windows Server 2008 R2 running Acronis Snap Deploy with PXE-Server - in future may be a clean Windows Deployment service without Acronis
--> that would be nice :)
I found serveral ini-files (dts.ini, pdhcp.ini, tftp.ini) where I configured the new IP-Address of the W2k8 PXE Server.
Now:
The Client gets its correct IP-Address from Netware DHCP
but after that the following messages:
Auto-select:
ZENworks Boot
Boot Server IP: --.--.--.-- (the correct one configured in the ini-files!)
TFTP.
PXE-T02:
PXE-E3C: TFTP Error - Access Violation
PXE-M0F: Exiting Intel Boot Agent
Any ideas?
Thanks a lot.

Originally Posted by magic31
You don't have to configure anything specifically in DHCP to work with PXE. Possibly just unconfigure an option that was set for the previos setup; One thing to check (and remove) is option 60 for the PXE Client option, if this is configured with the DHCP subnet options. This option should only be set if both DHCP and PXE services are on the same server (as is probably the case in your situation as I'm guessing both DHCP as also PXE get loaded in the same cluster resource script).
For subnets serviced outside of the subnet your DHCP server is running in, you will need to configure multiple ip helpers: one that points to the DHCP server and one points to the PXE server so those requests on other subnets get serviced correctly.
To get things running it's probably easier to try to get this to work on the subnet your DHCP and PXE server are running in (so you are not also having to deal with the ip helper setup just yet). If that works, then expand you configuration to different subnets & ip helpers.
Hope that helps,
Willem
As a ps and for clarification, don't load the PDHCP on any of the NetWare servers... just have the PXE PDHCP service running on the Windows server.
The PDHCP/PXE service for ZenWorks won't understand/work with the Arconis one and visa versa.
-Willem

DHCP Scopes and Scope Options Import & Export

I need to adjust lease times for over one hundred scopes spread across multiple servers (about half of them are on one server, though). There will be 2 or 3 different lease times used. What is the best way to do this?
I know I can use netsh to change the option for each scope. But I would like to script the collection of the list of scopes, rather than typing the list manually. Is there a way to export a list that contains just scopes and descriptions?
Thanks

Hi,
Actually, it can be exported as txt file.
netsh dhcp server export c:\DHCP\myscopes.txt
Export-DhcpServer
And you can also manage it via powershell
Use the PowerShell DHCP Module to Simplify DHCP Management
http://blogs.technet.com/b/heyscriptingguy/archive/2011/02/14/use-the-powershell-dhcp-module-to-simplify-dhcp-management.aspx
Hope this helps.

Internal DHCP scope for AP on WLC 7.0 (on diff subnet)

hi All,
I would like to know if it is possible to assign dhcp pool on a different subnet to the WLC management interface?
Eg: Management Interface is on 172.16.4.100 /24
I would like to use the WLC Internal DHCP to assign IP to my APs on the a different range 172.16.2.x /24
Is that possible?
I have tried assigning dhcp scope for the AP within the same subnet as the management interface and it works. But that is not my requirement
Apparently i need my AP to be sitting on a different vlan
please advise

No its not possible.. this works only if the AP and the WLC management interface is in the same subnet!! to ur issue we use something called as DHCP OPTION 43, google search DHCP OPTION 43 + cisco, the first link that u get wil help you!!
Please dont forget to rate the usefull posts!!
Regards
Surendra

Is there a way for internal DHCP Scope to release scope addresses when the wifi client has disconnected?

DHCP scope is configured on a WLC 5508.
I'm checking if there' a way for WLC to clear the dhcp leasing when a user is diconnected from wireless?

Unless the client sends a DHCP Release upon disconnect, which is not mandaded in the protocol, the lease will simply remain until it has expired. If you're concerned with running out of leases, you only have 2 options.
1. reduce the lease time of your dhcp scope
2. increase the network size to accomodate more usable addresses.
There isn't a way to force a DHCP address lease to be "cleared" from the WLC simply because the client was disconnected.

How can configure scope options in dhcp server

Good Night Partners.
I need configure scope options in dhcp server on mac mini.
i dont know how to do.
its my first mac and i confuse.
Can anybody help me please.

Are you referring to DHCP Option Codes? If so then this can be done with the DHCP server included with Mac OS X Server. However Apple do not provide a tool for doing this nor for encoding the values in the required format.
What you will need to do is edit the DHCP Server configuration file manually using a text editor. This configuration file is located at /etc/bootpd.plist before you do this I advise having a read of the Unix man page for bootpd (the DHCP server software Apple use).
You can use a utility I have written to generate the required information and then paste this in to /etc/bootpd.plist it can be downloaded from -
http://web.me.com/jelockwood/MyUtilities/dhcp.html

Multiple Lease Duration for one DHCP Scope?

Hi All,
I have an urgent question. I wanted to know if it is possible to have many lease durations for different computer groups getting their addresses from one DHCP scope. I saw somewhere that it is possible to use User Classs or Vendor Classes for setting a lease
duration for a group of computers sharing the same class Id ?
If it is true, How can to configure ?
Also i would like to know about the lease duration period what is the maximum days can we have ( 8 days After )?
Thanks
Atul

Please refer to the following-
http://social.technet.microsoft.com/Forums/windowsserver/en-US/26de79f9-6ad7-4088-9077-006b9dd8c1fb/multiple-lease-durations-for-one-dhcp-scope?forum=winserveripamdhcpdns
You can configure any value as lease duration; however if you want a very big/infinite value; it makes sense to convert the lease(s) to a reservation.

Best place to create the DHCP scope for Guest SSID for remote office connected to HQ Foreign-Anchor controller

Hi Experts ,
Need help with the respect to understand the best practice to place/create the DHCP scope for remote site Guest SSID which will be connected to HQ Foeign-Anchor controller set-up.
how about internet traffic for Guest SSID , which one will be recommanded :
1) Guest SSID gets authenticated from HQ ISE and exposed to the local internet
2) Guest SSID gets authenticated from HQ ISE and exposed to the HQ internet
Thanks

Hi George ,
Thanks for your reply ...So you mean, best design would be to create the DHCP scope into DMZ for guest and let it get exposed to HQ internet ...
how about if I have another anchor controller in lets say in other office and I need to anchor the traffic or load balance from HQ foreign controller , in that case if I create DHCP scope into HQ anchor controller and if its down , I will loose the connectivity , how do I achieve fail-over to another anchor ?
Do I need to create secondary scope into another anchor controller and let the client get reauthenticated from other location ISE and get ip address as well from another anchor controller . Is it what you are proposing ?

DHCP - Cannot add text option for VOIP phones in OES Linux

While working through this, I solved the issue, but decided to post this anyway as it may help others to find these sorts of errors.
I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has Shoretel VOIP phones. Existing NetWare-based DHCP has no problem. Option 156 has been configured to give out the required text information that Shoretel phones require.
Problem is that I could not get the OES11 DHCP to run with that option. Nor could I migrate the existing option over - the Migration Tool (in OES11) says it successfully migrates DHCP, but I cannot start the dhcpd daemon. Error is that it failed, and in the rc.dhcpd.log file I see an error:
LDAP Line 26: unknown option dhcp.Shoretel_Boot.
LDAP Line 26: unexpected end of file
LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
Configuration file errors encountered -- exiting
If I look in the file (created when LDAP reads DHCP config from eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry at line 26:
option Shoretel_Boot "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time 259200 ;
This option does NOT show up in the newdhcpservice option when I look at it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
This option DOES show up in the DNS/DHCPManagement Console if I look at the DHCP (NetWare) tab and look at Other DHCP Options for some of the configured subnets, but it actually has different text from the above, specifically:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
Note that it does not have a " character anywhere in the entry. This option is configured as a Global DHCP text option.
Novell TID 7009464 mentions the issue, though not for Option 156. In that TID there is this:
"Situation #2
Migrate a working DHCP server with DHCP options that are of type "Text" to an OES server.
Load the DHCP server service... it fails to load and gives similar errors to the ones listed above."
Under resolution the TID says to delete and recreate the dhcp service object without the text option and it will load. That doesn't work for me as I still get an LDAP error pointing to the Shoretel_Boot unknown option. (I dare not try deleting it from the NetWare DHCP config and risk breaking the client's phone system).
One of the options in the TID to fix this is to re-enter the data using the DNS/DHCP Management Console - but that didn't work.
Here is the answer:
First, the log files are misleading. The error message points to not being able to read the newdhcpservice object entry - but the problem was elsewhere. In fact the problem showed up in the logs even when there were no option 156 entries at all in any object inside the newdhcpservice or the newdhcpservice object itself. The problem existed in the NetWare configuration of the object for one of the dhcp subnets.
Specifically, there was an illegal character in the text entry for option 156 - the # character was in there, like this:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
If you look at the error log entry for syntax error you can see that the option 156 text stopped at the # symbol, and then default-lease-time was appended to the end.
Removing the # symbol got things working.
Craig Johnson
(former Novell partner / sysop)

On 30/08/2014 21:16, phxazcraig wrote:
> While working through this, I solved the issue, but decided to post this
> anyway as it may help others to find these sorts of errors.
>
> I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has
> Shoretel VOIP phones. Existing NetWare-based DHCP has no problem.
> Option 156 has been configured to give out the required text information
> that Shoretel phones require.
>
> Problem is that I could not get the OES11 DHCP to run with that option.
> Nor could I migrate the existing option over - the Migration Tool (in
> OES11) says it successfully migrates DHCP, but I cannot start the dhcpd
> daemon. Error is that it failed, and in the rc.dhcpd.log file I see
> an error:
>
> LDAP Line 26: unknown option dhcp.Shoretel_Boot.
> LDAP Line 26: unexpected end of file
> LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
> Configuration file errors encountered -- exiting
>
>
> If I look in the file (created when LDAP reads DHCP config from
> eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry
> at line 26:
>
> option Shoretel_Boot
> "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time
> 259200 ;
>
>
> This option does NOT show up in the newdhcpservice option when I look at
> it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
>
> This option DOES show up in the DNS/DHCPManagement Console if I look at
> the DHCP (NetWare) tab and look at Other DHCP Options for some of the
> configured subnets, but it actually has different text from the above,
> specifically:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
>
> Note that it does not have a " character anywhere in the entry. This
> option is configured as a Global DHCP text option.
>
> Novell TID 7009464 mentions the issue, though not for Option 156. In
> that TID there is this:
> "Situation #2
> Migrate a working DHCP server with DHCP options that are of type
> "Text" to an OES server.
> Load the DHCP server service... it fails to load and gives similar
> errors to the ones listed above."
>
> Under resolution the TID says to delete and recreate the dhcp service
> object without the text option and it will load. That doesn't work for
> me as I still get an LDAP error pointing to the Shoretel_Boot unknown
> option. (I dare not try deleting it from the NetWare DHCP config and
> risk breaking the client's phone system).
>
> One of the options in the TID to fix this is to re-enter the data using
> the DNS/DHCP Management Console - but that didn't work.
>
> Here is the answer:
> First, the log files are misleading. The error message points to not
> being able to read the newdhcpservice object entry - but the problem was
> elsewhere. In fact the problem showed up in the logs even when there
> were no option 156 entries at all in any object inside the
> newdhcpservice or the newdhcpservice object itself. The problem
> existed in the NetWare configuration of the object for one of the dhcp
> subnets.
>
> Specifically, there was an illegal character in the text entry for
> option 156 - the # character was in there, like this:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
>
> If you look at the error log entry for syntax error you can see that the
> option 156 text stopped at the # symbol, and then default-lease-time was
> appended to the end.
>
> Removing the # symbol got things working.
>
> Craig Johnson
> (former Novell partner / sysop)
Thanks for taking the time to post the above as I'm sure it will help
someone else in the future.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

DHCP Scope Options for PXE on swtiches

Similar Messages

Maybe you are looking for