Configuring a Routemap in Gaia Clish

Each route map includes a list of match criteria and set statements. You can apply route maps to inbound, outbound, or redistribution routes.

Routes are compared to the match criteria, and all the actions specified in the set criteria are applied to those routes which meet all the match conditions.

You can specify the match conditions in any order. If you do not specify any match conditions in a route map, the route map matches all routes.

You define route maps, then assign them to protocols for export or import policy for that protocol.

Route maps take precedence over other Route Redistribution and Inbound Route Filters settings that you configure in Gaia Clish or Gaia Portal.

To create a route map, use CLI commands to specify a set of criteria that must be matched for the command to take effect. If the criteria are matched, then the system executes the actions you specify. A route map is identified by name and an identifying number, an Allow or Restrict clause, and a collection of match and set statements.

There can be more than one instance of a route map (same name, different ID). The lowest numbered instance of a route map is checked first. Route map processing stops when either all the match criteria of some instance of the route map are satisfied, or all the instances of the particular route map are exhausted. If the match criteria are satisfied, the actions in the set section are performed.

Routing protocols can use more than one route map when you specify distinct preference values for each. The appropriate route map with lowest preference value is checked first.