Using Extra Routes in Neutron

The Extreme Neutron L3 Router plugin and flavors implement the extra routes API that enables the addition of static routes via OpenStack. An extra route is added using the destination and gateway fields, representing the destination CIDR and the next hop gateway IP address. Deletion of routes can also be performed with equivalent REST API and CLI commands. Routes installed on the router can be listed with the openstack router show command.

The support is available for both IPv4 and IPv6 address families.

Note

• You can add a duplicate route, that is, one with the same destination CIDR and gateway, or delete a non-existing route to or from a router.
• There is no field available in the openstack router show command to display route status. Even if the static routes fail to configure on the fabric side, their status is not shown in OpenStack.
• Extra routes are supported only in extreme_v2 drivers with journaling support.

Border leaf pair selection

Creating a border leaf pair

openstack network efa-bl-pair-map create --name <string> --switch-ips <comma separated string of ips>

Example

openstack network efa-bl-pair-map create --name blp1 --switch-ips 10.2.2.2,10.2.2.3
+------------+--------------------------------------+
| Field      | Value                                |
+------------+--------------------------------------+
| id         | 0d19abc5-d31b-4682-b86d-cc1617ea0c97 |
| name       | blp1                                 |
| switch_ips | 10.2.2.2,10.2.2.3                    |
+------------+--------------------------------------+

You can also add the border leaf pair by using a topology link mapping file. In the topology link mapping border leaf pair, mappings can be provided in the new section [efa-bl-pairs]. This section should be provided after topology link mapping entries. If more than one entry is provided, then only the first entry will be considered.

Example

opensuse@Openstack114:~$ cat /home/opensuse/link.csv
Openstack115,eth1,default,10.24.14.133,0/1,lag_1
Openstack115,eth2,default,10.24.14.134,0/1,lag_1
Openstack116,eth1,PFPT_LAG,10.24.14.135,0/1,lag_2
Openstack116,eth2,PFPT_LAG,10.24.14.136,0/1,lag_2
Openstack117,eth1,VFPT_L10.24.14.136,0/1
DC-GW1, ,EXT1,10.24.14.191,0/1,lag_4
DC-GW1, ,EXT1,10.24.14.192,0/1,lag_4
[efa-bl-pairs]
Bleaf-1,10.2.2.2,10.2.2.3

The following fields are available for the efa-bl-pairs section:

Deleting border leaf pair

openstack network efa-bl-pair-map delete <id>

Example

openstack network efa-bl-pair-map delete 0d19abc5-d31b-4682-b86d-cc1617ea0c97

Listing border leaf pairs

openstack network efa-bl-pair-map list <id>

Example

openstack network efa-bl-pair-map list
+--------------------------------------+------+-------------------+
| ID                                   | Name | Switches          |
+--------------------------------------+------+-------------------+
| 0d19abc5-d31b-4682-b86d-cc1617ea0c97 | blp1 | 10.2.2.2,10.2.2.3 |
+--------------------------------------+------+-------------------+

Neutron EFA console commands

For convenience, Neutron EFA console commands are also provided in the topology plugin for adding, removing, and listing border leaf pairs.

For more details on the commands in this section, see EFA OpenStack Service Command Reference..

Creating border leaf pairs

efa-blpair-mapping add <id>

Example

efa-blpair-mapping add --name blp2 --switch-ips 10.2.2.4,10.2.2.3

Removing border leaf pairs

efa-blpair-mapping remove <id>

Example

efa-blpair-mapping remove --name blp2

Listing border leaf pairs

efa-blpair-mapping list <id>

Example

efa-blpair-mapping list
+--------------------------------------+------+-------------------+
| ID                                   | Name | Switches          |
+--------------------------------------+------+-------------------+
| 8f3d786b-70e3-4c8e-888c-4f95adc162f4 | blp2 | 10.2.2.4,10.2.2.3 |
+--------------------------------------+------+-------------------+