From: David Luu (wicked01@xxxxxxxxxxxxx)
Date: Fri May 24 2002 - 00:44:40 GMT-3
i believe DHCP redundancy can be accomplished through HSRP, there is
another way, but it escapes me at the moment, when i remember it, i will
post it up
At 10:40 PM 5/23/2002 -0400, p729@cox.net wrote:
>I don't believe so. Since the DHCP request is a broadcast, the CNR main
>and backup DHCP servers have to track each other's state so that each one
>knows who's supposed to fulfill the request for a given scope. As far as I
>know, there is no provision for this with the IOS DHCP server and you can
>only get a small measure of redundancy by splitting the scopes across two
>servers without overlap.
>
>Regards,
>
>Mas Kato
>https://ecardfile.com/id/mkato
>
>============================================================
>From: "CCIE-Maillist" <CCIE-Maillist@foxgal.com>
>Date: 2002/05/23 Thu AM 07:02:27 EDT
>To: <ccielab@groupstudy.com>
>Subject: Cisco IOS DHCP primary/secondary server on same VLAN
>
>With the Cisco IOS DHCP server feature, is there some way to have one server
>as the primary server and another as the backup, on the same vlan, with an
>automatic "failover", such that clients go to one Cisco router DHCP server and
>if that one goes down, the second one answers?
>
>(this is WITHOUT using a product like Cisco Network Registrar)
>
>I know that I could configure two Cisco IOS DHCP servers on the same vlan with
>different scopes and that would make two servers available. The first one to
>answer the broadcast for DHCP services would provide the service to the
>client. BUT, how would I have one server be preferred over the other in that
>situation, or another one that someone can come up with?
>
>*** Does this command do that or is this just for TFTP download?
>
>next-server
>To configure the next server in a Dynamic Host
>Configuration Protocol
>(DHCP)
>client's boot process, use the next-server DHCP pool
>configuration
>command.
>Use the no form of this command to remove the boot
>server list.
>
>next-server address [address2...address8]
>
>no next-server address
>
>
>Syntax Description
>address
>Specifies the IP address of the next server in the
>boot process, which
>is
>typically a Trivial File Transfer Protocol (TFTP)
>server. One IP
>address is
>required, although you can specify up to eight
>addresses in one command
>line.
>
>
>
>
>Defaults
>If the next-server command is not used to configure a
>boot server list,
>the
>DHCP server uses inbound interface helper addresses as
>boot servers.
>
>Command Modes
>DHCP pool configuration
>
>Usage Guidelines
>This command first appeared in Cisco IOS Release
>12.0(1)T.
>
>You can specify up to eight servers in the list.
>Servers are listed in
>order
>of preference (address1 is the most preferred server,
>address2 is the
>next
>most preferred server, and so on).
>
>Examples
>The following example specifies 10.12.1.99 as the IP
>address of the
>next
>server in the boot process:
>
>next-server 10.12.1.99
>
>Related Commands
>bootfile
>ip dhcp pool
>ip helper-address
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:07 GMT-3