[j-nsp] BGP Communities and exports

[Richard A Steenbergen]

On Wed, Oct 18, 2006 at 02:22:10PM -0400, James Cornman wrote:
> Agreed, however, I'd rather the route get into BGP with the community
> aside from setting it on EVERY individual neighbor.
> 
> In cisco land, doing a network 10.59.235.0 mask 255.255.255.0 route-map
> BGP-Origination, would do the trick. Is their a similar functionality
> here?

Yeah Juniper doesn't work like that. As you said, in Cisco-land you can 
inject a route into BGP once, and then it is "already in BGP" by the time 
you go to export routes. In Juniper-land, there is only export policy, and 
you must explicitly add the route every time you export.

Personally I like the Cisco method more, but Juniper wants *everything* 
done via policy-statements (same issue with prefix filtering, etc. You get 
more control, but you also get big unwieldly and unnecessarily complex 
policy statements. :)

What you want is something like:

policy-statement bgp-announce {
    term your_existing_bgp {
        from { community YOUR_CUSTOMER_ROUTES_TAG; }
        then { next policy; }
    }
    term local-origination {
        from { prefix-list bgp-origination; }
        then { next policy; }
    }
    then reject;
}

prefix-list bgp-origination {
    10.59.235.0/24;
}

bgp {
...
    neighbor export [ bgp-announce your-other-chains-here ];
}

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)