PXE booting on network

[SACHIN SHARMA]

Hello All,

PXE boot is not working on the network ,does it require any configuration on the network device.

Regards,

Chakra.

[Reza Sharifi]

Hi

Yes you need to configure the correct vlans on the switch
Here is a sample config

http://www.shanekillen.com/2012/07/cisco-core-switch-config-for-pxe-boot.html?m=1

HTH


Sent from Cisco Technical Support iPhone App

[Richard Burts]

Chakra

It certainly takes some configuration on the network device. The answer to what it takes varies depending on whether you have a DHCP/PXE server set up and you just need the router to forward the requests or whether you need to have the network device serve as DHCP server and provide correct parameters for PXE. Can you tell us which of these you need?

HTH

Rick

[SACHIN SHARMA]

Richards,

we have a dhcp server and PXE server configured and present in the server vlan and user machines on the user vlan receive dhcp address  from the server ,but PXE client does not receive dhcp address and struck there forever.we ip helper-adress configured under the router interface.Do we need any additional configuration on the router ?

Regards,

chakra.

[Richard Burts · Accepted solution]

Chakra

If you have a DHCP server then the main thing that you need to configure on the network device is the ip helper-address. Can you post the configuration from one of your devices so that we can see the details of how you have set it up?

Also can you verify that the helper-address points at the correct address for the DHCP server and that the address of the DHCP server is reachable from this device? Can you also verify that the scope on the DHCP server for this subnet does have the correct information for the PXE server configured?

HTH

Rick

[SACHIN SHARMA]

Thanks Richard configuring correct server details fixed the issue.

[Richard Burts]

Chakra

I am glad that my suggestion pointed you in the correct way to a solution for your problem. Thank you for posting back to the forum and indicating that you have solved your problem and that it was details of the server configuration that were the problem. This information will be helpful to other readers in the forum, especially if someone is facing a similar problem.

HTH

Rick

[SACHIN SHARMA]

Thanks  you.

[Balaji Rajan]

Hi Sachin,

How this issue resolved.

By setting pxeServer details in DHCP server scope

or 

by having pxeServer as ip help-address

I am facing the PXE booting issue. VLAN config as follows;

interface Vlan103
ip address 172.16.22.1 255.255.254.0
ip helper-address 172.16.21.11 <-----DHCP server
ip helper-address 172.16.20.19 <-----PXE server

Thanks,

Balaji Rajan

[Balaji Rajan]

PXE Boot on SDA Fabric 

We had an issue with PXE boot on SDA Fabric.

Option-82 required on both DCHP for IP allocation and SCCM for PXE boot to work. SDA Fabric uses anycast gateway IP, thus FE switch add Option-82 header contains FE switch identifier (Loopback IP). Thus BDR can return the DHCP Reply or PXEBOOT reply from SCCM to correct FE switch by reading Option-82 returned back by DHCP/SCCM.

Without Option-82 on SCCM, PXEBoot will not work. 

https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/32370460-need-support-for-option-82-in-pxe-dhcp-handshake-a

Though there is another option to add Policy deployment on DHCP server scope options 60/66/67 etc to point for every PXEClient architecture. But Microsoft does not recommend implementing this as it adds more confusion.

[Richard Burts]

Balaji Rajan

Thank you for updating the post with the details of needing option 82. This will help others in the community who might face this issue.

[rawatkuldeep23]

@BALAJI RAJAN Can DHCP server and Client can sit in same Fabric? if yes, what would be the idea of traffic flow? some hint on configuration?