[j-nsp] vpn-apply-export

[harry]

I think I need to see the complete config to get a better handle. It sounds
like you are saying:

 term limited-routes {
        from {
            protocol [ bgp aggregate static ];
            as-path limited-routes;
        }
        then accept;
    }


Is part of your unicast PE-PE BGP routing policy. I assumed this was part of
your VRF related policies.



> -----Original Message-----
> From: Blaz Zupan [mailto:blaz at inlimbo.org] 
> Sent: Monday, November 10, 2003 8:58 AM
> To: harry
> Cc: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] vpn-apply-export
> 
> 
> > Hmmm. The static route does not appear to have the "from-customer 
> > from-lix from-six" communities attached, nor does it have 
> any as path 
> > attributes. I do not think the static should be advertised in this 
> > context, regardless of JUNOS version as you policy only 
> accepts routes 
> > with these attributes. You can add community/AS path 
> attributes to a 
> > static on routing-options; perhaps this information was 
> there at one 
> > time?
> 
> As I understand the documentation, if vpn-apply-export is not 
> configured, only vpn-import/vpn-export or vpn-target policy 
> apply to the routes created under the routing-instance. At 
> least that's how it worked with 5.5R1.2. When you configure 
> vpn-apply-export, it should first apply the 
> vpn-import/vpn-export or vpn-target and after that the normal 
> BGP policy. Problem is, it behaves for me like I have 
> vpn-apply-export configured, but I don't have it.
>