DHCP Stateful Configuration

From: Ken.Farrington@barclayscapital.com
Date: Mon Nov 24 2003 - 18:26:58 GMT-3


Is there such a thing?

Say a config below without HSRP. Or even with HSRP, the state (active
router could change)
Both routers will receive a DHCP request (packet shows IP broadcast), which
DHCP offer will the client pick up from which router.

Boring subject this one :) This should be for the windows guys...........
you know, those people that click and drag ?????

Only joking :)

Capture summary on the end of e-mail

Router 1

!
ip dhcp pool E0
   network 167.203.21.0 255.255.255.0
   default-router 167.203.21.1
   domain-name kenny
!
ip dhcp pool E1
   network 167.203.22.0 255.255.255.0
   default-router 167.203.22.1
   domain-name kennyF
!
interface Ethernet0
 description VLAN 1
 ip address 167.203.21.1 255.255.255.0
!
interface Ethernet1
 description VLAN 2
 ip address 167.203.22.1 255.255.255.0

Router 2

!
ip dhcp pool E0
   network 167.203.21.0 255.255.255.0
   default-router 167.203.21.2
   domain-name kenny
!
ip dhcp pool E1
   network 167.203.22.0 255.255.255.0
   default-router 167.203.22.2
   domain-name kennyF
!
interface Ethernet0
 description VLAN 1
 ip address 167.203.21.2 255.255.255.0
!
interface Ethernet1
 description VLAN 2
 ip address 167.203.22.2 255.255.255.0

    No. Time Source Destination Protocol
Info
      3 2.003610 167.203.22.5 224.0.0.13 PIMv2
Hello
      4 2.111123 167.203.22.6 224.0.0.10 EIGRP
Hello
      6 4.206077 167.203.22.5 224.0.0.10 EIGRP
Hello
      7 4.552545 Cisco_29:09:07 Cisco_29:09:07 LOOP
Loopback
      9 6.394249 0.0.0.0 255.255.255.255 DHCP
DHCP Discover - Transaction ID 0xdb0fe00d
     10 6.396530 167.203.22.6 167.203.22.2 ICMP
Echo (ping) request
     11 6.397800 167.203.22.5 167.203.22.2 ICMP
Echo (ping) request
     12 6.887026 167.203.22.6 224.0.0.10 EIGRP
Hello
     13 7.894996 167.203.22.6 167.203.22.2 ICMP
Echo (ping) request
     14 7.900174 167.203.22.5 167.203.22.2 ICMP
Echo (ping) request
     16 8.396142 167.203.22.6 167.203.22.2 DHCP
DHCP Offer - Transaction ID 0xdb0fe00d
     17 8.396487 0.0.0.0 255.255.255.255 DHCP
DHCP Request - Transaction ID 0xdb0fe00d
     18 8.399563 167.203.22.6 167.203.22.2 DHCP
DHCP ACK - Transaction ID 0xdb0fe00d
     19 8.401462 192.168.69.5 Broadcast ARP Who
has 167.203.22.2? Tell 167.203.22.2
     20 8.403970 167.203.22.5 167.203.22.2 DHCP
DHCP Offer - Transaction ID 0xdb0fe00d
     21 8.841820 167.203.22.5 224.0.0.10 EIGRP
Hello
     22 9.294380 192.168.69.5 Broadcast ARP Who
has 167.203.22.2? Tell 167.203.22.2
     24 10.295374 192.168.69.5 Broadcast ARP Who
has 167.203.22.2? Tell 167.203.22.2
     25 11.798999 167.203.22.6 224.0.0.10 EIGRP
Hello
     27 12.798965 167.203.22.2 40.25.1.87 NBNS
Multi-homed registration NB IBM-LAPTOP<00>
     28 12.799779 167.203.22.6 167.203.22.2 ICMP
Destination unreachable
     29 13.273276 167.203.22.5 224.0.0.10 EIGRP
Hello
     31 14.301138 167.203.22.2 30.25.1.87 NBNS
Multi-homed registration NB IBM-LAPTOP<00>
     32 14.301897 167.203.22.6 167.203.22.2 ICMP
Destination unreachable

------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.

Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.

------------------------------------------------------------------------



This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:16 GMT-3