Hi, On Tue, Jan 03, 2012 at 05:51:37PM +0100, Vitkovsky, Adam wrote: > Now here's the catch: > If I decide to use "ttl-security" in the session template on both ends I > won't get routing updates across the established session > Reason according to debug: -- DENIED due to: non-connected MP_REACH NEXTHOP;, > label 18
Unless you use "ebgp-multihop" or "disabled-connected-check", the
next-hop received must be in a locally connected(!) subnet on the
receiving side.
> -which is not true as the Inter-AS-route-reflector has a route to the
> originating PE in the other AS route is pointing to the ASBR connecting to
> the other AS
... which is not "connected". Very much not so :-)
Note that it doesn't tell you "non-reachable ... NEXTHOP" but "non-connected".
gert
no 4-letter certificates
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpFHDYvpajIM.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
