Configuring Route Maps in Gaia Clish

Route maps support both IPv4 and IPv6 protocols, which includes RIP, RIPng, BGP, OSPFv2, and OSPFv3.

You can only define BGP-4 Multiprotocol Extensions policy with route maps.

For the other protocols, you can use route maps or the Route Redistribution and Inbound Route Filters features that you configured.

Each route map includes a list of criteria and statements. You can apply route maps to inbound, outbound, or redistribution routes. Routes are compared to the match criteria, and all the actions defined in the criteria are applied to those routes which match all the criteria. You can set the match criteria in any order. If you do not define match criteria 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.

To create a route map, use CLI commands to define a set of criteria that must be matched for the command to run. If the criteria are matched, then the system runs the actions you define. A route map is identified by a name and a 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 all the criteria of a route map instance are matched, or all the instances of a route map are exhausted. If the criteria are matched, the actions in the section are run.

Routing protocols can use more than one route map when you set clear preference values for each. The applicable route map with lowest preference value is checked first.

Important: - Route maps override the settings configured in Gaia Portal Web interface for the Check Point Gaia operating system..

For more information, see sk100501: How to configure Routemaps in Gaia Clish.