The advanced vDC gateway supports both static and dynamic routing including support for BGP, OSPF and IS-IS protocols. Routing functionality is enabled by default ensuring that Virtual Machines in a vDC can access both the internet and other connected networks.
Below are details on Routing options available on your NSX Advanced Networking Edge. For information about other features of NSX Advanced Networking click here.
On the General tab underneath the parent Routing tab, you can configure the Router ID for use on the gateway, this is by default the primary public IP address and in the majority of cases doesn’t need adjustment. Additionally, this tab allows you to configure and name prefixes to be used later in dynamic routing policy configuration.
The BGP tab enables configuration of both global BGP parameters such as local AS number, graceful restart, default route propagation and individual neighbor configuration. When configuring a neighbour, a neighbour address and remote AS number are required options – the default timer values are recommended for the majority of cases.
The OSPF tab allows vNIC interfaces to be added to OSPF areas, the default being area 0. Areas can be added and configured as either Normal or NSSA area types. It is important to note, that a single vNIC interface cannot be part of an IS-IS configuration as well as participating in OSPF at the same time.
The top section of the Static tab allows users to configure the default gateway for their Gateway. By default this section is configured automatically to ensure that Virtual Machines within a vDC can default route to the internet via the “NSX Uplink” interface (vNIC 0).
Static routes can also be configured in the lower section of this page. Users must give the route a name, set the outgoing vNIC interface and ensure the next-hop address given is within the subnet specified on the chosen vNIC interface.
Beneath the BGP, OSPF and IS-IS routing tabs, there is the option to enable Route Redistribution. This allows the routes learnt by one routing protocol to be propagated by another. When configuring route redistribution, you are required to select a named prefix configured under the General tab along with the source protocols from which the selected protocol is allowed to learn the route. For example, when configuring a BGP neighbour, you may with to allow the propagation of “Connected” routes (the interfaces attached to the Gateway) – ensure the “Connected” switch is selected when adding a route redistribution rule and the named prefix is configured to allow your chosen interface’s subnet.
For information about other features of NSX Advanced Networking click here.