[j-nsp] multiprotocol bgp and bgp reflection

[Richmond, Jeff]

The only other thing you have to watch for is how you have your next-hop self policy configured. The way we traditionally did it was causing problems when using route reflection. Instead of reworking the whole thing, I went and updated the policy with a new term to ignore anything with a community of target:*:* (basically if you match on that community, accept and jump out).

Shoot me an email if you want more detail.

-Jeff



-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Sean Clarke
Sent: Tuesday, January 23, 2007 6:40 AM
To: Benny Sumitro
Cc: juniper-nsp
Subject: Re: [j-nsp] multiprotocol bgp and bgp reflection



--

Not so long ago you wrote :
BS> The configuration is the same like configuring normal route
BS> reflector except you must enable family inet-vpn for L3VPN. The
BS> important thing is you must have a LSP to all PEs because without
BS> LSP or reachability, the RR will mark the routes as unusable and not advertised it to the PEs.

  Or  ..  you  add a discard route to the loopback addresse network on
  the  P-router  in  inet.3,  then  the  routes  will not be marked as
  unusable.  It's  easier  than  configuring  LSP's  between PE - P
  routers.

i.e.

# show routing-options
rib inet.3 {
    static {
        route 192.168.0.0/24 discard;
    }
}  

cheers
Sean
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp