AFAIK there is no special interaction between SRM and HSRP.
You might want to use the 'standby preempt delay ' feature
to be sure that routing protocols have converged before the router
is taking over hsrp active router functionality.
http://www.cisco.com/warp/public/619/hsrpguide4.shtmlT
hth
Eric, Reinhold,
Thank you. It makes sense that if the non-DR MSFC doesn't maintain a
routing table (which it apparently doesn't), the standby HSRP router would
need to handle traffic for at least a brief while. Delaying the preempt on
the non-DR sounds like a wise move. Or maybe not using
This is very closely related to another active thread but thought I should
probably start another. I know better than to post on a Friday and expect
much of an answer, but I could really use some insight on this one...
I recently was looking at a network about to roll into production. It's a
Scott,
Normal HSRP rules would be in effect in this scenario
I would say (haven't done this yet). If the failed
unit had a higher HSRP priority and was configured to
preempt then when it came back online it would become
active HSRP router.
--- s vermill wrote:
This is very closely related to
4 matches
Mail list logo
