[j-nsp] vpn-apply-export

[Gary Tate]

A behavioural change was indeed introduced in 5.7R1 to do an implicit 
vpn-apply-export when RR or ASBR functionality is enabled.  This was 
introduced as part of PR27920.

So what you are seeing is the following:

Your vrf policy is accepting the vrf static route which which moves it 
to the l3vpn.bgp table.

The route attributes are maintained and it is therefore still seen as 
static.

The next stage is to apply the pe-pe policy to routes in the l2vpn.bgp 
table, which in your case rejects the route - your final statement is 
to reject all.

As you have seen the addition of protocol static or the addition to a 
match on the vrf-target fixed your problem.

In short, as you first speculated, the router does have an implicit 
vpn-apply-export and hence you see this behaviour.

I have taken steps to document more clearly this change in behaviour.

Sorry for the earlier confusion, I missed the cluster id which should 
have alerted me to the fact that this was an PE-RR combined 
configuration.


Gary