From: ccie2be (ccie2be@nyc.rr.com)
Date: Fri Nov 12 2004 - 16:08:36 GMT-3
Hey David,
Thanks alot for your response.
Both of your ideas sound excellent so I'm gonna try them out and see which
one works best for me. .
But, I have to admit I don't know how to change the register to make the
router look like a client. Actually, I don't recall ever hearing of that
being done. I know how to change the register, for example, to do a
password recovery but can you explain how to make the router "appear" like a
client or point me to a link that explains that?
Also, when you say make the router look like a client, you mean a dhcp
client, right?
And, when the register is changed, how does the router behave as compared to
when just the interface is made a dhcp client?
Thanks again, Tim
----- Original Message -----
From: "David Buechner" <dbuechn@attglobal.net>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Mark H. Turpin" <MHTurpin@basspro.com>;
"Group Study" <ccielab@groupstudy.com>
Sent: Friday, November 12, 2004 1:24 PM
Subject: Re: DHCP config on an HSRP segment
> You can always temporarily reconfigure one of your other routers to be a
> DHCP client. If I were under time pressure I'd make sure I saved the
> config somewhere like Notepad first! :-) Another option is to change the
> config register on your "look like a client" test router so that it
ignores
> the config in NVRAM for the duration of your testing. As long as you
don't
> save any config changes your original config will be preserved. Just make
> sure to change the config register back!
>
> I've used this technique in various scenarios to test DHCP, planning for a
> another router to be added to a routing domain, etc.
>
> HTH!
>
> David Buechner, CCIE #13539
>
> At 05:13 PM 11/11/2004, ccie2be wrote:
> >Thanks for confirming that. That's what I figured.
> >
> >Have any suggestions for how I can verify the config in the lab where
there
> >aren't any real dhcp clients?
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:42 GMT-3