NSX Edge supports static and dynamic (ospf, bgp) routing.
To configure routing, in vCloud Director, go to Administration and click on the virtual data center. From the horizontal menu, select the tab Edge gateways. Right-click on the desired network and select the option Edge Gateway Services.
Go to the Routing menu.
Initial Configuration (Routing Configuration)
In this deposit, you can:
— activate the ECMP parameter, which allows you to set up to 8 equivalent routes in the RIB.
- change or disable the default route.
- select Router-ID. As Router-ID, you can select the address of the external interface. Without the Router-ID, it is not possible to start the OSPF or BGP processes.
Or add your own by clicking +.
We save the configuration.
Done.
Setting up static routing
Go to the Static routing tab and click +.
To add a static route, fill in the following required fields:
— Network—destination network;
- Next Hop - IP addresses of the host / router through which traffic will pass to the destination network;
- Interface - the interface behind which the required Next Hop is located.
Click Keep.
We save the configuration.
Done.
Configuring OSPF
Go to the OSPF tab. Enable the OSPF process.
If required, disable Graceful restart, which is enabled by default. Graceful restart is a protocol that allows you to continue forwarding traffic during the process of control plane convergence.
Here you can also activate the default route announcement, if it is in RIB - the default originate option.
Next, add Area. Area 0 is added by default. NSX Edge supports 3 types of Area:
- Backbone area (area 0+Normal);
— Standard area (Normal);
- Not-so-stubby area (NSSA).
Click + in the Area Definition field to add a new Area.
In the window that appears, specify the following required fields:
- Area ID;
— area type.
If required, set up authentication. NSX Edge supports two types of authentication: clear text (password) and MD5.
Click Keep.
We save the configuration.
Now add the interfaces on which the OSPF neighbor will be raised. To do this, click + in the Interface Mapping field.
In the window that appears, specify the following parameters:
- Interface - the interface that will be used in the OSPF process;
- Area ID;
— Hello/Dead interval — protocol timers;
— Priority – priority required to select DR/BDR;
- Cost - the metric needed to calculate the best path. Click Keep.
Let's add an NSSA Area to our router.
We save the configuration.
In the screenshot below we see:
1. established sessions;
2. established routes in RIB.
Configuring BGP
Go to the BGP tab.
Enable the BGP process.
If required, disable Graceful Restart, which is enabled by default. Here you can also activate the default route announcement, even if it is not in the RIB - the Default Originate option.
Specify the AS of our NSX Edge. 4-byte AS support only available from NSX 6.3
To add a Neighbors peer, click +.
In the window that appears, specify the following parameters:
— IP Address—BGP peer address;
— Remote AS—AS BGP number of the peer;
- Weight - a metric that can be used to control outgoing traffic;
- Keep Alive/Hold Down Time - protocol timers.
Next, we will configure BGP Filters. For an eBGP session, by default, all advertised and received prefixes on this router are filtered, except for the default route. It is announced with the default originate option.
Click + to add BGP Filter.
Set up a filter for an outgoing update.
Set up a filter for an incoming update.
Click Keep to complete the setup.
Save the configuration.
Done.
In the screenshot below we see:
1. established session.
2. received prefixes (4 prefixes /24) from BGP peer.
3. default route announcement. The 172.20.0.0/24 prefix is not advertised as it is not added to BGP.
Configuring Route Redistribution
Go to the Route Redistribution tab.
Enable route import for the protocol (BGP or OSPF).
To add an IP prefix, click +.
Specify the name of the IP prefix and the prefkis itself.
Set up a Route Distribution Table. Click +.
- Prefix Name - select the prefix that we will import into the corresponding protocol.
- Learner Protocol - the protocol where we will import the prefix;
- Allow learning - protocol, from where we export the prefix;
- Action - the action that will be applied to this prefix.
We save the configuration.
Done.
The screenshot below shows that a corresponding announcement has appeared in BGP.
That's all about routing with NSX Edge. Ask if something is unclear. Next time we will deal with the balancer.
Source: habr.com