From: Petr Lapukhov (petr@internetworkexpert.com)
Date: Sun Dec 03 2006 - 04:21:04 ART
Ed,
As per standard troubleshooting recommendations, you need to investigate
& isolate the problem; Was IPsec involved in your configuration? If yes,
then
maybe IPsec SAs got unsynced on hub/spokes; you can get rid of this doing
"clear crypto sa" & "clear crypto isakmp".
If you suspect NHRP slowness, try setting NHRP hodltime to a low value
(e.g. 30 seconds) on spokes and hub; This way you'll force spokes to
re-register often on the hub.
Anyway, you should track the problem to it's rource, looking at crypto SAs,
NHRP caches, and debugging output to isolate the true reason. Also, in
complex scenarios it's often helpful to setup a simplified model (e.g. mGRE
only),
and try isolating problem with this 'parsimonic' scenario.
HTH
2006/12/3, Lab Rat #109385382 <techlist01@gmail.com>:
>
> I have DMVPN configured between three routers in a hub-and-spoke frame
> relay
> configuration.
>
>
>
> Why is it that, when my hub router crashed and came back (with the exact
> same config), it would not peer with the two spoke routers again?
>
>
>
> I tried shutting and no-shutting the tunnel and nothing happens. All
> loopback source addresses are ping-able.
>
>
>
> I solved this by copying the tunnel configurations off each router,
> deleting
> the tunnel interface, and then pasting them back in.
>
>
>
> This cleared everything up. Am I missing something regarding how NHRP
> times
> things out?
>
>
>
> Anyone?
>
>
>
> Thanks,
>
>
> Ed
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Petr Lapukhov, CCIE #16379 petr@internetworkexpert.comInternetwork Expert, Inc. http://www.InternetworkExpert.com Toll Free: 877-224-8987 Outside US: 775-826-4344
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:36 ART