Hi All, During translation from JunOS to IOS I ran into interesting problem.
Juniper CLI has an option called vrf-export. I basically replace the basic RTs export with a policy which allows you to put any community wherever you want. Now, in this particular network, every Juniper box attaches the same SoO to every route it exports (per VRF, i.e. every VRF has its own SoO). Many traffic flows are based on this idea. For instance, a router will prefer a path to the nearest router advertising a prefix (based on matching the SoO). Cisco, on the other hand, does what the SoO is intended to do. In Cisco's world, there is no way to put a SoO on each and very route being exported from a VRF. Cisco simply says, put a SoO on the interface connected to the multi-homed CE and we'll do the rest. Now, that's perfectly fine with me and that's what SoO should do in the first place but that's not the way it goes here. We're talking of moving configuration from some MX960 boxes to Cat6500/Sup-2T boxes and the idea to go over each and every interface of these and put there a sitemap sounds very unattractive. Not to mention is not as generic as it was before (i.e. Juniper attached SoO by export policy, now we need to remember the sitemap for every interface). I've tried vrf export-maps (did nothing as long as SoO is concerned), per neighbor SoO is not available. So the question is, will somebody here can come up with a trick to replicate JunOS behavior in a Cisco environment? Thanks in advance, Alex. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/