From: Guyler, Rik (rguyler@shp-dayton.org)
Date: Mon Sep 05 2005 - 11:29:08 GMT-3
Gladston, what do you have in place to resolve the hostname? Perhaps adding
a static host entry will help?
Rik
-----Original Message-----
From: gladston@br.ibm.com [mailto:gladston@br.ibm.com]
Sent: Thursday, September 01, 2005 9:57 AM
To: Thomwin Chen
Cc: ccielab@groupstudy.com
Subject: Re: DHCP based on hostname
Thanks for the reply,
Yeah, client-id or default type + MAC works.
Just cliente-name does not work.
Cordially,
------------------------------------------------------------------
Gladston
Thomwin Chen <thomwin_chen@yahoo.com>
31/08/2005 15:16
To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR, ccielab@groupstudy.com cc
Subject
Re: DHCP based on hostname
Gladston,
have you try this on your DHCP Server ?
suppose that the DHCP Client is R2
ip dhcp pool R2
host 192.168.1.2 255.255.255.0
client-identifier 01ab.cdab.cdab.cd
default-router 192.168.1.1
Rgds,
Thomwin
gladston@br.ibm.com wrote:
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.3
0
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.3
0
(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.3
0.
*F! eb 28 21:18:10: DHCPD: Sending DHCPACK to client
0063.6973.636f.2d30.3030.332e.3662.6563.2e66.3338.302d.4574.302f.302e.3530.3
0
(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.
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3