DHCP based on hostname

From: gladston@br.ibm.com
Date: Wed Aug 31 2005 - 13:24:30 GMT-3

• Next message: Andaluz, Danny: "RE: OT default gateway"
• Previous message: Jerry Wang: "Traceroute issue - MPLS CE router replys 2 hops on ingress &"
• Next in thread: Thomwin Chen: "Re: DHCP based on hostname"
• Maybe reply: Thomwin Chen: "Re: DHCP based on hostname"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

DHCP based on hostname does is not working for me. Do you see any problem here?

It works for client-id or the default (media type + MAC address)

Client config:

sh run
interface Ethernet0/0.500
 description DHCP vlan60
 encapsulation dot1Q 60

ip address dhcp client-id Ethernet0/0 hostname BB2

or

ip address dhcp hostname BB2

Both do not work.

The result is that R1 receives the dhcpdiscover but does not associates it with the client

Rack2R1#
*Feb 28 22:05:17: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.332e.3662.6563.2e66.3338.302d.4574.302f.302e.3530.30 on interface Ethernet0/0.60.

This is the config on R1

ip dhcp pool Dhcp-to-bb1-based-on-hostname
   host 148.5.15.20 255.255.255.0
   client-name BB2

This is the debug when it is working for client-id:

*Feb 28 21:15:51: DHCPD: DHCPDISCOVER received from client 0100.036b.ecf3.80 on interface Ethernet0/0.60.
*Feb 28 21:15:51: DHCPD: Sending DHCPOFFER to client 0100.036b.ecf3.80 (148.5.15.10).
*Feb 28 21:15:51: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.
*Feb 28 21:15:51: DHCPD: DHCPREQUEST received from client 0100.036b.ecf3.80.
*Feb 28 21:15:51: DHCPD: Sending DHCPACK to client 0100.036b.ecf3.80 (148.5.15.10).
*Feb 28 21:15:51: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.

This is the debug when it is working for combined media type and MAC:

Rack2R1(dhcp-config)#
*Feb 28 21:18:10: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.332e.3662.6563.2e66.3338.302d.4574.302f.302e.3530.30 (148.5.15.4).
*Feb 28 21:18:10: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.
*Feb 28 21:18:10: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.332e.3662.6563.2e66.3338.302d.4574.302f.302e.3530.30.
*Feb 28 21:18:10: DHCPD: Sending DHCPACK to client 0063.6973.636f.2d30.3030.332e.3662.6563.2e66.3338.302d.4574.302f.302e.3530.30 (148.5.15.4).
*Feb 28 21:18:10: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.

I also tried this test, using a wrong hostname, to see if R1 considers the hostname. The result shows R1 does not take in accont the hostname and offers the IP:

R1
ip dhcp pool Dhcp-to-bb1
   host 148.5.15.10 255.255.255.0
   client-identifier 0100.036b.ecf3.80
   client-name bb4

bb2
BB2(config-subif)#ip ad dhcp client-id e0/0 hostname BB3

Rack2R1(dhcp-config)#
*Mar 1 00:41:50: DHCPD: DHCPDISCOVER received from client 0100.036b.ecf3.80 on interface Ethernet0/0.60.
*Mar 1 00:41:50: DHCPD: Sending DHCPOFFER to client 0100.036b.ecf3.80 (148.5.15.10).
*Mar 1 00:41:50: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.
*Mar 1 00:41:50: DHCPD: DHCPREQUEST received from client 0100.036b.ecf3.80.
*Mar 1 00:41:50: DHCPD: Sending DHCPACK to client 0100.036b.ecf3.80 (148.5.15.10).
*Mar 1 00:41:50: DHCPD: broadcasting BOOTREPLY to client 0003.6bec.f380.

• Next message: Andaluz, Danny: "RE: OT default gateway"
• Previous message: Jerry Wang: "Traceroute issue - MPLS CE router replys 2 hops on ingress &"
• Next in thread: Thomwin Chen: "Re: DHCP based on hostname"
• Maybe reply: Thomwin Chen: "Re: DHCP based on hostname"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:20 GMT-3