From: Brian S turner (brian@xxxxxxxxxxxxxxxxx)
Date: Tue Aug 15 2000 - 11:41:51 GMT-3
If you try to configure DHCP for a pool that you don't have a network
configured on your router you get an error message. When you give the
network command it looks for what interface it is going to be assigned to
that is how it knows. There are no parent or child pools in Cisco DHCP.
Each pool is independant of the others. If you are talking in the sense
like microsoft has global params and scop params etc... Cisco has only scope
params.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
dave hart
Sent: Tuesday, August 15, 2000 3:56 AM
To: Derek Buelna; 'ccielab@groupstudy.com'
Subject: Re: DHCP
Derek,
How do you tell one pool that it is the parent. Is it
by allocating it the natural network of the child
pools. Also, i thought it was not critical to have to
store the database of on a dedicated server. except
for resiliance. if i wanted to use a tftp server for
storing the database. what would be the command syntax
?
--- Derek Buelna <dameon@aracnet.com> wrote: > Hi,
>
> I heard someone asking about DHCP and also that it
> may appear on the test, along with everything
> else...
>
> It is rather simple actually. A critical element is
> an IOS 12.0T train or better! You'll also need an
> ftp server or something that the router will use to
> store the database.
>
>
>
>
> -Derek
>
>
>
>
> > serv dhcp (default I think)
> ip dhcp database
> ftp://user:password@10.10.10.79/dhcp_db.wri
> write-delay 60
> ip dhcp excluded-address 10.10.10.1 10.10.10.189
> ip dhcp excluded-address 10.10.10.220 10.10.10.254
> !
> ip dhcp pool 10net
> network 10.10.10.0 255.255.255.0
> default-router 10.10.10.50
> domain-name syrex.com
> dns-server 205.159.88.1
> netbios-node-type h-node
> lease 3 2
>
> Washington#
>
> Washington#sh debug
> DHCP server packet debugging is on.
> Washington#
>
> Aug 15 06:17:03.978: DHCPD: DHCPDISCOVER received
> from client 0100.10a4.e58d.3f on interface Ethernet
> 0.
> Washington#
> Aug 15 06:17:05.982: DHCPD: Sending DHCPOFFER to
> client 0100.10a4.e58d.3f (10.10.10.190).
> Aug 15 06:17:05.986: DHCPD: creating ARP entry
> (10.10.10.190, 0010.a4e5.8d3f).
> Aug 15 06:17:05.986: DHCPD: unicasting BOOTREPLY to
> client 0010.a4e5.8d3f (10.10.10.190).
> Washington#
> Aug 15 06:17:08.002: DHCPD: DHCPDISCOVER received
> from client 0100.10a4.e58d.3f on interface Ethernet
> 0.
> Aug 15 06:17:08.002: DHCPD: Sending DHCPOFFER to
> client 0100.10a4.e58d.3f (10.10.10.190).
> Aug 15 06:17:08.006: DHCPD: creating ARP entry
> (10.10.10.190, 0010.a4e5.8d3f).
> Aug 15 06:17:08.010: DHCPD: unicasting BOOTREPLY to
> client 0010.a4e5.8d3f (10.10.10.190).
> Washington#
> Aug 15 06:17:15.022: DHCPD: DHCPDISCOVER received
> from client 0100.10a4.e58d.3f on interface Ethernet
> 0.
> Aug 15 06:17:15.022: DHCPD: Sending DHCPOFFER to
> client 0100.10a4.e58d.3f (10.10.10.190).
> Aug 15 06:17:15.026: DHCPD: broadcasting BOOTREPLY
> to client 0010.a4e5.8d3f.
> Aug 15 06:17:15.038: DHCPD: DHCPREQUEST received
> from client 0100.10a4.e58d.3f.
> Aug 15 06:17:15.042: DHCPD: Sending DHCPACK to
> client 0100.10a4.e58d.3f (10.10.10.190).
> Aug 15 06:17:15.046: DHCPD: broadcasting BOOTREPLY
> to client 0010.a4e5.8d3f.
> Washington#
>
> Washington#
> Writing dhcp_db.wri !
> Washington#sh ip dhcp data
> URL :
> ftp://user:password@10.10.10.79/dhcp_db.wri
> Read : Never
> Written : Aug 14 2000 11:37 PM
> Status : Last write succeeded. Agent information
> is up-to-date.
> Delay : 60 seconds
> Timeout : 300 seconds
> Failures : 0
> Successes: 1
>
> Washington#
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:26 GMT-3