VMWare NSX EDGE and OSPF Routing

Configuration
Introduction

Below picture will give you an idea of our setup before moving forward.
Deploy NSX EDGE

Login to vCenter – Network and security – NSX Edge – click on + sign to deploy an EDGE
appliance.

Select edge services gateway – Provide Name and hostname as EDGE-01 , select Deploy
NSX Edge , select enable HA only if you are using single edge and not ECMP.

Provide login name for edge, password and enable SSH

Select + sign under edge appliances and provide the location where the EDGE appliance will
beployed, Typically you will deploy this in EDGE cluster or Production cluster.
Provide the size, as in my case its my lab so compact but based on your environment select it.
Now the important step is the interfaces. In my case my edge will be connected to my
physical router with uplink.

provide name for uplink – select uplink – select the distributed port group which has access to
physical router, provide IP for this interface – ok

In my case remember my physical router ip is 192.168.2.1 so i am using 192.168.2.2 for

edge.
Now create interface to connect to DLR.

remember we connected DLR uplink with transit-LS and gave IP 2 to DLR.

Now provide name – select internal – click change and select Transit-LS logical switch –
provide IP 192.168.8.1
As shown below both uplink and internal interfaces are configured.
select uplink and provide the physical router ip and next
click on configure firewall – accept for now and next
review and click finish to deploy edge appliance.
Now as shown below edge appliance is deployed successfully.

Configure OSPF between DLR and EDGE

First we need to configure OSPF in DLR then in Edge.

OSPF in DLR

Double click on DLR – Mange – routing – global configuration – click edit under dynamic
routing
Select transit to edge and click ok

Click on Publish changes so that Router ID will be configured.

Now click on OSPF – Edit

Before moving to next step for OSPF configuration in DLR we need couple of things.

1. Area ID – which is the OSPF area ID used.

2. Forwarding address – 192.168.8.2 ( this is the interface IP used before while deploying DLR)
3. Protocol address – 192.168.8.3 ( this is the extra IP required for Dynamic routing
configuration)

Select the transit-2-edge , provide the protocol address and forwarding address as shown
below.
then remove the default 51 area as shown below.

Click on + sign under area definitions and create new area say 10 and type NSSA
Click on + sign in area to interface mapping

provide the interface-2-edge , select area 10 and ok.

review all the information and click on publish changes.

OSPF in EDGE

Now back to network and security – click on edge appliance – enable router ID as shown
below as we have done for DLR.

select uplink and click ok.

Publish changes
Now click on OSPF – EDIT

Select enable OSPF – ok

Note: remove area 51 if required.

Click on + sign in areas and create the area 10, provide 10 – NSSA and ok.

Note: this is the same area we had created in DLR also.

Click on + sign in area to interface mapping – select Transit-2-DLR and area 10- ok
Review the information and click on publish changes.

Now click on route redistribution – select OSPF – ok

Then Click edit (pencil) on route redistribution table – select any- OSPF – static routes and
connected – ok as shown below.
Click on publish changes. This will make sure the connected and static routes are pushed to
DLR.

I had created two physical server subnets as static routes and pointed them to my physical
router as shown below.
Verifying OSPF confiruation

Now login to NSX edge appliance as admin and password given while creating

provide command – show ip route

as shown below 172.16.10.1 and other two are showing as O meaning learned with OSPF and
next hop as DLR interface IP 192.168.8.2

Similarly connect to DLR using the protocol address as shown below.

show ip route command will give the static routes created in Edge and connected routes in
DLR.

C means connected routes, O means routes learned from OSPF which are static routes created
in EDGE.
To test i am trying to ping the DLR interface IP, protocol IP and gateway IP’s from physical
subnets.

Note: make sure on your physical router create static routes or configure OSPF between
physical router and EDGE for learning subnets created in DLR like 172.16.10.x