A continue statement in a route map directs program flow to skip route map instances to another, user-specified instance. When a matched instance contains a continue statement, the system looks for the instance that is identified in the statement.
The continue statement in a matching instance initiates another traversal at the instance specified. The system records all of the matched instances and, if no deny statements are encountered, proceeds to run the set clauses of the matched instances.
The system does not update routes if it finds no matches in the route map instances or if it encounters a deny condition. When a matched instance contains a deny statement, the current traversal is terminated. None of the updates in the set statements of the matched instances in current and previous traversals are applied to the routes.
The continue statement feature supports a more programmable route map configuration and route filtering scheme for BGP4 peering. The feature can also execute additional instances in a route map after an instance is executed by means of successful match statements. You can configure and organize more modular policy definitions to reduce the number of instances that are repeated in the same route map.
This feature applies only to BGP4 routes. Continue statements are ignored for protocols other than BGP4.