Solved

PXE booting from Cisco Router

Posted on 2009-07-08
2
1,077 Views
Last Modified: 2012-05-07
Hello,

I am trying to get dhcp clients to pxe boot via our cisco 1811 router. I would like to use the router as the pxe server for the initial connection due to various issues that will not allow other solutions. The router is setup with an ip of 10.59.120.1 255.255.255.0. The dhcp pool for the clients is setup as follows:

ip dhcp pool testpool
   import all
   network 10.59.120.0 255.255.255.0
   bootfile initrd
   default-router 10.59.120.1
   option 60 ascii "PXEClient"

I have the bootfile located on the router's flash card (flash: initrd). I have made sure that ip bootp server is enabled on the router and that spanning-tree portfast is enabled on the port that the dhcp client is connected to.

I currently get an ip address of 10.59.120.2 255.255.255.0 when trying to pxe boot, however I then get the error PXE-E55: ProxyDHCP service did not reply to request on port 4011.

Is there something I am missing in my config? Is it even possible to do what I am trying to do?

Any help would be greatly appreciated.
0
Comment
Question by:Tech Services
2 Comments
 
LVL 5

Expert Comment

by:JanSc
ID: 24811934
Bootp server is not ment for PXE boot. Is something else. The bootfile for bootp contains IP gateway information and additional parameters such as where startup files can be found and how to get them.
(Is very old way to do this. DHCP has many more options). In bootp you can configure things like autoexec.bat and where boot files like commanc.com can be found. Are you still using DOS?

You need a PXE server, like Altirus, for that as far as i know. It looks like bootp, but with option 60 you tell the client where the pxe server is located. The PXE file can be obtained there.
0
 

Accepted Solution

by:
Tech Services earned 0 total points
ID: 25081437
Thanks for the info. I've managed to get a solution working that has our clients booting to a novell pxe boot server using the following two commands on the cisco router:

bootfile nvlnbp.sys (this points the clients to the novell pxe boot file)
next-server XX.XX.XX.XX (this is the ip address of the novell pxe boot server)

This solution requires nothing to be done to the switches. It does require this information to be in the dhcp pool of every vlan that you want to be able to pxe boot.
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Join & Write a Comment

New Server 172.16.200.2  was moved from behind Router R2 f0/1 to behind router R1 int f/01 and has now address 172.16.100.2. But we want users still to be able to connected to it by old IP. How to do it ? We can used destination NAT (DNAT).  In DNAT…
Problem Description:   Couple of months ago we upgraded the ADSL line at our branch office from Home to Business line. The purpose of transforming the service to have static public IP’s. We were in need for public IP’s to publish our web resour…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now