Hi Jurgen, Thank for your message.
But it was not my decision to put the continue clause in that position. It is IOS that did so, whatever the order you configure your "set" and "continue" statements. Yann 2011/2/15 Jurgen Marenda <[email protected]> > > Yann, > > you have configured a rout-map with a > "Match operations with Continue Clauses" > instead of a "Set Operation with Continue Clauses" : > > > route-map PEER-OUT permit 10 > > match community 1 > > continue > ---!!!!!!!! > > set community 1:100 additive > > The "continue" should go for the desired behaviour > behind the set clause to read: > > ! > route-map PEER-OUT permit 10 > match community 1 > set community 1:100 additive > continue > ! > > See: > > http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gt_brmcs.html > > Juergen. > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
