Route Maps - Configuration Commands
|
Important - In a Cluster |
-
To see the available "
set
" commands for Routemaps, enter in Gaia ClishThe name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell).:
set routemap[Esc][Esc]
-
To see the configured Routemaps, enter in Gaia
Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. Clish:
show routemaps
show routemap <Name of Route Map> {all | id <1-65535>}
|
Important - Some statements have an effect on some protocols only. The same parameter cannot appear both as a " |

|

|

|
|
|
|

Parameter |
Description |
|||
---|---|---|---|---|
|
Configures Route Map match conditions. |
|||
|
Configures the Route Map to only match routes being received from or advertised to the specified BGP Autonomous System number. Multiple AS match conditions can be configured for a given Route Map ID. A match will occur if any one of the AS match conditions matches a given route.
|
|||
|
Configures a regular expression to match the BGP Autonomous System Path (AS Path). Configures a route origin. |
|||
|
A valid AS_PATH regular expression contains only digits and these special characters:
|
|||
|
The route origin:
|
|||
|
Configures the Route Map to match the specified Community ID and Community AS number attributes of BGP routes.
|
|||
|
Matches exactly the set of configured Communities against the entire BGP Communities attribute. You must add the Community String(s) to be matched to this Route Map ID with this command:
|
|||
|
Matches routes, which have the No-Advertise option set in the BGP Communities attribute. Routes with this value are not advertised to any BGP peers.
|
|||
|
Matches routes, which have the No-Export option set in the BGP Communities attribute. Routes with this value are not exported outside a BGP Confederation boundary. This option also applies to stand-alone Autonomous Systems, which are not part of a Confederation.
|
|||
|
Matches routes, which have the No-Export-Subconfed option set in the BGP Communities attribute. Routes with this value are not exported outside a BGP Autonomous System. For Confederations, routes are not exported to routers that have a different Routing Domain Identifier.
|
|||
|
Matches routes, which have an empty BGP Communities attribute.
|
|||
|
Configures a regular expression to match the BGP Community.
|
|||
|
Configures the Route Map to match the specified interface IP address. The specified IP address is matched against the IP address of the interface, which received the route. This match condition only applies to routes received through dynamic routing protocols and is otherwise ignored. For example, static routes match the Route Map, even though they were not received from the interface IP address specified by this match condition. There can be multiple interface address match conditions under the same Route Map ID. This type of match condition applies to Route Maps, which are used with the "
|
|||
|
Configures the Route Map to match the specified interface name. There can be multiple interface match conditions under the same Route Map ID. This type of match condition applies to Route Maps, which are used with the "
|
|||
|
Configures the Route Map to match routes that have a specific metric. This match condition is applicable for RIP, BGP, and OSPF.
|
|||
|
Configures the Route Map to match routes from the specified neighbor. This match rule Multiple neighbor match conditions can be configured for a given Route Map ID. |
|||
|
Configures the Route Map to match routes, which are based on the specified IPv4 or IPv6 subnet. |
|||
|
Configures the Route Map to match all subnets, which are equal to, or contained within the specified IPv4 or IPv6 subnet.
|
|||
|
Configures the Route Map to match routes that are within the specified IPv4 or IPv6 subnet, and which have a mask length that is between the specified range of values. To resolve conflicts in match conditions, Route Maps are ordered by ID. For a specified Route Map, the match conditions under ID 1 take precedence, followed by ID 2, and so on.
|
|||
|
Configures the Route Map to only match routes, which have the same prefix and mask length as the specified IPv4 or IPv6 subnet.
|
|||
|
Removes the network match condition. |
|||
|
Configures the Route Map to match routes, which are contained within the specified IPv4 or IPv6 subnet. Routes that exactly match the specified subnet (have the same mask length), are excluded from the match.
|
|||
|
Configures the Route Map to match routes that have the specified IPv4 or IPv6 next hop gateway address. Multiple next hop match conditions can be configured for a given Route Map ID. A match occurs, if any of the next hop values are matched by a specified route. This match is only applicable when you use the " |
|||
|
Matches routes learned from a specific OSPF Instance. This only affect routes from OSPF. |
|||
|
Configures the Route Map to match the specified Prefix List. Each route is matched against the specified prefix list's prefixes and is accepted or rejected according to the prefix list's policy. Multiple prefix lists may be matched, and are considered in order of preference (from low to high). Prefix lists may be used for either " A specified Route Map ID may only match one of these types:
|
|||
|
Removes the prefix list match condition. |
|||
|
Configures the preference for this match statement. Groups of prefixes are matched in increasing order of preference, until a match is found.
|
|||
|
Creates the prefix list match condition. |
|||
|
Configures the Route Map to match the specified Prefix Tree. Each route is matched against the specified prefix tree's prefixes and is accepted or rejected according to the prefix tree's policy. Multiple prefix trees may be matched, and will be considered in order of preference (from low to high). Prefix trees may be used for either " A specified Route Map ID may only match one of the following types:
|
|||
|
Removes the prefix tree match condition. |
|||
|
Configures the preference for this match statement. Groups of prefixes are matched in increasing order of preference, until a match is found.
|
|||
|
Creates the prefix tree match condition. |
|||
|
Configures the Route Map to match routes of the specified protocol type. Use this match for route redistribution between protocols.
|
|||
|
Removes all BGP Autonomous System match conditions from this Route Map ID. |
|||
|
Removes the BGP AS-Path RegEx match condition from this Route Map ID. |
|||
|
Removes all BGP Community match conditions from this Route Map ID. |
|||
|
Removes the BGP Community match condition. |
|||
|
Removes all interface address match conditions from this Route Map ID. |
|||
|
Removes all interface name match conditions from this Route Map ID. |
|||
|
Removes the metric match conditions from this Route Map ID. |
|||
|
Removes the neighbor match conditions from this Route Map ID. |
|||
|
Removes the network address match conditions from this Route Map ID. |
|||
|
Removes the nex thop gateway match conditions from this Route Map ID. |
|||
|
Removes the OSPF instance match conditions from this Route Map ID. |
|||
|
Removes the prefix list match conditions from this Route Map ID. |
|||
|
Removes the prefix tree match conditions from this Route Map ID. |
|||
|
Removes the protocol match conditions from this Route Map ID. |
|||
|
Removes all route type match conditions from this Route Map ID. |
|||
|
Removes all OSPF Tag match conditions from this Route Map ID. |
|||
|
Configures the Route Map to match the specified route type. This match condition is only applicable when used with the " For example:
During the export OSPF ASE routes to other protocols, if the metric match condition is set, but the route type match condition is not set, the routing system tries to match the metric value for both There can be multiple route type match conditions.
|
|||
|
Configures the Route Map to match OSPF external routes with the specified tag value. Multiple tag match conditions can be added to a given Route Map ID to broaden the range of tag values which are matched. Currently this feature can only be used to export OSPF routes to BGP.
|
|||
|
Configures action to perform on matching routes. |
|||
|
Causes the local Autonomous System (AS) number to be affixed to the beginning of the AS path when routes matching the Route Map are advertised through BGP. The provided value indicates the number of times the local AS number should be prepended. This action only applies to BGP, and only applies when you export routes with the " |
|||
|
Configures actions to alter the Communities attribute of BGP routes matched by this Route Map ID. The Community Action List configured here and the configured operation determine how the BGP Communities attribute are altered. |
|||
|
Configures the Route Map to append a Community with the specified Community ID and Community AS number to the Community Action List.
|
|||
|
Configures the Communities in the Community Action List to be appended to the BGP Communities attribute of BGP routes matched by this Route Map ID.
|
|||
|
Configures the Communities in the Community Action List to be deleted from the existing BGP Communities attribute of BGP routes matched by this Route Map ID.
|
|||
|
Appends the special Community "NO_ADVERTISE" (65535:65282) to the Community Action List. Routes with this value are not advertised to any BGP peers.
|
|||
|
Appends the special Community "NO_EXPORT" (65535:65281) to the Community Action List. Routes with this value are not exported outside a BGP Confederation boundary. This option also applies to stand-alone Autonomous Systems, which are not part of a Confederation.
|
|||
|
Appends the special Community "NO_EXPORT_SUBCONFED" (65535:65283) to the Community Action List. Routes with this value are not exported outside a BGP Autonomous System. For Confederations, routes are not exported to routers that have a different Routing Domain Identifier.
|
|||
|
Configures no BGP Community attribute to be sent, regardless of any existing BGP Community attribute.
|
|||
|
Configures the Communities in the Community Action List to replace all Communities in the BGP Communities attribute of BGP routes matched by this Route Map ID. If the Community Action List is empty, the BGP Communities attribute remains unchanged.
|
|||
|
Configures the local preference for iBGP routes which match this Route Map. This action only applies to the iBGP protocol, and only to Route Maps, which are used with the " |
|||
|
Increments the metric of matching routes by the specified amount. This action only applies when:
Otherwise, this action has no effect. For example, when you import OSPF/OSPFv3 routes from other routers.
|
|||
|
Configures the metric to the RIP metric value and adds the specified constant to it. This action only applies when you export OSPF/OSPFv3 or RIP/RIPng routes to BGP with the " The valid range of values for the resulting metric is 0 - 4294967295. |
|||
|
Configures the metric to the RIP metric value and subtracts the specified constant from it. This action only applies when you export OSPF/OSPFv3 or RIP/RIPng routes to BGP with the " The valid range of values for the resulting metric is 0 - 4294967295. |
|||
|
Decrements the metric of matching routes by the specified amount. This action only applies when:
Otherwise, this action has no effect. For example when you import OSPF/OSPFv3 routes from other routers.
|
|||
|
Configures the metric of matching routes to the specified value. When you export to IPv4 RIP or IPv6 RIPng, this action sets the RIP metric. The valid range of values is 1 - 65535, where 16 or greater indicates the route is unreachable.
This action only applies to Route Maps used with the "export-routemap" command. Otherwise, this action has no effect. |
|||
|
Configures the IPv4 next hop address for matching BGP routes. The next hop address value in the match condition cannot be a link-local address. This action only applies when you import BGP routes from, or export BGP routes to another router. When operating as a route reflector, the next hop is not changed for any route learned from iBGP when the route is being exported to an internal BGP peer. |
|||
|
Configures the IPv6 next hop address for matching BGP routes. The next hop address value in the match condition cannot be a link-local address. This action only applies when you import BGP routes from, or export BGP routes to another router. When operating as a route reflector, the next hop is not changed for any route learned from iBGP when the route is being exported to an internal BGP peer. |
|||
|
Configures the automatic tag for OSPF external routes that match the Route Map. This action only applies when you export non-OSPF routes into OSPF with the " See RFC 1403 for more information on OSPF tags. |
|||
|
Configures the manual tag for OSPF external routes that match this Route Map ID. This action only applies when you export non-OSPF routes into OSPF with the " See RFC 1403 for more information on OSPF tags. |
|||
|
Configures the precedence of routes, which match this Route Map ID. If the same route is being imported into the kernel routing table from multiple sources (multiple protocols), the precedence values are compared to determine which route is preferred. The lower value has priority. The non-preferred routes are marked as inactive and not installed in the kernel. This action only applies when you use the " |
|||
|
Configures the BGP preference of routes, which match this Route Map ID. This action applies only to routes received via BGP advertisements. This is equivalent to the BGP weight (in Cisco terms) of the route. However, unlike Cisco, the route with lower value is preferred. Routes with any weight are preferred over routes without a weight. The preference value is only applicable for the local router. |
|||
|
Removes the |
|||
|
Removes all Community action statements from this Route Map ID. |
|||
|
Removes the local preference action statements from this Route Map ID. |
|||
|
Removes the metric action statements from this Route Map ID. |
|||
|
Removes the IPv4 next hop action from this Route Map ID. |
|||
|
Removes the IPv6 next hop action from this Route Map ID. |
|||
|
Removes the OSPF automatic tag action statements from this Route Map ID. |
|||
|
Removes the OSPF manual tag action statements from this Route Map ID. |
|||
|
Removes the precedence action statements from this Route Map ID. |
|||
|
Removes the preference action statements from this Route Map ID. |
|||
|
Removes the RIP tag action statements from this Route Map ID. |
|||
|
Removes the route type action statements from this Route Map ID. |
|||
|
Configures the RIP tag for external routes that match this Route Map ID. |
|||
|
This action only applies when you export non-RIP routes into RIP with the " See RFC 2453 for more information on RIP route tags. |
|||
|
Allows all matching routes, unless specifically restricted. |
|||
|
Disables the Route Map ID (use " |
|||
|
Removes ( Range: 1-65535 Default: 10 |
|||
|
Restricts all routes, unless specifically accepted. |