Re: DHCP Manual Binding

From: William Chen (kwchen@netvigator.com)
Date: Wed Jan 28 2004 - 12:22:18 GMT-3


Dear Scott,

    Indeed, I tried using hardware-address and client-name, but it does not
work. Then I have to use client-identifier, and it works.

Best Regards,
William Chen

----- Original Message -----
From: "Scott Morris" <swm@emanon.com>
To: "'Tom Lijnse'" <Tom.Lijnse@globalknowledge.nl>; "'William Chen'"
<kwchen@netvigator.com>; <ccielab@groupstudy.com>
Sent: Wednesday, January 28, 2004 8:23 PM
Subject: RE: DHCP Manual Binding

> It would seem to be a whole lot easier to use the 'hardware-address'
command
> and just put the MAC! :)
>
> You can also use 'client-name' to indicate the name of the PC/Host machine
> for further marking (if supported on the device).
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
> JNCIS, et al.
> IPExpert CCIE Program Manager
> IPExpert Sr. Technical Instructor
> swm@emanon.com/smorris@ipexpert.net
> http://www.ipexpert.net
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Tom
> Lijnse
> Sent: Wednesday, January 28, 2004 2:53 AM
> To: William Chen; ccielab@groupstudy.com
> Subject: RE: DHCP Manual Binding
>
> Hi William,
>
> The default client-identifier that a cisco router uses is
> "cisco-MAC-ADDRESS-INTF", where "MAC-ADDRESS" is the interface mac-address
> and "INTF" is the interface descriptor.
>
> For instance, if you take the client-identifier that you are using and
> convert it to ascii (leaving off the leading two zeroes) you get
> "cisco-0000.0c8e.ded4-Et0".
>
> For more details look at:
>
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr
> as_r/1rfdhcp.htm#1049289
>
> Regards,
>
> Tom Lijnse
>
> CCIE #11031
> Global Knowledge Netherlands
>
> -----Original Message-----
> From: William Chen [mailto:kwchen@netvigator.com]
> Sent: Wednesday, January 28, 2004 1:43 AM
> To: Tim Fletcher; ccielab@groupstudy.com
> Subject: Re: DHCP Manual Binding
>
>
> Hi,
>
> Thanks, it works if I use the client-identifier. However, really don't
> understand how cisco comes to the client identifier.
>
> ip dhcp pool R3
> host 192.168.0.30 255.255.255.0
> client-identifier
> 0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30
> bootfile R3.txt
> option 150 ip 192.168.0.3
> !
>
> Best Regards,
> William Chen
>
> ----- Original Message -----
> From: "Tim Fletcher" <groupstudy@fletchmail.net>
> To: "William Chen" <kwchen@netvigator.com>; <ccielab@groupstudy.com>
> Sent: Wednesday, January 28, 2004 2:36 AM
> Subject: Re: DHCP Manual Binding
>
>
> > William,
> >
> > What you are seeing is perfectly normal. Here's an excerpt from RFC
2131:
> >
> > DHCP defines a new 'client identifier' option that is used to pass
an
> > explicit client identifier to a DHCP server. This change eliminates
> > the overloading of the 'chaddr' field in BOOTP messages, where
> > 'chaddr' is used both as a hardware address for transmission of
BOOTP
> > reply messages and as a client identifier. The 'client identifier'
> > is an opaque key, not to be interpreted by the server; for example,
> > the 'client identifier' may contain a hardware address, identical to
> > the contents of the 'chaddr' field, or it may contain another type
of
> > identifier, such as a DNS name.
> >
> > I don't know how they come up with the particular client ID that they
use,
> > but it doesn't really matter as long as it's unique.
> >
> > -Tim Fletcher
> >
> > At 01:48 AM 1/28/2004 +0800, William Chen wrote:
> > >Dear all,
> > >
> > > I try to configure and test the manual binding of DHCP. I am
running
> the
> > >DHCP sever in R5 (a 2500 router) and I simulate a client with another
> 2500
> > >router. After I shutdown and no shutdown the client, the following
> message
> > >is display in the DHCP server. It seems the debug message is so strange
> that
> > >the client hardware address is wired. Any idea?
> > >
> > >R5#
> > >01:12:56: DHCPD: DHCPDISCOVER received from client
> > >0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on
> interface
> > >Ethernet0.
> > >01:12:56: DHCPD: there is no address pool for 192.168.0.100.
> > >01:12:59: DHCPD: DHCPDISCOVER received from client
> > >0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on
> interface
> > >Ethernet0.
> > >01:12:59: DHCPD: there is no address pool for 192.168.0.100.
> > >01:13:02: DHCPD: DHCPDISCOVER received from client
> > >0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on
> interface
> > >Ethernet0.
> > >...
> > >01:15:20: DHCPD: there is no address pool for 192.168.0.100.
> > >01:15:21: DHCPD: DHCPDISCOVER received from client 0100.c002.b682.67 on
> > >interface Ethernet0.
> > >01:15:21: DHCPD: there is no address pool for 192.168.0.100.
> > >01:15:22: DHCPD: BOOTREQUEST received from BOOTP client 00c0.02b6.8267
on
> > >interface Ethernet0.
> > >
> > >Best Regards,
> > >William Chen
> > >
> > >_______________________________________________________________________
> > >Please help support GroupStudy by purchasing your study materials from:
> > >http://shop.groupstudy.com
> > >
> > >Subscription information may be found at:
> > >http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:51 GMT-3