From: John Underhill (stepnwlf@magma.ca)
Date: Thu May 27 2004 - 13:49:09 GMT-3
Ok.. I have two problems with autoinstall, and this time have included the
debugs and my notes, and I'm hoping someone out there has either had these
problems, or can spot the issue with my configs..
Problem 1: Still that hardware-address command under DHCP.. when I bind an IP
address to the client mac address, I'm thinking that when that host requests
an address from the dhcp server, it will give it that address, then the
autoinstall router can resolve its hostname from the network-confg file, and
unicast for the host specific configuration file, (R2-confg). But it simply
doesn't work. When the autoistall router asks for its ip address it sends the
client id, (a long number the concatenation of media type and mac), but dhcp
doesn't see the mac address.. here is the debug ip dhcp pac when I use the
client-identifier string.
DHCPD: DHCPDISCOVER received from client
0063.6973.636f.2d30.3065.302e.6230.3535
.2e61.3434.662d.4574.30 on interface Ethernet0.
DHCPD: Sending DHCPOFFER to client
0063.6973.636f.2d30.3065.302e.6230.3535.2e61.
3434.662d.4574.30 (172.16.40.2).
DHCPD: broadcasting BOOTREPLY to client 00e0.b055.a44f.
DHCPD: DHCPREQUEST received from client
0063.6973.636f.2d30.3065.302e.6230.3535.
2e61.3434.662d.4574.30.
DHCPD: Sending DHCPACK to client
0063.6973.636f.2d30.3065.302e.6230.3535.2e61.34
34.662d.4574.30 (172.16.40.2).
DHCPD: broadcasting BOOTREPLY to client 00e0.b055.a44f. <- client mac address
Now clearly, once the exchange begins it sees the mac address in the BOOTREPLY
line, and that is the address I specify in the hardware-address command,
here's the config:
service dhcp
ip dhcp pool MYPOOL
host 172.16.40.2 255.255.255.0
hardware-address 00e0.b055.a44f
default-router 172.16.40.1
option 150 ip 172.16.40.254
bootfile R2-confg
Now if I try this config, all I get on the debug output is:
DHCPD: there is no address pool for 172.16.40.1
If I use the client id, it works like a charm. Is there some long timeout
value that I have to wait through, (I've let it go for a couple minutes, but
that seems a little long). Or can someone spot an issue with my config, or
know of an issue with autoinstall?
Problem 2:
SLARP. So I set up the staging router with a connection to the tftp server, ip
helper-address command pointing to tftp, static routes, and ip
forward-protocol udp tftp command, create the default network-confg file with
a hostname mapping, the staging server has the address 192.168.1.1, and the
network-confg file resolves 192.168.1.2 to host R4. and I have an R4-confg
host specific config file. The autoistall router boots, gets an ip address,
contacts the tftp server, but the tftp server gets timeout loading
network-confg. The staging router can ping tftp and visa versa, and the
autoistall router is obviously talking to tftp, (and has a base config, no
acls or such), but always the timeouts.. here's the config for the staging
router: (off the top of my head)
int s0
ip add 192.168.1.1 255.255.255.0
ip helper-address 193.168.1.254 <- tftp server
int e0
ip add 193.168.1.2 255.255.255.0
ip helper-add 193.168.1.254
ip forward-protocol udp tftp
ip route 193.168.1.0 255.255.255.0 e0
ip route 192.168.1.0 255.255.255.0 s0
Thats all there is right? I have read every murky cisco doc I could find and
the configs line up.. any ideas? anyone have a working config?
Appreciate the interest..
cheers
John
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:18 GMT-3