On (2012-07-10 18:51 +0300), Alex K. wrote: > to turn the import/export process to something more evolved than list of > RTs. Each route you're exporting or importing, can go thru elaborate set of > filters JunOS provide all of us with – and, as a result, be attached with > different RTs, SoO and other BGP communities.
IOS has the same. ip vrf foo export map vrf-export ! route-map vrf-export permit 100 set extcommunity foo Infact IOS is IMHO better with this regard, as you can use both, you can use route-targets _AND_ maps. So just because you want to enable say VRF MGMT, does not mean you need per-customer route-maps/policies like in JunOS. However, I don't think even this support SOO, RT and regular community at least would work. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
