On Sat, Apr 19, 2008 at 01:30:11PM +0200, Peter Rathlev wrote: > Hi, > > According to > > http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/cs_brmcs.html > > the "continue" route-map statement is only supported in the outbound > direction when running 12.0(31)S and later. According to the Feature > Navigator, 12.2(33)SRB + SRC also supports it, but 12.2(18)SXF doesn't. > > Now the strange thing is that I can use it fine in labs on 6500 and 7600 > SXF. I can configure it, and it works as I expect. > > Is it a very bad idea starting to use this in production? I haven't > tested SXH yet, and I am a bit worried, thinking this might be an > "unintended feature" like BFD+SVI. Anybody else using it with C6k, maybe > SXH?
Route-map outbound continue most definitely does not work in SXF, SXH, or SRA. It causes everything to leak through the route-map regardless of your matches, which is a very bad thing if you're applying it to a transit or peer session. Personally I'm baffled why it took them until SRB to fix such a massive glaring oversight. Route-map in general is already Cisco's weakest area compared to Juniper, and a working route-map outbound continue is one of the few ways to make route-maps even vaguely useable in comparison. Then again, we still don't have named as-path lists, and we still can't match named communities in a policy-list, so the list of absurd oversights is hardly short. For me, route-map outbound continue is the #1 motivator to run SRB+ over SXH right now, and I'm sure this applies to others as well. -- Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
