Configure Route Map on devices

efa policy route-map create ?
Flags:
      --name string           Name of route-map
      --rule stringArray      Rule in format seq[seq-num],action[permit/deny]

The following is an example of creating a route map rmap_1 with two rules:

efa policy route-map create –-name rmap_1 –-rule seq[5],action[permit] –-rule seq[10],action[permit]

The update command configures the route map on device, removes configuration from a device or updates action of route-maps.

efa policy route-map update ?
Flags:
      --name string      Name of route-map
      --rule string      Rule in format seq[seq-num],action[permit/deny]
      --operation string Valid options are add-device, remove-device, update-action
      --ip string        Comma separated range of device IP addresses. Example: 1.1.1.1-3,1.1.1.2,2.2.2.2

• You can associate a route map with multiple rules.
• The add-device operation adds all the rules of the route map on the specified devices.
• The delete-device operation deletes all the rules of the route map on the specified devices.

For an update-action operation, specify the route map name and the rule. You can modify the action to permit or deny for a specific rule. You can provide only one rule at a time.

The IPv4 prefix list is the only match supported.

efa policy route-map-match create ?
Flags:
      --name string              Name of route-map
      --rule string              Rule in format seq[seq-num],action[permit/deny]
      --match-ipv4-prefix string IPv4 prefix-list name

The following is an example of route map match create in IPv4:

efa policy route-map-match create –-name rmap_1 –-rule seq[5],action[permit] --match-ipv4-prefix prefix_1

The IPv4 prefix list is the only match supported.

efa policy route-map-match delete ?
Flags:
      --name string              Name of route-map
      --rule string              Rule in format seq[seq-num],action[permit/deny]
      --match-ipv4-prefix string IPv4 prefix-list name

The following is an example of route map match delete in IPv4:

efa policy route-map-match delete –-name rmap_1 –-rule seq[5],action[permit]

In the command output, the App State column reflects the state of configuration on the specified device. When there is drift in a rule, the App State is shown as cfg-refreshed.

efa policy route-map list ?
Flags:
      --ip string     Comma separated range of device IP addresses. Example: 1.1.1.1-3,1.1.1.2,2.2.2.2

Example:

efa policy route-map list –-ip 10.20.246.10-11  
 
Route-map details: 
 
Name: rmap_1 
Seq: 5 
Action: permit 
Match-ipv4-prefixlist: 
    Prefix-list: prefix_1 
 
Name: rmap_2 
Seq: 5 
Action: permit 
Match-ipv4-prefixlist: 
    Prefix-list: prefix_1 

IP Addresses: 
+----------------+-----+---------------+-----------------+ 
|     Name     | Seq |  IP Address   |     App State     | 
+--------------+-----+---------------+-------------------+ 
| rmap_1       |  5  | 10.20.246.10  |    cfg-in-sync    | 
+--------------+-----+---------------+-------------------+ 
| rmap_1       |  5  | 10.20.246.11  |    cfg-in-sync    | 
+--------------+-----+---------------+-------------------+ 
| rmap_2       |  5  | 10.20.246.10  |    cfg-in-sync    | 
+--------------+-----+---------------+-------------------+ 
| rmap_2       |  5  | 10.20.246.11  |    cfg-in-sync    | 
+--------------+-----+---------------+-------------------+ 

efa policy route-map delete ?
Flags:
       --name stringArray      Name of route-map
       --seq string            Sequence numbers. For example 5,10,20, or all

• The command removes the route map rule from the XCO database and from the associated devices.
• You can delete a specific rule of a route map by specifying the route map name and the sequence number of the rule.
• You can delete all the route map rules for a specific route map name by specifying the sequence number as "all".
• The result of this command depends on whether the route map is bound with a BGP neighbor.
  • If the route map is bound to BGP peer, you cannot delete the last route map rule.
  • If the route map has no bindings, the command deletes the configuration on all devices associated with the route map.

The following example deletes two rules with sequence numbers 5 and 10 from a route map (rmap_1) that has three rules:

• rmap_1 seq 5 action permit
• rmap_1 seq 10 action permit
• rmap_1 seq 20 action permit
  

  efa policy route-map delete –-name rmap_l –-seq 5,10