Lab: Configure IPv6 Routing between NSX Segments and external networks

From Iwan
Jump to: navigation, search
Software Version Filename
VMware vCenter Server Appliance 7.00U3G VMware-VCSA-all-7.0.3-20150588.iso
VMware ESXi Server 7.00U3F VMware-VMvisor-Installer-7.0U3f-20036589.x86_64.iso
VMware NSX 4.0.0.1 nsx-unified-appliance-4.0.0.1.0.20159694.ova
TinyVM 2.7 TinyVM.ova
Ubiquiti Networks Edge Router 4 (Hardware) Edge OS v2.0.9-hotfix.2 N/A
VyOS VyOS 1.4-rolling-202202180317 VyOS 1.4-rolling-202202180317.iso
  1. Configure IPv6 OSPFv3 routing between the Pod-110 and Pod-120 Routers and the WAN Gateway.
  1. Create a Tier-0 Gateway on Pod-110 and Pod-120 and configure IPv6 BGP between the Tier-0 Gateways and the Pod Routers.
  1. Create a Tier-1 Gateway with a Web, App and DB Segment on Pod-110 and Pod-120 and connect the Tier-1 Gateway to the Tier-0 Gateway.
  1. Deploy VMs on all the segments.
  1. Make sure the Web, App and DB VMs on Pod-110 can reach the Web, App and DB VMs on Pod-120 using end-to-end IPv6 network communication.

To make it a bit easier to understand I have included two network diagrams below. One with the IPv4 address details and one with the IPv6 address details. I will be using the IPv6 address details moving forward.

Untitled.png

Untitled%201.png

The Steps

  • STEP 1: Configure IPv6 Routing using OSPFv3 on the WAN Gateway
  • STEP 2: Configure IPv6 Routing using OSPFv3 between the WAN Gateway and the Pod Gateway
  • STEP 3: Prepare Pod Gateways for IPv6 BGP
  • STEP 4: Add IPv6 BGP Uplink Segments in NSX
  • STEP 5: Create a Tier-0 Gateway
  • STEP 6: Configure IPv6 BGP Routing between Tier-0 Gateway and the Pod Gateway
  • STEP 7: Create a Tier-1 Gateway
  • STEP 8: Add IPv6 Web, App and DB Segments in NSX
  • STEP 9: Configure Route Advertise connected Tier-1 Gateway segment networks to BGP
  • STEP 10: Configure route redistribution between BGP and OSPFv3
  • STEP 11: Create Test Virtual Machines and perform ping connectivity tests


STEP 1» Configure IPv6 Routing using OSPFv3 on the WAN Gateway

The first step in this lab is to make sure OSPFv3 is configured in the WAN Gateway so that it can exchange IPv6 networks with the Pod-110 and Pod-120 Routers.

Untitled%202.png

The configuration parameters that I will used are listed in the table below.

Hardware Ubiquiti Networks Edge Router 4
Hostname WAN-Gateway
Domain Name sddc.lab
DNS Server 10.203.0.5
VLAN 203 IP Address 10.203.0.1/24
VLAN 203 IPv6 Address fd00::1/64
OSPF Area 0
OSPF dead timer 40
OSPF hello timer 10
OSPFv3 Area 0.0.0.0

The commands that I am using to configure the WAN Gateway can be found below.

WAN Gateway OSPFv3 configuration

OSPF Verification

After the configuration of the WAN Gateway I did a quick verification to see if I could see any OSPFv3 neighbors. 

admin@WAN-Gateway:~$ show ip ospf neighbor
admin@WAN-Gateway:~$

Because my Pod Routers are not configured yet with OSPFv3 I am not able to see the neighbors yet. I will do this configuration in the next step.

STEP 2» Configure IPv6 Routing using OSPFv3 between the WAN Gateway and the Pod Gateways

Now that the WAN Gateway is fully configured with OSPFv3 I am going to configure the Pod Routers with OSPFv3 so that the WAN gateway and the Pod Routers can form a neighbor relationship to exchange IPv6 routes.

Untitled%203.png

Pod 110

The configuration parameters that I will use for Pod-110 are listed in the table below.

Software VyOS
Hostname Pod-110-Router
Domain Name sddc.lab
DNS/NTP Server (IPv4) 10.203.0.5
DNS/NTP Server (IPv6) fd00:0000:0000:0000::0005
VLAN 203 IPv4 Address 10.203.0.110/24
VLAN 203 IPv6 Address fd00:0000:0000:0000::006e/64
OSPF Area 0
OSPF dead timer 40
OSPF hello timer 10
OSPFv3 Area 0.0.0.0

I also decided to configure some additional interfaces so that these networks can be redistributed into OSPF.

The configuration parameters for these interfaces ale listed in the table below.

VLAN IPv4 address IPv6 address
Management VLAN Pod 110 110 10.203.110.1/24 fd00:0000:0000:006e::0001/64
BGP Uplink VLAN #1 Pod 110 116 10.203.116.1/24 fd00:0000:0000:0074::0001/64
BGP Uplink VLAN #2 Pod 110 117 10.203.117.1/24 fd00:0000:0000:0075::0001/64

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-110-Router OSPFv3 configuration

Pod 120

The configuration parameters that I will use for Pod-110 are listed in the table below.

Software VyOS
Hostname Pod-120-Router
Domain Name sddc.lab
DNS/NTP Server (IPv4) 10.203.0.5
DNS/NTP Server (IPv6) fd00:0000:0000:0000::0005
VLAN 203 IP Address 10.203.0.120/24
VLAN 203 IPv6 Address fd00:0000:0000:0000::0078/64
OSPF Area 0
OSPF dead timer 40
OSPF hello timer 10
OSPFv3 Area 0.0.0.0

I also decided to configure some additional interfaces so that these networks can be redistributed into OSPF.

The configuration parameters for these interfaces ale listed in the table below.

VLAN IPv4 address IPv6 address
Management VLAN Pod 120 120 10.203.120.1/24 fd00:0000:0000:0078::0001/64
BGP Uplink VLAN #1 Pod 120 126 10.203.126.1/24 fd00:0000:0000:007e::0001/64
BGP Uplink VLAN #2 Pod 120 127 10.203.127.1/24 fd00:0000:0000:007f::0001/64

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-120-Router OSPFv3 configuration

OSPF Verification

Now that OSPFv3 is configured between the WAN Gateway and the Pod Routers I can now verify if there is a neighbor adjacency formed.

On the WAN Gateway I see two neighbors that are the Pod Routers. 

admin@WAN-Gateway:~$ show ipv6 ospfv3 neighbor
OSPFv3 Process (*null*)
Neighbor ID     Pri   State           Dead Time   Interface  Instance ID
10.203.0.110      1   Full/DR         00:00:31    eth1.203   0
10.203.0.120      1   Full/Backup     00:00:35    eth1.203   0
ubnt@ubnt:~$

On the Pod-110 Router I also have two neighbors. 

vyos@Pod-110-Router:~$ show ipv6 ospfv3 neighbor
Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]
10.203.0.1        1    00:00:38     Full/DROther       5d11:01:06 eth0[DR]
10.203.0.120      1    00:00:32     Full/BDR           5d17:25:40 eth0[DR]
vyos@Pod-110-Router:~$

On the Pod-120 Router I also have two neighbors. 

vyos@Pod-120-Router:~$ show ipv6 ospfv3 neighbor
Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]
10.203.0.1        1    00:00:30     Full/DROther       5d11:02:16 eth0[BDR]
10.203.0.110      1    00:00:32     Full/DR            5d17:26:56 eth0[BDR]
vyos@Pod-120-Router:~$

STEP 3» Prepare Pod Gateways for IPv6 BGP

Now that OSPFv3 os working I am now going to prepare IPv6 BGP on the Pod Routers so that it will be able to peer with the Pod Tier-0 Gateways.

Pod 110

I have already configured the BGP uplink VLANs and interfaces in the previous step.

Untitled%204.png

So now it is time to configured IPv6 BGP on Pod-110 using the configuration parameters in the table below

Neigbor Local AS Remote AS Peer IPv4 Peer IPv6
WAN Gateway 65110 65000 10.203.0.1 fd00:0000:0000:0000::0001
Pod-110-T0-EdgeVM-01-1 65110 65111 10.203.116.2 fd00:0000:0000:0074::0002
Pod-110-T0-EdgeVM-02-1 65110 65111 10.203.116.3 fd00:0000:0000:0074::0003
Pod-110-T0-EdgeVM-01-2 65110 65111 10.203.117.2 fd00:0000:0000:0075::0002
Pod-110-T0-EdgeVM-02-2 65110 65111 10.203.117.3 fd00:0000:0000:0075::0003

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-110-Router IPv6 BGP configuration

To make the SDDC Network configuration complete I have also added the VLANs and interfaces based on the table below.

VLAN IPv4 Address IPv6 Address
vMotion 111 10.203.111.1/24 fd00:0000:0000:006f::0001/64
vSAN 112 10.203.112.1/24 fd00:0000:0000:0070::0001/64
IP Storage 113 10.203.113.1/24 fd00:0000:0000:0071::0001/64
Overlay Transport 114 10.203.114.1/24 fd00:0000:0000:0072::0001/64
Service VM Management 115 10.203.115.1/24 fd00:0000:0000:0073::0001/64
RTEP Transport 118 10.203.118.1/24 fd00:0000:0000:0076::0001/64

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-110-Router IPv6 SDDC VLAN/interface configuration

Because the Pod-110 Tier-0 Gateway is not configured yet, I do not see any BGP neighbors (output not included). This will be configured in Step 4.

Pod 120

I have already configured the BGP uplink VLANs and interfaces in the previous step.

Untitled%205.png

So now it is time to configured IPv6 BGP on Pod-120 using the configuration parameters in the table below

Neigbor Local AS Remote AS Peer IPv4 Peer IPv6
WAN Gateway 65120 65000 10.203.0.1 fd00:0000:0000:0000::0001
Pod-110-T0-EdgeVM-01-1 65120 65121 10.203.126.2 fd00:0000:0000:007e::0002
Pod-110-T0-EdgeVM-02-1 65120 65121 10.203.126.3 fd00:0000:0000:007e::0003
Pod-110-T0-EdgeVM-01-2 65120 65121 10.203.127.2 fd00:0000:0000:007f::0002
Pod-110-T0-EdgeVM-02-2 65120 65121 10.203.127.3 fd00:0000:0000:007f::0003

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-120-Router IPv6 BGP configuration

To make the SDDC Network configuration complete I have also added the VLANs and interfaces based on the table below.

VLAN IPv4 Address IPv6 Address
vMotion 121 10.203.121.1/24 fd00:0000:0000:0079::0001/64
vSAN 122 10.203.122.1/24 fd00:0000:0000:007a::0001/64
IP Storage 123 10.203.123.1/24 fd00:0000:0000:007b::0001/64
Overlay Transport 124 10.203.124.1/24 fd00:0000:0000:007c::0001/64
Service VM Management 125 10.203.125.1/24 fd00:0000:0000:007d::0001/64
RTEP Transport 128 10.203.128.1/24 fd00:0000:0000:0080::0001/64

The commands that I am using to configure the Pod-110 Router can be found below.

Pod-120-Router IPv6 SDDC VLAN/interface configuration

Because the Pod-120 Tier-0 Gateway is not configured yet, I do not see any BGP neighbors (output not included). This will be configured in Step 4.

STEP 4» Add IPv6 BGP Uplink Segments in NSX

The Tier-0 Gateway is using NSX Segments as the main way of communicating with the Physical network. These segments are created inside NSX.

Pod 110

Untitled%206.png

Pod-110 is using Virtual Edges. These Edges are responsible for hosting the Tier-0 Gateway. These Edges are using VDS Port Groups, NSX Uplink Profiles. Transport Zones with Uplink Teaming Policy Names just to make sure the Tier-0 Gateway is able to create its uplink interfaces for BGP peering over VLAN 116 and 117.

For reference I have included some of the Edge prerequisites below.

  • VDS Port Groups

    Untitled%207.png

    Untitled%208.png

  • NSX Edge Uplink Profiles

    Untitled%209.png

  • NSX Edge Transport Zone

    Untitled%2010.png

  • NSX Edge configuration

    Untitled%2011.png

To configure the BGP peers towards the Pod-110 Router I have use the configuration parameters in the table below.

Segment Name Transport Zone Uplink Teaming Policy VLAN IPv6 Network IPv4 network
SEG-T0-Edge-Uplink1_VLAN-116 VLAN Tor-A 116 fd00:0:0:74::/64 10.203.116.0/24
SEG-T0-Edge-Uplink2_VLAN-117 VLAN Tor-B 117 fd00:0:0:75::/64 10.203.117.0/24

This is the output of both segments after I have created them.

Untitled%2012.png

Pod 120

Untitled%2013.png

Pod-120 is using Virtual Edges. These Edges are responsible for hosting the Tier-0 Gateway. These Edges are using VDS Port Groups, NSX Uplink Profiles. Transport Zones with Uplink Teaming Policy Names just to make sure the Tier-0 Gateway is able to create its uplink interfaces for BGP peering over VLAN 126 and 127.

  • VDS Port Groups

    Untitled%2014.png

    Untitled%2015.png

  • NSX Edge Uplink Profiles

    Untitled%2016.png

  • NSX Edge Transport Zone

    Untitled%2017.png

  • NSX Edge configuration

    Untitled%2018.png

To configure the BGP peers towards the Pod-120 Router I have use the configuration parameters in the table below.

Segment Name Transport Zone Uplink Teaming Policy VLAN IPv6 Network IPv4 network
SEG-T0-Edge-Uplink1_VLAN-126 VLAN Tor-A 126 fd00:0:0:7e::/64 10.203.126.0/24
SEG-T0-Edge-Uplink2_VLAN-127 VLAN Tor-B 127 fd00:0:0:7f::/64 10.203.127.0/24

This is the output of both segments after I have created them.

Untitled%2019.png

STEP 5» Create a Tier–0 Gateway

Now it is time to create the Tier-0 Gateways and configure the Uplink Interfaces for the BGP and uplink network traffic.

Pod 110

I have created the Tier-0 Gateway using the configuration parameters in the table below.

Name Edge Cluster
T0-Gateway-01 T0-Pod-110-T0-Edge-Cluster-01

This is the output of the Tier-0 Gateway after I have created it.

Untitled%2020.png

I have created the Tier-0 Gateway uplink interfaces using the configuration parameters in the table below.

Interface Name Edge Node Segment IPv4 Address IPv6 Address
Pod-110-T0-EdgeVM-01-1_VLAN-116 Pod-110-T0-EdgeVM-01 SEG-T0-Edge-Uplink1_VLAN-116 10.203.116.2/24 fd00:0000:0000:0074::0002/64
Pod-110-T0-EdgeVM-01-2_VLAN-117 Pod-110-T0-EdgeVM-01 SEG-T0-Edge-Uplink2_VLAN-117 10.203.117.2/24 fd00:0000:0000:0075::0002/64
Pod-110-T0-EdgeVM-02-1_VLAN-116 Pod-110-T0-EdgeVM-02 SEG-T0-Edge-Uplink1_VLAN-116 10.203.116.3/24 fd00:0000:0000:0074::0003/64
Pod-110-T0-EdgeVM-02-2_VLAN-117 Pod-110-T0-EdgeVM-02 SEG-T0-Edge-Uplink2_VLAN-117 10.203.117.3/24 fd00:0000:0000:0075::0003/64

This is the output of the EdgeVM-01 interfaces after I have created them.

Untitled%2021.png

This is the output of the EdgeVM-02 interfaces after I have created them.

Untitled%2022.png

Pod 120

I have created the Tier-0 Gateway using the configuration parameters in the table below.

Name Edge Cluster
T0-Gateway-01 T0-Pod-120-T0-Edge-Cluster-01

This is the output of the Tier-0 Gateway after I have created it.

Untitled%2023.png

I have created the Tier-0 Gateway uplink interfaces using the configuration parameters in the table below.

Interface Name Edge Node Segment IPv4 Address IPv6 Address
Pod-120-T0-EdgeVM-01-1_VLAN-126 Pod-120-T0-EdgeVM-01 SEG-T0-Edge-Uplink1_VLAN-126 10.203.126.2/24 fd00:0000:0000:007e::0002/64
Pod-120-T0-EdgeVM-01-2_VLAN-127 Pod-120-T0-EdgeVM-01 SEG-T0-Edge-Uplink2_VLAN-127 10.203.127.2/24 fd00:0000:0000:007f::0002/64
Pod-120-T0-EdgeVM-02-1_VLAN-126 Pod-120-T0-EdgeVM-02 SEG-T0-Edge-Uplink1_VLAN-126 10.203.126.3/24 fd00:0000:0000:007e::0003/64
Pod-120-T0-EdgeVM-02-2_VLAN-127 Pod-120-T0-EdgeVM-02 SEG-T0-Edge-Uplink2_VLAN-127 10.203.127.3/24 fd00:0000:0000:007f::0003/64

This is the output of the EdgeVM-01 interfaces after I have created them.

Untitled%2024.png

This is the output of the EdgeVM-02 interfaces after I have created them.

Untitled%2025.png

STEP 6» Configure IPv6 BGP Routing between Tier–0 Gateway and the Pod Gateway

Now that the Tier-0 Gateway is in place and the uplink interfaces are configured I am going to configure BGP on the Tier-0 Gateway. BGP is already configured on the POD-Router in one of the previous steps.

Pod 110

Untitled%204.png

I have configured BGP using the configuration parameters in the table below.

T0-Gateway-01
BGP enabled
Local AS 65111
Inter SR iBGP on
ECMP on
Multipath Relax on

This is the output of the Tier-0 Gateway’s BGP configuration.

Untitled%2026.png

Now that BGP is enabled I will configure the actual neighbors towards the Pod-110 Router.

I have configured the BGP neighbors using the configuration parameters in the table below.

Neigbor Local AS Remote AS Peer IPv4 Source IPv4 Peer IPv6 Source IPv6
Pod-110-Router 65111 65110 10.203.116.1 10.203.116.2

10.203.116.3

 fd00:0:0:74::1 fd00:0000:0000:0074::0002

fd00:0000:0000:0074::0003

Pod-110-Router 65111 65110 10.203.117.1 10.203.117.2

10.203.117.3

 fd00:0:0:75::1 fd00:0000:0000:0075::0002

fd00:0000:0000:0075::0003

This is the output of the Tier-0 Gateway’s BGP neighbor configuration for IPv4.

Untitled%2027.png

This is the output of the Tier-0 Gateway’s BGP neighbor configuration for IPv6.

Untitled%2028.png

💡

The BGP neighbors on the Tier-0 Gateways can be verified on both Edge-VMs by logging into the Tier-0 SR VRF (not the DR).

Verify BGP neighbors on the Pod 110 Router
Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 110 EdgeVM-01
Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 110 EdgeVM-02

Pod 120

Untitled%205.png

I have configured BGP using the configuration parameters in the table below.

T0-Gateway-01
BGP enabled
Local AS 65121
Inter SR iBGP on
ECMP on
Multipath Relax on

This is the output of the Tier-0 Gateway’s BGP configuration.

Untitled%2029.png

Now that BGP is enabled I will configure the actual neighbors towards the Pod-120 Router.

I have configured the BGP neighbors using the configuration parameters in the table below.

Neigbor Local AS Remote AS Peer IPv4 Source IPv4 Peer IPv6 Source IPv6
Pod-120-Router 65121 65120 10.203.126.1 10.203.126.2

10.203.126.3

 fd00:0:0:7e::1 fd00:0000:0000:007e::0002

fd00:0000:0000:007e::0003

Pod-120-Router 65121 65120 10.203.127.1 10.203.127.2

10.203.127.3

 fd00:0:0:7f::1 fd00:0000:0000:007f::0002

fd00:0000:0000:007f::0003

This is the output of the Tier-0 Gateway’s BGP neighbor configuration for IPv4.

Untitled%2030.png

This is the output of the Tier-0 Gateway’s BGP neighbor configuration for IPv6.

Untitled%2031.png

💡

The BGP neighbors on the Tier-0 Gateways can be verified on both Edge-VMs by logging into the Tier-0 SR VRF (not the DR).

Verify BGP neighbors on the Pod 120 Router
Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 120 EdgeVM-01
Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 120 EdgeVM-02

STEP 7» Create a Tier–1 Gateway

Now it is time to create the Tier-1 Gateways and link them to the Tier-0 Gateway.

Pod 110

I have created the Tier-1 Gateway using the configuration parameters in the table below.

Name Linked Tier-0 Gateway
T1-Gateway-01 T0-Gateway-01

This is the output of the Tier-1 Gateway after I have created it.

Untitled%2032.png

Pod 120

I have created the Tier-1 Gateway using the configuration parameters in the table below.

Name Linked Tier-0 Gateway
T1-Gateway-01 T0-Gateway-01

This is the output of the Tier-1 Gateway after I have created it.

Untitled%2033.png

STEP 8» Add IPv6 Web App and DB Segments in NSX

Now that I have created to Tier-1 Gateway and linked the Tier-1 Gateway to the Tier-0 Gateway I am going to create three segments that are going to be linked to the Tier-1 Gateway.

Pod 110

Untitled%2034.png

I have created the Segments using the configuration parameters in the table below.

Segment Name IPv6 Network IPv6 T1 Interface address IPv4 Network IPv4 T1 Interface address Transport Zone Connected Gateway
Pod-110-Web fd00:a:a::/64 fd00:a:a::1 192.168.1.0/24 192.168.1.1 Overlay T1-Gateway-01
Pod-110-App fd00:a:b::/64 fd00:a:b::1 192.168.2.0/24 192.168.2.1 Overlay T1-Gateway-01
Pod-110-DB fd00:a:c::/64 fd00:a:c::1 192.168.3.0/24 192.168.3.1 Overlay T1-Gateway-01

This is the output of all three segments after I have created them.

Untitled%2035.png

Pod 120

Untitled%2036.png

I have created the Segments using the configuration parameters in the table below.

Segment Name IPv6 Network IPv6 T1 Interface address IPv4 Network IPv4 T1 Interface address Transport Zone Connected Gateway
Pod-120-Web fd00:b:a::/64 fd00:b:a::1 192.168.5.0/24 192.168.5.1 Overlay T1-Gateway-01
Pod-120-App fd00:b:b::/64 fd00:b:b::1 192.168.6.0/24 192.168.6.1 Overlay T1-Gateway-01
Pod-120-DB fd00:b:c::/64 fd00:b:c::1 192.168.7.0/24 192.168.7.1 Overlay T1-Gateway-01

This is the output of all three segments after I have created them.

Untitled%2037.png

STEP 9» Configure Route Advertise connected Tier–1 Gateway segment networks to BGP

Now that the Segments are connected to the Tier-1 Gateways both in Pod 110 and Pod 120 these networks need to be advertised into the network so that the Virtual Machines of the Web, App and DB Segment in Pod 110 can reach the Virtual Machines of the Web, App and DB Segment in Pod 120.

Untitled%2038.png

Pod 110

T1–Gateway

On the Tier-1 Gateway I have enabled Route Advertisement for “All connected Segments & Service Ports”.

Untitled%2039.png

T0–Gateway

On the Tier-0 Gateway I have enables Route Redistribution so it will Advertise Tier-1 Subnets by enabling “Connected interfaces & Segments”.

Untitled%2040.png

Untitled%2041.png

Untitled%2042.png

Pod 120

T1–Gateway

On the Tier-1 Gateway I have enabled Route Advertisement for “All connected Segments & Service Ports”.

Untitled%2043.png

T0–Gateway

On the Tier-0 Gateway I have enables Route Redistribution so it will Advertise Tier-1 Subnets by enabling “Connected interfaces & Segments”.

Untitled%2044.png

Untitled%2045.png

Untitled%2046.png

STEP 10» Configure route redistribution between BGP and OSPFv3

In the previous step we have only enabled that the Web, App and Database are advertised into BGP. But between the Pods OSPFv3 is running.

Pod 110

To redistribute the Networks learned using BGP into OSPF and the other way around I have configured the following commands on the Pod 110 Router. 

#
set protocols ospf redistribute bgp
set protocols ospfv3 redistribute bgp
#

Verify Routing

After the redistribution configuration was done I can now see the Pod 120 networks inside my Pod 110 Router and the Pod 110 Tier0 and Tier 1 Gateway.

An output of the routing tables can be found below:

Pod-110-Router (IPv6)
Pod-110-Router (IPv4)
Pod-110-T0-EdgeVM-01 | DR-T0-Gateway-01
Pod-110-T0-EdgeVM-02 | DR-T0-Gateway-01
Pod-110-T0-EdgeVM-01 | DR-T1-Gateway-01
Pod-110-T0-EdgeVM-02 | DR-T1-Gateway-01

Pod 120

To redistribute the Networks learned using BGP into OSPF and the other way around I have configured the following commands on the Pod 120 Router. 

#
set protocols ospf redistribute bgp
set protocols ospfv3 redistribute bgp
#

Verify Routing

After the redistribution configuration was done I can now see the Pod 110 networks inside my Pod 120 Router and the Pod 120 Tier0 and Tier 1 Gateway.

An output of the routing tables can be found below:

Pod-120-Router (IPv6)
Pod-120-Router (IPv4)
Pod-120-T0-EdgeVM-01 | DR-T0-Gateway-01
Pod-120-T0-EdgeVM-02 | DR-T0-Gateway-01
Pod-120-T0-EdgeVM-01 | DR-T1-Gateway-01
Pod-120-T0-EdgeVM-02 | DR-T1-Gateway-01

WAN

The WAN Gateway also learns all the routes that are coming from Pod 110 and Pod 120.

Verify Routing

An output of the routing tables can be found below:

WAN Gateway (IPv6)
WAN Gateway (IPv4)

STEP 11» Create Test Virtual Machines and perform ping connectivity tests

To do a full end-to-end ping I have deployed some Virtual Machines (TinyVM) that I will be using for testing purposes.

Pod 110

Untitled%2047.png

I have created three Virtual Machines, one on each segment using the configuration parameters in the table below.

VM Name IPv4 address IPv4 gateway IPv6 address IPv6 gateway
Pod-110-Web 192.168.1.2/24 192.168.1.1 fd00:a:a::2/64 fd00:a:a::1/64
Pod-110-App 192.168.2.2/24 192.168.2.1 fd00:a:b::2/64 fd00:a:b::1/64
Pod-110-DB 192.168.3.2/24 192.168.3.1 fd00:a:c::3/64 fd00:a:c::1/64

Pod 120

Untitled%2048.png

I have created three Virtual Machines, one on each segment using the configuration parameters in the table below.

VM Name IPv4 address IPv4 gateway IPv6 address IPv6 gateway
Pod-120-Web 192.168.5.2/24 192.168.5.1 fd00:b:a::2/64 fd00:b:a::1/64
Pod-120-App 192.168.6.2/24 192.168.6.1 fd00:b:b::2/64 fd00:b:b::1/64
Pod-120-DB 192.168.7.2/24 192.168.7.1 fd00:b:c::3/64 fd00:b:c::1/64

Testing connectivity 1 〈CLI ping〉

Below I have collected all the ping outputs to I can prove that full end-to-end IPv6 connectivity is possible.

Pod 110 to Pod 120 IPv6 connectivity ping tests

Ping tests from the Pod 110 Web VM to all Pod 120 VMs
Ping tests from the Pod 110 App VM to all Pod 120 VMs
Ping tests from the Pod 110 DB VM to all Pod 120 VMs

Pod 120 to Pod 110 IPv6 connectivity ping tests

Ping tests from the Pod 120 Web VM to all Pod 110 VMs
Ping tests from the Pod 120 App VM to all Pod 110 VMs
Ping tests from the Pod 120 DB VM to all Pod 110 VMs

Testing connectivity 2 〈Traceflow〉

As an extra test I also did some traceflow tests,

Untitled%2049.png

Pod 110 Web to Pod 120 Web IPv6 traceflow test

Untitled%2050.png

The packets are successfully delivered.

Untitled%2051.png

Pod 110 Web to Pod 110 App IPv6 traceflow test

Because the traffic is now staying within the same NSX Domain (Web to App inside Pod 110) traceflow generates a nice diagram and shows how the traffic is flowing. The packets are successfully delivered.

Untitled%2052.png

Retrieved from "http://www.iwanhoogendoorn.nl/index.php?title=Lab:_Configure_IPv6_Routing_between_NSX_Segments_and_external_networks&oldid=5291"