> This might work:
>
> [edit routing-options]
> # show generate
> route w.x.y.z/28 policy MATCH-16;
>
>
> [edit policy-options]
> # show policy-statement MATCH-16
> term 1 {
> from {
> route-filter w.x.0.0/16 exact;
> }
> then accept;
> }
> term 2 {
> then reject;
> }
I don't think so. Aggregate and generate routes
need to have contributors which have _longer_
prefix lengths than the route being created....
_______________________________________________
juniper-nsp mailing list juniper-nsp puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
|