On Wed, Nov 4, 2009 at 8:48 AM, Nathan Richie <nathanr_at_boice.net> wrote:
> Thanks Roy & Mark. I am going to chalk this "feature" up to software engineers on crack when writing code :)
Thinking out loud.. I guess it could be useful in a template /
cookie-cut config scenario.
Imagine you had an existing WAN router deployment at your branch
offices, and you were adding a second link and router for fault
tolerance and engaging a third party integration company to deploy the
new kit. In combination with other IOS features, you could come up
with a single standard config that could be applied to every new
router to be deployed. The 2nd router at each branch location could
'learn' the existing LAN-side HSRP VIP from the existing router
without you needing to hard-code it in the config.
There are almost certainly better ways to manage deployments like
this, but it might be OK for some scenarios. For the record, we always
hard-code VIPs on all group members :-)
If standby group members picked up the new IP when changed on the
active router, the feature could be more useful in the real world. In
the context of the CCIE lab, I agree with Roy, it's just about knowing
how to deal with a task where, for example, you're asked to configure
HSRP but explicitly told not to configure the VIP on one of the
routers.
cheers,
Dale
Blogs and organic groups at http://www.ccie.net
Received on Wed Nov 04 2009 - 09:26:06 ART
This archive was generated by hypermail 2.2.0 : Tue Dec 01 2009 - 06:36:28 ART