[j-nsp] JUNOS Equivalent to CISCO IOS next-hop-self

[adel mezibra]

you may also use something like :

policy-statement color-external-neighbor {
        then {
            color 666;
        }
    }
policy-statement next-hop-self {
        from color 666;
        then {
            next-hop self;
        }
    }

and use color-external-neighbor as import policy in your core bgp mesh group

adel mezibra



-----Message d'origine-----
De : juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]De la part de Jeff Wheeler
Envoyé : lundi 15 décembre 2003 21:51
À : juniper-nsp at puck.nether.net
Objet : Re: [j-nsp] JUNOS Equivalent to CISCO IOS next-hop-self


I question the utility in using next-hop-self on internal sessions, or
even eBGP import policy-statements. In my ASes, I keep the remote (/30)
next-hop and import the /30s into my IGP. This allows me to tweak the
metrics on those /30s as another means of controlling my egress paths.

When you rewrite learnt next-hops to the addresses of your own routers,
you lose the ability to influence the IGP-cost step in BGP best-path
selection based on the specific eBGP peer.

One thing I have always wished for is the ability to skip the external >
internal step in best-path selection, which comes before IGP cost. This
would have to be applied through the entire AS to avoid inconsistent
best-path decisions (routing loops), but I think it would be useful.

--
Jeff at Reflected Networks

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp