Just an FYI:
I just had an outage on one of my primary circuits used by an OpenNHRP
spoke. Because the DMVPN device at this location had a secondary circuit
used for such an occasion, I stumbled across some undesirable behavior by
performing the following:
1) I changed *only* the route to the DMVPN hub (i.e. "route add host ...")
to go out through the secondary connection.
2) I changed racoon.conf to reflect the new isakmp listen address.
3) Restarted racoon and opennhrp services.
This caused the entire DMVPN to fail (all spokes down). Upon sober
inspection, I obviously need to re-route *all* other spokes through the
secondary as well. But this failure mode certainly shouldn't cause a
systemic outage.
I did not get a chance to confirm my suspicion (by setting spoke routes)
because the primary connection came back up just after this all happened.
Since this is a production network that spans many time zones, there is
little opportunity to do further testing. But I did want to report it for
the sake of continuous improvement.
Regards,
Darren
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
opennhrp-devel mailing list
opennhrp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opennhrp-devel
